Related
Hi
I want to transfer my own windows ce 6.0 os design to a htc prophet ?
Is it possible?
I found a nk.bin file in os release dir. is it the same as nk.nbf or it needs something to be added to it like ipl/spl?
No.
Let me just verify that I understand you correctly:
You have Platform Builder for Windows CE (not Mobile) 6 and you compiled and OS.
Now you want to put it on your Prophet?
Here is why this can not work:
a) You do not have the hardware drivers. Even if by some miracle you got the Prophet BSP (board support package) from HTC, because CE 6 architecture is so different from CE 5 on which the BSP is based you would have to rewrite them.
b) The nk.bin Platform Builder produces is in plain binary format. The nk.nbf which the Prophet bootloader can recognize is in HTC's special encrypted format so the bootloader will not read the bin.
Yes. You get it right. I know if I want to use phone features completely I need BSP. But what if I want just use some standard features? just LCD and phone features.
Also I saw nbftool that decrypt and encrypt nbf files. Can I use it to encrypt files for prophet?
You need BSP for everything, not just "full features". Every little bit of hardware that connects to the CPU requires a driver unique for your device, that includes the screen, the digitizer (touch screen), hardware keys, USB port, SD card, etc.
This is why the Linux project for these devices hasn't moved beyond booting the kernel.
There are tons of work to be done (not to say it is impossible).
I am not sure about the nbftool but even if you manage to create an image that boots best case scenario is you will see something on the screen.
But you will have no way of controlling the device - no touch screen or keys, and no way to connect to it from windows since you do not have USB drivers.
Then what are the BSPs which exist in Wince by default. There is a ARMv4. How can I use it? Can you help me?
There is ARMv4 and there is Samsung, TI, Xscale, etc. Unlike x86 - all are different. Different memory map, different GPIO, different periferials.
Better waste your time on something else. Anyway CE 6 does not have phone features at all. Compile it for your PC and see that yourself.
mamaich said:
There is ARMv4 and there is Samsung, TI, Xscale, etc. Unlike x86 - all are different. Different memory map, different GPIO, different periferials.
Better waste your time on something else. Anyway CE 6 does not have phone features at all. Compile it for your PC and see that yourself.
Click to expand...
Click to collapse
I think ARMv4 BSP in Platform Builder already have enough driver for this type of CPUs. And HTC phones are ARMv4. So normaly I should be able to build and transfer my OS to there. CE 6 have buitin drivers for modem,LCD and so on. But there is no phone. Because phone is an app that runs on CE. So if I just want to use devices like modem It is enough. The problem is nbf files ae encrypted and os.bin file should encrypt to os.nb and then transfer to device.
shariat said:
I think ARMv4 BSP in Platform Builder already have enough driver for this type of CPUs. And HTC phones are ARMv4. So normaly I should be able to build and transfer my OS to there. CE 6 have buitin drivers for modem,LCD and so on. But there is no phone. Because phone is an app that runs on CE. So if I just want to use devices like modem It is enough. The problem is nbf files ae encrypted and os.bin file should encrypt to os.nb and then transfer to device.
Click to expand...
Click to collapse
you dont really understand the problem.
ARMv4 is not a cpu, it is the ARM version 4 instruction set ....
afaik your phone has some kind of OMAP.
i don't know if CE6 has a BSP for that, but even if it does, it will still not work without modifications.
a recent example. a friend of mine wanted to download a generix xscale 25x eboot (bootloader) to a device that had xscale 255. he almost killed the whole device because the RAM memory map of this generic eboot managed to overlap with the device's original bootloader memory space in ROM. (the virtual memory mapping differed in such an unlucky way.) and so the device's own bootloader thought it had to flash it in instead of loading it into RAM and it overwrote part of itself. luckily only the splashscreen got damaged...
(and of course the device would not boot this eboot.)
that's what happens when someone who has not ever dealt with hardware and memory mappings (i.e. you) tries to play with platform builder and flashing.
also, what is this about CE6 having built in drivers for the modem (you mean GPRS?) and LCD. it doesn't have the correct ones for your device.
and, the phone is more than just an app, it also needs drivers. the modem needs it too.
all in all...i strongly discourage you trying to flash that nk.bin.
it is not even in a format that your bootloader will understand, it is MS BIN format. the nk.nb0 in same release dir (or if there is none then cvrtbin will convert it) will be the raw format that needs to be encoded for nbf, but that is far from enough because it will never boot anyway. so forget this info.
cmonex said:
you dont really understand the problem.
ARMv4 is not a cpu, it is the ARM version 4 instruction set ....
afaik your phone has some kind of OMAP.
i don't know if CE6 has a BSP for that, but even if it does, it will still not work without modifications.
Click to expand...
Click to collapse
But at least the way of using loader is possible. Like how Linux is loaded
shariat said:
But at least the way of using loader is possible. Like how Linux is loaded
Click to expand...
Click to collapse
loader, for what purpose?
cmonex said:
loader, for what purpose?
Click to expand...
Click to collapse
For running WinCE , like Linux. Am i right? Linux devs uses Loader to load Linux on Mobile devices. I think I am confused. Help me on this. My purpose is to use my own OS design.
shariat said:
For running WinCE , like Linux. Am i right? Linux devs uses Loader to load Linux on Mobile devices. I think I am confused. Help me on this. My purpose is to use my own OS design.
Click to expand...
Click to collapse
well, for linux, the drivers have to be written too. (most of the time there are existing ones with source available that can be modified, though.)
so it is more complicated than that.
shariat: writing your own OS for this hardware is not impossible, but is not easy.
I suggest you go away for a while and get hold of platform builder and an arm reference guide and read everything you can about the device, the memory structure, your dedicated hardware structure, and then start writing.
Knowing how the hardware and CPU operate is fundamental to the OS you will write. Platform Builder will give you some source code access and help give you some ideas.
This is a nearly impossible task for a hobbyist coder. I'm sure people will help you, but you need to discuss what you have in mind.
Have a look here for some other easier ideas:
http://simpleos.iroot.ca/index.php
V
Greetings Everyone,
I wanted to share with everyone what I encountered.
I didnt like windows 8. I had severe kernal issues, 4500+ errors on a brand new computer and if I sneezed BSOD occurances! If you want help in any form removing windows 8 just let me know! It can be intense since it isnt a simple 'Install Windows 7'.
I know getting into safe mode or any of the BIOS is difficult to do without the start up disk.
I did a quick write up on how to get into boot options and BIOS as well.
**Note I didnt do a search, I am feeling lazy! **
Steps to get to the Boot Options in Order to get into Safe Mode -
1- Rest your cursor in the upper right hand corner for the charm to appear.
2- On the bottom of the charm you will see ‘Change PC Settings’ Click on that.
3- In this window you will see a few options, the one want to click on is - Update and Recovery.
4- Next you will see Advanced Options. This could potentially be different depending on the version.
5- Choose the Procedure to get into ‘Troubleshoot Start Up options’ (I can not remember the exact name, it is one that will get you into boot up and start up options)
6- Now you should be able to configure into the BIOS and what needs to be corrected are 2 main steps.
A- Change Secure boot to disable
B- Change to Legacy Boot Enable
C- This is an option to disable UEFI as well if you want.
7- With these tasks done you should now see that getting into BIOS, Boot options and safe mode is feasible.
Enjoy!!
XDA has freely given to me and I will freely give back when I can. By all means, share, give thoughts, make love..lol
Or you can do it the normal way.... F2, F10, F11, F12 or whatever other key your computer has set to bios, just press it as you turn the machine in and the PC boots straight into bios not windows. I thought this was common knowledge... Seriously, takes all of a second compared to your method.
Might be useful for guys on tablets and no external keyboard though, thats about it.
That's a great suggestion. However, it won't work until you disable secure boot and enable legacy boot. Windows 8 is a different animal. I wish it was as easy as rapidly mashing the F keys..
The entire purpose if this is to get to the F mashing sequence.. This will get people to that point.
Sent from something not stock
Droidnoobi said:
That's a great suggestion. However, it won't work until you disable secure boot and enable legacy boot. Windows 8 is a different animal. I wish it was as easy as rapidly mashing the F keys..
Click to expand...
Click to collapse
Both windows 8 laptops I have tried did it first time with no modifications or altering of settings in windows. Secureboot/legacy boot *do not* prevent bios access. One of these 2 machines is my own, I certainly did not change the settings, the other was a relatives brand new machine. I also have a windows 8 desktop, however it had windows 7 previously which I updated to windows 8, so that may not be the fairest test to say that it can boot into bios directly (which it can) without altering windows 8 settings.
Windows does not have access to change the bios settings. It has no way to prevent your system booting into bios, hell thats how a PC works, load bios from RAM which then loads the bootloader from hard disk which then loads windows. Pressing F keys just interrupts the BIOS before loading the bootloader, windows doesnt even exist at this point in the boot cycle.
SixSixSevenSeven said:
Both windows 8 laptops I have tried did it first time with no modifications or altering of settings in windows. Secureboot/legacy boot *do not* prevent bios access. One of these 2 machines is my own, I certainly did not change the settings, the other was a relatives brand new machine. I also have a windows 8 desktop, however it had windows 7 previously which I updated to windows 8, so that may not be the fairest test to say that it can boot into bios directly (which it can) without altering windows 8 settings.
Windows does not have access to change the bios settings. It has no way to prevent your system booting into bios, hell thats how a PC works, load bios from RAM which then loads the bootloader from hard disk which then loads windows. Pressing F keys just interrupts the BIOS before loading the bootloader, windows doesnt even exist at this point in the boot cycle.
Click to expand...
Click to collapse
Then your settings or something must be different because in order for me to even do anything at all I had to follow specific steps, turn legacy boot on, turn secure boot off..
I am grateful you have an easier time then I did.
SixSixSevenSeven said:
Both windows 8 laptops I have tried did it first time with no modifications or altering of settings in windows. Secureboot/legacy boot *do not* prevent bios access. One of these 2 machines is my own, I certainly did not change the settings, the other was a relatives brand new machine. I also have a windows 8 desktop, however it had windows 7 previously which I updated to windows 8, so that may not be the fairest test to say that it can boot into bios directly (which it can) without altering windows 8 settings.
Windows does not have access to change the bios settings. It has no way to prevent your system booting into bios, hell thats how a PC works, load bios from RAM which then loads the bootloader from hard disk which then loads windows. Pressing F keys just interrupts the BIOS before loading the bootloader, windows doesnt even exist at this point in the boot cycle.
Click to expand...
Click to collapse
Droidnoobi said:
Then your settings or something must be different because in order for me to even do anything at all I had to follow specific steps, turn legacy boot on, turn secure boot off..
I am grateful you have an easier time then I did.
Click to expand...
Click to collapse
@Droidnoobi is correct, you have to disable secure boot on the UEFI to access the BIOS. Otherwise, Windows boots too fast for you to press the keys. I believe it boots in 200 miliaseconds, which is too fast for anyone to press a key.
I did manage to disable secure boot and driver signature enforcement and enable legacy boot. However, I still can't install a second OS on my HP laptop. I've got both Ubuntu and Android (x86) installed, but they won't boot. Any suggestions?
Ph0enix_216 said:
@Droidnoobi is correct, you have to disable secure boot on the UEFI to access the BIOS. Otherwise, Windows boots too fast for you to press the keys. I believe it boots in 200 miliaseconds, which is too fast for anyone to press a key.
I did manage to disable secure boot and driver signature enforcement and enable legacy boot. However, I still can't install a second OS on my HP laptop. I've got both Ubuntu and Android (x86) installed, but they won't boot. Any suggestions?
Click to expand...
Click to collapse
Funny that this *stock* HP laptop which came preinstalled with windows 8 allows me to do it without modification.... It most certainly does not boot in 200 milliseconds, add another 0, plenty of time to press a key.
Duplicated on several machines now. I am yet to find a single one requiring this so called hack.
SixSixSevenSeven said:
Funny that this *stock* HP laptop which came preinstalled with windows 8 allows me to do it without modification.... It most certainly does not boot in 200 milliseconds, add another 0, plenty of time to press a key.
Click to expand...
Click to collapse
I've got an HP Sleekbook 15". It booted so fast that I couldn't boot the BIOS. I had to disable secure boot to access it at all.
Don't know about you 2 but I needed to go to a secret retreat hidden in some mountains to meditate in order to acquire the uber l33t haxxor skills of pressing F10 as soon as the display backlight turned on.
I did however need uber l33t haxxor skills to get youtube embed working so have a link instead: http://youtu.be/6_3OCjMY_pg
For whatever reason XDA instead of neatly embedding my youtube video has opted for display chunks of HTML no matter what format the youtube URL is given as. Cant really be bothered to argue with it.
SixSixSevenSeven said:
Don't know about you 2 but I needed to go to a secret retreat hidden in some mountains to meditate in order to acquire the uber l33t haxxor skills of pressing F10 as soon as the display backlight turned on.
I did however need uber l33t haxxor skills to get youtube embed working so have a link instead: http://youtu.be/6_3OCjMY_pg
For whatever reason XDA instead of neatly embedding my youtube video has opted for display chunks of HTML no matter what format the youtube URL is given as. Cant really be bothered to argue with it.
Click to expand...
Click to collapse
Okay, I can access the BIOS. However, now I can't get a different OS to boot. Anytime I try to boot Ubuntu or Android (x86), it fails to start and tells me that the .mbr file is missing, even though I can see it in Windows Explorer. Any thoughts?
Oh, and my computer threw a hissy fit when I pressed F10 at boot. It kept beeping and beeping and beeping quite loudly. Maybe this is why I am not allowed to have nice things At least I was able to access the BIOS.
Ph0enix_216 said:
I've got an HP Sleekbook 15". It booted so fast that I couldn't boot the BIOS. I had to disable secure boot to access it at all.
Click to expand...
Click to collapse
Try holding the power button until it powers off instead of shutting down. That should at least slow down the Windows boot up. The default windows power off utilizes a form of hibernate. Or you can disable hibernate entirely, there are instructions online in various places.
I don't really have any problems with getting into bios myself.
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?
There seems to be a way to instal a uefi bios in the zenfone 2, this seems to be possible with intel manufacturing flash tool. Did anyone try this yet on a zenfone 2?
In a few weeks I will give it a try aswell unless there are negative results already. This may be the way to instal linux or windows without the android system and a vm.
Don_prince said:
There seems to be a way to instal a uefi bios in the zenfone 2, this seems to be possible with intel manufacturing flash tool. Did anyone try this yet on a zenfone 2?
In a few weeks I will give it a try aswell unless there are negative results already. This may be the way to instal linux or windows without the android system and a vm.
Click to expand...
Click to collapse
You have any links for this? Am very interested.........
Sent from my ASUS_Z00AD using XDA-Developers mobile app
no video drivers for windows afaik
UEFI bios
Well the idea originated from here:
Cant post the ##### link
toms guide: install-windows-android-intel-tablet
::
Yes,you can(but it is windows 8.1 with bing).find roms on web.I find one.You need:intel manufacturing flash tool to1.12,then find a windows 8.1 rom,an OTG usb,ADB tools(can use 15 seconds adb installer),and UEFI BIOS.
steps:
1:use intel manufacturing flash tool to flash to 1.12
2:install UEFI to your android tablet.
3ut your windows 8.1 rom to OTG usb
4:wait
5ONE!
::
Also
::
this IS possible especially now that there is more and more INTEL CPU (baytrail / atom) for android tablets and all in one pcs, look:
Cant post link (unfortunatly broken)
the tool: cant post link
The problem is, the instructions are not very well organized and put out.
::
That one is not related to the zenfone 2 but for a similair device, however its mentioned in the thread. Problem is the brazilian source of the tool is down. thats where my research till now stopped.
The gpu is not directly a concern. I think first goal is to get uefi on it at all.
I believe there is drivers from other tablets and phones, I believe someone mentioned a dell tablet but I can be wrong.
What's the difference between UEFI and old method of installing Windows in dual-boot mode?
Zhabishe said:
What's the difference between UEFI and old method of installing Windows in dual-boot mode?
Click to expand...
Click to collapse
As I know, there is no old way of dual booting. In the UEFI you can possibly create a seccond instance to boot to with gnu grub. The only other way I know is via a VM, this has the disability with the drivers and no direct access to the hardware. This makes use of the gpu near impossible and will always leave resources to android wich has to run in the background.
Don_prince said:
As I know, there is no old way of dual booting. In the UEFI you can possibly create a seccond instance to boot to with gnu grub. The only other way I know is via a VM, this has the disability with the drivers and no direct access to the hardware. This makes use of the gpu near impossible and will always leave resources to android wich has to run in the background.
Click to expand...
Click to collapse
Thanks for clarification here. Yeah, I thought about KVM from this thread http://forum.xda-developers.com/zenfone2/general/zf2-running-windows-7-using-kvm-t3153299 which seemed a bit overcomplicated and more proof-of-concept thing, sort of similiar to running Windows 9x via DosBox on Symbian smartphones years ago. They also run into problem with unobtainable gpu drivers.
I believe there is drivers from other tablets and phones, I believe someone mentioned a dell tablet but I can be wrong.
Click to expand...
Click to collapse
As I mentioned above and keeping mind those news about Intel not being happy with their SoCs perfomance on market it could possibly become a problem to get support on their side. Correct me if I am wrong, that's just my thoughts
I have cracked open a android, how do you call it, bios and am compiling a uefi bios now with the information from the droidbios and another uefi bios, Well see how this ends, This will take a lot of time.
Curious, any headway on this yet?
Progress is slow, I am working beyond my knowledge, so every step needs to be researched. Next to that at this point (rounding off university) my time is quit limmited.
Verry interesting! But I feel like it ended bad
Other options are coreboot or libreboot.
Man what happened u very-hard-briked it ?
Been too bussy to spend more time on it, and since my other cellphone died, my zf2 is my daily driver again...
Oh ok.
I think that the hard-brick is the biggest problem. We need a way to hard-flash a boot firmware if we hard-brick. To try many times
xdaxuser said:
Oh ok.
I think that the hard-brick is the biggest problem. We need a way to hard-flash a boot firmware if we hard-brick. To try many times
Click to expand...
Click to collapse
so why did nobody code an UEFI bios as a part of a modded twrp with some failsafe measures (for early builds) zenfone 2 with a full windows would be amazing
News from the other tread.
On the asus web there is the kernel sources!
Look like zf2 uses Bootstub.
2/18 Update:
USB charging and controller works, audio probably works. Here's some update on this project:
Battery
Put C:\DPP and C:\EFIESP back. Nokia's driver reads C:\EFIESP\Battery.json in kernel mode (WTF). If you have NokiaEnergyDriver.sys and other PMIC/PEP/MIPI BIF (on some models) drivers installed, you should get battery show up.
Sign drivers?
Yes. Sign everything to prevent bad things from happening. I used a commercial certificate for conveience , but you don't have to do that. Here's a handy script that generates a self-signed certificate and installs it on your phone: https://gist.github.com/imbushuo/4de89ad18a0f538d8ebd18bf6daca56a
Download it, run it as administrator and specify ImageDir to your phone's partition (in mass storage mode). Then sign all your drivers binaries (and catalogs as well) with the fingerprint provided.
When signing your drivers, remember timpstamp all drivers. DigiCert's help documentation is useful for signing binaries.
Turn off UMCI
See https://forum.xda-developers.com/showpost.php?p=36394268&postcount=222. Set UMCIAuditMode key to allow all desktop applications and UMDF drivers load.
Make USB work
You will need several supplemental drivers from Windows Phone: BattFltr.sys, CAD.sys, ufx01000.sys, ufxsynposys.sys (or ufxchipidea.sys, depends on your chipset). Copy registry keys (HKLM\ControlSet001\Services and HKLM\ControlSet001\Enum\ROOT\CAD / HKLM\ControlSet001\Enum\ROOT\BattFltr) add supplemental WDF registry keys. Some files are attached as attachments, so you can take a look to get some idea about that.
Make Windows Store Apps work on unsupported resolution
See my blog post.
---------
While this project is not totally finished (e.g. No Battery status/charging unknown, no cellular, no audio), I decided to post this thread as many people asked me about the tutorial. This is just a brief tutorial, you need to have plenty of time on this to make this happen. Be careful as some steps are very dangerous.
This tutorial is provided AS-IS, without any implicit or expressed warranties. By reading this brief tutorial, you are agreed that you are taking your own risk trying this. I am not responsible for any possible consequences of installing Windows RT or other non-Windows Phone OS on Lumia phones. If your phone ships with Windows 10 Mobile, then this tutorial might not fit you. You can try drivers from other models, but I have no guarantee on this.
General workflow
- Unlock your phone with WPInternals 2.4
- Enter mass storage mode, copy registry files from MainOS partition
- Copy files from DPP partition
- Download Windows RT 8.1 ISO (publicly available on Internet, Google it)
- Download a Lumia 2520 recovery image for some files (I will post these files later)
- Download a Windows Phone 8.1 firmware for your phone
- Extract drivers, re-assembly INF files
- Patch some drivers (see my note)
- Self-sign some drivers (see my note)
- Make sure you know what you are doing: Delete MainOS and Data partition, create new NTFS partition for Windows RT. Do not touch other partitions.
- Apply system image (dism works fine)
- Copy DPP files back (C:\DPP)
- Modify sysprep tasks (see my note)
- Apply BCD configuration
- Boot
- Let OOBE fail once
- Go to mass storage mode again, mount registry and force OOBE run again
- Have fun
Notes on this project
ACPI
Reading ACPI DSDT table will help you understand your phone architecture. ACPI tables are located in PLAT partition. It is easy to extract them with 7-zip (after converting FFU to VHD). To decompile dsdt.aml, you need to download iASL tool, which is available on Internet.
Certain devices, like touch screen or panel, require other devices have driver loaded and enabled. This is not shown in Qualcomm's ACPI implementation. In my case, I need PEP, PEP 3rd, GPIO, BAM, I2C Device, QMUX, Shared Memory drivers loaded to make touchscreen work. It varies by model.
Re-assembly INF files
Mount SYSTEM registry from your phone or FFU, go to DriverDatabase\DriverPackages\<Some Driver Package>, each key in driver package key matches INF sections respectively. See some driver INF files to get some idea.
Remember to check ControlSet001\Service for additional information if necessary. If you are working on Windows Phone 8.1 firmware, check \Windows\System32\Packages to make sure you've got correct files and registry configs. These files are gzipped.
Patch drivers
Certain drivers read DPP partition for device-specific calibration information. While Qualcomm shares the codebase between Windows RT and Windows Phone, DPP partition is handled differently between platforms. You can search Unicode string "PhoneNT" to determine whether drivers read DPP or not.
To fool drivers think they are living in Windows Phone, you can create another multi-string value in the ProductOptions key. I created a value called "AnotherSuite" and filled "PhoneNT" in. Then I modified all "ProductSuite" Unicode strings in drivers to "AnotherSuite". Remember to re-calculate linker checksum (dependencies) and PE checksum.
This is critical to make wireless (Wi-Fi and Bluetooth) subsystem work.
Graphics
DO NOT use user-mode driver module from WP on Windows RT. The Windows Phone Qualcomm GPU driver does not implement DirectX 9, which is required by Windows desktop. Using WP UM driver will crash DWM.
To correctly enable GPU acceleration, use kernel driver and decoder module from your firmware, and user mode driver from Lumia 2520's recovery image. At least this works on Lumia 640 XL.
Touchscreen
Touchscreen works, however, WP driver reports wrong metric system to Windows RT. To workaround this, modify SYSTEM\TOUCH key, make some value larger than expected. See my value for 640XL in attachment.
Remove some sysprep tasks
Remove BCD and WinRE specialization and generalization tasks from sysprep task definition. OOBE will fail still. Boot to mass storage mode, mount SYSTEM registry, change setup type to 1 (see your current OS for ideas about other values), change program path to oobe\msoobe.exe. You should be able to see normal OOBE then.
BCD and Driver Signing
Test signing should be on. Disabling integrity check is recommended (though documentation says this key is ignored prior to Windows 10). Copy catalogs to the new OS, and self-sign drivers you patched.
Kernel Debugger
To enable WinDbg KD, modify your phone BCD:
Code:
bcdedit /store <Path> /dbgsettings usb TARGETNAME:WOATARGET
bcdedit /store <Path> /set {Your OS GUID} Debug On
Connect your phone to PC, start WinDbg, USB kernel debugging, target name "WOATARGET".
Have fun with Windows RT on Lumia, I am going to continue working on audio and battery
Follow
Ty Imbushuo , GREAT WORK
didnt you forgot to make efiesp guid to a efi partition else bcd cant be updated
Is there a way to patch the kernel or a bypass to avoid SECURITY_SYSTEM BSOD on MSM8960 devices?
Thanks for your work. I hope to get a newer Windows Phone soon and try Win10PE, I'm working on a custom shell that hopefully grants it a good experience on handheld devices since we lack ARMv7 ShellExperiences
J0SH1X said:
didnt you forgot to make efiesp guid to a efi partition else bcd cant be updated
Click to expand...
Click to collapse
Qualcomm's firmware is weird, so I didn't do that. (They hard-coded something) Maybe I will try it later with a dev board and see what will happen.
Fantastic job :good:
Is it possible to enable a second external monitor via Miracast ?
What about bluetooth keyboard and mouse ?
Lumia 950/XL should also support 2x monitors ( DisplayPort/HDMI via USB-C ).
It also has more RAM and might run apps better than L640.
imbushuo said:
Qualcomm's firmware is weird, so I didn't do that. (They hard-coded something) Maybe I will try it later with a dev board and see what will happen.
Click to expand...
Click to collapse
thats weired on my 930 this is NEEDED to get rt to boot but weired enough my 640 lte doesnt boot it at alll but sadly i dont get how to reassamble the inf files (im litterally just comparing my compiled touch driver inf with the registry of my 930)
I can not find the windows rt on the Internet. Can I send the file link download?
imbushuo said:
While this project is not totally finished (e.g. No Battery status/charging unknown, no cellular, no r FFU, go to DriverDatabase\DriverPackages\<Some Driver Package>, each key in driver package key matches INF sections res
Click to expand...
Click to collapse
I use google translate so it's hard to follow, it's great when you have a video tutorial, everything is more intuitive and easy.
INF files Qualcomm ARM-based View attachment Inf.zip
prokakavip said:
I use google translate so it's hard to follow, it's great when you have a video tutorial, everything is more intuitive and easy.
Click to expand...
Click to collapse
If you are an end user I would recommend waiting for WPInternals partition dumps for your device
I knew this solution... so they cant make general Qualcomm drivers never. Device specification is nightmare. Better get a hammer and deepmagic
Thank you for all the effort of going through this and providing the information.
Can somebody whoever upload fixed registry files and drivers? i was able to follow all steps successfully (except these parts) but on first boot i just get a blue screen with a sad smiley.
Also, i assumed you meant applying the install.wim image via DISM from the Windows RT 8.1 ISO.
(For those who need more help with this, Google: "Append, apply, and export volume images with a Windows Image (.wim) file",
i'm not allowed to post links due to post count).
Die Anleitung ist jetzt auch in deutsch verfügbar und hier zu finden:
Windows RT 8.1 auf ein Lumia installieren
WPVision.de said:
Die Anleitung ist jetzt auch in deutsch verfügbar und hier zu finden:
Click to expand...
Click to collapse
I registered and it still said i'm not allowed to visit the forum because i dont have permission.
D-V-D-K said:
I registered and it still said i'm not allowed to visit the forum because i dont have permission.
Click to expand...
Click to collapse
That's correct, because you did not follow the guidelines.
The activation for this area is done manually by your first post.
Samuelgames said:
If you are an end user I would recommend waiting for WPInternals partition dumps for your device
Click to expand...
Click to collapse
Can you upload your partition dumps for 640xl?
Removed. Sorry I was being rash.
spavlin said:
INF files Qualcomm ARM-based View attachment 4410518
Click to expand...
Click to collapse
but theese inffiles arent redone from registry
for example touch driver is missing
imbushuo said:
- Download a Lumia 2520 recovery image for some files (I will post these files later)
Click to expand...
Click to collapse
Use at your own risk!
Some Lumia 2520 Firmware And Driver Update 10. 6. 2014:
Code:
http://au.ds.download.windowsupdate.com/c/msdownload/update/driver/drvs/2014/03/20623735_d3143757b17f94d00f53dc6f3f4dbdf48c36430e.cab
http://au.ds.download.windowsupdate.com/c/msdownload/update/driver/drvs/2014/03/20624060_4b5dec4829bf5e013bf5e6c045a4ed9367afe88d.cab
http://au.ds.download.windowsupdate.com/c/msdownload/update/driver/drvs/2014/03/20624064_70ea6951b8f7c7d72963c38e302356f46642ec85.cab
http://au.ds.download.windowsupdate.com/c/msdownload/update/driver/drvs/2014/03/20624552_3c10b74a53f010a90539ea1e606f562d65a03082.cab
http://au.ds.download.windowsupdate.com/c/msdownload/update/driver/drvs/2014/03/20626644_7f0f6945d5e0e19e78b3794490990145b98e2c0c.cab
http://au.ds.download.windowsupdate.com/d/msdownload/update/driver/drvs/2014/04/20639225_555ea122b93d34720513db1b344254a0a69a158c.cab
http://au.ds.download.windowsupdate.com/c/msdownload/update/driver/drvs/2014/04/20639552_08956ac77c46334650fc675794d58325f279ddbb.cab
http://au.ds.download.windowsupdate.com/c/msdownload/update/driver/drvs/2014/04/20640693_4d4f789e1349e350324fb7e31b60514ae191cb46.cab
http://au.ds.download.windowsupdate.com/c/msdownload/update/driver/drvs/2014/04/20642401_1278d3d9f4ae8d1903ec0c6f0861ec9912139b96.cab
http://au.ds.download.windowsupdate.com/c/msdownload/update/driver/drvs/2014/04/20643591_beca8afddf93a8679f6e875f5abfc44f9395975a.cab
http://au.ds.download.windowsupdate.com/c/msdownload/update/driver/drvs/2014/04/20643598_4a154479fe2ad83eef04c99e96e44b0e88efce8e.cab
http://au.ds.download.windowsupdate.com/c/msdownload/update/driver/drvs/2014/04/20643814_2d9a86009238af018f92aa76a9be453ef9231424.cab