Hi,
I was just wandering if an auto-configuring ROM exist. What I mean is so if there was a ROM (let's just call it Cool), and it could be used on any device, and comes in different formats (zip, exe, cab, nbh, nbf), and once it is executed/launched it flashes on your phone (Hermes in my case) and then it reboots and boots up Cool. But because it doesn't have any drivers for the phone, it does a "search" and finds all the hardware on the device, and estimates what that hardware is for. Once the "search" is finished, the phone starts to generate drivers for use with the device's hardware that it found during the search, and then you are able to use Cool on your device. I have seen that on Windows(XP), when I reinstall it I have to install the drivers again, but when I boot Ubuntu from a Live CD, it already has the important drivers (LAN, WLAN, Sound, etc..),so is this possible with a phone?
I'm not a developer per-se, though have cooked ROMs in the past.
What you're talking about I'd call a "live" ROM Kitchen
My initial thought is that your idea is a good one, though in the past had been an impractical/impossible approach due to ROM file size... since every driver for every device would have to be present.
This idea, if possible, would probably have to be implemented/run from a PC.
Why don't you develop it? If you could do it you'd raise a lot of eyebrows, LOL.
Oh, and PS - nope it doesn't exist in the case that you didn't get that
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
Hello,
I've been googling around for a workaround but I cannot seem to find one that actually works. The problem is, when I try to connect my phone to the PC and, for example, want to flash it with an official rom - it simply cannot find it. It can find the SD card when I mount it.
When I put it in, Windows attempts to install a few drivers but fails at the ADB. According to several sites, I can just use the one from HTC Sync or from the Android SDK. It installs fine but it still doesn't seem to be able to contact my phone. I cannot sync it either.
Anyone got an idea? I seem to be on my last nerve.
I dont have any problems here. What windows beta release do you use?
Final version. Released today. It's Windows 7 Professional.
First, set the phone to debugg mode...
Ok here we go (at least it works for me)...
1.- Remove the drivers actuaslly installed (it might get tricky, as I don't know exactly how to remove the registry keys)
2.- Once you have cleaned windows from the drivers, connect the phone to the computer and let it recognize everything (Probably it would not recognize the ADB drviers, so far we are good)
3.- After the drivers are installed, go and check in control panel/Devices Administration (or something like that... I have Windows in spanish so I don't know exactly how is called on english... By the way, sorry if my english sound a little bit weird =P..)
4.- Here you should see probably a device as "not recognized" or what ever is called... Here is the part where you need to select the driver manually.
5.- Check the phone driver folder (you should have it, if you don't get them)
6.- When you see the different options, select the one called HTC Dream Composite ADB Interface
7.- You are done =D...
I hope I made it clear enough for you...
If you have any doubt, add me to MSN xnofrostx - hotmail.com (I don't put the @ because I hate spam xD so you should add only the xnofrostx =P...
Hope you can get it to work...
I couldn't, for the life of me, get it to work so I put Windows XP on a vmware and flashed it through there. Works wonders.
Sorry for not being able to help.
I run Windows 7 Evaluation copy. I have had no problems. In fact there was nothing for me to set up, it just saw it on first attempt.
trillex said:
Hello,
I've been googling around for a workaround but I cannot seem to find one that actually works. The problem is, when I try to connect my phone to the PC and, for example, want to flash it with an official rom - it simply cannot find it. It can find the SD card when I mount it.
When I put it in, Windows attempts to install a few drivers but fails at the ADB. According to several sites, I can just use the one from HTC Sync or from the Android SDK. It installs fine but it still doesn't seem to be able to contact my phone. I cannot sync it either.
Anyone got an idea? I seem to be on my last nerve.
Click to expand...
Click to collapse
I'm on Windows 7 Ultimate. Driver from AndroidSDK and HTC Sync works perfectly for me. I can access everything except cannot sync with HTC Sync.
Rogers Magic
Rooted
CyanogenMod 4.1.9999
I cannot sync either, when installing the sync program it gives an error but continues installation, then my phone says it cannot detect htc sync on my computer, but im gonna try this link http://www.mydigitallife.info/2009/08/24/workaround-for-htc-hero-sync-problem-in-windows-7/
trillex said:
I couldn't, for the life of me, get it to work so I put Windows XP on a vmware and flashed it through there. Works wonders.
Click to expand...
Click to collapse
I'm glad you decided to upgrade back to XP!
IE_DSM said:
I'm glad you decided to upgrade back to XP!
Click to expand...
Click to collapse
LOL, Windows 7 is a damn nice release and a lot faster than both xp and vista compared to the hardware available at the moment off release.
i am also using windows 7 beta and final
no issues at all. and i also think, that win7 is really good piece of software. far superious to win xp
Please someone has to be able to help me! My phone as of three days ago, HTC One X, had drivers working completely fine. As of a couple of days ago my computer has just stopped seeing my phone! Whenever I try to install the drivers, I get an error that says "Windows tried installing the driver but failed. The request is not supported." I've searched everywhere and have not been able to find a solution. I was just trying to copy files between my computer and phone but I couldn't do it. I'm sorry if this is the wrong area, but it is a Windows 8 machine with this issue. The thing that baffles me is the same exact drivers work on my Windows 8 laptop. I have a screenshot attached of the error, as well.
Please note that XDA-Devs is not a tech support forum. Unless you were doing some kind of hacking on your PC (or phone) that you would expect us to understand but not a more traditional environment, this is not a good place to ask such questions.
With that said, the first thing I'd try is completely purging the phone's drivers from the PC (uninstall them, and remove the files), preferably while the phone is disconnected. You can do this in Device Manager. Then, reboot the PC. After reboot, re-connect the phone and see if you can get the drivers to work now.
GoodDayToDie said:
Please note that XDA-Devs is not a tech support forum. Unless you were doing some kind of hacking on your PC (or phone) that you would expect us to understand but not a more traditional environment, this is not a good place to ask such questions.
With that said, the first thing I'd try is completely purging the phone's drivers from the PC (uninstall them, and remove the files), preferably while the phone is disconnected. You can do this in Device Manager. Then, reboot the PC. After reboot, re-connect the phone and see if you can get the drivers to work now.
Click to expand...
Click to collapse
Sorry about that, but I'll try that.
Sent from my HTC One X using xda app-developers app
I have no idea in which section to write this, so General seams like the best choice.
I have a Galaxy Y testing device with a broken boot.img. I am trying to get Odin working in Windows 7 in order to flash a new boot.img to this device, but I can't get the Samsung USB drivers to work and my Windows knowledge is now that great as I mostly work on Linux computers, but no fastboot on Samsung devices.
There are two drivers listed in the Device Manager. The Regular Samsung USB drivers, and something called Samsung USB CDC. It's the CDC I seam to have issues with. It just shows an error message that states "The device could not start (Code: 10)". I have already talked to Samsungs online support, but there is not much support to find there. They know nothing about Windows or how to get anything working on it. And google's search engine, which usually is the best friend for something like this, did not come up with much either.
I should mention that I run Windows in VirtualBox. However, I already have HTC Sync Manager fully working with an older HTC device, so this is not a VBox issue. Also, Windows do find the device just fine, it just can't start one of the drivers.
I have tried installing Kies. I have also tried installing other separate driver versions. Nothing is working.
Search the forums for Naked Drivers, its a complete driver package for a lot of android devices.
Give em a try.
I would post a link but my post count is as such that I cannot at this time.
WooHooGuy said:
Search the forums for Naked Drivers, its a complete driver package for a lot of android devices.
Give em a try.
I would post a link but my post count is as such that I cannot at this time.
Click to expand...
Click to collapse
I love the idea of a multi driver for all devices, much like on my linux boxes, so thanks for that. However, I get the same issue and same error message. I will try to reinstall windows and see if that will work. It has been many many years since I ran windows as my daily OS, but I do remember that formatting was the best way of fixing issues with it. If this is still no go, I will try to put windows directly on my netbook to see if this could be a Virtual problem anyways, but I don't think so. USB stuff is working fine on the Virtual OSX.
Will report back later
EDIT:
Nothing is working. All I have installed, is the naked driver. When I plug-in my HTC Desire or HTC Wildfire S, the driver is working fine. But when I plug-in the Galaxy S3 or the Galaxy Y, I get the "The device cannot start (Code: 10)".
So HTC devices are working, but Samsung is not. The same problem I had with separate HTC and Samsung drivers.
try the one from my link,its latest usb driver exe from kies,worx on win8 64bit too.
http://forum.xda-developers.com/showthread.php?t=1927769
-CALIBAN666- said:
try the one from my link,its latest usb driver exe from kies,worx on win8 64bit too.
http://forum.xda-developers.com/showthread.php?t=1927769
Click to expand...
Click to collapse
Thanks, but I have tried that version, and the one newer (1.5.23). I did manage, efter some reinstalls, to get 1.5.18 (I think is was) to work on the real installation. So maybe my issue is with virtualbox, I just can't see what. I have disabled everything in linux that could block something, I have disabled firewall and such on the virtual windows, I have tried checking and changing perms on the linux device nodes, and tried running VB as root.
At least I got the Galaxy Y running again, but I don't like having unresolved issues so VB is going down
I have a Clarion car radio running WinCE 6.0 (pure, no Chinese hybrid). Been toying around with it for a bit, and apparently messed it up somehow.
Normally, the device would run \Hard Disk\SW_Update\UpdateUtility.exe, if a USB stick (mounted at \Hard Disk) is present during boot. This utility allows to replace the stuff stored in \NandFlash with an image on the SD card. This is simply a zip file, so easy to mess around with. Which I did, and everytime I went too far I just reflashed an older image over it using this update mechanism.
Now, the update mechanism no longer showed when the device boots with the update utility on the inserted USB stick. It still booted into CE desktop, so I figured let's go back and start from scratch. I manually started the UpdateUtility.exe and placed back the original firmware back, update completed successfully.
Rebooted the device, and it "hangs" at the manufacturers splash screen. Their main menu never shows. The update utility is no longer invoked. The SD card with \2577\autorun.exe trick doesn't work either, I'm not entirely sure whether it ever did. This effectively means I can't do **** with the device. I know that it does not completely hang, if I insert an unknown USB device I get a WinCE style popup asking for a driver (which I can't enter, there is no keyboard :laugh. When I plugin a keyboard it is not asking for a driver, so I believe there's at least some form of a HID driver present, but the keyboard doesn't seem to work.
Now, what are my options for unbricking this device? I've analysed the device before and all prerequisites for making activesync connections over USB are in place, except, there's no external USB client port available on the device. The circuit board contains a 4-port USB chip though, but I haven't been able to find a second (hidden) USB port yet. Do these devices typically have a USB client port used in their development process? I haven't been able to find it after several hours measuring on the board.
Also, the board appears to feature a JTAG connector, but I believe this is to be used to program a second microcontroller on the device, which handles the LCD, the external buttons and retractable screen.
Any ideas?
zzattack said:
The SD card with \2577\autorun.exe trick doesn't work either, I'm not entirely sure whether it ever did.
Click to expand...
Click to collapse
The well known \2577\autorun.exe trick in 99% doesn't work: most OEMs have their own method.
Perhaps this will bring you a step further:
http://forum.xda-developers.com/showthread.php?p=49355285#post49355285
jwoegerbauer said:
The well known \2577\autorun.exe trick in 99% doesn't work: most OEMs have their own method.
Perhaps this will bring you a step further:
http://forum.xda-developers.com/showthread.php?p=49355285#post49355285
Click to expand...
Click to collapse
Came across your pretty nice compilation of methods, but it seems they are all disabled on the device
Anyway, it appears there's multiple updating mechanisms on the device, using an SD card prepared for a 1-year older generation device I could flash some things with a completely different updater interface. Sadly, this updater asks no confirmation whatsoever, doesn't seem to check update contents, and has no way of verifying the correct image is written to a compatible device. Now, the 1-year older generation device was mostly compatible, except for the bluetooth module. At least I got it unbricked, and the 'old' firmware upgrade mechanism worked once more.
Problem is, for my specific radio no software update has been released, so I don't have any perfectly compatible firmware files for it. Long story short, in my trying I put on a very incompatible firmware and now the thing no longer turns on
Which is really a good excuse to buy one of these so that I have a sane way of flashing at least that part of the board
Also I contacted the manufacturer and they immediately sent me the correct image. Guess I should have done that sooner ... Will be continued, probably (hopefully :angel
How did you unbrick your device? I have also the nx702e and it freezes on manufacturer's screen.
I ve made a mistake and I did 1st os update and then software update and it froze on mpu update.Then it booted only on wince and when I renamed the folder ce69 backup to ce69 maybe some file it was missing from there when I reset it stucks on manufacturer logo.help please!