Related
Hi, I have an i9505 which I have rooted with the help of some of the guides on here.
Anyway, I encrypted my phone from settings -> security not really knowing what I was doing. I was just thinking that it would make my phone more secure or whatever.
Anyway, following this I now have to enter a password every time I lock my phone screen which I find very inconvenient and I understand that I can't install any custom roms in the future.
I have tried to decrypt the phone from settings -> security but the process doesn't seem to complete.
It says that the decrypting process is irreversible ect ect.. it will take one hour ect... ect.. then when I click to confirm it and begin the decryption process the phone just seems to switch off then it turns back on by itself within 30-60 seconds and that is it. The phone is still encrypted?
Can anyone help me please?
I am really gutted!!!
Thanks
I am experiencing the same problem right now, did you ever find a solution?
imstilly said:
Hi, I have an i9505 which I have rooted with the help of some of the guides on here.
Anyway, I encrypted my phone from settings -> security not really knowing what I was doing. I was just thinking that it would make my phone more secure or whatever.
Anyway, following this I now have to enter a password every time I lock my phone screen which I find very inconvenient and I understand that I can't install any custom roms in the future.
I have tried to decrypt the phone from settings -> security but the process doesn't seem to complete.
It says that the decrypting process is irreversible ect ect.. it will take one hour ect... ect.. then when I click to confirm it and begin the decryption process the phone just seems to switch off then it turns back on by itself within 30-60 seconds and that is it. The phone is still encrypted?
Can anyone help me please?
I am really gutted!!!
Thanks
Click to expand...
Click to collapse
Encryption is irreversible without a factory restore.
read here http://www.dummies.com/how-to/content/encrypt-your-samsung-galaxy-s-4.html
did you try to back to stock with odin?
samersh72 said:
Encryption is irreversible without a factory restore.
read here http://www.dummies.com/how-to/content/encrypt-your-samsung-galaxy-s-4.html
did you try to back to stock with odin?
Click to expand...
Click to collapse
I was keeping my hopes going because there is a "decrypt device" option in the security settings, but that wouldn't work and I was hoping I was ****ing it up somehow. Guess device cleansing is my only option.
Penetal said:
I was keeping my hopes going because there is a "decrypt device" option in the security settings, but that wouldn't work and I was hoping I was ****ing it up somehow. Guess device cleansing is my only option.
Click to expand...
Click to collapse
Samsung device have the "decrypt device" option and it works, tried it multiple times.
Decrypting a Samsung Galaxy S4
Had the same problem several times. Make sure "USB Debugging" is off in the "Developer Options" section of the Settings screen.
Dont fret....go to settings<lock screen and then change it to swipe....Hope this works!
imstilly said:
Hi, I have an i9505 which I have rooted with the help of some of the guides on here.
Anyway, I encrypted my phone from settings -> security not really knowing what I was doing. I was just thinking that it would make my phone more secure or whatever.
Anyway, following this I now have to enter a password every time I lock my phone screen which I find very inconvenient and I understand that I can't install any custom roms in the future.
I have tried to decrypt the phone from settings -> security but the process doesn't seem to complete.
It says that the decrypting process is irreversible ect ect.. it will take one hour ect... ect.. then when I click to confirm it and begin the decryption process the phone just seems to switch off then it turns back on by itself within 30-60 seconds and that is it. The phone is still encrypted?
Can anyone help me please?
I am really gutted!!!
Thanks
Click to expand...
Click to collapse
Last night i had the same problem but i managed to fix
If you press decode it says password and then enter a password of at least 6 digits AND AT LEAST 1 NUMBER to activate the decoding part i tottaly missed that but i realized it a few hours after.
And then it started decoding for about half an hour and it was fixed.
Hope this was usefull so you wont need a system reset.
Given that the original post was in 2013, the OP likely had to reset, if none of the other posts from 2013 in the thread helped.
4.1/2 years on - there must be someone out there that knows how to decrypt the GT-I9195 ??
I spent yesterday researching pro's & con's of encrypting my phone. Couldn't find anyone saying password had to be entered EVERY TIME I USE the phone, just people wrongly advising that I would have to enter password every time I switch the phone on. I could live with that, I thought, so I encrypted it. Big mistake. Why anyone wants a phone that needs a password on every use, I do not know.
Please help me decrypt my phone. Thanks
Hello! My Galaxy Note 3 Exynos SM-N900 is now officialy a brick, so I guess this thread will help others to not do the same as I did. Here I go:
As you guys know, Exynos version of the Galaxy Note 3 doesn't have a lot of custom roms, so, I get tired of waiting for the kitkat update, donwloaded the Crisktelo rom 4.4.2, and flash it. Nothing wrong. The problem get with the camera, it works but takes so poor quality photos.
I tried to get back to stock, I get the Panama's TBA 4.4.2 stock firmware from Sammobile, because I am from Costa Rica and my Sammy is unlocked carrier free. Flashed as usual using Odin but the phone was the same no data was deleted, just the firmware changed. I wanted to get full wype to start again, backup everything and make factory reset using the menu on the phone. I totally forgot that the security option using Samsung Account to prevent theft was enabled. So I get to the screen of Samsung Account and get the ERR_0000 (Processing Failed) when I put my email and password for my Sammy Account. Aparently there is no way no get my phone back, this error is very weird in forums to happens and tried everything, from changing my password, by unsuscribing my account and enable it again. Flash the stock firmware several times, and as you know I can get the warranty because of the Know counter.
So maybe some of you are thinking to use that security feature, I guess if you use custom roms is a bad idea, but if you use stock there is no problem, even if your phone gets stolen, neither the thief or you can get it work again.
PS: I know ther is a thread similar to this one, but the difference is I KNOW my password and user, and this error is in the equation. So maybe I can get help or get help to others. Either way, I'm looking for a new phone, HTC One or LG G2?
As u can see Processing Error means -> wrong email/account has been entered.
Please use the correct account fro N900 otherwise u need to perfrom EFS clear
Also, can you check REACTIVATION LOCK in download mode and post result.
That is surely an expensive lesson. I guess Samsung Service Center can help you out providing that u can bring prove of purchase and be prepared for some financial charges as this kind of thing is surely out of warranty.
exprxp said:
As u can see Processing Error means -> wrong email/account has been entered.
Please use the correct account fro N900 otherwise u need to perfrom EFS clear
Also, can you check REACTIVATION LOCK in download mode and post result.
Click to expand...
Click to collapse
I read the whole thread but apparently is not available for end users just for Samsung Support... I think that is the solution but I can`t do it. But thanks!
nlatifolia said:
That is surely an expensive lesson. I guess Samsung Service Center can help you out providing that u can bring prove of purchase and be prepared for some financial charges as this kind of thing is surely out of warranty.
Click to expand...
Click to collapse
Indeed. My note 3 is just 3 months old, I have the invoice, I will send the phone this saturday to them, if they charge me more than $200 to do that I will let the phone as a loss and buy a new one. I'll update this thread.
JosHeron said:
Indeed. My note 3 is just 3 months old, I have the invoice, I will send the phone this saturday to them, if they charge me more than $200 to do that I will let the phone as a loss and buy a new one. I'll update this thread.
Click to expand...
Click to collapse
Noone will charge you.
JosHeron said:
Hello! My Galaxy Note 3 Exynos SM-N900 is now officialy a brick, so I guess this thread will help others to not do the same as I did. Here I go:
As you guys know, Exynos version of the Galaxy Note 3 doesn't have a lot of custom roms, so, I get tired of waiting for the kitkat update, donwloaded the Crisktelo rom 4.4.2, and flash it. Nothing wrong. The problem get with the camera, it works but takes so poor quality photos.
I tried to get back to stock, I get the Panama's TBA 4.4.2 stock firmware from Sammobile, because I am from Costa Rica and my Sammy is unlocked carrier free. Flashed as usual using Odin but the phone was the same no data was deleted, just the firmware changed. I wanted to get full wype to start again, backup everything and make factory reset using the menu on the phone. I totally forgot that the security option using Samsung Account to prevent theft was enabled. So I get to the screen of Samsung Account and get the ERR_0000 (Processing Failed) when I put my email and password for my Sammy Account. Aparently there is no way no get my phone back, this error is very weird in forums to happens and tried everything, from changing my password, by unsuscribing my account and enable it again. Flash the stock firmware several times, and as you know I can get the warranty because of the Know counter.
So maybe some of you are thinking to use that security feature, I guess if you use custom roms is a bad idea, but if you use stock there is no problem, even if your phone gets stolen, neither the thief or you can get it work again.
PS: I know ther is a thread similar to this one, but the difference is I KNOW my password and user, and this error is in the equation. So maybe I can get help or get help to others. Either way, I'm looking for a new phone, HTC One or LG G2?
Click to expand...
Click to collapse
You're not alone here, and I can tell you that this problem has absolutely nothing to do with the fact that you're using a custom rom, because my phone is on the stock 4.4 rom, and has never been rooted, wiped (until now), or tampered with.
This is not an "Expensive lesson," or a mistake on your part.
This is a broken feature of the note 3 device, and I have been on and off the phone with samsung all day.
So far there is nothing they can do from their end. And for those of you who are wondering, yes, you can log into your samsung account from your PC or whatever, but the activation lock will not let you in. I'm still working on resolving this issue. I think it's a problem with Samsung's login gateway to be honest. I experienced this last night at 10pm, and so far it hasn't been fixed.
So far I have this:
10pm - 7am EST: "Processing Failed.(ERR_0000)"
7am - 9am EST: "Unfortunately Samsung Login has stopped."
10am - 2pm EST: Processing failed
Between not letting me in and crashing, everything else has been pretty useless. Don't waste any more time formatting or wiping.
I CAN tell you that the minute I get back into the phone, I'm returning it to stock and putting it up for sale.
zer0xp said:
You're not alone here, and I can tell you that this problem has absolutely nothing to do with the fact that you're using a custom rom, because my phone is on the stock 4.4 rom, and has never been rooted, wiped (until now), or tampered with.
This is not an "Expensive lesson," or a mistake on your part.
This is a broken feature of the note 3 device, and I have been on and off the phone with samsung all day.
So far there is nothing they can do from their end. And for those of you who are wondering, yes, you can log into your samsung account from your PC or whatever, but the activation lock will not let you in. I'm still working on resolving this issue. I think it's a problem with Samsung's login gateway to be honest. I experienced this last night at 10pm, and so far it hasn't been fixed.
So far I have this:
10pm - 7am EST: "Processing Failed.(ERR_0000)"
7am - 9am EST: "Unfortunately Samsung Login has stopped."
10am - 2pm EST: Processing failed
Between not letting me in and crashing, everything else has been pretty useless. Don't waste any more time formatting or wiping.
I CAN tell you that the minute I get back into the phone, I'm returning it to stock and putting it up for sale.
Click to expand...
Click to collapse
Thanks! I try to spread this info to as many people as I can, Google+, Twitter, Facebook... People need to know that Samsung is doing this, and I know that this "feature" is not well implemented, I will go to the store and try to get a replacement. If Samsung is keeping this Knox and other security "fails" features, they are gonna keep me away from their products. Please keep updating if you get your device back working.
zer0xp said:
You're not alone here, and I can tell you that this problem has absolutely nothing to do with the fact that you're using a custom rom, because my phone is on the stock 4.4 rom, and has never been rooted, wiped (until now), or tampered with.
This is not an "Expensive lesson," or a mistake on your part.
This is a broken feature of the note 3 device, and I have been on and off the phone with samsung all day.
So far there is nothing they can do from their end. And for those of you who are wondering, yes, you can log into your samsung account from your PC or whatever, but the activation lock will not let you in. I'm still working on resolving this issue. I think it's a problem with Samsung's login gateway to be honest. I experienced this last night at 10pm, and so far it hasn't been fixed.
So far I have this:
10pm - 7am EST: "Processing Failed.(ERR_0000)"
7am - 9am EST: "Unfortunately Samsung Login has stopped."
10am - 2pm EST: Processing failed
Between not letting me in and crashing, everything else has been pretty useless. Don't waste any more time formatting or wiping.
I CAN tell you that the minute I get back into the phone, I'm returning it to stock and putting it up for sale.
Click to expand...
Click to collapse
I have had the exact same experience. A guy from tech support in the US said that mine may be trying to authenticate in the US, but since it is from Panama, it is conflicting and causing the error. He also mentioned a seemingly universal unlock code that can be provided from Samsung in the UK. I have already spent 10USD adding Skype credit in order to contact them, but they were closed when I called. I'm going to attempt it tomorrow. I will be destroyed if I have to send my phone to Panama or a similar place; the wait and customs can be aggravating.
The phone was so awesome (minus the volume warnings and skype vs call app default selection not working) before I upgraded to KitKat. I just wanted to factory reset it to make it stable :/
We should warn people not to select that Samsung Account option; it is certainly not stable.
lagoboss said:
I have had the exact same experience. A guy from tech support in the US said that mine may be trying to authenticate in the US, but since it is from Panama, it is conflicting and causing the error. He also mentioned a seemingly universal unlock code that can be provided from Samsung in the UK. I have already spent 10USD adding Skype credit in order to contact them, but they were closed when I called. I'm going to attempt it tomorrow. I will be destroyed if I have to send my phone to Panama or a similar place; the wait and customs can be aggravating.
The phone was so awesome (minus the volume warnings and skype vs call app default selection not working) before I upgraded to KitKat. I just wanted to factory reset it to make it stable :/
We should warn people not to select that Samsung Account option; it is certainly not stable.
Click to expand...
Click to collapse
Yeah, that's definitely not a bad idea.
If you find out anything about this "universal unlock code," be sure to post it here for the rest of us!
zer0xp said:
Yeah, that's definitely not a bad idea.
If you find out anything about this "universal unlock code," be sure to post it here for the rest of us!
Click to expand...
Click to collapse
Will do. If you can beat me to it, here is the "elevated tech support" number US: 1-888-987-4357 and this is the number in the UK that he gave me for the probable pipe dream code lol 4401932454358.
lagoboss said:
Will do. If you can beat me to it, here is the "elevated tech support" number US: 1-888-987-4357 and this is the number in the UK that he gave me for the probable pipe dream code lol 4401932454358.
Click to expand...
Click to collapse
I talk with the support in Panamá today. Because I Live in Costa Rica, I can call them for free. They didn't tell me anything about the universal unlock code. But only I have to take my phone back to the store and they will reset it. I Was wondering about what you say, how they can give you a unlock code even if they can't verify from distancie that you are the true owner of the phone?
I read in another thread here that Samsung support guys can only reset the phones verifying the true autenticy of the owner. If you wish, i can call samsung support in Panamá today and así if your phone using a firmware from Panamá needs to be sent there. I guess not but I can ask.
JosHeron said:
I talk with the support in Panamá today. Because I Live in Costa Rica, I can call them for free. They didn't tell me anything about the universal unlock code. But only I have to take my phone back to the store and they will reset it. I Was wondering about what you say, how they can give you a unlock code even if they can't verify from distancie that you are the true owner of the phone?
I read in another thread here that Samsung support guys can only reset the phones verifying the true autenticy of the owner. If you wish, i can call samsung support in Panamá today and así if your phone using a firmware from Panamá needs to be sent there. I guess not but I can ask.
Click to expand...
Click to collapse
That would be so helpful. Please ask them about it because my Spanish sucks lol. And please report back about the reset experience.
As far as that code, I admit that it does sound fishy like most things Sammy reps say. I thought they would investigate the processing failure instead of exploring the possibility that it wasnt really my phone.
I hope all goes well with resetting yours.
Sent from my XT560 using xda app-developers app
Thanks again JosHeron for offering to talk to Sammy in Panama for me.
I fixed my issue I used a XXUDNA9 4.4.2 KitKat rom that I flashed with ODIN 3.7. Once I flashed the rom, the phone rebooted and then it said that it was optimizing the apps. After that, I went through all of the steps and on the sign-in screen, it accepted my Sammy account and password on the first try.
Here is my theory on what caused the issue. When I did the recovery screen (vol up, home, power) wipe data and erase all, I think that it tripped the abnormal reset thing. Im not sure if it would do the processing failed if I had reset the phone from the settings menu. In any case, attempt to reinstall XXUDNA9 4.4.2 KitKat and then try to enter the Samsung account and Password.
Detailed Steps:
I am assuming that you have a SM-N900 International Note 3. If your phone does not boot with SM-N900 on the splash screen, find the appropriate stock rom for your phone. Otherwise, you can break your phone
This process should could take 4 hours +/- 1 depending on your internet speed.
Step 1: Get Materials (Adapted from http://nasirtech.blogspot.com/2014/02/n900xxudna9-android-442-kitkat-firmware.html)
- Download KitKat XXUDNA9 4.4.2 for SM-N900: http://terafile.co/3120933f433b
- Download Odin Verision 3.07 (3.09 does not play well with Note 3 and the old KitKat): https://copy.com/zowadQ32bn9T
Step 1: Factory Wipe and Clear Cache (Adapted from http://nasirtech.blogspot.com/2014/02/n900xxudna9-android-442-kitkat-firmware.html)
- Switch off the phone
- Remove the battery and then re-insert it after several seconds
- Next, press and hold simultaneously Volume Up, Home and Power.
- Release the buttons when the screen flickers and then wait for the Recovery Mode main screen to appear.
- If the Recovery Mode doesn’t boot, then you should keep trying until it does.
- Select factory wipe with the volume up key and then the power button, confirm
- Select Clear Cache
- Reboot the phone in normal mode by selecting the Reboot option.
Step 2: Make Sure the Phone to at least 80% capacity
Step 3: Reinstall KitKat XXUDNA9 (Adapted from http://nasirtech.blogspot.com/2014/02/n900xxudna9-android-442-kitkat-firmware.html)
- Switch off your phone and boot Galaxy Note 3 N900 into Download Mode by pressing and holding the Volume Down+Home+Power buttons (long press until the boot screen appear), now press Volume Up key to proceed to Download Mode.
- Extract the downloaded Odin3.07 zip file and run the Odin3 v3.07.exe file as an administrator (Right click on the .exe file and click on Run as administrator)
- Now connect your Galaxy Note 3 N900 to your computer via USB cable
- In Odin3 screen, you should see a COM Port number like “0:[COM7]” at ID:COM section and “Added!” text at the message box. This means -your device has been detected by Odin3.
- Make sure that, only the “Auto Reboot” and “F. Reset Time” options are checked. Failure to do so can brick (break/damage your device)
- Now, extract the downloaded firmware zip file, you’ll find a firmware file with extension .tar.md5
- In Odin screen, click on PDA button and select the firmware file with .tar.md5 extension (The firmware file look something like: N900XXDLJ5_N900ODDDLI7_INU.tar.md5)
- Now, click on the Start button to begin the installation process, wait few moments.
- Once completed, you would see “PASS!” message in ID:COM port having green background
- Your phone should automatically reboot after completion
- You can now disconnect your phone from computer
You should be able to enter your Samsung Account and Password without processing error_0000 now.
(Update: There is an issue with the Internet browser, flash the latest KitKat to fix)
Although it is fixed, I'm still scared about what else Samsung and Knox may do. I love the phone, but the thought of $700.00 down the drain was pretty horrific.
Lessons learned: Turn off that Samsung Activation thing before reset and don't update the phone until most users say that it is stable.
I hope this helps. I'm going to get some sleep. I've spent the night obsessing over it lol
lagoboss said:
Thanks again JosHeron for offering to talk to Sammy in Panama for me.
I fixed my issue I used a XXUDNA9 4.4.2 KitKat rom that I flashed with ODIN 3.7. Once I flashed the rom, the phone rebooted and then it said that it was optimizing the apps. After that, I went through all of the steps and on the sign-in screen, it accepted my Sammy account and password on the first try.
Here is my theory on what caused the issue. When I did the recovery screen (vol up, home, power) wipe data and erase all, I think that it tripped the abnormal reset thing. Im not sure if it would do the processing failed if I had reset the phone from the settings menu. In any case, attempt to reinstall XXUDNA9 4.4.2 KitKat and then try to enter the Samsung account and Password.
(Update: Email, the default Samsung app may crash. In order to fix, navigate to settings-> application manager -> Email -> and then force stop. Next clear the cache.)
Although it is fixed, I'm still scared about what else Samsung and Knox may do. I love the phone, but the thought of $700.00 down the drain was pretty horrific.
Lessons learned: Turn off that Samsung Activation thing before reset and don't update the phone until most users say that it is stable.
I hope this helps. I'm going to get some sleep. I've spent the night obsessing over it lol
Click to expand...
Click to collapse
It really does give me great pleasure to announce that this method worked for me as well. I'm gonna go out on a limb and say that the rough, official fix for this issue is as follows: (you'll get more detailed instructions on flashing and using Odin elsewhere, typing this quickly at work)
1) Download XXUDNA9 4.4.2 firmware for the SM-N900
2) Download Odin 3.07 (it is reported that the note 3 doesn't play well with 3.09)
3) connect your phone to your pc, open Odin and select your md5 file under PDA
4) allow it to complete the flashing process and then log into your Samsung account
Thanks to everyone who helped in trying to figure this out. I'm gonna check back and make sure everyone's phone was fixed.
Good luck!
lagoboss said:
Thanks again JosHeron for offering to talk to Sammy in Panama for me.
I fixed my issue I used a XXUDNA9 4.4.2 KitKat rom that I flashed with ODIN 3.7. Once I flashed the rom, the phone rebooted and then it said that it was optimizing the apps. After that, I went through all of the steps and on the sign-in screen, it accepted my Sammy account and password on the first try.
Here is my theory on what caused the issue. When I did the recovery screen (vol up, home, power) wipe data and erase all, I think that it tripped the abnormal reset thing. Im not sure if it would do the processing failed if I had reset the phone from the settings menu. In any case, attempt to reinstall XXUDNA9 4.4.2 KitKat and then try to enter the Samsung account and Password.
(Update: Email, the default Samsung app may crash. In order to fix, navigate to settings-> application manager -> Email -> and then force stop. Next clear the cache.)
Although it is fixed, I'm still scared about what else Samsung and Knox may do. I love the phone, but the thought of $700.00 down the drain was pretty horrific.
Lessons learned: Turn off that Samsung Activation thing before reset and don't update the phone until most users say that it is stable.
I hope this helps. I'm going to get some sleep. I've spent the night obsessing over it lol
Click to expand...
Click to collapse
Well, finally I can join and tell that my phone is back and running as before. Thank you guys, this method is the real fix for this issue and as always, I can find better support here than the official one.
7 days without the phone was horrible, because I had to use a laggy, crashed screen iPhone 4 with those little keyboards. God, no. I repeat Thank you!
JosHeron said:
Well, finally I can join and tell that my phone is back and running as before. Thank you guys, this method is the real fix for this issue and as always, I can find better support here than the official one.
7 days without the phone was horrible, because I had to use a laggy, crashed screen iPhone 4 with those little keyboards. God, no. I repeat Thank you!
Click to expand...
Click to collapse
I had the same problem, but after doing the procedure described before is working as well, I must say thank you to give us a solution, everything is working as before with my phone. thanks again.
I know this is off topic, but do you guys know of a real backup without root? After I reinstalled kitkat and restored the backup, I was not impressed; Kies is a joke
Sent from my SM-N900 using xda app-developers app
lagoboss said:
I know this is off topic, but do you guys know of a real backup without root? After I reinstalled kitkat and restored the backup, I was not impressed; Kies is a joke
Sent from my SM-N900 using xda app-developers app
Click to expand...
Click to collapse
I never do a "real" backup, I just backup my photos on OneDrive, Dropbox and Google+. My sms and whatsapp chats always get lost and the others like Telegram have sync. But do you ever tried Helium?
JosHeron said:
I never do a "real" backup, I just backup my photos on OneDrive, Dropbox and Google+. My sms and whatsapp chats always get lost and the others like Telegram have sync. But do you ever tried Helium?
Click to expand...
Click to collapse
Helium looks like it could work. I lost my subway surfer progress after I fixed the phone. With kies, it only saved text messages, photos and music, and some other useless settings. I think I may have backed up incorrectly with kies. When I selected apps, I don't think all of them were actually selected.
Anyhow, I'm definitely going to try helium. Some people in the comments said that it backed up the kind of data that I'm interested in.
Thanks.
Sent from my SM-P600 using xda app-developers app
So I fell victim to googles new FRP Security feature that requires you to log in using the same gmail account associated with the phone before it was reset. Short of it was I decided to flash a 6.0 ROM after using the 5.1.1 ROM to get my Project Fi account activated correctly.
After flashing 6.0 and I began going through the setup wizard where I was eventually prompted to enter the credentials for the account that I had used previously. I entered my credentials and was then sent to another screen asking me to reset my Gmail password (Turns out google decided my login attempt was suspicious...). So i reluctantly reset the password not knowing I had just screwed myself(for 72 hours at least). There is a 72 hour reset time from the time you changed your account password until you're able to use it to authenticate during the setup process and until you authenticate you cant use the phone.
Not having a backup phone I took to google and found that the only way around this problem involved a USB OTG storage device loaded with an apk that causes the settings app to launch allowing you to do a real factory reset(complete wipe of all credentials and data). Resetting the phone this way removes any account associations allowing you to setup the phone as if it were new once you've re-flashed it.
Not having the tools needed to do it that way I thought about it and decided to try a few things out and eventually found my solution.
Disclaimer: I am not responsible for any damage or loss of data that may result from the following procedure.
Solution
Requirements
A computer with adb installed
USB cable
Rom with Persistent ADB Enabled (I used the 5.1.1 Stock, Rooted Project Fi ROM)
Phone booted and at the Setup Wizard
Procedure
Have the phone turned on and sitting at the startup wizard
Connect the USB to you computer and then plugin your phone ( I assume you've already setup ADB)
The phone may then prompt you and ask to verify the device fingerprint which you will say yes to
open a terminal and type:
Code:
adb shell
Code:
am start -S com.android.settings -c android.intent.category.LAUNCHER 1
This will launch the Settings.apk
***NOTE: This will completely wipe your phone!*** (Edit: The Reset program claims to wipe all internal storage but for whatever reason my SDcard data was not touched. Would still recommend pulling any wanted data from the device prior to resetting)
Go to the Backup & Reset menu and perform a factory reset
After the phone finishes resetting, proceed to boot back into Recovery mode and re-flash your ROM
The Setup Wizard will now go through the steps without the FRP authentication steps.
Again, I have only tested this on my T-Mobile Nexus 6 (using Project Fi) running 5.1.1 so your mileage may vary depending on your setup. If you find this worked or didn't work for your particular setup/situation then post your results here.
Hope this helps!
EDIT: The original solution using the USB OTG storage can be found here.
Just to clarify a bit. The problem that these two methods try and fix stems from a new feature introduced in Lollipop called FRP(Factory Reset Protection). It is meant to keep someone that has stolen a phone from being able to use it by simply doing a factory reset and reinstalling the OS. To counter this, google requires the user to verify they're the owner of the device that was reset by giving the credentials of the google account associated with the phone before it was reset. The issue arises when the password to this account is changed after the device was reset but before verifying ownership of the device during the setup process. When this happens, you have to wait 72 hours before you will be able to verify ownership using the new password.
Edit 2: Specified having a ROM with Persistent ADB Enabled as a requirement for this to work.
I don't really follow your problem. It sounds like you may be using 2 factor authentication? If not You Should!
Also once you set up 2 factor make sure to print out the one time codes.
Maybe that wouldn't fix this, but I thought this was one of the things the one time codes get around.
Sorry if you're really saying that you can't reset your phone for 3 days after you change your password. If it is really that simple it seems pretty broken. I'd call Google on the phone. They are the only major corporation I've ever seen that has a phone answered by people that know what they're doing and can actually help you.
Sent from my Nexus 6 using Tapatalk
joyrida12 said:
...snip...
Click to expand...
Click to collapse
Ah, a workaround, nice!!! Tahnks for sharing!
Keep "OEM unlocking" enabled in the future. It will disable "Device protection"
---------- Post added at 02:27 PM ---------- Previous post was at 02:27 PM ----------
ethutch said:
I don't really follow your problem. It sounds like you may be using 2 factor authentication? If not You Should!
Also once you set up 2 factor make sure to print out the one time codes.
Maybe that wouldn't fix this, but I thought this was one of the things the one time codes get around.
Sorry if you're really saying that you can't reset your phone for 3 days after you change your password. If it is really that simple it seems pretty broken. I'd call Google on the phone. They are the only major corporation I've ever seen that has a phone answered by people that know what they're doing and can actually help you.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
This is not about 2 way auth i'm affraid
ethutch said:
I don't really follow your problem. It sounds like you may be using 2 factor authentication? If not You Should!
Also once you set up 2 factor make sure to print out the one time codes.
Maybe that wouldn't fix this, but I thought this was one of the things the one time codes get around.
Sorry if you're really saying that you can't reset your phone for 3 days after you change your password. If it is really that simple it seems pretty broken. I'd call Google on the phone. They are the only major corporation I've ever seen that has a phone answered by people that know what they're doing and can actually help you.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
No, this isn't an issue with 2FA. From Google's standpoint this isn't an issue at all actually. This verification is, to my understanding, only required when the device is factory reset in recovery mode.
The purpose of 72 hour lock period seems to be there to protect user in the event someone is trying to gain access to their phone/account.
This normally isn't an issue since most people won't change their password in that small timeframe. In order to not require the verification, you have to disassociate the account from the phone before resetting it. This is done for you when you do a reset from the settings app on the phone. That's the reason for using these methods, it does a full reset including account removal.
Sent from my Nexus 6 using Tapatalk
@joyrida12
Would you mind sharing the other solution you found? The one *with* USB OTG.
Thanks in advance!
Droidphilev said:
@joyrida12
Would you mind sharing the other solution you found? The one *with* USB OTG.
Thanks in advance!
Click to expand...
Click to collapse
Edited the post and added a link to it
Sent from my Nexus 6 using Tapatalk
joyrida12 said:
Edited the post and added a link to it
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
perfect, thanks!
Great work around.
I love that Google is putting in theft detection. A good fix to this chaos would be to require you to auth to do a reset from settings. That would close the hole. They also need to allow you to skip the 72 hour reset time with more security questions/answers. You know Google caches your PC settings. Simply logging into your google account from a known PC would be a great way to allow account authentication.
I am about to return my phone to amazon so just factory resetting through the settings menu will be fine for returning the phone so the next person doesn't have problems?
Sent from my Nexus 6 using Tapatalk
So to recap. It will NOT work on a device that was reset. Since USB debugging is off after a reset.
player911 said:
Great work around.
I love that Google is putting in theft detection. A good fix to this chaos would be to require you to auth to do a reset from settings. That would close the hole. They also need to allow you to skip the 72 hour reset time with more security questions/answers. You know Google caches your PC settings. Simply logging into your google account from a known PC would be a great way to allow account authentication.
Click to expand...
Click to collapse
That was my thoughts exactly as it was happening to me, I initially was trying to figure out if there was an alternate authentication method and was a little surprised not to find one.
I really like the direction they're moving with thus security feature but I think it was thrown out a bit early. Nexus users are more likely to be doing factory resets and locking them with no way of fixing it (aside from waiting 3 days) out because they did so on a custom recovery isn't very cool on their part lol.
Sent from my Nexus 6 using Tapatalk
sthpaw01 said:
I am about to return my phone to amazon so just factory resetting through the settings menu will be fine for returning the phone so the next person doesn't have problems?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Yes, that will work just fine.
yossijoe said:
So to recap. It will NOT work on a device that was reset. Since USB debugging is off after a reset.
Click to expand...
Click to collapse
It worked for me. Before I figured this method out I had reset and flashed 2 6.0 ROMs and then the 5.1.1 ROM. Once I got to the setup wizard my device was listed under adb devices and I was able to get a shell.
Edit: It could be that the project fi ROM has USB debugging enabled by default(just a guess, haven't looked at the source to verify).
Edit 2: Confirmed that the Stock, Rooted, decrypted 5.1.1 ROM for Project Fi has persistent ADB enabled. Adding this as a requirement to the original post.
Sent from my Nexus 6 using Tapatalk
sthpaw01 said:
I am about to return my phone to amazon so just factory resetting through the settings menu will be fine for returning the phone so the next person doesn't have problems?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
He's wrong, that absolutely will not be fine.
You need to make sure to remove any screen locking you've setup, sync your Google account, and then remove your Google account before resetting.
http://forum.xda-developers.com/nexus-6/general/guide-properly-prepare-nexus-6-resale-t3104504
My nexus 6 doesn't have custom recovery installed,It has only stock one,the phone is on stock rom,and it is stuck in setup screen asking for 1st used gmail !
I have OTG usb cable but it is useless ,not working, seems motorola improved security in nexus 6,to be specific the phone has OEM lock ,so i can't install cust.recovery
is there any trick to apply those adb commands ?
any help friends ? im still stuck ,any way to disable OEM lock or to flash custom rom on frp locked nexus6 ?
joyrida12 said:
Before I figured this method out I had reset and flashed 2 6.0 ROMs and then the 5.1.1 ROM. Once I got to the setup wizard my device was listed under adb devices and I was able to get a shell.
...
.... the project fi ROM has USB debugging enabled by default
Click to expand...
Click to collapse
It seems you can enable persistent ADB and USB debugging on any ROM, as long as you can connect to the phone through ADB in recovery mode.
You just have to add a few lines to a file or two, then reboot the phone. See this post http://forum.xda-developers.com/showpost.php?p=47423916&postcount=5
W60 said:
It seems you can enable persistent ADB and USB debugging on any ROM, as long as you can connect to the phone through ADB in recovery mode.
You just have to add a few lines to a file or two, then reboot the phone. See this post http://forum.xda-developers.com/showpost.php?p=47423916&postcount=5
Click to expand...
Click to collapse
Hey, first time poster, long time lurker. This is the first thing I have not been able to find a solution for.
In order to connect to ADB in recovery, does one need a custom recovery? My Nexus 6 bootloader is locked, running 5.1.0 LMY47D. I have fastboot access but can't pull up an ADB shell.:crying::crying:
I bought a Nexus 6 on eBay that was reset and I do not have the original users info. (I thought I was getting a pretty sweet deal because I'm so good at phones and blah blah)
Thanks in advance for any assistance!
- Beej
Beej4real said:
In order to connect to ADB in recovery, does one need a custom recovery?
Click to expand...
Click to collapse
As far as I know, yes, you need a newer version of a custom recovery. Anyway, if ADB doesn't connect, you certainly need another recovery, and you can't install that if you have a locked bootloader.
....
In the Welcome screen, have you tried the OTG trick, or any of the other methods that seem to allow you to get in Settings, from where you can do a proper reset?
W60 said:
In the Welcome screen, have you tried the OTG trick, or any of the other methods that seem to allow you to get in Settings, from where you can do a proper reset?
Click to expand...
Click to collapse
I did give it a shot. No dice. I also tried entering lots of numbers in as the emergency number. No response from the phone.
Hi guys can you help to frp bypass on Samsung SM-G530H Galaxy Grand Prime without otg function, can i use this tut or need another rom for sm-g530h? where i can find Rom with Persistent ADB Enabled? Thanks
Alright so im dead set on rooting my phone once i realised why the **** not. Im used to jailbreaking iphones and i used to do that alot. (man its so much more complicated on android).
and im god damn stuck on the first step already.
the freaking OEM unlock option is missing??? Im into the developer mode. its not there. Now i know you have to wait 7 Days, but ive had the phone for 2 months. Is it because Ive just updated it to oreo and it reset that timer so now i have to wait seven days... (im sadly a pretty impatient person, im trying to do this at 2am instead of sleeping)
I have an international version and i know its possible. Ive got the SM-G950F Model
Please help. theres so many different guides for so many separate things and old posts and different phones and models and situations.. :c
Same problem here. BUMP!!!
I have also the same problem. my model is G955f Exynos. after flashing official Oreo Rom, CRB7, then updating that to CRE3, I can flash nothing again, not TWRP, not Cf-root, not even nougat Rom. I have tried different versions of Odin, TWRP, and Cf-root but no result. And there is also no damn OEM unlock in Developers options. Does anyone have any solution?
someone has posted here a software named "Cygwin". Its Linux tool, so hard and complicated to use for me.
If anyone can find how to use "Cygwin" to erase Nand and flash again, please reply.
the post Address is this;
https://forum.xda-developers.com/chef-central/android/nand-write-start-fail-odin-soluction-t2851096
Go into the settings and turn off auto-detect time. And time to transfer a month ago. Next, the developer options disable auto-update. Then go into the firmware update to disable the automatic download and click on download updates. Reboot the device and it will appear. I always do that !!!
altai1963 said:
Go into the settings and turn off auto-detect time. And time to transfer a month ago. Next, the developer options disable auto-update. Then go into the firmware update to disable the automatic download and click on download updates. Reboot the device and it will appear. I always do that !!!
Click to expand...
Click to collapse
Of all the instructions i have read.
This one is the best and working answer.
Thank you so much for your idea
1. Disable auto date/time.
2. I set my date 1 or 2 previous months ago.
3. In developer options, I disabled auto system update.
4. In Software update menu, I disable auto download update.
5. Lastly, click the "manually download update" ,I received an error but that's okay.
6. Reboot.
Voila i got my OEM Unlock option without waiting for 7 days or so
batuzai04123 said:
Of all the instructions i have read.
This one is the best and working answer.
Thank you so much for your idea
1. Disable auto date/time.
2. I set my date 1 or 2 previous months ago.
3. In developer options, I disabled auto system update.
4. In Software update menu, I disable auto download update.
5. Lastly, click the "manually download update" ,I received an error but that's okay.
6. Reboot.
Voila i got my OEM Unlock option without waiting for 7 days or so
Click to expand...
Click to collapse
Do you know if this method works with Galaxy Note 8, too?
burduli said:
Do you know if this method works with Galaxy Note 8, too?
Click to expand...
Click to collapse
I don't have Note 8 so I can't be sure but there's no harm with the steps I mentioned.
I actually tried to re flash it clean again(for the 2nd time) with Odin, and @altai1963's trick work again.
Why need 7 or more days when you can do this?
Just try it and let others know if it works for Note 8
Goodluck!
batuzai04123 said:
I don't have Note 8 so I can't be sure but there's no harm with the steps I mentioned.
I actually tried to re flash it clean again(for the 2nd time) with Odin, and @altai1963's trick work again.
Why need 7 or more days when you can do this?
Just try it and let others know if it works for Note 8
Goodluck!
Click to expand...
Click to collapse
I don't own Note 8. I needed it for the article, it will be published on the XDA portal in a couple of minutes.
Does not work for me. Every time I reboot it shows todays date and no OEM unlock.
I go to "date and time" and set to 6 weeks ago, press done.
Disable auto update time.
Disable Auto update system
Disable download updates automatically
press download manually, get error "couldn`t download update"
reboot, and time goes back to today.
What am I doing wrong.
dogsfoot said:
Does not work for me. Every time I reboot it shows todays date and no OEM unlock.
I go to "date and time" and set to 6 weeks ago, press done.
Disable auto update time.
Disable Auto update system
Disable download updates automatically
press download manually, get error "couldn`t download update"
reboot, and time goes back to today.
What am I doing wrong.
Click to expand...
Click to collapse
You just need to make sure your date doesnt revert to current date time after you reboot.
Can you try turning off the sim slot? or airplane mode(then turn wifi on)so that wifi is the only wireless connection u have.
I believe mobile data/sim network auto. adjusts ur time. Let me know if this works
batuzai04123 said:
You just need to make sure your date doesnt revert to current date time after you reboot.
Can you try turning off the sim slot? or airplane mode(then turn wifi on)so that wifi is the only wireless connection u have.
I believe mobile data/sim network auto. adjusts ur time. Let me know if this works
Click to expand...
Click to collapse
Nope, same issue. Airplane mode, no sim,
could be that i have june update installed ???
I can set time forward and it stays set but going back always reverts to 26th june for some reason. not even todays date.
edit: ok, think i`ve solved it. I re-flashed stock firmware on Monday as I had "only official binaries" error, could that be why I cant go back further than a couple of days? It`s the only thing i can think of why I have this problem.
dogsfoot said:
Nope, same issue. Airplane mode, no sim,
could be that i have june update installed ???
I can set time forward and it stays set but going back always reverts to 26th june for some reason. not even todays date.
edit: ok, think i`ve solved it. I re-flashed stock firmware on Monday as I had "only official binaries" error, could that be why I cant go back further than a couple of days? It`s the only thing i can think of why I have this problem.
Click to expand...
Click to collapse
Same thing happenig to me...doesn't matter if i even turn the wifi off and take out the sim card, after reboot it shows the current date.
Any confirmation whatsoever on the Note 8? Have people seriously been so scared off by the OEM Unlock issue that no-one has bought a new one recently, lol???
dogsfoot said:
Does not work for me. Every time I reboot it shows todays date and no OEM unlock.
I go to "date and time" and set to 6 weeks ago, press done.
Disable auto update time.
Disable Auto update system
Disable download updates automatically
press download manually, get error "couldn`t download update"
reboot, and time goes back to today.
What am I doing wrong.
Click to expand...
Click to collapse
dogsfoot said:
Nope, same issue. Airplane mode, no sim,
could be that i have june update installed ???
I can set time forward and it stays set but going back always reverts to 26th june for some reason. not even todays date.
edit: ok, think i`ve solved it. I re-flashed stock firmware on Monday as I had "only official binaries" error, could that be why I cant go back further than a couple of days? It`s the only thing i can think of why I have this problem.
Click to expand...
Click to collapse
Sorry I cant help u with that where DATE & TIME is not sticking after reboot.
Im not sure whats the real cause but for me, the steps / bypass for OEM Unlock option is still working to me until now.
My device is SM-G950FD Dual XTC CRED build
sign into your google account (Must do)
and sign into your Samsung account
1)- change phone date manually back 10 days
2) go to settings - software update and check for update. You should receive errors messages sometime. Don't worry. Just ignore it.
3)- restart phone. After that go to settings -checking software update (when it says your phone is up to date) immediately go to Developer Options and you should see OEM Unlock appear back. You may need to try checking software update few times to get it work.
I tried that 2 days ago and it worked
So updated to latest CRG1 firmware hoping that would bring back OEM unlock function. Well it`s been over 3 weeks since update and still no OEM unlock option available.
Has this feature gone ???? It`s bootloader 3.
proven way 4 the oem unlock to reappear:
1. remove the sim card, factory reset
2. on setup screen, log in wifi, skip gmail, skip samsung account, skip the additional apps, set the time back 1 month (twice, because s8 will try to correct the time immediately)
3. untick automatically update, then check for update manually. then restart
4. sim card still out, phone self correct time, check for update manually again, then restart.
5. sim card still out, turn on developer mode, go on developer mode, wait 5 seconds n oem unlock is there.
immortel_la said:
proven way 4 the oem unlock to reappear:
1. remove the sim card, factory reset
2. on setup screen, log in wifi, skip gmail, skip samsung account, skip the additional apps, set the time back 1 month (twice, because s8 will try to correct the time immediately)
3. untick automatically update, then check for update manually. then restart
4. sim card still out, phone self correct time, check for update manually again, then restart.
5. sim card still out, turn on developer mode, go on developer mode, wait 5 seconds n oem unlock is there.
Click to expand...
Click to collapse
On CRG1, will try this out
Update: Nope, didnt work.
Soapy! said:
On CRG1, will try this out
Update: Nope, didnt work.
Click to expand...
Click to collapse
sometimes u need to repeat the whole process twice - 5 times T_T
immortel_la said:
sometimes u need to repeat the whole process twice - 5 times T_T
Click to expand...
Click to collapse
Same doesnt work for me without a sim in and on wifi
G950FXXU2CRED
Any luck?
The toggle to enable OEM unlocking under developer options is completely missing, and nothing seems to make a difference.
The widely-shared workaround involving changing the date didn't work.
Waiting seven whole days didn't work.
Is 168 hours uptime with no reboots necessary?
Is a Google account necessary?
Is a Samsung account necessary?
Could someone please just explain the exact set of conditions necessary to enable this option?
try connecting to wifi
SiliconValleyPondScum said:
The toggle to enable OEM unlocking under developer options is completely missing, and nothing seems to make a difference.
The widely-shared workaround involving changing the date didn't work.
Waiting seven whole days didn't work.
Is 168 hours uptime with no reboots necessary?
Is a Google account necessary?
Is a Samsung account necessary?
Could someone please just explain the exact set of conditions necessary to enable this option?
Click to expand...
Click to collapse
I would like to find the answer, I am with this problem in a galaxy xcover pro that I need to root to use development apps, no method worked for me and even worse it was automatically updated to Android 11, I have even less hope that it will work
Is this an LTE variant?
-SpaceCowboy- said:
I would like to find the answer, I am with this problem in a galaxy xcover pro that I need to root to use development apps, no method worked for me and even worse it was automatically updated to Android 11, I have even less hope that it will work
Click to expand...
Click to collapse
I also have Samsung Galaxy Xcover Pro (SM-G715FN) with Android 11. On my phone the `OEM Unlocking` option appeared after using phone for 7 days and I successfully rooted the phone. I had Google account, Samsung account and automatic software updates enabled, but I don't know if it was neccesary.
d5sword said:
I also have Samsung Galaxy Xcover Pro (SM-G715FN) with Android 11. On my phone the `OEM Unlocking` option appeared after using phone for 7 days and I successfully rooted the phone. I had Google account, Samsung account and automatic software updates enabled, but I don't know if it was neccesary.
Click to expand...
Click to collapse
thank you, i trie and coment you
The following worked for me:
1. Factory reset
2. During tablet setup:
a. connect to wifi
b. Sign in to Google and Samsung accounts
3. turn on developer mode
4. the OEM Unlock option appears!
I did not have to reset the tablet date/time.
Can I get someone with a Tab S6 to confirm the above?
---
Edit:
Here's the relevant software info:
One UI Version: 3.1
Android Version: 11
Kernel Version: 4.14.190-21627332-abT860XXS3CUG1
Build Number: RP1A.200720.012.T860XXS3CUG1
-SpaceCowboy- said:
I would like to find the answer, I am with this problem in a galaxy xcover pro that I need to root to use development apps, no method worked for me and even worse it was automatically updated to Android 11, I have even less hope that it will work
Click to expand...
Click to collapse
TLDR: Just enable Wifi.
I bring you the answer today
I'm with a XCover Pro running Android 12 already (G715FNXXUADVG4). Before connecting the device to the internet, I absolutely wanted to prevent any further updates, as I'm going to use some variant of the xposed framework and higher Android versions make things more complicated.
So I disabled automatic Updates in the developer options (and everywhere else I could find anything update-related).
I even removed almost every app, including update apps, using this debloat script: https://github.com/khlam/debloat-samsung-android .
I have no Samsung account nor Google account.
The option to unlock the bootloader was still missing.
I changed the date from 2022 to 2023 (for some reason it was a couple of months off). I restartet the phone.
Still no option to unlock OEM.
The device told me there were updates available now (for whatever reason). There is not even a sim card inserted, yet.
Then I enabled wifi. Couldn't tell if any updates happened, didn't notice anything going on.
And then the magic happened ...
"Unlock OEM" appeared INSTANTLY in the developers menu, just after the device connected to wifi / internet.
That's it.