Related
Ok I've flashed close to a dozen times using various great ROMS everyone has provided and never had a problem. Today I realized that ATT/HTC released their official ROM yesterday and I thought I would give it a try. I followed their instructions but it did not work.
My phone looked as though it was updating and it got stuck at 11%. Followed the instructions to recover and it still did not work. Now my phone is stuck at the Triple Color Bar screen and I cannot do anything.
Did I brick my phone?
Can I use some of the options to try to unbrick in the xda wiki?
Thank you in advance.
- Monty
Have you tried flashing a different rom or using a different pc to flash with?
i managed to revive mine from that state the key is getting the usb to let you update again dont plug in the cable until after the ruu is looking for the connection might take a couple tries but that worked for me.
Hi
Try this:
1) Turn your phone off completely
2) Hold the side OK button and the power button, at the same time push the reset button at the bottom with your stylus.
3) this should get you into the bootloader (the three colour screen)(dont be lazy and just let it load into the bootloader, actually run the key sequence ive just mentioned!)
4) on your PC run the update, i would reccomend the latest official update for your handset, BUT, do the following:
a) Make sure you have WinRAR installed
b) Right click on the update file you have just downloaded
c) 'Extract' the update file to the folder it makes
d) within that folder should be ANOTHER executable file that has the same icon as the original update
e) Extract this file again
f) open the folder it makes and within that there should be a RUUSIGNED.NBH and also the RUU utility itself
5) Run the update utility in the second folder
6) once the utility has loaded, plug your phone in (the text will change from 'SERIAL' to 'USB')
7) proceed with the update and see what happens
hope that helps
good luck.
MontyV77 said:
Ok I've flashed close to a dozen times using various great ROMS everyone has provided and never had a problem. Today I realized that ATT/HTC released their official ROM yesterday and I thought I would give it a try. I followed their instructions but it did not work.
My phone looked as though it was updating and it got stuck at 11%. Followed the instructions to recover and it still did not work. Now my phone is stuck at the Triple Color Bar screen and I cannot do anything.
Did I brick my phone?
Can I use some of the options to try to unbrick in the xda wiki?
Thank you in advance.
- Monty
Click to expand...
Click to collapse
You should not update using the Oficial ROM release Update because you put in the boot loader from here (Hard-SPL-V7) and it will try over righting the entire rom if you do and is probably what messed up your update attempt. Use Dutty's NBH tool and just decompile the NBH of the official rom, then recompile the windows, splash screens and radio into a new NBH then flash using the RUUwrapper from this site to flash the phone.
TooSharp said:
Have you tried flashing a different rom or using a different pc to flash with?
Click to expand...
Click to collapse
Yes I've tried two different Official ATT ROMs and on different computers but same problem. Actually the only one that will attempt to start loading are the ATT ROMs and none of the cooked ROMs here are loading. Maybe that has something to do with the way they are packaged.
Jefem24 said:
i managed to revive mine from that state the key is getting the usb to let you update again dont plug in the cable until after the ruu is looking for the connection might take a couple tries but that worked for me.
Click to expand...
Click to collapse
Yeah I've done this now over a dozen times since yesterday and still no luck.
duke_stix said:
Hi
Try this:
1) Turn your phone off completely
2) Hold the side OK button and the power button, at the same time push the reset button at the bottom with your stylus.
3) this should get you into the bootloader (the three colour screen)(dont be lazy and just let it load into the bootloader, actually run the key sequence ive just mentioned!)
4) on your PC run the update, i would reccomend the latest official update for your handset, BUT, do the following:
a) Make sure you have WinRAR installed
b) Right click on the update file you have just downloaded
c) 'Extract' the update file to the folder it makes
d) within that folder should be ANOTHER executable file that has the same icon as the original update
e) Extract this file again
f) open the folder it makes and within that there should be a RUUSIGNED.NBH and also the RUU utility itself
5) Run the update utility in the second folder
6) once the utility has loaded, plug your phone in (the text will change from 'SERIAL' to 'USB')
7) proceed with the update and see what happens
hope that helps
good luck.
Click to expand...
Click to collapse
This looked the most promising maybe because it felt like I was doing something and I was using the ATT ROM again to update, and it actually started updating again. But it stopped at 11% again and gave me the 262 error.
Below pulled from readme.txt file.
"ERROR [262, 276, 284, 302] : UPDATE ERROR
This error occurs during the CE ROM code upgrade process.
Solution: If this happens, you can just soft-reset the device and run RUU again. The update process will then continue.
Note: At this stage, the Wince is destroyed; instead, it is in upgrade mode."
Click to expand...
Click to collapse
Tried to soft-reset and reinstall but same problem.
Scrambler001 said:
You should not update using the Oficial ROM release Update because you put in the boot loader from here (Hard-SPL-V7) and it will try over righting the entire rom if you do and is probably what messed up your update attempt. Use Dutty's NBH tool and just decompile the NBH of the official rom, then recompile the windows, splash screens and radio into a new NBH then flash using the RUUwrapper from this site to flash the phone.
Click to expand...
Click to collapse
Haven't yet tried this because I am having a hard time getting details on this. I've been searching looking for "duttythroy nbh tool", "nbh tool", "dutty nbh tool", and "dutty's nbh tool" and I can't find it.
If this helps anyone this is what I have on my tri-color screen:
HERM100
IPL - 1.04
HERM100
SPL - 2.03
Click to expand...
Click to collapse
You can also try to flash from the SD card:
- format a SD card with FAT32
- extract the .NBH file from the rom image you like (for your device of course)
- rename the .NBH to HERMIMG.NBH and copy it to your SD card
- put SD card in phone and start it in bootloader (hold OK button on left side and POWER button at same time and stick with stylus in RESET on bottom)
- confirm flashing on screen
- flashing might hang after some time but this is normal. Just wait. Complete flash takes about 30 minutes.
This also works for normal (non preproduction) devices but keep in mind that if the CID does not match the flashing might not work. - this was taken from one old thread
- notes - you should backup everything on your SD card to your PC (because except for HERMIMG.NBH it should be blank)
- you can not get USB related error because it loads from a card
- if you flash official ROM you flash it with everything - radio ROM, Windows and bootloader
I am not really sure about bootloader you should have but for official upgrade official bootloader should be ok (it is first thing to be flashed - so I think you have bootloader from ATT ROM already.
Hope it can help somehow...
hey, what is your spl version?
it should say on your bootloader mode
and then read this http://wiki.xda-developers.com/index.php?pagename=Hermes_Unbrick
that really helps a lot, it has the solution and stuff. hope you unbrick your phone! all i did was download the update and it reloaded to wm5 update on my 8525 then after that, i went for olipro's 2.10 so i dont unbrick it anymore =) then flash all you want!
oh yea the factory update for my 8525 that unbricked my phone was this http://www.htcamerica.net/support/8525/software-downloads.html
try loading that in your phone =)
Ok that was the oddest thing but it worked. I've been trying to possibly unzip some of the packages by way of what duke_stix instructed. My last ROM was Schaps most recent 4.0. I unzipped what he had and ran the RUU file. What was funny though is that it started updating up to 3% then gave me the 260 error but this time my phone restarted and booted back up. I don't know what happen but it works now. If this is suppose to go in as a fix I don't know what happen.
Thank you everyone for all your help. I want to reflash my ROM but I will wait until I see this working for a while.
- Monty
asianr0cker said:
...i went for olipro's 2.10 so i dont unbrick it anymore =) then flash all you want!
Click to expand...
Click to collapse
How do I change my SPL to 2.10 now?
Here is nice tutorial how to flash HardSPL v7 (a.k.a. bootloader 2.10 Olipro). Glad to see you are out of brickland
KarhU said:
Here is nice tutorial how to flash HardSPL v7 (a.k.a. bootloader 2.10 Olipro). Glad to see you are out of brickland
Click to expand...
Click to collapse
Thank you just finished flashing it. Thanks again to all that helped.
MontyV77 said:
How do I change my SPL to 2.10 now?
Click to expand...
Click to collapse
See mrvanx.org
... Edit: That's what you get for waiting 10 minutes before posting. Doh!
Thank You So Much !
I did all pricedures and it worked perfectly. You are the best dude!
duke_stix said:
Hi
Try this:
1) Turn your phone off completely
2) Hold the side OK button and the power button, at the same time push the reset button at the bottom with your stylus.
3) this should get you into the bootloader (the three colour screen)(dont be lazy and just let it load into the bootloader, actually run the key sequence ive just mentioned!)
4) on your PC run the update, i would reccomend the latest official update for your handset, BUT, do the following:
a) Make sure you have WinRAR installed
b) Right click on the update file you have just downloaded
c) 'Extract' the update file to the folder it makes
d) within that folder should be ANOTHER executable file that has the same icon as the original update
e) Extract this file again
f) open the folder it makes and within that there should be a RUUSIGNED.NBH and also the RUU utility itself
5) Run the update utility in the second folder
6) once the utility has loaded, plug your phone in (the text will change from 'SERIAL' to 'USB')
7) proceed with the update and see what happens
hope that helps
good luck.
Click to expand...
Click to collapse
if its an official rom you may need to hard sol it first as i had the same problem updating to original after a chefs special
blowfeld said:
if its an official rom you may need to hard sol it first as i had the same problem updating to original after a chefs special
Click to expand...
Click to collapse
what is a hard sol and how do I do it? I wanna go back to the OEM Official ROM to see if it fixes my no service phone problems.
Ok, I've tried everything that was posted in this thread and nothing worked so far.
My last setup before trying to reinstall the Radio is:
AT&T 8525 (location - Hawaii)
Black Majik's WM6
Herm Radio 1.43.00.00
Hard SPL-V7
The OS has been working great until this previous Monday. Also just in case if this is any relevant, Hawaii has just recently upgraded and turned on it's 3G network just a couple of weeks ago. They are still tweaking the whole thing to make sure all is well. Unfortunately it seems that something they did this past Monday seemed to really screw up the 8525's.
The reason I'm trying to reinstall my radio is because I happened to go to the phone settings, and saw that there was no Radio version on the screen. Thought this might also add to the problem.
Well where I'm at now is that I'm stuck at the Tri-Color loader screen. I've read the Wiki regarding fixing a bricked phone. Doesn't seem to help.
So I'm now stuck and need expertise of more knowledgeable members who might have been in the same situation as me.
Please, really need help as this is a company phone and I've got to get it working cause I don't wanna have to pay for it.
Everything was fine, I was just browsing for wireless connections and then I've done a softreset and to my surprise it went into bootloader mode, and now whatever I do (softreset, remove battery, hard reset) it goes immediately in the bootloader mode and I can't boot windows.
I am running SPL 2.10 Olipro IPL 1.04.
Not sure if this is relevant at all, but I am running Schap's 4.31.
Any ideas?
Thanks
read the wiki
since youre hard spl you can flash the rom again. jsut run the ruu and select 2.10 and select hard spl, dont auto-detect,go through the steps and it will flash
Hmmm try reinstalling 4.31 or any other ROM again to see if it works!
Tried that already. I have tried the same ROM again (schaps 4.31), and tried the t mobile official ROM (WM6). they didn't change anything, it flashed the rom to the end and then after the reboot it goes back to the bootloader and can't get off it. I have tried the phone's original ROM which was WM5 but I couldn't do that (doesn't flash it, it says the phone is not available, maybe because it's in bootloader and it doesn't connect to activesync).
The strange thing is that overnight I left the phone off and this morning it did boot into windows (this was on the official t mobile WM6 rom) and went as far as running the custom network settings, but then after the restart it went back to bootloader and now it's back, can't get out of it.
Any ideas?
oooo
im having the very same prob
official wm6 from t-mob (UK) upgrade from WM5 that came with the hermes.
now i cnt get outta boot load.
check out my fight to bash the brick back in to its senses...
http://forum.xda-developers.com/showthread.php?t=361323
If anyone can help give my phone CPR - please do.
serializable said:
Tried that already. I have tried the same ROM again (schaps 4.31), and tried the t mobile official ROM (WM6). they didn't change anything, it flashed the rom to the end and then after the reboot it goes back to the bootloader and can't get off it. I have tried the phone's original ROM which was WM5 but I couldn't do that (doesn't flash it, it says the phone is not available, maybe because it's in bootloader and it doesn't connect to activesync).
The strange thing is that overnight I left the phone off and this morning it did boot into windows (this was on the official t mobile WM6 rom) and went as far as running the custom network settings, but then after the restart it went back to bootloader and now it's back, can't get out of it.
Any ideas?
Click to expand...
Click to collapse
Run mtty and try to see if there is bad NAND blocks on the device, to do that run 'info 8' which will report if bad blocks exist. If they do (there should be 3 bad blocks on a normal device, ignore them) then run 'task 2a' which should sort out bad blocks, then flash a new ROM.
EDIT:: Always look at the Hermes Unbricking Thread aswell.
Ok, thanks mr vanx. I'll try that.
Here's a quick update: it would appear that after it is off for a while (about 30 mins, without the battery) it boots into windows, but then after any restart it goes back stuck in the bootloader. Does this mean anything to anybody?
Brilliant
mrvanx said:
Run mtty and try to see if there is bad NAND blocks on the device, to do that run 'info 8' which will report if bad blocks exist. If they do (there should be 3 bad blocks on a normal device, ignore them) then run 'task 2a' which should sort out bad blocks, then flash a new ROM.
Click to expand...
Click to collapse
Thank you ! That fixed it.
Brilliant!
Out of curiosity, what does set 14 0 do? (as stated here: http://wiki.xda-developers.com/index.php?pagename=Hermes_UpgradeProblems#problem4)
serializable said:
Thank you ! That fixed it.
Brilliant!
Out of curiosity, what does set 14 0 do? (as stated here: http://wiki.xda-developers.com/index.php?pagename=Hermes_UpgradeProblems#problem4)
Click to expand...
Click to collapse
Sweet stuff, glad that worked
set 14 0 i presume is a standard bad NAND command or something, thankfully in HardSPL olipro enabled checking and fixing of bad blocks.
Have fun with your Hermes again
Thank you
mrvanx said:
Sweet stuff, glad that worked
set 14 0 i presume is a standard bad NAND command or something, thankfully in HardSPL olipro enabled checking and fixing of bad blocks.
Have fun with your Hermes again
Click to expand...
Click to collapse
Cheers mate, I sure will !
This was like reading a good book with a very happy ending.
I feel all warm and fuzzy inside.
stuck in HTC splash screen ..Help!
HI guys ,
I have been following the forum from a long time ..... so before i proceed .... i would like to acknowledge all the great work the guys r doin out here !!..
was working on a friends jasjam which had schaps 4.20 running ... due to some issuses ( screen going blank white )with schaps' ROM , was trying to flash K's 1.30b .... the flashing froze midway .... after that could only see the bootloader for a couple of days .... used the mtty method to recover ... but now i am stuck with the first splashscreen and it doesn't budge from there.....
Would really like some advice here guys
Hi,
I bought a diamond a few days ago, and the touch screen recently stopped working. Before it's death, I flashed it with HardSPL 1.40 Olinex, but kept the rom and the radio stock. The problem now is that I would like to send it in for warranty to repair the screen, and I can't revert it back to the original SPL. I've read several threads about how to change it back to OEM specs, but all of them have resulted in the bootloader still displaying HardSPL 1.40Olinex.
Since my touch screen is broken and I recently performed a hard reset to try to fix the screen, I can't get past the align screen, so i've attempted all my upgrades from the bootloader screen(the screen with 4 colors is bootloader screen i think?). I've tried several SPL's from a thread which i beleive where 1.24 original, 1.37 original, 1.93Olinex, all of them still resulting in 1.40Olinex displaying on the bootloader. I also tried installing an official ROM, but that did nothing. I'm desperate for any help or advice so I can get this phone fixed and start enjoying it.
Thank you
Try make connection via AS ( not bootloader ) and shipped rom with not patched custom_ruu
Did you read this single post by cmonex?
HERE
kvm55 said:
Try make connection via AS ( not bootloader ) and shipped rom with not patched custom_ruu
Click to expand...
Click to collapse
I'll try that. I think i've tried it before, where I could make a connection but was not able to update due to me being stuck on the align screen? I'll give it another go.
R3PUBL1K said:
Did you read this single post by cmonex?
HERE
Click to expand...
Click to collapse
Yes I have thanks. That was where I tried using the RUU-SSPL-withoutNBH.zip along with the 1.37 from the first attachment, which still ended up as 1.40OliNex. I'll give it another go from the active sync rather than bootloader.
Thanks guys
Ok so I tried from AS, here's what i got:
Using CMONEX's post, with all the roms and the custom ruu I was able to detect the phone version and press update, but before it starts updating it gets an error [202], connection.
Using a shipped ruu with the 1.37 from CMONEX's post as well as the shipped nbh, the device loaded into bootloader and updated, but still displayed 1.40OliNex. It was able to install from AS though.
I really have no clue what's going on. Any suggestions?
EDIT:
I was able to magically get the touch screen to work to get past the align screen after updating to a different rom, and I was able to update it normally following CMONEX's post.
Thanks for your help guys.
Great News
Glad you got it sorted
i have flashed my diamond with the official htc rom
im on 1.40 olinex, now i can only access boot mode.
sometimes if i leave the phone without a battery for like 2 hours, when i turn it on i see the "touch diamond" logo, if i leave the battery for a whole day i see the windows mobile loading screen, but then suddenly the phone turns off
plz if you have any idea about this problem help me
If you can acces bootloader, then your diamond isn't bricked.
Try the unsigned version of olinex' hard-SPL and flash the ROM again.
Good luck!
hey ElCondor, im on 1.40 olinex, i cant flash it because it is protected
how can i flash the unsigned 1.40 olinex one?
Here is a link to the unsigned hard-spl.
Make sure you download "Unsigned-Hard-SPL-Diamond-OliNex.zip".
Follow the instructions:
1) Download, extract to an empty folder.
2) Run RomUpdateUtility.exe, Have Phone Synced with PC (go into bootloader, connect your cable, then the word "serial" in bootloader will change into "USB".
3) follow steps, check device for prompts after PC shows loading bar. it should go to black screen now.
4) SPL flashes, device automatically reboots, job done.
5) to confirm you got it installed, go into bootloader mode (volume down + reset, i.e. press volume down button and reset then keep holding the volume down key until you see tricolour screen) and verify the screen shows 1.40.OliNex.
note: you will not see the SPL version during normal boot, that is the OS version, not SPL!
Installing this will hard-reset your device.
Best Regards,
ElCondor
when i flashed the unsigned 1.40 olinex, the device rebooted
windows mobile is preparing your phone for first use
htc logo
phone went off :S
will try flashing rom again
flashed ROM again, now it wont boot up no htc diamond logo no nothing
i can access boot mode (1.40 olinex unsigned now i guess)
is there no way i can boot the rom? what seems to be my problem?
mzaouar said:
flashed ROM again, now it wont boot up no htc diamond logo no nothing
i can access boot mode (1.40 olinex unsigned now i guess)
is there no way i can boot the rom? what seems to be my problem?
Click to expand...
Click to collapse
Hi
If you can access the bootloader then your device is not bricked. Therefore download a rom of your choice then connect to the usb when on the bootloader then use a Diamond custom RUU (normally come with the rom) follow the steps. After rom updated make a hard reset. I hope it will run ok.
Looks your symtons are showing like your rom corrupted.
Good luck
i am flashing this ROM
RUU_Diamond_HTC_Europe_1.93.401.2_Radio_Signed_Diamond_52.29.25.12_1.00.25.05_Ship
the newest one i downloaded from htc. com is giving me rom update error
would you recommend a good rom for my phone?
after flashing and reflashing and hard resetting with the ROM showed above
still cant boot in ROM mode, only in boot mode
el condor sabes, anything ???
should i flash with a new rom, and if yes with which?
(diam100 olinex 1.40 unsigned)
Perhaps try a custom rom?
I found when flashing to an official rom from a different provider (my phones telstra and was flashing 3) I had issues with the rom booting and had to follow a post on here somewhere to get it working, however When I had this problem I could still flash any custom rom with no issues.
Unless its for warrenty purposes then its probably not worth flashing the "original" perhaps flash A.Z.T.O.R. = Alpha Zero Tweaked Official Roms which are close to the original but with benifits of being modded for faster speed etc.
Anyways Im no pro but I know what you are going through and I am trying to find the link to the fix to your problem as I also had the problem. But recommend trying a custom rom to confirm the problem is the same as mine.
For the record now I do not use official roms anymore, with WM6.5 running well for the most part on the diamond its a great step backwards when you revisited 6.1
flashed to SwiftBL-WWE-Diamond-v7.5-Full-16MbPP
still same problem can only go to boot mode
i am feeling there is no solution to my problem ?
is the phone bricked? :S
If you haven't done yet, flash the hard-spl I posted. Just do it, re-instal the hard-spl! Then, flash another ROM, maybe (as said before) your rom is corrupted.
The problem here is, that you first installed the unsigned hard-spl, and then flashed a corrupt rom. In that way, the hard-spl can be damaged too, so flash the hard-spl again and flash another rom should work.
Good luck!
I did :S but to no avail, I will do it again fingers crossed :S !
update: weird, everytime after i flash the hardspl unsigned, it boots up, i can see the "touch diamond" logo
windows mobile booted.. preparing your device..
update 2: windows mobile booted, installing everything
omgomg it looks it might work this time, fingers still crossed !!
el condor !! haha fingers crossed
update 3 :S : windows mobile installed properly, phone rebooted, went again and opened it, then i heard a sound from the speaker and the phone turned off :S
it must work what could the problem be now? last step !
Okay try a hard-reset, maybe that works.
If not, then flash hard-spl again, then hard-reset, then flash another ROM. Then hard reset. Then try again if it boots.
Is your battery enough charged? That could also be a reason.
did not work, wont even boot up
when i said if i leave battery out and such, I thought it might be hardware/heat related
http://www.htcwiki.com/thread/2069847/HTC+Diamond+-+Severe+Crashing+Problem,+maybe+heat+related
could this be it? will i have to send my phone for repairs?
because maybe when WinMo was loaded, the phone started to heat up and it shut down
so basically my solution is not a software fix??
If none of the tips worked, and you have the same problems as described in the site you linked, then you probably have to send it back.
One thing you could do: Try if the other hard-spls (1.37 and 1.93 unsigned) are working for you.
I'm sorry for you, maybe someone more skilled than me (like cmonex or olipro) knows how to solve your problem.
it's alright :S i thank you for all the help you have offered !
( it is customizing right now) but i expect it to reboot anytime now
worked, 5 minutes into winmo it restarts
mzaouar said:
worked, 5 minutes into winmo it restarts
Click to expand...
Click to collapse
oh,does it worked?how can you get it work?Please tell me....my diamond could only get in the bootloader yet....
mzaouar said:
worked, 5 minutes into winmo it restarts
Click to expand...
Click to collapse
OK good to hear that, if you have any more questions in future, just ask!
Glad to be of some help
msvb007 said:
oh,does it worked?how can you get it work?Please tell me....my diamond could only get in the bootloader yet....
Click to expand...
Click to collapse
Ive sent you a pm, there's no need to use this thread for your questions because the problem in this thread is solved.
So take a look at your pm!
When I turn on my phone, it starts in the Tri-Color bootloader mode and on the screen it shows that there are errors with it. It was flashed with the Olinex HardSPL but it's not saying Olinex any more. When I attempt to flash a ROM or revert to stock SPL or to flash HardSPL back onto it, it opens the % indicator but stays at 0%. I also have tried to flash via SD card but when it recognizes the SD it shows "Loading" but never gets past that.
Is there any way to manually reset the SPL or reload it so that I can get past the error?
When I turn it on without being attached to USB, it says "Serial" at the bottom but changes to "USB" when I connect it to my PC. Is there a way to update it through a Serial connection?
Can someone help walk me through how to get my phone working again? I'd really appreciate some help.
just flash the stock tmobile ROM.
I would run the enablerapinew.cab that Olinex puts out and then try and reload the hardspl back onto the phone. Once you have the hardspl reestablished you should be able to rewrite a rom to the phone.
palosjr said:
just flash the stock tmobile ROM.
Click to expand...
Click to collapse
I can't flash any ROM, including the T-Mobile Stock ROM. The SPL is messed up.
InRBigness said:
I would run the enablerapinew.cab that Olinex puts out and then try and reload the hardspl back onto the phone. Once you have the hardspl reestablished you should be able to rewrite a rom to the phone.
Click to expand...
Click to collapse
I can't get the phone to boot into Windows or I would just run Olipro's CAB and be done with it. I'm stuck at the bootloader and can't get past it.
ahh so true.
I had trouble flashing the HardSPL and I just kept doing it until it took. It would sit at 0% then error out. Make sure that computer has fresh boot, no antivirus running etc and keep trying to get it to take the flash. Not much else you can do. You might want to ask in the Rom section or open a ticket at Olinex website. http://support.htc-unlocks.com
InRBigness said:
ahh so true.
I had trouble flashing the HardSPL and I just kept doing it until it took. It would sit at 0% then error out. Make sure that computer has fresh boot, no antivirus running etc and keep trying to get it to take the flash. Not much else you can do. You might want to ask in the Rom section or open a ticket at Olinex website. http://support.htc-unlocks.com
Click to expand...
Click to collapse
It's not the computer that's the problem, it's the phone, though I don't have AV software or anything like that anyways. I have tried is on 2 computers at home and 1 at work.
I tried to flash a new ROM via SD card... all it said was "Loading" forever (I left it on "Loading" for over an hour with no change). I left it attempting to flash HardSPL over night and it was still at 0% in the morning.
The SPL is not working right and I can't flash a new SPL without already having a working SPL.
I got this working. Olipro got back to me from my his support.htc-unlocks.com trouble ticket site.
I had to use MTTY to run the command "SET 16 0". Then I was able to get my phone to reboot and it was then able to load the stock T-Mobile ROM. From there, I was able to flash HardSPL back onto it, then a custom ROM.
Thanks Olipro!