Related
Here's an attempted TLR of what has happened
Tried installing LineageOS. Got Error 7. Tried a bunch of things to make it work like editing the updater-script and things like that but it didn't work.
Then I simply wanted my phone to work again. Installed Clean Stock ROM + Stock Recovery straight out of OnePlus webpage. Now I have permanent dm-verity error (tried going back to 4.0.2, disabling dm-verity via fastboot commands and restoring 4.0.3) and still appears.
So yeah, basically that.
I messed up like a month ago too, bricked the OP3T and managed to revive it with a chinese program.
Any ideas on why I can never manage to install LineageOS?
EDIT: After the last factory reset, the phone wouldn't find any wifi network. After an hour or so, it found my wifi and got a 92mb update that fixed the dm-verity error
What firmware are you running and what's your Android version? If you're running 7.1.1 on 4.1.0 you should be good to go just by flashing all the latest LOS files
sakumaxp said:
What firmware are you running and what's your Android version? If you're running 7.1.1 on 4.1.0 you should be good to go just by flashing all the latest LOS files
Click to expand...
Click to collapse
I just received the 4.1.0, going to try again tonight. Hope it works
I successfully rooted my droid (that came with lollipop), using this guide
https://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684
installed twrp backed up the stock OS and installed resurrection remix lollipop rom. I did not install any different modems or radios as I planned to stay on lollipop.
Everything worked great yet after a day or two the display/phone would appear to lock up. I can press power, the display doesn't come on and when (usually) moving the the volume up/down I do hear sounds. Sometimes at this point it will reboot by itself, other times I have to reboot it.
When it comes up it goes through the android is upgrading thing, and sometimes works fine after, sometimes not, regardless eventually this problem repeats.
Thinking it was perhaps RR I tried straight Cyanogenmod, and eventually the rooted stock OS, both have this same problem.
I've tried using it with very minimal installed in the way of apps, same issue.
I've tried saving the log to SD to peer at later, but going through it I don't really see anything obvious to show what the problem is.
I"m wondering if there's a problem with the phone itself (it's a refurb) and am considering unrooting it and returning it.
Anyone seen this or thoughts on what might be the issue?
p.s.
if you happen to have a good link handy to an unrooting guide you might shoot it my way thanks.
thanks in advance!
What versions of the other ROMs did you use? Lollipop also, or Marshmallow? Nougat? For rooted stock ROM did you upgrade to Marshmallow? None of the Lollipop ROMs are supported anymore, so hard to answer for those.
There are ways to grab logs after a reboot, but here's another suggestion...
I use Auto Reboot app (needs root) to schedule a reboot my phone every day while I'm asleep.
This seems to keep the cobwebs cleared out, so the phone runs better. I know you want to find the issue, but maybe it's an accumulation of apps not releasing RAM orb something. This might help prevent that.
thanks for the reply
ChazzMatt said:
What versions of the other ROMs did you use? Lollipop also, or Marshmallow? Nougat? For rooted stock ROM did you upgrade to Marshmallow? None of the Lollipop ROMs are supported anymore, so hard to answer for those.
Click to expand...
Click to collapse
I tried the last released CM lollipop snapshot, as well as the last nightly.
For RR it was last released, "ROM OS Version: 5.1.x Lollipop"
ChazzMatt said:
There are ways to grab logs after a reboot,
Click to expand...
Click to collapse
Yeh I've been saving it to the SD so I can view it after a reboot, I've looked at 4 or 5 of them after the problem occurred and at least to me nothing really stood out
ChazzMatt said:
but here's another suggestion...
I use Auto Reboot app (needs root) to schedule a reboot my phone every day while I'm asleep.
This seems to keep the cobwebs cleared out, so the phone runs better. I know you want to find the issue, but maybe it's an accumulation of apps not releasing RAM orb something. This might help prevent that.
Click to expand...
Click to collapse
Yeh I expect it might periodically need a reboot but if it's just unpredictiably locking up or rebooting on its own it's not very usable.
I think I'm just going to have to try to unroot and return, maybe I'll go with a LG V20 as I don't want to have pay to re-root another one of these and possibly have same issue. Also the whole pay to have some app do something secret to my phone does leave me a bit uneasy.
Kind of a bummer as I'm actually pretty impressed with this device, fast, good battery, takes nice photos, only drawbacks for me are no removable SD and lack of LED notification, but I was willing to live without those given how good everything else was.
thanks
Same here,
I tried with different Roms 7.X, still blocking and display not turning on.
I'd appreciate some help.
Thanks!
Android Version: 7.1.2
Current Rom: AOKP
Kernel: 3.10.107-Stock-bhb27-nougat-kerneL
MrN00b said:
Same here,
I tried with different Roms 7.X, still blocking and display not turning on.
I'd appreciate some help.
Thanks!
Click to expand...
Click to collapse
FWIW and in case it helps you or someone else, I seem to have fixed mine finally, here's what I did.
First I installed latest twrp (mod 4) https://androidfilehost.com/?w=files&flid=39562 (there's a thread on this twrp if you want tor read on it). That in itself didn't fix the issue but did finally let me format and got rid of an 'mkfs.f2fs: invalid option -- r, ERROR=1' type error I used to get.
I installed this stock zip from twrp as described in thread:
https://forum.xda-developers.com/droid-turbo/development/rom-su4tl-49-100-stock-t3390041
It would never actually boot it would shut my phone off not long after showing the boot screen, and I'm not sure if doing that was necessary or not.
Taking some suggestions from here:
https://forum.xda-developers.com/droid-turbo/help/help-request-custom-rom-phone-unlocked-t3767070
I dug up the last official CM 13 snapshot:
https://www.google.com/search?q=cm-13.0-20161221-SNAPSHOT-ZNH5YAO3Y5-quark.zip
sha1: 9a219dd487c27e51b0c5c4922812838f394099c5
Wipe and installed with no gapps and voilà it would boot consistently. Without reinstalling I tried installing pico gapps and it would still boot though it took maybe 15 mins initially.
I want Nougat so I wiped and installed lineage-14.1-20180612-UNOFFICIAL-quark.zip from https://forum.xda-developers.com/moto-maxx/development/rom-t3494646 again no gapps and it also booted fine, whereas previously it would hang on booting. Without reinstalling ROM I tried installing opengapps nano and it would just hang.
I could then no longer get it to boot again, so I reinstalled CM13 no gapps, which booted fine, wipe and install lineage-14.1-20180612-UNOFFICIAL-quark.zip no gapps, and now it boots fine though currently it's taking a while.
I should perhaps note I took twrp backups inbetween steps whenever I had a working boot, (ex before installing gapps), but once the phone went back to hanging on boot, those restores didn't help. Only reflashing CM13 seemed to clear things up.
My ultimate goal is a LOS ish Nougat/Oreo ROM with no gapps using microg, and running tmobile, I'll see what I end up with.
OOS 5.0 (Oreo) seems to have a few hiccups, most notably lower battery life, and many are reverting back to OOS 4.5.1.
For those who've tried to downgrade to 4.5.1, can it be done without wiping internal storage? I'm trying to avoid this because I don't want to copy close to 100GB of files back to my phone as it's very time-consuming.
I use Titanium Backup so I'm not worried about app data too much. I'm currently rooted with Magisk and would like to go back to the same rooted setup on 4.5.1. I'm also on blu_spark/eng.stk's oreo-compatible TWRP right now.
rebelpixel said:
OOS 5.0 (Oreo) seems to have a few hiccups, most notably lower battery life, and many are reverting back to OOS 4.5.1.
For those who've tried to downgrade to 4.5.1, can it be done without wiping internal storage? I'm trying to avoid this because I don't want to copy close to 100GB of files back to my phone as it's very time-consuming.
I use Titanium Backup so I'm not worried about app data too much. I'm currently rooted with Magisk and would like to go back to the same rooted setup on 4.5.1. I'm also on blu_spark/eng.stk's oreo-compatible TWRP right now.
Click to expand...
Click to collapse
Unless you backup your 4.5.1 with the same twrp you are using right now, there might be a risk.
but you already have backup, right ? the worst thing is having to wait for those 100GB data to be copied back to your phone, rather than loosing everything.
I actually didn't bother doing a nandroid backup of my 4.5.1 partitions, all I did before upgrading to oreo was:
- titanium backup of all apps
- copy all of /sdcard to an external disk
I'm just considering what would be the shortest path to going back to 4.5.1.
What would be great though is if Oneplus releases the next version of stable Oreo that fixes the battery drain and the other issues that people have encountered.
I don't know why the peoples are complaining high battery drain in oxygen os 5.0. Peoples also complaint about VOLTE issues but I am using it without any issue. Perhaps they don't perform clean flash before ROM installation.
ersandeepkr said:
I don't know why the peoples are complaining high battery drain in oxygen os 5.0. Peoples also complaint about VOLTE issues but I am using it without any issue. Perhaps they don't perform clean flash before ROM installation.
Click to expand...
Click to collapse
Clean flashing would be a good option for tbose who have time. But the Oreo update was designed to be a seamless upgrade from OOS 4.x, especially for normal users who haven't even heard of the xda forums.
I don't think the same issues manifested for everyone, but considering the general response in Oneplus's forum, I think the OOS 5.0 problem has some issues.
Just to add, I can confirm better performance and battery life when I downgraded to 4.5.1.
rebelpixel said:
Clean flashing would be a good option for tbose who have time. But the Oreo update was designed to be a seamless upgrade from OOS 4.x, especially for normal users who haven't even heard of the xda forums.
I don't think the same issues manifested for everyone, but considering the general response in Oneplus's forum, I think the OOS 5.0 problem has some issues.
Just to add, I can confirm better performance and battery life when I downgraded to 4.5.1.
Click to expand...
Click to collapse
XDA forum is mainly for rooter.......
rebelpixel said:
Clean flashing would be a good option for tbose who have time. But the Oreo update was designed to be a seamless upgrade from OOS 4.x, especially for normal users who haven't even heard of the xda forums.
I don't think the same issues manifested for everyone, but considering the general response in Oneplus's forum, I think the OOS 5.0 problem has some issues.
Just to add, I can confirm better performance and battery life when I downgraded to 4.5.1.
Click to expand...
Click to collapse
Where exactly is it stated that Oreo is designed like this?
Sent from my ONEPLUS A3003 using Tapatalk
RASTAVIPER said:
Where exactly is it stated that Oreo is designed like this?
Click to expand...
Click to collapse
Hey, the thread has been cleaned because of your trolling. Just stop it if you can't contribute anything useful to this topic.
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
Hey,
I got my Pixel 7 last week and installed Graphene OS on it, however after some days I noticed it behaved very strange.
No buttons on the phone worked anymore, neither the power nor the volume buttons. After I did a full reboot the buttons worked again, but then the fingerprint scanner is not available anymore?!
As i very much like to have both, the buttons and the finger print, working I did a factory reset and installed LineageOS. But now I have the same beavior again after 2 days with the new ROM.
Did anyone experiences something similar already? Do you think this is a hardware issue? Can I still get a replacement if I already unlocked the bootloader and tinkered around with the OS on the phone?
Sounds like a hardware issue. Although its a bit strange that it would affect either the fingerprint sensor or the buttons. Could you describe what goes on with the fingerprint sensor in more detail?
Well the fingerprint hardware is simply not available, conpletely gone from the settings, doesn't show up on the lockscreen, like it doesn't even exist on the device.
If I then reboot the hardware is available again but the whole OS is super buggy, the buttons don't work and the phone will soft reboot after a few minutes.
Before you call it a hardware issue why not flash back to stock and verify. Most likely a rom issue and I'm sure the other rom pulls from the lineage source, most do. Would also explain the issue persisting on two different roms.
Yeah I will try it but the Android flash tool failed on me on 2 seperate machines. So now I habe to do it manually with adb it seems.
But even if the Stock ROM works, it's still weird, as nobody else reporting on this.
elba96 said:
Yeah I will try it but the Android flash tool failed on me on 2 seperate machines. So now I habe to do it manually with adb it seems.
But even if the Stock ROM works, it's still weird, as nobody else reporting on this.
Click to expand...
Click to collapse
I seem to recall a problem with fingerprint disappearing from screen and settings like you described. I think it was in the Pixel 6 forums months ago. I don't remember any details.
It's not unusual to lose certain functions with a custom ROM but the button problem is definitely unusual. Whether it's software or hardware, if you can reproduce at least one of these problems with stock Android then I think you have your answer. And as long as factory firmware is installed, bootloader is locked and you factory reset it, you should be ok returning the phone for repair or replacement.
Thanks for the answer!
Today I finally had the time to flash a factory image. After rooting and restoring all my apps the issue reappeared after about 20 min. on the stock rom it was even more severe. Now I uninstalled magisk and flashed the stock init_boot.img file and until now it seems fine.
Can the patched boot image cause the problems described above, or even an unlocked bootloader?
elba96 said:
Can the patched boot image cause the problems described above, or even an unlocked bootloader?
Click to expand...
Click to collapse
If these problems are caused by bootloader unlocking or rooting stock Android I think the same would've happened to other people by now and it would have been mentioned.
Regarding the bootloader, was GrapheneOS fully erased? In particular its verified boot key.
GrapheneOS CLI install guide
Command-line installation instructions for GrapheneOS, a security and privacy focused mobile OS with Android app compatibility.
grapheneos.org
If that's not it, or something similar leftover from Lineage, I think you should forget any modifications long enough to reproduce your problems in the phone's factory state. Just run flash-all.bat (or bash equivalent) and let it wipe, lock the bootloader, install updates and use the phone. Time consuming, I know. But if there are hardware issues one or both problems may show up again and it's less of a mystery.
manjaroid said:
Regarding the bootloader, was GrapheneOS fully erased? In particular its verified boot key.
Click to expand...
Click to collapse
Thanks for the notice, I forgot about this!
So far the stock rom without root performs ok, no problems. It just sucks to not have all the customizations I'm used to for the last 10 years...
Maybe try not restoring any apps and see if it still persists.
manjaroid said:
If these problems are caused by bootloader unlocking or rooting stock Android I think the same would've happened to other people by now and it would have been mentioned.
Click to expand...
Click to collapse
@elba96
Maybe it's too soon to dismiss Magisk patching as the problem. You might try Magisk stable 25.2 or canary 25206 if you've been patching with one of the newer 26.x releases.
I'm starting to suspect my patched boot image may be the cause of a new problem on a Pixel 5. Either that or it's a new Android bug.
My problem is similar to one of yours: a lost function combined with a disappearing setting. SmartLock hasn't worked right since the April update a couple days ago. When I check its settings all three SmartLock options are gone. Rebooting brings them back and I'm able to get SmartLock working again. The problem seems to repeat when the phone goes idle and locks down.
By now I'm pretty sure it was the patched boot image. Until now (2 days) the stock ROM doesn't show any bugs.
And now that you say it. I used Magisk 26 for the patching as it rolled out right when I was setting up my phone. Should have stayed with v25.x it seems.
I'll give it 1 or 2 days more just to be sure and then I'll try it with Magisk v25.x again.