Hi, Good Day Everyone...
After the second failure of installing Magisk, i've kinda frustrating, Just want to move from my N9208 quickly. I have latest Oreo Rom installed on my N950F Dual Sim (N950FXXS3CRDB). Waiting a week for the next try is really pain.... (Right i will wait for the next week to try again :crying
I've searching some of tutorial, but it's weird doesn't work. I think i did wrong Step on process. Please help in details for this.
what I did:
1. Boot to Download Mode
2. using Odin 3.12.3 install twrp-3.1.1-0-greatlte_V3.tar ( is this wrong? because there are Odin 3.13.1 and twrp 3.2.1.0 version out there)
3. before start Flashing, (in Odin, Auto Reboot and F. Reset Time is ticked) i hold Vol down + Bixby Button + Power Button and then click Start on Odin.
4. After that, i successfully get into TWRP
5. in this step, i confused, what should i choose, Read only or Swipe to allow Modification? two times i choose Read Only
6. after this, i did Format Data, and then back to Main Menu, and Select Reboot -> to Recovery
7. after re-Enter TWRP, i still not sure, Read only or Swipe to allow Modification? i still click Read Only
8. and then i Install Magisk-v16.0.zip (there is Magisk-v16.3.zip out there again... i wonder if this causing the problem)
9. after this, i reboot to system... i think i've been Successful. After a first setup, Magisk icon are there. but, Root not detected. When i try do install from inside Magisk app, i download the magisk, and when i try to get back into TWRP, only official binaries is happened...
which step i've missed?
on some tutorial, they said we must swipe to allow modification on step 5, the other said we must keep Read Only
Other thing i've read, they said we need to flash fix mount data from dr.ketan everytime , afteri flashed something on TWRP
How to properly install Magisk and got Root and safely get in to TWRP anytime we need to? PLease Guide me. I think it should help anyone with the same problem.
Big Thanks in Advance...
you forgot to install dm-no-verity before root with Magisk. and you should use the most recent TWRP version 3.2.1.0 that supports Oreo as well as Nougat
vriend80 said:
Hi, Good Day Everyone...
After the second failure of installing Magisk, i've kinda frustrating, Just want to move from my N9208 quickly. I have latest Oreo Rom installed on my N950F Dual Sim (N950FXXS3CRDB). Waiting a week for the next try is really pain.... (Right i will wait for the next week to try again :crying
I've searching some of tutorial, but it's weird doesn't work. I think i did wrong Step on process. Please help in details for this.
what I did:
1. Boot to Download Mode
2. using Odin 3.12.3 install twrp-3.1.1-0-greatlte_V3.tar ( is this wrong? because there are Odin 3.13.1 and twrp 3.2.1.0 version out there)
3. before start Flashing, (in Odin, Auto Reboot and F. Reset Time is ticked) i hold Vol down + Bixby Button + Power Button and then click Start on Odin.
4. After that, i successfully get into TWRP
5. in this step, i confused, what should i choose, Read only or Swipe to allow Modification? two times i choose Read Only
6. after this, i did Format Data, and then back to Main Menu, and Select Reboot -> to Recovery
7. after re-Enter TWRP, i still not sure, Read only or Swipe to allow Modification? i still click Read Only
8. and then i Install Magisk-v16.0.zip (there is Magisk-v16.3.zip out there again... i wonder if this causing the problem)
9. after this, i reboot to system... i think i've been Successful. After a first setup, Magisk icon are there. but, Root not detected. When i try do install from inside Magisk app, i download the magisk, and when i try to get back into TWRP, only official binaries is happened...
which step i've missed?
on some tutorial, they said we must swipe to allow modification on step 5, the other said we must keep Read Only
Other thing i've read, they said we need to flash fix mount data from dr.ketan everytime , afteri flashed something on TWRP
How to properly install Magisk and got Root and safely get in to TWRP anytime we need to? PLease Guide me. I think it should help anyone with the same problem.
Big Thanks in Advance...
Click to expand...
Click to collapse
Me myself, i select always "swipe to allow modifications"
Since you are on Oreo use Odin 3.13.1 and TWRP 3.2.1-2 by Tkkg1994:
https://forum.xda-developers.com/showpost.php?p=76514731&postcount=741
After you format data with the "yes" command and reboot into recovery you need to flash the
No verity opt encrypt zip from here (use the latest 6.0):
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
Also you need the RMM state fix! (IMPORTANT)
You will find the flashable zip file here:
https://forum.xda-developers.com/showpost.php?p=75360965&postcount=22
After that flash magisk.zip or SuperSU.zip to root your device.
After first boot in setup wizard uncheck diagnostic data.
Then enable the developer options and check if the OEM Toogle is available and enabled! (IMPORTANT) with rooted device this toggle must available and enabled all the time! If not, you will get in jail again after a phone reboot.
Gesendet von meinem SM-N950F mit Tapatalk
khoanb1 said:
you forgot to install dm-no-verity before root with Magisk. and you should use the most recent TWRP version 3.2.1.0 that supports Oreo as well as Nougat
Click to expand...
Click to collapse
Logel said:
Me myself, i select always "swipe to allow modifications"
Since you are on Oreo use Odin 3.13.1 and TWRP 3.2.1-2 by Tkkg1994:
https://forum.xda-developers.com/showpost.php?p=76514731&postcount=741
After you format data with the "yes" command and reboot into recovery you need to flash the
No verity opt encrypt zip from here (use the latest 6.0):
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
Also you need the RMM state fix! (IMPORTANT)
You will find the flashable zip file here:
https://forum.xda-developers.com/showpost.php?p=75360965&postcount=22
After that flash magisk.zip or SuperSU.zip to root your device.
After first boot in setup wizard uncheck diagnostic data.
Then enable the developer options and check if the OEM Toogle is available and enabled! (IMPORTANT) with rooted device this toggle must available and enabled all the time! If not, you will get in jail again after a phone reboot.
Gesendet von meinem SM-N950F mit Tapatalk
Click to expand...
Click to collapse
Ah, i forgot to mention that i did flash dm verity on step 8 before flash Magisk.
But i didn't use rmm fix, i just read about that too.
Big thank you for explaining this in details.
A few more question:
1. should i Reboot to twrp after flash dm-verity and rmm fix too? Or is it ok to flash it in a single shot ( dm-verity -> rmmfix -> Magisk ) ?
2. When all is done, i think we can go into system right now, and make sure oem unlock toggle showing and always switched on. So i must not reboot if the toggle not show up?
3. What is get in jail means? Is that means Wait for another week?
4. So i don't need mount data fix from dr.ketan?
Thank you so much @Logel for the explanation
vriend80 said:
Ah, i forgot to mention that i did flash dm verity on step 8 before flash Magisk.
But i didn't use rmm fix, i just read about that too.
Big thank you for explaining this in details.
A few more question:
1. should i Reboot to twrp after flash dm-verity and rmm fix too? Or is it ok to flash it in a single shot ( dm-verity -> rmmfix -> Magisk ) ?
2. When all is done, i think we can go into system right now, and make sure oem unlock toggle showing and always switched on. So i must not reboot if the toggle not show up?
3. What is get in jail means? Is that means Wait for another week?
4. So i don't need mount data fix from dr.ketan?
Thank you so much @Logel for the explanation
Click to expand...
Click to collapse
1. You should can flash it in a single shot
2. No. Don't reboot if you don't see the OEM Toggle. See answer for point 3
3. Correct. In jail means, you can't reboot your phone. You will get a black screen with a red information line and the only way is to flash a stick Rom again. And after flash a stock Rom in most cases you have to wait again 168 hours until the OEM Toggle is visible again.
4. Nope. You have all fixed by yourself [emoji6][emoji106]
5. If you don't see the OEM Toggle you can use the phone. You only may not reboot it for the next 168 hours! After that time the OEM Toggle should be visible again. Now you can enable the toggle and reboot as often you want
Sent from my SM-N950F using Tapatalk
Is the info in this thread also valid for the N950N?
Thanks...
rljuss said:
Is the info in this thread also valid for the N950N?
Thanks...
Click to expand...
Click to collapse
yes it's the same since N950N and N950F are both Exynos variants
Logel said:
1. You should can flash it in a single shot
2. No. Don't reboot if you don't see the OEM Toggle. See answer for point 3
3. Correct. In jail means, you can't reboot your phone. You will get a black screen with a red information line and the only way is to flash a stick Rom again. And after flash a stock Rom in most cases you have to wait again 168 hours until the OEM Toggle is visible again.
4. Nope. You have all fixed by yourself [emoji6][emoji106]
5. If you don't see the OEM Toggle you can use the phone. You only may not reboot it for the next 168 hours! After that time the OEM Toggle should be visible again. Now you can enable the toggle and reboot as often you want
Sent from my SM-N950F using Tapatalk
Click to expand...
Click to collapse
Wahhh, Excellent Explanations... Thank you very Much @Logel for the answers... I just need to read this carefully and slowly before proceeding the third chance. :good:
Hi @Logel ,
Today my Oem Unlock Button is re appear. I just don't want to fail again.
I want to ask, what is Samsung AntiRoot Removal? is that necessary to use in Root Process?
Thank you in Advance
Good morning
What is Samsung anti root removal? I think i never heard it before
Gesendet von meinem SM-N950F mit Tapatalk
Logel said:
Good morning
What is Samsung anti root removal? I think i never heard it before
Gesendet von meinem SM-N950F mit Tapatalk
Click to expand...
Click to collapse
oh, i think i shouldn't use it.
thank you for confirmation. Preparing to root for the third times... :laugh:
Good luck, mate ?
Gesendet von meinem SM-N950F mit Tapatalk
Logel said:
Good luck, mate ?
Gesendet von meinem SM-N950F mit Tapatalk
Click to expand...
Click to collapse
@Logel ,
I've Just Done Installing TWRP and Magisk.
this is first Boot, already initial setup, and then, when i open Magisk, it's not installed. what happened?
Oem Unlock is Visible right Now. i need to install Magisk 16.0 again.
when i was on first try two weeks ago, after reboot i got jailed when trying to install Magisk 16.0 again. Please look at my Attachment.
Thank you @Logel
Sorry for late answer. I was busy.
If your OEM toggle is visible and unlocked (like in your ss) all is fine. Also if you have flushed the RMM state fix you are safe.
Now you should can reboot as often you want!
I always use supersu instead magisk, so i can't really tell you what to do. I would recommend to reboot into twrp recovery and flash the magisk zip again.
Have you flashed a custom Rom?
It looks a bit strange. You haven't magisk installed, but you successful passed safetyNet.
Gesendet von meinem SM-N950F mit Tapatalk
Logel said:
Sorry for late answer. I was busy.
If your OEM toggle is visible and unlocked (like in your ss) all is fine. Also if you have flushed the RMM state fix you are safe.
Now you should can reboot as often you want!
I always use supersu instead magisk, so i can't really tell you what to do. I would recommend to reboot into twrp recovery and flash the magisk zip again.
Have you flashed a custom Rom?
It looks a bit strange. You haven't magisk installed, but you successful passed safetyNet.
Gesendet von meinem SM-N950F mit Tapatalk
Click to expand...
Click to collapse
Hi, I'm not using Custom ROM, i'm using Stock ROM. i Think i'll try re-flash Magisk and see what will happen.
Thank you so Much @Logel for your Help
Just want to Report, i successfully installed Magisk an now it's rooted.
Now i'll try Systemless Xposed INstaller, hope this work.
Thanks again Mate @Logel for your Help
Update:
Install Systemless xposed on my N950F DS cause reboot immediately after first reboot. i Think it's not safe to use systemless xposed right now.
updtae 2:
Right Now, I'am using Xposed Installer without a problem.
Related
This is an unofficial TWRP port for LG-H960A.
Thanks to @KAsp3rd and @GROGG88
I DON'T TAKE ANY RESPONSIBILITY. YOU DO EVERYTHING AT YOUR OWN RISK.
READ EVERYTHING and MAKE A BACKUP BEFORE YOU START.
Instructions:
1. You must be on newest stock Marshmallow: H960A20a_00_0316.kdz
You can use LG Bridge to install official update, or download .kdz file HERE
2. You need to have bootloader ulocked.
Official instructions are here: ( Unlocking the Bootloader @ LG Developer )
Remember that this will completely WIPE YOUR DATA, you will LOSE WARRANTY and this operation is IRREVERSIBLE.
3. Flash TWRP.
I assume you got ADB and FASTBOOT drivers working and adb is paired (it should be if you completed step 2).
Connect your phone to your pc, open command prompt and reboot to bootloader:
Code:
adb reboot bootloader
Your phone should reboot and you should be welcomed by Fastboot Mode screen.
Now download the recovery file (below) to your pc, unpack (to get .img) and rename it to recovery.img and put it in folder where you got command prompt open and:
Code:
fastboot flash recovery recovery.img
4. Boot to TWRP.
As on Marshmallow some fastboot commands are not working and LG is restoring recovery on every boot (so you cant use "adb reboot recovery" right now) you need to use one trick.
DO NOT REBOOT YOUR PHONE.
When still in fastboot from step 3 you need to turn off your phone completely. You can do that by holding power button or if that is not working take the battery out.
Now (put the battery in) and press POWER + VOL DOWN buttons. When you see LG logo release the POWER button (while still holding VOL DOWN) and press POWER button again.
You should see a screen which is asking you if you want to factory reset your phone. Don't worry - if you made everything correctly it should not wipe your phone.
Use volume and power buttons to choose YES (twice) - and you should see a TWRP screen (after a while)
WARNING: IF YOU REBOOTED YOUR PHONE AFTER FLASHING RECOVERY THIS STEP WILL REALLY ERASE ALL DATA. You need to flash recovery again (step 3)
5. (optional) flash SuperSU to get root.
Get SuperSU from official thread and put it in your phone.
While in TWRP from step 4 your phone should be recognized by ADB. Use below to move file to sdcard.
Code:
adb push BETA-SuperSU-v2.74-2-20160519174328.zip /sdcard/supersu.zip
Now in TWRP click Install, go to /sdcard/ and chooose supersu.zip. Follow instructions. After install you should choose to wipe cache/dalvik and reboot to system.
Your phone should be rooted now.
Download:
twrp-3.0.2.0-0-h960a.img.zip
(unpack .zip to get flashable .img)
Issues:
- Layout is wrong, status bar is being drawn on second screen.
- Date/time is wrong.
broken url
OK, now if we have recovery, is it possible to dump rooted system and pack it to .tot file for people who don't want to lose warranty?
11868 said:
broken url
Click to expand...
Click to collapse
Oh, true. Fixed.
rascal0pl said:
OK, now if we have recovery, is it possible to dump rooted system and pack it to .tot file for people who don't want to lose warranty?
Click to expand...
Click to collapse
Maybe.
Thank You it worked!
Great. Just bought it 2 days ago for good price. Will try it.
Sent from my LG-H955 using Tapatalk
Hi,
that's just great, thanks a lot.
As root is now possible has anyone tried to install xposed on th H960A?
I'm wondering if the second screen fix for the Telekom V10 also works with the H960A.
What about Viper4Android and AdAway?
rudi666 said:
This is an unofficial TWRP port for LG-H960A.
Thanks to @KAsp3rd and @GROGG88
I DON'T TAKE ANY RESPONSIBILITY. YOU DO EVERYTHING AT YOUR OWN RISK.
READ EVERYTHING and MAKE A BACKUP BEFORE YOU START.
Instructions:
1. You must be on newest stock Marshmallow: H960A20a_00_0316.kdz
You can use LG Bridge to install official update, or download .kdz file HERE
2. You need to have bootloader ulocked.
Official instructions are here: ( Unlocking the Bootloader @ LG Developer )
Remember that this will completely WIPE YOUR DATA, you will LOSE WARRANTY and this operation is IRREVERSIBLE.
3. Flash TWRP.
I assume you got ADB and FASTBOOT drivers working and adb is paired (it should be if you completed step 2).
Connect your phone to your pc, open command prompt and reboot to bootloader:
Code:
adb reboot bootloader
Your phone should reboot and you should be welcomed by Fastboot Mode screen.
Now download the recovery file (below) to your pc, unpack (to get .img) and rename it to recovery.img and put it in folder where you got command prompt open and:
Code:
fastboot flash recovery recovery.img
4. Boot to TWRP.
As on Marshmallow some fastboot commands are not working and LG is restoring recovery on every boot (so you cant use "adb reboot recovery" right now) you need to use one trick.
DO NOT REBOOT YOUR PHONE.
When still in fastboot from step 3 you need to turn off your phone completely. You can do that by holding power button or if that is not working take the battery out.
Now (put the battery in) and press POWER + VOL DOWN buttons. When you see LG logo release the POWER button (while still holding VOL DOWN) and press POWER button again.
You should see a screen which is asking you if you want to factory reset your phone. Don't worry - if you made everything correctly it should not wipe your phone.
Use volume and power buttons to choose YES (twice) - and you should see a TWRP screen (after a while)
WARNING: IF YOU REBOOTED YOUR PHONE AFTER FLASHING RECOVERY THIS STEP WILL REALLY ERASE ALL DATA. You need to flash recovery again (step 3)
5. (optional) flash SuperSU to get root.
Get SuperSU from official thread and put it in your phone.
While in TWRP from step 4 your phone should be recognized by ADB. Use below to move file to sdcard.
Code:
adb push BETA-SuperSU-v2.74-2-20160519174328.zip /sdcard/supersu.zip
Now in TWRP click Install, go to /sdcard/ and chooose supersu.zip. Follow instructions. After install you should choose to wipe cache/dalvik and reboot to system.
Your phone should be rooted now.
Download:
twrp-3.0.2.0-0-h960a.img.zip
(unpack .zip to get flashable .img)
Issues:
- Layout is wrong, status bar is being drawn on second screen.
- Date/time is wrong.
Click to expand...
Click to collapse
Are there any other known issues? I don`t need to install any custom roms. I need it only for root and xposed on Marshmallow. Is there something that can surprise me?
Hi,
"OK, now if we have recovery, is it possible to dump rooted system and pack it to .tot file for people who don't want to lose warranty? "
Ohh, thats sounds nice if this realy possible.
i love my v10.
orbitandre said:
hi,
"ok, now if we have recovery, is it possible to dump rooted system and pack it to .tot file for people who don't want to lose warranty? "
ohh, thats sounds nice if this realy possible.
i love my v10.
Click to expand...
Click to collapse
+1 ??
cyvr1 said:
As root is now possible has anyone tried to install xposed on th H960A?
I'm wondering if the second screen fix for the Telekom V10 also works with the H960A.
What about Viper4Android and AdAway?
Click to expand...
Click to collapse
Didn't try xposed but I think it should work (if it's working on other V10 models - they are not that different). I just recently bought V10 and was disappointed in dpi, so I needed root to patch second screen to be dpi-independent.
Also: why would you want things like Viper4Android when you got really good sounding hifi dac onboard?
fixxxer102 said:
Are there any other known issues? I don`t need to install any custom roms. I need it only for root and xposed on Marshmallow. Is there something that can surprise me?
Click to expand...
Click to collapse
For sure it's enough to flash packages and get root. Xposed is independent from recovery so I can't say anything about that.
Testing are up to you guys. Don't be afraid as this phone is not easy to brick.
rudi666 said:
Also: why would you want things like Viper4Android when you got really good sounding hifi dac on board?
Click to expand...
Click to collapse
Quite simple answer. The onboard Hifi DAC only works with cable headphones. Viper4Android also supports Bluetooth devices.
rudi666 said:
I just recently bought V10 and was disappointed in dpi, so I needed root to patch second screen to be dpi-independent.
Click to expand...
Click to collapse
Could you write a small guide about the dpi change (I prefer 540-580)?
Thanks in advance.
cyvr1 said:
Quite simple answer. The onboard Hifi DAC only works with cable headphones. Viper4Android also supports Bluetooth devices.
Click to expand...
Click to collapse
Ah, you are right, that makes perfect sense. Sorry, I forgot about that.
paschalism said:
Could you write a small guide about the dpi change (I prefer 540-580)?
Click to expand...
Click to collapse
There is still a long way, right now second screen FCs are fixed, but layouts are still wrong. I don't know if I can fix it to be truly dpi-independent but I think 560 is optimal value for this screen.
Is this working with
H960a
V20a-AME-xx??
1k views and only 11 "thanks"??? Really? Guys! We need support devs! Big THANK YOU for ur hard work @rudi666. I haven't try ur method yet but I am happy with the fact that something is beginning to happen with v10
Wysłane z mojego LG-H960 przy użyciu Tapatalka
asmoroth said:
I haven't try ur method yet but I am happy with the fact that something is beginning to happen with v10
Click to expand...
Click to collapse
I did try his method and it worked like a charm. Ok, you'll have to reflash TWRP if you want to use it but I'm sure it's just a matter of time until we have permanent TWRP like th T-Mobile V10 obviously has.
Thanks to rudi666 I have root, xposed, adaway and viper4audio up and running on my V10. And as there are no interesting custom roms to flash in my opinion it does not matter that I'd need to reflash TWRP. If you plan your flashing in advance you can flash all zip files in one go. No real need for TWRP afterwards.
Thanks guys. Unfortunately I see there is not much going on in V10 scene, and it's a shame.
cyvr1 said:
Ok, you'll have to reflash TWRP if you want to use it but I'm sure it's just a matter of time until we have permanent TWRP like th T-Mobile V10 obviously has.
Click to expand...
Click to collapse
Hm.. if you follow instructions you should get permanent TWRP, just try "adb reboot recovery" to test it if you don't want to risk clearing data when using button combination. There is a file called /system/boot-from-recovery.p which is 'restoring recovery' on every boot (that's why there is an info in instruction about not rebooting your phone the first time), but after all the steps this file will be patched. I don't remember if the first use of TWRP or flashing SuperSU does it, but you should get permanent recovery. If not you can always rename this file manually.
rudi666 said:
Hm.. if you follow instructions you should get permanent TWRP, just try "adb reboot recovery" to test it if you don't want to risk clearing data when using button combination. There is a file called /system/boot-from-recovery.p which is 'restoring recovery' on every boot (that's why there is an info in instruction about not rebooting your phone the first time), but after all the steps this file will be patched. I don't remember if the first use of TWRP or flashing SuperSU does it, but you should get permanent recovery. If not you can always rename this file manually.
Click to expand...
Click to collapse
Hi,
I will try that again and see if I can get permanent TWRP. But as I said currently there is no real requirement for that. I flashed SuperSU and both files for xposed when I first booted into recovery and that is all I need at the moment.
i cant enter bootloader
h960A
after adb reboot booloader it keeb restart to soft
UPDATED AND EDITED
Hello everyone. I decided to edit my first post on this thread to make finding the instructions on how to Root & Install TWRP along with Magisk on the LG ARISTO or LV3 for T-Mobile/Metro PCS
WARNING:
I AM NOT RESPONSIBLE IF YOU BRICK YOUR PHONE, DAMAGE IT, GET IT STUCK ON BOOTLOOP, MAKE YOUR DEVICE CAUSE A NUCLEAR EXPLOSIVE, OR HAVE IT CAUSE A ZOMBIE APOCALYPSE. TRY AT YOUR OWN RISK.
But if you follow Messi's instructions down to a tee. You shouldn't have any problem
The stock boot image has dm-verity, which prevents you from booting if you swipe to enable system modifications after flashing twrp!
SOLUTION:
Flash a root such as SuperSU or Magisk V13.3 You should also flash no-verity-opt-encrypt.zip. (although I was informed you might not need to with Magisk, again try at your own risk)
Prerequisites :
Enable OEM Unlocking and usb debugging in developer options!
Go to settings
About Phone
Software Info
And press on Build Number about 9 times
You will see a pop up notifying you that you have unlocked Developer Options
Go Back and you should see the new settings option
Enter Developer Options
Enable it, select ok
Enable OEM unlock
And finally disable Automatic System Updates
UNLOCKING BOOTLOADER
(You must be familiar with Command Prompt on Windows)
• YOUR BOOTLOADER MUST BE UNLOCKED
- reboot into fastboot [ adb reboot bootloader ]
- fastboot oem unlock [ this is going to wipe your data ]
If you have problems with the device drivers installed , you will need to install lg bridge app from lg that contains the device driver
http://tool.lime.gdms.lge.com/dn/downloader.dev?fileKey=PWZO7A26B9UW
How to flash the recovery:
• BOOT INTO FASTBOOT MODE:
With your phone off, connect your usb cable to your phone while holding VOLUME DOWN to boot into fastboot mode or just type [adb reboot bootloader] in the adb terminal
• ONCE YOU ARE IN FASTBOOT MODE:
Open a command prompt and type "fastboot flash recovery <path_to_recovery.img>” without the quotation marks.
Example: fastboot flash recovery C:/Users/John/Desktop/recovery.img
[don't forget to extract the downloaded recovery zip to get the recovery.img]
• WHEN THE FLASH COMPLETES: (Takes about 2 seconds)
On your phone, unplug the usb cable and power it off by taking out the battery and putting it back in.
• BOOT INTO RECOVERY MODE FOR THE FIRST TIME
HOLD VOLUME DOWN + POWER until you see the LG logo and then temporarily release the POWER button, immediately pressing and holding it back down until you see the white prompt [factory reset] screen. You will NEVER release the volume down button in this process!
Use the hard keys to select "YES" and then "YES" again to boot into TWRP!
How to Disable encryption & flash super su
1. In TWRP, go to Wipe > Format Data. Enter the keyword ‘yes‘, in the provided space and enter. This will wipe the automatically encrypted filesystem, and decrypt it.
2. Once the wiping is done, reboot back into recovery. Go to Reboot > Recovery.
3. When the recovery boots again, connect your phone to the PC and Enable MTP under the Mount section.
4. Transfer the downloaded ‘no-verity-opt-encrypt-5.1.zip’ and ‘UPDATE-SuperSU-v2.82-20170528234214.zip or if you wants MAGISK then the MagiskV13.zip to your internal storage or EXTSD
5. Disconnect the device now.
6. Tap on Install. Now, navigate your phone’s storage and select ‘no-verity-opt-encrypt-5.1.zip’. Finally swipe the ‘Swipe to confirm Flash’ button on the bottom of the screen.
7. The flashing process will merely take a few seconds. And when it’s done, follow the same method to flash the root package – UPDATE-SuperSU-v2.82-20170528234214.zip or you can flash the MAGISKV13.zip
Wait 1 or 2 minutes after the zip files are done flashing then reboot system and PROFIT! Your phone may take 3-5 minutes to boot the first time and it might boot-loop once or twice at the Metro PCS splash screen but don’t worry this is expected.
DOWNLOADS
All required files [supersu+dm-verify disable] can be found in this thread :
https://forum.xda-developers.com/lg-g5/development/recovery-team-win-recovery-project-lg-g5-t3363047
MAGISK V13.3 by topjohnwu
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
#2 build [stable]
http://www.mediafire.com/file/x1bo7scmrga40q5/lg_aristo_twrp_v3_stable_build_by_messi2050.zip
#2 build Changelog:
-fixed device gets wiped everytime you use the hardware buttons to boot into twrp.
-fixed flashing boot/recovery images through twrp
-built using latest twrp source.
[do not mirror the downloads]
Notice: After the TWRP splash screen you will see the option to type in the password to decrypt the filesystem. just ignore it and hit the cancel button.
--------------------------------------------------------------------------------------------------------
Please note I don't own this device and spend a lot of my free time bringing these builds for you to use and benefit from So Please Consider donating using the link below if you appreciate my work.
https://www.paypal.me/messi2050
THANKS AND CREDIT
I do not take any credit for this. All the thanks and credit go to:
@Messi:
https://androidforums.com/members/messi2050.1983077/
For taking time to build a TWRP Recovery for us without actually owning the device. Much credit and a million thanks.
@topjohnwu
https://forum.xda-developers.com/member.php?u=4470081
For their hard work on the Magisk systemless interface software and dedication to keep on developing the software especially for a lot of us Nougat phone owners. Thanks thanks thanks
Special Thanks
@phhusson for his advice with sepolicy and his sepolicy injection tool, boot image tools, hide su tools, superuser
@Chainfire for many bits of shell script code, his supolicy in older versions, and the complete documentation How-To SU
@nkk71 for his original resetprop
@osm0sis for his shell script for image/zip size detection, unSU, addon.d, also providing numerous support for all kinds of boot image unpacking knowledge
@digitalhigh and @DVDandroid for massive contributions to Magisk Manager
@Captain_Throwback for being the No.1 supporter, testing and finding bugs all the time
Ortem1UP said:
Hello everyone. I'm no stranger to rooting and TWRP. Always looking for rooting methods for wtv device I own. I currently own an LG LV3 or Aristo running Nougat 7.0 and successfully rooted it via adb as well as installed a fully functional TWRP thanks to Messi's method.
Now when it comes to Xposed I'm no novice. But unfortunately there isn't a Nougat compatible one yet. So I'm going with the alternative Magisk. But I am a complete noob when it comes to Magisk.
Can I simply flash the Magisk zip and follow the steps mentioned on the Magisk forum? Also, will MagiskSU replace my current SU without any flaws?
Any help would be appreciated
Click to expand...
Click to collapse
Depends on what root solution you're currently using. If you're using systemless SuperSU Magisk won't replace it, but use that instead. In that case you'll have to first remove SuperSU. If you're using any other root Magisk will try to replace it with MagiskSU (no guarantees). Also, I believe LG devices need a "bump" script, or something like that... I also believe this has been added to the Magisk code, but is not yet in the official release. If v11.1 doesn't work, you could try the unofficial beta snapshot: https://forum.xda-developers.com/apps/magisk/unofficial-magisk-v10-beta-built-t3521901
And just to clarify: Magisk is not an alternative to Xposed... You can do certain things with Magisk that can also be done with Xposed, but they work in completely different ways. Think of Magisk as a "file injector" where it can replace files and props on your device at boot, completely systemless. And along the same kind of thinking Xposed is a "code injector" that can alter the code of a running app. This can also be made systemless, by tools such as Magisk. @topjohnwu have hinted at ideas about making Magisk work as a "code injector", but this is purely on the idea stage at the moment and is probably quite far away in a possible future.
Take a look in the release thread and the Magisk All-In-One Wiki (both stickied at the top). They contain a lot of useful information. There's also a lot of information in the support thread, which is pretty big by now so the search function is a good tool there.
I've also collected a bunch of tips and tricks for Magisk installation and troubleshooting, and as well for Magisk Hide if you want to use that:
https://forum.xda-developers.com/apps/magisk/magisk-magisk-hide-troubleshooting-tips-t3561828
Didgeridoohan said:
Depends on what root solution you're currently using. If you're using systemless SuperSU Magisk won't replace it, but use that instead. In that case you'll have to first remove SuperSU. If you're using any other root Magisk will try to replace it with MagiskSU (no guarantees). Also, I believe LG devices need a "bump" script, or something like that... I also believe this has been added to the Magisk code, but is not yet in the official release. If v11.1 doesn't work, you could try the unofficial beta snapshot: https://forum.xda-developers.com/apps/magisk/unofficial-magisk-v10-beta-built-t3521901
And just to clarify: Magisk is not an alternative to Xposed... You can do certain things with Magisk that can also be done with Xposed, but they work in completely different ways. Think of Magisk as a "file injector" where it can replace files and props on your device at boot, completely systemless. And along the same kind of thinking Xposed is a "code injector" that can alter the code of a running app. This can also be made systemless, by tools such as Magisk. @topjohnwu have hinted at ideas about making Magisk work as a "code injector", but this is purely on the idea stage at the moment and is probably quite far away in a possible future.
Take a look in the release thread and the Magisk All-In-One Wiki (both stickied at the top). They contain a lot of useful information. There's also a lot of information in the support thread, which is pretty big by now so the search function is a good tool there.
I've also collected a bunch of tips and tricks for Magisk installation and troubleshooting, and as well for Magisk Hide if you want to use that:
https://forum.xda-developers.com/apps/magisk/magisk-magisk-hide-troubleshooting-tips-t3561828
Click to expand...
Click to collapse
Thank you so much. I will definitely look over the links you shared and try some out. I couldn't thank you enough for taking the time to reply and with a ton of info. I'm bound to find something that works. Thanks again.
Sent from my lv3 using XDA Labs
Ortem1UP said:
Hello everyone. I'm no stranger to rooting and TWRP. Always looking for rooting methods for wtv device I own. I currently own an LG LV3 or Aristo running Nougat 7.0 and successfully rooted it via adb as well as installed a fully functional TWRP thanks to Messi's method.
Now when it comes to Xposed I'm no novice. But unfortunately there isn't a Nougat compatible one yet. So I'm going with the alternative Magisk. But I am a complete noob when it comes to Magisk.
Can I simply flash the Magisk zip and follow the steps mentioned on the Magisk forum? Also, will MagiskSU replace my current SU without any flaws?
Any help would be appreciated
Click to expand...
Click to collapse
so what method did you use to root? I can't find any documentation anywhere
brad2192 said:
so what method did you use to root? I can't find any documentation
Here is the link. Sorry for the late response been busy with work and school I'm not sure if this is against the XDA rules like sharing a link to another Forum but here you go
http://androidforums.com/threads/recovery-twrp-v3-for-lg-aristo-metropc-t-mobile.1117942/
Sent from my lv3 using XDA Labs
Click to expand...
Click to collapse
Ortem1UP said:
Thank you so much. I will definitely look over the links you shared and try some out. I couldn't thank you enough for taking the time to reply and with a ton of info. I'm bound to find something that works. Thanks again.
Sent from my lv3 using XDA Labs
Click to expand...
Click to collapse
Did you ever get this figured out? Kinda curious if I can do this without wiping.
BrothelWaffles said:
Did you ever get this figured out? Kinda curious if I can do this without wiping.
Click to expand...
Click to collapse
I almost did but I got stuck on bootloop. The only way I can think it might work would be to return to stock. Follow Messi's method for Twrp & Root. But at the point of root. U can stick with Chainfires SuperSU, or use the latest MagiskSU by Topjohnwu (would recommend)
Then just reboot the device and follow TopJohnwus method of installing Magisk.
But don't take my word for it. It's just and idea. I've yet to try it Cuz I haven't really had time. So it's up to you if u wanna give it a shot.
Or u can wait for me to try it. I was thinking of doing it 2nite. It's 930pm pst
I say around 11-12 I will be giving it another go. Wtv my results are. I will report back. Wish me luck
SUCCESS
I got Magisk to work on My LG Aristo as of today. It was just as I thought.
I went back to stock. Then I followed Messi's method to get TWRP installed. Since I already had my bootloader unlocked. I didnt need to worry about it. Just flashed TWRP via adb as Messi says to do. Unplugged my device and pulled out the battery to turn of my device. Put it back in and rebooted into recovery. Went to wipe and formatted data. Once it was done. Went back and went into Reboot. Rebootted back into recovery. Plugged my phone to my laptop, enabled mtp and transferred both the no-verity-opt-encrypt-2.1.zip file and magiskzip file. Didn't need SuperSu seeing as how Magisk alone roots the device. Flashed the no-verity-opt-encrypt-2.1.zip first and then Magiskzip. Latest version is V13.2 right now. It automatically installs Magisk Manager since it isn't available on the Play Store anymore. Rebooted system. Waited for my phone to start. Set it up and immediately tested it. And Magisk is 100% fully functional with all green checkmarks. Hope it helps. Maybe I should create a thread. Would be my first one. Don't really know how to tho. But I'll try.
Also, here are the snapshots of proof and my magisk settings to get them to pass.
Ortem1UP said:
SUCCESS
I got Magisk to work on My LG Aristo as of today. It was just as I thought.
I went back to stock. Then I followed Messi's method to get TWRP installed. Since I already had my bootloader unlocked. I didnt need to worry about it. Just flashed TWRP via adb as Messi says to do. Unplugged my device and pulled out the battery to turn of my device. Put it back in and rebooted into recovery. Went to wipe and formatted data. Once it was done. Went back and went into Reboot. Rebootted back into recovery. Plugged my phone to my laptop, enabled mtp and transferred both the dm-verity file and magiskzip file. Didn't need SuperSu seeing as how Magisk alone roots the device. Flashed Dm-verity first and then Magiskzip. Latest version is V12 right now. Rebooted system. Waited for my phone to start. Set it up and immediately updated Magisk Manager and viola. Magisk is 100% fully functional with all green checkmarks. Hope it helps. Maybe I should create a thread. Would be my first one tho. Don't really know how to tho. But I'll try.
Also, here are the snapshots of proof and my magisk settings to get them to pass.
Click to expand...
Click to collapse
Thank you so much your a life saver I finally have magisk installed right
Hey ortem, have you had an issue with magisk modules knocking out cell service upon reboot?
Anyone install this by unrooting\uninstalling supersu and flashing the zips...its crazy i have to go all the way back to square one just to install this...any help appreciated
jessebanks said:
Anyone install this by unrooting\uninstalling supersu and flashing the zips...its crazy i have to go all the way back to square one just to install this...any help appreciated
Click to expand...
Click to collapse
Use the full uninstall provided within the supersu app and restart your phone, then go into recovery and flash magisk.
Ortem1UP said:
SUCCESS
I got Magisk to work on My LG Aristo as of today. It was just as I thought.
I went back to stock. Then I followed Messi's method to get TWRP installed. Since I already had my bootloader unlocked. I didnt need to worry about it. Just flashed TWRP via adb as Messi says to do. Unplugged my device and pulled out the battery to turn of my device. Put it back in and rebooted into recovery. Went to wipe and formatted data. Once it was done. Went back and went into Reboot. Rebootted back into recovery. Plugged my phone to my laptop, enabled mtp and transferred both the dm-verity file and magiskzip file. Didn't need SuperSu seeing as how Magisk alone roots the device. Flashed Dm-verity first and then Magiskzip. Latest version is V12 right now. Rebooted system. Waited for my phone to start. Set it up and immediately updated Magisk Manager and viola. Magisk is 100% fully functional with all green checkmarks. Hope it helps. Maybe I should create a thread. Would be my first one tho. Don't really know how to tho. But I'll try.
Also, here are the snapshots of proof and my magisk settings to get them to pass.
Click to expand...
Click to collapse
Hi Ortem1UP, I get the jist of the method but not sure what the dm-verity parts are. Can you explain what this is for, and where are you getting it and what version? Is dm-verity the same as no-verity-opt-encrypt-2.1.zip that messi describes in his twrp tutorial for the Aristo?
azizLIGHT said:
Hi Ortem1UP, I get the jist of the method but not sure what the dm-verity parts are. Can you explain what this is for, and where are you getting it and what version? Is dm-verity the same as no-verity-opt-encrypt-2.1.zip that messi describes in his twrp tutorial for the Aristo?
Click to expand...
Click to collapse
Oh wow. So sorry. I hadn't noticed my mistake. Yes, the dm verity I accidentally mentioned is actually the no-verity-opt-encrypt zip that Messi mentions. I'll fix that mistake. Wouldn't want ppl to get confused. Thanks for that. BTW, the same method also works with the new Magisk V13.2. Just an FYI
Sent from my lv3 using XDA Labs
ninjasinabag said:
Hey ortem, have you had an issue with magisk modules knocking out cell service upon reboot?
Click to expand...
Click to collapse
I apologize for the very late reply.
Actually, no I haven't. Which modules did you install?
Sent from my lv3 using XDA Labs
Ortem1UP said:
Oh wow. So sorry. I hadn't noticed my mistake. Yes, the dm verity I accidentally mentioned is actually the no-verity-opt-encrypt zip that Messi mentions. I'll fix that mistake. Wouldn't want ppl to get confused. Thanks for that. BTW, the same method also works with the new Magisk V13.2. Just an FYI
Sent from my lv3 using XDA Labs
Click to expand...
Click to collapse
Ortem, while I was waiting for your reply, I went ahead and flashed the magisk zip (13.2) without flashing no-verity and I was able to get it to work. I have all green checks as well with SafetyNet. So the no-verity-opt-encrypt zip file may not be needed for magisk to work and to get root/safetynet pass
azizLIGHT said:
Ortem, while I was waiting for your reply, I went ahead and flashed the magisk zip (13.2) without flashing no-verity and I was able to get it to work. I have all green checks as well with SafetyNet. So the no-verity-opt-encrypt zip file may not be needed for magisk to work and to get root/safetynet pass
Click to expand...
Click to collapse
No way. Seriously? Does SafetyNet always pass? Because for me it does at times and other times it doesn't. I wonder if the no-verity-opt-encrypt.zip is to blame? I shall try it your way and see how that goes. Thanks for the heads up. Guess the zip is only needed for SuperSu. Not Magisk.
Sent from my lv3 using XDA Labs
Ortem1UP said:
No way. Seriously? Does SafetyNet always pass? Because for me it does at times and other times it doesn't. I wonder if the no-verity-opt-encrypt.zip is to blame? I shall try it your way and see how that goes. Thanks for the heads up. Guess the zip is only needed for SuperSu. Not Magisk.
Sent from my lv3 using XDA Labs
Click to expand...
Click to collapse
Yeah I'm actually passing SafetyNet sometimes as well and sometimes not. I can't figure out why that's the case. In any case, I don't think the no-verity-opt-encrypt.zip is to blame given since we're both experiencing the same symptoms!
azizLIGHT said:
Yeah I'm actually passing SafetyNet sometimes as well and sometimes not. I can't figure out why that's the case. In any case, I don't think the no-verity-opt-encrypt.zip is to blame given since we're both experiencing the same symptoms!
Click to expand...
Click to collapse
Oh OK. For a second I thought it was the zip file.
Anywho. IDK about you but ever since the latest update. I haven't had a single problem with Safety Net. It passes every time now. I hope your getting the same results?
Sent from my lv3 using XDA Labs
In the "first boot" after TWRP flash process. While holding power button+vol. Down . You must let go of the volume button to make the selection "yes" then "power" to select then hold "VOL DOWN" the next option comes up. Let go press "VOL DOWN" to select "YES" still holding down push "POWER" to make final selection along with DOWN and again proceed as you would when you first went into recovery. Now this in no way a insult to the work that's put into this but I believe in order to teach those that want to learn we must combine our knowledge and create an amazing Rom:victory:
Hi,
I used Magisc with several chinese brand phones and never had problems so far.
Now I got a new Moto Z, and I don't want to unlock the bootloader and install a custom recovery.
Is there another way to get Magisc working on my new device?
I understand the concept of systemless root and modification in general. The bootloader unlock and custom recovery installation do not fit in this concept, don't you think so?
Kind regards
Gesendet von meinem XT1650 mit Tapatalk
Not to hijack your thread, so consider this a free bump, but I am also curious. Galaxy S7 G920T here and looking for the same options.
JRapsky said:
Hi,
I used Magisc with several chinese brand phones and never had problems so far.
Now I got a new Moto Z, and I don't want to unlock the bootloader and install a custom recovery.
Is there another way to get Magisc working on my new device?
I understand the concept of systemless root and modification in general. The bootloader unlock and custom recovery installation do not fit in this concept, don't you think so?
Kind regards
Gesendet von meinem XT1650 mit Tapatalk
Click to expand...
Click to collapse
1 answer,,u can't..
Systemless mean that's it's doesn't messed with system partition so u can get the OTA update..
Or some app that detec change from system partition then refuse too work..
And to do that u need to flash TWRP and unlocked bootloader..
Sent from my Redmi 2 using Tapatalk
fake2die said:
1 answer,,u can't..
Systemless mean that's it's doesn't messed with system partition so u can get the OTA update..
Or some app that detec change from system partition then refuse too work..
And to do that u need to flash TWRP and unlocked bootloader..
Click to expand...
Click to collapse
Not completely accurate. Magisk modifies boot.img (boot partition) and to modify it, you need to have an unlocked bootloader.
veez21 said:
Not completely accurate. Magisk modifies boot.img (boot partition) and to modify it, you need to have an unlocked bootloader.
Click to expand...
Click to collapse
Right! So you can accomplish a Magisk install without a custom recovery for example using the Magisk Manager or Flashfire but as stated above, in order to boot a modified boot.img the bootloader needs to be unlocked or otherwise it will refuse to boot it.
There should be an option to install magisc like a systeme update with the stock recovery.
Gesendet von meinem XT1650 mit Tapatalk
JRapsky said:
There should be an option to install magisc like a systeme update with the stock recovery.
Click to expand...
Click to collapse
I don't think you understand how Android works, there are several stages to the system in which the actual /system rests. Basically everything is signed and validated to guarantee the installation of the official software and to protect the phone. Even if you can install Magisk via the stock recovery (which would require a phone specific Magisk which is the opposite of the universal interface that topjohnwu is targeting) you won't be able to boot the phone because the /boot partition is altered and the verity function won't allow an altered image to load in order to protect the phone. So in order to load the changes Magisk makes, the bootloader which checks and loads the boot.img (that's why it's called boot-loader) needs to be unlocked so it boots everything (the new boot.img needs to be compatible of course, you cannot boot the S8 img on the G6 for example). If I missed anything or something is wrong please correct me.
Sytis said:
I don't think you understand how Android works, there are several stages to the system in which the actual /system rests. Basically everything is signed and validated to guarantee the installation of the official software and to protect the phone. Even if you can install Magisk via the stock recovery (which would require a phone specific Magisk which is the opposite of the universal interface that topjohnwu is targeting) you won't be able to boot the phone because the /boot partition is altered and the verity function won't allow an altered image to load in order to protect the phone. So in order to load the changes Magisk makes, the bootloader which checks and loads the boot.img (that's why it's called boot-loader) needs to be unlocked so it boots everything (the new boot.img needs to be compatible of course, you cannot boot the S8 img on the G6 for example). If I missed anything or something is wrong please correct me.
Click to expand...
Click to collapse
but can we could not flash magisk file useing pc instead of custom recovery??(with unlock bootloder) if no then Y?
COOLPLAY6FAN said:
but can we could not flash magisk file useing pc instead of custom recovery??(with unlock bootloder) if no then Y?
Click to expand...
Click to collapse
Of course you can (with some possible limitations set by the OEM). With fastboot, for example. But you won't be using the recovery at all (stock or custom).
JRapsky said:
Hi,
I used Magisc with several chinese brand phones and never had problems so far.
Now I got a new Moto Z, and I don't want to unlock the bootloader and install a custom recovery.
Is there another way to get Magisc working on my new device?
I understand the concept of systemless root and modification in general. The bootloader unlock and custom recovery installation do not fit in this concept, don't you think so?
Kind regards
Gesendet von meinem XT1650 mit Tapatalk
Click to expand...
Click to collapse
Actually you can boot into twrp rather than install/flash twrp which means u must use cmd to boot twrp everytime for flashing something~ As for locked bootloader, just like others said, you must unlock it.
Didgeridoohan said:
Of course you can (with some possible limitations set by the OEM). With fastboot, for example. But you won't be using the recovery at all (stock or custom).
Click to expand...
Click to collapse
so can u gave proper guide to root useing magisc useing pc instead of custom recovery
(with unlock OEM)
Thanks in advance
COOLPLAY6FAN said:
so can u gave proper guide to root useing magisc useing pc instead of custom recovery
(with unlock OEM)
Thanks in advance
Click to expand...
Click to collapse
There are installation instructions on how to create the patched boot image with the Magisk Manager in the release thread.
When you have the patched_boot.img file, you'll need to flash it to your device. On most normal devices you can do this with fastboot. Check out your device's forums/DuckDuckGo/Google/Whatever-search-engine-you-use for instructions on that.
I'm also interested to install Magisk with as less impact as possible, so to summarize for newbies like myself:
* Unlocked bootloader is needed. Period.
* A custom recovery is needed to flash Magisk. TWRP for instance.
* That custom recovery prevent the built-in OTA update to work
* But TWRP can flash OTA updates that can be downloader from XDA for example
Am I correct?
Also,
* Magisk needs a patched boot image
* This image has no impact on the OTA process at all
* There are encryption matters to take care of (I don't understand them yet though).
Is everything correct?
Thanks.
Krystanos said:
I'm also interested to install Magisk with as less impact as possible, so to summarize for newbies like myself:
Click to expand...
Click to collapse
Let's see about answering those statements/questions.
* Unlocked bootloader is needed. Period.
Click to expand...
Click to collapse
Yes.
* A custom recovery is needed to flash Magisk. TWRP for instance.
Click to expand...
Click to collapse
Not necessarily. You can let the Magisk Manager patch your device's stock boot image and then flash it to your device with fastboot. See the installation instructions in the release thread.
* That custom recovery prevent the built-in OTA update to work
Click to expand...
Click to collapse
Yes.
* But TWRP can flash OTA updates that can be downloader from XDA for example
Click to expand...
Click to collapse
No. And yes. Official OTA files can (most of the time) not be flashed in TWRP. ROM zips and flashable firmware packages can.
* Magisk needs a patched boot image
Click to expand...
Click to collapse
Yes, that's all Magisk is about.
* This image has no impact on the OTA process at all
Click to expand...
Click to collapse
It definitely does. See the official docs
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips for more info on how to keep OTA capabilities for your device.
* There are encryption matters to take care of (I don't understand them yet though).
Click to expand...
Click to collapse
Possibly. Depends on what you're talking about.
Great answers. It's more clear for me now. Many thanks sir!
JRapsky said:
Hi,
I used Magisc with several chinese brand phones and never had problems so far.
Now I got a new Moto Z, and I don't want to unlock the bootloader and install a custom recovery.
Is there another way to get Magisc working on my new device?
I understand the concept of systemless root and modification in general. The bootloader unlock and custom recovery installation do not fit in this concept, don't you think so?
Kind regards
Gesendet von meinem XT1650 mit Tapatalk
Click to expand...
Click to collapse
Hi!
There are good news for you, rooting with magisk is very easy that way . No bootloader unlocking, custom recovery,
adb and fastboot command, no sdk no mtk tool . NOTHING but Sp flashtool - our best friend. This method really works with mtk phones android 5.0+ .
What U only need is
Sp flashtool and its drivers /scatter file with the ROM/ -I think not mtk devices with their own flashtool will work too
the ROM of your device
Magisc manager app on the phone
First of all you need clear up the device / after backup somewhere if needed/with sp flashtool - flash the whole ROM in format+download mode.
Install Magisc manager app , it will load for U a zip file in the map of the app
Put the boot img file of your rom in that map too
Run install option - it will create a patched boot img file within the app s map
Run again sp flashtool with download mode , mark only the boot section , and flash that patched boot img in phone
After reboot phone it is rooted
best regards
Forgive me and explain me something:
I read that "no custom recovery needed" and through the application it will create a patched boot img file.
I installed Magisk Manager 5.4.3, οpens and displays "not installed". I followed the steps that are described in the guide without anything being done.
One of the users they created patched recovery from the application menu in what order did they do it?
@Galaxtracker: you write "it will load for U a zip file in the map of the app" Where is the map of application ; I do not see any folder created ιn Android/Data or or somewhere else.
I have the Ulefone S8Pro with unlock bootloader (Android 7)
lefteriskmail said:
Forgive me and explain me something:
I read that "no custom recovery needed" and through the application it will create a patched boot img file.
I installed Magisk Manager 5.4.3, οpens and displays "not installed". I followed the steps that are described in the guide without anything being done.
One of the users they created patched recovery from the application menu in what order did they do it?
@Galaxtracker: you write "it will load for U a zip file in the map of the app" Where is the map of application ; I do not see any folder created ιn Android/Data or or somewhere else.
I have the Ulefone S8Pro with unlock bootloader (Android 7)
Click to expand...
Click to collapse
Install Magisk Manager.
Press install.
Select "Patch Boot Image File".
Select the stock boot image you've previously saved on your device.
Wait.
Flash the patched boot image to your device.
Done.
All of this is covered in the installation instructions...
The folder being mentioned above is MagiskManager on your internal storage (where the patched boot image is also stored).
Magisc
Hi!
Magisc works fine for me from the first time. Excuse me I won't do installation again to see how it goes. Really it causes some hesitation but in the end it's clear.
I use Total commander, and magisc folder is on the external SD card after installing magisc manager app. Factory reset later will not clear the root. After installing manager it says "not installed" till the end of the rooting process. Opening the app it begins to look after the downloadable zip file, you have to wait and download it. This zip and the stock boot img must be in the same place in a folder, and the app itself makes the patched boot img but I don't remember what was the name of the option. This is the flashable img file. In the end after flashing with flashtool and rebooting, magisc manager says "installed". Good luck
Hi, I am trying to centralise this sort of information and am compiling it in another topic for Magisk and android-based media centres too.
Trying to properly document things (full sentences with references, links, and examples) rather than just writing some brief summarised steps that most people will not understand - not just for myself but to share should it assist others learn and understand the preparation and steps involved, plus consequences and ramifications of their actions (which never seem to be stressed enough).
Here is what I have compiled. Hopefully it will help and prevent you going loopy!? :silly:
- - - - - - - - - - - - - - - - - - - -
*** EXTREMELY CLEAR MAGISK ROOT INSTRUCTIONS ***
(Work In Progress! To Be Verified & Critiqued By Others)
Connect your WiFi so that all auxillary files can be downloaded during the rooting process.
Ensure you have a minimum of 2GB of free disk space. Allow for 1-2 hours to perform these steps. Do not rush!
Bootloaders come with every Android device, and give it all the instructions on how to boot and what to execute. If your Bootloader is locked, then you have not flashed anything like TWRP previously, or, you have re-flashed a stock Bootloader and Recovery, etc. The process is much easier when you have previously rooted the device using another method, and the Bootloader already unlocked.
To preserve your System partition, Magisk only modifies the unlocked Bootloader boot partition, which can easily* be restored and 'locked' later.
0. Before starting anything, always perform a FULL Backup (ADB) of your device, using a good quality USB cable and ADB FastBoot toolkit. Or on some devices you can use a Micro SD card with a TWRP recovery.img to boot into TWRP to perform a backup of partitions. Do both if you want! Make sure you search for the appropriate commands and usage of ADB FastBoot backup so that all data is backed up and included.
> ADB FastBoot: https://developer.android.com/studio/releases/platform-tools.html
> TWRP: https://dl.twrp.me/twrpapp/ \\ https://twrp.me/FAQ/
> Plus various other solutions...
1. Identify your device's firmware, build number, Bootloader, full unique model number, etc. Download any two of these apps:
a) AIDA64 ("System", "CPU" & "Android" tabs.)
b) Device Info HW ("General" & "System" tabs.)
c) DevCheck ("Hardware" & "System" tabs.)
2. Download the stock Bootloader, Recovery and Firmware (___.tar.md5) for your device model, variant and OS. (e.g. match your firmware, build number, bootloader, full unique module number, etc). Some sites will force you to pay to download - search around and you can get free download links, or sometimes from the manufacturer's site. From this firmware, we need to either extract or download the stock Bootloader.img image separately.
3. Install Magisk Manager v5.3-v5.6 as of 2017.02.22 ("Magisc" is typo by guy above).
4. Open Magisk and go to settings, adjust theme, change the language, enable notify for updates, change prompt timeout, etc.
5. On the home screen of the Magisk Manager app, click "Install" then in the pop-up select "Install" again.
a) If you have root access already, choose "Direct Method" - Select, wait, reboot and done (very easy!);
b) If you have stock recovery & locked bootloader, choose "Patch Boot Image File" - in the pop-up explorer, browse for the downloaded Bootloader Image.
c) ... I don't know about "Download ZIP Only" - I assume for flashing with Odin or ADB FastBoot from PC or existing root/unlocked user....?
NOTE: If you are being asked to browse and select a file, be aware that there is no confirmation! As soon as you click, that JPG or RAR archive will be used for patching (and result in an error if cannot be extracted!!!)
6. A file will likely be downloaded in the background (flashable ZIP), a black screen will pop-up processing etc. Wait.....
The processed Boot image will be processed and output to the /MagiskManager/ directory.
If you do NOT have root, or custom recovery, you will need to:
a) grab a PC, install the USB drivers for your device and confirm your device is fully recognised
b) then flash the "patched" Boot image from the Magisk Manager directory with ODIN for Windows or FastBoot on Windows via a good-quality USB cable.
7. ...
8. ...
I think that is it... I may have forgotten something. Please advise if something needs to be fixed or corrected. My Media Centre was already unlocked, so I did not have to unlock and flash the Bootloader.
9. Install free TWRP on your device, and choose to backup any partitions, should you wish to restore them later. Set an alarm to backup your device every few months! What are you prepared to lose if your device was lost/squashed/washed/crunched et al.???
Say thank you and donate to the amazing and all powerful Magisk developer 'TopJohnWu' and team!
Sweet! :fingers-crossed:
How to root any version of the OnePlus 7T Pro!
1. Make sure your bootloader is unlocked!
2. Once you're unlocked enter the following ADB commands to extract your current boot image (Your phone needs to be on)
adb shell dd if=/dev/block/bootdevice/by-name/boot_a of=/boot_a.img
adb pull /boot_a.img pathinyourpc
Click to expand...
Click to collapse
3. Download & install Magisk Manager on your phone
4. Put the boot_a.img file on your phone
5. Open the magisk manager app and click the "Advanced Settings" button, then enable "Prserve AVB 2.0/dm-verity & Preserve force encryption", then select the top "Install" button and select "Patch to boot image" and select the boot_a.img
6. Now magisk will create a magisk patched boot image file, put that on your computer
7. Now enter the following ADB command
adb reboot fastboot
fastboot --set-active=a
fastboot boot pathtomagiskpatched.img
Click to expand...
Click to collapse
8. Now you'll boot into the system, reopen the magisk app and click the top install button again and select "Direct install", then reboot
Congratulations you've now successfully rooted your phone!
EDIT: This guide is wrong.
Check these references for the proper guide to root. OP refuses to acknowledge it's wrong even when I pointed it out to him with proof.
https://forum.xda-developers.com/showpost.php?p=81023631&postcount=144
^^^
Mainly this one.
https://forum.xda-developers.com/showpost.php?p=81105485&postcount=171
https://forum.xda-developers.com/showpost.php?p=81106827&postcount=173
-----
Now I have something so do for the weekend, thanks
Just a question, have you tried Viper4Android (if your use it)?: Use 2.7.1.6 stable version.
hi,
tryed it out.. When i boot your patched image.. there is no install button in magisk. It tolds me that i am already on the newest version.
Second.. WLAN isnt working any more. Cant enable wlan. When i reboot with stock img. everything is fine.
Dukynuky said:
hi,
tryed it out.. When i boot your patched image.. there is no install button in magisk. It tolds me that i am already on the newest version.
Second.. WLAN isnt working any more. Cant enable wlan. When i reboot with stock img. everything is fine.
Click to expand...
Click to collapse
Yes it says its installed thats correct but you need to install it again in the magisk app so it stays after restarting the phone. I don't know about WLAN tho
Can you turn on Wifi ?
When i turn it on. It is disabled at the end.
There are similar problems in the 7t forums. Seems a problem with the used magisk version for the boot image.. did you use the canary magisk files ?
and yes.. I know why i need to install. But the linked version of magisk says only.. uninstall..
Edit: i have a european version of the oneplus 7t pro .. and can you provide the original boot image.
I can confirm I have successfully rooted using this method, and WIFI is working fine. Thank you very much, OP and everyone involved, no wits time to set up my device
Ah! Will do this immediately when I get home.
I tried magisk and now it loops to fastboot, does anyone know to recover from this? Does the msm tool for OP7T Pro?
edit: flashed the original boot img and boots fine, whever i try to boot magisk patched it bootlops because faulty drivers
to clear up, i tried installing viper4android driver directly from the app, so i guess theres residue left
Lossyx said:
I tried magisk and now it loops to fastboot, does anyone know to recover from this? Does the msm tool for OP7T Pro?
Click to expand...
Click to collapse
did you install modules ? try booting the patched boot image from here and then, uninstall the modules again...
Works like a charm!
Minor thing you may want to clarify (I know you know, but to prevent confusion for readers), you give a warning that this will wipe all data, but that is not exactly true. Unlocking the bootloader wipes all data, but that step is not part of your instructions. Just following your steps on an already unlocked phone does not wipe the phone.
Thanks to everyone who made this possible so soon!
Dukynuky said:
did you install modules ? try booting the patched boot image from here and then, uninstall the modules again...
Click to expand...
Click to collapse
please see my edited reply, i installed directry through viper4android app, no the module
Dukynuky said:
Can you turn on Wifi ?
When i turn it on. It is disabled at the end.
There are similar problems in the 7t forums. Seems a problem with the used magisk version for the boot image.. did you use the canary magisk files ?
and yes.. I know why i need to install. But the linked version of magisk says only.. uninstall..
Edit: i have a european version of the oneplus 7t pro .. and can you provide the original boot image.
Click to expand...
Click to collapse
got ist working.. layer 8 error.. didnt had the ota update installed.
Updated oxygen os.. then wifi is working. also used canary magisk files.. works perfekt.. thanks
Dukynuky said:
Can you turn on Wifi ?
When i turn it on. It is disabled at the end.
There are similar problems in the 7t forums. Seems a problem with the used magisk version for the boot image.. did you use the canary magisk files ?
and yes.. I know why i need to install. But the linked version of magisk says only.. uninstall..
Edit: i have a european version of the oneplus 7t pro .. and can you provide the original boot image.
Click to expand...
Click to collapse
my wifi works perfectly fine, I have the EU version too.
I attached screenshots of what to do with the installed, please select the direct install option and then reboot!
droidvark said:
Works like a charm!
Minor thing you may want to clarify (I know you know, but to prevent confusion for readers), you give a warning that this will wipe all data, but that is not exactly true. Unlocking the bootloader wipes all data, but that step is not part of your instructions. Just following your steps on an already unlocked phone does not wipe the phone.
Thanks to everyone who made this possible so soon!
Click to expand...
Click to collapse
I have a warning above the instructions already, I think you might have missed it
Lossyx said:
I tried magisk and now it loops to fastboot, does anyone know to recover from this? Does the msm tool for OP7T Pro?
edit: flashed the original boot img and boots fine, whever i try to boot magisk patched it bootlops because faulty drivers
to clear up, i tried installing viper4android driver directly from the app, so i guess theres residue left
Click to expand...
Click to collapse
I also bootlooped as well, I tried to install liveboot and i guess that didnt work lol
anyways, I fixed my bootloop by booting the unpatched boot img and then doing a factory reset in the settings, after that you can just boot to the magisk boot img again!
Lossyx said:
please see my edited reply, i installed directry through viper4android app, no the module
Click to expand...
Click to collapse
Use the module next time!
HolyChickenGuy said:
I have a warning above the instructions already, I think you might have missed it
Click to expand...
Click to collapse
I'm not sure where the misunderstanding is coming from, I know that you give that warning. What I mean is that strictly speaking following your steps does not wipe the phone, unlocking the bootloader wipes the phone. But you don't have that step in your instructions. See what I mean? .
When I read your steps, I was like "wipes my phone how?" Maybe booting your image would wipe my phone or something? I'm glad it didn't .
I just thought for clarity's sake it would be good to make that clear in the steps that's all!
droidvark said:
I'm not sure where the misunderstanding is coming from, I know that you give that warning. What I mean is that strictly speaking following your steps does not wipe the phone, unlocking the bootloader wipes the phone. But you don't have that step in your instructions. See what I mean? .
When I read your steps, I was like "wipes my phone how?" Maybe booting your image would wipe my phone or something? I'm glad it didn't .
I just thought for clarity's sake it would be good to make that clear in the steps that's all!
Click to expand...
Click to collapse
Oh sorry, yeah I rewrote it to make it clearer. Unlocking the bootloader will wipe your data
Sent from my HD1913 using Tapatalk
HolyChickenGuy said:
I also bootlooped as well, I tried to install liveboot and i guess that didnt work lol
anyways, I fixed my bootloop by booting the unpatched boot img and then doing a factory reset in the settings, after that you can just boot to the magisk boot img again!
Click to expand...
Click to collapse
Damn, you are my hero. Did a factory reset and followed the OP again, now everything is fine and I'm rooted. Thank you again.
edit: also, for safety precaution, disable automatic updates in Developer options
https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation
Great, I'll check back in on this tomorrow and see how everyone is getting on before I try. Had a skim through here this morning before mine arrived and didn't see anything so set up as is.
[TWRP] MI 11 (Pro/Ultra) (mars/star)
WARNING : I do not know who made this TWRP and I am NOT taking credit for it. It was posted on eu site and I'm just sharing since there was no thread for twrp here on xda.
INSTRUCTIONS
1. Before starting the process, the bootloader must be unlocked.
2. Install Xiaomi USB drivers.
3. Enable Usb debugging from Settings - Additional settings - developer options.
4. Download TWRP for Mi 11 (Pro/Ultra) , and put it in your fastboot folder.
5. Put your phone into fastboot mode.
6. Rename downloaded file to "twrp.img".
7. Do the following command. It will automatically boot into TWRP.
Code:
fastboot boot twrp.img
8. If you get a screen asking for a pin, press 2nd option
and change language to English then enter phone pin.
9. Change language to English (press the 6th option).
10. Go to "Advanced" and select "Onekey inject TWRP".
11. Swipe to inject the TWRP. It might take a few minutes, so don't worry.
Note
1) Don't change the boot slot, currently (Slot A) for most or your device will not boot at all.
2) For user experiencing decrypt issue, you can try one of the methods below to enable decryption:
a. Remove all your security eg. fingerprint, face unlock, pattern and leave ONLY pin. Reboot to twrp and try again.
b. Reflash twrp.
c. LAST RESORT! Format data and factory reset your device then reflash twrp.
3. For user experiencing decrypt issue but just want to flash latest build:
a. Boot to twrp > mount > mount usb storage then transfer your rom.zip to data/media/0
b. Now go to install and look for rom.zip under data/media/0. Profit!
4. The decrypt issue was a bug on the Chinese twrp, no update since may so don't ask for an ETA.
CHANGELOGS
07/18/21
1) Additional instruction from scratch.
2) Additional note for people having decrypt issue.
CTTO: xiaomi.eu, hoangsang
Is the legit TWRP ?? Xiaomi.EU getting ready to push updates via TWRP? :'D
skylerfly16 said:
Is the legit TWRP ?? Xiaomi.EU getting ready to push updates via TWRP? :'D
Click to expand...
Click to collapse
Yes, They just did the new stable in TWRP Format.
The Chinese exe worked for me this morning but after I installed it the phone didn't want to boot and I got stuck in twrp for awhile
speedtripler said:
The Chinese exe worked for me this morning but after I installed it the phone didn't want to boot and I got stuck in twrp for awhile
Click to expand...
Click to collapse
Why did you install the Chinese exe?
skylerfly16 said:
Why did you install the Chinese exe?
Click to expand...
Click to collapse
The official one hadn't been released yet and I like a challenge sometimes
Hey, thx for bringing this to my attention, but i checked... root-access is gone... :/
deleted post
I keep getting a " no such partician " fail msg , what am I doing wrong here?
speedtripler said:
I keep getting a " no such partician " fail msg , what am I doing wrong here?
Click to expand...
Click to collapse
Your device is not connected, hence the empty list after adb devices.
Did you enable USB debugging in Developer options?
heinhuiz said:
Your device is not connected, hence the empty list after adb devices.
Did you enable USB debugging in Developer options?
Click to expand...
Click to collapse
Thx It's ok,I got it after a few attempts
The language on twrp still opens on Chinese and it needs changed to English each time but apart from that it seems to work fine!
SanHelios said:
Hey, thx for bringing this to my attention, but i checked... root-access is gone... :/
Click to expand...
Click to collapse
mine was revoked after i flash the latest stable, just download magisk23.apk then rename it to magisk23.zip and flash thru twrp, got my root back that way, cheers
innocence07 said:
mine was revoked after i flash the latest stable, just download magisk23.apk then rename it to magisk23.zip and flash thru twrp, got my root back that way, cheers
Click to expand...
Click to collapse
Is banking and payment apps still working?
Can you still pass safetynet check?
speedtripler said:
Is banking and payment apps still working?
Can you still pass safetynet check?
Click to expand...
Click to collapse
Yes and yes
Thanks, it works for me.
But each time i boot on TWRP, go back to chinesse language.
Can we do backup ? (and what can we backup) in case of something wrong in the future
sabrewulf said:
Thanks, it works for me.
But each time i boot on TWRP, go back to chinesse language.
Can we do backup ? (and what can we backup) in case of something wrong in the future
Click to expand...
Click to collapse
The recovery is fully functional as far as I can tell...
I did a complete backup successfully but I haven't tried to restore it yet
You click on everything ?
Hi,
after a long day of learning the hard way (got stuck in Fastboot Loop) I am now on stable EU 12.5.7 (MI11 Ultra, EU phone). So far so good, but I was wondering, how can I make TWRP stuck to the phone, meaning, when I push the power button to have an option like: Boot into TWRP. Is that possible or is there a "click this button with this... trick"?
ATM, I can only get TWRP to work, when I enable it via PC, which is not good.
I am asking, because I have an old Oneplus 6, which has this option. TWRP is installed and I can boot directly to it, if I want to.
Can you please help me out? Is there a trick or am I doing something wrong?
Greetings from Germany
Placebo
I believe you are on custom EU rom right? Just reboot into recovery, custom eu rom injects twrp as standard recovery
Hi, yes I am and I did that also. But still can't boot into TWRP from within the phone. Is there a trick after the injection?