This is a discussion on Droid X: Bootloader 30.03, Err:A5,70,00,00,23 within the Droid X Rescue Squad forums, part of the Droid X Discussion category; Whew! Taking a crash-course on Froyo, Gingerbread, Bomb Pops, Push-Ups, molten lava cakes, 4.5.621, 4.5.605, 2.3.3, rooting, SBFing, OTAing, hair pulling, and all that techy ...
Whew! Taking a crash-course on Froyo, Gingerbread, Bomb Pops, Push-Ups, molten lava cakes, 4.5.621, 4.5.605, 2.3.3, rooting, SBFing, OTAing, hair pulling, and all that techy Droid X stuff...I'm sizzling in the pan.
Right now, I've got Verizon trying to push their damned update down my throat again.
Here's where I am...
Yesterday, the phone was fine, then Verizon shoved their update down my throat and it killed the phone. Verizon says, "Dead." A new warranty phone arrives today. I went home and, as posted above, found this forum and fixed the phone by downloading the Froyo file.
But, now I've got Verizon trying to push the 4.5.621.en.US update onto my phone again, which killed it yesterday.
Researching, it doesn't look like there is anyway to stop the download, unless I am misunderstanding.
What should I do? Root? It sounds cool, but I don't want to have to jack with my phone. I just want it to run, leave me alone, and I want to kill the Verizon/Google midget living inside of it that keeps telling me I have "1 hour" before a "7 minute" update kills my phone again.
Here's what my phone says:
System Version: 4.5.605.mb810.Verizon.en.US
Model #: Droid X
Android Version: 2.3.3 (Gingerbread, right? Which doesn't make sense to me, because I used that Froyo image thingy to fix it yesterday--of course, maybe Verizon forced an update on it when I wasn't looking, or maybe I said yes when I meant to say F off)
Baseband Version: BP_C_01.09.13P
Kernel Version: 2.6.32.9-g34b306d, bmvq37@zin22lnxdroid28#1
Build #: 4.5.1_57_DX5-35
ERI Version: 5
PRL Version: 52363
The Verizon System Update that it is trying to make me install (in one hour...blah) is 4.5.621.en.US
Can I do anything to make my phone stay right where it is and ignore Verizon for the rest of my life?
You could root. Or you could take the update. If the update fails you can just do what you did in thr first place to save your phone but you can do it to 621
I am having the same problem... my phone decided to updated without me saying yes.... can someone please walk me thru how to fix it... I am not real technical...
Verizon is trying to promote another update under its throat.
We all know what .621 is at this point. I think .621 was the sneakiest thing they could have done. Breaking reversion and root all in one fell-swoop WITHOUT changing bootloader versions (so we had no way of knowing so) plus the update bricking phones half the time people try to take the OTA... that's crap. No idea what the OTA issues are personally, I had SBF'd to it and I've never done a single OTA on my phone. There isn't much Verizon could do beyond that besides just sending out an update that hard-bricks all DXs. That's almost what the .621 did. I know at least 3-4 people who took the soak test and then when they attempted an SBF back they soft-bricked and with no .621 SBF there stuck with bricked phones that Moto refused to fix despite the fact they were SOAK TESTERS for them and their update BRICKED the phone. Same with if its bricked on the OTA, if you take it to Verizon they will refuse to fix unless you have insurance, even if you were stock unrooted and the OTA bricked it.
We all know what .621 is at this point. I think .621 was the sneakiest thing they could have done. Breaking reversion and root all in one fell-swoop WITHOUT changing bootloader versions (so we had no way of knowing so) plus the update bricking phones half the time people try to take the OTA... that's crap. No idea what the OTA issues are personally, I had SBF'd to it and I've never done a single OTA on my phone. There isn't much Verizon could do beyond that besides just sending out an update that hard-bricks all DXs. That's almost what the .621 did. I know at least 3-4 people who took the soak test and then when they attempted an SBF back they soft-bricked and with no .621 SBF there stuck with bricked phones that Moto refused to fix despite the fact they were SOAK TESTERS for them and their update BRICKED the phone. Same with if its bricked on the OTA, if you take it to Verizon they will refuse to fix unless you have insurance, even if you were stock unrooted and the OTA bricked it.
That might be the best worded paragraph about Verizon's 621 update I've heard. Absolutely ridiculous they did it
That might be the best worded paragraph about Verizon's 621 update I've heard. Absolutely ridiculous they did it
FreeMyMoto!!!
With the rant over, I can honestly say though that the 15p radio is pretty bomb, and I'm pretty sure I get incrementally better performance on the .621 kernel.
Its just unfortunate it had to come with all the hooks and qualms it did. Pain in the butt to root (I don't mind the 1KDS ISOs and definitely appreciate the effort and assistance it has provided to thousands of people but I've always used RSD prior to this as I have no issues with it and find it quite a bit faster.) and its painful not being able to revert. I'm pretty much always on GB and ICS, but its frustrating from a development standpoint. When I wanted to test some stuff on the .15p radio flash I was unable to test it myself as I was stuck and jammed on it. Eventually I just put it off on working further because I feel bad having people brick phones for me and I can't get a proper logcat or whatnot that is needed from a development standpoint. Just a royal pain.
With the rant over, I can honestly say though that the 15p radio is pretty bomb, and I'm pretty sure I get incrementally better performance on the .621 kernel.
Its just unfortunate it had to come with all the hooks and qualms it did. Pain in the butt to root (I don't mind the 1KDS ISOs and definitely appreciate the effort and assistance it has provided to thousands of people but I've always used RSD prior to this as I have no issues with it and find it quite a bit faster.) and its painful not being able to revert. I'm pretty much always on GB and ICS, but its frustrating from a development standpoint. When I wanted to test some stuff on the .15p radio flash I was unable to test it myself as I was stuck and jammed on it. Eventually I just put it off on working further because I feel bad having people brick phones for me and I can't get a proper logcat or whatnot that is needed from a development standpoint. Just a royal pain.
Well hey. When I come up there in October I'll bring my phone and give it to you haha you just gotta figure out what's wrong with it.
But I was a lucky one and never got the 621 update so I cannot speak of performance wise but I just see it as a stab in the back move, of course with the radio it was a major update to nonrooted DXs. Theres always two sides to an agruement.
And also question.. secret shadow build. Is that what I think it is? Shadow being CM codename and you're talking about development point. I have a feeling something big is being cooked up haha
LinkBack URL
About LinkBacks
View Profile
View Forum Posts
View Forum Threads
Show All Albums
Private Message
Reply With Quote
Originally Posted by LorettaGibbs
