Database Develop

PRI 2.20_003 from the Official Release?? Does it make a difference??

Is it possible to install the new PRI 2.20_003 from the official sprint 2.1 release without having to run the RUU thus losing root.
Would there be any gain from having the 2.20_003 vs 1.68_003/1.70_003?
A few things I have noticed and was not sure if it was because the PRI is that my data connection goes to sleep and my weather does not update, my internet connection stops, my exchange mail says it failed to sync. I end up having to put in airplane mode and back to normal to get the data working again. I was not sure if this had to do with the Radio instructions.

I just experienced the same thing. I noticed that I no longer had weather information on my screen and when I went to update it, I was informed that I had no connection...in spite of the fact that I was showing 5 bars and 3G. I tried to internet and had the same thing. I just rebooted my phone and I'm back to normal. Doesn't look like Sprint pushed any more auto-updates, so its kind of weird.
I'm currently running Damages 2.1 ROM also. Other than this one time, it had been running flawlessly.

Afaik it doesn't allow for MNS over 3G still. I think we still need to flash an Eris based ROM to get that.

Possible to do a reset to update the PRI
I am a new user, but for some reason they're flagging link to Avalaunchmods' "How fix PRI" post in the development forum as an outside link.
I used it once to change back to 1.70_003 from the Flipz-01 custom PRI flipzmod's Fresh 2.0D ROM did. While it said it had to be from a 1.5 ROM, any chance that doing the same ##786# and Reset with the stock 2.1 update.zip running on your phone could make your phone update to PRI 2.20_003 and PRL 65000 or would that just be asking to brick your phone?
My first post, please go easy.

I would think that should work. Your MSL shouldn't have changed, and that was the only real requirement to use the fix. Personally, though, I think I would say wait until root has been gained so you can nandroid before you try it. If you are having major issues and have insurance, though, go for it. Worst that can happen is you end up with another phone after running a Sprint update kills yours.

wadeheisen said:
I would think that should work. Your MSL shouldn't have changed, and that was the only real requirement to use the fix. Personally, though, I think I would say wait until root has been gained so you can nandroid before you try it. If you are having major issues and have insurance, though, go for it. Worst that can happen is you end up with another phone after running a Sprint update kills yours.
Click to expand...
Click to collapse
I am rooted so I can put any rom on. I was just wondering if I can add the new PRI 2.20_003 some how without flashing the Official RUU and will it improve anything over the old ones.

diaknia said:
...any chance that doing the same ##786# and Reset with the stock 2.1 update.zip running on your phone could make your phone update to PRI 2.20_003 and PRL 65000 or would that just be asking to brick your phone?
My first post, please go easy.
Click to expand...
Click to collapse
As soon as I ran Damages 2.1 ROM, I did the ##786# reset and the only thing that was reset was the PRI changing back to 1.70_003 from the Flipz-01. It had no impact on the PRL at all (stayed at 60664).

diaknia said:
I am a new user, but for some reason they're flagging link to Avalaunchmods' "How fix PRI" post in the development forum as an outside link.
I used it once to change back to 1.70_003 from the Flipz-01 custom PRI flipzmod's Fresh 2.0D ROM did. While it said it had to be from a 1.5 ROM, any chance that doing the same ##786# and Reset with the stock 2.1 update.zip running on your phone could make your phone update to PRI 2.20_003 and PRL 65000 or would that just be asking to brick your phone?
My first post, please go easy.
Click to expand...
Click to collapse
The Avalaunchmods thread is for the 2.10_003 PRI that was in an Eris leak which is a Verizon PRI. Thats not what my question is about.
Right now I am on 1.68_003 PRI (1.5 original Sprint PRI) I want to know how to install the official Sprint PRI 2.20_003 without having to flash the official RUU and lose root.

