Database Users

Root for SM T237P 5.1.1 ???

As the title suggests, I am hoping someone can point toward the process of rooting this tab on stock 5.1.1 ota update. Every search turns up the process to root kitkat (which does pass Odin but did not root it.)but that didn't work on lollipop, and I can't seem to get TWRP to flash, for me at least. Is it KNOX stopping me maybe? I'm lost, Any help would be appreciated, I usually get by fine as long as I follow instructions.

sprint T237P WITH LOLLIPOP 5.1.1 (Need root)
.Sprint T237P 5.1.1 ota running philz recovery (Needs Root)
Hi , I had my device rooted and had philz touch 6.5 plus pure performance stock (which is another link in xda for the 4.4.2 root) on my tablet before I got the 5.1.1 upgrade on Sept 30 2015. I got the 5.1.1 upgrade the other day and I flashed philz touch recovery back onto my tablet it works perfectly and I installed pure performance on my tablet also with philz touch recovery runs good , now all I need is root for the 5.1.1 sprint T237P. Is anyone working on root for 5.1.1 for the t237p or can someone tell me anything all the hard work is appreciated. There is a link in XDA for philz touch recovery i don't know it offhand it is where i got mine... I wanted to add zip file of philz touch but don't see a way to add or attach file either...Anybody with information though on root for T237P 5.1.1 Please Post....Thanks
---------- Post added at 05:59 PM ---------- Previous post was at 05:56 PM ----------
Quote:
Originally Posted by DavidBeckett.db
Hi , I had my device rooted and had philz touch 6.5 plus pure performance stock (which is another link in xda for the 4.4.2 root) on my tablet before I got the 5.1.1 upgrade on Sept 30 2015. I got the 5.1.1 upgrade the other day and I flashed philz touch recovery back onto my tablet it works perfectly and I installed pure performance on my tablet also with philz touch recovery runs good , now all I need is root for the 5.1.1 sprint T237P. Is anyone working on root for 5.1.1 for the t237p or can someone tell me anything all the hard work is appreciated. There is a link in XDA for philz touch recovery i don't know it offhand it is where i got mine... I wanted to add zip file of philz touch but don't see a way to add or attach file either...Anybody with information though on root for T237P 5.1.1 Please Post....Thanks
SM-T237p Philz 6.59 [QCOM/MSM] Thanks @hookem2oo7 for testing.
https://www.androidfilehost.com/?fid=95916177934549969

jayare313 said:
As the title suggests, I am hoping someone can point toward the process of rooting this tab on stock 5.1.1 ota update.
Click to expand...
Click to collapse
DavidBeckett.db said:
Anybody with information though on root for T237P 5.1.1 Please Post....Thanks
Click to expand...
Click to collapse
Alright here's my two cents worth. Going off what I saw from the 8.0 models, because you've got lollipop 5.1.1 and not 5.0.x, you cannot just root by flashing Philz and then in Philz flashing the superSU zip like usual. There is something new in the security measures of the 5.1.1 kernel that causes a boot loop if you try this. I say this because the 10.1 models, which got 5.0.2, could root like I just described but the 8.0 models, which got 5.1.1, could not.
Therefore, it seems that someone will have to make a modified rootable kernel, in a similar manner to what moonbutt74 did for the 8.0 models. Check out his thread here to see what I mean

T237P on 5.1.1
Hi, I wrote yesterday that i flashed philz touch recovery and pure performance to my tab 4 T237P which they worked good...Well today I flashed KitKat 4.4.2 back to the T237P and then updated back to Lollipop 5.1.1 OTA I am just going to be patient until I find out if someone comes up with a Root for the device a new kernel or Whatever it will much so be worth the wait...Moonbutt74 did it before for the T237P for root on kitkat so either he or someone else will come up with a good method for root on T237P using 5.1.1 Thanks to all...

Try Kingroot?
I am glad that you confirmed that Philz recovery at least installs and you can flash back to stock 4.4.2! Have you tried King root? I was thinking about trying King root first then replacing their custom recovery with ours if needed. Then we hope that recovery works correctly...

@jayare313 @DavidBeckett.db @thisisapoorusernamechoice
hi guys, can one of you upload and post the LP 5.1.1 release's boot.img to a site i can access, and also provide a listing of
/system/lib/modules
and as well provide the block device number for boot/kernel for this device? Meaning /dev/block/mmcblk0p??
While the kernel's for the sm-t33x "s work because i have an sm-t330nu to test, I DO NOT have an sm-t237p BUTTCHEEKS, because it's qcom/msm the leap shouldn't be too far. I already have a test defconfig and build using my working source for the sm-t53x/33x. I am interested in seeing if the sm-t237p/230nt etc. can also be supported from that source.
m

I have the 237p running 5.1.1 id be willing to upload your request Moonbutt if i knew how, would love to root this device and get its full potential back in play any instructions
---------- Post added at 08:13 PM ---------- Previous post was at 08:10 PM ----------
moonbutt74 said:
@jayare313 @DavidBeckett.db @thisisapoorusernamechoice
hi guys, can one of you upload and post the LP 5.1.1 release's boot.img to a site i can access, and also provide a listing of
/system/lib/modules
and as well provide the block device number for boot/kernel for this device? Meaning /dev/block/mmcblk0p??
While the kernel's for the sm-t33x "s work because i have an sm-t330nu to test, I DO NOT have an sm-t237p BUTTCHEEKS, because it's qcom/msm the leap shouldn't be too far. I already have a test defconfig and build using my working source for the sm-t53x/33x. I am interested in seeing if the sm-t237p/230nt etc. can also be supported from that source.
m
Click to expand...
Click to collapse
Enlighten me so i may assist i have the 237 p on 5.1.1.

