I made this post to hopefully help me help you help us.
My Razer Phone is currently unable receive any commands while in fastboot mode/bootloader.
This seems to be a fairly common problem that I see some people are running into without having any concrete solution. I have tried numerous suggestions and then some. Therefore, I want to provide as much information and background to the problem to try and help anyone with more experience that is willing to get to the bottom of this.
So for some background, I successfully rooted my Razer Phone with help from both of these threads:
Rooting Android 9 December Update With Magisk (No TWRP)(Global)
and
[TWRP + MAGISK] FULLPROOF Guide for all Razers! Wifi Fix!
I primarily used the first thread listed to achieve root.
The phone is currently on the stock ROM, rooted with magisk installed. I do not have TWRP installed. It works perfectly fine under normal use.
I am trying to revert to stock and relock my bootloader using Razer's guide HERE. When using the 'flash_all' script that the guide references, the script fails, because the phone cannot receive fastboot commands.
I followed Razer's installation guide PDF to install the adb/fastboot drivers.
I have also tried using ClockworkMod's Universal ADB Driver.
EDIT: I also tried using [Tool] Latest ADB Fastboot and USB Driver installer tool for Windows
The phone is currently on the stock ROM, rooted with magisk installed. I do not have TWRP installed. It works perfectly fine under normal use.
I'm pretty sure I have installed the adb drivers correctly. I can use adb commands while android is running. It's listed when using the "adb devices" command. It successfully restarts and enters the bootloader after typing "adb reboot bootloader", but after typing "fastboot device", it only outputs "< waiting for any device >" and waits. I have also tried using the command "fastboot -i 0x1532 devices" as suggested in a related thread, but this just returns "fastboot.exe: unknown option -- i" and fails.
I have also tried selecting "Android ADB Interface", as well as "Android Bootloader Interface" when installing the google usb driver. I even tried using the third option, no luck.
Now here's why I say that I'm pretty sure that I have the drivers installed correctly:
{
"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"
}
This is what is displayed in Device Manager when the phone is in fastboot mode and connected to my PC after installing the drivers.
It displays normal when android is running with or without USB debugging enabled.
I have tried this on a few Windows 10 PCs and get the same result. So, I wouldn't be able to tell if this is a Windows problem or if it is my phone:
This is what my bootloader shows. Besides the serial number I blocked out, notice how some data is missing? Could this be the problem?
I'm curious to know the method of root everyone else having this problem had used and whether their bootloader looks like this.
I understand the community for this phone isn't as active as it used to be.
So, thank you to anyone in advance for the help and your time.
This devices is tricky for sure. Everything worked just fine when I unlocked bootloader a few months back, but now when I wanted to flash LOS I just couldn't get anything working with drivers.
Then I stumbled upon this [Tool] Latest ADB Fastboot and USB Driver installer tool for Windows and it actually installed the correct driver.
Adb & fastboot all works fine after that.
tys0n said:
This devices is tricky for sure. Everything worked just fine when I unlocked bootloader a few months back, but now when I wanted to flash LOS I just couldn't get anything working with drivers.
Then I stumbled upon this [Tool] Latest ADB Fastboot and USB Driver installer tool for Windows and it actually installed the correct driver.
Adb & fastboot all works fine after that.
Click to expand...
Click to collapse
I forgot to mention that I had also tried this tool to install the drivers on a few different PCs. I did all of this (including other methods) after making sure to uninstall any drivers that were previously installed. The installation succeeds, but still has no effect on the phone being detected when it's in fastboot. Everything else, like file transfer and adb commands does.
Thank you for your time and for replying.
I've had the same problems you've had Waffle. I tried everything I could read in the forms, what ended up fixing the driver issues for me was to use Linux. I owe it to Linux's superior driver support that fixed the issue for me.
Well, I finally got it to work. I decided to try the tool tys0n mentioned again, and it worked. Not sure what I did differently this time, but I am thankful that it is now connecting properly.
Sorry for piggybacking onto my own post but now, after using the razer file to factory reset and lock the bootloader, the screen says "Your device has loaded a different operating system." on boot and some apps still say that the phone is rooted. When accessing the bootloader it says that everything is locked and the OEM Unlocking switch is disabled in developer options. Not sure what I may have done wrong, since it's just running a script for the most part or if it's just stuck like this since I rooted the phone in general.
Related
Hey All,
Been rooted/unlocked since launch and the only time I've flashed a ROM to this device was when the IMM76K leak hit. After flashing I lost CWM and root. Didn't worry too much at the time, but the past couple days I've been attempting to get it back.
I cannot, for the life of me, get the Fastboot drivers to work. I've tried every driver I could think of and I constantly get a "Device cannot start (error 10)". I've tried every USB port, multiple cables and even different machines. Everytime I plug the device in while in the bootloader I get the Windows popup that says my device can perform faster if I plug it into a USB 2.0 port.
When I did the update, does the new bootloader now require a different driver? Everything else works. MTP, ADB etc. Just not fastboot.
I'll include the specs at the bootloader screen.
Fastboot Mode
Product Name - tuna
Variant - toro 32GB
HW Version - 9
Bootloader Version PRIMELA03
Baseband Version - I515.FC05 CDMA - I515.FC04
Carrier Info - None
Serial Number
Signing - production
Lock State - Unlock
Has anybody had this problem since flashing to the latest update? Does anybody have any suggestions or advice?
BonzTM said:
Hey All,
Been rooted/unlocked since launch and the only time I've flashed a ROM to this device was when the IMM76K leak hit. After flashing I lost CWM and root. Didn't worry too much at the time, but the past couple days I've been attempting to get it back.
I cannot, for the life of me, get the Fastboot drivers to work. I've tried every driver I could think of and I constantly get a "Device cannot start (error 10)". I've tried every USB port, multiple cables and even different machines. Everytime I plug the device in while in the bootloader I get the Windows popup that says my device can perform faster if I plug it into a USB 2.0 port.
When I did the update, does the new bootloader now require a different driver? Everything else works. MTP, ADB etc. Just not fastboot.
I'll include the specs at the bootloader screen.
Fastboot Mode
Product Name - tuna
Variant - toro 32GB
HW Version - 9
Bootloader Version PRIMELA03
Baseband Version - I515.FC05 CDMA - I515.FC04
Carrier Info - None
Serial Number
Signing - production
Lock State - Unlock
Has anybody had this problem since flashing to the latest update? Does anybody have any suggestions or advice?
Click to expand...
Click to collapse
No, there should not be any issue. I suggest to re-install the fastboot driver. Use 1wayjonny's drivers here.
I've seriously never had any issues whatsoever in any way with the drivers I'm using, and I got them from the knives & forks package. Check my sig.
Well I don't know what's your case but as I do stuff with Nexus, Galaxy tab and lg o2x on my computer sometimes one of the drivers gets messed for randoms reasons.. So I re install drivers and that's it... Try that suggestions
Sent from my Galaxy Nexus using xda premium
No matter what I do I get this error message.
No matter what driver I use. Even the Universal Naked Drivers.
{
"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 just spent the last hour in the hell where everything is great when Android is booted up, but no ADB in fastboot mode.
After trying anything and everything, I got it to work:
1. Installing the Samsung Drivers while Android was up and running.
2. Reboot device to Fastboot (adb reboot bootloader)
Windows 7 now identified the device as "Android 1.0" with a yellow triangle
3. Right click | Update Drivers | Select Device
From list selected Android Phone
The dialog now showed two possible devices : Google and Samsung. Clicking Samsung showed 3 different drivers. Picked the newest.
Accepted warning about unsigned drivers, it installed it. Voila...I now see no more errors.
rmagruder said:
I just spent the last hour in the hell where everything is great when Android is booted up, but no ADB in fastboot mode.
After trying anything and everything, I got it to work:
1. Installing the Samsung Drivers while Android was up and running.
2. Reboot device to Fastboot (adb reboot bootloader)
Windows 7 now identified the device as "Android 1.0" with a yellow triangle
3. Right click | Update Drivers | Select Device
From list selected Android Phone
The dialog now showed two possible devices : Google and Samsung. Clicking Samsung showed 3 different drivers. Picked the newest.
Accepted warning about unsigned drivers, it installed it. Voila...I now see no more errors.
Click to expand...
Click to collapse
I must've done this a million times. Where are the newest drivers? I've downloaded 1.4.6.0 from Samsung's website. If you or somebody has these "newest" drivers, could I please get a link?
I've used the ones from Samsung's website, the Universal Naked drivers, Google's drivers from SDK, Drivers from Galaxy Nexus Toolkit v7, drivers from Galaxy Nexus Root Toolkit 1.4 by WugFresh. I get the same issue with all of them.
BonzTM said:
No matter what I do I get this error message.
No matter what driver I use. Even the Universal Naked Drivers.
Click to expand...
Click to collapse
Uninstall all drivers related to the Galaxy Nexus using Driver Sweeper, then check my signature and give knives & forks a go.
Theshawty said:
Uninstall all drivers related to the Galaxy Nexus using Driver Sweeper, then check my signature and give knives & forks a go.
Click to expand...
Click to collapse
Did one even better. Went to a brand new machine that had never seen an Android phone to be sure I was getting a clean experience.
Firstly, when I plugged the phone in (Android on), immediately said that the device could perform faster if I plugged it into a USB 2.0 port. Problem is, it was a 2.0 port. Got all the drivers installed etc. MTP, PTP, ADB works; granted very slowly because it's only going at 1.1 instead of 2.0.
Rebooted into Fastboot, same problem as before. Device failed to start (error code 10).
I've done just about everything I can think of to do. It's gotta be something wrong with the hardware itself to be doing this. Problem is, how do I send it back if I can't even un-root it and re-lock it.
BonzTM said:
[snip]
I've done just about everything I can think of to do. It's gotta be something wrong with the hardware itself to be doing this. Problem is, how do I send it back if I can't even un-root it and re-lock it.
Click to expand...
Click to collapse
Have you checked your USB port on your device? Is it dirty/bent/etc? I doubt there is anything wrong with your phone besides that.
And yes, there is no way to re-lock the bootloader if you can't plug into a computer OR if you don't have root.
efrant said:
Have you checked your USB port on your device? Is it dirty/bent/etc? I doubt there is anything wrong with your phone besides that.
And yes, there is no way to re-lock the bootloader if you can't plug into a computer OR if you don't have root.
Click to expand...
Click to collapse
It seems to be fine. :crying:
BonzTM said:
It seems to be fine. :crying:
Click to expand...
Click to collapse
Try using a different cable. I just went through the exact same experience. Hours of not being able to get fastboot drivers to work (ADB would though!).
I have a small desk dock that I got off of E-Bay, and I too was getting the USB 1.1 speed warnings when using it. Never really thought much about it until this particular problem.
I've un-installed, re-installed drivers and done everything short of standing on my head in a corner
Unplugged it from the 'Dock' and used a regular USB2.0 compatible cable, and fastboot fired right up.
pls delete this thread, wiping my pc again and make an format.
Install windows fresh and hoping the best.
KornY10 said:
pls delete this thread, wiping my pc again and make an format.
Install windows fresh and hoping the best.
Click to expand...
Click to collapse
Did it work?
Didnt done it. Maybe today or tomorrow, dont know -.- How can i complete deinstall USB Drivers?
Installed now:
Android SDK
ADB install 1.4.3
Oneplus3 Drivers
Device is detected as: Kedracom?! And then - Kedracom Device, after clicking on "driver update" i can change it to "Android ADB Device" then ADB Sideload works.
When i boot then to Fastboot the Device is detected as "Android Bootloader Device" or so...then i cant install nothing, and i cant connect to the Phone.
Im Using the USB ports from behind, dont use the front one.
Any tip? What can i do? screws me up -.-
{
"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"
}
KornY10 said:
Didnt done it. Maybe today or tomorrow, dont know -.- How can i complete deinstall USB Drivers?
Installed now:
Android SDK
ADB install 1.4.3
Oneplus3 Drivers
Device is detected as: Kedracom?! And then - Kedracom Device, after clicking on "driver update" i can change it to "Android ADB Device" then ADB Sideload works.
When i boot then to Fastboot the Device is detected as "Android Bootloader Device" or so...then i cant install nothing, and i cant connect to the Phone.
Im Using the USB ports from behind, dont use the front one.
Any tip? What can i do? screws me up -.-
Click to expand...
Click to collapse
I'm sitting in the same boat xD
ADB is working fine phone Will be recognized. But in Fastboot Mode nothing.....
On my PC is Windows 10 installed and on my phone OOS 3.2.7
Same here, really strange, or a rly ****ing Noob fail and I don't get it. If someone else could read and help ...would be good
So, dont know...read so many things, all is fine and adb connected but wtf is fastboot not work -.-
are u trying some thing?
me too no Fastboot at all
OP3 : 3.2.7
It maybe bcz the last update, or that old OP3 tool
Hello again
Everything is working good
it seems to be a problem with adb Windows 10 IDK
, it is better to do it on Windows 7
Follow this :
http://forum.xda-developers.com/oneplus-3/how-to/oneplus-3-how-to-unlock-bootloader-t3398733
Ok, so i could install win7 as second OS? Have enough Harddisks, so its np.
Think i try this, PC is fresh installed, so if its not good or buggy i kill it again :/
Ok, Installed Windows 7 and all works fine... damn. thx for the tip
I had this exact issue and fixed it. Fastboot would never see my device, and the device manager shows "Kedracom" no matter how I tried to install or force the correct drivers. Turns out Windows 10 (and Windows 8) has a feature that completely prevents installation of unsigned drivers. If you're seeing "Kedracom" in the device manager, then your driver is NOT actually installed. This is true even if Windows doesn't throw you an error message during install, or if you appear to force the installation. Even though it looks like you're doing the install correctly, Windows just ignores your unsigned drivers.
You need to temporarily disable the security feature to permit installation of unsigned drivers. This involves invoking a special restart function. http://www.howtogeek.com/167723/how...8.1-so-that-you-can-install-unsigned-drivers/
One you've done this you, you can do a forced install of the drivers you downloaded for the OP3.
So I'm wondering anyone can help Ive got a 1st gen and it's bricked it was rooted with custom firmware and had twrp installed i was flashing new firmware and was on twrp I wiped something can't remember what as it was months ago and since then device won't turn I've tried using a fast boot cable but my pc keeps saying its an unrecognised device I've tried using Linux aswell but no such look any ideas any help is appreciated thanks in advance
What does the tab say?
Can you access twrp?
Kenora_I said:
What does the tab say?
Can you access twrp?
Click to expand...
Click to collapse
Can't access anything just get a black screen nothing loads atm might aswell be a wedge to keep the door open I'm trying on a diffrent pc no but installing adb drivers I'm getting an error fail to write 0x1949 hoping if I fix that maybe I'll be a step in the right direction
Does fastboot commands work?
Can you try booting to fastboot
sd_shadow said:
Sounds like a driver issue
Sent from my Moto E (4) using Tapatalk
---------- Post added at 08:54 AM ---------- Previous post was at 08:51 AM ----------
See
https://forum.xda-developers.com/showpost.php?p=54123148&postcount=1
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
Nothing at all work I connect it to the pc try turning it on and it goes be bop bop be over and over again so it's connecting disconnecting connecting disconnecting etc I've drived downloading the drivers off amazon directly it installs then says at the end something like it's installed but incorrectly or may need rebooting
lsngregg said:
Howdy all, I have an old KF here that I have bricked. I'm stuck at the logo. I'm trying to issue shell commands and I get the "- exec '/system/bin/sh' failed: No such file or directory (2)" error. So far I've found that this means I screwed up my /system when I tried getting this thing back to stock. I cannot remember what I was running on it earlier today.
I do know that I downloaded a factory update.zip and installed that from TWRP. I wiped everything before hand. I'm afraid wiping the SD card after installing the update.zip may have caused me to be stuck at the logo without being able to issue shell commands? I've tried the KindleFireUtility and KindleUnbrickUtility and a few things with soupkit. Nothing is working.
I seem to have found a few hints that there are indeed workarounds to this problem without having to make or buy a factory cable. I'm terrible at soldering.. much better at typing in terminals.
If there is any help out there, I would massively appreciate it.
All I want to do is read a d*** book.
-Ellison
UPDATE:
I bought a fastboot cable.
It appears that I can boot in to fastboot mode (Kindle Fire logo, green light, and screen never dims) but I think at some point, the device gets lost. I installed the android bootloader ADB drivers for the fastboot mode. If I start the kindle without the factory cable and it boots normally and sits at the logo screen forever, it gets listed as an ADB device. While the kindle is still attached, I can reboot it in to what I am assuming is fastboot mode. My Windows10 rig sees it as a composite ADB bootloader interface. But I can't get unBrickUtility to do anything... the only thing I saw it do to the kindle was wipe the userdata. Other than that, UnBrickUtility cannot see my kindle in fastboot mode.
Unplugging my factory cable and plugging it back in causes the kindle to be completely unrecognized ( unknown usb device set address failed) on Windows 10.
I have soupkit running on a netbook... it tells me that my shell is damaged, which I know is the problem. But now I'm not sure what to do next as I can't get linux (mint) to recognize my kindle in fastboot mode either.
I really hope someone out there has been here before and can help. I'd love to see this thing running back to normal again.
related image:
{
"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"
}
UPDATE: I FIXED IT.
What ultimately saved this device was being able to get in to fastboot mode. I bough the cable, flashed FFF and TWRP from fastboot mode. I then found I could not run shell commands. I fixed this by running
Code:
fastboot oem format
from fastboot mode. Then going back in to TWRP, I was able to mount /System and was then able to use Soupkit's kindle fire utility to fix the /sdcard. The version of TWPR I was using would not flash the stock update, so I downloaded and flashed that. Afet that installed, I was able to flash the stock update and now I'm up and running again! WOO! Thank you so much for the developers here!!!
Admin: can I get the thread title so reflect the fact that I have fixed this for future users? Thank you!
Click to expand...
Click to collapse
It's driving me nuts been trying to fix it on and off for ages still get no where the pc has the drivers installed but just connects and disconnects every tool I've tried says it either waiting for device or can't find device
Try the tools mentioned in above post
Phone will only connect to adb in bootloader mode and shows as (unauthorized) despite USB debugging enabled. Tried revoking all but did not fix.
Won't prompt for file transfer or USB debugging. Nothing even shows up in device manager when phone is booted into Android.
Tried 4 cables and 4 computers. Tried changing default usb mode.
Bootloader is unlocked.
I used to transfer files all the time but not it randomly does not connect.
You have to click on the popup on phone to "authorize" adb connection. Otherwise, u need latest platform tools and drivers
HueyT said:
You have to click on the popup on phone to "authorize" adb connection. Otherwise, u need latest platform tools and drivers
Click to expand...
Click to collapse
I never get the popup. It is as if the phone is connected to the wall when I plug it into my computer. EXCEPT when I am in booted into recovery and it says it is unauthorized.
adb devices
{
"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"
}
Not detected in fastboot mode at all.
The only option I see is to try factory reset via recovery.
I see this in recovery
Now I literally can't get anything to show in device manager or adb/fastboot.
I have tried every driver and guide under the sun. Disabled driver signature enforcement. Ran the convert MSM and the regular 1907 MSM, didn't fix.
No matter how many times I install the OP drivers or Google nothing even shows in device manager even when "Show hidden devices" is checked. This picture I am in the system with USB debug and OEM unlock enabled set to file transfer (Although it never prompted me for anything, in fact USBDeview doesn't show anything when I plug in the phone):
So it recognized your hd1907 in EDL mode for msmtool? If so then it's a software prob and fixable with oos10:
[CLOSED] T-Mobile 7T Conversion to International WITHOUT unlocked bootloader/SIM unlock!
Here is a patched MSM download tool for TMobile OP7T. It will bypass the need to sim unlock before unlocking the bootloader, and will also bypass the need of an unlock token file from OnePlus (hence skip the wait period of 1 week to get the...
forum.xda-developers.com
HueyT said:
So it recognized your hd1907 in EDL mode for msmtool? If so then it's a software prob and fixable with oos10:
[CLOSED] T-Mobile 7T Conversion to International WITHOUT unlocked bootloader/SIM unlock!
Here is a patched MSM download tool for TMobile OP7T. It will bypass the need to sim unlock before unlocking the bootloader, and will also bypass the need of an unlock token file from OnePlus (hence skip the wait period of 1 week to get the...
forum.xda-developers.com
Click to expand...
Click to collapse
I already ran this patched MSM like 10 times, I just get left in fastboot with no recovery or system and am forced to run the regular 1907 MSM to get back. Also tried Ubuntu just now and still not detected. I am very confident it is a software issue (on both phone and pc maybe) but I just can't figure it out for the life of me.
Now my bootloader is locked and I can't even connect to fastboot to unlock it again.
My sim is genuinely unlocked and I also have the genuine unlock_code.bin.
Currently spinning up a brand new install of Windows on my laptop to test with. Do you have exact recommendations for drivers? Some people recommend the Oneplus one and others the Google. What about the all in one tool driver install?
I currently have a network unlocked stock fully updated OOS 11.0.1.6.HD63CB system with locked bootloader. (I tried OTA updating to see if it would fix it)
Jonnyswboy said:
I already ran this patched MSM like 10 times, I just get left in fastboot with no recovery or system and am forced to run the regular 1907 MSM to get back. Also tried Ubuntu just now and still not detected. I am very confident it is a software issue (on both phone and pc maybe) but I just can't figure it out for the life of me.
Now my bootloader is locked and I can't even connect to fastboot to unlock it again.
My sim is genuinely unlocked and I also have the genuine unlock_code.bin.
Currently spinning up a brand new install of Windows on my laptop to test with. Do you have exact recommendations for drivers? Some people recommend the Oneplus one and others the Google. What about the all in one tool driver install?
I currently have a network unlocked stock fully updated OOS 11.0.1.6.HD63CB system with locked bootloader. (I tried OTA updating to see if it would fix it)
Click to expand...
Click to collapse
U need Qualcomm USB 9008 drivers
HueyT said:
U need Qualcomm USB 9008 drivers
Click to expand...
Click to collapse
I successfully ran the MSM several times.
After above patched MSMtool, Then can't u do "fastboot flashing unlock_critical" to unlock bootloader? Only then do u fastboot flash all oos10 files
HueyT said:
After above patched MSMtool, Then can't u do "fastboot flashing unlock_critical" to unlock bootloader? Only then do u fastboot flash all oos10 files
Click to expand...
Click to collapse
After above patched MSMtool I cannot connect to PC via fastboot. I just bought a Pixel 6, but thanks for the help.
Pixel Exp USB not working
So i want to install pixel experience on my one plus 7T and I did all the steps until i reached the side loading but the issue is when ever I enter pixel experience recovery mode my computer doesn’t recognize my phone and there is a triangle on it in device manager but in bootloader or when booted the connection works fine.
- i have installed google drivers
- usb is working fine
Install Qualcomm driver
https://gsmusbdriver.com/install-qualcomm-usb-driver
I'm currently having this same issue with the Qualcomm Drivers installed. Any other suggestions?
Azu1e said:
I'm currently having this same issue with the Qualcomm Drivers installed. Any other suggestions?
Click to expand...
Click to collapse
Try reinstalling USB and Qualcomm drivers with Windows in Test Mode. Sharing a screenshot of you Device Manager could help us help you also.
Did you find a solution? I am facing the same issue.
- Check the USB cable being used
- Try another USB port on the computer
- LIke other user mentioned boot your windows into recovery then start the windows with disabled driver signature verification mode then install the drivers (For me Oneplus drivers itself worked fine) this will just make sure that ur computer recognizes your android rest is left to what you have fiddled on the ROM. worst case just download the stock ROM with MSM tool and reset your entire phone and continue the experiments.
Robinlong said:
Try reinstalling USB and Qualcomm drivers with Windows in Test Mode. Sharing a screenshot of you Device Manager could help us help you also.
Click to expand...
Click to collapse
Hello havent had time to mess with my phone. Bellow I have attached a copy of how my device manager looks like when in the pixel experience recovery mode. When trying to update the drivers these are the options that I get. Regardless of what I click on for the model option none of them seem to work. I am kind of stuck 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"
}
Azu1e said:
When trying to update the drivers
Click to expand...
Click to collapse
Make sure Windows is in Test Mode or Disable Integrity Check. Then, try reinstalling the Oneplus USB drivers from here first and lastly Qualcomm drivers from here or from here.
I think that in Recovery Mode the Device should look like this:
Robinlong said:
Make sure Windows is in Test Mode or Disable Integrity Check. Then, try reinstalling the Oneplus USB drivers from here first and lastly Qualcomm drivers from here or from here.
I think that in Recovery Mode the Device should look like this:
View attachment 5918033
Click to expand...
Click to collapse
I tried this again using the three links provided. I made sure to reset my computer by disabling the Integrity and being in test mode. Still no luck. I have no idea where I went wrong. I've followed all the instructions from the forums and made sure to read every step carefully before attempting. As and alternative I tried to run TWRP and install the rom from a usb plugged into my phone. Even this has been failing with both Pixel experience and Lineage OS. At the moment I have flashed back to 10.0.13 Global OnePlus 7t with the pixel experience recovery image. Any further help or advice is much appreciated.
Azu1e said:
I tried this again using the three links provided. I made sure to reset my computer by disabling the Integrity and being in test mode. Still no luck. I have no idea where I went wrong. I've followed all the instructions from the forums and made sure to read every step carefully before attempting. As and alternative I tried to run TWRP and install the rom from a usb plugged into my phone. Even this has been failing with both Pixel experience and Lineage OS. At the moment I have flashed back to 10.0.13 Global OnePlus 7t with the pixel experience recovery image. Any further help or advice is much appreciated.
View attachment 5918571
Click to expand...
Click to collapse
Could using windows 11 be causing a problem?
Any suggestions I have tried installing the drivers on Windows 10 and 11. I have tried using different computers but still no luck.
Azu1e said:
Any suggestions I have tried installing the drivers on Windows 10 and 11. I have tried using different computers but still no luck.
Click to expand...
Click to collapse
Can you define "no luck"? What error or problem are you having?
If you are still getting the yellow exclamation in Device Manager, you could try clicking "Update Driver" and browsing to the folder where you unzipped the drivers.
Also there are many solutions you could try from this thread.
I've tried following the instructions on that thread and have been unable to update the drivers from the disk. The only inf file available to me is the autorun file in the OnePlus_USB_Drivers_Setup folder. All of these issues are when running the phone in the pixel experience recovery mode.
View attachment 9rkonok9bdv81.webp