Database Info

[STOCK][TWRP BACKUP][UPDATE] AT&T H910_10L Stock Recovery, Boot, and System Image

Below are links to full backups that can be restored in TWRP for the H910 after the Dirty Santa exploit. This is useful for restoring a bad install once you have access to TWRP. I will outline three methods for install below that will help in putting back the TWRP backups, a good method for installing it, and a few suggestions I have from restoring my device about 10 times now. So without further ado.
UPDATE: I bricked my device and had to send it off for repair (turns out I can't just flash US996 firmware for funsies) I received my phone back with the still rootable OTA 10L and yesterday I rooted it again and uploaded the new firmware. So if you're an AT&T user who wants the second latest update (10M dropped 04-15 but it isn't rootable as far as I know) then you can grab this and run it along with the stock kernel I made a backup of. I'll update the links below to reflect this. Stock 10L kernel located in tips section. Not flashable, you must extract and install as image and immediately install SuperSU 2.79 or greater or your device won't boot!
How to Install and Restore Stock Images and Boot (Kernel) Image
1.) DOWNLOAD - https://www.androidfilehost.com/?fid=673368273298948069 (Updated to 10L) download the file and verify the MD5sum of the zip matches the file you downloaded. (System image link for devs posted at the bottom)
1a) Download the latest SuperSU 2.79 flashable zip from here: http://www.supersu.com/download
2.) EXTRACT --This is not a flashable zip-- extract the zip file wherever you would like so that it can be copied to the device
3.) COPY - The extracted folder to TWRP > BACKUPS > (paste here) on either the MicroSD card (preferable) or internal storage (This will be wiped when you format data)
4.) REBOOT TO RECOVERY - Once the folders are copied to the backup directory you can reboot to TWRP to begin the restore process.
5.) WIPE - This is getting two sections in order to account for two situations
5a) MICROSD - If you have a MicroSD card and copied the restore files to it wipe everything: Data, Cache, Dalvik/ART, Internal Storage, and System.
5b) INTERNAL STORAGE - If you don't have a MicroSD card installed only wipe the following: Data, Cache, Dalvik/ART, and System.
6.) REBOOT TO RECOVERY - Once you have wiped everything, especially if you wiped internal storage, you should reboot TWRP before you start the restore process
7.) RESTORE - Back in TWRP Choose Restore from the main menu and if you can't see your restore file choose "Select Storage" at the bottom and inside that folder uncheck RECOVERY unless you want to overwrite TWRP (which I recommend against).
7a) I would recommend checking the box "Enable MD5 Verification of Backup Files" which is a little slower but ensures a good restoration
8.) SWIPE - Swipe to begin the operation and it will alert you upon completion. You will need a very large amount of space on your card to do it since the system image is split into 3 packages
9.) ROOT - Do not reboot until you have rooted! The unlocked bootloader will prevent booting on the stock kernel. The stock kernel can be used if it is rooted first, otherwise you will be stuck on the LG Boot logo.
10.) REBOOT TO SYSTEM - The phone will reboot itself! Don't panic, this is part of the standard rooting procedure. Now, see tips at the bottom for best performance.
TIPS!
- This is the 10L update stock kernel made during dirty santa method. This kernel has all features working minus the static on boot being gone, but Wifi calling, comfort view, FM radio, etc are fixed using this kernel. https://www.androidfilehost.com/?fid=817550096634762281 (You must flash SuperSU 2.79 or greater after flashing this kernel before you reboot! Not Flashable, must extract)
- To use the above kernel, download his ROM and extract the boot.img file from that archive. Save it to your device, boot to TWRP, choose Install, Install Image, and click the boot.img file. Then choose the checkbox for "boot" and swipe to flash. Really important to install SuperSU again after installing the custom kernel.
- Boot-up static can be cleared by allowing phone to boot to screen off, placing it face down to turn of second screen, and then flipping it back over. Static will be gone until next boot.
- Using fstrim after wiping in TWRP is good for increasing flash drive performance. Go to TWRP > Advanced > Terminal and type fstrim -v /data/
- You can do fstrim on /system and /cache as well to get all three partitions running clean
- Some of the AT&T apps that you can remove with TiBu are tied to bootup. Be careful what you remove if you like to get past the AT&T logo.
- The button combo to get into TWRP from powered off is Vol Down + Power until the LG Logo appears then let go of power and immediately press power again.
- That button combo boots you to a screen asking it you want to wipe your device. Answering 'yes' to both questions boots you to TWRP.
10L System Image Link for ROM creation (In TWRP emmc format): https://www.androidfilehost.com/?fid=745425885120724506
THANKS!
Google - Because, Android
@me2151 for the unlock and root method (and bricking his phone for us; sorry that happened to your device)
@glitschi667 for the work he did on Dirty Santa with me2151
@jcadduono for getting TWRP ready for us despite not having a V20 at all
@Tilde88 for compiling the kernel sources and creating an excellent ROM for all rooted variants of the device!
@EMSpilot for the debug phone!
@elliwigy for helping everyone troubleshoot and test everything recently
If I forgot you, and believe me a lot of people deserve to be here, let me know and I'll add you

9.) ROOT - Do not reboot until you have rooted! The unlocked bootloader will prevent booting on the stock kernel. The stock kernel can be used if it is rooted first, otherwise you will be stuck on the LG Boot logo. [/QUOTE] What exact method of rooting do you mean, without rebooting? Do you mean just flashing SuperSU? Can you clarify? THANKS for everything! Hoping this gets me out of my semi-brick. No matter what I flash...it keeps reverting back to TWRP.
EDIT: I did this, exactly...and yet again...I'm stuck in the phone autobooting back to TWRP. Any suggestions? Is this bricked?

jreed3786 said:
9.) ROOT - Do not reboot until you have rooted! The unlocked bootloader will prevent booting on the stock kernel. The stock kernel can be used if it is rooted first, otherwise you will be stuck on the LG Boot logo. What exact method of rooting do you mean, without rebooting? Do you mean just flashing SuperSU? Can you clarify? THANKS for everything! Hoping this gets me out of my semi-brick. No matter what I flash...it keeps reverting back to TWRP.
EDIT: I did this, exactly...and yet again...I'm stuck in the phone autobooting back to TWRP. Any suggestions? Is this bricked?
Click to expand...
Click to collapse
If you do a battery pull and can get to TWRP you are not bricked. However, I have no idea what you did to get a bootloop. What kernel did you install: the stock one from TWRP or Tilde88's kernel from his ROM? Either way, if you did this:
Wipe > Restore (Boot and System) > Install SuperSU 2.79 zip > Reboot
then you did the correct steps. The issue of not having SuperSU installed on my device was not booting past the LG logo and never rebooting. However, the method I most recently followed was:
Wipe > Restore (boot and system) > Install Tilde88 kernel > Flash SuperSU > Reboot
and my phone has been running extremely well. I need way more info from you before I can help you further.

