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~
Related
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.
I am unable to get into boot loader mode.
I've pressed camera + power and reset as usual but it won't go into bootloader it just boots the phone up.
I managed to get into bootloader mode using a KaiserCustomRRU and then it picked up the new ROM from the SDCard but when i press power to flash the rom nothing happens.
I can still boot into windows mobile and the power button works when I press it there.
I only got this kaiser a day ago is it possible this is a new version or something?
Please help!
Harsesis said:
I am unable to get into boot loader mode.
I've pressed camera + power and reset as usual but it won't go into bootloader it just boots the phone up.
I managed to get into bootloader mode using a KaiserCustomRRU and then it picked up the new ROM from the SDCard but when i press power to flash the rom nothing happens.
I can still boot into windows mobile and the power button works when I press it there.
I only got this kaiser a day ago is it possible this is a new version or something?
Please help!
Click to expand...
Click to collapse
Are you fully pressing the Camera button, it has two levels, it must be presses in fully and help whilst you restart your phone with the stylus (or turn on if the phone is off).
Off Topic:
This makes a nice change, helping someone into bootloader, rather than someone stuck in it.
Dave
Yup I'm pressing it down super hard, I've had the kaiser since it came out so I know I'm doing it as usual. For some reason it isn't working this time.
I had lots of trouble flashing HardSPL aswell! Now this problem with entering boot loader. This is getting irritating .
Harsesis said:
Yup I'm pressing it down super hard, I've had the kaiser since it came out so I know I'm doing it as usual. For some reason it isn't working this time.
I had lots of trouble flashing HardSPL aswell! Now this problem with entering boot loader. This is getting irritating .
Click to expand...
Click to collapse
Does the Camera button work normally? I.e. Launches the camera in Windows.
What problems are you having with HardSPL?
Dave
Yup camera button does work normally.
I had to reset the device loads of times before customRUU noticed that the phone was plugged in.
At the moment I'm stuck in RUUNBH recovery mode in HardSPL. It detects that I have put a memory card with a KAISIMG.nbh into the phone, it says that it will flash radio, rom, splash and says press power to continue but when I press power nothing happens. Now no matter what I do I can't get out of HardSpl and I can't even flash a rom anymore
Harsesis said:
Yup camera button does work normally.
I had to reset the device loads of times before customRUU noticed that the phone was plugged in.
At the moment I'm stuck in RUUNBH recovery mode in HardSPL. It detects that I have put a memory card with a KAISIMG.nbh into the phone, it says that it will flash radio, rom, splash and says press power to continue but when I press power nothing happens. Now no matter what I do I can't get out of HardSpl and I can't even flash a rom anymore
Click to expand...
Click to collapse
Check the link in my sig for getting out of the bootloader...
Dave
Thanks so much
Ok so its booting up again but I'm still having the same problem, ie it won't get me into bootloader using camera and power button.
I can't even press the 2 buttons to clear storage either, it just boots straight into the rom.
Harsesis said:
Thanks so much
Ok so its booting up again but I'm still having the same problem, ie it won't get me into bootloader using camera and power button.
I can't even press the 2 buttons to clear storage either, it just boots straight into the rom.
Click to expand...
Click to collapse
Very strange...
Why do you need to access the Bootloader? To flash from SD Card?
Ta
Dave
Yup also I'm having weird problems which I think are associated with this particular problem.
When I boot up the rom lots of keys just randomly get pressed. e.g. if I have a pin set loads of characters will be put into the input box and the only way i can stop it is by pressing a hardware button.
I'm trying to flash a dutty rom which I know doesn't really have those kinda problems to see if its just the rom, although other people aren't reporting the same problem with the rom though :/
Harsesis said:
Yup also I'm having weird problems which I think are associated with this particular problem.
When I boot up the rom lots of keys just randomly get pressed. e.g. if I have a pin set loads of characters will be put into the input box and the only way i can stop it is by pressing a hardware button.
I'm trying to flash a dutty rom which I know doesn't really have those kinda problems to see if its just the rom, although other people aren't reporting the same problem with the rom though :/
Click to expand...
Click to collapse
Flash back to your Original ROM, Radio and SPL. If the problems are still occuring, take it back to the shop, IMO.
Dave
Know where I can find the original T-mobile splash?
Harsesis said:
Know where I can find the original T-mobile splash?
Click to expand...
Click to collapse
No Idea, try searching / asking in this thread: http://forum.xda-developers.com/showthread.php?t=335568
Ta
Dave
Reverted everything back to default now, still got the same problem so I'm going to get a replacement send out to me tomorrow.
Do you think there is a new version of the kaiser that messes up when you flash hardspl?
Harsesis said:
Reverted everything back to default now, still got the same problem so I'm going to get a replacement send out to me tomorrow.
Do you think there is a new version of the kaiser that messes up when you flash hardspl?
Click to expand...
Click to collapse
I doubt they gave you that newer Model what doesn't work.
I think it is the SPL that figures out wether or noot to boot the OS or run the Bootloader... when loading the OS the SPL checks for what keys are pressed and goes into the SPL or OS.
If Hard SPL and the OEM SPL fail to load the bootloader, there must be something wrong with the device IMO.
Ta
Dave
Harsesis said:
Yup also I'm having weird problems which I think are associated with this particular problem.
When I boot up the rom lots of keys just randomly get pressed. e.g. if I have a pin set loads of characters will be put into the input box and the only way i can stop it is by pressing a hardware button.
I'm trying to flash a dutty rom which I know doesn't really have those kinda problems to see if its just the rom, although other people aren't reporting the same problem with the rom though :/
Click to expand...
Click to collapse
I have the same problem with key press, it happened after a recent flash to a new rom.
I have found out what keys it is in my case. It is the "button 6" (voice recorder) and "edfc".The last are just endlessly pressed. Anybody knows how to fix this? My temporary fix was to remap button 6 to "rotate screen" but it is really anoying. I would like to just disable button 6, until I can return it, if there is no fix.
The problem has persisted over 3 roms now (PV rom (8 oct by medkid) - where it all started, Garmin 4.3 and now hyperdragon III 6 oct)
any help will be greatly welcomed!
I have a Kaiser which I updated a while ago with WM6.1 official Belgian dutch. Since it became way to slow, I wanted to hard reset the device. Since a couple of hours, it has been stuck on the green WM screen saying The device is erasing the memory, Please wait...
I have been looking through the forum, but have not found the same issue.
It does not come up in acctive sync, so a normal relaod is not possible. Any ideas?
bsgbelg said:
I have a Kaiser which I updated a while ago with WM6.1 official Belgian dutch. Since it became way to slow, I wanted to hard reset the device. Since a couple of hours, it has been stuck on the green WM screen saying The device is erasing the memory, Please wait...
I have been looking through the forum, but have not found the same issue.
It does not come up in acctive sync, so a normal relaod is not possible. Any ideas?
Click to expand...
Click to collapse
manually go into bootloader if you want to reflash the rom, if phone is powered on hold camera button in and the softreset button at the same time! it sounds like you possibly have had a bad flash, OR you had a bad download!!!
Not possible to flash anything
what I've tried so far:
- activate active sync to install hardSPL. Not working
- install HardSPL through microSD. Not working
- install ROM through SD. Not working
I tried a non HCSD for a change, and then I see the loading scree flashing up, but quickly says No rom found and returns to the bootloader screen.
The only thing that works is load the bootloader (red green blue white) into a screen that says:
KAIS130
SPL-3.29.0000
CPLD-8
Serial
When connected to USB, it says USB, but no disk is showing in Explorer or any connection is made to AS
The only thing I've done in the past is flash the 6.1 rom through the system provided by HTC with a file called RUU_Kaiser_HTC_NLD_3.29.404.0_radio_sign_25.83.40.02_1.65.16.25_Ship.exe
Please help, I really like this phone and hate to loose it
put it into bootloader, connect it to the computer and then flash one of the htc roms. make sure its an htc rom, you cant flash a custom rom cause you dont have hardspl
I have not been able to find the original rom, only the exe from htc which says Connect with active sync. Do I have to set it in bootloader and then execute the program?
Solved
Just want to let you know I sorted it out!
Flashing the original rom does not need active sync, the bootloader USB connection is sufficient.
After this, the phone restarted in 'Erasing memory' mode, but was able to finish it and reinstall the whole rom.
I believe I got the taste of it and will start testing some other roms...
msd24200 said:
manually go into bootloader if you want to reflash the rom, if phone is powered on hold camera button in and the softreset button at the same time! it sounds like you possibly have had a bad flash, OR you had a bad download!!!
Click to expand...
Click to collapse
Thanks, worked fine
majedaly said:
Thanks, worked fine
Click to expand...
Click to collapse
good to know
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!