Develop Bugs

My universal is a brick!

Hello everyone, my first experience of upgrading the firmware is sadly failed and now my beloved m5000 is only a beautiful paperweight!!!
No key combination could start the bootloader nor soft or hard reset works.
When I connect it to mains charger, the right led goes red for few seconds and then goes off...
In the service manual I have read that this signal means hardware failure but because the fault is the consequence of a failed upgrade I don't thing that it is really broken.
I already tried to contact htc and orange for repairing but in Italy where I live it seems that the warranty isn't valid and services are very scarce.
Someone have an hint?
Thanks.

Try to do a hard reset, many manage to get that white screen.

Thank you for the suggestion but it doesn't work The phone is completely dead, except for the red led. Any key combination including hard reset simply doesn't work.
I suspect that the only way to resurrect it is to reflash using a jtag interface.
But unluckily I don't own the pinout!!!

take a look here: http://wiki.xda-developers.com/index.php?pagename=Instructions for those stuck on Boot Screen for instructions on how to use the mtty utility to bring your device "back to life"
There's additional information on the mtty utility in this thread: http://forum.xda-developers.com/showthread.php?t=259003
hope this helps

If you are on the bootloader menu...
Try to flash again a complete rom + extended rom + Radio
SOmetimes it can work again

sigh... thanks to everyone but I can't reach the bootloader menu: the uni is bricked!
My only hope is to find the jtag pinout...

Try holding down Light + power for at least 5sec. and while still pressing, do a soft reset.
If you dont go to BootLoader then try to increase the Hold down Light + Power some more.
This worked for me, could again get it active on usb and ran my original rom upgrade while it was in BootLoader mode.
If that dossent work, try the bootloader upgrade version at
http://wiki.xda-developers.com/inde...tion On How To Upgrade with Bootloader method
You can do the same with the two - - buttons, holding for more than 5sec. then soft reset. Should bring up the Reset with 0 or X to cancel.
But it just reverted to a brick every time for me with this.

BTW. do this with USB or Power Cable plugged in!!

another possibility is that your battery is low enough not to allow booting but is still able to light up the LED. it happened to me a few times that i was thinking it was completely gone and it was just low bat. remember that if you have a non booting device it may not even charge the battery anymore so you'd better ask a friend to lend you a charged one, just to be sure.
cheers!

Ill Buy The Brick!
au$200.00 in your paypal account upon a sale +50 to Australia.
Let me know...
Simon

Still Charging
I have 2 wizards and a universal... By mistake, i have tried to upgrade the G3 wizard but pluged the G4!!!!!...... So now i have abricked G4 wizard. Now when i plug the G4 it does NOTHING, it is completly dead, BUT is still charging the Battery!!!! I am sure of this because i have tested the battery in the other device.. So try the same on universal plug it in and wait a few hours it may charge the battery.

anyway, if you can't unbrick it, do me me know if u're selling it.
need some spare parts.

Suggestion
What you can also try is remove Activesync from your desktop, Restart your desktop, install Activesync again and connect your device.
It's word a try! Has something to with rapi.dll!
Cheers...
Leo

My failure...
Hello everyone, I've tried all yours suggestion one by one and step by step but without success.
My last chance to not consider this phone a complete loss is to sell it as spares/repair...
Does someone is interested?
P.S.: notwithstanding the phone is bricked it still charge the battery

Try holding the the two - softkeyes for longer/shorter time before you softreset while still holding them down.
Also try different intervals with the softbuttons while holding the Power + Light down, also with soft+Light & soft+power & power+light
all with different intervals.
Look closely at the screen after each try, to se if it goes to bootloader mode.
And remove SD card and Sim also.

