Database Users

No sim card detected on custom roms

I have a XT1572 (Indian variant dual sim) . The sim card works good on both 6.0 & 7.0 (official roms) however remains undetected on any custom rom . Any guidance would be of great help .

Using magisk? It will cause that. Flash magisk uninstaller and reboot system once before flashing a new rom.

Tried but no success
jason2678 said:
Using magisk? It will cause that. Flash magisk uninstaller and reboot system once before flashing a new rom.
Click to expand...
Click to collapse
So I was on stock mm , had magisk -uninstalled and rebooted afterwards . Installed RRemix(RR-N-v5.8.5-20171230-clark-Final) . Again no sim . Attaching two screen shots for your reference .
One thing to note I have a dual sim variant and under all custom roms imei of only one is being displayed .
This whole thing is very strange since I could run Lineage very easily on the same phone sometime back , roughly around Oct'17 . Used the phone on stock nougat afterwards .

Anyone ?
Sir2taj said:
So I was on stock mm , had magisk -uninstalled and rebooted afterwards . Installed RRemix(RR-N-v5.8.5-20171230-clark-Final) . Again no sim . Attaching two screen shots for your reference .
One thing to note I have a dual sim variant and under all custom roms imei of only one is being displayed .
This whole thing is very strange since I could run Lineage very easily on the same phone sometime back , roughly around Oct'17 . Used the phone on stock nougat afterwards .
Click to expand...
Click to collapse
@antariksh
I am very well aware of the fact that lineage would not run on nougat modem. Have tried aicp rremix unofficial lineage etc . The issue remains the same no sim detected .
What I have done for installation -
fastboot install marshmallow/nougat build (depending upon the custom rom)
flash latest twrp
in twrp factory reset (don't mount/unmount anything, all default)
rom boots but doesnt detect any sim .
details of only one imei of the two is displayed under about phone .

Sir2taj said:
@antariksh
I am very well aware of the fact that lineage would not run on nougat modem. Have tried aicp rremix unofficial lineage etc . The issue remains the same no sim detected .
What I have done for installation -
fastboot install marshmallow/nougat build (depending upon the custom rom)
flash latest twrp
in twrp factory reset (don't mount/unmount anything, all default)
rom boots but doesnt detect any sim .
details of only one imei of the two is displayed under about phone .
Click to expand...
Click to collapse
Have you tried this version with this guide?
P.S: Nougat has 9 system.img_sparsechunk's. So flash accordingly and then try any other custom ROMs.
P.P.S: Flash Modem twice if you get any 'prevalidation failed error'

antariksh said:
Have you tried this version with this guide?
P.S: Nougat has 9 system.img_sparsechunk's. So flash accordingly and then try any other custom ROMs.
P.P.S: Flash Modem twice if you get any 'prevalidation failed error'
Click to expand...
Click to collapse
Will try the guide and get back to you
Update
Tried each and every step as per your suggestions . No change .
The phone is failing to recognize sims on all custom roms .

Sir2taj said:
Will try the guide and get back to you
Update
Tried each and every step as per your suggestions . No change .
The phone is failing to recognize sims on all custom roms .
Click to expand...
Click to collapse
@antariksh pls help

Sir2taj said:
@antariksh pls help
Click to expand...
Click to collapse
I'm afraid it must be your device issue.
Cause last week I followed the same steps to Flash Stock Nougat and went back to NucleaROM.
You sure you are using Nougat Modem based Custom ROMs?

antariksh said:
I'm afraid it must be your device issue.
Cause last week I followed the same steps to Flash Stock Nougat and went back to NucleaROM.
You sure you are using Nougat Modem based Custom ROMs?
Click to expand...
Click to collapse
Very very strange because I do recall that all these custom ROMs used to run fine without any such stupid issues back in October last year . its really disheartening. Yes I am using nougat firmwares for nougat modem compatible ROMs and mm firmware for rhe mm compatible one's . Its just that be it any custom ROM this thing won't work at all ! Is it anyhow related to recovering phone from brick state because I do remember that I had to flash the bootloader on a memory card in order to get the device up ?
Appreciate your efforts brother.

i have similar problem

antariksh said:
Have you tried this version with this guide?
P.S: Nougat has 9 system.img_sparsechunk's. So flash accordingly and then try any other custom ROMs.
P.P.S: Flash Modem twice if you get any 'prevalidation failed error'
Click to expand...
Click to collapse
HI there , I hope my constant requests aren't bothering . If they are kindly let me know & I shall refrain in future .
I just realised one thing . On installing nougat fastboot file from " https://forum.xda-developers.com/moto-x-style/general/xt1572firmwareclarkretasiaindiads7-t3735257" as per suggestions I get model as XT 1572 on connection to PC . Although in recovery mode when connected (twrp) the same pc recognizes the phone as XT1575 . Is it normal ?

Sir2taj said:
HI there , I hope my constant requests aren't bothering . If they are kindly let me know & I shall refrain in future .
I just realised one thing . On installing nougat fastboot file from " https://forum.xda-developers.com/moto-x-style/general/xt1572firmwareclarkretasiaindiads7-t3735257" as per suggestions I get model as XT 1572 on connection to PC . Although in recovery mode when connected (twrp) the same pc recognizes the phone as XT1575 . Is it normal ?
Click to expand...
Click to collapse
Yep. It is normal. TWRP was probably based out on XT1575. But it doesn't matter.
Only modems differ between XT1575 and XT1572.

Flash the MM firmware, make sure the modem has no validation issues, then flash the custom ROM you want. Flashing with Nougat firmware won't allow boots. Also, sometimes the MM firmware just doesn't work, and flashing stock firmware will "rejuvenate" it.

parker.stephens said:
Flash the MM firmware, make sure the modem has no validation issues, then flash the custom ROM you want. Flashing with Nougat firmware won't allow boots. Also, sometimes the MM firmware just doesn't work, and flashing stock firmware will "rejuvenate" it.
Click to expand...
Click to collapse
I wanted to try installing it on 6.0 . The install process didn't initiate saying that the bootloader (A**52) isnt compatible.
Plus I noted that on downgrading to 6.0 from 7.0 the loader and gpt bin gave failure errors in fastboot.

Sir2taj said:
I wanted to try installing it on 6.0 . The install process didn't initiate saying that the bootloader (A**52) isnt compatible.
Plus I noted that on downgrading to 6.0 from 7.0 the loader and gpt bin gave failure errors in fastboot.
Click to expand...
Click to collapse
GPT is not downgradeable and it doesn't need to flash successfully. Also, one you are on 0xA052 firmware, you can't go back, but you can edit the rom's files and make it skip the bootloader check. This is a quote of myself on how to do that from the LOS thread,
"Extract the ROM zip into it's own subdirectory. Then go into the folder META-INF, then com, then google, android, then open updater-script in a text editing program. I prefer Notepad++. Locate the line that says assert getprop ro.bootloader. Should be line 2. You can either add your bootloader by copying another item, or this is easier, edit a line already there, such as "|| getprop("ro.bootloader") == "0xA048" ||" and replace 0xA048 with 0xA052 or the bootloader your device has. Then save it by going to the root folder, not the folder labeled "lineage-14.1-xxxxxxxx-nightly-clark-signed", but the folder with the folders install, META-INF, system, and etc. Select everything by dragging your cursor over all the files, then right-click, send-to, compressed zip. Name it anything, then copy it to your device however you prefer, I just sideloaded it in TWRP. If you get an error talking about a digest file, you might have accidentally deleted something you shouldn't have."

parker.stephens said:
GPT is not downgradeable and it doesn't need to flash successfully. Also, one you are on 0xA052 firmware, you can't go back, but you can edit the rom's files and make it skip the bootloader check. This is a quote of myself on how to do that from the LOS thread,
"Extract the ROM zip into it's own subdirectory. Then go into the folder META-INF, then com, then google, android, then open updater-script in a text editing program. I prefer Notepad++. Locate the line that says assert getprop ro.bootloader. Should be line 2. You can either add your bootloader by copying another item, or this is easier, edit a line already there, such as "|| getprop("ro.bootloader") == "0xA048" ||" and replace 0xA048 with 0xA052 or the bootloader your device has. Then save it by going to the root folder, not the folder labeled "lineage-14.1-xxxxxxxx-nightly-clark-signed", but the folder with the folders install, META-INF, system, and etc. Select everything by dragging your cursor over all the files, then right-click, send-to, compressed zip. Name it anything, then copy it to your device however you prefer, I just sideloaded it in TWRP. If you get an error talking about a digest file, you might have accidentally deleted something you shouldn't have."
Click to expand...
Click to collapse
Will give it a try

parker.stephens said:
GPT is not downgradeable and it doesn't need to flash successfully. Also, one you are on 0xA052 firmware, you can't go back, but you can edit the rom's files and make it skip the bootloader check. This is a quote of myself on how to do that from the LOS thread,
"Extract the ROM zip into it's own subdirectory. Then go into the folder META-INF, then com, then google, android, then open updater-script in a text editing program. I prefer Notepad++. Locate the line that says assert getprop ro.bootloader. Should be line 2. You can either add your bootloader by copying another item, or this is easier, edit a line already there, such as "|| getprop("ro.bootloader") == "0xA048" ||" and replace 0xA048 with 0xA052 or the bootloader your device has. Then save it by going to the root folder, not the folder labeled "lineage-14.1-xxxxxxxx-nightly-clark-signed", but the folder with the folders install, META-INF, system, and etc. Select everything by dragging your cursor over all the files, then right-click, send-to, compressed zip. Name it anything, then copy it to your device however you prefer, I just sideloaded it in TWRP. If you get an error talking about a digest file, you might have accidentally deleted something you shouldn't have."
Click to expand...
Click to collapse
Iam gettign error 6 . Pls share the edited updater script for bootloader - A0.52

I've got exactly the same issue.... Sim not detected on Nougat, can't boot Marshmallow roms.
Someone found a fix to this?

Perhaps I'm not the only one having the issue of no sim

Sir2taj said:
Perhaps I'm not the only one having the issue of no sim
Click to expand...
Click to collapse
i have the same issue my friend and i dont know what to do.

TWRP for P580 running Oreo?

Is anyone able to run TWRP on P580 running Oreo?
Im having problems with my Tab stuck on a black screen instead of recovery mode.
Please help.
Thanks!!

I found a solution if you don't need TWRP, only Magisk or Root. (Using sm-p580 german version P580KXU1CRJ7)
Short Version:
Install Magisk without TWRP with odin in AP section(google it)
Problem is: Once booted up it will tell you that you have to reset your device because the system recognizes that you modified something.
Solution: Just click on the reset button( Magisk will still be there afterwards).
Long Version
Flash the Oreo firmware onto your device.
Set it up (turn on USB debugging) (or dont, I believe you dont need it for download mode ?)
Unzip the AP part of the firmware you have flashed. You may need a modified version of 7-zip, I needed it, because it couldn't unzip lz4.
Google mcmilk 7 zip and download the github release (I hope I'm allowed to reference it, CREDIT goes to MILKY)
You need the boot.img.
Now install Magisk Manager apk.
Under its settings check " .img.tar" under "return of patched boot-images" (Something like that, mine is german)
Click on install in Magisk Manager apk.
Select make thing with boot img, use the boot.img you have extracted and copied onto your phone.
Magisk will create new patched boot img automatically, copy the finished one u find under your main storage in downloads to your pc.
Go into download mode and flash new boot.img with odin using the AP tab.
Now do the things I described in the Short Version
Afterwards install Magisk Manager Apk.
You need internet connection, because it will prompt you to allow installing additional stuff.
A message from some Security App will appear, that something is wrong.
And your device will get laggy and restart.
After that the lag will disapear
I like to use Bk disabler to remove bloatware/ other stuff to flash or back up your device
(Please dont remove any of the 3 phone apks, on Nougat it worked to remove two of them, but oreo will continuously give an error message <- I found out that you can uninstall two of them, but dont uninstall the storagedial-programm thats what gives the errormessage.)
Hope it will help you!

Worked !!!
Thank you dear. Its worked for mine in p585 oreo android....
Anyone can search mcmilk 7zip in google and download program to extract boot.img.lz4 and get boot.img :good:

use the last TWRP for Oreo.
old version makes black screen or red stripes.
go in download-mode (power+home+vol-) and install the last TWRP over with Odin.
for Oreo use the last Odin 3.13
it tested, i had the same problem :fingers-crossed:

Latest twrp dose not worked on my device but this solution work fine

I can confirm that this method does work. I used it on my SM-P580 yesterday. I would suggest that you first backup your all of your apps, contacts, photos, etc using SmartSwitch. You will need to restore everything after the tablet tells you that it needs to be reset because it wipes everything. After the restore, you will need to enter all of your accounts and passwords again but at least all of the data will be back.
amosdinh said:
I found a solution if you don't need TWRP, only Magisk or Root. (Using sm-p580 german version P580KXU1CRJ7)
Short Version:
Install Magisk without TWRP with odin in AP section(google it)
Problem is: Once booted up it will tell you that you have to reset your device because the system recognizes that you modified something.
Solution: Just click on the reset button( Magisk will still be there afterwards).
Long Version
Flash the Oreo firmware onto your device.
Set it up (turn on USB debugging) (or dont, I believe you dont need it for download mode ?)
Unzip the AP part of the firmware you have flashed. You may need a modified version of 7-zip, I needed it, because it couldn't unzip lz4.
Google mcmilk 7 zip and download the github release (I hope I'm allowed to reference it, CREDIT goes to MILKY)
You need the boot.img.
Now install Magisk Manager apk.
Under its settings check " .img.tar" under "return of patched boot-images" (Something like that, mine is german)
Click on install in Magisk Manager apk.
Select make thing with boot img, use the boot.img you have extracted and copied onto your phone.
Magisk will create new patched boot img automatically, copy the finished one u find under your main storage in downloads to your pc.
Go into download mode and flash new boot.img with odin using the AP tab.
Now do the things I described in the Short Version
Afterwards install Magisk Manager Apk.
You need internet connection, because it will prompt you to allow installing additional stuff.
A message from some Security App will appear, that something is wrong.
And your device will get laggy and restart.
After that the lag will disapear
I like to use Bk disabler to remove bloatware/ other stuff to flash or back up your device
(Please dont remove any of the 3 phone apks, on Nougat it worked to remove two of them, but oreo will continuously give an error message <- I found out that you can uninstall two of them, but dont uninstall the storagedial-programm thats what gives the errormessage.)
Hope it will help you!
Click to expand...
Click to collapse

Im not sure if this post belongs here, you link to the T580 TWRP, not the P580.
Is that one compatible with P580?
nill3bor said:
use the last TWRP for Oreo.
old version makes black screen or red stripes.
go in download-mode (power+home+vol-) and install the last TWRP over with Odin.
for Oreo use the last Odin 3.13
it tested, i had the same problem :fingers-crossed:
Click to expand...
Click to collapse

If I do this, will I be able to mount my SD Card as internal storage? 16gb just isnt enough on this tablet.

Do you have to be on oreo already for this to work I'm still on 7.0 and with my system modified I can't upgrade normally

This method root my P585 device but the sim card not working anymore until I odin official rom
also twrp-3.2.3-4-gtaxllte-OMNI6 not work and freeze on Samsung logo
there is no method to root android Oreo P585 Realllllly????

khatkhatik said:
This method root my P585 device but the sim card not working anymore until I odin official rom
also twrp-3.2.3-4-gtaxllte-OMNI6 not work and freeze on Samsung logo
there is no method to root android Oreo P585 Realllllly????
Click to expand...
Click to collapse
This one worked for me on a P585Y. You just have to skip the steps below.
A message from some Security App will appear, that something is wrong.
And your device will get laggy and restart.
After that the lag will disapear
Click to expand...
Click to collapse
It will also show on the Device Maintenance, just ignore the warning.
You can freeze some of the system apps to prevent it from showing on the notification again.

amosdinh said:
I found a solution if you don't need TWRP, only Magisk or Root. (Using sm-p580 german version P580KXU1CRJ7)
Short Version:
Install Magisk without TWRP with odin in AP section(google it)
Problem is: Once booted up it will tell you that you have to reset your device because the system recognizes that you modified something.
Solution: Just click on the reset button( Magisk will still be there afterwards).
Long Version
Flash the Oreo firmware onto your device.
Set it up (turn on USB debugging) (or dont, I believe you dont need it for download mode ?)
Unzip the AP part of the firmware you have flashed. You may need a modified version of 7-zip, I needed it, because it couldn't unzip lz4.
Google mcmilk 7 zip and download the github release (I hope I'm allowed to reference it, CREDIT goes to MILKY)
You need the boot.img.
Now install Magisk Manager apk.
Under its settings check " .img.tar" under "return of patched boot-images" (Something like that, mine is german)
Click on install in Magisk Manager apk.
Select make thing with boot img, use the boot.img you have extracted and copied onto your phone.
Magisk will create new patched boot img automatically, copy the finished one u find under your main storage in downloads to your pc.
Go into download mode and flash new boot.img with odin using the AP tab.
Now do the things I described in the Short Version
Afterwards install Magisk Manager Apk.
You need internet connection, because it will prompt you to allow installing additional stuff.
A message from some Security App will appear, that something is wrong.
And your device will get laggy and restart.
After that the lag will disapear
I like to use Bk disabler to remove bloatware/ other stuff to flash or back up your device
(Please dont remove any of the 3 phone apks, on Nougat it worked to remove two of them, but oreo will continuously give an error message <- I found out that you can uninstall two of them, but dont uninstall the storagedial-programm thats what gives the errormessage.)
Hope it will help you!
Click to expand...
Click to collapse
this works great! thanks!
2 side notes on the process:
1. Magisk no longer provides " .img.tar" patched files, so a tool like "Tar-tool" is required to convert the file from the ".img" type. The patched file should be renamed "boot.img" before conversion in order to be succesfully flashed by Odin.
2. like f4vr said, freeze the apps that give the error notification or just disable the specific notification. Hiding them in Magisk Hider does not seem to work
Cheers, and thanks again for the guide!

Hello Gyus,
I managed to root the device with the method posted by @amosdinh (Thank you so much). Now I'm trying to configure adoptable storage. So far I didn't achieve this goal. ADB commands doesn't work and I can't install the ASPlugin.zip needed by Root Essentials to set adoptable storage by the app.
TWRP for P585 is corrupted, gives blue/red lines screen. The dev that maintains the code is absent since march. I'm out of luck on this. If anyone have a idea to get adoptable storage on this device while using Oreo, please comment.
Thanks!
---------- Post added at 11:17 AM ---------- Previous post was at 11:11 AM ----------
artaeun said:
this works great! thanks!
2 side notes on the process:
1. Magisk no longer provides " .img.tar" patched files, so a tool like "Tar-tool" is required to convert the file from the ".img" type. The patched file should be renamed "boot.img" before conversion in order to be succesfully flashed by Odin.
2. like f4vr said, freeze the apps that give the error notification or just disable the specific notification. Hiding them in Magisk Hider does not seem to work
Cheers, and thanks again for the guide!
Click to expand...
Click to collapse
Just renaming magisk_patched.img to boot.img and adding to .tar file by 7zip worked for me.

We should ask a dev to update twrp for android 8.1

khatkhatik said:
This method root my P585 device but the sim card not working anymore until I odin official rom
also twrp-3.2.3-4-gtaxllte-OMNI6 not work and freeze on Samsung logo
there is no method to root android Oreo P585 Realllllly????
Click to expand...
Click to collapse
Same freeze for me with the Omni - can't do anything outside of access download mode

Same Problem
cmzizi said:
Is anyone able to run TWRP on P580 running Oreo?
Im having problems with my Tab stuck on a black screen instead of recovery mode.
Please help.
Thanks!!
Click to expand...
Click to collapse
I have the same problem. It just keep getting to the bad TWRP, it seems that it does not work with the SM-P580. I had to flash stock firmware to get it back to work.

luinkazofeifa said:
I have the same problem. It just keep getting to the bad TWRP, it seems that it does not work with the SM-P580. I had to flash stock firmware to get it back to work.
Click to expand...
Click to collapse
Really wish this wasn't the case. I'd actually keep this thing if it had a working TWRP.

On my SM-P580 I used Odin and TWRP I don't get the black screen but when I reboot to get into TWRP recovery mode it shows the padlock and says swipe to unlock. Tried many times bit cannot swipe and cannot get past this. All I want is to be able to use the SD card as internal storage. HELP???? Thanks!!

luinkazofeifa said:
I have the same problem. It just keep getting to the bad TWRP, it seems that it does not work with the SM-P580. I had to flash stock firmware to get it back to work.
Click to expand...
Click to collapse
thanks in advanced
where can i find stock firmware?

I've just installed magisk using TWRP via command line. P580
I've just installed magisk using TWRP via command line.
Read the entire post before trying this yourself.
I installed the latest TWRP, the one that bugs and doesn't display anything, this allows to root without wiping data. I'm running the latest korean firmware for P580.
Just do this:
1. Launch TWRP and INMEDIATELY LOCK YOUR SCREEN. (I got ghost stripes that disappeared after 2 days when testing this, work with low light so you can notice your screen whenever it tuens on) Please don't forget this point, don't [temporarily] damage your screen as I did.
2. adb push Magisk-v[Current version].zip external_sd
3. adb shell
4. twrp install external_sd/Magisk-v[Current version].zip
After this you just need to install MagiskManager-v[Current version].apk and you will be all done.
But there is one thing...
If you ever get into recovery mode, there is no way out without using adb as far as I know. You can launch download mode and cancel it but you'll boot back to TWRP.
When in twrp touching your screen or any button will wake the device up and will start burning the ghost image to your screen.
So if you know of a method for rebooting to system without using adb, please let me know.
Also a solution for this would be to flash back the stock recovery, wich may or may not force to wipe system, that something that needs to be tested tho.
Update: Ok so, you can use a handy tool called MTKroot on recovery.img.lz4 to get recovery.img, then use 7z to pack it into a tar file and flash that tar file with odin (AP, same as TWRP)
This way you will not have a 0.001% chance of random boot into recovery mode and damage your screen

(Method) For everyone who wants to Downgrade Galaxy S8 to Oreo/Nougat

Hey guys!
I recently read many Questions About downgrading the Galaxy S8 to 7.0/8.0 after we got the 5x Bootloader.
Well many of you say NO but What many of you forgot is that there is a way to Downgrade your phone.
I already had that Problem with my S6 back in 2016, where I wanted to Downgrade it to 5.1. All you Need for a Downgrade is a Combination File.
Combination files are basically used for testing purposes in the Samsung devices. These files are there to make sure that the functionality of your device is error-free, before making its final release. These files are created by Samsung company and are found in only their devices.
Combination ROM Advantages:
Its help you to repair imie number in some models like S8/S8 plus S7/S7 Edge S6/S6 Edge…
Its very useful in bypass samsung account in too many models.
Its very useful in bypass Google account in too many models.
Its very useful for downgrade in some models.
Its help you to enable usb debugging.
its help to remove any security FRP / Reactivation Lock from Samsung like 2016-2019
You can find Combination Files for Galaxy S8 devices here:
G950U with latest Bootloader: http://www.mediafire.com/file/j8xi2n73zhh37q1/COMBINATION_FA70_G950USQU5ARG4.zip
G950F (currently only for 4x Bootloader): http://www.mediafire.com/file/c37zq...QB19841686_REV00_user_mid_noship.tar.rar/file
Here is a Video of Downgrading a Galaxy S6 Edge with Combination File : https://www.youtube.com/watch?v=dOKJcHU1pXM Should work with S8 too

Hello, nice tutorial!
Want to ask:
"Combination files are basically used for testing purposes in the Samsung devices. These files are there to make sure that the functionality of your device is error-free, before making its final release. These files are created by Samsung company and are found in only their devices. "
So only Samsung releases these files to public? or are leaked?
I`m asking to check if I should wait or not, I had V4 bootloader but recently by accident with the latest update I got V5

rilley said:
Hello, nice tutorial!
Want to ask:
"Combination files are basically used for testing purposes in the Samsung devices. These files are there to make sure that the functionality of your device is error-free, before making its final release. These files are created by Samsung company and are found in only their devices. "
So only Samsung releases these files to public? or are leaked?
I`m asking to check if I should wait or not, I had V4 bootloader but recently by accident with the latest update I got V5
Click to expand...
Click to collapse
I would recommend you to wait till the latest Combination File gets public for the G950F/G955F. They do work very good and are also stable. Usually I think Samsung does not public These files online but they get leaked very often. I used the Combination File to Downgrade my S6 from 7.0 with Bootloader 6 to 5.1.1 with Bootloader 2.
Im sorry but I can only explain the function of a Combination Rom along with the Galaxy S6..
Once Cthe latest Combination File is available, do this:
1. Download your Nougat/Oreo Firmware you want to install
2. Download Combination File with the latest Bootloader Version
3. Downlad 7zip, since you Need to edit the firmware you want to install
3b) Extract the firmware you want to install to a new Folder
3c) Delete all files except for boot.img, cache.img, recovery.img and system.img
3d) Open 7zip from your Start Menu and locate the firmware Folder
3e) Mark the remaining files and press the green "Add" Button at the upper left corner and create a tar (Odin Flashable) file
4)Download Odin
5) First uncheck Auto-Reboot
6) Now first Flash the Combination File
7) Afterwards go directly again in Download Mode and Flash the tar- firmware File
8) Reboot your phone and do a wipe
9) Congrats! You now have Stock 7.0/8.0 Back!
Notes: Fingerprintscanner wont work, because it is a part of cm.bin, OTA Updates wont work as well, Dont worry if you see a green text next to the Phone logo while starting it. Thats normal and not an error.
Backup your files before you do that!

