Related
I can't install Windows 10 Technical Preview on my Samsung RV509 laptop (Core i5 and 6Gigs of RAM). I tried doing a clean install, and once I boot from the flash stick It gets stuck on the Windows logo and the loading dots doesn't appear, so I tried to do an upgrade from Windows 7 and once it restarts it gets stuck on the windows logo and doesn't load after that (I tried both 32 and 64bit versions) then i get the error 0xC1900101-0x20017. So I tried to install it inside a virtual machine and i tried another machine,and it did install just fine. I tried everything I can from trying to launch the setup from the command prompt but still once it restarts it gets stuck on the windows logo. I'm not sure what do I need to do to get it to install and boot. I've tried with every single build since the insider program started till 9926.
I would really appreciate any help in this matter. Thank you.
I think you didn't really tried a clean install, since you wrote that you've tried to upgrade later. Clean install means you erase all traces of previous system installation. Also, it's good to delete all partitions. Maybe you're hard disk is MBR formatted and Windows 10 requires GPT (just a suggestion, I'm not sure about that).
Secondly, are you trying an UEFI install? I've had Win10 for a couple of months now but I remember having problems with starting UEFI installation from USB stick. To do this, you have to change partition layout on usb stick to GPT, then make new primary partition, format it to FAT32 and copy all files from install iso to usb stick. Then you can start your install in UEFI mode and I think this will help you. Just remember to delete all partitions and let Windows create new partition layout for you, this way it will create EFI partition.
If the installer says it can't create partitions in UEFI mode, you will have to change partition layout to GPT by yourselft. You can put your hdd in a PC and use a Windows based tool (search google) or maybe some Linux LiveCD will let you do that without removing your hdd.
All I did was just use demon tools and install over my w7. It installed as Uefi. Don't like it and w10 gave me an option on restart to roll back my system. I did and went back to w7.
You shouldn't use Daemon Tools to install Windows from an ISO. If Windows needs to reference a file inside the Install.wim folder on the disc for any reason, that copy will fail as the disc it's using is not a physical disc, but a virtual one that the new installation has no knowledge of. The best way to install Windows from an ISO is to copy the ISO to a flash drive or to the local hard disk and run setup that way, or use Rufus to create a bootable USB media for installing. That could be related to your error codes.
Thank you sanshinron for your reply. I always do a clean install for windows, the only reason that i tried to upgrade is that the setup didn't even load when booting from a USB stick (stuck on the windows logo). The USB stick was created using Microsoft's "Windows 7 USB DVD Download Tool". The same stick loads fine on other PCs. I will try to do what you suggested with the USB stick and give it another try.
sanshinron said:
I think you didn't really tried a clean install, since you wrote that you've tried to upgrade later. Clean install means you erase all traces of previous system installation. Also, it's good to delete all partitions. Maybe you're hard disk is MBR formatted and Windows 10 requires GPT (just a suggestion, I'm not sure about that).
Secondly, are you trying an UEFI install? I've had Win10 for a couple of months now but I remember having problems with starting UEFI installation from USB stick. To do this, you have to change partition layout on usb stick to GPT, then make new primary partition, format it to FAT32 and copy all files from install iso to usb stick. Then you can start your install in UEFI mode and I think this will help you. Just remember to delete all partitions and let Windows create new partition layout for you, this way it will create EFI partition.
If the installer says it can't create partitions in UEFI mode, you will have to change partition layout to GPT by yourselft. You can put your hdd in a PC and use a Windows based tool (search google) or maybe some Linux LiveCD will let you do that without removing your hdd.
Click to expand...
Click to collapse
try https://rufus.akeo.ie/ for the usb install
onebyside said:
try https://rufus.akeo.ie/ for the usb install
Click to expand...
Click to collapse
I tried both Rufus and ISO2Disk to make the USB stick GPT, but still i'm having the same issue with the setup not loading.
toulan said:
I tried both Rufus and ISO2Disk to make the USB stick GPT, but still i'm having the same issue with the setup not loading.
Click to expand...
Click to collapse
I installed UEFI without a problem, is there a reason your set on GPT?
I tried everything with the USB drive and it just installs fine on other pcs. I guess this could be because of hardware not supported yet by Microsoft in the current windows 10 builds. I found many people having the same issue. I just hoped there could be a fix to get the installer to start
I encountered same boot-hang problem when clean installing Win 8.1, and Win 10 shouldn't be different. My solutions:
Post-install boot-hang: The hang at logo boot happens when I don't format the install-to partitition with Win 8.1 installer (I normally partition/format using another tool, to skip the redundant WinRE partition that Win creates). Formatting with the installer allows the boot to complete (you can still keep the original partitioning).
Pre-install boot-hang: Some PCs are idiosyncratic with USB boot; likewise, some USB sticks are "different" from others. I found that using DiskPart to partition & format the USB stick (like a HDD) works when Rufus & straight formatting wouldn't. This, admittedly from a small sample set of one particular problematic combo. Simpler is just try to use different USB sticks.
toulan said:
then i get the error 0xC1900101-0x20017
Click to expand...
Click to collapse
This error indicates an update issue.
Try this:
- Ingersoll mini tool partition wizard
- check your disk type
If it's GPT,
- download minitool portable ISO and burn on USB with UUI.
- boot to the application and convert GPT to MBR
- Format the C: partition or wherever the previous windows was installed
- then overwrite it with win10
If it's UEFI change it from the bios. Turn off secure boot and everything.
Try and let me know.
Is there Windows 10 for Nokia Lumia 625?
Tiash420 said:
This error indicates an update issue.
Try this:
- Ingersoll mini tool partition wizard
- check your disk type
If it's GPT,
- download minitool portable ISO and burn on USB with UUI.
- boot to the application and convert GPT to MBR
- Format the C: partition or wherever the previous windows was installed
- then overwrite it with win10
If it's UEFI change it from the bios. Turn off secure boot and everything.
Try and let me know.
Click to expand...
Click to collapse
After using the minitool partition wizard i found out that it was already MBR.
feherneoh said:
Does that pc have Win8.1 installed with UEFI?
If so, connect installer drive, go to shutdown menu, hold shift, press restart
Then select Use device => UEFI USB
Click to expand...
Click to collapse
Tried it, but still the same issue.
Then turn off safe boot and try format the whole disk and start Windows installation from scratch?
Only if you want Windows 10 badly and are ready to sacrifice your data.
Caution: This 'might' work. No guarantees.
Tiash420 said:
Then turn off safe boot and try format the whole disk and start Windows installation from scratch?
Only if you want Windows 10 badly and are ready to sacrifice your data.
Caution: This 'might' work. No guarantees.
Click to expand...
Click to collapse
Tried it, but it didn't work. I think this could be an issue with a hardware that is not supported yet by the preview. I guess i'll have to wait for that to change in next builds.
toulan said:
Tried it, but it didn't work. I think this could be an issue with a hardware that is not supported yet by the preview. I guess i'll have to wait for that to change in next builds.
Click to expand...
Click to collapse
That might be it cause it's a preview and they sure are known for this kinda issue
Tried build 10041 and still same issue.
toulan said:
Tried build 10041 and still same issue.
Click to expand...
Click to collapse
My Laptop is SAMSUNG RV509 but with intel core i3 1st Generation and 2 GB of RAM inside
And I have the same problem with you when trying to install Windows 10 Technical Preview even with it's latest version just like you, get stuck at begin of instalation process, Windows logo appear without any waiting animation (circle of dots), and nothing happen after that.
Just like you, I'm trying install it so many time and so many way such as update latest version of BIOS, but nothing change.
So, if you have a solution for our laptop, please take your time to guide me.
"Sorry if any inconvenience come to your attention with my English writing skill"
shinstar123 said:
My Laptop is SAMSUNG RV509 but with intel core i3 1st Generation and 2 GB of RAM inside
And I have the same problem with you when trying to install Windows 10 Technical Preview even with it's latest version just like you, get stuck at begin of instalation process, Windows logo appear without any waiting animation (circle of dots), and nothing happen after that.
Just like you, I'm trying install it so many time and so many way such as update latest version of BIOS, but nothing change.
So, if you have a solution for our laptop, please take your time to guide me.
"Sorry if any inconvenience come to your attention with my English writing skill"
Click to expand...
Click to collapse
Of course, once i find a solution i will post it here, so far no luck.
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.
Today I tried to install windows 10 in my lenovo laptop. When installation process going on my pc restart with white screen. I can't able to go to boot menu, safe mode.
Any help
sheikalthaf said:
Today I tried to install windows 10 in my lenovo laptop. When installation process going on my pc restart with white screen. I can't able to go to boot menu, safe mode.
Any help
Click to expand...
Click to collapse
If you have a USB stick (~4GB) and access to a second computer then you could create a Windows 10 USB installation medium with Microsofts Media Creation Tool (please Google it, can't post links yet)
After that you can boot from the Windows 10 USB Stick and select the repair options, either that works or you simply make a fresh install with it. Be aware that you may lose your files on your laptop!
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,
On jan 2021 I've installed windows 10 cracked version in my hp laptop. Later than i got issue during use of dev apps. Now I want to switch back to official version of windows 10.
I've created windows 10 bootable usb from media creation tool. But I'm not able to boot it. I pressed F9 key and select usb on boot option than my pc stuck on hp logo in boot loop.
I also tried to reset but got an error (no recovery environment) also tried to advance startup got no reset option there. Please find the bios setting and error images as attachment.
Thanks for help in advance.
Nikhilll_mishra said:
Hey guys,
On jan 2021 I've installed windows 10 cracked version in my hp laptop. Later than i got issue during use of dev apps. Now I want to switch back to official version of windows 10.
I've created windows 10 bootable usb from media creation tool. But I'm not able to boot it. I pressed F9 key and select usb on boot option than my pc stuck on hp logo in boot loop.
I also tried to reset but got an error (no recovery environment) also tried to advance startup got no reset option there. Please find the bios setting and error images as attachment.
Thanks for help in advance.
Click to expand...
Click to collapse
i think you are using a bad program for making a bootable iso.the best program i think its rufus-1.3.4 for making a bootable iso win10 or win7 i will attached it here for you.i hope it will help.
just unzip the file and run the program after you insert your usb drive or sdcard
If the BIOS is well set and the flashable USB is ok (Rufus or Media Creation Tool -> follow online guides) turn poweron the notebook and by pressing F9 with the pendrive inserted select the last option "USB Hard Drive - SanDisk Cruzer Blade" than the Windows 10 logo should appear immediatly, and than the Win 10 installation menu.
Download the latest version of the BIOS and UEFI firmware on your PC, and unplug all the other USB drives connected to the device.
Will on windows, open pendrive and execute setup.exe. Check if start.