I Hate Bootloader!
I have tried ALL of these power+light+reset suggestions and I STILL can't get into the damn bootloader menu! I just gave up and rip apart my JasJar every time I want to update it. For some reason the only way I can access this menu is by pulling the main battery and disconnecting the smaller(watch battery) one in the upper right hand corner and letting it sit for a couple of hours.
Come to think of it, when I use even the factory updates I don't even get a report on the update screen telling me what my current config is! So then I hit update anyway, the unit turns off, I lose my USB connection, it no longer charges, and I have to take the battery out. Almost like the PROGRAM can't even get it into the loader! This is probably how I learned to just yank the batteries when I want to upload.
Unless there is something different because I have an earlier model... I have no clue. Does the unit need to be running or something when I do this? I think this is a fairly elementary task but it just doesn't work. Has this happened to anyone else?
Yes, all my buttons are in working order = )
BTW after my last tear-down I have -
Bootloader: 1.01
Rom version: Ivan-2.60.00WWE
Rom date: 12/20/06
Radio version:1.14.00
ExtRom version: Modified

http://forum.xda-developers.com/showthread.php?t=247440&page=14 I think someone already suggested this, but just in case...

No chances
Well, today I've verified my battery and it works like a charm in the uni of a friend. Then the last possibility is gone.
Someone knows how to go ahead any further?

Help!! just got an Xda IIs - seems locked up

Hi all, I have just got a Blue Angel Xda which is in mint condition but when powered up hangs with an unlit screen showing the O2 logo and some faint red writing near the bottom right of the screen which I cant read. It does nothing from this point.
I have tried pressing the key combination to enter bootloader mode and this appears to work with a blank white screen saying 'serial' and a version number - but what to do from there?
Can I reflash the software? does this problem sound easy to fix or is it destined for the bin? I have the docking cradle and some software with it - I would like to unlock it if possible but since I cannot access the PDA I cannot copy the unlock file to it.
Any help would be very appreciated - what software do I need to get it working again if I can?
Thanks in advance.

oh dear I was hoping I would be told it was simple matter by now - anyway in the mean time I have tried to get the phone to connect to active sync but it will not. I have put it in boot loader mode and it says serial on the screen which changes to USB when put in the cradle - still will not connect to active sync. I can in fact read the red writing on the screen which I said I couldn't above - it seems to be various version numbers of something.
I am using XP with the latest version of active sync for XP downloaded from MS yesterday.
All I want to do is reflash this XDA - I was told it was a simple thing but so far have had no luck even connecting to it.

Hi.
Try to do a hard reset first. You can learn how by reading the following:
http://wiki.xda-developers.com/index.php?pagename=BlueAngel_WM5_For_Beginners

No luck
Thanks for that but I never see the coloured stripes - maybe its not WM5? I can clearly enter boot mode according to that guide but otherwise just have a stuck unlit O2 loading screen. The soft reset only seems to cause a momentary blanking of the screen and then back to the same O2 logo. I have tried pressing the camera and record buttons a thousand times whilst pressing soft reset but nothing different ever happens.
isn't there a way to just reflash the rom?

Yes...of course you can reflash.
Download the rom from the following thread:
http://forum.xda-developers.com/showthread.php?t=382909
Enter bootloader mode, connect your Blue Angel to the cradle and run MaUpgradeUt_noID.exe.
When the flashing is complete...hard reset your device.

Wow - thanks so much you are a genius - I followed the instructions with relative ease and my Xda lives again - I need to play on a bit with it now to learn how to use it but thanks a million.

Everything seems to be OK - WiFi seems a bit flakey with connecting but once connected behaves well - biggest annoyance by far is the fact that there is no sound at all, no matter what the format and volume the xda is mute!

Heh..you're welcome.
The 'no sound' issue could be a hardware problem. If you are sure that the software is ok and you should hear sound then the best scenario would be a replacement speaker.
I have just replaced my speaker with a spare from a qtek s200 and it's great.
BA is a great device

I am not sure the software is OK - the PDA is in mint condition it seems highly unlikely that the sound is faulty - its totally silent - wma makes no sound at all.
I wonder if there is a factory rom I could try just to be sure if its the software or hardware - I have followed links to various 'ship' roms and they seem to be dead now.
I plugged headphones in and they too are dead so it it probably isn't the speaker?
Also the camera button starts media player not the camera and I dont appear to have any access to camera functions - I think this could be a software thing perhaps a less ambitious version of WM.
As a beginner in this forum its really hard to find any actual files - there is much talk about this rom and that but where are they kept?
surely there is a stock rom that can try to be sure the hardware is ok?

