Root The Triumph Experiment Thread (CAUTION!)

[Goofee691]

Almost forgot, also in that thread I had looked at each of the unknown "RAW" partitions with a hex editor trying to find anything linking them together in a attempt to find and correct the MEID without much luck but I was able to find out a little on what each one does, a little but not much.

 

[BSydz]

So, while trying to dig up specs on the phones hardware, I was looking on the motorola site and found this:

DEDICATED KEYSVolume control, Camera, Back, Search, Menu, Power/Lock, Home

So, does anybody have a dedicated camera button on their phone? Just thought this was interesting.

 

[Goofee691]

maybe its on the hardware trace but not hooked up?

 

[BSydz]

OMG I DID IT!


I got the phone back to factory, connected to the network and shows regular baseband and everything, proper MEID and ESN stuff also. I will give more details, after I flash another nbo to jack it up and figure out exactly the source, as soon as I stop jumping up and down from all this adrenaline.

 

[BSydz]

Ok, I got sidetracked and was trying to make some other roms work. I got the Cherry magnum rom to boot and say it was cdma evdo only but I don't think it contains the correct RIL data to support the network. So I tried the Sharp rom and it blue screened like when I used the wrong recovery, because it has the newer kernel.

I am still working on an exact bare minimum fix, but it will work with any MT. I have successfully restored my phone from 3 x6 variants, so far, and all meid stuff is intact.

I know I've seen it somewhere, but can't find it, is the serial in the phone. Like get the serial while the phone is on. Any pointers would be helpful, battery is at 5% so I have to charge it before I can do anything else.

 

[BSydz]

CAUTION! CAUTION! CAUTION!

I can not guarantee this will not mess up your phone.

ONLY TAKE THESE STEPS IN A LAST DITCH EFFORT!

YOU SHOULD NEVER FLASH A NB0 FILE THAT IS NOT MEANT FOR YOUR DEVICE!

But if you do, make sure you backup your whole original device through DD_rescue to be sure you can get it back. NO GUARANTEES.

Ok, so if you have already flashed the Cherry Magnum nb0 or other X6 nbo, I attached the partition below.

So I didn't mess up my new phone, I did a backup of my never turned on stock Triumph to a thumb drive, like this "dd_rescue /dev/sdc /dev/sdb", if sdc is the phone and sdb is thumb drive. I also backed up the phone how it was so I could get it back if anything went wrong. If you read further you will see which partitions you don't need, or want to use.

IF YOU BACKUP THE WHOLE PHONE, IT WILL CHANGE THE MEID AND ESN. BE CAREFUL!

After trying many different ways, this is the quickest way to achieve stock from a Cherry Magnum Gingerbread nb0 flash.

From stock Cherry Magnum Gingerbread nb0, I began by entering download mode and placing cwm recovery in the image folder and then flashing b_randons stock rom with splash.zip. I then placed the phone in download mode and connected it to my Ubuntu machine. With both the thumb drive and the phone connected I used dd_rescue to change partitons 3 and 1, like this "dd_rescue /dev/sdb3 /dev/sdc3", if sdb is thumb drive and sdc is the phone. Always check disk utility to make sure the paths are correct. Then reboot your phone and your done. And back on the VMU network!

If you don't have a phone to get the partition from, then use the attached .img and restore it to "/dev/sdb3" if sdb is your phone.


Partition 1 is just the mobile partition with the image folder in it. So, if you would like to keep cwm recovery you can just copy amss.mbn and emmcboot.mbn from Austries thread or your own backup of the image folder.EDIT: Here is my Mobile partition with cwm recovery. I used the one in Austires thread to be sure it would work for others. If you just do sdb3 and not 1, it won't boot, it will only boot into download mode but it will show polling no matter how you start the phone. You have to put the mbn files in the image folder, for it to work. After you change the 3rd partition, your buttons will be switched back to normal, and download mode is Vol down and power, instead of Vol up and power like in the other roms.

