Going back to older ROM
 

Ok, so I upgraded (finally) to the new Rom 3.35 and I am not happy at all with the new performance. It lags worse then the previous ROM, it always freezes when sliding the phone. Sometimes when it rings, it'll stay frozen even when I hit the send or end buttons and continue to ring.

1) Does anyone else have this problem?

2) Is there anyway to revert to the previous Rom versions? I downloaded 2.17 and tried installing it but it told me that it is invalid.

Any suggestions?

Re: Going back to older ROM
 

Don't revert to 2.17 there is a strong chance you will brick your phone! 3.35 has been the snappiest stock rom ever for me though.

Re: Going back to older ROM
 

just curious, Y is there such a strong chance of bricking if you downdate vs update? other than the lack of tutorials and info on downdating is it possible to revert to a prev Radio version and prev ROM? again, not planning on it... just curious

Re: Going back to older ROM
 

The GPS radio is a new beast, it protects itself from overwriting. Before this rom we were free to go back to WM5 at any point (check my sig). The new GPS radio is highly dependent on the OS and SPL as well and not compatible with previous versions. This puts it in a inconsistent state when you try to revert and the radio protection keeps you from fully going back. Mine are in a black screen called download mode at the moment. If they become fixable there will be a post about it as soon as it's ready.

Re: Going back to older ROM
 

Out of curiosity, have you tried yet simply doing a hard reset? While I haven't actually used 3.35 (stuck to customs ever since 6.1 became available), I've overall heard nothing but compliments for 3.35's improved performance, so your problem sounds unusual. That said, occasionally people just get a bad session and hard-resetting has frequently been known to clear up issues despite the fact that you're running the same ROM. I'd strongly recommend that before considering a new ROM altogether.

Re: Going back to older ROM
 

ok. so it appears to be possible, but HIGHLY not recommended. you mention WM5 but

it appears that he still wants WM6 but just not the GPS flavor, not sure why - but anyway, in theory you could flash 1.20 bootloader, then the official 2.17 ROM to match the Radio, OS, and bootloader, then install a custom ROM that matches...



your sig says
what is the Special_4350.nbh used for? care to elaborate?

Re: Going back to older ROM
 

What i'm sayin is it's not possible, don't do it. <- PERIOD

Re: Going back to older ROM
 