I hope it helped you

halloo13 said:
I hope it helped you
Click to expand...
Click to collapse
Yes, many thanks for response!
I guess I will wait until I get the combination of files, but until then I want to switch CSC, found a solution to use THAI sim card, but not sure, if everything goes ok, I guess the new OTA update will be the latest from THAI, there are no changes to get bricked by this method right? ( I will be able to get back to the ROM stock that I have now? )

halloo13 said:
I would recommend you to wait till the latest Combination File gets public for the G950F/G955F. They do work very good and are also stable. Usually I think Samsung does not public These files online but they get leaked very often. I used the Combination File to Downgrade my S6 from 7.0 with Bootloader 6 to 5.1.1 with Bootloader 2.
Im sorry but I can only explain the function of a Combination Rom along with the Galaxy S6..
Once Cthe latest Combination File is available, do this:
1. Download your Nougat/Oreo Firmware you want to install
2. Download Combination File with the latest Bootloader Version
3. Downlad 7zip, since you Need to edit the firmware you want to install
3b) Extract the firmware you want to install to a new Folder
3c) Delete all files except for boot.img, cache.img, recovery.img and system.img
3d) Open 7zip from your Start Menu and locate the firmware Folder
3e) Mark the remaining files and press the green "Add" Button at the upper left corner and create a tar (Odin Flashable) file
4)Download Odin
5) First uncheck Auto-Reboot
6) Now first Flash the Combination File
7) Afterwards go directly again in Download Mode and Flash the tar- firmware File
8) Reboot your phone and do a wipe
9) Congrats! You now have Stock 7.0/8.0 Back!
Notes: Fingerprintscanner wont work, because it is a part of cm.bin, OTA Updates wont work as well, Dont worry if you see a green text next to the Phone logo while starting it. Thats normal and not an error.
Backup your files before you do that!
Click to expand...
Click to collapse
Hi, ok but it means that i cannot use fingerprint or ota update anymore or after dowgrade could i install full stock firmware with odin and recovery functionalities?

