Database Users

Fire OS 5 developer preview available

DO NOT USE THIS METHOD ANYMORE DUE TO BRICKS WITH LATEST DEV PREVIEW. PLEASE FOLLOW ONE OF @DoLooper 'S GUIDES TO GET OS5.0
Warning: I am not responsible for any damage that may occur. Follow this video at your own risk
Just got an email about the Fire OS 5 developer preview. It's available for the fire HD6 and HD7. It runs lollipop.
developer.amazon.com/public/solutions/platforms/android-fireos?sc_channel=EM&sc_campaign=FireOSPreview&sc_detail=GetPreview
It's downloading now on my device. I'll let you know if I figure anything out.
Edit: Amazing update so far. Much closer to stock android! It even has wallpapers enabled by default. It has a few strange grapgical glitches but nothing to worry about. Many of the apps are stock instead of amazonified. For example the browser and even Launcher are stock aosp. Even the recents activity is aosp. I really do like this. If we never get a custom rom, this will be the best choice as an os.
DO NOT USE METHOD DESCRIBED IN THIS VIDEO ANYMORE DUE TO BRICKS ON LATEST DEV PREVIEW. INSTEAD, DOWNLOAD update-kindle-devpreview_ariel-20.5.2.2_user_522041550.bin FROM forum.xda-developers.com/fire-hd/general/lolipop-ota-capture-t3141810 AND PLACE IT ON THE ROOT OF YOUR SD CARD. THEN GO TO SETTINGS>DEVICE>SYSTEM UPDATES AND PRESS UPDATE etc.
Downgrade Instructions:
1. Download firmware from http://www.amazon.com/gp/help/customer/display.html?nodeId=201596860
2. reboot device into recovery via "adb reboot recovery" or by holding power, volume up, volume down all at the same time on boot
3.use volume and power keys to select "apply update from adb"
4.sideload the firmware with "adb sideload update-kindle-20.4.5.3_user_453011120.bin"
5.wipe data/factory reset
6.reboot

Did you install this via TWRP and kept root, or just the regular Amazon update?
How is the speed? Slower than 4.5.x, or about the same?

bibikalka said:
Did you install this via TWRP and kept root, or just the regular Amazon update?
How is the speed? Slower than 4.5.x, or about the same?
Click to expand...
Click to collapse
regular amazon update. Seems about the same speed
Sent from my LG-V480 using Tapatalk

powerpoint45 said:
regular amazon update. Seems about the same speed
Sent from my LG-V480 using Tapatalk
Click to expand...
Click to collapse
So you just gave up on the whole root business ? Back to the Amazon empire for good ?
Amazon probably could not keep up with the changes required for Lollipop 5, and so they are switching to stock versions of stuff. Which is good news for us, those who manage to keep root going forward ! I see the light at the end of the tunnel!

powerpoint45 said:
Edit: Amazing update so far. Much closer to stock android! It even has wallpapers enabled by default. It has a few strange grapgical glitches but nothing to worry about. Many of the apps are stock instead of amazonified. For example the browser and even Launcher are stock aosp. Even the recents activity is aosp. I really do like this. If we never get a custom rom, this will be the best choice as an os
Click to expand...
Click to collapse
Sounds incredible! I don't know about developer previews, so just to clarify: Amazon has killed the carousel and is (finally) providing aosp-like launcher that allows wallpaper?!
Are you testing Kingroot yet? lol!
.

Some pics

bibikalka said:
So you just gave up on the whole root business ? Back to the Amazon empire for good ?
Amazon probably could not keep up with the changes required for Lollipop 5, and so they are switching to stock versions of stuff. Which is good news for us, those who manage to keep root going forward ! [emoji14] I see the light at the end of the tunnel!
Click to expand...
Click to collapse
ya pretty much at least as of now unfortunately. I made the mistake of updating to the 4.x version and lost root so I'm stuck for now
Sent from my LG-V480 using Tapatalk

DoLooper said:
Sounds incredible! I don't know about developer previews, so just to clarify: Amazon has killed the carousel and is (finally) providing aosp-like launcher that allows wallpaper?!
Are you testing Kingroot yet? lol!
.
Click to expand...
Click to collapse
Well at least in the preview. Also I need to check if the amazon Launcher is still disabled. Some reason pm unblock was not working for me earlier. That may have been changed to prevent that stuff.. No KingRoot does not work
Sent from my LG-V480 using Tapatalk

