Database Info

GApps not working with CM7 ROM

I installed the CM7 port and the GApps, but my Google apps don't show up. I've tried reflashing the ROM and the GApps package over and over and clearing all the caches to no avail. Help?

you have to flash GAPPS separately. refer original post of CM7 thread and you will find the link

That's what I did. I flashed the ROM then I flashed the GApps, but they're still not showing up.

Ok that's weird. Can you pinpoint the exact steps you performed from download to copying to erasing to booting up? Each and every step please.

Sure thing.
I downloaded the ROM and the GApps package from the ROM's thread and stored the files on my desktop. While the downloads were going, I booted my phone into recovery and mounted the USB storage. I then plugged the phone into my computer and copied the files over before ejecting the USB device and unplugging the phone. I then wiped the user data, the cache, and the Dalvik cache and flashed the ROM, then, straight after, the GApps. I wiped the user data again just to be safe then rebooted back into the OS.
After it didn't work the first time, I downloaded the GApps again and copied them to my phone again, this time within the OS instead of the recovery. Rebooted, wiped user data, cache, and Dalvik cache, flashed the GApps, and nothing.
Not being sure if it was the ROM or the GApps package, I flashed the MIUI beta then flashed the GApps (using the same sequence of steps mentioned above) and it still didn't work, so it doesn't seem to be specific to CM7.

Ok try these steps:
1. Download the ROM
2. Download GApps from here: http://cmw.22aaf3.com/gapps/gapps-gb-20110828-signed.zip
3. Wipe the big 3's (user data, cache and dalvik-cache).
4. Flash the ROM.
5. Flash Gapps.
6. Boot without erasing anything.

I followed your instructions exactly but I still have the same problem.
Interestingly, if I go into the list of installed applications in the settings, Market (but no other Google apps) shows up but it's greyed out and I don't have any options to run it or anything.

dftba said:
I followed your instructions exactly but I still have the same problem.
Interestingly, if I go into the list of installed applications in the settings, Market (but no other Google apps) shows up but it's greyed out and I don't have any options to run it or anything.
Click to expand...
Click to collapse
Crap. Something's really not right. Can you give it a try with the SuperOSR ROM? Need to see if it's specific to the CM build.
EDIT: Can you try searching for the Market .apk file around the forum and install it manually? It should be somewhere in Themes&Apps section. Give that a try before trying with the SuperOSR ROM. Wipe, re-flash ROM, flash Market.apk, reboot.
Reason: the gapps provided by CM team are old (v2 market) and it might be that Google does not support v2 anymore since they've switched to Play Store. (not sure).

I did try with the MIUI ROM and the same thing happened, I don't think it's specific to your ROM build. Perhaps my phone just doesn't like Cyanogen's GApps package? No idea why that would be though.
Anyway, I did as you suggested and installed an APK and it worked! I found this one on Redmond Pie and put in the SD and installed it with the file browser on the phone. Seems to work fine so far

dftba said:
I did try with the MIUI ROM and the same thing happened, I don't think it's specific to your ROM build. Perhaps my phone just doesn't like Cyanogen's GApps package? No idea why that would be though.
Anyway, I did as you suggested and installed an APK and it worked! I found this one on Redmond Pie and put in the SD and installed it with the file browser on the phone. Seems to work fine so far
Click to expand...
Click to collapse
Awesome!

While you're here, a bug I've noticed that's only popped up on your ROM is that, when I turn the phone off, sometimes the orange light stays on and the phone's completely frozen up until I pull the battery. It's only happened twice but I thought it might be something to look into.
Other than that, it's very good! I'm enjoying it, keep up the good work

dftba said:
While you're here, a bug I've noticed that's only popped up on your ROM is that, when I turn the phone off, sometimes the orange light stays on and the phone's completely frozen up until I pull the battery. It's only happened twice but I thought it might be something to look into.
Other than that, it's very good! I'm enjoying it, keep up the good work
Click to expand...
Click to collapse
It's a CWM based problem. Update your CWM recovery to the latest one from the CWM thread in the Dev section and you are good to go.
Way too many CWM's in two sentences..

I'll do that now, cheers

