Slashdot Mirror
Canadian Android Carrier Forcing Firmware Update
Wolfier writes "For wireless carrier Rogers in Canada, it seems that 'Customer Safety' only becomes a concern after months of neglect. Rogers is the only GSM carrier in Canada and so the only choice for Android users. Months ago, a customer called Rogers to report a firmware bug that was preventing users from making 911 calls under certain circumstances, and informed the carrier that Google had fixed the bug (recording of that call). But Rogers is only doing something about it now — namely, cutting data access of paying customers until they accept a mandatory firmware upgrade that not only fixes the 911 problem, but also contains 'extra' features that prevent users from ever gaining root access to their phones — even non-subsidized ones. And some phones are also getting bricked by this 'official' update. The moral: we really need to open up the competition here up North."
I run CyanogenMod on my Rogers HTC Dream, and it has apparently had the fix for this issue for 5+ months. Yet I am still cut off from data access, they keep insisting I install their update.
It is no measure of health to be well adjusted to a profoundly sick society. - Krishnamurti
Yea, I'm a douche, I didn't even read the entire summary apparently.
Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
I've documented everything I've collected on the issue here: http://www.litui.net/archives/796
More detailed and ordered than the OP's links.
I send you this message in order to have your advice.
The user-applied fix isn't available for Mac or Windows 7 users. Those users are required to call into the Rogers tech support line to get the fix.
I did that, and had to wait on hold for over 30 minutes while the phone support waded through the (expected) deluge of calls. When I got through, I was told that I could either:
I stopped in the Rogers store to get the fix. I waited for about 20 minutes while the customer support people (calling them "techs" wouldn't be accurate) installed the fix software on their in-store computers. Then I was told that the fix would wipe my phone. Did I have a backup? I said no; I haven't been able to find any evidence of Rogers-capable phone-sync software that works on my Mac (it's all Windows only). The store person offered to make a backup there, but after doing so he said that it only backed up my contacts, not my apps or settings (IMO the important parts). I walked out hoping that the SD solution will be better, but at best, I'm locked out of my wireless Internet service for 3-5 days.
It's hard to imagine how Rogers could have made this process worse.
I thought the one of the battle cries that Android fanboys wave at the iPhone fanboys was that it was open and you weren't locked into running what the provider wanted, you had root on your own device and they can't take it away ... Turns out they can force remote updates and lockout root?
By comparison, Palm not only has root available on all their WebOS phones, it is provided by Palm's SDK itself and not by an unsupported hack that can be closed later at the carrier's or device maker's discretion. CEO Jon Rubenstein has even publicly praised the Homebrew community, who's efforts are encouraged, and they've promised not to close developer mode.
Maemo, from Nokia (N900, Nokia Internet Tablets) is even more open in a way; not only you have root, you have essentially a little Linux computer with all that implies; this is due to it's UMPC heritage, it originally wasn't really a smartphone OS. (Though it's a little easier to hack the apps for WebOS with "patches" because they're just JS/HTML5 text files, except the new native apps. :) )
Really, although Android has Linux, among the Linux-based phone OSs, it is probably the most closed.
Note: The networks you're mentioning from Telus and Bell are UMTS only, with no 2G GSM support at all. Won't matter in 5-10 years, but just a heads up.
The problem people don't really seem to get about mobile pricing and "competition" in Canada is that it really is a system with only two sides Rogers and Telus/Bell. Telus and Bell themselves barely compete as their pricing structures are nearly identical beyond minor differences, which makes sense given their Network Sharing Agreements.
Fido is effectively the WestJet of our carriers, cherry picking the majority of their clients within high population density areas, which did make them a competitor within the major cities and a large portion of the market until about 2004 when they became wholly owned by Rogers.
Some people may mentioned the MVNO's Koodo and SOLO Mobile not realizing that Koodo is effectively a slightly lower margin Telus, and Solo Mobile is Bell (down to the same exact 'customer service' tools, except I believe Solo CSSR's are primarily through Canadian based subcontractors only).
Given these details, you see we have effectively two sides only. Two sides which somehow magically conviced everyone in the country that it makes sense for them to have doubled the price (two-sided billing) of per usage SMS's from 15c to 30c a piece. Two sides that maintain suspiciously close pricing that tends to vary only by small amounts for specific cases. Two sides that maintain a consistent CHURN back and forth between the two sets of groups generating Long Term Contract Charges and a variety of fine print charges so that when One is considered the evil, users switch to the other (with similar THEY ARE THE WORST rants concerning the business model in either case, rogers OR bell). The only reason it works is that the worst things only happen to a low enough percentage for each carrier that after they ragequit and go to the other side, its unlikely for it to happen again to the same person (post 90 day billing errors that are considered valid so long as client wasnt able to ask the right question to a CSSR before the 90 days was up thanks to the Consumer Protection Act [HAH], defective merchandise that is considered not covered under warranty but still generated a contract with a valid LTCC charge if cancelled [*cough*AUDIOVOX*cough*], etc).
The long and short of it is Telco companies have us by the short hairs up here in Canada. Heres hoping WIND Mobile takes off, but given that they only launched in friggan December, i cant have an opinion quite yet.
Ice Cream has no bones.
I received text messages last week warning of the cutoff and forced update.
I called Saturday afternoon and politely asked the CSR if I'd receive any consideration for running an unaffected 1.6 ROM and have made a few 911 calls. Apparently the guy made a note. I asked for his name and ID number and hung up. Next day neither of the phones had internet, so I called up and sang the same song to the this CSR; he insisted that I had to update, I explained that I'm not affected and being asked to install an earlier revision of the ROM is hardly an update. He said all he could do is "reset the phone" when we hung up. He asked me to restart my phone when we hung up and when I did, my 3G signal was back and has been back since.
I've been getting texts to update, though.
You just have to fake your Android version to appear to be the version they're looking for. If you look through the forum threads linked in the story the exact method is there. I will put it here for convenience:
adb shell reboot recovery /system/build.prop ***or whatever it was called*** /system/build.prop
***Wait for Magic to boot into recovery***
adb shell mount -a
adb shell
cd system
ls
***look for your build file, will be build.prop or build.sapphire.prop most likely***
CTRL-D ***to quit the shell***
adb pull
***make a backup copy and edit the file***
adb push build.prop
adb shell reboot
The actual changes you need to make to the file are:
ro.build.description=3.05.631.7 CL#118917 release-keys
ro.build.changelist=118917
ro.product.ua=
ro.build.fingerprint=rogers/htc_magic/sapphire/sapphire:1.5/CUPCAKE/118917:user/release-keys
ro.build.display.id=DRC92 3.05.631.7
Once you reboot your Magic, you should see the changes in Settings->About Phone under "Build Number".
Call into Rogers and get then to reset your network and you should be good.