I put up a video if anyone is interested btw
Sent from my LG-V480 using Tapatalk

Kingroot
I tested, and Kingroot unfortunately does not work (which was to be expected).

would it be possible to remove the recovery and bootloader it comes with an flash it to a device with twrp and an unlocked bootloader?

siegesoldier said:
would it be possible to remove the recovery and bootloader it comes with an flash it to a device with twrp and an unlocked bootloader?
Click to expand...
Click to collapse
it is only plausible if we can either root this version so we can grab the partition we want, find the direct download to the bin update file, or somehow grab the update file once it's downloaded via otaverify
Sent from my LG-V480 using Tapatalk

All of the Amazon apps crash for me and an error message saying there was an internal error for third party apps is popping up for me. Is anyone else getting the same problem?

Bahamutmaster said:
All of the Amazon apps crash for me and an error message saying there was an internal error for third party apps is popping up for me. Is anyone else getting the same problem?
Click to expand...
Click to collapse
I'd sugest doing a factory reset
Sent from my LG-V480 using Tapatalk

considering doing that anyway - the screen is extremely twitchy and seems to react if you simply look at it wrong lol.
but I really like this, and probably won't even try to -> 4.5.3 -> root. agree with the comments about lollipop possibly being different enough they may never try to re-spamazon-ify this OS as hard as they have in the past. (but I'll still keep updates blocked if possible lol)
---------- Post added at 08:25 PM ---------- Previous post was at 08:21 PM ----------
oh and good call on speeding up by hitting system update. although surprisingly my did it on its own within minutes of applying for 5.0 on spamazon.
(which is doubly-hilarious, because I had gone through their phone support in an effort to downgrade mine to 4.5.3, and after tens of minutes of trying to convince them that YES IT IS POSSIBLE, they agreed and said it would take up to 24 hours. naturally it never happened, and subsequent calls to try to make it happen were even more painful lol. trying to explain the whole thing again over and over, surprising since obvs they had records/logs of the initial request...)

tarvoke said:
considering doing that anyway - the screen is extremely twitchy and seems to react if you simply look at it wrong lol.
but I really like this, and probably won't even try to -> 4.5.3 -> root. agree with the comments about lollipop possibly being different enough they may never try to re-spamazon-ify this OS as hard as they have in the past. (but I'll still keep updates blocked if possible lol)
---------- Post added at 08:25 PM ---------- Previous post was at 08:21 PM ----------
oh and good call on speeding up by hitting system update. although surprisingly my did it on its own within minutes of applying for 5.0 on spamazon.
(which is doubly-hilarious, because I had gone through their phone support in an effort to downgrade mine to 4.5.3, and after tens of minutes of trying to convince them that YES IT IS POSSIBLE, they agreed and said it would take up to 24 hours. naturally it never happened, and subsequent calls to try to make it happen were even more painful lol. trying to explain the whole thing again over and over, surprising since obvs they had records/logs of the initial request...)
Click to expand...
Click to collapse
You might wamt to do a factory reset as well. Seems to have fixed some of my issues i've had before in 5.0. Good thing you can downgrade without calling now
Sent from my Nexus 7 using Tapatalk

had definitely been considering the reset - thing was getting abominably super-hot and the screen was absolutely not behaving. but next day, it seems to have changed its mind lol. possibly just b/c it cooled down.
I wonder also if some of the weird behavior was due to some spamazon packages still remaining pm-blocked, even after the OS update? obvs a factory reset would clear this, although I could also just use the debloater tool to check. (well, whenever I get a chance to run windows)
also also, can you report any experience with the stock kindle-reader app in this version? (up until now, I have been using the hackified version that I believe you can be thanked for repackaging)
and getting some consistent failures on spamazon-appstore apps, but not all of them. instant video and mp3/music are fine, but xbox-smartglass and spamazon-echo always fail. probably also just indicates need to reset the whole thing...

ryanyz10 said:
I tested, and Kingroot unfortunately does not work (which was to be expected).
Click to expand...
Click to collapse
if kingroot didnt work on 4.5.4 why would it work on 5.0 at all. its not like they released 5.0 with the same vulnerable kernel as 4.5.3 and below

