Database Develop

[XT1069] Help with WiFi - Does not activate

Can you guys help me with this issue?
My device is a XT1069 (Moto G - 2nd Gen - Dual SIM with DTV).
It was running stock firmware, with latest OTA update installed.
I had a problem while resetting and flashing my device back to stock firmware.
After facing a bootloop, I tried to flash Andro X (that is designed for XT1068, and not XT1069).
After successfully booting on Andro X, I noticed that my wifi was dead...
It did not activate, nor detect any wifi network.
Later on, I tried formatting every device partition with CWM, and re-flashing stock firmware again, booting successfully this time.
But still, my wifi remains dead!
Note that the wifi is gray, making it impossible to activate:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Below, you can check my kernel and system version:
Does it have anything to do with the kernel or the wifi driver? How can I fix this? Any ideas?
Best regards,

have you tried re-flashing?

barry_ said:
have you tried re-flashing?
Click to expand...
Click to collapse
At least a dozen times!

have you tried different versions of your firmware? I noticed that you have September as your kernel? whereas my 1068 is July.
Also, have you tried installing/wiping via fastboot?
Sent from my XT1068 using XDA Free mobile app

i have the same problem (XT1068)

barry_ said:
have you tried different versions of your firmware? I noticed that you have September as your kernel? whereas my 1068 is July.
Also, have you tried installing/wiping via fastboot?
Sent from my XT1068 using XDA Free mobile app
Click to expand...
Click to collapse
Yeah! I tried flashing and wiping via both fastboot and CWM...
Still, no luck!
PS: Reloading wifi driver by dialing *#*#526#*#* does not work either.
After typing it, nothing shows up...

just had a look at a couple of mentions that have fixed wifi
http://www.appsapk.com/wifi-fixer-app/
Install a Root Explorer (phone must be rooted), go to data\misc\wifi\wpa_supplicant.conf and rename that wpa_supplicant.conf to wpa_supplicant.bak, Restart the phone and see your Wifi Toggle work again.
this might help? http://www.smartmobilephonesolutions.com/content/android-wifi-wont-turn-on

barry_ said:
just had a look at a couple of mentions that have fixed wifi
http://www.appsapk.com/wifi-fixer-app/
Install a Root Explorer (phone must be rooted), go to data\misc\wifi\wpa_supplicant.conf and rename that wpa_supplicant.conf to wpa_supplicant.bak, Restart the phone and see your Wifi Toggle work again.
this might help? http://www.smartmobilephonesolutions.com/content/android-wifi-wont-turn-on
Click to expand...
Click to collapse
Nope... Does not work!
I can't turn it on:

what about the other two suggestions?

barry_ said:
what about the other two suggestions?
Click to expand...
Click to collapse
Tried them all...
wpa_supplicant was empty.
And I've already tried these solutions before as well, with no luck.

you would have to think that it's hardware related then? (although, only happening after a flash would point to software?).
Have you tried different firmwares?

