Related
http://forum.xda-developers.com/showpost.php?p=64916199&postcount=3
Changelogs
10.05.2016 - v2.72 - BETA - RELEASE NOTES
- Add support for ChromeOS boot images (Pixel C)
- supolicy: Fix logging to logcat for some processes on some firmwares
- supolicy: Fix fsck of /data/su.img being denied on some firmwares
- ZIP: Add LESSLOGGING flag
- ZIP: Add KEEPVERITY flag
- ZIP: Add KEEPFORCEENCRYPT flag
- ZIP: Also read flags from /cache/.supersu (aside from /data/.supersu and /system/.supersu)
Yes, baby !
wow! That's a surprise!
BaristaBot said:
wow! That's a surprise!
Click to expand...
Click to collapse
Indeed .. but now we have support.
Just tested 2.72 .. works perfectly.
Installed stock boot.img via TWRP and Supersu.zip directly afterwards ..
Supersu.zip is perfectly modifying the ramdisk and re-signing the kernel to chromeos.
Tested xceed kernel and my pre-rooted kernel too.
Supersu will not modify the ramdisk at all.
"Can't find stock Image, already modified .." and will stop the ramdisk installer.
The system will start anyway, but with "old" ramdisk modifications.
So a fresh clean stock boot.img is recommended.
Install it via TWRP, just before the supersu.zip installation.
No reboot required, nothing.
Download from here ..
http://forum.xda-developers.com/pixel-c/development/twrp-flashable-monthly-update-zip-pixel-t3375591
Running on 2.72 now ... we don't need to build any stock rooted kernels anymore.
Don't be surprised .. after Supersu.zip installation the first boot will look like bootloop, but only once. Same like on other devices as well.
Cheers
After flashing a stock android N preview 2, I installed TWRP and flashed the superSU ZIP (2.72). I can confirm this works perfectly, and i have root on android N preview 2
@NYCHitman1 @cheep5k8 Did you see this? Great news eh?
Samt434 said:
After flashing a stock android N preview 2, I installed TWRP and flashed the superSU ZIP (2.72). I can confirm this works perfectly, and i have root on android N preview 2
Click to expand...
Click to collapse
Great! I'd like to give the N preview a try now, too. Could you please elaborate on how you achieved root with the new SuperSU? Did you have to reflash a custom recovery after flashing Android N?
Which version of TWRP should be used as there are alot of other versions around thats not clear which one is working?
scoobydu said:
Which version of TWRP should be used as there are alot of other versions around thats not clear which one is working?
Click to expand...
Click to collapse
This one
TWRP_dragon_3.0.2-0_v2.img
- Added vendor.img flashing via TWRP. (thx to NYCHitman1 )
Download: https://onedrive.live.com/?authkey=!ABLdSOKIeXgg_XU&id=479EB75F5DD9DA59!117&cid=479EB75F5DD9DA59
Cheers
followmsi said:
This one
TWRP_dragon_3.0.2-0_v2.img
- Added vendor.img flashing via TWRP. (thx to NYCHitman1 )
Download: https://onedrive.live.com/?authkey=!ABLdSOKIeXgg_XU&id=479EB75F5DD9DA59!117&cid=479EB75F5DD9DA59
Cheers
Click to expand...
Click to collapse
Using this version, TWRP loads but it cannot see my files on the internal sdcard, so I cannot install supersu, or anything else for that matter.
Not sure what I am missing.
Edit: Ok, didn't do the format data piece doing that now
Edit2: I managed to boot with boot-ryu-MXC89F-su-nocrypt-r205 and then copy the latest supersu to my sdcard. I rebooted into TWRP and installed Supersu successfully. Rebooted to system resulted in a boot loop to recovery?
Going into security to check encryption status causes setting to fc.
Edit 3 [Resolved] Copied the only kernel that would boot, as well as the clean boot.img from the latest factory images. Booted into TWRP and first flashed the clean boot.image from the factory images and then installed supersu successfully this time. I tried before with the boot.img from here -> http://superuser.phh.me/nexus/ryu/MXC89F/ but couldn't get supersu to install.
@Chainfire Thanks!! for supersu and flashfire support.
Great news! Any idea if supersu works with complete stock and encryption enabled?
And TWRP_dragon_3.0.2-0_v2.img doesn't solve the encryption problem yet, right?
doumer said:
Great news! Any idea if supersu works with complete stock and encryption enabled?
And TWRP_dragon_3.0.2-0_v2.img doesn't solve the encryption problem yet, right?
Click to expand...
Click to collapse
For me on a previously unrooted encrypted device I couldn't get it to work by just installing it and supersu, no.
But that may have been user error on my part, but my guess is that encryption was causing an issue with just the v2 TWRP installed as it could not see my data partition, even after a format.
scoobydu said:
Using this version, TWRP loads but it cannot see my files on the internal sdcard, so I cannot install supersu, or anything else for that matter.
Not sure what I am missing.
Edit: Ok, didn't do the format data piece doing that now
Edit2: I managed to boot with boot-ryu-MXC89F-su-nocrypt-r205 and then copy the latest supersu to my sdcard. I rebooted into TWRP and installed Supersu successfully. Rebooted to system resulted in a boot loop to recovery?
Going into security to check encryption status causes setting to fc.
Edit 3 [Resolved] Copied the only kernel that would boot, as well as the clean boot.img from the latest factory images. Booted into TWRP and first flashed the clean boot.image from the factory images and then installed supersu successfully this time. I tried before with the boot.img from here -> http://superuser.phh.me/nexus/ryu/MXC89F/ but couldn't get supersu to install.
@Chainfire Thanks!! for supersu and flashfire support.
Click to expand...
Click to collapse
Three lines above your thread ..
Tested xceed kernel and my pre-rooted kernel too.
Supersu will not modify the ramdisk at all.
"Can't find stock Image, already modified .." and will stop the ramdisk installer.
The system will start anyway, but with "old" ramdisk modifications.
So a fresh clean stock boot.img is recommended.
As well the Phhuson kernel is not pre-rooted for SuperSU.
( boot-ryu-MXC89F-su-nocrypt-r205 )
NEW Root access:
For root access: Pls install latest "stock" kernel and install SuperSU.zip version 2.72 directly afterwards - no reboot in between.
Hope this help all people in the same situation ..
Cheers
doumer said:
Great news! Any idea if supersu works with complete stock and encryption enabled?
And TWRP_dragon_3.0.2-0_v2.img doesn't solve the encryption problem yet, right?
Click to expand...
Click to collapse
Yes, it doesn´t solve the problem ..
There were no encryption related changes in this TWRP release.
But .... we have a new SuperSU now ..
Look here .. should be tested from the encryption fans .. Maybe this works on Pixel C too.
http://forum.xda-developers.com/htc...bootloader-t3365986/post66837323#post66837323
EDIT 2: Figured I might as well detail my complete procedure here, so others can confirm whether it works for them (or not):
Unlocked bootloader via HTC Dev
Flash TWRP
Boot into TWRP (Cancel decryption prompt & leave system read-only on boot)
Backup "Boot" and ""System Image" in TWRP to External SD
Wipe - Format Data (or Wipe Encryption) in TWRP
Boot device and let it re-encrypt
Reboot back into TWRP (Cancel decryption prompt & leave system read-only on boot)
In adb shell or TWRP Terminal, echo KEEPFORCEENCRYPT=true>>/cache/.supersu
Flash BETA-SuperSU 2.72 from external SD card
Reboot back to system, and the device will reboot itself once as SuperSU installs
Do the SunShine
Boot into TWRP, restore stock boot and system image backup & Wipe - Format Data (or Wipe Encryption) again
Reboot device and let it encrypt again
Reboot back into TWRP (Cancel decryption prompt & leave system read-only on boot)
In adb shell or TWRP Terminal, echo KEEPVERITY=true>>/cache/.supersu (the file should still be there, so both commands will now be present)
Flash BETA-SuperSU 2.72 (again) from external SD card
Reboot back to system, and the device will reboot itself once as SuperSU installs (again)
Now you're rooted, with pristine stock system image and with forced encryption and dm-verity still enabled. In this state, you should be able to Download OTAs, use Android Pay, etc.
Inside the SuperSU.zip are more informations ...
Overridable variables (shell, /system/.supersu, /cache/.supersu,
# /data/.supersu):
# SYSTEMLESS - Do a system-less install? (true/false, 6.0+ only)
# PATCHBOOTIMAGE - Automatically patch boot image? (true/false,
# SYSTEMLESS only)
# BOOTIMAGE - Boot image location (PATCHBOOTIMAGE only)
# STOCKBOOTIMAGE - Stock boot image location (PATCHBOOTIMAGE only)
# BINDSYSTEMXBIN - Poor man's overlay on /system/xbin (true/false,
# SYSTEMLESS only)
# PERMISSIVE - Set sepolicy to fake-permissive (true/false, PATCHBOOTIMAGE
# only)
# KEEPVERITY - Do not remove dm-verity (true/false, PATCHBOOTIMAGE only)
# KEEPFORCEENCRYPT - Do not replace forceencrypt with encryptable (true/
# false, PATCHBOOTIMAGE only)
# Shell overrides all, /data/.supersu overrides /cache/.supersu overrides
# /system/.supersu
Hope this helps .. but the external sd card could be tricky.
Cheers
followmsi said:
Three lines above your thread ..
Tested xceed kernel and my pre-rooted kernel too.
Supersu will not modify the ramdisk at all.
"Can't find stock Image, already modified .." and will stop the ramdisk installer.
The system will start anyway, but with "old" ramdisk modifications.
So a fresh clean stock boot.img is recommended.
As well the Phhuson kernel is not pre-rooted for SuperSU.
( boot-ryu-MXC89F-su-nocrypt-r205 )
NEW Root access:
For root access: Pls install latest "stock" kernel and install SuperSU.zip version 2.72 directly afterwards - no reboot in between.
Hope this help all people in the same situation ..
Cheers
Click to expand...
Click to collapse
Is this the case if you are already stock, unrooted and encrypted? as I had copied Supersu to my sdcard but TWRP could not see it.
boot-ryu-MXC89F-su-nocrypt-r205 was used only to boot the device after twrp was installed, as the stock boot.img would not boot and caused a recovery boot loop.
boot-ryu-MXC89F-su-nocrypt-r205 got me out of the bootloop and allowed me to recopy supersu to the sdcard, but I could not see if encrypttion was now disabled, as settings/security caused a force close of settings.
I had assumed that boot-ryu-MXC89F-su-nocrypt-r205 allowed me to disable encryption and copy supersu to sdcard, which twrp could then find and supersu worked successfully.
scoobydu said:
Is this the case if you are already stock, unrooted and encrypted? as I had copied Supersu to my sdcard but TWRP could not see it.
Click to expand...
Click to collapse
If you are on stock and unrooted it works the way above.
Sorry, I am not sure on encryption now.
Removed it on the first day.
Before copying SuperSu to data .. just followed the guide.
Needs to be verified if 3.0.0.0 version from xceed is able to access encrypted data ..
Sorry, can't help you better here ...
scoobydu said:
Is this the case if you are already stock, unrooted and encrypted? as I had copied Supersu to my sdcard but TWRP could not see it.
boot-ryu-MXC89F-su-nocrypt-r205 was used only to boot the device after twrp was installed, as the stock boot.img would not boot and caused a recovery boot loop.
boot-ryu-MXC89F-su-nocrypt-r205 got me out of the bootloop and allowed me to recopy supersu to the sdcard, but I could not see if encrypttion was now disabled, as settings/security caused a force close of settings.
I had assumed that boot-ryu-MXC89F-su-nocrypt-r205 allowed me to disable encryption and copy supersu to sdcard, which twrp could then find and supersu worked successfully.
Click to expand...
Click to collapse
I saw only the first part of your answer ...
You got recovery boot-loop after installing TWRP ?
Never had any reboot issues, but I had always unencrypted data partition and could access my SuperSu.zip - all the time.
Never had to reboot without unchanged fstab nor stock kernel, as was able to flash SuperSu all the time.
As said before, I did remove encryption directly.
I did use xceed kernel for this .. some time ago.
Needs to be checked if xceed 3.0.0.0 TWRP has also problems to boot into system with stock kernel, was always used with xceed kernel together.
Version 3.0.2.0.img is using xceed only settings.
Version 3.0.2-0_v2.img has some parts from NYCHitman1 included.
Needs to be verified...
But we may need to adapt the instructions .. and may still need a stock rooted kernel for initial SuperSU installation.
Uploaded new TWRP version .. as TWRP flashable zip !
Just install this version with your current TWRP version and reboot to recovery again.
Have a look .. OTG is working now.
Update.ZIP_TWRP_dragon_3.0.2-0_v4.zip
Just made a fresh backup to my usb-stick via USB-OTG ..
Cheers
Samt434 said:
After flashing a stock android N preview 2, I installed TWRP and flashed the superSU ZIP (2.72). I can confirm this works perfectly, and i have root on android N preview 2
Click to expand...
Click to collapse
Is your device still encrypted ?
Did you format the /data partiton inside TWRP ?
How did you access the SuperSu.zip file inside TWRP ?
Did you install other kernel for intermediate reboot into system to decrypt data ?
A lot of questions .. but it helps to understand problems better
Thanks
I just successfully rooted the Android N beta with this!
I upgraded from Preview 2 via flash-all without wiping data.
This is my installation process [last post is OK]
https://forum.xda-developers.com/galaxy-s5/help/wifi-problem-flashed-lineageos-t3576865
Below are screens from CATLOG [not full tho]
If I try to update binaries in TWRP it stops [nothing in TWRP logs about SU], restarts and stops during Lineage loading screen forever.
So I flash ROM again, and SuperSU from TWRP to fix it.
I was reading that after flashing SuperSU - during first restart it should ask me something like "DO you want to keep root" - it doesn't happen.
SuperSU has no apps listed with root access, but root is OK. TitaniumBackup works, but I'm afraid some of the apps doesn't work properly
Now I'm using
lineage-14.1-20170329-nightly-klte-signed.zip
addonsu-ARM-signed_14.1
SM-G900F
Is there a way to have it done?
I remember like trough a fod that once I was setting permissions in Terminal for some files before updating SU? AM I correct?
Thanks for reding
Hi,
With LineageOS, you must only use one root method otherwise problems will occur. The addonSU zip and SuperSU are not the same thing.
The provided root SU zip from Lineage should be enough to give root permissions for apps. If you want to use SuperSU instead of the SU provided by the Lineage team, you must not flash the addonSU zip.
Saber said:
Hi,
With LineageOS, you must only use one root method otherwise problems will occur. The addonSU zip and SuperSU are not the same thing.
The provided root SU zip from Lineage should be enough to give root permissions for apps. If you want to use SuperSU instead of the SU provided by the Lineage team, you must not flash the addonSU zip.
Click to expand...
Click to collapse
I have tried to flash everything and indeed only addonsu-ARM-signed_14.1 is working from TWRP level. Although SuperSU from APK is working OK [latest SR4].
So root seems to be fine for browsing into root or TB! is not complaining about root, but I can not update SU binary - I have also updated Lineage to today's nightly - same thing.
I've used an S4 with lineage and flashing supersu doesn't work. ONE app in particular will not work because the su part of lineage (and old cyanogenmod) doesn't cooperate; it needs supersu for some reason. I was originally on Cyanogenmod from about a year ago, and tried flashing supersu and had this very problem, which is why I tried lineage, but lineage doesn't work and I cannot flash supersu either. I can install from the play store, but it won't update the binary; flashing in recovery fails (in both older cyanogenmod and lineage os) at the boot image patcher step.
supersu 2.79 said:
Finding boot image
Boot image: /dev/block/mmcblk0p20
Extracting ramdisk
Decompressing ramdisk
Failure, aborting
Click to expand...
Click to collapse
The only reason I'm having to resort to this is because Samsung has a problem with their s7 screens failing and won't do a recall...so I'm having to use an older phone and trying to setup my rooted apps, all of which work with the standard Cyanogenmod root or lineage+su addon, except for one app.
EDIT:
Ah-ha, system mode may be the solution, but I'm still trying to get it to boot without getting stuck! I haven't tinkered with supersu in well over a year, and I didn't even know there were two methods for it now.
https://forum.xda-developers.com/apps/supersu/v2-64-2-66-supersu-mode-t3286120
Hello,
I have followed the step of the "X727 (US Model) Persistent bootloader unlock from 5.8.019s" and successfully unlocked the bootloader and loaded various customized ROM and they boot and work OK. The only issues is that I am not able root my device. I have tried to install different version of SuperSU in TWRP but during the the installation at the "Boot image patcher" stage, it shows:
**********************
Boot image patcher
**********************
-Finding boot image
--- Boor image: /dev/block/sde18
- Decompressing ramdisk
- Checking patch status
--- Already patched. attempting to find stock backup
--- Stock remote failed, attempting ramdisk restore
- checking patch status
- Patching sepolicy
--- Failure, aborting
After reboot, the SuperSU app is there but the device is not rooted and SuperSU keeps saying a binary update is required and it downloads it but fail to install. Verified by RootChecker app and LukcyPatcher, the device is not rooted. Anyone have the experience? How can I solve it? Thank you ~~~
dennytsai said:
Hello,
I have followed the step of the "X727 (US Model) Persistent bootloader unlock from 5.8.019s" and successfully unlocked the bootloader and loaded various customized ROM and they boot and work OK. The only issues is that I am not able root my device. I have tried to install different version of SuperSU in TWRP but during the the installation at the "Boot image patcher" stage, it shows:
**********************
Boot image patcher
**********************
-Finding boot image
--- Boor image: /dev/block/sde18
- Decompressing ramdisk
- Checking patch status
--- Already patched. attempting to find stock backup
--- Stock remote failed, attempting ramdisk restore
- checking patch status
- Patching sepolicy
--- Failure, aborting
After reboot, the SuperSU app is there but the device is not rooted and SuperSU keeps saying a binary update is required and it downloads it but fail to install. Verified by RootChecker app and LukcyPatcher, the device is not rooted. Anyone have the experience? How can I solve it? Thank you ~~~
Click to expand...
Click to collapse
Did you flash the latest SU version ? http://download.chainfire.eu/1021/SuperSU/SR3-SuperSU-v2.79-SR3-20170114223742.zip
If not worked, flash Magisk here : https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Hope it will work. Good luck :fingers-crossed:
bayad said:
Did you flash the latest SU version ? http://download.chainfire.eu/1021/SuperSU/SR3-SuperSU-v2.79-SR3-20170114223742.zip
If not worked, flash Magisk here : https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Hope it will work. Good luck :fingers-crossed:
Click to expand...
Click to collapse
Thanks for your suggestion.
I flash the Majisk v12 in TWRP. It did not show any errors during installation but it doesn't work. After reboot, I cannot see the app. I install Majisk Manager and it confirms that the phone is not rooter and it cannot detect the location of bootimage. Is it possible that something wrong with my bootimage? I followed the instruction of the "X727 (US Model) Persistent bootloader unlock from 5.8.019s" thread and I am now able to flash any custom ROM but just cannot root. Anyone have similar experience??
hi fir me same problem.... i an on N and i flash super su. 78 and its ok.... i think compatibility problem ??
dennytsai said:
Hello,
I have followed the step of the "X727 (US Model) Persistent bootloader unlock from 5.8.019s" and successfully unlocked the bootloader and loaded various customized ROM and they boot and work OK. The only issues is that I am not able root my device. I have tried to install different version of SuperSU in TWRP but during the the installation at the "Boot image patcher" stage, it shows:
**********************
Boot image patcher
**********************
-Finding boot image
--- Boor image: /dev/block/sde18
- Decompressing ramdisk
- Checking patch status
--- Already patched. attempting to find stock backup
--- Stock remote failed, attempting ramdisk restore
- checking patch status
- Patching sepolicy
--- Failure, aborting
After reboot, the SuperSU app is there but the device is not rooted and SuperSU keeps saying a binary update is required and it downloads it but fail to install. Verified by RootChecker app and LukcyPatcher, the device is not rooted. Anyone have the experience? How can I solve it? Thank you ~~~
Click to expand...
Click to collapse
Flash the lastest version of ElementalX Kernel and reboot system. After, flash the supersu. The ElementalX Kernel is required before attempting to root.
Greeting from Chile
I am trying to re-root my SM-T380 after updating to Pie and am following the latest process per [TWRP 3.2.1-1] [ROOT] Tab A SM-T380/T385 - 10/02/2018 but am running into some issues with steps 3 & 4.:
Boot to TWRP
Format the Data partition (not wipe) using the FORMAT DATA button under Wipe options
Install the memory decryption patch
Assume this is the file found in Ashyx's siganture Samsung encryption disable patch but I can't find any mirrors when trying to download it. Is this the right file for the memory decryption patch?
Install the modified kernel
The file for the SM-T380 found in this post appears to be for the T380DXU3CSI5 but the current stock image is T380DXU3CSL2 for the latest firmware installation (Jan 2020 security patch). I assume a new kernel is needed for this latest version. Is that the case? Also, the file is in tar format but need in zip format to flash in TWRP. Is it as simple as repackaging the tar into a zip file instead?
Install Magisk
Thanks for the help!
I will write out what I just got to work with the latest update of Android Pie for the Samsung Galaxy Tab A T380 running T380DXU3CSL2, security patch January 2020. I have tried all of the methods on the main TWRP/Root thread (which is now closed) and only had success with one.
To clarify, yes - using the patched boot.img from ashyx that was made from T380DXU3CSI5 WILL work with T380DXU3CSL2 (latest as of time of writing) just fine. Make sure to flash Stock first and OEM Unlock.
Ashyx does give some files still needed in his/her first post on the main TWRP thread, but the boot image and the DM-verity are buried within a 66 page thread. Out of respect for ashyx's wishes I will not direct link to files. Get TWRP from the first post here. The patched boot image and DM verity no encrypt get from the guide here by user zfk110. Pg. 65 of the TWRP thread. The guide itself did not work for me though. Just grab the files.
So, files you will need:
>twrp_3.2.3-1_sm-t380_oo_4119.tar (TWRP)
>T380DXU3CSI5_patched_boot_111119.tar (boot.img inside the .tar)
>Latest Magisk version here
>Tab_A_2017_Pie_forced+encryption_disabler-1.zip (no-verity-no-encrypt)
Not only have I found RMM Bypass unnecessary, but in my many trials I think maybe it was causing an issue for me. Perhaps someone much smarter than I can explain, but there is no setting in build.prop to need it - I did check.
TWRP/Root:
>Flash TWRP with Odin with "Auto Reboot" setting turned off: (file: twrp_3.2.3-1_sm-t380_oo_4119.tar in AP slot)
>Boot straight to TWRP (home + vol down + power to get out of download mode then as soon as the screen flashes swap to home + vol up + power),
>In TWRP main menu press "Wipe" and the "Format Data", type "yes" to proceed.
>Reboot to TWRP by going back to main menu of TWRP, select "Reboot" then "Recovery"
>Install boot.img to your boot partition from your external SD card in TWRP (there is a YT video how to do this within TWRP if you need help, just Google it. The file you need is: T380DXU3CSI5_patched_boot_111119.tar then extract boot.img from that for TWRP (use ZArchiver or a program that will unzip .tar). It MUST be in .img to install it with the TWRP "Image" button. TWRP won't even read that the .tar is there, and I don't recommend Odin for this)
>Install Magisk from your external SD card (I used the latest, 20.4 just fine)
>Install the DM-Verity Forced Encryption Patch from your external SD card (file: Tab_A_2017_Pie_forced+encryption_disabler-1.zip)
>Wipe Cache and Dalvik
>Reboot to System
Notes:
Boot image must be first before flashing the others. I tried it after Magisk et.al as with a number of people's directions and several other configurations in addition both in TWRP and with Odin (and the other boot image as well on the thread: t380_boot_pp.img - no luck on XSA for me at least) and it caused a bootloop every time. I don't know why. The smart guys are on the TWRP thread but it's closed (and confusing). I just try things.
To the other OP question here - use the later version of the DM-verity patch - the original one (no-verity-no-encrypt_ashyx) you are referring to is a different size and structure (I have it archived) so it is probably necessary to use the Tab_A_2017_Pie_forced+encryption_disabler-1.zip. It's on pg.65 on zfk110's guide that I linked above (though again, the guide itself did not work for me).
Edit: I know someone could find this method out from the big thread but I know what it is like to feel newby and get confused and want to give up. And the number of different methods and files on that dang thread was a bit maddening honestly and frequently in direct conflict with each other.
Thank you for the guide Winston Churchill, I tried following it for my device Samsung Tab A T380 (build T380DXU3CTH4) but I am stuck at installing Magisk. The patched boot.img is installed successfully but when I go to the system and Magisk does not appear so I have to install it manually with Magisk.apk file. Then when I check the status it says "Installed N/A, Ramdisk Yes, A/B No, SAR No" and root is not active.
I really appreciate any help on this!!
Many thanks Winston Churchill, this worked for me after many failed efforts using other methods and procedures.
Just one or two cautions, as I had to go through the process twice -- because the first time I got locked out with an "unauthorized" firmware notice on the first reboot. I'm not sure if it was because I did not flash the RMM Bypass the first time, or I didn't make sure my OEM Unlock was showing after flashing TWRP, etc. At any rate, I ended up with the RMM Prenormal state.
So I started over . . .
- Odin-flashed my Pie version 3CSI5 one more time
- Setup, went through the time and software update thing to get OEM Unlock to show, and enabled USB Debugging
- Odin-flashed twrp_3.2.3-1_sm-t380_oo_4119.tar
- In TWRP, ran Format Data, rebooted recovery and Formatted again (this has been necessary or advised for other Samsung devices in the past, so I did it here too)
- Then flashed in TWRP:
--- (1) boot.img
--- (2) Magisk 20.4
--- (3) Tab_A_2017_Pie_forced+encryption_disabler-1.zip
--- (4) RMM-State_Bypass_Mesa_v2.zip.
- Wiped Dalvik and Cache
- Rebooted to system
- Made sure OEM Unlock showed and USB Debugging was enabled
- Installed Magisk Manager 7.5.1
- Opened Magisk Manager and made sure Magisk was installed (sometimes it takes a reboot to see Magisk, and sometimes I've actually had to go back into TWRP and reflash it).
All good. So I installed my usual root-needed apps, Speed Software Root explorer, Titanium Backup, Adaway and Power Toggles. All are now rooted and working (including Titanium Backup!!!) and my Android Pie appears to be very stable. Soooo . . . quickly back to TWRP to run a Backup in case something breaks!
I have never had so much trouble rooting any Android device before. The T380 is a nice size and very nice weight, but man oh man . . . I was beginning to wonder if I would ever get it rooted. I can't tell you how much I appreciate (finally) finding this thread and specifically your post.
Moondroid said:
Many thanks Winston Churchill, this worked for me after many failed efforts using other methods and procedures.
Just one or two cautions, as I had to go through the process twice -- because the first time I got locked out with an "unauthorized" firmware notice on the first reboot. I'm not sure if it was because I did not flash the RMM Bypass the first time, or I didn't make sure my OEM Unlock was showing after flashing TWRP, etc. At any rate, I ended up with the RMM Prenormal state.
So I started over . . .
- Odin-flashed my Pie version 3CSI5 one more time
- Setup, went through the time and software update thing to get OEM Unlock to show, and enabled USB Debugging
- Odin-flashed twrp_3.2.3-1_sm-t380_oo_4119.tar
- In TWRP, ran Format Data, rebooted recovery and Formatted again (this has been necessary or advised for other Samsung devices in the past, so I did it here too)
- Then flashed in TWRP:
--- (1) boot.img
--- (2) Magisk 20.4
--- (3) Tab_A_2017_Pie_forced+encryption_disabler-1.zip
--- (4) RMM-State_Bypass_Mesa_v2.zip.
- Wiped Dalvik and Cache
- Rebooted to system
- Made sure OEM Unlock showed and USB Debugging was enabled
- Installed Magisk Manager 7.5.1
- Opened Magisk Manager and made sure Magisk was installed (sometimes it takes a reboot to see Magisk, and sometimes I've actually had to go back into TWRP and reflash it).
All good. So I installed my usual root-needed apps, Speed Software Root explorer, Titanium Backup, Adaway and Power Toggles. All are now rooted and working (including Titanium Backup!!!) and my Android Pie appears to be very stable. Soooo . . . quickly back to TWRP to run a Backup in case something breaks!
I have never had so much trouble rooting any Android device before. The T380 is a nice size and very nice weight, but man oh man . . . I was beginning to wonder if I would ever get it rooted. I can't tell you how much I appreciate (finally) finding this thread and specifically your post.
Click to expand...
Click to collapse
So many conflicting instructions - Why exactly are people flashing this modified boot image and then magisk? Correct me if Im wrong, but isnt that what installing magisk DOES (patches the boot image) when you rename the magisk apk to a zip and install in TWRP? I only FINALLY got this working after I ignored the patched boot.img step completely and simply - flash twrp in odin, reboot rocovery, format data, reboot recovery, flash magisk, disable verity whatever, reboot system..
Dick_Stickitinski said:
So many conflicting instructions . . .
. . . isnt that what installing magisk DOES (patches the boot image) when you rename the magisk apk to a zip and install in TWRP? . . .
Click to expand...
Click to collapse
Magisk patches boot.img for Root access. Sometimes there are also other reasons for flashing a boot.img. I'm not an Android coder so I can't explain every reason why flashing boot.img might be necessary in this case.
. . . "rename the magisk apk to a zip" . . . you renamed a Magisk Manager apk to "zip" for flashing in TWRP? How did that work?
At any rate, my method worked for me and yours (however you actually did it) worked for you. I can say for sure that Android itself can be quirky, for example, my recent experiences with a Galaxy S9 on Pie where, after reflashing the exact same build 5-6 times -- because trying to set a security PIN for some screwy reason kept crashing the system (?!!) -- from one reflash to the next I got different app-disabling experiences. For example, a few built-in apps (like google movies etc) showed the option to Uninstall instead of the expected Disable. The same generic reason why an S8 G950U on Pie v8 can be rooted successfully using @jrkruse's Extreme Syndicate method, and other S8 G950s on Pie v8 will brick. Quirky? Weird, I don't know, can't explain, I just go with the flow as it flows and count my blessings when it works.
Moondroid said:
. . . "rename the magisk apk to a zip" . . . you renamed a Magisk Manager apk to "zip" for flashing in TWRP? How did that work?
Click to expand...
Click to collapse
Yeah, you can rename the APK to zip & flash it in TWRP
The Magisk Manager APK can now be flashed from within TWRP
Magisk is now distributed as part of the Manager APK, meaning you no longer need to flash a separate ZIP file from a custom recovery.
www.xda-developers.com
However, I spoke too soon... I got it to stop bootlooping and actually got it to boot into system, and magisk manager is installed, but still not rooted. When flashing magisk in recovery again (or even extracting the boot.img & patching it in magisk manager, it recognizes it as a magisk-patched boot.img, but it's still not rooted. This tablet is frustrating the hell out of me, I'm about to say the hell with it & toss it.
Dick_Stickitinski said:
Yeah, you can rename the APK to zip & flash it in TWRP
The Magisk Manager APK can now be flashed from within TWRP
Magisk is now distributed as part of the Manager APK, meaning you no longer need to flash a separate ZIP file from a custom recovery.
www.xda-developers.com
Click to expand...
Click to collapse
As of January last year, okay. On older phones/tabs I almost always go with older Magisk versions that were more current with the older device's firmware.
Dick_Stickitinski said:
However, I spoke too soon... I got it to stop bootlooping and actually got it to boot into system, and magisk manager is installed, but still not rooted. When flashing magisk in recovery again (or even extracting the boot.img & patching it in magisk manager, it recognizes it as a magisk-patched boot.img, but it's still not rooted. This tablet is frustrating the hell out of me, I'm about to say the hell with it & toss it.
Click to expand...
Click to collapse
Just a suggestion, maybe try using an older Magisk. I flashed Magisk v20.4 in TWRP and Magisk Manager v7.5.1 after booting to system. Older Magisk (zip and Manager) can be found on topjohnwu's GitHub.
Note, doing it this way, I always have to reboot one more time to see Magisk fully installed and working.
Hello there, back in the day (2019 in March or April the phone shipped with Android 9) I rooted my galaxy S10+ Exynos with Magisk and stock recovery (because TWRP method did not exist yet or did but non twrp method looked safer, I forgot the reason)
Then I forgot about TWRP and even upgraded to Android 10 like this:
(standard procedure, download android with Friya, then patch ap file with magisk, then flash it with odin)
Well I used my phone as always, forgot about twrp, but always had a little voice in my head telling me, that twrp is good idea, what if something happens, I would at least be able to copy my data)
So I decided to flash twrp, to ease my mind a bit, and also be able to copy apps to /system/priv-app
So I am using Android 10 (see no reason to upgrade, what I need is there I prefer OneUI 2.0 over later versions and I dont want to make my device slower or loose some obscure api function that I dont even know exists until I need it)
Now, can I just use official twrp app and let it do its thing (I have root), or do I need to download twrp with the app, but prepatch it with magisk before I install it? (I read conflicting info, on xda they say you need to prepatch it, while on twrp guide: https://twrp.me/samsung/samsunggalaxys10plus.html
They say to just use the app if you already have root, so I am confused now
It seams using the app is the easiest and most safe method
Thanks for Anwsering and Best Regards
only in case recovery and boot share the same partition, you will lose magisk after flashing TWRP (does not apply)
alecxs said:
only in case recovery and boot share the same partition, you will lose magisk after flashing TWRP (does not apply)
Click to expand...
Click to collapse
well, I gues this did apply to me, because I tried to flash TWRP with the app (latest version: twrp-3.7.0_9-2 that the app offered, it offered 2 files .img or .img.tar, and I chose to flash .img), and now my phone cannot boot, its stuck in download mode it says with red letters
kernel: Could not do normal boot, (DT LOAD failed)
I don't know know what happened, I only flashed recovery, and bootloader is unlocked
adb doesn't work
I cannot even get to recovery
So what now? Can at least flash TWRP somehow back so I can get ot my files (I have most of my videos on an SD card, but 2 or 3 are on internal storage )
I would reflash Android 10 anyway if it wasn't for the files
you can flash recovery.img as tar file but that is useless for backup stock ROM userdata. if you still have the magisk_patched.tar you can flash it to get your data back. don't flash unpatched stock boot.img this will most likely result in data loss.
I would first try older TWRP as DT LOAD failed (device tree) looks like TWRP problem to me.
alecxs said:
you can flash recovery.img as tar file but that is useless for backup stock ROM userdata. if you still have the magisk_patched.tar you can flash it to get your data back. don't flash unpatched stock boot.img this will most likely result in data loss.
Click to expand...
Click to collapse
OK
after installing TWRMP
3.4.0 I got into recovery
I guess the latest version twrp-3.7.0_9-2 is broken (because I tried flashing from Odin and I got the same error
but 3.4.0 works now
Well then I got into a non rooted android state (I couldnt boot into the rooted one because if I held volume up I just got into TWRMP)
I do have my magisk patched AP file (I did keep that), so I tried flashing it by odin to get into rooted state again, but then got scared because I was aftaid it would delete my data, so pulled the plug out, immediately after I discovered its flashing system.img (it just started)
thats where I interupted it
<ID:0/035> SingleDownload.
<ID:0/035> dt.img
<ID:0/035> dtbo.img
<ID:0/035> system.img
<ID:0/035> __XmitData_Write
<ID:0/035> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
So then phone would not boot, not in TWRMP not in android anymore, so I flashed TWRMP again and now at least
I am in TWRMP (I can see my files, but they are encrypted (they have wierd names but size does seam to match my files)
So how do I reflash android now, without messing with /data partition?
or can I somehow backup just data partition, reflash android and flash /data back?
let the magisk_patched.tar flash, just make sure you don't flash CSC (HOME_CSC is fine it won't erase userdata)
alecxs said:
let the magisk_patched.tar flash, just make sure you don't flash CSC (HOME_CSC is fine it won't erase userdata)
Click to expand...
Click to collapse
Yey, that did it (that was scarry), now root works, as well as android 10 (for some reason Magisk Manager does not open (but all the magisk modules work)
Now, I did patch this ap file back in the day I updated android to 10 so
I used Magisk Manager 7.4.1.291c718b
and if I remember corecly (thanks got I recorded everything) I patched the AP file for Magisk 20.2-11b7076a)
Now I have Magisk Manager 8.0.7 installed
So after I downgraded my Magisk manager to 7.5.0 it opened
Now I just have to figure out how to install Magisk v21.4 which is the version that belongs to my Magisk Manager 8.0.7, because Magisk Manager won't let me install a custom magisk, it only wants to download the latest version
you can install latest Magisk apk and patch stock boot.img again. Anyway I would do a backup with Migrate and adb pull -a /sdcard first.
or you can paste this url as custom channel and install older magisk if you want to.
https://raw.githubusercontent.com/topjohnwu/magisk_files/b0694fad86/stable.json
alecxs said:
you can install latest Magisk apk and patch stock boot.img again. Anyway I would do a backup with Migrate and adb pull -a /sdcard first.
Click to expand...
Click to collapse
aha, I see
is there any other way besides patching my AP file again? (I mean Magisk can clearly update itself somehow)
I mean, Magisk Manager does open (but only version 7.5.0, not version 8.0.7), and I have root its just that I don't have Magisk Manager 8.0.7
So how do I install a specific Magisk version from Manager? (I did try to install like a Magisk module, but now I am stuck in download mode again, so lets install Android 10 again )
look in the json for download link
https://github.com/topjohnwu/Magisk/releases/download/manager-v8.0.7/MagiskManager-v8.0.7.apk
https://github.com/topjohnwu/magisk_files/commits/master/stable.json
https://github.com/topjohnwu/magisk-files/commits/master/stable.json
alecxs said:
look in the json for download link
https://github.com/topjohnwu/Magisk/releases/download/manager-v8.0.7/MagiskManager-v8.0.7.apk
https://github.com/topjohnwu/magisk_files/commits/master/stable.json
https://github.com/topjohnwu/magisk-files/commits/master/stable.json
Click to expand...
Click to collapse
OK, after I installed Android again (with my older prepatched magisk)
Not sure what happened but now Magisk Manager 8.0.7 opens and says I have 20.2-11b7076a installed
of course as this combo should not exist, magisk Manager cannot see any modules (modules are there in /data/adb/modules and they do work, its just that Magisk Manager cannot see them installed, which means you can not easly delete them and you could install them over and over again, since Manager would not know that they are there)
So now I need to find a way to update to Magisk 21.4
So how would I do that (I tried the module install method before (I downloaded 21.4 from official github release pages) , but that just got me stuck into download mode again, so any other way, is there a patcher for computer maybe?
I mean I can only install the latest version, even if I disable internet, I cannot select a specific version
refer to post #8
Thanks, after spending 3hours to get into magisk I decided to share my procedure (because I forget it a lot)
FIrst: make sure your phones last state was power off (you can eather power off from red button or from recovery)
Then turn phone on and start holding power button + bixby + volume up, and count to 10 then release (not 11, 10, if you count to 11 you will get to recovery)
To try out if you are in magisk mode (without ruining your saved wifi passwords), you can plug the phone into the charger, if it turn on normaly, you are in magisk, if it shows battery charging, then you are not in magisk mode)
OK, I tried updating Magisk with https://raw.githubusercontent.com/topjohnwu/magisk_files/b0694fad86/stable.json
but for some wierd reason, it doesn't want to update, its stuck on 20.2-1
OK,. I tried installing Magisk Manager v7.4.1 and when launching it, it said that it patched dtbo.img and it needs reboot, so after I reboot, I am stuck on download mode again
It sayd: DT table header check fail
well, lets install Android 10 a third time
wait, you're booting into recovery to get into Magisk? you can use Nemesis kernel to skip this.
https://forum.xda-developers.com/posts/81316371
alecxs said:
wait, you're booting into recovery to get into Magisk? you can use Nemesis kernel to skip this.
https://forum.xda-developers.com/posts/81316371
Click to expand...
Click to collapse
Yes I am, but its allright, I am used to this
one day I will have to compile my own kernel anyway (to add some drivers to the phone)
Now I have to figure out why Magisk 21.4 won't install
I tried patching my AP file with it, but no matter what I do, I cannot get into it for some reason? (even my trust and tried method does not get me into it, while it got me into 20 all the time)
Is this version broken?
Whats the latest magisk version that still supports Magisk Hide (usefull thing that always worked for me)
With Nemesis kernel no need for button dance, it boots straight into Magisk. Magisk Hide exist up to v23 but there is also unofficial Magisk v25
[Discussion] Magisk Delta - Another unofficial third-party Magisk fork
This is not an officially supported topjohnwu project. If you are looking for official Magisk source, please go to this page Introduction Custom Magisk fork by HuskyDG. Sync with official Magisk adding back MagiskHide...
forum.xda-developers.com
alecxs said:
only in case recovery and boot share the same partition, you will lose magisk after flashing TWRP (does not apply)
Click to expand...
Click to collapse
Magisk needs the ramdisk of the recovery/TWRP to patch it. If flashing a non-prepatched image you will lose root.
WoKoschekk said:
Magisk needs the ramdisk of the recovery/TWRP to patch it. If flashing a non-prepatched image you will lose root.
Click to expand...
Click to collapse
Yea, I discovered that already
Now I am trying to get it back and failing
UPDATE: after installing Magisk 23 (last version that has Magisk Hide), prepatching AP file, and flashing it like 10th time, I finaly have root
Do I dare to try TWRP again? (I guess I need to prepatch it with Magisk before I install it with odin? (but which file do I install there are 2 files provided (twrp-3.4.0-2-beyond2lte.img.tar or twrp-3.4.0-2-beyond2lte.img)?
patch the tar file