So i decided to root a couple days ago and when i went to update to 4.3 it gave me the "Custom" padlock. I care more about warranty than root at this point and will do whatever to get back to it. Dumb of me, i know. The only other way is triangle away but the boot loader hasn't been unlocked yet, has it?
Thanks.
My plan of attack is thus: reroot, triangle away, no wipe flash vrudmi1, accept ota.
In case anyone is wondering.
Once the knox counter gets tripped theres no resetting it.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
I concur...
Sent from my SCH-I545 using xda app-developers app
schimm1 said:
So i decided to root a couple days ago and when i went to update to 4.3 it gave me the "Custom" padlock. I care more about warranty than root at this point and will do whatever to get back to it. Dumb of me, i know. The only other way is triangle away but the boot loader hasn't been unlocked yet, has it?
Thanks.
Click to expand...
Click to collapse
The "Custom" flag that shows up when you boot is not related to the Knox Warranty Void counter. You haven't done anything to trip the Knox counter so you should be fine. If you want to check it, start your phone in downloader mode and check the value there.
I'd re-root, then flash the no-wipe. That should clear the "custom" flag. If not, use Triangle Away. Then, once you're rooted on MI1, update to MJ7.
k1mu said:
The "Custom" flag that shows up when you boot is not related to the Knox Warranty Void counter. You haven't done anything to trip the Knox counter so you should be fine. If you want to check it, start your phone in downloader mode and check the value there.
I'd re-root, then flash the no-wipe. That should clear the "custom" flag. If not, use Triangle Away. Then, once you're rooted on MI1, update to MJ7.
Click to expand...
Click to collapse
Still at 0x0, thank deity
rerooted and custom/padlock disappeared. flashed no wipe, uninstalled all my root apps, going to accept OTA.
Update: OTA took as if i had never deviated from samsung's creepily obsessive grasp. Hopefully this thread helps someone in the future.
OTA took as if i had never deviated from samsung's creepily obsessive grasp. Hopefully this thread helps someone in the future.
schimm1 said:
rerooted and custom/padlock disappeared. flashed no wipe, uninstalled all my root apps, going to accept OTA.
Update: OTA took as if i had never deviated from samsung's creepily obsessive grasp. Hopefully this thread helps someone in the future.
Click to expand...
Click to collapse
can you explain that a little more? i am hoping to do the same
HwaA18 said:
can you explain that a little more? i am hoping to do the same
Click to expand...
Click to collapse
I rooted a little while ago and tried to update to MJ7 but it did a flash check (i think) and gave me the padlock and wouldn't update. So i re-rooted the root de la vega for MI7 (which got rid of the "custom" padlock,) then flashed the MI7 no-wipe factory and removed root, essentially giving me a "clean/untouched" stock samsung. I deleted all of my root apps (supersu, rootchecker, barnacle) just in case the update checks for them and tried the OTA update. It worked.
Link to No-Wipe stock image
Hopefully that helps. I'm not great at this stuff, just a script kiddie who follows guides.
Related
hi,
just got my GS4 today and, very stupidly, agreed to let the phone update to the new firmware via verizon's OTA update to VRUDMI1. realizing i had already made a mistake, i used ODIN to try and flash it back to the stock firmware, which failed. i tried a couple packages for the stock VZ image, but both have failed. also, apparently the VZ GS4 does not give you a serial number, so Samsung's KIES is not an option, unless i am mistaken. i tried downloading that and using my IMEI as the serial but it says the serial is incorrect.
am i completely screwed? or maybe just for the time being until a new image for flashing back to stock from the new firmware is released? the phone boots into ODIN but gives the message that there was an error while updating the firmware, and to try the software repair assistant. based on what i've been reading, it seems that this is sometimes fixable, but perhaps it is just too early for this firmware at this point? ugh.
long shot: the phone was not rooted at the time, locked bootloader, running the fully stock VZ image and new firmware -- perhaps they would provide assistance? i wouldn't hold my breath though!
androidy_guy said:
hi,
just got my GS4 today and, very stupidly, agreed to let the phone update to the new firmware via verizon's OTA update to VRUDMI1. realizing i had already made a mistake, i used ODIN to try and flash it back to the stock firmware, which failed. i tried a couple packages for the stock VZ image, but both have failed. also, apparently the VZ GS4 does not give you a serial number, so Samsung's KIES is not an option, unless i am mistaken. i tried downloading that and using my IMEI as the serial but it says the serial is incorrect.
am i completely screwed? or maybe just for the time being until a new image for flashing back to stock from the new firmware is released? the phone boots into ODIN but gives the message that there was an error while updating the firmware, and to try the software repair assistant. based on what i've been reading, it seems that this is sometimes fixable, but perhaps it is just too early for this firmware at this point? ugh.
long shot: the phone was not rooted at the time, locked bootloader, running the fully stock VZ image and new firmware -- perhaps they would provide assistance? i wouldn't hold my breath though!
Click to expand...
Click to collapse
Yeah once you go to ME7 or MI1, there is no going back. You can only stay where you are, or go forward. You'll need to use Odin again and this time flash the MI1 file.
Which can be found here thanks to Surge1223
http://forum.xda-developers.com/showthread.php?t=2484726
spc_hicks09 said:
Yeah once you go to ME7 or MI1, there is no going back. You can only stay where you are, or go forward. You'll need to use Odin again and this time flash the MI1 file.
Which can be found here thanks to Surge1223
http://forum.xda-developers.com/showthread.php?t=2484726
Click to expand...
Click to collapse
Chances are it will also flip the knox warranty to void because knox status/warranty is now included in the new firmware.
tech_head said:
Chances are it will also flip the knox warranty to void because knox status/warranty is now included in the new firmware.
Click to expand...
Click to collapse
hmm, interesting. perhaps i should try my luck with VZ first? i guess it can't do any harm. currently when it turns on it shows knox status 0x0, which is apparently good. perhaps VZ can flash it somehow? i have no idea what kind of support they provide for this kind of thing.
edit: also it seems this KNOX is mainly relevant for creating a secure zone for corporate applications? i am not using it in that setting. perhaps it would just reduce the resale value somewhat? or is there something i'm not understanding about it.
That flag if set will have Samsung trying to deny any warranty.
They are not going to flash it for you.
Not advocating fraud or anything., but you have only had it one day.......
Sent from my SCH-I545 using Tapatalk
tech_head said:
That flag if set will have Samsung trying to deny any warranty.
They are not going to flash it for you.
Not advocating fraud or anything., but you have only had it one day.......
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
yea, i figured as much. it does say "system status: custom" though - maybe that alone will screw me? not sure how VZ will see that. if they refuse is it worth contacting samsung directly?
also, bought the phone used from a friend, so that prob eliminates any hope from VZ to begin with.
Flash the Odin posted in post 2. Then you can root and use safestrap the same as it being on me7 like it was.
androidy_guy said:
yea, i figured as much. it does say "system status: custom" though - maybe that alone will screw me? not sure how VZ will see that. if they refuse is it worth contacting samsung directly?
also, bought the phone used from a friend, so that prob eliminates any hope from VZ to begin with.
Click to expand...
Click to collapse
Okay, bought from friend not Verizon.
So back to ODIN it is.
You just need the latest firmware to flash. You can't use ME7 but you can use the latest one.
The file is in this thread -> http://forum.xda-developers.com/showthread.php?t=2484726 like one of the previous people posted.
You already know how to use ODIN and this should work. Just remember PDA mode.
Once you flash Me7 there was no going back and MI1 is the same. No going backward.
You should be fine if you can get into download.
^^^^^^^^^ what he said
tech_head said:
Okay, bought from friend not Verizon.
So back to ODIN it is.
You just need the latest firmware to flash. You can't use ME7 but you can use the latest one.
The file is in this thread -> http://forum.xda-developers.com/showthread.php?t=2484726 like one of the previous people posted.
You already know how to use ODIN and this should work. Just remember PDA mode.
Once you flash Me7 there was no going back and MI1 is the same. No going backward.
You should be fine if you can get into download.
Click to expand...
Click to collapse
will do - downloading the package now. should be able to fool around with it after work today. i feel like a real idiot for rushing into this without knowing enough about the OTA firmware that i ignorantly accepted.
at this point i don't really care if the KNOX is triggered or whatever - i always purchase my devices out of warranty and activate them so i can keep my grandfathered unlimited. it's the risk i run for wanting stock android on verizon with unlimited data
ooooook, the package in that thread worked. thanks a lot guys! i was really kicking myself all day over this one, and really had only myself to blame. my only questions now are:
how can i check my KNOX status?
is it likely that there will be a root/CM version for this phone, post UMI1?
Reboot into download and read the tiny text with a magnifying glass
Sent from my SCH-I545 using Tapatalk
Im glad the odin image worked...pulling that thing was kinda difficult lol.
ok i booted into ODIN again and KNOX comes up 0x0, so it looks like i came out unscathed all around. too bad i inadvertently locked my phone down with this update. i got the GS4 so i could upgrade from my GN, in hopes of flashing the latest CM10 on a phone with some nicer hardware.
I'm running 4.3 and kind of getting tired of waiting for a root method other than vroot. So I might as well use it. I just have a few questions for people that have used it.
- Does it show a custom boot animation?
- Can you receive OTA updates?
- Can you completely unroot?
- If you unroot will the boot animation go back to stock? (From what I've seen and heard there is a custom boot animation but I wasn't sure)
- Does it wipe your phone/delete everything?
- Does it void the KNOX warranty? (0x0 to 0x1)
For the most part I've heard some answers here and there and they were not clear enough. I would like to know from someone who's done it and what their experience was like. Thanks.
Sent from my SCH-I545 using xda app-developers app
1. Yes it does
2. I'm on MJ7 so I couldn't say for sure
3. Haven't tried it yet but while I was attempting to root there was an area that appeared to be unroot, don't mark my words
4.
5. Does not wipe
6. Not that I know
Sent from my SCH-I545 using XDA Premium 4 mobile app
tredonkulous said:
I'm running 4.3 and kind of getting tired of waiting for a root method other than vroot. So I might as well use it. I just have a few questions for people that have used it.
- Does it show a custom boot animation?
- Can you receive OTA updates?
- Can you completely unroot?
- If you unroot will the boot animation go back to stock? (From what I've seen and heard there is a custom boot animation but I wasn't sure)
- Does it wipe your phone/delete everything?
- Does it void the KNOX warranty? (0x0 to 0x1)
For the most part I've heard some answers here and there and they were not clear enough. I would like to know from someone who's done it and what their experience was like. Thanks.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
I'm only going to attempt one question on that list.
At this point presume that rooting will cause OTA to fail, minimally you will lose root.
I say this because the files they check are getting more encompassing.
When I went from ME7 to MI1, no problem, rooted and retained root.
MI1 -> MJ7, can't update rooted unless you jump through a couple of hoops.
Presume those hoops will get tighter and tighter as Verizon tries harder at every update to hold your phone hostage.
I'm not going to MJ7 because tethering is now difficult at best and all the hacks that allowed Google Wallet to work, don't work anymore.
tredonkulous said:
I'm running 4.3 and kind of getting tired of waiting for a root method other than vroot. So I might as well use it. I just have a few questions for people that have used it.
- Does it show a custom boot animation?
- Can you receive OTA updates?
- Can you completely unroot?
- If you unroot will the boot animation go back to stock? (From what I've seen and heard there is a custom boot animation but I wasn't sure)
- Does it wipe your phone/delete everything?
- Does it void the KNOX warranty? (0x0 to 0x1)
For the most part I've heard some answers here and there and they were not clear enough. I would like to know from someone who's done it and what their experience was like. Thanks.
Sent from my SCH-I545 using xda app-developers app[/QUOTE
It has the stock samsung boot animation with the pad lock unlocked, you can recive ota if you dont freeze or remove system apps or install xposed framework but ota usually kills root so freeze sdm 1.0 and knox through titanium backup to avoid future ota hassle, to completely unroot download odin and get the mj7 odin file boot your phone into odin download mode and flash back to stock. Dont worry about the boot animation if use odin it all gets wiped back to stock but it does wipe your data but knox wont be tripped if you use odin because you are reflashing the rom which resets everything. I used vroot with zero issue and love my 4.3 stock rooted phone!
Click to expand...
Click to collapse
I have Verizon Samsung Galaxy S4 with 4.4.2. It has been rooted since I bought it at the end of May 2013. I re rooted many times to keep up with software updates. I used Kies 3 to flash back to default 4.4.2. I mean a complete nuke. I then flashed with towelroot and rebooted to see if the custom broken padlock was present at boot. The padlock was not present and no padlock icon present yay!!!. I installed SuperSu by chainfire and disabled knox as per SuperSu suggestion. I rebooted to check if custom flag had been tripped. The broken padlock was there god dammit.
SuperSu seems to have triggered knox or tripped the counter.
How do I maintain root and have the boot screen display everything is normal.
AND how do I get settings to display official instead of custom.
Please help as XDA and Google searches are not providing ansers.
You won't find a lot of info because most people would tell you if you don't want the custom padlock don't use custom software. You can use "Triangle Away" or the option in the Security Hacks section of the Wanam Xposed module.
Thanks
joshm.1219 said:
You won't find a lot of info because most people would tell you if you don't want the custom padlock don't use custom software. You can use "Triangle Away" or the option in the Security Hacks section of the Wanam Xposed module.
Click to expand...
Click to collapse
Well. I looked at triangle away. It messes with the hardware startup code and I don't want to do that. So ill be fine for now. My phone is out of warranty so it's not a big deal and I have insurance on my pbone. I was only bothered because I like pretty visuals.
purplenate26 said:
I have Verizon Samsung Galaxy S4 with 4.4.2. It has been rooted since I bought it at the end of May 2013. I re rooted many times to keep up with software updates. I used Kies 3 to flash back to default 4.4.2. I mean a complete nuke. I then flashed with towelroot and rebooted to see if the custom broken padlock was present at boot. The padlock was not present and no padlock icon present yay!!!. I installed SuperSu by chainfire and disabled knox as per SuperSu suggestion. I rebooted to check if custom flag had been tripped. The broken padlock was there god dammit.
SuperSu seems to have triggered knox or tripped the counter.
How do I maintain root and have the boot screen display everything is normal.
AND how do I get settings to display official instead of custom.
Please help as XDA and Google searches are not providing ansers.
Click to expand...
Click to collapse
Well, perhaps you could start with the sticky threads here?
One: Assuming that "triped" is just a typo for "tripped": No, that's wrong. First, the phrase "tripped Knox" is usually how people refer to something that sets the "Knox Warranty Void" flag. Installing SuperSU will not set the Warranty Void flag.
You're apparently seeing the "Custom" flag show up at boot, and claiming that's evidence that something "tripped Knox". That's wrong. That's been discussed in the sticky threads here and in the General forum. The "Custom" status means that your phone is no longer running stock.
If you care about the "Custom" flag, flash stock. It'll get cleared after a while. Or, run one of the several techniques to clear it (Triangle Away, Xposed framework, etc.)
The easy way to clear that flag is to flash a stock ROM. If you want to run non-stock, you'll need to live with it, or use one of the work-arounds. I use TA to clear Custom.
something i kinda want to add to this, SuperSU will actively disable knox upon installing it. There is absolutely no way you can trip Knox just with SuperSU. From what i can tell, Knox only gets tripped when you modify the kernel or boot stuff (recovery, etc.) and by that point you'd end up bricking a phone if you didnt have the MDK bootloader
Clear syscope with titanium backup
Sent from my GT-I9505G using XDA Free mobile app
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.
Hi,
I have been with AT&T for a long time. AT&T locks boot loader so there were limited options in rooting.
My understanding is that T-Mobile does not lock the boot loader. So the easiest way to root is to install TWRP using Odin and then use TWRP to flash SuperSU.apk. Is this correct? Does it trip KNOX?
Once installed, is there a way to uninstall it and revert back to full stock?
Thanks
redhonker said:
Hi,
I have been with AT&T for a long time. AT&T locks boot loader so there were limited options in rooting.
My understanding is that T-Mobile does not lock the boot loader. So the easiest way to root is to install TWRP using Odin and then use TWRP to flash SuperSU.apk. Is this correct? Does it trip KNOX?
Once installed, is there a way to uninstall it and revert back to full stock?
Thanks
Click to expand...
Click to collapse
Same AT&T situation here. Yes you can root with twrp and supersu zip. It does trip Knox. If you factory reset and flash a stock Odin firmware that should revert to full stock
Hmm, tripping KNOX would need void warranty right? Is there an alternative to root? Thanks
redhonker said:
Hmm, tripping KNOX would need void warranty right? Is there an alternative to root? Thanks
Click to expand...
Click to collapse
I've successfully brought in a device with a tripped Knox flag for warranty. I said Kies caused the problem (the word "lie" has such a negative connotation, but this was patently not true) and they were completely fine with that explanation, in fact they were tripping over themselves to make sure they could fix it for me. I guess that's my long-winded way of saying a tripped Knox flag doesn't prevent you from taking advantage of your warranty. Besides, I could swear I remember reading an article recently saying Samsung will now honor warranties even on devices where the Knox flag is tripped.
TLDR: A tripped Knox flag is no longer the black mark of death that it used to be