off topic, whoops.

ryanyz10 said:
LOL it's worth a shot. You get nowhere if you don't try. Why are you so mad about it??? It didn't affect you in any way, and you didn't have to reply either.
Click to expand...
Click to collapse
nobody said i was mad about it, that was just your own assumption, and you didnt have to reply either LOL

HELP ME

okay guys so this is the dilemma...
i was rooted on 7.1.1 dp1 with the flashable pixel zip. I received the DP2 OTA somehow, tried to install but it just restarted the phone.. nothing changed.
I eventually got bored of it and tried flashing the resurrection ROM. however, i got stuck on the boot screen. so i unrooted and flashed the factory image off googles devs site. Now i want to go update to DP2, i have enrolled in the beta but still nothing comes up. i have unenrolled and enrolled heaps of times and nothing is happening.
thanks for any help

It's not immediate. Enroll in the beta again. Wait a couple of hours. Eventually it'll pop up. Reboot after a few hours if you still don't have it.

If all else fails, the DP2 image is available online at developer.android.com/preview/download.html if you don't get the OTA. Just download from the developer site, extract, put phone into fastboot mode, and then run the flashall.bat. This will flash your phone back to stock on developer preview 2. The DP2 build number is NPF26F (You said you had an image from the dev site, check the build number).

RoyJ said:
It's not immediate. Enroll in the beta again. Wait a couple of hours. Eventually it'll pop up. Reboot after a few hours if you still don't have it.
Click to expand...
Click to collapse
I was enrolled in the beta for a couple of days and I still haven't gotten anything
Sent from my Nexus 6P using XDA-Developers mobile app

krisyarno said:
If all else fails, the DP2 image is available online at developer.android.com/preview/download.html if you don't get the OTA. Just download from the developer site, extract, put phone into fastboot mode, and then run the flashall.bat. This will flash your phone back to stock on developer preview 2. The DP2 build number is NPF26F (You said you had an image from the dev site, check the build number).
Click to expand...
Click to collapse
Silly questions but do I need to be rooted to flash the dp2 image ? And no, my apologies. I've got 7.0 NBD91K from Google, not the dev site. My bad!
Sent from my Nexus 6P using XDA-Developers mobile app

agerciaffaa said:
Silly questions but do I need to be rooted to flash the dp2 image ? And no, my apologies. I've got 7.0 NBD91K from Google, not the dev site. My bad!
Sent from my Nexus 6P using XDA-Developers mobile app
Click to expand...
Click to collapse
Nope! There's no need to be rooted! You do, however, need to have an unlocked bootloader. But I'd imagine you'd have that if you're flashing roms :laugh:
And ah! I'm on the same page as you now about the google developers factory images site. With the android developers site I posted, just scroll down on that page and find the nexus 6P link and download that! This will wipe your data though.
Your problem originally that caused the DP2 update to not work was the pixel mod. If you have that flashed, the ota update doesn't work. I had the same problem. But the good news is, you can get pixel mods for DP2 too! I'm using one too.

krisyarno said:
Nope! There's no need to be rooted! You do, however, need to have an unlocked bootloader. But I'd imagine you'd have that if you're flashing roms :laugh:
And ah! I'm on the same page as you now about the google developers factory images site. With the android developers site I posted, just scroll down on that page and find the nexus 6P link and download that! This will wipe your data though.
Your problem originally that caused the DP2 update to not work was the pixel mod. If you have that flashed, the ota update doesn't work. I had the same problem. But the good news is, you can get pixel mods for DP2 too! I'm using one too.
Click to expand...
Click to collapse
i will know flash dp2 hahaha
and yes i just figured id try to install it only because i received it. i mean, i was able to receive it and it noticed that it was a 6p depsite having flashed the pixel mod

agerciaffaa said:
i will know flash dp2 hahaha
and yes i just figured id try to install it only because i received it. i mean, i was able to receive it and it noticed that it was a 6p depsite having flashed the pixel mod
Click to expand...
Click to collapse
Yeah, it doesn't hurt to try (unless it does). I did the same thing because I was curious about that. I figured it would update and wipe the pixel mod, but nope! :laugh: I hope everything goes smoothly :good:

