Related
Hey I'm looking around and found 2 interesting posts.
http://forum.xda-developers.com/lg-...fficial-cyanogenmod-13-lg-g2-t3264508/page422
http://forum.xda-developers.com/lg-g2/help/starting-root-recovery-custom-rom-t3440752/page1
Click to expand...
Click to collapse
Pretty good instructions? I'm dancing around threads all over. I can't seem to get twrp onto a lollipop build. If I have twrp installed and try to manually go to LP from kk I get a bootloop the last few tries. If I have lp installed I can't seem to get autorec to respond, no matter which cfsu.
@blastagator:
Can you possibly list your steps for cwm and working magisk on your d800? Maybe I need to wipe all but internal, install lp bootstack in twrp-updated to one of your newer versions, install cwm? Is it clean from there to magisk and phhsu, magisk hide, phhapp? Will I need bumpboot ever for this?
andrew2432 said:
Hey I'm looking around and found 2 interesting posts.
Pretty good instructions? I'm dancing around threads all over. I can't seem to get twrp onto a lollipop build. If I have twrp installed and try to manually go to LP from kk I get a bootloop the last few tries. If I have lp installed I can't seem to get autorec to respond, no matter which cfsu.
@blastagator:
Can you possibly list your steps for cwm and working magisk on your d800? Maybe I need to wipe all but internal, install lp bootstack in twrp-updated to one of your newer versions, install cwm? Is it clean from there to magisk and phhsu, magisk hide, phhapp? Will I need bumpboot ever for this?
Click to expand...
Click to collapse
I do not use CWM, so I can't help you with that.
Basic Sequence (assuming starting from completely stock):
Use your favorite rooting tool - OneClick Root still works (I think)
Then install AutoRec (appropriate version for your ROM)
That gets you TWRP - boot TWRP with the key combo
Flash newest TWRP - reboot recovery
Flash bootstack to match new ROM (LP for LP or MM)
Advanced wipe, wipe /data, /system, /cache, /sd, /dalvik
Reboot Recovery
Copy new ROM to phone
Install new ROM
Reboot phone, profit
for magisk, flash magisk zip and then flash boot bump zip
IMPORTANT: If ROM has built-in su (like CM13 DOES) you need to delete that from the device.
I'd recommend deleting these BEFORE installing magisk (but I don't know if it actually matters)
For CM13, enable root in the developer menu
use your favorite console app
Code:
su
mount -o remount,rw /system
rm /system/xbin/su
rm /system/bin/su
Some ROMs might have an su file in /sbin and you might need to remount / as rw to remove that. For CM13 it is just those two files.
blastagator said:
I do not use CWM, so I can't help you with that.
Basic Sequence (assuming starting from completely stock):
Use your favorite rooting tool - OneClick Root still works (I think)
Then install AutoRec (appropriate version for your ROM)
That gets you TWRP - boot TWRP with the key combo
Flash newest TWRP - reboot recovery
Flash bootstack to match new ROM (LP for LP or MM)
Advanced wipe, wipe everything
Reboot Recovery
Copy new ROM to phone
Install new ROM
Reboot phone, profit
for magisk, flash magisk zip and then flash boot bump zip
IMPORTANT: If ROM has built-in su (like CM13 DOES) you need to delete that from the device.
I'd recommend deleting these BEFORE installing magisk (but I don't know if it actually matters)
For CM13, enable root in the developer menu
use your favorite console app
Some ROMs might have an su file in /sbin and you might need to remount / as rw to remove that. For CM13 it is just those two files.
Click to expand...
Click to collapse
Ahh cm is just the recovery not the rom, you use it and not twrp? The newest twrp for g2d800 is yours...twrp-d800-bump-blastagator?? What rom do you use? Will I be able to transfer files to the phone after wiping? I guess it stays in recovery after a wipe...just not used to that I guess.
Get twrp, flash bootstack...from you, wipe all, push my rom, flash rom, boot to phone. Experience my first ever custom os for a bit....Remove su with adb, boot to recovery, magisk, bump, phhsu zip, boot to phone. Install magisk 2.1, enable hide, reboot, phhsu app, ???, profit.
1. How can I thank ALL your posts ever?
2. Cwm nightly is the rom, the other is the recovery?
andrew2432 said:
Ahh cm is just the recovery not the rom, you use it and not twrp? The newest twrp for g2d800 is yours...twrp-d800-bump-blastagator?? What rom do you use? Will I be able to transfer files to the phone after wiping? I guess it stays in recovery after a wipe...just not used to that I guess.
Get twrp, flash bootstack...from you, wipe all, push my rom, flash rom, boot to phone. Experience my first ever custom os for a bit....Remove su with adb, boot to recovery, magisk, bump, phhsu zip, boot to phone. Install magisk 2.1, enable hide, reboot, phhsu app, ???, profit.
1. How can I thank ALL your posts ever?
2. Cwm nightly is the rom, the other is the recovery?
Click to expand...
Click to collapse
Recovery lives in /recovery partition, so I guess I should clarify, don't wipe EVERYTHING, lol. I can't remember if I enabled ability to wipe recovery, DONT DO THAT :silly:
edit: Advanced wipe, wipe /data, /system, /cache, /sd, /dalvik
But, as for everything else, recovery will live through wiping /system /data, etc. You need to backup anything you want to save though. Wipe will destroy everything.
Other than that, you pretty much got the rest.
edit 2: http://download.cyanogenmod.org/?device=d800
See image for ROM vs CM Recovery.
CWM = Clockwork Mod (a different recovery)
CM = CyanogenMod (a ROM)
.
@blastagator:
Haha I may have noticed that during the process. The bumpbootv1.0 is the one to use for even these newer methods?? That was what q2 really was supposed to be. I keep mentioning you because I assume it helps you see my posts, I assume your pretty busy. Some of those posts and files are rom when the g2 was almost new lol thanks seriously for getting back so fast I wish I could help this community more but I'm a skid
EDIT: awesome, I have to run all Internet functions off of the sprint lte network and was downloading one of those behemoths during that posts....that let's me know my efforts aren't in vain
andrew2432 said:
@blastagator:
Haha I may have noticed that during the process. The bumpbootv1.0 is the one to use for even these newer methods?? That was what q2 really was supposed to be. I keep mentioning you because I assume it helps you see my posts, I assume your pretty busy. Some of those posts and files are rom when the g2 was almost new lol thanks seriously for getting back so fast I wish I could help this community more but I'm a skid
Click to expand...
Click to collapse
Please read my edits and don't kill your phone. I am not always so timely in my responses :good:
Other than that, good luck!
There are tons of posts that go into more detail about what I wrote. Just make sure you have a plan before you do it. Think: Measure twice, cut once.
This g2 I found service locked while cleaning out a rental property. I have a galaxy s5 stupid sprint for my primary. I use the g2 for...well everything game and other related. until my Hotspot mod on my galaxy suddenly stopped working on lp. I blame the man
Äptiva is the one I read about a gutted 802 into an 800 or something, got you guys confused!!
@blastagator
Didn't work...steps followed what OS do you use? Do you use you d80030b or something else? No sn or pgo
If I update autorec twrp to your 3.0.2-1 will it hold through a manual FOTA update to 5.0? I use GPS system app for location. Is it possible moving to system then unrooting causes these bootloops and such? My g2 passes sn but I cm and gApps is causing issues? Logged into sc, pass sn, no pgo
andrew2432 said:
@blastagator
Didn't work...steps followed what OS do you use? Do you use you d80030b or something else? No sn or pgo
If I update autorec twrp to your 3.0.2-1 will it hold through a manual FOTA update to 5.0? I use GPS system app for location. Is it possible moving to system then unrooting causes these bootloops and such? My g2 passes sn but I cm and gApps is causing issues? Logged into sc, pass sn, no pgo
Click to expand...
Click to collapse
CM13.
If you're trying to get safety net to work, you have to enable magisk hide (in the magisk app)
Also, if you're using xposed, you can't use safety net.
@blastagator
Yeah done and done. Only things I can figure is installed the application side of phh su last, and gaps after being phh rooted.? I'm gonna check for su files with es here shortly. Safety net passes, snapchat works, just not pgo
Enabled hide after installing application and got root access when ticking hide. Literally the only thing that won't work is pgo, haven't tried android pay yet
No xposed I bought a way around that, not causing the issue because I haven't installed it on the d800
andrew2432 said:
@blastagator
Yeah done and done. Only things I can figure is installed the application side of phh su last, and gaps after being phh rooted.? I'm gonna check for su files with es here shortly. Safety net passes, snapchat works, just not pgo
Enabled hide after installing application and got root access when ticking hide. Literally the only thing that won't work is pgo, haven't tried android pay yet
No xposed I bought a way around that, not causing the issue because I haven't installed it on the d800
Click to expand...
Click to collapse
If the safety net test app passes, it should be working. perhaps downgrade your pogo a version or two, maybe they added something else.
Well, it's on a WiFi only, no SIM device...
I'm thinking this is the issue I'm experiencing now. Which may stem from an update. An older apk is a good idea, I was able to log on with magisk v6 a bit a go and when magisk 7 and 8 first came out I could.
I'm following the topjohnwu's guide on how to update with Magisk but I do not find it clear enough. Are these the steps I need to take in order to not-brick and update my phone with the Feb update.
1. Uninstall Magisk by "restore images" option.
2. Install OTA
3. Reboot to reinstall Magisk on second slot
Magisk is NOT installed on the second partition! And I prefer not to flash back the original image just to do that. My system should be read only and I do not have twrp, I never had, I updated my Google services framework from apkmirror and I got the update, now how do I apply it without soft bricking?
Update
Step 2 failed, "installation problem". Wtf do I do in order not to lose Magisk or data?
Edit
I've uninstalled Magisk but haven't restarted, hoping to get a solution where I keep my sh*t since that's what the guide said...
Edit 2
I'm reading the other thread but I'm having trouble finding a single useful information there, quote one if you find it, it might be my autism that I don't see a solution in that three pages long thread. Tell me I need to MiFlash this sh*t so I calmly jump through my window instead of wasting the whole night on making it work, then wasting another day on backing my sh*t up.
Edit 3
Fully uninstalled Magisk by instructions of an indian guide. BOOTLOOP.
Note to self, stop following southern asian guides.
Downloaded ROM and MiFlash, flashed flash_all_except_storage.bat.
Shook for 4 minutes until "success" mark, successful reboot.
Edit 4:
follow the regular magisk flash guide https://forum.xda-developers.com/mi-a1/help/how-to-root-mi-a1-february-ota-update-t3757934
If you got into bootloop after Magisk uninstallation, you did modify system partition at some point. This is also the reason why you couldn't install OTA. Magisk OTA update guide works perfectly fine for unaltered system partition.
_mysiak_ said:
If you got into bootloop after Magisk uninstallation, you did modify system partition at some point. This is also the reason why you couldn't install OTA. Magisk OTA update guide works perfectly fine for unaltered system partition.
Click to expand...
Click to collapse
That's what I figured, but how? I just did exactly everything I did before the OTA attempt, I just installed few modules and touched nothing else. At which point could've I touched system partition?
So I'm reading now that apps can still alter /system with the Magisk root perm, so, I what about one of these apps.
1. Does anyone know if they can mess with the system?
BusyBox
Greenify
Lucky patcher (this c*nt is my main suspect)
Titanium backup
2. Can we somehow make sure that we haven't touched the system partition before OTA attempt?
3. Once I've redone everything (flash Rom without storage, install OTA, install Magisk), my system shouldn't be touched now, right?
A14DWIN said:
That's what I figured, but how? I just did exactly everything I did before the OTA attempt, I just installed few modules and touched nothing else. At which point could've I touched system partition?
So I'm reading now that apps can still alter /system with the Magisk root perm, so, I what about one of these apps.
1. Does anyone know if they can mess with the system?
BusyBox
Greenify
Lucky patcher (this c*nt is my main suspect)
Titanium backup
2. Can we somehow make sure that we haven't touched the system partition before OTA attempt?
3. Once I've redone everything (flash Rom without storage, install OTA, install Magisk), my system shouldn't be touched now, right?
Click to expand...
Click to collapse
Please keep in mind that Magisk is 2in1 package. First of all it provides root access, any app with root access can modify system directly. Second feature are systemless modifications, but you must follow defined rules to make them work.
From your list of apps, BusyBox would be my first suspect. You must use Magisk BusyBox module, the standard BusyBox is installed directly to the system partition. Lucky app might be the culprit too, though it depends on which features exactly did you use.
Yes, once you reflash stock ROM, apply OTA and install Magisk (the correct way), you're system partition will be ready for the next OTA.
Someone mentioned one command which could verify the last modification date of any partition, but can't find it right now.
_mysiak_ said:
Please keep in mind that Magisk is 2in1 package. First of all it provides root access, any app with root access can modify system directly. Second feature are systemless modifications, but you must follow defined rules to make them work.
From your list of apps, BusyBox would be my first suspect. You must use Magisk BusyBox module, the standard BusyBox is installed directly to the system partition. Lucky app might be the culprit too, though it depends on which features exactly did you use.
Yes, once you reflash stock ROM, apply OTA and install Magisk (the correct way), you're system partition will be ready for the next OTA.
Someone mentioned one command which could verify the last modification date of any partition, but can't find it right now.
Click to expand...
Click to collapse
Dang I really need that command.
_mysiak_ said:
Please keep in mind that Magisk is 2in1 package. First of all it provides root access, any app with root access can modify system directly. Second feature are systemless modifications, but you must follow defined rules to make them work.
From your list of apps, BusyBox would be my first suspect. You must use Magisk BusyBox module, the standard BusyBox is installed directly to the system partition. Lucky app might be the culprit too, though it depends on which features exactly did you use.
Yes, once you reflash stock ROM, apply OTA and install Magisk (the correct way), you're system partition will be ready for the next OTA.
Someone mentioned one command which could verify the last modification date of any partition, but can't find it right now.
Click to expand...
Click to collapse
Don't bother trying to find it, it exists, I'll make a dedicated thread at some point, thanks for the answer, BusyBox seems logical.
The correct way to install Magisk? I just flash Ranjit's patched img from the official thread on Magisk root, that should be the correct way.
I just use lucky to patch cirtain apps, so that shouldn't be a problem
Right now, I'm giving Magisk root perm to Greenify, Lucky Patcher and Unified Hosts. Also both Greenify and the Unified hosts adblock have their own modules in magisk.
Hopefully I still haven't touched my system partition.
I encountered the error as well after trying the Pixel OTA method. To flash the update successfully, I flashed stock January system and boot img via fastboot and it updated properly after. Then I just patched the stock Feb boot img and went back to fastboot. Once there, i did the fastboot boot command with the patched Feb boot.img so I got root back after updating.
Sent from my Xiaomi Mi A1 using XDA Labs
HI,
I have a redmi5+ rooted. I use luckypatcher (i applied some patchs to some apps) and i have installed once BusyBox (didn't do anything in special).
I want to know if it is secure to flash the full update?
PS: how do I confirm if the system files and vendor are ok to proceed?
Thanks
cant you flash the ota in twrp and then reflash magisk if needed?
robgee789 said:
cant you flash the ota in twrp and then reflash magisk if needed?
Click to expand...
Click to collapse
Yes, I can do that.
I Know the procedure to flash full zip file via TWRP. Via this toturial: youtube.com/watch?v=oUUzxYHV_ac&t=1s&index=11&list=WL
But i want to know if it is secure to flash, because i used these two applications.
Ok, why the f. did I get "installation failed" when installing OTA following this guide?
I followed the guide, I hit uninstall and "restore images" in magisk, it restored the stock image and when I tried running feb ota, I got "installation failed", why?
Also, why did my device get in a bootloop by just fully uninstalling magisk?
I had unlocked bootloader with systemless root, with no TWRP, never booted it, never flashed it, only fastboot commands I ran were oem unlock and boot patched_boot.img. I never touched system partition (on purpose), never installed anything other than a bunch of magisk modules, safetynet was always working, if it matters.
PSA FOR GOOGLE VISITORS:
Do not fully uninstall magisk after you get "installation failed", I got a bootloop and had to flash flash_all_except_storage.bat from mi a1 stock rom using miFlash (bottom right to select it, don't flash_all if you want your data).
Same thing happened with me... what exactly i done was...booted into patched boot.img using fastboot and after that used magisk manager and installed camera2api and just substratum.....but when i got notification of feb update... I tried to uninstall magisk manager using complete uninstall option....then restarted manually then it booted up and then suddenly shuts down and started showing a black screen with Android logo with (No command) written below it......to recover from this condition i again tried to use the same fastboot method for booting into patched boot... after which i was able to use my mobile.... normally but I'm not able to install feb update.... I'm downloading the complete stock rom.....but if there's any other method which can be efficient so plz inform....
Azeemkwow said:
Same thing happened with me... what exactly i done was...booted into patched boot.img using fastboot and after that used magisk manager and installed camera2api and just substratum.....but when i got notification of feb update... I tried to uninstall magisk manager using complete uninstall option....then restarted manually then it booted up and then suddenly shuts down and started showing a black screen with Android logo with (No command) written below it......to recover from this condition i again tried to use the same fastboot method for booting into patched boot... after which i was able to use my mobile.... normally but I'm not able to install feb update.... I'm downloading the complete stock rom.....but if there's any other method which can be efficient so plz inform....
Click to expand...
Click to collapse
Just like he said, yeah using Magisk means waving bye to OTA updates. This was the exact problem I faced where I installed Magisk module without TWRP for the joys of using substratum. Installating magisk won't taper your system, they said, you would still get the update, they said. Well NEWS FLASH for those, installing magisk tampers your system partitions and you are in a dreadlock situation where you can't do ****. People claim there are work arounds like you linked but no one has actually confirmed using it. And the worst part is that if you try to install the update even after uninstalling Magisk , it will still give you the error. How do I know? tried it, doesn't work. The only option which was left to me was to download the official Oreo ROM from MiUI global and flash it using MiFlash.
Flashing the boot.img from stock rom might solve the problem. If not, flash the stock rom using MiFlash with save user data option.
Alanjameson99 said:
Just like he said, yeah using Magisk means waving bye to OTA updates. This was the exact problem I faced where I installed Magisk module without TWRP for the joys of using substratum. Installating magisk won't taper your system, they said, you would still get the update, they said. Well NEWS FLASH for those, installing magisk tampers your system partitions and you are in a dreadlock situation where you can't do ****. People claim there are work arounds like you linked but no one has actually confirmed using it. And the worst part is that if you try to install the update even after uninstalling Magisk , it will still give you the error. How do I know? tried it, doesn't work. The only option which was left to me was to download the official Oreo ROM from MiUI global and flash it using MiFlash.
Click to expand...
Click to collapse
Thanks...now that's what I'm planning to do...install official rom through miflashtool
RavinduSha said:
Flashing the boot.img from stock rom might solve the problem. If not, flash the stock rom using MiFlash with save user data option.
Click to expand...
Click to collapse
Does the 'save user data'-option also preserve the apps installed?
Thanks!
Tiemichael said:
Does the 'save user data'-option also preserve the apps installed?
Thanks!
Click to expand...
Click to collapse
Yes it saves all user data including settings, apps and app data
I had the same issue. I used the tool linked below and the steps:
- Unlock Bootloader
- Flash Stock ROM
- Download ROM (and wait for that to happen)
- Keep UserData (and wait again)
- Lock Bootloader
After that I was able to install the update, then re-install Magisk and camera tweaks.
https://forum.xda-developers.com/mi-a1/how-to/tool-xiaomi-mi-a1-tool-drivers-unlock-t3742857
The guide mention in OP had worked for me for at least 3 updates including the major one from nougat to oreo with any issue. Be aware that mounting system partition as read AND WRITE brakes OTA. You don't even need to change anything just mounting it will brake it. That could easily happen using a root file explorer or a hosts file based add blocker if Magisk is not properly set (systemless hosts support toggle in Magisk settings).
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.
Hi,
I was trying to install the new version of Magisk 22, by patching my recovery image since Ramdisk is indicated as No in Magisk, but I can't figure out which recovery.img I should be using. I have OrangeFox 11 recovery installed, but I tried with its .img and it didn't work. My phone got encrypted, and I had to format my data thus reseting my phone in order for it to boot.
I also tried to flash the Magisk.apk file renamed as .zip but same issue, password at reboot which made me format my data partition again.
It's bugging me and I don't know what to do.
If someone can help me I would be very thankful!
U need only a recovery, flash the apk as zip. That's working
I already tried flashing the apk, it only ended with the same issue at boot, asking a password I didn't have
Ti64CLi++ said:
I already tried flashing the apk, it only ended with the same issue at boot, asking a password I didn't have
Click to expand...
Click to collapse
Then use magisk from orangefox. It's 21.4 I think
Thanks I will.
But it's still bizarre that Magisk 22.0 doesn't work on my phone
I just tried and once again it didn't work. I had to format data partition once again, and restore a previous backup, which by the way, didn't fully work.
I'm starting to think that I won't be able to install Magisk on my phone anymore
Ti64CLi++ said:
I just tried and once again it didn't work. I had to format data partition once again, and restore a previous backup, which by the way, didn't fully work.
I'm starting to think that I won't be able to install Magisk on my phone anymore
Click to expand...
Click to collapse
It worked fine for me. Maybe try and ask you problem in the general Magisk support thread? https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/page-2264#post-84825737
svendsvin said:
It worked fine for me. Maybe try and ask you problem in the general Magisk support thread? https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/page-2264#post-84825737
Click to expand...
Click to collapse
You too have a Redmi Note 7?
Did you manage to install Magisk 22.0 or an older version?
Thanks I will ask on the general Magisk support thread
Yes I have. I used Magisk from Orangefox first time and since updated to Magisk 22.1.
I whould suggest flashing Magisk v20.4 zip for Redmi Note 7 using OrangeFox recovery, cause this worked for me, then using the Magisk app, update it to 22.1 using the app itself, its quick and painless and also can remove force encryption. I hope it could work for you.
The required files for root are in this link (i used the same files) https://drive.google.com/drive/folders/1bpvlCnRFNQS8hIrYY5ePWS6WXfeSyt9x?usp=sharing
P.S. dont unzip anything cuz the zip file has to be flashed all together
update : the apk is deleted cuz the zip already installs it