Develop Bugs

Successful Root - Samsung Galaxy Note 4, Just one drawback...

Hello all,
I was testing and fooling around with my Note 4 SM-910A when I tried rooting my phone again. (Manually) and I did something different giving me root and the bootloader now shows the Custom (unlocked) symbol. Meaning, that I got root and my bootloader was unlocked. Here is some proof:
imgur (DOT) com/2qjJmWs
But there is one catch to it.
You get bricked. AT&T sees that you are rooted and you cannot use your phone unless you restore it to stock or you take it to AT&T store and they will do it for you.
Also you get a : SECURE = FAIL on your scree.
When I got this root, I made an account quickly and then I posted. This is the biggest day for me. I'm gonna try and see if I can bypass the SECURE = FAIL and make it into SECURE = I DON'T EVEN CARE!
--Sarmad Wahab
--Android Rootivist

Hahahahahahahaa
Sent from my SM-N910T using Tapatalk

No kidding
getyroks said:
Hahahahahahahaa
Sent from my SM-N910T using Tapatalk
Click to expand...
Click to collapse
Dude, no kidding this just happened to me like 10 minutes ago. I'll be going to AT&T store, like the phone said. I will see what they do.

If you look into the root progress forum, a couple of us has had the same thing happen. I am hoping that some devs are looking into this. I know how to do this every time now and have to unbrick my phone every time.
Sent from my SAMSUNG-SM-N910A using XDA Free mobile app

http://forum.xda-developers.com/showthread.php?p=65784783
Look into this here.
I have done this more than 10 times trying various root procedures to stick on reboot. I'm sure there are A LOT of other that have had this happen also. It's not new.

What a troll. New user sign up, 1st post said ROOTED. LOL

getyroks said:
Hahahahahahahaa
Sent from my SM-N910T using Tapatalk
Click to expand...
Click to collapse
sweetboy02125 said:
What a troll. New user sign up, 1st post said ROOTED. LOL
Click to expand...
Click to collapse
Bro, not a troll. My note 4 is now permanently bricked. The os was deleted by the bootloader. I took it to Att and they say that it is permanently bricked. Hard-bricked. Gonna send it to samsung or go to another att store to see wut happenes.

No. No. No. Nonononono
I hope you didn't send it in yet.
Go here-> http://forum.xda-developers.com/showthread.php?p=63431559
Download needed files and don't forget about Odin program.
As I stated earlier, I have done this over 10 times trying various root methods to stick. If you weren't so noobish in thinking AT&T was going to help you...maybe you could read around on these awesome forums and figure it out for yourself... but alas, you can lead a horse to water, blah blah blah...

Walt
I had the same thing happen to me. King root app popped & asked me to try again so I did. (Stupid me) I tried everything I know how to fix this.. In recovery mode I told phone to wipe data factory reset. Still pops up after reboot stating kernal is not seaddroid enforcing then says secure fail kernel and had large yellow triangle saying system software not authorized by at&t has been found etc. Turn off and take to at&t store.
Anyone know how to fix this or have I ruined the phone?

getyroks said:
No. No. No. Nonononono
I hope you didn't send it in yet.
Go here-> http://forum.xda-developers.com/showthread.php?p=63431559
Download needed files and don't forget about Odin program.
As I stated earlier, I have done this over 10 times trying various root methods to stick. If you weren't so noobish in thinking AT&T was going to help you...maybe you could read around on these awesome forums and figure it out for yourself... but alas, you can lead a horse to water, blah blah blah...
Click to expand...
Click to collapse
cboysfan said:
I had the same thing happen to me. King root app popped & asked me to try again so I did. (Stupid me) I tried everything I know how to fix this.. In recovery mode I told phone to wipe data factory reset. Still pops up after reboot stating kernal is not seaddroid enforcing then says secure fail kernel and had large yellow triangle saying system software not authorized by at&t has been found etc. Turn off and take to at&t store.
Anyone know how to fix this or have I ruined the phone?
Click to expand...
Click to collapse
use the link @getyroks posted, it unbricked my phone!

---------- Post added at 03:11 PM ---------- Previous post was at 03:08 PM ----------
[/COLOR]
cboysfan said:
I had the same thing happen to me. King root app popped & asked me to try again so I did. (Stupid me) I tried everything I know how to fix this.. In recovery mode I told phone to wipe data factory reset. Still pops up after reboot stating kernal is not seaddroid enforcing then says secure fail kernel and had large yellow triangle saying system software not authorized by at&t has been found etc. Turn off and take to at&t store.
Anyone know how to fix this or have I ruined the phone?
Click to expand...
Click to collapse
Please read the whole thread instead of asking to be spoon-fed, don't be lazy. READ, SEARCH,and RESEARCH!!!
Sent from my SM-N910T using Tapatalk