I pm'd him and he's moved on and I don't fault him for that. I also pm'd Kruser who rooted 442, just wish there was a simple guide. I don't have a ton of time to devote, but would gladly put up a bounty for it.
Bluheven14760 said:
I have the 237p running 5.1.1 id be willing to upload your request Moonbutt if i knew how, would love to root this device and get its full potential back in play any instructions
---------- Post added at 08:13 PM ---------- Previous post was at 08:10 PM ----------
Enlighten me so i may assist i have the 237 p on 5.1.1.
Click to expand...
Click to collapse

I too would love the 5.1.1 to be rooted. I need UVC video on the tablet via otg.

Kingroot and Supersu_me works... almost! Also captured 5.1.1 update.zip
I successfully rooted my SM-T237p with King root and then supersu_me. The only problem is once you reboot the device it goes into a boot loop mode. Check out the entire process... https://www.youtube.com/watch?v=d8fAA4uTwuc
I ODIN to stock 4.4.2 to fix it. I also captured the update.zip from the /data/fota folder for the 5.1.1 OTA but it is encrypted... I can upload it if it would be helpful. Any way to unzip it?

K94U said:
update.zip from the /data/fota folder for the 5.1.1 OTA but it is encrypted... I can upload it if it would be helpful. Any way to unzip it?
Click to expand...
Click to collapse
Upload the zip

Here is the download link... http://www.filedropper.com/sm-t237pota511
Let me know how else I can help. Is there anything I can do if I root 511 again? And pull some files?

Works but nothing sticks...
I'm currently rooted on 5.1.1 with a working Philz recovery nandroid backup. everything works great except nothing sticks. Recovery is over written immediately on boot and su makes the os boot loop if the device is restarted. To restore, I flash Philz recovery in ODIN then boot recovery and restore or do a new backup. I'll try to get Moonbutt74 the files and info soon. What is the easiest way to fix this?

moonbutt74 said:
hi guys, can one of you upload and post the LP 5.1.1 release's boot.img to a site i can access, and also provide a listing of
/system/lib/modules
and as well provide the block device number for boot/kernel for this device? Meaning /dev/block/mmcblk0p??
While the kernel's for the sm-t33x "s work because i have an sm-t330nu to test, I DO NOT have an sm-t237p BUTTCHEEKS, because it's qcom/msm the leap shouldn't be too far. I already have a test defconfig and build using my working source for the sm-t53x/33x. I am interested in seeing if the sm-t237p/230nt etc. can also be supported from that source.
m
Click to expand...
Click to collapse
Here are the files... How do I determine the block/device boot/kernel info? There are many mmcblk0p...
http://www.filedropper.com/sm-t237poh7
Update, I rebooted to try some other stuff and it actually restarted and kept su. Then I reinstalled recovery and it stuck! I think I might have used the root option in recovery and then apply the updated su 2.52

All working perfect!!!
So, it seems that I had to whip this device into permissive mode by working it from both ends, hahaha... the Kingroot and supersu me method makes it boot loop but then you need to install PhilZ recovery and install from that side also. The first thing to do is install PhilZ recovery and immediately reboot into recovery and do a nandroid backup! Make sure you have enough memory internal or sd... Full backup is 4+ gigs!!! Then experiment away... This DOES TRIP KNOX!... Here is a little video for you all. Experiment at your own risk!!
https://youtu.be/kzOYB7l5XLo
PhilZ recovery: http://forum.xda-developers.com/tab-4/development/recovery-philz-smnu-t2980094
SuperSU 2.52: http://download.chainfire.eu/743/SuperSU/BETA-SuperSU-v2.52.zip
Special update... It seems Chainfire has developed SuperSU 2.60 that has a special non-system mod root available!!! Anybody willing to install PhilZ on a stock OH7 and flash this new SU??? I think it might work... Just nandroid backup first! This is a special SU that MUST be installed on stock boot and kernel! Do NOT update your current SU with this version!
SuperSU 2.60: http://forum.xda-developers.com/attachment.php?attachmentid=3565977&d=1449330539

I restored my nandroid backup in recovery just to try this new Supersu on my sm-t237p lollipop and it worked the first time!!! All apps get root access OK except es file explorer(now bloatware anyway)... Su2.61 was just released. It works for mostly ALL Samsung and Nexus devices now... Read more:
http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
SuperSU 2.61 video: https://www.youtube.com/watch?v=03dBX7c2yiY

OK, just got my sm-t237p on 5.1.1, and philz recovery is loaded, @moonbutt74 are you still willing to help with root, i can upload partitions as needed... I'm here to help anyway i can...

fiddy619 said:
OK, just got my sm-t237p on 5.1.1, and philz recovery is loaded, @moonbutt74 are you still willing to help with root, i can upload partitions as needed... I'm here to help anyway i can...
Click to expand...
Click to collapse
f,
hi, this is what i need
reboot to recovery and connect via adb and run the following
adb shell
parted /dev/block/mmcblk0
print all
q
post that output.
and upload your current boot.img [lp 5.1]
in regular operation run in terminal
cat /proc/partitions
ls /system/lib/modules/
post that output
goto device setting about and post that screenshot, i need the build number for the rom/kerne/build id
There is currently no LL kernel source release for the sm-t237p and i will need to make a source request and that
is the information i require.
m

@moonbutt74 All requested has been uploaded, I had to compress the boot.img file using 7zip to allow to be uploaded due to 8MB limit, but just extract, and should be good... If you need anything else, just let me know...

A quick update, i can't get Philz recovery to stick, i have to re odin every time i want to get to recovery, I'm kinda new to odin, i've mainly been on htc, and lg devices, concepts all still the same just methods are a bit different to get to the same outcome. Is there a trick to get philz to stick, so i don't have to keep using odin?

[Root][5.1.1] Root with Stock Kernel

