If you get a device like a Magician with a newer version of the ROM, Radio etc. it would be nice to be able to run a tool that would suck out the radio, OS and ExROM into .nbf files which could then be packaged up for posting. Any tool that gets these images cleanly out so that something like xda3nbftool can work on them?
Also it would be terrific to be able to get the bootloader as well like this.
By the way, while I know how to use it I haven't found a link for tghe docs and maybe the source for xda3nbftool? Is that posted?
Hi all!
Downloading custom ROMs is VERY cool, but a bit of a pain sometimes because the downloads are huge. I have a suggestion about how this could be resolved.
To explain my idea, let's look at how you would flash a ROM using the new method being suggested. You'd need the following things...
- USPL (as usual)
- Custom RUU (as usual)
- 'Control' ROM NBH
Here's the first difference. The control ROM in my proposal is the widely circulated HTC ROM NBH, which can be found here. You'd keep the NBH from this ROM (RUU_Signed.nbh) named as HTC.nbh, and it would be used by all subsequent updates.
So let's imagine that I have a device (USPL'd of course) that I want to flash to the T-Mobile ROM. I'd make sure I had a directory with the Custom RUU and Control ROM NBH in, then i'd download the file from the ROM creator. In this file would be a batch file, a ROM patch and the patcher. The batch file would patch HTC.nbh to T-Mobile spec, then run Custom RUU. The beauty of it? The download would be very small!
Would it work? YES! And to prove a point, please check out this post - where you'll find Orange, T-Mobile and Tilt ROMs in tiny downloads based off the control NBH. ROM chefs - let's start using this system, which i'm calling 'Kaiser TLR ROMs' for obvious reasons.
ROM chefs, to create the patches you just need to use bsdiff, which can be found here. Use the syntax 'bsdiff HTC.nbh YourROM.nbh YourRom.patch'. You can see a sample batch file in my link above.
So... what do u think?
TLR
I don't get it once your HTC is HardSPL'ed then there is no CID lock and you can flash any rom to your device. Most rar files containing the RUU_signed.nbh are only 40-50MB thats pretty small and can be deleted when your finished flashing. To me this seems like a lot of extra work for the cook(sometimes me) and more support issues I find it easy just to upload the ROM i made to rapidshare or some other file hosting site and people can download as they like.
40-50MB is a lot bigger than 6-7MB.
It's not a lot of extra work at all really, it's running one command line, and distributing a couple of files.
I think patching definitely has potential, not least that they are a lot easier (and a lot less illegal?) to host.
TLR
theloanranger said:
40-50MB is a lot bigger than 6-7MB.
It's not a lot of extra work at all really, it's running one command line, and distributing a couple of files.
I think patching definitely has potential, not least that they are a lot easier (and a lot less illegal?) to host.
TLR
Click to expand...
Click to collapse
Sounds interesting about the legal hosting capability for diff ROM files instead entire ROM. The ROM archive goes down in the past for the M$ pressing . If we can archive only diif ROMs, this can be one solution to take back the ROM archive into the FTP at XDA.
One offtopic question, where did you get the Orange Shipped ROM for Kaiser?
Cheers.
I didn't, it's a dump and repack, as is the T-Mo one.
TLR
Hi,
I didn't find any information about this: create all images you need to flash yours device and put them into one file (like shipped rom from HTC)
If it's not possible tell me why - yes, I'd really like to know
regards,
Robert
I'm not sure of what you mean. The RUU_signed.nbh file contains a lot of things: the Windows Mobile 6 OS, Programs, and maybe the radio firmware.
What do you have to begin with?
I'd like to get ROM for my Kaiser from polish Orange - I've found only reconstructed ROM without specific radio 1.27.12.29 (this radio is available as 4 files, not one *.nbh file)
greetz
i stumbled across the 6.5 emulator which i downloaded from microsofts website....ive been looking all over the net for a way to test out custom roms with this program with no luck...is it not possible? or is there another program similar to this one to test out roms before flashing?
Im searching the right thing.... I had split my 6.5.X 23053 nb... into .bin overwrite the older .bin for the same ress... and the emulator said... that is not a .bin image rom or .nb0... so is there a way to make it runs newer or other builds in it?
Thanks
I am interested to know what tools are available to do a "diff" ( http://unixhelp.ed.ac.uk/CGI/man-cgi?diff ) between ROMs in Android and, if possible, even against the a nandorid backup or some other method to get the file on the phone.
I expect that it would be possible to to extract the content of the ROM on two different folder and then running a opendiff or some other tools (ex: http://meldmerge.org/ ) on the two folder.
I am trying to see what executable and what script changed between a stock ROM and what I have currently running on my phone or other ROMs available here.
Thank you in advance!