Develop Bugs

CAN I LOAD WINDOWS MOBILE 6.0 ON SONYERICSSON M600i (UIQ 3)

CAN ANYBODY GUIDE ME ON HOW TO INSTALL WM6 ON MY SE M600i

of course NOT!..
its like saying "can i LOAD PSP to my Gameboy Color"

double_ofour said:
of course NOT!..
its like saying "can i LOAD PSP to my Gameboy Color"
Click to expand...
Click to collapse
lol lol

ravinbajaj said:
CAN ANYBODY GUIDE ME ON HOW TO INSTALL WM6 ON MY SE M600i
Click to expand...
Click to collapse
You cannot put Windows Mobile to SE M600i, It is a diffrent OS platform.

hahahahaha

can I load the ROM from other type? like can I load a WM6 from an Atom to a XDA III?

That's about like asking my wife if I can have a sex change...
I really don't know whether to laugh or cry at your ignorance.

sorry for this silly question
I was considering if it's like PC OS that have almost the same core and can be modified before deploy to another station.

imnewer said:
sorry for this silly question
I was considering if it's like PC OS that have almost the same core and can be modified before deploy to another station.
Click to expand...
Click to collapse
It could be possible like using the HTC Wizard rom for a Charmer... This has already been done... Still it's a silly question without having checked the inner hardware, etc.
So yes, this CAN be done... (if the hardware is not too different)

It is not like PC OS at all. I should probably send you to the WiKi but I do have a bit of time to burn so here is the explanation:
First, you can not load Windows Mobile on to devices with other OS. It would be the same as trying to run Windows on a Mac or Mac OS on a PC, the BIOS (or in our case bootloader) wouldn't support it, plus I am fairly sure there is some difference in processor architecture so it can't "understand" the code at all.
Second you can not change ROM between different Windows Mobile devices because unlike desktop PC Windows Mobile comes in an image bundled with drivers and other hardware specific components. Flashing the wrong image will brick the device, and there is no such thing as "generic" WM installation.
To conclude: You can not put WM on anything other that the devices that have official or unofficial update to this OS.

thank you so much guys for guide me a lot.
I knew that different devices might built in different architectures, but some of the devices use same series of cpu. and also did concern about different hardware need respective driver...but not aware of the encryption there might be...
thx for the explanation~

levenum said:
It is not like PC OS at all. I should probably send you to the WiKi but I do have a bit of time to burn so here is the explanation:
First, you can not load Windows Mobile on to devices with other OS. It would be the same as trying to run Windows on a Mac or Mac OS on a PC, the BIOS (or in our case bootloader) wouldn't support it, plus I am fairly sure there is some difference in processor architecture so it can't "understand" the code at all.
Second you can not change ROM between different Windows Mobile devices because unlike desktop PC Windows Mobile comes in an image bundled with drivers and other hardware specific components. Flashing the wrong image will brick the device, and there is no such thing as "generic" WM installation.
To conclude: You can not put WM on anything other that the devices that have official or unofficial update to this OS.
Click to expand...
Click to collapse
have a look at the facts you can run windows xxxx on a imac and mac mini and you can run mac osx on a pc so it may be possible to run windows mobile on se m600
jim

HI-JET said:
have a look at the facts you can run windows xxxx on a imac and mac mini and you can run mac osx on a pc so it may be possible to run windows mobile on se m600
jim
Click to expand...
Click to collapse
Well it may very well be possible, but not with the tools available to us or any other average joe.

masr1979 said:
Well it may very well be possible, but not with the tools available to us or any other average joe.
Click to expand...
Click to collapse
go to link and read for you self how it done run oxs on a pc
http://www.osx86project.org/
---------------------------------------------------------
go to link and read for you self how it done run windows on imac and mac mini
http://www.apple.com/macosx/bootcamp/
jim

this thread has to be the dumbest one ive seen in awhile..

