Lost root after upgrading - P8lite Q&A, Help & Troubleshooting

Hey I just updated my phone through twrp and I lost root access & custom recovery. Could someone tell me how I can root my phone now again? Info of my phone is below in the pic
P.S: I used KingRoot before and it worked. But not anymore.

RautMike said:
Hey I just updated my phone through twrp and I lost root access & custom recovery. Could someone tell me how I can root my phone now again? Info of my phone is below in the pic
P.S: I used KingRoot before and it worked. But not anymore.
Click to expand...
Click to collapse
Flash magisk 13

​
RautMike said:
Hey I just updated my phone through twrp and I lost root access & custom recovery. Could someone tell me how I can root my phone now again? Info of my phone is below in the pic
P.S: I used KingRoot before and it worked. But not anymore.
Click to expand...
Click to collapse
Of course you lost root and TWRP because a update.zip contains also recovery and other things(vendor, custom, etc.) and by flashing it the stock recovery will overwrite your TWRP and the new system will delete your root access.
And NEVER install KingRoot on this device! It will mess a lot of things(SuperSU and Magisk work)
You will need to flash TWRP again in order to have root because both supersu and magisk need to be flashed through TWRP(because they are .zip files, at least a part of the root, you will need to install the magisk app to have full root)
SuperSU root just needs to be flashed, just magisk needs an app to be installed after .zip flash.

XTutorials said:
​Of course you lost root and TWRP because a update.zip contains also recovery and other things(vendor, custom, etc.) and by flashing it the stock recovery will overwrite your TWRP and the new system will delete your root access.
And NEVER install KingRoot on this device! It will mess a lot of things(SuperSU and Magisk work)
You will need to flash TWRP again in order to have root because both supersu and magisk need to be flashed through TWRP(because they are .zip files, at least a part of the root, you will need to install the magisk app to have full root)
SuperSU root just needs to be flashed, just magisk needs an app to be installed after .zip flash.
Click to expand...
Click to collapse
Ok, thank you very much. Ill just wait to come back home from my Vacation and then flash twrp

Related

(REQ)Samsung A700YD android 5.0.2 root

