[Q] Rogers Dream and non-working 2G/3G - G1 Q&A, Help & Troubleshooting

I have a Rogers Dream on the Rogers network with the old radio and eng spl which I tried to upgrade. It was already rooted and working with CM6.1, but I tried to flash the new radio and spl on it.
I flashed hboot-1.33.0013d.img and radio-2.22.27.08.img.
I wiped everything and reflashed CM6.1 and realized that the phone no longer connects to EDGE or 3G. It can still connect to the internet through wifi.
This is actually my wife's phone and I did this a while ago, so I don't remember that clearly, but correct me if I'm wrong, the board is supposed to be 32A on a Rogers Dream right?
I finally decided to try and revert to the old radio / spl and see if that would fix the problem, but she still doesn't have data connection.
I flashed radio-3.22.26.17_dream.img with hboot-1.33.2005.img, but bootloader still says 32B. Is there something I'm doing wrong?

remember that e911 upgrade... They forced you to upgrade or cut data.. what they are checking for is that you have installed that craptastic radio that keeps dropping 3g until you either giveup and use 2g only, or go to airplane mode and back.
If you change to *ANY* other radio rogers then blocks your data.
Take a spin: http://www.rogers.com/htcwaiver/
you win if it works (data back in 24h or so and you can use the new radio.. call if you need then to be more proactive)..
-1 point for invalid IMEI,
-2 points for invalid mobile number.
(note to self never buy a phone a on contract [didn't but a reminder] or from a Canadian carrier I may ever use.. ie. phone must be unlocked from an independent source)

I guess I have to call them, their website conveniently says I entered an invalid IMEI code.
Which version was the Rogers radio that worked anyway?

yingjai said:
I guess I have to call them, their website conveniently says I entered an invalid IMEI code.
Which version was the Rogers radio that worked anyway?
Click to expand...
Click to collapse
um 3.22.26.17 was the one that they won't disable your data.. "worked" is a bad word for it since it has a nasty habit of dropping 3g.. if you are calling them anyway ask to sign the wavier.. you may want to upgrade to the e911 update with 3.22.26.17 + re-root to an ebi1 rom until they actually add you .. then fastboot back to 2.22.28.25 + 2708+ kernel

So they won't let me sign the waiver if i have the 2.22.28.25 + 2708+ kernel?
I just rerooted her phone trying to fix things and reflashed that stuff...

yingjai said:
So they won't let me sign the waiver if i have the 2.22.28.25 + 2708+ kernel?
I just rerooted her phone trying to fix things and reflashed that stuff...
Click to expand...
Click to collapse
If you are on the list its fine to install 2.22.28.25, but if there will be a delay before you are added.. 3.22.26.17 may be better while you wait for them to add you or you may get the boot again while you wait to be officially on the list

boot as in they'll say no if i ask to sign the waiver? what's the point of the waiver if i already have the radio?

Related

Rogers Dream questions

I realize there are numerous threads about the phone, but I have several questions and I don't think they fit into any single thread. Merge this if necessary.
First of all, the phone in question ran on Dwang's rom using EBI0 root hack. After the 911 bug thing with Rogers, they disabled the internet and the phone did not have data and sms. I found out about Cyanogen's radio update trick and proceeded to try it. I flashed the latest Cyanogen rom first, then did the radio update with the EBI1 kernel patch. The phone boot up normally.
Several days later (haven't used the phone), I realized another problem. Data and sms came back, but now I can't call or receive. Has anyone any idea about this problem?
[edit] Realized it is a temporary issue (one of many) with Rogers as other people I know can't call either.
I also pulled the battery out for some reason and noticed it was bloated/fatter/expanded/etc. Went to Rogers store and they were going to replace whole phone instead of just the battery. They're probably doing that to ensure I get a phone with the unrootable update.
Question is: Will Rogers realize if I send the new phone back with the old battery?
yingjai said:
Question is: Will Rogers realize if I send the new phone back with the old battery?
Click to expand...
Click to collapse
Yes due to IMEI, but if they ask just say you didnt need the phone.

No connection

Background: Switched to backup battery pack, lost internet service. Rebooted a few times, then had no reception at all.
I backed up and wiped, but nope. I'm guessing the SIM card's damaged? (happened before)
So I need to call Tmobile. Before I call Tmobile, though, I need to downgrade and unroot. So I went back to RC 29 with DREAIMG.nbh as usual (done this before. kiiiiinda getting sick of the g1 now.)
Now I have original SPL and have RC29. Also have RA recovery, but I can reapply dreaimg and get rid of that.
Problem: I need to upgrade my phone, since it'd be kinda weird if I called and I said I was on RC29. Thing is, either cellphone reception is needed for OTA updates (that is, non-wifi internet connection), or they're simply not supplying OTA updates for the 29.
I guess I need to manually update, but that would require root (which I have, but need to get rid of before I call t-mo). If you have a way to update an RC29 to 1.6, or have a way to unroot without using DREAIMG.nbh, please post. Also might need a link to the standard, no-root 1.6 file.
If there are any questions, or at some point in the above post i was spouting nonsense, please tell me.
Thanks!

HTC Dream losing 3G?

I'm wondering if anyone else ever came across this weird issue. I am on the Rogers network with a HTC Dream. I've tryed several ROMs and none make a difference. The issue is, I lose 3G connection and my SIM card gets corrupted. I have a LG GW620 and I used it for a long time and this never happened. What happens is I totally lose 3g capability and I can't get it on any other phone unless I get another SIM card activated. I've had this happen to me twice now and it ONLY happens when I used my HTC Dream for couple weeks it seems. Could this be due to that my phone is using roms or is my phone just mangled? I'm just thinking of smashing this phone with a hammer as it is useless to me if my 3G connection is gone.
Any information would be appreciated.
Thanks
IIf you currently have radio 3.22.26.17, please find and download the 3.22.20.17 radio image and flash via fastboot 'fastboot flash radio-3.22.20.17.img'
The image is on bcrooks server.
Please note the imei-sv is 3 in 3.22.26.17 but 2 in 3.22.20.17, this means if you are a rogers/Fido customer with a rogers branded dream you will be flagged by rogers for not having the e911 rom.. and thus they will disable your data if you have not filled the wavier. To reactive a call to the call center is usually required (preferably on a phone other than the cell in question)
Note the radio has nothing to do with the e911 issue, as the bug was in android not the radio.. so if you have signed the wavier or are not a rogers customer feel free to use 3.22.20.17.. of if preferred downgrade to 2.x via fastboot
(its unknown if the lattest 2.x or the older 3.x provides better signal on the Rogers network .. but the newer 3.x has problems in every rom.. including the official one HTC/rogers forced on everyone, sad since the bug was just in the Java code of one file on the phone in /system.. nothing to do with the radio)
Alright just let me get this straight.
So they are flagging me because of my phone, or radio? I am a Rogers Customer, have been since 2004 I believe. How would I go about getting data to not dissapear on my phone again? I had just bought this phone used and rooted it and put on a custom OS. I'm not exactly sure which radio I have at the moment, but if i update to 3.22.20.17 would that fix the issue if I got rogers to re-activate my data?
What radio do you have now
I believe this one is on there.
Radio Image update 2.22.23.02
So if I update to Radio 3.22.26.17 via Fastboot and call the support line to re-activate my data or w.e that will work?
Not quite that simple your current rom wont work with the 3.x radio as is..
I recommend one of two things..
1) goto http://rogers.com/htcwaiver and sign it.. then call rogers saying you signed the waiver and want data back.. if it fails tell them that..
2) if this is a rogers branded dream and I assume it is unroot to the stock e911 patched rogers rom and start from scratch on android 1.5 .. this is not optimal and I highly recommend option 1.. and you still may need to call after to get data back http://forum.xda-developers.com/wik...Branded_EBI1_Dreams#Returning_to_Stock_Rogers
Huge low blow in Rogers case. Plus I have to call them cause they say my number does not exist when I put it in that Waiver. What a joke in my opinion.
Thanks for the information though. Much appreciated.

[Q] Is Flashing the Radio Possible with ICS??

...well......just like the tittle says....is it possible to flash the radio on the bionic under stock ICS???
Reason I ask, is because it might be the reason I cannot for the life of me get the bionic working on another CDMA carrier and have it up and running on 3G.
I believe maybe the radio has a part in that.....!?!?!?
I am trying to get it up and running on a non US CDMA carrier. I actually had the razr working with out problems and would only pick up 3G on CDMA if the verizon sim card was in the phone, otherwise voice but no 3G. I had a droidx running untill the last update that got a new radio and my 3G died. I also have done a razr , a photon, and a droid x2.....not saying I am a guru, but just saying I have had my share of getting phones up and running, and never had any headaches like I have had with his one.....I only get voice but no 3G. I even go to *#*#4636... and will pick up both 1X and 3G strong signals but will NOT connect.
So figured the radio could be the culprit...
Any input will be welcomed.
P.S. I have followed several guides for other carriers and same result on all, voice ad no 3G.
Have you been entering the proper APN's for the other CDMA carrier? The symptoms you're describing are a classic symptom of the device not having the APN's set correctly. ##PROGRAM in the dialer should help you.
If you believe the radio is corrupted for some reason, you can reflash it to make sure there aren't any issues. Just grab the FXZ file for ICS, and make sure you have fastboot.exe available from the Android SDK. Reboot the Bionic into fastboot mode. Make sure that the radio file is in the same folder as fastboot.exe. Then just type in 'fastboot flash radio radio.img' and then you'll have a brand new reflashed radio to start tinkering with.
projektorboy said:
Have you been entering the proper APN's for the other CDMA carrier? The symptoms you're describing are a classic symptom of the device not having the APN's set correctly. ##PROGRAM in the dialer should help you.
If you believe the radio is corrupted for some reason, you can reflash it to make sure there aren't any issues. Just grab the FXZ file for ICS, and make sure you have fastboot.exe available from the Android SDK. Reboot the Bionic into fastboot mode. Make sure that the radio file is in the same folder as fastboot.exe. Then just type in 'fastboot flash radio radio.img' and then you'll have a brand new reflashed radio to start tinkering with.
Click to expand...
Click to collapse
APN???? in CDMA??? Could you please explain a little??? I believed apn's where only used for gsm. But then again, I could be wrong....
Since I did not find any posts regarding radio flashing, do you know where I could find older radio files for the bionic, as I have not seen anything.
I am on ICS and would like to flash the GB radio if possible......(if possible)
Thanks!

[Q] Unrooting HTC One running 3.04.651.2 with hboot 1.55

Hi All ,
My apologies if there is a solution to my problem in another thread. I have spent countless hours looking for a way to unroot my Sprint HTC One because the Sprint network can't seem to activate it until I do. Or I need to figure out a way to force the Sprint network to accept my MDN and MSID which can "sometimes" be problematic with rooted devices. It might be easier to just unroot and see if that helps getting the phone to properly activate.
Other than the network connectivity issues, the phone is fully functional. Just cant make calls or send texts.
I am running this ROM based on benny's system dump: http://forum.xda-developers.com/showthread.php?t=2467607 so my device information is:
Android version - 4.3
Sense version - 5.0
Software version - benny's 4.3
Kernel version - [email protected] #1 SMP PREEMPT
Baseband version - 1.00.20.0913_3
Build number - 3.04.651.2 CL251863 release-keys
I've tried everything I can think of to get my device unrooted, but none of the RUUs work due to being on hboot 1.55 s-on or having an older firmware version (1.29.xx or 1.39.xx.)
Is there any method I can use to get completely back to un-rooted stock rom with, relocked boot loader (know how to do that part), stock recovery, etc?
I've looked at so many different threads and google searches and all say you need to be s-off and run RUUs of versions that will either cause my touch screen to not work or worse. If anyone can help me it would be amazing and I would be much obliged.
I am having similar issues. I'm about to try this method - http://forum.xda-developers.com/showthread.php?t=2470569&page=3 Read OP and see post#27
jharre08 said:
I am having similar issues. I'm about to try this method - http://forum.xda-developers.com/showthread.php?t=2470569&page=3 Read OP and see post#27
Click to expand...
Click to collapse
Ah yes! The 3.04 version wasn't available the last time I read that post! I can confirm that the other that using the 1.29 and 1.31 versions caused serious issues for me and my phone. This post is actually what led me to learn about the issues due to different firmware and file structure between new and older versions.
I'm downloading now. Let me know how it goes!
tuckprodigy said:
Ah yes! The 3.04 version wasn't available the last time I read that post! I can confirm that the other that using the 1.29 and 1.31 versions caused serious issues for me and my phone. This post is actually what led me to learn about the issues due to different firmware and file structure between new and older versions.
I'm downloading now. Let me know how it goes!
Click to expand...
Click to collapse
Also, check this out - http://qbking77.com/development/how-to-unrootunbrick-the-htc-one-to-stock-2/
It's a bit dated, but I am going to try this method if I can find a 3.04 RUU. Note, he is doing this to an S-On phone, which is what we have. So it SHOULD work:good:
Nothing against the first method I posted, but I'd much rather do a RUU and get a clean slate...
There is no RUU for 3.04 yet ( that I know of)...
this is your best (and pretty much only) option: http://forum.xda-developers.com/showpost.php?p=46565593&postcount=27
Did you ever find a way to resolve this issue? Also did this start after flashing Cyanogenmod? I have the exact same issue and it seems I have exhausted all available resources. Currently have the following setup:
Android version - 4.3
Sense version - 5.0
Software version - 3.04.651.2
Kernel version - [email protected] #1 SMP PREEMPT
Baseband version - 1.00.20.0913_3
Build number - 3.04.651.2 CL251863 release-keys
Noticed that the phone is unable to update PRL correctly. Version will switch from 00000 to 1 to 55016. I am also unable to commit changes to any EPST settings (which is the first thing sprint tried to do). MDN and MSID both currently say 'no' and I can't update.
I'm having the exact same issue with everything working fine but no calls/texts.
I flashed the Guru reset for 3.04 but still no calls/text.
Any other solutions?
kindabizzie said:
I'm having the exact same issue with everything working fine but no calls/texts.
I flashed the Guru reset for 3.04 but still no calls/text.
Any other solutions?
Click to expand...
Click to collapse
Try the following:
Full wipe. Flash the newest stable CM.
Go into Settings > More... (under Wireless & Networks) > Mobile networks > CDMA subscription:
Confirm the following settings:
Network mode = LTE/CDMA/EvDo
CDMA subscription = NV
After you confirm these settings, switch the network mode to CDMA/EvDo only and then back to LTE/CDMA/EvDO.and give it a minute or so, you should see 3G/Phone availability come back. You can test this by dialing a number. You should be able to make a call, or at least get the default Sprint "device is not activated" recording. After confirming this, you can do another wipe and flash back to a stock ROM. You should now have mobile network connectivity back. You may need to Activate the phone again and update the profile/PRL to get back to 100%.
jjmckaskie said:
Try the following:
Full wipe. Flash the newest stable CM.
Go into Settings > More... (under Wireless & Networks) > Mobile networks > CDMA subscription:
Confirm the following settings:
Network mode = LTE/CDMA/EvDo
CDMA subscription = NV
After you confirm these settings, switch the network mode to CDMA/EvDo only and then back to LTE/CDMA/EvDO.and give it a minute or so, you should see 3G/Phone availability come back. You can test this by dialing a number. You should be able to make a call, or at least get the default Sprint "device is not activated" recording. After confirming this, you can do another wipe and flash back to a stock ROM. You should now have mobile network connectivity back. You may need to Activate the phone again and update the profile/PRL to get back to 100%.
Click to expand...
Click to collapse
Didn't work man, thanks though. My data is fine, I just can't call/txt...it's really bizarre...
kindabizzie said:
Didn't work man, thanks though. My data is fine, I just can't call/txt...it's really bizarre...
Click to expand...
Click to collapse
Hmm. That's pretty much the issue that I had except 4G/Wifi was working and 3G/Call/Text didnt seem to be. You might try switching the CDMA mode to SIM and then back to NV to make sure the setting takes. I know CM can be really finicky with network changes.
tuckprodigy said:
Hi All ,
My apologies if there is a solution to my problem in another thread. I have spent countless hours looking for a way to unroot my Sprint HTC One because the Sprint network can't seem to activate it until I do. Or I need to figure out a way to force the Sprint network to accept my MDN and MSID which can "sometimes" be problematic with rooted devices. It might be easier to just unroot and see if that helps getting the phone to properly activate.
Other than the network connectivity issues, the phone is fully functional. Just cant make calls or send texts.
I am running this ROM based on benny's system dump: http://forum.xda-developers.com/showthread.php?t=2467607 so my device information is:
Android version - 4.3
Sense version - 5.0
Software version - benny's 4.3
Kernel version - [email protected] #1 SMP PREEMPT
Baseband version - 1.00.20.0913_3
Build number - 3.04.651.2 CL251863 release-keys
I've tried everything I can think of to get my device unrooted, but none of the RUUs work due to being on hboot 1.55 s-on or having an older firmware version (1.29.xx or 1.39.xx.)
Is there any method I can use to get completely back to un-rooted stock rom with, relocked boot loader (know how to do that part), stock recovery, etc?
I've looked at so many different threads and google searches and all say you need to be s-off and run RUUs of versions that will either cause my touch screen to not work or worse. If anyone can help me it would be amazing and I would be much obliged.
Click to expand...
Click to collapse
You may need to flash a stock rom and manually enter you MDN and MSID using the epst menu
no luck
At this point I have not had any luck solving this issue. I used Guru's reset tool as well and believe the problem is the radio firmware. I spent a good deal of time on the phone with Sprint support and with a surprisingly competent technician in the store. He tried to work with multiple different systems they have available to get the phone to recognize the Sprint towers with no success.
He said that the phone just isn't recognizing them in any way and commented that a phone that isn't activated will still show bars of service because the phone gets the signals from nearby towers, but just doesn't know what to do with the signal until activated. In my case, all I see is the "X" above the signal bar graphic.
If you're experiencing the same issue as me, there is nothing Sprint can do to make the phone recognize their towers based on the conversations I've had. I saw my options as:
1. Wait for an RUU to come out or something like that
2. Try out different ROMs - jjmckaskie suggested the newest CM, but I would think others might be worth trying as well. Basically anything that uses different radio firmware
3. Get a new phone - This is the option I've gone with. Since my phone is running a stock ROM and the guy at Best Buy where my insurance is from, didn't check the bootloader (would have said "tampered" and "unlocked"), he assumed I never voided my warranty and sent out for a refurb. This may not work if your insurance is through Sprint though. I'm not sure how thorough they are.
tuckprodigy said:
At this point I have not had any luck solving this issue. I used Guru's reset tool as well and believe the problem is the radio firmware. I spent a good deal of time on the phone with Sprint support and with a surprisingly competent technician in the store. He tried to work with multiple different systems they have available to get the phone to recognize the Sprint towers with no success.
He said that the phone just isn't recognizing them in any way and commented that a phone that isn't activated will still show bars of service because the phone gets the signals from nearby towers, but just doesn't know what to do with the signal until activated. In my case, all I see is the "X" above the signal bar graphic.
If you're experiencing the same issue as me, there is nothing Sprint can do to make the phone recognize their towers based on the conversations I've had. I saw my options as:
1. Wait for an RUU to come out or something like that
2. Try out different ROMs - jjmckaskie suggested the newest CM, but I would think others might be worth trying as well. Basically anything that uses different radio firmware
3. Get a new phone - This is the option I've gone with. Since my phone is running a stock ROM and the guy at Best Buy where my insurance is from, didn't check the bootloader (would have said "tampered" and "unlocked"), he assumed I never voided my warranty and sent out for a refurb. This may not work if your insurance is through Sprint though. I'm not sure how thorough they are.
Click to expand...
Click to collapse
Dang, and I was gonna go to a Sprint store after work. *Sigh* guess I have NO CHOICE but to get a Nexus 5 now, lololol
kindabizzie said:
Dang, and I was gonna go to a Sprint store after work. *Sigh* guess I have NO CHOICE but to get a Nexus 5 now, lololol
Click to expand...
Click to collapse
As a last resort you could also try the hard reset code from your dialer by entering ##72786# . You will need to be on a stock rom. You will also need your MSL code (you can usually get this from Sprint support). This will reset EVERYTHING so be mindful. It will also force a hands free activation/Profile/PRL update after the phone reboots which is sometimes useful.
jjmckaskie said:
As a last resort you could also try the hard reset code from your dialer by entering ##72786# . You will need to be on a stock rom. You will also need your MSL code (you can usually get this from Sprint support). This will reset EVERYTHING so be mindful. It will also force a hands free activation/Profile/PRL update after the phone reboots which is sometimes useful.
Click to expand...
Click to collapse
I still took it to Sprint just to see and they fixed it. Downside is my GPS and LTE is messed up again (Me trying to fix those things is the reason all this happened in the first place) but I'd rather not have GPS than not have phone capabilities on my phone (And LTE in Los Angeles is garbage anyway). I think I'm gonna leave my phone alone for a while tho, lol.
jjmckaskie said:
As a last resort you could also try the hard reset code from your dialer by entering ##72786# . You will need to be on a stock rom. You will also need your MSL code (you can usually get this from Sprint support). This will reset EVERYTHING so be mindful. It will also force a hands free activation/Profile/PRL update after the phone reboots which is sometimes useful.
Click to expand...
Click to collapse
Looks like I am going to go this route. I hit ##72786# and it takes me to SCRTN screen. I'm guessing I just hit menu in the top right, then reset? Then it will prompt me for my MSL code?
jharre08 said:
Looks like I am going to go this route. I hit ##72786# and it takes me to SCRTN screen. I'm guessing I just hit menu in the top right, then reset? Then it will prompt me for my MSL code?
Click to expand...
Click to collapse
Yup. I actually dont remember if it does a full wipe, or just forces an activation/profile/PRL update. But either way it's worth a shot.
tuckprodigy said:
At this point I have not had any luck solving this issue. I used Guru's reset tool as well and believe the problem is the radio firmware. I spent a good deal of time on the phone with Sprint support and with a surprisingly competent technician in the store. He tried to work with multiple different systems they have available to get the phone to recognize the Sprint towers with no success.
He said that the phone just isn't recognizing them in any way and commented that a phone that isn't activated will still show bars of service because the phone gets the signals from nearby towers, but just doesn't know what to do with the signal until activated. In my case, all I see is the "X" above the signal bar graphic.
If you're experiencing the same issue as me, there is nothing Sprint can do to make the phone recognize their towers based on the conversations I've had. I saw my options as:
1. Wait for an RUU to come out or something like that
2. Try out different ROMs - jjmckaskie suggested the newest CM, but I would think others might be worth trying as well. Basically anything that uses different radio firmware
3. Get a new phone - This is the option I've gone with. Since my phone is running a stock ROM and the guy at Best Buy where my insurance is from, didn't check the bootloader (would have said "tampered" and "unlocked"), he assumed I never voided my warranty and sent out for a refurb. This may not work if your insurance is through Sprint though. I'm not sure how thorough they are.
Click to expand...
Click to collapse
Sounds like you solved your issue, but for anyone else having trouble....
I re-tried GURU's reset and it worked. The first time I downloaded it over the 4G network. I also downloaded the OTA over the 4G network. My radio has been giving me fits ever since. Finally, I downloaded GURU's reset over WIFI, then made sure the OTA downloaded over WIFI, and my phone is like new again! No radio issues, everything is perfect. Hope this helps some people...

Categories

Resources