getyroks said:
No. No. No. Nonononono
I hope you didn't send it in yet.
Go here-> http://forum.xda-developers.com/showthread.php?p=63431559
Download needed files and don't forget about Odin program.
As I stated earlier, I have done this over 10 times trying various root methods to stick. If you weren't so noobish in thinking AT&T was going to help you...maybe you could read around on these awesome forums and figure it out for yourself... but alas, you can lead a horse to water, blah blah blah...
Click to expand...
Click to collapse
Dude thank you soo much, I got my phone fixed, and also I got my note 3 fixed using files from the same person

getyroks said:
---------- Post added at 03:11 PM ---------- Previous post was at 03:08 PM ----------
[/COLOR]
Please read the whole thread instead of asking to be spoon-fed, don't be lazy. READ, SEARCH,and RESEARCH!!!
Sent from my SM-N910T using Tapatalk
Click to expand...
Click to collapse
Wow. Don't be lazy. Not cool dude. I did read the whole post and I am trying what was listed. Anyway I wanted to add that my phone has never been rooted. I have tried Kingroot many times with no success. I am running Lollipop 5.1.1 which is locked by AT&T so I am curious if bootloader is locked how this happened or how I will be able to fix this. I will continue to read as I have been doing prior to being called lazy. I have yet to see anyone else state they were running the same OS I am.

cboysfan said:
Wow. Don't be lazy. Not cool dude. I did read the whole post and I am trying what was listed. Anyway I wanted to add that my phone has never been rooted. I have tried Kingroot many times with no success. [bold]I am running Lollipop 5.1.1 which is locked by AT&T so I am curious if bootloader is locked how this happened [\bold]or how I will be able to fix this. I will continue to read as I have been doing prior to being called lazy. I have yet to see anyone else state they were running the same OS I am.
Click to expand...
Click to collapse
The files mentioned in my previous post are the 5.1.1 OS files. I have used them multiple times to recover from a soft-brick. So, YES, I have the same OS Lollipop as you should have. AT&T has locked the bootloader on the Note 4 from the beginning. But in 4.4.4 you could temp-root in order to get rid of some files. But results are so different from phone to phone that a temp-root scenario is complicated to explain. Some work some dont. KINGROOT is also in the same boat, might or not work. You might be able to keep your phone from rebooting or it might freeze and you HAVE to pull the battery. When the battery gets pulled and reboots SOMETIMES you can reboot to a temp-rooted phone, MOST OF THE TIME it soft bricks. All of this information is in either of the posts I linked earlier, so either you're lazy, or you don't understand what you're reading. If you don't understand, then please READ, SEARCH, and RESEARCH.
Sent from my SM-N910T using Tapatalk
Start at the beginning of this here->----->>>http://forum.xda-developers.com/showthread.php?t=2961974

Thank you getyroks.
I was concerned to load the files because I did not see anyone who was not rooted and running my OS. I installed them and all is well. Thank you again.
getyroks said:
The files mentioned in my previous post are the 5.1.1 OS files. I have used them multiple times to recover from a soft-brick. So, YES, I have the same OS Lollipop as you should have. AT&T has locked the bootloader on the Note 4 from the beginning. But in 4.4.4 you could temp-root in order to get rid of some files. But results are so different from phone to phone that a temp-root scenario is complicated to explain. Some work some dont. KINGROOT is also in the same boat, might or not work. You might be able to keep your phone from rebooting or it might freeze and you HAVE to pull the battery. When the battery gets pulled and reboots SOMETIMES you can reboot to a temp-rooted phone, MOST OF THE TIME it soft bricks. All of this information is in either of the posts I linked earlier, so either you're lazy, or you don't understand what you're reading. If you don't understand, then please READ, SEARCH, and RESEARCH.
Sent from my SM-N910T using Tapatalk
Start at the beginning of this here->----->>>http://forum.xda-developers.com/showthread.php?t=2961974
Click to expand...
Click to collapse

