Database Develop

DEAD QTEK 9090 after update to 1.40 - please help me.

Hello,
I try to update my Blue Angel to new 1.40 ROM from post “New Rom Qtec BA_WWE_14000_147_11200_Ship” I download type II ROM and converted to type I, then I change with tool xda3nbftool.exe nbf files to my setings:
xda3nbftool -x ms_.nbf ms_.nba 0x20040522
xda3nbftool -x nk.nbf nk.nba 0x20040521
xda3nbftool -x radio_.nbf radio_.nba 0x20040523
xda3nbftool -sd PH20B -sl WWE -so T-MOB009 ms_.nba
xda3nbftool -sd PH20B -sl WWE -so T-MOB009 nk.nba
xda3nbftool -sd PH20B -sl WWE -so T-MOB009 radio_.nba
xda3nbftool -c -u NK.nba
xda3nbftool -c -u ms_.nba
xda3nbftool -c -u Radio_.nba
xda3nbftool -x ms_.nba ms_.nbf 0x20040522
xda3nbftool -x nk.nba nk.nbf 0x20040521
xda3nbftool -x radio_.nba radio_.nbf 0x20040523
del *.nba
and I miss some warning message, then I run BaUpgradeUt.exe and update ROM successfully.
But when I restart after update I see:
No GSM
D 1.40.00 WWE
My Device Information is:
ROM version: 1.40.00 WWE
ROM date: 03/10/05
Radio version: [empty]
Protocol version: [empty]
ExtROM version: [empty]
Now I can't load any kind of ROM, always I see message:
ERROR 120: COUNTRY ID ERROR : No-No-42-42-42 (last three numbers change)
I already changed the RUU.conf ([CHECKCEID_TYPE]=1) - but before MDA switch to “USB 2.05” no COUNTRY ID ERROR and then setup making one more checking and display COUNTRY ID ERROR.
I try all of ROMS from ftp.xda-developers.com – 8( always error.
DeviceData.txt before wrong update:
PH20B 0 B WWE G T-MOB009 1.06.00 0 0 1.06.135 1.00.00 00.00
now my DeviceData.txt is as in attachment for this message
(I can connect with ActiveSync and run GetDeviceData.exe).
PH20B 0 B WWE 1.40.00 0 0
Please help me, I’m going crazy and spend on that problem last 48 hours, read and try everything on forum, wiki.

Go to the thread http://forum.xda-developers.com/viewtopic.php?t=16953
It is the Wiki: Help me! And yes I have read getting started
There are nice people who will help you surely!

mariusz said:
.... I download type II ROM and converted to type I, then I change with tool xda3nbftool.exe nbf ....
Click to expand...
Click to collapse
1. How did you convert a type II to a type I...?
2. Upgrading a type II to a device that does not allow it will give you the Country Code error.
Have you tried to reinstall your ORIGINAL ship ROM...? This should work. See the FAQ link in my sig for more prob solving (red one).

HappyGoat said:
mariusz said:
.... I download type II ROM and converted to type I, then I change with tool xda3nbftool.exe nbf ....
Click to expand...
Click to collapse
1. How did you convert a type II to a type I...?
2. Upgrading a type II to a device that does not allow it will give you the Country Code error.
Have you tried to reinstall your ORIGINAL ship ROM...? This should work. See the FAQ link in my sig for more prob solving (red one).
Click to expand...
Click to collapse
1. I don't convert type II to type I. I download converted type I from:
http://forum.xda-developers.com/viewtopic.php?t=20770
2. YES 8)
3. I don't know my ORIGINAL ship ROM. 8(
4. I read all of the FAQ at your link - nothing help, I can't find my qtek with T-MOB009.
I have now wrong DeviceData.txt and I think is the main problem. Can't set nbf files to settings from my DeviceData.txt file. 8(

