I bought the international version from Amazon and got it today. I turned it on and it worked fine, about 4 minutes in to me going through the setup screen, the screen went all pixelated with a white bar through the screen. I pulled the battery and restarted, then an update popped up, I then went ahead and installed it. It completed, booted up and I signed into evertthing. About 10 minutes later it froze, so I pulled the battery again, and went to restart and now it just boot loops.
Is the device rooted? If so, you could try installing a custom rom assuming doing so doesn't void your warranty.
Sent from my GT-N7000 using Tapatalk
Sounds dodgy. I wouldn't bother flashing custom Rom or rooting a device so clearly faulty. Return it and get a working unit.
Sent from my GT-N7000 using XDA App
forsakenwicked said:
Is the device rooted? If so, you could try installing a custom rom assuming doing so doesn't void your warranty.
Sent from my GT-N7000 using Tapatalk
Click to expand...
Click to collapse
Nope, this is my initial turning on of the device so it isn't rooted yet.
newg said:
Sounds dodgy. I wouldn't bother flashing custom Rom or rooting a device so clearly faulty. Return it and get a working unit.
Sent from my GT-N7000 using XDA App
Click to expand...
Click to collapse
I figured it was, but I wanted to make sure it wasn't just some error that the phone gave before the recent update. I'll be returning it and maybe I'll get the AT&T version. Thanks a lot.
forsakenwicked said:
Is the device rooted? If so, you could try installing a custom rom assuming doing so doesn't void your warranty.
Sent from my GT-N7000 using Tapatalk
Click to expand...
Click to collapse
Did you actually read the post?
---------- Post added at 12:18 AM ---------- Previous post was at 12:17 AM ----------
Dacian said:
I bought the international version from Amazon and got it today. I turned it on and it worked fine, about 4 minutes in to me going through the setup screen, the screen went all pixelated with a white bar through the screen. I pulled the battery and restarted, then an update popped up, I then went ahead and installed it. It completed, booted up and I signed into evertthing. About 10 minutes later it froze, so I pulled the battery again, and went to restart and now it just boot loops.
Click to expand...
Click to collapse
Return it immediately!
I purchased the AT&T version of the Galaxy Note 3 a little less than a week ago and, to be honest, I'm not really keen on it. There are a number of reasons, but what it boils down to is that I just don't think I like it all that much. I've already sold my Galaxy Note 2, so I'll have to figure out what I'm going to do about a cell phone, but that's something beyond the scope of this particular posting. What I need help with is how to unroot this device. I used the Root De La Vega procedure very shortly after it came out and it worked like a charm. I noted that when the phone boots up, there is the word "Custom" and an unlocked padlock. How do I get this AT&T model of the Galaxy Note 3 back to the condition, more or less, of when I bought it about a week ago so that I won't have any issues getting the refund processed? I've heard some people requesting help with unrooting and they've been told to use the unroot in SuperUser. Will this get rid of the "Custom" wording on boot-up AND the unlocked padlock? If not, is there a way to get this back to the way it was or am I just out of luck since I only have about another week to return this device. Obviously, if I'm stuck, I'm stuck and I'll find a way to live with it. Who knows...I might actually get to liking it down the road when some of the quirks have been worked out. However, if there's a way to sort all of this out in a timely manner where there's no muss or fuss, that would be the ideal solution. Any help would be greatly appreciated.
KennyXL said:
I purchased the AT&T version of the Galaxy Note 3 a little less than a week ago and, to be honest, I'm not really keen on it. There are a number of reasons, but what it boils down to is that I just don't think I like it all that much. I've already sold my Galaxy Note 2, so I'll have to figure out what I'm going to do about a cell phone, but that's something beyond the scope of this particular posting. What I need help with is how to unroot this device. I used the Root De La Vega procedure very shortly after it came out and it worked like a charm. I noted that when the phone boots up, there is the word "Custom" and an unlocked padlock. How do I get this AT&T model of the Galaxy Note 3 back to the condition, more or less, of when I bought it about a week ago so that I won't have any issues getting the refund processed? I've heard some people requesting help with unrooting and they've been told to use the unroot in SuperUser. Will this get rid of the "Custom" wording on boot-up AND the unlocked padlock? If not, is there a way to get this back to the way it was or am I just out of luck since I only have about another week to return this device. Obviously, if I'm stuck, I'm stuck and I'll find a way to live with it. Who knows...I might actually get to liking it down the road when some of the quirks have been worked out. However, if there's a way to sort all of this out in a timely manner where there's no muss or fuss, that would be the ideal solution. Any help would be greatly appreciated.
Click to expand...
Click to collapse
I'm not super familiar with the unrooting process, but try to unroot using SuperSU and reboot a couple of times to see if it goes away. If that doesn't work then flash the original firmware with odin and that should do it. Pretty easy to do from what I understand.
agent929 said:
I'm not super familiar with the unrooting process, but try to unroot using SuperSU and reboot a couple of times to see if it goes away. If that doesn't work then flash the original firmware with odin and that should do it. Pretty easy to do from what I understand.
Click to expand...
Click to collapse
Perhaps this is showing my ignorance, but since the AT&T Galaxy Note 3 has a locked bootloader (which, as of yet, has not been unlocked), would that prevent Odin from flashing a new image? If I don't need an unlocked bootloader to flash with Odin, do you know where I might find the original image that came with my phone from AT&T in a format that Odin can flash? I haven't tried the SuperSU yet since I want all my options readily available so that if one fails, I can move on to the next one.
KennyXL said:
Perhaps this is showing my ignorance, but since the AT&T Galaxy Note 3 has a locked bootloader (which, as of yet, has not been unlocked), would that prevent Odin from flashing a new image? If I don't need an unlocked bootloader to flash with Odin, do you know where I might find the original image that came with my phone from AT&T in a format that Odin can flash? I haven't tried the SuperSU yet since I want all my options readily available so that if one fails, I can move on to the next one.
Click to expand...
Click to collapse
To my understanding you can flash anything with Odin on a locked bootloader phone that is "signed". If you give me a few minutes I'll help you look for the original odin file to flash.
agent929 said:
I'm not super familiar with the unrooting process, but try to unroot using SuperSU and reboot a couple of times to see if it goes away. If that doesn't work then flash the original firmware with odin and that should do it. Pretty easy to do from what I understand.
Click to expand...
Click to collapse
agent929 said:
To my understanding you can flash anything with Odin on a locked bootloader phone that is "signed". If you give me a few minutes I'll help you look for the original odin file to flash.
Click to expand...
Click to collapse
I really appreciate your help. Every time I've used Odin in the past has involved a phone with a non-locked bootloader (as far as I know) so this is new territory for me.
KennyXL said:
I really appreciate your help. Every time I've used Odin in the past has involved a phone with a non-locked bootloader (as far as I know) so this is new territory for me.
Click to expand...
Click to collapse
Not a problem. I've been looking for that odin file with no luck. I would PM designgears and ask him if he can provide a link for it because you couldn't find it.
agent929 said:
Not a problem. I've been looking for that odin file with no luck. I would PM designgears and ask him if he can provide a link for it because you couldn't find it.
Click to expand...
Click to collapse
Thanks. I'll give that a try.
Use the same file that u used to root. The one with the one click. After it pass, you're back to stock. i just did it yesterday.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
If you looked at the root thread you'd see directions to unroot right there.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
panday74 said:
Use the same file that u used to root. The one with the one click. After it pass, you're back to stock. i just did it yesterday.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Zach Alt said:
If you looked at the root thread you'd see directions to unroot right there.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Click to expand...
Click to collapse
What they said
Sent from my SAMSUNG-SGH-I467 using Tapatalk 4
panday74 said:
Use the same file that u used to root. The one with the one click. After it pass, you're back to stock. i just did it yesterday.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I tried the SuperSU full unroot method - didn't remove the padlock, flashed the one click - didn't remove it, and just flashed the second (for funsies) and that didn't help (probably shouldn't have expected it to).
I'm returning my note and can't get rid of the lock. Will PM Designgears I guess
Did you restart it a few times? Also a factory reset?
Sent from my SAMSUNG-SM-N900A using Tapatalk 5
seanu13 said:
I tried the SuperSU full unroot method - didn't remove the padlock, flashed the one click - didn't remove it, and just flashed the second (for funsies) and that didn't help (probably shouldn't have expected it to).
I'm returning my note and can't get rid of the lock. Will PM Designgears I guess
Click to expand...
Click to collapse
I was kinda wondering how to remove the padlock also. I have read that some people that haven't even rooted have the padlock on boot up also??? I read somewhere about triangle away working, have you tried that?
agent929 said:
Did you restart it a few times? Also a factory reset?
Sent from my SAMSUNG-SM-N900A using Tapatalk 5
Click to expand...
Click to collapse
yes to both (restarted 5 times). since i was already so far into the root process, I added the files to the sdcards that are in the root steps, and the lock went away. Then I finished rooting.
went back and did one click again and still had the lock after rebooting 5 times. Thought about how it went away after adding the files so I skipped through the phone setup, enabled USB debugging again and added a dummy file to the sd card (a .csv I had on my desktop) and then removed it. Rebooted, and the lock was gone.
I'd use the padlock hack in Wanum and hide the root apps via Nova Launcher just to stick it to ATT and return it rooted.
Sent from my SAMSUNG-SM-N900A using xda premium
Omg, just reflash the stock rom from the package. Says so in the instructions.
READ!
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Jammol said:
Omg, just reflash the stock rom from the package. Says so in the instructions.
READ!
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
If you READ, you will see he already did that.
agent929 said:
If you READ, you will see he already did that.
Click to expand...
Click to collapse
The last post that was here when I posted was yours. That's why I posted for him to Read the instructions.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Ok well here's what I did and the padlock is gone.
Factory reset on the phone
Phone rebooted and I removed the super su app using the setting in the su app.
Then flashed the one click 9 tar
phone reboots on its own after flashing, icon was still there
rebooted the phone twice and the padlock was gone
Not sure if I just got lucky or what lol
Jammol said:
The last post that was here when I posted was yours. That's why I posted for him to Read the instructions.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Got ya..tapatalk has been mean to me too lol
---------- Post added at 10:26 AM ---------- Previous post was at 10:25 AM ----------
Quickvic30 said:
Ok well here's what I did and the padlock is gone.
Factory reset on the phone
Phone rebooted and I removed the super su app using the setting in the su app.
Then flashed the one click 9 tar
phone reboots on its own after flashing, icon was still there
rebooted the phone twice and the padlock was gone
Not sure if I just got lucky or what lol
Click to expand...
Click to collapse
I know you have to reboot a few times to set the status somehow, iB4STiD explained it in one of his post before.
So I have note3 I rooted with lingo everything was food good. Then I loaded safestrap and now I'm stuck at the samsung boot screen with the unlocked custom pad lock logo.
How do I get back to a working bootable phone and remove the padlock icon? I found this post but don't know if I'm on mj5 or not?
http://forum.xda-developers.com/showthread.php?t=2559715
[12/29] Restore for MJ5 --Doesn't trip Knox and optionally provides root--
Sent from my Nexus 7 using XDA Premium 4 mobile app
Need more info..are you just trying to get rid of padlock or is phone stuck on thst screen? If so did you try battery pull or booting into recovery via power button + home+volume up
Sent from my SM-N900A using Tapatalk
You don't need to be on MJ5 to restore to it.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Both. I have the padlock and it stays on the Samsung screen. At this point I just what to get back to a stock state and clear any of the tamper flags
Sent from my Nexus 5 using xda premium
I had a similar problem yesterday. I accidentally deleted my os without replacing it cuz im a noob. I was stuck on the boot screen with the padlock.
I went into panic mode and upgraded to kitkat. It worked, but I wanted root, and safestrap. So I followed the method that you linked, and it successfully restored me to 4.3 with root access.
In short, it will work, but it will wipe your phone. And it didn't trip knox for me.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Sireniankyle is right. I wiped my stock rom in safestrap..used this method with no issues..now im back up and running safestrap installed running Megas FireNote. Just follow the steps do not diviate from them
Sent from my SM-N900A using Tapatalk
I am trying to get my device back to as close to stock as possible. I have played with Root and Wanam Exposed.
I had a weird issue with force closes and could not figure it out so I wiped the device using the factory reset option. Even after that I have FC's with the health app. (no biggie there). The odd thing is that I still have the "CUSTOM" logo on the boot screen that I cant seem to get rid of.
I did a quick search on a bone stock ROM for NC2 KK but have come up empty.
I am currently looking at the Download Screen "ODIN MODE" and the Current Binary is "Samsung Official" System Status "Official" Knox Lock reads 0x0, so I have not tripped knox either.
Kinda baffled here and I seem to be coming up empty handed on all my searches.
Any one got any ideas?
Hoyt Thompson said:
I am trying to get my device back to as close to stock as possible. I have played with Root and Wanam Exposed.
I had a weird issue with force closes and could not figure it out so I wiped the device using the factory reset option. Even after that I have FC's with the health app. (no biggie there). The odd thing is that I still have the "CUSTOM" logo on the boot screen that I cant seem to get rid of.
I did a quick search on a bone stock ROM for NC2 KK but have come up empty.
I am currently looking at the Download Screen "ODIN MODE" and the Current Binary is "Samsung Official" System Status "Official" Knox Lock reads 0x0, so I have not tripped knox either.
Kinda baffled here and I seem to be coming up empty handed on all my searches.
Any one got any ideas?
Click to expand...
Click to collapse
You're on nc2? Pls post your about device info so we can help out.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
posersk8r said:
You're on nc2? Pls post your about device info so we can help out.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Not sure what all you need posted....
It is a 900a AT&T Note 3 running KK 4.4.2 NC2 rom.
Rooted via towel root
Tweaked a bit using Exposed Framework and Wanam.
Also jave the latest Safestrap for making nandroids.
HAVE NOT tried to do a custom ROM yet.
What else would you like?
Hoyt Thompson said:
Not sure what all you need posted....
It is a 900a AT&T Note 3 running KK 4.4.2 NC2 rom.
Rooted via towel root
Tweaked a bit using Exposed Framework and Wanam.
Also jave the latest Safestrap for making nandroids.
HAVE NOT tried to do a custom ROM yet.
What else would you like?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=51572014 just in case you f'ed up this will get you back to official nc2. Check out the thread man. As for now I would uninstall all my root apps, delete them then full unroot with supersu so you wouldnt see that custom boot anymore( takes a couple of reboots)
Sent from my GT-I9300 using XDA Premium 4 mobile app
posersk8r said:
http://forum.xda-developers.com/showthread.php?p=51572014 just in case you f'ed up this will get you back to official nc2. Check out the thread man. As for now I would uninstall all my root apps, delete them then full unroot with supersu so you wouldnt see that custom boot anymore( takes a couple of reboots)
Sent from my GT-I9300 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yeah I read that but their where a few comments made to to make me think that thos was not for those already on NC2. Maybe I read to much into it?
Thanks for your help.
Hoyt Thompson said:
Yeah I read that but their where a few comments made to to make me think that thos was not for those already on NC2. Maybe I read to much into it?
Thanks for your help.
Click to expand...
Click to collapse
The op warned those who are still on 4.3 that if they used the ver 3 mlg with the nc2 bootloader they cannot go back to jb. But to those of us who already are locked to nc2 we could recover from a bootloop or restore to factory for warranty purposes or just want to go back to stock. Read up on that carefully very very useful if you like to play with your phone.
Sent from my GT-I9300 using XDA Premium 4 mobile app
Hoyt Thompson said:
I am trying to get my device back to as close to stock as possible. I have played with Root and Wanam Exposed.
I had a weird issue with force closes and could not figure it out so I wiped the device using the factory reset option. Even after that I have FC's with the health app. (no biggie there). The odd thing is that I still have the "CUSTOM" logo on the boot screen that I cant seem to get rid of.
I did a quick search on a bone stock ROM for NC2 KK but have come up empty.
I am currently looking at the Download Screen "ODIN MODE" and the Current Binary is "Samsung Official" System Status "Official" Knox Lock reads 0x0, so I have not tripped knox either.
Kinda baffled here and I seem to be coming up empty handed on all my searches.
Any one got any ideas?
Click to expand...
Click to collapse
Visit my thread fixes for everyone and see if it can help you. I got something for you there
After using the one-click method, the initial boot screen has a new icon of a lock and it says "Custom" above it. Does this mean the knox flag has been tripped or is it nothing to worry about? What part of the rooting process made this appear?
I'm sure it's ok...I think it's talked about in the OP..
Doesn't mean Knox was tripped, just that the checksum of a system folder was modified. Nothing to worry about. It goes away if you Odin back to stock.
Sent from my Galaxy S6 Edge
Ah ok, I renamed the SDM apk so that makes sense. Thanks guys!
32BitWhore said:
Doesn't mean Knox was tripped, just that the checksum of a system folder was modified. Nothing to worry about. It goes away if you Odin back to stock.
Sent from my Galaxy S6 Edge
Click to expand...
Click to collapse
I ODIN'd back to stock and it didn't get rid of it.
Berzerker7 said:
I ODIN'd back to stock and it didn't get rid of it.
Click to expand...
Click to collapse
Once you odin back to stock you have to boot into recovery and factory data reset
Sent from my SM-G925V using Xparent Green Tapatalk 2
2swizzle said:
Once you odin back to stock you have to boot into recovery and factory data reset
Sent from my SM-G925V using Xparent Green Tapatalk 2
Click to expand...
Click to collapse
Did this also and I still have custom on my splash screen...