Going back to older ROM

[bakntyme]

Originally Posted by ImCoKeMaN

Just a little more clarification, and i do understand what you're saying ppc_n00b. The final step i took when my phone died was to flash a full 2.17 rom, so i have reasons why i said what i said. Until now i still have not seen any verified proof of a radio version being downgraded after a 3.16 or 3.35 rom was installed with it's radio. I currently do not know any way to revert that as it is protected from being over written and any attempt to revert is dangerous as you can see =)

PS: that does include the post you linked as well as far as i can tell.

Just on the off chance that it will make any difference in your attempts to find the problem...I don't have verified proof, but back in January I did install the 3.16 pre-release package and then reinstall the 2.17 stock package. It did not cause any issues. I have since installed the 3.35 package. The closest thing to proof that I have is this post on another forum from January stating that I did so.
http://forums.buzzaboutwireless.com/....id=2979#M2979

[tivoboy]

I had a bunch of LAGGY problems with the new ROM, and disabled the NEW TAKS MANAGER. I haven't had the laggies at all since 48 hours. I put in the regular HTC X button manager, so I have single point to kill applications, but I have the feeling that the STOCK ROM TASK MANAGER is sapping resources

[ImCoKeMaN]

Originally Posted by bakntyme

Just on the off chance that it will make any difference in your attempts to find the problem...I don't have verified proof, but back in January I did install the 3.16 pre-release package and then reinstall the 2.17 stock package. It did not cause any issues. I have since installed the 3.35 package. The closest thing to proof that I have is this post on another forum from January stating that I did so.
http://forums.buzzaboutwireless.com/....id=2979#M2979

Well, what i really would liked to have known is what radio version you had on the device at that point. From the boot up i supposed it might actually look like the 2.17 versions radio, but the level i am looking at myself and others have not been able to overwrite with any nbh. I'm not really meaning to be cryptic, but i don't really know a good way to explain it. The radio is actually made of different parts and the part that i can actually access on my phone at this moment is still the same as the one from the 3.16 update i did. I have since put on the 3.35 and went to revert to the 2.17 (bricked in this process, but there were other variables). There are all sorts of different combinations of those parts that could have occurred, but i can't really backtrack at this point and as it's bricked i can't even access all of it to verify. This is what i mean by radio not being over written and my one statement of "it can't be done." =) I'm actually looking at the ram and doing a hex dump looking for version strings and comparing to rom radio updates for this info.

[shadowmite]

To confirm what cokey has said, to date we have been unable to overwrite a gps enabled 3.x radio with any non gps enabled radio. These radio's have a different nbh header ID given to the bootloader for writing. Non gps radio's are a 0x300, gps radio's are 0x785. If you flash a 2.17 rom onto a 3.x radio device, it might work and appear to be back to normal, but I highly doubt you have flashed back the radio as we have specifically tried to accomplish this for days without success.

Be warned, this is dangerous territory as cokey himself has bricked a device in this process.

[freeza]

if downgrading from the beta rom that was released a while ago was possible, why not this one?

[ImCoKeMaN]

it wasn't fully, if you read carefully you'll see i still have the 3.16 radio (the beta) on my device that is bricked even after loading other roms. No GPS radio has been fully over written on a titan

[puff]

Originally Posted by ImCoKeMaN

Just a little more clarification, and i do understand what you're saying ppc_n00b. The final step i took when my phone died was to flash a full 2.17 rom, so i have reasons why i said what i said. Until now i still have not seen any verified proof of a radio version being downgraded after a 3.16 or 3.35 rom was installed with it's radio. I currently do not know any way to revert that as it is protected from being over written and any attempt to revert is dangerous as you can see =)

PS: that does include the post you linked as well as far as i can tell.

Well, perhaps i should have just referenced the entire thread, based on this post toward the beginning, we have 3.35 ROM loaded, which would include the 3.35 Radio...

Originally Posted by gregshap

I now have the Sprint 3.35 ROM with a custom ROM after config'd for Verizon.

Then later on, a few pages later...

Originally Posted by gregshap

*Burned it back to 1.06 bootloader from 1.20.
*relocked it.
*burned it back to Verizon stock again.
*then went to 2.06 Bootloader.
*Loaded Stock Sprint 3.35 which gave me 2.4 bootloader.

Which would imply that the Radio was overwrote, or perhaps not, back to the Verizon Stock? but here's another thread, for reference in this dangerous endeavour

-> http://forum.ppcgeeks.com/showthread.php?t=23565

Red indicates what i think was mispelled

Originally Posted by mommasboy

