{
"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"
}
TWRP custom recovery for the Tab A SM-T280/T285. Latest build is 3.2.1-1
Disclaimer: you flash these at your own risk. Knox counter will be tripped. Having the stock firmware to hand is also advised.
NOTE: BEFORE MAKING MODIFICATIONS, ON SOME ANDROID 5.1.1/6.0 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
UPDATE 08/01/2018 - TWRP updated to version 3.2.1-1
UPDATE 21/11/2017 - Magisk updated to v14
UPDATE 26/10/2016: GUI lag fix - Lag in the GUI should now be fixed
MTP fix - MTP should now be working
To install TWRP:
1. Flash with ODIN 3.10.7 in the AP slot.
Uncheck Auto reboot.
2. Load the respective file below into the AP slot and hit start.
3. After flashing when ODIN says PASS immediately reboot to recovery by holding POWER + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding the other buttons.
You should now see TWRP recovery.
DOWNLOAD:
TWRP_3.0.2-1_SM-T280_261016
twrp_3.2.1-1_sm-t280_080118
twrp_3.2.1-1_sm-t285_080118
NOTE: at the moment there seems to be a bug which causes the GUI to get a little laggy. If things stop responding just be patient and wait for the GUI to respond. I'm looking into this. (FIXED)
For Systemless Root with SuperSu.
1. Install Supersu via TWRP
SR1-SuperSU-v2.78-SR1-20160915123031
This step only required for the SM-T280
2 . Flash the PRE-ROOTED boot image below with ODIN(AP slot) or TWRP(extract boot.img first from tar file). Current version is [SR1-SuperSU-v2.78-SR1-20160915123031].
supersu_2.78_SR1_systemless_boot_t280
3. Reboot
4. Check you have root
To install Magisk v14:
1. Download Magisk v14 to your device
Magisk v14
2. Install the Magisk v14 zip with TWRP
This step only required for the T280
3. Flash the patched boot image below with TWRP.
magiskv14_boot_aqd1
4. Reboot
5. Install Magisk manager
Magisk Manager
PLEASE LEAVE FEEDBACK IF YOU FIND MY WORK USEFUL. THANKS.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
GUI lag fix - Lag in the GUI should now be fixed
MTP fix
Help me root my phone
Sent from my SM-G903W using XDA Free mobile app
ashyx said:
GUI lag fix - Lag in the GUI should now be fixed
MTP fix
Click to expand...
Click to collapse
interesting, what caused the lag to happen? I initially suspected it to be gpu clock throttling but didn't have time to figure it out
jedld said:
interesting, what caused the lag to happen? I initially suspected it to be gpu clock throttling but didn't have time to figure it out
Click to expand...
Click to collapse
Hi Jed, after trying various different configs in twrp and even modifying the graphics source code it made no difference.
Using the the touch debugger in twrp it was apparent that the touch was responding fine.
So I turned my attention to the kernel.
After several builds of modifying the cpu config making no difference, it turns out TWRP only supports double buffering, but the kernel was forcing triple buffering.
It seems this was causing an extra frame to be displayed causing what seemed like lag and explains why when pressing the screen a second time would cause the frame to update.
The page that was in ram had changed when tapping a button, but the wrong frame in the buffer was displayed until the next touch which then updated the display.
Disabling triple buffering in the kernel fixed the issue.
jaritico said:
PRE-ROOTED boot image can be used on 285? (needed for Systemless Root ) same at magisk patched boot
Click to expand...
Click to collapse
You don't need it for the T285.
Worked perfectly, first time.
Installed supersu via trwp and then img via boot in twrp also.
Thank you for the clear tutorial.
Excellent
just about to root mine now are there any custom roms that can go on it?
ashyx said:
TWRP custom recovery for the Tab A SM-T280. Latest build is 3.0.2-1
Disclaimer: you flash these at your own risk. Knox counter will be tripped. Having the stock firmware to hand is also advised.
NOTE: BEFORE MAKING MODIFICATIONS, ON SOME ANDROID 5.1.1/6.0 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
UPDATE 26/10/2016: GUI lag fix - Lag in the GUI should now be fixed
MTP fix - MTP should now be working
To install TWRP:
1. Flash with ODIN 3.10.7 in the AP slot.
Uncheck Auto reboot.
2. Load the respective file below into the AP slot and hit start.
3. After flashing when ODIN says PASS immediately reboot to recovery by holding POWER + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding the other buttons.
You should now see TWRP recovery.
TWRP_3.0.2-1_SM-T280_261016
NOTE: at the moment there seems to be a bug which causes the GUI to get a little laggy. If things stop responding just be patient and wait for the GUI to respond. I'm looking into this.
For Systemless Root with SuperSu.
1. Install Supersu via TWRP
SR1-SuperSU-v2.78-SR1-20160915123031
2 . Flash the PRE-ROOTED boot image below with ODIN(AP slot) or TWRP(extract boot.img first from tar file). Current version is [SR1-SuperSU-v2.78-SR1-20160915123031].
supersu_2.78_SR1_systemless_boot_t280
3. Reboot
4. Check you have root
To install Magisk v7:
1. Download Magisk v7 to your device
Magisk v7
2. Install the Magisk v7 zip with TWRP
3. Flash the patched boot image below with ODIN(AP slot) or TWRP(extract boot.img first from tar file)
magiskv7_boot_sm-t280
4. Reboot
To Install Magisk v7 with SuperSu:
1. Follow the instructions above to install SuperSu
2. Reboot to TWRP and install the Magisk v7 zip below:
Magisk v7
3. Flash the patched boot image below with ODIN(AP slot) or TWRP(extract boot.img first from tar file):
magiskv7_boot_sm-t280
4. Reboot
5. Install Magisk Manager
PLEASE LEAVE FEEDBACK IF YOU FIND MY WORK USEFUL. THANKS.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
Click to expand...
Click to collapse
I don't know how this is working for others, but installing SuperSu uninstalled android.
Ethan-56 said:
I don't know how this is working for others, but installing SuperSu uninstalled android.
Click to expand...
Click to collapse
It does what? [emoji55]
Also please don't quote the entire OP.
ashyx said:
It does what? [emoji55]
Also please don't quote the entire OP.
Click to expand...
Click to collapse
OK, I'm new to XDA. I installed TWRP and supersu, but when switching to Odin to install that other supersu thing, It wouldn't boot properly I tried deleting supersu, but I uninstalled android entirely. I got the splash screen, but TWRP warned that there was no OS installed. Does XDA Developers have a tutorial on reinstalling Android? I also can't locate the stock firmware and I forgot to back up my system.
Download the stock firmware from sammobile or UPDATO and flash with odin.
T280 comes in on Tuesday, will try this method and report back. Seems fairly easy, thanks for allowing us to have TWRP and root, it will help in debloating this 8gb version i picked up.
Any suggestion how to install Magisk v9?
Root done in five minutes, I can't believe!
Thanks ashyx!
What Gives???
magiskv7_boot_sm-t280 in first post Failed to download, registered in Microsoft Security as a Trojan! Also download page in Android file host has the developer name as "ashyt6" and not "ashyx."
Anyone else noticed this, or did I miss something???
gello924 said:
magiskv7_boot_sm-t280 in first post Failed to download, registered in Microsoft Security as a Trojan! Also download page in Android file host has the developer name as "ashyt6" and not "ashyx."
Anyone else noticed this, or did I miss something???
Click to expand...
Click to collapse
Ffs have you never heard of false positives? [emoji55] What do you expect you're installing files that compromise an operating system.
Also what relevance is it that my AFH user name is different?
ashyx said:
TWRP custom recovery for the Tab A SM-T280. Latest build is 3.0.2-1
Disclaimer: you flash these at your own risk. Knox counter will be tripped. Having the stock firmware to hand is also advised.
NOTE: BEFORE MAKING MODIFICATIONS, ON SOME ANDROID 5.1.1/6.0 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
UPDATE 26/10/2016: GUI lag fix - Lag in the GUI should now be fixed
MTP fix - MTP should now be working
To install TWRP:
1. Flash with ODIN 3.10.7 in the AP slot.
Uncheck Auto reboot.
2. Load the respective file below into the AP slot and hit start.
3. After flashing when ODIN says PASS immediately reboot to recovery by holding POWER + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding the other buttons.
You should now see TWRP recovery.
TWRP_3.0.2-1_SM-T280_261016
NOTE: at the moment there seems to be a bug which causes the GUI to get a little laggy. If things stop responding just be patient and wait for the GUI to respond. I'm looking into this.
For Systemless Root with SuperSu.
1. Install Supersu via TWRP
SR1-SuperSU-v2.78-SR1-20160915123031
2 . Flash the PRE-ROOTED boot image below with ODIN(AP slot) or TWRP(extract boot.img first from tar file). Current version is [SR1-SuperSU-v2.78-SR1-20160915123031].
supersu_2.78_SR1_systemless_boot_t280
3. Reboot
4. Check you have root
To install Magisk v7:
1. Download Magisk v7 to your device
Magisk v7
2. Install the Magisk v7 zip with TWRP
3. Flash the patched boot image below with ODIN(AP slot) or TWRP(extract boot.img first from tar file)
magiskv7_boot_sm-t280
4. Reboot
To Install Magisk v7 with SuperSu:
1. Follow the instructions above to install SuperSu
2. Reboot to TWRP and install the Magisk v7 zip below:
Magisk v7
3. Flash the patched boot image below with ODIN(AP slot) or TWRP(extract boot.img first from tar file):
magiskv7_boot_sm-t280
4. Reboot
5. Install Magisk Manager
PLEASE LEAVE FEEDBACK IF YOU FIND MY WORK USEFUL. THANKS.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
Click to expand...
Click to collapse
followed your instruction & it works, many thanks..much appreciated:good::good::good:
Hi ashyx
To start sorry for my English, I am French and a bad student.
I want to thank you for this guide and all of your contribution on the Android scene :good:
I followed your instructions successfully but I have some questions
Can I install Busybox? If so, is it useful? If yes, how?
I have to do update Magisk v7 to v9?
To finish what is the best solution to extend the internal memory? Actually I used Link2Sd but I'm not satisfied
Thanks again for your work, a little boy will be in the angels when he will receive his gift of Christmas
Error - Security check (boot)
While odin is telling me everything it's correct and shows PASS message on my tablet Sm-t280 shows Security check fail - (boot) and when i restart i can't see any changes,
Oem unlocked and usb debug activated i tried flash with twrp image file and with supersu img file.
I hope your help thanks
Related
I am on OOS 2.2.3 on my Oneplus X. Rooted with Twrp recovery. Was not able to flash the new and official OOS 3.1.3 zip file through TWRP, so flashed Blue_spark TWRP in recovery mode (read somewhere that it could have enabled me to flash OOS 3.1.3). Now the phone boots into OOS 2.2.3 normally, but I cant boot into recovery or bootloader and it gets stuck at the logo screen in both these modes.
Could someone please help me out with this?
Shalabh21 said:
I am on OOS 2.2.3 on my Oneplus X. Rooted with Twrp recovery. Was not able to flash the new and official OOS 3.1.3 zip file through TWRP, so flashed Blue_spark TWRP in recovery mode (read somewhere that it could have enabled me to flash OOS 3.1.3). Now the phone boots into OOS 2.2.3 normally, but I cant boot into recovery or bootloader and it gets stuck at the logo screen in both these modes.
Could someone please help me out with this?
Click to expand...
Click to collapse
As a result of this, I am not even able to do a manual factory reset from the setting menu in OOS 2.2.3, because when i try to initiate this the phone again gets stuck at the logo screen of recovery mode.
Shalabh21 said:
I am on OOS 2.2.3 on my Oneplus X. Rooted with Twrp recovery. Was not able to flash the new and official OOS 3.1.3 zip file through TWRP, so flashed Blue_spark TWRP in recovery mode (read somewhere that it could have enabled me to flash OOS 3.1.3). Now the phone boots into OOS 2.2.3 normally, but I cant boot into recovery or bootloader and it gets stuck at the logo screen in both these modes.
Could someone please help me out with this?
Click to expand...
Click to collapse
blu.spark TWRP v41 uses the updated Marshmallow bootloader from OOS3.1.3, and you are on the Lollipop bootloader.
Lollipop Bootloader recovery won't boot on Marshmallow bootloader and Marshmallow bootloader recovery won't boot on Lollipop bootloader.
If you wanna flash the 3.1.3 zip, then use these instructions.
Download Oxygen OS 3.1.3 full ROM
Download MM based unofficial TWRP
Downloaded Modded SuperSU if you want root
You will require a PC with WinRAR & Notepad++, because as we are running custom ROMs the zip will give an error 7 saying that The package is for OnePlus, this is an onyx, we need to remove that.
Don't worry, its super easy.
- Download the OOS3 zip, copy it to your PCs desktop
- Open it with winRAR, dont extract it, just open it
- There will be a META-INF folder, open it
- Then open com, then google, then android, there will be 2 files here, updater-binary & updater script
- Double click on updater-script
- It will ask which app to use to open the file, then select to open with Notepad++ (designate it from its installed directory if it isn't visible in the initial list)
- The file will look like this
{
"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"
}
- Delete the entire first line that starts with getprop
- Now it should look like this
- Now press Ctrl+S to save the file and close the window
- WinRAR will ask weather to update changes in the archive, say yes to that
- Let it finish its job
- Done !
Moving on to the flashing now...
Assuming you on OOS2.2.3, goto settings, enable Advanced Reboot.
Then reboot to bootloader, this is fastboot mode.
Flash this recovery.
Done, now...
- Copy the modded OOS3 zip into your Device
- Boot into TWRP recovery
- Wipe system, data, cache & dalvik/art cache
- Flash the modified OOS3 zip
- Let it complete
- After it completes, press the wipe cache/dalvik button below
- Now reboot to system
- Complete the initial setup
- Goto settings, unlock developer options by tapping 7 times on build number in about phone
- Enable advanced reboot
- Then reboot to bootloader
- Flash the MM based unofficial TWRP via fastboot
- Remember to boot into this newly flash TWRP before booting into system so that it doesn't overwite it
- Done
Now you are on OOS 3.1.3, and have a working TWRP, you can proceed to flash SuperSU etc to gain root
Joshwin Aranha said:
blu.spark TWRP v41 uses the updated Marshmallow bootloader from OOS3.1.3, and you are on the Lollipop bootloader.
Lollipop Bootloader recovery won't boot on Marshmallow bootloader and Marshmallow bootloader recovery won't boot on Lollipop bootloader.
If you wanna flash the 3.1.3 zip, then use these instructions.
Download Oxygen OS 3.1.3 full ROM
Download MM based unofficial TWRP
Downloaded Modded SuperSU if you want root
You will require a PC with WinRAR & Notepad++, because as we are running custom ROMs the zip will give an error 7 saying that The package is for OnePlus, this is an onyx, we need to remove that.
Don't worry, its super easy.
- Download the OOS3 zip, copy it to your PCs desktop
- Open it with winRAR, dont extract it, just open it
- There will be a META-INF folder, open it
- Then open com, then google, then android, there will be 2 files here, updater-binary & updater script
- Double click on updater-script
- It will ask which app to use to open the file, then select to open with Notepad++ (designate it from its installed directory if it isn't visible in the initial list)
- The file will look like this
- Delete the entire first line that starts with getprop
- Now it should look like this
- Now press Ctrl+S to save the file and close the window
- WinRAR will ask weather to update changes in the archive, say yes to that
- Let it finish its job
- Done !
Moving on to the flashing now...
Assuming you on OOS2.2.3, goto settings, enable Advanced Reboot.
Then reboot to bootloader, this is fastboot mode.
Flash this recovery.
Done, now...
- Copy the modded OOS3 zip into your Device
- Boot into TWRP recovery
- Wipe system, data, cache & dalvik/art cache
- Flash the modified OOS3 zip
- Let it complete
- After it completes, press the wipe cache/dalvik button below
- Now reboot to system
- Complete the initial setup
- Goto settings, unlock developer options by tapping 7 times on build number in about phone
- Enable advanced reboot
- Then reboot to bootloader
- Flash the MM based unofficial TWRP via fastboot
- Remember to boot into this newly flash TWRP before booting into system so that it doesn't overwite it
- Done
Now you are on OOS 3.1.3, and have a working TWRP, you can proceed to flash SuperSU etc to gain root
Click to expand...
Click to collapse
Thank you very much Joshwin Aranha. This worked like a charm.
However I modified the last step and flashed OOS recovery instead. Want to use the phone without root for a while, because the main reason I rooted it in the first place was to install Greenify and save battery (battery used to drain heavily in OOS 2.2.2 and all prior versions), but unfortunately it did not have a great impact on battery life. So going back to stock version for now.
Shalabh21 said:
Thank you very much Joshwin Aranha. This worked like a charm.
However I modified the last step and flashed OOS recovery instead. Want to use the phone without root for a while, because the main reason I rooted it in the first place was to install Greenify and save battery (battery used to drain heavily in OOS 2.2.2 and all prior versions), but unfortunately it did not have a great impact on battery life. So going back to stock version for now.
Click to expand...
Click to collapse
Whatever rocks your boat buddy, glad you sorted that out.
OPX stuck at oneplus logo after following the procedure
@Joshwin Aranha
Hi, I followed the exact same procedure you mentioned, and the process goes smoothly. But when i reboot the phone is stuck at oneplus logo (when i check through my PC for the status it says it is in fastboot mode).
I can easily flash OOS 2.2.3 and move to lollipop , but the problem occurs in OOS 3.1.3 MM
P.S. - i am not rooted.
hbansal24x7 said:
@Joshwin Aranha
Hi, I followed the exact same procedure you mentioned, and the process goes smoothly. But when i reboot the phone is stuck at oneplus logo (when i check through my PC for the status it says it is in fastboot mode).
I can easily flash OOS 2.2.3 and move to lollipop , but the problem occurs in OOS 3.1.3 MM
P.S. - i am not rooted.
Click to expand...
Click to collapse
Which recovery did you use to flash OOS3 ? And did you properly wipe everything ? Try re-flashing.
Joshwin Aranha said:
Which recovery did you use to flash OOS3 ? And did you properly wipe everything ? Try re-flashing.
Click to expand...
Click to collapse
I have used official TWRP that you mentioned in the procedure. I can easily flash CM13 and get my phone running. The problem is only coming in flashing OOS 3.1.3 after OOS 2.2.3.
And yes i have tried it multiple times. With factory reset, user data erase . Everything.
One quirk which i faced 1 time was that while flashing OOS 3 via official twrp 3.0.2.0 , during system verification stage i got an error "system partition has unexpected contents". I cleaned dalvik/cache/data and the error went away but the problem still persists
hbansal24x7 said:
I have used official TWRP that you mentioned in the procedure. I can easily flash CM13 and get my phone running. The problem is only coming in flashing OOS 3.1.3 after OOS 2.2.3.
And yes i have tried it multiple times. With factory reset, user data erase . Everything.
One quirk which i faced 1 time was that while flashing OOS 3 via official twrp 3.0.2.0 , during system verification stage i got an error "system partition has unexpected contents". I cleaned dalvik/cache/data and the error went away but the problem still persists
Click to expand...
Click to collapse
Does the OOS3 zip give any errors ? Or flashes properly ? This seems like a peculiar issue nonetheless..
Joshwin Aranha said:
Does the OOS3 zip give any errors ? Or flashes properly ? This seems like a peculiar issue nonetheless..
Click to expand...
Click to collapse
It does flash properly when i try to flash from OOS 2.2.3->3.1.3 . What i have observed is that as soon as the phone starts it gets stuck on oneplus logo without "android" written below. When i plug it into my system and check the device, it responds to "fastboot devices". I guess there is some issue with the bootloader or something
hbansal24x7 said:
It does flash properly when i try to flash from OOS 2.2.3->3.1.3 . What i have observed is that as soon as the phone starts it gets stuck on oneplus logo without "android" written below. When i plug it into my system and check the device, it responds to "fastboot devices". I guess there is some issue with the bootloader or something
Click to expand...
Click to collapse
Very the md5 of the OOS3 zip to check for a corrupted download.
Original md5 is 162f12d4dfef0142a184e761da868c5f
Joshwin Aranha said:
Very the md5 of the OOS3 zip to check for a corrupted download.
Original md5 is 162f12d4dfef0142a184e761da868c5f
Click to expand...
Click to collapse
MD5 is the same for UNCHANGED zip. i guess md5 will differ on a modified zip due to the changes you mentioned in the process.
Attached in this thread is TWRP repackaged for the SM-T285 built by @ashyx with the UI lag fixed and a new custom kernel that I built.
TWRP-3.1.1-0 for the SM-T285 is now available, you should hop on to this thread for more information.
Update 01/17/2017
==============
TWRP with F2FS support here. Use only if you plan to use the F2FS enabled CM13 builds for the SM-T285.
Update 11/24/2016
==============
* MTP should now be fixed
Installation Instructions
This installation instruction is only for the LTE enabled version of the Samsug galaxy tab A 7" 2016 (SM-T285). If you have a wifi-only version (SM-T280) go to this thread instead.
Disclaimer: I am not responsible for bricked devices and provide no warranty, make sure you made the proper backups and contingencies before you do this procedure. Make sure you have a stock firmware available as a contingency plan
Before going through this make sure your tablet is OEM Unlocked. Make sure you have developer settings enable and there should be a setting there that says OEM unlock. That should be enabled, otherwise your SM-T285 will not accept firmware changes. Also make sure your tablet has sufficient charge and is not about to die.
1. Put your tablet in download mode (Turn off. holding POWER + HOME + VOL DOWN until download mode appears. There will be a warning that about custom firmware blah- blah-blah just hit volume up to proceed). Connect your tablet to your computer using the provided micro usb cable.
2. Flash with ODIN 3.10.7 in the AP slot. Uncheck Auto reboot. (If you are on Linux you can use Heimdall
3. Load the respective attached file (TWRP_3.0.2-1_SM-T285_20161124.zip) in this thread below into the AP slot and hit start.
4. After flashing when ODIN says PASS immediately reboot to recovery by holding POWER + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding the other buttons.
You should now see TWRP recovery.
Root and SuperSU
==============
1. Download the latest available SuperSu Zip from chainfire. Install Zip using TWRP. Reboot phone.
2.Your phone might reboot a couple of times, however at the end of the process you should be rooted.
enjoy!
jedld said:
Attached in this thread is TWRP repackaged for the SM-T285 built by @ashyx with the UI lag fixed and a new custom kernel that I built.
For the installation instructions, should be the same with the SM-T280 in this thread http://forum.xda-developers.com/galaxy-tab-a/development/recovery-samsung-galaxy-tab-a6-sm-t280-t3475381
enjoy!
Click to expand...
Click to collapse
Thanks! The lag is completely gone, making the recovery a joy to use. However, MTP is still not working.
Thanks
I rooted my device (Glaxy Tab a 7" T285)by your method and files.
Next day i saw my device was off ,i pressed power but it could not boot and show this:
Code:
custom binary blocked by frp lock
Afterward i tried to go recovery by pressing Home+Power+volum up but it could not go recovery and show me:
Code:
custom binary blocked by frp lock
Recovery is not Seandroid Enforcing
Therefor my device had been useless.
so I go to download by odin and install a stock ROM.
I search and saw 2 advises:
1)this problem occur if androd version is 5.1.1
2) this problem occur if in developer menu OEM Unlock Option is disabled.
IS THIS ADVISES TRUE? OR THAT PROBLEM HAS OTHER REASON?
I went dev menu and enabled OEM and afterward i did ROOT again.
I have some questions:
1) Is it important Factory reset after install new ROM ? Also after ROOT? Also after unroot?
2) How do i unroot my device?
I have some questions:
1) Is it important Factory reset after install new ROM ? Also after ROOT? Also after unroot?
Click to expand...
Click to collapse
If you install a new rom, then yes you have to factory reset. If it is just to install TWRP I don't think you need to do that.
2) How do i unroot my device?
Click to expand...
Click to collapse
Easiest way is to just flash stock again
Many thanks @jedld, root works perfectly in Galaxy Tab A6 (2016) SM-T285.
Flash twrp.tar by odin, then flash @Chainfire SuperSU SR 2.78 and get rooted !
acornkenya said:
Thanks! The lag is completely gone, making the recovery a joy to use. However, MTP is still not working.
Click to expand...
Click to collapse
MTP should now be fixed with the latest release.
jedld said:
MTP should now be fixed with the latest release.
Click to expand...
Click to collapse
MTP is now working like a charm; thank you
Adam Hui said:
Many thanks @jedld, root works perfectly in Galaxy Tab A6 (2016) SM-T285.
Flash twrp.tar by odin, then flash @Chainfire SuperSU SR 2.78 and get rooted !
Click to expand...
Click to collapse
Pls help subinary files not installed superSU v2.78.SR1
siukbah112 said:
Pls help subinary files not installed superSU v2.78.SR1
Click to expand...
Click to collapse
Just download & flash latest SR5 superSU.zip
@jedld
So just flash the TWRP file with Odin or follow the long steps provided in that thread about the T280?
The links seem to get outdated very quickly so a step by step guide would be really appreciated to avoid mistakes :good:
From beginning to end until I have SuperU :good:
Thanks in advance if I don't reply m8
Shook1 said:
@jedld
So just flash the TWRP file with Odin or follow the long steps provided in that thread about the T280?
The links seem to get outdated very quickly so a step by step guide would be really appreciated to avoid mistakes :good:
From beginning to end until I have SuperU :good:
Thanks in advance if I don't reply m8
Click to expand...
Click to collapse
ok, I've updated the instructions.
finally, I've managed to flash the recovery img to my Stock 285. I have compiled the heimdall from source (github), using Debian 8 Jessie. I also managed to download the stock firmware from sammobile using wget + cookies trick so it can be resumed without requiring a premium account. Thanks for the TWRP
BTW, after installing the SuperSU the SELinux is gone? do I need to flash your custom kernel too?
What do you mean? Was SELinux set to permissive? From what I know the stock kernel has SELinux configured to always enforce and can't be disabled that easily.
SCREENSHOT SELF DESTRUCT AFTER 24 HRS
{
"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"
}
Before I flashed TWRP nad ROOT (SR5-SuperSU-Chainfire) the SELinux can be seen Set to 'Enforcing' then it is now gone? THe SUperSU asked that 'Samsung KNOX has been detected, try to disable KNox?' I clicked 'Yes'. I have not used yet your kernel img, i am still using the 'stock' kernel, i've only flashed recovery img using heimdall 1.4.1
$ sudo heimdall flash --RECOVERY recovery.img
----
This may not be related but. The screen lock password prompt does not popup the keyboard (samsung or any other). I've also tried 'Pi Locker' the PIN code option and the keyboard still won't appear so there s no way to type the code/pin/password. I am trying to set the screen lock to pattern lock but it is greyed out it security settings because I used device encryption. Is there a adb/shell command to enable Pattern Lock method? Thanks
screen shots:
#1 Stock android lock screen
#2 Pi Locker (F-Droid)
gian20 said:
SCREENSHOT SELF DESTRUCT AFTER 24 HRS
Before I flashed TWRP nad ROOT (SR5-SuperSU-Chainfire) the SELinux can be seen Set to 'Enforcing' then it is now gone? THe SUperSU asked that 'Samsung KNOX has been detected, try to disable KNox?' I clicked 'Yes'. I have not used yet your kernel img, i am still using the 'stock' kernel, i've only flashed recovery img using heimdall 1.4.1
$ sudo heimdall flash --RECOVERY recovery.img
----
This may not be related but. The screen lock password prompt does not popup the keyboard (samsung or any other). I've also tried 'Pi Locker' the PIN code option and the keyboard still won't appear so there s no way to type the code/pin/password. I am trying to set the screen lock to pattern lock but it is greyed out it security settings because I used device encryption. Is there a adb/shell command to enable Pattern Lock method? Thanks
screen shots:
#1 Stock android lock screen
#2 Pi Locker (F-Droid)
Click to expand...
Click to collapse
Interesting, I haven't encountered that on my device, then again I'm not using encryption. In that case it could be related to something SuperSU is doing. Unfortunately I have no clue as to what that is, it does touch the sepolicy files in order to allow for root as far as I know.
jedld said:
Interesting, I haven't encountered that on my device, then again I'm not using encryption. In that case it could be related to something SuperSU is doing. Unfortunately I have no clue as to what that is, it does touch the sepolicy files in order to allow for root as far as I know.
Click to expand...
Click to collapse
I don't know if that issue (missing keyboard) was patched with the new stock firmware update on Dec 13, 2016 or if it may block installation of custom firmwares... I ended up not using a password on the lock screen, I deleted the passowrd.key and modified the android settings database to disable password lock, but seperating the necrpytion password using an app.
Unroot without rebloating?
I've rooted using this method (smooth as anything, by the way) in order to remove the various bits of bloatware. What I'm wondering is, is it possible to unroot, take the recovery back to stock and not end up with the bloatware back on?
Reason I'm asking is, my 6 year old loves playing Pokemon Go (honest!), but any of the custom ROMs I've tried meant I couldn't play the game anymore.
Failing that, is there a workaround?
DJThunderGod said:
I've rooted using this method (smooth as anything, by the way) in order to remove the various bits of bloatware. What I'm wondering is, is it possible to unroot, take the recovery back to stock and not end up with the bloatware back on?
Reason I'm asking is, my 6 year old loves playing Pokemon Go (honest!), but any of the custom ROMs I've tried meant I couldn't play the game anymore.
Failing that, is there a workaround?
Click to expand...
Click to collapse
If you have removed the bloatware it should stay like that unless you reflash the stock rom.
My device software info
Baseband version: T285XXU0APH4
Kernel version: 3.10.65-8968674
[email protected] #2
Wed Dec 28 11:00:16 KST 2016
Build Number:
LMY47V.T285XXU0APL7
I had software update few days back so wondering if the TWRP method to root would still work?
I could not select TWRP_3.0.2-1_SM-T285_20161124.zip file in AP slot so I selected TWRP_3.0.2-1_SM-T285_20161124.tar.md5 I hope this correct.
After seeing PASS on odin I could not go into recovery mode directly.
I did press power + vol down and home button but the device rebooted.
And when I did
adb reboot recovery there is not TWRP but stock recovery.
What am I doing wrong? can I still use TWRP method for with latest samsung software?
Is there a easy method to get into recovery mode after running odin?
thank you.
kannaiah said:
My device software info
Baseband version: T285XXU0APH4
Kernel version: 3.10.65-8968674
[email protected] #2
Wed Dec 28 11:00:16 KST 2016
Build Number:
LMY47V.T285XXU0APL7
I had software update few days back so wondering if the TWRP method to root would still work?
I could not select TWRP_3.0.2-1_SM-T285_20161124.zip file in AP slot so I selected TWRP_3.0.2-1_SM-T285_20161124.tar.md5 I hope this correct.
After seeing PASS on odin I could not go into recovery mode directly.
I did press power + vol down and home button but the device rebooted.
And when I did
adb reboot recovery there is not TWRP but stock recovery.
What am I doing wrong? can I still use TWRP method for with latest samsung software?
Is there a easy method to get into recovery mode after running odin?
thank you.
Click to expand...
Click to collapse
It's possible the stock rom overwrites the recovery since you rebooted straight to stock after flashing. Try to flash again but this time when the device reboots, try to press and hold power + home + vol up immediately to attempt to load TWRP recovery.
Unofficial release -TWRP recovery for the Samsung Galaxy Tab S3 - SM-T820/T825, Qualcomm MSM8996
{
"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"
}
TWRP 3.2.1-0 Released
Dec 9, 2017
TWRP 3.2.1-0 is out now for most currently supported devices.
What's new in 3.2.1-0:
What's new in 3.2.1-0:
* minui fixes (cryptomilk)
* Better android-8.0 compatibility in ROM trees (Dees_Troy)
* Fix missing library in android-8.0 (nkk71)
* Fix inconsistent SDCard naming (DevUt)
* Default to TWRP restore instead of adb backup restore to fix restore on fresh TWRP boot (jlask)
Update 18/5/2018
TWRP 3.2.1-1 build released.
Current status: BETA
Features:
MTP working
ADB working
SEANDROID warning fix
TWRP and Kernel built from latest source
Factory Image flashing(see below) >> to be added
NTFS support
F2FS support >> To be added
Twrp app support
IMPORTANT:
PLEASE READ ALL OF THIS POST BEFORE FLASHING ANYTHING TO YOUR DEVICE.
WHATEVER YOU DO BEFORE FLASHING ANYTHING MAKE A BACKUP OF YOUR DEVICE AND HAVE THE STOCK FIRMWARE TO HAND JUST IN CASE, DOWNLOADED FROM SAMMOBILE OR UPDATO.
THIS WILL TRIP KNOX AND MAY VOID YOUR WARRANTY!
Instructions:
Flash with ODIN using the AP slot.
1. Put your device in DOWNLOAD mode.
2. Uncheck Auto reboot.
3. Load the respective file below into the AP slot and hit start.
4. After flashing and ODIN reports PASS immediately reboot to recovery by holding POWER + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding POWER + HOME.
You should now see TWRP recovery.
Failure to implicitly comply with step 4 will result in stock recovery replacing TWRP at first boot
NOTE: Since android 5.1.1 it is necessary to enable OEM Unlock.
Settings -> Developer Options -> OEM unlocking
ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
DOWNLOAD -
Device must be running at least AQD6 or later firmware. Earlier firmware may need the previous builds:
UPDATE: 18/5/2018 TWRP 3.2.1-1
twrp_3.2.1-1_T820_28518
twrp_3.2.1-1_T825_29518
UPDATE: 8/5/2017 TWRP 3.1.0-1
twrp_3.1.0-1_sm-t820_AQD6
twrp_3.1.0-1_sm-t825_AQD6
Previous builds:
SM-T820:
https://www.androidfilehost.com/?fid=745425885120721426
SM-T825:
https://www.androidfilehost.com/?fid=673368273298945058
IMPORTANT! This device enforces dm-verity. ANY modifications or even mounting system will put the device into a bootloop. To prevent this TWRP will ask at first boot if you want to keep system 'Read only' or 'Allow modifications to system'. If you choose to keep 'Read only' you will have to flash TWRP at every boot to recovery.
If you choose to 'Allow' then Magisk needs flashing below to disable dm-verity.
Follow the instructions below to disable dmverity, forced encryption and mount internal storage(DATA):
MARSHMALLOW AND NOUGAT ONLY!:
To disable forced encryption, mount internal storage(DATA) and disable dm-verity:
1. Boot to Twrp
2. Format Data partition using FORMAT DATA button under Wipe options.
(Note: This will wipe the internal storage)
3. Check DATA is mountable.
4. Install Magisk
5. Reboot
OREO ONLY!:
To disable forced encryption, mount internal storage(DATA) and disable dm-verity:
1. Boot to TWRP
2. Install the Forced encryption patch: Tabs3_oreo_forced encryption_disabler
3. Format DATA using the *FORMAT DATA button* under the wipe options.
(NOTE - THIS WILL WIPE ALL INTERNAL STORAGE!)
4. Install Magisk
5. Reboot and check DATA is mountable
Done.
Magisk: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
INSTRUCTIONS TO USE ADB BACKUP:
https://www.droidorigin.com/take-adb-backup-using-twrp-v3-1-0-0/
DEVICE TREE: soon
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
Credits: Me, my testers @suzook, @jonathonalexander, Teamwin
Please note I don't own this device and spend a lot of my free time bringing these builds for you to use and benefit from.
FEEDBACK IS APPRECIATED PLEASE.
THANKS.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
.
RESERVED
Delete
Deleted.
ashyx said:
How do you mean it bootloops? I thought you said that you were able to mount the partitions and flash supersu?
Click to expand...
Click to collapse
I can. It flashes, and boots to TWRP., Partitions are mounted. But I can never reboot to system. It winds up bootlooping, even without flashing SuperSU.
suzook said:
I can. It flashes, and boots to TWRP., Partitions are mounted. But I can never reboot to system. It winds up bootlooping, even without flashing SuperSU.
Click to expand...
Click to collapse
Ah right, the issue isn't twrp, it's dmverity. If you allow modifications to system in twrp it triggers dm-verity which causes a boot loop.
To remedy this you need to disable it by either flashing SuperSU and/or the boot patch
Be aware that after flashing the boot patch you will need to FORMAT (not wipe) /DATA
The other alternative is to disable 'allow modifications to system'
However if you choose to disable modifications you will need to reflash twrp each time you reboot as it will be replaced by stock recovery.
.
ashyx said:
Ah right, the issue isn't twrp, it's dmverity. If you allow modifications to system in twrp it triggers dm-verity which causes a boot loop.
To remedy this you need to disable it by either flashing SuperSU and/or the boot patch
Be aware that after flashing the boot patch you will need to FORMAT (not wipe) /DATA
The other alternative is to disable 'allow modifications to system'
However if you choose to disable modifications you will need to reflash twrp each time you reboot as it will be replaced by stock recovery.
.
Click to expand...
Click to collapse
Format data for me at this point is fine, as I'm starting fresh again. Where is this boot patch? Will give it a try tonight.
suzook said:
Format data for me at this point is fine, as I'm starting fresh again. Where is this boot patch? Will give it a try tonight.
Click to expand...
Click to collapse
Its in the first post.
ashyx said:
Its in the first post.
Click to expand...
Click to collapse
, TWRP flashed, booting, and making backups. Supersu....No good. It flashes, but I have NO ROOT. Thoughts?
its failing on the boot.img patcher it states boot.img not found.
suzook said:
, TWRP flashed, booting, and making backups. Supersu....No good. It flashes, but I have NO ROOT. Thoughts?
its failing on the boot.img patcher it states boot.img not found.
Click to expand...
Click to collapse
I need the recovery log after installing supersu and boot.img patcher.
ashyx said:
I need the recovery log after installing supersu and boot.img patcher.
Click to expand...
Click to collapse
https://drive.google.com/file/d/0BwPAGUQCA8FDN2pGWV9HSmdYNDQ/view?usp=drivesdk
suzook said:
https://drive.google.com/file/d/0BwPAGUQCA8FDN2pGWV9HSmdYNDQ/view?usp=drivesdk
Click to expand...
Click to collapse
Looks like Chainfires script can't find partitions defined as block devices. I must say a bit of an oversight by CF if that's the case.
Try this, recovery log if possible please after installing.
https://www.androidfilehost.com/?fid=529152257862715887
If there is still an issue I will patch the boot image manually.
.
ashyx said:
Looks like Chainfires script can't mount partitions defined as block devices. I must say a bit of an oversight by CF if that's the case.
Try this, recovery log if possible please after installing.
https://www.androidfilehost.com/?fid=529152257862715887
If there is still an issue I will patch the boot image manually.
.
Click to expand...
Click to collapse
Thanks, will give it a go, and post results and recovery log.
Edit...So flash this new recovery, then SuperSU, and the patch?
suzook said:
Thanks, will give it a go, and post results and recovery log.
Edit...So flash this new recovery, then SuperSU, and the patch?
Click to expand...
Click to collapse
Yes apply the patch after supersu to be on the safe side.
Wow, I haven't got the tab in my hands yet, and there's already recovery & root!
Have some beer: Confirmation number: 49581192XS319942M
ashyx said:
Yes apply the patch after supersu to be on the safe side.
Click to expand...
Click to collapse
Quick question, can I flash the latest TWRP you updated with the current TWRP installed? Or should I Odin it?
suzook said:
Quick question, can I flash the latest TWRP you updated with the current TWRP installed? Or should I Odin it?
Click to expand...
Click to collapse
Yep. Just extract it from the tar archive and then select install in twrp.
ashyx said:
Yep. Just extract it from the tar archive and then select install in twrp.
Click to expand...
Click to collapse
Latest TWRP does not mount partitions again
https://drive.google.com/file/d/0BwPAGUQCA8FDcmdCUWNXUnNRdEk/view?usp=drivesdk
Log
suzook said:
Latest TWRP does not mount partitions again
https://drive.google.com/file/d/0BwPAGUQCA8FDcmdCUWNXUnNRdEk/view?usp=drivesdk
Log
Click to expand...
Click to collapse
Damn, even defining the boot device in the command line doesn't allow named partitions to mount.
Back to the previous twrp then.
Looks like manual patching of the boot image is going to be required.
ashyx said:
Damn, even defining the boot device in the command line doesn't allow named partitions to mount.
Back to the previous twrp then.
Looks like manual patching of the boot image is going to be required.
Click to expand...
Click to collapse
Ok, sounds good. Ready to test whenever you need. I'm available rest of day, and all weekend. Thanks.
Hello I change a boot img for those who have a NOTE8 and it is difficult to Root their phone from Oréo&Pie.
I tested For me it works as I met those problem.
The method works with Magisk & Supersu.
WARNING !!
The boot img is from the Rom (N950FXXU3CRC1) do not try on other version.
This operation involves risks: This forum "X.D.A" and / or myself can not be held responsible for any problems encountered during installation or possible handling problems.
READ THE TUTO BEFORE ALL HANDLING (EVEN SEVERAL TIMES)
PREREQUISITES .
1-Have a Galaxy Note 8 charge a 70%
2-Having to install TWRP: https://eu.dl.twrp.me/greatlte/
3-Download the file Boot.img Forcencrypt V6 Modify by but care: https://androidfilehost.com/?fid=673956719939830199
4-Download the file SUPERSU 2.82: https://androidfilehost.com/?fid=818070582850492673
5-Download Magisk V16 file: https://androidfilehost.com/?fid=818070582850503184
6- CAUTION : Simply download Or SUPERSU or Magisk You can install both but Magisk already has a Super_User ..
7-Put all the zip on the map SD.EXT before doing anything ...
installation.
1-Once TWRP install restart your Note 8 in Recovery Mode.
2-Restart your N8 Press (Bixby / Volume + / Power).
3-Go to wipe and select (Wipe_Data) then write YES and check the box at the bottom right.
4-Go back with Back or return if you put it in FR.
5-Press Install Then Image Select Boot for Boot not Recovery The Boot.img Edit by my Force_Encrypte V6 care then swiper when it's done done back.
6-Press Install Select File SUPERSU or MAGISK V16 then made swiper when it's finished restart you are Root.
I WILL WAIT YOUR RETURNS !!!!
{
"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"
}
boot_noverity_N950FXXU3CRD7.img:https://androidfilehost.com/?fid=962339331458990151
boot_novity_N950FXXU3CRDF.img : https://androidfilehost.com/?fid=890278863836292778
boot_no_verity_N950FXXS4CRG1.img : https://androidfilehost.com/?fid=5862345805528063891
boot_no_verity_N950FXXU4CRGA.img : https://androidfilehost.com/?fid=1322778262903993371
boot_no_verity_N950FXXU5CRHA.img : https://androidfilehost.com/?fid=1322778262904006642
boot_no_verity_N950FXXS5CRJ1.img :https://androidfilehost.com/?fid=11410932744536987620
boot_N950FXXU5CRK2.img : https://androidfilehost.com/?fid=11410963190603890268
boot_N950FXXU5DSB2.img : https://androidfilehost.com/?fid=1395089523397910786
boot_N950FXXS5DSB4.img : https://androidfilehost.com/?fid=1395089523397916549
thank you jeannot.
Great
pendor24 said:
thank you jeannot.
Great
Click to expand...
Click to collapse
You're welcome my friend
Envoyé de mon SM-N950F en utilisant Tapatalk
perfect job evrything is fine great
drone1 said:
perfect job evrything is fine great
Click to expand...
Click to collapse
with pleasure a little thank you enough[emoji6]
FAST&FAMOUS TEAM_GNT
1-Have a Galaxy Note 8 charge a 70%
Click to expand...
Click to collapse
Does it need to be exactly 70? what if i am 80 or 60? what happens?
Sorry to ask this question but I'm new to "root" i was in the jailbreak world before my note 8 and I feel like this is deeper stuff hahaha
WillHouli96 said:
Does it need to be exactly 70? what if i am 80 or 60? what happens?
Sorry to ask this question but I'm new to "root" i was in the jailbreak world before my note 8 and I feel like this is deeper stuff hahaha
Click to expand...
Click to collapse
It is especially that it consumes a lot of battery the first time !!
baloo30310 said:
It is especially that it consumes a lot of battery the first time !!
Click to expand...
Click to collapse
Ok, I have a lot of questions, so I'm gonna number them hahaha;
1) Can I restore from backup after the root?
2) The root would need a data wipe right?
3) Could I do a backup before the root and then restore it once i have everything installed?
6) Should I do like a backup on the computer or on samsung cloud?
7) Which apps can't I use after the root?
8) will I be able to have OTA updates?
Thank you sooo much if you answer all of them
WillHouli96 said:
Ok, I have a lot of questions, so I'm gonna number them hahaha;
1) Can I restore from backup after the root?
2) The root would need a data wipe right?
3) Could I do a backup before the root and then restore it once i have everything installed?
6) Should I do like a backup on the computer or on samsung cloud?
7) Which apps can't I use after the root?
8) will I be able to have OTA updates?
Thank you sooo much if you answer all of them
Click to expand...
Click to collapse
1) Yes you can but the data will be encrypted.
2) Yes so that data appears then can not be encrypted
3) Yes via smat switch without root
4) Yes you can make a backup on PC or Cloud.
5) After Root do not use antivirus or Play Protect the only antivirus after Root is you.
6) After the Root over OTA Shift everything will go through Sammobile and Odin.
Here I think you have said a lot of things.
On the other hand under Oréo for the backup of the data serves you of this recovery 3.2.1.0 : https://androidfilehost.com/?fid=746010030569968126
A little thanks on the like:good:
will trip knox as before I assume?
tx!
WillHouli96 said:
Does it need to be exactly 70? what if i am 80 or 60? what happens?
Sorry to ask this question but I'm new to "root" i was in the jailbreak world before my note 8 and I feel like this is deeper stuff hahaha
Click to expand...
Click to collapse
Hi ,
Your actual question hasn't been answered so I thought I'll do that. The 70% battery rule is as the person said, it really is used a lot.
The other reason which may or may not be true in our case is that some phones dont allow you to perform any flash or recovery operation till you have 70% battery or more. That means being on the plus side is fine.
daivatam said:
will trip knox as before I assume?
tx!
Click to expand...
Click to collapse
Knox 0x1 warranti
FAST&FAMOUS_TEAM
daivatam said:
will trip knox as before I assume?
tx!
Click to expand...
Click to collapse
Your knox will change to 0x1 after you can remove some Knox apk
centaur31 said:
Hi ,
Your actual question hasn't been answered so I thought I'll do that. The 70% battery rule is as the person said, it really is used a lot.
The other reason which may or may not be true in our case is that some phones dont allow you to perform any flash or recovery operation till you have 70% battery or more. That means being on the plus side is fine.
Click to expand...
Click to collapse
Thank you for answering
Finally
baloo30310 said:
Hello I change a boot img for those who have a NOTE8 and it is difficult to Root their phone from Oréo.
I tested For me it works as I met those problem.
The method works with Magisk & Supersu.
WARNING !!
The boot img is from the Rom (N950FXXU3CRC1) do not try on other version.
This operation involves risks: This forum "X.D.A" and / or myself can not be held responsible for any problems encountered during installation or possible handling problems.
READ THE TUTO BEFORE ALL HANDLING (EVEN SEVERAL TIMES)
PREREQUISITES .
1-Have a Galaxy Note 8 charge a 70%
2-Having to install TWRP: https://eu.dl.twrp.me/greatlte/
3-Download the file Boot.img Forcencrypt V6 Modify by but care: https://androidfilehost.com/?fid=673956719939830199
4-Download the file SUPERSU 2.82: https://androidfilehost.com/?fid=818070582850492673
5-Download Magisk V16 file: https://androidfilehost.com/?fid=818070582850503184
6- CAUTION : Simply download Or SUPERSU or Magisk You can install both but Magisk already has a Super_User ..
7-Put all the zip on the map SD.EXT before doing anything ...
installation.
1-Once TWRP install restart your Note 8 in Recovery Mode.
2-Restart your N8 Press (Bixby / Volume + / Power).
3-Go to wipe and select (Wipe_Data) then write YES and check the box at the bottom right.
4-Go back with Back or return if you put it in FR.
5-Press Install Then Image Select Boot for Boot not Recovery The Boot.img Edit by my Force_Encrypte V6 care then swiper when it's done done back.
6-Press Install Select File SUPERSU or MAGISK V16 then made swiper when it's finished restart you are Root.
I WILL WAIT YOUR RETURNS !!!!
Click to expand...
Click to collapse
Finally!! Hands down the most straight forward and most accurate tut made, highly appreciated your work !
asokhaki said:
Finally!! Hands down the most straight forward and most accurate tut made, highly appreciated your work !
Click to expand...
Click to collapse
Thank you @asokhaki !!
A small thank you is enough.
baloo30310 said:
Hello I change a boot img for those who have a NOTE8 and it is difficult to Root their phone from Oréo.
I tested For me it works as I met those problem.
The method works with Magisk & Supersu.
WARNING !!
The boot img is from the Rom (N950FXXU3CRC1) do not try on other version.
This operation involves risks: This forum "X.D.A" and / or myself can not be held responsible for any problems encountered during installation or possible handling problems.
READ THE TUTO BEFORE ALL HANDLING (EVEN SEVERAL TIMES)
PREREQUISITES .
1-Have a Galaxy Note 8 charge a 70%
2-Having to install TWRP: https://eu.dl.twrp.me/greatlte/
3-Download the file Boot.img Forcencrypt V6 Modify by but care: https://androidfilehost.com/?fid=673956719939830199
4-Download the file SUPERSU 2.82: https://androidfilehost.com/?fid=818070582850492673
5-Download Magisk V16 file: https://androidfilehost.com/?fid=818070582850503184
6- CAUTION : Simply download Or SUPERSU or Magisk You can install both but Magisk already has a Super_User ..
7-Put all the zip on the map SD.EXT before doing anything ...
installation.
1-Once TWRP install restart your Note 8 in Recovery Mode.
2-Restart your N8 Press (Bixby / Volume + / Power).
3-Go to wipe and select (Wipe_Data) then write YES and check the box at the bottom right.
4-Go back with Back or return if you put it in FR.
5-Press Install Then Image Select Boot for Boot not Recovery The Boot.img Edit by my Force_Encrypte V6 care then swiper when it's done done back.
6-Press Install Select File SUPERSU or MAGISK V16 then made swiper when it's finished restart you are Root.
I WILL WAIT YOUR RETURNS !!!!
Click to expand...
Click to collapse
hi i have a note 8 with the official oreo, so i can flash this and root will work fine? if i flash this boot img can i always restore back to stock firmware?
---------- Post added 3rd May 2018 at 12:01 AM ---------- Previous post was 2nd May 2018 at 11:54 PM ----------
baloo30310 said:
Hello I change a boot img for those who have a NOTE8 and it is difficult to Root their phone from Oréo.
I tested For me it works as I met those problem.
The method works with Magisk & Supersu.
WARNING !!
The boot img is from the Rom (N950FXXU3CRC1) do not try on other version.
This operation involves risks: This forum "X.D.A" and / or myself can not be held responsible for any problems encountered during installation or possible handling problems.
READ THE TUTO BEFORE ALL HANDLING (EVEN SEVERAL TIMES)
PREREQUISITES .
1-Have a Galaxy Note 8 charge a 70%
2-Having to install TWRP: https://eu.dl.twrp.me/greatlte/
3-Download the file Boot.img Forcencrypt V6 Modify by but care: https://androidfilehost.com/?fid=673956719939830199
4-Download the file SUPERSU 2.82: https://androidfilehost.com/?fid=818070582850492673
5-Download Magisk V16 file: https://androidfilehost.com/?fid=818070582850503184
6- CAUTION : Simply download Or SUPERSU or Magisk You can install both but Magisk already has a Super_User ..
7-Put all the zip on the map SD.EXT before doing anything ...
installation.
1-Once TWRP install restart your Note 8 in Recovery Mode.
2-Restart your N8 Press (Bixby / Volume + / Power).
3-Go to wipe and select (Wipe_Data) then write YES and check the box at the bottom right.
4-Go back with Back or return if you put it in FR.
5-Press Install Then Image Select Boot for Boot not Recovery The Boot.img Edit by my Force_Encrypte V6 care then swiper when it's done done back.
6-Press Install Select File SUPERSU or MAGISK V16 then made swiper when it's finished restart you are Root.
I WILL WAIT YOUR RETURNS !!!!
Click to expand...
Click to collapse
and i have 1 more question i have flashed magisk before and everything worked fine but if i leave my phone or restart my phone it says magisk is not installed...i have used the method from youtube from Max Lee will this solution fix that for me also?
baloo30310 said:
Hello I change a boot img for those who have a NOTE8 and it is difficult to Root their phone from Oréo.
I tested For me it works as I met those problem.
The method works with Magisk & Supersu.
WARNING !!
The boot img is from the Rom (N950FXXU3CRC1) do not try on other version.
This operation involves risks: This forum "X.D.A" and / or myself can not be held responsible for any problems encountered during installation or possible handling problems.
READ THE TUTO BEFORE ALL HANDLING (EVEN SEVERAL TIMES)
PREREQUISITES .
1-Have a Galaxy Note 8 charge a 70%
2-Having to install TWRP: https://eu.dl.twrp.me/greatlte/
3-Download the file Boot.img Forcencrypt V6 Modify by but care: https://androidfilehost.com/?fid=673956719939830199
4-Download the file SUPERSU 2.82: https://androidfilehost.com/?fid=818070582850492673
5-Download Magisk V16 file: https://androidfilehost.com/?fid=818070582850503184
6- CAUTION : Simply download Or SUPERSU or Magisk You can install both but Magisk already has a Super_User ..
7-Put all the zip on the map SD.EXT before doing anything ...
installation.
1-Once TWRP install restart your Note 8 in Recovery Mode.
2-Restart your N8 Press (Bixby / Volume + / Power).
3-Go to wipe and select (Wipe_Data) then write YES and check the box at the bottom right.
4-Go back with Back or return if you put it in FR.
5-Press Install Then Image Select Boot for Boot not Recovery The Boot.img Edit by my Force_Encrypte V6 care then swiper when it's done done back.
6-Press Install Select File SUPERSU or MAGISK V16 then made swiper when it's finished restart you are Root.
I WILL WAIT YOUR RETURNS !!!!
Click to expand...
Click to collapse
guys i still have the problem everything works fine but if i restart my device or leave my phone for 1hour it says magisk is not installed? can anyone help me? if i reboot my device for the seccond time ,it says magisk is installed so i dont know what the issue is...
princceaj said:
hi i have a note 8 with the official oreo, so i can flash this and root will work fine? if i flash this boot img can i always restore back to stock firmware?
---------- Post added 3rd May 2018 at 12:01 AM ---------- Previous post was 2nd May 2018 at 11:54 PM ----------
and i have 1 more question i have flashed magisk before and everything worked fine but if i leave my phone or restart my phone it says magisk is not installed...i have used the method from youtube from Max Lee will this solution fix that for me also?
Click to expand...
Click to collapse
Hi guys ! Yes if you are well under Rom (N950FXXU3CRC1).
For Magisk it happens sometimes tries to disable Updating searches .
A small thank you!
In fact you can go back with the original firmxare and Odin
baloo30310 said:
Hi guys ! Yes if you are well under Rom (N950FXXU3CRC1).
For Magisk it happens sometimes tries to disable Updating searches .
A small thank you!
In fact you can go back with the original firmxare and Odin
Click to expand...
Click to collapse
thankq for your answer so i can use magisk but i have to keep rebooting my device everytime it says magisk is not installed? is there no fix for this yet?
How to Root Samsung S23 (SM-S91*B/N/0)
WARNING!
Before you root your device you must be aware that
This will void warranty.
As of now you will lose Samsung Pay and Samsung Pass forever if you root once, even unrooting won't help.
There are many features stop working when you unlock bootloader other than S pay/Pass like Samsung Health, Secure Folder, Galaxy Watch pairing issue, Issue connecting old gear watch (S3 or earlier), Google Pay etc but some ROMs are patched for all these mentioned features, you can use custom ROM or patch it yourself for stock ROM. Still you may trouble using some bank apps and these may fixed by adding these apps to Magisk Hide
There may be some knox features there which you may not able to use but I can't list those as I never used. Just Google It
Patched featurs are working today when writing this, No idea if it may stop working next moment/tomorrow or later
Also to note, once you root, you can't go back to "pre-rooted" state completely. It is one way!
OTA won't work once you root device.
ROOT with caution.
You can unroot & Relock bootloader after flashing stock firmware, but still your warranty flag remain 0x1 and most of countries it still voids warranty. Also after unrooting & relocking bootloader, some knox features never work again.
How to Unlock Bootloader
Follow below four steps to ulock the bootloader
1.Enable Developer Option
Open the Settings app on your Galaxy device.
Choose About > Software Information.
Now tap on Build Number 7 times to enable the developer option.
You’ll get a message “You’re now a developer.”
Now Developer option has been enabled.
2: Enable OEM Unlock
Go to the Settings app again on your device.
Navigate to the Developer option.
Enable the toggle next to OEM Unlocking.
Tap YES to turn on the confirmation dialog box.
3: Boot Your device to Download Mode
While device is booted → Connect device to PC → Select to Restart → As soon as device screen turns off, Press and hold Volume Up + Volume Down simultaneously OR In case device is powered off Press and hold Volume Up + Volume Down simultaneously and connect your device to the PC via a USB Cable.
You can see the warning message on your device and release the pressed keys.
Finally, press the Volume Up key once, and you will be booted into Download Mode.
4: Unlock Bootloader
Once device booted into Download Mode, you will see option to long press Volume up to unlock bootloader,Now, press and hold the Volume Up key for a few seconds., Here, you’ll get a confirmation whether you are sure to proceed.
Use the Volume Up button to reply to the confirmation.
This will erase all the data on your device and unlock the bootloader.
Once completed, your device will automatically boot up to the OS.
Now you have successfully unlocked the bootloader
How to root S23
Instructions for stock non rooted ROM
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
Download and Install latest Magisk apk (Get Latest Magisk apk from here)
Press the Install button in the Magisk card
Choose “Select and Patch a File” in method, and select the AP tar file
When done, copy patched file to PC
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.
Install the Magisk app you’ve already downloaded above 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!
Upgrading the OSOnce you have rooted your Samsung device, you can no longer upgrade your Android OS through OTA. To upgrade your device’s OS, you have to manually download the new firmware zip file and go through the same AP patching process written in the previous section. The only difference here is in the Odin flashing step: do NOT use the CSC tar, but instead use the HOME_CSC tar as we are performing an upgrade, not the initial install.
Important Notes
Never, ever try to restore either boot, recovery, or vbmeta partitions back to stock! You can brick your device by doing so, and the only way to recover from this is to do a full Odin restore with data wipe.
To upgrade your device with a new firmware, NEVER directly use the stock AP tar file with reasons mentioned above. Always patch AP in the Magisk app and use that instead.
Never just flash only AP, or else Odin may shrink your /data filesystem size. Flash AP + BL + CP + HOME_CSC when upgrading.
PS : It is strongly recommended to make EFS backup once you root device and save to safer place like on cloud or PC
For TWRP : Read here
Credit : topjohnwu Guide part taken from Origin guide here
{
"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"
}
Will try this now. Should the other slots BL/CP/CSC be filled with the firmware files when flashing this AP?
zzattack said:
Will try this now. Should the other slots BL/CP/CSC be filled with the firmware files when flashing this AP?
Click to expand...
Click to collapse
No needs, Flash requied file with AP slot onl
I flashed the AP file. I could not enter recovery mode to do factory reset. Device went into boot-loop mode, but after some failed attempts launched recovery by itself. Then I was able to do factory reset, and device boots properly.
Magisk (25.2 from apk in your zip file) still indicates: not installed. Ramdisk yes. Zygisk no (obviously).
zzattack said:
I flashed the AP file. I could not enter recovery mode to do factory reset. Device went into boot-loop mode, but after some failed attempts launched recovery by itself. Then I was able to do factory reset, and device boots properly.
Magisk (25.2 from apk in your zip file) still indicates: not installed. Ramdisk yes. Zygisk no (obviously).
Click to expand...
Click to collapse
You flashed AP file I have provide or one with patched with magisk yourself?
Earlier today I used Magisk alpha to patch the AP from WA6 firmware.
Some minutes ago I flashed AP file from you on top. It only wrote boot and vbmeta.
Any debug info/logging I can provide?
zzattack said:
Earlier today I used Magisk alpha to patch the AP from WA6 firmware.
Some minutes ago I flashed AP file from you on top. It only wrote boot and vbmeta.
Any debug info/logging I can provide?
Click to expand...
Click to collapse
Odin was passed successful?
Kernel I have provided is surely Patched., May be needs to contact Jhon with log. Kindly post in Magisk thread
Yes, no problems from ODIN. I will try to find the magisk thread and useful logging infos.
Magisk log added
zzattack said:
Magisk log added
Click to expand...
Click to collapse
If you can save log from Magisk App - Logs - Save and attach here
Also show me screenshtot of magisk app
Nice!!!
zzattack said:
Magisk log added
Click to expand...
Click to collapse
I have updated link (with debug version), Can you flash again and Install included Magisk? After this take log so I can send to Jhon with debug version. Also take screenshot of magisk app
Logs + magisk screenshot attached with debug image and apk.
zzattack said:
Logs + magisk screenshot attached with debug image and apk.
Click to expand...
Click to collapse
Do you have telegram? If yes inbox me. We can do some test with easy communication
@zzattack or any other user
I have updated link(v3), If anyone available to test new version.
.
This one gave me the "Magisk needs additional setup" prompt. After accepting + reboot, Manager detects magisk correctly and root is functional. Great work!
Would you be able to upload a release kernel too? Thanks so much!
zzattack said:
This one gave me the "Magisk needs additional setup" prompt. After accepting + reboot, Manager detects magisk correctly and root is functional. Great work!
Would you be able to upload a release kernel too? Thanks so much!
Click to expand...
Click to collapse
Great,
That's awesome news!
Thank you very much for testing.
Any other user available to test then let me know, Next test will be for Root with Magisk Stable (25.2)
Debug version already reported working (reported by @zzattack )
.
I'm waiting for my s23 ultra next week and then I'll be able to test.
I'm aware I'll lost Samsung Pay and pass. I really don't care... Don't use it... But, will I have troubles with Google pay and secure folder if rooted?
zzattack said:
This one gave me the "Magisk needs additional setup" prompt. After accepting + reboot, Manager detects magisk correctly and root is functional. Great work!
Would you be able to upload a release kernel too? Thanks so much!
Click to expand...
Click to collapse
does zygisk work?