yashsingh1/xdaforums huggingface dataset:
[myTouch 3G, Magic Android Development] nybble:
I'm trying this without calling rogers.:mad: it didnt work

I've already called them and had a lengthy discussion with them about this.

Some tips rogers indicated to me:

The system is automated as it stands right now, the CSRs and the Data dept CSRs cannot override, yet.

You can try tricking the system, if you can find someone with the patch applied. No guarantees on how well this will work.

Speculated you might be able to trick the system by using another data device (iphone, or something) and then moving it back. But that might only cure it temporarily.

I am going to escalate my complaint through the structure on the website (http : // your.rogers.com / contact / complaint.asp ), as I have already went through 2 tiers of customer support.

I'll keep everyone posted on my progress.
[myTouch 3G, Magic Android Development] bjtheone:
Just hacked the build.prop file based on what bcrook did (wanted to keep an bunch of network tweaks that Amon_RA uses that "seem" to give me better 3G performance). Pushed it and rebooted the phone, verified the changes...

Called Rogers - went to Wireless - General and just politely asked for a network reset. When asked why I just said I did the update and did not want to wait for the rescan. Rep had no issues doing it. She did mentioned that if it did not resolve the issue, she would have to transfer to the tech queue.

Power cycled the phone and I am back with full data. Will report back if it drops again.

Definitely suggest going into the general queue... they will happily do a reset as it is an easy call, and the wait time was under 30 seconds. Took longer for the phone to reboot to make sure I at least still had voice.
[myTouch 3G, Magic Android Development] bcrook:
While I dont think they can override they will and can do a 'network reset.' It worked for me and many others.
[myTouch 3G, Magic Android Development] aloneandeasy:
mlav advice confirmed

I've just finished talking to a rogers rep via the online tech support and I've got my 3G signal up and running.

Here's the complete chat log...

25 Jan 2010 11:49:52	Jony says: Hello,.

25 Jan 2010 11:50:22	Mark XXX says: I have an HTC Magic and I've been waiting for my internet service to be re-enabled

25 Jan 2010 11:51:00	Mark XXX says: I have an updated ROM (build number 3.05.631.7) which does not have the 911 issue

25 Jan 2010 11:51:04	Jony says: Sorry to hear that I can certainly look into the issue for you, to start may I please have your wireless phone number,the postal code on the account and the billing name on the account?

25 Jan 2010 11:51:27	Mark XXX says: oh sure... i figured you already had that stuff.

25 Jan 2010 11:51:42	Mark XXX says: 519-111-1111, A1A 1A1, Mark XXX

25 Jan 2010 11:51:51	Jony says: Thank you. One moment please.

25 Jan 2010 11:54:19	Jony says: Have you done the software update in your HTC?

25 Jan 2010 11:54:30	Mark XXX says: i have an updated ROM, yes

25 Jan 2010 11:54:44	Jony says: May I ask you to remove the battery from your device?

25 Jan 2010 11:54:50	Jony says: Let me know once you have done that.

25 Jan 2010 11:55:16	Mark XXX says: Ok, Battery is out

25 Jan 2010 11:55:22	Jony says: One moment please.

25 Jan 2010 11:56:05	Jony says: Please go ahead and put the battery back on.

25 Jan 2010 11:56:30	Mark XXX says: done, just waiting for the phone to boot

25 Jan 2010 11:57:15	Jony says: Ok.

25 Jan 2010 11:58:34	Mark XXX says: great. that seems to have fixed the issue

3 other people in my office have just done the same procedure successfully.

Done!
[myTouch 3G, Magic Android Development] fkung:
After giving up on waiting (12 hours after applying the build number patch... yes, I know they say 24), I called tech support... did the usual, gave them the build number, and the tech did mention that I wasn't showing up as blocked on his end. Maybe the patch would have worked on its own, if I'd been more patient?

But after removing the battery and restarting the phone a few times, things are working (suspect a network reset happened, though the words didn't come up). So +1 for calling them (and being on hold for half an hour =) )
[myTouch 3G, Magic Android Development] aaziz:
This didn't work for me, and I've tried it twice. My build says "DRC92 3.05.631.7", but should it say "DRC92 3.05.831.7"? I'm going to modify it in build.prop and build.sapphire.prop and ask for another network reset.

The tech also told me there was no hold on my account, however I still don't have data.
[myTouch 3G, Magic Android Development] aaziz:
(double post delete)
[myTouch 3G, Magic Android Development] bcrook:
Have you power cycled? Turn off the phone, pull the battery, replace and boot up.
[myTouch 3G, Magic Android Development] aaziz:
I did this several times. Like I said, my build says "3.05.631.7". I checked the files in both signed-Rogers-netfix2-sapphire.zip and CM-Rogers-NetFix-signed.zip, and both locations in each file say 3.05.631.7. Maybe that's correct, but the Build Number of another user was different (or so he posted, in the "Rogers Mandatory Update Thread" - perhaps it could've been a type on his part). Just for s&g, I tried editing the build.prop and build.sapphire.prop from signed-Rogers-netfix2-sapphire.zip to the 831 number and tried flashing that, but it says "Wrong digest...verification failed", so I guess I'm not competent enough for that :P

I'd seriously appreciate help on this. I love the CM ports... you're the go-to guy, and I don't want to try the Cursordroid mod (yet).

Thanks.
[myTouch 3G, Magic Android Development] bcrook:
If you have a magic:

http://downloads.rogers.com/wireles...ic_Required_Software_Upgrade_Instructions.pdf

Dream:

http://downloads.rogers.com/wireles...am_Required_Software_Upgrade_Instructions.pdf

There are screenshots with correct builds in there. Dont volunteer the build number unless they ask. Most CS reps haven't asked.

Also, you need to resign an update.zip if you change it. It may be easier to

adb pull /system/build.prop .
***Then edit the build.prop in the current directory***
adb remount
adb push build.prop /system/build.prop

Or just fake it with the screenshots...if they say the numbers are wrong, tell them those are the numbers show in their official instructions (basically, tell them to stfu).
[myTouch 3G, Magic Android Development] aaziz:
Thanks I'm going to try this. My build says exactly "DRC92 3.05.631.7", it does not say "3.05.631.7 CL#118917 release-keys". Is this accurate or is it not okay?

I'm going to try your advice with adb right now.
[myTouch 3G, Magic Android Development] aaziz:
I should also not I am on a business account, I don't know if that changes anything.
[myTouch 3G, Magic Android Development] walie:
Has anyone noticed that certain paid apps are missing now from the market (ex. twidroid pro) even after using market enabler? This is after pushing the updated build.sapphire.prop provided by bcrook.

There are reports of similar occurences with the new cursordroid Rom as well
[myTouch 3G, Magic Android Development] aaziz:
Talking with bcrook, who encouraged me (thanks), and I called tech support. Talked to a regular rep who wanted to transfer me to smartphone support, but warned of a long wait time. I asked her if she could just to do a network reset for me and she said sure, and now I HAVE DATA!

Now, what's different from the 3 times I tried over the web support? Well, 2 things:

1) I changed ro.build.display.id to the same as ro.build.description in both prop files and pushed them out over adb. The difference is "DRC92 3.05.631.7" (previous) compared to "3.05.631.7 CL#118917 release-keys" (changed to).

