Database Develop

[Q] Verizon G2 acting crazy after FDR

Hello, and thank you in advance for any support on my issues. I have done some extensive searching regarding my issues but am coming up empty. I consider myself a relative noob and am now facing multiple questions and issues with my phone.
Device Info:
Verizon LG G2
Rooted, stock
Android Version 4.2.2
Software Version VS98011A
I did not personally root my phone - I paid to have it done for me remotely.
I have been using Titanium Backup to freeze or remove applications and bloat.
I also have used the paid version of ROM Manager for when/if I need it - I have never personally flashed a custom ROM or Kernel, etc.
I did personally side load the HotSpotProvision apk to use the Verizon Hotspot feature with my unlimited data and it worked great.
I also have the Verizon versions of the Galaxy S5 and LG G3. I recently did a 4G LTE speed test with all 3 devices and got insane speeds (attached) with the S5 and G5 but not the G2. I tried researching whether KitKat was the reason for being able to access XLTE speeds or not but couldn't find anything definitive there either. So I decided to attempt the Verizon OTA KitKat update for the G2. Here is where my nightmare begins...
To my knowledge, no backup had ever been done to my phone unless it was done when it was rooted. Regardless, I wanted to do one before making any changes to the phone but I have a feeling I was unsuccessful. After more searches on how to perform a backup and trying 6 times with ROM Manager (unsuccessfully), I decided to try the physical key option to launch into Recovery Mode. Based on what I did find online, this method would take you to the FDR screen but not to worry and to continue because it would actually take you to the TWRP home screen. Well, it did not. My phone reset and I lost everything in my gallery, etc. On reboot, I did see that I was still rooted but not able to do the OTA (because I am still rooted, I assume?). I have done 2 more FDRs and now my phone is acting out of it's mind.
Issues:
Touch screen unresponsive or turning off/on all by itself
Contact info not syncing to native messaging app
Previously installed free or purchased apps not reinstalling (although they did after the first FDR)
Can't receive OTA
At this point, I might as well do whatever I need to do to get things working correctly since I'm already reset.
My questions are:
How can I check if I do in fact have, or don't have a backup that I can access?
How do I create a backup so this doesn't happen again?
What do I need to do to get the OTA and will KK allow me to access the XLTE band?
Can I still do a Factory Data Reset and get back to the true "out of the box" version of the phone? If so, how?
I think that's it for now!! Thanks for any help that can be offered. Cheers.
{
"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"
}

Sounds like whoever you paid to root the phone didn't install a recovery or you lost it from applying the KK OTA.
You can install TWRP using Autorec if you're on KK (4.4.2) now.
http://forum.xda-developers.com/showthread.php?t=2715496
Personally I'd start clean to see if it clears up your issues, the touch screen thing sounds more like a hardware problem. If all is well after returning it to stock, re-root it yourself using ioroot/towelroot and install a recovery again and make a back up to save somewhere once you get it set up the way you want it.
http://forum.xda-developers.com/showthread.php?t=2448960

Thank you very much, Matt.
KK never did get installed...I am still on 4.2.2 and every time I try to go back to stock through various methods on this site I get the attached image. I would definitely like to start with the out-of-box device again, OTA KK and re-root but I'm not even having any luck with that either. This whole project began with the thinking that I needed KK to access the XLTE network since I was getting incredible speeds with the G3 and S5...do you know if that is accurate?
mjones73 said:
Sounds like whoever you paid to root the phone didn't install a recovery or you lost it from applying the KK OTA.
You can install TWRP using Autorec if you're on KK (4.4.2) now.
http://forum.xda-developers.com/showthread.php?t=2715496
Personally I'd start clean to see if it clears up your issues, the touch screen thing sounds more like a hardware problem. If all is well after returning it to stock, re-root it yourself using ioroot/towelroot and install a recovery again and make a back up to save somewhere once you get it set up the way you want it.
http://forum.xda-developers.com/showthread.php?t=2448960
Click to expand...
Click to collapse

