Related
hello..
is there a chance to do it ?
writting the nb1 file to SD card directly from the PPC device its self without need to buy a card writer/reader ?
why not ? out PPC can write & read the card, so any chance to do it ?
best regards
Yes, this possibility exists. Nobody has written code to do it though.
We're toying woth the idea of a whole new tool which allows many more operations directly to the device. If only we could find either a lot of time, or some sharp volunteer coders with too little on their hands...
yes, it is possible. just didn't have the time to write a program to do it yet.
I did write some test code, to see how it works
source + exe here
btw, warning - the write function will erase what ever was on your sdcard.
hello again..
well thank u all XDA developers, i wanna know is it just a raw writting of nb0 & nb1 on SD card starting from block 0 to the end of nb1 ?
best regards
for 5.14, 5.15, 5.22 the first sector contains a string specifying the cardtype:
"HTC$WALLABY00" - bootloader ( nb0 )
"HTC$WALLABY11" - wince image (nb1)
"HTC$WALLABY22" - bootloader(nb0) + wince image(nb1)
"HTC$WALLABY33" - diagnostics card(nb2)
"HTC$WALLABY44" - gsm
"HTC$WALLABY55" - gsm + wince image
starting at the 2nd sector, the data is written.
these last 2 we have not experimented with yet.
for 5.17 the layout is a bit different, the first sectory contains the string 'HTC FLASH KEY', the 2nd sector starts with the md5sum of the cardid, the 3rd sector has a 4 byte counter value, the 4th the md5sum of this counter, the 5th contains 'N'
starting at the 6th the about HTC$WALLABY string + bootloader/wince images are written.
a bootloader is always 512 512byte blocks or 256k
a os image is always 65024 blocks, or 31.75M
see xdarit source for more details
thanx alot XDA developer
my WALLABY boot loader is v5.15
I'm on my way to write xdirt for PPC, many thanx for ur information.
best regards
Hi...
Can't wait to get my hands on your code...hoping it works with 5.17.
Is the idea behind your program to prepare the SD card with the .NB0 / .NB1 files so we can upgrade our PPC's to 2003 through an ActiveSync connection?...yes, I'm a complete novice at this...sorry
G
I'd like to toss this out for discussion. This might already exist, it might not.
Microsoft had system builders use a Disk Differencing technique to extract what exactly had changed after installing applications and customizations.
First, we'd install the OS and create a base image.
Second, we'd install the apps & customizations we wanted for our customers.
Third, we'd create another image. An app would then compare these two images and determine what files were added/changed and what registry additions, deletions, alterations were performed.
I'm hoping we can do the same for ROM upgrades.
1. OLD ROM - Base image.
2. Install apps and customizations - Image "Apps". This will give us our customizations.
3. Install new ROM - NEW base image created. Compare to OLD ROM base image to see what has changed (that we need to look out for that our APPs image might adversly change).
4. Apply Apps image to restore all customizations & applications.
Ideas anyone?
The theory sounds good.
Maybe buzz can comment?
The theory is very feasable, ive used similar building Win PE rescue disks, you have a app that gives you the base bootable image made from a Win XP install CD. then you add home made "modules" ie, your installed apps or networking capabilities etc. then it makes an image for you to use,
that cant really be that difficult to do the same for Win CE,
Ive also seen a M$ webcast thing where the guy took 45 mins to build an entire image for a win ce device,
so yer, it is very feasible that such dev apps exist, after all, they were made and then sold to the hardware vendors before ever being a rom image.
check in msdn for win ce 5 stuff, its a very intresting read, :shock:
it is a good idea, but only for linear ROMs, where each file has always it's own and same place in the rom and such rom is not compressed.
hmm...
but you can do partial rom upgrades with wm5 roms...
...and it would be possible to make registry diff + DOC Storage partition backup, where you actually install programs (so called \Device) and userdata.
buzz
buzz_lightyear said:
it is a good idea, but only for linear ROMs, where each file has always it's own and same place in the rom and such rom is not compressed.
hmm...
but you can do partial rom upgrades with wm5 roms...
...and it would be possible to make registry diff + DOC Storage partition backup, where you actually install programs (so called \Device) and userdata.
buzz
Click to expand...
Click to collapse
Ok...Since I'm not a programmer and somewhat of a noob with respect to WinCE, I am NOT constrained by what might be a logical limitation to a programmer or someone in the "know". So, below is my thinking ... outside of the box (er, PDA) style.
But first, I need to grasp further Buzz's post above about the locations of things in ROM. Does this mean that there isn't, for lack of a better example, a FAT for the ROM? That every individual thing is expected to be at some specific, static location that can't change? If so, I see your point. But that tells the system that this location is static? Also, doesn't that make bug fixes difficult as the fix might exceed the designated space in ROM? Or do bug fixes always get re-applied after each reset? Patching in memory is how I'm looking at this. (Remember, I'm a non-programmer...deal with me, please.) LOL
Ok..out of the box time.
1. Can a shim be used to capture calls to a certain location in the ROM and redirect to another location (within the ROM or even the storage card. Linux builds anyone?). Like what HD disk managers did to get around LBA limitations or even boot sector viruses did.
2. Can an emulator be used to simulate/backup/build/test the ROMs on a PC before wiping the PDA? Don't laugh, but if not, could something be done with Virtual PC? Oh..Ok, laugh.
(Should I go hide somewhere?)
Hi!
So what it's all about?
There are so many projects dedicated to porting linux to WM devices.
Mostly the only way to boot into linux and kick windows mobile out of RAM is the haret tool.
For thoose who never heard of it is a linux bootloader (it is even more), that is started from within windows mobile.
This is the result of the fact that the native bootcode of the device could not easily be replaced.
Apart from that, there are to many things to consider to rewrite own bootcode for a closed device.
So what if the native bootcode "thinks" it boots in windows mobile again, but it in fact jumps into linux kernel code?
Whaaat, you might think and i thought a lot of it in the last few weeks:
The idea is, to embed a linux kernel in a XIP container and boot it with the native bootloader
So that's crazy stuff and it's even more crazy, that some insane hackers already did some successful attempts.
The project aims to port Android to a device called Meizu M8.
Step into this thread and start reading:
http://www.meizume.com/modding-development/9014-project-port-android-meizu-m8-18.html
One of the developers already has started to push some GIT-repos of the toolset here:
http://gitorious.com/~banxian
Of course there's a lot to investigate and other things to consider:
1. The injected code must be in good shape (kernel needs excellent hardware support)
2. The device will need to be hard-SPLed (no security check)
3. The files must match the Flash layout of the bootcode
4. JTAG support for the device would be mandatory for testing
5. Lots of information about internal Flash structure is required
....
Please tell me what you think about it!
Cheers,
scholbert
That's an excellent idea!
Multiboot would seem to be a better (albeit more complicated) alternative to me though... In their current stage, Linux ports to WM devices tend to be unstable and rather limited in functionality. Replacing a fully functional WM with a semi-functional Android on one's primary device is not as tempting as having both at the same time.
I'd say the first step in this direction is bootstrapping custom XIP from RAM with a patched SPL. Flashing XIP nbX every time custom XIP is patched is slow and tedious. Once a working XIP with booting Linux kernel is available, it should be relatively easy to switch SPL back to normal booting from NAND. Also ULDR XIP can be used as a container for the custom XIP rather than the WM kernel XIP. This way one can boot WM by default and then reboot to ULDR/Linux if required (not quite multiboot, but something close).
The caveat here is that when HaRet is used to boot Linux kernel from under WM, some hardware init could have been carried out by WM kernel at boot time. When WM kernel/XIP was never ran, there's a good chance some of the hardware that works when booting Linux via HaRet won't work anymore Completely bypassing WM kernel initialization means more initialization may have to be done in Linux kernel/custom XIP.
The progress that Meizu people made is certainly impressive, but there's a long way from a 100-byte piece of code that fills the framebuffer to a fully working Linux kernel. I'm not being sceptical here, on contrary I'm pretty sure this is possible, but it will take a lot of time and dedication to make this happen. At any rate, good luck and I'm sure you'll find plenty of support here.
This project, is cool, i am waiting any progress, i want put the android in the MS20(Brazillian KS20 without wifi and 3G)
Hi again,
thanks for the feedback so far
@ stepw:
I really share your thoughts concerning long and dusty road of development.
So perhaps i was in kind of euphoria when i decided to post it yesterday.
Anyway, let's see what the future will bring us
Maybe we should start with some kind of ramloader and place it in XIP area.
BTW, could you be more specific about this ULDR XIP thing?
Sounds interesting and to be honest, never heard of it...
Please consider the thread as a starting point for an open discussion.
Anyway, i will need help, because i'm a horrible hacker.
So maybe i should have written IDEA not PRJ
Have a nice day!
scholbert
As per http://channel9.msdn.com/wiki/CEDeveloper/BSP/
ULDR and IPL
For BSPs that are for Windows Mobile products, the ULDR and IPL are required parts of the BSP.
“ULDR” stands for “Update Loader”, and is part of the Image Update system. This system allows deployed devices to be updated with new software after they ship. The Update Loader reads a configuration stored in persistent memory and downloads and installs new versions of operating system or OEM files.
“IPL” stands for “Initial Program Loader”. This piece of code is launched by the bootloader or executed directly at startup if a bootloader has been removed from a board. The sole job of this program is to choose whether to execute the ULDR software, or load and execute the operating system that is currently on the device. If a user has downloaded new versions of operating system or OEM files, the IPL will be configured to launch the ULDR. Otherwise, it will load and launch the OS.
===
Da_G's thread http://forum.xda-developers.com/showthread.php?t=520009 has plenty of information about ULDR, although it's more about keeping it rather than about using it for something else.
Replacing ULDR is a valid way to inject another item into NAND partition table. Unfortunately with WM all 4 primary partitions are used in the MBR by default, so taking ULDR out allows for reuse of one of the parition slots for other purposes. IPL already has a way to bootstrap either ULDR or OEM XIP (WM kernel), it should be possible to control boot partition selection from each of the OSes. Manipulating partition type and flags should make it possible to choose the default OS too.
ULDR partition is typically fairly small, but it can be expanded to store Linux ramfs image or even the filesystem. Alternatively, FATFS partition in NAND could be mounted at boot and filesystem image could be located there. Yet another location for it is IMGFS partition, but that calls for a file system driver (read-only at least) that I don't think exists for Linux. Anyway, if at least FATFS can be mounted, access to all user files accessible from WM should also be possible from Linux/Android once it's booted.
Sorry for deviating from the original topic
Hey stepw!
Sorry for deviating from the original topic
Click to expand...
Click to collapse
Hey we got an open discussion here...
Thanks for all this useful information so far!!
I knew about starting up WM platform and i also looked deeper into IPL and stuff. What i am missing a little is just these information about XIP and WM image in general.
So i think i'll first step through Da_G'S thread, it looks very promising. Great stuff!
Again leave your technical comments here, because i think it's the only way to get best solution
Best regards,
scholbert
Hi,
I've been working on this for a few days now and have a simple bootloader that loads and runs a kernel on my vogue. Unfortunately the kernel doesn't boot properly because it can't initialise all the hardware correctly but it definitely runs. Attached is my code and a script to insert it into an xip payload with a kernel.
Woooow.....
Hey dzo,
this is a real breakthrough or whatever you may call it.
Really great stuff!
Maybe this won't reach peoples interest right now,
but let me forecast, that someday this will give us the opportunity
to wipe out windows mobile completely if we like to
Anyway i think it would be nice to get some stuff pointed out more clearly.
So let me sum up:
1. Let's assume we got excellent kernel zImage to support the hardware of our device.
We will need to initialize even parts of hardware in this kernel,
that we did not even know about, while testing with haret.
2. We need some hard-SPL bootcode on our device, because we need to avoid security check of the image.
3. We got WM ROM for our device and we got some kitchen to extract it and work with it.
The starting point will be the file OS.nb.payload, because this is pure binary.
(the image like it is stored in NAND flash memory).
The image (OS.nb.payload) itself is organized in different parts and partitions.
At the moment we don't care much about it, because we leave it mainly untouched.
We need to find the entry point from the WM kernel, which is pure XIP code (XIP.bin).
4. We inject a tiny loader for elf binaries at this point, which is also compiled as XIP code (tinboot).
5. We step a bit further and place the kernel zImage (which is an elf file) at a certain offset.
At least this should be the address the tiny loader points at (e.g. offset + 0x8000).
6. We use some kitchen tools to reconstruct a flashable image.
7. We flash this image to our platform, using the same tools we use to flash a cooked ROM.
8. We boot into linux!
Please correct me if i forgot something or made a wrong assumption here.
Would be really nice to get some more hackers and ROM cookers over here to benefit the discussion.
Thanks again dzo!
Best regards,
scholbert
Hi again!
A little research at the forum gives some more details about OS.nb.payload:
http://forum.xda-developers.com/showthread.php?t=446506
This maybe all well known, but should help to point at it again for a better understanding.
So if we use mtty and type the info 8 command on HTC loaders this prints out these partitions (should be all the same on HTC devices):
Partition[0], type=0x20, start=..., total=... BOOT (ULDR)
Partition[1], type=0x23, start=..., total=... RAWFS (XIP)
Partition[2], type=0x25, start=..., total=... IMGFS (SYSTEM)
Partition[2], type=0x04, start=..., total=... FATFS
TBC
scholbert
dzo said:
Hi,
I've been working on this for a few days now and have a simple bootloader that loads and runs a kernel on my vogue. Unfortunately the kernel doesn't boot properly because it can't initialise all the hardware correctly but it definitely runs. Attached is my code and a script to insert it into an xip payload with a kernel.
Click to expand...
Click to collapse
That's some excellent progress! Did you build your kernel yourself too? Is it mission critical hardware that fails initalization or some minor stuff?
LMAO - No need to say it. I know my iPAQ rx3115 is a dinosaur, but so am I.
However, the damn thing refuses to die and has been a good, faithful workhorse for a loooong time. To me, that speaks to the quality of the hardware. The rx3115 just seems to be built solidly. Sad to say the PocketPC Pro 2003 (SE) operating system is at the bottom rung of the support ladder from M$ and we all know that means it will be phased out soon...
I just can't give up on my trusty rx3115. Hell, even the original battery is still holding a charge really well. And believe me, it hasn't spent a lot of time forgotten and idle despite the constant rotation of new toys that might pass through my hands. It's been used a lot and just keeps on ticking.
So, even though it continues running just fine, I'm now willing to experiment and try to make it more up-to date. Why not tinker with it since all support is fading fast? LOL if I break it now it hardly matters after all these years and I have plenty of other devices to rely on.
So yeah, I'm a bit of a noob (despite being a dinosaur ) who is willing to learn...
First step was to search the Google-sphere. Seems there are a lot more questions than answers out there for rx3115. How to upgrade the OS to WM5 or even WM6.1 Classic? I saw that asked over and over, but very few answers. Most who did reply said, "Try Universal Bootloader and a ROM image for another device..." OK, so that seemed the way to go, but is it?
There are a LOT of dead links for a Universal iPAQ Bootloader out there. I did manage to find a copy @ http://sourceforge.net/projects/ubl/files/ubl/Binaries/ where I selected the GUI version which came as an executable. Double clicking it creates a folder which UBL runs out of.
Caution: My system flagged it as having a Worm in the Vista Driver folders (2... Vista and Vista x64) and the Vista Drivers.exe application.
Who wants Wormy drivers? For that matter, who wants Vista?
I'm not qualified to judge if it is a false positive to some of the developers legitimate code. Maybe someone more savvy might want to take a look at it and make a ruling...
So I sanitized UBL by quarantining and deleting the offenders. Next, I asked Windows 7 to run it under compatibility mode for XP service pack 2. (It looks like it was always an XP box utility anyway.)
Here's a sanitized version of UBL for download. http://www.mediafire.com/file/7anraar1tkc3lz1/BootLoader.rar This is a rar of the extracted file folder (minus the Wormy bits). Just expand it and run "Bootloader.exe" right inside the folder. Maybe someone else will have more luck playing with it than I did.
I could in no way make it communicate with my rx3115 under Windows 7. Mtty always fails to open the port. I tried following the advice of UBL's readme and making a settings.ini file to direct mtty to the right port, but with no luck. IDK - I never wrote an .ini file before. Maybe I messed it up. I tried a few variations (settings/bootloader settings/mtty settings for file names) all with no success.
Then I used a friend's XP system and got closer... UBL gets past the mtty stage and opens the com with my rx3115, but then the ROM flash just hangs at 0%. I tried several times with no further success. And without the ROM being cooked for my specific device, flashing from the SD card is out.
I was hoping to force flash the Kitchen WM6.1 Classic ROM for rx1950 I got from this xda thread by Victory144 and Guifort: http://forum.xda-developers.com/showthread.php?t=510764 The ROM size is perfect for rx3115!!!
Heck, I even tried looking at the RUU's from valid rx3115 and rx1950 ROM updates and seeing if I could puzzle out how to cobble something with a Hex Editor. But I'm not really qualified for that.
It's been a lot of years and no one has cooked an upgrade ROM for rx3115 yet. At least as far as I can tell. But even recently I've seen rx3115 owners posting to forums and asking for an upgrade. I know I'm not alone in this desire and that's why I started this thread. Maybe some other rx3115 owners will join this discussion. We might just figure something out.
Something else I've begun looking into is installing Linux on my rx3115. It seems possible and there are a few reports of it being done, but little in the way of tutorials for the challenged. More on that later...
Or... maybe I'm crazy... Doesn't the Samsung s3c2440 CPU meet the minimum system requirements (@ 300mhz) for XP Tablet? CPU's can be overclocked anyway and the s3c2440 should be capable of sustained 400mhz efforts. It is set at that speed in some other PDAs The RAM is right at the bottom edge of requirements as well, IF all 64mb can be freed up for the user. Is there a way to boot XP Tablet off an SD card? Could the RAM/ROM chipsets be instructed to act as two RAM slots for that purpose creating 96mb RAM? Am I just a fool?
I welcome any advice, questions, derisive laughter... whatever...
I'll be checking the thread and updating the reports of my efforts.
Thanx for stopping in.
Maybe I'm missing a step...
If I press Mobile Media (button 1) + iTask (button 4) + Power + Reset
I get a blank white screen with the HP logo in the center and the revision #'s on the top...
From here (Bootloader screen - right???) rx3115 will try to flash ROM from an SD card if one is inserted that has a ROM image. Unfortunately I don't have a valid image except the 1.01.11 ROM of WM 2003 that I want to upgrade away from.
However - and this may be where I'm missing a step - without an SD card inserted I can't get bootloader to show USB connection. I've tried every button and combo of buttons I can to try and get USB to show up on the bootloader screen.
I feel like I'm missing something and that next step will allow Universal Bootloader to force flash a WM6.1 ROM under XP.
Any help? Anyone? How to get USB connection for bootloader with rx3115?
Handhelds.org continues to be down for maintenance. They are the distribution and support site for Familiar Linux, an alternative iPAQ OS. They were supposed to be reopened last week...
Angstrom Linux has shown itself capable of running on iPAQ and I found a very in depth tutorial - LOL - but it's in Spanish. I'm sorry to say me Spanish es no bueno. There's even a video on YouTube of Angstrom on an iPAQ rx3115 - so I know it can be done. Again though, it's in Spanish.
Today I'm checking out a "Live RAMdisk" version of Angstrom. It's like a LiveBoot CD Linux. You can boot and run Linux from storage (SD card) without installing. Instead of "try before you buy," it allows you to test before you install. At least I will get a chance to see how the Angstrom OS handles without having to flash my ROM and then reflash if I want to revert to WM 2003.
They have LiveRAMdisk and install versions supported for iPAQ h2200, h3900, h4000 and hx4700. The h5000 series is still in testing. More information is @ angstrom-distribution.org/taxonomy/term/6
I'm going to try the LiveRAMdisk version for the h2200 series as it's closest to rx3115. Same RAM and ROM, but the h2200 uses an Intel Xscale CPU rather than the Samsung... Still, it's the closest hardware match to the rx3115 out of all the supported models.
I'll post back about how AngPAQ handles.
HandHelds.org is still down. A shame since my research indicates Familiar Linux associates closely with PDAs...
Seems Ubuntu had a project they've abandoned or moved beyond (depending on your perspective), but the hardware requirements are way beyond iPAQ. They do have some stables for anyone interested. Google Ubuntu Mobile or Ubuntu MDI. Might be a nice alternative for some earlier tablet users...
Like they say..... BACKUP your data before any major changes!!!
I did try the LiveRAMdisk version of Angstrom Linux for h2200...
The LiveRAMdisk is a 23mb self executing file that you open from the root of your SD card. It was a non-starter. After booting from my SD card the iPAQ froze. I did a hard reset and freed up as much memory as I could from WM 2003 before trying again. Same result.
No worries, restored from backup and all is OK with my rx3115.
Just to be sure I tried with another method called a Loopback Image. I downloaded an Angstrom/Opie (full PDA style GUI) image and a bootloader from the Angstrom repository as another method of running Angstrom from my SD card. You use 7zip to extract the downloaded .bz2 and it inflates into a robust sized image (96mb in the case of h2200). Add the image and the bootloader to the same location on your SD card (preferably root). Execute the bootloader and run Angstrom off of your SD card. This too failed to run after several attempts...
LOL - another hard reset and restore from back up after each try.
I'm convinced it's a hardware incompatibility due to the difference in processors between h2200 and rx3115. But, darn it, if you look at development boards you find that they use Angstrom on boards with the same Samsung s3c2440 CPU that rx3115 has.
Next step is to try and find some of the Angstrom versions used on those development boards... And hope I get more than a bare-bones, command line only GUI.
If you have one of the supported iPAQs (h2200, h3900, h4000, h5000 or hx4700) it may well be worth your while to try running a Loopback Image from your SD or CF card. A full Linux emvironment when you want and you can always hard reset and restore to get back to Windows Mobile. More information can be found @:
(www) linuxtogo.org/gowiki/WinCeQuickInstall
Well, the Angstrom online builder won't give me Opie in a build for a mini2440 board.
I did find a .tar.bz2 that someone built up from Angstrom and marked as "Angstrom-opie-image-glibc-test-20070620-rx3000.rootfs.tar.bz2" (Thanx whynot). If I can convert the extracted .tar to .img I could try a Loopback Image with it from my SD card... Meanwhile, I suppose I have to start learning how to build up the bootloader myself. *sigh* Did I mention that I'm more of a hardware guy?
Handhelds.org still down.
Despite all the Linux talk I'm still trying to get a higher version of WinCE to install on rx3115... Options are good if you can manage to have them.
Ongoing Questions/Help Sought:
1) Anyone have a cooked ROM (or want to cook one) for iPAQ rx3115 that would flash WM5 or WM6.1 Classic to the rx3115?
2) Any help or suggestions with UBL (Universal BootLoader)?
a) Is the UBL I found @ sourceforge really infected with a worm?
(Note that it is marked as uploaded by the original UBL developer chrismrulz)
b) Am I better off leaving out the suspect Vista Drivers and just using an XP box to run UBL anyway?
3) Why can't I get rx3115 to acknowledge USB under the iPAQ bootloader screen?
4) Could someone go over to HandHelds.org to knock on their door and tell them to get their site back up already?
5) Anyone know how to. or can suggest software to, Convert .tar to .img?
6) Any other Linux Distros I should be looking at as suitable for iPAQ rx3115?
7) Will anyone else post to this thread or am I just Blogging here?
a) Am I boring all the fine xda members?
b) Or are my bungling attempts at least providing a good laugh?
Yesterday I checked out NetBSD (Unix). They have prepared distributions for a wide array of PCs and Devices... I took a chance and tried one for Strong ARM iPAQs (even though rx3115 is Friendly ARM). Another no go... But I will say that they have the nicest bootloader of all the options I've worked with so far.
Now that I have my minimum posts in, thanx to Blogging in this thread and trying to help some seemingly lost first time posters, I can finally post outside links to the forum. HUZZAH!!!!
There are a few things I've got for download by anyone interested.
Here's the Universal BootLoader with GUI for iPAQ from chrismrulz, without the suspect Vista Drivers. So (I believe) it only works on XP boxes.
http://www.mediafire.com/file/7anraar1tkc3lz1/BootLoader.rar
I had tried a few overclock programs recently... ClockWizard, Pocket Hack Master and XCPUscalar.
ClockWizard is freeware and worth exactly that IMHO. I found it buggy to run...
Pocket Hack Master supports a lot of processors including the s3c2440. I got a version from somewhere with a working serial#. Again, I didn't care for it despite rave reviews elsewhere for other devices.
XCPUscalar worked the best for me, even though there is no official support for Friendly ARM. I found a version which is a free install cab of this $ware. There are a few tricks for some to get the scaling feature to work and that helped me get her configured... I included a .txt of the advice.
All 3 overclocks in one .rar file are here:
http://www.mediafire.com/file/636a5cl8ofzaa2z/OverClock.rar
As a "best of" I broke out XCPUscalar separately.
http://www.mediafire.com/file/z593cqhbnvegpg9/XCPUScalar.arm.CAB
Along with the advice .txt.
http://www.mediafire.com/file/igoragriu8lc2ha/XCPU tricks.txt
Here's the LiveRAMdisk of Angstrom Linux for iPAQ h2200.
http://www.mediafire.com/file/i61956852696grp/Angstrom-x11-image-liveramdisk-2007.12-h2200.exe
Just load it on your SD card and execute it from there to boot into Angstrom. Check out their guide to installing Angstrom under WindowsCE.
http://www.linuxtogo.org/gowiki/WinCeQuickInstall
Of the two methods (LiveRAMdisc or Loopback Image), I think Loopback Image seems more promising...
Check their Repository to see which machines are supported by stable releases.
http://www.angstrom-distribution.org/releases/2007.12/images/
Or visit http://www.angstrom-distribution.org/ for more information. They are heavily into embedded.
Here's the NetBSD files I grabbed all in one .rar file. This executable will boot NetBSD for the following devices: IPAQ h3100, h3600, h3660, h3900, Jornado 720(US/Many Europe/Japan) & Jornado 820(US/Japan).
http://www.mediafire.com/file/ync2ltv3l7oo4si/NetBSD.rar
Inside the folder are the 3 files you need to boot NetBSD under WindowsCE (hpcboot.exe, netbsd-IPAQ.gz and netbsd-IPAQ.symbols.gz) Put all three files on the root of your memory card and execute bootloader to boot into NetBSD.
Also in the .rar is a list of the md5 checksums for each file.
NetBSD has a lot of support for older hardware. Look them up: http://netbsd.org/
Or check out their long list of supported machines.
http://netbsd.org/ports/
If anyone needs a widget for verifying md5 checksums under Windows OS, here's an outstanding one from Jem Berkes. I've used this freeware many times (On XP and Win7). A nice, small footprint program that just works great.
http://www.mediafire.com/file/bhebw4ozo6dz767/md5sum checker.rar
rx3115
I have an rx3115 also. I have tried angstrom, with no luck. I am following your progress.
Thanks for the reply, kati. Now I don't feel so lonely.
And I added a Thanks to your meter for your post in this thread:
http://forum.xda-developers.com/showthread.php?t=472643
It seems like your post there got a cook interested in our device. I posted some links and PMed him some info. I'm keeping my fingers crossed. Maybe he can port over the WM 6.1 Classic ROM that was among the links I sent him. (Thanks tomcug)
Meanwhile...
Handhelds.org is still down.
Angstrom has added a new release (2011.03), but the online builder still won't include Opie in the .tar for mini2440 boards (my best hope for a working Angstrom straight from the source).
I'm still holding out hope for the "Angstrom-opie-image-glibc-test-20070620-rx3000.rootfs.tar.bz2" that I found.
http://www.mediafire.com/file/f2fsd...age-glibc-test-20070620-rx3000.rootfs.tar.bz2
I just need to find the right kernel and HaRet bootloader for it to run from SD card...
I'm basing that work on this document for installing a Loopback Image which I got translated from Portuguese (Thanx Rubberman).
http://www.mediafire.com/file/ci92vshhpojbyb8/AngPAQ rx3115.pdf
And I'm following the progress of whynot on another board where he documents his efforts to port Angstrom onto rx3115.
Here's a couple more things available for download...
The last official WM 2003 update (1.01.11) with installer
http://www.mediafire.com/file/i6k0935chhkgzlh/iPAQ rx3115 ROM 1_01_11.exe
The cooked ROM of WM 6.1 Classic designed for the rx1950. (.nbf file only)
http://www.mediafire.com/file/iu9p815w3yjpy6h/CEOS.nbf
In case any other cooks want to look at it. At 27.82mb it would just fit on rx3115 and may benefit from being trimmed down. Or someone might have more luck flashing it with the UBL mentioned above.
Here's the whole kitchen package from Victory144 and Guifort
http://www.mediafire.com/file/nna2yo92q2beiik/Flasher_Hp_Ipaq_rx1950_ENG_WM6.1.rar
It includes the installer and the .cab for the appropriate version of Mobile Office.
And just the Office cab for any WM 6.x users who may need it
http://www.mediafire.com/file/nmz3sbyuxan7c4e/office_wpc_WM6.CAB
LOL it seems rx3115s are popping up out of retirement (at least from what I see in the Googlesphere). In case any resurrected machines need it, here's the Daylight Savings Time patch for the new DST schedule.
http://www.mediafire.com/file/i51hkr3c8ep8t5e/Daylight Savings Fix.exe
Stay tuned... I'm still working on Linux booting from an SD card.
rx3115 user whynot has been having some luck getting Angstrom to boot from an SD card. I'm trying to get the proper kernel and HaRet from him. Here's his thread:
http://www.linuxforums.org/forum/mobile-devices/175821-ipaq-hp-rx3115.html
Today I uploaded ActiveSync 3.7.1 in an attempt to help xda member Orangekid sync an old device under Windows XP. If anyone else wants this fossil it can be downloaded from here:
http://www.mediafire.com/file/88xr4pjl14x7883/ACTSYNC_3_7_1.rar
A couple more things I uploaded to help others...
Uedit32 Hex Editor:
http://www.mediafire.com/file/6r8ffn1fq3bh9mu/uedit32.exe
mtty11a a command console for sending commands to iPAQ.
http://www.mediafire.com/file/7srppxvnr728ime/mtty11a.exe
A tutorial on How to install a different language ROM in your PDA I grabbed from another site and turned into a PDF:
http://www.mediafire.com/file/5e48n571jg1adqb/How to install a different language ROM in you PDA.pdf
LOL helping him has helped me... I hope. I may have a better idea of how to use a Hex Editor to change the WM 6.1 ROM and make it installable for rx3115.
I've also learned how to use mtty to make a backup of the ROM image on iPAQ to an SD card. I'll post details here later IF anyone posts that they are interested. I'd rather get back to work on my projects than spend time blogging right now.
LMAO - Handhelds.org is still down. They are one month overdue for coming back online.
I tried a few new ways to get the Kitchen ROM for rx1950 to flash to rx3115. No luck again.
tomcug has apparently given up on cooking a WM6.1 ROM for rx3115...
whynot finally replied to my query with a few tips and hints... I'll be making another run at getting Angstrom Linux to boot from SD card soon...
RumoredNow said:
LMAO - Handhelds.org is still down. They are one month overdue for coming back online.
I tried a few new ways to get the Kitchen ROM for rx1950 to flash to rx3115. No luck again.
tomcug has apparently given up on cooking a WM6.1 ROM for rx3115...
whynot finally replied to my query with a few tips and hints... I'll be making another run at getting Angstrom Linux to boot from SD card soon...
Click to expand...
Click to collapse
I'm still following ya I may not have an rx1950 but I think it's cool to see what other people on here can do. I'm rooting for you!
Great thread! I just recently started searching for Linux options for the two H3835's I have gathering dust. I retired them long ago for more modern hardware.
Now my kids (8 and 6) have taken over my (and my wife's), Android phones to play games on every time we get in the car. So I thought I'd see what I could do with the old iPaqs to make gaming devices for the kids. But before I can try to get any games running, I have to get an OS on them.
Anybody out there having any luck with the H3835? It appears from the Angstrom Forums that the "lightning fast" 206mhz StrongArm processor isn't up to the task of running Angstrom.
Handhelds.org is still down, so I can't try Familiar yet. I read somewhere else that the delay in bringing the site back up is due to the developers & site admins being adversely impacted by Nokia's recent decision to cease development on Maemo/Meego in favor of Windows Mobile 7. If that's the case, maybe it will be down permanently?
Sadly, I'm a compulsive tinkerer with old hardware and I may not be able to rest until I get it working or brick the silly things.
Thanks for joining my thread Markedswan.
Yeah, Handhelds.org is still down... Interesting rumor - I think I read on a wiki page that there is a split among the developers over some code. The server owner may have frozen access pending legal clarifications. LMAO - It's supposed to be Open Source.
I too am a relentless tinkerer. I understand the upgrade or brick it mentality.
First thing I did was look up the h3835 specs on www.pdadb.net That Intel StrongARM SA-1110 CPU looked familiar from my research so I double checked...
NetBSD (Unix) supports lots of old hardware. Your CPU is in their Tier I support group (the highest level of support). http://netbsd.org/ports/#ports-tier1 (The hpcarm listing.) Clicking that link shows that your processor is supported. http://netbsd.org/ports/hpcarm/#processors
h3835 is not listed specifically, but your system architecture is the same as the h3600 series. The only difference is you have twice the ROM. The NetBSD package that I tried should boot on h3835 from the SD card.
http://www.mediafire.com/file/ync2ltv3l7oo4si/NetBSD.rar
or if you prefer to get it from the source
http://ftp.netbsd.org/pub/NetBSD/NetBSD-5.1/hpcarm/
Don't forget the MD5sum checker if you need it. A list of the MD5 sums for each file is in the NetBSD folder.
http://www.mediafire.com/file/bhebw4ozo6dz767/md5sum checker.rar
Good luck and be sure to go to http://netbsd.org/ for documentation and support help.
Interesting
Interesting work going on here. Have you tried Android 0.8? It seems to be the most light-weight and flexible choice of Android out there.
Hmmm... That's a thought. I'll definitely look into it. I'm still trying to block out some time to get Angstrom to boot up. I finally got a working (or so my source says) HaRet. I just need the right Linux image.
But I'll give Android 0.8 a try for sure.
I've read that Android was too much for these devices. Memory on Android devices is in the Gigibytes (my phone has 10 GB on board I believe) while the iPaqs have less than 100mb typically (mine has 96mb between the RAM and ROM). I have no idea if that is truly the case though. Maybe with a decent size CF or SD card on board?
Rumorednow: NetBSD looks promising from what I've read on the website. Do you know off hand what window manager options will work with the handhelds? I wasn't seeing anything in the packages specifically for handhelds, maybe I missed something. I'll dig deeper, but thought I'd ask in case you knew.
I have the Compact Flash jacket for my 3835, so was thinking about trying Debian (which I'm more comfortable with) & can boot off a 1 GB Compact Flash card. Debian's site says the ARM version was designed with XScale processors and some of the custom router processors in mind, but the instruction set is specficially called out as being V4 for maximum compatability (the StrongARM in my iPaq uses the V4 instruction set) rather than the V5 native to the XScale series which came after StrongARM was introduced. So maybe it will work? I believe OPIE works with Debian as a window manager and that seems pretty slick and well supported.
I'll be living out of a suitcase for work pretty much all of May, so I'll have some time to tinker on this more in the evenings then. But, maybe someone will have it all figured out by then though?
Markedwsan said:
I've read that Android was too much for these devices. Memory on Android devices is in the Gigibytes (my phone has 10 GB on board I believe) while the iPaqs have less than 100mb typically (mine has 96mb between the RAM and ROM). I have no idea if that is truly the case though. Maybe with a decent size CF or SD card on board?
Rumorednow: NetBSD looks promising from what I've read on the website. Do you know off hand what window manager options will work with the handhelds? I wasn't seeing anything in the packages specifically for handhelds, maybe I missed something. I'll dig deeper, but thought I'd ask in case you knew.
I have the Compact Flash jacket for my 3835, so was thinking about trying Debian (which I'm more comfortable with) & can boot off a 1 GB Compact Flash card. Debian's site says the ARM version was designed with XScale processors and some of the custom router processors in mind, but the instruction set is specficially called out as being V4 for maximum compatability (the StrongARM in my iPaq uses the V4 instruction set) rather than the V5 native to the XScale series which came after StrongARM was introduced. So maybe it will work? I believe OPIE works with Debian as a window manager and that seems pretty slick and well supported.
I'll be living out of a suitcase for work pretty much all of May, so I'll have some time to tinker on this more in the evenings then. But, maybe someone will have it all figured out by then though?
Click to expand...
Click to collapse
The packed android kernel is only 30 or 40 mb if i'm not mistaken. You would have the whole thing from there.
Hi I'm new and registered specifically because of this thread. I gotta agree with you, waaay too little support for the rx3115. I love this iPaq, have 2 of them and I use them for everything (especially with the nifty universal remote feature, I run around and turn things on and off and annoy my girlfriend a lot). As great as I think it is, it really needs some updating in any way possible really.
Great job on pushing forward with all the different options. Anything you need a second tester on just give me a shout, my 2nd one can be used as a guinea pig
Also... What happened to handhelds.org? I check in every day wishing for a shinning ray of hope that they'll be up and running again soon
OVERVIEW
some people may have already seen some of the stuff i make like apps, tools, roms, mods and exploitation.
yesterday i got my first ever MTK device, and in all honesty i think the range of tools are crap other then MTK droid tools but that unfortunately isnt open source
THIS IS A COMMUNITY PROJECT AND THAT MEANS FREE AND OPENSOURCE AND OPENMINDED TO IDEAS
DOWNLOADS, DOCUMENTATION AND SOURCE
DOWNLOAD(VERY EARLY STAGES)
SOURCE CODE
NOTES
hopefully the community jumps in and gives me a hand and suggests features
XDA:DevDB Information
MTK open source AIO tool, Tool/Utility for all devices (see above for details)
Contributors
Ricky Divjakovski
Source Code: https://github.com/Ricky310711/OpenSource-MTK-Tool
Version Information
Status: Testing
Created 2016-01-14
Last Updated 2016-01-21
those are Teclast T98 MT8752
first stock
second modified for resizing purpose (system userdata)
hocuspocus69 said:
those are Teclast T98 MT8752
first stock
second modified for resizing purpose (system userdata)
Click to expand...
Click to collapse
i have made the scatter file parser made, ill be making a new repo and pushing to git later tonight
Great idea since MTK Droid Tools doesn't have support. :good:
My MT6572 scatter file with custpack partition (Alcatel Pop C2).
MT6575 scatter file with custpack partition (Alcatel S'Pop).
MT6571 scatter file (Blu Dash Jr K)
MT6577 scatter file with custpack partition (Alcatel Idol 6030X)
Mt6572 ( other china phone)
Here is the scatter for the Wiko Fever: http://forum.xda-developers.com/showpost.php?p=63755203&postcount=4
scatter file for Coolpad Note 3
scatter file for Coolpad Note 3
keemi said:
MT6577 scatter file with custpack partition (Alcatel Idol 6030X)
Mt6572 ( other china phone)
Click to expand...
Click to collapse
kirito9 said:
Great idea since MTK Droid Tools doesn't have support. :good:
My MT6572 scatter file with custpack partition (Alcatel Pop C2).
MT6575 scatter file with custpack partition (Alcatel S'Pop).
MT6571 scatter file (Blu Dash Jr K)
Click to expand...
Click to collapse
well normal scatter conversion is done, but may i ask what is an emmc scatter?
and couldnt we refer to a normal scatter file rather then the eMMC scatter, it doesnt seem to contain much info other then the partition label and size?
Ricky Divjakovski said:
well normal scatter conversion is done, but may i ask what is an emmc scatter?
and couldnt we refer to a normal scatter file rather then the eMMC scatter, it doesnt seem to contain much info other then the partition label and size?
Click to expand...
Click to collapse
It's basically the same as a normal scatter but some smart phones produce that scatter type(emmc) instead of the normal scatter. Same goes for some MTK Droid Tool versions like it happened with me. I got both normal scatter and an emmc scatter for the same phone.
I don't know why that is though. By both scatter files work with SP Flash Tool.
kirito9 said:
It's basically the same as a normal scatter but some smart phones produce that scatter type(emmc) instead of the normal scatter. Same goes for some MTK Droid Tool versions like it happened with me. I got both normal scatter and an emmc scatter for the same phone.
I don't know why that is though. By both scatter files work with SP Flash Tool.
Click to expand...
Click to collapse
ok, well ive made the scatter conversion, added the project donate feature and the abillity to see the tool and utillity versions, the source is in the main post
mt6572 jb scatter
TurkishBoy1 said:
mt6572 jb scatter
Click to expand...
Click to collapse
scatter files arent needed anymore, thanks anyway ill keep it for refferrence
Ricky Divjakovski said:
ok, well ive made the scatter conversion, added the project donate feature and the abillity to see the tool and utillity versions, the source is in the main post
Click to expand...
Click to collapse
Great I will check it out.
kirito9 said:
Great I will check it out.
Click to expand...
Click to collapse
any features you would like to suggest use the suggest features tab
Ricky Divjakovski said:
any features you would like to suggest use the suggest features tab
Click to expand...
Click to collapse
I recently go into mtk myself and have used your kitchen, Thank you! I don't have much experience in making roms but I have hard bricked my mt6572 K8 watch and my Cubot X-15 by getting carried away with with flashing but while doing so I've managed to bring them both back to life and have aquired 10 gigs of all kinds of different MTK tools. I'm mpre then willing to share my collection, now why would any one need 10 gigs of tools? well I learned the hard way that SP flash tools can be a pain in the ass when trying to bring your phone back from the dead hitting you with mad BROM errors so I found out that if you need a no bull**** save me flash tool, go with Infinix Flash. Any ways I'm more then down to be a part of this and will try to comtribute whatever I can
m0nt3s said:
I recently go into mtk myself and have used your kitchen, Thank you! I don't have much experience in making roms but I have hard bricked my mt6572 K8 watch and my Cubot X-15 by getting carried away with with flashing but while doing so I've managed to bring them both back to life and have aquired 10 gigs of all kinds of different MTK tools. I'm mpre then willing to share my collection, now why would any one need 10 gigs of tools? well I learned the hard way that SP flash tools can be a pain in the ass when trying to bring your phone back from the dead hitting you with mad BROM errors so I found out that if you need a no bull**** save me flash tool, go with Infinix Flash. Any ways I'm more then down to be a part of this and will try to comtribute whatever I can
Click to expand...
Click to collapse
SP flash tool is a great tool, abit complicated fpr norrmal users to use but gets the job done, if it were upto me personally id make a menu from the scatter file presented and have a list of partitions to flash based on the scatter
MediaTek 6571 which wont address hard drive properly
Ricky Divjakovski said:
SP flash tool is a great tool, abit complicated fpr norrmal users to use but gets the job done, if it were upto me personally id make a menu from the scatter file presented and have a list of partitions to flash based on the scatter
Click to expand...
Click to collapse
Not sure where to start, trying to get my MediaTek MT6571 working properly but before I try to flash, is there any utility which can read the hard drive, either in Windows, Mac or Linux please? I and numerous others report that we have severe partitioning problems and would like either to see if there is unallocated space on my hard drive OR if there is some endemic problem with my Hexing71_et_lca ROM which is stopping it addressing its drive properly.
I feel I am caught in a Windows 98 time warp with some sort of LBA problem where I can't address anything more than a tiny percentage of the hard drive!
The 6571 seems to have a 16 gig hard drive but if it does, most of it is unallocated and only 899 meg shows as usable. When I try to install anything much larger than a few meg on it, I get OUT OF SPACE error messages.
So I figured that I need to install an SD card in the device and installed a 32 gig one, - obviously for all the apps. Aparted managed to get the card working but now after I did manage to install AIda on the phone, I am getting the same 32 gig installed, 899 meg available (none actually usable and) OUT OF SPACE error messages in Disk Storage & when I try to use the SD card as well!
Is there any GUI out there which can show what is actually going on with this device please? It wont show up in OSX, even in Disk Utility, but I do seem to be able to read (only) the hard drive's empty photos storage partition in XP and Linux. The only thing I know about the device from recovery mode is that it might be a sw version alps.jb7.mp.v1.14
custom build vern 1443066946, whatever that means!
licensedtoquill said:
Not sure where to start, trying to get my MediaTek MT6571 working properly but before I try to flash, is there any utility which can read the hard drive, either in Windows, Mac or Linux please? I and numerous others report that we have severe partitioning problems and would like either to see if there is unallocated space on my hard drive OR if there is some endemic problem with my Hexing71_et_lca ROM which is stopping it addressing its drive properly.
I feel I am caught in a Windows 98 time warp with some sort of LBA problem where I can't address anything more than a tiny percentage of the hard drive!
The 6571 seems to have a 16 gig hard drive but if it does, most of it is unallocated and only 899 meg shows as usable. When I try to install anything much larger than a few meg on it, I get OUT OF SPACE error messages.
So I figured that I need to install an SD card in the device and installed a 32 gig one, - obviously for all the apps. Aparted managed to get the card working but now after I did manage to install AIda on the phone, I am getting the same 32 gig installed, 899 meg available (none actually usable and) OUT OF SPACE error messages in Disk Storage & when I try to use the SD card as well!
Is there any GUI out there which can show what is actually going on with this device please? It wont show up in OSX, even in Disk Utility, but I do seem to be able to read (only) the hard drive's empty photos storage partition in XP and Linux. The only thing I know about the device from recovery mode is that it might be a sw version alps.jb7.mp.v1.14
custom build vern 1443066946, whatever that means!
Click to expand...
Click to collapse
The best way to really see how much space each partition has is using MTK Droid Tool and choose the option block information.There you will see your partition sizes and names.
licensedtoquill said:
Not sure where to start, trying to get my MediaTek MT6571 working properly but before I try to flash, is there any utility which can read the hard drive, either in Windows, Mac or Linux please? I and numerous others report that we have severe partitioning problems and would like either to see if there is unallocated space on my hard drive OR if there is some endemic problem with my Hexing71_et_lca ROM which is stopping it addressing its drive properly.
I feel I am caught in a Windows 98 time warp with some sort of LBA problem where I can't address anything more than a tiny percentage of the hard drive!
The 6571 seems to have a 16 gig hard drive but if it does, most of it is unallocated and only 899 meg shows as usable. When I try to install anything much larger than a few meg on it, I get OUT OF SPACE error messages.
So I figured that I need to install an SD card in the device and installed a 32 gig one, - obviously for all the apps. Aparted managed to get the card working but now after I did manage to install AIda on the phone, I am getting the same 32 gig installed, 899 meg available (none actually usable and) OUT OF SPACE error messages in Disk Storage & when I try to use the SD card as well!
Is there any GUI out there which can show what is actually going on with this device please? It wont show up in OSX, even in Disk Utility, but I do seem to be able to read (only) the hard drive's empty photos storage partition in XP and Linux. The only thing I know about the device from recovery mode is that it might be a sw version alps.jb7.mp.v1.14
custom build vern 1443066946, whatever that means!
Click to expand...
Click to collapse
what do you mean read the hard drive?
if your reffering to the phones storage i think you mean eMMC?
and that is devised into seperate partitions and filesystem formats, you need software to read it not to mention split it, a good start would be SP flashtool and MTK droid tools, also i suggest you format the sdcard(take it out of the device) as FAT32 with minitool partition wizard, also might be a good idea to check for damaged blocks and if you have the time zero all sectors out
EDIT: also if your modifying andd flashing .img files make sure you save it as the exact same size as the partition
Thnx