Database Develop

Orange TyTN II troubles

Hi there folks. Appreciate you having a look here, and bear with me while I try to explain everything as I am unsure what on earth is wrong with my phone.
Firstly, I have read pretty much everything that the wiki and stickies and various other posts have pointed me to before making this post, so I am going to utterly hate myself if you guys point me in the correct direction within a couple minutes. I don't think that will happen, but none the less!
Secondly, as the title says, I am running a UK HTC TyTN II with boot SPL 1.81.0000. I have Radio 1.27.14.35.
I only got my phone on Weds of last week. After reading various bits, I tried installing HardSPL, and got the white screen of death. I didnt have time at that time to find the answer, but have subsiquently located it. Shortly after that I located and installed KaiserTweak, and then Resco explorer. Now, both these programs were installed, but I made no changes to anything with them.
After a little bit of searching I found the white screen fix. Great I thought! So went ahead and downloaded the files and stuck them on my PDA. When I tried to run them, they would not run. The error tells me that they are not signed or corrupt.
Ok, so I thought I would try and fix the signiture issue as that is most likely the problem. So I try to run KaiserTweak. No joy. I try to run Resco. No joy. Neither program will do anything. Next I try to re-install either of these. Nothing. Wont work. Either tells me the same thing as the SPLs do (invalid signiture or corrupt) in the case of KaiserTweak, or tells me the installs have failed in the case of Resco.
Now I have tried to install anything and everything since this, and not one thing will install. Nothing. It wont let me change anything or get to anything. I have tried hard resetting the phone, nothing changes. The phone still acts like it did the day I bought it, and as most Orange users will know, they have destroyed any useful software that HTC has used in order to rebrand it with their OS. I would dearly love to get another cab on there, but I am at a loss as to figure out how to get past this stuck phone?!
Any help would be greatly appreciated.

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

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.

my Dream have a big white "G1"

Was updating my G1 and bricked it when I installed the SPL from http://code.google.com/p/sapphire-port-dream/
This had root access before I messed it up.
I've tried all booting methods. Camera and Power, Home Power, etc. and nothing gets me out of the T-Mobile G1 screen.
Please advise if this can be fixed.

congratulations if you cant do anything with those buttons you have now bricked your phone, it makes a nice looking paperweight tho, there is no way to fix what you have done

I REALLY hope you flashed the Radio first like it said so in the instructions... But I guess it doesn't matter now, you are bricked sir =/. I hope you still have the warranty or insurance...?

There is a thread some where on here claimong some type of method to get a new one or something you should look for it n see if it helps u n any way

if you still have a warrenty....say this
"after months of waiting i finally recieved the 1.6 update. but after the phone rebooted it wouldnt start up. i have tried everything the guides on the internet say about how to get it working again and nothing worked. the guides all said that if you cant get to the 'recovery screen' or something like that then you cant fix it..."
wing it along those lines....it works
and next time please post in the correct section - questions go in the QnA section

sidenote - if its a tmobile UK or USA one this will work
if its rogers Canada it wont as there is no 1.6 for rogers dream

did you remember to back it up before you done anything - if so do try the following as this fixed mine when i had that issue
remove and replace battery
boot into recovery mode
use the restore option and restore from backup
if you can get into fastboot then you maybe able to push a new recovery and spl but not sure so you will need to search the forums

as stated, they cant get in, unfortunately

I would say act more innocent than what you say.
Guides, recovery, 1.6 update etc.. would all ring alarm bells for me if I worked for tmobile.
Just say it said something about an update, you clicked ok, it restarted and then wouldnt come back.
Dont mention recoverys, 1.6, guides online etc....

i found that acting intelligent worked better coz 'an intelligent person would never **** up their phone'
and edited version:
"i woke up yesterday and my phone said 'update available' so i hit ok. once it was finished my phone wouldnt turn on - it just got stuck at the G1 screen"

Short Story: GPS didn't work on my G1 so I unrooted for warranty return. After dropping to RC29 my update came and it bricked the phone.
Garok89's statement below is almost verbatum what I told the rep. New phone 3 days later.
garok89 said:
"i woke up yesterday and my phone said 'update available' so i hit ok. once it was finished my phone wouldnt turn on - it just got stuck at the G1 screen"
Click to expand...
Click to collapse

btw.....
i live in Asia....God

well i would try to act dumb first, but then if they start trying to give you hassle, little by little pile on your knowledge of the phone, if you live in asia and cant do anything about it, just make a call to the corporate office and handle it with them, the minute a business this big hears the words "corporate office" im sure they will find a solution for you.

[Q] Urgent help required (Device appears dead)

Hello,
This is my first time posting here, and I would like to request anyone on here to please assist me with the problem I am currently facing. I bought an unlocked, rooted HTC One with stock Android 4.3 installed as it's sole, primary OS this past summer. The person I bought it from is the one who actually rooted the phone, as my knowledge of such processes is fairly limited. I understand there are plenty of complications that I may run into dealing with this problem on my own and technical references may be lost on me, but I'm fairly competent enough to follow instructions from someone who may be able to help.
Here's the problem: I received an Android 4.4 OS update yesterday, which downloaded automatically and asked me if I wanted to install it. I thought the process would be fairly simple and I would not encounter any problems. However, when I asked the update to register and install, first it went into boot (I'm not certain which software was used for root), then the process started and everything seemed to be going fine until 'Patching files onto the whatever' came up and then it appeared that I encountered an error and the phone automatically went into what I can only assume is the bootloader menu? There were big Stock Android looking buttons on it which said things like Install, Root, Settings and a few others I don't recall. I tried to hit Install to see what happened and it brought me back to the part where 4.4 was supposed to be installed and I could read the error message at the end of it which said something like 'Error in patching files to zip folder or something', and I went back to the supposed bootloader menu. Confused and afraid, I think I pressed a button which I felt would allow me to reboot my phone and bring me back to my original 4.3 OS and that I would still be able to use my phone. First it said something like 'You no longer have root permissions', and there was an option where I could slide to apparently 'fix this', but I selected the 'don't fix' option as I obviously had no idea what I was doing. After this, the phone attempted to reboot, and a turquoise blue screen with strange markings came up on it and my phone hung. I killed the phone with the master power button and held it to switch off the phone.
BUT now, even since that has happened, my phone appears to be dead. It isn't starting up. When I put it on charge, the red LED doesn't show up. I have tried to used several ways to turn on my phone but it just wouldn't work.
I would like some light to be shed on this particular problem, and if anyone has experienced something similar to this, PLEASE, help me in fixing this. I am an eager learner and despite my limited, close to non-existent knowledge about dealing with a phone's OS, I know I can learn fast and follow instructions cleanly.
Please help me. Thank you.