lantzman said:
Thank you very much, Matt.
KK never did get installed...I am still on 4.2.2 and every time I try to go back to stock through various methods on this site I get the attached image. I would definitely like to start with the out-of-box device again, OTA KK and re-root but I'm not even having any luck with that either. This whole project began with the thinking that I needed KK to access the XLTE network since I was getting incredible speeds with the G3 and S5...do you know if that is accurate?
Click to expand...
Click to collapse
Follow the directions in the return to stock guide provided, see if you can get the phone in download mode...
Install the LG Flash Tool and drivers then try this.
1) Go ahead and put phone in Download mode by VolUp + plug in USB to PC. At this time your computer should install the device, if it hadnt already. Open device manager to check if un der "Ports (Com and LPT)" it shows up as LGE AndroidNet for VZW USB Serial Port (COM##) IF the COM number is anything other than 41, which it probably will be. Right click it in device manager and choose peroperties, then go to port settings tab and click advanced. On the bottom choose COM41 and hit OK. (if you get an error about it being in use I'll write more about that later)
hit ok and all that and close out the properties.
Click to expand...
Click to collapse

OK, I'm on download mode, the computer installed drivers and I changed to COM41. Phone still shows "Firmware Update" screen and 0% on progress. Where do I go from here?
mjones73 said:
Follow the directions in the return to stock guide provided, see if you can get the phone in download mode...
Install the LG Flash Tool and drivers then try this.
Click to expand...
Click to collapse

lantzman said:
OK, I'm on download mode, the computer installed drivers and I changed to COM41. Phone still shows "Firmware Update" screen and 0% on progress. Where do I go from here?
Click to expand...
Click to collapse
Did you unplug and replug in the phone?

I think I got it done. Phone is downloading KK now. This is where I would get the error on the install because I was rooted. Did the process I just go through unroot me?
mjones73 said:
Did you unplug and replug in the phone?
Click to expand...
Click to collapse

OK, it's doing the OTA!
lantzman said:
I think I got it done. Phone is downloading KK now. This is where I would get the error on the install because I was rooted. Did the process I just go through unroot me?
Click to expand...
Click to collapse

lantzman said:
I think I got it done. Phone is downloading KK now. This is where I would get the error on the install because I was rooted. Did the process I just go through unroot me?
Click to expand...
Click to collapse
Yes, returns the phone to out of the box stock basically. Now if you want to re-root, you can use ioroot25 or towelroot.
ioroot25 - http://forum.xda-developers.com/showpost.php?p=48709232&postcount=869
Once rooted, use autorec to install a recovery (kitkat requires some additional steps besides just flashing a recovery and it does them for you)
http://forum.xda-developers.com/showthread.php?t=2715496
Make sure you grab the vs980 version of autorec.

So I can't create a stock recovery prior to root, correct...so that I can go back to stock from root?
mjones73 said:
Yes, returns the phone to out of the box stock basically. Now if you want to re-root, you can use ioroot25 or towelroot.
ioroot25 - http://forum.xda-developers.com/showpost.php?p=48709232&postcount=869
Once rooted, use autorec to install a recovery (kitkat requires some additional steps besides just flashing a recovery and it does them for you)
http://forum.xda-developers.com/showthread.php?t=2715496
Make sure you grab the vs980 version of autorec.
Click to expand...
Click to collapse

lantzman said:
So I can't create a stock recovery prior to root, correct...so that I can go back to stock from root?
Click to expand...
Click to collapse
No, you need to root it first if you want to back it up.

OK, so I can root with the Towelroot app and use Autorec for backup. Does it give me TWRP?
mjones73 said:
No, you need to root it first if you want to back it up.
Click to expand...
Click to collapse

and where do I find the process for installing Autorec?
lantzman said:
OK, so I can root with the Towelroot app and use Autorec for backup. Does it give me TWRP?
Click to expand...
Click to collapse

sorry, I was making this way too difficult. I ran Towelroot and Autorec and I believe we are good to go. Now, when would I use Autorec...when I have an issue flashing other ROMs, kernels, etc?
How do you prefer to receive donations? I really appreciate your help...you've been great!

lantzman said:
sorry, I was making this way too difficult. I ran Towelroot and Autorec and I believe we are good to go. Now, when would I use Autorec...when I have an issue flashing other ROMs, kernels, etc?
How do you prefer to receive donations? I really appreciate your help...you've been great!
Click to expand...
Click to collapse
Autorec is a one and done, you can remove it now, it installs TWRP, that's all you need it for. You should now be able to get into recovery using the same sequence you used before if it installed clean for you. Any flashing of rom, kernels, etc would be via TWRP.
One last note, don't install any OTA's while you're rooted.
You don't have to donate anything but if you really want to, just hit the Donate to Me button under my name.

OK, thank you. One last question: it seems the touch screen may be starting to fail. If I needed to unroot or at least show unrooted to turn it in for a warranty replacement, can that be done and if so, how?

lantzman said:
OK, thank you. One last question: it seems the touch screen may be starting to fail. If I needed to unroot or at least show unrooted to turn it in for a warranty replacement, can that be done and if so, how?
Click to expand...
Click to collapse
This will get you back to stock. Make sure you read the first page before you do this...if needed. FYI: Device needs to be off to get into download mode and you should be in download mode before installing the drivers. http://forum.xda-developers.com/showthread.php?t=2448960
Sent from my XDABBEB VS98025A v2.0.0 using XDA free mobile app

Perfect, that's the process I just did from root so I could get the KK OTA. Just wasn't sure if there was an easier way to just show "unrooted" in "about phone" before having them look at it. Love your call sign/avatar. Huge Huge Huge Zeppelin fan here! Ever since hearing "Stairway" in 7th grade! Mght need to see if "LantZeppelin" is available! Thanks again.

Force closes after 5.1 update

I just received the 5.1 update today. I'm on sprint, if that matters. Immediately after the update, I'm getting bombarded with these force closes, immediately returning after hitting either "ok" or "report". It will continue for 3 or 4 minutes, then clear up for a few minutes, then returning when I open an app.
I'm stock, not rooted. Since I'm not rooted, I'm not sure what I can do other than reboot or factory reset? This is the first phone I haven't rooted since I got into android. I'm feeling like I should just root /wipe/flash, but before I do, any other suggestions to quickly clear up the force closes? Thanks!
{
"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"
}

I had the same message after updating to 5.1 from 5.0 when trying to use my camera app.
I had rebooted the phone, and the problem went away.

3f62011 said:
I had the same message after updating to 5.1 from 5.0 when trying to use my camera app.
I had rebooted the phone, and the problem went away.
Click to expand...
Click to collapse
Thanks! Unfortunately that hasn't solved it. I booted into the stock recovery and wiped cache. Still no dice. I'll factory reset next I guess!

I guess if you don't want to root I would get some cache cleaning apps
Sent from my Google N6 on VZ

Well I unlocked the bootloader and flashed the most updated stock image using fastboot, manually. All is well now. It took longer to get my computer and drivers working than actually fixing the phone. Now that my bootloader is unlocked, I guess it's time to root. Thanks for the advice.

Do yourself a favor and get the Nexus toolkit you can run commands by hand or let the tool do it for you.
http://www.wugfresh.com/nrt/
WugFresh trolls this forum pretty often too
Sent from my Google N6 on VZ

You don't need root or any special "app" to see what is going on.
You need a LOGCAT.
And to post it here so that somebody who understands it can interpret it.

doitright said:
You don't need root or any special "app" to see what is going on.
You need a LOGCAT.
And to post it here so that somebody who understands it can interpret it.
Click to expand...
Click to collapse
I 100% percent agree with you but the reality is you could reload the phone and reset everything before you get a definitive answer.
Sent from my Google N6 on VZ

DebianDog said:
I 100% percent agree with you but the reality is you could reload the phone and reset everything before you get a definitive answer.
Click to expand...
Click to collapse
I don't agree. At least not entirely. There are enough people here to interpret a logcat, it could be done in seconds.
But it does come down to how significant of a setup you're dealing with, and how well equipped you are to understand and manage a problem.
My wife's hammerhead did something weird not long ago, google applications continuous force close. A quick examination of the logcat yielded a "can not downgrade database from version 3 to 2" problem on the gms package. Kind of weird, since it just happened out of the blue, she's running factory + root on the thing. So I wiped the database, rebooted, and its back to normal. Took 2 minutes. A wipe and reload and reconfigure would have taken hours.
For my own devices, last time I did a "wipe" was in... 2012. I did a full backup and restore from my last phone to my N6, wiped/adjusted/reset whatever databases and configurations didn't match between the Samsung Relay custom 5.0 build (I did userdata "upgrade" the whole way up from 4.0 on that device, without wiping even ONCE) and the N6. Saved tons of time.

In the time it took you to respond to this message I could have backed up my whole phone on titanium backup. Wiped it. flashed it. Reroot it and restored all my settings and applications. That's my point.
Sent from my Google N6 on VZ

DebianDog said:
In the time it took you to respond to this message I could have backed up my whole phone on titanium backup. Wiped it. flashed it. Reroot it and restored all my settings and applications. That's my point.
Click to expand...
Click to collapse
Except that in restoring your backup, you have also restored whatever the problem was, and are now back to square one.

doitright said:
Except that in restoring your backup, you have also restored whatever the problem was, and are now back to square one.
Click to expand...
Click to collapse
Maybe or maybe not you mean. Caches inconsistent with the current version how Android are usually the cause of this or caches that got corrupted in some manner . And as you know you never restore caches.
My 5 years experience with Android dictates that these problems are usually EASILY resolved with a wipe of the cache/phone. perhaps your personal evidence is different.
Yes I personally would fire up system info and look at the logs before I wiped my caches and if that didn't work I would wipe the phone.
Sent from my Google N6 on VZ

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

Droid Turbo (XT1254) autoiniroot problem

Hey.
I have a Droid Turbo XT1254 with bootloader locked (I am planning to unlock soon).
Recently, I stumbled across the thread and saw that someone had made rooting MCG25.251-5-5 possible and it made me want to try it out.
Anyways, I downloaded all the files (magisk and autoinitroot) and was able to root my phone just fine.
I tried giving Super user permission to some apps, and it worked flawlessly. I then tried to install Magisk module but oddly enough it failed.
It gave me an error that magisk was not properly installed. Also the SafetyNet check failed.
I decided to uninstall root, factory reset my device and root the device again.
Now the thing is that when I booted back into fastboot and ran the command that was meant to uninstall the root, it failed.
Obviously, I made sure that I was typing the correct command, I didn't even miss the "" marks. But it still didn't work.
It only gave me an error that the command 'confirm' doesn't exist.
I tried running the autoinit script and I booted just fine.
But the problem is that magisk isn't working properly and I'm unable to uninstall the autoinit root.
Any help will be greatly appreciated.
Also, Im using minimal adb and fast boot setup. Not sure if that's what causing the uninstall to fail or not.
TL; DR: Magisk doesn't work properly after doing the autoinitroot and I'm unable to uninstall the root by using the command that was mentioned in the original post.
Thanks for taking the time to read it

DuringSummer said:
Hey.
I have a Droid Turbo XT1254 with bootloader locked (I am planning to unlock soon).
Recently, I stumbled across the thread and saw that someone had made rooting MCG25.251-5-5 possible and it made me want to try it out.
Anyways, I downloaded all the files (magisk and autoinitroot) and was able to root my phone just fine.
I tried giving Super user permission to some apps, and it worked flawlessly. I then tried to install Magisk module but oddly enough it failed.
It gave me an error that magisk was not properly installed. Also the SafetyNet check failed.
I decided to uninstall root, factory reset my device and root the device again.
Now the thing is that when I booted back into fastboot and ran the command that was meant to uninstall the root, it failed.
Obviously, I made sure that I was typing the correct command, I didn't even miss the "" marks. But it still didn't work.
It only gave me an error that the command 'confirm' doesn't exist.
I tried running the autoinit script and I booted just fine.
But the problem is that magisk isn't working properly and I'm unable to uninstall the autoinit root.
Any help will be greatly appreciated.
Also, Im using minimal adb and fast boot setup. Not sure if that's what causing the uninstall to fail or not.
TL; DR: Magisk doesn't work properly after doing the autoinitroot and I'm unable to uninstall the root by using the command that was mentioned in the original post.
Thanks for taking the time to read it
Click to expand...
Click to collapse
1) why are you waiting to unlock your bootloader? Temp root is unstable and won't give you what you want.
2) of course Magisk won't work until you unlock your bootloader. Why would you think otherwise? On Motorola phones you have to unlock the bootloader to make changes like permanent root, install custom recovery, etc. Magisk just hides that.
3) you SAY you typed the correct command but after having a back-and-forth for two days over three pages with someone else who claimed the same thing and was WRONG, I'm skeptical.
Type exactly what you think is the correct command. Don't copy and paste anything. Actually type it out.
Better yet, post screenshot. That's how we proved to the other guy he was not reading what we had written.
"Oh, I didn't know."
Yes he did. It was in post #2, the very FIRST reply in the thread, which I wrote. And I told him over and over to go re-read that post!