Will this trip Knox?

Any idea if I can downgrade from pie on a S8+ on bootloader 6?

I've tried this method on my S7 edge but I've stucked on step - deleting files.
After extracting the firmware I get 5 files- Ap, Bl ect.
When i extract the AP file (previously deleting "md5" from the name, and becoming rar file) there are only 3 new files (nothing for delete if i remembering correctly)
Files i need to delete are on other files from extracted firmware.
At the end I finished on unsuccessful flash.
I want to go back to nougat on my S8+ (955f), but i dont want to take risks, so I did flashing on old device with corect firmware.
I'm really mad at Samsung. Battery life become horrible at pie. Thats why I want to go back to nougat or at least oreo.
I will post some videos after day or two how is possible to downgrade android version on some Samsung devices with higher bootloader version. These methods didn't worked for me but may be they will encourage some of you to make possible the downgrade.

As I promised:
1. Interesting way to downgrade Samsung Device (J series) when touchscreen does not working:
https://www.youtube.com/watch?v=SmfgxoUhflA&feature=emb_title
2. Second method:
https://www.youtube.com/watch?v=ZKg1DC4ul_g&feature=emb_title
As I remember oreo and nougat have pro mode on video recording and faster charging speed. I hope someone to explain is it possible to downgrade S8 and whats are the steps with this method.

