Database Users

HTC TyTN doesn't boot.

Hi there.
Today my HTC TyTN decided to hardware-reset itself twice, which I thought was a bit weird, but not the biggest problem since I have most of the same stuff on my other phone.
But just now, it seems like it did it again, only now it doesn't boot. It seems like it freezes while booting.
I've tried taking the battery out and in again, booting while connected to USB, and booting without the SIM card inserted, but nothing fixed it.
Does any of you guys have ideas that might solve my problem ?
Might it be possible to flash it with a new ROM without being connected with ActiveSync ?

Do a search for bad blocks, look in the upgrading thread, guaranteed that theres something there or do a search for "how to fix bad blocks hermes", that should get you some things to read.
If it is bad blocks reflashing a new rom WON'T help.
If you don't have bad blocks, you may have installed a BS ROM recently, then the best advice is to flash a Stock rom first, make sure the radio rom has been stripped out or you'll end up having to reflash that too. Then reflash the BS rom of your choice.
Cheers...

[Q] How to avoid bricking your device?

I`m going to start cooking custom ROMs for my diamond and i don`t want to lose[/brick] it, i want it alive.
The question is, what actually bricks your device, a wrong cooked ROM or too many ROM flashes? Or both? I know that importing a ROM from another device to your kitchen and flash it to your device bricks it. Are there other ways to brick it?
My device has about 50 flashes and about 40-50% are with MTTY[/TASK 29]. How many ~ flashes can take a diamond before brick?
Sorry if my english is bad!

One has to establish what the term "bricking my device" is really intended to describe. Historically, it is used to describe when a device cannot be resurrected from a non-booting state and is generally non-responsive to attempts to get into bootloader. However, being able to get into bootloader doesn't necessarily mean that you'll be able to flash and recover, as I have seen two occasions where the person could get into bootloader, flash the appropriate stock rom and when the device reset, it simply returned to bootloader.
I go through all of this to contrast the above scenarion against what some folks have started to describe as "bricking my device" ... which is a bad flash, where the device doesn't get past the boot splash, but is easily resolved by going into the bootloader and flashing a rom that is known to be good.
Generally, the risk of really "bricking your device" is low as long as you are flashing SYS/XIP/OS only roms for your device.
Most folks get into trouble when the start messing with the boot loader and / or radio.
Based on MTBF, it has been stated that the average flash rom included in these phones could probably flash somewhere near 10,000 times.
All IMHO ... you'll do yourself a favor and, in addition to asking via this thread, use google to search for existing threads to get a variety of replies, just so you have visibility into the range of answers that you'll come across.
Best regards,
-boggsie

