Database Develop

2.3.6 to 4.1 , help

Hi,
Ive just bought a used Galaxy Note running Stock 2.3.6 (N7000XXLC1 Kernel an N7000XXLB2 baseband) and want to put the latest jellybean rom on.
Ive read through lots of threads about the brick warning and so on, i just want to know how to go from 2.3.6 and have it rooted and cwm on and the latest 4.1 leak or a modified 4.1
Could somebody please tell me the steps to do it as dont want to brick it and this 2.3.6 is rubbish
Matt

Hello!
I've rooted my Note like this:
#1
Get the original software (like N7000XXLRU - the file is 914Mb and it is a *.md5 file. ) and odin (Odin3 v1.87), install it in odin...how?
Open odin and put the file in PDA.
Option in odin leave alone (Auto Reboot & F. Reset Time; are selected)
Put Note in download mode: Volume Down Key + Home Key + Power Key; then Volume up key to continue
Connect the phone to computer
Odin recognize the phone and you will see it on COM port
Click Start
After several minutes the phone will turn on.
Now you have a original sw on your phone, and believe me this sw is GREAT...but if you want more...
#2
Root you phone
Described in this link (http://forum.xda-developers.com/showthread.php?t=1329360)
I used ''1A.Root + safe kernel + advance recovery''
Just read carefully (will write it down)
Visit this thread
http://forum.xda-developers.com/showthread.php?t=1901191
And download kernel in zip format according ROM you are having on device (just look for XXLRU-VDI; PhilZ-cwm6 v3.5 with CWM 6.0.1.8)
Copy downloaded file to Ext SD card to root directory (or any folder you make; I have ''A_ROOT'' for this things)
Reboot into recovery (Volume Up Key + Home Button + Power Key)
Select install(update) zip from ext SD card (Install zip >> Choose zip from sdcard; and click on the *.zip file)
select '[your downloaded kerenel].zip' which you have copied to Ext card above
Reboot device
Now you will have Root + safe kernel
And your phone is rooted now. You can have all the programs that work only when your phone is rooted (Titanium Backup, Root Uninstaller, Root Browser Lite, ...)
#3
Your phone is now ready to install all Android Development ROMs
Read each post ''How to flash'' it is easy
For instance I like stock rom and love 4.1.2, so i have sw from http://forum.xda-developers.com/showthread.php?t=1970626
Example:
Save *.zip on your SD/EXT Card (Ultimate N7000 XXLSA JellyBean 4.1.2 v5)
Restart in CWMR (Volume Up Key + Home Button + Power Key)
Be sure you're on SAFE KERNEL, then you can wipe (jes you are - on PhilZ-cwm6)
Full wipe /data/factory reset /cache and dalvik (dalvik is in advanced option)
Flash the ROM (Install zip >> Choose zip from sdcard; and click on the *.zip file)
Wait some minute until your phone boot!
You are done. That's all.
I've never had any problems with any of the ROMs. You can do the #3 1000 times and nothing will go wrong. Just remember to do a back up in CWM, when you have a rom that works great for you and you like. So if anything happens and you phone is stuck in ''samsung'' sing, you can go in CMW and restore it.
I hope it helps and I didn't forget anything.

Thanks so much for posting. I followed all the instructions and it worked fine. I have however gone and installed a 4.0.4 rom after using 4.1 for a bit and finding it too juddery.
Thanks again
Matt

No problem.
You can wait for the official firmware release and then everything will work 100%.

Since he didnt i hit thanks
Sent from my Amazon Kindle Fire using Tapatalk 2

Have hit thanks now , forgot!

ANDROID PIE Snapdragon (no root)

!!!!!! KEEP IN MIND THAT THIS WILL RESTORE YOUR FACTORY MOBILE, PLEASE MAKE BACKUP SECURITY !!!!!!!
1. Download and flash by odin 3.13.1 the ROM N960USQS1ARI5 oreo 8.1.0.zip (if you already have this base installed in your phone go to step 2)
2. Download the file PIE and save it to the SD card of your mobile.
September patch OTA-N960USQS1ARI5-to-U1CRJ3-UP.zip (Android PIE) 1.6 GB
3. Turn off and start the phone in recovery mode.
4. Using the volume keys, select the option: "Apply update from the SD card", select the file and press the power button and wait for it to finish. Patience will take about 10 minutes
* enjoy!

This is a duplicate thread

mweinbach said:
This is a duplicate thread
Click to expand...
Click to collapse
Report it then...
/CK

Duplicate --> Serves no purpose --> Closed.

How to upgrade without losing Root/Twrp ?

First of all, a big thankx to S10+ Thread members who've helped me to root and install twrp on the device. Without your help i couldn't have done it.
Secondly, i've installed the December security patch firmware. Now its been rooted with magisk and a twrp installed. So i was thinking to upgrade to January patch. But i am afraid, it would affect the rooted state or replace the twrp.
Is there any way to upgrade without losing current status and data on the device ?

No easy way. Pre patched firmware then flash pre patched twrp

but no TWRP
sunmughans said:
Is there any way to upgrade without losing current status and data on the device ?
Click to expand...
Click to collapse
Firmware updates and keeping your data, for phones Magisk rooted without TWRP.
https://forum.xda-developers.com/showpost.php?p=80076303&postcount=1436
Just download new firmware, copy the AP file of the new firmware to your phone.
Open Magisk Manager, ensure Magisk is up to date, if not, update it.
When Magisk is up to date, if you have any Magisk Modules running, go into Modules and disable them (no need to uninstall them). Then reboot and go back into Magisk Manager.
Hit the _top_ INSTALL, select INSTALL again then select 'Select and Patch a File'
Locate the new AP file from your new firmware and patch it. Then copy the *magisk_patched.tar* (find it in /sdcard/Download - do not forget to delete it here after everything is done; otherwise Magisk will choke on the next patch) back to your computer, preferably with adb pull to minimize corruption during transfer.
Power off phone and reboot to *Download mode* (switch off, Vol-Down + Bixby and plug USB cable).
Open Odin 3.13.1 or later on your computer, and deselect Reboot under Options tab.
Now use the new magisk_patched file in the AP slot, the BL and CP from your new firmware into their respective slots and importantly *HOME_CSC* into the CSC slot.
Press start and let Odin do it's stuff.
When flashed, do not wipe.
Press and hold Vol-down and Power, when screen goes off, quickly change to Vol-up, Bixby button and Power.
As soon as screen appears, let go of all buttons.
Within moments without any further user intervention your phone will reboot into your updated Magisk rooted mode, data intact.
Just re-enable your previously disabled Magisk modules.
This is the original work of:
Last edited by @robbo1947; 2019-08-30 at 04:28.
(only copied here because this useful stuff is buried in a long thread - follow the link on the second line)
last edited by me 2019-10-05

DHGE said:
Firmware updates and keeping your data, for phones Magisk rooted without TWRP.
https://forum.xda-developers.com/showpost.php?p=80076303&postcount=1436
Just download new firmware, copy the AP file of the new firmware to your phone.
Open Magisk Manager, ensure Magisk is up to date, if not, update it.
When Magisk is up to date, if you have any Magisk Modules running, go into Modules and disable them (no need to uninstall them). Then reboot and go back into Magisk Manager.
Hit the _top_ INSTALL, select INSTALL again then select 'Select and Patch a File'
Locate the new AP file from your new firmware and patch it. Then copy the *magisk_patched.tar* (find it in /sdcard/Download - do not forget to delete it here after everything is done; otherwise Magisk will choke on the next patch) back to your computer, preferably with adb pull to minimize corruption during transfer.
Power off phone and reboot to *Download mode* (switch off, Vol-Down + Bixby and plug USB cable).
Open Odin 3.13.1 or later on your computer, and deselect Reboot under Options tab.
Now use the new magisk_patched file in the AP slot, the BL and CP from your new firmware into their respective slots and importantly *HOME_CSC* into the CSC slot.
Press start and let Odin do it's stuff.
When flashed, do not wipe.
Press and hold Vol-down and Power, when screen goes off, quickly change to Vol-up, Bixby button and Power.
As soon as screen appears, let go of all buttons.
Within moments without any further user intervention your phone will reboot into your updated Magisk rooted mode, data intact.
Just re-enable your previously disabled Magisk modules.
Last edited by @robbo1947; 2019-08-30 at 04:28.
last edited by me2019-10-05
Click to expand...
Click to collapse
Thank you so much bro! You really saved a lot of time. I will follow your instructions.

sunmughans said:
Thank you so much bro! You really saved a lot of time. I will follow your instructions.
Click to expand...
Click to collapse
Don't forget to thank me, I wrote the original instructions !!.
https://forum.xda-developers.com/ga...s10-series-t3918699/post80076303#post80076303

Did not work for me(root&twrp), phone is required to reset, however with backup, data can be restored. So backup your data before update.

DHGE said:
When flashed, do not wipe
Click to expand...
Click to collapse
what do you mean by that?

[Guide][SM-T500/T505] Galaxy Tab A7 10.4 - Unlock Bootloader & Root with Magisk

I recently purchased the Galaxy Tab A7 10.4 (released in 2020) and couldn't help but notice that there's no dedicated thread in the forums for unlocking the bootloader or rooting (Although, the method should be very similar to what is followed for the Tab 10.1 (2019)).
It's been quite some time since I published a tutorial on XDA. So, I decided to put up this comprehensive tutorial, hope it helps everyone who's looking for it. We will take the direct approach of rooting the tab by patching the AP firmware and flashing the patched AP through Odin.
/* I will be using the same images I prepared for the tutorial to be posted on my blog. Sorry that they have been watermarked, that is to prevent scrapers from stealing. It took me enough time to capture them and do some post-processing. */
Before we start, here's the obligatory disclaimer and warning:
Unlocking the bootloader will erase all the data on your tab, including all the data that's on the internal storage. So, make sure that you have taken a complete backup of all your important data.
Flashing a custom binary (such as Magisk patched TAR in this guide) will trip the KNOX counter. Your device's official warranty will be void once KNOX is tripped.
You will not be able to use apps and services like Secure Folder, Samsung Pass, and anything that relies on KNOX.
Although I have tried this on my Galaxy Tab A7 (SM-500) and can confirm that this works, I will not take any responsibility of any bricked/toasted devices. Make sure that you fully understand what you're doing and accept the consequences if anything goes wrong.
If you do land your tablet in trouble, feel free to ask, I shall try my best to help.
Click to expand...
Click to collapse
Update log
Updated on March 2, 2021
Added more info about the warranty. It seems like some users are still not aware of how KNOX affects the warranty. If you're getting into software modifications such as rooting, I expect you to have some prior knowledge about such things.
Redacted the part where you needed to change Magisk's update channel under Step #5. Not needed anymore as Magisk v21.x was released to the Stable channel in January 2021.
Replaced all instances of "Magisk Manager" with "Magisk App". Starting with Magisk v22, Magisk Manager is gone and merged with the core Magisk. It's now called the "Magisk App".
Click to expand...
Click to collapse
Requirements
Your Galaxy Tab A7 with SM-T500 or SM-T505 model number
A compatible USB-C cable
A Windows computer. (Odin only works on Windows. If you're using Linux or Mac, you could try Heimdall)
Instructions
Step 1: Enable OEM Unlocking
In order to unlock the bootloader, you must first enable the 'OEM Unlocking' toggle. This toggle resides inside the 'Developer options' screen, which is hidden by default on most Android devices.
First, enable 'Developer options' by going to 'Settings' > 'About tablet' > 'Software Information' and repeatedly tap on the 'Build number' section five times. If you have a lock screen security set, you will need to input your PIN/Password/Pattern when prompted.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Once you do this, you should see a toast notification on the bottom of the screen saying that "Developer mode has been enabled".
Once that is out of the way, go to 'Settings' > 'Developer options' and turn ON the toggle next to "OEM unlocking". You will instantly be prompted to enter your PIN/Password/Pattern, so do it. Then select "Enable" to allow OEM unlocking.
Note: If the OEM unlocking toggle is grayed out, make sure that you have connected the tablet to the internet first (via WiFi or mobile network, your choice).
Step 2: Unlock the Bootloader
Start by powering off your tablet completely. Then while holding the Volume Up and Volume Down keys together, connect it to your computer using the USB cable. This should take you to the bootloader screen (I call it that because logically that's what directs you to either Download Mode or Device Unlock Mode). Long-press the Volume Up key to enter the 'Device unlock mode'.
Your tab should now prompt you with a confirmation screen, so press the Volume Up key to confirm and unlock the bootloader.
Your Tab A7's bootloader is now unlocked and it should reboot automatically. You should also see a warning message right before the Samsung splash screen, just as shown in the picture below. Don't worry, it's completely normal. And no, there's no way to get rid of it (unless of course, you relock the bootloader).
The first boot after unlocking the bootloader could take some time (took around 3-4 minutes for me). So be patient.
Now that the bootloader is unlocked, let's verify it. Samsung introduced a new feature known as "VaultKeeper", which will automatically relock the bootloader if you do not perform this step.
After your tab boots, connect it to the internet. Then enable the Developer options as shown in step #1 and go to 'Settings' > 'Developer options'. The OEM unlocking toggle should be greyed out and say that the bootloader is already unlocked. Again, refer to the picture below.
Step 3: Download the firmware package
With the bootloader properly unlocked, you can begin with the rooting part. As I mentioned, we will be patching the AP firmware file via Magisk App, as instructed by John Wu in his installation guide on Github.
So, you will need to download the firmware package for the software version that's currently installed on your tab. This is very important, do not use an older firmware, as it will result in issues. You could of course use a newer firmware, which will update your tab at the same time as rooting it.
To verify your software version, you can go to 'Settings' > 'About tablet' > 'Software information' and check the "Build number". The latter half of the mentioned build number is your tab's software version, which in my case as shown in the picture below is: T500XXU1ATJ2. So, I will need to download the firmware package for "T500XXU1ATJ2" and in your case you should download the one corresponding to the info you see under 'Build number'.
Where to download? You could use online FW databases like SamMobile, Samfrew, etc. However, I would recommend using Frija or Samloader as they allow you to download the firmware directly from Samsung's Firmware Update Servers and without any speed caps. If you're operating on Windows, use Frija. On macOS/Linux, use Samloader.
Step 4: Extract the AP firmware and transfer it to your Tab A7
Once you have the ZIP package downloaded, you will need to extract it to get The extracted folder should contain the individual firmware files like BL, AP, CP (only for SM-T505 LTE variant), and CSC/HOME_CSC (in .tar.md5 file format).
The file you'll require is the AP firmware, which in my case is "AP_T500XXU1ATJ2_CL19362637_QB34980135_REV00_user_low_ship_MULTI_CERT_meta_RKEY_OS10.tar.md5". Again, in your case, the filename would be a bit different, but it should follow the same structure.
After extracting the AP firmware, connect your tab to the computer, enable File Transfer (MTP) mode on it, and copy over the AP firmware to your tab's internal storage. Copy it to the root directory, that is, outside all the folders as shown below. The location of the file doesn't matter, you can copy it anywhere, but I prefer this for easier access.
Step 5: Patch the AP firmware using Magisk App
Now's the time to patch the AP firmware. To do this, download the latest version of the Magisk app from the official Github releases page to your Tab A7. This will be an APK file. Once downloaded, install the APK file using your choice of file manager.
Warning about unofficial sources of Magisk: Magisk does not have any officially registered domain. If you Google for it, you will probably come across multiple websites that have the word "Magisk" in their domain URL. They are there to deceive the users, and often misinform users, especially those who are new to the scene.
John Wu, as well as XDA have previously warned the users from falling into these deceptive websites. The only official place to get Magisk is from Github.
Click to expand...
Click to collapse
You do not need to change Magisk's update channel to Beta anymore. Starting January 12, Magisk v21.x was pushed to the stable channel (default).
After installing, go to the app drawer and launch the Magisk Manager app. Before you start patching, you would want to change Magisk Manager's update channel to Public Beta. This is because Magisk's latest version (i.e. v21.0) is only available on the beta channel and hasn't been pushed to the stable channel yet (at least at the time of publishing this tutorial).
To do this, press the settings icon on the top-right, tap on "Update channel" and select "Beta". Then go back to the app's main screen. It should refresh and show you the latest version as v21.0.
Press the "Install" button and then "Select and Patch a File" from the list of available methods. This should open the file selector, so navigate to the internal storage and select the AP firmware you transferred during the previous step.
Once the file is selected, hit "LET'S GO" to start the patching process. This should take a minute or so because the AP firmware is quite a heavy file. Once it is done, the patched AP firmware with the filename "magisk_patched_xxxxx.tar" (where "xxxxx" is an arbitrary code) should be stored inside the "Download" folder of your tab's internal storage.
Step 6: Flash the Patched AP Firmware using Odin
The last step is to flash the patched AP firmware to your Galaxy Tab A7 and root it. For this, connect your tab to the computer over USB and copy the "magisk_patched.tar" file from the Download folder. Paste this patched AP firmware inside the firmware folder that was extracted during step #5, along with the rest of the firmware files (BL, CSC, etc). Disconnect it from the PC after transferring the file.
Now, boot your Tab A7 into Download Mode. Power it off, and connect it to the computer over USB while holding the Volume Up and Volume Down keys together. This should bring up the bootloader screen. Simply tap the Volume Up key once to enter Download Mode. Here's what the Download Mode on the Tab A7 looks like.
Next, download Odin v3.14.1 from this XDA thread (NOT the patched version, but the regular one) and extract the contents of the downloaded ZIP package. Then launch Odin on your computer by double-clicking the "Odin3 v3.14.1.exe" executable and click "Ok" when prompted. You should see the Odin interface on your computer screen now.
Odin should automatically recognize your tab in Download Mode and display the COM ID on the top-left.
Click the 'Options' tab and uncheck the 'Auto Reboot' option. This will prevent the tablet from being automatically restarted after the flash is complete.
Now, load the firmware files in the respective slots of Odin.
The BL firmware file (BL_T500/5XXXXXXX_xxxxxxxxxxx.tar.md5) goes to the "BL" slot
The CP firmware file (CP_T505XXXXXX_xxxxxxxxxxx.tar.md5) goes to the "CP" slot. Note that the CP firmware only applies to the Tab A7 LTE variant with the SM-T505 model number.
The HOME_CSC firmware file (HOME_CSC_OMC_ODM_T500/5XXXXXXX_xxxxxxxxx.tar.md5) goes to the "CSC" slot. We will not be using the regular CSC, as it will erase all the data. If you want to do that, feel free to use it.
And finally, the patched AP firmware file (magisk_patched.tar) goes to the "AP" slot.
Once the files are loaded in their respective slots, hit the "Start" button to flash them to your tab.
Note: While you could get away with just flashing the patched AP firmware alone, John recommends NOT doing it. Always flash the patched AP along with the rest of the firmware files like BL, CSC, etc.
Wait for the flash to finish. Once it is, you should see the 'PASS!' message in Odin. Like so:
You can now close the Odin window and disconnect your tab from the computer.
Step 7: Perform a Factory Reset
Once the flash is complete, you will need to manually boot your tablet into the stock recovery mode and do a factory reset. This is only mandatory during the initial rooting process, which is exactly what we are doing here.
To do this, hold the Volume Down and Power keys together for about 7 seconds. As soon as the screen turns off, release the Volume Down key and quickly hold the Volume Up key, while still holding the Power key. Keep holding the keys until you see the stock recovery screen.
You should now see the stock recovery screen with some device information in yellow color at the top. Like so:
Use the Volume keys to move the selector to 'Wipe data/factory reset' and hit the Power key to confirm the selection.
You will now see a confirmation prompt on the screen. Select 'Factory Data Reset' to confirm and finally perform a factory reset.
Once done, select the 'Reboot system now' option from the recovery's main menu. Your Tab A7 should now reboot may be more than once, so be patient.
We're not done yet. After booting, you will need to open the Magisk app from the app drawer and follow the on-screen instructions to replace the Magisk stub with the actual full application, and further complete the required setup when prompted by Magisk app.
Once this is done, your Tab A7 should reboot one last time and should be rooted thereafter.
Your Tab is Rooted!
You may now go ahead and start using root applications, install some modules, etc. Since v20.4, Magisk Hide has been disabled by default on new installations in light of the new hardware-backed SafetyNet attestation. So, to use banking/security, or any other sort of apps that may detect root, you will need to turn ON Magisk Hide from within the Magisk App settings.
Before you leave, there are a few key things you should note:
Unlike some other Samsung phones, you will not need to follow any complex button combinations to boot into the stock recovery. A normal reboot will always boot your Tab A7 into the rooted Magisk system. On the other hand, the regular Volume Up + Power key combo will get your tab into the stock recovery mode.
Second, if a new software update is rolled out, you will need to repeat the same process from step #4 all the way to step #7. When updating the FW, you can simply use the HOME_CSC instead of the regular CSC to prevent your data from being wiped. A backup should still be taken.
Click to expand...
Click to collapse
That's all from my side. If you run into any issues, feel free to post. Don't forget to share details like the software version your tab is on, the firmware package you downloaded and used, and of course your tab's complete model number.

Thank you for posting this! I bought a 2019 Tab A just before the A7 released and have been tempted to return it and pick up the A7 but wanted to make sure I could root it. How is the performance if this?

jserio said:
Thank you for posting this! I bought a 2019 Tab A just before the A7 released and have been tempted to return it and pick up the A7 but wanted to make sure I could root it. How is the performance if this?
Click to expand...
Click to collapse
I was really inclined to the Tab S6 Lite. But being honest, I wouldn't have used the SPen that much. So, I dropped it.
I saw Tab A 10.1 (2019), the one you're referring to, and it was a steal for the specs. The reviews were good too. But then the A7 was released, an upgraded model along the same lines. I like it very much. For a budget tab, it really delivers decent performance and a premium-ish design. And, great speakers I must say.
Unlocking and rooting were really fun and easy as well. Overally, it's a pretty darn good tab for the price.

Thanks for the guide, I've been undecided for days if I should pull the trigger or not and no info on rooting was one of the things that was making me hesitate.
The other one is 3gb of ram, how's your experience been so far? I don't play games on my phone/tablet so that's not an issue.

Gitah. said:
Thanks for the guide, I've been undecided for days if I should pull the trigger or not and no info on rooting was one of the things that was making me hesitate.
The other one is 3gb of ram, how's your experience been so far? I don't play games on my phone/tablet so that's not an issue.
Click to expand...
Click to collapse
You're welcome!
For me, 3GB of RAM is enough, of course given my usage. I usually use it for browsing and streaming only. Not much of a mobile gamer, use real consoles and PC for that, lol.
I like Samsung's One UI experience, compared to any other OEM skin (apart from OxygenOS). It's quite smooth IMO. Already removed the bloatware via ADB, might as well come with a guide for that.
It could however be different under heavy multi-tasking usage, like playing mobile FPS titles, etc. Couldn't tell on that.

storage problem
you can not move any app to the sdcard no option tried different formats as well tried app2sd pro creating a adaptable storage will work but you cant see the partition and you cant move apps back to the internal with out app corruption. terminal commands dont work cant edit system

You are a lifesaver, my friend. I just wanted to note for others that Frija did not work for me. It would only fetch a .zip.enc4 image for my SM-T500 (CSC is XAR). I am currently downloading the firmware from SamMobile to try. Magisk can't flash the file Frija get's for me, it needs to be .tar. Yes, I know it says zip but the file is extracted. Just a heads up for others out there! Also, have you flashed a different recovery for this tablet? And, if so, what image based on what model? TWRP and OrangeFox don't have an official image for the SM-T500. Thanks in advance!
DJ
UPDATE: the image from SamMobile was corrupt. Stuck me in a boot loop with a message about it not being offical Samsung software. Had to factory reset from recovery. This method is flawless, otherwise. Gonna try again with different firmware.

Hey guys. Followed the guide to a T (downloaded latest firmware using Friaj) and also flashed CSC (not home) so I could have a clean install. Magisk patched the file just fine. Odin flashed with no error but on first boot besides the usual "bootloader unlocked" error I get another one saying that custom binaries are installed and the tablet is locked. I cant seem to boot to download mode now. I can boot to the bootloader unlock screen but that's it. Any ideas?

Thanks, DJBhardwaj. Very good guide!
Just a note for European SM-T500 users: SafetyNet won't pass as magisk will return evalType: hardware. At least that's what I found in T500XXU2ATJ6. That's not a problem for me as the only app that requires SafetyNet that I use is Netflix and the issue can be fixed by installed a very legacy version of it, but I think people should be warned before tripping knox fuse

Cloudxddd said:
you can not move any app to the sdcard no option tried different formats as well tried app2sd pro creating a adaptable storage will work but you cant see the partition and you cant move apps back to the internal with out app corruption. terminal commands dont work cant edit system
Click to expand...
Click to collapse
I suppose Scoped Storage has some effect, not 100% sure. But I am really curious now. Going to dig in.

Dj89 said:
You are a lifesaver, my friend. I just wanted to note for others that Frija did not work for me. It would only fetch a .zip.enc4 image for my SM-T500 (CSC is XAR). I am currently downloading the firmware from SamMobile to try. Magisk can't flash the file Frija get's for me, it needs to be .tar. Yes, I know it says zip but the file is extracted. Just a heads up for others out there! Also, have you flashed a different recovery for this tablet? And, if so, what image based on what model? TWRP and OrangeFox don't have an official image for the SM-T500. Thanks in advance!
DJ
UPDATE: the image from SamMobile was corrupt. Stuck me in a boot loop with a message about it not being offical Samsung software. Had to factory reset from recovery. This method is flawless, otherwise. Gonna try again with different firmware.
Click to expand...
Click to collapse
Thanks for the kind words.
Frija, Samloader, SamFirm. All of those tools fetch the firmware from Samsung's Firmware Update Servers. These packages are encrypted as .zip.enc4 (for newer devices) or .zip.enc2 (mostly for old ones).
After downloading, the firmware package will automatically be decrypted and converted to a regular ZIP file, if you're using Frija or SamFirm. The ZIP file should contain the AP, CSC, and BL firmware TAR files.
I don't use custom recoveries anymore, but I was more than willing to try. Couldn't find anything for the Tab A7 (yet).

paziusss said:
Thanks, DJBhardwaj. Very good guide!
Just a note for European SM-T500 users: SafetyNet won't pass as magisk will return evalType: hardware. At least that's what I found in T500XXU2ATJ6. That's not a problem for me as the only app that requires SafetyNet that I use is Netflix and the issue can be fixed by installed a very legacy version of it, but I think people should be warned before tripping knox fuse
Click to expand...
Click to collapse
It's more likely to be unit-based. For example, my OnePlus 8 still hasn't been forced to hardware-backed attestation for SN. But my friend's unit (same model and region) has been.
Have you tried enabling Magisk Hide? It is disabled by default. Another thing to try is the Magisk Props module.

jserio said:
Hey guys. Followed the guide to a T (downloaded latest firmware using Friaj) and also flashed CSC (not home) so I could have a clean install. Magisk patched the file just fine. Odin flashed with no error but on first boot besides the usual "bootloader unlocked" error I get another one saying that custom binaries are installed and the tablet is locked. I can't seem to boot to download mode now. I can boot to the bootloader unlock screen but that's it. Any ideas?
Click to expand...
Click to collapse
Could you share a picture of the screen you're referring to?

DJBhardwaj said:
Thanks for the kind words.
Frija, Samloader, SamFirm. All of those tools fetch the firmware from Samsung's Firmware Update Servers. These packages are encrypted as .zip.enc4 (for newer devices) or .zip.enc2 (mostly for old ones).
After downloading, the firmware package will automatically be decrypted and converted to a regular ZIP file, if you're using Frija or SamFirm. The ZIP file should contain the AP, CSC, and BL firmware TAR files.
I don't use custom recoveries anymore, but I was more than willing to try. Couldn't find anything for the Tab A7 (yet).
Click to expand...
Click to collapse
Thanks for the info! I'll post an update later this week once I get it going! Take care and thanks again for posting this guide!

DJBhardwaj said:
Could you share a picture of the screen you're referring to?
Click to expand...
Click to collapse
Sorry for the late reply. I went through the process again and everything worked. It's possible the issue was either a) I used the newest fw to patch and flash or b) I didn't check to make sure "oem unlocking" was greed-out after unlocking it.
Any way to block updates? I prefer not to go through this each update? Hopefully we get twrp for this tablet. I live it compared to the 2019 A with its crappy one-sided speakers.

jserio said:
Sorry for the late reply. I went through the process again and everything worked. It's possible the issue was either a) I used the newest fw to patch and flash or b) I didn't check to make sure "oem unlocking" was greed-out after unlocking it.
Any way to block updates? I prefer not to go through this each update? Hopefully we get twrp for this tablet. I live it compared to the 2019 A with its crappy one-sided speakers.
Click to expand...
Click to collapse
That's great!
As for updates, I think there was a way by blocking the update services using Titanium. Might have to look it up again. I did that years ago. Yes, TWRP would be great for flashing ROMs and NANDroid backups.
I was going for the 10.1 earlier, didn't knew it had one-sided speakers.

I have a question... Unlocking the bootloader and rooting a device are mostly the first steps to a custom rom like lineageos . I find tons of threads for the SM-T510, but not the SM-T505.
Will there ever be a custom rom for the T505?

DJBhardwaj said:
I suppose Scoped Storage has some effect, not 100% sure. But I am really curious now. Going to dig in.
Click to expand...
Click to collapse
So it's impossible to move apps to sd even with root?

Any fixes to allow apps to be moved/installed on SD card? Can't root with work/UEM apps installed. Seems super wierd for a new tablet, is this a bug or should I return?

Allow apps to be moved/installed on SD card
ormefocus said:
Any fixes to allow apps to be moved/installed on SD card? Can't root with work/UEM apps installed. Seems super wierd for a new tablet, is this a bug or should I return?
Click to expand...
Click to collapse
Same here i tried on 2 different sd cards(SD- HD) format them from the tablet and no one app won't move to the sd card.
I turn on the develpoers options and i fount this option: Force allow apps on external(Makes any app eligible to be written to external storage regardless of manifest values) and i tried to donwload Asphal 9 and Gangster Vegas and 2 apps downloaded to the internal storage...
I chekt if the options to move apps is visable on this apps and its not.
If any one fine how to transfer apps to the sd card i will very thankful

Root Instructions for SM-T290 (Samsung Galaxy Tab A 8.0 2019)

Root Instructions for SM-T290 (Samsung Galaxy Tab A 8.0 2019)​
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Welcome! This is my first guide on XDA Developers. This will tell you how to root a Samsung Galaxy Tab A 8.0 2019, specially for the SM-T290 model of it. I hope you like it and it works! It has exactly 30 steps.
Disclaimer​
* Your warranty will or is now be void. It might already been void (if your warranty is over...)
* I'm not responsible for any damage to your device when following this guide. It's your choice to do it.
* If you still say it's my fault, I'll probably say that I had warned you.
Click to expand...
Click to collapse
UPDATE YOUR TABLET TO VERSION T290XXU3CVG3 AND NOT HIGHER!!!​Please update your tablet to the version listed above and NOT higher. Make sure it is fully upgraded to Android 11, so that you can use the better version of TWRP. BUT NOT HIGHER THAN THE VERSION ABOVE, AS THE DEVICE WILL LIKELY NEVER BE ABLE TO BE ROOTED AGAIN. Update by flashing T290XXU3CVG3 with Odin. Download the firmware for your country. Soon I might will update this guide so that TWRP will work on the latest firmware, but for now, DO NOT GO HIGHER THAN T290XXU3CVG3!!! If you have bootloader version 4, it is impossible to flash any of the stuff described here and your device won't be able to have a downgraded bootloader, making it currently impossible to flash any custom stuff when you have bootloader version 4!
MAKE A BACKUP!​Be sure to make a complete backup first of all important stuff you have! When you have TWRP (and likely also ROOT), you are able to make a COMPLETE backup of your tablet, including partitions like boot and data and allows apps with complete data to be restored, be sure to use this feature when you have installed TWRP.
Known issues​
Charging the device while it is powered off will power it on again. The device will always be on when charging.
Sometimes, when you wipe and/or format data, the storage space is seen as 8GB, while it has 32GB. You can find the fix here.
The battery may drain fast. If this is your case, check this fix.
You may get a black screen after you have flashed TWRP. This means that this method likely doesn't work for your device, because your device came with Android 10 instead. This means that the Android 9 bootloader doesn't work properly on this device. We know the device can be used by using screen mirroring from ADB, but we need more research.
Issue tracker​You can report issues here. This repository is used to report issues for all my XDA threads. You MUST add the label 'Root Instructions For SM-T290', so I know where to post this issue.
Instructions for ROOT​1. Power on your device.
2. Open the settings app.
3. Go to 'About device/phone/tablet'
4. Click on 'Software info'.
5. Tap on the build number for 7 times until a message pops up saying "You are now a developer!".
6. Go back to home menu of settings app and click on 'Developer options'.
7. Enable the OEM unlock switch.
Optional: Unlock the bootloader using the steps below, go through setup, enable developer options and check if the option is still enabled.
8. Turn your device off and reboot into download mode by plugging the device into a PC using an USB cable and holding Pwr+VolUp+VolDown after being plugged in.
9. Disable the OEM lock and enable bootloader by holding VolUp for 10 seconds and then follow the instructions.
10. After that, you should see a download icon saying (downloading...).
11. Download Odin Flash Tool 'Odin3-v3.14.4.zip' from the files below.
12. Extract the ZIP file.
13. Open the ODIN executable.
14. Connect your tablet with a micro-USB to USB-A adapter (Your charging cable).
15. Download TWRP recovery image by clicking here. It should work with any version on your tablet. (TWRP XDA Thread)
16. Go back to ODIN, click OK.
17. Go to 'options' tab.
18. Disable 'Auto Reboot'. (not required, keeping enabled may be needed if you can't install and/or use the device.)
19. Click the check box before 'AP'.
20. Click on 'AP'.
21. Select the TWRP file 'twrp-3.7.0_11-0-T290XXU3CVG3-20221120.tar.md5'.
For users with auto-reboot enabled: read step 22, 23 and 24 first to do it correctly.
22. Click 'start'.
23. Wait until you see 'PASS' in the left upper corner.
24. READ THIS WHOLE STEP BEFORE YOU EXECUTE IT! On your tablet, hold the Pwr+VolDown button for 10 seconds until it reboots. From then, you need to be fast. When you see the logo, hold Pwr+VolUp. When you see a warning, IMMEDIATELY press ONLY Pwr for once. After that, hold Pwr+VolUp again as fast as you can until you see the TWRP logo. You successfully managed to install custom recovery! If you fail, you must redo step 16-18 until you get into TWRP.
25. Swipe the box to the right so that you can make modifications and can install Magisk (App for ROOT) and Multidisabler (Disables VaultKeeper, so that ROOT and TWRP will not be uninstalled after normal boot).
26. On the computer, download 'Magisk-v25.2.apk' from here and 'multidisabler-samsung-3.1.zip' from below (under thread), and copy these 2 files to the root directory of the tablet's internal storage by selecting the tablet in Windows Explorer, selecting 'Internal Storage' and pasting them there. If you see weird directories, you may need a SD card connected to the tablet and paste the file there, which was my case. For SD card, you are going to select 'SD Card' instead of 'Internal Storage'.
27. Press 'Install' on tablet.
28. If you have an SD Card, click 'Select storage' and click on '(micro)SD Card'. Select 'Magisk-v25.2.apk' and then swipe to install. Wait until this is done. After that, repat step 21-22 for 'multidisabler-samsung-3.1.zip' and do the same, but this time, also click 'Wipe cache/dalvik' afterwards to make sure it can build new, fresh cache.
29. When you are done, click 'Done'.
30. Click 'Reboot' and then 'System'.
Hooray! You have rooted your SM-T290 tablet successfully. You can close/exit everything now! The app for root is 'Magisk', so verify that you have root completely by opening it, and looking at the 'Installed' column in the 'Magisk' section. If it says 'Installed 25.2 (252XX)', and ROOT is succesfully installed! If it doesn't say this, reboot into TWRP and repeat step 21-22.
(Maybe edited so please stay tuned.)
TWRP image could not be upload here due to XDA not allowing me to upload it due to the .tar.md5 file extension.
Recommended TWRP flashable ZIPs​
Open Gapps - Replaces/Installs more up-to-date apps from Google: https://opengapps.org
Samsung Game Services (by me) - Installs Samsung Game Booster + Launcher + Optimizing Service on any Samsung device with OneUI: https://github.com/minionguyjpro/Samsung-Game-Services-Installer
Troubleshooting​Problem: 8GB on a 32GB device
Fix: Turn your device off, boot into TWRP by holding Pwr+VolDown, pressing Pwr once immediately on the warning prompt, and pressing Pwr+VolDown again, until you boot into TWRP. Then go to Wipe > Advanced Wipe > Select System > Repair or Change File System > Resize File System > Swipe to the right. If that doesn't work, you can also try the Data partition, and/or the other option 'Repair File System'.
Problem: Fast battery drain
Fix: Turn your device off, boot into TWRP by holding Pwr+VolDown, pressing Pwr once immediately on the warning prompt, and pressing Pwr+VolDown again, until you boot into TWRP. Then go to Wipe > Advanced Wipe > Select Dalvik / ART Cache > Swipe to Wipe. If that doesn't work, try to factory reset the device, look for apps that may cause a fast battery drain or use a Custom ROM that is faster and has a better battery life.
Offline instructions and data​The offline guide and data are also available below:

Couple points of note:
To enter recovery mode, hold Volume UP (+), not Down (-). Do not hold Power, it will force a reboot again.
After unlocking the bootloader, the best course of action is to allow the device to boot into Android and enable Developer Options, then check to ensure OEM Unlocking is still there and grayed out (should show Bootloader is already unlocked). If not, this may cause problems when attempting to flash TWRP. See here
TWRP 3.6.0_11 is here: XDA Thread Download link
It's not necessary to change the Magisk extension from .apk to .zip. TWRP will still install it as a ZIP.
The only acceptable source for Magisk is the Magisk Github
It is not necessary to use an SD card, although it's recommended given the tablet's limited storage. MTP should work while in TWRP; the user can transfer both Magisk and the Multidisabler to the internal storage via USB and install them before wiping data.

V0latyle said:
Couple points of note:
To enter recovery mode, hold Volume UP (+), not Down (-). Do not hold Power, it will force a reboot again.
After unlocking the bootloader, the best course of action is to allow the device to boot into Android and enable Developer Options, then check to ensure OEM Unlocking is still there and grayed out (should show Bootloader is already unlocked). If not, this may cause problems when attempting to flash TWRP. See here
TWRP 3.6.0_11 is here: XDA Thread Download link
It's not necessary to change the Magisk extension from .apk to .zip. TWRP will still install it as a ZIP.
The only acceptable source for Magisk is the Magisk Github
It is not necessary to use an SD card, although it's recommended given the tablet's limited storage. MTP should work while in TWRP; the user can transfer both Magisk and the Multidisabler to the internal storage via USB and install them before wiping data.
Click to expand...
Click to collapse
While you say SD is not required, on mine my internal storage had random dirs. And didnt show files so i needed SD, but that depends of someone else has this too.

Minionguyjpro said:
While you say SD is not required, on mine my internal storage had random dirs. And didnt show files so i needed SD, but that depends of someone else has this too.
Click to expand...
Click to collapse
That's normal. TWRP is unable to decrypt storage, so the random directory names are because everything is scrambled. Still, you should be able to transfer files to internal storage via USB; just put them in the root of internal storage. The files you transfer will be unencrpyted.
That being said, it IS easier to use an external SD card...

V0latyle said:
TWRP 3.6.0_11 is here: XDA Thread Download link
Click to expand...
Click to collapse
According to this link, the file twrp-3.6.1_11-0-T290XXU3CUK4-20220327.tar.md5, which includes 4 files: recovery.img (actually TWRP), vaultkeeper.mbn, vbmeta.mbn and finally the file aboot.mbn, and this android bootloader 9 T290XXS3ATF1. That is, when installing TWRP, the android bootloader 11 is replaced with the android bootloader 9 ... Naturally, then we get a positive result

Talich52 said:
According to this link, the file twrp-3.6.1_11-0-T290XXU3CUK4-20220327.tar.md5, which includes 4 files: recovery.img (actually TWRP), vaultkeeper.mbn, vbmeta.mbn and finally the file aboot.mbn, and this android bootloader 9 T290XXS3ATF1. That is, when installing TWRP, the android bootloader 11 is replaced with the android bootloader 9 ... Naturally, then we get a positive result
Click to expand...
Click to collapse
Interesting. I'm getting set up now after installing CVG3, I'll update when done.
Edit: Yep, bootloader version shows as T290XXU3CVG3. I'll flash TWRP and update when done.

V0latyle said:
Interesting. I'm getting set up now after installing CVG3, I'll update when done.
Click to expand...
Click to collapse
Pay attention to the bootloader version. This is clearly visible in the Phone Info application in the Firmware Information tab...

V0latyle said:
Couple points of note:
To enter recovery mode, hold Volume UP (+), not Down (-). Do not hold Power, it will force a reboot again.
After unlocking the bootloader, the best course of action is to allow the device to boot into Android and enable Developer Options, then check to ensure OEM Unlocking is still there and grayed out (should show Bootloader is already unlocked). If not, this may cause problems when attempting to flash TWRP. See here
TWRP 3.6.0_11 is here: XDA Thread Download link
It's not necessary to change the Magisk extension from .apk to .zip. TWRP will still install it as a ZIP.
The only acceptable source for Magisk is the Magisk Github
It is not necessary to use an SD card, although it's recommended given the tablet's limited storage. MTP should work while in TWRP; the user can transfer both Magisk and the Multidisabler to the internal storage via USB and install them before wiping data.
Click to expand...
Click to collapse
OK, great!
Talich52 said:
According to this link, the file twrp-3.6.1_11-0-T290XXU3CUK4-20220327.tar.md5, which includes 4 files: recovery.img (actually TWRP), vaultkeeper.mbn, vbmeta.mbn and finally the file aboot.mbn, and this android bootloader 9 T290XXS3ATF1. That is, when installing TWRP, the android bootloader 11 is replaced with the android bootloader 9 ... Naturally, then we get a positive result
Click to expand...
Click to collapse
Yes, it does still work.

Talich52 said:
Pay attention to the bootloader version. This is clearly visible in the Phone Info application in the Firmware Information tab...
Click to expand...
Click to collapse
Yes, I understood you the first time.

V0latyle said:
Couple points of note:
To enter recovery mode, hold Volume UP (+), not Down (-). Do not hold Power, it will force a reboot again.
After unlocking the bootloader, the best course of action is to allow the device to boot into Android and enable Developer Options, then check to ensure OEM Unlocking is still there and grayed out (should show Bootloader is already unlocked). If not, this may cause problems when attempting to flash TWRP. See here
TWRP 3.6.0_11 is here: XDA Thread Download link
It's not necessary to change the Magisk extension from .apk to .zip. TWRP will still install it as a ZIP.
The only acceptable source for Magisk is the Magisk Github
It is not necessary to use an SD card, although it's recommended given the tablet's limited storage. MTP should work while in TWRP; the user can transfer both Magisk and the Multidisabler to the internal storage via USB and install them before wiping data.
Click to expand...
Click to collapse
I made a few changes. VolDown and VolUp are now correct. And removed Magisk and changed to direct download link from GitHub.

Talich52 said:
Pay attention to the bootloader version. This is clearly visible in the Phone Info application in the Firmware Information tab...
Click to expand...
Click to collapse
This should be no issue if you have Android 11. I installed it this exact way while i already had Android 11. I think the bootloader just gets a different version. I have latest T290XXU3CVG3 version with the android 9 bootloader from that TWRP version.

Minionguyjpro said:
This should be no issue if you have Android 11. I installed it this exact way while i already had Android 11. I think the bootloader just gets a different version.
Click to expand...
Click to collapse
Turns out flashing TWRP does overwrite the bootloader.
After updating via Odin, I was at T290XXU3CVD3.
After flashing TWRP, it's at T290XXS3ATF1.

Talich52 said:
Pay attention to the bootloader version. This is clearly visible in the Phone Info application in the Firmware Information tab...
Click to expand...
Click to collapse
Is no
V0latyle said:
Yes, I understood you the first time.
Click to expand...
Click to collapse
First flash update, then flash only AP with TWRP. Make sure to disable auto-reboot.

V0latyle said:
Turns out flashing TWRP does overwrite the bootloader.
After updating via Odin, I was at T290XXU3CVD3.
After flashing TWRP, it's at T290XXS3ATF1.
Click to expand...
Click to collapse
Yes, maybe that the bootloader is overwritten. But this is only a issue if you want the latest security patches. But i have the latest version of Android 11 installed. May it be possible that the software will be updated, but the bootloader/firmware will stay on an older version?

V0latyle said:
Turns out flashing TWRP does overwrite the bootloader.
After updating via Odin, I was at T290XXU3CVD3.
After flashing TWRP, it's at T290XXS3ATF1.
Click to expand...
Click to collapse
Yes, that's why it works. And the author of the TWRP file modestly kept silent that he was changing the bootloader to Android 9 ...
There is no trouble in this, the device is fully functional on Android 11 with 9 bootloader. One trouble - charging does not work, more precisely, there is no display of charging when charging the switched off device. This is critical for someone, but I don’t turn off the device, it only blocks ...

Minionguyjpro said:
May it be possible that the software will be updated, but the bootloader/firmware will stay on an older version?
Click to expand...
Click to collapse
A rooted device will not be updated over the air or via SmartSwitch. But you can update the firmware via ODIN, saving the data. But the bootloader should remain 9 android ...

Talich52 said:
Yes, that's why it works. And the author of the TWRP file modestly kept silent that he was changing the bootloader to Android 9 ...
There is no trouble in this, the device is fully functional on Android 11 with 9 bootloader. One trouble - charging does not work, more precisely, there is no display of charging when charging the switched off device. This is critical for someone, but I don’t turn off the device, it only blocks ...
Click to expand...
Click to collapse
Works for me
Minionguyjpro said:
Yes, maybe that the bootloader is overwritten. But this is only a issue if you want the latest security patches. But i have the latest version of Android 11 installed. May it be possible that the software will be updated, but the bootloader/firmware will stay on an older version?
Click to expand...
Click to collapse
Talich52 said:
A rooted device will not be updated over the air or via SmartSwitch. But you can update the firmware via ODIN, saving the data. But the bootloader should remain 9 android ...
Click to expand...
Click to collapse
Samsung devices are a bit weird. On "proper" devices like my Pixel, you can force update system without updating bootloader or radio. Not sure if Samsung works the same way; I suppose someone could try only flashing AP, CP, CSC and see if it works?

V0latyle said:
Works for me
Samsung devices are a bit weird. On "proper" devices like my Pixel, you can force update system without updating bootloader or radio. Not sure if Samsung works the same way; I suppose someone could try only flashing AP, CP, CSC and see if it works?
Click to expand...
Click to collapse
The weird thing is that you need to flash TWRP as AP, not BL. Indeed the charging will turn the device on.this issues is listed in the thread.

Minionguyjpro said:
The weird thing is that you need to flash TWRP as AP, not BL. Indeed the charging will turn the device on.this issues is listed in the thread.
Click to expand...
Click to collapse
Yeah...so updating will always overwrite TWRP. My theory is by not flashing the BL tar, maybe it won't overwrite the older bootloader?

V0latyle said:
Yeah...so updating will always overwrite TWRP. My theory is by not flashing the BL tar, maybe it won't overwrite the older bootloader?
Click to expand...
Click to collapse
Could be. Im not really sure. But... is the root workimg?