hey all...i need help did anyone been able to succefly msm his phone on a virtualbox? i had setup everything on a win7 wnd win 10 machine every driver and all so the msm detect my phone and all and its says conected but as soon as i press start boom "sahara conexion failed" its driving me nuts i have tried everything drivers the + and power button nothing work.....i need help urgently
so here is the conclusion after long testing msmtool does not work on virtualisation i tried (virtualbox and qemu/kvm)....my problem was almost similar to this
crispy-cat said:
So, my phone's bricked - it won't boot, just brings up fastboot. As the solution to this problem appears to be to use the MSM tool to do an "actual" factory reset, I downloaded the MSM tool, and the decrypted ROM from this link: https://androidfilehost.com/?fid=8889791610682918291.
First I tried this on a Windows 7 VirtualBox VM (I use Ubuntu on my actual computer). The drivers didn't even install right it seems, and the device (in EDL mode) wasn't even recognized. Then I tried it on my mom's Windows 10 laptop. MSM never showed the device as connected. I think possibly the lack of a USB 2 port could be the cause.
Finally I set up a basic VM with Windows 10 and a USB 2 controller, and it worked-ish. MSM recognized the device, showed it as connected and started doing its thing, but stopped at "Sahara Communication failed". What is preventing it from getting past this? I'm using the cable provided in the box. Everything is recognized correctly. I've retried multiple times but still the same result.
SUCCESS!
I had a spare laptop lying around, and it has USB 2 ports. I loaded WIndows 10 onto it and tried the MSM from there -- AND IT WORKED!
As much as I hate Qualcomm for their monopolistic business practices, I thank them for EDL mode. I also thank OnePlus for somehow failing to prevent the MSM tool from entering the hands of the public every time, and @Some_Random_Username for trafficking this good. Yeet!
Click to expand...
Click to collapse
crispy-cat said:
The USB controller is part of VirtualBox. I think you need to download and install the extensions pack for the USB 2.0 version. The problem is that the controller is not capable of the absolute direct communication that the software needs to work, or it just doesn't connect fast enough. This would be a great example of why Windows on a USB would be great, since you could just boot it. But then MS wouldn't be able to make its billions. So we lose.
I'd try VMWare and KVM to see if they do any better. I'm not sure if WINE supports USB passthrough or not. Otherwise try to find a Windows box you can use.
Click to expand...
Click to collapse
so i dualbooted windows and i was able to flash so in future references dont try on virtual box if your on linux or mac... ahh wish there was msmtool for linux
wasted-potential said:
so here is the conclusion after long testing msmtool does not work on virtualisation i tried (virtualbox and qemu/kvm)....my problem was almost similar to this
so i dualbooted windows and i was able to flash so in future references dont try on virtual box if your on linux or mac... ahh wish there was msmtool for linux
Click to expand...
Click to collapse
https://forum.xda-developers.com/t/...ad-tool-to-work-on-a-virtual-machine.4475529/ this person seemed to manage to get it working. My issue is now that I cant get edl to work. No matter what I do..
pyry666 said:
https://forum.xda-developers.com/t/...ad-tool-to-work-on-a-virtual-machine.4475529/ this person seemed to manage to get it working. My issue is now that I cant get edl to work. No matter what I do..
Click to expand...
Click to collapse
i have no clue i did exact same steps as he did even more with multiple attempts no luck so i gave up...
if you are stuck just dual boot temporarly install a light version of that spyware windows and set up your stuffs its flashed at first attempt for me even with a usb 3.0 port i read that its buggy with msm but wasnt the case for me
wasted-potential said:
i have no clue i did exact same steps as he did even more with multiple attempts no luck so i gave up...
if you are stuck just dual boot temporarly install a light version of that spyware windows and set up your stuffs its flashed at first attempt for me even with a usb 3.0 port i read that its buggy with msm but wasnt the case for me
Click to expand...
Click to collapse
I might just do that. I only wanted msm as a back up option. I am pretty sure I can fastboot flash back to stock atm anyway and I am not bricked, yet..
Related
So, I tried to use Parallels (running windows XP) on my Intel Imac to flash a Kaiser Rom onto my AT&T Tilt. I'm currently stuck on the bootloader. I think I did find a solution, but I need to wait 10 minutes til I can download another Rapidshare file. In the meantime . . .
I think I did everything right. HardSPL worked fine, but then, when I tried to flash Dutty's Dual v4 ROM, it stopped at 6% and told me there was a communication error. I tried it a few more times, tried Dutty's Touchflo Rom (that got to 4%) . . . still no luck. Same error. In between each try, I reset using the stylus and sometimes the stylus while holding down power and camera.
Am I doing something wrong, or was my mistake trying to do this via parellels?
Current screen says:
KAIS1*0 MFG
SPL-1.0.OliPof
CPLD-8
USB
Thanks, guys.
I can confirm that if you install xp via boot camp then you can flash fine on a mac. I haven't tried going through an emulator such as parallels though. It should work fine though as long as parallels has taken over the usb ports.
Yeah, the USB connection wasn't the problem. And, unfortunately, I don't have extra XP licenses lying around to bootcamp. my mac.
Anyone have any idea? I'll give you a cookie . . .
By the way
It is error 262 that I'm getting . . .
I went through bootcamp boot as well, I rather assumed that I was going to need direct access to the hardware rather than the pass through of parallels...
btw you can set up parallels to boot a bootcamp partition... so you can use the direct boot and parallels from the same installation.
drewcopeland said:
It is error 262 that I'm getting . . .
Click to expand...
Click to collapse
I might have to look into that. My "solution" didn't work. I'm going to try to find the original ROM somewhere . . .
zenrandom said:
I went through bootcamp boot as well, I rather assumed that I was going to need direct access to the hardware rather than the pass through of parallels...
btw you can set up parallels to boot a bootcamp partition... so you can use the direct boot and parallels from the same installation.
Click to expand...
Click to collapse
I am using Fusion instead of Parallels but this is what I do. I only have 1 copy of xp installed via bootcamp but I can also access it through Fusion.
I also have fusion on my MacBook Pro, and it failed when tried to flash. So I bootcamp and started XP and it flashed flowlessly
If you own original XP CD (like me) you can always call microsoft to activate, and since it is installed in 1 PC then fine (you'll have 1 license for parallel & another for Bootcamp)
drewcopeland said:
So, I tried to use Parallels (running windows XP) on my Intel Imac to flash a Kaiser Rom onto my AT&T Tilt. I'm currently stuck on the bootloader. I think I did find a solution, but I need to wait 10 minutes til I can download another Rapidshare file.
Click to expand...
Click to collapse
Which version of parallels do you have? In version 5160 the usb flashing works fine, in 5582 it is broken, as is in version 5584. They had an special build 5582.5 which allowed me to flash my phone correctly and according to parallels, the "next" version will include those usb fixes.
I'm using the latest version 5584 and when I need to flash my phone, first i shut down windows vm, install parallels 5160 over the current version and then boot up windows. I ignore the installation of parallels tools and just flash my phone. Then shut down windows again, re-install parallels 5584 and all is fine again.
Hope this helps you...
that does. Do you mean the most recent update will work?
edit: never mind. the most recent is 5583. I'll try to find 5160
drewcopeland said:
Yeah, the USB connection wasn't the problem. And, unfortunately, I don't have extra XP licenses lying around to bootcamp. my mac.
Anyone have any idea? I'll give you a cookie . . .
Click to expand...
Click to collapse
If you have a valid license for parallels, then you have a valid license to use bootcamp...
That said, I have flashed through parallels and vmware fusion TONS of times (about to do it again, in fact). So long as you've routed the "HIGH GENERIC RNDIS" device to the virtual machine it should work fine.
I posted this in another thread, but created this new one specifically for these users that are having this issue and can't solve it because they don't have access to an XP machine.
I solved my issue late last night. I am running Windows 7 64bit. I saw that a lot of the guys here used XP to run the KDZ flasher and that wasn't an option for me until I installed XP Mode.
XP Mode allows you to run a virtual XP machine inside Windows 7. I was able to run the KDZ flasher in there and successfully flashed the KDZ GB file to my phone.
You do need to flash stock recovery first. I tried unsuccessfully to flash the KDZ with CWM recovery installed. It would not work until I flashed stock recovery.
One other problem I ran into is, in XP Mode, you are "attaching" USB devices to the virtual XP session via a "stub USB driver." For some reason during the KDZ flashing process the USB modem driver for LG kept releasing from my session. What I did to counteract this was manual attach it each time it released. This was easy, but I had to stay on top of it until the flasher finished the job. I have two monitors so I had the "Devices and Printers" window open in Windows 7, and when I heard the ding indicating the USB driver had left the session, and saw the LG devices appear in the Devices and Printers window, I would just click attach on the USB pulldown in the XP session.
I know this sounds a little complex for some (and possibly vague), but once you get into the XP Mode session you will see what I'm talking about.
I hope this helps you guys still stuck on SW Update screen that don't have XP.
hey guys whats up
i lost my nerves for 2 days tr5ying everything to bring back to life my P990..
since im huge noob with android i messed up everything when i tried to update phone with cm7. anyway i can bring it back to life with rom for p999 and thats it...
all other techniques dont work. cant even boot phone or whatever.. tried smartflash but i dont get anything what should be automaticaly assigned.. like communication driver..com port etc. i wanted to try kdz but this file cant be downloaded..its forbidden on lg site and now it cant be downloaded on megaupload. can i download file from somewhere else? im really pissed off cuz im stuck like this. please help
http://forum.xda-developers.com/showthread.php?t=1056847
And if you have a P990, you're in the wrong forum (this forum is for the P999).
omerika.emir said:
hey guys whats up
i lost my nerves for 2 days tr5ying everything to bring back to life my P990..
since im huge noob with android i messed up everything when i tried to update phone with cm7. anyway i can bring it back to life with rom for p999 and thats it...
all other techniques dont work. cant even boot phone or whatever.. tried smartflash but i dont get anything what should be automaticaly assigned.. like communication driver..com port etc. i wanted to try kdz but this file cant be downloaded..its forbidden on lg site and now it cant be downloaded on megaupload. can i download file from somewhere else? im really pissed off cuz im stuck like this. please help
Click to expand...
Click to collapse
The Roms for the p999 and the p990 are not inter changeable. Different frame work.
jrfaulkin said:
I posted this in another thread, but created this new one specifically for these users that are having this issue and can't solve it because they don't have access to an XP machine.
I solved my issue late last night. I am running Windows 7 64bit. I saw that a lot of the guys here used XP to run the KDZ flasher and that wasn't an option for me until I installed XP Mode.
XP Mode allows you to run a virtual XP machine inside Windows 7. I was able to run the KDZ flasher in there and successfully flashed the KDZ GB file to my phone.
You do need to flash stock recovery first. I tried unsuccessfully to flash the KDZ with CWM recovery installed. It would not work until I flashed stock recovery.
One other problem I ran into is, in XP Mode, you are "attaching" USB devices to the virtual XP session via a "stub USB driver." For some reason during the KDZ flashing process the USB modem driver for LG kept releasing from my session. What I did to counteract this was manual attach it each time it released. This was easy, but I had to stay on top of it until the flasher finished the job. I have two monitors so I had the "Devices and Printers" window open in Windows 7, and when I heard the ding indicating the USB driver had left the session, and saw the LG devices appear in the Devices and Printers window, I would just click attach on the USB pulldown in the XP session.
I know this sounds a little complex for some (and possibly vague), but once you get into the XP Mode session you will see what I'm talking about.
I hope this helps you guys still stuck on SW Update screen that don't have XP.
Click to expand...
Click to collapse
I'm running Windows 7 Home premium 64 Bit and Virtual XP Mode is not compatible with this version of Windows 7... Is there another way around this issue...???
Erocks said:
I'm running Windows 7 Home premium 64 Bit and Virtual XP Mode is not compatible with this version of Windows 7... Is there another way around this issue...???
Click to expand...
Click to collapse
VMware with XP on it/Google how to bypass limitation?
Found this to get Xp Mode on home edition idk if it works I just use VMware personally
http://m.tomshardware.com/news/windows-xp-mode-windows-7-win7,10213.html
Sent from my LG-P999
Bricked my OPO somehow flashing cosmic OS. I get the load screen and thats it. no recovery and no fastboot. I've found a million tutorials on how to fix a hard brick, but all of them show the opo in device manager as qualcomm. I've downloaded some drivers but not sure what to do from here to get that to read qualcomm so i can start the unbrick process. any help or suggestions?
Jjleininger said:
Bricked my OPO somehow flashing cosmic OS. I get the load screen and thats it. no recovery and no fastboot. I've found a million tutorials on how to fix a hard brick, but all of them show the opo in device manager as qualcomm. I've downloaded some drivers but not sure what to do from here to get that to read qualcomm so i can start the unbrick process. any help or suggestions?
Click to expand...
Click to collapse
Forget all the other guides...
https://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
Just use this one and the drivers included.
It will easily restore back to cm11s(stock KK),after that you can flash MM(Cos13.1x) if you want through fastboot.
The key-point is you need to find one of Xp systems around you and then use that because win8/10 somehow makes driver signature a headache and takes more time to set-up.
Mr.Ak said:
Forget all the other guides...
https://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
Just use this one and the drivers included.
It will easily restore back to cm11s(stock KK),after that you can flash MM(Cos13.1x) if you want through fastboot.
The key-point is you need to find one of Xp systems around you and then use that because win8/10 somehow makes driver signature a headache and takes more time to set-up.
Click to expand...
Click to collapse
I'll check this out this evening. I'm playing hell trying to get drivers working. All the write ups I see show the opo saying qualusb in device manager upon connection and no matter what I do I can't get mine to. I've got an old laptop running win7 maybe I'll give that a shot. This would be done and over if it showed as qualusb in "ports" instead of adb interface in "usb".
Thanks for the info.
Jjleininger said:
I'll check this out this evening. I'm playing hell trying to get drivers working. All the write ups I see show the opo saying qualusb in device manager upon connection and no matter what I do I can't get mine to. I've got an old laptop running win7 maybe I'll give that a shot. This would be done and over if it showed as qualusb in "ports" instead of adb interface in "usb".
Thanks for the info.
Click to expand...
Click to collapse
Remove all other drivers.
Again,XP is advisable,I don't think it takes long to dual boot XP alongside.
Downgraded to Windows 7, now the phone shows up as Qualcomm, but still can't get the program to recognize. Bootable xp drive failed, will try disc when I get home.
Jjleininger said:
Downgraded to Windows 7, now the phone shows up as Qualcomm, but still can't get the program to recognize. Bootable xp drive failed, will try disc when I get home.
Click to expand...
Click to collapse
Sorry for late reply.It should be "Qhs_bulk" or "qualcomm_diagnostics9006" not just "Qualcomm".
Just try refreshing through Ebus button and make sure you're using original 1+ cable and try changing ports likewise.
I'd still say try with XP,use rufus to make a bootable usb and if you're good to go.After you setup the drivers(from thread link I gave you or from the zip itself), make sure you run the program as an administrator.
Mr.Ak said:
Sorry for late reply.It should be "Qhs_bulk" or "qualcomm_diagnostics9006" not just "Qualcomm".
Just try refreshing through Ebus button and make sure you're using original 1+ cable and try changing ports likewise.
I'd still say try with XP,use rufus to make a bootable usb and if you're good to go.After you setup the drivers(from thread link I gave you or from the zip itself), make sure you run the program as an administrator.
Click to expand...
Click to collapse
I've got it so it says qualcomm hs-usb qdloader 9008. I'll continue refreshing and swapping ports. I've used Rufus and four whatever reason it's giving me bsod when booting via USB. I'll give a disc a try.
Jjleininger said:
I've got it so it says qualcomm hs-usb qdloader 9008. I'll continue refreshing and swapping ports. I've used Rufus and four whatever reason it's giving me bsod when booting via USB. I'll give a disc a try.
Click to expand...
Click to collapse
Your motherboard supports usb booting?
Mr.Ak said:
Your motherboard supports usb booting?
Click to expand...
Click to collapse
Yessir, just went from windows 10 to 7 via USB boot.
Jjleininger said:
Yessir, just went from windows 10 to 7 via USB boot.
Click to expand...
Click to collapse
You can use other software than rufus for XP but that'll make the process too slow,atleast while installing XP.
But a CD always does the work perfectly for XP!
Mr.Ak said:
You can use other software than rufus for XP but that'll make the process too slow,atleast while installing XP.
But a CD always does the work perfectly for XP!
Click to expand...
Click to collapse
I tried a straight jump from win 10 to xp with a disc and the installation option was grayed out, maybe with 7 it'll give me that option back. I'll burn a new one this evening and give it a go.
Jjleininger said:
I tried a straight jump from win 10 to xp with a disc and the installation option was grayed out, maybe with 7 it'll give me that option back. I'll burn a new one this evening and give it a go.
Click to expand...
Click to collapse
Dual boot?
Hello XDA!
I am attempting to restore my OnePlus 6 back to full stock using the MSM Downloader tool. I have followed multiple guides but every-time I use the tool the progress stops at "Param preprocessing".
I have attempted to use multiple versions of the image (9.0.5, 9.0.4, 9.0.7 etc.) but to no avail. I've even completely re-installed Windows just-in-case drivers did not install correctly.
I would greatly appreciate any insight you guys can give me,
p.s. if there is another way to restore the phone to complete stock that would be great
DragonsFedora said:
Hello XDA!
I am attempting to restore my OnePlus 6 back to full stock using the MSM Downloader tool. I have followed multiple guides but every-time I use the tool the progress stops at "Param preprocessing".
I have attempted to use multiple versions of the image (9.0.5, 9.0.4, 9.0.7 etc.) but to no avail. I've even completely re-installed Windows just-in-case drivers did not install correctly.
I would greatly appreciate any insight you guys can give me,
p.s. if there is another way to restore the phone to complete stock that would be great
Click to expand...
Click to collapse
Have you tried a different cable and or different USB port. Do you know how to put phone in edl mode?
Hi, I got the same error, try to uninstall all Qualcomm related drivers and let W10 download them for you, don't install them by yourself.. This is how I got it working (W10 Insiders Prev) and when you connect your phone while holding volume up, keep it pressed for like ~5 more seconds (IDK if that's usefull)
MrSteelX said:
Have you tried a different cable and or different USB port. Do you know how to put phone in edl mode?
Click to expand...
Click to collapse
I know how to put the phone on EDL mode. I have also tried multiple USB ports but the same error occurs.
Did you enter in Windows 10 test mode?
yeah, I did make sure.
Don't like Android v.12 at all, so decided to test our a v 13 build. Even worse. So, decided to roll back to v11... something very bad happened along the way.
After getting the 11 dev version installed, I was installing another v11 rom and ended up with a Recovery boot loop,. Somewhere along the way while trying to fix that, my screen that will no longer come on at all. No vibrations or display no matter what I do.
Turns out, Windows could see it plugged in; albeit as Unknown Device (Device Descriptor Request Failed). After lots of holding down buttons, lots of driver installs, disabling windows signatures, lots of different USB cables, leaving it on the charger overnight, and trying both USB and the USB-C ports, I finally got it to go from Unknown Device to Qualcomm HS-USB QDLoader 9008.
Tried MSM, but after 10-12 seconds I would get Sahara communication failed.
Back to troubling shooting... Start MSM as amin, swap usb cables, test all ports, ect., no luck.
Somewhere along the way, it seemed to get even worst... now, after 10 seconds or so after plugging in the phone, it will disconnect, followed by reconnecting a few seconds later. It is being detected as as the Qualcomm and it shows the com port it is connected to, but the device will drop out of device manager every few seconds before reconnecting. It is acting like it is in some soft of EDL bootloop.
I tried uninstalling the Qualcomm drivers and tried several different driver versions ( unsigned 2.1.0.5, Authenticode Signed 2.1.1.2, and Digitally Signed 2.1.2.2).
Outside of that, I am at a complete loss of what to try or do. Any suggestions?
Raccroc said:
Don't like Android v.12 at all, so decided to test our a v 13 build. Even worse. So, decided to roll back to v11... something very bad happened along the way.
After getting the 11 dev version installed, I was installing another v11 rom and ended up with a Recovery boot loop,. Somewhere along the way while trying to fix that, my screen that will no longer come on at all. No vibrations or display no matter what I do.
Turns out, Windows could see it plugged in; albeit as Unknown Device (Device Descriptor Request Failed). After lots of holding down buttons, lots of driver installs, disabling windows signatures, lots of different USB cables, leaving it on the charger overnight, and trying both USB and the USB-C ports, I finally got it to go from Unknown Device to Qualcomm HS-USB QDLoader 9008.
Tried MSM, but after 10-12 seconds I would get Sahara communication failed.
Back to troubling shooting... Start MSM as amin, swap usb cables, test all ports, ect., no luck.
Somewhere along the way, it seemed to get even worst... now, after 10 seconds or so after plugging in the phone, it will disconnect, followed by reconnecting a few seconds later. It is being detected as as the Qualcomm and it shows the com port it is connected to, but the device will drop out of device manager every few seconds before reconnecting. It is acting like it is in some soft of EDL bootloop.
I tried uninstalling the Qualcomm drivers and tried several different driver versions ( unsigned 2.1.0.5, Authenticode Signed 2.1.1.2, and Digitally Signed 2.1.2.2).
Outside of that, I am at a complete loss of what to try or do. Any suggestions?
Click to expand...
Click to collapse
First try and go ahead and pick target and the start button on MSM tool. Then try the 3 button combo till it reboots edl. When MSM tool connects it should start process without rebooting device.
mattie_49 said:
First try and go ahead and pick target and the start button on MSM tool. Then try the 3 button combo till it reboots edl. When MSM tool connects it should start process without rebooting device.
Click to expand...
Click to collapse
So, that actually stablized the driver connection; however, it also brought be right back to Sahara Communication Failed.
Progress (I hope)!
Thread '[Solved!] MSM Download Tool Issues - Sahara Communication failed, phone exits EDL' https://forum.xda-developers.com/t/...communication-failed-phone-exits-edl.4245913/
Thanks for the info and links. I am on Windows 11, which seems to be an issue for some. I will see about trying it on my wife's v10 laptop tonight and see if that changes anything.
Solved!
Three button reboots and then both volume buttons to get back to EDL as soon as the driver dropped seemed to work. Took a few tries (on Win 11 using original usb-c cable) but it installed the rom and booted up.
'course, now is on an India variant, so I still gotta get back to LE2115, but that is another story for another thread.
Raccroc said:
Solved!
Three button reboots and then both volume buttons to get back to EDL as soon as the driver dropped seemed to work. Took a few tries (on Win 11 using original usb-c cable) but it installed the rom and booted up.
'course, now is on an India variant, so I still gotta get back to LE2115, but that is another story for another thread.
Click to expand...
Click to collapse
There is a global msm with target id india
[Locked] Global 11.2.10.10 MSM Tool (added experimental support for Indian variant flashing as well)
This method is outdated. You must use this method or you will run into problems...
forum.xda-developers.com
rizzmughal said:
[Locked] Global 11.2.10.10 MSM Tool (added experimental support for Indian variant flashing as well)
This method is outdated. You must use this method or you will run into problems...
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks for the link, I will give that a go.
Most of the MSM packages I could find for the LE2115 specifically either were bad links or had viruses. I did find a global version, which is what I was originally trying to use; however, when I finally got past my other issues, it gave me some sort of hardware version mismatch error in MSM (don't remember the exact message).
Somewhere along the way, someone suggested the India version. That one worked and I wasn't going to quibble at the time, as my main concern was just getting the lights to come back on.
Now I have a phone with a working display, that is my next todo...
Raccroc said:
Thanks for the link, I will give that a go.
Most of the MSM packages I could find for the LE2115 specifically either were bad links or had viruses. I did find a global version, which is what I was originally trying to use; however, when I finally got past my other issues, it gave me some sort of hardware version mismatch error in MSM (don't remember the exact message).
Somewhere along the way, someone suggested the India version. That one worked and I wasn't going to quibble at the time, as my main concern was just getting the lights to come back on.
Now I have a phone with a working display, that is my next todo...
Click to expand...
Click to collapse
I know thats when ur phone was hard bricked now this one will work for u to get back to global 2115
Raccroc said:
Thanks for the link, I will give that a go.
Most of the MSM packages I could find for the LE2115 specifically either were bad links or had viruses. I did find a global version, which is what I was originally trying to use; however, when I finally got past my other issues, it gave me some sort of hardware version mismatch error in MSM (don't remember the exact message).
Somewhere along the way, someone suggested the India version. That one worked and I wasn't going to quibble at the time, as my main concern was just getting the lights to come back on.
Now I have a phone with a working display, that is my next todo...
Click to expand...
Click to collapse
Index of /list/Unbrick_Tools
These are def not viruses and windows has warned me of these as well on Win 11. Just accept and install. These are legit af
Completely back up and running again. Ran into the touchscreen issue, but fixed by using the linked Global MSM above.
As an FYI: the virus issue was from a FizzyAps post linking MSM for LE2115 on a Google Drive share. Couldn't download the file because it didn't pass Google's virus scan.
https://forum.xda-developers.com/t/global-oneplus-9-msm-tool-updated.4284779/
Raccroc said:
Completely back up and running again. Ran into the touchscreen issue, but fixed by using the linked Global MSM above.
As an FYI: the virus issue was from a FizzyAps post linking MSM for LE2115 on a Google Drive share. Couldn't download the file because it didn't pass Google's virus scan.
https://forum.xda-developers.com/t/global-oneplus-9-msm-tool-updated.4284779/
Click to expand...
Click to collapse
Good deal. That's all we here for neway is to help one another.