I am upgrading to a 6800 tomorrow if all goes well. I have a 6700 right now and know about flashing, but my question is why is the titans process so much more complicated? On the 6700 I could just make the rom in the kitchen and go flashing away. The 6800 needs epst, specific bootloader upgrades and then specific radio files for a rom?
Am I missing something here? Is it just because of the gps?
nothing's complicated in that
ok first STOP saying that it's so easy to brick a 6800. The ROM and Kitchen that where build at beginning by DCD or any other where making phone possibly to brick.
Now the ROM, Kitchen, etc are made by Peoples who know what they do like or friend DCD. everything is so well explain on WIKI. I think after making so many test to brick my phones that if you BRICK your phone with a DCD ROM and others its because of a really really bad computer. Or you're try to brick it. I've try to flash ROM from other phone(no success-phone working), ....
the first time i've flash a ROM i was so afraid in that because Bricking a 600$ phone is making somebody mad. but i've discovered the case on my Mogul, my Vogue or my S720 that with Telus you just have to flash the Radio and the DCD ROM and soft reset and its done everything work SO EASY.
At now the way they builds there ROM or KITCHEN are so secure that its almost impossible to brick a phone.
TELUS
HTC Mogul
ROMCD 3.3.4
RADIO: 3.42.30 better time finding gps
HTC Vogue
ROM:Manilla Crystal based on a DCD VOGUE RoM
RADIO:3.41.00
HTC LIBRA (`GHOST PHONE`)
ROM:new telus wm 6.1 stock rom with some modif on .....
RADIO:.............. at now just getting a free way to acces cell tower for internet access IS WORKING, next step getting a way to access to make and receive calls.
Caferacer said:
I am upgrading to a 6800 tomorrow if all goes well. I have a 6700 right now and know about flashing, but my question is why is the titans process so much more complicated? On the 6700 I could just make the rom in the kitchen and go flashing away. The 6800 needs epst, specific bootloader upgrades and then specific radio files for a rom?
Am I missing something here? Is it just because of the gps?
Click to expand...
Click to collapse
I would imagine the biggest difference is that the 6800 has had many major software and firmware updates over it's lifecycle, and because when you make a massive change to the firmware (i.e. going from a 1.x or 2.x radio to a 3.x radio), enough gets overwritten that it's important to backup your settings, etc. Since 1.x and 2.x didn't have full GPS implemented, yes, GPS was a main reason for having to do the extra work. They also weren't written to support 6.1, so a new radio was required for that as well.
However, once this initial flash is done, all future flashes are very easy.
The SPL is required because HTC didn't want the phone to be easily flashable.
And it checked for signed image files. Signing an image without the private key is difficult so they cracked the bootloader to not require a signed image. This was a requirement to be able to flash a custom rom/radio.
BTC
It's my understanding that you could only brick your phone by installing a non-working bootloader. All other problems can be resolved.
Although I don't understand why the latest bootloader is non-working unless you've updated your radio. I don't think it's that complicated, but there aren't any clear and complete written instructions anywhere.
If flashing were easy, everyone would do it.
And then Verizon/Sprint, etc would have hundreds of thousands (vs probably just dozens) of customers calling or going to stores needing help fixing their screw ups.
That would make giving everyone else decent service an impossibility.
I'm all for the carriers making it difficult to flash phones.
guig54 said:
ok first STOP saying that it's so easy to brick a 6800. The ROM and Kitchen that where build at beginning by DCD or any other where making phone possibly to brick.
He didn't say anything about bricking it. He just asked the reason for it being so difficult. No need for the hostility. We're all here to learn and help.
Click to expand...
Click to collapse
guig54 said:
ok first STOP saying that it's so easy to brick a 6800. The ROM and Kitchen that where build at beginning by DCD or any other where making phone possibly to brick.
Now the ROM, Kitchen, etc are made by Peoples who know what they do like or friend DCD. everything is so well explain on WIKI. I think after making so many test to brick my phones that if you BRICK your phone with a DCD ROM and others its because of a really really bad computer. Or you're try to brick it. I've try to flash ROM from other phone(no success-phone working), ....
the first time i've flash a ROM i was so afraid in that because Bricking a 600$ phone is making somebody mad. but i've discovered the case on my Mogul, my Vogue or my S720 that with Telus you just have to flash the Radio and the DCD ROM and soft reset and its done everything work SO EASY.
At now the way they builds there ROM or KITCHEN are so secure that its almost impossible to brick a phone.
TELUS
HTC Mogul
ROMCD 3.3.4
RADIO: 3.42.30 better time finding gps
HTC Vogue
ROM:Manilla Crystal based on a DCD VOGUE RoM
RADIO:3.41.00
HTC LIBRA (`GHOST PHONE`)
ROM:new telus wm 6.1 stock rom with some modif on .....
RADIO:.............. at now just getting a free way to acces cell tower for internet access IS WORKING, next step getting a way to access to make and receive calls.
Click to expand...
Click to collapse
I never said it was easy to brick. I know from reading the wiki that a lot of things are recoverable, however compared to my 6700 it is more complicated.
I simply asked because, knowing myself, I like to research and know things beforehand. It cuts down on the 'oh sh*t' moments. Thats the reason I got a 6700 2 years ago, and the reason I upgraded to a 6800.
Thanks for the replies everyone.
Caferacer said:
The 6800 needs epst, specific bootloader upgrades and then specific radio files for a rom?
Click to expand...
Click to collapse
Stop right there -- just as the 6700 the potential steps involved for flashing are identical.
The differences are your sources for instruction.
It depends if you found a short-cut method that may leave people dangerously stumped in ignorance or a more comprehensive list of steps to cover nearly every contingency and prepare one with a foundation to recover to and options of what and how to flash. Myself and others have evolved the Wiki instructions to help everyone from n00bies to those recovering from flashing errors or incompatible OS/Radios ROM & SPLs. Comprehensive information shouldn't freak you out.
Keystone said:
Stop right there -- just as the 6700 the potential steps involved for flashing are identical.
The differences are your sources for instruction.
It depends if you found a short-cut method that may leave people dangerously stumped in ignorance or a more comprehensive list of steps to cover nearly every contingency and prepare one with a foundation to recover to and options of what and how to flash. Myself and others have evolved the Wiki instructions to help everyone from n00bies to those recovering from flashing errors or incompatible OS/Radios ROM & SPLs. Comprehensive information shouldn't freak you out.
Click to expand...
Click to collapse
I was reading the comprehensive wiki.
I didn't freak me out, just made me curious. I will be flashing either way
Well, flashed my 6800. Used latest DCD and the 50 radio that is compatible.
Can't see satillites in google maps, and I need to call tech support tomorrow because my phone apparently can't be authenticated. Everything I can see in EPST looks fine, and over air programming didn't work.
BUT, I can still call out. So it's a software issue that can be fixed. No brickage!
Otherwise it was painless. Very snappy now, although considering I upgraded from a 6700 just about anything would be eh?
Caferacer said:
Well, flashed my 6800. Used latest DCD and the 50 radio that is compatible.
Can't see satillites in google maps, and I need to call tech support tomorrow because my phone apparently can't be authenticated. Everything I can see in EPST looks fine, and over air programming didn't work.
BUT, I can still call out. So it's a software issue that can be fixed. No brickage!
Otherwise it was painless. Very snappy now, although considering I upgraded from a 6700 just about anything would be eh?
Click to expand...
Click to collapse
Use GPS Viewer to get a lock before using google maps.
Related
hey guys,
please don't get angry with me.
I am just a newbie about upgrading PPC roms. (I was using PalmOS devşces for 6 years until last month)
On my Imate Jasjam I just made a "radio rom update" ; it works fine...
But when it comes to OS updates I am total newbie.
Now I plan to upgrade to WM6 rom but I am too excited. I don't know if I am "ok" to do it.
Do you think the WM6 rom for HTC Hermes works fine on Imate Jasjam ?
(as it is only OS update it should be, but just to be sure)
Any problems that may occur with my Jasjam ?
One other question is:
I know that I have to hard reset before the update. But then, can I restore from my "SK tools" backup over the WM6 OS ?
And last one:
I see on the Radio ROM page that there is a newer radio rom which has "GPS enabled" mark. Also, I see in some of the member's signatures :
"RADIO ROM: 1.35.00.11 (Trinity GPS enabled)"
What does that mean ? Is there really a GPS in all Hermes devices ? Should I only upgrade to that rom to be able to use it ?
Btw, I am sure that most of this is already discussed in one of those very long threads but I am very excited and I wanted to ask it directly.
So please don't flame me...
Thanks for your help.
Hey, there's almost a tacit rule that you have to do a certain amount of reading to be a bona fide member of XDA! Some of your questions indicate that you have done very little... where do you get the idea that you have to hard reset before doing an update!? Start at the WIKI!!
I'll give you this one though... it's an extremely bad idea to retore from a backup after updating the ROM.
Wam7 said:
Hey, there's almost a tacit rule that you have to do a certain amount of reading to be a bona fide member of XDA! Some of your questions indicate that you have done very little... where do you get the idea that you have to hard reset before doing an update!? Start at the WIKI!!
I'll give you this one though... it's an extremely bad idea to retore from a backup after updating the ROM.
Click to expand...
Click to collapse
thank you.
however, I don't understand why it's a bad idea.
I have many apps installed.
To install them from scratch would be too difficult.
I don't think the places in the registry would be different in new rom.
am I wrong ?
my word of advice, If you're not willing to spend time, then upgrade the ROM is NOT for you.
btw, spend a day or 2 to read the WIKI & some of the stickies.
mrmrmrmr said:
thank you.
however, I don't understand why it's a bad idea.
I have many apps installed.
To install them from scratch would be too difficult.
I don't think the places in the registry would be different in new rom.
am I wrong ?
Click to expand...
Click to collapse
You are wrong. As others have said, do some reading before you take the plunge. You'll be glad you did.
And if you keep CAB files on your external storage card, reinstalling apps isn't all that difficult. Trust me, I reflash ALL THE TIME and getting up and running after a flash only takes me about 10 mins. Of course, I don't use half the crap everyone else uses; I mainly stick to a few utils and my corporate email.
Thanks for all of your replies...
Mostly they are discouraging ((
I have read many threads about the upgrade process and I couldn't understand why "upgrade the ROM is NOT for me"
It seems simple as running the exe on the PC.
is there something I missed ?
because if you run the wrong exe file from your pc you will end up with a really expensive paper weight
And you've indicated that you're too lazt to reinstall your favorite apps unless you can simply restore from a back-up.
Hint, experiment... I know which apps will work from my storage card without need a fresh install after Rom upgrade or hard reset.
concur: changing ROMs is like crack... once you start, you're hooked
Best to get proficient with the reloading process since eventually you'll wind up being able to do it in your sleep. I actually reloaded from a cold reset while working out at the Gymn once.... (capital G in geek here...)
thank you for all of your replies.
then I will wait some more to see if a more stable wm6 rom is available.
maybe kyphur can release one which is even better than his forst one
then I will hard reset my hermes (as I will need space on it for the update)
and then run the exe from my computer.
then I will have to install all of my apps from beginning.
I hope I don't lose data
Hey there, I've been anxious to flash my xv6800. I've been reading and searching extensively in the forums and FAQs and the Wiki (I don't usually post until my frustration is out of control). I've found some useful info here:
How-to for Wizard
http://forum.xda-developers.com/showthread.php?t=298613
but didn't see the G3/G4 designation on my splash screen (dead end)
How do I go about flashing to a DCD rom (or any custom rom for that matter)? Is there software I need to install on my comp and are there any steps specific to the xv6800 verizon firmware?
I would really appreciate any help. Thanks
I'm in a similar situation to you. I found this helpful guide the wiki here and it got me started. I also posted a similar plea on the DCD's Titan Rom thread so see if a response turns up there. Good luck and PM me if you find anything helpful. The title of your thread makes it a good place to post for the likes of us.
edit: I bet if this was made a sticky and some informed people posted some helpful info, us noobs would stay out of other threads asking for answers. (sound of kitten stuck in tree)
i need help too
well i got impatient and just downloaded dcd 1.6.10 and just clicked on the .exe without doing anything else. its currently doing its thing, hope it works!
You so crazy! I hope that works, but I have my doubts. The version you're referring to, 1.6.10, is for DCD's Titan kitchen. AFAIK, the kitchen's for cooking your own rom. Cooking is different from flashing as far as I can tell. I think you'll now find that you're ready to make your own rom on your PC, but that still leaves us unsure of how to prepare for and execute the actual rom replacement on the Titan. Right, wrong, Bueller?
it didnt work. it was stuck at 0% forever and then gave an error. i took the battery out and back in and am back to how i was before. no brick
i think i need some sort of bootloader. "re-locker" ? i cant find this when searching.
i thought dcd 1.6.10 is a rom for everyone, and kitchen is for those who want to make their own roms? im so confused.
http://forum.ppcgeeks.com/showthread.php?t=9927
excellent. Thanks!
fusQer said:
it didnt work. it was stuck at 0% forever and then gave an error. i took the battery out and back in and am back to how i was before. no brick
i think i need some sort of bootloader. "re-locker" ? i cant find this when searching.
i thought dcd 1.6.10 is a rom for everyone, and kitchen is for those who want to make their own roms? im so confused.
Click to expand...
Click to collapse
I tried to load dcd's and the official rom and the same thing happens to me, stuck at 0% then connection error.
Been trying to get some info from ppcgeeks.com but the forum has been down since yesterday.
What are we doing wrong?
Throw you a bone
OK, you guys sound real clueless (actually only a little more clueless than me!) so I'll help out. The ROM by itself is all ready to flash to your phone, like reinstalling a new operating system on your PC. The kitchen can be used to customize your own ROM, but I'd suggest you guys read up a bit more before going here. The garden variety ROMs that DCD and others provide is fine for now.
There are utilities on this forum to get you out of the bootloader screen if you get stuck (heppened to me last night). Search around a bit, and certainly read up a bit before flashing. These things are real complicated, but it takes a bit of understanding because the steps MUST be done in the right order, and many impatient folks dive in and get screwed, then complaign to the folks who gave them the files to begin with!
jorge_culv
Maybe ur misunderstanding what's happening.
Whenever I try to flash the device Windows Mobile Device Center closes both the screen on my Mogul and the window on the host pc never moves from 0%
Hope that helps
OK - I'm new to this also but have a question. I know data is lost so does that mean I need to re-establish all my email accounts and contact lists? I installed the cab to allow you-tube and bluetooth data to my tomtom. Also the Touch commander. Is all that gone and I have to redo that as well? Is there a suggested utility to back up as much as possible to restore? I sync with my company email via exchage. Right now everything is basically working fine so hate to take a chance.
Regards... Steve
US Cellular is notorious for not releasing updates for their phones unless it's truly broke. So it's unlikely an official 6.1 update will ever show up from them.
I know a few have successfully updated thru non-official channels by modifying other kitchens/roms.
Hoping someone who has done it can post what roms they used and what changes were needed.
Thanks,
BTC
If you can get a ROM dump, someone like DCD could probably provide you with a carrier cab. Otherwise, you need to write down a lot of your PST settings and restore them manually, including shared keys for data.
If you can manage to get a carrier cab, then you can do the same procedure as most people. If you want, look at the guide in my signature, the only thing different would be you need to get a carrier cab or the settings for your phone company.
Is there a tool that will let me make
A dump of my ROM? I would like the ability to go back in case I screw something up.
My main goal is to get the internal GPS working, and having 6.1 would be a plus, but not as big a goal.
Thanks,
BTC
Bump...
I am in the same boat at BTC.
My employer was with ATT and I had an 8525, waiting up upgrade to 8925/Tilt next month. They switched carriers to USC, and it was 6800 or a Q. I chose the 6800.
Thanks to XDA, long ago I unlocked my 8525, ran several custom ROMs on it, and had it doing everything but my laundry. Very cool.
But now again I have a stock phone. I was excited to have GPS onboard, but I am frustrated by this old ROM.
I am more than willing to do a ROM dump if you can point me to instructions on how to do it, and PM me or something with who to send it to.
THANKS!
I already have a USCC rom dump but I have been lazy. I will try and find time today.
USCC ROM dump: ftp://up.ppcgeeks.com/Titan/Users/ImCoKeMaN/USCCRomDump.zip
USCC carrier cab: http://www.dcd-roms.com/files/carriers/
Hate to clutter up the board, but just wanted to gush "THANK YOU" for doing this and so darn quickly! If this were Plurk, I would send Karma your way!
THANK YOU!!
I... I, I think I lo... lov... I think I love you! Thank you DCD, and thanms to all the rest for the helpful info! I spent 3/4 of my shift (protecting and serving), not "protecting and serving"; I've been looking for US Cellular (wretched... ewewwww!) specific ROMs and tutorials. So many of them in here, but was unsure as to which was appropriate. I'm going to attempt scrawnyb's tutorial with DCD's latest ROM... I hope I don't screw this up!
And how would I use these files?
DCD, is this a fully flashable format? (having to download it via my phone at the moment, so will take over an hour to finish...), however, with the proper bootloader and radio, could this be flashed over one of your roms and be fully functional?
Thanks,
BTC
did your spl unlock code work for you? mine isn't working for me how did you get you msl?
I used the registry tweak that creates a log file containing the SPL code, once I had that I was able to use QPST to read the phone programming, and reload it back once the phone was updated to a new BL, radio and rom. This kept all of my data settings, and all I had to do was run the carrier cab file.
BTC
I overwrote my DMU key with the DCD rom.. will this put me back online?
Still available?
After some rebuilding and starting over, I no longer have DCD's rom. Following the URL in this thread the page has reverted to GoDaddy. Is the USCC rom for the 6800 still out there anywhere?
TIA!
vdub144 said:
After some rebuilding and starting over, I no longer have DCD's rom. Following the URL in this thread the page has reverted to GoDaddy. Is the USCC rom for the 6800 still out there anywhere?
TIA!
Click to expand...
Click to collapse
If you are referring to his rom dump, it would only be useful to pull apps and settings out of the original rom. It's not flashable, mostly because of how old their radio/rom was. It is very likely that you would brick the phone if you were somehow able to flash this back.
I may still have a copy on my dead computer (You aren't the only one DCD!, lol), need a new HDD then I can see whats still in my archives of stuff.
BTC
Great and wonderful gurus...I think I dug myself into it. I was hoping my first post here would one with better news...but alas I am calling on your help.
I own a Telus P4000 (TITA100) and was keen on trying out dcd's new ROM. I did the following in the following order and now I have some unfortunate results.
1. Upgraded bootloader to 2.40 using USB instructions here:
http://wiki.xda-developers.com/index.php?pagename=TitanRecentHome
2. Thought 'what the heck' and tried upgrading to bootloader 2.47 using the microSD instructions at the same address.
3. Upgraded the Radio to 3.42.50.
4. A reboot brought me to the Telus screen so I thought I had done something wrong.
5. I reverted back to Radio version 1.40
6. I reverted the bootloader to 2.07 using the instructions here: http://wiki.xda-developers.com/index.php?pagename=TitanStockHome
7. I reflashed the stock Telus ROM.
8. Results are now that I cannot make any outgoing calls or data connections
(automated voice says I need to activate my phone) and my power key does not turn the device back on once it goes into 'hibernate' mode.
I am really hoping someone can help me out. I've been searching for hours to find the original Radio (1.32) and the original bootloader (1.04) so I can put things back to the way they were but I can't find anything.
Any help is well appreciated,
Ry
PS - Update - I tried the other method of reverting back to stock (via USB) and now the bootloader is 1.04 and the Radio is 1.32. BIG Steps in the right direction....
Okay...so most of the issues seem to have been resolved and I'll call Telus to re-activate my phone tomorrow but there is one remaining question:
Did I do anything wrong here and how can I continue on my quest to give this another whirl?
(I debated not posting at all...but I figure my conundrums may help someone else later)
Extra info
For you Telus users...found the last link...programming. I completely forgot about this and thank goodness I stumbled across this link thus making me feel completely stupid but nonetheless satisfied....
http://taiu.wordpress.com/2008/02/06/updating-my-telus-p4000/
I think I'm going to bed now...
I'm glad you got it to work. I just had to mention that I thought your title was vey clever
Inescapbl said:
(automated voice says I need to activate my phone)
Click to expand...
Click to collapse
Keep in mind, at least on Verizon, when upgrading your radio from a non-GPS radio to a GPS radio, the phone will require re-authentication. The A-Key will have to be given by your provider. When I called, I basically told them I had to do a hard reset. The tech on the other end said that every time I do a hard reset, I need a new A-key. NOT!(idiot)...
nitro66215 said:
Keep in mind, at least on Verizon, when upgrading your radio from a non-GPS radio to a GPS radio, the phone will require re-authentication. The A-Key will have to be given by your provider. When I called, I basically told them I had to do a hard reset. The tech on the other end said that every time I do a hard reset, I need a new A-key. NOT!(idiot)...
Click to expand...
Click to collapse
Actually, I've only needed a new A-Key once, and that was when I hard reset my device. However, when I got my phone, I upgraded the stuff before activating.
So yes, hard-resetting does (sometimes/always?) causes you to need a new A-Key.
And even then, I didn't call in; I did the whole online "activate another phone, then reactivate the 6800" trick to avoid dealing with terrible CS
nitro66215 said:
Keep in mind, at least on Verizon, when upgrading your radio from a non-GPS radio to a GPS radio, the phone will require re-authentication. The A-Key will have to be given by your provider. When I called, I basically told them I had to do a hard reset. The tech on the other end said that every time I do a hard reset, I need a new A-key. NOT!(idiot)...
Click to expand...
Click to collapse
I don't know if this A-key thing is true anymore. On my original phone I had to do an A-Key update twice. And both times was when I upgraded the Radio. After a while I stopped having to do them.
Yesterday I got a replacement 6800 (old one had bad charging port). I activated it got it working, and immediately put on SPL 2.47, radio 3.5.42 and DCD 3.2.5 (in that order)
I DID NOT have to call verizon for an A-key update.
Inescapbl said:
For you Telus users...found the last link...programming. I completely forgot about this and thank goodness I stumbled across this link thus making me feel completely stupid but nonetheless satisfied....
http://taiu.wordpress.com/2008/02/06/updating-my-telus-p4000/
I think I'm going to bed now...
Click to expand...
Click to collapse
Also take a look at some P4000 instructions I posted here.
http://www.howardforums.com/showthread.php?t=1413430&page=1&pp=15
I have never had a problem flashing my P4000 except for when I used a Sprint ROM to get an updated radio and let the customizations run. This made it so that I could not send text messages but everything else worked fine.
Here's how I fixed it:
- used the relocker to relock the phone and restore the original bootloader
- flash with stock Telus ROM
- change to 2.40 bootloader
- flash radio (didn't use the Sprint ROM this time, used SD card method instead)
- flash DCD ROM
- run Telus carrier cab
Since then I have updated to 2.47 bootloader, updated to DCD3.2.5, went to a lower version of the radio because I was having signal issues, and then just recently went to the latest radio version. I haven't had any problems other than that one I just mentioned above.
Even when you flash with DCD's ROMs the Telus splash screen will still come up as this is not overwritten by the ROM. This will only change if you use a flasher to change it or flash with another carrier's ROM (like Sprint for example).
Without a major scew-up, you should not have had to activate your phone on Telus after unlocking and a ROM update. I've never such an issue nor anyone else I know.
1. Upgraded bootloader to 2.40 using USB instructions here:
http://wiki.xda-developers.com/index...itanRecentHome
2. Thought 'what the heck' and tried upgrading to bootloader 2.47 using the microSD instructions at the same address.
3. Upgraded the Radio to 3.42.50.
4. A reboot brought me to the Telus screen so I thought I had done something wrong.
5. I reverted back to Radio version 1.40
6. I reverted the bootloader to 2.07 using the instructions here: http://wiki.xda-developers.com/index...TitanStockHome
7. I reflashed the stock Telus ROM.
8. Results are now that I cannot make any outgoing calls or data connections
(automated voice says I need to activate my phone) and my power key does not turn the device back on once it goes into 'hibernate' mode.
Click to expand...
Click to collapse
Inescabl, in all of those steps you failed to say when and where you upgraded to a third party ROM.... Within the first two I already see a point of concern where you stated you unlocked to 2.40 and then your next step being, ''what the heck' and tried upgrading to bootloader 2.47 using the microSD instructions. How did you get into the OS? Were you still on the stock radio and ROM?? You then stated that you flashed to the latest radio, but of course a reboot would only bring you to be stuck on the Telus screen if you'd not bothered to also flash to an appropriate ROM.
From what you've described, you decided to go a bit your own way, and did not pay close enough attention to the stated steps and problem solving that I wrote in the Wiki.
I'm glad that it all worked out for you, but this should be a warning to others to not rush into things without first being clear upon what the Wiki's guides and troubleshooting offer.
Keystone,
Correct. I should have used the phrase 'reprogram' by dialing *22803 for Telus users after you reflash your phone. 'Re-activate' was the wrong term.
Second, you are also correct in that my steps failed to say that I upgraded to a third party ROM and that was what I missed. On my second attempt I did upgrade to the third party ROM and all systems are now 'go'.
Third, when I said 'what the heck' I meant that since I had successfully upgraded the bootloader to 2.40 using USB I thought I'd try upgrading to 2.47 using the MicroSD method. You don't need to go into the OS to do that but merely need to get back into the bootloader screen by pressing POWER-CAMERA-SOFT RESET.
The difficulty I had resulted from the fact that the wiki is not clear that in order to install the latest ROM you need to be connected to the phone via USB and on the bootloader screen on your phone. This is where I was slightly confused and didn't understand where to go next. Perhaps you could update your instructions a little? It's funny how one person can read something and think one thing and another can read it and not see what you were thinking!
One final note. With respect to these statement: "You then stated that you flashed to the latest radio, but of course a reboot would only bring you to be stuck on the Telus screen if you'd not bothered to also flash to an appropriate ROM.From what you've described, you decided to go a bit your own way, and did not pay close enough attention to the stated steps and problem solving that I wrote in the Wiki.I'm glad that it all worked out for you, but this should be a warning to others to not rush into things without first being clear upon what the Wiki's guides and troubleshooting offer.
Though I appreciate your response I didn't really care for this final note where you took the opportunity to jab at my personal character. I did take the time and did pay attention and did not 'go my own way'. There was just that one step that I mentioned that was confusing. My post was not a personal affront to your wiki and I do appreciate it as do many others. Instead this is perhaps an opportunity to make your wiki even better!
Thanks,
Ry
_____
unL33T,
Thanks! That's a great nutshell version for the upgrade.
Ry
Inescapbl said:
Though I appreciate your response I didn't really care for this final note where you took the opportunity to jab at my personal character.
Click to expand...
Click to collapse
I never did anything of the sort! Please, have better respect for other members here and take better care in what you read:
Keystone said:
From what you've described, you decided to go a bit your own way, and did not pay close enough attention to the stated steps and problem solving that I wrote in the Wiki.
Click to expand...
Click to collapse
I was not sure what you had presented in the OP and was trying to clarify what had occurred to cause your problems. In many such threads newer people will read and get confused, and that is why I prefer to get to the bottom and then use that information to help prevent such mishaps occurring again. As what I concluded was apparently spot on, then, dude, politely recognising what was - was certainly no comment in-any-shape-nor form upon your character. Smile.
The Wiki instructions are attempting to cover nearly all of the bases to best serve the most people and likely problems. There is no single way to flash and there are numerous roadblocks that may occur. Having a simple and linear guide may be nice, but I strongly feel that it leads to rushed and relatively uninformed short-cuts where one error or another problem can leave one stuck and confused.
Keystone,
Glad to know it was just a misunderstanding. And to clarify, at no time have I disrespected you or the other fine members of this forum who use their spare time to have some fun with their hobby.
Also for the record, you did not conclude spot on unfortunately as it was not my rushing through the instructions that caused the issue but rather the fact that there is a certain amount of extrapolation required from your instructions to get everything working correctly.
Thanks again for all your help as I do appreciate it.
You're, welcome.
I've posted about this b4 and i havent recieved too many responses about it... I've checked on line and sprint touch pros have been having the same prob..
The problem is that when I flash my phone with whatever ROM it will work fine for a day or two and then it freezes which is o.k, because they all do freeze from time to time so when i hit he soft reset button at the bottom it hard resets the phone... "WHAT IN THE WORLD'" so reading some info online they stated that It maybe a bad SPL so i reinstalled it to no avail ... Please someone help... I've been Posting this like crazy everywhere
http://www.smartphonejunkie.com/showthread.php?t=182230
Here is some more info on what I've found online
I have ATT
HTC FUZE AKA TOUCH PRO
EnergyROM 3.0 serier 51009 NRGZ28 WWE
Hard SPL... SPL-1.90. OloNex microP- Raph (Key) v5 PSOC- Raph Stage_CVT v0x36
Model RAPH110
Some people have had this problem; the recommendation is to re-flash your originally shipped ROM before you flash a custom ROM. Hope this helps.
thankx.. will try..
I personally have a Touch Pro from Sprint (my wife's) and a Fuze from AT&T. I have flashed those two many times and I have never seen this behavior (not that it can't happen), but supps2 has a good point. Try to reflash to stock and see if the problem still persists. If it does, then you may have a bad phone. In such case, just relock it and try to get AT&T to exchange it for another one stating that the phone is defective (or something like that). Good luck!
I concour with supps2. As uncommon as this issue is, the people that have seen this happen just re-flash the stock ROM for whatever their phone is and whallah. Some people actually swear by flashing the stock ROM before any custom ROM flash in order to "reset" it, although there is no hard evidence that i've come accross that explains this phenominom.
you're not alone, by the way. i have the same issue with mine. i'm going to flash to stock right now to see if that helps. let me know if you have success with something else. thanks!
cool thankx you guys.. will let you guys know the process
I have the same issue and i just reflashed the ATT ROM. Its UGLY
Now i will try to reflash to something more eye soothing. Hope it fixes it, else need to lock and return it.
i've been having the same problem. its been driving me nuts! i'll give the stock rom thing a try too...
I had the same issue after flashing a diamond for a friend. The solution is here but I don't know if it applies to the TP. Maybe try sending a pm to cmonex
task 29 would be a bootloader command for diamond, i would think Raphael bootloader might have different commands. Has someone dumped the Raphael bootloader to get the list of supported commands (at least for formatting the NAND)? Or if someone is feeling lucky they can try task 29 and report back
i had the exact same issue about a month ago, i followed the same steps everyone else has stepped. reflashed to original at&t rom, then to the rom you want. also, follow these steps exactly, when you flash the at&t rom and the rom you want
http://forum.xda-developers.com/showthread.php?t=448008
step by step, i missed one (sim card) and i had it hard reset on me all the time. im not sure if thats what caused it, but i followed the steps perfectly and the phone is great now
so i was searching and came across these 2 threads which would explain why original ROMS would usually help recover from the sitaution
http://forum.xda-developers.com/showthread.php?t=435527&highlight=mtty
http://forum.xda-developers.com/showthread.php?t=491554&highlight=mtty
BTW, it seems Raphael hard spl has formatting disabled. Also some folks had been worried about bad blocks. This is what i was reading in WikiPedia
http://en.wikipedia.org/wiki/Flash_memory
Most NAND devices are shipped from the factory with some bad blocks which are typically identified and marked according to a specified bad block marking strategy. By allowing some bad blocks, the manufacturers achieve far higher yields than would be possible if all blocks had to be verified good. This significantly reduces NAND flash costs and only slightly decreases the storage capacity of the parts.
Click to expand...
Click to collapse