Greetings all. Long time lurker and first time poster just for this dilemma.
I have a MB 860 that was given to me to be my new ForeverPhone. WiFi is stuck at a perpetual grayed out "On" where it is instructing me to connect with WiFi to see networks. Sounds typical and you are about to yell at me for not using the search function, right?
But here's the kicker: Bluetooth works and works well. It connects. It disconnects. It is glorious.
All the other threads are about a combined WiFi/Bluetooth failure. I don't have that combination. And none of the threads solve my problem.
Here is what I did before the WiFi borked on me:
Unlocked the boot loader.
Installed the KitKat ROM for the phone based unofficially on CM 11. (Works a treat, too!)
Requested and received an unlock code from ATT so that I could travel internationally.
Attempted (thrice) to unlock the carrier lock while inside a Rooted non-stock ROM. (I didn't know better.)
Carrier unlock code failed ... but so suddenly did WiFi.
WiFi now not working, I then went on to:
Reverted to Stock so as to carrier unlock. Stock revert worked.
Carrier unlock then worked.
Stock's WiFi said "Error" instead of OFF/ON.
Stock started randomly rebooting.
Returned to KitKat of Gloriousness. Returned to a still non-functioning WiFi but at least without the random reboots. Enjoying my carrier unlock freedom.
So, now I ask you all ... what happens if WiFi is borked but Bluetooth still works. What then? Likely not a hardware problem, right?
So what do I need to flash/fix? What bit of code in what place got corrupted from me trying to carrier unlock from a rooted ROM? And where can I find the correct bit of code to replace it with?
Thank you ever so kindly!!!!
PS: Not that you need it, but I got you some pictures of the non-functional WiFi so you can see what I am perpetually stuck with. (Again, Bluetooth works!)
theinfamousj said:
Greetings all. Long time lurker and first time poster just for this dilemma.
I have a MB 860 that was given to me to be my new ForeverPhone. WiFi is stuck at a perpetual grayed out "On" where it is instructing me to connect with WiFi to see networks. Sounds typical and you are about to yell at me for not using the search function, right?
But here's the kicker: Bluetooth works and works well. It connects. It disconnects. It is glorious.
All the other threads are about a combined WiFi/Bluetooth failure. I don't have that combination. And none of the threads solve my problem.
Here is what I did before the WiFi borked on me:
Unlocked the boot loader.
Installed the KitKat ROM for the phone based unofficially on CM 11. (Works a treat, too!)
Requested and received an unlock code from ATT so that I could travel internationally.
Attempted (thrice) to unlock the carrier lock while inside a Rooted non-stock ROM. (I didn't know better.)
Carrier unlock code failed ... but so suddenly did WiFi.
WiFi now not working, I then went on to:
Reverted to Stock so as to carrier unlock. Stock revert worked.
Carrier unlock then worked.
Stock's WiFi said "Error" instead of OFF/ON.
Stock started randomly rebooting.
Returned to KitKat of Gloriousness. Returned to a still non-functioning WiFi but at least without the random reboots. Enjoying my carrier unlock freedom.
So, now I ask you all ... what happens if WiFi is borked but Bluetooth still works. What then? Likely not a hardware problem, right?
So what do I need to flash/fix? What bit of code in what place got corrupted from me trying to carrier unlock from a rooted ROM? And where can I find the correct bit of code to replace it with?
Thank you ever so kindly!!!!
PS: Not that you need it, but I got you some pictures of the non-functional WiFi so you can see what I am perpetually stuck with. (Again, Bluetooth works!)
Click to expand...
Click to collapse
What stock version are you using? Have you tried flashing an sbf?
Sent from my ATRIX HD using XDA Free mobile app
palmbeach05 said:
What stock version are you using? Have you tried flashing an sbf?
Click to expand...
Click to collapse
I rolled back to the nandroid backup that I made of whatever stock version ATT had put on the phone. Gingerbread, I think.
As for flashing an sbf, I cannot find any online that are still at good hosting links. I looked and looked and looked. Will that do more than a nandroid backup of stock?
theinfamousj said:
I rolled back to the nandroid backup that I made of whatever stock version ATT had put on the phone. Gingerbread, I think.
As for flashing an sbf, I cannot find any online that are still at good hosting links. I looked and looked and looked. Will that do more than a nandroid backup of stock?
Click to expand...
Click to collapse
An sbf hits every partition available, a backup only hits select ones. Now if wifi will not turn on at all, even after a backup is restored, then your wifi chip is dead, time for a replacement
Sent from my ATRIX HD using XDA Free mobile app
palmbeach05 said:
An sbf hits every partition available, a backup only hits select ones. Now if wifi will not turn on at all, even after a backup is restored, then your wifi chip is dead, time for a replacement
Click to expand...
Click to collapse
The problem with the "the wifi chip is dead" argument is that it is an integrated chip with Bluetooth so if the chip is dead, both should be nonfunctional. And Bluetooth works.
But I'm game to try to sbf. Do you have a link to a working, reputable sbf for the MB860?
theinfamousj said:
The problem with the "the wifi chip is dead" argument is that it is an integrated chip with Bluetooth so if the chip is dead, both should be nonfunctional. And Bluetooth works.
But I'm game to try to sbf. Do you have a link to a working, reputable sbf for the MB860?
Click to expand...
Click to collapse
The results you are experiencing is normal. I'll post the sbf in a few mins on my G Drive and will provide the link.
https://drive.google.com/file/d/0B52pkPIFU2dRQ1BMZk5fVmc2OVE/view?usp=sharing
Many thanks. Unfortunately, that didn't fix it.
However, I purchased a few other Atrix 4Gs from eBay and was able to confirm that trying to unlock while inside a CM rom does, indeed, kill WiFi consistently. So it cannot be a hardware issue.
Then I used the last one to be my permanent phone and unlocked it properly, before doing anything snazzy to it.
So for those people who still have Atrix 4Gs, now we know a new thing: SIM unlocks need to be done on a stock ROM or else!
Related
Hi guys,
i know this has probably been asked a 100 times and i was searching for it on the forums and on google for 2 hours, but i couldnt find a fitting guide to it (i found tons of guides how to root it per se, but not how to save/backup the stock rom in case i would need to restore it to stock one day.
thanks in advance
crnkoj said:
Hi guys,
i know this has probably been asked a 100 times and i was searching for it on the forums and on google for 2 hours, but i couldnt find a fitting guide to it (i found tons of guides how to root it per se, but not how to save/backup the stock rom in case i would need to restore it to stock one day.
thanks in advance
Click to expand...
Click to collapse
This phone just came out. It takes time for developers to start developing. Saying that, there is no way to back up your current ROM as of now. That requires a custom recovery which has not yet been made for the Atrix.
OH, and about rooting, it won't brick your phone. I'm can't think of one phone that has got messed up from the rooting process. And if you need to unroot to "return it to stock" just unroot it. It's one of the features in SuperOneClick.
ok great thank you very much. just on a second thing, maybe if you know? i have a terrible problem with the phone. i got me a sim unlock code, that worked (can put any sim in as i l ike) but the thing is if i put a sim that is active (so it gets signal bars of my carrier) the wifi connection instantly stops working in goes into what seems to be some sort of scanning/disconnect loop. i can repair that only by hard resetting it with an old sim that doesnt get any reception, so that the wifi works than. oh and i can do calls and stuff with the working sim. so im terribly nervous right now. i found some things while googling that the wpa_supplicant is bugged on the stock 2.2.1 (what the phone is running apparently), so i tried to change the file (just did the things) and it didnt help, still the same issue. and i sort of have a problems since im now in europe and well cant really return the phone oh and otherwise the wifi works perfectly .. and another thing wifi wont work ever after inserting the working sim, even with the nonworking sim wifi still has the same problem.
Hi guys,
Lately I've been having problems with the WiFi and BT.
I know it has been like that for a while but I only noticed it yesterday.
The BT on the phone doesnt work - when I try to turn in on it just doesnt... I press the button and it stays the same way.
The WiFi doesnt work - when I try turning it on it says ERROR. and stays like that... not on and not of.
And not only that, another thing is that my phone started crushing A LOT.
I have no idea what's going on... it can crash at any moment without worning... not always coming back (sometimes I have to pull the battery out).
it can happen after 1 minute or after 3 hours...
the 2 things that changed on the phone lately are:
1. swiched from neutrino 2.8EE to 2.9EE.
2. I was in a vecation and when I tried to charge the battery it got only upto 82%. didn't cross it no matter how long it was in...(it was like that for a week).
I have to phone for like a year and a half.
help? anybody?
This is a known problem and it's been reported countless times already. Unfortunately the most likely reason is that your wifi/bt chip is fried. This is a hardware issue (more specifically, a design flaw) and there is no workaround. It has affected many others and they are just as pissed off about it as I'm sure you are. Some even say all Atrixes will sooner or later end up this way because of this design flaw.
Not sure about the crashing, but it could be related to broken wifi/bt.
Hi
I have same problem. I have Atrix 4G from UK Tmobile, with stock froyo. I flashed the stock 2.3.4 with RSD successfully, and i unl*cked the carrier.
Then i noticed, that Wifi don't work good. I don't know turn on: Wifi (error). The other problem, that the finger print scanner isnt work...
These actions do not help: factory reset, unlock BL, custom ROM (i tested Nottachtrix, any ICS ROM, stock froyo), erase all at fastboot, full wipe with CWM...
I am sure, that it is a software bug! (before flash 2.3.4 and carrier unlck, phone works fine...)
Some solutions? (I think, if we restore back to stock, the problem is solve) How can i make a fully reset, which is stronger than RSD flash stock sbf?
edit: http://forum.xda-developers.com/showthread.php?p=13754274#post13754274
or
http://forum.xda-developers.com/showthread.php?t=1035139
rain91x said:
Hi
I have same problem. I have Atrix 4G from UK Tmobile, with stock froyo. I flashed the stock 2.3.4 with RSD successfully, and i unl*cked the carrier.
Then i noticed, that Wifi don't work good. I don't know turn on: Wifi (error). The other problem, that the finger print scanner isnt work...
These actions do not help: factory reset, unlock BL, custom ROM (i tested Nottachtrix, any ICS ROM, stock froyo), erase all at fastboot, full wipe with CWM...
I am sure, that it is a software bug! (before flash 2.3.4 and carrier unlck, phone works fine...)
Some solutions? (I think, if we restore back to stock, the problem is solve) How can i make a fully reset, which is stronger than RSD flash stock sbf?
edit: http://forum.xda-developers.com/showthread.php?p=13754274#post13754274
or
http://forum.xda-developers.com/showthread.php?t=1035139
Click to expand...
Click to collapse
looks promising... did you try it?
I donnot if I can even try it... the first step is "close WiFi"... and I can't. it doesnt go off and doesnt go on... just stays on "Error".
should I just except the fact that I have to get a new phone?
should I send it to Motorola?
Alonleibo said:
looks promising... did you try it?
I donnot if I can even try it... the first step is "close WiFi"... and I can't. it doesnt go off and doesnt go on... just stays on "Error".
should I just except the fact that I have to get a new phone?
should I send it to Motorola?
Click to expand...
Click to collapse
I try it later, but i dont know now SD card. I hope, that it is a correctable bug.
edit: i tryd it, but still not good. Other solutions?
I have the same problem (wifi error, bt does not open). I guess it is a hardware problem but when I installed TopSmart rom (coming from Neutrino) they worked for 10 minutes then they crashed again. If it is a software problem (but i dont think so) there must be the answer that everyone's looking for. I hope it ends up as a software problem.
Sent from my Motorola Atrix 4G
It's most certainly a hardware problem. Clearly the WiFi chip in this phone just dies. This is also why your phone is crashing. You'll just have to leave WiFi off (if you can get to the switch before the phone crashes).
This issue started a couple months ago for me, and today I managed to accidentally flip the WiFi switch on again, sending my phone into an endless cycle of crashing and rebooting. I had to factory reset and re-flash CM10 about three times just to get it to stop rebooting repeatedly (which sucks because I didn't have a recent TiBu backup...). You might have to do this as well if your phone doesn't stop crashing.
I'd say just get a new phone. Don't send it in to Moto because even if you're in warranty they'll likely send you back a unit with a permanently locked bootloader, which isn't worth it.
It is frequent bug on Android phones. (wifi - error)
https://www.google.hu/#hl=hu&gs_nf=1&tok=EBl1OHx7E49rfa9s8zPj_A&cp=13&gs_id=1f&xhr=t&q=android+wifi+error&pf=p&output=search&sclient=psy-ab&oq=android+wifi+&gs_l=&pbx=1&bav=on.2,or.r_gc.r_pw.r_cp.r_qf.&fp=aee7b1a090091e6a&biw=1680&bih=949
MdX MaxX said:
It's most certainly a hardware problem. Clearly the WiFi chip in this phone just dies. This is also why your phone is crashing. You'll just have to leave WiFi off (if you can get to the switch before the phone crashes).
This issue started a couple months ago for me, and today I managed to accidentally flip the WiFi switch on again, sending my phone into an endless cycle of crashing and rebooting. I had to factory reset and re-flash CM10 about three times just to get it to stop rebooting repeatedly (which sucks because I didn't have a recent TiBu backup...). You might have to do this as well if your phone doesn't stop crashing.
I'd say just get a new phone. Don't send it in to Moto because even if you're in warranty they'll likely send you back a unit with a permanently locked bootloader, which isn't worth it.
Click to expand...
Click to collapse
I did turn it off... eventually.
but my phone still crashes... at the same frequency...
*added alogcat files of 2 of the crashes... if anybody can understand it...
As the title suggests, suddenly I started getting force closes with com.android.phone when I'd receive a call. I immediately tried to call out, same story. I've been troubleshooting for the past few hours, and had no luck finding anything relevant on XDA or any other site.
Firstly I switched kernels, since I'd updated to DSB's latest, though I'd had no issues with it until then. That failed, so I reverted to Viper's stock build.prop, undoing some changed I'd been running for a while (and hadn't modified at all today).
With no luck there, I backed up my sdcard and did a full factory reset and formatted the sdcard in twrp and then in cwm, followed by a reinstall of the latest Viper ROM. Even that didn't work, so I relocked and RUU'd back. Twice. Same exact issue. I can text anyone just fine, data over LTE goes on as normal, but anytime I try to make a call, be it with the stock dialer or through a diff one from the play store (for kicks, last resort). I reseated the SIM card a multitude of times, to no avail. I get full functionality with my SIM in my other phone, so I'm sure it must be the hardware itself on the phone. Every time com.android.phone stops, the SIM initialization happens like when you physically re-seat the SIM.
The troubling thing is that I haven't done anything, save for a simple kernel and recovery update, which would've been negated by two RUU runs to stock. I haven't touched the SIM card or anything, at least until that started happening. Furthermore confusing is how all other functionality can remain except for actually making phone calls.
Removing the SIM entirely and dialing a number does the exact same thing, just as an FYI.
Has anyone seen this? Any ideas?
As I've unlocked my phone, my last resort is to go into a VZW store and act like an idiot so they don't check to see if i unlocked it. Further complicating that is the fact that the DNA was actually purchased on my own account, which I closed, and brought to an unlimited data line that was preexisting. I'm half tempted to wait for the official OTA and see if that will remedy the issue, but my fear is this may be a physical issue beyond the remedy of a firmware update.
http://forum.xda-developers.com/showthread.php?t=2126386
Check this thread, me and another member faced the same problem. I can get 3g/2g data, sms and all other functions just right. Just no phonecalls, every time i make a call i get a crash of the app.
So, i am pretty sure this is a software bug. For god's sake, what a strange problem!Did your phone used to work right?
I bought my phone from ebay, did not check if phonecalls are working(i couldn't imagine such a bug) and went straight away to rooting/other kernels/roms etc. But can't find a solution too,tried everything as you, and the worst, i am overseas!!!
Is the update coming soon?
edit1: i have seen lots of threads about sim errors,a very common issue of DNA, i am believing that these two bugs have something in common. No hardware defect, just software bugs.
ergotelis said:
http://forum.xda-developers.com/showthread.php?t=2126386
Check this thread, me and another member faced the same problem. I can get 3g/2g data, sms and all other functions just right. Just no phonecalls, every time i make a call i get a crash of the app.
So, i am pretty sure this is a software bug. For god's sake, what a strange problem!Did your phone used to work right?
I bought my phone from ebay, did not check if phonecalls are working(i couldn't imagine such a bug) and went straight away to rooting/other kernels/roms etc. But can't find a solution too,tried everything as you, and the worst, i am overseas!!!
Is the update coming soon?
edit1: i have seen lots of threads about sim errors,a very common issue of DNA, i am believing that these two bugs have something in common. No hardware defect, just software bugs.
Click to expand...
Click to collapse
thanks for the thread, for the life of me i couldn't find anything exactly relating to what i described. that is spot on though, and def makes me feel a bit more at ease that maybe it can be resolved with an update to the firmware that's due soon.
yea, the funny thing is that it worked flawlessly, i never even got the SIM error message, i'd been texting my gf, a few friends, and my parents and then my pops called in the evening and it immediately closed out the call before it really even rang. i called him right back and that's when the force closes started happening, calls never working agian thereafter. however, i was able to still text everyone i was before and data was working flawlessly as always, just no calls, not even after all the crap i did to troubleshoot.
the update is hopefully going to be out soon. the support documents came out a few days ago. i def can't survive on this galaxy nexus after having used my DNA since launch!
I will wait for the update too, hopefully it will be uploaded today or tomorrow i think. But just because i can't get on the air update, i need to download from a server the update and install it on my own.
If anyone finds a solution or have an idea of what to look/do, please post here. I am pretty sure it is a software bug, something is stucking the application from working properly. The other solution is RMA, but it is a very difficult to send it back and get it back again.
ergotelis said:
I will wait for the update too, hopefully it will be uploaded today or tomorrow i think. But just because i can't get on the air update, i need to download from a server the update and install it on my own.
If anyone finds a solution or have an idea of what to look/do, please post here. I am pretty sure it is a software bug, something is stucking the application from working properly. The other solution is RMA, but it is a very difficult to send it back and get it back again.
Click to expand...
Click to collapse
The update is out now, can someone send it to me too? I am overseas, trying to find a way to download it.
OP, can you test this one to see if you get a fix?Thanks!!!
Ok, I had the same exact issue. I was stock then went to viper Dna then tried going to hatka and soft bricked my phone. I went back to stock using the RUU. That's when I got the com. Android. Phone crash message. So I had to re unlock reboot and then flash viper Dna again. Everything works as it should now.
After saying all that I just got the new update from Verizon. I assume I shouldn't flash this since I'm on a custom rom.
Sent from my Nexus 7 using xda premium
Thanks for the input, really interesting!Will try it right away! Hope you won't have any problems with the update now!
msturner79 said:
Ok, I had the same exact issue. I was stock then went to viper Dna then tried going to hatka and soft bricked my phone. I went back to stock using the RUU. That's when I got the com. Android. Phone crash message. So I had to re unlock reboot and then flash viper Dna again. Everything works as it should now.
Click to expand...
Click to collapse
THIS IS THE SOLUTION!Now working! A HUGE HUGE HUGE THANKS TO YOU!!!! :victory:
ergotelis said:
THIS IS THE SOLUTION!Now working! A HUGE HUGE HUGE THANKS TO YOU!!!! :victory:
Click to expand...
Click to collapse
Hi guys i got a similar problem. My DNA was perfect since yesterday but now i can use data connection for internet. All the other stuff is working fine....SMS,call, wifi, the only thing that is not working is the 3g data. All of this problem came when i flashed the viper DNA, so i flashed the supercharged hoping it was an issue of the rom. Olso with the supercharged the problem was always here.... So i decide to came back to stock and i re-lock my bootloader and flasched stock RUU. But data connection is still not working :crying:
can anyone please tell me what can i do?
Did you install patches 1.1.1& 1.1.2 from viper?They fix some gsm problems.
As I've unlocked my phone
ergotelis said:
Did you install patches 1.1.1& 1.1.2 from viper?They fix some gsm problems.
Click to expand...
Click to collapse
yes but notthing changed.... :'(
Now i'm compleatly stock and the problem is still here.
flash again the viper rom, do the whole procedure again, at least this is what i did and fixed the problem!(stock->viper->stock-> viper and then OK)
ergotelis said:
flash again the viper rom, do the whole procedure again, at least this is what i did and fixed the problem!(stock->viper->stock-> viper and then OK)
Click to expand...
Click to collapse
Which version of viper worked for you?
hard problem
Has any one figured out this problem? I have not been able to received any phone calls since I did s-off. I have tried everything that has been wrote so with no luck. I have relocked my phone and flashed stock RUU no change. Unlocked and tried several roms still no calls. formatted everything under CWM not change. Fixed permissions. Went back and re-locked and reflashed stock RUU. I know that some of the things above have fixed others phones and some still have problems. I also found a script someone wrote lock my phone which now it says locked and flashed stock rom after that still have problem. Does anyone here here a idea that I have not already mentione above? I like my droid dna but if I can't get it to make and take calls it is a paperweight.:crying:
jimmydee62 said:
Has any one figured out this problem? I have not been able to received any phone calls since I did s-off. I have tried everything that has been wrote so with no luck. I have relocked my phone and flashed stock RUU no change. Unlocked and tried several roms still no calls. formatted everything under CWM not change. Fixed permissions. Went back and re-locked and reflashed stock RUU. I know that some of the things above have fixed others phones and some still have problems. I also found a script someone wrote lock my phone which now it says locked and flashed stock rom after that still have problem. Does anyone here here a idea that I have not already mentione above? I like my droid dna but if I can't get it to make and take calls it is a paperweight.:crying:
Click to expand...
Click to collapse
Still broke?
Sent from my HTC6435LVW using xda app-developers app
kaliblazin707 said:
Still broke?
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Yes it is still broke I just don't know what to do at this point paper weight right now.
I work with a guy that owns an ATT m7. He isnt too knowledgeable on rooting however he does flash his own roms and has some idea about it all. he told me he bricked his phone and thinks that after flashing so many roms he fried something with the radio. The phone does not receive a signal.
I took the phone home for him to fix. Just to test I flashed CM11 and just as he said radio was not working. It showed bars but if i tried to make a call it didnt work. I figured this would happen anyways so i carried on with obtaining s-off. I then flashed a 4.1.2 RUU. I put my sim card in (straightalk) and at first it didnt work. after a few minutes I looked again and vuala I had service. I added in my APN and everything seemed to go smooth. I did notice that periodically I would look at the phone and see it said "emergency calls only" but it quickly fixed itself (my s4 does the same thing so it could just be my area)
I used the phone all day and it seemed to be fine. Texts and calls worked perfectly. Feeling confident I then rooted and installed twrp. I backed up the stock rom and flashed CM.
No service.....
Anyone have any clue whats going on? I am currently RUUing again to see if it will work again and I am sure it will.
Im having trouble understanding this issue as I feel that if there was a mismatched radio then RUU fixed it. How would CM make this not work? Only thing I havent tried is a different rom (this was a nightly so i dont know if it has an issue) I just really don't feel like going through all the trouble again just to find out its not the ROM.
Hopefully someone has some insite.
Something is wrong with the software hes using if working on regular sense build and not cm,best aaking in the rom developers thread.
paradoxed said:
I work with a guy that owns an ATT m7. He isnt too knowledgeable on rooting however he does flash his own roms and has some idea about it all. he told me he bricked his phone and thinks that after flashing so many roms he fried something with the radio. The phone does not receive a signal.
I took the phone home for him to fix. Just to test I flashed CM11 and just as he said radio was not working. It showed bars but if i tried to make a call it didnt work. I figured this would happen anyways so i carried on with obtaining s-off. I then flashed a 4.1.2 RUU. I put my sim card in (straightalk) and at first it didnt work. after a few minutes I looked again and vuala I had service. I added in my APN and everything seemed to go smooth. I did notice that periodically I would look at the phone and see it said "emergency calls only" but it quickly fixed itself (my s4 does the same thing so it could just be my area)
I used the phone all day and it seemed to be fine. Texts and calls worked perfectly. Feeling confident I then rooted and installed twrp. I backed up the stock rom and flashed CM.
No service.....
Anyone have any clue whats going on? I am currently RUUing again to see if it will work again and I am sure it will.
Im having trouble understanding this issue as I feel that if there was a mismatched radio then RUU fixed it. How would CM make this not work? Only thing I havent tried is a different rom (this was a nightly so i dont know if it has an issue) I just really don't feel like going through all the trouble again just to find out its not the ROM.
Hopefully someone has some insite.
Click to expand...
Click to collapse
Yes but after 4.1.2 RUU it still cuts data on and off. Is it possible it's a bad radio or should we try a differentRUU?U
first id say get to an area where the radio reception is better, get an att card and not straight talk and test.this could very well be a hardware issue as well, but it seems more of a simcard issue/software issue than a hardware issue
Hello! I hope everyone is doing great and I hope LG G2 mini threads aren't dead, which I doubt.
So my issue is that SIM card, afew months ago, just randomly stopped working. Tried all classical, to remove it, clean it, let the phone stay off without the battery, try different SIM, but all lead to the same result, no service.
Another issue, that just recently occurred, is that radio devices, like Wi-Fi and Bluetooth, don't work. After attempting to turn on any of them, the button turns on for a few seconds and then it turns off or something like that. Also MAC address isn't present. But here is the ridiculous fact. So I found out a way to get it functioning. Before booting up the system, I slam it on the back and sides and then gently turn it on. Great! The Wi-Fi works, able to connect to my home Wi-Fi and to play a YouTube video. Bluetooth also able to pair it with my PC, transfer files. It works 1/5 times that I've tried because after rebooting the phone, it just losses it.
Now I'm guessing it's because of the bad contacts on the both issues. Though a heat gun would help but I don't own one. Maybe a hair dryer could do the trick? Or maybe even cook it? Motherboard of course, not the whole phone.
Now I also should mention that it's got Lineage OS 15.1 unofficial running on it. That is actually when the issue with Wi-Fi and Bluetooth started to happen but that I'm guessing is just a crazy coincidence. Also it's LG-D620r
Did the problem start when you unlock the bootloader?
Have you tried flashing another ROM to see if it gets better?
Vagelis1608 said:
Did the problem start when you unlock the bootloader?
Have you tried flashing another ROM to see if it gets better?
Click to expand...
Click to collapse
The SIM problem started before flashing new rom. Everything was stock, but Wi-Fi and Bluetooth issues started after flashing the rom and recovery. But I haven't tried flashing new one, just the same one twice because I had problems with play services
Make a backup and flash a kdz and tell me if that fixes anything.
Vagelis1608 said:
Make a backup and flash a kdz and tell me if that fixes anything.
Click to expand...
Click to collapse
My priority is to fix the SIM issue and I doubt that installing the stock ROM will fix that. Like I've stated before, the SIM issue started before Installing Lineage OS 15.1. The version I was on was plus.pl, Poland's service provider, version of Lolipop 5.0.2 which was upgraded from KitKat 4.4.2, if I'm not mistaken
Assuming that it is not caused by the ROM or broken/incompatible drivers, then the SIM slot is probably broken.
Not much you can do about it. Not worth the money, anyway.
Vagelis1608 said:
Assuming that it is not caused by the ROM or broken/incompatible drivers, then the SIM slot is probably broken.
Not much you can do about it. Not worth the money, anyway.
Click to expand...
Click to collapse
Alright, at least I tried. Thanks anyways