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?
Related
Hello,
I have a rooted Iocean G7.
I wanted to install the framework module with the Xposed installer app. This was no success, I got a bootloop. After this I contacted Iocean, and I have flashed my phone with the computer. It works fine now, as it should.
Now my question is, how can I install the framework module without getting a bootloop or other problems?
Thank you,
Robert
Not compatible with your device maybe.
XperienceD said:
Not compatible with your device maybe.
Click to expand...
Click to collapse
That could be possible, I am going to ask to rovo98, if he can make framework compactible with my phone.
I hope he wants to do
On Tweakers they think that the Rom is not compactible, but I do not think so... You?
-RobertNL- said:
That could be possible, I am going to ask to rovo98, if he can make framework compactible with my phone.
I hope he wants to do
On Tweakers they think that the Rom is not compactible, but I do not think so... You?
Click to expand...
Click to collapse
Did you ask him already? Could you tell me the development process of that.
Thank you.
-RobertNL- said:
Hello,
I have a rooted Iocean G7.
I wanted to install the framework module with the Xposed installer app. This was no success, I got a bootloop. After this I contacted Iocean, and I have flashed my phone with the computer. It works fine now, as it should.
Now my question is, how can I install the framework module without getting a bootloop or other problems?
Thank you,
Robert
Click to expand...
Click to collapse
Hi Robert
I did the same thing as you...except that I have not been able to fix it. Can you please describe to me exactly how you reflashed your phone please?
Thanks in advance!
Sanxion said:
Hi Robert
I did the same thing as you...except that I have not been able to fix it. Can you please describe to me exactly how you reflashed your phone please?
Thanks in advance!
Click to expand...
Click to collapse
You guys know that Xposed puts a framework disabler zip on your internal storage? All you have to do is boot into a custom recovery and install it.
es0tericcha0s said:
You guys know that Xposed puts a framework disabler zip on your internal storage? All you have to do is boot into a custom recovery and install it.
Click to expand...
Click to collapse
Unfortunately, I don't have a custom recovery installed. My phone is literally out of the box.
Sanxion said:
Unfortunately, I don't have a custom recovery installed. My phone is literally out of the box.
Click to expand...
Click to collapse
https://mega.co.nz/#!pppliCCK!09s525-EUAU2Uy7yqwMvFfm0RwyboUCFoY4yvq7pa80 - Recovery from here: http://www.needrom.com/mobile/iocean-g7-miui/#comments
https://www.youtube.com/watch?v=IXYYbDPfk48 - Install Guide
I do not have this phone, so have no way to test. You attempt at your own risk.
es0tericcha0s said:
https://mega.co.nz/#!pppliCCK!09s525-EUAU2Uy7yqwMvFfm0RwyboUCFoY4yvq7pa80 - Recovery from here: http://www.needrom.com/mobile/iocean-g7-miui/#comments
https://www.youtube.com/watch?v=IXYYbDPfk48 - Install Guide
I do not have this phone, so have no way to test. You attempt at your own risk.
Click to expand...
Click to collapse
Thank-you...will this work even though I did not enable usb debugging on my phone?
Sanxion said:
Thank-you...will this work even though I did not enable usb debugging on my phone?
Click to expand...
Click to collapse
What root method did you do that didn't require USB Debugging to be enabled?? But yea, I dunno about that. You're going to have to find out though. You'll need the SP Flash Tool to work, whether it's to install the custom recovery, or to install the entire stock firmware.
es0tericcha0s said:
What root method did you do that didn't require USB Debugging to be enabled?? But yea, I dunno about that. You're going to have to find out though. You'll need the SP Flash Tool to work, whether it's to install the custom recovery, or to install the entire stock rom.
Click to expand...
Click to collapse
There is a 'Super User' setting in Settings which I enabled.
I tried installing PdaNet but that does require USB debugging to complete the installation.
Isn't there a standard recovery mode on these phones that I can use (combination key press) to install a rom copied onto the SD card?
Sanxion said:
There is a 'Super User' setting in Settings which I enabled.
I tried installing PdaNet but that does require USB debugging to complete the installation.
Isn't there a standard recovery mode on these phones that I can use (combination key press) to install a rom copied onto the SD card?
Click to expand...
Click to collapse
That's pretty handy. But no, the stock recovery does not support that. You might be able to get out of it just from doing a factory reset in the stock recovery, but it's hard to say since Xposed makes changes to /system as well and the factory data reset does not affect the /system partition, just /data
es0tericcha0s said:
That's pretty handy. But no, the stock recovery does not support that. You might be able to get out of it just from doing a factory reset in the stock recovery, but it's hard to say since Xposed makes changes to /system as well and the factory data reset does not affect the /system partition, just /data
Click to expand...
Click to collapse
Ok...how do I access the "stock recovery"?
Sanxion said:
Ok...how do I access the "stock recovery"?
Click to expand...
Click to collapse
It's in the comments to the needrom thread I linked to.
es0tericcha0s said:
It's in the comments to the needrom thread I linked to.
Click to expand...
Click to collapse
Thanks...I have fixed it...strangely the PdaNet drivers worked when I turned my phone on...from there I was able to install MTK tools, then cwm recovery, wiped dalvik etc and did a reset...all fine now.
-RobertNL- said:
Hello,
I have a rooted Iocean G7.
I wanted to install the framework module with the Xposed installer app. This was no success, I got a bootloop. After this I contacted Iocean, and I have flashed my phone with the computer. It works fine now, as it should.
Now my question is, how can I install the framework module without getting a bootloop or other problems?
Thank you,
Robert
Click to expand...
Click to collapse
hi good day how to root iocean g7
anyone have any luck getting it to work?
Yes. Refer to this thread
http://forum.xda-developers.com/showthread.php?t=3074586
[EXPERIMENTAL] [UNOFFICIAL] Xposed for arm64 devices | 5.1 and 5.0 versions available
thicklizard said:
Yes. Refer to this thread
http://forum.xda-developers.com/showthread.php?t=3074586
[EXPERIMENTAL] [UNOFFICIAL] Xposed for arm64 devices | 5.1 and 5.0 versions available
Click to expand...
Click to collapse
I tried both zip files and both failed to install
Part of the reason I haven't taken mine out of the box yet.
jpwhre said:
I tried both zip files and both failed to install
Click to expand...
Click to collapse
Well what errors does it give you? Do you have a recovery log? I've been using it for almost a week now and it's working flawlessly
thicklizard said:
Well what errors does it give you? Do you have a recovery log? I've been using it for almost a week now and it's working flawlessly
Click to expand...
Click to collapse
any lagging for you?
trev23sks said:
any lagging for you?
Click to expand...
Click to collapse
So far none at all. I am only using a few modules though
Deleted, took up way to much space here for a log file
Are you using captain throwbacks beta twrp? You need to mount system is seems. If your using captains twrp just go to mount in twrp and select system
thicklizard said:
Are you using captain throwbacks beta twrp? You need to mount system is seems. If your using captains twrp just go to mount in twrp and select system
Click to expand...
Click to collapse
Did this http://forum.xda-developers.com/one-m9/orig-development/recovery-twrp-touch-recovery-t3066720
Ended up with this http://forum.xda-developers.com/showpost.php?p=60059404&postcount=30
Going into mount, there is no option for system
jpwhre said:
Did this http://forum.xda-developers.com/one-m9/orig-development/recovery-twrp-touch-recovery-t3066720
Ended up with this http://forum.xda-developers.com/showpost.php?p=60059404&postcount=30
Going into mount, there is no option for system
Click to expand...
Click to collapse
Then if you didn't use the beta version you need to issue the command to mount
http://forum.xda-developers.com/showthread.php?p=59759441
thicklizard said:
So far none at all. I am only using a few modules though
Click to expand...
Click to collapse
Dope! what Rom are you using? You still on stock ota? or you flashed viper?
trev23sks said:
Dope! what Rom are you using? You still on stock ota? or you flashed viper?
Click to expand...
Click to collapse
Stock
thicklizard said:
Then if you didn't use the beta version you need to issue the command to mount
http://forum.xda-developers.com/showthread.php?p=59759441
Click to expand...
Click to collapse
yeah so i thought i done the beta version, guess i didn't clearly read the thread and ended up flashing official and things went wrong from there.
Wouldn't let me do a backup, still showed divice as untuched, but wouldn't let me backup. After the official clean backup was released here, i downloaded it.
Tired of waiting, i went ahead and flashed beta superSU "before seeing the command block" and now i issue the command, and it takes, but it wont mount as system, and now device shows that it has been tampered.
I already know what is going to happen.
fastboot oem lock
RUU
start all over with everything wiped :victory:
or flash captn beta twrp and hope it fixes it.
Tomorrow I'll stop procrastinating......
Hey guys, Kyle here. I'm unlocked/running latest beta TWRP/rooted/S-OFF on stock and I can't seem to get this working. The apk and zip install fine but it bootloops after the install. Anything I can provide or any insight I can get?
For anyone having issues with xposed bootlooping after S-off flash the zip linked below. What happened with S-off is it triggered hrdump to create a 3gb backup of the devices ram into data. the zip will remove the dump and the bin file causing this.
Flash the zip linked below
Boot back into system
then go back into recovery and flash xposed for arm64 sdk21 and you should be good
The only issue we've noticed is with stock odexed roms. you can try and post what happens but we've only seen it work on all other deodexed roms.
Xposed fix for S-off users.
steal25 said:
For anyone having issues with xposed bootlooping after S-off flash the zip linked below. What happened with S-off is it triggered hrdump to create a 3gb backup of the devices ram into data. the zip will remove the dump and the bin file causing this.
Flash the zip linked below
Boot back into system
then go back into recovery and flash xposed for arm64 sdk21 and you should be good
The only issue we've noticed is with stock odexed roms. you can try and post what happens but we've only seen it work on all other deodexed roms.
Xposed fix for S-off users.
Click to expand...
Click to collapse
After flashing this system.ui force closes... among other things...
Sent from my SM-T217S using Tapatalk
steal25 said:
For anyone having issues with xposed bootlooping after S-off flash the zip linked below. What happened with S-off is it triggered hrdump to create a 3gb backup of the devices ram into data. the zip will remove the dump and the bin file causing this.
Flash the zip linked below
Boot back into system
then go back into recovery and flash xposed for arm64 sdk21 and you should be good
The only issue we've noticed is with stock odexed roms. you can try and post what happens but we've only seen it work on all other deodexed roms.
Xposed fix for S-off users.
Click to expand...
Click to collapse
Went through the steps and ended up having to download the apk 2.71 and got the result in the pic. I feel is so close but I'm missing something
motoelliot said:
After flashing this system.ui force closes... among other things...
Sent from my SM-T217S using Tapatalk
Click to expand...
Click to collapse
I'll bet your using a theme? The new Apktool is causing issues where it's not reinjecting the classes.dex it's fine after you flash the theme because dalvik is built. But this zip wipes dalvik so being that there's no classes it won't rebuild. Hence the fcs. This is just a guess.
knightwolf123 said:
Went through the steps and ended up having to download the apk 2.71 and got the result in the pic. I feel is so close but I'm missing something
Click to expand...
Click to collapse
Download the latest alpha apk and you should be good.
Hello Geeks,
I flashed the twrp and installed SU(att htc m9), initially i got Super SU, but after a pushing the new camera RUU update, i am unable to get the root on the device.
It gives me an error saying "No SU binaries present, SuperSU cannot install them..
What is the way that i can regain root on the device? NO S-OFF made on the device
yashwanthl92 said:
Hello Geeks,
I flashed the twrp and installed SU(att htc m9), initially i got Super SU, but after a pushing the new camera RUU update, i am unable to get the root on the device.
It gives me an error saying "No SU binaries present, SuperSU cannot install them..
What is the way that i can regain root on the device? NO S-OFF made on the device
Click to expand...
Click to collapse
Did you install the latest su
SU Binaries
Yes v2.46!
BR7fan said:
Did you install the latest su
Click to expand...
Click to collapse
Back to Stock
Can you help me in bringing my device back to as it was? like with original ATT ROM(1.32.502.9) unrooted?
Please help, with steps!
BR7fan said:
Did you install the latest su
Click to expand...
Click to collapse
yashwanthl92 said:
Can you help me in bringing my device back to as it was? like with original ATT ROM(1.32.502.9) unrooted?
Please help, with steps!
Click to expand...
Click to collapse
Put stock recovery back in . if you need tutorial link I'll give you one
Follow these instructions
Yes I did that! later how to gain root access?
Install the latest version and may try the paid version
ROOT
Yes I did that! later how to gain root access now?
BR7fan said:
Put stock recovery back in . if you need tutorial link I'll give you one
Follow these instructions
Click to expand...
Click to collapse
I tried even that...it says su binaries are missing and super su cannot install them.
I even tried via twrp and installing super su, it didnt work!
AbhishekMittal29 said:
Install the latest version and may try the paid version
Click to expand...
Click to collapse
yashwanthl92 said:
Yes I did that! later how to gain root access now?
Click to expand...
Click to collapse
Install TWRP and use the latest su in the link I provided in earlier post.
Which phone?
oh its working with the newer version of su? Thanks will try and check on
BR7fan said:
Install TWRP and use the latest su in the link I provided in earlier post.
Click to expand...
Click to collapse
Kingroot has root privilege not SuperSU, it says, install SU binary I don't know how to replace it.... Installed latest superSU as well, but the problem still persist
Sent from my Lenovo A6000 using XDA Free mobile app
I own an Honor 5x, which I used to have rooted running a TWRP recovery and SuperSU. I wanted to update my phone to marshmallow, but it was an OTA update so i had to unroot and go back to the original bootloader. I did everything needed and got my phone upgraded to marshmallow, and was then hoping i could play pokemon go, but for some reason i am getting the error where it says the game does not support my device, the exact same one that i got when i was rooted. i double checked that i was unrooted by downloading literally every single root checking app on the play store, and all of them have classed my phone as unrooted. i dont want to root my phone again as i have nox for rooted stuff now, and it was a hassle extracting th e recovery.img from the update file as noboby else had it, so i was wondering someone here could help me
thanks in advance!:good:
Honor 5x guy said:
I own an Honor 5x, which I used to have rooted running a TWRP recovery and SuperSU. I wanted to update my phone to marshmallow, but it was an OTA update so i had to unroot and go back to the original bootloader. I did everything needed and got my phone upgraded to marshmallow, and was then hoping i could play pokemon go, but for some reason i am getting the error where it says the game does not support my device, the exact same one that i got when i was rooted. i double checked that i was unrooted by downloading literally every single root checking app on the play store, and all of them have classed my phone as unrooted. i dont want to root my phone again as i have nox for rooted stuff now, and it was a hassle extracting th e recovery.img from the update file as noboby else had it, so i was wondering someone here could help me
thanks in advance!:good:
Click to expand...
Click to collapse
OTA update does not wipe the entire phone, you need to download the full update and manually wipe your phone and install the Full update to totally remove SuperSu.
You could also uninstall SuperSU from the apps settings before taking the OTA to avoid this problem
clsA said:
OTA update does not wipe the entire phone, you need to download the full update and manually wipe your phone and install the Full update to totally remove SuperSu.
You could also uninstall SuperSU from the apps settings before taking the OTA to avoid this problem
Click to expand...
Click to collapse
So what should I do now, I had already downloaded the update thinking it would fix it. I guess I try to manually uninstall it, seeing as the supersu app has already gone?
Honor 5x guy said:
So what should I do now, I had already downloaded the update thinking it would fix it. I guess I try to manually uninstall it, seeing as the supersu app has already gone?
Click to expand...
Click to collapse
install supersu and choose to uninstall it from the app
clsA said:
install supersu and choose to uninstall it from the app
Click to expand...
Click to collapse
Okay , if this works I love you.
clsA said:
install supersu and choose to uninstall it from the app
Click to expand...
Click to collapse
It won't let me enter the supersu app it's telling me there's no supersu binary.
Honor 5x guy said:
It won't let me enter the supersu app it's telling me there's no supersu binary.
Click to expand...
Click to collapse
are you flashing superSU from custom recovery first ?
clsA said:
are you flashing superSU from custom recovery first ?
Click to expand...
Click to collapse
No, I have a stock recovery ATM, to play Pokemon go you need to be unrooted but somehow I am detected as rooted
Honor 5x guy said:
No, I have a stock recovery ATM, to play Pokemon go you need to be unrooted but somehow I am detected as rooted
Click to expand...
Click to collapse
Two possible ways imo...
If you don't want to root then
Extract and manually flash stock boot.img, Cust.img and system.img and you are good to go without any data loss (but make a backup to be sure if something goes wrong).
Second is to root your phone, and use an app like 'hide my root' to hide your root from Pokemon go and you are good to go.
The third is to root and unroot using the inbuilt function of SuperSU.
muradulislam said:
Two possible ways imo...
If you don't want to root then
Extract and manually flash stock boot.img, Cust.img and system.img and you are good to go without any data loss (but make a backup to be sure if something goes wrong).
Second is to root your phone, and use an app like 'hide my root' to hide your root from Pokemon go and you are good to go.
The third is to root and unroot using the inbuilt function of SuperSU.
Click to expand...
Click to collapse
Thanks you so much . I will try these methods .
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