This thread contains a tutorial on how to patch boot.img on Samsung Lollipop devices and achieve root with a stock firmware. The tutorial is intended for those who wish to make their own boot.img for their specific firmware. For the rest, a patched boot.img for each device variant is attached. Simplified instructions for flashing with these patched images is first, followed by the tutorial.
NOTES!
1: YOU MUST EXTRACT THE .IMG FILE FROM THE TAR AND FLASH WITH TWRP. For some reason flashing with ODIN does NOT work with the images attached to this thread.
2: To make ODIN tars, look at @drExel's post here.
3: In most variants, TWRP 2.8.7.0 appears to work, though there are some issues. On some devices, it takes a REALLY long time to boot into TWRP, making you believe the device has frozen, but just give it time and it will load eventually. On other devices, TWRP loads, but touch does not work. In these cases, the S-Pen works without any problems (but is very sensitive). Some users have posted alternate TWRPs that work properly; search the thread for this. I am not including it here because I have not personally tried these versions myself.
4: Since this issue came up multiple times, though it is mentioned in the instructions below, I am stressing this once again. DO NOT ALLOW TWRP TO AUTOMATICALLY INSTALL SUPERSU WHEN YOU HIT REBOOT. THIS WILL CAUSE A BOOTLOOP, GUARANTEED! YOU MUST FLASH THE BETA 2.52 SUPERSU MANUALLY AFTER FLASHING THE PATCHED BOOT.IMG AND CONFIRMING THE DEVICE WORKS PROPERLY!
5: If you take the time to read the entire thread, you will find redirects to other kernels, firmwares and more. I am sure they are excellent, but having not used any of them, I cannot vouch for the outcomes if you flash them. All information related to the other firmwares and any questions you have about them are best served by going to their dedicated threads. This thread is ONLY for a pure stock firmware with only the boot.img patched to permit root, and nothing else touched.
6: XPosed Framework does not work yet for TW LL, but @wanam has an unofficial version here that various members have reported works quite well.
7: Knox WILL be tripped. If you care about Knox, leave now and do not come back!
Simplified Instructions
The thread originally began as a pure tutorial, with only the P607T image. But given the requests others had, and my need to confirm that this works on all variants, I made more patched images. No 'simple instructions' were available earlier because this was not intended for end-users who might flash and find that it does not work. Now that all the images are confirmed working, and we have tested on all variants, here is a simplified set of instructions for those who just wish to flash and do not care what they are flashing.
1: Update to fully stock 5.1.1 for your device. Whether it is OTA or ODIN flash using a firmware from sammobile or elsewhere does not matter. You start with a fully stock device running 5.1.1.
2: Download the appropriate patched_boot.img for your device. They are attached as tar files due to XDA size restrictions, so you must untar and then save the .img file to your device. Also download SuperSU Beta 2.52.zip and save it as is to the same folder on your device where you put the .img file.
3: Download TWRP 2.8.7.0 for your device and flash it with ODIN. To get TWRP to stick, when the device reboots, you must go directly into recovery. If the device reboots normally, TWRP will be replaced by the stock recovery. There are guides on how to flash TWRP and you should go look at them if you are unsure how to do this.
4: Once you are in TWRP, go the Install area. The default is for installing .zip files. At the bottom right of the screen, you will see a button to change to Images. Hit this. Then select the patched_boot.img file that you saved on your device in the previous step. When you hit install, TWRP will ask you whether this is a boot image or a recovery image. Select Boot. Let TWRP do its thing. When done, go back and hit reboot. TWRP will volunteer to install SuperSU for you now. SAY NO TO THIS. If you accept this install, your device will bootloop and you have start all over again!
5: Make sure the device rebooted without any problems. You will see a red "Kernel SEAndroid Not Enforcing" message when you reboot. Ignore it, it just means that the patched boot.img is working. Once you have confirmed that the device is able to boot properly with the patched boot.img, reboot into recovery again. Go back to Install, this time, stick with Zip mode and install the Beta SuperSU 2.52.zip that you saved to your device. Reboot.
6: If you followed instructions properly, you will reboot without any problems. Run SuperSU, allow it to update if it wants to, and to disable knox if you want to. You have a rooted device now with a virgin firmware.
7: This process has worked for enough people now that any errors are user errors. If you are bootlooping after following these instructions to the letter, you should do a full factory reset and try from scratch. A previous incorrect flash of SuperSU that caused a bootloop seems to persist even if you reflash the stock firmware and messes things up. Always perform a clean install!
Tutorial to patch your own boot.img
This section is NOT meant for the non-technical end-user who "... just wants root ... "
So far, it seems the only way to get root on the 5.1.1 Firmware was to flash a permissive kernel that disabled SEAndroid completely. This is a bit like killing the patient to cure the disease. @Chainfire describes a 'trick' to get root with a fully stock kernel on this thread. Special Thanks to @garyd9 and @SHM for helping me get everything working properly.
Part 1:
1) Extract boot.img from your device's stock firmware.
2) Unpack the boot.img to get access to the ramdisk.
3) Copy the sepolicy file from the ramdisk. You will be patching this file to make the usual SuperSU method work again.
The stock image can be extracted from the firmware using any archive tool. To unpack the boot.img, you can take a look at the following threads for tools and instructions.
Carliv's Kitchen : Windows, very beginner friendly.
SHM's Toolset : I used this on Linux.
copy sepolicy from the ramdisk folder to your adb folder (If you are on Windows and using Minimal ADB and Fastboot; I am assuming linux users don't need to be told what to do here )
Part 2:
1) Connect an already rooted device running 4.4+ firmware & SuperSU Beta 2.50+ to your system. Make sure you have adb access.
2) Push the sepolicy file to the device.
3) Run supolicy on the sepolicy file to patch it.
4) Pull the sepolicy file back to your computer.
I used my rooted Note 2 to get the job done. ANY rooted device that permits adb should do the trick, but it needs to be on 4.4+ firmware and running SuperSU Beta 2.50+.
Once you have an adb connection established, do the following (this is from Chainfire's thread referenced at the beginning):
Code:
adb push sepolicy /data/local/tmp/sepolicy
adb shell su -c "supolicy --file /data/local/tmp/sepolicy /data/local/tmp/sepolicy_out"
adb shell su -c "chmod 0644 /data/local/tmp/sepolicy_out"
adb pull /data/local/tmp/sepolicy_out sepolicy_out
Part 3:
1) Replace the sepolicy file in the stock ramdisk with the newly patched sepolicy file.
2) Repack the ramdisk.
3) Make a new boot.img with the stock kernel and repacked ramdisk.
4) Flash new boot.img on your Note 10.1. Reboot, make sure everything is working.
Replace the sepolicy in the ramdisk with the sepolicy_out file that you pulled from your reference device. This means RENAME sepolicy_out and overwrite the original sepolicy file.
Repack the ramdisk using the instructions that came with your tool.
Make a new patchedboot.img file using the instructions that came with your tool.
Copy this patchedboot.img file to your Note 10.1, reboot into TWRP, go to the install zip section, toggle image mode, flash the patchedboot.img file and reboot the device. DECLINE TWRP's friendly offer to install SuperSU for you. This will cause a bootloop!If the device reboots successfully, pat yourself on the back. At this point, all you have done is patched the sepolicy to allow rooting, but you have not yet rooted the device.
Part 4:
1) Use TWRP to install SuperSU Beta 2.50+ (I used 2.52)
2) Reboot
Copy SuperSU Beta 2.50+ (I used 2.52) to the device, reboot into TWRP and install SuperSU. Reboot for rooted Note 10.1 running a Stock Kernel and no compromised SEAndroid. Of course, it goes without saying, this will trip knox. Also, please note that XPosed is not out for 5.1.1 yet, at least not officially. @wanam has an unofficial version here that various members have reported works well.