Hmm..
Try this wm2003 rom(run MaUpgradeUt_noID.exe):
http://rapidshare.com/files/111121136/BA_O2UK_14000_237_11200_ShipXdaIIs.rar
Are you sure that there's a camera on your BA? Because some BA come without a camera.

Thing is when I try the stock rom I end up exactly where I started with it frozen on the boot screen - it just wont seem to allow me to do a hard reset - I reflashed the 6.11 and works fine but again no sound and the camera says it cant initialise the hardware (definately has one)
I even flashed a T Mobile stock rom and it froze exaclt y the same as the O2 rom on the boot screen and wont respond to the hard reset buttons.
When i flash the WM6.11 the hard reset works just as it should so I conclude from this that the buttons are OK
I am at a loss as to what is going on - right now I am back to 6.11 but no sound and no camera again but I cant see me living with it like this

Busted Standby button

hi everyone
ive seen quite a few busted/malfunctioning standby button posts but none have had any proper answer other than to open the device and clear the dust.
ive done exactly that- opened up the device, blew off all the dust. but no help.
on closer inspection i realised that the legs of the standby button had actually come OFF the circuit board.
now..i could probably take it into a mobile shop and have it fixed. but i wonder if there is any software out there that could possibly simulate a Standby Button press?
this would be especially useful for flashing ROMs..

i am sorry but i can't figure out, how it should work. if it was some sort of cab and you "pressed standby" once, how would you wake up the device, you can test that with pshutxp. plus, the program would of course not be accessable when turned of or for reset. when reflashing the device, the prog would be gone anyway. if there was a remote program to control via pc, same thing, when your device is in standby, there is no pc connection, and again, no way to do it, while not being sync with AS. so the only actual access to that function is the hardware button itself, so instead of trying to substitute it, you should probably go get it fixed or order spare parts, or an entirely new device, which is probably the cheapest.
greetz
Chef_Tony

thanks for the reply
well i just need to press it once :S
to flash a new ROM
after that i can then reinstall the app (if it exists) to do any hard resets thereafter i guess......

zes, and that is the problem, in that situation, trying to start the bootloader, and also after flashing for the hard reset, you don't have any external access to the functions or to any programs on your device (since at that moment there are none, quite redundant). the one and only option to give the device the power buttons impulse, is the power button.
also i guess you're aware of the fact that upgrading your rom does not solve nor avoid your problem, you will still have no key lock, drain incredibly much standby time and once the device shuts off, you need to soft reset it to restart. if the button in physically broken, it needs to be physically repaired or your problem will not be solved.
http://mikechannon.net/PDF Manuals/HTC Blue Angel Service Manual.pdf
that is the ba's service manual, in which you can find the exact process on how to change the power button, and if you don't have spare parts, you could get inspired on how to substitute one...
also, maybe posting a photo of the damage to your button could make people who went through the same be able to advise you exactly, since all my experience in the hardware section of the ba is purely theretical.
greetz
Chef_Tony

hi tony
thanks.
after the flash i can still access the clear reg hive thing by holding record and cam button..
that should be all i need.
as for waking the phone, i can set it not to disable other buttons while on standby, so i can wake it with Call/End buttons.
and then with that, i can use s2cu to software lock the device to avoid accidental presses.
but you're right, nothing better than getting it fixed physically.
i GUESS itll just require resoldering the little switch back on, as the damage is that 2 of its pins have left the circuitboard. i dont have the tools to do a small and precise soldering job so..
ill try to take a pic too and post one later

