Bricked Lumia 950XL and Windows Device Recovery Tool EOL - Microsoft Lumia 950/950 XL

I've bricked 950XL and in the device manger i can see the qualcomm serial device
Now i wanted to download the Windows Device Recovery Tool
-------
This XML file does not appear to have any style information associated with it. The document tree is shown below.
<Error>
<Code>ResourceNotFound</Code>
<Message>The specified resource does not exist. RequestId:b63fac0c-501e-0003-2f80-4c2de5000000 Time:2021-05-19T07:30:29.8362829Z</Message>
</Error>
-------
I have no idea how i can recover my phone

mathewm said:
I've bricked 950XL and in the device manger i can see the qualcomm serial device
Now i wanted to download the Windows Device Recovery Tool
-------
This XML file does not appear to have any style information associated with it. The document tree is shown below.
<Error>
<Code>ResourceNotFound</Code>
<Message>The specified resource does not exist. RequestId:b63fac0c-501e-0003-2f80-4c2de5000000 Time:2021-05-19T07:30:29.8362829Z</Message>
</Error>
-------
I have no idea how i can recover my phone
Click to expand...
Click to collapse
bad news microsoft has finally retired the Windows Device Recovery Tool and the last only method to recover a lumia device
according to this thread in Microsoft forum (In Spanish) and is for the end of support of W10M in 2020
From what I understand there is not an installer that does not use the internet as well as the drivers to be able to recover the device
I quote verbatim what he meant
"I can tell you that the Windows Device Recovery Tool is no longer available for download, nor is it functional on computers that are still installed, due to the end of the life cycle of Windows Phone 8.1 in June 2019 and the end Windows 10 mobile support cycle in June 2020"
Sorry for those bad news but I had an lumia 640xl and in order to test windows rt or windows ARM I need the WDRT for drivers and to downgrade my device to WP8.1