AlkaliV2 said:
If you do a battery pull and can get to TWRP you are not bricked. However, I have no idea what you did to get a bootloop. What kernel did you install: the stock one from TWRP or Tilde88's kernel from his ROM? Either way, if you did this:
Wipe > Restore (Boot and System) > Install SuperSU 2.79 zip > Reboot
then you did the correct steps. The issue of not having SuperSU installed on my device was not booting past the LG logo and never rebooting. However, the method I most recently followed was:
Wipe > Restore (boot and system) > Install Tilde88 kernel > Flash SuperSU > Reboot
and my phone has been running extremely well. I need way more info from you before I can help you further.
Click to expand...
Click to collapse
Shoot...I think I followed your instructions in Tilde88's thread....and hit reboot instead of flashing his kernel. I then went back in to TWRP to reflash the entire thing...and the kernel...and I was given crap about encryption. Then, that's when the bootloop started. Right now, I'm sitting on TWRP. I've tried flashing everything, per instructions....but I guess, what I'm asking, is...since I'm on TWRP...and it's bootlooping because of encryption...what would you personally do? Shoot...I'll pay ya if you can fix this! LOL. I just really never dealt with the encryption thing until this phone...never really had problems till now.
---------- Post added at 09:28 AM ---------- Previous post was at 09:12 AM ----------
FLASHED EXACTLY THE WAY YOU DID (WITHOUT THE REBOOTING TO RECOVERY IN THE OP)...NOW, IT GETS TO STATIC, THEN LG SCREEN, REBOOTS ONCE TO STATIC THEN BOOTS UP!!! YAY!!! :good::highfive:
I guess there's no need to REBOOT TO RECOVERY if a person faces encryption issues and is trying to fix their phone. Even after decrypting, I came up with issues. Now let's see if this this asks for my PIN on reboot. THAT was another issue!
IT WORKED!!! THANKS! I'LL now try to go back into TWRP and flash the Tilde's boot.img

So...by flashing your STOCK TWRP backup...per your instructions, I was TOTALLY FIXED...I then didn't even flash Tilde88's kernel...I immediately rebooted back to TWRP, and DID NOT WIPE...but immediately flashed his ROM....and BOOM! Google Now/Always On works flawlessly, zero lag! AWESOME!
So, to all that are having issues with no Google Now/Always On...follow this instructional on this thread and DO NOT wipe after flashing Tilde's rom.
BTW, I shot you a PM, bro! :highfive::good:

jreed3786 said:
So...by flashing your STOCK TWRP backup...per your instructions, I was TOTALLY FIXED...I then didn't even flash Tilde88's kernel...I immediately rebooted back to TWRP, and DID NOT WIPE...but immediately flashed his ROM....and BOOM! Google Now/Always On works flawlessly, zero lag! AWESOME!
So, to all that are having issues with no Google Now/Always On...follow this instructional on this thread and DO NOT wipe after flashing Tilde's rom.
BTW, I shot you a PM, bro! :highfive::good:
Click to expand...
Click to collapse
Nothing like some good news to start the day. I wanted to let you know that the reason this worked is that it is essentially a dirty flash that replaces the stock kernel and adds his ROM tweaks into my stock system. So once it had booted and you flashed over it you were able to keep the stock files needed to get screen off Google Now working while adding his audio tweaks and build.prop because they overwrite the stock files. Since my stock files are odexed and his are not I'm not sure how well all your system files will function since they've been overwritten but if you have no issues then no harm, no foul.
I'm glad this got sorted and to anyone else if you follow this guide and you have any confusion about the instructions just do an @AlkaliV2 and I will do my best to help and I will also fix up the guide so that it is less confusing. Just let me know.

Stuck again....in TWRP.
Delete please

Same issue
i followed it to the letter yet i still keep being returned to team win recovery no matter what i do.

Great step by step instructions. Thanks!

sikiro said:
i followed it to the letter yet i still keep being returned to team win recovery no matter what i do.
Click to expand...
Click to collapse
Try booting into your bootloader (fastboot) and type:
fastboot erase misc
fastboot erase cache
fastboot erase fota
fastboot reboot
See if that helps you at all. Make sure you have a valid ROM flashed correctly though.

im having trouble, i downloaded the file, and i put the extracted folder into TWRP>BACKUPS but when i go to restore on TWRP theres no files to be open, am i supposed to keep the file as a zip or?

prlatorre said:
im having trouble, i downloaded the file, and i put the extracted folder into TWRP>BACKUPS but when i go to restore on TWRP theres no files to be open, am i supposed to keep the file as a zip or?
Click to expand...
Click to collapse
I was having the same issue, do a backup(choose something small) from TWRP. It will create the TWRP>Backups Folder for you and then you can place the extracted zip. from this thread into that folder and it will see it.

ajairola said:
I was having the same issue, do a backup(choose something small) from TWRP. It will create the TWRP>Backups Folder for you and then you can place the extracted zip. from this thread into that folder and it will see it.
Click to expand...
Click to collapse
i've tried what you suggested, and still nothing seems to show up, i made a back up in both internal and micro sd

prlatorre said:
i've tried what you suggested, and still nothing seems to show up, i made a back up in both internal and micro sd
Click to expand...
Click to collapse
So you created a backup of let's say the EFS partition in TWRP. You backed it up once to the internal SD card and once to the external sd card. Then you extracted the zip from step one, placed the folder inside of the backups folder and it does not appear?

how can i use this file if i i'm not rooted? My phone is being weird and i would like to reload the stock software on it.

truwrxtacy said:
how can i use this file if i i'm not rooted? My phone is being weird and i would like to reload the stock software on it.
Click to expand...
Click to collapse
You cant all you can do is factory reset on stock

jerrycoffman45 said:
You cant all you can do is factory reset on stock
Click to expand...
Click to collapse
Does the factory reset to stock also reset the recovery? Want to root phone but will most likely trade in to ATT once I'm eligible for upgrade(with trade in).

Manbot27 said:
Does the factory reset to stock also reset the recovery? Want to root phone but will most likely trade in to ATT once I'm eligible for upgrade(with trade in).
Click to expand...
Click to collapse
right now the root method for the h910 does not allow you to go back to stock

My 8gb sdcard ran out of space during step #8. Can I copy the contents of the sdcard to a bigger card and redo the full restoration from step 1?
---------- Post added at 01:27 PM ---------- Previous post was at 01:06 PM ----------
AlkaliV2 said:
So you created a backup of let's say the EFS partition in TWRP. You backed it up once to the internal SD card and once to the external sd card. Then you extracted the zip from step one, placed the folder inside of the backups folder and it does not appear?
Click to expand...
Click to collapse
Having the same issue. I copied the folder over to the microsd card and the folder I copied over isnt showing up in restore. I cant do anything or wipe anything if I cant see a backup right?
Im going to try and do the internal storage copy. No other choice.

cwis said:
My 8gb sdcard ran out of space during step #8. Can I copy the contents of the sdcard to a bigger card and redo the full restoration from step 1?
---------- Post added at 01:27 PM ---------- Previous post was at 01:06 PM ----------
Having the same issue. I copied the folder over to the microsd card and the folder I copied over isnt showing up in restore. I cant do anything or wipe anything if I cant see a backup right?
Im going to try and do the internal storage copy. No other choice.
Click to expand...
Click to collapse
If you create a backup of anything on the Microsd card before you attempt to put the folder in it, it will create the directories for you and all you have to do is copy and paste at that point.

