Related
Hi, I used PwnMyMoto-1.4.3-TMobile.apk to get root on my T-mobile Moto X.
http://forum.xda-developers.com/showthread.php?t=2444957
Today, there was an OTA update that downloaded and said it would install. Now the phone is stuck in a boot loop. It boots OK but about 45 seconds after loading it shuts down and reboots. I'm guessing its because the PwnMyMoto removed the stock recovery or altered it to be unable to install the OTA update. However I guess the phone still sees the downloaded OTA update and wants to install it, so it reboots the phone to try to install.
I can't post in the PwnMyMoto thread because I'm too new to XDA
I have froze the ota apk to try to prevent this
small update. I used the T-mobile bundle here to get stock recovery.img and put that on my phone (because PwnMyMoto removes it) and then the OTA update installed. I guess instead I could have removed the downloaded update if I knew where it was!! After the OTA I lost root
http://sbf.droid-developers.org/ghost_rcica/list.php
emerica243 said:
I have froze the ota apk to try to prevent this
Click to expand...
Click to collapse
what do you mean by this? Can you tell me how to do that?
jackashe said:
what do you mean by this? Can you tell me how to do that?
Click to expand...
Click to collapse
Freezing a particular app can be done using Titanium Backup. Its available for download on play store. Titanium Backup requires root permissions. Freezing an app will leave the app on your phone but it wont work cuz its frozen lol... the app wont be uninstalled. this way if you decide later that you need the app then you can just unfreeze it and use it.
OK, I have TB and I know it supports freeze. I didn't realize you could freeze the OTA capability as a separate program. However given that I already downloaded the update, its too late to freeze.
jackashe said:
small update. I used the T-mobile bundle here to get stock recovery.img and put that on my phone (because PwnMyMoto removes it) and then the OTA update installed. I guess instead I could have removed the downloaded update if I knew where it was!! After the OTA I lost root
http://sbf.droid-developers.org/ghost_rcica/list.php
Click to expand...
Click to collapse
sorry if i or many people would have seeen this earlier we could have stopped you. Always be patient next time because you may have lost root forever now. Not that we know a patch will come through to allow us to maintain root in 4.3, but jcase said he proabbly wouldn't make a rot for 4.3 because it could be a pain and he doens't want to waste any of the exploits he knows of. You could always figure out a way your phone is bad and go exchange it and root again and don't take OTA until someone has figured out something to do to maintain root. It would be worth it for me.
You always have the option to unlock your bootloader with the T-Mobile version. I plan on unlocking the Dev edition I will be buying and then buying a SquareTrade warranty and that will cover any issues I might ever have including breaking/water damage.
jackashe said:
small update. I used the T-mobile bundle here to get stock recovery.img and put that on my phone (because PwnMyMoto removes it) and then the OTA update installed. I guess instead I could have removed the downloaded update if I knew where it was!! After the OTA I lost root
http://sbf.droid-developers.org/ghost_rcica/list.php
Click to expand...
Click to collapse
FSRBIKER said:
You always have the option to unlock your bootloader with the T-Mobile version. I plan on unlocking the Dev edition I will be buying and then buying a SquareTrade warranty and that will cover any issues I might ever have including breaking/water damage.
Click to expand...
Click to collapse
Yup I almost unlocked the boot loader but instead I was able to flash stock recovery. I wish android itself was smart enough to not try to install OTA when recovery was gone. I finally read through the jcase thread and I think I might have been able to delete the downloaded OTA by running:
Code:
fastboot erase cache
fastboot erase userdata
But I didn't try that. I also don't know what exactly that would have erased.
I will certainly look into a SquareTrade warranty!
Argh, I'm having the same problem. I have a Sprint version with unlocked bootloader and PwnMyMoto 1.1. Began after OTA update today. I have about 20 seconds after booting up that I'm able to do things on the phone before it goes into a loop; I've tried uninstalling the camera and disabling the gallery, which I thought were the two things that were updated. Safe mode doesn't work, nor does trying to enter recovery through fastboot. I've even tried factory resetting the phone from settings, but it can't do this before the power-down process begins. I haven't had any success with working through adb and the command prompt on this phone (device not found). At this point, I'm SOL and out of ideas with a bricked phone. Any other ideas?
UPDATE... Tried the fastboot erase cache & userdata; essentially performed a hard reset of device. Not the most convenient thing, but at least I have a working phone now.
so if we freeze updater and ota, we should be covered?
not sure about the other suspect apk with is fota.apk. I rename otacerts.apk as well. I may be a little paranoid about this but bricking is definitely not an option
jayboyyyy said:
sorry if i or many people would have seeen this earlier we could have stopped you. Always be patient next time because you may have lost root forever now. Not that we know a patch will come through to allow us to maintain root in 4.3, but jcase said he proabbly wouldn't make a rot for 4.3 because it could be a pain and he doens't want to waste any of the exploits he knows of. You could always figure out a way your phone is bad and go exchange it and root again and don't take OTA until someone has figured out something to do to maintain root. It would be worth it for me.
Click to expand...
Click to collapse
Yeah, root is great... I guess I'll just have to keep fingers crossed that jcase works on 4.2.2 post OTA but since it hasn't even been pushed to all carriers maybe it won't happen. Yes, I should have NOT gotten the OTA, but once it had downloaded my phone was totally unusable until I restored recovery and it installed itself.
jackashe said:
Yeah, root is great... I guess I'll just have to keep fingers crossed that jcase works on 4.2.2 post OTA but since it hasn't even been pushed to all carriers maybe it won't happen. Yes, I should have NOT gotten the OTA, but once it had downloaded my phone was totally unusable until I restored recovery and it installed itself.
Click to expand...
Click to collapse
Curious have you tried to reroot, and for future reference I believe ota are usually in cache under the previous build # for Verizon at least.
shane1 said:
Curious have you tried to reroot, and for future reference I believe ota are usually in cache under the previous build # for Verizon at least.
Click to expand...
Click to collapse
I did try rooting again using PwnMyMoto-1.4.3-TMobile.apk but it failed to install (since one of the exploits it used is patched)
I have t-Mobile but how would I get to the cache? My phone would boot for about 45 seconds and in that time-frame I could adb shell into the phone but could not find the path for the OTA update. Do you mean it would be in /cache/some-build/ or so?
Yes in cache and you would have to attempt from a PC , which might not have been possible because the phone kept rebooting. Also I am sry for your loss
Would ota root keeper do anything for us?
Sent from my XT1058 using XDA Premium 4 mobile app
IncredibleHulk6 said:
Argh, I'm having the same problem. I have a Sprint version with unlocked bootloader and PwnMyMoto 1.1. Began after OTA update today. I have about 20 seconds after booting up that I'm able to do things on the phone before it goes into a loop; I've tried uninstalling the camera and disabling the gallery, which I thought were the two things that were updated. Safe mode doesn't work, nor does trying to enter recovery through fastboot. I've even tried factory resetting the phone from settings, but it can't do this before the power-down process begins. I haven't had any success with working through adb and the command prompt on this phone (device not found). At this point, I'm SOL and out of ideas with a bricked phone. Any other ideas?
UPDATE... Tried the fastboot erase cache & userdata; essentially performed a hard reset of device. Not the most convenient thing, but at least I have a working phone now.
Click to expand...
Click to collapse
Can you please tell me how you did this? Thanks in advance
Perhaps this thread helps http://forum.xda-developers.com/showthread.php?p=46179190#post46179190
Erk, after getting into the same post-Root update loop, I flashed back to stock using the recipe here: http://forum.xda-developers.com/showthread.php?p=46175635&postcount=8
I now have 13.9.0Q2.X-116-X-17-51 installed.
When I go to System updates to update to the OTA update 13.0Q2.X-116-X-17-54, I get told that I am already updated to the latest version.
Any help would be much appreciated!
jayboyyyy said:
sorry if i or many people would have seeen this earlier we could have stopped you. Always be patient next time because you may have lost root forever now. Not that we know a patch will come through to allow us to maintain root in 4.3, but jcase said he proabbly wouldn't make a rot for 4.3 because it could be a pain and he doens't want to waste any of the exploits he knows of. You could always figure out a way your phone is bad and go exchange it and root again and don't take OTA until someone has figured out something to do to maintain root. It would be worth it for me.
Click to expand...
Click to collapse
manfly9884 said:
Can you please tell me how you did this? Thanks in advance
Click to expand...
Click to collapse
You have to make sure you have downloaded & installed the Android SDK and the latest Motorola Android drivers to your computer. On your phone, shut it down before it has the chance to re-enter the boot loop cycle. Then press the down button simultaneously with the power button for a few seconds and release the down button a split second before releasing the power button. This enters the bootloader (you may have to try it a few times to get it). Plug your phone into the computer and open a command prompt on the computer; type "fastboot erase cache", hit enter, type " fastboot erase userdata" and hit enter. You'll see confirmation in the command prompt and your phone will reboot as factory reset.
A few days ago randomly lost root couldn;t figure out wh. Since I'm pre OTA, I used RSD to reset and then reroot with PwnMyMoto.
Since then when my alarm goes off, the original screen that would pop up that would allow me to either snooze or turn it off simply doesn't appear. The only way I can turn it off is to force stop the clock app.
I'm trying to figure out if I should just use RSD again and root or it is time to change to the most recent root method anounced. Are there any disadvantages to the new root method? Has anyone had anything weird like this happen to them?
Icon000 said:
A few days ago randomly lost root couldn;t figure out wh. Since I'm pre OTA, I used RSD to reset and then reroot with PwnMyMoto.
Since then when my alarm goes off, the original screen that would pop up that would allow me to either snooze or turn it off simply doesn't appear. The only way I can turn it off is to force stop the clock app.
I'm trying to figure out if I should just use RSD again and root or it is time to change to the most recent root method anounced. Are there any disadvantages to the new root method? Has anyone had anything weird like this happen to them?
Click to expand...
Click to collapse
this has nothing to do with the root method. it is something going on when you restore to factory stuff. redownload the fxz, make sure its the right one (carrier, version, etc.) and then make sure rsd actually finishes everything it is trying to do.
Is there a way to verify that is has done everything it is trying to do? I have restored with this file before and I had no previous issues.
jayboyyyy said:
this has nothing to do with the root method. it is something going on when you restore to factory stuff. redownload the fxz, make sure its the right one (carrier, version, etc.) and then make sure rsd actually finishes everything it is trying to do.
Click to expand...
Click to collapse
Icon000 said:
Is there a way to verify that is has done everything it is trying to do? I have restored with this file before and I had no previous issues.
Click to expand...
Click to collapse
it would show something failed if something failed. But maybe it just got sent yo your phone improperly or something. The only reason i say this is the case, is because there is no chance it was the root exploit, maybe something you did during that exploit or after but not the exploit itself. No one else is having this issue, so it is most likely something you did and not something that is an actual bug. If the only thing oyu did was restore your phone with rsdlite, then something prob errored during this restore. It is a software issue, so the fact that you have the problem but i haven't seen it reported any where else ever, probably means its something you did to your phone incorrectly.
I rooted once upon a time using Kingo Root. Worked fine, love being rooted, been doing it for years. But as everyone knows, the GPS signal is really crap on these phones. Mine keeps cutting out randomly.
Lo and behold! KitKat is now available! And among the changes AT&T is bragging about is improved GPS performance. As much as I enjoy being rooted, I need a working GPS a lot more. So I tried installing the OTA update... but it failed. I assume because the device status is listed as "Custom".
So I used Triangle Away, did a full unroot using SuperSU, rebooted... and it still says "Custom". There didn't used to be an open padlock during boot while I was rooted, but now there is, along with the word "Custom". Check the Odin mode, and sure enough it says the system status is "Custom". However Knox flag is still 0x0, and it states I'm running the Samsung Official binary. I've never flashed a ROM on this phone, all I did was root it.
Re-rooted, installed Triangle Away again. It states my system status is "Official" and the flash counter is at 0. However whenever I check the Device status in settings, it always says "Custom". There doesn't appear to be any way to get it back to "Official". Sometimes I can get it to say "Official" for a single boot, but then it always reverts back to "Custom" within a couple minutes whether the phone is rooted or not.
What am I doing wrong?
After unroot, you need to do a factory reset, then boot into your recovery, wipe cache, reboot your phone few times the pad lock and custom logo should go away. I am not sure about the "Device status in settings" showing custom, mine always shows official.
GoremanX said:
I rooted once upon a time using Kingo Root. Worked fine, love being rooted, been doing it for years. But as everyone knows, the GPS signal is really crap on these phones. Mine keeps cutting out randomly.
Lo and behold! KitKat is now available! And among the changes AT&T is bragging about is improved GPS performance. As much as I enjoy being rooted, I need a working GPS a lot more. So I tried installing the OTA update... but it failed. I assume because the device status is listed as "Custom".
So I used Triangle Away, did a full unroot using SuperSU, rebooted... and it still says "Custom". There didn't used to be an open padlock during boot while I was rooted, but now there is, along with the word "Custom". Check the Odin mode, and sure enough it says the system status is "Custom". However Knox flag is still 0x0, and it states I'm running the Samsung Official binary. I've never flashed a ROM on this phone, all I did was root it.
Re-rooted, installed Triangle Away again. It states my system status is "Official" and the flash counter is at 0. However whenever I check the Device status in settings, it always says "Custom". There doesn't appear to be any way to get it back to "Official". Sometimes I can get it to say "Official" for a single boot, but then it always reverts back to "Custom" within a couple minutes whether the phone is rooted or not.
What am I doing wrong?
Click to expand...
Click to collapse
Did you delete system (AT&T) apps?
coolmingli said:
After unroot, you need to do a factory reset, then boot into your recovery, wipe cache, reboot your phone few times the pad lock and custom logo should go away. I am not sure about the "Device status in settings" showing custom, mine always shows official.
Click to expand...
Click to collapse
Yep, I did all of that. Exact procedure:
- Reset flash counter using triangle away
- full unroot using SuperSU
- reboot immediately into Odin mode (system status says "Official")
- reboot immediately into recovery, do a factory reset
- reboot immediately into Odin mode (system status still says "Official")
- reboot immediately into recovery, do ANOTHER factory reset (because I'm anal that way)
- reboot immediately into Odin mode, (system status STILL says "Official")
- reboot normally, go through normal first-time setup, go into settings, check Device status... it says "Custom"
- reboot into Odin mode, system status now says "Custom"
- reboot normally, stupid open padlock is there again with the word "Custom"
- countless reboots later, it still says "Custom"
serpent2005 said:
Did you delete system (AT&T) apps?
Click to expand...
Click to collapse
Nope, none. They're all still there. Like I said, I'm still running the bone stock image, never flashed a ROM, and I never edited the image. I only use root for things like GMD S-pen control, Titanium Backup, and FS Trim.
What's really annoying is that damn open padlock is never there while the system really IS modified, it only shows up when I unroot and everything is back to stock. I call it irony.
Would region lock be affecting this? I disabled the region lock many moons ago using RegionLock Away. Does that survive after a factory reset, and would it cause my device status to show up as Custom?
Nope, restoring the region lock did not fix the problem. It continues to revert to "Custom" Device status no matter what I try. This is infuriating.
GoremanX said:
Nope, restoring the region lock did not fix the problem. It continues to revert to "Custom" Device status no matter what I try. This is infuriating.
Click to expand...
Click to collapse
This is what you need to do
http://forum.xda-developers.com/showthread.php?t=2559715
it fully returns your phone to stock. and you can get your OTAs again at that point.
the2rrell said:
This is what you need to do
http://forum.xda-developers.com/showthread.php?t=2559715
it fully returns your phone to stock. and you can get your OTAs again at that point.
Click to expand...
Click to collapse
I tried that too. Didn't work. Still says "Custom". However, part of those instructions failed for me, the Heimdall image upload did not work at all. Never could figure out why.
GoremanX said:
I tried that too. Didn't work. Still says "Custom". However, part of those instructions failed for me, the Heimdall image upload did not work at all. Never could figure out why.
Click to expand...
Click to collapse
they work, it maybe your PC, i know Heimdall can be a bugger at times. It DOES work though. have you tried another PC if that is an option.
the2rrell said:
they work, it maybe your PC, i know Heimdall can be a bugger at times. It DOES work though. have you tried another PC if that is an option.
Click to expand...
Click to collapse
I just tried it from my laptop, same result. The MI9_fix.img.ext4 file refuses to upload to my device. The instructions state it should fail at 95%, but it always fails immediately. I tried downloading the file multiple times from different mirrors to make sure I wasn't getting a bad one. The result is always:
Uploading SYSTEM
0%
ERROR: Failed to send file part packet!
ERROR: SYSTEM upload failed!
GoremanX said:
I just tried it from my laptop, same result. The MI9_fix.img.ext4 file refuses to upload to my device. The instructions state it should fail at 95%, but it always fails immediately. I tried downloading the file multiple times from different mirrors to make sure I wasn't getting a bad one. The result is always:
Uploading SYSTEM
0%
ERROR: Failed to send file part packet!
ERROR: SYSTEM upload failed!
Click to expand...
Click to collapse
you have all the drivers and everything loaded up?
thats odd.
Yep, everything called for in the instructions. I get the same result every time.
Did I mention how infuriating this is?
GoremanX said:
Yep, everything called for in the instructions. I get the same result every time.
Did I mention how infuriating this is?
Click to expand...
Click to collapse
Yes but it should work, another member just did the same thing you are trying to do. with success. it has to be drivers or maybe running odin as a admin.
Oh and you may want to move the Odin file to a folder on your desktop or just put them on your desktop and try that. im betting its something simple that we are just over looking.
Finally got it restored to factory. Just about everything that can go wrong did go wrong. My USB cable failed. Then my SD card failed and was spitting out garbage. And one of my downloaded files was corrupted. At one point, I got the status back to "Official", but the phone was so screwed up it was nearly unusable, spitting out error messages every 30 seconds. When this happened, I took it to a local AT&T store hoping they would just flash a new image on there (it did say "Official" in all the right places after all). But all they wanted to do was replace it with a refurb unit. Screw that! So I went home and tried AGAIN, re-downloading everything and using an all new USB wire and SD card, and this time it worked like a charm.
Now I'm attempting to install the OTA update, hopefully all goes according to plan.
Nope, complete failure. Update to NB4 worked fine, but then the update to KitKat failed at 27%. The MJ5 image being used in that thread is not a stock image. It's "fixed" to allow rooting.
Maybe I'll take that refurbished phone from AT&T after all... bastards
GoremanX said:
Nope, complete failure. Update to NB4 worked fine, but then the update to KitKat failed at 27%. The MJ5 image being used in that thread is not a stock image. It's "fixed" to allow rooting.
Maybe I'll take that refurbished phone from AT&T after all... bastards
Click to expand...
Click to collapse
That is stock. It's not prepared for root. You can choose to root or not. I have not updated so I don't know. But if you made it to nb4 why do think it would do that if the mj5 was fixed for root right
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Nah, everyone else in the same situation as me has the exact same problem:
http://forum.xda-developers.com/showthread.php?t=2686652&page=21
We're talking dozens and dozens of attempts by sozens and dozens of people here. Downgrading to the MJ5 image in that restore thread does not actually bring the phone back to stock. The NB4 upgrade apparently just doesn't have the same level of verifying in it as the KitKat update. The author of that thread specifically mentions that the MJ5 image he's listing has been modified to allow rooting using his method, but the rooting part of it is optional. Either way, the image itself has been modified. That's why it has the word "fix" in the filename.
Others have stated that going to an AT&T retail location and having them flash a real MJ5 image DID work, and allowed the KitKat update to happen without issues.
I am having difficulties updating to the newest system update on the stock rom. I am rooted and have unlocked my bootloader, so that may have something to do with it. I am also running on straight talk, but I doubt that would be an issue, as it says it's already downloaded it and it just needs to install it. When I click install now, it turns the phone off, does the little thingy, then reboots. Upon rebooting, everything loads up, and a popup appears saying that the update failed, and then every hour it pops up asking to update. Do you know why this is happening and how to fix it, or a way to permanently suppress this popup?
ace_case said:
I am having difficulties updating to the newest system update on the stock rom. I am rooted and have unlocked my bootloader, so that may have something to do with it. I am also running on straight talk, but I doubt that would be an issue, as it says it's already downloaded it and it just needs to install it. When I click install now, it turns the phone off, does the little thingy, then reboots. Upon rebooting, everything loads up, and a popup appears saying that the update failed, and then every hour it pops up asking to update. Do you know why this is happening and how to fix it, or a way to permanently suppress this popup?
Click to expand...
Click to collapse
You need to be completely stock to take the OTA. If you haven't flashed Mex or Bell, I have a zip, maybe flashable (can't test, broke phone) that contains a completely stock /system. Or you can just backup your apps and flash the stock AT&T fastboot.
Post with link to zip.
skeevydude said:
You need to be completely stock to take the OTA. If you haven't flashed Mex or Bell, I have a zip, maybe flashable (can't test, broke phone) that contains a completely stock /system. Or you can just backup your apps and flash the stock AT&T fastboot.
Post with link to zip.
Click to expand...
Click to collapse
Is there a way to just suppress the update? I am a little wary of flashing etc. after the close call my first time...
ace_case said:
Is there a way to just suppress the update? I am a little wary of flashing etc. after the close call my first time...
Click to expand...
Click to collapse
Yes, you clear the cache. But if you want to leave yourself open to be vulnerable to the Heartbleed bug, a pretty serious security issue, then by all means, leave your front door unlocked so hackers can tap into your device and take anything they want.
palmbeach05 said:
Yes, you clear the cache. But if you want to leave yourself open to be vulnerable to the Heartbleed bug, a pretty serious security issue, then by all means, leave your front door unlocked so hackers can tap into your device and take anything they want.
Click to expand...
Click to collapse
I'd say it's more like posting on Craigslist that you're going on vacation and then leaving all the doors open with your debit/credit card on the coffee table. It's a pretty serious bug, and according to wikipedia, 1.5% of the most popular 800,000 websites are still vulnerable to the bug, not to mention running a sideloaded app or connecting to a malicious website.
got the same issue on one of my atrix hd's but not the other. On mine that I unlocked the bootloader and rooted myself took the ota update but the other which was bought in the same condition will not and just keeps giving an error. trying to figure this out now so will update.
lilred91 said:
got the same issue on one of my atrix hd's but not the other. On mine that I unlocked the bootloader and rooted myself took the ota update but the other which was bought in the same condition will not and just keeps giving an error. trying to figure this out now so will update.
Click to expand...
Click to collapse
Flashing back to completely stock may be the easiest way to get the update.
lilred91 said:
got the same issue on one of my atrix hd's but not the other. On mine that I unlocked the bootloader and rooted myself took the ota update but the other which was bought in the same condition will not and just keeps giving an error. trying to figure this out now so will update.
Click to expand...
Click to collapse
If you flash the OTA update manually using something like Philz recovery, you can see the progress on the screen and where it stops updating. For me, it kept hanging on updating the smartactions.apk, which was because I had previously (long time ago) merged updates of the app to my System partition (along with a few other apps that were updated). This will mess up any attempt to do an OTA update, because your "stock" ROM is no longer stock.
I ended up having to flash back to the real stock with Mythtools, then install the OTA zip manually.
If you can't find the zip in your cache, you can download it directly from this post (thanks @skeevydude): http://forum.xda-developers.com/showpost.php?p=52657363&postcount=13
So last night my face unlocked just stopped working. I deleted my face data and added it again and now it still doesn't work. It just says can't verify face. Anyone else experience this?
sruel3216 said:
So last night my face unlocked just stopped working. I deleted my face data and added it again and now it still doesn't work. It just says can't verify face. Anyone else experience this?
Click to expand...
Click to collapse
Not just spontaneously as you described. It's happened to many ppl but usually immediately after they updated, or tried a custom kernel. If you are unlocked try re-flashing the last image (or probably just boot.img). If not, you could try flashing the latest OTA image via recovery.
v12xke said:
Not just spontaneously as you described. It's happened to many ppl but usually immediately after they updated, or tried a custom kernel. If you are unlocked try re-flashing the last image (or probably just boot.img). If not, you could try flashing the latest OTA image via recovery.
Click to expand...
Click to collapse
Im locked. Never unlocked or rooted. It hasn't worked ever after it stopped last night. Multiple face deletes and re-adds. Also haven't updated since last ota 3 weeks ago.
sruel3216 said:
Im locked. Never unlocked or rooted. It hasn't worked ever after it stopped last night. Multiple face deletes and re-adds. Also haven't updated since last ota 3 weeks ago.
Click to expand...
Click to collapse
...If not, you could try flashing the latest OTA image via recovery. You can find the OTA's and instructions on how to perform a "rescue OTA" on Google's Dev Site. I know it sucks not having FR because it happened to me playing around with a kernel that wasn't updated for December. I got FR back by flashing a different, updated kernel. Let us know what you decide to do and how it turns out. No telling when you will get the next OTA!
v12xke said:
...If not, you could try flashing the latest OTA image via recovery. You can find the OTA's and instructions on how to perform a "rescue OTA" on Google's Dev Site. I know it sucks not having FR because it happened to me playing around with a kernel that wasn't updated for December. I got FR back by flashing a different, updated kernel. Let us know what you decide to do and how it turns out. No telling when you will get the next OTA!
Click to expand...
Click to collapse
Ok il try that thanks!
It's just annoyed cuz my phone has been the same for weeks and never rooted. It began with a notification saying I needed to re-registered my face or it might now work. So I deleted and added and then it's never worked since
v12xke said:
...If not, you could try flashing the latest OTA image via recovery. You can find the OTA's and instructions on how to perform a "rescue OTA" on Google's Dev Site. I know it sucks not having FR because it happened to me playing around with a kernel that wasn't updated for December. I got FR back by flashing a different, updated kernel. Let us know what you decide to do and how it turns out. No telling when you will get the next OTA!
Click to expand...
Click to collapse
I dont understand why i am getting this error:
PS C:\adb> adb sideload flame-ota-qq1b.191205.012.a1-59de0d4d
adb: failed to stat file flame-ota-qq1b.191205.012.a1-59de0d4d: No such file or directory
I have the file in the adb folder where i am launching cmd. adb devices shows my device ID and "sideload"
sruel3216 said:
I dont understand why i am getting this error:
PS C:\adb> adb sideload flame-ota-qq1b.191205.012.a1-59de0d4d
adb: failed to stat file flame-ota-qq1b.191205.012.a1-59de0d4d: No such file or directory
I have the file in the adb folder where i am launching cmd. adb devices shows my device ID and "sideload"
Click to expand...
Click to collapse
Make sure you have the correct image for your device. Flame is for the 4, not 4XL. If that is the correct image for you, most errors are caused by either 1) you are not using the latest adb/fastboot binaries. If you type adb version you should get a return of 29.0.5 (October 2019). or 2) you have multiple versions of adb on your machine and verifying the version as in #1 above will alert you to that. Even if you are in the same folder, if an older version is in your PATH statement it can/will cause issues. Good luck.:good:
PS.. or you forgot to add the ZIP extension in your command? The image is a zipfile and you have to include the entire filename including the file extension. eg. flame-ota-qq1b.191205.012.a1-59de0d4d.zip
v12xke said:
Make sure you have the correct image for your device. Flame is for the 4, not 4XL. If that is the correct image for you, most errors are caused by either 1) you are not using the latest adb/fastboot binaries. If you type adb version you should get a return of 29.0.5 (October 2019). or 2) you have multiple versions of adb on your machine and verifying the version as in #1 above will alert you to that. Even if you are in the same folder, if an older version is in your PATH statement it can/will cause issues. Good luck.:good:
Click to expand...
Click to collapse
Ahh it's prob 2). I have the 4 I just posted in XL cuz there is more activity.
sruel3216 said:
Ahh it's prob 2). I have the 4 I just posted in XL cuz there is more activity.
Click to expand...
Click to collapse
Ah, ok ... just remember the file extension too. Best of luck.
v12xke said:
Ah, ok ... just remember the file extension too. Best of luck.
Click to expand...
Click to collapse
got it to flash. i forgot to add the .zip part when sideloading.
now to see if faceunlock is fixed
Edit: Faceunlock still doesnt work...
is there an app in settings that controls faceunlock that i can clear data/cache and force stop?
sruel3216 said:
got it to flash. i forgot to add the .zip part when sideloading.
now to see if faceunlock is fixed
Edit: Faceunlock still doesnt work...
is there an app in settings that controls faceunlock that i can clear data/cache and force stop?
Click to expand...
Click to collapse
Not that I am aware of... it's the phone security so I'm sure it's encrypted and on the Titan M chip (but I don't know for sure). Some folks have had to do a factory reset to fix the issue, especially if BL locked. Highly unlikely next months OTA will fix your issue. Do you have the option of unlocking? If so, now would seem a good time because you're going to lose your data either way. Anyway, start backing your stuff up and it may be time for a FDR. :crying:
v12xke said:
Not that I am aware of... it's the phone security so I'm sure it's encrypted and on the Titan M chip (but I don't know for sure). Some folks have had to do a factory reset to fix the issue, especially if BL locked. Highly unlikely next months OTA will fix your issue. Do you have the option of unlocking? If so, now would seem a good time because you're going to lose your data either way. Anyway, start backing your stuff up and it may be time for a FDR. :crying:
Click to expand...
Click to collapse
damn it lol. yeah i have the option so i might as well unlock. Il do that tonight i guess. thanks for the help!
my phone wasnt ready for 2020
sruel3216 said:
...my phone wasnt ready for 2020
Click to expand...
Click to collapse
Live and learn. Next time unlock out of the box before setting up. Even if you have no intention of ever rooting, if the "fit hits the shan"- you have more tools (and options) being BL unlocked. Cheers! :good:
v12xke said:
Live and learn. Next time unlock out of the box before setting up. Even if you have no intention of ever rooting, if the "fit hits the shan"- you have more tools (and options) being BL unlocked. Cheers! :good:
Click to expand...
Click to collapse
unlocked and faceunlock works again...for now. hopefully that doesnt happen again. Thanks for the help!
Any idea what got it back going? Mine started repeatedly notifying me last night to update my face recognition data. As soon as I deleted the old data and enrolled again, it stopped working completely. Been broken 100% ever since. Tried reenrolling a couple more times. Reboot. So far no improvement. It just rhythmically flashes 'Can't verify face. Try again.'
fastpakr said:
Any idea what got it back going? Mine started repeatedly notifying me last night to update my face recognition data. As soon as I deleted the old data and enrolled again, it stopped working completely. Been broken 100% ever since. Tried reenrolling a couple more times. Reboot. So far no improvement. It just rhythmically flashes 'Can't verify face. Try again.'
Click to expand...
Click to collapse
This same exact thing happened to me last night. Message on the lockscreen saying to re-enroll my face or it may not unlock. What was funny was that it was able to unlock every time I tried. After re-enrolling, I get the same flashing "Can't verify face. Try again." message. Wonder if there was an A/B test that went out that messed things up. Do you happen to be rooted or have any other modifications?
Tried flashing a few different kernels to see if anything would change. I'm away from my computer for another week so I can't try reflashing images. Booting into safe mode did not work. Uninstalling Magisk did not work either.
sruel3216 said:
Im locked. Never unlocked or rooted. It hasn't worked ever after it stopped last night. Multiple face deletes and re-adds. Also haven't updated since last ota 3 weeks ago.
Click to expand...
Click to collapse
Same boat (locked and stock - Verizon....tried to BL unlock when first turning on phone (removed SIM as to not activate) but that didn't work so locked it is). 2 days ago got the android notification to update my face data so I deleted it and went to re add and nothing but the cannot verify face try again messages. I just deleted face data and use my fitbit to smart unlock for now until this gets fixed to avoid having to repeatedly type my PIN in. To note I did the December update back in early December so it's odd that this has now reared it's ugly head.
Seems to have happened to a lot of people after the new year. Y2K bug twenty years later perhaps? lol
tysj said:
This same exact thing happened to me last night. Message on the lockscreen saying to re-enroll my face or it may not unlock. What was funny was that it was able to unlock every time I tried. After re-enrolling, I get the same flashing "Can't verify face. Try again." message. Wonder if there was an A/B test that went out that messed things up. Do you happen to be rooted or have any other modifications?
Click to expand...
Click to collapse
Yep, that's precisely how mine is behaving. I'm 100% stock.
The same just happened to me the last evening. Suddenly that message popped in and when I tried to delete and re-add the face unlock it completely stopped working. Pretty sure there is some Google A/B testing going on.
People reported factory reset should be the only way to fix this, so I'm gonna wait till tomorrow for the new security patches.
bakemcbride21 said:
Same boat (locked and stock - Verizon....tried to BL unlock when first turning on phone (removed SIM as to not activate) but that didn't work so locked it is). 2 days ago got the android notification to update my face data so I deleted it and went to re add and nothing but the cannot verify face try again messages. I just deleted face data and use my fitbit to smart unlock for now until this gets fixed to avoid having to repeatedly type my PIN in. To note I did the December update back in early December so it's odd that this has now reared it's ugly head.
Seems to have happened to a lot of people after the new year. Y2K bug twenty years later perhaps? lol
Click to expand...
Click to collapse
fastpakr said:
Yep, that's precisely how mine is behaving. I'm 100% stock.
Click to expand...
Click to collapse
TENN3R said:
The same just happened to me the last evening. Suddenly that message popped in and when I tried to delete and re-add the face unlock it completely stopped working. Pretty sure there is some Google A/B testing going on.
People reported factory reset should be the only way to fix this, so I'm gonna wait till tomorrow for the new security patches.
Click to expand...
Click to collapse
yup pretty annoying. think factory reset is the only fix