Database Develop

locked up wont reinstall and now not charging! help!!

ok my xda locks up (nothing new there!) soft rest and all i get is a white screen! try again and the same thing happens. So i decide to do a hard reset. This appears to be working until it's loading applications and settings (O2) when it hits a .per file (i think) and tells me i need to find the source .cab file.
the 2 choices i then have are ok or cancel, niether work the bloody thing is locked up again! so i soft rest it and it's back but with no O2 settings. I try and run a back up from my pc and it all works apart from about 15 files that it cannot reinstall (mainly to do with contacts). I then sync my contact list as that is missing and all looks good! 2 days configuring it back to my liking and all looks good once again!
This morning no alarm to wake me up (bugger im now half hour late for work! lol) the xda had been on charge all night and it appears to be dead! All i can see is the O2 logo like you get at start up but with no back light. the unit does not respond to anything. I've tried taking the battery out, soft and hard reset all with no response! I try and put it back on charge and all i get is the red light come on for 2 mins then go off again! can't turn it on while on charge!
Please help as phoning O2 is really like banging our head against a brick wall!
thanks guys

i'm not to sure but i would say you have two options either download the rom from the o2 website or download the rom Modified_XDA_IIi_Upgrade_V1.11.162_Radio_1.04.rar i installed it yesterday and i haven't had any problems hope this helps

ty but if i cant turn the phone on or connect it to the pc how can i do that????
i might give O2 a call anyway and see what they say. they might offer me a new one which is always good!

o2 could offer you a new one but i read somewhere on this site that the xda IIi has been discontinued so they might upgrade to the xda exec

When I first got my 2i, I had it for a week and then out of the blue it decided to do this after a soft reset one day - got stuck at the O2 splash screen, no backlight, frozen forever. Had to take the battery out to turn it off.
Took it into the shop, the store manager said "yeah, we've seen this happen more than once", and just went into the storeroom and got a me a brand new one.
This did happen the day after I'd run the simunlock tool found on this forum, which worked successfully (I tried my Virgin mobile SIM in it and it worked first time, but I then took it back out and put my O2 SIM back in)... I'm not sure if it was just coincidence or what, but I'm not feeling too eager to run simunlock on my Alpine again until I sell it

thanks guys i thought it might be fried!
called last night but got cut off and then was after 7 so couldn't speak to anyone! :evil:
will try again and see what they say!
when i put it on charge it charges for a few mins then turns onto splash screen for a few mins then turns off and charges again and so on in a loop! really quite annoying! lol

Another thing to try is to put the device into bootloader mode and force a firmware upgrade. It can be connected to the PC but it will no longer use Activesync so the upgrade will work fine.
Once this is done it will be using more up to date firmware if you download the ROM from this sites FTP and should work better in general.

well carphone craphouse couldnt do anything with it so has had to go back to O2 went on the 10th dec and still no word

PC crashed during flashing, recovery!

Hello
Ive finally got round to putting new radios and ROM on my diamond, a year after buying. Didnt want to before now incase i cocked it up (theres a lot of things to remember!)
Hard SPL went fine and i was putting the new radio on (1.00.25.05 in this case) when, at about 80% of the way through the install my pc froze (as its having a habit of doing at the most awkward times recently!)
I soft reset the diamond but now its at what i assume is the bootloader screen (?), its got red, green, blue and white bars and various writing, along with a message saying 'Upgrade ROM code error Please try again'
I had a hunt round and found something for another device saying how to get it back by loading a factory ROM through the bootloader menu but i dont know how to do this as i dont have a connection to activesync (phone wont go beyond this screen) etc.
If someone could explain in relatively simple steps it would help!
I should also clarify that the only way i can get this screen off is to remove all power but as soon as i put power back on it loads up direct to this screen again!)

When you device is in bootloader mode, you dont need active sync connection. just run the update utility and it will work without it, as it uses different drivers when connecting.

This turned out to be quite easy actually, i stumbled across the answer somewhere else!
Thanks for the help

Slightly different Kaiser problem

