First things first! As the topic states, this is a *TEST ROM*
DO NOT expect this ROM to be usable for every day use
DO NOT expect this ROM to be well tweaked for performance
DO NOT expect this ROM to ... you get the idea, i hope!
This is the first Test ROM for the Image Update service - this ROM has a 1024KB free space buffer for NK partition, 20MB free space for OS partition. This should be enough to facilitate several ImageUpdates for testing. (It's not intended to have enough space for you to add all your chosen apps for every day use - this is just for TESTING!)
It's based on WM 6.5 21812. This ROM is unique in that both the NK and OS partitions are completely uncompressed, rather than using either XPR or LZX - so i'm testing that too. Please report on overall system performance of the BUILT IN applications (not cabs or packages you install) - i'm wondering if Uncompressed is viable at all vs. XPR and LZX. So far i'm thinking no (60MB LZX -> 80MB XPR -> 150MB Uncompressed) - but testing is warranted!
The Image Update packages for this ROM are now in post 2!
Here's the download link!
Again, this is BAREBONES, the ONLY thing it has is drivers and comm manager, this is done on purpose, so that we can have as few variables as possible while testing deployment
http://rapidshare.com/files/244900505/ImageUpdate-ready-ROM-Raphael.rar
Some notes:
The ROM has an OS pagepool size of 26MB
The ROM has a ULDR pagepool size of 4MB (up from 1mb)
All compression is disabled entirely (not XPR or LZX, but Uncompressed - both on NK and OS partition, also compression is disabled on individual modules and files)
Dr. Watson (Error reporting) buffer reduced from 300K to 0K
Update Packages
QuickGPS
EzInput+eT9
Camera - This will install the Camera, Dshow, Mhub, and SensorSDK packages (Camera is dependant on the others)
Here's the test case scenario - create a directory named "Release" in your filesystem, at the root \ folder (so \Release)
Copy the cab.pks to your device, or sd card, and run it as you would a cab
Note any errors or anything that might occur before the process succeeds or fails
If the process fails - please attach the logs found in \ and \Release to a post, so we can analyze it further
If it succeeds, time to hard reset your device!
Check and see if the package remains after hard resetting.
If it does - We have a winner
A live-updating rom with no need to reflash the device after each upgrade? I love it!
Keep up the good work!
Interesting concept.
this is awesome! cant wait to cook one for kaiser(hint, hint) thanks for all your work, this is going to change EVERYTHING.
Image Update System
I have been following the WM Image Update System thread and the idea sounds very doable. How can we help?... David.
I can Hard reset my phone every day, so if you in need of any volunteers Im here .
I have been following your kitchens for a while, and it's time to return the favor.
Thanks so much for your hard work Da_G!!
-------
HTC Fuze - WM6.5 21812
Da_G...Sir, you are a saint and a scholar...when this is finished it will be the coolest thing since velcro...
I would love to help just let me know how...would be happy to test..report...etc.
Dreaming of the day...no more hard reset
Da_G,
Thanks for your hard work.
I'll been dreaming of the day when I don't have to reflash my ROM or hard reset just to update the software.
I'll beta test and give you report.
D/Ling now, will report after work this evening. :excited:
i am really enjoying the speed. its unreal. every thing else seems normal. i am still loading up my apps right now. i'll post up some more when i get home.
the speed and respon se is secon d to none . i am very much plea des with the performance .
i know you said its barebo nes....so. i will view the lack of came ra e xe and .net. fram ework as by design . let me know if there is anyt hing spe cific you want me to test .
rzanology said:
the speed and respon se is secon d to none . i am very much plea des with the performance .
i know you said its barebo nes....so. i will view the lack of came ra e xe and .net. fram ework as by design . let me know if there is anyt hing spe cific you want me to test .
Click to expand...
Click to collapse
I'm going to need you to test your awesome space bar, it seems to be more than working well... =P
LOL, didn't overwrite CompIME.dll in this release (again for compatibility reasons) so that's why the jacked up spacebar..
But hey, it's a test
Hoping to have packages for you soon
Everything is working smoothly, no issues yet. I read your other post on the image update and want to know how far into user customizablity we can go without messing up the update process, ie. regedits, packages, etc.. Or if its a secure core that we can't really mess up.
Oh, yeah, its supper snappy and extremely responsive. And running at 26% Memory isn't bad either.
Is it safe to assume any updates needed to be deployed, such as over writing the CompIME.dll will be done thru the this new Updating system, correct?
Thanks for your hard work Da_G!!!
So, am I correct that any chefs who want to incorporate the working updating system into their roms will have to cook unprotected? This could get really interesting, LoL.
Thanks for the awesome work!
@Farmer Ted:
Yes, to support Image Update, ROM's will need to be fully "unprotected" - protection is really just damage to the ROM structure that still allows the phone to work
@NFRCER:
Yep, that will be one of the first test packages probably
@danthman2000:
The only thing you need to be concerned about in doing mods is that any files you replace or registry settings you change that might be in a future update, the update will not apply them, unless its specifically set to override your settings by using an mxipupdate_*.provxml - but the creator of the package should be aware of this before hand - so if it needs to override any of your settings it should be set to.
By the way, I plan to have the first test .cab.pkg up by tomorrow, so if you're sitting there with the test rom flashed, might wanna go back to a working one for now
Da_G said:
@Farmer Ted:
Yes, to support Image Update, ROM's will need to be fully "unprotected" - protection is really just damage to the ROM structure that still allows the phone to work
@NFRCER:
Yep, that will be one of the first test packages probably
@danthman2000:
The only thing you need to be concerned about in doing mods is that any files you replace or registry settings you change that might be in a future update, the update will not apply them, unless its specifically set to override your settings by using an mxipupdate_*.provxml - but the creator of the package should be aware of this before hand - so if it needs to override any of your settings it should be set to.
By the way, I plan to have the first test .cab.pkg up by tomorrow, so if you're sitting there with the test rom flashed, might wanna go back to a working one for now
Click to expand...
Click to collapse
A working one? This one is working beatifully lol .
Im curious, I checked the system tab, and I didnt see the Windows Update Icon...
How will we check for the update then? Just wondering, thats all.
My apologies if im asking too many questions
Great news Da_G. I'll test it once you post the update tomorrow. How do the updates get delivered?
Is the .cab.pkg a small file which contains the server information so the phone can go out and retreive it? Or is the .cab.pkg the whole kitten caboodle?
Related
I just put together the following pieces
OS 1.72.00WWE
Radio 1.17.00
ExtROM 1.72.902
"CountryCode" = TMOBILE
All configured for T-Mobile NL
Plz. Post any comments
(Plz. note this thread replaces http://forum.xda-developers.com/viewtopic.php?t=11781 )
8-11-2004 20:57 GMT: New version V2 uploaded.
I added a small archive containing the changed ExtROM files to solve the earlier reported errors (not updating ExtROM version and not making IIWPO un-installable).
Comment on IIWPO and making it un-installable: After having customized & installed IIWPO, you will have to do one of the following to make it un-installable if youre using the 1.72.902 ExtROM:
a. Another hard-reset
b. Running Version_172_902.cab from the ExtROM
NOTE: This thread is being replaced by
http://forum.xda-developers.com/viewtopic.php?p=68652#68652
Thank You!!!!!!!!!!!!
I am d/l'ing right now and will be installing shortly...
One request... You might want to include the cab for setting up IIWPO in case someone is installing it into the phone.
edsub Thanks.
Question tho. Can I use this for T-Mobile USA and does it fix the MMS problem ?
asking because the version says NL, isnt that the Netherlands country code ?
Thanks again
Well from first look everything seemed ok.
THese are a few of the things I have noticed since loading.
1. The ext rom version # doesn't show up in the info
2. If you use the IIWPO then it still shows in the remove list
3. The new apps from the 187 version will not install no matter what you do. (I have tried adding the ver # in the Reg, both 902, and 187 (not at same time)) Niether worked.
These are the few things that I have found since loading. If I find any more I will loet you know. Other than these I think you havea winner here!
I was wondering about the streaming MMS, the new bluetooth stack, and some of the other new versions of software that came in the 181,187 packages, and why you didn't include or update to them? Was there some incompatibality issue?
Thanks and great job!
Re: Home-cooked 1.72.902 upgrade package (1.72.00/1.17.00) T
edsub said:
I just put together the following pieces
OS 1.72.00WWE
Radio 1.17.00
ExtROM 1.72.902
"CountryCode" = TMOBILE
All configured for T-Mobile NL
Plz. Post any comments
(Plz. note this thread replaces http://forum.xda-developers.com/viewtopic.php?t=11781 )
Click to expand...
Click to collapse
Is SRS included?
SRS is not included due to the fact that I don't see any use for it personally. Since it is an ExtROM installer, you could add it yourself.
The NL is only there because some sdetting are more or less specific to the Netherlands. I had feedback on my earlier 1.72.901 package that it worked for other countries (incl USA) as well. Be prepared that the date format will be dutch by default (easy to change via settings though).
Also MMS is suposed to be working (but I have not tried it due to lack of interest in MMS)
The ExtRom# is not showing because some bug in the Version_172_902.cab. Working on that now.
IIWPO not showing in the remove programs list is a bit more difficult than it seems if you install for the first time. Normally you would boot up the device with new rom. IIWPO is NOT installed at this point. Once you have customised & installed IIWPO, you will have to do ANOTHER hard-reset (ie run the ExtRom contents again) to disable the uninstall. You could force this by hand first time to re-run Version_172_902.cab after installing the customised IIWPO. BUT as this cab is not OK, it wont work anyway. Working on that now.
I did not find the time to look into the new O2 apps. If someone finds a solutiuon here, I am more than happy to includew it in a new version.
For the streaming MMS, the new bluetooth stack, and some of the other new versions of software that came in the 181,187 the basic reason is lack of time. I dont know what 'extra' new there is on bluetooth in the O2 builds? OS Rom 1.72 allready has an updated BT stack that fixes most open issues. I have no experience (& interest) in MMS / streaming MMS . . .
I suppose the issue with TomTom locking up without GPS enabled is not solved with this rom ?
I know: wishful thinking..........
@Pleun: Nope. I WISH I would have solved that one!!! FYI: I tested he new TomTom GPS 3.07. It doesnt solve any locking issue and next to that makes my Headset react very slow. Also the 'Bluetooth GPS' option that is supposed to solve the locking has gone, at least with my installation. Not advisable. I reverted back to TomTom GPS 3.03.
@all: I solved the issue of not setting the Ext Rom version and making IIWPO non-uninstallable. New version V2 will be up in 10mins (incl. incremental fix for all that downloaded the version from yesterday).
New V2 is up now. See first post in thread.
Plz keep posting comments to make this upgade better
edsub said:
New V2 is up now. See first post in thread.
Plz keep posting comments to make this upgade better
Click to expand...
Click to collapse
I feel like my MDA2 is a little bit slower to respond not sure why! I added PocketMVP, Belkin Bluetooth GPS, Resco Explorer 2003 V5.0 and .NET Compact Framework 1.0 SP2 for Pocket PC 2003.
I am having problem with Belkin BT GPS; I got it to bond, detect the COM port (COM5) and baud rate(4800) to use but my MDA2 hangs up and had to soft reset. Any idea why?
I will try to install one by one and see what's causing it and report here.
edsub thanx for me it works great its a great improvement!
machine seems faster and no more lock-ups.
Keep up the good work (ill be following you)
p.s only one thing my battery seems to give me no more than 4 hours of on-time
4 hours is very different from my (and others!) experience. The 1.72 rom should even improve battery life.
My battery lasts for about 1,5 days (not measured but recalled from my memory) with approx 1-1.5 hours on the phone and bluetooth permanently switched on . . .
were can I download this rom from?
from the first msg in this thread : RUU172902WWE_eDsuBsofT V2.exe
Hi me again, dont want to sound stupid but I've tried both Opera and Explorer and cannot find any executable file in the first post. Normally it appear in some sort of info box but none to be seen on this thread and the link to the previous one!?!?! Is this something to do with XP SP2?
Anonymous said:
Hi me again, dont want to sound stupid but I've tried both Opera and Explorer and cannot find any executable file in the first post. Normally it appear in some sort of info box but none to be seen on this thread and the link to the previous one!?!?! Is this something to do with XP SP2?
Click to expand...
Click to collapse
You cannot download it as a guest! If you are a member of this forum you have to log-in before you can see the file you want to download. That's what I encountered before so just try logging in first.
Good luck!
THank you very much superperry. Should have registered before but was always too lazy.
I have put together rom upgrade 1.72.903
This thread can be closed. See http://forum.xda-developers.com/viewtopic.php?p=68652#68652 for the new one
Edit: The new upgrade files are now available (see refered post)
An error need help please
I downloaded the files then followed the instruction below but now I get error
the flashing process
first the devicedata is obtained from the device, with HimaGetDeviceData.exe, this gets the operatorname, and language/country code from the extended rom, sector 2 of the BDK.
Then a tool 'HimaClearJumpCode' is executed, which erases the jump at the start of the kernel. causing the bootloader to start at next reboot.
the upgrade tool then connects to the bootloader of the xda, via serial over usb. ( port \\.\WCEUSBSH001 )
warning do not just run the 'HimaClearJumpCode' program, it will erase part of your OS rom, after which you will have to repair your device by running an entire upgrade again.
Hello all!
Here is the new way of rom cooking and upgrading for our Prophet:
- new original XIP
- original drivers
- original OEM from 734 ROM
- fast official update method without downgradings and first steps
- no miniOS partition + LZX compression of IMGFS (+20Mb Storage to install programs)
Stable and fast!
---
This is a clean rom with no additional programs and themes installed cooked with official Artemis WM6 SYS part. Only Office mobile updated to the latest version and some unused applications removed. Original 12 Mb poolsize - can be changed later.
No screenshots because you can't see something new - clean official rom with official theme
Update instructions:
1. Download g4.zip attached if you have G4 device or download g3.zip attached if you have G3 device. Unpack it to some place on you PC. You will have 2 dirs inside: "jumpspl" and "update"
2. Copy 3 files from "jumpspl" dir to the root of your Prophet (near Windows folder)
3. Download and unpack nk.nbf to "update" folder on your PC ( Download link: http://rapidshare.com/files/73971476/nk.rar.html )
4. Disconnect your device form PC
5. Run "SPL.lnk" in the root of your device from File manager. You will see a white screen
6. Connect your device to PC with USB cable
7. Run "ROMUpdateUtility.exe" in "update" folder and follow all steps
8. You can see process indicator only on PC! Screen of your device will be white during all update process. When finished your device will reboot.
9. Enjoy
---
If you want to change poolsize - download "korand_wwe_1_change_pool_size.zip" attached. This is patched Paradis utils. Just connect your device to PC with Activesync and run .bat with needed poolsize.
---
Bass boost and earphone volume up - download "korand_volume_up.zip" attached and see readme.txt for details. You need to import the registry files (I do it by Resco Explorer).
---
Based on firestarter prophet rom from 4pda.ru
Thanks to Prislav for his work and help
[size=+1]New version available:[/size] Korand WWE 2.1 Clean
OK, waht's inside the ROM? Picture, themes, included programs...
please give some screenshots and some description about everything inside your ROM..
thanks
matthze, varanusvincent - its a clean rom with no modifications or additional programs and themes installed.
The main advantages of this rom are: original XIP, drivers, OEM part and no Extrom (+20 Mb to storage).
All native - no bugs with drivers!
And OS part can be taken from any WM6 ROM. I take OS part from official WM6 update for Artemis (a little old build 17745 - but official and stable) - but can take any other.
Sounds very interesting
Had someone already tried this rom?
Feedbacks?
Looks like a normal WM6 ROM.
I didn't flash it jet. The new Cam software is inside.
Which WM6 Build is this based on? And what is the value of free storage?
This looks interresting.. Iam really considering to try it out..
Anyone got it flashed ?
If it does include the new camera s/w, does it have the same battery drain reported by others?
I'd be interested in a review from anyone who's installed this. I would do it myself but I have no time this week. Thanks for posting it, I don't know why but I expect it will be very good.
thankx man...
downloading...
Virus Alert
AVG reports "Dropper.Agent" in both the G3 and G4 files attatched.
Please be careful. Let me know if this is in error.
skylow said:
Looks like a normal WM6 ROM.
I didn't flash it jet. The new Cam software is inside.
Click to expand...
Click to collapse
new cam?? if it refers to the "new camera", the ansewr is negative.
however, this rom is really interesting, fast and responsive so far...
iiiox said:
new cam?? if it refers to the "new camera", the ansewr is negative.
however, this rom is really interesting, fast and responsive so far...
Click to expand...
Click to collapse
Okay you have it iiiox ? Great ! What about a mini review my friend.. ?
Screenshot?
Can you post a screenshot?
Da9L said:
Okay you have it iiiox ? Great ! What about a mini review my friend.. ?
Click to expand...
Click to collapse
Sure, my friend^^" just mention a few noteworthy as below:
@Korand: Many thanks for sharing
Speed: Fleeting
it takes less than a quarter round of the waiting cursor to open the windows folder with 14xx files / omap 264HMz (not as precisely a way to measure the speed, but certainly enough for a quick review^^")
Whether or not the speed lasts after intalling various apps remains more observation
Memory: A LOT
Storage : 57.41M
Program: 24M+ (12PP)
Both available storage memory and program memory are definitely amazing! 24M+ for program seems not so appealing at the first sight, but if the additional 6M is added as other roms with 6 PP, the total available program memory will be over 30M+
Stability: Not quite sure, but it "seems" not very optimistic^^"
Without the stability-killer "nls with chinese regions", something negative occured as below:
1. SD card missing happend once
2. The compatibility seems not good. The super lean HTC Home modified by hma4 doesn't work, celedial, a smartdialing-like app, doesn't work, either ...(try some other version later / edited: HTC.Kaizer.Home.Plugin.with.Tabsetting.schen.cab works. not sure if anyone installs incompatible apps above with luck...)
3. No "start" sound effect like the early roms from Gullum (easy to deal with though)
4. Old camera, and the quality is, unfortunately, horrible....(see the thumbnail) Note: for this single reason, i've backed to my favorate one^^"
Others:
1. No touchflo (might try FtoughFlo later)
2. No smart dialing
All opinions above are merely my very personal experience. You may find it much better than I observed and vice versa. Yet it's always touching to know that some more wonderful people are still trying to last the legend of our prophet^^
korand have you patched TrueFFS.dll to merge the extrom with storage ?
How did you manage to merge the extrom ?
iiox :
the reason your camera is like that is because you overclocked your device.
thank you!
hma4 said:
iiox :
the reason your camera is like that is because you overclocked your device.
Click to expand...
Click to collapse
Thank you very much for the info^^"
I've noticed that....yet i used to "review" all roms with conditions as similar as possible. Although it's impossible with the respect of speed or stability, the quality of camera can be an exception....maybe...^^"
BTW, I'm so curious if your super lean HTC Home can be installed properly into this rom^^? I tried and failed >_<"
iiiox said:
Thank you very much for the info^^"
I've noticed that....yet i used to "review" all roms with conditions as similar as possible. Although it's impossible with the respect of speed or stability, the quality of camera can be an exception....maybe...^^"
BTW, I'm so curious if your super lean HTC Home can be installed properly into this rom^^? I tried and failed >_<"
Click to expand...
Click to collapse
i haven't flash this rom yet (no time) but maybe the reason is that cooker of this rom haven't applied the security off package. anyway, where did you find my home plug in ?! in extrom folder of crystal V4 ?! because that cab file is only for Crystal V4.
I will look inside this rom later when i had time then i can answer your question.
hma4 said:
i haven't flash this rom yet (no time) but maybe the reason is that cooker of this rom haven't applied the security off package. anyway, where did you find my home plug in ?! in extrom folder of crystal V4 ?! because that cab file is only for Crystal V4.
I will look inside this rom later when i had time then i can answer your question.
Click to expand...
Click to collapse
Only for Crystal V4....? no wonder then -_-"
Anyway, patiently wait for your experience about this rom and ...hehehe...your V5
I've been struggling over the past few days trying to get the latest AT&T ROM working in a kitchen. I've tried three different workstations and two Virtual Machines assuming it was an environmental issue.
As a result, I decided to create a fresh new "old style" (PkgToolsBuildOS) kitchen on the assumption that something was wrong with my kitchens.
Noticed the following anomalies in the fresh new kitchen:
1) XIP.BIN / OS.NB.PAYLOAD
Noticed that when performing a Find Date/Rom Version on PAYLOAD or Find Date/ROM Version on XIP_OUT.BIN using XIPPORTEREX 1.2 rev32 , I get the following information:
Date: 06/May/2009
Rom Version: [K] InitDr
I've used the standard process that I always use which yields a working OS.NB.PAYLOAD and even validated it against Aruppenthal & Da_G's sk00ling.
Essentially: PP Unlock, NoCert Patch, PP = 6 MB ... same OEMXIP & MSIXP kernel for now just to try and get it to work.
2) Compiled ROM
If I change the ROM Version & update the Date (as per usual), the ROM compiles fine and boots. However, I am unable to connect to browse the Internet even though the 3G/H data connection appear indicating that a connection is established.
The ROM, OEM, SYS are all 20771 (5.511.502.2) for now just to try and get it to work using my Rogers SIM.
Has anyone else run into similar anomalies before? Cause I'd sure love to know what the heck I'm missing/doing wrong.
* EDIT *
Some of the "paranoid" measures I have done: Rootkit Scan, Full Anti-Virus Scan, Mem Test, Hard Drive Diag, CHKDSK, Restart, typical IT stuff ...
I'm not really sure what could be wrong, but if you need the dump set up for Visual, I had no problems dumping it and uploaded the untouched "Kitchen" to my FTP. Its labeled correctly as the build number 5.11.xxxx. I wish Icould help more, as you have helped me out a bunch.
EDIT: I did dump a ROM recently and got the same Version ID with xipporter as you have mentioned, but thought nothing of it. And I dont remember which it was, so sorry still not very helpful.
The ROM Version "garbage" is odd and IMHO should not be like that - your confirmation that you saw the same thing is very helpful ... at least I'm not losing my mind completely.
I'm trying to keep a PkgToolsBuildOS (5.3) and a Visual Kitchen (9.8) going for folks to use.
I had gone through all of the effort to port 21051 (SYS) and 20771 (OEM) in the hopes of posting it up before the end of the weekend ... then I started running into these unexplained issues and ended up scrubbing the lot.
I'm in the midst of recreating a new Visual Kitchen (9.8) and am discovering additional files in the OEM folder that weren't there before in older versions of the Visual Kitchen - not sure what it means yet; sure hope it doesn't mean having to recreate a kitchen everytime there's an update to the tools.
Cheers,
hilaireg said:
I've been struggling over the past few days trying to get the latest AT&T ROM working in a kitchen. I've tried three different workstations and two Virtual Machines assuming it was an environmental issue.
As a result, I decided to create a fresh new "old style" (PkgToolsBuildOS) kitchen on the assumption that something was wrong with my kitchens.
Noticed the following anomalies in the fresh new kitchen:
1) XIP.BIN / OS.NB.PAYLOAD
Noticed that when performing a Find Date/Rom Version on PAYLOAD or Find Date/ROM Version on XIP_OUT.BIN using XIPPORTEREX 1.2 rev32 , I get the following information:
Date: 06/May/2009
Rom Version: [K] InitDr
I've used the standard process that I always use which yields a working OS.NB.PAYLOAD and even validated it against Aruppenthal & Da_G's sk00ling.
Essentially: PP Unlock, NoCert Patch, PP = 6 MB ... same OEMXIP & MSIXP kernel for now just to try and get it to work.
2) Compiled ROM
If I change the ROM Version & update the Date (as per usual), the ROM compiles fine and boots. However, I am unable to connect to browse the Internet even though the 3G/H data connection appear indicating that a connection is established.
The ROM, OEM, SYS are all 20771 (5.511.502.2) for now just to try and get it to work using my Rogers SIM.
Has anyone else run into similar anomalies before? Cause I'd sure love to know what the heck I'm missing/doing wrong.
* EDIT *
Some of the "paranoid" measures I have done: Rootkit Scan, Full Anti-Virus Scan, Mem Test, Hard Drive Diag, CHKDSK, Restart, typical IT stuff ...
Click to expand...
Click to collapse
Several of the new builds are this way. Its because the date info has been moved. Until someone figures out which part needs hex edited we are stuck with stock dat Version changes fine.
Are you saying that we should *no longer* be changing the ROM Version and ROM Date?
In my case the Date "looked" ok but the ROM Version was bogus.
Which leads to these questions:
Does this also mean that PagePool Unlock, NoCert Patching, PagePool sizing are also in jeopardy of moving? (I know you or others won't have an answer for this one as it's in the hands of the OEM).
Does this mean that PkgToolsBuildOS kitchens and supporting tools are now at end-of-life?
Hate that when I forget to read the memo
UPDATE
Well, after an all-nighter ...
I can confirm that attempting to change the ROM Version and/or ROM Date via XIPPorterEX, PkgToolsBuildOS6.x-5.3, or Visual Kitchen 9.8 will indeed mess up the ROM - at least on the Raphael.
hilaireg said:
Well, after an all-nighter ...
I can confirm that attempting to change the ROM Version and/or ROM Date via XIPPorterEX, PkgToolsBuildOS6.x-5.3, or Visual Kitchen 9.8 will indeed mess up the ROM - at least on the Raphael.
Click to expand...
Click to collapse
So am I correct in assuming that when I change the PP in the 21806 version (as posted by Da_G) it is not really changing the PP. I did wonder why the amount of RAM didnt increase
B4PJS said:
So am I correct in assuming that when I change the PP in the 21806 version (as posted by Da_G) it is not really changing the PP. I did wonder why the amount of RAM didnt increase
Click to expand...
Click to collapse
The PagePool seems ok on my 6.1 builds at the moment but Da_G could best confirm that as he's been on this "circuit" way longer than I.
An observation I made, while I've been working on this, is that the PP size on the AT&T 5.11.502.2 seems to be set 1MB ... at least that's what XIPPorterEX 1.2 rev32 reports when I issue a change to the PagePool to 16MB on a non-reduced ULDR os.nb.payload.
Hmmm, Wonder why when I change my PP to 0 I still only have 197mb Total instead of about 213mb total? Might have to do a test and set it higher to see if my free space decreases
UPDATE: Direct From Da_Grand Pubba ...
Just had a quick chat with Da_G and he confirms that there's been a change in the XIP modules.
At first glance, he noticed that the NK.EXE module has three (3) new resource strings. So in short, if the ROM Version happens to display [K] InitDr (which is [K] InitDriverGlobals) DO NOT attempt to change the Date/ROM Version.
He also had a quick look for Certificate Patching, PagePool Unlock, and PagePool resizing - these appear to be untouched at the moment.
HTH,
please rom cookers have a look .can u guys cook rom for our device by this method .
if we got success in this matter no device will be bricked.
i m not so aware of technical terms .so i cant advice u guys!!
http://forum.xda-developers.com/showthread.php?t=520009
sorry for my bad english
i hope u will understand what i want to say
thanks!!!!!!!!
We are aware of this system, but right now, the system is under testing and not fully working. Rest assured when it becomes fully ready and if its possible to use it on gene, we will definately use it.
I said if it is possible, because, on gene, the concept of ULDR partition doesn't exists as far as i know. And ULDR partition is an integral component of that system. ULDR was most probably introduced in WM 6.1 but since Gene is a WM 6 device, it doesn't have the parition layout entry for ULDR. I could be wrong, this is just what my logic says based on my current information.
Also, it wont prevent bricking, as for the system to work, you will need to flash a ROM that supports the ULDR partition and the update system itself, before anything else. For that, you will need to patch your SPL as cooked ROMS will never have the HTC's digital signature. And as we know, patching the SPL is the reason behind all the bricking mess.
But anyways, thanks a lot for sharing
Double Post!
Will it ever work?
I have read the thread sometime back, but I have a few queries...
1. When you upgrade your OS from, say 98 to XP or XP to Vista, there always is a performance issue (compared to formatting your hard drive and doing a fresh install). And since our WinMo are nothing but hand held PCs (well you can say that, it got a processor, a hard disk (ROM), RAM), I guess that issue will crop up here as well.
2. What will happen if you have a 3rd party s/w which is incompatible with the new version of WM? Those of you who are in the PC tech field for a long time, you know after you have upgraded your OS, you can't use that software, neither can you uninstall it ...
So there will be issues, if I am not wrong.
But thats only my opinion. Most pple here are head and shoulders above me technically .
@Addicted: Well, Here are my opinions on your queries :
1. Yes, if the registry of the PPC is having some problems, then it will be an issue. Its a bigger issue in PCs as compared to PPCs coz in PCs the software are huge in size and they write thousands of entries to registry, modify system files etc. SO when an upgrade occurs, these changes either cause a corrupted registry, or in the second case when system files had been modified or replaced by a program, these files will be again updated by the OS and the program may not work, and if its a system level program with deep roots in system functionality, it will cause the system to slowdown at least or crash at worse.
These issues dont affect PPC much coz, for one, PPC software are usually small, they dont write much in registry (ms office on pc for example on PC writes a few thousand keys to registry while registering COM servers etc while MS Office on PPC just adds 10 or 20), and since the OS files are in ROM, they cant be touched by a software. They will remain overridden, if they have beem overridden as the updating process doesn't touch the phone memory.
2. Think again buddy, this is not applicable for WinMO. When you flash a ROM, you already change your OS version, so that will happen anyway, if you flash a ROM or you use the update system on an existing ROM.
I hope this would have cleared your doubts.
krazy_about_technology said:
2. Think again buddy, this is not applicable for WinMO. When you flash a ROM, you already change your OS version, so that will happen anyway, if you flash a ROM or you use the update system on an existing ROM.
I hope this would have cleared your doubts.
Click to expand...
Click to collapse
Actually you did not get me about the second issue, what I was trying to say is, if you flash your ROM, you incompatible program will be deleted (obviously) and thus free up space, but if you upgrade, your program will still take up space but will be of no use to you. Since most of the programs in Winmo are stored in Windows folder itself, it will be next to impossible for 99% users to identify the files to delete .
i already talk about image update in visual kitchen for gene thread, all this take lots time. da_g bepe and lots senior ppl are working on this its required new kitchen new rom format
as per i know it's required more rom space which not possible on gene rom
thanks !!!!!! guys for taking interest.
i like it because i have bricked my gene 4 times and got new motherboard.
but now my phone is not in under warranty so i cant take more risk.
i have done all methods correctly but unfortunately i was failed every time .
so after a year of trying i m still using wm5. so i want a new method without
zero risk for updating my rom.
Sorry buddy, but I dont think you can damage ur MB by wrong flash .
Update: New release (RLS 5)
-Comes with 'rogue tools' for overclocking and setting display density will need an update over market to support nike, myn told me he will push it to the market during the next day or so)
-feels smoother, connectivity seems to be a lot better (I never had a faster browsing experiance on my nike than with this build and opera mini), rejoining network after lost signal also seems to be faster
-nice new weather/clock widget
-if you use installd version, the androidupdate.tar from rls4 is still necessary for powermanagement
Myn's new (16.03.2010) Donut android build runs quite smooth on nike! Finally a decent alternative to Ion on nike.
Get it from the vogue forums (SQSH version):
http://forum.xda-developers.com/showthread.php?t=619980
Here is a link to the basefiles I am using:
http://84.23.71.227/kerneloftheday/RootfsBasefiles20100318.zip
The kernels are from dzo's branch with a few minor fixes (vibration, irq-wakeup, red led blinking when in sleep mode). Additionally the kernels should work with enabled HW3D in eclair with boot parameter hw3d.version=1 (not tested yet...).
HowToInstallInANutshell:
-delete old android files from sd
-extract basefiles to sdcard
-extract system.sqsh from myns package and copy to sd
-if you are on a nike100 make sure deafault.txt points at the kernel without vibration (included)
-otherwise default.txt should be fine, most parameters are ignored anyway.
-run haret
-be happy
Impressions:
-sleepmode 1 ok, wakes up, red led blinking. Battery life seems ok, but i only tested a few hours...
-very fast
-many locales, not just english like in good ol' ion
-quite stable net, nice apn autodetect (just had to select from two alternatives), working google stuff
-still not working: bt, incall volume, cam
So, give it a shot and leave your impreesions here!
mblaster
********** UPDATE ************
Installation with the NoRootfs Method is now possible with working net and powermanagement. This gives us the possibility to use the Themes and the default font and everything else that can be provided via androidupdate.tar
See the Wiki for installation instructions. Make sure that you have the provided 'androidupdate.tar' (see attachment, file is in the zip archieve) in your andboot folder along with the androidinstall.tar when installing.
To install themes just copy them in you andboot folder (must be named androidupdate.tar), reboot into menu -> update (-> fix permissions).
PS: Doesn't seem to work with eclair builds, but could work with other donuts
PPS: This should also work with ext2, if someone tried successfully please let me know. €: Works with ext2
Additionally the kernels should work with enabled HW3D in eclair with boot parameter hw3d.version=1 (not tested yet...).
Click to expand...
Click to collapse
you've added hw3d support? I tried to do that - all that I got is 3D without textures or simply nothing - black screen. I did same as in this commit in repo.
I did the same. The only build i saw it working was aosp eclair for kaiser (gallery3d worked). Otherwise i got the same errors. I read that the other devices suffer from similar problems.
Ps: Writing this on myns donut. Everything stable so far.
mblaster said:
Myn's new (16.03.2010) Donut android build runs quite smooth on nike! Finally a decent alternative to Ion on nike.
...
So, give it a shot and leave your impreesions here!
mblaster
Click to expand...
Click to collapse
Hi mblaster,
works like a charm here. Very fast and stable. This is the first ever Donut Build with stable working Data i've seen....
Only Point is, that icons are really very small. Seem to me even smaller than in the old Cupcake Releases with 320x480...
Tried higher settings for lcd.density, but screens don't fit than anymore.
Have you tried it with a non modded system Image ?
Greetz, lagloose
ECLAIR
because you are starting another section of the eclair?
already has almost no one accessing the other thread ...... I have a question there for two days and no one responds more ..
I am very impressed with the progress of the android in my eclair NIKI100 (20 keys)
is making calls, receiving messages, all volumes of the system are working (calls, music (I had to install another player why that came standard did not work), alarm etc. ..) I'm using it for three days, battery lasts long , it does not heat the unit, since I use it in everyday life.
now I have some questions for you:
is so difficult to operate the headphones?
I love listening to music, especially in the way of work, if possible, please someone do work ....
particularly hate wm, I think one day we niki users, we can get the WM and definitely use the android, (because you can try to do everything, are the gods of HTC ....).
another question, I can change the theme of the eclair? wanted it like this: http://forum.xda-developers.com/showthread.php?t=600154, it is possible??
I'm not charging, just begging! rsrsrsrs
Congratulations XDA....( GODS OF HTC)
Hi there,
together with mblaster's combination of basefiles in the first post of this Thread, the sqsh Version of the image in this thread http://forum.xda-developers.com/showthread.php?t=591104 works also...
mblaster; seem's you've found/made the ultimate combination for Donut Images. PERFECT !
Greetz, lagloose
Theming with Metamorph
I been reading around on Vogue's thread and Metamorph catched my attention. It can style up android theme. Is this apps runs well on this build. I am confused because based on this site http://www.androlib.com/android.application.stericson-xda-metamorph-xnFD.aspx it can only run n Rooted phones. What is rooted phones anyway and can this run well in nike100 with the android build posted in this thread?
When is the nand version available? I think the only thing missing now in nike100 are camera and vibration features. Great job!
More Power!!!
Anyone encountered the "Half Size" icon problem ?
This is, when there's a reload of the Home Screen, all icons are suddenly half the size than normal. I had this after leaving the Browser.
Couldn't find a solution for that behaviour. Any ideas ?
Greetz, lagloose
ohh, nice ROM, everything is fine except one - it says that my pin code is incorrect ;//
and what else.. is it possible to get to wifi on Nike using wifi-enabled android?
jefins said:
ohh, nice ROM, everything is fine except one - it says that my pin code is incorrect ;//
and what else.. is it possible to get to wifi on Nike using wifi-enabled android?
Click to expand...
Click to collapse
You have to disable PIN in WinMobile afaik for all builds so far.
About wifi: The stickies say no wifi on nike. Never.
"never ever say never" ;DD
thanks anyway for Pin code tip.
Network problem
got two bugs here.
1. browsed from wm then switchd to android. i cannot connect anymore when in android. even if i reconfigure my apn.
2. switching from phon mode to airplane mode and airplane mode to phone mode will stuck in airplane mode.
@mblaster
how to enable apn autodetect?
@mblaster
First of all, good idea with the new wiki. Hope to add some things in the near future...
had the idea of creating system.sqsh files of all variants (Themes) of the original Vogue Thread. So i downloaded one of the androidupdate.tar files, und untared it "over" the files of the original ones in the androidinstall.tar file. Made an ext2 System and then a Squashfs System with genext2fs.
But no success....
Booting stucks obviously just before the Android Setup Wizzard should appear. Any Ideas ? Perhaps a permission problem ?
Greetz, lagloose
lagloose said:
@mblaster
First of all, good idea with the new wiki. Hope to add some things in the near future...
had the idea of creating system.sqsh files of all variants (Themes) of the original Vogue Thread. So i downloaded one of the androidupdate.tar files, und untared it "over" the files of the original ones in the androidinstall.tar file. Made an ext2 System and then a Squashfs System with genext2fs.
But no success....
Booting stucks obviously just before the Android Setup Wizzard should appear. Any Ideas ? Perhaps a permission problem ?
Greetz, lagloose
Click to expand...
Click to collapse
me again...
just got a flash in my brain...
probably a story about the rootfs because of different load types (NoRootFs vs. Classical sqsh File) ?
so what about mounting the original sqsh Image and untaring the update "over" the rootfs ? ...
@lagloose: Might be an issue because the androidupdate.tar files are made for norootfs. Perhaps its time to move on to an installed version without rootfs...
@ebautista: Sorry, but I do not maintain myn's build. Perhaps it would be a good idea to report bugs in myn's thread in the vogue forums. APN detection worked for me right out of the box. Do you use the basefils from this thread?
€: your brainflash was faster than my typing... but perhaps you should at laest try to set the right permissions, it might work
Hi all,
Just tested sqsh Image from http://forum.xda-developers.com/showthread.php?t=628459. Not completely tested but seem to work also with our basefiles.
I'm working on a way to get themed Images for us Nike Users. Still some problems to solve, but shouldn't be that difficult...
As soon as i've found a way, i'll state it here.
Greetz, lagloose
I really would suggest to move on to NoRootFs for various reasons:
The theme packages are already available there
The basefiles are still supported and regularly updated, while SQSH is dying out, and as there are very few devs for nike we should try to profit from the progress made on other devices
There should be no drawbacks, just a few more MB on sd-card for the system
The installer for systems / updates is extremely useful (theming, installing your favourite apps in one shot ...)
Give it a try, you will find a little howto and links to ressources in the wiki
mblaster,
€: OK, I have good and bad news. The good news is that it seems like you can keep your datafile after switching to norootfs. The bad news is that sleep doesn't work anymore (same settings/build/kernel) -> The problem that prevents us from using more recent builds seems to exist inthe basefiles!!!
Basically thids leaves two possibilities: Either its in the part of the nonexistant rootfs that now is part of the system, or (my guess) it is in the initrd. At least it does not seem to be a problem with the kernel.
mblaster said:
...
€: OK, I have good and bad news. The good news is that it seems like you can keep your datafile after switching to norootfs. The bad news is that sleep doesn't work anymore (same settings/build/kernel) -> The problem that prevents us from using more recent builds seems to exist inthe basefiles!!!
Basically thids leaves two possibilities: Either its in the part of the nonexistant rootfs that now is part of the system, or (my guess) it is in the initrd. At least it does not seem to be a problem with the kernel.
Click to expand...
Click to collapse
..same here after trying. I also couldn't get a Data Connection. Obviously Network Device ppp0 is missing. So i'd guess, that your guess concerning the initrd is correct. Unfortunately, i won't have the time to look after the problem in the next days. So for now we still have to use the SQSH files, until the problems are fixed...
hi, mblaster,
i want to download the file as "Get it from the vogue forums (SQSH version):
but i cant aceessed "mediafire"
Could you email to me a file that it can running on nike100, thnks
my mail is [email protected]
See Post 1 for UPDATE!
lagloose said:
..same here after trying. I also couldn't get a Data Connection. Obviously Network Device ppp0 is missing. So i'd guess, that your guess concerning the initrd is correct. Unfortunately, i won't have the time to look after the problem in the next days. So for now we still have to use the SQSH files, until the problems are fixed...
Click to expand...
Click to collapse
I am quite sure now that the initrd is fine and the problem is in the Rootfs, or better what is left of it. The latest working basefiles include a Rootfs dated to 2009-11-16. There is a newer Rootfs on sourceforge (sometime in december 09) that shows the same problems (net/powermanagement/shutdown). As parts of the rootfs are included in the androidinstall.tar images, thos errors are still there. My update file (now included in post 1) overwrites those files with versions from the 11/16 rootfs. That leeds to a working system (with the new initrd).
Unfortunately the update is incompatible with the newer eclair builds that are around. Seems like they use another rootfs that rejects the old files...
Does anyone maintain a git repo of the rootfs? It would be interesting to patch the problem for good