I have a T-Mobile LG G5, H830.
Current system is unlocked bootloader, TWRP installed, Rooted with Super SU.
Android version H83020F
Kernal 3.18.31-As hard_v4.1
How do I switch/ install to Magisk? So I can use Android pay?
The guides I found are for unrooted devices and wheren't specific to LG G5 H830 so I wanted to ask here before I try something.
buyslake said:
I have a T-Mobile LG G5, H830.
Current system is unlocked bootloader, TWRP installed, Rooted with Super SU.
Android version H83020F
Kernal 3.18.31-As hard_v4.1
How do I switch/ install to Magisk? So I can use Android pay?
The guides I found are for unrooted devices and wheren't specific to LG G5 H830 so I wanted to ask here before I try something.
Click to expand...
Click to collapse
Go into TWRP, reinstall Asgard kernel (may not be necessary but doesn't hurt) and then flash magisk v12. Reboot into system and open up SuperSU app and go into settings and click on full unroot and restart. In magisk manager make sure you enable magisk hide and don't use built in busy box (using magisk hide and built in BusyBox causes issues with root not showing up).
jeffsga88 said:
Go into TWRP, reinstall Asgard kernel (may not be necessary but doesn't hurt) and then flash magisk v12. Reboot into system and open up SuperSU app and go into settings and click on full unroot and restart. In r showing up).
Click to expand...
Click to collapse
I did what you said and it did not go well.
After many attempts, I was finally able to remove SuperSu and install Magisk and it said it was rooted.
Some how I lost all of my apps, settings, etc.
Then I went into settings and selected the option to restore to factory settings so I could get it to ask me to restore my apps from my Gmail account when it would reboot after factory reset.
HOWEVER, now it only reboots into TWRP recovery.
So I tried reinstalling Magisk and it still only boys into recovery. I tried reinstalling the kernel and it still only reboots into recovery. Then I tried installing the rom, the kernel, and Magisk and it still only boys into recovery.
Why won't it boot? In the TWRP advanced wipe... What options ships be selected to wipe before reinstalling the rom?
buyslake said:
I did what you said and it did not go well.
After many attempts, I was finally able to remove SuperSu and install Magisk and it said it was rooted.
Some how I lost all of my apps, settings, etc.
Then I went into settings and selected the option to restore to factory settings so I could get it to ask me to restore my apps from my Gmail account when it would reboot after factory reset.
HOWEVER, now it only reboots into TWRP recovery.
So I tried reinstalling Magisk and it still only boys into recovery. I tried reinstalling the kernel and it still only reboots into recovery. Then I tried installing the rom, the kernel, and Magisk and it still only boys into recovery.
Why won't it boot? In the TWRP advanced wipe... What options ships be selected to wipe before reinstalling the rom?
Click to expand...
Click to collapse
First of all, flashing magisk wouldn't make you lose any settings so not sure exactly what happened there. Secondly, never use factory reset option from phone when you have TWRP installed. Now to get out of TWRP bootloop go into TWRP, click advanced and then terminal and type the following:
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=256 count=1 conv=notrunc
Then reboot into system.
jeffsga88 said:
First of all, flashing magisk wouldn't make you lose any settings so not sure exactly what happened there. Secondly, never use factory reset option from phone when you have TWRP installed. Now to get out of TWRP bootloop go into TWRP, click advanced and then terminal and type the following:
Then reboot into system.
Click to expand...
Click to collapse
Thank you for giving me that terminal code. I am now rebooted and phone is working fine.
Help for install magisk
Can u give me step by step how to install magisk? My position on h830a, rooted, UBL, twrp.
i have xposed, busybox, gltools,
Can i directly flash magisk via twrp or flash asgard first?
Because i can't found asgard yet for H830
Thanks before
Related
Hello guys, so previously I was on nameless rom 4.4, and i wanted to change my recovery from cwm recovery to twrp recovery. So I used this app from the playstore to do it TWRP Manager app. Anyways this app seemed pretty buggy to me, and it was requesting me to install busybox, so i just followed the instructions. Anyways, after it had finished installing twrp, I wanted to test it out. So, when i tried to reboot in recovery, the phone is now stuck on the samsung logo. Cant even boot normally. What should i do now?
lopiop said:
Hello guys, so previously I was on nameless rom 4.4, and i wanted to change my recovery from cwm recovery to twrp recovery. So I used this app from the playstore to do it TWRP Manager app. Anyways this app seemed pretty buggy to me, and it was requesting me to install busybox, so i just followed the instructions. Anyways, after it had finished installing twrp, I wanted to test it out. So, when i tried to reboot in recovery, the phone is now stuck on the samsung logo. Cant even boot normally. What should i do now?
Click to expand...
Click to collapse
Try and reboot into recovery holding up power and home keys then wait galaxy s3 to be displayed then the phone should boot into recovery. From there do a wipe data factory reset, wipe cache and wipe dalvik cache. I would recommended using the latest Clockworkmod recovery as it seems reliable. You can install it using Rom Manager from Play Store, as long as you have root follow the necessary instructions to flash the recovery.
tail.adam said:
Try and reboot into recovery holding up power and home keys then wait galaxy s3 to be displayed then the phone should boot into recovery. From there do a wipe data factory reset, wipe cache and wipe dalvik cache. I would recommended using the latest Clockworkmod recovery as it seems reliable. You can install it using Rom Manager from Play Store, as long as you have root follow the necessary instructions to flash the recovery.
Click to expand...
Click to collapse
i tried to manually reboot into recovery, but it wont enter.
can you use adb sideload if you cannot enter recovery?
lopiop said:
i tried to manually reboot into recovery, but it wont enter.
Click to expand...
Click to collapse
You may need to flash back to stock using Odin then re rooting again.
so i should flash the latest stock rom (4.3) for my region using odin? like this guide http://forum.xda-developers.com/galaxy-s3/general/restore-to-stock-rom-galaxy-s3-i9300-t2187081
fixed using odin, though rather sad that my internal sd got wiped as well
lopiop said:
fixed using odin, though rather sad that my internal sd got wiped as well
Click to expand...
Click to collapse
Glad it's fixed I would recommend not to use apps from playstore to flash recoveries or roms seen nothing but trouble from them.Either use Odin or custom recovery to flash to avoid trouble in the future.
Hi Everyone,
I just followed the instruction and unlocked my bootloader.
I am in marshmallow and then used twrp to flash supersu 2.64.
When i was flashing to root twrp asked me about the partition change which i dont understand so swiped it and now i cant get past the htc one bootscreen. I have tried factory reset and wipe dalvik cache.
What do i do?
kisshell99 said:
Hi Everyone,
I just followed the instruction and unlocked my bootloader.
I am in marshmallow and then used twrp to flash supersu 2.64.
When i was flashing to root twrp asked me about the partition change which i dont understand so swiped it and now i cant get past the htc one bootscreen. I have tried factory reset and wipe dalvik cache.
What do i do?
Click to expand...
Click to collapse
Go back and change partition to read and write in twrp (I think), sounds like you set it to read only if you are getting stuck at that screen. If all else fails I'd try running the RUU then re flashing twrp , but are you s off? I've been s off since sunshine came out (which I highly recommend) and don't know how things work being s-on. Also which version of twrp are you using?
Go read up about how twrp works , that way when you are prompted with things that could prevent you from obtaining root you will know what to do. #4 in the link below might be able to help you... but once again read all the information provided.
http://forum.xda-developers.com/showpost.php?p=59745198&postcount=3
you need to update your TWRP to 3.0.0. Flash it through CMD or sdcard way, reboot to recovery, "Mount as Read Only" message swipe to right. You want it to be that way for an untouch system backup(if you wanted to do). Reflash MM ROM.
got it
The problem was twrp was asking to flash the supersu from itself even after i had flashed the su manually from twrp. i just installed badboyz and then flashed the su and did not accept the twrp option to flash supersu again and it is working again. To add more, i think i even got it dsu with the recent guide posted here which saved me few bucks. I love xda!
Hi,
I'm using CM13 on my LG d620, recently I tried installing SuperSu, and then updating binary, but normal way did not worked so I tried to install it with TWRP recovery, so my phone rebooted into recovery, supersu script automatically stared and installation was successfull. I wiped cahce, even dalvik just to be sure, and rebooted system, but it is now stuck in bootloop.
So I'm just curious if anyone would know if I can somehow fix this problem, maybe through recovery, flashing some script, or in terminal in recovery, with adb... pretty much anything just to avoid flashing new rom again and losing all of data and setings....
Thanks in advance
(btw, i'm on cm13 6.0.1, latest update to this day, twrp 3.0.0, supersu latest version on google play store i think, and also have enabled root access)
Enigma. said:
Hi,
I'm using CM13 on my LG d620, recently I tried installing SuperSu, and then updating binary, but normal way did not worked so I tried to install it with TWRP recovery, so my phone rebooted into recovery, supersu script automatically stared and installation was successfull. I wiped cahce, even dalvik just to be sure, and rebooted system, but it is now stuck in bootloop.
So I'm just curious if anyone would know if I can somehow fix this problem, maybe through recovery, flashing some script, or in terminal in recovery, with adb... pretty much anything just to avoid flashing new rom again and losing all of data and setings....
Thanks in advance
(btw, i'm on cm13 6.0.1, latest update to this day, twrp 3.0.0, supersu latest version on google play store i think, and also have enabled root access)
Click to expand...
Click to collapse
I end up with same issue now. I could have read this before flashing SuperSu. Now my device is in boot loop. Please help how to fix this without wiping data?
Rasgola said:
I end up with same issue now. I could have read this before flashing SuperSu. Now my device is in boot loop. Please help how to fix this without wiping data?
Click to expand...
Click to collapse
Just flash rom from the recovery, thats it. Let me know if it worked for you
So I was wondering...
Today once again I forgot to flash SuperSU after flashing new kernel and I'm left without root. While rooted I was using an app to restart into recovery and it was fine.
As we all know, when you boot into recovery on LG G5 by button combination, you're asked to to wipe everything. My question is, is there any method to boot into recovery without wiping? Without root?
resutatto said:
So I was wondering...
Today once again I forgot to flash SuperSU after flashing new kernel and I'm left without root. While rooted I was using an app to restart into recovery and it was fine.
As we all know, when you boot into recovery on LG G5 by button combination, you're asked to to wipe everything. My question is, is there any method to boot into recovery without wiping? Without root?
Click to expand...
Click to collapse
If you still actually have TWRP installed, pressing yes when it asks to factory reset / wipe (using the button combo) will not wipe anything, it will just boot into TWRP. Just be sure TWRP is actually installed still, as if TWRP is not installed, then it would wipe your phone saying yes. To check, you can always boot into phone and use
Code:
adb reboot recovery
I'm using TWRP 3.1.0.0, but as far as I remember it wipes anyway. It was on the older TWRP version though. And unfortunately adb command doesn't work for some reason, adb reboot bootloader works.
Anyway, worth trying, I have to do it anyway sooner or later. It would be nice if it wouldn't wipe my apps.
Same problem here. I ran into a bootloop and need to flash the Magisk uninstaller. How to boot into TWRP? With the key combination it always asks me to wipe my phone?!
SOLVED. Just select Yes. This is only a leftover of the Stock recovery. Nothing will be wiped if you already have TWRP installed.
Typical disclaimer, etc etc.
You nuke your phone, I'm not paying for it
Thanks to @zefie for converting the kdz to a zip.
The zip
The anti-root removal
I flashed the zip in TWRP, rebooted to the OS, and was unrooted.
Reboot into the bootloader, and flashed TWRP.
Rebooted into recovery, flashed the lucye anti root removal, then rebooted into recovery again, and flashed Magisk.
Phone has been fine since Thursday.
Did you flash this dirty or clean?
I flashed it. Works GREAT. Dirty flashed.
Here's what I did...
-Flashed this zip
-Flashed Eliminator74 twrp image https://forum.xda-developers.com/lg-g6/development/twrp-t3828254 (you'll need to change from .zip to .img in TWRP)
-Rebooted to recovery
-Flashed antiroot removal zip
-rebooted to recovery
-Flashed magisk
-rebooted to system
-be patient
Can you please post a link to eliminator74 twrp build? I'm not sure if I have that one...
Link to his thread
jjohn7293 said:
Can you please post a link to eliminator74 twrp build? I'm not sure if I have that one...
Click to expand...
Click to collapse
Here's a link to his thread https://forum.xda-developers.com/lg-g6/development/twrp-t3828254
monark88 said:
I flashed it. Works GREAT. Dirty flashed.
Here's what I did...
-Flashed this zip
-Flashed Eliminator74 twrp image https://forum.xda-developers.com/lg-g6/development/twrp-t3828254 (you'll need to change from .zip to .img in TWRP)
-Rebooted to recovery
-Flashed antiroot removal zip
-rebooted to recovery
-Flashed magisk
-rebooted to system
-be patient
Click to expand...
Click to collapse
Dirty from 21B worked fine for me
Dirty flash from 20A worked perfectly.
FYI: This ROM has the recovery image removed, so if you already have TWRP, flashing this won't remove TWRP. No need to reinstall TWRP.
I actually started having bad idle drain. Flashed LOS for now, will go back to stock soon. If anyone else notices idle drain, please do let us know.
Thank you!
Only wiped caches
Dirty flashed over 20A
Reboot to recovery
Flashed anti root removal tool
Reboot to recovery
Flashed Magisk 17.3
Wiped caches again
Reboot to system
Showed Android is updating screen
All is well so far!
Still running 17A [rooted]... think dirty flashing this will be alright? Been looking for a good time to update.
Coming from 20A, battery life has been about the same- maybe even a bit better. All's well.
MetalMan2 said:
Still running 17A [rooted]... think dirty flashing this will be alright? Been looking for a good time to update.
Click to expand...
Click to collapse
Go for it. Be sure to install Magisk for root. SuperSU (if you happen to be using it) doesn't work anymore.
gl;hf
BeardKing said:
Coming from 20A, battery life has been about the same- maybe even a bit better. All's well.
Go for it. Be sure to install Magisk for root. SuperSU (if you happen to be using it) doesn't work anymore.
gl;hf
Click to expand...
Click to collapse
Thanks for instilling confidence. It all seems to have worked out just fine. :good:
Time will tell how battery life and what-not compares to 17A.
MetalMan2 said:
Thanks for instilling confidence. It all seems to have worked out just fine. :good:
Time will tell how battery life and what-not compares to 17A.
Click to expand...
Click to collapse
Good to hear. :good:
US997 14a to 21c (Keeping Root)
I'm using the US997 still on 14a (rooted, TWRP installed) would I need to (CLEAN) flash up to 17a and then the 21c? After that flash the anti-root and flash an updated version of Magisk? (currently stuck on v16.4) Can't find my stock boot image to update. Only got the phone back in October and stopped all updates before I unlocked the bootloaded, installed TWRP and used Magisk to get root. I had a hard time finding a version of TWRP with a kernel that worked for my phone (Melina v3.2.1-0) would I have to update that also? Was waiting to see the highest update I could get without losing root. Anyone done this? Any help would be greatly appreciated.
My wife and I both have G6 phones. On mine, I dirty flashed this over 20A with absolutely no problem. My sequence was: flash Eliminator74 TWRP, reboot to recovery, flash 21C zip, reboot to recovery, flash lucye anti-root, reboot to recovery, flash Magisk, wipe cache and Dalvik, reboot to system. I'm guessing I really didn't need those extra reboots but it felt safer. Phone is perfectly stable.
On my wife's phone it was another matter. Her data partition was encrypted, due to the phone having been reimaged by LG during warranty repair. I'd rooted it but never decrypted it. None of the default ways to decrypt it worked, so I was forced to format /data. I thought that would do it, but the resulting installation was unstable, and wouldn't get through setup successfully without continually looping, freezing, and returning to start. Finally I realized it was probably flashing over the LG factory image that caused the problem. I wiped /system and started over, and had much better results.
LPMatt said:
Thank you!
Only wiped caches
Dirty flashed over 20A
Reboot to recovery
Flashed anti root removal tool
Reboot to recovery
Flashed Magisk 17.3
Wiped caches again
Reboot to system
Showed Android is updating screen
All is well so far!
Click to expand...
Click to collapse
MetalMan2 said:
Thanks for instilling confidence. It all seems to have worked out just fine. :good:
Time will tell how battery life and what-not compares to 17A.
Click to expand...
Click to collapse
So I tried this coming from 17A.
When I reboot to recovery on the first go I have the Oreo bootloader screen and it goes into the white reset menu. All encryption is enabled again.
I have to fastboot bootloader, install TWRP recovery, wipe/format and then restore my 17A to recover the phone.
What steps did you take MetalMan2?
Malezar said:
So I tried this coming from 17A.
When I reboot to recovery on the first go I have the Oreo bootloader screen and it goes into the white reset menu. All encryption is enabled again.
I have to fastboot bootloader, install TWRP recovery, wipe/format and then restore my 17A to recover the phone.
What steps did you take MetalMan2?
Click to expand...
Click to collapse
This probably won't help, but are you using this version of TWRP?
BeardKing said:
This probably won't help, but are you using this version of TWRP?
Click to expand...
Click to collapse
Yep. Just downgraded the bootloader back to 17a through it.
Malezar said:
What steps did you take MetalMan2?
Click to expand...
Click to collapse
I exactly followed LPMatt's list which you quoted.
Still no problems. Pretty sure the battery life is less than 17A, but I think we all know that and for me it's "good enough".
How to remove root checker?