Hi everyone,
After my A700YD upgrade to android 5.0.2, I cannot find a feasible solution to root my phone. I have tried the CF root or TWRP recovery of other A700 model but my phone stuck at samsung logo after reboot. Could anyone help me to root my A700YD? Many thanks.
dropbox.com/s/vfcms69qfn0vziq/BL_A700YDZSU1BOL4.tar.md5?dl=0
dropbox.com/s/phmabycaq9d5dm0/recovery.img?dl=0
Could anyone help? You can find the BL and recovery in the above links. New users cannot post link, sorry
Anyone can help?
Install twrp then use supersu v2.65
ashyx said:
Install twrp then use supersu v2.65
Click to expand...
Click to collapse
I have tried some twrp recovery. It can enter the recovery successfully but it cannot boot normally. It stuck at samsung logo.
ashyx said:
Install twrp then use supersu v2.65
Click to expand...
Click to collapse
I've tried to dig more in it, and what I get is
1. The only way I succeed is by using KingRoot, and the method it's using is by exploiting and keeping a daemon background and the su file for calling the daemon. So that means after reboot, root is lost.
3. Replacing KingRoot with SuperSU's su file will lead to a bootloop, same as goes to installing zip by twrp.
4. In the bootloop, logcat shows that it is repeating a particular normal boot process
5. In the bootloop, using adb shell and typing "su" will not get into root, despite su is located in xbin.
6. Busybox functions normally.
Any ideas?
ProtoAES256 said:
3. Replacing KingRoot with SuperSU's su file will lead to a bootloop, same as goes to installing zip by twrp.
Click to expand...
Click to collapse
Incorrect, installing supersu version 2.6x> with twrp will patch the boot image to prevent bootloop on samsung devices.
ashyx said:
Incorrect, installing supersu version 2.6x> with twrp will patch the boot image to prevent bootloop on samsung devices.
Click to expand...
Click to collapse
Whether or not the patch applies, it will still stuck in bootloop.
Same thing occured on current BETA supersu
ProtoAES256 said:
Whether or not the patch applies, it will still stuck in bootloop.
Same thing occured on current BETA supersu
Click to expand...
Click to collapse
Hi, I'm very interesting to this discussion, because yesterday my a700yd update to lollipop, then I root it with king root, but many app eg. leandroind not function with kingroot, so I use kingroot remove script but i'm occurred in bootloop, so I reflash original kitkat firmware but the phone does'nt work correctly, so I reflash lollipop firmware and all work perfectly. Now I would ask you if there is a functionally root method for a700yd?
Ps:when I do a wipe data in recovery mode, I have an error: E:can't mount /preload.
pianman said:
Hi, I'm very interesting to this discussion, because yesterday my a700yd update to lollipop, then I root it with king root, but many app eg. leandroind not function with kingroot, so I use kingroot remove script but i'm occurred in bootloop, so I reflash original kitkat firmware but the phone does'nt work correctly, so I reflash lollipop firmware and all work perfectly. Now I would ask you if there is a functionally root method for a700yd?
Ps:when I do a wipe data in recovery mode, I have an error: E:can't mount /preload.
Click to expand...
Click to collapse
From my current experience, no. The sad thing is I'm not skilled enough to do it myself, and seemly there is no reason that skilled devs are willing to have a head in to this not-quite-popular device.
Btw, you need to format /system partition before you flash the kitkat(well, maybe it works maybe it don't, it's just my experience.)
ProtoAES256 said:
Whether or not the patch applies, it will still stuck in bootloop.
Same thing occured on current BETA supersu
Click to expand...
Click to collapse
Nope, it will only do that if you attempt to replace Kingroot with supersu.
If you apply supersu to a clean stock boot and system partition it shouldn't boot loop.
---------- Post added at 10:16 AM ---------- Previous post was at 10:11 AM ----------
pianman said:
Hi, I'm very interesting to this discussion, because yesterday my a700yd update to lollipop, then I root it with king root, but many app eg. leandroind not function with kingroot, so I use kingroot remove script but i'm occurred in bootloop, so I reflash original kitkat firmware but the phone does'nt work correctly, so I reflash lollipop firmware and all work perfectly. Now I would ask you if there is a functionally root method for a700yd?
Ps:when I do a wipe data in recovery mode, I have an error: E:can't mount /preload.
Click to expand...
Click to collapse
If you have twrp installed I will upload a modified version of SuperSU which will allow systemless root on 5.0.2.
This will patch the boot image and should prevent a bootloop.
ashyx said:
Nope, it will only do that if you attempt to replace Kingroot with supersu.
If you apply supersu to a clean stock boot and system partition it shouldn't boot loop.
Click to expand...
Click to collapse
Weird, I did format my /system, /data and /cache before pushing in stock rom and supersu...
Isn't it sufficient to remove KingRoot?
Edit:
Or did I just messed up something?
ProtoAES256 said:
Weird, I did format my /system, /data and /cache before pushing in stock rom and supersu...
Isn't it sufficient to remove KingRoot?
Edit:
Or did I just messed up something?
Click to expand...
Click to collapse
If you flashed the stock rom that should remove the Kingroot and Super su binaries.
Are you using a stock kernel?
Usually only 5.1.1 and 6.0> need a patched boot.img as Samsung don't use root protection on 5.0.2 firmware.
However never say never and Samsung may may now be using root prevention in the later 5.0.2 kernels.
This means that a patched boot image is required to circumvent Samsung's root prevention.
If you have the boot.img I can patch it manually.
ashyx said:
If you flashed the stock rom that should remove the Kingroot and Super su binaries.
Are you using a stock kernel?
Usually only 5.1.1 and 6.0> need a patched boot.img as Samsung don't use root protection on 5.0.2 firmware.
However never say never and Samsung may may now be using root prevention in the later 5.0.2 kernels.
This means that a patched boot image is required to circumvent Samsung's root prevention.
If you have the boot.img I can patch it manually.
Click to expand...
Click to collapse
here you go, extracted from A700YDZSU1BOL4_A700YDZZT1BOL4_A700YDZSU1BOL4_HOME.tar
https://mega.nz/#!14IE3YoA!mRAhQSJCgZ53r5teACeJGWMwrftIY0g0GvZM0LMX9Kg
Hi everyone!
I found this two files, they are recovery.img and supersu 2.46. I still haven't tested them, because recovery is in img format and it has only the Chinese language. If anyone can help me translate the recovery and convert it in tar.md5 format. I found this 2 files on a700yd chinese forum. Thanks!
Same device platform. So should be compatible.
http://forum.xda-developers.com/samsung-a-series/general/recovery-twrp-galaxy-a7-t3153369
ashyx said:
Same device platform. So should be compatible.
http://forum.xda-developers.com/samsung-a-series/general/recovery-twrp-galaxy-a7-t3153369
Click to expand...
Click to collapse
I wiped my phone again and tried it
Here's my procedure
Wipe everything excluding external storage
reboot to bootloader and odin in stock rom
reboot to bootloader again and odin in twrp
reboot to recovery
twrp pops up patch notification(agrees and applied)
install SuperSU 2.65(stable) via sideload
reboot into system
Bootloop. ):
What does not cause bootloop
Stock ROM
TWRP installed only with stock ROM
What causes bootloop
installing SuperSU just after TWRP install (via zip or sideload)
Other problems
installing SuperSU from TWRP built-in will cause a recovery loop(unable to get past recovery screen)
=========
the recovery works good! (a good news at least)
ProtoAES256 said:
I wiped my phone again and tried it
Here's my procedure
Wipe everything excluding external storage
reboot to bootloader and odin in stock rom
reboot to bootloader again and odin in twrp
reboot to recovery
twrp pops up patch notification(agrees and applied)
install SuperSU 2.65(stable) via sideload
reboot into system
Bootloop. ):
What does not cause bootloop
Stock ROM
TWRP installed only with stock ROM
What causes bootloop
installing SuperSU just after TWRP install (via zip or sideload)
Other problems
installing SuperSU from TWRP built-in will cause a recovery loop(unable to get past recovery screen)
=========
the recovery works good! (a good news at least)
Click to expand...
Click to collapse
Try the supersu version above.
ashyx said:
Try the supersu version above.
Click to expand...
Click to collapse
i just update myphone to new firmware. i see something new eg : About device > "android security patch level"
i have same prolem (myphone boot stuck after flash superuser.zip v2.62-2.72 via twrp). And i try reflash one old boot.img via odin then myphone boot up normally with superuser.
i think the new boot.img make myphone stuck.
Can you please help me patch the new boot.img !?
ps: i'm so sorry for my bad english
https://drive.google.com/folderview?id=0B7uFmNBw-G1QalBCZERkeUpjd0U&usp=sharing
Hi Guys!
I ask you if someone used cf-auto root on this device and it was able to root the phone? Thanks.
hkopenh17071 said:
Hi everyone,
After my A700YD upgrade to android 5.0.2, I cannot find a feasible solution to root my phone. I have tried the CF root or TWRP recovery of other A700 model but my phone stuck at samsung logo after reboot. Could anyone help me to root my A700YD? Many thanks.
dropbox.com/s/vfcms69qfn0vziq/BL_A700YDZSU1BOL4.tar.md5?dl=0
dropbox.com/s/phmabycaq9d5dm0/recovery.img?dl=0
Could anyone help? You can find the BL and recovery in the above links. New users cannot post link, sorry
Click to expand...
Click to collapse
http://forum.xda-developers.com/samsung-a-series/development/galaxy-series-cf-auto-root-t3280406