Thanks for replying.
The answer to the first question is that I don't have $$$ right now. Will do it next month or so.
#2: Hahah. I did read that thread, and I'm pretty sure I'm not making that mistake, In any case I'll attach screenshots.

This is the screenshot. This time I tried specifying the directory to the fastboot.exe that came with autoinitroot, still no luck. Same error comes up regardless of whether I specify the directory or just use normal fastboot the came with minimal ADB.
And yes. I did it while I was in fastboot mode.
For some reason the app won't let me upload screenshot. Here is the link instead
http://i.imgur.com/Y5L5kvw.png

ChazzMatt said:
1) why are you waiting to unlock your bootloader? Temp root is unstable and won't give you what you want.
2) of course Magisk won't work until you unlock your bootloader. Why would you think otherwise? On Motorola phones you have to unlock the bootloader to make changes like permanent root, install custom recovery, etc. Magisk just hides that.
3) you SAY you typed the correct command but after having a back-and-forth for two days over three pages with someone else who claimed the same thing and was WRONG, I'm skeptical.
Type exactly what you think is the correct command. Don't copy and paste anything. Actually type it out.
Better yet, post screenshot. That's how we proved to the other guy he was not reading what we had written.
"Oh, I didn't know."
Yes he did. It was in post #2, the very FIRST reply in the thread, which I wrote. And I told him over and over to go re-read that post!
Click to expand...
Click to collapse
Yeah but in the original thread by autoprime, users have posted that they managed to install modules like "xposed systemless" etc. No reason it shouldn't work on mine.
Edit: Furthermore, autoptime himself mentioned that we can use custom magisk script to avoid boot loop, as far as I understand that's only possible when magisk recognizes modules.
Thing is that I have root, I can even use apps like titanium backup and whatnot. I can't use the script he mentioned unless magisk allows me to install something.