did you tried flashing this firmware instead? (http //sbf.droid-developers.org/download.php?device=36&file=947
Correct the link

barry_ said:
you would have to think that it's hardware related then? (although, only happening after a flash would point to software?).
Have you tried different firmwares?
Click to expand...
Click to collapse
I tried stock firmware (Blur_Version.21.11.18.titan_retbr_dstv.retbr.en.BR), tried Andro X and Stock ROM - XT1069 - KXB21.85-24
None of them fix it...
The problem of my dead wifi happened after flashing and booting Andro X.

the same for me...
MOTO G2 (2nd GEN) XT1068
Android 4.4.4
KXB21.85-23
21.11.23.titan_retaildsds.retaildsdsall.en.03

Also tried to flash Furnace Kernel... It didn't help. Wifi remains dead!
So, I flashed stock boot.img back in.
My kernel is now back to stock... And no wifi!

how feasable is returning your phones for repair/replacement?

barry_ said:
how feasable is returning your phones for repair/replacement?
Click to expand...
Click to collapse
I'll relock the bootloader and give it a try.

maybe an issue with wifi modules? in lib/modules. but i supose that when you flash, everything went back to stock
just guessing, im a noob

Battery percentage showing 3800% after flashing 6.0.1/Root/LK

I just did a no-wipe flash of 6.0.1 and then rooted with NRT and flashed LK (I had it with 6.0 too) and now my battery percentage is messed up. Keeps fluctuating in the 3000s. Any ideas?
http://imgur.com/a/90iUu

I'm having the same problem here, confused

its a bug, ignore it. btw http://forum.xda-developers.com/nexus-6/help/battery-problem-6-0-1-factory-image-t3265899

It's a bug of 6.0.1... Wait for small OTA or 6.0.2

Is it a bug or just an issue with custom kernels? I expect the latter.

simms22 said:
its a bug, ignore it. btw http://forum.xda-developers.com/nexus-6/help/battery-problem-6-0-1-factory-image-t3265899
Click to expand...
Click to collapse
How long do I have to ignore it? What's causing the problem?

Amos91 said:
Is it a bug or just an issue with custom kernels? I expect the latter.
Click to expand...
Click to collapse
It's not a custom kernel - its a fresh factory image install, so stock kernel.
I'd say wait for Google to push an OTA out or another factory image.

Shadester9 said:
How long do I have to ignore it? What's causing the problem?
Click to expand...
Click to collapse
cause, no idea. but i remember the M dev preview had the same issue. some were affected, some werent. id just give it a few run throughs, maybe itll fix itself?

Well, it's not the kernel, since I have the same issue with the stock kernel with 6.0.1 and LeanKernel.

This is just bad.. I can't see how long my battery will actually last
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
http://imgur.com/24jDFHQ

Yeah, I think I'm going back to 6.0. This isn't worth it.

Not only battery status messed up, the Battery tab in setting is missing as well ...

antiquezip said:
Not only battery status messed up, the Battery tab in setting is missing as well ...
Click to expand...
Click to collapse
Yeah, I accessed mine by tapping the battery icon in quick settings.
Really odd for a bug like this to go unnoticed by Google.

No issues here on a clean install (including partition trims in TWRP) of 6.0.1.

Face_Plant said:
No issues here on a clean install (including partition trims in TWRP) of 6.0.1.
Click to expand...
Click to collapse
Nice! Mines still saying 3925% battery.. Mine was a fresh install from the Google dev images. Full wipe too..

MarkPH123 said:
Nice! Mines still saying 3925% battery.. Mine was a fresh install from the Google dev images. Full wipe too..
Click to expand...
Click to collapse
That's strange. Wiping everything (including internal storage) and doing a partition trim in TWRP before flashing the image fixed it for me. Are you rooted? Custom kernel?

Face_Plant said:
That's strange. Wiping everything (including internal storage) and doing a partition trim in TWRP before flashing the image fixed it for me. Are you rooted? Custom kernel?
Click to expand...
Click to collapse
Ah I see, I was rooted beforehand but wiped everything for a clean slate.
So still stock recovery, stock kernel and no root.
Might have a go at TWRP partition trimming tomorrow when I've got some time to do it.

My battery indication shows 100%, did a clean install and no issues whatsover.

gee2012 said:
My battery indication shows 100%, did a clean install and no issues whatsover.
Click to expand...
Click to collapse
This is odd.
I did use NRT's 'Stock & Unroot' option.
It may have missed the kernel so I'll extract that and try flashing different parts of Android to see if I get any sense out of it or some sort of fix, or Google may figure it out before me (hopefully )

Shadester9 said:
I just did a no-wipe flash of 6.0.1 and then rooted with NRT and flashed LK (I had it with 6.0 too) and now my battery percentage is messed up. Keeps fluctuating in the 3000s. Any ideas?
http://imgur.com/a/90iUu
Click to expand...
Click to collapse
Congratulations man! You're battery should last a whole month without charging!!! Suh-weeeet!

OP3T Constant awake?

My device is constantly awake on the current build after doing a full clean flash (twice).
Something in the system is holding awake after the screen is off.
So I've tried stock OOS and CM13, and I am still getting the same wakelock so that means it is not ROM dependent, something else changed within my phone that is causing this wakelock.
I first started noticing this wakelock when I tried the offical ResurrectionRemix 7.1 from here, after flashing that ROM, I've had the wakelock on all other roms. Anyone have any ideas about how to solve this?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

check with better battery stats app and post Screenshots

ForcedZucchini said:
My device is constantly awake on the current build after doing a full clean flash (twice).
Something in the system is holding awake after the screen is off.
So I've tried stock OOS and CM13, and I am still getting the same wakelock so that means it is not ROM dependent, something else changed within my phone that is causing this wakelock.
I first started noticing this wakelock when I tried the offical ResurrectionRemix 7.1 from here, after flashing that ROM, I've had the wakelock on all other roms. Anyone have any ideas about how to solve this?
Click to expand...
Click to collapse
Take it off the charger.
Sent from my OnePlus 3T using XDA Labs

Try the wakelock detector app
Sent from my ONEPLUS A3000 using Tapatalk

Attaching some wakelock screenshots. These also show that it is off the charger.

Id format everything in twrp after saving anything valuable. Then I'd install a ROM without flashing Google apps. I wouldn't even login or sign-in or install a single app after booting up. Then see if the issue is still present. If it is gone then you know it's either your apps or Google but not the ROM or phone.

954wrecker said:
Id format everything in twrp after saving anything valuable. Then I'd install a ROM without flashing Google apps. I wouldn't even login or sign-in or install a single app after booting up. Then see if the issue is still present. If it is gone then you know it's either your apps or Google but not the ROM or phone.
Click to expand...
Click to collapse
So here is what I've tried so far:
I installed stock OOS Recovery over TWRP. Through the stock recovery I sideloaded the official OOS 4.0 Nougat release and wiped the phone clean through recovery selecting the option (Erase everything (pics, vids, etc.)). I then rebooted the phone and completed set-up by skipping everything and no google sign in. I am still getting the constant wake issue.
I also noticed the following kernel wakelocks that show 99% and 69% usage respectively:
1. fusb301_otg_wl
2. 6a00000.ssusb
I found these threads around the wakelocks above.
https://forum.xda-developers.com/showthread.php?p=68634552#post68634552
^ This one suggests clearing cache on Play Services, I tried this and still not working.
https://forum.xda-developers.com/oneplus-3/help/otg-wakelock-problem-t3511310
https://forum.xda-developers.com/oneplus-3/help/6a00000-ssusb-wakelock-wld-bbs-t3463062

Just wanted to update in case anyone else has this problem. I have fixed the issue.
I flashed 3.5.4 OOS and then proceeded to install CM13. I am no longer experiencing constant wake on CM or OOS.

ForcedZucchini said:
Just wanted to update in case anyone else has this problem. I have fixed the issue.
I flashed 3.5.4 OOS and then proceeded to install CM13. I am no longer experiencing constant wake on CM or OOS.
Click to expand...
Click to collapse
Will try this. Hopefully this helps.

The problem has actually reappeared for me on OOS. Still not sure what is causing it...
Screenshot attached is me currently running OOS Nougat beta.

I've got already the same problem
ForcedZucchini said:
The problem has actually reappeared for me on OOS. Still not sure what is causing it...
Screenshot attached is me currently running OOS Nougat beta.
Click to expand...
Click to collapse
Did you solve the problem? I'm bored with this new phone. Thanks

What version of stock rom do you use?

Hello everyone, I got few questions.
As the title says, which version of stock rom do you use? Does it have any issues, are you rooted or not, green camera even with TA keys provisioned? Asking because, while I was following tutorial I couldn't pull out TA-unlocked.img, it said that file doesn't exist. I pulled entire /data/local/tmp folder and it showed 3 renoroot files and one "g+fffffffffffffff+fffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff" file which is 12kb in size. I have green camera in Oreo, so Oreo is no go for me. Looking for decent stock Pie version, because latest one has touchscreen issues, it becomes unusable for 5-6 seconds and then works and stops working. Also, someone mind directing me to which TWRP should I use for PIE to install Magisk and other things, would be really nice. Any help is wellcome.

The last pie stock "2.2.8 should not have touchscreen issues, or any other firmware. If you have issues, and you still have warranty, try to send it it. Sony, in my opinion, is notorious for their touchscreen issues. I experienced touchscreen issues on z3 compact and z5 compact EOL. I suspect the same will happen with xz1 compact, unfortunately. However I am on my 3rd original screen repair/replacement , so hopefully it will last a bit longer this time.

mcmanuf said:
The last pie stock "2.2.8 should not have touchscreen issues, or any other firmware. If you have issues, and you still have warranty, try to send it it. Sony, in my opinion, is notorious for their touchscreen issues. I experienced touchscreen issues on z3 compact and z5 compact EOL. I suspect the same will happen with xz1 compact, unfortunately. However I am on my 3rd original screen repair/replacement , so hopefully it will last a bit longer this time.
Click to expand...
Click to collapse
Phone is not under warranty, so that is out of question, also don't want to lose waterproofing. This touchscreen issue happens only on Pie, currently I can find only latest pie and latest LineageOS, who aswell have that issue, while no issue occurs on stock Oreo, besides green camera.

Frano35 said:
Asking because, while I was following tutorial I couldn't pull out TA-unlocked.img
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
adb pull /data/local/tmp/TA-locked.img
Have you done a full wipe when installing the latest ROM? I've updated 3 times to Pie and come back to Oreo within hours due to certain issues so you may live to regret not following the guide properly.

SXUsr said:
adb pull /data/local/tmp/TA-locked.img
Have you done a full wipe when installing the latest ROM? I've updated 3 times to Pie and come back to Oreo within hours due to certain issues so you may live to regret not following the guide properly.
Click to expand...
Click to collapse
I did as the guide said, and I have done it all on Oreo. I have pulled TA-Locked.img and later it said to pull TA-Unlocked.img and push TA-Locked.img. I tried pulling out entire tmp folder but it had only renoroot files and weirdly named one. Then I pushed back locked img and did rest as guide says. I have attest key provisioned but not SOMC Fido and SOMC Attest. Any idea if I can still fix it?

Frano35 said:
Any idea if I can still fix it?
Click to expand...
Click to collapse
If you still have your TA-Locked.img then yes, the unlocked one is for "(for future comparisons)".
Start from scratch with the guide and redo the restoration of the locked TA img. If it doesn't work you're doing something wrong.

SXUsr said:
If you still have your TA-Locked.img then yes, the unlocked one is for "(for future comparisons)".
Start from scratch with the guide and redo the restoration of the locked TA img. If it doesn't work you're doing something wrong.
Click to expand...
Click to collapse
Do I need to flash back to Oreo or I can do it from LOS16?

Frano35 said:
Do I need to flash back to Oreo or I can do it from LOS16?
Click to expand...
Click to collapse
You tell me.

Question Xiaomi Developers are MORONS !!! - Do not update Framework Services

Hi All,
So it appears my phone has now died, and I am guessing it's the same issue that's affecting everyone in this thread....
I believe my issues occurred when I updated the Framework Services.
So DO NOT UPDATE FRAMEWORK SERVICES if you get the notification....
- Xiaomi staff/developers if you browse these forums, let it be known YOU ARE MORONS !!!
Please reply back to all of us, whose phones you've now broke and data potentially LOST !!!!
Anyone with a working phone, can you check the file name that is associated with Framework Services. And will see if I can uninstall/pull the file with ADB commands in Fastboot. As Fastboot is the only system that is stable at the moment...
Cheers, Lister

Hi All,
Ok, I might be getting somewhere with this....
So the package name is : com.xiaomi.xmsf
And here the offending/good versions.... Things all went a bit Pete Tong when upgrading to 6.0.5, before that things were rosey....
So, I've managed to sideload 5.4.2 via ADB commands, and it said Success.... I can now see my old desktop/icon layout, and not the basic/safemode version that been stuck in.
But things are still far from stable...
Xiaomi, if you're still reading.... you're still MORONs.... Where can I bill you for wasted time ??
Lister
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Lister Of Smeg said:
Hi All,
Ok, I might be getting somewhere with this....
So the package name is : com.xiaomi.xmsf
And here the offending/good versions.... Things all went a bit Pete Tong when upgrading to 6.0.5, before that things were rosey....
So, I've managed to sideload 5.4.2 via ADB commands, and it said Success.... I can now see my old desktop/icon layout, and not the basic/safemode version that been stuck in.
But things are still far from stable...
Xiaomi, if you're still reading.... you're still MORONs.... Where can I bill you for wasted time ??
Lister
View attachment 5754977
Click to expand...
Click to collapse
How did you do it? I can't enable USB Debugging, the phone restarts before I can even click OK...

Lister Of Smeg said:
Hi All,
Ok, I might be getting somewhere with this....
So the package name is : com.xiaomi.xmsf
And here the offending/good versions.... Things all went a bit Pete Tong when upgrading to 6.0.5, before that things were rosey....
So, I've managed to sideload 5.4.2 via ADB commands, and it said Success.... I can now see my old desktop/icon layout, and not the basic/safemode version that been stuck in.
But things are still far from stable...
Xiaomi, if you're still reading.... you're still MORONs.... Where can I bill you for wasted time ??
Lister
View attachment 5754977
Click to expand...
Click to collapse
Well, I managed to uninstall the Xiaomi service framework from my phone and it isn't broken, it just reboots like before...

AdonysGames said:
Well, I managed to uninstall the Xiaomi service framework from my phone and it isn't broken, it just reboots like before...
Click to expand...
Click to collapse
Yeah same.... I already had USB Debugging on from the start. I removed the corrupt version, even forced the old original version back on. But yeah, the same... keeps rebooting.
I am hoping Xiaomi MORONs will release another version of Framework Service that restores any of the corrupt builds out, god knows there's a few now.
This update SUCKS.... I have a feeling gonna have to say goodbye data...
Xiaomi = The Brand that don't give a fook...
Lister

Hmmm that's a strange one , I'm on 13.0.13.0 UK version . Looked through the updates and these are what I have...
6.0.6-g version was updated the end of September

bernardblacksbookshop said:
Hmmm that's a strange one , I'm on 13.0.13.0 UK version . Looked through the updates and these are what I have...
6.0.6-g version was updated the end of September
View attachment 5756467View attachment 5756469
Click to expand...
Click to collapse
We now know the bug is caused by Qualcomm's location process, so yeah makes sense

glad i didnt update anything beside the os

bernardblacksbookshop said:
Hmmm that's a strange one , I'm on 13.0.13.0 UK version . Looked through the updates and these are what I have...
6.0.6-g version was updated the end of September
View attachment 5756467View attachment 5756469
Click to expand...
Click to collapse
Hi BernardBlackBookshop,
Yeah, I only assumed it was the Xiaomi Framework Services... as up until that point, I hadn't installed anything else new. I too am on the same version as you, I've not received any notification yet to upgrade to A12.
The X F S was the last thing I installed, and was at 6.0.5 when I installed, so assumed that at the time. We was all trying to do anything/everything to get our devices back alive. The 6.0.5 came out 2x days before I applied the update, and died the following day without any other changes.
I see that X F S is now upto 6.0.8, which updated too... and no side effects yet. <pheeeew>
So glad @AdonysGames found the solution that day, as I was very close to wiping my phone and all the data with it...
Cheers, Lister