how to dump the splashscreen without an official rom image ? - P3600 Software Upgrading

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).

Related

operator code killed?????

hello
i patched my ba several times but yesterday i got the failure message country code wrong.
i run getdivicedata and get this info:
P H 2 0 B W W E AT%CID?  5 . 0 3 . 0 2 0.0 1.13.00 % 4
how can i "repair/fix" my operator code
thanx
Your operator is 'T%CID?'
It is fine - same as mine
This proceedure is all over the forum.
This is what I do:
1) create a new file on ur desktop C drive - call it ROM
2) copy and paste NK.nbf and setoperator files to this new file
3) start - run - type 'cmd' - ok
4) type 'cd\'
5) type 'cd rom\'
6) type 'setoperator T%CID?' - enter
7) your NK.nbf file is now changed to your operator code
8) copy and paste NK.nbf back to your file
9) and flash your ROM using BaUpgradeUt
to flash your ROM:
1) press softrest+pwr+record button at the same time
2) you will see a white screen on your BA with 'SERIAL' letters on top
3) put BA in cradle and allow few seconds for the computer to pair with it
4) run BaUpgradeUt to flash your ROM
Should work
No dude, its not your operator code thats gone wrong...How did you set the operator in the first place? if you used the setoperator, did you enter the 8 digit alpha numeric code, ie. T-MOB001 or XGULA001 or whatever ur code is?
Well, what i would suggest is that you open the Setoperator.bat file using Notepad, make sure it is for you device and language. Then change the operator code using the normal procedure.
Now, use xda3nbftool to check that the values have been set correctly (hint: see how the commands display in DOS when you do the setoperator procedure)
Hopefuly this might help! Good Luck!
Yaantra
all my device data became scrambled during a rom update once, i just reflashed again, using the no_id tool and it went back to normal.

Wings SSPL and HardSPL