You took a tpye I CE Rom and Type II radio and Ext Rom.
Flashed your device and got stuck, no point explain how or why you did it, lets move on.
1) Radio rom, go to wiki, download the radio 1.12 and the tools, fix it with fix.bat, run the upgrade.
This should give you 1.40 rom and radio 1.12
2) extended rom. You now need to get any extneded rom on your device so that you can then unlock it and copy the 1.40 one over.
So following the wiki getting started download the I-mate 1.62, extract and remove all *.nbf BUT the ms_.nbf, fix the file, run the upgrade.
This will now put a 1.22.162 EXt rom on your 1.40 rom with radio 1.12. Sorry you will have to live with the i-mate splash screens, you can fix that in another thread.
Now unlock, unhide that (also on wiki) delete all and replace it with the extracted 1.40 Ext Rom out of wiki (were else) avalible Extended roms. Lock and hide, hard reset and you should be up and running.
Oh Yes and please if it says extract or download what ever files please do it so that you dont get a version problem.
Have fun

MDAIIIUser said:
...
1) Radio rom, go to wiki, download the radio 1.12 and the tools, fix it with fix.bat, run the upgrade.
This should give you 1.40 rom and radio 1.12
Click to expand...
Click to collapse
U la laaaa...
I can't update radio ROM as in step by step instruction at wiki becouse I ALWAYS STOP on ID COUNTRY ERROR.
My DEVICEDATA.TXT is wrong. I don't have in this file some versions numbers and somthing like T-MOB009.
8(
If you know how I have set fix.bat for my DeviceData.txt please send more details.
DeviceData.txt :
PH20B 0 B WWE E 1.40.00 0 0

so try the Country Code error hack, its for type II but it might work on type I, You have a type I rom so the file is called HTCRUU.conf
http://wiki.xda-developers.com/index.php?pagename=BA_FAQ_Upgrade_Errors
What happens if you try to flash the I-mate 162 with out the fix.bat, its a clean Type I install and you don't have a Operator code to check against, its also a wwe rom.
La laaaa

MDAIIIUser said:
so try the Country Code error hack, its for type II but it might work on type I, You have a type I rom so the file is called HTCRUU.conf
http://wiki.xda-developers.com/index.php?pagename=BA_FAQ_Upgrade_Errors
What happens if you try to flash the I-mate 162 with out the fix.bat, its a clean Type I install and you don't have a Operator code to check against, its also a wwe rom.
La laaaa
Click to expand...
Click to collapse
1. Hack dosen't work.
2. When trying I-mate 162:
ERROR 120: COUNTRY ID ERROR: NO-No-12-12-12
8(

Hmmmm....ok, I think the problem is T-MOB009. Are you sure that was your original config? Was your operating system German to start out with (G)?
Here's an idea (perhaps):
Try the Type II Ship ROM (1.40) complete, but with country code hack.
You probably have tried that already, not sure.
Last alternative I can think of, is to put PDA in bootloader mode, and use mtty.exe to remove everything from your PDA.
See also itsme website for such rapi tools: http://www.xs4all.nl/~itsme/projects/xda/tools.html
I have never tried this procedure, so not sure if it will work for ya.
Perhaps my Boss MDAIIIUser has another great idea...he's good at this stuff...so await his reply.

HappyGoat said:
Hmmmm....ok, I think the problem is T-MOB009. Are you sure that was your original config? Was your operating system German to start out with (G)?
Here's an idea (perhaps):
Try the Type II Ship ROM (1.40) complete, but with country code hack.
You probably have tried that already, not sure.
Last alternative I can think of, is to put PDA in bootloader mode, and use mtty.exe to remove everything from your PDA.
See also itsme website for such rapi tools: http://www.xs4all.nl/~itsme/projects/xda/tools.html
I have never tried this procedure, so not sure if it will work for ya.
Perhaps my Boss MDAIIIUser has another great idea...he's good at this stuff...so await his reply.
Click to expand...
Click to collapse
1. Yes, I'm sure T-MOB009 is my ORYGINAL setting - 8)
2. Yes, I try type II with hack - it dosen't work.
3. Could you send more detail instruction how remove everythink from PDA using mtty.exe (link or description step by step)?! - now i have this tool but I don't know how I can I use it.
...and I waiting for replay from Boss and Master of Raster MDAIIUser.

Please confirm that you can connect to your device with acticve sync.
Thus that you are able to browse your documents on your device form your pc.
Next check your dont have that pc issue that is in the wiki getting startted last section of the thread.
I am going to tell you the same as what is in that thread so read it. before I tell you.
@ HappyGoat ,
I must be sick I turned very Green <Grin>,
so can't be your boss no more, will never get that respect now will I? (don't answer )

MDAIIIUser said:
Please confirm that you can connect to your device with acticve sync.
Thus that you are able to browse your documents on your device form your pc.
Next check your dont have that pc issue that is in the wiki getting startted last section of the thread.
I am going to tell you the same as what is in that thread so read it. before I tell you.
@ HappyGoat ,
I must be sick I turned very Green <Grin>,
so can't be your boss no more, will never get that respect now will I? (don't answer )
Click to expand...
Click to collapse
1. Yes I can connect via ActiveSync and browse file from desktop PC.
2. I don't know what are you asking for ?! PC issue, last section... hmm...
If you are asking for:
http://wiki.xda-developers.com/index.php?pagename=BA_GettingStarted
but I can't find anythink about pc issue at last section, please send it here.

