Samsung note 3, so messed up it works. - Verizon Galaxy Note 3 General

Ok, to start off I'm going to let you know that I don't know everything about this topic, I know enough to get my self in major trouble but still. With that in mind I start from the beginning, I got my note 3 then decided to root it with like one click root or something, looking back probably should have followed the video and done it right. After I would try to install a rom using safe strap rom slot 1 so I wouldn't lose my stock rom. Dumb me I tried loading cm11 and that's when I think I tripped Knox because after rebooting a custom logo was in the bootloader, I didn't think anything of it at the time. Now we skip ahead a few months to were I went camping with my family and my father's friends who's really good at this stuff had the jasmine rom on his note 3, my reaction was like I want that gimme. So the truth comes out here when he looked at my phone the Knox counter was 0x1 and he said something about a eFuse, after trial and error when I got home I forced the kk firmware through Odin and then flashed jasmine rom on the phone and it worked . So the question is, is my phone a special case or is that supposed to happen, I figured if Knox was tripped you could install any roms. What do you guys think?

Tripping Knox just breaks your warranty. So that's actually bad. It doesn't unlock the bootloader which is what allows any rom to be installed or more specifically any kernel. If you attempt to install cm11 again it still won't work, however if you try to return the phone they will see that Knox has been triggered (meaning you messed with stuff you weren't 'supposed' to) and will say NAH. Doesn't really matter though in my opinion as it is hard to brick this phone and need a replacement anyway.

Related

[Q] Device Status: Official

I have rooted and installed a custom rom on my GS4 and it still says official. Is this normal?
I expected that after bricking and flashing stock and rerooting and everything I must have tripped the flash counter.
I don't really care as I don't plan on needing the warranty, I'm just surprised. I even previously had the custom unlock boot screen before bricking the phone.
Am I just looking in the wrong place?
DanGerousDroid said:
I have rooted and installed a custom rom on my GS4 and it still says official. Is this normal?
I expected that after bricking and flashing stock and rerooting and everything I must have tripped the flash counter.
I don't really care as I don't plan on needing the warranty, I'm just surprised. I even previously had the custom unlock boot screen before bricking the phone.
Am I just looking in the wrong place?
Click to expand...
Click to collapse
Flash counter will only register non Samsung images which we cannot flash successfully with a locked boot loader. Unless you are unlucky enough to accidently use Odin to install cwm or push a rom, them a factory restore via Odin should for all intents be undetectable as previously rooted. There might be something on a hidden partition I am unaware of but I have heard nothing yet.
Sent from my Galaxy S4

new ota s4 yesterday

So I made the switch from my hyperdrive S3 to the s4 yesterday. Best buy did the update to me7... Am I understanding that I'm stuck with stock because it has an unlockable bootloader? I rooted it last night and it was fine but now what?
I can't stand a bloated stock phone anymore after my slimmed s3.
Everything I've read seems to indicate there's no way around the bootloader
As of right now, yes, you're stuck on stock. You do have root, so you can at least freeze the Samsung/carrier apps you don't want, but the bootloader is locked and nobody has figured out a way to bypass it yet. If you unroot you might be able to return it on the excuse that the phone is having performance issues, and tell them you've heard the new software update is to blame so you don't want it installed on the replacement.

I had knox bootloader with 0x1 tripped and now I don't even have knox bootloader.

I am not a developer and I don't know how this happened. From what I hear this is impossible. I now have the odin I am used to with the binary counter that can be reset. It still says warranty bit: 1 in a spot but knox is not mentioned anywhere in my software. I first updated my t999l to 4.3 officially when I got it before hearing about knox. I then used odin to revert back to stock but rooted software and installed cwm. Since then I have tried out cyanogen and ended up sticking to Liquidsmooth rom. I am just pretty confused because I managed to revert back off knox bootloader to the original. I also have installed 4.3 after reverting back to 4.2 and from what I hear this should hard brick my device. Any ideas on how this happened would be nice because it sounds like the dream of a lot of people to figure out how to do this.

Re-enabling OTAs after Knox trip?