moto x pure stuck on motorola logo after installing superSU?

so i recently got the pixel, had the moto x for about a year and decided to see what was going on with the rooting scene with this device. turns out that someone came along and created a simple solution to rooting and installing twrp for this device. I was happy. TWRP works just fine. But upon flashing SuperSU and rebooting from that i'm now stuck on the M logo permanently it seems. Yes i can reboot back into recovery and fastboot mode. But i can't seem to get past the M logo and all i've done was flash TWRP and SuperSU any idea about what's going on?
You need to flash as systemless root. Recent versions of SuperSU installs it as system root by default on this phone for some reason.
The SuperSU zip from my thread does it: https://forum.xda-developers.com/mo...t/rom-marshmallow-6-0-september-2016-t3536120
Spasticdroid said:
You need to flash as systemless root. Recent versions of SuperSU installs it as system root by default on this phone for some reason.
The SuperSU zip from my thread does it: https://forum.xda-developers.com/mo...t/rom-marshmallow-6-0-september-2016-t3536120
Click to expand...
Click to collapse
awesome thanks!!!! <3 now i just need to find a rom to play around with :3
silvernirvash said:
awesome thanks!!!! <3 now i just need to find a rom to play around with :3
Click to expand...
Click to collapse
No offense, but why are you bothering to root if you are just going to flash a ROM?
Also, there is nothing wrong with the latest version of SuperSU, you just need to do a manual systemless flash by creating the file /data/.supersu with the contents "SYSTEMLESS=true" and it will work perfectly.
acejavelin said:
Also, there is nothing wrong with the latest version of SuperSU, you just need to do a manual systemless flash by creating the file /data/.supersu with the contents "SYSTEMLESS=true" and it will work perfectly.
Click to expand...
Click to collapse
That's exactly what my zip does. I've only put it together to make the process much simpler, and I love automating stuff when it's possible.
SuperSU inside is unmodified. Updater-script copies a file named "systemless" from the zip which has "SYSTEMLESS=true" in it to /data, renames it to ".supersu", then proceeds flashing SuperSU.
Hello all,
I need some help!I have a Moto X Pure Edition XT 1575 I just unlocked bootloader and then intalled TWRP 3.1.1 and then installed SuperSU 2.79 and now no Sim is detected. What did I do wrong?
Thanks!
Unroot & clean with supersu app. It should restore boot image.
/You can also restore boot, system, wipe data in twrp/
Reboot & check.
If ok try rooting with supersu 2.82 or magisk 14. @kaleend101