well i dug deeper...
seems that there is a 'Enterbl.exe' thats supposed to be related to enterin the bootloader without having to do all the hardware keypresses.
I've not yet had luck with this...dont know which 'version' i need..
so perhaps to rephrase my question:
is there an alternative way to enter the bootloader mode on the blue angel?
similar to the Wizard Service Tool (which i also tried out of desperation, though all it does is blink the BA's screen)

Anyone afraid of NAND flashing is a wuss. Check this out, its so easy..

These Instructions are out of date, and may not work anymore.
-CarComp
EDIT POST ON 5-5-2010
INSTRUCTIONS ARE IN BOLD!!!!!!!
EDITS AND MY OPINIONS ARE IN ITALICS
Want google and not winmo but can't wade through all of the confusion offered up by the supergeeks of android linux? Well just do these steps. It took me an evening to figure out these steps, and could whip it up instantly now.
BTW - it REALLY helps to have a computer with an SDcard slot adapter that handles the micro-sd cards. I don't really recommend trying all this with a USB cable, b/c once you get to linux only, you will kinda be screwed cause it doesn't quite work the same like windows CE. Also that and you can't format through the phone, so just get an adapter ok? Stop right here if you don't have one and just order one or go to walmart and spend 10 bucks and get one. BTW, your micro sd card should have come with one when you bought it, so go look for it.
Ok how to get the super Eclair android into NAND and live a happy life....
1, CHARGE YOUR PHONE UP ALL THE WAY BEFORE ANYTHING. When done charging, unplug whatever is in your USB port for the rest of this procedure. Having phone plugged in while flashing = BAD
2, get hard spl on your phone.
3, Install Hyperdragon IOlite on your phone to get the radio(1.65.24.36) that I recommend, which will improve battery life and possibly other things that I don't know about. Get it here -> http://sakajati.com/blogs/2009/02/hyperdragon-iv-iolite-based-on-htc-iolite/
4, format your 1+ GB sdcard using fat32 only.
5, download polyrhythmics dark / light build for nand and sdcard.
put that SINGLE FILE (androidinstall.tgz) into a folder in the root of the SD-CARD called "andboot" - Get it here -> http://forum.xda-developers.com/showthread.php?t=600154
6, go to http://sourceforge.net/projects/androidhtc/files/ and download KAISIMG-PANEL2-320-TILT.NBH if you have an ATT tilt. If you have something else, download that NBH.
7, Rename that NBH file to "KAISimg.nbh". Put it in the root of your storage card.
8. Now you are ready to install to nand. Get out your stylus, hold down the camera and power button and press the reset button with the stylus. It should go to an updating screen. If you don't get a white screen with a progress bar, but instead it still shows tri color and says "serial" then you did something wrong. Start over from step 1. Once you get to 100%, wait 20 seconds or something (just for shihtz and giggles) and then pull out the battery.
9. Now, put it back in, press power and wait for android to start booting. You will know cause all this random looking text will go by. You have to be quick to do it, but press the middle button on the d-pad when it says 'press the middle button to enter setup' or soemthing like that. (EDIT: I've been told that you have to just hold the d-pad center button down. Either way, just get that button pushed when it says to push it).
You will be presented with some options. Make sure the little asterisk is on the "NAND" option.
10. Go to the install (first option) and tell it to overwrite everything. It may ask you twice.
Now it should go into a fix of text and waiting and hanging, but be patient. You should eventually see a colorful "X" for about 10 minutes. Go to eat, have a beer, leave the house for awhile. Go mow the yard. Just don't use the phone. When you come back, go through the inital setup (touch the android, and skip everything else. Don't set up anything.) Now go mow the yard again. After about 5-10 minutes goes by, come back and pull out the battery. Put it back in and push power.
Crap your pants at the speed NAND offers. Install some live desktops (I like the starfield warp drive one from the google market.)
BTW: If you mess up your phone doing this, blah blah its not my fault blah blah you probably shouldn't be on these forums etc. Just make sure you have HardSPL and you will be fine. I've flashed hundreds of roms hundreds of times. Just that one little step will make your life easier.
EDIT:
RADIO DETAILS:
I've heard a LOT about using the latest radio or whatever version 1.71 or soemthing. I run radio 1.65 just fine. I never upgraded it through out all of the android builds. I operate like this.. If you weren't having cell quality issues, GPS lock issues, or any other radio issues in WINMO, then android will be fine too. I've added a step to the process to install a specific winMO rom that has the radio that I use. If you don't like the fact that I'm telling people to use an older radio, so be it. I'm just spreading the word for what works REALLY well for me.
EDIT: (My thoughts on the panel 1 2 3 and the 320 or 428 or whatever...) Picking the right panel is like playing the 'cups and ball' game. if you know which one the ball is under, you will win. Well for you TILT users, the ball is under #2. I don't know why, but it is. If 2 doesn't work, use 1. Doesn't get simpler than that. As for the resolutions, just use the 320. Ya, some apps fit better on the higher res, but our screens don't support them really well, and its all blurry. Think of it like this..... using 4xx instead of 320 is like asking 3 pixels to display as 1, vs. one pixel displaying as one pixel very clearly. Polyrhymic has done a great job supporting our screen's native 320 size, so just use it.
EDIT: (An issue i've noticed with booting and having your phone plugged in). Android just won't do it on nand. You can charge your phone from a dead point for say 20 mins, unplug it, then turn it on, boot android then plug it back in. You can't plug it in, and turn it on. It gets stuck in some sort of USB status loop.
EDIT: (When your phone just sits there on the A N D R O I D text and won't boot). Seems like this has been happening a lot, for me too. I've found there are two ways to stop this, one is preventative... Don't let your phone go totally dead. The second, when you reboot your phone, press and hold dpad center, then just count to 10 and go to the QUIT option. 9 times out of 10 it will boot right up.
IF YOU HAVE ANY PROBLEMS, JUST REPEAT THE PROCESS.. Don't skip the full charge and installation of Hyperdragon first.

for may people on here, the fear of flashing isn't the problem. it's the missing features such as bluetooth, speakerphone and in some builds even camera.
I would LOVE to go nand. I hate not knowing if the problem is with the build or with the sucky sdcard.
but I need to revert back to winmo for bluetooth headset. once that or speakerphone works I am ON IT.

Nice, couldn't have said it better myself, a few small points, press and HOLD the centre button on Dpad, a quick press will not do it, I'd mention the radio version too, but those are not major issues, and can be sorted easily enough
Good advice about the card reader and adaptor, those two saved my ass a few times in the early days of Nand flashing, I keep a good stock winmo kaisimg.nbh on a spare SD card, you only need a 128Mb one for a stock rom.
Yes there are install instructions on the build posts, but a lot of the info is now spread though some 2000+ posts, so having it all in easy terms helps a load.

I have a question. What is the different those PANEL1, PANEL2 and PANEL3? And the following number 320 - 428 - 480?
And one more silly question, is Tilt the one without 3G camera?
Thx for the instruction, it is easy to understand and so helpful!

added info about panel stuff to the instructions

It is not a fear of flashing in NAND It is just the issue that not all the features works...CAMERA,Bluetooth, voicesearch, so when the features will work than probably everybody will change I know i will ))

my problem is, that i cant get to boot the android for the second time. it just hangs in first screen after booting and thats it...
tried to pull out the battery for 10minutes and still nothing...

Disturbed21 said:
It is not a fear of flashing in NAND It is just the issue that not all the features works...CAMERA,Bluetooth, voicesearch, so when the features will work than probably everybody will change I know i will ))
Click to expand...
Click to collapse
agreed, currently no gps working map that can be rely such as garmin that can work on winmo.. 1 disadvantage of android.. need to be online to get route..