DuringSummer said:
This is the screenshot. This time I tried specifying the directory to the fastboot.exe that came with autoinitroot, still no luck. Same error comes up regardless of whether I specify the directory or just use normal fastboot the came with minimal ADB.
And yes. I did it while I was in fastboot mode.
For some reason the app won't let me upload screenshot. Here is the link instead
http://i.imgur.com/Y5L5kvw.png
Click to expand...
Click to collapse
{
"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"
}
Your screenshot shows you typed "confirm". That's not the right command. It's "config".
fastboot oem config fsg-id ""

ChazzMatt said:
Your screenshot shows you typed "confirm". That's not the right command. It's "config".
fastboot oem config fsg-id ""
Click to expand...
Click to collapse
Oh. Hell. I feel stupid. I kinda copied from one the comments in OP. Will update brb.

Still doesn't work. This time it gave me error (bootloader) something-suffixes: false.
Etc etc. Will post screenshot.
EDIT: It WORKED. I placed the autoinitroot to desktop and changed the directory along with folder names. Ran the command, seems to have worked. Thanks anyways.
Probably had something to do with really long directory name. Idk.

DuringSummer said:
Yeah but in the original thread by autoprime, users have posted that they managed to install modules like "xposed systemless" etc. No reason it shouldn't work on mine.
Click to expand...
Click to collapse
Show me examples of that with Motorola phones.
I also have extensive experience with LG phones, and many of those (like LG G2 and LG G3) do not need bootloader unlock to root and install custom recovery. Whereas, Motorola phones require unlocked bootloader.
---------- Post added at 03:27 PM ---------- Previous post was at 03:21 PM ----------
DuringSummer said:
Still doesn't work. This time it gave me error (bootloader) something-suffixes: false.
Etc etc. Will post screenshot.
EDIT: It WORKED. I placed the autoinitroot to desktop and changed the directory along with folder names. Ran the command, seems to have worked. Thanks anyways.
Probably had something to do with really long directory name. Idk.
Click to expand...
Click to collapse
Yes, the suffixes errors are normal. Only by rebooting do you see if it worked.

