Database Develop

[Q] Bootloops, systemui force closes, and wifi errors after flashing back to stock

I absolutely hate creating yet another thread, but I've tried everything I can and I'm stuck. I was up until 4am (no lie) last night and been at it again for hours tonight. So... here are the symptoms.
Multiple bootloops/reboots at any of the following points:
1) "Preparing device" with the "Please wait" animation.
2) Force close: Unfortunately, Setup has stopped.
3) Force close: process.com.android.systemui has stopped.
4) Force close: Google search has stopped.
5) Bootloop at the bootloader warning message
Usually, the boot animation doesn't even start. Often, I'll see the "Bootloader Unlocked" warning message, then the Moto logo, then it cycles back through any of the above fail points. Sometimes, it'll stay on the bootloader warning message the whole time and then jump directly to the lock screen.
All of this started after unlocking my brand new Moto X Pure Edition and then attempting to use the "Multi-tool" to root. Or...maybe it was after trying to root using one of the Chainfire images. I can't recall. After doing so, wifi stopped working (wouldn't turn on). So, I tried (using the tool again) to flash back to stock. At that point things strange things started happening (force closes). I then tried flashing to stock and immediately flashing the OTA (all via fastboot). When I booted up, Lollipop setup wouldn't load, it'd bootloop, come back and maybe I could get to the next screen, but wifi would be dead. Or I'd get wifi to work, but it'd crash after accepting Google privacy terms.
So, after all of that, I decided I would just revert back to stock. At that point I tried a number of options including what I think is the likely best bet, @SolarTrans guide here. Oh, and somewhere along the line I flashed TWRP 2.8.3 and flashed one of the custom ROMs (LiquidSmooth). It booted, but was very unstable and also threw the same/similar systemui force close messages, occasionally would lose wifi or begin force closing like crazy. Makes me think I have a bigger issue since it happens regardless of ROM/firmware. I also tried graffixnyc's images. So... yeah... just want to get back to stock.
I've been doing this stuff with Android for many years. Not a newbie by any means. Completely comfortable using fastboot or adb command line. I'm just at a loss and feel that it's likely I'll have to send it back to Motorola. I can get into the bootloader no problem. Everything else is a toss up. The last time I flashed files via the SolarTrans guide, it eventually loaded up the home screen (after many bootloops), but wifi wasn't working and I got a strange Moto message about reverting the sensors firmware or update. I rebooted and it never booted again, so I erased cache and userdata via fastboot. That didn't help. I just flashed the original firmware again and it spent a good 20/30 minutes bootlooping before getting to the setup screens. I skipped everything. Then it bootlooped at the home screen.
Open to suggestions!
Edit 1:
Pretty much anything causes the phone to bootloop, but I was able to get a screenshot of the baseband, kernel, build, etc. It bootlooped, but worked the second time around. I think I just made things way worse by trying to turn on bluetooth. It's just bootlooping over and over. Gonna try and get some sleep!

So, before bed, I flashed the OTA from the SolarTrans thread. It booted up, threw some errors and then once I connected to wifi it bootlooped. It did this for at least 10 minutes before I plugged the phone in and went to bed. When I woke up this morning, it was sitting on the setup screen. No errors. I signed in to my Google account and it restored all my apps. I rebooted. Still no problems. Just before leaving for work, I noticed that Dropbox wasn't installed. I installed it, signed in and then it bootlooped. After that...no luck. Kept rebooting. So, I brought the phone to work and left it on my desk for a few hours. It bootlooped or hung on the bootloader unlocked warning screen for at least 3 hours. I wiped cache. Same thing. Just now, I wiped userdata and rebooted. It went through the setup process without errors. Began restoring my apps and then froze. I manually restarted and now... no dice. Bizarre.

mercado79 said:
So, before bed, I flashed the OTA from the SolarTrans thread. It booted up, threw some errors and then once I connected to wifi it bootlooped. It did this for at least 10 minutes before I plugged the phone in and went to bed. When I woke up this morning, it was sitting on the setup screen. No errors. I signed in to my Google account and it restored all my apps. I rebooted. Still no problems. Just before leaving for work, I noticed that Dropbox wasn't installed. I installed it, signed in and then it bootlooped. After that...no luck. Kept rebooting. So, I brought the phone to work and left it on my desk for a few hours. It bootlooped or hung on the bootloader unlocked warning screen for at least 3 hours. I wiped cache. Same thing. Just now, I wiped userdata and rebooted. It went through the setup process without errors. Began restoring my apps and then froze. I manually restarted and now... no dice. Bizarre.
Click to expand...
Click to collapse
So, what was the problem then? The Dropbox app? Why is that?