cboysfan said:
Thank you getyroks.
I was concerned to load the files because I did not see anyone who was not rooted and running my OS. I installed them and all is well. Thank you again.
Click to expand...
Click to collapse
The sad part is that it cleans the whole system. So starting from scratch everytime is a drag.
Sent from my SM-N910T using Tapatalk

ejectedmatrix said:
use the link @getyroks posted, it unbricked my phone!
Click to expand...
Click to collapse
It helped me as well. Just download the package and use ODIN and you are back in buisness. Btw, all your personal data is gone bye bye though, I will be like a having a brand new phone again.
Take care.
Sent from my SAMSUNG-SM-T537A using XDA Free mobile app

ejectedmatrix said:
Bro, not a troll. My note 4 is now permanently bricked. The os was deleted by the bootloader. I took it to Att and they say that it is permanently bricked. Hard-bricked. Gonna send it to samsung or go to another att store to see wut happenes.
Click to expand...
Click to collapse
1) Not a troll. Just someone not knowing what they're doing.
2) ATT reps don't even know the difference between a locked sim and locked bootloader, so they wouldn't know the difference between a hard and soft brick.
3) All you had to do was use Odin to fix the phone. You just traded your phone for a factory refurbished one. Good job!
4) Read the latest forum posts before doing things.
Sent from my SAMSUNG-SM-N910A using Tapatalk

Hey guys. Thought I'd chime in with a little insight here. Had someone call me the other day that tried to root one, and ended up with the same unauthorized software error. Couldn't get to download mode, couldn't get to recovery, couldn't get phone to boot. He took it to AT&T, where they of course told him the phone was "hard bricked". I just used a usb jig and restored it with odin. Did just fine.
This is the jig I used. It was $4.92 on eBay
http://www.ebay.com/itm/NEW-Samsung...SB-jig-EXCLUSIVELY-US-MADE-SOLD-/141351359584

strabo231 said:
Hey guys. Thought I'd chime in with a little insight here. Had someone call me the other day that tried to root one, and ended up with the same unauthorized software error. Couldn't get to download mode, couldn't get to recovery, couldn't get phone to boot. He took it to AT&T, where they of course told him the phone was "hard bricked". I just used a usb jig and restored it with odin. Did just fine.
This is the jig I used. It was $4.92 on eBay
You wasted $4.92 on ebay, All you got to do is download USB Driver for your phone and install it on your computer. Once this is done, your computer we recognize your soft bricked phone and you can use Odin to reload the firmware.
Click to expand...
Click to collapse

Device State - locked

I know there are other threads regarding this but those included someone having TWRP already flashed and in this case I do not.
I sadly took a chance and bought a Nexus 5X off someone on Kijiji and it looks like I got got scammed.
I've own other Nexus phones in the past but was unaware of the OEM Lock on the latest devices and it is in a locked state and I do not know the google account to unlock it (as it wasn't my phone prior to this)
None of the fastboot/adb commands work as it is locked.
I just wanted to know if there was any other way I could fix this or if I have brick on my hands here. Any assistance would be amazing as this would mean I just blew my money away.
N

sniperIT said:
I know there are other threads regarding this but those included someone having TWRP already flashed and in this case I do not.
I sadly took a chance and bought a Nexus 5X off someone on Kijiji and it looks like I got got scammed.
I've own other Nexus phones in the past but was unaware of the OEM Lock on the latest devices and it is in a locked state and I do not know the google account to unlock it (as it wasn't my phone prior to this)
None of the fastboot/adb commands work as it is locked.
I just wanted to know if there was any other way I could fix this or if I have brick on my hands here. Any assistance would be amazing as this would mean I just blew my money away.
N
Click to expand...
Click to collapse
So you purchased a 5X that wasn't factory reset? Have you tried asking the previous owner for assistance? They might be able to remotely wipe the phone using Android Device Manager.

metpage said:
So you purchased a 5X that wasn't factory reset? Have you tried asking the previous owner for assistance? They might be able to remotely wipe the phone using Android Device Manager.
Click to expand...
Click to collapse
It was reset and required login of the previous account to unlock it. Unfortunately, the previous owner is nowhere to be found...
The build number is MHC19J and I've been told that I am screwed to unlock it.
Nick

sniperIT said:
It was reset and required login of the previous account to unlock it. Unfortunately, the previous owner is nowhere to be found...
The build number is MHC19J and I've been told that I am screwed to unlock it.
Nick
Click to expand...
Click to collapse
I would try and get your money back, chances are you could have brought a stolen phone.

