Hey..
I think in the moment there are many guys, out there, included me, that share the same problem: all probably unlocked their Dash's, Mail's or whatever using anykind of unlocking method (me, imei-check).
I am using a German MDA Mail, i needed to unlock it, in order to use it with my phone carrier apparently.
Now, the version of my phone is somewhat 1.18, and I want to update it to the WM6, like many others too. Both ways; SPL 1.11 and trying the update itself onyl lead to the same outcome : Invalid vendor/model id !
Many often say: yea, look in the CID unlock thread...well i did, very often, but there is no real solution to that problem, since basically, my Dash is unlocked, and presumably also CID unlocked since i got that from imei-check, which i think is a pioneer in that sector.
So, after all, what can we do!? Is it possible to still trying update that phone?
Hope we can find a solution, cuz i dun feel i am the only guy who has that problem.
I may have the same problem. Are you trying to unlock on Vista or XP?
I got it unlocked on XP, it worked fine i got to admit, no problems at all, my phone now seems to be unlocked and it works with another phone carrier, apart from T-Mo, which should be an indication FOR the CID unlock...
I dont think it is important to App unlock the Mail as well, cuz imei-check said it would be included...soo, would it be reasonable to ask imei-check, or does somebody else have an opinion about that?
I just upgraded to WM6. Here's what I did.
Unlocked it from imei-check. Ran SPL Upgrader. It gave me a Vendor ID being incorrect error.
Then I ran the WM6 upgrader from HTC. It upgraded and rebooted.
Now my phone is running WM6 and everything is fine.
Ha? you serious, thats very cool...well i tried it again with the spl upgrader, he went to 100%, aborted then with an invalid model error...then ran the upgrade afterwards, still didnt work... what about the version, did u take the German or the English one!?
Aaaargh, i am about to freak out..why doesnt it work, both SPL and the WM6 Upgrade give Invalid model errors, before i at least got a invalid vendor id, but not even that anymore...HELP...did imei-checks unlock didnt really work or what...
Yeah, I am very serious. I am using WM6 right now. I have a Dopod C720w.
Ok, here's what I did.
Unlocked through IMEI-check's software.
After that, I ran the SPL Upgrader. It went to 100% then gave me an Invalid Vendor ID error. I exited from there and then ran the HTC WM6 upgrade rom program. That started and slowly went to 100%. It said it had finished its job, so I removed my phone from the cable.
Then I proceeded to totally freak out because my phone looked like it was stuck at the Windows Mobile loading screen. I waited and after a long time, the rom initialised and ran through its first boot sequence.
Now its working perfectly and everything feels a bit faster.
If you went through the exact same steps, then I am not sure what your problem might be. Sorry. To tell you the truth, I am a completely noob at this who just did random steps and was lucky enough for it to work
P.S. I used the WWE (English) version, as I can't read German. I downloaded it off a rapidshare link posted in the big thread about HTC's rom release.
Well, i might not have much more skill either, but it is still quite worrying, is there maybe a difference between model and vendor id !? i am not quite sure what to try anymore, i remember yesterday, that i had a wrong vendor id as well, but today i just always got invalid model ids...very weird...well i will continue trying..do u remember what ur MDA mail version was before u updated it..sth like...1.18 !? by the way, which SPL upgrader are u using?
I am not using a MDA Mail. It's a Dopod c720w, same hardware, different branding.
This is the SPL Upgrader I used:
ftp://xda:[email protected]/smartphones/Excalibur/RUU_Excalibur_SPL-1.11_UpgradeOnly.exe
Try with that. It should work.
I think my version before upgrading was 1.15 something.
Nah, i think its the same SPL Upgrader (same size...) but i just dont get the idea why it doesnt work, some experienced upgrader here who can explain us the process?!?! I am not sure whether a reset of all settings would do a thing?! geez feel quite helpless in the moment^^
I had the same problem
but the only thing I did when got those problems was leaving my Vista based laptop and try with an XP based, downloaded the activesync, connected my htc, installed the SPL (downgrade) and then the WM6 WWE ROM, oh, I remember, first I installed the german version by mistake, so I had to repeat the process with the SPL before applying the correct ROM again.
When I was unlocking my HTC, I had some problems on the vista system, and I deactivated the antivirus... Could that be related?
Good Luck!!!
You haven't answered as to whether you're using XP or Vista. I ran into the same issues trying to do the SPL and ROM updates via Vista, when I tried it on my XP system -- both worked without errors.
vivid22 said:
Nah, i think its the same SPL Upgrader (same size...) but i just dont get the idea why it doesnt work, some experienced upgrader here who can explain us the process?!?! I am not sure whether a reset of all settings would do a thing?! geez feel quite helpless in the moment^^
Click to expand...
Click to collapse
Yeah, after hearing so much about Vista, I used my XP system to update the rom. Worked fine.
i LOVE imei-check, i wrote them an email a moment ago to ask them for support, they replied me after 10 minutes with a full strategy how to encounter the problem, fabulous support i gotta admit, here's what they said:
Hello,
It sounds like you try to make a CROSS-MODEL-ID update (e.g. WiFi chip missing T-Mobile ROM on a WiFi enabled HTC device).
EVERYTHING IS POSSIBLE. You only have to use SPECIAL INSTRUCTIONS in order to make a CROSS-MODEL-ID update:
*If you REALLY do it EXACT step by step like described you will have no problems*
Tools you need:
===============
- HexWorkshop from http://www.bpsoft.com/downloads/
- the ROM of your choice
- Winzip or Winrar
- a valid UNL file for YOUR phone
Preparation:
============
a) install HexWorkshop and Winzip or Winrar on your pc
b) in explorer on pc, RIGHT click on the ROM of your choice and use: "Extract files to folder ..." from conext menu Now it will unpack all the files
c) in the new folder you will have ONE file like "HRUU_signed.NBH" (*.NBH) RIGHT click on the .NBH file and use: "Hex Edit with Hex Workshop" from context menu
d) You'll see on the 5th row EXCA20000 ==> !!! make it EXCA***** (5 stars) and save the file
e) Now RIGHT click on ROMUpdateUtility.exe and use:
"Hex Edit with Hex Workshop" from conext menu Search for word
"BsaD5SeoA" (without quotes, case sensitive)
You'll find it around address 0x3FC6C
==> replace "BsaD5SeoA" with "IMEICHECK" (without quotes) and save the file
ROM-Update:
===========
1) take SIM card and SD card OUT of the phone
2) Connect the phone running windows ce to the pc (normal way).
3) Completely Unlock your phone using our unlocker <== REALLY IMPORTANT
4) After phone is unlocked run unlocker (again) BUT when the unlocker ask for UNL file, remove the USB cable from the phone THEN press "Cancel" on the unlocker select file window (unlocker will close on PC). NOTE: The screen on the device will not show something usefull when in this mode. Most probably it is complete WHITE. !!THIS IS NORMAL!! Don't touch phone, let it like it is!
5) After you closed the unlocker, attach usb cable again (phone has still white screen)
6) start (the modified) ROMUpdateUtility.exe
7) when update finished and device started you will get a message:
"Data Crashed, contact service provider" (!NO PANIC!)
==> Simply fix this problem by running the unlocker again and this time select the key file normal way (full unlock process again).
In case you have problems please indicate the step number/letter which is not clear/not working for you.
*If you REALLY do it EXACT step by step like described you will have no problems*
Click to expand...
Click to collapse
P.S., would be a good idea to post this as a sticky, since it really explains how to update a original HTC rom on such wifi lacking Excalibur versions like the MDA Mail,
greets and good night
Did you try to email imei-check?
I know that exactly the same problem occurred when the T-Mo WM6 came out.
Imei-check had sent back their customers who were not able to upgrade a procedure how to modify their unlocker with a hex editor to change the model ID.
BTW: Model ID: there are two different models - EXCA100 and EXCA200 - take a look under your battery - german XDA Cosmo for example is EXCA200 (there the SPL seems not to work)
The other thing is the vendor ID. This seems to be solved by pof's Upgrade SPL 1.11
So simply try to write to imei-check and say that your unlock does not work - in the past they were very customer friendly - hope this didn't change meanwhile
EDIT: OK - vivid was a little bit faster - next time I should refresh the thread before I answer...
FYI !!
saw some post where people was being impatient during the upgrading process and completely abort the process ...etc
you are supposed to be at the logo screen for a period of time ... it doesn't meant it's hanged ... be patience !
just a note
Patience is the key...
Hm, OK, I did it... I bought the fracking UNL, took me one hour to figure how to get rid of the protection (security + antivirus) in my laptop that did not allow me to run the unlocking app. Finally, I got it.
First time I flash the ROM it did not work. I tried using first the SPL, and it worked nicely. After that, I could flash the ROM. Be patient, it takes some minutes to reboot, and it looks like is freezed, but not... wait!
Can´t see much difference from WM5, but I noticed a best performance in wifi connection. Now I´m fracking installing all the goodies I had before... bluetooth keyboard is not working... I will work it out a little bit.
Just in case, if someone wants the UNL for research... PM me.
I am glad it all worked out for you. Didn't know that the MDA Mail came without Wifi.
Wow, I must say, I am glad I used Imei-Check's service as well. That was an extremely helpful reply they sent you. Not seen many companies who do that.
That's exactly what i thought
Maybe we should write them a thankyou email for all their great help in name of the whole xda-developers community what u think
Anyhow, can somebody explain me real quick what should be definitely be installed to WM6?
@PhoenixAG: yeaa stupid T-Mobile GER...they didnt take away the wifi chip on the S710 or the newer ones, have no idea why they did it to the Excalibur then..
It would be a good idea to stick this solution.
I think many users in this forum have exactly the same problem in doing a cross model ID update. You can see Excalibur devices from many countries and carriers here.
I have a T-Mobile MDA Mail too which lacks the Wi-Fi and had to do the same steps after cid-unlocking it through imeicheck.
You have to do it really step by step. I had problems in doing it out of my memory for the new HTC ROM and wondered why it failed. But going through it step by step really works EVERY time I did it and thats now the third time.
First was installing T-Mobile Dash WM6 ROM, second the Russian HTC ROM and now finally the German HTC WM6 ROM.
Related
Time to kill my Orbit and start again....
It's running painfully slowly and the GPS won't work so I'm going to hard reset my XDA and get rid of the O2 crap, then install TomTom. I know all this stuff is here somewhere but I’m up to my eyeballs in tech articles so…. Questions:
1. Should I upgrade the ROM, and if so can anybody point me to a suitable ROM image? If I do this should I unlock it first?
2. What's the best way of getting a clean install - is it to hard reset then soft reset before the O2 stuff loads? Or should I go for a cosporate install option (is this available for the Orbit) And how do I hard reset?
3. is there an easy way of setting up the O2 connection settings afterwards or do I have to do it manually?
Lots of questions and not enough time….
I have an O2 Orbit. Best thing to do is get it unlocked by imei-check. Then run USPL program from mobile6 forum. Makes it a lot easier to fix if something goes wrong at any time. After this you can flash the ROM to your hearts content. I use Black&Bluev3 and i can truly say that WM6 is amazing. To get a clean install just do a Hard Reset then when it boots back up, before the O2 customization routine runs just Soft reset. That's all there is to it. As far as O2 setting go. Have a look through the upgrading forum. There are usually a few postings of O2 settings. If not let me know. I have the HTC UK settings file on my PC. Anything else you need help with let me know.
Shand359 said:
I have an O2 Orbit. Best thing to do is get it unlocked by imei-check. Then run USPL program from mobile6 forum. Makes it a lot easier to fix if something goes wrong at any time. After this you can flash the ROM to your hearts content. I use Black&Bluev3 and i can truly say that WM6 is amazing. To get a clean install just do a Hard Reset then when it boots back up, before the O2 customization routine runs just Soft reset. That's all there is to it. As far as O2 setting go. Have a look through the upgrading forum. There are usually a few postings of O2 settings. If not let me know. I have the HTC UK settings file on my PC. Anything else you need help with let me know.
Click to expand...
Click to collapse
Thats different to my understanding of things.
If you are thinking of upgrading the rom (instead of just hard resetting the phone) then you will need to either get your phone CID unlocked with the imei-check team or run the Artemis USPL application prior to loading the new rom file. The USPL program temporarily 'unlocks' the CID whereas imei-check does it permanently. Once you've done either of these methods (I ran USPL as didn't want to pay £40 when I could get it done temporarily for free) you can then flash any of the roms suitable for your phone. I've got an o2 UK supplied Orbit and went with Tom's Black & Blue v3.
When you load the B&B rom it writes over the extended rom so all of the o2 programs are cleared so no need to soft-reset once its been flashed. This way will give you a fully functional phone with a lot of preinstalled apps (all of which are useful if not essential in my opinion) and none of the o2 junk on there.
Your other choice is to hard reset the phone and once its finished it'll prompt you about customising your phone. Simply soft reset before it gets a chance to run the ext_rom and none of the o2 crap will be on there. Now your phone will be pretty much as it left the factory with WM5 installed and thats it. If you're in the UK using o2 then the attached cab file contains all the settings that you'll need for MMS and GPRS etc.
As for question 3, see my previous statement about the cab file. Very useful to keep this as I've re-flashed my phone a few times and it makes the process a whole lot more bearable trust me!
thanks for the valuable info - I'll try Black&Bluev3 once I unlock. Excuse the ignorance, but do I just run the copy the O2 cab file to the Orbit, then run it from there?
Yep, as simple as that Probably best to copy it to your SD card and keep it on there as once the phone has been reflashed you won't have to connect up to a pc to install the network settings.
everything seemed to have gone fine, but after restarting the phone won't recognise the sim - before i even had a chance to enter the pin 3 times it reported that it required the unlocking code, and then refused to accept the unlocking code once I'd got that.
So now I've got a very sleek PDA, but no phone Any idea where I can get an O2 ROM from as I can't see it listed in the Artemis list, and am I looking for a ROM or extended ROM (what is the difference anyway?)
TIA
Peter
The b and b rom your usings originates from the leaked o2 orbit german rom - changed to wwe by bepe and tweaked by tom. So firstly i would try a hard reset or reflashing the rom. You dont need to flash USPL again as its an os only rom. If still not working flash original wm5 rom - see sticky in artemis mobile 6 forum for the link.
Just thought I'd drop this here... Despite how much I read and re-read all the instructions, I mis-understood the two unlockers, and flashed the Alltel ROM on my Verizon XV6900 with the 0.40 Unlocker and wound up with a brick.
Even flashing the Verizon RUU dump wouldn't fix it... SPL 2.01 RGB screen and that's it.
So after much research... MTTY to the rescue. set 16 0, task 8, and viola... unbricked! (I think flashing the verizon ruu first was important)
No storage card needed (or possible on the Verizon, there's no slot!)
Thanks all... still trying to get GPS working now, so far nothing.
vogue_brick1 said:
Just thought I'd drop this here... Despite how much I read and re-read all the instructions, I mis-understood the two unlockers, and flashed the Alltel ROM on my Verizon XV6900 with the 0.40 Unlocker and wound up with a brick.
Even flashing the Verizon RUU dump wouldn't fix it... SPL 2.01 RGB screen and that's it.
So after much research... MTTY to the rescue. set 16 0, task 8, and viola... unbricked! (I think flashing the verizon ruu first was important)
No storage card needed (or possible on the Verizon, there's no slot!)
Thanks all... still trying to get GPS working now, so far nothing.
Click to expand...
Click to collapse
There is a microSD slot on the XV6900. It is on the right side of the phone under the chrome trim. You can see a small SD icon on the side of the phone next to the stylus under the battery cover!
louderjw said:
There is a microSD slot on the XV6900. It is on the right side of the phone under the chrome trim. You can see a small SD icon on the side of the phone next to the stylus under the battery cover!
Click to expand...
Click to collapse
Thanks! I looked all over
vogue_brick1 said:
No storage card needed (or possible on the Verizon, there's no slot!)
Thanks all... still trying to get GPS working now, so far nothing.
Click to expand...
Click to collapse
Not trying to be a flamer here ... but ... you should really learn about your phone stock ... capabilities ... features ... etc. ... prior to doing custom flashes ... especially with the radio ... fortunately for you and me ... it is extremely hard to "brick" a HTC phone ... it may seem bricked ... but I've only ever seen a couple true bricks ... most can be recovered by the heavy hitters here
My point is that you really need to understand your phone and what you're trying to do prior to doing custom roms ... unlockers, relockers, etc. ... this is extremely important when doing radio changes ... fearless and aggressive is no way to approach these changes
And as always .... read ... read ... read ... did I mention READ!!!!!
Again ... not flaming you ... kinda using you as an example so others will learn and maybe keep the number of true bricks to a minimum
Fuzzy
I agree, I got a little excited with this and should have taken my time... My last phone was an Apache xv6700 and I had a blast flashing that and upgrading it over the past 2 years. I rushed into it with this one because I'm an impulse guy and had just bought the phone within 24 hours
me too!
vogue_brick1 said:
Even flashing the Verizon RUU dump wouldn't fix it... SPL 2.01 RGB screen and that's it.
So after much research... MTTY to the rescue. set 16 0, task 8, and viola... unbricked! (I think flashing the verizon ruu first was important)
No storage card needed (or possible on the Verizon, there's no slot!)
Thanks all... still trying to get GPS working now, so far nothing.
Click to expand...
Click to collapse
could you explain how to use mtty! i "bricked" my xv6900 a couple weeks ago too. its stuck on the rainbow screen with the original spl (took a few flashes to get there)! i tried mtty when i did it and there wasnt a usb option in the program! im running on vista. already got my replacement too!
Not sure how to help you... There was a USB entry in the list when I did it, on XP.
On a separate note, I got GPS working and it's incredible.
Nice to see a Verizon user with GPS working!
Mind posting a little guide? I have my Vogue on order right now and want to update it right away for the GPS.
vaxick said:
Nice to see a Verizon user with GPS working!
Mind posting a little guide? I have my Vogue on order right now and want to update it right away for the GPS.
Click to expand...
Click to collapse
Here are the steps I took to successfully get the Verizon hacked with gps:
1. get it hooked up with activesync
2. unlock with imcokeman 0.40 unlocker
(the docs said to flash to the original rom here, but there is no verizon ruu, and my phone auto-reflashed itself anyways and ran customizations)
3. unlock with imcokeman 2.31 unlocker
4. install the alltel RUU (should be in sticky thread)
5. download Build OS from ppckitchen.org and use the updater to get the vogue 6.1 gps 3.02 kitchen
6. pick options and build, flash..
fire open google maps, pick menu->use gps.. magic.
It helped me out of a jam tonight, lost in bumblefukk and found my way back with it.
could you please explain in step-by-step detail as to how you unbricked your xv6900?
I'm currently working on my friend's xv6900 (TyTN II user myself) and unlocking and flashing roms on this phone is so different (yet kind of the same?) and I'm now at a point where I'm stuck at the HTC startup screen and thats about it. where did you get MTTY and how exactly do you use it? I tried downloading one but it was a very old version (2001) and I'm pretty sure that it's not the one you were using.
if anyone else knows how to unbrick this phone please chime in thanks a lot!
vogue_brick1 said:
Just thought I'd drop this here... Despite how much I read and re-read all the instructions, I mis-understood the two unlockers, and flashed the Alltel ROM on my Verizon XV6900 with the 0.40 Unlocker and wound up with a brick.
Even flashing the Verizon RUU dump wouldn't fix it... SPL 2.01 RGB screen and that's it.
So after much research... MTTY to the rescue. set 16 0, task 8, and viola... unbricked! (I think flashing the verizon ruu first was important)
Click to expand...
Click to collapse
Can you explain what you did after MTTY? I bricked mine, got stuck in the SPL 2.1.1000 bootloader, used MTTY, got it unbricked, but now am stuck at the leaked sprint rom's splash screen. Any help would be greatly appreciated!!
[size=+1]Greetings From the Diamond Elite Project Team (currently only Olipro and Cmonex, so, any other skilled devs wanted - please PM Olipro and/or Cmonex, don't PM this account, we rarely check it)[/size]
We are proud to announce the release of Hard-SPL for *ALL* Diamond devices, overcoming the new MPU protection on the device.
[size=+2]NOTE: This is NOT a SIM unlocker - it also doesn't unlock Security for other radios. if you need that, GO HERE[/size]
As an added feature, the Hard-SPL requires signed code even after flashing... we chose to do this for several reasons.
1) safety... we will begin releasing all available Diamond resources re-signed with our certificate, this means you don't need to worry about flashing something incompatible, if it's something bad, we won't sign it.
2) reliability; If you want something signed, just ask, we will be able to verify that it's not going to be something that breaks the device, as has been the case with the Elf ROM disaster.
We'll be releasing a developer edition in the future; we will continue to maintain the signed SPL as this is quite nice for total and utter noobs afraid of bricking their device.
Flash this now, [size=+2]Go to our separate thread listing Supported ROMs for ROMs you can flash[/size]
[size=+2]Installation Instructions:[/size]
1) Download, extract to an empty folder.
2) Run RomUpdateUtility.exe, Have Phone Synced with PC in Windows Mobile
3) follow steps, check device for prompts after PC shows loading bar.
4) SPL flashes, job done.
Anyone having problems with the device entering SSPL automatically, please copy SSPLManual.exe to the device and run it. then once the screen is black, run RUU manually.
IMPORTANT NOTES:
1. do not try to use this SSPL to flash anything else other than an SPL file. it explicitly blocks other flashes anyway. SSPL is *never* a good way to flash OS images
2. INSTALLING THIS WILL HARD-RESET THE DEVICE
Thanks to Walshieau for a **** load of testing!
All Project Donations gratefully accepted
INSTALLING THIS WILL HARD-RESET THE DEVICE
TROUBLESHOOTING TIPS:
- read the instructions.
- read the instructions.
- read the instructions.
- Anyone having problems with the device entering SSPL automatically (your device doesn't even go to black screen), please copy SSPLManual.exe to the device and run it. then once the screen is black, run RUU manually (you run the RUU on the PC, if it isn't obvious).
- if you get connection error in RUU after the device goes to black screen, then try a different USB port, also do not use USB hub, you can also try rebooting your PC, and can try using another PC. read the thread for even more tips that I don't remember now. also you can try unticking advanced network functionality in start menu / settings / connections / usbtopc applet.
- if SSPL-Manual.exe or enterbootloader.exe fails to run (says missing component or similar), try a hard reset of the device.
- CDMA (Sprint or Telus) diamonds need my other hardspl:, head over to: CDMA (not GSM) diamond hardspl - ONLY use this if your diamond does not use GSM protocol for radio!!! otherwise you will brick the device!!!
UPDATE: 1.37 Hard-SPL
for those who need 1.37 due to some screen fuzziness issues on some newer diamonds, here it is with hardspl patches:
- Developer Edition: can flash unsigned code. Version: 1.37.OliNex
- Signed Edition: can only flash preapproved signed code. Version: 1.38.OliNex (of course still based on 1.37).
please see Attachment below for Signed Edition!!
for Developer Edition, see the developer hardspl thread of course.
(use attachment Hard-SPL-Diamond-OliNex.zip to get the RUU package to flash the 1.38 NBH from HardSPL_OliNex138_Signed.zip. just overwrite the NBH file with 1.38 NBH)
I recommend you flash the original HardSPL, as that one is MFG. only flash the 1.37/1.38 if you experience the fuzzy display issue.
UPDATE 2: 1.93 Hard-SPL
(placeholder for now, but you can already download unsigned version in the Developer HardSPL thread!)
if someone's diamond came with 1.93 SPL originally, maybe this HardSPL based on 1.93 will work better than the olders. I have a report that someone has black screen with older SPL's.
but even if your diamond didn't come with 1.93 stock, but 1.37/1.38 doesn't fix screen problems (fuzzy screen, flickering, etc.), it is recommended to try this 1.93 HardSPL.
if your diamond works fine with original HardSPL, no need to flash this one.
IMPORTANT: all in all, I recommend you flash the original HardSPL, as that one is MFG and easier to deal with if there is some problem. only flash the 1.37/1.38 or 1.93 if you have screen issues.
if it was some other version and you still have issues after trying 1.37/1.38 and 1.93, then please let us know.
Stock SPL's for warranty reasons:
visit the http://forum.xda-developers.com/showthread.php?t=400411 (Signed ROMs) thread, see post #20.
(or visit Developer HardSPL thread post #39, same thing.)
Thank you. I am going to flash..
panosha said:
Thank you. I am going to flash..
Click to expand...
Click to collapse
enjoy! you won't imagine how much work it was for me to get this ****er (SSPL) working
anyway, this has been tested on radio versions 0.91 and 0.93, I don't think it is radio specific, but if you have some newer radio version (haven't seen any yet) and have trouble with running SSPL or flashing it, let us know.
also, the SSPL screen is black, not tricolour, that's just the way it is. only preproduction diamond had it tricolour.
last note: do not try to use this SSPL to flash anything else other than an SPL file. it explicitly blocks other flashes anyway. SSPL is *never* a good way to flash OS images.
Thanx a lot guys, awesome work.
Thanks Olinex
i agree to the idea of olipro, it is good to the community ...especially for new comer who had not muc experience in rom flashing
but i think for developer and some experienced user , a unsigned version is neccessary for daily testing like :
1) if i am cooking a rom and wanna flash into the device to had a real test , i need to wait u guys to sign..u guys may busy and wasting unneccessary time for signing some "beta" rom ...example I made a hermes rom before ..which had chinese build in support, i had made more than 5 nbh for my own testing ....:S .. u can imagine if need signed .. i need to bother "olinex" tooo many time
look forward for a developer unsigned ver
@leofungwai.
can't you just sign this HSSPL code with you own certificate before getting this thing on of course if that's the case? should be straight forwar, really..
also, it should allow for flasing genuine firmwares signed by vendors, meaning hardware vendor's certificate is still must be valid.
And if it doesn't then, what happens if device is stucked in bootloader or doesn't boot into OS anymore? that would make difficult for reverting back to original SPL.
SecureGSM said:
can't you just sign this HSSPL code with you own certificate before getting this thing on of course if that's the case? should be straight forwar, really..
Click to expand...
Click to collapse
Surely you're not THAT stupid?
testing now
hi all testing now updating soon
First of all great work guys!
I am trying to flash my Diamond from a Windows XP machine. I start the RUU and when the progress bar appears it halts at 0% and after some time starts about a connection problem, my diamond is not going in bootloader mode. So I started my Diamond mannualy in 3 color mode and started the RUU again. Again it halts at 0% and is there now for about 5 mins. Can you help me out guys?
RvBCrS
Great!
And thanks for the TEAM!!!
Just installed it.
Worked.
this makes a Hard Reset on the Device.
Now will try to update with a different rom.
Nadavi.
what is that suppposed to mean? calling someone stupid is already bad but that was my question.
The way I understood, if your SPL code is checking for presence of your certificate "attached" to the NBH, then if the certificate in your SPL code is patched to different certificate, then SPL will not complain about code is not being signed by your certificate anymore. call this stupidity, but I am not going to put something on my device I would not be able to remove with out third party *permission* to do so.
again, I can be wrong. I am not a programmer, but then your explanation is confusing.
Very strange, if I start the RUU updater with my phone booted in Windows Mobile, it try's to start EnterBootloader.exe but that crashes with an exception window!?!
just reset the device and try again. it MUST be done from windows
Olipro said:
just reset the device and try again. it MUST be done from windows
Click to expand...
Click to collapse
Thanks olipro for you response, I rebooted my device and did it again with windows mobile booted, waited for device center connection, and again got the exception on "Enterbootloader.exe" very strange it looks like a .NET exception window.. I have a Dutch Mobile edition, don't know if that matters..
SecureGSM said:
what is that suppposed to mean? calling someone stupid is already bad but that was my question.
The way I understood, if your SPL code is checking for presence of your certificate "attached" to the NBH, then if the certificate in your SPL code is patched to different certificate, then SPL will not complain about code is not being signed by your certificate anymore. call this stupidity, but I am not going to put something on my device I would not be able to remove with out third party *permission* to do so.
again, I can be wrong. I am not a programmer, but then your explanation is confusing.
Click to expand...
Click to collapse
yes... patched to a different certificate, therefore, requiring files that you flash to be signed with it.
If you want to get rid of it, you can have a stock HTC SPL signed with it.
Personally I like this because our released ROMs have no SPL in and a dedicated rollback desired for warranty purposes can be used with no chance of mistake
SecureGSM said:
@leofungwai.
can't you just sign this HSSPL code with you own certificate before getting this thing on of course if that's the case? should be straight forwar, really..
also, it should allow for flasing genuine firmwares signed by vendors, meaning hardware vendor's certificate is still must be valid.
And if it doesn't then, what happens if device is stucked in bootloader or doesn't boot into OS anymore? that would make difficult for reverting back to original SPL.
Click to expand...
Click to collapse
you can't, because the SSPL also requires this custom signing to flash the HSPL...
your point is very good about allowing for stock ROMs.
we actually can have a way to do that
though hopefully this won't last long and the unsigned "developer version" will be available to everyone soon. I strongly disagree with the original idea anyway.
same
same here stuck in 0 %
motin said:
same here stuck in 0 %
Click to expand...
Click to collapse
did the screen actually go black (i.e. into bootloader)
WooooooT great job guys!!!!
when you run the new rom from europe then it will boot to the 3 bootolader mode you can see your spl installed and then not mov any more from 0%
Hi amm
I am new to windows mobile. i got this ophone of my old work mate.
I have tryed to put windows mobile 6 on the phone as it only have wm5 on it, but i get as far as the phone changing to upgrade mode ( 3 striped red, blue and green) screen and then it says that the phone cant comunicate.
I have tryed going though o2 website but it not recignizing my serial for the phone ( ex contract and also was a replacement handset)
any help would be nice, by the way i am on windows vist a, but i have also tryed it on xp, but the same still happns.
Thanks
Paul
anyone? noow any suggestions
This answer may seem condescending, but it isn't.
1. Are you attemtping to flash a rom update from the phone's original carrier or a non carrier specific rom? If a non carrier specific rom then see #2. If carrier specific did you download the rom from a secure place such as the carrier's website? If not, you may want to and try again.
2. Have you made sure your phone is CID and sim unlocked? This has to happen if you are attempting to flash a non carrier specific rom onto your phone. There is literature in your specific phone's Mobile 6 forum that is stickied or in the Wiki which will show you the best way to accomplish flashing. You must first read, then use the correct methods and tools or you will most likely create a brick. At this point of the game your phone is a little older and the path to Mobile 6 is well laid out. Which leads to the next question.
3. Have you done a search for this problem? You are not the first and will not be the last to have run into this issue. Using the search button does wonders here. If you have the cajones to flash your phone you are adventerous and the knowledge you will pick up will help in the long run. I say this because flashing is addictive and once you see the immediate improvements you will continue to look for better roms.
4. Please remember this is a developer's forum so the intelligence level is higher than most other forums but the patience level is much lower for those not willing to follow directions and/or help themselves. Some things have well laid out paths and others are trial and error. A lot of people here are doing a large amount of work for little to no money so please READ before embarking on your journey.
5. Get to work. Oh yeah. Please lit your phone's information in your signature. It will save someone asking the first 2 or 3 questions I did everytime. You could use mine as an example. Believe me it saves time and people are more willing to help.
hey thanks for your message
I am trying to flash the phone with Official O2 UK WM6 Trion (Hermes) rom 3.54.206.1_6275+radio 1.47 (3-8-2007) , the phone is simfree.
but even on trying to install Olipro v7 2.10 i get messages like 266 or 260 conection timed out or something. i am technical minded and i have tryed to serch for the awsers using google.
I suggest reading the Wiki and your Mobile 6 forums for the way to flash without using the usb cord. It will take a non-sdhc memory card and uses the nbh file from the rom you are flashing. Research that.
What is the HTC name for your phone? The Trion is a Hermes or a Wizard correct?
Also, CID and sim unlocking your phone will eliminate many future problems. Just be aware it automatically voids your warranty.
Okay - can you do a soft reset and have the phone work fine? That is step one. If so, then go to the Hermes Mobile 6 forum and check out the stickies. Dr. Puttingham wrote a great guide to flashing our phones.
If you can't get the phone working from the soft reset I suggest reading the Wiki and the Mobile 6 forums for the way to flash without using the usb cord. It will take a non-sdhc memory card and uses the nbh file from the rom you are flashing. Research that.
The Trion is a Hermes, which is what I have (Cingular 8525). I would suggest a non carrier rom of Mobile 6.1. You will find it to be much faster and stable.
Also, CID and sim unlocking your phone will eliminate many future problems. Just be aware it automatically voids your warranty.
hi i just found out that thephone is not a trion afterall it is a xda mini s, can this still be upgraded
I believe the Mini S is a Wizard. check out the forums. All the answers are there. I retired my Wizard 3 months ago . This is an easy problem to fix. Just read. I still suggest Mobile 6.1. Especially on the Wizard.
Hi I have recently tried to flash my Touch Diamond ROM, messed the hell out of it and, the only way to fix it is to flash it with the original stock ROM that it came with. Could anyone please help me with this.
HTC Touch Diamond P3700
Rom SPL 1.93
CID HTC_017
The phone was not branded straight from the manufacturer.
The problem is that I tried to flash the phone without doing hard SPL
Cleaned the whole phone and the only thing working now is the connection to the computer Trough mtty. I tried using other ROMS but they stop at 1% and gave me a vendor incorect error or something.
just download it from htc site
I tried but when I select the Serial number it says that the update is not for my phone and doesn't let me download it. and the ones that they have are only updates.
Does anyone have a valid Serial Number that i can use to download update ROM from HTC?
Have you tried any official roms posted around here? like this one: http://forum.xda-developers.com/showthread.php?t=410720
I did that but it started to load the roam into the phone and crashed at 1%,
it gave "Invalid Vendor Id" error and it turns off. Is there like a unversal HTC rom that at very least gets me access to the NANd Memory
I just want to HArd_spl the phone and install a new ROm
Dont even care about the original ROM any more
ekirakosyan said:
I did that but it started to load the roam into the phone and crashed at 1%,
it gave "Invalid Vendor Id" error and it turns off. Is there like a unversal HTC rom that at very least gets me access to the NANd Memory
I just want to HArd_spl the phone and install a new ROm
Dont even care about the original ROM any more
Click to expand...
Click to collapse
Try that one HT828GN27034 and let me know the result.
Oh very nice, thank U very much, I'll try it right now.
All of the Upgrade ROMs just give me invalid Vender ID error message
Doesn't make sense to me though, i tried flashing the Phone With Hard-SPL but for some odd reason it hangs at 0%.
Is my phone dead for good or there might be a way to fix this issue
did u installed OLINEX first?
If ur phone is in 3 color screen try to install Olinex 1.4 and after that flash it with stock ROM.
No thats the thing, I Just Cleaned the phone with Mtty and tried to flash it with WM6.5. but after the cleaning nothing really work out. and i cant even go back to the the old Rom cose I did not back it up.
ekirakosyan said:
No thats the thing, I Just Cleaned the phone with Mtty and tried to flash it with WM6.5. but after the cleaning nothing really work out. and i cant even go back to the the old Rom cose I did not back it up.
Click to expand...
Click to collapse
not even hard reset? did u tried?
yeah man i tried hard reset too, that was no go, I wish there was a way to remove the CID Lock
ekirakosyan said:
yeah man i tried hard reset too, that was no go, I wish there was a way to remove the CID Lock
Click to expand...
Click to collapse
What windows are you using?
I am using windows 7, but i tried the same process on vista and XP, same result, the phone connects to the pc, and right as i try to load one of the ROMs from HTC's website, the thing crashes at 1% and says invalid vendor ID error.
IS there a universal ROM that can be loaded, or my phone is bricked for good?
Perhaps you want to have a look here: http://wiki.xda-developers.com/index.php?pagename=Diamond_Upgrades
Succes!
Oh wow this place has every ROM type but mine, so not fare, u think if i download and try every one of these other ones I might have some sort of luck?
I used HTC's MTTY and figuered that My CID is HTC__017, and the 1.93 Spl
and mine is not listed there.
Hey, I have the EXACT same problem. My diamond is the US 3G Unbranded phone (DIAM110, CID=HTC__017). I've both called and emailed HTC asking for the ROM, but they say that they do not have it. The only way to get it would be to request it from the vendor you bought it from. I got mine as a gift so I can't really do that. Oh, and if you want them to flash it for you, you have to pay like $160. Not cheap. And you know HTC, they'll make up that your main board's fried, and ask you to pay $300. If you have WARRANTY, send ASAP. Mine expired a week ago.
As for flashing random ROMs, most likely this will not work (although you can try). The way your phone determines if it's allowed to install the ROM is by looking at the beginning of the file. If you open up the NBH with an editor, you can see and even change the ID. The problem is, HTC "signs" the file with a 2048 RSA key (2^2048), and if you even change one digit then the signature will be invalid.
So yes, I have the exact same problem, my thread is at: http://forum.xda-developers.com/showthread.php?t=623320, so if you have any luck, or I do, check out that thread.
At this point, the only things that are left to do are to beg HTC or a vendor for the ROM update (I might find HTC developer's mailing address and ask them); find a way to get into Soft SPL, or in other words load into memory a bootloader that would allow flashing of unsigned code; or find a vulnerability that would allow flashing unsigned code (has been done with Trinity).
Also you can try contacting Olipro, cmonex, and pof, but I so far have had no luck.
Hopefully we'll find something.
~codeslicer
Hey man, thanks for the reply, we are pretty much on the same exact boat, am gonna try to contact HTC see if my warranty is still up, and the phone i got it as a gift, I don't have a recipt of a proof of purchase, what do u think i should tell them. And if that doesn't work, I think I am going to try every single 1.93 ROM
in this site.
http://wiki.xda-developers.com/index.php?pagename=Diamond_Upgrades
And also what is your CID. if its HTC_017 then its not here, but there are a lot of them in here so u might get some luck.
let me know how it goes man.
I think i have the solution
can u please confirm clearly as what has happened , hope i have the specific solution .