Hey everyone. I decided I would unlock my bootloader and trip Knox about two days before towelroot came out. Yay.
I've since gotten the OPO, so I wasn't that concerned. I wanted to give the phone to my mom who lives in another state, so I Odin'ed back to what I believe is the most current OEM firmware available (NK2) because I want my mom to be able to get updates OTA and not have to worry about troubleshooting her phone as much as if it were a custom ROM, or a phone with root.
Unfortunately, checking for a system update says the system is modified (ROM is all stock though) and device status is custom. I also discovered while testing the phone (it had been sitting in a drawer for months) that the microphone isn't working very well. I tried different sims, calling different people on different networks, I'm sure it's hardware problem. Is there any way to re-enable the OTAs? I'd like to get this hardware problem warrantied. The knox tripping didn't destroy the mic, so please no judgement here. I'm also not comfortable in removing the glass to replace the mic. If the mic could be replaced without that step, I would simply do that.
Thank you.
rockingondrums said:
Hey everyone. I decided I would unlock my bootloader and trip Knox about two days before towelroot came out. Yay.
I've since gotten the OPO, so I wasn't that concerned. I wanted to give the phone to my mom who lives in another state, so I Odin'ed back to what I believe is the most current OEM firmware available (NK2) because I want my mom to be able to get updates OTA and not have to worry about troubleshooting her phone as much as if it were a custom ROM, or a phone with root.
Unfortunately, checking for a system update says the system is modified (ROM is all stock though) and device status is custom. I also discovered while testing the phone (it had been sitting in a drawer for months) that the microphone isn't working very well. I tried different sims, calling different people on different networks, I'm sure it's hardware problem. Is there any way to re-enable the OTAs? I'd like to get this hardware problem warrantied. The knox tripping didn't destroy the mic, so please no judgement here. I'm also not comfortable in removing the glass to replace the mic. If the mic could be replaced without that step, I would simply do that.
Thank you.
Click to expand...
Click to collapse
Hmm. Last time I Odined back to stock, using the tar file of the firmware version that came before NK2, my device was totally fine to receive OTA, despite Knox being tripped. Try removing root first, then Odin stock NK2, then factory reset.
Hm, so I now need to install SuperSU in order to use the un rooting function? I would've thought a full stock image file would've eliminated root...
EDIT - Simple Root checker says SuperSU is not installed BUT terminal app "does Rooted".
Installed SuperSU, but binary is not installed, so it doesn't run. WTH? What happened to the good old days of just flashing stock images and not worrying about it anymore?
SOLVED
I looked at the slightly outdated stock collection thread, flashed the NG4 stock image, then was able to take the OTA update to NK2. Went ahead and told T-Mobile the whole problem and they really only seemed to care if there was physical damage or water damage (which there is not).
Just leaving this here for future searches. How do I get this thread closed?

How to root Note 3 on Lollipop