Thanks to Goofee691 documenting some info on the partitions in his MEID thread, I was able to figure some stuff out.

The partition table is still unknown, but here is a quick once over. I am NOT responsible if anything happens to your phone.

Spoiler

I have changed out the following partitions with dd_rescue without loosing my MEID or ESN stuff : 1, 2, 3, 5, 7, 8, 9, 10, 11, and 12

I have NOT, and suggest NOT to even try unless it is your own backup, to change out partitions : 4, 6, 13, 14, 15, 16, or 17 as 4 is the large extended partition that 5 through 17 sit on, and goofee691 said

when I copied partitions 6, 13, 14, 15, 16 and 17 to the phone it then was fully functional with my phones MEID and the old PRL so I am guessing that their is some check amongst the partitions to make sure they all match with the radio

NOTE: I have successfully gotten back to stock from Wellcom, Cherry, Spice, and the Sharp rom, but this is the bare minimum to get back from Cherry. I have not once had to backup the whole device from my "jacked up backup". But the sharp rom is tricky, I did SUT LR from it to the Cherry nb0 to get started testing the bare minimum.

 

[BSydz]

Does anybody here have any embedded Linux experience? After reading over the last couple days I am beginning to believe our system is just a portable embedded machine.

This is a very detailed explanation of how the Qualcomm SOC boots, and is very interesting, these are a couple lines I pulled to give you the gist.

"An examination of how the Qualcomm Mobile Station Modem (MSM) Snapdragon 7x30 system-on-chip boot-straps the processors into an operating system,"

"There are two processors in the MSM 7x30, an ARM9 for the radio and an ARM11 auxiliary applications processor. Each processor has its own JTAG and can be independently controlled using it."


"The ARM9 is the primary processor. It boots first, executing the Primary Boot Loader (PBL) from on-board ROM at 0xFFFF0000 ."

"DBL is part of Qualcomm's SecureBoot, which uses cryptography to guarantee that the boot-loader images haven't been tampered with. DBL configures the Cryptographic Look-aside Processor (CLP), a dedicated cryptographic co-processor, and other hardware sufficient to load and execute the Secondary Boot Loader (SBL) from a Flash memory device on EBI2 (External Bus Interface 2) from partition 3 (Linux mmcblk0p3)."

"Finally on the ARM9 REX executes the Advanced Mobile Subscriber Software (AMSS). AMSS runs in Security Domain 1 "

This is the link to the page.

Android/HTC/Vision/BootProcess ? TJworld

There is a wealth of knowledge at this guys webpage about android and the SOC, though it is mostly about his htc.

TJworld

 

[BSydz]

So, this is what I have found so far about the partitions on the Triumph, I can't guarantee that this is all correct, but if anybody has any input feel free to chime in.

WARNING, THE INFORMATION PROVIDED BELOW IS SPECULATIVE AND COMES WITH NO WARRANTY. IF YOU MESS WITH THIS STUFF, I AM NOT RESPONSIBLE IF YOU DAMAGE YOUR PHONE.

Partitions:
1 (FAT) Mobile Partition containing image folder, which is very well documented around the forums.

2 (crypt/QNX4.x) Primary Boot Loader (PBL) I believe that this is what the SOC uses to boot.

3 (crypt) Secondary Boot Loader I believe this is where the hardware layout is contained, as it changes button configuration and was key to getting back to normal after I flashed the wrong nb0. It is linked to the mobile partition, as the phone will not boot properly without the correct amss.mbn

4 (extended) Just an extended partition containing partitions 5 - 17.

5 (Boot) This is where the boot img is extracted.

6 (OnTrack DM) I think this manages and verifies integrity of partitions 13-17.

7 (ext3) This is where the system/rom is located. This is what you see in root explorer as "system", containing the build.prop and other stuff.

8 (ext3) This is the "data" folder .

9 (ext) This partition holds CDA info, with OEM apks, ringtones, and wallpapers, it seems to be mounted inside partition 10 (hidden) when the phone is on you can find the information merged into "hidden/data" using root explorer.