Glad to know you are up and running, but it's still quite strange. Every time I flashed CM7.2 (it it was quite a lot of times GApps were there, Market included. Just running the Market app would actualize it to Play Store automagically.
Of course, as Alex says, it may not be supported by Google anymore, but still you should have gmail, etc from the zip file even without a working Play Store...
The issue was probably related to CWM, if you have an old enough version it could be messing up with the zip internals, but sometimes it's just anything else... (I installed the first CM9 alpha rom w/o problem, the second one wouldn't install, one week later, doing exactly the same with the same zip file, it installed flawlessly)
It may also be related to the specific terminal, I have noticed that depending on the device type (country of release, free or network operator locked, and so on) terminals behave a little bit different in some aspects (e.g. my GPS stopped working after unlocking the bootloader and was only fixed when I reflashed the radio firmware after getting S-OFF; and now, with the CM9 alpha, my keyboard won't get backlight while it's dark outside but adxl's is working fine, which is bad for debugging purposes, of course )
If you could make a backup and install SuperOSR and see if everything works fine the first time (even if you go back to CM afterwards, as I did) it may help to understand the issue better... Or maybe just posting your phone's specific data (model, build, country, etc) may give us a hint.
We know that free UK terminals are somewhat different to Spain free terminals, and those are a bit different from Orange or Yoigo locked terminals... It may be related to hardware batches out fro the factory, who knows?
Enjoy your ChaChaCha!

I think the problem was my CWM in the end. After I upgraded it (that alone included some trial and error, eventually the fastboot method worked) the GApps zips worked fine.
So if anyone else has this problem, check your CWM version and upgrade it if you need to

Can i Upgrade CWM without any change of my current OS ?
i actually couldnt go to Market after i flashed GServices. I downloaded newest Google Play in HTC Chacha apps, installed it and it work until now (of course wit GService flashed before).
Btw, how can i check my current CWM. Thanks!

Similar problem...
dftba said:
I installed the CM7 port and the GApps, but my Google apps don't show up. I've tried reflashing the ROM and the GApps package over and over and clearing all the caches to no avail. Help?
Click to expand...
Click to collapse
Hello there!
I've came by to add my issue, similar to yours.
I was on CM7 too and wanted to try the SuperOSR ROM. I used the common steps for flash it (all cache Wiping and factory reseting, ROM installing, Gapps installing), rebooting my phone, connect it with a Google account, launched Gmail and then when I've arrived at a certain level of my mails, the app crash...
For the Google Play app, I've got a server connexion error...
It's like if all the Google's framework was here but totally not stable...
I've tried with an another ROM, the MUI ROM and everything works...
Like I said, I came from the CM7 ROM wich was working...
Alex C. said:
Ok try these steps:
1. Download the ROM
2. Download GApps from here: http://cmw.22aaf3.com/gapps/gapps-gb-20110828-signed.zip
3. Wipe the big 3's (user data, cache and dalvik-cache).
4. Flash the ROM.
5. Flash Gapps.
6. Boot without erasing anything.
Click to expand...
Click to collapse
I thinks I will try to do those steps and if it does not work...
dftba said:
I did try with the MIUI ROM and the same thing happened, I don't think it's specific to your ROM build. Perhaps my phone just doesn't like Cyanogen's GApps package? No idea why that would be though.
Anyway, I did as you suggested and installed an APK and it worked! I found this one on Redmond Pie and put in the SD and installed it with the file browser on the phone. Seems to work fine so far
Click to expand...
Click to collapse
... this one.

After that you can install from market any google app you want (talk, search, etc.).

Alex C. said:
After that you can install from market any google app you want (talk, search, etc.).
Click to expand...
Click to collapse
Strange... Was not working when I flashed the Gapps but worked when I've only flashed the ROM...

Alex C. said:
Ok try these steps:
1. Download the ROM
2. Download GApps (your link)
3. Wipe the big 3's (user data, cache and dalvik-cache).
4. Flash the ROM.
5. Flash Gapps.
6. Boot without erasing anything.
Click to expand...
Click to collapse
Hi, I registered in this forum just to say THANK YOU SO MUCH! I was searching for that appropriate GApps for the CM7 I installed previously with the GApps for Ginger Bread (not the same with this link you posted) and it gave me a headache too. I tried flashing for 3x & the Gapps were not working. Then I tried this link and VOILA! Now my smile is from ear to ear.. so SALAMAT! (Tagalog word for THANK YOU). I'm from Philippines anyway. I bookmarked this page for future reference. A million thanks to XDA Developers and it's helpful members & thanks for welcoming me even I'm a noob.. :laugh::laugh:

[Q] Curiosity: My N5 only works with Flyme, FFOS, Sailfish and Ubuntu

First of all sorry for my English....
Flyme OS and the experimental port of Sense are the only android based roms that works on my (i guess) hardware bricked Nexus 5 (moisture maybe); Sailfish, B2G and Ubuntu Touch works too (everythig that can work), but the stock rom and other android based roms screen locks as soon configuration starts (usually touching in "next" after selecting language) and the power button no longer unlocks. I'm trying to find the differences between Flyme and other Roms, especially in the framework-res.apk, to port this to a stock or cm rom (on which is based flyme) but I'm a little lost...
Flyme Os is stable and daily use, the only error message that it shown when boot is "cannot load native library cpu arch invalid for this build", but then use it normally
Thanks in advance, for any idea

Have you tried flashing stock with fastboot?

Yes, of course, in every way, even with the flashtool lg and factory original image .tot and D820 DLL (process that also closes the bootloader)...

So you've done this... With fastboot?
http://forum.xda-developers.com/showthread.php?t=2513701
And what errors did you get?

KJ said:
So you've done this... With fastboot?
http://forum.xda-developers.com/showthread.php?t=2513701
And what errors did you get?
Click to expand...
Click to collapse
Yes, same error: the screen locks when i touch "next" in language selection and no longer responds.

So fastboot installed everything without error?
Just wanna be sure you successfully installed stock. Which image did you use?

KJ said:
So fastboot installed everything without error?
Just wanna be sure you successfully installed stock. Which image did you use?
Click to expand...
Click to collapse
yes, entire process without error
I use any official found in https://developers.google.com/android/nexus/images

So after flashing stock, it freezes during setup? Very strange. I can only guess that those other OS's messed up your partitions.
I'm not sure what else you can try. Did you fastboot erase system, user data and cache first?
And have you asked others in the threads for those oddball OS's if they had issues like yours?

KJ said:
So after flashing stock, it freezes during setup? Very strange. I can only guess that those other OS's messed up your partitions.
I'm not sure what else you can try. Did you fastboot erase system, user data and cache first?
And have you asked others in the threads for those oddball OS's if they had issues like yours?
Click to expand...
Click to collapse
Very strange, yes. I also think it's an issue of partitions, damaged sectors or any where the stock image using to store settings or something...
I asked in a thread Flyme, about major structural changes that i can carry a stock rom, but no response yet

KJ said:
So after flashing stock, it freezes during setup? Very strange. I can only guess that those other OS's messed up your partitions.
I'm not sure what else you can try. Did you fastboot erase system, user data and cache first?
And have you asked others in the threads for those oddball OS's if they had issues like yours?
Click to expand...
Click to collapse
Sorry, i don´t undertand. Such other operating systems were installed once the problem was presented. First the original stock android (from the box, only updated by ota) started having problems, autolock randomly. Then reinstall the factory image (in every way) and still failing so I went back to using my Nexus 4 and began to try other Roms and OS's. Until I arrived at the only functional rom based on android that not autolock, Flyme...

ferozzzz said:
Sorry, i don´t undertand. Such other operating systems were installed once the problem was presented. First the original stock android (from the box, only updated by ota) started having problems, autolock randomly. Then reinstall the factory image (in every way) and still failing so I went back to using my Nexus 4 and began to try other Roms and OS's. Until I arrived at the only functional rom based on android that not autolock, Flyme...
Click to expand...
Click to collapse
What you have is DOA, look at the logs after you installed flyme os and check sd card for errors/repartition (mentioned before). But i would just change the device using DOA warranty. Dont forget to reset the tempered flag afterwards.

nbite said:
What you have is DOA, look at the logs after you installed flyme os and check sd card for errors/repartition (mentioned before). But i would just change the device using DOA warranty. Dont forget to reset the tempered flag afterwards.
Click to expand...
Click to collapse
Its not DOA, it works for over 7 months, I think that are bad sectors
attached logcat

Im not sure whats happening but it looks like your lollipop preview isnt booting with multirom. I can see the i/o error but im not sure whats causing it.
sd 0:0:0:0: [sda] Unhandled error code looks like drive is failing. Also some wifi problems but dont think thats the reason. 70% sure its the drive. Check reformat or replace. Good luck man!

nbite said:
Im not sure whats happening but it looks like your lollipop preview isnt booting with multirom. I can see the i/o error but im not sure whats causing it.
sd 0:0:0:0: [sda] Unhandled error code looks like drive is failing. Also some wifi problems but dont think thats the reason. 70% sure its the drive. Check reformat or replace. Good luck man!
Click to expand...
Click to collapse
Already formatted it, ran e2fsck (with verbose: no bad sectors), I'll wait for the final version of lollipop, if I keep using FlymeOS until I get a motherboard at reasonable price in Argentina

ferozzzz said:
Already formatted it, ran e2fsck (with verbose: no bad sectors), I'll wait for the final version of lollipop, if I keep using FlymeOS until I get a motherboard at reasonable price in Argentina
Click to expand...
Click to collapse
It either the nand or the nand controller or software thats causing bad block (going to stock, flashing everything correctly, reflashing kernel, radio etc). Very little chance of it being a software fault since it persists on different roms. Good luck!

[solved] TWRP shows wierd file names, please help

I've been at this issue for 2 days please can any one determin what is the issue and help? (attached)
it happend right after I tried rr rom then I flashed stock miui again and tried a new clean istall but ever since twrp doesn't show files. so far I learned it is xiaomi encryption thing in vendor image.
hope you guys have sulotion

الحمدلله
I got it,
to whom may face what I severely faced, just flash a developer rom through mi flasher and then you are good to go it is as simple as that!.
may miui die forever !

What happened was your storage was encrypted. TWRP is supposed to ask for your pattern or password when it starts so it can decrypt and read it. I had that issue a couple times where it didn't ask me on some custom roms, not sure why.
Using the new unofficial resurrection remix build now, and you can disable encryption on that.

Just do a format data.

Ezito said:
Just do a format data.
Click to expand...
Click to collapse
That's a negative it will not resolve the issue.

jouid33 said:
That's a negative it will not resolve the issue.
Click to expand...
Click to collapse
Everytime I got this wierd file names, I've done a format data and everything was back to normal. Altough, after the format data there's only TWRP file avaiable.

Encryption Issues

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.

Where can I download A2020U stock Android 9 image?

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.