Database Info

Stuck on lockscreen - androidui has stopped

Moto G 16GB, bought off Amazon.co.uk. Rooted and flashed 4.4.2 before it was pushed to the device (I think it was an image off US version, found it in these forums back when I got the phone). I've been getting a prompt to install some Motorola US update for a few weeks, it pops up every now and then, has gone away when I tapped "No, thanks" option. All was fine until this morning...this is a really weird problem.
I don't know if the phone updated itself overnight, but when I dismissed the alarm this morning I couldn't get past the lockscreen. I put in my lock code and the phone had the stock wallpaper, then cycled to black background, then back to stock wallpaper and then I got a pop up saying "Unfortunately, the process com.android.systemui has stopped." and I was bumped back to the PIN lockscreen. Tried again, same thing. Now it doesn't even say anything about androidui, just cycles between black background and stock wallpaper and kicks me out.
Tried hooking it up to a PC and Mac, but neither recognized it and the phone appeared to be just charging. Power cycled it a dozen times by holding down the power button for about 6 seconds and I always end up with the same problem of not getting past the lockscreen. Every time I boot the phone now it says "Android is upgrading... Optimizing app 1 of 1". This is why I thought maybe I was pushed some incompatible US update?
Underneath it all the phone works fine, got the alarm this morning, received an SMS, answered a phone call. I can even get to the camera from the lockscreen. Is there any other options besides complete wipe and starting from the beginning again?
Probably OT, but I've always had trouble with the launcher quitting, no matter what launcher I'm using, on Moto G and the previous GNex.
Any help is appreciated, I'm bummed.

Hi,
i've today the same, exactly the same problem. It's strange, because i can't reset my phone to factory default, i went to the recovery menu, then "factory", but it only rebooted...
My "solution":
I reinstalled the original firmware:
http://forum.xda-developers.com/showthread.php?t=2542219
Then all works fine.. No matter why this error occurs.. an automatic firmware update? ..i don't know...

the exact same thing happened to me today out of nowhere and i'm about to leave on a trip, i'm so angry!

Jeez...well, looks like I'm not the only one. WTF happened? I left on a weekend trip too and I'm P.O.'d. I haven't been too religious with my backups either, that's why I was trying to find a way to back things up before wiping it all, but it looks like I'm out of luck. Guess a full wipe is in order.

hmmm i'm a complete dufus when it requires ADB, i've followed the procedures at the link but everytime i try to enter an input cmd says "mfastboot is not a recognized command"
electrictimes said:
Jeez...well, looks like I'm not the only one. WTF happened? I left on a weekend trip too and I'm P.O.'d. I haven't been too religious with my backups either, that's why I was trying to find a way to back things up before wiping it all, but it looks like I'm out of luck. Guess a full wipe is in order.
Click to expand...
Click to collapse
my phone wasn't even rooted, pure stock kitkat, i'm taking my heavy ass old notebook with me and will spend my days off trying to fix this **** it seems

a.monteiro said:
hmmm i'm a complete dufus when it requires ADB, i've followed the procedures at the link but everytime i try to enter an input cmd says "mfastboot is not a recognized command"
Click to expand...
Click to collapse
Take a look:
c) If the firmware file you downloaded is a .xml.zip file then download Motorola Fastboot mfastboot-v2.zip (attached to this post) and extract the .exe into the same folder as the stock firmware files (the same folder as the .bin and .img files). If your firmware is a .tar.gz file then skip this step.

I'm debating if I should go ahead and restore the firmware OR wait for Motorola to right their wrongs!

a.monteiro said:
the exact same thing happened to me today out of nowhere and i'm about to leave on a trip, i'm so angry!
Click to expand...
Click to collapse
Same situation....

ifishy said:
Take a look:
c) If the firmware file you downloaded is a .xml.zip file then download Motorola Fastboot mfastboot-v2.zip (attached to this post) and extract the .exe into the same folder as the stock firmware files (the same folder as the .bin and .img files). If your firmware is a .tar.gz file then skip this step.
Click to expand...
Click to collapse
I... did that, but obviously not the correct way, i'm downloading the files on my note and will try again. Maybe I should unpack the firmware files at some specific place? The instructions said nothing about this so I did nothing.
zofari said:
I'm debating if I should go ahead and restore the firmware OR wait for Motorola to right their wrongs!
Click to expand...
Click to collapse
Just reminded me that my phone is still within warranty, doing this restore may void it?

