Related
I was going to update my Cingular 8525 to WM6 and in preparation for it flashed it with the latest OLIPRO V6. I got COLD FEET and instead decided to try upgrading to the HTC RUU_Hermes_CINGULAR_WWE_2_1_[1].06.502.3_6275_1.33.31.00_108_Ship.exe
Apparently the OLIPRO V6 has changed it to where I can't upgrade… I get an error (206) when trying to upgrade. I lose my SYNC connection. Doing a master reset didn't do a thing and the OLIPRO V6 is still there when I check it. Can someone PLEASE give me the instructions how to get it back to NORMAL? Yes, I realize NUUBS are a real pain in the butt, but we've got to start somewhere (you were new once, too!!).
Whoever helps, MY THANKS IN ADVANCE!!!
Check the wiki...how to flash is inthere...important however will be what OS you computer is running...i'm sytill a nooob too and i was getting the 260 errors when i tried to flash form Vista...ended up having to use a differentset of drivers...then life was cool.
search for "HERMIMG.NBH"
There are other (better) ways too, but I don't think you're good enough to do it yourself.
I'll give you one hint... Oli 1.40 is based on 1.11. The rom you you're installing is 1.04. But, before you screw around.. Read!
I've flashed other phones to different ROMs and never had any problems. As I said, I installed the Olipro V6 as recommended to insure I wouldn't "BRICK" the phone. The phone works now, BUT I still want to upgrade to the HTC supplied "RUU_Hermes_CINGULAR_WWE_2_1_[1].06.502.3_6275_1.33.31.00_108_Ship.exe” and be done with it. Apparently Olipro won’t allow me to do that!!! So I need to re-install what Olipro V6 REPLACED!
LegolasTheElf said “search for "HERMIMG.NBH"
There are other (better) ways too, but I don't think you're good enough to do it yourself.
I'll give you one hint... Oli 1.40 is based on 1.11. The rom you you're installing is 1.04. But, before you screw around.. Read!”
I DID search and read, but I guess I either missed it or don’t understand what I’m reading! So I’m a NOOB in need of help! I guess I need to be “spoon fed” whatever it takes to het me back to an ORIGINAL CINGULAR 8525 where I can upgrade to "RUU_Hermes_CINGULAR_WWE_2_1_[1].06.502.3_6275_1.33.31.00_108_Ship.exe” Did I get in over my head? It seems so!!! Not BRICKED, but just want to revert back to the ORIGINAL CINGULAR 8525. PLEASE can I get some help here??? THANK YOU!!!!
Use the custom RUU with the NBH file you want to upgrade.
pof said:
Use the custom RUU with the NBH file you want to upgrade.
Click to expand...
Click to collapse
I downloaded and tried the custom RUU, but kept getting the error message 240 file open. The phone shows "Hermes 100 FPL-101 and SPL-1.10.oli. All I want to do is to remove the SPL-1.10.oli and revert back to FPL-101 !!! I'm getting advice that either doesn't work, I can't make it work, I'm not explaining what I want to do OR... God I don't know!! Let it suffice to say I"M A LOST BALL IN TALL WEEDS folks. HELP!!!!!!
I'm so happy you're reading carefully
I'll do this once, if you can't figure it out, then, you're better off finding someone to pay to do it for you!
1) Get CustomRUU
2) Get the Cingular ROM
3) Get WinRAR
4) Extract Cingular ROM
5) Extract CustomRUU
6) Place the .nbh from Cingy ROM and CustomeRUU.exe into ONE directory--alone.
7) Run the CustomRUU.exe file
8) READ THE ****ING DIRECTIONS
That's it.
Oh, and stay away from roms that you don't want to spend the time to understand.
Many THANKS to LegolasTheElf!!! You pulled my bacon out of the fire and saved the day! I DO APPRECIATE IT!!! All is well and these 57 year old eyes are headed off to bed... Lesson Learned!
Hi,
i was trying to upgrade my Hermes to WM6 and i was doing it according to mrvnx guide. First i tried the WM6 guide. Ipl was 1.01 and SPL was 1.11. Evrything went fine up until the part where the actual ROM was supposed to be flashed. The update pocess started, and i went for a smoke somewhere at 2%. When i came back, there was a message saying image file was corrupted, and Hermes was up and running. So, my first instinct was that i missunderstood something and that that guide was for phones already having WM6, so i decided to do the WM5 guide. I flashed the SPL, skipped the radio upgrade (cause i didn't know whether to use that version or the later one) and skipped to the next page. And, low and behold, there it says "Firstly download the WM5 ROM you wish to upgrade to"
And now i'm stuck and i don't know what to do. Should i get some WM5 ROM and first upgrade to it and then to WM6? Or should i go straight for WM6 ROM? If so, do i just follow the WM5 guide only using WM6 ROM or do i just flash it by the WM6 guide?
The phone still works with no problems at all. The desired WM6 ROM is Pays Full. Is it really corupted (got it from the "download full" link in the first post here), or was it my mistake?
Sim unlock and cid unlock your device then - http://pof.eslack.org/hermes-unlocker/
Download your carriers Rom (wm5 or wm6 - o2,orange,at&t etc)
then flash that.
then HARDSPL your device - http://forum.xda-developers.com/showthread.php?t=296722
then use modified updater to flash your device with the wm6/6.1 rom of your choice.. works fine for me.
2.10 bootloader with the "is it hardspl" checked and wa'la its updated
hope this helps.
Thanx for the answer. I doubt i'll find my carrier's rom, since i'm from Croatia, and i think it hasn't been posted here, and certainly hasn't been posted on my provider's site. I did make a backup before upgrading, and i have the three raw files made with itsutils. Will this do?
Also, could you please explain why i need to sim/cid unlock it? The device itself is not branded at all, i believe it's only locked to the provider's sim, and that's all. Does sim /cid unlocking cover that or is it about something else?
Thanx!
Sim unlocking = you can use other sims
CID unlocking = you can use other roms (maybe why your update is crashing)
HARDSPL = One less chance of bricking your device
as your device is still currently up and running im guessing you can do it all via that rom.
Ok, just so i don't missunderstand you, can i do what you suggested, but without flashing the carrier's rom?
you can, however you may encounter problems with wm6.1 in the future (hard resets etc)
OK to clear this thread up....
...make sure you have flashed HardSPL before continuing then...
...redownload the ROM it sounds like it has become corrupted whilst being downloaded so make sure you unzip the whole thing to a folder first then try it.
did everything like kingsizeriz told me, except i did it on the existing rom. uploaded the same rom i tried before and it worked like a charm. me and mates have been fiddling with it the whole evening and noticed no problems so far. Thanx for the help, much appreciated
Btw, one last question, is NK.EXE supposed to be 0 bytes?
Hi @ all,
after reading many and many threads here in this forum (and even others) I thought I gathered enough information for starting with update my T-Mobile MDA. The original image shows the following versions:
ROM-Version: 1.35.111.13
ROM-Date: 03/14/08
Radio-Version: 1.58.21.24
Protocol-Version: 25.65.30.04H
I saw that HTC offers an official WM6.1 build for this device and since I'm running WM6.0 with many obvious bugs (and slowlyness) I decided it can't get worst.
Fortunately I found the download-link here in this forum for the official WM6.1 Professional build in german, because HTC denies access telling me that this build can't be installed on a foreign (OEM) device. After downloading the image from the link I've found here I started the updater. But even this updater refused attempts telling me that the VendorID is wrong.
As stated before I read and read and read before trying the update - but it went wrong finally. By using uSSPL 1.16 I started the update process with the original HTC updater. Everything went fine until 15% then the updater again quotes that my device has a wrong VendorID. From that moment on I saw only the rainbowscreen telling me the following:
(Top right corner: RUUNBH)
NIKI200
SPL-1.18.0000
CPLD-4
I assume that the SPL on my device is guilty of deciding which firmware to install. Luckily I found a way of still booting my device using MTTY 1.42 and sending "boot" as command. Then it booted - but I have to do that right now every time I boot up the device - it doesn't bootup by itself :-(
Here's my first question: How can I achieve that the device boots up completely and automatically again without sending a "boot" command?
I certainly still want to upgrade to ANY better OS than the current one - it just sucks! So, here're my further questions and I know there are many, many threads here and I think that read all of them according to this, but I'm still confused:
Q: What do I need as prequisites for updating this T-Mobile branded device with the official HTC Image? I'm sure SPL 1.15 and 1.16 are "too old"(??) for dealing with this brand new release firmware, right? Maybe that was the cause why the update failed.
Q: Is it necessary to install a hardSPL before starting the update? I would prefer NOT to modify the hardSPL because if I brick the device totally, I lose warranty - I just want to prevent that! If anyone tells me here, that there's really no risk of flashing hardSPL and that this certainly will work (due to his/her own experience) then I sure would proceed. BTW: I'm a newbie to this forum here and by dealing with consumer PDAs and flashing them in general, but I'm working for a company who's manufacturing such devices for the industry in rugged environments as technical supporter/consultant therefore the basics an beyonds are clear to me - only this specific field is new.
Final question: According to my questions above, a structured list (Step-By-Step) of what is necessary to do to "convince" this T-Mobile device of loading foreign Firmware is highly appreciated!
Thanks in advance for your support!
Reingucker
If you can actually get in with the boot command from mtty you're in luck.
If you're getting the vendor ID error then you'll need to unlock the device (see http://forum.xda-developers.com/showthread.php?t=395945)
You don't need to install a hard spl, once you're unlocked and booted copy over the sspl file from the spl thread to your device (the device itself and not the SD) then take out your SD and run the sspl
This will then reboot the phone to bootloader and allow the rom to be flashed without a hard spl. As the new rom comes with spl 1.22 this will be installed.
WOW - thanks very much for this fast response!!
I've read the article of the link you quoted. There it is said, that I have to flash hardSPL 1.15 before proceeding. So I guess, there's no way around of modifying the device in such a manor that it would be noticed in cases of warranty repair, right?
Cheers,
Frank
hardSPL is an advisable safeguard while flashing but you can always revert to a stock SPL afterwards if you need to.
If you went to SPL 1.22 you'd need to do that anyway if you needed to return the device as T-mobile don't have a rom with that spl yet.
Dear randomelements,
THANKS VERY MUCH for your fast response and help!
FINALLY I DID IT!!!
BUT :-D one question left:
Now I've flashed the official HTC Image with WM6.1.
Is there any way of getting the T-Mobile splash screen back onto
the device? I've found the splash-screen flasher, but do you know
where to get the T-Mobile splash-image?
Thanks again very much,
Reingucker
There are some t-mob roms around for download (links are somewhere in the forum)
Using the nbh tools the splash screens can be extracted from that and repackaged.
I'll have a look when I get home tonight.
OK, great - thanks!
In the meanwhile I'm searching around for this as well. If I'm faster I'll let you know.
Since my device is "still" on hardSPL 1.15, would you recommend to upgrade to 1.22 or is that not necessary - or, better to say, what would be the advantage resp. the disadvantage?
Cheers,
Frank
Reingucker said:
OK, great - thanks!
In the meanwhile I'm searching around for this as well. If I'm faster I'll let you know.
Since my device is "still" on hardSPL 1.15, would you recommend to upgrade to 1.22 or is that not necessary - or, better to say, what would be the advantage resp. the disadvantage?
Cheers,
Frank
Click to expand...
Click to collapse
I have 1.22 for two days now an it is so fast. I think there are no disadvantages
Reingucker said:
OK, great - thanks!
In the meanwhile I'm searching around for this as well. If I'm faster I'll let you know.
Since my device is "still" on hardSPL 1.15, would you recommend to upgrade to 1.22 or is that not necessary - or, better to say, what would be the advantage resp. the disadvantage?
Cheers,
Frank
Click to expand...
Click to collapse
It's usually better to have a later SPL and everyone is saying that 1.22 makes the device run smoother.
Liquid Silver has created a 1.22 HardSPL so you might like to give that a try - I've been using it without issues:
http://forum.xda-developers.com/showpost.php?p=2778832&postcount=429
*** Request Completed ***
OK guys, especially randomelements,
I'm through! I did everything I wanted to do... Time to setup the device aknew.
Thank you very, very much!!
Hope the device works more stable now.
Have a great day!
Reingucker
Grrrrr.....
Okay, one more thing....
I tried to replace the "animated.gif" in the /windows directory.
But the file is a system file and I always get an error message
that this operation isn't allowed.
How can I replace this?
Thanks in advance,
Reingucker
You can replace it with Resco Explorer or Total Commander, because these File Explorers can overwrite system files!
*** Request Now Really Completed ***
OK, thanks for the hint....
I achieved it by changing the registry entry that links to the file...
However... learning that these two apps can do that helps certainly...
Thanks again and....
GOOD BYE for today!!
Cheers,
Reingucker
hardspl 1.6 or 1.22 is good?
hello mate
can you post a reply how excactly did you solve the above isue?
As i am havving the sane problem and cannot fix it.
Please help if you do remember how you solved this
rob
Reingucker said:
Hi @ all,
after reading many and many threads here in this forum (and even others) I thought I gathered enough information for starting with update my T-Mobile MDA. The original image shows the following versions:
ROM-Version: 1.35.111.13
ROM-Date: 03/14/08
Radio-Version: 1.58.21.24
Protocol-Version: 25.65.30.04H
I saw that HTC offers an official WM6.1 build for this device and since I'm running WM6.0 with many obvious bugs (and slowlyness) I decided it can't get worst.
Fortunately I found the download-link here in this forum for the official WM6.1 Professional build in german, because HTC denies access telling me that this build can't be installed on a foreign (OEM) device. After downloading the image from the link I've found here I started the updater. But even this updater refused attempts telling me that the VendorID is wrong.
As stated before I read and read and read before trying the update - but it went wrong finally. By using uSSPL 1.16 I started the update process with the original HTC updater. Everything went fine until 15% then the updater again quotes that my device has a wrong VendorID. From that moment on I saw only the rainbowscreen telling me the following:
(Top right corner: RUUNBH)
NIKI200
SPL-1.18.0000
CPLD-4
I assume that the SPL on my device is guilty of deciding which firmware to install. Luckily I found a way of still booting my device using MTTY 1.42 and sending "boot" as command. Then it booted - but I have to do that right now every time I boot up the device - it doesn't bootup by itself :-(
Here's my first question: How can I achieve that the device boots up completely and automatically again without sending a "boot" command?
I certainly still want to upgrade to ANY better OS than the current one - it just sucks! So, here're my further questions and I know there are many, many threads here and I think that read all of them according to this, but I'm still confused:
Q: What do I need as prequisites for updating this T-Mobile branded device with the official HTC Image? I'm sure SPL 1.15 and 1.16 are "too old"(??) for dealing with this brand new release firmware, right? Maybe that was the cause why the update failed.
Q: Is it necessary to install a hardSPL before starting the update? I would prefer NOT to modify the hardSPL because if I brick the device totally, I lose warranty - I just want to prevent that! If anyone tells me here, that there's really no risk of flashing hardSPL and that this certainly will work (due to his/her own experience) then I sure would proceed. BTW: I'm a newbie to this forum here and by dealing with consumer PDAs and flashing them in general, but I'm working for a company who's manufacturing such devices for the industry in rugged environments as technical supporter/consultant therefore the basics an beyonds are clear to me - only this specific field is new.
Final question: According to my questions above, a structured list (Step-By-Step) of what is necessary to do to "convince" this T-Mobile device of loading foreign Firmware is highly appreciated!
Thanks in advance for your support!
Reingucker
Click to expand...
Click to collapse
hello mate
can you post a reply how excactly did you solve the above isue?
As i am havving the sane problem and cannot fix it.
Please help if you do remember how you solved this
rob
You wrote you need an update from WM6.0 to WM6.1,
i think you are a german user, so if you want a original WM6.1 from T-Mobile try this <<link>>
Its the T-Mobile Update to WM6.1 including the start splash screen
I recently flashed my Wizard with TNT WM6 and I am getting all kinds of problems so I am wanting to bring it back to Wizard Love so I can attempt TNT's again and avoid a "bad flash".
My question is, do I need to put the phone in the bootloader (i.e. the 3 colored bars?) or can I flash it with the phone loaded and everything. I am using RUU to flash.
Or do I need to use ShellTool?
If its a G3,then simply hook up the phone with pc and run the RUU,it'll reflash,there's no need to get into Bootloaders (RGB Screen).
But if its a G4,then how did you upgrade first,if through HardSPL,then again just hook up and run the RUU,well,if you used Shelltool,then there's no need to go through again with Shelltool.Get the phone HardSPL once,then you can flash any rom as much as you like
I used shelltool for the first flash, but it kind messed up so I had to redo Wizard Love with the RGB boot loader.
If I remember correctly by "messed up" I think it froze during flashing.
Yes I do have a G4
well do as zabardast_1's has said and flash HardSPL to your g4 wizard and then you can just flash another cooked rom
and added....Don't use ShellTool again even you are using a G4! RUU can be used on G4 directly given that you have installed HardSPL and you are going to flash a custom ROM posted here.
So even though ShellTool kinda messed up, my device is still HardSPL'ed?
To be safe you can flash using Softspl , that is the way i flashed few times althouhg my wizard was hardspl and it was ok. If you have hardspl try using Mun's RUU . Both methods worked fine for me.
Ok, I just re-flashed my G4 with Wizard Love using the RUU that it came with and everything seemed to work fine. Does this mean that my HardSPL was successful? See what I think had happened was I flashed TNT's rom with ShellTool and not RUU after I had HardSPL'ed my device. Could that have had something to do with it?
Thanks for all the help so far, you guys have been very knowledgeable.
Read this maybe its helpfull for you http://forum.xda-developers.com/showthread.php?t=435852
Mortifix said:
Ok, I just re-flashed my G4 with Wizard Love using the RUU that it came with and everything seemed to work fine. Does this mean that my HardSPL was successful? See what I think had happened was I flashed TNT's rom with ShellTool and not RUU after I had HardSPL'ed my device. Could that have had something to do with it?
Thanks for all the help so far, you guys have been very knowledgeable.
Click to expand...
Click to collapse
Ah! You are mixing up all three methods Shelltool,RUU,HardSPL together,they all are different methods to flash a rom.Shelltool is a different method then RUU(RomUpdateUtility) and HardSPL(Patched IPL/SPL) is altogether a different process to flash and upgrade a G4 device.
Try to read all about these methods for better understanding.
Here, I wud not like to go into details,you can read about these methods in their respective threads.
Flashing wizard_love rom doesn't mean your phone is HardSPL'd ? No,wizard_love rom is a patched rom,it'll flash to any G4 device with original official IPL/SPL (Bootloaders) running on it,but if the phone is HardSPL'd,it flashes patched IPL/SPL,thus tricking it to think its semi-permanent CID unlocked,after this its possible to flash any wm6.1 custom rom.But flashing a wizard_love,it still has its own official IPL/SPL,but you cannot upgrade to any wm6 rom as its not CID unlocked.As a G4 device cannot be CID unlocked like a G3 phone,so KardSPL is applied to make it trick into semi-permanent CID unlock,whereas,its in fact CID locked,but here its possible to upgrade to any wm6 rom,hope you got my point !!!
So,if you want to upgrade to wm6 or flash TNT wm6.1 rom,you have to first apply HardSPL,it'll change the IPL/SPL of the phone,only then you can flash TNT wm6.1 rom
Ok yeah thanks for clearing that up for me I was trying to update my phone with the RUU that came with TNT .20273, but it kept giving me an Error 300 which I am assuming that means its not HardSPL'ed. So from the sounds of it, I would probably like to get my phone HardSPL to I can flash any new roms that come out. I was under the assumption that ShellTool was HardSPL'ing my phone, but I guess not. Before I proceed to the next step, is this the instructions I should be following?: http://forum.xda-developers.com/showthread.php?t=332320
EDIT:
Ok, I went ahead and HardSPL'ed my device. I followed the instructions on that thread and everything seems to be working. I get SoftSPL: something something olipro so I am guessing thats good. I am still having problems when I go to flash TNT. I am trying to use the RUU that is included with TNT, but I keep getting Error 300 (Invalid Update Tool).
ok,download 'Mun's RUU' from the HardSPL thread you just posted above and replace the RUU in this zipfile with RUU in the TNT rom and run this replaced RUU,it'll work and flash the rom
I have everything all set and I am rocking TNT .191213. Thanks for all the help guys!!
Hi guys,
After stumbling across a guide on how to get android 2.2 on to my HD2 i thought it was time to let the old wm6.5 leave my phone for good. The guide is easy enough to use i guess but I'm struggling a bit with getting my SPL down to 2.10.0000 to install HSPL3 on my phone. After reading and googeling in this forum, i have learned new words like radio and what not, but it is still not very clear to me how to downgrade my SPL. My SPL is now at a staggering 3.03.0000.
Would be nice with a bit of guidance, a link to the right guide for me to use or something. Its really amazing things you are doing here.
Cheers guys
Read this thread http://forum.xda-developers.com/showthread.php?t=893948
Russ
Thanks for a quick reply.
I have already looked at a few of these guides but they get me a bit confused. In order to install HSPL3 i need to get my SPL down to 2.10, and in order to downgrade radio or ROM, i need to have the HSPL3 or something similar hacking thingy. In the link i got from your post its recommended to use Radio version 2.15.50.14, that might or might not have an SPL below 2.10. If i could get a simple guide or a bit of assistance on how to get my SPL suitable for HSPL3, everything will be hunky dory.
cheers
jubocrisp said:
Thanks for a quick reply.
I have already looked at a few of these guides but they get me a bit confused. In order to install HSPL3 i need to get my SPL down to 2.10, and in order to downgrade radio or ROM, i need to have the HSPL3 or something similar hacking thingy. In the link i got from your post its recommended to use Radio version 2.15.50.14, that might or might not have an SPL below 2.10. If i could get a simple guide or a bit of assistance on how to get my SPL suitable for HSPL3, everything will be hunky dory.
cheers
Click to expand...
Click to collapse
Install a previous stock ROM; a version before the 3.14 stock ROM.
make sure that the stock ROM match your device aria/language
Cheers, just what i needed, a simple answer. So now i guess i am almost finished but encountered another problem:
Problem: On some devices MAGLDR won't boot at all (HTC logo stay after turn on).
Solution: Install HSPL208.
Don't understand how to install the hspl208 instead when my phone is not to keen on booting. If i get a little assistance with this i guess i should be able to finally get Android on my phone
hurrah,
After dicking around a bit i managed to sort it out. Cheers guys and thanks for all the help