Samsung Xcover 4 SM-G390F Root Magisk + TWRP +Disable Encryption Oreo/Pie (2019/2020)

Hi,
Finally I had time to finish my work on Xcover 4. I couldn't disable ForceEncryption by any flashable tool so I prepared 2 version of firmware (Oreo and Pie), both prerooted (Magisk) and free from Force Encryption. Everything except boot.img left untouched, both ROMs are BTU so no brand.
Just flash it with Odin 3.13.3. I recommend to flash CSC_BTU instead of HOME_CSC_BTU. HOME BTU should work as well but then probably You gonna have to format data with TWRP. CSC_BTU is already tested and there are no problems with Encryption.
After flashing just install Lastest Magisk Manager. SafetyNet Passed.
Oreo: G390FXXU4BSB3_BTU_G390FBTU4BSC1_Patched_By_Chamelleon
Code:
https://mega.nz/#!ONoFTIhD!rBOhDR0j874zpyeLiDVwfwOcodRi5OhdxyF0ZTRMslE
PIE: G390FXXU4CSF9_BTU_G390FBTU4CSFA_Patched_by_Chamelleon
Code:
https://mega.nz/#!XBhnRCCY!_IOOtXcLsGZQfVY17JD4YxxzaAWJqy2NoxVSrsJRs5M
If You need TWRP (not necessary to flash this ROMs) flash this version:
TWRP: TWRP-3.1.1_SM-G390F_by_nemo-nemo
Code:
https://mega.nz/#!DIo1SSBT!w4dPPAF3BEcfQmsy7mANO33Lb5Gj4jzDkrrPfbH56uo
Working on both versions, Oreo and Pie. I didn't test backup and recovery options but flashing is working on both. ADB and MTP are not working.
To remove Security Log Agent notifications use SecurityLogAgent Disable. It will disable this annoying app completely.

Hello!
Can you explain because i would like only to root my phone in oreo 8.1 without losing apps and data. Is it possible with your method?
thank you for your answer.

Would anyone happen to know if I can use TWRP for SM-G390F's on SM-G390W's? (the only differences I know of between them are the supported LTE frequencies)

You can try to flash it, just backup your data and if something goes wrong just flash it with back with stock firmware.

Updated main thread

Hi mates
very interesting matter. Will like to make it from a ubuntu 18.04 system? Did someone had tried it ?

Yea, it's a normal ROM so you can flash it with Heimdal.

Chamelleon said:
Yea, it's a normal ROM so you can flash it with Heimdal.
Click to expand...
Click to collapse
thank you C for this fast answer .
Here is the second point :
IS this rom free from google , I mean enough
And the third
any visible amelioration from the XCOV 2 Model in battery standing . I do not care about photos for my purpose .
Only memory, increased by SD, and lasting time

It's completely stock rom without any modifications except integrated Magisk and disabled force encryption. Rest is untouched.

I don't understand what file I should use to flash with Odin.. in the link you posted sends to a download of a zip file of almost 2gb in which there are many files, so from those files which one should I set in Odin?

Flash it like any other stock ROM:
BL file in BL
AP file in AP
CP file in CP
CSC_BTU file in CSC

Everything works great:]
Thanks man.

Hi Chamelleon and thanks for all the effort you've made already!
I successfully flashed the Pie variant of the two ROMs and got it to work. However, turned out that in an app that I'm developing, for some reason, when my device is equipped with G390FXXU4CSF9_BTU_G390FBTU4CSFA, the app doesn't behave in the same way as when G390FXXU4CSF9_ G390FXEO4CSFA has been installed. That's why I would like to be able to root the XEO-version of the firmware. Moreover, there will be many other non-rooted devices equipped with the XEO-version using the app in the near future.
Having flashed my device with G390FXXU4CSF9_ G390FXEO4CSFA, I tried installing the version of TWRP you have provided but I can't figure out how to install Magisk from there. By default, TWRP can't find the Magisk zip-file that I push onto the device. I tried formatting data, as per this post. The post lead me to believe that the files could be found after formatting but even though there were now plenty of TWRP-related folders, I couldn't find the zip. And as ADB and MTP don't seem to work in recovery mode, I'm unable to get the zip file on board after formatting. Booting to system doesn't work either after allowing modifications for TWRP, which might be due to dm-verity preventing boot, but franky I don't understand much of that topic.
You mentioned that you couldn't disable Force Encryption with any flashable tool. Is that the reason why TWRP (or any other tool) couldn't reach the zip file for Magisk?
This is the first time I've attempted rooting a phone so my knowledge regarding the topic is pretty basic.
So I suppose preparing a prerooted and Force Encryption free version of the firmware might be a possibility? I have no idea how to patch a ROM though. Any advice on how to proceed?

Hi, I had no time to play with this during Christmas. If you send me your boot.img I can modify it for you. If You just flash magisk with TWRP it will root your phone but after first reboot whole data partition will be encrypted again and you wont be able to flash anything with twrp or modify data partition without full wipe. For some unknown reason this and probably more Samsung models have different structure of files responsible for encryption and because of this none of pre-made patches are working. Only manual kernel modification can safe from encryption, at least for now.
I'm not a developer so I don't know how to prepare patch for this to allow anyone to flash it, I just found few lines of code in kernel You need to modify to disable encryption.

Chamelleon said:
Hi, I had no time to play with this during Christmas. If you send me your boot.img I can modify it for you. If You just flash magisk with TWRP it will root your phone but after first reboot whole data partition will be encrypted again and you wont be able to flash anything with twrp or modify data partition without full wipe. For some unknown reason this and probably more Samsung models have different structure of files responsible for encryption and because of this none of pre-made patches are working. Only manual kernel modification can safe from encryption, at least for now.
I'm not a developer so I don't know how to prepare patch for this to allow anyone to flash it, I just found few lines of code in kernel You need to modify to disable encryption.
Click to expand...
Click to collapse
Hi, I really appreciate the help!
I sent the boot.img to your paypal donation email. Let me know if you want me to send it to you some other way.

How to flash firmware on linux?
I know that i have to use heimdall but how to load these files into the program because filenames say basically nothing to me.
Thanks in advance.
Also does it delete user data?

SpurguX said:
Hi, I really appreciate the help!
I sent the boot.img to your paypal donation email. Let me know if you want me to send it to you some other way.
Click to expand...
Click to collapse
1. Flash clean ROM, same as boot you send me)
2. Enable OEM Unlock in Developer settings
3. Flash patched boot with Odin as AP/PDA.
4. Install Magisk Manager app
5. Install TWRP and format data partition, option where you need to type "YES"
6. Reboot system and then back to TWRP. If you can mount data and there are no errors it's done.
AndroidBroker said:
How to flash firmware on linux?
I know that i have to use heimdall but how to load these files into the program because filenames say basically nothing to me.
Thanks in advance.
Also does it delete user data?
Click to expand...
Click to collapse
Sorry but I never had a chance to use Heimdall. You can't dirty flash this because when your phone is encrypted and you can't replace kernel corrupting data.

