After a lot of tries, I am writing this.
Steps I follow: http://forum.xda-developers.com/showpost.php?p=69651636&postcount=314
I know that SuperSU 2.79 SR1 is for Nougat. I tried that too, and my device doesn't get SuperSU.
I flashed SuperSU 2.78 SR3 and got root, but the combination doesn't seem to work in Pokemon GO.
So I got iSU which perfectly worked until the PGO update 0.55, after which it stopped working.
Now I got back to this systemless flashing, and after I flash suhide, my phone enters bootloop.
Please give me guaranteed instructions about how to play Pokemon GO with Resurrection Remix (CM13).
Pokemon GO already banned root users quite some time back. It's supposed to be possible to play it with magisk, but I don't know much more beyond that.
Just delete su file from System/bin and system/xbin. It will work fine then.
darius7203 said:
Just delete su file from System/bin and system/xbin. It will work fine then.
Click to expand...
Click to collapse
Cant find it unfortunatly... I am on CM13 and rooted my device before that to flash it fro EMUI to CM13 RECENTLY... but i weirdly cant find super su anymore? Is it deleted during the flash? Or is is somewhere hidden?
Related
Bump script for SuperSU (2.62+) system-less install modeWhat it does:
Shortly: it let's you install newer SuperSU (version 2.62 or later) on Marshmallow ROMs with read-only system partition without issues.
Newer SuperSU installer repacks kernel (boot.img) during installation, so bootloader's security key is lost. This scripts allows SuperSU installer to add it back to kernel before flashing it back to boot sector. No more Secure Boot error!
It should work on any LG device with locked bootloader that supports Bump method (G2 and G3 do).When to use:
You're on Marshmallow ROM;
You want to flash latest SuperSU.
How to use:
(if older (<2.62) SuperSU is already installed) open supersu app and remove root completely;
reboot recovery;
MAKE BACKUP of boot sector! In case something goes wrong;
flash CustomPatcherScript_Bump.zip;
flash SuperSU v2.62+;
reboot system.
Downloads:
Script in attachments
SuperSU v2.62+
NOTE:
If you use system-less root, you would need to flash SuperSU on every system and kernel update!
Script is stored in /data, so if you format /data (factory reset), you'd need to flash it again.
Have fun! :good:
I've made a flashable zip and updated instructions. Everything work fine for me here!
Btw, it should work for every device with Bump (like G3), feel free to test and report.
Added to index
[INDEX][LG G2] ROMs, Kernels, Guides and more
Works well on D802
Thanks a lot mate for the script.
Added a little more info to OP.
Anyone else tried it? Any issues?
SimpleX91 said:
Added a little more info to OP.
Anyone else tried it? Any issues?
Click to expand...
Click to collapse
Just tested of LG G3 D855 and working perfectly.
Thanks!
Working on CM13 with BETA SuperSU 2.67 (D802).
Thx for great script
Is it possible using this script on Cloudy G2 3.3?
Didn't work. CM13 05/03 - D802 - SuperSU 2.68.
No errors, but no sign of SuperSU too. I installed by Play Store but don't update binary.
InsideMuz said:
Didn't work. CM13 05/03 - D802 - SuperSU 2.68.
No errors, but no sign of SuperSU too. I installed by Play Store but don't update binary.
Click to expand...
Click to collapse
i played with it and no SuperSU also from me and then i tried another Tool, SuperSU is visible.
Oops. I didn't realize this was already a thing :silly:
Thank you. Works well on G3.
InsideMuz said:
Didn't work. CM13 05/03 - D802 - SuperSU 2.68.
No errors, but no sign of SuperSU too. I installed by Play Store but don't update binary.
Click to expand...
Click to collapse
Read the description. You need to FLASH supersu zip file via recovery, not install with play store. If supersu would alternate kernel files somehow and didn't call the script, ROM wouldn't boot at all.
andh1ka said:
Is it possible using this script on Cloudy G2 3.3?
Click to expand...
Click to collapse
This script is just a helper for SuperSU flashable zip. If supersu flashes in systemless mode, you need it. If not, this script won't be even called (so useless).
For me SuperSU v2.68 not working I'm back to 2.67 and everything is ok
SimpleX91 said:
Read the description. You need to FLASH supersu zip file via recovery, not install with play store. If supersu would alternate kernel files somehow and didn't call the script, ROM wouldn't boot at all.
Click to expand...
Click to collapse
I did how description says, but didn't work, so I tried installing by Play Store. I think it's SuperSu 2.68 fault, because blastagator's tool didn't work too, now I'm going to try with 2.67.
By "doesn't work" you mean no supersu (app and/or binary)? If so, it's not related to the patcher script here. If you'd flash SuperSU in systemless mode without custom_boot_image_patch.sh in /data, you'd get a security error during boot.
I can't test it anymore, my G2's display is dead. But please try SuperSU-2.69 and look at flashing log. It should patch kernel image AND call "custom_boot_image_patch.sh" ("- Calling user boot image patch script").
See this and next page. On G3 also is some problem with 2.68.
Eselter said:
See this and next page. On G3 also is some problem with 2.68.
Click to expand...
Click to collapse
I used this Bump script and 2.68 and 2.71 on my LG G3 D855 and it works perfectly.
Sent from my LG-D855 using Tapatalk
@SimpleX91 Hi man.
I wanted to update supersu then I tried but it failed. My phone got bootloop. Firstly I had supersu 2.52 then I followed instructions except for remove root. Because I cant get into recovery if I remove root( I have installed widget to get into recovery). I did everything else as you mentioned.
My device is LG G3 D855TR Fulmics 4.2 MM
Please help...
Just flash the zip in the attachment, and then flash SuperSU. No more messing with Terminal Emulator!
Note: if you installed SuperSU first, and got a bootloop, install the fixer then SuperSU again. All will be good.
Please don't redistribute this, just link to the thread.
Thanks. Phone wouldn't boot after SuperSU install. This worked perfectly.
Note: if you installed SuperSU first, and got a bootloop, install the fixer then supersu again. All will be good.
mx597turbo said:
Thanks. Phone wouldn't boot after SuperSU install. This worked perfectly.
Note: if you installed SuperSU first, and got a bootloop, install the fixer then supersu again. All will be good.
Click to expand...
Click to collapse
I'll add your note to the op
Life saver
Yay! I was in that bootloop, and then I couldn't find an ADB driver that worked, to load this fix. The obvious solution was to put the fix on a Micro-SD card but it didn't come to me for a bit - my other current phone has no external card slot - but once I did this, the fix worked perfectly. Many thanks to whomever came up with this!!!
No need to flash SuperSu for root, phh's SuperUser works perfect
Can I ask what this script exactly does?
Is this only for flashing SuperSU on to stock? or is this something I need to use every time I flash SuperSU on any rom, even on lineageOS?
I just am confused what this script does and when exactly I would need to use it. Thanks!
BigNaes said:
Can I ask what this script exactly does?
Is this only for flashing SuperSU on to stock? or is this something I need to use every time I flash SuperSU on any rom, even on lineageOS?
I just am confused what this script does and when exactly I would need to use it. Thanks!
Click to expand...
Click to collapse
This is for roms on stock and also roms that do not support native root. If you flash LineageOS, all you have to do is flash their SU package in their Extras section on the website. Some of the roms in the development section have native root built in under development settings, and some do not.
fireball0093 said:
This is for roms on stock and also roms that do not support native root. If you flash LineageOS, all you have to do is flash their SU package in their Extras section on the website. Some of the roms in the development section have native root built in under development settings, and some do not.
Click to expand...
Click to collapse
Thank you for your reply. I understand. I prefer to use SuperSu as opposed to the LineageOS SU package.
When I installed LineageOS I flashed this zip first and then SuperSU after and it works perfectly, I am just not sure if I needed this zip first when using Lineage OS.
Also one last question is I believe I found a post which explains what this fix does, can anyone confirm this is the fix being performed? https://forum.xda-developers.com/moto-g4/how-to/how-to-root-g4-fix-bootable-attempted-t3417592
Thanks again for all the help, always learning on XDA :good:
If anybody wants the manual method, type this is Terminal in TWRP Recovery:
echo SYSTEMLESS=true>>/data/.supersu
Ashutosh Sundresh said:
If anybody wants the manual method, type this is Terminal in TWRP Recovery:
echo SYSTEMLESS=true>>/data/.supersu
Click to expand...
Click to collapse
What's that for??
Sanjay parsi said:
What's that for??
Click to expand...
Click to collapse
SuperSU, if you don't type this, your device WILL bootloop
download link isn't working for me.
Edit: everything is fine my brain is the one not working
Follow this steps:
Boot into TWRP recovery
Flash the latest full signed flashable zip
Flash the new OTA incremental update zip
Flash the SuperSU zip
Reboot
Download links:
1.Oxygen OS 3.6.0: OnePlus2Oxygen_14_OTA_031_all_1706262034.zip
2.TWRP Recovery.-Official TWRP custom recovery with USB OTG support
3.Super SU zip:Modified SuperSU v2.82 TWRP flashable zip
4.Xposed installer zip: http://dl-xda.xposed.info/framework/sdk23/arm64/
5.Xposed uninstaller zip:http://dl-xda.xposed.info/framework/uninstaller/
Video:
Source:hacksters.tk
Thanks its working fine..
I updated to 3.6.1 (late and reluctant because of root) and obviously lost root... Been trying to get it back and I figured when I landed on this thread I realized I had done so when the last update was pushed and thought this root zip should work (I even had it in my files.. DOH!) but alas, it did not. I've tried the last 5 versions of twrp thinking it might help, still nada!
Is it only me or do you guys know if this modded superSU works for 3.6.1?
thanks!
Same Issue
orangeworx said:
I updated to 3.6.1 (late and reluctant because of root) and obviously lost root... Been trying to get it back and I figured when I landed on this thread I realized I had done so when the last update was pushed and thought this root zip should work (I even had it in my files.. DOH!) but alas, it did not. I've tried the last 5 versions of twrp thinking it might help, still nada!
Is it only me or do you guys know if this modded superSU works for 3.6.1?
thanks!
Click to expand...
Click to collapse
Same. I can't even get my phone to root again. Any help would be appreciated!
mananrishab said:
Same. I can't even get my phone to root again. Any help would be appreciated!
Click to expand...
Click to collapse
I scrapped SuperSu and went with Magisk... it's doing it's job. Wasn't down to clear everything off my phone ... always a hassle to backup, upgrade and restore with, most of the time, tons of crap happens along the way.
Hope this helps and sorry late reply!
EASY METHOD : tested on N-B05 - report when problems
(THIS SHOULD WORK FOR EVERY MODEL IMO)
For those who want to replace SuperSU with the latest Magiskv13.3 (stable) :
0. BACKUP FIRST !
1. Download latest here and put it on ext.SD
2. go into SuperSU app (#) and scroll down to 'Fully Unroot'
3. Tap it and tap YES when asking to replace boot.img - if this doesn't work : tap NO and flash it in TWRP before Magisk (works on B04, B05 and B06)
4. As soon as it starts to run and you get a first black screen : hold VOL+ and Power as to go into TWRP (if you should have missed the first attempt, don't panic, let it boot, power off again and go back into TWRP )
5. once in TWRP flash Magiskv13.3 (or flash boot and Magisk depending on the method you choose)
6. Done !
I tested it by installing a module and no problem so far...
Having root...
EDIT : when above steps are not working (Magisk Manager chashes) try following steps :
1. First download Magisk v13.3 and Magisk Manager v5.2.0 which you can find here and put both on ext SD
2. Follow procedure like above again
3. Run Magisk and when it chrashes to give permissions just go into settings/apps/wipe cache and settings from magisk.
Then install latest Magisk Manager v5.2 0 apk , run Magisk again and see if it grants permissions to f.e AdAway.
Normally this should work when you encounter crashes by just installing Magisk 13.3
Report when having issues or comment
thnx @topjohnwu
Thanks bro
Confirmed working on 2017G
i didnt replace boot.img in su uninstall(was giving error in su uninstall)
i flashed it in twrp before magisk install
And what happens if you mess up or miss going directly into TWRP?
Edit: Well I did it on, on a 2017U. It gave me a heart attack because it went black but that was TWRP just putting the screen to sleep. I'll report back if there are any issues.
Edit 2: "Magisk Manage keeps stopping".
What do I do now?
Cyrus D. said:
And what happens if you mess up or miss going directly into TWRP?
Edit: Well I did it on, on a 2017U. It gave me a heart attack because it went black but that was TWRP just putting the screen to sleep. I'll report back if there are any issues.
Edit 2: "Magisk Manage keeps stopping".
What do I do now?
Click to expand...
Click to collapse
Try reading the b32 thread.
lafester said:
Try reading the b32 thread.
Click to expand...
Click to collapse
I found it: https://forum.xda-developers.com/showpost.php?p=73654420&postcount=37
Thanks.
Edit: But I'm wondering, why does Root Switch say "Magisk is not fully supported"?
Cyrus D. said:
And what happens if you mess up or miss going directly into TWRP?
Edit: Well I did it on, on a 2017U. It gave me a heart attack because it went black but that was TWRP just putting the screen to sleep. I'll report back if there are any issues.
Click to expand...
Click to collapse
You can't mess up , it just reboots, so power off again to go back in TWRP, that easy. I updated OP to lower the chances of possible heart attacks
EDIT : for some reason this method works on N-B05 and not on latest N-B06 (crashes) - EDIT2 : figured it out :cyclops: ( wipe cache/data from Magisk in settings/apps and install Magisk Manager v5.2.0 )
tuiyaan said:
Thanks bro
Confirmed working on 2017G
i didnt replace boot.img in su uninstall(was giving error in su uninstall)
i flashed it in twrp before magisk install
Click to expand...
Click to collapse
I can confirm the same flow as well, it works! (A2017G B06)
good morning.
I'm stuck at the point of flashing boot.img (restoring by uninstalling supersu doesn't work), where can I get it? I have an A2017G with lineage 14.1
thanks.
---------- Post added at 04:28 PM ---------- Previous post was at 04:27 PM ----------
good morning.
I'm stuck at the point of flashing boot.img (restoring by uninstalling supersu doesn't work), where can I get it? I have an A2017G with lineage 14.1
thanks.
chironfr said:
good morning.
I'm stuck at the point of flashing boot.img (restoring by uninstalling supersu doesn't work), where can I get it? I have an A2017G with lineage 14.1
thank.
Click to expand...
Click to collapse
SuperSU backs up the original boot image with a long name and .gz extension. Exact whereabouts I forgot. Oddly, on my currently running ROM, I can't a backed up image anywhere.
Regardless, unpacking the LOS zip will get you the original boot image.
ZTE Axon 7 A2017U, Dark ROM, LlamaSweet 0.5 Kernel, Multiboot, XDA Legacy
I never post for help, but I am at my wits end.
I have a Vodafone tablet that's running 6.0 marshmallow that refuses to root. I did find a TWRP recovery compiled for the device, which I installed using SP Flash Tool.
TWRP seems to work as expected. I can make and restore backups, format partitions, mount system, delete files with the file manager and so on.
TWRP is also kept on every reboot. It never replaced by the stock recovery.
However, when I try and install the SuperSU zip 2.82 to root the device, it seems to be successful. However, when I boot into Android and open the SuperSU app, it says,"SU binary occupied" and closes.
That error is displayed when installing 2.82. When installing versions like 2.79, it shows the option to install the SU binary, again like normal, but it always fails to install the binary.
Using a root checker app from FDroid tells me the same thing, that root isn't avaliable. TWRP flashing should be working though, since I can flash busybox and it is detected correctly by the same root checker app.
Other root apps refuse to work.
Whilst in TWRP, I am able to browse the file system and the su file is located in system/xbin, again like it should be. Numerous other files from busybox are also located there, further signalling a successful flash. I can chmod 755 the su file without issue, but it doesn't fix anything.
The bootloader of the tablet is unknown to me. I can't boot into fastboot or bootloader mode. Trying to do so just reboots the tablet. Nothing is shown on the screen either, and it boots to Android again. I did enable ,"OEM Unlocking" in developer options.
Any ideas what I can do? I really want to give this device a thorough chance, since it is a surprisingly enjoyable device to use, and for the price I paid it's almost a total no-brainer.
I just want root so it can become a total no-brainer to own.
Thank you for your time.
I figured it out.
I tried installing Magisk by patching the boot.img within the app and flashing it via SP Flash Tool, and it worked perfectly.
I never thought of using that, but I am glad that I did.
So, yeah. Use Magisk.