Calling all experts!! Think I've killed it........? - ONE Q&A, Help & Troubleshooting

I have a recent thread ' A real amateur'
But I have started a new one as I have delved deeper into the depths of a dead phone
This is a slight continuation from the previous thread but what I've done now is more worrying.
I had wanted to put pie os on phone, updated twrp the wrong way and wouldn't go into recovery.
Tried to use guides on fastboot and I have had no luck at all with it. Tried SDK downloads and my pc wouldn't run the files( winrar and 7zip didn't show .exe files, just 'emulators'. Even right clicked to run as administrator but still, no luck.
Pc wouldn't recognise my phone also, even turning debugging mode on and alsorts.
So I thought i could run factory reset..? And as you'd of guessed, I have TOTALLY wiped the lot so there's no OS (was using resurrection remix) and now I can't turn phone on and no recovery and the only option available for the phone is fastboot but my pc won't recognise the device, nor can I get SDK, ADB or fastboot to work on my phone.
Have I completely killed my phone now???
I hope not and thank you in advance for the tremendous amount of help in advance and previously.
Someone help me

Hi
Have you tried this? it detects and installs a new rom by scaning the com ports, worked for me in the past.
https://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732

ricardopt78 said:
Hi
Have you tried this? it detects and installs a new rom by scaning the com ports, worked for me in the past.
https://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
Click to expand...
Click to collapse
Hi ricardopt78.
No I haven't tried this as I never knew about it but I will give it a go and let you guys know how I get on.
Thank you very much!! ?

Related

[Q] HTC HD7 Diag Mode and Zune need some help

