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
Related
Flashed WMXL 0.20 yesterday. All fine. I stupidly installed a WM2003 program that seems to have edited the graphics driver. Now the thing wont boot past the HTC splash screen. I've tried flashing, same rom, different t-mobile roms etc. No luck, always same error.
What gives?
Installing a program does not usually brick a device.
And if your graphics driver has been modified,I suggest you do a hard reset on your device.
If that is not helping,please provide your SPL and Radio version,also Cid status and so on ,see who can help you here.
Spuddy said:
Flashed WMXL 0.20 yesterday. All fine. I stupidly installed a WM2003 program that seems to have edited the graphics driver. Now the thing wont boot past the HTC splash screen. I've tried flashing, same rom, different t-mobile roms etc. No luck, always same error.
What gives?
Click to expand...
Click to collapse
Sounds like you're flashing & writing before reading. I'm guessing you went straight to the WM6 rom and didn't do any of the SIM or CID unlocking. Read the following threads and you should discover what you need and probably loads more too...
The Hermes Bible - points to all you need to know
http://wiki.xda-developers.com/index.php?pagename=HTC_Hermes
Common upgrade problems (including yours)
http://wiki.xda-developers.com/index.php?pagename=Hermes_UpgradeProblems
Good luck in your discoveries
Thanks for your advice. I have managed to flash a hungarian T-Mobile ROM to my device and am now going to make is supercid so I can put WM6 back on. Thanks again.
Spuddy said:
Thanks for your advice. I have managed to flash a hungarian T-Mobile ROM to my device and am now going to make is supercid so I can put WM6 back on. Thanks again.
Click to expand...
Click to collapse
Congrats and have fun flashing - it's addictive.
I'd suggest that you read and try Olipro's Hard-SPL before you go any further. This appears to be the answer to many of our prayers because you should be able to recover a bad radio flash. (I'm guessing that the 1.04 version will become most popular)
Hard-SPL, Or How to Not Brick Your PDA Ever Again
http://forum.xda-developers.com/showthread.php?t=296722
Spuddy said:
. . . a WM2003 program that seems to have edited the graphics driver . . .
Click to expand...
Click to collapse
What program was that, if you don't mind my asking?
abubasim said:
What program was that, if you don't mind my asking?
Click to expand...
Click to collapse
DotPocket.
http://www.dotpocket.com/pocket-pc-software.html
I got this phone a few days ago and I'm already on a modding spree.
Today, I upgraded to SPL-1.40.01ipro and also upgraded the radio to 1.38.00.10.
To continue my modding spree, I wanted to update to the new Cingular ROM (2.06.502.3). I downloaded the package and launced it. I went through the usual ROM upgrading steps (checkboxes, etc.). Finally, at the last screen (before the status bar) I clicked ok, and it popped up a message saying "Verifying PDA information, etc." The phone disconnected from ActiveSync (even quit the program), Windows made the disconnecting sound, and then it made the connecting sound, and my phone went into bootloader mode. It then stayed there until a window popped up on my monitor saying "Error [260]: Update Error".
I searched about Error 260 and all I came up with was program conflicts. I rebooted the computer and tried to exit pretty much every program. Do I not have enough space on the phone?
Anyone have any idea how I can fix this? I searched alot. Thanks
Edit: I am using WinXP Pro, so the Vista issue has no concern.
If it is a standard RUU updater provided by Cingular you need to disable USB connections in activesync first.
Using the customRUU updates provided here (all the WM6 builds and HardSPL...and radio) its the opposite, but try unticking "allow usb connections" in connection settings (in activesync on your pc).
I assume it's the standard RUU, as it does not say CustomRUU on the file.
Edit:
I am using this one:
http://wiki.xda-developers.com/index.php?pagename=Hermes_Upgrades
Cingular English CWS__001 2.06.502.3 02/02/07 ?? 1.33.31.00 32.66.7020.10H 15671.3.3.0 3.3 1.09 108
Should I just do the Ext. ROM ones?
Also, wouldn't disabling the USB connection result in a connection error (since it's not "connected")?
By the way, your upgrade guides are excellent! They really helped with the radio and SPL update.
A few minutes ago, I tried the the SIM unlock/CID unlock .v3 and it does the same thing. Error [206].
justsignbythex said:
I assume it's the standard RUU, as it does not say CustomRUU on the file.
Edit:
I am using this one:
http://wiki.xda-developers.com/index.php?pagename=Hermes_Upgrades
Cingular English CWS__001 2.06.502.3 02/02/07 ?? 1.33.31.00 32.66.7020.10H 15671.3.3.0 3.3 1.09 108
Should I just do the Ext. ROM ones?
Also, wouldn't disabling the USB connection result in a connection error (since it's not "connected")?
By the way, your upgrade guides are excellent! They really helped with the radio and SPL update.
Click to expand...
Click to collapse
I think i might have been confused with using the mtty program, never mind.
The reason your RUU will not work is because you have an upgraded SPL (HardSPL) on your device and it is not recognised by the operator RUU.
The procedure to flash the cingular ROM to your device is the same as in my WM5 Downgrade Guide.
(you might not understand this until youve read the guide)
Just package the OS,Extrom and splashscreens as in the guide and flash with the CustomRUU tool, you will be fine. (follow the guide its all in there). Just to add to that when you come to flashing the repackaged ROM (at the end of the guide) select the 'Autodetect' option when the flashing utility asks what SPL you have.
Thanks for the help so far!
I read another thread: http://forum.xda-developers.com/showthread.php?t=293085&highlight=error+260
that if I update the ROM a certain way, I will not be able to upgrade the radio afterwards. Is this true for your WM5 downgrading guide? (I am upgrading to AKU3.3 by the way)
Just want to make sure before I do it.
justsignbythex said:
Thanks for the help so far!
I read another thread: http://forum.xda-developers.com/showthread.php?t=293085&highlight=error+260
that if I update the ROM a certain way, I will not be able to upgrade the radio afterwards. Is this true for your WM5 downgrading guide? (I am upgrading to AKU3.3 by the way)
Just want to make sure before I do it.
Click to expand...
Click to collapse
You can change the radio without issue dude. Aslong as you have HardSPLv6 (1.40.olipro) then we will have no problem sorting you out.
The guide is awesome!
But when it comes to this window:
Follow the RUU instructions as usual to flash the WM5 ROM. Select 'Autodetect' when the RUU asks which SPL version you have.
when I select Autodetect it says it cannot query the device and it advises me to pick SSPL. Should I just do that? Activesync is running and connected.
justsignbythex said:
The guide is awesome!
But when it comes to this window:
Follow the RUU instructions as usual to flash the WM5 ROM. Select 'Autodetect' when the RUU asks which SPL version you have.
when I select Autodetect it says it cannot query the device and it advises me to pick SSPL. Should I just do that? Activesync is running and connected.
Click to expand...
Click to collapse
select the third option down, then tick hardspl. sometimes it doesnt detect correctly
Thanks alot! Your help has been indisposable.
It's currently flashing as we speak. Will update you as it's done.
It works great, thanks!
justsignbythex said:
It works great, thanks!
Click to expand...
Click to collapse
No probs dude
Might wanna give the threads on HardSPL, CustomRUU and maybe the (hermes) rom koch???
The info there is great for future releases of ROM (and also for the techniques used in my guide)
I have same problem, error 260. At same time, after final check. I have made my .nbh with this guide (from Original ROM 2.11.255.1 03/07/07 and 2.05.255.1 01/17/07 ).
I have tryed to update with that guide that I mentioned before on two different computers Win XP sp2 and Win 2000. I have ActiveSync 4.2 on PC and the phone is Vodafone v1605 (with only rom that it has) and I have updated bootloader to 1.40.olipro.
Does this RUUWrapper.exe work with this .nbh allso? I want to upgrade everything to newest, or should I? I didn't find userguide for RUUWrapper or when it should be used.
I also tryed to flash ROM with "ModifiedRUUUpdater-V2", it went little bit further, but it hanged in 0% with error 244
Error 260 continuted
hello
I had the same issue, Error: 260. I have a hermes TyTn, WM6. I have tried to follow the steps on the downgrade to WM5 but have some issues. There is a warning to do the HardSPL first because this would prevent the unit from being bricked, but i am doing this because I can't do the Hard SPL. Secondly the Hermes RomKoch by dutty can not be found at the link provided. please help!
Try this method:
First go to this mode:
http://rt002nf0.eresmas.net/TodoPDAs200/bootloader01.jpg
And finally run ruuwrapper. This helps me.
error 260
I am getting the same error 260 message when I try to upgrade as well. I read several threads with different solutions and none of them worked for me. The link in this forum pointing to the downgrade guide does not work. I've tried on 2 different Vista Ultimate machines with no success. The funny thing is, I upgraded one of my 8525s on one of these machines with no problem, but this new 8525 I received today isn't playing nice. Any suggestions would be greatly appreciated.
Thanks
Install Hard SPL V7, then use sd card method to install ROM.
Go to page 116, post 1160 on this thread - http://forum.xda-developers.com/showthread.php?t=296722
for sd card method for Hard SPL.
Just drop the steps using sspl.exe when flashing roms as you would now have Hard SPL installed.
You need a 2Gb or less sd card formatted FAT32 and make no spelling mistakes when renaming .nbh file to hermimg.nbh..
Cheers...
But how do I get the Hard SPL V7 installed. That is the version I was trying to install. I go through the steps and once my phone gets to the bootloader, it disconnects from the WMDC and then the error message. So I need to get past the Hard SPL V7 install first. Any ideas on that?
Thanks ultramag69
ultramag69 said:
Install Hard SPL V7.
Go to page 116, post 1160 on this thread - http://forum.xda-developers.com/showthread.php?t=296722
for sd card method for Hard SPL.
You need a 2Gb or less sd card formatted FAT32 and make no spelling mistakes when renaming .nbh file to hermimg.nbh..
Cheers...
Click to expand...
Click to collapse
As I said before
Thanks ultramag69 it worked. I appreciate your help. Do you also have a good link for the Windows Mobile 6 download?
Thanks again.
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
HTC Wizard SoftSPL (sSPL) For G4 Wizards
FAQ:
What is SoftSPL?
-SoftSPL is a patched SPL that will temporary unlock your CID (untill reboot).
-It will be copied to your device and loaded (BUT NOT FLASHED!), the device is tricked to believe it has SuperCID (More accuratly g_cKeyCardSecurityLevel will be 0 ).
Why Temporary?
-1st because of warranty, since there is no CID block written, warranty isn't void
-2nd with this tool it's not necesarry to have a permanently unlocked CID.
-3rd it's safe, it doesn't flash CID block or IPL/SPL by it's own, but choose your ROM you want to flash wisely!
Isn't shelltool the same?
-no shelltool will strip the rom, and then flash it with pdocwrite, where sSPL is a bootloader which says it has supercid, thus tricking the RomUpdateUtility.
But can I make it permanent?
-Yes it can make it semi permanent, with HardSPL (it's the same trick, but now a patched SPL is flashed to device).
What does Soft SPL change on my device?
-nothing, it's loaded into memory. Only the ROM you choose to flash with the RUU will change your device.
USE AT OWN RISK
How To use?
If you don't know what a G4 safe ROM is, don't even try to upgrade!
WILL NOT WORK IN VISTA
-Unzip SoftSPL.zip
-copy the nk.nbf file from desired G4 safe ROM to the SoftSPL folder
-Fully Connect to ActiveSync
-Run START-sSPL.exe
-the Screen of your Device will turn white, don't panic, this is normal
-SoftSPL will now run the RUU, proceed as usual (the screen of the wizard will stay white during whole process, again don't panic!)
DO NOT PROCEED WITH RUU if the screen isn't WHITE, OR when in bootloader SPL version isn't 2.21.olip
G4 Safe means:
-No IPL/SPL and no Extended ROM.
Many Thanks Go to:
Olipro: For patching the latest SPL
SAA044: For testing all the versions, and keeping his head cool when the first hardSPL killed his Wizard (beyond repair!), and for keeping on testing the new versions with his brand new Wizard!
Whiterat: For all his technical and moral support, without him it wouldn't have excisted.
Pof & Des: From whom I took the idea, and some of the scripts.
NB. This sSPL is not for G3, it will proceed with updating, but in the end OS will not be written, tested it with my own G3. Beware of the SPL/IPL (there is danger to flash G4 spl on your G3 due to the fact you are using a G4 sSPL, the RUU will probably think it's running from a G4 device!).
NB.2 If you want to mtty in stead of flashing a ROM, place mtty in the folder and rename it 2.exe
[EDIT:12-september 19:54] I updated the file for a confirmed working RC1 (v0.1) WITH the missing dll [/EDIT]
[edit] 23.09.07
Some people reported that enable rapi does not always work, if that is the case for you, you can try to replace the original enable-rapi with the one attached here.
[/edit]
Well Done Eqx and Well Done to everybody else involved.
I look forward to giving this a go.
This is great work.. I will try this first thing in the morning..
Many Thanks
First of all many thanks for ur effort.
second-should i back to the love room befor flashing this room or i can flash directly from any room?
third - with shell tool if any problems happend i can back to love room and retry again. is it possible here also?
forth - is soft room = new room without spl & ipl?
awaiting ur reply & thanks again for ur hard work
First of all many thanks for ur effort.
second-should i back to the love room befor flashing this room or i can flash directly from any ROM?
third - with shell tool if any problems happend i can back to love room and retry again. is it possible here also?
forth - is soft (safe?) ROM = new ROM without spl & ipl?
awaiting ur reply & thanks again for ur hard work
Click to expand...
Click to collapse
First, you're welcome.
2nd Please keep in mind you need IPL/SPL 2.xx.00001 for WM6 (use the latest officcial one from your provider)
3rd It's not different from an ordinary flash, you can go back to any ROM that is G4 safe.
4rd G4 safe means no IPL/SPL (Extended ROM hasn't been tested yet)
Thanks bro
thanks bro for ur quick reply & i will try it as soon as TNT5 release.(inshaa-allah)
it's sound pretty easy ... i'mma try it 2marow as well .
thanks for everything
where r u guys?
42 person's were downloded without any comments. your feedback is very important to other's.
yalla come on
[solution] G4 SoftSPL Flash any ROM to CID locked device
Thanks!! I wil post the results a soon as i flash a new ROM
Thanks!! It's 2:33 in the morning where I live and I just found this. Am trying now. Will report results.
I tried it and it didn't work. But it was probaly my fault.
Would anyone be so friendly posting some G4 Save-Roms. I think a lot of us guys aren't sure wich are save and wich aren't.
Thank you
thomme
My way
For anyone interested i did it like this!!!!
1. Flashed back to latest origenal rom.
2. Copied the file into shelltool directory to verify the ipl/spl status. (Normally most roms here dont have ipl/spl in it, never hurts to check though.
3. Used wizard service tool to make sure the enable rapi command is installed on device.
4. Copied the desired nk.nbf file into softspl (root) folder.
5. Ran the main exe file without errors and had wm6 flashed successfully.
saa044 said:
For anyone interested i did it like this!!!!
1. Flashed back to latest origenal rom.
2. Copied the file into shelltool directory to verify the ipl/spl status. (Normally most roms here dont have ipl/spl in it, never hurts to check though.
3. Used wizard service tool to make sure the enable rapi command is installed on device.
4. Copied the desired nk.nbf file into softspl (root) folder.
5. Ran the main exe file without errors and had wm6 flashed successfully.
Click to expand...
Click to collapse
The only difference now is that there is a ROM folder now
hmmm
thomme said:
I tried it and it didn't work. But it was probaly my fault.
Would anyone be so friendly posting some G4 Save-Roms. I think a lot of us guys aren't sure wich are save and wich aren't.
Thank you
thomme
Click to expand...
Click to collapse
Most of the roms on this page should be G4 safe.
http://wiki.xda-developers.com/index.php?pagename=wizard_WM_6
The ones I have tested up till now is the wrcx, TNT and SNE 3 ones. Try what I said in my previous post, that might also work for you. What error did you get by the way, a 620 errors that said it could not communicate with device?
the-equinoxe said:
The only difference now is that there is a ROM folder now
Click to expand...
Click to collapse
yup, that is nice.
I tried and it didn't work at all. I tried 3 times already from the time I downloaded the rar and still no success.
First time I tried it I had Titanium 2 installed and it was a no go even though the IPL/SPL were 2.26.0001
Then I tried twice using the official T-Mobile rom with IPL/SPL 2.26.0001 and followed the directions provided to a t and no success...
I am going to try once more tonight since it is 3:25am and then im giving up for the night.
Oh and I am trying to flash faria's rom. Think that might have something to do with it?
dharvey4651 said:
I tried and it didn't work at all. I tried 3 times already from the time I downloaded the rar and still no success.
First time I tried it I had Titanium 2 installed and it was a no go even though the IPL/SPL were 2.26.0001
Then I tried twice using the official T-Mobile rom with IPL/SPL 2.26.0001 and followed the directions provided to a t and no success...
I am going to try once more tonight since it is 3:25am and then im giving up for the night.
Oh and I am trying to flash faria's rom. Think that might have something to do with it?
Click to expand...
Click to collapse
Can you give us more detail to where you get the error and what it is? Also did you flash origenal rom with softspl or bootloader? Oh and if your device asks for permission to load the dll files it wont work.
the-equinoxe said:
4rd G4 safe means no IPL/SPL (Extended ROM hasn't been tested yet)
Click to expand...
Click to collapse
I have a CID Locked G4 and I can flash using RUU any ExtendedRom
contact me
dharvey4651 said:
I tried and it didn't work at all. I tried 3 times already from the time I downloaded the rar and still no success.
First time I tried it I had Titanium 2 installed and it was a no go even though the IPL/SPL were 2.26.0001
Then I tried twice using the official T-Mobile rom with IPL/SPL 2.26.0001 and followed the directions provided to a t and no success...
I am going to try once more tonight since it is 3:25am and then im giving up for the night.
Oh and I am trying to flash faria's rom. Think that might have something to do with it?
Click to expand...
Click to collapse
Contact me via msn at [email protected] I will try me best to help u, but eventually EquinoXe is the master here.
saa044 said:
Can you give us more detail to where you get the error and what it is? Also did you flash origenal rom with softspl or bootloader? Oh and if your device asks for permission to load the dll files it wont work.
Click to expand...
Click to collapse
Here is exactly what my device is doing:
I flash back to the official T-Mobile WM5 rom for the 2.26.0001 IPL/SPL adn then let customization finish and then try to softSpl but with no success. On my MDA, it asks me to confirm something and the screen never turns white like it is supposed to do.
I have tried this several ways and on 2 different roms.
I have tried flashing back to T-Mobile official but skip customization 2 times and use softSpl to flash faria's rom and it failed. I tried once after waiting untill customization is complete and installing faria's rom and it failed once again.
I also tried installing cert_SPCS.cab and installing enablerapi.cab prior to running softSpl 2 different times, once before customization and once after customization. both times failed. this time I was using Black Diamond 2.0 instead of faria's rom to see if it was just the rom.
Not once did I ever get the white screen and not once did it flash successfully using this method.(At least not for me)
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.