Related
Now, from what I can gather, this problem stems from a faulty or dirty Micro-USB port. I tried compressed air, but it did nothing for me.
I decided to do a complete unroot, S-ON, factory restore and call HTC to see if I could get it fixed. To my surprise, the problem vanished. Thinking I had lucked out and that fixed it, I re-rooted the phone and the problem still didn't reappear.
Then, thinking I would start small, I flashed a Sense kernel. As soon as I rebooted it went straight to Car Home and began answering in speakerphone. For laughs I went ahead and flashed MIUI then CM7, both of which exhibited the same behavior.
After all of this, I got to wondering just why the stock ROM and kernel worked but nothing third party would. Then it hit me that all the 3rd party stuff I had been using were DHD ports, and not based off the Inspire. I downloaded and flashed ClearDroid, which has an Inspire base, and the problem is once again dormant.
The only sense I can make from it is that HTC has implemented some kind of fix for shoddy USB ports in the Inspire kernel.
So now here's the question: Does anybody know anything about this, and would it be possible to implement said fix in, say, and AOSP kernel?
When you flash a Rom there is a folder created called data on the root of your phone. This contains many files that control various settings on your phone. There is a file in particular where cardock settings get synced in data/data/Com.android.providers.settings/databases/settings.db. When you sign in with your google account some of these settings get restored to the mode in which you had it in when you wiped your phone. This is what causes some people to think that parts of their old Rom are bugging out their phone, I guess in a way it is, but its googles fault. The car dock is getting resynced to being on even though you haven't done anything. In order to fix it you must use SQL editor to open the database and look for the carmode or dock settings and set them back to 0. Once you do this it the next time the phone autosyncs it will save your newer settings.
Also Im pretty sure when your rooted this setting will take effect as to where a nonrooted phone doesn't allow the permission to execute the command.
Gizmoe said:
When you flash a Rom there is a folder created called data on the root of your phone. This contains many files that control various settings on your phone. There is a file in particular where cardock settings get synced in data/data/Com.android.providers.settings/databases/settings.db. When you sign in with your google account some of these settings get restored to the mode in which you had it in when you wiped your phone. This is what causes some people to think that parts of their old Rom are bugging out their phone, I guess in a way it is, but its googles fault. The car dock is getting resynced to being on even though you haven't done anything. In order to fix it you must use SQL editor to open the database and look for the carmode or dock settings and set them back to 0. Once you do this it the next time the phone autosyncs it will save your newer settings.
Click to expand...
Click to collapse
I'll try that, but I can completely wipe my phone (cache, system, data, d-cache), flash CM 7.1.0, and without even logging into my Google account it happens.
After searching it seems this is a common problem with the phone. Some people where able to fix it and some where not. Even when it does go away for a while it will re emerge and get worse.
Some of the fixes are
1. turning airplane mode on for 10 min and then shutting it off
2. Changing chargers(dont ask me)
3. Blowing out port which you said you tried.
I am still not 100% its not some internal issue but why even bother if the hardware is malfunctioning.
I would start the warranty process and get it replaced.
Backing up to the beginning.....Are you flashing ROMs or kernels? Seems to me you are flashing ROMs but keep using the word kernel.
Why not just remove the car dock app from the ROM or use Titanium Backup to freeze it?
Agoattamer said:
Backing up to the beginning.....Are you flashing ROMs or kernels? Seems to me you are flashing ROMs but keep using the word kernel.
Why not just remove the car dock app from the ROM or use Titanium Backup to freeze it?
Click to expand...
Click to collapse
Both.
With the stock ROM and kernel, everything is fine. With the stock ROM and a DHD-based kernel it happens. With any AOSP ROM it happens.
Removing the Car Dock app keeps it from launching, but the phone still defaults to speakerphone for all calls (incoming and outgoing).
Gizmoe said:
After searching it seems this is a common problem with the phone. Some people where able to fix it and some where not. Even when it does go away for a while it will re emerge and get worse.
Some of the fixes are
1. turning airplane mode on for 10 min and then shutting it off
2. Changing chargers(dont ask me)
3. Blowing out port which you said you tried.
I am still not 100% its not some internal issue but why even bother if the hardware is malfunctioning.
I would start the warranty process and get it replaced.
Click to expand...
Click to collapse
The problem about warrantying it is when it's in a stock state, it works fine.
I've never dealt with HTC, but I can't exactly see it going over well if I call up and say "My phone acts funky when I run CyanogenMod".
The airplane mode fix is something I haven't heard before. I guess I'll give it a go.
Hi, everyone. First I want to thank everyone who takes their time to come and help people like me who mess with things we don't know anything about - such as rooting phones, etc
I installed JellyBam 4.0.0 on my (US T-Mobile) HTC One S S4 earlier this evening. Everything so far seems to be working fine except there is no external audio - no ringtone sound, no radio or music file sound, no notification sound, etc. However, the headphones work fine. I'm not great with tech things, but I'm not a complete idiot, either. I've searched for similar issues and can't find one posted, don't see any settings that may be causing the issue... I'm at a loss.
JellyBam was installed on TWRP recovery and the boot.img was flashed immediately after installation via fastboot. I'm trying to think of what other information from me would prove helpful, but I can't come up with anything else.
So, can anyone offer any ideas as to what the problem (and solution!) may be? I will add that immediately prior to beginning the flash of the ROM and boot.img, I updated the HTC drivers through HTC Sync/Windows 7.
Thanks for any insight or ideas.
david251 said:
Hi, everyone. First I want to thank everyone who takes their time to come and help people like me who mess with things we don't know anything about - such as rooting phones, etc
I installed JellyBam 4.0.0 on my (US T-Mobile) HTC One S S4 earlier this evening. Everything so far seems to be working fine except there is no external audio - no ringtone sound, no radio or music file sound, no notification sound, etc. However, the headphones work fine. I'm not great with tech things, but I'm not a complete idiot, either. I've searched for similar issues and can't find one posted, don't see any settings that may be causing the issue... I'm at a loss.
JellyBam was installed on TWRP recovery and the boot.img was flashed immediately after installation via fastboot. I'm trying to think of what other information from me would prove helpful, but I can't come up with anything else.
So, can anyone offer any ideas as to what the problem (and solution!) may be? I will add that immediately prior to beginning the flash of the ROM and boot.img, I updated the HTC drivers through HTC Sync/Windows 7.
Thanks for any insight or ideas.
Click to expand...
Click to collapse
Change the ring volume and it should kick in.
Darknites said:
Change the ring volume and it should kick in.
Click to expand...
Click to collapse
Thank you. I just tried that and there's no change. Also went into the sound menu, turned everything down (volume settings) then opened it again and turned everything back up. No change.
I suppose I could walk around everywhere with me headphones on I love this ROM.
david251 said:
Thank you. I just tried that and there's no change. Also went into the sound menu, turned everything down (volume settings) then opened it again and turned everything back up. No change.
I suppose I could walk around everywhere with me headphones on I love this ROM.
Click to expand...
Click to collapse
Are you doing this with the headphones still plugged in?
No, I didn't. But after your question I did - still no change
david251 said:
No, I didn't. But after your question I did - still no change
Click to expand...
Click to collapse
Hmm not sure then other then doing a wipe and try the volume when it first boots.
Ok. Thanks for the time. I'll try that.
Sent from my HTC One S using Tapatalk 2
Darknites said:
Hmm not sure then other then doing a wipe and try the volume when it first boots.
Click to expand...
Click to collapse
Do you think he might have to do what I did for the sd card, maybe that will kick in what he is missing plus doing the full wipe and re-flashing the ROM just wondering?
TheCrow1372 said:
Do you think he might have to do what I did for the sd card, maybe that will kick in what he is missing plus doing the full wipe and re-flashing the ROM just wondering?
Click to expand...
Click to collapse
No its an old bug that's been there for as long I can remember lol but changing the volume should fix it.
Darknites said:
No its an old bug that's been there for as long I can remember lol but changing the volume should fix it.
Click to expand...
Click to collapse
Just to make sure I understand (because I am technology-challenged), when you say changing the volume - I assume you're talking about either using the volume rocker on the side of the phone or simply going into Settings > Sound and changing the volume sliders there.
Correct?
david251 said:
Just to make sure I understand (because I am technology-challenged), when you say changing the volume - I assume you're talking about either using the volume rocker on the side of the phone or simply going into Settings > Sound and changing the volume sliders there.
Correct?
Click to expand...
Click to collapse
Ya I mean the first but both ways should work but do it without the headphones.
---------- Post added at 04:13 PM ---------- Previous post was at 04:11 PM ----------
Oh just popped in the head but try having music playing and do it.
I did. Tried it when searching ring tones, then tried it with Google Music playing a track, tried it with local radio playing and tried it with nothing at all playing.
So let me ask you this - can I make a backup (Titanium Backup) of all my current settings so that when I wipe/reinstall, I don't have to redownload all my apps and redo everything?
Lol - I gotta say, though, as irritating as it is to have only this one issue... I love this ROM and the way my phone works with it. It's worth the hassle if I can get it fixed. (Especially considering I almost bricked it yesterday before finally finding this ROM.)
I should really not mess with stuff I know nothing about. But I just can't help it.
david251 said:
I did. Tried it when searching ring tones, then tried it with Google Music playing a track, tried it with local radio playing and tried it with nothing at all playing.
So let me ask you this - can I make a backup (Titanium Backup) of all my current settings so that when I wipe/reinstall, I don't have to redownload all my apps and redo everything?
Lol - I gotta say, though, as irritating as it is to have only this one issue... I love this ROM and the way my phone works with it. It's worth the hassle if I can get it fixed. (Especially considering I almost bricked it yesterday before finally finding this ROM.)
I should really not mess with stuff I know nothing about. But I just can't help it.
Click to expand...
Click to collapse
Load TWRP and do a backup there, then still in TWRP do factory reset and reboot and skip over the signing in stuff and then try playing with volume without plugging in the headphones and if this still don't work you could try in TWRP factory reset and then system and them reflash the rom and if this still some how don't work you can restore the backup in TWRP.
Ok, I'll do that now - but first, one more stupid question. After this, I'll leave you alone.
When I first installed this ROM, I went through Fastboot to flash the boot.img. Do I have to do that again if reflashing the ROM, or can I skip that step?
Thanks for all your guidance. Seriously.
Update on thread
So I followed the instructions above.
Went into TWRP, did a factory reset and rebooted. Played with volume. Still no external audio.
Went back into TWRP, factory reset, wiped system, reflashed ROM (did NOT manually reflash boot.img in Fastboot) then rebooted. Played with volume. Still no external audio.
Went back into TWRP and restored the backup - so I'm still left with a killer phone with no external audio, ringtone, etc.
Hmmm.... hope nobody calls when I can't hear/feel the vibrate or have my headphones in
That's strange though - I find no other threads mentioning a glitch like this and, except for this one issue, the phone/ROM works flawlessly. It even fixed the wifi connection problem that always existed with the stock phone/ROM and I know a lot of people with this phone have had that problem. With the stock, the wifi always had a problem (from the first day) connecting to my home wifi. Sometimes it would connect but normally it would take a long time (an hour or more) before finally connecting and still other times it wouldn't connect at all. Now if I leave the house, it connects as soon as I pull up in the driveway and if I power down/reboot, it connects instantly upon reloading.
Just before installing the ROM (the first time) I connected with HTC Sync via my pc/usb and made sure drivers were up to date, which is why I'm thinking it's not a driver issue. Would you agree?
david251 said:
So I followed the instructions above.
Went into TWRP, did a factory reset and rebooted. Played with volume. Still no external audio.
Went back into TWRP, factory reset, wiped system, reflashed ROM (did NOT manually reflash boot.img in Fastboot) then rebooted. Played with volume. Still no external audio.
Went back into TWRP and restored the backup - so I'm still left with a killer phone with no external audio, ringtone, etc.
Hmmm.... hope nobody calls when I can't hear/feel the vibrate or have my headphones in
That's strange though - I find no other threads mentioning a glitch like this and, except for this one issue, the phone/ROM works flawlessly. It even fixed the wifi connection problem that always existed with the stock phone/ROM and I know a lot of people with this phone have had that problem. With the stock, the wifi always had a problem (from the first day) connecting to my home wifi. Sometimes it would connect but normally it would take a long time (an hour or more) before finally connecting and still other times it wouldn't connect at all. Now if I leave the house, it connects as soon as I pull up in the driveway and if I power down/reboot, it connects instantly upon reloading.
Just before installing the ROM (the first time) I connected with HTC Sync via my pc/usb and made sure drivers were up to date, which is why I'm thinking it's not a driver issue. Would you agree?
Click to expand...
Click to collapse
Ya not sure what's up if you still got your backup you could try another rom like CM10 to see if its the same. The wifi confused me, everybody else find AOSP not as good at wifi, for me Sense let me set the router how ever I want but on AOSP I have to have it at default settings.
Final update on this thread
Earlier, I wiped everything (through hboot) and reflashed JellyBam. Once rebooted, not only did I still not have audio, but the wifi connection went back to normal - it would connect, but not without difficulty/delays. Strange,
Since I can't feasibly go without a ringtone/alarm/notifications (I use my phone for my business) I rewiped everything from TWRP and installed Dark Jelly v23 to include the Fusion Ultimate kernel. On first boot, still no sound but the notes here mention that may be an issue until it's rebooted a second time. So I set everything up, played around with the same ideas we were using earlier in this thread (to no avail) and then rebooted.
Wifi is the same as it always has been (with the exception of the glorious several hours when it worked like a champ on JellyBam). That's no big deal - I'm used to it and know it's an HTC One S quirk.
But....
Sound is back :good:
david251 said:
Earlier, I wiped everything (through hboot) and reflashed JellyBam. Once rebooted, not only did I still not have audio, but the wifi connection went back to normal - it would connect, but not without difficulty/delays. Strange,
Since I can't feasibly go without a ringtone/alarm/notifications (I use my phone for my business) I rewiped everything from TWRP and installed Dark Jelly v23 to include the Fusion Ultimate kernel. On first boot, still no sound but the notes here mention that may be an issue until it's rebooted a second time. So I set everything up, played around with the same ideas we were using earlier in this thread (to no avail) and then rebooted.
Wifi is the same as it always has been (with the exception of the glorious several hours when it worked like a champ on JellyBam). That's no big deal - I'm used to it and know it's an HTC One S quirk.
But....
Sound is back :good:
Click to expand...
Click to collapse
Lol the phone does love to be picky.
I didnt root or unlock it myself.... im pretty sure i wiped all data before flashing the rom i have on there now, but i cant remember for sure....
seems to be the only way to truly fix my extremely messed up WIFI situation... (wifi kills my phone completely... regardless of whose internet as i tried my neighbours and got the same error). i did a restore to last year but it only fixed it for a day... if im gonna restore to a year ago again, i figure i may as well do a full fresh install, since its crapping out still anyway
i have something called superuser (i know is root access), and something called stk which ive read is sim toolkit, in "system/app" they are both apk's. "superuser.apk" and "stk.apk"
also, will my custom recovery be gone? as far as i remember that is how i flashed my ROM last time... but its been so long i cant remember...
Let me try helping since myself new on forums:-
There are two types of phone resets available- 1.Factory wipe from settings of phone/from custom recovery (cwm/twrp) or 2.Complete wipe performed such as in upgrading os version of android (like i did lollipop from jellybean). The complete wipe is done in custom recovery only under mounts and advance option in cwm and then wiping cache,system,data and everything else. If you do so,you will be losing everything installed in your phone EXCEPT Root and Custom recovery.
Back to your question, if you perform factory reset,NO,you don't lose root. If you do complete wipe from recovery,still you don't lose root of your phone UNLESS you fix the root on reboot.
Choose the reset carefully before installing any rom,read their steps,if they ask full wipe or just factory reset and dalvik cache.
Hope it helps.
Sent from my GT-I9300 using XDA Free mobile app
you cannot unroot yourself thru factory reset
Pawprints1986 said:
I didnt root or unlock it myself.... im pretty sure i wiped all data before flashing the rom i have on there now, but i cant remember for sure....
seems to be the only way to truly fix my extremely messed up WIFI situation... (wifi kills my phone completely... regardless of whose internet as i tried my neighbours and got the same error). i did a restore to last year but it only fixed it for a day... if im gonna restore to a year ago again, i figure i may as well do a full fresh install, since its crapping out still anyway
i have something called superuser (i know is root access), and something called stk which ive read is sim toolkit, in "system/app" they are both apk's. "superuser.apk" and "stk.apk"
also, will my custom recovery be gone? as far as i remember that is how i flashed my ROM last time... but its been so long i cant remember...
Click to expand...
Click to collapse
Factory reset WILL:
Remove all apps and their data
Contacts that are not on the SIM card
(In some rare cases) Pictures, music...
Factory reset WILL NOT:
Remove carrier unlock
Remove root (but may remove superuser app)
Remove the recovery
In case that superuser app is gone, just install that same superuser app from Google Play and update it if it asks to do so.
Ok, let me ask this, to ask if its even worth me doing....
last night i did the same restore to a year ago... except this time while i still had wifi i had downloaded both avast and AVG
I can with both now, and my phone says its clean...
but yet the problem is recurring now, and wifi, 4g, tethering..... basically any function that connects me to the world outside completely craps out my phone...
i thought the restore, and especially he restore and downloading antivirus would fix it, or at least be able to tell me WHAT the problem is... avast will scan the wifi network, but of course this test now freezes up just the same cuz it has to turn on wifi to do so.... while it was still working this test did execute just fine with no errors....
its as soon as internet is connected... for 3g or even my router, it will read it without the internet feed plugged in. but plug that in and it all goes to crap again. Id just hate to do a full fresh install just for it to all go to crap *again*....
ive scanned all computers on the router and those come back clean/no viruses... i tried i different router with internet, same error. i tried the neighbours connection.... same thing again.
this is really baffling.
so i feel more comfortable doing a factory reset....... but i guess im wondering is will it help me??? at all????
whatever this is is clearly not an infected device as some on another forum had thought.... something *else* is going wrong....
Pawprints1986 said:
Ok, let me ask this, to ask if its even worth me doing....
last night i did the same restore to a year ago... except this time while i still had wifi i had downloaded both avast and AVG
I can with both now, and my phone says its clean...
but yet the problem is recurring now, and wifi, 4g, tethering..... basically any function that connects me to the world outside completely craps out my phone...
i thought the restore, and especially he restore and downloading antivirus would fix it, or at least be able to tell me WHAT the problem is... avast will scan the wifi network, but of course this test now freezes up just the same cuz it has to turn on wifi to do so.... while it was still working this test did execute just fine with no errors....
its as soon as internet is connected... for 3g or even my router, it will read it without the internet feed plugged in. but plug that in and it all goes to crap again. Id just hate to do a full fresh install just for it to all go to crap *again*....
ive scanned all computers on the router and those come back clean/no viruses... i tried i different router with internet, same error. i tried the neighbours connection.... same thing again.
this is really baffling.
so i feel more comfortable doing a factory reset....... but i guess im wondering is will it help me??? at all????
whatever this is is clearly not an infected device as some on another forum had thought.... something *else* is going wrong....
Click to expand...
Click to collapse
Factory reset fixes all problems that were not made with root. You will not lose root either. For a total fix just wipe everything and reflash rom.
Right now im trying a different router, which doesnt have any windows XP machine plugged into it, and i made it extremely secure. even changed the default username and password to get onto the router itself (never bothered with the other one, the one i had been routinely using)... I did a complete reset of this router before even connecting to it with my phone, after it was secured. the other regular one still has everything else connected to it. this one is literally a separate connection, which i named "phone test" lol.
if it makes no difference, total fresh install is my last resort. if it *does* make a difference however... then something in my other regular router is messed up that cause my phones connections to freeze up - but that avast or AVG wouldnt detect (thats the only weird part)...
i even did a scan of my external SD card the other day, thats clean too.
time will tell, im approaching the 24 hour mark with this new setup. if by tomorrow its freezing up again, its not the router. but if its still working, ill have extreme suspicion that it was in fact, the router, probably something dealing with my XP machine thats plugged into it (well, normally anyway).
Time will tell...
im also trying to remember which apps i had updated before any problems started in case there are any corrupted updates i installed, without knowing it. (legit from play store, but still, ive heard that doesnt always mean totally safe, cuz anyone can make them)
Dude, wipe data, cache, system, reflash rom on your phone. BUM, problem fixed.
I still may, but i wanted to play around with the routers first to see if i could fix the problem.... that way id know i wouldnt be fully wiping for no apparent reason. if in a week or so things have been fine and i try connecting to the old regular router... than ill know its something on there infecting my phone... id rather not have a fresh install crapping out on me.
You can do a nandroid backup and then reflash everything. That way if you screw something up or the problem is not fixed you can restore in minutes.
THE ORIGIN OF THE ISSUE:
Everything began 1 month ago. I was using my Nexus 5 like I always did. I had my WiFi turned on because I was chatting with my friends on Instagram and I left my smartphone charging. There were notifications and the notification light turned on showing me that I had two texts from Instagram app. When I tried to turn it on the screen, I pressed the power button, but the screen did not turn on. I pressed the power button again and again and again, but still the same. I tried to force-reboot my device and that's what I did. When the screen started again, my WiFi was stuck at "turning WiFi on...", also, my Bluetooth was not working properly too, because when I tried to turn it on, it automatically turned back off.
ATTEMPT TO FIX #1:
First thing I tried was unrooting and reinstalling stock using Nexus Root Toolkit. That didn't work... I tried doing a simple factory reset from the phone settings, also didn't work...
After those fails, I noticed that my MAC address was corrupted, showing this: 02:00:00:00:00:00 so I searched the Internet for stuff related to this MAC address error and found people with similar problem just like mine. I found solutions like deleting /persist/wifi folder (my friend did not recommended me to do so after I did this). So, I did the thing, AND IT DID NOT HELP. Tried returning to stock using Nexus Root Toolkit AND IT DID NOT HELP. I had an idea to delete my entire system using TWRP and I thought that reinstalling it would fix the problem. But I was noob at the moment, didn't know how to flash after deleting it. Anyway, I went on, and deleted system, but I didn't know how to reinstall and I was without a smartphone for 3 weeks. I was sooooooooo sad cause this was the worst issue I had to deal with... No smartphone... No WiFi.... life sucks (still does, I am sooo depressed for a stupid smartphone)... Well, obviously, NOTHING HELPED.
ATTEMPT TO FIX #2:
After those 3 weeks, I finally managed to find a way to reinstall OS on my smartphone again (using Nexus 5 factory image found in Google site for developers). I was sooo happy because at least I managed to turn the smartphone back on. So, step two was to check if WiFi worked. Well... not as I expected things to be. It didn't work... Obviously... Well, after doing simple experiments, I tried to do "the thing again". After deleting file .macaddr from /persist/wifi folder, without deleting the folder, only the file, WiFi turned back on!!! I went in tears thanking God. Sooooo much happiness!!! I desided to insert WiFi APs that I prevously saved in a wpa_supplicant.conf file, and guess what.... I F***** UP WIFI AND SENSORS!!! I was sooooo mad!
ATTEMPT TO FIX #3:
Well, the next day, I attempted to do a system delete again, but this time, I used another computer device, my family laptop. I deleted system, and this time, I didn't flash anything using Nexus Root Toolkit, but I used this Nexus 5 factory image again. WIFI WAS BACK ON!!! YEESSS!!! I was crying soooo hard!! I again thanked God!!! But it didn't last long... After two days, I turned on my WiFi to check my messages from Instagram, sadly, my WiFi was again stuck on "turning WiFi on..." and my smartphone rebooted by itself (again). So... guess what. I DEAR YOU TO GUESS WHAT HAPPENED NEXT!!! MAC address was back to this STUPID 02:00:00:00:00:00. I had enouch. I installed Termux, I installed a packet called "macchanger" and tried to change my MAC address to something random. I used command "macchanger -r wlan0" and I rebooted. This changed my MAC address to something random. Now, WiFi turns on and when I open an application to use WiFi with, it turns off immediatelly... Also, my MAC address is on changing again with command "macchanger -r wlan0" and is stuck in the previous randomized MAC address. Using "macchanger" command, I also noticed that my "permanent" MAC address is now: 00:00:00:00:00:00 (something that was never valid).
WHAT DO I DO?
DO I NEED TO BUY A NEW SMARTPHONE BECAUSE THIS ONE IS PRETTY F***** UP?
DO I NEED TO REPLACE THE ENTIRE MOTHERBOARD?
IS THIS EVEN A HARDWARE ISSUE?
IS THIS A SOFTWARE ISSUE?
DO I NEED TO REPLACE FIRMWARE? IF SO, HOW DO I DO THAT?
DOES THIS HAVE SOMETHING TO DO WITH /PERSIST?
WHAT DO YOU PROPOSE? BECAUSE I AM TIRED OF THIS STORY, REALLY...
SPECIAL URL: https://forum.xda-developers.com/t/...y-are-and-how-to-get-it-back-if-lost.3307793/
Retr0.Hacker said:
THE ORIGIN OF THE ISSUE:
Everything began 1 month ago. I was using my Nexus 5 like I always did. I had my WiFi turned on because I was chatting with my friends on Instagram and I left my smartphone charging. There were notifications and the notification light turned on showing me that I had two texts from Instagram app. When I tried to turn it on the screen, I pressed the power button, but the screen did not turn on. I pressed the power button again and again and again, but still the same. I tried to force-reboot my device and that's what I did. When the screen started again, my WiFi was stuck at "turning WiFi on...", also, my Bluetooth was not working properly too, because when I tried to turn it on, it automatically turned back off.
ATTEMPT TO FIX #1:
First thing I tried was unrooting and reinstalling stock using Nexus Root Toolkit. That didn't work... I tried doing a simple factory reset from the phone settings, also didn't work...
After those fails, I noticed that my MAC address was corrupted, showing this: 02:00:00:00:00:00 so I searched the Internet for stuff related to this MAC address error and found people with similar problem just like mine. I found solutions like deleting /persist/wifi folder (my friend did not recommended me to do so after I did this). So, I did the thing, AND IT DID NOT HELP. Tried returning to stock using Nexus Root Toolkit AND IT DID NOT HELP. I had an idea to delete my entire system using TWRP and I thought that reinstalling it would fix the problem. But I was noob at the moment, didn't know how to flash after deleting it. Anyway, I went on, and deleted system, but I didn't know how to reinstall and I was without a smartphone for 3 weeks. I was sooooooooo sad cause this was the worst issue I had to deal with... No smartphone... No WiFi.... life sucks (still does, I am sooo depressed for a stupid smartphone)... Well, obviously, NOTHING HELPED.
ATTEMPT TO FIX #2:
After those 3 weeks, I finally managed to find a way to reinstall OS on my smartphone again (using Nexus 5 factory image found in Google site for developers). I was sooo happy because at least I managed to turn the smartphone back on. So, step two was to check if WiFi worked. Well... not as I expected things to be. It didn't work... Obviously... Well, after doing simple experiments, I tried to do "the thing again". After deleting file .macaddr from /persist/wifi folder, without deleting the folder, only the file, WiFi turned back on!!! I went in tears thanking God. Sooooo much happiness!!! I desided to insert WiFi APs that I prevously saved in a wpa_supplicant.conf file, and guess what.... I F***** UP WIFI AND SENSORS!!! I was sooooo mad!
ATTEMPT TO FIX #3:
Well, the next day, I attempted to do a system delete again, but this time, I used another computer device, my family laptop. I deleted system, and this time, I didn't flash anything using Nexus Root Toolkit, but I used this Nexus 5 factory image again. WIFI WAS BACK ON!!! YEESSS!!! I was crying soooo hard!! I again thanked God!!! But it didn't last long... After two days, I turned on my WiFi to check my messages from Instagram, sadly, my WiFi was again stuck on "turning WiFi on..." and my smartphone rebooted by itself (again). So... guess what. I DEAR YOU TO GUESS WHAT HAPPENED NEXT!!! MAC address was back to this STUPID 02:00:00:00:00:00. I had enouch. I installed Termux, I installed a packet called "macchanger" and tried to change my MAC address to something random. I used command "macchanger -r wlan0" and I rebooted. This changed my MAC address to something random. Now, WiFi turns on and when I open an application to use WiFi with, it turns off immediatelly... Also, my MAC address is on changing again with command "macchanger -r wlan0" and is stuck in the previous randomized MAC address. Using "macchanger" command, I also noticed that my "permanent" MAC address is now: 00:00:00:00:00:00 (something that was never valid).
WHAT DO I DO?
DO I NEED TO BUY A NEW SMARTPHONE BECAUSE THIS ONE IS PRETTY F***** UP?
DO I NEED TO REPLACE THE ENTIRE MOTHERBOARD?
IS THIS EVEN A HARDWARE ISSUE?
IS THIS A SOFTWARE ISSUE?
DO I NEED TO REPLACE FIRMWARE? IF SO, HOW DO I DO THAT?
DOES THIS HAVE SOMETHING TO DO WITH /PERSIST?
WHAT DO YOU PROPOSE? BECAUSE I AM TIRED OF THIS STORY, REALLY...
Click to expand...
Click to collapse
You said you were rooted.
Any chance you made a backup, especially a backup from the efs partition?
User699 said:
You said you were rooted.
Any chance you made a backup, especially a backup from the efs partition?
Click to expand...
Click to collapse
What is EFS? What backup do I do. Cause, I'm a noob and all, and I am not the type of a developer... But, I guess I am able to do a backup using root. But how will this work? How will this help the situation. Could you explain to me friend? (If you are willing to do so of course)
Retr0.Hacker said:
What is EFS? What backup do I do. Cause, I'm a noob and all, and I am not the type of a developer... But, I guess I am able to do a backup using root. But how will this work? How will this help the situation. Could you explain to me friend? (If you are willing to do so of course)
Click to expand...
Click to collapse
Maybe you want to have a look on this thread: https://forum.xda-developers.com/t/...y-are-and-how-to-get-it-back-if-lost.3307793/
EFS stands for Encrypted File System. […]
It contains your IMEI, lots of files revolving around your SIM card and Wifi/Bluetooth (this includes your MAC address for all the radios of your phone), and lots of other things that should never ever under any circumstance be deleted or touched. […]
If you lose your EFS folder, you lose pretty much any chance of your phone being able to use data, Wifi, Bluetooth […].
Click to expand...
Click to collapse
If you had done a backup (e.g. via twrp) prior to rooting you might have also done a backup of that efs partition.
And if you had a backup you could restore that partition. Don't know if you somehow managed to mess this partition up (or if its related at all in your case. Someone with more knowledge hopefully sees your thread) but if you did, there would be no point in backing up that partition now (if its damaged, there is no use to backup a damaged partiton to restore it afterwards).
You can ask me everything you want, don't worry. But I don't know if I'll be able to explain it.
You could try to follow above mentioned guide. If it works, please upvote that guide so others find that helpfull content too.
User699 said:
Maybe you want to have a look on this thread: https://forum.xda-developers.com/t/...y-are-and-how-to-get-it-back-if-lost.3307793/
If you had done a backup (e.g. via twrp) prior to rooting you might have also done a backup of that efs partition.
And if you had a backup you could restore that partition. Don't know if you somehow managed to mess this partition up (or if its related at all in your case. Someone with more knowledge hopefully sees your thread) but if you did, there would be no point in backing up that partition now (if its damaged, there is no use to backup a damaged partiton to restore it afterwards).
You can ask me everything you want, don't worry. But I don't know if I'll be able to explain it.
You could try to follow above mentioned guide. If it works, please upvote that guide so others find that helpfull content too.
Click to expand...
Click to collapse
I did not mess with any partitions. I do not like to mess with my system. I never did. I always made a backup if I had to do something with the system. Before the incident, I never EVER messed with the system. I only started some experiments after the thing happened. I first deleted the whole content of /persist folder (which I restored, because I had a backup), then I deleted .macaddr file inside /persist/wifi folder which actually turned on my WiFi access again, only to f*** things up after doing something stupid, which is to replace wpa_supplicant.conf file inside the /data/misc/wifi folder with one I had with my previously saved WiFi Access Points and their passwords, which resulted to the corrupted MAC address again (02:00:00:00:00:00). No, my WiFi can be scanned successfuly and I am able to connect to it, but still, it does not work properly, because when it connects, it automatically disconnects when I try to use apps like Chrome and Instagram and other apps that need Internet to use. I am currently deleting and re-installing my Factory Image and this will be the last time...
Also, I will attach your URL for sure.
Thanks.
Retr0.Hacker said:
I did not mess with any partitions. I do not like to mess with my system. I never did. I always made a backup if I had to do something with the system. Before the incident, I never EVER messed with the system. I only started some experiments after the thing happened. I first deleted the whole content of /persist folder (which I restored, because I had a backup), then I deleted .macaddr file inside /persist/wifi folder which actually turned on my WiFi access again, only to f*** things up after doing something stupid, which is to replace wpa_supplicant.conf file inside the /data/misc/wifi folder with one I had with my previously saved WiFi Access Points and their passwords, which resulted to the corrupted MAC address again (02:00:00:00:00:00). No, my WiFi can be scanned successfuly and I am able to connect to it, but still, it does not work properly, because when it connects, it automatically disconnects when I try to use apps like Chrome and Instagram and other apps that need Internet to use. I am currently deleting and re-installing my Factory Image and this will be the last time...
Also, I will attach your URL for sure.
Thanks.
Click to expand...
Click to collapse
Another thing which would be helpful:
If your problem is still present you might want to have a look at the logs. That way it's easier to see what causes this behavior.
Code:
adb logcat > log.txt
Run this and try to reproduce the error.
Don't worry about messing with anything. We don't know what happened and sometimes the best of us do things they shouldn't do.
And it seems that also other things (like installing a custom OS) messed with partitions somehow.
But yes, doing a backup prior to modifing is extremly wise – keep up that habit!
I would suggest to try this solution I found:
Aniki43 said:
My Solution {Nexus 5 stuck on "Turning wifi on"}
MY Nexus5 got the same problem today WiFi just stopped working suddenly. The mac got some stupid address like 2.00.00.00. I tried every thing still nothing. I have already rooted my nexus so tried different roms but issue still remains.
Then i just remembered about the ROM UBUNTU Touch i have installed it and WiFi in Ubuntu start working again with original mac address. I am currently using Ubuntu touch and didn't try to reinstall or reset the android rom again.if some one try this and got WiFi working like me please inform me that if the WiFi still works if i reinstall android system.
If you want to download Ubuntu touch download it ubports
Click to expand...
Click to collapse
It is said that the "fix" stays after Android is reinstalled afterwards.
momojuro said:
I would suggest to try this solution I found:
It is said that the "fix" stays after Android is reinstalled afterwards.
Click to expand...
Click to collapse
I saw this thread before. I did not try to flash other OS than the one I use now. I was also thinking downgrading to Android 5.1.1 (because I am currently using 6.0.1 with MOB30H build) and I might try some time.
BTW there is another problem now. I installed a packet from Termux called "macchanger" and I used the packet in order to - what else - change my MAC address. The packet seems to work. It DID change my MAC address and I am now able to scan for local WiFi. But the thing is that every time my I try to connect ti the Internet, WiFi automatically closes, and the randomized MAC address is permanently stuck ( I think, because I can reset it sometimes, but still, it changes back the the one who got randomized first)
I may get a new smartphone for WiFi, calls and stuff and use my Nexus 5 in order to try and find a fix for it. Idk...
So I know there's a method for pairing Wear OS watches running 2.0 through ADB with the Google Wear OS app.
Does the same apply for Galaxy Watch 4 and the Galaxy Wearable App? I really don't want to go through the configuration and sideloading of all these apps again ... That's what I get for trying to do too much with ADB and experimenting .
Not that ive found.....its annoying as hell, i have a ticket in with Samsung over it, Lots of shouting at them for selling me a $500 watch that they then seem to think they can tell me how to use. I havent finished shouting at them by a long shot. Because i test ROM's you can imagine how many hours their bs costs me....
My previous watch the Active 2 was simplish, you just set the Android ID to the same as previous install...
Niether that or the ADB method posted for earlier Wear OS works...
Do you mean this method?
Because if this doesn't work, I have a major problem, since I'm replacing roms quite often.
How to Pair Android Wear Watches to New Phones without Factory Resetting
A tutorial on how to pair Android Wear smartwatches to a new phone without factory resetting. Also useful if you flash a custom ROM and don't want to reset!
www.xda-developers.com
munky-head said:
Do you mean this method?
Because if this doesn't work, I have a major problem, since I'm replacing roms quite often.
How to Pair Android Wear Watches to New Phones without Factory Resetting
A tutorial on how to pair Android Wear smartwatches to a new phone without factory resetting. Also useful if you flash a custom ROM and don't want to reset!
www.xda-developers.com
Click to expand...
Click to collapse
it dosent work ;P
So this is the thing you were referring to. Good to know. I was planning on switching roms over the weekend, but I think I'll wait for a bit now.
munky-head said:
So this is the thing you were referring to. Good to know. I was planning on switching roms over the weekend, but I think I'll wait for a bit now.
Click to expand...
Click to collapse
I doubt Samsung will do something about it ; ) they are out of their mind! For example they block blood pressure on non samsung phone so good that on some samsung phones it doesn't work too and they region lock the watch so when you have a phone from different region you can't connect the watch at least easily
Maybe they think if they block everything on everything they will sell some more blocked **** you know because security!
Yesterday I tried pulling an adb backup (adb backup -all or something) and ended up with a ~60MB file.
Has any of you tried this method for backing up and restoring a backup? Might not save the need to reset and pair again, but can save some time when reinstalling.
Haven't tried it myself, just throwing it out there.
munky-head said:
Yesterday I tried pulling an adb backup (adb backup -all or something) and ended up with a ~60MB file.
Has any of you tried this method for backing up and restoring a backup? Might not save the need to reset and pair again, but can save some time when reinstalling.
Haven't tried it myself, just throwing it out there.
Click to expand...
Click to collapse
How it went in the end? If successfully, can you briefly describe the steps? I'll do my own research based on those, thanks
BigRulaZ said:
How it went in the end? If successfully, can you briefly describe the steps? I'll do my own research based on those, thanks
Click to expand...
Click to collapse
In a nutshell, it didn't work.
I pulled a backup, but no command would restore the apps.
This is so frustrating! I experiment with ROMs and the fact that that I have to start out fresh each time really makes me think of switching back to TicWatch.
munky-head said:
In a nutshell, it didn't work.
I pulled a backup, but no command would restore the apps.
This is so frustrating! I experiment with ROMs and the fact that that I have to start out fresh each time really makes me think of switching back to TicWatch.
Click to expand...
Click to collapse
Speaking of switching back to TicWatch, you're not wrong. The only feature that I will miss would be the ECG capability (which also is broken, no QTc value calculation, etc)
berni502 said:
I doubt Samsung will do something about it ; ) they are out of their mind! For example they block blood pressure on non samsung phone so good that on some samsung phones it doesn't work too and they region lock the watch so when you have a phone from different region you can't connect the watch at least easily
Maybe they think if they block everything on everything they will sell some more blocked **** you know because security!
Click to expand...
Click to collapse
Part of this is that blood pressure has to be approved by different authorities in different places. In the US, the FDA has not approved it.
Also, the stupid resetting thing appears to be a Wear OS 3 issue. Samsung never did that with Tizen. Google seems to have screwed the pooch on this one.
The thing about being unable to pair them once they lose connection is quite a big issue.
My watch and phone has just unpaired a few days ago, and I didn't do any system mods or anything for that to happens. If I try manual pairing with bluetooth it does not work.
I'm not friend of backups, since sometimes that process import some errors among system updates. So I normally do clean installings.
I tried that procedure removing google services via adb and wifi connection but de watch didn't connect in the end. And even if it connected it seems that some apps such as google Pay etc would give problems and would require to be reinstalled again.
On top of that I'm not quite sure but as I have the LTE version I think I will have to ask to my carrier to send me a new e-sim in order to connect the watch again, since I guess they are just one use.
So quite a big problem.
The really crummy part of it all, 1) the annoying tutorial EVERY DAMN TIME. although, as of the latest update (besides a reset a few days ago, oddly enough) it hasn't made me go through it. 2) the wearable app REQUIRING samsung internet (not beta) to be installed and default as browser while signing in and through the entire setup process. these are just to name a few things.