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
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......
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...
This thread was originally for Pixel-specific rooting instructions, but by now the SuperSU ZIP and TWRP are fully supported:
- Fastboot boot TWRP
- Install latest SuperSU ZIP (v2.79-SR3 at the time of writing)
Note that at this time I recommend against fastboot flashing TWRP. With the Pixel's new partition layout, the recovery files are inside the boot partition, and so is SuperSU. If you flash both, SuperSU's internal boot image backup will not be of the original boot image, but of TWRP. This means that neither the 'full unroot' option in SuperSU, nor incremental OTA update through FlashFire, will work as expected.
OR
- Use CF-Auto-Root for Pixel (not released at the time of writing, but should be released soon)
Nice work!
Hell Yeah!!! Thanks @Chainfire, your time as well as others that have made this and the bootloader unlock happen is appreciated very much.
Sent from my Pixel XL using Tapatalk
can we flash another kernel such as elementalX on top of this?
diabl0w said:
can we flash another kernel such as elementalX on top of this?
Click to expand...
Click to collapse
How does this relate?
Ker~Man said:
How does this relate?
Click to expand...
Click to collapse
because I attempted to not really thinking about that its systemless and wasnt sure if root would persist. after attempting to flash boot elementalX's kernel my device just powered off so i immediately reflashed root and all is okay now
diabl0w said:
can we flash another kernel such as elementalX on top of this?
Click to expand...
Click to collapse
Lol if you read chainfires instructions you would have e your answer,but it short no, not until they add it
I did read the readme.. so not sure what your getting at
cwalker0906 said:
Lol if you read chainfires instructions you would have e your answer,but it short no, not until they add it
Click to expand...
Click to collapse
chainfire said:
- If you want to use a custom kernel, simply 'fastboot boot' the root image again after flashing the custom kernel. This has been tested with a few custom kernels and found to work well so far.
Click to expand...
Click to collapse
It was a valid question since this flashing method is different than what we are used to due to the difference in partitions and the file system.
lexcyn said:
It was a valid question since this flashing method is different than what we are used to due to the difference in partitions and the file system.
Click to expand...
Click to collapse
okay thanks, so i guess the answer is actually yes
Thanks @Chainfire - booted and working well!
thanks..emoji..root explorer.. viper.. naptime.. titanium.. yes..
if new kernel must boot boot to root again..
Seems I cannot remount /system_root as rw (to copy Emoji font over).
marlin://system_root/system/fonts # mount -o remount,rw /system_root
mount: '/dev/block/bootdevice/by-name/system_a'->'/system_root': Device or resource busy
Edit: Nevermind, used Solid Explorer and granted it SuperUser and seemed to work. Strange.
Does anyone have the stock boot.img for the pixel xl? I don't have the data to download the full factory image.
Life is good!
Thanks to all involved, especially Chainfire.
You Rock!
Worked like a charm. Thanks @Chainfire!
Can't thank you enough. Works perfectly.
can someonone please post the exact steps they are using?
I just unlocked my bootloader. then tried flashing the root-boot img file, it did the reboots, but when i complete android setup, theres no SuperSU and if i install the .apk, it still does not detect root...
just reflashed stock boot.img, locked and unlocked bootloader. waiting for instrustion.
thanks!
spunks3 said:
can someonone please post the exact steps they are using?
I just unlocked my bootloader. then tried flashing the root-boot img file, it did the reboots, but when i complete android setup, theres no SuperSU and if i install the .apk, it still does not detect root...
just reflashed stock boot.img, locked and unlocked bootloader. waiting for instrustion.
thanks!
Click to expand...
Click to collapse
fastboot boot boot-to-root.img
lexcyn said:
fastboot boot boot-to-root.img
Click to expand...
Click to collapse
what about superSU?
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
hi Guys!
I just wanted to share my work with you.
I created a working TWRP recovery for the Pixel on Android O developer preview 4, that can boot and decrypt the /data partition. I don't own a Pixel XL, so I can't test, but @Chainfire did a few quick tests and it seems to be working on his Pixel XL too. So I would say you can try and see if it works for you. Please keep in mind, that I didn't test it, and neither Chainfire, or myself or anyone else can be blamed if it doesn't work, or damages your phone (shouldn't actually, but who knows..).
If you are still not scared enough, please follow this link to the Pixel forums and check out my work:
https://forum.xda-developers.com/pixel/development/mod-twrp-recovery-pixel-android-o-dp4-t3651896
Good luck!
I test it on my pixel xl， working well.
Thank you very much.
But it seems to not be able to flash supersu
When I try to flash it via fastboot it says file is not signed. What am I doing wrong here? I wanted to be rooted and I am on Android op4 preview. Please guide me how to root. Thank you everyone.
sahilarora2003 said:
When I try to flash it via fastboot it says file is not signed. What am I doing wrong here? I wanted to be rooted and I am on Android op4 preview. Please guide me how to root. Thank you everyone.
Click to expand...
Click to collapse
Its in the instructions but here is the command and you shouldn't flash it but instead fastboot it.
fastboot boot trwp.img
flash the latest supersu 2.82 sr1
NVM. Mission accomplished. Thank you for help.
feimummy said:
I test it on my pixel xl， working well.
Thank you very much.
But it seems to not be able to flash supersu
Click to expand...
Click to collapse
To root, you don't even need recovery. Use @Chainfire's boot-to-root.img (fastboot boot it), and it will do the job for you. Easiest way to root...
And don't forget to thank him!
SR2 flash fine
gubacsek said:
To root, you don't even need recovery. Use @Chainfire's boot-to-root.img (fastboot boot it), and it will do the job for you. Easiest way to root...
And don't forget to thank him!
Click to expand...
Click to collapse
You can try SR2 flash fine.
gubacsek said:
To root, you don't even need recovery. Use @Chainfire's boot-to-root.img (fastboot boot it), and it will do the job for you. Easiest way to root...
And don't forget to thank him!
Click to expand...
Click to collapse
Thank you for your answer.
Thank Chainfire.
But my phone Pixel XL is at home now,I will try it later.
Is it this one?
https://download.chainfire.eu/1011/CF-Root1/root-marlin-pixelxl.zip
feimummy said:
Thank you for your answer.
Thank Chainfire.
But my phone Pixel XL is at home now,I will try it later.
Is it this one?
https://download.chainfire.eu/1011/CF-Root1/root-marlin-pixelxl.zip
Click to expand...
Click to collapse
Yes, that should be it!
Although Chainfire has released a new version in zip format, with a lot of pixel (XL) related fixes. You can also try to flash that one using my modded TWRP.
gubacsek said:
Yes, that should be it!
Although Chainfire has released a new version in zip format, with a lot of pixel (XL) related fixes. You can also try to flash that one using my modded TWRP.
Click to expand...
Click to collapse
I have used your modded TWRP to flash SuperSU zip,but there was nothing happened after rebooting the phone.
And I also try "fastboot boot boot-to-root.img" just now,there was still nothing happened...
View attachment 4236828
I mean,it was so strange that SuperSU can not be flashed into my Pixel XL with these two methods.
——————————The final outcome——————————
I have solved the problem with this SuperSU version:
https://forum.xda-developers.com/showpost.php?p=72686197&postcount=10481
Thanks a lot.
feimummy said:
I have used your modded TWRP to flash SuperSU zip,but there was nothing happened after rebooting the phone.
And I also try "fastboot boot boot-to-root.img" just now,there was still nothing happened...
View attachment 4236828
I mean,it was so strange that SuperSU can not be flashed into my Pixel XL with these two methods.
Click to expand...
Click to collapse
Try to flash the original boot.img first.
1. reboot to bootloader
2. fastboot flash boot.img from the factory image zip
3. fastboot boot recovery.img
4. in the recovery, flash supersu
Or you can skip points 3 and 4, and fastboot boot boot-to-root.img
gubacsek said:
Try to flash the original boot.img first.
1. reboot to bootloader
2. fastboot flash boot.img from the factory image zip
3. fastboot boot recovery.img
4. in the recovery, flash supersu
Or you can skip points 3 and 4, and fastboot boot boot-to-root.img
Click to expand...
Click to collapse
Sr2 flash fine!
caballon said:
Sr2 flash fine!
Click to expand...
Click to collapse
Great! Nice to see that everything is working I had this itching, you know, when something is not as it should be, because I wanted to have Android O, but there was no recovery to do what I want... Now this feeling is gone, and I'm relaxed again
The only thing missing is a flashable zip. Is my current "itch"
Very nice. I booted into TWRP with no issue. I had already used boot-to-root so I did not have to flash SR2 in TWRP but nice knowing we have it working for the XL.
Thank you for making this sir.
Work like a charm in Final Android O!!! Thanks man.
caballon said:
Work like a charm in Final Android O!!! Thanks man.
Click to expand...
Click to collapse
Same here!
People have successfully rooted O Final? I used the img but I can't flash zips or access any folders they all have weird names is that due to Encryption?
liam_davenport said:
People have successfully rooted O Final? I used the img but I can't flash zips or access any folders they all have weird names is that due to Encryption?
Click to expand...
Click to collapse
Had this already sometimes on 7.1.2 with twrp rc 1 and 2. Must be an encryption error. Only way for me to use the phone again was to start all over with flashing factory image with flash-all.bat.
liam_davenport said:
People have successfully rooted O Final?
Click to expand...
Click to collapse
Reboot until you get prompted for your PIN in recovery, then flash SuperSU v2.82 SR3 from here.