so if i want to downgrade to firmware with bootloader v4 but my phone has now v6, will i download combination file with bootloader 6 or 4? I didn't get that part, sorry. i have s8+
edit: ok, 4 didn't work, so i guess need to get 6

Does anyone know the password for the linked Combination file?

Thanks for this thread.
I want to downgrade from Oreo to nougat too, I'm on "U1" security patch, but I don't understand the order of bootloader version... Can you try to explained how to ?
I found this if it can help : https://combinationfirmware.com/combination-samsung-galaxy-s8/

Scylla.bx said:
Thanks for this thread.
I want to downgrade from Oreo to nougat too, I'm on "U1" security patch, but I don't understand the order of bootloader version... Can you try to explained how to ?
I found this if it can help : https://combinationfirmware.com/combination-samsung-galaxy-s8/
Click to expand...
Click to collapse
Since you are on bootloader version 1, you don't need the combination files. If you were past version 2 they would be needed.
Once you update to a new bootloader you can't go back to software on the older bootloader without the combination files.

Kaloob said:
Since you are on bootloader version 1, you don't need the combination files. If you were past version 2 they would be needed.
Once you update to a new bootloader you can't go back to software on the older bootloader without the combination files.
Click to expand...
Click to collapse
Thank you for your reply.
Ok so if im on the right bootloader for Nougat, why can i install this rom ?
[S8/S8+][Nougat][01-Jan-2020][v30] LightROM
In fact i can install it, all seem to be fine, no error in twrp, but at reboot it freeze at bootloader
Thanks for your help bro