dwertz said:
The Avalaunchmods thread is for the 2.10_003 PRI that was in an Eris leak which is a Verizon PRI. Thats not what my question is about.
Right now I am on 1.68_003 PRI (1.5 original Sprint PRI) I want to know how to install the official Sprint PRI 2.20_003 without having to flash the official RUU and lose root.
Click to expand...
Click to collapse
I'm about same boat, actually. I'm on 1.70_003 PRI (I bought my hero after 1.56.651.2 released), though.
I just tossed the MSL-reset idea out as a possible way of getting new PRI, though I guess for now, it seems you really have to run the RUU.
No big, I'm running the stock 2.1 for right now to see the difference between it and Fresh 2.1.1

wadeheisen said:
I would think that should work. Your MSL shouldn't have changed, and that was the only real requirement to use the fix. Personally, though, I think I would say wait until root has been gained so you can nandroid before you try it. If you are having major issues and have insurance, though, go for it. Worst that can happen is you end up with another phone after running a Sprint update kills yours.
Click to expand...
Click to collapse
Same as dwertz, I'm still rooted as I never used the newest RUU. I've Nandroid-backup'd my Fresh 2.1.1 install, and about to do a backup of the Stock 2.1 Release (from damageless SprintUpdate2.zip) I just installed.
So I should be able to restore after the Reset fine with those backups if I do the MSL-Reset?

I change my to the new PRI and didn't really notice a difference. I didn't know how to manually do it, so I took Damage's ROM that switched every bodies PRI to the Eris PRI and substituted in the new PRI, resigned, flashed, and nandroided back.

4.06 radio and AT&T/Rogers phone incompatibility?

