i would like to know how to extract the nb0 file.. is there a nb0 file that i could download that is stock to the triumph?

http://android-dls.com/wiki/index.ph...epack_NB0_file

Contents of .nb0:
total 817800
-rw-r--r-- 1 tejesh staff 13815808 Aug 12 19:43 FB0-0-2340-ftm.img
-rw-r--r-- 1 tejesh staff 4464640 Aug 12 19:43 FB0-0-234A-0001-recovery.img
-rw-r--r-- 1 tejesh staff 733412 Aug 12 19:42 FB0-0-234A-emmcboot.mbn
-rw-r--r-- 1 tejesh staff 419522 Aug 12 19:42 FB0-0-2350-MPRG7x30.hex
-rw-r--r-- 1 tejesh staff 768449 Aug 12 19:42 FB0-0-2350-NPRG7x30.hex
-rw-r--r-- 1 tejesh staff 5405484 Aug 12 19:42 FB0-0-2350-adsp.mbn
-rw-r--r-- 1 tejesh staff 18362368 Aug 12 19:42 FB0-0-2350-amss.mbn
-rw-r--r-- 1 tejesh staff 223888 Aug 12 19:42 FB0-0-2350-dbl.mbn
-rw-r--r-- 1 tejesh staff 2724 Aug 12 19:42 FB0-0-2350-loadpt.cmm
-rw-r--r-- 1 tejesh staff 955936 Aug 12 19:42 FB0-0-2350-osbl.mbn
-rw-r--r-- 1 tejesh staff 32768 Aug 12 19:42 FB0-0-2350-partition.bin
-rw-r--r-- 1 tejesh staff 512 Aug 12 19:42 FB0-0-2350-partition.mbn
-rw-r--r-- 1 tejesh staff 256000000 Aug 12 19:43 FB0-0-318B-5017-system.img.ext3
-rw-r--r-- 1 tejesh staff 96 Aug 12 19:43 FB0-318B-0-5019-A01.md5
-rw-r--r-- 1 tejesh staff 3851 Aug 12 19:42 FB0-318B-0-5019-A01.mlf
-rw-r--r-- 1 tejesh staff 2512 Aug 12 19:43 FB0-5019-007-NV_cust.mbn
-rw-r--r-- 1 tejesh staff 83886080 Aug 12 22:00 FB0-5019-007-cda.img.ext3
-rw-r--r-- 1 tejesh staff 768000 Aug 12 19:43 FB0-5019-007-splash.img
-rw-r--r-- 1 tejesh staff 31457280 Aug 12 21:49 FB0G-0-3010-5019-hidden.img.ext3
-rw-r--r-- 1 tejesh staff 584 Aug 12 19:43 FB0_5019_NV.xml
-rw-r--r-- 1 tejesh staff 1373773 Aug 12 19:43 NvDefinition.xml
-rw-r--r-- 1 tejesh staff 517 Aug 12 19:43 list
*there's also a boot.img. I must've moved it around when I uploaded it for Isaac on this thread.

.mlf contents:
[Package Download Profile]
PROFILE VER = 0.3
MODEL = 7x30
PROJECT = FB0
PLATFORM = Q21
EMMC = TRUE
INITOPTION = 0x110
INITDLTYPE = 0x1

[Package Info]
/*-----------------------------------------------------------------------------
UPDATE_FLAG_NULL = 0x00
UPDATE_FLAG_DBL = 0x01
UPDATE_FLAG_FSBL = 0x02
UPDATE_FLAG_OSBL = 0x04
UPDATE_FLAG_AMSS = 0x08
UPDATE_FLAG_CEFS = 0x10
UPDATE_FLAG_APPSBOOT = 0x20
UPDATE_FLAG_WIN = 0x40
UPDATE_FLAG_DSP1 = 0x80
UPDATE_FLAG_DSP2 = 0x100
UPDATE_FLAG_ANDROID_BOOT = 0x200
UPDATE_FLAG_ANDROID_SYSTEM = 0x400
UPDATE_FLAG_ANDROID_USER_DATA = 0x800
UPDATE_FLAG_ANDROID_RECOVERY = 0x1000
UPDATE_FLAG_ANDROID_SPLASH = 0x2000
UPDATE_FLAG_ANDROID_HIDDEN = 0x4000
UPDATE_FLAG_ANDROID_FTM = 0x8000
UPDATE_FLAG_CUSTOMER_NV = 0x10000
UPDATE_FLAG_ANDROID_CDA = 0x20000
UPDATE_FLAG_RESERVED_1 = 0x40000
UPDATE_FLAG_RESERVED_2 = 0x80000
UPDATE_FLAG_RESERVED_3 = 0x100000
UPDATE_FLAG_RESERVED_4 = 0x200000
UPDATE_FLAG_RESERVED_5 = 0x400000

Modem: DBL + OSBL + AMSS + dsp1 = 0x8D
Host : APPSBOOT + DSP1 + ANDROID_BOOT + ANDROID_SYSTEM + ANDROID_USER_DATA + ANDROID_RECOVERY = 0x1EA0
FTM : APPSBOOT + ANDROID_BOOT = 0x220
-------------------------------------------------------------------------------*/
FLAG = 0x3F6AD