This mode was accidentally entered when I'm trying to boot my htc hd7 and press camera button together with volume up (around 20sec while the phone booting). For your information, my htc hd7 having problem with zune application and my device manager recognize it as unknown devices (yellow exclamation mark).
It was caused when I've sideloading USBModeSwitch.xap and change from ZUNE to DIAG mode. After the phone restarting, the apps has been revoke then i've no chances to install the apps again to fix it back to ZUNE mode.
Now the phone can operate as usual but cannot recognize by zune (yellow exlamation mark in device manager in PC).
The good news is, the phone had recognized by pc when entering this mode. and the devices manager detect the phone under Portable Devices -> Schubert. Can we sideloading apps using this mode? If yes... it was a good news for those having the same problem with me. But the question is.. HOW.
Note: After the incident, I already flash the phone. but still unable to be detected by ZUNE Desktop in normal state. it can operate, can install from market place as usual but cannot sync with zune desktop. Can somebody help me on this? Sorry for my English. You may refer with my attachment for the images and the XAP application.
Note 2: Never try the USBModeSwitch.xap if your phone is not fully unlock or will facing the same problem with me. hope someone can fix this issue. because lot of friends are stuck in this doom.
same problem here....
an hd7 too...
First, are your phones unlocked? I assume they are. Otherwise you wouldn't be able to deploy this USB-whatever.xap.
You may try deploying smth after running WPConnect (Phone has to be connected already). This small consoleapp does some funny stuff with the phone/PC connection. So maybe your devices will be recognized this way.
Best you start WPConnect from commandline, to have a look at the output, which should be smth like "[Devicename] successfuly connected..." or such.
C~
tried it, doesn't help
the phone is not unlocked anymore... that is the problem in my case ;-)
but i was able to install the HTC Diagnostic Drivers...
but i dont know if i can use it to disable Diag-Mode...
And you are not able to re-unlock your phone (via official or Chevron)? Have you tried to unlock after connecting - closing Zune - running WPConnect?
This is just a mere guess, but hey, who knows it maybe work
we cannot lock our devices as neither zune nor WPConnect realize that the phone is connected (because of it is in Diagnostic-Mode)
but thanks for your reply ;-)
Oberoth said:
we cannot lock our devices as neither zune nor WPConnect realize that the phone is connected (because of it is in Diagnostic-Mode)
but thanks for your reply ;-)
Click to expand...
Click to collapse
Yup that's true. I try to used ansar ROM, flash it, but nothing change. I wonder if we can custom a rom and implement the extract file of USBModeswitch.xap to the rom. so that the phone will boot with usbmodeswitch installed in it, using this step, we're able to switch the mode from diag back to zune.
This the final technique might can help for now. For the ROM, i can only break/extract until I've got the 2 OS file:- 2_os.nb.extra (±2.4MB) and the other one is 2_os.nb.payload (±181MB). Ok, until then, I was stuck. if not... we can extract the XAP directly to the OS folder, then repacking back the ROM. the 2_os.nb.payload file was unable to extract to bin file. Error shown:- "no boot partition". Maybe I'm using the old WinMo tools to extract it.
ahhh.... gosh... stuck in this step. any help and guide will be much appreciated.
AzmanIshak said:
Yup that's true. I try to used ansar ROM, flash it, but nothing change. I wonder if we can custom a rom and implement the extract file of USBModeswitch.xap to the rom. so that the phone will boot with usbmodeswitch installed in it, using this step, we're able to switch the mode from diag back to zune.
This the final technique might can help for now. For the ROM, i can only break/extract until I've got the 2 OS file:- 2_os.nb.extra (±2.4MB) and the other one is 2_os.nb.payload (±181MB). Ok, until then, I was stuck. if not... we can extract the XAP directly to the OS folder, then repacking back the ROM. the 2_os.nb.payload file was unable to extract to bin file. Error shown:- "no boot partition". Maybe I'm using the old WinMo tools to extract it.
ahhh.... gosh... stuck in this step. any help and guide will be much appreciated.
Click to expand...
Click to collapse
Hi,
from your writing i can read that you have the needed knowledge to make this thing...
so how long do you think will it take to get the two files...
and if you get these files, how can we flash that ROM without HSPL or SSPL?
thanks for your answer ;-)
our problem is... there's still no kitchen for WP7 (temporary). So.. we have to wait Da_G or Ansar.Ath.Gr work. they might have some tools that can help us. I knew.. lot of our friend already stuck in this mode as well. So... there's no sync with zune for us... no music transfer via usb.. and we have to forget all the thing that we can do using the USB cable except for charging it. lol~ how sick...
yeah...
i can only listen to radio in the morning when i drive to school...
i hate the most of the breakfast-shows
i have another idea instead of waiting for an C-ROM...
but that is only possible with a clean, Chevron-Unlocked and USB-Switch installed WP7 phone...
so nothing personally...
and we need to wait for the update...
the whole clean system would be backed up and could be used for our WP7 devices to get the USBSwitch-App onto our phone (holding camera-key when starting to install backup)
would be great if there is anybody who makes it...
hi
ask the autor of this http://forum.xda-developers.com/showthread.php?t=922000
maybe he can help ,his tool use usbmodeswitch.
im active in his thread too, but he didn't answer at all...
I have actally done this myself sadly the only option I had was to sync all my contacts with Windowslive and reset the HD7 by holding both volume keys while powering it on from a cold boot.
AzmanIshak said:
This mode was accidentally entered when I'm trying to boot my htc hd7 and press camera button together with volume up (around 20sec while the phone booting). For your information, my htc hd7 having problem with zune application and my device manager recognize it as unknown devices (yellow exclamation mark).
It was caused when I've sideloading USBModeSwitch.xap and change from ZUNE to DIAG mode. After the phone restarting, the apps has been revoke then i've no chances to install the apps again to fix it back to ZUNE mode.
Now the phone can operate as usual but cannot recognize by zune (yellow exlamation mark in device manager in PC).
The good news is, the phone had recognized by pc when entering this mode. and the devices manager detect the phone under Portable Devices -> Schubert. Can we sideloading apps using this mode? If yes... it was a good news for those having the same problem with me. But the question is.. HOW.
Note: After the incident, I already flash the phone. but still unable to be detected by ZUNE Desktop in normal state. it can operate, can install from market place as usual but cannot sync with zune desktop. Can somebody help me on this? Sorry for my English. You may refer with my attachment for the images and the XAP application.
Note 2: Never try the USBModeSwitch.xap if your phone is not fully unlock or will facing the same problem with me. hope someone can fix this issue. because lot of friends are stuck in this doom.
Click to expand...
Click to collapse
can you tell me what rom was on the phone and what rom you flashed After you F*****up your phone ?
I want to know what Radio was on it , I think that tool does something with the radio rom on the phone , it could help the flash an older rom using a goldcard with an older radiorom in it.
edit:
maybe it is the spl , try to flash a rom with a lower/higher spl number.
ceesheim said:
can you tell me what rom was on the phone and what rom you flashed After you F*****up your phone ?
I want to know what Radio was on it , I think that tool does something with the radio rom on the phone , it could help the flash an older rom using a goldcard with an older radiorom in it.
edit:
maybe it is the spl , try to flash a rom with a lower/higher spl number.
Click to expand...
Click to collapse
Hi Ceesheim, thanks for reply. I'm not remember my preveous ROM, by the way
currently only RUU_Schubert_hTC_Asia_WWE_1.23.707.01_Radio_5.51.09.06a_22.30.50.09U_Signed_by_ansar that can be flash to my phone.
AzmanIshak said:
Hi Ceesheim, thanks for reply. I'm not remember my preveous ROM, by the way
currently only RUU_Schubert_hTC_Asia_WWE_1.23.707.01_Radio_5.51.09.06a_22.30.50.09U_Signed_by_ansar that can be flash to my phone.
Click to expand...
Click to collapse
thats a modded rom (don't use it)
try this one :
http://forum.xda-developers.com/showthread.php?t=853945
Hi
i think the best way to fix your problem is this rom.
http://forum.xda-developers.com/showthread.php?t=948497
this one contain developer tools & can help you with usb problem.
send me a pm after install it an maybe we can fix this.
xboxmod said:
Hi
i think the best way to fix your problem is this rom.
http://forum.xda-developers.com/showthread.php?t=948497
this one contain developer tools & can help you with usb problem.
send me a pm after install it an maybe we can fix this.
Click to expand...
Click to collapse
ok... will test it now. thanks!
I'll report to you after complete. thanks again~
xboxmod said:
Hi
i think the best way to fix your problem is this rom.
http://forum.xda-developers.com/showthread.php?t=948497
this one contain developer tools & can help you with usb problem.
send me a pm after install it an maybe we can fix this.
Click to expand...
Click to collapse
I already download and install to my PC. but cannot flash to my phone.
Currently the only ROM that my HD7 can flash is with this number: 1.23.707.01
Make a goldcard and then flash it
Sent from my HD7 T9292 using Board Express

Help !! I cannot install a rom

Hello,
Few months ago , the power button of my nexus s had broken. I used volume rocker and I could turn on the screen.
Today I tried to flash a rom . I have done this before many times and I know the process.
After I had wiped all the data ( system , faxtory reset, cache) , I pulled off the battery.
When the phone starts it stucks on google logo , because there is no rom in it.
When I boot it into the fastboot mode , my pc cannot recognize it at all, I plug it in my pc and there is no sign that a new hardware has been installed.
I don't know what else to do. If I could get it recognized by my pc , I would be able to silve the problem.
Any suggestions on how can I fix it? Can I fix the fastboot mode problem????
Thanks for your time
I am looking forward hearing your replies...
If you don't have this installed on your PC already, you should install it and follow the directions for installing the drivers carefully. It worked for me.
P.S. this thread belongs in Q&A
Thanks for the reply but it cannot do anything. I posted here so as I can get help from developers who know more stuff than other users.
unless your thread is about ANDROID DEVELOPMENT ... IE your own ROM / KERNEL / MOD etc... it should be in q and a or general.
OP that is not how it works, posting in the Development Section because you believe the help is great there....WRONG! Sir, you will find the best help is in the proper place in the proper Threads....Please familiarize yourself with the Forum Rules on Posting. Thank You and Moved here.
When you connect your phone to your PC while it's in fastboot mode, if you haven't tried already, go to device manager (assuming your pc is running windows), there should be an unrecognized device in the list, if so you can right click on it and choose update driver, then select driver manually and navigate to the data/drivers folder where ever you have Wug's tool installed (if you don't have it installed then you should), that should properly install the drivers and allow your computer to recognize the phone, then you can use the flash stock+unroot option to repair your phone.
If you don't see any change in device manager when your phone is connected to your computer then I can't help much, maybe try a different usb port if you haven't already.
Good luck
jj_z1 said:
When you connect your phone to your PC while it's in fastboot mode, if you haven't tried already, go to device manager (assuming your pc is running windows), there should be an unrecognized device in the list, if so you can right click on it and choose update driver, then select driver manually and navigate to the data/drivers folder where ever you have Wug's tool installed (if you don't have it installed then you should), that should properly install the drivers and allow your computer to recognize the phone, then you can use the flash stock+unroot option to repair your phone.
If you don't see any change in device manager when your phone is connected to your computer then I can't help much, maybe try a different usb port if you haven't already.
Good luck
Click to expand...
Click to collapse
There are no changes when I plug in the phone, I tried all the usb ports , other pc and other new cable but nothing work.
Thanks for the reply

