[Q] Radio Bricked HD2 Please Help - HD2 Windows Mobile 6.5 Q&A, Help & Troubleshooting

Hi Friends,
Everything was fine until my HD2 it turned off and since then ( two weeks ago) all it shows me when I turn it on is a black and white striped page( it goes to bootloader mode though and everything is fine,! it's not a hardware problem) . I've tried everything you name it,( Flashing via SD card, Using Mtty, Usin diff radios, and a buch of other stuff) I have the T-mobil insurance plan where I'll tell them the problem and they will send me a new phone, all I need to do is to get rid of that CotullaHSPL so that they wont find out that the phone has been messed with. So, My question is how do you recover to the original SPL, ((I've tried uninstalling the HSPL and it goes all the way to 100 but once the phone restarts and I go to bootloader it still shows me "CotullaHSPL"
Thanks,
Amir Najafi

its a reasonably common problem, , radio gets stuck, flashing appears to work but doesnt.
there are some out there threads about chilling it for half an hour, flashing certain test roms and the like, but there is no real answer to it. (not taht ive seen)
you could always try flashing a non tmous stock rom, (with a 51 radio) and hoping it takes enough to brick it completely, or go for the ten seconds in a microwave option, but ive always thoughtthe danger of exploding teh screen a bit much.

samsamuel said:
its a reasonably common problem, , radio gets stuck, flashing appears to work but doesnt.
there are some out there threads about chilling it for half an hour, flashing certain test roms and the like, but there is no real answer to it. (not taht ive seen)
you could always try flashing a non tmous stock rom, (with a 51 radio) and hoping it takes enough to brick it completely, or go for the ten seconds in a microwave option, but ive always thoughtthe danger of exploding teh screen a bit much.
Click to expand...
Click to collapse
I have accidental on the phone worse comes to worse, I'll just do that, I've heard of freezing it for half an hour, but would that really work?!

lol, no idea, ,
i can imagine a scenario where corrupt software is overpowering the hardware so much that it is failing, and that cooling it may allow it to work past its thermal limits just long enough to flash, , , but its more like an old wives tale, an urban legend really, doing somethng just because someone else did it and it worked i think, luck of the draw. 1 - freeze phone - 2 - into bootloader - 3 - sacrifice chicken - 4 - flash hspl - 5 - recite ' arr ay dee eye ohh ' over and over - 6 - flash radio.... hehehe.

samsamuel said:
lol, no idea, ,
i can imagine a scenario where corrupt software is overpowering the hardware so much that it is failing, and that cooling it may allow it to work past its thermal limits just long enough to flash, , , but its more like an old wives tale, an urban legend really, doing somethng just because someone else did it and it worked i think, luck of the draw. 1 - freeze phone - 2 - into bootloader - 3 - sacrifice chicken - 4 - flash hspl - 5 - recite ' arr ay dee eye ohh ' over and over - 6 - flash radio.... hehehe.
Click to expand...
Click to collapse
HA HA HA HA HA HA HA HA HA
That is the funniest sh*t I have heard all day.
Now as for the op's problem, if the phone feels hot after you try the flashing or after you leave it on for a while then you might have a processor that is slowly frying itself are causing itself to lose it's connections to the mother board because of the heat.
I know you said you tryiex everything but go get yourself a cheap 2GB SD card and format it even though it is new and the use it to put you ROM on e ergonomics time you try a ROM and try to flash via your SD card. If one ROM does not work delete it from the SD card download another and copy it to the SD card and try to flash it. One of them had got to eventually flash. Just be aware that if you flash any official ROM via SD card it will revert you back to SPL and you will have to reflash HSPL

I've tried the chilling thing btw, lol, it didnt work hahaha

Related

Good lie to tell T-Mobile for brickin my phone

Well, i ****ed up my phone.
Trying to bring it back alive failed, so I'm going to bring it
back to T-Mobile.
Does someone know a very good lie I can tell them, so I don't have to pay for the repair.
When i try to start my phone, i see a HTC splashscreen, and thats it. Normally it start with a T-Mobile splashscreen. Can they see i tried flashing my phone, or is that an assumption they make.
CCRDude said:
I don't think using bold letters and the clear word "lie" will help you a lot... you just highlight that you ask for illegal help
Maybe you should take a look at the bricked-devices topic for a chance to revive it?
Click to expand...
Click to collapse
I have spent the last 3 days 30 hours orso fixing my phone. Revive is something my dead baby won't do.
vayip said:
I have spent the last 3 days 30 hours orso fixing my phone. Revive is something my dead baby won't do.
Click to expand...
Click to collapse
enter the bootloader; try to flash a regular update from your provider to it.
vayip said:
Well, i ****ed up my phone.
Trying to bring it back alive failed, so I'm going to bring it
back to T-Mobile.
Does someone know a very good lie I can tell them, so I don't have to pay for the repair.
When i try to start my phone, i see a HTC splashscreen, and thats it. Normally it start with a T-Mobile splashscreen. Can they see i tried flashing my phone, or is that an assumption they make.
Click to expand...
Click to collapse
I did the same with my Vodafone (UK). I just told them I'd hard reset and this is all I can see on the screen (don't get stroppy etc).
Mine will be back Tuesday, warranty repaired.
Vod UK use an outside repair centre so will probably be the same as T-Mobile if you are in UK. Mine needed a new motherboard, but there is a bit of a shortage in the UK (too many bricks???). I guess it depends on the outside service centre contract whether they charge you or T-mobile (and maybe also because I had warranty and Insurance)..
Just go in and plead ignorance, but if they want to charge you, ultimately it was you that ****ed it and not them
Toast it in the microwave for 5 seconds!
boz said:
Toast it in the microwave for 5 seconds!
Click to expand...
Click to collapse
That's a new one - when car radio codes first came out they always said to put them in the freezer then stroke the chips legs to erase the cmos... never worked for me, but I'd probably get away with the microwave thing with 3 kids at home!!!
@ Olipro
If you mean the SD-card flashing, T-Mobile Holland doesn't have an update available. There is an T-Mobile Holland ROM available, but the image is older than the image installed on my phone. When checking the ROM in the white screen, it says not allow. I think i need ROM 1.21.114.3 from T-Mobile if I want to do the SD-card flash.
I only have access to the bootloader, I have bootloader 1.04, and I have access to KITL mode, but the Windows CE Platform Builder fix also doesn't work
@ ach2
I was thinking also something like that. That I hard reset my phone and now it's broke. I was also thinking something like I left my phone on the charger for the weekend, and when I came back I did a soft reset because it wouldn't go on and know I only see a HTC splash screen.
vayip said:
When i try to start my phone, i see a HTC splashscreen, and thats it. Normally it start with a T-Mobile splashscreen. Can they see i tried flashing my phone, or is that an assumption they make.
Click to expand...
Click to collapse
Can you think of a good reason whey the boot screen has changed from the normal T-Mobile one... just hope they don't turn on the phone. Did you try Olipro's suggestion?
@ Wam7
The T-Mobile splash screen is in the extended ROM. If the extended ROM is ****ed up like mine is, it probably goes back to its embedded splash screen, and that's the one from HTC. But thats not what I'm going to say, I'm going to say how should I know.
If I remember correctly a guy has managed to dump the ROM from a Hermes and flash it to the phone... saw a thread somewhere here. If that's the case then you should just need a ROM from a fellow dutch T-Mobile owner with the newer ROM. I take it your phone is not SuperCID
vayip said:
@ Olipro
If you mean the SD-card flashing, T-Mobile Holland doesn't have an update available. There is an T-Mobile Holland ROM available, but the image is older than the image installed on my phone. When checking the ROM in the white screen, it says not allow. I think i need ROM 1.21.114.3 from T-Mobile if I want to do the SD-card flash.
I only have access to the bootloader, I have bootloader 1.04, and I have access to KITL mode, but the Windows CE Platform Builder fix also doesn't work
Click to expand...
Click to collapse
if you have 1.04; run the RUU on your computer; you will get a "Vender ID Error" immediately ignore this and run the updater AGAIN (do not touch or unplug your PDA) after doing this a second time it will begin to flash
vayip said:
Well, i ****ed up my phone.
Trying to bring it back alive failed, so I'm going to bring it
back to T-Mobile.
Does someone know a very good lie I can tell them, so I don't have to pay for the repair.
When i try to start my phone, i see a HTC splashscreen, and thats it. Normally it start with a T-Mobile splashscreen. Can they see i tried flashing my phone, or is that an assumption they make.
Click to expand...
Click to collapse
seriously this is why MS and Carriers HATE us
Olipro said:
if you have 1.04; run the RUU on your computer; you will get a "Vender ID Error" immediately ignore this and run the updater AGAIN (do not touch or unplug your PDA) after doing this a second time it will begin to flash
Click to expand...
Click to collapse
I did what you said. I connected the phone to my laptop in bootloader. I started the RUU from WMXL 0.20. My phone goes to the white screen and at 0% i get a message on my laptop the connection got disconnected. So i start the RUU again, but again the message my connection got disconnected.
So still working on a good lie.
@vayip: sounds like a problem with the USB on your laptop. Try using a different computer. BL1.04 will let you flash any OS provided your NAND isn't full of bad blocks. You're a long way away from returning your device to Tmo IMO.
On the new computer:
direct USB connect to rear port only no usb hubs
pc running windows XP
turn off screensaver/Powersave mode
close all other apps
hands off the computer for the 25 minutes or so that it takes
Sleuth255 said:
@vayip: sounds like a problem with the USB on your laptop. Try using a different computer. BL1.04 will let you flash any OS provided your NAND isn't full of bad blocks. You're a long way away from returning your device to Tmo IMO.[/list]
Click to expand...
Click to collapse
Does it matter if the phone is simlocked or not. My phone is not SuperCID.
The strange thing than is, i have 2 laptops. Doing the upgrade don't work on both.
Will try a normal pc then. Maybe more luck.
Follow Oli's advice about retrying the update if you get an initial vendor ID error. BL1.04 will flash any rom without SuperCID due to a bug.
You might want to jump in with mtty first to see if your NAND is full of bad blocks. If it is then your device is toast fttb.....
spiritofseth said:
seriously this is why MS and Carriers HATE us
Click to expand...
Click to collapse
I completely agree! If you ****ed up your device, than you should have the courage to stand up for it and if it was not your fault, than just tell them the truth! But suggestions like "put it in the microwave for 5secs".... come on
And just a small hint: If you (for example) really put it in the microwave, than you'll better pray that no technician ever analyses your device - if so you could get into serious trouble, mate.
Btw, if you microwave it, you probalby need a new microwave too.
Edit: And i dont think its warranty would cover "I just put my Phone in there"
"So still working on a good lie."
Doesn't breaking your phone through your own actions and then getting it repaired/ replaced for free by telling lies make you a liar and a thief?
I trashed 8525, and that sucks, but it was my fault so I have to pay for it.
In my adventures flashing Roms, I've only bricked 1 Hermes (Cingular 8525). I actually told the local Cingular shop that I broke it 2 weeks after I bought it. The manager told me to bring it in and she replaced it under the 30 day in-store return policy. I was suprised because I had caused the bad NAND Block problem on the device but she said that since I was able to get an official Cingular Rom flashed onto it and it booted into WM5 (just wouldn't do anything because of memory errors).
Now I also have a very good working relationship with this store. I've gotten a phone about every 6 months from them over tha past 2 years and have given them some great info regarding WM5 devices (reccomendations on screen protectors, software & cases etc). I have 3 lines (2 with Data) and even if they don't know me by name eveyone in the store knows me by reputation.
Tomorrow I will have my spare Hermes (also 8525) so we can begin experimenting with getting some additional storage memory without risking bricking my primary phone.
The way I see it, we are taking a chance when we modify our devices.
I've had to return 2 Wizards for Warranty replacement to Cingular, both were CID Unlocked but the problems were unrelated to flashing Roms (One was because the touch screen developed a dead spot the other was because of Radio hardware issues).

