Related
G'day people I've run into something pretty weird with my OnePlus One. I installed the CM12 nightly and booted it up, ran it for a few hours then got ghost touches and the screen became unresponsive at times.
So, having my usual backup of CM11S, I wiped and restored to the latest backup I had and everything was weird. I kept getting ghost touches and reduced responsiveness, and sometimes it would just randomly malfunction and not unlock and just keep the screen off.
Rebooting clears up the problem for about 5 minutes and then it comes back at full blast.
I tried installing the last CM11S update via flashing Calkunins stock XNPH44S zip and still I have all these weird issues that wasn't there before I flashed the CM12 nightly.
Has anyone come across this problem or is it just me and my device? It's seriously a cause for concern, and I'm posting this to both XDA and the OnePlus forums in hopes of getting some sort of help and relief in this situation.
Any assistance is appreciated and I thank you in advance for taking the time to read this.
reflash cm12 nightly and try again.
perhaps use fastboot to flash the partitions .
You might need to find a copy of the first cm11s rom and try that one. I have a feeling your one of the unlucky with firmware sensitivity.
Which date is your phone from? (its on the box)
Sent from my A0001 using XDA Free mobile app
GO back to completely factory fresh, via fastboot commands.
If you still have problems, it's a hardware issue then.
kthejoker20 said:
GO back to completely factory fresh, via fastboot commands.
If you still have problems, it's a hardware issue then.
Click to expand...
Click to collapse
not entirely true, there are different screens, that could be the issue. It was reported in boeffla kernel thread. sesrch throught it and it might contain something useful to try.
also open a support question, Oneplus needs to know how annoying their poor choice of different lcds are
Sent from my A0001 using XDA Free mobile app
bachera said:
reflash cm12 nightly and try again.
perhaps use fastboot to flash the partitions .
You might need to find a copy of the first cm11s rom and try that one. I have a feeling your one of the unlucky with firmware sensitivity.
Which date is your phone from? (its on the box)
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
I'll try to flash CM11S via fastboot to see if it clears up the issue. For now, the date I got mine is 2014-07-16. Shipped to me after 12 days (International shipment via courier)
UPDATE
Flashing CM11S via fastboot resolved all issues as far as I can tell.
Will remain on the lookout for the bugs in the future but for now I'm happy to say it worked for me.
Thank you all again for the advice and guidance, it was appreciated.
GLad it worked for you.
I love when other posters try to punk you when you try to help people.
kthejoker20 said:
GLad it worked for you.
I love when other posters try to punk you when you try to help people.
Click to expand...
Click to collapse
Nobody was trying to "punk" you. There are usually several different potential causes for the same symptom, all he was doing was highlighting that and adding extra information in order to help further (in the case that flashing the stock images didn't help, which has happened many times). He was also trying top help the OP. Calm down.
Transmitted via Bacon
timmaaa said:
Nobody was trying to "punk" you. There are usually several different potential causes for the same symptom, all he was doing was highlighting that and adding extra information in order to help further (in the case that flashing the stock images didn't help, which has happened many times). He was also trying top help the OP. Calm down.
Transmitted via Bacon
Click to expand...
Click to collapse
I thought it was the partition thing too because I had almost the same problem on my HTC Amaze back in 2014, and flashing the OEM RUU helped with sorting things out.
But as for the random screen touches, flashing everything from fastboot helped for only a few hours. The symptoms came back after a while, specifically when I replaced my music and pictures. I'm thinking that I may have a corrupted file on it somewhere but I doubt it'll cause a malfunction like that.
So I tried flashing Franco Kernel, and it seems to have cleared it up..... for now.
It's so frustrating thinking that my device may be defective
UPDATE #2
Flashing Franco Kernel didn't help. Symptoms came back within a couple hours. Will try a custom ROM, specifically AOPK (because I want to )
If that doesn't fix the issue then I've just got to face the fact that I have a defective device (somehow)
Bump
Nothing worked. I contacted the manufacturer but they seem to think doing a factory reset will help. It didn't.
Flashing CM11S via fastboot doesn't help
I really think this is a hardware issue that just emerged from nowhere, probably due to lack of premium or standardized quality adhesive.
There's a really long thread over at the OnePlus forums about a guy who found it was a grounding issue and took some adhesive tape to insulate the area near the proximity sensor (I think? I'll include the link in here somewhere)
Honestly, OnePlus impressed me....at first. But I cannot use a phone that's not working properly.
https://forums.oneplus.net/threads/...-hint-it-was-never-a-software-problem.186235/
Same problem here... I had the first ghost touches after having installed CM12 Nightly.
I was using CM12 built by Daleski75 so far without any issue. The problem does not appear on a regular basis and when it does, a reboot seems to fix it, at least for a few minutes/hours.
I'll try a clean install when the stable version is out (don't really want to wipe now and once more in two/three weeks).
@rdar_93: Did you find a solution? Are you going to send the device back to OnePlus? If it is actually a hardware issue, that will be enough for me, no more OPO. Sending the device back to China after 2 months of use and having to pay for the shipping is not acceptable.
Edit: It's getting worse... I am gonna wipe soon. Here is a short video: drive.google.com/file/d/0B-EYHGTB15_wS1JXdXlmZXVsT0k/view?usp=sharing
I can't post link for now so you'll have to copy and paste it in your browser.
Edit2: After a full wipe and the installation of the latest nightly, the situation seems to be better, even though I will have to use the phone a bit more to see if it happens again. By the way, I lost dt2w and the gestures don't work well, if not at all... When I draw a V, nothing happens, when I draw a circle, the phone behaves as if I did a double tap. Weird. Again, this happens after a wipe+latest nightly installation+wipe again (to be sure ).
sylvain15250 said:
Same problem here... I had the first ghost touches after having installed CM12 Nightly.
I was using CM12 built by Daleski75 so far without any issue. The problem does not appear on a regular basis and when it does, a reboot seems to fix it, at least for a few minutes/hours.
I'll try a clean install when the stable version is out (don't really want to wipe now and once more in two/three weeks).
@rdar_93: Did you find a solution? Are you going to send the device back to OnePlus? If it is actually a hardware issue, that will be enough for me, no more OPO. Sending the device back to China after 2 months of use and having to pay for the shipping is not acceptable.
Edit: It's getting worse... I am gonna wipe soon. Here is a short video: drive.google.com/file/d/0B-EYHGTB15_wS1JXdXlmZXVsT0k/view?usp=sharing
I can't post link for now so you'll have to copy and paste it in your browser.
Edit2: After a full wipe and the installation of the latest nightly, the situation seems to be better, even though I will have to use the phone a bit more to see if it happens again. By the way, I lost dt2w and the gestures don't work well, if not at all... When I draw a V, nothing happens, when I draw a circle, the phone behaves as if I did a double tap. Weird. Again, this happens after a wipe+latest nightly installation+wipe again (to be sure ).
Click to expand...
Click to collapse
I contacted them and they sent me a program to use. It uses fastboot to flash CM11S and probably fix the partitions that are messed up (I'm making an assumption)
UNFORTUNATELY I'm stuck in a bootloop.
I'm so angry, disappointed and depressed at the same time. I paid about $2500 TTD (in my country) which is probably the equivalent to somebody's rent. I had to work a month to save up the money to buy this and it turns out that the device is faulty after a certain amount of time (or at least mine was)
This is BS.
They said to send them a snapshot of what went on with the fastboot thing, so I figure I"ll upload it here too.
rdar_93 said:
I contacted them and they sent me a program to use. It uses fastboot to flash CM11S and probably fix the partitions that are messed up (I'm making an assumption)
UNFORTUNATELY I'm stuck in a bootloop.
I'm so angry, disappointed and depressed at the same time. I paid about $2500 TTD (in my country) which is probably the equivalent to somebody's rent. I had to work a month to save up the money to buy this and it turns out that the device is faulty after a certain amount of time (or at least mine was)
This is BS.
They said to send them a snapshot of what went on with the fastboot thing, so I figure I"ll upload it here too.
Click to expand...
Click to collapse
I guess you didnt unlock bootloader first
Which when you do wipes the phone so you loose all your stuff.
possible workaround is fasboot on custom recovery and then flash the zip that sets unlock status and circumvents the whole format thing
Sent from my A0001 using XDA Free mobile app
bachera said:
I guess you didnt unlock bootloader first
Which when you do wipes the phone so you loose all your stuff.
possible workaround is fasboot on custom recovery and then flash the zip that sets unlock status and circumvents the whole format thing
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
I actually did unlock my bootloader.
PS I also got tired of seeing CM11S try to boot up so I flashed ColorOS (because it's the only rom I had on my laptop. Why not download another 4.4.x AOSP rom? Unstable wifi at school)
So yeah, wifi is not turning on. Gonna try the program again. I wonder if it would work this time?
The conditions aren't as different as before, could work, right?
Honestly I want to wait but they take so long to reply.
UPDATE
After flashing ColorOS I decided to go back and try doing the CM11S via fastboot commands. Still got a bootloop but hey I got the correct fastboot logo now in case if it made a difference.
So I did the compulsory flashing commands when I went from Color to CM11S and still bootlooped.
So I booted into fastboot again
fastboot oem unlock (supposed to unlock bootloader and reboot if it's locked, no reboot if unlocked [assumption])
then rebooted into fastboot again, ran the batch files OnePlus sent to me which essentially flashed CM11S just like you would over fastboot, but with added modems etc.
Successfully booted into CM11S without issues, WiFi works again and so far no symptoms as yet.
Will keep this post updated if anything happens.
My screenshots of the batch file commands OnePlus sent would be found in the attachments.
UPDATE 2
So I think it's fixed permanently this time.
I'm not sure though. It hasn't done anything weird. I will copy my music and photos to see if that would cause anything to happen
I would stay away from os since it messes up partition and people ran into data drop out and modem issues.
Cm11s Roms are the way to go on this hardware.
FYI, when you flash CM12 the radio is overwritten with an alpha/beta radio which causes (well, caused for me) THE EXACT issues OP was having in CM11/S. The CM12 radio (as far as I can tell) ONLY works with CM12 - making going back a PITA.
If you have the baseband in this thread (see screenshot in first post) then that means you are on the experimental radio and are going to have a bad time if you aren't on CM12.
I flashed the latest OTA radio found here and all was right with the world (at least where my OPO was concerned ).
hp13 said:
I would stay away from os since it messes up partition and people ran into data drop out and modem issues.
Cm11s Roms are the way to go on this hardware.
Click to expand...
Click to collapse
I would like to go back to CM11s to check if the situation is better. I tried to flash the lastest CM12 build and it seems to be better but still not as good as before
When I do a wipe and then flash the ROM in TWRP, there are some "folder already up to date", which I would like to avoid. What I would like to do is doing a complete clean install of either CM12 or CM11s plus rewriting the partitions,... So that I'm sure if the problem is still here it is due to an hardware issue.
Is there any chance someone can help me with this? Even with a link... I searched for "write partition" without any luck :-/
Thanks !
EDIT: Do you think the OnePlusRecovery Tool can help me with this?
Hi, I hope you guys can help. I have an OPO which is on Android 8 as per this link and it was all working fine (well, it's a bit buggy in places, but I can live with it!).
I have TWRP installed (3.2.3.0), and had no problems with it, was easy to access and install/backup with it; I have reasonably recent backups too (but wait for it....), and phone is rooted using Magisk.
Anyway, in a recent bout of paranoia, I encrypted my phone. It's a long story, but the company I work for recently employed an IT company to manage its systems and I didn't want them poking about where they shouldn't (they are not particularly good).
The encryption worked straight away, and clearly functions as it should; rebooting the phone requires a pattern unlock, and the phone is clearly marked as encrypted.
HOWEVER when I went to try and get into TWRP, I was faced with the same pattern unlock request - I tried it, and my pattern doesn't work. I have seen suggestions about disabling screen lock, or changing it to a PIN, but this doesn't affect the pattern unlock on TWRP. I reckon I can probably access the backups when unlocked via PC file transfer, so presumably can flash these via ADB, but I'm a bit loathe to in case something horrible happens.
So, is there a solution? do I:
try and reflash TWRP/different version of TWRP
flash the backup?
try and decrypt the phone
cry?
with regards decrypting, I can't see any way of reversing the encryption one it has happened - kinda wish I'd known that before I'd done it.
Help would be greatly appreciated. It isn't a major problem, phones working, it's just my modding is kinda curtailed....
Would this one work?
GitManMatt said:
Hi, I hope you guys can help. I have an OPO which is on Android 8 as per this link and it was all working fine (well, it's a bit buggy in places, but I can live with it!).
I have TWRP installed (3.2.3.0), and had no problems with it, was easy to access and install/backup with it; I have reasonably recent backups too (but wait for it....), and phone is rooted using Magisk.
Anyway, in a recent bout of paranoia, I encrypted my phone. It's a long story, but the company I work for recently employed an IT company to manage its systems and I didn't want them poking about where they shouldn't (they are not particularly good).
The encryption worked straight away, and clearly functions as it should; rebooting the phone requires a pattern unlock, and the phone is clearly marked as encrypted.
HOWEVER when I went to try and get into TWRP, I was faced with the same pattern unlock request - I tried it, and my pattern doesn't work. I have seen suggestions about disabling screen lock, or changing it to a PIN, but this doesn't affect the pattern unlock on TWRP. I reckon I can probably access the backups when unlocked via PC file transfer, so presumably can flash these via ADB, but I'm a bit loathe to in case something horrible happens.
So, is there a solution? do I:
try and reflash TWRP/different version of TWRP
flash the backup?
try and decrypt the phone
cry?
with regards decrypting, I can't see any way of reversing the encryption one it has happened - kinda wish I'd known that before I'd done it.
Help would be greatly appreciated. It isn't a major problem, phones working, it's just my modding is kinda curtailed....
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-one/development/recovery-twrp-3-0-3-k1-t3563692
The developers of LOS have worked in and recommended this version:
https://androidfilehost.com/?fid=1395089523397886136
Taurus_XDA said:
The developers of LOS have worked in and recommended this version:
https://androidfilehost.com/?fid=1395089523397886136
Click to expand...
Click to collapse
Thanks for this, I'll give it a go now
Working again
Taurus_XDA said:
The developers of LOS have worked in and recommended this version:
https://androidfilehost.com/?fid=1395089523397886136
Click to expand...
Click to collapse
yep, that's awesome, fully up and running now. Just for anyone else experiencing this problem, I downloaded the TWRP version listed above, then flashed it via ADB (unlock USB debugging on your phone, connect it, open a powershell window where you keep your adb files, 'adb reboot bootloader' then 'ffastboot flash recovery [NAME].img' and it will reinstall TWRP with the new version).
Bit of a moment when I rebooted to recovery, as faced with the same decryption unlock window, but this time the decryption worked and was able to access TWRP fully.
Nice one.
Hi,
A few days ago, I was on official Pixel experience rom. Fingerprint unlock started to don't work sometimes. I had to wake up screen with power button before using fingerprint sensor to unlock the phone.
Yesterday, my phone just stopped to react to any fingerprint unlock attempt. I thought that was a software issue, so I decided to migrate to LineageOS. That was a success. However fingerprint sensor doesn't work. Worse : fingerprint settings just disappeared in phone settings.
I would like to know if there is a way to test the hardware part. Or if anyone has gone through this before, any advice will be appreciated.
Thanks.
Phoque_You said:
Hi,
A few days ago, I was on official Pixel experience rom. Fingerprint unlock started to don't work sometimes. I had to wake up screen with power button before using fingerprint sensor to unlock the phone.
Yesterday, my phone just stopped to react to any fingerprint unlock attempt. I thought that was a software issue, so I decided to migrate to LineageOS. That was a success. However fingerprint sensor doesn't work. Worse : fingerprint settings just disappeared in phone settings.
I would like to know if there is a way to test the hardware part. Or if anyone has gone through this before, any advice will be appreciated.
Thanks.
Click to expand...
Click to collapse
I had the same, but I do not remember exactly how I solved it. I think by clean flashing a MIUI developer rom, booting into system, flashing twrp again, format data, and flashing my custom rom.
M1chiel said:
I had the same, but I do not remember exactly how I solved it. I think by clean flashing a MIUI developer rom, booting into system, flashing twrp again, format data, and flashing my custom rom.
Click to expand...
Click to collapse
Thank you for your answer. Do you think I can do a full nandroid backup of my current setting, then format to install MIUI, then restore my backup so I don't lose my data?
Phoque_You said:
Thank you for your answer. Do you think I can do a full nandroid backup of my current setting, then format to install MIUI, then restore my backup so I don't lose my data?
Click to expand...
Click to collapse
You should. I had difficulties with restoring a Nandroid backup, but that was probably related to encryption. So by removing your PIN or password it should work. I used the app Migrate to restore my data.
M1chiel said:
You should. I had difficulties with restoring a Nandroid backup, but that was probably related to encryption. So by removing your PIN or password it should work. I used the app Migrate to restore my data.
Click to expand...
Click to collapse
Thanks. I gonna try that when I get some free time
OK, that was a hardware issue. Everything works fine now. The fingerprint sensor flat cable was mounted fold. This must be the reason.
If someone has the same problem, it's easy to fix it by yourself. You can find cheap tools and part on aliexpress, and disassembly videos on youtube. This took me 30min and it was the first time I opened a phone.
The last photo show the new fingerprint sensor mounted unfolded
After upgrade to Android 10, GPS is having issues. It takes long time to fix a location. Tried all kind of solutions suggested on forums. Tried many apps for clearing, updating AGPS data. Nothing worked permanently.
Did anyone else faced similar issues on A2020U pro?
Also, sometimes notifications from app stopped showing. After I turn off Wifi and when data switches to LTE, I see all older notifications pop up.
I believe it's issue with Android 10. Is there possibility of rollback to its stock Android 9. I saw another thread where OP mentioned that it can be rolled back using the system update, but for that I need to have stock image on sdcard.
For rollback from stock 10 to stock 9, do I need to root/unlock bootloader/or install TWRP?
ccraze said:
After upgrade to Android 10, GPS is having issues. It takes long time to fix a location. Tried all kind of solutions suggested on forums. Tried many apps for clearing, updating AGPS data. Nothing worked permanently.
Did anyone else faced similar issues on A2020U pro?
Also, sometimes notifications from app stopped showing. After I turn off Wifi and when data switches to LTE, I see all older notifications pop up.
I believe it's issue with Android 10. Is there possibility of rollback to its stock Android 9. I saw another thread where OP mentioned that it can be rolled back using the system update, but for that I need to have stock image on sdcard.
For rollback from stock 10 to stock 9, do I need to root/unlock bootloader/or install TWRP?
Click to expand...
Click to collapse
I had a minor issue with my wifi after updating to A10, was fighting with my router. Googled it and basically A10 in general has issues... some people said they were resolved by clearing the dalvik cache. I never got around to trying it and over time the issue seems to have gone away.
Anyhow, the best way to downgrade currently is the EDL tool and firmware package I put together (for exactly this reason). You don't need to root/unlock.
Here's the tools: https://forum.xda-developers.com/t/...ded-edl-tools-new-fixes-general-tips.4174667/
And here's the Android 9 firmware: https://forum.xda-developers.com/t/rom-stock-stock-firmware-packages-for-expanded-edl-tools.4194045/
Make sure you do a full backup of your phone, then install the firmware (to make it easy, just install it to both A and B partitions). More detailed instructions are on the tools thread, ask if you have any questions.
bobthenormal said:
I had a minor issue with my wifi after updating to A10, was fighting with my router. Googled it and basically A10 in general has issues... some people said they were resolved by clearing the dalvik cache. I never got around to trying it and over time the issue seems to have gone away.
Anyhow, the best way to downgrade currently is the EDL tool and firmware package I put together (for exactly this reason). You don't need to root/unlock.
Here's the tools: https://forum.xda-developers.com/t/...ded-edl-tools-new-fixes-general-tips.4174667/
And here's the Android 9 firmware: https://forum.xda-developers.com/t/rom-stock-stock-firmware-packages-for-expanded-edl-tools.4194045/
Make sure you do a full backup of your phone, then install the firmware (to make it easy, just install it to both A and B partitions). More detailed instructions are on the tools thread, ask if you have any questions.
Click to expand...
Click to collapse
I tried clearing the dalvik cache after resetting all apps settings. That also didn't work.
Thanks for the links. I will give it a try to downgrade to previous release and will post how it goes.
Thanks @bobthenormal for the image and EDL tool. I finally tried to flash with EDL and A9 image. I could see the GPS working perfectly fine. Also tested various OTA updates, GPS problem actually starts with 1.13 A9 last security update and not with A10 (2.09). Then I reflashed again to the A9 image and have GPS working.
Now, I am having issues with sensors.
Fingerprint sensor is working but other sensors like Acclerometer, Magnetic, Gyro, Light etc are not working.
If I do the Sensor Test in EMODE with code *983*0# I could see All sensors shows "CTS Fail". Is there any mod or any patch that I can use to get sensors working?
ccraze said:
Thanks @bobthenormal for the image and EDL tool. I finally tried to flash with EDL and A9 image. I could see the GPS working perfectly fine. Also tested various OTA updates, GPS problem actually starts with 1.13 A9 last security update and not with A10 (2.09). Then I reflashed again to the A9 image and have GPS working.
Now, I am having issues with sensors.
Fingerprint sensor is working but other sensors like Acclerometer, Magnetic, Gyro, Light etc are not working.
If I do the Sensor Test in EMODE with code *983*0# I could see All sensors shows "CTS Fail". Is there any mod or any patch that I can use to get sensors working?
Click to expand...
Click to collapse
I think you're past what I know... I can only guess. Do you have a backup of your phone before installing any ROMs/firmware changes?
The other thing I would try is flashing the stock bootloader (you'll get that annoying warning on boot is the only downside). A pretty desperate leap of an idea, but I did have a problem that was only resolved by doing this. Sorry I can't be of more help!
Thanks for getting back. I am able to recover. After updating to v1.11 and v1.13 via OTA, sensors started working. But after sometime GPS again started giving issue. So I had to reflash again. Strange thing noticed that when I flash first to Partition B and then A, I see the issue of sensors not working. If I flash B later then it is working. I had to disable auto update otherwise it was updating automatically via OTA to A10. Because of that I re-flashed almost 3-4 times.
To disable auto update I had to stop all networks otherwise it downloads OTA and does not show settings menu. Sometimes it went into boot loop, but setting the correct bootable partition using your tool helped. Finally I am on A9 v1.10 and managed to disable auto update and everything is working fine. GPS is locking in 3-5 secs and no issues with notifications getting stuck when on Wifi. I have kept a backup_all after things are setup, in case required in future.
Your tool is amazing, thank you for sharing and providing detailed steps.
@ccraze I just ran into the same issue with the sensors myself. The last time I re-flashed, I only flashed partition B, because - from earlier experiences = I learned that partition B is the one that matters. So I skipped writing to partition A.
Just to be clear, what you did was this:
1. Run Load Programmer.ps1 - phone should now be connected
2. Ran Write Firmware v1.1.0 to A.ps1 <-- THIS
3. Ran Write Firmware v1.1.0 to B.ps1
4. Ran Set Bootable Partition0 Slot B.ps1
Is that right?
karlovac said:
@ccraze I just ran into the same issue with the sensors myself. The last time I re-flashed, I only flashed partition B, because - from earlier experiences = I learned that partition B is the one that matters. So I skipped writing to partition A.
Just to be clear, what you did was this:
1. Run Load Programmer.ps1 - phone should now be connected
2. Ran Write Firmware v1.1.0 to A.ps1 <-- THIS
3. Ran Write Firmware v1.1.0 to B.ps1
4. Ran Set Bootable Partition0 Slot B.ps1
Is that right?
Click to expand...
Click to collapse
@karlovac The sequence you mentioned is correct. But later I noticed that there is no set sequence which can cause this issue and no specific sequence which can fix it. After my previous post, I tried installing OTA and sensors worked. Then I reflashed it and it worked again. Later by mistake I took the OTA again and saw GPS issues. So reflashed, and then ran into sensor issue again. Again reflashing worked and AFAIK it was not in the sequence mentioned above in your post.
I would say just a matter of luck, I couldn't find exact sequence which can cause this issue. Just try flashing again, most probably you will not see sensor issues. If you still see sensor issues then try installing all OTA till your system is back to A10, meanwhile checking if the sensors are back after every OTA. If you see sensors working, then no need to install all OTAs and reflash with this image to go back to A9 and disable auto updates. Good Luck!
Thanks @ccraze . I already did *one* OTA system update to see if that fixed it but it didn't. My build number is now GEN_NA_A2020U_PROV.1.11
The way I'm testing the sensors is:
1. Open dialer
2. Enter *983*673636# -> this enables EMODE
3. Enter *983*0# -> this opens the testing app
4. Go to sensor test
They all say CTS Fail. (I got that from this thread BTW).
Do you happen to know how many OTA updates there were before you get to the "bad" A10 one? I know the bad build is GEN_NA_A2020U_PROV2.09.
@ccraze success! I did the following:
1. Wiped the cache partition. See this video. It did *NOT* fix the sensors. But apparently it's a good thing to do.
2. Did an OTA update to the next A9 build . My build number is now GEN_NA_A2020U_PROV1.13
After that, my sensors worked again. Thanks for the tips.
karlovac said:
Thanks @ccraze . I already did *one* OTA system update to see if that fixed it but it didn't. My build number is now GEN_NA_A2020U_PROV.1.11
The way I'm testing the sensors is:
1. Open dialer
2. Enter *983*673636# -> this enables EMODE
3. Enter *983*0# -> this opens the testing app
4. Go to sensor test
They all say CTS Fail. (I got that from this thread BTW).
Do you happen to know how many OTA updates there were before you get to the "bad" A10 one? I know the bad build is GEN_NA_A2020U_PROV2.09.
Click to expand...
Click to collapse
Even that is not consistent. Once, I have seen it worked fine till I got all A9 updates. But in one run GPS went bad in first OTA itself. Definitely A10 is bad, but there something else wrong with the A9 OTAs also which mess up the drivers. I would recommend to not take any OTA after flashing with this image.
karlovac said:
@ccraze success! I did the following:
1. Wiped the cache partition. See this video. It did *NOT* fix the sensors. But apparently it's a good thing to do.
2. Did an OTA update to the next A9 build . My build number is now GEN_NA_A2020U_PROV1.13
After that, my sensors worked again. Thanks for the tips.
Click to expand...
Click to collapse
Great! just make sure that OTA is not messing up GPS again. otherwise you might need to reflash and disable auto updates immediately after booting.
@ccraze how did you disable OTA updates exactly? My phone was fine for the last few days, but then it installed the A10 update last night again! I haven't restarted it yet, but it's definitely the A10 one.
I really don't know what else to do. I disabled "automatic system updates" in developer options, *and* I removed the permissions from the system update app.
Is there a different place you disabled OTA updates?
karlovac said:
@ccraze how did you disable OTA updates exactly? My phone was fine for the last few days, but then it installed the A10 update last night again! I haven't restarted it yet, but it's definitely the A10 one.
I really don't know what else to do. I disabled "automatic system updates" in developer options, *and* I removed the permissions from the system update app.
Is there a different place you disabled OTA updates?
Click to expand...
Click to collapse
After you flash the OS, immediately turn off all data (Mobile + Wifi). Then go to Settings->System->System Update->Click 3dots on the top right -> Settings -> Disable all options.
Its easy to see those options if you have all data sources turned off. It will download and will show that update is ready to install but will not install automatically.
I think I did what you're describing, right after I flashed:
However, the update still downloaded, and it sounds like if I reboot the phone, it will automatically install:
I'm afraid to reboot now since I can't afford to lose GPS reliability now.
karlovac said:
I think I did what you're describing, right after I flashed:
View attachment 5338875
However, the update still downloaded, and it sounds like if I reboot the phone, it will automatically install:
View attachment 5338877
I'm afraid to reboot now since I can't afford to lose GPS reliability now.
Click to expand...
Click to collapse
You are not following the menu items that I mentioned before. You should see following screens. Developer options system update is different setting.
Oh man, that's confusing that there are *two different* places to disable auto updates. Very frustrating!
Unfortunately now that the update is downloaded, I can't go into the System Update settings any more. The System Update app is in a state where I can't get to the ... menu. I haven't restarted my phone for 2+ weeks, since I've been traveling, and I couldn't afford for GPS to break.
Do you know if there's a way I can delete the downloaded update, so it doesn't install, using the tools?
karlovac said:
Oh man, that's confusing that there are *two different* places to disable auto updates. Very frustrating!
Unfortunately now that the update is downloaded, I can't go into the System Update settings any more. The System Update app is in a state where I can't get to the ... menu. I haven't restarted my phone for 2+ weeks, since I've been traveling, and I couldn't afford for GPS to break.
Do you know if there's a way I can delete the downloaded update, so it doesn't install, using the tools?
Click to expand...
Click to collapse
Your phone seems to have A/B partition.
So the update is written into the inactive slot.
Check which slot it's using and which slot is inactive.
Then purposely corrupt the inactive slot which contains the update. Make backup of what you change though in case you targeted the wrong stuff.
So the update will fail and the update in the inactive slot will not boot.
Then it will return back to the previous active slot with the old system.
Risk it yourself though. I never had an A/B slot, so can't make sure if it works.
pl1992aw said:
Check which slot it's using and which slot is inactive.
Then purposely corrupt the inactive slot which contains the update. Make backup of what you change though in case you targeted the wrong stuff.
Click to expand...
Click to collapse
Thanks for the feedback! When you say "purposely corrupt the inactive slot", I take it you mean that I should manually corrupt a ROM and then flash it to the inactive partition, right? I've been using the tools here to flash, so there are two scripts - one to write to partition A and one to write to partition B. Do you have any specific suggestions on what I should do to corrupt it - specific file(s) I should delete perhaps, that would guarantee it fails?
Also, to check which slot is inactive, according to this doc, it seems I should run:
fastboot getvar all | grep “current-slot”
Do I have to put my phone in EDL mode to do that, or can I run fastboot without EDL mode. I'm worried that if I put my phone in EDL mode, when I exit out of it, it will reboot. So I'll be past the point of no return.
karlovac said:
Thanks for the feedback! When you say "purposely corrupt the inactive slot", I take it you mean that I should manually corrupt a ROM and then flash it to the inactive partition, right? I've been using the tools here to flash, so there are two scripts - one to write to partition A and one to write to partition B. Do you have any specific suggestions on what I should do to corrupt it - specific file(s) I should delete perhaps, that would guarantee it fails?
Also, to check which slot is inactive, according to this doc, it seems I should run:
fastboot getvar all | grep “current-slot”
Do I have to put my phone in EDL mode to do that, or can I run fastboot without EDL mode. I'm worried that if I put my phone in EDL mode, when I exit out of it, it will reboot. So I'll be past the point of no return.
Click to expand...
Click to collapse
I never had ZTE phones, so can't really be sure about the flashing process.
You don't need to corrupt the whole ROM, you can rather just corrupt the boot partition of the inactive slot with update. Or even just flash a wrong version of boot partition into that inactive slot can corrupt it as well.
Either
Code:
fastboot flash boot_a wrong_boot_file.img
Or
Code:
fastboot flash boot_b wrong_boot_file.img
The corrupt can be done with root or in fastboot, EDL should be not needed.
About which slot is inactive, since your case is complicated that it's going to do an update, the fastboot command to check inactive slot is hard to distinguish.
You may need to use rather command
Code:
fastboot getvar all
It will show like this:
With this, you will be able to see the system version.
eg. ro.build.version (find the correct one yourself, I don't know this phone.)
Before power off, you first find out your current version, so then in fastboot, you check if it's the same as read from fastboot.
Hi friends,
Since yesterday, my wifi and bluetooth don't work anymore. When enabling them, it scans nothing . I've made a factory reser without any psuccess !
Never seen an issue like this on any phone...
Thanks for your help guys
Have you tried restarting the phone? I had 1 time yesteday too, suddenly, the phone was idle, and when I checked Wifi found nothing. Restarted and then it works again. Not sure if related to March update or some other stuffs
creezalird said:
Have you tried restarting the phone? I had 1 time yesteday too, suddenly, the phone was idle, and when I checked Wifi found nothing. Restarted and then it works again. Not sure if related to March update or some other stuffs
Click to expand...
Click to collapse
Restarted and also factory reseted
YassGo said:
Restarted and also factory reseted
Click to expand...
Click to collapse
Wow...after a factory reset, that's pretty much it!
You can try doing the reset network settings button (you can search it in the search bar in Settings or find it in the Internet setting on top right button [wrench and reset circle]), but I can't imagine it doing better than a factory reset.
The best/last thing that can be suggested, since it states you are rooted in your sig, is to flash the latest Full Factory image (March) and/or with the "-w" intact (since you stated that you did a factory reset so I imagine your phone is wiped anyways) and see if that doesn't fix the issue. The best 3 methods to achieve this is using the online Android Flash Tool, the tool PixelFlasher that can be found here on XDA, or manually using platform-tools (you must've used one of these in the past to be rooted, so I assume you're familiar).
Hopefully you get it figured out. Worst case, the phone is still under manufacturer's warranty and you should be able to get it replaced with a refurbished if it truly isn't resolved...
simplepinoi177 said:
Wow...after a factory reset, that's pretty much it!
You can try doing the reset network settings button (you can search it in the search bar in Settings or find it in the Internet setting on top right button [wrench and reset circle]), but I can't imagine it doing better than a factory reset.
The best/last thing that can be suggested, since it states you are rooted in your sig, is to flash the latest Full Factory image (March) and/or with the "-w" intact (since you stated that you did a factory reset so I imagine your phone is wiped anyways) and see if that doesn't fix the issue. The best 3 methods to achieve this is using the online Android Flash Tool, the tool PixelFlasher that can be found here on XDA, or manually using platform-tools (you must've used one of these in the past to be rooted, so I assume you're familiar).
Hopefully you get it figured out. Worst case, the phone is still under manufacturer's warranty and you should be able to get it replaced with a refurbished if it truly isn't resolved...
Click to expand...
Click to collapse
Yesterday I dirty flashed March update bmand disabled verity stuff. It forced me to format data. Is it enough or is there a better clean flash way ?
Btw I tried the reset network thing without success
YassGo said:
Hi friends,
Since yesterday, my wifi and bluetooth don't work anymore. When enabling them, it scans nothing . I've made a factory reser without any psuccess !
Never seen an issue like this on any phone...
Thanks for your help guys
Click to expand...
Click to collapse
YassGo said:
Yesterday I dirty flashed March update bmand disabled verity stuff. It forced me to format data. Is it enough or is there a better clean flash way ?
Btw I tried the reset network thing without success
Click to expand...
Click to collapse
Mmmm...when you stated you "factory reset", it wasn't clear whether it was from the OS system setting or when flashing...
I don't think there is a "better clean" way to flash and/or reset the phone. If you're not flashing/sideloading OTA (which you aren't)...
It (reset network) was a very long shot, but worth exploring just in case it hadn't been tried yet...
I mean, I guess you can try Android Flash Tool and even go as far as to flash to both slots and relock bootloader to get a pure, stock status and see if the problem truly sticks that way. You've already wiped the phone, so I doubt this could hurt or you lose anything important at this point. But I can't imagine dirty flashing the latest March update (or even including disabling the verity stuff) wouldnt've addressed or reset things to set the issue straight...
If it's still there after relocking the bootloader and flashing to both slots, then it's warranty exchange time (if you ever want to resolve the issue)...
*most likely the flashing somehow wrecked the system board radio enough...
If/When this works, you'll need go through the trouble of unlocking the bootloader, and reflashing the Full Factory image with disabling the verity & validation stuff, before rooting again.
Ok I think it's a hardware problem. When I shake my phone, I hear something moving.
I dropped it from my bed saturday night. The wifi module must be disconnected.
Let's send it to Google....
YassGo said:
Ok I think it's a hardware problem. When I shake my phone, I hear something moving.
I dropped it from my bed saturday night. The wifi module must be disconnected.
Let's send it to Google....
Click to expand...
Click to collapse
Are you sure that what you are hearing move when you shake the phone is just the OIS for the camera? All phones with OIS will make some noise when you shake them.
jaseman said:
Are you sure that what you are hearing move when you shake the phone is just the OIS for the camera? All phones with OIS will make some noise when you shake them.
Click to expand...
Click to collapse
I don't know my friend. Google will send me the return process tomorrow. They told me 7 to 10 days for repairing. Why did I sell my old oneplus ?
YassGo said:
I don't know my friend. Google will send me the return process tomorrow. They told me 7 to 10 days for repairing. Why did I sell my old oneplus ?
Click to expand...
Click to collapse
I have had several OnePlus phones and they have all been great for me! However, I am having no problems with my 7 Pro either so....YMMV