Thank you for your reply! I`ll search on google too.
I think that this question has found its answer.
Thanks again!

thecrazyman64 said:
I`m going to start cooking custom ROMs for my diamond and i don`t want to lose[/brick] it, i want it alive.
The question is, what actually bricks your device, a wrong cooked ROM or too many ROM flashes? Or both? I know that importing a ROM from another device to your kitchen and flash it to your device bricks it. Are there other ways to brick it?
My device has about 50 flashes and about 40-50% are with MTTY[/TASK 29]. How many ~ flashes can take a diamond before brick?
Sorry if my english is bad!
Click to expand...
Click to collapse
Okay, I learned it the hard way , cooking and flashing already costs me 2 devices.
The first device I only went back to my original rom when my devices acting weird, most of the time after 10 flashes, but after 6 months my device died.
My second device, I always flashed the original after a cooked build but that one only lived for 3 months.
So I decided to get myself another phone (all 3 phones are Niki btw) and only flash through sd-card, for now I already flashed my device 200 times without getting back to the original rom.
Regards,

Rataplan said:
Okay, I learned it the hard way , cooking and flashing already costs me 2 devices.
The first device I only went back to my original rom when my devices acting weird, most of the time after 10 flashes, but after 6 months my device died.
My second device, I always flashed the original after a cooked build but that one only lived for 3 months.
So I decided to get myself another phone (all 3 phones are Niki btw) and only flash through sd-card, for now I already flashed my device 200 times without getting back to the original rom.
Regards,
Click to expand...
Click to collapse
Well, this is why i got scared, the chef of the ROM i am using bricked his second diamond yesterday. And the second device lived only 1-2 months, but it was a used one.
I made only about 10 ROM flash in the normal way, RUU and USB cable, but now i am only flashing from internal storage and before that i use MTTY.

[Q] Freezing issue for the clever folks

Hello folks, I appear to have gotten into bother during a rom flash. After successfully installing a MAGLDR nand rom via CWM, the first boot of said rom just gives me the frozen splash screen without animation and the boot does not complete. Happens the same with three different roms.
I suspected somewhere further back in the boot process was at fault so I reflashed a known working radio rom, but problem still persists.
Despite a LOT of reading I can't see much about freezes at this point in the boot process on MAGLDR roms.
Bits that work - HSPL rainbow boot screen happily comes up, Task 29 works, magldr reinstalls and works fine, CWM perfect. Installs roms from SD (freshly reformatted) and appears to be ready to go, until boot actually begins then... splash screen freeze.
I have redownloaded various versions of everything to ensure no issues with corrupt files. I have also used different SD cards and ensured freshly formatted FAT32.
If it helps anyone, I have previously used NDT CM7 12.1 for about a month with zero problems.
Any other less obvious stuff I'm missing?
I'm off to bed so will be approx 7 hours from post time when I start responding. In the meantime I've put MAGLDR 1.10 on the phone so at least it can charge!
Many thanks in advance for reading.

Replying to self with update:
Installed OzRom Winmo 6.5 via the tried and trusted CustomRUU method, and it appears to work perfectly. What is winmo doing that android nand roms don't? I assumed if there had been bad blocks on the nand the much larger windows mobile rom would have covered this, and thus failed on boot.
At least opens the door to using an SD build till I can troubleshoot. Odder and odder.
Forgive my ignorance, but if the CustomRUU flash method still works for me, are there any modern android roms that don't need MAGLDR or clk?
Again, many thanks.

drachers said:
Replying to self with update:
Installed OzRom Winmo 6.5 via the tried and trusted CustomRUU method, and it appears to work perfectly. What is winmo doing that android nand roms don't? I assumed if there had been bad blocks on the nand the much larger windows mobile rom would have covered this, and thus failed on boot.
At least opens the door to using an SD build till I can troubleshoot. Odder and odder.
Forgive my ignorance, but if the CustomRUU flash method still works for me, are there any modern android roms that don't need MAGLDR or clk?
Again, many thanks.
Click to expand...
Click to collapse
How long have you been leaving the ROM on the boot screen? A first install of an Android ROM can take anywhere up to and over 15 mins for first boot. I also remember one when installing a hyperdroid ROM I had to restart the phone once to get passed boot splash.
I'd recommend flashing a popular ROM, leaving it for 20 mins, restarting and leaving another 20 mins. What do you have to lose? Just remember magldr doesn't have charge while off capabilities!
Also check your partition sizes and layout (you have to edit flash.cfg for magldr builds, partition sizes depend on the rom you pick but will be specified in the ROM thread).

Thanks for the reply. Each time I left the rom on the boot screen for a good half hour, and in one case an hour. I have installed NDT 12.1 and the newer v16 successfully before, so I know what sort of timescales are involved. I also had a go at an earlier Typhoon build. Naturally I used only the recovery sizes specified in each rom's own thread, using versions of MAG/CWM specified there, and Task 29 beforehand.
I have an update to all this, however. Previously I said Winmo installed, but now it is bugging out to all hell. This might fit my "bad blocks in nand" hypothesis, perhaps the files covering the bad area are less critical than the ones in each android build, and Winmo just crosses its fingers and tries to boot anyway!
In any case, if I can get an SD android build running I'll cut my losses and stick with whatever works.
Cheers again, hopefully this random screed of info will help people. Seems to be if all else fails, try winmo.

[Q][Nov. 16]upgrading my htc hd2 TMOUS

Good day to all esp. to the masters of XDA,
First off, I'd like to apologize if there's already a thread like this or a kinda sorta thread like this. I've tried searching but haven't found answers really pertaining to my inquiry. If you do know a thread please point me to it, sorry for the trouble.
On to my question: I have an HD2 TMOUS with stock rom ver. 2.10.xxx, I would like to upgrade to stock rom ver. 3.14.xxx. I would like to know if I could upgrade directly to 3.14.xxx or do I have to go through upgrading to the versions in the middle of 2.10.xxx and 3.14.xxx before going to 3.14.xxx.
Currently I have SPL-3.03.0000 which I've installed using HSPL4. Do I have to uninstall this and go back to 1.66?

Hey ralfkof119, this topic have been discussed several times. Since I'm in a good mood today I will point you out to the right direction. Yes you can download directly from 2.10.xxx to 3.14.531.1
1) http://dl.htc.com/ruudownload/t-mobileUS/DeviceDownloads.aspx?pid=leo2
2) type in your 15 digit IMEI number then press SUBMIT.
3) download the file to your desktop.
4) connect your phone to the computer and let it synchronized
5) backup all your personal information because it will factory reset your phone.
6) double Tap on the file you just downloaded follow the steps and VOILA'.
your phone should bow be Tmobile official 3.14.531.1.

Thanks for the reply. I read in the link you gave me that I can update directly to 3.14 so I tried it but upgrade doesn't go successfully, I always get error 262. So I searched the forums for error 262.
Although there wasn't much about 262, the threads gave me an idea to use task 29 before installing 3.14. So I installed HSPL 3.03 with HSPL 4 and tried task 29 and then run the 3.14 ROM downloaded from your link and it went successfully.
I just want to know if I did it right. Although it is working now, I might've messed something up to cause a major bad later. Please do confirm. Thanks again.

Yes you did it right.

Error 262 is because you were running the update with winmo running, so step 1 when you run the .exe is the phone restarting into bootloader, by which time the USB connection has timed out.
the method you ended up using, you entered bootloader manually and then established the USB connection, so no timeout.
when you received the 262, had you simply run the .exe again without touching the phone (which had already entered bootloader) the flash would have worked.
Summary, when flashing rom/radio/hspl, put the phone into bootloader manually first.

Ohhhh.... Thanks samsamuel. But it is still good practice to do a task 29 just to clean things up ^_^.
I'll be sure to remember that samsamuel.

ralfkof119 said:
But it is still good practice to do a task 29 just to clean things up ^_^.
Click to expand...
Click to collapse
well, kinda, in theory. i've never done one (well, once, two yrs ago) and ive never had any probs . Flashing a stock rom performs a task 28 anyway, which covers most of the areas a task 29 covers, , plus, there are increasing numbers of people reporting what appear to be bad blocks, especially now we are flashing nand android a lot, and to my mind a task 29 seems like unecessary extra wear and tear on the nand memory.
Im not saying task29 is useless, i'm sure it does help in certain circumstances, , but i'm also sure 99% of task29's that get performed every day are wasted.

[Q] ClockworkMod installing problem and fatal hit error at AD Recovery..help ?

Hello..a friend of mine gave me a HD2 to fix, said it can't load anything. As I own a HD2, I took it just to see what's wrong. I own an Asian HD2, and everything is fine, I tried various ROMs..both Android and WinPhone, settled at Hyperdroid. Anyway, I have no idea where the heck the other HD2 is from, neither my friend has.
So, the phone had nothing in it and was stuck at the HTC logo, so I loaded into bootloader and saw HSPL 3.03. Then I changed it to 2.08 in order to install MIUI android. Then I installed MAGLDR. The issue occured when I went to install CWM. I loaded the 150M partition at USB Flasher, it was doing all fine until it became stuck at "reset now...!". So I just took the battery off, and tried to load into AD recovery. While it loads to 1, then it shows "fatal hit" error. I tried a lot of times including task 29, but it persists. Was the phone bricked from earlier ? Something like heating issues I assume. Anyway, I tried to install my phones stock WinMo rom to it from SD but it also gives error like failed, not allow etc. The both phone looks the same, under the battery hood of my phone, it's written HTC HD2 T5858. On the other one, nothing. Rest visuals are same.
So is there any way I can bring this anonymous HD2 to life ? I think it's almost dead but still if there's any way you people can come up with. I'm using a 2GB Sandisk MicroSD and the phone's S/N is HT01CNW04979 ; if that helps to sort out the phone's identity. Your help is much appreciated. Thanks

http://forum.xda-developers.com/showthread.php?t=1520439
this is a thread I created 3 days ago....me, another user, and now you...
our hd2s are going to diee D: stop joking, I (and toher guys) think that is hardware related....like in my case....but I don't really know what's the problem, just guessing....take a look to my post

True that. Only the difference is, it's happening to me during clockwork recovery installation. And I don't know where the heck is the phone from so that I can load custom WinMo lol. My own HD2 is doing just fine by the way.
http://imageshack.us/photo/my-images/263/87604378.jpg/
http://imageshack.us/photo/my-images/412/59177201.jpg/