Stuck in bootloader ? Or device recognition problem ?

Hello everyone !
This morning, out of the blue (I think it was during a Whatsapp automatic backup), my Google Pixel 2 XL shut down. I can't get it started and the phone is stuck on the white screen with the Google Logo. I can access the bootloader and Recovery though, so that's something. I spent my whole day skimming through the forum and other websites/videos. but I only have a slight understanding of what is happening and I'm not sure where my problem lays. Now when I click on the Start option in the bootloader, it just starts back in the bootloader screen.
I've been a bad scholar and did not backup my data. So if there is a solution, I'd rather not factory reset my phone.
Got my phone a month ago.
I unlocked the bootloader and rooted the phone (Magisk).
Stock Rom
Today,
I tried to connect my phone to my computer but so far it is not recognised by my computer and I can't access OEM unlocking/usb modes.
I verified. I have the latest adb and fastboot version on my computer, dowloading the latest SDK platforms tools.
I downloaded the usb driver packages from the SDK manager.
I tried using an universal android adb driver tool.
I've used multiple usb-c to usb-c and usb-c to usb-a cables, on different ports.
I restarted my phone and computer multiple times (just to make sure)
My phone doesn't appear in the Device manager.
I am now completely lost and would really much appreciate your help.
Thank you for reading this. Thank you for helping me !
Sounds bad.....maybe in first instance try letting tge device shut off due to low battery. Maybe this helps to hard reset. So just leave it on in fastboot mode
donkeydances said:
Hello everyone !
This morning, out of the blue (I think it was during a Whatsapp automatic backup), my Google Pixel 2 XL shut down. I can't get it started and the phone is stuck on the white screen with the Google Logo. I can access the bootloader and Recovery though, so that's something. I spent my whole day skimming through the forum and other websites/videos. but I only have a slight understanding of what is happening and I'm not sure where my problem lays. Now when I click on the Start option in the bootloader, it just starts back in the bootloader screen.
I've been a bad scholar and did not backup my data. So if there is a solution, I'd rather not factory reset my phone.
Got my phone a month ago.
I unlocked the bootloader and rooted the phone (Magisk).
Stock Rom
Today,
I tried to connect my phone to my computer but so far it is not recognised by my computer and I can't access OEM unlocking/usb modes.
I verified. I have the latest adb and fastboot version on my computer, dowloading the latest SDK platforms tools.
I downloaded the usb driver packages from the SDK manager.
I tried using an universal android adb driver tool.
I've used multiple usb-c to usb-c and usb-c to usb-a cables, on different ports.
I restarted my phone and computer multiple times (just to make sure)
My phone doesn't appear in the Device manager.
I am now completely lost and would really much appreciate your help.
Thank you for reading this. Thank you for helping me !
Click to expand...
Click to collapse
Flash latest factory image (either 8.1 or DPx/P/9.0).
mrorange2108 said:
Sounds bad.....maybe in first instance try letting tge device shut off due to low battery. Maybe this helps to hard reset. So just leave it on in fastboot mode
Click to expand...
Click to collapse
I'm trying that. Thank you !
xFirefly93 said:
Flash latest factory image (either 8.1 or DPx/P/9.0).
Click to expand...
Click to collapse
Thank you for your answer. How would you do that ? I can't get it to be recognized by my computer.
donkeydances said:
Thank you for your answer. How would you do that ? I can't get it to be recognized by my computer.
Click to expand...
Click to collapse
Have you tried with the Fastboot protocol?
xFirefly93 said:
Have you tried with the Fastboot protocol?
Click to expand...
Click to collapse
Like I said, I can't get my phone to be recognized by my computer so no Fastboot protocol. I am not sure why it doesn't get recognized though.