Hey, So at what step in this do I start if I dl'ed the Patched boot img? Thanks in advance.

icemanscion said:
Hey, So at what step in this do I start if I dl'ed the Patched boot img? Thanks in advance.
Click to expand...
Click to collapse
Part 3, Step 4:
Flash new boot.img on your Note 10.1. Reboot, make sure everything is working.
Copy this patchedboot.img file to your Note 10.1, reboot into TWRP, go to the install zip section, toggle image mode, flash the patchedboot.img file and reboot the device. If the device reboots successfully, pat yourself on the back. At this point, all you have done is patched the sepolicy to allow rooting, but you have not yet rooted the device.
Click to expand...
Click to collapse
In TWRP, when you hit Install, on the bottom right, you will see an option for Images. Select that and when you goto the folder with your img, you should see the new img you copied on to your device. Continue with Part 4 for full root.
IF the device does not boot, you want to flash the stock boot.img again, so make sure you have a copy of that on your device as well, so you can recover easily!

karthikrr said:
Part 3, Step 4:
In TWRP, when you hit Install, on the bottom right, you will see an option for Images. Select that and when you goto the folder with your img, you should see the new img you copied on to your device. Continue with Part 4 for full root.
IF the device does not boot, you want to flash the stock boot.img again, so make sure you have a copy of that on your device as well, so you can recover easily!
Click to expand...
Click to collapse
I have issues with TWRP since it wont work properly for me, so I'm going to try it with Philz CWM. Thank you again.

icemanscion said:
I have issues with TWRP since it wont work properly for me, so I'm going to try it with Philz CWM. Thank you again.
Click to expand...
Click to collapse
Good luck Just make sure you have the stock boot.img around, in case there are any problems. You are the first one trying it on the P600, or at least the first who cared to write in this thread, so this is uncharted territory!

So to get the patches boot.img, we unpack the tar file posted in the OP?
Sent from my SM-P600 using Tapatalk

iridaki said:
So to get the patches boot.img, we unpack the tar file posted in the OP?
Sent from my SM-P600 using Tapatalk
Click to expand...
Click to collapse
Yes. xda does not allow me to post an image file greater than 8mb, but the P607T image is 10.5mb, so had to tar it. Decided to be consistent with all the images.
Technically, you can try to flash that .tar with ODIN, but in my case, it would not work. Only flashing the .img through TWRP did.

karthikrr said:
Yes. xda does not allow me to post an image file greater than 8mb, but the P607T image is 10.5mb, so had to tar it. Decided to be consistent with all the images.
Technically, you can try to flash that .tar with ODIN, but in my case, it would not work. Only flashing the .img through TWRP did.
Click to expand...
Click to collapse
Thank you! And thank you for providing us with a patched kernel!
I'll try rooting and installing Xposed tonight and report back!

iridaki said:
Thank you! And thank you for providing us with a patched kernel!
I'll try rooting and installing Xposed tonight and report back!
Click to expand...
Click to collapse
Technically its just a patched boot image with a STOCK kernel, but yea, glad to help The real work was done by Chainfire and garyd9 and SHM helped me put this thing together, so they deserve the thanks!
If you get Xposed on it, let me know which version. The official one does not work on TW LL yet, but I believe Wanam has another version out that does. I haven't had the time to install it and test it, so your review will be helpful.

karthikrr said:
Technically its just a patched boot image with a STOCK kernel, but yea, glad to help The real work was done by Chainfire and garyd9 and SHM helped me put this thing together, so they deserve the thanks!
If you get Xposed on it, let me know which version. The official one does not work on TW LL yet, but I believe Wanam has another version out that does. I haven't had the time to install it and test it, so your review will be helpful.
Click to expand...
Click to collapse
Any contribution is a worthy contribution!
Wanam Xposed works perfectly on my Note 4 and I think it will work on the 10.1 as well. I'll report back soon!

SM-P600-TWRP 2.8.7.0 touch input doesn't work, but stylus input does
Hi!
Thanks for your posts, I'm sifting through is now. I was reflashing TWRP 2.8.7.0 (for SM-P600) and discovered that it wasnt responding to touch input. But I quickly discovered that it's UI does respond to the s-pen
I'll share my rooting experience as soon as possible.
V

