Related
......................
Some rogers phones are having connectivity problems with the 2.22.19.26I radio. You could try switching back to the stock radio to see if this fixes your problem. See the link to the guide below. Since you have already rooted you won't be able to follow that guide exactly.
http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_Rogers_Dream_EBI1_to_CyanogenMod
You need can get the radio from http://www.stevebirstok.com/android/losemyroot.zip and the ra-recovery and EBI1 port from the guide. Use fastboot to flash the radio and the recovery, boot into the recovery then flash the port file. That port file is for cyanogen so you may have to switch to that unless there is a port file for what you are using.
If you want to go completely back to stock just use the update on rogers site.
Hope this helps
..........................
I have never personally tried it myself, but I'm pretty sure that it it will reflash everything on the phone. Part of the update is a new spl so it must flash that. Are you asking about a guide for what I talked before or to go back to stock? There really isn't a guide for either. Let me know if you have any questions.
...................
Msn, google talk or irc would be fine. PM me to let me know. I'm not at home right now but ill be in about an hour.
It's been sending for about 10 minutes so far :O
I'm a little worried. Thanks,
It could take awhile.... Which radio did you flash? are you still in the screen where the android is out of the box? Be patient bro, no matter what dont take out the battery, or you will brick your device.
gstar_raw said:
It's been sending for about 10 minutes so far :O
I'm a little worried. Thanks,
Click to expand...
Click to collapse
rjhay22 said:
It could take awhile.... Which radio did you flash? are you still in the screen where the android is out of the box? Be patient bro, no matter what dont take out the battery, or you will brick your device.
Click to expand...
Click to collapse
Hey rjhay22, thanks for the fast reply.
I flashed back to 4.04 from 4.06 as I was having some serious signal problems and random reboots ever since I updated to Froyo.
It just started writing to radio then the following error
writing 'radio' ... FAILED (remote: image update error) finished.
Click to expand...
Click to collapse
Ugh can't be too good...
I can still get into recovery, and I just flashed back to the stock ROM without any problems so I don't think I bricked it. Any idea as to why the radio won't flash? Checked the md5 and it was alright. Possibly a prob with the USB cable/laptops end?
Yah, must be a bad download, I suggest downloading the file again and try. which ROM are you on and which radio are you trying to flash? is it the IMG file? or the update.zip file?
If youre trying to flash 4.0.2 (stock) / 4.0.3 / 4.0.4 versions heres a link for an update.zip version.
http://forum.xda-developers.com/showthread.php?t=614427
these radios are Eclair ROM radios, if you're using FroYo then you should use, 4.0.6. otherwise it'll give you camera FC.
gstar_raw said:
Hey rjhay22, thanks for the fast reply.
I flashed back to 4.04 from 4.06 as I was having some serious signal problems and random reboots ever since I updated to Froyo.
It just started writing to radio then the following error
Ugh can't be too good...
I can still get into recovery, and I just flashed back to the stock ROM without any problems so I don't think I bricked it. Any idea as to why the radio won't flash? Checked the md5 and it was alright. Possibly a prob with the USB cable/laptops end?
Click to expand...
Click to collapse
rjhay22 said:
Yah, must be a bad download, I suggest downloading the file again and try. which ROM are you on and which radio are you trying to flash? is it the IMG file? or the update.zip file?
If youre trying to flash 4.0.2 (stock) / 4.0.3 / 4.0.4 versions heres a link for an update.zip version.
http://forum.xda-developers.com/showthread.php?t=614427
these radios are Eclair ROM radios, if you're using FroYo then you should use, 4.0.6. otherwise it'll give you camera FC.
Click to expand...
Click to collapse
Currently just reverted back to Cyanogen 5.0.6 and trying to get back to 4.0.4. Would the best route be to go into recovery and just flash the zip to do this? I was a little scared of doing it before considering my phone was crashing but I'm pretty sure it's stable in recovery.
(I was trying to flash via cmd with the img file in my tools folder before).
Yes, I find it to be easier and less scary to go through the update.zip file... And the link I gave you, I've been using those files to go back and forth on radio. Good luck brother.
gstar_raw said:
Currently just reverted back to Cyanogen 5.0.6 and trying to get back to 4.0.4. Would the best route be to go into recovery and just flash the zip to do this? I was a little scared of doing it before considering my phone was crashing but I'm pretty sure it's stable in recovery.
(I was trying to flash via cmd with the img file in my tools folder before).
Click to expand...
Click to collapse
rjhay22 said:
Yes, I find it to be easier and less scary to go through the update.zip file... And the link I gave you, I've been using those files to go back and forth on radio. Good luck brother.
Click to expand...
Click to collapse
Right on, everything went smooth and back on the good ol radio. Thanks!
Anytime brother.
gstar_raw said:
Right on, everything went smooth and back on the good ol radio. Thanks!
Click to expand...
Click to collapse
so do you guy sreally think that the froyo radio is faulty somehow, particularly for the ATT version of the N1? i'm thinking of going to froyo, but not sure about the new radio (i'm happy with current radio). but then i hear about video problems without new radio.
is it that easy to bounce back and forth?
Hello again lol. Froyo radio works a lot better than the previous ones for me at least. There isn't anything wrong with it, now this might not be true on yours since you are from another carrier . But you can always switch back to the old one, whatever works best for you.
RogerPodacter said:
so do you guy sreally think that the froyo radio is faulty somehow, particularly for the ATT version of the N1? i'm thinking of going to froyo, but not sure about the new radio (i'm happy with current radio). but then i hear about video problems without new radio.
is it that easy to bounce back and forth?
Click to expand...
Click to collapse
Ok cool, I just gotta figure how how to tell what radio I'm currently using. I'm sure its the previous one that we've been using.
which will be the exact steps to revert my att band N1 to eclair again?
Should i first flash 32.26.00.24U_4.04.00.03_2 radio and then cyanogen's mod? or firts cyanogen's mod and then the 32.26.00.24U_4.04.00.03_2 radio?
im willing to to this, because my gps is not accurate with froyos radio...
Works either way
donchele said:
which will be the exact steps to revert my att band N1 to eclair again?
Should i first flash 32.26.00.24U_4.04.00.03_2 radio and then cyanogen's mod? or firts cyanogen's mod and then the 32.26.00.24U_4.04.00.03_2 radio?
im willing to to this, because my gps is not accurate with froyos radio...
Click to expand...
Click to collapse
rjhay22 said:
Works either way
Click to expand...
Click to collapse
rjhay22, do you think that the oficial release of froyo will have a better radio for all att band N1's? couse mine is kinda sucky right now... the gps is slow and inaccurate...
What yave you heard, will froyo have 850 and 900 separeted radios?
As of now, google has been quiet about what's going to be in the official release. We can only hope that if they include a different radio in that release, that it would work perfectly on both ATT and T-Mobile devices.
donchele said:
rjhay22, do you think that the oficial release of froyo will have a better radio for all att band N1's? couse mine is kinda sucky right now... the gps is slow and inaccurate...
What yave you heard, will froyo have 850 and 900 separeted radios?
Click to expand...
Click to collapse
rjhay22 said:
As of now, google has been quiet about what's going to be in the official release. We can only hope that if they include a different radio in that release, that it would work perfectly on both ATT and T-Mobile devices.
Click to expand...
Click to collapse
whoa! thnx!
dude sorry about bugging this much but, which are those "camera issues" that the people tak about when going back to an old radio with froyo? are there another issues!
RogerPodacter said:
Ok cool, I just gotta figure how how to tell what radio I'm currently using. I'm sure its the previous one that we've been using.
Click to expand...
Click to collapse
You can tell which radio you are using by going into the bootloader; a few lines from the top I believe.
Also in the main settings menu it shows baseband version and it looks like 4. 00. 04 or something like that. Isn't that the radio info?
How long should it take to flash Radio_12.28e.60.140f_26.04.02.17_M2_SF over stock 26.03.02.26_M??? It's been going a good while now and I'm getting freaked out!!
Judging by the radio model, you posted in the wrong forum.
When I install an new ROM, phone only can call out, cann't call in.
Seems install stock ROM then the first time flash 2.3 ROM, phone can call in and out.
muziling said:
When I install an new ROM, phone only can call out, cann't call in.
Seems install stock ROM then the first time flash 2.3 ROM, phone can call in and out.
Click to expand...
Click to collapse
MODS PLEASE MOVE TO HERO CDMA Q AND A SECTION....
...as for an answer....first answer a few questions and then i can help
what radio?
what prl?
what rom?
what extra "mods/tweaks" did you do/you're currently using?
what carrier?
kifno said:
MODS PLEASE MOVE TO HERO CDMA Q AND A SECTION....
...as for an answer....first answer a few questions and then i can help
what radio?
what prl?
what rom?
what extra "mods/tweaks" did you do/you're currently using?
what carrier?
Click to expand...
Click to collapse
radio: 2.42.02.10.29.zip
PRL: 2.20_003
ROM: aospCMod-HC-20110421-signed.zip
no tweaks
carrier: china telecom
try this:
look up on your search engine how to update to the latest prl and pri
then i'd also like for you to try a sense rom, a froyo rom, and cm7.0.2
then i'd like for you to tell me what was the last working rom you used that it worked on?
i have to know this information to help you as best as possible b/c right now there are a broad amount of solutions
kifno said:
try this:
look up on your search engine how to update to the latest prl and pri
then i'd also like for you to try a sense rom, a froyo rom, and cm7.0.2
then i'd like for you to tell me what was the last working rom you used that it worked on?
i have to know this information to help you as best as possible b/c right now there are a broad amount of solutions
Click to expand...
Click to collapse
Last working rom is aospCMod-20110310-signed.zip
I update to aospCMod-HC-20110421-signed.zip last night, and phone call in problem happend, Now I flash Sprint_2.1(2.32.651.2), It works.
muziling said:
Last working rom is aospCMod-20110310-signed.zip
I update to aospCMod-HC-20110421-signed.zip last night, and phone call in problem happend, Now I flash Sprint_2.1(2.32.651.2), It works.
Click to expand...
Click to collapse
Hmp, stick with a rom that works THAT YOU LIKE, not by what I tell you. But did you try these rom's?
- CM v7.0.2?
- GingerSense?
- AOSP 0.9.9.2 Froyo?
- CM6.1-RC2?
- NFX Stock Rom?
- My Sense Roms?
Try all of those and for whichever the phone calls work, take note of that. And then also I'd like for you choose what you like the best. Also did you try the update prl/pri on a sense rom? Try doing it on the rom you're on now
And glad to see it worked for ya bud
muziling said:
Last working rom is aospCMod-20110310-signed.zip
I update to aospCMod-HC-20110421-signed.zip last night, and phone call in problem happend, Now I flash Sprint_2.1(2.32.651.2), It works.
Click to expand...
Click to collapse
FYI the functionality of the dialer is hard-coded into the phone, not each ROM, so if it works at all, it works. Sometimes phone and data issues can be solved by updating PRL and profile as suggested, but it sounds like your issue may have been simply your carrier at the time. If a phone can call out, it can call in, and vice versa. It may have something to do with the fact that you are flashing Sprint ROMs for a Chinese carrier, but who knows. There are a few members in these forums that are on your same chinese carrier and are running aospCMod without issue, one member in particular is called "oldghost", maybe you should PM him and see if he has had any issues, and what ROM best suits the needs of the Chinese version of the heroC. Good luck.
il Duce said:
FYI the functionality of the dialer is hard-coded into the phone, not each ROM, so if it works at all, it works. Sometimes phone and data issues can be solved by updating PRL and profile as suggested, but it sounds like your issue may have been simply your carrier at the time. If a phone can call out, it can call in, and vice versa. It may have something to do with the fact that you are flashing Sprint ROMs for a Chinese carrier, but who knows. There are a few members in these forums that are on your same chinese carrier and are running aospCMod without issue, one member in particular is called "oldghost", maybe you should PM him and see if he has had any issues, and what ROM best suits the needs of the Chinese version of the heroC. Good luck.
Click to expand...
Click to collapse
Yes oldghost uses a Chinese carrier and I don't think he had any issues at all. But first try updating the prl/pri
Interesting. I just realized I'm seeing similar since (I think) flashing 4/29 aosp 2.3.3. Thought I had just messed up on a setting or something. Incoming calls are going straight to voicemail. I see them almost immediately in the call log on the phone, but no ring or any other indication. The only other record of the call would be the voicemail notification after a bit.
Now, my assumption here is that I messed up on my last flash, so I'll go back and do a redo, including going back to a sense rom just in case.
I was coming from 4/21 aosp 2.3.3. Before the 4/21, I did get rid of firerats, installed fresh, updated prl (now at 60678) and profile, though I think that's been current for me for a while.
I then installed 4/21 from scratch (fr 110/4).
Radio has been current.
4/29, I just wiped caches and flashed over.
Like I said, I'm sure I just messed up at one of these points. I don't know for sure when I stopped receiving calls. I don't get a lot of them, so it took me a while for the loneliness to kick in. It IS possible that I messed up on the 4/21 even.
hareofthedog said:
Interesting. I just realized I'm seeing similar since (I think) flashing 4/29 aosp 2.3.3. Thought I had just messed up on a setting or something. Incoming calls are going straight to voicemail. I see them almost immediately in the call log on the phone, but no ring or any other indication. The only other record of the call would be the voicemail notification after a bit.
Now, my assumption here is that I messed up on my last flash, so I'll go back and do a redo, including going back to a sense rom just in case.
I was coming from 4/21 aosp 2.3.3. Before the 4/21, I did get rid of firerats, installed fresh, updated prl (now at 60678) and profile, though I think that's been current for me for a while.
I then installed 4/21 from scratch (fr 110/4).
Radio has been current.
4/29, I just wiped caches and flashed over.
Like I said, I'm sure I just messed up at one of these points. I don't know for sure when I stopped receiving calls. I don't get a lot of them, so it took me a while for the loneliness to kick in. It IS possible that I messed up on the 4/21 even.
Click to expand...
Click to collapse
Try troubleshooting the problem by doing the following things one at a time to see if they work:
- Try a different radio that works for the SPRINT HERO CDMA ONLY (else you will brick your phone, if you need help finding radios let me know)
- Try without firerat's
- Try wiping everything using the latest official clockwork mod 3.0 after backing up everything
- Try s0be's kernel
- Try the official CM7 v7.0.2
i can come up with more options for you to try one by one but that should last you for about an hour or so
after doing all those let me know what happens
Actually, got this working again.
flashed aosp 2.3.3 4/29 clean, removed firerats, etc (since my next step would have been to put on a sense rom).
clean install seemed to fix the problem. Able to receive calls.
then for fun... did the full factory reset and wipe wipe wipe again, installed this time WITH firerats (100 20), bumped the cache size for the hell of it.
That worked as well. Calls being received. I think something just got hosed, or my original 4/29 install, which was just a cache wipe and flash over, didn't go so well.
Still figure it was user error on my part somewhere along the line, but all is well for me now.
hareofthedog said:
Actually, got this working again.
flashed aosp 2.3.3 4/29 clean, removed firerats, etc (since my next step would have been to put on a sense rom).
clean install seemed to fix the problem. Able to receive calls.
then for fun... did the full factory reset and wipe wipe wipe again, installed this time WITH firerats (100 20), bumped the cache size for the hell of it.
That worked as well. Calls being received. I think something just got hosed, or my original 4/29 install, which was just a cache wipe and flash over, didn't go so well.
Still figure it was user error on my part somewhere along the line, but all is well for me now.
Click to expand...
Click to collapse
Glad to see its working now. If you need any more help feel free to PM me or post again in the q n a forum and the community and myself will gladly answer your question asap.
same problem with hareofthedog, strange, phone can't call in ,but call log has call-in logs..Do I can use some command to print kernel logs?
flash cm7.02, now phone can call in
muziling said:
same problem with hareofthedog, strange, phone can't call in ,but call log has call-in logs..Do I can use some command to print kernel logs?
flash cm7.02, now phone can call in
Click to expand...
Click to collapse
if a rom isn't broke, don't fix it...stick with gingerbread, its fresh out the oven
but seriously if cm7 works, then use it. unless if you really don't like cm7....but i doubt that..i hope
Hi is there a 2.2 rom for the incredible s that is close to stock that i can flash in clockwork recovery?..thanks
fridaycider said:
Hi is there a 2.2 rom for the incredible s that is close to stock that i can flash in clockwork recovery?..thanks
Click to expand...
Click to collapse
I should think the very early versions of some ROMs might be 2.2... Possibly ARHD? Worth asking the devs directly, or looking at old versions of the ROMs in the development forum.
All that said, why do you even want a 2.2 ROM?
Thanks for the reply. i have had a look but couldnt see any..
The reason i want to downgrade is because of the delayed text messages and poor network reception which i didn't have a problem on 2.2..
fridaycider said:
Thanks for the reply. i have had a look but couldnt see any..
The reason i want to downgrade is because of the delayed text messages and poor network reception which i didn't have a problem on 2.2..
Click to expand...
Click to collapse
If you have upgraded to a GB Rom and radio combination, you may have a problem trying to go back to a Froyo Rom and radio. Although the Rom can be downgraded, you probably will have an issue trying to downgrade the radio and a GB radio with a Froyo Rom will not work. You won't be able to make or hear calls.
fridaycider said:
Thanks for the reply. i have had a look but couldnt see any..
The reason i want to downgrade is because of the delayed text messages and poor network reception which i didn't have a problem on 2.2..
Click to expand...
Click to collapse
Which ROMs have you tried so far?
right i decided to try and go back to 2.2 and couldn't downgrade the radio to a 2.2 one, but really stupidly ran a ruu and lost root access but still had revolutionary.
tried to re-run revolutionary without success so was stuck with 2.3 without root so could not install recovery or anything and no permissions.
eventually got root access back by running superoneclick 2.2.1 now everything is back to normal..
not going to mess anymore as i have messed it up once,next time it'll probably get bricked. i'll just wait for a fix...
Why don't you just try a different gb radio.
Quick question to the vivid folks, does thecubed's restore work? (the one from ICS to GB). I was reading through some of the questions and it seems like some people had trouble working it out. Has anyone had success with it? I dont want to end up like the guy who had his radios deleted...
I can't directly answer your question. If you are stock and un-rooted the update through ATT works really well. I had no issues whatsoever with the update..
My issue with ICS right now is there no voice dialer when using bluetooth. Other than that it is really fluid and works well.
im on the pre rooted ics and i dont really like it. I'm going back to GB.
never used thecubed's method, but i have installed holiraider(gb) rom after ive installed pgs rumfloat(ics) with no problems
just flashed the boot.img through fasboot then flashed the rom zip on cwm
and everything worked fine
hope this helps
Sent from my HTC PH39100 using XDA
^didnt know you could do that. hmm. I might just do that...
Hanzee94 said:
Quick question to the vivid folks, does thecubed's restore work? (the one from ICS to GB). I was reading through some of the questions and it seems like some people had trouble working it out. Has anyone had success with it? I dont want to end up like the guy who had his radios deleted...
Click to expand...
Click to collapse
I can only assume that when you say "that guy" you mean me, but that method works, but it won't downgrade your radio back to the gb radio. what you thought was deleted radios was a result of swapping out RIL files so the rom didn't know what show in the info because the files are different and can't be swapped out like on other htc phones such as the inspire 4g. and the reason i was playing around with that is because i believe it's what causes people hearing their echo back when i talk to them while i'm on speakerphone.
with that being said, good luck to you. let me know if you have similar issues otherwise ur stuck on ics
i3am5not8real13 said:
never used thecubed's method, but i have installed holiraider(gb) rom after ive installed pgs rumfloat(ics) with no problems
just flashed the boot.img through fasboot then flashed the rom zip on cwm
and everything worked fine
hope this helps
Sent from my HTC PH39100 using XDA
Click to expand...
Click to collapse
I can vouch for this as well. I flashed back and forth between ICS and GB ROMS. Just fastboot flash the boot image and do not try to reflash any HBOOT to go back to GB or you will likely brick your Vivid.
Sent from my HTC PH39100 using xda premium
I used thecubeds' GB restore 2x: #1 went from ICS RUU.52 to GB then did the OTA to .56 and #2 my wifes phone got an error during the .56 OTA install. I just pulled the battery and put in my EXT SD with the PH file and went back to GB then did the OTA again with success. It's pretty simple and worked perfectly both times. Glad I have that file. Thanks thecubed!