ChazzMatt said:
Show me examples of that with Motorola phones.
I also have extensive experience with LG phones, and many of those (like LG G2 and LG G3) do not need bootloader unlock to root and install custom recovery. Whereas, Motorola phones require unlocked bootloader.
Click to expand...
Click to collapse
http://i.imgur.com/u06AaAV.png
http://i.imgur.com/7AHc5Bk.png
He explicitly mentioned that about bootloader locked Moto. Also the tool only works on Moto so.

DuringSummer said:
http://i.imgur.com/u06AaAV.png
http://i.imgur.com/7AHc5Bk.png
He explicitly mentioned that about bootloader locked Moto. Also the tool only works on Moto so.
Click to expand...
Click to collapse
Well, I know he was wrong about one thing. When the phone reboots it doesn't just boot into a stock system. Instead it bootloops and gets hung on the Moto logo. It never finishes booting until you run that end temp root command in fastboot.
Go to the thread and ask him how to do what he describes.... He is an expert and knows a lot more than me.
But also remember if your phone reboots in any way while you are away from your computer with fastboot installation, your phone will be totally useless until you get back to your computer and temp re-root or run that end temp root command.

ChazzMatt said:
Well, I know he was wrong about one thing. When the phone reboots it doesn't just boot into a stock system. Instead it bootloops and gets hung on the Moto logo. It never finishes booting until you run that end temp root command.
Click to expand...
Click to collapse
Oh that. What he meant was that if you place the custom magisk script in the right folder it will avoid boot loop and will boot into stock system, from there you'll have to use autoinitroot tool from pc again to re-root it, the script is handy if you're going somewhere and won't have access to pc. In which case, even if your phone gets turned off or reboots, it won't bootloop like crazy and you get access to stock system. Though you won't have root until you run autoroot script again from PC.
Also, it does provides full root. The only downside is that it isn't permanent. So as long as you're careful and don't mess with system and only use systemless modifications using magisk, you're safe. In worst case scenarios you'll only have to run the unroot command and factory reset to go back to 100% stock.
It's useful for those who can't get their bootloader unlocked.
Sadly, In my case magisk isn't working properly. That's why I'll factory reset and try again. Hopefully it'll work then.
Also do you by any chance know how and where to place custom scripts of magisk? Will be doing that after factory reset.
Also you helped a lot. Thanks, mate