a.monteiro said:
I... did that, but obviously not the correct way, i'm downloading the files on my note and will try again. Maybe I should unpack the firmware files at some specific place? The instructions said nothing about this so I did nothing.
Just reminded me that my phone is still within warranty, doing this restore may void it?
Click to expand...
Click to collapse
My phone is back working..at the cost of wiping out all my data.

zofari said:
My phone is back working..at the cost of wiping out all my data.
Click to expand...
Click to collapse
Guess this is the only way out of this, then. What a mystery... I wonder if this is the "Welcome to Lenovo" update 1.0 lol.

i'm getting a "missing AdbWinApi.dll" although i've installed all the applications required, any help?
edit: guess i also need the android sdk, right?
edit2: got it, just copy the dlls from the minimal adb directory into the firmware directory and it's good to go, just configuring my newly restored device, thanks all

I wonder why this happened? I was using google play store at the moment, updating the flipboard app...

a.monteiro said:
I wonder why this happened? I was using google play store at the moment, updating the flipboard app...
Click to expand...
Click to collapse
I guess It's the problem of flipboard app!

My father's phone is also experiencing this issue, I can't even reset the phone to factory settings.
This occurred when I was also updating the flipboard app... seriously I'll have to RMA this...
----------------------
So I also have an issue where when you unlock the screen, it just locks back up (no android dialogue saying that com.android.systemui has crashed, but the same result).
I'm also unable to go into bootloader -> Recovery to factory reset the phone.
I stupidly tried to uninstall the flipboard app and reinstall it and it killed the phone... it's now stuck and quite annoying.
I'm 99% sure it's Flipboard.

Looks like others are having issues with Flipboard too
http://forums.androidcentral.com/moto-g/391289-something-seriously-wrong-my-moto-g.html
----------------
I solved the issue by following the instructions here:
https://motorola-global-portal.custhelp.com/app/answers/prod_answer_detail/a_id/97329/p/30,6720,9050

how could a flipboard update screw android so badly? what a strange day
edit: they seemed to have pulled the update back or fixed it though, during my restore flipboard installed without issues

Holy S*** I'm in the same situation. It's definitely the Flipboard update that caused everything. Support just acknowledged me but never gave me any solution. I'm running ART and I think that was contributing the problem. It's terrifying knowing how a single app can completely ruin your phone!!
Anyway guys, is there anyway I can save my pics and stuff before I wipe my data?

Good detective work, I now remember updating the Flipboard app w/ bunch of others as well when things were still all good. Could this be remedied if Flipboard would manage to push a working update? I really don't wanna wipe everything, and I'm not sure I can.

Word from Flipboard (via Twitter):
"Flipboard does not support the experimental OS ART at this time."

OnePlus One Malfunction? Help please

G'day people I've run into something pretty weird with my OnePlus One. I installed the CM12 nightly and booted it up, ran it for a few hours then got ghost touches and the screen became unresponsive at times.
So, having my usual backup of CM11S, I wiped and restored to the latest backup I had and everything was weird. I kept getting ghost touches and reduced responsiveness, and sometimes it would just randomly malfunction and not unlock and just keep the screen off.
Rebooting clears up the problem for about 5 minutes and then it comes back at full blast.
I tried installing the last CM11S update via flashing Calkunins stock XNPH44S zip and still I have all these weird issues that wasn't there before I flashed the CM12 nightly.
Has anyone come across this problem or is it just me and my device? It's seriously a cause for concern, and I'm posting this to both XDA and the OnePlus forums in hopes of getting some sort of help and relief in this situation.
Any assistance is appreciated and I thank you in advance for taking the time to read this.

reflash cm12 nightly and try again.
perhaps use fastboot to flash the partitions .
You might need to find a copy of the first cm11s rom and try that one. I have a feeling your one of the unlucky with firmware sensitivity.
Which date is your phone from? (its on the box)
Sent from my A0001 using XDA Free mobile app

GO back to completely factory fresh, via fastboot commands.
If you still have problems, it's a hardware issue then.

kthejoker20 said:
GO back to completely factory fresh, via fastboot commands.
If you still have problems, it's a hardware issue then.
Click to expand...
Click to collapse
not entirely true, there are different screens, that could be the issue. It was reported in boeffla kernel thread. sesrch throught it and it might contain something useful to try.
also open a support question, Oneplus needs to know how annoying their poor choice of different lcds are
Sent from my A0001 using XDA Free mobile app

