Ive flashed many photon Q's before using RSD lite but for some reason now they wont even show up in AP Fastboot. IM not sure why but im wondering if it has anything to do with installing PDAnet a few weeks ago for htc drivers. RSD does however recognize my photon q booted normally. I can choose the file to flash and hit start, but where RSD used to reboot the phone into fastboot and start flashing, it says "The phone failed to switch to fastboot mode". Any help would be appreciated. I used to use RSD 6.1.4 and now use 6.1.5. This is happening with both versions. ive updated drivers, uninstalled and reinstalled drivers, uninstalled PDAnet.....
Have you tried forcing the device into fastboot mode yourself?
Code:
adb reboot bootloader
arrrghhh said:
Have you tried forcing the device into fastboot mode yourself?
Code:
adb reboot bootloader
Click to expand...
Click to collapse
the phone goes into fastboot mode. I can get it by holding vol up and down and power. The problem is that when in fastboot, it isnt recognized by RSD. where in the past it has been. it just stopped one day. the drivers fail and i go to device manager and cant find a driver that needs updating to get the phone to connect. if you know of a driver i need to install manually please let me know what it is cause nothing is jumping out as needing updating. thank you.
wbbjason said:
the phone goes into fastboot mode. I can get it by holding vol up and down and power. The problem is that when in fastboot, it isnt recognized by RSD. where in the past it has been. it just stopped one day. the drivers fail and i go to device manager and cant find a driver that needs updating to get the phone to connect. if you know of a driver i need to install manually please let me know what it is cause nothing is jumping out as needing updating. thank you.
Click to expand...
Click to collapse
Hm, I think the Motorola Device Manager was all I needed on my Windows machine.
arrrghhh said:
Hm, I think the Motorola Device Manager was all I needed on my Windows machine.
Click to expand...
Click to collapse
already had that. most recent version. uninstalled and reinstalled that as well. i have no idea why none of the photon Qs will connect now.
Try usbdeview uninstall and delete! all moto drivers and reinstall.
Photon Q &/or Note 3 on ting.com
arrrghhh said:
Hm, I think the Motorola Device Manager was all I needed on my Windows machine.
Click to expand...
Click to collapse
rbeavers said:
Try usbdeview uninstall and delete! all moto drivers and reinstall.
Photon Q &/or Note 3 on ting.com
Click to expand...
Click to collapse
Thanks for the help guys. So problem still unsolved but today I went back at it and noticed that the phone was showing up in device manager as "Samsung mobile device". So i uninstalled that driver, put it back into AP fastboot and plugged it in. now under "other devices" i have "Fastboot ASANTI_C S" and it needs to be updated. i want to make sure i update it with the correct file. if anyone knows where i can find this on my computer or the internet please let me know. it would be greatly appreciated.
wbbjason said:
Thanks for the help guys. So problem still unsolved but today I went back at it and noticed that the phone was showing up in device manager as "Samsung mobile device". So i uninstalled that driver, put it back into AP fastboot and plugged it in. now under "other devices" i have "Fastboot ASANTI_C S" and it needs to be updated. i want to make sure i update it with the correct file. if anyone knows where i can find this on my computer or the internet please let me know. it would be greatly appreciated.
Click to expand...
Click to collapse
Did you try the Moto Device Manager? That's all I recall needing for Windows.
wbbjason said:
Thanks for the help guys. So problem still unsolved but today I went back at it and noticed that the phone was showing up in device manager as "Samsung mobile device". So i uninstalled that driver, put it back into AP fastboot and plugged it in. now under "other devices" i have "Fastboot ASANTI_C S" and it needs to be updated. i want to make sure i update it with the correct file. if anyone knows where i can find this on my computer or the internet please let me know. it would be greatly appreciated.
Click to expand...
Click to collapse
If you haven't already, you can try putting the USB cable into a different USB slot. I didn't notice it before, but I had mine plugged in to a USB 3.0 slot. It worked for ADB, FASTBOOT and file transfers, so I thought nothing of it. Still the damn thing wouldn't be recognized in RSD Lite 6.5
I just switched it over to another usb slot(USB 2.0 port) and voila, works like a champ every time. You've probably already done this, but I thought I would just throw it out there.
arrrghhh said:
Did you try the Moto Device Manager? That's all I recall needing for Windows.
Click to expand...
Click to collapse
KoolBurnX8 said:
If you haven't already, you can try putting the USB cable into a different USB slot. I didn't notice it before, but I had mine plugged in to a USB 3.0 slot. It worked for ADB, FASTBOOT and file transfers, so I thought nothing of it. Still the damn thing wouldn't be recognized in RSD Lite 6.5
I just switched it over to another usb slot(USB 2.0 port) and voila, works like a champ every time. You've probably already done this, but I thought I would just throw it out there.
Click to expand...
Click to collapse
yeah i tried the device manager. uninstalled and reinstalled. and changing ports doesnt work. i have motorola drivers. like ADB QC Diag that i can install but im not sure its the right one. does anyone know the name of the driver that shows up in device manager when you plug in a photon q in AP fastboot?
wbbjason said:
yeah i tried the device manager. uninstalled and reinstalled. and changing ports doesnt work. i have motorola drivers. like ADB QC Diag that i can install but im not sure its the right one. does anyone know the name of the driver that shows up in device manager when you plug in a photon q in AP fastboot?
Click to expand...
Click to collapse
Not sure if this will help you, but here's a screenshot of Device Manager when I rebooted to bootloader (fastboot) mode.
{
"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"
}
When I was having trouble, i've also read that RSDLite can be picky about the USB cable you use sometimes. If you have extras or have the one your phone came with, you might wanna give it a shot.
Related
SOLVED - you have got to be kidding me though. i had 2 faulty cables, one was my original cable and another a brand new one. so i used one of my friends and it worked fine. I HATE ELECTRONICS
my drivers dont work and my phone is stuck in boot loop and i CANNOT get into recovery
i just need someone that can get me back to stock :[
PM ME if you can help
heres my problem thread
http://forum.xda-developers.com/showthread.php?t=1353314
VIDEO showing boot loop (same thing if i try 3 button recovery)
http://www.youtube.com/watch?v=n3ALNj5q-hY
VIDEO showing download mode + odin , USB NOT RECOGNIZED usb error 43 device has stopped working
http://www.youtube.com/watch?v=D4CnRnecNrQ
i have deleted all drives so someone can help me fresh
rsx19 said:
my drivers dont work and my phone is stuck in boot loop and i CANNOT get into recovery
i just need someone that can get me back to stock :[
Click to expand...
Click to collapse
Restart your computer and then pull the battery out of your phone and put it back in. Now on your computer open Odin and then hold vol+ and vol- and plug in the USB cord this will put you in downlaod mode. And use Odin to get you back to a stock rom
Currently Fusionized
Wdustin1 said:
Restart your computer and then pull the battery out of your phone and put it back in. Now on your computer open Odin and then hold vol+ and vol- and plug in the USB cord this will put you in downlaod mode. And use Odin to get you back to a stock rom
Currently Fusionized
Click to expand...
Click to collapse
ive had this problem for a week now, it doesnt seem to be that simple. installing new drivers doesnt work, using different usb ports dont work, going into download mode doesnt work, thats why i need someone to try it for me cause i just cant figure it out
there has to be somebody!
Have you read this post ?
studacris said:
Have you read this post ?
Click to expand...
Click to collapse
not related to my post. can anyone help me on teamviewer?
bump + op update
not sure what someone would be able to do remotely to help you with a device you hold in your hand......why havent you tried Heimdall method? ODIN sucks.
Pirateghost said:
not sure what someone would be able to do remotely to help you with a device you hold in your hand......why havent you tried Heimdall method? ODIN sucks.
Click to expand...
Click to collapse
doesnt work either cause my phone isnt recognized by the computer at all so ANYTHING usb based doesnt work and i cant get into recovery so that doesnt work either, i mean i have to be doing something wrong right? the phone cant be dead
Heimdall uses it's own driver so Jake you install that and uninstall all the others, SO that may help with the recognition issue, as the stock closed source driver can be a douche sometimes...like in your case.
studacris said:
Heimdall uses it's own driver so Jake you install that and uninstall all the others, SO that may help with the recognition issue, as the stock closed source driver can be a douche sometimes...like in your case.
Click to expand...
Click to collapse
there is nothing in the drop down menus
{
"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"
}
bump, would be great if someone could help me tomorrow night so i can use my phone in a presentation
rsx19 said:
bump, would be great if someone could help me tomorrow night so i can use my phone in a presentation
Click to expand...
Click to collapse
I've seen that error code 43 on my machine when there's a larger USB issue. Usually two things will correct that - a reboot and switching USB ports.
I would also suggest (if you haven't already) uninstalling all of the drivers you have installed - Samsung- or Heimdall-related, then reboot, then do the Heimdall again.
jmtheiss said:
I've seen that error code 43 on my machine when there's a larger USB issue. Usually two things will correct that - a reboot and switching USB ports.
I would also suggest (if you haven't already) uninstalling all of the drivers you have installed - Samsung- or Heimdall-related, then reboot, then do the Heimdall again.
Click to expand...
Click to collapse
ive tried reinstating and tried all 4 of my laptop ports and all 12 or 14 of my desktop ports. ive tried installing all the different drivers users gave me but that never helped. and as you can eee i cant even install the heimdall drivers
either both my desktop and laptop have something wrong with them or its a user error, thats why i want someone else to help me through team viewer, this thread is moving to slow for me to get anything done
I'll ask the obvious question, just to make sure - Have you tried a different cable?
jmtheiss said:
I'll ask the obvious question, just to make sure - Have you tried a different cable?
Click to expand...
Click to collapse
yup yup that i have done
Ok, I took a quick look at the videos in the OP. Two things I noticed:
- You have the phone plugged in prior to putting it into download mode. It's possible you're just keeping the plug in after putting it there (couldn't see in the video). Try putting the phone in download mode, unhook the cable, then rebooting the computer (leave the phone in DL mode), then hook it up again.
- I saw that you have an ICS build. Do any button combinations get you to recovery (V+/V-/Power, V+/Power)? If so, you might be able to flash another rom.
- You may also want to look for AdamOutler's One-click Unbrick. That might be of some use in your situation.
jmtheiss said:
Ok, I took a quick look at the videos in the OP. Two things I noticed:
- You have the phone plugged in prior to putting it into download mode. It's possible you're just keeping the plug in after putting it there (couldn't see in the video). Try putting the phone in download mode, unhook the cable, then rebooting the computer (leave the phone in DL mode), then hook it up again.
- I saw that you have an ICS build. Do any button combinations get you to recovery (V+/V-/Power, V+/Power)? If so, you might be able to flash another rom.
- You may also want to look for AdamOutler's One-click Unbrick. That might be of some use in your situation.
Click to expand...
Click to collapse
at school writing 2 papers so ill have to try these when i get home
i put the phone in download mode with vol + - while plugging in the cord but ill try the others
no none get me into recovery,
could you link me that one?
rsx19 said:
at school writing 2 papers so ill have to try these when i get home
i put the phone in download mode with vol + - while plugging in the cord but ill try the others
no none get me into recovery,
could you link me that one?
Click to expand...
Click to collapse
Ok, I looked a little more at the one click unbrick, and since you can get to download mode, it doesn't look like the right solution. So.. nevermind that one.
As far as removing the drivers, it's something of a two-step process.
Step one is to plug the phone in, let Windows see it (even if incorrectly), and then go to device manager. From there, find the phone, and uninstall it/remove drivers. Then unplug the phone.
Step two is to go to "Programs and Features" and remove any android/samsung drivers that show up there.
Once you've done that, check to make sure any folders that drivers would have been unpacked into (mine is in C:\usb_driver) has all the Samsung or Heimdall drivers removed (BE CAREFUL WHILE DOING THIS - ONLY REMOVE SAMSUNG/HEIMDALL DRIVERS IF YOU'RE 100% CERTAIN).
Then, reboot the computer, re-run Heimdall to get zadig.exe to do its thing, then connect the phone.
Also, have you considered dual-booting (or using a USB live drive) of Ubuntu? Heimdall seems to be a little happier in Linux, but you'll just need to make sure that Java installs with it.
There's also a really slim chance that if you hook the phone up in download mode, ADB might detect it enough to where you can give the "adb reboot recovery" command.
jmtheiss said:
Ok, I looked a little more at the one click unbrick, and since you can get to download mode, it doesn't look like the right solution. So.. nevermind that one.
As far as removing the drivers, it's something of a two-step process.
Step one is to plug the phone in, let Windows see it (even if incorrectly), and then go to device manager. From there, find the phone, and uninstall it/remove drivers. Then unplug the phone.
Step two is to go to "Programs and Features" and remove any android/samsung drivers that show up there.
Once you've done that, check to make sure any folders that drivers would have been unpacked into (mine is in C:\usb_driver) has all the Samsung or Heimdall drivers removed (BE CAREFUL WHILE DOING THIS - ONLY REMOVE SAMSUNG/HEIMDALL DRIVERS IF YOU'RE 100% CERTAIN).
Then, reboot the computer, re-run Heimdall to get zadig.exe to do its thing, then connect the phone.
Also, have you considered dual-booting (or using a USB live drive) of Ubuntu? Heimdall seems to be a little happier in Linux, but you'll just need to make sure that Java installs with it.
There's also a really slim chance that if you hook the phone up in download mode, ADB might detect it enough to where you can give the "adb reboot recovery" command.
Click to expand...
Click to collapse
ill also try ubuntu since i do have it on a usb drive. my paper isnt getting written well..ll sigh
I will be straightforward:
I bought an used OPO, I booted it up, configured the phone, took a photo and then decided to reboot it (turn off and then turn on), then my device simply hard bricked.
1. I already tried turning it on, the device does nothing (no vibration).
2. I already tried using Power + Vol Up and Power + Vol Down, nothing happens (no vibration).
3. Windows recognizes the device as "QHSUSB_BULK", I already tried installing the drivers and using ColorOS flashing tool from here http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732 , the device IS RECOGNIZED by the tool, but when I start flashing, it starts a loop when trying to flash the "8974_msimage.mbn" file (the progress bar goes until the end and then the process repeat in the same file).
Yes, the device has the bootloader unlocked, because the previous owner flashed a custom ROM, custom kernel and SuperSU.
No, the device isn't recognized by adb.
No, the device isn't recognized by fastboot.
I already tried searching on Google for this issue, everyone who had this issue never replied saying that they fixed the issue...
I never had any kind of soft/hard brick on my Moto G 2014 (and I flashed custom ROMs constantly on it)... so... can someone help me? Thanks!
I'm also willing to give 5$ on PayPal to someone who can fix this issue.
Also, if I try to use the ColorOS flashing tool, the device disconnects in the middle of the process, causing the infinite flash loop.
First, if you have a computer which installed Windows XP, just flash the ROM with COLOROS tool.
Second,if you a using Windows7 or later,,give me a photo of what the COLOROS tool showed.
Thanks for forgiving my poor English
sino1641 said:
First, if you have a computer which installed Windows XP, just flash the ROM with COLOROS tool.
Second,if you a using Windows7 or later,,give me a photo of what the COLOROS tool showed.
Thanks for forgiving my poor English
Click to expand...
Click to collapse
Nah, your english is fine, I could understand what you are saying.
{
"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"
}
After I clicked "Start"
Then the "device plugged in" sound plays and the process repeats...
It keeps doing this:
(If you can't view the images, click here:
http://lori.mrpowergamerbr.com/sharex/Msm8974DownloadTool_2016-07-22_10-39-42.png
http://lori.mrpowergamerbr.com/sharex/Msm8974DownloadTool_2016-07-22_10-40-18.png
http://lori.mrpowergamerbr.com/sharex/2016-07-22_10-41-05.gif
)
Morning,my friend.
I tried to brick my OPO for testing.
Here's the solution.
First,open Device Manager and checked this(dont know how to speak in English):
Second, open COLOROS tool,click start and it will show the situation like what happened to you.
NOW,check Device Manager again.
Has three ways.
1.shows 9006 and MMC storage.COLOROS tool wil continue later.
2.shows QHSUSB_BULK with a yellow ! before,means no driver.
3.shows unknown device,means not enough elec.
You should be the second way.
Third,Disable Signed Driver Enforcement in Windows 7 or later.
My laptop company's suggestion:
http://acer.custhelp.com/app/answer...windows-10:-disable-signed-driver-enforcement
After that, reinstall the bricked driver and everything will be in way 1.
At last,wait for the imgs downloading,unplug microUSB,press power and reboot twice,then you can unlock bootloader and do what you want.
sino1641 said:
Morning,my friend.
I tried to brick my OPO for testing.
Here's the solution.
First,open Device Manager and checked this(dont know how to speak in English):
Second, open COLOROS tool,click start and it will show the situation like what happened to you.
NOW,check Device Manager again.
Has three ways.
1.shows 9006 and MMC storage.COLOROS tool wil continue later.
2.shows QHSUSB_BULK with a yellow ! before,means no driver.
3.shows unknown device,means not enough elec.
You should be the second way.
Third,Disable Signed Driver Enforcement in Windows 7 or later.
My laptop company's suggestion:
http://acer.custhelp.com/app/answer...windows-10:-disable-signed-driver-enforcement
After that, reinstall the bricked driver and everything will be in way 1.
At last,wait for the imgs downloading,unplug microUSB,press power and reboot twice,then you can unlock bootloader and do what you want.
Click to expand...
Click to collapse
Thanks for replying!
Sadly, your suggestion didn't work, I plugged in the OPO, opened Msm8974DownloadTool.exe and clicked "Start", closed drivers manager and reopened it and nothing changed (It was like your first screenshot)
EDIT: And yes, I'm on Test Mode + Allow Unsigned Drivers
MrPowerGamerBR said:
Thanks for replying!
Sadly, your suggestion didn't work, I plugged in the OPO, opened Msm8974DownloadTool.exe and clicked "Start", closed drivers manager and reopened it and nothing changed (It was like your first screenshot)
EDIT: And yes, I'm on Test Mode + Allow Unsigned Drivers
Click to expand...
Click to collapse
Open Device Manager.
Press Power &Vol Up for about 10 seconds.
See if it will change between 9008 and 9006.
I have same thing did it work
I am just wondering if u managed to fix it.
I had the exact same issue. To stop the device from disconnecting, I needed to remove all existing drivers, let the phone charge, plug it into the PC. Hold volume up + power until the PC recognises it. Then I used the color OS flashing tool.
I had to run it as administrator, and it worked fine on Windows 10, without anything extra. However remember you'll lose all your stuff. Lucky for me I had a backup of my entire phone on my PC when I switched file system to F2FS.
This issue in itself has really baffled me. It happened to me when flashing sultans rom, and the phone completely bricked. However I'm using the rom now after fully recovering the device... I guess it's just down to bad luck?
mark1320 said:
I am just wondering if u managed to fix it.
Click to expand...
Click to collapse
Nope, never fixed it, I don't even have the device anymore (now rocking a Moto G Turbo)
mark1320 said:
I am just wondering if u managed to fix it.
Click to expand...
Click to collapse
Don't use "msm8974-download-manager" use qfil to recover the phone. Worked for me.
http://www.androidbrick.com/ultimate-qualcomm-snapdragon-unbrick-guide-snapdragons-are-unbrickable-qhsusb_dload_qpst_qfil/
Download 2012 qhs diagnostic driver and use xp machine.It will work just fine.
install a fresh windows either x32/x64 winxp/win 7 extract color OS and install the correct drivers
Hi
Please help! I have downloaded everything in this link:
https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691
It contains "guacamole_21_O.07_190512_repack" and "L2 drivers"
I have followed the mega unbrick guide:
https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-mega-unbrick-guide-hard-bricked-t3934659
So far the pc can find "Qualcomm HS-USB QDLoader 9008 (COM7).
But it stuck when I use MSM tool to unbrick it!
It keeps Param Preloading.
Please, any help will be really much appreciated!
I had a similar issue at first. Verify the drivers are good to go (it shows up as the right device in device manager) aside from that, try to boot into recovery or something to shut the phone down. Now hold down both volume buttons at the same time - followed by the power button. Immediately plug the phone in. Took me a couple tries but eventually you will succeed.
gh279760559 said:
Hi
Please help! I have downloaded everything in this link:
https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691
It contains "guacamole_21_O.07_190512_repack" and "L2 drivers"
I have followed the mega unbrick guide:
https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-mega-unbrick-guide-hard-bricked-t3934659
So far the pc can find "Qualcomm HS-USB QDLoader 9008 (COM7).
But it stuck when I use MSM tool to unbrick it!
It keeps Param Preloading..
Please, any help will be really much appreciated!
Click to expand...
Click to collapse
Try different drivers. When I ran into that issue I found different drivers on another website which ended up working.
thanks for your help. I have searched a lot and it seems it is the newest so far.
atrix4gtransamgta said:
I had a similar issue at first. Verify the drivers are good to go (it shows up as the right device in device manager) aside from that, try to boot into recovery or something to shut the phone down. Now hold down both volume buttons at the same time - followed by the power button. Immediately plug the phone in. Took me a couple tries but eventually you will succeed.
Click to expand...
Click to collapse
Thanks for your reply. I just did exactly as the instruction suggested. The device name in the manager was showed correctly. But still, the msm tool stucked at the param preprocessing stage.
Try installing Google's Android USB driver from Android studio, then try using the msmtool
Sent from my GM1915 using Tapatalk
D31337 said:
Try installing Google's Android USB driver from Android studio, then try using the msmtool
Sent from my GM1915 using Tapatalk
Click to expand...
Click to collapse
Hi, I think it is not the adb side problem. Because when I use my laptop to connect to another phone, it works fine. Some one suggested the oneplus driver is not the latest. Actually I have checked the forum. It seems it is the newest one AFAIK.
Try to use the oneplus red USB cable if you arent already
Vanhoud said:
Try to use the oneplus red USB cable if you arent already
Click to expand...
Click to collapse
thanks, well, do you mean the oneplus driver? I have installed it already.
this took me a couple of hours to figure out so hopefully, it works for you all. I got a program from the xda forums called TOOL ALL IN ONE which can put your phone into edl mode at the click of a button. I also went to the device manager to make sure the phone was showing up as Qualcomm and not the QLK_ USB thing. if it shows up for you you have to download the drivers. I updated the drivers through the windows update > view optional updates > Drivers and install the Qualcomm one and restart pc. Then plug your phone in have the TOOL ALL IN ONE put it in edl mode then quickly open msm as administrator and uncheck Sha256 and press start. I think my Qualcomm driver was out of date and that might have been what caused me to have the param preload issue.
CookieMonster23 said:
this took me a couple of hours to figure out so hopefully, it works for you all. I got a program from the xda forums called TOOL ALL IN ONE which can put your phone into edl mode at the click of a button. I also went to the device manager to make sure the phone was showing up as Qualcomm and not the QLK_ USB thing. if it shows up for you you have to download the drivers. I updated the drivers through the windows update > view optional updates > Drivers and install the Qualcomm one and restart pc. Then plug your phone in have the TOOL ALL IN ONE put it in edl mode then quickly open msm as administrator and uncheck Sha256 and press start. I think my Qualcomm driver was out of date and that might have been what caused me to have the param preload issue.
Click to expand...
Click to collapse
Thanks but this does not work if you are stuck in Fastboot mode.
Finally got it to work. Turns out the vast majority of problems people encounter while trying the MSM Tool is with the Qualcomm drivers.
I found the correct (and latest version) drivers.
Just unzip the CAB file, uninstall any old Qualcomm drivers you have tried, and then install this one. It should work!
Let me know if you need any assistance.
Rayan said:
Finally got it to work. Turns out the vast majority of problems people encounter while trying the MSM Tool is with the Qualcomm drivers.
I found the correct (and latest version) drivers.
Just unzip the CAB file, uninstall any old Qualcomm drivers you have tried, and then install this one. It should work!
Let me know if you need any assistance.
Click to expand...
Click to collapse
Tried but not working. Tried 10 different drives, 3 different laptops with all the USB 2.0 ports but still no luck. Don't know what's the issue and why am keep getting stuck at param preload. What should I do?
umargillen said:
Tried but not working. Tried 10 different drives, 3 different laptops with all the USB 2.0 ports but still no luck. Don't know what's the issue and why am keep getting stuck at param preload. What should I do?
Click to expand...
Click to collapse
Are you making sure you are uninstalling any other drivers? You should only have installed the correct version.
Rayan said:
Finally got it to work. Turns out the vast majority of problems people encounter while trying the MSM Tool is with the Qualcomm drivers.
I found the correct (and latest version) drivers.
Just unzip the CAB file, uninstall any old Qualcomm drivers you have tried, and then install this one. It should work!
Let me know if you need any assistance.
Click to expand...
Click to collapse
It's work, thank you
Rayan said:
Are you making sure you are uninstalling any other drivers? You should only have installed the correct version.
Click to expand...
Click to collapse
Yup. First uninstalled the other driver and installed this one again. Will give it one more go and share the outcome. But its very strange to me how confusing all this is. Can't get my head around why on Earth its not working. Am literally sick of not getting update. Badly want to flash the international rom to my Sprint OnePlus.
umargillen said:
Yup. First uninstalled the other driver and installed this one again. Will give it one more go and share the outcome. But its very strange to me how confusing all this is. Can't get my head around why on Earth its not working. Am literally sick of not getting update. Badly want to flash the international rom to my Sprint OnePlus.
Click to expand...
Click to collapse
Remember to reboot between uninstalling and reinstalling drivers. Also try to use the OEM cable that came with the OnePlus.
Rayan said:
Finally got it to work. Turns out the vast majority of problems people encounter while trying the MSM Tool is with the Qualcomm drivers.
I found the correct (and latest version) drivers.
Just unzip the CAB file, uninstall any old Qualcomm drivers you have tried, and then install this one. It should work!
Let me know if you need any assistance.
Click to expand...
Click to collapse
Thanks a lot! You saved my night 11pm here ^^.
{
"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"
}
Awesomeness
Rayan said:
Finally got it to work. Turns out the vast majority of problems people encounter while trying the MSM Tool is with the Qualcomm drivers.
I found the correct (and latest version) drivers.
Just unzip the CAB file, uninstall any old Qualcomm drivers you have tried, and then install this one. It should work!
Let me know if you need any assistance.
Click to expand...
Click to collapse
thank you! this really work.
I've been running the crDroid OOS 10 OB3 ROM since I got my phone two weeks ago and everything was fine and I updated to OB4 today. Well, after I tried changing system ui themeing my phone stopped displaying any system ui at all so I tried to restore my nandroid backup. My nandroid backup took 4 hours then when it got to bluetooth my battery was dying so I had to stop it.
I rebooted into TWRP and tried to clean flash the rom but it gave me errors about mounting the data partition so I tried changing slots.
Well after I changed slots I am stuck in fastboot mode and can't get back to TWRP and adb wont recognize my phone. There's no bootloader or baseband version displayed on fastboot and the product name/variant is msmnile/SDM UFS, my phone is still unlocked if it matters. Someone in the ROM telegram suggested I try the MSM tool but my phone doesn't seem to want to boot into Qualcomm mode and I'm worried that might be a big issue.
Hi!
I really don't know if this helps because you might have already tried it, but I had a similar problem where the normal fastboot mode didnt work and I had no Recovery. Someone suggested, that I should hold Volume Up, Volume down and the Power button all at the same time and from there I was able to revive the phone with the All-In-One Tool...
I quickly looked up the Qualcomm Mode and MSM-Tool you mentioned but I'm still not sure if that is what I just described, so Im posting this just to make sure you tried it because it was a really easy fix when I thought I bricked my phone
Sorry if you already did it, anyway Good Luck!
David
DvdStrbl said:
Hi!
I really don't know if this helps because you might have already tried it, but I had a similar problem where the normal fastboot mode didnt work and I had no Recovery. Someone suggested, that I should hold Volume Up, Volume down and the Power button all at the same time and from there I was able to revive the phone with the All-In-One Tool...
I quickly looked up the Qualcomm Mode and MSM-Tool you mentioned but I'm still not sure if that is what I just described, so Im posting this just to make sure you tried it because it was a really easy fix when I thought I bricked my phone
Sorry if you already did it, anyway Good Luck!
David
Click to expand...
Click to collapse
Well see the issue is I'm trying to get All in One to recognize my phone but it won't seem to boot into EDL mode. I installed the Qualcomm USB drivers but it's still not showing my phone. When I use the key combo suggested to boot into EDL mode my phone does refresh in device manager giving me the qualcomm device so I assume this is download mode just not displaying the text anymore. If i try the key combo with my phone unplugged it takes awhile but eventually goes into fastboot.
In this case I can't help you, i googled EDL, it is what I meant and it was all I got :-/
Wish you good luck
If your bootloader is unlocked try to flash the fastboot rom from fastboot.
https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
Bradl79 said:
If your bootloader is unlocked try to flash the fastboot rom from fastboot.
https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
Click to expand...
Click to collapse
When I try flashing anything at fastboot it just hangs waiting
viralhysteria said:
I've been running the crDroid OOS 10 OB3 ROM since I got my phone two weeks ago and everything was fine and I updated to OB4 today. Well, after I tried changing system ui themeing my phone stopped displaying any system ui at all so I tried to restore my nandroid backup. My nandroid backup took 4 hours then when it got to bluetooth my battery was dying so I had to stop it.
I rebooted into TWRP and tried to clean flash the rom but it gave me errors about mounting the data partition so I tried changing slots.
Well after I changed slots I am stuck in fastboot mode and can't get back to TWRP and adb wont recognize my phone. There's no bootloader or baseband version displayed on fastboot and the product name/variant is msmnile/SDM UFS, my phone is still unlocked if it matters. Someone in the ROM telegram suggested I try the MSM tool but my phone doesn't seem to want to boot into Qualcomm mode and I'm worried that might be a big issue.
Click to expand...
Click to collapse
what the problem u are facing while flashing from msm tools?
If you haven't fixed your phone yet just use MSMtool it will fix it, this phones essentially unbrickable.
whoamanwtf said:
If you haven't fixed your phone yet just use MSMtool it will fix it, this phones essentially unbrickable.
Click to expand...
Click to collapse
I installed the qualcomm drivers and it showed up in MSM tool and gave me success after 6 seconds but nothing else happened so I unplugged my phone now it says device descriptor failed when I try to go into qualcomm mode
If i uninstall the drivers and try again same thing and trying to use the qualcomm driver files tells me my driver is already up to date
Well you need to hit start once it's connected. https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691 follow the instructions there with the phone being unplugged and powered off open msm hold volumes while not hitting power at all and wait then plug into the computer.
viralhysteria said:
I installed the qualcomm drivers and it showed up in MSM tool and gave me success after 6 seconds but nothing else happened so I unplugged my phone now it says device descriptor failed when I try to go into qualcomm mode
If i uninstall the drivers and try again same thing and trying to use the qualcomm driver files tells me my driver is already up to date
Click to expand...
Click to collapse
During Installing drivers again choose the option (something of) search from internet. And let the file be downloaded and install. Trust me this method works. I too had same problem
whoamanwtf said:
Well you need to hit start once it's connected. https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691 follow the instructions there with the phone being unplugged and powered off open msm hold volumes while not hitting power at all and wait then plug into the computer.
Click to expand...
Click to collapse
Okay I got the descriptor issue to stop and MSM is detecting the phone again but its still not booting to anything when I run the tool like the guide said it should. I do upgrade mode right?
viralhysteria said:
I installed the qualcomm drivers and it showed up in MSM tool and gave me success after 6 seconds but nothing else happened so I unplugged my phone now it says device descriptor failed when I try to go into qualcomm mode
If i uninstall the drivers and try again same thing and trying to use the qualcomm driver files tells me my driver is already up to date
Click to expand...
Click to collapse
viralhysteria said:
Okay I got the descriptor issue to stop and MSM is detecting the phone again but its still not booting to anything when I run the tool like the guide said it should. I do upgrade mode right?
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-7-pro/how-to/op7pro-collection-unbrick-tools-t3956595
I meant to send that one, follow those instructions and you'll be good. It's Android 9 but that doesn't matter, you can update from there once your phones working again.
whoamanwtf said:
https://forum.xda-developers.com/oneplus-7-pro/how-to/op7pro-collection-unbrick-tools-t3956595
I meant to send that one, follow those instructions and you'll be good.
Click to expand...
Click to collapse
It says to wait about 5 minutes after starting but I get stuck at this
{
"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"
}
Where did you get the files you're using? Maybe download one from my link, they're the only ones I've personally used and can say for sure they work
whoamanwtf said:
Where did you get the files you're using? Maybe download one from my link, they're the only ones I've personally used and can say for sure they work
Click to expand...
Click to collapse
Your file does the same thing
The connection status switches to N/A but if i stop it and enum it still detects the phone
I used the drivers provided in your link and it still doesnt seem to work
that status bar at the bottom says Running: Upgrade though but thats just an indicator of the job task, no?
viralhysteria said:
Your file does the same thing
The connection status switches to N/A but if i stop it and enum it still detects the phone
I used the drivers provided in your link and it still doesnt seem to work
that status bar at the bottom says Running: Upgrade though but thats just an indicator of the job task, no?
Click to expand...
Click to collapse
Send a larger screen grab of the MSMtool running, I don't recognize what you sent.
whoamanwtf said:
Send a larger screen grab of the MSMtool running, I don't recognize what you sent.
Click to expand...
Click to collapse
So it sounds dumb but try rebooting your computer and switching USB ports then trying again.
whoamanwtf said:
So it sounds dumb but try rebooting your computer and switching USB ports then trying again.
Click to expand...
Click to collapse
Same thing it just assigned a new COM port
My phone's power button is broken. I accidentally went into recovery mode. My computer does not see my phone. How can I get rid of it? When does it run out of charge?
Samsung j6+
karmastir said:
My phone's power button is broken. I accidentally went into recovery mode. My computer does not see my phone. How can I get rid of it? When does it run out of charge?
Samsung j6+
Click to expand...
Click to collapse
Do you have ADB? is so do
Code:
adb reboot
karmastir said:
My phone's power button is broken. I accidentally went into recovery mode. My computer does not see my phone. How can I get rid of it? When does it run out of charge?
Samsung j6+
Click to expand...
Click to collapse
are you using windows? if so have you installed the usb driver? In device manager when you add a device, it will show as an unknown or fastboot device then you just need to add the driver to be able to send probably a fastboot request.
Code:
fastboot reboot
Spoiler: DRIVER STEPS IF YOU NEED
{
"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"
}
All you need is the usb driver, you can get from android studio, your manufacturer, or you can try this one from nvidia for the shield, I use it on my phone and it works fine to be able to send fastboot requests
Shield Drivers.zip
drive.google.com
jenneh said:
are you using windows? if so have you installed the usb driver? In device manager when you add a device, it will show as an unknown or fastboot device then you just need to add the driver to be able to send probably a fastboot request.
Code:
fastboot reboot
Spoiler: DRIVER STEPS IF YOU NEED
View attachment 5756167View attachment 5756169View attachment 5756171View attachment 5756173View attachment 5756175
All you need is the usb driver, you can get from android studio, your manufacturer, or you can try this one from nvidia for the shield, I use it on my phone and it works fine to be able to send fastboot requests
Shield Drivers.zip
drive.google.com
Click to expand...
Click to collapse
Does ADB work too?
Arealhooman said:
Does ADB work too?
Click to expand...
Click to collapse
Not in this case bc the user's phone is stuck in recovery, adb is an option we can access only when the device is posted into the actual system, and we have enabled developer options, then usb or wireless debugging, then lastly adb connect. Fastboot skips everything and lets us run commands when the device is not completely online or loaded into the system
jenneh said:
Not in this case bc the user's phone is stuck in recovery, adb is an option we can access only when the device is posted into the actual system, and we have enabled developer options, then usb or wireless debugging, then lastly adb connect. Fastboot skips everything and lets us run commands when the device is not completely online or loaded into the system
Click to expand...
Click to collapse
Ah, i get it now, but doesnt samsung not have fastboot
Arealhooman said:
Ah, i get it now, but doesnt samsung not have fastboot
Click to expand...
Click to collapse
I honestly don't know, haha. I just saw this post, remembered myself in the same boat last year for a different device, and wanted to share what worked for me.
jenneh said:
I honestly don't know, haha. I just saw this post, remembered myself in the same boat last year for a different device, and wanted to share what worked for me.
Click to expand...
Click to collapse
Well, it was a good idea, but I do not think samsung supports fastboot
Arealhooman said:
Well, it was a good idea, but I do not think samsung supports fastboot
Click to expand...
Click to collapse
That's Super interesting knowledge. Thank you for sharing that with me. All the tricky ways samsung likes to use to keep things "safe". Almost makes me want to get one to play cat and mouse too but I already have an awful phone with it's own dastardly tricks. A "Nokia" mtk device with a Preloader instead of a bootloader. A "1 second handshake process" to be able to access or communicate with the preloader, no recovery, no bootloader menu, no fastboot oem commands. Haha. Terrible!
jenneh said:
That's Super interesting knowledge. Thank you for sharing that with me. All the tricky ways samsung likes to use to keep things "safe". Almost makes me want to get one to play cat and mouse too but I already have an awful phone with it's own dastardly tricks. A "Nokia" mtk device with a Preloader instead of a bootloader. A "1 second handshake process" to be able to access or communicate with the preloader, no recovery, no bootloader menu, no fastboot oem commands. Haha. Terrible!
Click to expand...
Click to collapse
I don’t even know what a preloader is could we continut talking and you can explain in dms? And a ”1 second handshake process”….
Arealhooman said:
I don’t even know what a preloader is could we continut talking and you can explain in dms? And a ”1 second handshake process”….
Click to expand...
Click to collapse
Spoiler: SHOW
Since I haven't messed with a samsung phone in almost a decade, I may be wrong, but if I had to guess, I would think that Samsungs come with a Preloader too, which is why there is a need for an external program like Odin.
But what a preloader is, is a layer below the Bootloader, it is what allows certain MTK or Qualcom devices to even be able to access the Bootloader.
I am a Nooby Cake and don't know much about anything, I just read a lot but if you are interested in what I have already read I started writing down the links for preloader knowledge on the last comment on this page of this thread and it continues into the next with nerdy rambling bs.
https://forum.xda-developers.com/t/mapping-out-the-g20s-internals.4416907/page-2
You can pm any questions just know I don't know much more than what I share on my threads haha. But I try to learn more everyday
karmastir said:
My phone's power button is broken. I accidentally went into recovery mode. My computer does not see my phone. How can I get rid of it? When does it run out of charge?
Samsung j6+
Click to expand...
Click to collapse
Go to a service centre. Repair or replace the power button. That's the best thing you can do.
ADB or FASTBOOT won't work at that situation.
.
Goddamn_srilankan said:
Go to a service centre. Repair or replace the power button. That's the best thing you can do.
ADB or FASTBOOT won't work at that situation.
Click to expand...
Click to collapse
You are telling the truth. Unfortunately, the charge does not end. lol
The first thing that came to my mind was adb, but the computer definitely does not see the device.
If I had a chance to reboot. Maybe it can see it, but it doesn't charge or I can't reboot with any key combination.
I guess the only thing to do is to repair the power button.
thanks everyone <3
karmastir said:
The first thing that came to my mind was adb, but the computer definitely does not see the device.
If I had a chance to reboot. Maybe it can see it, but it doesn't charge or I can't reboot with any key combination.
I guess the only thing to do is to repair the power button.
thanks everyone <3
Click to expand...
Click to collapse
<3