Darke5tShad0w said:
I would try and get your money back, chances are you could have brought a stolen phone.
Click to expand...
Click to collapse
Sadly you may be right, but like any good thief he seems to be unreachable, so I unfortunately can't get the money back. I have checked the IMEI and it is clean so i should be able to activate it.
I just need a way to bypass the FRP (Factory Reset Protection). I've seen posts on this on XDA but they are for patches up to the March 1st Patch. I build I have is the March Patch and I can't seem to find any workarounds for this patch level.
In the event that someone has found a way please let me know as it would save me a lot of grief.
Thank you for your responses.
N

sniperIT said:
Sadly you may be right, but like any good thief he seems to be unreachable, so I unfortunately can't get the money back. I have checked the IMEI and it is clean so i should be able to activate it.
I just need a way to bypass the FRP (Factory Reset Protection). I've seen posts on this on XDA but they are for patches up to the March 1st Patch. I build I have is the March Patch and I can't seem to find any workarounds for this patch level.
In the event that someone has found a way please let me know as it would save me a lot of grief.
Thank you for your responses.
N
Click to expand...
Click to collapse
I don't know if will help, but the N preview may not include or may reset FRP. Usually OTAs only include the changed files but since the N preview was bricking locked phones, Google released full OTAs that contained everything. You could try flashing it with ADB while in the stock recovery.
Sent from my Nexus 5X using Tapatalk

PiousInquisitor said:
I don't know if will help, but the N preview may not include or may reset FRP. Usually OTAs only include the changed files but since the N preview was bricking locked phones, Google released full OTAs that contained everything. You could try flashing it with ADB while in the stock recovery.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I was thinking the same thing but I don't want to make the situation worse than it already is. I have seen vids from RootJunky showing that the N preview is bypassable and it can be done with a reset.
Will the OTA wipe all the data on the device?
Just to be clear are these the OTA's you are referring too? http://developer.android.com/preview/download-ota.html
Thank you for your advice.
N

sniperIT said:
I was thinking the same thing but I don't want to make the situation worse than it already is. I have seen vids from RootJunky showing that the N preview is bypassable and it can be done with a reset.
Will the OTA wipe all the data on the device?
Just to be clear are these the OTA's you are referring too? http://developer.android.com/preview/download-ota.html
Thank you for your advice.
N
Click to expand...
Click to collapse
Those are the files. That is what I would do.
Sent from my Nexus 5X using Tapatalk

PiousInquisitor said:
Those are the files. That is what I would do.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Ok thank you very much I am in the process, will update once it is complete.
N

sniperIT said:
Ok thank you very much I am in the process, will update once it is complete.
N
Click to expand...
Click to collapse
Looks like it is still a no go. The FRP seems to still be in place and the reset idea didn't work.
I may need to see if i can get this phone completely blanked.
N

sniperIT said:
Looks like it is still a no go. The FRP seems to still be in place and the reset idea didn't work.
I may need to see if i can get this phone completely blanked.
N
Click to expand...
Click to collapse
I've got on last idea. Is it a 32 gig model?
Sent from my Nexus 5X using Tapatalk

PiousInquisitor said:
I've got on last idea. Is it a 32 gig model?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
16GB unfortunately.

sniperIT said:
16GB unfortunately.
Click to expand...
Click to collapse
Bummer. I was going to suggest THIS. But there isnt a 16 TOT file.
So you were able to successfully flash N from the stock recovery? And you simply couldnt get past the login screen? FRP is a *****. I had no idea what it was when I sold my Moto X Pure Edition last year. I ended up giving the guy I sold it to my password so he could unlock it. That was after about a day of searching for a workaround. Then my sis bought a G4 and when it arrived it was locked with FRP. We ended up finding a tool to wipe it out. Such a pain. Lol. Good luck finding a solution. Let us know if you get it working some other way.
---------- Post added at 10:41 PM ---------- Previous post was at 10:30 PM ----------
sniperIT said:
16GB unfortunately.
Click to expand...
Click to collapse
Have you tried this? EDIT: Looks like its been patched already...
https://www.youtube.com/watch?v=ocC7ruFCqOI

