Database Users

Error 0000 (Processing Failed) Stuck on Samsung Account Screen

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

Stock SM-N9005 Restarting 4-5 times a day - need some advice

Hi,
I have been having a ongoing problem with my Galaxy Note 3 N9005 in where after the 5.0 upgrade (stock over air) it has been restarting pretty much 4-5 times during the day, and a number of times while even just sitting on the desk doing nothing.
Since I am still on contract with my supplier in NZ, I took the phone back to get repaired, in which Samsung sent it back to state "Software corruption, reloaded software".
I didn't believe them, but hoped it was correct - but sure enough the same thing happened. So I once again took it back, where they have once again told me the same thing. It is now the third time I have done this, with Samsung saying the same thing!
Now I am at wits end, and have asked for replacement, but I am being told "It is due to your google account being corrupt, and it is causing software corruption....." *sigh*
So now not only is Samsung just not helping, they are blaming my Google accounts for causing the issue. Which btw - I didn't setup the last time, and still it restarted - but they are ignoring that fact!
Anyway - the advice I want to get is has anyone else had the same issue with the Galaxy Note 3 after upgrading? I know there is no way to rollback 5.0 to old version, but did anyone fix the issue by Root and then adding another ROM (I don't want to root this phone, but to be honest I also can't afford right now to replace so I am looking at options)
Right now I am facing a ongoing battle with Samsung and my provider to replace the phone, but they are fighting it a lot and to be honest I have lost my patience so I am thinking to just drop them, root/flash new Rom, and then go to another provider - and probably never buy Samsung again when I can finally upgrade.
(used to love Samsung products but this behavior I have had is certainly making me think twice before I touch them again)

Since they refuse to accept warranty you can try to flash twrp. Then clear everthing(system/caches). Then back to stock with odin. There might be leftover of corrupted files that could cause reboot.
But later they have a better reason not to accept your phone, knox tripped.
And you can actually downgrade to 4.4.2. Just flash firmware of the same csc to be safe.
Sent from my SM-N920C

Do you have memory card installed? if so then scan you memory card for possible viruses.

Actually I have this issue too before.
Even if I left it lying on the table, it can restart by itself.
I tried to update to latest PB1 rom, the update failed, the phone restart while ODIN updating.
So I use Kies recovery and got it working again.
After that, i tried again update to PB1 rom using ODIN. and now no issues at all.
I dont know which one did the trick whether update to PB1 or KIES recovery.
Goldendawn said:
Hi,
I have been having a ongoing problem with my Galaxy Note 3 N9005 in where after the 5.0 upgrade (stock over air) it has been restarting pretty much 4-5 times during the day, and a number of times while even just sitting on the desk doing nothing.
Since I am still on contract with my supplier in NZ, I took the phone back to get repaired, in which Samsung sent it back to state "Software corruption, reloaded software".
I didn't believe them, but hoped it was correct - but sure enough the same thing happened. So I once again took it back, where they have once again told me the same thing. It is now the third time I have done this, with Samsung saying the same thing!
Now I am at wits end, and have asked for replacement, but I am being told "It is due to your google account being corrupt, and it is causing software corruption....." *sigh*
So now not only is Samsung just not helping, they are blaming my Google accounts for causing the issue. Which btw - I didn't setup the last time, and still it restarted - but they are ignoring that fact!
Anyway - the advice I want to get is has anyone else had the same issue with the Galaxy Note 3 after upgrading? I know there is no way to rollback 5.0 to old version, but did anyone fix the issue by Root and then adding another ROM (I don't want to root this phone, but to be honest I also can't afford right now to replace so I am looking at options)
Right now I am facing a ongoing battle with Samsung and my provider to replace the phone, but they are fighting it a lot and to be honest I have lost my patience so I am thinking to just drop them, root/flash new Rom, and then go to another provider - and probably never buy Samsung again when I can finally upgrade.
(used to love Samsung products but this behavior I have had is certainly making me think twice before I touch them again)
Click to expand...
Click to collapse

Munawar Mehmood said:
Do you have memory card installed? if so then scan you memory card for possible viruses.
Click to expand...
Click to collapse
Thanks - but no I don't - these are the first things I did when it started happening.
When it started happening I did factory reset, removing memory card, factory reset again, didn't restore backup from google... etc etc - so the general admin tech stuff.
Because under warranty (2 year contract) I didn't want to do anything more so sent to provider to get dealt with (into my 22 months of 24 months). For the last 4 months it has been to them a number of times for the same thing.
Now each time they send it back they claim "software corrupt" and that there is no hardware issue. So doing a software root and mod change for me is a hope - and probably not a good one - that the Stock 5.0 is the problem on this phone. And only going down this road because I am coming out of the warranty and right now I have a phone I can't really use, and damn Samsung won't support it or fix it (which is really all I want them to do!!) sigh

syamsoul said:
Actually I have this issue too before.
So I use Kies recovery and got it working again.
Click to expand...
Click to collapse
Thanks for this information, because in fact you are not the first time I have read this but I am not sure what the Kies recovery is - is there some instructions you have because maybe that is what should try, because I have seen other people on Google state this has helped them with restarting, but that was usually after Mod fix. Maybe there is something in the 5.0 update on GN3 that might cause this?