Hey !! Can you give me the ROM of Darkdroid for Micromax A177. Thanks

Vasishtha said:
Hi!
Thanks for your posts, I'm sifting through is now. I was reflashing TWRP 2.8.7.0 (for SM-P600) and discovered that it wasnt responding to touch input. But I quickly discovered that it's UI does respond to the s-pen
I'll share my rooting experience as soon as possible.
V
Click to expand...
Click to collapse
How do you make it? I cannot flash the twrp successfully, there is always an error saying ''Recovery is not SEAndroid Enforcing''.

iopxiang said:
How do you make it? I cannot flash the twrp successfully, there is always an error saying ''Recovery is not SEAndroid Enforcing''.
Click to expand...
Click to collapse
You should wait a few moments. TWRP will open.
Flashing the SU.zip ends up in Bootloop for me._.

Fabi7775 said:
You should wait a few moments. TWRP will open.
Flashing the SU.zip ends up in Bootloop for me._.
Click to expand...
Click to collapse
Did you flash the boot.img before flash SU?

iopxiang said:
Did you flash the boot.img before flash SU?
Click to expand...
Click to collapse
Actually not, sorry.
I just thougt it is worth a try.

The SM-P600 rooting(with your patched boot) was a success! I encountered no problems at all. Only the lack of touch responsiveness of twrp 2.8.x had me worried, but thankfully the s-pen had my back and I was able to browse the twrp UI with it.
I'm now restoring all my apps with titanium backup, I'll try out xposed later this afternoon.
Regarding the LL update: wow this tablet completely feels like a new device, the fluidity is just stunning. 60 fps animations

Vasishtha said:
The SM-P600 rooting(with your patched boot) was a success! I encountered no problems at all. Only the lack of touch responsiveness of twrp 2.8.x had me worried, but thankfully the s-pen had my back and I was able to browse the twrp UI with it.
I'm now restoring all my apps with titanium backup, I'll try out xposed later this afternoon.
Regarding the LL update: wow this tablet completely feels like a new device, the fluidity is just stunning. 60 fps animations
Click to expand...
Click to collapse
Finally, a confirmation Thanks for letting us know!
As for TWRP, I believe the 2.6.3.3 (or something else in the 2.6 series) works without any problems on the P600.
XPosed is officially not out for Samsung LL, BUT Wanam has a version in development that works well, according to @iridaki on this thread. If you switch TWRP or try Wanam Xposed, post an update here as well!
And yes, the LL update actually made the device feel so damn good, its practically a Note 10.1 (2015 Edition)!

karthikrr said:
Finally, a confirmation Thanks for letting us know!
As for TWRP, I believe the 2.6.3.3 (or something else in the 2.6 series) works without any problems on the P600.
XPosed is officially not out for Samsung LL, BUT Wanam has a version in development that works well, according to @iridaki on this thread. If you switch TWRP or try Wanam Xposed, post an update here as well!
And yes, the LL update actually made the device feel so damn good, its practically a Note 10.1 (2015 Edition)!
Click to expand...
Click to collapse
Twrp 2.6.x does work, however there is no option to flash .img files on those versions.
So you either have to use heimdall or something else in order to flash that boot.
The unofficial xposed 5.1.x on my nexus 5 worked without any problems, so I expect the same for the LL variant. But I'll keep you posted.
The multiwindow transitions now have fade in/out effects <3 and we now can snap floating windows to either the left or right sides D:

karthikrr said:
Update 3: The patched P600 image has been confirmed to work by @Vasishtha, who also says TWRP 2.8.7.0 works with the S-Pen, but no touch input.
Click to expand...
Click to collapse
Can we use Temasek's 2.8.7.0 TWRP that has touch working?

SM-T590 root/custom recovery?

So i got today the "Samsung Galaxy Tab A 10.5 (gta2xlwifi /SM-T590) with Android 8.1, the first Question i had "Can i root the Tablet?".
Well this is now my Question, i used google for a Hour and the Search function in XDA but apperently i cant find smth about this Device + root/custom recovery, i just found a news article with rumors about the Bixby Button.
so i wanted to ask if someone know already smth about rooting this device or give me some advises where i should begin with workarounds or smth like that.

Hi,
As far as I know there is no custom recovery for the SM-T590 yet. You're best bet to root the device is most likely to use Magisk and create a patched boot.img with Magisk Manager. The following steps should do the trick, but no guarantees as I have not tested it with this device:
Download the firmware matching your device firmware version
Unlock your bootloader (this will also trigger the KNOX fuse, so apps like Samsung Pay will no longer work)
Install Magisk Manager
In the settings of Magisk Manager, set the boot image format to img.tar
Unpack the lz4 compressed image
Install Magisk and select the Patch boot image method
Flash the patched boot image with ODIN/Heimdall
Cheers, Tom

tomparr said:
Hi,
As far as I know there is no custom recovery for the SM-T590 yet. You're best bet to root the device is most likely to use Magisk and create a patched boot.img with Magisk Manager. The following steps should do the trick, but no guarantees as I have not tested it with this device:
Download the firmware matching your device firmware version
Unlock your bootloader (this will also trigger the KNOX fuse, so apps like Samsung Pay will no longer work)
Install Magisk Manager
In the settings of Magisk Manager, set the boot image format to img.tar
Install Magisk and select the Patch boot image method
If sucessful, flash the patched boot image with ODIN/Heimdall
Cheers, Tom
Click to expand...
Click to collapse
(That English sounds kinda bad not gonna lie xd im really sorry for this crappy text tried my best)
first of all thanks for your time
so..... i did not found any infos about unlocking bootloader for this tablet... probably i dont search the right terms...
Well i tried it without unlocking it (idk if its maybe already unlocked)
now i created the boot image, install it via odin now yeah...
ive got magisk now and "root" but root do not actually work (apps like titaniumbackup cant find the "su") (probably because the bootloader isnt unlocked?)
so maybe its because of the bootloader not unlocked, just not working because of this "workaround", so i basically just can wait till someone take her/his time with this device or i did something wrong and didnt do it right

