Always bootloader screen

[Sendoa]

Hi, I've a vodefone v1240 (HTC Tornado), i've tried to flash wm6 flash to it... but... i haven't super cid unlock... the flash is ok but phone always star in muticolor screen (botloader screen), i've tried to flash a lot of flashes but always get invalid vendor id or "only upgrade"... i've tried too with TyphoonNbfTool to edit nbf and change vendor id.. but always get the same mensaje ("invalid vendor id" or "only upgrade")...

How can i recover my phone? :S

Thanks
Sendoa

[jm012a9749]

Determine your original CID first, to do this type:info 2 into mtty or teratermpro and paste the output in the thread

Phil

[anandoc]

Ahh, there you are ! Are you or duke_Stix still planning to cook some newer ROMs or remove bugs from the existing one ? We hardly see you guys around there days :)

[Sendoa]

i get this... what is the original CID? ¿?


info 2
GetDeviceInfo=0x00000002
+ SD Controller init
- SD Controller init
+StorageInit
***** user area size = 0x3CE40000 Bytes
HTCSVODA0504 㱍dHTCE
Cmd>

[jm012a9749]

@anandoc: I've been fairly busy lately what with Jury Service etc but I've got a beta version in progress :)

Changelog:
HTC Task Manager inc
HTC File Manager inc
Application Unlocked
Fixed WiFi
HTC Comm Manager inc
Removed Wireless Manager
Removed Debug Apps
Removed Marketplace
Removed Office
Removed Voice Command,
Removed Windows Update,
Added Bluetooth DUN support for TomTom compatibility
Added Bluetooth FTP protocol

Extra's (as a separate download)
Office
MMS (semi working)
HTC Clear Storage
Jeodek Java
Button fixes
xT9 (for those who prefer it over standard T9)
xT9 lang packs (split into separate languages)
TCPMP
wm5torage
VoIp

Localisations:
Polish
Czech
Russian

However at the moment I'm having issues with initflashfiles.dat, once these are sorted, it will probably be released the same day.

Back to the topic:
Ok, using typhoonnbftool v0.41 open up a tornado nbf (wm6 or official, it doesnt matter) and then edit the header data so that the Operator field reads:VODA0504 That is your original CID

Then save the nbf and flash it to your device :)

Phil

[Sendoa]

Hi, i've done but... always get a "only upgrade"... only let me to reflash wm6 flash.. but it always return to bootloader screen :S what am i doing wrong? :S

Thanks anyway
Sendoa

[jm012a9749]

Try adjusting the version numbers to something ridiculous like 99.99.99.99 as well

Phil

[anandoc]

@anandoc: I've been fairly busy lately what with Jury Service etc but I've got a beta version in progress :)


Phil

Hey Phil, Thanks very much for the update ! Your hard work is much appreciated here !!

[Straker]

I'm having the same problem as Sendoa. I flashed the WM6 ROM to my 8310but after 100% completion, the phone re-started in bootloader mode.

I can flash it again with the WM6 but the same thing happens each time (bootloader mode). I've tried to flash with several other ROMs but each time I get the "Invalid Vendor ID" error before flashing begins.

I've tried the Typhoonnbftool tool to change the header as suggested earlier in this thread but without any success. My CID is 'DNG_0501'. I'm still stuck in bootloader mode.

I'd appreciate any assistance.

Thanks,
Straker.

[Straker]