On my first try I flashed 3.35 from 2.17 and noticed that my Bootloader number was 2.0. I tried to flash a custom and it didn't work. So next I figured it didn't work because i didn't unlock it. Once I unlocked it my bootloader went back to 1.20. Next I tried to install olipro's 2.40 and it starts to install, but then I get an error 260. I disabled activesync and that didn't work either. I can't get 3.35 back, but I love the custom roms that u guys provide. Can anybody help me, i don't k now what to do next.

Originally Posted by PPC_N00B

what bootloader and radio do you have currently?

Originally Posted by mommasboy

1.47.1 radio and oli's 1.20 bootloader and 2.17 rom, i'm about to flash back to the 3.35 rom.

There's been more posts that ive seen about this subject, but not near as many as the "i think i bricked my mogul" posts that are everywhere. And perhaps it's a mute point, since it's only a minority that wants to downgrade from 3.35 AND the high risk involved.

Thanks for your reply!

[puff]

Originally Posted by ImCoKeMaN

Well, what i really would liked to have known is what radio version you had on the device at that point. From the boot up i supposed it might actually look like the 2.17 versions radio, but the level i am looking at myself and others have not been able to overwrite with any nbh. I'm not really meaning to be cryptic, but i don't really know a good way to explain it. The radio is actually made of different parts and the part that i can actually access on my phone at this moment is still the same as the one from the 3.16 update i did. I have since put on the 3.35 and went to revert to the 2.17 (bricked in this process, but there were other variables). There are all sorts of different combinations of those parts that could have occurred, but i can't really backtrack at this point and as it's bricked i can't even access all of it to verify. This is what i mean by radio not being over written and my one statement of "it can't be done." =) I'm actually looking at the ram and doing a hex dump looking for version strings and comparing to rom radio updates for this info.

So to clarify, you bricked the other mogul in an attempt to go from 3.35 official Sprint Rom to the 2.17 official Sprint ROM? did you flash bootloader 1.20 first? nothing to do with wM5? perhaps thats another story/brick? if so, soon you will have that patio !!!

Originally Posted by shadowmite

To confirm what cokey has said, to date we have been unable to overwrite a gps enabled 3.x radio with any non gps enabled radio. These radio's have a different nbh header ID given to the bootloader for writing. Non gps radio's are a 0x300, gps radio's are 0x785. If you flash a 2.17 rom onto a 3.x radio device, it might work and appear to be back to normal, but I highly doubt you have flashed back the radio as we have specifically tried to accomplish this for days without success.

Be warned, this is dangerous territory as cokey himself has bricked a device in this process.

Thank you for that explanation!!!
So you are saying that even if 2.17 Flashback appears to be successful,
that the Radio would prolly still be 3.35 or 3.27 (depending on the Radio prior)

Hmm, RAM addresses, hex dumps, man i need to learn more!!!
If only i had an xtra 6800 for experimenting...

Originally Posted by ImCoKeMaN

it wasn't fully, if you read carefully you'll see i still have the 3.16 radio (the beta) on my device that is bricked even after loading other roms. No GPS radio has been fully over written on a titan

Upgrading is different though, right?
you can upgrade 3.16 to 3.35 and that will overwrite the GPS 3.27 Radio to 3.35, correct? can you also go from Radio 3.35 -> 3.27 or do you think that would brick as well?

Thanks again for both of your replies,

P.S. have you see this ->

[bakntyme]

Originally Posted by ImCoKeMaN

Well, what i really would liked to have known is what radio version you had on the device at that point. From the boot up i supposed it might actually look like the 2.17 versions radio, but the level i am looking at myself and others have not been able to overwrite with any nbh. I'm not really meaning to be cryptic, but i don't really know a good way to explain it. The radio is actually made of different parts and the part that i can actually access on my phone at this moment is still the same as the one from the 3.16 update i did. I have since put on the 3.35 and went to revert to the 2.17 (bricked in this process, but there were other variables). There are all sorts of different combinations of those parts that could have occurred, but i can't really backtrack at this point and as it's bricked i can't even access all of it to verify. This is what i mean by radio not being over written and my one statement of "it can't be done." =) I'm actually looking at the ram and doing a hex dump looking for version strings and comparing to rom radio updates for this info.

At this point there probably isn't any way to tell what parts of the radio were or were not properly overwritten in the downgrade process. All I know is the boot-up and Device Info screens displayed the proper radio version, and it worked properly for about six weeks until I installed the official stock 3.35 package. I also remember trying to use the internal GPS after downgrading the ROM, hoping that some settings were left behind, but it did not work.

This stunt was performed by someone with an apparent abundance of pure dumb luck; do not try this at home.

[EtherealRemnant]

I'm curious about this too.

I may be willing to experiment with this... I need a new device anyway. Mine has a white spot on the LCD, is missing the letter S on the keyboard, and has been dropped more times than I can count.