Related
this is rom for new gene ie ht8xxxxx
nothing new just port xip sys for new gene
original rom
here is kitchen only work for new gene
part1 part2
extract all file in same folder
Thank you for the same. Just for the sake of curiosity, how much RAM is available free, on startup, in this ROM?
Hey Ankit, you did it yourself? have you found out the kitchen?
After reading the original thread, i guess there are many unsolved issues with this ROM. Calculator doesn't works, calender gives problem, powerpoint gives some certificate error, No java etc. And i think this also does not include Windows Live.
So i dont think its worth an upgrade. This ROM needs some serious tweaking before i can use it. I haven't installed this ROM but i got all this conclusion from the original thread. Is anybody's experience better with this ROM?
dheerajk27 said:
Thank you for the same. Just for the sake of curiosity, how much RAM is available free, on startup, in this ROM?
Click to expand...
Click to collapse
According to the author, you'll have about 29 MB. Haven't tested yet.
krazy_about_technology said:
Hey Ankit, you did it yourself? have you found out the kitchen?
After reading the original thread, i guess there are many unsolved issues with this ROM. Calculator doesn't works, calender gives problem, powerpoint gives some certificate error, No java etc. And i think this also does not include Windows Live.
So i dont think its worth an upgrade. This ROM needs some serious tweaking before i can use it. I haven't installed this ROM but i got all this conclusion from the original thread. Is anybody's experience better with this ROM?
Click to expand...
Click to collapse
yes i did it myself
i port xip sys first then use Ramersonw's Kitchen (some modification required )
i will upload kitchen tonight so u modify it
because my exam is there i not be able to Cook rom
can u post some screen shots plzzz..if u hav any
thnx
@ankit360: I would really appreciate it buddy if you share with me the details of the process of XIP porting you gone through. I want to learn the whole process as its quiet an important information to cook a ROM successfully. After knowing all this, i would be able to create ROMs and share them with our friends here.
Its really great man! you learned the process so quickly. Hats off to you!
Hey Ankit,
I tried this ROM. Its clean and ultra fast and very little problems. I am sure if they are ironed out, this could be an ultimate ROM for Gene. i have written about the problems in my previous post. In addition to those here is another one.
I tried installing windows live on this rom too but it didn't worked. Since this is a quiet clean ROM with no Windows Live in ROM, there is no possibility of any conflict. I think the problem is related to some certificates.
I examined my original WM 6 ROM and found that All the ROMs in this forum contains all the other certificates except these two from HTC on the top of the list, see the attached files.
I think this could be the cause of all the Windows Live problems as may be since these certificates are not present, windows live is unable to communicate with the server over an encrypted ssl connection.
What do you think?
I will try to extract these out of the ROM. You try yourself too and PM me if there is any success.
can u list out all bug so i will try to fix it
Just trying out your ROM, its lightning fast!
Thanks for the ROM
60 MB free after restoration of around 300 contacts! Wow, Gr8 Word
@ankit360: OK, here is the list of bugs:
1. Calculator is not working. Reports a missing file "\windows\spbcalc_p.gif".
2. Calender not working.
3. Java runtime is not included (if you correct this error and insert a java runtime, use the latest JBed version, it is the only runtime that can run opera mini fullscreen)
4. Powerpoint shortcut not working. It needs a change in registry. If you click the shortcut it will say some certificate thing but thats not true. The shortcut points to the shortname :MSPOWERPINT. These shortnames are created in registry and the path to powerpoint exe is not correctly given there. either correcting the path in registry or making the shortcut directly point to the powerpoint executable will correct this error.
5. Small bug but there is no option to set the device lock (password when the phone is restarted)
6. No Transcriber (Not really a bug but i need it)
7. Clock canot be set to 12 hour format. it always returns to 24 hour format.
8. Search feature that comes with default windows mobile has been removed.
9. Tabs in HTC home show up even when they are removed from settings>today>htc home setting. It happens sometimes only i think.
10. Windows Live not working at all even after installing the official cab. I tried about 10 cabs from this forum. Nothing worked. It confirms that the issue is not due to conflict with older version of live on ROM coz this ROM doesn't have windows live on it.
Thats all i can think of right now. Will post more if i find some.
man i don't have time to fix this issue bcoz my exam is there
i make kitchen for this rom work only for new gene
try to fix bug and release some nice rom
happy rom cooking
part1 part2
extract all file in same folder
Hey ankit,
I have succeeded in porting the XIP of the default kitchen given by Ramersonw by using my original Wm 6 XIP as base. I have created a ROM based on that kitchen which i will post tomorrow as i am currently uploading both of these.
The kitchen is working perfectly for new GENE and i am 90% sure that i'll be able to port most of the ROMs using this kitchen. Will post kitchen on the Ramersonw's thread also.
that's grate news plz post only xip or changes u made is default kitchens i will not able to download whole because i don;t have enough bandwidth
Hi Ankit,
I am uploading the zip file with changes only. Here is the link for it. And dont forget to read the Readme.txt i have included in it. I am also uploading the ROM i created. Wait for the new ROM thread. Here is the address for the zip file:
http://cid-988261b694475a67.skydriv...gesOnly|_for|_NewGene|_Kitchen|_Ramersonw.zip
thanks for sharing file i will test it
i want to know is ur xip porting procedure is work on different gene rom ?
my xip port procedure work on only this rom
My XIP will work on any ROM which has the same version of WM 6.1. Actually buddy, as you might already know, what happens is that XIP contains a portion of the main files of the WIndows Mobile operating system which are executed without loading into main ram. That is why this part is called XIP (eXecute In Place). So These files have to be the exact same version as the rest of the OS. My XIP is from CE OS 5.2.20931 (Build 20931.1.5.0) so all the ROMs that use this version of WM 6.1 can use this XIP as base.
And this is true for your ROM too. You can use the XIP with any ROM with same version and build no.
I hope i have made myself clear but feel free to ask more.
thanks for info man i really don't known this
Sorry for bumping this.
I have installed this ROM, And I really liked this. It has fastest responce times, and the most Available RAM, from all the ROM's for Gene(More than 25% using even after 2 Hrs of use.)
So Ankit or Sumit, if you have time, will you please modify this rom (I still need to learn cooking.)
Download Java - JBed
Attached the spbcalc_p.gif. Placing it in windows dir, works.
Thanks
Sumit
brother Sumit / Ankit: Please cook and release for Old Gene also.
Thanks for all the great cooks....
My inspiration 4 releasing this kitchen is Mr.Krazy , But I think he is also going to release this updated rom soon with a new kitchen.
I just tried to do one myself.
I know there are many fine cooks here and all are happy with the new 6.5 I know they wont expect wm6.1, But as a cook i like to try the new roms. But i am not releasing the rom, just the kitchen.
I tried my level best to port the XIP for both new and old Gene, But i only tried on old gene.
For kitchen tools, I used and both worked fine (for old gene only, I dont have new gene)
(Ramersonw's Kitchen for Gene)
http://forum.xda-developers.com/showthread.php?t=464632
(BesFen's Kitchen)
http://forum.xda-developers.com/showthread.php?t=505156
For Sys and original rom Xip and language Packs, I recompiled the packs for gene.
Da_G's
http://forum.xda-developers.com/showthread.php?t=547314
For OEM i used
ankit360 Ingredients to Cook ROM
http://forum.xda-developers.com/showthread.php?t=544966
I dint modify any files in sys Its been 3 days i tested. Its fine.
(with PP 6 starting was 24 mb and after 2days its 19 mb)
I dont have to warn about rom cooking. As you cooks know all.
Download Here and post review, It took hours of learning.
wm6.1_Build 21054 SYS and XIP (ported for new and old gene)
Good..
Do you use an Old Kitchen or New Kitchen (Base on Platform rebuilder)???
BesFen said:
Good..
Do you use an Old Kitchen or New Kitchen (Base on Platform rebuilder)???
Click to expand...
Click to collapse
Hi i used your Build_WM6.1_ROM.cmd from DUMP & REBUILD ROM from this thread
[16 August 09|TUTORIAL|XIP+SYS] MSXIPKernel + MSXIPKernelLTK & SYS of Build 23025
http://forum.xda-developers.com/showthread.php?t=505156
I gave the links for the tools and i mentioned your thread also
Battery Backup
tvk24 said:
Hi i used your Build_WM6.1_ROM.cmd from DUMP & REBUILD ROM from this thread
[16 August 09|TUTORIAL|XIP+SYS] MSXIPKernel + MSXIPKernelLTK & SYS of Build 23025
http://forum.xda-developers.com/showthread.php?t=505156
I gave the links for the tools and i mentioned your thread also
Click to expand...
Click to collapse
Hey buddy,
How about the battery backup in this ROM? Since in Krazy's ROM, I was getting just one day of battery backup.
yours_vinodh said:
Hey buddy,
How about the battery backup in this ROM? Since in Krazy's ROM, I was getting just one day of battery backup.
Click to expand...
Click to collapse
To be honest it came 1 day. But i was testing with some packages and av files. And did normal use of calls and texts.
tvk24 said:
To be honest it came 1 day. But i was testing with some packages and av files. And did normal use of calls and texts.
Click to expand...
Click to collapse
try to make 0 module in slot 0 partitions, it can increase the battery back up, mine is 2,5 days with active exchange mail.
BesFen said:
try to make 0 module in slot 0 partitions, it can increase the battery back up, mine is 2,5 days with active exchange mail.
Click to expand...
Click to collapse
hey buddy can u explain in simple steps how to do this?
ams1576 said:
hey buddy can u explain in simple steps how to do this?
Click to expand...
Click to collapse
Convert some module to file.
tvk24 said:
Hi i used your Build_WM6.1_ROM.cmd from DUMP & REBUILD ROM from this thread
[16 August 09|TUTORIAL|XIP+SYS] MSXIPKernel + MSXIPKernelLTK & SYS of Build 23025
http://forum.xda-developers.com/showthread.php?t=505156
I gave the links for the tools and i mentioned your thread also
Click to expand...
Click to collapse
Why don't you use new kitchen base on platform rebuilder?? it can be use both for wm 6.5 and wm 6.1, it more simple, no need to port xip, you can follow my tut.
Good..
How Says everybody into 6.5? Eh? Atleast I am still in 6.1. With Sumit's VM Ultimate 3.1.1.
Its great someone is still interested in developing 6.1. I always find 6.1 in much better than 6.5 in Usage wise. All apps run smooth. Doing great, So keep it up pal, I was so upset Sumit's no longer relesing 6.1 developments. Now we have you.
Great Going!
Its not true that i wont release 6.1 now. There were no new builds since long and ever since this 21054 has came out i am on phone internet so i cannot post it. I have already made the ROM from it and it works nice and well.
As Besfen has pointed out and also from the word of one of my other friend in forum, the problem with new 6.1 builds is that there are larger sized and a bit more modules in the recent builds which cause the slot 0 to fill more. This causes decrease in available virtual memory and drainage of battery. I was not aware of this issue till i built the 21051 build, Pro Users ROM 6.1 Edition version 2.7. The new ROM that i have built is not having the power issue and i got 2.5 days of battery with quiet heavy use.
The trick is to recmod (covert to dll) the modules which are heavier in size, like say more than 150 or 200 kb. Plus we also have to keep in mind that we dont recmod resource only modules, the modules which dont have code inside them. Resource only modules are automatically relocated in SLOT 63 as according to Da_G and recmodding them will actually cause them to be allocated in slot 0 dynamically at the runtime (when we actually use them in out phone). These modules generally have names ending in "res" or sometimes, the word comes in between the name. To really verify this, you need to open the module in a program like PE Explorer and check that it should not have a .data or .text segments. Resource dlls only have .rcdata segments. For more information on these segments and all, you will need to understand the intricacies of "The PE File Format" which is available on MSDN, just search for it.
krazy_about_technology said:
Its not true that i wont release 6.1 now. There were no new builds since long and ever since this 21054 has came out i am on phone internet so i cannot post it. I have already made the ROM from it and it works nice and well.
As Besfen has pointed out and also from the word of one of my other friend in forum, the problem with new 6.1 builds is that there are larger sized and a bit more modules in the recent builds which cause the slot 0 to fill more. This causes decrease in available virtual memory and drainage of battery. I was not aware of this issue till i built the 21051 build, Pro Users ROM 6.1 Edition version 2.7. The new ROM that i have built is not having the power issue and i got 2.5 days of battery with quiet heavy use.
The trick is to recmod (covert to dll) the modules which are heavier in size, like say more than 150 or 200 kb. Plus we also have to keep in mind that we dont recmod resource only modules, the modules which dont have code inside them. Resource only modules are automatically relocated in SLOT 63 as according to Da_G and recmodding them will actually cause them to be allocated in slot 0 dynamically at the runtime (when we actually use them in out phone). These modules generally have names ending in "res" or sometimes, the word comes in between the name. To really verify this, you need to open the module in a program like PE Explorer and check that it should not have a .data or .text segments. Resource dlls only have .rcdata segments. For more information on these segments and all, you will need to understand the intricacies of "The PE File Format" which is available on MSDN, just search for it.
Click to expand...
Click to collapse
Nice tut.ThanksHere is more abou it
http://www.everythingdiamond.info/showthread.php?t=490
Hi.
Forgive me I asked here but it seems to be nowhere explained, maybe I was not able to find.
I try to utilize leeston2379 suggestions about cooking in His tutorial.
Could anybody explain me why newly created ROM from original firmware ( in my case Malezya ROM ) after dumping and building without any changes , differs significantly from original in size.
It is about 20-30MB lesser than original.
I dumped this newly created ROM. It seems to have all packages like original ROM but for example .dsm files are significantly lesser.
Could anybody confirm that such created ROM ( even without any changes ) can be safely loaded to tg01 and what exactly has been changed and why ?
I count on serious and comprehensive explanation.
Regards
fxdjacentyfxd
fxdjacentyfxd said:
Hi.
Forgive me I asked here but it seems to be nowhere explained, maybe I was not able to find.
I try to utilize leeston2379 suggestions about cooking in His tutorial.
Could anybody explain me why newly created ROM from original firmware ( in my case Malezya ROM ) after dumping and building without any changes , differs significantly from original in size.
It is about 20-30MB lesser than original.
I dumped this newly created ROM. It seems to have all packages like original ROM but for example .dsm files are significantly lesser.
Could anybody confirm that such created ROM ( even without any changes ) can be safely loaded to tg01 and what exactly has been changed and why ?
I count on serious and comprehensive explanation.
Regards
fxdjacentyfxd
Click to expand...
Click to collapse
hi, sorry for my poor english, but i will help you
when you dump a ROM, that has orginal 200 MB and you building a new ROM without any changes, then must your cooked ROM to have also 200 MB. ech oem package folder has one .dsm file. pls tell me: wich kitchen and wich ROM.
regards, miro
mirolg said:
hi, sorry for my poor english, but i will help you
when you dump a ROM, that has orginal 200 MB and you building a new ROM without any changes, then must your cooked ROM to have also 200 MB. ech oem package folder has one .dsm file. pls tell me: wich kitchen and wich ROM.
regards, miro
Click to expand...
Click to collapse
Thanks miro.
1) Kitchen suggested in this thread http://forum.xda-developers.com/showthread.php?t=804529 and with direct link here :
http://forum.xda-developers.com/attachment.php?attachmentid=416649&d=1286711727
2) I did two steps from this kitchen as leeston2379 suggested :
a) "1. dump.bat"
b) "2. build no XIP port_no auto.bat"
The same result ( I mean new ROM lesser than original ) I got when in step b)
I run "2. build.bat" instead of "2. build no XIP port_no auto.bat"
3) Original ROM I took for experiments is Malezya ROM from link :
http://www.toshiba.co.jp/product/etsg/cmt/english/asian/tg01/exe/TG01WP-WM6.5-Malaysia.exe
Currently I use this rom and I wanna to see what cooking is and in first step to cook ... nothing so dump and build without any changes.
Regards
fxdjacentyfxd
one question by side O i have noticed, you thank after a helpful post, but not with the thank button. why? is not why i like you thank- point- i´m wondering only- and you not the only.
fxdjacentyfxd said:
Thanks miro.
1) Kitchen suggested in this thread http://forum.xda-developers.com/showthread.php?t=804529 and with direct link here :
http://forum.xda-developers.com/attachment.php?attachmentid=416649&d=1286711727
2) I did two steps from this kitchen as leeston2379 suggested :
a) "1. dump.bat"
b) "2. build no XIP port_no auto.bat"
The same result ( I mean new ROM lesser than original ) I got when in step b)
I run "2. build.bat" instead of "2. build no XIP port_no auto.bat"
3) Original ROM I took for experiments is Malezya ROM from link :
http://www.toshiba.co.jp/product/etsg/cmt/english/asian/tg01/exe/TG01WP-WM6.5-Malaysia.exe
Currently I use this rom and I wanna to see what cooking is and in first step to cook ... nothing so dump and build without any changes.
Regards
fxdjacentyfxd
Click to expand...
Click to collapse
ok, this kitche i use mostly too.
the result in MB is the same if "2. build no XIP port_no auto.bat" or " 2. build.bat"
different is: 2. build no XIP port_no auto.bat- no new xip building- less time
i don´t know what is wrong- but is wrong and i think this ROM will brick your tg01
mirolg said:
one question by side O i have noticed, you danken after a hilfreiche post, but not with the thank button. why?
Click to expand...
Click to collapse
hehe, it was so called "thanks in advance" . If You give me answers to my questions I will press "thanks" button
Regards
fxdjacentyfxd
mirolg said:
ok, this kitche i use mostly too.
the result in MB is the same if "2. build no XIP port_no auto.bat" or " 2. build.bat"
different is: 2. build no XIP port_no auto.bat- no new xip building- less time
i don´t know what is wrong- but is wrong and i think this ROM will brick your tg01
Click to expand...
Click to collapse
It's too bad So I will try the same not with original rom but for example with clean Mangasora rom and will see results.
Anyway is there any other available kitchen/way to use original rom for cooking not special prepared rom like Mangasora rom ?
Regards
fxdjacentyfxd
fxdjacentyfxd said:
hehe, it was so called "thanks in advance" . If You give me answers to my questions I will press "thanks" button
Regards
fxdjacentyfxd
Click to expand...
Click to collapse
no, no problem- but is not the first time. i think you are very critical
but
fxdjacentyfxd said:
It's too bad So I will try the same not with original rom but for example with clean Mangasora rom and will see results.
Anyway is there any other available kitchen/way to use original rom for cooking not special prepared rom like Mangasora rom ?
Regards
fxdjacentyfxd
Click to expand...
Click to collapse
the easyst kitchen is that you use. ffboy kitchen is not so easy to understand.
BUT i tell you: no matter ROM or custom ROM- that what you dump out must, when no changes, the same Value in MB and kB!
if you like- one link http://forum.xda-developers.com/showthread.php?t=564130
mirolg said:
BUT i tell you: no matter ROM or custom ROM- that what you dump out must, when no changes, the same Value in MB and kB!
Click to expand...
Click to collapse
Explain me one thing yet. I noticed that even retrieving payload from .tsw and merging it again with the same .tsw to get "new" .tsw gives ROM that is not binary equal to original. Yes, it has the same size but comparing both roms in any editor one can see a lot of similar looking places that has been changed. Could You xplain it to me ?
I tested original ROMs again. English Orange ROM and Malezya. Both after cooking nothing gives .tsw files that differs in size to their originals. Maybe You could ask Your colegues cookers about it ? Is this situation exception for original roms and if not what has to be done additionally after dumping , so that new .tsw files have the same size as their originals. I would really prefer to work on original roms
Regards
fxdjacentyfxd
.. your thread is open for all cooks, to answer you: D
all my knowledge i have from this "best" forum site and his members!
If someone begins to cook, he must be prepared and know that it can so often give problems and that the tg01 brick or not start. ShortPin and tg01 downloader-procedure i must make multiple times (i love and have also afraid for my tg01)
BUT this a way to learn everything and to find a solution.
wish you all succes
miro
mirolg said:
.. your thread is open for all cooks, to answer you: D
all my knowledge i have from this "best" forum site and his members!
If someone begins to cook, he must be prepared and know that it can so often give problems and that the tg01 brick or not start. ShortPin and tg01 downloader-procedure i must make multiple times (i love and have also afraid for my tg01)
BUT this a way to learn everything and to find a solution.
wish you all succes
miro
Click to expand...
Click to collapse
Maybe someone answer who knows. Anyway thanks for help.
What I found interesting. Such newly created rom form original rom has as You know lesser length. Dumping it again and building new rom without changes, gives at last what we want - new rom size has the same size as original ( not virgin one but this cooked without changes ).
Maybe it is nothing terrible that first rom created from original rom is lesser and as a matter of fact we should take for cooking not original rom but this created from it without changes ? . Maybe original rom has any redudant information ( I mentioned You , .dsm file were shortened after cooking and in my oppinion they are now similar to thouse I can typically see in Novembre or Mangasora roms ).
On the other hand, I have never found anywhere yet, original rom should be treated with any special atention during dumping and cooking.
I know I can use short pin method but matter must be worthy to sacrifice tg01. Currently problem seems to be known for some cookers ( some ot them had to use original rom as a base of cooking ) so I will wait.
Regards
fxdjacentyfxd
fxdjacentyfxd said:
I know I can use short pin method but matter must be worthy to sacrifice tg01.
Click to expand...
Click to collapse
I am dumping the Malaysia ROM now, I will rebuild and flash to my test device regardless of size difference and let you know the result. Give me a few hours though as i am very busy and doing this in 5 minute gaps when I a have chance.
I have dumped the ROM twice and found that "Missing Manifests" are reported.
First time there were 3 missing, 2nd time 5 missing. The manifests are .dsm files so I am assuming that if the .dsm is missing from a package it is no longer a package and won't be included in the ROM by BuildOS causing the size difference. The first dump also failed to separate the OEM and SYS packages but succeeded the second time
I have rebuilt and flashed the ROM and it appears to work, i do not have time to test it fully but it does boot and run with SPB Mobile Shell, HOWEVER as the two dumps had different .dsm files missing it may be something more important missing the next time causing a real brick.
This is purely speculation but I believe this particular ROM does not like to be dumped and you will have to use a different base ROM. I am happy for you to use mine but I would recommend one of Miros clean ROMs as a base.
Hope this is helpful
Attached is a photo of the output from the .bat file showing the missing .dsm files (this is from the second dump).
... As already mentioned: Each folder (if any OEM packages) need a .dsm file. Without it, the package can not be cooked. Ie = if at the end (finished ROM) that those. dsm missing, is missing the complete pakage = Created ROM has less RAM.
if you has nothing doing- but a .dsm file is missing, then is something wrong
what? i don´t know
leeston2379 said:
I am dumping the Malaysia ROM now, I will rebuild and flash to my test device regardless of size difference and let you know the result. Give me a few hours though as i am very busy and doing this in 5 minute gaps when I a have chance.
Click to expand...
Click to collapse
You are great ! I am waiting for results.
leeston2379 said:
I have dumped the ROM twice and found that "Missing Manifests" are reported.
First time there were 3 missing, 2nd time 5 missing. The manifests are .dsm files so i am assuming that if the .dsm is missing from a package it is no longer a package and won't be included in the ROM by BuildOS causing the size difference.
This is purely speculation but I believe this particular ROM does not like to be dumped and you will have to use a different base rom.
I am rebuilding the ROM now and will flash it soon.
Click to expand...
Click to collapse
Maybe You are right but I hope You are not
So Your test will show the truth. I did not pay attention on this "Missing manifest" assuming that any errors stop dumping/building.
Regards
fxdjacentyfxd
Updated post #13
leeston2379 said:
I have dumped the ROM twice and found that "Missing Manifests" are reported.
First time there were 3 missing, 2nd time 5 missing. The manifests are .dsm files so I am assuming that if the .dsm is missing from a package it is no longer a package and won't be included in the ROM by BuildOS causing the size difference. The first dump also failed to separate the OEM and SYS packages but succeeded the second time
I have rebuilt and flashed the ROM and it appears to work, i do not have time to test it fully but it does boot and run with SPB Mobile Shell, HOWEVER as the two dumps had different .dsm files missing it may be something more important missing the next time causing a real brick.
This is purely speculation but I believe this particular ROM does not like to be dumped and you will have to use a different base ROM. I am happy for you to use mine but I would recommend one of Miros clean ROMs as a base.
Hope this is helpful
Attached is a photo of the output from the .bat file showing the missing .dsm files (this is from the second dump).
Click to expand...
Click to collapse
Thanks a lot for Your test. I have this manifest warning too doing dump process to text file. I have found somwhere in internet that some of this .dsm are concerned with XIP . Here if You wanna to see Nokser's thread not concerned with tg01 but mentioning some of the manifest files :
http://webcache.googleusercontent.c...fd3-bd127a05e4de.dsm&cd=1&hl=pl&ct=clnk&gl=pl
Anyway, could You explain me once again what build is running without brick ?
You simply did dump and build on malezya rom and took created .tsw or You dumped created rom again and built again and took this double built rom?
Regards
fxdjacentyfxd
fxdjacentyfxd said:
Anyway, could You explain me once again what build is running without brick ?
You simply did dump and build on malezya rom and took created .tsw or You dumped created rom again and built again and took this double built rom?
Regards
fxdjacentyfxd
Click to expand...
Click to collapse
I dumped the original ROM rebuilt it then flashed it. I did not double build.
Just dumped the rebuilt ROM and no errors occurred. It may be worth dumping the Malaysian ROM removing the packages you require then adding them to the Orange UK ROM as this dumps OK and both ROMs are in English.
The build of the Malaysian ROM is CE OS 5.2.21840 (Build 21840.5.0.60), just for reference.
leeston2379 said:
I dumped the original ROM rebuilt it then flashed it. I did not double build.
Click to expand...
Click to collapse
I am not familiar with the matter so far but I did simple test as in Nokser's thread about dumping XIP. I took xip.bin created after dumping malezya rom and dumped it via XipPort.exe. All "not available" manifest files are present so in my oppinion it should be possible to avoid this "terrible" warnings and maybe any new dump script is required for such original rom. This time it is my speculation
Regards
fxdjacentyfxd
leeston2379 said:
I dumped the original ROM rebuilt it then flashed it. I did not double build.
Just dumped the rebuilt ROM and no errors occurred. It may be worth dumping the Malaysian ROM removing the packages you require then adding them to the Orange UK ROM as this dumps OK and both ROMs are in English.
The build of the Malaysian ROM is CE OS 5.2.21840 (Build 21840.5.0.60), just for reference.
Click to expand...
Click to collapse
Hmmm, really ? I dumped English Orange ROM too. I do not remember whether mentioned warnings appeared but I am sure created rom was lesser than original rom like with Malezya rom.
Regards
fxdjacentyfxd
We decided to start a survey for OsBilder users. The question of it is the following:
What new options/settings/possibilities do you want to have in future releases of the program?
Please leave the detailed description of these options, as well as specify the reason why they so are necessary or desirable for you.
Your ideas and recommendations could be useful for further development of the program.
Do not post requests to implement complete support for building ROMS for some definite device name or brand - Barin cannot buy all the brands available at the market to carry out tests with them.
If you stubbornly want this support – you are free to buy and send a desired device to Barin for testing.
Requests to add one or another program option without giving a reason to do it – won’t be under consideration.
Requests to translate program interface into any language other than English and Russian won’t be answered here. We can only talk about the options related directly to functionality of DumpTool and OSBuilder features.
Concerning bug reports for currently implemented features – they should be also posted in the main OsBuilder thread.
Note about the Rom-Protection feature of OsBuilder for WP7.
The OsBuilder developers and the other members of asusmobile team get a lot of PMs from xda rom-cooking guys with the requests to implement kinda “rom protection” feature for WP7 roms.
Guys and gals!
For the moment only one developer has a real reason to protect his own work. It’s DFT, because DFT makes real development. With unique programs and features included. With new cool possibilities enabled.
But DFT is able to PERFECTLY protect their work without our humble assistance.
The rest of us guys – have NOTHING to protect. All of us have the identical registry tweaks, unlocks etc.
Protection of your personal “eye candy” stuff is considered to be a waste of time – all nice pictures are available in web.
So guys – please stop PM-ing about WP7 rom protection – at least until we all start to really develop WP7 – not just dump stocks and rebuild them moving away some langs and adding some pictures.
One more important thing: dumping DFT PROTECTED roms will NEVER be implemented as DumpTool feature.
Changing the LOGO and SLDR1-2
NK.bin XIP as well as automatic
1: Changing the LOGO and SLDR1-2
thanks
pdaimatejam said:
NK.bin XIP as well as automatic
1: Changing the LOGO and SLDR1-2
thanks
Click to expand...
Click to collapse
Changing LOGO - already implemented. Will be available in the next public version (coming soon).
Base OS.nb file is over 300Mb in the kitchen. So I have to rebuild it into smallest size manually. (after reduced its size about 20Mb)
My suggestion is OSbuilder will auto reduce base OS.nb after run dump/create packages to get smallest kitchen folder size. Thanks so much.
Regards.
nhathoa said:
Base OS.nb file is over 300Mb in the kitchen. So I have to rebuild it into smallest size manually. (after reduced its size about 20Mb)
My suggestion is OSbuilder will auto reduce base OS.nb after run dump/create packages to get smallest kitchen folder size. Thanks so much.
Regards.
Click to expand...
Click to collapse
We are working on it, but we don't have enough info about some data structures in NB to recreate them. If you have all info about them, please PM me. (logical/checkpoint sectors recreation, mapping tables, etc...)
EDIT: nhathoa, thanks for your advice in PM
nhathoa said:
Base OS.nb file is over 300Mb in the kitchen. So I have to rebuild it into smallest size manually. (after reduced its size about 20Mb)
My suggestion is OSbuilder will auto reduce base OS.nb after run dump/create packages to get smallest kitchen folder size. Thanks so much.
Regards.
Click to expand...
Click to collapse
If we get any new *.nbh file then OSBuilder display error, but if we get os.nb.payload from this same ROM, then OSBuilder support this file
Important:
OSbuilder: - In this moment no extract/dump of some files *. nb0 (SAMSUNG), and *.nbh (exam. HTC Spark/Mozart/Mango)
Nokser said:
In this moment no extract/dump of some files *. nb0 (SAMSUNG), and *.nbh (exam. HTC Spark/Mozart/Mango)
Click to expand...
Click to collapse
OSbuilder supports Mozart/Spark stock rom, but do not try to dump DFT protected ROMs.
Btw i've got Mozart and i made the dump with OSBuilder
Guys, this message is about Rom-Protection feature of OsBuilder.
The OsBuilder developers and the other members of asusmobile team get a lot of PMs from xda rom-cooking guys with the requests to implement kinda “rom protection” feature for WP7 roms.
Guys and gals!
For the moment only one developer has a real reason to protect his own work. It’s DFT, because DFT makes real development. With unique programs and features included. With new cool possibilities enabled.
But DFT is able to PERFECTLY protect their work without our humble assistance.
The rest of us guys – have NOTHING to protect. All of us have the identical registry tweaks, unlocks etc.
Protection of your personal “eye candy” stuff is considered to be a waste of time – all nice pictures are available in web.
So guys – please stop PM-ing about WP7 rom protection – at least until we all start to really develop WP7 – not just dump stocks and rebuild them moving away some langs and adding some pictures.
One more important thing: dumping DFT PROTECTED roms will NEVER be implemented as DumpTool feature.
This message will be added to the first post
will ROM protection ever be implemented in future version of OS Builder?
though, i suppose, one knows they have a 'good' ROM when others' 'take' from it.
would like to see...
a. Settings be save-able and imported
b. being able to import .CAB files (i.e. OEM firmware updates)
also, in the current version of OS Builder,
if Expand/Collapse button is Expanded and the content is refreshed, the Expand/Collapse button doesn't revert to Expand even though it is Collapsed.
hope that made sense.
sh4d0w86 said:
...being able to import .CAB files (i.e. OEM firmware updates)
Click to expand...
Click to collapse
We are working on it
Really hope i well see other web viewer like opera or firefox
Maybe we well see a new way to custom our home screen
hossam.salah, heh
I would also like to have new opera and customized homescreen.... And even something else... like new WP7 phone set
Hate to disappoint you, but we discuss here future OsBuilder features. OsBuilder does not provide any new OEM packages or custom screens. It's an advanced tool for creating roms.
So your dreams should be published maybe in WP7 Software development thread...
sh4d0w86 said:
b. being able to import .CAB files (i.e. OEM firmware updates)
Click to expand...
Click to collapse
I would love to see that
IzaacJ said:
I would love to see that
Click to expand...
Click to collapse
Will be implemented in future public
Changing the logo
florirs said:
Changing the logo
Click to expand...
Click to collapse
Implemented already! Since OS Builder V1.3.189 FULL (08.11.2011)
Read changelogs!
http://forum.xda-developers.com/showpost.php?p=19168768&postcount=65
POLL What new features do you want to have in OsBuilder future releases
Hey guys What apps do you use most and are best with HTC HD2?
because we can get widgets made to link these apps on the touchxperince homescreen
mine in google maps with street view
BiapLorScarp said:
Hey guys...
Click to expand...
Click to collapse
Hey guy!
If you are able to explain - what is common between OsBuilder features thread and Google Maps with touchxperience on Leo - we will definitely talk about that....
Otherwise - try to find yourself another topic to talk.
Start point for bulding wp7 for hd2
mb a basic non protected non dft dump?
not sure what i just sayed but i think you understand what i meen.
will Samsung support be coming to OSBuilder?
Hmmm...
Yes I know, again stupid Question.
Why we can not use SHW-M130K "Modem" or part from it?
S8500 not start ?
S8500 explode ?
Any Logfiles exists?
Later I will write more... need to check again SHW-M130K files and JTAG Dump...
Its long long time ago...
Best Regards
It's so old... I have forgotten where my files stored.
http://forum.xda-developers.com/showthread.php?t=1133736
Here seems Firmware still active for SHW-M130K...
http://pspmaster.tistory.com/48
I have forgotten which files inside...
In bada Firmware amss.bin is mandatory file for Call.
This files is huge, more then 12 MB...
If you write own Code, then you know why I wrote huge... for 12 MB...
Samsung Android handset need file modem.bin...
Don't punish me, if wrong name...
In actual bada Android Port... modem.bin is complete DISABLED/or ignored by zImage ...
SHW_M130K_0x00000000_OK.rar this is JTAG dump I have for study...
No idea, if I remember correct, modem.bin from SHW-M130K is near 7 or 10 MB...
Damn, if I find my files I know it correct...
Best Regards
Short checked I9000 Firmware...
But here is baseband from Infineon... instead Qualcomm...
modem.bin is bigger then 12 MB...
I have taken this one for "research"...
GT-I9000_XEU_I9000XXJW4_I9000OXAJW4_I9000XXJW4.zip
Now I will download SHW-M130K WC21 from here:
http://pspmaster.tistory.com/48
Soon more ...
Best Regards
adfree said:
Short checked I9000 Firmware...
But here is baseband from Infineon... instead Qualcomm...
modem.bin is bigger then 12 MB...
I have taken this one for "research"...
GT-I9000_XEU_I9000XXJW4_I9000OXAJW4_I9000XXJW4.zip
Now I will download SHW-M130K WC21 from here:
http://pspmaster.tistory.com/48
Soon more ...
Best Regards
Click to expand...
Click to collapse
I really wish i learn to develop softwares nt unfortunately nt nw... So jst tell me in plain words gud news r bad news...i think u shud check for oldr samsung android phones....
M130K-HOME-GB-REV04-WC21
Short checked...
modem.bin bigger then 15 MB...
This time it is Qualcomm related... and also QSC6270...
Next...
For AMSS, this is your Modem... you need NVM knowledge...
NV items is also NO Kindergarten...
Minimum knowledge is Qualcomm related Tools like QPST and if more advanced. Then QXDM...
http://forum.xda-developers.com/showthread.php?t=899023
So you need advanced users with deep Qualcomm knowledge about AMSS, NVM... for instance like our pro Unlockers... GSM...
No Link to forum...
But this Forum is nice... Maybe you find here ""enough"" stuff for study.
http://www.finetopix.com/
Here are smart users with deeper knowledge...
Best Regards
Summary...
For successfully Modem integration you need expertS with:
- deep Qualcomm knowledge about AMSS, RF, NV...
this include working with Tools like QXDM...
- coding skills alone are nice... but not enough to manage all problems...
As modem.bin is 10 MB of perfect matching data... this is like rocket science.
This means many years of experiences in this GSM/CDMA business...
So in my opinion we have at the moment nobody... who can finish this in 2012...
1 man can't finish this...
Best Regards
QXDM overview from Qualcomm
Feel free to clicking around.
https://support.cdmatech.com/qxdm/1_START_HERE.htm
Here Call related...
https://support.cdmatech.com/qxdm/CallManager/CallManagerindex.htm
Here some NV...
https://support.cdmatech.com/qxdm/NVbrowser/NVindex.htm
Now maybe you can understand, how complex AMSS/Modem is...
Best Regards
https://jobs.qualcomm.com/public/jobDetails.xhtml?requisitionId=1888000&page=jobSearch
Such users we need also.
Embedded Software Engineer - GSM/EDGE Modem Physical Layer
Click to expand...
Click to collapse
http://www.qualcomm.com/careers
Clicking around and you will see. How long some jobs require...
3 years of experience...
Maybe after 3 years we will have someone, who is able to finish succesfull Modem functionality...
Maybe someone is able to make visible progress in 2013.
After hard, hard, hard learning process...
Best Regards
after seeing all this i have lost hopes for modem. drivers to be written from scratch.
only hope is that some modification of other android modem.bin gets fit to our modem.
or else we can hope for an optimised 3.3 inch android tab.
god bless wave.
Yes,its seems that modem writing is not an easy job...
especially for 1 person...
anyways,Adfree...u did a fantastic job by finding all this stuff...
only hope is with some trick or shortcut by which we can modify some other android modem...(my weird thought)
but for now,well done
Regards,
WaveGuru
http://www.youtube.com/watch?v=IWSCdpAeONA
Found this here:
http://code.google.com/p/docl4amss/wiki/ReferencePage
Btw...
Someone has this Doc found ?
80-VE263-25-MSM7200A-BasebandTopics.pdf
And normally for each Qualcomm Chip...
Full AMSS Source Code exists...
Several hundret MB...
Maybe someone has found something... MSM6xxx or older ?
Pudn is very good site to find interessting stuff...
Best Regards
http://bb.osmocom.org/trac/
OsmocomBB is an Free Software / Open Source GSM Baseband software implementation.
It intends to completely replace the need for a proprietary GSM baseband software, such as
drivers for the GSM analog and digital baseband (integrated and external) peripherals
the GSM phone-side protocol stack, from layer 1 up to layer 3
In short: By using OsmocomBB on a compatible phone, you are able to make and receive phone calls, send and receive SMS, etc. based on Free Software only.
Over the past 12 months, we've been making very good progress. Most of the hardware drivers have been written, and a relatively complete layer1, layer2 and layer3 exist.
No work has yet been done on any sort of UI on the phone. The only user interface is a telnet-based command line.
Click to expand...
Click to collapse
Our chipset is not listet... but maybe interesting for research...
Best Regards
Using modem from any other QSC6270 based phone is some kind of solution. modem.bin does in fact contain AMSS, stored in same or almost same format.
Actually Oleg used some modem.bin and it seems like it worked but
a) It would require rebuilding EFS aswell (like cloning it from QSC6270 phone and replacing IMEI?)
b) If there's no Android phone based on QSC6270 with battery fuel gauge controlled by modem - we won't have battery control, and this seems to damage something. My battery seems to be pretty well "worn out" and my fuel gauge totally decalibrated, it keeps showing fake values all the time and at all my battery keeps power for ~20hours, I will put a warning in kernel thread.
Comparing to implementation of new RIL - it's rather easy way to get some more functionallity out of Badadroid.
I've got pretty complete sources for MSM7200 AMSS and believe me - it's not something you want to dig in. It's just HUGE.
a) It would require rebuilding EFS aswell (like cloning it from QSC6270 phone and replacing IMEI?)
Click to expand...
Click to collapse
There are few Fake IMEI... kind of "Emergency IMEI" somewhere in AMSS...
In theory we can have all the same IMEI for Calling...
I remember from my AMSS journey from 2006... QC Standard IMEI bla...bla
Will look into my old stuff...
Also I think we have enough space... to create more NV items...
I've got pretty complete sources for MSM7200 AMSS and believe me - it's not something you want to dig in. It's just HUGE.
Click to expand...
Click to collapse
I know few sources... but never seen complete AMSS package...
Also my brain is tooooo small to use these sources for something usefull.
I need this only for my QC collection. :angel:
Best Regards
http://blog.csdn.net/yili_xie/article/details/5656608#comments
Here seems few QC related infos... maybe more...
Request to other users.
Please.
1.
I need AMSS source for Download.
No idea, 300 or 400 MB ZIP or more...
Maybe this is something in this kind... Google Power. :angel:
https://www.codeaurora.org/git/proj...ions/db2575e163152f681668800744c99f287f77a8ef
Best Regards
How about Samsung Galaxy 3 I5800 ?
004400152020000
This is IMEI from SXG75, EF81, SL91 ... handset from 2006 with MSM6250...
If NV item 550 was lost/empty/blocked...
There are hundrets of such devices...
Also this IMEI can be found on other manufacturer, if QC AMSS...
a) It would require rebuilding EFS aswell (like cloning it from QSC6270 phone and replacing IMEI?)
Click to expand...
Click to collapse
For Android you could define new NV ID for IMEI... instead NV 550...
Best Regards
Rebellos said:
Using modem from any other QSC6270 based phone is some kind of solution. modem.bin does in fact contain AMSS, stored in same or almost same format.
Actually Oleg used some modem.bin and it seems like it worked but
a) It would require rebuilding EFS aswell (like cloning it from QSC6270 phone and replacing IMEI?)
b) If there's no Android phone based on QSC6270 with battery fuel gauge controlled by modem - we won't have battery control, and this seems to damage something. My battery seems to be pretty well "worn out" and my fuel gauge totally decalibrated, it keeps showing fake values all the time and at all my battery keeps power for ~20hours, I will put a warning in kernel thread.
Comparing to implementation of new RIL - it's rather easy way to get some more functionallity out of Badadroid.
I've got pretty complete sources for MSM7200 AMSS and believe me - it's not something you want to dig in. It's just HUGE.
Click to expand...
Click to collapse
and what about tablet like this
http://www.androidtoitaly.com/goods.php?id=368
or this
http://it.aliexpress.com/product-fm/591540997-2012-new-android-tablet-sim-card-slot-wholesalers.html
they also have QSC6270...
also many renesas tablet have QSC6270, here some firmware/skd
http://www.chinadigitalcomm.com/opa...enesas-android-tablet-pc-firmware-t10398.html
Rebellos said:
Using modem from any other QSC6270 based phone is some kind of solution. modem.bin does in fact contain AMSS, stored in same or almost same format.
...
b) If there's no Android phone based on QSC6270 with battery fuel gauge controlled by modem - we won't have battery control, and this seems to damage something.
...
Comparing to implementation of new RIL - it's rather easy way to get some more functionallity out of Badadroid.
I've got pretty complete sources for MSM7200 AMSS and believe me - it's not something you want to dig in. It's just HUGE.
Click to expand...
Click to collapse
Rebellos, the modem control the battery? or them is related someway? kinda creepy
How to edit AMSS.bin or Modem.bin??