10 (ext3) This is the hidden partition containing boot images and CDA info. This can be found in "hidden" using root explorer.

11 (ext3) This is the cache partition.

12 (ext3) This is the Caivs, can't find too much info on this.

13-17 (unknown) I believe this is where the phone specific data is stored, including but not limited to MEID, ESN, and PRL.


I would like to start a thread with this information, but would like to wait til some more experienced people weigh in. It is probably better off buried in this thread, for now. Realize that, the first time I used Linux was, when I installed Ubuntu 11.10, about 18 days ago, just after I screwed my phone up. I just used my Win systems to mess with my phones. I'm sure there is somebody that has a better understanding of manipulating filesystems than I have, since my knowledge is mainly with Win systems.

Let me know if you think anything is incorrect so I can fix it as soon as possible. Thanks.

 

[BSydz]

Ok, so, if any of you wanted to know what is in partition 3 here is a text file, I use notepad ++ to view it. I also attached the partition, for anybody needing it to recover from an NB0 flash, you can find it here.

I want to create a zip to replace all of the partitions except 6 and 13-17, and maybe 2 cause I think that is download mode, it would act basically like an nb0, but I still have some digging to do, I might just have to make an nb0. I have looked through partition 2 and 3 and haven't found any phone specific stuff (meid, esn, serial) yet, so now on to partition 5.

 

[Austrie]

Impressive BSydz!

 

[BSydz]

This has been a very tedious process, Ubuntu will show the unknown partitions but won't read them, and windows would only read partition 1.

But I found a way. If you use http://www.diskinternals.com/download/Linux_Reader.exe ,in windows, you can get access to every partition, you just can't directly open the unknown partitions, but you can right click and choose "hex preview".

I have created img files for the partitions needed to make a FULL restore zip or nb0, I just have to get a little more familiar with the updater scripts and the nb0 hex and xml files. If anybody has any input or wants to help, let me know.

 

[BSydz]

Impressive BSydz!

Thanks, I always want to know how everything works. I can usually just look at something and figure out how it works, but this phone stuff is complicated. It's messed up, my brain will not let me let this go. I wake up in the morning in the middle of thoughts of how to get stuff working. It's like my mind is crunching all the numbers while I sleep and wakes me up in the middle of figuring it out. I'm not a phone guy by any means, though I do consider myself a PC guy. So to me, this is just another computer system to figure out.

I'm just trying to get as much info, about our phone, out in the open, in hopes that it will help somebody trying to work out some kinks with our phone.

I am willing to do experiments on this phone if anybody has any ideas or experimental roms and such, just pm me or reply in this thread.

Thanks again to all the devs in this community.

 

[BSydz]

I don't know if anybody has looked into the nb0s of the other x6 phones, but I figure I'll post some info from some of the files, for anybody interested. I am working on getting us a stock nb0 to flash through SUT, but I will only have my old phone for about a week and am not really willing to try this on my new phone. So if somebody has some time to help work this out, any help would be greatly appreciated, as I am basically shooting in the dark, and running out of time.

WARNING THIS IS ALL INFORMATION FROM THE CHERRY MOBILE NB0, NOT THE MOTOROLA TRIUMPH!

Though the layout of the partitions seems to be identical between the devices.

This is the file size info of included files:

Spoiler

