I posted this in the Q&A thread but it looks pretty dead, I can delete that if needed but hoping to get some help on this one.
I had an Android 10 update this morning, and ever since the person on the other end cannot hear me at all. No way to fix, reset etc.
I don't think I can roll back right? My only solution might be to unlock BL and flash custom, because I cannot wait for a patch to fix this.
Anyone have this same issues? Is there an alternative to going custom? If I do go custom what is the closest to stock that actually fixes this?
This sounds like the problem I have been having since December with still no permanent fix. A temporary fix is to turn on the loudspeaker and then back off and the other caller can hear you. Seems the bug will never get fixed after waiting 3 months now for a fix now.
I decided to use a custom Rom (Ion OS is what I'm using, but any AOSP Rom will do), which fixes the issue altogether. Or you could downgrade back to MIUI 10, which I can confirm it also fixes the call audio issue. So, yes you'll need to unlock the bootloader. I tried other MIUI Roms like Mi-globe, Xiaomi.EU, and ROS-MIUI, and all give the same issue. Well, the ones that's base on android 10 give the call audio issue, the ones based on android 9 don't.
Ok I fixed this yesterday on my own, here's what I did:
1) Back everything up that i needed, then unlocked the BL.
2) booted into TWRP, then flashed TWRP, then flashed the disable verity zip
3) Tried a few ROMs, all had the same issue, and other issues
4) Finally downloaded a ROM I "built" from mi-global, https://mi-globe.com/miui-firmware-rom-builder/
5) Once the ROM was built (I included Magisk, removed some bloatware etc), I flashed it, I intentionally used about a month old build since the the current stock one is what borked me. Mic problem still evident.
6) So finally I removed the modem.img file from the ROM zip and went into fastboot and manually flashed the modem image, rebooted, and that fixed it.
No matter what you have to be BL unlocked to flash files in fastboot, but I think just flashing the older modem.img would have fixed it, but I am better for it because now i have a stock android 10 ROM with bloat removed, and root permissions.
orangekid said:
Ok I fixed this yesterday on my own, here's what I did:
1) Back everything up that i needed, then unlocked the BL.
2) booted into TWRP, then flashed TWRP, then flashed the disable verity zip
3) Tried a few ROMs, all had the same issue, and other issues
4) Finally downloaded a ROM I "built" from mi-global, https://mi-globe.com/miui-firmware-rom-builder/
5) Once the ROM was built (I included Magisk, removed some bloatware etc), I flashed it, I intentionally used about a month old build since the the current stock one is what borked me. Mic problem still evident.
6) So finally I removed the modem.img file from the ROM zip and went into fastboot and manually flashed the modem image, rebooted, and that fixed it.
No matter what you have to be BL unlocked to flash files in fastboot, but I think just flashing the older modem.img would have fixed it, but I am better for it because now i have a stock android 10 ROM with bloat removed, and root permissions.
Click to expand...
Click to collapse
I might have to give that a try then. Glad you have yours working, hope that's the problem I'm having too with the modem.img.
Edit: Tried your steps, but what I get is complete silence now on both ends of a call. Used a modem from the 11.0.6.0.PEAMIXM (android 9) stable build.
Tried V11.0.3.0.QEAMIXM (android 10) firmware and it just brings back the buzzing/static muffled sounds. Shame I can't find why I can't use MIUI 11 without getting this issue.
orangekid said:
Ok I fixed this yesterday on my own, here's what I did:
1) Back everything up that i needed, then unlocked the BL.
2) booted into TWRP, then flashed TWRP, then flashed the disable verity zip
3) Tried a few ROMs, all had the same issue, and other issues
4) Finally downloaded a ROM I "built" from mi-global, https://mi-globe.com/miui-firmware-rom-builder/
5) Once the ROM was built (I included Magisk, removed some bloatware etc), I flashed it, I intentionally used about a month old build since the the current stock one is what borked me. Mic problem still evident.
6) So finally I removed the modem.img file from the ROM zip and went into fastboot and manually flashed the modem image, rebooted, and that fixed it.
No matter what you have to be BL unlocked to flash files in fastboot, but I think just flashing the older modem.img would have fixed it, but I am better for it because now i have a stock android 10 ROM with bloat removed, and root permissions.
Click to expand...
Click to collapse
Hello orangekid, am on the same situation as you was. The 2 mic Works flawlessly when i rec a vidéo or audio memo but when its on call other hear me with buzing and muffling sound.
I am on custom rom Android 11 (EvolutionX 5.3).
Can u plese give me a link to the modem that you flashed in order to ride off this issue.
Thanks in advence
Sld_Ultra said:
I might have to give that a try then. Glad you have yours working, hope that's the problem I'm having too with the modem.img.
Edit: Tried your steps, but what I get is complete silence now on both ends of a call. Used a modem from the 11.0.6.0.PEAMIXM (android 9) stable build.
Tried V11.0.3.0.QEAMIXM (android 10) firmware and it just brings back the buzzing/static muffled sounds. Shame I can't find why I can't use MIUI 11 without getting this issue.
Click to expand...
Click to collapse
Hello sld ultra, did u find a solution for the mic problem since ? Its really annoying.
Sindalf said:
Hello sld ultra, did u find a solution for the mic problem since ? Its really annoying.
Click to expand...
Click to collapse
The problem went away after updating to a MIUI 11 build a month later, can't remember which one. Ever since then, the mic problem hasn't come back and had no problems with MIUI 12.
I'm now using Evolution X 5.3 since the Mi 8 stop getting MIUI updates. Now the only time the mic problem comes back is is when I flash ZenX OS ROM, none of there builds work for me. I don't know why, I just decided that my phone hates what ever setting or config that's in the ROM. From the maintainer's view, I missed up something on my phone, yet other custom and MIUI ROMs work fine.
Back to your question, I didn't find a solution to the problem, it just went away after an update. Now ZenX OS is the only ROM that brings back the problem. Plan to try their A11 build when it comes out, if the problem is still there I'll just move back to Evolution X. Are you using the latest MIUI 12 build? Global stable or xiaomi.eu beta?
Thanks for
Sld_Ultra said:
The problem went away after updating to a MIUI 11 build a month later, can't remember which one. Ever since then, the mic problem hasn't come back and had no problems with MIUI 12.
I'm now using Evolution X 5.3 since the Mi 8 stop getting MIUI updates. Now the only time the mic problem comes back is is when I flash ZenX OS ROM, none of there builds work for me. I don't know why, I just decided that my phone hates what ever setting or config that's in the ROM. From the maintainer's view, I missed up something on my phone, yet other custom and MIUI ROMs work fine.
Back to your question, I didn't find a solution to the problem, it just went away after an update. Now ZenX OS is the only ROM that brings back the problem. Plan to try their A11 build when it comes out, if the problem is still there I'll just move back to Evolution X. Are you using the latest MIUI 12 build? Global stable or xiaomi.eu beta?
Click to expand...
Click to collapse
Thanks for the reply, i was with official MIUI 12 globale version , now i am using évolution x 5.3, i have also replaced my screen and only some twrp Works.. the issue it not related to hardware because when i rec a vidéo or audio memo its Works normally, but when calling the sound is muffled and buzing.. i will try to get back to an android 9 rom ? I will try and will see
Related
Hi
I have installed many of the Android 7.0 ROMS for Shamu and all of them have this annoying problem:
When I dial out I cannot hear the ring or the other person.
When I receive a call I don't often hear the other person but they may hear me.
Yes I've installed the N6 boot loader and radio and do not load any other mods, custom kernels.
I just can't figure this out. Any ideas? Is there a Android 7.0 firmware that I need to install to prepare my Shamu for Android 7?
Thanks
Aussie
I had this same problem, I had to re flash stock 7.0 and the problem was gone. No idea what caused it
Flashing Stock 7.0
aroy97 said:
I had this same problem, I had to re flash stock 7.0 and the problem was gone. No idea what caused it
Click to expand...
Click to collapse
Did flashing stock 7.0 re-lock bootloader? Were you able to unlock the phone?
Thanks
Aussie
aussie1234 said:
Did flashing stock 7.0 re-lock bootloader? Were you able to unlock the phone?
Thanks
Aussie
Click to expand...
Click to collapse
Flashing stock does not relock the bootloader.
Didn't work
Ok I flashed stock 7.0 using Wugfresh's tool.
But still when I use the phone I can't hear who is on the other end.
Really odd!
Anyone have any suggestions?
Thanks
Aussie
I'm having the same issue on a stock Nougat phone as well. The problem appeared a few days ago out of the blue. The only band aid fix I've found is the sound about app and force assigned the mic and earpiece functions.
Sadly, this doesn't address the main issue in the first place.
none
Why are you using Wugfresh? Plug the phone in the computer and when it communicates with the phone tap the menu bar that says it's charging, when you open that tick allow files/folders, the second option. Then put your files on the root of internal storage, wipe the entire system then flash your rom, you don't need Wugfresh.
If you lose your data who cares, just set the phone up again and you should be good to go, this is much more dependable as I use to use Wugfresh, you do know how to get into recovery and install that way? You will want to do a full wipe, then flash
---------- Post added at 07:53 AM ---------- Previous post was at 07:50 AM ----------
USMC retired said:
Why are you using Wugfresh? Plug the phone in the computer and when it communicates with the phone tap the menu bar that says it's charging, when you open that tick allow files/folders, the second option. Then put your files on the root of internal storage, wipe the entire system then flash your rom, you don't need Wugfresh.
If you lose your data who cares, just set the phone up again and you should be good to go, this is much more dependable as I use to use Wugfresh, you do know how to get into recovery and install that way? You will want to do a full wipe, then flash
Click to expand...
Click to collapse
If you need anything else you can PM me
I didn't realize there was a thread on this already.
I'm using Pure Nexus and the other end would go silent for about 5 seconds and then come back...so that's a bit different than what you guys are experiencing.
stevew84 said:
I didn't realize there was a thread on this already.
I'm using Pure Nexus and the other end would go silent for about 5 seconds and then come back...so that's a bit different than what you guys are experiencing.
Click to expand...
Click to collapse
have you tried reflashing your radio? Maybe try flashing a MM radio as well
Just wanted to chime in, I think this is actually more of a VoLTE/HD issue. It happens to my N6 that's still on MM. Sometimes the dialtone/ring is there, other times it's not. Would love to know of there's a fix!
Found a fix..
Hello all.
I found a fix to Shamu+Nougat ROM problem when I am called I do not hear the other person and vice versa.
To install Factory Nougat from Google: https://developers.google.com/android/nexus/images
FIRST backup your phone (contacts, files, pics, movies etc) as this will totally erase EVERYTHING!
When you are on the Factory Images for Nexus Devices page click "backed up to your Google Account" then go click 'back' on your browser and click on 'Acknowledge' to see the list of Factory Nougat ROMS for Shamu come up on the right.
Download the Android 7.0 Factory ROM for Shamu/Nexus 6.
Do not flash this stock ROM using Wugfresh's tool. Instead follow precisely the 'Flashing Instructions' on the page https://developers.google.com/android/nexus/images. Allow the phone to reboot and fully set up. Restart the phone again.
Then use Wugfresh to Root the phone and also to install custom recovery (I already have unlocked bootloader).
Now, nothing against Wugfresh Tool (I do not know why the flashing method above works better) as Wugfresh has saved my phone many times.. Its just that Googles recommended flashing instructions worked best.
Now I use the phone and not only do I hear the caller and they hear me I have much better reception (Australia). Yes I did previously flash latest radio but the above method seemed to improve my Shamu 100%.
What I have not done yet is flash a custom ROM in case the problem re-appears. But my phone is rooted and unlocked so I can install other mods that work with Nougat.
Hope this works for you.
Cheers
Aussie
Another Fix Part 2
Hi
I stumbled on another method that has seemed to work:
Ensure you have unlocked bootloader.
Flash Tupacs Android 6.0 MOB31H ROM from http://forum.xda-developers.com/nexus-6/development/rom-rooted-deoxeded-fast-stable-t3252922
(*Note I used his MOB31E Android 6.0 ROM so I am presuming current MOB31H will work).
Credit to this ROM goes to tupac4u as I am not a Developer.
I then flashed SuperUser but did not flash a custom kernel.
Setup the ROM as usual.
Selected Settings - About Phone - System updates and let the phone install the Android 7 OTA update. Be aware its a 878Mb download.
Let the update download and fully install. I had TWRP recovery and the update still installed fine.
After installation fully completed I enabled Developer Options and USB Debugging.
Then using WugFresh's excellent tool http://forum.xda-developers.com/nexus-6/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2947452 I applied Root and Custom Recovery.
I also flashed Radio 5.39R which I found works best.
Now my phone works very well and (for now) now I can hear the caller and they can hear me.
Cheers
Aussie
aussie1234 said:
Hi
I stumbled on another method that has seemed to work:
Ensure you have unlocked bootloader.
Flash Tupacs Android 6.0 MOB31H ROM from http://forum.xda-developers.com/nexus-6/development/rom-rooted-deoxeded-fast-stable-t3252922
(*Note I used his MOB31E Android 6.0 ROM so I am presuming current MOB31H will work).
Credit to this ROM goes to tupac4u as I am not a Developer.
I then flashed SuperUser but did not flash a custom kernel.
Setup the ROM as usual.
Selected Settings - About Phone - System updates and let the phone install the Android 7 OTA update. Be aware its a 878Mb download.
Let the update download and fully install. I had TWRP recovery and the update still installed fine.
After installation fully completed I enabled Developer Options and USB Debugging.
Then using WugFresh's excellent tool http://forum.xda-developers.com/nexus-6/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2947452 I applied Root and Custom Recovery.
I also flashed Radio 5.39R which I found works best.
Now my phone works very well and (for now) now I can hear the caller and they can hear me.
Cheers
Aussie
Click to expand...
Click to collapse
Has there been a listed fix for people who haven't rooted their nexus?
Hi all,
I am having issues with my Bluetooth and GSM. I am considering trying to downgrade from OOS 4.1.3 to 4.1.1. I am completely stock, not rooted and don't even have TWRP.
Would appreciate some clarification to the following questions:
1) Can I downgrade by just flashing the official full 4.1.1 zip found in OP website?
2) Should I only flash the modem zip? And if so, can I use 4.1.1 modem while having 4.1.3 installed?
3) Since 4.1.1 already has nougat 7.1.1, is 1) also safe for further downgrades, for example, directly to 4.0.4?
Thanks.
Best regards,
Oldiamond
If your bootloader is locked, you can't downgrade (unless you exploit the security vulnerability from a few weeks back).
If your bootloader is unlocked, use TWRP or fastboot to clean flash whatever version of OOS you want.
You should consider flashing the latest open beta release, I think it's already fixed over there plus there are some Extra goodies and its stable as ****
Anova's Origin said:
If your bootloader is locked, you can't downgrade (unless you exploit the security vulnerability from a few weeks back).
If your bootloader is unlocked, use TWRP or fastboot to clean flash whatever version of OOS you want.
Click to expand...
Click to collapse
Pharrax said:
You should consider flashing the latest open beta release, I think it's already fixed over there plus there are some Extra goodies and its stable as ****
Click to expand...
Click to collapse
Thanks to both. I am this close to send it back to RMA, as I did not install anything other than 4.1.3, and didn't even unroot it. I don't know... perhaps by sending it back without ever installing TWRP or unlocking anything would provide more feedback to the manufacturer, other than saying "damn guy, started fiddling with the phone and ROMs, and here's the result".
Regarding the beta, I initially considered avoiding it because i read in the forums about issues such as sometimes alarms not ringing. I figure that my boss wouldn't like that
Going back from BETA to regular version also requires TWRP?
Best regards,
Old
oldiamond said:
Thanks to both. I am this close to send it back to RMA, as I did not install anything other than 4.1.3, and didn't even unroot it. I don't know... perhaps by sending it back without ever installing TWRP or unlocking anything would provide more feedback to the manufacturer, other than saying "damn guy, started fiddling with the phone and ROMs, and here's the result".
Regarding the beta, I initially considered avoiding it because i read in the forums about issues such as sometimes alarms not ringing. I figure that my boss wouldn't like that
Going back from BETA to regular version also requires TWRP?
Best regards,
Old
Click to expand...
Click to collapse
Alarm issues were fixed, also it never happened to me I and I've been on beta a long time i think on the official page there are the steps to switch between stable and beta. I don't think it requires twrp but don't take my word for it.
XZ/KAGURA/F8331 OmniROM BUILDS
PIE 9.0
DOWNLOAD WEEKLY
REQUIREMENTS TO SUCCESSFULLY FLASH OMNIROM:
1. The device has the latest stock ftf
2. The device has an unlocked bootloader
3. The ODM image zip (version 9) has been downloaded from HERE, and the ODM image has been extracted from it
4. The WEEKLY zip file has been downloaded and copied to the device
INSTALLATION INSTRUCTIONS:
1. Reboot device to fastboot mode, and flash the ODM image with this command
Code:
fastboot flash oem <ODM image>
2. Reboot device to TWRP and flash the WEEKLY zip file
3. (If coming from an 8.1 ROM) Fix /dsp SELinux labels with the dsp-label-fixer.zip
4. (Optional) Flash a gapps package
5. Reboot device to system
CURRENT ISSUES ON OFFICIAL:
1. Device wakes up by itself every 5 seconds, reason unknown
2. Camera quality is suboptimal
KERNEL SOURCE: https://github.com/omnirom/android_kernel_sony_msm/tree/android-9.0
BUG REPORTS
REPORT BUGS ONLY:
- AFTER A CLEAN INSTALL
- USING STOCK OMNI KERNEL
- NO MODS OF ANY SORT
OMNI GERRIT REVIEW
https://gerrit.omnirom.org/
DISCLAIMER:
No one is responsible for any damage done to your device but YOU. You've been warned.
XDA:DevDB Information
[ROM][XZ][P][9.0][WEEKLY]OmniROM, ROM for the Sony Xperia XZ
Contributors
oshmoun, humberos, local__hero
Source Code: https://github.com/omnirom
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: latest stock ftf
Version Information
Status: Beta
Created 2019-03-17
Last Updated 2019-05-31
Thank you for the separate this from the other pie roms.
I will flash it after I arrive home.
Thank you all for the hard work!
Sent from my kagura using XDA Labs
I'm loving the fact Omnipie is official. I will be flashing this right now. Thank you so much.
Finally flashed! been using it for less than an hour, i can say that its definitely good for daily use. Camera seems better and hasnt crashed yet (like it use to), mic actually picks up audio properly, brightness slider is finally proportional to the brightness level, and its pie
however, the stereo speaker seems to muffle at high volumes (especially with the ringtones and less with youtube, but still a little prevelent), app opening times seem a little longer than 8.1, and 120HZ still doesnt work
im also curious why the linked odm isnt the latest one (im pretty sure the latest is 1st march not feb)
anyways, thanks dev! (may be editing this thread after more use for battery etc)
XxperexX said:
however, the stereo speaker seems to muffle at high volumes (especially with the ringtones and less with youtube, but still a little prevelent)
Click to expand...
Click to collapse
Could it be this kernel bug: https://github.com/sonyxperiadev/bug_tracker/issues/336 ? Looks like the sonyxperiadev team is working on it.
XxperexX said:
im also curious why the linked odm isnt the latest one (im pretty sure the latest is 1st march not feb)
Click to expand...
Click to collapse
The March 1 release says "Android 8.1", the linked one looks like the latest for Pie.
sinivalas23 said:
Could it be this kernel bug: https://github.com/sonyxperiadev/bug_tracker/issues/336 ? Looks like the sonyxperiadev team is working on it.
The March 1 release says "Android 8.1", the linked one looks like the latest for Pie.
Click to expand...
Click to collapse
Ah, your correct it does say 8.1 my bad
opps
I saw this version from delta updater (using 8.1 omni) and immediately downloaded flashed oem for pie and downloaded omni 9 but it stucked new omni animated logo. Waited like 10 minutes but nothing happened then rebooted phone but same thing happened. Should i wait more or something went wrong?
Im here with OmniROM freshly flashed trough Open Delta.
I have some problems. First boot never ends, BUT restart worked for me but I have another problem.
Now I need 10 min to unlock the phone when Im lucky.
I unlock with the code and then its instantly relock and it say I cant use fingerprint for first unlock, so I use code again and not work again and still can't use fingerprint.
I do this A LOT OF TIME before I can use my phone. Sometimes it helps sometimes not if I not unlock my phone but use corner dial icon first and then if its ask for code i use it and then I got SystemUI crash error again and again and again.
As I said I try to repeat this methods for like 10 min after every restart. I tried to delete some maybe not compatible apps with this new update but still nothing. Now I will remove some Magisk modules. I will write again.
KikiGames said:
Im here with OmniROM freshly flashed trough Open Delta.
I have some problems. First boot never ends, BUT restart worked for me but I have another problem.
Now I need 10 min to unlock the phone when Im lucky.
I unlock with the code and then its instantly relock and it say I cant use fingerprint for first unlock, so I use code again and not work again and still can't use fingerprint.
I do this A LOT OF TIME before I can use my phone. Sometimes it helps sometimes not if I not unlock my phone but use corner dial icon first and then if its ask for code i use it and then I got SystemUI crash error again and again and again.
As I said I try to repeat this methods for like 10 min after every restart. I tried to delete some maybe not compatible apps with this new update but still nothing. Now I will remove some Magisk modules. I will write again.
Click to expand...
Click to collapse
you need to do a full wipe before upgrading to p
Just as @oshmoun said; before flashing new ROMs, it's imperative to do full wipe (if you don't want to lose all your data, then do a full backup in TWRP), as flashing without full wiping can cause TONS of problems. Don't be lazy and follow the instructions properly.
oshmoun said:
you need to do a full wipe before upgrading to p
Click to expand...
Click to collapse
I used the same rom before but the last update. I updated through OpenDelta.
Hello !
It's cool to see our XZ is alive !
I have some problems with this rom after a full wipe and update to oem V6 :
- no sounds during calls, no mic, no earphone, no sounds on speaker
- Magisk 18.1 not working
- With official camera app, while using the flash, only the autofocus led is lit, the second and much powerful led is never triggered resulting on dark shots
For now that's all
Thx
Performance is somewhat distressed and the camera does not work for the sound is not working after restarting the device is improving
KikiGames said:
I used the same rom before but the last update. I updated through OpenDelta.
Click to expand...
Click to collapse
you cant do that. its pretty misleading having it available on that opendelta ota thingy. you have to follow the instructions in this thread
Flashed data, cache and dalvik, factory reset. And installed latest nightly with gapps and magisk 18.1.
Only reason I did it this way is because I was on a unofficial build on Omni. Everything is working as it should. Very snappy and no lag. Still have to see how the ROM handles after it's settled for a couple day, but right off the bat it's amazing. Thank you very much Dev, and happy to see you back on XDA.
XxperexX said:
you cant do that. its pretty misleading having it available on that opendelta ota thingy. you have to follow the instructions in this thread
Click to expand...
Click to collapse
Why this ROM showed up as an update then?
I just don't understand it.
Nevermind this is my main and only phone and I work 4 days straight before I can use my PC so I need to use this ROM buggy for me. :/
KikiGames said:
Why this ROM showed up as an update then?
I just don't understand it.
Nevermind this is my main and only phone and I work 4 days straight before I can use my PC so I need to use this ROM buggy for me. :/
Click to expand...
Click to collapse
You need a PC to flash this. Follow all steps in order and it'll work. Always remember, unless you have a messaging app that backups texts, you will lose them flashing a cfw. Always always backup anything you don't want to lose.
---------- Post added at 12:56 AM ---------- Previous post was at 12:28 AM ----------
I've had a reoccurring issue on the unofficial and official builds so far. I do not have the option to use my phone when calling unless speaker phone or a Bluetooth headset. I cannot put the phone to my head and use normally. Is there any kind of option to fix this nuisance. Any feedback is truly appreciated
Every 9.0 ROM I ever flash, I always seem to have the same problem. Whether its dirty flashing, or starting with flashtool, to CMD, and then to TWRP, the same problem seems to happen. After the ROM has settled, audio quality through calls becomes a huge problem. I'm not sure if I'm doing something wrong, but it has been a persistent bug, next chance I get for the next nightly ill send a logcat, kinda cant not since back on stock. I need good call quality for work lol. Either way, thank you for bringing OMNI to 9.0 official
anyone having problems with video playback? videos dont play on instagram, youtube or snapchat. using magisk 18.1 and latest omni 9 rom
edit: nvm, found out that the Google camera fix module for magisk was the problem
So about 3 weeks ago my 2 year old 3T just stopped working out of nowhere. I debated on whether to upgrade for over a week, but eventually decided to replace it with the same, just to have the familiar ROM, & not to have to learn anything new or mess with anything else, since I'm going through a lot of personal stuff right now. Anyway, I got the phone over a week ago and I've tried everything since then to get it running something beside OOS to no avail. Every single time it goes to sleep in another ROM, once I wake it up, touch is no longer responsive. I can't for the life of me figure out why. I have tried so many different things, in so many different ways. I know it might sound ridiculous but at this point I'm just in tears... I really need a functional phone, and I never would have bought another OP3T if I knew I'd be stuck with OOS....
The process I went through as soon as I got it:
Unfortunately I don't remember the version of OOS that it came with
- Unlock bootloader
- Flash TWRP (twrp-3.0.4-1 due to a thread I came across and was confused by)
- Wipe everything
- Flash recommended firmware for my ROM (posted in the ROM's thread)
- Flash my favorite ROM (Unofficial RR)
- Flash Magisk
- Boot, everything seems fine, screen goes off, turn it back on, unable to use touchscreen anymore.
I then used the unbrick tool, and tried again. Same problem. Used unbrick tool, unlocked bootloader, this time tried to flash this unofficial Lineage . Booted. It went to sleep. Woke up. Touchscreen nonfunctional.
I shut it down. Unbrick tool. This time I let it update itself all the way up to the very latest version of OOS. I go through the entire process again, this time flashing TWRP 3.2.1.0, it's the same thing. I've tried going up to open beta and then flashing my roms. I've tried flashing the rom without firmware, without magisk. With gapps. Without gapps. I always format and wipe everything. I also tried this on the off chance it might work.... I have seriously done the process every way imaginable, over twenty times since I got the phone last week.... nothing ever works. I also just tried Cyanogenmod, but it wouldn't flash at all.
I don't know what to do anymore. I just want to have a phone that I don't hate. At this point, I am too tired and I've got too much going on to figure this out on my own anymore. I would be grateful to pay someone at this point just to help me get this working honestly.... so if there's anyone out there who knows how to fix this, please let me know
Did you buy a new unit from somewhere or did you get a second hand unit ? In the latter case, the person who owned the device before you might have replaced the display for whatever reason, replaced displays often run into these kind of issues.
Also, does this happen on all the ROMs ? It seems you're only flashing Nougat roms, It could be that the hardware is not falling in line with the older software (just a guess). Try flashing a newer, latest updated pie rom and see how that works out.
Mizart said:
It seems you're only flashing Nougat roms, It could be that the hardware is not falling in line with the older software (just a guess).
Click to expand...
Click to collapse
What does that even mean? Sounds like you are just making stuff up.
---------- Post added at 12:23 PM ---------- Previous post was at 12:19 PM ----------
SpaceOctopus said:
I shut it down. Unbrick tool. This time I let it update itself all the way up to the very latest version of OOS.
Click to expand...
Click to collapse
At any point, did you flash a full OOS zip (over 1 GB) and not just update patches? That is where I would start, to make sure it's one a completely stock baseline (including firmware, etc.).
You can get the latest full update zip from here: https://forum.xda-developers.com/oneplus-3t/how-to/official-oxygenos-5-0-1-android-8-0-t3728119
@SpaceOctopus
I would try a newer firmware like the
Stable5.0.8 Firmware+Modem_OnePlus3T.zip
I would also recommend the latest TWRP = twrp-3.3.0-1-oneplus3.img
if still not working definitely flash the flash a full OOS zip from the post above which is 5.0.8
else you should try making the jump to a 9.0 PIE ROM, I see an official and unofficial RR if that is your goto ROM, easy to locate in the [INDEX] ROMs, Kernels & Misc. for 3/3T thread
.
Mizart said:
Did you buy a new unit from somewhere or did you get a second hand unit ? In the latter case, the person who owned the device before you might have replaced the display for whatever reason, replaced displays often run into these kind of issues.
Also, does this happen on all the ROMs ? It seems you're only flashing Nougat roms, It could be that the hardware is not falling in line with the older software (just a guess). Try flashing a newer, latest updated pie rom and see how that works out.
Click to expand...
Click to collapse
Brand new from ebay. Sealed in the box.
I did try flashing a more recent version of resurrection remix, but it failed. Any recommendations?
redpoint73 said:
What does that even mean? Sounds like you are just making stuff up.
---------- Post added at 12:23 PM ---------- Previous post was at 12:19 PM ----------
At any point, did you flash a full OOS zip (over 1 GB) and not just update patches? That is where I would start, to make sure it's one a completely stock baseline (including firmware, etc.).
You can get the latest full update zip from here: https://forum.xda-developers.com/oneplus-3t/how-to/official-oxygenos-5-0-1-android-8-0-t3728119
Click to expand...
Click to collapse
I mean, does using the unbrick tool count? I think it completely flashes everything back to stock. Granted it's a very old version of OOS, but either way I will try that next just in case. Thank you.
hhp_211 said:
@SpaceOctopus
I would try a newer firmware like the
Stable5.0.8 Firmware+Modem_OnePlus3T.zip
I would also recommend the latest TWRP = twrp-3.3.0-1-oneplus3.img
if still not working definitely flash the flash a full OOS zip from the post above which is 5.0.8
else you should try making the jump to a 9.0 PIE ROM, I see an official and unofficial RR if that is your goto ROM, easy to locate in the [INDEX] ROMs, Kernels & Misc. for 3/3T thread
.
Click to expand...
Click to collapse
I did try that TWRP eventually. No change. I would probably have switched to pie a while ago, except one small thing. There's an xposed module I'm really attached to, and as far as I'm aware, xposed isn't available on pie? Or at least that's what I've heard/read. It's the xprivacy lua module that lets you control every type of data an app has access to. I think I've tried looking for an alternative and there aren't any, either. :'( You know, sometimes it's just that one small thing... lol
However, I did try to install the most recent version of RR yesterday, and it failed flashing. Don't know why. I'm going to try again after flashing the firmware. Maybe it'll work this time.
Anyway, I'm also going to try what you all have recommended and see what happens. Hopefully something happens. Thank you much for your help
Ok, well, this time it let me install Resurrection Remix latest version. It may not be exactly what I wanted, but it's pretty goddamn close, and it sure as hell isn't OOS! lol
Thanks for your help everyone! I really appreciate it. I do still really wish I knew wtf was happening honestly with it not properly running nougat ROM's, but hey, this works for me. It won't make me want to toss it in a dumpster and set it on fire every time I pick it up. :laugh: :laugh: :laugh:
Maybe I can get someone to figure it out in the future or something, I don't know. I sure wish someone would convert that xprivacy module to work with Magisk though! I'm surprised nobody has even made an alternative or an app or anything like it really.
SpaceOctopus said:
I mean, does using the unbrick tool count? I think it completely flashes everything back to stock. Granted it's a very old version of OOS, but either way I will try that next just in case.
Click to expand...
Click to collapse
I think the unbrick tool does flash the full OOS. But honestly not 100% sure, as I have never actually had to use the unbrick tool (knock on wood!). Which is one reason I decided to pose that as a question.
In any case, if the unbrick did flash an old OOS, best to replace with newer version (or at least the firmware). Updated firmware typically plays better with the current custom ROMs. And old firmware is often a culprit when random bugs occur after flashing a custom ROM. So again, flashing firmware and/or the full update zip (which also flashes the firmware) is best practice in such cases. And if you are in any doubt about the OOS version or corresponding firmware that was installed, it probably doesn't hurt to flash again.
Hi all.
I've just bought this device. When I first launched it, it was on miui9, i updated to miui 10 stable 10.0.3.0 (8.1 Android) via ota. Then, I saw that I could also upgrade to miui 11. However, I've read that battery is worse than Miui 10 so I don't know If I should install it.
I've unlocked the recovery because I want to try some custom roms but I'm a bit scared of the anti-rollback.
Could you please tell me what should I do?
Thanks all.
Before you do anything you need to figure out which device you own. You bought it and you already unlocked the bootloader? That generally takes 360 hours, are you sure it wasn't already unlocked? If it was unlocked you probably have a Chinese device, and in that case be extremely careful about not relocking the bootloader. if the phone is not bound to your account ( linked to you personally) then you could brick it and have no recourse.
if you unlocked it yourself and you have a locked device , then don't worry about anti-rollback. So far it has not been implemented. Next, you heard wrong about Miui 11, its battery is equally as good. Although the best version of Miui and currently the most stable Android 10 overall is Xiaomi.EU which is a custom rom based on the china beta but globalised, with Google services.
Again do your homework, avoid extremely old posts that are no longer relevant. Never attempting upgrading your screen refresh and never flash someone else's persist image and you will be good. This community has tons of infor...read a lot and take your own notes.
tsongming said:
Before you do anything you need to figure out which device you own. You bought it and you already unlocked the bootloader? That generally takes 360 hours, are you sure it wasn't already unlocked? If it was unlocked you probably have a Chinese device, and in that case be extremely careful about not relocking the bootloader. if the phone is not bound to your account ( linked to you personally) then you could brick it and have no recourse.
if you unlocked it yourself and you have a locked device , then don't worry about anti-rollback. So far it has not been implemented. Next, you heard wrong about Miui 11, its battery is equally as good. Although the best version of Miui and currently the most stable Android 10 overall is Xiaomi.EU which is a custom rom based on the china beta but globalised, with Google services.
Again do your homework, avoid extremely old posts that are no longer relevant. Never attempting upgrading your screen refresh and never flash someone else's persist image and you will be good. This community has tons of infor...read a lot and take your own notes.
Click to expand...
Click to collapse
Hi Thanks for your reply.
My device is global version (not just global ROM, I do know the difference)
I am unlocked the bootloader using the Xiaomi official tool, i had to activate the developer tools on the device and check the bootloader status and the button which was there ( U know what I mean). Besides, when I turn on the device it says unlocked.
I've read that miui 11 has kinda bad sot because of miui and/or the bug with WhatsApp. So I don't know if I have to update via ota and If I do that I don't know if I will have any problems while trying to install a custom ROM.
I've had a Xiaomi before so I know that I shouldn't install strange zips.
Thank you
Boiisxu said:
Hi Thanks for your reply.
My device is global version (not just global ROM, I do know the difference)
I am unlocked the bootloader using the Xiaomi official tool, i had to activate the developer tools on the device and check the bootloader status and the button which was there ( U know what I mean). Besides, when I turn on the device it says unlocked.
I've read that miui 11 has kinda bad sot because of miui and/or the bug with WhatsApp. So I don't know if I have to update via ota and If I do that I don't know if I will have any problems while trying to install a custom ROM.
I've had a Xiaomi before so I know that I shouldn't install strange zips.
Thank you
Click to expand...
Click to collapse
Yes, the last build of Xiaomi.EU had worse SOT than usual ( about 5 hours. However, the issue was only with one of the weekly builds) I personally resolved that issue for myself by flashing the kernel from the previous build. Also, Xiaomi.EU is updated every Thursday so later today there will be a new build that will very likely resolve the issue. On the other hand the stable builds do not have an issue with SOT. At least not in my experience. I have averaged around 8 to 9 hours SOT.
I don't use Whatsapp, so I can't help you with that.
Since you were previously on stock you will need to backup your data, if you are still using stock, backup to MiCloud as well. This way if you use a Miui based rom you can quickly restored most of your data and partial settings. You will also need to format use storage (type yes, reboot to recovery)
tsongming said:
Yes, the last build of Xiaomi.EU had worse SOT than usual ( about 5 hours. However, the issue was only with one of the weekly builds) I personally resolved that issue for myself by flashing the kernel from the previous build. Also, Xiaomi.EU is updated every Thursday so later today there will be a new build that will very likely resolve the issue. On the other hand the stable builds do not have an issue with SOT. At least not in my experience. I have averaged around 8 to 9 hours SOT.
I don't use Whatsapp, so I can't help you with that.
Since you were previously on stock you will need to backup your data, if you are still using stock, backup to MiCloud as well. This way if you use a Miui based rom you can quickly restored most of your data and partial settings. You will also need to format use storage (type yes, reboot to recovery)
Click to expand...
Click to collapse
I see.
I've just updated to miui 11 stable via ota.
BTW, Is TWRP the best recovery for this device isn't it? I've read that exist other types of recovery (not CWM but someones).
And my last question, I cannot find which version of gcam fits on miui 11 (Android Pie). Is there any thread, telegram channel?
Thanks for all.
Boiisxu said:
I see.
I've just updated to miui 11 stable via ota.
BTW, Is TWRP the best recovery for this device isn't it? I've read that exist other types of recovery (not CWM but someones).
And my last question, I cannot find which version of gcam fits on miui 11 (Android Pie). Is there any thread, telegram channel?
Thanks for all.
Click to expand...
Click to collapse
Personally I use the TWRP that I posted here : I talked to a few friends / android developers on other devices and several of them believe that this a TWRP issue.
I have not had any more of these issues since using this TWRP https://forum.xda-developers.com/showpost.php?p=80952013&postcount=121
If using AOSP, you should use the official version.
The best Gcam ( I Think is by Sanity )
https://www.celsoazevedo.com/files/android/google-camera/dev-san1ty/
FYI the builds made for the Poco F1 and Razer 2 are also compatible.
tsongming said:
Personally I use the TWRP that I posted here : I talked to a few friends / android developers on other devices and several of them believe that this a TWRP issue.
I have not had any more of these issues since using this TWRP https://forum.xda-developers.com/showpost.php?p=80952013&postcount=121
If using AOSP, you should use the official version.
The best Gcam ( I Think is by Sanity )
https://www.celsoazevedo.com/files/android/google-camera/dev-san1ty/
FYI the builds made for the Poco F1 and Razer 2 are also compatible.
Click to expand...
Click to collapse
Thank for helping me.
As I've posted in the official twrp thread, I was able to install twrp and get to it but after power off the phone and try to get there again miui recovery was there instead.
I've installed the last build of twrp 3.3.1.1.
Maybe If I install magisk via TWRP I will have twrp *forever*.(?)
Thank you man
Boiisxu said:
Thank for helping me.
As I've posted in the official twrp thread, I was able to install twrp and get to it but after power off the phone and try to get there again miui recovery was there instead.
I've installed the last build of twrp 3.3.1.1.
Maybe If I install magisk via TWRP I will have twrp *forever*.(?)
Thank you man
Click to expand...
Click to collapse
No problem.
After installing TWRP, you must initially install Root and then reboot to recovery.
Often you will see a message asking if you want to install the TWRP manager, click those boxes and then proceed to rebooting to recovery.
If you are using the full stock Rom, you must have root, so anytime that you flash the official Global stable rom, or an update, flash root again...unless you see via the Recovery terminal that Root maintained it's persistence.
tsongming said:
No problem.
After installing TWRP, you must initially install Root and then reboot to recovery.
Often you will see a message asking if you want to install the TWRP manager, click those boxes and then proceed to rebooting to recovery.
If you are using the full stock Rom, you must have root, so anytime that you flash the official Global stable rom, or an update, flash root again...unless you see via the Recovery terminal that Root maintained it's persistence.
Click to expand...
Click to collapse
Okey, I'll try tomorrow again.
Thanks.