I was trying to load wm6.5 and I must have missed a step or loaded bad rom. I unlocked it, at least i think i did. When I load the boot screen (volume down and power) it says "security unlocked".
When I start the phone, it says "Touch Pro" like usuall and then crashes, vibrates and restarts.
I used the search function on this forum to find a similar problem but I could not understand the solutions. Any help would be great, since I have NO phone.
Ya know, if you want help, you could post some basic info. As is, your post is as useless as your phone.
Exact device?
Carrier?
SPL?
Previous ROM?
ROM that bricked your phone?
Previous flashes? Radio?
OK,
Touch Pro - Sprint
All the other info I know is that before this it was running stock rom. And all the info I can get now is off the bootloader screen. It says...
"
Security unlocked
RAPH800
SPL-0.37.CMONEX
MixeoP-Hermann (LED) v0C85
MicroP-Hermann (KEY) v0685
PSOC-Raph STAGE_EVT v20
"
You have a CDMA phone, and you have tried to flash GSM ROM. That is the best way to kill your phone. ROMs that you want are in this section: http://forum.xda-developers.com/forumdisplay.php?f=465.
Well that would explain the problem. But everytime I go to install new ROM it starts the process then goes from 0% TO 100% in less than 30 sec. It says its complete and there is still no change.
It's time for Mr. Herman to meet Mr. Microwave.
absolutely brick... never flash GSM ROM in CDMA...
gld_krieg said:
absolutely brick... never flash GSM ROM in CDMA...
Click to expand...
Click to collapse
Farmer Ted said:
It's time for Mr. Herman to meet Mr. Microwave.
Click to expand...
Click to collapse
Really guys, because after hours of messing around with it I fixed it. Fricken Senior and Junior members acting like they know it all, got bested by a noob. bunch of douche bags
so how did u fix it?
touch pro symbol then crash
I had the same problem if you turn the phone off hold the volume down and the power buttom together this will turn your phone on and place it in boot loader mode
Now use a differnt Rom to flash on the phone and it should work as long as the new rom is the correct rom for your phone (GSM, CDMA)
i had a sprint CDMA and i used the energy rom from oct 25 which crashed my phone then mighty rom brought it back to life so try that and see if it works
Floods7 said:
Really guys, because after hours of messing around with it I fixed it. Fricken Senior and Junior members acting like they know it all, got bested by a noob. bunch of douche bags
Click to expand...
Click to collapse
hey watch what your saying in the forums, theyre only suggesting and teaching u some moral lessons
Ted is just suggesting u something thatll get u a refurb or possibly(if your lucky) a new TP
and Krieg is just telling you that, soo the next time it wont happen again
good for you for fixing ur TP, consider yourself lucky, but maybe next time be more grateful that theyre telling u stuff that you DONT know and that will help u in the long run instead of calling them douche bags, theyre more experienced than you, not saying ur dumb but name calling makes you look immature
i suggest u reading this before you go any further
http://forum.xda-developers.com/showthread.php?t=508084
Sorry for double post
Related
i originally had faria's wm6 on my phone, but then i wanted to try xplore core 2.0. i flashed it, but when it finished it would start. it wouldnt go past the second splash screen. i tried a hard reset using the hard keys, but when i try it, it says format failed. i have tried to reflash using bootloader using the OEM carrier roms from both t-mobile and cingular. i am having the same issue no matter what i do. if there is anything i can do to fix this.. please help me because i constantly use my wizard and i don't no what i can do without it. i really appreciate any input. thanks
im not sure what to do but i figured i'd respond just so you know people are trying to help. I've heard of the format failed problem, but im not sure what the solution was. Good luck!
What device do you have ? A G3 ?
How I fixed my Format failed problem...
This is a quote from thread
http://forum.xda-developers.com/showthread.php?t=276963&highlight=splash+screen+freezing
I followed these steps with an SD card fresh from the package...
Drug_Store said:
...
2- Get a clean SD card (in qtek 9100 / Htc Wizard case is MiniSD) with 128MB (some people say 64MB, but I personally used a 128MB, maybe a 64MB is enough)
3- Kill (task manager) wescomm.exe (this is related with activesync installed on your PC). Insert the blank SD card on the phone.
4- Get your phone in bootloader mode. Like this : Phone powered off, press Camera button + Power On, will enter in bootloader mode (RGB screen).
5- Now connect your USB cable to your phone. And start MTTY_updateROM.exe (http://wiki.xda-developers.com/uploads/romupdate.rar). After open, on Port selection, choose \\.\WCEUSBSH001 and press OK. A window will open with a blank sheet.
6- Type "r2sd all" and hit enter... wait to the end (at end shows "cmd>"). On your phone screen u can follow backup progress... small bar will appear down the RGB screen.
7- Power off the phone (or remove battery), enter bootloader mode (camera button + power on) and this time RGB won´t appear right away. Will ask if u want to "download SD image", press voice dial button to agree, and writting will begin. Wait to the end. Power off and power on normally. Now your phone should be working ok. Not even needed to reflash the phone after this.
Thanks to all and hope this helps more people with this problem
Click to expand...
Click to collapse
thanks guys... im going to try that.. and just so all of you know, its a g3
thanks everyone who helped me out. my wizard is working perfectly again. i appreciate all the help
wow that's awsome
idd, mtty is last chance weapon.
woah...
Guess I'll post this...
For the record, the Core 2.0 rom ****ED my phone up too. When I tired to flash back a different rom because of all the changed **** in Core 2.0 my phone flipped out. I had to flash it 3 or 4 times to get it to even boot.
I recommend anyone thinking of tyring Core 2.0 to stay away from it unless they don't plan on changing roms after going to it.
GldRush98 said:
woah...
Guess I'll post this...
For the record, the Core 2.0 rom ****ED my phone up too. When I tired to flash back a different rom because of all the changed **** in Core 2.0 my phone flipped out. I had to flash it 3 or 4 times to get it to even boot.
I recommend anyone thinking of tyring Core 2.0 to stay away from it unless they don't plan on changing roms after going to it.
Click to expand...
Click to collapse
yes, i edited it.
I believe operator error isnt something to blame on the rom. Anyone that openly drops the "F" bomb when discussing a cell phone really should get a life.
GldRush98 said:
woah...
Guess I'll post this...
For the record, the Core 2.0 rom ****ED my phone up too. When I tired to flash back a different rom because of all the changed **** in Core 2.0 my phone flipped out. I had to flash it 3 or 4 times to get it to even boot.
I recommend anyone thinking of tyring Core 2.0 to stay away from it unless they don't plan on changing roms after going to it.
Click to expand...
Click to collapse
anichillus said:
You are an asshole, pardon my language. My rom doesn't **** systems up, mabe you just don't know what you are doing.
I won't release any more roms. I am just tired of all this SH**. I stay calm and watch people who only know how to complain and don't give a F*** about all the work that's put up just for free, but this does it. I am giving up.
I can't afford to brick my Wizard for people like you who are simply here as ignorant sharks.
Click to expand...
Click to collapse
You sound like Faria...LOL!
Really, that's why I put what I did in my thread about saying "My phone is stuck in bootloader..." (remember the fillet knife?) ROM's DO NOT MESS UP A PHONE UNLESS THEY ARE CID LOCKED, THE FLASHING PC HAS ISSUES, OR BECAUSE OF OTHER OPERATOR ERRORS.
Don't let it get you down. You're doing a good work and if one or two people out of a thousand can't get it right, then they need to be running carrier ROMs, and you can stay calm and happy helping those who really need it.
See, that's not so bad now is it?
GldRush98 said:
woah...
Guess I'll post this...
For the record, the Core 2.0 rom ****ED my phone up too. When I tired to flash back a different rom because of all the changed **** in Core 2.0 my phone flipped out. I had to flash it 3 or 4 times to get it to even boot.
I recommend anyone thinking of tyring Core 2.0 to stay away from it unless they don't plan on changing roms after going to it.
Click to expand...
Click to collapse
i went form core 2.0 back to the tmobile rom and then to the core 2.0n and it worked fine. did you lose connection during the flash or somthing?
anichillus said:
You are an asshole, pardon my language. My rom doesn't **** systems up, mabe you just don't know what you are doing.
I won't release any more roms. I am just tired of all this SH**. I stay calm and watch people who only know how to complain and don't give a F*** about all the work that's put up just for free, but this does it. I am giving up.
I can't afford to brick my Wizard for people like you who are simply here as ignorant sharks.
Click to expand...
Click to collapse
Boy, I know more about what I'm doing then most people here put together.
Your rom ****ed my phone right in the ass.
Luckily I recovered from it.
You call your Rom "stock" yet YOU CHANGED ALL KINDS OF STUPID STUFF IN IT.
Like the alignment screen graphic?
Why the hell would you do that.
Or putting on 3 different boot screens. wtf?
Oh yeah, not to mention it runs like **** before even loading any more software on it since you used the OLD WM6 build.
Don't release any more.
You're terrible at it.
kthx bye.
jawnsixteen said:
i went form core 2.0 back to the tmobile rom and then to the core 2.0n and it worked fine. did you lose connection during the flash or somthing?
Click to expand...
Click to collapse
Nope, flash went to 100% then the phone tried to reboot and nothing happened.
I do all my flashing on that machine because it's stable and I have never had a problem flashing until the Core 2.0 rom. That is the first and only rom I have had any trouble with.
golfernutnflorida said:
I believe operator error isnt something to blame on the rom. Anyone that openly drops the "F" bomb when discussing a cell phone really should get a life.
Click to expand...
Click to collapse
OMG, he used a naughty word.
Like you don't hear it daily?
Get real.
GldRush98 said:
Boy, I know more about what I'm doing then most people here put together.
Your rom ****ed my phone right in the ass.
Luckily I recovered from it.
You call your Rom "stock" yet YOU CHANGED ALL KINDS OF STUPID STUFF IN IT.
Like the alignment screen graphic?
Why the hell would you do that.
Or putting on 3 different boot screens. wtf?
Oh yeah, not to mention it runs like **** before even loading any more software on it since you used the OLD WM6 build.
Don't release any more.
You're terrible at it.
kthx bye.
Click to expand...
Click to collapse
I do my rom as I please, you can't question that.
For YOU to know all roms have 3 (boot =NOT) splash screens You're just too SMARTass to notice.
You can quote multiple post in same message, in case that slipped your soo full-of-knowledge mind.
I used old WM6 build ? Please explain to me what you mean ...i am not that wize
I did not called my rom STOCK ! I called it Core . But you are probably too smart to actually even read anything.
In case you don't understand the word "CUSTOM", then let me explain it to you : I can change whatever i want in it. All of it if I like to.
Ah yeah, and i almoust forgot ... please read this
http://forum.xda-developers.com/showpost.php?p=1241040&postcount=1
It's been there from day 1, just made it bigger now, so that you can see too
And next time, keep your opinions to yourself. No need for public -> "Ooh, look at me how tough I am ! " stunts.
....
whether you like it or not...
I'm confused by people who choose to post cooked ROMs in a public forum, invite people to use and comment, but them complain if the feedback it not all roses and accolades.
You may have done this for free, and many if not most, appreciate your time and effort. That being said, some have legitimate complaints and are posting them because they have experienced problems with your ROM. I’ve been reading your reaction to any negative feedback and you are highly defensive, never conceding that there may be issues to address.
All cooks say that you are not responsible if the ROM bricks someone’s device or if they have problems, and no one has asked for you to pay for their repairs or replace their devices.
There is no place for foul language or insults in such a forum. It's childish and may simply help support the complainant’s point.
If this is your reaction to complaints, then yes do us all a favor and stop posting and keep your work for your personal enjoyment and benefit.
If you can't stand the heat, then get out of the kitchen. No pun intended.
Well if it doesn't work for you then try a different ROM. I tried all the ROMs and pretty much gonna stay with Faria The Real Thing
I tried Xplore 1.0 and i had alot of troube so I dont think im gonna try 2.0. If it works dont change
Funny thing is I have flashed this ROM to my wizard 6 times, and each time something else didn't work. But let me explain...
I want a stripped version of windows, I don't do any messaging at all. And since the Explorer ROMS are known for their stability, it seemed a logical choice. So I have been using package tools, to create packages with option.XML files for each package so you can choose, what parts of the OS get installed.
But back to the point...
Each time I flashed something went wrong... Something I did, a "tmail not found warning when activesync starts", to once I got a 260(?) error once when flashing at 63% so I started it while holding the voice command button. It booted into Bootloader, I flashed it to Cingular 2.25.11 and immediately flashed back to the same ROM successfully.
There are hundreds of people Ecstatic with the Xplorer ROMs, for each one of you here complaining. I for one would think it a travesty, for a few unappreciative people to ruin it for hundreds of others. By pissing off one of our cookers. Maybe had you posted your problems here we would have been able to help you.
But please don't be so accusing, just read, and if you can't find an answer. Then ask nicely, and thank the cook for the time he spends cooking for us! If you don't like the answer you get or you decide you don't like this ROM try one of the many others...
Well i dont have a device so i cant provide much info, but wanted to start a thread of problems and possible solutions...
So i will kick it off.. A friend of mine just messaged me said he acquired a post-production kaiser and wanted to install the ATT rom on it... however when he does it just says could not flash handheld or whatever or its not compatible...it goes to bootloader, gets to around 1% and then stops and phone restarts...
shogunmark said:
Well i dont have a device so i cant provide much info, but wanted to start a thread of problems and possible solutions...
So i will kick it off.. A friend of mine just messaged me said he acquired a post-production kaiser and wanted to install the ATT rom on it... however when he does it just says could not flash handheld or whatever or its not compatible...it goes to bootloader, gets to around 1% and then stops and phone restarts...
Click to expand...
Click to collapse
Well I'm probably going to catch a beating for this but has anybody has the BALLS to hard spl the kaiser with the hermes version. I realize saying this is obvious is an understatement but I would venture to say that most people would be to scared to try. I have a solid connection at a cingy cough...cough I mean at&t store that has switched out 8525's for me without question so I may try if I can get my hands on one. The way I see it I have to start contributing at some point LOL
I would guess it is due to a CID lock...
But then again, what do I know
Tr1gg3R said:
I would guess it is due to a CID lock...
But then again, what do I know
Click to expand...
Click to collapse
if it was cid lock you generally get the "invalid vendor" code.. He specifically stated it wasnt that error... but that was my first thought also... not to mention it should be unlocked at least for the first flash since its HTC branded..
although we did discover that a hard reset is done the same way as the hermes, 2 soft keys + reset ... couldnt find how to put it in bootloader though
It is due to CID lock.
To put in bootloader hold camera + power and reset with stylus.
I got my kaiser today, I'll start to work on a CID unlocker soon
pof said:
It is due to CID lock.
To put in bootloader hold camera + power and reset with stylus.
I got my kaiser today, I'll start to work on a CID unlocker soon
Click to expand...
Click to collapse
thanks for the insight pof, i couldnt tell for sure since i dont actually this device yet.. hopefully i can get my hands on one soon..
****
My phone seems to have given up the ghost. A few days after having put on the excellent Q-Mobile system. My phone has refused to boot properly. Heres what happens:
In start up from Soft reset, or Power off, i get the tricolour screen saying:
KAIS130 MFG
SPL-1.0 OliPof
CPLD-8
a few2 lines benath that is written 'Serial'
it then flashed onto a white screen saying 'loading......no image file' - this all takes about a second.
And then it rests on the screen mentioned above.
I haven't dropped it or done anything other than flash- correctly.
AAAARGH! it does randomly decide to boot up properly after its been left of for a whil if that helps.
Also - active synch wont recognise it , in the tr-colour state.
HELP!!!
Just bring it back to the store and claim your warranty.
If they start asking questions just say that you are unaware of any software change, act like your life depends on it
European law states that every device should have a 2 year warranty.
Try a hard reset...
Hold down the two so-called "soft buttons" at the bottom of the screen while pressing the reset button with the stylus.
I feel your pain man!
the phone is now on, anyone out there got any advice on how to stabalise?
thansk for the support!
tuntang said:
the phone is now on, anyone out there got any advice on how to stabalise?
thansk for the support!
Click to expand...
Click to collapse
Update to dutty's v3 rom that is your best bet...
tekerleki said:
Update to dutty's v3 rom that is your best bet...
Click to expand...
Click to collapse
Its all well and good to pump your favorite ROM, but don't give bad advice. This sounds like a hardware issue to me (usually intermittent things like this are). I recommend the same as a user above...go claim your warranty and be on the safe side.
FYI there's absolutely nothing in any ROM (including mine) that should make your device do this.
Quentin- said:
Its all well and good to pump your favorite ROM, but don't give bad advice. This sounds like a hardware issue to me (usually intermittent things like this are). I recommend the same as a user above...go claim your warranty and be on the safe side.
FYI there's absolutely nothing in any ROM (including mine) that should make your device do this.
Click to expand...
Click to collapse
Maybe I should have been more clear with my previous post, it happened to me too (exactly similar symptoms) but with different rom (not Quentin).
tuntang said:
the phone is now on, anyone out there got any advice on how to stabalise?
thansk for the support!
Click to expand...
Click to collapse
Connect phone to PC with a usb cable.
Does the word "Serial" on the phone display change to "USB"?
If not you are in trouble and you have to send it to service.
But if it shows USB you can flash any ROM update.
thanks for all the help
Its sorted now, and i'm running a perfectly stable Q Mobile. Its really nice not being 'Dutty-Centric'. In response to the person that said upgrade to Dutty V3, it was bad advice for another reason. It would have been incompatible with my radio. Only AT&T versions work on my uk orange tytnII i've got the ...14.09 radio.
anyways - thanks for intervening Quentin and well done its a brilliant ROM
tuntang said:
Its sorted now, and i'm running a perfectly stable Q Mobile. Its really nice not being 'Dutty-Centric'. In response to the person that said upgrade to Dutty V3, it was bad advice for another reason. It would have been incompatible with my radio. Only AT&T versions work on my uk orange tytnII i've got the ...14.09 radio.
anyways - thanks for intervening Quentin and well done its a brilliant ROM
Click to expand...
Click to collapse
Did I read that right? How have you got a 14.09 radio on your orange UK tytn II. Did it come like that or did you flash the radio?
Edit: sorry for the 20 questions but Its the first I've heard of an orange uk tytn 2 haveing the 14.09 radio.
Dear Folks at XDA,
I would like to ask for you help with my HTC Touch Pro 2. I recently tried to update it to the new AthineOS CHome TF3D WM6.5 Manila ROM v 1.0 and unfortunately I failed.
The problem is that my phone now freezes at the black startup screen with the Touch Pro 2 logo and the red codes at the bottom.
I've flashed the ROM several times before and never got this issue.
Due to the fact that the phone doesn't finish the boot-up and I thus I can't get ActiveSync I'm afraid I messed up my phone for ever.
Please someone tell me I got a way out of this, I'd appreciate it very much.
Greetz,
SjonSjon
umm.... I don't think you can change the firmware just yet on the CDMA version of the phone... if you used a HardSPL that's available in the Rhodium forums then you probably used a GSM specific ROM on your CDMA phone... not sure what to tell you other than making sure you read the CDMA forum before trying something so risky. Best solution, unless someone knows how fix your phone in it's current state, is to toss it under your car and run it over and try to cash in on the insurance.
Problem solved!
Hey guys,
I got my HTC Touch Pro 2 functioning again. Thought I'd post the solution for other people who might encounter the same issue. I don't exactly know what the problem was. I'm assuming a non-compatible ROM or something, but after opening 30 tabs in my browser and reading my eyes out I found that if you put your phone into bootloader mode and connect it through usb to your computer you can flash the ROM without using activesync.
So I turned my phone off, pressed the power and Volume Down button simultaneously and then used the Stock ROM upgrade software from HTC to restore my phone
This solution beats the hell outta "run it over and try to cash in on the insurance" if I say so myself!
Greetz,
SjonSjon
I am glad you have recovered the beautiful device; and thanks for sharing a working solution.
sjonsjon said:
Hey guys,
I got my HTC Touch Pro 2 functioning again. Thought I'd post the solution for other people who might encounter the same issue. I don't exactly know what the problem was. I'm assuming a non-compatible ROM or something, but after opening 30 tabs in my browser and reading my eyes out I found that if you put your phone into bootloader mode and connect it through usb to your computer you can flash the ROM without using activesync.
So I turned my phone off, pressed the power and Volume Down button simultaneously and then used the Stock ROM upgrade software from HTC to restore my phone
This solution beats the hell outta "run it over and try to cash in on the insurance" if I say so myself!
Greetz,
SjonSjon
Click to expand...
Click to collapse
Good job!
big thanks for solution.
You just saved my life!!!
Don't get our hopes up! This is the wrong forum. CDMA TP2s can't be flashed at all yet.
This was a life saver post so a quick bump for anyone that needs it.
I unlocked my CDMA phone, installed a few roms -- decided to go back to my stock rom default (which was Telus) -- reinstalled and bam -- bricked.
Well, technically it's not a brick if you can get back into the bootloader to reflash. So no worries everyone. If everyone reads instructions well enough we should hopefully see zero "real" bricks. Or at most, just enough to only build bbq pit rather than a house.
I think my phone is truly bricked
I was unlocking my phone (the HTC Touch Pro 2 <Verizon>) and I was using a Diamond unlocker (I thought it would be fine), but during the process there was a connection error and now my phone seems to be bricked. I can't get it to even turn on, get to a bootloader screen, or anything even remotely close.
The one odd thing that it does though, is when I connect it to my computer, it pops up and my computer recognizes there is a device there. In my Device Manager there is an unknown device called: Qualcomm CDMA Technologies MSM. I have tried every combination of two buttons, including holding down the reset button with all of them, but nothing gets me anywhere.
If anyone could help, I would really appreciate it. Let me know if you need any more information.
my cdma is rebooting endlessley i reflashed stock rom and evorything. it seriously dosnt want to work. its most sadness... i am cashing in on the insurence. but they are going to send me a refurb..
spend 600$ on a phone got inurnce i hope the used one dosnt fail me.
Esazi said:
I was unlocking my phone (the HTC Touch Pro 2 <Verizon>) and I was using a Diamond unlocker (I thought it would be fine), but during the process there was a connection error and now my phone seems to be bricked. I can't get it to even turn on, get to a bootloader screen, or anything even remotely close.
The one odd thing that it does though, is when I connect it to my computer, it pops up and my computer recognizes there is a device there. In my Device Manager there is an unknown device called: Qualcomm CDMA Technologies MSM. I have tried every combination of two buttons, including holding down the reset button with all of them, but nothing gets me anywhere.
If anyone could help, I would really appreciate it. Let me know if you need any more information.
Click to expand...
Click to collapse
I did the same exact thing to mt TP2. Same outcome.
We have to learn somehow....
That stinks man. If you did, then your phone is truly bricked. You are going to have to get a replacement or switch to another phone because there is nothing you can do to get it going again. I tried everything possible and eventually just ordered a replacement. I have it now and it's working beautifully, but needless to say I am a little scared away from any more unlocking or flashing for a while.
If you read carefully you dont have to be scared of flashing
I was a noob some time ago but before doing anything I took care of reading and understanding before doing nothing.
lesson learned
By now I have flashed more than 60 times on 3 diferent HTC devices and all were a succes
Hope you get your TP2 working again!
I hope I can get there
Someday I hope to be a flashing expert, but until then I will take it slow and read carefully. Thanks for your encouragement. When I actually get money to pay for the unlock for my TP2, I will let you know how flashing goes.
How do you keep the phone in bootloader? Mine goes right to the press volume instuction screen. Other than that I'm stuck on the black name screen,also my usb will not register in device manager. This was my first try at flashing.
gadgetgirl28 said:
You just saved my life!!!
Click to expand...
Click to collapse
Holy hell, you're not lying. Thanks for coming back to post your solution!
This post saved me at least a few hours of frustration and ever worsening decision making.
So it's totally true???
this situation hasn't solution;
I was unlocking my phone (the HTC Touch Pro 2 <SPRINT>) and I was using a Diamond unlocker (I thought it would be fine), but during the process there was a connection error and now my phone seems to be bricked. I can't get it to even turn on, get to a bootloader screen, or anything even remotely close.
The one odd thing that it does though, is when I connect it to my computer, it pops up and my computer recognizes there is a device there. In my Device Manager there is an unknown device called: Qualcomm CDMA Technologies MSM. I have tried every combination of two buttons, including holding down the reset button with all of them, but nothing gets me anywhere.
If anyone could help, AND PLEASE somebody tell me , that it can be save it
;9
please help
i have the same problem. is there a way to save my phone?
I think i bricked theHTC fuze that i bought yesterday I tried to do the Hard SPL but i was getting an error message, error 244 invalid model ID so i used a program to change the .nbh (a radio file) file so it bypassed the error message (by changing DIAM***** to RAPH*****, since my phone is raphael). I even got a message that the process was successfully finished but it turned out not to be true because the screen went black and now i cant turn it on, and i cant even get it into the bootloader mode. If i could at least get it into to tricolor screen i would be able to flash back the original radio and that would solve the problem because ive already done it a few times. Please let me know if there is a chance to get it fixed, even i had to send it to a professional but as long as it could be fixed, im really desperate. Thank you
brick, htc fuze, diamond, raphael, hardspl
You only get that error when your trying to flash the wrong device... Did you use the file "Raphael_CDMA_HSPL_037.zip" to unlock..?? Sound's to me like you used the Diamond Unlocker... Shouldn't be that hard to fix, hold the volume down button, power button, and insert stylus into the hole on the bottom to soft reset to try and open up BL screen... LMK if that works...
Why didn't you just follow the instructions for flashing? You aren't even security unlocked, so why were you trying to flash a diamond radio? That makes no sense at all. Also, if you are security unlocked, you need to get diamond radios from the raphael forum, because they're patched to flash onto raphaels. It sounds like you got yours from the diamond forum, which is the wrong way to go (especially if it's a cdma radio-that would kill your phone for sure). Did hard spl work? If not, why on earth did you forge ahead? YOU CAN'T DO ANYTHING UNTIL YOU FLASH HARD SPL!!!!!
Try pulling the battery for a while, the see if it will start up. It's hard to tell what you did, but since you went down such a wrong path, I wouldn't be surprised if the phone is a giant brick.
komar808 said:
by changing DIAM***** to RAPH*****
Click to expand...
Click to collapse
this should've been clue #1. If you have to change it because of the device ID, it's the wrong thing to flash. The Diamond and Raph look alike on the front, but are almost totally incompatible ROM-wise.,
I even got a message that the process was successfully finished but it turned out not to be true because the screen went black and now i cant turn it on
Click to expand...
Click to collapse
You are wrong there, it did flash successfully. The tools worked EXACTLY as they were designed. It's not the tools fault
Please let me know if there is a chance to get it fixed, even i had to send it to a professional but as long as it could be fixed, im really desperate. Thank you
Click to expand...
Click to collapse
You might contact olipro, I hear he's got the "magic touch" with devices. No guarantees. I've heard that it's almost impossible to unbrick a device like this after an incorrect/bad radio flash.
I really hope it works out for you. Read dude, the stickies are everywhere for your benefit. Best of luck to you.
brick, htc fuze, diamond, raphael, hardspl
I run into things like this DAILY. Been a service rep for over 30 years. If people would ONLY follow the instructions, I'd have less follow up work to do.
Unfortunately they make these phones too easy to hack (good for us) but sometimes noobs make it hard for the rest of us.
lol
This is what happens when you don't follow directions, don't read enough, and are monkeying with things you obviously shouldn't be monkeying with.
When you got the device ID error, you should have stopped right there and thought "gee, maybe I should go over these instructions again and see what I did wrong" instead of trying to force a radio that will never work on your device.
Hope you can get it in to bootloader, otherwise enjoy your shiny new brick.
Well, hope you get it solved and otherwise you learned a lesson in a very expensive way I'm afraid...
Farmer Ted said:
Why didn't you just follow the instructions for flashing? You aren't even security unlocked, so why were you trying to flash a diamond radio? That makes no sense at all. Also, if you are security unlocked, you need to get diamond radios from the raphael forum, because they're patched to flash onto raphaels. It sounds like you got yours from the diamond forum, which is the wrong way to go (especially if it's a cdma radio-that would kill your phone for sure). Did hard spl work? If not, why on earth did you forge ahead? YOU CAN'T DO ANYTHING UNTIL YOU FLASH HARD SPL!!!!!
Try pulling the battery for a while, the see if it will start up. It's hard to tell what you did, but since you went down such a wrong path, I wouldn't be surprised if the phone is a giant brick.
Click to expand...
Click to collapse
I did hard SPL first with 1.90OliNex (because the one that was in the unlocking package originally didnt work beacuse of the invalid model ID message) and i thought thats what security unlocked the phone and then i tried to put a costume radio that would allow me to unlock the phone but the radio wouldnt flash. So i went back to the SPL from the unlocking package (HARD SPL 1.34) and i changed the .nbh file from DIAM***** to RAPH***** and then it bricked... The reason i did this is beacuse of the following link :
http://forum.xda-developers.com/archive/index.php/t-427305.html
I just hope something can still be done otherwise this is just a good warning for all others not to do this. Thank you for the replies
jdmsohc22 said:
You only get that error when your trying to flash the wrong device... Did you use the file "Raphael_CDMA_HSPL_037.zip" to unlock..?? Sound's to me like you used the Diamond Unlocker... Shouldn't be that hard to fix, hold the volume down button, power button, and insert stylus into the hole on the bottom to soft reset to try and open up BL screen... LMK if that works...
Click to expand...
Click to collapse
No I used a gsm unlocker, HARD SPL 1.34... There is a more detailed explanation in the post above
Hard spl 1.34 is either cdma or diamond gsm-I don't know which. I do know that it will brick a gsm touch pro. Flashing the wrong hard spl is the guaranteed way to kill a phone. If you actually flashed it, the phone is dead. Try pulling the battery for a day.
You need to run the gsm raphael unlocker to security unlock your phone. You need to pay for it, too. Hard spl doesn't security unlock your phone-it only CID unlocks it.
Farmer Ted said:
Hard spl 1.34 is either cdma or diamond gsm-I don't know which. I do know that it will brick a gsm touch pro. Flashing the wrong hard spl is the guaranteed way to kill a phone. If you actually flashed it, the phone is dead. Try pulling the battery for a day.
You need to run the gsm raphael unlocker to security unlock your phone. You need to pay for it, too. Hard spl doesn't security unlock your phone-it only CID unlocks it.
Click to expand...
Click to collapse
I used the GSM one. Ok i just pulled out the battery and hopefully the phone allows to get it into the bootloader...
Worst case scenario, smash it and pay $100 for ur insured replacement... That is, if you have insurance...
jdmsohc22 said:
Worst case scenario, smash it and pay $100 for ur insured replacement... That is, if you have insurance...
Click to expand...
Click to collapse
Hahahaha !
Good one !
But dude no offense but u deserve a black shiny 600$ brick because YOU DIDN'T FOLLOW THE INSTRUCTIONS ! THEY ARE THERE TO BE FOLLOWED UNLESS AND UNTIL YOU ARE SO RICH THAT YOU CAN WASTE 600$ OR YOU ARE A SUPER CHEF AT XDA AND ARE SURE OF WHAT YOU ARE DOING !
Anyways Best of luck hope you can unbrick it !
otherwise smash it
Bye.
LoL yeah a $600 paper weight may also come in handy..?? Or like previously stated, take your anger out on it for not doing it right the first time lol...
I now this might be a little too late to answer,but i want to give my two cents to this brick posts. Maybe someone will need it. This is for anyone that might be where I was for over 2 weeks. I though my Fuze/ Raphael / touch pro was history. My phone will get into restart loops when ever he wanted. It was very anoying. After replacing every possible software from Radio, Hard Spl, different rooms and even start up splashes, and almost getting "ORD" in the process. I finally took my phone apart, since there was no warranty. Once open I saw that the reset bottom inside was too close to the rubber reset bottom from outside. Guess what ?? That as all it was..... Good luck to all. : )