"SIM Failure" error after signal loss in WM6 ROM - HTC Tornado

I have a T-Mobile SDA. I recently flashed my SDA to vj's 3.5 revision.
My office is in a basement (No, not my parent's. I do have a job). Because of this, I have always had issues with signal loss. With other ROMS (T-mobile stock, qtek AKU2, custom WM5, WM6 PEE, phils WM6 beta), I would inevitably lose signal at some part of the day and the phone would go into constant "searching" mode. Normally, when I went upstairs, the phone would reattach after a few minutes. Occasionally , I would have to reboot the phone.
With vj's 3.5 ROM, when I lose signal, I get a "SIM Failure" error as soon as the phone goes into "searching" mode and I have to pull the battery in order to reset the phone.
I went back to the qtek WM5 AKU2 ROM and everything worked OK. However, as soon as I upgrade back to the new ROM, the problem reappears.
A couple of thoughts (and I may be wayyyyy off base)...
1) This is the first ROM I have seen that had the STK Service listed (Sim ToolKit). Was it was just hidden on the other ROMS, or is it a new addition? If this is new, is it possible that the service is causing a conflict of some sort?
2) The default provider list under "Start/Settings/Phone/Networks/Preferred Networks" is MUCH shorter than in previous ROMS. Is this a possible issue? (i.e. my SIM is not identified on the closest tower). How do you identify which provider entries to add?
Please note that I am not picking on vj, as I love almost everything else about the ROM.
Has anyone else had a similar issue?
Thanks.
dc

