Related
Hi all,
I've managed to find a dump of build 19900, however I haven't managed to make a working ROM out of it as yet. I'm hoping to find a way to get it working with bepe's kitchen tools - therefore removing the reliance on a custom chinese binary to build these ROMs.
I believe this ROM is big storage, so I'd like to make available a non big storage version as well for everyone to benefit.
Any takers to help out?
Download URL: http://rapidshare.com/files/113432995/Hermes_RomKitchen_19900.rar
CRCinAU said:
Hi all,
I've managed to find a dump of build 19900, however I haven't managed to make a working ROM out of it as yet. I'm hoping to find a way to get it working with bepe's kitchen tools - therefore removing the reliance on a custom chinese binary to build these ROMs.
I believe this ROM is big storage, so I'd like to make available a non big storage version as well for everyone to benefit.
Any takers to help out?
Download URL: http://rapidshare.com/files/113432995/Hermes_RomKitchen_19900.rar
Click to expand...
Click to collapse
Will take a look at it dude, aint got a load of time at the mo though. Might have a quick PM session and see if theres a WWE version we cna use.
Have you guys tried PM'ing Dvha79_ddt? I'm not much help on cooking but i'll try and suggest anything
Good luck guys.
Need testers let me know.
I've managed to get the ROM to build using Bepes kitchen, however it doesn't boot. It sits there at a black screen on power on...
This leads me to believe it's part of the XIP that is just wrong.
I've attached what I've extracted from the included os.nb by doing:
nbsplit -hermes os.nb
RomMaster -w 5 os.nb.payload -x -o xip.bin
Run xipport, choose Dump xip.bin
I then deleted os.nb & os.nb.extra.
Then put the XIP dump together as it should be (i think) for bepe's kitchens.
Not 100% sure where to go from here...
edit: Oh, I've attached the TOOLS directory too - just in case you don't have a copy of Bepes great work.
This is a non big storage modded 19900 xip that works.
I haven't used in a kitchen just yet.
I will have a look at the dump later on.
dan1967 said:
This is a non big storage modded 19900 xip that works.
I haven't used in a kitchen just yet.
I will have a look at the dump later on.
Click to expand...
Click to collapse
Hmmm - I've used your XIP - it boots, but same as using the default ROM kitchen tools, it hangs after displaying splash2. I replaced the OEM_FLASHDRV.DLL in OEMDrivers with a non-BS version, in case that was an issue, but still no go...
CRCinAU said:
Hmmm - I've used your XIP - it boots, but same as using the default ROM kitchen tools, it hangs after displaying splash2. I replaced the OEM_FLASHDRV.DLL in OEMDrivers with a non-BS version, in case that was an issue, but still no go...
Click to expand...
Click to collapse
For now you can try to merge that XIP with the payload from the ROM (without kitchen) and it should boot&work.
Will try to get the romhdr.bin and in fact to rebuild the whole ROM folder and let u know whats happening.
Using Dvha79_ddt 900
I know it's not what you are looking for, but I am using Dvha79_ddt ROM and it is working as well as his 701 which was very fast and rock solid. Would like to help in any way I can as I loved your ROM's apart from the issues. As a noobie where do you find these ROM's in the first place?
A lot of it is hit and miss finding things here and there - like this kitchen that seems to be almost complete, but just doesn't work. A bit of hacking around and it can probably be made to work.
As WM6.1 doesn't exist for the hermes devices, it is always ported from something else - which can lead to weirdness.
Most of it is pot luck, and a lot of knowledge (and I'm missing some in getting this kitchen working )
just a working trick
what I am sure is working (tried it before) is replace the whole ROM folder from new kitchen with your working one and then just slip in the xip.bin into the new payload in a few steps.
Still can't get this working....
I've changed the BuildNB.bat to show the following:
Code:
echo.
CD ROM
..\TOOLS\buildxip.exe -b
if not "%errorlevel%"=="0" goto error
del out.bin
copy xip_out.bin out.bin
CD..
This should use your XIP in the ROM, which shows as 3.62.07.Dan - however I still can't get past splash2... Eventually, the backlight goes out, but it doesn't seem to display anything past splash2... Eventually, the screen goes off (power setting). Turning it back on via the power button just gives me a white screen... I'm at a loss to figure out what's happening here.
The OS.nb.payload is the same (non-BS) that I was using from my 10.1 release of my ROM, and the XIP folder contains the same XIP as 10.1 release (Build 19209) - however the XIP version shouldn't matter, as we delete it and merge yours into the OS-new.nb instead...
About the same happened to me and after a re-flash of a good nbh I got some very strange things happening. I could not install any cab. Very weird.
I had to format everything.
Anyway the xip is working if slipped into old rom, but that's not much of a news...
I looked into S00 of FLASHDRV.DLL module in order to convert it, but it does not look like usually.
Maybe that dump is not from a hermes device.
Hrrrm - that is possible, however the site said that it was for Hermes devices... Are you looking at it in the OEMDrivers directory or the XIP?
Can we swap out the FLASHDRV.DLL from a working ROM? I'm pretty sure that isn't tied to a certain build?
CRCinAU said:
Hrrrm - that is possible, however the site said that it was for Hermes devices... Are you looking at it in the OEMDrivers directory or the XIP?
Can we swap out the FLASHDRV.DLL from a working ROM? I'm pretty sure that isn't tied to a certain build?
Click to expand...
Click to collapse
I can try to make it work with the XIP from the 19900 version existing on this thread. (actually from there was the xip I uploaded). Could it work? There will be maybe a 409 & 804 conflict?? I have no clue really. Can only try.
I don't believe the XIP is localised, nor are the OEMDrivers. I may be wrong here though. 409 vs 804 should in theory only become an issue when applications that use localisation is involved..
It is definitely not a hermes rom as the kitchen does not accept a hermes payload while other kitchens accept older (different) payloads. Kitchen halts at ImgfsFromNb.
I can not think of something else. I give up on this one.
Hrrrmmm...
What about this:
ftp://user:[email protected]:333/Aikon/Build19900RKXiaoQiao.7z
It weighs in at 145Mb, but it is supposed to be another Hermes 19900 kitchen that I haven't managed to get going either...
The XIP definatly isnt localised at all,
What sort of sizes are you guys getting for the os.nb filesize?
CRCinAU said:
Hrrrmmm...
What about this:
ftp://user:[email protected]:333/Aikon/Build19900RKXiaoQiao.7z
It weighs in at 145Mb, but it is supposed to be another Hermes 19900 kitchen that I haven't managed to get going either...
Click to expand...
Click to collapse
The download speed is obscene. It will finish maybe tomorrow.
Need help porting sys folder..
I've successfully ported XIP to 20757 and now i've been trying to port the sys build folder 20757 and up, from multiple roms, such as the xperia x1 roms, the blackstone roms, and other's from the site.
But all of my attempts has fail, so was hoping someone could tell me what im doing wrong.
First sys attempt i tried was;
How to port a SYS folder
Open your old SYS folder and copy the .VM and WinCENLS_WWE folders into your new SYS folder
Go to your old SYS\Shell and copy shell32.exe and shellres.dll into your new SYS\Shell
found here http://forum.xda-developers.com/showthread.php?t=389772
Second i tired, to port it from a thread on the kaiser forum, http://forum.xda-developers.com/showthread.php?t=437264
and third i tried this following guide from the elf forms, http://forum.xda-developers.com/showthread.php?t=379598
so for short
1. made 1 folder for old sys, and 1 for new system with the build number
2. copy .vm .rom WinCENLS_WWE, shell/shellresand shell/shell32 folder, with my already ported XIP
3. swap out the res folder like 800 and 640 ones for the diamond, (where ever it is needed to port the rom)
4. then ran g'reloc
so yeah finally when i tried all this, form the guide, it doesnt work
What about the easiest way?
Take a look here:
http://forum.xda-developers.com/showthread.php?t=452779
Ervius's tool is to port XIP
To port SYS is the easiest porting Simply run Greloc on old SYS and note all the values. Then run Greloc on new SYS and change the values as per old SYS. No replacement needed, no swapping required
Simple!
ababrekar said:
Ervius's tool is to port XIP
To port SYS is the easiest porting Simply run Greloc on old SYS and note all the values. Then run Greloc on new SYS and change the values as per old SYS. No replacement needed, no swapping required
Simple!
Click to expand...
Click to collapse
I thought that to but every time i tried to port the Blacstone sys and Greloc
the rom doesnt boot, I have tried many times and allways the same result.
havent test for a wile, the xip port I get whit your exellent manual xip port but not the sys, so now I have a rom os 20757 Build 19665
have you tried replacing all except the Metadata folder ?
for your XIP which is the base used 1.93, 1.96, 1.97 ?
I have tried the xiportereex tool but some modules are missing, so I tryied to add it by myself, it boot but sometime touch screen doesn't responde at first tap, very strange, I have also a pb with default ringtone witch is not the one it should be by mxipupdate
hi
thank you for your reply everyone but several attempts trying you methods but none has worked ; ;
UPDATE; i give up trying to port sys build, thnx for you help everyone.
Same problem for me, if I try all these method in order to port the sys 20764 ( blackstone) to me ELF, the phone don't boot :-(
if the problem is running poutlook, please check if you have custsat.dll in your rom.
if removed, poutlook won't run.
This is the sam exact problem i'm running into. I can't just not port the SYS because the XIP i'm using opens the windows in a tiny little corner in the top left hand corner. Has anyone figured out how to actually port the SYS since none of the tutorials seem to work.
Hi All,
Try this:
1. Copy all modules and dsm ONLY from these few folders (BaseApps, Shell, Phone, PhoneRedist and Redist) from new SYS to your old SYS folder. No need copy ***_DPI_*** (images), ***_0409 / ***_0804 (language files) and the rgu because they never change even how high the build number goes
2. Copy gwes.exe from new build OS folder to your OS folder (if you don't want to get small little window on the top left corner)
3. g'reloc
4. Cook
Good luck !
Bxsteez said:
a tiny little corner in the top left hand corner
Click to expand...
Click to collapse
take gwes.exe from a vga rom and replace that... you have same problem I had the sys was from a no vga rom and when I took the gwes from my stock rom it make the trick gwes.exe u find in Os folder
Vic5870 said:
Hi All,
Try this:
1. Copy all modules and dsm ONLY from these few folders (BaseApps, Shell, Phone, PhoneRedist and Redist) from new SYS to your old SYS folder. No need copy ***_DPI_*** (images), ***_0409 / ***_0804 (language files) and the rgu because they never change even how high the build number goes
2. Copy gwes.exe from new build OS folder to your OS folder (if you don't want to get small little window on the top left corner)
3. g'reloc
4. Cook
Good luck !
Click to expand...
Click to collapse
In fact, you can take the rest of the OS folder too, with the exception of the rgu and ossvcs
omaga said:
take gwes.exe from a vga rom and replace that... you have same problem I had the sys was from a no vga rom and when I took the gwes from my stock rom it make the trick gwes.exe u find in Os folder
Click to expand...
Click to collapse
I had this problem when i was porting the Touch HD ROM to the Xperia X1 and thats wvga to wvga. I honestly thought porting the SYS would be the easy part but the SYS is why my phone doesn't boot up it just sits there
Bxsteez said:
I honestly thought porting the SYS would be the easy part but the SYS is why my phone doesn't boot up it just sits there
Click to expand...
Click to collapse
Ye I thought that sys is the easy part I got so many sys port that the rom doesnt boot. Now i get 2 in a row 21109 and 21014 sudden and If I remember right I have allways done the same way
Thats the one that i'm working on now. I'm trying to port the 21109 from the touch pro to the xperia but i can't get it to work. Can u give me any tips?
Bxsteez said:
Thats the one that i'm working on now. I'm trying to port the 21109 from the touch pro to the xperia but i can't get it to work. Can u give me any tips?
Click to expand...
Click to collapse
Maybe you should post in the X-Peria ROM dev. forum!?
I have but as we all know the xperia doesn't get as much attention as to the full blown htc devices. I figure that the porting method should be about the same with the exception of changing some things based on resolution. Am i wrong?
Have you deleted some folders from official HD SYS??
If yes, notice that the rom doesn't boot without SqlCeMobile and SqlCeMobile_Lang_0409 folders. I'm speaking from my experience with HD.
And I remember I've ported these official builds to Toshiba G900 without problems. Then, make attention to these things too.
And control if into your original SYS, you have some different folders in comparison to the new SYS.
Another thing, Ervius xipporterex rev-35, deletes some things from xip, but it works perfect in that way. The only thing you have to notice, is that it deletes WinCENLS_WWE from xip, then you have to add it into SYS folder.
@Bxsteez,
chek your 21109 SYS, and change mxip_system.vol(into Shell), with your original and see if mxipcold_wpc_2.provxml is into Base_DPI_192 folder, if not, copy your original one there. Change MobileCalculator.exe into baseapps folder too.
Just gave this a shot and nothing works again.... I can't even port the XIP and use the standard SYS and get it to boot. I wonder if i'm using a some corrupted build of 21109. Can someone point me in the direction of where to get OS CE 21109 and 21109 build?
Search on ppcgeeks the calkulins kitchen for diamond, then extract the xip from os.nb.payload and use that to port, worked for me with ervius xipporterex-35.
And make those changes into SYS folder, they are needed to boot properly.
I have been working on this new ROM Kitchen project over the last months.
Public beta can be found here:
http://www.darkforcesteam.com/showthread.php?p=3560
Downloading this minute. Is it also for old devices? (Blue Angel?)
Sounds great, thanks for this kitchen
motisu said:
Downloading this minute. Is it also for old devices? (Blue Angel?)
Click to expand...
Click to collapse
Should theoretically work for all HTC devices.
Only have an HTC Diamond to try it myself, but others tested it on Universal, HD, Raphael, ...
Nice to see you back Bepe!, Happy New Year
OMFG
bepe, you've completely outdone yourself this time!!! Checked out the videos, looks amazing!! Congratulations.
Downloaded, will check it out and post results. Thanks!!!
Hmm.it will work on all htc devices.
maybe some older dev cant use,need to test by yourself
really nice Rom Kitchen.
Great jod!!!
Cheers
Monkeybape
i second the post with the video tutorial !! great work and even me is able to build a rom now *lol*
Is removal of unneeded files from XIP supported, bepe??
this look fantastic bepe, as usual
even though I have tested it, I noticed two things:
1. Wouldn't replacing WINCE_NLS in the XIP from a different device, let's say, cause the phone not to boot?
2. What if the device you are porting from has a different resolution, wouldn't you have to change the files in the SYS manually?
other than that, it looks GREAT!
thanks again
chavonbravo said:
Is removal of unneeded files from XIP supported, bepe??
Click to expand...
Click to collapse
yes, it possible to add/remove all files/modules you want. It works the same way as in IMGFS... just delete the file/module from the XIP package or add a new one to an existing or new package.
the Kitchen will not include files that are not needed like boot.rgu, *.rgu, *.dsm to the XIP section, so there is no need to remove them after the XIP partition is build.
mbarvian said:
this look fantastic bepe, as usual
even though I have tested it, I noticed two things:
1. Wouldn't replacing WINCE_NLS in the XIP from a different device, let's say, cause the phone not to boot?
2. What if the device you are porting from has a different resolution, wouldn't you have to change the files in the SYS manually?
other than that, it looks GREAT!
thanks again
Click to expand...
Click to collapse
1. replacing WINCE_NLS is not really a problem, but the size of the .nls file might be.
example:
- you are using a WWE Kitchen with a WWE nls size: 267 KB
- you want to change lang to CHT, the nls size would be 1500 KB
--> this means the size of the xip section would grow very much
--> ROM\os.nb.payload is WWE and would not have enough space for the bigger CHT XIP
--> ImplantXIP.exe should give you an error I think... never tried it...
solution: use the CHT os.nb.payload (just replace the WWE .\ROM\os.nb.payload by the CHS one)
The CHS roms would have more space for XIP, so all would be working fine
2. Using another resolution is not a good idea... most SYS packages are compatible, but there are packages like this:
- Base_DPI_192 - this is for 192 DPI like Diamond, Raphael, HD
- Base_DPI_96 - only for QVGA devices
- base_dpi_192_resh_480_resv_640 - this package tells you the exact resolution it was made for
You could mix two builds, like using only new packages without *_DPI_192 or *_dpi_192_resh_480_resv_640 in the name...
... but not really a good idea, even that many ppl are making that. Consider that there might be resources that might be changed
Would take a look at it, but the forum requires compulsory registration to view.
Please fix your forum.
It tells me I'm missing msvcr71.dll when I try and dump. I noticed that file is other kitchens so I tried to copy it over and it starts the dump but then RecMod.exe stops responding and it asks to close.
I keep getting this error when it comes to running platformbuilder
Code:
This aplication has requested the runtime to terminate it in an unusal way
boo, I wanted to watch the tutorial on your forum again, getting an initflashfiles .dat not where it's supposed to be error. but your forum seems to be down, or under too high traphic right now, is there any way you would think of putting together a short text based info set on everything we need to know to dump and rebuild? if not, no biggie, I am sure I will figure it out, like any great new tool, there is always a learning curve Thanks much for sharing your work with all of us though
Good to see you back bepe!!! I will give this a shot later on today...
outstanding bepe!! I thought your tutorials were excellent too!
thanks bepe
tested your kitchen on my Elfin and it worked well except for implantxip, because i've reduced the size of my XIP partition in template payload, so implantxip gave me error like "no xip section found". i replaced implantxip with msflshtool and it worked fine. no other issues faced in ROM building and porting newer build for my Elfin . although i had to make some adjustments to Dump_200.bat for dumping the ROM.
also, we used buildxip for xip porting before and it had some specific switches like -g, -k and -f useful for enabling different kernel modes, changing fsrampercent etc. i was wondering if same is possible while xip porting with new kitchen or is the best setting chosen automatically?
and, do check your paypal for Transaction ID: 45A49499TS934251W
Hi to all chefs,
I am looking for as much info on rom cooking as possible as to understand the process that is happening,
what i want to know is when the batch file is run this launches other commands could somebody please explain what is happening behind the scenes
when the buildos runs it processes all the files into a temp folder,
now my most important question is,
when building up the registry, what is the order that the files are processed, by dsm filename? package filename?
also when are the mxip_******.provxml files processed (reg esttings added to the registry and in what order
how is the best way to add a custom mxip_****.provxml to garantee my setting don't get changed,
also if there is enough useful answers posted, i will edit this post to make a time-line in post2 to help others new to cooking there own roms,
then infos wanted for timeline are the background into whats happening in each program launched (buildos,nbhtool etc) from pressing the cook batch file through to windows being flashed and autorun kicking in, sdautorun if exists, then the end would be the final reset and windows ready to use,
hope you will make useful answers
many thanks.
Reserved for timeline
timeline
1 cook button pressed
1.1 BuildOS launches
1.2 G'Reloc launches
1.3 NBSplit -kaiser OS.nb
1.4 ImgfsFromNb OS.nb.payload imgfs.bin
1.5 ImgfsFromDump imgfs.bin imgfs-new.bin
1.6ImgfsToNb imgfs-new.bin os.nb.payload os-new.nb.payload
1.7NBMerge -kaiser os-new.nb
1.8 HTCRomTool.bat
1.9 DiamonCustomRUU.exe
1.10 Cleanup.bat
garymeg said:
Hi to all chefs,
I am looking for as much info on rom cooking as possible as to understand the process that is happening,
what i want to know is when the batch file is run this launches other commands could somebody please explain what is happening behind the scenes
when the buildos runs it processes all the files into a temp folder,
now my most important question is,
when building up the registry, what is the order that the files are processed, by dsm filename? package filename?
1. the *buildos*.exe generates logfile with order
2. you can minimize the number of dsm-files/packages by your self.
i.e OEM, Packages and SYS to one dsm/rgu/provxml
also when are the mxip_******.provxml files processed (reg esttings added to the registry and in what order
mxipCOLD at coldboot (first time/only one time)
mxipUPDATE at resets (allways)
how is the best way to add a custom mxip_****.provxml to garantee my setting don't get changed,
"your device will ... in 3 seconds ... 2 seconds"
also if there is enough useful answers posted, i will edit this post to make a time-line in post2 to help others new to cooking there own roms,
these are not usefull answers, but iam to tired for details but i cant write nothing ...
then infos wanted for timeline are the background into whats happening in each program launched (buildos,nbhtool etc) from pressing the cook batch file through to windows being flashed and autorun kicking in, sdautorun if exists, then the end would be the final reset and windows ready to use,
hope you will make useful answers
many thanks.
Click to expand...
Click to collapse
generaly the kitchen/device that you use and/or how much detaild you have cooking-knowns will determines the order.
I Know very little, i can take a rom add packages and rebuild, thats my limit, i want to create this thread so i can better understand what is happening, edit files, make sure my edits dont get changed later during the setup process, I would think this applies to most devices (i have a diamond and also Artemis) the kitchen i use is the modifyed kiaser kitchen as when i was modding artemis i found a simular kitchen for that device and a lot of my packages were reused.
for extracting artemis i use the hypercore-kitchen. but for cooking i changed to ARTEMIS_DEV_v2.1_Build_19199-kitchen. the reason is, that the file-structure in hypercore dismis/damages my brain.
for diamond i use the "kitchen"-kitchen (orig. download filename was kitchen.rar).
ohh, its ringing, so i have end again ...
p.s.
study the system.txt inclusive the batch-files together with the batch-files from "kitchen"-kitchen.
Hello everyone,
here's the wm6.5 rom for asus p835.
last updated: 10-12-09
http://cid-cf1603cd2858a369.skydrive.live.com/browse.aspx/PUBLIC
So far tested everything ok except Garmin XT not working anymore. Cant even start the application. Please let me know if you find otherwise.
btw, as usual, you use this rom at your own risk as you should understand there's always risk when flashing rom to your mobile... blah blah blah..
------------------------------------------------------------------------------------------------------------------------------------
[14-12-09]
I guess most of us p835 users have to use our own effort to build the rom for this phone.
Here i will give you some guide how I did building the ROM. Hopefully we can gather more intelligence to make a nicer ROM for this phone.
first off, I will explain how to properly extract xip/sys from the original ROM. With these only you can modify it's system.
Tools needed: p835abisplit2.exe, osnbtool.exe
1. rename the original ROM you downloaded from asus site. Rename to G5.exe. run command: "p835abisplit2 g5.exe". You will now get a file FLASH.BIN.
2. Now we need to work with FLASH.BIN. Using OSNBTOOL, put in command "osnbtool -sp flash.bin", you will get something just like below:
OS ROM Partition Tool V1.59 By Weisun :> PDAclan.com
Sector size : 0x00000800
Extra data bytes : 0x00000008
OS IMAGE found.
Partitions infomation:
**************************************
Part-0 type: BOOT SECTION image
Part-1 type: XIP RAM Image
Part-2 type: IMGFS file system
Part-3 type: legit DOS partition
**************************************
Found BIN_FILE structure in source file.
Records: 0x0000036D RecordsSize: 0x06E10328
StartAddr: 0x01030200 ---------------->we need this address when we repack flash.bin. Check if yours is the same with this?
flash.bin.Header written.
3. command: "osnbtool -sp flash.bin.BIN.NB0"
4. command: "osnbtool -d flash.bin.BIN.NB0.OS.NB 2 imgfs.bin" --> you'll get imgfs.bin
5. command: "osnbtool -d flash.bin.BIN.NB0.OS.NB 1 xip.bin" --> you'll get xip.bin
6. command: "imgfstodump imgfs.bin" --> with this, you'll get a "imgfs" folder. You'll need to make it into a easy to use package. rename the folder to dump.
7. command: "packagebuilder dump" --> you will see inside dump folder, you have all files packed into different folders. You wont be able to see a single file in dump folder. if you do, probably packagebuilder unable to recognize them or something wrong with the files(i'm not sure what to do then). The most important thing in dump folder are the folders with letters starting with OEMxxxx and .ROM, .VM. These few folders should be retained in the new system. Others are all replaced with new system.
assume you are able to modify everything without question, you are now in the situation where you want to repack a ROM. We will need these files in the same folder: FLASH.BIN.HEADER, flash.bin.BIN.NB0.OS.NB, IMGFS.BIN.
1. You will need to repack imgfs first. using "imgfsfromdump imgfs.bin imgfs-new.bin", you get the new imgfs-new.bin.
2. assuming you already modified xip.bin, it should be in name xip-new.bin. Using "osnbtool -c flash.bin.BIN.NB0.OS.NB 1 xip-new.bin"
3. "osnbtool -c flash.bin.BIN.NB0.OS.NB.NEW 2 imgfs-new.bin", repacking imgfs
4. "osnbtool -extra flash.bin.BIN.NB0.OS.NB.NEW.NEW"
5. "osnbtool -2bin flash.bin.BIN.NB0.OS.NB.NEW.NEW.EXA 0x01030200 -cutheader", remember when we first unpack FLASH.BIN? There's a starting address which we must use here.
6. "copy/b/y flash.bin.Header+flash.bin.BIN.NB0.OS.NB.NEW.NEW.EXA.BIN os-new.nb0"
7. "p835abisplit2 /B G5.EXE" ---> you must have the original ROM G5.exe. Output is a file named "out.exe". This is a USB flash file. For me, I'd prefer a card flashing ABI file. Which I felt safer. For generating ABI file, you will need to download a flashable ABI file, rename to G5.abi and run this command "p835abisplit2 /B G5.ABI". You will get "OUT.ABI". Rename to G5_ALL_WWE.ABI to flash with an SD card.
Btw, all these are not my original works, credits to DA_G for his ROMs and guides, BEPE and others for their great tools, zhaochengw: most of the guides above is from him.
--------------------------------------------------------------------------------------------------
[16-12-09]
SYS modification:
to upgrade a sys, all you need from original ROM is .ROM, .VM and all OEMxxxxx folders. (that's all i know of). All other folders are to be deleted and replaced with folders from new builds. After you work out a complete SYS, use G'reloc to relocate address. I've tried using WMreloc, but everytime i tried doesnt boot. I'm not sure what caused the problem but at least G'reloc worked. There might be some hiccups when using G'reloc, you'll have to google abit on that. If you encountered a problem saying that there's not enough memory on slot0, try remove some of the removable directories such as office or onenote.
Once you successfully relocated, you will have to use BuildOS to pack it back. You might encounter problems like duplicated files, just delete the one not from OEM folders. after you're done, copy the DUMP folder from TEMP directory and use imgfsfromdump(step1 from second part above).
--------------------------------------------------------------------------------------------------
[19-12-09]
I'm not going to cover xip.bin porting, but i'll mention here that you will need to use xipport to manually port xip for this rom. I've tried some kitchen tools but none working. It's the same for sys porting too, you have to manually replace the files and/or change REG. After which you'll use BUILDOS to build it. Other than that, you'll need an OEM sys/xip. I'ved used D_GA's 28002 and found that his package works pretty well. You can find it here.
http://forum.xda-developers.com/showthread.php?t=544445
I'll upload some related tools together so you'll wont have to look everywhere. You can find the upload together with the ROM downloads area.
regards.
blue.
Nice working!
Thx for blue's hard working on this poor handset.
wish ASUS can fix bugs on drivers and also hope guys like u can countinue Cooking better roms!
Thanks Guy! You're the best!
Call Key,Trackball and Volume Key cannot use
blue00mountain said:
So far tested everything ok except Garmin XT not working anymore. Cant even start the application. Please let me know if you find otherwise.
Click to expand...
Click to collapse
I had this issue too. Make sure you recmod all the browsing folders, incl Browsing, Browsingie & Lang folders
Sorry, How to Flash the Rom Use ABI File?
Blade0rz said:
I had this issue too. Make sure you recmod all the browsing folders, incl Browsing, Browsingie & Lang folders
Click to expand...
Click to collapse
i'm a beginner chef, so please tell me what's the purpose of recmod? For my understanding, it is only to make files become module? what else does it do?
blue00mountain said:
i'm a beginner chef, so please tell me what's the purpose of recmod? For my understanding, it is only to make files become module? what else does it do?
Click to expand...
Click to collapse
As I understand it, not only does it make a module into a file, it makes that file use the memory available in SLOT 0 in the ROM. Modules use SLOT 1 memory be default, so I think the browsing folders have issues accessing memory across the two slots
Have a read at Da_G's thread & the Native Kernel post - he explains it a lot better than I do
Good job on the ROM!
Blade0rz said:
As I understand it, not only does it make a module into a file, it makes that file use the memory available in SLOT 0 in the ROM. Modules use SLOT 1 memory be default, so I think the browsing folders have issues accessing memory across the two slots
Have a read at Da_G's thread & the Native Kernel post - he explains it a lot better than I do
Good job on the ROM!
Click to expand...
Click to collapse
ok, now the browser problem and garmin problem solved. although not really sure what i did that made it worked. Now i'm facing another problem, asus utilities, i.e. autorotate can only work once, and then it stoped working the next time ie starts. Autocleaner does not work at all. Any ideas?
Is there anyone testing my rom anyway?
regards,
B
I have test your ROM.It is very good.Sometimes any programs can be down.
Hi Blue00mountain
Thanks for your hard work, downloading.... hunger for P835 rom,
Read form other thread and noted that WM6.5.3 build 28002 was not as stable and fast as 28003 or later, would you consider to move on to newer version, thanks so much in advance.
blue00mountain said:
Hello everyone,
here's the wm6.5 rom for asus p835.
last updated: 10-12-09
http://cid-cf1603cd2858a369.skydrive.live.com/browse.aspx/PUBLIC
So far tested everything ok except Garmin XT not working anymore. Cant even start the application. Please let me know if you find otherwise.
btw, as usual, you use this rom at your own risk as you should understand there's always risk when flashing rom to your mobile... blah blah blah..
regards.
blue.
Click to expand...
Click to collapse
Thanks, that's great. BTW, I am start reading about porting XIP, would you mind telling me how to port XIP and how to test the ROM before hardware flashing the ROM?
leofong2022 said:
Thanks, that's great. BTW, I am start reading about porting XIP, would you mind telling me how to port XIP and how to test the ROM before hardware flashing the ROM?
Click to expand...
Click to collapse
There's quite some information on the web regarding xip porting. I felt that XIP is quite straight forward, not much problem. The problem I felt so far lies in SYS porting, and a chance to get a good OEM unmodified rom.
And there isnt any emulator to test rom. YOU WILL NEED TO FLASH INTO PHONE TO TRY IT OUT. However, this phone has a nice bootloader, which it checks for rom integrity before flashing. if you rom is incorrect, it doesnt allow to flash at all. Basically it is quite safe unless you messed something other than xip sys itself.
Thx blue!
anyway,the solution of unpack and repack P835 ROM may have another way:
follow steps are from hdubli,and hope can help everyone to Cooking ROMs!
---------------------------------------------
@ECHO off
ECHO Preparation
del flash.bin
del os-new.nb0
del flash.bin.bin.nb0.bin
del G5_ALL_WWE.abi
pause
TOOLS\p835abisplit2 g5.abi
ren os.nb0 flash.bin
TOOLS\osnbtool -sp flash.bin
TOOLS\nbsplit -data 2048 -extra 8 flash.bin.bin.nb0
copy flash.bin.bin.nb0.payload ROM\flash.bin.bin.nb0.payload
pause
ECHO Building OS
pause
TOOLS\BuildOS.exe
ECHO Realocating Modules
pause
TOOLS\WMReloc -gtemp\dump -llog.txt
ECHO Next: Build the rom...
pause
copy imgfs.bin temp\imgfs.bin
cd temp
..\TOOLS\ImgfsFromDump imgfs.bin imgfs-new.bin
cd..
copy temp\imgfs-new.bin
pause
TOOLS\insert -i imgfs-new.bin -o flash.bin.bin.nb0.payload -d 0x00460000 -s 0x5fdfff0
pause
TOOLS\insert -i 21812.bin -o flash.bin.bin.nb0.payload -d 0x00180000
pause
TOOLS\nbmerge -data 2048 -extra 8 flash.bin.bin.nb0 -conservative
pause
TOOLS\osnbtool -2bin flash.bin.bin.nb0 0x1030200 -cutheader
pause
copy /b/y flash.bin.header+flash.bin.bin.nb0.bin os-new.nb0
pause
TOOLS\cvrtbin os-new.nb0
ECHO Check the Out Put
pause
TOOLS\p835abisplit2 /b g5.abi
ren out.abi G5_ALL_WWE.abi
pause
del flash.bin.bin.nb0
del flash.bin.bin.nb0.payload
del flash.bin.header
del flash.bin.bin.nb0.extra
del imgfs-new.bin
pause
---------------------------------
Hi Blue,
Thanks for your details cooking step, I've done all the way to the dump folder, and after repack the dump folder using packagebuilder, I got a "info.txt" file and a "sys" folder, I leave everything untouch and try to repack imgfs, however I always get error as below after runing the command imgfsfromdump:
>imgfsfromdump imgfs.bin imgfs-new.bin
ImgfsFromDump 2.1rc2
Using compression type 'XPR'!
Sector size is 0x800
Processing "info.txt" as file
Processing "SYS" as module
then error message pop up "ImgfsFromDump.exe has stopped working"
Have you ever got this error? Did I missing something here, please help, thanks.
lizard999 said:
Hi Blue,
Thanks for your details cooking step, I've done all the way to the dump folder, and after repack the dump folder using packagebuilder, I got a "info.txt" file and a "sys" folder, I leave everything untouch and try to repack imgfs, however I always get error as below after runing the command imgfsfromdump:
>imgfsfromdump imgfs.bin imgfs-new.bin
ImgfsFromDump 2.1rc2
Using compression type 'XPR'!
Sector size is 0x800
Processing "info.txt" as file
Processing "SYS" as module
then error message pop up "ImgfsFromDump.exe has stopped working"
Have you ever got this error? Did I missing something here, please help, thanks.
Click to expand...
Click to collapse
i found there's some problems when u use the imgfsfromdump tool to make imgfs-new.bin
imgfsfromdump can't proceed the SYS folder,it can only deal with original "DUMP" folder
that means,when u dumped out the "DUMP" folder and use pkgtool(or packagebuilder) proceed it into models(SYS、OEM...ETC),u have to use BuildOS.exe rebuild all the files in SYS OEM.the result of BuildOS's rebuild just like the original "DUMP" folder.then u can use imgfsfromdump to make a imgfs-new.bin
Sorry about my poor English...
well,i still try to show u the way i repack imgfs.bin wihtout change anything.
1st, get the imgfs.bin
2nd,use imgfstodump and get the "dump" folder
3rd,use imgfsfromdmp directly,i get the imgfs-new.bin
blue00mountain said:
There's quite some information on the web regarding xip porting. I felt that XIP is quite straight forward, not much problem. The problem I felt so far lies in SYS porting, and a chance to get a good OEM unmodified rom.
And there isnt any emulator to test rom. YOU WILL NEED TO FLASH INTO PHONE TO TRY IT OUT. However, this phone has a nice bootloader, which it checks for rom integrity before flashing. if you rom is incorrect, it doesnt allow to flash at all. Basically it is quite safe unless you messed something other than xip sys itself.
Click to expand...
Click to collapse
ic, but i find that the xip size should be ~3200kb, is it just omit it during compling the xip?
In addition, do you mean it is just simply that just using Da_G's build with Da_G's MSXIPKernel + initflashfiles.dat and original P835 OEMXIPKERNEL is ok?
Sorry for my question because I know less on the OS complie, thanks
leofong2022 said:
ic, but i find that the xip size should be ~3200kb, is it just omit it during compling the xip?
In addition, do you mean it is just simply that just using Da_G's build with Da_G's MSXIPKernel + initflashfiles.dat and original P835 OEMXIPKERNEL is ok?
Sorry for my question because I know less on the OS complie, thanks
Click to expand...
Click to collapse
i don't think the XIP size should be 3200kb,anyway,in the Traditional Chinese version Rom,the size of XIP is more than 4200kb.
based on my experience, you dont need to have an exact same size for xip.bin. not sure if it will cause any problem but It will start anyway.
regarding your repacking dump question, the proper sequence i think is:
imgfstodump-->packagebuilder-->greloc-->buildos-->imgfsfromdump = imgfs-new.bin
blue00mountain said:
based on my experience, you dont need to have an exact same size for xip.bin. not sure if it will cause any problem but It will start anyway.
regarding your repacking dump question, the proper sequence i think is:
imgfstodump-->packagebuilder-->greloc-->buildos-->imgfsfromdump = imgfs-new.bin
Click to expand...
Click to collapse
Since I saw the p835abisplit2 creator starkwong said that (若要修改 XIP，請確保重新嵌入 nb0 前的 XIP 大小是跟原來的相同，否則刷機後會開機失敗)
-> if modifying XIP, please ensure the re-embedding nb0 XIP size is same as original XIP size, otherwise it may cause turn-on (mobile) failure after flashing.
If it is ok, that's great