Database Develop

Flashing Firmware without wipe

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!

Moving from Oreo to Pie with no TA keys

Hi everyone,
I was one of the early "plungers" for the XZ1c, so I unlocked my bootloader without any TA key backup, flashed Oreo (47.1.A.12.145), and got by with Xperifix. But now I want to upgrade to Pie for a plethora of reasons (e.g. development).
I did a bit of reading here and there, and I came up with a set of steps for me to follow (and maybe anyone else who wants to attempt the same). Please do correct me if I'm wrong, and risk a brick:
Method A:
Backup all my stuff (a combination of manually, TitaniumBackup, Google, Sony)
Download the official stock firmware for Pie (47.2.A.10.45) via Xperifirm.
Flash Pie with a full format, to prevent any instabilities from apps.
Flash j4nn's bootloader unlock hide kernel to get root + Magisk (v18.1).
Restore backups.
Method b:
Backup all my stuff (a combination of manually, TitaniumBackup, Google, Sony)
Download the latest firmware and kernel for Pie (47.2.A.8.24) from janjan's thread.
Flash Pie with a full format, to prevent any instabilities from apps.
Flash janjan's kernel to get root + Magisk (v?).
Restore backups.
I'm leaning towards method A, as it'll be a newer version of Pie, but I do have some questions I couldn't manage to find a clear answer for:
Will Google Pay work with either method? This is kind of a deal breaker for me, as contactless payments are prevalent in my region.
Is there a reason to use Newflasher over Flashtool? I had used Flashtool for my XZ1c (even before they added official support in 0.9.24.3).
Does the gimmicky slo-mo video camera feature still work?
Is it possible to get TWRP with j4nn's method?

@TheFuzzy, concerning janjan's kernel, there is no drmfix included in pie releases, so that kernel seems to be only somehow tuned stock kernel.
My kernel releases are stock identical, no tuning at all, the only difference to stock is the kernel patch to hide bootloader unlocked state.
I believe this is a great benefit even in case of lost drm keys, if you need to use google pay or such apps. And yes, by following alternate use guide, my kernel can be flashed and used with twrp.
As tested by @russel5 (with some help and ideas from me), google pay now seems to use Android Attest Key (as I've expected long ago to happen) to truly detect bootloader unlock state.
In case you have Android Attest Key _working_ (see here to find out), even my kernel would not help to hide bootloader unlock (you can test that with the linked Auditor app even while running my kernel).
Destroying Android Attest Key seems to help to make google pay working as tested by russel5 - I did not test that myself, but @russel5 might confirm (thanks again for your testing and your finds, russel5).
But it seems to be irreversible change - we might still try to do some backup and restore tests...

@j4nn Thanks for the info! It is a bit confusing to keep up with the differences between the different methods.
I used your bootloader with 47.2.A.10.45, and it works like a charm.
I flashed your kernel directly as I'm not interested in FOTA. I've not tried to flash TWRP as I was afraid it might break the bootloader hide unlock patch (unless there is a specific order to follow, i.e. flashing it over TWRP or vice versa).
I ended up using Newflasher too, as I had read about not flashing the persist.sin file, and it seemed too tricky to do it with Flashtool.
One odd side effect is that I required the patched kernel to be flashed instead of booted from via adb, otherwise the device would boot loop and boot with the stock kernel instead.
I wasn't able to use your patched Auditor app as I don't have another phone at Nougat to verify. Indeed, Google Pay did pick up on the bootloader unlock status (maybe because of the Attest Key), but I was able to re-enable it using the SQLite trick mentioned here. My banking apps work fine with MagiskHide, too.

@TheFuzzy, you may use my patched Auditor app just with your single phone, which you like to check your attest key in.
Just install the patched Auditor and scan the QR code available on google play store in the Auditor's screenshots, instead of using a second phone.
That will trigger the verification just fine and then the audit results are simply displayed on the phone.

After upgrade to 9.0.4 => Error message "corrupt data" and no way from there

After upgrade to 9.0.4 => Error message "corrupt data" and no way from there
After upgrade to 9.0.4 (from 8.1, rooted with magisk) I was getting an error message "password is correct but data is corrupt... factory reset needed".
Factory reset? No way! I have a backup of the state just before upgrade to 9.0.4 (made with TWRP v3.2.3-0), and wanted to go back to that state.
First strange thing: This wasn't possible with TWRP v3.2.3-0 anymore because it needed to reformat /data with f2fs which lead to an error. TWRP v3.3.1-0 solved that issue.
After restore first I was unpatient, but waiting overnight finally returned my phone to the saved state (except that my internal storage was gone, because it was killed by the 9.0.4 upgrade).
But then it turned out that some things are not as good as before:
1) The fingerprint sensor is dead
2) "Calling" *#808# shows an error "Connection problem or invalid MMI code"
3) When re-entering TWRP the /data partition cannot be mounted (after a much too quick entry indicating that decryption did not took place)
What did the 9.0.4 update do to prevent the nandroid from 100% restore ? What can I do?
What do I need to do, to at least get my backup working just as it worked before?
What do I need for a successful upgrade to 9.0.4?

