Related
So after flashing the new lollipop update I found myself stuck in a bootloop unable to get into the android operating system at all. I used flashboot and the intel flash tool to try and restore to an older ROM. It forze at 91% with an "error:unable to mount /data" I then used the root tool to try and sideload and install the update.zip from adb shell. No luck. When I rebooted I got to a strange efi menu. Looked around, and it gives me the option to install with with windows?
Anyone have any ideas. I'm waiting for radio shack to open, its the only local place that sells USB otg cables locally.
Here are the photos
njking25 said:
Here are the photos
Click to expand...
Click to collapse
njking25 said:
So after flashing the new lollipop update I found myself stuck in a bootloop unable to get into the android operating system at all. I used flashboot and the intel flash tool to try and restore to an older ROM. It forze at 91% with an "error:unable to mount /data" I then used the root tool to try and sideload and install the update.zip from adb shell. No luck. When I rebooted I got to a strange efi menu. Looked around, and it gives me the option to install with with windows?
Anyone have any ideas. I'm waiting for radio shack to open, its the only local place that sells USB otg cables locally.
Click to expand...
Click to collapse
That is something interesting. It is asking which os to boot to, not install.
I'd like to know how you got into the bios? I am looking for a way to install Linux....
Sent from my YOGA Tablet 2-1050F using Tapatalk
njking25 said:
Here are the photos
Click to expand...
Click to collapse
Did you get this figured out?
I can see "fast boot" enabled. Have You tried to switch it off? any other menu is displayed?
Have You tried to "power+vol down" on it?
I've tried a few ways to get into the BIOS shown... all failed.
Maybe the only way to trigger the BIOS to show is to fully wipe/format the internal storage so the BIOS can't pick up droidboot or anything else. Quite risky though if it isn't the way.
I'm in no way telling anyone to do this and I have not tried it myself. I'd be curious to hear from any advanced users if they have ever completely wiped the internal memory and what options would be available to restore if things did go wrong.
zach181 said:
I've tried a few ways to get into the BIOS shown... all failed.
Maybe the only way to trigger the BIOS to show is to fully wipe/format the internal storage so the BIOS can't pick up droidboot or anything else. Quite risky though if it isn't the way.
I'm in no way telling anyone to do this and I have not tried it myself. I'd be curious to hear from any advanced users if they have ever completely wiped the internal memory and what options would be available to restore if things did go wrong.
Click to expand...
Click to collapse
This guy seems to have stumbled on it also. I flashed the stock kk firmware and I am trying to do it but can't get Lollipop update to work. But it won't boot after it fails so I am reflashing KK again.
http://forum.xda-developers.com/showpost.php?p=60490907&postcount=578
Thanks for the link workdowg,
I'm still trying to work out how they did it. Could do with a step by step and whatever files needed uploaded and linked to. Also the bit about not using windows startup programs.
zach181 said:
Thanks for the link workdowg,
I'm still trying to work out how they did it. Could do with a step by step and whatever files needed uploaded and linked to. Also the bit about not using windows startup programs.
Click to expand...
Click to collapse
If you try it do let me know. I need to get into the bios to get started on a dual boot to Linux on this bad boy...
I will let you know.
I just asked for the OP to clarify a few things before I go ahead. I may try Linux first with Windows 8/10 being the final install.
So... conclusion. we have to damage firmware to boot efi...
If we could swap img file before upload to tab (during this 25 second wait) we could make windows installation possible. Am i right?
zach181 said:
I will let you know.
I just asked for the OP to clarify a few things before I go ahead. I may try Linux first with Windows 8/10 being the final install.
Click to expand...
Click to collapse
@social-design-concepts suggested we should try to change the boot order using efibootmgr. I've been communicating with him. Here is the post in the Venue thread... http://forum.xda-developers.com/show...postcount=2083
Links giving 404
zach181 said:
Links giving 404
Click to expand...
Click to collapse
here it is again... http://forum.xda-developers.com/showpost.php?p=61108700&postcount=2083 it got truncated.
Thanks workdowg.
It seems it's not as clear cut as first thought. Mind you, I didn't expect it to be. I did try a HP keyboard with OTG in Android and that got picked up ok (No lights on keyboard)
I'm a bit in the same mind as Social-Design. I'd rather have a definite way to restore Android from a totally blank internal drive before I have a go. Just up to page 214 in the thread so it may be covered later.
UEFI soft brick?
Hi guys,
I accidentely tried to use the firmware on my 1050 as described in this thread. I can indeed load the UEFI BIOS with all its settings (even though most don't do anything). But unfortunately, I cannot load any OS. I always get the error "EFI Harddrive failed" - meaning it cannot boot fomr hardrive.
I have used an externally powered USB-HUB with mouse, keyboard and USB-Stick and connected to the 1050 via OTG-cable. If the stick is bootabnle with GPT x64 then it will boot from that stick. All 64bit windows versions that I tried failed to install with "ACPI_BIOS_ERROR". 32bit windows would not start, because the GPT is 32bit and the BIOS does not recognise it.
The best success I had so far was to copy a ISO from android-x86 on the usb stick. It will boot in live-mode from the USB. Not so suprisignly, mouse and keyboard are working, touch isn't. WiFI is working and the SD card is detected. I tried to install this version of android on the harddrive which works, but it installs the EFI GRUB bootloader which is not recognised by the BIOS.
I can also access the UEFI shell.
Unfortunately, I am running a bit out of ideas of what to do in order to get a normal system (or firmware) back. ADB-drivers obviously don't work (the Intel SoC driver is installed as well), so I cannot use the Phone Flash Tool.
Any ideas would be greatly appreciated.
Yosha1 said:
Hi guys,
I accidentely tried to use the firmware on my 1050 as described in this thread. I can indeed load the UEFI BIOS with all its settings (even though most don't do anything). But unfortunately, I cannot load any OS. I always get the error "EFI Harddrive failed" - meaning it cannot boot fomr hardrive.
I have used an externally powered USB-HUB with mouse, keyboard and USB-Stick and connected to the 1050 via OTG-cable. If the stick is bootabnle with GPT x64 then it will boot from that stick. All 64bit windows versions that I tried failed to install with "ACPI_BIOS_ERROR". 32bit windows would not start, because the GPT is 32bit and the BIOS does not recognise it.
The best success I had so far was to copy a ISO from android-x86 on the usb stick. It will boot in live-mode from the USB. Not so suprisignly, mouse and keyboard are working, touch isn't. WiFI is working and the SD card is detected. I tried to install this version of android on the harddrive which works, but it installs the EFI GRUB bootloader which is not recognised by the BIOS.
I can also access the UEFI shell.
Unfortunately, I am running a bit out of ideas of what to do in order to get a normal system (or firmware) back. ADB-drivers obviously don't work (the Intel SoC driver is installed as well), so I cannot use the Phone Flash Tool.
Any ideas would be greatly appreciated.
Click to expand...
Click to collapse
You can get it to boot from USB? Get someone with to use tethered twrp and get a backup of the esp and fastboot partitions.
I have 2 things you can try if the goal is getting back to booting stock Android.
Yosha1 said:
The best success I had so far was to copy a ISO from android-x86 on the usb stick. It will boot in live-mode from the USB. Not so suprisignly, mouse and keyboard are working, touch isn't. WiFI is working and the SD card is detected. I tried to install this version of android on the harddrive which works, but it installs the EFI GRUB bootloader which is not recognised by the BIOS.
I can also access the UEFI shell.
Any ideas would be greatly appreciated.
Click to expand...
Click to collapse
Have You tried booting any x64 linux iso from flash drive?
dreamnewbie said:
Have You tried booting any x64 linux iso from flash drive?
Click to expand...
Click to collapse
Thank you for your fast reply.
I just tried that with an Ubuntu Desktop Distro. It boots up from teh USB drive, keyboard and mouse are present. Wifi, sound, touch don't work but I can see the internal Harddrive and the sdcard in the file exsplorer.
Yosha1 said:
Thank you for your fast reply.
I just tried that with an Ubuntu Desktop Distro. It boots up from teh USB drive, keyboard and mouse are present. Wifi, sound, touch don't work but I can see the internal Harddrive and the sdcard in the file exsplorer.
Click to expand...
Click to collapse
extract and dd this to a usb drive and see if it is able to boot it View attachment 3415895 if it successfully boots replace the fastboot.img thats on the thumbrive with one for your devices and see if it boots. if your fastboot.img is named droidboot.img rename it to fastboot.img.
If you can successfully get your devices droidboot/fastboot.img to load you can then disconnect the usb-otg cable and reconnect it to your PC and use the phone flash tools to restore your device completely.
I'm having an issue with file transfer where my computer can't 'see' the phone when an AOSP ROM is installed.
File transfer is fine when mounting in recovery, also when I have OOS installed, so it isn't a hardware problem.
I've gone through the forum searching for a solution, and I have:
Changed the default USB configuration (under Developer options) to MTP
Uninstalled the phone from Device Manager on my computer
Tried installing OnePlus drivers to my computer
Tried installing Qualcomm drivers to my computer
Can anyone suggest a solution? I'm desperate to get this sorted as I can't tolerate OOS any longer, I just want a cleanish build of Android with no OnePlus rubbish in it!
I join your quest man... Im looking for the solution for this problem since i have installed my first AOSP rom on OP5... Never find the solution, i'm curious for this too... Now im on PureFusion and MTP of course isnt working... so i use recovery for file transfer (which is annoying) or the WiFi server (which is slow and isnt "operations" friendly)
In the same time cant understand why my nexus 6p with PureNexus is fully working in MTP but the oneplus 5 nope
Hitman478™ said:
I join your quest man... Im looking for the solution for this problem since i have installed my first AOSP rom on OP5... Never find the solution, i'm curious for this too... Now im on PureFusion and MTP of course isnt working... so i use recovery for file transfer (which is annoying) or the WiFi server (which is slow and isnt "operations" friendly)
In the same time cant understand why my nexus 6p with PureNexus is fully working in MTP but the oneplus 5 nope
Click to expand...
Click to collapse
That's interesting. I'm transferring like 80% of my files trough MTP and it is and always was working fine, but I'm using Linux, so that might help you guys to solve it
siankatabg said:
That's interesting. I'm transferring like 80% of my files trough MTP and it is and always was working fine, but I'm using Linux, so that might help you guys to solve it
Click to expand...
Click to collapse
I know it's windows fault because when it have too many drivers to manage for the same thing it goes crazy.. but even removing every single driver (ADB and Android related) it doesn't work.. I'm looking in a solution on the Linux build called "forget windows use Linux" since I can't completely remove windows 10
I had same issue in Linux
Typically, issue is not the ROM
1) check the phone get set to "file transfer" when connected, you generally have option to chose
2) plugging to a usb in chain to other switches it was not work, connected directly to a usb MB port, worked.
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
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
Hey guys,
I build a new pc, first new build in 20 years.
I’m using an ASUs tug gaming x670e plus WiFi motherboard with and 7800x3d cpu.
I’m stuck with the windows installation from usb.
First attempt I used a SanDisk 8gb stick and windows media creator. That’s right load, but looking back that was probably because of bios settings.
second attempt I used a leef 16gb stick. Art the verify stage at 99% it failed.
Third attempt save stick same method created the usb successfully. Had to pay around a lot with bios settings to get the stick seen as bootable. But during the windows installation it reported a file inaccessible or missing. Soo I put the stick in another machine to check but the file in question was there.
Soo I tried again, but now it cannot start up from the usb stick.
I’m in progress of creating an iso usb using the 8gb SanDisk drive, but I think I’m missing something significant.
I’ve attached my bios settings for booting.
If anyone can give some clarification, that would be greatly appreciated! If I can’t die this tonight I’ll bring it in a shop this weekend (just for a windows installation, sigh)
This... happy hunting.
Make a cloned copy of the disk once loaded and configured but before adding data, antivirus or trashware with Acronis to a spare hdd for easy OS restore.
*Redundantly backup critical data, first*
Separate data drives + OS drive are best plus the backup drives that are physically and electronically isolated from each other and the PC.
Managed to get an install.
Had to change a few bios settings (apparently one of the videos I watched for the right bios settings was the exact opposite of what was needed). Agassi used an iso stick.
That seemed to do the trick.
Thanks for the suggestions. It’s much appreciated.
I managed to get things installed. My issues were a combination of bad luck with my usb drives (and how the bootable stick was generated), as well as some poor advice on YouTube that told me the opposite of what was needed.
I also had problems obtaining an activation key legally, but that got resolved as well, so I finally managed to get my pc up and running.
Thanks again for the suggestions!