Database Users

ROM Upgrade fails when ActiveSync disconnects

Boo Hoo ... I love my HTC-HD2, (despite all the grief HTC should have avoided inflicting on us), ... and so I was really looking forward to the 1.66 ROM Upgrade. BUT it won't load for me...
I downloaded the ROM ("GCC & Egypt" version out of Middle-East & Africa site - I'm an expat living in Dubai), connected my phone to my PC by USB & ActiveSync, ran the ROM.exe on my PC, carefully ticked and clicked my way through all the dialogue boxes and when I hit the last "next" button to launch the ROM upgrade, ActiveSync decides to disconnect leaving the phone hanging in the tri-clour bootloader mode and 10 seconds later, (with the connection dropped), I get Error [266] UPDATE ERROR (see attached screen shot).
Happily a quick restart after removing the battery restored the phone to its un-upgraded state. Thinking I may have tweaked something I shouldn't have on my phone (with loaded software, reg-edits and xda-tweaks), I hard reset it back to the original factory 1.43 ROM condition and retried the 1.66 Upgrade; but no go - same ActiveSync disconnection/bootloader hang. Tried again with firewall and virus protection turned off; and again on a different PC; and again and again holding my tongue in every conceivable different position - but no joy and now I have a bald patch from all the hair I pulled out.
I might just be thick and missed something, (though - as a last resort - I did read the instructions seven times), ... so I'm desperately seeking assistance. Any help would be greatly appreciated ... as I'm finding it difficult to suppress the rising anger and loathing I developing for Team HTC - who have now predisposed me to blame them for everything that goes wrong including global warming; - this is turning out to be pretty much like my relationship with all the old Landrovers I've owned - but I digress - can anyone suggest a solution or point out my error ... before I send the less than complimentary email I'm drafting to HTC, who will then have to blacklist me from buying the HD3 and then I won't have anything to complain about, (because my current Landrover Discovery 3 is uncharacteristically perfect !!).

That's because Windows needs an extra driver for the phone in bootloader mode. It is then no longer connected via Activesync.
Put your phone into bootloader mode, connect it to your PC, wait for the driver to install, then flash again (while the phone is in bootloader mode).

ROM Upgrade Utility / Phone connection problem persists
Thanks for the advice; but still have a problem.
PC connects and recognises the phone via USB connection in bootloader mode(so I assume driver has loaded properly) but ROM upgrade utility still stalls with error message saying "Update Utility cannot get response from your PDA Phone".
Several attempts to run Upgrade Utility while phone is in bootloader mode all fail; sometimes with no detection at but once or twice it manages to detect the phone but doesn't obtain any status info and ultimately fails to communicate properly, always ending up with the Error message noted.
Starting think I have a hardware problem ... oh no ... will have to deal with HTC Middle-East (which will mean numerous miscommunications, 3-4 week waits, phone being lost/misplaced, after 2-months being told there is actually no problem - must all be in my head ... think I'll just slash my wrists now and save the aggravation.)

eViking said:
Thanks for the advice; but still have a problem.
PC connects and recognises the phone via USB connection in bootloader mode(so I assume driver has loaded properly) but ROM upgrade utility still stalls with error message saying "Update Utility cannot get response from your PDA Phone".
Several attempts to run Upgrade Utility while phone is in bootloader mode all fail; sometimes with no detection at but once or twice it manages to detect the phone but doesn't obtain any status info and ultimately fails to communicate properly, always ending up with the Error message noted.
Starting think I have a hardware problem ... oh no ... will have to deal with HTC Middle-East (which will mean numerous miscommunications, 3-4 week waits, phone being lost/misplaced, after 2-months being told there is actually no problem - must all be in my head ... think I'll just slash my wrists now and save the aggravation.)
Click to expand...
Click to collapse
What version of Windows are you using? If you are using Windows Vista or Windows 7 64 bit you may need to install the required drivers by yourself, rather than automatically updating drivers.

Have tried on two systems:
1. Win XP (32bit version with Service pack 3) running as virtual machine in Parallels 5.0 on an iMac OS 10.6 (snow leopard) - yes I've ventured out of the shadows into the light.
and
2. Win XP (32bit version with Service pack 3) running on a standard PC
Both seem to connect, bootloader on phone shows "USB" and under Control Panel/System/Device Manager the HTC Device shows as a USB Root Hub device "working properly" ???

eViking said:
Have tried on two systems:
1. Win XP (32bit version with Service pack 3) running as virtual machine in Parallels 5.0 on an iMac OS 10.6 (snow leopard) - yes I've ventured out of the shadows into the light.
and
2. Win XP (32bit version with Service pack 3) running on a standard PC
Both seem to connect, bootloader on phone shows "USB" and under Control Panel/System/Device Manager the HTC Device shows as a USB Root Hub device "working properly" ???
Click to expand...
Click to collapse
Strange. I guess you have tried using different USB ports, and not using a USB hub port. Are you using the stock USB cable that came with your HD2?
You might also try flashing a ROM with your storage card. That should bypass your USB problem. You can find instructions here.
Flashing Via MicroSD Card
1. Make sure your microSD is Formatted to fat32 (you dont have to delete all files but it is safer if you do)
2. Download your prefered Rom from the LEO Rom Develpoment Page and unzip/unrar it to your PC
3. Goto the Roms Folder and rename the .nbh file to LEOIMG.nbh
4. Copy the LEOIMG.nbh file to the root of your MicroSD Card
5. Plug the MicroSD Card into the phone
6. Reset the device while pressing the volume down button to enter the BootLoader screen, you will first see a tri-color screen with the phone and SPL Information at the top
7. Follow the On Screen instructions to start the update
8. After flash has completed, press the reset button with the stylus to reset the device.

Yes; the first thing I tend to suspect is the USB Hub or ports on peripherals, but I also tried virtually every direct connect USB port on both machines.
and
Yes, I'm using the standard HTC micro-USB cable ... BUT whilst waiting for my second HTC cable to arrive I have also been using a micro-USB from a Jabra SP700 (car speaker) which "looks" identical but only charges my HD2 and doesn't work with ActiveSync ... so now I'm wondering if it is slightly different, maybe it has damaged the terminals on the phone - though would've thought that all micro-USBs plug in the same even if terminal configs differ resulting in connectivity differences ???

eViking said:
Yes; the first thing I tend to suspect is the USB Hub or ports on peripherals, but I also tried virtually every direct connect USB port on both machines.
and
Yes, I'm using the standard HTC micro-USB cable ... BUT whilst waiting for my second HTC cable to arrive I have also been using a micro-USB from a Jabra SP700 (car speaker) which "looks" identical but only charges my HD2 and doesn't work with ActiveSync ... so now I'm wondering if it is slightly different, maybe it has damaged the terminals on the phone - though would've thought that all micro-USBs plug in the same even if terminal configs differ resulting in connectivity differences ???
Click to expand...
Click to collapse
I do not understand all the mechanics of it, but no, not all micro-USB cables are the same, apparently some do not carry enough current, or some such thing. I am searching for more information for you now. If I find it, I will post it here.
For the life of me, I cannot find the information I was looking for. I read somewhere that others solved the problem by just disconnecting and reconnecting the phone during the flash process when the error occurs.
Well try another HTC cable as that sure seems to be suspect now. If all else fails, I would try flashing through the memory card method.
Keep us update. Hopefully soon you will get what you want.

Success!!! Flashing from a 3rd (more powerful) PC, went without a hitch and I'm now up and running.
My observations for what they're worth:
1. As noted by "FreyBerry", when running the Upgrade Utility from a PC using an ActiveSync connection to the phone, the connection gets dropped when the phone goes into bootloader mode and the PC is supposed to detect the phone as a USB device and reconnect - loading the appropriate driver. If driver and/or connection fails to load quickly enough the Utility times-out and you get the error message.
2. Though my USB cable may have been my problem, it seemed to work flawlessly on the 3rd PC. So other possibilites could be:
3. On the 1st attempt, running WinXP as a virtual machine inside an iMac, the USB-device re-connection doesn't happen fast enough as the Mac and PC inside the Mac arm-wrestle over which OS will pickup the connection.
4. On the 2nd attempt, using my office PC, our network/virus protocols/firewall or simply the aging PC may have been too slow or obstructed in reconnecting.
If the problem re-occurs I'll be opting for the SD-Card Flash method you suggested.
Many thanks for all the help ... I can already feel my pulled-out hair re-growing. Cheers.

Windows 7 seems to be the problem. I have the same problem if I want to upgrade the ROM on Windows 7, not on Windows XP.

3. On the 1st attempt, running WinXP as a virtual machine inside an iMac, the USB-device re-connection doesn't happen fast enough as the Mac and PC inside the Mac arm-wrestle over which OS will pickup the connection.
Click to expand...
Click to collapse
I never succeeded in flashing from a virtual machine on OS X.
@wereldbol No, it should work fine with Windows 7, both 32bit and 64bit.

Just last week I flashed a rom on a Vista x86 no problem. Now I've got Windows 7 x64 on a brand new computer and I'm now getting error 266. I don't have the option of using the old computer so I'm lost on what to do. I was already even able to flash HSPL3 to my wife's phone on the Win7 pc and didn't have this kind of trouble. But now I can't install a rom.
The device drivers installed. If anyone has any help. It would be much appreciated.

[Q] SD Card not mountable during ROM Flash, update not possible

Hi guys,
I got me a Defy and wanted to flash CM7/CM9. I got a few problems:
1. What did I do until now?
I rooted with Super one click, es it didn't work with the pushing and exploting the rageagainstthecage-arm5.bin (after exploiting, if the Defy did it properly, it used to exit from shell and the phone remained offline, so no more action could be performed with adb).
Also, ClockworkMod Recovery is installed.
I used this and another push/chmod approach: Cyanogenmod Wiki /Motorola_Defy:_Full_Update_Guide
2. Problem A)
When putting the CM Update zips on the SD card and booting, it will say it can't mount the SD Card.
I mixed some things up and tried to make the SD card mountable again with this approach (last paragraph): Cyanogenmod.com /index.php?title=Motorola_Defy:_Full_Update_Guide&oldid=13776#Problems_with_Android_2.1
By typing too fast i added two incorret entries (shouldn't be a problem).
Somewhere than I read, installing CM7 is only possible with Android 2.2. My Phone says the following:
- System version: Blur_Version.2.51.1.MB525.Retail.en.DE
- Firmware version: 2.1-update1
- Kernel version 2.6.29
3. Problem B)
So I thougth, next approach should be updating to Froyo. Sadly, Motorola Software Update doesn't recognize my phone, wheter with drivers from first link above nor with the drivers that come with the Update center (frankly, I haven't tried first link driver only but Software Update only and both togheter).
Several wipes and factory resets didn't help.
Any thoughts how I could fix this and get me a CM7? Best would be without loosing garantee (I mean sticking with an official software version as downgrade possibility). Should I have updated without ClockworkMod installed? Could return the phone and get me a new one if necessary.
Thanks for your help.
Edit: Is it possible that Motorola Update doesn't work with Win7 64Bit at all?

1st of all you MUST have froyo kernel (but certainly not eclair) before you can install Cm7 properly!
2nd it seems that your SD Card could be corrupted. It's important to eject your device from Windows PC properly before unplugging it. Otherwise you can corrupt your sdcard and/or internal memory.
Here is how you fix both your SD Card and internal FAT32 memory.
1) Plug in the device to the PC.
2) In Android turn on USB
3) The removable drives will show up in Windows.
4) Do one drive at a time. Right click on the removable drive and select Properties.
5) In this screen click the tools tab. Under error checking click the check now button
6) On this screen click the box "Automatically fix errors" and click start.
7) When it finishes it will either tell you if fixed problem or not.
8) If it did fix problems then you will find on the removable drive a folder called FOUND.000, FOUND.001, etc. You can delete those as they are broken files that got corrupt and you probably can’t do anything with them anyway!
9) Now eject the drives properly and you done.
Hope that helps.

