Related
Hi!!
PLEASE NOTE!!
This guide and these files are ONLY intented for samsung galaxy ace S5830i
If you use these files in any other model your phone will be unable to boot anymore and you might not be able to recover it from brick.
This guide is mainly for getting rid of the junk mobile companies put in your mobile phones.
When you are finished you will be updated to a Non-Branded STOCK 2.3.6 Turkish ROM. This rom is multilingual so you'll find no problems
You need to do the flasing:
-Odin v1.84
-ROM Files (multiple ROM files, as many people have problems with one-package file)
-PIT FILE (cooperve_0623.pit)
-Samsung Mobile Drivers 1.4.8.0
1 - Be sure to have installed the drivers properly. Reboot your system after de installation.
2 - Run ODIN 1.84 as administrator.
3 - Select the PIT File (do not change any option in ODIN, leave them as they are)
4 - Select all the four files in their proper place (this is the same as other samsung mobiles, do not use DEFAULTCALDATA file if you don't know what it is for, just use the other 4 files)
5 - Put your Galaxy ACE in download mode. To do so, shutdown your phone, remove the battery, remove simcard, remove microsdcard. Wait 10 secs. Put the battery (dont insert SIM or SDCARD). Now press vol+ vol- and power and wait until a warning screen appears. Then pres Vol UP to continue. You will see now DOWNLOAD MODE
6 - Connect your galaxy ace to your PC via USB. Odin will detect it and a yellow box will appear. Press START and do not touch anything until the proccess finishes. The phone will auto-reboot if everything goes well.
7 - When the android configuration screen appears, shutdown your phone, insert SIM and SDCARD and turn it on again. Finish the configuration proccess.
8 - DONE!!!
If you want to download all the files needed (except for the samsung drivers) download this .rar file
http://ul.to/ixtvnths
You are free to copy, send, upload in other server, etc in order for people to get the file.
I think it is easy but should you need an screenshot please feel free to tell me
Thanks for reading
Here is everything you need for a flawless upgrade from a 4.2.2 to 4.4.2 on the i537 hardware.
Step 0: Download this zip file. It has everything that we will need (except Odin3. Don't want my link/thread/post pulled).
Step 1 - Update from to 4.3.
Download and unzip the Stock ML2 4.3 image. Reboot your phone into Download Mode (Hold Volume Down while booting up, then press Volume Up when prompted). Don’t worry about current root, SafeStrap, etc - as it’s all going away soon.
Step 2 - Match up the file names to the four ‘Files’ sections in the lower right corner of Odin3. The individual filenames of the .tar.md5 files will be used as an identifier. Check “update bootloader” and click ‘Start’. Once it finishes and reboots into 4.3, enable USB debugging mode on the phone.
Step 2- Reboot into Download Mode. Apply Pwnedkernel 4.3 with Odin using the PDA File section.
Step3 - Now let the phone boot up. You will need USB Debugging enabled again, and ensure that you have USB ADB access.
Step 4 - Once ready, run Saferoot to the running pwned 4.3 image (install.bat for Windows, install.sh for Linux/Mac OS). Follow the terminal instructions until completion.
Reboot. Launch SuperSU and update the binary. Disable Knox with your new root access. Ignore any issues with Modems, etc.
Step 5 - Flash original 4.3 kernel back with Odin3 using the PDA File section.
Step 6 - Place your SafeStrap apk, PwnedKitKat, and SuperSU to your SD Card.
Step 7 - Install SafeStrap (make sure to launch it for the bootloader to install correctly)
Step 8 - Reboot into SafeStrap recovery. Flash PwnedKitKat.zip, followed by SuperSU.zip. Do not reboot in between, clear cache, or any other nonsense.
Step 9 - When finished, reboot back into DOWNLOAD MODE. Now flash the stock KitKat kernel using Odin3 (using the PDA File section).
Finished!
Shout-out to: Hashcode, My-blue-snog-box, TransformixS4, & Sunderwear. Y’all have kept me sane dealing with this phone and it’s locked bootloader.
casadelbeard said:
Finished!
Shout-out to: Hashcode, My-blue-snog-box, TransformixS4, & Sunderwear. Y’all have kept me sane dealing with this phone and it’s locked bootloader.
Click to expand...
Click to collapse
Great guide!
I'm glad I helped and thanks for the shout out!
I hope I will help you in more things!
-TransformixS4
Do I have to do a factory reset? Or simply clear cache/dalvik?
casadelbeard said:
Step 1 - Update from to 4.3.
Click to expand...
Click to collapse
I hate to be a nit picker, but shouldn't this say "from 4.2 to 4.3"?
Thanks for a great post and the zip file! Makes it nice n easy for us. Can't wait to flash later!
?
Tell me how do you download your zip because after an hour of "downloading to my pc" I yet have to see any file in any of my download folders.
2nd of all I made the mega account, tried downloading through the account to my pc, then through the cloud, then through the sync & still am unable to physically see any download happening onto my pc hdd... Although I respect the owner, Kim Dotcom there is something wrong since you can't simply even download a file like it is normally available, (a standard) through your browser..
Please explain to me how do you get the 1.67gb file onto the pc because I tried everything I could think of and I am unable to & I am not a noob.
This is the first time i stumbled upon something weird like this..
when i update to Kitkat on safestrap it says "Checking MD5 File... Skipping MD5 Check: no MD5 File found." Should i be worried?
casadelbeard said:
Here is everything you need for a flawless upgrade from a 4.2.2 to 4.4.2 on the i537 hardware.
Step 0: Download this zip file. It has everything that we will need (except Odin3. Don't want my link/thread/post pulled).
Step 1 - Update from to 4.3.
Download and unzip the Stock ML2 4.3 image. Reboot your phone into Download Mode (Hold Volume Down while booting up, then press Volume Up when prompted). Don’t worry about current root, SafeStrap, etc - as it’s all going away soon.
Step 2 - Match up the file names to the four ‘Files’ sections in the lower right corner of Odin3. The individual filenames of the .tar.md5 files will be used as an identifier. Check “update bootloader” and click ‘Start’. Once it finishes and reboots into 4.3, enable USB debugging mode on the phone.
Step 2- Reboot into Download Mode. Apply Pwnedkernel 4.3 with Odin using the PDA File section.
Step3 - Now let the phone boot up. You will need USB Debugging enabled again, and ensure that you have USB ADB access.
Step 4 - Once ready, run Saferoot to the running pwned 4.3 image (install.bat for Windows, install.sh for Linux/Mac OS). Follow the terminal instructions until completion.
Reboot. Launch SuperSU and update the binary. Disable Knox with your new root access. Ignore any issues with Modems, etc.
Step 5 - Flash original 4.3 kernel back with Odin3 using the PDA File section.
Step 6 - Place your SafeStrap apk, PwnedKitKat, and SuperSU to your SD Card.
Step 7 - Install SafeStrap (make sure to launch it for the bootloader to install correctly)
Step 8 - Reboot into SafeStrap recovery. Flash PwnedKitKat.zip, followed by SuperSU.zip. Do not reboot in between, clear cache, or any other nonsense.
Step 9 - When finished, reboot back into DOWNLOAD MODE. Now flash the stock KitKat kernel using Odin3 (using the PDA File section).
Finished!
Shout-out to: Hashcode, My-blue-snog-box, TransformixS4, & Sunderwear. Y’all have kept me sane dealing with this phone and it’s locked bootloader.
Click to expand...
Click to collapse
I do not understand which 4 files to put where
Match up the file names to the four ‘Files’ ... How do you MATCH them up. I only see one file to match up called CSC
What does the AP CL and CP and how do those match up to Bootloader PDA and PHONE ??
Display issues
As soon as I installed 442 kernel display issues popped up. The screen is brighter on the left than on the right with vertical lines running throughout.
Started whole process again... issues go away until 442 kernel is reapplied.
Any suggestions?
I was able to get Eclipse TW 4.02 SS ROM to boot and it looks very nice so far.. as close to AOSP as we will get. I started with the usual 4.3 > TR> SS 3.71 > NC9 Update >KK Kernel > SS3.73 upgrade path, then downloaded the newest eclipse 4.02 SS ROM and 4.4.2 i537 modules. I went ahead and inserted the modules into the eclipse ROM just to save an additional flash step, then flashed the new rom, wiped data,dalvik and cache then rebooted to download and flashed the KK i537 kernel on top. After a few minutes I'm at the setup screen.
So far the only issue I'm battling is the default camera FC, the Google camera app doesn't seem to work either
downloading issues?
baldusiek said:
Tell me how do you download your zip because after an hour of "downloading to my pc" I yet have to see any file in any of my download folders.
2nd of all I made the mega account, tried downloading through the account to my pc, then through the cloud, then through the sync & still am unable to physically see any download happening onto my pc hdd... Although I respect the owner, Kim Dotcom there is something wrong since you can't simply even download a file like it is normally available, (a standard) through your browser..
Please explain to me how do you get the 1.67gb file onto the pc because I tried everything I could think of and I am unable to & I am not a noob.
This is the first time i stumbled upon something weird like this..
Click to expand...
Click to collapse
I have downloaded the file 3 times now (accidentally deleted it the first, then ineeded it on a laptop at a friends house. Downloaded flawlessly. Im FAARRR from a noob, but honestly, a 10 year old could do it. I did my sons active and mine. Try using a differrnt browser or something. Only took about 20 minutes total to download the whole file. I used IE every time. I dont know if thays the dame browser you used but if not, then try that. (I know this post is a little older, but for someone like me who just picked up a couple actives this week it came in mighty handy. Thanks for the tutorial. Does anyone know of any 4.4.2 touchwiz based rome that I can use now that I have safestrap (3.73) running? Or is this basically all we are going to get. Im ok with that but woild love a deodexed TW rom to use. Have trued deodexing mine several times now and while it says thay it worked and is complete, its still odexed after reboot from recovery??!?!
I have a big problem with my Samsung Galaxy Mini 2 GT-S6500D. My SD Card and USB storage is not loading up. If I try to open my files or gallery or listen to music it tells me there is not card inserted. When I go see the amount of storage used, It says 0,00B/0,00B for both USB and SD Card. Also, the upper part of the screen where it's suppose to give me notifications and battery stats and time is missing. As well as my Wi-Fi won't turn on, when I try to it gives me an error. I can't plug it onto my computer.I tried a few ways of fixing but to no avail. Anyone know how to fix this, people if it's possible not to lose my memory?
do you use cm 10.1 or stock
if stock try to flash it with odin3 and pit file
Please explain me what are you talking about. I am a noob to these stuff about and around phones
I think im using the stock one but the I can't connect my phone to the usb on the computer and use it normal. Nor I can't use internet
you should flash your phone this is the instructions
download odin3 https://www.copy.com/s/qmTqyZFweDIj/Odin3_v3.09.zip
samsung driver for s6500 downloadcenter.samsung.com/content/SW/201401/20140121132354500/SAMSUNG_USB_Driver_for_Mobile_Phones_v1.5.33.0.exe
frimware for s6500 fileparadox.com/0bi6jri969ai/S6500DBGMK1_S6500DXECML1_XEC_.zip
install samsung drivers and
Download firmware from the above list
and extract the zip file, you should get
.tar.md5 file along with few other files.
2. Download Odin v3.09 and extract the zip
file, you should get Odin v3.09.exe file
along with other files.
3. Now Open/Run Odin v3.09.exe file as an
administrator (to open program with
admin privilege, right click on the Odin
v3.09.exe file and click on the “Run as
administrator” from the context menu, this
is applicable only on Windows Vista,
Windows 7 or higher PC)
4. Switch off and boot Galaxy Mini 2 S6500
into Download Mode by pressing and
holding the Volume Down+Home+Power
buttons together (long press until the
boot screen appear). A warning message
will flash, now press Volume Up key to
proceed to Download Mode .
5. Now connect your Galaxy Mini 2 S6500 to
your PC via USB cable
6. In Odin screen, you should see a COM
Port number like “0:[COM7]” at ID:COM
section and “Added!” text at the message
box. This means your device has been
successfully detected by Odin. (If not, then
try connecting through another USB port.
If you are using desktop PC, use USB port
located at the back of the CPU. If still
don’t work, then you should reinstall the
USB driver and try again)
7. Make sure that, only the “Auto Reboot”
and “F. Reset Time” options are checked
in Odin screen.
8. Now, click on the AP button and select
the .tar.md5 file that you get by
extracting the firmware zip file in step 1.
9. Now, click on the Start button to begin
the installation process, and wait few
moments.
10. Once completed, you would see “PASS!”
message in ID:COM port having green
background
11. Your phone should automatically reboot
after completion
12. You can now disconnect/unplug your
phone from computer
Done it all, just one thing, when I completed it, it showed me RESET with blue background.................... After which, later when my phone loaded it turned into PASS.
Thank you for helping me fix the problem with my phone
if i help you press thanks
How to install Android 9 Pie update on Galaxy S9 [One UI update]
Compatibility: This section is compatible only with model SM-G960F of the Galaxy S9,
Step by step guide:
Step 1. Download the Android Pie firmware from the downloads section above – software version CRLI/CSAB. Make sure you have downloaded the correct firmware file on your PC. Remember, this is only for the Galaxy S9 model no. SM-G960F and Galaxy S9 model no. SM-G965F.
Step 2. Install Samsung USB driver (method 1 on the linked page) first of all. Double-click the .exe file of drivers to begin the installation. (Not required if you have already done this.)
Step 3. Also, download Odin PC software (latest version).
Step 4. Extract the firmware file now. You can use free software like 7-zip for this. Install 7-zip, then right click on firmware file and under 7-zip, select ‘Extract here’. You should get files in .tar.md5 format now. (You may a bunch of files, and you will find text like AP, BL, CP or CSC etc. written at the beginning of those files.) We will be loading this file into Odin, to be installed on the device.
Step 5. Extract the Odin file. You should get the Odin exe file (other files could be hidden, hence not visible).
Step 6. Disconnect your Galaxy S9 from PC if it is connected.
Step 7. Boot your Galaxy S9 into download mode:
Power off your device. Wait for 6-7 seconds after screen goes off.
Press and hold the three buttons Volume down + Bixby + Power together until you see the Warning screen.
Press Volume Up to continue to download mode.
Step 8. Double click on Odin .exe file (from step 5) to open the Odin window as shown below. Be careful with Odin, and do just as said to prevent problems.
Step 9. Connect your device now using the USB cable. Odin should recognize your device. It’s a must. When it recognizes, you will see Added!! message appearing in the Log box in the bottom left, and the first box under ID:COM will also show a no. and turn its background blue.
You cannot proceed until you get the Added!! message, which confirms that Odin has recognized your device.
If you don’t get Added!! message, you need to install/re-install drivers again, and use the original cable that came with the device. Mostly, drivers are the problem (look at step 2 above).
You can try different USB ports on your PC too.
Step 10. Load the firmware files into Odin. Click the AP button on Odin and the select the .tar.md5 file from above. See the screenshot below to find how the Odin window will look like after you have loaded the files.
Click on BL tab, and select the file beginning with BL text.
Click on AP tab, and select the file beginning with AP text.
Click on CP tab, and select the file beginning with CP text.
[Different!] Click on CSC tab, and select the file beginning with HOME_CSC text. If HOME_CSC file isn’t available, then select the file beginning with CSC text.
About CSC file: Using the HOME_CSC file won’t reset your device, and data on the phone shouldn’t be deleted. However, when we select regular CSC file, and it results in CSC on the device being different than that in CSC file, your phone will be formatted automatically. You can even choose to ignore loading the CSC file, that may do alright too. But if it doesn’t work out, repeat the whole process and select CSC file this time around.
Info: When you load files, Odin checks the md5 sum of firmware file, which takes time. So, simply wait until that’s done and the firmware file is loaded. Don’t worry if Odin gets unresponsive for a while, it’s normal. Binary size will also show up in Odin.
Step 11. Click on Options tab, and make sure Re-partition checkbox is NOT selected. Don’t use PIT tab, ever.
Go back to the Log tab now, as it will show the progress of the firmware installation when you hit the start button in the next step.
Step 12. Verify that everything is okay as mentioned above. When satisfied, click the Start button on Odin now to start flashing the firmware on your device.
Wait till installation is finished, after which your device will reboot automatically. You’ll get PASS message as shown below upon successful installation from Odin.
Some errors you may run into, and with respective solution.
If Odin gets stuck at setup connection, then you need to do this all again. Disconnect your device, close Odin, boot device into download mode again, open Odin, and then select the file and flash it again as said above.
If you get FAIL in the top left box, then also you need to flash the file again as stated just above.
Done!
Download Link:
Click Here To Download
Thanks bro
Bro,
The download link does not exist.
/*** BEGIN DISCLAIMER ***/
If you follow this procedure and lose every bit of content on your device / end up with a fancy paperweight, I, nor anyone involved with the referenced open source or otherwise licensed projects is responsible. It's all on you, and this will void your warranty. Do not proceed if you don't understand something. Chances are you will have a bad time.
/*** END DISCLAIMER ***/
Hey everyone - my Samsung Galaxy Tab A 10.1" (2019) - SM-T515 - recently applied a security update without my consent (The Samsung Android 11R September 8th 2021 Security update - side note, make sure that you turn off Samsung's push service ), which canned my previous root access. I use server software and internal port forwarding to do... Things on my device, so I needed my root access back.
Here's how I retrieved it, and how I put TWRP in place as my recovery partition in the process.
The Tools
Make sure you have these before you start. Because this is a Samsung device, you'll have to do some things under Windows, like using Frija and Odin (unfortunately).
1.) Frija - Available here - https://forum.xda-developers.com/t/tool-frija-samsung-firmware-downloader-checker.3910594/
2.) The latest SM-T515 / SM-T510 firmware from Samsung for your device's CSC (if you use the firmware for the wrong CSC code the most common problem that I have seen as a result is typically incorrect partition sizes after flashing, which can be corrected with TWRP). Frija is listed first, because you'll use Frija to get this directly from Samsung.
3.) Some kind of generic tool that you're comfortable with for working with archives. Ideally whatever tool you choose should be able to work with .tar, .gz, and .zip archives for this process. Personally I like 7-Zip on *Nix and Windows, and ZArchiver on Android.
4.) Odin (firmware flash tool by Samsung) - attached.
5.) The latest Samsung device USB drivers for your environment (they're fine as long as they enable both ADB and MTP correctly) - available here https://developer.samsung.com/mobile/android-usb-driver.html
6.) The latest TWRP image for Samsung SM-T5xx devices - available here https://androidfilehost.com/?fid=14943124697586374577 (and attached)
7.) ADB - downloading / installing and using adb are outside the scope of this post. It is available here - https://forum.xda-developers.com/t/...vers-15-seconds-adb-installer-v1-4-3.2588979/
8.) The latest Magisk APK file - available here https://github.com/topjohnwu/Magisk/releases/download/v23.0/Magisk-v23.0.apk
The Process
0.) Back up your stuff, and remove your SD card if it makes you more comfortable - do whatever you need to do to be comfortable with "I might lose EVERYTHING on this device." If you plan on following this procedure, you should know how to do this, and I'm not going to try to explain it. If you can't get past this part, you should stop while you're ahead and still have a device that boots.
1.) Unlock your bootloader.
2.) Download the most recent firmware package for your device using Frija and extract all of the individual .md5 files which it contains.
2.) Use Odin to flash the most recent firmware to your device, and factory reset / wipe / format partitions and caches until you have a clean device that boots correctly. If your partitions aren't sized properly at this point it isn't something to be too concerned with, as you can correct them later using TWRP.
3.) Turn developer options back on, enable USB debugging, set the default USB configuration to "File Transfer", connect your device to your PC and copy the Magisk APK over to the internal storage of your device.
4.) Remove .md5 from the filename of the AP file that was included in your firmware package from Samsung and extract its contents into its own directory.
5.) Extract the contents of the latest TWRP package for these devices into the same directory where you extracted the individual partition image files contained in the AP file. Overwrite contents in the destination directory as necessary. The TWRP package should contain three files - param.bin.lz4, recovery.img.lz4, and vbmeta.img.lz4 - If there are uncompressed images (.img files) that correspond to the LZ4 compressed images from the TWRP package in the AP file of your firmware package, remove them first. Odin will (understandably) freak out if you try to flash two different images to the same partition in the same flash operation.
6.) Compress the contents of your modified AP directory which now contains the TWRP package's contents into a tar ball on your PC, and then copy it somewhere that Magisk will be able to access it on the Internal storage of your device (the Downloads directory - "/storage/emulated/0/Downloads/" is a good choice).
7.) Copy the latest Magisk APK to your device (again, the Downloads directory is a good choice), and then install it on your device.
8.) Launch Magisk on your device and choose "Install". Be sure to uncheck the "Recovery Mode" option. We don't want to use "Recovery mode" for Magisk's patching process. Even though this is a Samsung device and this would normally be how to proceed, in this case we're using our own custom TWRP recovery partition, and we don't want Magisk to mess with it. So make sure you aren't patching the bootloader or recovery images in unnecessary ways with Magisk.
9.) In Magisk on your device, choose "Select and patch a file" and then choose the AP file that you created and copied to the device which now contains TWRP as its recovery partition.
10). Let Magisk do its patching and when it has completed take note of where the patched file which it generated was written.
11.) Launch a command line / Powershell / Bash terminal where you can perform ADB commands, and issue the command "adb pull "/storage/emulated/0/Download/magisk_patched-23000_xYzXyZ.tar" (replace "XyZxYz" with whatever random sequence of characters that Magisk generated during its patching operations) to use ADB to download the patched AP file from your device.
12.) Power off your device.
13.) Reboot your device into FANCY download mode by holding the volume up and volume down keys simultaneously while inserting a USB cable that is connected to your PC into your device's USB C charger port. Your device should boot as you insert the USB cable and your bootloader should already be unlocked, so when prompted press the volume up button to continue.
14.) Launch Odin on your PC, and choose the BL, CP, CSC, and UserData images from the firmware package that you retrieved from Samsung to flash the corresponding slots in Odin. In the AP file slot, choose the Magisk patched AP file which contains TWRP as its recovery partition which you retrieved previously using ADB.
15.) Start the flash operation in Odin, and wait patiently for it to complete. Stay alert, because if you left "Auto reboot" checked in the Odin options, your device will reboot immediately upon completion, and there are actions that you need to take while the device is in its "off" state before it re-launches itself.
16.) Once the Odin flash operation has completed, boot to recovery mode. If you left "Auto reboot" checked in Odin, immediately as the flash operation completes, press and hold the power key and the volume up key and remove the USB cable from the device. Otherwise press and hold the power button and the volume down button until the device restarts, and while the device is in its "off" state remove the USB cable and press and hold the power button and the volume up button during device restart to enter recovery mode.
17.) Immediately upon entering recovery mode you should see TWRP do a couple of things that ensure that Samsung's device protection solutions don't remove it. Once those operations have completed, reboot into the system partition.
18.) Your device should be BASICALLY ready to go. Go through the steps to "complete" setup as you see fit. If you have not already done so, connect your device to a WiFi or to an LTE network and then launch the Magisk application.
19.) Magisk may want to download updates, if it does, let it do so.
20.) Once any necessary updates / downloads have completed, re-launch Magisk and it should present you with a prompt to the effect of "Magisk is installed, but additional configuration needs to be done on your device for it to work the right way. Do you want to reboot now?" If you've made it this far, the answer is "Yes, please do."
21.) After rebooting, your device will now be configured, and be running TWRP in its recovery partition, along with a properly Magisk rooted system partition.
22.) ????
23.) PROFIT!
I hope this helps some people out!
- The Scarecrow - 2021/09/22
Has anyone besides been successful?
mydjtl said:
Has anyone besides been successful?
Click to expand...
Click to collapse
I can provide screenshots from the device that I did this to if you would like.
It's pretty cool to see the TWRP logo on a Samsung Tab series device that's running Android 11.
I don't even get the little Samsung warning prompt during device bootup that says "This device's software can't be verified" or whatever Samsung's custom ROM message is. All I get is the "This device's bootloader is unlocked" message, no warning about the integrity of the software.
mydjtl said:
Has anyone besides been successful?
Click to expand...
Click to collapse
Follow this simple as he'll no need to read all these things
pankspoo said:
Follow this simple as he'll no need to read all these things
Click to expand...
Click to collapse
Yeah - pretty much exactly that, except I Magisk patched the system image, and then copied the TWRP package's vbmeta and recovery image into the AP file for the Odin flash, and then flashed every slot rather than just the AP.
is it systemless root?
Will this work on Galaxy Tab A sm-t595? on android 10?
or know of a root guide that will work with said device?
If you dont untick auto reboot, how do you fix any issues that happen because of it?
I rooted my t500 but I think it auto rebooted, which then caused a vbmeta error that stopped it booting. It worked again after flashing the stock rom, but now it gives a vbmeta error if I try to flash a modded rom to root it and I cant get oem unlock to appear in the stock os (download mode says its already unlocked tho)
Hello,
Code:
9.) In Magisk on your device, choose "Select and patch a file" and then choose the AP file that you created and copied to the device which now contains TWRP as its recovery partition
Step 9 yields an error on T515 : Unsupported/Unknown image format
I also tried to install AP patched file with Odin, same result.
Any idea ?
Damn this works so nicely, thanks mate! Cheers!