Three again. Verizon, Dutsche and every one else. Flashing now.
So far full images only, no OTA.
OTAs are up too. Anyone see a change log or know if TWRP and SuperSU are working?
sliding_billy said:
OTAs are up too. Anyone see a change log or know if TWRP and SuperSU are working?
Click to expand...
Click to collapse
I am still investigating, but it would seem SU is not working.
I ran flash-all.bat after removing the -w
Boots and runs fine.
fastboot booted twrp RC1 and flash SU 2.79 SR3
It is sitting here bootlooping now. I have reflashed and tried a couple of times. Same result.
TonikJDK said:
I am still investigating, but it would seem SU is not working.
I ran flash-all.bat after removing the -w
Boots and runs fine.
fastboot booted twrp RC1 and flash SU 2.79 SR3
It is sitting here bootlooping now. I have reflashed and tried a couple of times. Same result.
Click to expand...
Click to collapse
Thanks for taking one for the team. It felt like something was going to fail based on comments about rooting the developer preview.
sliding_billy said:
Thanks for taking one for the team. It felt like something was going to fail based on comments about rooting the developer preview.
Click to expand...
Click to collapse
Not sure what another build of 7.1.2 has to do with ODP1. Plus, SuperSU v2.79 SR4 w/delay works on ODP1 after some dual-slot magic.
Kisakuku said:
Not sure what another build of 7.1.2 has to do with ODP1. Plus, SuperSU v2.79 SR4 w/delay works on ODP1 after some dual-slot magic.
Click to expand...
Click to collapse
Just was a gut feeling that whatever was going wrong in the developer build would somehow been implemented in the May build. I am sure they are unrelated, but that was why I asked before the OP was updated to include the SU break.
The VZ OTA will download if you set the date to May 4th.
just checked my phone and got Verizon update without changing date
My OTA for Verizon didn't hit yet. And moving the date forward didn't help. Hopefully soon.
what will happen to supersu if try to flash this full factory image via flashfire and
bush911 said:
what will happen to supersu if try to flash this full factory image via flashfire and
Click to expand...
Click to collapse
It will be gone.
Pixel users are reporting bootlooping on the May update after flashing TWRP only
https://forum.xda-developers.com/showthread.php?p=72121371
https://forum.xda-developers.com/showthread.php?p=72120712
What are the chances that this was done purposely? "Breaking root and twrp"
DR3W5K1 said:
What are the chances that this was done purposely? "Breaking root and twrp"
Click to expand...
Click to collapse
Anyone try Magisk? I imagine same result.
Sent from my Pixel XL using Tapatalk
I sideloaded n2g47o ota, there were no errors but it didn't seem to take. Still shows n2g47e as the build. Something must have went wrong. I will hold off on trying again for now.
if i try to go back to march update and to root it again, i got a bootloop. right now is no root for me anymore
itchy67x said:
if i try to go back to march update and to root it again, i got a bootloop. right now is no root for me anymore
Click to expand...
Click to collapse
Just use April's bootloader.
Taebom said:
Just use April's bootloader.
Click to expand...
Click to collapse
thx that works
Taebom said:
Just use April's bootloader.
Click to expand...
Click to collapse
Thanks, that works for the Pixel too. I flashed April's K bootloader on the May L version no problem. TWRP and SU work fine now.
dowlf said:
I sideloaded n2g47o ota, there were no errors but it didn't seem to take. Still shows n2g47e as the build. Something must have went wrong. I will hold off on trying again for now.
Click to expand...
Click to collapse
FWIW: sideload of n2g47o worked fine on my (stock) XL. Did you have any modifications?
Related
Hey guys, so I installed twrp and formatted data, rebooted, installed super su (sr version), and now my phone is decrypted and rooted on 7.1.1 Just passing this along if anyone needs it
Xdevillived666 said:
Hey guys, so I installed twrp and formatted data, rebooted, installed super su (sr version), and now my phone is decrypted and rooted on 7.1.1 Just passing this along if anyone needs it
Click to expand...
Click to collapse
Screenshots guys
I can confirm CF-Autoroot works without flaws!
I used the Nexus Root Toolkit and that worked a charm, got recovery and root installed easily.
What recovery are you guys using? latest 3.0.2-3?
Krenol said:
What recovery are you guys using? latest 3.0.2-3?
Click to expand...
Click to collapse
I'm using 3.0.2-1 but I have heard people say 3.0.2-2 works as well. Hope that helps
does formatting the data is really needed? I tried to flash twrp with everything on stock (encrypted), it works on first boot of twrp but whenever I boot to system then try to boot to twrp, it gives 'No Command' and I have to reflash twrp again :silly:
RonnellTapawan said:
does formatting the data is really needed? I tried to flash twrp with everything on stock (encrypted), it works on first boot of twrp but whenever I boot to system then try to boot to twrp, it gives 'No Command' and I have to reflash twrp again :silly:
Click to expand...
Click to collapse
It would seem so. Until I decrypted, I wasn't able to keep it permanently installed.
I can also say that Nexus Root Toolkit worked for me. That's a great app - I suggest using it and helping the developer!
Razeer123 said:
I can also say that Nexus Root Toolkit worked for me. That's a great app - I suggest using it and helping the developer!
Click to expand...
Click to collapse
Yeah, it is nice . I just like doing it myself ,though I used the app to flash stock recovery and get the ota.... Speaking of the ota , does anyone else have "android 7.1.1" under about phone ???
I rooted at first with PHH suhide and the only thing I couldn't do was change system files, as expected. Flashed back to stock, updated to dev preview again (clean slate) and installed magisk v8 and root. Everything is working fine and dandy.
Xdevillived666 said:
Yeah, it is nice . I just like doing it myself ,though I used the app to flash stock recovery and get the ota.... Speaking of the ota , does anyone else have "android 7.1.1" under about phone ???
Click to expand...
Click to collapse
Yeah, I think everyone have this number. I suppose the x.x.1 means Security Patch number, but I'm not sure.
I'm new to the beta program. What happens if I root and install a custom recovery in this beta version 7.1.1? I assume that I will no longer be able to get future incremental OTA beta updates?
ToothTooth said:
I'm new to the beta program. What happens if I root and install a custom recovery in this beta version 7.1.1? I assume that I will no longer be able to get future incremental OTA beta updates?
Click to expand...
Click to collapse
You can. Just before installing , reinstall stock recovery and then install ota or use flash fire
Have any of you been able to use SuHide?
Im just getting a constant bootlogo and no further.
Morning all
Just checking in to say I've been running this 7.1.1 preview for over 24 hours, without so much as a slight hiccup. It's very smooth and fluid. I haven't bothered rooting or anything yet as the phone runs beautifully as is, but no doubt I will tinker when I get back from a short break. Only disappointing thing is android pay not working due to unlocked bootloader
Anyone has no-force decrypt boot img, coz seems like device is encrypted, as Im stuck with TWRP(3.0.2-1) logo
odunke01 said:
Have any of you been able to use SuHide?
Im just getting a constant bootlogo and no further.
Click to expand...
Click to collapse
My bad, didnt wait long enough.
Problem is though that we cant seem to keep changes to the /system file on the preview
https://www.reddit.com/r/Android/comments/58npsl/71_appears_to_aggressively_fix_errors_to_the/
odunke01 said:
My bad, didnt wait long enough.
Problem is though that we cant seem to keep changes to the /system file on the preview
https://www.reddit.com/r/Android/comments/58npsl/71_appears_to_aggressively_fix_errors_to_the/
Click to expand...
Click to collapse
What are you using su hide for?
It was for pokemon go.
Although I have reverted to PN on 7.0 as I was having other issues. Root (edit:and recovery) wasn't holding after reboot and my hosts file kept disappearing.
I also missed the night light.
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
I can confirm that as of this morning I have been running official 6.0.1 and my bootloader is still unlocked!
thewire1o1 said:
I can confirm that as of this morning I gave been running official 6.0.1
Click to expand...
Click to collapse
Are you part of the soak test?
TheSt33v said:
Are you part of the soak test?
Click to expand...
Click to collapse
I can not confirm or deny that!
thewire1o1 said:
I can not confirm or deny that!
Click to expand...
Click to collapse
Haha well you already violated your NDA with this post, so there's no need for that anymore.
Factory reset and download all of the system imgs so we can all upgrade.
Crowick said:
Factory reset and download all of the system imgs so we can all upgrade.
Click to expand...
Click to collapse
I would second that:good:
Crowick said:
Factory reset and download all of the system imgs so we can all upgrade.
Click to expand...
Click to collapse
VincentCode88 said:
I would second that:good:
Click to expand...
Click to collapse
Already done, as of 1pm Sunday 12/4/12016. Also there's a TWRP flashable version, and now even TWRP flashable ebloated ROM based on the OTA:
[OTA] Official Marshmallow build MCG24.251-5
http://forum.xda-developers.com/dro...ota-official-marshmallow-build-mcg24-t3512813
[ROM] MCG24.251-5 100% Stock (TWRP flashable)
http://forum.xda-developers.com/droid-turbo/development/rom-mcg24-251-5-100-stock-t3512949
debloated Verizon 6.0.1 ROM ( MCG24.251-5) (TWRP flashable)
Computerfreek274_MM_1.0.3 Marshmallow 6.0.1
http://forum.xda-developers.com/droid-turbo/development/computerfreek274mm1-0-android-6-0-1-t3503634
Best to unlock your bootloader and flash or you may never be able to unlock your bootloader later.
ChazzMatt said:
Already done, as of 1pm Sunday 12/4/12016. Also there's a TWRP flashable version, and now even TWRP flashable ebloated ROM based on the OTA:
[OTA] Official Marshmallow build MCG24.251-5
http://forum.xda-developers.com/dro...ota-official-marshmallow-build-mcg24-t3512813
Click to expand...
Click to collapse
Great! Work for me on my xt1254 stock and lock
superuser install?
I flashed the TWRP zip, wiped everything, then it said I need to install SU... tried several times, but just got the bootloader unlocked disclaimer screen... finally didn't install SU, and it appears to be working.
i wipe system and cache , flashed but just got the disclaimer unlocked screen.
is necessary tu uninstall su before^?
gherman222 said:
I flashed the TWRP zip, wiped everything, then it said I need to install SU... tried several times, but just got the bootloader unlocked disclaimer screen... finally didn't install SU, and it appears to be working.
Click to expand...
Click to collapse
Which SuperSu are you using?
The one in this post works for Quark Motorola Marshmallow. SuperSu beta 2.62. After you flash it for initial root, then you can update to newer version.
http://forum.xda-developers.com/showpost.php?p=69722490&postcount=17
INITIAL ROOT ON QUARK MOTOROLA MARSHMALLOW 6.0.1
This same version of Marshmallow was released back in July for sibling Quark Moto XT1225. We found out then newer versions of SuperSu don't work for initial root. You need this older version first. No need to re-invent the wheel. It's the same device, same software.
_______________
Go ahead and download SuperSU from the attached file at bottom of this post. It's an older version of SuperSu but works well on the Quark Motorola Marshmallow ROM. You can always update to newer version later.
BETA-SuperSU-v2.62-3-20151211162651
Attached to this bottom of this post or download from here:
https://download.chainfire.eu/751/SuperSU/
Flash this version initially. You can update to newer version later. (People had problems flashing the very newest SuperSu for initial root, but this version works good. Again, you can update to newer version later, after you gain root.)
_______
BONUS TIP - SuperSu Setting
After you reboot, go into SuperSu settings and UNcheck this box. Mount namespace separation.
Uncheck that. Disable that. Then, reboot.
If it's enabled it will conflict with Titanium Backup which you will use at some point, or should. And you will have no idea why Titanium Backup is saying you are out of space, when you are not -- but it's due to this setting in SuperSu!
"M" Motorola boot logos
checo79 said:
i wipe system and cache , flashed but just got the disclaimer unlocked screen.
is necessary tu uninstall su before^?
Click to expand...
Click to collapse
No. You can just reflash your choice of boot logo to replace the unlocked warning screen. It's just a static image Motorola insists on showing you that your bootloader is unlocked. I know, I UNLOCKED it on purpose!
Here's boot logos (not to be confused with boot animation -- the boot logo is what you see before the boot animation starts) you can flash with ADB. Various colors of the Motorola M logo.
Remove annoying bootloader unlocked warning
ADB FLASHABLE BOOT LOGOS
http://forum.xda-developers.com/showpost.php?p=68538894&postcount=2
And here's the same boot logos you can flash with TWRP:
TWRP FLASHABLE BOOT LOGOS
http://forum.xda-developers.com/showpost.php?p=68579272&postcount=5
Works for all Quarks (XT1254/XT1250/XT1225).
It worked! Thanks man.
ChazzMatt said:
Which SuperSu are you using?
The one in this post works for Quark Motorola Marshmallow. SuperSu beta 2.62. After you flash it for initial root, then you can update to newer version.
http://forum.xda-developers.com/showpost.php?p=69722490&postcount=17
Click to expand...
Click to collapse
can anyone who's taken the OTA verify that it doesn't undo an existing sunshine bootloader unlock?
I want to take it, but don't want to risk the unlock,
thanks!
rhcreed said:
can anyone who's taken the OTA verify that it doesn't undo an existing sunshine bootloader unlock?
I want to take it, but don't want to risk the unlock,
thanks!
Click to expand...
Click to collapse
It doesn't. Confirmed.
TheSt33v said:
It doesn't. Confirmed.
Click to expand...
Click to collapse
Thanks!,
Of course, I delayed it a couple days, and now it doesn't show the update available anymore. Still get the "you're up to date" even though it shows a failed download in the status.
Guess it's for the best, I'll wait for a 7 rom that's stable enough to be a DD.
rhcreed said:
Thanks!,
Of course, I delayed it a couple days, and now it doesn't show the update available anymore. Still get the "you're up to date" even though it shows a failed download in the status.
Guess it's for the best, I'll wait for a 7 rom that's stable enough to be a DD.
Click to expand...
Click to collapse
You can download the OTA from here and flash it.
ChazzMatt said:
You can download the OTA from here and flash it.
Click to expand...
Click to collapse
if I do that will it wipe what I have now, or upgrade like an ota? I'm unlocked but still stock, too lazy to want to wipe and rebuild just yet.
Know of a way to reset the update service so it tries again? (I'm googling now, but figured you knew better than I did )?
rhcreed said:
if I do that will it wipe what I have now, or upgrade like an ota? I'm unlocked but still stock, too lazy to want to wipe and rebuild just yet.
Know of a way to reset the update service so it tries again? (I'm googling now, but figured you knew better than I did )?
Click to expand...
Click to collapse
From the op description, it will wipe what you have. So, yeah, wait for the OTA.
http://forum.xda-developers.com/showthread.php?t=3512813
I just downloaded and flashed the May security update.
Booting into TWRP and then installing SU throws it into a bootloop. Still testing and investigating, would be great if some others could test to see if it is universal or just me.
TonikJDK said:
I just downloaded and flashed the May security update.
Booting into TWRP and then installing SU throws it into a bootloop. Still testing and investigating, would be great if some others could test to see if it is universal or just me.
Click to expand...
Click to collapse
It's not just you.
TonikJDK said:
I just downloaded and flashed the May security update.
Booting into TWRP and then installing SU throws it into a bootloop. Still testing and investigating, would be great if some others could test to see if it is universal or just me.
Click to expand...
Click to collapse
ME too. TWRP installer for sure.
Tulsadiver said:
ME too. TWRP installer for sure.
Click to expand...
Click to collapse
Installing SuperSU from the RC1 img or installing RC2 and then installing SuperSU from there?
Looks like I'll wait on May factory images ...
sliding_billy said:
Installing SuperSU from the RC1 img or installing RC2 and then installing SuperSU from there?
Click to expand...
Click to collapse
After booting into TWRP, flashing twrp pixel installer, then trying to boot back into TWRP bootloops without even getting to supersu.
The reasons to stay stock, are starting to out weigh the reasons to root.
Tulsadiver said:
After booting into TWRP, flashing twrp pixel installer, then trying to boot back into TWRP bootloops without even getting to supersu.
Click to expand...
Click to collapse
Gotcha. That stinks! I have never booted back into TWRP after installing. I have just went straight to SuperSU installer after RC2 install. I imagine that would have just created a different issue.
sliding_billy said:
Gotcha. That stinks! I have never booted back into TWRP after installing. I have just went straight to SuperSU installer after RC2 install. I imagine that would have just created a different issue.
Click to expand...
Click to collapse
They will probably figure something out. Nexus 5X didn't have any problems with their May update.
Tulsadiver said:
They will probably figure something out. Nexus 5X didn't have any problems with their May update.
Click to expand...
Click to collapse
I'm sure. I am in no hurry for what is most likely just a security update.
Sideloading the correct image now. Pisses me off there is a separate image for Verizon. I flashed the Verizon version instead of the standard one.
---------- Post added at 04:42 PM ---------- Previous post was at 04:35 PM ----------
Loaded the May images on the 5x. Magisk is good to go for the 5X. Pixel is stock right now.
Glad I came here before installing the May update.....
TonikJDK said:
I just downloaded and flashed the May security update.
Booting into TWRP and then installing SU throws it into a bootloop. Still testing and investigating, would be great if some others could test to see if it is universal or just me.
Click to expand...
Click to collapse
Definitely not just you. I thought it was an issue with SuperSU, but it's actually an issue with TWRP?
CatThief said:
Definitely not just you. I thought it was an issue with SuperSU, but it's actually an issue with TWRP?
Click to expand...
Click to collapse
Both
CatThief said:
Definitely not just you. I thought it was an issue with SuperSU, but it's actually an issue with TWRP?
Click to expand...
Click to collapse
Tulsadiver said:
Both
Click to expand...
Click to collapse
Just use April's bootloader and everything works fine. Thanks to a user in the XL therad for the info. I'm rooted on the May L version with April's K bootloader.
Misterxtc said:
Just use April's bootloader and everything works fine. Thanks to a user in the XL therad for the info. I'm rooted on the May L version with April's K bootloader.
Click to expand...
Click to collapse
Works for me. Thanks Misterxtc!
Misterxtc said:
Just use April's bootloader and everything works fine. Thanks to a user in the XL therad for the info. I'm rooted on the May L version with April's K bootloader.
Click to expand...
Click to collapse
How did you do that?
UPDATE: Problem solved...
Swerner1975 said:
How did you do that?
UPDATE: Problem solved...
Click to expand...
Click to collapse
If you didn't figure it out or anyone else needs help I downloaded both the K and L updates, installed L, rebooted to bootloader and ran the following command with the K bootloader then reboot bootloader. After that you can install TWRP and root.
Code:
fastboot flash bootloader bootloader-sailfish-8996-012001-1702151126
Misterxtc said:
If you didn't figure it out or anyone else needs help I downloaded both the K and L updates, installed L, rebooted to bootloader and ran the following command with the K bootloader then reboot bootloader. After that you can install TWRP and root.
Code:
fastboot flash bootloader bootloader-sailfish-8996-012001-1702151126
Click to expand...
Click to collapse
THX!
If you flash manually you just skip the first step. The bootloader part.
The January updates are up.
OTA is live too. Just 50.8 MB for 1st Gen XL.
ylapas said:
OTA is live too. Just 50.8 MB for 1st Gen XL.
Click to expand...
Click to collapse
Installing now
ylapas said:
Installing now
Click to expand...
Click to collapse
I just flashed January Factory image...standard process as past months. Same platform tools, same TWRP. Magisk v18. ElementalX v4.10. Up and running. Root works fine. Experimenting with BlackenedMod3.0 now. But all seems to be fine on this update so far. Good luck to all.
sb1893 said:
I just flashed January Factory image...standard process as past months. Same platform tools, same TWRP. Magisk v18. ElementalX v4.10. Up and running. Root works fine. Experimenting with BlackenedMod3.0 now. But all seems to be fine on this update so far. Good luck to all.
Click to expand...
Click to collapse
TWRP just booted of flashed?
The last update I heard about bootloops when flashing recovery and magisk 18, atm I only boot recovery to avoid any kind of problem. For you works fine?
TENN3R said:
TWRP just booted of flashed?
The last update I heard about bootloops when flashing recovery and magisk 18, atm I only boot recovery to avoid any kind of problem. For you works fine?
Click to expand...
Click to collapse
I have always just booted TWRP - I never have flashed it. Sorry for the confusion.
Has anyone been able to root the January update with Magisk?
UPDATE:
I haven't had any boot loop issues after updating, flashing TWRP, and routing with Magisk, so I thought I would post my steps:
Note: My bootloader is unlocked.
Before updating, I flashed the Magisk Uninstaller zip.
Once completed, I rebooted to bootloader and flashed the January factory image (saving data) > booted TWRP > flashed TWRP > rebooted recovery > flashed Magisk 18.0 > rebooted.
I haven't had any boot loop issues.
Magisk is installed and passes Safety Net check, but I wasn't able to grant root privileges for apps right away. It took a while (5 minutes) to get the prompt to grant root privileges. Finally got the prompt and now everything seems to be working correctly.
I hope this helps someone!
Does anyone have the January pre-rooted boot.img?
BoboBrazil said:
Does anyone have the January pre-rooted boot.img?
Click to expand...
Click to collapse
Not handy anymore, I deleted the .zip once I updated. But you should be able to grab it from the Factory image .zip readily available on the Google Developers site.
sb1893 said:
Not handy anymore, I deleted the .zip once I updated. But you should be able to grab it from the Factory image .zip readily available on the Google Developers site.
Click to expand...
Click to collapse
I need it pre-rooted. I'm trying to root someone else's phone for them and would be easier to just be able to flash it than transferring, using magisk manager, then transferring back to flash.
^^^
This is a 1st.........never seen anyone ask for it........LoL
BoboBrazil said:
I need it pre-rooted. I'm trying to root someone else's phone for them and would be easier to just be able to flash it than transferring, using magisk manager, then transferring back to flash.
Click to expand...
Click to collapse
Sorry - my mistake - when you said "pre-rooted" I took that to mean "before rooted" - meaning the stock boot.img. Unfortunately, I do not have the Magisk rooted boot.img handy. But, it only takes a few minutes to root using the standard process with Magisk....might be quicker than waiting for a response to your request??? Just a thought...good luck...
crackerjack1957 said:
^^^
This is a 1st.........never seen anyone ask for it........LoL
Click to expand...
Click to collapse
Pretty common on the newer pixel and OnePlus forums. Someone usually shares it to save others some of the work