Database Info

What type is .NBH?

Does anyone know what type of a file a .nbh is and how to make it veiwable/modifiable. If there was a way that we can mod the NBH file that I believe would be the successful way of rooting the MyTouch 3G. I will be getting one of the production devices in a week or so anyone want to have anything dumped let me know.

the nbh is a ROM and you can't flash it without a modified SPL. i'm not even sure the SPL used for android even supports the file type but any kitchen from winmo can decompile it

Not really so much an android thing but is a hardware thing of HTC. The Dream and Sappihre support these files. There is a NBH file which will take you all the way back to RC29 and also flashes back the original SPL as well. So it is my belief that if we can make a compatible NBH for the sapphire it will accomplish the end result.

Of course it will... That's what NBH files are made for. I don't think you can make one since it's signed (or something) with a key we don't have.

Ehh, i have an idea:
Some has to decompile .nbh and modify it to work on mytouch 3g.
Than you have to create a goldcard.. not sure about if viperbjk is putting sapphire into qmat..

Yeh I have tried to decode with hex editor and have not had any real luck with it at all. Looks coded. Just wondering if anyone knows how to decode would be greatly appreciated. I have tried to use some of the old Windows mobile kitchen tools.

There are lots of tools to extract NBH files, they should work if HTC hasn't changed anything...look for other devices kitchens and you'll find the tools.
Also there's a project which tries to achieve the same result under linux http://code.google.com/p/htc-flasher/.

where did you guys get an android nbh? this is odd because android is updated by placing and update.zip on the root of the sd card (among other ways) which is handled by the SPL. why wouldn't HTC just stick with nbh then?

sammypwns said:
where did you guys get an android nbh? this is odd because android is updated by placing and update.zip on the root of the sd card (among other ways) which is handled by the SPL. why wouldn't HTC just stick with nbh then?
Click to expand...
Click to collapse
android is updated by .zip but NBH is an all in one image type file that flashes htc phones to factory defaults. its usually used by the support techs to restore phones.
android/google=zip
htc =nbh

tripledes said:
There are lots of tools to extract NBH files, they should work if HTC hasn't changed anything...look for other devices kitchens and you'll find the tools.
Also there's a project which tries to achieve the same result under linux http://code.google.com/p/htc-flasher/.
Click to expand...
Click to collapse
this looks promising...i wonder if we can figure out how to resign it....

Hi,
I have just tested the HTC-Flasher and unfortunately it does not work with the DREAIMG.nbh
So i someone know how to extract and re-flash the dream NBH please help.
Bye
Herc. 8)

Cannot install from SD