Scylla.bx said:
Thank you for your reply.
Ok so if im on the right bootloader for Nougat, why can i install this rom ?
[S8/S8+][Nougat][01-Jan-2020][v30] LightROM
In fact i can install it, all seem to be fine, no error in twrp, but at reboot it freeze at bootloader
Thanks for your help bro
Click to expand...
Click to collapse
If you have an Exynos version, maybe ask around on that thread.
If you have a Snapdragon variant, you can't flash that ROM.

Kaloob said:
If you have an Exynos version, maybe ask around on that thread.
If you have a Snapdragon variant, you can't flash that ROM.
Click to expand...
Click to collapse
I have exynos. Anyway thank for your help, i try to post on that thread and hope someone could figure it out.
Peace

Did anyone find the password for the file?

necklickhia said:
Does anyone know the password for the linked Combination file?
Click to expand...
Click to collapse
Password I had to find it elsewhere: "www.samkey.org/forum" without the quotes

(Root Guide) Samsung Galaxy J7 Prime J727t1 (U4 Only)

Finally, a method to root the Galaxy J7 Prime!!!!
Do note, this root isnt perfect. Root has to be manually started every reboot via ADB or the included bat script.
By installing this, you will not loose any data. I still would be wise to backup your devices regadless.
This root package only supports firmware U4. Odin will not flash these files if your build is above U4.
If you are on a build lower that U4, do not flash this, you will softbrick your device.
I can provide the U4 update if people need it. TBA
J727t1 U4 Odin Firmware
The Steps
1. Download and Extract the zip package to your desktop. --------> J727t1 Root.zip
2. Go into J727t1 Root\Odin Firmware and run odin.
3. Click BL and select "Put in BL Slot ENGSboot.tar" (Its in the Odin_Firmware folder)
4. Click AP and select "Put in AP slot ENGRoot.tar" (Its in the Odin_Firmware folder)
5. Power off you device, and then by pressing and holding "Power Vol_Down and Home" boot into download mode. (Dont forget to press Volume Up when prompted)
6. Connect your phone and then click start. Let your phone reboot.
7. Once booted, go into Go into J727t1 Root and run Install_Root.bat . Let your phone reboot again.
8. Now finally, in the J727t1 Root folder run 00activate_root.bat
You are now rooted and SuperSu should work until you reboot your phone.
Additional notes:
NO OEM UNLOCK NEEDED
The Install_Root.bat puts the bat file to activate root on your device.
That way, if your out and about while your phone reboots, you just need
a computer to reactivate root. lol lol

