Database Users

New tool!!! Forced downgrade of AT&T using Dirtycow exploit 5195

Warning: This is the most dangerous tool I've personally ever seen!!! It writes to your partitions without checking.. you could accidentally write a text file to the partition!!!
I created tool specifically for downgrading. I have to be away 1 to 4 weeks and then I will continue progress. It is my goal to downgrade to Android 5.01, take root, then upgrade to Nougat with full root. Some ideas are to flash OJ1 files using this tool then reflash them again with Odin. You may have to shrink the system.img and flash cache.img last, if at all. Another idea is to get twrp from a Note 5 BOTA0 and BOTA1 along with RECOVERY partitions then flash them to the device.. risky would be an understatement but I've tested writing to a lot of other partitions already.. just not those.
i'm so tired right now.. it works and i will make it better but i need sleep.. (see the readme on github)
https://github.com/droidvoider/Android_6.01__DD_Dcow
IGNORE THE REMAINING POSTS THEY ARE OUTDATED... I am rushing to finish this tonight because I won't have time for 1 to 4 weeks. Please post issues I will address them.

droidvoider said:
when you flash the correct one your phone will text AT&T a coded message
Click to expand...
Click to collapse
Can you please rephrase this? Is there any way for us to intercept or interfere with such a message.

Anonymously_Unknown said:
Can you please rephrase this? Is there any way for us to intercept or interfere with such a message.
Click to expand...
Click to collapse
You can avoid it by flashing your entire firmware again. I haven't tried to avoid the message I just end up flashing the entire firmware back when my attempts fail.
edit
New method, tested several times now and now more unwanted texts during testing. (probably great info to clear the data trail of hack attempts on frp lock bypass, usually a modem file "i think?")
**** Please be advised I've never attempted a frp bypess nor do I flash incorrect firmware, only previous but correct versions! still dangerous.
BEFORE flashing back the correct modem firmware...
<under application manager "more+show system apps">
1. Clear data MESSAGES
2. Remove permissions MESSAGES
3. Clear data OMACP
4. Flash back modem file and repeat step 1 through 3 for good measures. Install Google Messenger, now Android Messenger..