Aw, men! I used not to eject any devices from my computer
I will try repairing and the the Software Update Center again.
If not, anybody knows which SBF file from sbf.droid-developers.org/umts_jordan/list.php is the one I would get after updating? I really don't get this list at all.
Thanks.

Ok I checked the sd card and there were no problems. So I switched to "Portal and tools" to check the Defy itself. The the first time Motohelper popped up and said something like:
"Starting the software not possible. In order to start Motorola Phone Portal you have to shut down all Motorola PC software and your phone has to be in one of the following modes: PC Mode, PC Tools or Portal Tools [not readable].
Open USB connection on your device and select either PC Model, PC Tools or Portal Tools"
This message keeps poping up if USB Debugging keeps enabled. Once I disable it and select Portal and tools again no pop up happens but no software (at least visible) starts. Should there pop up something? Start Motorola Phone Portal at device plug in is enabled. Or is this a normal behaviour at all?
Thanks.

Check out device manager in your windows if you have any question marks after connecting your defy to it properly (usb debugging and phone portal on). Maybe you do need some extra drivers on this one.

Well, now i got tired of this and I flashed a SBF with Froyo. Now I`ll trie flashing CM again.
Thanks anyway!

Nextbook Flexx 11 Tutorials

Nextbook Flexx 11
A 200-250$ 2-in-1 laptop.
CPU: 1.83 GHz Intel Atom Z3735F Quad-Core
RAM: 2 GBs
SSD: 64GBs
Screen: 11.6" Touchscreen
Ports: 1 x MicroHDMI, 1 x MicroUSB 2.0, 2 x USB 2.0
Micro SD Card slot

Installing every linux based OS(Android, RemixOS, Linux Distros)
Prerequisites:
A bootia32.efi file (Found in attachments)
A copy of your favorite linux distro
Rufus, UNetbootin, or a USB disk image write of your choice.
A flash you can wipe, and boot from
A little bit of time
Step 1: Setting up
First thing you'll need to do is use your image writer to write the iso to your USB.
MAKE SURE YOU SELECTED THE RIGHT USB DRIVE!
I cannot stress this enough, if you don't want to lose everything on another flash drive, or your hard drive, check and make sure you are using the right drive letter.
Do not restart now. We need to add some files to it.
Extract bootia32.efi and copy it to /boot/efi on your flash drive.
So this was some instructions I made for booting it, but this is much more complicated than it should be. You can totally disregard this spoiler.
Step 2: Booting
Plug your USB into your nextbook (if you haven't already) and turn it on/reboot it.
As its powering on, hold ESC to get into the boot options.
Click "Boot Manager" and select your USB drive.
IF IT DOESN'T SHOW UP, FORMAT YOUR USB DRIVE TO FAT32 AND GO BACK TO STEP 1.
Now, 2 things may happen, it may boot up perfectly, and from there, just follow the steps to install.
If it doesn't boot properly, we'll need to type a few commands.
Step 2.1: Grub Command Line.
So if it doesn't boot up properly, which chances are it wont, you'll be dropped into a command line.
This is grub, if you didn't know, and to boot we need to locate the drive its on.
First press FN+Ins to turn off NumLk, then type,
Code:
linux (hd
now if you press tab, it should list everything you have attached, for example:
Code:
hd0, hd1, hd2, hd3
The usb will most likely be hd0. So now you should have
Code:
linux (hd0,
If you press tab again, it will list off all of your partitions, or autofill one in.
Now you should have either:
Code:
1. linux (hd0,msdos1)
2. linux (hd0,gpt1)
Now, if you have this, type this(replace hd0,gpt1 with what you got):
Code:
set root=(hd0,gpt1)
then type
(new)Step 2: Creating a boot file.
So, now that you have the files copied over, you need to name the drive.
Right click your drive, and click Rename... (Remember the drive name, its important)
After you renamed your drive, create a folder at DriveLetter:/boot/grub
In that directory, create a file named grub.cfg
Now depending on your linux version, you'll have either syslinux, or grub already.
If grub: The file should already be there, so you can move on to step 3.
If syslinux: Find the isolinux.cfg or syslinux.cfg (probably in /syslinux or in /isolinux)
It will look something like:
Code:
label LinuxVersion
kernel /kernelFile
append initrd=/initrdFile (more options)
We're going to use these options to create our grub.cfg file.
Use this as a template.
Code:
menuentry 'LinuxVersion' {
search --set=root --label THIS_IS_WHERE_THE_LABEL_YOU_SET_EARLIER_GOES
linux /kernelFile (more options)
initrd /initrdFile
}
Step 3: Boot into your new OS.
Reboot your PC. When it turns back on, hold ESC.
You should be brought back to the BIOS area.
Press "Boot Manager" (you will need a mouse for this), and select your USB drive.
If you did everything correctly, it should boot.
Step 4: Go wild!
You should be booted, GO CRAZY!
There are a few problems with most distros, including:
No Wifi
No Bluetooth
No Gyroscope
No Audio
There are drivers online for these, but you need to be able to patch a kernel, and build/install a driver.
Wifi
Is the guide not working?
Go ahead and ask some questions, don't be afraid of help.

Useful resources:
Ubuntu with Wifi (Source)
Thats all the links for now. I will add more as I find them (hopefully to fix audio, power button, and rotation)
Huge thanks to Ian Morrison for the Ubuntu iso.

TAG

Any chance you're going to do the linux?
Reserved
I'm guessing that is where the linux how to, is going.

Dude.. You gonna finish this?
set code=(hd0,msdos1)
Then type
Type what? Need a complete tutorial here...

I'm so sorry
Chaosmstr said:
Dude.. You gonna finish this?
set code=(hd0,msdos1)
Then type
Type what? Need a complete tutorial here...
Click to expand...
Click to collapse
I apologize for the delay, busy with school and all.

You can't leave us hanging like this!

I'm not sure about OP here, but I have the smaller model of this device being the Flexx 10. Now I haven't tried to boot Android on it, but I have successfully booted Linux Mint with it.
First I would recommend using a USB OTG capable flash drive (they are available at office stores, walmart, and so on and so forth,) or an OTG adaptor instead of using a full sized usb. The reason for this is stability of the booted system as the connection of the keyboard dock does not appear to be extremely reliable. This may vary by model or device but I would still recommend it as you may need the full sized USB ports later.
Now instead of using Unetbootin, I used Rufus. I used the settings of GTP for efi and bios to write the image to the drive. I didn't mess with any other settings there. After that I had to get a file called bootia32.efi and then add it to the /efi/BOOT/ before the system would even try to recognize it. From there it was just waiting patiently while it booted. (use the instructions in the earlier post to get to the boot options of the UEFI) It took it a while to boot as I suspect the USB speed was rather slow.
As I didn't really have time to really mess with it and get to the point of install, I will list the issues I came across.
1: Automatic rotation of the screen did not work.
2: wifi (RTL8723BS SDIO)
3: bluetooth
4: sound
everything else seemed to work just fine though, even the volume rocker, windows button and power button on the tablet section reacted and did things. not entirely useful, but they did work.
Edit: forgot to mention that if you go through with the install, you will have to finish the install by doing some grub modifications to make it boot without a live disk. just a heads up.

Hmfan said:
I'm not sure about OP here, but I have the smaller model of this device being the Flexx 10. Now I haven't tried to boot Android on it, but I have successfully booted Linux Mint with it.
First I would recommend using a USB OTG capable flash drive (they are available at office stores, walmart, and so on and so forth,) or an OTG adaptor instead of using a full sized usb. The reason for this is stability of the booted system as the connection of the keyboard dock does not appear to be extremely reliable. This may vary by model or device but I would still recommend it as you may need the full sized USB ports later.
Now instead of using Unetbootin, I used Rufus. I used the settings of GTP for efi and bios to write the image to the drive. I didn't mess with any other settings there. After that I had to get a file called bootia32.efi and then add it to the /efi/BOOT/ before the system would even try to recognize it. From there it was just waiting patiently while it booted. (use the instructions in the earlier post to get to the boot options of the UEFI) It took it a while to boot as I suspect the USB speed was rather slow.
As I didn't really have time to really mess with it and get to the point of install, I will list the issues I came across.
1: Automatic rotation of the screen did not work.
2: wifi (RTL8723BS SDIO)
3: bluetooth
4: sound
everything else seemed to work just fine though, even the volume rocker, windows button and power button on the tablet section reacted and did things. not entirely useful, but they did work.
Edit: forgot to mention that if you go through with the install, you will have to finish the install by doing some grub modifications to make it boot without a live disk. just a heads up.
Click to expand...
Click to collapse
Sorry I'm coming back so late, I've been busy with life.
The Wifi issue can be fixed by building the driver (https://github.com/hadess/rtl8723bs)
The bluetooth wont work on most OS' because it relies on some windows drivers to work.
I might be able to find a driver for screen rotation/audio.
Another issue is the power doesn't get registered, and the touch screen is VERY flaky.

Kitsumi said:
Sorry I'm coming back so late, I've been busy with life.
The Wifi issue can be fixed by building the driver (URL removed per post restrictions.)
The bluetooth wont work on most OS' because it relies on some windows drivers to work.
I might be able to find a driver for screen rotation/audio.
Another issue is the power doesn't get registered, and the touch screen is VERY flaky.
Click to expand...
Click to collapse
I didn't really notice that power one as I did not use it long, but I think that is just an atom thing. My old n270 based aspire one does that too.
Really though, the way I would use it, I wouldn't miss screen rotation or the bluetooth, but the touch screen is the nuisance. What I noticed with it is that when the screen is forced into proper orientation (by use of screen rotation in the settings, you know without using the command line) is that the touch screen doesn't follow the new orientation correctly. It appears to have the portrait resolution set to the top left of the screen in landscape. That said, it works fine in portait. Or at least managably.

Hmfan said:
I didn't really notice that power one as I did not use it long, but I think that is just an atom thing. My old n270 based aspire one does that too.
Really though, the way I would use it, I wouldn't miss screen rotation or the bluetooth, but the touch screen is the nuisance. What I noticed with it is that when the screen is forced into proper orientation (by use of screen rotation in the settings, you know without using the command line) is that the touch screen doesn't follow the new orientation correctly. It appears to have the portrait resolution set to the top left of the screen in landscape. That said, it works fine in portait. Or at least managably.
Click to expand...
Click to collapse
Well, I decied to try and boot remixOS, and it works VERY well, so does android-x86 5.0
That being said, audio is a glaring issue.

When you tried Remix OS and say it worked very well. What do you mean? What actually worked? Obviously audio is what doesn't since you mentioned it. But am I to assume that screen rotation works as expected then?
I'm not willing to use REMIX OS personally as the whole android bit is a limiting factor to me. Unless it rooted of ccourse. but even then some of my prefered uses for Linux is lost.
Also hows the hardware acceleration?

How do I install the x64 version of Windows? I downloaded the ISO with the Media Creation Tool and it won't boot from the USB drive. I enabled USB booting and made sure secure boot was off, but it's not working. It keeps saying there's no USB device available.

Unfortunately due to the way that Windows works, the 64 bit version is not usable due to the bootloader difference. Even though the hardware of the device is capable of 64 bit code execution, the 32 bit UEFI Bootloader will only allow a 32 bit version of Windows or a 64 bit version of Linux with some EFI fiddling. And as far as I know there is not a way to fiddle with the EFI related workings of a Windows ISO so 64 bit Windows is not possible on these Nexbook devices or others with similar hardware (Asus t100 is a good example of similar device)

Hmfan said:
Unfortunately due to the way that Windows works, the 64 bit version is not usable due to the bootloader difference. Even though the hardware of the device is capable of 64 bit code execution, the 32 bit UEFI Bootloader will only allow a 32 bit version of Windows or a 64 bit version of Linux with some EFI fiddling. And as far as I know there is not a way to fiddle with the EFI related workings of a Windows ISO so 64 bit Windows is not possible on these Nexbook devices or others with similar hardware (Asus t100 is a good example of similar device)
Click to expand...
Click to collapse
That's really dumb. Most Windows devices are 64-bit nowadays. Why would they put in a 64-bit processor but not allow x64 operating systems?

You're guess is as good as mine on that one. Ask Microsoft on that one. They used the 32 bit version because Microsoft will only give the "Windows XX (originally 8.1) with bing 32bit for free. Which keeps the device cost down. Kinda hard to to sell a cheapskate device when it ends up costing as much as a better speced laptop.

Where can I find recovery images for this? I messed up and now I don't have audio or touchscreen drivers.

You can try this web site from Efun themselves
http://nextbookusa.com/recovery/index.html That is their official recovery download site.
(apparently I can post links...)

Hmfan said:
You can try this web site from Efun themselves
http://nextbookusa.com/recovery/index.html That is their official recovery download site.
(apparently I can post links...)
Click to expand...
Click to collapse
I tried that. It says there's no recovery option for this model....
Do you have this tablet? Do you think you could do a driver backup and upload it here? Or create a recovery image and share it?

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

Unable to install widows on new pc build

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!