tomparr said:
Hi,
As far as I know there is no custom recovery for the SM-T590 yet. You're best bet to root the device is most likely to use Magisk and create a patched boot.img with Magisk Manager. The following steps should do the trick, but no guarantees as I have not tested it with this device:
Download the firmware matching your device firmware version
Unlock your bootloader (this will also trigger the KNOX fuse, so apps like Samsung Pay will no longer work)
Install Magisk Manager
In the settings of Magisk Manager, set the boot image format to img.tar
Install Magisk and select the Patch boot image method
If sucessful, flash the patched boot image with ODIN/Heimdall
Cheers, Tom
Click to expand...
Click to collapse
Edit: I tried this and the boot.img won't patch, comes back saying it can't patch the stock kernel.

airmaxx23 said:
Edit: I tried this and the boot.img won't patch, comes back saying it can't patch the stock kernel.
Click to expand...
Click to collapse
Hi,
Could you upload the boot.img(.lz4) somewhere? My device should arrive any day now, so I am really interested to get it working.
-- Tom

tomparr said:
Hi,
Could you upload the boot.img(.lz4) somewhere? My device should arrive any day now, so I am really interested to get it working.
-- Tom
Click to expand...
Click to collapse
Here you go, please keep me updated on your progress and let me know if I can help. This is from the December update.
https://drive.google.com/file/d/1hlntpS7hj6zsfuBW6JbPvJoCOEVSDG3i/view?usp=drivesdk

airmaxx23 said:
Here you go, please keep me updated on your progress and let me know if I can help. This is from the December update.
https://drive.google.com/file/d/1hlntpS7hj6zsfuBW6JbPvJoCOEVSDG3i/view?usp=drivesdk
Click to expand...
Click to collapse
Thank you. I ran the above steps (after decompressing the image with lz4) and the patching process went through without any issues. You can find the recompressed image here. No warranty it will work though since I don't have access to the device (yet) but please let me know if it works.

tomparr said:
Thank you. I ran the above steps (after decompressing the image with lz4) and the patching process went through without any issues. You can find the recompressed image here. No warranty it will work though since I don't have access to the device (yet) but please let me know if it works.
Click to expand...
Click to collapse
It's my first time messing with Samsung firmware in a long time so I've pretty much forgotten everything, I've also never messed with the lz4 extension before. How did you go about extracting the boot.img?
I'll probably wait until you try it since you're obviously more experienced with Samsung firmware. Please keep me posted.

airmaxx23 said:
It's my first time messing with Samsung firmware in a long time so I've pretty much forgotten everything, I've also never messed with the lz4 extension before. How did you go about extracting the boot.img?
I'll probably wait until you try it since you're obviously more experienced with Samsung firmware. Please keep me posted.
Click to expand...
Click to collapse
My last Samsung device was a Galaxy S2, so it has been a long time for me too. For now I just did a bit of reading about the new formats. The lz4 compression also seems to be relatively new and replace the old img.tar format. You can simply extract the boot.img from the boot.img.lz4 by using the official lz4 binary with the command
Code:
lz4.exe boot.img.lz4
After Magisk patched the image you can repack it by using
Code:
lz4.exe -B6 --content-size patched_boot.img patched_boot.img.lz4
The new image should be flashable with Odin/Heimdall.

tomparr said:
My last Samsung device was a Galaxy S2, so it has been a long time for me too. For now I just did a bit of reading about the new formats. The lz4 compression also seems to be relatively new and replace the old img.tar format. You can simply extract the boot.img from the boot.img.lz4 by using the official lz4 binary with the command
Code:
lz4.exe boot.img.lz4
After Magisk patched the image you can repack it by using
Code:
lz4.exe -B6 --content-size patched_boot.img patched_boot.img.lz4
The new image should be flashable with Odin/Heimdall.
Click to expand...
Click to collapse
Would I use the AP slot in Odin? If I have issues I'd just flash the stock boot.img.lz4?

airmaxx23 said:
Would I use the AP slot in Odin? If I have issues I'd just flash the stock boot.img.lz4?
Click to expand...
Click to collapse
Yes and yes

tomparr said:
Yes and yes
Click to expand...
Click to collapse
There's only one problem, the file you patched needs to have a .tar or .md5 extension for Odin, it won't accept an .lz4 extension. When you patched it with Magisk did you select .tar format?

From what I've read, you need at least Odin 3.13.1 to flash a lz4 image.

tomparr said:
From what I've read, you need at least Odin 3.13.1 to flash a lz4 image.
Click to expand...
Click to collapse
I have Odin 3.13.1 and there's no option or way to flash an LZ4 image.

airmaxx23 said:
I have Odin 3.13.1 and there's no option or way to flash an LZ4 image.
Click to expand...
Click to collapse
My bad, I've been away too long from Samsung firmwares. Please try this patched boot image. I've recreated it as an img.tar file.

tomparr said:
My bad, I've been away too long from Samsung firmwares. Please try this patched boot image. I've recreated it as an img.tar file.
Click to expand...
Click to collapse
That worked, we have root. A couple things are acting strange but it may be a Samsung thing. Adaway won't stay enabled after a reboot, when trying to edit the build.prop with Root Explorer the tablet reboots when I hit "save". Root Explorer won't delete anything in system/app or system/priv-app.
I have Magisk installed, V4A, Substratum and OnePlus Gestures.
Could you do me one favor and repackage the stock boot.img.lz4 with a .tar extension so I have it. Or explain to me the steps to do it.