Ok, first off ive scanned xda and cant see an answer to this specifically, hence the post.
Love the Kaiser-14months and using L26 Diamond Build
Lost the phone one night while worse for wear and bought another on ebsay-cus its a great phone. This morning new phone and where the problem begins-
Phone arrived. Good nick and standard O2 rom is onboard- no issues. Had my sim in for a while, and texting/phone/apps are normal. Now i had an old Sprite Backup file from my old phone from March so i straight away tried to back up. I didnt consider any other factors.
Now however im stuck. The phone boots. The L26 screen and music come up but eventually i hit a new message on white screen:-
"The device is unable to boot because you have turned off the device incorrectly or tried to install an application from untrusted source.Press send to rest your device... blah blah"
Pressing send,doing nothing or hard resetting the device just keeps me going on the same cycle. I take it because i backed up a new ROM, i should have flashde this phone first. Never thought.
Can i get back to basics again?? Help.Im using a Palm treo at min and hate it.

Possibly a dead Kaiser, suggestions? (or purchase!)

So, I plugged my Kaiser (Tilt) into my computer the other day to charge it, and the next morning when I unplugged it, I noticed it was locked up. No biggie, I soft-reset it, and it came directly back to the bootloader (right before the bootloader shows is a white screen, that says "Loading image... No image found!", that flashes for a fraction of a second.
If I plug it into my computer at this point, Windows says the USB device has malfunctioned and it doesn't recognize it. I can't flash it ("connection error"), and it wouldn't hard reset.
Then it kinda came back to life, kinda. Suddenly it'll boot into WM. Windows still doesn't recognize it, but I used JumpSPL to get it into a bootloader, and tried to install a HardSPL on it so I could flash a new ROM (to this point it's been stock-only because it belongs to the company I work for). The HardSPL flash failed partway through, and then it was stuck in bootloader for real. At that point I tried flashing a stock ROM, and it kept failing at different points, never getting more than about halfway through.
Does anyone have any suggestions? Or, do you want to buy it? At this point it's mine (company doesn't want it back), so I'm willing to experiment freely with it. Right up until my Touch Pro 2 comes in and I lose interest
*** UPDATE ***
So after writing this, just for kicks, I decided to give re-flashing the original ROM one more shot (it's been off and untouched now for several days at this point) and the flash succeeded. We'll see where it goes from here

Good luck with your phone.. I hope all goes well.. If you find out what the problem was/is, let me know

Hey godefroi, im new to all of this, just bought a messed up tilt from my friend, and i want to know if you could givve me the link for the insturctions to refalsh my tilt

Just hit up AT&T's site (which redirects you to HTC's site) and download the ROM. The file you want is "_ATT Tilt_RUU_Kaiser_CINGULAR_WWE_3.57.502.2_radio_sign_25.88.40.05_1.65.21.18_Ship.exe", which was the latest update for the phone.

Seems it's not fixed. After playing around with it for a couple days, it's back into bootloader and stuck there. Taking out the battery and leaving it for a few hours brings it back for a while, but it seems there's no permanant fix. Next step will be flashing HardSPL and a custom ROM. I'll update when that happens.

awww dang, that sucks. thank you for tellin me. hopin your tilt comes out ok

Did you ever get this resolved?
Hey man did you ever get this fixed? I cant find anything on it.
I can get to a boot loader screen and it shows USB and when I plug it into my computer I hear the sound that it's recognized but my active sync wont connect.
This is what I posted earlier and a moderator killed the post because I didn't spend hours hunting for a solution first before posting. I don't think one exists but if there is I would be glad to know it. I have flashed this phone and my older HTC Wizard dozens of times with no issues so Im not a "noob"
Earlier today I was taking a picture and the screen kind of stuck so I has to soft reboot it.
It didn't come back up. I was left at the rainbow bootloader screen.
I tried holding the camera button down and rebooting but it didn't change anything.
I tried several different combo's of holding keys down and rebooting and it always came back to that bootloader screen.
So the next thing I did was to format my cd card and downloaded KaisDiagTest1.zip and then coppied the KAISDIAG.NBH image file from the zip on to the root of the sd card.
That worked fine and I was left at a screen saying SPL 1.00.OliNex.
Next thing I did is were I think I screwed up. I flashed it with _ATT Tilt_RUU_Kaiser_CINGULAR_WWE_1.62.502.0_radio_sign _22.45.88.07_1.27.14.09R2_Ship.exe which is the ROM from the HTC site and I think I was only supose to use a custom ROM and now after it finished flashing the ROM it rebooted and is stuck showing loading ... on the screen.
It goes past the boot loader and is stuck at loading...
Please advise if there is anything I can do.
Cheers,
Chris
godefroi said:
So, I plugged my Kaiser (Tilt) into my computer the other day to charge it, and the next morning when I unplugged it, I noticed it was locked up. No biggie, I soft-reset it, and it came directly back to the bootloader (right before the bootloader shows is a white screen, that says "Loading image... No image found!", that flashes for a fraction of a second.
If I plug it into my computer at this point, Windows says the USB device has malfunctioned and it doesn't recognize it. I can't flash it ("connection error"), and it wouldn't hard reset.
Then it kinda came back to life, kinda. Suddenly it'll boot into WM. Windows still doesn't recognize it, but I used JumpSPL to get it into a bootloader, and tried to install a HardSPL on it so I could flash a new ROM (to this point it's been stock-only because it belongs to the company I work for). The HardSPL flash failed partway through, and then it was stuck in bootloader for real. At that point I tried flashing a stock ROM, and it kept failing at different points, never getting more than about halfway through.
Does anyone have any suggestions? Or, do you want to buy it? At this point it's mine (company doesn't want it back), so I'm willing to experiment freely with it. Right up until my Touch Pro 2 comes in and I lose interest
*** UPDATE ***
So after writing this, just for kicks, I decided to give re-flashing the original ROM one more shot (it's been off and untouched now for several days at this point) and the flash succeeded. We'll see where it goes from here
Click to expand...
Click to collapse

I never did. Every once in a while I can get it reflashed, but inevitably it stops working. Just like yours, I'll sfot reset it and it'll be stuck in bootloader.

Best bet is when it gets stuck on the bootloader or on the "white screen" as to put it. Do the following:
1) Unplug battery, memory car and simcard. Reinsert battery ONLY after 3 seconds (cards stay out!)
2) Hold BOTH softkeys down at the same time
3) Whilst holding softkeys, turn the unit on
4) You will be prompted to press "SEND" to reset all user data (you will lose everything on the internal storage. Press the Dial (green button) to reset.
5) When it's finished, you will be prompted to press "SEND" to reboot. Press send and it will boot into WM but might take slightly longer.
6) Realign your pointer and tada. It's up and running.
n.b. This often happens when the radio version of your phone isn't correct. If you notice, when you get stuck in the "white screen" the "gsm signal sight" is frashing green!
I've got to warn you again, this procedure WILL delete all of your internal user storage, hence why I recommend taking out all of the cards before proceeding.

