Related
Hey,
Just got a OnePlus 3T (Midnight Black) for my wife and wanted to get it rooted and updated to 7.1.1 as soon as I got it. I followed TK's suggestion on his video on using Opera VPN to change my region to Canada and got the update on the first try. After all was said and done I put my wife's sim card to start using the device and the 3T will not allow me to send phone calls, texts, or use data unless connected to Wi-Fi. I wasted a lot of time with AT&T thinking it was the sim card that was the issues but the device does receive text messages and calls so I am lost. The community on the OnePlus website has others who have issues after updating also to where their devices don't recognize the sim card(s) but they all seem pretty lost on any fixes to the issue. Anyone else have something similar or any solutions? Thanks in advance for anything positive.
No, I don't face this type of issue Sorry
After the 7.1.1 update, did you do a factory restore to make sure no data structures for the old ROM/apps is in place that could cause issues like this? In other words format the data partition.
I've always had an issue having the SIM card show up. I have to eject and reinsert the SIM slot after a reboot with the phone still on.
SIM issues after update seem to be a known problem on this phone, according to the following post. Either do a clean install of the full OTA, or do factory reset (somewhat obvious, backup any data you want to keep before doing either):
https://forum.xda-developers.com/showpost.php?p=71825477&postcount=1104
pitrus- said:
After the 7.1.1 update, did you do a factory restore to make sure no data structures for the old ROM/apps is in place that could cause issues like this? In other words format the data partition.
Click to expand...
Click to collapse
I did do a factory reset, one from settings and then two others from TWRP. I thought about it some more and since the 3T is so close to stock Android I remembered what another member suggested as far as flashing a previous version of the OS (like one would do with a Nexus device). I flashed the OnePlus 3T 7.0 version and it's working now for my wife. I downloaded the update straight from the OnePlus website. I do miss the features 7.1.1 brought but I guess I need to wait for OnePlus to iron out the bugs. Thanks all for the suggestions! Much respect to the XDA community.
rsnyc said:
I did do a factory reset, one from settings and then two others from TWRP. I thought about it some more and since the 3T is so close to stock Android I remembered what another member suggested as far as flashing a previous version of the OS (like one would do with a Nexus device). I flashed the OnePlus 3T 7.0 version and it's working now for my wife. I downloaded the update straight from the OnePlus website. I do miss the features 7.1.1 brought but I guess I need to wait for OnePlus to iron out the bugs. Thanks all for the suggestions! Much respect to the XDA community.
Click to expand...
Click to collapse
Unless you do like me, and run latest Lineage OS (Cyanogenmod), then you'll get 7.1.1 and working dual SIM. ?
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.
After upgrading (dirty flashed) to OxygenOS 5.0.5 & OxygenOS 5.0.6 from Nougat (OxygenOS 4.5.1), in the incoming calls screen doesn't appear the toggle to pick up the phone , just the caller name and number, I have to slide down the notifications bar to be able of picking up the call. Do you know how to solve this?
Factory reset - major Android upgrades require that to avoid issues
Many thanks for your answer but I'd prefer to find the root cause of the issue.
spaniard said:
Many thanks for your answer but I'd prefer to find the root cause of the issue.
Click to expand...
Click to collapse
The root cause is that you dirty flashed.
Seriously, if you have random bugs after dirty flash, the most likely solution is to clean flash or wipe data.
spaniard said:
Many thanks for your answer but I'd prefer to find the root cause of the issue.
Click to expand...
Click to collapse
The root cause is the incompatibility between major upgrades and doing such upgrade very often introduces weird bugs.
This probably wouldn't be the cause if upgraded like from Android 8.0 to 8.0.1 (just an example), but not 7 to 8.
Every manufacturer, if asked for support, will ask you to reset your device to default and check if problem persists.
Thanks guys, I know that and I think that this is the most probable solution, anyway as I'm too lazy for clean flashing will keeep researching a more direct solution. Next step: trying a new dialer.
spaniard said:
Thanks guys, I know that and I think that this is the most probable solution, anyway as I'm too lazy for clean flashing will keeep researching a more direct solution. Next step: trying a new dialer.
Click to expand...
Click to collapse
That's a temp solution till u start having other problems too.
U know what's the problem, so sooner or later u shall proceed with factory reset.
Sent from my ONEPLUS A3003 using Tapatalk
RASTAVIPER said:
That's a temp solution till u start having other problems too.
U know what's the problem, so sooner or later u shall proceed with factory reset.
Click to expand...
Click to collapse
Will try to wait until Pie
spaniard said:
I'm too lazy for clean flashing will keeep researching a more direct solution. Next step: trying a new dialer.
Click to expand...
Click to collapse
My opinion, the clean flash is the more direct solution. Tinkering with things like a new dialer is indirect. You may even be causing more problems than you solve. The problem is conflicting user data. The stock dialer app works just fine.
With a dirty flash, I always say "hope for the best, prepare for the worst". Meaning, you can try to dirty flash (as it is quite convenient). But be prepared to wipe or clean flash if you run into any issues with the dirty flash (which you are).
Well, the issue was caused by an old call recording Magisk module, restored latest nandroid backup, deleted the module and dirty flashed again 5.0.6 an everything looks working nice again .
After upgrade to 9.0.4 => Error message "corrupt data" and no way from there
After upgrade to 9.0.4 (from 8.1, rooted with magisk) I was getting an error message "password is correct but data is corrupt... factory reset needed".
Factory reset? No way! I have a backup of the state just before upgrade to 9.0.4 (made with TWRP v3.2.3-0), and wanted to go back to that state.
First strange thing: This wasn't possible with TWRP v3.2.3-0 anymore because it needed to reformat /data with f2fs which lead to an error. TWRP v3.3.1-0 solved that issue.
After restore first I was unpatient, but waiting overnight finally returned my phone to the saved state (except that my internal storage was gone, because it was killed by the 9.0.4 upgrade).
But then it turned out that some things are not as good as before:
1) The fingerprint sensor is dead
2) "Calling" *#808# shows an error "Connection problem or invalid MMI code"
3) When re-entering TWRP the /data partition cannot be mounted (after a much too quick entry indicating that decryption did not took place)
What did the 9.0.4 update do to prevent the nandroid from 100% restore ? What can I do?
What do I need to do, to at least get my backup working just as it worked before?
What do I need for a successful upgrade to 9.0.4?
After spending major part of this weekend, this is what I found out so far:
1) Doing restore directly on the filesystem after 9.0.4 upgrade was the reason for the multiple strange behavior afterwards. Correct restore was like this:
- Flash a 5.0.8 stock firmware (!!!)
- Flash TWRP v3.3.1-0 (using v3.2.3-x would still fail with /data restore)
- Restore the backup, but leaving out the "system image"
2) After the successful restore, however, TWRP couldn't decrypt the /data partition. Flashing TWRP v3.2.3-1 was the solution for this.
3) BTW: The issue with *#808# was due to a non-stock dialer I was using. What misled me was that also the non-stock dialer was able to run some USSD codes, but strangely not all, and especially not the diagnostics one.
Ok, all issues solved so far, but now I'm on 5.0.8 again. And there I have this banking app, which once in a while tells me that "a phone with these settings is not supported due to high security standards" (meaning that it's rooted). In the past this issue has always been able to be fixed by firmware or magisk update. But right now magisk is at v19.3 and no update available. So, I need to upgrade the OS (I assume).
Is there a safe way to upgrade to 9.0.4 (or 9.0.5, which came out last Friday)?
Just an idea I'm having from the issues with TWRP version (one seems to work only with 5.0.8, the other only with 9.0.x): Might it be as simple as flashing a stock recovery just for the update? Or are there other things to obey?
ako673de said:
Is there a safe way to upgrade to 9.0.4 (or 9.0.5, which came out last Friday)?
Click to expand...
Click to collapse
The safe way is here:
https://forum.xda-developers.com/oneplus-3t/how-to/guide-cope-9-0-3-5-0-8-firmware-barrier-t3941164
Dirk said:
The safe way is here:
https://forum.xda-developers.com/oneplus-3t/how-to/guide-cope-9-0-3-5-0-8-firmware-barrier-t3941164
Click to expand...
Click to collapse
Hello Dirk,
I've read so many threads these days, to just confuse me even more. This is the very first really helpful tip.
Maybe I will try it out. But as for now the mixing of 5.0.8 and 9.0.x parts of the firmwares feels so desparately dirty, that maybe I should better try everything else first.
And here your other comments about banking apps were very interesting. Why exactly did you remove them later?
First of all I need to mention, that all my banking apps worked just fine until about 2 weeks ago. Basically everything is still perfectly alright: Safetynet is still being passed, the device is still "certified", magisk is still well hidden, and none of the critical apps "see" the root. Furthermore it's only one out of 4 banking apps that has stopped working (unfortunately it's the most critcal one with no alternative access (no website, no HBCI)).
So, could you please get a little bit more in detail?
I don't know enough about the details, but intuitively an unlocked bootloader might well be something a banking app could successfully look out for. But none of my research pointed me to a thread where the bootloader was successfully relocked with TWRP present. Could you please point me to that one?
The "LOS" thread, what exactly is that, and where? LineageOS? That's a branch from CyanogenMod, as far as I have read. What exactly does this ROM better wrt banking apps? I already had CM on my former Samsung S4, and it didn't work out very well. It was full of bugs...
And what exactly is "NLOS" (wrt banking apps)?
Thank you very much for your assistance.
ako673de said:
I've read so many threads these days, to just confuse me even more. This is the very first really helpful tip.
Maybe I will try it out. But as for now the mixing of 5.0.8 and 9.0.x parts of the firmwares feels so desparately dirty, that maybe I should better try everything else first.
Click to expand...
Click to collapse
If your aim is to be on the latest version of OOS whilst preserving Data, you need to use the modified Firmware.
LineageOS with latest TWRP allows you to relock your Bootloader. You wouldn't have any issues with Banking Apps with that setup. You can't get from OOS to LOS without losing Data though, and there's no point discussing custom ROMs further if your objective is to be on OOS.
Solved the banking app issue! It's the so called UDS detection method which was new and is not yet covered by magisk (incl. Beta), but the so called "canary" branch.
BTW: Bootloader is (should be) not something an app can detect with magisk in place.
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.