Database Info

[Root] [guide] Samsung Galaxy A20 rooting guide

Read the first 3 posts before you proceed.
For Android 10 go here
https://forum.xda-developers.com/galaxy-a20/how-to/android-10-q-guide-a20-t4095589
For a20e go here
A20e Root,Kernel, TWRP and custom ROM
Root & TWRP from Xyn XDotnest https://forum.xda-developers.com/galaxy-a20/development/recovery-twrp-3-4-0-0-galaxy-a20e-a202f-t4141767 Orange Fox Recovery from @Royna...
forum.xda-developers.com
WARNING: Rooting your phone may be dangerous.
Rooting a device may void the warranty on the device. It may also make the device unstable or if not done properly, may completely brick the device. XDA-Developers or the author does not take any responsibility for your device. Root at your own risk and only if you understand what you are doing!

Advantages of rooting:
Once you root your device you can install flashable zip files and custom ROMs.
You can backup all your apps and data using Titanium Backup.
You can customize your device according to your needs by deleting unwanted system apps and using Deathly Adiutor to modify the kernel.
View attachment 4802662
Disadvantages of Rooting:
Once you root your device, your device warranty will be void.
After rooting yourndevice may become unstable.
You may not be able to upgrade OTA in the future.

This method should root your Samsung Galaxy SM-A205X (all models except SM-A205U and SM-A205DL).
It was developed for the U2 bootloader (June 2019 firmware)
This method does not work for the a20s (A207X)
This method can be used to root other Samsung phones including the a20e( post#77 post#180, post#256)
Quick Root and TWRP for A205xx
https://forum.xda-developers.com/galaxy-a20/how-to/guide-quick-root-twrp-galaxy-a20-t4069423
You'll find it much quicker.
Repair Firmware
This site contains
1. Full repair firmware
2. Combination firmware
3. Fix dm verify
4. Root instructions and unpatched boot images
https://www.full-repair-firmware.com/search?q=A20
More firmware (some are even prerooted)
https://www.needromarab.com/1/122/SAMSUNG
Samfirm Tool for really fast downloads
https://samfirmtool.com/samfirm-v0-5-0

Useful videos
Instructions
A. Prepare boot image
1. Download magisk manager apk
2. Download the exact firmware (including upgrade date) for your device from https://samfrew.com or https://www.samfirmware.net/ or https://www.full-repair-firmware.com/search?q=A20 or
https://samfw.com/
3. Use zarchiver to copy AP_20xxxxxxxx.md5 to download directory. It will extract it from the zip.
4. Rename AP_20xxxxxxxx.md5 to AP_20xxxxxxx.tar and extract using zarchiver
5. Copy boot.img.Iz4 to download directory and extract (resulting in boot.img)
6. Use magisk manager to patch boot.img (use top install) result magisk_patched.img
(If using Magisk (Canary) patch, options should be remove dm-verity and not via recovery, but allowing Persist Encrypt.)
7. Rename magisk_patched.img to boot.img
9. Use zarchiver to compress boot.img to boot.tar. If you have a A205xx June firmware (U2 bootloader), you can use my one of you're willing to take a risk. View attachment boot.zip. Just unzip it first.
9a. For a20e users, try this boot.img https://forum.xda-developers.com/showpost.php?p=81649257&postcount=260
10. Copy boot.tar to Windows pc or Windows Virtualbox.
11. On phone developer options in settings unlock OEM and enable usb debugging
(If using Linux
9. Don't compress `boot.img`
10. install heimdall flash with `sudo apt install heimdall-flash`, if you want front-end install it with `sudo apt install heimdall-flash-frontend`)
B. Unlock bootloader
Useful video
12. Backup data. It will be wiped.
13. Turn phone off
14. Hold vol- and vol+ and plug in power cable attached to pc then release vol up to enter unlock screen.
15. Follow the instructions to unlock
(You might need to long press vol up to unlock bootloader)
vol + to select yes to confirm.
17. Press power key to unlock bootloader.
18. Reboot and reactivate developer options and enable usb debugging. Don't enter too much data at this stage as you will lose it again later.
C. Flash boot image.
19. Turn phone on in bootloader (download) mode (Hold power and vol+ to enter recovery mode then select bootloader download mode)
20. Connect phone to computer.
21. Use Odin in Windows to add boot.tar to phone. (Select AP). Some people recommend adding the other firmware parts to their slots at the same time.
22. Restart phone
23. select bootloader
24. Select factory reset (this will wipe data)
25. Restart phone
26. install data
26. install magisk manager
27. If green phone is rooted.
View attachment 4802665
28. Of red select install/direct install
29. Advanced tick both.
30. Install root checker and verify root
If Something Goes Wrong
Go here
https://forum.xda-developers.com/galaxy-a20/how-to/crash-recovery-t4068369
If you get a DTBO error after updating Magisk, flash this vbmeta https://drive.google.com/file/d/1-dogButfxKGlx_x2tSROOBDiq90SDlmc/view
(If using Linux
To flash:
20. Detect device with `heimdall detect`
21. Flash the `boot.img` with `heimdall flash --BOOT {location of the boot.img, you can also just drop the file into terminal and terminal should auto-fill it}` ex: `heimdall flash --BOOT '/home/utku/Programlar/ext/boot.img'`
P.S: an easy way to boot into download mode is `adb reboot bootloader`)
If you want to remove the warning messages on the boot screen
try this.
https://forum.xda-developers.com/galaxy-a30/how-to/hide-bootloader-warning-unlocked-t3954589
The images shown on the A30 thread aren't suitable for the A20 so I have included some better ones here.
View attachment 4803752
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You can use this param.tar to make these changes easier.
https://forum.xda-developers.com/showpost.php?p=80169262&postcount=91
You can now move on to install TWRP
This TWRP was originally designed for Android 9 but works perfectly with Android 10 and also has MTP built-in.
https://forum.xda-developers.com/ga...overy-twrp-3-3-1-0-galaxy-a10-exynos-t4013481
physwizz collection
A collection of guides, kernels and ROMs. Guides Complete Guide to the A20 GSIs for the A20 Quick Root and TWRP for the A20 Making my First Kernel for the A20 A20 Rooting Guide Making Your Own ROM Making Your Own Version of QwizzROM-a20...
forum.xda-developers.com

Mine
Discussion page.
https://forum.xda-developers.com/t/samsung-galaxy-a20

On the lighter side of rooting....
From the A30 forum:
https://forum.xda-developers.com/galaxy-a30/how-to/hide-bootloader-warning-unlocked-t3954589
Works for A20 too

jajk said:
On the lighter side of rooting....
From the A30 forum:
https://forum.xda-developers.com/galaxy-a30/how-to/hide-bootloader-warning-unlocked-t3954589
Works for A20 too
Click to expand...
Click to collapse
Another reason to merge. This is a procedure for removing those annoying error messages on startup screens.

A205U owners complaining about not being able to oem unlock bootloader might want to study this:
https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
It looks like a way to switch to another unlockable firmware version.

Please, need magisk_patched.img file for SM-A205F.

jajk said:
A205U owners complaining about not being able to oem unlock bootloader might want to study this:
https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
It looks like a way to switch to another unlockable firmware version.
Click to expand...
Click to collapse
Yeah tried that option. Samsung has our model on a bootloader 2, means our device won't accept flashing from any other firmware but the original non-modded firmware only.
Tried prince Odin,patched Odin all versions, tried Heimdall etc..
Error is ...boot secure check failed..
I've tried to flash firmware a205G only with fail error Everytime.
Psa I've had my a205u for 10 days no OEM unlock option.
Main reason why I'm not buying another Samsung phone.
Bought a Moto g7 and the g7 power ..I rooted both within 10 min from purchase. Motorola emailed me my bootloader unlock code . Fastboot flashed and Bam good to go. I'm done .

jhjhjhjhjhjh said:
Bought a Moto g7 and the g7 power ..I rooted both within 10 min from purchase. Motorola emailed me my bootloader unlock code . Fastboot flashed and Bam good to go. I'm done .
Click to expand...
Click to collapse
^^^^^^^^^^^^^^^^^^^^^^^THIS ALL DAY. I swapped mine out for the G7 Power and already done rooted, flashed, and wrote a guide while all the 205u users are waiting for the mythical OEM Unlock to magically appear which it ain't gonna. Sammy can kiss my techie ass...we are officially divorced. I won't even go back and buy an old Sammy like I wanted to (was thinking about getting that S7 edge). It's me and Moto for now.

jhjhjhjhjhjh said:
Yeah tried that option. Samsung has our model on a bootloader 2, means our device won't accept flashing from any other firmware but the original non-modded firmware only.
Tried prince Odin,patched Odin all versions, tried Heimdall etc..
Error is ...boot secure check failed..
I've tried to flash firmware a205G only with fail error Everytime.
Psa I've had my a205u for 10 days no OEM unlock option.
Main reason why I'm not buying another Samsung phone.
Bought a Moto g7 and the g7 power ..I rooted both within 10 min from purchase. Motorola emailed me my bootloader unlock code . Fastboot flashed and Bam good to go. I'm done .
Click to expand...
Click to collapse
Maybe Samsung has an issue with US tariffs.

Samsung have certainly turned an essentially good piece of hardware into a pile of rubbish with mega-invasive bloatware. I have barely started to strip back the garbage and the phone is springing to life. Need a working TWRP before getting too keen as the path back to functionality is long and arduous without a way of restoring partitions if anything gets screwed up. Here is what the phone looks like with Google Play junk removed plus a bit of Samsung bloat removed - not everyone is ready to kick the Alphabet addiction I know, but it has become an absolute monster that eats battery and cpu cycles....apart from the privacy invasion side of it
I am finding that many unknown, non-visible apps with innocent sounding names or "security" inferred in the name are likely to be ad server or data mining software - I got wise to this with my first and last Xiaomi device

jajk said:
Samsung have certainly turned an essentially good piece of hardware into a pile of rubbish with mega-invasive bloatware. I have barely started to strip back the garbage and the phone is springing to life. Need a working TWRP before getting too keen as the path back to functionality is long and arduous without a way of restoring partitions if anything gets screwed up. Here is what the phone looks like with Google Play junk removed plus a bit of Samsung bloat removed - not everyone is ready to kick the Alphabet addiction I know, but it has become an absolute monster that eats battery and cpu cycles....apart from the privacy invasion side of it
I am finding that many unknown, non-visible apps with innocent sounding names or "security" inferred in the name are likely to be ad server or data mining software - I got wise to this with my first and last Xiaomi device
Click to expand...
Click to collapse
I used titanium backup first. Now I'll debloat.

physwizz said:
Maybe Samsung has an issue with US tariffs.
Click to expand...
Click to collapse
The US doesn't have an issue with South Korea on tariffs, despite Trump's big mouth.
The problem is that Sammy wants to be essentially Apple Android. And that is what's driving this crap in the same of "security". Knox has been like the devil and even sentient since it came to power almost like Skynet. And all of this started when Verizon offered Sammy big bucks to lock it down ala Kyocera with the S5 era - which coincidentially is the last great breath of air they had to give.
They don't care about the developer models either - look in the forums, many of them are just as locked down.
Sammy knows ain't that many phone companies left in the US; Tmobile done bought out half the cell companies and AT&T got the other half in a duopoly, meaning they and other companies can continue this path of nanny phones on the general public that are going for more personalized computers they can't control than actual phones that work. Most Americans aren't going to turn to GooPhone nor will many XDA devs develop any type of TWRP or rom for those types. And that means they can dangle a bells and whistle carrot while their demographic signs their privacy away.
I ain't a fan of Lenovo-Moto, but at least they let half the phone companies unlock the variant to their devices. Sammy, on the other hand, does not and is playing Xiaomi type of games on that bootloader.

Articul8Madness said:
The US doesn't have an issue with South Korea on tariffs, despite Trump's big mouth.
The problem is that Sammy wants to be essentially Apple Android. And that is what's driving this crap in the same of "security". Knox has been like the devil and even sentient since it came to power almost like Skynet. And all of this started when Verizon offered Sammy big bucks to lock it down ala Kyocera with the S5 era - which coincidentially is the last great breath of air they had to give.
They don't care about the developer models either - look in the forums, many of them are just as locked down.
Sammy knows ain't that many phone companies left in the US; Tmobile done bought out half the cell companies and AT&T got the other half in a duopoly, meaning they and other companies can continue this path of nanny phones on the general public that are going for more personalized computers they can't control than actual phones that work. Most Americans aren't going to turn to GooPhone nor will many XDA devs develop any type of TWRP or rom for those types. And that means they can dangle a bells and whistle carrot while their demographic signs their privacy away.
I ain't a fan of Lenovo-Moto, but at least they let half the phone companies unlock the variant to their devices. Sammy, on the other hand, does not and is playing Xiaomi type of games on that bootloader.
Click to expand...
Click to collapse
I find it strange that the US version is the only one that can't unlock the bootloader.
The rest of us are all unlocked and rooted.

physwizz said:
I find it strange that the US version is the only one that can't unlock the bootloader.
The rest of us are all unlocked and rooted.
Click to expand...
Click to collapse
It aint strange, its common. Before it was locked exclusively to Verizon; after the S3 it became more and more carriers. Then the dev models started being locked up but "open".

Articul8Madness said:
It aint strange, its common. Before it was locked exclusively to Verizon; after the S3 it became more and more carriers. Then the dev models started being locked up but "open".
Click to expand...
Click to collapse
Mine is locked to Vodafone but I can still unlock the bootloader.

physwizz said:
Mine is locked to Vodafone but I can still unlock the bootloader.
Click to expand...
Click to collapse
Same here.
Did you mod your param.tar (to change the warnings at startup) file by any chance? Would you be able to attach it at all? I was gonna download the firmware but it's taking 9 hours.
Thanks.

burningcreation said:
Same here.
Did you mod your param.tar (to change the warnings at startup) file by any chance? Would you be able to attach it at all? I was gonna download the firmware but it's taking 9 hours.
Thanks.
Click to expand...
Click to collapse
I've downloaded the 2 pics and I modified one to contain my name.
I will try the mods shortly.

[GUIDE] AN ESSENTIAL GUIDE FOR G935F/FD

AN ESSENTIAL GUIDE FOR G935F/FD​
DISCLAIMER☆THIS WILL BE A HUGE WORD WALL, SO DON'T BOTHER WITH THIS IN ADVANCE IF YOU MIND READING LARGE AMOUNTS OF WORDS ON SCREEN
☆THIS ISN'T A ROOT GUIDE EXACTLY BUT WHEN YOU READ THIS TILL THE END, ROOTING WILL BE AS EASY AS BREATHING FOR YOU (LITERALLY)
NOTE : THIS GUIDE DOESN'T APPLIES TO YOU IF YOU ALREADY KNOW BASICS AND/OR ARE ADVANCED USER WHO KNOWS GUTS OF ANDROID. THIS IS EXPLICITLY FOR NOOBS LIKE MYSELF WHO ACCIDENTALLY MESS THEIR DEVICES AND GET A BRICK !
WARNING : THIS DOESN'T APPLIES FOR ANY OTHER MODEL THEN G935F/FD, AND IS JUST FOR INFORMATIONAL PURPOSES, I WILL NOT BE RESPONSIBLE FOR ANY DAMAGE CAUSED TO YOUR DEVICE FOLLOWING THIS GUIDE.
P.SHERE I PRESENT MY FIRST GUIDE FOR S7 SERIES, YOU CAN SAY ITS A BASIC ROOTING GUIDE AND SUCH GUIDES ARE EVERYWHERE HERE ON S7 FORUMS BUT THIS ONE CONTAINS VITAL INFORMATION WHICH I COLLECTED FROM VARIOUS SOURCES AND TRIED KEEPING IT AT ONE PLACE AND FOR THE NOOBS LIKE ME WHO DON'T KNOW WHERE TO SEARCH FOR THESE THINGS
ALSO AS I RECEIVE HUNDREDS OF PM'S FOR HELP REGARDING PEOPLE ACCIDENTALLY TURNING OEM UNLOCK OFF AND MESSING THEIR DEVICES, I HAD TO MAKE A GUIDE NOW SO EVERYONE CAN BENEFIT FROM THIS
AND YEAH I CANNOT HELP ANYONE REMOTELY NOW, SORRY LIFE SUCKS IN AT TIMES
AND YOU GUYS KNOW THAT S7 SERIES ARE ALMOST EOL BY SAMSUNG SO I TRIED MAKING AN EOL GUIDE TOO
--------------------------------------------------------------------​
INTRODUCTION
EFS :
EFS (encrypting file system) is the partition which stores nv data of your phone, that is a read only partiton and it contains nv data (non-volatile data) memory which stores all the vital data from the manufacturer which is non volatile or in other words.. not to be removed/modified in any way.. and So, this nv data kinda makes your phone a 'phone'
UFS :
The UFS is universal flash storage chip also known as nand memory in older terms, your internal memory chip on the s7 edge series.. it contains all the android partitions of your phone i.e everything your smartphone has to be a 'smartphone' ..
DM-VERITY :
Device-Mapper verification is a new security measure in latest samsung devices, it basically checks system integrity i.e to check if system partition is modified by any method .. if your system partition is modified even willingly by yourself by any method like non-systemless root/mod/custom binaries etc, dm-verity will kick in and prevent your phone from booting normally. DM-verity is explicitly present in recovery partition which prevents boot on activating and it kicks in through a check inside the stock kernel which activates it.. apparently, removing dm-verity in recovery or kernel makes the device boot-able again.
DRK :
DRK or device root key is present in efs partition of your phone, DRK is a device-unique asymmetric key pair that is signed by Samsung's root key through an X.509 certificate, this certificate proves that the DRK was produced by Samsung. DRK is explicitly present in EFS partition. If due to any reason your drk gets corrupted/deleted, you get a permanent type of dm-verity error and your phone will not boot even stock samsung roms without dm verity disabler zips ..
NV DATA :
Non-volatile data is present on efs partition and includes, device specific vital manufacturer binaries which are never to be modified/removed in anyway. This includes device specific network certificates, IMEIs, SERIAL numbers, bluetooth ids/mac addresses, DRK, nfc parameters and others etc ..
PARTITIONS :
Android adopts linux like partitions and file tables, but most of the partitions present on samsung phones are not to be modified/messed up in any way, other then backing them up. The most common partitions to modify/format include :
1. DATA
2. CACHE
3. DALVIK CACHE
4. SYSTEM
But system partition is often recommended to not modify/format for the reasons I will explain further down in the guide ..
A partitions screenshot of s7 edge G935F running a stock rooted rom on version 8 binary
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The highlighted ones in yellow contain your nv data..
NOTE : ITS A VITAL STEP TO BACKUP ALL NV DATA PARTITIONS AFTER ROOTING (SHOULD BE THE FIRST THING TO DO AFTER ROOTING! )
PARTITION STYLE/IMAGE TYPE :
S7 series (exynos) partition table is A type on oreo stock firmware and until pie based custom roms.. one ui 2.0 introduced A/B style partitioning. Only difference between them is about how hard magisk implementation is in A/B and also the absence of ramdisk. You can get more info in magisk's documentation on github.
FIRMWARE TYPES :
All firmwares before the 10th binary update are called as A firmwares, the 10th or 0 one being called as A and after onwards from that we call the binaries as B firmwares i.e all firmwares from G935FXX1XXXXX to G935FXX9XXXXX will be called A firmwares simply, the 10th one being G935FXXAXXXXX and after that B firmware starts as G935FXXBXXXXX and then binaries continue like C/D/E/F if samsung wanted to update the device further.. S7 exynos are currently on 8th version binary.. where the binary number is actually the bootloader number and you cannot downgrade to lower version binaries from a higher version ..
Also the B firmwares are a very special case, will explain later further down later.
BOOTLOADER VERSION :
Refer to the above paragraph. Numbers/alphabets after XX and before XXXXX denote the version number of the binaries or in other words the bootloader version, which after upgrading to a higher version cannot be downgraded to a lower bootloader version ..
WHAT IS AP/CP/CSC/BL/PIT?
AP is Application Processor, known as PDA in older terms, the core android of the flashing package, CP being the Core Processor also known as modem, while CSC is Consumer Software Customization which contains regional/country based settings for your phone which includes network settings and custom preloaded software, also to mention that CSC has two types CSC and HOME_CSC ..
CSC contains the pit file which partitions and formats the phone before flashing in odin, while HOME_CSC doesn't include pit file and is meant to upgrade/dirty flash without wiping data in odin.. PIT means partition information table, if you are flashing CSC you don't need to manually extract and place pit file in odin as this is automatically done when flashed using CSC..
ODIN :
Odin, the lord of the dead as known in norse mythology is actually a lord of dead samsung phones too you already know what this is, but in case if you really don't; then this is a flashing software for samsung phones and you don't need to select any advanced options in odin when flashing.. just select auto-reboot and f.reset when flashing stock firmwares - all other options are obsolete and/or have no use for s7 series devices. Also when flashing any recovery don't tick auto reboot just f.reset and manually force reboot from download mode to custom recovery using key combinations
DOWNLOAD, RECOVERY MODE, SAFE MODE AND FORCE REBOOT :
While phone is turned off, holding vol down+home+power buttons will make you go in download mode.
And while phone is off, holding vol up+home+power buttons will make you go in recovery mode ..
Holding vol down after samsung animation comes during boot would make you enter in safe mode (this option is obsolete since in most bootloops we cannot go in safe mode because phone isn't booting properly to accept safe mode key input)
Hold vol down+home+power buttons on any screen to force reboot phone ..
DOWNLOAD MODE INFO :
There are details written in download mode which are very useful for diagnosing various issues.
Such as :
>Real Model Number : displays real phone's hardware model.
>System Status : displays intact-ness of /system partition.
>Binary Status : displays intact-ness of other partitions like boot (kernel) or recovery etc.
>KNOX Status : displays the hardware e-fuse status for warranty purposes. Anything other then 0x00 means its tripped.
>Letters B/K/S : letter B means bootloader version number, K for kernel's and S for system's version number. You cannot flash any firmware with lower numbers then displayed here because secure bootloader will always block it.
UPLOAD MODE :
There is not much info on this or any info at all for the matter. All I know per my personal experience is that it happened due to SBL (secure bootloader) error after flashing an incompatible firmware. It can be due to any other software or hardware reasons, but my guess is that it protects phone from becoming a complete brick in case of bootloader error or corruption. But again, its so scarce that hardly any reliable information exists about it and I'm not gonna brick my phone just to see if it really 'works'
FRP LOCK :
FRP lock is the factory reset protection, it kicks in two ways.
1. You had oem unlock off and you forgot to delete your/last google account on device before factory resetting it and for some reason you also forgot that google account's password, so this frp lock kicks in and you need to login with that last google account to regain access to your phone, this is basically an anti-theft measure, also ironically there were/are ways to bypass it too ..
2. If you disable oem unlock after rooting/modifying/installing custom binaries or you try to root/modify/install custom binaries without enabling oem unlock first, you get custom binary blocked by frp on next boot, for solving this you just need to flash back stock rom.. and login with last google account password if required ..
3. Its a bit same like no. 2, but this one is a dreaded and notorious issue.. happens when your drk or efs gets corrupted due to any reason and you also "Accidentally" turn OEM Unlock OFF (lmao) . Now when you flash custom binary you get the same frp lock as no. 2, BUT you cannot boot stock rom back to Enable OEM Unlock due to drk error/efs corruption (which prevents even stock rom from booting up because of dm-verity error) and you cannot fix drk/dm-verity error by flashing no verity zips.. because custom binary block by frp error.......
So now you know its not a good idea to do "Accidents"
COMBINATION BINARIES :
Combination binaries are troubleshooting firmwares developed specially for repairing by samsung which don't have dm-verity checks as well as no developer options either, which mainly can be used to fix imei/efs issues AFTER restoring a backup which you are SURE to be WORKING and taken from an earlier/working environment..
Sometimes combination roms can fix efs/imei and network issues without restoring a working earlier backup (in case of some software bug), though this only works if the original factory efs of your phone is intact ..
NOTE : AS OF NOW, LATEST COMBINATION ROMS FOR VERSION 7 AND 8 BINARIES AREN'T AVAILABLE ON THE POPULAR AND TRUSTWORTHY SOURCES - NOT EVEN ON PAID ONES. SO EITHER DON'T UPGRADE YOUR PHONES TO LATEST BINARIES OR DON'T MESS THEM UP SO THEY DON'T REQUIRE COMBINATION ROMS TO FIX THEM
--------------------------------------------------------------------​
MAIN GUIDE AND ISSUES TROUBLESHOOTING
NOW THAT YOU HAVE READ MY ENCYCLOPEDIA, I WILL BEGIN WITH MY DARWIN PHILOSOPHIES
1. DEVELOPER OPTIONS AND OEM UNLOCK :
Developer options are the first step when you want or even think of modifying/rooting your device in anyway. You go in about section of your phone and tap build number 8 times to enable developer options and then you need to ENABLE OEM UNLOCK BEFORE MODIFYING/ROOTING YOUR DEVICE IN ANYWAY POSSIBLE
FLASHING ROMS AFTER ENABLING OEM UNLOCK DOES NOT CHANGE ITS STATE
BE WARNED : CLEARING DATA OF SETTINGS APP OR FOLLOWING ANY GUIDE ON INTERNET TO DISABLE DEVELOPER OPTIONS AFTER ROOTING/MODIFYING YOUR PHONE CAN RESULT IN OEM UNLOCK BEING TURNED OFF AND YOU GETTING THE CUSTOM BINARY BLOCKED BY FRP MESSAGE
AND YES PLEASE DON'T ACCIDENTALLY TURN OEM UNLOCK OFF FOR HEAVEN'S SAKE
2. USB DEBUGGING :
Although not vital, but usb debugging is needed for using adb from your pc and adb has many useful commands if you like digging in the linux shell, plus many no-root apps require adb commands to make them run some useful functions without root.. I recommend keeping it on just in case.
3. DM-VERITY ERRORS :
Ah yes, I hate this one, this is one of the most notorious errors I have ever seen, DM verity as told above is a system integrity check for modifications, but this dm-verity thing on occasion can make a hard brick coupled with some kind of encryption in the kernel/bootloader, Master @Chainfire describes such behaviour in one of his posts here, it was on nougat though and I can only expect it to be worse on oreo ..
https://forum.xda-developers.com/showpost.php?p=72204306&postcount=978
In simple terms a s7 can become a partial hard brick IF user had no access to a working rom (due to dm-verity) and custom recovery is broken/can't be flashed (due to OEM Unlock being turned off) ..
What worries me most, is that I could not get my device in any sort of booting state without formatting /data and /cache in recovery (something that you would normally be able to do through ODIN by flashing empty images). This means that if you end up in this broken state and for any reason recovery isn't functional, your device may be unrecoverable and essentially bricked. It is certainly not unheard of to have a broken recovery, especially on Samsung devices. Combine the two, and it is a certainty that some users will eventually end up bricked.
Click to expand...
Click to collapse
So, if anyone modifies their system partition after root without disabling dm-verity check in the stock kernel or they root using non-systemless method or they did a swipe for system modifications in twrp or they installed any non-systemless mod, they get dm-verity error.. For most part a dm-verity error due to a modified system partition on a rooted phone can be easily fixed by flashing no-verity zips in twrp recovery ..
OR by flashing a stock firmware of matching binary through odin ..
Even if you have accidentally turned oem unlock off, you simply reflash stock firmware and go in developer options to re-enable oem unlock. This is what I call type 1 dm-verity which is the easy one to fix ..
NOW, lets see another scenario where some people accidentally turned oem unlock off (yeah believe me there are tons of users doing this these days lol) and for those people dm-verity was not going away even after a stock firmware reflash and because they turned OEM UNLOCK OFF they could NOT flash custom binaries to bypass dm-verity either.. HENCE THEIR DEVICE WAS IN A STATE OF SEMI-PERMANENT HARD-BRICK..
My search revealed that a corrupted/missing DRK in EFS partition was actually the root cause of this type of dm-verity error, such unfortunate users CANNOT EVER REVERT BACK TO A STOCK UNMODIFIED ROM (without restoring an intact DRK backup) and they ALWAYS HAVE TO FLASH NO VERITY ZIPS TO USE/BOOT STOCK ROM..
But if OEM UNLOCK IS TURNED OFF, they get STUCK BADLY because device rejects any custom binaries like no-verity zips and twrp etc ..
My further search concluded that since the stock recovery kicked in dm verity, So if the AP file of firmware is extracted and stock recovery is deleted from it, while the boot.img is renamed as recovery.img and only system.img alongwith renamed recovery.img is repacked and flashed alongwith BL, CP and CSC, it allows users to BOOT into stock rom to ENABLE OEM UNLOCK AGAIN and use their device with custom binaries, and so their device is back to the living once more
The exact steps are as follow :
1. Extract the correct matching-binary firmware package.. then extract the AP file, and copy boot.img and system.img to a new separate folder ..
2. Rename boot.img to recovery.img and repack this renamed recovery.img alongwith system.img (only these 2) using autotar tool (I've posted the link to autotar tool now although it gets detected as a virus, So download at your own risk) or any other tar packing utility ..
AutoTar Tool
3. Flash this modified AP using latest odin along with BL, CP and CSC (not HOME_CSC) and only tick auto reboot and f.reset in odin options ..
Your phone should boot now and you can ENABLE OEM UNLOCK to flash custom binaries and make your phone usable again.. personally tested that this method works ..
BE WARNED THAT THIS METHOD REQUIRES ATLEAST 10% BATTERY FOR FLASHING AND BOOTING
Since many devices had been hard bricked for months and battery being drained completely, they couldn't boot or complete flash due to their phone becoming dead in the middle of flashing process or booting process ..
I recommend charging phone by a wireless charger in this state (since wireless charger is said to be working even in bricked state, also connecting it to a charger while in download mode may give it some charge) or simply try continously to boot it, if flash using above method is successful then don't reflash anymore just try to boot phone while putting it on charger ..
And hopefully your device will get out of this dreaded dm-verity + frp lock due to custom binary ..
Here's my original post for such dm-verity fix : https://forum.xda-developers.com/showpost.php?p=82294339&postcount=11
WARNING : MULTIPLE INTERRUPTED/INCOMPLETE FLASHES DUE TO NO BATTERY OR BATTERY DYING IN THE MIDDLE OF FLASHING PROCESS CAN CAUSE PERMANENT UFS CHIP HARDWARE DAMAGE !!
END NOTE : ALL OF DM-VERITY ISSUES ONLY HAPPEN ON A FULLY STOCK ROM WITH STOCK BOOT/KERNEL AND STOCK RECOVERY, ONCE A CUSTOM ROM OR CUSTOM BOOT/KERNEL AND CUSTOM RECOVERY ARE FLASHED, THEN THERE MAY NOT BE A NEED TO FLASH NO VERITY ZIPS, BECAUSE DM-VERITY MAY ALREADY BE DISABLED IN THE CODE. REFER TO YOUR RESPECTIVE ROM THREAD FOR THE REQUIRED INFO.
4. FORCED ENCRYPTION :
My personal experience and testing with root on android 8.0 stock oreo made me conclude that for some reason, the latest twrp as well as tkkg's modified twrp (which only supports quota) fails to mount /data even after formatting, when we reboot first time into system after formatting data and then go again in twrp, twrp fails to see /data again ..
Well, this is not a huge problem BUT if due to any reason your phone got in a non-fixable bootloop and you still got valuable data on it, then there's no practical way to recover it, except copying and moving it from twrp to external sd card/usb otg ..
So yeah an accessible /data is a big factor for me to have it working ..
Tkkg's post on encryption : https://forum.xda-developers.com/showpost.php?p=77296095&postcount=2228
link where he says he hasn't added encryption support : https://forum.xda-developers.com/showpost.php?p=77314388&postcount=1251
I first thought that latest official/tkkg's twrp would have fixed this problem, but even when forced encryption is disabled using zips, every twrp I tried could not see /data partition ..
EDIT : OFFICIAL TWRP 3.3.1+ WORKS BUT WE NEED TO FLASH MAGISK RIGHT AFTER BOOTING TWRP FOR FIRST TIME AFTER DOING A FORMAT DATA UNDER WIPE OPTIONS, AFTER THIS REBOOT TO SYSTEM, AND ENCRYPTION WON'T COME BACK AND YOU WOULD BE ABLE TO ACCESS DATA AFTER EVERY REBOOT IN TWRP !!! SEEMS LIKE IF NO MAGISK = NO /DATA ACCESS IN TWRP OR IN OTHER WORDS "FORCED ENCRYPTION"
5. ODIN ISSUES :
Many users on the forums reported issues with flashing via odin, my own experience and research tells me it can be due to :
》You're using a wrong model firmware.
》You're using a counterfeit/modified phone whose real hardware model is different then what's displayed.
》Your phone's internal nand storage hardware got faulty and fails to write anything on it.
》Odin's version is wrong and/or you got a fake software (can happen when downloading odin from fishy webs)
》Either your PC/Samsung usb drivers/usb cables/usb ports got some bugs/issues.
》Smart switch is running in background processes and it is known to mess with odin flashing (often that's the culprit)
You can try to download odin from a reputable web, re-verify that you're using correct firmware and smart switch isn't running as a background process. Also try checking with some other usb cables/ports or PC. Also verify that your phone isn't a counterfeit product (hardware modified)
If you were already rooted or flashed a custom rom before, and you're sure that OEM Unlock is enabled in developer options, you can try flashing twrp in odin and then a custom rom through twrp - as a last resort. But if you haven't rooted/enabled OEM Unlock before, this won't work either and you may had to take your phone to a repair shop
Heads Up : Incase you didn't knew, but if odin fails a flash or flash gets interrupted at or during sboot.bin (the bootloader flashing step) or you flash a wrong bootloader which unfortunately download mode couldn't stop from getting flashed, it can cause hard bricking due to corrupted bootloader (no download mode) and can only be fixed via UART interface using a hardware repair box. Ofcourse this doesn't include failed flashes at sboot which are due to download mode blocking the flash (its actually protecting itself from flashing a wrong/incompatible bootloader)
6. ROOTS AND SYSTEM-LESS ROOTS :
I guess in all my rant you must have noticed that the biggest problem comes in when efs partition becomes corrupted specifically, now when i searched countless pages of users and their issues I came to conclusion that somehow ROOTS using system modifications and also TWRP with system modifications enabled HAVE A HIGHER CHANCE TO MESS/CORRUPT EFS PARTITION, specifically the FULLY MODIFIED CUSTOM ROMS OUT THERE (AND NO I AM NOT BLAMING ANY CUSTOM ROM OR DEV, JUST THAT A FULLY ACCESSIBLE SYSTEM PARTITION HAVE MORE RISK OF CORRUPTING EFS PAR MY OBSERVATION- I hope to be wrong lol)
Now, thats where system-less roots come in !!
THEY ARE SIMPLY AWESOME AND NOT BECAUSE I AM A FANBOY OF MAGISK BUT BECAUSE THEIR ACCESS TO SYSTEM PARTITION IS TOTALLY INDIRECT WHICH INTURN PASSES SAFETY NET CHECKS TOO.
SYSTEM-LESS ROOTS ARE ONE OF THE BEST EVOLUTION OF ROOTS, IN MY VIEW SYSTEM-LESS ROOT AND SYSTEM-LESS CUSTOM ROM DEV BASE ARE ONE OF THE BEST ROOT AND ROM RESPECTIVELY NOT BECAUSE IT ONLY PERFORMS WELL AND FEELS STABLE BUT BECAUSE IT HAS THE LEAST TENDENCY TO CORRUPT EFS BECAUSE IT IS MUCH MORE CLOSER TO STOCK ROM! A BIG SHOUT OUT TO @_alexndr FOR HIS SUPERB SYSTEM-LESS DEV BASE.. AND THE BEST THING IS THAT DOWNLOAD MODE REPORTS SYSTEM AS OFFICIAL AND PASSES SAFETY NET EVEN WHEN YOU'RE ROOTED AND USING EDXPOSED !
THAT BEING SAID, THE BIGGEST REASONS OF EFS CORRUPTIONS ARE NOT DUE TO CUSTOM ROMS, BUT DUE TO THE VARIOUS MODS AND INCORRECT FOLLOWING OF FLASHING/INSTRUCTIONS WHICH CAUSE THIS.. AND SOMETIMES FAULT/ERROR OF THE HARDWARE TOO.. AND VERY RARELY ITS A MISTAKE ON DEV'S PART ..
Moving on to root types, you got Super SU along with its system-less root option and Magisk (has system-less root as default); both have hiding root options as well, you just need to choose your preference and flash it in twrp.. I really don't recommend king root or any other root types !!
FOR USING SYSTEM-LESS ROOT KEEP SYSTEM READ ONLY IN TWRP!!! (DO NOT SWIPE TO ALLOW SYSTEM MODIFICATIONS WHEN BOOTING IN TWRP FOR FIRST TIME AND TICK DON'T ASK ME AGAIN)
BE AWARE ! CHOOSING SYSTEM MODIFICATIONS IN TWRP WILL AUTOMATICALLY CAUSE NON-SYSTEMLESS ROOT METHOD !
ALSO : WITH MAGISK ONE NEEDS TO FLASH IT AFTER FLASHING NO VERITY ZIPS IN TWRP (IF USING MAGISK IN NON-SYSTEMLESS MODE OR DUE TO DRK BEING CORRUPTED)
Please note that CF Auto root is now obsolete for s7 series on version 5+ binaries ..
7. BOOTLOADER EXCEPTION BUG (SBL ERRROR) :
Another rare and possibly dangerous bug, ironically I encountered it on my first days of getting this device
That screen was terrifying for a noob like me at that time lol, now how did I got it in first place ?
Yeah I tried to be a smart-ass and flashed a normal bootloader along with a combination firmware in odin lol (tried to bypass bootloader blocking flash of lower binary version), flash was successful and when phone booted it caused bootloader exception bug ..
And what I did to solve it ? Simply hold home button until you see upload mode and then force reboot by combination keys and then immediately hold download mode combination keys to go in download mode and reflash stock rom
Seems like other people on forums weren't that lucky to get out of this error easily
Possibly, this error can also be caused by some hardware fault/bug.
Further investigation revealed that SBL error (secure bootloader error) is particularly a semi-corrupted bootloader which in reality would cause the device to become a hard brick which can only be recovered through UART interface using a hardware box (which essentially requires us to open phone's guts), but instead it caused bootloader to get in a fail-safe 'UPLOAD MODE' which is surprising actually because any wrong bootloader flash is sure to make your device a permanent brick.
So better NOT cross-flash firmwares or bootloaders not designed for your phone, specially which are apparently made for same hardware as yours but you may not be that lucky to get in upload mode after that, So :
>Don't try to flash a G935F (global) bootloader on a G935W8 (Canada variant) or G935V/T/A/U (US variants) or G9350/K/L/S (Chinese/Korean/Hongkong variants etc) and vice versa.
>Don't try to flash a G9350/K/L/S (Chinese/Korean/Hongkong variants etc) bootloader on G935V/T/A/U (US variants) or G935F (global) or G935W8 (canada variant) and vice versa.
>The above instructions includes both normal and combination firmwares. Also don't try to flash normal firmware's bootloader with combination firmware or vice versa.
>Don't try to downgrade bootloader by 'any method'..
>Don't use any 'patched odin' to flash an incompatible firmware.
>Don't try to flash bootloader using flashfire/twrp or any other mobile flashing utility.
8. NETWORK AND IMEI'S ISSUES :
Regarding loss of network signals, there are 2 possibilities, either that your imei got deleted/corrupted due to a bad efs partition or your phone's imei was changed and a network certificate patch was used to make it working, and you reflashed your phone through odin or any other flashing method which removed that network certificate patch and you lost your signals ..
Now both can be fixed only by a box or box-like alternative see this thread link for more info :
1. https://forum.xda-developers.com/s7-edge/how-to/fix-imei-downgrading-g935f-fd-t3947911
Remember : There's always a risk of bricking your device or screwing it further by using such (box-free) tools ..
Moreover, signals can be lost when flashing old modem on newer bootloader, it can be fixed by reflashing correct firmware (matching bootloader version) for your phone ..
Signals can also be lost by a bugged out csc (probably due to a bad efs), for solving this you can try changing your csc code by flashing different csc firmware with matching bootloader version (preferably a single csc firmware like dbt/xeu) and then reflashing your original csc to revert back and applying the fix mentioned in No. 1 thread link above.
A bugged out/corrupted efs is often the main culprit for signals issue, which needs combination rom with matching bootloader version and/or an earlier working efs backup to fix it.
See this thread link below for more on this :
2. https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-fix-check-drk-imei-issues-t3379516
Another option is if you got an older working efs backup, just restore it and then give appropriate permissions and then flash combination rom for your rom, but problem is.. you need quite a bit of linux command knowledge and updating the permissions according to your own phone and android version (originally it was done on note 4) plus combination roms for latest binaries are not getting released into public now !!
Please refer to this thread link of note 4 below :
3. https://forum.xda-developers.com/note-4/general/fix-drk-dm-verity-factory-csc-serial-t3422965
As a token I provide my phone's DRK, the prov_data folder (for getting rid of dm-verity error by following No. 3 thread link of note 4 above).. if anyone experienced and interested enough wants to experiment to fix their drk/dm-verity errors permanently ..
NOTE : As policy of xda, I'm not sharing any imei/personal phone data, but just a DRK encrypted key which could benefit users with dm-verity and drk errors, if anyone finds it against xda's terms or rules, feel free to report my shared prov_data (but it has already been shared before for note 4)
BUT EVEN WITH THIS PROV DATA AND SUCCESSFULLY GIVING PERMISSIONS YOU WOULD STILL NEED COMBINATION ROM TO FIX DRK AND SIGNALS/IMEI AS STATED IN NOTE 4 THREAD !
ALSO THIS WILL ONLY WORK ON DEVICES BEING ROOTED AND IN WORKING CONDITION !
TIP : WELL, SOMETIMES YOU TRAVEL ALL THE WORLD TO FIND SOMETHING WHEN ITS ALREADY THERE IN YOUR HOME OR NEIGHBOURHOOD AND SAME THINGS CAN HAPPEN WITH THESE ISSUES TOO, IN THE END YOU DID EVERYTHING YOU CAN TO TRY AND GET YOUR SIGNALS FIXED WHEN YOU JUST HAD TO REPLACE YOUR SIM CARD LOL
SO YEAH SIM CARD CAN BE FAULTY TOO, ALWAYS TRY CHANGING SIM CARDS FIRST IF YOU GET ANY NETWORK ISSUES. ALSO, SOMETIMES ITS THE PHONE'S MODEM HARDWARE THAT'S FAULTY AND YOU CAN'T DO ANYTHING ON THE SOFTWARE SIDE.
9. BATTERY DRAIN ISSUES :
Ever since the version 7 binary update i.e december 2019 security patch and later, I noticed my phone draining battery heavily due to android system and kernel.. and I lost almost 50% of s.o.t and also created this warning thread here :
https://forum.xda-developers.com/showpost.php?p=81410317
SO YEAH. I RECOMMEND USERS TO NOT UPDATE TO VERSION 7 BINARIES OR LATER !! IT WILL ONLY CAUSE A DELIBERATE SAMSUNG CREATED BATTERY DRAIN TO PUSH USERS FOR UPGRADING THEIR PHONES !
10. BINARY UPDATES :
Since samsung has officially made s7 series eol, the updates they will now push would always to some extent, try to limit device in some ways - like the huge battery drains with version 7+ binaries and the fact that you cannot downgrade, the whole point is that they want users to upgrade their phones and hence they will push such updates which will further limit our device !
Also let me tell you, once S7 reaches Version 11 or in other words 'B' binary, its stated that twrp will not work and I think even root will be much harder to achieve and sustain.. if I'm wrong then I request someone to please correct me
ALL IN ALL, UPGRADING BINARIES WILL ONLY CAUSE YOU TO BE STUCK ON EVEN WORST FIRMWARES !!
I REALLY RECOMMEND TO NOT UPDATE YOUR PHONES ANYMORE !!
11. PERSONAL RECOMMENDS :
I am not the one to recommend anyone something but if you do want to get root but want stability, unmodified system-partition, less risks of your phone being messed up or simply you care for your phone's health; this is still a great phone
I heavily recommend alexndr's custom devbase rom or if you don't want that debloated stock rom, you can just use his system-less devbase root option too.. along with system-less Magisk ..
AND MY BIGGEST RECOMMENDATION IS :
ALWAYS BACKUP YOUR EFS AND NV DATA PARTITIONS FIRST THING AFTER ROOT !!!
This is it from this noob guide of mine, thanks for reading such a long "rant", I hope it would benefit you. My original aim was to create an END OF LIFE GUIDE for S7 series combining various info, and I think I'm partially successful in it
I'm always open to add new info and/or correct anything which I mentioned wrong, also if you need any help feel free to post a reply.. I'm not able to help remotely anymore though
But no matter, all the info I learned remains archived in this thread till the end of times
USEFUL LINKS :
ODIN
ODIN
SAMSUNG STOCK ROMS
SAMSUNG USB DRIVERS
OFFICIAL TWRP
SUPER SU
SUPER SU
MAGISK
MAGISK
SYSTEM-LESS ROOT DEVBASE
SYSTEM-LESS DEVBASE ROM
NoVerityOptEncrypt
NoVerityForceEncrypt
ALL CREDITS TO THEIR RESPECTIVE CONTRIBUTORS​

.............................

shah22 said:
.............................
Click to expand...
Click to collapse
https://www.reddit.com/r/GalaxyS7/comments/qn5q99
What do you think about that problem?

[GUIDE] Cherry Mobile Flare S8 Rooting, Bootloader Unlocking, ROMs, TWRP [09/30/20]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this Kernel
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
This is a (more updated) tutorial thread made for those who are having difficulties following the guides that were provided by others.
Welcome to the guide thread of Cherry Mobile Flare S8 (series) that I made.
Here, you can learn more about unlocking its bootloader, rooting it, flashing treble GSI images, and flashing custom recoveries. If you have the right device, then this is the right thread made for you.
If you are not a Flare S8 user but you are holding a device included in the Flare S8 series, don't worry because I will be creating a guide for them, too! Stay tuned for more updates.
ADDITIONAL NOTE
Please make sure that you have already read the disclaimer above because we are not taking responsibilities of any kind when something bad happens on your device. As always, do it at your own risk and proceed with caution.​
Unlocking the bootloader is very simple. But before that, make a backup of your files first because after unlocking a bootloader, it performs a factory reset.
THIS IS A VERY IMPORTANT STEP. AN UNLOCKED BOOTLOADER HELPS YOU MODIFY YOUR DEVICE EASILY. HOWEVER, IT VOIDS YOUR WARRANTY.
YOU HAVE TO UNLOCK THE BOOTLOADER FIRST BEFORE ROOTING. (Yes, rooting your device doesn't require an unlocked bootloader, it's just recommended.)
To unlock the bootloader of your device, first, install ADB drivers on your PC. You can choose to install them manually or to install them with ease by using the 15-second ADB installer.
Download the 15-second ADB installer, here.
After installing the ADB drivers, open your device and locate to "About Phone." Click the "Build version" five times to enable the Developer Options in the Settings. After that, go to Developer Options and toggle USB Debugging. After toggling USB Debugging, connect it to your PC and wait until it recognizes your device. If it didn't recognize your device, make sure that the ADB drivers are installed properly.
If you're done, locate your PC to any folder and launch the command prompt (It's Power Shell if your PC is running in Windows 8-10; you can make the command prompt option appear in the menu by clicking shift and the right button of your mouse simultaneously.)
Here are the lines that you'll be required to execute when unlocking your device's bootloader.
First, reboot your device to fastboot.
Code:
adb reboot bootloader
After rebooting your device to fastboot, check it if it's detected by your PC by executing this line.
Code:
fastboot devices
If you can see the serial number of your device, followed by its name in the command prompt. Congrats! Your device is now detected in your PC. (A serial number is like an IMEI.)
Now that your device is ready to be modified, you can now unlock the bootloader by executing this line.
Code:
fastboot flashing unlock
After executing this code, look at to your device and unlock the bootloader with its volume buttons. Remember that unlocking the bootloader voids the warranty of your device.
And then, voila! You have already unlocked the bootloader of your device! You can now reboot it to system and it will automatically perform a factory reset. Since that you have now unlocked the bootloader of your device, your device can now be modified with ease.
Now, if you got tired of customizations and you have decided you want to revert everything back to normal. You might want to relock the booloader.
HOW TO RELOCK BOOTLOADER?
Just enter the line below to relock your device's bootloader in the command prompt.
MAKE SURE THAT YOU HAVE ALREADY ATTACHED YOUR DEVICE INTO YOUR PC IN ITS ADB STATE!
Code:
fastboot flashing lock
After that, look at to your phone to make a confirmation and then, voila! You have successfully relocked the bootloader of your device.
Please note that relocking the bootloader requires an official firmware installed, and remember, YOU CANNOT LOCK THE BOOTLOADER WITH A CUSTOM ROM INSTALLED.​
First things first. In order to root your Flare S8, you must patch the stock boot image of your device. You can patch it through Magisk Manager. Download Magisk Manager, here.
Before downloading Magisk Manager, make sure that you already have a copy of the stock boot image of your device in your storage.
If you are very lazy to do that and you want someone to do it for you, congrats. You have achieved laziness . You can just download the patched boot image of Flare S8, right here.
Boot Image uploaded by Isaiah Ezra Legaspi.
After patching the boot image, you can flash it via SPFT or ADB on your PC. (You cannot root your device without a PC anymore)
SPFT is more easy than ADB but ADB is more reliable.
Please execute this line when you are flashing the patched boot image via ADB (You will need ADB drivers first + USB debugging toggled in the Developer Options of your device)
Code:
fastboot flash boot <boot-name>.img
If this isn't the answer that you wanted, don't worry, there's an alternative way to root your device. A Flare S8 user, Isaiah Ezra Legaspi, volunteered to create a video in rooting the device so that people like you will be able to root your device easily. Go watch his video, it also has TWRP flashing, so the video is not just about rooting.
Here is his video.
https://youtu.be/Lw7xzTi8PKQ
Notice: After rooting your device, you will see "unwritten tee key" and "unwritten google key." It is because you have successfully rooted your device. If you want to remove it, go to this XDA thread to uninstall any OEM Bloatwares via ADB. Well, the title of the thread clearly says that you will be removing those apps without root. But now, you have root. So, what to do? You can just use any Root File Manager app to remove bloatwares. Root Explorer will do the thing.​
In order to flash a custom recovery to your device, you will be required to use your PC again. But before flashing a custom recovery, you will be required to unlock the bootloader of your device first and unlocking it is the very important step of all.
If you are having confusions, TWRP is a kind of custom recovery.
Let's get into it.
First, visit this device thread in phhusson's GitHub Wiki. All stuffs are listed there. (Except firmware, of course )
Cherry Mobile Flare S8 Wiki
Scroll down until you find the TWRP section and download the build that is suitable for your device's Security Patch in your PC.
After downloading it, you can flash it through SPFT or ADB manually.
Or, just flash the latest source-built PBRP for Flare S8 by @loveleyz, here.
Visit the XDA thread down below.
XDA Thread - PBRP 3.0.0 for X930
These are the codes that you will be executing when you are flashing a custom recovery in ADB (Android Debug Bridge)
Code:
fastboot flash recovery <recovery-name>.img
fastboot boot <recovery-name>.img
Please note that after flashing a custom recovery, you will be required to flash this zip file to disable the dm verity of your device and to force its encryption. Flashing this zip file is a MUST.​
In order to flash treble ROMs or GSI images, please make sure that you already have a custom recovery installed in your device. You can just look for them in the internet. Since that your device is Project Treble-supported, you can install Custom ROMs much easier without any problems. To install a Custom ROM, download a GSI image, paste it into your device, then flash it on your system partition and then, voila! You have managed to install a Custom ROM to your device! Since that Custom ROMs don't come with G-Apps (or Google Apps), you have to install them manually. Download a package from http://opengapps.org and flash it to your recovery.
If you want to gain some hints about where to find the ROMs and what are the tested ROMs, you can always visit the Flare S8 Wiki page in phhusson's treble experimentations in GitHub at anytime.
Cherry Mobile Flare S8 Wiki
Also, if you don't have some 'time,' you can just scroll down and look for the ROM links that I provided. I will try to provide more as much as possible.
TESTED TREBLE IMAGES WITH LINKS
Big credits to Alfredo Cortez for testing the ROMs and for sharing them.
• AOSP 10 GSI by @phhusson - Link
• Havoc OS v6.6 GSI by @Aryan Patidar - Link
• Evolution X v3.3 GSI by @Developer Luke - Link
If any of these ROMs didn't suit your taste, you can actually just search the ROM that you want through the internet and make sure that it meets the requirements so that it will boot on your device without any problems.
More ROMs to be tested soon! I will provide links as much as possible. Keep tuned!
Please help me gather more ROM links by replying them in this thread.
That's it, folks! This is the end of the thread. If you have any questions, feel free to ask them in the comment section.​
Videos related to Cherry Mobile Flare S8
How To Flash Cherry Flare S8 firmware via Spft
Flashing GSI ROM Tutorial For Flare S8
Cherry Mobile Flare S8 for Flash TWRP recovery mode and boot.img for rooted(need Magisk app)via SPFT
Cherry Mobile Flare S8 TWRP (recovery mode) to disable force encrypt
MSM Extended V8 ARM64 AB GSI - Flare S8
Bliss 12.8 (X930 Flare S8)
Aosp Extended 7.0 Alpha Android 10 GSI Flare S8 as Test Device
Havoc OS 3.5 Official - Flare S8
AncientOS Civilization 3.7 Flare S8 MTK Treble Device
Descendant 4.0 Android 9 GSI Boot Up
Android Ice Cold Project (AICP 10) - Flare S8 ©AljunCortezYT Property
Pixel Experience Plus Android 9 Pie For Flare S8
AEX 6.6 SNEAK PEAK (FLARE S8 X930)
Don't forget to join our development groups to communicate with other Flare S8 users!.
Cherry Mobile Flare S8 X930
Cherry Mobile Flare S8 / S8 Lite PH Development
Please also join our telegram group.
Flare S8 Chat
Learn more about the treble compatibility of Flare S8
Cherry Mobile Flare S8 Wiki
Like my page for more development, stay tuned for more updates!
Androidist1204's Projects and Developments
​
@Alfredo
@LiaFourté
@Hadenix
@loveleyz
@Liam
@Isaiah Legaspi
@DC Sumcio​
PLEASE HIT THANKS IF YOU LIKE MY WORK​
XDA:DevDB Information
[GUIDE] Cherry Mobile Flare S8 Rooting, Bootloader Unlocking, ROMs, TWRP [09/30/20], Tool/Utility for all devices (see above for details)
Contributors
androidist1204, loveleyz
Version Information
Status: Stable
Created 2020-07-15
Last Updated 2020-09-30

androidist1204 said:
[GUIDE] Cherry Mobile Flare S8 Rooting, Bootloader Unlocking, ROMs, TWRP [07/15/20]
DISCLAIMER
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this Kernel
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
WHAT IS THIS?
This is a tutorial thread made for those who are having difficulties following the guides that were provided by others.
Welcome to the Tutorial thread of Cherry Mobile Flare S8. Here, you can learn more about unlocking its bootloader, rooting it, flashing a treble GSI image, and flashing a custom recovery. If you are a Flare S8 user, then this is the right thread made for you.
If you are not a Flare S8 user but you are holding a device included in the Flare S8 series, don't worry because I will be creating a guide for them, too! Stay tuned for more updates.
ADDITIONAL NOTE
Please make sure that you have already read the disclaimer above because we are not taking responsibilities of any kind when something bad happens on your device. As always, do it at your own risk and proceed with caution.
HOW TO UNLOCK BOOTLOADER?
HOW TO ROOT?
HOW TO FLASH TWRP?
HOW TO FLASH TREBLE ROMS? (KNOWN AS GSI IMAGES)
TESTED TREBLE ROMS WITH LINKS
SOME STUFFS
[/B]
CREDITS
Code:
@RIO-S5501: For being the first one who started the development community of the device! Big credits goes to him!
@androidist1204: For creating this guide thread in XDA and for supporting the community
@Hadenix: For compiling some TWRP builds and for making them available to our device. Cheers!
Special Thanks:
Alfredo Buensalida Cortez
Isaiah Ezra Legaspi
Brahm Daniel Verano
DC Sumcio
Nanik
Liam
Mar Yvan Dela Cruz
XDA:DevDB Information
Guide for Cherry Mobile Flare S8(see above for details)
Version Information
Status: Stable
Created 2020-07-16
Last Updated 2020-07-16
XDA:DevDB Information
[GUIDE] Cherry Mobile Flare S8 Rooting, Bootloader Unlocking, ROMs, TWRP [07/16/20], Tool/Utility for all devices (see above for details)
Contributors
androidist1204
Version Information
Status: Stable
Created 2020-07-15
Last Updated 2020-07-15
Click to expand...
Click to collapse
My Flare S8 updated the OS and something went wrong. the screen is now black with green vertical lines and I cannot see the cherry mobile logo on startup. (audio only)
Can anyone help me with this? appreciate if there is a step by step instruction and/or video resolving my issue.

kristray333 said:
My Flare S8 updated the OS and something went wrong. the screen is now black with green vertical lines and I cannot see the cherry mobile logo on startup. (audio only)
Can anyone help me with this? appreciate if there is a step by step instruction and/or video resolving my issue.
Click to expand...
Click to collapse
download this
drive.google.com/uc?id=11j99l7a_rQBYGigonVZVjtb9SiU2Wj_L&export=download&fbclid=IwAR28iHQ4-Kkz0IVqw2L69fkQsHU6gXKGr_2ChNfqQiddSgsNUtnNSOu_V3E
open SPFT then flash teksunhw.bin

jcmon said:
download this
drive.google.com/uc?id=11j99l7a_rQBYGigonVZVjtb9SiU2Wj_L&export=download&fbclid=IwAR28iHQ4-Kkz0IVqw2L69fkQsHU6gXKGr_2ChNfqQiddSgsNUtnNSOu_V3E
open SPFT then flash teksunhw.bin
Click to expand...
Click to collapse
Thank you.
Can you provide a screenshot from the SPFT on which one I should tick?

kristray333 said:
Thank you.
Can you provide a screenshot from the SPFT on which one I should tick?
Click to expand...
Click to collapse
Untick everything and just leave teksunhw.bin ticked, if you're still having a hard time to understand it, please join the facebook groups that we provided above

Sorry for the duplicated messages.

no one is accepting my request to join the group.
also, after flashing, i am ezperiencing boot loop.

kristray333 said:
no one is accepting my request to join the group.
also, after flashing, i am ezperiencing boot loop.
Click to expand...
Click to collapse
https://drive.google.com/file/d/1-5...kK6MT72-i8KGiSz9FSIol4BmIbPt7scbs_hqMvTWjo3uM
Try this one. It's only for those who are encountering black screen issues with their devices so unnecessary files are already removed to avoid confusion. A scatter file is also in there, so that you'll just have to use it without changing a thing.
Don't forget that you should only use the "Download Only" option in SP Flash Tool. Don't ever change it. Always use the default option in order to avoid IMEI losing, Preloader corruption, etc.
Credits again goes to Alfredo Cortez for uploading it in his Flare S8 Dev.
Please give me a thanks if I helped you. Thank you.

hello, i am experiencing a black screen during calls. help please? thanks in advance.
Sent from my Flare S8 using Tapatalk

blissakiara said:
hello, i am experiencing a black screen during calls. help please? thanks in advance.
Sent from my Flare S8 using Tapatalk
Click to expand...
Click to collapse
Hello, blissakiara. I'm thinking that the issue is about the proximity sensor of your device. If you have a tempered glass installed, please make sure that you have installed it correctly and don't let it take over the proximity sensor.
If I'm mistaken, you might want to join the official Facebook group of Cherry Mobile users, there you can get a lot of support from its Tech Support, its staff, etc.
I cannot put a link to it right now but I assume that its name was "Cherry Mobile PH Official."

androidist1204 said:
If you have a tempered glass installed, please make sure that you have installed it correctly and don't let it take over the proximity sensor.
Click to expand...
Click to collapse
Um, can you tell me where the proximity sensor is?[emoji28] Thanks in advance.
Sent from my Flare S8 using Tapatalk

blissakiara said:
Um, can you tell me where the proximity sensor is?[emoji28] Thanks in advance.
Sent from my Flare S8 using Tapatalk
Click to expand...
Click to collapse
Near the teardrop notch.

Happy 800+ viewers! Cannot wait to make it to thousand.

Happy 1,003 views! Thread will be updated some time now. Keep tuned.

Please help. Nag trinatry kong mag unlock ng bootloader, first nadedetect siya ng pc ko, pero once i typed the adb reboot bootloader sa powershell, pupunta siyang fastboot and after non wala na di na siya ma detect. stucked ako sa process nato

jordy24 said:
Please help. Nag trinatry kong mag unlock ng bootloader, first nadedetect siya ng pc ko, pero once i typed the adb reboot bootloader sa powershell, pupunta siyang fastboot and after non wala na di na siya ma detect. stucked ako sa process nato
Click to expand...
Click to collapse
check if the driver for adb and fastboot is properly installed

LiaFourté said:
...
Try this one. It's only for those who are encountering black screen issues with their devices so unnecessary files are already removed to avoid confusion. A scatter file is also in there, so that you'll just have to use it without changing a thing.
Don't forget that you should only use the "Download Only" option in SP Flash Tool. Don't ever change it. Always use the default option in order to avoid IMEI losing, Preloader corruption, etc.
Credits again goes to Alfredo Cortez for uploading it in his Flare S8 Dev.
Please give me a thanks if I helped you. Thank you.
Click to expand...
Click to collapse
thanks a lot! this worked and fixed my daughter's phone (blackscreen after flashing).

pabile said:
thanks a lot! this worked and fixed my daughter's phone (blackscreen after flashing).
Click to expand...
Click to collapse
You're welcome thank you for trusting my guide, please give my thread a "thanks"

Can you give the link again?
Google drive says it doesnt exist anymore.

RusticDeveloper said:
Google drive says it doesnt exist anymore.
Click to expand...
Click to collapse
It's to protect the file from being sold. If you need an immediate response coming from the admins, please join this group.

Question Can the P11 Plus be rooted?

Hi all. I'm new to the Lenovo space, so please bear with me. After some searching, I can't quite seem to figure out what the model number of the P11 Plus is? Can anyone enlighten me?
Tab P11 Plus | 11" Family Tablet
Meet the Lenovo Tab P11 Plus, an Android tablet featuring an 11" 2K display and quad speakers for immersive multimedia, plus Google Kids Space and Entertainment Space for family fun and education.
www.lenovo.com
Knowing that, can this particular model's bootloader be unlocked and the OS rooted? Cheers.

Found the model number: TB-J616F or TB-J616X
Android Upgrade Matrix - Lenovo Support US
support.lenovo.com

molohov said:
Found the model number: TB-J616F or TB-J616X
Android Upgrade Matrix - Lenovo Support US
support.lenovo.com
Click to expand...
Click to collapse
Have you found the answer whether the Lenovo P11 Plus (TB-J616F) model can be rooted?

I am thinking of buying this tab. Is it stock unlocked or is it not?

kanines said:
Have you found the answer whether the Lenovo P11 Plus (TB-J616F) model can be rooted?
Click to expand...
Click to collapse
The answer is yes.
First, using Rescue and Smart Assist, DL the latest rom for this model this model. I used TB_J616F_S000046_220311_ROW.
Next go to C:\ProgramData\RSA\Download\RomFiles\TB_J616F_S000046_220311_ROW and you will find the boot.img files. Copy it to a folder on the tablet. Remember where.... duh.
Install Magisk 25.2 which is the version that I used. Follow Magisk instructions to "patch" the copied boot.img file. When complete, copy the patch boot image file back to your Adb/Fastboot folder, normally X:\platform-tools.
Put your tablet in fastboot mode and run: fastboot flash boot <name of patched boot.img file>.
So, there's no need to ask questions as there are a least a bizzion guides on the internet on how to do a "Magisk boot.img patch and flash".

I am stuck on unlocking the bootloader as, when I use adb reboot bootloader. I am greeted with => FASTBOOT mode..., and when i go to fastbootd using recovery mode. I am stuck with Download is not allowed on locked devices, and when trying to unlock. Stuck with Command is not supported in default implentation.

levrx said:
I am stuck on unlocking the bootloader as, when I use adb reboot bootloader. I am greeted with => FASTBOOT mode..., and when i go to fastbootd using recovery mode. I am stuck with Download is not allowed on locked devices, and when trying to unlock. Stuck with Command is not supported in default implentation.
Click to expand...
Click to collapse
every android ive unlocked bootloader, you click on the build number in settings 7 times, after aprox 3 it shows a count down until its unlocked, then it depends on the device im pretty sure, it was diff between my phone n table so it depends on ur device here is some resources
Locking/Unlocking the Bootloader | Android Open Source Project
source.android.com
How To: Unlock Bootloader
How To Unlock Bootloader Galaxy A12. *** Disclaimer I am not responsible for any damage you made to your device You have been warned - Go to Settings -> About phone and find your build number. - Tap on your build number 6 times until you see...
forum.xda-developers.com
Unlocking the bootloader and rooting
DISCLAIMER: I WAS NEVER, HAVE NEVER BEEN, AND WILL NEVER BE RESPONSIBLE OF ANY DAMAGES AGAINST YOUR DEVICES BY YOUR OWN MIS-OPERATIONS # knox_bit_warranty:0x1 # # Your warranty is now void # # You have been warned. # # I will laught at you if you...
forum.xda-developers.com
there is a diff between download mode and fastboot, just so u know, you need adb and fastboot from Androids SDK tools, you can find online, depending on ur computers OS. Also, ADB commands work with ur device on n plugged into the computer fastboot is for commands when ur in fastboot mode

levrx said:
I am stuck on unlocking the bootloader as, when I use adb reboot bootloader. I am greeted with => FASTBOOT mode..., and when i go to fastbootd using recovery mode. I am stuck with Download is not allowed on locked devices, and when trying to unlock. Stuck with Command is not supported in default implentation.
Click to expand...
Click to collapse
I have the same issue!!! It seems a problem with the Fastboot mode.

19blacktiger77 said:
I have the same issue!!! It seems a problem with the Fastboot mode.
Click to expand...
Click to collapse
I solved!!!
I just had to download the latest version of ABD and Fastboot!

Hi. i rooted with this video.. it is in portuguese, but the codes are in english, 15 minutes and it´s done..

I also want to root this device but I am waiting for their Android 12 update. Is anyone running Android 12 ?

I've successfully rooted my Lenovo P11 Plus (J616F) tablet via the latest stock rom + Magisk 25.2, and it was much more painless than I'd thought it'd be. But I can't figure out how to get TWRP or any other custom recovery, and I'd be happy to hear if anyone has had any success with it...
HackVasant said:
I also want to root this device but I am waiting for their Android 12 update. Is anyone running Android 12 ?
Click to expand...
Click to collapse
Yes...
1.) Install USB drivers (I used this to detect fastboot mode: https://motorola-global-en-uk.custhelp.com/app/usb-drivers/)
>> NOTE: With your tablet in fastboot mode, you might have to go into device manager and manually update the drivers for your "unknown android device", pointing it to the usb drivers from the previous step)
2.) Install the lastest ADB and Fastboot software
3.) Unlock your bootloader!
3a.) Enable developer options -> Enable OEM unlocking
3b.) Enter fastboot mode (turn tablet off then hold power + volume up until just after it vibrates)
3c.) With your device connected to your PC, type fastboot flashing unlock in command prompt
4.) Look for the current latest stock rom TB-J616F_S240138_221026_ROW_SVC.ZIP
5.) Extract it somewhere on your PC, and copy boot.img to somewhere on your device
6.) Install Magisk v25.2 on your device
7.) Follow the rest of the installation instructions here: https://topjohnwu.github.io/Magisk/install.html
If all went well, after rebooting you might get a warning about your device being in "Orange State" and therefore cannot be trusted because the bootloader was unlocked... This is normal, and your instinct might be to run the command fastboot flashing lock to get rid of it, but THS IS A BAD IDEA because it could place your device into a "Red State" requiring you to unlock it again, effectively wiping your device