Can't say I've seen this error - and I'm using a T-Mobile SDA also. Though I have v3.6 ROM installed (but I never saw this with v3.4 either). Granted I've not been in a situation where my phone lost connection with a tower.
Did you also update the radio firmware when you jumped to WM6? It may be worth checking what you have with the latest ones available (best way is to check Nitrogenious' signature).
Good luck.

bipinsen said:
Can't say I've seen this error - and I'm using a T-Mobile SDA also. Though I have v3.6 ROM installed (but I never saw this with v3.4 either). Granted I've not been in a situation where my phone lost connection with a tower.
Did you also update the radio firmware when you jumped to WM6? It may be worth checking what you have with the latest ones available (best way is to check Nitrogenious' signature).
Good luck.
Click to expand...
Click to collapse
I have:
IPL: 2.00
SPL: 2.00.0008
Radio: 4.1.13.28_02.61.01

dmcaylor said:
I have:
IPL: 2.00
SPL: 2.00.0008
Radio: 4.1.13.28_02.61.01
Click to expand...
Click to collapse
Hello dmcaylor,
I have lost signal a few times with this ROM (v3.6 and also v3.5) in a location where there was no service and it maintained the searching mode (without going into sim failure) and returned without problems at all. BTW it is great you have upgraded the radio, but the following is just a suggestion and I don't know if you have performed it before flashing this version...make sure before you install this ROM or flash any ROM for that matter you perform a "format BINFS" following this guide.
The reason why I encourage this is that if I don't perform a "format BINFS" and flash a ROM, weird and quirky things have a tendency to happen, and when the "format BINFS" is done these things "magically disappear". This has been evident over the last month when I have started to "religiously" perform this procedure before every flashing (and believe me I have done this several times with all the testing for these versions) and the "quirky" nature has disappeared. I believe it is attributed to erasing/eliminating the pre-existing ROM files thus reducing the chance of conflict from prior ROM files.
I hope that helps.
Take care!!

Thanks vj. I formatted before flashing as advised.
I think I found the problem. If either "GPRS AutoDisable" or "GPRS AutoEnable" are set to On, I get the SIM error. After turning off those options, the issue goes away. I still lose signal, but I do not get SIM-locked out of the phone.
vjgrace said:
Hello dmcaylor,
I have lost signal a few times with this ROM (v3.6 and also v3.5) in a location where there was no service and it maintained the searching mode (without going into sim failure) and returned without problems at all. BTW it is great you have upgraded the radio, but the following is just a suggestion and I don't know if you have performed it before flashing this version...make sure before you install this ROM or flash any ROM for that matter you perform a "format BINFS" following this guide.
The reason why I encourage this is that if I don't perform a "format BINFS" and flash a ROM, weird and quirky things have a tendency to happen, and when the "format BINFS" is done these things "magically disappear". This has been evident over the last month when I have started to "religiously" perform this procedure before every flashing (and believe me I have done this several times with all the testing for these versions) and the "quirky" nature has disappeared. I believe it is attributed to erasing/eliminating the pre-existing ROM files thus reducing the chance of conflict from prior ROM files.
I hope that helps.
Take care!!
Click to expand...
Click to collapse

Related

No ROM usable ??, hang on Opera9 customization process

I would need some help to understand the following :
whatever ROM i try to install, after successfull flash and the following reboot when you get the "customization will start in 3 sec", it always hang on the "Installing WM6_PPC_HTC_Opera9_WWE.CAB" (last time i wait 5h to see if it move)
i tried RomeOS1.01 as well as 1.02 (just a few minutes ago), same also happen with DCS-TouchProv13 or even when i try to revert to RUU_raphaelWWE1.66...
i have a successfull HardSPL1.90.1.3 Olinex properly showing up on the 3 color screen.
Soft reset allow me to use the phone with a somehow successfull install ? (i get some of the appz but not sure it is 100% successfull / how can i check??)
Only concern is that the phone get warm around the camera/speaker after a few hours of usage and battery doesnt sound very powerfull (full load stay on about 5 to 6h with no bluetooth but wifi on)
original is an XDA diamond pro from o2 germany (model RAPH120)
as of right now i have
ROM: ROMeOSv1.02 WWE
Radio: 1.02.25.11
Protocol 52.33.25.17u
Any idea why the custom... always hang on the Opera install ? i dont care to not use opera or dl and install it myself afterward ??
thks
Stephane
(frenchy leaving in Germany and working for a US company.... cannot afford to use a DE phone only )
How about flash ur stock ROM back, then revert the stock SPL. There may be semething wrong with ur device
GERMAN ROM
http://forum.xda-developers.com/showthread.php?t=426400
German ROM work fine
Guess what .... after flashing back to a german ROM (thks for the link to an htc oiginal ) the "customization" with Opera9_DE went well and finish up normally.
i am going to work/play a bit with the German version to make sure it does not come from the device
any other idea in how/why my German o2 xda does not love all the great simple ROM cooked here ??
is any o2 Germany user here havig successfully flashed their xda with an English (or French ) ROM ??
Thanks guys for the great work you do here !
Steph.
I am seeing this exact same issue.
I have had no end of grief flashing my Raph, I maintain an XP VM (I am on OS X) entirely for flashing. I have flashed many different devices with dozens of ROMs and never had a problem until I got the Raphael. I have seen BSOD's and numerous connection issues while flashing using both Raphael_CustomRUU_v1.2 and RaphaelWrapper.
Also, every ROM I have flashed (on a XP SP3 box I put together from old pieces just to flash this bastard) has hung whilst installing opera.
I am using the o2 uk variant (as yet unreleased XDA Serra).
It is a RAPH120, is this unique to o2 devices?
Would appriciate any help getting this sorted, it could become a more widespread problem with the o2 uk variant is released, as there may be an influx people wondering why their device wont flash properly.
nb. I have an unreleased o2 built ROM (RUU_Raphael_O2_UK_1.60.206.1_radio_sign_52.29.25.12_1.01.25.16_Test.exe) that flashes and installs fine even from inside my VM.
Thanks in advance for any help anyone could provide!
[UPDATE] I tried installing Opera build 1957 from a cab and it worked fine.
maybe a dumb suggestion... but try to get your device unlocked and see what happen
I checked with Oli about whether unlocking would help:
Olipro said:
I see, then that's a weird issue, however, not related or fixable by the unlocker.
your best bet is to do a soft reset as soon as the customization dialog appears and see what happens.
I was initially suspecting it could be region protection, but in those cases, the ROM doesn't boot at all, so your case is a strange one.
Click to expand...
Click to collapse
So no leads there, as an interim solution I will repack ROMeOS² v1.03 without Opera and see how that works out.
i have the same device and the same problem. I will try to repack it with the german version of opera..
Oh dear, so it would appear that current roms do not work on O2 variant devices...
Has anyone successfully flashed an O2 device (with a cooked rom)?
I have hit some problems repacking ROMeOS² as hung has included measures to stop people making their own roms based on his. I pm'd him last night asking if he could help us out, but as of yet I have not recieved a reply.
I will probably start making my own rom from scratch tonight, but its a fair bit of work just to take opera out of the customization sequence. Hopefully its just some odd bug in the opera install, rather than something more serious. I guess worst case scenario is that after opera is removed it just crashes at another point during the costomization process.
[UPDATE]
hang.tuah said:
@dabs
I'll try to make it [ROMeOS² without Opera] for v1.04 mate, thanks for ur support..
Click to expand...
Click to collapse
Excellent, so at least we have a workaround in the pipeline. Still, it would be best to find the cause of the problem, as not all cooks have the time and dedication to make special versions of their roms for a small sub-set of users.
Actually Opera is included but with no device specific & v1.04 is done
smaier said:
I would need some help to understand the following :
whatever ROM i try to install, after successfull flash and the following reboot when you get the "customization will start in 3 sec", it always hang on the "Installing WM6_PPC_HTC_Opera9_WWE.CAB" (last time i wait 5h to see if it move)
i tried RomeOS1.01 as well as 1.02 (just a few minutes ago), same also happen with DCS-TouchProv13 or even when i try to revert to RUU_raphaelWWE1.66...
i have a successfull HardSPL1.90.1.3 Olinex properly showing up on the 3 color screen.
Soft reset allow me to use the phone with a somehow successfull install ? (i get some of the appz but not sure it is 100% successfull / how can i check??)
Only concern is that the phone get warm around the camera/speaker after a few hours of usage and battery doesnt sound very powerfull (full load stay on about 5 to 6h with no bluetooth but wifi on)
original is an XDA diamond pro from o2 germany (model RAPH120)
as of right now i have
ROM: ROMeOSv1.02 WWE
Radio: 1.02.25.11
Protocol 52.33.25.17u
Any idea why the custom... always hang on the Opera install ? i dont care to not use opera or dl and install it myself afterward ??
thks
Stephane
(frenchy leaving in Germany and working for a US company.... cannot afford to use a DE phone only )
Click to expand...
Click to collapse
Hi Stephane and others having similar trouble,
I had the same situation but my original ROM was Japanese, after trying a lot of possible official WWE versions for flashing and cooked ROMs, only one version worked.. Check the official WWE version Singtel.. it worked up to customization without problem.. the only difference the default internet page is Singtel but it is not a problem cause I can still go to the other sites..

Universal No GSM Problem

Hi All,
It had been a long time that i have been trying to solve the 'No GSM' problem.
My device is O2 xda Exec, but strangely it started to show no sim card and then showing No GSM on the boot screen.
I had tried various ROMS by our friends, but no one is able to sort out this problem. Now i am really tired of it.
If anyone can help, knows any method to sort this out, any clues, i will be very happy.
i have the same problem.....
i had flash several rom's, but i cant flash radio rom as i show in this topic
http://forum.xda-developers.com/showthread.php?t=457873
Try flashing back to the original factory ROM pack, it comes with everything in one upgrade package, so it will flash your ROM, Radio and Extended ROM at once. Trying cooked ROMs will not solve it, simply because they don't come with Radio as a general rule, so if you are missing a Radio, flashing a developed ROM will not add one.
Alternatively, of course, it may indicate problems with your main board that simply no longer reads your SIM.
i don't know the original rom version of it.
i had tried 2 original Imate WWE roms and it stucks at 0% at flashing radio rom. i instead it, i flash the rom and extrom separately several times, with severak versions, and the only problem is flashing the radio rom.
the device works properly, except GSM. the wifi and BT turns on and off. (no other devices to have comunicate)
i tried also sim "unlock" (it is already unlocked from factory) and i have the "success" message, then tried to flash radio rom, but unsuccessful.
then i did a rom backup from other device (Orange SPVM500 brand) to sd card and then restore to Jasjam, but shows "error ID"
then, i tried to backup the entire rom from itself to SD and restore it again, but the commands seems to not work.
then a did a upgrade bootloader (because it stucked at bootloader) even using UNI_bootloader EXIT.exe
i have no more ideas, then have it a large hammer!
hi_siddhu said:
.... but strangely it started to show no sim card and then showing No GSM on the boot screen....
Click to expand...
Click to collapse
mine started like that.... and the other one (i have 2), today showed me the same message...
jesuis said:
mine started like that.... and the other one (i have 2), today showed me the same message...
Click to expand...
Click to collapse
SIM is due for replacement?
i tried 2 sim card's from 2 different operators.
actually it is without sim card, but shows the "NO GSM" at start up.
on past Saturday, my other pda (old HTC BLUEANGEL) had a freeze on receiving a call (i must reset it 4 times) then i made a call and nothing happened after that.
very strange.
i tried also backup a rom from the device to sd card and shows me an error (error = FF) on mtty1[1].42
i do the operation successfully on my other htc.
i read that sometimes take out and plug in the batery several times, works...
mine dont.
Try this it worked for me.....
Most of the ROM you update only have the nk.nbf (OS ROM) but don't have ms_.nbf (Extended ROM), radio_.nbf (Radio ROM). so you should upgraded the radio_.nbf manually.. and the problem should me solved..... so simply download any new Radio version in my case 1.17.XX and copy the file radio_.nbf (Radio ROM) in to the ROM update folder . Enter boot screen and update... the problem should be solved.... have a look at following link as welll... might be helpful...
http://wiki.xda-developers.com/index...name=UNI_Radio
I too have the "NO GSM" issue, and have noticed that most cases are associated with the o2 Exec; as is mine. I'm also missing my IMEI in 'device information'. I think the issue may have something to do with the CID lock originally found in the o2 Exec. I too have tried almost anything and have heard the original ROM is the only way back (which I don't have). However, I believe that an SD upload/download of a radio ROM may be a possible solution. The trick is getting the 'header' of the "to be downloaded" radio ROM to match up with the device. This is where I'd left off on trying to fix my device...I don't know how to edit the ROM's header and save, so that I may download via SD card...any help would be much appreciated...
Its a HW problem...
what do you mean by sd upload/download of rom ????
EXEC/JASJAR said:
I too have the "NO GSM" issue, and have noticed that most cases are associated with the o2 Exec; as is mine. I'm also missing my IMEI in 'device information'. I think the issue may have something to do with the CID lock originally found in the o2 Exec. I too have tried almost anything and have heard the original ROM is the only way back (which I don't have). However, I believe that an SD upload/download of a radio ROM may be a possible solution. The trick is getting the 'header' of the "to be downloaded" radio ROM to match up with the device. This is where I'd left off on trying to fix my device...I don't know how to edit the ROM's header and save, so that I may download via SD card...any help would be much appreciated...
Click to expand...
Click to collapse
what do you mean by sd upload and download of rom ??????
can you be explain in more detail.....
Cheers
rajiv
You can find more information in the forum adout downloading by SD card. Tomal has an SD ROM tool; or you could try the service manual...Either way, I cannot seem to get an SD download to work because of a fixed CID lock; this was confirmed through MTTY. However, I believe if I clone the header (acceptable to the device) into the "new" radio ROM; my device should be able to update. If it doesn't, I feel I could then confidently believe that the issue is in the hardware...'til then...
Can anyone out there help me with this, PLEASE!!!
So try unlockind your device to make it SuperCID
EXEC/JASJAR said:
You can find more information in the forum adout downloading by SD card. Tomal has an SD ROM tool; or you could try the service manual...Either way, I cannot seem to get an SD download to work because of a fixed CID lock; this was confirmed through MTTY. However, I believe if I clone the header (acceptable to the device) into the "new" radio ROM; my device should be able to update. If it doesn't, I feel I could then confidently believe that the issue is in the hardware...'til then...
Can anyone out there help me with this, PLEASE!!!
Click to expand...
Click to collapse
try to unlock ue device then.follow the link below..
http://wiki.xda-developers.com/index.php?pagename=Uni_Simlock_by_Buzz_and_team
Cheers
Rajiv