airmaxx23 said:
That worked, we have root. A couple things are acting strange but it may be a Samsung thing. Adaway won't stay enabled after a reboot, when trying to edit the build.prop with Root Explorer the tablet reboots when I hit "save". Root Explorer won't delete anything in system/app or system/priv-app.
I have Magisk installed, V4A, Substratum and OnePlus Gestures.
Could you do me one favor and repackage the stock boot.img.lz4 with a .tar extension so I have it. Or explain to me the steps to do it.
Click to expand...
Click to collapse
Glad to hear it worked, at least to some extend.
I've created a flashable tar from your initial boot image, which you can find here. If you want to try it yourself, here's what I did:
Decompress lz4 image: 'lz4 -d boot.img.lz4'
Create tar archive: ' tar --create --format=gnu -b20 --quoting-style=escape --owner=0 --group=0 --totals --mode=644 -f boot.img.tar boot.img'

tomparr said:
Hi,
As far as I know there is no custom recovery for the SM-T590 yet. You're best bet to root the device is most likely to use Magisk and create a patched boot.img with Magisk Manager. The following steps should do the trick, but no guarantees as I have not tested it with this device:
Download the firmware matching your device firmware version
Unlock your bootloader (this will also trigger the KNOX fuse, so apps like Samsung Pay will no longer work)
Install Magisk Manager
In the settings of Magisk Manager, set the boot image format to img.tar
Unpack the lz4 compressed image
Install Magisk and select the Patch boot image method
Flash the patched boot image with ODIN/Heimdall
Cheers, Tom
Click to expand...
Click to collapse
Thanks for that, worked for me after some glitches. Now rooted with xposed working.

gscollier said:
Thanks for that, worked for me after some glitches. Now rooted with xposed working.
Click to expand...
Click to collapse
Which SDK version did you install?
Also, can you please do me a favor? Go into system/app or system/priv-app and try to rename an apk and see what happens.

So you guys are making some progress. Its been a while for me too. I used to develop ROMs here ages ago but I am so out of the loop. Can't find any repos either. The last time I used Odin (and hated it) was back in the skyrocket days. Is it absolutely mandatory? Would adb work in Linux?
I always tried to avoid magisk or just didn't need it. Is it possible to avoid a recovery with it?

(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

Downgrade Galaxy s10+ Binary 15 android 12 to android 11

Hi guys,
Sorry if it is a silly question but I have been trying to get the information with no results.
I have a Samsung galaxy s10+ SM G975F... It is binary 15 and when I use Odin, I can get a newer binary than 14... I want to downgrade from Android 12 to 11... The Batery drain is insane now...
Odin always said that the Binary is incorrect and can't flash any diferent rom
Any ideas or suggestions? Can I install a custom Rom at least?
Thanks and I hope you can help me.

Downgrading Samsung phones is pretty much impossible without unlocking bootloader some funky playing around (manually flashing system, boot, and probably way more) and a TON of luck. I could help you better with an older android Version as i dont have much experience with android 9 or newer.

Arash2803 said:
Hi guys,
Sorry if it is a silly question but I have been trying to get the information with no results.
I have a Samsung galaxy s10+ SM G975F... It is binary 15 and when I use Odin, I can get a newer binary than 14... I want to downgrade from Android 12 to 11... The Batery drain is insane now...
Odin always said that the Binary is incorrect and can't flash any diferent rom
Any ideas or suggestions? Can I install a custom Rom at least?
Thanks and I hope you can help me.
Click to expand...
Click to collapse
Bump same question my device is 16 and binary i want to install is 14? help

no, you CANT downgrade the binary but you can try make a rom with older version of android but expect bugs and a lot of issues due the bootloader

i got s10+ "G975FXXUFHVE1" i cant downgrade also im new to this whole stuff i really need help
🥹

Ch_ali134 said:
i got s10+ "G975FXXUFHVE1" i cant downgrade also im new to this whole stuff i really need help
Click to expand...
Click to collapse

Same boat here... S10+
i'm on G975FXXUGHVJ5 (android 12), so locked to bin 16. Wanted to go back to G975FXXSEFUL1 (android 11) So I could use my GearVR again, but that is bin 14... Backporting GearVR is out of the question... So i'm left with a feature downgraded p.o.s.. and this was the last moddel to support GearVR...

Pandoriaantje said:
Same boat here... S10+
i'm on G975FXXUGHVJ5 (android 12), so locked to bin 16. Wanted to go back to G975FXXSEFUL1 (android 11) So I could use my GearVR again, but that is bin 14... Backporting GearVR is out of the question... So i'm left with a feature downgraded p.o.s.. and this was the last moddel to support GearVR...
Click to expand...
Click to collapse

From what i've read, its mainly dowload mode/odin that does the check and blocks the downgrade. But what about converting an official samsung update to a flashable twrp/recovery zip? I already have a fully magisk rooted stock android 12 rom, i just want do downgrade the system to stock android 11 (rooted) for GearVR. I don't think actually loading the kernel/system is blocked at the bootloader lvl right?
Maybe with a rom kitchen it could be possible to convert to a flashable zip?

Pandoriaantje said:
From what i've read, its mainly dowload mode/odin that does the check and blocks the downgrade. But what about converting an official samsung update to a flashable twrp/recovery zip? I already have a fully magisk rooted stock android 12 rom, i just want do downgrade the system to stock android 11 (rooted) for GearVR. I don't think actually loading the kernel/system is blocked at the bootloader lvl right?
Maybe with a rom kitchen it could be possible to convert to a flashable zip?
Click to expand...
Click to collapse

Pandoriaantje said:
From what i've read, its mainly dowload mode/odin that does the check and blocks the downgrade. But what about converting an official samsung update to a flashable twrp/recovery zip? I already have a fully magisk rooted stock android 12 rom, i just want do downgrade the system to stock android 11 (rooted) for GearVR. I don't think actually loading the kernel/system is blocked at the bootloader lvl right?
Maybe with a rom kitchen it could be possible to convert to a flashable zip?
Click to expand...
Click to collapse
its only blocked when the bootloader is locked, you can just slap the files into an unsigned tar and it will flash fine with odin (bootloader cant be downgraded tho), but you will have to unlock bootloader and the binary version wont be downgraded just ignored

NigrumTredecim said:
its only blocked when the bootloader is locked, you can just slap the files into an unsigned tar and it will flash fine with odin (bootloader cant be downgraded tho), but you will have to unlock bootloader and the binary version wont be downgraded just ignored
Click to expand...
Click to collapse

NigrumTredecim said:
its only blocked when the bootloader is locked, you can just slap the files into an unsigned tar and it will flash fine with odin (bootloader cant be downgraded tho), but you will have to unlock bootloader and the binary version wont be downgraded just ignored
Click to expand...
Click to collapse
My bootloader is already unlocked. haven't tried downgrading through ODIN, as this is my Daily driver Phone, but i'dd love to get GearVR back. The phone is fully unlocked, with custom kernel, as per my Signature ... So (according to you) I should be able to downgrade to G975FXXSEFUL1 without error through ODIN? despite everyone claiming it can't be done? (I realise that the bootloader binary can't be downgraded, but ODIN/Download mode checks everything. Bootloader, kernel, etc.. no?)
What do you mean with "unsigned tar"?
side question: What about kernel? could I reuse/reflash (from TWRP) my current kernel (Ambasadii HVJ5, android 12) as it is pre-patched with latest magisk, on an older android 11 rom?

