Database Develop

root for vzw moto x 4.4.2?

While we wait for real root for 4.4.2...in the meantime, I wouldn't mind having root with write protection upon reboot. Could someone walk me through the process for that? I'm more than happy to reapply any changes when the phone is rebooted (which won't be too often, hopefully)

If you're already on 4.4.2....you can't root. Can't downgrade to do the safe strap method.
If you are on 4.2.2 or 4.4....then read the safe strap thread. Also there's a couple ROMs now that apparently root and disable write protection. But again, if you are already on 4.4.2....you can't do it.

I saw it mentioned in a thread that root could exist but with write protection. Is that not true?

terrorist96 said:
I saw it mentioned in a thread that root could exist but with write protection. Is that not true?
Click to expand...
Click to collapse
You can't root on 4.4.2 period. There's no way. Simple as that.
Sent from my XT1060 using Tapatalk

DroidOnRoids said:
You can't root on 4.4.2 period. There's no way. Simple as that.
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
Guess I'll just wait

terrorist96 said:
Guess I'll just wait
Click to expand...
Click to collapse
That's the only thing to do. It sucks because I'm stuck too.
Sent from my XT1060 using Tapatalk

terrorist96 said:
I saw it mentioned in a thread that root could exist but with write protection. Is that not true?
Click to expand...
Click to collapse
The only way was to have it on 4.4 before taking ota. I guess root survived with write protection enabled tho.
But already being on 4.4.2.....can't root now.

This is kinda weird. I was talking to Motorola via the help app and the representative was adamant in telling me that I am able to unlock my bootloader on the Verizon version. I even said that xda developers say it cannot be unlocked but he told me it was possible and to try it. He linked me here:
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-b
Has anyone tried this?

terrorist96 said:
This is kinda weird. I was talking to Motorola via the help app and the representative was adamant in telling me that I am able to unlock my bootloader on the Verizon version. I even said that xda developers say it cannot be unlocked but he told me it was possible and to try it. He linked me here:
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-b
Has anyone tried this?
Click to expand...
Click to collapse
I think the rep told you wrong. According to this link (found on the page that you linked under the "Find Your Device" section) https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/87215, it only works with the Verizon Dev Edition. You can give it a go, but it will probably reject the attempt. If Verizon has changed their policy (highly doubtful) a lot of people would be extremely happy. Anyway, give it a shot. The worst that can happen is that it tells you that your device doesn't qualify.

Yeah, I even sent him that page saying that only the sprint, t-mobile and US Cellular versions can be unlocked. But I'll try this tomorrow. Anyone else can feel free to do so as well in the meantime.

kj2112 said:
The only way was to have it on 4.4 before taking ota. I guess root survived with write protection enabled tho.
But already being on 4.4.2.....can't root now.
Click to expand...
Click to collapse
Correct.
If you were on 4.4, you could root and disable write protection. When you took the 4.4.2 OTA, write protection became re-enabled, but you kept root. Of course this meant any changes/installs/etc made to /system and the like since taking 4.4.2 would be lost at power off/on.
Once 4.4.2 is on your phone, you can't root, and you can't disable write protection, unless you have a developer edition, or a carrier edition like Sprint, T-Mobile, etc that Moto gives out the bootloader unlock codes on their web site for. Once you unlock the bootloader you can root and write protection is disabled, and this can be done no matter what rom is on the phone.
The bounty to unlock the bootloader for VZW/ATT (who can't get codes from moto's web site), has continued to grow. No one has found a way. Same with some older Moto's too. Same with the updated GS4 and GS5, and so on.... So the chances of seeing a bootloader unlock hack are fading. Root exploits seem to get patched with each new ROM update (to root 4.4, you had to downgrade and root 4.2.2), so that is getting harder.
To be realistic, the only way to ensure you can have root and write protection disabled is to buy a Developer Edition, or from a carrier that allows you to unlock the bootloader. Yup it can cost more, and you can't customize its look, but its a small trade off if you *NEED* working root no matter what rom comes on your phone. Its a trade off I had to make, but it was easier when I did it as I was paying full price (to keep my unlimited data), and the Dev Edition was the only 32gig option for Verizon at the time.
---------- Post added at 09:46 PM ---------- Previous post was at 09:44 PM ----------
terrorist96 said:
This is kinda weird. I was talking to Motorola via the help app and the representative was adamant in telling me that I am able to unlock my bootloader on the Verizon version. I even said that xda developers say it cannot be unlocked but he told me it was possible and to try it. He linked me here:
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-b
Has anyone tried this?
Click to expand...
Click to collapse
As @HeroOfTime has said, unless Moto has reversed their course of action, Verizon and ATT non-developer phones can not receive an unlock code via Moto's web site.
That is why there was such a big "to do" about the Chinese site that was selling codes not too long ago. (which has been shut down).
Once you try it. Please let us know. There are MANY who would be very happy if Moto has changed things!!

Well, I tried and got the expected error telling me that my device wasn't eligible. Guess that Motorola rep didn't know what she was talking about. I talked to someone else and they basically confirmed it, saying you can only do it on the Dev Edition on Verizon. :\

I'll just leave this right here.... PLEASE be smart and do not start spamming him with "ETA?" and other b.s. that will make him not want to share it. We are NOT entitled to his work. If he decides to share, he will. Leave it at that.

jimmiet said:
I'll just leave this right here.... PLEASE be smart and do not start spamming him with "ETA?" and other b.s. that will make him not want to share it. We are NOT entitled to his work. If he decides to share, he will. Leave it at that.
Click to expand...
Click to collapse
He's already said that he's not going to release it. Jcase is a lost cause.

Jump on this while you can !! -> http://forum.xda-developers.com/moto-x/general/china-middleman-t2751177

terrorist96 said:
He's already said that he's not going to release it. Jcase is a lost cause.
Click to expand...
Click to collapse
He said on Twitter that it would more than likely be released just not by him.
Sent from my XT1060 using XDA Premium HD app

Well let's hope so.

And then 4.4.3 will come out. Lol

kj2112 said:
And then 4.4.3 will come out. Lol
Click to expand...
Click to collapse
His tweet did say "Don't OTA"

I've been searching for an answer to my problem and this is the best thread I have seen but....I'm a little confused. Here is what I did:
Bought a BOOST Mobile MOTO-G.
I unlocked the bootloader. I can be done on this device.
I flashed CWM from recovery. It worked fine.
From recovery, I flashed the VERIZON 4.4.2 image.
Booted the phone, activated it on PagePlus.
Went back to recovery, flashed SUPERSU. It worked....no errors.
Root checkers say I have root. I cannot use anything that needs root such as Titanium.
I connected the phone and did :
adb shell
getprop ro.boot.write_protect
It returned a 0 (zero)
Does this make sense? I just would like someone to confirm it does. Reading this thread has helped but it is the ZERO write protect thing that is throwing me.
Thanks in advance.

PrototypeProtection.apk ?

I noticed that my Z3C has an app/module installed that is called "PrototypeProtection". I first noticed it when I looked at the details of "Android System" in the battery usage screen. What is this? Does it mean that my unit is actually a prototype? It's not present on my Z2 tablet.

It's on my Z3C as well. The permissions on it are crazy.

It's an application used for blocking access to certain applications and network addresses on prototype devices. It uses the DELETE_PACKAGES and PACKET_FILTER permissions to perform these tasks.
It only considers a device to be a prototype if the app finds a file named /mnt/sdcard/SOMCPrototypeProtectionKey on boot (I didn't find that file on my device, my guess would be that Sony's places this file on devices destined for trade shows, etc.)
To prevent it from running issue 'pm block com.sonymobile.prototypeprotection' from an adb shell.
I've attached the blacklist application and website address files pulled from the apk if you're interested. Looks like they are mainly benchmarking apps or news sites that typically post new device leaks.

cschmitt said:
It's an application used for blocking access to certain applications and network addresses on prototype devices. It uses the DELETE_PACKAGES and PACKET_FILTER permissions to perform these tasks.
It only considers a device to be a prototype if the app finds a file named /mnt/sdcard/SOMCPrototypeProtectionKey on boot (I didn't find that file on my device.)
To prevent it from running issue 'pm block com.sonymobile.prototypeprotection' from an adb shell.
I've attached the blacklist application and website address files pulled from the apk if you're interested. Looks like they are mainly benchmarking apps or news sites that typically post new device leaks.
Click to expand...
Click to collapse
Thanks, this answers the question perfectly.

thank god for this thread. Ive been trying to get rid of the prototype status on my Z3 for ages now.
---------- Post added at 02:28 AM ---------- Previous post was at 01:49 AM ----------
Anyway, now to ask how do I remove the thing that doesn't allow me to update my Sony apps?
Sent from my D6653 using XDA Free mobile app

lzwtheprodigy said:
thank god for this thread. Ive been trying to get rid of the prototype status on my Z3 for ages now.
---------- Post added at 02:28 AM ---------- Previous post was at 01:49 AM ----------
Anyway, now to ask how do I remove the thing that doesn't allow me to update my Sony apps?
Sent from my D6653 using XDA Free mobile app
Click to expand...
Click to collapse
AFAIK there's not by default any 'thing' that prevents updating Sony apps...
Did you unlock your bootloader?

Nope,did not do that
Sent from my D6653 using XDA Free mobile app

hi! this is great information, thank you. i didn't quite understand the adb part. are you saying that by running that command i can prevent the prototypeprotection from recognising my phone as a prototype? it came with an unlocked bootloader and all methods for relocking it don't even give me the option to try (i.e. flashtool and a bootloader unlock/relock utility i found), and i wonder if it is this that is stopping it. on the z3 relocking the bootloader is part of the process of restoring DRM functions (not DRM keys) which i never had, and i'd really like to get it working. since my bootloader may never have been locked in the first place it may be that which is stopping it, but i'd like to give it a try. if i have misunderstood you, can you think of i way in which i can disable or remove prototype protection/status?
cschmitt said:
It's an application used for blocking access to certain applications and network addresses on prototype devices. It uses the DELETE_PACKAGES and PACKET_FILTER permissions to perform these tasks.
It only considers a device to be a prototype if the app finds a file named /mnt/sdcard/SOMCPrototypeProtectionKey on boot (I didn't find that file on my device, my guess would be that Sony's places this file on devices destined for trade shows, etc.)
To prevent it from running issue 'pm block com.sonymobile.prototypeprotection' from an adb shell.
I've attached the blacklist application and website address files pulled from the apk if you're interested. Looks like they are mainly benchmarking apps or news sites that typically post new device leaks.
Click to expand...
Click to collapse

were you able to update it to 5.0
lzwtheprodigy said:
thank god for this thread. Ive been trying to get rid of the prototype status on my Z3 for ages now.
---------- Post added at 02:28 AM ---------- Previous post was at 01:49 AM ----------
Anyway, now to ask how do I remove the thing that doesn't allow me to update my Sony apps?
Sent from my D6653 using XDA Free mobile app
Click to expand...
Click to collapse
so I bought the variant D6616 but it turns out the device has prototype status. I went ahead and disabled the prototype protect app but I am still unable to upgrade it to 5.0 I tried clearing the cache and there was nothing helpful in the recovery menu other than a factory reset.
I'm wondering if I am able to flash a "normal" status z3 rom on it? is that such a thing? I'm pretty new to all of this but I'll continue trying to figure it out.
( I wasn't sure if it was worth starting a new discussion since this thread seems to be about fixing prototype limitation anyways)
one other thing, I didn't find the file under mnt/sdcard etc but my phone was still being blocked from accessing those listed sites.

prototype20 said:
so I bought the variant D6616 but it turns out the device has prototype status. I went ahead and disabled the prototype protect app but I am still unable to upgrade it to 5.0 I tried clearing the cache and there was nothing helpful in the recovery menu other than a factory reset.
I'm wondering if I am able to flash a "normal" status z3 rom on it? is that such a thing? I'm pretty new to all of this but I'll continue trying to figure it out.
( I wasn't sure if it was worth starting a new discussion since this thread seems to be about fixing prototype limitation anyways)
one other thing, I didn't find the file under mnt/sdcard etc but my phone was still being blocked from accessing those listed sites.
Click to expand...
Click to collapse
Did you unlock your bootloader? Because then you can't install official updates from Sony.
Or have you just not received a notification for 5.0 yet?

degraaff said:
Did you unlock your bootloader? Because then you can't install official updates from Sony.
Or have you just not received a notification for 5.0 yet?
Click to expand...
Click to collapse
I think the bootloader is locked
in the service menu it says "bootloader unlocked allowed: Yes"
Also the update should be coming from tmobile right? In my original post, I meant to say I have the tmobile variant.
I'm not sure if this has anything to do with it, but I can't update the sony apps either. In the update center they don't show up and when I try to download them from the play store I get an a error saying "Package file was not signed correctly. Uninstal the previous copy of the app and try again"ther
Or maybe it's just a really selective role out and hasn't gotten to me yet? The odd thing is that I can't force it to update from PC or thru the phone

reviving this thread to thank @cschmitt because he gave detailed information about this apk.
For information , on Z5C marshmallow (maybe also on Z3C) the apk is now called pip.apk but it contains exactly the same lists

just like to add for those with an xperia z2 on lollipop, use the command hide instead of block
and thanks for the info!

I have the same problem
How did you get rid of prototype status on your Z3 because I really do not know how to get rid of it and can use some help if you are willing

Install TWRP on locked bootloader with Android 5.1

Hello,
Kindly how can I install TWRP recovery on my Nexus 6 with Android 5.1 and locked bootloader and I don't have a working android (shows android figure and it maybe bricked)?
Is it possible to install a recovery to install any other custom ROM so I can make the device working?

Pr0fess0rX said:
Hello,
Kindly how can I install TWRP recovery on my Nexus 6 with Android 5.1 and locked bootloader and I don't have a working android (shows android figure and it maybe bricked)?
Is it possible to install a recovery to install any other custom ROM so I can make the device working?
Click to expand...
Click to collapse
Please provide some more information.
Can you boot into Android at all? (Does the phone work)
Can you get to the developer options menu?
---------- Post added at 06:40 AM ---------- Previous post was at 06:27 AM ----------
Also, please list any steps you took, prior to the phone being in this present condition.

Evolution_Freak said:
Please provide some more information.
Can you boot into Android at all? (Does the phone work)
Can you get to the developer options menu?
Click to expand...
Click to collapse
I can't boot into phone and after I relocked the bootloader after the factory image installed (as I do usually since years to receive the OTAs for Nexus devices).
Unfortunaily Google changed the game here without notifying US about this big move and it should mention to not relock the bootloader after installing 5.1!
I know I can unlock the bootloader from the developers tools but I can't open (boot into) android.

Pr0fess0rX said:
I can't boot into phone and after I relocked the bootloader after the factory image installed (as I do usually since years to receive the OTAs for Nexus devices).
Unfortunaily Google changed the game here without notifying US about this big move and it should mention to not relock the bootloader after installing 5.1!
I know I can unlock the bootloader from the developers tools but I can't open (boot into) android.
Click to expand...
Click to collapse
The bootloader can be re-locked but there's a process that must be followed. Click the top link in my signature for more information.
So, you flashed a factory image and then locked the bootloader before booting into Android and ticking the button in developer options to allow OEM unlock, correct?
If this is the case, you are bricked. There is no fix for this. You can RMA or return it to where you purchased it from. Sorry.

Evolution_Freak said:
If this is the case, you are bricked. There is no fix for this. You can RMA or return it to where you purchased it from. Sorry.
Click to expand...
Click to collapse
Thank you but what do you mean by RMA?

Pr0fess0rX said:
Thank you but what do you mean by RMA?
Click to expand...
Click to collapse
RMA = Return Material Authorization. i.e. warranty return from your retailer.

Pr0fess0rX said:
Hello,
Kindly how can I install TWRP recovery on my Nexus 6 with Android 5.1 and locked bootloader and I don't have a working android (shows android figure and it maybe bricked)?
Is it possible to install a recovery to install any other custom ROM so I can make the device working?
Click to expand...
Click to collapse
Pr0fess0rX said:
I can't boot into phone and after I relocked the bootloader after the factory image installed (as I do usually since years to receive the OTAs for Nexus devices).
Unfortunaily Google changed the game here without notifying US about this big move and it should mention to not relock the bootloader after installing 5.1!
I know I can unlock the bootloader from the developers tools but I can't open (boot into) android.
Click to expand...
Click to collapse
cam30era said:
RMA = Return Material Authorization. i.e. warranty return from your retailer.
Click to expand...
Click to collapse
Sadly if u would have done a simple search you would have known this is something that has been talked about for a few months now. RMA is the only option.

While folks who visit these forums regularly may have know about this, Google really should update the factory images site for those who are not regular to these forums

jj14 said:
While folks who visit these forums regularly may have know about this, Google really should update the factory images site for those who are not regular to these forums
Click to expand...
Click to collapse
Even if ur not a regular number one rule here is use the search, and u will find it. Simple search as issues with nexus 6 updating or updating nexus 6.

I do agree that the factory images page should have some mention of the new procedure needed for locking. While it doesn't apply to all devices, it obviously applies here. Too many devices have been lost because of this.

kpierce2014 said:
Even if ur not a regular number one rule here is use the search, and u will find it. Simple search as issues with nexus 6 updating or updating nexus 6.
Click to expand...
Click to collapse
Not disputing that.
But realize that there are folks out there who may expect the Nexus devices to work the way they always have, and may not bother to ever visit xda (maybe they are ok with their devices completely stock). If a user doesn't visit xda, they aren't going to search xda (unless they don't know how to do what they want to do, or they suspect things have changed)

Why do I have to search about a standard procedure I am doing since years and there is no warning from Google that this time this procedure might brick the phone!!!

Pr0fess0rX said:
Why do I have to search about a standard procedure I am doing since years and there is no warning of Google that this time this procedure might brick the phone!!!
Click to expand...
Click to collapse
This is what we've been discussing in the posts above. The process has changed significantly with the new security features of 5.1 and Google needs to update their page to reflect this.
That being said, you still should read before jumping into anything because things change. Plain and simple, things and procedures change. We're talking about a whole new OS with lollipop. It is not entirely your fault but in a sense, you, with a bit of searching and reading, could have avoided this situation.
Sadly, this is a very common problem, which led to me working with others and creating the guide to safely re-lock. A 2 minute search of XDA would have given multiple results for you to read.
---------- Post added at 09:47 AM ---------- Previous post was at 09:35 AM ----------
I also feel that this hasn't been publicized enough. This thread is a perfect example. I understand that people have done things the same way for years but without an in your face warning of some sort, why would people think they were doing it wrong? Yes, my thread is mentioned in the sticky roll up thread, and for some that is enough. But as mentioned earlier, what about those that don't read the sticky roll up or use XDA at all?
The blame should fall on Google for not promoting a new procedure. They have to be aware of it, right? Why, also, have none of the Android forums or online magazines made mention of the new procedures? Obviously people use factory images and many have bricked. ???

Evolution_Freak said:
The blame should fall on Google for not promoting a new procedure. They have to be aware of it, right?
Click to expand...
Click to collapse
I agree - at the very minimum, update the instructions on the factory images site. Currently, here's what it states
6. Execute the flash-all script. This script installs the necessary bootloader, baseband firmware(s), and operating system.
Once the script finishes, your device reboots. You should now lock the bootloader for security:
1. Start the device in fastboot mode again, as described above.
2. Execute:
fastboot oem lock
Click to expand...
Click to collapse

Looking to buy a N6 that's Google Account Locked

I would like to purchase a Nexus 6 (US Version) and I've seen a few for sale that claim to be google email account locked.
The reason usually given the "owner" forgot their password and can't reset it.
I was thinking a factory image restore would clear everything and un lock the phone.
Not sure if this would work, if someone could confirm either way, I would appreciate it.
Is there a way to bypass the google account lock?
Thank you!

There is no bypass method known..do not buy it.

danarama said:
There is no bypass method known..do not buy it.
Click to expand...
Click to collapse
Is there anywhere that I can learn how this account lock works?
I am legitimately trying to get a nexus 6 cheap then use it as my personal phone, not intending on hacking into someones, I could care less if all data on the phone is lost.
I was thinking if I wiped the system and data partitions it would undo the software lock. Or is this Google Account Lock more than just software rooted?

xNotta said:
Is there anywhere that I can learn how this account lock works?
I am legitimately trying to get a nexus 6 cheap then use it as my personal phone, not intending on hacking into someones, I could care less if all data on the phone is lost.
I was thinking if I wiped the system and data partitions it would undo the software lock. Or is this Google Account Lock more than just software rooted?
Click to expand...
Click to collapse
The information has not been released into the public domain. We don't know how it works. It's most likely stored on one of the many partitions that we don't have access to, but we don't know that. All we know is that we haven't found a fix. Flashing system images doesn't help.

danarama said:
The information has not been released into the public domain. We don't know how it works. It's most likely stored on one of the many partitions that we don't have access to, but we don't know that. All we know is that we haven't found a fix. Flashing system images doesn't help.
Click to expand...
Click to collapse
That's exactly the info I was looking for. Thank you for saving me a few $!
Guess I'll put that twords a Nexus 5.
https://www.youtube.com/watch?v=5ySekEg-I8g That guy claims to be able to do it.... for a fee.
Why'd Google have to go all iCloud lock on us?

xNotta said:
https://www.youtube.com/watch?v=5ySekEg-I8g That guy claims to be able to do it.... for a fee.
Click to expand...
Click to collapse
It's your risk. One random guy here reckons he managed to get it bypassed at a mobile phone repair shop, but he couldn't give us any information towards how that was achieved. We take it with a pinch of salt.

It's Just anti theft which imo is a great feature to have
Sent from my Nexus 6 using Tapatalk

It's meant as a security feature to deter phone theft, whoever said they were able to work around it was lying, the only way to get past that screen is to input the correct password of the google account, factory reset and flashing google images do not get rid of the lock. If the person that had it before removed his/her account before wiping the device than that screen would not show. Now if the person truly forgot their google account pass, they could easily reset their password if they are really the original owners of the phone provided they have another email/number for google to send the verification info, my opinion is the seller either found or stole the phone and is looking to make a buck on someone unsuspecting, because they cant use it themselves.

bigjack216 said:
It's Just anti theft which imo is a great feature to have
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
It is, but what it should do when you're factory resetting, is remind you to remove your google account first if you are selling it.
---------- Post added at 07:20 PM ---------- Previous post was at 07:16 PM ----------
djkinetic said:
It's meant as a security feature to deter phone theft, whoever said they were able to work around it was lying, the only way to get past that screen is to input the correct password of the google account, factory reset and flashing google images do not get rid of the lock. If the person that had it before removed his/her account before wiping the device than that screen would not show. Now if the person truly forgot their google account pass, they could easily reset their password if they are really the original owners of the phone provided they have another email/number for google to send the verification info, my opinion is the seller either found or stole the phone and is looking to make a buck on someone unsuspecting, because they cant use it themselves.
Click to expand...
Click to collapse
No way to tell the back story of the phone. This anti-theft measure came in without warning, so people who updated and then wiped it without knowing they needed to remove the account first, could easily have sold it and it not been tested by the buyer for this as they didn't know. There could easily be a legitimate story behind it.
That said, no one should buy these devices anyway, for their own sake and the fact that they *may* be stolen.
Also, as unlikely as we believe it to be that someone managed to get it bypassed at a mobile phone repair store, doesn't mean it isn't true. Just because we don't know a way around it, doesn't mean someone else can't - though that is besides the point

xNotta said:
That's exactly the info I was looking for. Thank you for saving me a few $!
Guess I'll put that twords a Nexus 5.
https://www.youtube.com/watch?v=5ySekEg-I8g That guy claims to be able to do it.... for a fee.
Why'd Google have to go all iCloud lock on us?
Click to expand...
Click to collapse
it was a bug in 5.1, where you would enter radom digits.. buts its been long fixed, and only worked if the person set a password.

you should be able to bypass this by flashing back to stock and using the no-encrypt kernel from Wugfresh's toolkit.
The google account lock is just because encryption is active and someone did a factory reset on it while it was encrypted.
Source:
I did this to my own once when flashing ROMs and could not get pass the password screen, flashing the no-encrypt fixed it

I haven't heard of this....I have a N6 on the way which means I'll be wiping and selling my LG G2 (running 5.1.1 Paranoid). Is this a new thing with lollipop that I need to remove my account first, or is it device based?
If so, Settings > Accounts > Google > Delete your account or services? Is that all I need to do before wiping?

plasticarmyman said:
you should be able to bypass this by flashing back to stock and using the no-encrypt kernel from Wugfresh's toolkit.
The google account lock is just because encryption is active and someone did a factory reset on it while it was encrypted.
Source:
I did this to my own once when flashing ROMs and could not get pass the password screen, flashing the no-encrypt fixed it
Click to expand...
Click to collapse
if your bootloader is locked, and you have stock recovery, you cant flash a stock factory image. and you cant flash a custom kernel with the stock recovery. so, you couldnt of done this in your wettest fantasy. but, if you have twrp, you could. but then again, if you have twrp recovery, you can fix the issue regardless.

simms22 said:
if your bootloader is locked, and you have stock recovery, you cant flash a stock factory image. and you cant flash a custom kernel with the stock recovery. so, you couldnt of done this in your wettest fantasy. but, if you have twrp, you could. but then again, if you have twrp recovery, you can fix the issue regardless.
Click to expand...
Click to collapse
if you can get into fastboot you can fix most of those things.
TWRP would be for the kernel, but you can unlock the BL and flash a recovery all from fastboot which is not secured by the account lock

plasticarmyman said:
if you can get into fastboot you can fix most of those things.
TWRP would be for the kernel, but you can unlock the BL and flash a recovery all from fastboot which is not secured by the account lock
Click to expand...
Click to collapse
You can't unlock the bootloader unless you set "enable OEM unlock" in Settings, which you can't get to if it is google account locked.

danarama said:
You can't unlock the bootloader unless you set "enable OEM unlock" in Settings, which you can't get to if it is google account locked.
Click to expand...
Click to collapse
oh snap! i totally forgot about that part....
okay nevermind my blathering idiocy

plasticarmyman said:
oh snap! i totally forgot about that part....
okay nevermind my blathering idiocy
Click to expand...
Click to collapse
No worries

danarama said:
No worries
Click to expand...
Click to collapse
it's been about a year since i've had to check that box

plasticarmyman said:
oh snap! i totally forgot about that part....
okay nevermind my blathering idiocy
Click to expand...
Click to collapse
yup. but if you have twrp, fastboot formatting userdata and cache should fix it. if you havd stock recovery, then youre screwed.

More than positive this Nexus is stolen.
Stay away from it. If it's locked, it's probably been reported and it's IMEI blacklisted. So even IF you could get it unlocked somehow. You will still be boned.
As for cheap Nexus 6? They are on sale for $350 on Amazon.

Bought used. Security concerns?

I had been looking for a new phone for awhile. Settled on a Note 9 because I wanted to try using the S Pen for work and dislike the Note 10 design. However, they are still sold at full price where I live, so I bought one secondhand. Everything seems generally fine with it, minus some freezing or weird reactions when it charges for awhile or restarts. But I have been skeptical of throwing passwords (personal and for work) on it to this point. Thats because I read an article about potential root level or firmware level spyware that remains after a reset.
I did a reset AND even took it to an official service center to flash new firmware (but they said they cannot do it there, but they did some kind of more advanced reset?). I checked my Knox counter in the Download menu and it reads 0x00000, maybe more or less zeros. Samsung pass, pay, health, and secure folder all seem to work (I can register for them, use the bio sensor). That all sounds like it has not been tampered with in any way, correct?
Thanks for the help.

IqD said:
I had been looking for a new phone for awhile. Settled on a Note 9 because I wanted to try using the S Pen for work and dislike the Note 10 design. However, they are still sold at full price where I live, so I bought one secondhand. Everything seems generally fine with it, minus some freezing or weird reactions when it charges for awhile or restarts. But I have been skeptical of throwing passwords (personal and for work) on it to this point. Thats because I read an article about potential root level or firmware level spyware that remains after a reset.
I did a reset AND even took it to an official service center to flash new firmware (but they said they cannot do it there, but they did some kind of more advanced reset?). I checked my Knox counter in the Download menu and it reads 0x00000, maybe more or less zeros. Samsung pass, pay, health, and secure folder all seem to work (I can register for them, use the bio sensor). That all sounds like it has not been tampered with in any way, correct?
Thanks for the help.
Click to expand...
Click to collapse
What's the model number?

Sm-n960n. Korean exynos model, 512gb.

IqD said:
Sm-n960n. Korean exynos model, 512gb.
Click to expand...
Click to collapse
If you are worried about remaining spyware of files, download the latest rom from sammobile and then flash with odin.
Just simply search how to use sammobile or how to use odin if you need help. Hundreds of years have posted how good and answered those questions already

I used to flip phones up until a couple years ago. I've bought and sold hundreds, maybe thousands of used phones, most of which had my accounts on them at one point and time. I think as long as the phone is running official firmware, isn't bootloader unlocked/rooted, and you've reset it, it should be fine. Of course you run the risk that someone has hacked it, installed spyware at the system level, and somehow overwritten the status to show as official such that the spyware persists even after a reset, but that's highly unlikely.
Sent from my SM-N960U using Tapatalk

Bober_is_a_troll said:
If you are worried about remaining spyware of files, download the latest rom from sammobile and then flash with odin.
Just simply search how to use sammobile or how to use odin if you need help. Hundreds of years have posted how good and answered those questions already
Click to expand...
Click to collapse
Thanks for the idea. I considered this but would like to avoid just because sammobile is unofficial, so it would still leave me slightly apprehensive even if everyone is using it.
Everything I read seems to suggest that the phone was never rooted if all of the Samsung apps work and the Download KNOX counter is 0x0. Just wanting to confirm by someone more knowledgeable about this.
joshw0000 said:
I used to flip phones up until a couple years ago. I've bought and sold hundreds, maybe thousands of used phones, most of which had my accounts on them at one point and time. I think as long as the phone is running official firmware, isn't bootloader unlocked/rooted, and you've reset it, it should be fine. Of course you run the risk that someone has hacked it, installed spyware at the system level, and somehow overwritten the status to show as official such that the spyware persists even after a reset, but that's highly unlikely.
Sent from my SM-N960U using Tapatalk
Click to expand...
Click to collapse
Thanks. I don't think it has ever been unlocked or rooted, but is there a guaranteed way to know?

IqD said:
Thanks for the idea. I considered this but would like to avoid just because sammobile is unofficial, so it would still leave me slightly apprehensive even if everyone is using it.
Everything I read seems to suggest that the phone was never rooted if all of the Samsung apps work and the Download KNOX counter is 0x0. Just wanting to confirm by someone more knowledgeable about this.
Thanks. I don't think it has ever been unlocked or rooted, but is there a guaranteed way to know?
Click to expand...
Click to collapse
Go to settings > about phone > status and it should say "official". That would tell you if the phones operating system has been modified (rooted). As far as checking for bootloader unlock, I'm not sure on Samsung's but on a Google Pixel once the bootloader is unlocked it'll show an unlocked lock on the bootscreen every time that you reboot the phone. North American snapdragon variants of Note 9's do not have an unlockable bootloader so if your phone is a carrier branded phone, the bootloader can't be unlocked. You can Google your model # to figure out which one you have.
You can also check that all functions work properly. Typically apps like Samsung Pay won't work if the phone is rooted. There are ways around that where you can trick the phone into thinking it's not rooted to get those apps to work so, again, that's not a full proof way to check. For example, I'm using an AT&T variant that's been sim unlocked and flashed with Verizon firmware and it works 100% like a Verizon phone.
I'd say, reboot the phone. If you don't see an unlocked icon it's probably not unlocked. Go into settings and take note of your model #
Then go online and research about Odin and flashing official firmware via your computer. Download the latest official firmware for your phone, flash it using Odin, and then you'll know that there's no spyware on your phone. That would essentially be the equivalent of wiping a computer and reinstalling Windows.
Sent from my SM-N960U using Tapatalk

joshw0000 said:
Go to settings > about phone > status and it should say "official". That would tell you if the phones operating system has been modified (rooted). As far as checking for bootloader unlock, I'm not sure on Samsung's but on a Google Pixel once the bootloader is unlocked it'll show an unlocked lock on the bootscreen every time that you reboot the phone. North American snapdragon variants of Note 9's do not have an unlockable bootloader so if your phone is a carrier branded phone, the bootloader can't be unlocked. You can Google your model # to figure out which one you have.
You can also check that all functions work properly. Typically apps like Samsung Pay won't work if the phone is rooted. There are ways around that where you can trick the phone into thinking it's not rooted to get those apps to work so, again, that's not a full proof way to check. For example, I'm using an AT&T variant that's been sim unlocked and flashed with Verizon firmware and it works 100% like a Verizon phone.
I'd say, reboot the phone. If you don't see an unlocked icon it's probably not unlocked. Go into settings and take note of your model #
Then go online and research about Odin and flashing official firmware via your computer. Download the latest official firmware for your phone, flash it using Odin, and then you'll know that there's no spyware on your phone. That would essentially be the equivalent of wiping a computer and reinstalling Windows.
Click to expand...
Click to collapse
yeah.. i whouldint fall for that system/status official crap. as you can see in the screenshot i posted from my rooted n960n.
the only real way is to check if knox is tripped is in DL mode( turn phone off. hold bixby and vol down button while inserting a usb cable hooked to a computer.).
also flashing a stock firmware on an FRP locked phone wont do **** if someone has had their accounts logged in/registered on it and have not reset it correctly.
surprised you dont know this.

IqD said:
Sm-n960n. Korean exynos model, 512gb.
Click to expand...
Click to collapse
FYI - This phone does have an unlockable bootloader.
I'd recommend using Bobby's advice and flash the latest firmware with Odin. If the phone is not already on the latest update, you could flash one firmware less than current and then let the phone download and install an OTA to the current version. You'll know that its official if the phone successfully downloads and installs the OTA.
Sent from my SM-N960U using Tapatalk
---------- Post added at 07:35 PM ---------- Previous post was at 07:31 PM ----------
bober10113 said:
yeah.. i whouldint fall for that system/status official crap. as you can see in the screenshot i posted from my rooted n960n.
the only real way is to check if knox is tripped is in DL mode( turn phone off. hold bixby and vol down button while inserting a usb cable hooked to a computer.).
also flashing a stock firmware on an FRP locked phone wont do **** if someone has had their accounts logged in/registered on it and have not reset it correctly.
surprised you dont know this.
Click to expand...
Click to collapse
Not sure why you're trying to call me out when I clearly said there are ways for it show official if it's rooted. Also, no one said anything about FRP. If the phone was FRP locked they wouldn't be able to use it at all... Unless you know how to remove an FRP lock, which I do. At that point the phone would work/be a normal phone.
Sent from my SM-N960U using Tapatalk

joshw0000 said:
FYI - This phone does have an unlockable bootloader.
I'd recommend using Bobby's advice and flash the latest firmware with Odin. If the phone is not already on the latest update, you could flash one firmware less than current and then let the phone download and install an OTA to the current version. You'll know that its official if the phone successfully downloads and installs the OTA.
Sent from my SM-N960U using Tapatalk
---------- Post added at 07:35 PM ---------- Previous post was at 07:31 PM ----------
Not sure why you're trying to call me out when I clearly said there are ways for it show official if it's rooted. Also, no one said anything about FRP. If the phone was FRP locked they wouldn't be able to use it at all... Unless you know how to remove an FRP lock, which I do. At that point the phone would work/be a normal phone.
Click to expand...
Click to collapse
point taken on the FRP lock but the real point I was making is that the system status is bogus:
joshw0000 said:
Go to settings > about phone > status and it should say "official". That would tell you if the phones operating system has been modified (rooted).
Click to expand...
Click to collapse

bober10113 said:
point taken on the FRP lock but the real point I was making is that the system status is bogus:
Click to expand...
Click to collapse
You obviously didn't read the entire comment:
"There are ways around that where you can trick the phone into thinking it's not rooted to get those apps to work so, again, that's not a full proof way to check."
Or this comment:
" I used to flip phones up until a couple years ago. I've bought and sold hundreds, maybe thousands of used phones, most of which had my accounts on them at one point and time. I think as long as the phone is running official firmware, isn't bootloader unlocked/rooted, and you've reset it, it should be fine. Of course you run the risk that someone has hacked it, installed spyware at the system level, and somehow overwritten the status to show as official such that the spyware persists even after a reset, but that's highly unlikely."
There are a lot of ways to check. I pointed out some of the simpler ways. None of which are truly bullet proof. Hell, back in the day we could reset knox counters so if someone is going to the extreme to install some spyware and they're smart enough to install anything that would persist a factory reset, even checking knox isn't a full proof method.
And your screenshot really doesn't tell me anything. It's possible to have an unlocked bootloader AND official firmware at the same time. The operating system and bootloader are two different things. It's only when you modify the system that you have to hack the status to make it say official.
Sent from my SM-N960U using Tapatalk

joshw0000 said:
You obviously didn't read the entire comment:
"There are ways around that where you can trick the phone into thinking it's not rooted to get those apps to work so, again, that's not a full proof way to check."
There are a lot of ways to check. I pointed out some of the simpler ways. None of which are truly bullet proof. Hell, back in the day we could reset knox counters so if someone is going to the extreme to install some spyware and they're smart enough to install anything that would persist a factory reset, even checking knox isn't a full proof method.
Click to expand...
Click to collapse
fine but i mean, why ask a user to validate the state of their device via the worst possible method of them all?
he even already posted in OP that he went to DL mode to check the knox fuse status so would supersede by far the need to check via software/status.
edit
and the photo of my device status was just a way to show how i know device actual status and bootlaoder state aren't linked. especialy when rooted devices can spoof software status but none cane spoof fuse state in DL mode. so not sure why you are trying to convince me of something i just proved. u can say u agree next time.

bober10113 said:
fine but i mean, why ask a user to validate the state of their device via the worst possible method of them all?
he even already posted in OP that he went to DL mode to check the knox fuse status so would supersede by far the need to check via software/status.
Click to expand...
Click to collapse
No actually he didn't. He never said he went to DL mode, he just said the knox counter says 0x0. That can be checked via apps from the phone. If the phone was rooted, it could be manipulated to show 0x0 when it's really not.
You're focusing on one sentence dude. Get your panties out of a wod and read the whole comment.
Sent from my SM-N960U using Tapatalk

joshw0000 said:
No actually he didn't. He never said he went to DL mode, he just said the knox counter says 0x0. That can be checked via apps from the phone. If the phone was rooted, it could be manipulated to show 0x0 when it's really not.
You're focusing on one sentence dude. Get your panties out of a wod and read the whole comment.
Click to expand...
Click to collapse
lol. but i did read he went to download menu which i think we can interpret it as download mode. but hey i might wrong. can you show me anywhere in the OS where download menu is?
IqD said:
I checked my Knox counter in the Download menu and it reads 0x00000, maybe more or less zeros.
Click to expand...
Click to collapse

bober10113 said:
lol. but i did read he went to download menu which i think we can interpret it as download mode. but hey i might wrong. can you show me anywhere in the OS where download menu is?
Click to expand...
Click to collapse
What a troll.
Sent from my SM-N960U using Tapatalk

joshw0000 said:
What a troll.
Click to expand...
Click to collapse
that's the spirit!

bober10113 said:
lol. but i did read he went to download menu which i think we can interpret it as download mode. but hey i might wrong. can you show me anywhere in the OS where download menu is?
Click to expand...
Click to collapse
joshw0000 said:
No actually he didn't. He never said he went to DL mode, he just said the knox counter says 0x0. That can be checked via apps from the phone. If the phone was rooted, it could be manipulated to show 0x0 when it's really not.
You're focusing on one sentence dude. Get your panties out of a wod and read the whole comment.
Sent from my SM-N960U using Tapatalk
Click to expand...
Click to collapse
Sorry for the confusion. I was referring to the Download mode by hitting the mentioned buttons on restart. The KNOX reads 0x0000. Also, it says OEM Lock: On. Then you are both saying the phone is safe?
Also, when I first got it, it did find an update OTA and installed it.

IqD said:
Sorry for the confusion. I was referring to the Download mode by hitting the mentioned buttons on restart. The KNOX reads 0x0000. Also, it says OEM Lock: On. Then you are both saying the phone is safe?
Also, when I first got it, it did find an update OTA and installed it.
Click to expand...
Click to collapse
no confusion on my part. i read and understood you correctly the 1st time around.
at first glance your device looks ok but...
additionally, there are ways to check if the device is off a lease with a ESN check. meaning if someone sold you a device still on contract. some sell contractual phones and after a period of time they will get blacklisted since the contract is never payed off fully. so device would appear to work fine and one day they just stop getting a signal and esn/imei get blacklisted.
side note:
surprised that this was not brought up earlier in the conversation as a factor to watch out for by some "experianced in the field flipping devices" user instead of stating the obvious like device status and the unreliable means to check it. especialy since, said user stated buying and selling hundred and even thousands of phones...!? ESN state would be no. 1 in the check list if things to watch out for.
anyways back to the current case, there are ESN/IMEI check services in the web to see status of device: stolen, still on contract...etc. i cannot provide any suggestion to these services unfortunately. this is something you need to check yourself or ask around.
good luck

IqD said:
I had been looking for a new phone for awhile. Settled on a Note 9 because I wanted to try using the S Pen for work and dislike the Note 10 design. However, they are still sold at full price where I live, so I bought one secondhand. Everything seems generally fine with it, minus some freezing or weird reactions when it charges for awhile or restarts. But I have been skeptical of throwing passwords (personal and for work) on it to this point. Thats because I read an article about potential root level or firmware level spyware that remains after a reset.
I did a reset AND even took it to an official service center to flash new firmware (but they said they cannot do it there, but they did some kind of more advanced reset?). I checked my Knox counter in the Download menu and it reads 0x00000, maybe more or less zeros. Samsung pass, pay, health, and secure folder all seem to work (I can register for them, use the bio sensor). That all sounds like it has not been tampered with in any way, correct?
Thanks for the help.
Click to expand...
Click to collapse
Reading this thread I've come to the conclusion that you should sell your rootable and boot unlockable device and buy a locked down USA model.
Thank me later. Least you'll be able to sleep well now.
Sent from my SM-G975U using Tapatalk

IqD said:
Sorry for the confusion. I was referring to the Download mode by hitting the mentioned buttons on restart. The KNOX reads 0x0000. Also, it says OEM Lock: On. Then you are both saying the phone is safe?
Also, when I first got it, it did find an update OTA and installed it.
Click to expand...
Click to collapse
It's about as safe, in terms of spyware, as you'll ever get from a used phone. I would assume you checked the ESN before buying it but if not, run a check with swappa.com/esn and checkesnfree.com to make sure it's clean. Screenshot the results and save them. Depending on your carrier you can likely run a check on their website and/or call support and ask them as well. As with any unlocked phone, know that you may not get all of the features that a carrier branded phone would have (i.e. I couldn't get WiFi calling working on a Korean S10 on Verizon).
Sent from my SM-N960U using Tapatalk