HI-JET said:
go to link and read for you self how it done run oxs on a pc
http://www.osx86project.org/
---------------------------------------------------------
go to link and read for you self how it done run windows on imac and mac mini
http://www.apple.com/macosx/bootcamp/
jim
Click to expand...
Click to collapse
I wasn't referring to osx on pc as I'm well aware of that. The question is can you direct me to a link where it shows some readily available hardware and software to port WM6 to a sony M600? not that I could do anything with the info, simply for arguments sake.

it becomes boring...Linux can be load on Xbox...just imagination, maybe there will be some way to load a WM rom within sort of hardward series...(like Dopod 828 & 838 & P800 are most the same series for TI cpu etc)...

Settle down, pleas I did not mean to start a debate.
When I was talking about Mac and PC I just wanted to use the older, Motorola processor based architecture as an example. (Forgot Macs use Intel these days).
Any way - Windows Mobile like any OS can be adopted to any platform - in theory, but the radical changes required are beyond the scope of private enthusiasts such as on this site.
Even if processor architecture is the same, you would at the very least have to rewrite all the drivers for the given device, and that is an enormous task.

it would most likely require access to the sourcecode (not something ms let you download being they hate opensoufce) and a team of developers to make new developing to support hardware they might not have any spcs on (not something sonyE hand out at the door)
depending one how much backward enginering would be required
1 man year of developer time
for each enuiqe platform
this is not counting the lawsuits from ms and or sonyE
and the man years of answering questions of people wanting to know if it works on their old nokia 3110

I cannot work out how to enable HSDPA on my commodore 64, could some one tell me if installing WM6 would help with this?

WinP7 Rom

im not sure i get whats going on with this new winp7 rom thats been posted.
has anyone run it on an emulator? if not how do you know its even real? and when you guys are talking about dumping it what exactly does that meen, sorry for nuub questions but im not that up on the dev scene

Well, it can't be run in the Emulator, as the Emulator uses x86 ROMs, while actual devices are based on the ARM architecture, so basically as of now no one can say for certain if it is real (although some things look promising).
As the ROM is intended for use on a not yet known device it also can't be flashed to a device anyone owns.
Dumping means that they are trying to extract the files which are contained in the ROM image, which is difficult as the format is different from WM6.5 and no documentation exists for it.
If they can extract the files they then could be repackaged to known formats which then could be flashed - nobody knows if that will boot on any existing device though.

StevieBallz said:
Well, it can't be run in the Emulator, as the Emulator uses x86 ROMs, while actual devices are based on the ARM architecture, so basically as of now no one can say for certain if it is real (although some things look promising).
As the ROM is intended for use on a not yet known device it also can't be flashed to a device anyone owns.
Dumping means that they are trying to extract the files which are contained in the ROM image, which is difficult as the format is different from WM6.5 and no documentation exists for it.
If they can extract the files they then could be repackaged to known formats which then could be flashed - nobody knows if that will boot on any existing device though.
Click to expand...
Click to collapse
ahh ryt. i get the emulator part, i actually have the visual studio 2k10 for win phone so i understand that there is a difference between computer based roms and mobile roms. but i thought maybe there was a tool out ther that could use mobile roms, lik a virtual box for phones, i know that people know the hardware specs for win phone 7.. 3 buttons, 1g processor, capacative touch screen etc etc so i thought maybe sumone had used it through a virtual phone

96edwy said:
... i know that people know the hardware specs for win phone 7.. 3 buttons, 1g processor, capacative touch screen etc etc so i thought maybe sumone had used it through a virtual phone
Click to expand...
Click to collapse
No, we've been told the minimum specs by MS.
Casey

Perhaps the old Emulator from the WinCE6 SDK might be able to run it, as it had to support native ARM Code, it had to emulate the CPU architecture, but most likely features of newer ARM Cores are missing and WP7 seems to be using them.
But obviously (as seen from the emulator) there is a way to compile the System to the x86 architecture, so maybe Intel gets around to include a decent graphices core and we might see some ULV Atom powered WP7 phones - or not ;-)

WinRT on Nexus 7

