Related
SuperJustKitchen v0.9 Released.
Go to my site: http://justkitchen.info to get the updates and the info. It takes to long to update every device's forum that is supported, and I plan to support all devices, eventually.
Word of warning:
Not all EXT's have been tested or modified for the every device. Please test test and test and then let me know which packages don't work and what YOU've done to fix them. (I don't have time to fix ALL of them by myself.) Some packages will only be compatible with some devices.
(I'm no longer updating each thread separately for each device but just updating my site and posting the release info here. I will only update each thread to say that a new version is out.)
**Warning**
Before using this kitchen, you MUST read the whole thread. Any questions that have been answered will be ignored. This is your only warning.
**Disclaimer**
I am not responsible for any damage that may be done to your phone with a ROM created in this kitchen.
I am not responsible for any damage done to your computer.
I am not responsible for anything... at all.
Introducing SuperJustKitchen!
SuperJustKitchen is based on [http://forum.xda-developers.com/member.php?u=843218"]airxtreme[/URL]'s osKitchen Zero. All credit on for the kitchen backend goes to him.
Features
A completely stripped ROM. (Work in progress for some devices.)
LZX and XPR compression (Also option for No compression.)
Auto clean files that are language specific or DPI specific that your ROM does not need
Auto port missing language MUI files
Automatic rec'loc'ing for devices without native 6.5 nk's
6.1 and 6.5 support
Auto XIP and SYS porting
Auto NBH packing
Tool to convert OEM packages to EXT packages
Auto file conflict fix (don't have to removing older file that conflict (not that there are any. )
Save custom ROM settings (for cooks for multiple ROMs)
Cook multiple languages at the same time with the same ROM settings (Have to add language support yourself. I removed the required MUI's a while back because they made updating the kitchen and adding devices a nightmare.)
MUCH better organization of EXT packages
Active development instead of a program that is no longer being developed
Cleaner and easier to use interface
A built-in and customizable Tutorial section
And more!
Builds included
21056 - WM6.1
23658 - WM6.5 with new redesigned GUI
At the moment, this is an ENGLISH (WWE) only kitchen. This might change...
NOTE: In order for me to keep track of whether my time was well spent or wasted, if you use this kitchen to make a ROM, please either include SJK in the name or just mention that it was SJK cooked in your ROM's thread.
NOTE: This kitchen assumes that you know how to flash through SD, recover from a bad flash and are able to backtrack your steps to figure out how you broke your own ROM. If you do not understand these, please learn them first. Do not PM me asking me. I have written numerous walkthroughs on all these except on how to backtrack your steps. For that, just remember what you're doing as you do it and keep backups.
If you find any issues, PLEASE report them to the bug tracker in my website. It will help me make this kitchen better!
ENJOY!!!
thanks i will try....
oh!!!!! it takes a long time as Compaed to earvius kitchen.....also i am not able to flash .nbh file it stops at 1% in ruu and then device restarts.......
Not working
indresh88 said:
oh!!!!! it takes a long time as Compaed to earvius kitchen.....also i am not able to flash .nbh file it stops at 1% in ruu and then device restarts.......
Click to expand...
Click to collapse
same here...the final ROM when flashed says image corrupt
Same here all the rom file made by sjkv0.8 gives unflashable rom.
Something might be broken then. I changed the executable last minute. What size is the NBH you are all producing?
ivan the output nbh size is ok it seems for a lite rom it produces about 56mb and remember the one nbh u provided for testing is also having prob it says its corrupt.
help me...SJK won't cook
i cannot make it work...
i get an error while cooking about some files (ringtones) not able to be copied and then hangs.
i tried it on Windows7 and it says that the some payload.nb file is not found in temp folder.
gui-wise/appearance wise...this is the best kitchen ever!!
can someone please tell me where i went wrong? i download four files from the SJK website: ext package, sys package, opal package and the SJK package and extracted to the same folder.
Update:
v0.8.1 - Fixed unflashable ROM bug
Thanks ivan now finally i can use sjk v0.8 (now 0.8.1) after using sjk 7 for so long time.
v0.8.2
Fixed LZX
still gives an error...
ivanmmj said:
v0.8.2
Fixed LZX
Click to expand...
Click to collapse
last night, i cooked 3-4 times using different settings, compression, rom version but it still gives a flash write error for me
cooking works fine except for some errors regarding some *.wma ringtone files inside SYS/PhoneRedist folder not being able to be copied (i overcame them by deleting)
flashing goes upto 100% (i used RUU via the usb cable) but the device reboots and goes to tri-color screen and says Rom Code Error.
btw...do i have to re-download every thing (SYS, EXT, *device_specific*) and the SJK_0.*.* or just the single SJK_0.*.* file?????
+1 Exactly same result since v8 and above
freelancer81 said:
last night, i cooked 3-4 times using different settings, compression, rom version but it still gives a flash write error for me
cooking works fine except for some errors regarding some *.wma ringtone files inside SYS/PhoneRedist folder not being able to be copied (i overcame them by deleting)
flashing goes upto 100% (i used RUU via the usb cable) but the device reboots and goes to tri-color screen and says Rom Code Error.
btw...do i have to re-download every thing (SYS, EXT, *device_specific*) and the SJK_0.*.* or just the single SJK_0.*.* file?????
Click to expand...
Click to collapse
No, if you already had the *_0.8 for all the files, just download the SJK_0.8.3. If you didn't have anything, download EVERY file that's not device specific and your device's file.
You're getting a flash write error?
Still error
what might be the problem????
flashing goes upto 100%, device reboots and goes to tri-color screen
and displays a "ROM CODE ERROR".
i tried all compression methods including UPX on EXT packages but same problem.
freelancer81 said:
what might be the problem????
flashing goes upto 100%, device reboots and goes to tri-color screen
and displays a "ROM CODE ERROR".
i tried all compression methods including UPX on EXT packages but same problem.
Click to expand...
Click to collapse
I think I know what happened. Please hold while I work with airxtreme to fix it.
gooooddddyyyy....i am looking forward to it!!!
Try this:
http://justkitchen.info/main/rokdownloads/SJK_0.8.5.7z
Please let me know ASAP if it works.
thank you for your promptness...i will surely try and let you know.
freelancer81 said:
thank you for your promptness...i will surely try and let you know.
Click to expand...
Click to collapse
Did you ever get a chance to try it out?
Well hello everyone.
I am an application development student from Belgium.
I am proficient in Java, VB.NET, some c/c++ and also PHP/JS/HTML/CSS
Anyways, my recent interest has been going out to creating custom roms for the galaxy S!
The problem now is though, I was able to find some guides and such, but most were incomplete, and for HTC(and other) devices.
I have no idea what is different between making a ROM for galaxy S or a ROM for an HTC device.
If anyone would like to link me to some good resources that can help me on my way, or would like to collaborate (and in the meanwhile teach me a bit) I would be more than happy! (I am open for collaboration as I am pretty proficient in Java and I'm always happy to code and learn more about coding!)
I think the question is really want you want to do!
Custom ROMs for Android are as simple as using recovery console to replace files on the system with your own versions.
ie. Replace the framework.apk which contains all theme images with your own modified one, which you can use to skin the device. Same for replacing other system apps.
Unfortunately, most of these apps are closed source, so modifying them is difficult. The stock android system has open source versions of most of them though, and you can modify those and build them, and then replace the ones on the device. I'm not entirely sure how to build them up though, but it probably isn't too hard.
Then there are custom kernels, which let you actually change the underlying linux system underneath android - Samsung has an open source version of the kernel available that you can compile, and then flash to your phone using Odin or other tools. Compiling the kernel is pretty tricky though.
Well i'm really talking about stuff like SamSet, MoDaCo, Doc's ROM and others.
I'm not saying I want to create a pro ROM in a day or anything, but i'd really love to learn more to get better (always looking for more stuff to put on the resume, I guess?!)
Thanks a lot,
Kenny
Bump for some help
(sorry for the double post but i'm really eager to learn)
I don't have time to give a detailed response right now. However you will want to read up on yaffs (file system) and odexing/deodexing ROMs.
Thank you I will definately do that,
I am following a guide now to start out creating custom ROMs for android, however it was written for Motorola Droid and I have no idea what you have to do different for a samsung galaxy s.
I am a good coder, even though I say so myself, with a lot of experience. I also have a lot of linux experience, you name it
Only the problem is the old, and much known "where do I get started?"
So if anyone can point me out in the right direction on that, tell me how/where you started out, I would appreciate it greatly!
Thanks!
Very sorry to bump again
I set up my environment in ubuntu today to get started (just gotta fix a few errors, didn't know android wouldn't compile on java 1.6, only on 1.5)
Anyways, still need some help here! thanks!
Again I am awefully sorry for the bump here but i'd really like some help.
Note that i'm not a newbie at coding whatsoever and i'm not unfamiliar with some hardcore java, c/c++ and other languages, I'm just having trouble getting started when it comes to modding an existing android release (there are tutorials on HTC and other devices but some methods do not apply to the galaxy S)
If you're trying to create a ROM from scratch then unfortunately you're out of luck at the moment. No one has really managed to do so yet. By "from scratch" I mean the Android Open Source Project (i.e. official Android git repository).
What you can do is grab an existing firmware. Extract the contents, de-odex the apks, modify them or add new apks, optionally you can also compile a custom SGS kernel using Samsung's kernel source. Then you can re-odex the ROM, pack it back up and distribute it.
There's no real "starting place" as such and you won't yet find any tutorials about how to create SGS ROMs. Just give it a go and see where you get.
Yes, I do mean creating a ROM from stock samsung firmware, of course.
So my next logical question would be now:
How do I go over extracting contents from the existing samsung firmware, de-odexing and so on?
Any links/guides/tips are greatly appreciated, as long as they are applicable to this cell phone and not totally crap, thanks!
Samsung uses rfs, I think you should know. There is a thread somewhere in this forum regarding extracting .rfs file. Understood you need Debian though.
For some readup, go search for a famous guy named JesusFreke. Tons of materials...
Hope that from here onwards, this can lead you on, and to find out more. Google is your friend too...
I'm afraid my biggest problems already occur in setting up the environment, so it's really the very beginning that gets me stuck, i'm sure coding would be a bikeride compared to setting up the environment for me (i'm no hero in linux,not at all, i'm afraid)
How the hell do I get from point A (being downloading the full source) to point B (starting to create a custom ROM?)
thanks
of course if anyone has the time, and wants to, you can PM me your msn or something, if anyone is up to it
Raykoid666 said:
I'm afraid my biggest problems already occur in setting up the environment, so it's really the very beginning that gets me stuck, i'm sure coding would be a bikeride compared to setting up the environment for me (i'm no hero in linux,not at all, i'm afraid)
How the hell do I get from point A (being downloading the full source) to point B (starting to create a custom ROM?)
thanks
of course if anyone has the time, and wants to, you can PM me your msn or something, if anyone is up to it
Click to expand...
Click to collapse
Agreed completely! Getting a full cross-compilation to Samsung's Android going is seriously difficult! There have been some promises for tutorials and guides for setting things up though, but none have appeared yet. Probably because it's hard!
Well thank you for agreeing with me on that.
I am really hoping for anyone that can help me out here, either on here or in private, and give some detailed instructions on how to get started.
Hell there is enough information on creating roms alread, deodexing, adding/removing apps etc etc etc... The real problem lies in setting everything up properly.
I think I have gotten to the point where I'm compiling the android source (without samsung specific files)
note i'm saying "i think i am compiling" because i'm hoping it won't error out on me again after an hour of compiling!
But once that is done... I have no idea where to go next, where to get the samsung specific files, or what to do with them whatsoever once i have them
thanks!
Android generic source won't actually help you much. Samsung has made a huge number of changes to it, and while it is all open source, backporting their changes to get your stock source running on the phone is a major undertaking. I believe cyanogenmod was actually working on this, but it seems without much success so far.
What the other rom makers you see are doing is taking a snapshot of a running rom, copying over all of the APKs and the files on a running device, and then tweaking those. ie. Opening up framework-res.apk and changing the image files inside.
The update.zip roms that are what most people are doing are really just using the Android recovery to replace files on the phone with their own versions. Since the underlying system is linux, and everything is a file, this actually works pretty well.
The kernel development effort is completely separate from the rest of the system though, and Samsung has provided the entire source tree that just has to be compiled. I'm a bit stumped myself on all the details of setting it up, but I have seen some threads on this forum about it, and it didn't seem too bad to set up. Apparently you shouldn't use the codesourcery toolchain though, or something. Not too clued up on it, sorry. Hopefully someone with the details can chime in, or give us a link to the old post on it (I'm failing to find it using the search function! )
Alright sounds good!
So these recovery files you are talking about (the contents of /system) how do i retrieve those from a base ROM such as JM7 or the likes after a clean flash?)
Raykoid666 said:
Alright sounds good!
So these recovery files you are talking about (the contents of /system) how do i retrieve those from a base ROM such as JM7 or the likes after a clean flash?)
Click to expand...
Click to collapse
Root your phone, zip them up onto the sdcard, and then copy them off.
There are probably better methods, but this works fine.
Also, with credits to Unhelpful, he has told me that the correct toolchain to be using is 'uClibc or eglibc toolchain with ct-ng'. I have no idea what to do with that yet, but it's a start.
RyanZA said:
Root your phone, zip them up onto the sdcard, and then copy them off.
There are probably better methods, but this works fine.
Also, with credits to Unhelpful, he has told me that the correct toolchain to be using is 'uClibc or eglibc toolchain with ct-ng'. I have no idea what to do with that yet, but it's a start.
Click to expand...
Click to collapse
You don't even need to root your phone to pull /system Ryan
adb pull /system <random folder>
is all you need ^^
Alright thank you, I managed to get all the /system files using abd pull /system
now next thing up would be de-odexing right, before I go editing stuff?
Now before I go de-odexing. Can anyone tell me what exactly de-odexing is and why I need it?
and what do I need to do to create an update.zip again?
thanks a lot all!
Tayutama said:
You don't even need to root your phone to pull /system Ryan
adb pull /system <random folder>
is all you need ^^
Click to expand...
Click to collapse
Haha cool, didn't know you could pull whole folders!
Raykoid666 said:
Alright thank you, I managed to get all the /system files using abd pull /system
now next thing up would be de-odexing right, before I go editing stuff?
Now before I go de-odexing. Can anyone tell me what exactly de-odexing is and why I need it?
and what do I need to do to create an update.zip again?
thanks a lot all!
Click to expand...
Click to collapse
The apk files in Android are odexed - that means they have a special index applied for dalvik that speeds them up somehow! I don't know how, I haven't checked how it actually works.
The important point is though:
odexed is faster, but you can't edit it because of signatures or something technical
deodexed means you can change it however you want
More useful info can be found from google - lots of it!
update.zip is easy - it's a zip file in a special format that can be understood by Android's recovery console. The easiest way to do it is to grab an existing update.zip and modify it as needed. Tayutama has millions of em around, so use his!
Then you need to sign it once you're finished with it so that the SGS will accept it. Samsung made a boo-boo and didn't disable the test keys for the 2.1 SGS firmwares. That makes it easy!
http://www.londatiga.net/it/how-to-sign-apk-zip-files/
Just use the test keys to sign it, and then copy it to /sdcard/update.zip and reboot into recovery and it'll work.
We have an imageinfo.bin, and S000, S001, S002, and S003. We need to combine them somehow.
So, I've found threads that will teach you how to create ROMs based on imageInfo.bin files, but does anyone know how to take the pieces of a DLL (or executable) and put them together as a standalone DLL? We are trying to do that in this thread: http://forum.xda-developers.com/showthread.php?t=844008&page=3
For an example of what we are trying to assemble, check here: http://forum.xda-developers.com/attachment.php?attachmentid=444604&d=1290160423
You need to get recmod.exe.
Awesome, thanks! You rock.
I'm running into an error message though, "Error! ProcessCase0: bit 5 is zero!" I think maybe the file format for windows phone 7 is different. Is there anywhere I can go to understand this problem, and maybe get the source code and fix it or something?
FWIW my suspicion is that recmode.exe doesn't properly handle signed binaries, since all the WP7 binaries are signed, but previous WM versions weren't all signed.
Ondraster probably knows the right way to re-file them.
OndraSter doesn't know the actual way .
Binaries in WP7 are a bit different, maybe those e32 and whatever (I haven't dug into this ever, don't understand it and I'm not sure it is worth learning, since WM is going off and WP7 won't be cookable or worth cooking) are different and recmod can't handle its new awesomeness .
Hey OndraSter,
Thanks for the reply. It seems it would be something useful in our efforts to run native code on Windows 7 to be able to recmod those things. Do you have the source code, or any tips on how to go about figuring it out? I can give you all the credit, all I want is to be able to assemble the files!
I have the same problem...
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
So I'm trying to simply add NoDo's Copy&Paste to DFT Original ROM, but i keep getting stuck and irritated.
You ask why? Well because at first all the ROMS were great and very thankyou to our smart developers but ever since the MANGO sdk was released people started adding mango parts to their ROMs and keyboards and FIREWORKS!! but that caused the ROMs to increased in size from 190~mbs to 200-300mbs. The issues comes up when flashing the part04 of the Data.zip and it fails with a sending memory block blah blah blah issue. A fix was announced of simply flashing the OS.nb or something but then none of the tools used are available anymore
Now i've read threw Yukis thread on how to simply extract the sys folder from the IMGFS of lets say the NoDo release for the HD7 and adding it to DFT's IMGFS and poof your done you got Copy&Paste, but for me i get stuck.. I cant figure out how to simply add the sys folder.. Now i bet its so dam easy that i overlooked something that's starring me in the face but i've tried like 6 times and each time get pissed off and just want to punch the screen.
SO if anybody can just clarify the steps to be more straight forward that be very much appreciated
And no smartass comments, don't reply unless it helpful please