MauriJ2001 said:
bad news microsoft has finally retired the Windows Device Recovery Tool and the last only method to recover a lumia device
according to this thread in Microsoft forum (In Spanish) and is for the end of support of W10M in 2020
From what I understand there is not an installer that does not use the internet as well as the drivers to be able to recover the device
I quote verbatim what he meant
"I can tell you that the Windows Device Recovery Tool is no longer available for download, nor is it functional on computers that are still installed, due to the end of the life cycle of Windows Phone 8.1 in June 2019 and the end Windows 10 mobile support cycle in June 2020"
Sorry for those bad news but I had an lumia 640xl and in order to test windows rt or windows ARM I need the WDRT for drivers and to downgrade my device to WP8.1
Click to expand...
Click to collapse
good news.
I could download the file from Microsoft and install it.
The download only worked with my Android Smart Phone (don't know why)
The installation worked too!
Test with the phone i can do in 2 hours

I tried to recover the phone
Possible with instructions
Bricked 950XL
Hi, It seem my 950 is dead brick, when I plug it vibrate, then nothing. No light on sceen, no logo. At least windows seem to recognize an unknow device. To get it back, I tried to follow the tutorial on lumiafirmware website. thor2 -mode...
forum.xda-developers.com
but after the WDRT said... Waiting for reconnection the phone ist no shown anymore in the device manager.
I think now it is completely dead

mathewm said:
I tried to recover the phone
Possible with instructions
Bricked 950XL
Hi, It seem my 950 is dead brick, when I plug it vibrate, then nothing. No light on sceen, no logo. At least windows seem to recognize an unknow device. To get it back, I tried to follow the tutorial on lumiafirmware website. thor2 -mode...
forum.xda-developers.com
but after the WDRT said... Waiting for reconnection the phone ist no shown anymore in the device manager.
I think now it is completely dead
Click to expand...
Click to collapse
I think (I'm newbie in Windows mobile development) the phone has a sudden death at this point you can only recover the phone using programming tools or JTAG
Check again if you can enter to download or serial mode and reflash using the Thor2 method or with windows phone internals if not the phone needs to be recovered with JTAG method
This my opinion and can or can't be asserted (based I'm my experience with android phones I didn't see a hard brick on lumia devices)

Did you succeed or do you need further help?
Best regards, Joachim

Related

[Q] Botched UniversalAndroot Attempt - Am I screwed?

(Moved from development forum, newb root thread)
I recently received my phone back from a HTC repair. I hadn't used it til today as I was waiting for froyd 1.5 to come out before rooting it and setting it up. Today I switched it on and it asked me if I wanted to update the software, I clicked no. Then I followed the steps in the OP but had problems in step 5 : everytime I typed anything (including "su") and hit enter I had a message saying "denied" or words to that effect, despite the UniversalAndroot program giving the "woot rooted" message.
This is the part where I might have done something stupid - I decided to let the phone update itself to the latest software, and then I was planning to run the UniversalAndroot again. I thought that maybe UA had been tested on the latest official HTC stuff but not whatever 2.1 but not fully updated version that mine had come back from repair with. It went to the update screen and the progress bar completed, it tried to reboot but just got stuck on the white boot screen with the green HTC logo. If I pull the battery out and start again it just hangs at the same screen.
I can get the 2.73.405.5 WWE RUU to see the phone when in fastboot, but when I try to update it it eventually gives me error 140 "bootloader version error".
I tried to load it through HBOOT using kazuni's technique in his thread "A way of flashing the RUU rom extract" (sorry, it won't let me paste a link to the actual thread) but it says "main version is older, update fail". Do I need to send it off to HTC again? I just got it back! Will they be able to tell what broke it and refuse to fix it?
Many many thanks
Try the 2.1 downgrade in my sig below.
Please could you explain "The recovery can be flashed via running 'runindos.bat'."? I assume I need to install this adb program that people keep mentioning?
Also what is the goal here? To upgrade my phone to 2.1 (which was already on from the HTC repair, the OTA update just said something about adding g-sensor calibration tool) to then root it or to downgrade my phone to 1.5 to root?
Many thanks!
Ah, just seen adb guide on villain forums. OK, I'll follow the guide to get adb installed, put your recovery files in the /tools folder, but then how exactly do I flash the recovery? Simply by typing runindos.bat in cmd whilst in the correct folder?
Ah, I see, I just run the batch file from your recovery download. Sorry for all the dumb questions! I ran this with my phone on fastboot usb but it said this :
adb server is out of date. killing...
* daemon started successfully *
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
"Files copied and permissions set, rebooting HTC Andriod 2.1"
"Your phone will now reboot into normal mode, then reboot into recovery mode. I
f it does not reboot the second time, wait 10 minutes and manually reboot and be
gin again."
error: device not found
As far as I can tell nothing happened on my phone. I assume my usb drivers are fine as the RUU was able to begin updating before it gave me the 140 version error. Any ideas?
It's the ADB drivers, what OS are you using?
I am using Windows 7. I thought i read that the latest version of htc sync had drivers fully compatible with win 7 and the RUU seems to see it fine once I selected 'my htc' drivers under adb in device manager. I am confused!
HairyBones said:
I am using Windows 7. I thought i read that the latest version of htc sync had drivers fully compatible with win 7 and the RUU seems to see it fine once I selected 'my htc' drivers under adb in device manager. I am confused!
Click to expand...
Click to collapse
You may want to build an XP workstation eitha virtual or physical. Don't be alarmed. Yes, the latest version of HTC Sync does contain the drivers. However, they some what don't work for majority of users. Sorry.
Just did a quick google - will http://www.microsoft.com/windows/virtual-pc/download.aspx work?
HairyBones said:
Just did a quick google - will http://www.microsoft.com/windows/virtual-pc/download.aspx work?
Click to expand...
Click to collapse
virtual box - http://www.virtualbox.org/
vmware player - http://www.vmware.com/products/player
Eek - I need to get an xp install disc and set it up like I was loading it onto an actual PC? The microsoft tool within win 7 definitely wouldn't work?
HairyBones said:
Eek - I need to get an xp install disc and set it up like I was loading it onto an actual PC? The microsoft tool within win 7 definitely wouldn't work?
Click to expand...
Click to collapse
Yeh, to install XP you will need an install disk, unless you download XP Trial version VHD. This is the trial version from Microsoft in virtual machine mode.
http://www.microsoft.com/downloads/...90-958F-4B64-B5F1-73D0A413C8EF&displaylang=en
Windows XP Mode with Windows Virtual PC, available for Windows 7 editions Professional, Enterprise, and Ultimate, provides a licensed virtual Windows XP Professional environment for compatibility with applications not compatible with Windows 7. Windows Virtual PC supports USB attachment, therefor supporting direct connection of USB devices to the virtual Windows XP environment.
For information and to download Windows XP Mode or Windows Virtual PC visit the product page microsoft.com/windows/virtual-pc/default.aspx
Brandon
Windows Outreach Team- IT Pro

Windows Phone Internals - Unlock bootloader, enable Root Access, create Custom ROM

I am proud to announce the immediate availability of Windows Phone Internals 1.0. This tool allows you to unlock the bootloader of selected Lumia Windows Phone models. After unlocking the bootloader, you can enable Root Access on the phone or create and flash Custom ROM's. I created two video's to demonstrate the features of the tool.
Root Access allows you to load your own homebrew software onto the phone with high privileges. Apps can escape from their sandboxes. The tool can also create backup-images of the phone and access the file-system in Mass Storage mode. The tool supports most versions of Windows Phone 8.1 and Windows 10 Mobile. For a complete list of supported phones and Operating Systems have a look at the Getting Started section of the tool.
The download package also contains an SDK, which helps you to easily access the filesystem and registry on the phone from your own homebrew app.
The tool, SDK and video's are available on my new website:
www.wpinternals.net
Update december 23rd:
Windows Phone Internals version 1.1 is released. It has a fix for the audio-issue when Root Access is enabled and it supports Root Access on the latest Windows 10 Mobile build 10.0.10586.36. You can find the new version of the tool in the Download section on wpinternals.net
It seems there were extra integrity checks for playing media. I fixed this for audio-playback. I will create a generic fix later, but this will work for now. If you already have Root Access and you experience the Audio-issue, just "Enable Root Access" again on the phone.
Update december 29th:
A small update this time. Changes in this version:
Compatibility improvement for Windows 7. In previous versions "Enable Root Access" could result in "Failed to enable Root Access on MainOS".
"Restore bootloader" now uses a different Flashing interface. Previously, when you restored the bootloader, you were forced to do a full flash afterwards. With this new method you can keep your current Windows Phone installation. Remember that you need to disable Root Access before you restore the bootloader.
Many small fixes and tweaks.
FAQ
If your question is not answered here, please watch my instruction video's and read the "Getting started" section in my tool. I spent a lot of time to explain everything. If you have more questions, they are probably already answered there.
Can we run Android on Lumia now?
Why people ask this is beyond me. If you want Android, buy an Android phone. If you still want it, it will be a big challenge. You can remove UEFI, EFIESP, MainOS and Data partitions and then add hboot and other Android partitions. But then you would still need Android drivers for the Lumia components.
Which Lumia's are supported by the tool?
Lumia 520, 521, 525, 620, 625, 720, 820, 920, 925, 928, 1020 and 1320 are supported. These bootloaders can be unlocked.
Which OS versions are supported?
For these OS versions Root Access can be enabled. To enable Root Access, the bootloader must be unlocked first.
8.10.12393.890
8.10.12397.895
8.10.14219.341
8.10.14226.359
8.10.14234.375
8.10.15116.125
8.10.15148.160
10.0.10512.1000
10.0.10536.1004
10.0.10549.4
10.0.10581.0
10.0.10586.11
10.0.10586.36
I will add support for new versions when they get released.
Why are other Lumia's not supported?
Other Lumia's have different CPU architectures. And these come with different bootloaders. Some of my hacks depend on the implementation of these bootloaders. Some of my hacks won't work on different bootloaders. I need to find new hacks for these bootloaders. I will try that, but I can't predict when that is ready. The tool has implemented all the basics. So adding new hacks will be easier.
Why are other brands not supported?
Same reason. Some hacks work different. I will try to add support for other brands. But I don't know when it is ready.
I need Emergency Flash Loaders. Where can I get them?
This search should yield relevant results:
https://www.google.com/search?q=%22lumia%22+%22emergency%22+%22hex%22
I need an Engineering SBL3. Where can I get it?
This search should yield relevant results:
https://www.google.com/search?q=%22engineering+sbl3s%22
You can download a full Engineering ROM or a separate SBL3 file. If you select an FFU file in the tool, the tool will extract the SBL3 from the FFU. SBL3 contains hardware-profiles of the phone and it initializes the hardware. Therefore you should only use an alternative SBL3 if it came from a phone that is at least the same brand and CPU architecture as your phone.
I can't find a matching Engineering SBL3. Can I still unlock my phone?
Yes. The alternative SBL3 is optional. You can still unlock your bootloader and flash Custom ROM's. But you will not have Mass Storage Mode. So you won't be able to enable Root Access directly on the phone or make a full backup-image of the phone. But you can still flash Custom ROM's and enable Root Access on the Custom ROM's. Use the second method from my "Unlock" video.
I unlocked my phone and now my audio is gone. Why?
This is an issue with Root Access in Windows Phone Internals 1.0. Update to Windows Phone Internals 1.1 and then choose "Enable Root Access" again.
Can I SIM-unlock my phone with this tool?
No. SIM-unlock is illegal in some countries. I don't support SIM-unlock.
Reserved (2)
* Reserved **
Great job @Heathcliff74! The king is back!
Simply amazing! Made a donation to honour your work! Hope other devs use this to push the bounderies of the os!
@Heathcliff74 THX, you are amazing :good: I'll be waiting for support other models (eg X3X series).
Awesome stuff, can't wait to see the potential fruits of this development! Thanks @Heathcliff74
Is possibile to change Lumia PRODUCT CODE too?
Thanks
super big news
Thank you very much my friend
good job but where the find flashing loder .i have ffu of my phone..
is it possible to unlock bootloader in windows 10 mobile.?? i have lumia 525 which is supported but i don't have ffu for windows 10 mobile..if i flash my phone with wp8 ffu ,the is it possible to update my phone to w10 mobile.??need a reply..
A AJAY said:
good job but where the find flashing loder .i have ffu of my phone..
Click to expand...
Click to collapse
Riyad_ said:
is it possible to unlock bootloader in windows 10 mobile.?? i have lumia 525 which is supported but i don't have ffu for windows 10 mobile..if i flash my phone with wp8 ffu ,the is it possible to update my phone to w10 mobile.??need a reply..
Click to expand...
Click to collapse
Download the tool, go to the "Getting started" and read thoroughly. These questions are answered there.
@Riyad_ , the short answer is: Yes, it is possible to update and to Windows 10 Mobile and unlock it. Follow the instructions.
@Riyad_ , the short answer is: Yes, it is possible to update and to Windows 10 Mobile and unlock it. Follow the instructions.[/QUOTE]
ya found my answer. but i have another question. im in now w10m build 10586.if i unlock bootloader then i update my phone to new w10m build(after release) ,the bootloader unlock will remain or not.??
N.B. - in the app u said to disable auto update in phone that's why i m asking.thanks..
thanks heathcliff. great work. :good:
Very very nice Cliff
Error when trying to open the website
Parse error: syntax error, unexpected T_STRING in /home/deb56898n2/domains/wpinternals.net/public_html/templates/jsn_metro_free/template.defines.php on line 19
Click to expand...
Click to collapse
Would this make dualbooting Windows 10 Mobile and Android possible on Lumia ?
i think i found a "bug". i am using an lumia 1020 with the newest windows 10 mobile build. the lumia 1020 is at&t branded and sim unlocked, but your software says under phone - info that the sim is stock locked. also i dont think the bootloader unlock or the flash of a custom firmware will with an an branded phone or does it now ?
also, it isnt really important, but you should in your software under getting started maybe link the "windows device recovery tool" instead of the abandoned "lumia software recovery tool". anotherthing: windows startscreen gives me a warning if i start the programm as the publisher of the tool is unknown and chrome warns me too that the downloaded archive from your website could probably be a virus.
other than that: awesome. thanks
Finally! Thank you very much!
Does this mean Android on Lumia coming soon?

Nokia Lumia 520 Rm-915 QHSUSB_DLOAD stuck

Please Help me
My nokia lumia 520 is dead in QHSUSB_DLOAD?
Pc/ device manager/other devices show me ?QHSUSB_DLOAD
Help meeee
fix the QHSUSB_DLOAD brick
I had this the other day but I got it fixed that is if you can still access flash mode (red screen with giant nokia logo)
1. press VOL - and POWER for 10 seconds
2. go to the cellomania website just type in on google "cellomania ffu downloader", click on the first link witch has a pixelated C as its icon next to the website name put in your product code it should be 059XXXX
3. download all required files such as XXXX.pcx or XXXX.XXXX.XXXXX.ffu
4. download nokia care suite its easy to find just type it in on google and it should appear
5. once nokia care suite has installed go to C:\ProgramData\Nokia\Packages\Products\RM-915 and put all files in there
6. then open product support tool for store then click work offline because as it saved locally you don't need a wifi connection
7. then click open product
8. type in RM-915 my code is RM-935 so mine is a nokia Lumia 625
9. go into programming --> recovery
10. then click your firmware files that you saved into that folder
11. it will say that it lost connection press VOL - while you plug the usb in
12. it will say it is just flashing the VPL file but in actual fact its flashing all the files
12. and finally it will say recovery completed
13. and your phone should come up with the language selection after 5 or 10 minutes
my cell phone is dead
It does not turn on, is dead
I want to umbrick with the method without tjag but i have error
-- GPT ENDs --
Can help me fix the error?
Sending OPEN_MULTI_REQ
Received valid response to OPEN_MULTI_REQ
Checking eMMC read / write test results...
Failed to read number of eMMC sectors. eMMC is not working!!
ALPHA EMERGENCY FLASH END
Emergency messaging closed successfully
Operation took about 12.00 seconds.
Unknown error code.
THOR2 1.8.2.18 exited with error code 85035 (0x14C2B)
@ feherneoh thanks...
This problem is strange
Because my phone never dropped and used the method in two lumias 520 but show me the same Error
Was running the OS the build windows 10 mobile 10586 insider
The battery was discharged and never turned on
feherneoh:
When I connect the phone to the computer
I quickly see a green color icons connected
QHSUSB DLOAD toolkit conectivity emergency
I use windows 10 But i don't know if the are the corrects drivers to windows 10
I'm at work now
I do not remember very well but my phone is recognized immediately when connecting to the pc
feherneoh said:
In this case the reason for immediately going into emergency mode is probably that the bootrom of the SoC cannot read the eMMC. You cannot do anything without some professional tools and luck.
Click to expand...
Click to collapse
Thank you so much..
Fight for a week with this phone
And with your answer I will not fight any more
The strange thing is that I try with
2 lumias 520 and none returned to life
Please close this topic...
Ive bricked my nokia lumia 520 while trying to unlock the bootloader:
the way i did it was
Going into C:/Program Files/Microsoft Care Suite/Windows Phone Recovery Tool
and generating GPT0.bin (this file is very important)
You can generate your GPT0.bin file by inserting
Thor2 -mode ffureader C:/example directory/myfile.ffu -dump_gpt C:/example directory
and getting the right .hex file corresponding to the RKH (root key hash) you can get your RKH by booting into flash mode, opening windows phone internals,going to the info tab and finding the really long string of letters and numbers because thats your RKH
Then going into the MPRG_HEX.zip (you can find it with a quick google search)
Rename the correct hex file with your RKH to hex.hex
Then going back into command prompt and inserting
thor2 -mode emergency -hexfile C:/example/hex.hex -mbnfile C:/example/GPT0.bin -orig_gpt
Then it should take a few seconds
DO NOT REMOVE PHONE UNTIL TOLD TO!!!!!!
Then remove phone, take out the battery, insert battery and turn on the phone, you should hear a vibration and it should boot into nokia flash mode and you can go ahead and flash the ffu by:
Thor2 -mode uefiflash -ffu C:/example/flashy.ffu
Replace the example directory with your real directory
Wait 20 minutes and your phone should be fully operational
You just revived your lumia from death!

Lumia 950 boot loop

Hello.
My Lumia 950 dual sim went into boot loop and can't start. It shows Microsoft logo, then blue windows, vibrate once and again Microsoft logo. I tried key combination to hard reset - didn't work.
Then I tried with Windows Device Recovery Tool - it finished instalation, but nothing.
With Windows Phone Image Designer I flashed some ffu file for my phone - also nothing.
Does anyone have some idea how can I recover my phone.
Thanks in advance.
I had a similar problem with my 950XL when it installed a bad ROM sent out by Windows Insiders. After the 10th try or so with the Windows Device Recovery Tool the phone finally took it and I was back in business. If you are still having a problem you could try repeating the method several times. I did it as I had few resources available to me at the time, but it worked.
Thanks for reply.
I tried several times with WDRT, but today I'll keep trying.
Ya, keep trying, as I said it took me at least 10 tries to get it. After each fail I would start the next attempt without stopping. Anyway, good luck with this. They are still nice phones to carry around.
rlydiard said:
Ya, keep trying, as I said it took me at least 10 tries to get it. After each fail I would start the next attempt without stopping. Anyway, good luck with this. They are still nice phones to carry around.
Click to expand...
Click to collapse
I spent many hours trying to get my device to fully load into Windows. Eventually, I removed the USB cable (I had been repeatedly trying to solve the issue using the Windows Device Recovery tool), and removed my SD card and my SIM card from the device. To my surprise, soon after I attached the battery and replaced the back cover, the device rebooted and entered the Windows language configuration screen. True, I had to reconfigure many settings, and there was also a problem in restoring from the online backup, but it does seem to work, although I have yet to power down and re-attach the SD card and SIM.
When I went into Phone update I could see that there are updates available - Windows 10 Mobile (10.0.14393.1066). I am hesitant to allow this to download in case it was this update which caused the issue previously.
Do any of you have this update already installed? Is it responsible for the issue we are discussing?
I just checked once again the information shown by the Windows Device Recovery tool. This is what it shows:
Model: Lumia 950 Dual SIM
Firmware version: 01078.00053.16236.35022
Operating system version: 10586.13169
I am rather confused - it says that this is the same version available on the server, and that I have the latest version, yet Windows informs me that Windows 10 Mobile (10.0.14393.1066) is available for download?????
Also, can anyone please tell me where to find the ROM downloaded by the Windows Device Recovery tool in Windows 10x64? I think it might be useful to have this stored as a ROM backup on another drive, in addition to the fact that being quite a large file it is presently taking up far too much space on my C: drive, so I would like to be able to delete it once I have backed it up to another drive.
Thank you.
David
truth57 said:
Also, can anyone please tell me where to find the ROM downloaded by the Windows Device Recovery tool in Windows 10x64? I think it might be useful to have this stored as a ROM backup on another drive, in addition to the fact that being quite a large file it is presently taking up far too much space on my C: drive, so I would like to be able to delete it once I have backed it up to another drive.
Thank you.
David
Click to expand...
Click to collapse
There you go.. Follow this and read through it..
https://forum.xda-developers.com/showthread.php?t=2515453
THis is NOT my guide
Good luck

[Solved!] MSM Download Tool Issues - Sahara Communication failed, phone exits EDL

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!
Glad you got it sorted and left some feedback! cheers
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
Hi crispy-cat,
Looks I have the same problem as you did. Using Kubuntu and Windows10 in VirtualBox.
My device is not recognized when I boot into edl-mode so I can't use MSM to unbrick my device. It does not pop up in devicemanager when I connect it with the original usb cable.
Can you explain the set up of a USB 2 controller? What is it hardware or software? I am not familiar to this and don't understand what you did. I think this can help me figuring out how to get the MSM tool working for me and flash the original OS back to the device.
Unfortunately I don't have access to a windows computer.
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.
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
Thanx crispy-cat,
I now understand what you mean. My V-Box is broken and won't start up anymore so it's time to try out the alternatives or install V-Box again ;-)
If those options won't work I think the best solution is to buy Windows10 and install this on the computer. What are your ideas about the last option crispy-cat?
SakasakaHeyhey said:
Thanx crispy-cat,
I now understand what you mean. My V-Box is broken and won't start up anymore so it's time to try out the alternatives or install V-Box again ;-)
If those options won't work I think the best solution is to buy Windows10 and install this on the computer. What are your ideas about the last option crispy-cat?
Click to expand...
Click to collapse
Don't waste your money. Just download the ISO from here:
Download Windows 10 Disc Image (ISO File)
If your computer supports multiple SSDs, find one that works in it, and install it in the second slot. Otherwise, find the cheapest SSD you can that works and install it on there.
The reason I say to install on a separate disk is because resizing partitions can corrupt your data and make your computer unbootable, and Windows doesn't provide an option to install alongside your existing OS. By all means do not get rid of your existing OS.
crispy-cat said:
Don't waste your money. Just download the ISO from here:
Download Windows 10 Disc Image (ISO File)
If your computer supports multiple SSDs, find one that works in it, and install it in the second slot. Otherwise, find the cheapest SSD you can that works and install it on there.
The reason I say to install on a separate disk is because resizing partitions can corrupt your data and make your computer unbootable, and Windows doesn't provide an option to install alongside your existing OS. By all means do not get rid of your existing OS.
Click to expand...
Click to collapse
Hi crispy-cat,
Thanx for your advise and the link. I have a laptop with one SSD in it and there is no room for a second SSD.
I have external harddisks I use for storage (no SSD) and was thinking what is the best option for me:
1) Buy an external SSD for Windows. I am wondering if and how this will work. The OS on the laptop is Kubuntu. I can change the boot option in the Bios and select the SSD. Because the OS is on the SSD and not on the laptop do I have access to the USB ports on the laptop via Windows which runs on the SSD? The purpose is to connect the bricked phone to one of the USB ports and use the MSM tool to unbrick my device.
2) Buy a USB flash drive and write the ISO from your link to the flashdrive. Install Windows on the laptop via the flashdrive. This will overwrite the current OS. When I can unlock my phone in Windows with the MSM tool I can install Kubuntu back again on the laptop.
It is no problem for me to change the OS because I don't lose any files. Everything I need is on the external harddisks.
What are your ideas about this and is there another option available that could work for me?
Dualboot with Windows/Kubuntu is a alternatieve but can also be tricky.
SakasakaHeyhey said:
Hi crispy-cat,
Thanx for your advise and the link. I have a laptop with one SSD in it and there is no room for a second SSD.
I have external harddisks I use for storage (no SSD) and was thinking what is the best option for me:
1) Buy an external SSD for Windows. I am wondering if and how this will work. The OS on the laptop is Kubuntu. I can change the boot option in the Bios and select the SSD. Because the OS is on the SSD and not on the laptop do I have access to the USB ports on the laptop via Windows which runs on the SSD? The purpose is to connect the bricked phone to one of the USB ports and use the MSM tool to unbrick my device.
2) Buy a USB flash drive and write the ISO from your link to the flashdrive. Install Windows on the laptop via the flashdrive. This will overwrite the current OS. When I can unlock my phone in Windows with the MSM tool I can install Kubuntu back again on the laptop.
It is no problem for me to change the OS because I don't lose any files. Everything I need is on the external harddisks.
What are your ideas about this and is there another option available that could work for me?
Dualboot with Windows/Kubuntu is a alternatieve but can also be tricky.
Click to expand...
Click to collapse
External SSDs are generally rejected by Windows and you'd have to do some very complicated setup. If it's no big deal to reinstall Kubuntu, go with option 2. Just disconnect the drives your files are on before you install Windows.
crispy-cat said:
External SSDs are generally rejected by Windows and you'd have to do some very complicated setup. If it's no big deal to reinstall Kubuntu, go with option 2. Just disconnect the drives your files are on before you install Windows.
Click to expand...
Click to collapse
Thanks for your help friend.
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
In msm tool its showing sahara communication problom..
Please help me
Nafih424 said:
In msm tool its showing sahara communication problom..
Please help me
Click to expand...
Click to collapse
Are you using the cable that came with the phone?
crispy-cat said:
Are you using the cable that came with the phone?
Click to expand...
Click to collapse
Yes same cable.
I'm not sure what's wrong then, sorry. Maybe someone who knows more about this can help.
Hello, having same problem here.
I have a Op 6T and after trying to install twrp as a system app, it kept me boot-failing twrp over and over again with screen flashing then immediately shutting down, now my phone is unable to boot with volume and power button, and I can't even see it with fastboot command, even though my desktop sees it..
Same issue. was someone able to resolve this?
I got my OnePlus 7 to be seen on virtualbox but driver shows exclamation mark on guest windows 10 OS.
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
Hello
I had the same issue now and don't have alternative laptop.
any solution to fix within the same laptop?
Thanks
Ak24607 said:
Hello
I had the same issue now and don't have alternative laptop.
any solution to fix within the same laptop?
Thanks
Click to expand...
Click to collapse
I had this issue before. You need to try a different cable/USB port.
FIX - PRESS (VOLUME+) + (VOLUME -) and connect the phone in EDL mode.
When you get the error, DONT DISCONNECT!!!!!!!!
Just PRess (VOLUME+) + Power Button and hold for few seconds.
IT DOES THE WORK!!!!!
yash.raj022 said:
FIX - PRESS (VOLUME+) + (VOLUME -) and connect the phone in EDL mode.
When you get the error, DONT DISCONNECT!!!!!!!!
Just PRess (VOLUME+) + Power Button and hold for few seconds.
IT DOES THE WORK!!!!!
Click to expand...
Click to collapse
I am using my Mac, and having windows using parallers. My device is getting detected in EDL. MSM shows that it's connected. But after 16s it says Sahara connection Failed. I was on siberia OS 12, wanted to revert back, and messed it up. Now the device doesn't boot up, can't access the fastboot as well - FASTBOOT is frozen.
Any help here would be great, else I might have to get a new phone

Categories

Resources