Database Develop

A bit of fun

Anybody had the November update yet. :laugh:

And anyone with unlocked bootloader have Pie october update ?

Keep the jokes coming

Almost got it, but it went too quickly.
For sure, I'll get it next time

I am getting 80 hours of screen on time. It's powered by nuclear reactor and it's a secret project of Juho Sarvikos.

k3dar7 said:
And anyone with unlocked bootloader have Pie october update ?
Click to expand...
Click to collapse
I have installed the Pie october update with a unlocked bootloader.
To get rid of the sideload error I have repacked the Pie september boot.img to change the 0001 into 00WW. I can't post link for the moment but if anyone is interested by the repacked boot.img pm me.

TomThePhysicist said:
I have installed the Pie october update with a unlocked bootloader.
To get rid of the sideload error I have repacked the Pie september boot.img to change the 0001 into 00WW. I can't post link for the moment but if anyone is interested by the repacked boot.img pm me.
Click to expand...
Click to collapse
Thanx for tip! I do repack myself, before i try find 0001 on */*prop* in booted system(and not found), not try find in boot.img(where this really is)

TomThePhysicist said:
I have installed the Pie october update with a unlocked bootloader.
To get rid of the sideload error I have repacked the Pie september boot.img to change the 0001 into 00WW. I can't post link for the moment but if anyone is interested by the repacked boot.img pm me.
Click to expand...
Click to collapse
i have repacked Pie september boot.img, in adb sideload is gone 0001 error, but still not finish, show "Error applying update: 20 (ErrorCode:: kDownloadStateInitializationError)"
first i try change 0001 to 00WW in default.prop and prop.default, second also in adbd and recovery binary...
repack using "Android_boot_image_editor"

k3dar7 said:
i have repacked Pie september boot.img, in adb sideload is gone 0001 error, but still not finish, show "Error applying update: 20 (ErrorCode:: kDownloadStateInitializationError)"
first i try change 0001 to 00WW in default.prop and prop.default, second also in adbd and recovery binary...
repack using "Android_boot_image_editor"
Click to expand...
Click to collapse
You need to have an unrooted system in order to make the update.
I think the error 20 is caused by a difference between the sha256 sum of your system and the expected one from the installer.
I have reinstalled the Pie september update prior to the october one and everything worked fine.

I have already got Android 9.1 with great new features:
1. Nokia camera has become better than Pixel 3, my friend wants my Nokia 7 Plus in exchange for his Pixel the new camera even features X-ray mode where you can see what's behind a wall, it uses Wifi and Radio signals to see what's behind a wall.
2. It works so flawlessly that even Fortnite is supported on this new build
3. Bootloader comes unlocked by default now, it's so open that now you will need to file a petition to close it.

TomThePhysicist said:
You need to have an unrooted system in order to make the update.
I think the error 20 is caused by a difference between the sha256 sum of your system and the expected one from the installer.
I have reinstalled the Pie september update prior to the october one and everything worked fine.
Click to expand...
Click to collapse
i know unrooted, i have complety uninstall magisk from magisk manager...
What you mean "reinstall" ? if i try sideload pie september then show same error, if try after change slot then show timestamp error

k3dar7 said:
i know unrooted, i have complety uninstall magisk from magisk manager...
What you mean "reinstall" ? if i try sideload pie september then show same error, if try after change slot then show timestamp error
Click to expand...
Click to collapse
If you have the september update installed on the active slot you will normally always get a timestamp error when trying to sideload it again.
To get rid of the timestamp error, simply flash an anterior boot image with fastboot (I have used a boot image from the last Pie public beta update).
To sum up:
Flash an anterior boot image (to the september Pie update) with fastboot and reboot to recovery (I always flash both slots).
Sideload the september Pie update and reboot to bootloader.
Flash a repacked September boot image with 0001 changed into 00WW in default.prop and prop.default (pm me if you need a working boot image) and reboot to recovery.
Sideload the october pie update and reboot to system.

TomThePhysicist said:
[...]To get rid of the timestamp error, simply flash an anterior boot image with fastboot (I have used a boot image from the last Pie public beta update)[...]
Click to expand...
Click to collapse
thanks, this do a trick, now i have Pie October installed

k3dar7 said:
thanks, this do a trick, now i have Pie October installed
Click to expand...
Click to collapse
So, if this is true then a thread which started out as a bit of a joke has actually been more useful that HMD support?
Having a Nokia phone really doesn't stop amazing me.

divvykev said:
So, if this is true then a thread which started out as a bit of a joke has actually been more useful that HMD support?
Having a Nokia phone really doesn't stop amazing me.
Click to expand...
Click to collapse
yes, is true
anyway, really thanks for your jokes thread i before some day from despair try contact HMD support... try tips as update without 4g enabled, update without sim inserted, update in safe mode, ended with tips wait for november update, maybe be full ota

k3dar7 said:
thanks, this do a trick, now i have Pie October installed
Click to expand...
Click to collapse
You're welcome, I'm glad I could help.

shailendra1993 said:
I have already got Android 9.1 with great new features:
1. Nokia camera has become better than Pixel 3, my friend wants my Nokia 7 Plus in exchange for his Pixel the new camera even features X-ray mode where you can see what's behind a wall, it uses Wifi and Radio signals to see what's behind a wall.
2. It works so flawlessly that even Fortnite is supported on this new build
3. Bootloader comes unlocked by default now, it's so open that now you will need to file a petition to close it.
Click to expand...
Click to collapse
Ha ha,this is funny,you made my day

December update issue

I am struggling trying to get the December update installed. Originally, I unlocked my bootloader, applied the November update, rooted the phone and installed the Floral kernel. Everything was working great. Since then I tried to install the latest version of the kernel and almost bricked the phone right away. I was able to get back on the November update, now I have the November update running, version 10.0.0 (QD1A.190821.014.C2, Nov 2019). I have not rooted or installed a custom kernel. I still have an unlocked bootloader. All I want to do now is install the December update, but when I install this version 10.0.0 (QQ1B.191205.011, Dec 2019, EMEA carriers, T-Mobile (US), Google Fi) - I have a "Google Fi" Pixel 4 XL purchased from the google store.. I can get it to load to the setup screen but I completely use touchscreen ability so the phone is useless.. My question is - Which December update is correct for my phone ? I am thinking it could be the next file under that one - 10.0.0 (QQ1B.191205.012.A1, Dec 2019)... But I am hesitant to attempt flashing a file I am unsure of. I have read that the reason I cant use the touchscreen is because the boot.img is different. I pushed the boot.img and pfpt.img (or whatever it is called) from that factory image and still it did not work. At this point I am almost ready to return it to bone stock out of frustration. Please advise how to verify what the correct file is, or the most simple method to get the update running. Thank you !
TL;DR
Would like december update installed - having a hard time figuring out the correct factory image to use or getting it to work correctly

The first build would be correct for you on Google Fi. Don't know why you're having touchscreen issues.
Are you trying to maintain root? If so, flash the factory image with the -w flag removed from the flash-all.bat. Also, make sure you disable Magisk modules if you have any installed, before flashing the factory image.
If you want to start fresh, leave the flag alone and just flash the image.
Edit: Didn't see that you aren't even rooted or anything in your wall of text.
Either way, since you're having issues, best to clean flash and start over. Once your running properly, I'd say read everything in the forums to get a grasp of everything before doing anything to modify the phone again.

subarubdub said:
I am struggling trying to get the December update installed...
...having a hard time figuring out the correct factory image to use or getting it to work correctly
Click to expand...
Click to collapse
https://forum.xda-developers.com/pi...-10-q-root-t3996969/post80774791#post80774791
In the guide above read Prerequisites, and #1, then do #4 to install factory image, then #9 to root/reroot
If you are reading the guide with the XDA app tap the three dots (on the top right) select open in browser.

subarubdub said:
I am struggling trying to get the December update installed. Originally, I unlocked my bootloader, applied the November update, rooted the phone and installed the Floral kernel. Everything was working great. Since then I tried to install the latest version of the kernel and almost bricked the phone right away. I was able to get back on the November update, now I have the November update running, version 10.0.0 (QD1A.190821.014.C2, Nov 2019). I have not rooted or installed a custom kernel. I still have an unlocked bootloader. All I want to do now is install the December update, but when I install this version 10.0.0 (QQ1B.191205.011, Dec 2019, EMEA carriers, T-Mobile (US), Google Fi) - I have a "Google Fi" Pixel 4 XL purchased from the google store.. I can get it to load to the setup screen but I completely use touchscreen ability so the phone is useless.. My question is - Which December update is correct for my phone ? I am thinking it could be the next file under that one - 10.0.0 (QQ1B.191205.012.A1, Dec 2019)... But I am hesitant to attempt flashing a file I am unsure of. I have read that the reason I cant use the touchscreen is because the boot.img is different. I pushed the boot.img and pfpt.img (or whatever it is called) from that factory image and still it did not work. At this point I am almost ready to return it to bone stock out of frustration. Please advise how to verify what the correct file is, or the most simple method to get the update running. Thank you !
TL;DR
Would like december update installed - having a hard time figuring out the correct factory image to use or getting it to work correctly
Click to expand...
Click to collapse
Go by the recommended factory image based on your carrier found here...https://support.google.com/pixelphone/thread/21769134?hl=en
You may have indeed already flashed the correct one, or maybe not, but it appears you have. Also, have you tried switching to your inactive slot, and flashed it again? I would at least try that before anything else to see if you get your touch input back.

ilal2ielli said:
The first build would be correct for you on Google Fi. Don't know why you're having touchscreen issues.
Are you trying to maintain root? If so, flash the factory image with the -w flag removed from the flash-all.bat. Also, make sure you disable Magisk modules if you have any installed, before flashing the factory image.
If you want to start fresh, leave the flag alone and just flash the image.
Edit: Didn't see that you aren't even rooted or anything in your wall of text.
Either way, since you're having issues, best to clean flash and start over. Once your running properly, I'd say read everything in the forums to get a grasp of everything before doing anything to modify the phone again.
Click to expand...
Click to collapse
Ive been rooting and playing with android phones since my G1. This is suddenly an issue for me haha, I think it was my platform tools or something.. a few things in my android studio needed updating. Now It is working ! thanks for the help everyone.. :silly:

March - Broken Face Unlock

I was on the January patch, unrooted, sideloaded the new March update(with -w taken out of the sh and bat files) then booted up and patched the boot file with magisk, rebooted to flash patched boot and when I finally got back in and started checking my apps for functionality, I noticed the face unlock was being slow. I deleted my face unlock and went to reregister and got the error "Enrollment was not completed. Face enrollment didn't work."
I tried deleting all security from the phone and rebooting to readd, but I still get the error.
Ideas?

ibphantom said:
I was on the January patch, unrooted, sideloaded the new March update(with -w taken out of the sh and bat files) then booted up and patched the boot file with magisk, rebooted to flash patched boot and when I finally got back in and started checking my apps for functionality, I noticed the face unlock was being slow. I deleted my face unlock and went to reregister and got the error "Enrollment was not completed. Face enrollment didn't work."
I tried deleting all security from the phone and rebooting to readd, but I still get the error.
Ideas?
Click to expand...
Click to collapse
You sideloaded the factory image or fastbooted it?
At any rate, you could try fastbooting the factory image again to both slots, one at a time, to see if that works. However, more than likely you'll need to do a factory reset. Going forward, it's always a good idea to remove face ID before doing a monthly update. Haven't had a problem with any update in that regard since I got the device last October :good:

Happened to me too. I fixed it by dirty flashing the march factory image. (I noticed that issue started after I flashed fsociety kernel)
(I was on a clean install of the march factory image; already did a factory reset before flashing and already cleared security/face data/etc beforehand. )

neo_lithic3K said:
Happened to me too. I fixed it by dirty flashing the march factory image. (I noticed that issue started after I flashed fsociety kernel)
(I was on a clean install of the march factory image; already did a factory reset before flashing and already cleared security/face data/etc beforehand. )
Click to expand...
Click to collapse
Could you explain your process just a little more. You deleted face data and then how did you dirty flash? Did you just 'adb reboot bootloader' then 'adb flash marchupdate.zip?

ibphantom said:
Could you explain your process just a little more. You deleted face data and then how did you dirty flash? Did you just 'adb reboot bootloader' then 'adb flash marchupdate.zip?
Click to expand...
Click to collapse
Dirty flash in essence means removing the -w characters from the flash-all.bat file. This prevents your data from being wiped, when you fastboot the factory image. It's pretty much like taking an OTA :good:

Yup, I can definitely go into more detail., but my situation probably doesn't match yours completely.
As badger50 mentioned, dirty flash is basically removing the -w. In my case, I removed the '-w" from the March factory image's (flash-all.bat) file. Then I cleared the face data from settings-security, removed any pins/pws/patterns, & did a factory reset from settings-system (b/c I read that the titan chip can only be cleared via factory reset). I then booted to bootloader (adb reboot bootloader or use the power-volume down method) and ran the edited flash-all.bat. That basically reinstalls the factory image without erasing my user data.
The reason I dont sideload OTA is because I never had good luck with sideloading. Something comes out wrong or I run into odd issues.
ibphantom said:
Could you explain your process just a little more. You deleted face data and then how did you dirty flash? Did you just 'adb reboot bootloader' then 'adb flash marchupdate.zip?
Click to expand...
Click to collapse

neo_lithic3K said:
Yup, I can definitely go into more detail., but my situation probably doesn't match yours completely.
As badger50 mentioned, dirty flash is basically removing the -w. In my case, I removed the '-w" from the March factory image's (flash-all.bat) file. Then I cleared the face data from settings-security, removed any pins/pws/patterns, & did a factory reset from settings-system (b/c I read that the titan chip can only be cleared via factory reset). I then booted to bootloader (adb reboot bootloader or use the power-volume down method) and ran the edited flash-all.bat. That basically reinstalls the factory image without erasing my user data.
The reason I dont sideload OTA is because I never had good luck with sideloading. Something comes out wrong or I run into odd issues.
Click to expand...
Click to collapse
Thank you. You're a wonderful person and I appreciate your time.:fingers-crossed:
Thanks to you as well Badger50:victory:

factory reset fixes it all... for some reason using -w may or may not delete something that a factory reset does?

Confirm. Works only factory reset from settings.
Dirty, clean flash, safe mode - doesn't work.

I've never had a problem on the pixel devices leaving my security in when flashing the full image but it can't hurt to remove it. I agree with others above as regards flashing it BTW, it's easy and works every time without having to research the secret handshake sometimes needed to get the OTA to go. You also don't have to wait for it and you don't have to deal with problems like this that come up here and there when sideloading an OTA.
I'm not really sure why so many are resistant to flashing the full image but you get a lot of push-back on it here which seems misplaced; over time you're ahead of the game.

If I install the March 2020 factory image, face unlock works fine. If I install the April 2020 OTA, face unlock breaks. If I install April 2020 or May 2020 factory images, face unlock is broken. SO FRUSTRATING!!!

jtwebfusion said:
If I install the March 2020 factory image, face unlock works fine. If I install the April 2020 OTA, face unlock breaks. If I install April 2020 or May 2020 factory images, face unlock is broken. SO FRUSTRATING!!!
Click to expand...
Click to collapse
Same it will only work for me on March or DP 3 of the beta. Just RMAd my Pixel

TechOut said:
Same it will only work for me on March or DP 3 of the beta. Just RMAd my Pixel
Click to expand...
Click to collapse
I have an RMA in for mine, but Google has nothing in stock.

jtwebfusion said:
I have an RMA in for mine, but Google has nothing in stock.
Click to expand...
Click to collapse
I'm doing one last full wipe and flash of the may update in hopes it might just work.
---------- Post added at 01:12 AM ---------- Previous post was at 01:10 AM ----------
jtwebfusion said:
I have an RMA in for mine, but Google has nothing in stock.
Click to expand...
Click to collapse
How long did it take for you to get the email with shipping label? Been waiting about 5 minutes and nothing yet.

TechOut said:
I'm doing one last full wipe and flash of the may update in hopes it might just work.
---------- Post added at 01:12 AM ---------- Previous post was at 01:10 AM ----------
How long did it take for you to get the email with shipping label? Been waiting about 5 minutes and nothing yet.
Click to expand...
Click to collapse
It took about 5-10 minutes to get it...

jtwebfusion said:
It took about 5-10 minutes to get it...
Click to expand...
Click to collapse
Yeah just got it and while scheduling the fedex pickup realized I mistyped the address so had to cancel and do it all over...

jtwebfusion said:
I have an RMA in for mine, but Google has nothing in stock.
Click to expand...
Click to collapse
Are they repairing any of these or have they just been replacing them?

TechOut said:
Are they repairing any of these or have they just been replacing them?
Click to expand...
Click to collapse
You'll get a refurbished one

Pixel 4 "FLAME" March 2020 QQ2A.200305.003 boot.img - Stock and Magisk v20.4 Patched

Pixel 4 "FLAME" March 2020 QQ2A.200305.003 boot.img - Stock and Magisk v20.4 Patched
Hey all, I just updated my wife's P4 to Magisk 20.4 as of yesterday and have had no issues so far on the new version (nor on my P4XL). Here are the stock and recently newly updated Magisk patched (v20.4) boot images. I couldn't direct install the update on either of the phones via Magisk Manager, so I figured I would share these images.
Stock March 2020 boot image: https://www.androidfilehost.com/?fid=4349826312261757144
Magisk Patched (v20.4) March 2020 boot image: https://www.androidfilehost.com/?fid=4349826312261757143
Remember, these are ONLY for those on QQ2A.200305.003 firmware already. Don't flash if you don't know what you're doing.

Hey i5lee8bit,
Thanks for posting the p4 OTA boot files. worked perfectly. I have a p4xl as well. How do I extract the boot image from the device? I can not find the new boot image online from google or anything.

Which method did you use to flash? I've tried it a few different ways and they don't work. I'm thinking on factory resetting and trying again but I don't want to do if I don't have to. I've had no problem rooting my pixel 4 on any of the other updates but for some reason I can't root the March update. It looks like things flash fine but when the phone reboots it gets to a black screen and just stays there. I know it can take a while during app optimization so I let it set over night. Still on a black screen the next morning.

falawefulwaffle said:
Hey i5lee8bit,
Thanks for posting the p4 OTA boot files. worked perfectly. I have a p4xl as well. How do I extract the boot image from the device? I can not find the new boot image online from google or anything.
Click to expand...
Click to collapse
I'm not sure, I just grab them from the factory images (https://developers.google.com/android/images#coral). If it's not there, I wouldn't know. I came from years of HTC devices, but even then we either used TWRP or RUU decryption tool / firmware zips. Not sure if there's a way to extract directly from the device using dd or adb commands, but even then that was done using TWRP. Not sure if there's an alternate method; I'm not the right person to ask either, sorry. Tulsadiver's thread that I linked to for the other guy mentions a boot.img extractor, but I've never used it.
But if the boot file I provided worked perfectly for you, I would assume that means you are using the USA Unlocked model, and it should be available on the developers.google.com link I posted.
Spookymyo said:
Which method did you use to flash? I've tried it a few different ways and they don't work. I'm thinking on factory resetting and trying again but I don't want to do if I don't have to. I've had no problem rooting my pixel 4 on any of the other updates but for some reason I can't root the March update. It looks like things flash fine but when the phone reboots it gets to a black screen and just stays there. I know it can take a while during app optimization so I let it set over night. Still on a black screen the next morning.
Click to expand...
Click to collapse
From bootloader, just the simple fastboot flash boot name_of_boot_image.img
It sounds like you OTA'd to the March build? And you previously had it Magisk rooted on a prior firmware version? It could be a module not playing nice. Maybe try booting into Magisk Core mode, see Tulsadiver's thread: https://forum.xda-developers.com/pixel-4/how-to/magisk-modules-disabler-booting-magisk-t3991739
Sorry for the delayed responses btw. Quarantine + work + school + new baby = wtf.

i5lee8bit said:
I'm not sure, I just grab them from the factory images (https://developers.google.com/android/images#coral). If it's not there, I wouldn't know. I came from years of HTC devices, but even then we either used TWRP or RUU decryption tool / firmware zips. Not sure if there's a way to extract directly from the device using dd or adb commands, but even then that was done using TWRP. Not sure if there's an alternate method; I'm not the right person to ask either, sorry. Tulsadiver's thread that I linked to for the other guy mentions a boot.img extractor, but I've never used it.
But if the boot file I provided worked perfectly for you, I would assume that means you are using the USA Unlocked model, and it should be available on the developers.google.com link I posted.
From bootloader, just the simple fastboot flash boot name_of_boot_image.img
It sounds like you OTA'd to the March build? And you previously had it Magisk rooted on a prior firmware version? It could be a module not playing nice. Maybe try booting into Magisk Core mode, see Tulsadiver's thread: https://forum.xda-developers.com/pixel-4/how-to/magisk-modules-disabler-booting-magisk-t3991739
Sorry for the delayed responses btw. Quarantine + work + school + new baby = wtf.
Click to expand...
Click to collapse
Thanks for the reply. I ended up getting it to work using the "payload_dumper-win64" method i found in another thread to extract the boot.img from the payload.bin file. Turns out the OTA file was online from google.
To updatePixel 4 xl with "coral-ota-qq2a.200305.003-3b25765d" MAach update OTA software:
- uninstalled Magisk
-updated software
-reinstalled magisk
-patched the boot img from payload.bin
-pushed modified boot to device
-Done
Everything seems to be working well. I got to use python for the first time, so that was kind of fun. I was a flashing machine back around the galaxy s4.

I got root working. Spent so much time trying different things and all I had to do was factory reset my phone. There must have been some file or module interfering with the process. Once I reset my phone the root process went without error. ?*

Fixing bootloop?

so my bramble spazzed and did a soft reboot and then the system ui wouldn't load (I was able to use the phone, but not the status bar, navbar). i disabled the lockscreen security and removed my magisk modules. then i tried flashing the stock firmware (december) *after erasing the -w*, then i tried sideloading the december ota via recovery, then i tried to do the same withe november versions and then again the december, you get the idea. nothing doing, the best i get is it'll get to "pixel is loading" for a split second then go to bootloader. anyone have any suggestions for me?
sorry, asking on the P5 forum because the phones are so similar the P5 forum is more active.

mistermojorizin said:
so my bramble spazzed and did a soft reboot and then the system ui wouldn't load (I was able to use the phone, but not the status bar, navbar). i disabled the lockscreen security and removed my magisk modules. then i tried flashing the stock firmware (december) *after erasing the -w*, then i tried sideloading the december ota via recovery, then i tried to do the same withe november versions and then again the december, you get the idea. nothing doing, the best i get is it'll get to "pixel is loading" for a split second then go to bootloader. anyone have any suggestions for me?
sorry, asking on the P5 forum because the phones are so similar the P5 forum is more active.
Click to expand...
Click to collapse
Are you booting on the right slot ?

jaythenut said:
Are you booting on the right slot ?
Click to expand...
Click to collapse
Thanks, yes I was. I ended up dirty flashing the stock firmware from December and from November and sideloading otas from both months over and over till it was working again. Took all day but I saved my data. I was flashing the all carrier December image as they was the one I was on, not flashing verizon one did the trick. Something to keep in mind for next time.