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
iv been rooted for a good month now, so i just restarted my phone and i tried to reboot it, it showed the Samsung galaxy s7 edge logo and also in very small writing it said custom binary blocked by frp lock? and it just wont boot up?
PistonHeadd said:
iv been rooted for a good month now, so i just restarted my phone and i tried to reboot it, it showed the Samsung galaxy s7 edge logo and also in very small writing it said custom binary blocked by frp lock? and it just wont boot up?
Click to expand...
Click to collapse
Just did the same to me yesterday.
Luckily I had the official firmware already downloaded on my pc so I just Odin to Stock and started over.
Find your firmware on sammobile download it and extract the files then place them in the corresponding slots in Odin.
I was back up and running in about 5 minutes
"And on that bombshell!"
Sent from my Gorgeous Echoe Powered AEL Kernel Driven G935F
s7freak said:
Just did the same to me yesterday.
Luckily I had the official firmware already downloaded on my pc so I just Odin to Stock and started over.
Find your firmware on sammobile download it and extract the files then place them in the corresponding slots in Odin.
I was back up and running in about 5 minutes
"And on that bombshell!"
Sent from my Gorgeous Echoe Powered AEL Kernel Driven G935F
Click to expand...
Click to collapse
thanks man, before i go ahead, will i lost all my data or root? and is there anyway to prevent this from happening again?
PistonHeadd said:
thanks man, before i go ahead, will i lost all my data or root? and is there anyway to prevent this from happening again?
Click to expand...
Click to collapse
You'll be back to fresh stock so yeah you'll lose everything unfortunately and that's the only way to recover from it that I know of.
I couldn't get past the boot screen no matter what I did.
So yep you'll have to root again I'm afraid.
As far as it not happening again I didn't have any lock like a pin or fingerprint security and when the phone was in my pocket no telling what I did. I know I Hutt dialed my son a couple times. When I looked at my phone I saw an update for AdAway and did that and when rebooted that's when I had FRP LOCK GRRRRRR
it was certainly a pain but recoverable
"And on that bombshell!"
Sent from my Gorgeous Echoe Powered AEL Kernel Driven G935F
My FRP method this:
Phone G935A, used Firmware G935U (not AT&T bloatware)
Insert prepaid sim 0$, and 0mb internet, but LTE network...
Personalise phone start, and wifi not turn on. Google verification fail, and NEXT button active...
Personalise finish, and turn dev.opt on, oem unlock on, and add the google account.
[emoji2]
Sent from my SM-G935U using Tapatalk
Hello fellow people of XDA!
Today I got an OTA update for my S7 edge (SM-G935F). The update has installed fairly fast (after the first reboot). But then, it got stuck on a decrypting loop. I have enabled prior the full phone encryption, and set it to ask for a password at each start. I entered the password correctly, as it said Starting Android... after, and since then, only the rotating padlock is showing. Every like 5 minutes the soft buttons are lighting up for a second, but then nothing is happening. After a while it even gets hot, but still nothing. I had this issue at the previous update too, but it started after like 30-40 minutes. Now 90 minutes have passed and still nothing.
I can reboot to the recovery and bootloader screens, and everything is fine. Knox not tripped, not rooted, everything official. In the recovery screen it says that my CSC is ECT (but according to sammobile it should be CNX).
Some additional info: samsung/hero2ltexx/hero2lte
7.0/NRD90M/G935FXXU2DRAG
I will try to flash a stock rom (PDA: G935FXXS2DRAA, CSC: G935FROM1DQJ3). If that doesn't work, I'll flash today's rom (PDA: same, CSC: G935FVFG1DQI1).
Any tips/help would be greately appreciated! Would not want to fall to the wipe data method, because I don't want to lose everything... But then again, I guess that would remove the boot password...
Thanks!
Update: After waiting for like 10+ hours, nothing has changed. Maybe I shouldn't have forced a reboot after an hour of the ota update? Going to try flashing the firmware now.
Update 2: I flashed the firmware, now the buttons seem to light up less often. But after an hour of decrypting, I guess the ultimate soultion would be to do a factory reset, since no one is helping...
jaszfalvi.tamas said:
Hello fellow people of XDA!
Today I got an OTA update for my S7 edge (SM-G935F). The update has installed fairly fast (after the first reboot). But then, it got stuck on a decrypting loop. I have enabled prior the full phone encryption, and set it to ask for a password at each start. I entered the password correctly, as it said Starting Android... after, and since then, only the rotating padlock is showing. Every like 5 minutes the soft buttons are lighting up for a second, but then nothing is happening. After a while it even gets hot, but still nothing. I had this issue at the previous update too, but it started after like 30-40 minutes. Now 90 minutes have passed and still nothing.
I can reboot to the recovery and bootloader screens, and everything is fine. Knox not tripped, not rooted, everything official. In the recovery screen it says that my CSC is ECT (but according to sammobile it should be CNX).
Some additional info: samsung/hero2ltexx/hero2lte
7.0/NRD90M/G935FXXU2DRAG
I will try to flash a stock rom (PDA: G935FXXS2DRAA, CSC: G935FROM1DQJ3). If that doesn't work, I'll flash today's rom (PDA: same, CSC: G935FVFG1DQI1).
Any tips/help would be greately appreciated! Would not want to fall to the wipe data method, because I don't want to lose everything... But then again, I guess that would remove the boot password...
Thanks!
Update: After waiting for like 10+ hours, nothing has changed. Maybe I shouldn't have forced a reboot after an hour of the ota update? Going to try flashing the firmware now.
Update 2: I flashed the firmware, now the buttons seem to light up less often. But after an hour of decrypting, I guess the ultimate soultion would be to do a factory reset, since no one is helping...
Click to expand...
Click to collapse
Wait, i dont get it, it is prompting you for a password even you didnt set it?
Sent from my S7 Edge using XDA Labs
shah22 said:
Wait, i dont get it, it is prompting you for a password even you didnt set it?
Sent from my S7 Edge using XDA Labs
Click to expand...
Click to collapse
I set a password when I enabled Secure Startup.
jaszfalvi.tamas said:
I set a password when I enabled Secure Startup.
Click to expand...
Click to collapse
Then use that same password, i think there is confusion, there is a password when you enable fingerprint and then a password when you enable secure startup. Be sure not to confuse them. If it still happens, then I guess there's got something wrong with the update, and only way is a factory reset. Btw, i also updated and i normally entered secure boot password and it started okay. Don't know what caused this for you.
Sent from my S7 Edge using XDA Labs
shah22 said:
Then use that same password, i think there is confusion, there is a password when you enable fingerprint and then a password when you enable secure startup. Be sure not to remember them. If it still happens, then I guess there got something wrong with the update, and only way is a factory reset. Btw, i also updated and i normally entered secure boot password and it started okay. Don't know what caused this for you.
Sent from my S7 Edge using XDA Labs
Click to expand...
Click to collapse
I entered the password correctly, as it stated "Starting Android..." then the rotating padlock took forever. More than 10 hours even. But in the end, a factory reset helped me. But rip my photos and memories...
Don't use device encryption anymore and leave OEM unlocking enabled in developer options.
Those two settings cause more hassle if you want to keep data, and make backups from time to time using Samsung Smart switch on computer. Use a microSD card to store and take all your photos from camera.
benjamen50 said:
Don't use device encryption anymore and leave OEM unlocking enabled in developer options.
Those two settings cause more hassle if you want to keep data, and make backups from time to time using Samsung Smart switch on computer. Use a microSD card to store and take all your photos from camera.
Click to expand...
Click to collapse
Right, but i use encryption and i could update without any problem, don't know what caused this issue with him. But one should backup all data BEFORE updating, as i did to save yourself from such hassle.
Sent from my S7 Edge using XDA Labs
benjamen50 said:
Don't use device encryption anymore and leave OEM unlocking enabled in developer options.
Those two settings cause more hassle if you want to keep data, and make backups from time to time using Samsung Smart switch on computer. Use a microSD card to store and take all your photos from camera.
Click to expand...
Click to collapse
Yeah, it's a sure thing I won't turn on Secure Stratup anymore. I don't know what OEM unlock does or does not, but right now, I don't have dev options enabled. If I had a microSD then I couldn't care less about resetting my phone, but since I don't have, because I have two SIM cards and a memory card has no place left, I feel bad.
Still, I don't know caused this issue. I had OTA updates before with full device encryption enabled and I had no issues before. I kinda used the same disk space at every OTA, so it should have took the same time... And I have to mention, that I did not tamper with the software. No root, no custom rom, and software only from the play store.
To enable developer options you click Build number 7 times which is located in the Software information tab in settings.
OEM unlock allows you to flash and boot the phone with custom binaries (Custom Recovery, Kernels, Roms). You can leave OEM unlock disabled if you don't want people that may steal your phone and use it for themselves.
With OEM unlock disabled and a google account signed in, it will block anyone from using the phone after a factory reset on stock Samsung firmware as it will prompt the user to enter the google account that was associated with that device.
Unfortunately there are rare cases that a OTA update may fail. Reflashing correct stock firmware usually fixes it but in worse case scenarios a factory reset will be required.
benjamen50 said:
To enable developer options you click Build number 7 times which is located in the Software information tab in settings.
OEM unlock allows you to flash and boot the phone with custom binaries (Custom Recovery, Kernels, Roms). You can leave OEM unlock disabled if you don't want people that may steal your phone and use it for themselves.
With OEM unlock disabled and a google account signed in, it will block anyone from using the phone after a factory reset on stock Samsung firmware as it will prompt the user to enter the google account that was associated with that device.
Unfortunately there are rare cases that a OTA update may fail. Reflashing correct stock firmware usually fixes it but in worse case scenarios a factory reset will be required.
Click to expand...
Click to collapse
Never had OEM unlock enabled, because I didn't know what is does, so thanks for the info. I reflashed the correct stock firmware, but that didn't help either, so I had to resort to wiping the data... Regarding this, do you know by any chance a good software for recovering data without root?
I don't know of any unfortunately, if anyone has any good paid ones that actually work please post here.