[Edit 4/4/2015]: Solved: Apparently the previous owner installed a custom kernel (without changing the kernel version) in order to disable encryption. Fixed via unlocking/wiping/rooting/installing a 5.1 ROM from XDA, and setting up my phone again from scratch. Thank you to everyone who posted. See this post for my process.
-------------------------
Original post:
The picture explains all.
http://i.imgur.com/C9GhN3y.jpg
Paul22000 said:
The picture explains all.
http://i.imgur.com/C9GhN3y.jpg
WHAT in the F!!!!!!!!!!!!????????????????
Click to expand...
Click to collapse
This is the second time I've, personally, seen this reported. Was your device purchased from T-Mobile or another source?
Paul22000 said:
The picture explains all.
http://i.imgur.com/C9GhN3y.jpg
WHAT in the F!!!!!!!!!!!!????????????????
Click to expand...
Click to collapse
if you have changed any system files, any at all, then you cant flash the ota, not even if you sideload it.
simms22 said:
if you have changed any system files, any at all, then you cant flash the ota, not even if you sideload it.
Click to expand...
Click to collapse
He couldn't have changed any system files. He's not rooted.
---------- Post added at 02:53 PM ---------- Previous post was at 02:53 PM ----------
Paul22000 said:
The picture explains all.
http://i.imgur.com/C9GhN3y.jpg
WHAT in the F!!!!!!!!!!!!????????????????
Click to expand...
Click to collapse
Which drivers are you using. Are you using mfastboot for sideload. I've heard that works better.
Evolution_Freak said:
This is the second time I've, personally, seen this reported. Was your device purchased from T-Mobile or another source?
Click to expand...
Click to collapse
I purchased it from Amazon in "Like New" and "Perfect condition", which indeed it was. I've been using it for a month now without a single issue whatsoever.
A) What does the above error message mean, and how can I install 5.1 without wiping?
Edit: B) What was the solution for the other case that you saw this?
simms22 said:
if you have changed any system files, any at all, then you cant flash the ota, not even if you sideload it.
Click to expand...
Click to collapse
I have not changed a single thing. Absolutely nothing. How do I install 5.1 without wiping?
toknitup420 said:
He couldn't have changed any system files. He's not rooted.
---------- Post added at 02:53 PM ---------- Previous post was at 02:53 PM ----------
Which drivers are you using. Are you using mfastboot for sideload. I've heard that works better.
Click to expand...
Click to collapse
Exactly. I haven't changed anything. Recovery is stock as well.
I was using "adb sideload" and I installed the newest drivers straight from Google as of 45 minutes ago. "Adb devices" in recovery was clearly showing my device right before entering the "adb sideload" command.
What is mfastboot? And do you think it will overcome this error?
Paul22000 said:
I purchased it from Amazon in "Like New" and "Perfect condition", which indeed it was. I've been using it for a month now without a single issue whatsoever.
A) What does the above error message mean, and how can I install 5.1 without wiping?
Edit: B) What was the solution for the other case that you saw this?
I have not changed a single thing. Absolutely nothing. How do I install 5.1 without wiping?
Click to expand...
Click to collapse
Here's the link to the other thread:
http://forum.xda-developers.com/showthread.php?t=3069402
What is your current software version? Is it LRX22C or something else? I'm asking because I want to be sure that when you tried to sideload, you used the proper one for the software version you have/want.
---------- Post added at 03:03 PM ---------- Previous post was at 03:02 PM ----------
Also, it is possible that the person who owned it before you made alterations that were not completely removed before you purchased it.
Evolution_Freak said:
Here's the link to the other thread:
http://forum.xda-developers.com/showthread.php?t=3069402
What is your current software version? Is it LRX22C or something else? I'm asking because I want to be sure that when you tried to sideload, you used the proper one for the software version you have/want.
---------- Post added at 03:03 PM ---------- Previous post was at 03:02 PM ----------
Also, it is possible that the person who owned it before you made alterations that were not completely removed before you purchased it.
Click to expand...
Click to collapse
Yes LRX22C. I used this one: LRX22C to LMY47M for T-Mobile http://android.clients.google.com/p...ed-shamu-ota-LMY47M-from-LRX22C-fullradio.zip
How can I investigate to see what the first owner changed? I don't want to wipe and find out it still doesn't work. And just for my knowledge, I do want to find out exactly what is the cause or changed files.
can always flash the factory img via fastboot, while the device is in its bootloader.
I wonder if this might partly be related to having a T-Mobile SIM and being purchased from Amazon - because the OTA is controlled by the carrier but perhaps they still have an IMEI check during the process. It seems unlikely, but my only guess at this time.
It's also possible that the prior owner unlocked, rooted, changed something and then unrooted+relocked, but seems a low probability.
A good test might be to remove the SIM, factory wipe and then bootup to see if the current Google OTA (to 5.1 "D") happens during the impending setup. But, you don't want to wipe at this time . . . btw, I took both the OTA and did a fastboot process - the latter process was easy, just took some time to do safely.
- ooofest
simms22 said:
can always flash the factory img via fastboot, while the device is in its bootloader.
Click to expand...
Click to collapse
This would also be my suggestion. However there is no factory image for LMY47M so you would have to use LRX22C and then apply the "M" version again via sideload.
ooofest said:
I wonder if this might partly be related to having a T-Mobile SIM and being purchased from Amazon - because the OTA is controlled by the carrier but perhaps they still have an IMEI check during the process. It seems unlikely, but my only guess at this time.
A good test might be to remove the SIM, factory wipe and then bootup to see if the current Google OTA (to 5.1 "D") happens during the impending setup. But, you don't want to wipe at this time, so I suppose checking to ensure you have the correct image for sideloading is your next step (per Evolution_Freak).
- ooofest
Click to expand...
Click to collapse
na.. you could buy a n6 from verizon, put in a tmobile sim, and get the update(for tmo). updates are related to your sim card, not to where you bought the n6. the ota is still controlled by google, not the carrier.
ooofest said:
I wonder if this might partly be related to having a T-Mobile SIM and being purchased from Amazon - because the OTA is controlled by the carrier but perhaps they still have an IMEI check during the process. It seems unlikely, but my only guess at this time.
It's also possible that the prior owner unlocked, rooted, changed something and then unrooted+relocked, but seems a low probability.
A good test might be to remove the SIM, factory wipe and then bootup to see if the current Google OTA (to 5.1 "D") happens during the impending setup. But, you don't want to wipe at this time . . . btw, I took both the OTA and did a fastboot process - the latter process was easy, just took some time to do safely.
- ooofest
Click to expand...
Click to collapse
I'm also wondering if this is a possibility. If you check the other thread I linked, the user was on T-Mobile with a Google play purchased device.
Evolution_Freak said:
This would also be my suggestion. However there is no factory image for LMY47M so you would have to use LRX22C and then apply the "M" version again via sideload.
Click to expand...
Click to collapse
Can you link me to the proper method for doing this? Will this cause a wipe?
simms22 said:
na.. you could buy a n6 from verizon, put in a tmobile sim, and get the update(for tmo). updates are related to your sim card, not to where you bought the n6. the ota is still controlled by google, not the carrier.
Click to expand...
Click to collapse
Maybe it's a terminology thing for me, then: Google controls their OTA (at "D" for the Nexus 6 right now, it appears), but the Verizon SIM was apparently holding my phone back from getting an update notification. So, I think you said the same thing and maybe I didn't express myself clearly before.
However, doesn't the T-Mobile OTA put their enabled phones at 5.1 "M"?
- ooofest
ooofest said:
Maybe it's a terminology thing for me, then: Google controls their OTA (at "D" for the Nexus 6 right now, it appears), but the Verizon SIM was apparently holding my phone back from getting an update notification. So, I think you said the same thing and maybe I didn't express myself clearly before.
However, doesn't the T-Mobile OTA put their enabled phones at 5.1 "M"?
- ooofest
Click to expand...
Click to collapse
m is "supposedly" for tmobile devices, but it seems as any of the updates work on any carrier. right now im on the 47I version, while on tmobile, while volte is working on my device properly. i was on m last week though
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
simms22 said:
m is "supposedly" for tmobile devices, but it seems as any of the updates work on any carrier. right now im on the 47I version, while on tmobile, while volte is working on my device properly. i was on m last week though
Click to expand...
Click to collapse
Yeah, I had "D" (via no-SIM+factory reset OTA) before E (via fastboot) on Verizon with the same general capabilities.
I was just wondering out loud if these supposedly carrier-specific updates might actually be installing to phones on their respective networks via OTA, because the T-Mobile Nexus 6 page seems to imply that their subscribers get "M". In that case, that might lend further credence to the idea that OTAs are more particular, based on your SIM (at the very least), but maybe there's other criteria at this time, too (like, white-listed IMEI).
- ooofest
Paul22000 said:
Can you link me to the proper method for doing this? Will this cause a wipe?
Click to expand...
Click to collapse
Yes, installing a factory image requires unlocking the bootloader which wipes your device. There's a thread in the general forum that explains all of this.
---------- Post added at 03:41 PM ---------- Previous post was at 03:38 PM ----------
Based on the info that @simms22 provided above, I would suggest first trying to sideload LRX22C to LMY47I first. If it fails again, then I would suggest the factory image route.
Paul22000 said:
Can you link me to the proper method for doing this? Will this cause a wipe?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=59853083&postcount=6
thacounty said:
http://forum.xda-developers.com/showpost.php?p=59853083&postcount=6
Click to expand...
Click to collapse
The user in this thread requesting help has a locked bootloader and is stock. Using fastboot to flash the images separately is not an option at this point because he doesn't want to wipe to unlock.
Related
Hi, my Nexus is on Android 5.0.1 (LRX22C). I haven't rooted or unlocked the bootloader; everything is totally stock. But I'm unable to successfully install the Android 5.1 OTA update. My phone downloads it, verifies it, then reboots to begin the installation process. After working on the update for a while, I see an error message (with an android on its back and a red "X"). The phone stays on that screen for a while, then eventually reboots without having installed the update. I've tried clearing cache, and it doesn't help. Anyone have any ideas?
carrot34 said:
Hi, my Nexus is on Android 5.0.1 (LRX22C). I haven't rooted or unlocked the bootloader; everything is totally stock. But I'm unable to successfully install the Android 5.1 OTA update. My phone downloads it, verifies it, then reboots to begin the installation process. After working on the update for a while, I see an error message (with an android on its back and a red "X"). The phone stays on that screen for a while, then eventually reboots without having installed the update. I've tried clearing cache, and it doesn't help. Anyone have any ideas?
Click to expand...
Click to collapse
Some more info please. What carrier are you using? Was your phone purchased from that carrier or somewhere else?
Evolution_Freak said:
Some more info please. What carrier are you using? Was your phone purchased from that carrier or somewhere else?
Click to expand...
Click to collapse
Thanks! I'm on T-Mobile, and bought the phone from Google Play.
carrot34 said:
Thanks! I'm on T-Mobile, and bought the phone from Google Play.
Click to expand...
Click to collapse
Are you familiar with sideload?
---------- Post added at 09:42 PM ---------- Previous post was at 09:37 PM ----------
Check out my thread on OTA's.
http://forum.xda-developers.com/showthread.php?t=2992919
In post #2, there's a link to the OTA files thread. Take the one that is specifically for T-Mobile. LRX22C to LMY47M.
Evolution_Freak said:
Are you familiar with sideload?
Click to expand...
Click to collapse
Yeah, I've sideloaded before with other devices, but I'd like not to have deal with wiping my phone to unlock the bootloader right now. I'd thought that by not rooting or messing with the bootloader, I'd keep things simple and be able to easily apply OTA updates. So I'm very frustrating that this isn't working. Any idea why this might be happening?
Thanks!
Alan
carrot34 said:
Yeah, I've sideloaded before with other devices, but I'd like not to have deal with wiping my phone to unlock the bootloader right now. I'd thought that by not rooting or messing with the bootloader, I'd keep things simple and be able to easily apply OTA updates. So I'm very frustrating that this isn't working. Any idea why this might be happening?
Thanks!
Alan
Click to expand...
Click to collapse
No, you do not need to wipe or unlock to sideload. Post #3 in the thread I linked, simple instructions on sideloading.
As for why this is happening, anyone's guess but it could, somehow, have something to do with your device having the T-Mobile Sim and being from Google play.
Evolution_Freak said:
No, you do not need to wipe or unlock to sideload. Post #3 in the thread I linked, simple instructions on sideloading.
As for why this is happening, anyone's guess but it could, somehow, have something to do with your device having the T-Mobile Sim and being from Google play.
Click to expand...
Click to collapse
OK, I'll give it a shot. Thanks! Any idea which OTA I want? I'm guessing it's LMY47M, since I'm on a T-Mobile SIM, even though the device was bought from Google? Need I worry that that build isn't up on Google's "Factory Images for Nexus Devices" page? And is there any risk that installing an update this way will make it more complicated to get OTA updates in the future? (I was hoping that by doing things the official way this time, I could avoid having to monkey around with stuff like this.)
Thanks!
Alan
carrot34 said:
OK, I'll give it a shot. Thanks! Any idea which OTA I want? I'm guessing it's LMY47M, since I'm on a T-Mobile SIM, even though the device was bought from Google? Need I worry that that build isn't up on Google's "Factory Images for Nexus Devices" page? And is there any risk that installing an update this way will make it more complicated to get OTA updates in the future? (I was hoping that by doing things the official way this time, I could avoid having to monkey around with stuff like this.)
Thanks!
Alan
Click to expand...
Click to collapse
Yes, you want the LRX22C to LMY47M OTA as I said before. No, you don't need to worry about it not being on the images page. Also a no for it affecting your ability to get OTA's in the future. On a Nexus, this is pretty much as official as getting the OTA natively.
OK, an update: got an error installing the update any way I tried, even after a factory reset. Called Google support, and they're replacing the phone for me.
I just sent back the N6 that had the screen burn out, I got my RMA device and its on just 5.1 not 5.1.1 should I update it or keep it does it matter? Also this N6 is doing some of the same issues that the other device did before it burned out. The screen has a lot of flickering and triangle flashes but only when I'm using my web browser, also, today I got off of a phone call and the proximity sensor failed to turn the screen on. What's up with that? I'm starting to wonder about these N6's man. Any ideas guys. I think I may need to just flash the s#-t out of this thing
electrojas said:
I just sent back the N6 that had the screen burn out, I got my RMA device and its on just 5.1 not 5.1.1 should I update it or keep it does it matter? Also this N6 is doing some of the same issues that the other device did before it burned out. The screen has a lot of flickering and triangle flashes but only when I'm using my web browser, also, today I got off of a phone call and the proximity sensor failed to turn the screen on. What's up with that? I'm starting to wonder about these N6's man. Any ideas guys. I think I may need to just flash the s#-t out of this thing
Click to expand...
Click to collapse
If it was mine, I'd RMA this one too.
Unlock it. Fastboot flash the updated 5.1.1 factory image and see what you have. If bad send it back. If good it all good.
---------- Post added at 12:47 PM ---------- Previous post was at 12:39 PM ----------
What browser. It may be the problem. There were proximity sensor fixes in one of the updates. Not sure which.
prdog1 said:
Unlock it. Fastboot flash the updated 5.1.1 factory image and see what you have. If bad send it back. If good it all good.
---------- Post added at 12:47 PM ---------- Previous post was at 12:39 PM ----------
What browser. It may be the problem. There were proximity sensor fixes in one of the updates. Not sure which.
Click to expand...
Click to collapse
I'm using adblock browser. I just updated to Windows 10 so now my adb is all jacked up for some reason. When I turned on the phone it said that there was a 5.1.1 update ready to be installed. Should I just take that one before I unlock the BL and root or do the unlock first? Thanks to all of you who are helping me out. Good people.
electrojas said:
I'm using adblock browser. I just updated to Windows 10 so now my adb is all jacked up for some reason. When I turned on the phone it said that there was a 5.1.1 update ready to be installed. Should I just take that one before I unlock the BL and root or do the unlock first? Thanks to all of you who are helping me out. Good people.
Click to expand...
Click to collapse
Unlock first. Too many been bricked on that update with bootloader locked. I wouldn't take it. Win 10 didn't jack with my adb. I have full SDK tho. Some are using the 15 minute adb/fastboot. I would search and try to reinstall it. Does your usb debug work as far as showing device MTP on PC. If not you lost the Google driver.
---------- Post added at 03:13 PM ---------- Previous post was at 03:10 PM ----------
More than likely that browser is the flicker problem. I use Chrome but with Adaway and MOAB. No adds anywhere. lol
I'll have to check. I'm so gunshy now I only hooked this to pc just to put music on it. I'll unlock BL and try the update after. Thanks
electrojas said:
I'll have to check. I'm so gunshy now I only hooked this to pc just to put music on it. I'll unlock BL and try the update after. Thanks
Click to expand...
Click to collapse
If able to put music on your driver is good. Need ADB/Fastboot working or you are already dead in the water.
prdog1 said:
Unlock first. Too many been bricked on that update with bootloader locked. I wouldn't take it. Win 10 didn't jack with my adb. I have full SDK tho. Some are using the 15 minute adb/fastboot. I would search and try to reinstall it. Does your usb debug work as far as showing device MTP on PC. If not you lost the Google driver.
---------- Post added at 03:13 PM ---------- Previous post was at 03:10 PM ----------
More than likely that browser is the flicker problem. I use Chrome but with Adaway and MOAB. No adds anywhere. lol
Click to expand...
Click to collapse
15 minute adb? What is that like a tool that does all of that for you?
electrojas said:
15 minute adb? What is that like a tool that does all of that for you?
Click to expand...
Click to collapse
It the lazy man ADB/Fastboot for those that don't want to install full SDK and edit the environmental path.
http://forum.xda-developers.com/showthread.php?t=2588979
So I just follow the unlock procedure in the how to post like normal now right
electrojas said:
So I just follow the unlock procedure in the how to post like normal now right
Click to expand...
Click to collapse
Enable unlock in developers options. Boot to bootloader. in command prompt type "fastboot devices" to make sure your device id shows up. If shows device type "fastboot oem unlock". Will see prompt on phone to agree.
It's just finished so now does it matter which 5.1.1 I take, and do I have to put TWRP on this in order to do it
I suppose now I can take the downloaded one or do you recommend a better file. I really would like to keep this Damn phone
electrojas said:
It's just finished so now does it matter which 5.1.1 I take, and do I have to put TWRP on this in order to do it
Click to expand...
Click to collapse
Latest for all carriers is I version unless you are on TMobile then it is the one that says TMobile only. They don't have the security update yet. No need for TWRP yet as long as unlocked. Get it booted and see if everything works. Do NOT relock. DO NOT use toolkit. Do it manually with fastboot commands.
prdog1 said:
Latest for all carriers is I version unless you are on TMobile then it is the one that says TMobile only. They don't have the security update yet. No need for TWRP yet as long as unlocked. Get it booted and see if everything works. Do NOT relock.
Click to expand...
Click to collapse
Mine is unbranded factory unlocked. It's restoring all my backed up poo right now. I guess I have 2 options. 1 take the Ota they send down or install the one I downloaded yesterday. It says for all carriers except tmobile. I got it from Google yesterday. It's the exact one that was on the phone I sent back. Do you have any particular preference or reccomendation?
electrojas said:
Mine is unbranded factory unlocked. It's restoring all my backed up poo right now. I guess I have 2 options. 1 take the Ota they send down or install the one I downloaded yesterday. It says for all carriers except tmobile. I got it from Google yesterday. It's the exact one that was on the phone I sent back. Do you have any particular preference or reccomendation?
Click to expand...
Click to collapse
The new I version has the Stagefright security fix otherwize the Z version is fine. That is what I am on. Haven't updated yet.. You can try OTA as long as unlocked. Have seen posts that say OTA won't work unlocked. Not sure. If it bootloops and it is locked you are hosed again and have to RMA.
prdog1 said:
The new I version has the Stagefright security fix otherwize the Z version is fine. That is what I am on. Haven't updated yet.. You can try OTA as long as unlocked. Have seen posts that say OTA won't work unlocked. Not sure. If it bootloops and it is locked you are hosed again and have to RMA.
Click to expand...
Click to collapse
The new I version? Is the best place to get it on here or Motorola? Also your gonna think this is a stupid question but what is I version? I'm coming from Sammy to LG back to Sammy, now this. Learning about fastboot its all new to me. Thanks bro
Sent from my Nexus 6 using XDA Forums Pro.
electrojas said:
The new I version? Is the best place to get it on here or Motorola? Also your gonna think this is a stupid question but what is I version? I'm coming from Sammy to LG back to Sammy, now this. Learning about fastboot its all new to me. Thanks bro
Sent from my Nexus 6 using XDA Forums Pro.
Click to expand...
Click to collapse
https://developers.google.com/android/nexus/images
Maybe first i can direct unlock ZV5/ZV6/ZV7/ZV8 without root.
International sim unlock ZV8 update android 6.0 Marshmallow without bugs
Removed hands free activation
Fully working smooth 2g/3g data connection,end call and got incomming call normal :good:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
HTCuser90 said:
Maybe first i can direct unlock ZV5/ZV6/ZV7/ZV8 without root.
International sim unlock ZV8 update android 6.0 Marshmallow without bugs
Removed hands free activation
Fully working smooth 2g/3g data connection,end call and got incomming call normal :good:
Click to expand...
Click to collapse
So, do you have ZV7/ZV8? Including Kernel? Can you DD the partitions and post the links?
** Also you don't need Root to pull system image using DD command from the Send_Command.exe file in download mode ***
/.
What!? How can you already have ZV7 or ZV8?
its fake...
Agimax said:
So, do you have ZV7/ZV8? Including Kernel? Can you DD the partitions and post the links?
/.
Click to expand...
Click to collapse
Intetnational unlock without root
KingFatty said:
What!? How can you already have ZV7 or ZV8?
Click to expand...
Click to collapse
Unroot and check OTA update
mayrer said:
its fake...
Click to expand...
Click to collapse
Jajaja,did you saw my video ??? Keep your mind and waiting update lol
HTCuser90 said:
Jajaja,did you saw my video ??? Keep your mind and waiting update lol
Click to expand...
Click to collapse
I can make video with zv10...
Upload your backup system (system.img) please.
---------- Post added at 02:57 AM ---------- Previous post was at 02:51 AM ----------
HTCuser90 said:
Maybe first i can direct unlock ZV5/ZV6/ZV7/ZV8 without root.
Click to expand...
Click to collapse
zv7 does not exist...
and Sprint not yet released updated zv8
http://support.sprint.com/support/a...:FindAndUpdateTheSoftwareVersionOnYourLgG4#!/
mayrer said:
I can make video with zv10...
Upload your backup system (system.img) please.
---------- Post added at 02:57 AM ---------- Previous post was at 02:51 AM ----------
zv7 does not exist...
and Sprint not yet released updated zv8
http://support.sprint.com/support/a...:FindAndUpdateTheSoftwareVersionOnYourLgG4#!/
Click to expand...
Click to collapse
Keep your mind :fingers-crossed: my screenshot and my video is fake
Just show information for anyone.
But, now ZV8 is official, and will be coming soon, it's on that one report forget the name, see ZV8 listed here:
http://device.sprintpcs.com/LG/LS991-SPRINT/LS991ZV8.rdf
KingFatty said:
But, now ZV8 is official, and will be coming soon, it's on that one report forget the name, see ZV8 listed here:
http://device.sprintpcs.com/LG/LS991-SPRINT/LS991ZV8.rdf
Click to expand...
Click to collapse
you repost my news
http://forum.xda-developers.com/showpost.php?p=63775901&postcount=8
mayrer said:
you repost my news
http://forum.xda-developers.com/showpost.php?p=63775901&postcount=8
Click to expand...
Click to collapse
You told me fake video and now got information about ZV8 update
HTCuser90 said:
You told me fake video and now got information about ZV8 update
Click to expand...
Click to collapse
ZV8 will, but not yet published.
my devices g4 sprint update android 6.0 ok .. use very good but.....
Can not send command
How to root ???
---------- Post added at 12:08 PM ---------- Previous post was at 12:07 PM ----------
Agimax said:
So, do you have ZV7/ZV8? Including Kernel? Can you DD the partitions and post the links?
** Also you don't need Root to pull system image using DD command from the Send_Command.exe file in download mode ***
/.
Click to expand...
Click to collapse
LG g4 android 6.0 no support Send command
And flashtools flash file TOT go back android 5.1 not work
Is it possible this is a leaked firmware? Maybe benefit of the doubt and a "wait and see" approach is best?
Someone asked how to dd if send command or send command lock.
I can direct unlock without root but need open diag port and here my answer for the question how to ?
Use this trick from xda with any lg g4 kdz for opening diag port http://forum.xda-developers.com/g4/general/lg-g4s-world-root-lg-devices-t3231759
Dont try to downgrade ZV5 or ZV6 TOT file, this will be make your phone bricked with qualcomm usb.
mayrer said:
ZV8 will, but not yet published.
Click to expand...
Click to collapse
Stop scam me,keep waiting and you will see,okay.
hoangps said:
Someone asked how to dd if send command or send command lock.
I can direct unlock without root but need open diag port and here my answer for the question how to ?
Use this trick from xda with any lg g4 kdz for opening diag port http://forum.xda-developers.com/g4/general/lg-g4s-world-root-lg-devices-t3231759
Dont try to downgrade ZV5 or ZV6 TOT file, this will be make your phone bricked with qualcomm usb.
Stop scam me,keep waiting and you will see,okay.
Click to expand...
Click to collapse
Looks like your buddy got a leak somehow, ZV8 is in testing stages.
HTCuser90 said:
You told me fake video and now got information about ZV8 update
Click to expand...
Click to collapse
it's real and true, it's happening to my phone. the only thing, it can't root and can't edit apn to get 3g. Is there anybody help me with this issue?
lnguyenvn2003 said:
it's real and true, it's happening to my phone. the only thing, it can't root and can't edit apn to get 3g. Is there anybody help me with this issue?
Click to expand...
Click to collapse
HTCuser90 is me
I can make injection root for zv8.
hoangps said:
HTCuser90 is me
I can make injection root for zv8.
Click to expand...
Click to collapse
Giving you the benefit of the doubt, and you say you are also HTCuser90 (the OP of this post), okay then-
As HTCuser90 - you say you don't have root, so you say you can't use the DD commands to pull system / kernel image and the Send_Command.exe is useless.
Now as user hoangps (HTCuser90) you say you can inject root for ZV8, so please inject the root and DD both partitions for posting.
Also, please list the steps taken to get the ZV8 update. Did ZV7 update first and then take the ZV8? or did you get a leak and manually update? I ask this because if it did the ZV7 update first, it may have locked it down for ZV8, we may be able to intercept the updates and keep it rooted to accept the ZV8. Of course none of this matters if you can indeed inject the root in ZV8.
Please enlighten us, because it still seems like something isn't right here.
Also user hoangps that is backing you up about the ZV8 update is a guy with only 4 posts...
/.
hoangps said:
HTCuser90 is me
I can make injection root for zv8.
Click to expand...
Click to collapse
On h815 wiht android 6.0 , root can be obtained only if unlock the bootloader.
On ls991 bootlodaer impossible to unlock, and you claim that you can get root, you are a genius?
do not make me laugh...
Agimax said:
Giving you the benefit of the doubt, and you say you are also HTCuser90 (the OP of this post), okay then-
As HTCuser90 - you say you don't have root, so you say you can't use the DD commands to pull system / kernel image and the Send_Command.exe is useless.
Now as user hoangps (HTCuser90) you say you can inject root for ZV8, so please inject the root and DD both partitions for posting.
Also, please list the steps taken to get the ZV8 update. Did ZV7 update first and then take the ZV8? or did you get a leak and manually update? I ask this because if it did the ZV7 update first, it may have locked it down for ZV8, we may be able to intercept the updates and keep it rooted to accept the ZV8. Of course none of this matters if you can indeed inject the root in ZV8.
Please enlighten us, because it still seems like something isn't right here.
Also user hoangps that is backing you up about the ZV8 update is a guy with only 4 posts...
/.
Click to expand...
Click to collapse
Long time ago,my currently account has been disable and only read, cant comment or reply.... then created a new account until my customer bring his lg g4 ls991 to me,asked remove google account verified and sim unlock for him :good: after removed done, saw his phone already running ZV8 marshmallow software.
You can read this post with trick for open diag port when command got id fail. http://forum.xda-developers.com/showpost.php?p=63804505&postcount=14
And see my log below for unlocking without root.
mayrer said:
On h815 wiht android 6.0 , root can be obtained only if unlock the bootloader.
On ls991 bootlodaer impossible to unlock, and you claim that you can get root, you are a genius?
do not make me laugh...
Click to expand...
Click to collapse
The kid,shut up and read before comment anything http://forum.xda-developers.com/showpost.php?p=63804505&postcount=14 and see log information
Code:
Device Detected...
model:= LGLS991
Androids Version:= 5.1
Description Version:= p1_spr_us-user 5.1 LMY47D 1523616304272 release-keys
Platform:= msm8992 [ ] [ msm ]
Baseband:= MPSS.BO.2.5.c3-00070-M8994FAAAANAZM-1.20288.2
Factory Ver := LGLS991AT-00-ZV6-SPR-US-AUG-24-2015+12
Model & Firmware Ver := LS991ZV6
Simstatus:= ABSENT
IMEI-1 = null or empty
ANDROID-ID = LGLS991dfdc28e6_00006B0C6F
[B][COLOR="Blue"]Device is not rooted[/COLOR][/B]
LG Sprint Unlocking Started..
Searching PHONE NOW...
[B][COLOR="Blue"]Port Found..COM52
Detected in EMP Mode..
Unlock Success..[/COLOR][/B]
!!! Success !!!!
Restart Phone if not auto...
Total Time Take...00:00:34
Log Saved
MOD EDIT: IMEI link removed
I know AT&T hasnt released the 6.0 update yet but I just got the November LMY48Y security update. Is there anyways I can flash or manually update to 6.0? I'm on the international N6 so its not carrier locked or anything, I'm just not sure which build of Marshmallow to flash as all of them come from different builds (LM48T - MRKxxx)
none
Are you rooted? If your rooted you shouldn't be getting, nor receiving any OTA. I don't know much about the International version but as long as your rooted with an unlocked bootloader flash the version you want to. The great thing about the Nexus 6 is all the developement you see. Any other questions shoot me a PM if you want to
USMC retired said:
Are you rooted? If your rooted you shouldn't be getting, nor receiving any OTA. I don't know much about the International version but as long as your rooted with an unlocked bootloader flash the version you want to. The great thing about the Nexus 6 is all the developement you see. Any other questions shoot me a PM if you want to
Click to expand...
Click to collapse
Not rooted right now but bootloader has been unlocked since the day I got it. I just didnt know if I can flash any 6.0 build. Will have to give a try tomorrow, any problems I'll be sure to PM you. Thanks for the info man, take care.
CavyS, I'm in the same boat as you... Also, I was told that flashing from the wrong OTA could cause problems. Please let me know if you tried flashing something. I'm stuck on LMY48Y...
Thanks!
There is no OTA to flash, for the Nexus 6 that has an AT&T sim. It hasn't been released yet. If you want to go to MM (6.0), you should flash the full 6.0 image that Google released back on October 5th, which was MRA58K and then let the security updates install WITHOUT the AT&T sim installed. "N" and "R" have since been released that contain the security updates. You could probably go directly to "R" without an issue. I'm backing up all of my data tomorrow morning and flashing "MRA58R" and if I run into problems, I'll flash back to LMY48Y. From what I gather, there is no issues with FULL IMAGE of MM on the Nexus 6 with AT&T, it's that there is no OTA yet available to go from 5.1.1 LMY48Y to 6.0 MRA58? because Google or AT&T is still trying to figure it out. Personally, I'd rather flash a full, clean image than get an OTA and still have to do a factory data reset (FDR) to fix all the issues that seems to come with an OTA update, especially one as comprehensive as going from Lollipop to Marshmallow.
UPDATE: I used the NRT (Nexus Root Tool Kit) from Wugfresh and following this video, I unlocked my bootloader and installed MRA58R. It installed quickly and painlessly, although I did a complete backup of all my data using Helium before I started the process. So far, so good. I'll report back if I have any issues.
https://www.youtube.com/watch?v=Emyd6od3tGs
http://www.wugfresh.com/
BEFORE:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
AFTER:
And here is another tip...once you install MM on your N6, if you want to re-lock your bootloader, lock it BEFORE you put back all of your user data. On previous versions of Android, locking the bootloader did not wipe user data, but on MM, it does! I wish I had known that before I set everything up. See this thread for more info: http://forum.xda-developers.com/nexus-6/general/locking-bootloader-wipes-data-t2947916
Doesn't really matter which build.
CavyS said:
I know AT&T hasnt released the 6.0 update yet but I just got the November LMY48Y security update. Is there anyways I can flash or manually update to 6.0? I'm on the international N6 so its not carrier locked or anything, I'm just not sure which build of Marshmallow to flash as all of them come from different builds (LM48T - MRKxxx)
Click to expand...
Click to collapse
Just use any build you like from the Google Developers page https developers.google.com/android/nexus/images
On the site are various instructions on how to flash the image(s). Not that you need your bootloader unlocked (if it isn't, doing so will delete all your data, so make a backup first).
Have fun with Marshmallow!
BartmanJax said:
UPDATE: I used the NRT (Nexus Root Tool Kit) from Wugfresh and following this video, I unlocked my bootloader and installed MRA58R. It installed quickly and painlessly, although I did a complete backup of all my data using Helium before I started the process. So far, so good. I'll report back if I have any issues.
https://www.youtube.com/watch?v=Emyd6od3tGs
http://www.wugfresh.com/
BEFORE:
AFTER:
And here is another tip...once you install MM on your N6, if you want to re-lock your bootloader, lock it BEFORE you put back all of your user data. On previous versions of Android, locking the bootloader did not wipe user data, but on MM, it does! I wish I had known that before I set everything up. See this thread for more info: http://forum.xda-developers.com/nexus-6/general/locking-bootloader-wipes-data-t2947916
Click to expand...
Click to collapse
@BartmanJax, is your N6 on AT&T still working smoothly. I heard of some issues with reboots and/or dropping connection when going to MM. If you are not having issues I'm going to use the WUG RootKit and do the same!
Genghis1227 said:
@BartmanJax, is your N6 on AT&T still working smoothly. I heard of some issues with reboots and/or dropping connection when going to MM. If you are not having issues I'm going to use the WUG RootKit and do the same!
Click to expand...
Click to collapse
Working perfect! No issues at all!
And I learned a trick this morning when I flashed my N7 (2013) with a fresh image. You don't have to do an OEM Unlock first by clicking the OEM Unlock button on NRT. It will be done for you automatically if you follow the steps below.
First, make sure your have USB Debugging turned on on your N6 AND have your USB connection set to PTP. (Go to settings -> Storage -> Hit the three dots in to top right -> USB Computer Connection -> and check PTP box).
With your N6 connected, launch NRT, answer the questions about YOUR model and the current build (probably Nexus 6 (Moto XT1100, XT1103) for your device and for the build, probably SHAMU-SHAMU: Android 5.1.1 - Build LMY48Y). Make sure your information is correct for what is CURRENTLY on your phone). NRT will want to download some files. Let it. It only take a minute or so on a high speed connection.
When you get to the main NRT window as shown here, click on "Flash Stock + Unroot" shown here highlighted.
On this next screen, just click OK.
Assuming you're on the AT&T network using a Nexus 6, on this screen, select MRA58R (MMB29K if you want to go straight to 6.0.1) in the drop down and in the "Choice" section, select Automatically download and shown in this image. This is what you will be adding to your phone. The new image. Then click OK.
That's all you have to do. If the phone is connected to your computer correctly and is communicating with the computer, it will automatically launch the bootloader and ask you if you really want to unlock the phone, That takes an action from you (Volume up button once to "Yes" and then the power button to select). When you do this, you have to go back into the phone (skip all those annoying steps) to get to the home screen and go back to Settings > About Phone > press on the Build 7 times to get the Developers Options and turn on USB debugging again and your also have to go back to PTP. NRT will guide you through the steps. It will then automatically download the MRA58R .tgz file, unzip it, push it to your phone and install the new image. It's truly painless.
Once everything is done, if you want to OEM Lock your phone, do it BEFORE you start putting your data back.
One side note. After you unlock the phone the first time and you have to go in to turn on USB debugging AND after you install 6.0, both of the those boot times are long (maybe 5-10 minutes). Don't worry. After 6.0 is installed and booted up the first time, subsequent boots are much faster. And shutdown is very fast in 6.0.
Will give it a try tonight probably. Thank you!
Sent from my Nexus 6 using Tapatalk
Genghis1227 said:
Will give it a try tonight probably. Thank you!
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
If you do, let me know how it goes. Good luck! :good:
BartmanJax said:
Working perfect! No issues at all!
And I learned a trick this morning when I flashed my N7 (2013) with a fresh image. You don't have to do an OEM Unlock first by clicking the OEM Unlock button on NRT. It will be done for you automatically if you follow the steps below.
First, make sure your have USB Debugging turned on on your N6 AND have your USB connection set to PTP. (Go to settings -> Storage -> Hit the three dots in to top right -> USB Computer Connection -> and check PTP box).
With your N6 connected, launch NRT, answer the questions about YOUR model and the current build (probably Nexus 6 (Moto XT1100, XT1103) for your device and for the build, probably SHAMU-SHAMU: Android 5.1.1 - Build LMY48Y). Make sure your information is correct for what is CURRENTLY on your phone). NRT will want to download some files. Let it. It only take a minute or so on a high speed connection.
When you get to the main NRT window as shown here, click on "Flash Stock + Unroot" shown here highlighted.
On this next screen, just click OK.
Assuming you're on the AT&T network using a Nexus 6, on this screen, select MRA58R in the drop down and in the "Choice" section, select Automatically download and shown in this image. This is what you will be adding to your phone. The new image. Then click OK.
That's all you have to do. If the phone is connected to your computer correctly and is communicating with the computer, it will automatically launch the bootloader and ask you if you really want to unlock the phone, That takes an action from you (Volume up button once to "Yes" and then the power button to select). When you do this, you have to go back into the phone (skip all those annoying steps) to get to the home screen and go back to Settings > About Phone > press on the Build 7 times to get the Developers Options and turn on USB debugging again and your also have to go back to PTP. NRT will guide you through the steps. It will then automatically download the MRA58R .tgz file, unzip it, push it to your phone and install the new image. It's truly painless.
Once everything is done, if you want to OEM Lock your phone, do it BEFORE you start putting your data back.
One side note. After you unlock the phone the first time and you have to go in to turn on USB debugging AND after you install 6.0, both of the those boot times are long (maybe 5-10 minutes). Don't worry. After 6.0 is installed and booted up the first time, subsequent boots are much faster. And shutdown is very fast in 6.0.
Click to expand...
Click to collapse
I remembered I had to do OEM unlock in developer menu... Did you do this before anything?
Sent from my Nexus 6 using Tapatalk
---------- Post added at 11:35 PM ---------- Previous post was at 10:42 PM ----------
Just finished the update to MM and everything so far is very smooth. The only thing I would say is to enable the Allow OEM Bootloader Unlock before pushing the Flash Stock + Unroot. Makes it that much quicker so that you don't have to boot back into the device and enable it later. Otherwise, setting up the apps and then going to put the SIM back on. Will report back if I get any issues while using it on the AT&T network when I put my SIM back on.
I put in my SIM and unfortunately I cannot connect via LTE, only HSDPA. I wonder if it just isn't showing LTE but really connected via LTE. In the 5.1.1 it showed LTE...
---------- Post added at 07:49 AM ---------- Previous post was at 07:36 AM ----------
Genghis1227 said:
I put in my SIM and unfortunately I cannot connect via LTE, only HSDPA. I wonder if it just isn't showing LTE but really connected via LTE. In the 5.1.1 it showed LTE...
Click to expand...
Click to collapse
After a second reboot I now have LTE.
Genghis1227 said:
I put in my SIM and unfortunately I cannot connect via LTE, only HSDPA. I wonder if it just isn't showing LTE but really connected via LTE. In the 5.1.1 it showed LTE...
---------- Post added at 07:49 AM ---------- Previous post was at 07:36 AM ----------
After a second reboot I now have LTE.
Click to expand...
Click to collapse
Excellent! :good:
Anybody try the 6.0.1 update and use the no wipe mode?
Looks like the 6.0.1 released https://developers.google.com/android/nexus/images
---------- Post added at 03:03 PM ---------- Previous post was at 03:02 PM ----------
Genghis1227 said:
Anybody try the 6.0.1 update and use the no wipe mode?
Looks like the 6.0.1 released https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
Perhaps will it OTA with pulling the SIM?
Genghis1227 said:
Anybody try the 6.0.1 update and use the no wipe mode?
Click to expand...
Click to collapse
Yep! I did yesterday morning. I went from MRA58R to MMB29K using the No Wipe Mode and it seems to have worked fine. Luckily, I had not locked my bootloader from the previous install of 58R. If I had, then it wouldn't have mattered since you wipe the phone as soon as you unlock the bootloader.
29K is working fine on my N6 on AT&T.
Genghis1227 said:
Perhaps will it OTA with pulling the SIM?
Click to expand...
Click to collapse
Probably not. AT&T is driving the release of OTA's, just like Verizon, Sprint and T-Mo is driving the release of OTA's of phones on their network.
So because you left the bootloader unlocked it just basically upgraded (aka sideloaded the OTA) right? Data and everything else intact? I'm just going to keep it unlocked from now on. AT&T is horrible at updating.
Genghis1227 said:
So because you left the bootloader unlocked it just basically upgraded (aka sideloaded the OTA) right? Data and everything else intact? I'm just going to keep it unlocked from now on. AT&T is horrible at updating.
Click to expand...
Click to collapse
Correct! Just be sure and select the "No Wipe Mode." I decided to leave mine unlocked as well. Makes updates easier. I don't really want to leave the bootloader unlocked, but like you said, AT&T is horrible at updating.
Here we go for those interested in sideloading
https://developers.google.com/android/ota
johnny8910 said:
Here we go for those interested in sideloading
https://developers.google.com/android/ota
Click to expand...
Click to collapse
thanks
Anyone else finding face unlock is now broken after the January update?
What's odd is that for 2 days after flashing the update, everything was just fine. But yesterday I got a notification that I needed to re-enroll my face for face unlock to work. I did that and now no matter what I do, I can't get face unlock to work. I've reflashed the update and the issue persists. Extremely annoying.
sn0warmy said:
Anyone else finding face unlock is now broken after the January update?
What's odd is that for 2 days after flashing the update, everything was just fine. But yesterday I got a notification that I needed to re-enroll my face for face unlock to work. I did that and now no matter what I do, I can't get face unlock to work. I've reflashed the update and the issue persists. Extremely annoying.
Click to expand...
Click to collapse
A week after updating, and still fine for me.
sn0warmy said:
Anyone else finding face unlock is now broken after the January update?
What's odd is that for 2 days after flashing the update, everything was just fine. But yesterday I got a notification that I needed to re-enroll my face for face unlock to work. I did that and now no matter what I do, I can't get face unlock to work. I've reflashed the update and the issue persists. Extremely annoying.
Click to expand...
Click to collapse
Hasn't happened for me but if you're having issues go back to December update with a clean flash. Then take the January update before you root. Once it's downloaded and installed then root.
Spookymyo said:
Hasn't happened for me but if you're having issues go back to December update with a clean flash. Then take the January update before you root. Once it's downloaded and installed then root.
Click to expand...
Click to collapse
I've tried all sorts of things to get it fixed, including what you mentioned. But it remains broken.
I've tried...
1) Clean flashing the January image again
2) Clean flashing the December image (which previously worked perfectly)
3) Clean flash December and let it auto-update to the January update before attempting to set up face Unlock
None of the above have solved the issue and now, no matter what image I clean flash, I get an error telling me a new face can't be added because there is old face data already uploaded. It gives me no way to remove the old face data in any clean flash I install. This has truly become a serious problem, at least in my case.
My only hope at this point is for Google to roll out an update/fix to correct it. Otherwise, the only other option I can think of is to RMA, which would suck because the phone has been flawless until now. Extremely annoying.
sn0warmy said:
I've tried all sorts of things to get it fixed, including what you mentioned. But it remains broken.
I've tried...
1) Clean flashing the January image again
2) Clean flashing the December image (which previously worked perfectly)
3) Clean flash December and let it auto-update to the January update before attempting to set up face Unlock
None of the above have solved the issue and now, no matter what image I clean flash, I get an error telling me a new face can't be added because there is old face data already uploaded. It gives me no way to remove the old face data in any clean flash I install. This has truly become a serious problem, at least in my case.
My only hope at this point is for Google to roll out an update/fix to correct it. Otherwise, the only other option I can think of is to RMA, which would suck because the phone has been flawless until now. Extremely annoying.
Click to expand...
Click to collapse
Are you making sure you're using the right build number? Mess ups like yours can be a result of flashing the wrong build.
Also try going back to stock unrooted with the bootloader relocked. Then try again. Other than that you may have to contact Google.
Spookymyo said:
Are you making sure you're using the right build number? Mess ups like yours can be a result of flashing the wrong build.
Also try going back to stock unrooted with the bootloader relocked. Then try again. Other than that you may have to contact Google.
Click to expand...
Click to collapse
I have a carrier unlocked US Pixel 4 and used the top factory image in this screenshot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Also, the December image I tried re-flashing was the proper image that had face unlock working perfectly up until moving to the January image.
It would be amazing if I simply flashed the wrong January image. However, even going back to the previously working December image (which was saved on my PC) didn't solve it. So I'm not confident that this is the case.
Also, I want to reiterate that face unlock WAS working for the first few days after flashing the top January image in the above screenshot. It only stopped working a few days after flashing when I got a random notification to re-enroll my face. After that, it was broken and there is seemingly no fix. I also haven't rooted my Pixel 4. Looks like I need to contact google.
Possible hardware fail?
gpvecchi said:
Possible hardware fail?
Click to expand...
Click to collapse
That's my main concern. I'm thinking about just testing one of the other January factory images to see if I can get lucky. I really have nothing to lose, at this point.
regardless, it does look like this issue is a bit more wide spread than just me...
https://www.androidpolice.com/2020/...ken-for-some-may-be-caused-by-recent-patches/
https://www.androidcentral.com/pixel-4s-face-unlock-inexplicably-broken-some
https://bgr.com/2020/01/10/pixel-4-face-unlock-not-working-authentication-failure-and-fixes/
https://9to5google.com/2020/01/09/pixel-4-face-not-available/
Can someone explain what "NTT DOCOMO" means in the bottom factory image from my above screenshot? I'm thinking about giving that a try. I know the "TW & JP" version is "Taiwan and Japan", so I'm not going to bother with that one.
On another note... when did Google start resorting to confusing factory image labels? I've had all the Pixel phones since the Pixel 1 and I have to say, the naming conventions Google is now using for factory images is the most confusing I've ever seen. They aren't even consistent, month to month.
---------- Post added at 12:35 PM ---------- Previous post was at 11:57 AM ----------
UPDATE: Face Unlock fixed!! :highfive:
Spookymyo said:
Also try going back to stock unrooted with the bootloader relocked. Then try again. Other than that you may have to contact Google.
Click to expand...
Click to collapse
I should have paid this more mind. I was digging around and saw someone on the Google support forum report that simply relocking and unlocking the bootloader solved the problem as relocking and/or unlocking the bootloader is the only way to do a 100% true wipe, which erases previously stored face data.
So I relocked the bootloader, immediately unlocked it again before even booting up. Then booted, went back through setup an VOILA! Face unlock working again. Extremely relieved right now.
sn0warmy said:
I have a carrier unlocked US Pixel 4 and used the top factory image in this screenshot:
Also, the December image I tried re-flashing was the proper image that had face unlock working perfectly up until moving to the January image.
It would be amazing if I simply flashed the wrong January image. However, even going back to the previously working December image (which was saved on my PC) didn't solve it. So I'm not confident that this is the case.
Also, I want to reiterate that face unlock WAS working for the first few days after flashing the top January image in the above screenshot. It only stopped working a few days after flashing when I got a random notification to re-enroll my face. After that, it was broken and there is seemingly no fix. I also haven't rooted my Pixel 4. Looks like I need to contact google.
Click to expand...
Click to collapse
QQ1B is the correct build.
You may have hardware failure.
---------- Post added at 05:34 AM ---------- Previous post was at 05:32 AM ----------
sn0warmy said:
That's my main concern. I'm thinking about just testing one of the other January factory images to see if I can get lucky. I really have nothing to lose, at this point.
regardless, it does look like this issue is a bit more wide spread than just me...
https://www.androidpolice.com/2020/...ken-for-some-may-be-caused-by-recent-patches/
https://www.androidcentral.com/pixel-4s-face-unlock-inexplicably-broken-some
https://bgr.com/2020/01/10/pixel-4-face-unlock-not-working-authentication-failure-and-fixes/
https://9to5google.com/2020/01/09/pixel-4-face-not-available/
Can someone explain what "NTT DOCOMO" means in the bottom factory image from my above screenshot? I'm thinking about giving that a try. I know the "TW & JP" version is "Taiwan and Japan", so I'm not going to bother with that one.
On another note... when did Google start resorting to confusing factory image labels? I've had all the Pixel phones since the Pixel 1 and I have to say, the naming conventions Google is now using for factory images is the most confusing I've ever seen. They aren't even consistent, month to month.
---------- Post added at 12:35 PM ---------- Previous post was at 11:57 AM ----------
UPDATE: Face Unlock fixed!! :highfive:
I should have paid this more mind. I was digging around and saw someone on the Google support forum report that simply relocking and unlocking the bootloader solved the problem as relocking and/or unlocking the bootloader is the only way to do a 100% true wipe, which erases previously stored face data.
So I relocked the bootloader, immediately unlocked it again before even booting up. Then booted, went back through setup an VOILA! Face unlock working again. Extremely relieved right now.
Click to expand...
Click to collapse
That's why I was thinking it was hardware failure. Because if relocking the bootloader didn't fix it then it had to be hardware related. Because without twrp to do a full wipe the only way to completely wipe the phone is by relocking the bootloader.
Glad it's fixed!