Beta 5/RC1 of Q on deck!

Beta 5/RC1 of Q is officially in the on-deck circle for registered devices; I'm downloading it now for my 3a. (OTA). The big attraction for me - dark mode changes (I enabled dark mode with the previous beta).

PGHammer said:
Beta 5/RC1 of Q is officially in the on-deck circle for registered devices; I'm downloading it now for my 3a. (OTA). The big attraction for me - dark mode changes (I enabled dark mode with the previous beta).
Click to expand...
Click to collapse
Let us know if it boots without fuss

SketchyStunts said:
Let us know if it boots without fuss
Click to expand...
Click to collapse
Working fine here. My 3a restarted once after first boot but it's working fine now

What Issues?
baddesthad said:
Working fine here. My 3a restarted once after first boot but it's working fine now
Click to expand...
Click to collapse
No issues at all; just one quibble - no dark-mode launch animation (even though systemwide dark mode is still active, as I set it with beta 4). And I'm admitting it's a quibble. (It should be present if you have systemwide dark mode set.)

anyone know how to root on beta5??

jayxiao171735 said:
anyone know how to root on beta5??
Click to expand...
Click to collapse
With the latest Magisk Canary, I guess. Haven't tried it myself because latest Pie security patch works like a charm for my needs.

baddesthad said:
Working fine here. My 3a restarted once after first boot but it's working fine now
Click to expand...
Click to collapse
I would double check you didn't fall back to DP4. A reboot means it might have failed to boot to DP5 and falled back to DP4 slot.

Uzephi said:
I would double check you didn't fall back to DP4. A reboot means it might have failed to boot to DP5 and falled back to DP4 slot.
Click to expand...
Click to collapse
I was on the stock July update (phone is a week old) and this is the first developer preview update I received. The build number I have is below

Where is everyone getting beta 5? I only have beta 4 available.

stevew84 said:
Where is everyone getting beta 5? I only have beta 4 available.
Click to expand...
Click to collapse
OTA here

Uzephi said:
OTA here
Click to expand...
Click to collapse
Are you already on Q4? That update is small.
I'm flashing the June stock image since the July one has an issue with the Q OTA.

stevew84 said:
Are you already on Q4? That update is small.
I'm flashing the June stock image since the July one has an issue with the Q OTA.
Click to expand...
Click to collapse
That's where I screwed up initially. Pie with July security patch... Took OTA beta 4 which had June's patch. This was withing a hour of buying it lol.

SketchyStunts said:
That's where I screwed up initially. Pie with July security patch... Took OTA beta 4 which had June's patch. This was withing a hour of buying it lol.
Click to expand...
Click to collapse
I went to the June image and now there is no Q beta available...even though I'm enrolled in the beta program. Weird. I've had the beta previously.
EDIT: got it. thanks.

stevew84 said:
Are you already on Q4? That update is small.
I'm flashing the June stock image since the July one has an issue with the Q OTA.
Click to expand...
Click to collapse
Yes, I went from Q4 to Q5. Needed a reboot as update was stuck at optimizing apps for over 30 minutes.

OTA in Both Caases
Uzephi said:
Yes, I went from Q4 to Q5. Needed a reboot as update was stuck at optimizing apps for over 30 minutes.
Click to expand...
Click to collapse
Beta 4 (via OTA) from default Pie two days ago, and beta 5/RC1 (from beta 4) today (also via OTA). I don't have the proper cables to connect to my PC (all my cables with the proper end at the PC end, can't connect to my 3a - because they are - at the phone end - USB-B - not USB-C; if I had even a USB-to-USB cable, I would not be in this pickle).

PGHammer said:
Beta 4 (via OTA) from default Pie two days ago, and beta 5/RC1 (from beta 4) today (also via OTA). I don't have the proper cables to connect to my PC (all my cables with the proper end at the PC end, can't connect to my 3a - because they are - at the phone end - USB-B - not USB-C; if I had even a USB-to-USB cable, I would not be in this pickle).
Click to expand...
Click to collapse
So basically you like to live dangerously....I can respect that :good:

Actually.....
SketchyStunts said:
So basically you like to live dangerously....I can respect that :good:
Click to expand...
Click to collapse
I live more dangerously testing Windows (which I have been doing since Windows 95 - the original one). Rather amusingly, I've been more conservative (if not downright chicken) when it comes to the phone side of operations - mostly because I've had to. Remember - until Q, Android beta testing was a lot more closed than the same for Windows. Heck - even with Q, where is the most OPEN portion of the testing program? Easily explained - the Pixels. Every Pixel ever built - from the first one to the current one - can- and could - opt-in to it. Problem - until now, Pixels were chained to a limited set of providers. (In the United States, a grand total of two - Verizon and Google itself (via Fi).) The 3a and 3aXL changed that - as long as you had a nano-SIM, and $479USD (at worst), you could get a Pixel and activate it. I'm not on Verizon - I'm not on a Big Four carrier, either. What carrier am I on? Tracfone - an MVNO. (Tracfone uses the towers of all of the Big Four carriers; with the S7 - the phone my SIM came out of, I used the towers of T-Mobile AKA the Uncarrier.) Since I've had the opportunities, I've paid it back, and paid it forward (when and where possible). The Pixel 3a makes it possible - so why not? However, I don't recommend it due TO that it lets me pay it forward - quite aside from that, the Pixel 3a - merely as a mainstream/midrange user - is the best-used and best-supported such new phone. THAT is why I recommend it.
#teampixel #whatcamera?

xFirefly93 said:
With the latest Magisk Canary, I guess. Haven't tried it myself because latest Pie security patch works like a charm for my needs.
Click to expand...
Click to collapse
sorry, this method seems doesn't work, when I use Magisk canary to create the patched boot img, it said that failed to build....any solutions for that?

jayxiao171735 said:
sorry, this method seems doesn't work, when I use Magisk canary to create the patched boot img, it said that failed to build....any solutions for that?
Click to expand...
Click to collapse
Ask John over at Twitter.

jayxiao171735 said:
sorry, this method seems doesn't work, when I use Magisk canary to create the patched boot img, it said that failed to build....any solutions for that?
Click to expand...
Click to collapse
I posted this in another thread you asked this question in, but I figured it would be good to post here to for the benefit of others.....
I found this on the latest Magisk Canary build thread.
tysj said:
Problem they're having is that it isn't outputting the patched boot.img as it says it is. I'm running to the same issue on my Pixel 3.
EDIT:
Somehow got it to work. Uninstalled Magisk Manager, re-downloaded again from the OP, decided to update Magisk Manager from the app, then tried patching the boot.img again which finally work. Flash the patched_boot in fastboot and all is well.
Click to expand...
Click to collapse
So it sounds like there is so issue with the Magisk Manager - either the user wasn't really on the latest build, or there is some sort of permission issue with writing files, etc. But it seems that reinstalling the manager fixes the issue and you should be able to get Magisk to modify the stock boot.img file as normal.

Android 10 factory images is live

Enjoy!
Currently two builds: QP1A.190711.019 and QP1A.190711.020
Factory Image: https://developers.google.com/android/images#sargo
OTA Image: https://developers.google.com/android/ota#sargo

No OTA here in Germany so far

Anyone know the difference between the two builds?
Sent from my Pixel 3a using Tapatalk

Neither in France

jerethi said:
Anyone know the difference between the two builds?
Click to expand...
Click to collapse
They have diferent checksums

jerethi said:
Anyone know the difference between the two builds?
Click to expand...
Click to collapse
"Within the .19 image META-INF\com\android\metadata, the post-timestamp UNIX value is 1565300664 which equates to 08/08/2019 @ 9:44pm (UTC).
Within the .20 image META-INF\com\android\metadata, the post-timestamp UNIX value is 1565743352 which equates to 08/14/2019 @ 12:42am (UTC).
Based on one of Google's release tool's code, this value seems to be utilized to determine whether it should perform an incremental or full OTA.
If I'm understanding their upgrade process correctly, the .19 image does not contain the September security patch. The .20 appears to be the full stable release with the September security patch.
It would appear .19 should support an incremental upgrade from the latest Android Pie (9) version, PQ3B.190801.002 but not bring you to the latest September security patch.
This leads me to believe that the .20 image is suitable for almost all OTAs. There may be carrier specific cases that one or the other should be utilized but nothing stands out too clearly within any of the immediately available metadata files."
- https://www.reddit.com/r/Android/comments/cz7lb1/android_10_images_are_live/eywlgww/