After spending major part of this weekend, this is what I found out so far:
1) Doing restore directly on the filesystem after 9.0.4 upgrade was the reason for the multiple strange behavior afterwards. Correct restore was like this:
- Flash a 5.0.8 stock firmware (!!!)
- Flash TWRP v3.3.1-0 (using v3.2.3-x would still fail with /data restore)
- Restore the backup, but leaving out the "system image"
2) After the successful restore, however, TWRP couldn't decrypt the /data partition. Flashing TWRP v3.2.3-1 was the solution for this.
3) BTW: The issue with *#808# was due to a non-stock dialer I was using. What misled me was that also the non-stock dialer was able to run some USSD codes, but strangely not all, and especially not the diagnostics one.
Ok, all issues solved so far, but now I'm on 5.0.8 again. And there I have this banking app, which once in a while tells me that "a phone with these settings is not supported due to high security standards" (meaning that it's rooted). In the past this issue has always been able to be fixed by firmware or magisk update. But right now magisk is at v19.3 and no update available. So, I need to upgrade the OS (I assume).
Is there a safe way to upgrade to 9.0.4 (or 9.0.5, which came out last Friday)?
Just an idea I'm having from the issues with TWRP version (one seems to work only with 5.0.8, the other only with 9.0.x): Might it be as simple as flashing a stock recovery just for the update? Or are there other things to obey?

ako673de said:
Is there a safe way to upgrade to 9.0.4 (or 9.0.5, which came out last Friday)?
Click to expand...
Click to collapse
The safe way is here:
https://forum.xda-developers.com/oneplus-3t/how-to/guide-cope-9-0-3-5-0-8-firmware-barrier-t3941164

Dirk said:
The safe way is here:
https://forum.xda-developers.com/oneplus-3t/how-to/guide-cope-9-0-3-5-0-8-firmware-barrier-t3941164
Click to expand...
Click to collapse
Hello Dirk,
I've read so many threads these days, to just confuse me even more. This is the very first really helpful tip.
Maybe I will try it out. But as for now the mixing of 5.0.8 and 9.0.x parts of the firmwares feels so desparately dirty, that maybe I should better try everything else first.
And here your other comments about banking apps were very interesting. Why exactly did you remove them later?
First of all I need to mention, that all my banking apps worked just fine until about 2 weeks ago. Basically everything is still perfectly alright: Safetynet is still being passed, the device is still "certified", magisk is still well hidden, and none of the critical apps "see" the root. Furthermore it's only one out of 4 banking apps that has stopped working (unfortunately it's the most critcal one with no alternative access (no website, no HBCI)).
So, could you please get a little bit more in detail?
I don't know enough about the details, but intuitively an unlocked bootloader might well be something a banking app could successfully look out for. But none of my research pointed me to a thread where the bootloader was successfully relocked with TWRP present. Could you please point me to that one?
The "LOS" thread, what exactly is that, and where? LineageOS? That's a branch from CyanogenMod, as far as I have read. What exactly does this ROM better wrt banking apps? I already had CM on my former Samsung S4, and it didn't work out very well. It was full of bugs...
And what exactly is "NLOS" (wrt banking apps)?
Thank you very much for your assistance.

ako673de said:
I've read so many threads these days, to just confuse me even more. This is the very first really helpful tip.
Maybe I will try it out. But as for now the mixing of 5.0.8 and 9.0.x parts of the firmwares feels so desparately dirty, that maybe I should better try everything else first.
Click to expand...
Click to collapse
If your aim is to be on the latest version of OOS whilst preserving Data, you need to use the modified Firmware.
LineageOS with latest TWRP allows you to relock your Bootloader. You wouldn't have any issues with Banking Apps with that setup. You can't get from OOS to LOS without losing Data though, and there's no point discussing custom ROMs further if your objective is to be on OOS.

