Related
Ok i know the fourm is somewhat littered with these posts, and i've tried to do as much myself as i can.
Last night my phone offered the KitKat OTA update.
Its a Nexus 4, with unlocked bootloader, TWRP recovery and root, but no system modifications.
I accepted the update, thinking that it would simply update to kitkat and lose my root. On rebooting to install, the phone launched TWRP by itself, and TWRP ran the update, it went thru various stages of patching things before getting to a step saying something about permissions, where it stopped with an error.
I rebooted the phone and ended up stuck at the new 4.4 boot animation.
I went back into TWRP and tried clearing the caches, and also using the "fix permissions" option but still it hung at the boot animation.
So needing to get the phone working, with minimal data loss, i downloaded the 4.3 stock image, and flashed the boot and system files on in fastboot mode. Hoping to get the phone rolled back to 4.3 where it was before.
Partial Success, in so far as the phone booted, but things are somewhat "weird".
Some data has vanished, such as my call log, and my SMS inbox. Other data seems fine, such as my email client, my wifi settings, google login info, backgrounds etc. But on top of that there are weird quirks, for instance if i swipe down the notification bar, the settings button doesnt work, and i think notifications arent actually showing up either. Similarly, the home button is broken and does nothing. And even more strangely the keyboard appears to be missing!
I'm thinking we're probably at the stage of having to flash a complete factory image, and at least the phones booted so i can pull off my images and things. I'm somewhat pissed about my SMS as i didnt even think of backing them up because it was an OTA update and i assumed it would Just Work.
Any thoughts on what has happened here?
Regards
Kevin
ok, so i decided to reflash 4.4, and things are still weird.
Same faults as before, no keyboard, no notifications etc etc.
I did fastboot update image image-occam-krt16s.zip, but that doesnt seem to have erased by Apps etc.
I presume i'm going to have to do a full wipe with -w switch and start from scratch?
Same case, mi phone only works with 4.3. Download the 4.3 image, and only flash boot and system, dont flash userdata.
Try flashing the images and making it wipe your device so you don't have any data left. (AKA Clean flash, you did a dirty flash)
ok, so i decided to reflash 4.4, and things are still weird.
Same faults as before, no keyboard, no notifications etc etc.
I did fastboot update image image-occam-krt16s.zip, but that doesnt seem to have erased by Apps etc.
I presume i'm going to have to do a full wipe with -w switch and start from scratch?
Aragorn84 said:
ok, so i decided to reflash 4.4, and things are still weird.
Same faults as before, no keyboard, no notifications etc etc.
I did fastboot update image image-occam-krt16s.zip, but that doesnt seem to have erased by Apps etc.
I presume i'm going to have to do a full wipe with -w switch and start from scratch?
Click to expand...
Click to collapse
Yes you do. A clean flash is a full wipe.
Yeh that sorted it, Sorry about the double post above, i tried to edit it but it wouldnt let me.
I copied my images off and did a full wipe and now its working again.
It seems like the forum is littered with these messages, but no-one seems to know the actual cause? I presume its somehow related to the modified recovery not applying the update properly?
This is on two standard Galaxy S5's, with standard ROM, etc - not rooted, or anything else.
Every time I turn off WiFi, or enable Mobile Hotspot, I get 'Unfortunately System UI has stopped'.
To fix I have to Power off/on the phone.
(Turning on WiFi is no problem, just turning it off.)
I have gone into 'Safe Mode', and same issue, so it looks to not be a bad App.
I have also uninstalled 'Google' updates, and again no change...
Any thoughts?
All of a sudden my S5 showed the exact same error message for no aparent reason... I didn't do anything, and now I can't use my phone at all because of that bug. It happens on every boot so I can't even unlock my phone. Tried reinstalling everything, ROM, recovery, kernel, with/without root = still same, what just happened here??
EDIT: Same thing if I'm in Safe Mode -_-
Seeing noone knows a solution here's what I did yesterday.
1. Backed up all my stuff from internal storage to the sd card
2. Did factory reset in TWRP recovery
3. Flashed completely stock official firmware from Samsung
4. Waited for it to boot up and try to restore some of my settings (it restored all folders on their places, made same amount of home screens as I had before the reinstall and downloaded all of my previously installed apps from the Play Store, ofcourse without the cracked ones, and it also restored most apps' data as well so it's not as bad as you may think to factory reset and reinstall everything)
5. Started rooting, flashing TWRP again, installing Dolby Audio, Xposed and everything I had before, took me one full day to set it up as it was before.
Now when I set it up I always make a nandroid backup from when things are working fine, in case it goes crazy for no reason again... Good luck!
when the wifi radio is acting weird, a dirty flash of your current ROM susually fixes is as its probably a radio issue. Id do that before doing anything drastic like the boot-n-nuke Odin flash and starting from scratch (which will fix that issue)
I don't think I have a ROM issue, as I have two S5's, and both have the same issue... and both are standard ROMs.
I will do a factory re-set on one at some point, but this looks to be a 'simpler' issue.
I have tried a full Cache delete, as well as other 'clean' processes.
Nothing works.
I tried to re-flash my stock ROM as @youdoofus said but still had that annoying popup. Try everything you can think of, if all else fails, reset.
koragg97 said:
I tried to re-flash my stock ROM as @youdoofus said but still had that annoying popup. Try everything you can think of, if all else fails, reset.
Click to expand...
Click to collapse
well, you can wipe cache, and dalvik 3x each (not kidding about the 3x each), then dirty flash the rom, pray to the gods of android, reboot. If failure occurs, its Odin Nuke time unless you want to try to flash an individual radio file by itself (not recommended)
TL;DR O was janky after dirty flash so downgraded but now N isn't right even after super wiping everything and reflashing stock N image.
Ok so I have no idea why I decided to try out O with all the dumb bugs that are being reported and the lack of a simple night light enabler but I did anyway. Phone was working great on 7.1.2, had the night light and blue pixel accents, the round icons actually just showed up for me which I like better than all the craziness of 5 different shaped icons cluttering up everything.
I dirty flashed stable O and it was janky as hell so after a few hours I decided to downgrade using my nandroid backup I just made. All seemed fine until I got in my car and noticed Bluetooth share was broken which kept causing force closes. I tried everything to fix it but nothing worked, had to end up reflashing latest N image. From that point all went downhill.
Phone will not show all the round icons anymore no matter what (play store being one that I totally despise being that huge play button, music, games, photos, movies, maps, etc but phone, messages, camera contacts and a few other are working), assistant would not enable and only screen search was there, Google drive backup isn't working either even with turning it off and on but it just says it's disabled by the administrator (??), I even went in to twrp and wiped EVERYTHING 3 times under the advanced menu and chose to repair the system and then fully ADB flashed the stock N image again.
After that, I rooted with magisk but now BusyBox won't install as systemless to the su/bin folder, I flashed both the night light only and the full pixel mod from gerard hoping it would enable the round icons on the GNL but it didn't. I tried flashfire to flash the N system again to clean that up but it just turned the phone off every attempt. I finally got it to work by reinstalling magisk but it didn't actually flash the system even though it went through the motions and said it was successful. I had to do it again for it to work but everything just seems weird now. What the F am I doing wrong? I know it's not a pixel thing for the round icons bc my wife's Moto z force just got 7.1 this weekend and the round icons showed up for her with no mods, no root, and she has GNL like me.
Help?
Try downloading a custom ROM like Nitrogen or Aquarius. Both of those have the options you want without having to flash any other mods. As for Google Assistant I've only had luck using Beans Gapps full package or open Gapps stock package. I personally prefer Beans. Do a full wipe before you flash and you should be good.
First of all, you went from N to O with a dirty Flash.... Of course there will be bugs. If you want to go back to N, Flash N image(boot, vendor, radio, system), when it boots up, go to settings and then perform a factory reset. After that, you can restore your Nandroid backup.
Thanks All,
Yes I do understand the issues with going from N to O on a dirty flash which is why it was janky and I decided to roll back. As mentioned, I used TWRP to wipe everything 3 times and then reflashed the latest stock N image. Google assistant worked after doing that and the interesting thing I found was if I disabled or deleted apps from the phone and then redownloaded or reenabled them, the round icons began showing again (i.e. google play, docs, sheets, etc) so that issue is resolved. I did not use the nandroid backup I made, I basically just started over from scratch and even though the Google Drive backup is still showing "disabled by your administrator", I see a new backup that was made this morning at 6:13am. I also installed busybox through magisk now rather than the separate app so I guess the only thing left outstanding is why the phone still says the Drive backup is disabled by an admin.
I would grab Nexus Root Toolkit, I install to C:\NRT, download the full August Nougat image, save it to C:\NRT too, then do a complete stock restore, this will wipe everything off phone.
Put you back to starting line and then race with flashing and mods.
ossito2012 said:
I would grab Nexus Root Toolkit, I install to C:\NRT, download the full August Nougat image, save it to C:\NRT too, then do a complete stock restore, this will wipe everything off phone.
Put you back to starting line and then race with flashing and mods.
Click to expand...
Click to collapse
I did use wug's toolkit to flash over ADB. I wonder if the image might have been slightly messed up even though the SHA-256 matched. I could always try to redownload the image again. I was going to wait until 8.0.1 was released to try O again but when I did have O, the backup options were stuck on "waiting for backup" (the menus are slightly different in O) and it never seemed to move forward. I researched that and I guess it's a known issue with some phones and a fix is supposed to be coming out this month but at this point, who knows.
jrg67 said:
I did use wug's toolkit to flash over ADB. I wonder if the image might have been slightly messed up even though the SHA-256 matched. I could always try to redownload the image again. I was going to wait until 8.0.1 was released to try O again but when I did have O, the backup options were stuck on "waiting for backup" (the menus are slightly different in O) and it never seemed to move forward. I researched that and I guess it's a known issue with some phones and a fix is supposed to be coming out this month but at this point, who knows.
Click to expand...
Click to collapse
Toolkit? FFS- fully wipe your device and install full 8.0 image. Done. That is what a full image is for --> janky.
v12xke said:
Toolkit? FFS- fully wipe your device and install full 8.0 image. Done. That is what a full image is for --> janky.
Click to expand...
Click to collapse
I don't think you are fully understanding what the situation is. I have said now 2 or 3 times, I have completely wiped the phone 3 times in a row using twrps advanced settings and I flashed the latest stock N image. The only reason I used wugs toolkit was so I didn't have to ype out all the commands to flash. After the flash was done, I manually flashed twrp again and re-rooting using magisk. Anyway, things are mostly back to normal now. I will manually flash O again at a later time.
jrg67 said:
I don't think you are fully understanding what the situation is. I have said now 2 or 3 times, I have completely wiped the phone 3 times in a row using twrps advanced settings and I flashed the latest stock N image. The only reason I used wugs toolkit was so I didn't have to ype out all the commands to flash. After the flash was done, I manually flashed twrp again and re-rooting using magisk. Anyway, things are mostly back to normal now. I will manually flash O again at a later time.
Click to expand...
Click to collapse
Still wrong. Nuclear flash everything even wiping the whole twrp since its a huge leap from N under the hood. Never dirty flash and of course clean flashing still won't be enough. Do a nuclear flash, wipe everything including your storage and recovery, back it up. Don't be lazy then be frustrated at a plethora of bugs if you didn't even flash properly.
phantom146 said:
Still wrong. Nuclear flash everything even wiping the whole twrp since its a huge leap from N under the hood. Never dirty flash and of course clean flashing still won't be enough. Do a nuclear flash, wipe everything including your storage and recovery, back it up. Don't be lazy then be frustrated at a plethora of bugs if you didn't even flash properly.
Click to expand...
Click to collapse
To be clear, what do you mean by "nuclear flash" bc I'm pretty sure that is exactly what I did, 3 times. Wiped dalvik/art, system, data, userdata, cache from twrp. As for wiping the recovery, that gets done during the flash of the image. So I ask again, what did I miss? Also, it's been said many times that dirty flashing can cause issues, I get it. I wasn't being lazy with trying to get back to N which is the whole point of this thread.
I installed 8.1 last week. Everything was working smoothly. Was trying magisk youtube mod. Screwed something up. Phone went into bootloops. Reinstalled everything .Wiped data. Now my phone reboots randomly. Everything stock .Rooted with Magisk. Mainly it happens whenever i launch a new app(An app which was not launched before). After few tries, the app opens up and doesnt' result in reboot.
Any ideas what could it be ?
You should of wiped system and cache also might be your problem. Also if you where using any substratum themes remove then manually as well. Not sure if they would cause reboots.
coolsid8 said:
I installed 8.1 last week. Everything was working smoothly. Was trying magisk youtube mod. Screwed something up. Phone went into bootloops. Reinstalled everything .Wiped data. Now my phone reboots randomly. Everything stock .Rooted with Magisk. Mainly it happens whenever i launch a new app(An app which was not launched before). After few tries, the app opens up and doesnt' result in reboot.
Any ideas what could it be ?
Click to expand...
Click to collapse
FC's are one thing but random reboots are a completely different animal. I would completely wipe the phone and apply the latest factory image using flash-all.bat. If that doesn't fix it you may have a hardware issue (eg. degraded battery).
Wiping caches helped
I'm running SUPERXE-8.1.0-OPP5.005_v1.5.1.
My 6P was going crazy, restarting every 5 minutes or so. It rebooted so quickly it felt like a soft restart, so I thought powering off and rebooting to recovery using the power + down volume to clear the cache in TWRP would help.
Cleared system and Dalvik and powered down. Full reboot and (for now) it feels much happier and hasn't spontaneously restarted yet. That was about 15 hours ago.
Hope I didn't just Jynx myself, but I think it helped...
I've flashed the final 8.1 images to upgrade my 8.0 unmodified system. Now I've random reboots, usually when I've leave home to go to work or vice versa. Something related to wifi, that I'm connecto on both my work and home?
Same here I had to factory reset I'm having a feeling it's going to happen again. I am on factory, rooted with magisk. I always use SuperSU not saying that is what it is however it did happen when I got home from work and just kept rebooting before I could unlock.
So I've finally got to upgrade from A10 to A11. I was unable to follow the guides for doing local upgrades, because of my previously mentioned "No changelog" and "System Update Installation Failed" message the moment you selected the upgrade package. I tried multiple downloads and verified hashes, this wasn't a corrupted download. So I ended up having to Wipe data to get to a stock A10 and then upgrade using local upgrade. That was Sunday. Since then, I've rooted, restored my apps, lived happily on A11....for about 1-2days before I'd wake up a bootloop. The phone would just be sitting on the spinning Oneplus logo without me knowing why we got here. Even stranger, I had NoLimits installed, so I should be seeing that instead of Oneplus.
Attempting to fastboot boot any of my boot images still keeps me in a boot loop, not much to do other than to wipe and try again....So wipe, on A11 stock, root, restore apps and go on my way....Worked great yesterday. again all apps were restored, things were working, no issues. And then I woke up this morning to find issues with Facebook app (images not loading). Okay, whatever, something may be corrupt, just wait for an update from them. Multiple apps in Playstore need an update, great...do those. But then Oneplus Gallery refuses to update...hmmm. Catlog/Logcat refuse to open with insta-crashes. Facebook nolonger has the corrupt image issue, it just insta-crashes.......uh oh......maybe a reboot?.....rebooted and then stuck on NoLimits bootscreen for about 2 minutes....after 2 minutes it reboots and I'm back to being stuck on Oneplus boot image.
So I'm out of ideas now. about to wipe and go back to A10, because I can't for the life of me find a connection to all of this and its getting tedious to restore apps (especially 2fa apps).
Any help would be appreciated.
Hi!
I have had annoying bootloops when making a call.
It connects to a call and then boom, goes dark and reboots by its self. Very annoying.
I have 2 SIM cards on use, dont know If that matters.
Iam suspecting the network connection change during call -setting has something to do with it...
Hope there is an update coming soon to fix this.
Yea I have 2 sims as well (TMo and GoogleFi) so that's an interesting point. We finally now have dual-sim (US/Glo).
I'm currently testing out how long i can go with my current setup: Just A11 + Root + NoLimits....wait about 2-3days, then try LuckyPatcher (best way I know to remove ads), 2-3days, and then continue testing other ideas).