PiousInquisitor said:
Bummer. I was going to suggest THIS. But there isnt a 16 TOT file.
So you were able to successfully flash N from the stock recovery? And you simply couldnt get past the login screen? FRP is a *****. I had no idea what it was when I sold my Moto X Pure Edition last year. I ended up giving the guy I sold it to my password so he could unlock it. That was after about a day of searching for a workaround. Then my sis bought a G4 and when it arrived it was locked with FRP. We ended up finding a tool to wipe it out. Such a pain. Lol. Good luck finding a solution. Let us know if you get it working some other way.
---------- Post added at 10:41 PM ---------- Previous post was at 10:30 PM ----------
Have you tried this? EDIT: Looks like its been patched already...
https://www.youtube.com/watch?v=ocC7ruFCqOI
Click to expand...
Click to collapse
Man is it ever. The last thing I was thinking was that they say there is a 72 hour lock on this and I only first started the phone on Sat night. maybe I need to wait until tomorrow and see what happens.
I will check out the Youtube video.
Thank you for all your help once again.
N

sniperIT said:
Man is it ever. The last thing I was thinking was that they say there is a 72 hour lock on this and I only first started the phone on Sat night. maybe I need to wait until tomorrow and see what happens.
I will check out the Youtube video.
Thank you for all your help once again.
N
Click to expand...
Click to collapse
So were you able to reset the phone on N, like in the rootjunky video?
https://www.youtube.com/watch?v=nOymYg3lswI

PiousInquisitor said:
So were you able to reset the phone on N, like in the rootjunky video?
https://www.youtube.com/watch?v=nOymYg3lswI
Click to expand...
Click to collapse
I unfortunately don't have a sim to test with. The one in my current is a micro not a nano. I am going to contact a repair store tomorrow to see if they can assist and I will try it out.
Sorry yes I did exactly as he suggested and it didn't work.
It gives me the option during setup to setup like it was a new phone but then as soon as I connect to my WiFi it performs a check and states the same reset message.
Which is why I might be thinking that it is the 72 hour lock on and maybe it will go away once it is complete.
N

sniperIT said:
I unfortunately don't have a sim to test with. The one in my current is a micro not a nano. I am going to contact a repair store tomorrow to see if they can assist and I will try it out.
Sorry yes I did exactly as he suggested and it didn't work.
It gives me the option during setup to setup like it was a new phone but then as soon as I connect to my WiFi it performs a check and states the same reset message.
Which is why I might be thinking that it is the 72 hour lock on and maybe it will go away once it is complete.
N
Click to expand...
Click to collapse
I would try it again. If you factory reset from within android, it should disable FRP, including the need to wait 72 hrs.
I wouldn't bother with the repair shop. The latest and greatest info is going to be on the internet and probably from rootjunky.

PiousInquisitor said:
I would try it again. If you factory reset from within android, it should disable FRP, including the need to wait 72 hrs.
I wouldn't bother with the repair shop. The latest and greatest info is going to be on the internet and probably from rootjunky.
Click to expand...
Click to collapse
I tried several times with no luck.
It just seems like once it phones home to Google it blocks me.
I'm going to try to contact rootjunky directly

sniperIT said:
I tried several times with no luck.
It just seems like once it phones home to Google it blocks me.
I'm going to try to contact rootjunky directly
Click to expand...
Click to collapse
Bummer. Im out of ideas.

What message do you exactly get when trying to execute something via fastboot?

Bricked Verizon Note 7?

