Database Users

Supersu abort on 7.1.1

Has anyone had any issues trying to flash the latest supersu beta on 7.1.1? I get an abort message whenever I flash

Guitarboarder28 said:
Has anyone had any issues trying to flash the latest supersu beta on 7.1.1? I get an abort message whenever I flash
Click to expand...
Click to collapse
Chainfire has stated before that root with SuperSU on 7.1 may be a while, that he's working on it but a lot has changed (at least I read this all from him on a Pixel related thread...I assume much of it holds true for 7.1 in general).

ohlin5 said:
Chainfire has stated before that root with SuperSU on 7.1 may be a while, that he's working on it but a lot has changed (at least I read this all from him on a Pixel related thread...I assume much of it holds true for 7.1 in general).
Click to expand...
Click to collapse
Oh thanks. I've seen others talk about rooting on 7.1 no problem. I'll have to do more digging I guess

I rooted the 7.1 DP 1 With supersu SR1-v2.78.
No issues at all (even A.R.I.S.E. worked after deleting audio_effects.conf)

Mgrev said:
I rooted the 7.1 DP 1 With supersu SR1-v2.78.
No issues at all (even A.R.I.S.E. worked after deleting audio_effects.conf)
Click to expand...
Click to collapse
Did you root after flashing the ota or full image? I've been trying sr1 and for whatever reason after the ramdisk patch script it fails.

