Database Info

ROM issue

I tried installing BAMF 3.0 RC2 on my phone, and I can't seem to get it working properly. Upon startup it force closes a bunch of things and the radio shows no signal at all. I have ran the MD5 on the download to ensure integrity. Also did a complete wipe prior to flashing. Could this be a radio problem? I haven't done any radio upgrades.

STEyeAndroid said:
I tried installing BAMF 3.0 RC2 on my phone, and I can't seem to get it working properly. Upon startup it force closes a bunch of things and the radio shows no signal at all. I have ran the MD5 on the download to ensure integrity. Also did a complete wipe prior to flashing. Could this be a radio problem? I haven't done any radio upgrades.
Click to expand...
Click to collapse
You need a gingerbread radio for a gingerbread rom.. so MR2 or MR2.5
Sent from my ThunderBolt using XDA Premium App

i have the same problem and ive been trying to flash both radios its acting like its doing it in hboot but everything still is the same and no mobile network for me. can someone please tell me a way to get it working how do i check my md5 of my rom and stuff

poloboogie said:
i have the same problem and ive been trying to flash both radios its acting like its doing it in hboot but everything still is the same and no mobile network for me. can someone please tell me a way to get it working how do i check my md5 of my rom and stuff
Click to expand...
Click to collapse
when you say everything is the same, do you mean it still has the previous radio version number?

I'd suggest that you both:
1) Wipe data/dalvik/cache and flash back to a froyo ROM where you do have a signal
2) Upgrade from froyo to the MR2/2.5 radio
3) Re-wipe data/dalvik/cache (or even do it twice for good luck ) and re-flash BAMF 3.0
If its worth doing, its worth overdoing, especially when you're messing with radios and the like. Best of luck!

That's the same problem I first had with gingeritis before flashing the correct radio.. if you are still experiencing the problems after the radio flash i would suggest confirming the radio did install by checking the version number..
if it is all correct do as MattBeyers said and wipe and reflash

Thanks, that seemed to work. I still got a couple of force closes but much less than before. Also I can see my radio now! If I wanted to restore my old my Backup (Stock Froyo - MR1), do I restore my backup then flash MR1? If so, does anyone have a link the MR1 image? TIA!

I'm always one to upgrade/downgrade radios before I flash a ROM, so I would say to downgrade to MR1 and then flash the Froyo backup. Also, try going into ROM manager and using the Fix Permissions tool to see if that helps with some of the force closes.
Sent from my Mecha using XDA Premium App

MattBeyers said:
I'm always one to upgrade/downgrade radios before I flash a ROM, so I would say to downgrade to MR1 and then flash the Froyo backup. Also, try going into ROM manager and using the Fix Permissions tool to see if that helps with some of the force closes.
Sent from my Mecha using XDA Premium App
Click to expand...
Click to collapse
Any reason for flashing one before the other? Reading through several of the ROM threads, it seems like everyone has a preference, but no one explains why.

I tried mr2 and mr2.5 but could only get 3g. Went back to CM7.
Sent from my ThunderBolt using XDA Premium App

Mr_Joshua said:
Any reason for flashing one before the other? Reading through several of the ROM threads, it seems like everyone has a preference, but no one explains why.
Click to expand...
Click to collapse
I just feel like the radio, being the thing that, well, controls every useful function on the phone, should be installed and present when a new ROM is flashed. I may be wrong, but it would seem logical to me that a new ROM would talk to the radio in order to make sure everything is kosher. But what if that's something that a ROM will only do once, at the first boot, and not once a new radio is flashed? Then, all of a sudden, you have the right radio, but its configured improperly by your ROM, since the ROM has already gone through its initial boot set up with the old radio. Therefore, my theory is radio > ROM (Please note, theory. )

Make sure u have a gb radio mr2 or mr2.5

MattBeyers said:
I just feel like the radio, being the thing that, well, controls every useful function on the phone, should be installed and present when a new ROM is flashed. I may be wrong, but it would seem logical to me that a new ROM would talk to the radio in order to make sure everything is kosher. But what if that's something that a ROM will only do once, at the first boot, and not once a new radio is flashed? Then, all of a sudden, you have the right radio, but its configured improperly by your ROM, since the ROM has already gone through its initial boot set up with the old radio. Therefore, my theory is radio > ROM (Please note, theory. )
Click to expand...
Click to collapse
This makes sense from a logical reason. Perhaps a ROM developer on this site can confirm this.

[Q] Desire S loosing signal

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)

Is there a solution for the WiFi issue?