Hey guys, I was trying to gain root on my New Note 7 With this method( http: //androiding.how/root-verizon-note-7-ph3-userdebug-firmware ) I get to the point where i flash the sprint firmware and it fails with Odin and now i cant boot my phone. Trying to figure out if there is a way to fix this or if i'm just screwed.
Comes up with a dead android with an exclamation point above him when i try to boot and I it won't let me do a factory restore.

Check out tje Verizon phone repair desktop app. You put the device in download mode and it resets it. Bricked mine 3 times and that always works

Fixed!
IronCross1788 said:
Check out tje Verizon phone repair desktop app. You put the device in download mode and it resets it. Bricked mine 3 times and that always works
Click to expand...
Click to collapse
Thanks bud, However i was able to repair it by finding the original firmware i had and flashed it with odin and it worked! PHEW! I'll keep this in mind for next time as well! Thanks!

IronCross1788 said:
Check out tje Verizon phone repair desktop app. You put the device in download mode and it resets it. Bricked mine 3 times and that always works
Click to expand...
Click to collapse
Do you have a link to this magical app?

JohnShaft69 said:
Do you have a link to this magical app?
Click to expand...
Click to collapse
I am in class right now but I will be more then than happy to share it in 2 aand a half hours

Same Issue
Hey OP, Im having the same issue you were having. Can you please go into a little more detail on how you fixed it? Thanks.
---------- Post added at 08:28 PM ---------- Previous post was at 08:23 PM ----------
IronCross1788 said:
I am in class right now but I will be more then than happy to share it in 2 aand a half hours
Click to expand...
Click to collapse
IronCross, Im desperate. Please link this magic. please help.......

JohnShaft69 said:
Do you have a link to this magical app?
Click to expand...
Click to collapse
I believe this will leave your phone updated to the latest firmware which means no root. You can always reflash your current version firmware with Odin to repair boot issues. You only have issues when trying to flash down to a previous version. See this post:
http://forum.xda-developers.com/ver...-your-verizon-note-7-and-quick-guide-t3443994
for this file
AP_N930VVRS1APH1_CL8720001_QB10528330_REV00_user_low_ship_MULTI_CER.zip

Repair
IronCross1788 said:
I am in class right now but I will be more then than happy to share it in 2 aand a half hours
Click to expand...
Click to collapse
Is this the one? https://www.verizonwireless.com/support/knowledge-base-80201/#

wayne8821212 said:
Is this the one? https://www.verizonwireless.com/support/knowledge-base-80201/#
Click to expand...
Click to collapse
Yes. Sorry I didnt get a chance to get back to you earlier.

Magical Tool
IronCross1788 said:
Yes. Sorry I didnt get a chance to get back to you earlier.
Click to expand...
Click to collapse
Thanks IronCross! What are you studying? I myself am not bricked yet LOL!.... just preemptively looking around ....in case one or more of my ODIN forays go bad. Still waiting for the AT&T ODIN files for the PHE (Green Battery) update.....test drove the Sprint version...

wayne8821212 said:
Thanks IronCross! What are you studying? I myself am not bricked yet LOL!.... just preemptively looking around ....in case one or more of my ODIN forays go bad. Still waiting for the AT&T ODIN files for the PHE (Green Battery) update.....test drove the Sprint version...
Click to expand...
Click to collapse
No problem buddy. Glad I can sort of help. I'm studying economics currently.. well see what the future holds . Ha

Firmware Downgrade

Is it possible to downgrade to NDE63P from NDE63X? Wanting to root now that TWRP is available...
Bootloader IS still locked...

nozzleman_85 said:
Is it possible to downgrade to NDE63P from NDE63X? Wanting to root now that TWRP is available...
Bootloader IS still locked...
Click to expand...
Click to collapse
Not if you have a locked bootloader

Cozzeck said:
Not if you have a locked bootloader
Click to expand...
Click to collapse
How would I go about doing this, I have a Verizon pixel xl that's unlocked and I am on the X update and would like to revert to P

shibbnasty said:
How would I go about doing this, I have a Verizon pixel xl that's unlocked and I am on the X update and would like to revert to P
Click to expand...
Click to collapse
What's the point of returning to P?
Sent from my Pixel XL using Tapatalk

david.degraw54 said:
What's the point of returning to P?
Click to expand...
Click to collapse
Well I'm trying to fix and issue I'm having with the camera flash, ever since the update it will only flash once and then will not work again with any app no matter what until I do a restart. It worked before the update and nothing happened to the phone so I wanted to see if going back might fix it before I have to get a refurbished one from Verizon.

shibbnasty said:
Well I'm trying to fix and issue I'm having with the camera flash, ever since the update it will only flash once and then will not work again with any app no matter what until I do a restart. It worked before the update and nothing happened to the phone so I wanted to see if going back might fix it before I have to get a refurbished one from Verizon.
Click to expand...
Click to collapse
Well first you need to unlock your bootloader: http://theroot.ninja/depixel8.html
After that, download the P factory image from Google's site and follow instructions to install. Just remember to backup stuff you want (photos, files, anything saved on storage) because unlocking will perform a factory reset.
Sent from my Pixel XL using Tapatalk

david.degraw54 said:
Well first you need to unlock your bootloader: http://theroot.ninja/depixel8.html
After that, download the P factory image from Google's site and follow instructions to install. Just remember to backup stuff you want (photos, files, anything saved on storage) because unlocking will perform a factory reset.
Click to expand...
Click to collapse
Already unlocked and downloaded the images and tried to install as the directions but during the process it says boot.img and recovery.img is missing even though I did exactly what it said.
---------- Post added at 12:59 AM ---------- Previous post was at 12:54 AM ----------
Not really sure what I'm doing wrong at this point and I'm stuck

Did you copy the files into the fastboot and adb program file?
They need to be in there for it to work.

shibbnasty said:
Already unlocked and downloaded the images and tried to install as the directions but during the process it says boot.img and recovery.img is missing even though I did exactly what it said.
---------- Post added at 12:59 AM ---------- Previous post was at 12:54 AM ----------
Not really sure what I'm doing wrong at this point and I'm stuck
Click to expand...
Click to collapse
Your using an outdated ADB and Fastboot (like 99% of the people on this forum).
Here is the latest: https://dl.dropboxusercontent.com/u/31360541/platform-tools-version_1.0.36-API_25.zip

Scott said:
Your using an outdated ADB and Fastboot (like 99% of the people on this forum).
Here is the latest: https://dl.dropboxusercontent.com/u/31360541/platform-tools-version_1.0.36-API_25.zip
Click to expand...
Click to collapse
Thank you, worked after that and I am back to P but unfortunately my flash is still not working correctly. Sucks in passed the 14 day return so I'll get a refurbished when the phone is practically brand new.

shibbnasty said:
Thank you, worked after that and I am back to P but unfortunately my flash is still not working correctly. Sucks in passed the 14 day return so I'll get a refurbished when the phone is practically brand new.
Click to expand...
Click to collapse
There might not be any refurbished phones to send you so you might luck out. Better to try now than later when they have a big stock of returned phones. Or I'm crazy and you'll get one either way...

Jacobk85 said:
There might not be any refurbished phones to send you so you might luck out. Better to try now than later when they have a big stock of returned phones. Or I'm crazy and you'll get one either way...
Click to expand...
Click to collapse
Yea I'm really hoping not to get a refurbished. I'm gonna do my best to see that I get a new one but if not I guess oh well. I have a 32g really blue model so not sure if they even have any new ones.

shibbnasty said:
Yea I'm really hoping not to get a refurbished. I'm gonna do my best to see that I get a new one but if not I guess oh well. I have a 32g really blue model so not sure if they even have any new ones.
Click to expand...
Click to collapse
Thanks for hijacking my thread dude....

nozzleman_85 said:
Thanks for hijacking my thread dude....
Click to expand...
Click to collapse
Sorry man....

shibbnasty said:
Well I'm trying to fix and issue I'm having with the camera flash, ever since the update it will only flash once and then will not work again with any app no matter what until I do a restart. It worked before the update and nothing happened to the phone so I wanted to see if going back might fix it before I have to get a refurbished one from Verizon.
Click to expand...
Click to collapse
Doubt you'd get a refurbished unit at this point, you'd still get one from replacement stock set aside for early issues.

nozzleman_85 said:
Is it possible to downgrade to NDE63P from NDE63X? Wanting to root now that TWRP is available...
Bootloader IS still locked...
Click to expand...
Click to collapse
You will need to unlock your bootloader. Why do you need to downgrade though? You can root and install TWRP on nde63x.

cambunch said:
You will need to unlock your bootloader. Why do you need to downgrade though? You can root and install TWRP on nde63x.
Click to expand...
Click to collapse
I realized that after a little research.. that's my fault..

Do I really have to wait 7 days for OEM unlock to appear?

I just got this S9+ today and I cannot find OEM unlock under Developer Options. I read that the only way is to wait 7 days and then it will appear. Is that true?

Yes as long as it is a Exynos S9, Snapdragon will never appear

Sick of Qualcomms locked bootloaders. I had to deal with this on the S7, S8, and S9. Think I may be finished with the Galaxy.

zzEvilGeniuszz said:
Sick of Qualcomms locked bootloaders. I had to deal with this on the S7, S8, and S9. Think I may be finished with the Galaxy.
Click to expand...
Click to collapse
Buy Exynos instead?

2 things:
1) there absolutely are unlockable Snapdragons. Only the US and Canada have perm locked ones. Don't believe the hype.
2) you might be able to skip ahead on the lock, but it doesn't always work and I think later firmware blocks it. It worked for me once but not the second time. It's a lot more likely to work if you don't have RMM status: Prenormal. Search xda to find out what that means if you don't know.
As for skipping the wait, there was an xda article about it this week or last week, should be easy to find. Also, if you have RMM status: normal (you see nothing about RMM in download mode) you can just flash the combination rom for your device and it's oem unlock it's always there. Doesn't work with Prenormal though

