- 02-21-2012, 01:29 AM
Thread Author #1
- 02-21-2012, 07:35 AM #2
Re: New Update!
- 02-21-2012, 08:07 AM #3
- 02-21-2012, 10:22 AM
Thread Author #4
Re: New Update!

I've was the 3rd person in line to get my X when it came out. I haven't been on these forums in awhile because, quite honestly, I thought Moto had given up on any updates on it in a year and a half.
I was excited to see this update cause I stream music a lot during my workout and it drives me crazy mad to be working out in a set and have it just stop..and look down to see it black. I've done everything I knew to fix it. I thought it was a clash with apps. I've deleted a bunch of apps, some I actually used, in order to troubleshoot it.
Be glad when I get it on my X.MAXX, XOOM and a Tab 2 all unrooted
How sweet...Your gramma let you borrow her iPhone..... - 02-21-2012, 12:49 PM #5
Re: New Update!
My buddy just got the update this morning and now his phone is bricked. It powers to the bootloader screen saying Battery Low. Critical Error. (Battery had been charging all morning).
Any ideas? where to find the orginal factory load to flash the device? He tried a factory reset, didn't work.
Oh, and a side note, he went to Verizon at lunch and was told tough luck, updates are pushed by Moto and if it breaks the phone, it's not covered under warranty (he has had the phone going on 2 years now). - 02-21-2012, 12:53 PM #6I am now in the Galaxy Nexus member's club as of Aug 2012. Late to the party, but well before it shuts down!
- 02-21-2012, 07:57 PM #7
- 02-21-2012, 09:28 PM #8
Re: New Update!
Question. If I never Updated to .602, can I still download the new Update and skip the .602 Update?
I never updated to .602, because I had a few problems just with the original GB update, with phone restarting after I try to turn it off and a few other random problems. I heard there were a lot of problems with .602 Update, so just been putting it off everytime my phone shows it wants me to load it. So just want to skip it and see if I can go to the new Update that's coming out. - 02-21-2012, 09:41 PM #9
Re: New Update!
What are you on currently .596?
I am now in the Galaxy Nexus member's club as of Aug 2012. Late to the party, but well before it shuts down! - 02-21-2012, 10:12 PM #10
Re: New Update!
Yes, still on .596, my phone reminds me every night to load the .602 update, but just push install later or hit the back button. Do I have to load the .602 to the phone, before I can update to the new one coming out? That's basicly my question, just would like to skip it if possible.
- 02-21-2012, 11:32 PM #11
Re: New Update!
As far as I know since it is a carrier push update singly you wont nor can get the 621 update until you have the radio file of the 602 installed so it knows to accept the push for the next in line update for 621. Someone may want to verify that but If Im not mistaken you must "follow the path"
I am now in the Galaxy Nexus member's club as of Aug 2012. Late to the party, but well before it shuts down! - 02-22-2012, 02:21 PM #12
Re: New Update!
is this available now? I tried to check for it maunally, and it tells me my phone is "up to date."
- 02-23-2012, 02:29 PM #13
- 02-23-2012, 09:32 PM #14
- 02-23-2012, 10:36 PM #15
- 02-23-2012, 10:43 PM #16
- 02-23-2012, 10:53 PM #17
Re: New Update!
I posted this in another thread, but didn't get a response yet. Hopefully this thread may be able to assist me.
My problem....
I previously used Droid 3 easy root script v7 to root my DX after a replacement DX with no problem. The problem I have now is that I can't do the update. I removed all traces of root (that I'm aware of) with OTA RootKeeper and then Ginger Unroot. Busybox and superuser are both off of my DX and none of my root apps will work. One would think my DX is unrooted........is it not? Any help would be appreciated. - 02-23-2012, 10:58 PM #18
- 02-23-2012, 11:50 PM #19
Re: New Update!
FYI
The best way to remove root from any rooted X is to .sbf it. It replaces the .su files with the locked system files an OTA carrier update comes with.
There is word now that once you take the .621 you cannot sbf back to a version below it and if you do try you will be stuck with a paperweight. According to online sources, it is going to be pretty tough to make a new .sbf for us but TBH and P3 I read somewhere are on the case like Matlock
Update path as far as I can remember for us was
.588 591. 596. 602. .605 .621
And you cannot go out of order either. The update wont push if it sees you dont have the proper path for the files to follow(radio, base, etc). So really read up on the .621 update before you get too excited about getting it. If you are fine on 602\605 then leave it there until the .sbf issue is solved. Might be a while.I am now in the Galaxy Nexus member's club as of Aug 2012. Late to the party, but well before it shuts down! - 02-24-2012, 05:22 AM #20
- 02-24-2012, 10:58 AM #21
- 02-24-2012, 08:35 PM #22
- 02-25-2012, 01:26 PM #23
Re: New Update!
Well, the update now makes the hard button lights go off when in the multi media dock! Yea! But I have lost root on my phone.
Willl just uninstalling superuser be good enough to get rid of all the root related files?
- 02-25-2012, 04:42 PM #24
Re: New Update!
Uninstalling Superuser.apk will delete the app from your phone. And now since you updated to .621 there's no SBF file yet to completely eliminate the sys write files root places so the best for now is boot into recovery and wipe system if you really need to.
I am now in the Galaxy Nexus member's club as of Aug 2012. Late to the party, but well before it shuts down! - 02-27-2012, 08:15 AM #25
Re: New Update!
update ran fine and the annoying camera settings bug (always go back to wide-screen) finally fixed. that one was driving me nuts. have not tested the random reboots w/music player yet, hard to reproduce on demand anyway.
unfortunately, the motorola exploit used to root GB seems to have been closed with this update. i lost root and cannot seem to re-root via pete's motorola root tool.
have to decide whether the update's benefits outweigh the loss of root!Last edited by jchasan; 02-27-2012 at 11:59 AM.



Reply

