The attached SSPL and HardSPL are based on the Wings MFG SPL v0.91
- download the attached files
- REMOVE SIM and SD CARDS !!
- connect usb cable
- create a SPL backup by running spl-backup.bat from SPL-backup-kit (make sure you Wings is "application unlocked", run the attached SDA_ApplicationUnlock on PC)
- copy sspl-0.91-wings.exe to your device and run it
- after a few seconds "USB" appears on the display
- unplug and replug the usb cable
- if you only want to test the sspl try flashing the attached splash screen by running CustomRUU.exe from flash-splash-wings
- you can now flash the hardspl-0.91-wings.nbh by running CustomRUU.exe from flash-hardspl-wings
- after installing the uspl or hardspl you can flash any rom, cooked rom, radio or splash screen
Note:
The HardSPL is never overwritten which in case of flashing trouble is a great insurance. Should you want to flash another SPL or USPL you must run the SSPL.
Features:
SuperCID / Security Level=0
Does not check NBH signatures
Based on 0.91 MFG bootloader, rtask, fat2sd, sd2fat enabled
Accept any password
Model ID check only 4 chars
SPL overwrite DISABLED (to bypass, use sspl-0.91-wings.exe)
Bypasses "Task 2A" (this formats entire flash which renders your Wings into a brick, we don't want that)
Important:
Use at your own risk! I'm not responsible for any damage to your device caused by using the attached files.
Credits:
Pof, Des, Olipro and arc.
Donations:
Any donation amount is greatly appreciated
Note:
I have also attached the htcrt_devices.ini file for Darksimpson's htc romtool
forgive my stupid question, but what is sspl hardspl etc?
maestro123 said:
forgive my stupid question, but what is sspl hardspl etc?
Click to expand...
Click to collapse
An SSPL allows you to flash a HardSPL. After flashing HardSPL you'll be able to flash any Wings ROM to your device! This tool will then allow you to change the ROM language, flash cooked ROMs, custom splash screens, etc...
The SSPL is only the vehicle to flash a HardSPL. The HardSPL will replace your current SPL. Your current SPL will not allow you to flash any ROM, except official ones which match your ModelID and VendorID (aka CID)
Aye, I did it on my wings, and it worked perfectly (backup + splash screen)
I was scared when I had to accept the flashing
The splash screen is :
"SmartMobility
Test Only
Not For Sale"
It's my proof
EDIT:: How can I have my original splash screen back ?
Great... and working
What parameters should we use in htc rom tool? Same as with Kaiser? (Only WING*****?)
Thank you very much for testing the SSPL on Wings
I'm sure we will find your original splash screen back.
But please let us finish our main mission first
I will now upload the HardSPL in the my post. Please flash it on your device in the same way as the splash screen. It will be the last time that you will have to run the SSPL, because after flashing HardSPL your device is SuperCID
I will upload also Simpsons device.ini file which includes Wings device
Fantastic work!!!
I flashed the HardSPL succesfully
Hopefully, pre-production roms will have more free RAM as well as a working GPS !
el_lo said:
I flashed the HardSPL succesfully
Hopefully, pre-production roms will have more free RAM as well as a working GPS !
Click to expand...
Click to collapse
Okay just to prove it is the HardSpl, can you go in bootloader mode and check if on display on top left corner it says "0.91-Hard".
It would also be good if you can flash another splash screen. Should now work fine w/o running SSPL
Bootloader mode says "SPL-0.91 Hard"
Where can I find a another good splash screen please?
I have flashed the test splash succesfully but now (after restart) I have troubles launching programs (such as sspl - so I cant flash rardspl now, resco viewer...). Weird...
moneytoo said:
I have flashed the test splash succesfully but now (after restart) I have troubles launching programs (such as sspl - so I cant flash rardspl now, resco viewer...). Weird...
Click to expand...
Click to collapse
Well, sometimes a symptom after SPL change is that you have to do a hard reset. But sometimes it already helps to unplug and reinsert battery. Try that first.
el_lo said:
Bootloader mode says "SPL-0.91 Hard"
Where can I find a another good splash screen please?
Click to expand...
Click to collapse
Try to flash the attachment.
Replace Splash.nbh in flash-splash-wings by the attached ATT-test-Splash.nbh
Hard reseted, and flashed hardspl ok.
Flashing my own splashscreen without sspl was also succesful. Thanks
moneytoo said:
Hard reseted, and flashed hardspl ok.
Flashing my own splashscreen without sspl was also succesful. Thanks
Click to expand...
Click to collapse
After hard reset no longer probs running softwares?
Okay guys thanks for testing, now we will focus on dumping OS using fat2sd
jockyw2001 said:
After hard reset no longer probs running softwares?
Click to expand...
Click to collapse
I didnt have too much time so I hard reseted Wings again and restored backup. No problem then, everything runs
Excellent
I'm now dumping my FAT partition using the HardSPL command "fat2sd" (watch spelling!).
Of course you have to start up in bootloader mode (tri-color) for that and then connect with MTTY 1.42
You can call it with a parameter which can have the value 1,2,3 or 4
I think "fat2sd 3" is filemode, but since it is currently running and takes a long time I am not yet sure.
Ah it just finished
Here is a snapshot of the MTTY output
Code:
Cmd>fat2sd 3
Nand2SDReorder start...
Buildup mapping table now
dwTotalLength=0x484800, remain:0x8A09800
dwTotalLength=0x1111000, remain:0x7D7D000
dwTotalLength=0x1D9D800, remain:0x70F0800
dwTotalLength=0x2A2A000, remain:0x6464000
dwTotalLength=0x36B6800, remain:0x57D7800
dwTotalLength=0x4343000, remain:0x4B4B000
dwTotalLength=0x4FCF800, remain:0x3EBE800
dwTotalLength=0x5C5C000, remain:0x3232000
dwTotalLength=0x68E8800, remain:0x25A5800
dwTotalLength=0x7575000, remain:0x1919000
dwTotalLength=0x8201800, remain:0xC8C800
searching for boot sector, please wait a min
boot sector hit, start writing
remain 15147 sectors
remain 13867 sectors
remain 13355 sectors
remain 13099 sectors
remain 4139 sectors
remain 3883 sectors
remain 3627 sectors
remain 3371 sectors
remain 2859 sectors
remain 2347 sectors
remain 2091 sectors
remain 1579 sectors
remain 1323 sectors
Last Sector = 53803, encounter Last Logical Sector
Cmd>
Ok I have checked the SD after "fat2sd 3" and it wrote about 7.41MB in filemode (FAT32)
This is the contents of the rootdir. I think what it has dumped now are user files. Don't know how ROM cooks call this (user FAT partition??):
Code:
I:\>dir /a
Volume in drive I is TFAT
Volume Serial Number is 07E4-000A
Directory of I:\
01/09/2007 00:00 <DIR> Documents and Settings
01/09/2007 00:00 <DIR> Windows
01/09/2007 00:00 <DIR> Temp
03/01/2008 23:57 77,824 ReplStorVol
01/09/2007 00:00 <DIR> My Documents
01/09/2007 00:00 <DIR> Program Files
01/09/2007 00:00 <DIR> Application Data
01/09/2007 00:00 28,672 mxip_initdb.vol
03/01/2008 23:57 151,552 mxip_system.vol
03/01/2008 23:57 32,768 mxip_notify.vol
03/01/2008 23:57 53,248 mxip_lang.vol
01/09/2007 00:01 <DIR> ConnMgr
03/01/2008 23:57 172,032 cemail.vol
03/01/2008 23:57 385,024 pim.vol
8 File(s) 901,701 bytes
7 Dir(s) 133,283,840 bytes free
Will now try the other options.
Now running "fat2sd 4" This one takes a long time ~ 30 min
MTTY snapshot:
Code:
Cmd>fat2sd 4
Nand2SDReorder start...
Buildup mapping table now
dwTotalLength=0x484800, remain:0x8A09800
dwTotalLength=0x1111000, remain:0x7D7D000
dwTotalLength=0x1D9D800, remain:0x70F0800
dwTotalLength=0x2A2A000, remain:0x6464000
dwTotalLength=0x36B6800, remain:0x57D7800
dwTotalLength=0x4343000, remain:0x4B4B000
dwTotalLength=0x4FCF800, remain:0x3EBE800
dwTotalLength=0x5C5C000, remain:0x3232000
dwTotalLength=0x68E8800, remain:0x25A5800
dwTotalLength=0x7575000, remain:0x1919000
dwTotalLength=0x8201800, remain:0xC8C800
last sector = 53803
remain 15147 sectors
remain 14123 sectors
remain 13867 sectors
remain 13355 sectors
remain 13099 sectors
remain 4139 sectors
remain 3883 sectors
remain 3627 sectors
remain 3371 sectors
remain 2859 sectors
remain 2347 sectors
remain 1579 sectors
remain 1323 sectors
Last Sector = 53803, encounter Last Logical Sector
Cmd>
I analyzed the contents of the SD and it turns out a raw binary image is written on SD.
You must open the SD with for example the Winhex tool.
I think the data is the same as with "fat2sd 3", but now in raw mode.
Meanwhile I have studied the HardSPL again and I think I can trick it in dumping other partitions.
Thanks for all this work, jockyw2001. It is appreciated. I think that after we all have working GPS and 3G, we should make some serious donations to jockyw2001!
One question...how do you enter bootloader mode in the wings?
Not sure how to enter bootloader on Wings (I don't own it), but I think press and hold camera and then power on.
That worked. I was trying holding camera then plugging in USB. Thanks!
butzchan said:
Thanks for all this work, jockyw2001. It is appreciated. I think that after we all have working GPS and 3G, we should make some serious donations to jockyw2001!
Click to expand...
Click to collapse
Go on boys! Good work! I am prepared for next amount of donation

Radio ROM Dump

For getting GPS to work on Wings production models I believe it is necessary to also dump and reconstruct the radio ROM from a pre-prod model. We also need the radio dumped from a production model so that we can compare. The dump procedure is more complicated than dumping the OS and this is nothing for n00bs.
Requirements
- Qualcomm QPST software (search)
- QC diagnostics drivers (attached)
- HardSPL, only needed if you want to dump from a production model
Procedure
1. Restart in tri-color bootloader mode and start MTTY
2. Type: rtask a
3. Type: radata Note: What you type is not echoed on screen!!!! (after pressing enter ignore the error message "Parameter error")
4. Type: retuoR Note: What you type is not echoed on screen!!!!
5. Type: rtask c
After step 5. the device will enter QC diagnostics mode and it will install 3 new devices on your PC. Make sure you install the attached drivers. After driver installation look in device manager to find which COM port the QC diag driver uses.
6. Exit MTTY
7. Start "QPST Configuration" and check if the device is recognized and if it is in "download" mode
8. Start "QPST Memory Debug", click "Get Regions" and then "Save To"
9. Upload the dumped files on XDA Devs FTP server
Dump NV Items
The configuration of radio are stored as NV items. It is possible to dump these as foolows:
1. Restart in tri-color bootloader mode and start MTTY
2. Type: rtask c
3. Exit MTTY and start "QPST RF NV Item Manager" and select Read from Phone from the File menu followed by Write Only listed Items to .QCN file
4. Upload the dumped files on XDA Devs FTP server
Version numbers listed in Splash screen
Please note them down and post them here.
Note that this procedure cannot harm your device in any way.
Final note: once an official HTC RUU file is available for Wings we can flash the reconstructed OS and Radio to your device. A RUU will be available sooner or later.
Here is the link to Qualcomm QPST software 2.7.247
I tried everything you said above, and all went well (retuoR gave mean an invalid command, but I went further and everything was ok ).
I attached pictures of the task manager and QPST configuration.
The files you should have when you're done are : smi.bin ; ebi.bin ; load.cmm and whatever.qcn (this last file is the NV dump) . Is this correct Jockyw ? Will we have to reconstruct those to a .nbh file somehow?
Well done el_lo
Yes, with ebi.bin and smi.bin *and* an official RUU we can reconstruct a complete pre-prod ROM.
jockyw2001 said:
Well done el_lo
Yes, with ebi.bin and smi.bin *and* an official RUU we can reconstruct a complete pre-prod ROM.
Click to expand...
Click to collapse
An official RUU?
butzchan said:
An official RUU?
Click to expand...
Click to collapse
Yes
Can someone write down version numbers appearing in the splash screen please. Thx.
Mine: (pre-production with working GPS):
R 1.58.06.16
G 25.42.11.00H
D 0.91.00.00
In Bootloader I have:
WING200 MFG
SPL-0.91.1000
CPLD-7
After I have put it into bootloader and started MTTY, I type in:
rtask a
Then it seems to hang. It shows:
POWER OFF PMIC VREG_USB : SUCCESS!
C VREG_USB : SUCCESS!
But I cannot enter more strings now...
I just ignored rtask a and did all other things
It installed the drivers but I get the following screen:
http://forum.xda-developers.com/attachment.php?attachmentid=66378&stc=1&d=1200611892
Dumdidum said:
After I have put it into bootloader and started MTTY, I type in:
rtask a
Then it seems to hang. It shows:
POWER OFF PMIC VREG_USB : SUCCESS!
C VREG_USB : SUCCESS!
But I cannot enter more strings now...
Click to expand...
Click to collapse
Yes you can. You can type it, but you won't see what you type on screen!
Your screenshot is showing the device in QC Diag mode, but not in Dload mode.
Try again and follow my instructions.
Ok its now working... dumping in this moment...
you need the NV Items too?
Where can I upload it? which ftp-link?
Ok I have the smi.bin , ebi.bin and load.cmm
But cannot get the NV-File...
did exactly what you said:
1. Restart in tri-color bootloader mode and start MTTY
2. Type: rtask c
3. Exit MTTY and start "QPST RF NV Item Manager" and select Read from Phone from the File menu followed by Write Only listed Items to .QCN file
but while starting "Read from File" I get:
http://forum.xda-developers.com/attachment.php?attachmentid=66379&stc=1&d=1200614645
My fault... I had to choose the com-port in the settings first...
So I got all the files you want...
I have upload it here:
ftp://xda:[email protected]/Uploads/Wings/HTC_Wings_Preproduction_radio_Dump_dumdidum.zip
I hope you can do something good with it. I love the GPS on my Wings But the preproduction ROM is very unstable, so I'de love to get a stable ROM with GPS-Support. Although I fear that they have deactivated something on hardware, cause the producive wings are getting GPS data, just no fix... perhaps no antenna?
Dumdidum said:
My fault... I had to choose the com-port in the settings first...
So I got all the files you want...
I have upload it here:
ftp://xda:[email protected]/Uploads/Wings/HTC_Wings_Preproduction_radio_Dump_dumdidum.zip
I hope you can do something good with it. I love the GPS on my Wings But the preproduction ROM is very unstable, so I'de love to get a stable ROM with GPS-Support. Although I fear that they have deactivated something on hardware, cause the producive wings are getting GPS data, just no fix... perhaps no antenna?
Click to expand...
Click to collapse
Well done
Yes, I share your fears but let's see we can proof it using the "reconstruct pre-prod software" approach
Anyone with a prod model care to take a note of the version strings in the splash screen please? Please note them down and post them here.
Production
R 1.58.17.02
G 25.62.30.03H
D 1.31.00.00
But here's someone with different version... http://www.htcwiki.com/thread/1104370/HTC+S730+rom?t=anon
moneytoo said:
http://www.htcwiki.com/thread/1104370/HTC+S730+rom?t=anon
Click to expand...
Click to collapse
Thx for that link.
So we have:
GPS/3G Enabled S730:
R 1.58.06.16
G 25.42.11.00H
D 0.91.00.00
Production S730:
R 1.58.17.02
G 25.62.30.03H
D 1.31.408.0
and
R 1.58.17.02
G 25.62.30.03H
D 1.31.00.00
Someone should now dump radio rom of a prod model!
jockyw2001 said:
For getting GPS to work on Wings production models I believe it is necessary to also dump and reconstruct the radio ROM from a pre-prod model. We also need the radio dumped from a production model so that we can compare. The dump procedure is more complicated than dumping the OS and this is nothing for n00bs.
Procedure
1. Restart in tri-color bootloader mode and start MTTY
2. Type: rtask a
3. Type: radata Note: What you type is not echoed on screen!!!! (after pressing enter ignore the error message "Parameter error")
4. Type: retuoR Note: What you type is not echoed on screen!!!!
5. Type: rtask c
After step 5. the device will enter QC diagnostics mode and it will install 3 new devices on your PC. Make sure you install the attached drivers. After driver installation look in device manager to find which COM port the QC diag driver uses.
6. Exit MTTY
7. Start "QPST Configuration" and check if the device is recognized and if it is in "download" mode
8. Start "QPST Memory Debug", click "Get Regions" and then "Save To"
9. Upload the dumped files on XDA Devs FTP server
Dump NV Items
The configuration of radio are stored as NV items. It is possible to dump these as foolows:
1. Restart in tri-color bootloader mode and start MTTY
2. Type: rtask c
3. Exit MTTY and start "QPST RF NV Item Manager" and select Read from Phone from the File menu followed by Write Only listed Items to .QCN file
4. Upload the dumped files on XDA Devs FTP server
Click to expand...
Click to collapse
Hi, mate.
First of all, congratulations for the finding
I'm taking a chance for the procedure in Kaiser device, and love to know what are the steps after the dump process to get the NB file...
For what i understand, i need to dump files from the first process (9 steps) and after this dump the config files too (4 steps), am i right?
many thanks...
jcespi2005 said:
For what i understand, i need to dump files from the first process (9 steps) and after this dump the config files too (4 steps), am i right?
Click to expand...
Click to collapse
Compare smi.bin and ebi.bin with the radio.nb you flashed originally, that will give you the memory layout vs. the rom (.nb) layout. With that you can reconstruct a radio.nb from any radio dump.
Good luck!
I've uploaded the radio from a production model here : Radio Production Model
Here is the info from the production model in question :
R1.58.17.02
G25.62.30.03h
D1.31.00.00
Excellent, so now we only need an official RUU to sort it all out.
Maybe we won't need it to reconstruct the radio, I'm not yet sure about that one.

Software or hardware problem?

HTC TyTN II
1. Wirlles DOES NOT WORK
2. Sometimes the signal does not work
3. The camera DOES NOT WORK
4. disc does not work
5. World to the keyboard does not work
Is this a software problem?
Sorry on my bad english.
konzul said:
HTC TyTN II
1. Wirlles DOES NOT WORK
2. Sometimes the signal does not work
3. The camera DOES NOT WORK
4. disc does not work
5. World to the keyboard does not work
Is this a software problem?
Sorry on my bad english.
Click to expand...
Click to collapse
Back up you data and do a hard reset. If the problems persist, you can pretty mouch assume it is a hardware problem.
Hello
I have some problems with the storge.. i have it find with MTTY
when I start my phone it won't show the radio version ect. only the boot display will work for few seconds
and it's crashs! What can i do!? I have flash some roms.
it flashes and it go but it didn't start it.
HardSPL 1.0 from oli
Rom before crash: NoThrills_WM61_GER_V3
meylan said:
Hello
I have some problems with the storge.. i have it find with MTTY
when I start my phone it won't show the radio version ect. only the boot display will work for few seconds
and it's crashs! What can i do!? I have flash some roms.
it flashes and it go but it didn't start it.
HardSPL 1.0 from oli
Rom before crash: NoThrills_WM61_GER_V3
Click to expand...
Click to collapse
Try upgrading your hardspl to 33.4 or 3.29 ,1.0 is a WM 6.0 hardspl.
I have try to upgrade Hardspl many times. And it doesn't do it
so I have try to fix my storege yesterday and then it's broke
then i want start only the lcd goes green.
no screen anymore
task 28 55aa
Format start
Fill RSVD information for block 288 to 309
Storage start sector=0x8DC0, total sector=0x12500
Storage start block=588, total block=1172
Total Bad Block in CE: 0
Erase physical block from 876 to 2048
formatstorage Bad block found: 1603
Format end
Cmd>task 2a
Format ALL start
backup SPL OK
backup MISC configuration OK
SPL start start block=288, total block of CE=1760
ERASE block 1315 FAIL !!!
Write 0xFF start page=0x4800, total page=0x1B800
SPL version and MFG TAG are same, skip it.
restore SPL OK
restore MISC configuratoin OK
restore MFG configuratoin OK
Format ALL end
Cmd>task 32
Cmd>task 37
Invalid debug log data. Please check debug log raw data in addr 0xAE100000
Cmd>task 28
Format start
Fill RSVD information for block 288 to 309
TAG NOT FOUND !!! NOT CLEAR STORAGE !!!
Format end
Cmd>erase
HTCST ÚÈÒHTCE
Cmd>erase a0040000
HTCST ÚÈÒHTCE
Cmd>checksum
Cmd>checkimage
SPL CRC checksum = 0x5507A35A
CE is None.
ExtROM is None.
Cmd>info 8
--- 2K bytes sector version ---
DEVICE NAME=samsung_k9k2g08
DEVICE ID=0xAA
DEVICE MAKER ID=0xEC
PAGE SIZE=0x800
TOTAL PAGE SIZE=0x840
BLOCK COUNT=0x800
BLOCK PAGE=0x40
Checking block information
BLOCK 8 (0x8) is reversed block
BLOCK 1315 (0x523) is bad block
OS NOT FOUND !!!
Cmd>info 7
CPLD ID=0x8
Cmd>wdatah
Command error !!!
Cmd>rtask 0
Cmd>rtask 4
Cmd>checkimage
SPL CRC checksum = 0x5507A35A
CE is None.
ExtROM is None.
Cmd>password BsaD5SeoA
Pass.
HTCST ÚÈÒHTCE
Cmd>ruurun 0
Command error !!!
Cmd>ResetDevice
what i can do ? since last command it didn't start it
try a new radio and maybe it'l work
meylan said:
what i can do ? since last command it didn't start it
Click to expand...
Click to collapse
The reason it won't start anymore is because you ran Task 2a, which, unlike previous devices, formats EVERYTHING away, including the SPL and Windows Mobile. It essentially bricks the device, as it will not boot past OEMSBL (The radio bootloader, it comes first in boot order and loads the SPL, AFAIK). As soon as the device is reset after running the Task 2a command, the device will not boot as there is no OS bootloader, nor is there anything to boot. However, Jockyw2001 has created tools which may help to recover from a task 2a. A thread concerning Task 2a bricks can be found here. Best of luck with recovering your device.
DaveTheTytnIIGuy said:
The reason it won't start anymore is because you ran Task 2a, which, unlike previous devices, formats EVERYTHING away, including the SPL and Windows Mobile. It essentially bricks the device, as it will not boot past OEMSBL (The radio bootloader, it comes first in boot order and loads the SPL, AFAIK). As soon as the device is reset after running the Task 2a command, the device will not boot as there is no OS bootloader, nor is there anything to boot. However, Jockyw2001 has created tools which may help to recover from a task 2a. A thread concerning Task 2a bricks can be found here. Best of luck with recovering your device.
Click to expand...
Click to collapse
agh f*** thanks i didn't know that...
It's normal that the device isn't detected as qualm anymore?
it display me by connecting with Pc: "DATA LINK" or so
meylan said:
agh f*** thanks i didn't know that...
It's normal that the device isn't detected as qualm anymore?
it display me by connecting with Pc: "DATA LINK" or so
Click to expand...
Click to collapse
When I manually put my phone in OEMSBL, which is what yours should be in when you turn it on right now (the light is green but the screen stays black), windows detects it in Device Manager as: ZTE NMEA Device CDMA 1X, ZTE Diagnostics Interface 6000 CDMA 1X, ZTE USB Modem 6000 CDMA 1X. It should also detect the GPS and some other stuff, but I can't find those in Device manager.
mhh i used MTTY but i can't get in download mode
what commands should I write?
meylan said:
mhh i used MTTY but i can't get in download mode
what commands should I write?
Click to expand...
Click to collapse
This kind of stuff is too complicated for me, so I can't answer that myself. However, there are many threads that talk about task 2a resets and how to recover from them. Here, here, and here are all good places to start. But keep in mind that you should NOT try anything in these threads unless you have read everything, and are absolutely sure that the tool is for your specific situation. For example, DO NOT use the FrankenKaiser version in the third link if you don't have the Radio from Hell installed.
Alternatively, you could try the XDA IRC channel, or PM jockeyw2001.
Once again, best of luck repairing your brick.

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" )

Categories

Resources