Hello all,
For the last 4-5 firmware updates I've had no issue using fastboot to flash the firmware images, then flashing SuperSU, ElementalX kernel, Viper4Android and AdAway host lists through recovery to update to the latest build but keep my root mods.
I would like to now to the same with DP5 (or, at the very least, the first official Nougat build when it drops soon) and make sure I do it safely without any bricking.
Here's the current status -
Bootloader: Unlocked
Build: Android 6.0.1 MTC19Z, July Security Patch
Root Status: Rooted
Root Mods: ElementalX Kernel, Viper4Android, AdAway
Essentially, I want the same set up/root mods as above, only on 7.0. My questions are as follows:
1. Does the process differ at all for both installation of the firmware (through fastboot) or root method (flash TWRP, flash SuperSU)?
2. Is a full data wipe required? Recommended?
3. Anything else I should know?
Thanks in advance for the help. I'd love to make this as painless as the monthly firmware updates without any hiccups.
- Moonboots
The process does not differ much for the installation of the firmware; all you need to do is flash the factory images and TWRP through fastboot, and flash SuperSU/root through TWRP.
However, for a working TWRP and root, you'll need to decrypt your phone again, which will of course wipe your phone's data and internal storage.
I suggest looking at this helpful thread over on the Nexus 6P forums saying how to switch to 7.0 here:
http://forum.xda-developers.com/nexus-6p/general/how-to-switch-to-android-n-preview-t3409538
Even though it's for the 6P, I have used it myself and the procedure is the same. Once you've done all that, you're good to flash the latest SuperSU through TWRP.
As for V4A, I'm not sure whether it is compatible with Android N yet. You can install the ElementalX kernel normally after installing 7.0, but I don't think it's been updated to DP5.
If you do decide to update to Nougat, the modified boot.img for NPD90G can be found here:
http://forum.xda-developers.com/nexus-5x/general/4-17-16-t3360574
Thank you! I actually kept my phone encrypted all this time. Have you seen significant performance increases by decrypting?
EDIT: I see it's actually necessary for working TWRP in 7.0, thus far. Interesting. I'll have to work on getting my data backups set tonight.
Related
I know there are several threads covering similar things, however I still can't find the relevant info for my specific question.
I am on 6.0 Build L
I rooted using systemless root - I have changed nothing in my system partition as far as I know as I wanted root for AdBlock and TitaniumBU.
I am using the stock kernel too.
TWRP 2.8.7.2
I now have a 6.0.1 OTA - but I'm 100pc confused as to exactly how to go about installing this.
Some people seem to say OTA on this setup will work fine on similar setups.
Others say I need to flash 101 things to get it working.
Literally no idea.
How I Did it...
From a site with this in the title:
can_i_manually_flash_601_also_does_ota_work_with
Systemless root doesn't break ota, non-stock recovery breaks OTA.
Unlock bootloader, flash 6.0.1, flash TWRP, flash systemless root...
I did this:
Went back to stock recovery, by flashing via ADB, rebooted downloaded and attempted to install OTA on phone. Process started, rebooted, proceeded and then failed with error . Rebooted, got Factory image.
Extracted and ran flash-all.bat ONLY AFTER Removing the -w from this line:
fastboot -w update image-bullhead-mmb29k.zip
Got latest SuperSU v2.61 zip with auto boot patcher:
See androiding.how/android-6-0-1-root
Copied this to Memory on phone.
Flashed/Installed TWRP Recovery using ADB.
Booted into TWRP Recovery and installed SuperSU.
So now I'm running systemless rooted 6.01 on a Nexus 5X with mmb29k and every thing is working.
I think even though I rooted systemless 6.0, the modified Boot Image was still not letting OTA work.
We shall have to wait and see on the next OTA. Maybe just going back to stock recovery will be all that's needed.
There are some ADB commands that allow you to temporarily select a recovery image, but I'm not sure how that works.
Good Luck!
teapea said:
I know there are several threads covering similar things, however I still can't find the relevant info for my specific question.
I am on 6.0 Build L
I rooted using systemless root - I have changed nothing in my system partition as far as I know as I wanted root for AdBlock and TitaniumBU.
I am using the stock kernel too.
TWRP 2.8.7.2
I now have a 6.0.1 OTA - but I'm 100pc confused as to exactly how to go about installing this.
Some people seem to say OTA on this setup will work fine on similar setups.
Others say I need to flash 101 things to get it working.
Literally no idea.
Click to expand...
Click to collapse
Hello,
I want to root my friends sprint note 4 (lolipop i believe). I was looking at this guide http://galaxynote4root.com/galaxy-note-4-root/how-to-root-galaxy-note-4note-edge-on-android-5-1-1/ and it seems straightforward. A little different than what I had to do with my phone becuase I had to unlock the bootloader and then flash the recovery and supersu. (I've never used odin) Does this mean the bootloader is already unlocked by default since all I have to do is install the recovery and then the kernel?
I'm a little confused, once I get the recovery, can I flash roms to it? Do I have to change the kernel again if I want to install a ROM? I don't plan on putting a custom ROM on his phone but I want reflash the stock rom or a debloated stock rom because he said even after a factory reset it was buggy (if you can link me to a proper stock rom that supports xposed I would be grateful).
And I also want xposed to work, is there a specific xposed version I should install?
And also, if I do flash something, is this method correct?
Backup data
factory reset
flash
clear cache
restore data
reboot
or do I restore the data later?
The thread and video are dated. A few key elementary facts are still relevant but as a whole, just not up to date. I wouldn't trust it and it lends to repeated help threads in this forum. If one read the OPs and threads of current ROMs in development and recent help threads, maybe less questions and help would be needed.
He omits current ROMs, didn't mention where the reactivation lock is for TW Android ROMs: Settings/Security/Reactivation lock (should be disabled). He doesn't mention Chainfire Auto root for Note 4 has been updated for 5.1 and will be key again for marshmallow (but that's only needed for rooting stock Odex). He also didn't tell you how to get to those old ROMs on his site. Some think you just Odin an old update but not so. That requires a 5.1 kernel matched with current bootloader rather than Odin downgrade.
The bootloader, while not locked to block root, is considered unlocked but actually is now security locked to block older security stock tars with lower security bootloaders. It's actually unknown until confirmed what tar you can downgrade to. It won't be KitKat or OB7 and some just after that. From OK1 update, I'm only aware that you can downgrade from OK1 to OJ6 and if you flash the MM leaked tar, you can still downgrade to OK1.
Kernels should be kept in zip form because backing up a kernel in TWRP doesn't backup /system/lib/modules to restore and some custom kernels modify or add modules which may not work restored boot.img And restoring stock kernel on a rooted phone would cause a boot loop. So to restore that, you'd need to full un-root in SuperSU to avoid the boot loop there as well as restore the stock /system/lib/modules.
Root methods: unless you're using the full un-root or wiping everything but extSdCard (particularly user data and internal memory), you don't fully remove systemless root. Flashing a ROM or SuperSU with system based SuperSU over systemless root without the wipes would break things like root. Not seeing the SuperSU app or loss of ability to add new apps to superuser would be impacted but also a boot loop is possible if but patching stock kernel su.img to boot.
The basic principal is that to flash the custom deodexed ROM you need for Xposed, just make sure you're on the right update, Odin TWRP and follow the OP closely. If wiping internal memory is suggested by OP, I'd suggest that. To keep things simple, I backup and wipe everything but extSdCard for ports or where Xposed or systemless SuperSU is used. I typically do the same for stock tar updates as well.
As to recommended ROMs, I'd suggest any deodexed OK1 ROM for Xposed. tx_dbs_tx has a variety of OK1 ROMs. Freeza has one with Xposed integrated with Xposed modules in system. If Note 5 Moar port is a good fit, I'd recommend trying without Xposed until you determine the minimum of Xposed mods you're lacking so you're not overlapping features and you're getting to know the stability of it, first.
Rooting a friend's phone? IMO, you should be very sure and confident before proceeding and advise rather than do all the work and take the risks yourself. Use the correct USB driver, not just one that works. Setup his computer to root and sustain that phone.
Sent from my SM-N910P using Tapatalk
How is it dated exactly? I thought 5.1 is highest OTA for Note 4? Do OTA security patches change how things work now? I wouldn't know about security patches since I have a moto x 2013, we are left in the dust.
This is the ROM I am looking at http://forum.xda-developers.com/note-4-sprint/development/rom-t3271966
I'm still a little confused about the bootloader, right now my friend is on Sprint 5.1 lolipop. Is there a way to check the bootloader version? Can I not use Odin to install TWRP? And I'm not sure about the modem/kernel stuff, I didn't have to deal with it on my 2013 moto x. The website links to these kernels https://www.mediafire.com/folder/naq9dih44fndv/SM-N915P. Can I flash the latest kernel that was uploaded in January? The ROM contains root so I know I'm not supposed to flash superSU by itself, also obviously not to take any OTA's. I know that I'm supposed to install the wanam version of xposed that is optimized for samsung phones.
rapiollymega said:
How is it dated exactly? I thought 5.1 is highest OTA for Note 4?
Click to expand...
Click to collapse
I answered that in detail.
rapiollymega said:
Do OTA security patches change how things work now?
Click to expand...
Click to collapse
No; it's the bootloader and updates that did that.
rapiollymega said:
This is the ROM I am looking at http://forum.xda-developers.com/note-4-sprint/development/rom-t3271966
Click to expand...
Click to collapse
Good choice.
rapiollymega said:
I'm still a little confused about the bootloader, right now my friend is on Sprint 5.1 lolipop. Is there a way to check the bootloader version?
Click to expand...
Click to collapse
Answered. Use Phone Info from Google Play or Galaxy Tools.
rapiollymega said:
Can I not use Odin to install TWRP? And I'm not sure about the modem/kernel stuff, I didn't have to deal with it on my 2013 moto x. The website links to these kernels https://www.mediafire.com/folder/naq9dih44fndv/SM-N915P. Can I flash the latest kernel that was uploaded in January? The ROM contains root so I know I'm not supposed to flash superSU by itself, also obviously not to take any OTA's. I know that I'm supposed to install the wanam version of xposed that is optimized for samsung phones.
Click to expand...
Click to collapse
Answered. Make sure you're updated, use Odin to flash TWRP and follow OP closely. I wouldn't concern myself with the kernels listed outside this forum. SuperSU and kernel are in those ROMs; they're pre-rooted. If you want an updated kernel, I'd recommend freeza Beastmode kernel from this forum.
Edit: don't use a Galaxy Edge ROM, kernel or recovery on a Note 4 or vice versa. To be clear, this is the Sprint Note 4 forum. SM-N910P not SM-N915P.
Edit 2: When flashing TWRP, verify the reactivation lock is unchecked in Settings/Security. Use latest Odin, uncheck only the auto reboot option. Once it flashes and you confirm 0 failed, pull USB and battery for 30 seconds. Reinstall battery and be sure to reboot directly into recovery. Skip steps and it may not stick.
Sent from my SM-N910P using Tapatalk
samep said:
Answered. Make sure you're updated, use Odin to flash TWRP and follow OP closely. I wouldn't concern myself with the kernels listed outside this forum. SuperSU and kernel are in those ROMs; they're pre-rooted. If you want an updated kernel, I'd recommend freeza Beastmode kernel from this forum.
Edit: don't use a Galaxy Edge ROM, kernel or recovery on a Note 4 or vice versa. To be clear, this is the Sprint Note 4 forum. SM-N910P not SM-N915P.
Edit 2: When flashing TWRP, verify the reactivation lock is unchecked in Settings/Security. Use latest Odin, uncheck only the auto reboot option. Once it flashes and you confirm 0 failed, pull USB and battery for 30 seconds. Reinstall battery and be sure to reboot directly into recovery. Skip steps and it may not stick.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Sorry if I'm not understanding some of your post since I'm not that experienced with android or the post is kind of worded ambiguously. For TWRP, should I use 3.0 or 2.8.7?
is now security locked to block older security stock tars with lower security bootloaders. It's actually unknown until confirmed what tar you can downgrade to. It won't be KitKat or OB7 and some just after that. From OK1 update, I'm only aware that you can downgrade from OK1 to OJ6 and if you flash the MM leaked tar, you can still downgrade to OK1.
Click to expand...
Click to collapse
I'm not sure what you mean here. Looking at youtube videos, people just flash TWRP with Odin. Should I just try to put TWRP in? I understand the part about either removing the battery or trying to instant go into recovery.
So the ROM I'm looking at already has a kernel? So all I need to do it flash the zip? And then install xposed? Is it recommended to restore data or should I boot first once and then restore data. Also on a side question: For data restoring, is there a way to only specifically restore apps from a data backup? Thanks for the help.
rapiollymega said:
Sorry if I'm not understanding some of your post since I'm not that experienced with android or the post is kind of worded ambiguously. For TWRP, should I use 3.0 or 2.8.7?
I'm not sure what you mean here. Looking at youtube videos, people just flash TWRP with Odin. Should I just try to put TWRP in? I understand the part about either removing the battery or trying to instant go into recovery.
So the ROM I'm looking at already has a kernel? So all I need to do it flash the zip? And then install xposed? Is it recommended to restore data or should I boot first once and then restore data. Also on a side question: For data restoring, is there a way to only specifically restore apps from a data backup? Thanks for the help.
Click to expand...
Click to collapse
It's the INTERNET that's ambiguous towards Touchwiz Android 5.1 There has been a few updates and each changed the way we do things. So when you say you're on Android 5.1, I say you need to be on the latest 5.1 update to have the greatest compatibility with the ROM you're choosing to flash.
Yes. You use Odin to install TWRP when rooting from full stock un-root to custom pre-rooted ROM. Perhaps my direction to Odin TWRP was ambiguous? Flash this in Odin AP slot with auto reboot unchecked- use the other option defaults from latest Odin:
https://dl.twrp.me/trltespr/twrp-3.0.0-0-trltespr.img.tar.html
http://forum.xda-developers.com/showpost.php?p=51767811&postcount=1
I would restore data after installing Xposed. Keep in mind that these installation boots of custom ROM and Xposed take time. The less apps and data, the shorter the boot times will be. Plus the ROM will have more time to stabilize. After you've verified the last three of the bootloader and modem matches OK1, you can proceed with TWRP, then install ROM per the 1st post and immediate posts from OP. When you get to the Wi-Fi connection in setup wizard, make sure you have radio signal before connecting Wi-Fi. Make sure everything is stable and functional before Xposed installation.
Again, about the long boot times on installation. Best to keep case off the phone and ventilate phone with not too cool or ambient air. This will speed the process and possibly prevent component failure.
When your ready for Xposed, you need the Wanam unofficial Xposed framework.
http://forum.xda-developers.com/showpost.php?p=62377731&postcount=1
You'll need sdk22 arm for Lollipop, not 64 bit Exynos or MM.
Currently it's the one labeled: xposed-v80.0-sdk22-arm-custom-build-by-wanam-20160211.zip
Grab the uninstaller too, just in case. You shouldn't need it but be prepared.
Edit: be sure to get the deodexed version of that ROM. Makes things easier for Xposed and Xposed compatibility when adding system applications, if that applies to anytime later.
Sent from my SM-N910P using Tapatalk
Thanks for all the help, did it over the weekend and everything went smoothly. Well except for one part before installing the new ROM, I deleted everything in data/system and forgot that the zip was In the internal storage instead of the sd card . And for whatever reason the PC usb connection wasn't working in TWRP so I had to use a flash drive and otg cable to put the zip ROM back in the phone.
Hello all,
Yesterday I did what many did and upgraded to Nougat as soon as it dropped, using the "sign up for Android beta" method. I came from a bootloader unlocked, rooted Nexus 5x running the latest version of 6.0.1 with a few basic mods - AdAway, Viper4Android, ElementalX Kernel w/ profile manager, Cf.Lumen and Greenify.
In upgrading to Android 7.0, I first flashed the system, vendor, boot and recovery image from the most recent version of 6.0.1 to revert completely to unrooted stock before taking the OTA.
After reading about this new method of systemless root that also seems to allow Android Pay to work, I'm trying to wrap my head around it before trying, and wanted some of the wise minds of XDA to confirm my procedure.
Current Status-
Device: Nexus 5x
Build: Android 7.0 NRD90M
Unlock Status: Bootloader Unlocked
Root Status: Unrooted
Boot.img and Recovery.img: Stock
Procedure:
1. Download latest TWRP, boot device into fastboot mode, and "fastboot flash recovery [TWRP file]"
2. Navigate to TWRP Recovery, locate phh root .zip (already downloaded to device), Magisk mod and ElementalX kernel, flash these.
3. Once booted, follow directions in the Magisk thread to mount the desired mods (AdAway, Viper4Android, etc.) while still passing SafetyNet check, and Android Pay will continue to work.
Also, if I understand correctly, future system updates will be possible using FlashFire and the OTA .zip while maintaining root status and the modifications, since \system is not modified using this method.
Any confirmation/feedback is welcome!
Thanks,
Moonboots
Moonboots said:
Hello all,
Yesterday I did what many did and upgraded to Nougat as soon as it dropped, using the "sign up for Android beta" method. I came from a bootloader unlocked, rooted Nexus 5x running the latest version of 6.0.1 with a few basic mods - AdAway, Viper4Android, ElementalX Kernel w/ profile manager, Cf.Lumen and Greenify.
In upgrading to Android 7.0, I first flashed the system, vendor, boot and recovery image from the most recent version of 6.0.1 to revert completely to unrooted stock before taking the OTA.
After reading about this new method of systemless root that also seems to allow Android Pay to work, I'm trying to wrap my head around it before trying, and wanted some of the wise minds of XDA to confirm my procedure.
Current Status-
Device: Nexus 5x
Build: Android 7.0 NRD90M
Unlock Status: Bootloader Unlocked
Root Status: Unrooted
Boot.img and Recovery.img: Stock
Procedure:
1. Download latest TWRP, boot device into fastboot mode, and "fastboot flash recovery [TWRP file]"
2. Navigate to TWRP Recovery, locate phh root .zip (already downloaded to device), Magisk mod and ElementalX kernel, flash these.
3. Once booted, follow directions in the Magisk thread to mount the desired mods (AdAway, Viper4Android, etc.) while still passing SafetyNet check, and Android Pay will continue to work.
Also, if I understand correctly, future system updates will be possible using FlashFire and the OTA .zip while maintaining root status and the modifications, since \system is not modified using this method.
Any confirmation/feedback is welcome!
Thanks,
Moonboots
Click to expand...
Click to collapse
Howdy sir! I'm still learning myself so I can't give you a great answer, but it's been a few weeks so I thought maybe you already gave this a shot? I'm looking to follow about the same process soon. I'm currently bootloader unlocked with TWRP loaded on Nougat (NRD90S on 5X).
How'd this go for ya?
Thanks!
Hello all-
I have looked everywhere for clarification on this to no avail. I am currently UN-rooted, Unlocked Bootloader & TWRP (OOS 4.0.3, 12/1/16 Android Security patch). Can I take the OTA for OOS 4.1.3 or will that make me lose TWRP? I know there are instances when you can take the OTA and where you have to flash the entire ROM but I can't locate the differences and which route I need to take? Please advise if you know this answer.
Thank you!
I'm not sure, but, you can just flash the ota in twrp and make sure to flash the twrp img after flashing the ota. And, always make a twrp backup
AFAIK you need stock recovery for OTA to work (not 100% sure).
If downloading whole 1.4GB ROM is not a big issue, it's safer to dirty flash the whole ROM. Otherwise you could flash back stock recovery, install small OTA, then flash TWRP again. A bit more work, but less downloading.
Sent from my OnePlus 3 using Tapatalk
This question doesn't belong in this section. @Stephen please move this to the Q&A section. Thanks.
DroidJay123 said:
Hello all-
I have looked everywhere for clarification on this to no avail. I am currently UN-rooted, Unlocked Bootloader & TWRP (OOS 4.0.3, 12/1/16 Android Security patch). Can I take the OTA for OOS 4.1.3 or will that make me lose TWRP? I know there are instances when you can take the OTA and where you have to flash the entire ROM but I can't locate the differences and which route I need to take? Please advise if you know this answer.
Thank you!
Click to expand...
Click to collapse
Let me make it clear, the full rom flash is a better option and you can do so from twrp. You would not loose twrp after the flash and need not flash the recovery again. SuperSU/Magisk flash is optional after the ROM flash. I see that you are running 3.0.4-1 which is a 7.1.1 compatible TWRP so there is no need to worry of any data loss. TWRP is also able to flash the OTA's provided you have not made any changes to your system partition and have remained unrooted.
You can come to General / OOS thread and ask there for further understanding :fingers-crossed:
You can flash OTA as long as your kernel is on default, what I mean is stock/untouched which is basically same situation as yours since youre unrooted. ? So yes you can flash OTA no need for full flash
If me, i like waiting full ROM zip release and do clean install.
Sometimes, flash OTA getting error (cause root, bla bla bla hahaha )
Yeah, it could be lazy gonna install back all apps at least you backup it
My advice, if you update same Android version, no problem to do a dirty flash (same ROM like LOS 14 to LOS 14, but if different ROM, i suggest better do clean install)
But if different version, mean 7.0 to 7.1.1, better clean install (dirty also no problem, but wonder in future got problem)
But hey, different people, different way right? This just my 2cent
It is my understanding that when moving from whole version number changes (6 to 7, 7 to 8) etc that a clean install is definitely way to go but even from 7.0 to 7.1? Also when you download the OTA, is the file saved somewhere so you can then locate it in TWRP for flashing? I don't want to allow the system to install the ota automatically correct?
DroidJay123 said:
Hello all-
I have looked everywhere for clarification on this to no avail. I am currently UN-rooted, Unlocked Bootloader & TWRP (OOS 4.0.3, 12/1/16 Android Security patch). Can I take the OTA for OOS 4.1.3 or will that make me lose TWRP? I know there are instances when you can take the OTA and where you have to flash the entire ROM but I can't locate the differences and which route I need to take? Please advise if you know this answer.
Thank you!
Click to expand...
Click to collapse
It is best to clean flash if you've major upgrade like 6->7 or 7>8 something like that but if as your question you're still on marshmallow so you can flash OTA zip through twrp and make sure after OTA you've to flash twrp again to maintain it. If the system shows OTA it can't flash it via open recovery on twrp, you must have stock recovery to do it.
This thread is not for ROM development. Please get a mod move this thread to the Q&A section.
I'm a little lost on Root for the Pixel XL. I am currently running unlocked with Screw'd ROM - 3.1.2-****ery-20170712-1454. This is a BETA, but has been running really smooth for the last 2 days.
Security Patch Level - July 5, 2017
Vendor - NJH47D
Last time I tried to apply root while running PureNexus the phone continued to boot loop and I had to eventually flashall.bat and start over.
1. What version of SuperSU should I be flashing? The latest and newest or is there other versions that work better?
2. What are the correct steps? Is wipe cache/dalvik necessary before? Do I need to install anything on the phone beforehand?
Boot to TWRP, Flash SuperSU, Reboot? Easy as that?
I see this version being talked about a lot - SR3-SuperSU-v2.79-SR320170114223742.zip, but it isn't the latest available that I can see. The SuperSU thread states to install the latest version and using google brings me to many versions of SuperSU.
Lastly, after rooting will apps like SnapChat work? If not how to you bypass this?
So I just found some information after searching more. Some of it is dated. I currently have twrp-pixel-installer-marlin-3.1.0-0RC2.zip version for TWRP installed.
Is RC1 needed for root, and with what SuperSU version. Or which combination of RC2 and SuperSU work together?
jws86 said:
So I just found some information after searching more. Some of it is dated. I currently have twrp-pixel-installer-marlin-3.1.0-0RC2.zip version for TWRP installed.
Is RC1 needed for root, and with what SuperSU version. Or which combination of RC2 and SuperSU work together?
Click to expand...
Click to collapse
When I was rooted I initially was using RC1, I think my supersu was V2.8? And no Snapchat, Pokemon go, and Android pay, etc, will not work. So a little work around for Snapchat, you need to log in first then flash supersu, or just go with magisk and enable magisk hide to make life easier.
sakumaxp said:
When I was rooted I initially was using RC1, I think my supersu was V2.8? And no Snapchat, Pokemon go, and Android pay, etc, will not work. So a little work around for Snapchat, you need to log in first then flash supersu, or just go with magisk and enable magisk hide to make life easier.
Click to expand...
Click to collapse
Is there a guide to Root with Magisk somewhere floating around?
jws86 said:
Is there a guide to Root with Magisk somewhere floating around?
Click to expand...
Click to collapse
I believe it's the same as when you flash supersu, don't quote me on that
sakumaxp said:
I believe it's the same as when you flash supersu, don't quote me on that
Click to expand...
Click to collapse
Yeah I found the guide. It seems I need to flash stock image first before. So Magisk gives you the ability to root first, then download apps such as snapchat and still login if you use magisk hide?
jws86 said:
Yeah I found the guide. It seems I need to flash stock image first before. So Magisk gives you the ability to root first, then download apps such as snapchat and still login if you use magisk hide?
Click to expand...
Click to collapse
Correct, downloading isn't a problem, but it'll just prevent you from logging in since supersu, trips safetynet
sakumaxp said:
Correct, downloading isn't a problem, but it'll just prevent you from logging in since supersu, trips safetynet
Click to expand...
Click to collapse
I read through this thread: https://forum.xda-developers.com/pixel-xl/how-to/guide-stock-7-1-2-root-safetynet-ok-t3617347
Seems pretty straightforward, however currently I have a ROM installed I'm really liking. To do this I would have to flash back to stock image, then go through the root process. My question would be after rooting, if I went to flash Screw'd again, doesn't it wipe everything and I would lose root again, then just have to flash it after the ROM?
jws86 said:
I read through this thread: https://forum.xda-developers.com/pixel-xl/how-to/guide-stock-7-1-2-root-safetynet-ok-t3617347
Seems pretty straightforward, however currently I have a ROM installed I'm really liking. To do this I would have to flash back to stock image, then go through the root process. My question would be after rooting, if I went to flash Screw'd again, doesn't it wipe everything and I would lose root again, then just have to flash it after the ROM?
Click to expand...
Click to collapse
Myself I've never been on screwd before, I would assume so, but in my experience the pixel XL is more complicated than my previous phones
If you just want root you shouldn't need to flash the stock image again. You would need to do that if you wanted to flash a custom kernel but not for root. You need to download the modified version of Magisk for the Pixel XL. The official version doesn't work on the Pixels. I'm not currently rooted as I went back to stock but I was using Magisk. At that time the latest version wasn't stable but it might be fixed now. You need to boot into fastboot TWRP, flash the Magisk zip, flash the TWRP zip and then boot up. After you are booted up you install the Magisk Manager app. The tricky thing is installing the right version of Magisk Manager that works properly with the unofficial build of Magisk that you are using. You can get more information in the Resurrection Remix rom thread which for some reason is the official place where the modified version of Magisk is hosted if you can't find good info about which combination of unofficial Magisk and Magisk Manager you should be using. Also when I used Magisk you needed to enable core only mode for it to pass Safety Net but that may no longer be the case. You should be able to find the most up to date info either in the thread you cited or the RR rom thread. Just remember that official builds of Magisk do not work on the Pixel. You need to stick with one of the unofficial builds.
jhs39 said:
If you just want root you shouldn't need to flash the stock image again. You would need to do that if you wanted to flash a custom kernel but not for root. You need to download the modified version of Magisk for the Pixel XL. The official version doesn't work on the Pixels. I'm not currently rooted as I went back to stock but I was using Magisk. At that time the latest version wasn't stable but it might be fixed now. You need to boot into fastboot TWRP, flash the Magisk zip, flash the TWRP zip and then boot up. After you are booted up you install the Magisk Manager app. The tricky thing is installing the right version of Magisk Manager that works properly with the unofficial build of Magisk that you are using. You can get more information in the Resurrection Remix rom thread which for some reason is the official place where the modified version of Magisk is hosted if you can't find good info about which combination of unofficial Magisk and Magisk Manager you should be using. Also when I used Magisk you needed to enable core only mode for it to pass Safety Net but that may no longer be the case. You should be able to find the most up to date info either in the thread you cited or the RR rom thread. Just remember that official builds of Magisk do not work on the Pixel. You need to stick with one of the unofficial builds.
Click to expand...
Click to collapse
I think I got which versions of magisk and magisk manager I need to use from the other thread I had posted earlier. This helps to clear some things up for me though. I have both the .apk and the zip on my phone now. Getting a bit of a charge and I guess I'll go ahead and try it.
It worked, I'm officially rooted .Thanks for the help!
jws86 said:
It worked, I'm officially rooted .Thanks for the help!
Click to expand...
Click to collapse
Cool.