@partcyborg Unfortunately, mine says pre-normal so I am forced to wait the 7 days. I came back to Liverpool two days ago and I had over 60 hours of uptime by then, but as soon as I inserted my Three UK sim card, I got a notification and was basically forced to reboot my device. I tried everything I can to try and dismiss that pop-up but I couldn't. The uptime was reset and now I have 22 hours which is extremely frustrating. Do you think the reboot messed things up or could it actually be counting from the 60+ hours it already had?

There is a thread on the forums that says you can change the date or something like that to "trick" it into thinking you have had it the 7 days... I don't know for sure if it works because I have a US T-mobile version, just figured I'd share what I came across...

TarekElsakka said:
@partcyborg Unfortunately, mine says pre-normal so I am forced to wait the 7 days. I came back to Liverpool two days ago and I had over 60 hours of uptime by then, but as soon as I inserted my Three UK sim card, I got a notification and was basically forced to reboot my device. I tried everything I can to try and dismiss that pop-up but I couldn't. The uptime was reset and now I have 22 hours which is extremely frustrating. Do you think the reboot messed things up or could it actually be counting from the 60+ hours it already had?
Click to expand...
Click to collapse
Rebooting does not reset the 7d counter. All reports of that being a thing are fake news. You are fine

jflow36 said:
There is a thread on the forums that says you can change the date or something like that to "trick" it into thinking you have had it the 7 days... I don't know for sure if it works because I have a US T-mobile version, just figured I'd share what I came across...
Click to expand...
Click to collapse
This worked for me one time but not the second. Definitely worth trying

