I have root on my SM-T295 A8 tablet!!
See my new post: How to Install TWRP and Root T295
Update 19 March 2021
Tested on T295XXU3BUC3 ROM
Prerequisites:
Bootloader unlocked - search forums.xda-developers for instructions how to do this.
OEM unlock on. In Settings/developer options, OEM Unlock slider should be to the right.
I see people still trying to patch files to get root.
If you flash the TWRP posted by @Talich52, with reboot unchecked you can install Magisk from TWRP.
1. If prerequisites met: install Android 9 bootloader through ODIN
2. Reboot to system
3. Go into download mode.
4. Open ODIN and in the AP slot put TWRP (see attachment below)
5. Uncheck auto reboot
6. Flash TWRP
7. Press vol dn + pwr keys.
8: When screen goes blank, press vol up + pwr keys.
9. Keep holding down both keys after reboot.
10. Tablet will reboot again.
11. When Samsung logo appears stop pressing pwr key.
12. When bootloader msg appears, release vol up key, quickly press & release pwr key, and quickly press vol up key until in TWRP.
13. You will then format (NOT WIPE) data. Answer yes to the format prompt
14. Clear dalvik/cache if prompted
15. Install Fix_vendor_9.0.zip or Fix_vendor_10.0.zip. See attached files.
16. Clear dalvik and cache.
17. Reboot back into recovery.
18. Install magisk - see attached
19. Reboot into system. May reboot again - that's okay
20. Enjoy!!
Updated (23 March 2020) my Tab A with XXS3ATB2 and got it rooted!!
Attached AP.tar file is for XXU2ASL3 only.
T295-Magisk-AP.tar
Okay, after multiple failed attempts, I read about a method to root my T295. It did not work!! But, I decided to just use Magisk Manager on the boot.img file only. The resultant file would not flash - it will fail. The original boot.img & recovery.img files are 65,536K bytes each. I had to take the Magisk modified boot.img and overlay it onto the original boot.ing file. I did the same for the recovery.img. Then the files would flash successfully. The first thing after booting was to check Magisk Manager. It showed I have Magisk 20.3 installed. So, I tested this with Root Explorer. I did have root!!
If you are going to try this, you need to unlock your boot loader, I think. I have not tried this with a locked bootloader.
Basic instructions
PLEASE READ ALL OF THIS BEFORE STARTING!! VERY IMPORTANT!!
Here are the steps to root your tablet:
Make a backup of you apps & data before doing this. This procedure will
wipe all you data.
Go to settings.
Select software info
Tap build number 7 times to get into developer mode
Go back to main settings page.
Scroll to bottom and select developer mode
In middle of page find OEM unlocking
Make sure slider is all the way to the right (should say allow bootloader to be unlocked)
Unlock bootloader:
1. turn off tablet
2. press and hold down vol up & vol down keys together
3. insert usb cable (should already be connected to computer)
4. when bootloader screen appears, release all keys
5. press and hold vol up key for 5 seconds, then release
6. read instructions on screen to unlock bootloader (this will wipe all your data)
After reboot, go through normal setup.
Now for the hard part.
You need to download the complete ROM you have installed on your Tablet.
It will be better if you have the same ROM version as I do in post in this post (#1).
You need to unzip the ROM so you can flash it in ODIN.
If you are on the same ROM version as in my post #1, then you can just download my rooted files.
Unzip my downloaded root files zip file.
Unzip the downloaded ROM files.
In the AP* file, you need to replace my files in the zip: boot.img, recovery.img & vbmeta.img
Start ODIN. Select files for BL*, AP*, CSC* & CP*
For CSC file, select HOME_CSC*
*** Uncheck auto reboot ***
Flash ROM.
After flashing ROM. press vol dn + pwr key
As soon as screen goes blank press vol up key and hold
When get into recovery, select data wipe, then reboot
Set up phone as you normally would.
After setup, go to Play store and install Magisk Manager. Run Magisk Manager to see if you have root.
Do It Yourself Instructions
You need to do some research before doing this. This is NOT a walk you by the hand tutorial. You need to learn some things before following these instructions. Learn how to use lz4.exe. Learn how to use simg2img. Learn how to make a .tar file.
Make a backup of you apps & data before doing this. This procedure will
wipe all you data.
Go to settings.
Select software info
Tap build number 7 times to get into developer mode
Go back to main settings page.
Scroll to bottom and select developer mode
In middle of page find OEM unlocking
Make sure slider is all the way to the right (should say allow bootloader to be unlocked)
Unlock bootloader:
1. turn off tablet
2. press and hold down vol up & vol down keys together
3. insert usb cable (should already be connected to computer)
4. when bootloader screen appears, release all keys
5. press and hold vol up key for 5 seconds, then release
6. read instructions on screen to unlock bootloader (this will wipe all your data)
After reboot, go through normal setup.
Now for the hard part.
You need to download the complete ROM you have installed on your Tablet.
Extract ROM files
Extract system.*.lz4, recovery*.lz4 and vbmeta*.lz4
Use tar to make an AP.tar file with the 3 above files. **Search the Internet if you do not know how to use tar.
Copy the AP.tar file to your phone. It is better to use adb push to prevent file correuption.
Install Magisk Manager from Play store.
Run Magisk Manager. Select install Magisk. Choose Select and Patch a file. Follow directions on screen to patch the AP.tar file.
Once the AP.tar file has been patched, use adb to pul the file to yur computer.
Extract the file from the AP.tar file.
Now come the hard part:
You cannot edit .lz4 directly. You have to decompress them. After decompressing system*, use simg2img to decompress the sparse file. Search the Internet if you do not know how to do this.
Now we make our modified files so they will flash in ODIN.
Instructions:
I used hex editor neo - a windows 10 app
I opened the stock kernel & recovery files in hex editor neo
I opened the Magisk modified kernel & recovery files in hex editor neo
I copied the modified kernel & recovery code onto their respective stock files in hex editor neo
I saved the stock files & closed hex editor neo.
I used cygwin to create a tar file: boot.img, recovery.img, vbmeta.img plus other files in original AP*.MD5 file.
You should also flash all ROM *.MD5 files (BL, CP, CSC) per Magisk instructions.
New AP.tar contents:
boot.img
dtbo.img.lz4
meta-data
recovery.img
system.img.ext4.lz4
userdata.img.ext4.lz4
vbmeta.img
vendor.img.ext4.lz4
I used Odin to flash the tar file
Flash ROM.
After flashing ROM. press vol dn + pwr key
As soon as screen goes blank press vol up key and hold
When get into recovery, select data wipe, then reboot
Set up phone as you normally would.
After setup, go to Play store and install Magisk Manager. Run Magisk Manager to see if you have root.
After installing Magisk:
(Powering up normally) → (System with NO Magisk)
(OEM Recovery Key Combo) → (Splash screen) → (Release all buttons) → (System with Magisk)
(OEM Recovery Key Combo) → (Splash screen) → (Keep pressing volume up) → (Actual recovery)
Please follow my instructions and the install instructions from Magisk web page.
Magisk Installation
What system do you use to manipulate the files? (Windows? Linux? Android?)
What is "overlay"? Do you extract the boot.img from the original AP.tar.md5, and from the magisk-patched.tar, copy the magisk-patched-boot.img to the beginning of the original-boot.img, and then replace the boot.img in magisk-patched.tar?
Do you give Odin four files, or just AP? Do you use CSC or HOME_CSC?
J.Michael said:
What system do you use to manipulate the files? (Windows? Linux? Android?)
What is "overlay"? Do you extract the boot.img from the original AP.tar.md5, and from the magisk-patched.tar, copy the magisk-patched-boot.img to the beginning of the original-boot.img, and then replace the boot.img in magisk-patched.tar?
Do you give Odin four files, or just AP? Do you use CSC or HOME_CSC?
Click to expand...
Click to collapse
In answer to your question, basically, yes.
I only flash the 3 files in the .tar file
I am on a Windows 10 laptop. Only 3 files need to be modified by Magisk: boot.img, recovery.img, vbmeta.img
I use Hex Editor Neo for overlaying the modified kernel and recovery files..
At the end of these 2 stock files is code that needs to be there, thus the 65 MB file size.
So I open the stock .img files (boot, recovery) in Hex Editor Neo, and copy the modded boot, recovery code into each stock .img file..
I use cygwin to create the .tar file, then flash with ODIN 3.1.14
Where does this leave you with respect to booting? Do you have to hold down buttons like you're trying to boot to recovery, then let go at the right time, to boot with Magisk active? Have you booted "normally" since you installed Magisk? Is Magisk still active? Have you shut down completely and then rebooted?
Wu's writeup says, when he's patching an AP file, to install to recovery, the boot.img is patched to "remove the signature of the image to prevent soft bricks". He doesn't explain why the signature would cause a soft brick with an unlocked bootloader and a nulled-out vbmeta. If you're restoring the original signature, it seems like you're flirting with the situation he was trying to avoid.
Will you be posting in the main Magisk thread. Aside from the news of another success, the details of your solution might help Wu improve the automatic patching enough to make manual adjustments unnecessary.
J.Michael said:
Where does this leave you with respect to booting? Do you have to hold down buttons like you're trying to boot to recovery, then let go at the right time, to boot with Magisk active? Have you booted "normally" since you installed Magisk? Is Magisk still active? Have you shut down completely and then rebooted?
Wu's writeup says, when he's patching an AP file, to install to recovery, the boot.img is patched to "remove the signature of the image to prevent soft bricks". He doesn't explain why the signature would cause a soft brick with an unlocked bootloader and a nulled-out vbmeta. If you're restoring the original signature, it seems like you're flirting with the situation he was trying to avoid.
Will you be posting in the main Magisk thread. Aside from the news of another success, the details of your solution might help Wu improve the automatic patching enough to make manual adjustments unnecessary.
Click to expand...
Click to collapse
No keypress is required for booting to maintain root.
I have tried this multiple ways: shutdown/boot & reboot - still have root.
I have not posted in main Magisk thread yet. Can you give me a link to the main thread where I can post this information?
https://forum.xda-developers.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382
This is the General Discussion thread. I've seen references to github for reporting bugs. github might be a better bet for providing technical information about how patching should be implemented.
J.Michael said:
https://forum.xda-developers.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382
This is the General Discussion thread. I've seen references to github for reporting bugs. github might be a better bet for providing technical information about how patching should be implemented.
Click to expand...
Click to collapse
Thanks for the link. I have posted to the Magisk forum.
Well, besides the possible outcomes, I tried the method and it worked for me. I'm not loosing magisk between boots too, not touching system apps but I can install modules and get root.
So, thank you very much for the finding!
Gartrax said:
Well, besides the possible outcomes, I tried the method and it worked for me. I'm not loosing magisk between boots too, not touching system apps but I can install modules and get root.
So, thank you very much for the finding!
Click to expand...
Click to collapse
You're welcome. Enjoy your Tab A now that you have root.
gcrutchr said:
I have root on my SM-T295 A8 tablet!!
Attached boot.tar file is for XXU2ASL3 only.
T295-Magisk-AP.tar
Okay, after multiple failed attempts, I read about a method to root my T295. It did not work!! But, I decided to just use Magisk Manager on the boot.img file only. The resultant file would not flash - it will fail. The original boot.img & recovery.img files are 65,536K bytes each. I had to take the Magisk modified boot.img and overlay it onto the original boot.ing file. I did the same for the recovery.img. Then the files would flash successfully. The first thing after booting was to check Magisk Manager. It showed I have Magisk 20.3 installed. So, I tested this with Root Explorer. I did have root!!
If you are going to try this, you need to unlock your boot loader, I think. I have not tried this with a locked bootloader.
Click to expand...
Click to collapse
You must have a unlocked bootloader to proceed. How did you overlay the files?
secretwolf98 said:
You must have a unlocked bootloader to proceed. How did you overlay the files?
Click to expand...
Click to collapse
Instructions moved to Post #1
In unlocking the bootloader, does it have any negative side? I remember on my sasung s5 before that i would loose what they call knox and not be able to restore permanently. How abiut in the 2019 tab?
amnher said:
In unlocking the bootloader, does it have any negative side? I remember on my sasung s5 before that i would loose what they call knox and not be able to restore permanently. How abiut in the 2019 tab?
Click to expand...
Click to collapse
Probably the same situation. I do not care about knox. I do not care about Samsun Pay.
I have not tested anything to restore knox.
gcrutchr said:
Probably the same situation. I do not care about knox. I do not care about Samsun Pay.
I have not tested anything to restore knox.
Click to expand...
Click to collapse
Attempting to restore Knox would be a waste of time because it is impossible. When you think of Knox, think of the manufacture warranty. Once you void the warranty, it's a goner.
secretwolf98 said:
Attempting to restore Knox would be a waste of time because it is impossible. When you think of Knox, think of the manufacture warranty. Once you void the warranty, it's a goner.
Click to expand...
Click to collapse
My understanding is knox is not installed on the T295
gcrutchr said:
My understanding is knox is not installed on the T295
Click to expand...
Click to collapse
According to the off site, the tablet has a Knox
Some user use the file from #1 and have this error(about security)
only official released binaries are allowed to be flashed after reboot
gcrutchr said:
My understanding is knox is not installed on the T295
Click to expand...
Click to collapse
The T29x and T51x has knox.
secretwolf98 said:
The T29x and T51x has knox.
Click to expand...
Click to collapse
Yea...just checked in priv-app folder.
I read somewhere the T29x series did not have knox...must have read wrong...ha, ha
And what we have?
How I can solve the problem with "Only official released binaries are allowed to be flashed"?
Alloc777 said:
And what we have?
How I can solve the problem with "Only official released binaries are allowed to be flashed"?
Click to expand...
Click to collapse
Did you unlock bootloader?
Did you toggle OEM unlock in settings/developer options?
Related
A/A & Welcome,
READ THE FULL GUIDE OR YOU CAN LAND IN TROUBLE
Ain't gonna work on pie official
AND DO PRESS THE THANKS BUTTON
Disclaimer
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or anything that happens to your device
INTRO
This is a full guide for unlock/relock, install TWRP, Root your device and backup/restore stock OS. Each and every step is explained thoroughly with pictures and videos.
I have ASUS Zenfone Max Pro M1 (6GB variant) (X00TD) (ZB601KL), so I can’t test for other variants. Please report back issues, corrections, omissions, etc., though the guide should work for all devices.
THINGS TO KNOW (IMPORTANT)
~Every text written in double quotes “” means the same written without the quotes.
e.g.:- “abcd” means abcd
“zxcv” means zxcv
They (“”) help to separate usual text from the other text (like a command, file name, etc.)
~If you have not enabled file name extensions then you will see files without their extension and vice versa
e.g.:- “filename”, “mypicture” in 1st case
“filename.extension”, “mypicture.png” in 2nd case, respectively.
~Boot Partition or Bootloader:-This is the partition that enables the phone to boot. Without this partition, the device will not be able to boot.
~Recovery Partition:-Recovery partition lets you boots the device into a recovery mode to perform recovery tasks.
~TWRP: - stands for TeamWin Recovery Project. It is a custom touch recovery that is GUI based.
~Flashing: - simplest: - installing
~Fastboot Partition: - lets us reflash partitions. (On device)
~Fastboot: - is an executable used to reflash partitions. It comes with the Android SDK. (On PC)
~Rooting: - an Android phone lets owner edit system files. Thus enabling various tweaks and use of apps that require root access.
~Device driver: - determines how PC will communicate with a device.
~Unlocking/Relocking:-With a locked Bootloader, booting into custom things is not allowed is not. Unlocking lets us do so.
~Reboot: - Switching ON AND OFF (in simple terms)
Requirements
MIND, PC, USB Cable, Internet, Fully charged PC (Windows OS), and obviously Asus Zenfone Max Pro M1
The Real Steps From Here
FOLLOWING THIS GUIDE YOU WILL PROBABLY LOSE ALL THE DATA ON YOUR PHONE SO MAKE A BACKUP FIRST (Don’t worry it’s in guide too)
STEP 1. Downloading all the necessary files
a. Here are 2 zip file with everything you will probably need following the guide :-
basic zip
extension zip
. I have tested the procedures using these files only so maybe other versions might not work. A “guide.doc” with the same text as in here (on XDA) is also present. It will be of great help if you don’t have internet connection in PC.
The basic zip file contains minium files needed.
The extension zip file contains the TWRP recovery(then one used in the guide),guide.docx ,and the videos used here too.
Copy the twrp file to unlock folder of extracted folder.
b. Extract the zip file above.
First download the zip file and Copy to PC
Then Right Click on it
Then click “Extract All”
Uncheck “Show extracted files…”
Click on “Extract”
The folder “zip” will be extracted
Done
This “zip” folder will be called extracted folder in the guide video link to extract zip
To download most up to date version of the files go to links present at last
STEP 2. BACKUP
a. Use an apk backup tool to backup app installers
VIDEO TO BACKUP APP INSTALLERS
b. Some APPS like Whatsapp, etc. have backup to drive function use that
VIDEO TO BACKUP WHATSAPP CHATS
c. Backup SMS AND Call Logs
VIDEO TO BACKUP CALL LOGS AND MESSAGES
d. Copy each and every file from you internal storage to PC.
Video to backup each file to pc
DONE
Step 3. UNLOCKING BOOTLOADER(Data will be wiped)
2 options:-
A. Official Method (NOT TESTED): -
In extracted folder go to “unlock” folder then “Official” folder. Install the “UnlockTool_9.1.0.3_180621_fulldpi_signed_ZB601KL.apk” in Asus and follow the steps from there.
B. Unofficial Method (Tested):-
a. Installing Drivers
Connect phone using USB cable to PC
Right click on This Pc
Go to “Manage” > “Device Manager” Or Just search for “Computer Management”/“Device Manager”
A list will appear.
Find your device (best way to do so is by disconnecting/connecting the device and notice the changes accordingly in the list)
Now right click on it>”Update Driver Software”>“Browse my computer for driver software”
Now either enter path of the driver folder or click on browse and navigate to the driver path from there.
Press Next OR
“Let me pick …”>and select the driver
video to install driver
The drivers have been installed
b. Booting into FASTBOOT
Switch Off the Phone
Hold the Volume UP and Power ON Button Simultaneously
Device buttons labbled image
You will see this on your phone
image of FASTBOOT screen
c. Unlocking Bootloader
Now connect phone using USB cable to PC
Look for the “unlock” folder in the extracted folder.
Open it
Find “unlock.cmd” or “unlock” file
(Or “unlock no erase.cmd” to keep data {not tested})
Open it
Done
d. You will see some messages in yellow/brown/white colour on your phone
You will most probably see “encrypting your device”, “warning Bootloader unlocked” messages, let phone do its work and don’t interrupt it, and keep cable connected. Phone might reboot too. The phone will at last boot into stock OS and you will see the device setup screen.
image of the warning message
e. Now if you wanted TO ONLY UNLOCK BOOTLOADER THEN THE JOB IS DONE, long press power button. If you want to root or flash TWRP then continue (Tested method to root requires TWRP flashing or you can try the untested method to root only)
Step4. Installing/Flashing TWRP
TESTED METHOD
a. Connect phone using USB cable to PC
b. Don’t setup your device just now because possibilities are you might lose the data again
c. Boot into fastboot mode
d. Open the “unlock” folder in the extracted folder.
Now Two Different ways to opt for from here:-
i. THE LAZY METHOD (Tested)
a. Open “flash_recovery.bat” or “flash_recovery” in the “unlock” folder of the extracted folder.
b. You can flash the tested or any other recovery using this script.
c. Follow the steps from the script
video of how to use the script
d.Then go to step of Flashing ZIPS of The Manual Method
e. Done
OR
ii. The Manual Method (Tested)
a. Keeping Shift Key pressed, right click {with mouse} in the blank white space of the “unlock” folder’s explorer window.
b. From the menu select “open command window here”
c. A CMD window will be opened
open cmd video
d. Now type “fastboot devices”
e. See if your device is connected. You will see something like this
f. Now type “fastboot flash recovery twrp-3.2.3-0-X00TD-20181024.img”
If you want to flash any other recovery instead of “twrp-3.2.3-0-X00TD-20181024.img” write the file name of your recovery file. Make sure it’s in “unlock folder”. Though this recovery is the only tested one (by me).
g. Now keeping the phone connected to PC, boot into TWRP/Recovery by pressing the Volume Down and Power ON Button Simultaneously.
h. The usual warnings, messages and recovery boot screen will flash:-
warning image
twrp flash screen image
i. It may take some time to load so wait for at least 2 minutes.
j. Now if touch is not working press power button 2 times (on and off the screen)
video showing how to enable touch in twrp
k. If it shows “Swipe to Unlock” do so. If it shows “Swipe to Allow Modifications” then wait and continue reading …
swipe to allow image
swipe to unlock
l. “Swipe to Allow Modifications” means you allow TWRP to modify system. This will make sure TWRP remains in the phone and not just vanish after a reboot but it also means you will have to flash some other files to be able to boot into stock rom back.
m.
2 ways from here:-
i. Now after swiping, Decrypt Screen will appear just press cancel.
decrypt screen image
OR
ii. If you have data on the device then enter pin/password or try default_password.
If you had kept pattern then either go back and change it or try this:-
1 2 3
4 5 6
7 8 9
these no’s correspond to pattern dots.
Say you kept pattern “third row left to right” then the password is 789 .
If all these fail then you will have to lose your data.
n. As we don’t have any precious data in our phone we will (or you are compromising)
Press “Wipe”
Press “Format Data”
TYPE “yes”
Press “tick” or “enter key”
Done
wipe data video
>Flashing ZIPS
o. Now Copy these 2 files
i. “decrypt.zip” or “decrypt”
ii. “Disable_Dm-Verity_ForceEncrypt_12.16.2018.zip” or “Disable_Dm-Verity_ForceEncrypt_12.16.2018”
From extracted folder to your phones internal storage.
p. Go to Install>select the zip>swipe to flash (flash dm_verity… then decrypt…)
If you don’t see your device storage connected then try reconnecting using USB cable and also check if MTP is enabled.
enable mtp video
>Done
Want to root? Then continue…
or >
Now reboot to system Go to Reboot>System
video to show how to rebbot to system in twrp
Step 5. Rooting
We will be using Magisk to root you can use any other method but this is the only tested method.
a. Copy “Magisk-v18.0.zip” or “Magisk-v18.0” to your phones internal storage from extracted folder.
b. Go to Install>select Magisk…>swipe to flash
Done
c. Now reboot to system Go to Reboot>System
reboot video
e. To use Magisk properly you may need to download latest apk. (Link at last)
Step 6. Relock (NOT TESTED)
a. Connect phone using USB cable to PC
b. Boot into fastboot mode
c. Open “Relock” folder from extracted folder
d. Open “relock.cmd” or “relock” file
Done
Step 7. RESTORING
a. First setup the Device again
b. Copy each and every file back to the phone storage
c. Now to restore messages see the restoring part of this video here
d. WhatsApp messages will be automatically restored after you install the app with same number as before.
Tips
After rooting don’t just go on and flash a custom rom. Take a backup first (of all partitions) using TWRP and keep it safe somewhere so you won’t need to find unbrick tutorials later. Plus you will have your most stable and tailored rom with you.
Also don’t just go on and flash xyz mod. Research and then Flash.
Magisk is our best friend. It lets you do modifications without hurting the system. The Magisk modules are most safe mods as they can be reverted back easily.
And don’t just go on and debloat stock OS. In Magisk there is a module called Debloater use that. You can easily revert back if anything goes wrong.
Other good Magisk modules: - Energized, Systemizer, MidnightCore & Advanced Charging Controller (acc) but do read their XDA guides first.
Sources/Credits:-
Dm_Verity.zip Official XDA:-
link
Original unlocking XDA:-
link
Magisk XDA:-
link
Original Decrypt Data XDA:-
link
TWRP Used XDA:-
link
Credits to the authors of the above guides
Plus sorry for bad editing of videos. I am facing some problems. Will try to post better videos.
I thank all the members who have made the previous guides for their hard work. This guide by no means disrespects their hard work. This guide is just an Addition instead of an Alternative.
Read the full guide
Press the thanks button
Re edited the guide.
Added link of apps used in YouTube videos.
Not working for pie official
Deleted cruddy comments. Good job.
Good initiative but not so good noob guide. Please format it for better organization and better understanding.
malikmiran19 said:
2. BACKUP
>Use an apk backup tool to backup app installers
howto video
Click to expand...
Click to collapse
Appreciate the effort . I have a suggestion. It would be helpful to put the name or link of the app that you used to back up apks.(some apk extractor lite ig). I'll provide the one I found anyway. https://www.apkmirror.com/apk/ankit.../apk-extractor-lite-2-8-android-apk-download/
camaroamarelo said:
Good initiative but not so good noob guide. Please format it for better organization and better understanding.
Click to expand...
Click to collapse
Did so
GliderZ said:
Appreciate the effort . I have a suggestion. It would be helpful to put the name or link of the app that you used to back up apks.(some apk extractor lite ig). I'll provide the one I found anyway. https://www.apkmirror.com/apk/ankit.../apk-extractor-lite-2-8-android-apk-download/
Click to expand...
Click to collapse
Added apk links in YouTube videos
Anyone tried unlocking without erasing data?
TheDarkKnight said:
Anyone tried unlocking without erasing data?
Click to expand...
Click to collapse
nyimak
fuzuy said:
nyimak
Click to expand...
Click to collapse
What?
TheDarkKnight said:
What?
Click to expand...
Click to collapse
it means im interested in your question and im following it
I want to unlock bootloader, flash TWRP and flash a custom ROM (Cerberus OS).
I have rooted and flashed TWRP before in my previous device but I'm not familiar with unlocking and Custom ROM.
Do I have to follow all hese steps for what I want to do or I must skip decrypt/encrypt and Magisk?
dharsouparno1 said:
I want to unlock bootloader, flash TWRP and Custom ROM.
Click to expand...
Click to collapse
U can flash twrp then flash ROM and probably flash magisk for root tooo
malikmiran19 said:
U can flash twrp then flash ROM and probably flash magisk for root tooo
Click to expand...
Click to collapse
Thanks for the help.
I'm running into some problems while installing the driver software on my Windows 10 laptop. It shows Error 10 this device cannot start.
I tried to uninstall and reinstall the drivers, rebooted my pc on every step, tried to install while connected to my phone, but nothing seems to work.
I've installed the Pie Beta for Asus Zenfone Max Pro M1 (not sure if this is causing it)
Is there a solution to this problem?
I am currently on Beta Pie...will these methods work for bootloader unlocking and TWRP, custom rom flash ???? I just wanna use PE/Havoc OS rom...no other tweaks or root
thanks its working
I updated to pie beta and I think this guide is not working for that, because when flashing twrp. I'm getting 'request download size is more than allowed size' and I tried every way possible to solve it. But no luck Hope you can help me with it, or maybe it'll work after stable version?
---------- Post added at 04:15 AM ---------- Previous post was at 04:11 AM ----------
utsavdey said:
I am currently on Beta Pie...will these methods work for bootloader unlocking and TWRP, custom rom flash ???? I just wanna use PE/Havoc OS rom...no other tweaks or root
Click to expand...
Click to collapse
It's not working for me. I also updated to pie beta few days back.
Is this method working on pie stable build
Anyone tried this method on the stable pie build 056?
How to Root Note 9 with Magisk on Android 10 (Q) without Custom Recovery (Eg.. TWRP)
This method will work with most of the latest Samsung devices running Android 9/10. (Tested and Working on Galaxy Note 9 (Exynos) with Android 10 Q).
WARNINGS: I am not responsible for any damage made. Your device warranty will be void. Do it at your own risk.
Warning: Before Installing Magisk
Installing Magisk WILL trip KNOX
Installing Magisk for the first time REQUIRES a full data wipe. Backup before continue.
You have to have your bootloader unlocked before following the instructions
REQUIREMENTS: (Basic knowledge about android rooting.)
Stock Firmware
Odin v3.14.1
Magisk Manager (You can find in Downloads section of Magisk Thread, I used Magisk Manager v7.5.1)
STEP 1 Unlocking Bootloader (This may need to Wipe your Data/Factory Reset.)
Enable Developer Mode on the Galaxy Note 9
To Enable Developer Mode Open Settings option.
Under Settings option, select About phone, then choose Software Information.
Scroll down the screen and tap Build number several times until you see a message that says "Developer mode has been enabled".
Tap on the Back button and you will see the Developer options menu under Settings, and select Developer options.
Toggle the OEM Unlock option on
Then tap on the Turn On button
STEP 2 Patching and Flashing (This may need to Wipe your Data/Factory Reset.)
Download the firmware for your device.
Unzip the firmware and copy the AP tar file to your device. It is normally named as AP_[device_model_sw_ver].tar.md5
Install the latest Magisk Manager
In Magisk Manager: Tap Install → Install → Select and Patch a File and select the AP tar file.
Magisk Manager will patch the whole firmware file and store the output to [Internal Storage]/Download/magisk_patched.tar
Copy the patched file to your PC with adb pull /sdcard/Download/magisk_patched.tar. Do not use MTP as it is reported to corrupt files. (I have copied with MTP)
Reboot to download mode, and flash magisk_patched.tar as AP in Odin, together with the BL, CP and HOME_CSC files (I have used CSC instead of HOME_CSC). (Never flash only an AP file, as Odin can shrink your /data file-system if you do). Important: Uncheck “Auto Reboot” in Odin Options!
Magisk is now successfully flashed to your device! But there are still several steps before you can properly use the device.
STEP 3 Wipe data/factory reset (This may need to Wipe your Data/Factory Reset. : D)
We now want to boot into the stock recovery to factory reset our device. Full data wipe is mandatory! Do not skip this step.
Press Power + Volume Down to exit download mode. As soon as the screen turns off, immediately press the combo key to boot to recovery (e.g. on the Note 9 it is Power + Bixby + Volume Up). Since we want to boot into stock recovery, continue pressing the volume up button until you see the stock recovery screen. (I had to release power button when Note 9 logo appeared).
Use volume buttons to navigate through the stock recovery menu, and the power button to select an option. Choose Wipe data/factory reset to wipe the data of the device.
This time, we can finally boot to the system with Magisk. Select Reboot system now, and immediately press the combo key to recovery. After seeing the bootloader warning screen, release all buttons so it can boot to the system. (Just select Select Reboot system now)
The device will automatically reboot for the first time it boots. This is completely normal and done by design.
After the device is booted up, do the usual initial setup. The following steps will need an internet connection.
You shall see Magisk Manager in your app drawer; if not, manually install the Magisk Manager APK and continue to the next step. The app would be a stub and it shall automatically upgrade to the full Magisk Manager when you open it.
Magisk Manager will ask to do additional setups. Let it do its job and the app will automatically reboot your device.
Voila! Enjoy Magisk
How to Root Note 9 with Magisk on Android 10 (Q) with Custom Recovery (Eg.. TWRP)
This method will work with most of the latest Samsung devices running Android 10. (Tested and Working on Galaxy Note 9 (Exynos) with Android 10 Q).
WARNINGS: I am not responsible for any damage made. Your device warranty will be void. Do it at your own risk.
Warning: Before Installing Rooting your device
Rooting your device WILL trip KNOX
Rooting your device for the first time may REQUIRES a full data wipe. Backup before continue.
You have to have your bootloader unlocked before following the instructions
REQUIREMENTS: (Basic knowledge about android rooting.)
Stock Firmware
Odin v3.14.1
TWRP For Android 10
Magisk Latest Stable ZIP or (I used Magisk Canary from Github)
DM-Verity, Force Encryption, and Disc Quota Disabler (I used Dm-Verity & ForceEncrypt Disabler v02.02.2020)
STEP 1 Unlocking Bootloader (This may need to Wipe your Data/Factory Reset.)
Enable Developer Mode on the Galaxy Note 9
To Enable Developer Mode Open Settings option.
Under Settings option, select About phone, then choose Software Information.
Scroll down the screen and tap Build number several times until you see a message that says "Developer mode has been enabled".
Tap on the Back button and you will see the Developer options menu under Settings, and select Developer options.
Toggle the OEM Unlock option on
Then tap on the Turn On button
STEP 2 Flashing Stock Firmware (This may need to Wipe your Data/Factory Reset.)
Reboot to download mode
To Boot into the Download Mode Power Off your device
Make sure you have a USB Type-C cable connected to your PC
Then press and hold the Volume Down and Bixby buttons at the same time
Hold these two buttons down and you insert the USB Type-C cable
Continue holding these two buttons down until you are greeted with the splash screen for Download Mode
Press the Volume Up button to bypass the splash screen and enter the Odin Mode
Now open Odin on your PC, Flash your firmware AP, BL, CP and CSC files. Important: Check “Auto Reboot” in Odin Options and keep your device in your hand and eye on Odin.
After you get flash got PASS! in Odin your device will restart and you will see blue screen saying you device is updating (or similar statement) for 2-5 seconds and then your device will restart again. (Next Step is Very Importent).
As soon as the screen turns off for second restart you have to press Power + Bixby + Volume Up to boot into the stock recovery. (I had to release power button when Note 9 logo appeared).
Use volume buttons to navigate through the stock recovery menu, and the power button to select an option. Choose Power Off and remove your USB Type-C cable from your device.
STEP 3 Flashing TWRP(This may need to Wipe your Data/Factory Reset.)
Now your device is in power off state you have to boot into the Download Mode to flash TWRP. (You can get info on STEP 2 to boot into Download Mode)
Now open/reset Odin on your PC and go to the Odin option uncheck “Auto Reboot”
Click on the AP button to select TWRP file (Eg: twrp-3.3.1-r3.7-q-crownlte.tar) and click Start. (Next Step is Very Importent).
After you get flash got PASS! in Odin Press Power + Volume Down to exit download mode. As soon as the screen turns off, immediately press the combo key to boot to recovery (e.g. on the Note 9 it is Power + Bixby + Volume Up). Since we want to boot into TWRP recovery, continue pressing the volume up button until you see the TWRP recovery screen. (I had to release power button when Note 9 logo appeared).
STEP 4 Rooting You Device (This may need to Wipe your Data/Factory Reset.)
In TWRP you have to swipe to allow the modification
Now format your data Tap Wipe->Format Data and type yes to continue. (You can Skip step 2 and 3)
No go back to TWRP home screen by pressing back button multiple times and tap Reboot and then click Recovery. (Your device will restart to TWRP recovery mode).
Insert your USB Type-C cable to connect your device to PC.
You will get your device MPT drive in my computer, Copy Magisk Canary zip file and Dm-Verity & ForceEncrypt Disabler v02.02.2020 zip file to your device.
Now you have to flash Magisk Canary in TWRP click Install and select Magisk Canary zip and start flashing. Then flash ForceEncrypt Disabler in TWRP. (If you get the mount error whioe installing ForceEncrypt Disabler then just ignore it and move to next step).
Click reboot to boot your system.
Done! Enjoy
Biometrics and fingerprint work after root?
Trimis de pe al meu SM-N960F folosind Tapatalk
Detonatte said:
Biometrics and fingerprint work after root?
Trimis de pe al meu SM-N960F folosind Tapatalk
Click to expand...
Click to collapse
Yes it works
Guessing this is non snapdragon use only. I don't see any models this works with but root isn't possible with North American note9 as far as I know. The boot loader is locked down.
I don't understand...where, how flash magisk_patched.tar ????
Please edit title to say this is Exynos only
thanks ..
secure folder still work after root?
Detonatte said:
I don't understand...where, how flash magisk_patched.tar ????
Click to expand...
Click to collapse
Follow STEP 2 Patching and Flashing (This may need to Wipe your Data/Factory Reset.)
Download the firmware for your device from sammobile or via Frija
Unzip the downloaded firmware on your PC and copy the AP tar file to your mobile device. (It is normally named as AP_[device_model_sw_ver].tar.md5).
Install the latest Magisk Manager on you mobile device.
In Magisk Manager: Tap Install → Install → Select and Patch a File and select the AP tar file that you have copied from your pc.
Magisk Manager will patch the whole firmware file and store the output to [Internal Storage]/Download/magisk_patched.tar.
Copy the patched magisk_patched.tar file to your PC with adb pull /sdcard/Download/magisk_patched.tar. (Do not use MTP as it is reported to corrupt files. (I have copied with MTP)).
Reboot to download mode, and flash magisk_patched.tar as AP in Odin, together with the BL, CP and HOME_CSC files (I have used CSC instead of HOME_CSC). (Never flash only an AP file, as Odin can shrink your /data file-system if you do). Important: Uncheck “Auto Reboot” in Odin Options!
macgyver40 said:
Guessing this is non snapdragon use only. I don't see any models this works with but root isn't possible with North American note9 as far as I know. The boot loader is locked down.
Click to expand...
Click to collapse
Yes this is only for Exynos version, before posting this tutorials I don't have info about this.
TokedUp said:
Please edit title to say this is Exynos only
Click to expand...
Click to collapse
Done.
moaz1988 said:
thanks ..
secure folder still work after root?
Click to expand...
Click to collapse
Currently I am not using this System-as-root method to root my device because working version of Dm-Verity & ForceEncrypt Disabler is released so I am using TWRP method to root my device so I can't test secure folder on this rooting method. Now my device is rooted with Magisk via TWRP and secure folder is working without any issue so I think it will work with this method too.
Zer0De8th work perfect root with: twrp-3.3.1-r3.7-q-crownlte.tar, Magisk-v20.3(20300).zip and Disable_Dm-Verity_ForceEncrypt_02.02.2020.zip
Thx very much man!!!
Detonatte said:
Zer0De8th work perfect root with: twrp-3.3.1-r3.7-q-crownlte.tar, Magisk-v20.3(20300).zip and Disable_Dm-Verity_ForceEncrypt_02.02.2020.zip
Thx very much man!!!
Click to expand...
Click to collapse
Glad to know it works for you.
And SecureFolder work perfectly!
Trimis de pe al meu SM-N960F folosind Tapatalk
Hello
Thanks to the authors of this tutorial, and others on XDA, I completed a detailed procedure to Root the Galaxy Note 9 SM-N960F under Android 10 with the Recovery Custom TWRP which allows the backup and restoration of all partitions.
This procedure may seem long because it is very detailed because there are very important points not to miss so that the partitions are not locked by Android 10.
I hope the French / English translation is good because I am very bad in English
cordially
https://forum.xda-developers.com/showpost.php?p=81695605&postcount=324
Montero try backup and restore with TWRP? Work??
Trimis de pe al meu SM-N960F folosind Tapatalk
Yes work very fine for All partitions
Detonatte said:
Zer0De8th work perfect root with: twrp-3.3.1-r3.7-q-crownlte.tar, Magisk-v20.3(20300).zip and Disable_Dm-Verity_ForceEncrypt_02.02.2020.zip
Thx very much man!!!
Click to expand...
Click to collapse
Me too....
Restoring my data using Titanium Backup..
Samsung acc working
How to enable hidden menu since no more CSC folder (feature.xml)?
inamie said:
Me too....
Restoring my data using Titanium Backup..
Samsung acc working
How to enable hidden menu since no more CSC folder (feature.xml)?
Click to expand...
Click to collapse
Here is the new location for CSC feature.xml "/odm/etc/omc/XXX- your country code/conf/cscfeature.xml".
You have to Decode / Encode CSC files use OmcTextDecoder .
Many of the old CSC features don't work on Samsung Android Q
Zer0De8th said:
Here is the new location for CSC feature.xml "/odm/etc/omc/XXX- your country code/conf/cscfeature.xml".
You have to Decode / Encode CSC files use OmcTextDecoder .
Many of the old CSC features don't work on Samsung Android Q
Click to expand...
Click to collapse
Thanks,
Any idea how to set Magisk Manager.
New version 7.5.2 no option to hide selected application..
cant use certain apps like shopee pay and ewallet on rooted device.
Previous version 7.5.1 no problem.
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?
purpose of this post is to share an alternative method for those who fail to root using @topjohnwu recommended method or the method posted by @Grarak here on A70 forum that involves patching recovery.img in magisk and then flashing that in twrp>install to boot.
failing to root means either bootloops or unstable magisk root or magisk root disappearing randomly or after a module installation.
this is not my original guide , i was told this method by @raeumler via PM and i am sharing it on A70 forums incase other methods dont work.Some of the steps may not be neccesary , but i did them ritually anyway
my phone model is SM-A705FN /DS and firmware version is A705FNXXU5ASL4( with 1st jan 2020 updates) . country is PAK
do this at your own risk! i will not be responsible for any negative consequences
appropiate links and files will be posted as attachments
rooting procedure( read each step twice)
1- UNLOCKING BOOTLOODER= this will factory reset device . backup your data
read step 02 of this linked guide https://forum.xda-developers.com/galaxy-a70/development/recovery-twrp-galaxy-a70-t3955984
DOWNLOAD FIRMWARE AND ATTACHMENTS= now i am assuming you have stock samsung android 9. if not, download your firmware via SamFirm windows program and flash in odin to go to stock[ program available in attachements]. Download other attachements too
2-Find vbmeta.tar in downloaded attachments and unpack it. you will get vbmeta.img file.
3. unzip stock Samfirm downloaded firmware. you will get 5 files in it (BL,AP,CP,CSC and CSC_HOME).open the AP File from the factory rom with 7zip
4. remove userdata.img, vendor.img and system.img from the AP file
5. replace vbmeta.img with the one you have downloaded in step 2.
6. repack AP as AP.tar [ use 7zip or peazip. i used peazip windows program, ensure file type is TAR]. transfer this AP.tar to your phone
7. install magisk manager 7.5.1 on your phone and open it. connect your phone to internet.
8. hit the upper install button and choose "patch a file"
9. choose the repacked AP file and patch it[ this requires active internet as magisk needs to download its zip file]
10. copy the AP file which magisk creates in internal storage/download/magisk_patched.tar back to your pc (better keep it named as such for differentiation, its irrelevant how the file is named as long its a tar file)
11. download,unzip and open Odin 3.1.3.1[available in attachements]. i used Odin3+v3.13.1_3B_PatcheD.exe , there is a simple version too inside the zip
12. go into download mode on your phone (shut down completely then hold vol+ vol- togather and plug in cable connected to PC ). Odins should show Com port X as blue
13. in odin: put the BL, CP and HOME_CSC in its place (the files from the factory firmware you downloaded in step 1 from SamFirm windows program) and place the magisk patched AP on AP
16. check if you want autoreboot or not, its your own taste (some feel safer with autoreboot unchecked, both works)[ i kept autoreboot checked]
15. hit start and let it finish (when it stucks on something try another cable and install latest samsung adb driver.)
16. let the system reboot
17. if you get stuck in bootloop or freeze >10 min on samsung logo, try to force reboot.press volume down + power till screen turns blank then press volume + and power till bootloader unlock screen appears and then let go of all keys.
if still it doesnt boot, then press volume down and power togather to force shutdown and then press volume up and power till stock recovery boots up. Mine at this stage said firmware is corrupt ,factory reset needed so thats what i did in stock recovery. power off system in stock recovery and then press volume+ and power till bootloader warning screen , let go of all buttons, it should now boot up fine with magisk manager app in app drawer. DONT OPEN IT YET
download this app from play store https://play.google.com/store/apps/details?id=fr.petrus.tools.reboot&hl=en_US. open app and press reboot. No need to press any keys
on reboot complete ,connect to internet,open magisk, let it check for updates, it should say installed in both portions. magisk will do additional enviromental steps and then reboot. on booted up, use the linked reboot app to reboot again.
now magisk should be installed all fine
for viper4android>open magisk>swipe left and tap downloads> installed 2.7.1.6> reboot with linked app
on reboot check if app is installed, if not > install and login on xda labs and download viper4android 2.7.1.6> open app> give it root accesss> let it reboot device on installtion> on bootied up reboot again with linked app and then check drivers on viper4android[ make sure master switch is on and then play some music ,tap the chip icon to see driver status and processing status
from here onward, always use the linked reboot app to reboot device. if an app or module reboot device automatically( like viper4android does ) then on boot complete,reboot again with the linked app
Credits to @Grarak for his original work and files
@raeumler for his guide.
Unfortunately, it doesn't work on Android 10.
There is an error in Odin when flashing files.
The error is when flash the AP file, more specifically vbmeta.
kac222 said:
Unfortunately, it doesn't work on Android 10.
There is an error in Odin when flashing files.
The error is when flash the AP file, more specifically vbmeta.
Click to expand...
Click to collapse
This is for stock android 9 as the title says.
Follow @MarvinMod guide to root android 10
Yes i know but i tried for yourself. I know how rooted on Android 10. Regards.
Wysłane z mojego SM-A705FN przy użyciu Tapatalka
Looks like a useful guide, thank you for putting it up. I'm really not sure how to get the firmware though from the SamFirm program. I found this ( https://androidmtk.com/use-samfirm-tool - might be useful info?) since I have never used the samfirm tool before I am lost at that step. I don't know if there's a list of region codes somewhere? I have an 'international version' A70. Using SM-A705MN, baseband version A705MNXXU3ASI1 .. Since I'm in the US, should I look to getting that type of ROM or should I find out what region this particular ROM already on the phone is, and use that?
I've done rooting before (Samsung S4, HTC M9, LG V20) but these phones seem even more complicated.
Even if all this works, then the root is not 'permanent'? I'm not sure why a different 'reboot app' would be needed if the system is modified in a way to enable things like magisk/super su?
DelphisDoofer said:
Looks like a useful guide, thank you for putting it up. I'm really not sure how to get the firmware though from the SamFirm program. I found this ( https://androidmtk.com/use-samfirm-tool - might be useful info?) since I have never used the samfirm tool before I am lost at that step. I don't know if there's a list of region codes somewhere? I have an 'international version' A70. Using SM-A705MN, baseband version A705MNXXU3ASI1 .. Since I'm in the US, should I look to getting that type of ROM or should I find out what region this particular ROM already on the phone is, and use that?
I've done rooting before (Samsung S4, HTC M9, LG V20) but these phones seem even more complicated.
Even if all this works, then the root is not 'permanent'? I'm not sure why a different 'reboot app' would be needed if the system is modified in a way to enable things like magisk/super su?
Click to expand...
Click to collapse
Download phone info app and note pda, csc and phone codes.
Use these codes to Google your exact firmware and download that ( you may have to visit various websites that offer better speed)
The samfirm, frija only allows latest firmware to be download, not the currently installed one.
One you have the stick firmware file, then you can proceed with rooting.
If you are on android 9 use this guide
If you are on Android 10 use MarvinMod guide.
This reboot app is what I currently use. Haven't experimented with other apps.
The root is permanent as long as your reboot with the mentioned key combination or the reboot app.
The reboot app simple allows you to reboot without the key combination. If you don't want to use this app then you must reboot with the mentioned key combination to retain root. Otherswise you wouldn't have root unless you reboot again with correct combination.
To make this easy I suggested that reboot app
Yes I feel you bro, I had Samsung note 2 then note 4 phone and they were easier to root.
But with Google changing things the best way to root is to use magisk and this complicated methods
i think you can make a little script for rebooting. should work. i really want to know how the bootpartition is corrected, at boot its recovery-from-boot.p as image and install-recovery.sh for reenabling stockrecovery. if you rename this files bootup should work without reflashing boot or recovery. there have to be something similar to the rebootprocess, a script that flashes a sparse image (the *.p file to delete su binary or something like that..) or it just kills the su binary in the folders itself. im to stupid for dmesg and logcat i couldnt find out whats going on at reboot. also the petrus reboot app reboots instant, keys doesnt. seems to be that adb reboot deletes root too. yesterday, somehow my fone did sonething last night, which crashes root again.....i need twrp urgent to make backup. but the binary let not decrypt it. U5 is android 10 bootloader and there are some issues with twrp (decrypt). last time it has saved my backuptry to /data/backupfolder as internal is encrypted. i dont want to factoryreset this phone....is it complicated to build a recovery ? or is there something like a clickitalltogetherapp?
---------- Post added at 09:46 AM ---------- Previous post was at 09:24 AM ----------
following reboot variants keeping root:
hold all keys for 10 seconds
reboot via terminal or script
petrus app
following kills root:
standartreboot with hw-keys
adb reboot (on a dosprompt from pc)
boot to stockrecovery
magisk module reboot
but thats is such a XXXX .. i dont have a word for it, in the beginning computers and so are working logical....seems that samsungs security trends are not that logical as needed... i hate samsung :/. there have to be someone who find the "unsu"-files...cannot be....
raeumler said:
i think you can make a little script for rebooting. should work. i really want to know how the bootpartition is corrected, at boot its recovery-from-boot.p as image and install-recovery.sh for reenabling stockrecovery. if you rename this files bootup should work without reflashing boot or recovery. there have to be something similar to the rebootprocess, a script that flashes a sparse image (the *.p file to delete su binary or something like that..) or it just kills the su binary in the folders itself. im to stupid for dmesg and logcat i couldnt find out whats going on at reboot. also the petrus reboot app reboots instant, keys doesnt. seems to be that adb reboot deletes root too. yesterday, somehow my fone did sonething last night, which crashes root again.....i need twrp urgent to make backup. but the binary let not decrypt it. U5 is android 10 bootloader and there are some issues with twrp (decrypt). last time it has saved my backuptry to /data/backupfolder as internal is encrypted. i dont want to factoryreset this phone....is it complicated to build a recovery ? or is there something like a clickitalltogetherapp?
---------- Post added at 09:46 AM ---------- Previous post was at 09:24 AM ----------
following reboot variants keeping root:
hold all keys for 10 seconds
reboot via terminal or script
petrus app
following kills root:
standartreboot with hw-keys
adb reboot (on a dosprompt from pc)
boot to stockrecovery
magisk module reboot
but thats is such a XXXX .. i dont have a word for it, in the beginning computers and so are working logical....seems that samsungs security trends are not that logical as needed... i hate samsung :/. there have to be someone who find the "unsu"-files...cannot be....
Click to expand...
Click to collapse
I didn't messed with boot or recuvery files like the way you DM me.
But I have been noticing strange behavior with petrus app.
Reboot option in petrus app is kinda of like fast reboot or reboot UI. Because all apps opened and present in task manager remain so after reboot with petrus app.
Also once you power off with petrus app,
1= booting up with root key combination results in phone getting freeze Or bootlooping
2=. Force shutting phone again bootloop phone.
3= Going to stock recovery and rebooting system bootloop.
4= going to stock recuvery and shutting off phone from there and then simply pressing power button without key combination, successfully bootup phone with root intact.
This is such a bizzare behaviour
Oh and i am still on Android 9 pie.
Did google remove the option of adopted storage? I don't see it on my SM-T295. I rooted it so I was wondering if there is a Magisk Module that can make sd card act like adopted storage.
Thank you.
Can you tell how did you root your tab please.
Dharmtej said:
Can you tell how did you root your tab please.
Click to expand...
Click to collapse
I have tried many methods dude
Before Installing Magisk
Installing Magisk WILL trip KNOX
Installing Magisk for the first time REQUIRES a full data wipe (this is NOT counting the data wipe when unlocking bootloader). Backup your data before continue.
Download Odin (only runs on Windows) that supports your device.
Unlocking BootloaderUnlocking the bootloader on modern Samsung devices have some caveats. The newly introduced VaultKeeper service will make the bootloader reject any unofficial partitions in some circumstances.
Allow bootloader unlocking in Developer options → OEM unlocking
Reboot to download mode: power off your device and press the download mode key combo for your device
Long press volume up to unlock the bootloader. This will wipe your data and automatically reboot.
Go through the initial setup. Skip through all the steps since data will be wiped again in later steps. Connect the device to Internet during the setup.
Enable developer options, and confirm that the OEM unlocking option exists and is grayed out. This means the VaultKeeper service has unleashed the bootloader.
Your bootloader now accepts unofficial images in download mode
Instructions
Use either samfirm.js, Frija, or Samloader to download the latest firmware zip of your device directly from Samsung servers.
Unzip the firmware and copy the AP tar file to your device. It is normally named as AP_[device_model_sw_ver].tar.md5
Press the Install button in the Magisk card
If your device does NOT have boot ramdisk, check the “Recovery Mode” option
Choose “Select and Patch a File” in method, and select the AP tar file
Start the installation, and copy the patched tar file to your PC using ADB:
adb pull /sdcard/Download/magisk_patched_[random_strings].tar
DO NOT USE MTP as it is known to corrupt large files.
Reboot to download mode. Open Odin on your PC, and flash magisk_patched.tar as AP, together with BL, CP, and CSC (NOT HOME_CSC because we want to wipe data) from the original firmware.
Your device should reboot automatically once Odin finished flashing. Agree to do a factory reset if asked.
If your device does NOT have boot ramdisk, reboot to recovery now to enable Magisk (reason stated in Magisk in Recovery).
Install the Magisk app you’ve already downloaded and launch the app. It should show a dialog asking for additional setup.
Let the app do its job and automatically reboot the device. Voila!
I have tried this one
I have tried flashing unofficial twrp
unofficial twrp 3.4.0 Root Samsung SM-T295 - unofficial twrp
download twrp 3.4.0 root Samsung SM-T295, user who own Samsung SM-T295 can root it by following the below instructions
unofficialtwrp.com
Can you help me please ?