Hi,
I've been trying to flash my hermes via the SD flashing, however when i try to my hermes briefly flashes on the screen "no image file" then it goes back to the tri colour screen.
Has anyone else had this trouble? Anybody got any ideas?
Cheers!
Aderrington
Have you read the Wiki page on this?
What CID is your device?? also which rom are you trying to flash??
Yep read that page, and most of the wiki and most of the forum, sadly i can't find anything about this, (don't think many people upgrade this way)
Trying to flash the latest 1.35 .......... Rom
As for my CID...well it was unlocked thanks to pof's unlocker, however while upgrading via the normal way it is now (according to info 2) HTCSF kE0
So i went through using hex editor and changed the (what i thought was) CID to what my hermes CID is.
But the reason i posted on here was mainly to see if anyone else had tried upgrading like this and had the same (brief) message???
But if anyone else has attempted editing the nbh file, and has any results, please can you advise at all???
Cheers
aderrington said:
As for my CID... it is now (according to info 2) HTCSF kE0
Click to expand...
Click to collapse
Looks like your CID is corrupted. Does it show "No Gsm" when booting? can you see your IMEI, radio & protocol versions in setings - system - device information?
aderrington said:
So i went through using hex editor and changed the (what i thought was) CID to what my hermes CID is.
[...]
But if anyone else has attempted editing the nbh file, and has any results, please can you advise at all???
Click to expand...
Click to collapse
The NBH file is signed, if you modifiy a single bit of it the signature becomes invalid and the bootloader won't let you flash it.
Yeah, it shows no GSM, and it won't boot up. I'm just trying anything i can, i figure it's an expensive paper weight at the moment, can't do any more damage. (can i?)
As for the nbh file....any way we can "sign" the file, make the hermes think it's a vaild file?
Related
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
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
In the wiki it is written that you need to CID unlock to be able to dump the ROM to an SD card from the bootloader.
http://wiki.xda-developers.com/index.php?pagename=Prophet_Rom_Dump
That's fine!
It is also written in the wiki that SoftSPL temporaily unlock your CID.
http://wiki.xda-developers.com/index.php?pagename=SoftSPL
That's also fine!
Then I'm wondering why can't I dump the ROM to an SD using Soft SPL?
I'm using the method from Update_Package of hma4 to perform the SoftSPL ONLY!
I'm having a G4 device.
After JumpSPL I got the nice white screen and I connect with TeraTermPro and got the prompt.
BUT!
After executing "r2sd all" only a partial text is replied and hangs and do not finish the text.
What is wrong?
Did anyone achieved to dump the ROM to an SD card using SoftSPL?
My goal is to dump the ORIGINAL ROM without doing any flashing even SPL! (don't want to loose warranty)
Is there a chance to perform this using SSPL ONLY?
Thanks!
imee.h said:
In the wiki it is written that you need to CID unlock to be able to dump the ROM to an SD card from the bootloader.
http://wiki.xda-developers.com/index.php?pagename=Prophet_Rom_Dump
That's fine!
It is also written in the wiki that SoftSPL temporaily unlock your CID.
http://wiki.xda-developers.com/index.php?pagename=SoftSPL
That's also fine!
Then I'm wondering why can't I dump the ROM to an SD using Soft SPL?
I'm using the method from Update_Package of hma4 to perform the SoftSPL ONLY!
I'm having a G4 device.
After JumpSPL I got the nice white screen and I connect with TeraTermPro and got the prompt.
BUT!
After executing "r2sd all" only a partial text is replied and hangs and do not finish the text.
What is wrong?
Did anyone achieved to dump the ROM to an SD card using SoftSPL?
My goal is to dump the ORIGINAL ROM without doing any flashing even SPL! (don't want to loose warranty)
Is there a chance to perform this using SSPL ONLY?
Thanks!
Click to expand...
Click to collapse
I think that needs an active sync connection to work...
If I remember properly, when I first arrived to this forum.
To dump the rom to the SD card, you should have cid unlocked your prophet, but according to the wiki you just can cid unlock G3 devices.
The way to solve the CID lock for G4, is to hardspl or softspl, the result is simmilar but the process is not the same. So you won't be able to use teraterm (at least I wasn't).
When I began, l3v5y suggested me the use of awizard to dump the rom, but I don't remember exactly the details of the process. I dumped, but I've never tried to restore it. So I cannot assure you the process is reliable.
myer said:
If I remember properly, when I first arrived to this forum.
To dump the rom to the SD card, you should have cid unlocked your prophet, but according to the wiki you just can cid unlock G3 devices.
The way to solve the CID lock for G4, is to hardspl or softspl, the result is simmilar but the process is not the same. So you won't be able to use teraterm (at least I wasn't).
When I began, l3v5y suggested me the use of awizard to dump the rom, but I don't remember exactly the details of the process. I dumped, but I've never tried to restore it. So I cannot assure you the process is reliable.
Click to expand...
Click to collapse
Using that technique, you will get a ROM that can be flashed as per the new WM6.1 ROMs.
It seems dumping ROM to SD card using SoftSPL works
Thanks for the replies guys!
It seems that the dumping now worked using mtty 1.42 instead of TeraTermPro.
For some reason the TeraTermPro hanged during printing the text. But I did not experience any problem using mtty 1.42.
The procedure is described in my other post:
http://forum.xda-developers.com/showpost.php?p=2327531&postcount=58
I haven't tried to restore yet, but the bootloader seems to recognize the rom dump on the SD card which is a good sign!
For people wanting to dump/restore their original rom of their device in case of no official rom for their country exists for download, this might be helpful.
EDIT:
Big warning goes here! It is not recommended to try to restore the image because the might fail! Other people tried the same procedure ending up in a failed restore! Investigation showed that the nk.nbf file (containing the ROM dump) has CRC errors when loading in neokit. Also shown that the ROM dump slightly differs at each creation!!! So do not try to restore it!
Cheers!
All,
I downloaded the original Cingular/ATT Rom, just in case, and bought Sprite and backed up my settings. I downloaded SDA_ApplicationUnlock.exe and ran it (from my PC, is this correct?). SDA_ApplicationUnlock.exe seemed to run okay, and gave me the message "SDA Successfully unlocked, Please Reboot SDA Now!". I rebooted my phone and did not notice a change (I assume I should?) I ran the Rom update for WM6.1 Standard, which opened up a DOS-looking box that stayed there forever and did not indicate it was doing anything. After just over an hour I disconnected my phone and rebooted it, no change.
My questions:
1) Do I run SDA_ApplicationUnlock.exe from my PC or from the WM phone itself?
2) Any suggestions as to what I may be doing wrong?
3) What does CID Unlock do, and do I need it?
Just to review, I have a Cingular 3125 with WM5, and I want to go to WM6.1 Standard.
Please help! Thanks!
Frank
geekzilla65
You were supposed to run Jump SPL on your phone which puts it into a special bootloader then run the update utility should run correctly. I personally prefer the MicroSD flash method myself.
Jump SPL?
icecube57 said:
You were supposed to run Jump SPL on your phone which puts it into a special bootloader then run the update utility should run correctly. I personally prefer the MicroSD flash method myself.
Click to expand...
Click to collapse
Thanks icecube57!
I know that SPL files were copied to my phone automatically when I ran Rom updater, but I don't think it ever launched. I am really confused about the CID unlock. I read one post where it says I have to do this, and another that says for Cingular Roms you don't need to.
Also, you mention the MicroSD flash method - is there a post here that explains how to do that? I would not mind trying it if you think it works better. Please help!
Frank
geekzilla65
If i dont say it someone else will. Please use the search function.
If the utility didnt automatically launch the Jump Spl program then navigate to the root of your phone using file explorer start it manually from your phone and it will put the phone into bootloader then try running the utility again. Thats how i had to do it with my phone
Thanks
icecube57 said:
If i dont say it someone else will. Please use the search function.
If the utility didnt automatically launch the Jump Spl program then navigate to the root of your phone using file explorer start it manually from your phone and it will put the phone into bootloader then try running the utility again. Thats how i had to do it with my phone
Click to expand...
Click to collapse
Okay, that's fair, thanks. Can I get an answer on one more thing? I did look in the forums, in the Wiki ,etc. on this - I am still confused on what CID unlock is. I really don't want to brick my phone. When this worked for you, was this on a Cingular 3125? Did you have to CID unlock?
Frank
geekzilla65
What you are talking about permenantly CID unlocks the phone which allows you to flash any rom. Instead of being stuck with carrier specific roms. What the JUMP SPL does is loads a specially modified bootloader that temporarily fakes the Update Utility into thinking your phone is CID unlocked that way you can flash any rom without going through that long complicated process in making it permenantly CID unlocked. I have a 3125 myself and flashes all the roms in this forum fine with the Jumps SPL Bootloader method.
MicroSD Flashing
Im feeling nice. Here is the MicroSD Flashing Method
http://forum.xda-developers.com/showthread.php?t=311232
Thanks!
icecube57 said:
What you are talking about permenantly CID unlocks the phone which allows you to flash any rom. Instead of being stuck with carrier specific roms. What the JUMP SPL does is loads a specially modified bootloader that temporarily fakes the Update Utility into thinking your phone is CID unlocked that way you can flash any rom without going through that long complicated process in making it permenantly CID unlocked. I have a 3125 myself and flashes all the roms in this forum fine with the Jumps SPL Bootloader method.
Click to expand...
Click to collapse
Thanks icecube57!!! I really appreciate the answers! You rock!
Frank
geekzilla65
Thanks!
icecube57 said:
Im feeling nice. Here is the MicroSD Flashing Method
http://forum.xda-developers.com/showthread.php?t=311232
Click to expand...
Click to collapse
Thanks for this one too! Awesome!
Frank
geekzilla65
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.