Rosli59564 said:
Since they refuse to accept warranty you can try to flash twrp. Then clear everthing(system/caches). Then back to stock with odin. There might be leftover of corrupted files that could cause reboot.
But later they have a better reason not to accept your phone, knox tripped.
And you can actually downgrade to 4.4.2. Just flash firmware of the same csc to be safe.
Sent from my SM-N920C
Click to expand...
Click to collapse
Thanks I didn't think from what I was reading that you could backwards - in fact Samsung have just down right refused, which is all I have asked them to do in the last two times - "Just flash back to the version that was on there last 4.4.2. because that didn't cause any issues!" However, they are stating very firmly that you can not rollback or re-flash back to a previous version.
Is there any instructions which are for the 9005? I have seen for the 900 but the instructions state very clearly you can't use them for 9005.

Goldendawn said:
Thanks I didn't think from what I was reading that you could backwards - in fact Samsung have just down right refused, which is all I have asked them to do in the last two times - "Just flash back to the version that was on there last 4.4.2. because that didn't cause any issues!" However, they are stating very firmly that you can not rollback or re-flash back to a previous version.
Is there any instructions which are for the 9005? I have seen for the 900 but the instructions state very clearly you can't use them for 9005.
Click to expand...
Click to collapse
Just flash the firmware with odin. Factory reset in recovery after it's done. That's it. There are a lots of threads about going down such this:
http://forum.xda-developers.com/gal...o-downgrade-lollipop-to-kitkat-t2990262/page2
I suggest you read through before you go further. They are mixed results. Some successful. Some did not. That is why it is better to flash the same csc firmware.
I even able to downgrade my S6 from 6.01 to 5.1.1 without issue but of course it's different phone.
Sent from my SM-N920C
---------- Post added at 08:38 PM ---------- Previous post was at 08:15 PM ----------
I sent you a PM.
Sent from my SM-N920C

Warning KingoRoot causes DM Verification failure, Kingroot seem to be Okay

II don't want to be an alarmist but back on 17th June 2016 I created this thread DM Verification failure , Please flash ENG binary then install DNK
At the time I wasn't sure what had caused the problem but last night with a different phone I used KingoRoot and it corrupted a second phone of mine. Now two out of three of my Verizon Note 4's have the dm-verification-failure.
The symptoms of the problem are when I am navigating some of the swipes lag. Sometimes when typing there is a lag delay before it is entered. Sometimes Wifi lags before it is turned on and the phone forgets my wifi password.
I found this thread How to solve dm-verity verification failed/need to check drk first on samsung devices but I don't have the experience to do it. Can a developer create the fix for the Verizon Note 4 , PLEASE, Thanks

doctor-cool said:
II don't want to be an alarmist but back on 17th June 2016 I created this thread DM Verification failure , Please flash ENG binary then install DNK
Now two out of three of my Verizon Note 4's have the dm-verification-failure.
Click to expand...
Click to collapse
I am at the end of consolidating all the info I can to determine if I should get a Note 4. Root is the thing that matters to me, but I have learned that regardless of 4.4.4 or 5.1.1 you have to unlock the bootloader which is the challenge.
Just as I think I have it all together and that the methods provided (on XDA only) are the only only ones available and apparently stable, I read this.
Am I COMPLETELY MISUNDERSTANDING your post? Is your post from here http://forum.xda-developers.com/not...bilized-process-to-unlock-bootloader-t3375527 which I've saved as reference for rooting a device no longer accurate?
I'm overwhelmed from so much research and think I've curated the posts that matter, then I see this. Can you offer anything on this? Again, I may not be understanding. I am NOT a developer or programmer. I've rooted a few devices, but it has been a long time with the most recent not requiring the seeming complication of this one (thanks a lot, Verizon!).

jecilop said:
I am at the end of consolidating all the info I can to determine if I should get a Note 4. Root is the thing that matters to me, but I have learned that regardless of 4.4.4 or 5.1.1 you have to unlock the bootloader which is the challenge.
Just as I think I have it all together and that the methods provided (on XDA only) are the only only ones available and apparently stable, I read this.
Am I COMPLETELY MISUNDERSTANDING your post? Is your post from here http://forum.xda-developers.com/not...bilized-process-to-unlock-bootloader-t3375527 which I've saved as reference for rooting a device no longer accurate?
I'm overwhelmed from so much research and think I've curated the posts that matter, then I see this. Can you offer anything on this? Again, I may not be understanding. I am NOT a developer or programmer. I've rooted a few devices, but it has been a long time with the most recent not requiring the seeming complication of this one (thanks a lot, Verizon!).
Click to expand...
Click to collapse
The stabilized-process-to-unlock-bootloader I posted is still valid. I recommended using Kingroot. I found the dm-verity problem with KingORoot. We need more feedback to be sure. I never had the problem with Kingroot. I removed the link to KingORoot from my guide today.

