How to be on N modem? And how to check whether, I am on N modem or M modem?
Bunny 2886 said:
How to be on N modem? And how to check whether, I am on N modem or M modem?
Click to expand...
Click to collapse
Check your baseband version, if it's ending in .52R (Nougat soak test, Oct 2016 security patch), .60R (Nougat v7.0, Nov 2016 security patch) or. 62R ( v7.0, Dec 2016 or March 2017 security patches), you're on a Nougat modem. If your baseband is. 48R or a lower version, then you're likely on marshmallow. If you're on a G4, you may not see much difference updating to the N modem if you're using a custom ROM, however for G4 plus devices you will have issues with the fingerprint sensor if you're on a MM modem with a Nougat based custom ROM.
If you want to update to the. 62R modem (the latest version we have), your best best is to flash the stock fastboot ROM. Be aware to back up your data beforehand and move your back up off your device if possible https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
I am on .62R and using the latest package NPJS25.93-14-4. But, I am still facing the fingerprint enrollment issue, can you help me on this?
Bunny 2886 said:
I am on .62R and using the latest package NPJS25.93-14-4. But, I am still facing the fingerprint enrollment issue, can you help me on this?
Click to expand...
Click to collapse
I take it you're on the stock ROM? What device are you running?
What do you mean by fingerprint enrolment issue, as in you can't get more than one fingerprint registered or are you referring to the ghost fingerprint issue as you posted previously? https://forum.xda-developers.com/moto-g4-plus/help/fingerprint-enrollment-issue-t3590634
Xt1643 and that ghost enrollment issue.
Bunny 2886 said:
Xt1643 and that ghost enrollment issue.
Click to expand...
Click to collapse
I'm having difficulty finding reports for others that have had that particular issue (it's usually been users trying to register more than one fingerprint, then having a enrolment error, but the fingerprint is recorded and usable).
I guess you've tried the usual wipe cache/Dalvik and/or a factory reset (of course, back up your data), does the issue still persist?
If it does still persist after a factory reset, then perhaps a re-flash of the firmware is required, is your bootloader locked or unlocked?
No, my bootloader is locked!
Bunny 2886 said:
No, my bootloader is locked!
Click to expand...
Click to collapse
Do you see this issue when you factory reset (if you did that)?
Hmm, in which case if a factory reset doesn't work (by wiping out your existing fingerprint records, then you start fresh), you could take your device to a service centre to re-flash the firmware, see if that fixes the issue (might be a dodgy flash of the modem). With a locked bootloader our options are limited and anything else may require unlocking your bootloader (even downgrading to 93-14) and thus voiding your warranty.
The other way is to ignore the ghost fingerprints (provided they are of your fingerprints), do you still see them listed if you reboot or do a cache/Dalvik wipe?
Yeah, it still persist. I did a factory reset.
Bunny 2886 said:
Yeah, it still persist. I did a factory reset.
Click to expand...
Click to collapse
That suggests an issue with your firmware or device, which a service centre will be able to help you with. I'd suggest asking them to help you with a re-flash, and if that doesn't solve it, perhaps a warranty repair (if you're willing to go down that route).
Related
Hey guys, I am facing a weird problem.
I was running the January patch, rooted with magisk, but I was facing some problems so I decided to return to the December Oreo patch.
I flashed the official patch (xiaomi firmware site) and I did a clean flash but after I flashed it when my phone booted it wouldn'1 detect my sim card and it reboots every minute and it's unusable because it keeps rebooting.
I tried flashing the January patch again but the same problem remained and it wasn't fixed.
I tried returning to the Nougat but when I flash the official firmware image, my phone enters a bootloop and doesn't start.
I don't know what caused this problem but I need help.
Update: wifi doesn't work either.
Try to flash the .18 nougat build with miflash, if I remember right it maybe could fix your issue. Nothing to loose anyway and do a clean flash.
Flash persist.img from August build, I'm sure it'll work.
Mazen Amr said:
Admin Note: This is a special Q&A-formatted thread. Please follow this link to view it in your browser: http://xda.tv/post75251443
Click to expand...
Click to collapse
https://forum.xda-developers.com/mi-a1/help/mi-a1-imei-lost-phone-restart-t3735440/page3
My brother has a RETIN Athene running stock ROM with latest April patch and he's been complaining about frequent ghost touches. He'd often find his phone call, text someone at random, apps opening automatically and what not. I've suggested him to do a factory reset but I'd like to know if this can be solved without a factory reset. I had already unlocked his bootloader earlier to let him try a custom ROM as the stock was getting sluggish so if needed, a fastboot ROM can be flashed as well if it comes to that.
He recently got a QC 3.0 charger from Motorola but the problem has been going on before that (if he recalls correctly). Could this be because of the charge as I remember his G4 plus had some occasional ghost touches when his phone was new but that only happened while it was being charged.
I'm open to any advice and tips. His phone is barely usable now.
Update: I did a cache wipe from recovery a few minutes ago and noticed that his recovery was showing the the following info:
oem_locked
Software status: Official
Maybe I relocked the bootloader when flashing stock back then. Do I need to unlock bootloader again with "fastboot oem unlock"?
Ghost touch is no software issue. It is hardware. There is no solution. Just do not use your phone under sunset, and what about brightness - change to automatic, or if you wanna no automatic make less brightness 1/3-1/5 point. But again not use under sun
Edit: you can not relock bootloader if you already unlocked it. And if bootloder is unlocked, do not use ota updates (any: security and os). if you do, your phone will be bricked again
gioyocho said:
Ghost touch is no software issue. It is hardware. There is no solution. Just do not use your phone under sunset, and what about brightness - change to automatic, or if you wanna no automatic make less brightness 1/3-1/5 point. But again not use under sun
Edit: you can not relock bootloader if you already unlocked it. And if bootloder is unlocked, do not use ota updates (any: security and os). if you do, your phone will be bricked again
Click to expand...
Click to collapse
I see... I'll tell him to change the brightness to auto. Do you think upgrading to a new phone is better and the only available solution?
Also, after I flashed the fastboot ROM a while ago, he has updated to all the following OTAs without any issues, that's how he's on the April patch. No hard brick, nothing.
gioyocho said:
Ghost touch is no software issue. It is hardware. There is no solution. Just do not use your phone under sunset, and what about brightness - change to automatic, or if you wanna no automatic make less brightness 1/3-1/5 point. But again not use under sun
Edit: you can not relock bootloader if you already unlocked it. And if bootloder is unlocked, do not use ota updates (any: security and os). if you do, your phone will be bricked again
Click to expand...
Click to collapse
You can relock your bootloader. And the bricking kicks in only if you flash OTAs when rooted or on a custom recovery. Generally when you have system modifications.
corlatemanuel said:
You can relock your bootloader. And the bricking kicks in only if you flash OTAs when rooted or on a custom recovery. Generally when you have system modifications.
Click to expand...
Click to collapse
Well, no system modifications were done. That's why the OTAs were successful
I have a phone that after installing the June security patch no longer works unless in airplane mode. WiFi works but if you enable the cell service the phone will crash as soon as it establishes connection to the cell network.
I have tried to reset cache and have run a factory reset.
Is there a way to reflash the update to possibly correct the problem?
Will installing a custom ROM resolve my problem?
zeroibis said:
I have a phone that after installing the June security patch no longer works unless in airplane mode. WiFi works but if you enable the cell service the phone will crash as soon as it establishes connection to the cell network.
I have tried to reset cache and have run a factory reset.
Is there a way to reflash the update to possibly correct the problem?
Will installing a custom ROM resolve my problem?
Click to expand...
Click to collapse
If bootloader unlocked, try flashing stock ROM from TWRP. Our device has one such thread for the same. If that's working well, go with any custom ROM. If bootloader not unlocked, take risk, it's mostly safe though, and unlock it.
Kaiwalya said:
If bootloader unlocked, try flashing stock ROM from TWRP. Our device has one such thread for the same. If that's working well, go with any custom ROM. If bootloader not unlocked, take risk, it's mostly safe though, and unlock it.
Click to expand...
Click to collapse
Ok, I will attempt to unlock the boot loader and then I assume that I follow instructions in this thread: https://forum.xda-developers.com/g4-play/development/fxz-harpia-twrp-flashable-fastboots-t3554840
I finally give up. I had lineage 15.1 running on the device and decided to upgrade to a pie based rom. So I flashed november firmware, rom etc. then I only had 3g. Now I decided maybe I need to flash latest december firmware so I flashed the 10.0.3 firmware zip and lost my sim card completely. I reflashed the november firmware. This made the device bootloop so I decided to flash stock november rom again and start all over. Now it's independent of the rom it's running it boots until the sim pin dialog, i can even press some numbers but it just reboots after a certain amount of time. Access to fastboot works fine so any idea how I could fix this would be greatly appreciated.
Looks like you got a corrupted EFS partition. If you have a TWRP backup for that, just restore. And if you don't, there is a thread in the Mi A1 forum about restoring EFS when downgrade from Pie.
Benjamin_L said:
I finally give up. I had lineage 15.1 running on the device and decided to upgrade to a pie based rom. So I flashed november firmware, rom etc. then I only had 3g. Now I decided maybe I need to flash latest december firmware so I flashed the 10.0.3 firmware zip and lost my sim card completely. I reflashed the november firmware. This made the device bootloop so I decided to flash stock november rom again and start all over. Now it's independent of the rom it's running it boots until the sim pin dialog, i can even press some numbers but it just reboots after a certain amount of time. Access to fastboot works fine so any idea how I could fix this would be greatly appreciated.
Click to expand...
Click to collapse
First of all try to disable SIM Pin Lock from another phone. It was a bug from previous releases.
Second: never downgrade from Pie because it will causes issues and potential corruption.
jack_21 said:
First of all try to disable SIM Pin Lock from another phone. It was a bug from previous releases.
Second: never downgrade from Pie because it will causes issues and potential corruption.
Click to expand...
Click to collapse
But is downgrading from a custom rom comparable? And the firmware zips only have modems and bootloaders don't they? I am always struck how difficult the a1 is compared to my pixel 2
Benjamin_L said:
But is downgrading from a custom rom comparable?
Click to expand...
Click to collapse
Well, you upgraded to 10.0.3.0 so you must use only that Pie firmware for now
Hy,
December Update out now.
Greets
got it too, can't see any fixes though. on the plus side they dont seem to have broken anything either. can call this a "win" i guess
Wondering if people stuck on September version can finally update without resetting data.
Please let us know if you're in this group.
laviniu_c said:
got it too, can't see any fixes though. on the plus side they dont seem to have broken anything either. can call this a "win" i guess
Click to expand...
Click to collapse
I would say the same. Can't expect anything better than this from these system updates.
until when mi a2 will receive updates? will this be the last?
Mi A1 was released with August 2017 security patch and received its last update on August 2020, something similar should happen for Mi A2 too.
birdflesh said:
Mi A1 was released with August 2017 security patch and received its last update on August 2020, something similar should happen for Mi A2 too.
Click to expand...
Click to collapse
thanks for the info! Mi A2 security patches until Aug 2021 (Mi A2 release August 2018)
Since that update my battery drains way faster.
Since that update my battery drains way faster.
+1
I'm still in the September update.
Has anyone with the bootloader unlocked updated their phone? If yes, what were your steps to update it?
ota should work with an unlocked bl, IF you have not changed the system. unlocking means you could change it, it doesnt in itself deny ota updates
salmonthefish said:
I'm still in the September update.
Has anyone with the bootloader unlocked updated their phone? If yes, what were your steps to update it?
Click to expand...
Click to collapse
I´m also waiting for anyone that reported that made the update. I have Setember Update with bootloader unlocked because of camera2api, i don´t made any system changes, and i get all the updates until september without problemes. After that i get Bootloop on October and don´t update anymore. If anyone upgrade from setember with sucess please report.
ki69 said:
because of camera2api
Click to expand...
Click to collapse
you answered your own question. if you've unlocked AND made ANY changes to the system ota can bootloop ofcourse.
With unlocked bootloader factory reset is needed once and only once when updating from any version < 11.0.15.0 (October patch) to any version >=11.0.15.0 regardless of update method (OTA or fastboot reflashing). I suspect that Xiaomy made breaking changes to /vendor and/or other system partitions in 11.0.15.0.
So if you want to fastboot flash 11.0.19.0 over 11.0.14.0 or 11.0.5.0 you will need to make factory reset or just flash with "flash_all.bat/sh".
I've seen reports here that factory reset was also required on fully stock phones when receiving 11.0.15.0 October OTA, and I am really sorry for those users, as they had no chance to update with full recovery of user data.
Those having unlocked bootloader can make full recovery of user data after reset using TWRP backup of /data partition, guide is here:
October 2020 Security Update now available
October Security Update just released today.
forum.xda-developers.com
Aerobatic said:
With unlocked bootloader factory reset is needed once and only once when updating from any version < 11.0.15.0 (October patch) to any version >=11.0.15.0 regardless of update method (OTA or fastboot reflashing). I suspect that Xiaomy made breaking changes to /vendor and/or other system partitions in 11.0.15.0.
So if you want to fastboot flash 11.0.19.0 over 11.0.14.0 or 11.0.5.0 you will need to make factory reset or just flash with "flash_all.bat/sh".
I've seen reports here that factory reset was also required on fully stock phones when receiving 11.0.15.0 October OTA, and I am really sorry for those users, as they had no chance to update with full recovery of user data.
Those having unlocked bootloader can make full recovery of user data after reset using TWRP backup of /data partition, guide is here:
October 2020 Security Update now available
October Security Update just released today.
forum.xda-developers.com
Click to expand...
Click to collapse
Thank you.
A question, if i unlock the bootloader afterwards will the same issue pop up again?
salmonthefish said:
A question, if i unlock the bootloader afterwards will the same issue pop up again?
Click to expand...
Click to collapse
I believe neither Xiaomi nor Google can answer this question.
Anyway,
1) right now factory reset for unlocked MiA2 is needed only once when updating from any previous ROM version to any currently available ROM version >= 11.0.15.0;
2) having unlocked phone one is sure that his data can be restored in any future mishap;
3) unfortunately unlocked phone prevents usage of most of banking apps unless Magisk + Riru + edXposed installed with MagishHide On and GooglePlayServices in Blocked List (SafetyNet issue).
So everyone decides himself whether to
a) keep phone untampered (with risk of loosing data with next OTA bootloop),
b) or unblock phone and then stay with updating stock (spending some time to get root, make SafetyNet passable, remove annoying settings suggestions, customize UI, etc.) ,
c) or unblock phone and then revert to Android 9 10.0.17.0 (disabling updates),
d) or unblock phone and then escape to a Custom ROM.
I personally prefer option (b) since my first Android gadgets (never bought a phone/tablet which had problems with rooting).
19Gerhard85 said:
Since that update my battery drains way faster.
Click to expand...
Click to collapse
19Gerhard85
after updating "Google Find my Device" app battery holds like before all ok now but i never use that app not even logged in calendar app also updated at same time but i don't thin it was calendar