Firmware Upgrade Encountered an Issue. Tab 2 7 (P3110)

Hi,
Yes, I know, there's a million topics about this and I'm pretty sure I tried them all!
Long story short: been running Lineage OS on my Tab 2 for a while but it's been sitting in a drawer. Saw a video about using old tablets for emulating retro consoles and the Tab works a dream for that. So I bought a Bluetooth controller for better gameplay but it just wouldn't work under Lineage so thought I'd flash the original ROM back onto it to see if that would work. I'm not a n00b, but haven't done it for a while so thought to be safe I'd follow a guide. All seemed to be working well when Odin crashed and left me with the Firmware Upgrade Failed error.
I've been trying for about four hours to get it back, but having no luck. I've tried the latest version of Odin, as well as the old 1.7 version I was using; tried Kies, tried uninstalling Kies; tried uninstalling the stock drivers MS installed when connected, no go. Interestingly Odin doesn't seem to see the Tab at all now, so I tried the UniversalADB installer, tried installing ADB drivers as well as Samsung drivers manually, but nothing works, it just sits at "connecting" but never actually does. Also tried different stock ROMs to no avail. I think my issue is with the ADB drivers, just don't know how to fix it.
I don't know what to try now. Any advice?
Using MS Surface Pro (2017) running Win10.
Not allowed to post screenshots, but do have some.
Thanks.
How is the tab behaving after this crash?
Can you use the tab as usual? But you are still in LineageOS? If Yes, what version of LineageOS?
Can you still get into Recovery Mode? If Yes, what Recovery and version do you have?
Download Mode seems Ok, but not Odin at the PC end. Correct?
The more info you can give the better. Also if you prepared the tab in any way other than just entering download mode.
Did you enable USB Debugging for example? (but I'm not sure how important that is)
Or wiped anything in recovery?
I'm not sure if I can help, but surely there must exist someone here that can. I'm new to the android world, but used to work in IT Support and Network Administration.
And 100 years ago I blogged with Blogger, but sat and amended the xml-file to get the design I wanted more than creating blog entries
Anyway, I hope it gets sorted.
Tab_Triggerhappy said:
How is the tab behaving after this crash?
Can you use the tab as usual? But you are still in LineageOS? If Yes, what version of LineageOS?
Can you still get into Recovery Mode? If Yes, what Recovery and version do you have?
Download Mode seems Ok, but not Odin at the PC end. Correct?
The more info you can give the better. Also if you prepared the tab in any way other than just entering download mode.
Did you enable USB Debugging for example? (but I'm not sure how important that is)
Or wiped anything in recovery?
I'm not sure if I can help, but surely there must exist someone here that can. I'm new to the android world, but used to work in IT Support and Network Administration.
And 100 years ago I blogged with Blogger, but sat and amended the xml-file to get the design I wanted more than creating blog entries
Anyway, I hope it gets sorted.
Click to expand...
Click to collapse
Hi,
Thanks for your reply and sorry it's taken me so long to respond; I've got several health issues I have to work around!
I can't get into the OS at all, it's just stuck at the "Firmware upgrade..." screen and there's nothing else I can do with it.
It was rooted and I was running TWRP recovery, but can't access it at all now. I did a wipe in TWRP but was still able to boot into it before I ran Odin. Odin worked fine, then it just stopped for reasons unknown and now there's nothing I can do with the Tab at all.
I see this in Device Manager: samsung mobile usb cdc composite device. Have tried manually installing driver but nothing seems to work.
Have tried it on my Mum's Win7 machine, but to no avail. I really need ADB drivers but I can't install them without turning on debugging on the Tab and I can't do that because I can't get out of this blasted error screen!
There's literally nothing else I can say about it as this is all that's happening.
Annnnd, now it doesn't seem to want to hold a charge. :crying:
Thanks again.
I've tried following a few tutorials, but I can't get past the ADB issue. Does anyone know of, or can link to, a solution to this please? I really want my Tab back!
Thanks!
Tabby22020 said:
I've tried following a few tutorials, but I can't get past the ADB issue. Does anyone know of, or can link to, a solution to this please? I really want my Tab back!
Thanks!
Click to expand...
Click to collapse
Maybe a longshot, but you can test if this free version can access the tab:
https://www.tenorshare.com/products/reiboot-for-android.html
No use buying if it can't.
But since Device Manager sees something it's worth a shot.
Do you have to longpress power button to turn it off?
If so... when the screen goes off, have you tried to quickly let go of the power button and immediately press it again together with Volume Up?
Or down, for download instead of Recovery.
With my P3100 it was much easier with no charger plugged in...
Edit:
Tried the software and my tab is OK, but no connection established anyway. Only result was that I couldn't access tab in File Explorer and MTP state... only PTP.
In Device Manager I got a new Android Device: Something like Google Nexus ADB... sorry but I uninstalled it directly without noting exact name.
Replugged USB cable and MTP working again.

help !. Bricked OP8 t-mobile unlocked

Hey guys. I need some help. this is my wrong doing !!
I got a network unlocked T mobile which I started using with AT&T. Today I received the unlock code from T mobile to unlock bootloader which I did. then I I installed TWRP and Magisk without any issues. then I tried to fix the persis.img coz fingerpritn is not working. it didnt work so I left it alone. But I dont know why I wiped cache, data and then phone got stuck at boot loop. (no backup). I tried to install using MSM tool but it didnt work. MSM tool was not detecting the phone. then in TWRP I clicked on EDL and now the phone screen is blank. tried every possible combination of keys but no luck. was doing all this on windows 10. any help would be greatly appreciated. thanks
kool_am said:
Hey guys. I need some help. this is my wrong doing !!
I got a network unlocked T mobile which I started using with AT&T. Today I received the unlock code from T mobile to unlock bootloader which I did. then I I installed TWRP and Magisk without any issues. then I tried to fix the persis.img coz fingerpritn is not working. it didnt work so I left it alone. But I dont know why I wiped cache, data and then phone got stuck at boot loop. (no backup). I tried to install using MSM tool but it didnt work. MSM tool was not detecting the phone. then in TWRP I clicked on EDL and now the phone screen is blank. tried every possible combination of keys but no luck. was doing all this on windows 10. any help would be greatly appreciated. thanks
Click to expand...
Click to collapse
So it turns out its not a hard brick. I'm stuck on TWRP. I'm able to get to fastboot. I tried to install Oxygen OS thru fastboot but the PC is not detecting the phone in fastboot. Mac detects it but I believe all the stock Roms are for PC use. I did try it on my MAc and was able to open a terminal window inside the Oxygen OS folder but then the fastboot device command is not found. any help would be greatly appreciated. I installed SDK and ADB drivers on PC but in device manager the device still only shows as Android device with no drivers. !! thanks
kool_am said:
So it turns out its not a hard brick. I'm stuck on TWRP. I'm able to get to fastboot. I tried to install Oxygen OS thru fastboot but the PC is not detecting the phone in fastboot. Mac detects it but I believe all the stock Roms are for PC use. I did try it on my MAc and was able to open a terminal window inside the Oxygen OS folder but then the fastboot device command is not found. any help would be greatly appreciated. I installed SDK and ADB drivers on PC but in device manager the device still only shows as Android device with no drivers. !! thanks
Click to expand...
Click to collapse
Solved !
solved how? i greatly would like to know how to flash from fastboot, i know that isnt what this thread was about but im having the exact same problems you are with msm. i can see the phone in fastboot but i have no idea how to flash or what to flash from there. I can get into recovery but i cant copy anything over to the phone and the drivers dont show up for adb. so i pretty much ONLY have fastboot and dont know what to do! 2 days since the phone been down and im lost AF
JCroffut said:
solved how? i greatly would like to know how to flash from fastboot, i know that isnt what this thread was about but im having the exact same problems you are with msm. i can see the phone in fastboot but i have no idea how to flash or what to flash from there. I can get into recovery but i cant copy anything over to the phone and the drivers dont show up for adb. so i pretty much ONLY have fastboot and dont know what to do! 2 days since the phone been down and im lost AF
Click to expand...
Click to collapse
Can msm detect the phone when connected in fastboot. Also check device manager in pc to make sure it detects the phone as qualcomm device. Otherwise msm will not work.
Download msm. Turn phone off. Connect phone to pc. Open msm. Press start. Press volume down and power button on phone. It should be detected by msm and should start flashing the software.
Standby....
When plugged in the phone in EDL it shows
QUSB_BULK_CID0412 with an exclamation mark inside a yellow triangle
When i plugged in the phone and open fastboot it shows
Android with an exclamation point inside a yellow triangle
I booted up msm, clicked other, clicked start, pressed volume down and volume up and plugged it in. still says waiting for device to connect. ive also tried this with a number of keys being help, ive tried to boot from twrp straight into edl mode, none of which works
which all says to me its a driver issue of some kind, but for 3 days ive been slaving away on xda and cannot for the life of me figure out where to get the drivers.
JCroffut said:
Standby....
When plugged in the phone in EDL it shows
QUSB_BULK_CID0412 with an exclamation mark inside a yellow triangle
When i plugged in the phone and open fastboot it shows
Android with an exclamation point inside a yellow triangle
I booted up msm, clicked other, clicked start, pressed volume down and volume up and plugged it in. still says waiting for device to connect. ive also tried this with a number of keys being help, ive tried to boot from twrp straight into edl mode, none of which works
which all says to me its a driver issue of some kind, but for 3 days ive been slaving away on xda and cannot for the life of me figure out where to get the drivers.
Click to expand...
Click to collapse
It is a driver issue for sure. When connected device manager should detect as qualcomm hd9008.......
kool_am said:
It is a driver issue for sure. When connected device manager should detect as qualcomm hd9008.......
Click to expand...
Click to collapse
i figured that, i am at a complete loss as to where to find the drivers. i actually might need you to hold my hand on this one a tiny bit because im about to smash the phone on the ground and say someone stole it. thats where i am with this phone haha
JCroffut said:
i figured that, i am at a complete loss as to where to find the drivers. i actually might need you to hold my hand on this one a tiny bit because im about to smash the phone on the ground and say someone stole it. thats where i am with this phone haha
Click to expand...
Click to collapse
qualcomm hs-usb qdloader 9008 - this is the exact name of the driver.
Try this link: https://forum.xda-developers.com/t/guide-fixing-hard-bricks-qualcomm-hs-usb-qdloader-9008.3403868/
kool_am said:
qualcomm hs-usb qdloader 9008 - this is the exact name of the driver.
Try this link: https://forum.xda-developers.com/t/guide-fixing-hard-bricks-qualcomm-hs-usb-qdloader-9008.3403868/
Click to expand...
Click to collapse
standby ill read through it now. we also have 2 different threads going so i can combine them if thats easier for you
kool_am said:
qualcomm hs-usb qdloader 9008 - this is the exact name of the driver.
Try this link: https://forum.xda-developers.com/t/guide-fixing-hard-bricks-qualcomm-hs-usb-qdloader-9008.3403868/
Click to expand...
Click to collapse
Only download the qualcomm driver from this link. Or search for it online.
I have spent much more time than you trying to figure this out. I have a pc and Mac both. Mac is not compatible with a lot of the software and my pc usb ports are all bad. Point being, leave it alone for a day or so. Come back at it with a fresh start and fresh mind.
kool_am said:
Only download the qualcomm driver from this link. Or search for it online.
I have spent much more time than you trying to figure this out. I have a pc and Mac both. Mac is not compatible with a lot of the software and my pc usb ports are all bad. Point being, leave it alone for a day or so. Come back at it with a fresh start and fresh mind.
Click to expand...
Click to collapse
i hear that. after 3 days of non stop working at it im pretty sure im just not smarter than the phone today lol. looks like this phone is now stolen and going into a trash can lol
JCroffut said:
i hear that. after 3 days of non stop working at it im pretty sure im just not smarter than the phone today lol. looks like this phone is now stolen and going into a trash can lol
Click to expand...
Click to collapse
If I were you, I wouldn't throw the phone away. Like I said it's a simple issue of driver. Install the correct driver and make sure you see it as qualcomm device in device manager. Trust me, from then on, it's just a matter of a few clicks.
I unbricked my phone to t mobile and then converted to global rom without any issues.
kool_am said:
If I were you, I wouldn't throw the phone away. Like I said it's a simple issue of driver. Install the correct driver and make sure you see it as qualcomm device in device manager. Trust me, from then on, it's just a matter of a few clicks.
I unbricked my phone to t mobile and then converted to global rom without any issues.
Click to expand...
Click to collapse
i sent you a private convo on here if thats ok so i dont spam the forum! You may be able to help me out if i could borrow a few minutes of your time!
JCroffut said:
i hear that. after 3 days of non stop working at it im pretty sure im just not smarter than the phone today lol. looks like this phone is now stolen and going into a trash can lol
Click to expand...
Click to collapse
i was definatly kidding tho this is my only phone and i have to solve this problem lol
I'm not sure if you have read this thread already. I messed up my phone a couple days ago as well and follow the steps there and was able to MSM my phone back to stock.
[OP8][OOS TMO 55CB] 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

Categories

Resources