Kurt Cobain said:
I have a question. What is the different those PANEL1, PANEL2 and PANEL3? And the following number 320 - 428 - 480?
And one more silly question, is Tilt the one without 3G camera?
Thx for the instruction, it is easy to understand and so helpful!
Click to expand...
Click to collapse
320-428-480 là chỉ độ phân giải đó bạn.
320 is a resolution of 240X320 and the 480 is a resolution of 320X480
Mình biết được chừng đó thôi

Created another edit to the 1st post.
I'm not saying that android doesn't have its shortcomings, I'm just offering a quick means to get to NAND without trying to comprehend the whole thing in the traditional sense of reading 200 threads.
BTW my radio is 1.65.24.36
Maranevin, try flashing Hyperdragon IOlite first. Maybe a radio switch will prod your phone into the correct direction.

Errr, for newbs who don't know how to properly unlock their device isn't this dangerous? There IS a possibility of bricking your phone if you don't know what you're doing -- right?
Anyway, I would also mention that if you or your phone can't do 3G don't flash to NAND yet. The radio can't be instructed to use GSM only with the current poly build (and any other I have tried so far)

I totally agree with mnjm9b, the problem is not flash the phone, the problem is that there are many things that do not. In particular I am very happy with the performance of 2.1g polymod to date is the best I've worked.
carcomp thanks for the help, very good summary.