Can it play Redbox (free video app) OK after rooted?
If it's OK, I think Netflix and Amazon Prime will be OK as well

mingkee said:
Can it play Redbox (free video app) OK after rooted?
If it's OK, I think Netflix and Amazon Prime will be OK as well
Click to expand...
Click to collapse
Yes, but you will need to do the following...
1.) In Magisk, make sure you have Zygisk enabled in the settings
2.) Install this Magisk module, then reboot your device:
Releases · kdrag0n/safetynet-fix
Google SafetyNet attestation workarounds for Magisk - kdrag0n/safetynet-fix
github.com
3.) Use YASNAC (from the app store) to verify that you pass the safetynet check (it passes for me)
4.) Uninstall Netflix, then manually download and install the latest Netflix APK from your favorite APK site
I didn't test Redbox or Amazon Prime, but I would imagine it'd just be repeating step 4 for each additional app you wish to install
You can also read this for more detailed information about Magisk & SafetyNet:
SafetyNet:Magisk and MagiskHide Installation and Troubleshooting guide
www.didgeridoohan.com

SpectreCular said:
Yes, but you will need to do the following...
1.) In Magisk, make sure you have Zygisk enabled in the settings
2.) Install this Magisk module, then reboot your device:
Releases · kdrag0n/safetynet-fix
Google SafetyNet attestation workarounds for Magisk - kdrag0n/safetynet-fix
github.com
3.) Use YASNAC (from the app store) to verify that you pass the safetynet check (it passes for me)
4.) Uninstall Netflix, then manually download and install the latest Netflix APK from your favorite APK site
I didn't test Redbox or Amazon Prime, but I would imagine it'd just be repeating step 4 for each additional app you wish to install
You can also read this for more detailed information about Magisk & SafetyNet:
SafetyNet:Magisk and MagiskHide Installation and Troubleshooting guide
www.didgeridoohan.com
Click to expand...
Click to collapse
The reason why I asked because A12 can make those video apps don't work even after passed safetynet and play integrity (2/3) and apps installed
However, those apps work on OnePlus N200 and 8T but NOT on Moto Edge 2021

