Hi all,
A week ago I bought a brand new Desire S and installed latest CM 7.1 stable following the guide on cyanogemod Desire S Wiki using revolutionary 0.4pre4. Everything was smooth and nice, I flashed ROM and GAPPS and my phone is working absolutely perfectly... but there is one little problem...
I am using Desire to fetch my mails from 2 mailservers using IMAP every 30 mins. But when the phone is switching between network modes i.e. HSDPA -> EDGE or EDGE -> GSM or any other way, I am disconnected from operator network for about 10 seconds until the network mode changes and everything is fine after that, until there is another network mode switch.
This happens for me about 10 times a day, so my phone sometimes appears that It is turned off for people who want to call me. Immediately after connecting to network I get a missed call SMS from my operator.
Interesting thing is, that when I disable email fetching, disable background data transfer and disable network data, the phone works fine without "blackouts".
Can someone help me with this problem? Maybe a radio issue?
Some more info:
ROM: Cyanogenmod 7.1.0 Desire S
Recovery: Revolutionary CWM v4.0.1.4
HBOOT: 6.98.1002
Kernel: 2.6.35.14-cyanogenmod+ [email protected] #1
Radio: 20.28I.30.085AU_3805.06.02.03_M
There is a newer radio-file online.
Maybe it's solving your problem.
I'm using MIUI and never had such problems, but i'm interested in flashing CM, so please report if the problem is gone by flashing newer radio!
Which radio version are you using?
Today I am testing 2G only switch so I am on EDGE data only.
Flashing radios is safe......, but a bad radio flash will instantly brick your phone.
You are using 1.47.401.4 radio, try updating to the 2.10.401.5 one.
Thanks for reply.
Shoud I flash something else with the radio?
I have 20.4801.30.0822U_3822.10.08.04 downloaded from cmw.22aaf3.com
Another I have is ftom OTA update zip file OTA_Saga_S_HTC_Europe_2.10.401.8-1.47.401.4_release_225210fmxlt12djw1sr7y5.zip where is one radio.img in formware.zip file too - version unknown
So Which one to flash?
and if so, which method should I use to flash radio? The Android SDK one or the ZIP + Bootloader one?
MyroLM said:
Shoud I flash something else with the radio?
Click to expand...
Click to collapse
no need
MyroLM said:
I have 20.4801.30.0822U_3822.10.08.04 downloaded from cmw.22aaf3.com
Click to expand...
Click to collapse
this file is what ur looking for! check md5-checksum before flashing!
MyroLM said:
and if so, which method should I use to flash radio? The Android SDK one or the ZIP + Bootloader one?
Click to expand...
Click to collapse
Both will work, i'm using method by using bootloader normaly
Strangely I had the same issues as you on Endymion.
Then I updated radio to the latest.
It worked well.
Then I went to CM7. It was fine for a while, but now I'm losing signal with no 3G bars and its not switching automatically to 2G like it should when It has no 3G signal!
EDIT:
After really reading your post, I realise my issue is no way like yours! Yours seems really bad. Update your radio.
-------------------------------
Sent from my HTC Desire S
So, here we go with the results
I flashed 20.4801.30.0822U_3822.10.08.04, md5sum checked OK, update sucess, but phone with no signal...
I flashed 20.48.30.0822U_3822.09.08.20, md5sum checked OK, update sucess, but phone with no signal again...
I flashed 20.28I.30.085AU_3805.06.02.03 back, md5sum checked OK, update sucess, but phone with no signal again...
... what now ... ?
After each flash wiped cache and Dalvik...
in your telephone-info there is shown the new radio after every flash?
do you have removed the batterycover, because there is integrated the antenna of your device!
mouzzza said:
in your telephone-info there is shown the new radio after every flash?
Click to expand...
Click to collapse
Yes, correct number every time.
mouzzza said:
do you have removed the batterycover, because there is integrated the antenna of your device!
Click to expand...
Click to collapse
No, the cover is at its place where it should be. Somehow I did the trick and I am back online with 20.28I.30.085AU_3805.06.02.03 on 2G only for now.
I read somwhere in the forum that ENG HBOOT is required for new radios... Are you sure I dont need to flash eng hboot it before new radio ??
MyroLM said:
Somehow I did the trick and I am back online with 20.28I.30.085AU_3805.06.02.03 on 2G only for now
Click to expand...
Click to collapse
in your area 3g is actually available?
may it helps to go outside, to find your net for the first time!
did you set an accesspoint for 3g?
may you have to set automatic settings, rather than 3g/2g-only?!
MyroLM said:
I read somwhere in the forum that ENG HBOOT is required for new radios... Are you sure I dont need to flash eng hboot it before new radio ??
Click to expand...
Click to collapse
using same hboot as you, never had problems on flashing radio-files!
yes, in my area there is 3g, when I turn off 2g only switch there is a problem described in my first post, so i am on 2g for now just to keep phone connected to network.
main problem is when i am driving and the phone is switching network modes.
so I give 20.4801.30.0822U_3822.10.08.04 today another chance, try to flash if again.
but i am woried about stucking on HTC logo after flash :-( and brick it.
MyroLM said:
but i am woried about stucking on HTC logo after flash :-( and brick it.
Click to expand...
Click to collapse
i already had the problem for several times, and i also pulled out the battery (you shouldn't do that)!
only had to boot into bootloader, start recovery, wipe all partitions, flash rom and was having fun again with my device
this thread could help you, if really stuck on HTC logo
For your real problem on loosing the signal, did you ever tried out using actual stock rom, or another custom one like MIUI?
i used MIUI from 2010-08 till yesterday, now trying out CM7.1 for some days
I have the same or a very similar problem. I have the stock rom.
I already had 3 different desire s motherboard's and 2 different display's.
The first Desire S i had, with android 2.3.3, had a excellent signal. Due some problems i had, the phone bricked and had to go to HTC to repair.
HTC replaced the motherboard and update the version of the android to 2.3.5 and ever since the signal caption, the signal switch was working very bad.
The phone went to a second repair because of this, new phone, and again with android 2.3.5. The problems persisted.
I also tested with different SIM cards, from different mobile operators.
So, my conclusion is either android 2.3.5 or this new versions of Desire S have problems with signal caption and signal switch.
So as you, i need some help with this issue!
mouzzza said:
i already had the problem for several times, and i also pulled out the battery (you shouldn't do that)!
only had to boot into bootloader, start recovery, wipe all partitions, flash rom and was having fun again with my device
this thread could help you, if really stuck on HTC logo
For your real problem on loosing the signal, did you ever tried out using actual stock rom, or another custom one like MIUI?
i used MIUI from 2010-08 till yesterday, now trying out CM7.1 for some days
Click to expand...
Click to collapse
But when I reboot to recovery it will flash the radio again I think.
i hate stock roms, and dont like MIUI design That is why I am using Cyanogen
Anyway if I use 2G only switch, the phone is stable as rock both calls and data transfer.
EDIT: OK, flashed 20.4801.30.0822U_3822.10.08.04 sucessfully, signal OK, I will see what happens whet metwork mode switches
@Green Hawk:
give us more information about your device please, which radio you're using? Did they flash actual radion also?
@MyroLM:
report if the problem is still there or it's gone with flashing the rom
I am still testing new radio, but looks good Give me some days let you know...
Hi All,
I have a similar problem with the latest CM7.1 nightly builds (Reaper, jorgen2009). I never saw this with older CM7.1 versions, e.g. Nexx version, ICS, MIUI oder Endymion.
I have WLAN on and leave my house. Phone switches to 2G/3G..., so far so good. When I return home, The WLan sign in the status bar appears again, everything seems to be fine, but I have no connection. I get no data via WLan until I swicth WLan off and on again.
Radio is the latest from 2.10.401.5.
Best Regards
Wrapp
Had similar problems, upgrading to the latest radio helped. I got stuck on the HTC screen and I went through flashing RUU's and unlocking bootloaders back and forth... when the only thing that needs to be done is to wipe the cache.
Learned a lot about bootloaders though. But my warranty got void because i did the htcdev unlock... (Sorry for OT)
I've tried just about everything to flash a new version of the radio firmware on my 9020a. I've used the Radio Flashing Guide and tried every version available for the 9020a. Each time, the flash reports that it was successful, but no matter which one I choose, baseband still shows I'm running i9020aucke1 when I boot it back up.
I've also flashed the stock ICS OTA update 4.04 for the 9020a, thinking "well, THAT has to do it." but still I'm stuck on cke1.
Are there permissions that may be wrong? Is there anything else I can do? I want to flash a new radio because e1 is terrible for me. It won't switch between "3g" to "H" and just spins it's wheels and I get no data. Sometimes I get ZERO signal. If I reboot or switch Airplane Mode on & off, data comes back and works for a while, but then reverts back to working like crap.
Thanks a lot.
Update
I was trying to flash via Clockworkmod. I used ADB FASTBOOT and the radio is now on J1.
So, if Clockworkmod isn't working, use ADB FASTBOOT.
metalgeek said:
I've tried just about everything to flash a new version of the radio firmware on my 9020a. I've used the Radio Flashing Guide and tried every version available for the 9020a. Each time, the flash reports that it was successful, but no matter which one I choose, baseband still shows I'm running i9020aucke1 when I boot it back up.
I've also flashed the stock ICS OTA update 4.04 for the 9020a, thinking "well, THAT has to do it." but still I'm stuck on cke1.
Are there permissions that may be wrong? Is there anything else I can do? I want to flash a new radio because e1 is terrible for me. It won't switch between "3g" to "H" and just spins it's wheels and I get no data. Sometimes I get ZERO signal. If I reboot or switch Airplane Mode on & off, data comes back and works for a while, but then reverts back to working like crap.
Thanks a lot.
Click to expand...
Click to collapse
What recovery and what version are you using?
I'm loving the Slim-NS-4.2.1.Beta.2-OFFICIAL (JOP40D) with all AIO_Addons as everything runs beautifully. Only problem is that with this configuration, using TWRP 2.3.3, my baseband has been changed to I9020AUCLH1 whereas my Nexus S model number is GT-9020T.
Is there any way for me to stay on my current ROM but modify the baseband so that I can restore my 3g data service? Right now, I can make calls (and even get Edge service for five minutes every once in awhile) but I cannot get consistently registered for 3g data.
If I have diagnosed my problem correctly, the problem either lies with the baseband version or the kernel as this is likely setup for AT&T. I'm happy to customize either the baseband, kernel, or radio but I just need some direction on how to do so without flashing another ROM, unless of course it is also 4.2.1 (I know how to go back to stock ROM just fine).
I have tried modifying the APN settings but to no avail: http://forum.xda-developers.com/showthread.php?t=1675006
Kernel version:
3.0.57-bedalus-g0bba1b5-dirty
[email protected] #1
Sat Jan 5 00:48:36 CET 2013
I also know that the next version of the [ROM][4.2.1]Slim Bean (Crespo) [RC1] was released yesterday but there is no information in the change log that leads me to believe that would make a difference; if someone could confirm otherwise that would be awesome.
Thanks everyone!
MCinNYC said:
I'm loving the Slim-NS-4.2.1.Beta.2-OFFICIAL (JOP40D) with all AIO_Addons as everything runs beautifully. Only problem is that with this configuration, using TWRP 2.3.3, my baseband has been changed to I9020AUCLH1 whereas my Nexus S model number is GT-9020T.
Click to expand...
Click to collapse
i'v never installed the add-ons but slim does not change your radio
i'd reflash a tmo radio first...
fwiw
FIXED after flashing radio
louderstill said:
i'v never installed the add-ons but slim does not change your radio
i'd reflash a tmo radio first...
fwiw
Click to expand...
Click to collapse
Worked as expected!
Steps
1. Came across this ADB statement to flash radio 'fastboot flash radio radio-crespo-i9020xxki1.img'
2. Found GT-I9020T radio-crespo.i9020xxki1.img file here: http://forum.xda-developers.com/showthread.php?p=24217600
3. ADB: adb reboot bootloader
4. ADB: fastboot devices
5. ADB: fastboot flash radio D:\XYZ\radio-crespo-i9020xxki1.img
3G data service is back!
is there anyone who has tried all these roms?
I need some recommendations cant figure out which one is stable and bugs in each build..
This will help lot of ppl in choosing the right rom for their use!
Flinny CM11 Alpha 3 (dalvik)
I am using Flinny's CM11 Alpha 3 all the time for daily use and it is working very smooth and without any problems !
Some people have ring tone problems but there is a fix (audio_policy.default.so) !
Battery time is same as with CM 10, perhaps even better.
I tried all 3.But all have same FC com.android.phone on registering network. Found that this happens only when switching from 3G to 2G.In 3G was working great but I restored 10.2.
Also tried but have problems with android.media.process has stopped keeps repeating... otherwise seems to look promising. No phone process FC for me...
Last time I tried any AOSP ROM with kernel >3.0.16 my battery ran out noticably faster (16 hours as opposed to 2 days) than on a Sense ROM.
Flinny's build 10.2 is quite fine with the battery drain... not as good as sense rom but given the upside in system as such I think it's worth trying (for me over one day)...
I'm using devil-kin cm10.2 and it's working great.About CM11 from what I see everyone with HBOOT 7.00.1002 and radio 20.76.30.0835U_3831.19.00.110 don't have problem with FC com.android.phone.My phone is S-ON so I can't try to change hboot and radio.Can't get old RUU on my phone back to do revolutionary S-OFF bc my hboot is 2.00.0002 .
I have that combination of hboot and radio, and I don't have any fc on cm11. It seems to be more region /carrier specific though.
Btw, you can use misc_version to change the reported software version on your phone, then you can flash an older RUU.
Edit: or do you mean you can't get the correct ruu anywhere? Maybe I misunderstood
I downgraded my hboot by installing RUU_Saga_HTC_Europe_1.47.401.4_Radio_20.28I.30.085AU_3805.06.02.03_M_release_199410_signed and revolutionary S-OFF.Flashed recorvery 4ext touch 1.0.0.6 RC1 and flashed Unofficial "Nightly" CM11.0 [20140228] by devil-kin and everything works.No FC com.android.phone.I can select 2G or 3G without problem.I will try tomorrow to change hboot to 7.00.1002 and radio to 20.76.30.0835U_3831.19.00.110 but for now CM11 works without problems.
So now question is who make FC com.android.phone HBOOT or radio.I vote for radio.
Update: After reboot got FC com.android.phone.Switched to 3G and reboot and works good.Tomorrow will try new hboot and radio.
Flashed hboot to 7.00.1002 and radio to 20.76.30.0835U_3831.19.00.110 and restored CM11 by devil-kin.Everything goes without problems but then I found 1 new and 1 old error :
1. new one: in got 3G and 2G when I call my number voicemail answer telling I'm unavailable and when I hangup msg come in next 10 sec that I have voicemail from that number that called.Second call goes normal and ring.If I wait some time (i waited 10+min) and call again same thing happen.
2.old error: when I switch from 3G to 2G I get new error(1.new one) and if I reboot phone upon registering network get FC com.android.phone.Switching back in 3G is hard ( have to click 5 or more times) but when back it works fine just new error make problem.
I restored 10.2 by devil-kin and all problems gone (new and old).:crying:
So what we can see there hboot and radio didn't do anything with FC com.android.phone and new error Unavailable.
What can be problem? Maybe old simcard (2001 or before I didn't change my number long time (maybe I really need new simcard)) or something with CM11 on Desire S.
My new vote is old simcard.Very old
(reason for my vote: what you can read above and information that just some phones are affected with FC com.android.phone).
Sorry for bad english.
It's definitely not the simcard i have 12 year old, latest hboot, radio, and only time when i got com.android.phone was when i forgot to flash boot.img after changing rom from devil-kin CM11 to Flinny's
After a tragedy with my S3, I'm having to limp along with my old One SV. Unfortunately I am having trouble getting this thing to keep a newer ROM. And before anyone says "turn s-off" I have S-Off already.
Booting to the boot menu it says:
moonshine S-OFF
K2_CL PVT SHIP S-OFF RL
CID-SPCS_003
HBOOT-1.01.4444
RADIO-1.1250.0516
OpenDSP-v9.2.0268.1214
eMMC-boot
Jan 16 2013, 01:26:39:-1
I've tried jellybean flashing
I tried the viper ROM (which gets stuck flashing unless I don't install all the google apps)
Post every flash, I turn the phone off and then power it back up. For a little while it'll say something "correctly" like that it's android 4.4.... buuuuut it is still the default wallpaper and goes back to saying android 4.0 and of course the bugging to update to a new stock android is still present as is the "out of storage space" error message....
I've tried updating the recovery (currently a somewhat buggy cwm where the screen is 1/8th offset half the time... v6.0.2.8) and that hasn't worked... Typing this out I decided to try flashing the recovery once more since when I first was doing it I apparently had S-ON... So I flashed the latest TWRP (3.0.1-0-k2_cl) and..... now it's bricked.... it won't boot normally nor will it boot into recovery mode, but I can get to the hboot menu.... HALP! lol
The final kicker to my scenario is that I'm on linux and don't have access to any Windows machines, but I do have heimdall and adb installed.
Okay... So because I was still able to get into the HBoot menu and then put it into the Fastboot menu with the USB cable connected I was able to flash a new recovery.
I got the TWRP 2.8.5.0 recovery from http://techerrata.com/browse/twrp2/k2_cl
I was able to install fastboot and adb thanks to http://forum.xda-developers.com/showthread.php?t=2638673
I re-tried flashing the Jelly Bean rom I had with the same result as before the bad recovery problem occurred... It boots up, but it's still Android 4.1, even though it is S-OFF-ed.... And that shouldn't be happening... I'm pulling the battery and rebooting after flashing so nothing should be overwritten... What gives?
Your best way to go:
http://dl3.htc.com/application/RUU_...V_NV_Boost_2.20_150_release_389346_signed.exe
As far as i remeber, there was no custom rom that was made for k2cl.
correct.. there is no custom rom for the boost variant.. there is a partition swapper changing the 4gb media with the 1gb internal storages.. romcleaner works to get rid of all the boost garbage.. twrp will fit your screen.. havent used cwm since my hero
The Viper rom claims it covers all variants. And somewhere along the way I downloaded two Boost based roms aside from that.
I tried to get the RUU to work, but couldn't. I borrowed a friend's Windows laptop, installed adb and fastboot and it just would not connect or see my phone in the RUU. I even tried forcing the driver to be installed correctly, which never worked for some reason.
I ended up installing Link2SD and setting up a 16gb partition for apps. So at least it's not complaining about being out of space anymore. It is still wanting me to download the OTA update. Not the end of the world.
I do have a new issue though. For some reason the "wiper" app keeps crashing. Not sure what it is or where to find it. I suspect it's named differently and I either need to flush it or install an uncorrupted copy. Any suggestions?
Hathalud said:
The Viper rom claims it covers all variants. And somewhere along the way I downloaded two Boost based roms aside from that.
Click to expand...
Click to collapse
Hm,
From the Viper Rom thread:
Modding.MyMind said:
THE VIPERSV ROM IS NOT FOR BOOST MOBILE (K2_CL) USERS!!!!!!!!
This is what could happen to you if you fail to follow instructions!
Click to expand...
Click to collapse
xpirt said:
This Rom is not compatible with Boost/Cricket variants, which model have you flashed it on?
xpirt
Click to expand...
Click to collapse
Hathalud said:
I do have a new issue though. For some reason the "wiper" app keeps crashing. Not sure what it is or where to find it. I suspect it's named differently and I either need to flush it or install an uncorrupted copy. Any suggestions?
Click to expand...
Click to collapse
This was a permission bug from updater script, when i remember.
Wiper is some wifi or network location service. If you don't need it, rename it or delete it.