No. Don't think so. It was just the trigger. I'm convinced any app would have eventually caused the bootloop.
I tried one more clean install of the official image straight from Motorola last night. Same results. So, I've initiated a return/repair.
Sent from my Moto X

Have they accepted repairing your device even with unlocked bootloader and root?
Sent from my XT1097 using XDA Free mobile app

They acknowledged that I'd unlocked the phone (it was logged in the record when they looked up my phone by IMEI), though I said I did so while trying to fix it (in order to wipe partitions and flash images which I also requested via their developer resources page).
They're sending a replacement phone without any push back at all. Honestly, I expected to send it in for repair. The rep said the standard protocol was to issue me a pin to order a new phone (mine is a customized Moto Maker model with a bamboo back).
Just so you're aware, unlocking the bootloader on Pure Edition phones does not void the warranty.
So, a replacement should be in my hands in about a week, I'm told. The phone was still within the initial month and so they're sending a brand new phone.
Sent from my Moto X

Help! Razr i stuck on boot (again)

So here's my story: my phone was JellyBean. I didn't tinker with it, didn't root, just used some launchers. It upgraded to KitKat. I kept using it, even though I liked JellyBean better. Then one month ago it froze and stopped responding even to physical buttons. I managed to restart it, but it wouldn't go past the intel logo. Somehow I got it to go past it and give me like two seconds on before it would freeze and become unresponsive again, so I got to enter safe mode (all following instructions on the internet, which buttons to hold to manage to get into safe mode). Once in safe mode, I deleted every app that had been recently updated or installed, one at a time, trying to turn my phone on each time, until I finally deleted facebook (that enourmous blue monstrosity taking all that internal space), and the phone seemed normal. I re-installed the other apps I had uninstalled, then one day later, it froze again. Now it wouldn't go past the intel logo. Only then I gave up and used RSDLite to re-install the firmware - BUT! The firmware I managed to find was JB, but I had been wanting to downgrade for some time, anyway, so I unlocked the bootloader and flashed JellyBean. And it worked. I was proud. Then one month later, today, it froze again. I can do the same procedure, and lose all my data again, but I fear the problem will remain unsolved and it will freeze/crash/explode one month from now. Can someone help me figure out what my problem is, or give an alternate solution to try?
TL;DR:
my razr i was stuck on the intel logo screen, I unlocked the bootloader and flashed JB, it worked, one month later it is now stuck on the WARNING BOOTLOADER UNLOCKED screen. Please help thank you.

Totally stock phone now totally broken

I like my Sprint M8 and I've avoided messing with it because I'd hate if it got bricked. It got bricked. In my pocket. Somehow. Seriously, I was using it like normal, put it in my pocket for maybe a half hour, then took it back out without having even moved from my seat and it's off. I assumed it somehow died but when I plugged it in it became obvious that wasn't the issue. It doesn't really seem to care what I do with the buttons, but eventually it'll end up in fastboot mode and nothing else. Any of the options just result in a black screen. Sometimes I get a charging screen though. HELP.

Bump

Cwazywazy said:
I like my Sprint M8 and I've avoided messing with it because I'd hate if it got bricked. It got bricked. In my pocket. Somehow. Seriously, I was using it like normal, put it in my pocket for maybe a half hour, then took it back out without having even moved from my seat and it's off. I assumed it somehow died but when I plugged it in it became obvious that wasn't the issue. It doesn't really seem to care what I do with the buttons, but eventually it'll end up in fastboot mode and nothing else. Any of the options just result in a black screen. Sometimes I get a charging screen though. HELP.
Click to expand...
Click to collapse
Destiny oi? maybe you should have really messed with it lol.
But were you able to enter recovery? You could try factory reset from there

jazzdglass said:
Destiny oi? maybe you should have really messed with it lol.
But were you able to enter recovery? You could try factory reset from there
Click to expand...
Click to collapse
Only goes into fastboot. If I try to hit recovery or factory reset, or basically anything that goes outside of fastboot I just get a black screen. I just bought a new phone (Pixel) so it's not a big deal, but I still really like my M8 and if I can fix it I will.

I have run into that a few times with mine and Was ALWAYS able to fix it .
Its just being stubborn. If you have Fastboot you can FIX IT
Is it rooted and bootloader unlocked