Guitarboarder28 said:
Did you root after flashing the ota or full image? I've been trying sr1 and for whatever reason after the ramdisk patch script it fails.
Click to expand...
Click to collapse
I used Fastboot and flashed every image manually (so that i wouldn't loose data). I used twrp 3.0.2-2 fyi. What about you?

Mgrev said:
I used Fastboot and flashed every image manually (so that i wouldn't loose data). I used twrp 3.0.2-2 fyi. What about you?
Click to expand...
Click to collapse
I was trying after flashing the ota. I even tried the full image without wiping (same version of twrp as you). Something must have just gotten messed up flashing the ota though. I gave up and did a full flash with wipe and sr1 flashed no problem. Thanks for trying to help me out though, I appreciate it
Edit: worded better. @Mgrev no hate was meant, thanks for trying to help me out!

Guitarboarder28 said:
you sound like you need a hug!
Oh thanks. I've seen others talk about rooting on 7.1 no problem. I'll have to do more digging I guess
Click to expand...
Click to collapse
Interesting...maybe he was exclusively referring to the new Pixel partition structure, etc...Not sure. Good luck

I was able to flash SuperSU R1 from TWRP and it worked, but when I added SUHIDE it hangs at boot animation. I flashed the factory image file by file, and not the OTA.

ohlin5 said:
Interesting...maybe he was exclusively referring to the new Pixel partition structure, etc...Not sure. Good luck
Click to expand...
Click to collapse
Yes that's my guess too I'm assuming he's talking about the pixel and it's new partitions
dratsablive said:
I was able to flash SuperSU R1 from TWRP and it worked, but when I added SUHIDE it hangs at boot animation. I flashed the factory image file by file, and not the OTA.
Click to expand...
Click to collapse
oh thanks for the heads up. Who knows if we'll ever see an updated suhide with safetynet checking the bootloader it may never be possible to pass safety net anymore

Guitarboarder28 said:
Yes that's my guess too I'm assuming he's talking about the pixel and it's new partitions
oh thanks for the heads up. Who knows if we'll ever see an updated suhide with safetynet checking the bootloader it may never be possible to pass safety net anymore
Click to expand...
Click to collapse
Well not worried about passing safetynet, since I can do without Android Pay, just want to hide root to play PoGo.

dratsablive said:
Well not worried about passing safetynet, since I can do without Android Pay, just want to hide root to play PoGo.
Click to expand...
Click to collapse
Oh is it no longer using safetynet? There's a new hide method with magisk V8 maybe that'll work

Guitarboarder28 said:
Oh is it no longer using safetynet? There's a new hide method with magisk V8 maybe that'll work
Click to expand...
Click to collapse
Well my bootloader is unlocked, but having suhide installed on the developer preview causes a boot hang. Will have to try the other method out. Thanks.

Guitarboarder28 said:
I was trying after flashing the ota. I even tried the full image without wiping (same version of twrp as you). Something must have just gotten messed up flashing the ota though. I gave up and did a full flash with wipe and sr1 flashed no problem. Thanks for trying to help me out though, I appreciate it
Edit: worded better. @Mgrev no hate was meant, thanks for trying to help me out!
Click to expand...
Click to collapse
I didn't think you meant to express hate either!
I seemed to forget to mention that i backed up my data with titanium backup, flashed, then wiped, and then restored it. So in the end, you probably need to wipe (just like you did)

dratsablive said:
Well my bootloader is unlocked, but having suhide installed on the developer preview causes a boot hang. Will have to try the other method out. Thanks.
Click to expand...
Click to collapse
Magisk hide just hides Magisk itself... it doesn't do anything for root. As for PoGo, right now the only way to do that on 7.1.1 is to NOT be rooted.
Once the kernel sources for the 7.1.1 are released, this patch will make its way onto custom kernels, which means you'll still be able to edit /system while rooted, unroot, and keep the changes via the patched kernel, as well as bypassing the SafetyNet bootloader check.
A kernel does exist now with that patch (francokernel), but it is based on the 7.0 kernel sources, so some things are broken if used on 7.1.1.
In re: to the superSU ramdisk install failure, this will happen if there are old files left over in /data from a previous magisk install and/or patched boot images. The SuperSU installer script will detect those and step into code branches that it doesn't need to be in, and thus fail. The solution is deleting the offending files from TWRP w/ adb, and installing SuperSU zip again.
/thread

Thread cleaned a bit, please stay on topic.
Have a good day!
Forum moderator,
Matt

Works fine for me flashed 7.1.1 OTA then flashed SuperSU zip

Project deleted.

Projector permanently suspended.

reserved for updated links.

Sands207 said:
I just made a ROM for Boost/Sprint SM-J327P J3 Emerge that should be flashable in TWRP. I have 2 versions, One that should be Odin flashable and the other being a zip that should be easily flashed in TWRP once we work out the kinks ... I worked primarily on LG's before this and Samsungs long before that. Anyway these are the features I've added so far:
Deodexed
Pre-rooted
Deknoxed
Busybox included
init enabled
Csc debloated (not exactly sure what to remove for bloat but I need feedback on what can be kept etc...
zip aligned on boot
xposed
links coming later today....
lemme know if I missed anything!!
I need testers! Chime in if you would like to help, we have a way to unbrick easily via Odin
*Update* 7.11.17 Flashed it on my phone but may have gotten steps CONFUSED? Installs perfectly... No loops just either takes forever to load initially or hangs on my device. I got sick of waiting but I'm curious if others know, when we flash a new pre rooted stock rom do we need to wipe data, then supersu & dm verity patch? Will removing csc stuff brick this device?
*FLASH AT YOUR OWN RISK!* I am not responsible for ANY damage to your device. ALWAYS MAKE A BACKUP FIRST, I can link to Odin and firmware files if needed til we get this right.
Flash rom
Mount DATA
Format data in TWRP this will wipe internal storage
Reboot recovery
Flash Supersu
Flash dm verity patch and *possibly* Xposed?
Credit goes to @[email protected]@[email protected] for TWRP Recovery and Root https://forum.xda-developers.com/ga...overy-twrp-3-1-0-1-samsung-galaxy-j3-t3573607
Wait for device to boot first boot may take awhile!!
Initial Alpha Release: https://drive.google.com/file/d/0Bz99NuhE3Xwmd2c4d3ZDV3dPcTA/view?usp=drivesdk
Signed Version
https://drive.google.com/file/d/0Bz99NuhE3XwmWXZHdWxCalBNcWM/view?usp=drivesdk
Please Report back with failure, success or bugs or feature requests.
Click to expand...
Click to collapse
Ill download and get back to you with sucess/failure or w.e i might encounter that can be tweakes.
Regards
Doctur

I'm downloading it now, I'll flash it as soon as I'm done. I just wiped my J327P after having root, no more knox, and Xposed running smooth. It accidentally had a pocket party with my keys and some of the seedier Xposed modules one night and then after that, it was never the same. I think I pretty got no more USB besides Odin. TWRP can't even use it.
But hey, listen Sands. This better not be some bull****. Don't you ever **** me Sands. You hear me? Don't you ever **** me. :good:

IdealInShade said:
I'm downloading it now, I'll flash it as soon as I'm done. I just wiped my J327P after having root, no more knox, and Xposed running smooth. It accidentally had a pocket party with my keys and some of the seedier Xposed modules one night and then after that, it was never the same. I think I pretty got no more USB besides Odin. TWRP can't even use it.
But hey, listen Sands. This better not be some bull****. Don't you ever **** me Sands. You hear me? Don't you ever **** me. :good:
Click to expand...
Click to collapse
ANYTHING

Sands207 said:
I just made a ROM for Boost/Sprint SM-J327P J3 Emerge that should be flashable in TWRP. I have 2 versions, One that should be Odin flashable and the other being a zip that should be easily flashed in TWRP once we work out the kinks ... I worked primarily on LG's before this and Samsungs long before that. Anyway these are the features I've added so far:
Deodexed
Pre-rooted
Deknoxed
Busybox included
init enabled
Csc debloated (not exactly sure what to remove for bloat but I need feedback on what can be kept etc...
zip aligned on boot
xposed
links coming later today....
lemme know if I missed anything!!
I need testers! Chime in if you would like to help, we have a way to unbrick easily via Odin
*Update* 7.11.17 Flashed it on my phone but may have gotten steps CONFUSED? Installs perfectly... No loops just either takes forever to load initially or hangs on my device. I got sick of waiting but I'm curious if others know, when we flash a new pre rooted stock rom do we need to wipe data, then supersu & dm verity patch? Will removing csc stuff brick this device?
*FLASH AT YOUR OWN RISK!* I am not responsible for ANY damage to your device. ALWAYS MAKE A BACKUP FIRST, I can link to Odin and firmware files if needed til we get this right.
Flash rom
Mount DATA
Format data in TWRP this will wipe internal storage
Reboot recovery
Flash Supersu
Flash dm verity patch and *possibly* Xposed?
Credit goes to @[email protected]@[email protected] for TWRP Recovery and Root https://forum.xda-developers.com/ga...overy-twrp-3-1-0-1-samsung-galaxy-j3-t3573607
Wait for device to boot first boot may take awhile!!
Initial Alpha Release: https://drive.google.com/file/d/0Bz99NuhE3Xwmd2c4d3ZDV3dPcTA/view?usp=drivesdk
Signed Version
https://drive.google.com/file/d/0Bz99NuhE3XwmWXZHdWxCalBNcWM/view?usp=drivesdk
Please Report back with failure, success or bugs or feature requests.
Click to expand...
Click to collapse
DM Verity is better if you flash it before instead of after root method. Instead of flashing SuperSU use magisk because a lot of apps are starting to reject rooted devices using SuperSU. After flashing magisk, wipe cache and dalvik

SonderTech said:
DM Verity is better if you flash it before instead of after root method. Instead of flashing SuperSU use magisk because a lot of apps are starting to reject rooted devices using SuperSU. After flashing magisk, wipe cache and dalvik
Click to expand...
Click to collapse
Should i make a new build with magisk incorporated? I've never used it before but my lady uses snapchat and will likely need this to root hers as well. i didn't update mine but she did so has the second to newest ota build on hers, i can use her system dump for an update. Can you link me to the recommended version for ours? xposed seems ok too but seems limited. thanks for your input
Sent from my SM-J327P using Tapatalk

Sands207 said:
Should i make a new build with magisk incorporated? I've never used it before but my lady uses snapchat and will likely need this to root hers as well. i didn't update mine but she did so has the second to newest ota build on hers, i can use her system dump for an update. Can you link me to the recommended version for ours? xposed seems ok too but seems limited. thanks for your input
Click to expand...
Click to collapse
She definitely will need magisk then, they are all the way on 13.2 . I could try to help you through the installation if you would like.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445/page3

SonderTech said:
She definitely will need magisk then, they are all the way on 13.2 . I could try to help you through the installation if you would like.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445/page3
Click to expand...
Click to collapse
Definitely, ill be back at my pc tonight or tomorrow i really appreciate it. hoping to make the next one smoother magisk sounds pretty interesting, do we have a safe list of what we can remove? or what needs to be flashed w the rom?

Sands207 said:
Definitely, ill be back at my pc tonight or tomorrow i really appreciate it. hoping to make the next one smoother magisk sounds pretty interesting, do we have a safe list of what we can remove? or what needs to be flashed w the rom?
Click to expand...
Click to collapse
Knox files are good to remove. Samsung device manager and samsung+ is a no go. That's all I know at the moment. Before I forget, if your gonna flash gapps do it before rooting but after DM Verity

SonderTech said:
Knox files
are good to remove. Samsung device manager and samsung+ is a no go. That's all I know at the moment. Before I forget, if your gonna flash gapps do it before rooting but after DM Verity
Click to expand...
Click to collapse
Cool, so from what ive gathered so far im going to make the next rom unrooted but deodexed as as debloated as i possibly can safely and we will flash the newest MM gapps first, then dm verity and a reboot to recovery per the directions, then magisk and finally xposed and clear cache and dalvik at the end... sound about right? I did try flashing magisk on my device as is but it failed because the boot image was already patched and stock was needed instead. Is dm verity absolutely needed or could magisk accomplish in theory what our patch does?

Sands207 said:
Cool, so from what ive gathered so far im going to make the next rom unrooted but deodexed and we will flash the newest MM gapps first, then dm verity and a reboot to recovery per the directions, then magisk and finally xposed and clear cache and dalvik at the end... sound about right? I did try flashing magisk on my device as is but it failed because the boot image was already patched and stock was needed instead. Is dm verity absolutely needed or could magisk accomplish in theory what our patch does?
Click to expand...
Click to collapse
I think it's better to flash Dm Verity and you would do it before you flash gapps because to flash Dm Verity you have to format data so you can mount the data partition

SonderTech said:
I think it's better to flash Dm Verity and you would do it before you flash gapps because to flash Dm Verity you have to format data so you can mount the data partition
Click to expand...
Click to collapse
ok excellent. I appreciate your help ?
Sent from my SM-J327P using Tapatalk

Sands207 said:
ok excellent. I appreciate your help ?
Click to expand...
Click to collapse
No problem, and when your flashing it on your device just flash stock ROM flash twrp recovery and then do the Dev mode and OEM unlock setup and then wipe data once again flash Dm Verity and clear cache and dalvik and then setup your device and then flash magisk and then wipe cache and dalvik once again

SonderTech said:
No problem, and when your flashing it on your device just flash stock ROM flash twrp recovery and then do the Dev mode and OEM unlock setup and then wipe data once again flash Dm Verity and clear cache and dalvik and then setup your device and then flash magisk and then wipe cache and dalvik once again
Click to expand...
Click to collapse
Excellent. I'll update the OP when i post the second build.

Sands207 said:
Excellent. I'll update the OP when i post the second build.
Click to expand...
Click to collapse
Coolio and if you need a boot animation just pm me. I have a couple zips that need converting and resizing.

SonderTech said:
Coolio and if you need a boot animation just pm me. I have a couple zips that need converting and resizing.
Click to expand...
Click to collapse
Awesome, I just finished the second build. My upload speed is insanely slow so it may take all night for me but i did manage to cut the size down considerably ? im sure there will be stuff to remove still but everyone is different. Definitely about a new boot animation tho stock is pretty blah lol

Sands207 said:
Awesome, I just finished the second build. My upload speed is insanely slow so it may take all night for me but i did manage to cut the size down considerably ? im sure there will be stuff to remove still but everyone is different. Definitely about a new boot animation tho stock is pretty blah lol
Click to expand...
Click to collapse
I have a batman sonar animation I got from bhoot.co.uk that I converted to a QMG for our device, just need to upload it to the drive with the rest of them

Alpha 2 released: https://drive.google.com/folderview?id=0Bz99NuhE3XwmWGN5ejBqMDlNUVU
Will update OP in a few to reflect changes ?

Is it going to be possible to port Lineage OS to this device ?

[Tutorial] Flashing OTA Updates on Unlocked, Rooted Pixel 2 w/o Custom Recovery

PLEASE READ MY IMPORTANT NOTICE ABOUT 8.1 BELOW
See update as well!
Hey, guys! This is my first thread ever, so please give me some grace. (I do not know all the formatting stuff yet)
I decided that because I had to wipe my Pixel 2 XL twice in the process of trying to figure this out, I may as well write a quick tutorial on how to do this the easy (and mostly safe) way.
This is where they all insert the disclaimer:
Code:
This tutoial is based on software I did not write or contribute to in any way, If you have issues with it, contact their respective developers, Google can help with this. DO NOT blame me for your now-a-fancy-paperweight-pixel,
I have diplomatic immunity and will tell you to contact my lawyer who doesn't care. You risk what you risk, take responsibility for that.
Now for the meat....
What you need:
Unlocked bootloader with MAGISK ROOT (other root may work, only tested magisk beta)
The Latest OTA File from the official download page, saved to your device
The Flashfire App by one of the greatest XDA legends of all time, Chainfire
The flashable zips for Magisk and any other stuff you want installed (like a custom kernel) when the update gets flashed (typically magisk modules do not need to be reflashed, they stay installed)
Advisable: nothing that has modified your system partitions (only have systemless mods like magisk)
Now that you're all set:
Open Flashfire and grant it root permissions.
Tap through all the warnings
Hit the plus sign and hit "Flash ZIP or OTA"
Find your stored OTA file you downloaded from the Google OTA page.
Check all three available options, (Auto-mount, Mount system..., and Restore Boot and Recovery)
Repeat step #3 with your newfound ability to flash zips, add a kernel (I use Flash Kernel) and flash the newest official magisk beta the same way. NOTE: Check boxes for these shouldn't need to include "auto-mount" or "restore boot and recovery images"
DISABLE ever-root settings completely from the flash queue.
Click the red lightning button at the bottom left.
Give it up to 5 minutes to do its business.
Reboot and profit.
If that didn't make sense, watch my simple video!!
(there is one mistake in the video, on all other things than the OTA itself, DO NOT check the box for restoring stock boot and recovery)
NOTE: You are unable to flash recoveries through this method, I've tried it and so far no luck. We may be able to later when apps let us flash the boot partition properly but for now, it won't stick.
Credits:
Chainfire for his amazing flashfire app!
Team Pixel for their awesome phone.
XDA for all the years of being awesome.
topjohnwu for magisk badassery
If you should be credited, PM ME.
IMPORTANT NOTICE:
Magisk beta thread clearly states that currently (12/05/2017) Magisk 14.5 with official pixel support is only tested up to 8.0, NOT 8.1 yet. Due to this and the fact that aosp 8.1 is super duper new and most kernels likely don't have an 8.1 version, I'd recommend waiting till this post is updated to flash anything 8.1
UPDATE 12/29/2017: As of now flashfire works for some things on oreo, but Ill need to look into it after we get another Oreo update to see if it can be flashed from there, however this may become obsolete assuming you can just use magisk's new features to do updates the official way. (google it)
That's all, Folks!
If this helped you, SMASH that thanks button! Also, Please try to keep OT stuff to a minimum.
I'll be posting a video soon that shows the flashfire process in a little better detail. Posted it, in the instructions!!

Nice work man. Always nice seeing people share their processes.
Sent from my Pixel 2 XL using Tapatalk

I've done similar ota flash with Flashfire on other devices. Will try this on my Pixel XL 2 with the next ota! Kudos

This method should work to flash the DP2 OTA from november update right?

Triscuit said:
This method should work to flash the DP2 OTA from november update right?
Click to expand...
Click to collapse
As long as the update is a newer one than your current one, is NOT an 8.1 beta, and is a FULL Ota (as in, it's larger than 1gb file) then it should flash. Of note: these are NOT the factory images you find on a very close by page from Google, they have to be the OTA zips.

What do you need to do if you have TWRP installed already? Can you still use this method?

uofirob said:
What do you need to do if you have TWRP installed already? Can you still use this method?
Click to expand...
Click to collapse
From what I remember from my Nexus 6p, having TWRP or Stock recovery made no difference flashing the update in FlashFire. But if you want TWRP installed you'll have to flash it again after the OTA due to the OTA replacing it unless you chose "Restore boot and recovery" during the zip selection process. Eben then I am not 100% sure TWRP will remain.
Sent from my Pixel 2 XL using Tapatalk

Does the OTA with this method delete the userdata partition? Or does it keep personal data intact?

so the magisk "install to Second slot (After OTA)" doesnt work?

FlashFire has not been updated since the Pixel 2 was released. Is it really meant to work with the Pixel 2?

cb474 said:
FlashFire has not been updated since the Pixel 2 was released. Is it really meant to work with the Pixel 2?
Click to expand...
Click to collapse
This is what I'm thinking. I doubt this will work at all. Flashfire is finicky at best. Works great when it works. Has never been updated to work on our device.

rester555 said:
Does the OTA with this method delete the userdata partition? Or does it keep personal data intact?
Click to expand...
Click to collapse
Nope. It updates, just like the title says. No wiping your rear required. Just a clean plop.

JeffBea said:
This is what I'm thinking. I doubt this will work at all. Flashfire is finicky at best. Works great when it works. Has never been updated to work on our device.
Click to expand...
Click to collapse
It fully recognized my device as supported, and the update worked, I have tested it.

thomasamas said:
It fully recognized my device as supported, and the update worked, I have tested it.
Click to expand...
Click to collapse
I'll definitely try this then when December updated hits then. This was my preferred update method on my 6p.

JeffBea said:
I'll definitely try this then when December updated hits then. This was my preferred update method on my 6p.
Click to expand...
Click to collapse
Make sure to check for Magisk and your preferred kernel compatibility with the 8.1 update when it comes. Flashing Magisk when the OS doesn't yet work with it could cause some serious headaches, so check the Magisk thread. I'm sure you know what happens when you flash an incompatible kernel too....
In the case Magisk isn't compatible yet, you can always check for SUPERSU systemless compatibility, and do that instead of flashing Magisk.

linezero said:
so the magisk "install to Second slot (After OTA)" doesnt work?
Click to expand...
Click to collapse
This is what I would like to know as well

For those of us that were on the original pixel phone without a custom recovery, the blow method was always the fastest and easiest way to update without losing root. Anyone tried on the Dec update?
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips

Just tried this method and worked flawlessly.. Thank you OP!
Sent from my Pixel 2 XL using Tapatalk

mrbracht said:
Just tried this method and worked flawlessly.. Thank you OP!
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Did you use this process to upgrade to the release build of 8.1 (Dec update)?

Jexx11 said:
This is what I would like to know as well
Click to expand...
Click to collapse
As far as I know, Magisk 14.5 understands both partitions now, and will flash to BOTH a/b, if you check the script for it, that's what it does. If this isn't what you're looking for, please clarify!

Rooting questions

Just bought my 6T and I have some questions about root:
-Will rooting the 6T wipes internal memory (SD)?
-Can you update OTA while rooted?

Unlocking the boot loader in order to root wipes everything clean. No way around it.
Once rooted I believe you have to apply the full size OTA not the incremental, then make sure to reflash twrp/magisk. See the guides section for details.
Sent from my ONEPLUS A6013 using Tapatalk

My buddy Baker has some kind of b******* as LG but he wants to route help him out

vegetaleb said:
Just bought my 6T and I have some questions about root:
-Will rooting the 6T wipes internal memory (SD)?
-Can you update OTA while rooted?
Click to expand...
Click to collapse
Rooting has no effect.
When you unlock the BL it will wipe the phone.
Once that is done, you don't need to fear wiping the phone when rooting.
You can flash the full OTA on the phone by using "local install".
You cannot take the OTA directly since it is incremental and won't install.
Once you download the full OTA you should install, allow the phone to reboot and install again.
This will install on both A/B partitions.

tech_head said:
Rooting has no effect.
When you unlock the BL it will wipe the phone.
Once that is done, you don't need to fear wiping the phone when rooting.
You can flash the full OTA on the phone by using "local install".
You cannot take the OTA directly since it is incremental and won't install.
Once you download the full OTA you should install, allow the phone to reboot and install again.
This will install on both A/B partitions.
Click to expand...
Click to collapse
thanks
Is there a custom rom based on Oxygen?

vegetaleb said:
thanks
Is there a custom rom based on Oxygen?
Click to expand...
Click to collapse
Don't know.
I run stock OS, TWRP, ElementalX kernel and rooted with Magisk.
I add a few Magisk modules for customization.

tech_head said:
Don't know.
I run stock OS, TWRP, ElementalX kernel and rooted with Magisk.
I add a few Magisk modules for customization.
Click to expand...
Click to collapse
Curious why that kernel instead of stock? Do you get better battery life out of it?

I wonder what the trade-offs of the custom kernel are...

Ok
Any module to have AOD on stock room?

vegetaleb said:
Ok
Any module to have AOD on stock room?
Click to expand...
Click to collapse
Please....
The answer is obvious of you just go in apps section.....

Striatum_bdr said:
Please....
The answer is obvious of you just go in apps section.....
Click to expand...
Click to collapse
It looks like not compatible with 9.0.11

New OP8Pro Owner, Tools and Utilities Questions

Just received my 8 Pro a couple days ago and am reading up before I mod, flash, etc. I see a few tools for fixing things if all doesn't go as planned but many are for Windows. What about things for Linux users? I've been doing this since the DroidX days but switch to using Linux on the host PC because Windows can be flaky.
Things like an unbrick tool procedure, EDL programmer, etc would be nice....
Thanks in Advance
Sent from my IN2025 using Tapatalk

NVM Found it
Sent from my IN2025 using Tapatalk

New question. Are there "preferred" steps to rooting? My last device (P3XL) had me out of the loop for the last 18 months, it was perma-locked.
Now with the 8Pro I want to get back into things. I'm not familiar with Magisk anymore and I've found that TWRP isn't quite ready for install on the device. I've downloaded the Zip, Magisk Manager, and the firmware (OTA file @ 2.3GB, no fastboot file).
Is there a specific process? Install Magisk Manager, Install Magisk from app or zip, flash patched boot image? If just flashing the patched .img is preferred I'll need to use a payload dumper the get the boot.img....
Sound about right?
Sent from my IN2025 using Tapatalk

FernBch said:
New question. Are there "preferred" steps to rooting? My last device (P3XL) had me out of the loop for the last 18 months, it was perma-locked.
Now with the 8Pro I want to get back into things. I'm not familiar with Magisk anymore and I've found that TWRP isn't quite ready for install on the device. I've downloaded the Zip, Magisk Manager, and the firmware (OTA file @ 2.3GB, no fastboot file).
Is there a specific process? Install Magisk Manager, Install Magisk from app or zip, flash patched boot image? If just flashing the patched .img is preferred I'll need to use a payload dumper the get the boot.img....
Sound about right?
Click to expand...
Click to collapse
IMO easiest is just to boot twrp (not install) and from there flash magisk. Thats it. Sure you need to unlock bootloader first..

pyry666 said:
IMO easiest is just to boot twrp (not install) and from there flash magisk. Thats it. Sure you need to unlock bootloader first..
Click to expand...
Click to collapse
Thanks. Unlocked as soon as it came out of the box. Just wanted to double check. I'm almost a little behind..... Lol
Sent from my IN2025 using Tapatalk

pyry666 said:
IMO easiest is just to boot twrp (not install) and from there flash magisk. Thats it. Sure you need to unlock bootloader first..
Click to expand...
Click to collapse
After getting set up, I would go with latest TWRP, which handles most partition backups except system. Having data and other partition backups can save the day if you're messing around and blow up your setup.

gaww said:
After getting set up, I would go with latest TWRP, which handles most partition backups except system. Having data and other partition backups can save the day if you're messing around and blow up your setup.
Click to expand...
Click to collapse
Thanks, pulled this from the 8 Pro forums.
twrp-3.4.0-2-instantnoodle-unified-mauronofrio.img
Unless TiBu is broken that's my usual backup method....
Sent from my IN2025 using Tapatalk

Download Magisk Manager - check.
Download Firmware - check.
Update Linux and Python - check.
Install Package Dumper - check.
Install Protobuf - check.
Pull boot.img - check.
Patch boot.img - check.
Flash boot.img - check.
We have Root!!!!!!
Backup current boot.img - check.
Backup Everything - check!!!!
Now to find a kernel/ROM I like.......
Does Viper4Android work?
Sent from my IN2025 using Tapatalk

FernBch said:
Download Magisk Manager - check.
Download Firmware - check.
Update Linux and Python - check.
Install Package Dumper - check.
Install Protobuf - check.
Pull boot.img - check.
Patch boot.img - check.
Flash boot.img - check.
We have Root!!!!!!
Backup current boot.img - check.
Backup Everything - check!!!!
Now to find a kernel/ROM I like.......
Does Viper4Android work?
Click to expand...
Click to collapse
Yes it does..
Currently using it on xXx no limits
Currently a thread about it.

dladz said:
Yes it does..
Currently using it on xXx no limits
Currently a thread about it.
Click to expand...
Click to collapse
Thanks. Been out of the loop for a while. Installed V4A already. Been checking out the kernels but haven't tried xXx yet. How is it? I'm still on stock (10.5.13 IN11AA) but may go to a custom ROM. Stock is nice but I prefer a more plain vanilla like AOSP. There's so much stuff I'll never use..........
Sent from my IN2025 using Tapatalk

FernBch said:
Thanks. Been out of the loop for a while. Installed V4A already. Been checking out the kernels but haven't tried xXx yet. How is it? I'm still on stock (10.5.13 IN11AA) but may go to a custom ROM. Stock is nice but I prefer a more plain vanilla like AOSP. There's so much stuff I'll never use..........
Click to expand...
Click to collapse
Tbh it's really good. All the tweaks and debloating options you'd expect, I can't fault it.
Zram off is a big one for me, forced 120hz mode.. im impressed by what you can get done with a Magisk ROM