But do I lose my data(Apps settings etc.)?
I'm OK with setting everything up back ,but it would be cool if it kept data.
(I'm going to use other computer that has windows on it btw, and I'm going to flash it with odin)

If your data partition is encrypted you gonna corrupt it by changing kernel. It means You wont be able to access, so yes, you will loose it.

What you mean by encryption some option in the Android or what?
If that's what you mean I haven't set up anything like this

How to root SM-J337P? Android 9

I have been searching the internet for days now and I haven't found a single way to root samsung SM-J337P Android 9 I hope to have some feedback on this site

Ive been looking to do the same for the last couple of months now & haven't had a bit of luck finding anythng or having any tried methods turn out successful

Root is fairly simple using Magisk pre patched method.
As for TWRP. Seems no one has bothered yet.
If there is a warrant for it I'll look into it, but I don't have as much enthusiasm nowadays as there seems to be a hit and run nature now on XDA.
I can't even get any feedback half the time.

ashyx said:
Root is fairly simple using Magisk pre patched method.
As for TWRP. Seems no one has bothered yet.
If there is a warrant for it I'll look into it, but I don't have as much enthusiasm nowadays as there seems to be a hit and run nature now on XDA.
I can't even get any feedback half the time.
Click to expand...
Click to collapse
tell me about it man. they even let me be a mod!! they must be hard up!! I had better button my lip, dont want any senior mods to think im attempting a mutiny LOLOLOL
it used to be back in the day that people would just accomplish stuff that the mfg said was impossible just to piss them off. Not because they wanted to do anything nefarious with the new found ability, just to poke a stick in their eyes! Man, i miss the OG Evo 4G days
@Androidhelper77 @poppas210 sorry, didnt mean to threadjack, but the root method is available, it just takes some reading of the threads to get there

Thank u

ashyx said:
Root is fairly simple using Magisk pre patched method.
Click to expand...
Click to collapse
This is probably obvious, but what do you mean by "pre patched method?"
EDIT: Nevermind, I figured out what you mean.