Cwazywazy said:
Only goes into fastboot. If I try to hit recovery or factory reset, or basically anything that goes outside of fastboot I just get a black screen. I just bought a new phone (Pixel) so it's not a big deal, but I still really like my M8 and if I can fix it I will.
Click to expand...
Click to collapse
Two case ..
1. SOFTWARE :
First try to RUU . (It will solve nearly all software related issue) . Backup everything as it will wipe all .
If going to flash marshmallow then firstly flash marshmallow firmware and theb RUU.
If problem still there then may b (not sure though) its..(2)
2.HARDWARE :
I have nearly same problem . The device stay at fastboot but can't go to any other option i.e recovery . (After flashing ruu ) , stay ON when only charger connected etc ..
Changed battery and all working fine now.
Your seems to be only software related .. try ruu first
Hit THANKS if somebody help you

sonnu0100 said:
Two case ..
1. SOFTWARE :
First try to RUU . (It will solve nearly all software related issue) . Backup everything as it will wipe all .
If going to flash marshmallow then firstly flash marshmallow firmware and theb RUU.
If problem still there then may b (not sure though) its..(2)
2.HARDWARE :
I have nearly same problem . The device stay at fastboot but can't go to any other option i.e recovery . (After flashing ruu ) , stay ON when only charger connected etc ..
Changed battery and all working fine now.
Your seems to be only software related .. try ruu first
Hit THANKS if somebody help you
Click to expand...
Click to collapse
It's totally stock and unrooted. I tried RUU about a thousand times, every time it gets to the rebooting into fastboot or whatever stage where it times out and fails because the phone takes minutes to turn back on and go into fastboot no matter what I do with the buttons, even if I don't touch them at all. My battery was fine, I think. Still lasted the whole day just fine. Stays on when I disconnect it.

New phone, bricked within 15 minutes!

Hey there fellow OP 3T owners,
I just received my brand new OP 3T and after painstakingly going through the Android / Google setup options, only then could I update the OS.
But it didn't. It bricked my phone within a minute of updating. Buttons and the screen are totally unresponsive.
When connected to my desktop PC, my OP 3T is not recognized. The phone is brand new and was in use only 15-20 minutes before I went for the official software update provided to me by OnePlus.
I just went and opened a service ticket to RMA the phone, though I hope I can somehow avoid this by unbricking the phone.
I don't mind losing all my data, but I hope I will be able to unbrick my phone without going through 12+ steps and using half a dozen unverified 3rd party firmware files?
I just want the official OS back, as I'm content already with Nova Launcher...
*edit* I solved the problem by using the official build OnePlus 3T OxygenOS 4.0.2, "Minimal ADB and Fastboot", the deletion of all other ADB drivers in the Device Manager (such as "LeMobile Android Device" > Android ADB Recovery interface), one restart and otherwise lots of unnerving, long button presses on my OP3T.
Conclusion: This is not what I expected how my first experience with OP would go !!

https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Try out this unbrick process, I've bricked my phone twice (put into bootloop into twrp), this put me back to stock and up and running again.

If you can get to fastboot or recovery, you are not bricked.

SlimJ87D said:
If you can get to fastboot or recovery, you are not bricked.
Click to expand...
Click to collapse
I don't know what that is? I just care about how to be able to recover.
Right now I managed to restart, but it only shows the OP logo and the "powered by android" signage, both in white...

Mine did the same thing after 3 weeks. Couldn't get it to turn on. Sent it back to Oneplus on an RMA, turned out the motherboard was bad. Once I got it back, there hasn't been an issue. Working great now. That might be the your problem.

My phone doesn't turn on at all now meanwhile. I managed to install that Qualcomm driver somehow, but it went downhill from there fast!

I have the exact problem the OP has while trying to upgrade the OS, 100% stock. I downloaded the OTA and tried to install the new OS, but it froze seconds into installing it. Just would not go forward. "ADB devices" doesn't recognize the phone. Was able to get into fastboot but bootloader and firmware are both blank. I did a factory reset, but still nothing. I can see the OnePlus logo when I turn the phone on but that's it. Is there anyway I can push something to the phone to make it work again? Thanks.
https://goo.gl/photos/fCNGtautw2uiEeyq6

The biggest issue I have right now with unbricking my phone is, that I simply do not have "USB debugging" activated, nor anything else, as I never even had the chance to do so, as I unfortunately applied the update right away after my first startup.

Thank you.
Haunt3r said:
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Try out this unbrick process, I've bricked my phone twice (put into bootloop into twrp), this put me back to stock and up and running again.
Click to expand...
Click to collapse
I tried the link you provided and it worked like a charm. I had exactly the same problem as the OP with the phone freezing while doing an OTA update and the ToolKit provided was able to unbrick my phone.
After unbricking the phone, I was able to upgrade the ROM to 7 using OTA with oneplus3toxygen_28_170114, download size was 1434MB.
Thanks.

Warranty..?

Hamiltoe said:
Warranty..?
Click to expand...
Click to collapse
What's it matter? OnePlus customer service is abysmal. The worst customer service I've ever experienced.