Sorted. Found another ROM (the fifth I've tried) that would flash without the 'Invalid Vendor' message. It let me get back to a standard WM5 setup.

[Sendoa]

Thanks to all :D

I flash it with a cingular flash with version changed to 79.79.79.79 and operator changed to VODA0504, and work again.. then i've unlock the cid and flash wm6 flash and it is working with it :D

Thanks again :D

[karhoe]

Wow, that's cool, means I can flash my phone to WM6 without voiding my warranty ( I still got 5 months left )

[bogdi1988]

Here, here they are:
cancer awareness ribbon (http://cancer-awareness-ribbon.bravehost.com)

ban this MOTHA F**&&

[flashhsalf]

Sorted. Found another ROM (the fifth I've tried) that would flash without the 'Invalid Vendor' message. It let me get back to a standard WM5 setup.

where did you get your flash from?

[fakbrenjeri]

Hi,
I have the new typhoonnbftool got it from sourceforge when i try to edit headers of a Imate rom to make it for xpa swisscom v1240 with the CID "VODA0505" i get only 1kb nbf file i try lots of thinks but no luck at all.

kind regards
Fakbrenjeri

[timwb]

I've used Typhoonnbftool to change header, but the resulting file is only ever 1kb or smaller! What am I doing wrong?

[timwb]

Straker,

Where did you get the rom that worked?

[tintome]

I've used Typhoonnbftool to change header, but the resulting file is only ever 1kb or smaller! What am I doing wrong?

use typhoon tools 0.4.1...

ftp://ftp.xda-developers.com/Uploads/Smartphone/Tornado/Shipped_Complete_Updates/I-mate

use the rom from here..

[gothicx]

I there!

I've tried everything that I could find here and still no luck...:-\

I've an SPV C600 and when I upload the Imate ROM it stays stuck on the BootLoader.

It only works if I upload the Orange Upgrade ROM...

I can't SuperCID it, since no app as worked till now...

What can I do?

Thank you! :)

[walram]

try this:

http://forum.xda-developers.com/showthread.php?t=285344

[java1991]

Hi.
I have the same problem like Sendoa. on my spv c600 starts only bootloader.When I instaling wm6 platinum edition I haven't super cid. Now when I connect phone to my PC on bootloader shows "usb" my pc "see" connection but tera term pro and mtty shows "disconnect". I don't know how I have to check what original cid i have. Please help
My spv c600 had original wm5 from orange PL
Sorry for my english:)

[AlainL]

Hi, I've a vodefone v1240 (HTC Tornado), i've tried to flash wm6 flash to it... but... i haven't super cid unlock... the flash is ok but phone always star in muticolor screen (botloader screen), i've tried to flash a lot of flashes but always get invalid vendor id or "only upgrade"... i've tried too with TyphoonNbfTool to edit nbf and change vendor id.. but always get the same mensaje ("invalid vendor id" or "only upgrade")...

How can i recover my phone? :S

Thanks
Sendoa
Hi all

Sorry to wake up this old thread, but I got exactly the same problem.
I followed the guide to upgrade to WM6, and did supercid stuff.
Then I flashed (flash was OK).
But it looks like there was a problem while superciding and now, phone is stuck in bootloader :(

When I type "info 2", here is what I get :
info 2
GetDeviceInfo=0x00000002
GetDeviceCID: Error - InitDecoder
HTCS ´í•6HTCE
Cmd>

As my device is a Swisscom XPA v1240 (vodafon), I tried to cook custom roms using Tornado kitchen (http://forum.xda-developers.com/showthread.php?t=619510) , vendor Id 0500 to 0506, but without success.
I also tried to find an original upgrade but there is nothing on Swisscom website and XDA's FTP section has no more roms.

Anyone have a hint ?
Thanks

[tobbbie]

First Question: are you stuck in Bootloader?
- if not then just SuperCID with lokiwiz
- if yes then:

Sad thing happened :-( - I see the following ways out:
1.) try to find Swisscom RUU (difficult, I believe there never was an official update from them)
2.) try and error for all CID in the ROM Builder, one should match
3.) learn about "Gold Card" method - did it myself with VOX but not Tornado.

In the meantime I have done SuperCID and SIM Unlock on the Tornado using the lokiwiz tooling - so you do not need the SPV Services to do it.

What did you use to SUperCID the device?

[AlainL]

First Question: are you stuck in Bootloader?
- if not then just SuperCID with lokiwiz
- if yes then:

Sad thing happened :-( - I see the following ways out:
1.) try to find Swisscom RUU (difficult, I believe there never was an official update from them)
2.) try and error for all CID in the ROM Builder, one should match
3.) learn about "Gold Card" method - did it myself with VOX but not Tornado.

In the meantime I have done SuperCID and SIM Unlock on the Tornado using the lokiwiz tooling - so you do not need the SPV Services to do it.

What did you use to SUperCID the device?

Hi

Yes, it's stuck in bootloader.
I tried the same method I did for C600.
note :
I did it a bit more than 1 month ago, so I don't remember all I have done.
I think it was just a bit after SPV service stop working (wich I wasn't aware of)
As I already did it for my C600, I already had the files on my HDD.
So I started with my files (use this method http://forum.xda-developers.com/showthread.php?t=542035).
But arrived to the SPV services part, it stopped.

Then I started with lokiwis method.
At step 7, I choose U [Unlock] then C [CID Unlock(SuperCID)]
After, I restarted the phone and the did the info 2 check.
If I remember well, I had the same result as in my previous post.
I just tought it must be OK ... and tried to flash a ROM.
I was thinking if phone is not superCID, flash would fail with invalid region error ...
that was not the case as flash was successful and i'm stuck in bootloader :(

About suggestion :
1) Can't find any update from Swisscom
2) Tried vendor Id 0500 to 0506, which should match all vodafon range (I think)
3) I will try it find info about it.