2) The CS rep asked me to also remove my SIM card when doing the reset, where as the online techs didn't. I don't know if this would have an impact, but I urge anyone to try this to also remove your SIM, as its easy and won't hurt anyways.

What matters is I now have data, without having to install another ROM or (god forbid) the Rogers 1.5 update.

Thanks to bcrook for his help and build.prop files.

Hope this helps anyone else that's stuck.
[myTouch 3G, Magic Android Development] cursordroid:
There's an 'online kitchen' available from Modaco to flash the latest Cyanogen with the latest EBI1 kernel port already included.

http://android.modaco.com/content/h...tchen-online-kitchen-for-cyanogenmod-v4-2-13/
[myTouch 3G, Magic Android Development] nybble:
Hmm. I'm now back up, was luck enough to get Jony to help, after being refused service by another customer.

Started out with Edge only, but 3g is now working.

Still going to give them hell though, as I have an open ticket with manager.
[myTouch 3G, Magic Android Development] bcrook:
Thanks for pointing this out - I had no idea! lol.
[myTouch 3G, Magic Android Development] polaroid22:
build number

Hi,

It's my first post and I'm using Cyanogenmod ebi1 since a couple of months and I enjoy. Thanks bcrook and radix for good work! :)

I'd flashed my dream with that procedure:

wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_Rogers_Dream_EBI1_to_CyanogenMod

(I can't post link since I'm newbie here)

So I think I still have original rogers radio.

I use latest CM and tried to apply CM-Rogers-NetFix-signed.zip with cyanogen updater but build number is still showing BC83, what's wrong?