xxMoon said:
Finally, a method to root the Galaxy J7 Prime!!!!
Do note, this root isnt perfect. Root has to be manually started every reboot via ADB or the included bat script.
By installing this, you will not loose any data. I still would be wise to backup your devices regadless.
This root package only supports firmware U4. Odin will not flash these files if your build is above U4.
If you are on a build lower that U4, do not flash this, you will softbrick your device.
I can provide the U4 update if people need it. TBA
The Steps
1. Download and Extract the zip package to your desktop. --------> J727t1 Root.zip
2. Go into J727t1 Root\Odin Firmware and run odin.
3. Click BL and select "Put in BL Slot ENGSboot.tar" (Its in the Odin_Firmware folder)
4. Click AP and select "Put in AP slot ENGRoot.tar" (Its in the Odin_Firmware folder)
5. Power off you device, and then by pressing and holding "Power Vol_Down and Home" boot into download mode. (Dont forget to press Volume Up when prompted)
6. Connect your phone and then click start. Let your phone reboot.
7. Once booted, go into Go into J727t1 Root and run Install_Root.bat . Let your phone reboot again.
8. Now finally, in the J727t1 Root folder run 00activate_root.bat
You are now rooted and SuperSu should work until you reboot your phone.
Additional notes:
NO OEM UNLOCK NEEDED
The Install_Root.bat puts the bat file to activate root on your device.
That way, if your out and about while your phone reboots, you just need
a computer to reactivate root. lol lol
Click to expand...
Click to collapse
Maybe, if you tried incorporating flashing Magisk or using Magisk to patch a boot.img and flashing that into this process, somehow, you might be able to keep persistent root.
Sent from my SM-S767VL using Tapatalk

You cant, the bootloader is locked. Any changes to boot, recovery or sboot trigger no boot.

xxMoon said:
You cant, the bootloader is locked. Any changes to boot, recovery or sboot trigger no boot.
Click to expand...
Click to collapse
Ah, I thought this method might have involved using an engineering(factory test) firmware that had a bootloader that would allow modification even with a locked bootloader or even allow the bootloader to be unlocked. I've seen similar steps and method used with that type of firmware. My mistake.
Sent from my SM-S767VL using Tapatalk

As for making it persistent, the only sh files the boot.img .rc's load are install-recovery.sh and init.sec.boot.sh . Patching them to load the su daemon does nothing. Gotta be a permission thing preventing them from running. Maybe its just a exynos oreo thing... Any ideas people?

xxMoon said:
As for making it persistent, the only sh files the boot.img .rc's load are install-recovery.sh and init.sec.boot.sh . Patching them to load the su daemon does nothing. Gotta be a permission thing preventing them from running. Maybe its just a exynos oreo thing... Any ideas people?
Click to expand...
Click to collapse
Your device doesn't have the OEM unlock setting? Factory test/Engineering firmware typically do.
Sent from my SM-S767VL using Tapatalk

Droidriven said:
Your device doesn't have the OEM unlock setting? Factory test/Engineering firmware typically do.
Click to expand...
Click to collapse
They dont, ive tested every build, they dont have it baked in. I looked throug, the decompiled secsettings.apk oem unlock is there, but something is disabling it.

xxMoon said:
They dont, ive tested every build, they dont have it baked in. I looked throug, the decompiled secsettings.apk oem unlock is there, but something is disabling it.
Click to expand...
Click to collapse
You mean the setting is there but it is greyed out? Have you tried the trick involving changing the date in system settings to a month or so ago? It bypasses the block that some carriers use that involves a set amount of time having to pass before the setting can be altered, once the time limit expires, the setting is available. Changing the date can trick this into thinking that the proper amount of time has passed.
Sent from my SM-S767VL using Tapatalk

Droidriven said:
You mean the setting is there but it is greyed out? Have you tried the trick involving changing the date in system settings to a month or so ago? It bypasses the block that some carriers use that involves a set amount of time having to pass before the setting can be altered, once the time limit expires, the setting is available. Changing the date can trick this into thinking that the proper amount of time has passed.
Click to expand...
Click to collapse
No, oem unlock doesnt show period, no matter what is done. As for init.d support, after looking through the kmsg, I discover defex was blocking it. I did find one gem though, after looking through the init.rc file, it looks for an rc file that doesnt exist. I can make an rc file with the name its looking for and put it in the directory where it should be, init will run it. But still anything that involves running sec-sh or su gets blocked by defex during init.

xxMoon said:
No, oem unlock doesnt show period, no matter what is done. As for init.d support, after looking through the kmsg, I discover defex was blocking it. I did find one gem though, after looking through the init.rc file, it looks for an rc file that doesnt exist. I can make an rc file with the name its looking for and put it in the directory where it should be, init will run it. But still anything that involves running sec-sh or su gets blocked by defex during init.
Click to expand...
Click to collapse
There is a .zip that can be flashed to bypass defex. If you have root, you can try flashing that .zip via Flashify or similar app.
There is a zip for disabling dm-verity also.
There is also a RMM fix that can be flashed via Odin.
Where did you get the files that you used to gain root? Where they specific to your device? Did you create them yourself? If you made them yourself, what did you use to make them, did you modify them yourself, if so, what about them did you modify?
I'm asking all this because I'm trying to root a SM-J737A and a SM-S767VL. I've tried all kinds of tricks trying to flash TWRP or Magisk. I don't think I can make it work so I wanted to try your method if nothing else. I just want to know if I need to modify your method to be compatible with my devices. If so, what do I need to modify or at least, where can I find information to make those modifications, if needed?
I see that your files are ENG files, did you get these from the engineering firmware for your device? I have the engineering firmware for both of the devices I listed, they are both U4, the full cstock firmware for both are S4. The J737A has the OEM unlock setting and it is enabled but in download mode it still says KG State: prenormal. The S767VL does not have the OEM unlock setting but in download mode it says KG State: checking. It's confusing and contradictory.
What do I need to adapt files from these firmware to use on these devices?
Sent from my SM-S767VL using Tapatalk

