Related
I have a Note 3 that I bought the day they where released so obviously I don't have the latest firmware.
I have safestrap installed (rooted with delavega). I have the stock but debloated ROM in the stock slot & Beans awesome ROM running in slot 1.
I have nandroid backups of both ROMs (on my 64gig card) and I have actually done a restore of both just to make 100% sure they worked.
I should probably leave well enough alone as EVERY SINGLE THING works perfectly in my slot 1 Beans setup but I'm still kinda on the fence about flashing the new firmware (my long time Wife once commented "you break things intentionally just so you can figure out how to fix them!!").
I have never had a phone that used safestrap so this is all new to me. My questions are:
1. I have downloaded the Odin flashable tar for the new firmware. If I flash this, does it wipeout safestrap/the ROM slots etc.(like formatting a windows hard drive) so it becomes basically a new stock phone unrooted and all the internal storage blank??
2. If that is the case, can I first flash the new firmware tar, then root with kingblo, then install safestrap/recreate ROM slot 1 and then restore the nandroid of my current Beans BU and be basically right back to where I am now but with the new firmware installed??
jmorton10 said:
I have a Note 3 that I bought the day they where released so obviously I don't have the latest firmware.
I have safestrap installed (rooted with delavega). I have the stock but debloated ROM in the stock slot & Beans awesome ROM running in slot 1.
I have nandroid backups of both ROMs (on my 64gig card) and I have actually done a restore of both just to make 100% sure they worked.
I should probably leave well enough alone as EVERY SINGLE THING works perfectly in my slot 1 Beans setup but I'm still kinda on the fence about flashing the new firmware (my long time Wife once commented "you break things intentionally just so you can figure out how to fix them!!").
I have never had a phone that used safestrap so this is all new to me. My questions are:
1. I have downloaded the Odin flashable tar for the new firmware. If I flash this, does it wipeout safestrap/the ROM slots etc.(like formatting a windows hard drive) so it becomes basically a new stock phone unrooted and all the internal storage blank??
2. If that is the case, can I first flash the new firmware tar, then root with kingblo, then install safestrap/recreate ROM slot 1 and then restore the nandroid of my current Beans BU and be basically right back to where I am now but with the new firmware installed??
Click to expand...
Click to collapse
I basically have the same set up as you except I’m running Hyperdrive. I just did this myself about an hour ago and didn’t lose anything. But I did and always make a backup before I do anything just in case.
1. Download Beans MJ7 Full Stock Tar: http://www.androidfilehost.com/?fid=23212708291674903
2. Make sure you boot into your “stock rom” before you Odin the stock tar. Latest Odin v.3.09: http://www.androidfilehost.com/?fid=23212708291676783
3. Odin the stock tar and when you’re done you’ll be un-rooted but on the MJ7.
4. Download and install the Kingo Root App to your PC and follow the instructions. LINK REMOVED BY VECTUS
5. After you re-root your phone and it reboots go back into safestrap or re-download it if it’s missing and reinstall the recovery. http://forum.xdadevelopers.com/showthread.php?t=2517610
Everything was still there for me when safestrap recovery booted up. I didn’t lose any data.
Good luck
Uhm. I don't think you're allowed to post links for Kingo.
Sent from my SM-N900V using Tapatalk
haza12d said:
Uhm. I don't think you're allowed to post links for Kingo.
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
Its not... I removed the link... :good:
Whoops you're right my mistake sorry about that.
Sent from my SM-N900V using xda premium
Is that app the only way to root the note 3 currently?
Thanks for the responses guys, it went like clockwork.
I Odin flashed the full mj7 tar that I downloaded from crack flashers (after beans like timed out on me about 25 times). Then immediately did the Kingo thing which worked super.
At that point, I installed the newest safestrap & recreated the same #1 ROM slot I had before the flash. I then restored a nandroid I had made of the Bean ROM install from that slot from before the Odin flash to that new ROM slot and it works perfectly.
I see no difference whatever except for the new firmware showing in the device properties.
Hey guys, been looking through the forum all morning at different ROM's. I considered the KK upgrade, however can't find a working link to a DL, my telco still have not released the KK update.
I have N9005 model, on 4.3 rooted using Chainfire, have CWM. I DL a 4.3 ROM, but can't figure out how to get it on my phone from PC (I sent the zip file over, but it does not show up on CWM), I found a few KK ROMS that interest me, but can't find a working link to a DL of 4.4.2 it for me to flash. I would post in the respective thread, but I cn't post in the developer forums yet.
As I understand to do most roms on here now, I need to flash 4.4.2, Root it, install new version of CWM, then install the rom.
However if I have used CWM to do a nandroid backup, is it possible to flash it back to that, or is any chance of 4.3 gone once I flash 4.4
I know this is very noob, but we all gotta learn some day.
Any help, even a link to 4.4.2 DL would be awesome.
Spudz30 said:
Hey guys, been looking through the forum all morning at different ROM's. I considered the KK upgrade, however can't find a working link to a DL, my telco still have not released the KK update.
I have N9005 model, on 4.3 rooted using Chainfire, have CWM. I DL a 4.3 ROM, but can't figure out how to get it on my phone from PC (I sent the zip file over, but it does not show up on CWM), I found a few KK ROMS that interest me, but can't find a working link to a DL of 4.4.2 it for me to flash. I would post in the respective thread, but I cn't post in the developer forums yet.
As I understand to do most roms on here now, I need to flash 4.4.2, Root it, install new version of CWM, then install the rom.
However if I have used CWM to do a nandroid backup, is it possible to flash it back to that, or is any chance of 4.3 gone once I flash 4.4
I know this is very noob, but we all gotta learn some day.
Any help, even a link to 4.4.2 DL would be awesome.
Click to expand...
Click to collapse
First thing, if you go to KK you can't come back. Nobody has yet found a way to reset Knox or to revert the bootloader from KK. Go to it and you're stuck with it. May not matter depending on how you use your phone but there's a thread on here where the poster actually got his phone replaced because KK update meant he could no longer use it as he wanted and as he had it set up under 4.3.
(see http://forum.xda-developers.com/showthread.php?t=2709623 )
You've already tripped Knox using Chainfire's autoroot so you're free to do pretty much whatever you wish. I have stayed with 4.3, using Alliance ROM, Philz recovery and Lean kernel because the phone is awesome using them and KK seems to be generating lots of problems even now and doesn't appear to offer anything really worth having to make up for the troubles... IMO.
If you can't see the zip in CWM the most likely reason is you're looking at the wrong 'card' - in Philz recovery for example, the external SD card is SDCard1, not SDCard. At a guess you have copied the zip to the external card and CWM is looking on the internal memory.Not sure what the options are for plain CWM but look for another card option or move the zip from where you have it. Given the best flash is to wipe everything on the internal memory, the external card is the best location - it won't be wiped.
Another way to do it is to use Odin - extract the zip till you get the MD5 file and flash that via Odin to the phone - you need to put the phone in Download mode to do it. (hold Menu + Vol Down + Power to get to DL mode) There are threads on here with instructions on how to use Odin.
Journyman16 said:
First thing, if you go to KK you can't come back. Nobody has yet found a way to reset Knox or to revert the bootloader from KK. Go to it and you're stuck with it. May not matter depending on how you use your phone but there's a thread on here where the poster actually got his phone replaced because KK update meant he could no longer use it as he wanted and as he had it set up under 4.3.
(see http://forum.xda-developers.com/showthread.php?t=2709623 )
You've already tripped Knox using Chainfire's autoroot so you're free to do pretty much whatever you wish. I have stayed with 4.3, using Alliance ROM, Philz recovery and Lean kernel because the phone is awesome using them and KK seems to be generating lots of problems even now and doesn't appear to offer anything really worth having to make up for the troubles... IMO.
If you can't see the zip in CWM the most likely reason is you're looking at the wrong 'card' - in Philz recovery for example, the external SD card is SDCard1, not SDCard. At a guess you have copied the zip to the external card and CWM is looking on the internal memory.Not sure what the options are for plain CWM but look for another card option or move the zip from where you have it. Given the best flash is to wipe everything on the internal memory, the external card is the best location - it won't be wiped.
Another way to do it is to use Odin - extract the zip till you get the MD5 file and flash that via Odin to the phone - you need to put the phone in Download mode to do it. (hold Menu + Vol Down + Power to get to DL mode) There are threads on here with instructions on how to use Odin.
Click to expand...
Click to collapse
I will stick with JB for now as I like my setup anyway. I know how odin works and CWM was definitely looking at my External SD as my backup was on it. This is the ROM I was trying http://forum.xda-developers.com/showthread.php?t=2541304 I DL, extracted to a folder on my PC, put onto my micro SD, but alas, nothing to choose from to flash.
Found the Alliance one for N9005, looks real nice, so will give it a shot.
Deleted
Urghhhh why is it after hours of trawling and googling I can't find my answer. I did the alliance ROM (and now know how my first rom stuffed up) how do I get rid of the icon in the top left which shows download rate? Can't find the option anywhere on phone
Edited: Found it myself.
Final bit of noob from me for now. I tried to restore my CWM backup after installing Alliance, alliance overwrote CWM with TWRP, I did a factory reset, but could not restore from backup. It noted my CWM backup, but I could not restore it. Anything I did wrong here?
Edited: Once again from learning I fixed my own issue. Reflashed CWM, restored from todays backup, phone has gone from factory reset to how it was earlier today. Love the nandroid backup.
I have a verizon note 3 on the stock nc4 rom with a 64gb sdxc u1 micro sdcard installed & I can't install any custom roms from my external sdcard neither from inside my stock rom or from safestrap recovery. Any help would be most appreciated thank you in advance.
raze5115 said:
I have a verizon note 3 on the stock nc4 rom with a 64gb sdxc u1 micro sdcard installed & I can't install any custom roms from my external sdcard neither from inside my stock rom or from safestrap recovery. Any help would be most appreciated thank you in advance.
Click to expand...
Click to collapse
Sent from my GT-I8552 using XDA Free mobile app
raze5115 said:
I have a verizon note 3 on the stock nc4 rom with a 64gb sdxc u1 micro sdcard installed & I can't install any custom roms from my external sdcard neither from inside my stock rom or from safestrap recovery. Any help would be most appreciated thank you in advance.
Click to expand...
Click to collapse
When you say "I can't install any custom roms from my external sdcard" is it that you are unable to locate the zip file or is it that you flash the ROM and then get a black screen?
We need more information to help you out. Otherwise, you can head over here and check out a more in depth guide made by @az_biker
shaggy_kobain said:
When you say "I can't install any custom roms from my external sdcard" is it that you are unable to locate the zip file or is it that you flash the ROM and then get a black screen?
We need more information to help you out. Otherwise, you can head over here and check out a more in depth guide made by @az_biker
Click to expand...
Click to collapse
it says invalid zip if I try to install from inside the stock rom. & it says failed to flash "name of rom" if I try to install from safestrap. & installing from internal sdcard just screws up the install somehow cause when I reboot it just stays on black screen for a half hour.
Sounds like u need to flash nc2 first then the rom
chefrd38 said:
Sounds like u need to flash nc2 first then the rom
Click to expand...
Click to collapse
Wouldn't that be because it can't read my external sdcard.
Put the file in internal storage instead of external and try flashing nc2 then rom if you're having trouble wit SD card
chefrd38 said:
Put the file in internal storage instead of external and try flashing nc2 then rom if you're having trouble wit SD card
Click to expand...
Click to collapse
Ok I'll try that? Where do u get the nc2 thing
http://forum.xda-developers.com/showthread.php?t=2726558
★ [ROM/ROOT][N900VVRUCNC2][4.4.2] Stock Root Odex/DeOdex [04/23/14]★
chefrd38 said:
http://forum.xda-developers.com/showthread.php?t=2726558
★ [ROM/ROOT][N900VVRUCNC2][4.4.2] Stock Root Odex/DeOdex [04/23/14]★
Click to expand...
Click to collapse
I just flashed that one with odin to get my custom roms to work. But thanks for the info.
Sup you guys,
I may be in a new predicament for myself, so I would like to ask a few questions before I tackle this task. It seems that I've flashed a JB rom on the stock slot of SS, and I thought that I had the NC2 kernel intact to do so. However, all I get is a black screen and then a botched up system partition, a soft brick if you will, on the stock slot. Couldn't mount the system, so wiping anything is out the window. In order to make my phone usable for now, I had to install a rom on Slot 1. All is fine, but the battery drain is a killer, so I would like recover the system partition of the stock slot. Now, I've read a few threads that kind of pertains to my situation and I learned that a pit file flash can recover it back to normal. Can I just flash only the pit through Odin, or are there other steps that I have to do to get this back on track? Any help and guidance would be greatly appreciated.
I need help too
krazyg said:
Sup you guys,
I may be in a new predicament for myself, so I would like to ask a few questions before I tackle this task. It seems that I've flashed a JB rom on the stock slot of SS, and I thought that I had the NC2 kernel intact to do so. However, all I get is a black screen and then a botched up system partition, a soft brick if you will, on the stock slot. Couldn't mount the system, so wiping anything is out the window. In order to make my phone usable for now, I had to install a rom on Slot 1. All is fine, but the battery drain is a killer, so I would like recover the system partition of the stock slot. Now, I've read a few threads that kind of pertains to my situation and I learned that a pit file flash can recover it back to normal. Can I just flash only the pit through Odin, or are there other steps that I have to do to get this back on track? Any help and guidance would be greatly appreciated.
Click to expand...
Click to collapse
I just got into ROMs and safeatrap and such. I started by trying to load them to the stock slot, which failed every time. I then made slots and had 3 ROMs, but the battery life was not good.
So I wanted to put a ROM on the stock slot. This is with nc2 on kitkat. When I went to load a ROM in stock slot, safestrap failed saying it couldn't mount /system. I tried wiping, but there too it said fail to mount /system.
I did "Fix Permissions" and rebooted. I was greeted by the Samsung boot screen, but it froze there. No safestrap, nothing. I recovery booted and the stock recovery says "E:failed to mount /system (Invalid argument)"
So now it seems that no part of my phone can get to /system. I will look into a .pit file and would appreciate guidance as well.
Seems like you have the problem that I had a week ago. I fixed it by flashing a stock tar and the pit file through Odin. Though I wasn't too sure if just flashing pit would repair the system partition (though, I think it would've been fine; I should've just done it with no questions asked), but in my situation, I got a bit more desperate as my problem got sort of worse. Yea, running any rom on any slot other than the stock slot will kill your battery quick. So a reminder, if you have a messed up system partition, do not let the battery die because your phone will be soft bricked and you won't be able to boot up to anything other than Download mode. At that point, I just flashed the stock tar and the pit file just to be on the safe side and start over. After I rooted and installed SS, I went and checked if it was working properly. It did for the most part, but I remember that I was still on slot 1 before my battery died and SS was highlighted that I was still on that slot. I think because of that, it gave me certain errors on some of things I was testing out, but you will be able to install normally on the stock slot again. There are some other issues I have because of that ordeal, but it's not game breaking, so make sure that you're on the stock slot before flashing the files through Odin.
krazyg said:
Seems like you have the problem that I had a week ago. I fixed it by flashing a stock tar and the pit file through Odin. Though I wasn't too sure if just flashing pit would repair the system partition (though, I think it would've been fine; I should've just done it with no questions asked), but in my situation, I got a bit more desperate as my problem got sort of worse. Yea, running any rom on any slot other than the stock slot will kill your battery quick. So a reminder, if you have a messed up system partition, do not let the battery die because your phone will be soft bricked and you won't be able to boot up to anything other than Download mode. At that point, I just flashed the stock tar and the pit file just to be on the safe side and start over. After I rooted and installed SS, I went and checked if it was working properly. It did for the most part, but I remember that I was still on slot 1 before my battery died and SS was highlighted that I was still on that slot. I think because of that, it gave me certain errors on some of things I was testing out, but you will be able to install normally on the stock slot again. There are some other issues I have because of that ordeal, but it's not game breaking, so make sure that you're on the stock slot before flashing the files through Odin.
Click to expand...
Click to collapse
Thanks for the reply. I flashed a stock tar last night since the stock bootloader couldn't mount /system. Not sure which slot was selected in safestrap, I couldn't get back in because it would freeze before safestrap.
I did not use a .pit file (FYI), and am now back on stock ROM.
What I woluld like isto flash a custom ROM, say a debloated, rooted ROM with ODIN. I see they are all zips with folders, not .tar. Maybe I could take out the recovery.img and put it into a ROM's zip and save the zip as a tar and flash it? Would this possibly break my device if it tried to flash a wrong recovery? I don't know.
If anyone has some knowledge of these things, I would appreciate tips.
Why wouldn't you towel root, install SS, and install a ROM?
xdadevnube said:
Why wouldn't you towel root, install SS, and install a ROM?
Click to expand...
Click to collapse
Because I have only been able to get ROMs working on slots 1-4 of SS and not stock slot, so the battery life is terrible. Also, it would be faster and easier just to flash a ROM with ODIN and not have to worry if my version of android has a working root method (thankfully towelroot v3 worked).
Oh boy, I really screwed this one up...
I purchased a used Note 3 from eBay, hoping to be able to root it after it arrived. Much to my surprise, it arrived rooted with Safestrap, Hyperdrive ROM in Stock slot, and a different Hyperdrive ROM in Slot1. I was also impressed that KNOX had not been tripped. (It said Custom, but the KNOX flag showed 0x00)
Sweet looking phone in hand, I was thrilled! I wasn't going to have to cut my teeth on rooting the device myself prior to having an opportunity to explore a rooted Android and a custom ROM. The very first thing I did was to use Safestrap to backup both the Stock slot and Slot1. After the backups, I booted the stock slot first, to see how a factory Note 3 should look. Surprise again, the stock slot booted a Hyperdrive ROM. I was a bit nervous that I didn't have a truly stock ROM, but wasn't too worried about it because I had no plans to resell or seek repairs under warranty.
I then spent a couple of days tinkering with the device. Unfortunately, half asleep during the wee hours of the morning, I was tinkering around with SuperSU -- setting grant/deny/prompt flags for different apps. Somewhere in the midst of that, SuperSU informed me that I had lost root. I checked with RootChecker, and sure enough NO Root.
Things got worse from there, as I'm sure you can imagine. RootChecker had a button to relaunch SuperSU, so I tapped it. This time, SuperSU wanted to re-install itself. Being the ignorant noob that I am, I told SuperSU to proceed, and crossed my fingers. After a few seconds of thrashing around, SuperSU wanted to reboot, so I said okay...
Now the device attempts to go into recovery, reboots itself, attempts recovery, reboots, again, and again... boot loop... and no way to charge the battery... I believe I am around 55% to 60% charged at the moment.
So I read great things about Odin and downloaded a copy -- not yet sure exactly what I was going to do with it. I have been trying to wrap my head around this for a couple of days now, but I have several questions that I hope somebody can shed some light on.
Does the rooting take place in the boot image, or in the ROM image? I am assuming it has to be in the boot image, but then I've heard you can have rooted and unrooted ROMs in different slots.
If I use Odin to flash fresh firmware, will this firmware will have a functional recovery tool bundled with it?
Since the phone is no longer rooted, the recovery will not be able to re-flash a ROM onto the device?
If an Odin installed recovery can't re-flash a ROM due to being unrooted, am I faced with JTAG options only?
If I were to use Odin to flash this firmware: http://forum.xda-developers.com/showthread.php?t=2726558 , could I perhaps get SafeStrap back and be able to restore the backups I made? The links on that page appear to be to the same (or very similar) firmware that was running prior to this disaster. NC2, Safestrap, etc.
If I can't use Odin to flash the firmware linked in the previous paragraph, and get Safestrap to restore my backups, can I use the firmware, ROMs, and PIT file linked here: http://forum.xda-developers.com/showthread.php?t=2576104 to restore the phone to factory conditions and re-root from there?
Finally, is there any way for me to avoid tripping KNOX at this point? I'm not really sure I care if it gets tripped, but if I can avoid it then I probably should. Am I likely to need KNOX container support on a private device in the near future? Is there any other reason to be spooked about losing KNOX? I really don't care much about the warranty.
Any help with this mess will be **greatly** appreciated!
lintex said:
If I were to use Odin to flash this firmware: http://forum.xda-developers.com/showthread.php?t=2726558 , could I perhaps get SafeStrap back and be able to restore the backups I made? The links on that page appear to be to the same (or very similar) firmware that was running prior to this disaster. NC2, Safestrap, etc.
Click to expand...
Click to collapse
Ok, if anybody comes across this thread looking for answers -- I did successfully use Odin to get this firmware back onto the device. Upon booting, I had Safestrap, was able to boot Slot1, and had root. When I boot from the Stock slot, still no root.
I have not yet attempted to restore the Stock slot backup, because I first want to see if I can boot Slot1 (to get root), and then find/mount the Stock slot image and see if I can find a way to re-root it manually.
lintex said:
Ok, if anybody comes across this thread looking for answers -- I did successfully use Odin to get this firmware back onto the device. Upon booting, I had Safestrap, was able to boot Slot1, and had root. When I boot from the Stock slot, still no root.
I have not yet attempted to restore the Stock slot backup, because I first want to see if I can boot Slot1 (to get root), and then find/mount the Stock slot image and see if I can find a way to re-root it manually.
Click to expand...
Click to collapse
Using any other slot other then stock is going to be problematic. So use the stock slot. You are using the nc2 firmware if you have the reboot to recovery bootloop issue. You can flash the nc4 patched firmware in beans firmware thread if you want. Reboot to recovery is not the same as reboot to safestrap. Download a fresh rom. Wipe everything but external sd under the advanced wipe button in safestrap. Flash your new rom making sure stock slot is the active slot. Setup phone like normal. Make a backup with your now freshly setup rom. Rinse and repeat for new roms. Label your backups if you want to rom jump. Always use stock slot. Odin the nc2 kernel if you have a blackscreen on first boot of a new rom.
RomsWell said:
Using any other slot other then stock is going to be problematic.
Click to expand...
Click to collapse
In my case, Slot1 is simply a rooted ROM that I can use when the Stock slot gets messed up. I have no desire or intent to tinker with Slot1. I consider it as an emergency tool only. It does seem to have an issue though. It never seems to want to power all the way down for some reason.
RomsWell said:
So use the stock slot. You are using the nc2 firmware if you have the reboot to recovery bootloop issue. You can flash the nc4 patched firmware in beans firmware thread if you want. Reboot to recovery is not the same as reboot to safestrap.
Click to expand...
Click to collapse
I am using the NC2 firmware, but I no longer have the bootloop problem. After using Odin to re-install the NC2 firmware from BeansTown, the device was once again able to boot to Safestrap. From there, I was able to select and boot either of the existing slots. Slot1 still boots to root, Stock slot is still unrooted. I should be able to use Safestrap to restore my Stock slot backup and regain root on Slot1, right?
The only reason I have not yet attempted to restore the Stock slot backup is because I hope to boot my rooted Slot1 ROM, mount the Stock ROM image, and fix the Stock ROM image. If not, then I will try to restore the Stock slot backup.
RomsWell said:
Download a fresh rom. Wipe everything but external sd under the advanced wipe button in safestrap. Flash your new rom making sure stock slot is the active slot.
Click to expand...
Click to collapse
I definitely plan to flash a new ROM, soon. I want a fresh clean ROM for personal use, and I also need to find a ROM that supports HDMI -- because I want to get Debian to display on a larger screen. My ultimate goal is to create my own ROMs. I have a bit of experience with kernel tweaking/building, and created a bootable Linux-based DVD image by hand. I believe I will someday be able to tweak phone ROMs as well, but I'm still fuzzy about much of the Android system. Stuff like locks and KNOX seem like quite a mine field and make me very nervous. A blank DVD coaster is one thing, an expensive smartphone is scary.
lintex said:
In my case, Slot1 is simply a rooted ROM that I can use when the Stock slot gets messed up. I have no desire or intent to tinker with Slot1. I consider it as an emergency tool only. It does seem to have an issue though. It never seems to want to power all the way down for some reason.
I am using the NC2 firmware, but I no longer have the bootloop problem. After using Odin to re-install the NC2 firmware from BeansTown, the device was once again able to boot to Safestrap. From there, I was able to select and boot either of the existing slots. Slot1 still boots to root, Stock slot is still unrooted. I should be able to use Safestrap to restore my Stock slot backup and regain root on Slot1, right?
The only reason I have not yet attempted to restore the Stock slot backup is because I hope to boot my rooted Slot1 ROM, mount the Stock ROM image, and fix the Stock ROM image. If not, then I will try to restore the Stock slot backup.
I definitely plan to flash a new ROM, soon. I want a fresh clean ROM for personal use, and I also need to find a ROM that supports HDMI -- because I want to get Debian to display on a larger screen. My ultimate goal is to create my own ROMs. I have a bit of experience with kernel tweaking/building, and created a bootable Linux-based DVD image by hand. I believe I will someday be able to tweak phone ROMs as well, but I'm still fuzzy about much of the Android system. Stuff like locks and KNOX seem like quite a mine field and make me very nervous. A blank DVD coaster is one thing, an expensive smartphone is scary.
Click to expand...
Click to collapse
As long as you stick to the known exploits like safestrap and towelroot then theres no worrys about knoxs. And no real way to perma brick the device. Make sure you stick to offical firmware when using odin and abuse your device like you would any other.