Has anyone else not been able to perform an update from the sd. States unverified , unsigned.
I have
HBOOT-1.33.0004 (SAPP10000) : Sapphire PVT 32B SHIP S-ON G : CPLD-10 (Voldafone NL + UK + Australia
Nothing will update from the sd, it always fails any suggestions ?

Hello mate, I have the exact some problem.
I've just been told though in another thread that when we rename the ROM we download and put on the SD card, we shouldn't name it 'update.zip' we should just name it 'update' the '.zip. should come naturally as it is still a compressed file.
Give it a whirl and let us know how you get on, I can't try until I get home from work but it would be nice to know if this solved it as I couldn't figure out why the ROM couldn't be found on the SD card at all last night
Good luck.

Roy_Drage said:
Hello mate, I have the exact some problem.
I've just been told though in another thread that when we rename the ROM we download and put on the SD card, we shouldn't name it 'update.zip' we should just name it 'update' the '.zip. should come naturally as it is still a compressed file.
Give it a whirl and let us know how you get on, I can't try until I get home from work but it would be nice to know if this solved it as I couldn't figure out why the ROM couldn't be found on the SD card at all last night
Good luck.
Click to expand...
Click to collapse
Hey I appreciate that.

Let us know if it wors for you.

Make sure the update.zip is not inside the .zip you downloaded. (if you know what I mean)

How do I port ROMs to 32A [Windows?]

Hey guys.
Is there any guide etc, that can show me how to port ROMs to 32A Magic using windows?
Thank you

WaterMan! said:
Hey guys.
Is there any guide etc, that can show me how to port ROMs to 32A Magic using windows?
Thank you
Click to expand...
Click to collapse
I think you'll be much better off using a Linux distribution for this sort of stuff. I have never looked into running perl scripts and the like in Windows but I dont imagine it is very enjoyable.
Run a virtual machine with Ubuntu or something.
The general process to port a 32B ROM --> 32A is to swap the 32b kernel for a 32a one. This also requires that you change the wlan.ko as it is tied to the specific kernel.
I recommend VirtualBox for a virtual machine - it is very simple to use and set up. Check out this article for a bit of a primer http://lifehacker.com/5204434/the-beginners-guide-to-creating-virtual-machines-with-virtualbox
Once you have Ubuntu (or w/e) set up...grab Amon_RAs port tools from here. You will also want to set up the android-sdk as well. There is a good guide on the android sdk download site. You dont need to worry about eclipse and stuff unless you are going to be a dev.
Basically, just download the sdk, unpack it, add the tools dir to your PATH and you are set.
From there you can download the update.zip I use for cyanogen ports, delete my packaged boot.img, grab a 32A kernel, get the ramdisk from a ROM you want to port and create a boot.img using the 32A kernel and the ramdisk. You will also need to replace the wlan.ko in /system/lib/modules to match the kernel you decide to use. Then, rezip everything, sign the existing zip file and flash away.
hope this helps and isnt super confusing.

bcrook said:
Run a virtual machine with Ubuntu or something.
Click to expand...
Click to collapse
or just format your comp and use ubuntu cus its the **** but ill have to agree it seems to be a headack with windows, far easier with linux

I am not getting Linux, windows has far to many things I need.
Guess I will stray away from that path then. Thanks anyways

Runnig a virtual machine is no risk. It runs ubuntu inside a window...like an application

bcrook said:
From there you can download the update.zip I use for cyanogen ports, delete my packaged boot.img, grab a 32A kernel, get the ramdisk from a ROM you want to port and create a boot.img using the 32A kernel and the ramdisk. You will also need to replace the wlan.ko in /system/lib/modules to match the kernel you decide to use. Then, rezip everything, sign the existing zip file and flash away.
Click to expand...
Click to collapse
Hi bcrook, thanks for the explanation. I have just a simple question: does it need to be the exact same kernel or can it vary (for example 2.6.27 vs 2.6.29 or TT vs gbo)?

edubarr said:
Hi bcrook, thanks for the explanation. I have just a simple question: does it need to be the exact same kernel or can it vary (for example 2.6.27 vs 2.6.29 or TT vs gbo)?
Click to expand...
Click to collapse
You can use any kernrl u want as long as it is 32a. The wlan.ko just has to match.

Alright! Thanks very much bcrook!!!

Perfect how to, thanks a lot!

Porting Dream roms to the Magic

I'm sure I someone posted a script to automate this but I can't find it - so here goes with the question.
If I want to port a Dream rom to the Magic (32B), do I just replace the boot.img in the zip with one from a 32B rom, resign the update.zip and flash? Or is there more too it than that?

depends, most dream roms will work natively on the mt3g. a lot of the devs support it already, so you dont need to port at all.

Note that there are actually 2 different types of Magic:
- 32A has more RAM but requires a custom kernel and wireless LAN module
- 32B more or less completely compatible with most Dream ROMs

st0kes said:
I'm sure I someone posted a script to automate this but I can't find it - so here goes with the question.
If I want to port a Dream rom to the Magic (32B), do I just replace the boot.img in the zip with one from a 32B rom, resign the update.zip and flash? Or is there more too it than that?
Click to expand...
Click to collapse
Actually there's LESS to it than that.
You need to unpack the boot.img, and if there isn't already a init.sapphire.rc, copy init.trout.rc to make one, then repack the boot.img. (Granted, that's actually harder than substituting the boot.img in its entirety, but it's less of an actual change in terms of the ROM contents! )
I always do it manually but remember the script, I think it was by Deicist - search for his (or her?) posts.
But this is only for 32B - 32A won't work like that.

Loccy said:
Actually there's LESS to it than that.
You need to unpack the boot.img, and if there isn't already a init.sapphire.rc, copy init.trout.rc to make one, then repack the boot.img. (Granted, that's actually harder than substituting the boot.img in its entirety, but it's less of an actual change in terms of the ROM contents! )
I always do it manually but remember the script, I think it was by Deicist - search for his (or her?) posts.
But this is only for 32B - 32A won't work like that.
Click to expand...
Click to collapse
What do you then do for porting 32B to 32A ?

here's my script for porting dream->32b in Linux.
http://forum.xda-developers.com/showthread.php?t=547260
Doesn't do anything particularly clever, just automates the unpacking->replacing->repacking procedure.

Cheers for the replies guys.
I'll give it a whirl tonight. There are a few that look interesting, might start with Micro Hero 1.5 since a lot of people are raving about it.

[HOWTO] porting a ROM for old radio to work with new radio

I would love to help the community by using your kernel for the newer radios to port any roms for the older radio... is there any help you can give me? should i use your boot.img from the test-donut.img/test-eclair.img?
Click to expand...
Click to collapse
first, a thing we must know for porting job is what boot.img included.
here: http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
the ramdisk do some initializing jobs, so if we port a ROM, we should ensure that the content in ramdisk and files which are included in ramdisk (like init.rc), have necessary things the ROM needed.
for the first step, we can just extract the boot.img from the ROM, and extract the ramdisk from the boot.img which extracted just now, then repack it with my kernel (you can extract the kernel from my boot.img with same tools).
(to execute the perl script in link above, you need linux or just cygwin. )
but if we are sure that the ROM we want to port have nothing special with ramdisk, just like common ROMs, we can use my boot.img files directly. for eclair ROM, I suggest you extract the boot.img from my ROM, and don't use the first boot.img (test-NOCDB.img) I had posted.
after this, make our update.zip (use other's ROM as an example, especially the update-script in META-INF directory). sign our zip with testkey and apply it, then we can make our phone booting into desktop.
(you can find information about sign and download tools here: http://forum.xda-developers.com/showthread.php?t=471586, though the thread is not talk about how to sign things)
the main troubles we may meet probably are symlinks and setperm* in the update-script. if there is already a file/link has a name we want to symlink to, or if there isn't a file we want to symlink from or setperm, we will fail. so check the files carefully.
the next step is make everything work properly. we can use file from a ROM which made for new radio (and work well of course) to replace the one in the ROM we are porting. we can find these files in my 2.x ROM for eclair, or other's 1.6 ROM for donut (and for new radio, since the maker of them tested them already).
the most important files are (to my knowledge):
system/lib/libhtc_acoustic.so
system/lib/libhtc_ril.so (if something wrong with mobile network)
system/lib/libcamera.so
system/lib/libcameraservice.so
system/lib/liboemcamera.so (for 2.x) or system/lib/libqcamera.so (for 1.6)
system/lib/libgps.so
system/bin/akmd
(are there something I missed?)
(if we want to use NCommander's work on CameraHardwareInterface with a 2.x ROM, we should use my kernel for DONUT instead. I didn't try it, and I don't recommend it.)
these files are some thing work with hardware partially, so different radio may need different files. but if something just work fine, don't hurry to replace the file for it.
and now...., I don't have more thing to talk about, since we have most things work well. but for further tweaks, there are lots of things to do.
everyone can post your question here. if I know the answer I will post it. if I don't or I am not online, I think others will response you. and if there are things I missed or made some mistake, plz point it out
I will update this post when we collection more info or correct something. I find that I don't organized everything in order . I will update it later.

Thanks for the post... what's the difference between your eclair/donut kernel? (This is based on your original post about your kernel... is there an updated kernel somewhere i should know about?)
Edit
Nevermind i figured it out by reading your post more. carefully thanks for the detailed instructions

Thank you very much for this sanpei. This is the type of posts that really should be on this forum
Appreciated so much. waiting for your next updates.

Phil_McRevis said:
Nevermind i figured it out by reading your post more. carefully thanks for the detailed instructions
Click to expand...
Click to collapse
sorry for my poor ability of expression
asero said:
This is the type of posts that really should be on this forum
Click to expand...
Click to collapse
I expect more people can share their knowledge, and we can make a wiki for all

Hello!
I have to edit some lines of init.rc of your kernel. I've thus extracted the ramdisk, edited the file, repacked and tried booting with fastboot boot kernel-img ramdisk-img, but the phone hangs on the operator logo. I've tried even just extracting kernel+ramdisk and boot them - same result (the boot.img works well).
how can I fix it? Thanks

Wrong post