-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Another OTA floating about? (5.9.901)
- Thread starter amageus
- Start date
johnlgalt
Antidisestablishmentarian
nope - I'm a part of the soak testers group - we had no inkling this as even in the works - it just started appearing on ppl's phones.
Trust me this was not an NDA violation at all - it was a real leak.
Working on it, but I'm also packing to go to South Carolina, and that makes it difficult.
I'm a stickler for details and for anticipating common errors people make, and this process will soft brick your phone (at least temporarily, but for some users it might be permanent).
So, I need disclaimers, etc. plus I want to keep the post locked since there is already the other discussion thread I have created. And with me being out of town all weekend (and thus with limited access) I'm debating if I just point y'all to the thread where I got the info from until I come back, so I can be here for easy support when my guide goes public.
Decisions, decisions....
Well John yes you can send the link to the post that you found the information.
I have flashed my phone probably 30 time over the last 3 days.
Or just tell what you did in the pm. I am very savy on working thru the errors just not a developer. However I can follow directions and know how to use the motorola fastboot to flash the stock webtop and image. I also have flashed backed to the old radio. just the kernal I can not get to be correct. So either i need a way to get the correct radio flashed or revert back the kernal to the previous one. However you get the picture.
thanks
I have flashed my phone probably 30 time over the last 3 days.
Or just tell what you did in the pm. I am very savy on working thru the errors just not a developer. However I can follow directions and know how to use the motorola fastboot to flash the stock webtop and image. I also have flashed backed to the old radio. just the kernal I can not get to be correct. So either i need a way to get the correct radio flashed or revert back the kernal to the previous one. However you get the picture.
thanks
http://androidforums.com/bionic-all...ceive-otas-again-if-you-leak.html#post3709086
I followed the steps precisely as described and was able to revert my phone to stock 886 and just finished downloading the OTA. I was on 5.7.893 and am now officially back on the upgrade path ^^
edit: am now on 5.9.901 as well
I followed the steps precisely as described and was able to revert my phone to stock 886 and just finished downloading the OTA. I was on 5.7.893 and am now officially back on the upgrade path ^^
edit: am now on 5.9.901 as well
lykofos
Member
I was on the official 5.5.893 OTA, which made my data connectivity soooo much worse. The phone wasn't bad on .886, but I now have daily thoughts of throwing this phone under my truck and running it over just about everyday since the .893 release b/c of data loss issues.
I grabbed this 5.9.901 file on the 19th from a user on a different forum who had it officially pushed to him OTA. Finally broke down and decided WTH, I've got nothing to lose. Installing it now. I figure that motorola has no choice but to support this build since they officially pushed it to some people, so it's a lot safer bet installing it than installing a leak.
I'll report back in a few days on how its working for me.
EDIT: Installed successfully! On a side note, while the update was installing I realized I hadn't unfroze any of my frozen system apps in TiBu. Update still applied successfully though!
I grabbed this 5.9.901 file on the 19th from a user on a different forum who had it officially pushed to him OTA. Finally broke down and decided WTH, I've got nothing to lose. Installing it now. I figure that motorola has no choice but to support this build since they officially pushed it to some people, so it's a lot safer bet installing it than installing a leak.
I'll report back in a few days on how its working for me.
EDIT: Installed successfully! On a side note, while the update was installing I realized I hadn't unfroze any of my frozen system apps in TiBu. Update still applied successfully though!
Neither one of them are supported on your device by them. If they had pushed it to you then I would agree with your conclusion. They didn't.
The risk is all yours.
As for your original problem ... I saw a number of places here it was recommended that you replace the SIM card after upgrading to 5.5.893. Did you try that?
... Thom
lykofos
Member
That is a possibility I suppose, but do you think moto / verizon can really track who the update was officially pushed to vs it being installed from the sdcard? We have quite a few reports on the forums from people that received it OTA, so how many hundreds of people that aren't on any of the forums received it as well?
I guess I don't perceive it as great of a risk as a leaked cheesecake update that was never officially pushed OTA to anyone. If I'm wrong though, I can always use John's newly discovered way of reverting to the OTA path that he posted about over at rootzwiki. I guess no one should install this then if they don't feel comfortable with the possibility of maybe having to do that at a future point in time.
The pushers never told me who got them.
It was reported elsewhere that they were pushed to people who had submitted a bug report to Verizon about data drops.
I never submitted such a report. I am on 5.5.893 and 5.9.901 was never pushed to me.
If you do anything other than install the official production releases you are at risk and you are unsupported. Looking at worst case ... you could have to buy a new device for $600.
It seems likely that if you had stayed on the production path and submitted a bug report about data drops that you probably would be running on a supported copy of 5.9.901 now.
... Thom
It was reported elsewhere that they were pushed to people who had submitted a bug report to Verizon about data drops.
I never submitted such a report. I am on 5.5.893 and 5.9.901 was never pushed to me.
If you do anything other than install the official production releases you are at risk and you are unsupported. Looking at worst case ... you could have to buy a new device for $600.
It seems likely that if you had stayed on the production path and submitted a bug report about data drops that you probably would be running on a supported copy of 5.9.901 now.
... Thom
I have made the correction in a number of places where I referred to it as having been sent to soak test. Those places now refer to it as a leak.
I believe that I read in this forum where it was in soak test but I can not find that reference now.
Thank you for the clarification.
A number of us can stop bothering to check to see if an update is available. There shouldn't bean update until at least a day or two after something goes into soak test.
... Thom
I believe that I read in this forum where it was in soak test but I can not find that reference now.
Thank you for the clarification.
A number of us can stop bothering to check to see if an update is available. There shouldn't bean update until at least a day or two after something goes into soak test.
... Thom
lykofos
Member
Here's my review of .901 so far:
Living in a 4G fringe area, .886 was pretty good after I replaced my SIM card, but I still got occasional drops where I had to reboot / airplane toggle. I rate the phone at about 75% of data connectivity. Update .893 update made things exponentially worse for me, transitions required me to actually reboot (restart connections or airplane mode didn't restore connection like they did on .886), multiple times a day. I rate the phone at about 40% of data connectivity.
I've noticed a huge difference being on .901 so far. On .901, 3G to 4G transitions happen really quickly and have been flawless. 4G signal seems to be holding much stronger, and I have 4G and 3G connection in areas of the house i didn't before. Still have some dead spots in the house where I get no connectivity (seems like more of a network not a phone issue), but it'll transition from no connection to 3G - 4G quickly as soon as I move to an area of the house that gets signal.
I haven't had to reboot / airplane toggle once since the .901 update! I rate the phone at about 95% data connectivity now. I think the remaining 5% is probably just network issues / certain parts of the house causing poor signal transmission. For me, it's a vast improvement over .893 which was a total failure of an update for people in 4G fringe zones.
Living in a 4G fringe area, .886 was pretty good after I replaced my SIM card, but I still got occasional drops where I had to reboot / airplane toggle. I rate the phone at about 75% of data connectivity. Update .893 update made things exponentially worse for me, transitions required me to actually reboot (restart connections or airplane mode didn't restore connection like they did on .886), multiple times a day. I rate the phone at about 40% of data connectivity.
I've noticed a huge difference being on .901 so far. On .901, 3G to 4G transitions happen really quickly and have been flawless. 4G signal seems to be holding much stronger, and I have 4G and 3G connection in areas of the house i didn't before. Still have some dead spots in the house where I get no connectivity (seems like more of a network not a phone issue), but it'll transition from no connection to 3G - 4G quickly as soon as I move to an area of the house that gets signal.
I haven't had to reboot / airplane toggle once since the .901 update! I rate the phone at about 95% data connectivity now. I think the remaining 5% is probably just network issues / certain parts of the house causing poor signal transmission. For me, it's a vast improvement over .893 which was a total failure of an update for people in 4G fringe zones.
johnlgalt
Antidisestablishmentarian
I can add to that review.
I live in a 3G only area, but I traveled through one 4G area on the way to another 4G area where I stayed for 3 days.
Wow. I had no issues with transitions. It slipped from one to the other with no problems.
Wow. I had no issues with fringe area drops - the signal, if dropped , would pick right back up.
Wow. I had a few 4G drops, but nothing like what I expected. The 4G area I was in was actually faster than my hotel's wireless....
Wow. I had one 4G drop that forced me to reboot.
I live in a 3G only area, but I traveled through one 4G area on the way to another 4G area where I stayed for 3 days.
Wow. I had no issues with transitions. It slipped from one to the other with no problems.
Wow. I had no issues with fringe area drops - the signal, if dropped , would pick right back up.
Wow. I had a few 4G drops, but nothing like what I expected. The 4G area I was in was actually faster than my hotel's wireless....
Wow. I had one 4G drop that forced me to reboot.
swc2001
Android Expert
do you have root on .901?i can add to that review.
I live in a 3g only area, but i traveled through one 4g area on the way to another 4g area where i stayed for 3 days.
Wow. I had no issues with transitions. It slipped from one to the other with no problems.
Wow. I had no issues with fringe area drops - the signal, if dropped , would pick right back up.
Wow. I had a few 4g drops, but nothing like what i expected. The 4g area i was in was actually faster than my hotel's wireless....
Wow. I had one 4g drop that forced me to reboot.
johnlgalt
Antidisestablishmentarian
yup. Fully rooted. Of course, I rooted the device after reverting to 5.5.886 system, then added the 5.5.886 radio, then added the 5.5.886 kernel, at which point I got the boot error - but since eFuse was not tripped, I was able to then flash the 5.5.893 update, verify I still had root, then flash 5.9.901 and again verify I still have root.