heyadrian said:
Best bet is when it gets stuck on the bootloader or on the "white screen" as to put it. Do the following:
1) Unplug battery, memory car and simcard. Reinsert battery ONLY after 3 seconds (cards stay out!)
2) Hold BOTH softkeys down at the same time
3) Whilst holding softkeys, turn the unit on
4) You will be prompted to press "SEND" to reset all user data (you will lose everything on the internal storage. Press the Dial (green button) to reset.
Click to expand...
Click to collapse
Nope. Stuck in bootloader is stuck in bootloader. Like, stuck. No, really, it's stuck. Hard-resetting doesn't get it out.
heyadrian said:
n.b. This often happens when the radio version of your phone isn't correct. If you notice, when you get stuck in the "white screen" the "gsm signal sight" is frashing green!
Click to expand...
Click to collapse
There's no white screen, just bootloader rainbow. Also, there's no chance that I flashed the wrong radio, because this phone has never been flashed with anything but the official ROM. It's never even had a HardSPL flashed on it.

hmmm...now that you mention it has never had a hardSPL, maybe that could be the next step?
i understand that some people may want to keep a "stock" configuration in case waranty needs to be claimed or for any other valid reasons...but if the phone is out of waranty, theres little to lose.
only reason i'm suggesting it is because cmonex has a hardSPL that aims to fix EXACTLY this problem, among others (if i understand your problem and cmonex's fix correctly):
http://forum.xda-developers.com/showthread.php?t=420683
also, this thread links to a page in the wiki about your problem (or something along the same lines):
http://forum.xda-developers.com/showthread.php?t=423486
finally, a collection of hardSPL versions can be found in this "roll up" thread:
http://forum.xda-developers.com/showthread.php?t=498320
i guess you may have already gone through the above mentioned links but if not, they may open up more avenues for troubleshooting or even a permanent resolution.

