Database Develop

How to install ElementalX Kernel

I'm a newbie and my phone is at Marshmallow 6.0.1, rooted with Nexus Root Toolkit su (with SuperSU 2.62)
later flashed twrp, now want to install ElementalX Kernel.
Do I need to unroot the system, and then flash the kernel with twrp?
thanks in advance.

The kernel is the boot.img. Just flash it via TWRP and it will automatically be present.

And why do you specifically want to install Elementalx? If you've got a working rooted phone, why continue to mess with it? Continual unnecessary tweaking is the sure way to end up with a glass-and-metal paperweight...

daddylok said:
I'm a newbie and my phone is at Marshmallow 6.0.1, rooted with Nexus Root Toolkit su (with SuperSU 2.62)
later flashed twrp, now want to install ElementalX Kernel.
Do I need to unroot the system, and then flash the kernel with twrp?
thanks in advance.
Click to expand...
Click to collapse
Better flash superSU2.65.zip (latest atm).

Not necessarily better. Versions after 2.62 have a number of comments across various threads saying that root doesn't work for them. 2.62 uses a different method from the later versions. 2.62 works fine for me and (from the silence in the forums) for most people, so upgrading to 2.64/2.65 is probably taking an unnecessary risk.
And again, why try to install a different kernel on a working rooted device? It makes no sense to me unless there's an amazing function that will make a discernable difference, and personally I don't believe that any kernel makes that much of a difference in real-life normal usage.

dahawthorne said:
personally I don't believe that any kernel makes that much of a difference in real-life normal usage.
Click to expand...
Click to collapse
Not something i'd agree with since CPU governors and I/O schedulers can make allot of difference to "real life normal usage", obviously this depends on what the developer impliments and user choice.

there are times that I'll run elementalx kernel, but I ALWAYS change the governor and scheduler. always. as I can't stand the way that its set up. personally, I always use ondemand with deadline :angel:

daddylok said:
I'm a newbie and my phone is at Marshmallow 6.0.1, rooted with Nexus Root Toolkit su (with SuperSU 2.62)
later flashed twrp, now want to install ElementalX Kernel.
Do I need to unroot the system, and then flash the kernel with twrp?
thanks in advance.
Click to expand...
Click to collapse
Wondering how you achieved root.I am unable using the stock kernel.TWRP installed just fine.Do you mind sharing your procedure?

