Database Develop

[Q] Having trouble upgrading to 4.4.2 stock on Verizon

I have a Moto X Developer Edition rooted on Verizon with TWRP 2.6.3.1 and stock Android 4.4 on it. I have been trying to upgrade to 4.4.2 without doing the OTA, and without having to reflash TWRP.
So far, I have been unsuccessful.
I have tried Blur_Version.140.45.5.ghost_verizon.Verizon.en.US.zip (approximate file size 150MB) from multiple sources as all the posts I read keep saying that is what works. I have also tried a ~650MB version I found somewhere. In addition, I tried the upgrade located here: sbf.droid-developers.org/phone.php?device=0 which is called VZW_XT1060_4.4.2-KXA20.16-1.25.2_CFC_1FF.xml.zip (It's the 4.4.2 upgrade listed under Verizon US).
All of these fail. In TWRP, about 2-3 steps after it verified md5, it simply says "Failed" with no explanation as to why.
Here is my question:
How can I upgrade to 4.4.2 without a data wipe, and without having to reflash TWRP?
I have no interest in going to a ROM, I want to stay stock, and if I must, I will reflash the recovery if I have to, but I *really* don't want to.

Flash stock recovery, take the OTA, flash TWRP again.
It's so simple, so painless, so quick and it will not wipe your data.

tcrews said:
Flash stock recovery, take the OTA, flash TWRP again.
It's so simple, so painless, so quick and it will not wipe your data.
Click to expand...
Click to collapse
I was hoping to avoid that (Yep, I really am that lazy...) but that's what I was going to do tonight if I couldn't get my hands on a .zip to flash.
Ironically, I bought the Dev Edition specifically so things like this would be easy.

It is easy.....just need to do it.
I support my sister, her husband and my wife (as well as my own) who all have Moto X's. 2 seconds to flash recovery, however long it takes for the OTA to install and reboot and then 2 seconds to flash TWRP again. Heck...I'd just leave the stock recovery in place since it's not needed if you don't plan on flashing any ROMs. The OTA doesn't even remove root.

tcrews said:
It is easy.....just need to do it.
I support my sister, her husband and my wife (as well as my own) who all have Moto X's. 2 seconds to flash recovery, however long it takes for the OTA to install and reboot and then 2 seconds to flash TWRP again. Heck...I'd just leave the stock recovery in place since it's not needed if you don't plan on flashing any ROMs. The OTA doesn't even remove root.
Click to expand...
Click to collapse
Oh, that last bit is good to know! Well, I think even if it did remove root, getting it back is easy on the DE.
I think you're right though, I probably won't install TWRP again, I specifically got the Moto X because I was tired of messing around with stuff when I all I want is a rooted, stock Android experience.

So, after several hours of messing with this, and thinking the stock recovery had gotten messed up because the instructions I had for getting in to it were wrong, I finally got the OTA installing...
and it fails.
I don't know why, I haven't seen the error (I'm not looking at the phone when it fails).
So... Awesome.

Taegost said:
So, after several hours of messing with this, and thinking the stock recovery had gotten messed up because the instructions I had for getting in to it were wrong, I finally got the OTA installing...
and it fails.
I don't know why, I haven't seen the error (I'm not looking at the phone when it fails).
So... Awesome.
Click to expand...
Click to collapse
Are there files out so you can just flash 4.4.2 with mfastboot? Would be easiest.

kj2112 said:
Are there files out so you can just flash 4.4.2 with mfastboot? Would be easiest.
Click to expand...
Click to collapse
I assume so, but I haven't found any instructions specifically saying how to do that, except for the ones that tell you how to return to stock without using RSD Lite.
Unfortunately, I don't know enough about how all this stuff works to be able to figure out which bits and pieces to put together to get upgraded without wiping my data.
What really pisses me off is that I specifically bought this phone so I wouldn't have issues like this, and here I am...
BTW: The only thing the error says is "Error". That's it, nothing else.

Taegost said:
I assume so, but I haven't found any instructions specifically saying how to do that, except for the ones that tell you how to return to stock without using RSD Lite.
Unfortunately, I don't know enough about how all this stuff works to be able to figure out which bits and pieces to put together to get upgraded without wiping my data.
What really pisses me off is that I specifically bought this phone so I wouldn't have issues like this, and here I am...
BTW: The only thing the error says is "Error". That's it, nothing else.
Click to expand...
Click to collapse
This guide has a return to stock section. It will tell you how to flash the stock firmware.
http://forum.xda-developers.com/showthread.php?t=2603358
Unfortunately the moto x is not a simple phone for tinkering with, like say a nexus, even the dev edition.
It can be easier once you do fully understand everything. Just gotta know what applies to you...meaning mostly the locked versus unlocked methods for everything.
After owning an s2, a moto x and now an n5 (n7 too...but I don't tinker with it really....its a family device) I've come to the mind set that for flashers and rooters.....nothing at all beats owning a nexus. Every other device has some limitations that a nexus won't have.

kj2112 said:
This guide has a return to stock section. It will tell you how to flash the stock firmware.
http://forum.xda-developers.com/showthread.php?t=2603358
Unfortunately the moto x is not a simple phone for tinkering with, like say a nexus, even the dev edition.
It can be easier once you do fully understand everything. Just gotta know what applies to you...meaning mostly the locked versus unlocked methods for everything.
After owning an s2, a moto x and now an n5 (n7 too...but I don't tinker with it really....its a family device) I've come to the mind set that for flashers and rooters.....nothing at all beats owning a nexus. Every other device has some limitations that a nexus won't have.
Click to expand...
Click to collapse
Yeah, that's the page I was talking about when I said I found the full instructions...
I specifically bought this phone because I didn't want to mess around with it like this, I just wanted to root it so I could use Titantium Backup and be done with it... and now I'm stuck at a halfway point.... Again...
I'll probably end up just doing the full wipe and manually flash to 4.4.2 (RSD Lite doesn't see my device... yay), since I have gone from my mute button not working (with 4.2.2), to a really bad echo for whomever I'm talking to when it's on speakerphone (Even when speakerphone is muted... THAT made for a fun conference call...).

Taegost said:
Yeah, that's the page I was talking about when I said I found the full instructions...
I specifically bought this phone because I didn't want to mess around with it like this, I just wanted to root it so I could use Titantium Backup and be done with it... and now I'm stuck at a halfway point.... Again...
I'll probably end up just doing the full wipe and manually flash to 4.4.2 (RSD Lite doesn't see my device... yay), since I have gone from my mute button not working (with 4.2.2), to a really bad echo for whomever I'm talking to when it's on speakerphone (Even when speakerphone is muted... THAT made for a fun conference call...).
Click to expand...
Click to collapse
Flashing stock and rooting on an unlocked Moto x is basically the same as a nexus. It really is simple, once you are familiar with fastboot.
I guess there are toolkits that automate everything....like Samsung's Odin, and there's a few for nexus....but it really doesn't help anyone learn. And that's kinda what this hobby is all about.
But, I am sorry you're having trouble. Not sure what else to add. The guides are there, and they work. Usually. I can't think of anything to add to whats already been said.
Hope it works out for you!

kj2112 said:
Flashing stock and rooting on an unlocked Moto x is basically the same as a nexus. It really is simple, once you are familiar with fastboot.
I guess there are toolkits that automate everything....like Samsung's Odin, and there's a few for nexus....but it really doesn't help anyone learn. And that's kinda what this hobby is all about.
But, I am sorry you're having trouble. Not sure what else to add. The guides are there, and they work. Usually. I can't think of anything to add to whats already been said.
Hope it works out for you!
Click to expand...
Click to collapse
I don't think I'm articulating my issue properly. I understand how to do everything in the guides you mentioned, they're a piece of cake. That doesn't solve my problem.
My problem is that I want to get to 4.4.2 WITHOUT wiping my data, but can't do the update via OTA or flashing in recovery. RSD Lite doesn't work either.
The ONLY option I have available to me is to manually push the update with fastboot, which I can definitely do with the instructions provided... But those instructions require me to wipe my data.
I know it's possible to apply the update with fastboot without requiring me to wipe my data, but I don't know enough about the inner workings to know which steps to skip, and which need to be modified, in order to make that happen.

Taegost said:
I don't think I'm articulating my issue properly. I understand how to do everything in the guides you mentioned, they're a piece of cake. That doesn't solve my problem.
My problem is that I want to get to 4.4.2 WITHOUT wiping my data, but can't do the update via OTA or flashing in recovery. RSD Lite doesn't work either.
The ONLY option I have available to me is to manually push the update with fastboot, which I can definitely do with the instructions provided... But those instructions require me to wipe my data.
I know it's possible to apply the update with fastboot without requiring me to wipe my data, but I don't know enough about the inner workings to know which steps to skip, and which need to be modified, in order to make that happen.
Click to expand...
Click to collapse
It says right at the bottom of the return to stock section in the guide I linked too.....you can skip
Fastboot erase user data
fastboot erase cache
Though if you have any problems after, you might have to do it again and do erase those, before spending time trying to figure out what's wrong.

kj2112 said:
It says right at the bottom of the return to stock section in the guide I linked too.....you can skip
Fastboot erase user data
fastboot erase cache
Though if you have any problems after, you might have to do it again and do erase those, before spending time trying to figure out what's wrong.
Click to expand...
Click to collapse
Wow... Attention to detail -5
Sorry about that, when I looked through that article, I skimmed through and saw that the "Return to Stock" section was (almost) identical to the other instructions I was reading...But I missed that last paragraph when I looked at the link you provided, the directions I was using referenced that article but did not include that last bit...
Thank you for your patients, I feel like a dumbass now *sheepish grin*

Taegost said:
Wow... Attention to detail -5
Sorry about that, when I looked through that article, I skimmed through and saw that the "Return to Stock" section was (almost) identical to the other instructions I was reading...But I missed that last paragraph when I looked at the link you provided, the directions I was using referenced that article but did not include that last bit...
Thank you for your patients, I feel like a dumbass now *sheepish grin*
Click to expand...
Click to collapse
No worries!! .
And sorry, its userdata. My keyboard split the words up.
---------- Post added at 11:16 AM ---------- Previous post was at 11:15 AM ----------
And, you may very well have issues doing that way. But its worth a shot first. If you do have issues, then you can erase those and repeat the process.

if using fastboot/mfastboot, I would still erase cache, as it doesn't touch your data/apps/config.
Another tip, use this mfastboot -> http://mark.cdmaforums.com/X-STUFF/Mfastboot-4.4.zip
or you can use RSDlite to flash the SBF, but there is a corresponding line for "erase data"
Two helpful links that will help explain what you saw...
Taking the OTA -> http://mark.cdmaforums.com/MotoX-OTA.html
various ways to Return to stock -> http://mark.cdmaforums.com/MotoX-ReturnToStock.html

kj2112 said:
No worries!! .
And sorry, its userdata. My keyboard split the words up.
---------- Post added at 11:16 AM ---------- Previous post was at 11:15 AM ----------
And, you may very well have issues doing that way. But its worth a shot first. If you do have issues, then you can erase those and repeat the process.
Click to expand...
Click to collapse
Alrighty, well I was able to successfully flash to 4.4.2 using the Fastboot instructions. Flashed TWRP afterwards and got root right back. Now that I know, this won't be a trial in the future (fingers crossed!)
Thanks for your help and patience

Trouble Decrypting Nexus 6

I recently received my nexus 6 a couple days ago and I LOVE it. The problem I am having at the moment is that I can't seem to get it to go decrypt. I downloaded the tool kit and my devices build isn't present. As a result, the tool kit it won't allow me to run the decrypt option on the fastboot window.
It's anyone running into this. My build is a LNX***.

First, what toolkit are you talking about?
Second, to decrypt the N6 you need to flash a modified boot image and then wipe your phone.
Thirdly, what's build LNX***?

Didgeridoohan said:
First, what toolkit are you talking about?
Second, to decrypt the N6 you need to flash a modified boot image and then wipe your phone.
Thirdly, what's build LNX***?
Click to expand...
Click to collapse
I'm using the nexus root toolkit . I have the flash on my computer and LNX07M is the build I have on the device. Maybe I should install a custom ROM first?
Nexus 6....man I missed being rooted.

KappaAce2010 said:
I'm using the nexus root toolkit . I have the flash on my computer and LNX07M is the build I have on the device. Maybe I should install a custom ROM first?
Nexus 6....man I missed being rooted.
Click to expand...
Click to collapse
You just need a custom kernel and a wipe.

another prime example of why you shouldn't use toolkits, if you don't understand what they are doing you shouldn't be using them.
To decrypt all you need to do is:
Backup your internal storage to a PC
Either use custom recovery to wipe everything including internal storage, install your rom and install a kernel that doesn't force
or
factory reset your phone, but before it boots up go back into recovery and flash a custom kernel that doesn't enforce

Circaflex said:
another prime example of why you shouldn't use toolkits, if you don't understand what they are doing you shouldn't be using them.
To decrypt all you need to do is:
Backup your internal storage to a PC
Either use custom recovery to wipe everything including internal storage, install your rom and install a kernel that doesn't force
or
factory reset your phone, but before it boots up go back into recovery and flash a custom kernel that doesn't enforce
Click to expand...
Click to collapse
Well if you to come off as a jerk, you have accomplished your goal. All you had to do was state what was needed and none of bs personal ideals you have. It's a Q & A section, so you should expect questions like this to arise.
Thank you for the input though.
Nexus 6....man I missed being rooted.

KappaAce2010 said:
Well if you to come off as a jerk, you have accomplished your goal. All you had to do was state what was needed and none of bs personal ideals you have. It's a Q & A section, so you should expect questions like this to arise.
Thank you for the input though.
Nexus 6....man I missed being rooted.
Click to expand...
Click to collapse
Although you're right, it is a personal ideal of many of us, I don't think he intended to come off as a jerk. But his point is that toolkits often remove the need for knowledge, which can become a problem for some users.
The good thing about nexus devices is that everything is pretty easy to do, so if you get stuck - continue to ask.

+1 to what rootSU said. And you should probably upgrade. That build is ancient and doesn't even have an official factory image (the reason it's not available in NRT).

Didgeridoohan said:
+1 to what rootSU said. And you should probably upgrade. That build is ancient and doesn't even have an official factory image (the reason it's not available in NRT).
Click to expand...
Click to collapse
I already plan on doing this anyway. Just time is conflicting with me at the moment.
rootSU said:
Although you're right, it is a personal ideal of many of us, I don't think he intended to come off as a jerk. But his point is that toolkits often remove the need for knowledge, which can become a problem for some users.
The good thing about nexus devices is that everything is pretty easy to do, so if you get stuck - continue to ask.
Click to expand...
Click to collapse
Well it happened, it's not going anywhere. Either way thanks guys for the advice. I should figure out everything tonight.
Nexus 6....man I missed being rooted.

Everything is a go. Fully decrypted and loving it. Thanks again.

How many people took the 5.1.1 and are stuck with the "locked" bootloader

If you didn't know the 5.1.1 update comes with a "locked" bootloader (G920T) that does not allow you to flash custom recoveries. I would like to know what your status is if you don't mind because I think the more people who are stuck like me the more developers will say we need to come up with a fix for flashing custom recoveries issue.

The bootloader isn't locked. Twrp just needs to be updated. Won't happen til kernel source for 5.1.1 drops

Did we really need another thread about this?
Edit: Please explain how someone "accidentally" upgraded from rooted 5.0.2 to 5.1.1

mikeyinid said:
The bootloader isn't locked. Twrp just needs to be updated. Won't happen til kernel source for 5.1.1 drops
Click to expand...
Click to collapse
That is why I put "locked" in quotes and no I am not sure of that the phone blocks any custom recovery installed and I explained in another thread how cf-auto-root is just a recovery that is why it isn't working either.

se1000 said:
Did we really need another thread about this?
Edit: Please explain how someone "accidentally" upgraded from rooted 5.0.2 to 5.1.1
Click to expand...
Click to collapse
What I mean by that is if you had no knowledge of the changes in the bootloader and the fact you can't downgrade

ethanscooter said:
Accidently* wasn't really paying while typing and what I mean by that is if you had no knowledge of the changes in the bootloader and the fact you can't downgrade
Click to expand...
Click to collapse
So what you meant is, "If you downloaded a 1.3GB file and ODIN'ed back to stock just to upgrade and ignored the big bold warning that you couldn't downgrade" OR "If you downloaded a 1.3GB file and ODIN'ed to a new version of android that there was an active thread where it was CLEAR there was no root method"
"Accidentally"

ethanscooter said:
That is why I put "locked" in quotes and no I am not sure of that the phone blocks any custom recovery installed and I explained in another thread how cf-auto-root is just a recovery that is why it isn't working either.
Click to expand...
Click to collapse
You don't have to take my word for it. But I'm telling you, the bootloader is not locked.

se1000 said:
So what you meant is, "If you downloaded a 1.3GB file and ODIN'ed back to stock just to upgrade and ignored the big bold warning that you couldn't downgrade" OR "If you downloaded a 1.3GB file and ODIN'ed to a new version of android that there was an active thread where it was CLEAR there was no root method"
"Accidentally"
Click to expand...
Click to collapse
LOL some people did it look in the Q&A section people are posting things about recovery not being seandroid enabled because of the bootloader for me I was actually in a boot loop so I just downloaded the latest version from Sammobile
OH and sorry for the last typo I thought you were correcting me

mikeyinid said:
You don't have to take my word for it. But I'm telling you, the bootloader is not locked.
Click to expand...
Click to collapse
I understand it isn't locked but what I mean is for the time being it feels like it is locked considering we can't root or install a custom recovery or downgrade.

ethanscooter said:
LOL some people did it look in the Q&A section people are posting things about recovery not being seandroid enabled because of the bootloader for me I was actually in a boot loop so I just downloaded the latest version from Sammobile
OH and sorry for the last typo I thought you were correcting me
Click to expand...
Click to collapse
Of course people did it, but don't make it seem like you clicked one button and the upgrade went through and now you're stuck. You ACTIVELY went through the upgrade process to force it through.
Plus, you don't need THREE threads on the same subject.

se1000 said:
Of course people did it, but don't make it seem like you clicked one button and the upgrade went through and now you're stuck. You ACTIVELY went through the upgrade process to force it through.
Plus, you don't need THREE threads on the same subject.
Click to expand...
Click to collapse
I didn't make the 3 threads others did I just responded to all 3. Also the whole point of that one choice in the poll is for people who were expecting a normal tmobile update and didn't get what they thought they would usually tmobile let's you downgrade and you can flash a recovery right away but this time it was different and not a ton of people knew it was going to be different maybe I should've worded it better I am sorry.

ethanscooter said:
I didn't make the 3 threads others did I just responded to all 3. Also the whole point of that one choice in the poll is for people who were expecting a normal tmobile update and didn't get what they thought they would usually tmobile let's you downgrade and you can flash a recovery right away but this time it was different and not a ton of people knew it was going to be different maybe I should've worded it better I am sorry.
Click to expand...
Click to collapse
You have 2 threads in the QA section that are on this same subject.
Look, if you want to have a rooted, custom recovery, custom kernel device, don't be the first to update. That's just how things go.

From the Moderator
Redundant Thread ......... So........
..............THREAD CLOSED...........

Nexus 6 bootloop when updating to android 5.1

Hey everyone I'm looking here as my last resort before sending my phone back to Motorola.
Bought a Nexus 6 from motorola uk which was delivered yesterday, switched phone on and all the Google apps on the phone updated, then had a notification OTA to download and install android 5.1 which I did, towards the end of the install process I had an error with the green android and a red exclamation mark.
I powered the device off with the power button and it turned back on and ever since it says "Android is starting" "Optimizing app 1 of 125" once it goes through all the apps it gets to the android boot screen then just goes back to the "Android is starting" "Optimizing app 1 of 125" over and over and over. (Infinite bootloop)
Pointers: The phone is not unlocked or rooted as I'm a noob its just fresh out the box, also I never opened/unlocked the developer options.
I have tried various recovery mode fixes, wiping cache and wiping all data and then rebooting the device with no luck.
Is there anyway I can hook my N6 up to my computer and fix this with a tool kit etc? I'm willing to try but I'd need basic instructions and reassurance it wouldn't muck up my warranty if it didn't work as my only other option is to exchange for a new device.
I'm a noob so I need detailed basic step by step instructions.
Any help, advice etc would be hugely appreciated. Thanks

Just send it back, no point messing about with it if it brand new could down to a fault with the hardware itself.

ixon2001 said:
Just send it back, no point messing about with it if it brand new could down to a fault with the hardware itself.
Click to expand...
Click to collapse
Iv'e heard this is a common problem with the N6 whilst trying to update the OTA 5.1 I had no other apps on the phone it was fresh, I did nothing wrong, I know someone who has been through 4 devices with the same bloody issues! In the end he had to sideload 6.0 and I'm not confident in being able to do that.

Well best bet is to download wugfresh toolkit 2.10 i think is the latest version, follow the instructions carefully because first you need to unlock the bootloader then flash 6.0.1 which has just come out.
Using Wugfresh is the best way to go if your new to flashing & you can't really go wrong with it.

ixon2001 said:
Well best bet is to download wugfresh toolkit 2.10 i think is the latest version, follow the instructions carefully because first you need to unlock the bootloader then flash 6.0.1 which has just come out.
Using Wugfresh is the best way to go if your new to flashing & you can't really go wrong with it.
Click to expand...
Click to collapse
I`am sure most xperienced users (me included) will not agree with you The best way to unlock, flash and root is still adb/fastboot. Especialy for lesser xperienced users that are lost is something goes wrong while using the toolkit, wich happens frequently btw. Just check the help threads.

gee2012 said:
I`am sure most xperienced users (me included) will not agree with you The best way to unlock, flash and root is still adb/fastboot. Especialy for lesser xperienced users that are lost is something goes wrong while using the toolkit, wich happens frequently btw. Just check the help threads.
Click to expand...
Click to collapse
Lol it's not rocket science using adb, been doing that way for years but for somebody that never flashed, rooted ect I still think the toolkit best way to go at first because everything is done for you at a click of a button.
Yes things can go tits up when using toolkits, mainly because they don't follow simple instructions.

ixon2001 said:
Lol it's not rocket science using adb, been doing that way for years but for somebody that never flashed, rooted ect I still think the toolkit best way to go at first because everything is done for you at a click of a button.
Yes things can go tits up when using toolkits, mainly because they don't follow simple instructions.
Click to expand...
Click to collapse
Lets agree to disagree

OK

ixon2001 said:
Yes things can go tits up when using toolkits, mainly because they don't follow simple instructions.
Click to expand...
Click to collapse
No, but because toolkits are always behind at least one version with marshmallow. People kept bricking their devices with toolkits when marshmallow came out and they thought they could root it. As 6.0.1 came out they'll do something else wrong.
Toolkits are not help. It's the lazy way if everything is already working and up to date.
Also what can a toolkit do if this phone doesn't even have developer options turned on? If it's in boot loop, as the OP said, then the Enable OEM unlocking was never set, then the only solution is to send it back. Unless there's a toolkit magic we don't know about.
Sent from my Nexus 6 running cyosp using Tapatalk

istperson said:
N
Also what can a toolkit do if this phone doesn't even have developer options turned on? If it's in boot loop, as the OP said, then the Enable OEM unlocking was never set, then the only solution is to send it back. Unless there's a toolkit magic we don't know about.
Click to expand...
Click to collapse
I think op created another thread http://forum.xda-developers.com/nexus-6/help/nexus-6-stuck-bootloop-trying-to-update-t3266100 for this issue - and was somehow able to unlock the bootloader (not sure how that worked if OEM unlock was never set)

jj14 said:
(not sure how that worked if OEM unlock was never set)
Click to expand...
Click to collapse
It was said that some of the first Nexus 6s with the original 5.0 came out with a bootloader that didn't check for this switch.

[Q] FRP error when trying to install a custom recovery

I've been digging around all day for an answer, but I can only find what to do for an FRP error if you're locked out of your phone, nothing about installing custom recoveries and roms.
Downloaded all the latest, and some older in case, recoveries, auto roots, and unlockers + roms even though I never got that far, lol. Tried Odin 3.11 and 3.10, nothing older yet because I'm just annoyed now.
So, I reboot into bootloader with adb or pressing buttons, Odin detects the phone fine, thow the recovery into the AP section, hit start, it starts the flash, I see a touch of a progress bar, and I get the "Custom binary blocked by frp...." error at the bottom of the info lines at the top. Phone locks up, I'll reboot with vol-/pwr or just pull the battery, and it reboots fine.
So, what do I have to do to get around this FRP so I can install a new recovery/rom? I'm really sick of 6.0.1 just not working right or doing anything it promised =/

Mage42384 said:
I've been digging around all day for an answer, but I can only find what to do for an FRP error if you're locked out of your phone, nothing about installing custom recoveries and roms.
Downloaded all the latest, and some older in case, recoveries, auto roots, and unlockers + roms even though I never got that far, lol. Tried Odin 3.11 and 3.10, nothing older yet because I'm just annoyed now.
So, I reboot into bootloader with adb or pressing buttons, Odin detects the phone fine, thow the recovery into the AP section, hit start, it starts the flash, I see a touch of a progress bar, and I get the "Custom binary blocked by frp...." error at the bottom of the info lines at the top. Phone locks up, I'll reboot with vol-/pwr or just pull the battery, and it reboots fine.
So, what do I have to do to get around this FRP so I can install a new recovery/rom? I'm really sick of 6.0.1 just not working right or doing anything it promised =/
Click to expand...
Click to collapse
Have you turned off Factory Reset Protection (reactivation lock)? :silly:

nine5raptor said:
Have you turned off Factory Reset Protection (reactivation lock)? :silly:
Click to expand...
Click to collapse
Well that does seem like it would fix the problem doesn't it? Of course, can't find how to do that

Mage42384 said:
Well that does seem like it would fix the problem doesn't it? Of course, can't find how to do that
Click to expand...
Click to collapse
Settings - security - reactivation lock. Untick the box

nine5raptor said:
Settings - security - reactivation lock. Untick the box
Click to expand...
Click to collapse
Not there

Mage42384 said:
Not there
Click to expand...
Click to collapse
I'm trying to upload a screenshot....stupid app failing. What OS version?
Edit: nevermind, I see 6.0.1 which is what I'm on

nine5raptor said:
I'm trying to upload a screenshot....stupid app failing. What OS version?
Edit: nevermind, I see 6.0.1 which is what I'm on
Click to expand...
Click to collapse
Was hoping it was that when I first saw it earlier, but not showing in security, developers, or searches

Should be attached now.

My current security screen

Mage42384 said:
My current security screen
Click to expand...
Click to collapse
Do you have OEM unlock at the bottom of developer options?

And my builds and versions since that's probably a question coming up soon

nine5raptor said:
Do you have OEM unlock at the bottom of developer options?
Click to expand...
Click to collapse
That I do have have (^_^)

Mage42384 said:
That I do have have (^_^)
Click to expand...
Click to collapse
So they dropped their reactivation lock on the T3 variant...interesting. OEM unlock should allow you to proceed.
Samsung and all their silly variants....just to confuse us.
Reactivation Lock is Samsung's proprietary variant of the OEM unlock Google already provides.

nine5raptor said:
So they dropped their reactivation lock on the T3 variant...interesting. OEM unlock should allow you to proceed.
Samsung and all their silly variants....just to confuse us.
Reactivation Lock is Samsung's proprietary variant of the OEM unlock Google already provides.
Click to expand...
Click to collapse
Not sure if it's all T3s, seen a bunch of posts today about the T3 using the Samsung security version, but this is a very late model, lol. Think I bought this a little over 6 months ago

I'll see if I have time tomorrow to try it out, but def let you know by Thursday. Thanks for the help =)

Mage42384 said:
I'll see if I have time tomorrow to try it out, but def let you know by Thursday. Thanks for the help =)
Click to expand...
Click to collapse
Hope it works out for you. Sorry for all the confusion searching menus.

nine5raptor said:
Hope it works out for you. Sorry for all the confusion searching menus.
Click to expand...
Click to collapse
No worries, it got done lol. Spent 6 hours at work today finding all the wrong answers xD

nine5raptor said:
Hope it works out for you. Sorry for all the confusion searching menus.
Click to expand...
Click to collapse
Ok, installation works...but when I try to go to recovery, I just get the dead droid pic saying no command now =( Back to digging through forums, unless you have any advice for that, lol

Mage42384 said:
Ok, installation works...but when I try to go to recovery, I just get the dead droid pic saying no command now =( Back to digging through forums, unless you have any advice for that, lol
Click to expand...
Click to collapse
After flashing twrp, don't let it boot system. As soon as it reboots, pull the battery. Then boot into twrp. For some reason, MM changed the process and now you cannot boot into system before booting twrp for the first time.

nine5raptor said:
After flashing twrp, don't let it boot system. As soon as it reboots, pull the battery. Then boot into twrp. For some reason, MM changed the process and now you cannot boot into system before booting twrp for the first time.
Click to expand...
Click to collapse
Ah, it does that first boot restore recovery thing that my HTC's used to do...but with those, you'd get one shot into recovery at any time if I remember right (could be 3 weeks later, but only once, lol)