Experiment that brings bricks back to life.

Okay today I intentionally bricked my phone. Not once, not twice, but 6 times with three bad ROM's (long boring day) and pulled the USB during the flashing at around 20%-95% as well as other no,no's
The experiment. To see how fast, and what I would use to unbrick it. Now being stuck in an all white screen or bootloader might bring fear or tears to some, but what I discovered is probably the best and easiest way to get your phone back to life in a relatively short amount of time.
If this has been covered before or mentioned elsewhere I didn't see it so I apologize if thats the case.
After I bricked each time I simply hooked up the usb cable to my pc. As you know when you are bricked or stuck in a loader Active Sync does not launch. What I found was that if you use a factory WM6 AT&T ROM it will still connect via usb and will flash said ROM 100% of the time restoring you're phone to a working state.
Now I did this 6 times today and it worked every time. I mean I really f'd with this second phone unplugging, Task Manager'd out during a flash, hard reset during a flash, etc. Every time it worked.
Hope this helps.
Well, you have been only lucky for 1 reason:
You always 'bricked' your device when it was in the middle of flashing the OS! This does not really matter as long as BOOTLOADER and CID are intact!
Do the same experiment but this time pull the plug at 15% and you will most likely fail to recover from that! At around 15% is the moment where the CID block gets written to the phones ROM.
Be very carefully that you do not 'brick' your device earlier because of in the state before 15% IPL and SPL are getting flashed! If you destroy the bootloader you can't do anything anymore!
If you are going to try that out please flash your phone first with the nbh from the CINGULAR WM5 (it is in the wiki) by using CustomRUU! CINGULAR WM5 has KITL enabled and you will be able to 'unbrick' your device by using the GUIDE in the WIKI.
I WILL NOT BE RESPONSIBLE IF YOU BREAK YOUR DEVICE TO A POINT OF NO RECOVERY POSSIBLE!
CID block is never written to the phone, it's just an area of storage inside the GSM chip.
however, if incomplete code is flashed to the GSM chip, the radio AT interface cant' boot... and then there's no way of talking to it, hence making it now dead.
On a different note, if the Radio Bootloader is in the middle of flashing (although I believe 0108 is persistent) and the connection is broken, you're now royally ****ed.
So, the GSM chip is not in the phone then?
<just kidding!>
However,
pulling the plug around 15% will most likely end in a brick! That was where I had my pc crash - thankfully KITL was enabled!
Tried again
Okay I did this at 12% and then at 16% (could not time it right for 15%) and I was able to recover. If I am just one lucky bastard, and this is highly against the odds, I would say don't do this on purpose like me.
My only point of the experiment was to see if I was to ever brick, at least I knew of one possibility that would recover it. And when looking at it like that it was a success.
Now that all is back to normal, I have HARD SPL.7 and have no issues.
ihavetinyballs said:
Okay I did this at 12% and then at 16% (could not time it right for 15%) and I was able to recover. If I am just one lucky bastard, and this is highly against the odds, I would say don't do this on purpose like me.
My only point of the experiment was to see if I was to ever brick, at least I knew of one possibility that would recover it. And when looking at it like that it was a success.
Now that all is back to normal, I have HARD SPL.7 and have no issues.
Click to expand...
Click to collapse
HARD SPL? try a different SPL and then try it again...
Oh yeah... Try to kill your bootloader too... And if it's like one of my devices
(HTC Charmer with a black screen... Only the power led lights up for half a second when I press the power button)
then try to flash your "holy" rom
eh, i don't understand why people call it bricking if only the OS needs a reflash
I wasn't clear. The phone was never hard SPL'd till after the experiment when I decided to lock the ***** up to keep it safe from doing more stupid stuff. The os flash wasn't all I crashed out on. I did this with this on purpose with the radio versions as well.
ihavetinyballs said:
I wasn't clear. The phone was never hard SPL'd till after the experiment when I decided to lock the ***** up to keep it safe from doing more stupid stuff. The os flash wasn't all I crashed out on. I did this with this on purpose with the radio versions as well.
Click to expand...
Click to collapse
then you are crazy
There are 2 possible explanations for your "luck":
Either the ROM you're flashing contains nothing but the OS and maybe the EXTENDED ROM in which case it does not really matter if you pull the plug because of your BOOTLOADER and GSM will remain intact or your FLASHING UTILITY 'ignors' the BOOTLOADER / GSM flash and writes only the OS and EXTENDED (which would have the same effect as case 1 when pulling the plug!).
However,
flashing an entire ROM takes a while, especially between 12% and 30% if you flash IPL / SPL / SPLASH / GSM / OS / EXTENDED - there is enough time to pull the plug at 15% because of it takes almost a minute until it jumps to 16% ...
I don't want to animate you to try that out because of sooner or later you will brick the device for sure!
Can you host the ROM file + flashing utility you used for your experiments, so, that we can download it and take a closer look?
ihavetinyballs said:
I wasn't clear. The phone was never hard SPL'd till after the experiment when I decided to lock the ***** up to keep it safe from doing more stupid stuff. The os flash wasn't all I crashed out on. I did this with this on purpose with the radio versions as well.
Click to expand...
Click to collapse
The world belongs to renegades and mavericks...
I did it with TNT's latest as well as VP3G 3.62
OK I'll bite where is WM6 AT&T ROM?
I have a bircked phone tytn (tried to unsucessfully unbrick around 50 times), not sure why or where it bricked.
Can reload but sticks at screen alignemnt EVERY TIME.
Was given as a challenge (failed so far).
If I could find this and it worked I be happy chappy long time.
If it works of mine it will work on anyone's.
Give it up dudes (or duedess if there is one out there).
Here is the secret. Use the bundled WM5 Cingular ROM from HTCs download site.
ihavetinyballs said:
Here is the secret. Use the bundled WM5 Cingular ROM from HTCs download site.
Click to expand...
Click to collapse
Do you have a link, filename or even better can post on Rapidshare?
Edit: btw, the moniker is hilarious!
rob8 said:
Do you have a link, filename or even better can post on Rapidshare?
Edit: btw, the moniker is hilarious!
Click to expand...
Click to collapse
He gave you the info you need. Go to HTC's site. Or use google.
K since i took the time to post this I might as well link it.
Go to the bottom of this page.
It is about time to give out a WARNING !!!
People, do not try to brick your device and trust in that you can recover from that by using the ROM from the HTC's website! This is not a magic tool and it won't bring your Hermes back to life if your device is really screwed up! There is nothing in the Cingular ROM what 'magically' does the trick! IHAVETINYBALLS was either just lucky or he isn't really bricking his device (consciously or unconsciously).
If you do not believe me ask other senior members with lots of experiences, such as OliP ...
However, I know there is no way of stopping fools to do foolish things, so, go ahead, destroy your expensive toy! You can always find a new one on eBay ... !
For all the retards who don't get it. (meaning the point)
To the dip**** retards who don't get the point. Like I said, I am probably just lucky. And like I said again, DO NOT try this unless your phone is stuck and ****ed, it was just an experiment. I have two 8525's one I bought as a refurb from AT&T for $99 and another one that was from an angry owner who threw it away at the AT&T store (as it was bricked and now "useless") and I pulled it from the garbage bin. Recovered it (just did a hard reset and put in a new battery and factory ROM and did a few experiments.
It didn't cost me anything and I did put a warning out there. The point of it all was that if you give up on bringing it back to life, maybe just maybe you should try this out.
Obviously if your phone is working just fine, don't do this or your a ****ing retard. Its meant for bricked or stuck phones as a possible recovery as it worked on said phone numerous times in various states of bad flashing and various types of ROMs.
This phone is now running vp3G 3.62 and now has HARD SPL.7, and Radio 1.54.07 and is running flawlessly.
So one mans brick/stuck frustration is making for an excellent spare / backup for me.
trying now
ok - have hybrid brick (no KITL, screwed CID and radio)
if everyone crosses their fingers at the same time maybe it will help???
will post back results!
Bugger
thanks for giving me hope! but alas...no good
hopefully someone else can figure out how to get back from a hybrid brick of no KITL and SPL 1.09

[Q] Is this still modable?

Okay I am looking at getting an HD2 used from a gentleman who says he's been having problems with it sticking on the "T-Mobile screen," which I'm assuming is the infamous "Stick Together" screen. From my knowledge he hasn't unlocked or rooted the phone or anything. Would flashing Android on it resolve the issue? I've dug through all the Q&A threads and used the search engine too but I didn't find any threads that were very helpful. Please help?
depends what he did, if he was playing around and task 29'd for instance, that would cause such symptoms, and can be resolved easily, but there are a ton of other, far less fixable causes too.
best thing, get the 3,14 t mobile rom from t-mobile.com, and flash it from sd card, (4gb or smaller, look up sd card flashing) if the flash takes and the phone boots, lovely, if it doesnt, stay away.
Okay I'll keep that in mind, he said something along the lines of it been stuck there. Like it doesn't progress at all. So if that's the case (I'm not a noob with roms and the like only with the HD2) would it still be flashable because I will have to set it up to be flashable period.
heh, theres the rub, you wont know till you try, it could be a corrupted flash that a new flash solves, it could be task29 left an empty OS, it could be a corrupted radio (more severe, not always fixable) it could be a hardware fault (overheating can cause same symptoms) stuck/unchangeable spl/radio will do this too, where flashing appears to happen but the phone sticks there, amd teh radio/spl didnt change, again, not always (very rarely, in fact,) fixable, its not an easy one to diagnose without seeing the results of a few flashes.
If you can, flash its stock rom from sd card(4gb or smaller, bigger cards wont work), that will be the big test, until that happens its all guesswork. You deff shouldnt hand over a fat wad of bills until such time.

