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?
Related
Hi all,
Hope I may be of help to those who have GSM Error on their Wallabys. I have almost given up hope but I just searched the threads. This is basically what I did:
1. Download xda developers special rom and re-flash via sd card
2. Hard reset, press contact and calendar buttons (or a combination of both), volume button, and soft reset will bring you to the today homescreen (I cant remember exactly what buttons I pressed, I just pressed them all)
3. Re-boot phone, you will notice you still have no radio but you can now enter today homescreen (please take note the "start" menu is not there)
4. Align screen / stylus. You can do this by pressing Action Key then Calendar button.
5. Press Contact and Action Key (both) several times (I think around 20 times). You will hear clicking sound. This will bring out the "start" drop down menu. If it does not pop out, repeat again.
6. Download the correct RSU for your phone. Save into SD and copy to programs (same procedure as in wiki)
7. Run the RSU program, expect to fail at 1%. Re-boot. this time you will be able to active sync your phone again. (my wallaby did to my surprise)
8. I gave up on the RSU 4.16 (after countless tries) and I downloaded RSU 4.21 from xda-developers ftp (exe file) since I am now able to sync to my device.
9. Install RSU upgrade to your device, the phone will automatically re-boot.
10. Surprise! I was able to re-flash the RSU! (I think the problem is the RSU 4.16, try other 4.xx instead but be careful to use the correct version)
Now my Wallaby is up and running again! Thanks to xda-developers and Wiki and to Lumpi. There is no secret. I just did a lot of reading from the threads. It's all there. Good luck guys! Merry Christmas!
why ur wallaby resynched....
The reason it re-synched.... is because... when u go to the wallaby bootloader... and go into the GSM menu's (that allow u to tun off and on the gsm... and band tests... the key to it is there.... just reset those puppies at least 1nce.. then when u reset and boot... voila... it will sync,, but... I'm still stuck on that 1% error... rsu failed!! so.. wish me luck... oh.. btw.. when u get the 1% error it will not sync again until u repeat the process at the wallaby bootloader... so... any ideas anyone>> to get past the 1% error? I've read up and down ... searched left and right here... but no luck yet... I'm still trying what was posted here... so... wish me luck.... !!! oh... question what version is ur wallaby?? PW10A or B?
Re: why ur wallaby resynched....
r5pete said:
The reason it re-synched.... is because... when u go to the wallaby bootloader... and go into the GSM menu's (that allow u to tun off and on the gsm... and band tests... the key to it is there.... just reset those puppies at least 1nce.. then when u reset and boot... voila... it will sync,, but... I'm still stuck on that 1% error... rsu failed!! so.. wish me luck... oh.. btw.. when u get the 1% error it will not sync again until u repeat the process at the wallaby bootloader... so... any ideas anyone>> to get past the 1% error? I've read up and down ... searched left and right here... but no luck yet... I'm still trying what was posted here... so... wish me luck.... !!! oh... question what version is ur wallaby?? PW10A or B?
Click to expand...
Click to collapse
hello..
did you find a solution for 1% error? I have the same issue and I tried all night...and day...and nothing (
Reflash via SD
Hi morph751,
Firstly, thanks for this, I have now finally got my Wallaby back to a state where I can ActiveSync it, and actually run programs on the thing. Unfortunately, the RSUupgrade continually faults at the 1% mark both version 4.16 and version 4.21. The one step in your instructions that I did not follow, was the first "Download xda developers special rom and re-flash via sd card". The problem with doing this, is that when cold booting with the SD card in the slot the device simply hangs at the GSM Error screen. I have bootloader version 6.22, so I assumed this was due to the post 5.17 SD card locking. But the info and utility to bypass this doesn't seem to help either.
Is there something fundamental I am missing in terms of being able to boot the device into a mode that will allow me to flash it via SD?
By the way, when trying to flash the device via Program A, it fails with an error indicating that the power cable is not plugged into the device. The device is in the cradle, with USB connected and power connected to cradle.
OK, by folllowing the instructions at http://forum.xda-developers.com/showthread.php?t=245282, I have been able to sucessfully flash the device to XDA Developers special ROM image 1.2. But I still get Program B failing at 1%, using version 4.21. Has anyone managed to overcome this, if so how? Thanks in advance for any help.
Hi guys, I have some experience with rom flashing, and I did it today as usual - flashed HTC 1.35 ... Update stopped at 1%. I tried everything I could to finish the update (It wasn't my first time ). Now, after restart TyTn is flashing with LCD (black & white) & camera led. I can't do anything, even turn it off. Seems like a problem with bootloader. What should I try before i send it for repairing? Do you have any experience with T-Mobile UK? I'm the legal owner of PDA, but I don't have any receipt. Should I contact seller (ebayer) or post it to T-Mob straight away?
Thanks in advance, Jack.
Anyone please?
Check out the wiki for Tytn upgrade problems
I also had this problem, upgrade stopped at 1%....Left it for an hour and no progress. Had to stop update, which then left me at the boot loader screen (tri-color) screen. Tried Hard reset as mentioned above, no luck, still stuck in boot loader, tried to reload rom..got error 262 upgrade error
I had just run the unlocker and set device to super CID, and thought maybe that was my problem, but it wasn't
Luckily the wiki had the answer
Problem 4: Device is stuck in bootloader mode (tri-color screen)
>Disable ActiveSync: connections -- settings -- uncheck "Allow USB Connections"
Remove the battery, put it back in, connect the USB cable, power on the unit (this should allow the USB port to be opened again)
Wait a minute or two, if you get a message that device cannot be recognized just close and ignore it
Open
mtty.exe and select "USB" from the dialog box, then hit Ok.
You should see a white screen, hit enter and you should see a prompt like this: "USB>"
Type set 14 0 (do not copy and paste!!!) and hit enter
Soft reset with stylus
OS ROM and radio version should be back and OS functional, the unit isn't a BRICK anymore!
I had to reload the rom. step 8 did nothing, but return me to bootloader. This time the rom upgrade took about 45 minutes to complete. Weird, but it worked...This is first time in at least 4 rom upgrades with this device and at least 50 other rom upgrades that I ever encountered any issues.
POF...Thanks for the great wiki
http://wiki.xda-developers.com/index...ame=HTC_Hermes
Unfortunately, when it hanged on 1% connection was totally lost. Everytime I tried to run rom upgrade/unlocker/spl downgrader is said no connection. Now I don't have bootloader screen, only flashing LCD & camera diode. Any suggestions?
If you can't get the bootloader running then a service center will be the only solution I think.
Has anybody found the solution to this problem, my phone is doing the same thing. Can't get it into bootloader and screen & camera flash just blinks? I tried everything but to no avail.
Hi mate, have you done anything special or it goes bricked "without help"? I I still haven't put it to RMA because there's no T-Mobile in Republic of Ireland and I'm 2 lazy to go to Belfast
jackass_ass said:
Hi mate, have you done anything special or it goes bricked "without help"? I I still haven't put it to RMA because there's no T-Mobile in Republic of Ireland and I'm 2 lazy to go to Belfast
Click to expand...
Click to collapse
It's bricked trying to update it!!! If i could just get it to the bootloader, i can probably revive it but can't do anything. Can't access USB or nothing, I'll guess I'll send it off to a repair center.
Are there any good repair centers in the US???
I managed to upgrade my phone to aku 3.3 using pof's method(bootloader 1.01 MFG) . Then, out of no where, I tried to use MTTY to upgrade my radio rom
It started as usual with the status bar moving. Suddenly some error messages came up.
Now, the phone is dead completely. I can''t even enter bootloader mode.
Is there a possible way that I can still save it??
Help!!!!
Have I bricked my device? Help plz
I managed to upgrade my phone to aku 3.3 using pof's method(bootloader 1.01 MFG) . Then, out of no where, I tried to use MTTY to upgrade my radio rom
It started as usual with the status bar moving. Suddenly some error messages came up. Can't remember exactly, but like some address can't find error.
Now, the phone is dead completely. I can''t even enter bootloader mode. Only when I take out the battery and plug in the charger cable the red light comes on. I looked the upgrade problem page, my symptom doesn't match any.
Is there a possible way that I can still save it??
Help!!!!
I had something similiar happen a little while back. What I did was pull the battery out and leave it out for a while, maybe a few minutes. I then put the battery back in and held the two side buttons and hit the reset button to put me into bootloader mode. I then cabled it to my computer and flashed a new OS via mutty. That got my phone back and operational.
@float. Nuh, it didn't work on my brick. Prob i will have to take it back to Tmobile if they kind enough to repair the no warranty phone i bought on ebay.
Sorry to have opened a new thread, I was so desperate.
Plz delelte it.
how exactly did you try to update the radio using mtty?
I download the 1.27 shipped radio rom. P.S. It seemed to be a german version, not sure whether that caused the disaster.
Using NBHextract to get the single GSM.NB file, then in MTTY, typed
USB> task 32
USB> lnb GSM.NB
Before flashing, just had it upgraded to the HTC AKU3.3 OS rom only. The old version radio rom version before flashing was 1.18.
Maybe the order i flash is wrong. I flashed OS first then the radio rom.
just guessing
ok, you loaded the radio rom code where os.nb should go. That may have caused mega bad blocks in flash. Can you even get bootloader mode if you reset using Wiki directions to obtain Tri-color bootloader?
Yes. I have tried many ways wiki suggests. Such as removing the battery leaving it more than half an hour and plugging it to the usb cable without battery. still can't get to the tri-color bootloader mode. Basically, I just can't turn on the phone.
If you connect it to the computer, can it communicate w/the PC? If you hear the windows tones try opening up mtty and see if you can communicate.
i'm stuck in the same place
for me it happened during extrom flash
Try removing the battery for a bit (a few minutes, maybe half an hour). Then, put the battery back in but don't plug the usb cable in. After that, hold the two side buttons as if you're trying to get it to go into the bootloader. Hit the reset button a few times with your stylus and see if that gets you to the bootloader. That's what worked for me.
tried that
tried removing battery and connecting usb
nothing helps
is there a place that fixes tytn in belgium ?
is there a way to flash a new rom via mutty ?
cause i still have the boot loader, but the phone still in the splash screen
when i type info 2 in the mutty command prompt i get this answer
Cmd>info 2
HTCSQTEK_203”µ·êHTCE
i think it's not realy normal
diffda said:
is there a way to flash a new rom via mutty ?
cause i still have the boot loader, but the phone still in the splash screen
when i type info 2 in the mutty command prompt i get this answer
Cmd>info 2
HTCSQTEK_203”µ·êHTCE
i think it's not realy normal
Click to expand...
Click to collapse
well your not supercid... your still locked to qtek
Look here and unlock your phone before doing any flashing!
http://forum.xda-developers.com/showthread.php?t=295751
to late i ve done that tow day's ago , now the only way to make my phone back to life, PB + KITL method i think
god bless KITL
Hey everyone,
i am so upset and lost; words cannot describe it.
So i installed WM6 black shadow and everything was working except for SMS and MMS. So i am like ok i can live with that for a day till custel' rom will come out. SO i decided to upgrade the radio to 1.43 and boom here is where the problem started, No GSM on boot up. Phone doesn't boot up. I tried install 1.40 over again, still nothing. No i tried upgrade the the rom itself, i tired custel 2.5 and nothing and i tried the new Cingular rom, still same problem. the roms flash all the way. I read the wiki, and saw the mtty.exe thing but that doesn't work for me either. I am really lost and don't know what to do.
Specs
cingular 8525
hardspl v7 cid and sim unlocked.
PLEASE HELP
4.13?? 4.10??
Where did you download these radios from??
or do you mean 1.41 or 1.43??
Yeah thats what i meant, 1.40 and 1.43 sorry. You can see how upset i am.
Thanks Again
Well, if your phone turnes on .. it's not a brick.. lol .. it IS fixable... When you turn the phone on does it go RIGHT to the 3 colored screen?
@dan5.5
You need to read the unbricking thread about this, all the info you need is there.
http://forum.xda-developers.com/showthread.php?t=286755
If you are superCID I don't see how flashing a radio could have messed up your phone.. that's weird.
mrvanx said:
@dan5.5
You need to read the unbricking thread about this, all the info you need is there.
http://forum.xda-developers.com/showthread.php?t=286755
Click to expand...
Click to collapse
I read everything there and nothing seems to be working for me. I woudnt post for nothing. i dont want to be annoying.
OK im going to repost what ive said on 4wm:
We need to check if your Radio BL is functional, firstly leave HardSPL v7 on there and connect to the bootloader via mtty (il assume you know how to do this).
Issue the following commands and tell us the results please:
1) checkimage (this shows the CRC checksums of each component...id expect the radio image to show a timeout....
2) info 2 (This will verify that your CID is intact)
3) info 8 (does a bad block check)
Once youve done this, flash SPL 1.10.oli to the device and once again connect up to mtty.
4) 'rtask a' this will enter the radio bootloader you will see "Enter Radio Bootloader" or something to that effect
from now on when you type the text does NOT appear on the mtty screen.
5) 'rversion' this should return your radio bootloader version...now unfortunatly if you see nothing...you radio BL is dead and sorry your device is royally bricked. If you get something returned back onto the screen (most probably containing the text '0108') then your radio BL is fine.
Click to expand...
Click to collapse
do as instructed in that text, post your results here.
I cant falsh spl 1.10 oli. it gives me the 260 error.
the 260 error is not connected via USB right? .. weird... have you tried taking your battery out for a couple minutes, then booting into BL mode? sounds weird but this worked for me when I didnt flash hardSPL firsl..
hey mrvanx's
I can't downgrade the hardspl to 1.10, anyhelp.
I cant active sync, the phone doesnt boot up.
Is there anyway to aviod having to respond on the phone.
hey,
i can get the phone to boot up into windows and then it freezes within a couple min. what should i do. Still no gsm message and no phone. thanks
Dan
OK, so let's try and get you to a working state - I've bricked mine a couple of times and it can be quite heart-stopping, eh?
The first thing I would do is re-download radio 1.43, just incase your current one is damaged somehow.
Secondly, download Black Shadow - I know it's not the ROM you ultimately want but the aim here is to get you working again and we can move forward from there.
First, boot up into BootLoader mode (hold down the OK button on the left side of the phone and the power button and then press the reset button on the bottom, just in case you didn't know
You should come to the three colour screen and it should be reading IPL-1.04 and SPL-2.10.Olipro. If it isn't, stop here and post what it does say.
If it everything is OK at this point, when you plug your phone into your computer, it should change to USB at the bottom. Just wait for the Found New Hardware prompts to clear on your PC and then flash the black rom - choose the hardspl option in the flash program.
Once that has finished and it is at the "tap screen to set up windows..." bit, put it back into bootloader mode as above and flash the radio.
This should hopefully give you a running phone again as I know this combination works OK as I am currently using it.
Fingers crossed, don't panic, and let us know what the results are
Cheers,
Smiffy.
Nothing is working, can some please help me. Is there anyt way i can restore the spl to the original one so i can send the phone back, i just got it like 2 weeks ago. thanks
Also i have a bad block thats what i think makes the phone freeze after i boot it up.
How can i get around this, thats seems to be the biggest problem.
Hey everyone, let me give you more info.
I can fully flash any rom and and radio,
phone will boot up like 1 out of 10 times and then freezes and thats it.
i have a bad block number 6. I have hard spl v7 installed before the phone got screwed up. I cant downgrader the spl to a lower one to check if radio stack is screwed up. Can someone please help me, if you need to ask me more info feel free.
After I microSD flashed my phone it said "update successful" I followed the directions on the wiki and did a soft reset. The phone returned back to the tri-color bootloader screen. Did I do something wrong or is the phone messed up beyond fixing?
I just flashed it again via microSD and it says:
Update Completed
UPDATE SUCCESS
Now if I try to soft reset it jumps back to the colored screen.
The screen says:
HERMIMG.nbh-ok
IPL-OK
BOOTLOADER-ok
SPLASH1-ok
SPLASH2-ok
EXTROM-ok
GSM-ok
OS-ok
Update Complete
UPDATE SUCCESS
THen after I did a hard reset it went back to the tri-color screen.
after flash just do soft reset. stylus in bottom of phone. Doing a hard reset seems to do BAD things...
reflash to OEM rom..
did you HardSPL? ..
Thanks guys. I did try doing a soft reset, same thing. I dont know if the previous owner did HardSPL. He was a friend of a friend and gave it to me for free. When I got it, it was stuck on the bootloader screen. I asked if he tried to flash it and he said no. My computer doesnt recognize it and my work computer same thing. Could the USB port on the phone be damaged? I flashed it with WM6 off the wiki and PDAcorner. Same thing. Loaded then after I soft reset it goes to bootloader screen.
mark1914 said:
Thanks guys. I did try doing a soft reset, same thing. I dont know if the previous owner did HardSPL. He was a friend of a friend and gave it to me for free. When I got it, it was stuck on the bootloader screen. I asked if he tried to flash it and he said no. My computer doesnt recognize it and my work computer same thing. Could the USB port on the phone be damaged? I flashed it with WM6 off the wiki and PDAcorner. Same thing. Loaded then after I soft reset it goes to bootloader screen.
Click to expand...
Click to collapse
Have you tried flashing a shipped rom with USB while on bootloader screen, plug in to PC and just run the exe file? report back? Check your serial against here for known problems.
Neither my home computer or work computer detects the phone when I plug it into a USB port. I have tried a 3 different cords and it still doesnt show up as a device.
Whats the SPL on bootloader screen. If its 2.10 olipro it has hard SPL installed...
ultramag69 said:
Whats the SPL on bootloader screen. If its 2.10 olipro it has hard SPL installed...
Click to expand...
Click to collapse
Ooops I didnt mean to make 2 threads about the same problem. Yeah it says 2.10 olipro but still jumps back to bootloader screen after a flash.
zocster said:
Have you tried flashing a shipped rom with USB while on bootloader screen, plug in to PC and just run the exe file? report back? Check your serial against here for known problems.
Click to expand...
Click to collapse
Checked my serial number (HT652) and there's no known problems on the wiki for this model. Tried to plug it into the PC but it cant connect. Tried two different PCs and updated Activesynch. Nothing. I am beginning to think that this phone is just dead period or the previous owner dropped it and messed it up.
UPDATE:
I flashed a shipped ROM from the wiki and it did the same thing. Loaded, said it was updated and when I did a soft reset it popped back to the bootloader screen. Should I let the battery drain and try again tomorrow?
No need to let the battery drain, take the battery out for about 20 seconds and put it back in, then turn the device back on. I had this problem once and that solved it. If your device can't connect to the computer you may have to flash via storage card.
I tried flashing it a few times with a storage card. It loads then after a soft reset goes back to bootloader screen.
Just to double check, under the battery should be a sticker with some info on it.
Should be imei and voltage etc... Does it have anywhere herm***? The *'s are for a number - 100,200 or 300. If it doesn't say herm*** then you are on the wrong forum. There are so many different names for the Hermes that I thought it may be an idea to check as flashing the wrong SPL will DEFINATELY brick your device and it seems to have been Hard SPLed. The os should be flashed fine but as MrVanx says you may have some bad blocks if you are sure you have a hermes.
Cheers...
ultramag69 said:
Just to double check, under the battery should be a sticker with some info on it.
Should be imei and voltage etc... Does it have anywhere herm***? The *'s are for a number - 100,200 or 300. If it doesn't say herm*** then you are on the wrong forum. There are so many different names for the Hermes that I thought it may be an idea to check as flashing the wrong SPL will DEFINATELY brick your device and it seems to have been Hard SPLed. The os should be flashed fine but as MrVanx says you may have some bad blocks if you are sure you have a hermes.
Cheers...
Click to expand...
Click to collapse
Yes it says HERM100. Also, the person that gave it to me said he might have been pushing the power button while he was putting the battery in. Would that brick it? Another thing, does the battery every run out? I left it on bootloader all night and its still on!
This isnt my exact phone but this is what my screen looks like and what it says.