Related
Has anyone been able to get magisk to work appropriately? I attempted and the magisk apk kept fc'ing. I read about LG devices needing a boot.img "bump". Is this true or has anyone got it working in their own way?
There Is no root method for variants that don't have a unlocked bootloader. You would know this if you read the forums before asking
Sent from my VS995 using Tapatalk
mrtruckincowboy said:
There Is no root method for variants that don't have a unlocked bootloader. You would know this if you read the forums before asking
Click to expand...
Click to collapse
So, quite frankly, if you read, another user has it working. Further more, with the TMO variant, I do have an unlocked bootloader. Root application works with magisk, however the APK itself fc's.
I thought cowboys were polite ; )
I misread your post thought you were the typical person asking for a update on root I apologize.
Sent from my VS995 using Tapatalk
Thats what you get for not reading posts Cowboy... Smh...
I have the H918/tmo and I was able to get magisk running with phh's superuser. I'm kinda iffy on magisk-hide, as i had issues with it initially ( random reboots with it enabled). I turned off magisk hide for about a week, then turned it back on last night with no reboots since.. but haven't tested it with apps.
After running the easy recowvery + root script, i got rid of SuperSU. I believe all i did was a Full Unroot in the options, with no changes to the recovery. (I also may have done a format /data when rebooting to recovery again, but i dont recall fully, so take that into consideration if it didnt work at first (followed by the no-verity-opt-encrypt zip).)
After getting rid of SuperSU/su binary, what i remember doing was:
1 ) Flash magisk v9.zip -> reboot to system to make sure it boots, then adb reboot recovery.
2 ) Flash phh's superuser r266-2.zip -> reboot to system
3 ) install magisk manager via apk, and phh's superuser via playstore.
4 ) test out root.
has anyone been able to get Phh's superuser to work on the Sprint v20 / LS997 ?? If so, how? Thanks in advance.
If you can't get this working there is an app called RootSwitch. It can successfully hide root on the V20 with a toggle.
HiddenKnight said:
Has anyone been able to get magisk to work appropriately? I attempted and the magisk apk kept fc'ing. I read about LG devices needing a boot.img "bump". Is this true or has anyone got it working in their own way?
Click to expand...
Click to collapse
ive got 1 working and 1 in testing that uses magisk and phh.
the phh superuser seems to be casusing the systemui to force close often when in hide mode and the random reboots and loss of service, otherwise it was working fine.
but yeah, just flash version 10.2 on your current rom and see what happens!
btw this was on DEC sec patch, on oct builds i never tried it, but this is latest DEC sofware, didnt even use rootswitch
slayerh4x said:
If you can't get this working there is an app called RootSwitch. It can successfully hide root on the V20 with a toggle.
Click to expand...
Click to collapse
Is this the App you used?
https://forum.xda-developers.com/android/apps-games/play-pokemon-root-switch-method-patched-t3483179
remix435 said:
Is this the App you used?
https://forum.xda-developers.com/android/apps-games/play-pokemon-root-switch-method-patched-t3483179
Click to expand...
Click to collapse
I am using the one from this rom thread;
https://forum.xda-developers.com/v20/development/h819-nrd90m-modded-stock-rom-t3503658
Just follow the directions in the OP and you'll be g2g.
slayerh4x said:
If you can't get this working there is an app called RootSwitch. It can successfully hide root on the V20 with a toggle.
Click to expand...
Click to collapse
Tried RootSwitch w/ SuperSU. Didn't pass SafetyNet if that's what you were referring to.
Tried it again last night. Had the 1st 3 options turned on. Soon as I opened Android Pay my phone hot booted and got stuck on the VZW splash screen. Had to pull the battery. Won't try that again with supersu.
I have a VS995 this is how I got my phone to finally take magisk and pass the safetynet check. I'm running software version VS99513A I performed dirty santa to get unlocked bootloader and root access. Now I tried to uninstall supersu threw the app and I got a failed message. I tried going into recovery and flashing the supersu unistaller and that would fail. I tried flash magisk v12.0 and keep getting error message. I got stock in twrp recovery several times and used LGUP and flash either VS99512A KDZ or the VS99513A KDZ. Am not a developer but it seemed as if the boot.img won't take by the magisk zip. Those where my failed attempts for about a week or two. Now on to the success story
Performed Dirty Santa on software version VS99513A. I decide to flash modstock kernaI update v1.1 because it seem to work well with a stock rooted VS995. I flashed busy box in recovery and downloaded the app and also downloaded quick reboot so I could reboot into recovery easier. After reading @poixninja thread on modstock kernal - stocked with goodies he mention flash a boot.img that was patched with magisk. So I but the phone into fastboot mode and flashed his boot.img onto the phone with cmd (command prompt). I think I might have tried to uninstall supersu threw the app and I think it didn't work after flash the boot.img. So I put the phone into recovery mode the to wipe and then to advance wipe and clear dalvik and cache. After that I went to install and flashed the supersu unistaller and it took. After flashing I wipe the cache that twrp ask after most flashes. I then rebooted into recovery to make sure my twrp was not affected because I had and issue with that in previous supersu unistaller attempts. Rebooted ito twrp recovery then rebooted into system. I think whenever I flashed the verzion logo stayed up longer than normal but the phone fully started up. I clicked on supersu and it said no root access. Turned of the phone and did the steps to get to recovery mode. Once in I first wiped dalvik and cache. Then I flashed magisk unistaller and it went threw with no issue. I wiped dalvik and cache then rebooted into recovery. After getting into recovery I rebooted to system.
Sidenote: I recommend after wiping supersu and flashing magisk unistaller. Once you boot up install magisk apk. I didn't install the apk until after I flashed the magisk v12.0 in recovery. I noticed when I reboot the magisk icon was on the phone but when I clicked it it said go to playstore to download. I had the magisk manager apk on my SD card so I just installed it. The install to longer than normal I think it was because I didn't install it prior to flash the zip in recovery. I didn't get a chance to verify it yet.
Once the phone boot and I installed the magisk app manager I open it up and got green checks for installed magisk v12 and properly rooted. I went to setting and turned on enable busy box, magisk hide, and systemless. But when I clicked safetynet I got cts mismatch. Did some research and read on other XDA magisk thread that it maybe because of custom roms, modified kernals and possible supersu somewhere on the system. The only root accessible apps I had installed during this process was busybox and quick reboot. I did notice the first time I ran quick reboot after getting magisk it did give it root access then it did after I opened it again.
I decide to uninstall quick reboot and busy box. I uninstalled both apps. I rebooted into recovery mode the manual way. First thing I did was wipe dalvik and cache. Then I flashed busy box uninstaller. When the flash was running I say in the command lines that it found supersu. Which I thought was odd so I also flashed supersu unistaller. I rebooted into recovery wipe dalvik and cache and flashed uninstall magisk. Then reboot into recovery. I ran busy box uninstaller one more time to see if it would pick up supersu again and the command lines did not mention it. I flashed back magisk v12.0 rebooted into recovery. Then rebooted into system
Opened magisk went to setting to turn on enable busy box, magisk hide and systemless. Check safetnet and failed I found a magisk XDA thread that talks about common issue. It said I had to check magisk core only mode. Once I did that he requested a reboot which I did. Once back up I first cleared in app manager under show system I cleared all data for google play store, google play service for instant app, google play services. I opened magisk clicked safetynet check and I passed it. I went to search for netflix in play store and it pop up I installed it and it working fine so far. I tried logging into snapchat and I got threw.
Hope this maybe help full to anyone having issues
https://forum.xda-developers.com/v20/development/kernel-modstock-kernel-stock-goodies-t3563887 (boot img and modstock v1.1)
https://forum.xda-developers.com/showpost.php?p=71154562&postcount=4 (Magisk common issues)
Easier than that...?
sentra10550 said:
I have a VS995 this is how I got my phone to finally take magisk and pass the safetynet check. I'm running software version VS99513A I performed dirty santa to get unlocked bootloader and root access...
...
...Hope this maybe help full to anyone having issues
Click to expand...
Click to collapse
If I may be so bold, I played around with the rooting process on mine (I have a VS995 on 13A, too), and found a much easier (and possibly cleaner?) way to do this. Of course, the way I'm about to suggest would require a full KDZ to stock and a factory reset...
Here's mine:
Follow this thread:
https://forum.xda-developers.com/v20/how-to/lgv20-vs995-verizon-aio-post-06-19-2017-t3624326
Note: For noobs: After step 13, it's a bit misleading, because it doesn't boot DIRECTLY into TWRP, but boots to the white-screen "stock" recovery. The trick is to tell it "Yes" to both reset prompts. (It doesn't actually reset your stuff.) After this, it will take you to the TWRP menu.
When you get to step 14E, DO NOT FLASH SuperSU!
Instead, flash the ReStock zip.
After flashing ReStock, follow step 14G, and then flash Magisk 13.3 (latest stable, haven't tested others) from here:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
I tried this out of order a couple of other times and ended up either having Magisk not following through with install, or developing issues installing certain apps. (Either getting a -504 error from Play Store, or having valid APKs reply that they were "corrupt" when directly installing.)
Of course, all of the stereotypical disclaimers apply-- YMMV, and I'm not responsible if you brick your device, yadda yadda...
No offense, intended, sentra10550. While I'm glad you managed to get things working, the directions were a bit convoluted and I hope my humble findings might help yourself, in the future(?), and any others that may have a VS995.
Good luck, everybody!
)O( NeoHiPPy )O(
Think I'll wait until an easier method comes out for the VS995 to run Magisk lol..
I was UNABLE to do full unroot on my V20 from SuperSu settings menu. It would say "uninstallation failed"
I tried running UPDATE-unSU.zip from TWRP and it did not help. Magisk keeps on complaining about modified boot file.
I am unlocking boot loader, trying to flash Magisk in TWRP instead of SuperSu as per DirtyStanta root method instructions.
I will also flash restock 1.3 right after to stop static and vibration issue.
If it works, ill update my post.
---------- Post added 21st February 2018 at 12:28 AM ---------- Previous post was 20th February 2018 at 11:48 PM ----------
Ok i got it working. It was easier then i thought it would be.
These are the steps i did the very first time i got into TWRP after bootloaded unlock process as per DirtySanta rooting instructions.
Entered TWRP
DID NOT format data>yes
Installed Restock1.3 and Magisk.zip
Wipe cache and dalvik. Says Failed to wipe Dalvik (dont know why but what ever)
Reboot.
Result: Asking for unlock password 9 attempts left. So i have to Format Data>Yes
Re-entered TWRP
Format Data>yes
Reboot.
Root works. No SuperSu needed.
Conclusion:
You have to format DATA not for the root to work, but to be able to get into the phone. If there was a way to bypass that, there would be no need to factory reset to root. Root method would not require you to wipe the phone.
How ever, some apps that i use still do not support systemless root. They fail to do their work such as removing system apps. I cant remove any of my system apps for some reasons. I get "failed" messageevery time.
I was told i need modules for Magisk, but i have yet understood what that even means.
Other apps that use root, work fine. Such as AdAway.org
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.
As the title describes, I did the probably not so smart and I tried updating Magisk from within the Magisk Manager and now I cant get out of the loop of it returning to "Downloading...".
I was using Magisk Manager 21.4 and when I tried running the uninstall Magisk zip file within TWRP, it fails cause of something in accordance to the SD card (probably where its running from) or something.
Edit: I figured it out, it does not recognize the contents of the zip files as a bootable image anymore
Now im not sure how im suppose to follow the guide from here: https://magiskmanager.com/uninstall-magisk
Do any of you have a suggestion that does require me to completely re-root my phone?
Im not sure how to remove this thread, but the issue is resolved and I probably posted it in the wrong forum place any way.
How did you resolve the problem. I'm having the same issue right now. Did you simply uninstall Magisk?
Hi @onurdz I faced the same. I solved it by removing the App, rebooting, installing the App v8.0.3 , updating the App to v22.1, and then the option to update Magisk appeared.
Thanks a lot for posting it here! I came here looking for solution for the same, without even realizing it might be caused by Magisk - update and reboot happened a good while apart.
I tried looking but couldn't find - is it a known issue with magisk, and is there a fix (in work) to solve it without removing or rolling back magisk?
Now I'm confused.
My phone wouldn't start. It's either "downloading", or TWRP.
I'm trying to uninstall magisk, by downloading the app, renaming it into uninstall.zip and installing in twrp.
It fails with an error. Not sure it's same, it says to me "unsupported/unknown image format"
AntonGut said:
Now I'm confused.
My phone wouldn't start. It's either "downloading", or TWRP.
I'm trying to uninstall magisk, by downloading the app, renaming it into uninstall.zip and installing in twrp.
It fails with an error. Not sure it's same, it says to me "unsupported/unknown image format"
Click to expand...
Click to collapse
Hi...
first...there is a Magisk Zip file you can use to uninstall with TWRP.
sec...you can flash the Stock Boot.img into boot partion
third...you can recover boot image from a backup
yeah im sure that every option will bring success
solong
speedson
to unbrick a samsung just download the Stock firmware by using Frija tool and start the into download-mode
then use Odin3 to flash the stock rom and restart into System...thats all
solong
speedson
after uptade magisk my phone stuck in fastboot . i cant go to recovery . what i can do ?
phone is over or i can fix it ?
Open Magisk Github, and try to find a solution in the Magisk Troubleshooting
You say you "updated Magisk". Since you didn't describe how, supposidely you did by flashing Magisk through TWRP or by Direct method from Magisk app/mngr
Unfortunately, those two ways are most risky. If anything goes wrong (if you don't have TWRP backup) you cannot go back to the previous working configuration
It takes just few minutes more to extract and patch the boot.img and to flash it. If anything goes wrong, you flash the original unpatched boot.img or boot.img that was patched by your older Magisk and you are back in business.
To fix the bootlop now, it will take more than few extra minutes for extracting, patching and flashing the image every time when installing and updating Magisk
zgfg said:
Open Magisk Github, and try to find a solution in the Magisk Troubleshooting
You say you "updated Magisk". Since you didn't describe how, supposidely you did by flashing Magisk through TWRP or by Direct method from Magisk app/mngr
Unfortunately, those two ways are most risky. If anything goes wrong (if you don't have TWRP backup) you cannot go back to the previous working configuration
It takes just few minutes more to extract and patch the boot.img and to flash it. If anything goes wrong, you flash the original unpatched boot.img or boot.img that was patched by your older Magisk and you are back in business.
To fix the bootlop now, it will take more than few extra minutes for extracting, patching and flashing the image every time when installing and updating Magisk
Click to expand...
Click to collapse
I did update magisk by direct method from the app. Now i am in a bootloop. I always had and still have the teamwin recovery project. Can you help me how to get out of this bootloop without losing my data?
Add me on discord for live support :
SneezeOnYou2#8507
AC420 said:
I did update magisk by direct method from the app. Now i am in a bootloop. I always had and still have the teamwin recovery project. Can you help me how to get out of this bootloop without losing my data?
Click to expand...
Click to collapse
You should better have updated Magisk by patching the boot.img, then flashing (from Fastboot or TWRP) - in that case, if you have bootloop you simply flash back your previously patched img that used to work
I cannot know what went wrong. Maybe, there is a module that is no more compatible and causing the bootlop:
- Reboot to TWRP, Advanced, File Manager and navigate to /data/adb/modules
Each folder corresponds to one module.
Add an empty file named: disable (exactly as that) to each folder/module (or only to those modules you suspect they might be causing the bootloop).
Once you disabled the critical module, you can boot to system and from Magisk app further manage your modules.
Or, from TWRP flash to Boot the original boot.img extracted from your OTA zip file.
When you reboot to system, there will be no Magisk but next time you install Magisk it will find and activate old modules, probably causing again the bootloop
Or, download Magisk apk, rename to uninstall.zip and flash from TWRP to fully uninstall Magisk (and all its modules, everything)
Recommending first method, but you see the other two options as well
zgfg said:
You should better have updated Magisk by patching the boot.img, then flashing (from Fastboot or TWRP) - in that case, if you have bootloop you simply flash back your previously patched img that used to work
I cannot know what went wrong. Maybe, there is a module that is no more compatible and causing the bootlop:
- Reboot to TWRP, Advanced, File Manager and navigate to /data/adb/modules
Each folder corresponds to one module.
Add an empty file named: disable (exactly as that) to each folder/module (or only to those modules you suspect they might be causing the bootloop).
Once you disabled the critical module, you can boot to system and from Magisk app further manage your modules.
Or, from TWRP flash to Boot the original boot.img extracted from your OTA zip file.
When you reboot to system, there will be no Magisk but next time you install Magisk it will find and activate old modules, probably causing again the bootloop
Or, download Magisk apk, rename to uninstall.zip and flash from TWRP to fully uninstall Magisk (and all its modules, everything)
Recommending first method, but you see the other two options as well
Click to expand...
Click to collapse
Connect me pls on discord fkr me its like chinese now it would be easy if you tell me live what to press on the teamwin mode. The reason i update magisk was because i had a module to block ads but suddenly it didnt work so i opened magisk and i saw the update and did the direct update like how i always updated my magisk before.
AC420 said:
Connect me pls on discord fkr me its like chinese now it would be easy if you tell me live what to press on the teamwin mode. The reason i update magisk was because i had a module to block ads but suddenly it didnt work so i opened magisk and i saw the update and did the direct update like how i always updated my magisk before.
Click to expand...
Click to collapse
I don't use discord and I have work and private life
I gave you directions that if you knew just basic things about flashing and File mngr in TWRP, about using Magisk, etc, would be nite than enough to follow directions
Most annoying users are those who install'nuclear bomb' like Magisk, do updates, etc, but never spent their time to learn (when things work and it's easier) how to use, read the Instructions (available by one click to Github from Magisk app), etc, and then when (sooner or later) get a brick, cry for somebody to guide them to click here, there, etc.
You can still use PC and google and fill the gaps from my instructions to what/how you must click here and there
Sorry to be brutal but I really don't have time
zgfg said:
I don't use discord and I have work and private life
I gave you directions that if you knew just basic things about flashing and File mngr in TWRP, about using Magisk, etc, would be nite than enough to follow directions
Most annoying users are those who install'nuclear bomb' like Magisk, do updates, etc, but never spent their time to learn (when things work and it's easier) how to use, read the Instructions (available by one click to Github from Magisk app), etc, and then when (sooner or later) get a brick, cry for somebody to guide them to click here, there, etc.
You can still use PC and google and fill the gaps from my instructions to what/how you must click here and there
Sorry to be brutal but I really don't have time
Click to expand...
Click to collapse
Its not that i didnt look up on youtube about flashing in revovery mode. When i did search for more information i get those videos of people in india talking their own language. Np if you dont have time and on other topic someone said that they wint use discord because it wont be public for someone else with the same problem but i was gonna make photos with the steps i did for fixing it. The thing is i cant find the uninstall. File or the older version of twrp. Skip i wont takr your time good luck with your private life
And about the installing nuclear bomb thing... magisk has the direct install option which is the nuclear bomb button (sometimes) the reason why my phone got into bootloop is a module which isnt working anymore its called energized its for blocking ads. I saw that it didnt work... before it worked fine i thought maybe i need to update magisk but thats why it went into the bootloop. I managed to delete the module through twrp mode and here this is for you
AC420 said:
And about the installing nuclear bomb thing... magisk has the direct install option which is the nuclear bomb button (sometimes) the reason why my phone got into bootloop is a module which isnt working anymore its called energized its for blocking ads. I saw that it didnt work... before it worked fine i thought maybe i need to update magisk but thats why it went into the bootloop. I managed to delete the module through twrp mode and here this is for you
Click to expand...
Click to collapse
You don't need to delete modules (some of them, like V4A might be complicated to install again) - just disable them through still the working Magisk app before you go for updating
Or patch and flash the image instead of taking Direct install. There might be other reasons to cause bootloop, not just incompatible modules.
If it bootloops when you flash the newly patched img, just flash your old img, previously patched by the older Magisk version, that used to work for you
As simple as that - and no bootloops, no emergency help needed, etc
zgfg said:
You don't need to delete modules (some of them, like V4A might be complicated to install again) - just disable them through still the working Magisk app before you go for updating
Or patch and flash the image instead of taking Direct install. There might be other reasons to cause bootloop, not just incompatible modules.
If it bootloops when you flash the newly patched img, just flash your old img, previously patched by the older Magisk version, that used to work for you
As simple as that - and no bootloops, no emergency help needed, etc
Click to expand...
Click to collapse
I am surei have the older backup in my internal storage of my phone but i dont know from where to recover that and on the internet they say everything and i am scared to make it worse than it is. I didnt use the phone for a long time because my lcd got a short circuit and i replacet it. On internet they say this bootloop problem can occure when you skip some updates some say to install a program on pc then go in download mode and fix with the program but i unpluggrd my pc and tv because me and they got too old for eachother.
Now i am just trying different things what i see on youtube and twrp says this: check picture.
AC420 said:
I am surei have the older backup in my internal storage of my phone but i dont know from where to recover that and on the internet they say everything and i am scared to make it worse than it is. I didnt use the phone for a long time because my lcd got a short circuit and i replacet it. On internet they say this bootloop problem can occure when you skip some updates some say to install a program on pc then go in download mode and fix with the program but i unpluggrd my pc and tv because me and they got too old for eachother.
Now i am just trying different things what i see on youtube and twrp says this: check picture.
Click to expand...
Click to collapse
I've had this ****, i just used abd to flash a new twrp img and dirty flashed the ROM after it flashed magisk back on again, only problem I got was safety new which idk how I solved but I think was using lsposed
I've been running custom roms since before android was a thing so I'm usually pretty good at this stuff.
I'm running 11.0.9.9 IN11AA
It refuses to root. I'm not sure if there is some step I'm missing that's so obvious nobody mentions it?
I was rooted, but when the new Magisk 23 came out without Magisk hide.. it was a big problem for me. I have corporate apps that will refuse to work on a rooted device. I restored the stock images (just like I do to get my OTA).. but then I uninstalled Magisk 23 and Installed 22.1. I then patched the bootloader (Dire3ct Install) and all was good, until I rebooted and had no root.
My bootloader is unlocked.
So I downloaded the full stock rom v11.0.9.9 IN11AA directly from Oneplus.
Extracted payload.bin
Used Payload dumper to get the proper boot.img.
Copied boot.img to my device and used magisk 22.1 to patch the file.
Downloaded the patched boot.img to my desktop.
Used ADB to flash it
adb reboot bootloader
fastboot flash boot patched_boot.img
fastboot flash boot_a patched_boot.img
fastboot flash boot_b patched_boot.img
fastboot reboot
Nothing. No Root.
I tried this over and over with different versions of magisk.
I tried downloading pre-patched version, and using fastboot boot patched_boot.img.
The device just hangs, and then boots using the stock image. No root.
I have no idea what could be wrong.
Ideas?
I just updated from v11.0.8.8 to v11.0.9.9 today on the EU variant.
Downloaded the update via Oxygen Updater, then used the built in updater with the local file downloaded.
Before restarting the device, opened up Magisk, then clicked "Install to inactive slot" since the new update gets put on the inactive slot. After it installed, rebooted the phone, and done. Updated to latest, and kept root. Didn't even turn off the modules, although I only have 1 installed.
This is my usual method to keep root while updating.
I'm not sure where you got your Magisk from, but i'm using v23.0 from the official github page (HERE), and it still has MagiskHide built-in, and currently using it for all of my banking apps, and it works.
Most likely the issue is that you have used the old Magisk version to patch the file.
Download the app from the link above, and use that to patch your boot.img file.
While the extracted file should work as flashed, I like to just boot from it rather than flash it and make it "permanent".
Use fastboot boot patched_boot.img to boot using the file once only.
After starting up, you should have Magisk installed in a couple of seconds. It might prompt you to restart the phone when opening it first time, but just ignore that and do not restart as you'll lose the root. Alternatively, you can install the app when you're not rooted yet, and when you boot using the patched boot.img, you won't need to restart.
When done, Magisk should tell that you have 23.0(23000) installed.
Then just use the built-in Install > Direct Install (Recommended) option within Magisk to install it to the current slot.
Do NOT install it to inactive slot. This option only to be used when updating via OTA.
Other option:
Download the Magisk app from the link above, and rename it to magisk.zip then copy it to your phone.
Download TWRP from HERE to your PC and use fastboot flash recovery twrp.img to flash this recovery.
Reboot to recovery. (Might take 2-3 mins to boot first time)
Flash the magisk.zip using recovery.
That's all you should need to be able to root.
I appreciate the help.
I was so hopeful you gave me what I needed, but it didn't work.
So, It wasn't an update issue... it was more of an attempt to downgrade Magisk.
I always OTA the same way as you and it always works.
I also always get Magisk from the official Github page.
What I got excited about was that I wasnt aware there was a working TWRP! So I thought.. THAT will fix it.
I didnt flash it, I just booted from it. I flashed Magisk that way, BUT... still not rooted.
Here is the interesting bit.. when flashing Magisk via TWRP, it detected that my boot.img was already Magisk patched and not stock (Which is right). It's like the boot.img is correctly patched, Magisk just isn't seeing it.
I'd be ok with a full wipe and factory reset at this point, but I'm not even sure that will fix it.
** Edit - I tried manually flashing the latest full OOS downloaded from Oneplus. It didnt help. I finally factory reset and it's working now.
This is my fav. root method.
[GUIDE] Easiest way to root/magisk Oneplus 8 Pro
This method will not flash any custom recovery or any custom boots. Caution: I don't take any responsibility. Proceed with your own risk and resilience in mind Prerequisites: Oxygen OS 11 (tested with 11, issues reported with 10) and a PC with...
forum.xda-developers.com
ps000000 said:
This is my fav. root method.
[GUIDE] Easiest way to root/magisk Oneplus 8 Pro
This method will not flash any custom recovery or any custom boots. Caution: I don't take any responsibility. Proceed with your own risk and resilience in mind Prerequisites: Oxygen OS 11 (tested with 11, issues reported with 10) and a PC with...
forum.xda-developers.com
Click to expand...
Click to collapse
Agreed, this is a great method. I tried that too before I ended up doing a reset... no good. I somehow broke something with the rom outside of Magisk so that Magisk wouldnt work. Whatever it was, A full wipe fixed it..