Pretty easily done with Odin and TWRP.
ALERT! This will void whatever warranty you have. Also, I am not at fault if your phone comes to life..... or dies.
Just need to download Odin (there are forums all over for finding the files.)
Download the TWRP recovery flash file:
http://dl.twrp.me/hltespr/twrp-2.8.6.1-hltespr-4.4.img.tar
Download Chainfire's SuperSU and copy to SD card:
http://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
Power off phone entirely.
Hold Volume down + home and power the device on, then press Volume up to confirm entering Download Mode.
Open Odin.
Connect Phone to computer.
Wait for drivers to install if not already. May need to obtain Samsung USB drivers (http://androidxda.com/download-samsung-usb-drivers)
When the box shows "COM #", click the PDA button and select the TWRP image file you downloaded. (or other recovery).
Uncheck "Auto Reset"
Click Start.
Once finished, disconnect device.
PULL BATTERY
Power into Recovery first thing first by holding Volume up + Home. (failure to do so will result in the stock recovery being flashed back on boot by the phone)
Recovery will autopatch the ROM to prevent the stock recovery from being rewritten on reboot. (or should)
From inside your recovery, flash the SuperSU update zip.
Reboot and enjoy root!
(I had to try a couple of times through trial and error to get it to stick)
Thank you.
Thank worked like a charm!
Worked first time. Thanks!
Sent from my SM-N900P using XDA Free mobile app
Does doing it this way trip Knox? I read the part about voiding your warranty. I know by having root it voids Samsung warranty.
Sent from my SM-N900P using Tapatalk 2
rbaucom said:
Does doing it this way trip Knox? I read the part about voiding your warranty. I know by having root it voids Samsung warranty.
Sent from my SM-N900P using Tapatalk 2
Click to expand...
Click to collapse
It does from what I can tell. A stock ROM flash should be able to reset Knox, it did for me, but varied results from other threads on these forums.
Greaper88 said:
It does from what I can tell. A stock ROM flash should be able to reset Knox, it did for me, but varied results from other threads on these forums.
Click to expand...
Click to collapse
Wow your the first person that I have read that was able to reset a blown an efuse American sprint note 3 Knox that way.
I'm reluctant to try it.
And thinking about it it looks like that yes it would looks like it needs a a non stock recovery.
I'll wait.
Looks like we are about to have a deodexed stock rom with root about to drop. From the other thread post in here.
http://forum.xda-developers.com/showthread.php?t=3104033
Stock rooted ROMs
Sent from my SM-N900P using Tapatalk 2
Just to clarify. Once KNOX is tripped there is no reseting it unless the insides are swapped out. When you trip KNOX you blow an e-fuse which is non reversible. However there are ways of upgrading and keeping root without tripping knox, but thats has nothing to do with this
May is Motorcycle Awarness Month. Sent from my Galaxy Note 3
elwood said:
Just to clarify. Once KNOX is tripped there is no reseting it unless the insides are swapped out. When you trip KNOX you blow an e-fuse which is non reversible. However there are ways of upgrading and keeping root without tripping knox, but thats has nothing to do with this
Click to expand...
Click to collapse
so tripping KNOX and blowing the e-fuse is bad, right? so what happens after? does the phone self destruct? and is there a way around it?
agentcelsius said:
so tripping KNOX and blowing the e-fuse is bad, right? so what happens after? does the phone self destruct? and is there a way around it?
Click to expand...
Click to collapse
It's only bad if you care about warranty. Once rooted it will show 0x1 in Download Mode. A Samsung repair Tech or Sprint Repair Tech can see that and refuse to fix your phone
By replying to this post, you acknowledge that you have read and understand the OP including all links included in OP.. Sent from my Galaxy Note 3
very good
Sprint doesn't care. It's more on Samsung go site. Never had a issue with Knox tripped with sprint.
Sent from my 0x1 Note 3...... I love tep
Got root
Worked a treat on my Note 3 SM-9005 Lollipop, took 1st time no probs.
Knox is tripped but what the hell, I've been living with the stock build up until the Lollipop update.
works fine
I recently upgraded to ok2, and used this same procedure to reroot my phone successfully.
Coming from JellyBean MJ4 firmware would it be safe to flash the pre-rooted OK2 through TWRP?
Flashed fine from NAB and seemed functional enough but I wasn't happy with the Lollipop UI. Reverted to NK4.
Thanks worked from OK2 Stock.
One question... Can I use another SU application? I was trying to use an old wireless tethering application but it is asking me if I am rooted and won't start.
Titanium backup runs fine and says I have root, as does Root Checker.
If not, does anyone have a working wireless tethering application for their Note 3?
yarmock said:
Thanks worked from OK2 Stock.
One question... Can I use another SU application? I was trying to use an old wireless tethering application but it is asking me if I am rooted and won't start.
Titanium backup runs fine and says I have root, as does Root Checker.
If not, does anyone have a working wireless tethering application for their Note 3?
Click to expand...
Click to collapse
I use Wi-Fi tether router. It's about $3 and works beautifully. (It does license check I believe)
They haven't updated their language to include lollipop, but as a general rule, whatever it says to do for kitkat will work on lollipop. Under "Configure Router," they have a link to the website with a list of configurations. Just follow that, and you should be good. One thing that I would add is to leave the "lte tether patch" unchecked.
https://play.google.com/store/apps/details?id=net.snclab.wifitetherrouter
You could try finding a newer superuser zip to flash in recovery. I do know that a couple of older ones gave that issue. I personally didn't have any luck with another supersu app, but the last time I tried a different one was on kitKat.

Categories

Resources