[Q] Successful rooted, but /system is read only?

Hi guys, I have successfully rooted using temporary TWRP + modded magisk method, but now I gain root and checked via Root checker. But the problem is most of the root functions don't work as /system is read-only. Any idea?
Ya i have an idea.. Happened to me as well. I tried almoat everything but system won't be accessible anywhere.. I followed the same tutorial and installed magisk 13.4.
The only solution i could find was flash the latest factory image, and root again using supersu. I used the AIO tool by ghpranav and have got my phone rooted with xposed working without any issues.
zazzy24 said:
Ya i have an idea.. Happened to me as well. I tried almoat everything but system won't be accessible anywhere.. I followed the same tutorial and installed magisk 13.4.
The only solution i could find was flash the latest factory image, and root again using supersu. I used the AIO tool by ghpranav and have got my phone rooted with xposed working without any issues.
Click to expand...
Click to collapse
I also fixed the issue. I flash the modified boot image and I am now gaining proper root access + Xposed. Get it working using Super SU, idk why Magisk keep failing thou. Was wanted to give Magisk a try, but it doesn't work properly on our device.
Cool:good:
Xposed isn't working with magisk? I was planning to install it
amithiel said:
Xposed isn't working with magisk? I was planning to install it
Click to expand...
Click to collapse
Only with SuperSU as I know.
Sent from my Mi A1 using Tapatalk
Guys, this is Magisk from Pixel. You can't expect that it is working. I wrote to MagiskDevs already, they are working on a own Version for Mi A1. Use for that time normal SuperSU (Xposed works normally )
how to??
soralz said:
I also fixed the issue. I flash the modified boot image and I am now gaining proper root access + Xposed. Get it working using Super SU, idk why Magisk keep failing thou. Was wanted to give Magisk a try, but it doesn't work properly on our device.
Click to expand...
Click to collapse
Hay how do you Fix the Read only Issue? can you please share the Modified Boot image and process for same, thanks
maxsan20 said:
Hay how do you Fix the Read only Issue? can you please share the Modified Boot image and process for same, thanks
Click to expand...
Click to collapse
https://desktop.firmware.mobi/device:1748
Just root with replacing the boot image then you are good to go.
soralz said:
https://desktop.firmware.mobi/device:1748
Just root with replacing the boot image then you are good to go.
Click to expand...
Click to collapse
Hi,
I have TWRP installed and unrooted, what I need to do please?
We7dy said:
Hi,
I have TWRP installed and unrooted, what I need to do please?
Click to expand...
Click to collapse
You need flash back stock boot image first, due to some limitations you can't have TWRP and SuperSU root at the same time. If you don't have the stock boot image. I suggest download the ROM from MIUI and then flash it. You can choose "flash_all_except_storage" option, this will keep your data.
http://en.miui.com/download-333.html
After flashing. Reboot back to fastboot and then:
Code:
fastboot oem unlock
After that just run root.bat from the cf-auto root folder you downloaded and wait for it to automatically reboot your phone. You should have root now, if you wish you can download SuperSU from the store.
soralz said:
You need flash back stock boot image first, due to some limitations you can't have TWRP and SuperSU root at the same time. If you don't have the stock boot image. I suggest download the ROM from MIUI and then flash it. You can choose "flash_all_except_storage" option, this will keep your data.
http://en.miui.com/download-333.html
After flashing. Reboot back to fastboot and then:
After that just run root.bat from the cf-auto root folder you downloaded and wait for it to automatically reboot your phone. You should have root now, if you wish you can download SuperSU from the store.
Click to expand...
Click to collapse
Ok, thanks. It's not possible to do that via TWRP? I don't have PC. Currently my bootloader is unlocked, I have TWRP and I'm unrooted.
We7dy said:
Ok, thanks. It's not possible to do that via TWRP? I don't have PC. Currently my bootloader is unlocked, I have TWRP and I'm unrooted.
Click to expand...
Click to collapse
I actually tried before, and I tell you the results:
Option 1 TWRP installed + Rooted with Magisk
= Pretty much useless as /system is read-only. Every root app doesn't function, unless it is system-less. But system-less modules nearly all doesn't work as the Magisk version too old. And this method won't trip safetynet
Option 2 no TWRP + Rooted with SuperSU (cf-root method) -- Currently using this state
= Got proper root access, Xposed works but will trip safetynet
Option 3 TWRP installed + Rooted with SuperSU (cf-root method)
= Don't try this, will cause your phone stuck in boot loop
soralz said:
I actually tried before, and I tell you the results:
Option 1 TWRP installed + Rooted with Magisk
= Pretty much useless as /system is read-only. Every root app doesn't function, unless it is system-less. But system-less modules nearly all doesn't work as the Magisk version too old. And this method won't trip safetynet
Option 2 no TWRP + Rooted with SuperSU (cf-root method) -- Currently using this state
= Got proper root access, Xposed works but will trip safetynet
Option 3 TWRP installed + Rooted with SuperSU (cf-root method)
= Don't try this, will cause your phone stuck in boot loop
Click to expand...
Click to collapse
So not possible via TWRP? Get root access and remove TWRP? I just need that... The root.
We7dy said:
So not possible via TWRP? Get root access and remove TWRP? I just need that... The root.
Click to expand...
Click to collapse
The best bet and possible trouble free is to first download the stock ROM from MIUI, reflash it and then root.
soralz said:
The best bet and possible trouble free is to first download the stock ROM from MIUI, reflash it and then root.
Click to expand...
Click to collapse
:/ Can't root with TWRP without system read only...
We7dy said:
:/ Can't root with TWRP without system read only...
Click to expand...
Click to collapse
It's possible to root without CF-Auto-Root? Why can't flash SuperSu directly with TWRP?
We7dy said:
It's possible to root without CF-Auto-Root? Why can't flash SuperSu directly with TWRP?
Click to expand...
Click to collapse
No, it will cause your phone stuck it boot loop if you try to flash the SuperSU zip directly from the official ChainFire site. I think probably is the AB partitioning problem or some sort (unsure). As I said you need to run CF-Auto root to get proper root access, otherwise flashing Magisk through TWRP will makes most of the root apps does not work properly unless it also uses system-less root function.
soralz said:
No, it will cause your phone stuck it boot loop if you try to flash the SuperSU zip directly from the official ChainFire site. I think probably is the AB partitioning problem or some sort (unsure). As I said you need to run CF-Auto root to get proper root access, otherwise flashing Magisk through TWRP will makes most of the root apps does not work properly unless it also uses system-less root function.
Click to expand...
Click to collapse
Ok I have TWRP installed can I use directly CF auto root?
We7dy said:
Ok I have TWRP installed can I use directly CF auto root?
Click to expand...
Click to collapse
No if you want proper root with CF-auto root you must not have TWRP installed. You either choose TWRP + Magisk (non-working root) or no TWRP but with SuperSU (working root, Xposed works too).
Follow the instruction here to get you on track:
https://forum.xda-developers.com/showpost.php?p=74326169&postcount=2

