Root CyanogenMod 5.0.7 (Android 2.1) on post e911 magic

[CooL_SpoT]

So you're saying we could root the phone, flash the Rogers Dream updated Radio, and use whatever ROM we wanted (compatible with 6.35.xx radios). And we wouldn't have to worry about data cut-off since we're using the official Rogers radio?

If that's the case, this is good news. Kinda wish I hadn't signed the waiver already.

 

[GreatBigDog]

So you're saying we could root the phone, flash the Rogers Dream updated Radio, and use whatever ROM we wanted (compatible with 6.35.xx radios). And we wouldn't have to worry about data cut-off since we're using the official Rogers radio?

If that's the case, this is good news. Kinda wish I hadn't signed the waiver already.

If it works, thats exactly the case.

I've had it confirmed that the Dream Radio will run on the Magic. I'm still working on how to get it flashed onto the system. Every time I try to use fastboot to flash the Radio the phone hangs after the radio is sent to it and it tries to write it. I'll continue investigating this today and see what I can come up with.

gbd

 

[vikingisson]

Is this radio any different than the new radio some of us have been running (as per cursordroid's radio update)? The version matches rogers and my data hasn't been cut since using it. I've been cut (4 times) when I used the old radio or the newish radio from the euro RUU. But never cut when using the regular new radio. Only issue is that there are fewer roms to choose from.

 

[GreatBigDog]

Is this radio any different than the new radio some of us have been running (as per cursordroid's radio update)? The version matches rogers and my data hasn't been cut since using it. I've been cut (4 times) when I used the old radio or the newish radio from the euro RUU. But never cut when using the regular new radio. Only issue is that there are fewer roms to choose from.

This will be the Radio that was applied to the Dream in the mandatory update and it's what the HTC Dreams are running right now (3.22.26.17)

If you're using cursordroid Rom you're probably on the new Magic Radio as I believe that cursordroid is one of the few that accepts a 6.x radio.

 

[GreatBigDog]

Here is my updated guide for Rooting the Post E911 Magic and Magic+ This guide will leave you with CyanogenMod 5.0.7 (Android 2.1) using the post E911 Dream radio. Hopefully this combination will get by the Rogers scanning and data will no longer be cut.

Rogers post E911 Magic to CM 5.0.7 (Andorid 2.1) with Dream E911 Radio The GreatBigDog Report

For those of you that followed my original guide I have edited it to include how to get the Dream Radio installed (Unfortunately a wipe is involved so you'll have to set the phone up again)

 

[crossed.out]

Just installed the new radio. Leaving the battery out of my phone to hopefully force a network refresh, but I'll probably have to wait at least 24 hours for Rogers to refresh on their end.. I'll post the outcome anyways.

Also, I noticed that Cyanogen has updated to a test3. Anyone tried flashing it?

 

[GreatBigDog]

Just installed the new radio. Leaving the battery out of my phone to hopefully force a network refresh, but I'll probably have to wait at least 24 hours for Rogers to refresh on their end.. I'll post the outcome anyways.

Also, I noticed that Cyanogen has updated to a test3. Anyone tried flashing it?

I'm running test three right now. Everything seams to be OK so far. Almost 7 hours running with my sim card installed and using the Dream radio. I still have data!!

gbd

 

[vikingisson]

Here is my updated guide for Rooting the Post E911 Magic and Magic+ This guide will leave you with CyanogenMod 5.0.7 (Android 2.1) using the post E911 Dream radio. Hopefully this combination will get by the Rogers scanning and data will no longer be cut.

So this is the old radio but the version from the updated Dream which should pass the sniffer even on a Magic? I don't suppose the radio could be flashed as per the 'downgrade' radio process listed alongside the upgrade radio process by cursor. That would be easier but it is the radio changes that are most risky.

I never heard back from rogers so I have to assume the status quo is the answer from them. I might stick with the limited selections for the new radio until I see what happens next month. Then ride out the contract and never go back.

So how is this v5 rom compared to the other 2.1s? What are the weak points and what does it do best?

 

[vikingisson]

I'm running test three right now. Everything seams to be OK so far. Almost 7 hours running with my sim card installed and using the Dream radio. I still have data!!

gbd

I found that it took 2 days before suddenly loosing data on the old radio. Then you have to get past Friday night to be certain.

 

[mjschmidt]

I think this brings up a very important question, one I doubt Rogers will answer.

Now that we can root the E911 phones, and now that we may possibly be able to load the Dream radio and keep our data... that means that we can all run versions of Android that are not the "officially approved" version Rogers would prefer we run.

Rogers made us upgrade because the previously existing version of Android we had suffered from a bug that could cause the phone to crash when dialing 911.

We know that the 1.6 and up ROMs have (or should have anyway) the fix in them, but Rogers wouldn't let us have data without either applying the E911 update, or signing a waiver.

Now that we can theoretically root and install a non-E911 OS version, and get data without signing the waiver... it stands to reason, logically, that Rogers must force another update to block root again and force another "official" version on us... otherwise they cannot justify cutting off data (or requiring the waiver) until/unless we have the E911 update, because rooting simply puts them back into that potential legal trap that existed because of the E911 bug.

It's a double-standard, just like allowing jailbroken iPhones on their network.

 

[GreatBigDog]

So this is the old radio but the version from the updated Dream which should pass the sniffer even on a Magic? I don't suppose the radio could be flashed as per the 'downgrade' radio process listed alongside the upgrade radio process by cursor. That would be easier but it is the radio changes that are most risky.

I never heard back from rogers so I have to assume the status quo is the answer from them. I might stick with the limited selections for the new radio until I see what happens next month. Then ride out the contract and never go back.

So how is this v5 rom compared to the other 2.1s? What are the weak points and what does it do best?

CM 5.X for the Dream/Magic is a fully functioning ROM, even the Camera is working on it. It is the first fully functioning 2.1 ROM available. It's still in Test (Experimental) phase right now, but I'm finding it stable enough to be a daily driver. On the Dream it requires the use of DangerSPL in order to fit on the phone.

If you install the HTC keyboard on it you will get the microphone for Voice to text entering in all text fields, you can run all Apps requiring 2.1 with the exception of apps requiring the Snapdragon processor (Google Earth, Flash 10.1). It still has the original launcher not launcher 2 as the devices just couldn't handle it. the 3D gallery is there along with support for LWP (still needs work and may not make the stable build)

With the first couple of test builds there were problems that some were having with poor battery performance on the Dream but so far I haven't seen any problems with it on the Magic. Batter performance is much better than with the crappy Rogers mandatory update with sense ui.

You can check most things out yourself be visiting CyanogemMod Forum for the 5.0.7 Experimental Mod

 

[Silvertag]

I think this brings up a very important question, one I doubt Rogers will answer.

Now that we can root the E911 phones, and now that we may possibly be able to load the Dream radio and keep our data... that means that we can all run versions of Android that are not the "officially approved" version Rogers would prefer we run.

Rogers made us upgrade because the previously existing version of Android we had suffered from a bug that could cause the phone to crash when dialing 911.

We know that the 1.6 and up ROMs have (or should have anyway) the fix in them, but Rogers wouldn't let us have data without either applying the E911 update, or signing a waiver.

Now that we can theoretically root and install a non-E911 OS version, and get data without signing the waiver... it stands to reason, logically, that Rogers must force another update to block root again and force another "official" version on us... otherwise they cannot justify cutting off data (or requiring the waiver) until/unless we have the E911 update, because rooting simply puts them back into that potential legal trap that existed because of the E911 bug.

It's a double-standard, just like allowing jailbroken iPhones on their network.

I don't think they will do another round of force-upgrace. The whole E911 was really just a "Oh oh our lawyers told us to cover our arses ASAP and we will" moment. They could of been sued if one of their user died in a emergency because of this issue and they rushed a update, spammed our sms boxes with warning and cut the data to make sure they cover their bases. Was it badly handled.. yes it was but the advisers who told Rogers to make a move to patch this problem don't care about customer experience they care about how much money business lose and dirty press they could get.

I'm running a 2.1 rom, for the last 3 months, on a 6.35 radio that is higher then the E911 one and did not lost my data. The problem will go away by itself when the 2.1 upgrade comes around. There will be no need to flag this update as the patch for the E911 is already there. The remaining users still using the non-patched update or running a inferior firmware rom will still get flagged because of the above paragraph.

 

[vikingisson]

The problem will go away by itself when the 2.1 upgrade comes around.

I'm not at all convinced and not sure how you are. If the update is forced (not likely) they will certainly do it. If it isn't forced (more likely) then there could still be an unpatched phone and they will continue the scan. I understand the legal baloney reasons but by now everyone has either updated or isn't getting data. It is now all about getting the rooters and anyone that dare run an unlocked phone off their network. They can just as easily scan for only the vulnerable phones and leave everyone else alone. but I hope you're right.

There are other 2.1s out there that technically have everything important working (no biggie if LWP doesn't work) so I'm wondering what the secret is that cyan has found. I can run several 2.1s that perform very well but are too easy to get into a laggy mess within a few days. So I'm still watching cyan before jumping to that. I loved the months I spent on the old cyan but rogers killed that bliss for me. If they'd only do the right thing with this scan nonsense.

 

[Silvertag]

I don't see any major issue from 1.5 or 1.6 that are not patched in 2.1. The scanning from E911 as really no reason to exist on 2.1. Even if i choose to stay on the 1.5 E911 update Rogers really has no reason to force me into a upgrade. I don't see business wise what a force upgrade from E911 to 2.1 could achieve other then alienate your dearly paying customers.

Yes they will continu to scan the network but i highly doubt it will be to check if a user has the patched E911 or 2.1. Why would you scan something that has no issue ?!. They already made a mess and have a tone of calls about the waiver form not taking the imei and data being cut for no reason why would they want to add this to 2.1.

Yes users running a modded rom with old radio "may" still be flagged as non-E911 and old 1.5 (non-E911) will be flag. Apart for the modded rom (already patched) being wrongfully flagged i don't see the issue continuing post E911 even less 2.1.

Its like Microsoft scanning your pc with Windows XP and telling you you need a security patch for it. It checks for the missing patch not if you run Vista on that machine. Until you get this patched you will get bugged to patch it that's normal design. You should not be force into having to use Windows7 because its the next best thing available.

 

[mjschmidt]

Silvertag, the point I'm making is that Rogers forced the upgrade to E911-1.5 because they wanted to make sure they were legally covered (from lawsuits about the E911 issue).

Since they have taken the position that they [Rogers] are responsible for ensuring that a user's phone complies with E911, the _only_ way they can ensure this is to force all users to have the exact same ROM, or have users sign waivers. The only available 3rd option would be for Rogers to "approve" certain rooted ROMs, which they won't do.

So, now that the Magic can be rooted, and pass the radio test (potentially) thus keeping data (their only means of enforcing compliance) without signing the waiver, their whole argument for forcing the E911-1.5 ROM is shot.

Any Magic or Magic+ owner can now, potentially, have a phone with a ROM that may (note I say "may" only because Rogers can't and won't approve other ROMs) have a bug or the same bug. [see below].

Rogers' "if/then" argument is: If the potential legal threat to Rogers exists because of a potential bug in a ROM we [Rogers] cannot control, the end-user must install only our "approved" ROM, or sign the waiver.

Anything other than those two options returns Rogers to the (presumed) legal position of being responsible in the event a bug in the phone software causes a failure of the user's ability to dial 911.

Yes, I know that the 911 bug is fixed in 1.6 and beyond, but what I (or we) know to be true is irrelevant to Rogers legal team. As far as they are concerned, they have indicated that a ROM must pass their approval to be used on the network and have data. Since they are not going to approve 3rd party ROMs, that means the Rogers E911 ROMs only.

If Rogers does not move to block root again, they will then be in a position of tacitly approving of ROMs they have not approved, and which may leave them in the same perceived legal difficulty as before.

In other words... if they aren't going to block root now, they shouldn't have forced the update in the first place.

 

[Silvertag]

Well it all depends if Rogers wants to go witch hunting or not. Right now they can only check what version of radio is running on your phone. If they spot a 3.22 you are a target if your on 6.35 you are in the clear.

Will they compare their 6.35 version (to the last digits) with your running version so they can force you into a 6.35 with perfect spl so that you cannot root anymore, maybe... They tried that trick with 1.5+ and it failed. It will most certainly fail with 2.1 also.

Rogers still does not graps what android is and how it works. They can play cat and mouse with us on every upgrade but will lose the match (and customers) in the long run.

 

[GreatBigDog]

Well it all depends if Rogers wants to go witch hunting or not. Right now they can only check what version of radio is running on your phone. If they spot a 3.22 you are a target if your on 6.35 you are in the clear.

Will they compare their 6.35 version (to the last digits) with your running version so they can force you into a 6.35 with perfect spl so that you cannot root anymore, maybe... They tried that trick with 1.5+ and it failed. It will most certainly fail with 2.1 also.

Rogers still does not graps what android is and how it works. They can play cat and mouse with us on every upgrade but will lose the match (and customers) in the long run.

Actually the 3.22.26.17 radio that I'm using is the same one that the dream is now using, the Dream is not on a 6.35.x radio. Unless Rogers wants to start blocking the data for all Dream owners then there should be no way to detect that the phone does not have the required update.

The only way that Rogers will be able to then detect that there is a non-updated phone on their network is to force another update that changes the radio that the dream uses. But then there is still nothing to stop anybody from just flashing any new radio.

gbd

 

[vikingisson]

Well it all depends if Rogers wants to go witch hunting or not. Right now they can only check what version of radio is running on your phone. If they spot a 3.22 you are a target if your on 6.35 you are in the clear.

Actually they are looking for specific 3.22 and 6.35 radio versions. even a slight rev difference will get you cut off. The euro rom for example has a 6.35 radio that won't pass the scan but is easy to change it to a good one.

Bottom line is they need to cover themselves for vulnerable roms. The radio versions for those are known so they should only look for those radios for cut off status. Everything else should be allowed to pass. if I bring my own phone that might have a slightly different yet perfectly safe radio I have to fight them to keep my data? That's unacceptable. This cat and mouse game is no fun at all.

 

[Silvertag]

Actually they are looking for specific 3.22 and 6.35 radio versions. even a slight rev difference will get you cut off. The euro rom for example has a 6.35 radio that won't pass the scan but is easy to change it to a good one.

Bottom line is they need to cover themselves for vulnerable roms. The radio versions for those are known so they should only look for those radios for cut off status. Everything else should be allowed to pass. if I bring my own phone that might have a slightly different yet perfectly safe radio I have to fight them to keep my data? That's unacceptable. This cat and mouse game is no fun at all.

Exactly and while they only check the radio since no other tools are available to them they will continu to cut us off if we are not on the same "page" (aka radio) they are. They must build a team (why not continu with you guys since you already had 2 meetings ?!) to see what other roms with different radio are out there and understand that the E911 is out of the way on many of them. They must see the android scene at large, standard rom and cooked rom, to get a better view or this whole mess will continu on each android upgrade. I have not eard of any other provider cutting of data to its users because of a bug on android.

1.5+ and up on 6.35 are in the clear it's a bit more tricky for the others still using 3.22 but i'm pretty sure all of them are patched also.

PS: To @RogerMary if you happen to follow this discussion i would recommend Rogers heads down to http://forum.xda-developers.com/index.php and see for themselves how much effervessence there is about android and the multiple roms for all the HTC models. The modding scene will not fade out it's actually picking up more and more as the Android users base expands.

PSS: Will now return to topic . GJ GBD for the Dream radio on Magic this will help alot of users to use CM since he will not cook a 6.35 radio version.

 

[vikingisson]

They really need to find a better solution. I don't see why they can't scan *only* for the vulnerable rom radio versions and assume the rest are safe. It isn't practical to make a white list of roms/radios. I don't care if they ever understand android or not, just let me use mine.

I'm very close to canceling my business and personal accounts and then come back in with no contract and no supplied phones. I think that will avoid the scans since they no longer have any reason to and I can run any phone/device I want. Or I'll just change providers, makes no difference to me anymore.

 

[Silvertag]

They really need to find a better solution. I don't see why they can't scan *only* for the vulnerable rom radio versions and assume the rest are safe. It isn't practical to make a white list of roms/radios. I don't care if they ever understand android or not, just let me use mine.

I'm very close to canceling my business and personal accounts and then come back in with no contract and no supplied phones. I think that will avoid the scans since they no longer have any reason to and I can run any phone/device I want. Or I'll just change providers, makes no difference to me anymore.

Won't change a thing. Contract or not they need to offer a stable service and for them not running a android rom with bugs is the way they do business. I'm still on a 2 year leach on my contract and i have a corporate account deal so it's real hard to get a better offer from the competition. If this continu i don't think i will use my 1 year HUP and get into another 3 years term. Will probably let it run out until i can get out and will endure having a outdated rom (until i can't upgrade my Magic rom anymore. Crossing fingers for Froyo)

 

[GreatBigDog]

So I'm day three of running Magic with the Dream radio and so far so good, I still have data. Looks like using the 3.22.26.17 radio from the Dream E911 update is the ticket to being able to keep data while using CyanogenMod.

gbd

 

[vikingisson]

That's good to hear. So the trick is the 3.22.26.17 radio instead of the 3.22.20.17 radio that we usually flash. The process to downgrade is pretty involved and wonder if the standard downgrade process would work except with this radio. Which hboot and recovery are you using?

Is this rom that much better than the other 2.1 roms out there? I've tried some nice 2.1 roms but they all suffered to various degrees after a few days. A good 1.6 that passes the stupid sniff test would be ideal for now but I don't see any. I've gone back to cursorsense just so I have speed and stability but the lack of the >1.6 apps is painful so I'm debating whether to wait or go for the cyan.

oh, have you used tethering? I need that about once per month and would hate to give that up.

 

[GreatBigDog]

That's good to hear. So the trick is the 3.22.26.17 radio instead of the 3.22.20.17 radio that we usually flash. The process to downgrade is pretty involved and wonder if the standard downgrade process would work except with this radio. Which hboot and recovery are you using?

Is this rom that much better than the other 2.1 roms out there? I've tried some nice 2.1 roms but they all suffered to various degrees after a few days. A good 1.6 that passes the stupid sniff test would be ideal for now but I don't see any. I've gone back to cursorsense just so I have speed and stability but the lack of the >1.6 apps is painful so I'm debating whether to wait or go for the cyan.

Hboot 1.33.2005
Radio 3.22.26.17
Recovery RA-saphire-v1.6.2H
Rom CM-5.0.7-test5
EBI1 Port bc-5.0.7-test5

You could always use the stable CM 4.2.15 1.6 ROM with the appropriate EBI1 kernel port instead of the 5.0.7 test 2.1 ROM or for that matter any ROM that is compatible with an EBI1 radio.

gbd

 

[vikingisson]

k, that hboot is also different (older) so I'd better not risk doing the normal downgrade and should do it the way you did. And like you said there are lots of roms that should work if the 2.1 turns out to lack something I need.

I ran the 1.6 cyan for a long time and never had a problem until after the rogers fiasco.

thanks!