DuringSummer said:
Oh that. What he meant was that if you place the custom magisk script in the right folder it will avoid boot loop and will boot into stock system, from there you'll have to use autoinitroot tool from pc again to re-root it, the script is handy if you're going somewhere and won't have access to pc. In which case, even if your phone gets turned off or reboots, it won't bootloop like crazy and you get access to stock system. Though you won't have root until you run autoroot script again from PC.
Also, it does provides full root. The only downside is that it isn't permanent. So as long as you're careful and don't mess with system and only use systemless modifications using magisk, you're safe. In worst case scenarios you'll only have to run the unroot command and factory reset to go back to 100% stock.
It's useful for those who can't get their bootloader unlocked.
Sadly, In my case magisk isn't working properly. That's why I'll factory reset and try again. Hopefully it'll work then.
Also do you by any chance know how and where to place custom scripts of magisk? Will be doing that after factory reset.
Also you helped a lot. Thanks, mate
Click to expand...
Click to collapse
His post #2 seems to talk about folders.

ChazzMatt said:
His post #2 seems to talk about folders.
Click to expand...
Click to collapse
Yeah. Saw that. Couldn't find those folders. Checked both root and normal storage.
Thanks anyway.

The whole temp root thing is really just a way to proceed with the bootloader unlock. to use temp root on any daily driver just seems like more trouble than its worth. Hurry up and find 25 bucks!!!
My opinion is that for the work that these guys do its a small price to pay and was money well spent

bigmatt503 said:
The whole temp root thing is really just a way to proceed with the bootloader unlock. to use temp root on any daily driver just seems like more trouble than its worth. Hurry up and find 25 bucks!!!
My opinion is that for the work that these guys do its a small price to pay and was money well spent
Click to expand...
Click to collapse
Actually, I don't have any problem paying 25 bucks. The thing is that I'm planning to buy a new phone. Seems really pointless spending 25$ on something that I'll replace in a few months. At first I thought that I should get it unlocked, however, this phone is 3 years old. I decided that I should upgrade to current technology.

ChazzMatt said:
Show me examples of that with Motorola phones.
I also have extensive experience with LG phones, and many of those (like LG G2 and LG G3) do not need bootloader unlock to root and install custom recovery. Whereas, Motorola phones require unlocked bootloader.
---------- Post added at 03:27 PM ---------- Previous post was at 03:21 PM ----------
Yes, the suffixes errors are normal. Only by rebooting do you see if it worked.
Click to expand...
Click to collapse
Caution thread jacking...... since you are very familiar with LG phones. What are the chances of the verizon g6 ever getting root?
Sent from my VS988 using XDA-Developers Legacy app

January Update

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!