Troubleshooting a ROM flash on the Verizon Vogue

Hi, I hope this is a good place to put this question, I would put this in the Vogue forum but it looks kind of slow-moving, so I figured I might as well turn it over to the experts. I encountered a problem on my first real ROM flash and now I'm kind of worried to try it again. So:
I'm using a Verizon XV6900/Vogue/TouchCDMA. I flashed to the leaked Verizon 6.1 upgrade, which worked flawlessly, and enabled Win 6.1, EV-DO Rev. A., and GPS with the Valhalla CAB. Then I decided to try some custom ROMs.
I unlocked without a problem, and confirmed that I achieved 2.31 coke. I then lauched the ROM update utility on a WDM ROM I got from here. It got hung up 69% through, the RUU tried to help me but failed at 69% again. It gave me an error 262 connection error, but couldn't give any more details.
I thought I had bricked my phone, but while stuck on the three-color screen I flashed back to the leaked Verizon ROM and authenticated, now I'm fine.
I'm guessing that the Verizon radio (3.37) wasn't new enough, since most other ROMs require the new Bell 3.42.
The actual question part: Should I update my radio and try WDM's again, or should I give something else a shot? I'm looking for something stable that includes M2D, and some of that new Opal stuff (title bar, Youtube, etc.) OMJ's also looks promising.
P.S. What exactly is User customization, and will flashing a non-carrier-specific ROM like this one affect my ability to connect to Verizon?
it isn't a problem of being "new enough" it has to do with radio compatibility.
That page specifically says flash version 3.42
I imagine user cusomization is refering to "uc" compliant roms that allow you to automatically install cabs from your storage card after a flash
Hmm, I really don't see a mention of it on the page, I guess I'm just supposed to assume 3.42 because it says simply, "update radio." Thanks though.
EDIT: Well I used a ROM that's compatible with 3.37 compatible, and it works great. I guess this thread is over now.