RHOD210 Won't Boot.

I was running one of the ENERGY ROMs on my TP2, so it's got a different SPL and all that. I then put it in the box for about 5 weeks. I took it out two days ago to install XDANDROID. I used XDANDROID for about an hour, until the TP2 started randomly shutting itsself off. I've tried flashing NRGZ28's ULTRA LITE ROM and the official T-Mobile USA 6.5 ROM for the TP2. It won't go past the boot loader a majority of the time. When it does, it goes on to act like it's flashing the RHODIMG.nbh on my MicroSD but almost instantly after it starts, it shuts off again. It doesn't always try to flash the .nbh, but when it does, it never finishes. It's the same story with a hard reset. I can't ever get it to turn on, and the only way it does turn on is to do a battery pull. If I'm lucky, it'll stay on for about 60 seconds and then shut off again. I'm really clueless as to what to do here and I'm hoping someone can help me.
The Bootloader reads as folows:
RUUNBH
RHOD210 32M SS-BC
SPL-0.85.OilNex
MicroP(LED) 0x0A
MicroP(KEY) 0x04
TURBO HW/TURBO SW
TP MFG DATA
[unreadable]
812,19...
217.855 Calibrated
The reason 1.5 of the lines is unreadable is because of the message over it: "Upgrade ROM code error. please try again."
http[colonslashslash]farm3[/url][dot]static[dot]flickr[dot]com/2726/4386331314_8036d882a6_o.jpg

try flashing hard spl 1.01 it looks like you got an old version of the spl. read the sticky on flashing for newbies i belive it tells you how to do the hard spl if you are having difficulty by usb connection other than that i wouldnt know what to tell you i nver had that problem only bad flashes but those could be solved by reflashing another ROM

Sorry, i should have explained that better. I can't connect to the PC. It won't stay in bootloader mode so I can't flash it that way either. From what i understand, the only way i can flash anything to it right now is to get the xxxx.nbh file, rename it to RHODIMG.nbh and place it on the root of my SD. When I do that, though, it won't finish the flash. It just keeps going in a loop. about every 5 minutes it randomly turns on and tries to flash the RHODIMG.nbh if present. If it's not present, it just flashes the boot loader for >10 seconds and shuts off again.
Also, I'm not sure if this makes any difference, but I've had TWO computers recognize it as a new device, "Qualcomm CDMA Technologies MSM."

Make sure the battery has a good charge, nothing else springs to mind
PS. the qualcomm thing is what appears when it's flashing via USB
also maybe try formatting your SD card and put the stock ROM back on there, or try diff card

chasejones8 said:
Sorry, i should have explained that better. I can't connect to the PC. It won't stay in bootloader mode so I can't flash it that way either. From what i understand, the only way i can flash anything to it right now is to get the xxxx.nbh file, rename it to RHODIMG.nbh and place it on the root of my SD. When I do that, though, it won't finish the flash. It just keeps going in a loop. about every 5 minutes it randomly turns on and tries to flash the RHODIMG.nbh if present. If it's not present, it just flashes the boot loader for >10 seconds and shuts off again.
Also, I'm not sure if this makes any difference, but I've had TWO computers recognize it as a new device, "Qualcomm CDMA Technologies MSM."
Click to expand...
Click to collapse
it sounds like you dont have your sd card formatted make sure its format to FAT32 go to your computer inserd sd card & reformatted (make sure its a micro sd & that its less than 2g) then transfer the ROM to the card already renamed to RHODIMG then inserd ur card on your phone & flash it. it should work. let us know what happens

