Related
OK Guys. Problem Solved : Dead devices due to tmob 1.72 + Downgrade
Problem: New version changes Device ID, as well as ID format.
If you upgrade to tmob 1.72, you cannot downgrade back, as you cannot supply valid NBF files for the new device ID. If you try to play around, you end up with a very dull bootloader screen "Serial V.1.06", and nothing more can be done. SD card images cannot be flashed due to the same reason.
Untill our developers come up with a simple tool, the following 2 solutions can be used to get out of the disaster:
Solution 1:
(tested and 100% working for both dead devices stuck in bootloader and devices working but stuck with the tmob 1.72 version.)
You will need a working device (with old ROM before 1.72), besides your dead one.
1. Prepare your DEAD device in Bootloader mode. Don't connect it yet. (If it is still working but you want to downgrade, press Power+Action+Stylus, if it is already stuck in bootloader, just reset with stylus).
2. Connect your WORKING device, with OLD version via activesync.
3. Start the rom installation of your choice normally, with a version compatible with this WORKING device (Official or Modified NBF files via HymaUpgradeUT). If you don't know what I am talking about, just use your official file downloaded from your WORKING devices' provider).
4. Press NEXT, untill you are presented with the Current version and the one that will be installed. DO NOT click "UPGRADE" yet. (If you got an error so far, you are not using the correct version for your working device.)
5. When you get the dialog with the versions, disconnect the WORKING device from the craddle and connect your DEAD device, in bootloader mode.
6. Click "UPGRADE" and go get yourself a drink.
Et Voila.
Thanks to Victor for inspiring this solution.
Solution 2:
If you don't have another working device, and only have a dead one stuck in BootLoader, you can flash the attached image, through SD card. It will bring back your device to life with the BETA tmob 1.72 CE ROM.
Write the image to the card using "NTRW". Info on SD images and NTRW can be found in this forum.
Unfortunately, i don't have device even with working bootloader And it stuck in TMObile screen
I am sorry I have no solution for screwed Bootloaders, but if your device loads into the tmob screen, there must be something there still working. The only thing I can advise is to try to hard reset and not go into the extended ROM setup files (Soft Reset right after the Hard Reset and welcome procedure), but I guess you don't reach that far ....
What is about for XDA 1?
HI !
I have a Dead XDA. The bootloader is OK. How can I do with it ?
I need some advice for doing it, please !
Best reguard,
Carlo & Victor... You are GREAT!!
Okey.... I will try FIRST!!
please, where is the officiale t mobil rom ? we all have the beta (and thee pb you solve) but not the official one...
thanks
When i posted the T-mobile 172 rom i did not know how much greif it would cause people, sorry to everyone for this
As to the second solution using the SD card is it possible to use this method on a working XDA2.
Basically i have a UK XDA2 and of corse i getthe ID error if i run the upgrade, i dont understand very well how to change the ID part so could i just make the SD card with the rom on it and follow your instructions to recover a dead XDA2
Thanks
John
What should I do when I want to upgrade/downgrade...
I have the T-Mobile 1.72WWE rom installed.
Everything works ok for now, no problems.
But do I need to do when I want to upgrade/downgrade?
I don't have a second device so thats not an option
Please advise.
Thanks
To cairo31male!!
NOP!! Can't HELP!! Maybe the BOOTLOADER got the diffrent version? Mine is 1.03. Can u tell me how to upgrade the bootloader to 1.06?
And you mentioned about OLD version, what do you mean by that?
@hcnsoft:
The 2 solutions described above are for XDA 2's which have been screwed up by installing / uninstalling the latest beta version tmob 1.72. If this is your situation, and you have a working bootloader, both solutions should work for you.
@SEB152030:
The beta we have is 1.72, which caused all these problems. If you have another working device, as described in solution 1, you can revert back to the latest working official ROM (1.66), just follow the steps decribed above and use the official 1.66 upgrade program.
@applecom:
If your XDA 2 is dead, there is no harm in trying. But basically, this SD file will only work on devices that have already been upgraded to 1.72 and then died. If it is dead because of any other reason, I suggest you stick with older stable versions and don't try to mess up with 1.72 for now, until the developers come up with a simple tool to go back and forth between different roms. You can flash SD images that were made from other working devices that have your same model/language. You wouldn't get any errors that way.
@Panja:
Since your device is working, I suggest you wait a couple of days, before trying anything. The developers might come up with a simpler solution. If you absolutely have to downgrade, you can follow the solution 1 described above, but you will need another working device for a few minutes. Use the other working device which has the old ROM installed and start the OLD ROM installation software, then plug in your device with the 1.72 ROM AFTER you get the different versions dialog with the button "UPGRADE".
@Ivan-R: which method are you tying? Solution 1 or 2? FOr the first solution, I guess it should work. For the SD flashing, I beleive you should have Bootloader 1.06. How to get that one, I don't know, but I strongly advise against it, untill all this matter is clear, as each new version of the bootloader implements stricter security, which will make it harder to customize in the future.
OLD version means any version before 1.72
cairo31male said:
@hcnsoft:
@Ivan-R: which method are you tying? Solution 1 or 2? FOr the first solution, I guess it should work. For the SD flashing, I beleive you should have Bootloader 1.06. How to get that one, I don't know, but I strongly advise against it, untill all this matter is clear, as each new version of the bootloader implements stricter security, which will make it harder to customize in the future.
OLD version means any version before 1.72
Click to expand...
Click to collapse
I already try BOTH solution!! Solution 1, i try with ROM 1.03.11, which is thats the basic ROM. Solution 2, the RESULT is Not Allowed UpDate!!
So i guess this is the matter of BOOTLOADER!! Yours is 1.06 and me 1.03. THATS THE PROBLEMO NOW!! Now... How about upgrade the BOOTLOADER??
[email protected]#$!%G FREAK ROM!! :evil:
Mas Ivan,
Sebaiknya anda jangan menggunakan sd image yang di upload karena masih beta untuk menghindari kesalahan pada rom 1.72
thanks cairo for the info, my xda is working with the standard rom, Our only problem is me and the guy that got the rom in the first place would like to use it but we cant
anyway thanks for youe info
John
Solution 1
Solution 1 don't work for me because (I think) 2 version of bootloader 1.03 and 1.06.....
I found a solution : Here
Radio Stack Downgrade
I loaded the 1.72 Beta and would like to keep it, but the Radio Stack is horrible for me. I need to go back to the O2 launch version of the radio stack. I noticed in the O2launch Rom that the contents of the exe file included Radio.nb while the 1.72 exe contained Radio.nbf.
Is it safe for me to try and downgrade only the radio stack and if so should i use the launch version of himalaya upgrade or the 1.72 version of himalaya upgrade to install the launch radio.nb file?
Can anyone give me some advice here? My radio is barely functional. can't find networks where i know there is coverage. Thanks for any advice.
Re: Radio Stack Downgrade
watchdogsdg said:
I loaded the 1.72 Beta and would like to keep it, but the Radio Stack is horrible for me. I need to go back to the O2 launch version of the radio stack. I noticed in the O2launch Rom that the contents of the exe file included Radio.nb while the 1.72 exe contained Radio.nbf.
Is it safe for me to try and downgrade only the radio stack and if so should i use the launch version of himalaya upgrade or the 1.72 version of himalaya upgrade to install the launch radio.nb file?
Can anyone give me some advice here? My radio is barely functional. can't find networks where i know there is coverage. Thanks for any advice.
Click to expand...
Click to collapse
Go go go... Just downgrade it!! 8) Then you will join me in HERE!! Huahahahaha... You are STUCK for the REST OF YOUR LIFE!!
Didn't have any trouble downgrading
I just upgraded to 1.72 last week...hated it...gprs was WAY too slow. Today I downgraded and crossed my fingers back to Xda_II_Upgrade_v16050.exe (filename..not sure where i got it).
IT WORKS!! everything went fine and is fine.
I think my bootloader said it was something like version 1.01 (very hard to read that screen without the backlight) So I'm guessing this downgrade problem may be specific to bootloader versions.
No expert, just letting you know what i did.
This site is amazing. Thanks for everything.
Re: Didn't have any trouble downgrading
mkriemersma said:
So I'm guessing this downgrade problem may be specific to bootloader versions.
No expert, just letting you know what i did.
Click to expand...
Click to collapse
I AGREE WITH YOU!! BOOTLOADER thang'!! I am not EXPERT too, but I REALLY NEED SOME HELP HERE!!
Hi,
Thanks for all help!
I have a dead unit due to 1.72 ROm.
Itried to fool the himalya upgrade program with a soft reset as suggested in another thread, it works It gets trough the device id but stops when erasing rom, any suggestion?
Is there anyone out ther that can disassamble the himalyprogram and
make a small program without error checking?
I also have bootloader 1.06 and tried also "ntrw write ROM.nb1 H:"
It works writing the image but my bootloader don´t loads any rom.
Tried with 2 differnet SD cards, and soft reset, hardreset, and only pushing camera button, without succes, what is the right command?
Any more suggestions?
@nilron:
Press ARROW KEY (any direction on joystick) + POWER Button + SOFT RESET, all together, then wait a little. You should get instructions to press POWER to start flashing.
Started a rom upgrade, power failure :x I am NOT a developer so need simple step by step advice on what I may be able to do to recover situaton. Device says Serial 1.06, if I plug into cradle machine beeps to confirm connection and XDA II says USB 1.06.
All I have is the original Rom file and the upgrade (these are both exe's designed to run on PC to upgrade through activesync.
I do have SD card but no raw image.
What are my chances (other than sending in for repair?)
JeremyC said:
Started a rom upgrade, power failure :x I am NOT a developer so need simple step by step advice on what I may be able to do to recover situaton. Device says Serial 1.06, if I plug into cradle machine beeps to confirm connection and XDA II says USB 1.06.
All I have is the original Rom file and the upgrade (these are both exe's designed to run on PC to upgrade through activesync.
I do have SD card but no raw image.
What are my chances (other than sending in for repair?)
Click to expand...
Click to collapse
Don't panic...
Put the device into cradle (with power supply plugged) and run that update again...
HTH
Beecher, thanks for your reply. Sadly I had already tried that!
With the upgrade rom the app ran and found the XDA but reported that the update was the wrong version (I can only guess because it could not find an existing rom to update (I know the update had got as far as erasing the old one)
I did also try and run the original factory release rom prog but that did not seem to do anything at all.
what's your device type (qtek2020, i-mate, MDA II, O2 XDA II) ? ... and what was the original ROM version ?
JeremyC said:
Beecher, thanks for your reply. Sadly I had already tried that!
With the upgrade rom the app ran and found the XDA but reported that the update was the wrong version (I can only guess because it could not find an existing rom to update (I know the update had got as far as erasing the old one)
I did also try and run the original factory release rom prog but that did not seem to do anything at all.
Click to expand...
Click to collapse
Ouch, it looks like I missed basic information you have a XDA1/MDA1 device! I thought you have XDA2/MDA2 device.
In this case, try to find on this forum LumpiStefan ROM kitchen for XDA1/MDA1, cook you own ROM and download only ROM image. Then upload this ROM to your card and get to bootloader. It should somehow update your ROM in device.
HTH
beecher said:
JeremyC said:
Beecher, thanks for your reply. Sadly I had already tried that!
With the upgrade rom the app ran and found the XDA but reported that the update was the wrong version (I can only guess because it could not find an existing rom to update (I know the update had got as far as erasing the old one)
I did also try and run the original factory release rom prog but that did not seem to do anything at all.
Click to expand...
Click to collapse
Ouch, it looks like I missed basic information you have a XDA1/MDA1 device! I thought you have XDA2/MDA2 device.
In this case, try to find on this forum LumpiStefan ROM kitchen for XDA1/MDA1, cook you own ROM and download only ROM image. Then upload this ROM to your card and get to bootloader. It should somehow update your ROM in device.
HTH
Click to expand...
Click to collapse
:?: :?: :?: :?: :?:
I brought Cingular 8525 off Ebay over a month ago and love it. I like experimenting things to improve and learn of this website about upgrading your Hermes to make it better than stock version provided by your carrier. I have been reading this forum for almost a month now since I got this 8525 and wanted to dive into it but I would like someone to confirm the step I am plan on doing is the way to go with least risk of bricking my pda. I understand there always a risk of bricking it but I want the least risk as possible =P
From reading this forum and wiki I learn that I should do this steps but correct me if I missed a step or doing something in wrong order.
1) Since I am going to use Hard SPL I don't need to SuperCID my phone and just download Hard SPL Hard-SPL-V2.zip at http://forum.xda-developers.com/showthread.php?t=296722 and flash it using usb port on a xp with activesync installed.
2) Download Radio 1.38 without gps HERM_RADIO_1.38.00.10_Only_SSPL.rar at http://forum.xda-developers.com/showthread.php?t=297925 and flash it the same method above via usb and activesync.
3) Test phone make sure everything working after 2 flashes.
4) Download WM6 ROM (I am leaning toward MWVI Black Edition v1.2) Windows_Mobile_VI_-_Black_Edition_v1.2_(Release_22-03-07_GMT+10_4am).exe at http://forum.xda-developers.com/showthread.php?t=298936 and flash it the same step as above via usb and activesync.
This part I am lost on is the statement on that forum -> "To install, run the (.exe). This will automatically push Des's SSPL to your phone although if you have security enabled then you will need to answer "Yes" to the dialogue when it appears on your phone."
Do I need to answer yes because I have Hard SPL install or is it going to overwrite my Hard SPL with Des's SSPL? I am lost about that one and wasn't sure on this.
5) Download cabs to restore Cingular data and mms settings at http://forum.xda-developers.com/showpost.php?p=1163312&postcount=1 and install it on phone.
6) Download Cingular Keyboard layout fix and install.
Also I am thinking of skipping step 2) - Radio upgrade also 4) - MWVI ROM upgrade and instead go with LVSW Edition at http://forum.xda-developers.com/showthread.php?t=298809 which came out yesterday and since it come with Radio 1.34 and are there any steps I need to do with SPL or it will flash fine with Hard SPL? then resume step 5) and 6)
In the future if I want to get a new pda and sell this one, all I need to do is download stock ROM from Cingular and flash it back on my 8525 then it should be back to the state it was like when I brought it overwriting or removing the Hard SPL and Radio and OS?
Thank for your inputs and help!
Bill
1234567890
... answer, "yes". It's just a warning/message, that's all. Sounds like you have a handle on everything else. Just go for it (and be sure to keep your eyes open).
TechBill said:
This part I am lost on is the statement on that forum -> "To install, run the (.exe). This will automatically push Des's SSPL to your phone although if you have security enabled then you will need to answer "Yes" to the dialogue when it appears on your phone."
Do I need to answer yes because I have Hard SPL install or is it going to overwrite my Hard SPL with Des's SSPL? I am lost about that one and wasn't sure on this.
Click to expand...
Click to collapse
SSPL stands for SoftSPL, so no, it won't overwrite Hard-SPL. It will run 1.09.des bootloader on your device for the duration of the flash, then you'll be back to whichever SPL you had before you started. If you don't have security turned off on your device (most don't), you'll have to answer 'Yes' when SSPL is pushed to your device because it's unsigned code. It has nothing to do with being Hard-SPL.
Whether or not you'll overwrite Hard-SPL with your flash depends whether the ROM you are flashing also contains SPL (and what version it is). Best to know exactly what you're flashing before you do.
The rest of your plan looks good to me, especially step 1 being to flash Hard-SPL. While nothing can "innoculate" your device from a brick (i.e., sh*t happens), Hard-SPL does give you a way out if a flash goes south on you.
Watch the Cingular settings cabs... I've had some issues with them. I prefer to set things up manually after a hard reset, but that's just my experience. They work fine for others.
Also, IMHO the newer radios work better with WM6. The combo shown in my sig runs beautifully for me (but, as always, your mileage may vary!).
i am on a cingular 8528 and i am looking fo rthese 2 cab files.
WM VI Black Clean Icon Patch.cab
Cingular 8525 keyboard CAB
i am in a huge rush so can someone point out where tehy are? thank you in advance!
Eric
TechBill said:
1) Since I am going to use Hard SPL I don't need to SuperCID my phone and just download Hard SPL Hard-SPL-V2.zip at http://forum.xda-developers.com/showthread.php?t=296722 and flash it using usb port on a xp with activesync installed.
Click to expand...
Click to collapse
Yep
TechBill said:
2) Download Radio 1.38 without gps HERM_RADIO_1.38.00.10_Only_SSPL.rar at http://forum.xda-developers.com/showthread.php?t=297925 and flash it the same method above via usb and activesync.
Click to expand...
Click to collapse
Yep
TechBill said:
3) Test phone make sure everything working after 2 flashes.
Click to expand...
Click to collapse
If you wish
TechBill said:
4) Download WM6 ROM (I am leaning toward MWVI Black Edition v1.2) Windows_Mobile_VI_-_Black_Edition_v1.2_(Release_22-03-07_GMT+10_4am).exe at http://forum.xda-developers.com/showthread.php?t=298936 and flash it the same step as above via usb and activesync.
Click to expand...
Click to collapse
Looking good
TechBill said:
This part I am lost on is the statement on that forum -> "To install, run the (.exe). This will automatically push Des's SSPL to your phone although if you have security enabled then you will need to answer "Yes" to the dialogue when it appears on your phone."
Do I need to answer yes because I have Hard SPL install or is it going to overwrite my Hard SPL with Des's SSPL? I am lost about that one and wasn't sure on this.
Click to expand...
Click to collapse
Hard SPL is only there to help recover your device if it gets bricked during a flash. The security is OS dependant and only requires you to click yes when SSPL is pushed to your phone as it indentifies it as an untrusted source. This will probably happen when you install the Radio upgrade as well. SSPL is only a temporary psuedo bootloader and will not overwrite Hard SPL or any other bootloader on your device.
TechBill said:
5) Download cabs to restore Cingular data and mms settings at http://forum.xda-developers.com/showpost.php?p=1163312&postcount=1 and install it on phone.
Click to expand...
Click to collapse
Unsure if those settings will work, maybe a cingular user can confirm this. If in doubt copy down your MMS and data connection settings and input them manually after OS upgrade.
TechBill said:
6) Download Cingular Keyboard layout fix and install.
Click to expand...
Click to collapse
Great!!
TechBill said:
Also I am thinking of skipping step 2) - Radio upgrade also 4) - MWVI ROM upgrade and instead go with LVSW Edition at http://forum.xda-developers.com/showthread.php?t=298809 which came out yesterday and since it come with Radio 1.34 and are there any steps I need to do with SPL or it will flash fine with Hard SPL? then resume step 5) and 6)
Click to expand...
Click to collapse
Ok, if you decide to go for the LVSW ROM then download the OS only repack that is posted somewhere in that thread (not the one thats in the 1st post). The reason for this is because it includes a bootloader that will overwrite Hard SPL. Just download OS and replace with Black Edition noted in step 4.
TechBill said:
In the future if I want to get a new pda and sell this one, all I need to do is download stock ROM from Cingular and flash it back on my 8525 then it should be back to the state it was like when I brought it overwriting or removing the Hard SPL and Radio and OS?
Click to expand...
Click to collapse
Shouldn't be a problem
TechBill said:
Thank for your inputs and help!
Bill
Click to expand...
Click to collapse
No problem, nice to see someone do a bit of research for a change.
S.K.
EDIT: LOL!! Deleted my first post to create a nice lengthy reply and other ppl have beaten me to it now.... *cries*
The Cingular settings worked for me to access the internet and mms!
thasiccest13 said:
i am on a cingular 8528 and i am looking fo rthese 2 cab files.
WM VI Black Clean Icon Patch.cab
Cingular 8525 keyboard CAB
i am in a huge rush so can someone point out where tehy are? thank you in advance!
Eric
Click to expand...
Click to collapse
Hey pal, the search function works really fast on this forum. Try using it for a change instead of cluttering threads with your "I'm in a huge rush" nonsense. You're not the only one on this planet that's busy.
WM VI Black Clean Icon Patch.cab
Can i use this if i am using the LVSW Edition
thank you,
Eric
vp3G said:
Hey pal, the search function works really fast on this forum. Try using it for a change instead of cluttering threads with your "I'm in a huge rush" nonsense. You're not the only one on this planet that's busy.
Click to expand...
Click to collapse
First off i hate being called PAL, but thats ok.... i did search BUT i can not find it! i found 2 links that were not in use anymore, so i could not download, instead of making a nasty reply why even reply at all?
I am new and i do this for fun, just like everyone here, so relax and have a good time!
Eric
thasiccest13 said:
First off i hate being called PAL, but thats ok.... i did search BUT i can not find it! i found 2 links that were not in use anymore, so i could not download, instead of making a nasty reply why even reply at all?
I am new and i do this for fun, just like everyone here, so relax and have a good time!
Eric
Click to expand...
Click to collapse
You hate being called PAL? What about SECAM?
OK, seriously though, the Black Edition patch was designed for the Black Edition, it's probably not a good idea to use it on the LVSW ROM.
The search function can be pretty crappy at times, which is why you can search the forums using Google instead. I think that changing the registry yourself is better anyway because then you know what you're doing...
Wow thank you everyone for your replys!!
I am still undecide which OS ROM to go with.. Both look great!
Bill
TechBill said:
I am still undecide which OS ROM to go with.. Both look great!
Click to expand...
Click to collapse
You could try both if you want to. That's one of the benefits of this community. You can actually *choose* what you want, and then have the option to change your mind as many times as needed!
thasiccest13 said:
First off i hate being called PAL, but thats ok.... i did search BUT i can not find it! i found 2 links that were not in use anymore, so i could not download, instead of making a nasty reply why even reply at all?
I am new and i do this for fun, just like everyone here, so relax and have a good time!
Eric
Click to expand...
Click to collapse
Ok SPORT (better?), perhaps you're totally oblivous to the fact you hijacked the OP's thread as if your woes take precendence over anyone else's. But oh, that's right... "you're in a rush".
Not "being nasty", just asking that you demonstrate a modicum of respect for the forum.
Upgrade was a success!
I went with Black Edition and I must comment it got nice Splash screen and today screen! I was a little worried it was going to be gothic looking screen but it wasn't and it is a very nice looking screen and setup and seem to be easier on the eyes too.
Thank you for all your inputs and feedbacks!
I entered the Cingular WAP setting manually and use a cab to fix the keyboard layout then uninstalled the cab so it wouldn't be in my Remove Program box.
Bill
Congrats!
TechBill said:
Upgrade was a success!
Click to expand...
Click to collapse
Congrats on no longer being a flashing virgin! Watching that radio flash creeeeeep along is a real nail-biter the first time, isn't it?
Thanks for this post! These were the same questions I had!
vp3G said:
Congrats on no longer being a flashing virgin! Watching that radio flash creeeeeep along is a real nail-biter the first time, isn't it?
Click to expand...
Click to collapse
OH yeah you got that right! The Radio flashing was exactly what you said. A real nail biter, there was moment when I thought my phone is screwed then it would jump another 4% or so in the status bar then another long pause.
But it was an awesome learning experience for me and now I feel more comfortable upgrading my pda.
Trancecoder said:
You hate being called PAL? What about SECAM?
OK, seriously though, the Black Edition patch was designed for the Black Edition, it's probably not a good idea to use it on the LVSW ROM.
The search function can be pretty crappy at times, which is why you can search the forums using Google instead. I think that changing the registry yourself is better anyway because then you know what you're doing...
Click to expand...
Click to collapse
Really I am having problems with the search function in this site too. I'll try google as mentioned.
Now this isn't completely my own guide, it is a guide hobbled together from other people's own guides, but has always worked for me. I run a Titan like the rest of you. My flavour is the HTC P4000 sold through Telus.
**INSTALLING FROM USB**
1. First, you'll want to BACK UP AT LEAST YOUR CONTACTS and anything else in the phone memory that you cannot live without Anything on your memory card will not be an issue.
2. Get your unlock code, msid, and msn and any other account/phone info before updating to a gps/rev. a radio as some people have lost it during the transition. they can view their info using ##778# on sprint phones ans they can use getspc to get their unlock code from their esn hex. (contributed by elgreek84).
3. Download Olipro 2.40.0 by clicking on the following link. http://www.fileshex.com/download.php?file=b8a2c4622ebdb1c857ac6cf068e6f818 and install it.
4. Download the latest Sprint rom, becaues it upgrades you to the latest Radio ROM 3.35.04 effortlessly. The Sprint rom is available from the HTC usa support site here. http://www.htc.com/us/FAQ_Detail.aspx?p_id=75&act=sd
Click on "Download Version 3.35.651.2".
5. Make sure your phone is connected through usb and start the last program you just downloaded. Once it is complete and it asks you to adjust your stylus settings, press the right side power button, camera button at the same time, and also press in the bottom reset button and HOLD IT until you see the multi colour boot loader. It'll look like a tv test screen.
6. Now at this point you'll need to go into Activesync settings, should be connection settings. In Vista (yes, I use Vista 64 bit and it works perfectly) go into the control panel and double click on "Windows Mobile Device Center" and uncheck the usb connection. In WinXP in Activesync it should be under the connection settings under file or edit.
7. Right.. now you're ready to download the latest rom which is compatible with the radio you flashed. If you're on Sprint and want regular Sprint, go ahead and stop at step 4 and configure the stylus settings, but if you want even better, go to DCD's rom here http://forum.xda-developers.com/showthread.php?t=376150 and install "ROMs (by |||bored|||):" I downloaded the Telus once since I'm on Telus.
8. Enjoy! Now install the apps and set up your settings, and synchronize your contacts and settings. Don't forget to re-enable that usb settings in the Windows Mobile Device center.
I'm fairly sure that pretty much covers it. This isn't my own work, I've just followed bits and pieces that are already available on this excellent website.
The DCD thread covered much of it but a few of you still seem to be having problems with it. I hope it helps those that are still out of the loop.
------------------------------------------------------------------------------------------------------------------
Installing from SD card. (contributed by Keystone).
Easy installation:
HINT: Avoid hassles with your USB connection and PC by flashing via the microSD card
Third party ROMs require a functioning and specific unlocking boot loader. Note what version is required for the ROM that you intend to boot into, or else you will face stuck staring at the boot screen.
No third party ROM include a functioning radio ROM. Note what radio is required for your chosen ROM. Radio 3.35.04 is required for those based off of the latest Sprint release.
via the microSD card flashing method (below), upgrade your Titan to the radio via the full Sprint 3.35.651.2 ROM (an executable archive, right click to extract the RUU_signed.nbh ROM file)
do NOT boot into the OS after flashing to this ROM.. After screen calibration Sprint customisations will run and alter your EPST settings to that operators settings.
Repeat the microSD flashing routine to flash to your chosen OS ROM.
I. OEMizer (optional)
Run OEMizer.exe from the kitchen's tool directory.
Complete your choices to customise your Titan's OS/Owner/Data/etc configurations
Hit the 'Create OEM' buttom for the customizations to be written into the kitche's OEM directory.
Build your ROM via the kitchen.
II. Kitchen
Run BuildNB.bat to execute BuildOS.
Hit the play button when you have selected your choices.
Exit BuildOS once it has completed.
Let the batch file complete its jobs.
quit the ROM Upgrade utility when it loads up and skip onto the following instructions on how to flash via the microSD card method.
OR follow through to finish the flash with the ROM Upgrade Utility via the USB.
III. PagePool Changer (optional)
Run PagePool Changer.exe
Select your ROM -- /RUU/RUU_signed.nbh
The default is 6 MB
The Titan has limited RAM so it isn't recommended to go beyond 8 MB
go smaller if you want more RAM free
Hit 'Close' when ready.
Flash your custom ROM.
IV. Flashing via the microSD card
With a card reader on your PC, format a microSD card into FAT32
From the kitchen's RUU directory, copy the ROM (RUU_signed.nbh) to the root of the microSD
Rename the ROM to TITAIMG.nbh
Insert your card.
Force into the boot loader with POWER-CAMERA-RESET
Follow the instructions and you'll quickly flash your Titan...
This will work to flash with an official ROM and radio, I think regardless of the boot loader you have installed. But ensure that you have the correct boot loader (olipro 2.40 for this ROM) installed for when you do eventually finish with your flashing and are ready to boot into the OS.
Can a mod sticky this?
If I missed anything at all, post the question and I'll modify the list to include that step.
Cheers on writing up a guide...but there are a few unnecessary steps in there...
First, there is no need to force the phone back into the bootloader after running the sprint update. Just let the phone boot up normally, wait for the tap the screen setup, and run the kitchen or RUU of your choosing. This will AUTOMATICALLY put the phone back into the bootloader and immediately begin to flash. There is no need to uncheck the usb setting in WMDC or activesync either.
gcincotta said:
Cheers on writing up a guide...but there are a few unnecessary steps in there...
First, there is no need to force the phone back into the bootloader after running the sprint update. Just let the phone boot up normally, wait for the tap the screen setup, and run the kitchen or RUU of your choosing. This will AUTOMATICALLY put the phone back into the bootloader and immediately begin to flash. There is no need to uncheck the usb setting in WMDC or activesync either.
Click to expand...
Click to collapse
Always helpful info. I just read on the forums how a few people did recommend doing that, and it always worked. Either way.
Plus, it can be much safer to get people familiar and accustomed to flashing via the microSD card way.
Knowing what an *.nbh file is and how to flash your device upon your own and without an extra utility are huge fundamentals to decreasing clls for help.
Most of the repeated troubled posts involve errors with the USB connection, installer utilities, unfamiliarity with a notable multi-coloured screen, switching between different boot loaders, etc... Here's a cut'n paste example from my kitchen's thread:
Easy installation:
HINT: Avoid hassles with your USB connection and PC by flashing via the microSD card
Third party ROMs require a functioning and specific unlocking boot loader. Note what version is required for the ROM that you intend to boot into, or else you will face stuck staring at the boot screen.
No third party ROM include a functioning radio ROM. Note what radio is required for your chosen ROM. Radio 3.35.04 is required for those based off of the latest Sprint release.
via the microSD card flashing method (below), upgrade your Titan to the radio via the full Sprint 3.35.651.2 ROM (an executable archive, right click to extract the RUU_signed.nbh ROM file)
do NOT boot into the OS after flashing to this ROM.. After screen calibration Sprint customisations will run and alter your EPST settings to that operators settings.
Repeat the microSD flashing routine to flash to your chosen OS ROM.
I. OEMizer (optional)
Run OEMizer.exe from the kitchen's tool directory.
Complete your choices to customise your Titan's OS/Owner/Data/etc configurations
Hit the 'Create OEM' buttom for the customizations to be written into the kitche's OEM directory.
Build your ROM via the kitchen.
II. Kitchen
Run BuildNB.bat to execute BuildOS.
Hit the play button when you have selected your choices.
Exit BuildOS once it has completed.
Let the batch file complete its jobs.
quit the ROM Upgrade utility when it loads up and skip onto the following instructions on how to flash via the microSD card method.
OR follow through to finish the flash with the ROM Upgrade Utility via the USB.
III. PagePool Changer (optional)
Run PagePool Changer.exe
Select your ROM -- /RUU/RUU_signed.nbh
The default is 6 MB
The Titan has limited RAM so it isn't recommended to go beyond 8 MB
go smaller if you want more RAM free
Hit 'Close' when ready.
Flash your custom ROM.
IV. Flashing via the microSD card
With a card reader on your PC, format a microSD card into FAT32
From the kitchen's RUU directory, copy the ROM (RUU_signed.nbh) to the root of the microSD
Rename the ROM to TITAIMG.nbh
Insert your card.
Force into the boot loader with POWER-CAMERA-RESET
Follow the instructions and you'll quickly flash your Titan...
This will work to flash with an official ROM and radio, I think regardless of the boot loader you have installed. But ensure that you have the correct boot loader (olipro 2.40 for this ROM) installed for when you do eventually finish with your flashing and are ready to boot into the OS.
Excellent stuff. I think it would be nice to have a centralized thread for installations.
they should also get their unlock code, msid, and msn and any other account/phone info before updating to a gps/rev. a radio as some people have lost it during the transition. they can view their info using ##778# on sprint phones ans they can use getspc to get their unlock code from their esn hex.
elgreek84 said:
they should also get their unlock code, msid, and msn and any other account/phone info before updating to a gps/rev. a radio as some people have lost it during the transition. they can view their info using ##778# on sprint phones ans they can use getspc to get their unlock code from their esn hex.
Click to expand...
Click to collapse
Aww, but that's just taking contingency preparedness too far......
Figures, I make a knowledgeable guide, and there are what.. at least 10 or 20 threads that keep asking the same quesitons over and over. Go figure.
Ironically I've never disabled the USB setting in Vista's (running 32-bit Ultimate) Sync Center and flashing still works fine.
subscribed
Fantastic guide. EvilDeadFan this is what i have been looking for. Especially with you being on Telus as i am. I have a couple small questions though. I have been reading for a couple weeks off and on and my issue is that most info is Sprint or Verizon specific so im left flapping on many of those carrier specific steps. In step 2 you recomend as pointed out by elgreek84 to backup the carrier required information. Now i know ##778# doesnt work on my phone but ##775# does and even when i get into the EPST it seems empty. Is this required on a Telus setup? I would think not as it was not part of your original steps. Is a reprogramming with Telus after its upgrade has completed required? possibly using *22803?
Also in step 3 to install the Olipro 2.40 i understand what to do but what results should i see? Should i soft reset so i can see the SPL that is installed? Sorry anal i know.
I really want to go ahead with this cause i seriously doubt Telus will ever get around to a proper update but im anal with things like this and have to know and be comfortable with every step.
So as a fellow Telus user how do you find DCD 3.0.1? Is it reliable and mostly glitch free? (Read about MMS issues, random reboots, BT issues still)
Also it seems there is a small spell-o on step 7 "I downloaded the Telus once since I'm on Telus." I think once should be one.
Thanks again stellar guide.
yonder711 said:
Fantastic guide. EvilDeadFan this is what i have been looking for. Especially with you being on Telus as i am. I have a couple small questions though. I have been reading for a couple weeks off and on and my issue is that most info is Sprint or Verizon specific so im left flapping on many of those carrier specific steps. In step 2 you recomend as pointed out by elgreek84 to backup the carrier required information. Now i know ##778# doesnt work on my phone but ##775# does and even when i get into the EPST it seems empty. Is this required on a Telus setup? I would think not as it was not part of your original steps. Is a reprogramming with Telus after its upgrade has completed required? possibly using *22803?
Also in step 3 to install the Olipro 2.40 i understand what to do but what results should i see? Should i soft reset so i can see the SPL that is installed? Sorry anal i know.
I really want to go ahead with this cause i seriously doubt Telus will ever get around to a proper update but im anal with things like this and have to know and be comfortable with every step.
So as a fellow Telus user how do you find DCD 3.0.1? Is it reliable and mostly glitch free? (Read about MMS issues, random reboots, BT issues still)
Also it seems there is a small spell-o on step 7 "I downloaded the Telus once since I'm on Telus." I think once should be one.
Thanks again stellar guide.
Click to expand...
Click to collapse
you only back this stuff up for safety or just incase you have a brain fart and go past the stylus setup
For us non sprint customers to get the radio or GPS Function we have to flash a rom to our Phone that was made for another carrier and they have different information in there ..... So IF you go past the stylus setup all of sprints information will over write all of our telus info causing our phones to not work as a communications device until we put all that stuff that we copied down in!
So as long as you do not go past the stylus setup you will not need that info!
For TELUS it is just "##778" not "##778#"
You only need to do this if your phone not able to send or receive calls or text MSG's or get a data connection
Great Rom, stable as hell, he has done a wonderful job on this rom. I haven't had any glitches lockups or malfunctions, I get all of my texts, emails, calls, alerts my callers hear me clearly and I hear them clearly.
This rom does what it was made for!
One thing that has not been an issue for me and it could be from some of the other settings in the REG that I’ve been messing with, is I have 3 all different high end model bluetooth ear pieces, all Pair to my phone but do not work!
Hey: EvilDeadFan good work man?/woman?
EvilDeadFan said:
Figures, I make a knowledgeable guide, and there are what.. at least 10 or 20 threads that keep asking the same quesitons over and over. Go figure.
Click to expand...
Click to collapse
The fact that the title of this thread is very vague probably doesn't help =(
Otherwise, great work it helped me out a lot!
paravis said:
The fact that the title of this thread is very vague probably doesn't help =(
Otherwise, great work it helped me out a lot!
Click to expand...
Click to collapse
How is "ULTIMATE INSTALLATION GUIDE" vague?
I agree that there should be more sticky's but this thread is generally commented on all the time, so it should be active when you log in.
serfboreds said:
I agree that there should be more sticky's but this thread is generally commented on all the time, so it should be active when you log in.
Click to expand...
Click to collapse
The Wiki is the best place for these guides. Each level or revision of this software requires its own installation process described. I have been trying to keep the Wiki updated and invite others to help. That way we can keep the number of "Best" installation guides minimized and focused on the ROMs they pertain to. Maybe we can get the noobs to read it first, too.
The Wiki should be a great resource for all. Ok, I'll get off my soapbox, but DCD made me do it.
rschell said:
The Wiki should be a great resource for all. Ok, I'll get off my soapbox, but DCD made me do it.
Click to expand...
Click to collapse
You needed to push it.
I just made some small additions for recording EPST data, editing it, and flashing via the microSD method.
queston
ok so I already had the newest sprint update on my phone(6800) and then I downloaded bootloader and loaded it and it was in bootloader screen and then I ran dcds 3.01, everything seems to be working right and running good, is there anything that can be affected by doing it this way? thanks in advance to any input
so doing these upgrades usually doesn't erase all the info in #778 right?
PS thanks for this guide. this is probably the most simple guide i've seen.
Makes it really easy looking. i've flashed my 6700 a few times, but
never had to upgrade the radio and unlock something before...
so I really appreciate this post having simple info with links.
hey all, I will be recieving my p4000 in a week, and I want to know if what I am thinking of doing will actually work, and greatly simplify the upgrade process for my. With my vogue I do all flashing from sd, and I want to do the same with the titan, so here is what I am hoping will work:
1. use dutty's nbh tool to extract radio from sprint update
-I assume it is the 785.nb, can anyone confirm this?
2. use winzip to extract hard-spl-mfg, and inside is olipro-2.40-hard.nb
3. create custom rom using ppckitchens 3.35 selections
4. use dutty's nbh tool to extract .nb's from custom rom
5. use dutty's nbh tool again to package up
-785.nb as radio
-olipro-2.40-hard.nb as spl
-use mainsplash, secondarysplash, and windows.nb from custom rom
Once packaged, will I be able to flash this all in one shot, or does the device have to be unlocked seperately, and then flashed with an nbh without spl?
...
serfboreds said:
How is "ULTIMATE INSTALLATION GUIDE" vague?
I agree that there should be more sticky's but this thread is generally commented on all the time, so it should be active when you log in.
Click to expand...
Click to collapse
How is it not?
Pretend you had not idea what was in this thread, and were just looking at the title. "ULTIMATE INSTALLATION GUIDE" What does that tell you? Here's a list of conclusions that can be drawn from that title, off the top of my head and obviously from my own tech background.
1. An installation guide for installing Windows Vista Ultimate.. obviously not likely as this is not an appropriate forum for that... HOWEVER
2. "" "" "" "" with the necessary components needed to properly sync, and be able to perform titan flashes correctly. Makes sense as many, like myself, have had troubles both syncing / getting usb connectivity, and / or being able to perform flashes in Vista.
Vista possiblities end -
3. Okay, its an installation guide.
First off, from my experience and observations in these forums and among the HTC mod communities, applying a new radio, or rom to a phone, is not usually referred to as "installing". Rather, the more prevelant term is "flashing" a new rom, or a new radio.
Secondly, I think it's obvious to anyone, that the topic, does not mention anywhere, as to what is going to be installed in this guide. Big clue to its apparent vagueness, and the easiest one
One could gather from the topic that it could be an installation guide for getting the new bootloader onto your phone.
And / or an installation of a custom rom... called "ultimate"?
Installation guide for installing DCDs kitchen, or perhaps just one of his roms.
"" "" "" the ppcgeeks official titan kitchen, using no2chem 5054 (or 5060)
You getting the picture now ?
It is very vague. And when I mentioned that, it was not a complaint... rather a friendly suggestion that the topic title should be changed to accurately reflect the content of this guide. Thus, helping to attract more users who are needing help with this because they can see by the thread title, that inside is something that could help them out in a big way.
Just trying to get this out there more for those who could use it.
Hi All,
I have been trying to get the FW update with extreme save mode for almost a week now.
I check for software updates daily and I get the NO UPDATE found message.
Called At&t and tech support is as useful as my 3 years old kid.
Does anyone have the same problem? Solutions?
Thanks
Unlock bootloader, install Android Revolution thats been updated with latest release and you are good to go. No reason to wait till they let it work for yea when you can do it yourself.
JayRolla said:
Unlock bootloader, install Android Revolution thats been updated with latest release and you are good to go. No reason to wait till they let it work for yea when you can do it yourself.
Click to expand...
Click to collapse
Thanks for the advice, but others are getting the update OTA, without root or downloading Android Rev.
Some M8 owners may see a delay in getting the OTA, as it rolls out sequentially, by some means (I've seen AT&T suggest its by IMEI number). A minority of folks will never get it, just by some random fluke or other (as happens on any OTA).
If you don't want to wait, the RUU is already posted. You can download to a PC, and run it with your phone connected. But it will wipe user data.
http://forum.xda-developers.com/showthread.php?t=2757462
redpoint73 said:
Some M8 owners may see a delay in getting the OTA, as it rolls out sequentially, by some means (I've seen AT&T suggest its by IMEI number). A minority of folks will never get it, just by some random fluke or other (as happens on any OTA).
If you don't want to wait, the RUU is already posted. You can download to a PC, and run it with your phone connected. But it will wipe user data.
http://forum.xda-developers.com/showthread.php?t=2757462
Click to expand...
Click to collapse
Thanks for the tip, I tried that and it wouldn't work. Do I need root or s-off?
Also, has everyone that attempted to download things manually received the update?
I would really appreciate the responses
sassij said:
Thanks for the tip, I tried that and it wouldn't work. Do I need root or s-off?
Also, has everyone that attempted to download things manually received the update?
I would really appreciate the responses
Click to expand...
Click to collapse
How did it not work? As long as you are completely stock with cid cws__001 it should work.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
sassij said:
Hi All,
I have been trying to get the FW update with extreme save mode for almost a week now.
I check for software updates daily and I get the NO UPDATE found message.
Called At&t and tech support is as useful as my 3 years old kid.
Does anyone have the same problem? Solutions?
Thanks
Click to expand...
Click to collapse
download ota package from here http://www.androidfilehost.com/?fid=23487008491963146
put it on your micro sd card
boot to recovery "vol up and power 10 sec, vol down and power until boot loader comes up and navigate to recovery"
once in recovery its either vol up and power or vol down and power for a few seconds for advanced options
choose install update from external sd.
sassij said:
Thanks for the tip, I tried that and it wouldn't work. Do I need root or s-off?
Click to expand...
Click to collapse
No, the phone does not need to be modded to run the RUU. Its a "official" update/recovery tool provided by HTC. If you phone is stock, it should work, as the above response also indicated.
If it "wouldn't work" it would be more helpful to give details, if you want proper help. Not just say it didn't work. What step did it fail at , any error message, etc. Also, the current state of your phone (root, unlocked bootloader, etc.), as we can only assume based on your comment about root, etc.
RUU failing on a stock device is usually a USB connectivity issue on the part of your computer (not a problem on the phone's side). Install or re-install the HTC drives, try a different USB port, or a different computer (if available). If on Windows 8.1, that version is a known issue and will not work with the HTC drivers. You can also try re-downloading the RUU to make sure it wasn't damaged/corrupted during download.