@everesee, My 925 is also the 32gb LE and its my main phone, so I'm not going to risk wreaking it to test something that's still basically WP8.1. That's what my older Windows Phones are for
I haven't even hesitated when I hear w10 can be installed on L925 NP for now (Lumia software recovery tool can rollback my phone to 8.1, so np again )
So naïve. Please read earlier Doing so, you testing your luck in dangerous means. The fact that you did this, and still have a working device is just some luck, because it is a real 50/50 between softbrick (may be LSRTd) and hardbrick (may not be). If you get offered some firmware update (e.g. 630/635/636/638/830-specific Denim tweaks) on top of your Windows 10, then it might be your ticket to hell due of the above. Didn't no one notice that all the currently supported devices run on Snapdragon 400? And you forcing that system to S4. There are reasons Microsoft locked the preview only to a few phones for the first wave. Impatience may show the other side too.
It's not possible deploying wrong firmware to device on recovery tool. My recovery tool still detects my device as Lumia 925, TR-Vodafone 32GB, and shows true firmware as update.(plus, a lot of people were able to turn back 8.1, i didn't do it yet) Secondly, which kind of firmware update will be offered to me? I will use this rom only for 2 or 3 weeks.(It's not possible for new firmware in 2-3 weeks) So I know risks, I won't apply any update from windows update to my device. Lastly, my device shows 000-HK instead of 000-TR for mobile operator. And again shows RM-1027_1007 instead of RM-892. My firmware version is still same with my own 8.1 version. So is it a bad thing? They are only texts... Not proper information. They can be fixed with recovery tool... NVM, thanks for information
Oh, I get what you mean. And yeah, I can see how it could affect the performance of resource hungry apps or games. Even if there are no VM's running, there will still be 4 or 5 Hyper-V services running and at least one of them affects Power Management, as some Surface Pro 3 owners have found. This is a common problem, most of the Distros are using older versions of 'LIS' which were designed for the Server version of Hyper-V and don't work correctly with Windows 8.x/10. As with any other drivers, you should always try and use the latest available. As for the 'disk IO' problem, if its not fixed by installing 'LIS' try this: Code: in the boot loader’s configuration (/etc/grub.conf, for example), add elevator=noop to the kernel parameters, and then restart.
True, normally flashing won't allow you to get wrong image, as if you try to push a FFU that is signed for another device, it will be declined. The point of the above is the definite possibility of bricking while being offered FOTA updates from phone update. The point is to not try to install FOTA updates intended for the other phones. Moreover once an update got pended, it cannot be removed from the installation pending queue, it's. either "install now" or "later" up to the displayed date of critical update threshold - before this happen its best to reflash while still can. This. Because you faked your rm-892 925 to be 636 (rm-1027), FOTA intended for 636 (059W245) might be offered in phone update, in case they decide to roll out some fix to the current firmware, who knows. If this happens, there is a great possibility of risk getting the wrong UEFI package FOTA, and in that case the recovery tool might not see the 925 ever. This also applies to the initial Windows 10 OTA offering, as phone updates might bundle firmware. Ever checked the phone DU log to see what packages get updated on each any OTA update?
Take it this way: we get a driver into a diesel car and say its a petrol car. He drives it, but eventually comes the time to refuel and the driver fuels petrol in instead of diesel oil. What happens?
Can we stop derailing the thread by asking how to stop a PREVIEW operating system from expiring? ITS A PREVIEW. ITS GOING TO EXPIRE. Trying to permanently activate an operating system that is not meant to be used permanently is stupid. Trying to remove a watermark for an OS that isn't done is also stupid. Who cares. A new build will come out shortly and you will have done it all for nothing. Please stop.