Last weekend I flashed the most recent CM 11 version and the Pico GApps package (from here). The phone has worked perfectly since then, very fast, no issues at all.
This morning when I turned it on I immediately saw 'Android is Upgrading' and 'optimizing __ of 42 apps.' I have all auto-updates and syncs disabled, and this is the first time this has happened.
When the phone finished booting, it told me that Chrome and my email app and AV crashed. Opening any user app results in the app crashing immediately.
I tried rebooting, same result, same Upgrading message.
I rebooted to recovery and cleaned the cache and Dalvik cache. This time I see 'Android is Upgrading' and 'optimizing __ of 132 apps.' When it finished booting, same thing - a few apps crash immediately, all other user apps crash when opening.
What's happened to my phone? I'm new at this, it's getting frustrating. I don't know why it was upgrading anything to start with...
I can't open any apps to look at Root Explorer, etc., can someone please tell me should I just reflash the CM 11? Do I need to flash the stock ROM first? I don't know what to do next. This is still new for me.
Basically I've had it working before but now I can't log in no matter what i do. I'm going viperrom 5.0.2 and have had no trouble for months with uninstalling xposed framework if I accidentally logout of snapchat. But this morning I randomly was logged out (happened to my friend on apple aswell) and I can't log in even if I factory reset . I've tried completely wiping my phone and re-installing the rom. I got into a fresh rom and unrooted with supersu and rebooted but my Wi-Fi wouldn't turn on. But snapchat would login so I assumed if was definitely root that was messing it up. So I did a fresh install again and unrooted and for Wi-Fi worked. But snapchat didn't work.
So at this point I have tried everything I can think of to make snapchat login. I've tried countless other snapchat apks. And even tried a blue stacks titanium recovery but it auto logs out as soon as you get in the app.
Please somebody help me
me too any solution??
Hi. My S6 has been running great for a while. It's running CleanROM. I got a notification that there is an update to SuperSU. I chose to update it normally because there's no recovery since the bootloader is locked. During the upgrade, I got a message saying that Knox was detected and if I wanted to disable it (temporarily?). I chose Never not thinking about the implications. The phone rebooted as part of the upgrade but now it is stuck in a bootloop. It does boot up for a very short time. Enough time for me to draw my security pattern and for some apps to load, but then the phone reboots. Any idea what's going on? Any suggestions on recovering from this? Thanks.
UPDATE: Somehow I recovered. I was able to power down the S6 because I had that small window to do so. I booted to Safe Mode and disabled SuperSU. I rebooted normally and everything was ok except SuperSU was disabled. I uninstalled SuperSU Pro and then uninstalled all updates for SuperSU. Play Store wouldn't let me totally uninstall it. I updated SuperSU. This is where it gets a little foggy. I think I re-enabled SuperSU and then it said that Knox was detected and whether to try to disable it or never disable it. This time I chose to disable Knox. SuperSU tried to disable Knox but got stuck with the spinning arrow. It was strange because I was able to go to Settings, but when I went to Apps or Logs, I got a continuous spinning arrow. It seemed to do what was needed though because my root checker verified I was rooted again. I rebooted again and ran SuperSU again. It gave me the Knox detected message again. This time I said Never disable. Rebooted one more time, ran SuperSU and no more message. Last step was to reinstall SuperSU Pro. I am not sure exactly if I had to do all these steps and what exactly was going on, but I think I am back to normal running SuperSU Pro v2.79.
I am running stock ROM and have bootloader unlocked and TWRP already installed. The phone was rooted without problems. I was getting an error from Super SU, so I looked up how to fix it online and the suggestion was to install an older version and then try to upgrade it. It was hard to find a zip from a legitimate source but once I found it, TWRP did not show the directory I was looking for (this was previously available when I rooted it). This is where I did something stupid and looked around in the settings and found the Slot A / Slot B option. I switched from B to A and the phone got stuck on the boot animation for several minutes after rebooting. I decided to reboot into TWRP and switched the slot back to B. This brought the phone back but WiFi is off by default and whenever I try to turn it on, it doesn't change.
I have seen a couple of other people mention similar issues about losing wifi after a root or changing the slot. What's the fix? I am wondering if there is anything else "broken" after the slot change and if I should do a factory reset (I would hate to do that as I was almost finished setting up this device). I have also received the error message saying "Process System isn't responding" in the settings menu a few times. It also seems like the finger print scanner isn't recognizing fingerprints any more and face unlock isn't working
One possibility is, that SuperSU isn't that compatible anymore. Magisk does a wonderful job and no problems so far. Maybe you should give it a try and switch from using SuperSU to Magisk.
shagexpert said:
I am running stock ROM and have bootloader unlocked and TWRP already installed. The phone was rooted without problems. I was getting an error from Super SU, so I looked up how to fix it online and the suggestion was to install an older version and then try to upgrade it. It was hard to find a zip from a legitimate source but once I found it, TWRP did not show the directory I was looking for (this was previously available when I rooted it). This is where I did something stupid and looked around in the settings and found the Slot A / Slot B option. I switched from B to A and the phone got stuck on the boot animation for several minutes after rebooting. I decided to reboot into TWRP and switched the slot back to B. This brought the phone back but WiFi is off by default and whenever I try to turn it on, it doesn't change.
I have seen a couple of other people mention similar issues about losing wifi after a root or changing the slot. What's the fix? I am wondering if there is anything else "broken" after the slot change and if I should do a factory reset (I would hate to do that as I was almost finished setting up this device). I have also received the error message saying "Process System isn't responding" in the settings menu a few times. It also seems like the finger print scanner isn't recognizing fingerprints any more and face unlock isn't working
Click to expand...
Click to collapse
I had the same issue when I first got my 6 when I was playing around with the slots. Also my original TWRP install for some reason would crash and reboot whenever I plugged in the data cable while in TWRP. I ended up flashing back to stock OOS 5.1.5 through fastboot (used the flash-all command) and then reinstalled TWRP and everything has been working great since then.
MickyFoley said:
One possibility is, that SuperSU isn't that compatible anymore. Magisk does a wonderful job and no problems so far. Maybe you should give it a try and switch from using SuperSU to Magisk.
Click to expand...
Click to collapse
The instructions I followed already installed Magisk to the phone. I wanted Super SU because some of the other chainfire apps like Liveboot and rooted apps like Titanium backup said Super SU is needed (Titanium said Magisk will work but may not be reliable for some newer versions of the ROM). I can live without liveboot but really need Titanium to reliably transfer data from my older phone.
To be honest I didn't know they did the same thing (magisk and Super SU). I am curious now, what if I factory reset my phone and attempted to install Super SU instead of Magisk this time?
If I do a factory reset (let's say I want it just like it was out of the box and I format the data partition as well), will I need to root the phone again? I am asking because I don't know which part of the instructions I should ignore. I am sure TWRP will already be installed after the reset so I would only need to install the extra apps...
You don't have to format data. Just factory reset it. Then use "fastboot boot twrp.img", don't allow modifications, flash a kernel you want (if you want one - I really recommend ElementalX) and then the latest version of Magisk (16.4 BETA currently). Did so - all fine. And yes: Even Titanium Backup works without any issue with Magisk.
We had similar problems with TWRP on the Razer Phone when it was new. We solved the problem by using the TWRP boot image to flash the stock boot image and then flashing a TWRP zip. I just got the OnePlus 6 yesterday and haven't really messed with it yet but everything sounds the same to me so far.
I read more about TWRP and realized what I was doing wrong when the directory with zip files wasn't showing up. When TWRP showed up I was supposed type in my regular unlock password to decrypt storage. When I did that the folder I was looking for showed up. I made a backup through recovery (which took like an hour, may be because the external flash drive I attached was really slow - and the size of the backup was about 12GB). After that I installed the zip file for Super SU, just to see if it worked - it showed the installation was successful but the app was still missing from the app drawer. Now I wanted to factory reset the device and start over.
I went into wipe and there was nothing listed under the wipe screen. I went into Advanced wipe and wiped whatever was selected by default. The selected items were Dalvik / ART Cache, System, Data. There was also "Internal Storage and USB Storage" that wasn't selected.
I swiped to wipe, it wiped everything. Then asked reboot, I rebooted, got a blank screen with white LED for a long time. When I plugged it into the computer it recognized the device as Qualcomm HS-USB Diagnostics 900E (COM4). I rebooted it by holding Power + Volume Up + Volume Down. I tried to boot into boot loader next. This brought me to another blank screen. The computer still makes a noise when it reboots but screen stays black. The only message that shows up is the one saying boot loader is unlocked. Did I brick my phone? This keeps getting progressively worse.
shagexpert said:
I read more about TWRP and realized what I was doing wrong when the directory with zip files wasn't showing up. When TWRP showed up I was supposed type in my regular unlock password to decrypt storage. When I did that the folder I was looking for showed up. I made a backup through recovery (which took like an hour, may be because the external flash drive I attached was really slow - and the size of the backup was about 12GB). After that I installed the zip file for Super SU, just to see if it worked - it showed the installation was successful but the app was still missing from the app drawer. Now I wanted to factory reset the device and start over.
I went into wipe and there was nothing listed under the wipe screen. I went into Advanced wipe and wiped whatever was selected by default. The selected items were Dalvik / ART Cache, System, Data. There was also "Internal Storage and USB Storage" that wasn't selected.
I swiped to wipe, it wiped everything. Then asked reboot, I rebooted, got a blank screen with white LED for a long time. When I plugged it into the computer it recognized the device as Qualcomm HS-USB Diagnostics 900E (COM4). I rebooted it by holding Power + Volume Up + Volume Down. I tried to boot into boot loader next. This brought me to another blank screen. The computer still makes a noise when it reboots but screen stays black. The only message that shows up is the one saying boot loader is unlocked. Did I brick my phone? This keeps getting progressively worse.
Click to expand...
Click to collapse
OK good news! I tried one more time and fast boot showed up. I was able to get into recovery. I have the backup so I will try to restore that. I don't know what to do after that. I am thinking wiping without getting into advanced mode.
shagexpert said:
OK good news! I tried one more time and fast boot showed up. I was able to get into recovery. I have the backup so I will try to restore that. I don't know what to do after that. I am thinking wiping without getting into advanced mode.
Click to expand...
Click to collapse
When your phone booted straight into that mode with black screen and the led, then you bricked it. Same happened to me 2 days ago. The solution was to use the Msmtool from another thread and it worked great. Just follow the guide. But it will wipe your device. And you have to install oxygenos manually via "local upgrade". If you have a question, just ask
What I ended up doing was restoring from the backup I had. This was the "bad backup" without WiFi and broken finger print and facial recognition. After the restore, I did a normal wipe (not advanced). This reset the phone to factory settings. Once I configured WiFi and signed into my Google account, Google offered to recover from a cloud backup of my One Plus - I didn't know Google made these backups. It downloaded all the apps automatically. I don't know yet if I have sign into all of them all over again.
The bad back up saved my ass, I wasn't even planning on making it. I was just testing the backup feature. That's why you should always do a backup, even if the device isn't in ideal configuration.
shagexpert said:
The instructions I followed already installed Magisk to the phone. I wanted Super SU because some of the other chainfire apps like Liveboot and rooted apps like Titanium backup said Super SU is needed (Titanium said Magisk will work but may not be reliable for some newer versions of the ROM). I can live without liveboot but really need Titanium to reliably transfer data from my older phone.
Click to expand...
Click to collapse
I rooted my phone with Magisk and installed the 5.1.6 via OTA (and reroot via installed Magisk Manager). So no need to install TWRP so far.
Titanium Backup runs flawlessly with Magisk (already on my OP 3T and my OP 5).
So give Magisk a try, I never had such an easy and reliable update as the one from 5.1.5 to 5.1.6
Helium is a great alternative to titanium.
So summary
OOS 9
Magisk 19
Disabled I think is quickswitcher module
Now I just get animation going forever on booting, if I leave it long enough about 20 minutes or so, it reboots itself and goes back to loop.
TWRP is accessible.
I tried MM recovery tool in core only mode but still doesnt boot.
Ideally I need a solution that doesnt involve a factory reset.
Ok the core only mode didnt stick I think, so did it again and the phone is booted.
With no phone app , completely gone off the phone.
It shuts down after about 20 seconds after booting up.
Backing up what I can over USB from TWRP, and this might force me to migrate to my Oneplus 8 pro which has been sitting in its box, but I will still appreciate any input on how to get this running again without a reset so I can properly migrate app settings etc even if its losing magisk.
I managed to keep the phone bpoooted up for ages, and have done things like titanium backups, app setting backups etc.
I then tried to reinstall the phone app from the play store but got a vague "cannot install phone from google".
But at least now I can access settings etc. Take screenshots of settings also. So better baseline for the new phone.
Pretty crazy how all this broke so easily though.
So I dont know how this happened but I managed to recover the phone.
The xXx rom magisk module got wiped when I deactivated the recents module, this removed the google dialer framework and some build.prop changes the rom module puts on the phone.
I initially just added the framework magisk module which allowed the google phone app to reinstall, all my call logs were intact. But the phone was still unstable on booting so had to reinstall xXx which seems to have fixed that, albeit now with added lag.
But I have backed up everything now anyway so will migrate to my newer phone its long overdue, but this post is here now in case anyone else has the same issue.