Ok, So I had dutty's rom running perfect for about 5 months. Decided I wanted to revert back to the stock ATT rom and play with it. I tried to revert and somewhere along the way, I did a soft reset and it screwed me up. I can still flash roms no problem, but for some reason, when the phone goes to start up, it gets to the first screen of the boot process (white with ATT logo) and then it freezes. After about 10-15 seconds, it automatically soft resets and tries again. So, I can hit the reset button while holding cam and pwr to get to the bootloader. I have tried flashing every rom I have downloaded, and nothing seems to work. I am trying the stock ATT rom as I type this but we will see what happens. That is what I was running when it F'd. I wanted to restore it to stock completely, thought about trying to have it replaced because the hinge is really loose on my handset. Anyway, any help would be appreciated. Thanks!
boot command from mtty reads:
Cmd>boot
InitDisplay: Display_Chip=1
Fill RSVD information for block 288 to 309
Storage start sector=0xAB80, total sector=0x10740
Storage start block=707, total block=1053
Total Bad Block in CE: 0
Erase physical block from 995 to 2032
formatstorage Bad block found: 1045
si backup: Erase physical block from 2032 to 2048
No card inserted
OSSIPreLoad ++
Try this
Try flashing this ROM and see what happens.
http://www.4shared.com/file/3857459...ULAR_WWE_157_-_Originaly_Shipped_ATT_ROM.html
What does your bootloader screen show?
Please Help!
Okay. I tried to flash the OEM rom back to my ATT Tilt. While doing this, somehow my phone entered an unending cycle of soft resets. I can still get to the bootloader, but as soon as I flash a rom, it tries to boot, gets to the first boot screen, then resets. My computer keeps popping up "install drivers for new hardware found".
I tried booting through MTTY, no dice.
My bootloader screen reads:
KAIS1*0 MFG
SPL-1.0.01OliPof
CPLD-8
I tried flashing hardspl. RUU opens and it runs instantly. The phone reboots and the boot loader screen still reads this. I flash a new rom, the bootloader still reads this. I'm at a loss. I've been working on this for 3 hours and I haven't gotten anywhere. I don't have a backup phone, so I have to figure this problem out. I have searched the forums and haven't found anyone with the same problem. Please, anyone who feels they can help, let me know what I can try to fix this problem. Thanks!
Threads merged.
Metzex08 said:
Ok, So I had dutty's rom running perfect for about 5 months. Decided I wanted to revert back to the stock ATT rom and play with it. I tried to revert and somewhere along the way, I did a soft reset and it screwed me up. I can still flash roms no problem, but for some reason, when the phone goes to start up, it gets to the first screen of the boot process (white with ATT logo) and then it freezes. After about 10-15 seconds, it automatically soft resets and tries again. So, I can hit the reset button while holding cam and pwr to get to the bootloader. I have tried flashing every rom I have downloaded, and nothing seems to work. I am trying the stock ATT rom as I type this but we will see what happens. That is what I was running when it F'd. I wanted to restore it to stock completely, thought about trying to have it replaced because the hinge is really loose on my handset. Anyway, any help would be appreciated. Thanks!
Click to expand...
Click to collapse
Some people go to far ahead before figuring out the real issue. Don't **** yourself.
Hold down your power, camera, and insert your stylus then tell us what your bootloader screen displays.
Metzex08 said:
Okay. I tried to flash the OEM rom back to my ATT Tilt. While doing this, somehow my phone entered an unending cycle of soft resets. I can still get to the bootloader, but as soon as I flash a rom, it tries to boot, gets to the first boot screen, then resets. My computer keeps popping up "install drivers for new hardware found".
I tried booting through MTTY, no dice.
My bootloader screen reads:
KAIS1*0 MFG
SPL-1.0.01OliPof
CPLD-8
I tried flashing hardspl. RUU opens and it runs instantly. The phone reboots and the boot loader screen still reads this. I flash a new rom, the bootloader still reads this. I'm at a loss. I've been working on this for 3 hours and I haven't gotten anywhere. I don't have a backup phone, so I have to figure this problem out. I have searched the forums and haven't found anyone with the same problem. Please, anyone who feels they can help, let me know what I can try to fix this problem. Thanks!
Click to expand...
Click to collapse
ok post was moved from another thread. sorry. It appears that you do have hardspl installed.
Metzex08 said:
Okay. I tried to flash the OEM rom back to my ATT Tilt. While doing this, somehow my phone entered an unending cycle of soft resets. I can still get to the bootloader, but as soon as I flash a rom, it tries to boot, gets to the first boot screen, then resets. My computer keeps popping up "install drivers for new hardware found".
I tried booting through MTTY, no dice.
My bootloader screen reads:
KAIS1*0 MFG
SPL-1.0.01OliPof
CPLD-8
I tried flashing hardspl. RUU opens and it runs instantly. The phone reboots and the boot loader screen still reads this. I flash a new rom, the bootloader still reads this. I'm at a loss. I've been working on this for 3 hours and I haven't gotten anywhere. I don't have a backup phone, so I have to figure this problem out. I have searched the forums and haven't found anyone with the same problem. Please, anyone who feels they can help, let me know what I can try to fix this problem. Thanks!
Click to expand...
Click to collapse
and your bootloader screen will not change because it does not display the rom version. You have hardspl installed what more do you want?
Did you believe your bootloader screen would change after you flashed a rom?
Damn!!!
Metzex08 said:
Ok, So I had dutty's rom running perfect for about 5 months. Decided I wanted to revert back to the stock ATT rom and play with it. I tried to revert and somewhere along the way, I did a soft reset and it screwed me up. I can still flash roms no problem, but for some reason, when the phone goes to start up, it gets to the first screen of the boot process (white with ATT logo) and then it freezes. After about 10-15 seconds, it automatically soft resets and tries again. So, I can hit the reset button while holding cam and pwr to get to the bootloader. I have tried flashing every rom I have downloaded, and nothing seems to work. I am trying the stock ATT rom as I type this but we will see what happens. That is what I was running when it F'd. I wanted to restore it to stock completely, thought about trying to have it replaced because the hinge is really loose on my handset. Anyway, any help would be appreciated. Thanks!
Click to expand...
Click to collapse
Dude it has been five months since you flashed a rom why bother getting all neurotic and worried For a common situation? I complained to mods because they closed your thread now I look like a douche bag. Thanks.
I had the same problem (continuous reboot) as before, see this thread:
http://forum.xda-developers.com/showthread.php?t=383678
but the problem that I had is because of bad blocks, post your info 8 and maybe I can help
ok, I got the phone to startup, eventually it stopped trying to soft reset. I hit the power button and it turned on. Now, I run jumpspl and it doesn't ever bring up the USB connection, so I can't change the bootloader back to oem. any suggestions?
I used the other version of jumpspl (1.56) and it brought up the USB connection (atleast it says it did). But, when I try to run RUU from the ATT_SPL folder it cannot connect to my phone. MTTY says USB connection is unavailable as well. What should I do?! I want the phone to be able to be sent in for warranty replacement as the hinge seems to keep getting looser and looser. Any ideas? Bootloader still reads the same as before.
Metzex08 said:
I used the other version of jumpspl (1.56) and it brought up the USB connection (atleast it says it did). But, when I try to run RUU from the ATT_SPL folder it cannot connect to my phone. MTTY says USB connection is unavailable as well. What should I do?! I want the phone to be able to be sent in for warranty replacement as the hinge seems to keep getting looser and looser. Any ideas? Bootloader still reads the same as before.
Click to expand...
Click to collapse
If your sending it for warranty replacement via AT&T just put it in the microwave for 2 seconds....problem solved.
Related
I'm having difficulty flashing the rom (There may be an issue with the phone, not sure yet). The phone was at 99% and the upgrade died, I'm stuck at the 3 color red/green/blue with the USB connection. I think there is a way to fix this, but I forget. Can anyone point me in the right direction? Thanks!
alan1974us said:
I'm having difficulty flashing the rom (There may be an issue with the phone, not sure yet). The phone was at 99% and the upgrade died, I'm stuck at the 3 color red/green/blue with the USB connection. I think there is a way to fix this, but I forget. Can anyone point me in the right direction? Thanks!
Click to expand...
Click to collapse
What phone you got... G3, G4 ... CID Locked/Unlocked ?
G3, CID was unlocked a long long time ago. IPL/SPL 2.25 and it says RUU at the top right corner. I should of included the info, thanks for the help!
alan1974us said:
G3, CID was unlocked a long long time ago. IPL/SPL 2.25 and it says RUU at the top right corner. I should of included the info, thanks for the help!
Click to expand...
Click to collapse
Turn the phone off (pull the battery if you have to) and unplug the USB cable. Then turn it back on so its back at the bootloader screen (rainbow color bars screen you saw). Now plug in the USB cable. ActiveSync will NOT connect, but thats fine. You will see USB above the left soft key. Now flash an offical rom (either the Cingular 2.25 found on the HTC website, or T-Mobile 2.26).
Read this thread for details, steps and links:
http://forum.xda-developers.com/showthread.php?t=298613
Once you get back on an official rom, then you can reinstall whatever custom rom you want (but you need to get back to an official one first at this point).
alan1974us said:
G3, CID was unlocked a long long time ago. IPL/SPL 2.25 and it says RUU at the top right corner. I should of included the info, thanks for the help!
Click to expand...
Click to collapse
OK then...
Plug it into the usb, and when the bootloader appears, start flashing whatever rom you like...
Easy, right ?
hmm, it died again at 99% on the upgrade. I can do the official install w/no problem. Maybe I need to go back through the cid unlocker?
alan1974us said:
hmm, it died again at 99% on the upgrade. I can do the official install w/no problem. Maybe I need to go back through the cid unlocker?
Click to expand...
Click to collapse
Please forgive me for stating the obvious but you do know that it is normal to stall at 99% for a few minutes sometimes longer.... What do you mean by "Died at 99%"?
To be honest. You didn't said anything but typical wrong flash case...RUU from custom ROMs to another custom ROM(or having CIDlock probs) is good method for having 3bars relax time.
it's question of the day: what do You mean by "died @ 99%". when i am flashing anything, stalls up to 5 minutes @ ANY percent arent reason to PLUG CABLE OFF,or ANY manipulation on pc, or ppc. if it just stuck forever, its time to turn back to old ROM image, or just any rescue ROM, SO:
revert to old rom with ruu, then install 2 cabs from shelltool, wait 30 secs, reset, turn radio off, plug usb on, and after adding nk.nbf into shelltools directory, and spectacular launching earlier mentioned shelltool, and rtfm od its docs, you may start to do what you've just read.
while flashing DO NOT DO ANYTHING with machines.
After finished operation you will see end so it IS END.
Hard reset.
100% positive flashes, if net is turned off, firewall killed and antivirus turned off. also, remove sd card before flash.
btw, what's your IPL/SPL...
Sorry, I should of been more descriptive. The rom update gets to 99%, then hangs for awhile, then the update application on my computer says that there was a communications error and goes into a recovery instructions. The phone itself stays at 99% until I unplug the battery.
I'll try doing the revert back to old rom in the morning, it's a secondary phone and I left it at work.
I had this problem as well...
I ended up just flashing a stock rom multiple times until it finally took.
I think I had to do it at least 2, if not 3 times before I was finally able to boot the phone.
alan1974us said:
Sorry, I should of been more descriptive. The rom update gets to 99%, then hangs for awhile, then the update application on my computer says that there was a communications error and goes into a recovery instructions. The phone itself stays at 99% until I unplug the battery.
I'll try doing the revert back to old rom in the morning, it's a secondary phone and I left it at work.
Click to expand...
Click to collapse
So, you are experiencing this when trying to flash a stock rom.
Check if the RUU is not corupted. If you downloaded it now, it may also cause this.
Also...restart your PC and don't run anything in the bacground while flashing. Just to make sure.
alan1974us said:
Sorry, I should of been more descriptive. The rom update gets to 99%, then hangs for awhile, then the update application on my computer says that there was a communications error and goes into a recovery instructions. The phone itself stays at 99% until I unplug the battery.
I'll try doing the revert back to old rom in the morning, it's a secondary phone and I left it at work.
Click to expand...
Click to collapse
Also make sure you remove the SD card in your phone if you have one. I've seen flashes fail when SD cards are installed.
Ok, I reloaded the rom. I can't figure out the button rom, there is a screen with a bunch of ???? that come up and none of the buttons do anything. :\ I loaded the wizard love one, which loaded ok. I tried the crossbow reloaded but it hung at 99% again and the application went back into error recovery mode. Maybe I'm just not meant to have it! lol. I don't have the sim or sd card installed atm.
Oh ya, this is probably the most responsive/helpful forum I think I have ever seen.
..removed..
I've tried on a clean machine and still same thing. What happens at 99%? Could the phone itself have issues?
alan1974us said:
I've tried on a clean machine and still same thing. What happens at 99%? Could the phone itself have issues?
Click to expand...
Click to collapse
All the roms will hang at some point towards the end of the flash (official ones tend to hang around 85% or so. The cooked ones hang closer to 99%). This is the point where the final part of the flashing is occuring and I think there is verification that what was written checks out as being valid.
If you can get a rom on and the phone working, and then do a hardreset and that works, then I would say you do not have a hardware issue with your phone (at least not from the flashing side).
BTW: Crossbow Reloaded v1.5 is out now. Please try downloading it and flashing that one (just to see if it makes a difference for you). It is very odd that multiple roms stop at 99% on your like this (hard to say its a bad download).
Sorry, I haven't reread this entire thread, but have you tried this from a different computer? ALso try to turn off any firewall, VPN, or even antivirus software on your computer while you flash to see if that corrects the issue. I think I remember someone trying to go into Safemode one time to do a flash.
Then there is also stand on your head or wave a dead chicken over your head while the flash is happening.... (yeah, I'm grasping at straws on this one )
Lol, thanks. I downloaded the 1.5 and going to give that a wing.
People... pleas read throught the forums!!!
Its so annoying that people asks the same question again and again and again. Dont be so lazy, do your research, search the forum and dont post ST$#"D questions!!!
Gah, error 302 every time. I loaded buttons ROM, unlocked again, tried reloading rom, then BOOM 302! Maybe WM6 isn't meant for this phone.. lol I can load any WM5 or lower and have zero issues.
Okay I got up this morning and my phone was working fine. But then I restarted it and it just booted to the tri-color screen. So i took out the battery and I did a reset and it just keeps comming back.
So I thought that the rom might have went bad, dont know how but I though I would just refalsh it to see if it works. I flashed correctly and said it was complete but just reboot back to the tri-color screen. So the flash will complete fine but cannot get out of boot loader. I tryed flashing original and cooked rom, same result.
So I thought I would try and flash back to an older hard spl, I have hardspl 3.29 right now so I thought I would try hardspl 3.28 just to see if issue would be fixed. So I flash it and it completes, then reboots to tri-color again, but instead of saying 3.28 like it should it still says 3.29. Wierd??
So I through I would give mtty a try and see if I could get past the boot loader. I tryed the boot command which gave me a command error so I did some searching and tryed:
"set 16 0"
"task 8" <- causes phone to restart and goes back to tri-color.
Right now I am stuck at this tri-color screen and I think I am never going to get out. This came up randomly my phone has been working fine for a while now until today.
Can someone please help me on how to make it work????
Thank you to anyone who provides help.
Hi sngskunk, I have a similar problem. After a radio flashing, my phone stopped in tri-color screen, returned to normal after 24h, then returned to hang on tri-color screen. By coincidence it happened after using the camera. I suspect that might be a hardware problem, maybe a short circuit in the camera button, but I will make sure after opening the unit and clean the contacts of the button.
I am going to try and take the phone apart and look at the camera button to see if that is the problem, but is there a command in mtty that will boot the os, after the bootloader.
Because i have tryed the boot command and that doesn't work in Hardspl 3.29, I get a cammand error. I have tryed resetting it but if the camera button is stuck then it is going to go back to the original tri-color screen.
Okay so I toke my phone apart to check the camera button, the button looks fine didnt look dirty or full of dust and I check the micro switch and it seemed okay. While the phone was a part I turned it on to check to see if it would boot to the os, but it didnt it stopped at the spl, and I know that the camera button wasnt pushed.
Going to try and install a new radio just to see if that fixes it, if not, I am all out of ideas.
sngskunk said:
Okay so I toke my phone apart to check the camera button, the button looks fine didnt look dirty or full of dust and I check the micro switch and it seemed okay. While the phone was a part I turned it on to check to see if it would boot to the os, but it didnt it stopped at the spl, and I know that the camera button wasnt pushed.
Going to try and install a new radio just to see if that fixes it, if not, I am all out of ideas.
Click to expand...
Click to collapse
Try flashing a shipped ROM via MicroSD
I tryed installing a radio by itself, didnt fix it.
Installed original shipped rom from microsd, flash when perfect, said it was complete, reset it phone and it came back to the tri-color screen.
There is no "RUU**" i dont know what else is in that string but some people get in at the top of the screen when they are having my problem, but mine does not have it.
I would try going though the FrankenKaiser steps and see if that works? Just an idea
I looked up the post you are talking about and I am confused on it, because if I have the phone connected with the usb cable and use mtty. There is no command named dload.
Code:
cmd>dload
Command error !!!
Ofcouse now that I look at that post again that was in the spl, I cannot get to the radio boot loader the way he says, holding down the green phone and turning on the phone doesnt work just boots into the spl again.
Okay well i found a good post on how to do it but I get errors on the commands becuase in the post he isnt using hardspl 3.29 the cammand is the following:
rtask a <--- gets command error
austinsnyc said:
I would try going though the FrankenKaiser steps and see if that works? Just an idea
Click to expand...
Click to collapse
austinsnyc,
using these steps? -> http://forum.xda-developers.com/showthread.php?t=394584
I tryed those steps, but didnt work it wont go into radio boot loader mode.
I also tryed these steps: http://forum.xda-developers.com/showthread.php?t=393337
But I cannot execute the command: "rtask a", I get a command error.
sngskunk said:
I tryed those steps, but didnt work it wont go into radio boot loader mode.
I also tryed these steps: http://forum.xda-developers.com/showthread.php?t=393337
But I cannot execute the command: "rtask a", I get a command error.
Click to expand...
Click to collapse
I try these steps on saturday, but hardspl 3.* don't suport rtask command . If nothing more resolve, I am putting my chips on this tool (read post 6) ->http://forum.xda-developers.com/showthread.php?t=415839
I've run into the exact same problem.
I just turned off my phone, turned it back on and now it's just stuck.. can't load anything.
2nd time i've had a problem with this phone
Ok so i've also noticed something else with this problem.
Basically, what had happened, I did the same thing as the first post. All I did was reset my phone. I turned it back on, and i'm stuck at bootloader screen
When it is loading, it flashes the screen to a complete white screen that says "Loading. No Image File!"
Then it goes right back to the bootloader screen and that's that.
It seems as though hard resetting, mtty or flashing back to original rom does not work.
Does anyone know what the heck is going on?
@kjb, have you tried the suggestions by AllTheWay and myself in the other thread you posted in. It's very hard to keep up when issues are on going in 2 threads. Please stick to just one, I suggest the other one.
Link here: http://forum.xda-developers.com/showthread.php?t=418692
Thanks
Dave
DaveShaw said:
@kjb, have you tried the suggestions by AllTheWay and myself in the other thread you posted in. It's very hard to keep up when issues are on going in 2 threads. Please stick to just one, I suggest the other one.
Link here: http://forum.xda-developers.com/showthread.php?t=418692
Thanks
Dave
Click to expand...
Click to collapse
Hi Dave,
Yes I have tried flashing the original rom. But unfortunately, i'm still stuck at the bootloader screen and it did nothing.
I am extremely confused now
kjb86 said:
Hi Dave,
Yes I have tried flashing the original rom. But unfortunately, i'm still stuck at the bootloader screen and it did nothing.
I am extremely confused now
Click to expand...
Click to collapse
Tri the link in my sig, There are some suggestions in the Wiki.
Ta
Dave
DaveShaw said:
Tri the link in my sig, There are some suggestions in the Wiki.
Ta
Dave
Click to expand...
Click to collapse
hmmmm, ok for mtty it's not working. There is no USB present and I can't select it.
It won't allow me to do any of the settings just by selecting COM1 or COM2.
kjb86 said:
hmmmm, ok for mtty it's not working. There is no USB present and I can't select it.
It won't allow me to do any of the settings just by selecting COM1 or COM2.
Click to expand...
Click to collapse
Did you disable USB connections first?
AllTheWay said:
Did you disable USB connections first?
Click to expand...
Click to collapse
No. Nothing was disabled. Activesync was not present at all either and nothing was in the task manager.
Few things i've noticed:
a) when flashing to a new rom (or attempting too) there is no image listed in the previous ROM
b) my phone would be off, I'll plug it in to the USB and all of a sudden my phone will turn on right to bootloader.
Don't know if that makes a difference, but it's just some observations for you guys.
kjb86 said:
No. Nothing was disabled. Activesync was not present at all either and nothing was in the task manager.
Few things i've noticed:
a) when flashing to a new rom (or attempting too) there is no image listed in the previous ROM
b) my phone would be off, I'll plug it in to the USB and all of a sudden my phone will turn on right to bootloader.
Don't know if that makes a difference, but it's just some observations for you guys.
Click to expand...
Click to collapse
No you need to disabled USB connections in Activesync for MTTY to work!
I installed HardSPL and checked to make sure it installed fine, ect. Then I went and downloaded this ROM.
http://forum.xda-developers.com/showthread.php?t=497699
I established an activesync connection and then installed the ROM, waited until it was 100% done and it reset itself. The next time it booted up, it stuck at the AT&T logo screen. I read somewhere to hard-reset when you get to the part where you configure the stylus... wanted to get back to a working phone, I hard-reset and formatted. When I reboot it still sticks at the AT&T screen, with the 3 colums of orange letters on the bottom.
Did I do something wrong, and what can I do?
Thanks.
get back to the tri-screen bootloader (hardspl, turn the phone on, volumedownkey+centerbutton+reset) , reflash the rom...
Is your phone cdma? If so, then, yeah, you did something wrong.
paperWastage said:
get back to the tri-screen bootloader (hardspl, turn the phone on, volumedownkey+centerbutton+reset) , reflash the rom...
Click to expand...
Click to collapse
The part where it says it will delete all information, ect. ect. and then it takes a few seconds and says restore complete VolUp to reboot?
I tried that and it yeilded the same results, and I just tried again now and it still sticks at the AT&T screen.
Farmer Ted said:
Is your phone cdma? If so, then, yeah, you did something wrong.
Click to expand...
Click to collapse
I should have specified, it's a GSM phone. The AT&T Fuze.
I also updated the OP with a working link, didn't realize it linked back to the ROM Development page. =/
Thanks for the suggestions though. I'm hoping I didn't do anything I'll regret, I can't afford to have an expensive paperweight right now.
go into bootloader (volume down and reset button) until u see the tri color screen. then connect the phone computer using ur usb cable and you should see something on the bottom of the screen that says "usb" now try flashing a ROM again.
flash the stock rom, then try reflashing the custom rom again!
Same thing happened to me with a Energy Rom so I just had to choose a different version of it and it worked
Hi,
I bought a HTC Touch Pro today from ebay, all working fine and everything. So I go to flash to the latest energyrom, using this guide:
http://lievenvw.wordpress.com/2008/...c-diamond-or-htc-touch-pro-with-a-custom-rom/
It starts, then has an error saying it was unable to flash and i should check my devidce etc. I look at my phone and it has a whit background and it just says 'Loading ...'. I had to take out the battery to get it back on again.
Everything is fine, my phone works, but I don't think I can flash anymore.
I then read this guide:
http://lievenvw.wordpress.com/2008/...c-diamond-or-htc-touch-pro-with-a-custom-rom/
When i got to this step:
Enter bootloader mode on your phone:
While the device is booting up or with the device turned on, press and hold the volume down button along with the power button, then press the reset button with the stylus tip, then release the volume down and power buttons when bootloader tricolour screen appears.
Everything was fine the tricolour appeared and the text, then suddenly it went back to 'Loading ...'
I really want to flash my phone, and i'm worried I won't be able to know. Ive tried hard reset, but it didn't do anything. Is there anything else I can do?
I've left the loading screen for 20 minutes, i don't think it's doing anything...
If anyone could help me that would be amazing.
Cheers
EDIT:
I just tried flashing with the default firmware, as guided here:
http://forum.xda-developers.com/showthread.php?t=410150
The phone fades to black, and doesn't show anything at all, and then i get ERROR [260] CONNECTION, and tells me to check if it's plugged in etc.
Very strange, i'm really worried I won't be able to fix this..
I had this issue
I had this issue with a Fuze that I had about a week ago.
It comes with a newer version of bootloader.
All you have to do is remove the Sim card and SD Card before you flash. That made the black fading go away and flashing succeeded.
Start by installing Hard SPL first. Once that is in they you can start flashing the rom.
How about reading and posting in the noob flashing thread? Do you know what hard spl, gsm, and cdma are? If not, you're either wasting your time and/or your phone.
Well I am clearly an idiot, thankyou both for you posts, phone is now successfully flashed!
Hi there,
I need help to know whats going on with my HTC Touch Pro.
After more than 1 year of use, the phone started yesterday giving this message:
RAPH100
SPL-5.05-0000
MicroP-Raph (LED) v13
MicroP-Raph (KEY) v5
PSOC-Raph STAGE_CVT v0x36
PCBID 0x80
RID 0x0
This happens with the screen splitted in 4 colours.
Before giving this message I can read very quickly a system message saying "No image file!"
The phone JUST shows this message, I can't do ANYTHING on it. I have tried to make an hard reset, but nothing - only shows this message.
What can I do to fix this?
thanks,
Alex
soo it doesnt boot up all the way to Windows Mobile screen? if so, then flash a ROM a STOCK Rom from the HTC Site, all though idk how to do that since i havent been in that situation before, but just connect ur device to the computer
XERO_Racer said:
soo it doesnt boot up all the way to Windows Mobile screen? if so, then flash a ROM a STOCK Rom from the HTC Site, all though idk how to do that since i havent been in that situation before, but just connect ur device to the computer
Click to expand...
Click to collapse
I there,
I have downloaded this file from htc.com site:
_HTC Touch Pro_RUU_Raphael_HTC_PTG_5.05.410.1_Radio_Signed_Raphael_52.58.25.30_1.11.25.01_Ship
Somehow the laptop was able to recognize usb connection to HTC and it seems it was installed. BUT in practice, everything stayed the same - only that screen appear, and nothing else.
Any other suggestions?
thanks
Try flashing from MicroSD. I think there's a summary of how to do this in one of the stickies in the Rom Development subforum. Sounds like your rom got corrupted or something is trigger that screen.. That screen you mention is the bootloader screen. It's access by holding down the Volume Down rocker as you power on the device.
SDreamer said:
Try flashing from MicroSD. I think there's a summary of how to do this in one of the stickies in the Rom Development subforum. Sounds like your rom got corrupted or something is trigger that screen.. That screen you mention is the bootloader screen. It's access by holding down the Volume Down rocker as you power on the device.
Click to expand...
Click to collapse
tried to FLASH HARDSPL but was not successful.
Can this be a hardware problem?
is there a way of reinstall the windows mobile, besides doing an hard reset?
Even i can flash the ROM , but the screen is always the same with the 4 colours.
more clues?
in your case, doing a hard reset seems to be the least of your worries. you can install the stock roms w/o hardspl so you should give that a shot first. through usb and through sd card if usb doesn't work.
from what you've said, you could flash the stock ROM but when you start up your phone, it brings you back to bootloader?
also, when you attempted to flash hardspl, what error did you get?
fatpandas said:
in your case, doing a hard reset seems to be the least of your worries. you can install the stock roms w/o hardspl so you should give that a shot first. through usb and through sd card if usb doesn't work.
from what you've said, you could flash the stock ROM but when you start up your phone, it brings you back to bootloader?
also, when you attempted to flash hardspl, what error did you get?
Click to expand...
Click to collapse
Hi there,
When I try to install hardspl the progression bar does not goes forward, it stays in the 0% - this by USB - I did not try it in the SDcard, but I think it should be the same...
I can flash the ROM with USB, but after the install is complete it brings me back the same 4 colours screen with that error I have mentioned first.
The funny is the cellphone just started this from day to night. Did not fell on the floor, I didn't installed anything... strange.
Can this be an hardware problem?
It seems like your Volume Down button got stuck - therefore you cannot pass bootloader screen.
pilgrim011 said:
It seems like your Volume Down button got stuck - therefore you cannot pass bootloader screen.
Click to expand...
Click to collapse
How can I fix this?
Even if the Vol Down button was stuck, she wouldn't get the "No Image File" message... it would just go into bootloader mode and say, "Serial".
I had this problem when I first got my Fuze and was playing with new roms. The solution would be to flash a new rom on there and be careful.
Connect the phone through USB and turn on the phone while holding Volume Down
Tri-Color screen should read "USB" at the bottom.
Load up the official firmware upgrader and click through the screens.
Wait for it to fully load.
If you are having problems with the official firmware, perhaps you have a bad download and need to redownload it.
Honestly, I think you should take it in (or send it in) for service. I'd quit screwing with it. You've got the stock rom and spl on there, and it's stuck in bootloader for some mysterious reason. You're ok. But if somehow you flash any non-stock firmware on there, and you end up still stuck in bootloader, you may have passed the point of no return, warranty-wise. Bummer that it happened, and it could well be a stuck volume down button, but I wouldn't try flashing as the solution.
i'd agree. since it seems like you never managed to successfully flash anything, everything should still be stock. and sometimes you get lucky and they don't care about that anyways. just send it in
Farmer Ted said:
Honestly, I think you should take it in (or send it in) for service. I'd quit screwing with it. You've got the stock rom and spl on there, and it's stuck in bootloader for some mysterious reason. You're ok. But if somehow you flash any non-stock firmware on there, and you end up still stuck in bootloader, you may have passed the point of no return, warranty-wise. Bummer that it happened, and it could well be a stuck volume down button, but I wouldn't try flashing as the solution.
Click to expand...
Click to collapse
I was just about to sent the HTC to the service today, but one last try before sending it: tried to turn it ON, and...it worked!! With the new ROM installed.
VERY STRANGE...
Well, as long as it keeps working that's fine...but I will never know what happened with my HTC these last days...
thanks for you guys help!!
player911 said:
even if the vol down button was stuck, she wouldn't get the "no image file" message... It would just go into bootloader mode and say, "serial".
I had this problem when i first got my fuze and was playing with new roms. The solution would be to flash a new rom on there and be careful.
Connect the phone through usb and turn on the phone while holding volume down
tri-color screen should read "usb" at the bottom.
Load up the official firmware upgrader and click through the screens.
Wait for it to fully load.
If you are having problems with the official firmware, perhaps you have a bad download and need to redownload it.
Click to expand...
Click to collapse
u r the best ty veryyy much.....i was having the same problem & solved with ur instruction...ty again
herhh87d7 said:
Hi there,
I need help to know whats going on with my HTC Touch Pro.
After more than 1 year of use, the phone started yesterday giving this message:
RAPH100
SPL-5.05-0000
MicroP-Raph (LED) v13
MicroP-Raph (KEY) v5
PSOC-Raph STAGE_CVT v0x36
PCBID 0x80
RID 0x0
This happens with the screen splitted in 4 colours.
Before giving this message I can read very quickly a system message saying "No image file!"
The phone JUST shows this message, I can't do ANYTHING on it. I have tried to make an hard reset, but nothing - only shows this message.
What can I do to fix this?
thanks,
Alex
Click to expand...
Click to collapse
Make be you should change your ROM at once~