Ok I have dirtycow working with PK1. I can patch things like /system/bin/run-as and also /data/tmp/local/* .... However if I try to patch /data/data/app-name/textfile my phone reboots. (not that i need to patch anything there) At this point I don't even know if there are any other PK1 AT&T Note 5 guys left besides me!! So this is just a short snippet 'how to' get dirtycow working on this version. If you need more help speak up.
(I bet you can take this kernel into the next few version but I'm not upgrading to find out.. logcat has some more errors than usual but nothing major, i broke the security update thing look like)
You don't have to use heimdall! ~ I made odin flashable tar.md5 files for this process a few posts down with a bunch of *****asterisk***** so I can find that post myself, laugh. Detailed inside is how I made them which is detailed on this forum very well.
=========> Flash boot.img from N920AUCS3CPJ1 firmware version into your Note 5 with this baseband version: N920AUCS4CPK1 <=============
1. Download heimdal from github and look at the readme under Linux. Near bottom of readme follow instructions including installing the 4 main dependencies.
2. You can use heimdall in the terminal or open a terminal and type: heimdall-frontend for a graphical user interface.
3. REBOOT UBUNTU! In some rare cases we do reboot Ubuntu.
4. Down the files I linked below which are the .pit file for version PK1 and the boot.img from version PJ1.
5. Select 'flash tab' and then browse for .pit file.. Click Add button, then select BOOT.
6. Browse for the boot.img we download then click flash.. Good luck, hope you don't brick!!! so far i'm good but it's been 3 hours only.
PK1 .pit file and PJ1 boot.img file to be used with heimdal for Ubuntu 16.10
https://mega.nz/#!KwlQTSDZ!N-SItLDERCOIE-hFENNQoH3g8SQMDgpa-RajolQhe5Q
Edited in Notes:
logcat clears up after a few minutes and the errors completely stop. I'm not even planning to flash it back to normal!

Is the linked PJ1 boot.img, the stock boot.img extracted from the PJ1 AP file for ODIN?
In my experience with downgrading my device, I can downgrade my build by flashing only the AP file of my chosen build firmware. But the AP file's boot.img containing the kernel must be loadable by the installed bootloader (sboot.bin). I cannot flash thus far an sboot.bin to my device from a firmware based on a binary 2 bootloader. I have a binary 3 lollipop bootloader I can flash to downgrade my system. After doing this it allows me to overwrite it a binary 2 sboot, but I wasn't able to get the tether root to fully reboot without a wipe first. Then I must start back at 3BPH4 and then re-downgrade to attempt a pull again. It's long. And requires 2 stages of flashing, per attempt.
The problem I have is how do I get ODIN to stop instantly denying my chosen file to flash. What check am I not bypassing or getting correct. How do I find the correct checksum or value to edit or spoof to force a mostly official-ish tar. There should be a way somewhere to intercept the communications between the phone, pc, download mode and the modem.

Delgoth said:
Is the linked PJ1 boot.img, the stock boot.img extracted from the PJ1 AP file for ODIN?
Click to expand...
Click to collapse
Yes it is the stock boot.img from a copy of the PJ1 firmware I found from this site somewhere.
Delgoth said:
In my experience with downgrading my device, I can downgrade my build by flashing only the AP file of my chosen build firmware. But the AP file's boot.img containing the kernel must be loadable by the installed bootloader (sboot.bin).
Click to expand...
Click to collapse
I don't have PJ1 sboot.bin because the copies online all have an error in the BL tar.md5. When I read your post I decided to try flashing in recovery.img, it accepted it! In my recovery screen now it reads PJ1, in my About screen reads PK1. I am starting to think I can keep flashing in PK1 stuff until it might let me flash the reset. I would love to find a N920AUCS3CPJ1 with a valid BL_N920AUCS3CPJ1_CL8961126_QB11173364_REV00_user_low_ship.tar.md5 file. (I can try this with PH4 but then I have to setup phone again so I rather wait until I crash it again lol)
Delgoth said:
The problem I have is how do I get ODIN to stop instantly denying my chosen file to flash. What check am I not bypassing or getting correct. How do I find the correct checksum or value to edit or spoof to force a mostly official-ish tar. There should be a way somewhere to intercept the communications between the phone, pc, download mode and the modem.
Click to expand...
Click to collapse
I've seen my recovery.img files getting denied by Odin before, however, I just cleanly flashed in recovery from PJ1 using heimdall. Again if I am not being clear I extract the .img files from the tar.md5 then I use the .pit file from PK1 and that .img file in "heimdall" for Ubuntu 16.10
I'm starting to think we can weasel down because PJ1 is binary 3, PK1 is binary 4. (edited.. wrong, you can flash boot.img, recovery.img, userdata.img and cm.bin, modem.bin crashes modem)

Battery drain less than 1% in 8 hours of screen off time!!
Disabling the AT&T apps with my simple exploit (now with it's own cve code and everything) I had great results finally getting back into the 6% battery drain in 8 hours of sleep. Then I discovered if I disabled almost all of Google Play except Google play itself and video watching stuff I was at approximately 2% drain in 8 hours.
Simply flashing in the previous version boot.img and recovery.img made my battery drain with screen off almost 0!!!! I do have to deal with AT&T Software Update has stopped when I boot, or when I disconnect/reconnect my network. This includes if I lose signal. But it is just an OK message and the phone keeps working even if you don't press OK.
Attached you will see my battery screen showing basically no loss from 2:10am to 10:08am. (edit just realized it says 98% now but it's because I was looking at it and screen capping)

If anyone is interested in a partial downgrade to allow the use of dirtycow here are my files. This was tested to downgrade the N920AUCS4CPK1 kernel to the N920AUCS3CPJ1 kernel by flashing boot.img and recovery.img of the previous baseband. (Oddly allowed? sw rev check fail doesn't apply to these files).. You can also use the userdata.img file which is not well tested, but I'm now using that also.
These are Odin flashable tar.md5 files after you unzip them. IF HAVE NOT tested these in Odin EXCEPT the 1st option, boot.img and recovery.img only.
1. N920AUCS3CPJ1 boot.img and recovery.img to be flashed on top of an already installed/working Note5 w/ N920AUCS4CPK1 installation.
https://mega.nz/#!nwFUVQaC!R3inD-QNEfLKmLGnVnMuAHG10WaMzvivdNn5samhSkA
2. N920AUCS3CPJ1 boot.img and recovery.img with N920AUCS4CPK1 system.img and userdata.img .. (This is for a full setup, use this AP file instead of PK1 AP file)
https://mega.nz/#!XsdxAR7D!RrmYvOgDYdt72MDsV7OmpW-eM5gHqSQu7clwrOIdSQk
3. This is the experimental AP file replacement. N920AUCS3CPJ1 boot.img, recovery.img and userdata.img with N920AUCS4CPK1 system.img. (CAUTION: untested)
https://mega.nz/#!e0ESUZBT!QbLR9Ew0-DFsOpte2wN-wCeRRfWQEATjyKlmuSn8hP8
Note: How I created them is detailed in the zip file.
(Downgrade isn't too likely at the moment I have no earthly idea how I would get rid of sboot.bin "the locked bootloader". The rest of my efforts are just root while preserving knox container)
*
*
*
*
*
*
*
*
**********************************************************************************************
*********************************SEARCH FOR ROOT*****************************************
**********************************************************************************************
****************Note 5 64 bit hacking tools. Readme has links to sources*******************
**********************************************************************************************
No root yet, just the beginning tools right now. (find a way to do something? please share this community needs it!)
Added: dirtycow, applypatch, app_process64, run-as and cowroot (run-as and cowroot don't work, even if cowroot worked it would crash in 20 seconds)
https://mega.nz/#F!wQVggApJ!Zv5wojVW5kiFi2crDDu02g
****************************************************************************************************************************************
Warning: The Note 5 is cool in a way to hack because most things you do will be undone when you reboot. I've altered things in / and /system/bin multiple times without any lasting effects! If you do modify things concerning knox permanently she won't boot. If you install a priv-app twice to make it stop you can also crash the phone out when playing around with knox. (refering to my little trick, see my thread on it. You reinstall a system/priv-app using adb install -rtsd <apk-name-you-adb-pulled-from /system/priv-app/> <=== oddly allowed. On another note patching certain things with dirtycow in /data will cause a sudden reboot.
If you patch app_process64 your phone will go dark, things that are important stop working. I personally do not want my phone in this state for long so I plan out things to try then get out quickly. I have disabler going, but I am not experiencing any cause for concern such as overheating, mass battery draw or odd screen handling. besides it going darker with app_process
Super dangerous expensive game be sure you want to play the entry fee is high. And backup your data you may never see this phone working again.
Project stopped someone else can take over without giving credit. Please don't give credit I don't want my name on this The tools on my github will be left up and I will help you compile any idea but officially I don't need to downgrade, and I wanna buy a unlocked phone

I designed a tool for the purpose of downgrading that I won't have time to test completely, but does work. It allows you to pull every partition from your device that you can see and also write those same partitions back!! This does include BOTA0, BOTA1, BOOT, RECOVERY, SYSTEM. you name it!!
back soon guys, be careful with it.. pulling seems safest if you are new, yeah? have fun!
https://github.com/droidvoider/Android_6.01__DD_Dcow

N920C ?

TWRP for P580 running Oreo?

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

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

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

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

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

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

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

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

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

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

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

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

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

We should ask a dev to update twrp for android 8.1

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

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

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

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

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

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

failing root, Odin gets stuck at cache.img [SM-G903F]

Hey guys, first time rooting my phone and as far as I can tell I followed every advice online but can't actually do it. I enabled USB debugging as well as install from unknown sources, removed the lock pattern and disabled some kind of protection in the developer settings. After that I downloaded the official firmware from firmware.mobi (CF Auto root), got Odin booted up and also booted into download mode on the smartphone. When I select my boot image and let it start, it gets to about 80% and stops at cache.img. My USB cable is not faulty and Odin is up to date as well. Any ideas on what I could do about the situation?

GDTyron said:
official firmware from firmware.mobi (CF Auto root)
Click to expand...
Click to collapse
Are you sure this is the right build for your exact firmware version (what's your exact model)? Never rooted official build - never needed. I jumped from stock ROM directly to LineageOS 15.1 + su addon + opengapps.

A51 AOSP vanilla firmware pure android + root. without gapps.

Draw your attention. There is no bootload patch for the May update (A515F...3BTD4). You cannot build from the May update based on these instructions. But you can create a bootload patch for the May update yourself (we will be grateful if you share it here), or use instructions for self-assembly, firmware that was released before May 2020, or use the ready-made version that is proposed in the topic. May update may be lowered. Accordingly, the instructions are correct.
A51 AOSP vanilla firmware pure android + root. without gapps.
basis and discussion
https://forum.xda-developers.com/galaxy-a51/how-to/galaxy-a51-root-unlock-bootloader-flash-t4053065
To install, you must have Thailand stock on your phone. (if you feel the need for pure rom you can install Thailand firmware on your phone (in any country) first and then use this rom)
AP_A515FXXU3ATC3_CL17851094_QB29741186_REV00_user_low_ship_meta_OS10.tar.md5
BL_A515FXXU3ATC3_CL17851094_QB29741186_REV00_user_low_ship.tar.md5
CP_A515FXXU3ATC1_CP15294611_CL17851094_QB29641384_REV00_user_low_ship.tar.md5
CSC_OMC_OLM_A515FOLM3ATC3_CL17851094_QB29741186_REV00_user_low_ship.tar.md5
HOME_CSC_OMC_OLM_A515FOLM3ATC3_CL17851094_QB29741186_REV00_user_low_ship.tar.md5
https://www.sammobile.com/samsung/g...T6-kad_5CGhxM0_oN8OpqFmxK9Ic3vl4HJiOYGHLWZkhQ
Download the Samsung firmware for the Galaxy A51 SM-A515F with product code THL from Thailand. This firmware has version number PDA A515FXXU3ATC3 and CSC A515FOLM3ATC3. The operating system of this firmware is Android 10 , with build date Mon, 09 Mar 2020 06:15:30 +0000. Security patch date is 2020-03-01, with changelist 17851094.
Model SM-A515F
Model name Galaxy A51
Country
Version Android 10
Changelist 17851094
Build date Mon, 09 Mar 2020 06:15:30 +0000
Security Patch Level 2020-03-01
Product code THL
PDA A515FXXU3ATC3
CSC A515FOLM3ATC3
AOSP vanilla.tar (only firmware size 2.2 gigabytes) remember for root rights you need to flash the kernel
https://ln2.sync.com/dl/7261cb390/pgwapmtq-gavgymv7-jthnj54s-ym4c7njc/view/default/9350928780004
AOSP (zip archive: firmware, kernel, tools, instructions, links. Firmware + kernel are in the A51AOSPcleanvanilla folder size 1.7 gigabytes)
https://ln2.sync.com/dl/162028af0/3457nwui-mur73px8-nkn68249-rikxt4dg/view/default/9350929170004
setting
unlock bootloader
unlock bootloader (step1)
go to settings. about the phone. several times click on the line "build number" - we become a developer.
back to the settings. go to the system item. bottom line is for developers. looking for the line "unlock bootloader" or "factory unlock"
if you suddenly find that there is no “unlock bootloader” item, you need to turn off the Internet, rearrange the date 2 "months ago. Turn on the Internet. Go to the search engine and type something. Then turn off the Internet again, set the correct date and go to the developer's menu.
item appeared
unlock bootloader (step2)
1. turn off the phone.
2. Hold down the volume keys Vol + and Vol -.
3. connect the computer USB to the phone.
4. the phone as soon as it turns on, release the buttons.
5. and immediately hold down the Vol + key.
6. and once again prompts you to hold down the Vol + key
in the same way and blocked.
!!! All your actions will lead to a reset, I advise you to backup and untie your Google, Samsung account !!!
Do not block the bootloader on custom firmware and custom kernels - different devices behave differently, but there can be serious problems, up to and including the brick of the device
put the phone in download mode
odin itself and files for firmware need to be placed in the root of the disk otherwise different kinds of problems may arise.
flash one by one through odin, inserting into the AP window 1) vanilla.tar 2) boot (NoForcedEnforce) .tar, be sure to turn off auto-reboot (auto-reboot, tab in odin)
in case of any incomprehensible situation, as well as between the firmware of the first and second file (if the kernel does not want to flash), go into the recovery and make wipes, then return to the firmware mode DO NOT FORGET TO REMOVE THE CHECK REBOOT IN ODIN after all the firmware boot into the recovery and do everything wipes and dumps!
also with various kinds of glitches can help restart the computer.
ATTENTION! do not disconnect the wire while ODIN is running - wait until ODIN finishes its work and you can disconnect the wire, reboot, etc. without problems as many times as needed.
after installing AOSP to get root, install the terminal (for example, from f-droid https://f-droid.org/ https://f-droid.org/F-Droid.apk)
dial in terminal
su
setenforce 0
getenforce
should issue
permissive
THANKS TO ALL with xda!
personal big thanks
BK https://forum.xda-developers.com/member.php?u=9402185
map220v https://forum.xda-developers.com/member.php?u=7618808
phhusson https://forum.xda-developers.com/member.php?u=1915408
gabrielfrias https://forum.xda-developers.com/member.php?u=4661848
ToddNachste https://forum.xda-developers.com/member.php?u=10721267
all health! Have a good mood! happiness!
p.s. IMPORTANT NOTE! start flashing the phone from a working state. that is, when the phone was launched at least once, there is a mark on the unlocked bootloader in the developer's menu. if you start the firmware immediately after resetting to the factory state, it is more likely that you will get an error about a locked bootloader, even if it is unlocked.
if you have a problem and a message is displayed on the phone screen: connect your phone to the Samsung Smart Switch program for recovery, you can try to fix it by flashing the phone through odin with official firmware, you just need to remove the check from the first line of BL, flash everything else as usual AP, SP, CSC ..
also remember, your firmware and kernel file may be damaged along the way. just download again.
p.p.s. The firmware contains 139apk including system (14apk user), at your discretion, disconnect / replace. in a 6/128 phone, firmware takes 8% free 117 gigabytes.
in native stock ~ 500apk%)
p.p.p.s. Before asking questions, look at the topic and header https://forum.xda-developers.com/galaxy-a51/how-to/galaxy-a51-root-unlock-bootloader-flash-t4053065, perhaps this has already been discussed. Thank you.
p.p.p.p.s. The firmware was created for personal use and is not laid out for tests and reviews. use if you need a clean android.

Nice tutorial ! Thanks

YOisuPU said:
A51 AOSP vanilla firmware pure android + root. without gapps.
basis and discussion
https://forum.xda-developers.com/galaxy-a51/how-to/galaxy-a51-root-unlock-bootloader-flash-t4053065
To install, you must have Thailand stock on your phone. (if you feel the need for pure rom you can install Thailand firmware on your phone (in any country) first and then use this rom)
AP_A515FXXU3ATC3_CL17851094_QB29741186_REV00_user_low_ship_meta_OS10.tar.md5
BL_A515FXXU3ATC3_CL17851094_QB29741186_REV00_user_low_ship.tar.md5
CP_A515FXXU3ATC1_CP15294611_CL17851094_QB29641384_REV00_user_low_ship.tar.md5
CSC_OMC_OLM_A515FOLM3ATC3_CL17851094_QB29741186_REV00_user_low_ship.tar.md5
HOME_CSC_OMC_OLM_A515FOLM3ATC3_CL17851094_QB29741186_REV00_user_low_ship.tar.md5
https://www.sammobile.com/samsung/g...T6-kad_5CGhxM0_oN8OpqFmxK9Ic3vl4HJiOYGHLWZkhQ
Download the Samsung firmware for the Galaxy A51 SM-A515F with product code THL from Thailand. This firmware has version number PDA A515FXXU3ATC3 and CSC A515FOLM3ATC3. The operating system of this firmware is Android 10 , with build date Mon, 09 Mar 2020 06:15:30 +0000. Security patch date is 2020-03-01, with changelist 17851094.
Model SM-A515F
Model name Galaxy A51
Country
Version Android 10
Changelist 17851094
Build date Mon, 09 Mar 2020 06:15:30 +0000
Security Patch Level 2020-03-01
Product code THL
PDA A515FXXU3ATC3
CSC A515FOLM3ATC3
AOSP vanilla.tar (only firmware size 2.2 gigabytes) remember for root rights you need to flash the kernel
https://ln2.sync.com/dl/7261cb390/pgwapmtq-gavgymv7-jthnj54s-ym4c7njc/view/default/9350928780004
AOSP (zip archive: firmware, kernel, tools, instructions, links. Firmware + kernel are in the A51AOSPcleanvanilla folder size 1.7 gigabytes)
https://ln2.sync.com/dl/162028af0/3457nwui-mur73px8-nkn68249-rikxt4dg/view/default/9350929170004
setting
unlock bootloader
put the phone in download mode
odin itself and files for firmware need to be placed in the root of the disk otherwise different kinds of problems may arise.
flash one by one through odin, inserting into the AP window 1) vanilla.tar 2) boot (NoForcedEnforce) .tar, be sure to turn off auto-reboot (auto-reboot, tab in odin)
in case of any incomprehensible situation, as well as between the firmware of the first and second file (if the kernel does not want to flash), go into the recovery and make wipes, then return to the firmware mode DO NOT FORGET TO REMOVE THE CHECK REBOOT IN ODIN after all the firmware boot into the recovery and do everything wipes and dumps!
also with various kinds of glitches can help restart the computer.
ATTENTION! do not disconnect the wire while ODIN is running - wait until ODIN finishes its work and you can disconnect the wire, reboot, etc. without problems as many times as needed.
after installing AOSP to get root, install the terminal (for example, from f-droid https://f-droid.org/ https://f-droid.org/F-Droid.apk)
dial in terminal
su
setenforce 0
getenforce
should issue
permissive
THANKS TO ALL with xda!
personal big thanks
BK https://forum.xda-developers.com/member.php?u=9402185
map220v https://forum.xda-developers.com/member.php?u=7618808
phhusson https://forum.xda-developers.com/member.php?u=1915408
gabrielfrias https://forum.xda-developers.com/member.php?u=4661848
ToddNachste https://forum.xda-developers.com/member.php?u=10721267
all health! Have a good mood! happiness!
p.s. IMPORTANT NOTE! start flashing the phone from a working state. that is, when the phone was launched at least once, there is a mark on the unlocked bootloader in the developer's menu. if you start the firmware immediately after resetting to the factory state, it is more likely that you will get an error about a locked bootloader, even if it is unlocked.
also remember, your firmware and kernel file may be damaged along the way. just download again.
p.p.s. The firmware contains 139apk including system (14apk user), at your discretion, disconnect / replace. in a 6/128 phone, firmware takes 8% free 117 gigabytes.
in native stock ~ 500apk%)
p.p.p.s. Before asking questions, look at the topic and header https://forum.xda-developers.com/galaxy-a51/how-to/galaxy-a51-root-unlock-bootloader-flash-t4053065, perhaps this has already been discussed. Thank you.
p.p.p.p.s. The firmware was created for personal use and is not laid out for tests and reviews. use if you need a clean android.
Click to expand...
Click to collapse
I will try this today, thanks!
Can you clarify what's the difference between the first package (AOSP vanilla), and the second one, which is smaller? Are these the same pieces indicated on gabrielfrias 's post?

rodrigofd said:
difference
Click to expand...
Click to collapse
first link
1) only firmware without zip is just a .tar archive
second link
2) zip archive - A51 AOSP firmware (as in the first link), kernel, original AOSP vanilla, 7z, lz4, otatools, simg2img, odin, all links and descriptions for all these tools. recommendations for battery calibration (forgot to translate - put it in the translator ) links and description to the original Samsung firmware, instructions for unlocking the bootloader (again you need the translator. !corrected! -> posted with the translation in the first post ) in general, everything that was used for creation and result. except for native Samsung firmware since its weight is large
with respect. be happy!

is super.img just renamed from the phhusson AOSP imgs? or is it a modified system image?

Is it possible to install and use samsung pay with this rom?
will knox be tripped?
thanks

Is the NoForcedEnforce boot image necessary for GSIs to boot, or does it only make root available?
I'm trying to boot GSIs on A51 5G (different hardware - just using this thread as a reference). Rooting via Magisk is straightforward, but when it comes to GSIs I get stuck in a boot animation loop. Looking around for some tips.
Ignore, booted AOSP just fine.

ESTIMULO said:
Is it possible to install and use samsung pay with this rom?
will knox be tripped?
thanks
Click to expand...
Click to collapse
I think a rooted system or modded system cannot use any "pay" or banking apps, thus it detect it's a third-party OS and will be prohibit sir

As you say is not possible to install in 3BTD4 original ROM (i already try it), so I installed the recomended THL original ROM from sammobile with odin (no errors), i finished the setup procces and activate USB debug again but it fail when i try to install your vanilla rom with odin at the end of the flashing process.
Can you help me please?
I really need a knox off rom to activate multi user profiles.
Thanks

this is the kernel for the U2 bootloader, not stable work on U3 for GSI.
i need patched kernel U3, becouse not work on my GSI ROM
Tested Please: Havoc-OS 3.8
need region SER, firmaware A515FXXU3BTD4
Download: https://yadi.sk/d/a4csxZGS59MVnQ

ive done all those steps mind you ive fully Rooted my phone in this process even replaced orignal md5 images with the AOSP ROM nup doesnt boot consistant reboots

but
i have a problem with <Phone is runing unofficial sofware > somebody help me plz

kooala94 said:
i have a problem with <Phone is runing unofficial sofware > somebody help me plz
Click to expand...
Click to collapse
From where you get that? And, maybe because you have root?

I have bootloader unlock without root when i startup Phone is restarting On Phone is running unofficial software plz help

kooala94 said:
I have bootloader unlock without root when i startup Phone is restarting On Phone is running unofficial software plz help
Click to expand...
Click to collapse
Somebody can help me What next?

only blabla discussion here...no samsuck user didnt tell us if that guide work or not! ...sooooo

firmware cant be downgraded so cant install this android...if exist any solution ...

Did anybody unlock the bootloader and root the unit?

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

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

Can the user unlock the bootloader then?

Haven't tried it, but it should be possible

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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