Android OS Forum banner

Droid X OTA .605 coming soon (but don't waste your time)

9590 Views 58 Replies 22 Participants Last post by  PappaFloyd
Okay supposedly Moto and VZW are deciding to release this build that is slower and buggier than .602 after I tested it (without permission but still). It's supposed to fix one mysterious keyboard bug no one knows about, so congrats to Moto and VZW for another crap update.
1 - 20 of 59 Posts
Any 605 roms yet?
bobAbooey said:
Any 605 roms yet?
Nope. I'm going to bed, night.
bobAbooey said:
Any 605 roms yet?
Nobody has done anything with it at all other then the people who tested it in the other thread.
"anrichardson said:
Nobody has done anything with it at all other then the people who tested it in the other thread.
It was a joke.
The bugs that I have I ran into when testing it.

1) At first it seems snappy, but adding a few LPP widgets, it lost it's snappyness

2) The battery gets hot like it did when it was on version .596 (even after everything was done syncing)

3) When the phone is plugged to be charged, it becomes very unresponsive. Or maybe very laggy, trying to catch up to what you are wanting to do.

Side note: One thing I didn't do was factory reset, but who is going to do a factory reset after doing an update?
hoodlum47 said:
Okay supposedly Moto and VZW are deciding to release this build that is slower and buggier than .602 after I tested it (without permission but still). It's supposed to fix one mysterious keyboard bug no one knows about, so congrats to Moto and VZW for another crap update.
i'm not trying to say moto doesnt screw up, but i think it's unfair that you're judging the performance of an update based on the 8mb leak that you pulled, when it's being reported that the actual update is 113mb.

Isnt it possible that the one you pulled is an early test build with random bugs?
razorloves said:
i'm not trying to say moto doesnt screw up, but i think it's unfair that you're judging the performance of an update based on the 8mb leak that you pulled, when it's being reported that the actual update is 113mb.

Isnt it possible that the one you pulled is an early test build with random bugs?
This is from Verizon's site here

Note: The size for this software upgrade may be up to 113MB. This may be a multiple set upgrade depending on your
software version
. If your device is not on a latest software version, please perform the steps in the section below twice.
Plus, if it was an earlier build, then the lates build should be .606 at least.
anrichardson said:
This is from Verizon's site here



Plus, if it was an earlier build, then the lates build should be .606 at least.
ah...i see now. didnt know about that. thanks for the info. still, i'll wait and see if the ota is the same.
hoodlum47 said:
Okay supposedly Moto and VZW are deciding to release this build that is slower and buggier than .602 after I tested it (without permission but still). It's supposed to fix one mysterious keyboard bug no one knows about, so congrats to Moto and VZW for another crap update.
I have a hard time believing they would take a step backwards to fix keyboard issues I don't think I've ever experienced. Who knows though..
"blaineevans said:
I have a hard time believing they would take a step backwards to fix keyboard issues I don't think I've ever experienced. Who knows though..
I work at a vzw retail store and the keyboard problem is horrible... I've seen around 15 x's with it... the keyboard freezes on your screen when you press the space bar... factory reset is the only thing that fixes it... for people like us it makes zero sense for the. 605 update since this bug only seems to affect stock... but its a severe problem... but losing performance.... moto/vzw need new devs :)
  • Like
Reactions: 1
johnfranckiv said:
I work at a vzw retail store and the keyboard problem is horrible... I've seen around 15 x's with it... the keyboard freezes on your screen when you press the space bar... factory reset is the only thing that fixes it... for people like us it makes zero sense for the. 605 update since this bug only seems to affect stock... but its a severe problem... but losing performance.... moto/vzw need new devs :)
Interesting. Had no idea. I'm on stock pretty often as well using the stock multi-touch keyboard. Guess that's just luck! *Knocks on wood.

Thanks for the info though.
johnfranckiv said:
I work at a vzw retail store and the keyboard problem is horrible... I've seen around 15 x's with it... the keyboard freezes on your screen when you press the space bar... factory reset is the only thing that fixes it... for people like us it makes zero sense for the. 605 update since this bug only seems to affect stock... but its a severe problem... but losing performance.... moto/vzw need new devs :)
is the bug only w/ the stock kybd? i've experienced this to varying degrees on almost every ROM i've been on, even when applying the ROM from an sbf. this is w/ the Swype beta as well as SwiftKey X, moreso w/ Swype. it happened to me 5 times while typing this post using SwiftKey X. i'm on Shuji 2.2 from the TBH 602 sbf, rooted w/ the one_click method, ALL apps installed from the Market.
hoodlum47 said:
Okay supposedly Moto and VZW are deciding to release this build that is slower and buggier than .602 after I tested it (without permission but still). It's supposed to fix one mysterious keyboard bug no one knows about, so congrats to Moto and VZW for another crap update.
You're coming off as pretty arrogant and ignorant here. You pulled an unverified update, which was only 8mb and still filenamed 602, and are assuming its the official update. I'd save my judgment until the real update is released and hold off on the criticism until then.
"Detonation said:
You're coming off as pretty arrogant and ignorant here. You pulled an unverified update, which was only 8mb and still filenamed 602, and are assuming its the official update. I'd save my judgment until the real update is released and hold off on the criticism until then.
Well the update is .605 and is signed by motor/Verizon. That's why it worked in stock recovery and changing it to update.zip. Some of us have already installed it.

I like posted earlier to razor. The file size could be UP TO 113mb depending on what version you are on. So when he pulled it, he was on .602. Try reading the whole thread before you sound ignorant.
Official OTA updates are always named for the build it is installing over.
I won't even bother. I never had the keyboard bug that it's trying to fix and I was on stock 602 for a number of weeks. Now that I'm on Rev's CM4DXGB my battery life is nearly equivalent to stock, but with much better responsiveness and functionality. If I want to go back I'll just restore my nandroid.
I am currently on .605 (day 2 now) with everything running just fine.. better than ever actually, and I haven't even removed any bloat or overclocked it yet... Just running ADW EX with everything else stock and about ~60 apps loaded.
.
Here are the steps that I took to get from my previous ROM which was VorteX Alpha 1.4.1 to rooted .605 (and a big thank you to all of the developers who do all the real work to make this stuff possible!)
.
Note: Some of this might be over-doing it but all I can say is that it has been problem free for me.
.
-Copy .605 zip to SD card root as update.zip
-Reboot into Clockwork Recovery
---format cache, data, system
---factory reset
-Reboot into stock bootstrap (camera + vol down + power)
-SBF to latest .602 from TBH
-Reboot into stock recovery (home + power)
---factory reset
-Reboot into stock recovery
---apply .605 update.zip
-Reboot into stock recovery
---factory reset
-Reboot into Blur
---activate phone
---enable USB debugging
---connect USB to computer in phone mode
---root from computer using Pete's 1-click root
---install Clockwork Recovery
-Reboot into Clockwork Recovery
---format cache
---factory reset
-Reboot into Blur
---set up phone as usual
See less See more
Did you guys know when you format data in CWR it also formats cache? Just sayin....
1 - 20 of 59 Posts
This is an older thread, you may not receive a response, and could be reviving an old thread. Please consider creating a new thread.
Top