Question :
If I find a stock v1240, is there a way to dump rom and to flash it back to my v1240 ?

[tobbbie]

The easiest way to try out is to repack the ready NB file to the various "CID" .nbf output files by manually calling the nb2nbf_tornado.exe in the Tools directory of the kitchen. Give them different names (as the CID is) .nbf. This is done in a few minutes and the RUU takes any available .nbh file it finds in its directory. So offer them to RUU only one by one and restart the device for each try. I hope the nb2nbf_tornado.exe has the right CID selectable for the Swisscom ROM. Look at the file "CID.txt" in the tools directory, the most promising should be VODA0501 as CID as Swisscom and Vodafone obviously had an agreement back that time.

You could also try a stock ROM for the Vodafone V1240 which is available for the Austrian version and for the UK Version.

I am uploading them to mediafire and post the links when they are up. The VDAII_AKU2.exe is promising because the ROM update starts in German language and does not look operator specific.

German language: http://www.mediafire.com/file/jmjmykwjwmm/VDAII_AKU2.exe
United Kingdom: http://www.mediafire.com/file/zyz4nncrzwl/vf-uk_v1240_aku2_v254832_ship.exe

The RUU can be started normally, it will also upload to the device if it is in bootloader mode already.

[AlainL]

You could also try a stock ROM for the Vodafone V1240 which is available for the Austrian version and for the UK Version.

I am uploading them to mediafire and post the links when they are up. The VDAII_AKU2.exe is promising because the ROM update starts in German language and does not look operator specific.
Hi,
VDAII_AKU2.exe did solve my problem.
Now my phone is booting without any problem.
Thanks a lot, that was quick and efficient !
Back to play with your kitchen :)

[Edit]
I did again the lokwiz unlock method. All was successful.
But when checking if supecid is OK, i got the following result again :
info 2
GetDeviceInfo=0x00000002
GetDeviceCID: Error - InitDecoder
HTCS ´í•6HTCE
Cmd>

[tobbbie]

[Edit]
I did again the lokwiz unlock method. All was successful.
But when checking if supecid is OK, i got the following result again :
info 2
GetDeviceInfo=0x00000002
GetDeviceCID: Error - InitDecoder
HTCS ´í•6HTCE
Cmd>

I doubt that everything worked right. Which Lokiwiz version did you use (latest ZIP is 02b)?

- make sure the device is properly application unlocked (SDA Application Unlock must confirm "succesfully unlocked")
- confirm the execution of itsutils when asked at the prompt
- follow up if the itsutils that are called by the tools are generating the BIN files
- check if the writing of the calculated file back to the device via itsutils also runs ok.
- mind that you must call the option "C" CID-Unlock for the SuperCid and not "U" Unlock (which is for SIM-lock).

Which are the versions for IPL and SPL on the 3-color screen?

[AlainL]

Hi,

Thanks for response.
I finally got some time, and tried to follow exactly your guide http://forum.xda-developers.com/showthread.php?t=619510 (incl. ROM now: WM 6 updated Tornado kitchen with SDHC + 28/25MB total/avail storage)