Solved the banking app issue! It's the so called UDS detection method which was new and is not yet covered by magisk (incl. Beta), but the so called "canary" branch.
BTW: Bootloader is (should be) not something an app can detect with magisk in place.

Rooting device?

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.

How do I create a full backup in lun0, lun1, ... etc. form? (Excluding IMEI and SN and such)

I saw this video:
Which has a link to this "ATT_FullBackup.zip" which is AT&T Android 8.1.0 V405UA10l: https://drive.google.com/file/d/1Gy0crcs4D4JgaL5w3yalAD2QcJ7Lgg8v/view
The backup is in the form of lun0 through lun6 and it was really useful for unbricking my V405UA since this appears to be one of the only full backups of the AT&T firmware on the internet (so I can actually make and receive calls over VoLTE/HD Voice).
The flashing process only requires that you flash 7 times (rawprogram0.xml through rawprogram6.xml) as compared to some other backups I've seen where I think you'd need to flash around 80 partitions which would be tremendously tedious.
Also the same ATT_FullBackup link was posted here but with English instructions:
LGV40 - 405UA - ATT/Sprint - Custom Rom/TWRP/Unlock Booloader/Cross Flash/Recovery Guide/SAHARA Fix Etc.
This is just a story of my crazy adventures learning to flash the LG V40 which was by far the hardest phone I've ever rooted. But I learned a lot. I wouldn't reccomend this to anybody who isn't confident w/ Android/Computers etc, but if your...
forum.xda-developers.com
TL;DR: How do I make a lun0 - lun6 backup like ATT_FullBackup.zip except for my current firmware? Looks like this thread for the G8 has instructions but I'm not sure if the "num_sectors" is the same. I want to share AT&T Android 10 V405UA30e so people who don't have AT&T SIM cards or can't get OTA updates for some reason can get the update. Importantly we want to avoid overwriting the modem (?) or something like that to prevent messing up the IMEI and SN right?

laminarturbulent said:
I saw this video:
Which has a link to this "ATT_FullBackup.zip" which is AT&T Android 8.1.0 V405UA10l: https://drive.google.com/file/d/1Gy0crcs4D4JgaL5w3yalAD2QcJ7Lgg8v/view
The backup is in the form of lun0 through lun6 and it was really useful for unbricking my V405UA since this appears to be one of the only full backups of the AT&T firmware on the internet (so I can actually make and receive calls over VoLTE/HD Voice).
The flashing process only requires that you flash 7 times (rawprogram0.xml through rawprogram6.xml) as compared to some other backups I've seen where I think you'd need to flash around 80 partitions which would be tremendously tedious.
Also the same ATT_FullBackup link was posted here but with English instructions:
LGV40 - 405UA - ATT/Sprint - Custom Rom/TWRP/Unlock Booloader/Cross Flash/Recovery Guide/SAHARA Fix Etc.
This is just a story of my crazy adventures learning to flash the LG V40 which was by far the hardest phone I've ever rooted. But I learned a lot. I wouldn't reccomend this to anybody who isn't confident w/ Android/Computers etc, but if your...
forum.xda-developers.com
TL;DR: How do I make a lun0 - lun6 backup like ATT_FullBackup.zip except for my current firmware? Looks like this thread for the G8 has instructions but I'm not sure if the "num_sectors" is the same. I want to share AT&T Android 10 V405UA30e so people who don't have AT&T SIM cards or can't get OTA updates for some reason can get the update. Importantly we want to avoid overwriting the modem (?) or something like that to prevent messing up the IMEI and SN right?
Click to expand...
Click to collapse
The utility people use for backing up / restoring is the bkerler EDL utilities. They are easily found - use google and you'll get the git page.
On that page you'll also find an ISO the author created that you can flash to a usb stick. Once booted it's a complete linux setup with all dependencies to use the EDL utilities already resolved.
One note though, many people who've made backups fail to realize there are partitions (as you mention) that contain their imei and s/n. They are ftm, fsc, fsg, modemst1 and modemst2. Never flash those partitions from someone else's backup.
The Bkerler EDL stuff is written in python, and thus the interface is a command line / parameter one. It's a little daunting at first, but the documentation / --help parameter explains it pretty well.
cheers