Thanks for your help.
[myTouch 3G, Magic Android Development] aaziz:
There's another zip, one for either Dream or Magic, that contains both a build.prop and build.[trout/sapphire].prop. Whether this makes a difference, I don't know, bcrook would have to verify that. Try flashing the update again and verify that it actually completed. Or follow the adb steps in my above post.
[myTouch 3G, Magic Android Development] polaroid22:
Thanks aaziz, I didn't saw the other file. I just tried Rogers-netfix3-dream-signed.zip from bcrook website but this time I'd rename file update.zip (is it really important?) and it seems working on my dream, now it show version "DRC83 1.89.631.1" instead of Rogers rom that say "1.89.631.1 146733 CL#94714 release-keys" Is this supposed to be like this with this fix? I just want to be sure that is correct before call for a network refresh.

Thanks again.
[myTouch 3G, Magic Android Development] bcrook:
Sorry, thats the old "fix."

Here are the updated versions:

http://briancrook.ca/magic/Rogers-netfix3-dream-signed.zip

Sapphire users:

http://briancrook.ca/magic/signed-Rogers-netfix2-sapphire.zip
[myTouch 3G, Magic Android Development] xaueious:
I'm not completely sure if the patch was even necessary.

Myself and some others have regained 2G/3G by simply requesting for the network refresh on our devices. Now unless they rescan our devices it shouldn't matter if we have the patch installed or not?

So did anyone who installed the patch go down during the 24 hours?

I installed to be safe anyways.
[myTouch 3G, Magic Android Development] gojifan2112:
well, as of 0139 hours est zinx recovery flasher seems to not be working.. looks like they did patch that hole, but good.

folowed CM's EBI1 stock to mod wiki to the letter.

could not get it to flash, even after rebooting.
[myTouch 3G, Magic Android Development] PremierITA:
can someone create a cyanogen build to run on new radio (6.335...) ? i've some issues with old radio, and new radio works good.
[myTouch 3G, Magic Android Development] aaziz:
Yes it's supposed to be that way, that is only the cosmetic display value. Though I will say that I changed my in the build.prop files to exactly what the back-end is (see my other post), and it worked my 4th time around (although I also did something different, too - pulled my SIM). Hope that helps at all.

You're right, the patch may not be necessary. A user on another thread reported she didn't need to either. It might be that the SIM card needs to be pulled as well, since my first 3 times I did not do that either (was not instructed to)
[myTouch 3G, Magic Android Development] aaziz:
Did you call and have them do a network reset? When I say "battery/SIM" pull, that's when you call for a network reset. They'll ask you to pull your battery and your SIM, but the first 3 techs I talked to (online) didn't tell me the SIM part.
[myTouch 3G, Magic Android Development] aaziz:
A question outside of the whole 911 issue...

I was going to try out a 2.0.1 ROM today, and was reading... apparently I have HBOOT 1.33.0010 (50000), which is a perfected SPL, and supposedly I can't root it? Except I have been running this CM port for months. Should I attempt to upgrade my SPL and radio. Is it safe, and will it give me a speed boost? I'll wait to hear back from someone who can confidently confirm this, as I don't want to brick this thing.

Thanks.

EDIT: My fastboot screen details:

SAPPHIRE PVT 32A SHIP S-ON H
HBOOT-1.33.0010 (SAPP50000)
CPLD-12
RADIO-3.22.20.17
Jun 2 2009, 17:28:28
[myTouch 3G, Magic Android Development] polaroid22:
No, I was thinking about Rogers with see my phone as a updated one and phone will restart working, so, I just tried online chat and refuse to do a network refresh since I said that update was did yesterday evening and I have to wait 24h to escalate call to engineer...
[myTouch 3G, Magic Android Development] aaziz:
Don't bother waiting. Just insist they do a network upgrade for you. If they won't, try again. You might have better luck with customer service or Iphone support. Just tell them you lost data again and if they could please do a network reset.
[myTouch 3G, Magic Android Development] bcrook:
SPL won't help speed I don't think but it lets you flash .img files, which is a great way to recover from soft-bricks (nearly a brick). Remember, that Dream ROMs will usually require an SPL (like Danger) because they need a larger system partition. This will happen with Sapphire too, an example of this is CursorSense that uses the 1.76 SPL. I am running 1.33.2010 eng. SPL and was previously on .2005. I only switched because it was easier to find the .2010 when I reverted from a CursorSense install.

