What I Did
1. I flashed the decrypt kernel for the N Beta through ADB
2. I did a factory reset to finish the decrypt process
3. I booted into TWRP using ADB (I did it this way to keep stock recovery, you can just flash TWRP if you like)
4. Once in TWRP, though ADB I typed "ADB Shell"
Then typed "echo SYSTEMLESS=true>>/data/.supersu"
Followed by "echo BINDSYSTEMXBIN=false>>/data/.supersu"
5. I proceeded to flash the latest Supersu Beta
6. Set up Android Pay and profit!
It is pretty much the exact process for Android Pay with Systemless root, but you do HAVE to have decrypted or else this will not work.
Screenshots or It Didn't Happen
Do you mind linking the decrypt kernel?
it simply works if you are stock and systemless rooted.
trebills said:
Do you mind linking the decrypt kernel?
Click to expand...
Click to collapse
No problem
http://forum.xda-developers.com/nexus-6p/general/stock-modified-boot-img-regular-root-t3306684
MrKaon said:
it simply works if you are stock and systemless rooted.
Click to expand...
Click to collapse
Yes exactly, but for now, there is no way to root unless you decrypt first
kingmikel said:
No problem
http://forum.xda-developers.com/nexus-6p/general/stock-modified-boot-img-regular-root-t3306684
Yes exactly, but for now, there is no way to root unless you decrypt first
Click to expand...
Click to collapse
I'm running the same setup but with Adaway and ElementalX Kernel. I was able to pay for coffe this morning
omf05 said:
I'm running the same setup but with Adaway and ElementalX Kernel. I was able to pay for coffe this morning
Click to expand...
Click to collapse
I'm still trying to get Adaway to work! And how's ElementalX running with the new preview? I have not tried it yet
kingmikel said:
I'm still trying to get Adaway to work! And how's ElementalX running with the new preview? I have not tried it yet
Click to expand...
Click to collapse
ElementalX is running fine for me so far, just use the version for DP2 and you should be fine..
I am system rooted with BusyBox and V4A installed and SELinux permissive on DP3. I haven't tested Android Pay, but I was able to add a card without a problem. Is that indicative that it should work? I had the opportunity to test it today but didn't.
Nitemare3219 said:
I am system rooted with BusyBox and V4A installed and SELinux permissive on DP3. I haven't tested Android Pay, but I was able to add a card without a problem. Is that indicative that it should work? I had the opportunity to test it today but didn't.
Click to expand...
Click to collapse
From my experience, if you successfully add a card then it works. Usually prevent you from adding a card. I also use Safetynet Helper Sample and make sure it passes
kingmikel said:
From my experience, if you successfully add a card then it works. Usually prevent you from adding a card. I also use Safetynet Helper Sample and make sure it passes
Click to expand...
Click to collapse
Fails the CTS check. I guess only way to know if to go try it out lol.
Nitemare3219 said:
Fails the CTS check. I guess only way to know if to go try it out lol.
Click to expand...
Click to collapse
Mine passes lol. I'm confused as to why it let you add a card!
kingmikel said:
Mine passes lol. I'm confused as to why it let you add a card!
Click to expand...
Click to collapse
Guy in the N development thread showed AP working for him and he is system rooted as well. Probably a bug... but it'd be nice if Google were allowing rooted users to use AP since they know we find workarounds anyway.
Nitemare3219 said:
Guy in the N development thread showed AP working for him and he is system rooted as well. Probably a bug... but it'd be nice if Google were allowing rooted users to use AP since they know we find workarounds anyway.
Click to expand...
Click to collapse
That guy was me. Passes safety net fine. All I did was root and added the card. Not sure probably a bug that will be fixed. Until then I'll enjoy not having to make any extra steps.
Don't like me......... BITE ME!!!
Nitemare3219 said:
Fails the CTS check. I guess only way to know if to go try it out lol.
Click to expand...
Click to collapse
Mine fails the step on N Beta 1 with systemless root. I haven't tried using pay though but I do have a card added.
Let me know if you try it and have success.
It is possible flash a custom kernel and still have Android pay working?
Enviado desde mi 6P
negrata said:
It is possible flash a custom kernel and still have Android pay working?
Enviado desde mi 6P
Click to expand...
Click to collapse
It works with current and prior Pure Nexus (MTC19T). Lately, I have flashed the FiFix_ Google Dialer zip (as noted by Beanstown) after the other steps to make Android Pay work. Using it on Rooted N now but just came from Pure Nexus.
Sent from my Nexus 6P using XDA-Developers mobile app
Related
Major credits again to @zachariahpope for the Lollipop build earlier tonight. Unfortunately getting it rooted from stock won't work. Which is why I proceeded to try the same method from my rooting guide to attempt root. And I am proud to say...I HAVE THE ROOTED LOLLIPOP SONY XPERIA Z3V!!!
And also, I have recovery as well.
If you're going to follow in the same footsteps, please PLEASE remember when you get the supersu file, grab the v2.49 as that is for LOLLIPOP.
@GigaSPX Make one of these in the development section too!!
well, looks like its time to flash
I thought this day would never come!!
Sent from my D6708 using Tapatalk
where is it? can I just root the phone when I Flash it back to stock root from there and not take the OTA and go straight to the pre-root for Lolipop?
GhostTrunks said:
where is it? can I just root the phone when I Flash it back to stock root from there and not take the OTA and go straight to the pre-root for Lolipop?
Click to expand...
Click to collapse
If you want root, you need to preroot. Otherwise, you won't have it at all.
Also this is an update: it seems it's still Verizon holding all of us by the edge about VoLTE. I tried activating it but it won't work. Still can't browse and call at the same time dammit.
Is this patched for Stagefright?
rooted lollipop for z3v ,,,,,,,,,, congrats
1linuxfreak said:
Is this patched for Stagefright?
Click to expand...
Click to collapse
Unfortunately... no.
GigaSPX said:
Unfortunately... no.
Click to expand...
Click to collapse
Giga, any success in actually using Advanced Calling? I can't seem to get it to work, even after "activating" it on the phone
srsaloom said:
Giga, any success in actually using Advanced Calling? I can't seem to get it to work, even after "activating" it on the phone
Click to expand...
Click to collapse
No, that's what I've been trying to tell a lot of people now. It's still all in the hands of the big red...
srsaloom said:
Giga, any success in actually using Advanced Calling? I can't seem to get it to work, even after "activating" it on the phone
Click to expand...
Click to collapse
You must also activate it from your vzw account.
GigaSPX said:
No, that's what I've been trying to tell a lot of people now. It's still all in the hands of the big red...
Click to expand...
Click to collapse
Figured so, just wasn't sure if I'd missed a memo somewhere along the way. Appreciate it!
Delebird said:
You must also activate it from your vzw account.
Click to expand...
Click to collapse
srsaloom said:
Figured so, just wasn't sure if I'd missed a memo somewhere along the way. Appreciate it!
Click to expand...
Click to collapse
Yeah, and can't activate it on the Verizon account when it won't let you to.
Has anyone tried installing Xposed? I can't flash to install.
GigaSPX said:
Has anyone tried installing Xposed? I can't flash to install.
Click to expand...
Click to collapse
Just installed it. v74-sdk21-arm . Gave me a little scare, as it hung on the Sony logo after rebooting. Also, upon that initial reboot, the lockscreen was vacant and couldn't get beyond what should've been there. Had to long-press power to bring up power menu and select reboot.
Following that, things seem to be working fine. Xposed Installer crashes if you click on xda support links in module pages, and the installation of xposed modules from within the Xposed installer can take significantly longer than it did on KK.
GigaSPX said:
No, that's what I've been trying to tell a lot of people now. It's still all in the hands of the big red...
Click to expand...
Click to collapse
Not sure if this helps, but, I jumped from this phone to the LG G4. We don't have much development but, some rooted users don't have advanced calling because they are rooted. I am a non-rooted user with advance calling. To add another variable to the equation, you have to have the My Verizon Mobile app installed and not disabled to at least initiate advanced calling. Some of the rooted users I think figured that out.
srsaloom said:
Just installed it. v74-sdk21-arm . Gave me a little scare, as it hung on the Sony logo after rebooting. Also, upon that initial reboot, the lockscreen was vacant and couldn't get beyond what should've been there. Had to long-press power to bring up power menu and select reboot.
Following that, things seem to be working fine. Xposed Installer crashes if you click on xda support links in module pages, and the installation of xposed modules from within the Xposed installer can take significantly longer than it did on KK.
Click to expand...
Click to collapse
Big thanks here. Fully updated now, and with this tip I'm running xposed as well.
Uninstalled old xposed first (may not have been necessary)
TWRP dirty flashed pre-rooted 5.0.2 zip from post 44 of that lollipop dev thread
After boot TWRP isntalled v74-sdk21-arm module
Installed xposed_installer.apk and added back my most used modules
-chromepie
-xtether (still working )
Didn't bother with xperiaxposed, not even sure if it's updated. Never really used it
Also, I like this boot animation, not that it's of any importance http://forum.xda-developers.com/z3/themes-apps/bootanimation-xperia-z3-t3079263
darker_slayer said:
Big thanks here. Fully updated now, and with this tip I'm running xposed as well.
Uninstalled old xposed first (may not have been necessary)
TWRP dirty flashed pre-rooted 5.0.2 zip from post 44 of that lollipop dev thread
After boot TWRP isntalled v74-sdk21-arm module
Installed xposed_installer.apk and added back my most used modules
-chromepie
-xtether (still working )
Didn't bother with xperiaxposed, not even sure if it's updated. Never really used it
Also, I like this boot animation, not that it's of any importance http://forum.xda-developers.com/z3/themes-apps/bootanimation-xperia-z3-t3079263
Click to expand...
Click to collapse
I did much the same but I did not uninstall xposed before I flashed and it wouldnt let me uninstall it after I upgraded to lollipop. But I flashed and installed the files above and it works great. Xperia Xposed works use v1.7 cause it's the only one that works.
Just wish there was a foolproof way to get rid of those useless small apps
darker_slayer said:
Just wish there was a foolproof way to get rid of those useless small apps
Click to expand...
Click to collapse
They're super useful to me, being all multitasking useful and all. loll
Files Credits: BadWolfYe
Reference thread: here
Note:-
-> Rooting may* void your phone warranty, and you won’t claim it back. (Honor India officials confirmed me that Rooting and bootloader unlocking doesnot voids the warranty).
-> Follow the steps correctly otherwise you may brick your device. I am not responsible for any damage of your phone.
-> Ensure that your phone has at least 50-60% charged to prevent the accidental shutdown in-between the process.
REQUIREMENTS(MUST)
1. Should have a custom recovery installed.
2. Should be rooted and SuperSu installed.
[Files needed to install custom recovery and flash Supersu in one package here.]
[Rooting Guide here ]
PROCEDURE
1. Boot in to twrp recovery(Vol.Up+Power) and Choose Install and flash the file here through twrp.
2. After installation Clear "dalvic cache" and reboot the system.
3. The reboot takes time(5-10minutes),so donot interfere the boot.
4. After bootup,install the apk from here.
;and Grant SuperSu access when prompted.
5. Now connect any pendrive via otg cable and see the magic.
Note: After installing the apk you can control the otg functionality using the Activate/Deactivate buttons in the App. Incase if the MTP or Charging doesnt work,press on Disconnect option in the app.
:fingers-crossed::laugh::fingers-crossed::laugh:HIT THANKS IF THIS HELPED YOU!:fingers-crossed::laugh::fingers-crossed::laugh:
nice guide
jkccl9 said:
nice guide
Click to expand...
Click to collapse
Check this and update here whether it worked in your device or not.
honor_ninja95 said:
Check this and update here whether it worked in your device or not.
Click to expand...
Click to collapse
Yep will do over the weekend
Can I try this on NEM-L21?
nucleuswizard said:
Can I try this on NEM-L21?
Click to expand...
Click to collapse
Yeah sure! It will work
good i a important developer
This should work in other Honor phones right?
Having conceived you duplicate already created subject???!!
http://forum.xda-developers.com/honor-5c/development/activation-support-otg-applications-t3471686
OOPS.. Without knowing the existence of this thread in ROM section I have done the same in Guides Section.
DRUGER said:
Having conceived you duplicate already created subject???!!
http://forum.xda-developers.com/honor-5c/development/activation-support-otg-applications-t3471686
Click to expand...
Click to collapse
No proper guides available... Thats why made this to make it simple.. Also given proper reference threads
DRUGER said:
Having conceived you duplicate already created subject???!!
http://forum.xda-developers.com/honor-5c/development/activation-support-otg-applications-t3471686
Click to expand...
Click to collapse
BadWolfYe said:
good i a important developer
Click to expand...
Click to collapse
Already given credits to you master !
honor_ninja95 said:
No proper guides available... Thats why made this to make it simple.. Also given proper reference threads
Click to expand...
Click to collapse
You did the right thing.
Can anyone give me confirmation regarding the working of these mods on other models?
please make a video and share that we will get clear idea regarding OTG enable in honor 5C
Hello, the apk doesn't ask SuperSu for root permission. I have a NEM-L51 rooted, and the app is telling me that root permission is necessary, but never asks for it.
An idea on how to fix that, plz ?
otg isn't working
my otg cable is not working. I flashes this zip file and installed otg app with supersu grant permission. thereafter its not working. It can't show any otg drive in my file manager. Anyone has any solution???
nucleuswizard said:
Can I try this on NEM-L21?
Click to expand...
Click to collapse
is it work well on NEM-L21 ?
Sent from my NEM-L21 using Tapatalk
Zhyrclew said:
Hello, the apk doesn't ask SuperSu for root permission. I have a NEM-L51 rooted, and the app is telling me that root permission is necessary, but never asks for it.
An idea on how to fix that, plz ?
Click to expand...
Click to collapse
In previous posts someone solved it for me. For some reason the latest supersu doesn't work. Root your phone with older version. I routed with Super su 2.65. Then flash the zip and reboot. It should work, did for me. Then install the latest super su 2.79 and it should remain working. Although a couple of times it forgot it has root after flashing the latest supersu. Just repeat steps again..
Hope this helps..and don't thank me,thank the person who posted the solution but you'll have to read a few threads....:silly:
Yes, i confirm that this manipulation does solve the problem. I did it following the advice i got on this thread. I must still thank you for spending time answering me.
I think i'll have to repeat the operation shorlty anyway, because i had to unroot my device to install a system update, and now i have to root it again ^.^
I made a video on how to to Install TWRP, Busybox and SuperSU to your Asus ZenWatch 2. Let me know what you guys think.
https://www.youtube.com/watch?v=2YB0rz98tS0&feature=youtu.be
Edit: This works on 2.0 as well!
Unroot: https://www.youtube.com/watch?v=C77cHOjXo_g
Poebat said:
I made a video on how to to Install TWRP, Busybox and SuperSU to your Asus ZenWatch 2. Let me know what you guys think.
https://www.youtube.com/watch?v=2YB0rz98tS0&feature=youtu.be
Click to expand...
Click to collapse
Could use some help--i can get TWRP installed fine, even install Supersu. It just doesn't "take". https://forum.xda-developers.com/zenwatch-2/help/tried-everything-to-root-sparrow-twrp-3-t3614177
jaysonic88 said:
Could use some help--i can get TWRP installed fine, even install Supersu. It just doesn't "take". https://forum.xda-developers.com/zenwatch-2/help/tried-everything-to-root-sparrow-twrp-3-t3614177
Click to expand...
Click to collapse
Resolved it. Had to mount system to get it to stick.
@Poebat
Nice tutorial?
yash92duster said:
@Poebat
Nice tutorial?
Click to expand...
Click to collapse
Thanks!
can I use this guide also for Android Wear 2.0 ?
milanored said:
can I use this guide also for Android Wear 2.0 ?
Click to expand...
Click to collapse
No, I think the SuperSU I used in the video is for AW 1.5. You can try just make a backup before you do it
but the recovery should work with AW2.0 ?!
milanored said:
but the recovery should work with AW2.0 ?!
Click to expand...
Click to collapse
Correct
I confirmed that the recovery still works with AW2.0. The SuperSU and busybox zip fails to flash. I flashed the latest stable SuperSU zip and it flashes completely, but the SuperSU app does not open and the watch hangs up when asking for root. I flashed the latest Stericson busybox zip, but obviously I can't test if it installed without su.
Poebat said:
I made a video on how to to Install TWRP, Busybox and SuperSU to your Asus ZenWatch 2. Let me know what you guys think.
https://www.youtube.com/watch?v=2YB0rz98tS0&feature=youtu.be
Click to expand...
Click to collapse
Everytime I try to install I keep getting an error and this is after flashing to stock, reinstalling twrp and trying again.
Keep in mind I'm trying to root 1.5 not 2.0
GTDarthYoda said:
Everytime I try to install I keep getting an error and this is after flashing to stock, reinstalling twrp and trying again.
Keep in mind I'm trying to root 1.5 not 2.0
Click to expand...
Click to collapse
What are you trying to install?
Poebat said:
What are you trying to install?
Click to expand...
Click to collapse
https://forum.xda-developers.com/apps/supersu/android-wear-6-0-1-root-squashfs-t3319097
GTDarthYoda said:
https://forum.xda-developers.com/apps/supersu/android-wear-6-0-1-root-squashfs-t3319097
Click to expand...
Click to collapse
That's really odd. Are you running a stock ROM? How much free space do you have? Can you flash busybox?
Stock, wiped, stock, still nothing.
Edit:
Busy box installed
Edit:
Tried SuperSU again. no luck
I have the same problem with AW2.0. Root works after flashing the latest SuperSU but the SuperSU app itself won't open.
Gfhoihoi72 said:
I have the same problem with AW2.0. Root works after flashing the latest SuperSU but the SuperSU app itself won't open.
Click to expand...
Click to collapse
Zip from this post did the trick.
https://forum.xda-developers.com/showpost.php?p=73165371&postcount=66
It appears the issue stems from the filesystem being squashfs. I've dealt with squashfs in the past, and it doesn't allow modification due to it's structure. The system needs to be un-squashed, modified, then re-squashed. There is a ROM for the LG watch where the developer converted it to ext4, but that requires editing partitions on the watch. I'm considering converting this to ext4, but I'm not thrilled with the idea of a hard brick.
Hmmmm very very strange, after some reboots the twrp recovery is gone.
The watch boots in the stock recovery.
Is it because this is an 1.5 version?
This is kind of storytime... I got the application by redeeming a code that was posted as a gift on their fanpage at Facebook. I had to sent them via Telegram the Google play ID order, something that I couldn't find. I explained that and they understood me and said that if I could send the code that I got the application, they are gonna send be the actual files. So I received the files and I'm ready to begin! I don't have much spare time so I'm gonna do this whenever I have the time to do so. Wish me luck! I'm gonna keep you guys updated and let you know what happened.
Andriano24 said:
This is kind of storytime... I got the application by redeeming a code that was posted as a gift on their fanpage at Facebook. I had to sent them via Telegram the Google play ID order, something that I couldn't find. I explained that and they understood me and said that if I could send the code that I got the application, they are gonna send be the actual files. So I received the files and I'm ready to begin! I don't have much spare time so I'm gonna do this whenever I have the time to do so. Wish me luck! I'm gonna keep you guys updated and let you know what happened.
Click to expand...
Click to collapse
knox to 0x0?
DaniPS2002 said:
knox to 0x0?
Click to expand...
Click to collapse
Yeah that's what the app suppose to do
Andriano24 said:
Yeah that's what the app suppose to do
Click to expand...
Click to collapse
the app name is knox reset 0x0 (0)?
DaniPS2002 said:
the app name is knox reset 0x0 (0)?
Click to expand...
Click to collapse
Yes
Okay, let we know!
MarcusBS said:
Okay, let we know!
Click to expand...
Click to collapse
I've stuck in a step. Sadly I cannot complete now the instructions given because I can't turn the systemless root into system mode
Andriano24 said:
I've stuck in a step. Sadly I cannot complete now the instructions given because I can't turn the systemless root into system mode
Click to expand...
Click to collapse
What do you mean you can't turn systemless root into system mode?
ashyx said:
What do you mean you can't turn systemless root into system mode?
Click to expand...
Click to collapse
https://android.stackexchange.com/q...om-systemless-root-to-system-traditional-root
Check that out
Andriano24 said:
https://android.stackexchange.com/q...om-systemless-root-to-system-traditional-root
Check that out
Click to expand...
Click to collapse
I actually meant what is preventing you from installing supersu in system mode, it's simple enough? Also which device is this?
ashyx said:
I actually meant what is preventing you from installing supersu in system mode, it's simple enough? Also which device is this?
Click to expand...
Click to collapse
I flash the super su, then try to full unroot, my phone reboots and I press the combination of keys to go to twrp recovery, go to terminal thingy, type the code and the last step I do is flashing again the supersu. But then I boot into system I stuck on the logo screen
Andriano24 said:
I flash the super su, then try to full unroot, my phone reboots and I press the combination of keys to go to twrp recovery, go to terminal thingy, type the code and the last step I do is flashing again the supersu. But then I boot into system I stuck on the logo screen
Click to expand...
Click to collapse
You've lost me Tbh. I don't understand what steps you are performing and why.
Type what code?
ashyx said:
You've lost me Tbh. I don't understand what steps you are performing and why.
Type what code?
Click to expand...
Click to collapse
Didn't you see the post I send you? The "code" is
Echo SYSTEMLESS=false > /data/.supersu
Andriano24 said:
Didn't you see the post I send you? The "code" is
Echo SYSTEMLESS=false > /data/.supersu
Click to expand...
Click to collapse
OK first things first. You have to reinstall SuperSu for that code to work AND a patched boot.img.
Second for what reason do you need SuperSU to be in system mode?
[Deleted by me]
ashyx said:
OK first things first. You have to reinstall SuperSu for that code to work AND a patched boot.img.
Second for what reason do you need SuperSU to be in system mode?
Click to expand...
Click to collapse
Thank you for your time. But can you wrote the full steps below? Because I'm tired of getting into a bootloop only because I am not able to understand the instructions! You can do it only of you want to!
Secondary, the Knox Reset app has a plugin to make the success rate bigger of turning the 0x1 back to 0x0 (as far as I know) and the plugin needs system mode root :/
Lol right now I'm not rooted because I'm tired of the bootloops while rying to system mode root
Andriano24 said:
Lol right now I'm not rooted because I'm tired of the bootloops while rying to system mode root
Click to expand...
Click to collapse
Easiest way is to reroot systemless. After rooting back up the boot partition with TWRP.
Unroot then install SuperSU in system mode.
Finally restore the boot.img from the backup.
Reboot.
Note also be aware that system mode root is hit and miss on devices running nougat.
You still haven't stated which device?
ashyx said:
Easiest way is to reroot systemless. After rooting back up the boot partition with TWRP.
Unroot then install SuperSU in system mode.
Finally restore the boot.img from the backup.
Reboot.
Note also be aware that system mode root is hit and miss on devices running nougat.
You still haven't stated which device?
Click to expand...
Click to collapse
Oh sorry I forgot about that! I have the Samsung galaxy A5 2017 running...... nougat.....
Andriano24 said:
Oh sorry I forgot about that! I have the Samsung galaxy A5 2017 running...... nougat.....
Click to expand...
Click to collapse
Then you have a 50/50 chance of root working in system mode.
Also tbh I think this knox app is fake or it just fakes knox to 0x0 the same way Magisk can.
It's up and here https://developers.google.com/android/ota
gm007 said:
It's up and here https://developers.google.com/android/ota
Click to expand...
Click to collapse
Changelog?
Sent from my Pixel 3 using Tapatalk
nickporwal said:
Changelog?
Click to expand...
Click to collapse
https://source.android.com/security/bulletin/pixel/2018-12-01.html
One of this days the 'Check for Update' button will work damn it! Hahahaha
Hahaha right, I have been flashing the OTA manually, its no biggie for me I am used to manually flashing the ota now
AntLyoN2053 said:
One of this days the 'Check for Update' button will work damn it! Hahahaha
Click to expand...
Click to collapse
Can anybody sucessfully root again?
Just flash-all works fine, but after flashing magisk 17.3 again and reboot, phone instant restarts to recovery and tells me devices is corrupt.
AntLyoN2053 said:
One of this days the 'Check for Update' button will work damn it! Hahahaha
Click to expand...
Click to collapse
I got it through ota 1 hour ago.
gm007 said:
I got it through ota 1 hour ago.
Click to expand...
Click to collapse
You know Im mashing the button, lol. Only google phone that got all the updates pretty much same day was the Nexus 6P, I used to get the update notification even before any site would announce that it was out
Bluffer94 said:
Can anybody sucessfully root again?
Just flash-all works fine, but after flashing magisk 17.3 again and reboot, phone instant restarts to recovery and tells me devices is corrupt.
Click to expand...
Click to collapse
Same, not able to root with beta or canary builds atm.. seems to just boot back to twrp every time.
sulpher said:
Same, not able to root with beta or canary builds atm.. seems to just boot back to twrp every time.
Click to expand...
Click to collapse
I've rooted with 17.3 without a problem. Are you just booting into twrp, not flashing it?
Sent from my [device_name] using XDA-Developers Legacy app
Bluffer94 said:
Can anybody sucessfully root again?
Just flash-all works fine, but after flashing magisk 17.3 again and reboot, phone instant restarts to recovery and tells me devices is corrupt.
Click to expand...
Click to collapse
sulpher said:
Same, not able to root with beta or canary builds atm.. seems to just boot back to twrp every time.
Click to expand...
Click to collapse
Do you have the Magisk uninstaller on your phone? Run it from the temp TWRP .img, and then it should boot OK. Go back to temp TWRP, and install Magisk again. The Edge Sense Plus module is broken again. Don not reinstall it until fixed.
Bluffer94 said:
Can anybody sucessfully root again?
Just flash-all works fine, but after flashing magisk 17.3 again and reboot, phone instant restarts to recovery and tells me devices is corrupt.
Click to expand...
Click to collapse
sulpher said:
Same, not able to root with beta or canary builds atm.. seems to just boot back to twrp every time.
Click to expand...
Click to collapse
Flash all after removing the -w, rebooted and let it finish. Boot to TWRP and installed the latest canary. Did not install TWRP.
All good.
jd1639 said:
I've rooted with 17.3 without a problem. Are you just booting into twrp, not flashing it?
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Ah figured it out, edge sense broken.
edit- thanks guys~
sulpher said:
Ah figured it out, edge sense broken.
Click to expand...
Click to collapse
There's no magic. I sideload the ota in the stock recovery. Booted into the system to make sure everything worked. Powered off the device and booted into the bootloader. Then booted twrp and flashed magisk. Then booted into the system. That's it.
Sent from my [device_name] using XDA-Developers Legacy app
No OTA here... It usually comes days later with unlocked Google pixel using TMobile. -.-
Installed the full version to update it, root just after and everything's fine!
There is only the edge sense that is'nt working as already told
TWRP keeps getting error 1 when flashing the OTA, bit odd
The TWRP for this device has never been able to side-load the OTA it always errors out. I just use the full firmware and take out the -w and all good.
laill said:
TWRP keeps getting error 1 when flashing the OTA, bit odd
Click to expand...
Click to collapse
Archangel said:
The TWRP for this device has never been able to side-load the OTA it always errors out. I just use the full firmware and take out the -w and all good.
Click to expand...
Click to collapse
So then how do we flash the OTA and keep root? Pardon my ignorance on the matter but taking out the -w, do you mean through terminal on the device or flashing with adb or something? Just need a little more detail.
I am used to putting the OTA on the device and flashing through TWRP then flashing TWRP&Magisk again before a full restart.
Once again I am new to this style of flashing so sorry for asking a dumb question.
What I do is download the full updated firmware, unzip that in your platform tools folder,,,make sure you also unzip the second zip inside there as well. If you have the Pixel edge module installed uninstall it and I also uninstalled Magisk in TWRP before I updated just in case there were any problems. Then find the flash-all.bat file in your platform tools folder, right click on it, open with notepad+ and find the -w at the bottom and delete it. After this, save the flash-all.bat notepad xml file and do not just close it. You can then flash the full firmware without it deleting your user data. After this you will have to fastboot boot TWRP and flash the TWRP zip over again. I rebooted then used TWRP to flash the Magisk 17.1 zip. I am up and running and did the same thing last month for the Nov update,,,hope this helps.
Rumsfield said:
So then how do we flash the OTA and keep root? Pardon my ignorance on the matter but taking out the -w, do you mean through terminal on the device or flashing with adb or something? Just need a little more detail.
I am used to putting the OTA on the device and flashing through TWRP then flashing TWRP&Magisk again before a full restart.
Once again I am new to this style of flashing so sorry for asking a dumb question.
Click to expand...
Click to collapse