PDA

View Full Version : Tricolor and invalid vendor ID


marcoryn
29th September 2007, 06:15 PM
After flashing my locked T-mob vario dutch (for the 20st time) it now is bricked.
I tried to flash the Fun_Key_rom.
Hermes is stuck on the HTC logo 1pl-1.01 and SPL-2.03 not Super CID. (because of the warranty). I followed the thread about unbricking, but untill now no result.
I can flash it with Ruu.exe (and ruuwrapper.exe) the option 2.02/2.10 works for me untill 1% and then I get a invallid vendor ID. :confused:
I read the thread over and over again, but didn't seem to get how to unbrick it. Do I need to have a special rom? or other software?

austinsnyc
29th September 2007, 06:22 PM
no you need to flash Hard SPL on your phone right now!!! you can always unflash the HardSPL at a later date but you where just asking for a brick by not flashing HardSPL in the first place!

marcoryn
29th September 2007, 07:33 PM
no you need to flash Hard SPL on your phone right now!!! you can always unflash the HardSPL at a later date but you where just asking for a brick by not flashing HardSPL in the first place!

Had no problems for all those times..untill now :mad: I know it was stupid.

Trying to flash Hard SPL I got a 260 update error on the HardSPL v7. I also tried it with another upgrader and got an 270 error. It installed until 100% but no result.

todd_jg
29th September 2007, 08:23 PM
Had no problems for all those times..untill now :mad: I know it was stupid.

Trying to flash Hard SPL I got a 260 update error on the HardSPL v7. I also tried it with another upgrader and got an 270 error. It installed until 100% but no result.

Yes, you need to use CustomRUU to avoid the invalid vendor ID. It bypasses the CID check. That is why it works, even though you are not superCID.

Regarding the 260 error, try a couple things.
If you can, try SD flashing.
If you cannot do SD method, try using "manual bootloader" method:
- Put phone in bootloader mode
- NOW attach to USB lead
- Start CustomRUU
If that does not work, try taking the battery out for a while (5 minutes) and then try again.

marcoryn
30th September 2007, 11:47 AM
[QUOTE=todd_jg;1547673]Yes, you need to use CustomRUU to avoid the invalid vendor ID. It bypasses the CID check. That is why it works, even though you are not superCID.
QUOTE]

Where can I get CustomRUU,Could'nt find it on XDA. Is it the same as RUUwrapper and RUUupdate?

todd_jg
30th September 2007, 02:53 PM
Where can I get CustomRUU,Could'nt find it on XDA. Is it the same as RUUwrapper and RUUupdate?

It may be the RUUWrapper you have, but you can get it at THIS THREAD (http://forum.xda-developers.com/showthread.php?t=298737) You may already have used it though, on the one that did not give you the invalid vendor error. Use it with the nbh file. If you only have an exe, then you can use winrar to take it apart into 2 files - the ruu file (the updater) and the nbh (the ROM itself). Once you are using the right CustomRUU, try the things I mentioned in my previous post.

Other things to be sure of...
If you are using Vista, check with MrVanx guides to see what you need to do.
You must have...
ActiveSync 4.5
.NET framework 2 or higher

marcoryn
30th September 2007, 04:52 PM
Thanks for ur help. Really appr. it.

When I use the CustomRuu on any nbh file I'll get the Update error (260).
If I use the same nbh file on the RUU.exe file and I choose the 2.02/2.10 option it flashes my mobile till 1%. Then I get error 274 Invalid Vendor ID.

I see on the forum a lot of people bricked there Tytn on SPL 2.03.

Is Mr. Olipro having an solution? ;)

todd_jg
30th September 2007, 10:42 PM
Have you tried these things...


Regarding the 260 error, try a couple things.
If you can, try SD flashing.
If you cannot do SD method, try using "manual bootloader" method:
- Put phone in bootloader mode
- NOW attach to USB lead
- Start CustomRUU
If that does not work, try taking the battery out for a while (5 minutes) and then try again.

marcoryn
1st October 2007, 02:05 PM
Have you tried these things...



Yes, but without any succes :mad:

todd_jg
1st October 2007, 06:30 PM
Yes, but without any succes :mad:

What were the specific errors for each method? I know you cannot get 260 with SD card flash method.

fun_key
1st October 2007, 07:43 PM
After flashing my locked T-mob vario dutch (for the 20st time) it now is bricked.
I tried to flash the Fun_Key_rom.
Hermes is stuck on the HTC logo 1pl-1.01 and SPL-2.03 not Super CID. (because of the warranty). I followed the thread about unbricking, but untill now no result.
I can flash it with Ruu.exe (and ruuwrapper.exe) the option 2.02/2.10 works for me untill 1% and then I get a invallid vendor ID. :confused:
I read the thread over and over again, but didn't seem to get how to unbrick it. Do I need to have a special rom? or other software?

You are in a quite bad situation. I am not well aware about all the new ways to backup bricked hermes; but as far as I know the only remaining possibility for you is to flash your device using the default flasher AND a rom matching your CID.

Hopefully tmobile dutch released an updated WM5 release for your phone. You should be able to flash it, setup hardspl, and flash anything you want; but in a safe way this time.

There is maybe a way to tweak the CID of cooked ROM, but don't know anything about it (and there will certainly be signing issues).

In order to get your CID and see if something matching it is available at the wiki read the wiki about mtty (as far as I remember it is something like "type 2").

marcoryn
1st October 2007, 11:01 PM
You are in a quite bad situation. I am not well aware about all the new ways to backup bricked hermes; but as far as I know the only remaining possibility for you is to flash your device using the default flasher AND a rom matching your CID.

Hopefully tmobile dutch released an updated WM5 release for your phone. You should be able to flash it, setup hardspl, and flash anything you want; but in a safe way this time.

There is maybe a way to tweak the CID of cooked ROM, but don't know anything about it (and there will certainly be signing issues).

In order to get your CID and see if something matching it is available at the wiki read the wiki about mtty (as far as I remember it is something like "type 2").

Hope Olipro will release a CustomRuu version where 2.03 can be flashed. Lot of people have probs with 2.03. Dutch T-Mob haven't released anything :mad: there is no rom availeble.

What were the specific errors for each method? I know you cannot get 260 with SD card flash method.


I got another error on cooked roms (26008 or something) and when I put an org. carrier rom on the card it says checking but will not install because its not a legal rom. :mad:

Because of a hardware error I had to return my Tytn today..while it still is bricked. Hope Tmob will be kind and fix this for me along with the hardware issue :(