Not-so N00B dumb question

I've been flashing new ROMS on an 8525 for a couple of years now, but I'm new to the 8925.
I've been reading a lot, I think I understand the relation between SPL and the ROMs now, but I'm still puzzled.
I keep getting a lot of cruft left behind from prior ROMs and don't know how to get rid of it. for example about three ROMs ago, I flashed the "Mobile Vista" from ansar. Now I still get his Today theme, and there are still a lot of apps installed that read "ansar..."
I've tried removing the battery before flashing, making sure the SPL version is OK with the ROM doing hard resets - nothing seems to let this device start from a "clean slate".
I'm trying to find a ROM I can be happy with, which is why I'm trying so many, but I can't fairly evaluate aon one ROM if I don't know what I've really got installed.
TIA
Walt
I've never heard of anything like that happening Are you sure it is the today theme, or just the boot splash? That would be most likely.
As far as the programs, maybe most of them are from ansar? Which ROM are you using right now?
I just flashed the PDA Corner latest version (15) and it seems to be behaving now. Prior ROMS I tried this morning included Athine, Garmin and Phoenix.
Prior to flashing PDA Corner, I did an "Erase memory" (hard reset from software) and removed the battery for about 10 minutes. Maybe that's what did it. I agree, I've never seen anything like this before, I always thought that flashing the ROM reased everything, but then I started reading about SPL on the Kaiser somehow being more than just a bootloader so I got concerned.
And yes, it was the Today screen including clock, wallpaper, etc. The splash screen on bootup actually did change to the one corresponding to the new ROM.
Thanks.
Walt
When flashing a new ROM, when you get to the "Tap screen to begin" do you perform a Hard Reset?
If not, I suggest you start doing now.
Also, merschle (ex-moderator and Artemis cook) recommended flashing a ROM twice with a Hard Reset in between. I don't do this, but it just might help
Ta
Dave
Flash a stock HTC rom and then try a modified rom again. It always helped me when i got strange flash problems.
http://wiki.xda-developers.com/index.php?pagename=Kaiser_ROMs
Billun said:
Flash a stock HTC rom and then try a modified rom again. It always helped me when i got strange flash problems.
http://wiki.xda-developers.com/index.php?pagename=Kaiser_ROMs
Click to expand...
Click to collapse
I hard reset three times then I flash an OEM ROM, then I hard reset three more times to be sure. I know it's anal, but it works for me.
I don't know how you're flashing try the SD Card method.
It's safer and more reliable.
The SPL & Rom have closer relationship than on your older device.
A sign of have the wrong SPL or needing to change to another SPL is freezing. If you notice your device is freezing or non-responsive, flash the recommended SPL by the chef.
Don't worry any, I was the same when I upgraded from the Wizard...gotta learn all over again.