doctor-cool said:
The stabilized-process-to-unlock-bootloader I posted is still valid. I recommended using Kingroot. I found the dm-verity problem with KingORoot. We need more feedback to be sure. I never had the problem with Kingroot. I removed the link to KingORoot from my guide today.
Click to expand...
Click to collapse
Hmmm..ok..thanks for the reply.
That's interesting as I've read so many posts that say KingRoot is not the way to go but rather KingOroot is the correct on to use. Specifically, a lot of people seemed to have tried it unsuccessfully in the process.
I was also hoping to avoid KR as I've read it is a bit sketchy. I've used it twice before doing that and found a Nextbook tablet it worked great on with seemingly no apparent problems since. Another Samsung phone was rooted with it (I was actually searching for KOR, but didn't remember the name exactly and ended up with KR on a search). Unfortunately, the security pop-up keeps coming up trying to remove it. The user who didn't know what they were doing inadvertently gave it the OK to remove it, and now I haven't been able to re-root with it...arrggh..
I recently thought to install their Purify app (which they push when doing KingRoot) separately, but the permissions in the app say that you give it the ability to analyze the content on the screen in an window...I can't figure how THAT is needed to block startup programs or background one to save battery!
So, I was hoping this meant the KOR was good to go with the process after the bootloader is unlocked and stable per your post. I wonder if anyone else is running into problems. I know this is all very new still.
I don't suppose you could tell me:
1) Is permaroot available (with these new methods) only on 5.1.1 , or is it also available on 4.4.4 ? I haven't been able to decipher that.
I kind of prefer KitKat over the material design changes that are just wasting space on my screen in JellyBean. The Note 4 I got to purchased recently (unfortunately, it was a sketchy phone now being returned), had notifications on constant screen overflow because they waste SO MUCH SPACE with them and with unnecessary notifications that I cannot stop from showing (Power Saving, Wif connected, Blocking on). I know a good bit of that is Samsung, but the non-compact use of the notifications is Android ( Google's changes). It was better on my SG3 with 4.4.4 even though they still has persistent notifications.
I'm hoping to root and find a mod to stop showing those. I'm aware enough to check my connections via the settings when needed.
Thanks Again.

jecilop said:
Hmmm..ok..thanks for the reply.
That's interesting as I've read so many posts that say KingRoot is not the way to go but rather KingOroot is the correct on to use. Specifically, a lot of people seemed to have tried it unsuccessfully in the process.
I was also hoping to avoid KR as I've read it is a bit sketchy. I've used it twice before doing that and found a Nextbook tablet it worked great on with seemingly no apparent problems since. Another Samsung phone was rooted with it (I was actually searching for KOR, but didn't remember the name exactly and ended up with KR on a search). Unfortunately, the security pop-up keeps coming up trying to remove it. The user who didn't know what they were doing inadvertently gave it the OK to remove it, and now I haven't been able to re-root with it...arrggh..
I recently thought to install their Purify app (which they push when doing KingRoot) separately, but the permissions in the app say that you give it the ability to analyze the content on the screen in an window...I can't figure how THAT is needed to block startup programs or background one to save battery!
So, I was hoping this meant the KOR was good to go with the process after the bootloader is unlocked and stable per your post. I wonder if anyone else is running into problems. I know this is all very new still.
I don't suppose you could tell me:
1) Is permaroot available (with these new methods) only on 5.1.1 , or is it also available on 4.4.4 ? I haven't been able to decipher that.
I kind of prefer KitKat over the material design changes that are just wasting space on my screen in JellyBean. The Note 4 I got to purchased recently (unfortunately, it was a sketchy phone now being returned), had notifications on constant screen overflow because they waste SO MUCH SPACE with them and with unnecessary notifications that I cannot stop from showing (Power Saving, Wif connected, Blocking on). I know a good bit of that is Samsung, but the non-compact use of the notifications is Android ( Google's changes). It was better on my SG3 with 4.4.4 even though they still has persistent notifications.
I'm hoping to root and find a mod to stop showing those. I'm aware enough to check my connections via the settings when needed.
Thanks Again.
Click to expand...
Click to collapse
I can only report my findings. We need more feedback.

The only real negative I've noticed with KingRoot is that it's erased the serial numbers from both of the phones I've used it on. Thankfully it didn't affect the IMEI, but whenever I try to check the serial number on those two devices, it just shows a bunch of zeros. Back up your EFS partition first (if you can without being rooted, I'm not sure), or at least make a note of the serial number. You can manually edit /efs/FactoryApp/serial_no to restore your serial number as long as you know what it is. I don't believe the serial number is used for anything (except maybe warranty-related things), just annoys me that KingRoot erased it.
As far as removing KingRoot, after you unlock the bootloader you can flash a modified stock firmware file for the phone (one that has had aboot.mbn removed) and still retain an unlocked bootloader. Flashing anything with an aboot.mbn will re-lock your bootloader, so be sure you remove that from any Odin tars before flashing. I had access to the full factory firmware for the device (containing the PIT file and a couple of other partitions not found in the home firmware files hosted by sites like SamMobile) so I stripped aboot.mbn from it and flashed that to make sure I started with a clean, KingRoot free device.

blindmanpb said:
The only real negative I've noticed with KingRoot is that it's erased the serial numbers from both of the phones I've used it on. Thankfully it didn't affect the IMEI, but whenever I try to check the serial number on those two devices, it just shows a bunch of zeros. Back up your EFS partition first (if you can without being rooted, I'm not sure), or at least make a note of the serial number. You can manually edit /efs/FactoryApp/serial_no to restore your serial number as long as you know what it is. I don't believe the serial number is used for anything (except maybe warranty-related things), just annoys me that KingRoot erased it.
As far as removing KingRoot, after you unlock the bootloader you can flash a modified stock firmware file for the phone (one that has had aboot.mbn removed) and still retain an unlocked bootloader. Flashing anything with an aboot.mbn will re-lock your bootloader, so be sure you remove that from any Odin tars before flashing. I had access to the full factory firmware for the device (containing the PIT file and a couple of other partitions not found in the home firmware files hosted by sites like SamMobile) so I stripped aboot.mbn from it and flashed that to make sure I started with a clean, KingRoot free device.
Click to expand...
Click to collapse
Thanks, I like the way you think.
Is there some file I can take from a good working Note 4 and repair the DM verification issue ? Do you think I could do it with efs Profestional. Just wondering.

I initially used KingRoot, and it failed 20 out of 20 times to root my phone. I used KingOroot on my laptop (in a VM) and it rooted my phone first try. I don't have any Wifi issues and I don't see any "DM Verity" messages anywhere on my phone.

raduque said:
I initially used KingRoot, and it failed 20 out of 20 times to root my phone. I used KingOroot on my laptop (in a VM) and it rooted my phone first try. I don't have any Wifi issues and I don't see any "DM Verity" messages anywhere on my phone.
Click to expand...
Click to collapse
I think, You would only see the DM Verity" messages when you are in stock recovery. Once you log into your google account, it remembers your passwords. But on my phoneS, I still get the other lagging problems. What ROM are you on?

blindmanpb said:
The only real negative I've noticed with KingRoot is that it's erased the serial numbers from both of the phones I've used it on. Thankfully it didn't affect the IMEI, but whenever I try to check the serial number on those two devices, it just shows a bunch of zeros. Back up your EFS partition first (if you can without being rooted, I'm not sure), or at least make a note of the serial number. You can manually edit /efs/FactoryApp/serial_no to restore your serial number as long as you know what it is. I don't believe the serial number is used for anything (except maybe warranty-related things), just annoys me that KingRoot erased it.
As far as removing KingRoot, after you unlock the bootloader you can flash a modified stock firmware file for the phone (one that has had aboot.mbn removed) and still retain an unlocked bootloader. Flashing anything with an aboot.mbn will re-lock your bootloader, so be sure you remove that from any Odin tars before flashing. I had access to the full factory firmware for the device (containing the PIT file and a couple of other partitions not found in the home firmware files hosted by sites like SamMobile) so I stripped aboot.mbn from it and flashed that to make sure I started with a clean, KingRoot free device.
Click to expand...
Click to collapse
That why I kept the original box with the serial numbers on it lpl
Sent from my SM-N910V using Tapatalk

raduque said:
I initially used KingRoot, and it failed 20 out of 20 times to root my phone. I used KingOroot on my laptop (in a VM) and it rooted my phone first try. I don't have any Wifi issues and I don't see any "DM Verity" messages anywhere on my phone.
Click to expand...
Click to collapse
Same here, only I used the Kingoroot APK, no issues on either the retail or DE. On JasmineROM (6.0 on the DE and 7.0 on the retail)

fz798 said:
Same here, only I used the Kingoroot APK, no issues on either the retail or DE. On JasmineROM (6.0 on the DE and 7.0 on the retail)
Click to expand...
Click to collapse
The lag is most apparent on stock rom that I rooted with KingOroot apk. On CyanogenMod it is more like a hesitation. The damage is so far as I know irreversible.
The other phone that has only been rooted with KingRoot is a a factory DE it does not have the DM Verification issue and it runs as smooth as silk on every ROM I have tried. So I say the problemS came from KingOroot. But we need more data points/ feedback to be sure.

pfcland said:
That why I kept the original box with the serial numbers on it lpl
Sent from my SM-N910V using Tapatalk
Click to expand...
Click to collapse
Verizon Note 4 does not list serial number on the box, unfortunately.

Can you post a short video detailing the issues and is there something I can do to immediately verify if there is a dm verification problem with my device? I also used Kingoroot on my Note 4 due to KingRoot not working after several tries, but I don't notice anything out of the ordinary, just the usual ocassional lag that is on every Android device.
Only noticeable issues I've experienced have been the "Unauthorized Actions Detected" issue and Wifi passwords not saving using PaulPizz 6.0.1/OscarKernel, but that was corrected with the freezing of a couple Samsung security apps and a build.prop edit.

NeoandGeo said:
Can you post a short video detailing the issues and is there something I can do to immediately verify if there is a dm verification problem with my device? I also used Kingoroot on my Note 4 due to KingRoot not working after several tries, but I don't notice anything out of the ordinary, just the usual ocassional lag that is on every Android device.
Only noticeable issues I've experienced have been the "Unauthorized Actions Detected" issue and Wifi passwords not saving using PaulPizz 6.0.1/OscarKernel, but that was corrected with the freezing of a couple Samsung security apps and a build.prop edit.
Click to expand...
Click to collapse
I'm working this now FIx DRK/dm-verity, Factory CSC and Serial Number So far I have been able to restore my serial#. after I turned on the hidden menu.You have to be in stock recovery to see the dm-verity verification failed message. You would have to Odin back to stock to see it.
Lag is not normal unless you have a ton of apps running. ., Wifi passwords not saving is not normal not even once , I bet you got the bug.

Maybe, but I don't have the wifi passwords issue unless I flash OacarKernel over either Jasmine or Paulpizz, stock kernels are OK in that regard.
How bad of a lag are we talking about? Slight hesitation or full on freezes for more than a second at a time?
After a few weeks of using the device with custom ROMs, no lag spikes have been out of the ordinary for me, feels more responsive than my Note 3 and noticeably better than both the Nexus 6/Moto X I've previously used.
The only truly frustrating lag spikes I've noticed are trying to use this site without any form of adblock on Chrome.

NeoandGeo said:
Maybe, but I don't have the wifi passwords issue unless I flash OacarKernel over either Jasmine or Paulpizz, stock kernels are OK in that regard.
How bad of a lag are we talking about? Slight hesitation or full on freezes for more than a second at a time?
After a few weeks of using the device with custom ROMs, no lag spikes have been out of the ordinary for me, feels more responsive than my Note 3 and noticeably better than both the Nexus 6/Moto X I've previously used.
The only truly frustrating lag spikes I've noticed are trying to use this site without any form of adblock on Chrome.
Click to expand...
Click to collapse
The Best example is scrolling lagging on this site with Chrome. My phone without the issue is as smooth as silk. No hesitation. The phones with the bug maybe two swipes work then the third swipe lags then the page jumps to catch up. It is uncomfortable to use.

XDA forums have been fine for me in Chrome since I installed an ad blocker not too long ago. Before that I would get annoying pauses and skips, like you're talking about. Though this also happened on my Note 3/Moto X/Nexus 6 as well on this site.
Is there any way to see if any running processes have large latency spikes when these lags/pauses occur?
Also is there another kernel I can try on PP 6.0.1 ROM or a way to easily flash the stock kernel on it without restoring a backup? Seems like the minor issue with Wifi only crops up with OscarKernel.

doctor-cool said:
I'm working this now FIx DRK/dm-verity, Factory CSC and Serial Number So far I have been able to restore my serial#. after I turned on the hidden menu.You have to be in stock recovery to see the dm-verity verification failed message. You would have to Odin back to stock to see it.
Lag in not normal unless you have a ton of apps running. ., Wifi passwords not saving is not normal not even once , I bet you got the bug.
Click to expand...
Click to collapse
Verizon devices do not have the typical Samsung serial number. The only serial number your device uses in the last 32 bits of your eMMC CID. The EFS serial number is supposed to be 00000000, and will not affect any functionality of your device. You had your DRK (Device Root Key) erased. It could have been from damage to the EFS partition or something else benign. You'll want to flash complete stock Odin, reboot to recovery and wipe data, and reboot. This should fix your issue, but if it doesn't, let me know and we'll cross that bridge.
In response to OscarKernel not saving WiFi passwords, it's an issue related to ROMs and not my kernel. It does not use secure_storage, so setting ro.secure_storage=false is necessary, and once done, everything will go back to normal and save fine.

ryanbg said:
Verizon devices do not have the typical Samsung serial number. The only serial number your device uses in the last 32 bits of your eMMC CID. The EFS serial number is supposed to be 00000000, and will not affect any functionality of your device. You had your DRK (Device Root Key) erased. It could have been from damage to the EFS partition or something else benign. You'll want to flash complete stock Odin, reboot to recovery and wipe data, and reboot. This should fix your issue, but if it doesn't, let me know and we'll cross that bridge.
Click to expand...
Click to collapse
The tutorial I was following was for the SM-N910C not the SM-N910V . For that device, magix01 has a tutorial to fix DRK. I was working on the premise that if I could repair the serial number, I could then use emergency software recovery. Thanks for straightening me out about the serial number. Put that aside for now.
I did Odin N910VVRU2BPA1_N910VVZW2BPA1_N910VVRU2BPA1_HOME.tar several times downloaded directly from SamMobile and did the data wipe and rebooted every way possible I think. I still get the dm-verity failure and more importantly, It still has the lag bug. I have in my possession another SM-N910V that does not have any issues. I was wondering if I could take a file from the good phone and use it to fix the defective phone. Thanks, for your help, I am ready to cross that bridge.

Samsung Galaxy Sky J3 SM-S320VL TracFone not flashing....

Here is the issue. A friend of mine had gone a bought a Galaxy Sky SM-S320VL from TracPhone. And had been using the phone without any problems until a couple of weeks ago. Then he decided to do a Factory Reset. Instead of doing the software reset, from with in Settings, he went and did a HARD Reset without unlocking the google account. And guess what, he can't remember the account information for that phone. And came to me to reset the phone. (As I had to deal with this problem in the past with other people and their phones.)
I have downloaded the only stock rom I can find for this phone and flashed it with Odin3. But for some reason the flashing of the rom is never done. By this I mean, the phone downloads the rom as Odin sends it. Odin reports a Success with the flashing. But, when the phone reboots. The system has not been reset and FRP is still active.
I have flashed only the AP, and the phone reboots directly into setup and shows a message about an unauthorized Factory Reset.
I have flash all 4 files in the ROM set (BL, AP, CP, and CSC). and Odin states the flash was a success. The phone reboots, goes to recovery and states Starting System Update. Goes so far into the update, then stops and shows Erasing. After a short time of showing Erasing it reboots to setup. Where again the phone shows the message about authorized Factory Reset.
I have used Odin3 v3.9.0, v3.11.1, v3.11.2, v3.12.5. And I have updated to the latest USB drivers from Samsung.
So my question is this. Has anyone had come across this behavior before? And how can I get past this?
The phones particulars:
Name: Samsung Galaxy Sky
Model #: SM-S320VL(GP)
OS v: 6.0.1
Firmware #: S320VLUDU2APJ3
Model #, as reported by Downloader: SM-S320VL
Note: As a strange side effect of when I flash all 4 rom files. For some reason once the phone has failed the system update, erased and has reboot. I have complete access to the phones User data area from within my computer. But, I am unable to access the phone with adb.

Hey folks,
I'm having the exact same issue as the OP. Odin does a successful install on the phone but I get the unauthorized reset message and then Wifi does not work when prompted on the next screen.
Is there a tracfone version of the rom or a fix that anyone here knows of? Thanks!

@drasnah
I have yet to get any kind of reply from anyone on this. Either now one knows, and is not stating so, or doesn't care.

I have seen the wi- fi fix in another thread.
Modify /system/build.prop:
ro.securestorage.support=true to false
Hope that helps!

20eyes said:
I have seen the wi- fi fix in another thread.
Modify /system/build.prop:
ro.securestorage.support=true to false
Hope that helps!
Click to expand...
Click to collapse
First this is not a wi-fi problem it is a re-flashing of the rom problem.
Second, I do not have access, root or otherwise, to any of the system files on the phone.
Third, with the first two in mind this possible solution is of no help.
Fourth, Re-read my original post. I have given complete detailed information as to what I have access to and what I have done.

Can someone send me a download think for this phone i downloaded one but it won't flash it keeps failing

This device has been locked down by Tradphone and Samsung. It gives errors flashing even the correct stock firmware. It's a piece of garbage. NEVER buy anything from Tracphone. Garbage company. You'll never fix this issue. Only pushed updates will flash via software from sammy and tracphone that is built into the rom..

Curtis1973 said:
This device has been locked down by Tradphone and Samsung. It gives errors flashing even the correct stock firmware. It's a piece of garbage. NEVER buy anything from Tracphone. Garbage company. You'll never fix this issue. Only pushed updates will flash via software from sammy and tracphone that is built into the rom..
Click to expand...
Click to collapse
Not sure if that's correct? It depends on the firmware and odin version being used.
---------- Post added at 10:00 PM ---------- Previous post was at 09:58 PM ----------
Nate1k904 said:
Can someone send me a download think for this phone i downloaded one but it won't flash it keeps failing
Click to expand...
Click to collapse
Post more details on the error, screenshots, firmware and odin version used.

Need to know if works. Or if needing to settle for a different route.
The_WABBIT said:
Here is the issue. A friend of mine had gone a bought a Galaxy Sky SM-S320VL from TracPhone. And had been using the phone without any problems until a couple of weeks ago. Then he decided to do a Factory Reset. Instead of doing the software reset, from with in Settings, he went and did a HARD Reset without unlocking the google account. And guess what, he can't remember the account information for that phone. And came to me to reset the phone. (As I had to deal with this problem in the past with other people and their phones.)
I have downloaded the only stock rom I can find for this phone and flashed it with Odin3. But for some reason the flashing of the rom is never done. By this I mean, the phone downloads the rom as Odin sends it. Odin reports a Success with the flashing. But, when the phone reboots. The system has not been reset and FRP is still active.
I have flashed only the AP, and the phone reboots directly into setup and shows a message about an unauthorized Factory Reset.
I have flash all 4 files in the ROM set (BL, AP, CP, and CSC). and Odin states the flash was a success. The phone reboots, goes to recovery and states Starting System Update. Goes so far into the update, then stops and shows Erasing. After a short time of showing Erasing it reboots to setup. Where again the phone shows the message about authorized Factory Reset.
I have used Odin3 v3.9.0, v3.11.1, v3.11.2, v3.12.5. And I have updated to the latest USB drivers from Samsung.
So my question is this. Has anyone had come across this behavior before? And how can I get past this?
The phones particulars:
Name: Samsung Galaxy Sky
Model #: SM-S320VL(GP)
OS v: 6.0.1
Firmware #: S320VLUDU2APJ3
Model #, as reported by Downloader: SM-S320VL
Note: As a strange side effect of when I flash all 4 rom files. For some reason once the phone has failed the system update, erased and has reboot. I have complete access to the phones User data area from within my computer. But, I am unable to access the phone with adb.
Click to expand...
Click to collapse
J3 sm s320vl... tracfone root availability? Just bought phone hopefully got a good one to root? Or maybe someone knows who maybe be able to... please help

No updates? Interested, I have the same phone.

There is no solution for this phone. It will forever be a Trac-phone.
Yes, it nice to imagine what could had been. If there was a fix for the locked bootloader. Its encrypted, and is highly unlikely to be broken by anyone.
Do not flash the boot.image that some people have suggested
Although that method works on some devices such as the AT&T Samsung Galaxy S5. In this case flashing the boot.image from an unlocked device does nothing but places the phone into an even more precarious situation, that makes it unusable even as a Trac phone.
While its true that this very low budget phone could had been decent with a custom Rom ,
You will not be able to get it working.
I have one that belonged to my daughter a couple of years ago and I managed to get it boot into the system again.
Its only function is as a calculator, or preschool game, the cellular reception and Wifi connections are highly unstable and will not stay connected.
Now it serves as my nieces play toy. I would donate to some poor person at the Salvation Army it if it was useable.
By the way, for anyone reading this.
If you have an old phone that is useable. You could dramatically help a Homeless people, by gifting them with a phone especially, if it has some minutes on it.
This gift will help them schedule job interviews, doctors appointments , etc and you will feel good knowing that you helped someone in need.
I have done this before, and will be dropping off a Blu phone, and Kindle Tablet this week.

tsongming said:
There is no solution for this phone. It will forever be a Trac-phone..
Click to expand...
Click to collapse
It is possible to gain root on this device.

ashyx said:
It is possible to gain root on this device.
Click to expand...
Click to collapse
I have permissible SE Status but can not achieve root on this device. Also, I have not found that anyone has had success rooting this exact model.
To be clear my device is the 2016 TracFone Samsung Galaxy J3 Sky model : SM-S320VL
Build S320VUDU1APG2
Hardware Version S320 VL04
I have found reports of people with S320VLUDU2API3 stating that the were able to achieve root and then assumed that it must also be possible with S320VUDU1APG2.
I am usually the guy that can figure these things out, very often before others. But I have had no success gaining root on this device using published methods. Also, I have not seen one example of someone with this identical device who gained root.
You are apparently the Wizard of these Samsung phones, so if you know of a definite way to root it, please point me towards the solution. I would really appreciate it.
I would love to root this phone, get it working again, and gift it to lady who was beaten by her husband and she is now living in a homeless shelter with her two children. She could use a phone to help with her job search. She would appreciate it.
At the moment this phone can will not keep a signal and I can't attempt the build prop solution without root.
Thank you.

tsongming said:
I have permissible SE Status but can not achieve root on this device. Also, I have not found that anyone has had success rooting this exact model.
To be clear my device is the 2016 TracFone Samsung Galaxy J3 Sky model : SM-S320VL
Build S320VUDU1APG2
Hardware Version S320 VL04
I have found reports of people with S320VLUDU2API3 stating that the were able to achieve root and then assumed that it must also be possible with S320VUDU1APG2.
I am usually the guy that can figure these things out, very often before others. But I have had no success gaining root on this device using published methods. Also, I have not seen one example of someone with this identical device who gained root.
You are apparently the Wizard of these Samsung phones, so if you know of a definite way to root it, please point me towards the solution. I would really appreciate it.
I would love to root this phone, get it working again, and gift it to lady who was beaten by her husband and she is now living in a homeless shelter with her two children. She could use a phone to help with her job search. She would appreciate it.
At the moment this phone can will not keep a signal and I can't attempt the build prop solution without root.
Thank you.
Click to expand...
Click to collapse
See the thread below. Root was gained, albeit temporary. However I believe this is due to kernel panics which may be solved by a few build.prop edits. We had to do the same on the J327T1.
https://forum.xda-developers.com/galaxy-j3-2016/help/samsung-galaxy-j3-sm-s320vl-rooted-t3561762
Also if you firmware S320VUDU1APG2 then why not just update it to the firmware that has been reported to work?

I have found one these phones left on a table of a food truck area, screen was cracked - the device was only getting the android guy with triangle on it, I done some research and found the stock rom and flashed it with odin; as some have mentioned in comments above I also experienced wifi issue, so I thought I had installed incorrect rom - downloaded a different one this was a combination file that was the factory repair rom used for testing the device, but wifi worked - it wasn't a fully working telephone it didnt have the app store, well it really didnt have any apps, but I found I could copy over apk files from my PC to the device and then install them, so the phones not completely useless or junk --- it could be used for something. I myself am using that device as a security camera using IP CAM app works great. I was actually using this device for quiet some time as my roku tv remote, because my actual roku remote grown legs and walked off... i havent tried this, but I am sure you could install a launcher apk such as "apex launcher"
well i wasted enough of your time today...

Rooting an sm-n910t WITHOUT a factory reset

(SOLVED)
Hi,
Ive been searching around all week now trying to find a way to do the above, root my note 4 without a factory reset.
As far as i can gather, my bootloader is unlocked.
I suspect it has had somekind of non-t-mobile standard wizardry performed upon it prior to my ownership (2nd hand). The reason i think this (naive?) is as i understand it, these, in the UK, were locked to t-mobile sims new, however, mine can use any sim. also, since my ownership (couple years +), maybe 3 or 4 times it has randomly rebooted and gone into some kind of anti-"fiddling" mode stating something along the lines of "this phone has none genuine blah blah and is now locked. take it into a t-mobile shop to get fixed". A simple battery pull has "fixed" the issue each and every time.
Now, the actual main reason i want to root this, apart from the obvious other advantages, is to be able to perform a complete backup (including all the backup locked out apps). i have a few apps ive paid for, but have since been pulled from the play store, thus, should this phone die, i have no way of restoring them.
it seems that, the only way to backup these apps is to root the phone. i can only find ways in which to root my phone that involve a factory reset. hence im stuck in a catch 22.
According to posts i've read, fastboot doesn't work with my phone. I have been reticent to actually follow through with any method which may reset/factory wipe my phone (as, if i understand it correctly, changing the bootloader/recovery will?).
even though i have found apk's for some of these apps, they are only for the trial versions, and not what i have previously paid for. furthermore, some of these companies have either gone bust, or simply refuse to respond to my emails. losing their cache i can live with, losing the full apps i "can't".
i use a laptop with arch installed. i have occassional access to a windows10 pc.
please please tell me it is possible to root this phone without losing these apps. Or at the very least, a way of pulling/backing up these apps.
ive not found a browser that can see into the data\app folder. adb can see into the data\app folder and pull apps, but not the apps i want to backup which have been pulled from the play store that ive paid for.
phone details:
model sm-n910t
android 6.0.1
baseband n910tuvu2eqi2
kernel 3.10.40 - 9385989
[email protected]#1
build no mmb29m.n910tuvu2eqi2

Hrafnblod said:
Hi,
Ive been searching around all week now trying to find a way to do the above, root my note 4 without a factory reset.
As far as i can gather, my bootloader is unlocked.
I suspect it has had somekind of non-t-mobile standard wizardry performed upon it prior to my ownership (2nd hand). The reason i think this (naive?) is as i understand it, these, in the UK, were locked to t-mobile sims new, however, mine can use any sim. also, since my ownership (couple years +), maybe 3 or 4 times it has randomly rebooted and gone into some kind of anti-"fiddling" mode stating something along the lines of "this phone has none genuine blah blah and is now locked. take it into a t-mobile shop to get fixed". A simple battery pull has "fixed" the issue each and every time.
Now, the actual main reason i want to root this, apart from the obvious other advantages, is to be able to perform a complete backup (including all the backup locked out apps). i have a few apps ive paid for, but have since been pulled from the play store, thus, should this phone die, i have no way of restoring them.
it seems that, the only way to backup these apps is to root the phone. i can only find ways in which to root my phone that involve a factory reset. hence im stuck in a catch 22.
According to posts i've read, fastboot doesn't work with my phone. I have been reticent to actually follow through with any method which may reset/factory wipe my phone (as, if i understand it correctly, changing the bootloader/recovery will?).
even though i have found apk's for some of these apps, they are only for the trial versions, and not what i have previously paid for. furthermore, some of these companies have either gone bust, or simply refuse to respond to my emails. losing their cache i can live with, losing the full apps i "can't".
i use a laptop with arch installed. i have occassional access to a windows10 pc.
please please tell me it is possible to root this phone without losing these apps. Or at the very least, a way of pulling/backing up these apps.
ive not found a browser that can see into the data\app folder. adb can see into the data\app folder and pull apps, but not the apps i want to backup which have been pulled from the play store that ive paid for.
phone details:
model sm-n910t
android 6.0.1
baseband n910tuvu2eqi2
kernel 3.10.40 - 9385989
[email protected]#1
build no mmb29m.n910tuvu2eqi2
Click to expand...
Click to collapse
Have you tried Odin? Samsung phones don't use fastboot but have their own flashing tool.

QuoPrimum said:
Have you tried Odin? Samsung phones don't use fastboot but have their own flashing tool.
Click to expand...
Click to collapse
I'm now rooted, cheers
I used ODIN on windows and CF_Auto Root.
I was just incredibly worried about getting a phone wipe/reset. I think, with having read through so many different guides and discussions, and having first tried to find a linux only solution, I'd ended up confusing myself. It just seemed that, when I thought I understood the process enough to actually physically start the rooting, all I could see was boot loop, bricking and factory reset issues in the guides.
Awesome forum.

Any apps you buy on the play store don't just disappear.
Check your actual purchase list for your Google account, it'll force a cached page.
Which is how I found out Activision pushed a (paid) mobile version of Zombies, removed it, then pushed the same game to the market which they continued to update.