Pandoriaantje said:
My bootloader is already unlocked. haven't tried downgrading through ODIN, as this is my Daily driver Phone, but i'dd love to get GearVR back. The phone is fully unlocked, with custom kernel, as per my Signature ... So (according to you) I should be able to downgrade to G975FXXSEFUL1 without error through ODIN? despite everyone claiming it can't be done? (I realise that the bootloader binary can't be downgraded, but ODIN/Download mode checks everything. Bootloader, kernel, etc.. no?)
What do you mean with "unsigned tar"?
side question: What about kernel? could I reuse/reflash (from TWRP) my current kernel (Ambasadii HVJ5, android 12) as it is pre-patched with latest magisk, on an older android 11 rom?
Click to expand...
Click to collapse
unpack the stock tar.md5 using 7zip or some tool and repack it into a normal .tar, to my knowledge odin only checks the binary of original unmodified tar.md5 files like they come from samsung (my newest samsung is from 2017 so that may not be true anymore but it should still be)
for the kernel question i dont really know as i run android 8 with a modded stock kernel

NigrumTredecim said:
unpack the stock tar.md5 using 7zip or some tool and repack it into a normal .tar, to my knowledge odin only checks the binary of original unmodified tar.md5 files like they come from samsung (my newest samsung is from 2017 so that may not be true anymore but it should still be)
for the kernel question i dont really know as i run android 8 with a modded stock kernel
Click to expand...
Click to collapse
Any updates on this process, i would also give it a try if it works out.

crucknova said:
Any updates on this process, i would also give it a try if it works out.
Click to expand...
Click to collapse
not really, my newest samsung is an a5 2017 (where this process works fine)
but it should work, downside is that your bootloader needs to be unlocked as you build you own unsigned flashfile
EDIT: i cant get it to work anymore even tho thats how i did it the first time, flashing using a custom recovery will work tho if thats an option for you
QUICK TUTORIAL
1: download your desired stock firmware
2: extract AP****.tar.md5 (basically just a normal tar with signatures at the end use 7zip or any other program you know)
3: repack boot.img system.img vendor.img (vendor.img may not be there depending on the android version) into an uncompressed tar (using 7zip or any other program)
4: flash said tar using odin
you could also manually flash the image files using heimdall without repacking into an tar

NigrumTredecim said:
not really, my newest samsung is an a5 2017 (where this process works fine)
but it should work, downside is that your bootloader needs to be unlocked as you build you own unsigned flashfile
QUICK TUTORIAL
1: download your desired stock firmware
2: extract AP****.tar.md5 (basically just a normal tar with signatures at the end use 7zip or any other program you know)
3: repack boot.img system.img vendor.img (vendor.img may not be there depending on the android version) into an uncompressed tar (using 7zip or any other program)
4: flash said tar using odin
you could also manually flash the image files using heimdall without repacking into an tar
Click to expand...
Click to collapse
Thanks for the reply and a quick tutorial
NigrumTredecim​i have an s10 plus and a m30, im a bit hesirtant on trying it on s10 plus, but i will try the process on m30, as i need to downgrade it as well!
can you give me an more detailed tutorial on the 3rd step which includes repacking the boot.img system.img vendor.img, should i delete everything except these 3 and repack or what!
Thank you

download lz4 https://github.com/lz4/lz4/releases and drag and drop your .img.lz4 files onto the exe to get the img files
AAAAAAAAAAAAAAA i cant get it to work even though thats how i did it before already, using a custom recovery to flash the images will definitely work, so thats an option for you thats easier just unpack the .img.lz4 and skip the rest and flash using a custom recovery
just leaving the rest here in case somebody wants to find where i made the oopsie here
select your files in 7zip and then click the green plus in the top left corner
then pick tar in the format dropdown menu and then click ok to create the archive
then open said tar with odin

NigrumTredecim said:
download lz4 https://github.com/lz4/lz4/releases and drag and drop your .img.lz4 files onto the exe to get the img files
AAAAAAAAAAAAAAA i cant get it to work even though thats how i did it before already, using a custom recovery to flash the images will definitely work, so thats an option for you thats easier just unpack the .img.lz4 and skip the rest and flash using a custom recovery
just leaving the rest here in case somebody wants to find where i made the oopsie here
select your files in 7zip and then click the green plus in the top left corner
then pick tar in the format dropdown menu and then click ok to create the archive
then open said tar with odin
Click to expand...
Click to collapse
if i do a custom recovery the knox would trip and i wont be able to use the samsung pay. which i use a lot for payments. And thanks for your support dude.