How can I remove Magisk?

I've flashed Magisk, but because I can't get Xposed to work, I'd like to remove Magisk and install SuperSU, but I don't know how. I tried to flash the uninstaller via TWRP and it says everything is fine, but after rebooting it just stays installed. If I try to flash SuperSU anyway I get stuck on boot. I have to flash stock boot.img via TWRP and then Magisk magically reappears. I tried using MiFlash but it refuses to do anything. It says no permission.
One possible solution, I guess, would be to flash stock ROM via TWRP. Can this be done? Any other ideas? Or am I just stuck with Magisk until a new version is available?
Filip013 said:
I've flashed Magisk, but because I can't get Xposed to work, I'd like to remove Magisk and install SuperSU, but I don't know how. I tried to flash the uninstaller via TWRP and it says everything is fine, but after rebooting it just stays installed. If I try to flash SuperSU anyway I get stuck on boot. I have to flash stock boot.img via TWRP and then Magisk magically reappears. I tried using MiFlash but it refuses to do anything. It says no permission.
One possible solution, I guess, would be to flash stock ROM via TWRP. Can this be done? Any other ideas? Or am I just stuck with Magisk until a new version is available?
Click to expand...
Click to collapse
Magisk is pretty much "useless" for now. Because it is based on system-less root, and cannot be updated (because still in testing phase! Newer Xposed module from Magisk requires latest Magisk root binary, which is pretty out of option atm as we can't update to the latest binary). The only solution if you want to have proper root access is:
1. Head over to Xiaomi MIUI website and download the full stock ROM again, and then flash it via fastboot (choose flash_all_except_storage.bat if you want to preserve your data).
2. Once flashed, reboot back to bootloader and unlock it.
3. While still in bootloader flash the correct CF-Auto root boot image for your ROM (contains SuperSU 2.82 binary, https://desktop.firmware.mobi/device:1748)
4. Wait patiently and it will automatically reboot. Install SuperSU from Play Store if you want root management app.
5. If you need Xposed, download the Xposed apk from XDA and then install it normally (not via recovery).
6. ??? Profit
*DO NOT INSTALL permanent TWRP as it will cause your phone stuck in boot loop.
@soralz
Thanks for your help, but no luck. I understand what I'm supposed to do, but I can't get MiFlash to work. When I try to flash stock image I get a "Permission Denied" error. (I have unlocked my bootloader successfully). I tried flashing modified stock image from here But then I couldn't boot. My only solution is to flash stock boot.img via TWRP and I can boot, but I stay stuck with Magisk.
So far, the only options I can think of is to wait for a recovery-flashable ROM, a new software update or a new version of Magisk.
Filip013 said:
@soralz
Thanks for your help, but no luck. I understand what I'm supposed to do, but I can't get MiFlash to work. When I try to flash stock image I get a "Permission Denied" error. (I have unlocked my bootloader successfully). I tried flashing modified stock image from here But then I couldn't boot. My only solution is to flash stock boot.img via TWRP and I can boot, but I stay stuck with Magisk.
So far, the only options I can think of is to wait for a recovery-flashable ROM, a new software update or a new version of Magisk.
Click to expand...
Click to collapse
You couldn't boot, are you using permanent TWRP?
Have you tried download the Full ROM from here and run this (as attachment)?
http://en.miui.com/download-333.html
Btw, place the folder under 1 directory only eg: as attachment. (I tried in multiple directory eg: "D:\Phones\ROM\Stock ROM", it just wouldn't flash)
@soralz
OMG!!! I can't believe it. MiFlash refused to let me flash because I tried to do that from the wrong location. Weird??!!
Good. I’ve managed to follow your instructions and success!! Just a minor note, I couldn't flash the modified boot.img directly via fastboot, it still won't let me. But I just booted TWRP (without flashing) and then flashed it from there. Again, THANK YOU!
BTW, yes, I had flashed permanent TWRP and then unsuccessfully tried to remove it.
Filip013 said:
@soralz
OMG!!! I can't believe it. MiFlash refused to let me flash because I tried to do that from the wrong location. Weird??!!
Good. I’ve managed to follow your instructions and success!! Just a minor note, I couldn't flash the modified boot.img directly via fastboot, it still won't let me. But I just booted TWRP (without flashing) and then flashed it from there. Again, THANK YOU!
BTW, yes, I had flashed permanent TWRP and then unsuccessfully tried to remove it.
Click to expand...
Click to collapse
Oh you manage to fix that? Good for you then. And yes you cannot have permanent TWRP and SuperSU at the same time. The CF-auto root for me I just click root.bat and done. btw side note, you will lose root after each update, besure to check out the new patched boot image. I m sure in the future we will have automated process, don't need to re-root manually after each update

Can I root and keep the stock ROM?

I have bought an LG G6 (US997) and planning on rooting it.
Can it be rooted and keep the stock ROM?
TIA
Yes course it can lol.
Yeah you can
I have rooted h870 with stock rom but when you get a new ota you can't install then you need a zip file for the new update and install it with your twrp
Thanks for the replies!
So, the G6 will be rooted the moment I unlock the bootloader?
No ! after unlocking the bootloader you need to install twrp and root ( superSu or Magisk ) for your phone but before doing it your phone need to be a free carrier
https://forum.xda-developers.com/lg-g6/development/recovery-twrp-lg-g6-us997-unofficial-t3629883
So you have 3 steps
1-Unlock bootloader
2-Flash twrp
3-Flash root
Good luck and be carefull to no brick your phone or lose your data
You should really do some more research before doing this. You clearly don't have a clue.
DamiDev said:
No ! after unlocking the bootloader you need to install twrp and root ( superSu or Magisk ) for your phone but before doing it your phone need to be a free carrier
https://forum.xda-developers.com/lg-g6/development/recovery-twrp-lg-g6-us997-unofficial-t3629883
So you have 3 steps
1-Unlock bootloader
2-Flash twrp
3-Flash root
Good luck and be carefull to no brick your phone or lose your data
Click to expand...
Click to collapse
When you say Flash root , do I simply install SuperSU? If yes, what method of installation works? Play Store, ADB, or TWRP?
Thanks again.
sp_1st_timer said:
When you say Flash root , do I simply install SuperSU? If yes, what method of installation works? Play Store, ADB, or TWRP?
Click to expand...
Click to collapse
I'd recommend Magisk over SuperSU at this point. Download the Magisk zip and flash it with TWRP.
If you don't root immediately after installing TWRP, your phone will revert to the stock recovery on the next boot.
Try this guide, it will answer some of your questions:
https://forum.xda-developers.com/lg-g6/how-to/official-lg-g6-bootloader-unlock-t3614719

Categories

Resources