com.android.phone crashing and restarting phone - OnePlus 6T Questions & Answers

moving to android 10, but installed update 9.0.17 with the settings app and magisk messed up something since the device after a twrp install boots with everything working other than the crashing.
I've wiped the cache for the install, tried out installing via twrp (with backups this time) and wipeing the phone cache (the phone boots fine just have to tap close and only have a few presses before a restart) but cant confirm the storage clear menu due to the crashing.
I'm currently trying to move over a magisk uninstaller but is there a way to remove the storage or uninstall and continue with an android 10 installation?

yep magisk uninstall and reinstall worked

Related

Urgent Help. Somethings

Here I Go
I was on CM11 Snapshot. Then I went to install Lollypop from http://forum.xda-developers.com/nexus-4/development/rom-aosp-build-t2929544. So I go on TWRP and wipe Dalvik Cache, Cache, Internal Storage and System. Then after, I noticed that everything was gone. So I sideload the ROM and my Gaaps. Something went wrong and old system apps like Dialer and Camera were installed and caused problems with the Newer apps and the system. I Wipe again....this time making sure to wipe data. I sideload but....the gaaps did not install. I went into Recover and noticed that TWRP was uninstalled and everytime I installed it VIA Fastboot, it worked but only for the Timebeing. Sideloading was not working and when I tried downloading the GAAPS straight from the browser, it was unsuccessful. Also, everything that I tried to download via browser did not work. Then I connected it to my Computer as an MTP. This was not working either.
Please Help and Thank You

Android cannot boot

Hi. It's my first post so sorry for all mistakes I'll do.
I had stock Android 5.1.1 installed with root. I decided to install Xposed. I did everything right but I couldn't install the package. When I rebooted my tablet I had a bootloop. I installed "uninstall" package and it booted well. I tried to install it again but still the same error, but this time "uninstall" package didn't anything. Bootloop again. I did factory reset, cache and dalvik reset but still the same problem. I tried to connect it to my PC and to install another OS (Chroma) but my PC didn't find it. Mount USB storage option in advanced in CWM does not work. Please, help me
Thanks

[Q] Stuck at boot animation after flashing SuperSU 2.46 in recovery (CM13)

So I completely wiped my Nexus 4 yesterday (everything but internal storage) and clean-installed the 12/29 CM13 nightly + nano Gapps. Everything was working great, installed a bunch of apps from Google Play, etc.
Then this morning I booted to recovery and installed SuperSU 2.46 via recovery zip flash (not via the app), which appeared to flash successfully/with no errors (plus I now see a supersu directory at the root level of my device).
I then rebooted and got stuck at the boot animation. Went back to recovery, wiped dalvik cache and regular cache, rebooted, and I'm still stuck at the boot animation. Reflashed the zip and then wipes dalvik/cache, still stuck.
Any ideas on (a) how to fix without rewiping-reflashing, and (b) how to get root on CM13? Thanks!
EDIT: Forgot to mention my bootloader is unlocked and I have TWRP recovery.
EDIT2: Appears to be solved. I simply deleted the "/supersu" directory in the TWRP file manager and it now boots fine. Unsure if it screwed up hidden stuff, but I didn't have to wipe my system partition, which is a win in my book.
You don't need SuperSU on CM since it has root acces integrated, you just need to enable it under developer options. Format system, cache/dalvik and reflash cm13 and gapps.
Well ****. Looks like I needed to use the newer beta versions of "systemless" SuperSU, like 2.56 or 2.61 for Android 6/CM13.
I wasn't aware that installing 2.46 would cause me to get stuck at bootup, though! That sucks. Still looking for a solution.
Ah I wasn't aware of that. Thanks!
I deleted the /supersu directory, reflashed the 12/29 nightly, wiped caches, and the phone got past the boot animation and booted normally. I'll reboot a few times and see if things are OK.
Saved me from having to format system yet again and redo everything.
Install 2.56b Beta thats working coz it uses systemless ROOT
Do not install 2.56b , because you won't be able to install 2.60+ supersu after that without reflashing system. Install 2.65 beta. It's stable and tested on cm13. I use it myself.
Thank you so much for this - I flashed 2.46 on cm13 on my motog3. I thought I'd lose all my data since I have device encryption and an external sd formatted as internal storage (which is unsupported in twrp for the moto3g, so it isn't accessible for backing up).
I just reflashed the rom and cleared cache and it's back to normal, encryption was fine, all my data is here, and the external sd card functions as well. Saved my ass.
I tried this and it didn't work. I installed supersu while on CM13 and it got stuck at the boot animation of CM. I deleted the /supersu directory reflashed the newest nighlty rom and wiped caches but still stuck at boot animation. I'm on TWRP btw
Doesn't cm13 have an option to enable root under developer settings?

Cleared cache, now phone doesn't boot and goes to recovery

A friend just cleared cache and dalvik cache from TWRP on his OP5 and now when the phone turns on, it shows the spinning OOS boot screen and after about 30 seconds it starts the recovery.
We tried flashing the ROM again but it didn't change a thing. We tried flashing it from the stock recovery but clicking "Install from internal storage" didn't work and ADB sideloading is not possible.
I'm running out of ideas.
Try doing adb sideload from linux instead of windows. You can also choose to load the rom from a pendrive using otg.
just flash twrp again, flash oos, boot. might ask for a password, at that point you will restart back to recovery (will be oos recovery now) and just select you dont know the password and it will wipe your phone and then turn on. then go back and reinstall twrp again.
my guess is he accidentally clicked clear system, clearing cache doesnt break anything. clearing system on oos breaks it and you have to start fresh. that or install a custom rom.... but oos is better, so id spend the time and just do it right.

Phone goes back to TWRP after re-installing rom

Hey, a few days ago i fked up again.
I was on the rooted global 10.3.9 rom (which is not the latest global version).
I got daily notifications to update to MIUI 11 but they were annoying and there was no way to disable those notifications. So i deleted the system updater app on titaniumbackup, also freezed the system APP updater and system app config or something.
Then I rebooted but it didn't boot system, it went to twrp instead (russian version).
So i figured i had to re-install the rom that was already on it to get the deleted system updater apps back. Dirty flashed it, but it booted into twrp again. And that's where I'm at now.
I don't want to factory reset because i forgot to back up my whatsapp chats...
Any solutions?
I still have all my personal data btw.

Categories

Resources