If you need more clarification or help, Gtalk me :)
[myTouch 3G, Magic Android Development] cursordroid:
He's using your port file, so you might want to talk to him about the file hosting arrangements, credit, etc...
[myTouch 3G, Magic Android Development] bcrook:
Yeah, I don't think I will, but it's weird there wasn't a heads up...
[myTouch 3G, Magic Android Development] polaroid22:
I had called this afternoon, tech have take my imei information and was supposed to forward info to second level support team. After hangup, I removed battery and SIM card and waited 1 hour. I've tried twice, still not working... :(
[myTouch 3G, Magic Android Development] aaziz:
What build number, ROM, SPL, and radio do you have?
[myTouch 3G, Magic Android Development] polaroid22:
build since I use bcrook fix I can't check on device but I think it's DC83 if I remember.

Rom is CM 4.2.13, SPL 1.33.2005 and radio 3.22.20.17
[myTouch 3G, Magic Android Development] SpaceBoy2000:
Okay, I'm a moron. I left it on for two days, and didn't get a connection. I finally caved (or rather, realized I still didn't have a connection, since I spent most of the time on WiFi) and called Rogers - 5 min wait + 5 min call, and I'm up and running after a network reset.

Morale of the story: call iPhone support, don't be a moron, reset your damn connection, continue on with your life. w00t.
[myTouch 3G, Magic Android Development] :
That was a crazy easy experience.

I switched over to Cursor's ROM from Cyanogen on Saturday and had 3G all Sunday and Monday without problem.

But it hit me once again that I prefer CM over the Hero ROM (nothing personal against Cursor's awesome support and dev work). I read all the threads, switched back to CM 4.2.13 last night, applied Brian's patch but forgot to update the ro.build.id (I only updated the ro.build.display.id).

I lost 3G today, late afternoon.

I fixed my build.prop and build.sapphire.prop files before dinner, called Rogers and the tech support claimed there was no way for him to do any reset for me - that I would have to wait as much as 24 hrs for my update to kick in (I told him I applied the Rogers HTC update).

After reading the post and others here I realised I would not automatically get 3G again without intervention.

http://howardforums.com/showpost.php?p=13459094&postcount=302

I decided to try the iPhone trick, called just now, got a hold of someone in 2 min, and 2 min later I've got full 3G. Hopefully it sticks.

Who knows, the guy could probably see that I don't have an iPhone on my account but he reset my network connection anyway and with no argument.
[myTouch 3G, Magic Android Development] kzin:
What Roger's is Saying

Saleh says:

Please note if you have updated the device and your data still does not work note that it will take about 24 hours to have the data working again. It has been rumored that a "network refresh" will work however word from network operations is that the block will come back again if a "network refresh" is performed. If you're phone has been past 24 hours since the update we can escalate you're issue to higher level engineering. They will run a backround check on the version you are running on you're phone if its found that you are running non rogers build on you're phone the fix will not work and they will not be able to remove the block.
[myTouch 3G, Magic Android Development] Survivor.Sole:
No more updates.

Look likes Cyanogen left us... :(
[myTouch 3G, Magic Android Development] polaroid22:
I'd called at lunch time, I told him that yesterday I'd called for data issue, CS said that no ticket as been opened for that... :S

So, a new ticket as been sent to network team, tried 2 hours later and still no data... *sigh*
[myTouch 3G, Magic Android Development] walie:
Quit whining, geez

This was tweeted by Cyanogen today:

"nope, gonna release an update either tonight or tomorrow for 4.2"
[myTouch 3G, Magic Android Development] frankinmerth:
Worked for me also. Calling the 'press 3' put me into 30 minute queues, calling iphone support went straight to operator.

I told him I had a network update that bunged up my 3g and it said if I didn't get it back in 24 hours to call in and ask for a network reset. He tried walking me through the iphone menus for a bit before I fessed up that 'oh.. no mine is an HTC!'. He said oh... we'll have to switch you over to PDA support. I told him that I was just calling in to ask for a network reset as per the HTC update instructions to fix 911, and could he try that first before I go on hold for a half hour?

He gave it a go, and wala, 3G came back up.

I'll chime in again if it drops, but for now it works.
[myTouch 3G, Magic Android Development] aaziz:
If you applied bcrook's patch it shouldn't say DC83, I don't think. check back in the thread for what i reported. make sure you use netfix2 file.
[myTouch 3G, Magic Android Development] polaroid22:
No on phone with fix it say DRC83 1.89.631.1 since it's not accurate information as far I remember before fix it was DC83
[myTouch 3G, Magic Android Development] :
If Cyanogen does release a new version maybe bcrook would be into including his netfix2 into his kernel port???

Maybe???

It would save us some time and trouble :)
[myTouch 3G, Magic Android Development] walie:
I hope not, if the netfix2 port is anything like the first one he released, i lost access to several protected apps in the market as a result. i don't think you need it anyway, i have data with the original port right now
[myTouch 3G, Magic Android Development] olvap377:
i am using a roger's dream and was wondering if bcrook or radix could make and ebi1 port of the ram hack cause my dream has a 32b board but is still ebi1. i bet alot of people would aprreciate the extra 10mb of ram
[myTouch 3G, Magic Android Development] frenchy128:
i think...

Yes, I recalled seeing DC83 as my build prior to applying netfix3 the patch.. I corrected the build.prop and build.trout.prop files that were provided to what rogers (i believe) wants too see..

Sorry for the image quality...

Changed -

- ro.build.version.release=1.6 to ro.build.version.release=1.5

- ro.product.locale.region=US to ro.product.locale.region=CA

- ro.product.model=TMobile G1 to ro.product.model=HTC Dream

- and every instance of "DR83 1.89.631.1" to "1.89.631.1 146733 CL#94714 release-keys"

I attempted to change the SDK from 4 to 3 (1.6 to 1.5) but this resulted in a black screen after the Android Logo..

Not sure if the mod's I made will help.. Here's hoping that my ticket that I open 24hr's ago results in a network refresh.
[myTouch 3G, Magic Android Development] polaroid22:
I just discovered these posts:

Original

http://xdaforums.com/showpost.php?p=5440198&postcount=6

User comment

http://xdaforums.com/showpost.php?p=5480955&postcount=416

It might be an solution for us.

What do you think?
[myTouch 3G, Magic Android Development] :
Do you have to change the build version from 1.6 to 1.5?

I didn't do that.

I have had data now for close to 48 hrs, but I got an email notice saying I needed to upgrade.

Not sure if that was automatic or pushed to me because they're gonna black me out.

A lot of people are wondering whether we need the newer radio too - maybe Rogers is checking this.
[myTouch 3G, Magic Android Development] frenchy128:
I don't think so, I just did it.. I believe it's the build number there looking for, but I'm unsure how they verify this..

I sure hope not..
[myTouch 3G, Magic Android Development] SpaceBoy2000:
So, it looks like the radio, not the build.prop is what Rogers tests for. So, how do we do that for the Magic?
[myTouch 3G, Magic Android Development] polaroid22:
Hey I just got data! (Edge only at this moment)

Since I made 4-5 call to rogers service to get a network refresh that seems that finally someone did it. :D
[myTouch 3G, Magic Android Development] bcrook:
We can change the radio but then we would have to port cyanogen for it. I believe the working theory is that once you get data, its there for good.

I can maybe look into porting to the 6.x kernel. I will speak to cursordroid.
[myTouch 3G, Magic Android Development] zuk_:
I'm starting to believe that Rogers is checking only for the build number (I changed mine to what Rogers is looking for and subsequently had my account unlocked).

But for at least some people (like myself), only having a valid build number reported is not enough. Even though my account is unlocked, I'm still not getting any data. I think a radio update may be necessary (and I'm not really sure how to go about it on the HTC Magic).
[myTouch 3G, Magic Android Development] :
That would be proactive and very helpful Brian.

FYI...even with the applied netfix2 patch for my Magic, I keep getting messages from Rogers. I would not be surprised if my network access for 3G gets pulled soon.

On a side note, assuming there have been some new code improvements put into the radio version, I have been wondering why Cyanogen or anyone else haven't already updated the kernel to work with the newer radio 6.x. Maybe that was to save everyone from a potential risky upgrade. However, I have applied the new radio version as per Cursor's instructions and downgraded to the older version to run Cyanogen again and it was straightforward and easy.
[myTouch 3G, Magic Android Development] :
I just got an automated phone call on my cell to warning me to apply the Rogers upgrade.

I have applied the netfix2 and changed my build.prop and related files.

My build number is the right one.

I'm not buying that Rogers can't see who has upgraded and who hasn't.

If that were the case then they would be placing automated calls to every HTC customer.

I wonder if anyone who is on Cursor's ROM is getting the same call.
[myTouch 3G, Magic Android Development] Survivor.Sole:
Yes. Good News!
[myTouch 3G, Magic Android Development] apacheo:
I'd rather see a 5.0 beta (i.e. an eclair rom) for dream/magic than another 1.6-based build. CyanogenMod is being left behind by other quality roms at the moment...
[myTouch 3G, Magic Android Development] xaueious:
I'm trying to run SuperD 1.7, and it seems that using the old SuperD boot.img from bcrook disables multitouch even though it boots. The boot screen also shows up as a white rectangle with black bars on top and bottom.

Is there already one compiled somewhere?

I could go back to Cynogenmod, but Super D seems alright so far.