aikeru, if someone is flashing a phone, they probably know the risks. Its not my fault if they do something stupid. Is it autozone's fault if I buy specialty tools and ruin my engine changing a timing chain?
Anyways, I don't get the 3g thing. We have hardly any 2g or whatever is below 3g here in Mulberry Indiana and my android works fine.
Like I said, maybe i've found that magic mix of things that works really darn good.
BTW: major argument for using android.....
First of all, i'm not borg. I have yet to really get into bluetooth. I own two earpieces and the only good thing i've found is you can talk on the phone in freezing weather with you hands in your pockets. Bluetooth to mute car radios is cool, but I have a 20 year old car. I don't need bluetooth for file transfer cause i've got wifi, and SD CARD.
Second, as for the speakerphone, it never really was that loud anyways. I came from a hermes, which has a speaker like the voice of god, so i've never been impressed with the kaiser speakerphone.
Third, the camera... I have a nikon D60 with a speedlight for taking stills and lowlights, and a Kodak Z612 in my wife's purse most all the time for the past 3 years for video and spot shooting. All this data easily goes onto the micro sd card and into the phone.....

carcomp said:
10. Go to the install (first option) and tell it to overwrite everything. It may ask you twice.
Now it should go into a fix of text and waiting and hanging, but be patient. You should eventually see a colorful "X" for about 10 minutes. Go to eat, have a beer, leave the house for awhile. Go mow the yard. Just don't use the phone. When you come back, go through the inital setup (touch the android, and skip everything else. Don't set up anything.) Now go mow the yard again. After about 5-10 minutes goes by, come back and pull out the battery. Put it back in and push power.[/B]
Click to expand...
Click to collapse
I've done all step above, just when i did this After about 5-10 minutes goes by, come back and pull out the battery. Put it back in and push power. it started back to Step 9 when i had to 'press the middle button to enter setup'.
So, i skipped that step, and then later everytime i tried to press reset button, the phone is freeze, then i had to started over again...
In some cases, my OK button became to POWER button...
And at first time, WIFI was OK, then it showed Unable to start Wi-Fi
Any suggestion for my troubles?
Thank you!!

Great!!
Hi all, Great!! I am now running Android on my kaiser and I love it!!!
Just a couple of questions for people who can answer them:
- How to change phisycal keyboard layout? I mean, some keys that I have in blue aren't the same I have on my keyboard...
- Is there any means to connect to a pc to transfer contacts and files?
Thank you all!!
Gnatto

Maranevim said:
my problem is, that i cant get to boot the android for the second time. it just hangs in first screen after booting and thats it...
tried to pull out the battery for 10minutes and still nothing...
Click to expand...
Click to collapse
Same problem here. Someone please help. My device is now a worthless brick!!!!

Ok when this happens (its happened to me), first of all don't panick. If you've installed hardspl you are protected, and besides, just cause your phone won't boot android doesn't mean its bricked, it just means its not booting android.
There can be a multitude of things causing this, but the #1 reason I think is "Just because thats how it is"
First of all, don't boot your phone with it plugged in. Ever. Charge it first, then boot it, or charge it enough to make it through boot then plug it in when it reaches android.
Second, sometimes during boot, it just hangs where it says A N D R O I D, or some other text. You can get around this by resetting with stylus, then pressing the center dpad button, then just counting to 10 or 20 or some random number that makes you happy, then select quit. It should boot.

Thanks. Fortunately I unbricked it by putting the KAISDIAG.NBH file onto the SD card, then booted it. This unbricked it. I also put the the KAISIMG.NBH for the Android on here and it booted into the installer. My problem now is that when I click install to NAND, it says it has an error extracting from the SD card for the android installer. It then quits back to the main install screen. I think it is a permissions error since it says on the screen something about being read only. If anyone could help me, I would greatly appreciate it. Thanks.
Oh and btw, I never had usb plugged in since mine is broken.