It's been some time since I posted the problem. I searched around and didn't find any new information, so I am just hoping I missed something, like a possible thread that has a fix.
I have no WiFi, have gone through the book trying to fix it, to no avail. HOWEVER, I left the phone un used for about a month, battery had died long ago. A few days ago, I grabbed and and just decided to give it another shot and install revolution hd on it. For whatever reason, it installed successfully and the WiFi was working perfectly. So I updated the 4ext and had notice that a new version of HD had come out, so I decided to update it, and well, back to square 0, WiFi no longer works. So I tried to back pedal and repeated the steps leading up to the WiFi working, Super Wipe with smart flash enable, reboot, installed HD with no smart flash. But this time it did not work. Strange that it worked before though, I wonder if it being out of battery for so long had something to do with it.

did you try to flash the boot.img of your rom?
also if you are S-ON when flashing a rom always enable smartflash

rzr86 said:
did you try to flash the boot.img of your rom?
also if you are S-ON when flashing a rom always enable smartflash
Click to expand...
Click to collapse
What he said.. if you're s-on always flash with smartflash
Sent from my HTC Sensation 4G

I too had the wifi issues for quite some time. After updating my kernel it got fixed.
Probably you could do the following:
1. If your HBOOT is S-ON, make sure you follow the above two posts while flashing ROM
2. Ensure that the latest firmware is being used.
2. Try changing the kernel (mine is faux 009b4 now).

I am S-OFF, like I said, I've tried everything.
Just seem odd that out of nowhere it flashed correctly, I should of just left it at that, maybe if I leave the battery inside the phone drained for a while I can repeat the successful flash.

F9zSlavik said:
I am S-OFF, like I said, I've tried everything.
Just seem odd that out of nowhere it flashed correctly, I should of just left it at that, maybe if I leave the battery inside the phone drained for a while I can repeat the successful flash.
Click to expand...
Click to collapse
well don't know if you have tried this but the last thing I can think of is to go back to stock ruu, if it still doesn't work it might be hardware related
Sent from my HTC Sensation 4G

I faced with same issue. I use ARHD 6.7.1 and i have no problems with wi-fi , but when I try to install sense 4.0 roms for sensation, I always have wi- fi problem.I live in Almaty and I use Beeline for mobile carrier, My device is Revolutionary S-OFF. I live in Almaty and I use Beeline for mobile carrier, and also I have one sim card for Turkey, AVEA, when I use Beeline wi-fi doesn't work but when I use Avea wi-fi works completely. I tried wifix manager. But I can't find solution :/

Same thing happened to me when I updated, go to tools in 4ext before flashing and enable smart flash, I'm pretty sure this will help
Sent from my HTC Sensation XE with Beats Audio Z715e using xda app-developers app

[Q] Crazy insane inverted touchscreen issue

crazy touchscreen problem
After flashing a ROM my touchscreen x axis seems to have inverted itself, so right is left on the screen.
This problem happens during the recovery screen also
I have tried changing recovery's,Kernals,flashed ROM's that I know work
I have even returned the phone back to stock nothing fixed it.
I have even went as far as removing the motherboard and installing one out of a working phone and guess what it does the same thing.
So i ask all you knowledgeable people WTF wold cause this and how can I fix it ?
these are the last two ROM's I was trying out when all this happened
they both ran without a problem I just didn't like them
MokeeOS 44.2 24/12/2013 [UNOFFICIAL],
UNOFFICIAL AOKP][4.4.2] [S4] [12/26/13]
I'm in no way blaming the ROM developers for this issue I just need a little help

Strange problem. I think you should flash firmware, it is worth to try i guess
Sent from my One S using xda app-developers app

mines actually doing the same, and from what i've been reading, i believe it has to do with your hboot version and ics not being compatible with it. try flashing your original ruu if you can. that's what i'm trying to do as we speak. if i ever get my problem figured out, i'll let you know if it works.

HomieOneKinobi said:
mines actually doing the same, and from what i've been reading, i believe it has to do with your hboot version and ics not being compatible with it. try flashing your original ruu if you can. that's what i'm trying to do as we speak. if i ever get my problem figured out, i'll let you know if it works.
Click to expand...
Click to collapse
This was my test phone I had flashed just about everything you can think of before I would install it on the phone I use every day
I guess my luck ran out
I ended up flashing the phone back to the original firmware and OS version using the factory RUU without a problem
If I try to install anything over 4.04 it goes right back to the same crap
I tried different firmware, kernels, roms with sense/ no sense doesn't matter.
the phone is being sold as I type this and I'm leaving my other two One S phones alone for now on
Nobody should have to go through this much bull for newer OS version so I'm saving for a Nexus 5
Thank you for the suggestion

[Q] Reboots 30 into loading ROM