bachera said:
reflash cm12 nightly and try again.
perhaps use fastboot to flash the partitions .
You might need to find a copy of the first cm11s rom and try that one. I have a feeling your one of the unlucky with firmware sensitivity.
Which date is your phone from? (its on the box)
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
I'll try to flash CM11S via fastboot to see if it clears up the issue. For now, the date I got mine is 2014-07-16. Shipped to me after 12 days (International shipment via courier)

UPDATE
Flashing CM11S via fastboot resolved all issues as far as I can tell.
Will remain on the lookout for the bugs in the future but for now I'm happy to say it worked for me.
Thank you all again for the advice and guidance, it was appreciated.

GLad it worked for you.
I love when other posters try to punk you when you try to help people.

kthejoker20 said:
GLad it worked for you.
I love when other posters try to punk you when you try to help people.
Click to expand...
Click to collapse
Nobody was trying to "punk" you. There are usually several different potential causes for the same symptom, all he was doing was highlighting that and adding extra information in order to help further (in the case that flashing the stock images didn't help, which has happened many times). He was also trying top help the OP. Calm down.
Transmitted via Bacon

timmaaa said:
Nobody was trying to "punk" you. There are usually several different potential causes for the same symptom, all he was doing was highlighting that and adding extra information in order to help further (in the case that flashing the stock images didn't help, which has happened many times). He was also trying top help the OP. Calm down.
Transmitted via Bacon
Click to expand...
Click to collapse
I thought it was the partition thing too because I had almost the same problem on my HTC Amaze back in 2014, and flashing the OEM RUU helped with sorting things out.
But as for the random screen touches, flashing everything from fastboot helped for only a few hours. The symptoms came back after a while, specifically when I replaced my music and pictures. I'm thinking that I may have a corrupted file on it somewhere but I doubt it'll cause a malfunction like that.
So I tried flashing Franco Kernel, and it seems to have cleared it up..... for now.
It's so frustrating thinking that my device may be defective

UPDATE #2
Flashing Franco Kernel didn't help. Symptoms came back within a couple hours. Will try a custom ROM, specifically AOPK (because I want to )
If that doesn't fix the issue then I've just got to face the fact that I have a defective device (somehow)

Bump
Nothing worked. I contacted the manufacturer but they seem to think doing a factory reset will help. It didn't.
Flashing CM11S via fastboot doesn't help
I really think this is a hardware issue that just emerged from nowhere, probably due to lack of premium or standardized quality adhesive.
There's a really long thread over at the OnePlus forums about a guy who found it was a grounding issue and took some adhesive tape to insulate the area near the proximity sensor (I think? I'll include the link in here somewhere)
Honestly, OnePlus impressed me....at first. But I cannot use a phone that's not working properly.
https://forums.oneplus.net/threads/...-hint-it-was-never-a-software-problem.186235/

Same problem here... I had the first ghost touches after having installed CM12 Nightly.
I was using CM12 built by Daleski75 so far without any issue. The problem does not appear on a regular basis and when it does, a reboot seems to fix it, at least for a few minutes/hours.
I'll try a clean install when the stable version is out (don't really want to wipe now and once more in two/three weeks).
@rdar_93: Did you find a solution? Are you going to send the device back to OnePlus? If it is actually a hardware issue, that will be enough for me, no more OPO. Sending the device back to China after 2 months of use and having to pay for the shipping is not acceptable.
Edit: It's getting worse... I am gonna wipe soon. Here is a short video: drive.google.com/file/d/0B-EYHGTB15_wS1JXdXlmZXVsT0k/view?usp=sharing
I can't post link for now so you'll have to copy and paste it in your browser.
Edit2: After a full wipe and the installation of the latest nightly, the situation seems to be better, even though I will have to use the phone a bit more to see if it happens again. By the way, I lost dt2w and the gestures don't work well, if not at all... When I draw a V, nothing happens, when I draw a circle, the phone behaves as if I did a double tap. Weird. Again, this happens after a wipe+latest nightly installation+wipe again (to be sure ).