Yeah any zip that modifies the ramdisk wont work. My suggestion for you is to scour the web for an eng root boot img. They give you a rooted adb which means you can do root stuff in the shell. They are signed by Samsung so they can flash via odin no problem.

https://gsm-firmware.com/index.php?a=downloads&b=folder&id=14315
If you contact this place, they offer eng root boot.imgs, i think they charge for em though.

Droidriven said:
I see that your files are ENG files, did you get these from the engineering firmware for your device? I have the engineering firmware for both of the devices I listed, they are both U4, the full cstock firmware for both are S4. The J737A has the OEM unlock setting and it is enabled but in download mode it still says KG State: prenormal. The S767VL does not have the OEM unlock setting but in download mode it says KG State: checking. It's confusing and contradictory.
What do I need to adapt files from these firmware to use on these devices?
Click to expand...
Click to collapse
Most of the newer factory combination roms are pretty secure. I think engroot files are made specifically for official firmwares, just have to match the builds. The sboot from my package is from a combination rom, had to use it to allow for system modifications. If you use just the engroot, all the files you push to /system dissappear after a reboot.

xxMoon said:
Yeah any zip that modifies the ramdisk wont work. My suggestion for you is to scour the web for an eng root boot img. They give you a rooted adb which means you can do root stuff in the shell. They are signed by Samsung so they can flash via odin no problem.
Click to expand...
Click to collapse
As in eng root boot.img specific to my model number and U4 binary? Or any eng boot.img from any 7870 J7 variant with U4?
Sent from my SM-S767VL using Tapatalk

Droidriven said:
As in eng root boot.img specific to my model number and U4 binary? Or any eng boot.img from any 7870 J7 variant with U4?
Click to expand...
Click to collapse
They are specific to your model number. They are also specific to your build, preferably you want it to match yours. If its a lower build they wont flash.

xxMoon said:
They are specific to your model number. They are also specific to your build, preferably you want it to match yours. If its a lower build they wont flash.
Click to expand...
Click to collapse
not specific to build, but specific to Binary, you cant write U4 stuff on U3 firmware.

yurais said:
not specific to build, but specific to Binary, you cant write U4 stuff on U3 firmware.
Click to expand...
Click to collapse
I could be mistaken, but, the U3 engineering firmware can be flashed over U4 full stock firmware, but the U3 full stock firmware can not be flashed over U4 full stock firmware.
Sent from my SM-S767VL using Tapatalk

Droidriven said:
I could be mistaken, but, the U3 engineering firmware can be flashed over U4 full stock firmware, but the U3 full stock firmware can not be flashed over U4 full stock firmware.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
As far as I know , you can't downgrade any thing from U4 to U3, not stock and not ENG.
Enviado desde mi SM-G960U mediante Tapatalk

xxMoon said:
Finally, a method to root the Galaxy J7 Prime!!!!
Do note, this root isnt perfect. Root has to be manually started every reboot via ADB or the included bat script.
By installing this, you will not loose any data. I still would be wise to backup your devices regadless.
This root package only supports firmware U4. Odin will not flash these files if your build is above U4.
If you are on a build lower that U4, do not flash this, you will softbrick your device.
I can provide the U4 update if people need it. TBA
The Steps
1. Download and Extract the zip package to your desktop. --------> J727t1 Root.zip
2. Go into J727t1 Root\Odin Firmware and run odin.
3. Click BL and select "Put in BL Slot ENGSboot.tar" (Its in the Odin_Firmware folder)
4. Click AP and select "Put in AP slot ENGRoot.tar" (Its in the Odin_Firmware folder)
5. Power off you device, and then by pressing and holding "Power Vol_Down and Home" boot into download mode. (Dont forget to press Volume Up when prompted)
6. Connect your phone and then click start. Let your phone reboot.
7. Once booted, go into Go into J727t1 Root and run Install_Root.bat . Let your phone reboot again.
8. Now finally, in the J727t1 Root folder run 00activate_root.bat
You are now rooted and SuperSu should work until you reboot your phone.
Additional notes:
NO OEM UNLOCK NEEDED
The Install_Root.bat puts the bat file to activate root on your device.
That way, if your out and about while your phone reboots, you just need
a computer to reactivate root. lol lol
Click to expand...
Click to collapse
Got a bootloop after flashing files , but it is because battery was drained
Replaced battery and all is well.
Is it engRoot boot.img file the same than extracting boot.img from combination firmware ?

yurais said:
delete it
Click to expand...
Click to collapse
No

Did anybody unlock the bootloader and root the unit?

As topic asked.
It looks like OEM unlock (in developers settings) is hidden on US phone models
The last Samsung I made root was S5e and I am wondering is S6L possible

sadly no
Nope, Samsung hasn't even released the stock firmware yet so any development is currently halted

Can the user unlock the bootloader then?

Haven't tried it, but it should be possible

I don't know about unlocking the bootloader. This page (updated in Apr 2020) showed a way https://www.getdroidtips.com/root-samsung-galaxy-tab-s6-lite/ to root it. I haven't tried it yet. If anybody tries, please leave some comments.
Edit: how to unlock the bootloader https://gearallnews.com/how-to-unlock-bootloader-of-samsung-galaxy-tab-s6-lite-guide-2020-2/

I managed to unlock the bootloader with the tutorial on http://androidbiits.com/root-samsung-galaxy-tab-s6-lite-sm-p610-sm-p610x-easily/, but rooting with the Magisk file failed.
I think i will try it later.
The bootlader is now unlocked, so it gives me a warning on the screen every time i boot the tablet.
I have the P610 version, only WiFi, no LTE

I tried it for the second time and now succeeded.
Installed Titanium Backup and removed some useless system apps.

Iceman66 said:
I tried it for the second time and now succeeded.
Installed Titanium Backup and removed some useless system apps.
Click to expand...
Click to collapse
Has Samsung released the firmware tho? I wanted to root but scared if the process failed I cant flash the old ROM