Do I have to do a factory reset , if I'm rooted on Android 9 to archive android 10 without any problems ?

I have just got the ota update, I'm updating from beta 6 and it's saying the update size is 41mb, is this correct?
Sent from my Pixel 3a using Tapatalk

Atiqx said:
Do I have to do a factory reset , if I'm rooted on Android 9 to archive android 10 without any problems ?
Click to expand...
Click to collapse
No, just uninstall magisk or flash stock boot.img. once that is done, you should OTA just fine.

upinsmoke7610 said:
I have just got the ota update, I'm updating from beta 6 and it's saying the update size is 41mb, is this correct?
Click to expand...
Click to collapse
On reddit they say that coming from beta the update file is only this small.

yabadabadooo said:
On reddit they say that coming from beta the update file is only this small.
Click to expand...
Click to collapse
Well I knew banking apps would not work on the beta but now I'm on the stable release and my banking app still will not even open, but of a nightmare really as I rely on it.
Sent from my Pixel 3a using Tapatalk

Got the OTA from pie right now 1188.8mb

I've just received the OTA notification here in Spain
---------- Post added at 08:50 PM ---------- Previous post was at 08:49 PM ----------
anyone knows if is there any difference, or added feature compared to the last beta version?

yabadabadooo said:
They have diferent checksums
Click to expand...
Click to collapse
A factory image is a full replacement - and is meant to replace everything (you'll lose all your data and else that isn't backed up). An OTA is an update - you lose nothing. If you're coming from a STOCK factory image (either a beta of 10 OR 9) and your phone is fine, you want the OTA; otherwise (including AOSP), you want the full factory image.

germany here, installing the update now, takes quite some time for being only 41mb, hope it works

I didn't want to wait for the OTA to be pushed to my phone, so I sideloaded it and the rooted it again with Magisk. My directions are accurate if anyone else wants to sideload the OTA. To be honest, the whole process is faster when you sideload anyway. So it is really a better solution than waiting for the OTA.
The initial boot took about 5 minutes. Don't get impatient and try to mess with the phone. Just let it do it's thing.

Got it 30 mins ago from stock rom over ota (1.1GB) in France.
Install was smooth and fast.
So far so good!
Enjoying the dark mode
#Edit: weather widget shows temperature in °F instead of °C while everything is setup right. Strange ^^

sic0048 said:
I didn't want to wait for the OTA to be pushed to my phone, so I sideloaded it and the rooted it again with Magisk. My directions are accurate if anyone else wants to sideload the OTA. To be honest, the whole process is faster when you sideload anyway. So it is really a better solution than waiting for the OTA.
The initial boot took about 5 minutes. Don't get impatient and try to mess with the phone. Just let it do it's thing.
Click to expand...
Click to collapse
Thank you sic0048! I followed your guide when my Pixel 3a was on 9 and it was smooth. The best instructions I have found and even bookmarked it.
I do have one quick question. I followed your instructions about updating the phone and keeping root, but I lost root after reboot. I probably did something wrong. :silly:
In your instructions under the "Custom Recovery Installation method" you state that TWRP doesn't support Android 10. So how do I root my phone again? Is it safe to use this method or should I use another one of your methods in this tutorial?

After update to 10, I was able to see "Enable DDS" toggle in phone information shortcut.
Now the toggle is gone.
Anyone else has this issue?

yabadabadooo said:
On reddit they say that coming from beta the update file is only this small.
Click to expand...
Click to collapse
I came from RC2 - the update is indeed that little.
However, you will have to wait for a 10-ready build of TWRP; the current TWRP is not ready (of course).

Question: how to solve the Pixel 4 sensors bug?

