Related
First, thank you again for this wonderful forum!
This is my problem:
I bought my X01HT AFTER Dec.2nd, to be precise on Dec.4th. Late afternoon I noticed it has dead pixel & considered returning it to the store and trying to ask for replacement...
I checked my X01HT version and it was the following:
ROM ver: 1.33.761.3
ROM date: 09/08/06
Radio ver: 1.14.00.10
Protocol: 32.50.7018.00H
Bootloader: IPL-1.01 SPL-1.06
Seems that I was lucky, and my ROM & boot loader was pre-Dec.2nd...
I didn't want to flash or tamper anything with my phone, since I really disliked this dead pixel, and was thinking about returning the phone. I went to SoftBank shop Dec. 5th and asked if it is possible to get replacement... Very bad mistake indeed!
There were no more X01HT available as replacements, as they were all sold out. Seems that I had bought very last one. They said they will look into this dead pixel issue and took my phone and said they need to 'send it to maker'. They gave some other phone as a replacement and said they will contact me next week...
So it happened, I waited (impatiently), and today they called... I went there all thrilled, and they finally gave me my phone back.
DAMN SoftBank! HATE THEM HATE THEM HATE THEM! (Sorry, I'm just human)
1. Dead pixel WAS STILL THERE... They said 'the maker' would not replace screens for just one dead pixel...
2. THEY UPDATED MY ROM with post Dec.2nd version!!! Now I'm the proud owner of the infamous unlockable phone! Here's version info:
ROM ver: 1.33.761.4
ROM date: 11/10/06
Radio ver: 1.14.00.10
Protocol: 32.50.7018.00H
Bootloader: IPL-1.01 SPL-1.09
I am just outrageous. I feel soooo stupid and bad. I should have known they could do this to me. Is it Friday 13th today or something?
Anyway, I have certain experience concerning flashing phones / PDAs, but now I'm not sure what to do!?! I really need SIM & CID unlocked phone.
I know people reported at this forum that new X01HT could not be SIM & CID unlocked because radio flash is not possible, because it seems to be read only... How come is it read-only, radio version is the same 1.14.00.10, and the only change is in ROM version (1.33.761.3 vs. 1.33.761.4) and of course bootloader is 1.09?
I am eager to start experimenting, try downgrading bootloader, flashing other ROMs, flashing only radio, or whatever... I just need some advice from more experienced users about what should be best thing to do (other than just sitting here and enjoying plain hate & disappointment). I was thinking of doing the same thing as julianfong done in this thread...
@Pof? Others? Any idea?
Or I should just wait patiently for some new solution of this issue, and use my (very limited) phone as most of the average users?
Thanks & sorry for this very long post...
yeah, just how unlockable is it? i mean... I am all too familiar with the new SE and Sharp DB2020 phones, but these are completely different.
is it unlockable because there is just no solution at the moment (a solution could be fairly soon)?
or, is it unlockable because 1.09 has DB2020-similar style of impossible to be cracked encryption...?
are the 1.09 models most likely permanently unlockable or what?
Seems that the ROM is somehow read-only, and nobody knows how to avoid this problem so far. Seems that it is possible to downgrade bootloader to 1.04 with some ugly tricks...
i read downgrade is possible using downgrade_spl file (i found one but it is dated July 2005).
but i also read that even with downgraded bootloader, the radio section is not changeable. is this the first time that there has been a device with this read-only problem?
Seems so... And it's here, on my table.
That certainly is a *****...Any ideas what falls under warranty for your phone?
Maybe there is a way to get it changed for a different reason. So at least you
could get rid of the dead pixel.
Also it might be worth shopping around. Possibly some other stores might still have the previous version, there are 1000`s of stores. if you hassle them enough, you might succeed.
Get it changed for other reasons?!? Maybe I should drop it down from my window and ask for a warranty... I really have no idea what to do, warranty and other stuff is all in Japanese, and I'm not really able to read them... I was reding Cingular's manual and there they said that they will not replace the phone if there is only one dead pixel... It's probbably in the japanese warranty as well... I wonder why did they took my phone at all that day?!?
I already checked more than 20 stores before I bought it! I was so happy when I had finally found it, but now, who knows...
Pixel dead or not, it's even more important for me if this phone is going to become unlockable or not at some point...
question is...since they didnt replace it, why did they do a rom upgrade?
They must have been bored.
I find it disappointing that a company wouldnt replace a display with a dead pixel, especially since it is a QVGA screen, where a bright pixel is way more bothering than on a 17" or 19" TFT. So maybe it might be worth dropping (if covered by warranty)
Basically for now, you might not be able to upgrade/unlock your phone.
But it might be just a matter of time since someone here (or elsewhere) comes up with a solution. If you still need to get the phone UI to display english, Asukal is currently working on a MUI upgrade for WM 5.
This way you can at least have english.
These are the questions that I asked to myself too many times... I'm usualy an lucky person, but this was very strange... The thing is that I am not able to read the warranty because it japanese (way too complicated japanese for me...). If there is someone who would like to read this warranty in details and check what rights do we, X01HT users have, please...
Until than, I'm waiting for solution... I know about Asukal's work, I'm eager to to try it too, even if I can manage ok with Japanese interface for now... What I really lack is the ability to unlock it (since I would like to use this phone when I travel back home, from time to time...)
Zgembo said:
These are the questions that I asked to myself too many times... I'm usualy an lucky person, but this was very strange... The thing is that I am not able to read the warranty because it japanese (way too complicated japanese for me...). If there is someone who would like to read this warranty in details and check what rights do we, X01HT users have, please...
Until than, I'm waiting for solution... I know about Asukal's work, I'm eager to to try it too, even if I can manage ok with Japanese interface for now... What I really lack is the ability to unlock it (since I would like to use this phone when I travel back home, from time to time...)
Click to expand...
Click to collapse
Im gonna get my wife to translate the warranty. I thought of the warranty procedure if you stuff up a rom upgrade. But i think they will flash your old phone again, and not replace it with a different one. Im not sure about that, maybe someone can fill you in on that.
I never had to get warranty for any of my phones, which is surprising, since i had 6 PDA phones.
You can also buy yourself an older version on yahoo auctions for around 45 000yen. then sell your at the same place...since its new, you might break even, but have the 1.06 bootloader
Thanks for good news! If you get it translated please write some summary here...
Basically, they dont cover anything...lol
If you drop it, water it, earthquake, dust, modify, sit on, step on, thunderstorm, missing details in warranty card (which is not filled out at all in my case...thanks SB), connect via USB and it breaks, all this is basically not covered by warranty... According to the warranty card included.
I dont know what warranty is for if major every day occurances are not covered.
ugly...
ugly indeed!
aquasesh said:
Basically, they dont cover anything...lol
If you drop it, water it, earthquake, dust, modify, sit on, step on, thunderstorm, missing details in warranty card (which is not filled out at all in my case...thanks SB), connect via USB and it breaks, all this is basically not covered by warranty... According to the warranty card included.
I dont know what warranty is for if major every day occurances are not covered.
Click to expand...
Click to collapse
The warranty covers manufacturing defects or breakage not normally expected by normal wear and tear only. Any actions by the user (dropping, sitting on, bricking, etc.) are not covered. Another poster on the forum had was refused warranty service because Softbank / HTC discovered that the user had flashed the ROM. One dead pixel is not a warrantable repair. If you want the old 1.06 ROM, you had better buy one on Yahoo Auction and sell your old phone. You should also mention the dead pixel. Under Yahoo Auction and Japanese mail order/online and secondhand trading law, buyers are well within their right to return a product if all of the conditions and defects are not noted before the purchase. The market is causing prices of 1.06 ROMs to be worth more than 1.09 ROMs, and a dead pixel will probably knock another 3000yen or so off the price, so you should expect to make a loss on this trade.
if you want to break it and try to get warranty on it .. i would suggest you microwave it ;-)
Not too long just a 1-3 sec's with it wrapped in a dry cloth and the unit turned on - It will cause some really strange faults
Disclaimer:- Do at your own Risk ..
Rob
How about doing some evil chanting and ritual sacrifice dance around my phone, and then pour some blood into my USB port? Would that be covered by warranty?
Maybe .. depends on the chants ...
Rob
what about wazz on the keypad from watching AV while in Japanese 410 at my University?
While walking a colleague thru his first WM6 upgrade last night, I happened to notice that my IPL had somewhere reverted to 1.00 Well, I just couldn't have that, and set out to re-up it to 1.04
Reflashed it to Vodafone OEM ROM, which for some reason also requires flashing any Radio Rom to get it past the Windows splash screen. Still showed IPL 1.00
Flashed it with the SIM-CIM unlock files, got the IPL up to 1.01
Next, still really wanting to get back to 1.04, and not being happy with a device that was running any and all ROMs I was throwing at it, I tried MTTY and tried to force 1.04nb on it, it wouldn't take it, but it didn't quit.
Then, about 4 am, I got really clever, took the 1.04.nb file, ran it thru nbhtool and made a .nbh file.
Put that on the SD card as HERMIMG.img, and fired up the bootloader.
The file flashed quickly, and gave me the Whoopie, it Worked message.
So, I removed the card, and did a soft reset. And that was the last thing the little guy ever did, reset to dead.
Good thing is our company has these things laying about like some companies have ball point pens, so getting replacement took just minutes.
Now I stick strictly to the guides, improvisation is best left for other folks.
This has been another in the continuing series "Noobs and our toys, how we break em".
... and you admit to the whole world that you are a total idiot?
... I'm convinced
You got balls kid, I'll give you that....
More Like This in the Wiki
Thanks for the excellent HOWTO
I'll try your procedure in a couple of months time when it's time to buy something more exciting (Toshiba Portégé G900, i-mate Ultimate 7150 or Nokia E90 -- which one shall it be?).
Actually you should have thanked him for the HowNOTTo!!
Not if you're looking for a good reason to buy another phone
simple said:
Actually you should have thanked him for the HowNOTTo!!
Click to expand...
Click to collapse
That's kinda what I was going for... don't get too cocky too soon, and learn from my dorkup. And no, I don't mind admitting I bricked one, I know that many of the senior guys must have too at some point, there are those that have, and those that will.
One thing though, in the 4 or 5 months I've had a Hermes, it has been amazing to see the evolution in tools and utilities that have evolved. Now I just have to keep straight in my noob brain which tools are cross compatible.
This is exactly what happened to my hermes... I sent it to be repaired 2 months ago.. and it is still being repaired I don't know how on earth this can take so much time. They've been saying they are waiting for some "parts" for 5 weeks now :>
Isn't it a bit strange?
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
I decided to play with the Debug Tool 3.2 and found all the Flash flags were set to 0. I saw there was a setting for Radio Flags. I set it to 8, wrote it, rebooted, just to see if there was any change in EDGE/3G capability (I have a Euro TP and I'm in the US). Since that didnt have any noticable effect, I changed the Radio Flags to 65535 , rebooted. The Phone showed the ToucHPro boot screen, then displayed the red version numbers and thats it.
I did a hard reset to reinit everything, no help. I reflashed the radio, no good either. Just reflashed the OS to DCS 1.5, still stuck.
Perhaps theres a way to reset the flags via MTTY in the bootloader, or through an AT command. If anyone has any ideas to try, let me know.
Edits:I just viewed the DebugToolAp.html and I think i know what I did wrong. Since I wrote a value of 65535 (16 bits, all ones), Im guessing the debug app properly converted it to hex and wrote 2 bytes instead of one, overflowing into the next location, where each 1 bit disables a piece of hardware. All 1's in that location would disable everything.
Now to figure out where that flash is and how to set those 2 locations back to 0's. I'm guessing I'll need a MFG SPL that has rtask enabled.
The Debug Tool calls the flash "PureFlash". Anyone know anything about it? Perhaps I can use JTAG to write to it? (I have a Wiggler)
Edit: running info 8 reports that I have 8 bad blocks, and based on similar symptoms posted on xda, the trick seems to be to run task 2a to fix the bad blocks, then task 28 to re-format the flash. But task 2a doesn't seem to do anything.
UPDATE: All the damage I did was repaired from remote by cmonex. I've learned my lesson, leave the tinkering to the experts!
dude if you want to brick your TP,instead of bricking it send it to me. i would be glad to accept.
lover said:
dude if you want to brick your TP,instead of bricking it send it to me. i would be glad to accept.
Click to expand...
Click to collapse
I'll keep that in mind next time I feel like wasting $1000
I can hear the interweb say "You dumb ass!".
rotohammer said:
I'll keep that in mind next time I feel like wasting $1000
I can hear the interweb say "You dumb ass!".
Click to expand...
Click to collapse
well kudos to you sir for bricking it and still keeping cool
maybe you can get some ideas in frankenkaiser-- it's connecting via radio SPL (OEMBSL) and I remember there is a read/write operation in there.
pfcsabre said:
well kudos to you sir for bricking it and still keeping cool
Click to expand...
Click to collapse
I'm not sweating it until someone who knows better tells me I done hosed it!
I still have a Kaiser and a Hermes, so I can still make calls
I'm browsing the the strings in HARD-SPL and see a lot of references to related bits, so I'm hoping theres a simple command in there to run to reset it.
rotohammer said:
I'll keep that in mind next time I feel like wasting $1000
I can hear the interweb say "You dumb ass!".
Click to expand...
Click to collapse
well attempting to brick sounds like wasting to me.
hehehe, if you want to brick flash a kaiser radio on raphael
I'm more of a dumb ass now
Update: True to the saying "A little knowledge is dangerous", I've succeeded in making matters worse.
Realizing task 2a wasn't working in HARD-SPL, I flashed back to the stock SPL, did the task 2a and then task 28. But now I can't flash HARD-SPL back, I just get "error 262". Flashing HARD-SPL from the SD Card just hangs on the loading message (never gets to the bar graph).
Since the CID is HTC_032 (Eastern European), I can't even try a SHIPPED ROM as I can't find one yet.
Running info 8 I only get checksums for SPL, not IPL. And I still have bad blocks.
I'm guessing the only thing left is to wait for a modified SPL that I can load into RAM, jump to it, and then try reloading HARD-SPL.
I'll stop fscking with it now, if I make it any worse then I know its JTAG time.
Send it back for warranty... if YOU cant boot, then THEY cant too and see that you have modified the rom
licht77 said:
Send it back for warranty... if YOU cant boot, then THEY cant too and see that you have modified the rom
Click to expand...
Click to collapse
Thats no fun I rather sit with it and wait for one of the big guns to advise.
I would suggest you pm cmonex , explain what you've done, and see what she recommends.
hey there, I'm checking this thread as per your PM.
classic case of reading BUT not reading enough. and also messing around more even after realizing something is wrong.. I hope you agree
I'll first try to correct all the wrong information mentioned here...
1) the debugflags have nothing to do with the 3G enabling.
2) task 2a is only useful for hermes, you're lucky it didn't kill the SPL totally. why do you think it is removed from hardspl otherwise.
3) task 28 is a plain hard reset, same as the button combo for hardreset. (BTW, many touch pro's have the same number of bad blocks, mine included, god knows why)
4) JTAG is not as simple as that. what devices have you jtagged before? any devices that have no publicly available documentation for it?
5) frankenkaiser will not work on a diamond/touch pro, because the normal USB interface is disabled in oemsbl command line and in dload mode. please no one should try setting any bootmodes in oemsbl command line!!! instant brick if you set 1, 2, or 3. and by brick I really mean brick, this touch pro right now can still boot SPL so not a true brick.
6) there is no IPL since kaiser came out. now radio bootloaders boot the SPL, not IPL.
7) if you have no shipped rom for this, you're in a much bigger trouble than originally even if you manage to unset the flags. btw there is a way to unset them, but the way I know of will only work with hardspl, we'll see if there is any other way. but again, your biggest trouble isn't the flags right now.
ok, i'll reply to your PM too and see how to go from there.
next time do not play around that thing what uu dot know deep enough....
rotohammer said:
I'll keep that in mind next time I feel like wasting $1000
I can hear the interweb say "You dumb ass!".
Click to expand...
Click to collapse
Next time you want to throw away $1000 consider donating it to a worthwhile cause. There are lots that need the money!
topspeclt said:
Next time you want to throw away $1000 consider donating it to a worthwhile cause.
Click to expand...
Click to collapse
I don't give to charities, only to hackers!
Man I really feel for you, Ive been there and done that only it was a Hermes I'd cooked and flashed a bad rom heart broken at the time.
ratcom said:
Man I really feel for you
Click to expand...
Click to collapse
I got what I deserved fair and square. Let that be a lesson to all the kiddies out there. There's still a .0005% chance that it an be saved. If not, then it becomes spare parts when I get a new Fuze
Let do a second chance, bro... give it back to the seller for warranty...
Another hope....
KChauJen said:
Let do a second chance, bro... give it back to the seller for warranty...
Another hope....
Click to expand...
Click to collapse
I thought about that, but no, thats not my style.
On the bright side, I flashed HyperDragon III Opal onto my Kaiser last night and I have to say its quite impressive. It's like having a Touch Pro, but faster! Cheers to Sakajati!
Just as cmonex said ..
but in my opinion it isn't bricked at all ... it's just waiting for the right spl and oemsbl to rewrite the config flag.
We'll have a look at it.
Cya,
Viper BJK
I remember GSLEON3 taking his Kaiser out of action with a task 2a for month's until Franken Kaiser came along.
Don't give up, I'm sure Viper and cmonex can get it sorted.
Ta
Dave
Well, after 9 months of lusting after this phone I finally got one. I wanted one with the intention of putting WP7 Mango on it and having a cheap WP7 phone.
I finally got one for $150 with money saved up from both Christmas and my birthday, but it had Android installed. I flashed an energy ROM on it, and played with that for a couple hours. I then looked at this thread:
http://forum.ppcgeeks.com/wp7-hd2/139787-how-flash-wp7-your-hd2.html
to see how to put WP7 on it. I downloaded "World Wide English (WWE) 1.66.405.2" since the thread says it has a .50 radio. Well, it seems it doesn't, because now I've got the same brick that happens when you flash a .51 radio.
No poweron, no tricolor screen, nothing. Occasionally I'll get a short chirp from the vibrator motor, but that's it. My computer makes no indication whatsoever of its existence.
Is my phone past DIY help? Would a cell phone repair store be able to do anything? Any clue how much they would charge for it?
Thanks a million
That's pretty unlucky, but also demonstrates why you shouldn't just blindly follow guides without some understanding of what's going on.
The rule for tmous isn't quite as simple as "..50.. radios only",, because 2.04.50 and 2.05.50 are also ..51.. radios.
Also, that rom you flashed usually comes with 2.06.51, so you probably got caught by a filename error, but that still doesn't excuse it properly, since had you read around the forum you would 1 - see the line " all non tmous stock roms WILL brick a tmous," (even without the radio, the rom wouldn't boot on your phone anyway) and 2. - you would have discovered that using hspl3 or Hspl4.would have done what you wanted without downgrading your rom.
so, unlucky, its bricked. JTAG will save it or new mainboard, and I'm betting you never dive in so quickly again!
(Before you start ranting about HTC and what a stupid phone, blah blah, remember it was t mo who asked HTC for a "special version",,, its all t mo's fault)
http://www.youtube.com/watch?v=oh_ex3VGHIM
samsamuel said:
That's pretty unlucky, but also demonstrates why you shouldn't just blindly follow guides without some understanding of what's going on.
The rule for tmous isn't quite as simple as "..50.. radios only",, because 2.04.50 and 2.05.50 are also ..51.. radios.
Also, that rom you flashed usually comes with 2.06.51, so you probably got caught by a filename error, but that still doesn't excuse it properly, since had you read around the forum you would 1 - see the line " all non tmous stock roms WILL brick a tmous," (even without the radio, the rom wouldn't boot on your phone anyway) and 2. - you would have discovered that using hspl3 or Hspl4.would have done what you wanted without downgrading your rom.
so, unlucky, its bricked. JTAG will save it or new mainboard, and I'm betting you never dive in so quickly again!
(Before you start ranting about HTC and what a stupid phone, blah blah, remember it was t mo who asked HTC for a "special version",,, its all t mo's fault)
Click to expand...
Click to collapse
I had no understanding of what the previous owner put on the device, I wanted to get it back to complete stock and try from scratch, mostly for the experience of doing it myself (something I enjoy doing). I don't know what amount of reading around would have saved me from a poorly-named file, but whatever.
Looks like I can get it JTAG'd for $40+sh, though I'm kind of hoping I can find someone cheaper on XDA-developers (this other guy is on eBay).
I guess that turns this thread into: Where's the best place I can send my phone to have it JTAG'd?
Ahh its not simply a 0 being a 1 in the filename.
for future reference the only stock roms you can flash will say TMOUS in the filename, and will never ever be rom version 1.x. , valid tmous rom versions are 2.10 2.13 and 3.14.
As for "what amount of reading..", did you find the dedicated tmous section of this forum yet?
(Not trying to be funny, just edjumacation!)