My unbranded TyTnII took a dump today, and reset itself to OEM condition, not so bad, except the data base was corrupt, so I would not configure a connection to my carrier (T-mo) .
So, I took it home, hooked it up to activeSynch, and brought up a previous sprite backup file to restore it.
Now it's a paperweight- it will start, display the three three install lines R-G-D with the Smart mobility splash, and that's it. I can't get it into bootloader, or anything else for that matter. Any ideas?
ttruex said:
My unbranded TyTnII took a dump today, and reset itself to OEM condition, not so bad, except the data base was corrupt, so I would not configure a connection to my carrier (T-mo) .
So, I took it home, hooked it up to activeSynch, and brought up a previous sprite backup file to restore it.
Now it's a paperweight- it will start, display the three three install lines R-G-D with the Smart mobility splash, and that's it. I can't get it into bootloader, or anything else for that matter. Any ideas?
Click to expand...
Click to collapse
If you get to the 3 color screen you are in bootloader my friend, do you notice the USB sign display in the screen? If you get that you can flash. I will recommend that you hard spl your device first (Please read the sitcky of how to perfom it, click under my TyTNII link)
Moved as not ROM Development..
Hard-Reset and do not use your backup as may be corrupted...
If that does not work then try and get into bootloader i know you said you can't but try again and flash stock ROM.
thanks for the move, and my apologies for the mispost- I realized only afterward I had put this up in developers.
I can't get to bootlogger mode- the phone hangs at the initial splash where it displays the SW versions of R D G. It will not move past this.
I hold the camera and on buttons, and push and hold the reset pin, but this is as far as it gets. I will sit here, so far for an hour, but will not progress further.
What am I missing? It's been some time since I've had to muck with it at all, so I've become unfamiliar with the tricks.
It's not bricked as long as you can get meaningful info on the screen. It sounds like you need to revisit HardSPL and put on a newer version. Then flash an appropriate rom.
All right,
Many thanks for the help! I flashed and manged to get the bone stock HTC WM 6.0 ROM loaded.
Now, at the risk of asking what could be considered a dangerous question (almost as bad as starting an oil thread on a moto list) what would be considered the latest and greatest ROM of them all? these days? I haven't been on this forum for quite some time, and I'm sure you all have been busy w/updates. I gave up when WM 6.1 came out, screwed up the GPS settings and made the camera even worse, so I've just stuck with my plain 'ol HTC OEM ROM.
Any suggestions?
ttruex said:
All right,
Many thanks for the help! I flashed and manged to get the bone stock HTC WM 6.0 ROM loaded.
Now, at the risk of asking what could be considered a dangerous question (almost as bad as starting an oil thread on a moto list) what would be considered the latest and greatest ROM of them all? these days? I haven't been on this forum for quite some time, and I'm sure you all have been busy w/updates. I gave up when WM 6.1 came out, screwed up the GPS settings and made the camera even worse, so I've just stuck with my plain 'ol HTC OEM ROM.
Any suggestions?
Click to expand...
Click to collapse
Yes, try them all and pick which one can meet your daily needs
having tried quite a few 'light and fast' types, i would say stick to more or less standard 6.1.
i spent a lot of time looking for cabs and then adding back in all the removed stuff i needed.
then get spb mobile shell on there and have a good looking phone.
6.5 never worked properly, esp messages, but a few other obscure probs.
my 2c
Related
ive posted before but really didnt get the answer i was looking for. all of this pocket pc smart phone stuff is new to me. i have the cingular 8125. my first pocket pc and it is all new to me. im trying to get the htc touchflo on my 8125. im like a baby learning how to walk haha as desperate as it sounds i need like a walk through of simple (non pocket pc savvy) how to install it all and everything like someone to hold my hand haha. sorry to sound so desperate and needy but any help is extremely appreciated.
First, we need to know a bit more info...is your phone locked or unlocked...stock rom, etc.
Secondly assuming everything is stock, you need to use the search button and search for lokiwiz, follow the directions explicitly.
Thirdly, search in the WM6 Wiz section for the rom that has the touchflo added...
I too was new and thought that if I said help I'm new, I'd be flooded with answers...I quickly discovered that the reasons the answers wouldn't come is because I didn't give enough info about my phone. A stock wizard is different from an unlocked wizard, which is different from an unlocked wizard running a rom from someones kitchen, and if your phone is a G4 then that's a whole different animal, etc...get the idea?? So to help, more info is needed about the phone itself. Power off, reboot...on the first page that pops up, there will be a few lines of info...copy those down with the numbers corresponding with it, then get back to us. "Knowing is half the battle" (famous philosopher=GI Joe). Hope this answer helps you.
thankyou.
i already unlocked my phone and went through the whole process im just not sure where to go from there.
ipl-2.26
spl-2.26
gsm-02.25.11
os-2.26.20.2
i just need to install the wm6 and toughflo im asuming i dont want to mess my phone up thats why im asking for help. thanks again.
AlexK
If you haven't flashed the T-Mobile OEM ROM yet and your IPL/SPL are still at 2.26, then you may not have unlocked your phone. I missed some of the reading first time around and this took me a while to catch, even though it was there in plain view. You may need to flash the Button ROM to get back to IPL 1.x as the lokiwiz only works with 1.x IPL.
Be carefull using the lokiwiz in the DOS window, and READ everything that comes up, especially notes like I/O error or unable to write, etc. . . If you try to flash a ROM and it appears that nothing has changed, then you're not unlocked, just going through the motions.
there is a thread here somewhere...unlocking for dummies or something like that...gives very detailed step by steps....follow this to the T. Then go to the WM6 threads section, choose the rom you want (download it), connect your phone via usb to the pc and fire up active sync. Run the loader to the rom you chose. The screen will go red and blue etc stripes and if done properly, a few minutes later it will say completed and reboot itself. DO NOT interrupt the loading process by disconnecting the usb before it's ready etc...re-install any third party apps or whatever, and you are good to go. NBo one can "hold your hand" you just need to try it until you do it. It's the only way to learn this stuff. Don't worry, I've thought I've bricked my phone so many times...MOST of the time, you can bring it back from the dead...unless you really fubar and rush things, don't read instructions properly, etc... good luck
Ok so I think I have some sort of problem here. Previous Kaiser started to act up (hardware keys and keyboard stopped working even after a hardreset) so I took the measures needed to get the phone back to factory stock conditions. Got the refurbed tilt in the mail today and of course tried to get it to the way my previous tilt was. Here is where I think I went wrong.
I placed JumpSPL1.56-KAIS on my phone and ran it and got the tri-color screen and what not. I think after this step I was supposed to install hardspl onto the phone but I forgot that step and instead installed a rom instead. The rom installed but it was the wrong one (Dutty's Hybrid NO.7b TouchFlo Final vs the one I really wanted: Duttys_New_years_Rom_2k8_[DualTouch_v2]). At this point I noticed my error because I tried to do the same thing again but when it got the rom% loaded screen it just stayed at 0% and froze.
From here I went through the motions to install hardspl properly but got the same results as above (freezing at 0%). Is there any way to correct this? I would really like to switch this rom (not that it's bad, it's actually a very solid rom but not what I want). Thanks in advance for any advice!
*Edit* Also for some odd reason I have no sound from the phone when getting a phone call (and yes I checked the settings and it's not muted).
*EDIT* Ok I'm really sorry for starting this thread. I figured the problem out. It wasn't even hardspl I was trying to install. Not sure what is was. I got the correct file and installed and updated the rom. Sorry again.
you did many things wrong, but atleast its working now. I would bet all you needed to do was reset phone/computer. as far as the sound issue, it is found everywhere. It is the result of an incompatible radio.
Been following this site for weeks and it is getting more popular eacha nd every time someone buys a Diamond phone, so keep up the good work.
I have finally decided to see what I can do with mine by upgrading the ROM and I would appriciate any advice you guys can give me as i am a totally newbie.
Here are the details:
It is on T-Mobile (UK)
Version -
1.37.110.3 WWE
06/20/08
1.00.25.03
Thanks
Hello there!
Not sure what you mean by upgrading the rom? Guess you mean applying a cooked rom?
A cooked rom is one thats been customised and is flashed over the top of your current rom, in your case probably a "stock" or out of the box/factory rom.
First thing to do in your case would be to upgrade the Radio. You may well need to run the HardSPL (I needed developer edition) and then apply the radio upgrade.
From then on, its up to you which cooked rom you run as they all have advantages and disadvantages. For example, im running the Diamond TLR rom as I don't like touchflo (i think its a gimmick that slows things down - drasticaly). Using this rom i'm able to uninstall touchflo and free up significant memory. This suits me down to the ground but not those who want to use touchflo!
Take a look at the wiki (mostly) and the Rom development sub-section of this Diamond section of the forums. As long as you follow the Wiki instructions on HardSPL and then use a rom specifically for a touch diamond, you should be fine.
Be very carefull though and DOUBLE check everything, one wrong flash program and you can destroy your phone.
Have fun!
p.s. Many people think that the factory 1.37.xx roms are the most stable, even more than the later versions. I'm running a TLR based 1.37something and I am very happy with it and never have to reboot my phone.
Got it....Its all here
Hi Lats... I've tried a variety of roms on my Compact IV and I have to say, me and my colleagues at work find that Swiftblades roms are pretty much as good as they come. He's now released version 5.0 and if you're still on the original T-mobile rom, then you'll notice one hell of a difference and improvement in speed and usability.
Go for it and don't worry if your concerned about warranty, there is a stock T-mobile rom floating around on the forum and instructions on how to return your Compact IV back to it's original state.
If you find the whole rom thing confusing, then take a look at this site:- www.modmydiamond.info It'll pretty much tell you everything.
Basically though, you'll find there are 3 phases to upgrading
1) HardSPL - In laymans terms, this pretty much opens the phone up for flashing roms. Most people seem to go for and recommend using Hard-SPL 1.40 Olinex Developers Edition-Unsigned. There are consequences to using an unsigned version, it means you could in theory download and install a dodgy untested Rom, but it's up to you to go for roms on the thread from reputable guys where you can see lots of other people have installed their tried and tested roms.
Once you've done this, you'll not need to do this again.
2) The Radio - This deals with the comms side of the phone, ie phone signal strength etc etc. It's pretty much been agreed by most people that v1.00.25.05 appears to be the best of the bunch.
3) Lastly choose a rom, there are half a dozen really good roms out there and many of them are down to personal choice. Many of them are customised too much for my liking. I chose Swifts as he pretty much keeps his clean and looking like a stock rom.
You'll only have to do the Hard-SPL once and probably the radio once, unless a better radio arrives. So once you've done all this, you can keep trying different roms without the need to do the Hard-SPL and radio all over again.
Hope this clarifies things a bit for you.
Good luck and have fun!
Thanks ever so much guys. I already feel alot more confident about this. Just one question... guide suggests the following:-
Manually enter the Bootloader by pressing the Power button, Camera button and performing a soft reset at the same time
Where is the camera button and it sounds as I need 3 hands to do this!
They're refering to the main round button below your screen in the middle of the 4 buttons, and yes you need 3 hands, but you can just about do it with 2
Let us know which ROM you upgrade to - I'm on the same ROM and radio as you are. Bit nervous about flashing the rom as my last phone (Vario II/Hermes) had to go back a month after I had it due to the screen alignment issues. After the warranty expired, I was flashing daily (lol) and yes, they do make a big difference.
I've got a copy of the UK Tmobile rom from this site, but cant remember the page now or what i typed in to get it... will try again later. It's called "RUU_Victor_TMO_UK_1.37.110.3_Radio_Signed_Diamond_52.26a.25.09_1.00.25.03_Ship"
Lats said:
Thanks ever so much guys. I already feel alot more confident about this. Just one question... guide suggests the following:-
Manually enter the Bootloader by pressing the Power button, Camera button and performing a soft reset at the same time
Where is the camera button and it sounds as I need 3 hands to do this!
Click to expand...
Click to collapse
That is for last resort methods only...
Ensure you are connnected via activesync when doing any flashing, remembering to hard reset again after every flash,
Yeah, most definetly I will let you know but I think it will be over the weekend now. I had a quick attempt to get bootloader going, but it don't look easy. Phone just resets everytime and just reboots back to normal.
If anyone has any tips on which buttons I need to press first or if there is any easier way of doing this, I'm listening.
Lats said:
Yeah, most definetly I will let you know but I think it will be over the weekend now. I had a quick attempt to get bootloader going, but it don't look easy. Phone just resets everytime and just reboots back to normal.
If anyone has any tips on which buttons I need to press first or if there is any easier way of doing this, I'm listening.
Click to expand...
Click to collapse
If you want to flash any ROM - you dont need to manually enter boot loader to do so...
As I mentioned before.
just make sure you have active-sync running and working and the battery id over %50 charged.
I'll be doing this tonight
The Tmobile stock rom can be found here
http://forum.xda-developers.com/showthread.php?t=406327
Hi guys,
Well, I've searched the forum and get close...but no cigar. So, I'll go ahead and ask.
I have an AT&T Tilt, Flashed the 6.1 from XDA MONTHS ago, and have been running Slither's Cube...not even all the time...as well as the HTC Home Customizer.
Yep, that's it.
Well, I have purchased another Tilt with a busted screen (otherwise absolutely fine) for $30 and am waiting to afford a new screen for it...at which time I'll have a backup and then the Cooking and Flashing will begin in earnest!
But I digress. Here is the sequence of events, and where I am at now:
1) Went to hang up from a phone call (BT headset active) by pressing the "Hang Up" Button...no response from the phone.
2) Pressed the Power Button...no response.
3) Slid open the Keyboard...no response.
4) Held the Power Button...no response.
5) Dumped the battery and rebooted...AT&T Splash then Radio Info...stays right there. Screen will dim after awhile, but never goes out. Rebrightens when removing external Power.
6) Soft Reset...same result.
7) Only way to Power Down is dump the battery.
8) Removed SD and SIM...attempted Bootloader Screen
9) Bootloader DOES show up:
KAIS1*0
SPL-1.93.0000
CPLD-8
Serial
10) I don't remember if there was anything with "Serial"...like a number or such...when I looked at it last (when flashing 6.1) so that may or may not be significant. There's nothing there now.
11) My Radios show up as:
R 1.27.14.09
G 22.45.88.07H
D 1.62.00.00
I am avoiding Hard Reset or Re-Flash until I can at least figure out what happened...if anyone has any ideas...or find out that this is common and that's the best or only way to solve it etc.
Since I haven't found anything quite like this in the Forum, I'm presuming that it may not be so common and I may...or may NOT...be able to find a way back before going that path. As well, I really don't want to send it off for repair...although I have insurance and coverage through Hawk (our AT&T Provider) that would be reasonable for repair ($35) but perhaps inordinate for rreplacement ($175). I'd like to be able to resolve this myself, but not knowing what may be wrong leaves me only with Hard Reset and/or Re-Flash alternatives...if those will even work...so out goes the question:
Has anybody run into this or have any idea of why it happened or the BEST recourse to resolve it?
Thanks in advance for any and all info, y'all are awesome and I truly appreciate your help...
RAF
These phones freeze all the time. Software conflicts, too much running at once, and it just feels like screwing you when you need it most. And of course all of a sudden, the hardware just crashes and never works again.
It looks like a hard reset will solve your problems, unfortunately, unless you do regular backups, you will lose all your info.
Thanks denco7!
Well, this is the first time it has locked up that early in the boot...all others have been easily resolved.
Hard Reset is not an issue with Data...I do keep my phone (data) backed up and have most of my volatiles on the SD.
And, honestly, I don't mind having to reflash or reinstall my apps...at least not yet, once I start cooking my own I feel I'll get a bit testy when I have to 'start over'.
I should probably find a good full backup app to snapshot the whole phone, then just put it back on when things 'happen'.
I do have a full backup from December using the 'supplied' app, so it will at least have most of the tweaks in it.
I'm gonna do the Hard Reset and see if that clears this, but I must say I'm not that hopeful.
Not really an expert...not a noob either...but this technology is just not rocket science, and I can actually do that along with quite a bit more.
Don't ask me to write a driver tho...I respect anyone that has that kind of patience!
Suffice to say, this just doesn't "feel" like a resetable issue...but I'm game. I'll update once attempted.
Thanks again, see you on the other side...
RAF
Okay...no joy on the Hard Reset. Behavior has stayed the same. Kinda expected that tho...
Next stop, Re-flash the ROM. I'm gonna check on latest releases of 'Official' HTC ROMs...but if anyone has any suggestions I'm open.
I'm still hoping that someone out there knows what happened here, it would be helpful to know the 'why'.
Thanks again...
not so much a suggestion but a correction. You don't have a wm6.1 rom but actually have a wm6 rom because the radio you have flashed i.e. R 1.27.14.09
is a wm6 radio not wm6.1 and that radio is only compatible with the following roms:
AT&T 1.60.502.3
AT&T 1.61.502.2
AT&T 1.62.502.0
Q-Mobile 1.2 AT&T Version
(source for above info: http://forum.xda-developers.com/showthread.php?t=393182)
so make sure that your rom matches the radio you have. I would recommend that if flashing is not something new to you than go ahead and upgrade your rom and radio to wm6.1 rom and see if the issue presists.
hope this helps
first post you stated you have a 6.1 rom but your spl is for a 6.0 rom, either your not on a 6.1 rom or your on the wrong SPL and should HARDspl if your flashing custom roms.
Thanks Guys...
I had it in my head that I went to 6.1 when I flashed it last...went out and looked at the file and sure enough it was 6.0.
This is what happens when u have 7 kids, 6 female and 4 of those in college...I'm too broke to pay attention.
No not new to flashing, and when I can get home before 10-11p some night...or this weekend...that's my plan.
Looking for the best choice 6.1 to flash and attempt to bring it back, but still curious as to the behavior in the first place.
Thanks for pointing out my ADD, and all comments are welcome...
Hoping for the un-bricking soon...
RAF
Now I'm REALLY Currious...and Frustrated! A Little Help Please...
Okay,
So I flashed the latest HTC Factory ROM: AT&T Tilt Windows Mobile 6.1 Software (ROM Version 3.57.502.2 WWE).
I wanted to do something mild at first before taking too many big steps...'small steps Ellie, smal steps'.
Once the Bootloader was up with USB showing at the bottom, I was certain I would at least have a connection to the Phone.
Of course with no ActiveSync or recognition from the PC, I simply ran the EXE and ignored the one line about making sure ActiveSync had a connection.
The only oddity was that at 13%, the Phone went from the "% Screen" back to the Bootloader Screen for a few seconds then continued normally to sucessful completion.
When it rebooted, it stayed at the AT&T initial splash and now NEVER shows the Radio or Protocol versions...just the initial splash.
As well, it does not dim the backlight after awhile as it used to nor do I ever get a Power Light...just plain LOCKED.
There is also still no way to Power Down the Phone except for removing the Battery.
Although I've never used MTTY, I'm wondering if that is now my only hope...and am currious as to the proper procedure for this particular circumstance.
I'm still searching the Forum for MTTY uses and info, but I would be appreciative if one of the Seniors could point me in the right direction.
Also, if ANYONE knows what may have caused this glitch in the first place it would help me to determine the best recourse.
Thanks again in advance to all...
RAF
Rustafergi said:
Okay,
So I flashed the latest HTC Factory ROM: AT&T Tilt Windows Mobile 6.1 Software (ROM Version 3.57.502.2 WWE).
I wanted to do something mild at first before taking too many big steps...'small steps Ellie, smal steps'.
Once the Bootloader was up with USB showing at the bottom, I was certain I would at least have a connection to the Phone.
Of course with no ActiveSync or recognition from the PC, I simply ran the EXE and ignored the one line about making sure ActiveSync had a connection.
The only oddity was that at 13%, the Phone went from the "% Screen" back to the Bootloader Screen for a few seconds then continued normally to sucessful completion.
When it rebooted, it stayed at the AT&T initial splash and now NEVER shows the Radio or Protocol versions...just the initial splash.
As well, it does not dim the backlight after awhile as it used to nor do I ever get a Power Light...just plain LOCKED.
There is also still no way to Power Down the Phone except for removing the Battery.
Although I've never used MTTY, I'm wondering if that is now my only hope...and am currious as to the proper procedure for this particular circumstance.
I'm still searching the Forum for MTTY uses and info, but I would be appreciative if one of the Seniors could point me in the right direction.
Also, if ANYONE knows what may have caused this glitch in the first place it would help me to determine the best recourse.
Thanks again in advance to all...
RAF
Click to expand...
Click to collapse
If you cannot flash a 6.1 rom or install the correct hard spl I would not even attempt using MTTY. Go to the rom section of this forum. Look for "spl rollup thread" it is a sticky from DaveShaw. Pick any 3.xx hard spl's for 6.1 rom and download. Now download jumpspl and place it somewhere on your device other than your memory card. Now run jumpspl and follow the rest of the directions in that thread. After you installed the correct SPL find a 6.1 rom and flash your device. If your sound doesn't work change your radio to a compatible radio, which would be listed in the "ultimate radio thread" by alltheway.
These are the basics. Hope it helps.
Rustafergi said:
Okay,
So I flashed the latest HTC Factory ROM: AT&T Tilt Windows Mobile 6.1 Software (ROM Version 3.57.502.2 WWE).
I wanted to do something mild at first before taking too many big steps...'small steps Ellie, smal steps'.
Once the Bootloader was up with USB showing at the bottom, I was certain I would at least have a connection to the Phone.
Of course with no ActiveSync or recognition from the PC, I simply ran the EXE and ignored the one line about making sure ActiveSync had a connection.
The only oddity was that at 13%, the Phone went from the "% Screen" back to the Bootloader Screen for a few seconds then continued normally to sucessful completion.
When it rebooted, it stayed at the AT&T initial splash and now NEVER shows the Radio or Protocol versions...just the initial splash.
As well, it does not dim the backlight after awhile as it used to nor do I ever get a Power Light...just plain LOCKED.
There is also still no way to Power Down the Phone except for removing the Battery.
Although I've never used MTTY, I'm wondering if that is now my only hope...and am currious as to the proper procedure for this particular circumstance.
I'm still searching the Forum for MTTY uses and info, but I would be appreciative if one of the Seniors could point me in the right direction.
Also, if ANYONE knows what may have caused this glitch in the first place it would help me to determine the best recourse.
Thanks again in advance to all...
RAF
Click to expand...
Click to collapse
Wow! I think you missed the advice and wisdom given to you about NOT FLASHING a 6.1 ROM with the SPL for a 6.0 ROM...
Anyways, lets see if we can help... I don't think you are going to be able to flash a SPL, as you probably can't even get an active sync connection to copy over the files...
So, try getting into boot loader screen; you hold down the camera button and then press in the rest button and hold that until a tri-color screen appears...
Then tell us exactly what it says, just to make sure we know which SPL you have... Then I will post a link to the exact ROM you need to flash to hopefully bring her back to life.
If you are not able to get into boot loader, which wouldn't surprise me, someone else with more experience un-bricking will have to help.
Some Answers and Info...Still Confused
redbandana said:
If you cannot flash a 6.1 rom or install the correct hard spl I would not even attempt using MTTY. Go to the rom section of this forum. Look for "spl rollup thread" it is a sticky from DaveShaw. Pick any 3.xx hard spl's for 6.1 rom and download. Now download jumpspl and place it somewhere on your device other than your memory card. Now run jumpspl and follow the rest of the directions in that thread. After you installed the correct SPL find a 6.1 rom and flash your device. If your sound doesn't work change your radio to a compatible radio, which would be listed in the "ultimate radio thread" by alltheway.
These are the basics. Hope it helps.
Click to expand...
Click to collapse
pjcforpres said:
Wow! I think you missed the advice and wisdom given to you about NOT FLASHING a 6.1 ROM with the SPL for a 6.0 ROM...
Anyways, lets see if we can help... I don't think you are going to be able to flash a SPL, as you probably can't even get an active sync connection to copy over the files...
So, try getting into boot loader screen; you hold down the camera button and then press in the rest button and hold that until a tri-color screen appears...
Then tell us exactly what it says, just to make sure we know which SPL you have... Then I will post a link to the exact ROM you need to flash to hopefully bring her back to life.
If you are not able to get into boot loader, which wouldn't surprise me, someone else with more experience un-bricking will have to help.
Click to expand...
Click to collapse
Hi again,
Thanks to redbandana and pjcforpres for the responses...I thought I might not get anymore!
I'll start with pjcforpres,
First, my appologies if I have not been specific enough on my descriptions...I've been attempting to be more succinct (I'm not so good at that).
This was a Stock ROM Tilt, then I had flashed RUU_Kaiser_CINGULAR_WWE_1.62.502.0_radio_sign_22.45.88.07_1.27.14.09R2_Ship.exe quite awhile back...shortly after it was available.
I added Slither's Cube and the HTC Home Screen and Customizer and have run it that way since then.
Somehow, I got it in my head that I had flashed 6.1 but I was flat out mistaken...hence the comment in the earlier part of the thread.
Then we get to the #1 post in this thread...add some confusion and voila.
The ref'd 6.1 flash was also Stock...RUU_Kaiser_CINGULAR_WWE_3.57.502.2_radio_sign_25.88.40.05_1.65.21.18_Ship.exe...and I thought I read everything, incl that it replaces the SPL.
Durring the flash, it pauses @ 13%, the USB disconnect 'bing' sounds and the Bootloader screen reappears showing SPL-3.02.000.
Then, the USB reconnect 'bing' sounds, goes back to the % screen and then completes the flash successfully.
My Bootloader screen is now:
KAIS1*0
SPL-3.56.000
CPLD-8
So...did I miss something and screw up? Or was I on the right track?
And redbandana,
It did successfully flash 6.1, but it still doesn't start...specifically, get passed the initial AT&T Splash.
Although I had already thought of going to JockyW's HardSPL 3.29, I cannot 'see' the phone in XP and therefore cannot get JumpSPL onto it...so, no HardSPL (unless I missed something else in the threads).
It DOES however give me the USB 'bing' sound when I go into the Bootloader...but clicking on the "Mobile Device" icon in Windows Exploder leaves a 'blank' right pane.
Before your post, I had read up on MTTY and noted the DON'Ts...like DON'T use task 2a!...and found several threads with commands.
None of the info commands seem to fuction, like info 2, info 7 or info 8 so I don't have much 'info' there.
One of the things I tried was 'task 28' to format the thing in case there was some corruption...this was the response:
Cmd>task 28
Format start
Storage start sector=0xC2C0, total sector=0xF000
Storage start block=800, total block=960
Total Bad Block in CE: 1
Erase physical block from 1091 to 2032
formatstorage Bad block found: 1397
formatstorage Bad block found: 1398
si backup: Erase physical block from 2032 to 2048
Format end
So I looked for 'bad blocks' on the Forum and there are suggestions to contact JockyW and GSLEON3 for more help.
I haven't as yet done this thinking I can work my way through this by searching the Forum and monitoring this Post.
My searches for MTTY Commands have shown me that there are different Commands for different SPLs, and the info is way scattered and confusing.
It is becoming clear(er) to me that I have an issue that is not that normal...or at least not with an intermediate level 'fix'.
That's why I asked for more help in the right direction, I feel like I've hit this pretty hard and done alot of footwork on my own.
I also feel like I'm running out of options and may resort to bugging JockyW and GSLEON3...unless there are any more suggestions
PLEASE let me know if there is more info that I can provide to narrow this down, or some procedure to attemt, or an MTTY comand that will give us more info, or another search in the Forum for something specific I've missed...or simply some PFM that can be performed...and I'll be HAPPY to comply!
Thanks again...and again...for the assistance, my grattitude and appreciation out!
RAF
I am going to be short and swet for the moment... my computer crashed so I am solely on my phone until I work again around 2 central time USA...
Good news is that there is a chance without MTTY to get you running, and if not, those with the knowledge are very hepful and patient.
I will do the searches tomorrow for the stock ROM you should try, and give a walk through on how to flash using a micro SD card.
I am out for now, and will get back to you as soon as I can tomorrow.
Patient and Prepared
Thanks pjc...if we can fix this I'll vote for you
I sincerely appreciate the assistace, and PLEASE let me know if there's any research I can do to facilitate.
If you're willing, let me know if I took a wrong turn somewhere or if I did something to make this worse...I like to learn from my mistakes (I AM pretty good at those...)
I just got the new screen for my backup Tilt and I'll be swapping that out tomorrow (uh...today) sometime, so I'll have a reference phone soon.
Askew but relevant, I'm on day 12 of a nasty cranial muscle spasm and 3 days into meds for it...so we'll see if I can stay focused
Thanks again and in advance...
RAF...Tilted
http://www.htc.com/us/SupportDownload.aspx?p_id=67&cat=2&dl_id=94
Try downloading from here... it is the 100% official AT&T Tilt 6.1 ROM, plus upgrade tool.
This includes everything you need, and is probably what you flashed already, but it sounds like you had a bad flash or something...
Make sure your computer doesn't go into hibernate during this process, and that you don't have anything running other than the update program and activesync...
Also, make sure when you run the update program, you right click and select 'run as administrator' or 'run as' then in the menu that comes after that select administrator.
If you can't establish an activesync connection, or if you are using Vista, and thus no Windows Mobile Device Center connection can be established, let me know, and I will track down the ROM by itself and the Radio by itself and walk you through that.
This should be the easiest fix, though, so we will try this first.
Been There, Done That...I Think ?!?
pjcforpres said:
http://www.htc.com/us/SupportDownload.aspx?p_id=67&cat=2&dl_id=94
1] Try downloading from here... it is the 100% official AT&T Tilt 6.1 ROM, plus upgrade tool.
2] This includes everything you need, and is probably what you flashed already, but it sounds like you had a bad flash or something...
Make sure your computer doesn't go into hibernate during this process, and that you don't have anything running other than the update program and activesync...
3] Also, make sure when you run the update program, you right click and select 'run as administrator' or 'run as' then in the menu that comes after that select administrator.
If you can't establish an activesync connection, or if you are using Vista, and thus no Windows Mobile Device Center connection can be established, let me know, and I will track down the ROM by itself and the Radio by itself and walk you through that.
This should be the easiest fix, though, so we will try this first.
Click to expand...
Click to collapse
1] Yep, same one I have already flashed several times to determine if there was a pattern.
2] ActiveSync will not connect...remember from #1 in this post:
1) Went to hang up from a phone call (BT headset active) by pressing the "Hang Up" Button...no response from the phone.
2) Pressed the Power Button...no response.
3) Slid open the Keyboard...no response.
4) Held the Power Button...no response.
5) Dumped the battery and rebooted...AT&T Splash then Radio Info...stays right there. Screen will dim after awhile, but never goes out. Rebrightens when removing external Power.
6) Soft Reset...same result.
7) Only way to Power Down is dump the battery.
8) Removed SD and SIM...attempted Bootloader Screen
9) Bootloader DOES show up:
KAIS1*0
SPL-1.93.0000
CPLD-8
I've never gotten passed the initial AT&T Splash since then...no matter soft hard reset flash the 6.0 ROM that was already on it or this 6.1 version.
Only difference is when I flashed this 6.1 ROM, the Radio and Protocol Versions that normally pop up at the bottom in red no longer pop up.
It now stays at the initial AT&T Splash, no versions, and never dims the backlight.
The ONLY time my Laptop 'sees' the Phone is when I put in into the Bootloader I get the USB 'bu-bingk'.
MTTY can see it, and the ROM Upgrades see it and run successfully...but Exploder can't and neither does ActiveSync.
Just to clarify that I've been there more than once...
3] Well, that I have not attempted...but all my previous flashes have gone fine (I am the only user on my Alenware Aurora m7700...and effectively I AM the Administrator), so I'll attempt that...(see next).
I downloaded, overwrote and ran this 6.1 ROM again...I set this XP install with me as the only Administrator (only user other than Guest), and I want to point something out that may be significant:
The Screnshots below show that there's no info in the Current Image Version area, I click on 'Update' and get the 2nd one.
(okay, sorry I haven't attempted very hard to embrace multiquote or embed a screenshot yet )
But this has happened every attemp to reflash after the initial sequence of events. As well, the same events recurred during the flash as all attempts before:
Durring the flash, it pauses @ 13%, the USB disconnect 'bing' sounds and the Bootloader screen reappears showing SPL-3.02.000.
Then, the USB reconnect 'bing' sounds, goes back to the % screen and then completes the flash successfully.
So...did I screw up somewhere? I really thought I had a handle on the 'small steps' that I took..it was the 'next steps' that I was mildly trepidatious about.
My understanding and instincts point to the 'bad blocks' errors durring the MTTY 'task 28' format, but I can't find anything pertinent to 'do' about it in the Forums...other than contacting JockyW or GSLEON3.
I want to try SOMETHING on my own before I go bothering them with a PM...although I've read (and even learned) alot here recently on TOP of what I had already learned over the last 2½ years, I feel I've got to at least attempt something before begging for help that way.
Still, I haven't found a path to get this basal into the core of the phone to noodle (safely mind you) around and become more adept so that I can solve these issues on my own...and it may be time to capitulate.
Let me know if you've spotted an error on my part...something I did or didn't do...or if there's another path I should take or search in the Forum I should look up.
Thanks ton again...and my appologies to all for my un-succinct pontifications...
(S)tilted...RAF
I don't think you are really doing anything wrong on your part, it just doesn't want to flash right... I had you try the stock stuff again just to make sure it was a clean download, and a clean flash.
I am not sure if it is the SPL not matching the ROM, or the Radio... The MTTY commands do indicate a problem with something not flashing right to the phone. Especially since that download has been recommended and successful so many times for people with a similar situation. I have done a fair amount of looking into this myself, and I have found a couple solutions:
1. Some people found success by flashing the same stock AT&T ROM 2 -5 times, and then it finally caught and worked right.
2. Others found luck by flashing a HardSPL, then new Radio, then new ROM.
3. They PM one of the greats... right now in the Kaiser area, JockyW is amazing! But is mostly focused on newer devices. I would recommend contacting mskip or DaveShaw. They have much more experience than I do, and should have a better idea of exactly what those block errors mean, and the solution....
If I were you I would try one last time doing a hard rest, you may need to hold down the 2 soft keys and the rest button extra long to get it to register... I would also try flashing that same upgrade 1 last time, followed by 1 last shot at a hard rest. If you still have the same stuff going on, I would contact those 2 guys and see what their wisdom says... mskip moderates the "NOOB flashing guide" thread and DaveShaw is a moderator for the Kaiser section in general.
Thanks pjcforpres...Contacting DaveShaw...Any Other Ideas?
Okay, one more time...and, no joy. Held the Soft Keys for 2 mintes solid for the Hard Reset, Reflashed, then another 2min Hard Reset.
I've resorted to sending DaveShaw a PM per the suggestion and will patiently wait for a reply.
In the mean time, if there's ANY other suggestions or a list of MTTY commands that run on the 3.56.000 SPL that can get info from the phone to help determine what the actual problem is or to correct bad blocks I'd be SERIOUSLY appreciative and VERY grateful.
Thanks to all who have responded, and in advance to all who may help from here...
RAF
A Little Updated Info:
Replaced the screen on my 'backup' Tilt, and flashed the RUU_Kaiser_CINGULAR_WWE_3.57.502.2_radio_s ign_25.88.40.05_1.65.21.18_Ship.exe ROM thaT I had flashed on the 'bricked' one.
It had the same behavior @ 13%, so I'm certain now that the flash went fine...I am even more convinced, with all of the events and symptoms to this point, that the issue lies in the 'bad blocks' reported durring the MTTY task 28 format.
I've left a PM for DaveShaw...and I AM patient...but if there is someone that may be more appropriate for this question I'd like to contact them as well. If anyone knows the right Guru, please let me know.
Thanks again to all...
RAF
Well I'm here at last sorry for the delay in getting back to you - I'm not sure how much I can help you though .
Can you post the output of "info 2" and "info 8" from an MTTY connection to your bootloader.
Also, can you please clarify: are you stuck at the bootloader (red/green/blue) or the splash screen (with R G D)?
Thanks
Dave
DaveShaw said:
Well I'm here at last sorry for the delay in getting back to you - I'm not sure how much I can help you though .
Can you post the output of "info 2" and "info 8" from an MTTY connection to your bootloader.
Also, can you please clarify: are you stuck at the bootloader (red/green/blue) or the splash screen (with R G D)?
Thanks
Dave
Click to expand...
Click to collapse
Wow man, THANKS for just bein here!
That's just it Dave, none of the info commands in MTTY seem to return anything (see #10). I've used MTTY: ver. 0.01 2001 and ver. 1.42 1997-2001 and both report literally nothing for info 2 info 7 or info 8...just another Cmd> prompt. However, (also in #10) I get to the 'bad blocks' ref running "task 28":
Cmd>task 28
Format start
Storage start sector=0xC2C0, total sector=0xF000
Storage start block=800, total block=960
Total Bad Block in CE: 1
Erase physical block from 1091 to 2032
formatstorage Bad block found: 1397
formatstorage Bad block found: 1398
si backup: Erase physical block from 2032 to 2048
Format end
Remember, the stuff in #1 of the thread happens and then I went through all this digging...took it to where I could and posted.
This wasn't a HardSPL fail or a bad Flash... I had BEEN running stock HTC 6.0 WWE with Slither's Cube, the HTC Home Screen and Home Customizer.
RUU_Kaiser_CINGULAR_WWE_1.62.502.0_radio_sign_22.45.88.07_1.27.14.09R2_Ship.exe (flashed 07/20/08)
This isn't a RUUNBH issue either, and I can get into Bootloader and I'm not 'stuck' there...currently:
KAIS1*0
SPL-3.56.000
CPLD-8
I can flash stock ROMs all day long w/no errors...flashed HTC 6.1 WWE on my backup Tilt to be sure the behaviors were the same, and they are exactly.
RUU_Kaiser_CINGULAR_WWE_3.57.502.2_radio_sign_25.88.40.05_1.65.21.18_Ship.exe runs FINE on the backup Tilt.
After flashing the HTC 6.1 WWE on the 'bricked' one however, there is no longer the R G D Radio Protocol info at the bottom of the AT&T Splash after the initial Splash...it was there before the 6.1 flash, and that's where it used to hang: Initial Splash, R G D, hang...backlight eventually dimed but never went out...battery dump only way off.
Now it hangs at the Initial Splash, NO R G D, NO backlight dim...still needs battery dump for off. It ACTS like it's lost it's damn mind...
I'm pretty sure I 'downgraded' back to the 6.0 mentioned above and went thru some similar steps to confirm, but I didn't write it all down and I'm way ADD so I can do that one again and record it all this time...unless that's a bad idea.
I very recently (like as I was searching I saw you had answered my plea...) found some other references to a MFG HardSPL that someone was thinking about working on to fix bad blocks, but I haven't read through it all yet. And, since Exploder and ActiveSync simply can't 'see' the phone, I'm not sure that I could get a HardSPL on the thing in the first place...'cause I can't get no JumpSPL on the phone itself...should've done that back when it was working I guess
I truly believe I'm at the 'needing guru help' level at this point, but if you see something I should do PLEASE point me that way and I'll dive right in. Also, like I've asked others, if you see something I did wrong or in the wrong order or whatever, please let me know that also...there's GOT to be something I can actually LEARN from this.
I warned you I tend to pontificate, but I hope that this clears up where I'm at. ANY help you can provide is fantastic and greatly appreciated, even if it's just to tell me to go somewhere else (I'm kinda used to that )
Thanks again, seriously...
RAF
In that case I have no idea. I think GSLEON3, jockyw2001 or cmonex are going to be the only one's who can help you.
Dave
Wouldn't open up a thread for this question but any custom ROM (RECENT EDITIONS) I've tried (NRGZ's, Sergio's, Ark's, Athine's and some others) for several days now have the "dead aka black" screen issue. Tried to find an answer in the original ROM-threads but haven't got any substancial responses. It seems like only few people have these issues. This would make me think the problem is my hardware (German Generic TP2) but the older ROMs of same chefs then run normal and without the dead screen issues.
Please any ideas, solution suggestions or experience share?
Thanks! Ibster
Edit: confirmed solution method described in post# 10 http://forum.xda-developers.com/showpost.php?p=5934002&postcount=10 . Thank you agent 47 big time for the tool you provided!
Ibster said:
Wouldn't open up a thread for this question but any custom ROM (RECENT EDITIONS) I've tried (NRGZ's, Sergio's, Ark's, Athine's and some others) for several days now have the "dead aka black" screen issue. Tried to find an answer in the original ROM-threads but haven't got any substancial responses. It seems like only few people have these issues. This would make me think the problem is my hardware (German Generic TP2) but the older ROMs of same chefs then run normal and without the dead screen issues.
Please any ideas, solution suggestions or experience share?
Thanks! Ibster
Click to expand...
Click to collapse
Is this the same as the "Sleep of Death" (SOD)? In which the phone won't wake from sleep/suspend state and has to be soft-reset?
If not, what's the symptom exactly?
MCbrian said:
Is this the same as the "Sleep of Death" (SOD)? In which the phone won't wake from sleep/suspend state and has to be soft-reset?
If not, what's the symptom exactly?
Click to expand...
Click to collapse
that's exactly what I'm talking about. I didn't know it was called the "sleep of death". I jusst have to softreset the phone all the time. The phone becomes just unuseable.
Ibster said:
that's exactly what I'm talking about. I didn't know it was called the "sleep of death". I jusst have to softreset the phone all the time. The phone becomes just unuseable.
Click to expand...
Click to collapse
i also experience it on my Tilt 2 AT&T unlocked, so i reverted back to Sense 2.1 Euro 1.86.401.0. any solution there, i bought mine from Negrielectronics USA.
Ibster said:
that's exactly what I'm talking about. I didn't know it was called the "sleep of death". I jusst have to softreset the phone all the time. The phone becomes just unuseable.
Click to expand...
Click to collapse
i also exprence it on my Tilt 2. is there any help out there
It's because chiefs have updated their XIP. Ask them to cook a rom for you with the old XIP from stock HTC WM6.5 Sense 2.1 rom.
Ach, that's just my theory based on my experience. I might be wrong, so keep that in mind.
I have a similar issue, but not exactly the sleep of death
A lot of times when I unlock the phone, Sense would not show up, only the taskbar and occasionally the bottom bar
Everything is responsive, the taskbar notification works, hardware buttons works, but not the sense part in the middle
This usually happens when I'm having an SMS conversation
I run this setup most of the time:
WM 6.5.x
Sense 2.5
HD mini lockscreen with Smartlock 2.0F or Lockdevice 1.6
Same here on the SMS black screen
ctbear said:
I have a similar issue, but not exactly the sleep of death
A lot of times when I unlock the phone, Sense would not show up, only the taskbar and occasionally the bottom bar
Everything is responsive, the taskbar notification works, hardware buttons works, but not the sense part in the middle
This usually happens when I'm having an SMS conversation
I run this setup most of the time:
WM 6.5.x
Sense 2.5
HD mini lockscreen with Smartlock 2.0F or Lockdevice 1.6
Click to expand...
Click to collapse
I just started having this problem with the newest Leo Cell Pro, I have not had it with any NRG or Deep Shinig ROMS though but I do like The cell pro details and the others are not without there faults. I like your screenshots and I can hardly wait for that new white theme to come out. I think it will make my phone so much better outdoors and enhance the Windroid look I am workin on.
Apical said:
I just started having this problem with the newest Leo Cell Pro, I have not had it with any NRG or Deep Shinig ROMS though but I do like The cell pro details and the others are not without there faults. I like your screenshots and I can hardly wait for that new white theme to come out. I think it will make my phone so much better outdoors and enhance the Windroid look I am workin on.
Click to expand...
Click to collapse
Yes....interesting that I've never had this issue on Energy's...my guess is he doesn't cook in the latest HTC SMS client which can be unstable at times
Are you talking about Elcondor's GTX theme? Yes that is a very awesome theme
I couldn't wait until 201x version comes out so I made my own Not as good as GTX but I'm half satisfied now
Apical said:
I just started having this problem with the newest Leo Cell Pro, I have not had it with any NRG or Deep Shinig ROMS though but I do like The cell pro details and the others are not without there faults. I like your screenshots and I can hardly wait for that new white theme to come out. I think it will make my phone so much better outdoors and enhance the Windroid look I am workin on.
Click to expand...
Click to collapse
like i mentioned in the the post#1 I had these problems with almost all recent (last two weeks) custom ROM releases, ROMs of different chefs. Because others or the majority of people don't have any problems with that I thought the reason must be hardware issues. yesterday I saw this thread http://forum.xda-developers.com/showthread.php?t=649191 opened by agent_47 where he provides a modified tool:
agent_47 said:
when u flash a rom, you are copying files onto the internal memory (like duh!) but if u repeatadly flash different roms, sometimes files from older version stays behind as when u flash a rom, you just copy and sometimes overwrite files without deleting the older ones. hence at times these older files may create bugs\instability. hardrest donot always fix it.so we use MTTY
Click to expand...
Click to collapse
Well I used it and have flashed to Sergio's Leo Cell Evo 6 and I can confirm that I haven't had any "sleep of death" issues, well still haven't and hope I won't have this "SOD" issue anymore. And when I tried this same ROM before I wasn't even able to make a proper configuration and set up the phone because the phone always froze or as soon the screen went off I wasn't able to activate it back without soft reset.
So maybe this is a solution and could help others who also are having this issue of "sleep of death".
Please if you try the tool from the mentioned agent_47's thread, let know us here because it will be very useful for the rest of the users to finally figure out "the dark side" of their phone and fix it.
Cheers, Ibster
Solution
I had this just recently. Funny side was that I installed an official new ROM from HTC which I just updated. Somehow the phone just didn't want to turn on and show the screen. So just like you guys said, hard-reset did the thing but just when the screen went off, same thing happened.
So what I did was wipe/clean or any other name. Practically did the installation of the rom again. Now, the device works normally and without any problems.
Maybe this happens because some old files of older ROMS sayed on the device itself and started making problems. Anyways, check this thread too, maybe it will explain something more: http://forum.xda-developers.com/showthread.php?t=649191
Or, final explanation. Our Rhodiums have soul inside their little chips and they just simply fu.k with us They tell us they're too tired of so many ROM changes.
I have also had this problem with my two latest official swedish roms (manilla 2.1 and 2.5) cant remember if I had it when I used 6.1. Now I use a cooked rom and still have the issue several times a week. The only thing I had done with my Rhodium before using cooked Rom was flashing hard spl for future use. If its not an inbuilt hardware/software problem from the beginning the only thing I can point at in my case is hard spl?
Originally Posted by agent_47
when u flash a rom, you are copying files onto the internal memory (like duh!) but if u repeatadly flash different roms, sometimes files from older version stays behind as when u flash a rom, you just copy and sometimes overwrite files without deleting the older ones. hence at times these older files may create bugs\instability. hardrest donot always fix it.so we use MTTY
Click to expand...
Click to collapse
back with my kaiser you always had to flash back to stock before going to a new ROM no matter what, for just this very reason...
could flashing back to stock be a 'best practice' that we as users should start doing to help with this issue?
I - have had some xperience with the issue in a few ROMS. Im a loyal flasher of Agent 47s masterpieces. And a month or so ago he had like 2 or 3 builds that had this issue. From what I remember he said that he thought it had to do with some sys evrybody was using to cook roms. and after her came out with this diagnosis and "fixed"(i dont know the technical part of what was fixed) this problem it has never happened since. But a good thing I would say to try is in Agents thread about 4 or so pages from the last page(maybe more or less) but close to the last page he posted a .zip file for this mitty fix. and you essentially flash this zip just like a rom then reflash which ever rom you had or a new one and ta da. Ive also heard of people reflashing a stock rom with results from doing so but from what Agent said is flashing a stock rom then back technicaly "shouldnt" do anything and to definately use mitty. But one of the other frequent valkyrie users that I chat with all the time Mcbrian who posted here on the first page has used the stock rom and did have whatever issue he had cured dont remember what that was tho.
UPDATE- Oh I guess that Agent has a thread for Tool29 so you dont have to search through his thread to find it.
I can confirm agent 47 method is working for me. I no longer have the sleep of death. But its only been half a day. I will report back in a few days.
aichemist said:
I can confirm agent 47 method is working for me. I no longer have the sleep of death. But its only been half a day. I will report back in a few days.
Click to expand...
Click to collapse
Great! I'm glad to hear your confirmation. I now on my side haven't had a sleep of death for three days on the ROM (Cell Leo V6) that previously, before I used the agent_47's tool, couldn't even start normally at all or had extremely many "sleeps of death". But I also noticed overall improvements even though the speed slows down but there are barely any freezes and stability is much better.
Cheers, Ibster
aichemist said:
I can confirm agent 47 method is working for me. I no longer have the sleep of death. But its only been half a day. I will report back in a few days.
Click to expand...
Click to collapse
I did tried agent 47 method at least three times this weekend. I did exactly what agent 47 instructed, flash Energy ROM 23547 with MaxManila = failed to initiated. Flash Tool29 again, reflash Energy ROM 23545 from MicroSD = Failed. Flash Athine OS XTreme = Worked, install MaxManila 3.0 on top of Athine OS Xtreme = Corrupted the manila display. Reflash stock ROM. Flash Deep Shining X.23544 = Worked. Flash Deep Shining X.23547 = Failed.
Look like I can get my phone to work but can't move on from now on! Any suggestion is greatly appreciated!
Thanks
kienkham said:
I did tried agent 47 method at least three times this weekend. I did exactly what agent 47 instructed, flash Energy ROM 23547 with MaxManila = failed to initiated. Flash Tool29 again, reflash Energy ROM 23545 from MicroSD = Failed. Flash Athine OS XTreme = Worked, install MaxManila 3.0 on top of Athine OS Xtreme = Corrupted the manila display. Reflash stock ROM. Flash Deep Shining X.23544 = Worked. Flash Deep Shining X.23547 = Failed.
Look like I can get my phone to work but can't move on from now on! Any suggestion is greatly appreciated!
Thanks
Click to expand...
Click to collapse
I'm not very clear about what you mean by failed. Do you mean you can't flash some of the ROMs or you get screens of death with them?
What I did was this: I took out the SD card. Ran the tool29 modified by agent_47 (see post 10 of this thread). After the tool finished cleaning all internal memory the phone went back on but got stuck in loading. I took the battery out of phone for few seconds and then put it back in. Then I connected the USB cable to the phone and started it in the bootloader mode by quickly pressing and releasing the switch button and then hitting the volume down. On the tricolor screen then it shows USB. Then I just flashed my ROM of choice normally with USB without need to flash from SD. I've done this several time with several ROMs without problems.
Ibster said:
I'm not very clear about what you mean by failed. Do you mean you can't flash some of the ROMs or you get screens of death with them?
What I did was this: I took out the SD card. Ran the tool29 modified by agent_47 (see post 10 of this thread). After the tool finished cleaning all internal memory the phone went back on but got stuck in loading. I took the battery out of phone for few seconds and then put it back in. Then I connected the USB cable to the phone and started it in the bootloader mode by quickly pressing and releasing the switch button and then hitting the volume down. On the tricolor screen then it shows USB. Then I just flashed my ROM of choice normally with USB without need to flash from SD. I've done this several time with several ROMs without problems.
Click to expand...
Click to collapse
Thanks for quick response. Yes. I did exactly what you spelled out in the message. i.e: Remove the memory card, Run Tool29, remove the battery, got into the bootloader mode, then flashed with USB connection. The phone went to the initial setup, I clicked the T-Mobile connection ....etc... then it restart - then stopped at "Launching HTC Sense...." This is = failed for me. i.e: Failed to clean the internal memory!
By the way, if the internal memory is cleaned, shouldn't the Start->Setting->Device Information->Software Information: Incoming Call & Outgoing Call reset to 0?
Thanks
kienkham said:
Thanks for quick response. Yes. I did exactly what you spelled out in the message. i.e: Remove the memory card, Run Tool29, remove the battery, got into the bootloader mode, then flashed with USB connection. The phone went to the initial setup, I clicked the T-Mobile connection ....etc... then it restart - then stopped at "Launching HTC Sense...." This is = failed for me. i.e: Failed to clean the internal memory!
By the way, if the internal memory is cleaned, shouldn't the Start->Setting->Device Information->Software Information: Incoming Call & Outgoing Call reset to 0?
Thanks
Click to expand...
Click to collapse
Your steps should be
1. Shutdown tp2..
2. Remove memory card( I also removed sim card).
3. Turn on tp2, connect through the computer through active sync.
4. Run task 29. Let it load flash, whatever it is doing until it actually reboots.
5. At this point, everything should be cleaned, you don't have a rom or radio anymore, so its blank, so you "pull battery out."
6. Put memory card/sim card back in. Flash radio through boot whatever menu. Soft reset it yourself. Pull battery out again.
7. Flash rom this time, and soft reset it again. Now rom should start setting up.
This shouldn't be rocket science.