[Q] Radio problem with custom ROM

I'm hoping for some friendly advice - I have a Desire S which was rooted last year and I installed CM10 to try out JB. All has been working well )part from the occasional reboot) however couple of days ago the battery started draining quickly, the phone became very hot and the wifi stopped working. After various wiping of caches and rebooting I decided to try some other ROMs (Fallout Evolution V5, Miui, IceDS) and although they all installed OK I still have no wifi and now the mobile network won't work.
It worked on Fallout at first but when the wifi wasn't working I wiped and re-installed and it hasn't worked since. It does see the O2 network although the phone hd previously been unlocked to work with Vodafone, so I think I may have rolled back the radio somehow.
At this stage I'm not entirely sure if it is a software or hardware problem, and I din't know how to test the hardware.
The phone is currently as follows:
UNLOCKED
Saga PVT ship s-on RL
HBOOT -2.02.0002
Radio -3831.19.00.110
eMMC -BOOT
July 31 2012>15.41.32​
Do I need to update the radio? If so, which version should I use? And do I need to s-off the phone first?
Any other help would be appreciated.
lesmorton said:
I'm hoping for some friendly advice - I have a Desire S which was rooted last year and I installed CM10 to try out JB. All has been working well )part from the occasional reboot) however couple of days ago the battery started draining quickly, the phone became very hot and the wifi stopped working. After various wiping of caches and rebooting I decided to try some other ROMs (Fallout Evolution V5, Miui, IceDS) and although they all installed OK I still have no wifi and now the mobile network won't work.
It worked on Fallout at first but when the wifi wasn't working I wiped and re-installed and it hasn't worked since. It does see the O2 network although the phone hd previously been unlocked to work with Vodafone, so I think I may have rolled back the radio somehow.
At this stage I'm not entirely sure if it is a software or hardware problem, and I din't know how to test the hardware.
The phone is currently as follows:
UNLOCKED
Saga PVT ship s-on RL
HBOOT -2.02.0002
Radio -3831.19.00.110
eMMC -BOOT
July 31 2012>15.41.32​
Do I need to update the radio? If so, which version should I use? And do I need to s-off the phone first?
Any other help would be appreciated.
Click to expand...
Click to collapse
Did You tried installing stock rom again in your mobile
No I haven't. I assume this would re-install the correct radio?
Not sure where to get the stock ROM, or which one was shipped with the phone.
If I did get it can I flash it through recovery - I'm using 4EXT?
lesmorton said:
No I haven't. I assume this would re-install the correct radio?
Not sure where to get the stock ROM, or which one was shipped with the phone.
If I did get it can I flash it through recovery - I'm using 4EXT?
Click to expand...
Click to collapse
Boot into bootloader and run following command
fastboot get cid
Than you can know which ruu to flash. But don't forget to downgrade your misc version before fishing ruu
No ruu are flashed from PC
Sent from my HTC Desire S using xda app-developers app
OK, I have managed to get the phone back to it's stock ROM which is O2 in the UK.
I had previously unlocked the phone but it now won't accept anything other than an O2 SIM. When I scan for networks only O2 is seen. I still have the unlock code but when I put a Vodafone SIM in it doesn't prompt me for the unlock code. I'm just getting a Limited Service display.
Is there any way of forcing the unlock code prompt screen - say with keyboard numbers or via Fastboot?
lesmorton said:
OK, I have managed to get the phone back to it's stock ROM which is O2 in the UK.
I had previously unlocked the phone but it now won't accept anything other than an O2 SIM. When I scan for networks only O2 is seen. I still have the unlock code but when I put a Vodafone SIM in it doesn't prompt me for the unlock code. I'm just getting a Limited Service display.
Is there any way of forcing the unlock code prompt screen - say with keyboard numbers or via Fastboot?
Click to expand...
Click to collapse
do i understand things as they are?
do you intend to use simcards of another operator?,
well... that`s what branding stands for,
to make sure
you`ll not use any sim from different carrier...
is your phone simlocked as well,
or is it only a branded rom ?
..but why bothering to flash the phone with branded RUU,
(when there are quite a few generic ones, still floating around,..)
except, when one wants to claim a warranty..may be...
I flashed the O2 ROM as it was what was on the phone when I bought it and I was trying to get back to a radio that would work.
I have since managed to get the phone working OK with the Asda/Vodafone SIM but I am still having problems with the wifi (this is where it all started!). whenever I switch the wifi on it scans and then reports that it is unable to scan for networks, after 2-3 attempts the wifi switches itself off.
I'm still trying to find out if it is a software or hardware problem. Other than that all is working well on the Fallout v5 ROm I have flashed - although it does make the phone run hot.
lesmorton said:
I flashed the O2 ROM as it was what was on the phone when I bought it and I was trying to get back to a radio that would work.
I have since managed to get the phone working OK with the Asda/Vodafone SIM but I am still having problems with the wifi (this is where it all started!). whenever I switch the wifi on it scans and then reports that it is unable to scan for networks, after 2-3 attempts the wifi switches itself off.
I'm still trying to find out if it is a software or hardware problem. Other than that all is working well on the Fallout v5 ROm I have flashed - although it does make the phone run hot.
Click to expand...
Click to collapse
make backup (CWM)
try to find, and flash another kernel- custom,
..that may be a possible fix, for wifi issues,
as that is very often caused by,
not efficient, or completely missing drivers (0kb file size)....
...depending on the RUU version- flashed,
you might be interested in:
http://forum.xda-developers.com/showthread.php?t=1845039
otherwise, try to look for < unity > or < endymion > kernel.....
..Heat might be caused either
by battery,
or CPU - struggling with heavy flaw of graphics, (like < Google Earth >+< Browser >+<anything one prefers > )
or a nasty app ( or several ), constantly trying to consume, most of its resources...
..both quite simple to eliminate...
..and...undervolting, it helps to reduce heat - too...
asgardr said:
make backup (CWM)
try to find, and flash another kernel- custom,
..that may be a possible fix, for wifi issues,
as that is very often caused by,
not efficient, or completely missing drivers (0kb file size)....
...depending on the RUU version- flashed,
you might be interested in:
http://forum.xda-developers.com/showthread.php?t=1845039
otherwise, try to look for < unity > or < endymion > kernel.....
..Heat might be caused either
by battery,
or CPU - struggling with heavy flaw of graphics, (like < Google Earth >+< Browser >+<anything one prefers > )
or a nasty app ( or several ), constantly trying to consume, most of its resources...
..both quite simple to eliminate...
..and...undervolting, it helps to reduce heat - too...
Click to expand...
Click to collapse
I changed the ROM to IceDS v8 which seems to run cooler. I think part of the problem was with Titanium Backup running and the wifi kept searching for a network.
I am still having the wifi problem as it displays 'unable to scan for networks'. Having searched the internet extensively and tried a few different so called fixes I have come to the conclusion it is a hardware problem. When I get time I'll see if I can strip the phone and see if I can find the cause.
lesmorton said:
I changed the ROM to IceDS v8 which seems to run cooler. I think part of the problem was with Titanium Backup running and the wifi kept searching for a network.
I am still having the wifi problem as it displays 'unable to scan for networks'. Having searched the internet extensively and tried a few different so called fixes I have come to the conclusion it is a hardware problem. When I get time I'll see if I can strip the phone and see if I can find the cause.
Click to expand...
Click to collapse
Well I stripped the phone and checked what connections I could but still no wifi.
I have used the RUU to get back to stock ROM and everything is fine except the wifi not working. Does anyone know if the wifi hardware is on the PCB, and if so where it would be in the phone. As the phone is in excellent condition I am thinking of getting a cheap phone with broken screen and just cannibalising it with my phone and building one good phone. It's just knowing what part of the phone contains the wifi hardware.
Any help would be appreciated.

Categories

Resources