StuKaGel said:
Has Samsung released the firmware tho? I wanted to root but scared if the process failed I cant flash the old ROM
Click to expand...
Click to collapse
You can find it here: https://samfrew.com/model/SM-P610/ I found the link in the turorial.
Be aware that this is for P610 (only Wifi), but you can find the firmware for the other versions off the S6 Lite as well on this website.

Iceman66 said:
I tried it for the second time and now succeeded.
Installed Titanium Backup and removed some useless system apps.
Click to expand...
Click to collapse
Hi, thank you very much for reporting it. Do you know if Netflix still works after the unlocking and rooting?

dxxvi said:
Hi, thank you very much for reporting it. Do you know if Netflix still works after the unlocking and rooting?
Click to expand...
Click to collapse
Yes, Netflix works after installing Magisk module liboemcrypto disabler :good:

Iceman66 said:
dxxvi said:
Hi, thank you very much for reporting it. Do you know if Netflix still works after the unlocking and rooting?
Click to expand...
Click to collapse
Netflix works after installing Magisk module liboemcrypto disabler :good:
Click to expand...
Click to collapse
I just read about that module. I post the info here for lazy people like me "Please note that a consequence of using this module is that Widevine DRM will fall back to using L3 instead of L1. This means that Netflix will play all content in SD quality, regardless of your subscription type"
https://forum.xda-developers.com/apps/magisk/magisk-liboemcrypto-disabler-drm-t3794393

dxxvi said:
I just read about that module. I post the info here for lazy people like me "Please note that a consequence of using this module is that Widevine DRM will fall back to using L3 instead of L1. This means that Netflix will play all content in SD quality, regardless of your subscription type"
https://forum.xda-developers.com/apps/magisk/magisk-liboemcrypto-disabler-drm-t3794393
Click to expand...
Click to collapse
The strange thing is, that after removing the module and rebooting tablet, Netflix is still working

Iceman66 said:
I managed to unlock the bootloader with the tutorial on http://androidbiits.com/root-samsung-galaxy-tab-s6-lite-sm-p610-sm-p610x-easily/, but rooting with the Magisk file failed.
I think i will try it later.
The bootlader is now unlocked, so it gives me a warning on the screen every time i boot the tablet.
I have the P610 version, only WiFi, no LTE
Click to expand...
Click to collapse
I tried using this guide and am getting a vbmeta signature failure upon flashing with odin. Did you run into any issues like that when you got your device rooted? I'm also using the P610

Same here. Not a noob despite being long time lurker and not posting. I have been rooting devices forever but this one is escaping me.
Using the guide and getting a vbmeta signature failure as well. I tries 3 various firmware versions to Magisk patch the required 4 files, but get the same error every time.
So close yet so far...
Thanks
Eric

Iceman66 said:
The strange thing is, that after removing the module and rebooting tablet, Netflix is still working
Click to expand...
Click to collapse
Yes, it does work but won't go above SD.
I bought the S6 Lite as a replacement for a Tab Pro 10.1 (SM-T520) which was running LOS 14.1. Netflix was working, but looked like crap. Downloading prior to watching improves the quality a bit, but you could see it is SD instead of HD.
I have rooted every Android devices I have had, but this time I do not want to lose the Widevine L1 certification. The SM-T520, which was in 2014 Samsung's high end tablet (>$600), only had one update from 4.4.2 to 4.4.4....rooting was the only way to move up. I hope Samsung will support this device a little better.

b0bness said:
I tried using this guide and am getting a vbmeta signature failure upon flashing with odin. Did you run into any issues like that when you got your device rooted? I'm also using the P610
Click to expand...
Click to collapse
Here is what ik did:
Starting from the step when the firmware is downloaded
Unpack the firmware with Winrar
Select the boot.img l4 file and use 7-Zip to transform it to boot.img
Transfer the boot.img file to tablet and patch the file with Magisk manager
Transfer the patched-boot.img to computer
Rename the file to boot.img
Put tablet in Bootloader-mode
Flash the boot.img with Odin 3.14
The first Block in Odin will turn green if flashing is succesfull
Now start up the tablet
In my case, a got a message that the software is damaged, i choose the option to restore to factor settings
After a few minutes the tablet booted and i installed Root-checker, rooting was succesfull

Iceman66 said:
Here is what ik did:
Starting from the step when the firmware is downloaded
Unpack the firmware with Winrar
Select the boot.img l4 file and use 7-Zip to transform it to boot.img
Transfer the boot.img file to tablet and patch the file with Magisk manager
Transfer the patched-boot.img to computer
Rename the file to boot.img
Put tablet in Bootloader-mode
Flash the boot.img with Odin 3.14
The first Block in Odin will turn green if flashing is succesfull
Now start up the tablet
In my case, a got a message that the software is damaged, i choose the option to restore to factor settings
After a few minutes the tablet booted and i installed Root-checker, rooting was succesfull
Click to expand...
Click to collapse
Thanks for the steps, got it working! To add a note for those reading the above comment. After renaming the file to boot.img, use 7z and 'add to archive' the boot.img to make it a boot.tar for Odin to be able to flash it.
Another thing that might help folks: The boot.img.l4z wasn't working with 7z to decompress the l4z. I installed l4z and moved the boot.img.l4z into the folder with l4z.exe. Then I ran the command 'l4z boot.img.l4z boot.img' in the folder where l4z.exe was located to get the boot.img.

Сan some one to upload a ready-made installation ROM file for direct flashing into Odin please? Cause I can not understand how to transfer and patch all this different parts together. I don't understand which files I need to marry each other
Please help to root with MAgisk tab6 lite (wifi only SM-P610).

Iceman66 said:
Here is what ik did:
Starting from the step when the firmware is downloaded
Unpack the firmware with Winrar
Select the boot.img l4 file and use 7-Zip to transform it to boot.img
Transfer the boot.img file to tablet and patch the file with Magisk manager
Transfer the patched-boot.img to computer
Rename the file to boot.img
Put tablet in Bootloader-mode
Flash the boot.img with Odin 3.14
The first Block in Odin will turn green if flashing is succesfull
Now start up the tablet
In my case, a got a message that the software is damaged, i choose the option to restore to factor settings
After a few minutes the tablet booted and i installed Root-checker, rooting was succesfull
Click to expand...
Click to collapse
[i followed your steps but now i get the [BLOCKED BY OEM LOCK] when using odin to flash boot.
i unlocked bootloader in developer settings. no idea what step i missed.
am using Firmware U1ATF2