When you refer to "sliding the phone" - my assumption is that you're talking about using a program like S2U2 or Slide 2 Unlock, right? I'll say this much - while I need the functionality that this app provides (so I don't pocket dial so darn much) - it definitely has a major impact on the overall performance of my phone. After I upgraded to the latest using DCD's kitch/rom - my phone seemed to operate pretty darn well - until I put the latest S2U2 on it. Now its got all sorts of flakey problems. I think that app is probably more to blame than anything...

Ultimately - I blame Windows Mobile as the root cause for most problems - simply because it seems that folks can't get solid/dependable performance unless they mix different concotions of apps/settings/tweaks to get their phones to work adequately...never had this problem with a Blackberry - but, then again - the Blackberry didn't have all the "potential" features as this device either <sigh>....darned if ya do - darned if ya don't...

Re: Going back to older ROM
 

thanks for your reply, although it was not helpful. didn't answer my questions, and seems more like you have the attitude of "do as I say because I tell you to"

Re: Going back to older ROM
 

no way i'm getting in the middle of this one.. oh, wait, i just did. yikes.
well anyway, i'm taking cokemans comment as one where he is trying to state 'you better not do this or you'll be sorry' kind of comment.. which frankly, is good enough for me !
although i can see your point PPC..... just carry on is all......

Re: Going back to older ROM
 

He is telling you because he knows from experience that you can truely brick your phone as he has actually done it. If that is not enough warning for you, then I am sorry.

Re: Going back to older ROM
 

Thank you Nickles. My post was a warning as the GPS radio is write protected (can not be overwritten) and any attempt to revert could cause issues. I have 2 bricked devices to prove it. Any further discussion is off the topic of the OP. I have other posts further documented what i did though. As for the attitude, this is a forum, its text sorry it came accross poorly. I was being blunt as a warning.

Re: Going back to older ROM
 

i could never go back to any older Rom. this is by far the best sprint rom period

Re: Going back to older ROM
 

thanks - really doubt that i personally will ever want to downgrade.. not to say others like the OP wont though

i have searched and found nothing useful on the special nbh you mention in your sig - which you referenced - something about it allows you to access the lower level programming, but nothing that i can tie to the downgrade process. while it sounds like you reluctantly might admit that it might be possible to downgrade, but there's very high chance of failure due to the Radio write protection, so dont do it. when i get the time, since i'm interested in learning more about what exactly u did to brick your titans, and what the special nbh file does... unless want to post a link to these more than likely scattered "further posts" i'll research more...

further discussion would entail that your wrong, but hopefully someone will figure out a way to successfully overright the GPS Radio w/out it causing the dreaded "download mode"


*edit*

did research a little and found that you have at least one bricked mogul, and one bricked touch. based on the following posts it looks like you had a failed radio port to the touch and flashed the special nbh on the mogul.

-> http://forum.ppcgeeks.com/showthread...728#post222728

-> http://forum.ppcgeeks.com/showthread...728#post233056

Phone won't start-no bootloader
http://forum.ppcgeeks.com/showthread.php?t=20882

-> http://forum.ppcgeeks.com/showthread...262#post235262

great explanation btw

-> http://forum.ppcgeeks.com/showthread...287#post233287

ROFLMAO - that's just a great post

so in reference to the other mogul brick, did you attempt 3.35 (GPS) downgrade to 2.17 (Non-GPS) as the OP asked? or did you try to downgrade to WM5 w/ the GPS Radio? (reference to sig)

Re: Going back to older ROM
 

I wish it was possible to go back to 2.17. :( I don't need the GPS, and for whatever reasons I had far superior speeds with that rom than I do with the new one here in Houston.

](*,)

Re: Going back to older ROM
 

eric, i would just like to add to that:

Re: Going back to older ROM
 

Have you tried turning off the keyboard slide sound? That silly sound tends to cause a lag.

... A hard reset might be the solution. Possibly you've made a reg tweak that messed things up and you didn't realize it. 3.35 is working great for me, best ROM yet by far on the Mogul.

Re: Going back to older ROM
 

PPC-NOOB!!!! Cease and Desist! IMCOKEMAN was/is a large contributor to any of us being able to switch ROMS. Show some respect and DO AS HE SAYS.

Re: Going back to older ROM
 

First let me say that i do respect ImCoKeMaN, and im very aware of his contributions to this community, and i dont think i can express enuff how grateful i am for those contributions!!!

That being said, just because you respect someone, doesn't mean that you agree 100% with everything they tell you and do as they command. And if there's a rule that says you are not allowed to speak your mind, please point that out, so that i may comply with your request to "cease and desist" - but until then.....



Now due note that if you carefully read thru my posts you will find that i have done a fair amount of research on this topic and have found that (as prev mentioned) 2 devices ImCoKeMaN has were bricked, but not as a result of downgrading. One was the result of a failed radio port (HTC Touch) and the other was flashing the special.nbh that was incl in the ROM update, now the 3rd it appears he attempted a downgrade that failed, possibly to WM5, not sure, but if you search you can find posts like say for example this one, where users have successfully completed this "impossible" task. in this example it was a verizon 6800, maybe that makes a difference, maybe they just got lucky, but never the less, i'm still curious...

http://theage.com.au/ffximage/2006/0...b__300x375.jpg



One Final Note: Thanks for the flame :mrgreen:

Re: Going back to older ROM
 

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.

Re: Going back to older ROM
 

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

Re: Going back to older ROM
 

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

Re: Going back to older ROM
 

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.

Re: Going back to older ROM
 

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.

Re: Going back to older ROM
 

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

Re: Going back to older ROM
 

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

Re: Going back to older ROM
 

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...

Then later on, a few pages later...

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
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!

Re: Going back to older ROM
 

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 !!!

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...

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 -> http://www.robotics.net/images/cokeman.jpg

Re: Going back to older ROM
 

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.

Re: Going back to older ROM
 

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.

Re: Going back to older ROM
 

@ ImCoKeMaN - did you install olipro 1.20 when attempting to downgrade to 2.17?

The reason i ask, is that in the thread HTC Splash Screen says no radio it appears that at least one or two people went from 3.35 to 2.17 by "accidentally" installing olipro 1.20 instead of olipro 2.40

Re: Going back to older ROM
 

That's interesting...

i upgraded to the beta rom the very same night it was released and hated it, so i reverted back to 2.17 with no problems... and here i am with the same phone, and the upgraded 3.35 rom...

Re: Going back to older ROM
 

i made an account just so i can reply to this msg... i had the same problem, i didnt read the instructions on the relocker thoroughly enough and i used the relocker on a "RUU_TITAN_SPRINT_WWE_3.35.651.2_RS_TITAN_3.35.04_ 4350H_SPCS_AM_Ship" phone.. and thought i had bricked it

i am using a verizon vx6800.. i now have the phone working again

i do not know much about this ppc business but i thought my posting would help more than hurt

what i did was run the ROMupdateutility under the RUU folder.. i would love to give more specifics to which ROM it was i installed, but the .nbh file under the folder is just simply titled "Ruu_signed.nbh".. and as i've been trying to fix this problem i downloaded about 8 different roms both official and custom so i cant specify which one this is exactly.. if it helps the size is "78.9 MB (82,756,469 bytes)"


hope this helps people to a certain extent.. if anything, i hope this lets people know that it IS possible to downgrade from a 3+ and get it working again..


to give additional details...


i had a brand new vx6800
tried to install a cusom dcd 3+
used unlocker 1.2 (instead of the 2.4 like im supposed to)
got stuck so installed an older versio of dcd >2
installed the official 3+
tried to install custom dcd 3+ again


this is where the hell began


the bootscreen said i had 1.20 olipro.. so i tried to isntall 2.4 and failed. so assuming i had to relock 1.20 before i can install 2.4, i did so. and CRASH!




afterwards i just started trying to install every single rom/exe i had that i downloaded for the phone, thinking my phone was gone forever. but that one file under the RUU folder helped.


i do hope this post helps some people, as vague as my solution seems. any specific questions, just ask i will be happy to reply with as much details as possible



best of luck

Jay