Related
Guys, before i brick my tytn i need to know whether the cooking method i'm using is correct. I'm using:
RUU-signed.nbh ---(*NBHExtract)---> OS.nb ---(NBSplit)---> OS.nb.payload -->--(ImgfsFromNb)---> imgfs.bin ---(ImgfsToDump)---> 'dump' directory, delete some files, add some files (with dsm and rgu if needed), edit initflash, edit default.hv and reverse the proces to build me the rom. The thing that wonders me if i'm doing it correct is that i'm not using the package tool to build the oem and sys dir. I'm just doing the work on the dump dir and rebuild from there. Would this be correct ?
From the dump, use bepe's package tool and convert it into SYS and OEM. Then you can add packages with .rgu, .dsm and initflashfiles.txt
Or..yeah ...that can work too. It's the old way , but you wouldn't need to add rgu's and dsm's since you make your changes right in the default.hv and user.hv, and of course, edit the initflashfiles.dat
can work or will work ... it's a big difference
btw. if i convert to oem and sys, reversing the proces starting with ImgfsFromDump errors out on me with processing OEM as module ...
Post a descriptive title for your threads.
Man, every time I see a thread titled "newbie question" or "please help" or some such nonsense it makes me wonder what these people are thinking. This thread for example, would be better titled something that indicated what you want assistance with, then if the right people see it they can respond instead of ignore it because it didn't blip their radar.
Hi all, I've a question, I readed in a lot of 3ds that to reallocate modules into xip section with xipport (the last by bepe) someone use also m'reloc....
I cannot find into xipport.exe imageinfo.bin references, apart the ones that creates imageinfo.bin into \out\modules\modulename!
now, my question is:
why they try to use m'reloc if xipport doesn't need it???
xipport.exe works on modules by imageinfo.txt, with D=, V= and R= values
if someone can explain better this step, becouse for me use m'reloc is useless.
Why not ?
ervius said:
Hi all, I've a question, I readed in a lot of 3ds that to reallocate modules into xip section with xipport (the last by bepe) someone use also m'reloc....
I cannot find into xipport.exe imageinfo.bin references, apart the ones that creates imageinfo.bin into \out\modules\modulename!
now, my question is:
why they try to use m'reloc if xipport doesn't need it???
xipport.exe works on modules by imageinfo.txt, with D=, V= and R= values
if someone can explain better this step, because for me use m'reloc is useless.
Click to expand...
Click to collapse
ervius, you doesn't use m'reloc when you port xip ?
can you tell me which XIPPort is the last one because Bepe doesn't make release number...
The procedure you're using is :
- Dump the xip.bin
- Make Pkgs
- Replace the new modules
- Undo
- Realloc P
- Build xip_out.bin
Thanks for your help
ervius said:
Hi all, I've a question, I readed in a lot of 3ds that to reallocate modules into xip section with xipport (the last by bepe) someone use also m'reloc....
I cannot find into xipport.exe imageinfo.bin references, apart the ones that creates imageinfo.bin into \out\modules\modulename!
now, my question is:
why they try to use m'reloc if xipport doesn't need it???
xipport.exe works on modules by imageinfo.txt, with D=, V= and R= values
if someone can explain better this step, becouse for me use m'reloc is useless.
Click to expand...
Click to collapse
m'reloc isnt useless. Traditionally m'reloc is used when the 'realloc P' and 'write map' buttons of Bepes XIPPort.exe causes the program to crash. In other words when two XIP modules occupy the same address and produce '!' characters throughout your MAP.txt.
peter petrelli said:
m'reloc isnt useless. Traditionally m'reloc is used when the 'realloc P' and 'write map' buttons of Bepes XIPPort.exe causes the program to crash. In other words when two XIP modules occupy the same address and produce '!' characters throughout your MAP.txt.
Click to expand...
Click to collapse
you need m'reloc for nothing.
all xipport process is based on imageinfo.txt files, while m'reloc changes module values on imageinfo.bin (and xipport ignore thatr file in module, in realloc P and in write Map.txt), bwt, I use XIPAddrTools, joined to xipport, and it use m'reloc, but with m'reloc, this utility:"XIPAddrTools", changes values on imageinfo.txt, it's the real way to port xip, playing around imageinfo.txt.
and to confirm all I hex edited xipport.exe, and it only writes imageinfo.bin, while dump xip.bin, never read imageinfo.bin to check values inside., try you also to hexedit it and change imageinfo.bin inside into:"omageinfo.bin", dump xip.bin, and inside all modules, you 'll find "omageinfo.bin", delete all omageinfo.bin, realloc P, write map, write new xip.bin, insert into payload and flash rom, it starts normally...., xipport not need imageinfo.bin, and doesn't use them.
ervius said:
.. xipport not need imageinfo.bin, and doesn't use them.
Click to expand...
Click to collapse
modifed xipport can make imgainfo.bin and u can manually extract it from xip.bin (it's not so complicated)
m'relock is usefull when u have to move VA of module coz of !!!!!!!!! in map.txt
mun_rus said:
modifed xipport can make imgainfo.bin and u can manually extract it from xip.bin (it's not so complicated)
m'relock is usefull when u have to move VA of module coz of !!!!!!!!! in map.txt
Click to expand...
Click to collapse
for me is useless, becouse, I don't know whatr kind of xipport you use, the one that I use, only create imageinfo.bin for compatibility with other utils, but created imageinfo.bin in modules, xipport ignores them until xip_out is created.
ervius said:
for me is useless, becouse, I don't know whatr kind of xipport you use, the one that I use, only create imageinfo.bin for compatibility with other utils, but created imageinfo.bin in modules, xipport ignores them until xip_out is created.
Click to expand...
Click to collapse
Can you share your XIPPort release please ervius ?
MickyMax said:
Can you share your XIPPort release please ervius ?
Click to expand...
Click to collapse
is not mine, is xipport that you also use, only I told that it create files imageinfo.bin, but never it use them, I checked all operations, an dthe imageinfo.bin files remain invariates, after: coredll.dll porting from xip to other ones...., only imageinfo.txt chenge values.
ervius said:
is not mine, is xipport that you also use, only I told that it create files imageinfo.bin, but never it use them, I checked all operations, an dthe imageinfo.bin files remain invariates, after: coredll.dll porting from xip to other ones...., only imageinfo.txt chenge values.
Click to expand...
Click to collapse
Excuse me. I would like to say : can you upload the release you use because we can found many builds in the forum but they seem the same... ?
MickyMax said:
Excuse me. I would like to say : can you upload the release you use because we can found many builds in the forum but they seem the same... ?
Click to expand...
Click to collapse
bo problem, I use this release and xiptools to realloc better all modules into xip...
bye!
Big thanks ervius !
ervius said:
try you also to hexedit it and change imageinfo.bin inside into:"omageinfo.bin", dump xip.bin, and inside all modules, you 'll find "omageinfo.bin", delete all omageinfo.bin
Click to expand...
Click to collapse
Hey ervius, you were right about this I did it and have now deleted all omageinfo.bin files from all modules. But now may I ask how to as you said "I use XIPAddrTools, joined to xipport, and it use m'reloc, but with m'reloc, this utility:"XIPAddrTools", changes values on imageinfo.txt, it's the real way to port xip, playing around imageinfo.txt". Please explain little I will do rest thanks.
tjkhattak61 said:
Hey ervius, you were right about this I did it and have now deleted all omageinfo.bin files from all modules. But now may I ask how to as you said "I use XIPAddrTools, joined to xipport, and it use m'reloc, but with m'reloc, this utility:"XIPAddrTools", changes values on imageinfo.txt, it's the real way to port xip, playing around imageinfo.txt". Please explain little I will do rest thanks.
Click to expand...
Click to collapse
you have to use xiptools with imageinfo.bin...
after, when finish, before realloc P and build Map, and build xip_out.bin, delete all imageinfo.bin, xip_out.bin will be created successfull, like all imageinfo.bin were inside all modules...
P.S.: is bit difficult use the xip_tools, but when you understood how it works, is easiest port xip... thanks to the author...
Hi all, i have complety translated, .rgu / .dsm / .bmp / dpi 96 to 192 / 0409 to 0406.
from 20924.
But, when i cook it, and flash my phone, it dosen't book. I can see the version, but i can't not come to wm6 startscreen.
Do some1 know what it could be ?
Could some1 please look at my files maybe :/?
http://rapidshare.com/files/161467646/sys.rar
Bump, no one want to look in it and help me ??
Search for and download a tool called G'reloc.
A common issue with ported OS builds is that they fail to boot due to improperly coded/placed files. G'reloc will fix this for you. Just run it right before cooking, and then once compiled and flashed, your ROM should boot fine.
*You will need to find the correct codes for G'reloc and a Diamond ROM. I have only used this tool on the Kaiser, so I cannot tell you what they are.
NotATreoFan said:
Search for and download a tool called G'reloc.
A common issue with ported OS builds is that they fail to boot due to improperly coded/placed files. G'reloc will fix this for you. Just run it right before cooking, and then once compiled and flashed, your ROM should boot fine.
*You will need to find the correct codes for G'reloc and a Diamond ROM. I have only used this tool on the Kaiser, so I cannot tell you what they are.
Click to expand...
Click to collapse
As I can see, my package builder+buildos run it before it is done.
But anyway, could allways try it ), what shall i put in ? Some1 knows it ?
danny_and_2 said:
As I can see, my package builder+buildos run it before it is done.
But anyway, could allways try it ), what shall i put in ? Some1 knows it ?
Click to expand...
Click to collapse
I tried using a newer BuildOS for the Kaiser that included G'reloc, and it never worked properly. I would run G'reloc on it's own, and then uncheck the box to run it as part of BuildOS.
If those values are auto filled in for you, then give it a shot with them. Worst case, the phone still doesn't boot.
NotATreoFan said:
I tried using a newer BuildOS for the Kaiser that included G'reloc, and it never worked properly. I would run G'reloc on it's own, and then uncheck the box to run it as part of BuildOS.
If those values are auto filled in for you, then give it a shot with them. Worst case, the phone still doesn't boot.
Click to expand...
Click to collapse
Yes they just came automatic, so. Yes i will try that one, will report back if it dosen't
--- Edit ---
I couldn't i get an I/O error 105. ? Some1 knows what this it ?
--
Run-time error 105: File not open for output.
This error occurs if you try to use standard input and output functions
like Readln and Writeln without the Uses WinCRT; statement.
To correct this error, add Uses WinCRT; to your program.
How exactly did you translate the 96.DPI files?
Safe yourself the headaches and use the Diamond 1.96 as a base.
That would give you all the SYS 192 dpi files you need.
Are you making the ROM true 0406?
Or just translating or renaming the 0409.mui files?
Noonski said:
How exactly did you translate the 96.DPI files?
Click to expand...
Click to collapse
I have copyed the files from the diamond (192) to it.
Noonski said:
Safe yourself the headaches and use the Diamond 1.96 as a base.
That would give you all the SYS 192 dpi files you need.
Click to expand...
Click to collapse
I also would, but it ain't released on danish
Noonski said:
Are you making the ROM true 0406?
Or just translating or renaming the 0409.mui files?
Click to expand...
Click to collapse
I have copied the danish 0406.mui files, and changed it in every .rgu and .dsm file.
Bump, bump, bump.
Must be some1 out there, there can help me find my mistake ;/
danny_and_2 said:
Must be some1 out there, there can help me find my mistake ;/
Click to expand...
Click to collapse
HI
For port this os build i've made this:
first try to port only the xip
Delete folder from your old working kitchen:
MSXIPKernel
MSXIPKernelLTK
AND OEMXIPKernel if exist
Delete your old OS.NB in ROM folder of your kitchen
Now you need to Extract OS.NB From a diamond ROM 20924 protected or not !
(My rom for exemple)
take the 20924 OS.NB in your ROM folder
then just cook with your old sys and oem folder without the folder mentioned on top. flash & verify xip version.
if this work ,change your sys with the 20924 you have
but keep some files from your old working sys
if i have a good memory i've keep this:
.ROM folder
.VM folder
.Metadata folder
.hd.dll folder
.osaxst0.dll folder
.gwes.exe folder
possible some other files...
if you have Greloc error replace files mentioned in error
try this.
ask if you need help
xboxmod said:
HI
For port this os build i've made this:
first try to port only the xip
Delete folder from your old working kitchen:
MSXIPKernel
MSXIPKernelLTK
AND OEMXIPKernel if exist
Delete your old OS.NB in ROM folder of your kitchen
Now you need to Extract OS.NB From a diamond ROM 20924 protected or not !
(My rom for exemple)
take the 20924 OS.NB in your ROM folder
then just cook with your old sys and oem folder without the folder mentioned on top. flash & verify xip version.
if this work ,change your sys with the 20924 you have
but keep some files from your old working sys
if i have a good memory i've keep this:
.ROM folder
.VM folder
.Metadata folder
.hd.dll folder
.osaxst0.dll folder
.gwes.exe folder
possible some other files...
if you have Greloc error replace files mentioned in error
try this.
ask if you need help
Click to expand...
Click to collapse
Hi there.
Thanks for you guide, I'll try it right away.
And I will say if I run into a problem.
xboxmod said:
HI
For port this os build i've made this:
first try to port only the xip
Delete folder from your old working kitchen:
MSXIPKernel
MSXIPKernelLTK
AND OEMXIPKernel if exist
Click to expand...
Click to collapse
They aren't in my kitchen with this rom. Don't know why.
xboxmod said:
Delete your old OS.NB in ROM folder of your kitchen
Now you need to Extract OS.NB From a diamond ROM 20924 protected or not !
(My rom for exemple)
take the 20924 OS.NB in your ROM folder
then just cook with your old sys and oem folder without the folder mentioned on top. flash & verify xip version.
Click to expand...
Click to collapse
It boot, and it works. Haven't looked so much on the rom, just verify'ed the xip version.
xboxmod said:
if this work ,change your sys with the 20924 you have
but keep some files from your old working sys
if i have a good memory i've keep this:
.ROM folder
.VM folder
.Metadata folder
.hd.dll folder
.osaxst0.dll folder
.gwes.exe folder
possible some other files...
Click to expand...
Click to collapse
I have tried what you said, but the mobile just won't boot, and i don't know why ! /:
I think i need some more files?
xboxmod said:
if you have Greloc error replace files mentioned in error
Click to expand...
Click to collapse
I don't have that.
have a look here :
http://forum.xda-developers.com:80/showthread.php?t=379598
TekTonik said:
have a look here :
http://forum.xda-developers.com:80/showthread.php?t=379598
Click to expand...
Click to collapse
Hi there, trust me. I have looked the thread many times ..
Anyway, i got an update.
I have get the phone to boot, with the orginal OS & OSFILES.. Now i just need to find what files i need to have, to get it boot..
But i still got a bug, when it boot, touchflo3d won't start, it just skips. ?
The problem you are facing might be (99%) because of improper XIP porting. Just for suggestion, go through my XIP porting guide (in my signature) and try again with a working 20924 XIP (if you cant find one then I'll up the xip.bin from which I ported and am using)
Using original OS folder would not qualify as SYS porting If you check the SYS build no, you will see the original no and not the ported build
ababrekar said:
The problem you are facing might be (99%) because of improper XIP porting. Just for suggestion, go through my XIP porting guide (in my signature) and try again with a working 20924 XIP (if you cant find one then I'll up the xip.bin from which I ported and am using)
Click to expand...
Click to collapse
Hi there.
I finally got it to work (more or less), someone, know the files i have to keep in the shell ?, it wont lunch flo3d. :S ?
Some1 know why ?
ababrekar said:
Using original OS folder would not qualify as SYS porting If you check the SYS build no, you will see the original no and not the ported build
Click to expand...
Click to collapse
But i needed to find out, witch folder there was stopping me from booting, and that was my answer , now i just need to find out what files i have to keep, and there are only 587 files..
I will report back soon
anything new about an issue, I try to port build 20757 from BlackStone and I'm facing the same problem too : replacing SYS only doesn't boot
Hi guys,
I decided to open a blog which explains how to cook roms for the i780. There are very few chefs, and cooking is a really hard science to learn without help! So, I decided that I take the time and write posts so that everyone could learn the process in a methodical manner and cook roms in the future!
I'd slowly write posts explaining each step of the process in detail, so that we can have more people learning how to cook and make the i780 community more happening
Head over to this URL to check out the first few posts -
http://i780romdev.blogspot.com
Update:
Attached core kitchen tools that you'll need to use! Enjoy!
cheers
San
I never was a fan of this forum, not sure why, maybe because I use a ASUS P527 and there are not proper instructions on how to create a custom ROM, I appreciate your taking the initiative
I think its good fun to try and figure out things on your own
Non-HTC devices do have a very small fan base unfortunately....and ironically, HTC makes the crappiest devices imo (highly crash prone, buggy, lousy drivers, useless qualcomm processor)!
You can apply the same tools and techniques even to cook asus roms....its not all that different
cheers
wooooooow thanks a lot buddy finally we have it also !!!
when will u release part 3? and also can u give the links of programs? like pkgtools_? coz i tried to download it from somewhere else and it had virus
benveq said:
when will u release part 3? and also can u give the links of programs? like pkgtools_? coz i tried to download it from somewhere else and it had virus
Click to expand...
Click to collapse
hi m8!
i'll try and upload the set of tools shortly. You can get it in any of the kitchens posted for the i780 here. I'll however consolidate them and add it in this post as an attachment!
Part 3 - very soon
cheers!
You guy thanks for sharing your experience at cook ROMS,I whink I need this for my SmartPhone.
Hey guys, just dropped the next part of the series on the blog. Check out http://i780romdev.blogspot.com
Of course, the same theory, tools and understanding goes to cook for any other device too
cheers
kitchen tools attached in the first post.
enjoy
dreamtheater39 said:
Hey guys, just dropped the next part of the series on the blog. Check out http://i780romdev.blogspot.com
Of course, the same theory, tools and understanding goes to cook for any other device too
cheers
Click to expand...
Click to collapse
yeah, now i am reading part 3 and u really teach very well! i think i will cook my own room soon with ur help i wanna ask a question if i dont want ms office and internet explorer in my rom which folders should i delete? i wanna add different office program
benveq said:
yeah, now i am reading part 3 and u really teach very well! i think i will cook my own room soon with ur help i wanna ask a question if i dont want ms office and internet explorer in my rom which folders should i delete? i wanna add different office program
Click to expand...
Click to collapse
To remove a package, you can get rid of the corresponding folders in your SYS folder. But its not recommended that you knock off office/ie as they might be referenced within other apps. You can always take it off, build a rom and see if everything works fine
For example, to remove IE, just delete your Browsing, Browsing_DPI_xx and Browsing_Lang_XXXX, BROWSINGCORE, browsingie, browsingie_LANG_XXXX folders. That should get rid of IE for you! Then you need to recreate your bin!
cheers
thanks a lot for kitchen tools and ur explanations! i read ur blog all the time great work!!
The next post is up
cheers
dreamtheater39 said:
The next post is up
cheers
Click to expand...
Click to collapse
yes i read it, and u r teaching with examples it is great
i have two problems while i am using ervius pkgtools
1. when i open dumo folder it shows
[Missing Manifests]
(Maybe):\ROM\XIP\45116509-e364-4775-9098-c25f0b1fbac2.dsm
(Maybe):\ROM\XIP\d92a4f0a-378a-4482-8fd3-bd127a05e4de.dsm
(Maybe):\ROM\XIP\723fb954-d931-4348-b672-82a188e587b5.dsm
(Maybe):\ROM\XIP\1a22bb67-d4c4-7bb4-c5d2-75cb3a85c45b.dsm
(Maybe):\ROM\XIP\449da4ef-e9c1-5cb4-2ec5-fb9b4c27a865.dsm
are these important dsm files?
2. when i press build packages it gives this error:
not found: select .os file to extract XIP
and i extract xip file using osbntool as xip.bin
any solutions for both of these?
benveq said:
i have two problems while i am using ervius pkgtools
1. when i open dumo folder it shows
[Missing Manifests]
(Maybe):\ROM\XIP\45116509-e364-4775-9098-c25f0b1fbac2.dsm
(Maybe):\ROM\XIP\d92a4f0a-378a-4482-8fd3-bd127a05e4de.dsm
(Maybe):\ROM\XIP\723fb954-d931-4348-b672-82a188e587b5.dsm
(Maybe):\ROM\XIP\1a22bb67-d4c4-7bb4-c5d2-75cb3a85c45b.dsm
(Maybe):\ROM\XIP\449da4ef-e9c1-5cb4-2ec5-fb9b4c27a865.dsm
are these important dsm files?
Click to expand...
Click to collapse
This is not important....ignore them, its normal
benveq said:
2. when i press build packages it gives this error:
not found: select .os file to extract XIP
and i extract xip file using osbntool as xip.bin
any solutions for both of these?
Click to expand...
Click to collapse
When you start, it asks if you would like to run build xip.bat.....just hit NO for that....
trojan reported in the attachment
Win32/TrojanDownloader.Zlob.NBP
false alarm?
well last night i finished my own wm6.1 build 20270 128dpi pdxib1 according to your guide i wanna tell what i did to complete it ;
1.i exctracted my rom using i780 kitchen and i got dump folder and i also added some extra tools like ervius buildos,osnbtool etc...then i used pkgbuildos to seperate folders into oem and sys
2. i used oem part from krizky82's kitchen and i add some extra packages using ervius package creator 2.7 and add them with oem_blahblah to oem folder.
3. i deleted windows live and msn messenger from sys folder and copied netcf 3.5 and flashlite v3.1 from krizky82 kitchen. i also used his initflash and rgu file coz i had same structure almost(oem totally same and sys programs also)
4.i looked at both efn's kitchen and krizky82 kitchen and i saw that they have this structure oem,sys and rom and in rom there is xip folder. when i looked at inside xip folder i saw that there is only coredll.dll folder and others are dsm rgu and boot files so my next step
5. i used osbn tool to exract xip.bin and after i got that xipkitchen_beta6 and i choosed the same donor and original and after extracting i got original xip files and i ordered in same structure like efn's kitchen
6.then i used pgkbuildos and let the process starti had some dsm duplicate errors and i delete duplicated ones and later i didnt start xip extract bat and flashable bin bat so after process again i had temp/dump folder
7. during buildos there wasnt any error and i was happy about it
8. using inputTXTFileMaker ( thanks to u dreamtheather93) i got input text and after that using these commands;
mgfsfromdump imgfs_raw_data.bin new_imgfs.bin
del imgfs_raw_data.bin
ren new_imgfs.bin imgfs_raw_data.bin
make_imgfs i780.nb0.payload.body -nosplit
merge i780.nb0.payload.header i780.nb0.payload.body i780.nb0.payload
nbmerge -data 2048 -extra 8 i780.nb0 -conservative
and conv3 input.txt > conv3_output.txt
ren i780.nb0.b000ff !!i780_flashable_bin.bin
i got my flashable bin file yupiiiii i controlled the size of flashable bin and it is 86.2 mb and the size of dump folder almost 125 mb i hope it is ok
now i will flash my phone but is there any possibility that my phone can be bricked ?
thanks a lot for ur guide again!!!
note: i already used i780.bin as 12mb page pool size i did it before kitchen using osbn tool
good job m8
You cant really brick your i780 because of this I've done way crazier stuff....like trying out omnia's xip, drivers of omnia on i780....and nothing's given way
However, i'm hoping you've ported your XIP accurately, and i'm unsure how've you've built your SYS folder.
but, go ahead and flash and see if it boots nothing to be paranoid if it doesnt boot/hangs at startup/throws an error and fails etc. etc. If any of this happens, then we could troubleshoot it together
cheers & good luck
Great job!
Nice start San!
Not even some days left from your first successful cooking and you already best gid on it!
Keep on do it. And we wait for new mods for our best touchphone!
I think now anyone is able to break Eagles wings =P
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