I just got a "really blue" pixel XL today and I seem to have the problem that so many people are facing, I can not unlock my bootloader
The guy I bought it from said it was the google version, but not 100% sure if it is or not, and not sure how to distinguish if it is or not.
Anyway, to my question, the main reason I bought the phone was to try out Android P, but it seems I can not install it, since my bootloader is lock, correct? and I would assume there is no workaround for this, either?
Thanks!
I could be mistaken, but I think if it's stock software you should be able to flash the file provided by Google.... On a locked bootloader.
If it is Verizon version you can still get Android P on it by side loading the OTA. You just need adb/fastboot on your computer. Very simple process. I am running Android P on my Verizon pixel with locked bootloader now.
tember1214 said:
If it is Verizon version you can still get Android P on it by side loading the OTA. You just need adb/fastboot on your computer. Very simple process. I am running Android P on my Verizon pixel with locked bootloader now.
Click to expand...
Click to collapse
how are you installing it without any issues?
I am running the basic commands
adb reboot recovery
adb sideload <filename.zip>
and it keeps erroring out on me., it says
E: Signature verification failed
E: error: 21
Am I missing something?
cms062407 said:
how are you installing it without any issues?
I am running the basic commands
adb reboot recovery
adb sideload <filename.zip>
and it keeps erroring out on me., it says
E: Signature verification failed
E: error: 21
Am I missing something?
Click to expand...
Click to collapse
Are you following these steps? I had no issue. Had the same error you had the first time because of bad download
tember1214 said:
Are you following these steps? I had no issue. Had the same error you had the first time because of bad download
Click to expand...
Click to collapse
Yep, I am doing those exact instructions.
I have even re-downloaded the OTA file a few times.
Did you do anything with the actual 1.3GB file or just flash it as it is? Did you rename it, by chance?
It may be some sort of device driver issue, but I also think it may not be, since my device is being recognized just fine within adb commands..
Dup post.
cms062407 said:
Yep, I am doing those exact instructions.
I have even re-downloaded the OTA file a few times.
Did you do anything with the actual 1.3GB file or just flash it as it is? Did you rename it, by chance?
It may be some sort of device driver issue, but I also think it may not be, since my device is being recognized just fine within adb commands..
Click to expand...
Click to collapse
I renamed it to ota.zip but the shouldn't matter
---------- Post added at 10:42 PM ---------- Previous post was at 10:36 PM ----------
cms062407 said:
Yep, I am doing those exact instructions.
I have even re-downloaded the OTA file a few times.
Did you do anything with the actual 1.3GB file or just flash it as it is? Did you rename it, by chance?
It may be some sort of device driver issue, but I also think it may not be, since my device is being recognized just fine within adb commands..
Click to expand...
Click to collapse
Your sure your downloading the ota file and not the factory image ?
tember1214 said:
I renamed it to ota.zip but the shouldn't matter
---------- Post added at 10:42 PM ---------- Previous post was at 10:36 PM ----------
Your sure your downloading the ota file and not the factory image ?
Click to expand...
Click to collapse
ohhhhh, that is more than likely it! I didn't see "OTA " files before..but i just googled it, and I see they are different file names...downloaded the OTA now, and about to try to install.
before, I just googled "android p pixel xl" and it brought me to this page... https://developer.android.com/preview/download.html
but the OTA downloads are on a totally different page at https://developer.android.com/preview/download-ota.html
tember1214 said:
I renamed it to ota.zip but the shouldn't matter
---------- Post added at 10:42 PM ---------- Previous post was at 10:36 PM ----------
Your sure your downloading the ota file and not the factory image ?
Click to expand...
Click to collapse
well, hell...looky there....it is now installing just fine! can't wait to see what P is about, now!
Thanks for the help with making sure I was downloading the OTA file....What are those factory images for then, if you can't install them with ADB commands?
cms062407 said:
well, hell...looky there....it is now installing just fine! can't wait to see what P is about, now!
Thanks for the help with making sure I was downloading the OTA file....What are those factory images for then, if you can't install them with ADB commands?
Click to expand...
Click to collapse
You can't with a locked bootloader haha. Glad you finally got it working
---------- Post added at 11:39 PM ---------- Previous post was at 11:31 PM ----------
Enjoy!!
Do you know if you can side load back to an older version or can you only go forward since they are OTA "updates".
Tried side loading old version and no go.
mswlogo said:
Do you know if you can side load back to an older version or can you only go forward since they are OTA "updates".
Click to expand...
Click to collapse
Don't think so on a locked bootloader. Are there any issues in particular with P?
Sent from my Pixel using Tapatalk
cms062407 said:
Thanks for the help with making sure I was downloading the OTA file....What are those factory images for then, if you can't install them with ADB commands?
Click to expand...
Click to collapse
Factory images are installed differently. I don't know if they'll install on a VZW device, I'd think they should because they're "official."
mike.s said:
Factory images are installed differently. I don't know if they'll install on a VZW device, I'd think they should because they're "official."
Click to expand...
Click to collapse
They will not install on Verizon device without unlocked bootloader.
---------- Post added at 04:38 PM ---------- Previous post was at 04:36 PM ----------
Jazznax said:
Don't think so on a locked bootloader. Are there any issues in particular with P?
Click to expand...
Click to collapse
Been using Android P since it came out. It's my daily driver. Works great. Only thing is now my Samsung gear watch won't work because the app isn't updated for new version of Android.
Pedroking78 said:
I've tried sideloading Android P but it keeps saying build date to old can not down grade??
Click to expand...
Click to collapse
If you're already on April security update you'll have to wait for the next preview build since preview 1 has an older timestamp than April patch.
Sent from my taimen using XDA Labs
joedeuce said:
If you're already on April security update you'll have to wait for the next preview build since preview 1 has an older timestamp than April patch.
Sent from my taimen using XDA Labs
Click to expand...
Click to collapse
Oh that's annoying. Any idea when that might be/how often they typically release updated builds?
Pedroking78 said:
just unlock your bootloader
and you can flash it thats want it did :laugh::laugh:
Click to expand...
Click to collapse
How do you unlock it then?
That's cool and all but personally I'd rather just wait for a new build of P.
Related
Got an update notification last night for 3.14.531.17 (19.72 MB). I'm running Unknown's ROM 1.7.1 so I thought this was a bit strange. Has anyone else received this update?
Anyways, here's a link to the update file for anyone that's interested and intrepid enough to try it. https://www.dropbox.com/s/ajueet3ta...e_320853foljnqxv82dc62l1.zip.20263.enc?v=0mcn MD5: af450b9f70e14fd01798031e7c52228e
So far I have not run it. I am on CID: T-MOB010, S-OFF for anyone that's curious.
Your file is corrupted.
hasoon2000 said:
Your file is corrupted.
Click to expand...
Click to collapse
no its encrypted that is what the .enc at the end is.
mkinney88 said:
no its encrypted that is what the .enc at the end is.
Click to expand...
Click to collapse
Oh yeah. Forgot about that encryption crap that HTC has.
hasoon2000 said:
Oh yeah. Forgot about that encryption crap that HTC has.
Click to expand...
Click to collapse
can you remove the .enc from the ota.zip.enc cause i know there is a program to remove the encryption from RUU ROM01.zip but i don't know if it works on the OTA zips cause the RUU ROM01.ZIP that is encrypted doesn't have the .enc at the end.
mkinney88 said:
can you remove the .enc from the ota.zip.enc cause i know there is a program to remove the encryption from RUU ROM01.zip but i don't know if it works on the OTA zips cause the RUU ROM01.ZIP that is encrypted doesn't have the .enc at the end.
Click to expand...
Click to collapse
Just tried it right now actually and it says "Invalid HTC AES encrypted zip file". I'm not very familiar with Ubuntu but I have decrypted a few RUUs before, just not OTAs.
hasoon2000 said:
Your file is corrupted.
Click to expand...
Click to collapse
I just deleted the file, ran the update check and downloaded again, and I'm getting the same file - MD5 matches. So if it's corrupted, then it's likely the source file that's corrupted.
mongoosesRawesome said:
I just deleted the file, ran the update check and downloaded again, and I'm getting the same file - MD5 matches. So if it's corrupted, then it's likely the source file that's corrupted.
Click to expand...
Click to collapse
its not corrupted its just encrypted, ill keep trying to check for an update but i don't get anything. I even ran the RUU and still no dice??
---------- Post added at 03:36 PM ---------- Previous post was at 03:34 PM ----------
mongoosesRawesome said:
I just deleted the file, ran the update check and downloaded again, and I'm getting the same file - MD5 matches. So if it's corrupted, then it's likely the source file that's corrupted.
Click to expand...
Click to collapse
i wonder if you try to run the update and when it reboot it will unencrypt it and before it errors out you and adb pull from a temp folder or something
---------- Post added at 03:46 PM ---------- Previous post was at 03:36 PM ----------
hasoon2000 said:
Just tried it right now actually and it says "Invalid HTC AES encrypted zip file". I'm not very familiar with Ubuntu but I have decrypted a few RUUs before, just not OTAs.
Click to expand...
Click to collapse
did you try and remove the .20263.enc off the end and try decrypting it
mkinney88 said:
its not corrupted its just encrypted, ill keep trying to check for an update but i don't get anything. I even ran the RUU and still no dice??
did you try and remove the .20263.enc off the end and try decrypting it
Click to expand...
Click to collapse
Yup. I'm thinking of ways to decrypt it
hasoon2000 said:
Yup. I'm thinking of ways to decrypt it
Click to expand...
Click to collapse
any new ideas?
mkinney88 said:
any new ideas?
Click to expand...
Click to collapse
I renamed it as update.zip and attempted to flash it. It failed. My One S is completely stock since I'm going to sell it. So it may be a bad download or something. Not too sure.
hasoon2000 said:
I renamed it as update.zip and attempted to flash it. It failed. My One S is completely stock since I'm going to sell it. So it may be a bad download or something. Not too sure.
Click to expand...
Click to collapse
It's definitely weird, I'll give you that. Especially since I haven't seen anyone else receive this update OTA. I just deleted, rechecked for updates, and it downloaded again, and I checked the MD5 with the previous file, and it matched, again, so we can rule out a bad download. Perhaps a bad source file.
MD5: af450b9f70e14fd01798031e7c52228e
What does the new update do?
Sent from my HTC VLE_U using xda app-developers app
Lionhardt said:
What does the new update do?
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
Since no one's been able to apply the update and it's not listed on the t-mobile website, who knows.
My phone is stock, but I haven't received this update. I'm guessing this is supposed to fix the battery drain from GPS always being on when wifi calling is enabled.
HTC has updated their ROM Update page with a 3.14.531.17 RUU.
HTC One S for T-Mobile ROM Update | 6.24.2013
RUU_Ville_U_JB_45_S_TMOUS_3.14.531.17_Radio_1.13.50.05.31_10.30.50.08L_release_320836_ICS_2_JB.exe
Anyone who's familiar with ruuveal want to take a crack at it?
I too am running unknown 1.7.1 and am getting an ota update that is 19mb. I as wondering if should run it.
---------- Post added at 08:00 PM ---------- Previous post was at 07:44 PM ----------
darrin976 said:
I too am running unknown 1.7.1 and am getting an ota update that is 19mb. I as wondering if should run it.
Click to expand...
Click to collapse
My file is named OTA_Ville_U_JB_45_S_TMOUS_3.14.531.17-3.14.531.11_release_320853foljnqxv82dc62l1.zip
You guys should upgrade to 1.8.1 here: http://forum.xda-developers.com/showthread.php?t=2250573
It contains the fixes for battery usage and wifi calling. If anything, I think it might be better than ICS. Now if I could only get Google Navigation to work properly in 3D mode (using Waze instead for now).
mongoosesRawesome said:
You guys should upgrade to 1.8.1 here: http://forum.xda-developers.com/showthread.php?t=2250573
It contains the fixes for battery usage and wifi calling. If anything, I think it might be better than ICS. Now if I could only get Google Navigation to work properly in 3D mode (using Waze instead for now).
Click to expand...
Click to collapse
I tried to yesterday unsuccessfully, I am going to try again soon.
Anyone know what will happen if I do this ota update?
The update you are referring to is going to be from T-mobile, so it will not work. What problems did you run into with the 1.8.1 update?
For those of you using official builds. Check for update.
Haha sorry I should know this by now
I should flash stock recovery first right
Is it possible to sideload the update while keeping root and xposed?
Anyone got that OTA link? I'm sideloading updates because Sprint.
billteeth said:
Anyone got that OTA link? I'm sideloading updates because Sprint.
Click to expand...
Click to collapse
Same here. Hopefully soon, haven't heard of anyone actually getting the update yet so it might not be live yet.
Just popped up on my Verizon connected PH-1
Rick
BlackIce
The install freezes on step 2/2, i'm not rooted, and i tried to restart, no installed. What should I do ?
basongwe said:
The install freezes on step 2/2, i'm not rooted, and i tried to restart, no installed. What should I do ?
Click to expand...
Click to collapse
You sure it froze? The update does take kinda long on the second step
wrapper said:
You sure it froze? The update does take kinda long on the second step
Click to expand...
Click to collapse
Agreed
wrapper said:
You sure it froze? The update does take kinda long on the second step
Click to expand...
Click to collapse
About 1 hour ?
Think it froze, and i rebooted
---------- Post added at 09:57 PM ---------- Previous post was at 09:55 PM ----------
still on 2/2
Finally worked, thanks
basongwe said:
About 1 hour ?
Think it froze, and i rebooted
---------- Post added at 09:57 PM ---------- Previous post was at 09:55 PM ----------
still on 2/2
Finally worked, thanks
Click to expand...
Click to collapse
A little bit of patience usually do the trick.
Skickat från min PH-1 via Tapatalk
Anyone notice haptic vibration is a little bit lighter after the update?
billteeth said:
Anyone got that OTA link? I'm sideloading updates because Sprint.
Click to expand...
Click to collapse
https://android.googleapis.com/pack.../b1f428ce77a3324759d0157f964b507ebc5e72fb.zip
Tardeaux said:
https://android.googleapis.com/pack.../b1f428ce77a3324759d0157f964b507ebc5e72fb.zip
Click to expand...
Click to collapse
Thank you! Sideload worked great for me.
This is 7.1.x?
---------- Post added at 07:18 PM ---------- Previous post was at 07:12 PM ----------
billteeth said:
Thank you! Sideload worked great for me.
Click to expand...
Click to collapse
you just flash this over F using fastboot?
n.m. something like this? Guess I can't use TWRP for this. ===> https://9to5google.com/2017/10/24/how-to-manually-sideload-install-ota-update-file-android-basics/
avd said:
This is 7.1.x?
---------- Post added at 07:18 PM ---------- Previous post was at 07:12 PM ----------
you just flash this over F using fastboot?
n.m. something like this? Guess I can't use TWRP for this. ===> https://9to5google.com/2017/10/24/how-to-manually-sideload-install-ota-update-file-android-basics/
Click to expand...
Click to collapse
Yea, TWRP works. But I've been just sideloading ota's instead of unlocking and rooting for the last few years. It has also been super fast and easy with the essential.
Drivers:
https://www.essential.com/developer/current-builds
Google and install "Minimal ADB and Fastboot."
Download and put the ota zip file in the fastboot folder (I always rename it to the build number, too)
Rest:
https://www.howtogeek.com/255311/how-to-manually-upgrade-your-nexus-device-with-adb-sideload/
billteeth said:
Yea, TWRP works. But I've been just sideloading ota's instead of unlocking and rooting for the last few years. It has also been super fast and easy with the essential.
Drivers:
https://www.essential.com/developer/current-builds
Google and install "Minimal ADB and Fastboot."
Download and put the ota zip file in the fastboot folder (I always rename it to the build number, too)
Rest:
https://www.howtogeek.com/255311/how-to-manually-upgrade-your-nexus-device-with-adb-sideload/
Click to expand...
Click to collapse
thanks
I'm on sprint and rooted to "F".
someone please confirm: to go to "B", first I need to uninstall majisk, the flash the stock recovery, then sideload the OTA, then flash the new TWRP then reinstall magisk?
How do I find the non Sprint/Telus OTA file to side load?
Worked fine for me. Phone is running great now with no hiccups. The past week I started getting freezes that required a reboot.. but all is well now.
Snappy and fast again.
my mic seems to stopped working since this update :/
Notice: before doing it, make sure your phone bootloader is unlocked or it won't work
This will require you to find a matching full ROM. To find your matching channel, go to Settings > About Phone > Software channel
Lookup the first two letters and find the matching ROM there
https://mirrors.lolinet.com/firmware/moto/river/official/
If your phone channel is "US Retail", download RETUS (retail US)
After you have downloaded the full ROM (you should keep the full ROM in case you want to revert to stock unrooted), unzip and get boot.img. Copy the image to your phone and use Magisk to patch the image. After that, copy the output image to your host computer.
Now turn your phone off, press and hold power + volume down to enter bootloader, connect your phone to host computer, and enter
Code:
fastboot flash boot
Press space once and drag and drop the output image file to command window.
If everything goes well, restart the phone and confirm it is rooted with Magisk
Now you have rooted G7
Nice solution. Did not even need TWRP for this either.
Seems to be oversimplified. I'm sure this makes perfect sense to those that go through the root process often or at least recently.
Unfortunately I'm not one of those. Last device I rooted was about 5-6 years ago.
I'll be doing my homework on the new tools and procedures while waiting for a more detailed step-by-step guide.
Thank you for your efforts and at least I know that root is possible.
Please can you guys make the steps easy to understand...some people here are new in this method.... Thanks
Question
What will my mirror be if Software Channel says Amazon?
O7ymand1as said:
What will my mirror be if Software Channel says Amazon?
Click to expand...
Click to collapse
I don't think Amazon version allows you to unlock the bootloader
Alternative method: look at the appendix of model on the box and find a matching one
O7ymand1as said:
What will my mirror be if Software Channel says Amazon?
Click to expand...
Click to collapse
I was able to unlock mine from amazon, it was XT1962-1 and said software variant amz and software channel amazon. For root I did have to flash with stock rom. The steps I took are listed in moto g7 questions thread. Look for amazon in the title.
I just picked up a G7 to play with today.
@mingkee I'm assuming these are similar to the Pixel devices when an OTA is sent we can just reflash the Stock boot.img and then take the OTA and re-root using the same methodology above?
Itachisasuke said:
I just picked up a G7 to play with today.
@mingkee I'm assuming these are similar to the Pixel devices when an OTA is sent we can just reflash the Stock boot.img and then take the OTA and re-root using the same methodology above?
Click to expand...
Click to collapse
Yes, as long as using correct boot.img
I tried with G7 Play - Channel
Did not work. These errors occurred in the prints.
Marcondes BR said:
Did not work. These errors occurred in the prints.
Click to expand...
Click to collapse
You should be good. The bad key error is normal. What happened on reboot?
Marcondes BR said:
Did not work. These errors occurred in the prints.
Click to expand...
Click to collapse
Don't worry about the error.
Install Magisk Manager and required components and that's it.
Keep the original boot in case to get OTA, but you should get updated full ROM and get updated boot and patch and flash again
timecutter said:
You should be good. The bad key error is normal. What happened on reboot?
Click to expand...
Click to collapse
Rebooted normally. When it starts, the screen turns completely black, and bad key is written in the upper left corner. It restarted in the same way.
---------- Post added at 02:06 PM ---------- Previous post was at 01:59 PM ----------
mingkee said:
Don't worry about the error.
Install Magisk Manager and required components and that's it.
Keep the original boot in case to get OTA, but you should get updated full ROM and get updated boot and patch and flash again
Click to expand...
Click to collapse
Can you explain this better? Did not quite understand.
This method works flawlessly. Thanks for the tip.
Marcondes BR said:
Rebooted normally. When it starts, the screen turns completely black, and bad key is written in the upper left corner. It restarted in the same way.
---------- Post added at 02:06 PM ---------- Previous post was at 01:59 PM ----------
Can you explain this better? Did not quite understand.
Click to expand...
Click to collapse
Boot.img should match ROM version or you may have trouble booting.
New OTA has been released for US, but it's recommended to wait for updated full ROM in order to regain root.
mingkee said:
Boot.img should match ROM version or you may have trouble booting.
New OTA has been released for US, but it's recommended to wait for updated full ROM in order to regain root.
Click to expand...
Click to collapse
Did not work.
My bootloader is unlocked.
The boot.img image is correct.
I did it step by step and it did not work.
I do not get root and magisk says that it is not installed.
Marcondes BR said:
Did not work.
My bootloader is unlocked.
The boot.img image is correct.
I did it step by step and it did not work.
I do not get root and magisk says that it is not installed.
Click to expand...
Click to collapse
Did you patch boot.img?
my moto g7 non variant river phone channel said "US Retail", but the required rom info was under River/Official/Retail, not River/Official/Retus. When I tried Retus, it bootlooped until I flashed Retail. FYI for anyone encountering same issue.
mingkee said:
Did you patch boot.img?
Click to expand...
Click to collapse
Yeah. I copied the patch boot to my computer and flashed with adb.
My software channel is "reteu2" and the software version is PPW29.98-28.
Under river/official/RETEU/ I cannot find a suitable software version. Is my version not available there?
versions 19 and 20 are up
https://developers.google.com/android/images
What's the difference between the two?
So I'm on 9 - could anyone tell me if I can still just remove the "-w" switch from flash-all.bat or do I need to do a totally clean install?
SinisterXReaper said:
What's the difference between the two?
Click to expand...
Click to collapse
.020 would be more.
kerobrat said:
So I'm on 9 - could anyone tell me if I can still just remove the "-w" switch from flash-all.bat or do I need to do a totally clean install?
Click to expand...
Click to collapse
You don't have to do a clean install, but I always do. I feel like I have less issues.
rooting works?
What's the current root method for 10.0? I take it there is no TWRP yet?
What is the difference between .019 and .020? The second one listed on the factory image page usually seems to be Verizon. Also, the odd numbered one seems to be Verizon. Yes I've read. Maybe I've overlooked something, but I'm at a loss.
SinisterXReaper said:
What's the difference between the two?
Click to expand...
Click to collapse
The .19 is for users on the Q betas already , the .20 are for users jumping from pie
Jiggs82 said:
The .19 is for users on the Q betas already , the .20 are for users jumping from pie
Click to expand...
Click to collapse
Thanks!
airmaxx23 said:
What's the current root method for 10.0? I take it there is no TWRP yet?
Click to expand...
Click to collapse
For TWRP check here...
https://forum.xda-developers.com/pi...pixel-3-xl-t3861623/post79995400#post79995400
Can I do a OTA with bootloader unlocked .? (No TWRP AND no ROOT)
STALKER18 said:
Can I do a OTA with bootloader unlocked .? (No TWRP AND no ROOT)
Click to expand...
Click to collapse
Yes you will be able to.
Magisk still works. For those lazy ones, here is the patched boot image (19): https://drive.google.com/file/d/1sy4jQjevqQwvGDVGw4d8sHY3bRXCXCjo/view?usp=sharing
---------- Post added at 08:36 PM ---------- Previous post was at 08:36 PM ----------
dnsmo said:
rooting works?
Click to expand...
Click to collapse
Yes, https://drive.google.com/file/d/1sy4jQjevqQwvGDVGw4d8sHY3bRXCXCjo/view?usp=sharing.
So, flashed 10 a bit ago. Just got a new OTA for 1.2MB? Anyone else?
magisk still works just need to do the manually patching method.
Flashed the 10 images and the phone wont go past the G logo. Removed the -W when i did it. Tried again to no avail. I didn't wipe anything before trying. Any suggestions?
Fuzzy13 said:
Flashed the 10 images and the phone wont go past the G logo. Removed the -W when i did it. Tried again to no avail. I didn't wipe anything before trying. Any suggestions?
Click to expand...
Click to collapse
Wipe
shiftr182 said:
Wipe
Click to expand...
Click to collapse
Backing up my internal drive just in case and that's what I'm going to try next. Thanks
Would someone who's on Android 10 release please do a simple check for me?
Go to Settings / Accessibility and check if there is an option for hearing aids / Pair new device
Thanks in advance
March updates are published.
https://developers.google.com/android/images
Nice
Looks like there are a lot of fixes this month.
https://support.google.com/pixelphone/thread/32079343?hl=en
Feature drop too.
https://9to5google.com/2020/03/02/pixel-feature-drop-march/
Anyone having problems with Magisk crashing while trying to patch the boot image? It crashes every time I try. Changed to stable, rebooted, nothing works. Thoughts?
gettinwicked said:
Anyone having problems with Magisk crashing while trying to patch the boot image? It crashes every time I try. Changed to stable, rebooted, nothing works. Thoughts?
Click to expand...
Click to collapse
Yep. I had to switch to stable magisk and it patched the boot fine for me. Odd it didn't work for you.
wolfeyes30 said:
Yep. I had to switch to stable magisk and it patched the boot fine for me. Odd it didn't work for you.
Click to expand...
Click to collapse
I reinstalled Magisk and it worked fine. Weird.
It Is just me or they have increased the maximum brightness ? It's like they have unlocked the High Brightness Mode
Had Problem with magisk but had franco kernel installed. You have to deactivate the modules for that kernel then magisk works again. Hole that helps
gettinwicked said:
Anyone having problems with Magisk crashing while trying to patch the boot image? It crashes every time I try. Changed to stable, rebooted, nothing works. Thoughts?
Click to expand...
Click to collapse
me too
Starting in Feb my phone no longer gets updates.. I'm not sure if it's because of Magisk or not. I search for update and for about 2 seconds it says preparing update and then it says you are up to date.
Anyone else? Any fix?
dave5777 said:
March updates are published.
https://developers.google.com/android/images
Click to expand...
Click to collapse
:good:
---------- Post added at 02:34 AM ---------- Previous post was at 02:31 AM ----------
murphyjasonc said:
Looks like there are a lot of fixes this month.
https://support.google.com/pixelphone/thread/32079343?hl=en
Click to expand...
Click to collapse
:good:
---------- Post added at 02:38 AM ---------- Previous post was at 02:34 AM ----------
troymz1 said:
Starting in Feb my phone no longer gets updates.. I'm not sure if it's because of Magisk or not. I search for update and for about 2 seconds it says preparing update and then it says you are up to date.
Anyone else? Any fix?
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.
Balulo_007 said:
It Is just me or they have increased the maximum brightness ? It's like they have unlocked the High Brightness Mode
Click to expand...
Click to collapse
They unlocked High. Brightness. That was one of the features in this quarters drop.
---------- Post added at 09:42 PM ---------- Previous post was at 09:38 PM ----------
troymz1 said:
Starting in Feb my phone no longer gets updates.. I'm not sure if it's because of Magisk or not. I search for update and for about 2 seconds it says preparing update and then it says you are up to date.
Anyone else? Any fix?
Click to expand...
Click to collapse
Just fastboot the factory image without the -w. It might just be personal preference but I think that's the easiest way to update if you are rooted.
murphyjasonc said:
Just fastboot the factory image without the -w. It might just be personal preference but I think that's the easiest way to update if you are rooted.
Click to expand...
Click to collapse
I'm aware of how to update but I used to be able to take the ota and re root with Magisk.. but now I don't even get the ota.
troymz1 said:
I'm aware of how to update but I used to be able to take the ota and re root with Magisk.. but now I don't even get the ota.
Click to expand...
Click to collapse
I have automatic system updates disabled in developer options. It's probably unlikely since you were getting updates but could you have disabled by accident? Not sure what else would suddenly cause you to stop getting them. I doubt it's something that simple but I've beat my head against the wall for something similar in the past....lol
troymz1 said:
I'm aware of how to update but I used to be able to take the ota and re root with Magisk.. but now I don't even get the ota.
Click to expand...
Click to collapse
I'm right there with you. Very annoyed that it won't do it through normal OTA. I waited it out through February and never got it.
murphyjasonc said:
I have automatic system updates disabled in developer options. It's probably unlikely since you were getting updates but could you have disabled by accident? Not sure what else would suddenly cause you to stop getting them. I doubt it's something that simple but I've beat my head against the wall for something similar in the past....lol
Click to expand...
Click to collapse
Disabling that toggle in developer options is a prerequisite for doing the OTA update option and retaining magisk.
wgrant said:
I'm right there with you. Very annoyed that it won't do it through normal OTA. I waited it out through February and never got it.
Click to expand...
Click to collapse
Have you tried doing the Magisk uninstall then tried taking the ota?
troymz1 said:
Have you tried doing the Magisk uninstall then tried taking the ota?
Click to expand...
Click to collapse
No, that'll be what I do this month if it doesn't pop up like it should.
wgrant said:
No, that'll be what I do this month if it doesn't pop up like it should.
Click to expand...
Click to collapse
I wanna try it but don't have time to fix right now if it goes wrong
I agree with a lot of others here: It's easier to dirty flash, no hassles and it works every time without having to figure out any secret handshakes.