MadBeef said:
Make sure the battery has a good charge, nothing else springs to mind
Click to expand...
Click to collapse
I wish I could. I have no means of checking the battery status. I've had it plugged in pretty much constantly for about the last two days.
MadBeef said:
PS. the qualcomm thing is what appears when it's flashing via USB
Click to expand...
Click to collapse
I figured that's what that was, I was just a little shocked that it said CDMA.
And I tried wiping the card and reflashing, but it did exactly the same thing.

See at the top of your bootloader readout, where it says RUUNBH? That means the RUU flag is set, and that needs to be unset before you can do other things. What you need to do is establish a connection with your device via MTTY. Follow the instructions here about how to do that. Once you get an MTTY connection established with the device (it may take awhile since MTTY is quirky sometimes), type
Code:
Set 16 0
You may need to manually soft reset afterward, but otherwise you should be in the clear

The TMO Stock ROMs can install via PC even if your phone has a faulty USB connection. The stock ROM installer will keep restarting the phone's USB connection automatically as needed if your phone can't appropriately flash in one straight attempt. You can get the newest stock ROM here. And definitely install HardSPL again after getting the phone up and running on the stock ROM.
You might also try MTTY.exe. When connected, run the command 'set 16 0' then 'task 8' then 'task 0'. If your phone doesn't automatically soft reset, then manually soft reset with the stylus.

will MTTY.exe work via parallels on a Mac? I haven't tried it yet, but I have limited access to a PC. also, I tried doing the HardSPL and the TMO rom via PC, but the phone just does the same thing. It will connect, but then the RUU tries to check the phone settings and the phone shuts off. this is the problem i am having. i just cant get it to say on long enough to do anything. I'll try the MTTY.exe through parallels and if it won't respond, I'll have to wait to try it on a PC. I'll let you know how that goes.

MTTY is quirky enough that it probably won't work through parallels, though there's no reason you shouldn't at least try and see if it works. You'll probably have to wait until you can get access to that PC. Best of luck

DaveTheTytnIIGuy said:
MTTY is quirky enough that it probably won't work through parallels, though there's no reason you shouldn't at least try and see if it works. You'll probably have to wait until you can get access to that PC. Best of luck
Click to expand...
Click to collapse
Thanks. I'll have to wait till i get back to the phone but i will let you know how it turns out.
also, in reading your sig, i see that i was using the same SPL that you are. have you had any problems with it?
I was also using the ENERGY LEO ROM [i now see that you are using it too.], which apparently was defective because the next day, the chef posted a new one because of "sleep of death." I read through the thread and didn't see anyone with the issues that i was having.

