Drm l1, I don't know.If you unlock bootloader to this and root it, do u lose the drm l1 so netflix hd?
+ do u void warranty and hit knox counter?
Knox and counter, country specific, herein the Netherlands warranty isn't void by law.
Drm l1, I don't know.If you unlock bootloader to this and root it, do u lose the drm l1 so netflix hd?
+ do u void warranty and hit knox counter?
You might want read this in advance to understand the procedure a bit better.
https://github.com/topjohnwu/Magisk/blob/master/docs/install.md
The other files in the docs folder also contain good info to read, better know to much than being sorry.
For me the @topjohnsw aka magisk worked better including that odin version, resulted in a no error flash.In Step 8 of the instructions for Samsung it reads:
"Flash magisk_patched.tar as AP in ODIN, together with the BL, CP and HOME_CSC files. Never flash only an AP file, as Odin can shrink your /data file-system if you do."
But PewPewK's instruction (#10) only mentions to flash AP. Should I only put the tar file in AP, and leave the BL, CP and CSC boxes untouched?
Can anyone please help me? @PewPewK
If you unlock bootloader to this and root it, do u lose the drm l1 so netflix hd?
+ do u void warranty and hit knox counter?
You want to flash patch or stock?
Try just AP to flash, no modem
Above is the post before.i want to flash the patch created by magisk when I load the AP in it.
https://github.com/topjohnwu/Magisk/blob/master/docs/install.md
in # 7 method for samsung, topjohnwu writes "Flash magisk_patched.tar as AP in ODIN, together with the BL, CP and HOME_CSC files. Never flash only an AP file, as Odin can shrink your /data file-system if you do." That is why i loaded BL AP and CSC files. I haven't gotten a chance to use the tablet but I feel as if pulling the patched tar file through adb might work. That is the only thing I didn't do exactly.
Following the post before yours worked for me perfectly, did That a few weeks before today (read all the md"s to be sure what I was doing)
For the life of me I can't get Odin 3.13.1 to recognize the device in download mode, not sure how to proceed. Different cables, different ports (2.0 and 3.0), different computers (Win 8.1, 10) I just keep getting Code 43 (Device Descriptor Request Failed).
Turns out all I had to do was just wait a few hours and it would magically start working... But now I have a new issue. Odin fails due to missing modem file since the Canadian version is wifi only and I'm scared to flash the AUS modem.
This is exactly how your 'magisk_patched.tar' should look.
Don't put anything else in there.
John Wu's instructions from here say you have to add files for BL, AP, CP and CSC right? Also my tar doesn't look like your screenshot. Did you manually remove the .lz4 files that were in it, and are flashing it by itself (so only AP checked in Odin)?
Any chance you can post it here? Or share via pm? I'd be really interested in root so I can do some debloat.
Because my installation process was hardly linear (I ran into many problems along the way), I can't guarantee that these are exclusively the exact steps you would need to take to get it working. But I think this should be a compilation of all the final (working-ish) steps I took.
(1) Setup tablet for first time, go to settings, enable developer mode, and flick the OEM Unlocking switch.
(2) Turn off the Tab S5e and boot into Download Mode by holding Power and Vol Up + Vol Down. Then hold up on the Vol Up button (not just a quick press) as it says to enter Bootloader Unlocking Mode. Follow the instructions there to fully unlock the bootloader.
(3) The tablet will be formatted at this step. After the bootloader is fully unlocked, make sure you boot back into the Tab S5e and perform the set up again. Enable developer options and make sure that the OEM Unlocking switch is turned on. Yes, again. This step is necessary apparently due to some changes Samsung made with their new VaultKeeper service? If you don't you may soft brick the device.
(4)Install @ianmacd's Magisk Manager application on your Tab S5e. Download is here.[Update: TopJonWu's official Magisk build should now work fine.]
(5) Download the latest Tab S5e firmware build. I found my copy here. Extract from it the AP file. Transfer this file to your Tab S5e.
(6) Back in Magisk Manager, go to settings and look for "Update Channel." Here's where I'm a little uncertain of what I did that finally got it to work, so I'll recommend two steps...
(7a)Select the ianmacd update channel and return to the home screen of Magisk. [Update: This shouldn't be necessary anymore, especially if you installed the official Magisk Manager earlier.] Click install, then choose the patch file option. Locate the AP file you transferred earlier and wait for it to finish creating a "magisk_patched.tar" file. Transfer this file to your computer and rename it "magisk_patched_ianmacd.tar," then delete the old magisk_patched on your device.
(7b) Do the same for the Canary (debug) update channel. Patch the AP again, and locate the patched file, copy it to your computer, and rename it to something clear.
(8) This is an odd step I had to follow to avoid errors flashing. It turns out of the several times I tried making the patched images, I almost always inevitably had some file in the archives getting corrupted. So open up both magisk_patched.tar's and test them for errors. I did this in 7-Zip, but there's probably ways to do it in WinRAR, too. If it gives you any error, take a note of which file it failed on because that guarantees your flashing will fail in later steps. In fact, the reason I recommended doing two different methods for patching magisk above was because the first ianmacd patch I tried had a corrupt recovery.img. What I ended up doing to fix it was extracting a working (non-error checking) recovery.img, vbmeta.img, and boot.img from the two different patched Magisks and then recombined them myself into my own Magisk tar. I also kept the meta-inf folder in there for good measure, though I don't think it's necessary? So in the end, I had what I called a "magisk_patched_lite.tar" that contained exactly three images: recovery.img, vbmeta.img, and boot.img, along with the meta-inf folder and ensured 7-Zip did not return any errors on the archive.
(9) Reboot the tablet to Download Mode. Press Vol Up to start. Attach the Tab S5e to your computer, and start Odin (I used v3.13.1_3B_PatcheD).
(10) Put some working archive of the patched magisk in the AP slot and uncheck "Auto Reboot." I don't know if the 'lite' version is sufficient for your first flash, but I suspect that it is (it would not be sufficient if you're pre-patching an updated firmware for the Tab S5e). Let Odin rip and see if you get any errors.
(11) Assuming Odin was successful, hold Power and Vol Down to exit Download Mode, then immediately switch to Power and Vol Up once the screen shuts off. Continue holding these until you are greeted with Recovery mode.
(12) Use the volume keys to select Factory Reset/Wipe Data. Execute that to make sure the tablet is properly formatted.
(13) Use the reboot into system option at the top of recovery. Hold Power and Vol Up until the "Bootloader is Unlocked" warning screen shows up, then release.
(14) If you're lucky, you should eventually see a red warning message about not having Samsung software installed. That's a good sign. My tablet fumbled around these steps and looked like it was gonna bootloop for a while? But eventually, it ran its course and booted.
(15) You hopefully have root installed now. Set up the tablet one last time, installthe ianmacdMagisk Manager again and open it up. If it says Magisk is installed, great job, otherwise... I don't know where the issue is because this rooting sequence is way more complicated than for other devices! At some point, I think after a reboot, Magisk Manager asked if it could do some additional setup stuff. Obviously let it do that.
@AHE_XDA, boss will you publish guide, with collected all knowledge and experiences?
Thanks