FB0-318D-0-5019-A03.mlf 3.76 KB
FB0-0-2380-MPRG7x30.hex 409 KB
FB0-0-2380-NPRG7x30.hex 750 KB
FB0-0-2380-partition.mbn 512 bytes
FB0-0-2380-partition.bin 32.0 KB
FB0-0-2380-loadpt.cmm 2.66 KB
FB0-0-2380-dbl.mbn 218 KB
FB0-0-2380-osbl.mbn 933 KB
FB0-0-2380-amss.mbn 17.5 MB
FB0-0-2390-emmcboot.mbn 716 KB
FB0-0-2380-adsp.mbn 5.15 MB
FB0-0-2390-5017-boot.img 3.51 MB
FB0-0-318D-5017-system.img.ext3 244 MB
FB0-0-2390-0001-recovery.img 4.25 MB
FB0-5019-008-splash.img 750 KB
FB0G-0-3010-5019-hidden.img.ext3 30.0 MB
FB0-0-2390-ftm.img 13.2 MB
FB0-5019-008-NV_cust.mbn 2.45 KB
FB0-5019-008-cda.img.ext3 80.0 MB
FB0_5019_NV.xml 584 bytes
FB0_5019_sim_perso.xml 764 bytes
NvDefinition.xml 1.30 MB
FB0-318D-0-5019-A03.md5 120 bytes

This is the mlf:

Spoiler

