Hello to all.
I need to ask here because Sony Forums sucks, so here the people has more knowledge
My phone is:
- G8142
- Unlocked Bootloader
- Android Nougat 7.1.1 installed from Sony Flashtool CE1 Firmware .137
- Kernel and drm patch from Xperifix
- Magisk 16.0
I installed (weeks ago) Android Oreo firmware Generic Lam, CE1 .75 till .145 (this last one not trying with CE1 firmware) downloaded from xperifirm and flash with newflasher v10 and v11, but somehow after flashing firmware, kernel (androplus) TWRP, DRM Patch, magisk, etc is working fine until a few hours (between 6 - 12 hours since boot and connected to network) wifi dropping can't reconnect, data is dead, voice call is dead too is very annoying because i have to restart de phone, tested with all oreo stock firmware to the latest even with locked bootloader had same problems (.75), i thought that unlocking BL was the problem or magisk but for some reason in Nougat i don't have any problems, none, zero. Some people in sony forums have problems with wifi, others with data, other with both, so my question, what would be the problem?
Greeting and Cheers.
You say your phone is Nougat in the bullet points, then say you've installed Oreo in the next paragraph. Which are you on right now?
You also said you're rooted with the DRM patch, then installed Oreo 'generic' firmware. I'd imagine if you are trying to install the stock Oreo firmware from Sony over a rooted and patched Nougat base, that may be causing you the problems if it installs at all.
More complete information might help others give you some advice.
ultyrunner said:
You say your phone is Nougat in the bullet points, then say you've installed Oreo in the next paragraph. Which are you on right now?
You also said you're rooted with the DRM patch, then installed Oreo 'generic' firmware. I'd imagine if you are trying to install the stock Oreo firmware from Sony over a rooted and patched Nougat base, that may be causing you the problems if it installs at all.
More complete information might help others give you some advice.
Click to expand...
Click to collapse
Hi, actually use nougat 7.1.1, but few weeks ago I flashed Sony firmware oreo (with newflasher) since. 75 to. 145 from scratch (no ota) to test adding DRM patch and magisk but all Oreo firmware failed in WiFi, data, voice, so, how Oreo is not for me right now I decide to flash nougat, that's how my question was born, why with Oreo firmware I'm having those problems?
Sent from my Sony Xperia XZ Premium using XDA Labs
Hakkinen3K said:
Hi, actually use nougat 7.1.1, but few weeks ago I flashed Sony firmware oreo (with newflasher) since. 75 to. 145 from scratch (no ota) to test adding DRM patch and magisk but all Oreo firmware failed in WiFi, data, voice, so, how Oreo is not for me right now I decide to flash nougat, that's how my question was born, why with Oreo firmware I'm having those problems?
Sent from my Sony Xperia XZ Premium using XDA Labs
Click to expand...
Click to collapse
That's my point. If you were already rooted and patched and you tried installing the stock firmware from Sony, that's going to cause you potential problems. Why don't you try flashing the Turbo or Carbon ROMs if you want to try Oreo and keep root?
Related
I unlocked my bootloader and relocked it with flashtool. Now I can only take photos on the camera app (same results with 3rd party apps). Any kind of video recording lags extremely or just gives me a blank screen and the fingerprint scanner doesn't respond. Like it's turned off. Any ideas how to fix this? I'm using the z5 premium e6853.
Thanks.
Mike3009 said:
I unlocked my bootloader and relocked it with flashtool. Now I can only take photos on the camera app (same results with 3rd party apps). Any kind of video recording lags extremely or just gives me a blank screen and the fingerprint scanner doesn't respond. Like it's turned off. Any ideas how to fix this? I'm using the z5 premium e6853.
Thanks.
Click to expand...
Click to collapse
How did you relock bootloader? with TA backup?
Try to use patched kernel.
Thanks for the reply. I actually just was about to report back that I fixed the issue. I flashed over the drm workaround with twrp.
I found it here:
https://forum.xda-developers.com/crossdevice-dev/sony/xperia-z1-z2-z3-series-devices-drm-t2930672
Happy to say everything is working perfectly now.
Will this work for 7 nougat on a z5?
I'm not sure. I flashed back to marshmallow to get it working. Then upgraded to the latest official firmware after.
i have even flashed back to marshmallow and still fingerprint is not working - has all the apk but doesnt look like its activating @Mike3009 are you able to give me the steps you used - i have tried numerous different processes
smiley.raver said:
i have even flashed back to marshmallow and still fingerprint is not working - has all the apk but doesnt look like its activating @Mike3009 are you able to give me the steps you used - i have tried numerous different processes
Click to expand...
Click to collapse
I'm pretty new to all of this so I'm not sure if this is the most efficient way to do it but here's what I did.
first I downloaded the official marshmallow firmware from xperiafirm and flashed it over with the latest version of flashtool. If you're bootloader isn't already unlocked, you should unlock it in flashtool. (needs to stay unlocked after too for this to work. I tried relocking it after and lost functionality) after you've flashed it over you need to get a modified kernel for your phone and firmware version. Flash that over and install the latest twrp. After that install the drm fix. Test if everything is working and if it is, download the latest official firmware from xperiafirm and flash over with flashtool.
Mike3009 said:
I'm pretty new to all of this so I'm not sure if this is the most efficient way to do it but here's what I did.
first I downloaded the official marshmallow firmware from xperiafirm and flashed it over with the latest version of flashtool. If you're bootloader isn't already unlocked, you should unlock it in flashtool. (needs to stay unlocked after too for this to work. I tried relocking it after and lost functionality) after you've flashed it over you need to get a modified kernel for your phone and firmware version. Flash that over and install the latest twrp. After that install the drm fix. Test if everything is working and if it is, download the latest official firmware from xperiafirm and flash over with flashtool.
Click to expand...
Click to collapse
Tried all that lol aw well I'm due for a new phone in a few months. I know mine isnt hardware related, but just something missing. Do you remember with MM firmware you got?
smiley.raver said:
Tried all that lol aw well I'm due for a new phone in a few months. I know mine isnt hardware related, but just something missing. Do you remember with MM firmware you got?
Click to expand...
Click to collapse
Try this drm fix. http://www.theandroidsoul.com/restore-drm-xperia-z5/
As for my marshmallow firmware, I'm in Taiwan so I used the only one listed on xperiafirm for Taiwan. Sorry I'm not able to use a Pc now to confirm.
are you on android 7.1.1?
Oops double post...sorry. Look below.
Yes. I didn't know to back up my drm keys before unlocking my bootloader and thought I was screwed. Now I'm on the latest 7.1.1, all drm functions working and I have root access. This drm fix works perfectly on the z5 premium e6853.(other models too but I can't personally verify)
Hey everyone.
I've stayed on Marshmallow since I got this phone, but now that Oreo has started rolling out on various devices, and Xposed is available for Nougat (I can't live without MinMinGuard anymore), I figured it's time for an upgrade to (stock) Nougat. I'm currently on EMUI 4.1, Android 6.0, version FRD-L09C432B131. Can I update to B403 without losing my data and access to root and Xposed? B403 is the highest version approved for installation for my device that I found through the Firmware Finder for Huawei app.
Googling on this issue hasn't left me much wiser; Can I just flash my stock recovery and boot partitions to enable the upgrade process, download and update through the firmware finder app, reflash newest twrp and then reflash supersu and xposed from twrp once on 7.0, all without losing my apps and data? I've used this phone as my daily driver for nearly two years, and I would like to avoid having to set it up from scratch as much as possible, as that's a pain-in-the-ass process that'll take me ages.
Anyone have any experience doing this? Any input is appreciated!
xdpirate said:
Hey everyone.
I've stayed on Marshmallow since I got this phone, but now that Oreo has started rolling out on various devices, and Xposed is available for Nougat (I can't live without MinMinGuard anymore), I figured it's time for an upgrade to (stock) Nougat. I'm currently on EMUI 4.1, Android 6.0, version FRD-L09C432B131. Can I update to B403 without losing my data and access to root and Xposed? B403 is the highest version approved for installation for my device that I found through the Firmware Finder for Huawei app.
Googling on this issue hasn't left me much wiser; Can I just flash my stock recovery and boot partitions to enable the upgrade process, download and update through the firmware finder app, reflash newest twrp and then reflash supersu and xposed from twrp once on 7.0, all without losing my apps and data? I've used this phone as my daily driver for nearly two years, and I would like to avoid having to set it up from scratch as much as possible, as that's a pain-in-the-ass process that'll take me ages.
Anyone have any experience doing this? Any input is appreciated!
Click to expand...
Click to collapse
You have root you will loose that , you need to flash it stock b131 as you have and go to hisuit i download the next version , after once updated go firmware finder and update new one update like c432b380 and next update is 382 you download it with FF and update and second is 391 you download id with FF and keep doing that until you reach the b403 i did that on my c432.
Hey guys,
after all these good messages (like DRM Backup/fix etc.) i consider to root my device finally, like i did with my old Z1. but im also interested in the new pie update to test it out. So im asking myself for some weeks now:
Should i finally root or wait till the update? i heard about the problem of downgrading that, once u get the update you couldn't downgrade to the exploitable fw. What's more, I want to keep my warranty (i know that drm backup is working but the message, that my device cannot be trusted is still there at every boot). i use several banking apps that checks for root and my experience with magisk and root hiding weren't so good at all.
Thats my current situation. Should i root or not?
Irrespective of the Android Version, Rooting on XZP requires you to UNLOCK the bootloader and loosing your DRM KEYS.
so the solution is either xperifix or posts in XDA offering kernels of specific builds for you to flash.
1. lets say you are on OREO and unlock your bootloader, if you wana root that oreo version, you must find the post on XDA offering modded kernels W.R.T that buildnumber for you to flash and flash drmfix.zip & finally flash Magisk.
2. let say you are on PIE, again you will do the same, but I am not sure they already have modded kernels available on xda or not. so make sure!!!
the third option is always (disputed tool on xda known as) xperifix.
YasuHamed said:
Irrespective of the Android Version, Rooting on XZP requires you to UNLOCK the bootloader and loosing your DRM KEYS.
so the solution is either xperifix or posts in XDA offering kernels of specific builds for you to flash.
1. lets say you are on OREO and unlock your bootloader, if you wana root that oreo version, you must find the post on XDA offering modded kernels W.R.T that buildnumber for you to flash and flash drmfix.zip & finally flash Magisk.
2. let say you are on PIE, again you will do the same, but I am not sure they already have modded kernels available on xda or not. so make sure!!!
the third option is always (disputed tool on xda known as) xperifix.
Click to expand...
Click to collapse
Im aware that i have to unlock the BL and all that stuff that i have to flash, thats not the problem at all. im just not sure if i should wait for the update (since some people experience some problems and they said they couldn't downgrade) and root or not. im currently waiting for the OTA update since my provider is vodafone and they take their time before releasing the fw. the benefits of the new updates, that i heard, are just some fixes for Android, new design for the camera ui, full hd ultra slow mo and some ui changes on xperia home. or did i miss some new functions?
If you unlook the BL, OTA didn't work anymore : so you must upgrade the phone by yourself. Via newflasher or (if you've a ftf file flash tool) you can up and downgrade when ever you want. I didn't know exactly in this this moment, how to hold the user data.... you lost in this moment only the feature video enhanced (something with X-....) if you unlook the BL and upgrade to Pie
Hi everybody,
I just bought a S8+ with firmware G955FXXU5DSFB - Pie - pre-installed.
After a couple of days (and nights), the frustration piled up:
- barely managed to install TWRP
- RMM protection and "only official released binaries are allowed" messages that seem to come up again almost randomly
- still didn't manage to root
- what's worse - this bootloader downgrade issue (which I've just found out about) - the bootloader cannot be downgraded - is it for real ?
The final question - how can I install a custom Oreo/Nougat custom ROM if I have the BL v5 ?
I guess all the custom ROMS have lower bootloader versions. Does this mean I am stuck forever with stock Pie ? That would be a really bad.
Since when did Samsung turn so bad ? My previous phone was a Note 4 - I haven't been following the xda/Android news for the past 5 years.
Thanks a lot, and as always - xda-developers rule !
I managed to root the phone with Magisk.
I tried to flash Omega ROM, but the phone was stuck at boot screen.
Can someone pmease confirm that there's no way I can install cuatom ROM?
Thanks.
Unfortunately you are stuck to Pie forever, it's also the case for me, got my s8+ with Pie (BL5) and didn't even try to downgrade to Oreo, coz it's impossible
I'm using Alexis Rom with NX Kernel now, everything is perfect, smooth along with 6h30 screen on time
Hi, thanks for the reply. Isn't there any version of Oreo that has BL5 ?
Anyway, had I known this stuff beforehand, I would have never bought the phone. I am sorry that Samsung went so wrong, locking down their phones so brutally. I owned only Samsung smartphones, starting with SGS1; most likely this will be my last Samsung.
realn said:
Hi, thanks for the reply. Isn't there any version of Oreo that has BL5 ?
Anyway, had I known this stuff beforehand, I would have never bought the phone. I am sorry that Samsung went so wrong, locking down their phones so brutally. I owned only Samsung smartphones, starting with SGS1; most likely this will be my last Samsung.
Click to expand...
Click to collapse
No, no oreo firmware with BL5 :/
I got mine for free so I'm not that bothered Plus I'm still enjoying oreo on my s7 edge
It seems that, in fact, there is a way of downgrading: I have now Oreo running on the device with BL5.
Please see below post
https://forum.xda-developers.com/ga.../test-u1ara2-devbase-v5-0-encryption-t3752964
Hello all
Been a member here for some time now and have a perplexing issue.
I upgraded a Samsung Device SM T395 to OS Pie 9 and decided I didn't like it. (There are no other posts with help on this matter)
I kept the STOCK roms Nougat 7.1 and Oreo 8 and want to put Nougat 7.1 back on my device , but is proving difficult using ODIN 13.3.1 or any other version of Odin. The result is FAIL, that's using a combination of AP, CSC, CP and BL.
I managed to get Oreo 8 back on it, but want Nougat 7.1 original installed instead.
Can anyone tell me can ADB Fastboot be used to Flash a Stock Rom back on a Samsung Device or is Odin the only method?
I know there are other similar programs like QFIL and Qualcomm that I have used for the Mi Max brand devices.
The device was rooted with Nougat 7.1 originally and I have USB debug set and FRP / OEM lock off also. So there's no problem there.
The last resort (stupidly expensive idea :crying is for me to buy another exact device that has Nougat 7 installed when boxed up!
I don't see how upgrading to Pie 9 and then wanting to go back to the original factory installed rom is a big problem, can anyone explain?
Would a CUSTOM Nougat 7.1 rom work if installed via TWRP ?
I have also come across this COMBINATION Software https://samsungcombinationfile.com/samsung-sm-t395 that is supposed to allow the downgrading of Android software, but hasn't worked as I had been lead to believe.
https://combinationfirmware.com/combination-samsung-galaxy-tab-active/
Thanks for reading :good:
tsam19 said:
Hello all
Been a member here for some time now and have a perplexing issue.
I upgraded a Samsung Device SM T395 to OS Pie 9 and decided I didn't like it. (There are no other posts with help on this matter)
I kept the STOCK roms Nougat 7.1 and Oreo 8 and want to put Nougat 7.1 back on my device , but is proving difficult using ODIN 13.3.1 or any other version of Odin. The result is FAIL, that's using a combination of AP, CSC, CP and BL.
I managed to get Oreo 8 back on it, but want Nougat 7.1 original installed instead.
Can anyone tell me can ADB Fastboot be used to Flash a Stock Rom back on a Samsung Device or is Odin the only method?
I know there are other similar programs like QFIL and Qualcomm that I have used for the Mi Max brand devices.
The device was rooted with Nougat 7.1 originally and I have USB debug set and FRP / OEM lock off also. So there's no problem there.
The last resort (stupidly expensive idea :crying is for me to buy another exact device that has Nougat 7 installed when boxed up!
I don't see how upgrading to Pie 9 and then wanting to go back to the original factory installed rom is a big problem, can anyone explain?
Would a CUSTOM Nougat 7.1 rom work if installed via TWRP ?
I have also come across this COMBINATION Softwarehttps://samsungcombinationfile.com/samsung-sm-t395 that is supposed to allow the downgrading of Android software, but hasn't worked as I had been lead to believe.
https://combinationfirmware.com/combination-samsung-galaxy-tab-active/
Thanks for reading :good:
Click to expand...
Click to collapse
Samsung firmwares can not be downgraded. This is due to your bootloader version number. The bootloader version is the 5th number from the right of the firmware being downloaded. You can also check in setting - about phone - software info - baseband version ( 5th number from right). You can also tell bootloader number in download (Odin) mode with a line saying AP SWREV B:? : K? : S?. The B is your bootloader number.
Combination firmware works on the same principle in regards to bootloader numbers.
You can only flash the same or higher bootloaders version numbers.
Custom roms will work as long as the bootloader version number is the same ( or higher ) than what is on you phone.
spawnlives said:
Samsung firmwares can not be downgraded. This is due to your bootloader version number. The bootloader version is the 5th number from the right of the firmware being downloaded. You can also check in setting - about phone - software info - baseband version ( 5th number from right). You can also tell bootloader number in download (Odin) mode with a line saying AP SWREV B:? : K? : S?. The B is your bootloader number.
Combination firmware works on the same principle in regards to bootloader numbers.
You can only flash the same or higher bootloaders version numbers.
Custom roms will work as long as the bootloader version number is the same ( or higher ) than what is on you phone.
Click to expand...
Click to collapse
RE: spawnlives. Many thanks for clearing that up, I now understand. Like many other people I have been trying to mix and match BL files from different OS variants to try and trick the device into accepting the main Nougat AP file via Odin, but nothing works.
These NEW combination files suggest that it is possible to downgrade the BOOTLOADER files on certain devices. However I downloaded all that was available for my device and tried the lot and found the only ROM that would flash correctly and properly was the latest one with the Binary 4 Bootloader. The rest would not register in Odin due to MD5 binary error messages.
In download mode my device AP SWREV B:4 K:2 S:2. ( So I have binary 4 which was released in January 2019, I believe). and this must have been updated when I updated to OS 9 Pie , using all the AP, CSC , BL and CP files.
So as you say, the answer is either , look for a Nougat 7.1 rom with a BL file that has a BINARY 4 code. Or buy another device that has the original Nougat 7.1 installed, which is silly really. :laugh:
Thanks :good:
tsam19 said:
spawnlives said:
RE: spawnlives. Many thanks for clearing that up, I now understand. Like many other people I have been trying to mix and match BL files from different OS variants to try and trick the device into accepting the main Nougat AP file via Odin, but nothing works.
These NEW combination files suggest that it is possible to downgrade the BOOTLOADER files on certain devices. However I downloaded all that was available for my device and tried the lot and found the only ROM that would flash correctly and properly was the latest one with the Binary 4 Bootloader. The rest would not register in Odin due to MD5 binary error messages.
In download mode my device AP SWREV B:4 K:2 S:2. ( So I have binary 4 which was released in January 2019, I believe). and this must have been updated when I updated to OS 9 Pie , using all the AP, CSC , BL and CP files.
So as you say, the answer is either , look for a Nougat 7.1 rom with a BL file that has a BINARY 4 code. Or buy another device that has the original Nougat 7.1 installed, which is silly really. :laugh:
Thanks :good:[/
The best you can do is roll back to Oreo. A new phone running nougat would be the best choice. I don't use custom roms but they all seem to keep up to the latest version. I have not seen one that ( latest version ) that is nougat favoured.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
spawnlives said:
tsam19 said:
spawnlives said:
RE: spawnlives. Many thanks for clearing that up, I now understand. Like many other people I have been trying to mix and match BL files from different OS variants to try and trick the device into accepting the main Nougat AP file via Odin, but nothing works.
These NEW combination files suggest that it is possible to downgrade the BOOTLOADER files on certain devices. However I downloaded all that was available for my device and tried the lot and found the only ROM that would flash correctly and properly was the latest one with the Binary 4 Bootloader. The rest would not register in Odin due to MD5 binary error messages.
In download mode my device AP SWREV B:4 K:2 S:2. ( So I have binary 4 which was released in January 2019, I believe). and this must have been updated when I updated to OS 9 Pie , using all the AP, CSC , BL and CP files.
So as you say, the answer is either , look for a Nougat 7.1 rom with a BL file that has a BINARY 4 code. Or buy another device that has the original Nougat 7.1 installed, which is silly really. :laugh:
Thanks :good:[/
The best you can do is roll back to Oreo. A new phone running nougat would be the best choice. I don't use custom roms but they all seem to keep up to the latest version. I have not seen one that ( latest version ) that is nougat favoured.
Click to expand...
Click to collapse
RE:spawnlives
Yes having researched the total list of softwares for the SM-T395 device, it seems the BL was updated to 4 on the 2nd roll out of Oreo 8.1. And having checked ALL stock Nougat variants, there was never any release of 7.1 with a bootloader binary 4!
I presume the BL Binary version is the 5 character from the right on the picture. (underlined red) :good:
It would make sense for Samsung to give the end user a choice what software they want, by keeping the BL version the same or giving a choice of BL selections to allow upgrade or downgrade.
Anyway, I rolled back to Oreo 8.1 with the binary 4 BL. And unfortunately there aren't many CUSTOM roms , nor a working TWRP for the Samsung Galaxy Active Tab2.
Thanks again :good:
Click to expand...
Click to collapse
Click to expand...
Click to collapse
tsam19 said:
spawnlives said:
tsam19 said:
RE:spawnlives
Yes having researched the total list of softwares for the SM-T395 device, it seems the BL was updated to 4 on the 2nd roll out of Oreo 8.1. And having checked ALL stock Nougat variants, there was never any release of 7.1 with a bootloader binary 4!
I presume the BL Binary version is the 5 character from the right on the picture. (underlined red) :good:
It would make sense for Samsung to give the end user a choice what software they want, by keeping the BL version the same or giving a choice of BL selections to allow upgrade or downgrade.
Anyway, I rolled back to Oreo 8.1 with the binary 4 BL. And unfortunately there aren't many CUSTOM roms , nor a working TWRP for the Samsung Galaxy Active Tab2.
Thanks again :good:
Click to expand...
Click to collapse
Yes the bootloader is 5th from the right.
I don't own a tab2. If no work twrp can be found and you want to at least have root try using magisk and used the patch root method.
Also to avoid possible upgrade turn off automatic updates in setting - software update as well as in developer option - auto update system.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
spawnlives said:
tsam19 said:
spawnlives said:
Yes the bootloader is 5th from the right.
I don't own a tab2. If no work twrp can be found and you want to at least have root try using magisk and used the patch root method.
Also to avoid possible upgrade turn off automatic updates in setting - software update as well as in developer option - auto update system.
Click to expand...
Click to collapse
Have rooted the device no problem with magisk and patching the original boot img file. Then flashing patched boot img via odin. Causing device verification to need to reformat the device, resulting in correct root.
Once a device , this device is rooted, no official updates can be installed anyway. When you try to uodate software, a pop up shows as the device recognises the software has been modified.
As for TWRP there ISN'T any version of TWRP available for the Samsung Galaxy Active Tab2 (SM-T395). I have even emailed the makers , developers of TWRP why there isn't one in their device inventory list on their webpage.
So no TWRP, and NO custom roms either for this model.
My concern , was all about finding a valid , safe way to downgrade back to original Nougat 7.1. And until someone can produce a working image with a BL with binary 4. Then there's only one optiin and that is to buy another untampered device with Nougat 7.1 out of the box and leave it un updated. :good:
Thanks for replying.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
tsam19 said:
Hello all
Been a member here for some time now and have a perplexing issue.
I upgraded a Samsung Device SM T395 to OS Pie 9 and decided I didn't like it. (There are no other posts with help on this matter)
I kept the STOCK roms Nougat 7.1 and Oreo 8 and want to put Nougat 7.1 back on my device , but is proving difficult using ODIN 13.3.1 or any other version of Odin. The result is FAIL, that's using a combination of AP, CSC, CP and BL.
I managed to get Oreo 8 back on it, but want Nougat 7.1 original installed instead.
Can anyone tell me can ADB Fastboot be used to Flash a Stock Rom back on a Samsung Device or is Odin the only method?
I know there are other similar programs like QFIL and Qualcomm that I have used for the Mi Max brand devices.
The device was rooted with Nougat 7.1 originally and I have USB debug set and FRP / OEM lock off also. So there's no problem there.
The last resort (stupidly expensive idea :crying is for me to buy another exact device that has Nougat 7 installed when boxed up!
I don't see how upgrading to Pie 9 and then wanting to go back to the original factory installed rom is a big problem, can anyone explain?
Would a CUSTOM Nougat 7.1 rom work if installed via TWRP ?
I have also come across this COMBINATION Software https://samsungcombinationfile.com/samsung-sm-t395 that is supposed to allow the downgrading of Android software, but hasn't worked as I had been lead to believe.
https://combinationfirmware.com/combination-samsung-galaxy-tab-active/
Thanks for reading :good:
Click to expand...
Click to collapse
To answer your question of how is downgrading such a big problem, it is due to security reasons, to keep your device as secure as possible with the newest available software and the latest security updates.
Sent from my SM-S767VL using Tapatalk