Ok well you are on the right track. Before you do anything else though, flash a copy of windows Mobile. Either take your pick, or use hyperdragon. Its very complete ... radio / ext rom etc. Next, try reformatting your SD card using windows. Do a complete format, not a quick one. That might help. Now reflash using the link to kaisnbh that i posted.
Remember, installing windows mobile is your NAND reset. Its lot like an sdcard where you can just erase everything. You have to put something else there that is radically different. I may be wrong about this, but it seems to be the case more often than not.
You may be one of the special case people who have a weird phone that takes one of the other KAISimg.nbh files too, so don't discount that. Also since you have hardspl, and you are flashing from the sdcard, you phone is probably NOT going to brick, and even if it does screw up royally, if you can still get to tri color, you can fix it.

Ok. That's great to know. I'll try what you stated. Do I need to partition my SD card? Thanks again. I really appreciate the help.

ATT Tilt 2 went to red, green, blue, white screen; how can I flash a cooked Rom to it

Hi,
Right in the middle of use, my ATT Tilt 2 went to a basic, dead screen with red, green, blue, and white bars that says Rhod300 32m SS-BC, etc.
The operating system seems have gone down--it won't respond to anything. Hard reset produces the same results.
Can I flash a cooked or official Rom back onto this? I think activesynch is needed for a normal flash and of course I can't use active synch with the phone in this condition.
I think probably what I need is an original ROM install. Is this possible with a normal Windows 7 PC and a dead phone?
I have so many Windows Mobile programs and peripherals that I am trying to avoid going to Windows Phone at all costs--at least until they have basic stuff like file systems, a way to port over notes, etc. Also need a hard keyboard.
Right now using an older Fuze, which works, but is slower, worse screen, smaller, and lacks some of the features I like.
Thanks for your help.

You sound like you're in the bootloader mode. Tri-color screen.
You can flash from USB or from SD at that screen. I'd recommend trying to flash a stock ROM - as it flashes everything. Assuming that works, hopefully you can flash back whatever ROM you were on.
The phone isn't dead if you're at the tri-color screen. It should say 'serial' at the bottom - when you plug in your USB cable, it should say 'USB' and install some drivers. Then with the RUU software that comes with every ROM, you should be able to flash it.

Phone won't reboot--stuck on tricolored boot screen
Hi,
Thanks so much for replying. I appreciate you pros helping us novices.
Just after I posted the first note, I pulled the battery and hit the power button, it rebooted, and everything was still there in the OS--working fine. But whenever the device had to be rebooted, I would have the same problem of it getting stuck in the boot screen. After that, for the last several days once in awhile, randomly, it would finally reboot from the boot screen after I pulled the battery and hit the power button. The rest of the time (about 5/1) it would just sit there in the boot screen no matter what I did. The "Serial"/"USB" thing would change when I plugged it in, but that's all.
Thought it was the OS, so at a lucky moment where the "pull battery, hit power button" strategy actually worked, I installed the latest official HTC/ATT Rom--it's the next to last one issued that ends in .4.
It was gorgeous and I got all excited--started installing stuff thinking my problem was solved.
Had to reboot to install some programs--now it is stuck again on the boot screen. Tried 30x again--no luck with the "pull battery/hit power button"
strategy. Sometime it would flash a white screen really quickly saying something like "Can't read image!" before going into permanent boot screen. The boot screen will switch from "Serial" to "USB" if you connect it to the computer. So, the problem doesn't seem to be in the OS--rather, in the ability of the device to "read" the OS from the boot screen.
I would be grateful if you or anyone else may know what's going on here, and any ideas on how to fix it. Is there any manual way to get it to read the OS from the boot screen when that's not happening?
I have two guesses (both of which may be wrong):
1. It may be something in the hardware is just worn out and is less and less able to read the Rom--any ROM. I got the phone new off Amazon for a profit of $50 ($.01 cost plus a refund for an older phone) in the summer of 2010 when it was already outdated. and WP was replacing WM. I've certainly gotten my money's worth after 18 months!
Of course we now know that a brand new ROM has the same problem as the older one--which suggests to me it's in the hardware. I'm sure the new OS and the stuff I installed is still there on the phone, but something it appears is not reading something in order to allow the boot up.
2. I have a squirrely free program called Rax Reset (from Windows Mobile Marketplace) that does a software-based hard or soft reboot from inside the OS. The very last time the device went down and didn't come back up, I had used that program to soft reset it. Might have been a big mistake. Could this program be causing the problem? If so, just one reboot would allow me to get rid of it or even hard reset to remove everything but the new OS--but can't get it to boot.
If it turns out the phone is just worn out, I've certainly gotten my money's worth.
I still love WM even with all its problems--and especially the newer Sense version. If this one is shot, I'm thinking about just buying a new Touch Pro2 on Ebay to avoid all of the sacrifices and backwards steps involved with Windows Phone.
Thanks for any help anyone can provide.
Phil Butin

