Related
just use the one click root tool by kennethpenn, work perfectly thanks. use titanium back to do a backup of all the app and system then took out all the att bloatware. i have few questions at this point.
1.
will i be able to get OTA updates from att? what will happen to all the bloatware that i deleted? would they appear again?
2.
what happens if i do a factory reset on the phone? would i brick the phone? under normal condition that will erase all apps i installed and return it to factory setting, that means all the att bloatware will be back? will i lost root?
3.
what other things i can do after i root the phone at this point?
thank you for your help
no one can help me with those questions??? anyone???
i am sure a lot of people have the same question.
1.
will i be able to get OTA updates from att? what will happen to all the bloatware that i deleted? would they appear again?
I'm not 100% sure on this, but as long as you're running an actual AT&T ROM (not an Asian or Rogers ROM), you'll be notified of the OTA's. Now, if you're not using the stock Recovery image (that is, if you've installed CWM Recovery), you won't be able to apply the update. OTA updates get applied via the stock Recovery image.
2.
what happens if i do a factory reset on the phone? would i brick the phone? under normal condition that will erase all apps i installed and return it to factory setting, that means all the att bloatware will be back? will i lost root?
If you do a factory reset from CWM or within the phone's UI, you're fine. Root will remain in place, and you won't brick it. It just clears the user data from the phone, and should leave "sdcard" intact. However, I'm not 100% sure what happens if you do a factory reset from the bootloader. So just don't do it that way, unless someone else can confirm that it's okay.
3.
what other things i can do after i root the phone at this point?
You ca use apps like AutoKiller to change your memory management, for one. That's about all I'm doing with root right now. If we ever get custom kernels, you'll be able to overclock your CPU. If you search the Play Store for "root," you'd doubtlessly find some other root apps that you may be interested in.
Hope this helps!
Don't ever ever ever install an OTA on any rooted Android device. At the least, it won't work anyway, or you will lose root. At the worst, you will be stuck in a bootloop. Updated ROMs (based on the OTA's, but rooted, and safe to flash) usually get posted in Development soon after the OTA's go out. That is what you want to install.
craig0r said:
However, I'm not 100% sure what happens if you do a factory reset from the bootloader. So just don't do it that way, unless someone else can confirm that it's okay.
Click to expand...
Click to collapse
I can confirm that it's OK. My phone was rooted and stuck in a boot loop. I did a factory reset. It was reset and still rooted after the fact. So you can do it.
thank you all
redpoint73 said:
Don't ever ever ever install an OTA on any rooted Android device. At the least, it won't work anyway, or you will lose root. At the worst, you will be stuck in a bootloop. Updated ROMs (based on the OTA's, but rooted, and safe to flash) usually get posted in Development soon after the OTA's go out. That is what you want to install.
Click to expand...
Click to collapse
Just to clarify, pre-rooted versions of the official ROMs (which often get posted on XDA, as I mentioned) may need unlocked bootloader to install, so this will possibly not be an option for a while. Although there may be alternate safe ways to update (but not OTA). For instance, a leaked 1.83 firmware version is already available as an RUU in the Development subforum. Apparently, its okay to install via RUU, then re-root.
In general, the safe thing to do is to read up on here when updates are released, and see if there is a safe way to update on a rooted phone.
Everyone help! I just updated my tf700 to the newest update which was supposed to be minor. Everything went smooth but upon boot up everything went wrong. Every single app force closes upon unlocking the lock screen. I get a pop up for just about every single app that's trying to start saying sorry the app has closed. Oddly, any app that was originally on the device works OK. I did a normal reboot and then again I saw the upgrading message and another message saying optimizing apps and it counts through the apps its optimizing. Then again when I reboot fully it does the same thing. I did a cold reboot and it seemed a little smoother but then again I had the same force closes and error messages. And still only the stock apps will function, anything and everything else force closes upon opening.
I've never even heard of errors or problems such as this. I have no idea what to do and I have lots of data on the device I don't want to lose and can't lose. By the way I am rooted and I did not uninstall any stock apps. Just froze a couple. Build # now 10.6.1.14.10-20130801
Please any and all suggestions!
Ps - under kernel version it says (concerned about name cancer):
3.1.10-gba9af5
[email protected] #1
Thu Aug 1 17:00:24 cst 2013
bobstone said:
Just froze a couple.
Click to expand...
Click to collapse
There's your problem...
Sorry mate, but I can't help myself - attention everyone, here comes a rant:
I cannot believe how many people do not backup the data on their tablets! This is the second time in as many days that I read: "Something unexpected went wrong and I cannot loose my data".
If you did not back it up the question is not if you loose it, the question is WHEN!
This is a portable device! Pre-destined to be lost, stolen, dropped, submerged, spilled upon, run over by trucks - and those are everyday scenarios which are LIKELY. Don't even want to get into freak accidents... It's so easy to protect your data now-a-days! There's Dropbox in conjunction with Dropsync, there's Google Drive and a host of other solutions. There is no excuse for having only one copy of important data...... End of rant
To your problem. Before you apply a stock update you have to replace/unfreeze all stock apps. Usually the update just fails if you have frozen system apps - I do not know what went wrong in your case.
How did you update? OTA or manually?
It sounds as if your data partition is corrupted since the stock apps (installed in /system) work, but your user apps (installed in /data) do not. But that your system apps work is the good news! At least you didn't brick your tablet.
One of the stock apps is the file browser. See if you can copy your precious data to a microSD. And I'm only talking about data like pictures, files, video, projects. Don't worry about your apps.
If the file browser cannot see your data you're gonna have to get into the area of data recovery tools - lots of research ahead of you there.....
Another possibility may be - if you can access your tablet from your PC through USB - to ADB pull files off your tablet, check if your computer recognizes your tablet.
Once you have your data safe (or given up on it) you can perform a factory reset and possibly have to reflash the firmware.
BTW, if you did not protect root with Voodoo Rootkeeper before the update or if you flashed the full firmware (as opposed to doing an OTA update) you also lost root. And Asus plugged the hole Motochopper used in the latest firmware version. At this point 10.6.1.14.10 is not rootable without unlocking.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
bobstone said:
Everyone help! I just updated my tf700 to the newest update which was supposed to be minor. Everything went smooth but upon boot up everything went wrong. Every single app force closes upon unlocking the lock screen. I get a pop up for just about every single app that's trying to start saying sorry the app has closed. Oddly, any app that was originally on the device works OK. I did a normal reboot and then again I saw the upgrading message and another message saying optimizing apps and it counts through the apps its optimizing. Then again when I reboot fully it does the same thing. I did a cold reboot and it seemed a little smoother but then again I had the same force closes and error messages. And still only the stock apps will function, anything and everything else force closes upon opening.
I've never even heard of errors or problems such as this. I have no idea what to do and I have lots of data on the device I don't want to lose and can't lose. By the way I am rooted and I did not uninstall any stock apps. Just froze a couple. Build # now 10.6.1.14.10-20130801
Please any and all suggestions!
Ps - under kernel version it says (concerned about name cancer):
3.1.10-gba9af5
[email protected] #1
Thu Aug 1 17:00:24 cst 2013
Click to expand...
Click to collapse
I would just wipe and start over, even if you get it functional again you could end up with problems.
Hmmm - I too think you are going to lose your data here as I can't see how you can recover without wiping if everything is force closing now.
BTW don't worry about the kernel version being cancer that is Asus naming convention. They have been using planets and have now run out so they are now using astrology instead of astronomy which is rather odd but there you go.
Previously we had mercury, venus, jupiter, uranus etc now we have aquarius and cancer......
What don't make sense and I can't accept, I've updated this device 4 times now total and never had a problem like this. Also, I've updated a few devices with frozen apps and had no problems. Are frozen apps really the cause? I can't see it.
And if I do have to wipe, and I really don't want to, will I still be rooted after wiping and is there a way to back up things since I can't use 3rd party apps? (Also, I used voodoo)
It just seems like something went wrong with the update, say something initializing or cache problem, and im sure there's an easy fix.
Please, keep the ideas coming...
I guess, I just need to clerify , stock bootloader, stock ROM, but rooted??
Sent from my [email protected]
Sorry all was reading it on the app wow that really is not good lol
Correct, stock rom rooted. No interest in custom roms. I know there's gotta be something simple, maybe even a chkdsk in linux or something. I just hate to wipe n start over. My files seem to be intact and non stock apps start to open for a split second then they force close.
Any responses guys? Would really appreciate any help.
Thanks,
Sent from my rooted Galaxy S4
bobstone said:
Any responses guys? Would really appreciate any help.
Thanks,
Sent from my rooted Galaxy S4
Click to expand...
Click to collapse
I think you will have to wipe mate as said. Painful but can't see any other way around it.
bobstone said:
Correct, stock rom rooted. No interest in custom roms. I know there's gotta be something simple, maybe even a chkdsk in linux or something. I just hate to wipe n start over. My files seem to be intact and non stock apps start to open for a split second then they force close.
Click to expand...
Click to collapse
Yea, wipe, and no you won't keep root on a stock rom wipe. As I said previously even if you managed to "fix" the problem you would be creating potential for lockups/forced reboots. Your also not the first to have issues when upgrading with sys apps frozen, look around the forum, its been discussed before. Sucks, but there it is.
I have the same issue, and I can't remember freezing any apps. I don't have any critical data that I can't loose though. Still it sucks to have to wipe if there's another way.
Stock, locked bootloader, rooted. Temp unrooted using OTA Rootkeeper and did the OTA. Then upon the next reboot, all apps FC. All earlier updates has worked flawless. :/
vatvedt said:
I have the same issue, and I can't remember freezing any apps. I don't have any critical data that I can't loose though. Still it sucks to have to wipe if there's another way.
Stock, locked bootloader, rooted. Temp unrooted using OTA Rootkeeper and did the OTA. Then upon the next reboot, all apps FC. All earlier updates has worked flawless. :/
Click to expand...
Click to collapse
boy, i can't believe how close i was to actually going forward with this OTA when it "pooped" up in the notification area. good thing i had just been reading xda forums and i saw a couple posts bout ppl losing root and whatnot with said update.
now i am a happy camper on Cromi-x =D
best bet as a few already said is to try to extract your data from the thingy, and wipe it out, if you wanna take a n00b advice, if you're close to the end of your warranty period, go ahead and unlock it then proceed to cromi-x it. i was of the same position as you back when i bought it, not interested in custom roms and whatnot, just root...... but since my warranty was expiring next month anyways, and it had grown considerably sloppy and laggy, i figured out, why not? and i gotta tell you, it was the right thing to do.
hands down
anyways, good luck on your recovery.
I wiped and downgraded to .8 and will happily stay there for now. Maybe until I unlock the bootloader in the future.
vatvedt said:
I have the same issue, and I can't remember freezing any apps. I don't have any critical data that I can't loose though. Still it sucks to have to wipe if there's another way.
Stock, locked bootloader, rooted. Temp unrooted using OTA Rootkeeper and did the OTA. Then upon the next reboot, all apps FC. All earlier updates has worked flawless. :/
Click to expand...
Click to collapse
If you don't have it download Titanium Backup, hit Menu and wipe Dalvic cache. Reboot. The reboot will take a while because the Dalvic has to be rebuild - so don't panic
If that doesn't do it, I'm fresh out of ideas.
I tried to wipe via the stock recovery, but all the FC's was still there, and what's worse was that because of the FC's I couldn't finish (or quit) the "Set up your tablet" thingie. I always crashed on setting up a gmail account. Didn't matter if I was connected to the internet or not, or if I declined setting it up. So I had to do everything from the stock recovery.
Downloaded the .8 firwmare, unpacked the first .zip file, renamed the second .zip (to EP201_768_SDUPDATE.zip) and put it on an empty micro SD, made sure the SD-card was FAT32, booted to recovery (Power Vol down for 5 sec) and installed it via RCK, Android stock recovery.
Thanks for the tip, though. It might have worked. I don't know.
Hello all...I need a bit of help. I rooted and then un-rooter my previous phone with KingRoot. After removing it with the KR uninstall program, I would use multiple root checking apps, and they would all report that the phone was NOT rooted, but when I tried to update system files with WiFi update, it would error with a "Root has been detected, can not update device" message. I recently purchased a new phone with 6.0 and transferred my files and settings to the new phone and now am having the same problem with my new phone.
What file/files does the system check in order to make that determination??? Is it something I can remove or edit with out a complete wiping and re-installation of Android??? King Root does not offer a rooting for my current phone where I could install and then try a removal on this phone.
I was really hoping that with a new phone that I would be leaving that problem behind!
Thanks ahead
never mind....
Well, for what ever reason...I did one more hard reset and the problem solved itself. Now able to receive regular updates from BLU/Android. Go figure..
Hello everyone, I need your help !
So I want to sell my Galaxy S8+ (G955F) but my potential buyer wants to get rid off root, so I flashed Android 7.0 via ODIN. Problem is with Samsung Health app, because immediately after launch an error occurs because this app will not work on rooted device (error 0x110060null5e2830). Any app for root detection isn't detecting root, so where is the problem? What can I do to make this app, and everything from Samsung, work?
Thanks in advance and sorry for my English
Ćwirek said:
Hello everyone, I need your help !
So I want to sell my Galaxy S8+ (G955F) but my potential buyer wants to get rid off root, so I flashed Android 7.0 via ODIN. Problem is with Samsung Health app, because immediately after launch an error occurs because this app will not work on rooted device (error 0x110060null5e2830). Any app for root detection isn't detecting root, so where is the problem? What can I do to make this app, and everything from Samsung, work?
Thanks in advance and sorry for my English
Click to expand...
Click to collapse
1. you must root stockrom again
2. go to buildprob and change ro config tima to 0 or1
3 reboot
4 start shealt
5 unroot phone and flash stockrom with odin
6 done
Thor1964 said:
1. you must root stockrom again
2. go to buildprob and change ro config tima to 0 or1
3 reboot
4 start shealt
5 unroot phone and flash stockrom with odin
6 done
Click to expand...
Click to collapse
What do you mean at #4? So basically I need to do exactly what on this video below? What about all of this when device will be restored to the factory settings? Will the application still work or will it be necessary to carry out the whole process again? And what about OTA updates from Samsung?
Mentioned video:
https://www.youtube.com/watch?v=QYKUyVs6gwM&t=
Ćwirek said:
What do you mean at #4? So basically I need to do exactly what on this video below? What about all of this when device will be restored to the factory settings? Will the application still work or will it be necessary to carry out the whole process again? And what about OTA updates from Samsung?
Mentioned video:
https://www.youtube.com/watch?v=QYKUyVs6gwM&t=
Click to expand...
Click to collapse
do it like in the video that works,if you then run the stockrom, after unroot, then you have to use the home csc instead of csc. otherwise everything will be deleted. translated with googel, hope you can understand
Thor1964 said:
do it like in the video that works,if you then run the stockrom, after unroot, then you have to use the home csc instead of csc. otherwise everything will be deleted. translated with googel, hope you can understand
Click to expand...
Click to collapse
Ok, so this is what have I done, maybe someone will find this useful:
1. Root stock Samsung firmware (XEO version, Android 7.0)) with Magisk;
2. Found this build.prop file and changed value ro.config.tima from 1 to 0 and saved the file;
3. Samsung Health still wasn't working, but I restarted the device and app starts to work;
4. Unroot phone by flashing stock Samsung firmware (Android 7.0) via ODIN, BUT, as you suggested, I used HOME_CSC file;
5. Update the phone to Android 8.0 via OTA update;
6. Samsung Health works!;
7. Restore phone to the factory settings;
And something went wrong here, because Samsung Health app again isn't working, still the same error occurs. Why? Is it because I restored the factory settings for this potential buyer? Well, he eventually will do this by himself... Is it because factory reset resets the changed value in build.prop? Is it possible to factory reset the phone without the necessity for editing build.prop all over again just to get rid of that error?
Ćwirek said:
What do you mean at #4? So basically I need to do exactly what on this video below? What about all of this when device will be restored to the factory settings? Will the application still work or will it be necessary to carry out the whole process again? And what about OTA updates from Samsung?
Mentioned video:
https://www.youtube.com/watch?v=QYKUyVs6gwM&t=
Click to expand...
Click to collapse
when the Knox fuse is blown (meaning you flashed twrp or a custom rom) you will never be able to use SHealth or Samsung Pay on that phone unless you root first. (I don't think Samsung Pay will ever work, but as stated earlier, there is a work around to get SHealth working again but you have to be rooted to do it.)
This is a hard ware thing - the phone knows that something was flashed on it - and samsung decieded that for security reasons, when soemthnig is flashed - ever - that phone is potentially corrupt and will not allow those apks to work on them. (as I said, the only way around that is to have some kind or work around you can use after you root the device) AND if rooted - you will not receive samsung OTA's.
Geekser said:
when the Knox fuse is blown (meaning you flashed twrp or a custom rom) you will never be able to use SHealth or Samsung Pay on that phone unless you root first. (I don't think Samsung Pay will ever work, but as stated earlier, there is a work around to get SHealth working again but you have to be rooted to do it.)
This is a hard ware thing - the phone knows that something was flashed on it - and samsung decieded that for security reasons, when soemthnig is flashed - ever - that phone is potentially corrupt and will not allow those apks to work on them. (as I said, the only way around that is to have some kind or work around you can use after you root the device) AND if rooted - you will not receive samsung OTA's.
Click to expand...
Click to collapse
I know about the OTA's, but I received one today (with Android 8.0) BEFORE I decided to factory reset this phone. Before this even Samsung Health app was working.
Ok, so please correct me if I'm wrong, but I can edit this ro.config.tima from 1 to 0 value so many times I want, but if I someone will try to factory reset this phone everything will be undone to the previous state (when ro.config.tima is 1 again, instead of 0) and actually nothing can be done to get rid of root permanently and make Samsung app works?
but if I someone will try to factory reset this phone everything will be undone to the previous state
that's it, why do you do it? factory reset??
you do not need that at the update
Thor1964 said:
but if I someone will try to factory reset this phone everything will be undone to the previous state
that's it, why do you do it? factory reset??
you do not need that at the update
Click to expand...
Click to collapse
As I mentioned above, I want to sell this phone and my potential buyer wants me to unroot the device, because he wants to use Samsung apps (like Samsung Health and all the others), he also mentioned that he wants to pull out the phone of the box "like he would buy the new one by himself" and because of this I tried to factory reset via option in settings. He would eventually do it himself and I want to avoid any problems because of this
So... Absolutely nothing can be done?
Galaxy s8 on Verizon, a standard update notice kept appearing past few days, finally installed it. The minute it finished, it is now in an endless restarting loop. The phone does unlock and show my homescreen. I can get into it, but I only get about 10 seconds to do stuff then it freezes/restarts. Tried Clear Partition Cache in the recovery mode. Tried Safe Mode. No luck.
When I rush over to Settings>Software Update, and click it, it says "Software update in progress"....so it makes me think it is the remnants of the new software update completing itself, and that causes the rebooting. The final stages perhaps? Is there a way to CEASE that the second I unlock my phone? To stop all the background stuff.
Or maybe wouldnt make a difference. Any ideas besides factory reset? Way to revert back?
Wanted to backup a few recent pictures first.
A factory reset is the last resort to fix this.
Maybe it's theme related. Try toggling the button layout (settings -> display -> navigation bar) a couple of times.
If you have substratum installed, try disabling it.
If you want to back up your pictures;
Have you tried accessing the phone using a computer? Either just through a file explorer or by using ADB? To use ADB, you may need to get into settings -developer mode
I tried plugging into a computer, but I only have about 10 seconds, so I dont get enough time to access the files. I get into the phone drive on windows Samsung Galaxy>DCIM> CAMERA> ...then it reboots.
Developer mode is already enabled. Can ADB be used while on the recovery mode screen? I can access that command line looking screen as long as needed.
But accessing the phone normally like turning it on and unlocking the screen would not work, I would keep losing the connection when it reboots.
halfhumble said:
Galaxy s8 on Verizon, a standard update notice kept appearing past few days, finally installed it. The minute it finished, it is now in an endless restarting loop. The phone does unlock and show my homescreen. I can get into it, but I only get about 10 seconds to do stuff then it freezes/restarts. Tried Clear Partition Cache in the recovery mode. Tried Safe Mode. No luck.
When I rush over to Settings>Software Update, and click it, it says "Software update in progress"....so it makes me think it is the remnants of the new software update completing itself, and that causes the rebooting. The final stages perhaps? Is there a way to CEASE that the second I unlock my phone? To stop all the background stuff.
Or maybe wouldnt make a difference. Any ideas besides factory reset? Way to revert back?
Wanted to backup a few recent pictures first.
Click to expand...
Click to collapse
Try downloading that same version of Odin flashable stock firmware from the internet, the same version as the update that you received, then flash that via Odin. As long as the update does not upgrade your bootloader or your binary, it will not wipe your user data(pics).
But first....
If you can get to the homescreen and unlock the device, don't touch anything else once the device opens, just connect it to PC and retrieve your photos from the internal storage, then factory reset the device.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
Try downloading that same version of Odin flashable stock firmware from the internet, the same version as the update that you received, then flash that via Odin. As long as the update does not upgrade your bootloader or your binary, it will not wipe your user data(pics).
Click to expand...
Click to collapse
I dont know what version the update was that caused it or how I would find out. But I ended up getting it fixed.
I just downloaded the most recent version firmware from SamFW.com, and used that one. The First flash, the phone was worse! It was now stuck at the samsung logo looping. I flashed it a second time, then it worked! Phone back to normal and backed up my pictures. I had used the home CSC file too, and none of my user data was wiped. I thought it was supposed to wipe that, got lucky
I assume once that OTA update comes back and tries to install, I may have this problem all over again. I can't go forever without the security updates.
Droidriven said:
If you can get to the homescreen and unlock the device, don't touch anything else once the device opens, just connect it to PC and retrieve your photos from the internal storage, then factory reset the device.
Click to expand...
Click to collapse
^
I had tried that a couple times, it lasts about 15 seconds then restarts. Not enough time, I would get to the DCIM folder but before pics loaded, it froze and restarted.
halfhumble said:
I dont know what version the update was that caused it or how I would find out. But I ended up getting it fixed.
I just downloaded the most recent version firmware from SamFW.com, and used that one. The First flash, the phone was worse! It was now stuck at the samsung logo looping. I flashed it a second time, then it worked! Phone back to normal and backed up my pictures. I had used the home CSC file too, and none of my user data was wiped. I thought it was supposed to wipe that, got lucky
I assume once that OTA update comes back and tries to install, I may have this problem all over again. I can't go forever without the security updates.
^
I had tried that a couple times, it lasts about 15 seconds then restarts. Not enough time, I would get to the DCIM folder but before pics loaded, it froze and restarted.
Click to expand...
Click to collapse
The most recent version that you downloaded might be the same update. The OTA updates and the Odin flashable updates are the same thing, the OTA update is just more automated. Flashing the same version as the OTA update via Odin, yields the same results. I think the Home CSC is the one that doesn't wipe user data. I think the Home CSC is intended for users that intend on keeping the device and using it in the same region/network and the other CSC is intended for users that want to sell the device or use the device in a different region or if you have a custom ROM and custom recovery on the device and you want to restore to stock. I could be wrong though.
If you do get a prompt for an OTA update, backup your data then factory reset the device then allow the device to update. That should prevent any further issues with updating via OTA.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
The most recent version that you downloaded might be the same update. The OTA updates and the Odin flashable updates are the same thing, the OTA update is just more automated. Flashing the same version as the OTA update via Odin, yields the same results. I think the Home CSC is the one that doesn't wipe user data. I think the Home CSC is intended for users that intend on keeping the device and using it in the same region/network and the other CSC is intended for users that want to sell the device or use the device in a different region. I could be wrong though.
If you do get a prompt for an OTA update, backup your data then factory reset the device then allow the device to update. That should prevent any further issues with updating via OTA.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Okay, I see.
Well when the phone did boot back up normally after the 2nd flash, there was a pop up that said software update unsuccessful. So I'm not sure if the same OTA update actually updated per se. But yeah, next time Im ready, I've got everything backed up!
Thanks so much!
halfhumble said:
Okay, I see.
Well when the phone did boot back up normally after the 2nd flash, there was a pop up that said software update unsuccessful. So I'm not sure if the same OTA update actually updated per se. But yeah, next time Im ready, I've got everything backed up!
Thanks so much!
Click to expand...
Click to collapse
I always prefer updating via Odin instead of OTA, it is much better and less chance of issues such as bootloop or random reboot. These are the issues you were having. I actually suggest using Odin or Smart Switch on PC the next time an update is available. Or, on older devices, use Odin or Samsung Kies to update. OTA is frequently unreliable, it commonly causes bugs, especially if the update is a newer android version than what is already on the device, it usually causes conflicts due to user data from your previous system apps and user settings conflicting with the new system because of differences between the older system apps and the newer system apps or differences in settings in the older system conflicting with changes in how the newer system settings are handled. Systems don't like using system data that was created by another system when there are differences between the two systems.
Another method that can be used is if your manufacturer/carrier releases a stock update.zip that can be flashed via stock recovery, they are made specifically for flashing via stock recovery ONLY, they are not the same as the stock firmware file that is flashed via Odin. These can be downloaded to the phone's internal/external memory then you boot into stock recovery then factory reset/wipe cache in recovery(backup data before wiping) then you can flash the update.zip. Alternatively, you can flash the update.zip without resetting/wiping(this is called a "dirty" flash), in theory, a dirty flash is useful when you don't want to wipe data or lose data. But that comes with a chance of causing bugs, as you have discovered for yourself during your update process.
Sent from my SM-S767VL using Tapatalk