Database Develop

GRRRRRRRR OTA Corrupted What in the ???? [Solved]

[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.

Update Failing

I just got a regular S6 through T-Mobile and for some reason, the initial update is failing. It will download (177 mb), reboot to install, get to 25%, fail, and reboot. The phone is working perfectly other than that. Any idea what I can do to fix it? Thanks.

Since you just got it, why not do a factory reset, then see if the update takes.

roger1955 said:
Since you just got it, why not do a factory reset, then see if the update takes.
Click to expand...
Click to collapse
I just did a factory reset and it still fails repeatedly.
I get the error "dm verity verification failed".
Also keep in mind that it was doing this out of the box before I even installed any apps.

BTow1105 said:
I just did a factory reset and it still fails repeatedly.
I get the error "dm verity verification failed".
Also keep in mind that it was doing this out of the box before I even installed any apps.
Click to expand...
Click to collapse
What firmware is listed under build number in settings?
The only things off the top of my head I can think of that would be causing this out of the box are Samsung's own phone security or a buggy phone. When trying to root some people got stuck in a boot loop, not cause of a bootloader lock, but because of some part samsung's anti malware security of whatever it is that can be disabled in settings. It was apparently turned on without them knowing. Not sure if this could happen with an official OTA but it's something you can check.
Other than calling samsung or T-mobile considering this is a bug that happened without root, you could try flashing the stock firmware with odin. Although, I can't say whether you'll still have access to the OTA or not, which is why I asked what firmware version you're on.
If it's G920TUVU1AOCG then it's the same as the stock anyway and potentially that could mean it's a bug with the update that was pushed to you seen as it's new. If it's not G920TUVU1AOCG then chances are G920TUVU1AOCG is newer and you can just flash it via odin to update.
edit: you could also try booting into recovery and clearing cache then try the ota again.

When me and my girlfriend got our S6's, hers wouldn't take the update either. It said she had a custom system....The only way I got it to take it was to odin the firmware. That's probably what you'll have to do. Out of curiosity is yours white?

Alarand said:
What firmware is listed under build number in settings?
The only things off the top of my head I can think of that would be causing this out of the box are Samsung's own phone security or a buggy phone. When trying to root some people got stuck in a boot loop, not cause of a bootloader lock, but because of some part samsung's anti malware security of whatever it is that can be disabled in settings. It was apparently turned on without them knowing. Not sure if this could happen with an official OTA but it's something you can check.
Other than calling samsung or T-mobile considering this is a bug that happened without root, you could try flashing the stock firmware with odin. Although, I can't say whether you'll still have access to the OTA or not, which is why I asked what firmware version you're on.
If it's G920TUVU1AOCG then it's the same as the stock anyway and potentially that could mean it's a bug with the update that was pushed to you seen as it's new. If it's not G920TUVU1AOCG then chances are G920TUVU1AOCG is newer and you can just flash it via odin to update.
edit: you could also try booting into recovery and clearing cache then try the ota again.
Click to expand...
Click to collapse
Here is the info you're looking for. It doesn't look to be exactly the same as either version you mentioned.
{
"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"
}
mikeyinid said:
When me and my girlfriend got our S6's, hers wouldn't take the update either. It said she had a custom system....The only way I got it to take it was to odin the firmware. That's probably what you'll have to do. Out of curiosity is yours white?
Click to expand...
Click to collapse
I tried to use Odin and it seemed like the phone froze on the blue "Downloading..." screen after I tried to send it the stock firmware.
Its a white 32gb regular S6.

BTow1105 said:
Here is the info you're looking for. It doesn't look to be exactly the same as either version you mentioned.
I tried to use Odin and it seemed like the phone froze on the blue "Downloading..." screen after I tried to send it the stock firmware.
Its a white 32gb regular S6.
Click to expand...
Click to collapse
Weird. Same as hers. Do you have all the drivers installed? Is odin seeing your device?

mikeyinid said:
Weird. Same as hers. Do you have all the drivers installed? Is odin seeing your device?
Click to expand...
Click to collapse
The drivers are installed, Odin recognizes the device, but it just seemed frozen on the blue screen. Odin did a few things and said "started" or something and it said that for about 20 minutes before I decided that couldn't be right. Rebooted it and it went right back to normal.

Have another computer to try, just to cancel out that computer being the problem?

So its fixed now. I went to Best Buy and they have a Samsung rep there. I talked to him about it and he decided to plug it into his laptop and put the stock firmware on it (which I tried to do but it also didnt work). The build number changed slightly and now it says the phone is up to date. Here is the old and new build info:

BTow1105 said:
So its fixed now. I went to Best Buy and they have a Samsung rep there. I talked to him about it and he decided to plug it into his laptop and put the stock firmware on it (which I tried to do but it also didnt work). The build number changed slightly and now it says the phone is up to date. Here is the old and new build info:
Click to expand...
Click to collapse
That was very cool of him, I'm pretty sure they're not suppose to do that. To bad he didn't flash some super secret unreleased test software on it lol.

mikeyinid said:
That was very cool of him, I'm pretty sure they're not suppose to do that. To bad he didn't flash some super secret unreleased test software on it lol.
Click to expand...
Click to collapse
5.1 the dream

mikeyinid said:
That was very cool of him, I'm pretty sure they're not suppose to do that. To bad he didn't flash some super secret unreleased test software on it lol.
Click to expand...
Click to collapse
They actually are setup to do it. The Bestbuy Samsung experience shops can install firmware on any Samsung device as long as it has not been modified. They cannot reset Knox.

altimax98 said:
They actually are setup to do it. The Bestbuy Samsung experience shops can install firmware on any Samsung device as long as it has not been modified. They cannot reset Knox.
Click to expand...
Click to collapse
Well , to be honest, they should be doing all warranty work and claims and things right there as well. They have such ****ttty customer service that I'd much rather go somewhere so that I could actually discuss things in person. Kinda like......... APPLE!! That's really the only reason I keep these Crapple devices around, because they will swap out anything 4 me on a dime and it can be done in less than an hour. No 2-3-4 weeks without a phone. It seems like being 2015, Samsung should be able to compete in that sense. Oh well, Sorry, I am just daydreaming over here. :cyclops:

Anybody have a tar file that we can flash in Odin for the 5.1.1 update? I just got my phone today and it wont take the update from T-Mobile. It downloaded all the files and started installing in recovery,then it rebooted and stated the update failed. My phone is bone stock factory and has never been modified in any way. Any help is greatly appreciated!!

PS4AndroidHacker said:
Anybody have a tar file that we can flash in Odin for the 5.1.1 update? I just got my phone today and it wont take the update from T-Mobile. It downloaded all the files and started installing in recovery,then it rebooted and stated the update failed. My phone is bone stock factory and has never been modified in any way. Any help is greatly appreciated!!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=62486197

Update N6 AT&T to Marshmallow?

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.

face unlocked stopped working?

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

Need to recover data - phone stuck in booting screen

For some reason my Pixel 4XL got stuck on the "G" screen. I realize this means I'm probably going to have to reset my phone, but I really need to recover the photos and videos that are on it. I know, I know, I need to back-up regularly. But I didn't, and now my kid has no digital memories of his pet that died last weekend. I followed some instructions posted by "Techno Bill" a few years ago to sideload an OTA image onto the phone, and everything went very smoothly, but when I re-booted the phone, it is still stuck on the G screen. The first time I got a "No error" error (...?),so I checked for a more recent version of the image and found one. Tried that one twice, seemed like it worked both times, but both times I was still stuck on the G screen. I'm wondering if its because I already had *210305.006* on my phone, which is the one I'm trying to sideload. Any ideas?
{
"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"
}

ChrisH78 said:
For some reason my Pixel 4XL got stuck on the "G" screen. I realize this means I'm probably going to have to reset my phone, but I really need to recover the photos and videos that are on it. I know, I know, I need to back-up regularly. But I didn't, and now my kid has no digital memories of his pet that died last weekend. I followed some instructions posted by "Techno Bill" a few years ago to sideload an OTA image onto the phone, and everything went very smoothly, but when I re-booted the phone, it is still stuck on the G screen. The first time I got a "No error" error (...?),so I checked for a more recent version of the image and found one. Tried that one twice, seemed like it worked both times, but both times I was still stuck on the G screen. I'm wondering if its because I already had *210305.006* on my phone, which is the one I'm trying to sideload. Any ideas?
View attachment 5253543
View attachment 5253545
Click to expand...
Click to collapse
Are you rooted? Did you ever enable usb debugging in developer settings?

Tulsadiver said:
Are you rooted? Did you ever enable usb debugging in developer settings?
Click to expand...
Click to collapse
I'm not, I haven't rooted a phone since my first gen Galaxy, haha. The only things I've done so far are in this instruction (https://drive.google.com/file/d/0Bz6x7k-VkpUJMlZ1aEliVnhMOHM/view). Installed ADB, Fastboot, and necessary drivers. Downloaded an OTA file from developers.google.com, and installed it using the "Apply Update from ADB" option in the recovery menu. My biggest concern is the data. If I can get those photos and videos off I'm perfectly happy nuking the install afterwards and going back to stock. Would rooting it wipe the data?

ChrisH78 said:
I'm not, I haven't rooted a phone since my first gen Galaxy, haha. The only things I've done so far are in this instruction (https://drive.google.com/file/d/0Bz6x7k-VkpUJMlZ1aEliVnhMOHM/view). Installed ADB, Fastboot, and necessary drivers. Downloaded an OTA file from developers.google.com, and installed it using the "Apply Update from ADB" option in the recovery menu. My biggest concern is the data. If I can get those photos and videos off I'm perfectly happy nuking the install afterwards and going back to stock. Would rooting it wipe the data?
Click to expand...
Click to collapse
Yes, you have to unlock the bootloader and that wipes the data. Your phone would have to be able to boot up for that to happen. Just wondering if you flashed something that didn't agree with your phone. Without usb debugging enabled, I don't know a way to pull anything off.

ChrisH78 said:
For some reason my Pixel 4XL got stuck on the "G" screen. I realize this means I'm probably going to have to reset my phone, but I really need to recover the photos and videos that are on it. I know, I know, I need to back-up regularly. But I didn't, and now my kid has no digital memories of his pet that died last weekend. I followed some instructions posted by "Techno Bill" a few years ago to sideload an OTA image onto the phone, and everything went very smoothly, but when I re-booted the phone, it is still stuck on the G screen. The first time I got a "No error" error (...?),so I checked for a more recent version of the image and found one. Tried that one twice, seemed like it worked both times, but both times I was still stuck on the G screen. I'm wondering if its because I already had *210305.006* on my phone, which is the one I'm trying to sideload. Any ideas?
Click to expand...
Click to collapse
At this point you may be lucky to recover your phone at all. It would be helpful to know how you got to this point. You started with the "rescue ota" method which is the last ditch effort for most to reflash a phone with a locked bootloader. Knowing what happened beforehand would be useful information. Since you have flashed the full OTA numerous times via ADB, the only thing left is a factory data reset. At some point you will have to abandon the data and move to the next step in recovering your phone. Even if you never intend to root your phone, you should ALWAYS unlock the bootloader so when the **** hits the fan you have more options to save your data. Wishing you a successful recovery.

v12xke said:
At this point you may be lucky to recover your phone at all. It would be helpful to know how you got to this point. You started with the "rescue ota" method which is the last ditch effort for most to reflash a phone with a locked bootloader. Knowing what happened beforehand would be useful information. Since you have flashed the full OTA numerous times via ADB, the only thing left is a factory data reset. At some point you will have to abandon the data and move to the next step in recovering your phone. Even if you never intend to root your phone, you should ALWAYS unlock the bootloader so when the **** hits the fan you have more options to save your data. Wishing you a successful recovery.
Click to expand...
Click to collapse
Thanks for the reply. I basically got here because every Google post I saw said that I was screwed and would be lucky to save my phone, forget about the data. Except for one, and that one told me to go this route. In the future I'll absolutely unlock my bootloader, but just for my own edification, where would have been a good first place to start with a locked bootloader?

v12xke said:
Wishing you a successful recovery.
Click to expand...
Click to collapse
Would the mount /system option be of any use to me?

ChrisH78 said:
Thanks for the reply. I basically got here because every Google post I saw said that I was screwed and would be lucky to save my phone, forget about the data. Except for one, and that one told me to go this route. In the future I'll absolutely unlock my bootloader, but just for my own edification, where would have been a good first place to start with a locked bootloader?
Click to expand...
Click to collapse
You would use fastboot to dirty flash a full image, removing the wipe flag (-w) from the flash-all script beforehand. This wipes and replaces the boot partition but leaves your data intact.

ChrisH78 said:
Would the mount /system option be of any use to me?
Click to expand...
Click to collapse
No. Even unlocked and rooted we cannot write to the system partition anymore. Any luck on getting your phone working again?