[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-2380-MPRG7x30.hex"
FILENAME_FLASH_HEX = "FB0-0-2380-NPRG7x30.hex"
FILENAME_FLASH_BIN = "xxx.bin"
FILENAME_PARTITION = "FB0-0-2380-partition.mbn"
FILENAME_PARTITION_BIN = "FB0-0-2380-partition.bin"
FILENAME_OSBLHD = "osblhd.mbn"
FILENAME_OSBL = "FB0-0-2380-osbl.mbn"
FILENAME_DBLHD = "dblhd.mbn"
FILENAME_DBL = "FB0-0-2380-dbl.mbn"
FILENAME_AMSSHD = "amsshd.mbn"
FILENAME_AMSS = "FB0-0-2380-amss.mbn"
FILENAME_CEFS = "cefs_modem.mbn"
FILENAME_DSP1 = "FB0-0-2380-adsp.mbn"
FILENAME_DSP2 = "dsp2.mbn"
FILENAME_APPSBOOTHD = "appsboothd.mbn"
FILENAME_APPSBOOT = "FB0-0-2390-emmcboot.mbn"
FILENAME_ANDROID_BOOT = "FB0-0-2390-5017-boot.img"
FILENAME_ANDROID_SYSTEM = "FB0-0-318D-5017-system.img.ext3"
FILENAME_ANDROID_USR_DATA = "FB0-0-VV-MM-userdata.img.ext3"
FILENAME_ANDROID_RECOVERY = "FB0-0-2390-0001-recovery.img"
FILENAME_ANDROID_SPLASH = "FB0-5019-008-splash.img"
FILENAME_ANDROID_HIDDEN = "FB0G-0-3010-5019-hidden.img.ext3"
FILENAME_ANDROID_FTM = "FB0-0-2390-ftm.img"
FILENAME_LOADPT = "FB0-0-2380-loadpt.cmm"
FILENAME_NV_CUST = "FB0-5019-008-NV_cust.mbn"
FILENAME_ANDROID_CDA = "FB0-5019-008-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

This is the FB0_5019_NV.xml

Spoiler

<?xml version="1.0" encoding="UTF-8" ?>
<NvSource>
<NvItem id="50028" name="NV_BSP_ADB_USER_RIGHT_I" mapping="direct" encoding="dec" index="0">1</NvItem>
<NvItem id="50030" name="NV_FIH_VERSION_I" mapping="direct" encoding="dec" index="0">48,48,48,48,48,67,77,84,86,70,66,48,88,48,50,56,49,48,50,56,49,48,48,48,48,49,48,51,70,66,48,50,48,52,53,48,49,57,51,48,51,50,46,50,52,48,49,49,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0</NvItem>
</NvSource>

This is the FB0_5019_sim_perso.xml:

Spoiler

<SIM_Lock_List>

<!--Sim Lock Data items-->
<SIM_Lock_item_01>
<Lock_Type></Lock_Type>
<Lock_Value></Lock_Value>
<Lock_Sim_Slot></Lock_Sim_Slot>
</SIM_Lock_item_01>

<SIM_Lock_item_02>
<Lock_Type></Lock_Type>
<Lock_Value></Lock_Value>
<Lock_Sim_Slot></Lock_Sim_Slot>
</SIM_Lock_item_02>

<!--Subsidy Data-->
<Subsidy_Data>
<Lock_Autolock>0</Lock_Autolock>
<Lock_Number_Retries>10</Lock_Number_Retries>
<Lock_Penalty_Timer>0</Lock_Penalty_Timer>
<Lock_Skip_Perso_Check_ACC>0</Lock_Skip_Perso_Check_ACC>
<Lock_Check_Unlock_Everytime>0</Lock_Check_Unlock_Everytime>
<Lock_Ignore_MNC_Length>0</Lock_Ignore_MNC_Length>
<Subsidy_Argu>0x0 0xa 0x0 0x0 0x0 0x0 0x0</Subsidy_Argu>
</Subsidy_Data>

</SIM_Lock_List>

This is the FB0-0-2380-loadpt.cmm:

Spoiler

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; GENERATED FILE - DO NOT EDIT
;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
global &JsFile00InUse &JsFile00Name &JsFile00Pos &JsFile00Offset
global &JsFile01InUse &JsFile01Name &JsFile01Pos &JsFile01Offset
global &JsFile02InUse &JsFile02Name &JsFile02Pos &JsFile02Offset
global &JsFile03InUse &JsFile03Name &JsFile03Pos &JsFile03Offset
global &JsFile04InUse &JsFile04Name &JsFile04Pos &JsFile04Offset
global &JsFile05InUse &JsFile05Name &JsFile05Pos &JsFile05Offset
global &JsFile06InUse &JsFile06Name &JsFile06Pos &JsFile06Offset
global &JsFile07InUse &JsFile07Name &JsFile07Pos &JsFile07Offset
global &JsFile08InUse &JsFile08Name &JsFile08Pos &JsFile08Offset
global &JsFile09InUse &JsFile09Name &JsFile09Pos &JsFile09Offset
global &JsFile10InUse &JsFile10Name &JsFile10Pos &JsFile10Offset
global &JsFile11InUse &JsFile11Name &JsFile11Pos &JsFile11Offset
global &JsFile12InUse &JsFile12Name &JsFile12Pos &JsFile12Offset
global &JsFile13InUse &JsFile13Name &JsFile13Pos &JsFile13Offset
global &JsFile14InUse &JsFile14Name &JsFile14Pos &JsFile14Offset
global &JsFile15InUse &JsFile15Name &JsFile15Pos &JsFile15Offset
global &JsFile16InUse &JsFile16Name &JsFile16Pos &JsFile16Offset
global &JsFile17InUse &JsFile17Name &JsFile17Pos &JsFile17Offset
global &JsFile18InUse &JsFile18Name &JsFile18Pos &JsFile18Offset
global &JsFile19InUse &JsFile19Name &JsFile19Pos &JsFile19Offset

&JsFile00InUse=0
&JsFile01InUse=0
&JsFile02InUse=0
&JsFile03InUse=0
&JsFile04InUse=0
&JsFile05InUse=0
&JsFile06InUse=0
&JsFile07InUse=0
&JsFile08InUse=0
&JsFile09InUse=0
&JsFile10InUse=0
&JsFile11InUse=0
&JsFile12InUse=0
&JsFile13InUse=0
&JsFile14InUse=0
&JsFile15InUse=0
&JsFile16InUse=0
&JsFile17InUse=0
&JsFile18InUse=0
&JsFile19InUse=0

&JsFile00InUse=1
&JsFile00Name="dbl.mbn"
&JsFile00Pos=0x00000200
&JsFile00Offset=0x0

&JsFile01InUse=1
&JsFile01Name="osbl.mbn"
&JsFile01Pos=0x00000300
&JsFile01Offset=0x0

&JsFile02InUse=2
&JsFile02Name="boot.img"
&JsFile02Pos=0x00000401
&JsFile02Offset=0x0

&JsFile03InUse=1
&JsFile03Name="adsp.mbn"
&JsFile03Pos=0x00000402
&JsFile03Offset=0x0

&JsFile04InUse=2
&JsFile04Name="system.img.ext3"
&JsFile04Pos=0x00000403
&JsFile04Offset=0x0

&JsFile05InUse=2
&JsFile05Name="userdata.img.ext3"
&JsFile05Pos=0x00000404
&JsFile05Offset=0x0

&JsFile06InUse=2
&JsFile06Name="cda.img.ext3"
&JsFile06Pos=0x00000405
&JsFile06Offset=0x0

&JsFile07InUse=2
&JsFile07Name="hidden.img.ext3"
&JsFile07Pos=0x00000406
&JsFile07Offset=0x0

&JsFile08InUse=2
&JsFile08Name="NV_cust.mbn"
&JsFile08Pos=0x0000040c
&JsFile08Offset=0x0

ENDDO

I have attached the NvDefinition.xml As it was rather long.

I noticed that the nv_cust.mbn has "/nvm/prl_0" in it, don't know if that had anything to do with why my system was seeing prl as 8888, it may just be a stock setting. Sorry, I'm still getting familiar with how the android layers work.

Like I said, I'm shooting in the dark here. I just want to help get as many resources for our phone as possible. Cause I'll probably have the Triumph for a while, and would like to have a safety net to be able to rely on. Especially now that I am trying to build roms and other stuff. I usually just search before asking but I have read all I can find about nb0s and my time is running short with this old phone. So If anybody wants to help, I have all the files just pm me or ask and I'll pm you the links for what you need.

I am pretty sure where all the needed data is for this, and have extracted it all on disk. But I am not sure how to dumb the scripts down to make it work properly, or fully understand the function of some of the files.

 

[zoltic101]

Ok, so I am neck deep in this Magnum nb0, and setting up my dev station. Here is a list of files in the nb0,
FB0-318D-0-5019-A03.mlf
FB0-0-2380-MPRG7x30.hex
FB0-0-2380-NPRG7x30.hex
FB0-0-2380-partition.mbn
FB0-0-2380-partition.bin
FB0-0-2380-loadpt.cmm
FB0-0-2380-dbl.mbn
FB0-0-2380-osbl.mbn
FB0-0-2380-amss.mbn
FB0-0-2390-emmcboot.mbn
FB0-0-2380-adsp.mbn
FB0-0-2390-5017-boot.img
FB0-0-318D-5017-system.img.ext3
FB0-0-2390-0001-recovery.img
FB0-5019-008-splash.img
FB0G-0-3010-5019-hidden.img.ext3
FB0-0-2390-ftm.img
FB0-5019-008-NV_cust.mbn
FB0-5019-008-cda.img.ext3
FB0_5019_NV.xml
FB0_5019_sim_perso.xml
NvDefinition.xml
FB0-318D-0-5019-A03.md5

If anybody has any ideas about where to look for the changes it may have made or wants to check out the files let me know. I'm just sifting through things and comparing the other nb0's right now.

I accidently deleted all files on my moterola triumph and need help how can i download the listed files you posted if thers a link you can give me that would be great. and do i put the files on the phone storage or the sd card

 

[BSydz]

I accidently deleted all files on my moterola triumph and need help how can i download the listed files you posted if thers a link you can give me that would be great. and do i put the files on the phone storage or the sd card

It is all gonna depend on what you deleted and how you deleted it. Those files are not for the Triumph, they are for the Cherry Magnum HD. As many details as possible is what I need to help you.

 

[henslo]

[NEW UPADTE][ROM]01-JULY-12 | IceColdSandwich -8.1 - AOKP EDITION for FAMILLY FBO-FIH - xda-developers

Here's an icecold sandwich rom for the x6 says camera half works lo

 

[phatboyslim12]

hey i have a question,

so i see all these threads with gb or ics roms with non working hardware etc. the norm. but i also see alot of we need sc to get things running, but isnt this: CAYM_D_0_1010_2039_BP_2037_CDA_1024. the sourcecode that was supplied by motorola or mabe a dumbed down version, im just confussed???

 

[emmaa]

These phones have no FM radio chip. FM radio will _never_ work. You can't just magically program in FM support and things like deemphasis and stereo decoding.

 

[BSydz]

[NEW UPADTE][ROM]01-JULY-12 | IceColdSandwich -8.1 - AOKP EDITION for FAMILLY FBO-FIH - xda-developers

Here's an icecold sandwich rom for the x6 says camera half works lo

Thanks, I'll check it out, I am working on a few ROMs right now, so it might be a minute. It's crazy that this was my first endeavor in to the android system. But, I don't think it will work on our phone regularly because it uses the 2.6.35.7 kernel and we can't use that because there are files needed in the nb0 that get written to hidden partitions for it to work.

hey i have a question,

so i see all these threads with gb or ics roms with non working hardware etc. the norm. but i also see alot of we need sc to get things running, but isnt this: CAYM_D_0_1010_2039_BP_2037_CDA_1024. the sourcecode that was supplied by motorola or mabe a dumbed down version, im just confussed???

Thanks, that is the source for Froyo, drivers and basic framework of the entire system changed between Froyo and Gingerbread and again for ICS. So, the devs are rewriting stuff to work with our old drivers and system setup, that is why you hear the calls for source code. Find some source code for some of the other variants like the Sharp SH8188u and we might have a shot.

These phones have no FM radio chip. FM radio will _never_ work. You can't just magically program in FM support and things like deemphasis and stereo decoding.

Yes, our phones have a totally different Bluetooth chipset as the other variants and the FM is built into the BT chip. Something I figured out through all of my testing of the other variant ROMs. It is related to the kernel but their BT drivers work fine.

 

[phatboyslim12]

that makes alot of sense for me now thanks bsydes, has anybody tried contacting sharp for updated sc for the sh8.... i found the developer sharp site but unfortunatly i cannot read japanese, im trying to translate it to get more info but as of yet no luck...

 

[BSydz]

These phones have no FM radio chip. FM radio will _never_ work. You can't just magically program in FM support and things like deemphasis and stereo decoding.

I ran across this in the kernel source notes thought it was kind of interesting.

Team  : SW2-6-1
Issuer: Johnny Lin
Mark  : None
IssueKeys:[FB3.B-933]
Summary: DUT lose FM radio frequency and cannot scanning to new station after exit GPS satellites function

Do    : [Change]
            - Modify the reference counter at gps_sync to fix this issue.

        [Symptom]
            - None.

        [Cause]
            - The reference counter had wrong decision, and would off FM LNA when turn off GPS.

        [Solution]
            - Modify the reference counter.

        [Notes]
            - None.

        [Expose]
            - None.

Files :
        * ./android/kernel/drivers/input/misc/gps_sync.c

 

[phatboyslim12]

That made me laugh. If I recall correctly, the Triumph was released in July 2011. So, almost any Triumph out there should still be under warranty, except maybe reburbs, right?

I was thinking about writing a letter to Motorola that demanded a stock .nb0 because they put no fail safe in place to make sure that new updates were for the correct phone version. Maybe it would work.

I have to call and check on warranty of this class a replacement but in my experience, the refurbs original warranty carries over say original is up july 12, the refurb comes in now your good till say sept 12... happened to me!

Anywho, im waiting to find another triumph on cl real cheap like $40ish, and ima use it as a doner test phone for developement

 

[maximumhax]

I'm going to see if I can get someone with an ics rom installed with camera working on one of our brother phones to do a dd if=/dev/sdX of=phone.img in download mode so I can check it out..

 

[BSydz]

I'm going to see if I can get someone with an ics rom installed with camera working on one of our brother phones to do a dd if=/dev/sdX of=phone.img in download mode so I can check it out..

Just extract the nb0, it has all of the files that go onto the phone. I have a dd backup from when I flashed the nb0s. But after it is written it is encrypted on the partitions. If you have any questions just ask.

 

[maximumhax]

I don't run windows. So can't use nb0