Ok, for anyone else who stumbles accross this thread, here's the steps:
Prerequisites:
- Samsung USB Drivers
- Patched Odin flashing tool. v. 1.13 or later. (Mine is v3.13.1_3B_PatcheD) (You might not need the patched one. It's just what I happened to use.) You do indeed need the patched one.
- Stock firmware img (To find version: Settings > About phone > Software version)
1. Activate developer mode.
- Settings > About Phone > Software Information
- Click "Build Number" repeatedly until it says "Congratulations! You are a developer!"
2. Enable USB Debugging and authorize computer.
- Settings > Developer Options > USB Debugging
3. Disable screen lock: Settings > Lock Screen > Screen lock type > None
4. Remove any Google or Samsung accounts: Settings > Accounts and backup > Accounts
5. Unlock boot loader WARNING: THIS WILL ERASE YOUR DEVICE
- Settings > Developer Options > OEM Unlocking
6. Copy the stock farmware img to your phone. You want the file that starts with "AP"
7. Install Magisk Manager by going to the magisk manager website on your phone and hitting "Download Magisk Manager" button and installing the app. The first time you open it, it will need to do additional setup and reboot your device.
8. Open Magisk Manager and select "Install" next to "Magisk." Click Install again, and then click "Select and Patch a File"
9. Select the firmware img you just copied to the phone.
10. Wait for process to complete. (Writing: system.img.lz4 takes a minute)
11. When Magisk Manager says "All done!" close it.
12. Copy the file called "magisk_patched.tar" from your phone to your computer. It should be found in your phone's internal memory "Download" folder.
13. Turn off the phone
14. Open Odin on PC
15. Boot phone into Odin mode: With the phone powered off, press and hold Vol-, Home, and Power until the blue warning screen appears, and then press Vol+ to enter Odin mode.
16. Your phone should appear in Odin on your PC
17. Click the AP button and select the "magisk_patched.tar" file.
18. Click "Start" and then DON'T TOUCH ANYTHING!
19. When the process is complete, a boc in Odin should say "PASS!" and be green. Your phone will reboot. (It will take longer than normal.)
20. Close Odin
21. Initial phone setup. Blah blah...
22. After initial setup, you may get a notification on your phone warning you of unauthorized changes. (Duh.) Just select it and hit cancel.
23. Install Magisk Manager on your phone again (repeat step 6)
24. After a reboot, open Magisk Manager again and it should say "Magisk is up to date."
You are done! Enjoy root access!

SlickStretch said:
Ok, for anyone else who stumbles accross this thread, here's the steps:
Prerequisites:
- Samsung USB Drivers
- Patched Odin flashing tool. v. 1.13 or later. (Mine is v3.13.1_3B_PatcheD) (You might not need the patched one. It's just what I happened to use.)
- Stock firmware img (To find version: Settings > About phone > Software version)
1. Activate developer mode.
- Settings > About Phone > Software Information
- Click "Build Number" repeatedly until it says "Congratulations! You are a developer!"
2. Enable USB Debugging and authorize computer.
- Settings > Developer Options > USB Debugging
3. Disable screen lock: Settings > Lock Screen > Screen lock type > None
4. Remove any Google or Samsung accounts: Settings > Accounts and backup > Accounts
5. Unlock boot loader WARNING: THIS WILL ERASE YOUR DEVICE
- Settings > Developer Options > OEM Unlocking
6. Copy the stock farmware img to your phone.
6. Install Magisk Manager by going to the magisk manager website on your phone and hitting "Download Magisk Manager" button and installing the app. The first time you open it, it will need to do additional setup and reboot your device.
7. Open Magisk Manager and select "Install" next to "Magisk." Click Install again, and then click "Select and Patch a File"
8. Select the firmware img you just copied to the phone.
9. Wait for process to complete. (Writing: system.img.lz4 takes a minute)
10. When Magisk Manager says "All done!" close it.
11. Copy the file called "magisk_patched.tar" from your phone to your computer. It should be found in your phone's internal memory "Download" folder.
12. Turn off the phone
13. Open Odin on PC
14. Boot phone into Odin mode: With the phone powered off, press and hold Vol-, Home, and Power until the blue warning screen appears, and then press Vol+ to enter Odin mode.
15. Your phone should appear in Odin on your PC
16. Click the AP button and select the "magisk_patched.tar" file.
17. Click "Start" and then DON'T TOUCH ANYTHING!
18. When the process is complete, a boc in Odin should say "PASS!" and be green. Your phone will reboot. (It will take longer than normal.)
15. Close Odin
19. Initial phone setup. Blah blah...
20. After initial setup, you may get a notification on your phone warning you of unauthorized changes. (Duh.) Just select it and hit cancel.
21. Install Magisk Manager on your phone again (repeat step 6)
22. After a reboot, open Magisk Manager again and it should say "Magisk is up to date."
You are done! Enjoy root access!
Click to expand...
Click to collapse
Bro I need your help,am stuck at stock farmware img,how do i get it because files come in 5 parts as my firmware?, how I get the boot img?,please help.

desmond462 said:
Bro I need your help,am stuck at stock farmware img,how do i get it because files come in 5 parts as my firmware?, how I get the boot img?,please help.
Click to expand...
Click to collapse
I'm getting ready to leave for work. I'll get back to you in when I get home. I know what you're talking about, but I'll have to look at the files to tell you which goes where.

SlickStretch said:
I'm getting ready to leave for work. I'll get back to you in when I get home. I know what you're talking about, but I'll have to look at the files to tell you which goes where.
Click to expand...
Click to collapse
OK bro, I truly appreciate the help. I await your help, am on pie just wondering if it could make a difference in it being able to root.

desmond462 said:
OK bro, I truly appreciate the help. I await your help, am on pie just wondering if it could make a difference in it being able to root.
Click to expand...
Click to collapse
You're going to want the file that starts with 'AP'. It should be the biggest one. (Mine is about 2.5 GB)

SlickStretch said:
You're going to want the file that starts with 'AP'. It should be the biggest one. (Mine is about 2.5 GB)
Click to expand...
Click to collapse
ok, wat i did was to change md5 to tar of AP, so it turn into zip then I extract boot.img from it, am i on the right path of doing this correctly?
then put in phone storage and open magisk manager to install and then select the boot img which start to flash and about few second it said it failed.

desmond462 said:
ok, wat i did was to change md5 to tar of AP, so it turn into zip then I extract boot.img from it, am i on the right path of doing this correctly?
Click to expand...
Click to collapse
No, I don't think you need to extract anything from it. Just remove the .md5 extension, and Magisk should be able to patch it.
For example, my file is named "AP_J337PVPS4BSI5_CL16191886_QB26045544_REV00_user_low_ship_meta_OS9.tar.md5" so I will remove the .md5 ext leaving me with "AP_J337PVPS4BSI5_CL16191886_QB26045544_REV00_user_low_ship_meta_OS9.tar" which is copied to the phone.

SlickStretch said:
No, I don't think you need to extract anything from it. Just remove the .md5 extension, and Magisk should be able to patch it.
For example, my file is named "AP_J337PVPS4BSI5_CL16191886_QB26045544_REV00_user_low_ship_meta_OS9.tar.md5" so I will remove the .md5 ext leaving me with "AP_J337PVPS4BSI5_CL16191886_QB26045544_REV00_user_low_ship_meta_OS9.tar" which is copied to the phone.
Click to expand...
Click to collapse
ok so u copy that file to phone storage then patch it using magisk?
---------- Post added at 06:57 AM ---------- Previous post was at 06:00 AM ----------
SlickStretch said:
No, I don't think you need to extract anything from it. Just remove the .md5 extension, and Magisk should be able to patch it.
For example, my file is named "AP_J337PVPS4BSI5_CL16191886_QB26045544_REV00_user_low_ship_meta_OS9.tar.md5" so I will remove the .md5 ext leaving me with "AP_J337PVPS4BSI5_CL16191886_QB26045544_REV00_user_low_ship_meta_OS9.tar" which is copied to the phone.
Click to expand...
Click to collapse
oh wow bro, thank you a thousand times over. am root now. Just that step about not extracting that you mention that i dont need to do made the difference in doing the right thing. truly appreciate your help. thank you again.

desmond462 said:
ok so u copy that file to phone storage then patch it using magisk?
---------- Post added at 06:57 AM ---------- Previous post was at 06:00 AM ----------
oh wow bro, thank you a thousand times over. am root now. Just that step about not extracting that you mention that i dont need to do made the difference in doing the right thing. truly appreciate your help. thank you again.
Click to expand...
Click to collapse
You're welcome! I'm glad it worked

SlickStretch said:
You're welcome! I'm glad it worked
Click to expand...
Click to collapse
Yea mon thanks again. So my reason to root is wanting to unlock my sim lock device, am outside US. But even after rooting it still not unlock using the software magic thunder which say it unlock it but still not seeing that it is unlock when I put in another sim, just showing invalid sim. so am stuck again. magic thunder was asking for root permission and not that its root am still unable to unlock it. Just wondering if you have any ideas or knowledge on this unlocking this device.

desmond462 said:
Yea mon thanks again. So my reason to root is wanting to unlock my sim lock device, am outside US. But even after rooting it still not unlock using the software magic thunder which say it unlock it but still not seeing that it is unlock when I put in another sim, just showing invalid sim. so am stuck again. magic thunder was asking for root permission and not that its root am still unable to unlock it. Just wondering if you have any ideas or knowledge on this unlocking this device.
Click to expand...
Click to collapse
It sounds like what you're looking for is a "carrier unlock," but I don't know anything about doing that. Good luck.

Been searching for J337P also...
Androidhelper77 said:
I have been searching the internet for days now and I haven't found a single way to root samsung SM-J337P Android 9 I hope to have some feedback on this site
Click to expand...
Click to collapse
The Best explanation / instructional video I've found so far is: h ttps://youtu.be/BOfv0F12gSI
But, TWRP does not have FW for j3topeltespr. And firmwar.mobi misidentified phone as galaxy j7 2016.
Two and a half days of reading and tubing and have better understanding but not much progress.
h ttps://youtu.be/nOGpFJnLP3A

Think I've found everything
poppas210 said:
Ive been looking to do the same for the last couple of months now & haven't had a bit of luck finding anythng or having any tried methods turn out successful
Click to expand...
Click to collapse
Think I've found everything
Instructions:
h ttps://rootmygalaxy.net/how-to-install-twrp-and-root-samsung-galaxy-j3-achieve/
The Release:
h ttps://github.com/TwrpBuilderTests/android_device_samsung_j3topeltespr/releases/tag/TWRP-3.2.3-TwrpBuilder-2018-10-28_03-45
Question:
Is this the version that causes the boot loop?

Motorola edge rootable?

I'm seeing so many different posts. Is it rootable or not? I wanna purchase the device but don't want to not be able to root it. Please let me know directly. I'm tmo btw

Got it already, on launch. It's fair, no real stutters at all, quick, but smooth(so don't mess with settings in developer options "drawing" section. There used to be a way, you could build, or "nominate", a twrp for your phone. I don't see that option anymore, just statistics. I'd like a twrp blog.

reggjoo said:
Got it already, on launch. It's fair, no real stutters at all, quick, but smooth(so don't mess with settings in developer options "drawing" section. There used to be a way, you could build, or "nominate", a twrp for your phone. I don't see that option anymore, just statistics. I'd like a twrp blog.
Click to expand...
Click to collapse
I am reading this comment AFTER I replied to your other on a different post and am realizing that your comment was NOT butchered and you DID indeed mean "builder". You can disregard the second half of my comment on that reply because it assumes you meant "build" and an actual "builder" which I had never even heard of. To that note, that actually would be great if there was still one around to utilize for this phone. A TWRP build is much needed to deal with the update problem I am having. The latest update in Lenovo Rescue does not provide the update since it is the same version number. The boot image can not be patched because they are actually different. I guess I can try my hand at capturing the download file if I only knew where it saved it.

There's an experimental build of TWRP for the Edge (NON +). I haven't tried it personally. Mine is BL unlocked and not rooted with Magisk patcher.

Yes the phone is rootable. I got mine a couple days ago - US retail model at BestBuy. Set the phone up, took the update...
Got: XT2063-2_RACER_RETUS_10_QPD30.114-80_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml from a thread here, made a tar archive with boot.img, ran the tar through Magisk, flashed it in fastbootd (I get there by booting the phone to recovery; in recovery hold power button for 3 seconds, keep holding it, hold vol up for 2 seconds, release vol up and there ya go. I 'enter fastboot', which shows fastbootd) - rebooted, opened magisk manager and it told me to continue setup - did. Root. Now, it's mine.
I don't undertand why TWRP is so important - I tried 3.4.0 beta9 on the moto g power last week, what a fuk'n mess. No way I was messing with twrp at all on the edge. AM I missing something? What do we even need twrp for anymore? Make a dump with adb, flash with it, do anything...

bronkish said:
Yes the phone is rootable. I got mine a couple days ago - US retail model at BestBuy. Set the phone up, took the update...
Got: XT2063-2_RACER_RETUS_10_QPD30.114-80_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml from a thread here, made a tar archive with boot.img, ran the tar through Magisk, flashed it in fastbootd (I get there by booting the phone to recovery; in recovery hold power button for 3 seconds, keep holding it, hold vol up for 2 seconds, release vol up and there ya go. I 'enter fastboot', which shows fastbootd) - rebooted, opened magisk manager and it told me to continue setup - did. Root. Now, it's mine.
I don't undertand why TWRP is so important - I tried 3.4.0 beta9 on the moto g power last week, what a fuk'n mess. No way I was messing with twrp at all on the edge. AM I missing something? What do we even need twrp for anymore? Make a dump with adb, flash with it, do anything...
Click to expand...
Click to collapse
Could you lay out the process in detail, or link us to an existing step by step with the correct download(s) that will work for the Edge? I'd really like to root but want to minimize my chance of creating a brick. Thanks!

If I remembered how I got to the firmware, I would have linked it, sorry - I do not. The filename is: XT2063-2_RACER_RETUS_10_QPD30.114-80_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip. No doubt I followed a thread here.
1 - obtain firmware, extract the archive, make a .tar archive of the boot.img file
2 - request bootloader unlock code from motorola (you must create an account)
3 - unlock bootloader
4 - install magisk manager
5 - in magisk, top section, install: patch file - feed it the boot.img.tar file you made. It will spit you out a new tar file
6 - in fastbootd, flash the patched boot.img file
you are rooted, unless you flashed in fastboot - you must flash the patched boot.img file in fastbootd

Hi,
could you please give the commands you used?
I have completed steps 1-5
I am not sure how to complete step 6
I have the magisk_patched_j5iak.tar file (there is a bot.img file in the archive)
Should I unpack the created magisk_patched_j5iak.tar file?
Please help

Umm, tell you what - try it both ways and then you'll know.
6: your phone is in fastbootd (I told you how to get there) and you flash the boot.img file that you just patched in magisk.

@bronkish Thanks again! I now have my beloved Titanium Backup again! It's been so long since I was rooted I'm going to have to see what else is available again.
[Edit]
Titanium looks a bit dated. Is there a better app now for doing what titanium did?

Rock ON!! SO many "I's" to follow....
I use to use Titanium (pro), too. Today I just export data from apps (settings, really) and I host a nextcloud server - which is handy as fuk (add a calendar event, or contact, on my phone, it's on my server, too, and vice-versa): I can 'share' dumps (exported nova settings, say) and data to nextcloud and if I take a picture 'in the field' it is immediately uploaded to my local nextcloud server and deleted (optional) from my phone. One can achieve all manner of function with nextcloud.
I restore and sync my calendar and contacts from nextcloud (dav), call log from sms backup & restore, which works great - although titamium, 3C, and others do the same.
I do keep handy an apk of every app I like to have installed on my phone, which, really isn't that many. I sometimes use app manager to export apks, or I use FX file manager. I use 3C to backup apps/data. I restore few apps/data with it. 3C can import titanium dumps, as well. I have less need for app/data dumps these days, though. DOn't care at all about twrp, but I'd be more inclined to use the twrp and full system dump restore methodology, as in the past, than using an app like titanium or 3c which requires setting up the phone again first, flashing or installing the app and then restoring apps/data - in this scenario a google account is required for some apps to function again (3c restore) or market links are broken as is handy to do in titanium. A restore from a twrp dump negates all this. You could also use adb for system level (phone) dumps/restore; it's fast and easy.
What do you need to backup? Why? Can you use app exports and a cloud or SD card or some connection to a server/desktop/drive? Can you employ dav? DO you even generate data worthy of backing up?
phone logs
firewall settings (as an example of app settings)
apps/apks in order to achieve function, if you even need to have them handy
texts (if you save them, I use signal and export a text dump to a folder on my sd card, if I even do, which is rare)
contacts, if you don't use google, or whatever
calendar
any important or usable generated data, apps likely have dump scenario
Like anything, there are myriad ways to accomplish the task.
If I'm gonna wipe or reset my phone I have common immediate dumps on my sd card (of course, the phone must have the slot). So, on my card is a folder with some app settings for a quick restore. AFWall settings are there. I have notification sounds and whatnot on the sd root so the phone picks them up. There's a contacts file and calendar file in the dump folder in case I'm near no network when restoring, which, would be odd. There's a couple text dumps, too. Hell, one is 2 years old - why do i keep it? lol.
Also on the card is a key file I use with keepassx as well as a keepass database dump, in case I need it - it's old but has what I need to 'start from scratch' if necessary. I typically just open the keepass dump from nextcloud I just reinstalled from the apk and bam, keepass opens on my phone with my thumb - fuk'n handy. The sd card dumps are just jump-starts if necessary, like, no networking, or something. But, they are there because they would be sorely missed if they were not.
I keep from setting up a google account on the phone for as ong as I can - everything restored, firewall tight, apps frozen, snuffed, or otherwise mitigated. I set the google account up to check fo app updates and for that pain in the ass poweramp which needs to hit the playstore every time it's reinstalled. Pfft. The sd maid and fx file manager apps are so much better to restore because no need for google to validate the purchase.
pffft.

bronkish said:
If I remembered how I got to the firmware, I would have linked it, sorry - I do not. The filename is: XT2063-2_RACER_RETUS_10_QPD30.114-80_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip. No doubt I followed a thread here.
1 - obtain firmware, extract the archive, make a .tar archive of the boot.img file
2 - request bootloader unlock code from motorola (you must create an account)
3 - unlock bootloader
4 - install magisk manager
5 - in magisk, top section, install: patch file - feed it the boot.img.tar file you made. It will spit you out a new tar file
6 - in fastbootd, flash the patched boot.img file
you are rooted, unless you flashed in fastboot - you must flash the patched boot.img file in fastbootd
Click to expand...
Click to collapse
After doing all of this I'm stuck on the Motorola boot screen. Is there any way to fix this?

bronkish said:
Yes the phone is rootable. I got mine a couple days ago - US retail model at BestBuy. Set the phone up, took the update...
Got: XT2063-2_RACER_RETUS_10_QPD30.114-80_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml from a thread here, made a tar archive with boot.img, ran the tar through Magisk, flashed it in fastbootd (I get there by booting the phone to recovery; in recovery hold power button for 3 seconds, keep holding it, hold vol up for 2 seconds, release vol up and there ya go. I 'enter fastboot', which shows fastbootd) - rebooted, opened magisk manager and it told me to continue setup - did. Root. Now, it's mine.
I don't undertand why TWRP is so important - I tried 3.4.0 beta9 on the moto g power last week, what a fuk'n mess. No way I was messing with twrp at all on the edge. AM I missing something? What do we even need twrp for anymore? Make a dump with adb, flash with it, do anything...
Click to expand...
Click to collapse
Question what update is that mine is the same XT2063-2 except mine reads QPDS30.114-80-2

Mine, too.

adbman said:
After doing all of this I'm stuck on the Motorola boot screen. Is there any way to fix this?
Click to expand...
Click to collapse
FastbootD
I gave instructions.

I don't mean to be a rude necromancer of posts but, I know nothing of these... tar files you speak of. I tried to do some homework and I see .tar.md5 and .tar.gz. Question 1: Does it make a difference? Is there a post somewhere I can learn from?
Question 2: How does one, or what software is available to, perform this work?
Respectfully,
Me

tar.md5 or, anything.md5 is just a text file containing the md5 hash of the file. You need or want it only if and when you do - if you don't know, then you don't. A .tar file is an archive like a .zip file. a tar.gz, or, .tgz is a compressed tar archive. tar only makes an envelope for the file(s), it doesn't compress unless you tell it to. There's lots of compression schemes - leave all that alone unless you wanna get back to it later. Magisk needs a .tar archive with the boot.img file in it - let's root
Rooting, with stock recovery, is just a couple simple steps. Magisk really makes it easy.
1 - get the firmware and extract it. You'll need the boot.img file.
2 - make an archive (*.tar) to contain the boot.img file. So, on linux, in a terminal, cd into the extracted firmware directory, do: tar -cvf boot-for-magisk.tar boot.img
windows user do your thing. I got a right-click, I don't even know anymore, check my command.
3 - drop that archive you just made onto your phone for magisk to use
4 - get and install magisk , the apk is fine
5 - open magisk. Top section, choose to install (touch the word: install), in next screen, choose select and patch file - feed it the tar achive you made of the extracted boot.img. point to the .tar file. do it.
Magisk will do its thing to the boot image and will spit out a new one that you can install to take advantage; to have root. Wicked. I copy it back to my computer for fastboot action. DO it - copy the new boot image that magisk generated to your computer.
6 - boot your phone to fastbootD - listen....plug your phone into your computer - usb-c cable.
reboot to recovery. In a terminal, do: fastboot devices <return> to check for your phone.
in recovery, press the power button for 3 seconds - at 3(onethousand), press the vol up button as well, for 2 more seconds
after you count 5, release the buttons and you should see a new menu - one of the items says to enter fastboot - that is fastbootD. If you attempt the power and vol up button task and it doesn't work, do it again - it works. SOmetimes it takes a time or 2 to catch it right. In any case, enter this fastboot. one onethousand...
FastbootD!
now, back in your terminal, flash the new boot image that magisk made for you. So: fastboot flash boot FILENAMEOFNEWBOOTIMAGE.img
following the successful flash, enter: fastboot reboot in your terminal - you may unplug your phone.
Success!

bronkish said:
If I remembered how I got to the firmware, I would have linked it, sorry - I do not. The filename is: XT2063-2_RACER_RETUS_10_QPD30.114-80_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip. No doubt I followed a thread here.
1 - obtain firmware, extract the archive, make a .tar archive of the boot.img file
2 - request bootloader unlock code from motorola (you must create an account)
3 - unlock bootloader
4 - install magisk manager
5 - in magisk, top section, install: patch file - feed it the boot.img.tar file you made. It will spit you out a new tar file
6 - in fastbootd, flash the patched boot.img file
you are rooted, unless you flashed in fastboot - you must flash the patched boot.img file in fastbootd
Click to expand...
Click to collapse
I remembered how you got to the firmware
Click this link thing down below the here.
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com

You'll be rooted in no time. Careful, now.

[2021 noob guide] Unlock and root (with working SafetyNet, Netflix & etc., Lock/Unlock in dev settings)

### Disclaimer ###
I am not responsible for damages of any kind. This will probably destroy your device without any warranty help or replacement.
If you follow this guide, your warranty will be lost forever.
Probably i described something wrong or it's not working for you.
### READ THIS ###
READ EVERYthing at least once before doing anything!
Current release of guide: 29/04/2021
Tested on:
Galaxy Tab S6 Lite (WiFi)
P610XXU2BTK2 (Nov2020, Android10, OneUI 2.5)
What's working: KG State, OEM Lock/Unlock in dev settings, SafetyNet, Netflix & etc. (NOT in HD with liboemcryptodisabler)
-> I have done this on latest the Android 10 (OneUI 2.5) because it seems the fastest OS for this tablet to me at this time of point. I don't know if this works the same way on Android 11.
Instructions
0. Make sure you have enough battery. Like 80%+
1. Create yourself an account on SamMobile https://www.sammobile.com/ and download your desired firmware for your country https://www.sammobile.com/samsung/galaxy-tab-s6-lite/firmware/SM-P610/DBT/#SM-P610
2. Extract firmware (WinRar is the fastest for that) and open the AP_[...] with WinRar or 7-Zip. Extract boot.img.lz4
3. Decode boot.img.lz4 with https://github.com/lz4/lz4/releases using lz4 boot.img.lz4 boot.img
4. Using 7-Zip add the boot.img to an tar archive and move it onto your tablet
5. Install Magisk APK from https://github.com/topjohnwu/Magisk/releases on your tablet, make sure there is no update available and press install. Choose the file patch and open the boot.tar (May need to enable show internal storage)
6. Move the patched boot.tar (named differently) onto your pc.
7. Make sure your downloaded firmware is the same as onto the device. If not flash it with https://odindownload.com/
- (Sync cloud apps and backup local data), turn off tablet, press Volume Up+Down and connect usb to pc while holding. When screen turns on the Download mode appears. Leave off the keys now and continue by pressing volume up
- Choose in Odin the following: BL: BL_[...], AP: AP_[...], dismiss CP, CSC: CSC_[...], Dismiss the Home_CSC_[...] from download
- Start and now wait until the tablet welcome screen appears. Skip it, we will reset it later again
8. Enable dev settings (tap 5 time onto build number for that), enable OEM-Unlock
9. Boot to download mode described above and unlock the Bootloader by following the instructions which show now up on the first screen in download mode (not the flash screen, before)
10. On welcome screen, skip setup because we will reset it later
11. Now we have to bypass KG State prenormal (or wait 7 days). Goto system update section, deactivate automatic download, then check for update. Your lasted checked date should be the current.
12. Then goto to general administration setting -> Date and Time -> Deactivate Auto time and timezone. Set the date manual to like 2 weeks earlier. Then check for updates again and the lasted checked date should be the current set manual.
13. Restart the device, activate auto time and timezone again and check for updates. The last checked data should be the current.
14. Boot to download mode flash screen like described earlier. The KG State should be checking (is for me), but not prenormal. If not then you have to wait 7 days for "natural" KG State reset i think but this never happened to me.
15. In Odin select in the AP section your patched tar created by Magisk from step 6, untick Auto reboot and F. Reset Time in options of Odin, then start
16. Once passed, turn off with Power + Volume Down for 7s, then after screen off unpress the keys and press Power + Volume Up immediately. This will boot recovery.
17. Wipe cache and data (factory reset) and reboot to system
18. Now you can setup the device properly. Download Magisk APK manual from https://github.com/topjohnwu/Magisk/releases, install it
19. Don't make the additional setup, cancel it. Make sure the manager has the latest version and no update is available. Then make the additional setup.
20. FOR BEAUTY ONLY (Optional): After the auto reboot, bypass KG State like above. We will now unblock the OEM-Unlock button in dev settings. For this we have to crash the tablet. Not force off, power off, ... but crash ;D Open Magisk, check for SafetyNet, Move home immediately and open PlayStore. Then open Magisk again and continue the cycle. When doing this fast, my tablet apps get unresponsive and after like 30-60s the Samsung logo appears. After the tablet is back there, my OEM unlock is always usable again. Probably there is a faster way to crash it ;D
21. Now we will fix SafetyNet and Netflix, etc.. Install https://github.com/kdrag0n/safetynet-fix Magisk module and liboemcryptodisabler from Magisk Modules. Then activate Magisk hide.
22. Now we will fix the PlayStore. Force close it, deactivate it and clean cache (I know data clean is not available)
23. Reboot your tablet. Then download PlayStore universal APK from https://www.apkmirror.com/apk/google-inc/google-play-store/#variants
24 Install the PlayStore APK. This will reactivate it. My device was certified at this point and Netflix was available on PlayStore and playing videos ;D
Note 1: Some flash process failed? Then you did very likely do something wrong. Try to make a clean flash. Fails too? Well this is bad. Probably resolvable by using another Odin version or some specific flash combination.
Note 2: I created a custom lcd calibration with Color Changer. Maybe interesting for more people ;D
The color seems for me less yellowish with white, more punchy but also less detailed. I prefer this look.
Note 3:
- Netflix is not available in HD. Stated that earlier already. It does work in HD with unlocked Bootloader but not with Magisk installed ;( Seems like the boot image is the problem here, which we cannot fix. Modded older Netflix APK's are not working either and removing Netflix system app makes the device unbootable the next boot. So if you want Netflix in HD then this is nothing for you at this time. Probably someone found a solution.
- However i did not try to use Netflix with the HiddenCore core method. I did also read in the other root guide for this device that people used MagiskHide Props. Maybe a kernel mod is required. Some research needs to be done here.
Note 4: Widevine L1 worked with unlocked bootloader and even stayed with root. However Netflix playback did not work after root... There exists a LuckyPatch for a version of Netflix newer than the one already installed in the firmware... I did not try but maybe this patch could also solve the problem
Hope my instructions are clearer then the bull**** flying around this forum for this device ;D;D

Hello , i have the s6 lite wifi with magisk on it... My problem is when I install a update every times I need to do a factory reset and start over again when I want to install the root ( the boot.img patched in Odin. ) For updating I download my complete firmware and install it with Odin... I have trying to patch the AP file from the firmware in magisk but never work when you want to install it, magisk do something wrong with this device I know this method work with the S21 and you can keep the data.. So who you can keep the data when you update the device with magisk??

I want to ask if colour changer drains battery or not bcz i use it too and i dont found any article on net about it pls tell if it drains battery or not (i am using custom with all colours on full) screen colours look like amoled

Max128 said:
Hello , i have the s6 lite wifi with magisk on it... My problem is when I install a update every times I need to do a factory reset and start over again when I want to install the root ( the boot.img patched in Odin. ) For updating I download my complete firmware and install it with Odin... I have trying to patch the AP file from the firmware in magisk but never work when you want to install it, magisk do something wrong with this device I know this method work with the S21 and you can keep the data.. So who you can keep the data when you update the device with magisk??
Click to expand...
Click to collapse
I've not tried that... but when using Odin there is a HOME_CSC and HOME image... The HOME_CSC does not reset the tablet. Also it is probably not necessary to wipe the tablet after the boot.img flash. On my phone this was not necessary but with this tablet users reported that otherwise it would boot loop. So i would try to update with Odin like that and reboot directly to download again, flash the updated boot.img and reboot.

Uniqueshiva said:
I want to ask if colour changer drains battery or not bcz i use it too and i dont found any article on net about it pls tell if it drains battery or not (i am using custom with all colours on full) screen colours look like amoled
Click to expand...
Click to collapse
Here is a quote from Color Changer: "This is NOT an overlay: it completely remaps your colors in all apps". I did not try for long because i needed Netflix in HD but i does not seem so. Tell us if you experience something like that if you try...

"1. Create yourself an account on SamMobile https://www.sammobile.com/ and download your desired firmware for your country https://www.sammobile.com/samsung/galaxy-tab-s6-lite/firmware/SM-P610/DBT/#SM-P610"
I can't. I have an Account and I can log in to that account. But when downloading the site tells me to "join". (Not Login or sth.) If I login and then click on "Edit Account", then it tells me to login first. If I login on that new site, then it tells me that my password (which I just succesfully used to login) is false. If I click reset password, then it tells me
"Invalid Redirect URL (https://www.google.com/)" If I try to "join" with new account, then it tells me that nickname and email are alreday taken.
If I register a new account with new nickname and new email, then I can't proceed either, the site will still tell me to join and if I click join, then it tells me that "Our records show that you have already registered under the name of andy02q. If you have lost your password, click here. If you would like to modify your profile, click here." I didn't even input "andy02q", it's just the account which I just created and confirmed.

andy01q said:
"1. Create yourself an account on SamMobile https://www.sammobile.com/ and download your desired firmware for your country https://www.sammobile.com/samsung/galaxy-tab-s6-lite/firmware/SM-P610/DBT/#SM-P610"
I can't. I have an Account and I can log in to that account. But when downloading the site tells me to "join". (Not Login or sth.) If I login and then click on "Edit Account", then it tells me to login first. If I login on that new site, then it tells me that my password (which I just succesfully used to login) is false. If I click reset password, then it tells me
"Invalid Redirect URL (https://www.google.com/)" If I try to "join" with new account, then it tells me that nickname and email are alreday taken.
If I register a new account with new nickname and new email, then I can't proceed either, the site will still tell me to join and if I click join, then it tells me that "Our records show that you have already registered under the name of andy02q. If you have lost your password, click here. If you would like to modify your profile, click here." I didn't even input "andy02q", it's just the account which I just created and confirmed.
Click to expand...
Click to collapse
You need to go to sammobile.com/login instead of just sammobile.com

I did go to sammobile.com/login. That's how I could login, how else? Although... now after trying the same thing again the login does carry over to https://www.sammobile.com/samsung/galaxy-tab-s6-lite/firmware/SM-P610/DBT/#SM-P610 and I can download the firmware from there, so thank you for the help. I guess Strg+F5 and closing and reopening the tab wasn't enough and I had to delete cookies or sth