Why are you crossposting? I read this EXACT same post in a thread just below this, in the same section. That's pretty low.. Crossposting across forums isn't welcome, crossposting within forums IN THE SAME SECTION is definitely not welcome.
Don't do it again.

Sorry, just trying to get help
Sorry, just trying to get help, not that familiar with the rules.
I searched on "bootloader" and found a thread (wrote a comment there too), but it's old....
Here is the thread. It doesn't really provide any solution.
HomeArrow
Legacy & Low Activity DevicesArrow
HTC Rhodium: Touch Pro2, Tilt 2Arrow
Touch Pro2, Tilt 2 GeneralArrow
issues with bootloader.

Either way, whether you know the rules or not - why would you think copying and pasting the exact same words in the exact same forum help you any more...
Anyhoo, have you tried the usual? Flash stock? Sometimes I've heard you have to flash several times, I never really understood that logic tho.

I'll try to reinstall the HTC/ATT Sense OS again. I guess you're saying active synch doesn't need to be working in order to do that. I'm at work now--have to wait until i get home. Nothing to lose at this point.
But I'm seriously wondering whether the problem is the OS install or whether there is something in the device that is supposed to read the ROM and start the bootup that is just wearing out.
Thanks.

"No Image File"
The quick little flash of white screen has "No image file" in blue letters--goes by so fast you can hardly see it.

[email protected] said:
The quick little flash of white screen has "No image file" in blue letters--goes by so fast you can hardly see it.
Click to expand...
Click to collapse
That error message is 'normal'. Basically the phone checks the SD card for a file labeled "RHODIMG.nbh". If said file exists, it will flash from it. If no file exists, or no SD present - it continues loading bootloader and should say "Serial" at the bottom. This indicates that it's ready to be flashed. If you plug in your USB cable, it will install some drivers and then it should change to "USB" at the bottom instead of "Serial".
Now you should be ready to flash from a normal RUU. I would recommend flashing STOCK, because this flashes everything.
It might also be good to note a lot of people have experienced something similar - the phone getting "stuck" in bootloader mode, and only occasionally making it to WinMo. I'd guess it's failing hardware in some way shape or form, as none of my RHOD's or RAPH's have ever done this.

Good News--at least for now
Good news--I hooked it up to the computer with the USB cable for awhile and the Windows 7 computer did set up some drivers. For some reason after I disconnected it I reset it, and the reboot worked. Then I immediately uninstalled the squirrely reset program and removed it.
Everything I installed yesterday is working fine--I have soft reset it about 5 times now and each time it has rebooted. So I think maybe I'm back in business. Too soon to tell--but we will pray and keep our fingers crossed.
Thanks so much for your time and help. I don't know how to use the thanks meter but I would have if I could have.

[email protected] said:
Thanks so much for your time and help. I don't know how to use the thanks meter but I would have if I could have.
Click to expand...
Click to collapse
You're welcome. Basically if I or someone else posts something helpful, click the "Thanks" button under that post.

15 hours later, Tilt 2 is still working fine on the newly installed Sense OS. I have rebooted freely (using the stylus button on the side) since removing the program "Rax Reset," and everything seems to be going well. I'm keeping my fingers crossed, and will end my contributions to this thread with a warning about using "Rax Reset."
Thanks to all.