Just got my nexus 5x a few weeks ago through google fi, got the phone rooted and TWRP installed. Got a message saying that an update was available, it downloaded and i restarted. Next time I looked at the phone it had loaded into TWRP. I booted into system, and the phone is still on 7.1.1, and if I try to run an update check it comes back saying I'm up to date... Anyone else have that issue, or suggestions?
pinkydw said:
Just got my nexus 5x a few weeks ago through google fi, got the phone rooted and TWRP installed. Got a message saying that an update was available, it downloaded and i restarted. Next time I looked at the phone it had loaded into TWRP. I booted into system, and the phone is still on 7.1.1, and if I try to run an update check it comes back saying I'm up to date... Anyone else have that issue, or suggestions?
Click to expand...
Click to collapse
It was your root and TWRP that prevented 7.1.2 update. Either flash factory images or use flashfire app to update..
indian84 said:
It was your root and TWRP that prevented 7.1.2 update. Either flash factory images or use flashfire app to update..
Click to expand...
Click to collapse
Thanks, I'll look at the flashfire. I'm debating trying lineageOS, but I'm hesitant to mess with a new phone too much.
https://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
Check out section 9. I do this with every new release and it works fine. I flash the files followed by TWRP and then Magisk/SuperSU
The1nonly1 said:
https://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
Check out section 9. I do this with every new release and it works fine. I flash the files followed by TWRP and then Magisk/SuperSU
Click to expand...
Click to collapse
Oooohhhh, Danke! I think I used that guide when I rooted my phone to begin with.
Ok, dumb question, if I flash the OTA image, does that wipe data?
pinkydw said:
Ok, dumb question, if I flash the OTA image, does that wipe data?
Click to expand...
Click to collapse
No, if you follow step 9 and not the others, you will keep all data. You do need to download the whole factory image and not the OTA as you cant use that to update since you are rooted and have TWRP installed. Use this link for the latest image - https://developers.google.com/android/images?hl=en#bullhead
The1nonly1 said:
No, if you follow step 9 and not the others, you will keep all data. You do need to download the whole factory image and not the OTA as you cant use that to update since you are rooted and have TWRP installed. Use this link for the latest image - https://developers.google.com/android/images?hl=en#bullhead
Click to expand...
Click to collapse
Finally got around to trying this, there was no cache file, does it take a while to load? Its got pass the google logo and doing the weird 4 circle animation thing.
https://forum.xda-developers.com/showpost.php?p=71723898&postcount=1744
I think this guy had the same issue, going to try his suggestion.
pinkydw said:
https://forum.xda-developers.com/showpost.php?p=71723898&postcount=1744
I think this guy had the same issue, going to try his suggestion.
Click to expand...
Click to collapse
Yes, the new 7.1.2 doesn't have cache file. I just got the one from the 7.1.1 build and used that.
The1nonly1 said:
Yes, the new 7.1.2 doesn't have cache file. I just got the one from the 7.1.1 build and used that.
Click to expand...
Click to collapse
That worked
Guess its time to try this again
Related
I was running 3.2.8 as of this morning but decided to go back to stock, so I:
flashed stocked recovery
installed 3.2.8
setup my phone, etc
connected to my vpn
downloaded and installed the update
phone boots to 6.0.1/OOS 3.2.8
I don't get it. Originally I had an issue with the update, it wouldn't install. SO I rebooted to (stock) recovery and wiped cache, rebooted and was able to perform the update. But when the phone rebooted it booted to OOS 3.2.8. WTF?!
Update - it does NOT say update successful, okay so that's a little better. But why the OTA is failing is unknown.
dcdevito said:
Update - it does NOT say update successful, okay so that's a little better. But why the OTA is failing is unknown.
Click to expand...
Click to collapse
Why don't you try installing the update manually?
Formhault said:
Why don't you try installing the update manually?
Click to expand...
Click to collapse
I tried side loading but I get "can't read [filename].Zip"
dcdevito said:
I tried side loading but I get "can't read [filename].Zip"
Click to expand...
Click to collapse
Download the file again. It could be a bad download.
Also, make sure you're using the stock Nougat recovery.
Formhault said:
Download the file again. It could be a bad download.
Also, make sure you're using the stock Nougat recovery.
Click to expand...
Click to collapse
I reinstalled adb drivers and I can at least get the stock recovery to attempt to sideload it, but the install fails like it does from the system updater.
Could be the stock Nougat recovery that I am not using - perhaps I am using an older version - where can I verify the download for that?
For reference this is where I got the stock recovery - https://s3.amazonaws.com/oxygenos.oneplus.net/recovery.img
(Update)
Got it to work - I get a dm-verity error on bootup, did a factory reset after the update but still get the error - but I got it. Thanks for your help, cheers
dcdevito said:
(Update)
Got it to work - I get a dm-verity error on bootup, did a factory reset after the update but still get the error - but I got it. Thanks for your help, cheers
Click to expand...
Click to collapse
How did you get it to work? Just curious.
About the dm-verity error... See this : https://forum.xda-developers.com/oneplus-3t/how-to/how-to-fix-dm-verity-issue-7-0-flashed-t3529680
Edit : whoops, it's for the 3T. Oh well...
Formhault said:
How did you get it to work? Just curious.
About the dm-verity error... See this : https://forum.xda-developers.com/oneplus-3t/how-to/how-to-fix-dm-verity-issue-7-0-flashed-t3529680
Edit : whoops, it's for the 3T. Oh well...
Click to expand...
Click to collapse
I re-downloaded the zip, I just wish I knew if the one I have was the latest version, and thus correct one.
Also, yeah I wish there was a OnePlus 3 Toolkit, not that I mind doing it all manually, I just don't have much time on weekdays to do this.....
dcdevito said:
I re-downloaded the zip, I just wish I knew if the one I have was the latest version, and thus correct one.
Click to expand...
Click to collapse
I see
dcdevito said:
Also, yeah I wish there was a OnePlus 3 Toolkit, not that I mind doing it all manually, I just don't have much time on weekdays to do this.....
Click to expand...
Click to collapse
Well, you missed this
Formhault said:
How did you get it to work? Just curious.
About the dm-verity error... See this : https://forum.xda-developers.com/oneplus-3t/how-to/how-to-fix-dm-verity-issue-7-0-flashed-t3529680
Edit : whoops, it's for the 3T. Oh well...
Click to expand...
Click to collapse
Formhault said:
I see
Well, you missed this
Click to expand...
Click to collapse
Cool, thanks - but I'm assuming this wasn't updated for Nougat, right?
dcdevito said:
Cool, thanks - but I'm assuming this wasn't updated for Nougat, right?
Click to expand...
Click to collapse
I stand correctd - looks like it TWRP and SU were indeed updated
I was using magisk so before update i uninstalled the magisk and checked for update it started immediately since then its stuck on downloading i did force stop for play services and google framework and checked again but nothing worked. However i did factory reset and then checked again this time also it stuck on downloading update. Does anyone know what is the issue ?
goti(0) said:
I was using magisk so before update i uninstalled the magisk and checked for update it started immediately since then its stuck on downloading i did force stop for play services and google framework and checked again but nothing worked. However i did factory reset and then checked again this time also it stuck on downloading update. Does anyone know what is the issue ?
Click to expand...
Click to collapse
There's really no reason to uninstall magisk before an update. Just let it update itself through the app. You should be able to just flash the magisk 16.0 zip in twrp to get things back to normal.
When you say update, you mean OTA or fastbooting the factory image?
Badger50 said:
There's really no reason to uninstall magisk before an update. Just let it update itself through the app. You should be able to just flash the magisk 16.0 zip in twrp to get things back to normal.
When you say update, you mean OTA or fastbooting the factory image?
Click to expand...
Click to collapse
OTA only
goti(0) said:
OTA only
Click to expand...
Click to collapse
Ah..gotchya. Yep, those can cause problems for sure with magisk. Did you try side loading the OTA zip, or consider learning fastboot?
goti(0) said:
OTA only
Click to expand...
Click to collapse
You probably got my issue lol did you flash a custom rom before flashing back stock or any mod that would give you the internal provider error pop up after every boot?
goti(0) said:
I was using magisk so before update i uninstalled the magisk and checked for update it started immediately since then its stuck on downloading i did force stop for play services and google framework and checked again but nothing worked. However i did factory reset and then checked again this time also it stuck on downloading update. Does anyone know what is the issue ?
Click to expand...
Click to collapse
No magisk installed here. Had the same issue of getting stuck at downloading. Factory reset and it worked. Need enough battery charge for it to work. Download was slow on a fast internet btw.
Hope it works fine for you soon
Sent from my Pixel 2 XL using Tapatalk
Badger50 said:
Ah..gotchya. Yep, those can cause problems for sure with magisk. Did you try side loading the OTA zip, or consider learning fastboot?
Click to expand...
Click to collapse
finally i did flash latest image using deuces script as factory reset did not solve the problem but i was wondering what may be the reason as i have never heard of this kind of issue so i posted if anyone else has the same problem.
Jiggs82 said:
You probably got my issue lol did you flash a custom rom before flashing back stock or any mod that would give you the internal provider error pop up after every boot?
Click to expand...
Click to collapse
no i am on stock+magisk since day 1 no rom at all.
X-jo said:
No magisk installed here. Had the same issue of getting stuck at downloading. Factory reset and it worked. Need enough battery charge for it to work. Download was slow on a fast internet btw.
Hope it works fine for you soon
ya i did that but i used deuces script so i can not tell that it will check the update correctly for next month security bulletin.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Hi all,
I've updated my 3xl to the december update like usual, flash-all.bat without -w. Afterwards, it boots fine, and in settings it clearly states that I'm running the December security patch.
However, when I boot into twrp (not installed) and flash magisk, android boots to just before asking my SIM PIN, says "Shutting Down", then reboots and gives me the message "Can't load Android System. Your data may be corrupt." etc. inside stock recovery.
Did the December update somehow break magisk? Anyone gotten it to work? I'd rather not do a factory reset if it's not needed.
Works fine for me.
Try re-flashing the December update with the - w deleted see if it boots up. Then try flashing magdisk manually on bkth a and b partitions
Working fine for me as well.
I would try flashing the stock boot and system images to both slots. It probably won't work but worth a try before doing a factory reset.
Sent from my [device_name] using XDA-Developers Legacy app
You have a corrupt backup copy of boot.img, Magisk grabbed that and used it for root.
Flash the stock boot.img to both slots and reroot.
mikepopo99 said:
Try re-flashing the December update with the - w deleted see if it boots up. Then try flashing magdisk manually on bkth a and b partitions
Click to expand...
Click to collapse
jd1639 said:
I would try flashing the stock boot and system images to both slots. It probably won't work but worth a try before doing a factory reset.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
TonikJDK said:
You have a corrupt backup copy of boot.img, Magisk grabbed that and used it for root.
Flash the stock boot.img to both slots and reroot.
Click to expand...
Click to collapse
First off, thanks for trying to help!
Flashing the stock boot.img "solves" the problem, I can boot and use the phone like normal, but without root obviously. Using the stock boot.img inside magisk manager to patch it with 17.3 and flashing that boot image to both partitions gives me this error again. I've also tried re-applying the December update at least 3 more times, with the same result. Any other ideas?
RogerXIII said:
First off, thanks for trying to help!
Flashing the stock boot.img "solves" the problem, I can boot and use the phone like normal, but without root obviously. Using the stock boot.img inside magisk manager to patch it with 17.3 and flashing that boot image to both partitions gives me this error again. I've also tried re-applying the December update at least 3 more times, with the same result. Any other ideas?
Click to expand...
Click to collapse
Flash the stock boot.img to both slots.
Reboot and check it.
Copy the Magisk zip to your phone.
Fastboot boot the TWRP img file, don't install it.
Use TWRP to install the Magisk zip, and you are done.
RogerXIII said:
First off, thanks for trying to help!
Flashing the stock boot.img "solves" the problem, I can boot and use the phone like normal, but without root obviously. Using the stock boot.img inside magisk manager to patch it with 17.3 and flashing that boot image to both partitions gives me this error again. I've also tried re-applying the December update at least 3 more times, with the same result. Any other ideas?
Click to expand...
Click to collapse
Do you have the previous version of Edge Sense Plus module installed? That sounds exactly like what happens if you install Magisk with that module still there. He put out a new one today.
sliding_billy said:
Do you have the previous version of Edge Sense Plus module installed? That sounds exactly like what happens if you install Magisk with that module still there. He put out a new one today.
Click to expand...
Click to collapse
Thank you so much, this worked!
Instead of going back an Android version, I used this script, uninstalled all modules and re-flashed Magisk. It works perfectly now. Thanks again!
RogerXIII said:
Thank you so much, this worked!
Instead of going back an Android version, I used this script, uninstalled all modules and re-flashed Magisk. It works perfectly now. Thanks again!
Click to expand...
Click to collapse
Good deal. That is why I always keep a copy of the Magisk uninstaller on the phone itself. As long as I can get to BL/temp TWRP .img, the worst I am out is the time it takes me to reconfigure Magisk.
RogerXIII said:
However, when I boot into twrp (not installed)
Click to expand...
Click to collapse
What do you use to get TWRP going when it's not permenantly installed? Just curious?
Fire Hound 8.1
Shaftamle said:
What do you use to get TWRP going when it's not permenantly installed? Just curious?
Fire Hound 8.1
Click to expand...
Click to collapse
The TWRP image from the official website, and then simply fastboot boot twrp.img
RogerXIII said:
The TWRP image from the official website, and then simply fastboot boot twrp.img
Click to expand...
Click to collapse
Ok cool. Wasn't sure if there was an app like fashify or something.
Fire Hound 8.1
sliding_billy said:
Do you have the previous version of Edge Sense Plus module installed? That sounds exactly like what happens if you install Magisk with that module still there. He put out a new one today.
Click to expand...
Click to collapse
you are godsend my friend.
Touz604 said:
you are godsend my friend.
Click to expand...
Click to collapse
Glad you got it figured out.
RogerXIII said:
The TWRP image from the official website, and then simply fastboot boot twrp.img
Click to expand...
Click to collapse
How can we boot the twrp from fastboot?
The one from official website doesn't support Android 10 I believe and I failed with the info says "too many links".
bbs3223474 said:
How can we boot the twrp from fastboot?
The one from official website doesn't support Android 10 I believe and I failed with the info says "too many links".
Click to expand...
Click to collapse
You ca't yet.
bbs3223474 said:
How can we boot the twrp from fastboot?
The one from official website doesn't support Android 10 I believe and I failed with the info says "too many links".
Click to expand...
Click to collapse
Thread is from 2018
I am gonna check the official TWRP website for the workable TWRP for my Pixel 3 till I see your post
wangdaning said:
Thread is from 2018
Click to expand...
Click to collapse
Just checked for updates and this popped up. Enjoy.
Link for the download is: http://bigota.d.miui.com/V10.2.1.0.PEEMIXM/miui_MIMIX3Global_V10.2.1.0.PEEMIXM_9dc43870b4_9.0.zip
I just got this too! Do you know how I can update having twrp installed?
I just tried to install the smaller update above, it failed and now I'm downloading a 1.8gb version. Of you have TWRP installed, I'd probably just download the older OTA and fastboot flash boot boot.img from that OTA.
faddys123 said:
I just got this too! Do you know how I can update having twrp installed?
Click to expand...
Click to collapse
You should be able to install it like normal but ensure when your device reboots you enter your password to enter twrp. If that doesn't work just reboot into twrp and install it by selecting it from the downloaded ROM directory (I forget what the folder is called but it's not the normal download folder). You will have to reflash twrp afterwards.
xreactx said:
You should be able to install it like normal but ensure when your device reboots you enter your password to enter twrp. If that doesn't work just reboot into twrp and install it by selecting it from the downloaded ROM directory (I forget what the folder is called but it's not the normal download folder). You will have to reflash twrp afterwards.
Click to expand...
Click to collapse
This *should* would too.
Filename for the big file is: miui_MIMIX3Global_V10.2.1.0.PEEMIXM_9dc43870b4_9.0.zip we should be able to assemble the whole bigota.somethingsomethingsomething.darkside.xiaomi.downloads url using that, but I'm not at a computer and going to be late for work as is.
Sent from my Mi MIX 3 using Tapatalk
Ok got it installed i downloaded the 1.8gb flashed it via twrp then flashed twrp again and installed magisk all it working now ?
Noticed a few new things battery percentage text is now inside the battery icon!
Also there's a new 'suggestions' in the recents view, it can be turned off in the settings
faddys123 said:
Ok got it installed i downloaded the 1.8gb flashed it via twrp then flashed twrp again and installed magisk all it working now
Noticed a few new things battery percentage text is now inside the battery icon!
Also there's a new 'suggestions' in the recents view, it can be turned off in the settings
Click to expand...
Click to collapse
What version of Magisk did you install? I tried 17.3 and have a bootlooping phone.
The URL for the big OTA (1.8gb) is: http://bigota.d.miui.com/V10.2.1.0.PEEMIXM/miui_MIMIX3Global_V10.2.1.0.PEEMIXM_9dc43870b4_9.0.zip
PWn3R said:
What version of Magisk did you install? I tried 17.3 and have a bootlooping phone.
Click to expand...
Click to collapse
Using 17.3 as well mate
faddys123 said:
Using 17.3 as well mate
Click to expand...
Click to collapse
I just tried downloading a fresh copy of the Magisk zip. Same result. The phone starts booting then reboots into recovery. I don't know why this doesn't work. Did you have a "global" version of the phone? If so, can you backup your boot image with TWRP (the Magisk rooted one) and post it so we can try downloading and installing to see if it works on a Chinese phone?
Is it normal for the update size to not be displayed? This is my first update using a Xiaomi device & found it odd to not know how large a update was.
eseanq said:
Is it normal for the update size to not be displayed? This is my first update using a Xiaomi device & found it odd to not know how large a update was.
Click to expand...
Click to collapse
Mine showed the size for the small incremental which failed and for the full OTA which installed sucessfully. I have not been able to root this with Magisk, no matter what I tried. Every attempt at rooting with SuperSU or Magisk caused the device to bootloop and go back to recovery.
PWn3R said:
Mine showed the size for the small incremental which failed and for the full OTA which installed sucessfully. I have not been able to root this with Magisk, no matter what I tried. Every attempt at rooting with SuperSU or Magisk caused the device to bootloop and go back to recovery.
Click to expand...
Click to collapse
Where does the file size show up?
eseanq said:
Where does the file size show up?
Click to expand...
Click to collapse
It showed it in the text right below the MIUI logo on the updates page. Check the screenshot in the OP
PWn3R said:
It showed it in the text right below the MIUI logo on the updates page. Check the screenshot in the OP
Click to expand...
Click to collapse
Oh ****.. I'm guessing its the 599M? For some reason I thought that was part of the build. :laugh: Lmao.
eseanq said:
Oh ****.. I'm guessing its the 599M? For some reason I thought that was part of the build. :laugh: Lmao.
Click to expand...
Click to collapse
Yeah, that's the update download size. Don't be surprised when the 599 one fails to install (if you have stock recovery). It will download a 1.8GB one (the one I linked to in the OP now) and that one will install as expected. I think you can install either with TWRP if you want. GLHF
anyone figured how to root this? I flashed twrp then flash magisk 17.3 but it kept bootlooping to twrp.
No, I've tried everything. I have a suspicion we can root this on the Chinese device after we have fastboot images.
Sent from my Mi MIX 3 using Tapatalk
Great Update! Many things changed that are not mentioned in the changelog! Finaly notifications in the AOD! ?*?*
PWn3R said:
No, I've tried everything. I have a suspicion we can root this on the Chinese device after we have fastboot images.
Sent from my Mi MIX 3 using Tapatalk
Click to expand...
Click to collapse
I think this too.
Phone is rooted with magisk, running Feb '20 build.
Last month (early Feb) for a split second, I saw the message 'preparing system update' when going to settings - system - system update. Then it went to 'system up to date' (back then it was obviously running Jan '20 update). So I had to download the factory image, patch the boot image and flash it in fastboot to be updated and rooted.
Saw the March update was available, went to system update again, no and behold. Same story. Split second 'preparing system update' and then nothing.
Oddly enough device updated to the januari update through magisk ota procedure just fine.
Has anyone else encountered this? How did you fix it?
Sent from my Pixel 3 XL using Tapatalk
I encountered this last month. Did the Magisk OTA update like you for January and wanted to do the Feb OTA update but it never became available on my phone. Just checked System Update and it says system is up to date. Haven't seen the "preparing system update" for March - yet.
Same here. Magisk OTA method in January then the preparing message then up to date last month and this month.
Seems Google is on to us.
When I get home I am going to unroot via Magisk, not reboot and check again.
TonikJDK said:
Same here. Magisk OTA method in January then the preparing message then up to date last month and this month.
Seems Google is on to us.
When I get home I am going to unroot via Magisk, not reboot and check again.
Click to expand...
Click to collapse
Exact same thing on my wife's phone; it just says system is up to date with January update. There has to be something going on because there are a number of users who have experienced this issue.
jlokos said:
Exact same thing on my wife's phone; it just says system is up to date with January update. There has to be something going on because there are a number of users who have experienced this issue.
Click to expand...
Click to collapse
Use This guide: Do #4 'keep data' then #9 to root.
It only takes 5 minutes.
Note: Before you start disable all your Magisk modules.
So long story short: download factory image and remove -w (wipe flag), flash everything, patch boot image with magisk, and flash image via fastboot. Now what I don't see (or I overlook it), do you flash the patched image via
Flash boot patched_boot.img or to both boot_a and boot_b?
Sent from my Pixel 3 XL using Tapatalk
Ch3vr0n said:
So long story short: download factory image and remove -w (wipe flag), flash everything, patch boot image with magisk, and flash image via fastboot. Now what I don't see (or I overlook it), do you flash the patched image via
Flash boot patched_boot.img or to both boot_a and boot_b?
Click to expand...
Click to collapse
#9. A. 11.
fastboot flash boot --slot all magisk_patched.img
Homeboy76 said:
#9. A. 11.
fastboot flash boot --slot all magisk_patched.img
Click to expand...
Click to collapse
Are you advising to just use the factory image to update or are you saying the OTA updates will work after reflashng factory image?
willyumlu said:
Are you advising to just use the factory image to update or are you saying the OTA updates will work after reflashng factory image?
Click to expand...
Click to collapse
@willyumlu
Flash the Factory Image, the OTA update is what you are having problems getting installed.
Also, if you are rooted take a look at #9. B. OTA Installation
Homeboy76 said:
@willyumlu
Flash the Factory Image, the OTA update is what you are having problems getting installed.
Also, if you are rooted take a look at #9. B. OTA Installation
Click to expand...
Click to collapse
Yeah it's not showing any OTA updates since ~January. I think there's some corrupt folder/file permissions after one of the OTAs or something - I can't use a log viewer app to check the logs. Tried to just flash stock Feb thru fastboot like you suggested and afterwards, even with the stock boot, I couldn't find any updates. I'll try to do a factory reset when I have time to see if that solves the issue
EDIT: Got it working after I used https://pixelrepair.withgoogle.com/ to reflash. When I tried factory resetting by follow @Homeboy76 's guide (w/o using the laptop), it still wouldn't find an OTA. The site got me back onto Feb stock and I rerooted and applied the OTA afterwards
willyumlu said:
Yeah it's not showing any OTA updates since ~January. I think there's some corrupt folder/file permissions after one of the OTAs or something - I can't use a log viewer app to check the logs. Tried to just flash stock Feb thru fastboot like you suggested and afterwards, even with the stock boot, I couldn't find any updates. I'll try to do a factory reset when I have time to see if that solves the issue
EDIT: Got it working after I used https://pixelrepair.withgoogle.com/ to reflash. When I tried factory resetting by follow @Homeboy76 's guide (w/o using the laptop), it still wouldn't find an OTA. The site got me back onto Feb stock and I rerooted and applied the OTA afterwards
Click to expand...
Click to collapse
Glad you got the OTA
I'm curious what # was, "factory resetting by follow @Homeboy76 's guide (w/o using the laptop), it still wouldn't find an OTA."
factory image method didn't work (flashing feb build and patching boot image). pixel repair isn't available in belgium. Still no OTA
Homeboy76 said:
Glad you got the OTA
I'm curious what # was, "factory resetting by follow @Homeboy76 's guide (w/o using the laptop), it still wouldn't find an OTA."
Click to expand...
Click to collapse
#3b
Ch3vr0n said:
factory image method didn't work (flashing feb build and patching boot image). pixel repair isn't available in belgium. Still no OTA
Click to expand...
Click to collapse
Maybe a factory image with -w would work? I'm not sure what exactly the pixelrepair site does but it seemed like it was doing a sideload after wiping data since it asks you to go into recovery mode
Don't care what the pixelrepair does, as I said. I can't use it. Probably Geo restriction.
Sent from my Pixel 3 XL using Tapatalk
willyumlu said:
#3b
Click to expand...
Click to collapse
I was pointing out the benefits of flashing the factory image #4 'keep data' an re- rooting #9. So, I was surprised to see factory reset in your response. :good:
Ch3vr0n said:
Don't care what the pixelrepair does, as I said. I can't use it. Probably Geo restriction.
Sent from my Pixel 3 XL using Tapatalk
Click to expand...
Click to collapse
Yeah I'm suggesting flashing the factory image without removing "-w" to do what the site did since you can't access it
Yeah I ain't doing that in the middle of a week after work. I can't go without phone during the week if something goes wrong, or spend hours after restoring the auto-backup and setting up mail etc all over again. Maybe over the weekend.
Sent from my Pixel 3 XL using Tapatalk
I had to Flash the factory Image too. No Ota arrived since the Dec 2019 update.
I remived the -w Option and everything is fine. No data loss.
Patching the boot.img with magisk didn't work. Magisk 7.5.1 always crashed. I tried Magisk 7.5.0 and everything worked.