chasejones8 said:
Thanks. I'll have to wait till i get back to the phone but i will let you know how it turns out.
also, in reading your sig, i see that i was using the same SPL that you are. have you had any problems with it?
I was also using the ENERGY LEO ROM [i now see that you are using it too.], which apparently was defective because the next day, the chef posted a new one because of "sleep of death." I read through the thread and didn't see anyone with the issues that i was having.
Click to expand...
Click to collapse
I haven't had any problems with this SPL, but then again, this is the only end-user version of HardSPL for GSM devices that's been made available. The SPL isn't even your problem, the only problem is that a bootloader flag is set which shouldn't be.
As for the EnergyROM sleep of death problem, that's not what you're suffering from. The sleep of death problem is when your device won't resume after being put into standby, meaning one must soft-reset their Rhodium and lose any unsaved data in open programs. It's a somewhat common problem among many HTC devices, from the old ones like the Kaiser to the newer ones like the Rhodium (though I don't think any Android device has this problem).

jdep1 said:
try flashing hard spl 1.01 it looks like you got an old version of the spl.
Click to expand...
Click to collapse
Eh ? Sorry, but I think you're confused. He's running 0.85 HardSPL, which is the one and only version for GSM Rhodiums.

I got to a PC and tried MTTY.exe
I can't seem to get it to connect. It just says "USB port can not open."
Any suggestions?
EDIT: I can get it to connect to a different version of MTTY.exe for a short time, but I can't type anything. All I get is a blinking cursor.

chasejones8 said:
I was running one of the ENERGY ROMs on my TP2, so it's got a different SPL and all that. I then put it in the box for about 5 weeks. I took it out two days ago to install XDANDROID. I used XDANDROID for about an hour, until the TP2 started randomly shutting itsself off. I've tried flashing NRGZ28's ULTRA LITE ROM and the official T-Mobile USA 6.5 ROM for the TP2. It won't go past the boot loader a majority of the time. When it does, it goes on to act like it's flashing the RHODIMG.nbh on my MicroSD but almost instantly after it starts, it shuts off again. It doesn't always try to flash the .nbh, but when it does, it never finishes. It's the same story with a hard reset. I can't ever get it to turn on, and the only way it does turn on is to do a battery pull. If I'm lucky, it'll stay on for about 60 seconds and then shut off again. I'm really clueless as to what to do here and I'm hoping someone can help me.
The Bootloader reads as folows:
RUUNBH
RHOD210 32M SS-BC
SPL-0.85.OilNex
MicroP(LED) 0x0A
MicroP(KEY) 0x04
TURBO HW/TURBO SW
TP MFG DATA
[unreadable]
812,19...
217.855 Calibrated
The reason 1.5 of the lines is unreadable is because of the message over it: "Upgrade ROM code error. please try again."
http[colonslashslash]farm3[/url][dot]static[dot]flickr[dot]com/2726/4386331314_8036d882a6_o.jpg
Click to expand...
Click to collapse
I had this EXACT same problem a week ago. I fell asleep in the middle of flashing, the phone died when it finished. I woke up, turned on the phone, ENERGY leo was trying to run its install but kept dying. Smart me, I tried to reflash (by holding the vol down button and turning it on- not through usb) and it kept dying in the middle of trying to flash.
The problem is the battery. It can't charge when it's flashing and it can't hold a charge long enough to get past the flash.
I swapped batteries with my friend, restarted the flash and it worked fine.
I let my battery charge in my friends Sprint Hero
and voila, everything went on happily ever after.
tl;dr find a way to use a charged battery while flashing.
your phone's not bricked.

bfgarzilla9k said:
I had this EXACT same problem a week ago. I fell asleep in the middle of flashing, the phone died when it finished. I woke up, turned on the phone, ENERGY leo was trying to run its install but kept dying. Smart me, I tried to reflash (by holding the vol down button and turning it on- not through usb) and it kept dying in the middle of trying to flash.
The problem is the battery. It can't charge when it's flashing and it can't hold a charge long enough to get past the flash.
I swapped batteries with my friend, restarted the flash and it worked fine.
I let my battery charge in my friends Sprint Hero
and voila, everything went on happily ever after.
tl;dr find a way to use a charged battery while flashing.
your phone's not bricked.
Click to expand...
Click to collapse
That's the best news i have heard so far. I don't know anyone with a TP2, but i do know someone with a Hero. I'm assuming the GSM hero uses the same battery as the CDMA Hero and the TP2. I'll look into it and let you know how it goes.

chasejones8 said:
That's the best news i have heard so far. I don't know anyone with a TP2, but i do know someone with a Hero. I'm assuming the GSM hero uses the same battery as the CDMA Hero and the TP2. I'll look into it and let you know how it goes.
Click to expand...
Click to collapse
chin up, bud
I actually had a replacement sent to me.
That took a week. I fixed my phone the DAY AFTER i requested a replacement.
ohwell.
Brand new TP2 for ten dollars (shipping) I'm not really complaining.
&yes. The GSM Hero does use the same battery. I was just looking at my friends phone, decided to take a look at the battery and shat bricks when I saw it fit in my phone.
report back after you try your friends battery if it works or not!

bfgarzilla9k said:
chin up, bud
I actually had a replacement sent to me.
That took a week. I fixed my phone the DAY AFTER i requested a replacement.
ohwell.
Brand new TP2 for ten dollars (shipping) I'm not really complaining.
&yes. The GSM Hero does use the same battery. I was just looking at my friends phone, decided to take a look at the battery and shat bricks when I saw it fit in my phone.
report back after you try your friends battery if it works or not!
Click to expand...
Click to collapse
thank you so much! that fixed everything. they weren't quite the same battery, the one from the HERO isn't quite as wide. it did work, though. I'm charging my tp2 now. not sure if the battery is shot or not. everytime i unplug it, it shuts off. i'll have to charge it for a while and see if that changes anything. again, thanks so much!