Hello friends -
Looking for some help. I am trying to upgrade several Galaxy S6 Active SM-G890A devices with 5.1.1 to Android 6.0.1 without wiping the existing apps. I have a device that has the OTA file downloaded, I followed the steps shown on XDA-Developers to capture the URL via ADB or via Take bug snapshot, didn't find the URL.
None of my devices are rooted. Is there a way I can flash or upgrade these devices without loosing the apps?
Please note, I have Mobile Device Management software installed on these devices to keep track of their location and usage.
So far, I've tried the following:
1) Downloaded Firmware 6.0.1 (4 Files - AP, BL, CP & CSC) - Couldn't find the HOME_CSC anywhere
2) Using Samsung Smart Switch - I was able to take a backup of one of my existing devices
3) Flash the firmware with 4 files using Odin
4) Firmware upgraded successfully, however the device was wiped.
5) I had to follow the startup prompts, like Click on Welcome, click Next and all that startup prompts till you get to the Home Screen
6) Restore the backup using Samsung Smart Switch
Here are the challenges:
1) The Mobile Device Management App doesn't restore all the way, it needs to be re-enrolled and I have to enter the code manually
2) The Google Account also needs to be added
3) There's one more proprietary App that I have to launch and close before it works properly
I am trying to upgrade several of these devices in the field and want a process that I can document and then have my team upgrade these remotely rather than share all these tedious steps with the people that are non-technical and spend hours upgrading.
Can anyone help me out by sharing some ideas or suggesting a different route or approach?
My goal is to upgrade the firmware from 5.11 to 6.0.1 without loosing apps or existing data.
Any help will be appreciated!!
Deejas
From my personal experience, upgrading to a higher Android version always makes you lose apps and accounts as the memory needs to be formatted to upgrade (afaik).
Some people tried a dirty flash with custom firmware (using a zip file) but this may render the handset unstable.
Knowing thas this is not what you wanted to hear I suggest you upgrade to Nougat directly, skipping 6.whatever!
Related
Hi,
about 2 years ago I rooted my S2 Galaxy Tab (T719) and now I would like to upgrade from Android 6.0.1 to Android version to 7 or 8. I have googled for instructions on how to upgrade a rooted S2 Tab but did not find anything useful (most info is on OTA upgrades which no longer works on rooted devices). Could someone please post step-by-step instructions (please bear in mind that I only ever deal with this kind of thing once every 2-3 years so I do not have much experience). I have TWRP v 3.0.2 installed (do I need to update this as well?) and the tablet is not encrypted (so hopefully I won't have to wipe the system partition and re-install all the app?!?). Thanks.
I also noticed that there is now a huge variety of ROMs out there. How can one know which ones are trustworthy? The main reason I rooted the tablet was to be able to increase privacy (control app permissions with XPrivacy). So I do not want to install some custom ROM that maybe contains spyware or other compromising features. Any advice on this would be greatly appreciated. Given my motivation (privacy) for rooting, would it maybe be better to go back to Stock ROMs (i.e. non rooted) and simply control web access via netguard (by preventing net access for some apps, they may still spy on my contacts, location, or email but cannot phone home to transmit the information)? At least I would still get OTA updates because being excluded from the OTA channel also poses a security risk in itself I suppose. Ok so any advice would be appreciated.
Thank you in advance!
There is no official Android 8 for our device. If you want 8 or 9 you have to install a custom ROM like LuK1337's LineageOS port. It is as safe as LineageOS is by itself on any device. Only problem you might have then is that calling is not possible anymore for now, but LTE works. If you want to use LOS, you HAVE to format data because it's not compatible at all. If you wanna stay on official Android you might keep it. Installing is done by flashing the official firmware with the correct country code over Odin. This will remove TWRP at first so you have to reflash it by Odin afterwards. For firmware download I always use: https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647 and Odin is found by google. If you wanna got the way to LOS you have to do all the steps I mentioned before too anyways to have a recent Modem firmware and bootloader. In that case you just have to flash LOS and OpenGAPPS by TWRP and delete /data aka Factory reset.
Regardless what you do, after ODIN is done, you HAVE TO boot into TWRP immediately to keep it from being removed by official firmware. While you are in there anyways you can install magisk to keep it from encrypting /data
Many thanks emuandco. So I guess I will stick with the Android 7 as I do not want to reformat the tablet and reinstall all the apps. I have started to download the Android 7 stock ROM, but it is taking quite long so in the meantime just to confirm, the steps to follow are:
1- use odin to flash the stock ROM (no steps required prior to this? I simply overwrite the existing ROM? I suppose that I will loose root then and need to re-root the device using the standard procedure as explained here: http://www.samsungsfour.com/tutoria...nougat-7-0-using-cf-auto-root-all-models.html ?)
2- use odin to flash TWRP (I will need the newest version I guess and cannot use the same as for Android 6?)
3- boot into recovery mode to ensure that TWRP does not get overwritten
4- done
Is this correct? Do I then need to reinstall Xposed, SuperSU and Xprivacy or will they be preserved?
Thanks again!
P.S.: BTW, I also found these instructions: https://forum.xda-developers.com/tab-s2/development/twrp-3-0-2-1-galaxy-tab-s22016-sm-t713-t3390627 which are slightly different from http://www.samsungsfour.com/tutoria...nougat-7-0-using-cf-auto-root-all-models.html and require a wipe of the data partition. Does this mean that for an update to Android 7 I definitely do need to wipe the data partition? If this is the case then this would be a major disadvantage of rooting in the first place and maybe I simply flash the stock ROM and do not root at all but go the "netguard" route as mentioned in my original message?
I never used the official Firmware that much. Fist thing I did was going on LuK1337's nerves to get a port of LOS for it up and running So no clue if Samsung manages to keep /data but I guess so. Yeah, looks fine what you list there. You COMPLETELY overwrite ANY modification in kernel or /system, so reflash your mods and root (Magisk). I always recommend to uase the MOST recent TWRP. (https://dl.twrp.me/gts28velte/ should be it in your case).
Ah and looking at your manuals... Check OEM unlock just to be rather safe than sorry if things go mad.
emuandco said:
I never used the official Firmware that much. Fist thing I did was going on LuK1337's nerves to get a port of LOS for it up and running So no clue if Samsung manages to keep /data but I guess so. Yeah, looks fine what you list there. You COMPLETELY overwrite ANY modification in kernel or /system, so reflash your mods and root (Magisk). I always recommend to uase the MOST recent TWRP. (https://dl.twrp.me/gts28velte/ should be it in your case).
Ah and looking at your manuals... Check OEM unlock just to be rather safe than sorry if things go mad.
Click to expand...
Click to collapse
Deleted
Using Odin files to update a Samsung AT&T model will almost always result in a factory reset being performed, and I've also seen the same thing happen when trying to update via OTA zip in Recovery. I'm providing this package for anyone still using the S5 Active, to be able to update software without needing to do a factory reset. I have personally verified that these files will perform the update without wiping any data. These files will update you to the Build/Baseband ending in PK5, Android 6.0.
My zips are compressed extra small for space and bandwidth savings. The default Windows extractor can't handle it, so you'll need a 3rd party tool like 7zip, WinRAR, etc.
Happy flashing!
https://www.androidfilehost.com/?fid=1899786940962576204
Do you have one of these packages, but for the G900A?
BrianSamsungTab said:
Do you have one of these packages, but for the G900A?
Click to expand...
Click to collapse
I can make one, following the same recipe
Hi Guys it would appear that my concerns for getting a 2020 or Android rom / firmware are slim to None in that I simply cannot find my type of file required to do the job anywhere??
My daily driver is in excellent condition but most definitely do with a major face - lift, make that overall as it is more than capable, I had just upgraded my wife's Note4 with crDroid firmware and it is Fantastic!
This is the type I need [samsung/nobleltezh/nobleltehk] my device is fitted with Exynos / Qualcomm that I believe to be rare in comparison to most other of its variants??
I put this out there as a real S.M.C. can anyone help please? Riccardoray.
The answer is no. I have tried LineageOS, Bliss rom, pixel experience, crDroid, but there is no "IMEI" and "SIM" meaning I cannot make a phone call. Work-around solution:
Install the rom of your choice and give up the phone call function, use it as a wifi-tablet;
When you want to downgrade back to Android 7 and use phone call normally, use the stock firmware from https://sfirmware.com/ + odin to restore. Remember to delete google/ samsung account (odin warns so) because the accounts might mess up odin restoration process.
The disadvantage is that you need a PC to use odin. If someone knows how to use TWRP to intall stock firmware, please let me know;
The stock firmware looks like this: a zip file containing AP, BL, CP, CSC files in md5 format. https://android.stackexchange.com/questions/176515/what-do-the-terms-bl-ap-cp-and-csc-mean-in-odin
If I root this device to use titanium backup and root for apps like gsm battery - if i were to upgrade using samsung services, would this undo my root or lock my phone from future updates in some way?
Is it advised against updating if one were to root in the future?
Lastly why can't I call record?
zetsui said:
If I root this device to use titanium backup and root for apps like gsm battery - if i were to upgrade using samsung services, would this undo my root or lock my phone from future updates in some way?
Is it advised against updating if one were to root in the future?
Lastly why can't I call record?
Click to expand...
Click to collapse
I will try to answer....
First, IF you Root, one is Not able to do the OTA updates! ( Meaning, you will not be able to update the phone from within the devise)
Second one- The Hard Q to address - Only due to the fact that Everyone is Different. Everyone uses their phone differently. Plus, add in the fact that Samsung has stated, that the S20 FE will receive regular security updates and a few OS updates as well!! (When Purchased in January I has Android 10. A couple of weeks later, it was February, Samsung updated to Android 11. (Knowing later this year, if not next, we will be on Android 12, says something, about the devise!))
Now all that said, knowing XDA People, in time, we should be able to have Our beloved Root, as well as, Updates that come from Google and Samsung.....
I had to check my phone (recent update, things have changed a bit...) in my case, I no longer have call recording (stock) on the phone! It has disappeared!!!
if you don't mind downloading and manually flashing the latest update via Odin, keeping root would mean taking the boot.img (I think) from the tar file and patching it via magisk and then putting it back into the tar file and flashing the whole thing.
3mel said:
if you don't mind downloading and manually flashing the latest update via Odin, keeping root would mean taking the boot.img (I think) from the tar file and patching it via magisk and then putting it back into the tar file and flashing the whole thing.
Click to expand...
Click to collapse
so the stock updated rom is available here? on this sub foruM? i'm fine with that for now. as long as i can keep my seetings and not hav et o resetup everything
zetsui said:
so the stock updated rom is available here? on this sub foruM? i'm fine with that for now. as long as i can keep my seetings and not hav et o resetup everything
Click to expand...
Click to collapse
not available from here yet, you'd have to download the firmware from one of the Samsung firmware sites / apps. don't quote me on these names, Samfirm, Sammobile and Frija. and again don't quote me, do your own searches here to confirm but if you use the HOME_CSC file instead of the regional one your data won't be wiped.
you'd lose root if you didn't also patch the boot.img file and copy that back to tar archive.
3mel said:
not available from here yet, you'd have to download the firmware from one of the Samsung firmware sites / apps. don't quote me on these names, Samfirm, Sammobile and Frija. and again don't quote me, do your own searches here to confirm but if you use the HOME_CSC file instead of the regional one your data won't be wiped.
you'd lose root if you didn't also patch the boot.img file and copy that back to tar archive.
Click to expand...
Click to collapse
you're confusing me now. so what's the order if I do want to update and keep root?
Root->magisk patch after its released for current upgrade (any eta on time after samsung releases)->upgrade?
my last Samsung was fully custom rom and I only ever flashed radio and bootloader, I got those from links in forums. I think firmware is pretty quick in being made available on these sites / apps but I've not used them myself.
so imagine your phone is already rooted (that first initial root is more involved as there's a data partition wipe), new firmware comes out.
* download that firmware
* open the archive tar of that firmware and copy boot.img file to your phone (I've only read this once so confirm I have the correct file name).
* from your phone install magisk v22
* open magisk and options for direct install will lead you to patching the boot.img
* when that's done, move the patched file back to your computer and replace the original version with the patched one. it might be handy to keep a copy of the unpatched file safe in case you need it one day.
* from your computer flash the contents of that tar archive, you'll need to read a proper guide for this, the correct files need to be assigned to the correct partitions in Odin (the flash app for Samsung) and the names aren't all obvious. also you need drivers for Odin too, and a good version that works for this phone.
* one of those files that needs to assigned is called the CSC file, that deals with the region your phone is going to be (put simply). if you use your phones correct CSC file for the region of firmware you downloaded the data partition will be wiped.
to avoid that you can use the HOME_CSC file and data will not be wiped. on your initial first root you will have to wipe though to make sure your storage is not encrypted.
* you really want to follow guides for everything you're doing for the first time, don't rely on previous experience. Samsung phones are different to Pixels etc. some guides are written as if you'll know half this stuff already, if you don't it doesn't hurt to ask someone.
lol, I haven't actually rooted my own phone yet. I'm waiting to borrow a laptop plus seeing how things develop with TWRP / mods / new procedures.
Help - my S20FE is driving me to the point where I'll reactivate my 15 year old nokia...
Here's what I have:
S20FE (german t-mobile, SM-G780G DS), latest OS image (G780GXXU3DVK5), rooted with the latest Magisk version.
What I'm experiencing: the UI freezes up, then eventually restarts, every 5 to 10 minutes. Visually the only indication that it's not an actual reboot is the fact that it goes directly to the screen that only has "SAMSUNG" on it, without the screen with the "bootloader is unlocked" warning that you'd normally see first.
I'm pretty sure it is not a hardware issue, when it first started I did a full wipe / reflash, and then the phone worked fine for about a week or two, now it's doing it again.
Is there ANY way to actually see WHAT is crashing, and maybe even why? I already wiped the cache of that oneUI, and the whole cache from recovery, that did not help.
I guess I'm the only one here who has a S20FE.
Hi, did you manage to solve the issue? I'm currently on Android 11 One UI 3.1 but thinking about updating but I want to know everything first. I was reading that you can update without loosing root but I want to know that is safe first.
I am not completely sure yet but I believe I have it narrowed down to two apps.
I actually went back to the previous major version which was a pain all in itself, it's not easy to find downloads for older Samsung images... anyway, I am back on Android 12, and one UI 4.1, when the crashes start again....
eventually, I uninstalled greenify and kde-connect and the crashes have stopped so far.
kaliko1991 said:
Hi, did you manage to solve the issue? I'm currently on Android 11 One UI 3.1 but thinking about updating but I want to know everything first. I was reading that you can update without loosing root but I want to know that is safe first.
Click to expand...
Click to collapse
I have done updates w/o loosing root or data on magisk-rooted samsung devices, but it is a manual process.
1. use samfirm or frija to get the latest rom image zipfile for your device
2. unpack the firmware zip, you'll get 5 image files.
3. update the magisk app on your device
4. out of the 5 files from the firmware zip, copy the one that starts with AP_ to your device
5. use the magisk app on your device to apply magisk to that file
6. copy the file resulting in that patch back to your computer
up to here the process is the same as the initial install of magisk on a samsung, minus the unlocking of the bootloader.
7. get your device into download mode, and use odin to flash all four parts (BL, CP, AP, and this is important HOME_CSC). by flashing HOME_CSC instead of CSC into the appropriate slot you retain all user data!!
So far this was worked for me on a Tab S2, and a S20fe. Haven't tried on any other yet. YMMV.
I did everything just as described and I'm currently with a boot loop and eventually boots into stock recovery and ask me to do a factory reset. I guess it's over then, I'm loosing all my data.