That statement is about as ambiguous as any I've seen posted. Mind giving a hint as what it was you tried?I tried, but it's not working. I'm stuck in download mode and it says invalid recovery.
I tried, but it's not working. I'm stuck in download mode and it says invalid recovery
What worked for me was flashing stock firmware and starting over. But I'm still on Pie; I could not root Android 10 using any method and not on custom ROM. For whatever reason, on this device KG State will go back to prenormal (and give you 1 of 3 error messages) if you don't go through the full setup and connect to internet everytime you reboot to system. You will need to check it in download mode before flashing anything & do the 7 day software update check thing to get it to checking if it reverts. Also still on magisk 19.3. Still trying to get 20.4 & 21.0 to worked based on posts here and in github, but no luck.
Karim Kahale
Senior Member
Odin just hangs at magisk_patched.img when I flash boot.img md5. Can you please provide some help?
Thanks a lot.
That statement is about as ambiguous as any I've seen posted. Mind giving a hint as what it was you tried?
Sorry yes of cause.
I successfully
- unlocked bootloader
- installed TWRP
- unencrypted partitions
- installed Magisk
- patched AP
after installing patched img. with Odin, no luck
stuck in bootloop
Sorry yes of cause.
I successfully
- unlocked bootloader
- installed TWRP
- unencrypted partitions
- installed Magisk
- patched AP
after installing patched img. with Odin, no luck
stuck in bootloop
What file did you specify in the AP slot in Odin? The TAR file "magisk_patched.tar"? Or an IMG file you extracted from magisk_patched.tar?
The opening post of the thread says you don't need to use Odin to install Magisk, you can use TWRP. That post does say you have to use Odin once, to flash the stock ROM.
- at first I extracted boot.img.lz4 used lz4 to change to boot.img patched that in magisk manager and installed it with Odin -> no luck
- then I patched the whole AP_T510XXU3BTH4....tar.md5 with magisk manager and installed with Odin -> no luck
(here the magisk_patched.tar has 3 changed files: boot.img.lz4 -> boot.img; recovery.img.lz4 -> recovery.img and vbmeta.img.lz4 -> vbmeta.img)
Somewhere I have seen to change all files in the AP to .img files, but I have not tried that jet.
Almost 2021 and People still get stuck following this tutorial. Is there any up to date guide for t510 and Android 10 ?
Look at the position of the OEM Enable switch. If it is greyed out, it is probably because it is already enabled. And you don't need it to unlock the bootloader anyway. All the OEM Enable does is turn off the FRP lock and all that lock does is require you to put in your Google Account info after a Factory Reset. If you don't recall your Google Account info, just add another account, write down the info, then delete the old account.
It sounds like what you might be dealing with is the RMM lock. There are tricks around it, but it can be difficult as there's lots to know. You can learn all about it here:
[GUIDE][17.06.2019] RMM/KG bypass - Root/Install TWRP on Exynos Samsung after 2018
UPDATE 17.06.2019 - NEW RMM/KG bypass patch UPDATE 23.02.2019 - Pie and more Please take some time and read carefully the whole post. I am not and i won`t be responsable for anything. Disclaimer I am not responsible for bricked devices, dead...
forum.xda-developers.com
After resolving RMM/KG lock, why go back to pie? Flash stock Android 10, matching versions. If you want the true stock firmware with T510XXU3BTH4, search for it at once of the big hosting sites:
If you're more interested in convenience, hanspampel has provided a stock rom based on December 2020's security update with a few modifications, and it's compatible with BTH4.
To root the device and eventually flash custom ROMs or GSIs download some.
Start by downloading the matching version of TWRP made by Magendanz:
Then download one of these custom roms, also by Magendanz, choosing from based on AOSP or LineageOS.
Or you could download an unofficial version of LineageOS, which'll also do the trick.
After you'll be able to flash to one of many GSIs available. Here are a couple I liked:
After you load these files to your external SD, backup any data on the device; rooting and flashing is going to wipe it.
- Enable dev options, check OEM unlock, USB debugging, and change USB configuration to file transfer. Don't worry, it'll still charge. Power off.
- Hold
VolUp+VolDownbuttons and plug USB to PC.
- Follow the directions to unlock bootloader and continue to download mode.
- Open Odin 3.14.4 on PC, untick auto-reboot option, flash TWRP in AP slot.
- Reboot your device to recovery without letting it boot to system.
Important: do not let it boot to system.
- HoldVolDown+Powerfor 7 seconds to reboot.
- Then holdVolUp+Powerduring reboot to enter TWRP.
- You can let go when you see the bootsplash.
- Allow modifications to system, make sure it's mounted, and install RMM_Bypass_v3_corsicanu.zip to be free from RMM/KG lockstate.
- Don't reboot.
*** Restart here when finished to try other ROMs and GSIs. ***
- Install multidisabler-samsung-2.6.zip.
- Perform
Wipe > Factory Reset.
- Select
Install > Install Zipand choose NexusAQ or Nexus LQ.
- Install Disable_Dm-Verity_ForceEncrypt_Latest.zip.
- Reboot and after completing any setup wizards, open Magisk Manager, select install Magisk, and choose the direct installation method, rebooting when complete.
You will now have a rooted, SAR tablet and you can simply wipe everything and install new ROMs on without (reasonable) worry over nasty lockouts or having to reroot again.
I know there are guides all over the place already, but I wrote this anyway 'cause my task saliency is dead and for reference cause I saw somebody complaining in another thread that there's nothing up-to-date.
Last edited:
Many thanks to everyone who contributed to this process and the various guides/tutorials/explainers. I've used guidance from XDA to root every device I've had since the Droid X. (Still have that phone, too!)
In case anyone else gets stuck on the "SAMSUNG" boot screen after rooting (not the "powered by Android" one, but the one after that), just wait a while. I got stuck on this screen and thought I'd made a mistake, so I redid the whole process three or four times and kept getting frustrated. The last time, I decided to just keep it plugged in and wait. About 15-20 minutes later, the tablet rebooted and finally loaded the system correctly. Hope this helps someone in the future!
In case anyone else gets stuck on the "SAMSUNG" boot screen after rooting (not the "powered by Android" one, but the one after that), just wait a while. I got stuck on this screen and thought I'd made a mistake, so I redid the whole process three or four times and kept getting frustrated. The last time, I decided to just keep it plugged in and wait. About 15-20 minutes later, the tablet rebooted and finally loaded the system correctly. Hope this helps someone in the future!
Everything works fine up to this point. When I try to install RMM_Bypass_v3 it gives the message
-Mounting /system ...
Failed! Can't mount /system, aborting!
How do I make the system mountable? Did I miss something?
you ever work this out? i am getting the same error.
"Only official released binaries are allowed to be flashed (Recovery)"
BL is unlocked. I too get the warning on boot saying that it is unlocked and when i go into DEV settings it says "Bootloader is already unlocked" though cannot flash TWRP..
I was on BTK1 and had to downgrade to BTH4.. maybe the downgrade only worked on the ROM and not on the Recovery/Bootloader hence it may not take the BTH4 based TWRP??
Does that make sense??
Last edited:
actually this kinda worked. i flashed your TWRP and it worked. though Recovery was now corrupt and coming up with an "Invalid" footer error.. though with the corrupt recovery in place it now let me flash the TWRP from the #1 post!! yay! up and running!
Guess #1
The system reboot after flashing TWRP.
Flashing TWRP disables something that allows you to mount the system. But if you let the system boot first instead of booting to TWRP, then the system re-enables the something. If this was the mistake, please note that bold and underlined words were used to highlight importance.
Guess #2
When you enter TWRP it asks you to swipe to allow modifications to the system. You must choose this option. Before going any further once you do, check TWRP's settings menu. There is an option in there that unmounts system before installs which might be trolling you.
The instruction to not boot to system applies to flashing TWRP from a stock ROM. If you do boot to system instead of recovery, the stock ROM will just rewrite the stock recovery over TWRP.Guess #1
The system reboot after flashing TWRP.
Flashing TWRP disables something that allows you to mount the system. But if you let the system boot first instead of booting to TWRP, then the system re-enables the something. If this was the mistake, please note that bold and underlined words were used to highlight importance.
Guess #2
When you enter TWRP it asks you to swipe to allow modifications to the system. You must choose this option. Before going any further once you do, check TWRP's settings menu. There is an option in there that unmounts system before installs which might be trolling you.
I tried, but it's not working. I'm stuck in download mode and it says invalid recovery
I had the same issue. Once you have the invalid recovery you can then flash the older twrp via Odin and it accepts it
Just got my hands on my tablet, and yeah I just googled and found this source of guides - though it is old. I was wondering if the steps still apply to the current tablet on the latest firmware/etc? (Current software info as of Feb 7th 2021) I was thinking of grabbing one of the roms in this forum. (Was eyeing this one since it's recent, and the customization in it looks good.) I haven't messed with rooting/flashing/etc in the longest of times so I'm real rusty - so any guides and such that I can pointed to would be appreciated!
The latest ROM for the T510 is the Nexus stock ROM based on Android 11. I think you need to downgrade from the current stock ROM to the previous one ending BTK1 instead of BUA1. But the first thing you have to do is unlock the bootloader and the steps to do that haven't changed.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
16The purpose of this thread is to have one post with links to all of the following guides:
Unlock Bootloader by @mingkee
TWRP Recovery by @Magendanz
Custom ROM Nexus Stock by @Magendanz - current release is SM-T510 only
Custom ROM LineageOS 16.0 by @Magendanz - SM-T510 only
All credit to @Magendanz and @mingkee for those.
Below are my own observations which supplement but do not replace the guides above. The original posts includes important information not quoted below. You need to read the relevant guides above (depending on what you want to do), and you may get some additional benefit from reading my thoughts below before following the guides above.
***Contents- Overview
- Downloads
- Buttons
- Unlock Bootloader
- Rooting
- How to use Odin
***OverviewTo root your device you need to first install the TWRP recovery. @Magendanz includes TWRP in his ROMs, so you have two options, TWRP without custom ROM, or TWRP with custom ROM.
To be able to install a ROM or recovery you first need to unlock your bootloader.
WARNING - take note of the kernel version of the custom ROM or TWRP you intend to use, e.g. T510XXU2ASI4. Newer bootloader releases will sometimes prevent downgrading, so if you flash a firmware/ROM/TWRP with a later kernel version you may not be able to flash your desired custom ROM without problems, or flashing an older version than you are currently running may trigger anti-rollback mechanisms. Magendanz suggests matching the version exactly.
There are then two paths:
Original ROM:
- Read the TWRP instructions
- Download any zip you plan to flash (install) from TWRP (e.g. Multi-disable and Magisk) and save to your sdcard. Internal memory will be wiped (formatted) as a necessary step in installing TWRP (if you follow the instructions correctly). Note that the folder /sdcard is part of the devices internal memory, your actual sdcard data can be found in something like /storage/ABCD-1234 in Android, or external_sd in TWRP.
- Unlock Bootloader - Click to see original post:
- Install TWRP recovery .tar.md5 file via Odin by following the TWRP instructions.
Click to see instructions from the TWRP OP - - [Optional] Install Magisk to get root - see Rooting section below
Don't forget to install Multi-disabler before doing Format Data! (as described in the guide) - In TWRP tap Install then select the Multi-disabler zip file.
Custom ROM [Allow several hours for the custom ROM download]:
- Read the custom ROM instructions: Nexus Stock / LineageOS 16.0
- Download any zip you plan to flash (install) from TWRP (e.g. Magisk) and save to your sdcard. Internal memory will be wiped as a necessary step in installing TWRP (if you follow the instructions correctly). Note that the folder /sdcard is part of the devices internal memory, your actual sdcard data can be found in something like /storage/ABCD-1234 in Android, or external_sd in TWRP.
- Unlock Bootloader - Click to see original post:
- Install custom ROM .tar.md5 file (which includes TWRP) via Odin, by following the custom ROM instructions.
Click for instructions from OP for Nexus Stock -
Click for instructions from OP for LineageOS 16.0 -
Note that "wipe data" means Wipe -> Format Data
- [Optional] Install Magisk to get root - see Rooting section below
Some users have reported getting stuck on the boot animation after a dirty flash, I don't know if that still happens with the latest versions of @Magendanz's ROMs. If it does the solution is to boot into recovery and flash Multi-disabler.
For TWRP versions before v3.3.1-5 you MUST format the encrypted data partition after flashing TWRP or TWRP will hang on the splash screen. For later versions of TWRP you should format the encrypted data partition after flashing TWRP so that TWRP can access the data partition.
You can use TWRP to flash zip files, e.g. to install newer versions of TWRP itself, or custom ROM zips, as follows:
1. Download the zip file
2. Boot into Recovery
3. Install -> Select the TWRP zip file
4. Reboot to System
You *cannot* use TWRP to flash tar.md5 files, and you must use Odin at least once to get TWRP installed in the first place.
***DownloadsYou may not need ALL of these downloads, this is just a handy list of some of the downloads mentioned in the guides
Samsung Smart Switch (for USB drivers)
Magisk - Download Latest Stable zip file to flash in TWRP (see Rooting below) and Latest Magisk Manager to install as an app
Odin
Multi-disabler (required by TWRP only tar.md5)
Firmwares SM-T510 SM-T515 - allow several hours, at least, for the firmware downloads to complete
WARNING - take note of the kernel version of the custom ROM you intend to use, e.g. T510XXU2ASI4 and your current version (Settings | About tablet). Newer bootloader releases will sometimes prevent downgrading, so if you flash a firmware with a later kernel version you may not be able to flash your desired custom ROM without problems, or flashing an older version than you are currently running may trigger anti-rollback mechanisms. Magendanz suggests matching the version exactly.
***Buttons- Power On: Hold the Power button for 3 seconds
- Boot to Recovery (Before unlocking bootloader) Power On and Press and hold Power and Volume Up until you see Recovery running.
- Boot to Recovery (After unlocking bootloader) Power On and then press Power and Volume Up as soon as you see the unlocked bootloader warning. No need to hold.
- Boot to Download: Press and hold Volume Up and Volume Down and connect to computer with USB cable.
***Unlock BootloaderClick to see Unlock Bootloader original post...
After unlocking the bootloader every time you turn the device on a warning about the bootloader being unlocked will appear for ten seconds, unless you dismiss it by pressing the power button.
If you are holding the Power button and Volume Up to boot into recovery this warning screen will flash on and off briefly, at which point you can stop holding down the buttons. Recovery will start a few seconds later.
***RootingRoot can be achieved by flashing Magisk in TWRP (you also need to install the Magisk Manager app). From Magisk 19.3 onwards there is no longer a need to use Magisk Manager to patch a tar.md5 file or anything like that.
You can even install Magisk the first time TWRP runs after flashing one of @Magendanz's tar.md5 files in Odin.
To do so follow @Magendanz's guide up to the point where you have Factory Reset/Wiped Data in TWRP then:
1. Reboot to Recovery
2. Install -> Select the Magisk zip file
3. Reboot to System
4. Install Magisk Manager
Otherwise you can start by installing the Magisk Manager app at any time.
Note: You will need to re-install Magisk after a TWRP update.
***How to use OdinOdin is a Windows tool for firmware flashing on Samsung devices via USB. Odin can be used to flash firmware, kernels, recoveries or ROMs to your device.
* Firmware zip (or rar) files need to be extracted and then install via Odin. Flashable zip files (e.g. new versions of TWRP or custom ROMs) can only be flashed from TWRP, not Odin, though you need to flash a TWRP tar.md5 file using Odin in the first place *
Preparing the device
- Charge the device to at least 80%.
- Bootloader unlocked
- In developer options, turn USB debugging on. Click on Build number in Settings several times until you see the toast notification "You are now a developer". Go to Developer Options and turn on the USB debugging option.
- In the stock ROM Build number can be found here: Settings | About Tablet | Software Information and the "Developer Options" menu item appears below About Tablet in the main Settings screen.
- The locations may be different in custom ROMs. In the Nexus based ROM the locations are Settings | About phone for Build number, and System | Advanced for Developer options
- Turn off the phone, hold down the Volumn Up and Volume Down buttons and connect the device to the computer with a USB cable (preferably the cable that came with the device). A warning will appear saying "A custom OS can cause critical problems in phone and installed applications".
- Press the Volume Up button briefly to continue.
The device is now in Download mode.
Install Odin version 3.13.3.
When you run it a dialog will pop up in English and Chinese. Click OK.
The Odin window looks like this:
Above ID:COM on the left is the progress bar, below ID:COM is the connection indicator which changes colour (and shows the COM id) when your device is connected in Download mode.
Below that is the "Log" tab which gives verbose output showing what's happening. Normally you will not need to go near the Option or Pit tabs.
There are four buttons in the middle of the screen corresponding to the types of file that you can flash: BL (boot loader), AP (Application Processor, PDA), CP (Core Processor, phone/modem), CSC (Consumer Software Customization)
Depending on what you are flashing you will need to load one or more files. To load each file type click on the corresponding button and select the file to be flashed.
Odin will show the following in the "Log" while the file is being processed:
For AP_ files this can take some time, during which the button will remain greyed out. When the file has loaded the "Log" will say:Code:<OSM> Enter CS for MD5 <OSM> Check MD5... Do not unplug the cable... <OSM> Please wait...
... the button will be enabled again, the text field beside the button will be filled with the fullpath of the selected file, and the checkbox next to the button ticked.Code:<OSM> Checking MD5 finished Successfully... <OSM> Leaving CS...
@Magendanz's TWRP and ROM files are both single files flashed to AP, so just click the AP button and the select the tar.md5 file.
If you are flashing firmware ( e.g. https://samfrew.com/model/SM-T510/ ) unzip the download into separate files and load each with the correspong button. The filenames begin with BL_..., AL_... etc so you'll know which is which.
There will be both a CSC_ and HOME_CSC_ file. You could flash HOME_CSC_ to keep your device's settings and data but normally you should use CSC_ for a clean install. If you have an SM-T515 then you'll have a CP_ file too, but if you have a SM-T510 then your firmware will not have a CP_ file because that's for the phone (SM-T510 is wifi only), so just leave CP alone, only load BL, AP and CSC.
Verify that your device is connected in download mode. The box below ID:COM should show the COM id of the connected device and there should be a line in the "log" saying something like <ID:0/008> Added!!
Click Start to flash the selected files. DO NOT UNPLUG THE CABLE UNTIL THE PROCESS IS COMPLETE. You can follow the progress in Odin and on the Download screen on your device. To flash a ROM or firmware will take several minutes.
If you are flashing one of @Magendanz's tar.md5 files then your device will reboot into TWRP once the install is complete. At that point continue following @Magendanz's guide.
Note: You will need to turn on USB debugging again after flashing firmware, or a clean install of a ROM, before you can use Odin to flash again. Also check that OEM unlock is still turned on.3I believe a critical issue is being missed in this process, and that is the T510 doesn't have a ramdisk available for boot, so Magisk must be installed to the recovery partition. Below is a screenshot of Magisk Manager data from my own tablet:
And per the Magisk installation instructions:
In order to boot into system with active Magisk, one has to essentially boot into recovery. From the Magisk in Recovery section (Bixby button references can be ignored):
I can understand now why John Wu was spitting nails mad when Google switched to dynamic partitions with system-as-root: it completely effs up the architecture for rooting with Magisk.
I don't know why Google and manufacturers persist in making it messy to nigh-impossible for end users--who desire to do so--to have full control of their own devices. Stupid. Just stupid.
Usunoro...
On the positive side, I hope this helps everyone trying to root their T510 tablets, and explains the weirdness people may have encountered.
(P.S. Since hardware attestation is used on the T510, SafetyNet won't pass, no matter what. There aren't any modules that can address this, given that hardware is being used for the evaluation. Another baka change! Also, I'm sticking with Pie since I can't stand Scoped Storage. Can't. Stand. It.)
Fur and Purrs --
--
King Cheetah3* * * REMINDER * * *
Please remember per Forum Rules, warez (like lucky patcher) is prohibited from being shared, linked, or encouraged.
...........................
6. Do not post or request warez.
If a piece of software requires you to pay to use it, then pay for it. We do not accept warez nor do we permit members to request, post, promote or describe ways in which warez, cracks, serial codes or other means of avoiding payment, can be obtained or used. This is a site of developers, i.e. the sort of people who create such software. When you cheat a software developer, you cheat us as a community.
...........................
All comments that violate the rules on warez will be deleted.
If you're going to steal the work of others, please don't post about it in Xda forums.
Thanks for everyone's cooperation.2
Check the Magisk version against posts in the Magisk thread. There was a point where Magisk reported SafetyNet test failed, but it was Magisk not getting a valid result from Google -- SafetyNet was passing, but Magisk did not know that. Problem corrected in later version of Magisk.2
After resolving RMM/KG lock, why go back to pie? Flash stock Android 10, matching versions. If you want the true stock firmware with T510XXU3BTH4, search for it at once of the big hosting sites:
If you're more interested in convenience, hanspampel has provided a stock rom based on December 2020's security update with a few modifications, and it's compatible with BTH4.
To root the device and eventually flash custom ROMs or GSIs download some.
Start by downloading the matching version of TWRP made by Magendanz:
Then download one of these custom roms, also by Magendanz, choosing from based on AOSP or LineageOS.
Or you could download an unofficial version of LineageOS, which'll also do the trick.
After you'll be able to flash to one of many GSIs available. Here are a couple I liked:
After you load these files to your external SD, backup any data on the device; rooting and flashing is going to wipe it.
- Enable dev options, check OEM unlock, USB debugging, and change USB configuration to file transfer. Don't worry, it'll still charge. Power off.
- Hold
VolUp+VolDownbuttons and plug USB to PC.
- Follow the directions to unlock bootloader and continue to download mode.
- Open Odin 3.14.4 on PC, untick auto-reboot option, flash TWRP in AP slot.
- Reboot your device to recovery without letting it boot to system.
Important: do not let it boot to system.
- HoldVolDown+Powerfor 7 seconds to reboot.
- Then holdVolUp+Powerduring reboot to enter TWRP.
- You can let go when you see the bootsplash.
- Allow modifications to system, make sure it's mounted, and install RMM_Bypass_v3_corsicanu.zip to be free from RMM/KG lockstate.
- Don't reboot.
*** Restart here when finished to try other ROMs and GSIs. ***
- Install multidisabler-samsung-2.6.zip.
- Perform
Wipe > Factory Reset.
- Select
Install > Install Zipand choose NexusAQ or Nexus LQ.
- Install Disable_Dm-Verity_ForceEncrypt_Latest.zip.
- Reboot and after completing any setup wizards, open Magisk Manager, select install Magisk, and choose the direct installation method, rebooting when complete.
You will now have a rooted, SAR tablet and you can simply wipe everything and install new ROMs on without (reasonable) worry over nasty lockouts or having to reroot again.
I know there are guides all over the place already, but I wrote this anyway 'cause my task saliency is dead and for reference cause I saw somebody complaining in another thread that there's nothing up-to-date.