partcyborg said:
Rebooting does not reset the 7d counter. All reports of that being a thing are fake news. You are fine
Click to expand...
Click to collapse
You were right. Someone on reddit also told me the same thing when I first purchased the phone and although the uptime was reset after I rebooted the device, OEM unlock showed up exactly 7 days later regardless so that was great!

partcyborg said:
2 things:
1) there absolutely are unlockable Snapdragons. Only the US and Canada have perm locked ones. Don't believe the hype.
2) you might be able to skip ahead on the lock, but it doesn't always work and I think later firmware blocks it. It worked for me once but not the second time. It's a lot more likely to work if you don't have RMM status: Prenormal. Search xda to find out what that means if you don't know.
As for skipping the wait, there was an xda article about it this week or last week, should be easy to find. Also, if you have RMM status: normal (you see nothing about RMM in download mode) you can just flash the combination rom for your device and it's oem unlock it's always there. Doesn't work with Prenormal though
Click to expand...
Click to collapse
How Do I can see my status if its normal or prrnormal?

Regikitten said:
How Do I can see my status if its normal or prrnormal?
Click to expand...
Click to collapse
Does oem unlock show up in developer options?

Regikitten said:
How Do I can see my status if its normal or prrnormal?
Click to expand...
Click to collapse
Download mode

partcyborg said:
Does oem unlock show up in developer options?
Click to expand...
Click to collapse
No
---------- Post added at 10:10 AM ---------- Previous post was at 10:08 AM ----------
*Detection* said:
Download mode
Click to expand...
Click to collapse
And if I try to do it How I get out of download mode
Ps: Sorry my English, I'm Brasilian

Regikitten said:
No
---------- Post added at 10:10 AM ---------- Previous post was at 10:08 AM ----------
And if I try to do it How I get out of download mode
Ps: Sorry my English, I'm Brasilian
Click to expand...
Click to collapse
Then it's prenormal

Regikitten said:
No
---------- Post added at 10:10 AM ---------- Previous post was at 10:08 AM ----------
And if I try to do it How I get out of download mode
Ps: Sorry my English, I'm Brasilian
Click to expand...
Click to collapse
Hold volume down & power

partcyborg said:
Rebooting does not reset the 7d counter. All reports of that being a thing are fake news. You are fine
Click to expand...
Click to collapse
@partcyborg, what about SIM card, is that required, or another myth?
Just got a SM-G9600 (TPA/Panama). I don't have any SIM in it, and waiting for 7 days to get out of prenormal. Had to take the August RH4, which must have included BL update as I couldn't odin back to July RF4.
Btw, the date bypass trick didn't work for me, either before the update or afterward. I'm curious how Samsung keeps track of the 7 days. If it's solely on the phone, then the date trick would have worked; they probably moved it to server side somehow (I watched my network traffic when doing the manual update, but should have done it earlier when enabling the dev options).