Hello All,
Firstly, I would like to say how great this website is and tip my hat off to all the people involved in maintaining this site.
I am very new to the whole XDA modification scene and have a ton of newbie questions. I know some of these questions have been asked before; however I still have not grasped the concepts fully. I have tried to restate the questions asked before so that I (and hopefully other newbie’s ) can fully understand how to modify XDA’s.
Any help anyone can provide will be greatly appreciated.
So here goes the questions:
When creating a customized ROM (using MKRom) my understanding is that one has re-create the initobj.txt and the Default.reg. Is it possible just to install all the applications you want, and then download the initobj.txt and the Default.reg and place them in the cfg directory for the custom ROM?
If this does not work, how does one know what to edit in these files?
When MKROM request a Rom image, is it requesting the backup ROM IMAGE? Will any image do?
When backing up a ROM, what option does one have to select to backup the operating system, settings and programs inside the ROM? Does CE do all of this?
What is CE, Boot, GSM stand for in the boot menu?
If one wants to just create a new boot image, what is the simplest way? Does one have to create a whole new ROM?
If one wants to just have the unlocking software, what is the simplest way? Does one have to create a whole new ROM?
When creating a Rom using RomKitchen, it asks you add Add your own ROM files? Is this your backup rom?
In RomKitchen one of the readme files asks for:
bootimage.bmp,_initobj.txt,_initdb.ini,_default.reg,xipchain
Is the default.reg and the initobj.txt in this directory have to be pre altered for the new programs one wants in the Rom like the way the MKROM wants them? Does the setup program create them for you?
Is the bootloader.nb0 file specific to the boot loader you have?
Very confused what is exactly needed in the /CFG directory.
In the CFG directory do you place your backup Rom dump?
Hi ...
Do you call these as newbie questions ??!! :shock: ... I can hardly wait to see your advanced ones :wink:
If I got you right, you want to "create" your own ROM instead of doing like most of us by "cooking" a new ROM in one of the kitchens like www.yorch.net
I may advice you to move this thread to the "Hacking it" forum which I see it a better place than here.
Not that i have any use for now but how do you chef do to extract such and such exe or image from a rom and cook it into your own?
I'd like to start and do my own simply because I'd like to be able to customize my own and also learn how you do it...
Can anyone point out to me some tuts or where to start?
Thanks
QkSi1ver said:
Not that i have any use for now but how do you chef do to extract such and such exe or image from a rom and cook it into your own?
I'd like to start and do my own simply because I'd like to be able to customize my own and also learn how you do it...
Can anyone point out to me some tuts or where to start?
Thanks
Click to expand...
Click to collapse
Have a look on the Wiki or the "* Upgrading Forum" for your Device type. There is normally a ROM Kitchen thread / wiki page.
Thanks
Dave
-------- RTFW! ----------------
Is there any way to change the kernel inside the NBH files from *can't insert link to DZO's Android files for Vogue*? DZO, what did you use to create them? I'm having a hard time replacing the kernel with my custom one... In case anyone is wondering, I'm attempting to install Debian on my XV6900's internal flash. I know what I'm doing here, but after tireless searching, I couldn't find anything about the kernel setup in the NBH files I mentioned.
Any help would be appreciated - maybe I'll make a tutorial when I'm done.
Thanks!
gTan
gTan64 said:
Is there any way to change the kernel inside the NBH files from *can't insert link to DZO's Android files for Vogue*? DZO, what did you use to create them? I'm having a hard time replacing the kernel with my custom one... In case anyone is wondering, I'm attempting to install Debian on my XV6900's internal flash. I know what I'm doing here, but after tireless searching, I couldn't find anything about the kernel setup in the NBH files I mentioned.
Any help would be appreciated - maybe I'll make a tutorial when I'm done.
Thanks!
gTan
Click to expand...
Click to collapse
Wrong part of the forum. You should ask in the General section of the Vogue.
Sorry, I just realized that after I posted it. I found what I was looking for, though
If anybody is interested in grabbing the ringtones/wallpaper/strange sample icons from WM7, it's possible to reverse engineer the BIN file to get at the raw files that make up WM7.
Happy to post steps if anybody wants to get at this stuff, if not please see wallpapers and ringtones attached to this post. Hopefully helpful to somebody out there.
thanks... please post how to extract the bin for noobs!
Of course... you need:
- The BIN file. In this case I used WM7Full.bin available from several sites
- viewbin.exe from Microsoft Platform SDK
- cvrtbin.exe from Microsoft Platform SDK
- dumprom.exe from Microsoft Platform SDK
You may also be able to find these utilities using Google.
Use viewbin.exe to analyse the file:
viewbin.exe -t wm7full.bin
You'll see an image start and length. Start was 0x81000000 with length 0x0496A294 for the specific file I used. Plug these values into cvrtbin.exe:
cvrtbin.exe -r -a 0x81000000 -l 0x0496A294 -w 32 wm7full.bin
(obviously substituting the -a and -l value for those obtained from viewbin. Leave -w as 32)
This will produce wm7full.nb0. Plug this file into dumprom.exe:
dumprom.exe -d c:\output wm7full.nb0.
And there you have it, the files will be chucked into c:\output in their entirety.
Thanks for this one, some good sounds inside
I can't find viewbin.exe, cvrtbin.exe, and dumprom.exe anywhere, can someone post a link?
EDIT: Or, better yet, could someone just upload the dump?
EDIT 2: Okay, I found the tools, but the dump didn't work. Any suggestions?
Could you provide details of the error that you're seeing please?
To answer your other questions, I'm not planning to upload the whole dump as it's copyright and against the forum rules. Same goes for the tools, they're part of the Platform Builder SDK.
akersj said:
Happy to post steps if anybody wants to get at this stuff, if not please see wallpapers and ringtones attached to this post. Hopefully helpful to somebody out there.
Click to expand...
Click to collapse
Thank you very much
Not to be a buzzkill, but these are the same ringtones and sounds from 6.1/6.5
Though I missed flamenco fire, thanks for bringing it back
mazzarin said:
Not to be a buzzkill, but these are the same ringtones and sounds from 6.1/6.5
Though I missed flamenco fire, thanks for bringing it back
Click to expand...
Click to collapse
LOL.. I didn't try 6.1/6.5, just saw the BIN file screaming to be taken apart! Flamenco Fire ... hmm interesting
akersj said:
Could you provide details of the error that you're seeing please?
To answer your other questions, I'm not planning to upload the whole dump as it's copyright and against the forum rules. Same goes for the tools, they're part of the Platform Builder SDK.
Click to expand...
Click to collapse
There is no error message; I run the tools exactly as described, which works, but when I look for "C:\output", I can't find it. Otherwise everything is fine.
Fdo35 said:
There is no error message; I run the tools exactly as described, which works, but when I look for "C:\output", I can't find it. Otherwise everything is fine.
Click to expand...
Click to collapse
You will need to substitute c:\output for a directory of your choice that exists on your system. Please also ensure that you are using the offset and length appropriate to the bin file you are using.
Fdo35 said:
There is no error message; I run the tools exactly as described, which works, but when I look for "C:\output", I can't find it. Otherwise everything is fine.
Click to expand...
Click to collapse
as akersj says above... you need to create the folder c:\output first or use another folder that already exists. The tools will not create a new directory for you.
Oh, I see now! I can't believe I didn't try that!
Well, anyway, this is pretty interesting. Especialy files like 'FileBrowser.exe,' FileBrowserCM.dll,'and 'NativeInstallerHost.exe' could be of some great use to us.
Hi all
Just need a little technical help here
I am making a script to odex a ROM
Currently the only way of odexing a ROM is by doing it on the phone (pushing the files to the phone and executing them there)
I have made a script which will extract a ROM to a folder, odex it, and let you compress/sign/flash it.
The problem :
It seems that deoxpt-wrapper (the module which odexes the files) is a binary file and therefore can not be executed. I assume only the Android OS can use this module which is why it can not be done on computer? Does this mean that odexing can only be done on a phone?
This is the code I am having trouble with:
Code:
~/resources/dexopt-wrapper $filename `echo $filename | sed 's/\(.*\.\)apk/\1odex/'`
Any advice would be greatly appreciated.
Regards
polite bump
no-one can help?