Good afternoon!
A few days ago came into my hands one file, it was a way I've found windows rt restore img. Googling found that hardware stuffing differs only display resolution and count-tion of memory (in Asus Vivo RT 2 GB, Microsoft Surface 2GB while the Nexus 7 1 GB), but the problem is that all WinRT tablet is uefi bootloader. Remembering Projects OSX86 and about chameleon, empire efi, decided to port the bootloader on Nexus. Make the type MultiBoot.
who will help me in my endeavors?
Cotulla make with htc hd2 magldr>uefi>win rt (magldr this is custom loader with sdcard boot support) / can we make a analog of magldr for nexus 7?

Hi, I acan't help but don't see why this isn't possible (albeit very hard) as win rt has been run on htc hd2 http://www.xda-developers.com/windows-mobile/htc-hd2-refuses-to-die-now-runs-windows-rt/ however I beleive a custom firmware was written for the very purpose.
I am trying to do the complete opposite and install android/ubuntu on the vivo tab tf600. Best of luck and please post updates if you make any progress.

need people who can write uefi loader/ please write.

blaze_cv said:
need people who can write uefi loader/ please write.
Click to expand...
Click to collapse
Unfortunately I don't have the technical knowledge to be able to help you with that...
But I think I've read that MAGLDR-UEFI was based on tianocore, so you can start with that!
Code:
tianocore.sourceforge.net
But it's an awesome project!:highfive:
I hope you can make it happen! :fingers-crossed:

Just now, we need MS SurfaceRT tablet, and I collect the money for it.
But in priority I have psVita Hacking...

[Q] Android 4.4 kitkat on Galaxy w?

Google says android 4.4 kitkat is available for everyone. So is it means we can flash it directly to our galaxy w?
Now our smartphones become a mini computers.
in dekstop computers we can install a new os(linux or windows) directly. The OS recognize the drivers then install them directly or from the web. Maybe some of hardwares drivers cant find but its very rare issue.
So why android doesnt like this. Thats everybody install new version of android and its install the phones drivers directly or from the internet.
The smartphones hardware manufacturers less than dekstop computers hardware manufacturers but dekstop computers OS can do it well and avaliable for every kind of computer.
Why Android OS install like dekstop computers OS.

pharatlil said:
Google says android 4.4 kitkat is available for everyone. So is it means we can flash it directly to our galaxy w?
Click to expand...
Click to collapse
No, it needs to be ported.
pharatlil said:
in dekstop computers we can install a new os(linux or windows) directly. The OS recognize the drivers then install them directly or from the web. Maybe some of hardwares drivers cant find but its very rare issue.
So why android doesnt like this. Thats everybody install new version of android and its install the phones drivers directly or from the internet.
The smartphones hardware manufacturers less than dekstop computers hardware manufacturers but dekstop computers OS can do it well and avaliable for every kind of computer.
Why Android OS install like dekstop computers OS.
Click to expand...
Click to collapse
This is just partially true. Windows and Linux for desktop PCs already come with most of the drivers directly on the CD or DVD or at least with hardware IDs for the drivers they can download and install via internet.
Your ROM simply isn´t about the same size like a Linux or Windows DVD It also doesn´t have a 100GB HD, a DVD drive and at least 4GB RAM installed.
So if you want an Android that is about as easy to install on all devices, you would have to make it about that big in size like a Linux or a Windows installation DVD which most of the devices couldn´t handle.
That´s why it needs to be ported with just the drivers for your specific device. And this is also the advantage to keep it as small and slick as possible.

Most of linux os about 1gb.
Windows is about 1-2 gn. Not about 100gb.
İ ha ve a galaxy s3 and stock rom about 900mb.
İf google want to give latest firmwares every device They can make a pc program and it finds devices specs automatically.
Samsung, htc, lg...etc.. maybe dont want to give newest firmwares to older devices for selling new devices.
But why google dont make roms for every device. Android is a linux based os and linuxs difference is its avaliable for everyone. So i think googles s strategy about android isnt true. İt must be same way with linux.

