Does anyone experience the same difficulties with the new spl 2.03 like I do?
- I can't use the 'old' upgrade tools anymore. I keep getting an error 260 which is very frustrating as the new upgrade program does actually work, but gives me a CID error. Yep I don't have SuperCID.
- Any custom build rom with all Hermes rom cookers I tried will give me an 'image is corrupt' error when I use the new upgrade tools.
So it seems to me the spl password algorythm has been changed and the hashcalculation for the rom too
Now I'm left to debugging the new upgrade, in which I'm not to good at. Why am I doing this? I broke my Hermes during the upgrade and for warranty I really like to have the origal splash screens showing. Even updating the splash is't possible now. The SD method doesn't work either, apperently (and luckily for not bricking purposes) the bootloader seems to check that image too.
Any help is welcome in this.
Cheers, M
oltp said:
- I can't use the 'old' upgrade tools anymore. I keep getting an error 260 which is very frustrating as the new upgrade program does actually work, but gives me a CID error. Yep I don't have SuperCID.
Click to expand...
Click to collapse
You need to use the new RUU since SPL-1.11. Both old and new RUU are packaged in CustomRUU, which will unpack either one or other depending on the SPL version you have.
oltp said:
- Any custom build rom with all Hermes rom cookers I tried will give me an 'image is corrupt' error when I use the new upgrade tools.
Click to expand...
Click to collapse
You need a patched SPL in order to flash unsigned code. All custom builds are not properly signed with a valid HTC certificate.
oltp said:
So it seems to me the spl password algorythm has been changed and the hashcalculation for the rom too
Click to expand...
Click to collapse
Before the password was dynamic, algorithm explained in the wiki. In SPL versions 1.11 or newer the password is always: BsaD5SeoA
Don't know what you mean by "hashcalculation"... the CRC algorithm is still the same, in all bootloader versions.
oltp said:
I broke my Hermes during the upgrade and for warranty I really like to have the origal splash screens showing. Even updating the splash is't possible now. The SD method doesn't work either, apperently (and luckily for not bricking purposes) the bootloader seems to check that image too.
Click to expand...
Click to collapse
With a non-patched SPL you won't be able to flash anything that is not signed.
If your CID is ok (info 2 bootloader command shows a valid CID), you can unbrick it by flashing a signed (shipped / official) rom matching your device's CID.
If your CID/radio is br0ken (shows "No GSM" when booting), you won't be able to flash anything on it, your only hope is having a KITL enabled OS image.
i have problem i have tmobile vario 2 after trying upgrade the rom to wm6 phone stop on 17% and now is stock on the bootloader mode spl 2.03 and i can to anything i try flashing with difrend wersion of the software and nothing.help
@pof: thanks for your instant reply and pointing me to my black-outs. The password does work, but still the lnbs command gives me back: invalid command. Maybe that's because the device isn't unlocked. Just like to flash the spl 1.01MFG so I can at least try to work my way out of the bricked situation. Since KITL isn't enabled there isn't much hope, I know. I really tried all the wiki solutions.
Guess there are only two options left: repair centre and IMEI-check for JTAG flash.
Anyone knowing an other alternative, pls let me know
Cheers,
M
same problem here.. need help
Related
well... that current NBH will brick any Hard-SPL device since it will overwrite the IPL. I have 1.50 which I have given to ToddJG; this new version prevents the IPL being overwritten, so as long as you don't flash using SSPL, you would be safe.
is there any actual demand for it?
Oli are you refering to the NBH on "Full WM6 Pro. from Dopod (Test rom)"?
I am using SPL 1.50 Olipro - it works great.
Whether there is demand or not, I think you should disable IPL flashing in the flasher and then (assuming you feel like it) release an expert version (or maybe just an expert mode?) that will allow you to flash IPL. Even that I guess isn't even needed because we could just SSPL an upgraded IPL if we ever need to (right?)
To my (limited) knowledge, there is currently not any real reason to upgrade your IPL and if there are NBH's out there that are going to brick devices, I think it would be best to limit newbies abilitys to brick their devices (which hopefully means less aggrevation for you!)
Package HardSPL-1.50 with IPL-1.03 on a single NBH and publish it
I actually got stuck in BL mode when I tried to flash IPL 1.03 with SPL 1.40.Olipro installed and using Hard-SPL to flash. set 14 0 doesn't work anymore. I had to re-flash the OS to get it to work again.. A real ****ter as I had just finished setting it up nicely and didn't have a backup
Anyways, just to let you know....
I think that bocking IPL flashing would be a good thing. Like it was said earlier I would release it if it could stop users from bricking devices. I have been very happy with your contribution. It has saved me twice now. My little rug rats have pulled out the usb cable on my laptop to pda connection twice. If it had not been for you tool I would have a great paper wieght.
Thanks again.
Erik
LegolasTheElf said:
I actually got stuck in BL mode when I tried to flash IPL 1.03 with SPL 1.40.Olipro installed and using Hard-SPL to flash. set 14 0 doesn't work anymore. I had to re-flash the OS to get it to work again..
Click to expand...
Click to collapse
when this happens, you can just flash a splash screen to get it working again
pof said:
when this happens, you can just flash a splash screen to get it working again
Click to expand...
Click to collapse
Actually, I tried that.. It refused to work. Flashing the OS was the ONLY thing it would do.. It was odd. I tried to flash SPL again, it failed with a communication error. IPL again, the same. Splash screen, ditto. OS worked.
LegolasTheElf said:
Actually, I tried that.. It refused to work. Flashing the OS was the ONLY thing it would do.. It was odd. I tried to flash SPL again, it failed with a communication error. IPL again, the same. Splash screen, ditto. OS worked.
Click to expand...
Click to collapse
OK, A NEW SPL WILL BE RELEASED SHORTLY: SPL-2.10 - BASED ON A NEW HTC SPL, 2.02
Hey there,
got a "new" device by T-Mob and wanted to unlock it again. So I did, and unlocking worked so far. Now I want to flash the original shipped Rom by T-Mob Germany, but this doesn't work. Device changes to bootloader and than the computer tells me to check the cable. Tried to flash the rom with changing to bootloader and than start flashing, too, but same error. I tried to flash the unlocker-radio-rom again and that works.
Now I need a solution to flash original T-Mob shipped (WM5).
Any ideas?
Update: Flashing with Custom RUU and the nbh-file from original Rom works. But still no 'normal' flashing possible.
Is it possible to set back SPL 1.04 instead of 1.40.Olipro (by the way nice work Olipro, but not for warranty-reasons )
No idea anybody?
This issue has been documented to DEAT, the reason a standard RUU program doesnt work correctly is because there is a modified (and FAR SUPERIOR) bootloader on the device and the RUU doesnt understand what it is.
CustomRUU can detect it because olipro has built the support for the different SPL versions into it.
It is highly recommended that you update to HardSPLv7 (SPL version 2.10.olipro) as this protects your device against a load of possible ways to really damage your device.
By following the guides i have compiled on "how to safely flash WM5" and the various downgrade/upgrade guides on my site you might see how much better CustomRUU and nbh editting is.....also i recommend you read the wiki before going any further.
Thank you so much! Will try it tomorrow! I know, that the newer SPL-stuff is better, but I'm not so much into it, because I just run the WM5-Rom and wanted a SIM-Unlock. Because of warranty reasons (on 2nd device) I want to get back to the original SW SPL and so on. But I really think of installing WM6 when my device is completely back alive Thank you
Is there any chance to create hermes noid updater? I mean updater who will no check what CID lock is on device and skip this?
Probably completely misunderstood this from day 1 - but isn't that exactly what Olipro's Hard SPL v7 was designed for? I thought it was designed not to check which CID is on, or whether it's corrupt,etc?
Not exactly. Hard SPL is fake bootloader which run with every rom updater. And I'm talking about fake updater which will work with every bootloader (especialy not hard spl). Same as it was in old pda as himalaya (mda 2), blueangle (mda 3) etc.
Another day, another lesson learned. Thanks Ell82
Hi
I think the main problem is, not the CID check. The reason, why a fake bootloader like HardSPL or SSPL is used is, that the ROM images in .nbh format are digital signed and the booloader checked the valid signature.
HardSPL accepts formally signed code without a valid signature.
That's the reason, why all actual devices used this way.
I may be misunderstanding what you're saying here but...
SSPL will let you flash any ROM to your device. So will HardSPL.
HardSPL ofers a certain limited protection against temporary or permanent bricking.
If you're looking for the easiest way to flash you RUU file to your Hermes, the put in the same folder as 'Faria's RUU Wrapper' - attached to the first post on here: http://forum.xda-developers.com/showthread.php?t=316723 - and run exe using SSPL, but not to flash EXTROM or RADIO, just an 'OS-only' upgrade.
The reason I wasn't sure if I'd understood your question was that all cooked ROMs for a good while have come with an SSPL option.
The attached should do the trick though. It just loads SSPL and runs it which puts your device immediately into a kind of fake bootloader which ignores CID but leaves your actual botloader alone.
Look for the threads on SSPL and on OliPro's HardSPL to see the relative advatages/risks. OliPro's HardSPL is safer, SSPL easier in my opinion, but you should only really use SSPL to load OS or Splashscreens.
Yes, there is litle misunderstanding. I know there is SSPL and what it's do. The reason I was asking about updater with no id is there is a lot of bricked hermes stoping on windows mobile boot screen and not allowing any update on bootloader becosue their not cid unlocked and don't have hard spl. I have device like this, with bootloader 1.09 and looking for any possibility to flash it and unbrick it. There is no way to put sspl to device which not boot to os and which is not cid unlocked and have bootloader 1.09. Or maybe I missed something.
ell82 said:
Yes, there is litle misunderstanding. I know there is SSPL and what it's do. The reason I was asking about updater with no id is there is a lot of bricked hermes stoping on windows mobile boot screen and not allowing any update on bootloader becosue their not cid unlocked and don't have hard spl. I have device like this, with bootloader 1.09 and looking for any possibility to flash it and unbrick it. There is no way to put sspl to device which not boot to os and which is not cid unlocked and have bootloader 1.09. Or maybe I missed something.
Click to expand...
Click to collapse
I had SPL 1.09, corrupt CID, and stuck in windows screen after I mistakenly tried to flash a rom which had a lower radio bootloader, it bricked my device, and I didn't have KITL either...
I sent mine to imei-check. com and they did a JTAG flash which brought it back to life, and there is zero sign that this device was ever bricked.
At what cost? I think they have other way to unbrick devices then jtag.
ell82 said:
At what cost? I think they have other way to unbrick devices then jtag.
Click to expand...
Click to collapse
I got this from imei-check:
Prices for fixing:
If the device been unlocked before by imei-check.co.uk (we will check the database for the imei of your handset) price is 20 GBP
If the device been unlocked before by cracked/cloned solution and user confirm this, price is: 60 GBP
If the device been unlocked before by cracked/cloned solution and user lie about it (we can easy detect it) price is: 100 GBP
If the device never been unlocked price is: 40 GBP.
To this prices need to add the delivery costs.
Click to expand...
Click to collapse
You can email them at:
[email protected]
You can also try the methods here:
http://wiki.xda-developers.com/index.php?pagename=Hermes_Unbrick
but based on the data you gave, you have to send it for JTAG flash, or motherboard replacement.
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.
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?
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!
austinsnyc said:
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!
Click to expand...
Click to collapse
Had no problems for all those times..untill now 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.
marcoryn said:
Had no problems for all those times..untill now 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.
Click to expand...
Click to collapse
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.
todd_jg said:
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?
Click to expand...
Click to collapse
marcoryn said:
Where can I get CustomRUU,Could'nt find it on XDA. Is it the same as RUUwrapper and RUUupdate?
Click to expand...
Click to collapse
It may be the RUUWrapper you have, but you can get it at THIS THREAD 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
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?
Have you tried these things...
Code:
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.
todd_jg said:
Have you tried these things...
Click to expand...
Click to collapse
Yes, but without any succes
marcoryn said:
Yes, but without any succes
Click to expand...
Click to collapse
What were the specific errors for each method? I know you cannot get 260 with SD card flash method.
marcoryn said:
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.
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?
Click to expand...
Click to collapse
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").
fun_key said:
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").
Click to expand...
Click to collapse
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 there is no rom availeble.
What were the specific errors for each method? I know you cannot get 260 with SD card flash method.
Click to expand...
Click to collapse
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.
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
Dear all,
I am facing a problem here.
Had a hardware problem with the built in microphone and had to revert back to stock rom/splash screen/Original SPL in that order.
Had no problems reverting the ROM and the original screen back (just a couple of flashes), BUT when I tried to revert back the stock SPL here http://forum.xda-developers.com/attachment.php?attachmentid=110582&d=1220406410
I renamed the file to RAPHIMG.nbh, copied it to the root of the SD Card and entered bootloader mode and this is what it displays:
RAPH100
SPL-1.90.0000 (Which means a successful flash)
!!! AND THEN THIS !!!
"Upgrade ROM code error"
"Please try again"
This message is located in the last part of the green stripe in the tri color screen (bootloader)
It is then followed by the grey screen automatically which you are supposed to press volume key to start a flash process BUT it just HANGS at Loading...
unabling you to flash anything.
It's actually a friend's phone too so I guess you understand how hard it is....
Any help is appreciated
Thanks in advance
Possible image might be corrupt on sd card, grey screen is shown when it's trying to read sd, have you tried with sd removed? if you get to 2nd tricolor screen with sd removed i would use usb flash to restore it to working order..
Da_G said:
Possible image might be corrupt on sd card, grey screen is shown when it's trying to read sd, have you tried with sd removed? if you get to 2nd tricolor screen with sd removed i would use usb flash to restore it to working order..
Click to expand...
Click to collapse
Removed the SD and it stays at the tricolor screen with the spl version as mentioned in 1st post.
Also, displaying the Upgrade ROM code error, please try again message
The mode is currently serial
What can I do from here?
fireblade63 said:
Dear all,
I am facing a problem here.
Had a hardware problem with the built in microphone and had to revert back to stock rom/splash screen/Original SPL in that order.
Had no problems reverting the ROM and the original screen back (just a couple of flashes), BUT when I tried to revert back the stock SPL here http://forum.xda-developers.com/attachment.php?attachmentid=110582&d=1220406410
I renamed the file to RAPHIMG.nbh, copied it to the root of the SD Card and entered bootloader mode and this is what it displays:
RAPH100
SPL-1.90.0000 (Which means a successful flash)
!!! AND THEN THIS !!!
"Upgrade ROM code error"
"Please try again"
This message is located in the last part of the green stripe in the tri color screen (bootloader)
It is then followed by the grey screen automatically which you are supposed to press volume key to start a flash process BUT it just HANGS at Loading...
unabling you to flash anything.
It's actually a friend's phone too so I guess you understand how hard it is....
Any help is appreciated
Thanks in advance
Click to expand...
Click to collapse
You cannot flash an SPL from the bootloader. You need to use SSPL. The directions can be found in the HardSPL thread.
NotATreoFan said:
You cannot flash an SPL from the bootloader. You need to use SSPL. The directions can be found in the HardSPL thread.
Click to expand...
Click to collapse
Hey man, thx for stopping by..
If I understand correctly, SSPL runs through the device which is stuck at bootloader currently... or am I hopefully wrong??
If you're at the tricolor screen and it reads serial, that should be fine.. plug in usb and it should switch to usb.. then flash a stock carrier rom through usb.. that should get you up and running and you can then run sspl and flash your spl
Da_G said:
If you're at the tricolor screen and it reads serial, that should be fine.. plug in usb and it should switch to usb.. then flash a stock carrier rom through usb.. that should get you up and running and you can then run sspl and flash your spl
Click to expand...
Click to collapse
Keep in mind im currently on stock SPL, do u think flashing the stock ROM is ok?
That's exactly why i suggested stock ROM, stock SPL will only accept stock ROM's (it will overwrite the spl too so make sure the stock rom you are using is the right one)
dude....i hate to say this...butyou might be s.o.l. at this point. i did the same to my fuze not too long ago... tryingto flash anything to the phone just locks it up.i was lucky enough to bs my way through an att guy to get me a new one (was still under the 30 day warranty).
Da_G said:
That's exactly why i suggested stock ROM, stock SPL will only accept stock ROM's (it will overwrite the spl too so make sure the stock rom you are using is the right one)
Click to expand...
Click to collapse
That's wt Im trying now, tried to flash 2 ROMs already and stops at 2% saying Invalid Vendor ID
I gess I'm using wrong shipped roms till now
fireblade63 said:
That's wt Im trying now, tried to flash 2 ROMs already and stops at 2% saying Invalid Vendor ID
I gess I'm using wrong shipped roms till now
Click to expand...
Click to collapse
I had the same problem as you and could not flash any rom, Always get Invalid vendor ID.
You need the right Stock Rom to flash and in my case in the middleeast, the Stock Rom is so far only available in at HTC.
I had to take the phone to HTC Service Center and they flashed the correct Stock Rom and charged me as they did it out of warranty.
Regards
fireblade63 said:
That's wt Im trying now, tried to flash 2 ROMs already and stops at 2% saying Invalid Vendor ID
I gess I'm using wrong shipped roms till now
Click to expand...
Click to collapse
Sorry about my last post... I misread your issue.
If you flashed the stock 1.90 SPL from the HardSPL thread, then you will need to ask Olipro (or cmonex) which WWE ROM it originated from. That ROM is the ONLY one your phone will accept.
The steps in reverting SPL for warranty / return state to always do the ROM first so that you do not run into this problem. I had the same issue when I was testing a US 3G Diamond I bought from Best Buy (to become acclimated to TF3D prior to the Fuze's release). I restored the SPL first, and then couldn't get Dutty's ROM off the phone, because I could not locate a downloadable version of the WWE ROM that phone came with. [Luckily, Best Buy Mobile's employees in KOP, PA aren't too clever, and I was able to convince them that the phone came that way. ]
NotATreoFan said:
Sorry about my last post... I misread your issue.
If you flashed the stock 1.90 SPL from the HardSPL thread, then you will need to ask Olipro (or cmonex) which WWE ROM it originated from. That ROM is the ONLY one your phone will accept.
The steps in reverting SPL for warranty / return state to always do the ROM first so that you do not run into this problem. I had the same issue when I was testing a US 3G Diamond I bought from Best Buy (to become acclimated to TF3D prior to the Fuze's release). I restored the SPL first, and then couldn't get Dutty's ROM off the phone, because I could not locate a downloadable version of the WWE ROM that phone came with. [Luckily, Best Buy Mobile's employees in KOP, PA aren't too clever, and I was able to convince them that the phone came that way. ]
Click to expand...
Click to collapse
Hmm, then I need to know from which ROM the SPL originated and then flash it.
Thing is, some of the shipped roms available at wiki are just nbh files..
I tried flashing with the wrapper exe and the RaphaelCustomRUU.exe and still all roms I've downloaded don't seem to work.
It's a RAPH100 untied to a network.
fireblade63 said:
Hmm, then I need to know from which ROM the SPL originated and then flash it.
Thing is, some of the shipped roms available at wiki are just nbh files..
I tried flashing with the wrapper exe and the RaphaelCustomRUU.exe and still all roms I've downloaded don't seem to work.
It's a RAPH100 untied to a network.
Click to expand...
Click to collapse
Post in the HardSPL thread asking which ROM the SPL originated from. Once you know that, you can download the appropriate ROM from the Wiki.
NotATreoFan said:
Sorry about my last post... I misread your issue.
If you flashed the stock 1.90 SPL from the HardSPL thread, then you will need to ask Olipro (or cmonex) which WWE ROM it originated from. That ROM is the ONLY one your phone will accept.
The steps in reverting SPL for warranty / return state to always do the ROM first so that you do not run into this problem. I had the same issue when I was testing a US 3G Diamond I bought from Best Buy (to become acclimated to TF3D prior to the Fuze's release). I restored the SPL first, and then couldn't get Dutty's ROM off the phone, because I could not locate a downloadable version of the WWE ROM that phone came with. [Luckily, Best Buy Mobile's employees in KOP, PA aren't too clever, and I was able to convince them that the phone came that way. ]
Click to expand...
Click to collapse
SPL has nothing to do with the Invalid Vendor ID Error, It is the CID. In another word you can flash SPL 1.95 and still can not flash the AT Rom 1.95.502.5 because the CID is different.
Regards
ViperBJK's QMAT features GoldCard generator for current HTC devices that can force RUU to bypass CID check.
Do you know what is the CID of your device?
shafez said:
SPL has nothing to do with the Invalid Vendor ID Error, It is the CID. In another word you can flash SPL 1.95 and still can not flash the AT Rom 1.95.502.5 because the CID is different.
Regards
Click to expand...
Click to collapse
The CID is determind by the SPL.
Look up the error code posted... everything points to HardSPL. Back in my Wizard days, HardSPL did not exist, and we just did a CID unlocking. This is not the case with newer devices.
All ROMs are not created equal. Each WWE ROM checks for specific information within the SPL, and if it doesn't find what it's expecting, fail...
stepw said:
ViperBJK's QMAT features GoldCard generator for current HTC devices that can force RUU to bypass CID check.
Do you know what is the CID of your device?
Click to expand...
Click to collapse
I'm not sure
Where can I know that?
@NotATreoFan && Shafez,
I remember from TyTNII day when Shafez suggested extracting 3.29 and 28 SPLs from the newer shipped 6.1's for a better responsive device.
We could extract and build with htc rom tool if I remember the name of the tool correctly.
Do we have a tool as such compatible with TP? (agreeing with NotATreoFan here)
@Shafez,
Since you think it is not SPL and it is a CID issue, what can I do about it?
Sending it to SVC for repair out of warranty is an option but I'd like to leave it as my last.
Did they provide the ROM or they flashed it for you?
Were u able to make raw files out of it for future use or any1 else has it?
Thx guys and keep the help coming
fireblade63 said:
@NotATreoFan && Shafez,
I remember from TyTNII day when Shafez suggested extracting 3.29 and 28 SPLs from the newer shipped 6.1's for a better responsive device.
We could extract and build with htc rom tool if I remember the name of the tool correctly.
Do we have a tool as such compatible with TP? (agreeing with NotATreoFan here)
@Shafez,
Since you think it is not SPL and it is a CID issue, what can I do about it?
Sending it to SVC for repair out of warranty is an option but I'd like to leave it as my last.
Did they provide the ROM or they flashed it for you?
Were u able to make raw files out of it for future use or any1 else has it?
Thx guys and keep the help coming
Click to expand...
Click to collapse
Since you cannot get past the bootloader, your only option is to find the WWE ROM that matches the SPL you flashed. Even though the HTC ROM Tool "signs" the NBH file, it still won't fool the stock bootloader... if it did, we wouldn't need HardSPL.