sylvain15250 said:
Same problem here... I had the first ghost touches after having installed CM12 Nightly.
I was using CM12 built by Daleski75 so far without any issue. The problem does not appear on a regular basis and when it does, a reboot seems to fix it, at least for a few minutes/hours.
I'll try a clean install when the stable version is out (don't really want to wipe now and once more in two/three weeks).
@rdar_93: Did you find a solution? Are you going to send the device back to OnePlus? If it is actually a hardware issue, that will be enough for me, no more OPO. Sending the device back to China after 2 months of use and having to pay for the shipping is not acceptable.
Edit: It's getting worse... I am gonna wipe soon. Here is a short video: drive.google.com/file/d/0B-EYHGTB15_wS1JXdXlmZXVsT0k/view?usp=sharing
I can't post link for now so you'll have to copy and paste it in your browser.
Edit2: After a full wipe and the installation of the latest nightly, the situation seems to be better, even though I will have to use the phone a bit more to see if it happens again. By the way, I lost dt2w and the gestures don't work well, if not at all... When I draw a V, nothing happens, when I draw a circle, the phone behaves as if I did a double tap. Weird. Again, this happens after a wipe+latest nightly installation+wipe again (to be sure ).
Click to expand...
Click to collapse
I contacted them and they sent me a program to use. It uses fastboot to flash CM11S and probably fix the partitions that are messed up (I'm making an assumption)
UNFORTUNATELY I'm stuck in a bootloop.
I'm so angry, disappointed and depressed at the same time. I paid about $2500 TTD (in my country) which is probably the equivalent to somebody's rent. I had to work a month to save up the money to buy this and it turns out that the device is faulty after a certain amount of time (or at least mine was)
This is BS.
They said to send them a snapshot of what went on with the fastboot thing, so I figure I"ll upload it here too.

rdar_93 said:
I contacted them and they sent me a program to use. It uses fastboot to flash CM11S and probably fix the partitions that are messed up (I'm making an assumption)
UNFORTUNATELY I'm stuck in a bootloop.
I'm so angry, disappointed and depressed at the same time. I paid about $2500 TTD (in my country) which is probably the equivalent to somebody's rent. I had to work a month to save up the money to buy this and it turns out that the device is faulty after a certain amount of time (or at least mine was)
This is BS.
They said to send them a snapshot of what went on with the fastboot thing, so I figure I"ll upload it here too.
Click to expand...
Click to collapse
I guess you didnt unlock bootloader first
Which when you do wipes the phone so you loose all your stuff.
possible workaround is fasboot on custom recovery and then flash the zip that sets unlock status and circumvents the whole format thing
Sent from my A0001 using XDA Free mobile app

bachera said:
I guess you didnt unlock bootloader first
Which when you do wipes the phone so you loose all your stuff.
possible workaround is fasboot on custom recovery and then flash the zip that sets unlock status and circumvents the whole format thing
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
I actually did unlock my bootloader.
PS I also got tired of seeing CM11S try to boot up so I flashed ColorOS (because it's the only rom I had on my laptop. Why not download another 4.4.x AOSP rom? Unstable wifi at school)
So yeah, wifi is not turning on. Gonna try the program again. I wonder if it would work this time?
The conditions aren't as different as before, could work, right?
Honestly I want to wait but they take so long to reply.

UPDATE
After flashing ColorOS I decided to go back and try doing the CM11S via fastboot commands. Still got a bootloop but hey I got the correct fastboot logo now in case if it made a difference.
So I did the compulsory flashing commands when I went from Color to CM11S and still bootlooped.
So I booted into fastboot again
fastboot oem unlock (supposed to unlock bootloader and reboot if it's locked, no reboot if unlocked [assumption])
then rebooted into fastboot again, ran the batch files OnePlus sent to me which essentially flashed CM11S just like you would over fastboot, but with added modems etc.
Successfully booted into CM11S without issues, WiFi works again and so far no symptoms as yet.
Will keep this post updated if anything happens.
My screenshots of the batch file commands OnePlus sent would be found in the attachments.

UPDATE 2
So I think it's fixed permanently this time.
I'm not sure though. It hasn't done anything weird. I will copy my music and photos to see if that would cause anything to happen

I would stay away from os since it messes up partition and people ran into data drop out and modem issues.
Cm11s Roms are the way to go on this hardware.

FYI, when you flash CM12 the radio is overwritten with an alpha/beta radio which causes (well, caused for me) THE EXACT issues OP was having in CM11/S. The CM12 radio (as far as I can tell) ONLY works with CM12 - making going back a PITA.
If you have the baseband in this thread (see screenshot in first post) then that means you are on the experimental radio and are going to have a bad time if you aren't on CM12.
I flashed the latest OTA radio found here and all was right with the world (at least where my OPO was concerned ).

hp13 said:
I would stay away from os since it messes up partition and people ran into data drop out and modem issues.
Cm11s Roms are the way to go on this hardware.
Click to expand...
Click to collapse
I would like to go back to CM11s to check if the situation is better. I tried to flash the lastest CM12 build and it seems to be better but still not as good as before
When I do a wipe and then flash the ROM in TWRP, there are some "folder already up to date", which I would like to avoid. What I would like to do is doing a complete clean install of either CM12 or CM11s plus rewriting the partitions,... So that I'm sure if the problem is still here it is due to an hardware issue.
Is there any chance someone can help me with this? Even with a link... I searched for "write partition" without any luck :-/
Thanks !
EDIT: Do you think the OnePlusRecovery Tool can help me with this?

TWRP Flipped Touchscreen Input Left-Right(Horizontally) HELP!

Hi, I recently downloaded Flashify and the TWRP img and used it. However, when I booted the .img into Flashify, my touchscreens input (the action when you tap your phone screen), not the touchscreen orientation. The Input has flipped left-right or horizontally. So lets say there are 4 apps on the dock. If i clicked the 1st one, I get the 4th. 2nd = 3rd, 3rd = 2nd, and 4th = 1st.
Please tell me how to fix this. If there is an easy way like using build.pro to somehow flip the touchscreens input because the hwrotation=180 only changed the orientation.
Any help is appreciated, thank you.
I have rebooted, Settings>Restore, Cleared cache dav cache internal storage, advanced clean through recovery

Reflash with stock 5.1.1 ROM via odin.

Can't Ive been trying. It keeps getting stuck at "Complete(Write) operation failed"
I used Odin successfully before this to update to 5.1.1 from 5.0.2
It's also recognizing my S6 as the S6 Edge
I Dl'd the driver already
Should I also be using the G920TUVU1AOCG_G920TTMB1AOCG_G920TUVU1AOCG_HOME.tar or the G920TUVUCOF6-20150615115627.tar?

Okay it finally worked. It didnt fix it and it removed my root. So even worse than before.

phongle123 said:
Okay it finally worked. It didnt fix it and it removed my root. So even worse than before.
Click to expand...
Click to collapse
Look here http://forum.xda-developers.com/showthread.php?t=3167666
I believe this will help. It'll tell you how to manually fix it and also how to get the correct version of twrp for your phone

drock212 said:
Look here http://forum.xda-developers.com/showthread.php?t=3167666
I believe this will help. It'll tell you how to manually fix it and also how to get the correct version of twrp for your phone
Click to expand...
Click to collapse
HAHAHHAHAHA!!! I looked at the one that said T-Mobile and instantly clicked it instead of actually looking at the name. It WAS indeed for the Edge, the left - right inverse does not happen anymore. This isn't fixed with a reflash or reboot or changing to correct TWRP. You need to refix it in phone>*#2663#
EDIT: To any others that have this happen. Even if you fix it with the phone>*#2663#, if you go back into the EDGE Variant TWRP it will make it back to left - right inverse. You need to change it to the right TWRP variant first otherwise going back to the wrong TWRP will mess it up again.
Thanks for that, I overlooked it.

Recovered from boot loop but constant crashes with older ROM

I am helping a friend to get his One Plus One 64GB to work again after an OTA update broke it.
Initial Problem
Two days ago she started an OTA update which made the phone reboot constantly before even android started. Basically it showed the logo for about 6s then vibrated and restarted again. I later found /o/Android/data/com.cyngn.fota/cache/cm-12.0-YNG1TAS17L-bacon-signed.zip so I assume that this was what was installed.
The phone is completely untouched otherwise. She has no computer knowledge whatsoever and says she didn't give it to anyone.
My attempt
I was able to install cm-11.0-XNPH33R-bacon-signed.zip and cm-11.0-XNPH22R-bacon-signed.zip via sideloading. The phone started ok but was crashing all the time. I am not able to get into settings to activate developer settings (adb) because the crash notifications hinder navigation and after about 10s the whole gui crashes and I see the black screen with the hexagon loading logo. The latter firmware is worse meaning it crashes at a higher frequency.
The Problem
She didn't expect any problems and does not have a backup of her data. Thus I can't do a factory reset or use fastboot.
Question
Did I use the wrong ROM? There seem to be many variants. I haven't found any information which explains the differences.
Could I maybe flash a minimal ROM that would not crash to backup the data and than do a factory reset?
Is there any way to activate adb access without having to navigate to settings?

I've experienced your issues as well when helping another friend out, try using a newer version of cm11s, something like 44S /44R (i dont remember what it is) or 05Q, those should not have the issue and everything should work fine

Jst flash a newer modem in recovery

mugoftee said:
I am helping a friend to get his One Plus One 64GB to work again after an OTA update broke it.
Initial Problem
Two days ago she started an OTA update which made the phone reboot constantly before even android started. Basically it showed the logo for about 6s then vibrated and restarted again. I later found /o/Android/data/com.cyngn.fota/cache/cm-12.0-YNG1TAS17L-bacon-signed.zip so I assume that this was what was installed.
The phone is completely untouched otherwise. She has no computer knowledge whatsoever and says she didn't give it to anyone.
My attempt
I was able to install cm-11.0-XNPH33R-bacon-signed.zip and cm-11.0-XNPH22R-bacon-signed.zip via sideloading. The phone started ok but was crashing all the time. I am not able to get into settings to activate developer settings (adb) because the crash notifications hinder navigation and after about 10s the whole gui crashes and I see the black screen with the hexagon loading logo. The latter firmware is worse meaning it crashes at a higher frequency.
The Problem
She didn't expect any problems and does not have a backup of her data. Thus I can't do a factory reset or use fastboot.
Question
Did I use the wrong ROM? There seem to be many variants. I haven't found any information which explains the differences.
Could I maybe flash a minimal ROM that would not crash to backup the data and than do a factory reset?
Is there any way to activate adb access without having to navigate to settings?
Click to expand...
Click to collapse
The problem here is that you flashed an older build, going backwards like that is what's causing the crashes. Grab the latest build from here:
https://www.androidfilehost.com/?fid=24052804347802356
Flash that and hopefully you'll be ok.

PivotMasterNM said:
I've experienced your issues as well when helping another friend out, try using a newer version of cm11s, something like 44S /44R (i dont remember what it is) or 05Q, those should not have the issue and everything should work fine
Click to expand...
Click to collapse
That won't help, flashing an older build than what was previously installed without wiping properly will cause problems.
KURDKiNG said:
Jst flash a newer modem in recovery
Click to expand...
Click to collapse
Modem has nothing to do with this.

Well mines did like it was at lockscreen and wen i tried to unlock it rebooted so i jst flash a modem and booted fine

KURDKiNG said:
Well mines did like it was at lockscreen and wen i tried to unlock it rebooted so i jst flash a modem and booted fine
Click to expand...
Click to collapse
Most likely pure coincidence.

Thanks your reply!
Heisenberg said:
The problem here is that you flashed an older build, going backwards like that is what's causing the crashes. Grab the latest build from here:
https://www.androidfilehost.com/?fid=24052804347802356
Flash that and hopefully you'll be ok.
Click to expand...
Click to collapse
Actually this is what I did in the very first beginning but I encountered the same rebooting symptoms like after the OTA update. Since it didn't seem to change anything I didn't mention it. I used cm-12.1-YOG4PAS1N0-bacon-signed.

Any other ideas? I am about to unlock it with fastboot but really would prefer not to delete all user data.

mugoftee said:
Any other ideas? I am about to unlock it with fastboot but really would prefer not to delete all user data.
Click to expand...
Click to collapse
I don't think you have any other option unfortunately.

Question Help ! No wifi and bluetooth scanning

Hi friends,
Since yesterday, my wifi and bluetooth don't work anymore. When enabling them, it scans nothing . I've made a factory reser without any psuccess !
Never seen an issue like this on any phone...
Thanks for your help guys

Have you tried restarting the phone? I had 1 time yesteday too, suddenly, the phone was idle, and when I checked Wifi found nothing. Restarted and then it works again. Not sure if related to March update or some other stuffs

creezalird said:
Have you tried restarting the phone? I had 1 time yesteday too, suddenly, the phone was idle, and when I checked Wifi found nothing. Restarted and then it works again. Not sure if related to March update or some other stuffs
Click to expand...
Click to collapse
Restarted and also factory reseted

YassGo said:
Restarted and also factory reseted
Click to expand...
Click to collapse
Wow...after a factory reset, that's pretty much it!
You can try doing the reset network settings button (you can search it in the search bar in Settings or find it in the Internet setting on top right button [wrench and reset circle]), but I can't imagine it doing better than a factory reset.
The best/last thing that can be suggested, since it states you are rooted in your sig, is to flash the latest Full Factory image (March) and/or with the "-w" intact (since you stated that you did a factory reset so I imagine your phone is wiped anyways) and see if that doesn't fix the issue. The best 3 methods to achieve this is using the online Android Flash Tool, the tool PixelFlasher that can be found here on XDA, or manually using platform-tools (you must've used one of these in the past to be rooted, so I assume you're familiar).
Hopefully you get it figured out. Worst case, the phone is still under manufacturer's warranty and you should be able to get it replaced with a refurbished if it truly isn't resolved...

simplepinoi177 said:
Wow...after a factory reset, that's pretty much it!
You can try doing the reset network settings button (you can search it in the search bar in Settings or find it in the Internet setting on top right button [wrench and reset circle]), but I can't imagine it doing better than a factory reset.
The best/last thing that can be suggested, since it states you are rooted in your sig, is to flash the latest Full Factory image (March) and/or with the "-w" intact (since you stated that you did a factory reset so I imagine your phone is wiped anyways) and see if that doesn't fix the issue. The best 3 methods to achieve this is using the online Android Flash Tool, the tool PixelFlasher that can be found here on XDA, or manually using platform-tools (you must've used one of these in the past to be rooted, so I assume you're familiar).
Hopefully you get it figured out. Worst case, the phone is still under manufacturer's warranty and you should be able to get it replaced with a refurbished if it truly isn't resolved...
Click to expand...
Click to collapse
Yesterday I dirty flashed March update bmand disabled verity stuff. It forced me to format data. Is it enough or is there a better clean flash way ?
Btw I tried the reset network thing without success

YassGo said:
Hi friends,
Since yesterday, my wifi and bluetooth don't work anymore. When enabling them, it scans nothing . I've made a factory reser without any psuccess !
Never seen an issue like this on any phone...
Thanks for your help guys
Click to expand...
Click to collapse
YassGo said:
Yesterday I dirty flashed March update bmand disabled verity stuff. It forced me to format data. Is it enough or is there a better clean flash way ?
Btw I tried the reset network thing without success
Click to expand...
Click to collapse
Mmmm...when you stated you "factory reset", it wasn't clear whether it was from the OS system setting or when flashing...
I don't think there is a "better clean" way to flash and/or reset the phone. If you're not flashing/sideloading OTA (which you aren't)...
It (reset network) was a very long shot, but worth exploring just in case it hadn't been tried yet...
I mean, I guess you can try Android Flash Tool and even go as far as to flash to both slots and relock bootloader to get a pure, stock status and see if the problem truly sticks that way. You've already wiped the phone, so I doubt this could hurt or you lose anything important at this point. But I can't imagine dirty flashing the latest March update (or even including disabling the verity stuff) wouldnt've addressed or reset things to set the issue straight...
If it's still there after relocking the bootloader and flashing to both slots, then it's warranty exchange time (if you ever want to resolve the issue)...
*most likely the flashing somehow wrecked the system board radio enough...
If/When this works, you'll need go through the trouble of unlocking the bootloader, and reflashing the Full Factory image with disabling the verity & validation stuff, before rooting again.

Ok I think it's a hardware problem. When I shake my phone, I hear something moving.
I dropped it from my bed saturday night. The wifi module must be disconnected.
Let's send it to Google....

YassGo said:
Ok I think it's a hardware problem. When I shake my phone, I hear something moving.
I dropped it from my bed saturday night. The wifi module must be disconnected.
Let's send it to Google....
Click to expand...
Click to collapse
Are you sure that what you are hearing move when you shake the phone is just the OIS for the camera? All phones with OIS will make some noise when you shake them.

jaseman said:
Are you sure that what you are hearing move when you shake the phone is just the OIS for the camera? All phones with OIS will make some noise when you shake them.
Click to expand...
Click to collapse
I don't know my friend. Google will send me the return process tomorrow. They told me 7 to 10 days for repairing. Why did I sell my old oneplus ?

YassGo said:
I don't know my friend. Google will send me the return process tomorrow. They told me 7 to 10 days for repairing. Why did I sell my old oneplus ?
Click to expand...
Click to collapse
I have had several OnePlus phones and they have all been great for me! However, I am having no problems with my 7 Pro either so....YMMV