pharatlil said:
Most of linux os about 1gb.
Windows is about 1-2 gn. Not about 100gb.
İ ha ve a galaxy s3 and stock rom about 900mb.
İf google want to give latest firmwares every device They can make a pc program and it finds devices specs automatically.
Samsung, htc, lg...etc.. maybe dont want to give newest firmwares to older devices for selling new devices.
But why google dont make roms for every device. Android is a linux based os and linuxs difference is its avaliable for everyone. So i think googles s strategy about android isnt true. İt must be same way with linux.
Click to expand...
Click to collapse
A totally fresh installed Windows 7 already is taking about 4GB on your HD and needs a way bigger partition to get installed at all.
Android is not a linux based rom. It´s a Java based ROM. Only the kernel is linux and this needs to be compiled first and match your hardware to make it able for the rom to work at.
Google only offers the basic code for a ROM but the rest must be added by the manufacturers. Beside this linux also wasn´t that userfriendly like it is now. The very first releases even didn´t use an UI. All had to be done on command line. Was meant to be used on servers but not for end users and though it was open source it took about 20 years from this stage to become an userfirendly OS for endusers like Windows.
So this is like comparing apples with pears. Best you ask Google and see what they will answer you.

İm disagree with you. or i couldnt explain well.
There in not more hardware manufacterers than PCs. But dekstop computers OS can handle it. For example i have got a hp compaq nx8220 notebook. its very old pc but i intalled windows 8 and its running very well. There is no drivers for windows 8 but windows have a feature for it. İ install many drivers in compatibility mode. ( Yes HP didnt publish a driver for it but windows's this compatibility feature solve the problem.)
Im not a developer but i know programming dialectic (i wrote programs in q basic and gw basic but i stay away from programming because of my job.) im interested about java and c++ and im learning. im seeing that developers main problem to porting Android to a device is hardware drivers. İf manufacterer give codes they port it easier.
İ want to say my hp compaq nx8220 is very old device but its runs with windows 8 very stable.
But my old phone and and my wifes phone galaxy w isnt a old device but they r saying your device cant runs properly with android's newest OS. It has 512 mb ram and 1,4ghz processor.??? (my notebook worst but runs w8)
Maybe one day some developers agree with my opinion and work with hardware drivers than making alot of custom roms. So maybe one day we enter a web page (for example cyanogenmod web page)and flash newest rom like installing a newest OS to a PC.

You may agree or disagree. No problem with that. It´s just you are comparing apples with pears. An Android Phone isn´t the same like a PC. Doesn´t have a HD or something equial to this in its capacity and so on. Neither Android, Firefox OS or Ubuntu Touch do have such an installer included that will install the Operating System on all devices. They all need to be ported. The same even for Windows Phone. So rather than arguing with me, go out and ask all the big players like Google, Ubuntu, Firefox or Microsoft why this isn´t the same like fo a PC.

Help needed to install Windows 10 for ARM32 for Nokia Lumia 2520 RT

Hi guys, can anyone help to install Windows 10 for ARM32 for Nokia Lumia 2520 RT tablet?

Same procedure as other devices but you will have to substitute the drivers with ones from the 2520 aside from qcpep which has to be replaced with an alternative one which I think came from the Lumina WoA project staff (From Lumia 930?). However, if your 2520 has been kept up to date with the latest patches under RT 8.1 then you won't be able to jailbreak it in order to use 15035

jwa4 said:
However, if your 2520 has been kept up to date with the latest patches under RT 8.1 then you won't be able to jailbreak it in order to use 15035
Click to expand...
Click to collapse
Hi JWA4 could you expand on this? Also is it the case for the surface RT as well (latest up to date version can't be jailbreaked) or just the 2520?

devinpatterson said:
Hi JWA4 could you expand on this? Also is it the case for the surface RT as well (latest up to date version can't be jailbreaked) or just the 2520?
Click to expand...
Click to collapse
The short version as I understand it is that Nvidia screwed up in users favor which makes the Tegra Surfaces immune to permanent effects of the jailbreak killing Windows RT updates. On these devices reversing the negative effects of theses updates is as simple as a factory reset.
Sadly with the Lumia 2520, Qualcomm did the job right and at present there is no going back if a jailbreak killer has ever been installed.
I will try to find the detailed explanation I read and post it here asap.

jwa4 said:
The short version as I understand it is
Click to expand...
Click to collapse
Thanks for taking the time to fill me in the 2520 Jwa4
jwa4 said:
I will try to find the detailed explanation I read and post it here asap.
Click to expand...
Click to collapse
That would be awesome if your able to locate the info in more detail

devinpatterson said:
That would be awesome if your able to locate the info in more detail
Click to expand...
Click to collapse
I was unable to find the explanation that I read but if I find it again I will post.
I could be wrong and there might be more to it but I think the general idea was that Nvida did not implement the mechanism that handles the revocation of previously issued certificates correctly whereas Qualcomm did. On a previously updated Lumia 2520 this prevents the Secure Boot Debug Policy from working because its certificate is no longer going to be valid on the device.

Telegram: Contact @L2520w10RT
4pda.ru
I installed Win 10 RT on Lumia 2520.
with any security updates! No problem.
But, I need help with drivers.

CageOff said:
Telegram: Contact @L2520w10RT
4pda.ru
I installed Win 10 RT on Lumia 2520.
with any security updates! No problem.
But, I need help with drivers.
Click to expand...
Click to collapse
How were you able to do this? I thought the Secure Boot issue stopped any other installations?

lord_melchett said:
How were you able to do this? I thought the Secure Boot issue stopped any other installations?
Click to expand...
Click to collapse
Go to Discord. I discuss all the sub-genes there. The system is not ready for public use. Testsign, secureboot and everything you need is there. No problem using Linux via grub uefi. It is much more difficult to find developers who will do this. And Tales about the impossibility of disabling Secureboot is just a fact of bygone days. The device is now free of these restrictions.
No touch, no modem, no BT, no audio, adreno 330 not work.
But yesterday qcpep and qcpepproxy did not work as expected.
Today they are working as expected.
I will start other hardware devices too. It just takes time.

CageOff said:
Go to Discord. I discuss all the sub-genes there. The system is not ready for public use. Testsign, secureboot and everything you need is there. No problem using Linux via grub uefi. It is much more difficult to find developers who will do this. And Tales about the impossibility of disabling Secureboot is just a fact of bygone days. The device is now free of these restrictions.
No touch, no modem, no BT, no audio, adreno 330 not work.
But yesterday qcpep and qcpepproxy did not work as expected.
Today they are working as expected.
I will start other hardware devices too. It just takes time.
Click to expand...
Click to collapse
Cool. So does everything work fine on Linux, just not in Windows 10? Having never used discord let me know where to find out. If I can dump any files to help let me know

CageOff said:
[URL unfurl = "true"] https://4pda.ru/pages/go/?u=https://t.me/L2520w10RT&e=103134199&f=https://4pda.ru/forum/index .php% 3Fshowtopic% 3Dst5135 [/ URL]
Ho installato Win 10 RT su Lumia 2520.
con eventuali aggiornamenti di sicurezza! Nessun problema.
Ma ho bisogno di aiuto con i conducenti.
Click to expand...
Click to collapse
Salve...mi potreste aiutare ad aistallare windows 10 oppure linux mine su nokia lumia 2520?

Salve ragazzi ... vorrei un aiuto per istallare windows 10 o linux mine su nokia lumia 2520 ... se è possibbile..grazie..questo forum e fantastico ... max

Do you have a guide to follow for this? I went to your Telegram site but all I saw was pictures.

i need help to install windows 10 rt on Nokia 2520

I know this device is so outdated and all, yet it'd be nice to get some use out of it. Anyone have a proper guide on how to accomplish what @CageOff was saying in order to bypass the security update patches and getting securebooot unlocked. I've tried so many different methods and gotten nowhere in my attempts to get working BOOTABLE USB media for 8.1. No guide clearly explains/points out that the Myriachan's Jailbreak is the exploit specifically intended for the Qualcomm Nokia Lumia 2520 to get the test mode exploit going (if it works). Longhorn obviously doesn't work as it can't install Golden Keys. I went to the Telegram group @CageOff mentions, but there is no way to talk to the person nor any clear info about how he managed to dualboot win10 arm/win8.1 arm. If anyone could shed some light on me here, It'd be much appreciated.

hugoBOSS1981 said:
I know this device is so outdated and all, yet it'd be nice to get some use out of it. Anyone have a proper guide on how to accomplish what @CageOff was saying in order to bypass the security update patches and getting securebooot unlocked. I've tried so many different methods and gotten nowhere in my attempts to get working BOOTABLE USB media for 8.1. No guide clearly explains/points out that the Myriachan's Jailbreak is the exploit specifically intended for the Qualcomm Nokia Lumia 2520 to get the test mode exploit going (if it works). Longhorn obviously doesn't work as it can't install Golden Keys. I went to the Telegram group @CageOff mentions, but there is no way to talk to the person nor any clear info about how he managed to dualboot win10 arm/win8.1 arm. If anyone could shed some light on me here, It'd be much appreciated.
Click to expand...
Click to collapse
Myriachan is not specifically intended for Qualcomm devices, its just that it can't be permanently patched against but this won't help you for 15035.
I don't have a 2520 but from what I can tell CageOff seems to have booted 15035 on a 2520 but the details are getting lost in translation and a writeup doesn't seem to be forthcoming. From what I can gather even though he has booted 15035 on his 2520, he has done so without the installation of the QCPEP driver and without this driver virtually nothing else will work.
On QCEP - BetaWiki.net
This build does not support the Nokia Lumia 2520 Qualcomm Power Engine Plugin driver. Loading a newer driver for the Snapdragon 800 is mandatory.
Click to expand...
Click to collapse
The newer driver I believe is harvested from the LumiaWOA project, specifically taken from the Lumia 930 package. It could be worth looking at how WFAv7_Installer installs 15035 on a 930? It might shed some light on the driver ordering, as far as I've been told Qualcomm stuff has to be dealt with in a certain order.
Before you put too much time in to this though remember 15035 is about as much use a chocolate teapot so remember its just for fun. If you spend a week figuring it and actually get it all working in the hope of making an ex-RT device useful you are going to be a little disappointed at the end of it.

jwa4 said:
Myriachan is not specifically intended for Qualcomm devices, its just that it can't be permanently patched against but this won't help you for 15035.
I don't have a 2520 but from what I can tell CageOff seems to have booted 15035 on a 2520 but the details are getting lost in translation and a writeup doesn't seem to be forthcoming. From what I can gather even though he has booted 15035 on his 2520, he has done so without the installation of the QCPEP driver and without this driver virtually nothing else will work.
On QCEP - BetaWiki.net
The newer driver I believe is harvested from the LumiaWOA project, specifically taken from the Lumia 930 package. It could be worth looking at how WFAv7_Installer installs 15035 on a 930? It might shed some light on the driver ordering, as far as I've been told Qualcomm stuff has to be dealt with in a certain order.
Before you put too much time in to this though remember 15035 is about as much use a chocolate teapot so remember its just for fun. If you spend a week figuring it and actually get it all working in the hope of making an ex-RT device useful you are going to be a little disappointed at the end of it.
Click to expand...
Click to collapse
That's definitely worth looking into in regards to the "WFAv7_Installer". I just tried the WOA Deployer v2.7.1 and it seems it could be of great use in getting Win 10/11 arm onto this device. Of course, if one can figure out how to access/enter a Mass Storage mode first.
I also read in another forum article that the IOT versions of Windows seems to be more useful for this device, rather than trying to get the standard Pro/Home editions. They also mentioned that one may need to apply the drivers from the original Win 8.1 RT in order to get all of the devices hardware working though. I would personally like to give this a try, but I can't seem to get to the point of being able to install Win 10 build 15035 onto my device. I can't enable test-signing mode, nor disable bootloader with any of the jail breaks available. I get the error code 0x000000000000d (not sure i put the correct amount of zero's there), which seems to give no existing info on the net for that error code, only a few forum posts regarding the variant to that code which ends in "f" which seems to be related to the Surface 1/2 devices.
I know I can format the eMMC properly via command prompt, diskpart, and dism (for Win 8.1 RT), then disable BitLocker (even though C:\ still says Bitlocker Encrypted). Yet, I just can't get the Win 10 media to work which i assume is due to secure boot. Does it make any difference if I'm using the install.wim or install.esd versions of the media?

hugoBOSS1981 said:
That's definitely worth looking into in regards to the "WFAv7_Installer". I just tried the WOA Deployer v2.7.1 and it seems it could be of great use in getting Win 10/11 arm onto this device. Of course, if one can figure out how to access/enter a Mass Storage mode first.
Click to expand...
Click to collapse
WOA Deployer is specifically for deploying WoA on the Lumia 950 & 950 XL, it doesn't support Windows 10 15035 or ARM32 devices like the Lumia 2520.
Windows 11 is out of the question, only small parts of it were built for ARM32 (nothing close to a full client) and the bits that were built won't work with this SoC. I don't believe WFAv7_Installer ever had the 2520 in mind, I only suggested it because how it prepares an image for some of the Lumia phones might shed some light on how an image would need to be prepared for the 2520.
hugoBOSS1981 said:
I also read in another forum article that the IOT versions of Windows seems to be more useful for this device, rather than trying to get the standard Pro/Home editions. They also mentioned that one may need to apply the drivers from the original Win 8.1 RT in order to get all of the devices hardware working though.
Click to expand...
Click to collapse
That's going to come down to what you define as useful but personally I don't see any point in running IoT on a tablet. At the time of writing only the 15035 client build is available and that's now over five years old. Drivers taken from the RT 8.1 recovery image would be required along with the replacement PEP driver mentioned previously but its possible not all drivers will be compatible with IoT.
hugoBOSS1981 said:
I would personally like to give this a try, but I can't seem to get to the point of being able to install Win 10 build 15035 onto my device. I can't enable test-signing mode, nor disable bootloader with any of the jail breaks available. I get the error code 0x000000000000d (not sure i put the correct amount of zero's there), which seems to give no existing info on the net for that error code, only a few forum posts regarding the variant to that code which ends in "f" which seems to be related to the Surface 1/2 devices.
Click to expand...
Click to collapse
To enable test mode you would need either Golden Keys or the Myriachan jailbreak, unless you are lucky then the device you have might not be capable of using Golden Keys anymore. If I'm remembering correctly the Myriachan jailbreak is only useful for running third party applications under RT 8.1 and wouldn't assist in running another OS.
hugoBOSS1981 said:
I know I can format the eMMC properly via command prompt, diskpart, and dism (for Win 8.1 RT), then disable BitLocker (even though C:\ still says Bitlocker Encrypted). Yet, I just can't get the Win 10 media to work which i assume is due to secure boot. Does it make any difference if I'm using the install.wim or install.esd versions of the media?
Click to expand...
Click to collapse
Windows 10 15035 isn't available as an ESD, you would need to take the 15035 installation files and properly add the drivers to boot.wim, install.wim and winre.wim before copying them to USB and attempting the installation. CageOff seems to have installed 15035 without the use of Golden Keys but even when booted the installation of 15035 is useless because he has not added the PEP driver.
A clean 15035 if you don't have one (No drivers):
Windows 10 Enterprise Build 15035 ARMv7 : Microsoft : Free Download, Borrow, and Streaming : Internet Archive
Windows 10 Enterprise Build 15035 ARMv7
archive.org
Lumia 2520 Drivers (Extracted from RT 8.1 Recovery Media):
Lumia_2520_Drivers.zip - AnonFiles
anonfiles.com
Replacement qcpep / qcpepproxy from Lumia project for 15035:
Lumia_930_qcpep.zip - AnonFiles
anonfiles.com
I don't know much at all about the 2520 and pretty much anything I say about it could be wrong