Ok the thead started here.
http://forum.xda-developers.com/viewtopic.php?p=112036#112036
The porblem was that the guy could not get his radio to flash which is some what the same as you at the moment, his solution was to move to an other pc.
Anyway there are a few steps that I think you should try.
On the i-mate 162, did you use the upgrade tools from the extracted ship.exe and did you run the fix.bat.
PH20B 0 B WWE G T-MOB009 1.06.00 0 0 1.06.135 1.00.00 00.00
Click to expand...
Click to collapse
Were did the "G" come from should be "E" ?

Hrmm... I would attack this as follows (don't actually expect this to work, you've probably already even tried it, this is just the first thing I'd try).
Download this rom:
ftp://xda:[email protected]_139_10600_SHIP/Xda_IIs_v131139_upgrade.exe
Then do this, since we know that this method works with that rom:
Edit the RUU.conf file
Add the following line
[CHECKCEID_TYPE]=1
Save changes
Now run BaUpgradeUt.exe
It will say that it will upgrade to this version.
However when the device enters bootloader mode the upgrade util gives a country error. (Don't panic)
Simply restart BaUpgradeUt.exe while the device is still in it's cradle.
Now it will install without a country error.
I hope that this trick works with other BA devices and not only with the XDA IIs.
Hopefully it will install. I'm betting that the bad upgrade messed up your country code, so instead of getting the country code it expects (as you enter with xda3nbftool) it receives something else, or null characters. I'm hoping a rom change can fix this.

Hi Mariusz
Have You suceeded, if no and You have mda3 bought thru era
i can send You my version of rom which is working well without problem on my era mda3
its 1.40 rom 1.12 radio and 110 extrom
i've upgraded it from original era 1.20 rom
rgds
lukasz

TheLastOne said:
Hrmm... I would attack this as follows (don't actually expect this to work, you've probably already even tried it, this is just the first thing I'd try).
Download this rom:
ftp://xda:[email protected]_139_10600_SHIP/Xda_IIs_v131139_upgrade.exe
Then do this, since we know that this method works with that rom:
Edit the RUU.conf file
Add the following line
[CHECKCEID_TYPE]=1
Save changes
Now run BaUpgradeUt.exe
It will say that it will upgrade to this version.
However when the device enters bootloader mode the upgrade util gives a country error. (Don't panic)
Simply restart BaUpgradeUt.exe while the device is still in it's cradle.
Now it will install without a country error.
I hope that this trick works with other BA devices and not only with the XDA IIs.
Hopefully it will install. I'm betting that the bad upgrade messed up your country code, so instead of getting the country code it expects (as you enter with xda3nbftool) it receives something else, or null characters. I'm hoping a rom change can fix this.
Click to expand...
Click to collapse
Dosen't work... 8( I add [CHECKCEID_TYPE]=1 and run it one more after recive coutry id error.
My log file HTCRUU.log :
23:57:25:802 [msg] : Config Info : [667685],[1],[0].
23:57:30:409 [msg] : Current Not in CE Mode or in CE Mode but ActiveSync Not Connected.
23:57:34:835 [msg] : Current in BL Mode. Open Port : [\\.\WCEUSBSH001] OK.
23:57:36:988 [msg] : Get Device Backup ID.
23:57:36:988 [msg] : Device BL VER : [2.05 ] [].
23:57:36:988 [msg] : Device ID Is Incompatible.
23:57:36:988 [msg] : START UnInitialization !
23:57:36:988 [msg] : END UnInitialization !
23:57:37:008 [msg] : IsBL. BL : [1]
Now my sytuaition change some:
1. After change PC I try to install qtek ship 1.40 and update hold for 30min with no meesage.
2. Now My CE don't start only program mode (Serial/USB 2.05), hard reset don't help. ONLY PROGRAM MODE START.

lukjod said:
Hi Mariusz
Have You suceeded, if no and You have mda3 bought thru era
i can send You my version of rom which is working well without problem on my era mda3
its 1.40 rom 1.12 radio and 110 extrom
i've upgraded it from original era 1.20 rom
rgds
lukasz
Click to expand...
Click to collapse
Oooo, No I'm still in truble... If you can please put your ROM on FTP and send link. 8(((

Wait for any solution... 8(
8( still at same point... only bootloader, and always Country ID error...
Pleaseee, help... 8(

I am lost, Thelastone tells you to install the o2 rom, you say that you have installed the qtec.
So what have you done?
What rom are you trying?

MDAIIIUser said:
I am lost, Thelastone tells you to install the o2 rom, you say that you have installed the qtec.
So what have you done?
What rom are you trying?
Click to expand...
Click to collapse
I try everything from XDA-dev ftp, with all known hacks and without... still only COUNTRY ID ERROOR.
I try backup to SD card but it is impossible:
Add record error... 8(
I can't find any image file to send it to SD by ntrw.exe, try send .nbf files from shipped ROMs but after insert card into MDA III and restart, ROM restore from SD don’t start.

AT Commands

Hi folks,
can anybody check the output from mtty with:
USB> rtask b
[email protected]
for me and copy the content after 2 minutes (the nmea gps traffic) into a *.txt and send it to me or attach it to a reply? please, please....
Thank you
PS: You must have bootloader <= 1.04, otherwise the commands do not work.

Hi,
okay now, i think i understand why nobody answers me, because nobody have the bootloader 1.04, right?
But maybe anybody could check if it works with a sspl fake bootloader?
Thanks and please write also, if it does not work

Hello.
i try to help you but nothing happend when i write the command,of caurse with sspl. cause my bootloader is 1.7.
command error. both of trye's
so you nead a device with 1.4 b.l.

thanks ausdim!

how to dump the splashscreen without an official rom image ?

Hi all ,
at this day , it don't exist any official rom of the S300+ (trinity branded by SFR in France) and so , i can't dump the splashscreen .....
is exist a way to do that in my trinity ? (i have of course this rom inside)
cause soon ,this evening i hope , we will able to create his own extrom so with the splashscreen of the S300+ , i can create a FULL rom for anybody
Thanks for your answers positive or negative
I look at the Wiki and don't see anything about that ...
perhaps a cool french guy could create these not me i am too lazy for that but NO lazy to make the else things to do

you have to patch an SPL to allow you to rbmc at any address, i did this on hermes, not on trinity, but I guess should be very similar:
search for this hex string on the SPL: 0532A0E30E3883E3
Replace it for 0532A0E30000A0E1
Make sure the string is found only once, and load the resulting SPL.nb with SSPL.
Then you can do:
Code:
Cmd> task 32
Level = 0
Cmd> set 1e 1
Cmd> rbmc splash1.nb 500e0000 40000
Cmd> rbmc splash2.nb 50140000 40000

ok Pof ,
search for this hex string on the SPL: 0532A0E30E3883E3
can you give me some help about that ? i don't know where i have to begin

Use an hex editor

lol , that was not exactly what i mean

OK, I don't put links to anything so you make a bit of reading / research yourself... and is faster for me to write
Download HardSPL for trinity, use nbhextract to get SPL.nb from the NBH file.
By default the SPL will only allow you to "dump" a small region of the NAND flash chip, you want to dump the splash screen, so we have to patch it. To patch it, take any hex editor of your choice (radare, winhex...) and find this hexadecimal string: "0532A0E30E3883E3", then replace it for "0532A0E30000A0E1".
Now you have to load this SPL on your device using SSPL (read the SSPL readme.txt file, advanced instructions), you have to pass it as a parameter so you have two options: either create a .lnk file or use itsutils:
Code:
pput.exe patchedSPL.nb
pput.exe SSPL-TRIN.exe
prun.exe SSPL-TRIN.exe patchedSPL.nb
After prun, you have to quickly press the bootloader buttons, and you'll see the tri-color screen with your patched SPL
Disable activesync from now on
Connect to bootloader and issue the following commands:
Code:
Cmd> task 32
Level = 0
Cmd> set 1e 1
Cmd> rbmc splash1.nb 500e0000 40000
Cmd> rbmc splash2.nb 50140000 40000
mtty is very fishy with rbmc, so probably you will see no output, if this is the case you have 3 options:
Use unix command 'cu' (inside uucp tools), it works fine with rbmc.
Use mtty and capture the output with usb monitor, then use unix command 'xxd' to create the binary files.
Try with putty (I never tested, but probably works).
The output of the two rbmc commands are your first and second splash screens.

Thanks a lot Pof , you are very kind to did this !!!
but i have no success yet but i continue ...

@pof
what do you mean with "Use mtty and capture the output with usb monitor"
i think i did the right things before rbmc but like you said : i see no results i look at the options in mtty and i don't see "usb monitor"
can you help me (again) please ?
Regards
edit : is is the good result of the prun command ? ERROR: CreateProcess failed with Errorcode = 0
- Une connexion existante a d¹ Ûtre fermÚe par l'h¶te distant. (an exist connexion was closed by the host)

extenue said:
what do you mean with "Use mtty and capture the output with usb monitor"
Click to expand...
Click to collapse
ftp://xda:[email protected]/Hermes/Tools_and_Programs/usb-monitor237.exe
Capture in "complete" tab, export as ANSI text file.
extenue said:
edit : is is the good result of the prun command ? ERROR: CreateProcess failed with Errorcode = 0
Click to expand...
Click to collapse
yes, it's normal cos the SSPL kills the OS.

ok ! i finally success in export as ANSI text file the two files
i have not unix at home (i have only windows) , so before i ask my friends to create the binary files , how can i be sure that my dump is correct ?
Thanx again

extenue said:
how can i be sure that my dump is correct ?
Click to expand...
Click to collapse
The dump should have 262144 bytes (size of a splash screen).

can't format extRom..

hi people...
i tried to install a wm5 and a wm6 rom in a qtek 9090 but i can't format and merge ExtRom... i tried to use the rom unlocker found in the a77ila wm5 rom pack but i have a lot of error during unlock.. and when i try to format this error will show: FL_IOCTL_FORMAT_PHYSICAL_DRIVE failed!
i tried with xda-developer unlocker but an unable to find exe file will show..
and repart_doc still not work...
anyone can help me?
my device:
qtek 9090
SO WM2003SE ver. 4.21.1088 (Build 15045.2.6.0)
ROM : 1.40.04ITA
Radio: 1.12.00
Prot Ver: 1337.42
ExtRom ver: 1.40.153 ITA
tnx in advance... and sorry for my bad english

1. You cannot reformat extROM without unhiding and unlocking it first. Follow the procedure step by step. (remeber aboutsoft reset
2. Correct links to both tools as well as the procedure you can find on Wiki (http://wiki.xda-developers.com/index.php?pagename=Helmi - Installation)
3. Report effects.
3b. Your english is OK

here i am...
followed tutorial step by step...
1. installed the unlocker
2. launched unhide
3. soft reset
4. launched unlock
5. system displays a windows named debug showin ERROR: press OK
6.another system window named debug showin FL_IOCTL_BDTL_HW_PROTECTION press ok
7. another window saying a peripheral connected to system in not working press ok
8. a debug window saying extrom unlocked
9. soft reset
10. launched repart_doc
11. error window saying "FL_IOCTL_FORMAT_PHYSICAL_DRIVE failed" press ok
tried also without soft reset at point 9. same results..
i only see Ext_Rom in memory page of Setting but still remain full
------------------------------------------------------------------
Finally solved...
i don't know why but ita extrom can't be formatted...
so i used an escamotage... upgraded qtek9090 with this rom BA_TMNL_14200_119_11300_Ship
After used unlocker and repart_Doc and all goes on....
now go to upgrade to HELMI_BA_WM6_R0_Public

hiya
i cannot format my DOC too, i got the same error ,
i used TASK 28 under MTTY , but still i'm getting this error.
anyone can help with this problem ?

Hiya
I was searching XDA-DEVELOPERS website about 2 days to find a solution for this problem, I have an I-mate PDA2K, i used all EXTROM tools on this website like this:
1- Installed EXTROM_tools,
2- run UNHIDE ,
3- then run UNHIDE,
4- Soft Reset,
5- now i can see Extended_ROM on my file explorer, i can read it , and able to write on it ... copy paste ...
6- run REPART_DOC.exe on my device,
7- tried many sizes like 128kb, 1024, 2048, 512, 61000, .................
but on this step i always get the god damned FL_IOCTL_FORMAT_PHYSICAL_DRIVE failed,
i finally used Task 28 under MTTY but nothing happened, still have this problem,
No Wayyyyyy ! No wayyyyyyyyyy to repart my DOC size, .... noooooooooooo wayyyyyyyyyyyyyyyy
anyone going to help me plzzzzzzzzzzz ?

try it in this order...
1. downgrade to 2003
2. in WM2003 unlock... unhide... softreset
3. then repart_doc...
4. then upgrade to WM5/WM6
PS:
@Borbor...
hmm... i cannot see any part on your post that you tried to UNLOCK the extrom.
mastermoon DID. you need to unlock it first in order to modify it.
unhiding it just simply makes it visible to filemanagers.

SilverSamurai said:
try it in this order...
1. downgrade to 2003
2. in WM2003 unlock... unhide... softreset
3. then repart_doc...
4. then upgrade to WM5/WM6
PS:
@Borbor...
hmm... i cannot see any part on your post that you tried to UNLOCK the extrom.
mastermoon DID. you need to unlock it first in order to modify it.
unhiding it just simply makes it visible to filemanagers.
Click to expand...
Click to collapse
Hiya
I'm not a braincracked one, I'm a computer software engineer and i write CNC machines programs, so i don't need to someone to teach me instructions !!!! i did all, but i got FL_IOCTL_FORMAT_PHYSICAL_DRIVE failed. !
find me a good solution plz !

and i thought landmark's the only one who is bossy...
if you dont need instructions then what are you looking for in here??? duh!!!
you're both at the same level of intelligence... are we downgrading humans now?
P.S.
look at the end of the third post... that is solved.

Everybody is allowed to name themself software engineers nowadays?

Please people start behaving like grown up's we are no longer in kindergarten.
Please:
- listen to each other
- be prepared to be wrong
- try explaining your problem in another way
- but most of all don't try to solve your listening problems by yelling and cussing to each other.
TIA, Flar

HELP!! [Invalid Device ID]

Please Help Can't update OS.
and in ROM not have OS.
Thank for help.

Can´t connect via USB?

jorge_jomi said:
Can´t connect via USB?
Click to expand...
Click to collapse
can connect via USB.
But, can't update any rom.

Try MTTY : http://wiki.xda-developers.com/index.php?pagename=Trinity_BootLoader

bbk said:
Try MTTY : http://wiki.xda-developers.com/index.php?pagename=Trinity_BootLoader
Click to expand...
Click to collapse
I'm noob. I don't know what command to use.
in mtty command . please tell me step by step.
Thank you.

you can try :
-task 2A
-task 32 (response must le =0=
-checkimage
-info 8
If all ok, you can re-try to load ROM
If Rom upgrade don't work or if no :
-task 28
-task 7 1
-set 14 0
-task 8

bbk said:
you can try :
-task 2A
-task 32 (response must le =0=
-checkimage
-info 8
If all ok, you can re-try to load ROM
If Rom upgrade don't work or if no :
-task 28
-task 7 1
-set 14 0
-task 8
Click to expand...
Click to collapse
Cmd>task 2A
Cmd>task 32
Level = 0
Cmd>checkimage
IPL CRC checksum = 0x32441C0C
SPL CRC checksum = 0xF5505B9E
CE is None.
ExtROM is None.
Radio Image CRC checksum = 0x27B3C9FF
Cmd>
UPDATE Error
Cmd>task 28
Storage format start
Write Nand Success
dwBlockToWrite = 13
Can't find OS in flash!!!
Storage format success
Cmd>task 7 1
Cmd>set 14 0
Write Nand Success
HTCST ÚÈÒHTCE
Cmd>task 8
UPDATE Error
NOT WORK.
Thank FOR HELP!!

Yes but do you use your original rom ?

bbk said:
Yes but do you use your original rom ?
Click to expand...
Click to collapse
I use Original ROM.
RUU_Trinity_DOPODASIA_WWE_1.23.707.6_6275_1.35.00.11_108_Ship.exe
RUU_Trinity_DOPODASIA_WWE_3.00.707.17_6275_1.46.00.11_108_Ship.exe
RUU_Trinity_DOPODASIA_WWE_3.00.707.18_6275_1.46.30.11_108_Ship.exe
Don't have WORK

I think i wan't your original ROM, when you buy, could you get your First ROM

bbk said:
I think i wan't your original ROM, when you buy, could you get your First ROM
Click to expand...
Click to collapse
RUU_Trinity_DOPODASIA_WWE_1.23.707.6_6275_1.35.00. 11_108_Ship.exe
This ROM from shop.

Could you load a IPL ROM (just an IPL) ?
Could you load a SPL ROM (just a SPL) ?
You can try SPLxploit

I had exactly the same problem
I uploaded a mtty TRIN_HardSPL.nb and then flashed to the native WM5.

namwarn said:
RUU_Trinity_DOPODASIA_WWE_1.23.707.6_6275_1.35.00. 11_108_Ship.exe
This ROM from shop.
Click to expand...
Click to collapse
but u have an p3600 or p3600 i
?

Yes it is important!

mahav said:
Yes it is important!
Click to expand...
Click to collapse
yes in the photo i see u have load spl 3.03.0000 ?????

Again, I had a problem (invalide device id), I decided to fill it with a mtty. Nb file lined earlier. Only then was able to flash to the native WM5 (for me it RUU_Trinity_HTC_RUS_1.23.411.2_103_6275_1.38.00.11_108_Ship).
Also, it makes sense to check with the creator of the theme, the problem is his problem or not.

invalid device id
look here
http://forum.xda-developers.com/showthread.php?t=490681&page=7
post #66
and
here
http://forum.xda-developers.com/showthread.php?t=490681&page=9
post #81
if u enable lnb command can load trinxxx.nb
but u can dead wlan
is an risk !

To me at the time the error was nothing left to lose and I was aware of all the risk.
But I had to somehow come out of the situation, so took the risk and flashed.
And the author of threads to choose ...

you can use this tools
is modify splxploit-windows
if work
upgrade directly an rom contains ipl spl wm 5 original (u can use "trinity tutto originale" )