Download SuperSU v2.62-3 (you can try later versions, but some people have reported that they don't work for them - v2.62 works fine for me and many others). http://forum.xda-developers.com/showpost.php?p=64161125
Copy the zip file to a folder in your Nexus 6 - say, Downloads, it doesn't really matter which one.
Boot into TWRP. Press Install. Navigate to the folder where the SuperSU zip file is and select it. Swipe in TWRP to install it. DO NOT accept any offer from TWRP to root your device (again) - you'll break it. Once installed, just reboot system. Done.

To install elementalx, just flash in recovery.
dahawthorne said:
And why do you specifically want to install Elementalx? If you've got a working rooted phone, why continue to mess with it? Continual unnecessary tweaking is the sure way to end up with a glass-and-metal paperweight...
Click to expand...
Click to collapse
Silliness. Why are you even on xda with that attitude? He probably wants to install it so he can use some of the added features and enhancements.

"Why are you even on xda with that attitude?" Ditto. We're all entitled to our opinions, and my opinion is that a lot of noobs do stuff just to see what happens, and the result is that they're in forums asking after the event "How do I fix this?" rather than "How do I do this?", and in both cases without any particular need or reason or understanding of what they want. And this is a typical thread - an admitted noob wants to install a specific kernel, and still hasn't said why (though he/she has thanked me, which I appreciate ). I think that to warn noobs about unnecessary tinkering is doing them a service - isn't that why we all respond to questions?

dahawthorne said:
Download SuperSU v2.62-3 (you can try later versions, but some people have reported that they don't work for them - v2.62 works fine for me and many others). http://forum.xda-developers.com/showpost.php?p=64161125
Copy the zip file to a folder in your Nexus 6 - say, Downloads, it doesn't really matter which one.
Boot into TWRP. Press Install. Navigate to the folder where the SuperSU zip file is and select it. Swipe in TWRP to install it. DO NOT accept any offer from TWRP to root your device (again) - you'll break it. Once installed, just reboot system. Done.
Click to expand...
Click to collapse
Thanks very much -so to be clear that was with the Stock kernel?
I am running 3.10.40-g557ba38
Trying to avoid a brick situation,sorry to be a bother..

Yes, stock kernel. As I understand it, the SuperSU backs up and replaces the stock kernel (as part of the boot image) and will restore it if you unroot. You just need to follow the instructions as written - it's exactly what I did on my stock 6.0.1 ROM.

Awesome thanks again.

dahawthorne said:
Yes, stock kernel. As I understand it, the SuperSU backs up and replaces the stock kernel (as part of the boot image) and will restore it if you unroot. You just need to follow the instructions as written - it's exactly what I did on my stock 6.0.1 ROM.
Click to expand...
Click to collapse
Thanks again-this worked out perfectly and I am running Cyanide which has made me very happy so far.REALLY fast and smooth.Everything working great so far.Loving my N6- who needs Samsung! I just had to edit the .xml file for the Music volume other than that the ROM seems about perfect.

[Help] Explain systemless Root

Hello. Please be gentle. I'm new to Systemless Root and need some clarification. I've done a lot of reading about it but still need some info. Im not bashing anything or anyone, I'm not trying to be a wise ass, I'm genuinely confused. From the vague installation process I read somewhere it seems that u already need to be Rooted with TWRP installed to install Systemless Root. Right? So what's the point of rerooting a phone thats already rooted? I would think it would be more useful to have it as another root method. So we can start off Locked and Unrooted, then use Systemless to root. Currently my N6 is locked and Unrooted because I have no use for Root at the moment yet all of my previous Android phones have been unlocked and rooted. Please explain to me what I'm missing here. Thanks guys. Happy New Year to u.

TokedUp said:
Hello. Please be gentle. I'm new to Systemless Root and need some clarification. I've done a lot of reading about it but still need some info. Im not bashing anything or anyone, I'm not trying to be a wise ass, I'm genuinely confused. From the vague installation process I read somewhere it seems that u already need to be Rooted with TWRP installed to install Systemless Root. Right? So what's the point of rerooting a phone thats already rooted? I would think it would be more useful to have it as another root method. So we can start off Locked and Unrooted, then use Systemless to root. Currently my N6 is locked and Unrooted because I have no use for Root at the moment yet all of my previous Android phones have been unlocked and rooted. Please explain to me what I'm missing here. Thanks guys. Happy New Year to u.
Click to expand...
Click to collapse
Read this http://forum.xda-developers.com/showpost.php?p=63197935&postcount=2 and this http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344 for starters. BTW Google is your friend and you can`t be rooted to use systemless root and obtain root.

I'm probably a lot less experienced than gee2012 and many others in the forum, but here's my very high-level understanding. I hope that the more knowledgeable members can add to or correct this as necessary.
First, you need to unlock the device (fastboot oem unlock), since you can't do much with a locked device. Not only that, but time and time again I've read pleas from users saying "My device is bricked and I didn't unlock it so I can't now enable developer options" - the responses have been generally "Sorry, you're stuffed then, send it back". Unlocking wipes the device, so make backups of whatever essential data you have.
You don't need to install TWRP permanently in order to root. I myself (after asking members for advice) temporarily booted into TWRP (fastboot boot twrp.img - when you reboot from TWRP it disappears and you're back to stock recovery). While TWRP is temporarily running, you can use it to install SuperSU.
The benefit of the new SuperSU (and also doitright's systemless root method) is that it maintains a stock system image, so in theory you have the benefits of superuser root but you can still get OTA updates, which are now much more frequent because of the security amendments. Chainfire (the SuperSU creator) says that he was able to install an OTA after having used the SuperSU unroot function, though he then had to re-root.
Hope this helps - and that it's correct...

dahawthorne said:
I'm probably a lot less experienced than gee2012 and many others in the forum, but here's my very high-level understanding. I hope that the more knowledgeable members can add to or correct this as necessary.
First, you need to unlock the device (fastboot oem unlock), since you can't do much with a locked device. Not only that, but time and time again I've read pleas from users saying "My device is bricked and I didn't unlock it so I can't now enable developer options" - the responses have been generally "Sorry, you're stuffed then, send it back". Unlocking wipes the device, so make backups of whatever essential data you have.
You don't need to install TWRP permanently in order to root. I myself (after asking members for advice) temporarily booted into TWRP (fastboot boot twrp.img - when you reboot from TWRP it disappears and you're back to stock recovery). While TWRP is temporarily running, you can use it to install SuperSU.
The benefit of the new SuperSU (and also doitright's systemless root method) is that it maintains a stock system image, so in theory you have the benefits of superuser root but you can still get OTA updates, which are now much more frequent because of the security amendments. Chainfire (the SuperSU creator) says that he was able to install an OTA after having used the SuperSU unroot function, though he then had to re-root.
Hope this helps - and that it's correct...
Click to expand...
Click to collapse
Thanks man. That makes certain things more understandable. The thing I still don't understand is the actual install process. I'm am stock, so ur saying I would just have to unlock BL then temp flash TWRP to flash the SU zip? If not what are the exact steps for installing?
BTW I'm on 6.0.1 MMB29K

TokedUp said:
Thanks man. That makes certain things more understandable. The thing I still don't understand is the actual install process. I'm am stock, so ur saying I would just have to unlock BL then temp flash TWRP to flash the SU zip? If not what are the exact steps for installing?
BTW I'm on 6.0.1 MMB29K
Click to expand...
Click to collapse
- Enable OEM UNLOCK in developer options and enable usb debugging
- Unlock the bootloader
- Reboot
- Flash TWRP (2.8.7.1 is the lastest afaik)
- Message by TWRP to modify the system, click no
- optional: If you format data you decrypt the phone (will wipe all files completely), reboot after if you choose to do so
- In TWRP flash the latest systemless superSU.zip (2.66) zip, link http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
- TWRP will say you`re not rooted, ignore it
- Reboot
- Install BusyBox from Play and you`re done.

gee2012 said:
- Enable OEM UNLOCK in developer options and enable usb debugging
- Unlock the bootloader
- Reboot
- Flash TWRP (2.8.7.1 is the lastest afaik)
- Message by TWRP to modify the system, click no
- optional: If you format data you decrypt the phone (will wipe all files completely), reboot after if you choose to do so
- In TWRP flash the latest systemless superSU.zip (2.66) zip, link http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
- TWRP will say you`re not rooted, ignore it
- Reboot
- Install BusyBox from Play and you`re done.
Click to expand...
Click to collapse
I don't want to be that guy but USB debugging is not needed to unlock the BL,it is only needed while in Android os

holeindalip said:
I don't want to be that guy but USB debugging is not needed to unlock the BL,it is only needed while in Android os
Click to expand...
Click to collapse
True, but i always enable it by default

gee2012 said:
- Enable OEM UNLOCK in developer options and enable usb debugging
- Unlock the bootloader
- Reboot
- Flash TWRP (2.8.7.1 is the lastest afaik)
- Message by TWRP to modify the system, click no
- optional: If you format data you decrypt the phone (will wipe all files completely), reboot after if you choose to do so
- In TWRP flash the latest systemless superSU.zip (2.66) zip, link http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
- TWRP will say you`re not rooted, ignore it
- Reboot
- Install BusyBox from Play and you`re done.
Click to expand...
Click to collapse
Thank you so much!

TokedUp said:
Thank you so much!
Click to expand...
Click to collapse
Tip: instead of flashing TWRP you can also boot it up ( fastboot boot nametwrp.img) to flash zip files and keep your stock recovery if you want to.

@gee2012 - "Install BusyBox from Play and you`re done"
I still don't get what exactly Busybox offers. I've been running fine on Marshmallow for several months without it. I installed it once because it was suggested as a fix for the constant nagging of AutomateIt Pro to reboot, and it made no difference, so I uninstalled it again.
Can you (or anyone) give me specific examples if where it actually makes a difference? Which functions won't work without it? I haven't come across any yet as far as I know.

Busybox is the space efficient way of the basic Unix commands like ln, pwd, chown, chmod, etc. So all apps that want to do some low level file system dabbling, like Android terminal, Titanium backup, or Linux installs, they need it. https://en.wikipedia.org/wiki/BusyBox
From Marshmallow, Android now uses toybox instead by default, which is quite the same, with a little different licensing. It's also in the AOSP source, so all user built AOSP roms already have toybox, so there's no need for busybox to install.

dahawthorne said:
@gee2012 - "Install BusyBox from Play and you`re done"
I still don't get what exactly Busybox offers. I've been running fine on Marshmallow for several months without it. I installed it once because it was suggested as a fix for the constant nagging of AutomateIt Pro to reboot, and it made no difference, so I uninstalled it again.
Can you (or anyone) give me specific examples if where it actually makes a difference? Which functions won't work without it? I haven't come across any yet as far as I know.
Click to expand...
Click to collapse
Apps like Rom Toolbox Pro, Franco Kernel Updater and Kernel Adiutor and lots of other application like Xposed framework (and its modules) and most (if not all) of the custom roms will not work (correctly) without BusyBox. All custom roms anyway have a BusyBox version by default installed Busybox https://en.wikipedia.org/wiki/BusyBox and https://www.google.nl/url?sa=t&rct=...6Z0ltw&usg=AFQjCNG-nKYoEI3kiDm4pgtRWbXFRTpI6A for instance.
Its an essential app for when you are rooted and want to do more with your phone and its not smart to not install it

Thanks, both. I like istperson's comment best : "there's no need for busybox to install." That would be why I haven't seen any negative impact from not having Busybox then. Still, money well spent to help development...

[GUIDE] Installing OxygenOS on Chinese models, easy rooting guide and much more!

Ok so I've seen a lot of confusion on how to correctly flash OxygenOS on your brand new OnePlus 5, and also how to correctly and easily root your phone.. This guide aims to clear up any confusion regarding this. Ready? Let's move on.
Q: What's the difference between International and Chinese versions of the OnePlus 5?
A: Hardware-wise there is absolutely no difference between the 2 versions. In terms of software, the international version runs OxygenOS (OOS) while the Chinese version runs HydrogenOS(H2OS). H2OS has no Google services pre-installed and is generally not recommended for use outside China. Both OxygenOS and HydrogenOS are official updates by OnePlus.
Q: I bought a Chinese phone. How do I install OxygenOS then?
A: 1. Download the latest OxygenOS from here. Download the full zip and NOT the OTA update.
2. Place it in the root of your internal memory. Basically don't put the file in any folder.
3. Go to Settings > System updates, press the gear icon and select Local upgrade.
4. Choose the file, the phone will boot into recovery and everything is done.
Q: OK I want to root my phone but I don't want to lose Android Pay, Netflix, Pokemon GO etc. Is it possible?
Simple answer: Yes. Long answer: Maybe not in the long run.
Why is that so? You see, back in the old days there were little downsides to rooting. Alas, Android Pay and Pokemon GO came along, and in an effort to tighten up security, Google implemented this thing called
SafetyNet. Basically it's a measure to test your system integrity, meaning that any modification to system will trigger SafetyNet and many apps will be "locked down". Android Pay and Pokemon GO will not work,
and Netflix won't show up on Google Play anymore. Some devices even check for unlocked bootloader, but apparently not the OnePlus 5, so you don't have to switch to a custom kernel to root.
To overcome this problem, the brilliant minds at XDA came up with system-less root. Chainfire was the first to implement it in SuperSU, but right now nobody uses SuperSU anymore. Magisk is the new kid in town,
and quite frankly much better IMO.
Q: Alright enough talk, how do I root the phone?
A: Patience my young Padawan. I will get to that in a moment. But here are some things you have to know.
1. Rooting involves unlocking your bootloader, and ALL YOUR DATA WILL BE WIPED. Keep a backup and move everything in your internal memory somewhere else.
2. Magisk may beat SafetyNet now, but there is no guarantee this will always be the case. So your SafetyNet enabled apps may not work all the time.
3. OTA updates from OnePlus will work differently when you are rooted. But hey that's what this guide is for. :good:
Easy rooting guide
1. Install ADB drivers.
2. Go into settings > about phone. Press the build no. a few times to activate developer options.
3. Turn on developer options, OEM unlocking and USB debugging.
4. Connect phone to PC and allow ADB access on phone. Wait for drivers to finish installing.
5. Download and install this simple tool on your PC.
6. Download one of the 2 TWRP recoveries below.
TWRP Official
xdvs23's TWRP
7. Open the All-in-One tool and make sure your device is recognised as OnePlus 5. Click on Unlock bootloader. Your bootloader is now unlocked and all your DATA WILL BE WIPED!
8. Select the "and boot it" arrow and click flash TWRP, click manual mode and choose the TWRP.img file you downloaded earlier.
9. After everything is done, your phone should now boot into TWRP successfully. Do not reboot yet.
10. On your PC, download the latest version of Magisk. Place the zip file onto your phone using USB and flash it with TWRP. Clear cache and reboot into system.
11. You should now see a new app called Magisk Manager. Check for updates!
12. However, do keep in mind not to mess around the system. If you need something, check to see if there any Magisk Modules available. There is also a small repo in the downloads section in Magisk Manager. Also Adaway works great with Magisk. Just make sure to turn on systemless host file in Magisk manager.
14. Congrats you are now rooted!:highfive:
Q: Alright now that I'm rooted, how do I get official updates?
A: 1. Download the latest OxygenOS from here. Download the full zip and NOT the OTA update. Place it on your phone. Make sure you also have your Magisk zip.
2. Boot into TWRP. Press the volume button when the bootloader unlocked screen comes up. Use volume buttons and power button to select recovery.
3. Flash the OxygenOS zip file. DO NOT reboot yet!
4. Tap the home button and flash Magisk. Clear cache.
5. Reboot into system and you are done!
Hope this guide is simple enough for you guys to understand. It might seem daunting at first, but practice makes perfect.
Also it is not a requirement to root, most people get by fine without ever rooting. But we are not like normal people, are we? Why else would we be on XDA then?
Further questions
Q1: Why Magisk and not SuperSU?
A: Besides the fact that Magisk is being constantly updated to bypass SafetyNet, it is also open-source. Wish I could say the same for SuperSU, the app is not what it used to be. Chainfire is no longer aware of the changes made in his app and I for one am not willing to take my chances with a shady developer. I had countless bad experiences with Chinese apps, many of them created by large companies. Check out this thread for more info.
Q2: Why exactly is HydrogenOS not recommended for use outside China?
A: Besides the aforementioned lack of Google apps, HydrogenOS is also tweaked differently from OxygenOS. It is significantly more aggressive in killing apps and not letting them run in the background, as you would expect with the number of rogue apps in China, made worse by the fact that there is no Play Store in China. OxygenOS on the other hand has a limit of 32 apps in memory, which I guess is a nice compromise between performance and battery life.

Reserved just in case. Probably will never need it though.

to be fair, there are still lots of people using SuperSU..

What should I do if I still want to use SuperSU?

2 noob questions @jasonwsc or anyone who knows
How about wiping dalvik and cache?
And how about encryption? Do I need to remove my fingerprint/security pattern before flashing OR rooting?
Thanks a lot for your help, the OP5 will be the first phone I can actually root. My old Xperia Z (2013) had a locked bootloader that was not unlockable haha.

ipredatorv said:
2 noob questions @jasonwsc or anyone who knows
How about wiping dalvik and cache?
And how about encryption? Do I need to remove my fingerprint/security pattern before flashing OR rooting?
Thanks a lot for your help, the OP5 will be the first phone I can actually root. My old Xperia Z (2013) had a locked bootloader that was not unlockable haha.
Click to expand...
Click to collapse
Wiping Dalvik and cache is usually done after flashing a ROM in TWRP. Not that big of deal now that many apps use ART, but still good to do to prevent app crashes.
No need to remove fingerprint security before rooting.

iamelton said:
to be fair, there are still lots of people using SuperSU..
Click to expand...
Click to collapse
Ningyou Higeki said:
What should I do if I still want to use SuperSU?
Click to expand...
Click to collapse
Just flash SuperSU zip instead of Magisk.
I don't know why anyone still uses SuperSU though. For one, it's sold to a Chinese company and is no longer open source. Not to mention it doesn't pass SafetyNet at all.

jasonwsc said:
Wiping Dalvik and cache is usually done after flashing a ROM in TWRP. Not that big of deal now that many apps use ART, but still good to do to prevent app crashes.
No need to remove fingerprint security before rooting.
Click to expand...
Click to collapse
Thanks for the clarification!
I only asked about wiping dalvik/cache because some other people here recommended that, as it may help to fix my battery drain issue.
Sent from my ONEPLUS A5000 using Tapatalk

ipredatorv said:
Thanks for the clarification!
I only asked about wiping dalvik/cache because some other people here recommended that, as it may help to fix my battery drain issue.
Sent from my ONEPLUS A5000 using Tapatalk
Click to expand...
Click to collapse
It might help with your battery drain issue, but chances are some apps are running in the background draining your battery.

Google services not working
I have installed oxygen OS in my chinese version OP5 following above method. However, after installing oxygen OS my google play store isnt working. When I open google play store, it stucks on checking info.

Nishatian1 said:
I have installed oxygen OS in my chinese version OP5 following above method. However, after installing oxygen OS my google play store isnt working. When I open google play store, it stucks on checking info.
Click to expand...
Click to collapse
Just a wild guess, but are you still in China? Check your VPN before trying to access the Google Playstore. Otherwise, remove the Playstore and download the most recent Playstore apk from a website like apkmirror. If they offer multiple versions, go for ARM 64.
Sent from my ONEPLUS A5000 using Tapatalk

jasonwsc said:
Just flash SuperSU zip instead of Magisk.
I don't know why anyone still uses SuperSU though. For one, it's sold to a Chinese company and is no longer open source. Not to mention it doesn't pass SafetyNet at all.
Click to expand...
Click to collapse
I'm a little tired of tuning my phone now. And I don't care about SafetyNet. BTW, how's Magisk's compatibility now?

jasonwsc said:
Just flash SuperSU zip instead of Magisk.
I don't know why anyone still uses SuperSU though. For one, it's sold to a Chinese company and is no longer open source. Not to mention it doesn't pass SafetyNet at all.
Click to expand...
Click to collapse
I got my Chinese OP5 two days ago and went through the whole procedure of unlocking, rooting, and flashing OxygenOS. Now I see that somebody took the time to write a nice guide on how to do it. Thanks @jasonwsc! I really wish I had this available to me already. I am sure it's gonna be a great help to others though!
I wasn't aware that SuperSU had been sold to a Chinese company through and that it is no longer open source. Knowing what I know now I regret flashing SuperSU yesterday and would love to switch to Magisk.
My question would be: what's the "proper way" to switch from SuperSU to Magisk? Just unroot via SuperSU and flash Magisk, or is there a better, cleaner way?
Edit:
Nevermind, just searched it and there's a super nice guide here.

Ningyou Higeki said:
I'm a little tired of tuning my phone now. And I don't care about SafetyNet. BTW, how's Magisk's compatibility now?
Click to expand...
Click to collapse
Magisk works fine, have no issues so far.

Hello,
I have the opportunity to receive an OP5T (128 GB)
from China. The ROM will be Hydrogen OS and not Oxygen OS.
I would like to be sure that the procedure used to install Oxygen OS will be the same as for the OP5?

Moazamali said:
Hello,
I have the opportunity to receive an OP5T (128 GB)
from China. The ROM will be Hydrogen OS and not Oxygen OS.
I would like to be sure that the procedure used to install Oxygen OS will be the same as for the OP5?
Click to expand...
Click to collapse
Yes it's the same. Just flash the firmware file for OP5T instead of the OP5.

i have international model oneplus 5. My phone was bricked, so i unbricked the phone by flashing h2os. I have rooted my phone with supersu and unrooted it again by flashing stock recovery. i want to now flash my phone with oxygenos. i have tried but no success. Please guide me with correct method.
Thanks

nayemohd said:
i have international model oneplus 5. My phone was bricked, so i unbricked the phone by flashing h2os. I have rooted my phone with supersu and unrooted it again by flashing stock recovery. i want to now flash my phone with oxygenos. i have tried but no success. Please guide me with correct method.
Thanks
Click to expand...
Click to collapse
See here https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003 it might be useful to format internal storage.

strongst said:
See here https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003 it might be useful to format internal storage.
Click to expand...
Click to collapse
Good morning all,
I have the same problem. Installed a H2os on a international oneplus 5.
Didn't like it so much so I formatted the system and installed the open beta 26.
However if I want to use the latest recovery either to clear cache or davlik cache I get a bunch of errors.
Any idea why?

kimon60 said:
Good morning all,
I have the same problem. Installed a H2os on a international oneplus 5.
Didn't like it so much so I formatted the system and installed the open beta 26.
However if I want to use the latest recovery either to clear cache or davlik cache I get a bunch of errors.
Any idea why?
Click to expand...
Click to collapse
Which h2os version and which recovery version did you use(file names please)? What do you mean with formatting the system? What did you wipe or format exactly?

Downgrade with patched image

I installed Magisk with a patched image on a Pixel 4. This process appears to always patch boot.img with the latest version of Magisk. Is there any way to patch an image with an old version of Magisk? Specifically I'd like to install 21.2 (coming from 21.4).
If not, I assume I need to install a custom recovery to downgrade to an older version?

I'm assuming you mean that you want to downgrade from 21.4 to 21.2. You have a couple of possibilities actually.
You could setup your own custom update channel with the Magisk zip of your choice. I've described that here:
https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-84290797
But since you want to use the stable releases you can find the old update channel in Github's commit history. It takes a little bit of insight into how Github works though... I've had plans to write down the steps required in my Magisk guide for ages, but somehow I never get around to it.
Using this as your custom update channel would give you Magisk v21.2:
https://raw.githubusercontent.com/topjohnwu/magisk_files/d10a630a4d4a3c54cf57abc7411f698f0ff79161/stable.json
If you want to use TWRP you do not need to install it though. It's perfectly possible to boot TWRP without having to install it:
fastboot boot twrp.img
Keep in mind that no official support is given for old releases...

Excellent. That worked!
I ask as the instructions seem to imply that installing from recovery is a thing of the past. Is that just for certain devices?
Any difference with using the custom channel to do a direct install vs patch for downgrades?

amw2320 said:
Excellent. That worked!
I ask as the instructions seem to imply that installing from recovery is a thing of the past. Is that just for certain devices?
Any difference with using the custom channel to do a direct install vs patch for downgrades?
Click to expand...
Click to collapse
If there is a custom recovery available for your device it's very often a viable option for installation. But, as it says in the instructions, it may fail and patching the image may be your only option. Boot image patching or the direct install option are the recommended methods (since there it's possible for @topjohnwu to control exactly what's going on).
Once you have Magisk installed already it's generally recommended to use the direct install option, but since Android is Android and there are way too many different setups out there to even count there is going to be instances where the direct install fails and patching a boot image is needed, or even that installing through recovery is the only option.
There's no practical difference between direct install and patching the image manually. The only difference is in who's doing the flashing of the image (you or the Manager).
You've got a Pixel device, so you should be good on all accounts. @topjohnwu uses his Pixel devices to test a lot of stuff with Magisk and they'll pretty much always be fully supported.

Thanks, super useful

Question Updating after root

I have my pixel 7 rooted and I cannot get automatic updates. What would be the best way for me to get updates on my system? Going by the name I'd guess the pixelflasher is used, but I honestly just don't want to brick my Christmas gift so I'm asking for any guidance I can get.

scuzzo500 said:
I have my pixel 7 rooted and I cannot get automatic updates. What would be the best way for me to get updates on my system? Going by the name I'd guess the pixelflasher is used, but I honestly just don't want to brick my Christmas gift so I'm asking for any guidance I can get.
Click to expand...
Click to collapse
You can update any way you want. You might find sideloading the OTA to be easiest.
The only way you can "accidentally" brick your device is if you break the bootloader by flashing the wrong image...but if you're not sure what that means, you probably shouldn't be attempting this anyway.

.

I'm pretty familiar with rooting and updating. If you look at my post history you can verify I've been working with root since Droid x2. I'm currently typing this on a one plus 7 pro I converted to gm1925. However, each platform has its specific issues and every new version of Android can be different. I don't have twrp to backup and I want to make sure I don't brick what, to me, is a significant financial investment. I'm just asking to understand what other individuals feel is best practices.

scuzzo500 said:
I'm pretty familiar with rooting and updating. If you look at my post history you can verify I've been working with root since Droid x2. I'm currently typing this on a one plus 7 pro I converted to gm1925. However, each platform has its specific issues and every new version of Android can be different. I don't have twrp to backup and I want to make sure I don't brick what, to me, is a significant financial investment. I'm just asking to understand what other individuals feel is best practices.
Click to expand...
Click to collapse
I personally update using PixelFlasher and the factory image each month. Others prefer sideloading the OTA. Yet others restore the boot image and take automatic OTAs.
It's completely up to you. Again, the only way you'll brick your device is by doing something stupid such as flashing the wrong image to the bootloader partition. As long as the bootloader functions and you can interact with the device via ADB, it's not bricked and is recoverable

V0latyle said:
I personally update using PixelFlasher and the factory image each month. Others prefer sideloading the OTA. Yet others restore the boot image and take automatic OTAs.
It's completely up to you. Again, the only way you'll brick your device is by doing something stupid such as flashing the wrong image to the bootloader partition. As long as the bootloader functions and you can interact with the device via ADB, it's
Click to expand...
Click to collapse

I still haven't put the phone into regular use because I want to make sure I can keep root while updating. I just cannot stand ads. I'll start reading up on pixelflasher and get a good feel for it. Thank you for the help.

I definitely bet on Pixelflasher. It is idiotproof and very handy.

I like sideloading OTA's when I'm stock. A couple commands from any device with current platform tools and it's done. It's also arguably the documented "Google way". Different strokes for different folks I guess...

Thank you to everyone. I've muddled through pixel flasher and I have updated to TD1A.221105.001. Now I'll jump in the pixelflash thread and ask a few questions.

H
scuzzo500 said:
I have my pixel 7 rooted and I cannot get automatic updates. What would be the best way for me to get updates on my system? Going by the name I'd guess the pixelflasher is used, but I honestly just don't want to brick my Christmas gift so I'm asking for any guidance I can get.
Click to expand...
Click to collapse
I have just updated mine without problems:
1.Open magisk an disable modules.
2.Press uninstall magisk - restore images (DO NOT REBOOT)
4.Install the ota in settings.
5. IMPORTANT, once finished DO NOT REBOOT, open magisk again and press install- (install to inactive slot (after OTA).
Then reboot and open magisk to enable the modules again. (maybe this is not necessary, to disable and enable, but it´s safer.
NOTE: I have done this with december update, for unknown reason it was impossible to me with november. I that case i had to complete uninstall magisk, use pixel flasher and then flash init_boot
patched again.

oscarcam said:
H
I have just updated mine without problems:
1.Open magisk an disable modules.
2.Press uninstall magisk - restore images (DO NOT REBOOT)
4.Install the ota in settings.
5. IMPORTANT, once finished DO NOT REBOOT, open magisk again and press install- (install to inactive slot (after OTA).
Then reboot and open magisk to enable the modules again. (maybe this is not necessary, to disable and enable, but it´s safer.
NOTE: I have done this with december update, for unknown reason it was impossible to me with november. I that case i had to complete uninstall magisk, use pixel flasher and then flash init_boot
patched again.
Click to expand...
Click to collapse
There is no problem if you install the last update without having installed the previous updates?

alsansan said:
There is no problem if you install the last update without having installed the previous updates?
Click to expand...
Click to collapse
If It's an OTA, i supose there is no problem. If the system gives you the option. Otherwise you can avoid previous justo using flasher. If you keep your init_boot patched It's easy to root again once used the flasher.

oscarcam said:
H
I have just updated mine without problems:
1.Open magisk an disable modules.
2.Press uninstall magisk - restore images (DO NOT REBOOT)
4.Install the ota in settings.
5. IMPORTANT, once finished DO NOT REBOOT, open magisk again and press install- (install to inactive slot (after OTA).
Then reboot and open magisk to enable the modules again. (maybe this is not necessary, to disable and enable, but it´s safer.
NOTE: I have done this with december update, for unknown reason it was impossible to me with november. I that case i had to complete uninstall magisk, use pixel flasher and then flash init_boot
patched again.
Click to expand...
Click to collapse
Just followed your instructions and it worked flawlessly. I totally forgot this and figured I would need to reflash each time.

oscarcam said:
H
I have just updated mine without problems:
1.Open magisk an disable modules.
2.Press uninstall magisk - restore images (DO NOT REBOOT)
4.Install the ota in settings.
5. IMPORTANT, once finished DO NOT REBOOT, open magisk again and press install- (install to inactive slot (after OTA).
Then reboot and open magisk to enable the modules again. (maybe this is not necessary, to disable and enable, but it´s safer.
NOTE: I have done this with december update, for unknown reason it was impossible to me with november. I that case i had to complete uninstall magisk, use pixel flasher and then flash init_boot
patched again.
Click to expand...
Click to collapse
Followed your steps. It was easy and worked well.
Thank you

scuzzo500 said:
I still haven't put the phone into regular use because I want to make sure I can keep root while updating. I just cannot stand ads. I'll start reading up on pixelflasher and get a good feel for it. Thank you for the help.
Click to expand...
Click to collapse
I don't understand rooting the phone just to block ads.
Just use Adguard which surpasses any root adblocking abilities.

oscarcam said:
H
I have just updated mine without problems:
1.Open magisk an disable modules.
2.Press uninstall magisk - restore images (DO NOT REBOOT)
4.Install the ota in settings.
5. IMPORTANT, once finished DO NOT REBOOT, open magisk again and press install- (install to inactive slot (after OTA).
Then reboot and open magisk to enable the modules again. (maybe this is not necessary, to disable and enable, but it´s safer.
NOTE: I have done this with december update, for unknown reason it was impossible to me with november. I that case i had to complete uninstall magisk, use pixel flasher and then flash init_boot
patched again.
Click to expand...
Click to collapse
I thought the problem here was that the patching from magisk doesn't back up the boot_init (Yet). If I recall correctly pixel flasher ensured the backup being there.
That would mean next time the attempt to restore images might fail again. Unless if this issue of magisk has already been addressed. I didn't check.

fivefour said:
I don't understand rooting the phone just to block ads.
Just use Adguard which surpasses any root adblocking abilities.
Click to expand...
Click to collapse
That's because you don't root just to block adds.

oscarcam said:
That's because you don't root just to block adds.
Click to expand...
Click to collapse
I know plenty of other uses of root, I have developed several root apps and maintained various kernels over the years.
Read what I quoted.

I read, but I didn't understand the same. Sorry.