After the lokiwiz part, I checked if supercid is OK with "info 2" and I still have exactly the same result as before :(

- make sure the device is properly application unlocked (SDA Application Unlock must confirm "succesfully unlocked")
OK
- confirm the execution of itsutils when asked at the prompt
OK
- follow up if the itsutils that are called by the tools are generating the BIN files
Two files created in "2 prepare for custom flash" directory : "cidunlocked.bin" and "lock_backup.bin". Both are 64ko
Compared with "winmerge", both are identical (stange, I think)
- check if the writing of the calculated file back to the device via itsutils also runs ok.
How do I check it ?
As there are no difference in files, I think it's OK
- mind that you must call the option "C" CID-Unlock for the SuperCid and not "U" Unlock (which is for SIM-lock).
OK

Note :
I got a stock v1240 (never flashed).
Result of "info 2" is
info 2
GetDeviceInfo=0x00000002
+ SD Controller init
- SD Controller init
+StorageInit
***** user area size = 0x1E3E0000 Bytes
HTCSVODA0505 㱍dHTCE


Is there anyway to dump full rom of ok's v1240 to the other one ?
Can I do the lokiwiz part on the stock v1240 and copy "cidunlocked.bin" to broken v1240 ?

Finally, just a note :
stock v1240 has no sim lock (as the other one).
But since I flashed roms you give in post 25, my sim card is rejected (try with a swisscom and a sunrise one).

[tobbbie]

If the .bin files are identical then the unlocking did not work - they have to be different. 32 byte from x'160 and the last 8 bytes at x'fff8. The unlocked CID shows the 8 bytes from x'170 from x'178 to be identical. This is what I have seen when comparing the 2 sets that I have backed up.

The line in the batchfile is:

Utils\wizardunlock.exe lock_backup.bin -c 11111111 -w cidunlocked.bin

You can try to SIM unlock the locked device, the batchfile will do the same framework but then call wizardunlock with different parameters.

Utils\wizardunlock.exe lock_backup.bin -nolock -w unlocked.bin

Mind that each step does a fresh "backup" of the same encrypted area and it would overwrite the previous. So you better put these backups aside for each step.

The tool itself seems to be a "compiled" perl script and the original author gave it a different name, as when you call without parameters it delivers:

Usage: typhooncidedit [-w outfile] [-lock/-nolock SIMLock Status] infile

This exe file was created with the evaluation version of Perl2Exe.
For more information visit http://www.indigostar.com
(The full version does not display this message with a 2 second delay.)
...



To dig deeper you have to google the perl script with that name. I found it at: http://www.xs4all.nl/~itsme/projects/xda/nbftools.html and it seems there is a newer version as a blank call delivers more info. You will also need perl installed along with the DES decryption routines. I have recently been pointed to a guide that deals with recovering from bootloader if you need to replace the SPL without the OS coming up. This references the tools you would need to go that path: http://wiki.xda-developers.com/index.php?pagename=Typhoon_downgrade_to_WM2003

The file I linked for the VDA1240 is for Austria and has a CID VODA0504 (which nb2nbf of the kitchen cannot create). You wrote the device is up again - info 2 still delivers decoding error of CID when doing "info 2"? Do you still have the very first lock_backup.bin?
When I understand the tools (the perl script) right then it alters just the CID area, so nothing should be lost until now.

Mind that the ROM does not change anything in the encrypted area - so if the device was SIMlocked it still is, if it was not it should also not be now. As written - try to SIM unlock it observing what the tools do.

To check if the decoding works, run the lokiwiz on the VODA0505 device, but if you want no risk, then edit the batch to not execute the pdocwrite commands.

Finally I am sure that the write of a different devices binfile will not work, it may put your device to become a real paperweight. The .bin files of my devices are totally different.

[AlainL]

Hi,

Thanks

You can try to SIM unlock the locked device, the batchfile will do the same framework but then call wizardunlock with different parameters.
Just tried to sim-unlock using U option in lokiwiz, and again, both bin files are identical.
To dig deeper you have to google the perl script with that name. I found it at: http://www.xs4all.nl/~itsme/projects/xda/nbftools.html and it seems there is a newer version as a blank call delivers more info. You will also need perl installed along with the DES decryption routines. I have recently been pointed to a guide that deals with recovering from bootloader if you need to replace the SPL without the OS coming up. This references the tools you would need to go that path: http://wiki.xda-developers.com/index.php?pagename=Typhoon_downgrade_to_WM2003
Will try when I got some time.
The file I linked for the VDA1240 is for Austria and has a CID VODA0504 (which nb2nbf of the kitchen cannot create). You wrote the device is up again - info 2 still delivers decoding error of CID when doing "info 2"? Do you still have the very first lock_backup.bin?
When I understand the tools (the perl script) right then it alters just the CID area, so nothing should be lost until now.
Unfortunatly, I don't have original file anymore.
And yes, info 2 still report an error.
To check if the decoding works, run the lokiwiz on the VODA0505 device, but if you want no risk, then edit the batch to not execute the pdocwrite commands.
Tried with the OK v1240, and files are different.
Then tried "for real", and v1240 is supercid.
Finally I am sure that the write of a different devices binfile will not work, it may put your device to become a real paperweight. The .bin files of my devices are totally different.
OK, I compared OK bin file to KO one, and, as you said, they are totally different.
So I will not try :)

[tobbbie]

Weird, something got broken in the scope of the first decode (or it was all the time already?).
As the tool (exe or perl) will overwrite the CID area with the SuperCID, encrypted with something device-specific, you still should have a chance to get the SuperCID written to it. Since also the SIM Unlock did not work, it seems that the tools cannot get the device specific part right from the dumped encrypted block. I still see a chance with the latest perl from itsme - would really like to know if you get it working finally.