There seems to be a major issue with the 4.06 radio and my phone - every time I have tried to flash it (from both validated .img's and update.zips) my phone becomes extremely unstable afterwards.
It goes into booting loops, hangs at the X, when I get it to boot it crashes while using heavy 3G or WiFi data, reboots when plugged into USB and receiving a call and it becomes almost impossible to get into recovery mode etc, etc.
The only way to get back to a working phone is to revert to stock 4.04. I have tried 5 different times over the last 2 weeks now with the same results every time.
I am starting to wonder if it is a AT&T/Rogers N1 issue or something specific to my device. If it was my device I would think that flashing back to 4.04 would also cause problems but that is not the case. This makes me believe there is there maybe an incompatibility with the leaked Froyo radio.
Appreciate any thoughts/comments.

I'm not having that problem. I flashed Modaco's first FroYo repack with root and the new radio, and things have been fine. To be honest, the only thing I've noticed is that Bluetooth seems to sync a lot faster to the head unit in my car.
Did you do a complete wipe before you installed the update and what applications have you added that may not like the radio?
Edit to add: By the way, you guys have a kick-ass little HTC Magic up there. It may not be a Nexus One, but it more than holds it's own running cyanogen. I have an import that my wife is playing with. I really like it.

Have you tried the 4.6.00.12_7 radio as well ast the 4.6.00.2_2? The 12_7 is working flawlessly for me both on Froyo and on CM 5.0.8-derived ROMs.

I just verified my version - it's definitely the 4.6.00.12_7 Froyo radio firmware.

codesplice said:
Have you tried the 4.6.00.12_7 radio as well ast the 4.6.00.2_2? The 12_7 is working flawlessly for me both on Froyo and on CM 5.0.8-derived ROMs.
Click to expand...
Click to collapse
I tried the 12_7 last night and after flashing it using fastboot, my phone got stuck in a reboot loop. I could get back into fastboot and saw the new radio version on the screen but could not for the life of me get my phone to boot into either the rom or recovery mode - I pulled the battery, took out the SD card etc but nothing worked. This prevented me from flashing a ROM and I could not get into Recovery. After about an hour of trying, I managed to get the 4.04 radio flashed using fastboot and then my phone booted with no problems.
Previously, I tried the various Froyo builds and with no additional apps installed I would still get random roboots when using data via either 3G or WiFi - usually when I try to do something big like downloading/syncing a large file.
This is the story every time I try a 4.06 radio. 4.04 is rock solid.

Have you tried flashing the 4.6 radio via an update.zip as opposed to through fastboot? It's about the only other idea I can think of lol...

Just checked, I flashed the 2_2 last night, not 2_7.
I have flashed the radio via update.zip before and my phone worked but would be unstable. I will have to double check which version I used, could have been 2_2 as well.

codesplice said:
Come to think of it, that's the radio version I'm currently using, and that's where I got mine while I was running his ROM. So yes, flash that zip, flash Kangorama, and you should be square.
Click to expand...
Click to collapse
This is the same radio image I flashed two days ago and it worked for me quite well for an entire day (light 3G use) and then started crashing the phone when I tried downloading larger files (using the Audible app) via both WiFi and 3G in the evening. Once it started crashing I could not get into recovery until after I pulled my SD card. Once it booted OK without the SD card I put the card back and it booted ok again. It would still crash on heavy data use though.

Maybe try the 12_7 radio from http://forum.xda-developers.com/showthread.php?t=692609 ? I'm fairly certain that is the same radio update that I have applied on my AT&T N1.
edit: disregard....
I'm running out of ideas, dude

codesplice said:
I'm running out of ideas, dude
Click to expand...
Click to collapse
I appreciate your input. Thank you. I will try _7 again.

DvTonder said:
This is the same radio image I flashed two days ago and it worked for me quite well for an entire day (light 3G use) and then started crashing the phone when I tried downloading larger files (using the Audible app) via both WiFi and 3G in the evening. Once it started crashing I could not get into recovery until after I pulled my SD card. Once it booted OK without the SD card I put the card back and it booted ok again. It would still crash on heavy data use though.
Click to expand...
Click to collapse
Did you try not running/removing the audible app and see about stability then? What else are you using? Not every app is going to play nice with newer firmware.

attn1 said:
Did you try not running/removing the audible app and see about stability then? What else are you using? Not every app is going to play nice with newer firmware.
Click to expand...
Click to collapse
The crashes started just after I got the Rom installed.
I did the following:
- Nandriod backup (thank goodness for this!)
- I wiped all as per instructions
- Installed radio, rebooted OK
- Installed ROM (Rodriguesstyle 1.6)
- Booted OK into setup
- Configured my phone - first crash just after entering my gmail ID and the syncing of all the apps from the market started
- Rebooted, configured my phone again - apps installed this time but while configuring ChompSMS the phone rebooted again
- Rebooted, phone came up clean, ran OK all day
- Got home and tried syncing Audible content - phone crashed
- Could not get into recovery or boot the phone normally for almost an hour (pulling battery etc did not help)
- Pulled the SD Card and the phone booted, shut down, put the sd card in again, phone booted OK
- Got a phonecall, phone rebooted
- Got fed up and restored 4.04 radio and stock ROM
- Phone stable since
I was running the following apps:
- Autokiller
- Doubletwist Player
- Audible beta
- Silent Sleep
- ChompSMS 4.2
- Switchpro Widget
- Barcode Scanner
- ADW Launcher
- newsRob
- File manager
- Backgrounds
- Rom Manager

DvTonder said:
The crashes started just after I got the Rom installed.
I did the following:
...
- Installed ROM (Rodriguesstyle 1.6)
...
Click to expand...
Click to collapse
What kernel is the Rodrigessstyle ROM using?
Try Modaco's straight up Froyo repack - it has a stock kernel. I'd get as close to stock Froyo ROM/Radio as possible, see what I have and then go from there.
Also, make sure you're using an updated version of chompsms. I think I heard that reports were that it was not compatible with Froyo, but that it's been updated.

attn1 said:
What kernel is the Rodrigessstyle ROM using?
Try Modaco's straight up Froyo repack - it has a stock kernel. I'd get as close to stock Froyo ROM/Radio as possible, see what I have and then go from there.
Also, make sure you're using an updated version of chompsms. I think I heard that reports were that it was not compatible with Froyo, but that it's been updated.
Click to expand...
Click to collapse
I used the stock kernel. ChompSMS 4.1 and later is compatible and I was using 4.2. I am planning on trying the new Kang-o-rama 0.8b1! (CM-5.0.8+2.6.34 Kernel) rather than Froyo - if only I can get the radio to flash.

DvTonder said:
I used the stock kernel. ChompSMS 4.1 and later is compatible and I was using 4.2. I am planning on trying the new Kang-o-rama 0.8b1! (CM-5.0.8+2.6.34 Kernel) rather than Froyo - if only I can get the radio to flash.
Click to expand...
Click to collapse
Why not start with FroYo - the ROM the radio was meant to work with - before flashing anything else? If it doesn't run then, you have a real problem. otherwise, you have no idea where the problem is.

attn1 said:
Why not start with FroYo - the ROM the radio was meant to work with - before flashing anything else? If it doesn't run then, you have a real problem. otherwise, you have no idea where the problem is.
Click to expand...
Click to collapse
Point taken. Back to the basics.

I came straight from Rodriguesstyle 1.6 with the included add-on OV/UV kernel to Kang 0.8b1 without any issues. Even got the 720p hack working beautifully

well i am using the new froyo radio with my ATT nexus one, and its been no different than the old radio. no crashes or anything. however, i had NO idea that there were 2 froyo radios. is that what someone just posted on the first page?

I have had a simmilar experienc, but it is NOT froyo related.
I was rooted, on the desire ROM
It was restarting at seemingly random (and frequent) times through the day -
I reflashed to stock 2.1.
During setup, phone rebooted.
Got through sign-in. Installed some apps. Phone rebooted.
Phone was absolutely fine, as long as I didn't touch it. I would use it - browse, etc. Seemed to be fine. Would then reboot. FLashed it up to froyo. Same.
I think it's the bad RAM issue i've seen reports of, but I'm not sure. Sent in for a replacement.

Let's hope that's not OPs issue, though the problem seems to be pointed in that kind of direction. Hope you get your situation resolved under warranty.
chordmasta said:
I have had a simmilar experienc, but it is NOT froyo related.
I was rooted, on the desire ROM
It was restarting at seemingly random (and frequent) times through the day -
I reflashed to stock 2.1.
During setup, phone rebooted.
Got through sign-in. Installed some apps. Phone rebooted.
Phone was absolutely fine, as long as I didn't touch it. I would use it - browse, etc. Seemed to be fine. Would then reboot. FLashed it up to froyo. Same.
I think it's the bad RAM issue i've seen reports of, but I'm not sure. Sent in for a replacement.
Click to expand...
Click to collapse

market problems

I need a little help.
Recently I've been switching roms back and forth between cm6 and aosp 2.1.
My problem is that on csrom 2.1.5 and damaged 2.09 and even the .5 ruu, I can't download apps from the market.
They all get stuck at "starting download" and nothing changes. I've tried stopping and starting the download with no solution.
The only rom in which market works is in cm6.
Can anyone offer insight?
phone about me
firmware version: 2.1-update (AOSP-1.3)
Kernel Version: 2.6.29.6-cyanogenmod
[email protected] #1
mod version: csrom-2.1.5
baseband version:2.42.01.04.27
build number: EPE54B
edit: surprisingly found this
http://www.google.ru/support/forum/p/Android+Market/thread?tid=71b498c23af08300&hl=en
with today's date...google claims it's fixed..it isn't
maybe it's not a problem on my end...

Could possibly be a problem with the market and/or network, but I just downloaded 4 or 5 new apps from the market earlier today with no hitches or problems at all.
Try updating your profile on a Sense-based ROM, maybe just nfinitefx45's stock. Could be that the market no longer recognizes your data profile associated with your account because of so many recent changes. Settings->About phone->System updates->Update profile
Not saying this will definitely fix your issue but it is a good thing to try. If it works, you could probably re-flash the ROM of your choice after you do this and still be fine.

chromiumleaf said:
Could possibly be a problem with the market and/or network, but I just downloaded 4 or 5 new apps from the market earlier today with no hitches or problems at all.
Try updating your profile on a Sense-based ROM, maybe just nfinitefx45's stock. Could be that the market no longer recognizes your data profile associated with your account because of so many recent changes. Settings->About phone->System updates->Update profile
Not saying this will definitely fix your issue but it is a good thing to try. If it works, you could probably re-flash the ROM of your choice after you do this and still be fine.
Click to expand...
Click to collapse
Hey I did try that earlier today because from past experience flashing a sense rom fixed some issues.
I updated the prl today to ..669 and did all the updates possible on the about menu. Nothing worked.
Thank you for the suggestion though.
I never thought i'd miss the market so much haha
What I don't understand is why it works fine in cm6 and not in darch or stock....
by the looks of it though, http://www.google.com/support/forum/p/Android+Market/label?lid=7dc8a5c590cd22ee&hl=en
it's not just me..
my market was working earlier in the morning, don't know what could've changed..

I had this issue too just now, I had to change to wifi to get downloads going. I don't know why; I hope it's temporary

I ended up going with cm6
figured I might as well
Sent from my HERO200 using XDA App

Anyone got Words With Friends for Android 1.6 before they removed it?

My girlfriend has the G1 with stock 1.6 and I believe the makers of Words With Friends (Zynga) removed the app from 1.6 compatibility - it now requires 2.1 and above. She therefore can no longer download it from the Market.
This is a free app so there is no copyright or piracy issue here. I did find an APK via Google, but it has strange bugs (not the usual bugs with this app) such as she ends up in a game where it is me vs. me, but not her. Have tried all manner of uninstalls, reinstalls, and new WWF accounts. Must be because it is not designed for 1.6 any more.
Does anyone have access to the last well-behaved APK for Android 1.6? It used to work perfectly fine for her.

Hmm, why not just upgrade her G1 to the current version of ROM? Then she won't have that problem. Just curious.

Thanks. Unless I'm mistaken, 1.6 was the last official release for the G1 from Google, no?
I did upgrade another G1 to the Cyanogen version of Froyo, but it always ran slow, got worse, and the user ended up getting rid of it due to this, so I am cautious.
In short, is there a simple ROM that will bring her up to 2.1 on the G1, without slowing the phone down any more than it currently does?
Preferably a ROM I can just download and install via the update.zip method, without all the rooting and hacking. Thanks!

Yes, 1.6 is the official release by google. If you are expecting them to release the next one that will include 2.x, you might not even see it.
Even with 1.6 it's still slow (IMO). And you can't load any other apps on because most of the apps now a day required 2.x and above to work.
Since you asked, I recommend SuperAosp, and it's currently has 2.3 on it. I have been using it since March and loving it. Default load already is fast. With radio 2708/SPL 13d and the 15MB-boot from the DEV. You can also tweak it more for better performance, etc...
As far as not rooting, to my knowledge that's probably impossible. You will required to root in order to load any ROM.

Thanks! Is there any simple step-by-step guide to install it, using a Mac? I can mount the SD card on the Mac so simple file operations are fine.
I'm not sure where to get the appropriate Radio zip for example.
Thanks!

I actually took the plunge and installed the recommended SuperAosp from stock 1.6, and Words with Friends wont let me log in. I tried WWF 3.34 and 3.20 and both of them let you put email in and then it asks for new user name. You put it in and it goes back to the email. I've tried multiple emails and user names & it just goes right back. So if anyone is using a rom that works with WWF would love to know.

I ended up installing ezterry's Froyo and it works great! Make sure you wipe all data and caches first.

whysonosey said:
I actually took the plunge and installed the recommended SuperAosp from stock 1.6, and Words with Friends wont let me log in. I tried WWF 3.34 and 3.20 and both of them let you put email in and then it asks for new user name. You put it in and it goes back to the email. I've tried multiple emails and user names & it just goes right back. So if anyone is using a rom that works with WWF would love to know.
Click to expand...
Click to collapse
Oops sorry, I don't know how I missed this. It should work. I am using it. It's because your user name is taken. I ran into that problem before. I am currently using it with SuperAosp 6.4.2.
My problem is now in some of the game. the letter that was played will not show up from my opponent. It will not display correctly.

Phone can call out, but can not call in

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