[Q] How many times we can flash our phone?

How many times we can flash our phone? like custom roming,rooting,kernel etc
I guess till it dies ..I have tested almost every rom n kernel in xda nd android world.it ,over fifty to hundred probably almost for 2 months now and keep changing no problems till now ..
Sent from my LG-P500 using xda premium
alxbsl96 said:
How many times we can flash our phone? like custom roming,rooting,kernel etc
Click to expand...
Click to collapse
you can flash it as many times as you can before it get bricked(from BRICKED i mean it cannot be reapaired by any way....
As many times as you wish.
^ Not completely true. At some point, the flash ROM will die on you. It's a natural event when it comes to flash memory, although it should take a good number of rewrites for that to happen.
metalboy94 said:
^ Not completely true. At some point, the flash ROM will die on you. It's a natural event when it comes to flash memory, although it should take a good number of rewrites for that to happen.
Click to expand...
Click to collapse
Flash memory gets deleted if u delete everything so theres no worry for that, so its almost,
unlimited flash times, as told until u cant start phone (hard bricked)
not soft bricked, l0l
however hard brick is kinda hard, (at least as we often cant flash other rom's also if we do so it wont boot properly to prevent phone from hard brick, so its kinda a good safety)
I'm not talking about bricking here, rather about the physical resistance of the memory. Why don't you check out the back of the packaging from a USB drive or memory card, you will notice an attribute named "Maximum Number of Cycles".
The Optimus One has EEPROM
http://en.wikipedia.org/wiki/EEPROM
Taken from Wiki:
The manufacturers usually specify the maximum number of rewrites being 10 to the 6th power or more.[2]
During storage, the electrons injected into the floating gate may drift through the insulator, especially at increased temperature, and cause charge loss, reverting the cell into erased state. The manufacturers usually guarantee data retention of 10 years or more.
In other words, don't worry about it

Titan I, error code...

I am Johnny-come-lately to this debranding scheme. I am in America, but I chose to downgrade to the Euro Rom. Half of it was a success, the other half a failure. The four lines on the top all said okay. The installation that follows went about a line and a half and errored out with the line: wrong or improper sign, which I suppose could be short for "signature". Anyway when I rebooted the phone it got to the HTC screen and froze right there. Also it is in the boot loop. I tried reinstalling the Rom, but it gave the same results. I haven't been able to install SPL 2.05 either. I would like to move forward. But without an OS on the phone, nothing else recognizes it. I have been using the GC method with a single card reader and an SD card. I gave an 8Gb SanDisk flash drive a try but to no avail. I have also tried the various naming variations that are employed here and there. So what does the error message mean? What are my chances of going forward with the Cingular rom so as to finish HSPLing it. Or going back to a shipped or stock rom.
EDIT: I have access to the bootloader and SPL mode.
Thanks to all of you for your unfailing support to us neophytes.
Mercurybird said:
.. I gave an 8Gb SanDisk flash drive a try but to no avail...
Click to expand...
Click to collapse
Try to find non-SDHC card for gold-carding.
The best result is SD 1.0 — up to 2 Gb. That what I do always - no issues on any type of thumb drive or card with reader. Other guys here have also success with SD 1.1 which is up to 4 Gb. But 8 Gb will not work.
AndrewSh said:
Try to find non-SDHC card for gold-carding.
The best result is SD 1.0 — up to 2 Gb. That what I do always - no issues on any type of thumb drive or card with reader. Other guys here have also success with SD 1.1 which is up to 4 Gb. But 8 Gb will not work.
Click to expand...
Click to collapse
My card is HD and is a single card reader. I have a 1Gb and a 4Gb thumb drives. No luck with either of the sticks, but the HD card works. I'm going to take another path. I need the file; IMG_Eternity_Cingular_US_1.10.502.04_Radio_16.23.0 2.26_A… (Radio 16). I'll be able to move forward with that. Where can I download it at?
Mercurybird said:
My card is HD and is a single card reader. I have a 1Gb and a 4Gb thumb drives. No luck with either of the sticks, but the HD card works. I'm going to take another path. I need the file; IMG_Eternity_Cingular_US_1.10.502.04_Radio_16.23.0 2.26_A… (Radio 16). I'll be able to move forward with that. Where can I download it at?
Click to expand...
Click to collapse
AndrewSH is correct; I had your exact same problem but before I get ahead of myself; your device must read x310e after you install the Euro ROM; if it doesn't you're dead right there. You may be the exception but no high capacity card worked on the two Titans I did; however, I did successfully use a PNY 4 GB thumb drive; a red one in fact that comes in a two pack - red/blue thumb drives from Wal-Mart with a Y cable. I tried an 8 gigger; no dice. When you flash SPL205; you need to be really, really patience; you might say to yourself this is not doing a damn thing...give it a solid 30 minutes before you give it up for dead; out of the blue my device came alive about 15 minutes into it and successfully updated the SPL by saying bootloader ok and radio ok. I cannot stress enough how important this 2nd step is and have the patience to wait it out. You only format your thumb drive/micro SD card once; that's it; all you have to do after that is remove the 1st ROM and replace it with the baby ROM from SPL205. One more thing, if you haven't renamed the image do so...change it from ETERIMG to ETERDIAG...those 8 letters that's it. "diag" behaves differently than "img". And look, I realize this stuff makes for boring reading but read all the threads on HSPL not just the Titan; I'm not implying you read everything here...but specific to HSPL and Windows Phone 7, you bet...regardless of device. I don't want to sound like a grouchy old man here but it took me 4 days to get this right and I did a level of reading I've never done before here and I've been flashing phones a long time; there's no quick fix solution here and to be frank, it's a crap shoot; it may and again it may not work. I rewrote my own experience here...read it and do exactly what I say, no shortcuts. One day I will sit down and rewrite the darn thing in common sense language. I can't stand a tutorial written over my head and there are a few here who do great stuff but are thee worse teachers. It reminds me of a calculus teacher teaching 2nd graders..nope! I realize this is frustrating...join the party! Your phone will work after the initial flash to either the Cingular 1.10 or European 1.09 but it's like stepping back in time. And unless you're really living in a cave, there is a stock Microsoft ROM for the damn thing. Don't ask me how much sleep or the lack of sleep I got during those 4 days. There's no comparison between locked and truly unlocked; once you turn this beast loose there's no going back.
berrywr said:
AndrewSH is correct; I had your exact same problem but before I get ahead of myself; your device must read x310e after you install the Euro ROM; if it doesn't you're dead right there. You may be the exception but no high capacity card worked on the two Titans I did; however, I did successfully use a PNY 4 GB thumb drive; a red one in fact that comes in a two pack - red/blue thumb drives from Wal-Mart with a Y cable. I tried an 8 gigger; no dice. When you flash SPL205; you need to be really, really patience; you might say to yourself this is not doing a damn thing...give it a solid 30 minutes before you give it up for dead; out of the blue my device came alive about 15 minutes into it and successfully updated the SPL by saying bootloader ok and radio ok. I cannot stress enough how important this 2nd step is and have the patience to wait it out. You only format your thumb drive/micro SD card once; that's it; all you have to do after that is remove the 1st ROM and replace it with the baby ROM from SPL205. One more thing, if you haven't renamed the image do so...change it from ETERIMG to ETERDIAG...those 8 letters that's it. "diag" behaves differently than "img". And look, I realize this stuff makes for boring reading but read all the threads on HSPL not just the Titan; I'm not implying you read everything here...but specific to HSPL and Windows Phone 7, you bet...regardless of device. I don't want to sound like a grouchy old man here but it took me 4 days to get this right and I did a level of reading I've never done before here and I've been flashing phones a long time; there's no quick fix solution here and to be frank, it's a crap shoot; it may and again it may not work. I rewrote my own experience here...read it and do exactly what I say, no shortcuts. One day I will sit down and rewrite the darn thing in common sense language. I can't stand a tutorial written over my head and there are a few here who do great stuff but are thee worse teachers. It reminds me of a calculus teacher teaching 2nd graders..nope! I realize this is frustrating...join the party! Your phone will work after the initial flash to either the Cingular 1.10 or European 1.09 but it's like stepping back in time. And unless you're really living in a cave, there is a stock Microsoft ROM for the damn thing. Don't ask me how much sleep or the lack of sleep I got during those 4 days. There's no comparison between locked and truly unlocked; once you turn this beast loose there's no going back.
Click to expand...
Click to collapse
I know what you mean, I know what mean... I have been reading a lot also. But coming late to the process, where all the posted links are dead, has left us late bloomers at a disadvantage. Thank you so much! Yeah I read the threads, and the tutorials. They were not QUITE clear enough, But the one thing I noticed right off the bat was, a LOT of people failed to simply read those posts. I read them and I can tell you that every one of them made the picture clearer. The European file errored out with a "wrong sign" or some such. So I don't even have a Rom in my phone. So I couldn't charge my battery. I bought a great little plug-in charger that I can put my battery in and charge it. Then I discovered that in Zune update mode that it will charge. So I've been doing that. I still have boot mode and PLC mode- and update mode. So I can still flash. So here goes nothing!:laugh: Thanks a cool million!
berrywr said:
AndrewSH is correct; I had your exact same problem but before I get ahead of myself; your device must read x310e after you install the Euro ROM; if it doesn't you're dead right there. You may be the exception but no high capacity card worked on the two Titans I did; however, I did successfully use a PNY 4 GB thumb drive; a red one in fact that comes in a two pack - red/blue thumb drives from Wal-Mart with a Y cable. I tried an 8 gigger; no dice. When you flash SPL205; you need to be really, really patience; you might say to yourself this is not doing a damn thing...give it a solid 30 minutes before you give it up for dead; out of the blue my device came alive about 15 minutes into it and successfully updated the SPL by saying bootloader ok and radio ok. I cannot stress enough how important this 2nd step is and have the patience to wait it out. You only format your thumb drive/micro SD card once; that's it; all you have to do after that is remove the 1st ROM and replace it with the baby ROM from SPL205. One more thing, if you haven't renamed the image do so...change it from ETERIMG to ETERDIAG...those 8 letters that's it. "diag" behaves differently than "img". And look, I realize this stuff makes for boring reading but read all the threads on HSPL not just the Titan; I'm not implying you read everything here...but specific to HSPL and Windows Phone 7, you bet...regardless of device. I don't want to sound like a grouchy old man here but it took me 4 days to get this right and I did a level of reading I've never done before here and I've been flashing phones a long time; there's no quick fix solution here and to be frank, it's a crap shoot; it may and again it may not work. I rewrote my own experience here...read it and do exactly what I say, no shortcuts. One day I will sit down and rewrite the darn thing in common sense language. I can't stand a tutorial written over my head and there are a few here who do great stuff but are thee worse teachers. It reminds me of a calculus teacher teaching 2nd graders..nope! I realize this is frustrating...join the party! Your phone will work after the initial flash to either the Cingular 1.10 or European 1.09 but it's like stepping back in time. And unless you're really living in a cave, there is a stock Microsoft ROM for the damn thing. Don't ask me how much sleep or the lack of sleep I got during those 4 days. There's no comparison between locked and truly unlocked; once you turn this beast loose there's no going back.
Click to expand...
Click to collapse
Did I do it!? I did the files correctly. Here is what it says;
P139100
HSPL2.5. 160015.3(137079)
eMMC SND 15188MB
CotullaH(F:81,ID:1,V11,B:F8)
Radio-16.23.06.10
When the phone starts up, I still see the HTC logo in green. So did I do it!? EDIT: BTW, when I restarted it, I had about 10 updates waiting for me. They were all AT&T apps if I'm not mistaken.
Mercurybird said:
Did I do it!? I did the files correctly. Here is what it says;
P139100
HSPL2.5. 160015.3(137079)
eMMC SND 15188MB
CotullaH(F:81,ID:1,V11,B:F8)
Radio-16.23.06.10
When the phone starts up, I still see the HTC logo in green. So did I do it!? EDIT: BTW, when I restarted it, I had about 10 updates waiting for me. They were all AT&T apps if I'm not mistaken.
Click to expand...
Click to collapse
Looks good. Now you have to make a decision - what custom to flash to your phone. Most of the customs here need Radio ver 17. As for me - I was using ver 17 for almost a year but than I returned to radio ver 16 - better signal quality and faster network detection (but it's absolutely the local problem of your carrier and coverage - so try by yourself). I wanna say that ver 16 and ver 17 radios need different roms - because of different OEM part. So choosing your custom - pay attention on the radio ver needed in rom description.
Thanks AndrewSh- Thanks everyone!
AndrewSh said:
Looks good. Now you have to make a decision - what custom to flash to your phone. Most of the customs here need Radio ver 17. As for me - I was using ver 17 for almost a year but than I returned to radio ver 16 - better signal quality and faster network detection (but it's absolutely the local problem of your carrier and coverage - so try by yourself). I wanna say that ver 16 and ver 17 radios need different roms - because of different OEM part. So choosing your custom - pay attention on the radio ver needed in rom description.
Click to expand...
Click to collapse
Thanks! The finish seemed so anticlimactic. The struggle, the doubt, the fear, the frustration, the lack of answers, a clear path to move forward on. Now that that is over I'm feeling much better. When it came down to it, my SD card started dying. The thumb drives didn't work. Then out of the blue I put the second file on my 1Gb stick and it flashed like a champ. Then the last file flashed over the same easy way.
I'm thinking about the Deepshining Rom. I like the way it looks. I'm looking for substance, but I'm also looking for eye candy. I run Windows 7- glass, aero... Then I set up a Windows 8 machine for my wife at work. They took the glass and aero out of it. Yuck. The stock Titan Rom looks like Windows 8. Deepshining looks like it has a glass aero look to it. Vivid colors also.
Hey thanks so much for your patient, helpful tutelage for everyone in helping to get us going. I couldn't have done it without the myriad of genuinely kind people here. Thanks EVERYONE. THANKS A COOL MILLION!

Categories

Resources