From the beginning.
Unlocked
EVITA PVT SHIP S-ON RL
HBoot 1.14.002
Radio 0.19as.32.09.11_2
OpenDSP v29.1.0.45.0622
eMMC-boot
June 11 2012, 14:36:28
Click to expand...
Click to collapse
I was running a ViperRom my camera light was staying on, I tried everything to get it to turn off. I decided it been a few month it was time to get a new ROM anyways. I tried installing Gummy Nightly's was having problem with the install read about getting a different version of TWRP so I updated to 2.6.3.0 I believe I had 2.1.0.0. Gummy still won't work, so I changed plans and want for the Viper XL Rom 4.2.0 this led to a bootloop not getting past the Viper splash screen. I thought I might as well just with one of my backup. So, i wiped and loaded a backup. This is the problem, it will load up the ROM for about 30 seconds before the icon all appear it will reboot. I've now been working on this for 2 days. I've went through each post and tried the advice each person was given, I've tried to Flash a different Rom, the Viper Rom I had when I had the Camera Light Issue, each time I get about 30 second into the Rom Load and reboot. (One of the ROMs would let me access the SDCARD0 but found a work around that.) I've let the phone sit charged for 2 hours looping. I've turn it off and let it sit charging. The next thing I'm going to try to to downgrade the TWRP. If anyone can give me some advice, something new and different to try that would be great. Thanks!
Cheers
xDrFirefly

talked to one of my buddy and said the downgrade would be pointless so, i'm trying to flash a stock rom at the moment.

When you changed to TWRP 2.6.3.0 was it the official version or the unofficial modified version?
Sent from my Evita

Recovery: Custom TWRP 2.6.3.0 w/selinux support

And what errors did it give you when trying to install Gummy?
Sent from my Evita

The install failed. I tried it multi times, and even d/l it again to see if that would make a difference. Nope.
Here is what i've done so far. I factory reset everything. Found a stock rom flashed it on. For the two hours I used it seemed to work fine. I then flashed CleanRom everytime I would open Ti Backup the phone would reboot. I flashed another ROM, was getting the signal drop snagged the Beastmode Kernel it keep failing everytime I tried to flash it. Factory Wiped EVERYTHING again. Flashed the Stock, then Flashed ViperXL (then went to bed) in the morning still had signal bars, so far had two reboots, one when I was uninstalling apps using Manage apps feature, and another time when I was in the Venom HUB app. But at the moment the phone seems to be working. The battery life is ****. In the 30 mins I've had the phone unplug i've down to 89% and all I did was delete a few apps, and move some stuff to the home screens. Hopefully it will get better with time.
Side Note: To anyone reading this. I got the AT&T HTC XL preorder. I doubt I will ever do that again. In all the years I've been flashing and messing with phone. ( My first phone I messed with was a Sidekick ) I've never had so much trouble as I had with this phone. ( HTC Tilt, Fuze and Tilt 2 never had this kinda problem ) a friend of mine whom waited a year to get the XL has never had any of the problem I've had. Just my thoughts. Thanks and I hope I won't have to be asking anymore question.
When, I have more time and such I'm going to try to flash Gummy. If I get the same error message for it or anything else I will post it here.
Cheers
-Dr FF

I get that it failed, I asked what error you got. Your battery life on Viper will improve, just let the ROM settle in for a few days. I've had this phone since just after release and I've never had a single problem with it, not one. There are quirks that come with any device but if you do the proper research and know what you're doing you shouldn't have issues.
Sent from my Evita

You might also want to try setting a fresh install up without restoring any apps or installing any social networking apps. Those are possibly the worst for fc's, random reboots, and bad battery life. At least for me that's how it is.

jacobas92 said:
You might also want to try setting a fresh install up without restoring any apps or installing any social networking apps. Those are possibly the worst for fc's, random reboots, and bad battery life. At least for me that's how it is.
Click to expand...
Click to collapse
I will try this. Sounds like a very logical plan.

timmaaa said:
I get that it failed, I asked what error you got. Your battery life on Viper will improve, just let the ROM settle in for a few days. I've had this phone since just after release and I've never had a single problem with it, not one. There are quirks that come with any device but if you do the proper research and know what you're doing you shouldn't have issues.
Sent from my Evita
Click to expand...
Click to collapse
Timmaaa I just get annoyed how easy this phone get caught in bootloops. That is really my main complaint. I know it's trivial. -- I really don't know what caused the fail when I tried to install Gummy. I wiped and tried it a few time and I keep getting failed. I normally try twice then find something else. To quote Little Britain "Computer says no".

xdrfirefly said:
Timmaaa I just get annoyed how easy this phone get caught in bootloops. That is really my main complaint. I know it's trivial. -- I really don't know what caused the fail when I tried to install Gummy. I wiped and tried it a few time and I keep getting failed. I normally try twice then find something else. To quote Little Britain "Computer says no".
Click to expand...
Click to collapse
Computer always says no for a reason. You need the right recovery installed to flash KitKat ROMs, you also need to check the md5 of every ROM you download before you flash it. What I'm saying is there's no reason Gummy wouldn't install if you have done everything correctly.