Related
Good day!
I'm one of those ZF5 owners who won their bootloader-"defective" phones out of the ASS-US Trash Lottery. Due to this problem, we are faced with an issue that keeps us from unlocking our bootloaders and enjoying the life that most of you enjoy --- the life of having a non-stock ROM.
I approach you all with a hopeless heart. Is there any available custom ROM out there that will boot with stock ASS-US kernels? I've tried some, but they all had issues:
AOSP 5.0.2 by tank0412
No support for dual-SIM functionality (I need both SIMs).
Vibrator not working (It's not what you think), though not necessarily a problem.
PZ-SleekStock ROM v4 by PaletroxZ
Without its default Borets kernel (custom), it's basically just stock ROM with a custom boot animation.
Any info is appreciated. (Better yet, if a fix for freezing bootloaders comes out, please tell me as well!)
What i did was,
I flashed jelly bean raw fw,then unlocked the bootloader using the official unlocking app from asus's site, unlocked the bootloader,then i flashed lollipop raw fw (surprisingly the bootloader remained unlocked)as soon as everything flashed, i didn't booted to rom,instead rebooted to bootloader directly,flashed twrp 3.0 M4 and flashed my CleanStock ROM, now there's no freezing issue at all till now,its been a week no freezes...
My device is a501cg with 2gb ram and 8gb rom,1.6ghz processor...
prathmesh pande said:
What i did was,
I flashed jelly bean raw fw,then unlocked the bootloader using the official unlocking app from asus's site, unlocked the bootloader,then i flashed lollipop raw fw (surprisingly the bootloader remained unlocked)as soon as everything flashed, i didn't booted to rom,instead rebooted to bootloader directly,flashed twrp 3.0 M4 and flashed my CleanStock ROM, now there's no freezing issue at all till now,its been a week no freezes...
My device is a501cg with 2gb ram and 8gb rom,1.6ghz processor...
Click to expand...
Click to collapse
Can you confirm that you have been experiencing the freezing issues in the past?
Also, I believe that flashing stock firmware does not re-lock your bootloader (As implied by the issues of many problematic ZF5 users who tried to flash stock firmware but still had freezing issues.)
cnswico said:
Can you confirm that you have been experiencing the freezing issues in the past?
Also, I believe that flashing stock firmware does not re-lock your bootloader (As implied by the issues of many problematic ZF5 users who tried to flash stock firmware but still had freezing issues.)
Click to expand...
Click to collapse
Yes, i was facing a lottttt of freezing in the past, it was like minimum 4-5 times freezing per day...
(Also i faced random reboots during call mostly because double tap 2 wake i.e. zenmotion was enabled so i don't use it anymore....without dt2w enabled,no random reboots at all)
After doing the entire process mentioned in the previous post, till now no freezes...
prathmesh pande said:
Yes, i was facing a lottttt of freezing in the past, it was like minimum 4-5 times freezing per day...
(Also i faced random reboots during call mostly because double tap 2 wake i.e. zenmotion was enabled so i don't use it anymore....without dt2w enabled,no random reboots at all)
After doing the entire process mentioned in the previous post, till now no freezes...
Click to expand...
Click to collapse
You already tought posting your process into a new thread? It may fix everybody's or some of them bootloader's problem
Sent from my ZenFone 5 (A500CG) using XDA Labs
MarconiGRF said:
You already tought posting your process into a new thread? It may fix everybody's or some of them bootloader's problem
Sent from my ZenFone 5 (A500CG) using XDA Labs
Click to expand...
Click to collapse
I will tag my post to my ROM's thread ,hope so it will help
prathmesh pande said:
Yes, i was facing a lottttt of freezing in the past, it was like minimum 4-5 times freezing per day...
(Also i faced random reboots during call mostly because double tap 2 wake i.e. zenmotion was enabled so i don't use it anymore....without dt2w enabled,no random reboots at all)
After doing the entire process mentioned in the previous post, till now no freezes...
Click to expand...
Click to collapse
I tried what you said. 5 minutes in. BANG! My phone froze again.
I rebooted my phone, lasted less than a minute. Freeze, once again. Thanks for trying, anyway. My phone is hopeless.
cnswico said:
I tried what you said. 5 minutes in. BANG! My phone froze again.
I rebooted my phone, lasted less than a minute. Freeze, once again. Thanks for trying, anyway. My phone is hopeless.
Click to expand...
Click to collapse
With which android version ur device was originally shipped when u purchased it?
prathmesh pande said:
With which android version ur device was originally shipped when u purchased it?
Click to expand...
Click to collapse
1.17. Version which headed the official bootloader unlocker.
Hi,
before upgrading to January Oreo patch i was rooted with magisk, when i recived the notification of the update, disabled all the modules and restored the stock boot.img, then i installed magisk on the second slot for rooting the update and i rebooted.
When the device started i realized the is was with oreo december patch
Since then i can't no more receive any update through Ota.
I flashed the first nougat build in a desperate attempt of fixing my device but even with that i solved nothing, currently i'm on 7.8.23 build and it can't find any update.
I've checked my imei is it was in any blacklist but nothing, it's clean.
I've serched everywhere but i haven't found nobody with my same or similar problem.
Please don't answere with something like try to clean google framework data or do a factory reset.
Currently I'm desperate my only hope resides in this community.
thanks so much for any help!
Lollo Olearo said:
Hi,
before upgrading to January Oreo patch i was rooted with magisk, when i recived the notification of the update, disabled all the modules and restored the stock boot.img, then i installed magisk on the second slot for rooting the update and i rebooted.
When the device started i realized the is was with oreo december patch
Since then i can't no more receive any update through Ota.
I flashed the first nougat build in a desperate attempt of fixing my device but even with that i solved nothing, currently i'm on 7.8.23 build and it can't find any update.
I've checked my imei is it was in any blacklist but nothing, it's clean.
I've serched everywhere but i haven't found nobody with my same or similar problem.
Please don't answere with something like try to clean google framework data or do a factory reset.
Currently I'm desperate my only hope resides in this community.
thanks so much for any help!
Click to expand...
Click to collapse
Either wait for the update, because there are yet many people that haven't received yet, or wait for Xiaomi to release latest fastboot rom and flash it with Mi Flash.
The issue isn't the fact that i haven't received the latest January update, i can't receive any ota, as said, even from the first build it don't find anything.
I now, i can flash through fastboot or MiFlashTool but I'm trying to fixing my issue not pretending to forgot it.
Lollo Olearo said:
The issue isn't the fact that i haven't received the latest January update, i can't receive any ota, as said, even from the first build it don't find anything.
I now, i can flash through fastboot or MiFlashTool but I'm trying to fixing my issue not pretending to forgot it.
Click to expand...
Click to collapse
he just told you to wait - oh wait can you still see your imei? in case the number is gone than you have a bigger problem.....
Dont panic, there nothing wrong with your phone, the only thing that wrong is Xiaomi and their updates. Just wait for the next update.
ltf_195 said:
Dont panic, there nothing wrong with your phone, the only thing that wrong is Xiaomi and their updates. Just wait for the next update.
Click to expand...
Click to collapse
The truth is, that Xiaomi temporally suspended all updates due to amount of bugs. Also try restore your phone with Mi Flash and latest firmware version ( Android O) from http://en.miui.com But as I said it is Xiaomi's fault.
Thanks so much for the help,
Yes my imei still there, i know the issue with ota that xiaomi had but i guess that at least i should be able of seeing something, i can understand not receiving the latest update but i don't get anything at all.
I hope there isn't nothing wrong with my phone or at least something i can fix.
Again, thanks for the support to everyone
DaveCZ said:
The truth is, that Xiaomi temporally suspended all updates due to amount of bugs. Also try restore your phone with Mi Flash and latest firmware version ( Android O) from http://en.miui.com But as I said it is Xiaomi's fault.
Click to expand...
Click to collapse
Ok, i was sure about the latest update but i wasn't thinking something of this scale, can someone with my issue can confirm that now is impossible to receive any ota?
Bored by waiting 2 days ago I got my OTA clearing google framework data and reboot. After that OTA was here.
macelaru said:
Bored by waiting 2 days ago I got my OTA clearing google framework data and reboot. After that OTA was here.
Click to expand...
Click to collapse
Just read the OT please
Lollo Olearo said:
Ok, i was sure about the latest update but i wasn't thinking something of this scale, can someone with my issue can confirm that now is impossible to receive any ota?
Click to expand...
Click to collapse
Kind of... I still didn't got the January update either. I just read some articles about it being resumed again. But I didn't get any update. I can see my IMEI number and flashed Oreo thru MiFlash (cuz I didn't get Oreo OTA) and yet no update whatsoever. Hope I'll get it soon?
DaveCZ said:
Kind of... I still didn't got the January update either. I just read some articles about it being resumed again. But I didn't get any update. I can see my IMEI number and flashed Oreo thru MiFlash (cuz I didn't get Oreo OTA) and yet no update whatsoever. Hope I'll get it soon?
Click to expand...
Click to collapse
It's seems to be pretty similar even if i received oreo through ota.
Funny fact, before uninstalling magisk and all the modules i was downloading the jenuary update, obviously i got an installation error, since than I'm fallen into a word without ota
Lollo Olearo said:
Funny fact, before uninstalling magisk and all the modules i was downloading the jenuary update, obviously i got an installation error, since than I'm fallen into a word without ota
Click to expand...
Click to collapse
Trust me that I feel your pain? Since I was playing around with flashing beta versions of Oreo and hard-bricked my phone twice. After second restoration of the OS no OTAs. So I thought it is because of false OS they put on it. So I flashed official Oreo through MiFlash but nothing yet so far. Meybe you or me can ask Xiaomi what to do or what is happening.
DaveCZ said:
Trust me that I feel your pain? Since I was playing around with flashing beta versions of Oreo and hard-bricked my phone twice. After second restoration of the OS no OTAs. So I thought it is because of false OS they put on it. So I flashed official Oreo through MiFlash but nothing yet so far. Meybe you or me can ask Xiaomi what to do or what is happening.
Click to expand...
Click to collapse
I'm not sure if is a problem of xiaomi or our, still the fact that xiaomi is acting like a ****: from kernel source to buggy update and then this, so far is really bad
Lollo Olearo said:
Just read the OT please
Click to expand...
Click to collapse
Ops! Sorry.
But to be ontopic I have another 2 A1's (yeah, I bought 3 of them) in family and both are on Oreo December update. No OTA for them until now.
Dunno if it helps but that's all I have. Mine forced 2 days ago from Nougat to Oreo 1 jan and my wife's and daughter stuck on Oreo december.
Lollo Olearo said:
I'm not sure if is a problem of xiaomi or our, still the fact that xiaomi is acting like a ****: from kernel source to buggy update and then this, so far is really bad
Click to expand...
Click to collapse
Sure is. It shouldn't be called Android One phone. The phone itself is great but software wise it is horrible. We are still not fully on 8.0 but there's 8.1.1 so Xiaomi should finally do something!
---------- Post added at 03:32 PM ---------- Previous post was at 03:31 PM ----------
macelaru said:
Ops! Sorry.
But to be ontopic I have another 2 A1's (yeah, I bought 3 of them) in family and both are on Oreo December update. No OTA for them until now.
Dunno if it helps but that's all I have. Mine forced 2 days ago from Nougat to Oreo 1 jan and my wife's and daughter stuck on Oreo december.
Click to expand...
Click to collapse
Yes I'm also stuck on 8.0 December. We should slam Xiaomi to co what they are supposed to so with Android One phone!
Today Xiaomi finally unlocked all the ota, i guess issue solved
Lollo Olearo said:
Today Xiaomi finally unlocked all the ota, i guess issue solved
Click to expand...
Click to collapse
Nope still didn't get any
Hello,
I recently noticed that the LG H815 build has been removed as a download because of an encryption issue, and I was wondering if, other than this, there were any other issues causing it to be taken down (I'm thinking of building it unofficially)
Thanks
ThePiGuy said:
Hello,
I recently noticed that the LG H815 build has been removed as a download because of an encryption issue, and I was wondering if, other than this, there were any other issues causing it to be taken down (I'm thinking of building it unofficially)
Thanks
Click to expand...
Click to collapse
Lol another one building LOS unofficially for the g4...
yea do it. Or use the the XDA search
Sent from my LG-H815 using XDA Labs
steadfasterX said:
Lol another one building LOS unofficially for the g4...
yea do it. Or use the the XDA search
Click to expand...
Click to collapse
Ok thanks. Is this the only major bug (I'm new to android development so I probably won't be able to fix many bugs)
ThePiGuy said:
Ok thanks. Is this the only major bug (I'm new to android development so I probably won't be able to fix many bugs)
Click to expand...
Click to collapse
There is an unofficial LOS build already. That's what I meant to say.
Yes encryption is the issue why we do not have official ones but encryption is fixed on aoscp by our genius kessaras. Ask in kobtuls LOS thread what the state in LOS is.
Sent from my LG-H815 using XDA Labs
steadfasterX said:
There is an unofficial LOS build already. That's what I meant to say.
Yes encryption is the issue why we do not have official ones but encryption is fixed on aoscp by our genius kessaras. Ask in kobtuls LOS thread what the state in LOS is.
Click to expand...
Click to collapse
Thanks again. Just out of interest, how would AOSCP compare to LOS (it's one I have only just heard of)
ThePiGuy said:
Thanks again. Just out of interest, how would AOSCP compare to LOS (it's one I have only just heard of)
Click to expand...
Click to collapse
https://forum.xda-developers.com/g4/development/g4-cypheros-t3680102
flash and find out.
raptorddd said:
https://forum.xda-developers.com/g4/development/g4-cypheros-t3680102
flash and find out.
Click to expand...
Click to collapse
I have just noticed it says you need v29a firmware. If I download it from cypheros.co, does it still need v29a (I'm on v20g and would rather keep it so I can roll back to stock using a TWRP backup if I need to)
ThePiGuy said:
I have just noticed it says you need v29a firmware. If I download it from cypheros.co, does it still need v29a (I'm on v20g and would rather keep it so I can roll back to stock using a TWRP backup if I need to)
Click to expand...
Click to collapse
You just need a V29a modem and bootloader package if you have a H815 handset, and you can actually flash that in TWRP as there is a flashable ZIP for that. I went straight from OEM Lollipop to AOSCP Oreo without issues.
aha360 said:
You just need a V29a modem and bootloader package if you have a H815 handset, and you can actually flash that in TWRP as there is a flashable ZIP for that. I went straight from OEM Lollipop to AOSCP Oreo without issues.
Click to expand...
Click to collapse
Thanks. Just out of interest, why is this required (I thought the rom rewrote this anyway)
ThePiGuy said:
Thanks. Just out of interest, why is this required (I thought the rom rewrote this anyway)
Click to expand...
Click to collapse
I assume this is mainly due to performance reasons and compatibility with newer custom firmware, but I do not know the full, technical story as to why that is the case. You're better off asking @kessaras and @steadfasterX for the answers
ThePiGuy said:
I have just noticed it says you need v29a firmware. If I download it from cypheros.co, does it still need v29a (I'm on v20g and would rather keep it so I can roll back to stock using a TWRP backup if I need to)
Click to expand...
Click to collapse
as far as i know if you have h815 that unlocks with .bin key from LG its bootloader its unlockable and it has antirollback 0 unless you have h815t or h815p thats locked bootloader and cant rollback i think
ask in thread and tell them if you have official unlocked boorloadre from LG. if you can roll back if you flash v29.
aha360 said:
I assume this is mainly due to performance reasons and compatibility with newer custom firmware, but I do not know the full, technical story as to why that is the case. You're better off asking @kessaras and @steadfasterX for the answers
Click to expand...
Click to collapse
raptorddd said:
as far as i know if you have h815 that unlocks with .bin key from LG its bootloader its unlockable and it has antirollback 0 unless you have h815t or h815p thats locked bootloader and cant rollback i think
ask in thread and tell them if you have official unlocked boorloadre from LG. if you can roll back if you flash v29.
Click to expand...
Click to collapse
Thanks for the replies. Does Lineage OS also need this or is it only AOSCP
ThePiGuy said:
Thanks for the replies. Does Lineage OS also need this or is it only AOSCP
Click to expand...
Click to collapse
I assume any Nougat or Oreo, or PQRSTUVWXYZ ROM needs the latest available OEM bootloader/modem package, but don't act on this information unless you have asked around and those on this forum give the same answers.
aha360 said:
I assume any Nougat or Oreo, or PQRSTUVWXYZ ROM needs the latest available OEM bootloader/modem package, but don't act on this information unless you have asked around and those on this forum give the same answers.
Click to expand...
Click to collapse
Ok. Just out of interest, if I did flash a ROM that required a different bootloader and modem to the version I have, would it brick my phone or would it just not work properly
ThePiGuy said:
Ok. Just out of interest, if I did flash a ROM that required a different bootloader and modem to the version I have, would it brick my phone or would it just not work properly
Click to expand...
Click to collapse
You CAN use an outdated modem partition. But you may encounter issues like camera crash, bad or no sound on voice calls, gps probs and / or sensor issues.
And depending on several things it's possible that it JUST WORKS FINE. I have tested even a LP modem partition with oreo (just a short test a while ago) and all was working here but issues can happen rarely.
A brick is possible but it will be a soft brick only which means the download mode is still there and you can flash a kdz to recover if needed. It either bootloops or a demigod bluescreen will happen on boot.
Sent from my LG-H815 using XDA Labs
steadfasterX said:
You CAN use an outdated modem partition. But you may encounter issues like camera crash, bad or no sound on voice calls, gps probs and / or sensor issues.
And depending on several things it's possible that it JUST WORKS FINE. I have tested even a LP modem partition with oreo (just a short test a while ago) and all was working here but issues can happen rarely.
A brick is possible but it will be a soft brick only which means the download mode is still there and you can flash a kdz to recover if needed. It either bootloops or a demigod bluescreen will happen on boot.
Click to expand...
Click to collapse
Thanks for confirming this. I want to keep as much of my phone stock as possible so it is easy to revert back to full stock if anything happens (this is my first proper venture into custom ROMs).
Also, is there any way to tell which version the rom requires by looking at the install files
Got the Pie update notice today along with January security patch. My question is for those who, like me, waited until the official notification to update.
With so many here experiencing problems with the previous update(s), it's hard to distinguish which threads are for it, custom, or for the latest Xiaomi update. Did you update to Pie in January? Are there any issues you've noticed with the update? Should I pull the trigger on the update or wait?
Any info is appreciated, as always.
Regards,
KB
I just directly installed January update, migrated from Oreo. Didn't face any issues as of yet.
By the way how do you guys turn on FM Radio?
No data since update.
I did the update earlier today and haven't been able to get mobile data since. Can anybody help me?
Barneyjp18 said:
I did the update earlier today and haven't been able to get mobile data since. Can anybody help me?
Click to expand...
Click to collapse
I downloaded my update with the mobile data and used it since right after. No problem. Wifi seems ok too.
Barneyjp18 said:
I did the update earlier today and haven't been able to get mobile data since. Can anybody help me?
Click to expand...
Click to collapse
That sounds like a serious issue, and one that makes me think I might just wait a bit on this update. Thanks for the feedback, and I hope you get the issue resolved. Where are you located?
KB_Thailand said:
That sounds like a serious issue, and one that makes me think I might just wait a bit on this update. Thanks for the feedback, and I hope you get the issue resolved. Where are you located?
Click to expand...
Click to collapse
I'm am located in Japan. Did the update while connected to wifi on WiFi. I never even questioned it as never had a problem in the 14months I have owned the phone.
Barneyjp18 said:
I'm am located in Japan. Did the update while connected to wifi on WiFi. I never even questioned it as never had a problem in the 14months I have owned the phone.
Click to expand...
Click to collapse
I understand. I've not experienced many of the issues some have with the updates, though the battery issues a few updates ago were driving me crazy. Those seem to be resolved now and I can easily get 2 to 3 days out of a charge. The only reason I hesitated was I read some of the threads from the initial update Xiaomi put out, and was trying to be sure this one was less troublesome before allowing it. I saw a couple of folks complain about the loss of WiFi and Data on the first update, so perhaps all of the initial bugs haven't been squashed. I'm in Thailand, so need it to be as clean as possible.
Again, hope you get the issue resolved. Let us know if you do.
I am from Czech Republic and I can say I don't have any LTE issues, battery is great. No issues with Pie at all.
@KB_Thailand
If you are a big fan of gcam.. Then dont update, else do it.
For me everything is working fine, except gcam focus issue.
Stock camera works though.
ShaikhSiddiky said:
I just directly installed January update, migrated from Oreo. Didn't face any issues as of yet.
By the way how do you guys turn on FM Radio?
Click to expand...
Click to collapse
You need to connect a wired headphone in the 3.5 mm jack, then you will get FM.
Regards
Eshwar123 said:
@KB_Thailand
If you are a big fan of gcam.. Then dont update, else do it.
For me everything is working fine, except gcam focus issue.
Stock camera works though.
Click to expand...
Click to collapse
It's not working even flashing the magisk patch module?
ccalixtro said:
It's not working even flashing the magisk patch module?
Click to expand...
Click to collapse
I don't know about this, coz I'm a non rooted user.
If it works, please share,
Eshwar123 said:
I don't know about this, coz I'm a non rooted user.
If it works, please share,
Click to expand...
Click to collapse
Well it works for me. Just unlock the bootloader, put the phone in fastboot mode, boot twrp cosmicdans from adb, flash magisk and when it boots open magisk and download camera patch for pie. It's really easy but i think when you unlock the bootloader you lose your data so think about it.
KB_Thailand said:
Got the Pie update notice today along with January security patch. My question is for those who, like me, waited until the official notification to update.
Click to expand...
Click to collapse
If you are stock 100% do it, if not hang out a while, no big issues now for stock, very few people on stock have had an issue with the latest Pie, those that do have very simple easily fixed things.
Barneyjp18 said:
I did the update earlier today and haven't been able to get mobile data since. Can anybody help me?
Click to expand...
Click to collapse
Try the last page here, changing the IPv4/IPv6 setting, it fixed it for others who had a problem.
https://forum.xda-developers.com/mi-a1/help
I have also lost my data connection since the update.
Does anyone have any idea on how to fix this problem?
EDIT : It seems that the update deleted the apn configuration. Re-entering it solved the issue.
Based on the positive responses I went ahead and did the update since my A1 is stock. So far so good with no issues I've noticed. Both data and wifi seem to be working properly.
Thanks for the responses!
After updating to pie many of the users including myself face an issue where the mic volume has reduced a lot. Other people can't hear me properly on normal voice calls
ccalixtro said:
Well it works for me. Just unlock the bootloader, put the phone in fastboot mode, boot twrp cosmicdans from adb, flash magisk and when it boots open magisk and download camera patch for pie. It's really easy but i think when you unlock the bootloader you lose your data so think about it.
Click to expand...
Click to collapse
Thank you for confirming that,
After rooting, and installing the magisk patch, can I completely unroot and lock the bootloader, and will the patch still work?
Will unlocking the bootloader also wipe data?
(i thought only locking bootloader will wipe, we can use the vol button trick)
Thanks in advance.
Eshwar123 said:
Thank you for confirming that,
After rooting, and installing the magisk patch, can I completely unroot and lock the bootloader, and will the patch still work?
Will unlocking the bootloader also wipe data?
(i thought only locking bootloader will wipe, we can use the vol button trick)
Thanks in advance.
Click to expand...
Click to collapse
1. Unlocking bootloader wipes data
2. Does your phone contain nuclear weapon key? If no, then i don't see any reason you dont want a unlocked bootloader. (Manufacturer denying warranty for unlocked bootloader is thing of past, MI has no problem with it. Also you can lock phone just before giving it to MI store in any case)
3. As long as you install apps from playstore, i also dont see any problem with a rooted phone either.
.:Addicted:. said:
1. Unlocking bootloader wipes data
2. Does your phone contain nuclear weapon key? If no, then i don't see any reason you dont want a unlocked bootloader. (Manufacturer denying warranty for unlocked bootloader is thing of past, MI has no problem with it. Also you can lock phone just before giving it to MI store in any case)
3. As long as you install apps from playstore, i also dont see any problem with a rooted phone either.
Click to expand...
Click to collapse
I just want to stay stock and receive official updates and with gcam working as like on oreo. That's it Bro.,
That's why i wanted to unroot and keep the BL locked.
Will the vol down key avoid wipe for unlocking BL as well?
And will the patch work after unroot?
Thanks
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