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.
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.
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~
My phone is looping (on and off) during the boot sequence. The boot screen (red green yellow) says code error then goes to the update screen. It starts to flash and then shuts off for a couple of minutes and does the same sequence again. I was running Nedidum v4 and activated the lock screen. Every since then I cant boot to this rom nor can I flash the stock sprint rom. Is my phone bricked? If i take it to sprint can they tell I was running a cooked rom? Note: I reported my touch pro lost through assurion to get this tp2. Can I do it again? Helpppppppppppppp!!!!!
jutaejrtouch said:
My phone is looping (on and off) during the boot sequence. The boot screen (red green yellow) says code error then goes to the update screen. It starts to flash and then shuts off for a couple of minutes and does the same sequence again. I was running Nedidum v4 and activated the lock screen. Every since then I cant boot to this rom nor can I flash the stock sprint rom. Is my phone bricked? If i take it to sprint can they tell I was running a cooked rom? Note: I reported my touch pro lost through assurion to get this tp2. Can I do it again? Helpppppppppppppp!!!!!
Click to expand...
Click to collapse
Perhaps this is karma hitting you in the ass?
Go to the boot loader by shutting the phone off, holding down the vol down button then turning the phone back on.
Once in the boot loader try flashing to the stock rom.
To answer your question, yes, Sprint could tell. That said, they aren't likely to check.
gamescan said:
Perhaps this is karma hitting you in the ass?
Go to the boot loader by shutting the phone off, holding down the vol down button then turning the phone back on.
Once in the boot loader try flashing to the stock rom.
To answer your question, yes, Sprint could tell. That said, they aren't likely to check.
Click to expand...
Click to collapse
it wont let me flash...it starts flashing and at about 10% phone shuts off...few minutes later it turns itself back on and goes to the boot--flash screen. i"ve tried 5 different roms including stock sprint. Only thing on card is the image file. You say sprint can't tell...I thought the boot screen says security unlocked or something like that?
jutaejrtouch said:
it wont let me flash...it starts flashing and at about 10% phone shuts off...few minutes later it turns itself back on and goes to the boot--flash screen. i"ve tried 5 different roms including stock sprint. Only thing on card is the image file. You say sprint can't tell...I thought the boot screen says security unlocked or something like that?
Click to expand...
Click to collapse
He is saying that sprint could figure out you flashed your phone, but it is more likely that they won't even check, as most users probably won't flash their phone. At the very least you could go through insurance.
jutaejrtouch said:
it wont let me flash...it starts flashing and at about 10% phone shuts off...few minutes later it turns itself back on and goes to the boot--flash screen. i"ve tried 5 different roms including stock sprint. Only thing on card is the image file. You say sprint can't tell...I thought the boot screen says security unlocked or something like that?
Click to expand...
Click to collapse
Yes, Sprint can tell if someone bothers to look. Chances are just low that someone will look.
Why are you flashing from a card? Ditch the card.
Flash the STOCK Sprint ROM over USB.
gamescan said:
Yes, Sprint can tell if someone bothers to look. Chances are just low that someone will look.
Why are you flashing from a card? Ditch the card.
Flash the STOCK Sprint ROM over USB.
Click to expand...
Click to collapse
I have Verizon but I agree, there are too many variables when flashing via sd card. A faulty or cheap card, bad sectors on the card itself, your card reader copying the rom file incorrectly, a bad format on the card, the list goes on and on with what can go wrong flashing via sd card. I only flash via USB. Then again I use buildos so I never had a problem with roms. Thats why I like cookin my own rom. No headaches.
Relax heres what you do.
bro heres what you gotta do to fix your pfoblem, first format your sd card to fat32 then copy the nbh file onto the card, rename it to RHODIMG insert the sd card then enter the boot loader menu by first taking out the battery, and reinserting it. now with the phone off hold the volume down button while pressing the power button this forces the device into bootloader mode. your screen WILL read RHODIMG os. now press the power button again to install whatever rom you want but I would recommend using a stock rom or one that you know works, ie- from past experience.
trust me bro do this and all will be fine again,
HAPPY FLASHING
oh dont forget to press the soft reset button once the rom installation is done when the screen says installation successful,
once again HAPPY Flashing>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
the nbh file can be found next to the RUU application of whatever rom you choose when you open the rom with winrar this is the rom that will be flashed onto the phone.
sapperpipo said:
bro heres what you gotta do to fix your pfoblem, first format your sd card to fat32 then copy the nbh file onto the card, rename it to RHODIMG insert the sd card then enter the boot loader menu by first taking out the battery, and reinserting it. now with the phone off hold the volume down button while pressing the power button this forces the device into bootloader mode. your screen WILL read RHODIMG os. now press the power button again to install whatever rom you want but I would recommend using a stock rom or one that you know works, ie- from past experience.
trust me bro do this and all will be fine again,
HAPPY FLASHING
oh dont forget to press the soft reset button once the rom installation is done when the screen says installation successful,
once again HAPPY Flashing>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Click to expand...
Click to collapse
Thanks all for your input...I've been flashing a year now, probably at least 500 times. Via sd card or activesync. I've tried everything..removing battery...formatting card...lada dada. cant connect via usb cause phone wont get past boot screen. I gave up and reported it missing o get a new one. It arrives today. I honestly think its the battery not holding a charge. Guess i find out for sure when the new tp2 arrives today. I'll post back here when i find out for sure.
Well got my new tp2 in this morning. I put the new battery in the old tp2 and it fired right up....to bad i had to waste my final insurance claim because of a battery.