[Firmware File Name]
FILENAME_EFLASH_HEX = "FB0-0-2350-MPRG7x30.hex"
FILENAME_FLASH_HEX = "FB0-0-2350-NPRG7x30.hex"
FILENAME_FLASH_BIN = "xxx.bin"
FILENAME_PARTITION = "FB0-0-2350-partition.mbn"
FILENAME_PARTITION_BIN = "FB0-0-2350-partition.bin"
FILENAME_OSBLHD = "osblhd.mbn"
FILENAME_OSBL = "FB0-0-2350-osbl.mbn"
FILENAME_DBLHD = "dblhd.mbn"
FILENAME_DBL = "FB0-0-2350-dbl.mbn"
FILENAME_AMSSHD = "amsshd.mbn"
FILENAME_AMSS = "FB0-0-2350-amss.mbn"
FILENAME_CEFS = "cefs_modem.mbn"
FILENAME_DSP1 = "FB0-0-2350-adsp.mbn"
FILENAME_DSP2 = "dsp2.mbn"
FILENAME_APPSBOOTHD = "appsboothd.mbn"
FILENAME_APPSBOOT = "FB0-0-234A-emmcboot.mbn"
FILENAME_ANDROID_BOOT = "FB0-0-234A-5017-boot.img"
FILENAME_ANDROID_SYSTEM = "FB0-0-318B-5017-system.img.ext3"
FILENAME_ANDROID_USR_DATA = "FB0-0-VV-MM-userdata.img.ext3"
FILENAME_ANDROID_RECOVERY = "FB0-0-234A-0001-recovery.img"
FILENAME_ANDROID_SPLASH = "FB0-5019-007-splash.img"
FILENAME_ANDROID_HIDDEN = "FB0G-0-3010-5019-hidden.img.ext3"
FILENAME_ANDROID_FTM = "FB0-0-2340-ftm.img"
FILENAME_LOADPT = "FB0-0-2350-loadpt.cmm"
FILENAME_NV_CUST = "FB0-5019-007-NV_cust.mbn"
FILENAME_ANDROID_CDA = "FB0-5019-007-cda.img.ext3"
FILENAME_RESERVED1 = ""
FILENAME_RESERVED2 = ""
FILENAME_RESERVED3 = ""
FILENAME_RESERVED4 = ""
FILENAME_RESERVED5 = ""
FILENAME_SIM_PERSO = "FB0_5019_sim_perso.xml"

[FAT]
FILE_LOCATION_OSBL = "5"
FILE_LOCATION_DBL = "5"
FILE_LOCATION_AMSS = "1"
FILE_LOCATION_DSP1 = "5"
FILE_LOCATION_APPSBOOT = "1"
FILE_LOCATION_ANDROID_BOOT = "5"
FILE_LOCATION_ANDROID_SYSTEM = "5"
FILE_LOCATION_ANDROID_USR_DATA = "5"
FILE_LOCATION_ANDROID_RECOVERY = "1"
FILE_LOCATION_ANDROID_SPLASH = "1"
FILE_LOCATION_ANDROID_HIDDEN = "5"
FILE_LOCATION_ANDROID_FTM = "1"
FILE_LOCATION_NV_CUST = "5"
FILE_LOCATION_ANDROID_CDA = "5"
FILE_LOCATION_RESERVED1 = "5"
FILE_LOCATION_RESERVED2 = "5"
FILE_LOCATION_RESERVED3 = "5"
FILE_LOCATION_RESERVED4 = "5"
FILE_LOCATION_RESERVED5 = "5"

[NV Item]
QCN FILENAME = "NV.xml"
NV DEFINITION = "NVDefinition.xml"
CUSTOM_NV = "FB0_5019_NV.xml"

[CEFS BACKUP FILE]
FILE NUMBER = 0
FILE NAME = NULL

Originally Posted by StaticMaal

YEA I WAS

Can you help me my phone wont boot up it keeps going into download mode. This is what i did i went into download mode to fix it from when i installed the gingerbread.nbo. I deleted the image folder then replaced it with the one i backed up with and now my phone will only boot in bootloader.

To get it to boot, you should be able to reflash the .nb0 file. Either place it on your sdcard as firmware.nb0 or use the SUT from the link posted where you got the gingerbread.nb0. Unfortunately, this will only restore the GSM version, so you still won't have CDMA cell signal. Unless Motorola releases an .nb0 file for the Triumph, you're likely SOL...

You could try to find a doner Triumph, put in download mode, and mount it under linux and clone it partition by partition and bit by bit... It might work? I'm not sure what else the nb0 file contains in addition to the partitions that it might've mucked with...

Cloning it SHOULD work from another unit, provided the partitioning didn't get too-seriously borked, and it probably didn't.

Incidentally I cannot get the loader to mount on my Linux (Ubuntu) distro; I am running it in a VM however. It does connect for adb and similar, but the automount that other people have reported doesn't work on my machine and no devices show up when I plug it in that I can manually mount either.....

If anyone finds a fix for this i will donate $5 through paypal

From what I'm understanding, what must be done is take Cherry Mobile's gingerbread ROM, replace the radio image w/ our current one, package that back up, and then we'll have gingerbread on our phones?

Hopefully more devs with the capability to do this will start using this phone. It seems so easy, yet it's beyond my technical capacity.

Without a CDMA load to grab from this is not as easy as it sounds.

It MAY be possible to graft in a CDMA radio to CM7. I'm playing with this, but it's a longshot.

The easy path is when Moto releases kernel sources, which they should eventually do. There may be a shortcut in the meantime, which is why I'm looking into it, but I wouldn't hold my breath....

Hopefully we get a custom rom sooner rather than later. I'm tired of the stock one already.

Hey is anything still needed from a stock triumph? I have a stock triumph (just rooted that's it) and I have windows PC, experience with adb.

Sent from my MOTWX435KT using XDA App