Related
ok, now I am totaly screwed.... imate stuck in loading screen with version numbers etc... Not going further and bootloader not available.... Is there any way to communicate with unit while it's in this mode?
what you are saying is unclear. Does your device say "Serial" (or "USB") on top with "V 1.06" on the bottom?
If so, you ARE in bootloader mode. If not, then please specify what it actually says on the screen
no, it's not in bootlader mode. it's in Tmobile screen at the bottom it says R 1.12.00
G blah
D blah
it stuck there. and I can't enter bootloader mode. looks like it's totaly dead
What happens when you try to enter bootloader (Power - Action - stylus)?
What happens when you try to press (Camera - Record - Stylus)?
GO TO HELL ROM 1.72.104
F%@#&!?G FREAK ROM!! :evil:
Please calm down... in a day or two, this problem will be solved and everyone will probably be back to where they were
((and a lot smarter than they were too))
Victor said:
What happens when you try to enter bootloader (Power - Action - stylus)?
What happens when you try to press (Camera - Record - Stylus)?
Click to expand...
Click to collapse
It both cases it still sits in this screen
Try removing the battery and waiting for a period of time (20 Mins ??)
Then try the two things again (first without the battery -- for the heck of it -- and then replace the battery and try them)
...obviously, you need to remove it from the charger too :wink:
to be clear... nothing is expected to happen when you try to do these without the battery in, except perhaps (??) clear out any remaining charge held in capacitance, if any.
Kinda like removing the batteries in the remote control of a TV and then pushing a button on it (there is always enough charge in the capacitors for a single push/command to the TV
that once happent to me
and softreset dident help
so i did a hardreset and that fixed it
fixed my data too though :/
Rudegar said:
that once happent to me
and softreset dident help
so i did a hardreset and that fixed it
fixed my data too though :/
Click to expand...
Click to collapse
nothing happenes Sent email to imate tech support. I am not sure if they going to warranty unit with Tmobile betta screen stuck on IMATE. looks like i am short 700 USD........
Is there any way to communicate with XDA2 when it stuck in this loading screen? Terminal via serial cable doesn't work. anyother low level programs are out there? please, help.
Have figured out that the problem is in the Bootloader. If there is a way to (and I know there is) revert to an older Bootloader version, then the problems will all be solved.
Problem Solved : Dead devices due to tmob 1.72 + Downgrade
OK Guys. Problem Solved : Dead devices due to tmob 1.72 + Downgrade
http://forum.xda-developers.com/viewtopic.php?t=8606
That's great, but unfortunately my device is one step more screwed that others - no bootloader not even working Windows now.
Is there any way to boot directly from SD card?
victor,
can you upgrade or downgrade the bootloader ? If you can, HOW? please post the way to upgrade or to downgrade the bootloader. :shock:
ID64,
I had an XDA I and wiped the bootloader by accident. As far as I know, you have only two options. The first one is JTAG [http://www.xda-developers.com/jtag/] but I don't think the boards have been documented yet for XDA II. The other option is to bring it back to where you bought it from. Tell them there's something wrong with it and play dumb. If you're lucky they might replace it for you, if they assume that you are still within warranty.
Yes, there is a way to upgrade/downgrade the Bootloader. I just don't know how.
The bootloader is locked, that is the problem you have (except for those who cannot access the bootloader).
If you know the right syntax and use the password to the bootloader (it is BOOTLOADER), you can load the proper ROM back using the "LNB" command. However, they have changed the syntax since ITSME's doc on the subject, or he mis-documented the syntax to the bootloader. Or at least his syntax was wrong with 1.06 version.
I got mine fixed, but I have means available that 99.9% of the people out there do not have. If I knew more, I would tell you about the percise syntax in the bootloader -- but alas, I am not a developer.
Victor said:
Yes, there is a way to upgrade/downgrade the Bootloader. I just don't know how.
The bootloader is locked, that is the problem you have (except for those who cannot access the bootloader).
If you know the right syntax and use the password to the bootloader (it is BOOTLOADER), you can load the proper ROM back using the "LNB" command. However, they have changed the syntax since ITSME's doc on the subject, or he mis-documented the syntax to the bootloader. Or at least his syntax was wrong with 1.06 version.
I got mine fixed, but I have means available that 99.9% of the people out there do not have. If I knew more, I would tell you about the percise syntax in the bootloader -- but alas, I am not a developer.
Click to expand...
Click to collapse
Thanks for the reply, Victor. When you talking about commands for bootloder what connection to PC you are talking about? Serial or jtag?
I am referring to the device in the cradle, in bootloader mode. The screen in this mode should read "USB" on top and "V.1.06" (or whatever version) on the bottom. Very hard to read, as there is no backlight.
Anyhow, just for fun.... why don't you try the following:
Uncheck the USB option in Active Sync Connection Settings
Cold boot your system (hard reset)
place the device in the cradle
run the communications software (found on this forum)
When asked which COM port to use, click on the down arrow and see if there is a USB port listed (should be top entry in list).
If so... click it. (if not, you are basically done)
After clicked, then hit return (enter) on the pc a few times.
Anything happen?
So I'm a total n00b at unlocking phones but I was trying to unlock my alltel 6800 and after running the program and following the steps I'm stuck on the screen that is red/green/blue/white that shows the rom info and says USB at the bottom when plugged into the pc. I tried a hard boot/soft etc. and can't find a solution. Also activesync is not recoginizing it. Thanks much for any help.
i believe you have to flash it with a new rom/radio.
download the the newest radio. connect your phone via usb. your screen should be in the tricolor (2.40spl) at this point. run the radio flash.
Download a new rom. do the same as above.
to get to tricolor screen (hold power + camera + press soft reset)
Yeah i'm thinking I might have to load it from the SD card but I can't find my stinkin adapter so I can format the SD card. Activesync is not recognizing my phone at all.
=I'm stuck on the screen that is red/green/blue/white that shows the rom info and says USB at the bottom when plugged into the pc.
Click to expand...
Click to collapse
it IS recognizing the phone being plugged in if it says USB at the bottom, so just flash a new rom/radio and you should be good.
HOLD, Give a little more info please
wilmheath said:
Yeah i'm thinking I might have to load it from the SD card but I can't find my stinkin adapter so I can format the SD card. Activesync is not recognizing my phone at all.
Click to expand...
Click to collapse
OK, before it is bricked, tell us the numbers on the rainbow screen, then if it is 1.6 then run the 2.40 olipro, then new ROM, then radio. It is not broken yet, activesync does not like it when the unit is in bootloader mode so it will not show it, but the RUU will work if you just go forward with it and when done it will get you out of bootloader. If you get confused and lost then being an alltel unit you can put the 1.6 bootloader back on, run the stock RUU from utstar.com, bring it back stock and start again.
I got it fixed and installed the sprint firmware but silly me let it run through the setup and now it's trying to use the spring network. Sometimes I wish i could punch myself in the face..
Ok so i got no2chem up and running great but I still can't actually dial out. When i dial it says i'm not allowed to etc after a few rings. Is there some way to change back to the alltel network?
ok now i'm running titan 3.35 but can no longer get active sync which is required to relock the phone. I've tried everything but activesync does not want to work anymore. Any ideas?
ok now i'm running titan 3.35 but can no longer get active sync which is required to relock the phone. I've tried everything but activesync does not want to work anymore. Any ideas?
Click to expand...
Click to collapse
First of all, you don't relock your phone...you leave 2.4-olipro on it because it's required to boot your phone with this rom on it.
Second, go into activesync settings and make sure usb is enabled in the connections.
get back to Alltel,,,,
wilmheath said:
ok now i'm running titan 3.35 but can no longer get active sync which is required to relock the phone. I've tried everything but activesync does not want to work anymore. Any ideas?
Click to expand...
Click to collapse
You will need to load up the PRL and then do IOTA.
madman34 said:
You will need to load up the PRL and then do IOTA.
Click to expand...
Click to collapse
I'm sorry but i'm not familiar with those terms. I do have USB enabled on activesync though but it never detects it.
From reading other threads I assumed I had to relock it, then reload the alltel rom to get the radio working again. Is there another way?
I got the factory alltel rom back in and working but it's not letting me make calls still. Any ideas on how to fix this?
Well i got my phone working finally but now the data line is not working. It says I need a password now which I haven't needed before.
I used to enjoy helping to unbrick Kaisers & I had half a dozen to play with, so I learned JTAGing with them, all about the OEMSBL, SPL & Radio Bootloader, working with Jocky in the development of the first mass unbricker for the MSMxxxx series devices, i.e. Frankenkaiser.
Since then the good folks at HTC have really locked things down, shutting the back doors that allowed us to sneak in & fix devices that previously were considered bricks fvor all time, unless you know a hell of a lot & have invested in a jtag box.
Recently I noticed that whenever you reset while holding the Volume up key, the device vibrates three time. After a few more key presses & some magic, I was able to get into DIAG mode, or so it appears using the Qualcomm Diagnostic tools.
I have still not been able to get into Dload mode, but from what I have seen makes me wonder... Just maybe good ole HTC left a back door once again that just maybe we can open & exploit.
I don't want anyone bricking there devices, so I am not going to get into all of the steps yet, but I will work with a few of the old timers to see just what is possible. This would be great, making unbricking possible for the Diamond, TouchPro & even the latest greatest releases, the TouchPro 2 & Diamond 2.
More as it's known.
BTW, for those of you noobies that are like I was & don't listen to warnings, don't be afraid if you hold the volume up key, get the three consecutive vibrations & then find you cannot restart your device. You can, but you must first remove the battery for a short time, then reinsert the battery & then soft reset. Voila, it will boot again.
d wonder what those three vibes were all about. Half the time I go to flash my phone this happens as Im not paying attention to what I'm pressing!
Keep up the good work
Holding the "volume up" key and resetting doesn't do anything other than a normal boot on my Diamond...
l3v5y said:
Holding the "volume up" key and resetting doesn't do anything other than a normal boot on my Diamond...
Click to expand...
Click to collapse
same on my raph
What SPL do you have (that's to GSLEON) as that may make a difference...
Down Vol + RST = Serial Boot Loader.
RAPH110 (is a Fuze)
SPL-5.10.0000
MicroP-Raph (LED) v13
MicroP-Raph (KEY) v5
PSOC-Raph STAGE_CVT v0x36
PCBID 0x080
RID 0x0
Serial
Running latest release production ROM
Down Vol + OK + RST= Clear Storage Util.
Entry into serial boot loader flashes a screen that states "No Image File!", that bootstrap could be used for chipset diags or reflash depending on image file that is present on storage card on boot.
?Glitch
This is great news! But who actually has bricked their touch pro? Most problems are because of hardware failure not because someone bricked it.
DJGonzo said:
This is great news! But who actually has bricked their touch pro? Most problems are because of hardware failure not because someone bricked it.
Click to expand...
Click to collapse
Ummm, I bricked mine awhile back. I'm sure I'm not the only one.
Captain_Throwback said:
Ummm, I bricked mine awhile back. I'm sure I'm not the only one.
Click to expand...
Click to collapse
Oh yeah, I remember reading your thread, sorry. We all brick phones, specially when we flash something we are not supposed to flash. Tip: always make sure your phone (or any hardware/electronic device you are flashing) a chip compatible with the ROM/firmware you are flashing. Sounds dumb, but I have fried things by ignoring this tip.
Anyways, isn't there a way to get all the official ROM's from HTC?
I know LG sells a subscription where you can download all firmwares for all their phones for any carrier. If there is something like that for HTC, maybe someone that has a subscription can help us out with this. I am interested in this, I will look more into this, as I may end up bricking my phone. I do stupid things often enough.
Back to the topic: I get the three vibes then nothing. What are we supposed to press after that? I have a Raph110 (AT&T Fuze)
Captain_Throwback said:
Ummm, I bricked mine awhile back. I'm sure I'm not the only one.
Click to expand...
Click to collapse
No, you for sure are not the only one. If anyone remembers, I bricked my first one while trying to come up with radios from diff. devices.
Now for the million dollar question: What do I do after I hold the Vol Up button and get three vibes?
After a few more key presses & some magic, I was able to get into DIAG mode, or so it appears using the Qualcomm Diagnostic tools.
Click to expand...
Click to collapse
Yes, some prototypes had such a code. But they removed it from production devices. Also the device needed to be security unlocked to make it work.
What keys did you press ? Do you have a GSM or CDMA device ?
Cya,
Viper BJK
viperbjk said:
Yes, some prototypes had such a code. But they removed it from production devices. Also the device needed to be security unlocked to make it work.
What keys did you press ? Do you have a GSM or CDMA device ?
Cya,
Viper BJK
Click to expand...
Click to collapse
GSM buddy. (AT&T Fuze)
updated the official rom and hd2 not turn over any sign of life is only recognized by PC as Qualcomm etc. etc. nothing sync anything hard reset bootloader ..... nothing I can throw it in the trash?
tmous phone?
official rom that's not a tmous official rom?
if yes to both, then its dead and gone.
I ran HSPL3 ok
chucky Rom ok
while installing this rom (_HTC HD2_RUU_Leo_HTC_ITA_1.66.408.1_Radio_Signed_15.30.50.07U_2.06.51.07_Ship)
has stopped and now it is seen from the PC Qualcomm interface has stopped.
ayrton1974 said:
(_HTC HD2_RUU_Leo_HTC_ITA_1.66.408.1_Radio_Signed_15.30.50.07U_2.06.51.07_Ship)
has stopped and now it is seen from the PC Qualcomm interface has stopped.
Click to expand...
Click to collapse
yep, its dead.
(It is from t mobile, yes?)
yes t mobile
but where did I go wrong?
I can repair the phone?
the radio in eth rom you flashed has a ..51.. in teh version number. If you read the tmous (t mobile us) section, there are hundreds of warnings about never flashing a radio with 51 in teh version.
No one has yet repaired it, sorry.
Take it back to t mo? (dont tell them you flashed it)
I mean if I send it in for service or repair should and too expensive?
depends howho honest you are, lots of people have returned them and played dumb and its been fixed under warranty.
I updated my phone (HD2 T-mobile) via internet website and when I finished the updating process, the phone did not work at all.
I tried more than once to switch it on, but it didn't respond. I took the battery out and put it in again, but nothing happened.
When I connect the phone with the charger, the charger light doesn't become on.
It seems that the phone is dead!!!. What do you suggest to solve this problem? If you think it is a hardware problem, what is the name of this hardware
Tray update ROM again
It dose not Enter in bootload mode
How I can apdate rom from diffrent way
What rom did you flash? If it isn't a tmous rom then the phone is destroyed.
HD2-RUU_Leo_HTC_ARA_1.66.415.9_Radio_15.37.50.07U_2.10.50.08_2_Signed_LEO_Ship
This ROM's name
Please support us with a bit more of information.
You´ve got a T-Mobile device and flashed it with a different ROM for a HTC device without branding.
But what did you meant with "flash via Website"? How did you really flash (via Active Sync or via SD card)?
Did you install HSPL or at least SSPL first?
I Flash it via Active Sync
yes I Installed HSPL But sspl I didn't Install
Its dead,the radio in that rom has killed it.
Only options are JTAG or replace mainboard
Though it is strange that the filename says 2.10.50 for the radio version,since 1.66 roms usually come with ..51.. radios,which kill tmouses.
If it really is a ..50.. radio in a 1.66 rom then a tmous should boot but hang at splash, yet you say yours just won't start, so I suspect a typo in the filename. (Not your typo,I can see lots of references to that filename online.)
I am download this rom from HTC site
Mo7ammad_89 said:
I Flash it via Active Sync
yes I Installed HSPL But sspl I didn't Install
Click to expand...
Click to collapse
You said that you have a T-Mobile device, but you didn´t tell that it is the US version of it. Is it or do you have the European version?
If it is the USversion you really flashed the wrong Radio ROM.
For the European version it would be no problem
no My Mobile Is Us version
Mo7ammad_89 said:
no My Mobile Is Us version
Click to expand...
Click to collapse
So it seems you have bricked your device, I would recommend to bring it to a service point and hope that they do not notice what you have done.
Perhaps this thread is a last chance for you:
http://forum.xda-developers.com/showthread.php?t=668347
Good luck!
Thank You My friend But This chance Is Impossible becuse It's need to Enter bootload mode and I can't Enter It
check the pins where the battery connect they bend very easy so you dont get a connection the red light will come on when u charge and the phone wont boot! there are three pins make sure they are all makeing a connection! Its very common!
I am sorry but I don't understand you very well can you explain more please
Mo7ammad_89 said:
I am sorry but I don't understand you very well can you explain more please
Click to expand...
Click to collapse
In other words:
Take out your battery and check the contacts between battery and the deviceframe. Is any of them bent?
No It's Not Any Of Them bent I think
but why you ask About It
AM I can repair My Mobile by them
And If you can explain for me by picture I well be glad
Mo7ammad_89 said:
No It's Not Any Of Them bent I think
but why you ask About It
AM I can repair My Mobile by them
And If you can explain for me by picture I well be glad
Click to expand...
Click to collapse
Sorry, it was not my idea but from b3ltazar. His thought was that your device might get no power to work.
I recommend once again to bring your device to a htc service center in order to repair it. In my mind you seem to have an hardware issue