Hey everyone. Im relatively new to this forum and rooting. I have some background knowledge in programming and other related aspects, unfortunately nothing related to Android. As well as some Linux OS experience. Now as far as i know ROM's could be compared to OS builds. Android 4.1.2, 4.3, 4.4, etc. Rooting makes you a super user/sudo like Linux. I think i have that pretty much correct. Now for the things i know little about.
-KNOX so far it seems its mostly used for enterprises and to see if we have installed a custom ROM. I've seen a lot of different information about Knox. What exactly else does it do/change? As of 4.3 i see we could no longer roll back or we will brick our device. What should i be wary of? I could care less about tripping the knox counter.
-Stock OTA is another thing i was curious about. This simply means an update was installed post factory by user, correct? My girlfriend has an S3 and i cant remember if 4.3 was stock or 4.1.2. I just wanted to clear up if my OTA updated S3 was covered under this.
-i saw one root method which kept the stock recovery but installed the superuser. What is the benefit for having a stock recovery? Would i be able to use a custom one with Knox in place? I was thinking of using a 4.4 cyanogenmod rom.
Sorry if this seems a bit noobish, but my schedule is tight and i spent maybe 6 hours trying to find exact information. Kind of hidden lol.
I appreciate any answers!
Sent from my SPH-L710 using xda app-developers app
All your questions are probably answered here-http://forum.xda-developers.com/showthread.php?t=2541343- read the whole thing and let us know if you have anymore questions
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And to answer some if them.
There is no advantage to stock recovery, you can't do anything with it.
Yes you can do anything the same with Knox but installing a custom recovery triggers the warranty bit in Knox. If you bring in your phone to be repaired or something, if they put the phone in Download Mode they could tell whether you installed a custom recovery because Warranty Bit would say 1 instead of zero. There's also no way to reset the flash counter with Knox.
And the biggest thing, if you have Knox do not try to downgrade the firmware. Aka don't try to Odin anything other than 4.3+. It will brick your device.
Other than those things it won't effect you at all.
And yes an OTA is Over The Air update. When the device scans for firmware updates and it find one it automatically downloads it and persistently bugs you about it until your firmware is the most current version. Done by the user or sometimes the techs at phone stores like to do it without asking you.
So to clarify (at work, ill read your link, appeciate it) Knox wont affect anything BUT the counter and downgrading? So i could root the old way with odin and cwm for 4.1.2 without problems?
Stock recovery is just worse in general or similar? Lastly "stock" ota is what i meant lol. I guess that means a non-custom ROM from your carrier?
I personally dont care for my warranty, i have a few months left in my contract and could upgrade now to a new phone if i wanted.
Thanks. I hate to sound like i did no research, i appreciate the link.
Sent from my SPH-L710 using xda app-developers app
Related
so i recently started having wifi issues with a few roms. i flashed back to stock with odin, and my wifi wouldnt turn back on. i made 2 threads about this issue in Q & A, and they were left without help (i provided info for people but they never responded)
i searched the forum, and found how to un-root my phone. on the first try, my wifi actually tuurned on for about 2 minutes, but then it went back to not turning on, and all the info on the phone said custom. i finally got everything to say samsung official, official, and all that.
so should i send it back for samsung to fix? and would they fix it, if they find everything on official? i had to resort back to my old iphone 3g which is a drag and i want to use my wifi on my s4 again...
BTW, everything else on the phone works except bluetooth, and i used the method in this thread >> http://forum.xda-developers.com/showthread.php?t=2336392
If everything is saying "Official" there's no need to be worry! :cyclops:
I don't know what could it be...
Sent from my
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Yes, send it back. It's probably a hardware issue.
Sent from my SGH-M919 using Tapatalk 4 Beta
Samsung openly admitted that this was a problem. There are ways to fix your issue u just have to look for it I forgot where. But I'm about to give my phone back ad well this is ridiculous
Sent from my SGH-M919 using xda app-developers app
Regarding returning your device, making sure everything is returned to stock is very important as you mentioned.
After you're done restoring your device to outta box set up with ODIN by installing the Samsung Stock Firmware tar, you want to remember to check the following:
- use Triangle Away by Chainfire to reset the bootloader to 0
The above has to be completed while you're still Rooted and you need the stock Kernel.
Read the TA thread so you know exactly what to do, if you didn't already.
After using Triangle Away, make sure everything is set tosstock.
In addition, TA doesn't change the Modified/Custom description in About deviceiin Settings. Only ODINing to Stock will.
- ODIN to stock
- check the Bootloader to make sure it doesn't say Custom and is set to 0 (mentioned above)
- boot into Recovery and make sure it's the stock recovery.
- check Device settings, About device and make sure it doesn't say Modified or Custom
If all the above checks out, you should be good to go
The above is a little checklist so that Samsung doesn't deny servicing your device and void your warranty
Thank you guys for all your feedback.
I just called t-mobile, and they said its a hardware issue, which i already kinda figured out. They are sending me a brand new s4, but i have to send my current s4 back to samsung. Like you guys said, it should be fine if everything says official, samsung official, etc., right? i also used triangle away to make sure the counter was at 0, or however it is supposed to be stock, and also did a factory reset again
Thank you, guys!
cucaz24 said:
Thank you guys for all your feedback.
I just called t-mobile, and they said its a hardware issue, which i already kinda figured out. They are sending me a brand new s4, but i have to send my current s4 back to samsung. Like you guys said, it should be fine if everything says official, samsung official, etc., right? i also used triangle away to make sure the counter was at 0, or however it is supposed to be stock, and also did a factory reset again
Thank you, guys!
Click to expand...
Click to collapse
Great to hear :good:
Glad we were able to help ya out!
Go over the checklist again for good measure
If you used triangle away properly, and everything says stock,you should be good to go.
I just got a used E980. idk what he's done to it. but appeared vanella. I tried rooting, from the proper thread with the right files. suposedly right for the e980. so I tried to just reboot recovery, but all i get is an android with a red triangle and an ! inside it of.
the error i get when trying to root is -
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If it's a custom Rom it's already rooted (obviously). Check the build version in your settings.
cougar214 said:
If it's a custom Rom it's already rooted (obviously). Check the build version in your settings.
Click to expand...
Click to collapse
yeah i can't get into TWRP, or the other one. it keeps giving me dude with red !. version is jz054k.
I did a full wipe and install of an origonal build of the software, was able to root it sucesfully now. but still can't get into the bootloader menu. tried cammand line to tell it to boot into it, tried rom manager. no dice. just keep getting little dude. i remember seeing a thread about him, i don't know what he means :\
The bootloader on these phones are locked. You are able to install the custom recovery only because Freegee can bypass the bootloader.
cougar214 said:
The bootloader on these phones are locked. You are able to install the custom recovery only because Freegee can bypass the bootloader.
Click to expand...
Click to collapse
yeah i got around it and managed to do it. didnt much like the rom, know any clean roms that are more stock like? i really didnt mind stock. but i want 4.4 or better than stock.
Honestly, your best option is to wait for the kitkat update to hit in a month or so. You get what you're looking for in one stock update. Hassle free. That's what I'm doing. The more I learn about this phone, the more I am hesitant to flash anything to it. Mostly because there are so many variants for this phone. Everything can't be compatible so why risk it.
eviling said:
yeah i got around it and managed to do it. didnt much like the rom, know any clean roms that are more stock like? i really didnt mind stock. but i want 4.4 or better than stock.
Click to expand...
Click to collapse
This http://forum.xda-developers.com/showthread.php?t=2703029
Read the whole thing then you'll be ready to go
Its the kitkat Korean update, I'm using it on my e980 , pretty sweet
yeah i agree, i havn't found many rom's i like. ive found roms always fail after awhile. so idk. they always bloat up and start to fail than they need the update to be stable blah blah than your reinstalling all apps and backing **** up. idk, was just looking at what phones offer these days for modding but nothing seems to of changed. this phone inparticular is a rather unstable device none stock, seems to be allota issues and a good reason to have bootloader locked.
Un locking the bootloader only allows for custom kernels on any given device. In some cases you will get greater stability. But for the most part you will still have glitches, performance decreases, etc. because you are STILL flashing custom Roms. And in allot of cases your phone will go completely nuts because custom kernels have their glitches too. So in short, sometimes, Custom Rom=glitches. custom kernel=glitches. That all adds up to a totally unstable Rom. Keep in mind all devices are not the same. What runs great on his might crash your phone completely. Just my 2 cents....lol
Just curious why KNOX is so awful to everyone.
Does it prevent root altogether?
Does it prevent custom ROMs from being installed?
Does it only prove to Samsung that you have messed with your phone and broken your warranty?
All honest questions: please be gentle.
magnamagna said:
Just curious why KNOX is so awful to everyone.
Does it prevent root altogether?
Does it prevent custom ROMs from being installed?
Does it only prove to Samsung that you have messed with your phone and broken your warranty?
All honest questions: please be gentle.
Click to expand...
Click to collapse
No
No
Yes
And prevents downgrading firmware... That's it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
magnamagna said:
Just curious why KNOX is so awful to everyone.
Does it prevent root altogether?
Does it prevent custom ROMs from being installed?
Does it only prove to Samsung that you have messed with your phone and broken your warranty?
All honest questions: please be gentle.
Click to expand...
Click to collapse
KNOX is so awful because many people don't realize they already have it. Then when trying to fix a semi brick, they flash the wrong tar file that downgrades the bootloader. BRICK!
sent from my GS3
Thanks for the info.
I don't care about my warranty; my cracked screen will probably prevent any warranty claims from happening anyway.
What do you look for to make sure that you are flashing to the same firmware?
magnamagna said:
Thanks for the info.
I don't care about my warranty; my cracked screen will probably prevent any warranty claims from happening anyway.
What do you look for to make sure that you are flashing to the same firmware?
Click to expand...
Click to collapse
Settings/More/About Device. Mostly whatever you firmware you flash, you can't go back from that.
magnamagna said:
Thanks for the info.
I don't care about my warranty; my cracked screen will probably prevent any warranty claims from happening anyway.
What do you look for to make sure that you are flashing to the same firmware?
Click to expand...
Click to collapse
One of the main things one has to be careful with when Knox'ed up is the bootloader. Once you have a Knox bootloader, you can't flash any ROM that will overwrite with a non-Knox bootloader, or flash back to a pre-Knox stock bootloader.
Sent from my SPH-L710 using Tapatalk
Since knox is inevitable, I am going to take a few moments to see if it is useful. I want to experience if enterprise email and calendar apps will be beneficial rather than using outlook web app.
I will eventually root the device which I believe will break knox. I understand there is no way to hide root from knox since it would defeat the purpose. Does anyone know if there is any way to go back after knox detects root. Does going back to stock allow knox to work again.
Sent from my SPH-L710 using XDA Free mobile app
biggolfer said:
Since knox is inevitable, I am going to take a few moments to see if it is useful. I want to experience if enterprise email and calendar apps will be beneficial rather than using outlook web app.
I will eventually root the device which I believe will break knox. I understand there is no way to hide root from knox since it would defeat the purpose. Does anyone know if there is any way to go back after knox detects root. Does going back to stock allow knox to work again.
Sent from my SPH-L710 using XDA Free mobile app
Click to expand...
Click to collapse
Once KNOX has been tripped, you no longer have protection through KNOX. None of the KNOX security apps will work and there is no way back.
Sent from my SPH-L710 using Tapatalk
I recently got my S6 back from Samsung. They untripped knox, and installed a very slim rom without any of the sprint bloatware, and no sprint splash screen. Is there some way I can back up this rom to be able to flash it in odin if/when I need to?
Thanks!
TWRP
bert1983 said:
I recently got my S6 back from Samsung. They untripped knox, and installed a very slim rom without any of the sprint bloatware, and no sprint splash screen. Is there some way I can back up this rom to be able to flash it in odin if/when I need to?
Thanks!
Click to expand...
Click to collapse
You can back up everything if you flash TWRP recovery and select the backup option it comes in hand but other than that i dont believe you can do it without tripping Knox again
Thanks for the reply, that's unfortunate news. I really don't feel like tripping Knox since I would like samsung pay to continue working.
bert1983 said:
Thanks for the reply, that's unfortunate news. I really don't feel like tripping Knox since I would like samsung pay to continue working.
Click to expand...
Click to collapse
You can try ADB Backup. A good set of instructions can be found at:
http://forum.xda-developers.com/galaxy-nexus/general/guide-phone-backup-unlock-root-t1420351
No guarantee that this will work, but it should not trip Knox.
Please post a system dump of this b3fore you do anything. PLEASE
Sent from my SM-G925P using Tapatalk
Is it oi1 build ? Ive sent plenty phones back for warranty and samsung never did that before . Trip knox , so what? Samsung warrantys phones like that all the time . Just tell them you took it to the samsung experience shop at "BestBuy" and they tried to flash the operating system to get the phone working properly again. Id tell them it kept rebooting after you updated it through wifi to 5.1.1 . Youll never have an issue with them if you explain it to them that way . Give us a new build lol
bert1983 said:
They untripped knox....
Click to expand...
Click to collapse
That's the real goal there....
OK I'll work on it this week. I don't want to not be able to use the Samsung pay feature though
I am curious if its the same build number as mine, I have this screenshot so tell me is yours the same or different? Mine is Stock Sprint
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
MindTrix said:
I am curious if its the same build number as mine, I have this screenshot so tell me is yours the same or different? Mine is Stock Sprint
Click to expand...
Click to collapse
That's the same build I have after updating my device. Have you had any luck rooting yours yet?
Sent from my SM-G920P using Tapatalk
gimmeitorilltell said:
That's the same build I have after updating my device. Have you had any luck rooting yours yet?
Sent from my SM-G920P using Tapatalk
Click to expand...
Click to collapse
I have yet to Root the phone, been waiting and think I will try soon, as I might not need Samsung Pay, been playing with Google 's " Android Pay " not sure what if I will even use these services, I might just root now... LOL
So last week my note started to receive the networksystemprovider error and the only way I can get it to stop popping up every 5 seconds is to freeze it, but then I cannot receive any text. So I was hoping to just update the phone but it has been so long since I did anything to it I am very confused on how.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is what my phone is currently running and I do have TRWP installed. Any help would be greatly appreciated. Thanks
Sent from my SM-N910P using Tapatalk
What are you currently running? Stock rooted OG5 with initial release of Beastmode?
You should remove ItsOn if running custom kernel- unless you know how to remove it. I've seen ItsOn try to repeatedly to activate itself- but can't with custom kernel. It prompts or forces reboots with no end after the user factory resets in recovery when leaving fragments of ItsOn in internal memory.
I don't know what you want to do but there's many choices:
If you're looking for customization on lollipop, checkout Moar 2.1b One day marshmallow will have a ported ROM of this caliber or better.
If you're looking for stability and maybe something a bit faster, try a marshmallow custom ROM.
Just a couple of examples. Find a ROM and follow the OP install instructions closely. That most likely means using the stock tar flash in Odin to update to suggested update and turning off automatic updates before the update nag starts. But don't go back any farther than OG5 with Odin; the bootloader won't allow the older stock tars to flash.
I was actually to go to stock marshmallow but with root like I have know. I have never been really into trying all the different roms I just want to have root for the Hotspot. I tried to look through the thread but I just get more confused.
Sent from my SM-N910P using Tapatalk
swiftyfrommi said:
I was actually to go to stock marshmallow but with root like I have know. I have never been really into trying all the different roms I just want to have root for the Hotspot. I tried to look through the thread but I just get more confused.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Which thread is confusing? Hotspot, update and root (aka stock tar thread in general forum) or custom ROM threads?
Which hotspot method are you using or prefer? I believe the non root method requires a do over on each boot. Don't use much at all but I prefer permanent myself for the other benefits custom services.jar provides.
That network error is caused by ItsOn not being fully removed and the custom kernel not supporting it. If you use stock kernel, you could leave ItsOn intact but some consider it a privacy and battery liability: unneeded bloat and potentially problematic.
Sent from my SM-N930P using Tapatalk
http://forum.xda-developers.com/showthread.php?t=2941853
This is how I got the Hotspot to work. So all I need help with is updating from lollipop to stock marshmallow. Is it just downloading the rooted stock marshmallow and use Odin to install?
Sent from my SM-N910P using Tapatalk
swiftyfrommi said:
http://forum.xda-developers.com/showthread.php?t=2941853
This is how I got the Hotspot to work. So all I need help with is updating from lollipop to stock marshmallow. Is it just downloading the rooted stock marshmallow and use Odin to install?
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Yes.This thread should get you started with that.
http://forum.xda-developers.com/showthread.php?p=63868221
Sent from my SM-N930P using Tapatalk