HELP! Note 8 stuck in "System Ui Has Stopped" problem!!

Hello. I REALY NEED HELP!! A couple of months ago when oreo got leaked for note 8 I installed it. I installed substratum themes before I did the update when I was still in 7.1.1 . When I installed the leaked oreo I had a problem that it wouldn't let me go past the lock screen unless I quick launched the camera and it said "system ui has stopped" and the phone kept vibrating. I couldn't turn off the phone.. only if I got lucky and then it would take me to a screen that said upload mode. no hard reset combo worked and only download mode combo worked. from there I would put cancel and it restarted the phone. somehow I got the phone to power off and immediately tried the hard reset combo and it worked. I factory reset it and everything went to normal. After that I never had the same issue again. But couple days ago I tried to install substratum to see if it would now work. WELL THAT WAS A HUGE MISTAKE. it was doing the same thing so I managed to factory reset it again. after that I didn't install substratum and everything would work fine until I woke up. when I woke up it kept doing the same thing so I wipped the cache and factory reset it again. Everything worked fine again and then the next morning IT DID THE SAME THING. I've factory reset it like 5 times now and don't have substratum installed at all and that doesn't work. it still says that "system ui has stoped" when I wake up in the mornings. I've been researching A LOT and I've tried to do everything the forums say but nothing works. HOW CAN I GET RID OF THIS SOFTWARE PROBLEM COPMLETLY?. (keep in mind i'm still on the beta software , I never got the official update). I even took it to a Samsung care center for a day and they told me that they couldn't fix it and I called Samsung and they said to ship it in to them so they could fix it. Have you guys been through this?

eze_espinoza said:
Hello. I REALY NEED HELP!! A couple of months ago when oreo got leaked for note 8 I installed it. I installed substratum themes before I did the update when I was still in 7.1.1 . When I installed the leaked oreo I had a problem that it wouldn't let me go past the lock screen unless I quick launched the camera and it said "system ui has stopped" and the phone kept vibrating. I couldn't turn off the phone.. only if I got lucky and then it would take me to a screen that said upload mode. no hard reset combo worked and only download mode combo worked. from there I would put cancel and it restarted the phone. somehow I got the phone to power off and immediately tried the hard reset combo and it worked. I factory reset it and everything went to normal. After that I never had the same issue again. But couple days ago I tried to install substratum to see if it would now work. WELL THAT WAS A HUGE MISTAKE. it was doing the same thing so I managed to factory reset it again. after that I didn't install substratum and everything would work fine until I woke up. when I woke up it kept doing the same thing so I wipped the cache and factory reset it again. Everything worked fine again and then the next morning IT DID THE SAME THING. I've factory reset it like 5 times now and don't have substratum installed at all and that doesn't work. it still says that "system ui has stoped" when I wake up in the mornings. I've been researching A LOT and I've tried to do everything the forums say but nothing works. HOW CAN I GET RID OF THIS SOFTWARE PROBLEM COPMLETLY?. (keep in mind i'm still on the beta software , I never got the official update). I even took it to a Samsung care center for a day and they told me that they couldn't fix it and I called Samsung and they said to ship it in to them so they could fix it. Have you guys been through this?
Click to expand...
Click to collapse
I am by no means on the level of the wonderful gentlemen that so often come to our rescue, but have you tried flashing the device's original firmware?

2Tone23 said:
I am by no means on the level of the wonderful gentlemen that so often come to our rescue, but have you tried flashing the device's original firmware?
Click to expand...
Click to collapse
I haven't successfully done it I can't find the correct software and when I tried it Odin said it failed

eze_espinoza said:
I haven't successfully done it I can't find the correct software and when I tried it Odin said it failed
Click to expand...
Click to collapse
What varient are you?

I have the exact same issue, how is this not talked about anywhere? The leaked beta was so wide spread, I'm assuming you've tried taking it to ubreakifixit? I think that's what it's called.

eze_espinoza said:
Hello. I REALY NEED HELP!! A couple of months ago when oreo got leaked for note 8 I installed it.
Click to expand...
Click to collapse
I think flashing the original firmware is your best option considering you are still on the beta.
Just post the variant you have and the country you're in and I can give you instructions on how to get the right firmware

I would advise that you take your device to a Samsung Service Center and let them take a look at it. As they will be able to help you resolve your issue

eze_espinoza said:
I've factory reset it like 5 times now and don't have substratum installed at all and that doesn't work. it still says that "system ui has stoped" when I wake up in the mornings.
https://youtu.be/zXSHe3oorIM
Click to expand...
Click to collapse
Here is a video about repair Android system issues, maybe helpful with you.