mingkee said:
The reason why I asked because A12 can make those video apps don't work even after passed safetynet and play integrity (2/3) and apps installed
However, those apps work on OnePlus N200 and 8T but NOT on Moto Edge 2021
Click to expand...
Click to collapse
Alright well I decided to take the time to check Redbox, and it works (or at least the Watch Free feature does)... And I don't have a prime account, but the prime video app makes it to the sign in screen, if that helps

SpectreCular said:
Alright well I decided to take the time to check Redbox, and it works (or at least the Watch Free feature does)... And I don't have a prime account, but the prime video app makes it to the sign in screen, if that helps
Click to expand...
Click to collapse
Good!
I will make a backup on mine (I have Yoga 11 and practically they're the same) and unlock the bootloader and root it.
The reason why I root it so I can do adb on other device without laptop.
Actually, I have a lot of experience to root variety of machines, but what happened on Edge 2021 A12 puts me on hold on other Moto/Lenovo
I have Netflix and cable apps (Sling and Philo) and Discovery+.

Well just so we're on the same page, the steps I've posted were specifically for J616F, so your mileage may vary if you're using a different device. Also, I would maybe use a more specific stock ROM, since the one I posted is also specifically for J616F

SpectreCular said:
Well just so we're on the same page, the steps I've posted were specifically for J616F, so your mileage may vary if you're using a different device. Also, I would maybe use a more specific stock ROM, since the one I posted is also specifically for J616F
Click to expand...
Click to collapse
I have to make it clear. I have both P11 plus and Yoga 11

I have the P11 Plus J616F model and cannot get the device to unlock after many attempts with wiping device reinstalling firmware reinstalling device drivers. Does failed (unknown status code) after (bootloader) sysytem-fingerprint:Lenovo/TB-J616F/TB-J616F:12/SP1A.210812.0 mean anything to anyone. I can adb reboot recovery, from recovery I can use the keys to choose fastboot and tab goes into fastbootd and fastboot devices returns my device fashboot flashing unlock starts but ends with the failed message above. fastboot getvar all returns a bunch of information about the device but also stops with same failed message. If I choose reboot bootloader using the keys on my tab while in fastbootd tab reboots to FASTBOOT... shows up in device manager as you would expect but typing fastboot flashing unlock returns waiting for device. Any thoughts or ideas would be greatly appreciated.

How to really downgrade Galaxy S6 SM-G920F firmware from 7.0 to 5.0.2/5.1.1/6.0.1?

Hello
I've been reading forums and downloading files for days. Many of the links in the posts no longer work. Posts are 5 years and older. There are no new ones. At least not one that actually works. Downgrade I mean. That's why I wrote this question and I'm asking for help - how to really downgrade my Galaxy S6 G920F.
Thanks for the help.

PSA: Downgrading WILL void your warranty!
What have you already done (what method, software) have you already tried?
The 100% surefire way to downgrade your phone (or any android phone really), is to:
1. Backup your phone data.
2. Switch the phone into download mode, connect to PC, boot into TWRP recovery through fastboot
3. Wipe your 7.0 firmware and all data
4. Flash android 5.02 ROM
For a samsung phones ODIN + Freya is also an option. Odin is a samsung's firmware flashing tool, Freya is a 3rd party program that can download the stock firmware android for you. All of these tools are available online, and you can ask on a samsung subsection of XDA about how to use them - people can give you up to date links.

I'm laughing because you write quite a lot in three days. Of course, this method does not work.
Is there anyone willing to help?

Totesnochill said:
PSA: Downgrading WILL void your warranty!
What have you already done (what method, software) have you already tried?
The 100% surefire way to downgrade your phone (or any android phone really), is to:
1. Backup your phone data.
2. Switch the phone into download mode, connect to PC, boot into TWRP recovery through fastboot
3. Wipe your 7.0 firmware and all data
4. Flash android 5.02 ROM
For a samsung phones ODIN + Freya is also an option. Odin is a samsung's firmware flashing tool, Freya is a 3rd party program that can download the stock firmware android for you. All of these tools are available online, and you can ask on a samsung subsection of XDA about how to use them - people can give you up to date links.
Click to expand...
Click to collapse
That is assuming they have TWRP.
Also, the part you mention about "boot into download mode, connect to PC then boot to TWRP via fastboot" is not correct because Samsung is not compatible with fastboot, adb works but fastboot does not. Some Samsung devices technically have a "fastboot mode" but it isn't functional, it doesn't respond to fastboot commands, it's basically useless.
Also, you can't flash a firmware that has a lower binary than the currently installed firmware so if the binary of the downgraded firmware is lower than the binary of the currently installed firmware, the downgraded firmware can't be flashed.
Samsung is making it harder and harder to downgrade their devices.

OK. I'm afraid I'm missing the point of what's being said.
I know it is possible and there are also posts about it, but they are old, the links in them do not work. I'm asking for an expert who knows how to do this, philosophizing about what it would be like if it somehow doesn't really help me and I'm not interested either
I'm only interested in a positive thought, help and not brainstorming, if you understand me?
No offense