Ever since last week I got all sensors of the device not working for no apparent reason.
I've reported about this, but then found out it's a very known issue that wasn't solved by Google yet, and that it randomly occurs for Pixel devices of all kinds, starting from Android 10.
Because of this issue, none of these work: auto-rotate, active edge, flip to shhh, proximity, ambient light, double tap to wake...
I tried to do factory reset, I tried to re-flash the firmware, update it to Android R, but none of those helped. I wanted to flash Android 9 somehow, because it says that the issue starts on Android 10, but then noticed there is no Android 9 for Pixel 4.
Then I noticed that some claim they found a fix for it, but on Pixel 3-XL :
Ask someone with working sensors to share the following folder with you: root/mnt/vendor/persist/sensors. Please ensure the device they have is the same as yours (Pixel 3 (blueline) and Pixel 3 XL (crosshatch) are NOT the same devices). They should, ideally, share it as a *.tar file to keep the permissions of subfiles intact.
Instructions to generate this tar file are here: https://forum.xda-developers.com/pix...4/post80833171
On your rooted phone running Android 10, navigate to: root/mnt/vendor/persist/ and first of all, backup your /sensors/ folder. Then, paste the contents of the tar file in there so you have the sensors folder from the working device that was shared with you.
Reboot and report. You should have working sensors now.
Click to expand...
Click to collapse
Can anyone please help me on this?
Would this help for Pixel 4 too?
If so, could anyone please share the file here, so that I could try it ?

Why not just RMA? Yeah, you'll get a refurb but it will work correctly.

bobby janow said:
Why not just RMA? Yeah, you'll get a refurb but it will work correctly.
Click to expand...
Click to collapse
RMA? I'm not in a country that Google provides service. Only some stores even offer to sell the device.
Plus what if it happens again?

AndroidDeveloperLB said:
RMA? I'm not in a country that Google provides service. Only some stores even offer to sell the device.
Plus what if it happens again?
Click to expand...
Click to collapse
Reports are that it doesn't happen on a new or RMA device but that's moot in your case. I don't see many options for you other than waiting.

bobby janow said:
Reports are that it doesn't happen on a new or RMA device but that's moot in your case. I don't see many options for you other than waiting.
Click to expand...
Click to collapse
Waiting for what?
Do you have Pixel 4? Can you please share the exact files that are suggested there?
Maybe it could help?

AndroidDeveloperLB said:
Waiting for what?
Do you have Pixel 4? Can you please share the exact files that are suggested there?
Maybe it could help?
Click to expand...
Click to collapse
Wait for an update that fixes your issue. Some have said the Feb update did it, some say no. Maybe the March update? I don't know but if you can't RMA then either flash another rom or wait for a fix from Google. It's a known issue so hopefully it will be fixed soon.

bobby janow said:
Wait for an update that fixes your issue. Some have said the Feb update did it, some say no. Maybe the March update? I don't know but if you can't RMA then either flash another rom or wait for a fix from Google. It's a known issue so hopefully it will be fixed soon.
Click to expand...
Click to collapse
I had stock ever since I got Pixel 4 (had Pixel 2 before). Maybe a custom rom will fix it. Any that you can recommend? I thought there aren't any custom ROMs for it yet.
I actually don't know how to flash custom ROMs on Pixel 4. TWRP doesn't seem to be a possible solution on it yet, no?
I only succeeded rooting it with Magisk, by patching the boot file. Tried to do it on Android R (was worth it if it worked), but it didn't work, sadly.
On Pixel 2 I could use TWRP. For some reason I failed to let it stay, so I had to flash it each time via the PC just to run it. On Pixel 4 I couldn't even find TWRP. Maybe now it's available.

AndroidDeveloperLB said:
I had stock ever since I got Pixel 4 (had Pixel 2 before). Maybe a custom rom will fix it. Any that you can recommend? I thought there aren't any custom ROMs for it yet.
I actually don't know how to flash custom ROMs on Pixel 4. TWRP doesn't seem to be a possible solution on it yet, no?
I only succeeded rooting it with Magisk, by patching the boot file. Tried to do it on Android R (was worth it if it worked), but it didn't work, sadly.
On Pixel 2 I could use TWRP. For some reason I failed to let it stay, so I had to flash it each time via the PC just to run it. On Pixel 4 I couldn't even find TWRP. Maybe now it's available.
Click to expand...
Click to collapse
Hopefully, someone will jump in here and help you with a custom rom suggestion. I haven't bl unlocked since midway through my 5X so I'm not the one to ask. From what I understand TWRP is basically on hold but I could be wrong.

damn, after almost 3 years i come here with the same issue, seems like nobody linked the persist.img or fixed the issue here