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...
Related
Currently, all official CyanogenMod ROMs use loki tool to install the kernel on the LG G Pad 8.3 v500. Unfortunately, using loki tool causes a benign "secure boot error message" upon startup.
Here are some scripts that can be flashed in the recovery to convert a loki kernel to a bumped (permissive) kernel. The kernel will remain permissive until a new ROM or kernel is flashed again.
When making a kernel permissive, the following commands will be appended to the kernel boot command line:
Code:
androidboot.selinux=permissive selinux=0
Note: Only apply these scripts one time when setting the kernel to permissive mode or the command line above will be appended twice.
Instructions:
1) Flash ROM
2) Flash one of the scripts below, depending on what you want.
1) Convert a loki kernel to a bumped kernel
v500-loki-kernel-to-bumped-kernel-signed.zip
2) Convert a loki kernel to a bumped permissive kernel (turns off selinux)
v500-loki-kernel-to-bumped-permissive-kernel-signed.zip
3) Convert an already bumped kernel to a permissive bumped kernel (turns off selinux)
v500-bumped-kernel-to-bumped-permissive-kernel-signed.zip
Thanks to @Skin1980 for the bash bump code.
Thanks to @aicjofs for the script base.
This is amazing, thanks for your work.
This is really great, we all love what your doing for us - thanks again. I'm gonna take a stab in the dark and guess that its probably a bad idea to use the CM updater due to these having to be flashed along with an update?
annoyingduck said:
This is really great, we all love what your doing for us - thanks again. I'm gonna take a stab in the dark and guess that its probably a bad idea to use the CM updater due to these having to be flashed along with an update?
Click to expand...
Click to collapse
It's fine to use the cm updater, but you will have to reboot into the recovery twice to apply the patch. Also, if you want your Bluetooth pairings to remain intact, then you want to keep the kernel in permissive mode and never let it boot with selinux enabled (at least until the selinux denials are fixed).
@annoyingduck
You can let cm updater download and verify the update and then hit cancel when it asks to install it. Then manually reboot to recovery and install from the cm updater download directory.
Amazing job @Deltadroid! I applied the first patch, rebooted and the warning message was gone!
Thank you very much for your outstanding work!
[]'s
So... This just removes the warning message when booting?
jesuita said:
So... This just removes the warning message when booting?
Click to expand...
Click to collapse
Yes
jesuita said:
So... This just removes the warning message when booting?
Click to expand...
Click to collapse
That is the only visible effect. It provides a cleaner way of mounting the boot.img
Ok thanks
Works fine with last Infected build.
I assume we have to flash this script after each update.
ledabe974 said:
Works fine with last Infected build.
I assume we have to flash this script after each update.
Click to expand...
Click to collapse
Yes, after each rom or kernel you flash.
Yay! thanks to the permissive script, SuperSU works on CM13! =)
nytral said:
Yay! thanks to the permissive script, SuperSU works on CM13! =)
Click to expand...
Click to collapse
That is good to hear.
The reason systemless supersu does not work with our device is because it breaks the signature on our bumped boot image.
If you choose option #1 on the op after flashing supersu, you should be able to keep selinux in enforcing mode and just rebump the boot image to fix the signature that supersu breaks.
Edit: you will need to dirty flash the rom again to put the device back into enforcing mode.. Then flash supersu and finally the script to bump the boot image over again.
Deltadroid said:
That is good to hear.
The reason systemless supersu does not work with our device is because it breaks the signature on our bumped boot image.
If you choose option #1 on the op after flashing supersu, you should be able to keep selinux in enforcing mode and just rebump the boot image to fix the signature that supersu breaks.
Edit: you will need to dirty flash the rom again to put the device back into enforcing mode.. Then flash supersu and finally the script to bump the boot image over again.
Click to expand...
Click to collapse
Well, that's what I thought and what I did first, but actually latest beta SuperSU (2.68) is not breaking the boot sig for some reason (no bootloader error as with previous builds). Looking at logcat during the stuck boot I noticed some zygote process failing because of selinux and that's when I decided to try to disable it -> success! Now a cleaner way would probably be to give the logs to @Chainfire so he can have a look but given the non-popularity of V500 he probably won't care/not be able to fix it without one. Oh well, at least I have something working although not as secure as it should be. So thank you for this :good:
Thank you for this great job!!! I was stuck on the LG logo with the know loki message... I though that my v500 was bricked for good.
I used the first file after cleaning everything in twrp 3.0.0 (not usb and external) and installing a)6.0 mmb29v, b) su v2.65 and c) your 1st file.
2 questions. 1) whenever I flash and update should I flash it through twrp with the above mentioned order? 2) Should I flash other version (older like 2..8.7.x) and philz zip?
Thank you again for your great job!!!
glyrakos said:
Thank you for this great job!!! I was stuck on the LG logo with the know loki message... I though that my v500 was bricked for good.
I used the first file after cleaning everything in twrp 3.0.0 (not usb and external) and installing a)6.0 mmb29v, b) su v2.65 and c) your 1st file.
2 questions. 1) whenever I flash and update should I flash it through twrp with the above mentioned order? 2) Should I flash other version (older like 2..8.7.x) and philz zip?
Thank you again for your great job!!!
Click to expand...
Click to collapse
You did it correctly. Every time you flash SuperSU over again, you will need to flash this script directly after that to bump the kernel over again and fix the boot signature. Any recovery should work, but I recommend using the latest official TWRP.
Deltadroid said:
You did it correctly. Every time you flash SuperSU over again, you will need to flash this script directly after that to bump the kernel over again and fix the boot signature. Any recovery should work, but I recommend using the latest official TWRP.
Click to expand...
Click to collapse
Sorry, but as a nobbie let me ask you something more. Do you have a link for the latest official TWRP. How to flash it? Through TWRP 3.0.0 that I have now, or through sideload? Also I cannot enter TWRP with the combination of the 3 buttons. I get Factory Reset menu.
Thank you.
glyrakos said:
Sorry, but as a nobbie let me ask you something more. Do you have a link for the latest official TWRP. How to flash it? Through TWRP 3.0.0 that I have now, or through sideload? Also I cannot enter TWRP with the combination of the 3 buttons. I get Factory Reset menu.
Thank you.
Click to expand...
Click to collapse
The official TWRP for device is here
http://forum.xda-developers.com/showthread.php?p=61363260
You can flash the new recovery image from within TWRP.
When you use the 3 buttons to get to recovery, it asks to factory reset, but it goes to TWRP instead. It is a hack because our recoveries were never actually unlocked. Just say, yes and TWRP will open.
Deltadroid said:
The official TWRP for device is here
http://forum.xda-developers.com/showthread.php?p=61363260
You can flash the new recovery image from within TWRP.
When you use the 3 buttons to get to recovery, it asks to factory reset, but it goes to TWRP instead. It is a hack because our recoveries were never actually unlocked. Just say, yes and TWRP will open.
Click to expand...
Click to collapse
Maybe I am not doing something good but when using the 3 button method it goes to factory reset and stays there endless if I do not press something .... but power whipes everything (i've re-setup my v500 for about 15 times already....) ... and volume up/down exits the menu and reboots......
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
Hello, I own a rooted HTC Desire 630 and I attempted to install Xposed Framework two times now, but both of my attempts failed miserably ( I got stuck at HTC boot screen, although I could access the recovery ) . So miserably that I had to relock the BL and flash the stock ROM. This is getting annoying, because I followed all the steps really carefully ( FROM HERE: bit(DOT)ly(SLASH)2oS8H1u ) and I used the correct ARM .zip file. Is there a software problem that doesn't allow this file to be flashed? Or do I have to use special Xposed files just like it's needed for Samsung?
I have to mention that I had unlocked BL, Superuser access and the latest TWRP beta made by @Captain_Throwback when doing the prcedure.
ANY HELP/FEEDBACK WOULD BE APPRECIATED
1. Root your phone
2. Install Magisk manager apk
3. Flash Magisk from recovery
4. Flash systemless Xposed framework
5. Install Xposed manager apk (modified for systemless xposed framework)
6. Install modules you want/ need.
7. Done!
mr_techno said:
1. Root your phone
2. Install Magisk manager apk
3. Flash Magisk from recovery
4. Flash systemless Xposed framework
5. Install Xposed manager apk (modified for systemless xposed framework)
6. Install modules you want/ need.
7. Done!
Click to expand...
Click to collapse
Did you attempt it? If yes, did it finish successfully?
KedBit said:
Did you attempt it? If yes, did it finish successfully?
Click to expand...
Click to collapse
I'll let the screenshots do the talking....
Screen1
Screen2
mr_techno said:
I'll let the screenshots do the talking....
That seems pretty convincing. I'll try it myself and confirm if it works for me.
Oh, and one more thing: Substratum. It's practically unusable for this device. Once you enter and finish the initial setup, you are prompted to grant it multiple app permissions, aswell as Superuser permissions. As soon as I hit GRANT on the Superuser pop-up, the phone reboots itself and the whole app data is cleared. Is it just my device that's operating like this or is Substratum unsupported?
Wondering if I should create a new thread on this if the problem persists.
Click to expand...
Click to collapse
Doesn't seem to work for me, Magisk just wouldn't install. Flashed the .zip in TWRP (v12.0) but after the reboot Magisk is still not installed.
So, in conclusion, the question still remains and the thread still awaits valid replies on how to do it.
KedBit said:
Doesn't seem to work for me, Magisk just wouldn't install. Flashed the .zip in TWRP (v12.0) but after the reboot Magisk is still not installed.
So, in conclusion, the question still remains and the thread still awaits valid replies on how to do it.
Click to expand...
Click to collapse
Use this twrp (TEST2) found on this link HERE, Install Magisk apk, flash the Magisk zip, search on XDA for SYSTEMLESS XPOSED FRAMEWORK on that thread you will find modified Xposed installer apk and ZIP file that you need to flash. While in recovery you can flash supersu zip, just google for that one. Aaaaaand you're done!
mr_techno said:
Use this twrp (TEST2) found on this link HERE, Install Magisk apk, flash the Magisk zip, search on XDA for SYSTEMLESS XPOSED FRAMEWORK on that thread you will find modified Xposed installer apk and ZIP file that you need to flash. While in recovery you can flash supersu zip, just google for that one. Aaaaaand you're done!
Click to expand...
Click to collapse
I got boot loop help me in geting stock rom for thid device please help give link
---------- Post added at 11:38 AM ---------- Previous post was at 11:26 AM ----------
KedBit said:
Hello, I own a rooted HTC Desire 630 and I attempted to install Xposed Framework two times now, but both of my attempts failed miserably ( I got stuck at HTC boot screen, although I could access the recovery ) . So miserably that I had to relock the BL and flash the stock ROM. This is getting annoying, because I followed all the steps really carefully ( FROM HERE: bit(DOT)ly(SLASH)2oS8H1u ) and I used the correct ARM .zip file. Is there a software problem that doesn't allow this file to be flashed? Or do I have to use special Xposed files just like it's needed for Samsung?
I have to mention that I had unlocked BL, Superuser access and the latest TWRP beta made by @Captain_Throwback when doing the prcedure.
ANY HELP/FEEDBACK WOULD BE APPRECIATED
Click to expand...
Click to collapse
Need stock rom of htc 630 please where u got
Give link
It does not work for me, tried everything.
How to edit in build.prob
I try to edit but after reboot on changes
Edited line are removed on every reboot ..
Any one know why and how to edit
Use Google Translator:
https://4pda.ru/forum/index.php?s=&showtopic=778560&view=findpost&p=61689325
Requirements:
- Unlock bootloader
- TWRP (3.1.x)
Download Magisk 13 fix for Axon 7
Uninstaller
Sorry my English )))
Thank you @NFound. I flashed both your B04 and magisk, magisk passes all green
For some reason everytime I try to install or download a Magisk addon the manager app just crashes. Any fix for this?
Work on A2017U?
Sent from my ZTE A2017U using Tapatalk
It works just fine for me on RR (A2017U). I flashed the uninstaller for 12 first, then I rebooted & uninstalled the magisk manager app, and lastly rebooted to recovery and flashed the zip from the op.
Thanks for this, NFound
I tried to install this on V2.0.0B01 chinese.
All passed green except the ctsProfile which returns false.
SU from magisksu works btw. what does ctsProfile mean?
Also, if I tried to enable su for apps and adb, basic integrity gives false too.
Hi, thanks for this
I'm trying this on A2017U and it doesn't seem to work. Mostly not prompting for root. Is there further progress on this?
thanks
A2017U
Click to expand...
Click to collapse
V2.0.0B01 chinese.
Click to expand...
Click to collapse
You read carefully? In title is written: for B04
If you have a different phone model, then we put the universal firmware and get rid of it!
Firmware here: https://www.androidfilehost.com/?fid=529152257862726754
Description (use translator): https://4pda.ru/forum/index.php?s=&showtopic=778560&view=findpost&p=61376493
NFound said:
You read carefully? In title is written: for B04
If you have a different phone model, then we put the universal firmware and get rid of it!
Firmware here: https://www.androidfilehost.com/?fid=529152257862726754
Description (use translator): https://4pda.ru/forum/index.php?s=&showtopic=778560&view=findpost&p=61376493
Click to expand...
Click to collapse
Thanks, sorry about that. I was linked to the thread, so I didn't notice the title. I'm reluctant to change my firmware to suit, is there possibility you could submit your changes to official magisk but also include info for A2017U? thanks either way for clearing up my misunderstanding!
Fix SafetyNet for AP
sm.bxsq said:
It works just fine for me on RR (A2017U). I flashed the uninstaller for 12 first, then I rebooted & uninstalled the magisk manager app, and lastly rebooted to recovery and flashed the zip from the op.
Thanks for this, NFound
Click to expand...
Click to collapse
i have yet to get magisk working on any rom
I don't know what to tell you. I've had it working on about all of them. I switched to AOSP Extended and is working all good still
can you please update to B05 ? Thanks
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