Okay guys. Here we go. I screwed up the other day while trying to load a custom ROM following a friends instructions. I tripped Knox on my Verizon Note II 4.3 and was forced to downgrade to 4.1.1. My phone is no longer rooted and I am trying to figure out how to root from 4.1.1 with a locked bootloader and then use safestrap to install custom ROMs. Sadly I cannot find any info anywhere after several hours of searching. I've read up on Knox and I could care less about warranty info (I bought the phone used after all) and I just want to be able to load custom ROMs so I can better enjoy my phone while being able to restore APN settings since I am running on a non-Verizon carrier service. Please help!
Edit: I used RootChecker to make sure that my phone is no longer rooted after downgrading to 4.1.1
Edit: Fixed with Kingo Root
Related
hey guys, so im sure many have tried to put cyanogenmod on a VZW Samsung Galaxy s III with 4.4.2 OTA on it. but couldnt. im really looking to put CM11 on it. im very much so new to rooting, and flashing roms, but i already rooted my device, and flashed the stock firmware back, due to not having a CWM back up and getting "system software not authorized by verizon" warning.
so my question.
can i downgrade my firmware from 4.4 to earlier to have an unlocked bootloader without bricking it? do i need to go to 4.3 and then 4.1.2?
because before 4.3 it had an unlocked bootloader.
I really want CM because i cant stand touchwiz anymore. thanks guys . help a newb out
oh and. should i use towel root? or another rooting method
Your now on the locked bootloader and you cannot downgrade to another firmware. You can root with towelroot but that's truly about all you can do
From my CM11 S3
I own a Samsung Galaxy S5 and I want to root to get full functionality from the device. I have read several root guides but they seem to be very old. Things like Towelroot I have read doesn't work anymore.
So if someone can give me a link or post and effective and up to date guide for rooting would be great.
I also have a few questions about rooting.
1. I have heard that some roots trip Samsung Knox so I need a root that wont do this
2. What does the Knox flag 0x1 actually do to the device other than void warrenty? I have heard it permanently disables Samsung services for the phone/tablet like Kies and adds warnings to the boot screen, but I don't know if this is true.
3. I want to get Android updates for security and such, will a small update cause unroot? (I will also upgrade to Android 6.0 if/when its available for the S5 and I know upgrade will unroot)
If there is a chance of tripping Knox I will not root. I also want to be able to return the phone back to exact stock software, settings and flags as before it was rooted if I choose to.
Phone info:
AT&T S5
Model: SAMSUNG-SM-G900A
Android version: 5.1.1
Baseband version: G900AUCU4COI5
Kernel version: 3.4.0-5869384
KNOX version
KONX 2.5
Standard SDK 4.5.0
Premium SDK 2.5.0
ect...
Don't root!!
I've got the same problem as you brother. I've got the same phone specs. I think we are out of luck right now. Attempting anything is probably a really bad idea.
But I second this call for help, I'm curious to know if there is anything that can be done.
@Woogoo as of now you can't root the AT&T S5 latest OS so don't try...
So question.. Can I use Xposed Framework on my Verizon Galaxy S III without tripping KNOX and bricking my phone or is that one of the things I can't do because I can't flash custom roms n such?
Phone is running Android 4.4.2
Model number is SCH-I535
If I can use Xposed then is there anything I should be careful about and not touch / do?
Any feedbk??
Dimmizer said:
So question.. Can I use Xposed Framework on my Verizon Galaxy S III without tripping KNOX and bricking my phone or is that one of the things I can't do because I can't flash custom roms n such?
Phone is running Android 4.4.2
Model number is SCH-I535
If I can use Xposed then is there anything I should be careful about and not touch / do?
Click to expand...
Click to collapse
I don't know much about Knox, I deleted anything that looked related to it from my phone that I Was able to, and last I checked with a program that is supposed to give you a status of knox it just throws an error that I believe means it can't tell the status.
Anyway, I have Xposed running without issue on my phone, same phone, same stock android (Although rooted and cleaned up the best I could) without issue. Running modules like APM+, EnableCallRecording, and Wanam Xposed.
I was running Xposed on my i535 with the 4.4.2 bootloader and modem installed. I bought the phone used last May with no intent of using it as a phone. I wanted it to learn more about modding. It was already on the 4.4.2 Stock ROM. At that point I started reading the i535 forums and learned of the limitations of my "new" device. After reading for a week I rooted with towelroot, installed busybox, installed safestrap and then flashed one of the two ROMs usable on this device. It worked well for four months. I lent it out to a friend and it was returned unbootable. I will probably be able to restore the device since I can get to download mode and the stock recovery.
I don't know if this changed my Knox/warranty bit status. I'm not concerned since the device is well out of warranty and I am not the original owner. It didn't change the performance or battery life of the phone. My understanding is that Knox is to run secure corporate apps to protect data, something I will not be doing. So, I wouldn't be concerned if I were you unless your worry is that it may affect resale.
Which Xposed Framework version did you use?
" I was running Xposed on my i535 with the 4.4.2 bootloader and modem installed. It was already on the 4.4.2 Stock ROM"
I have a Towelroot rooted Verizon GS3 i535 and want to install xposed framework but everything I read is 2 years old and version for Kit Kat 4.4.2 is experimental. I'm on a stock rom. So now in June 2016, which stable version should I install? My rom is touchwiz and build NE1 if that helps.
I read warnings that installing on a Samsung modified rom will result in a bootloop and that is a show stopper for me.
Also confused about version numbers. 2.7 is download file number V33. I can't find a list showing which version numbers go with which file numbers.
Many Thanks!
Not much activity on the AT&T sub forum so I'm here for help if possible.....
I rooted my AT&T S6 when I first got it 2 years ago and haven't messed with it since. Still running CleanRom 1.1-OE2 5.0.2 baseband AOE2 ......
I also have another ATT S6 thru work. It's all stock, no root unfortunately. It was recently updated to 7.0 and got the itch to update my personal S6 to a more modern version of Android but don't want to loose root.
Is it possible to update to a version of Android 6 or 7 and keep root since my phone is already rooted and running an old kernel etc.... ????
I guess I'm not really worried about voiding the warranty and/or tripping knox or whatever, since I've had the phone 2yrs I believe all factory warranty has expired right?
Remember it's been a while (almost 2yrs) since I've hacked on a phone so I'm a newb again lol!
Any help is appreciated.
There's no way to use 5.1.1,6.0.1 and 7.0 with root on SM-S920A
And you can't trip the knox counter on SM-G920A
I'm new to posting to these forums, so forgive me if i don't add the right tags or do something right...
Anyway, I was given a TMobile Galaxy S6 as a hand-me-down phone from my family, and wanted to know what was the best way to root the device. I don't really care if i trip Knox, but i'd like it to be unnoticeable, and i'd love to not trip it at all, if possible. I don't want to have an "Unlocked" sign everytime i bootup. I want to be able to run Vanilla Oreo (or close to it) without touchwiz as the phone has been getting laggy, and since i already have another Rooted Device, it's not laggy when running Resurrection Remix, which i'll probably end up running that ROM on this phone as well. I've heard the TMobile version has a Bootloader unlock, but i'm not sure how to go about doing that without bricking the device. The reason i'm asking is because the last Samsung device i had, a Galaxy S5, was bricked for a number of months before i was able to flash stock again using a SD Card, and i don't want to have to go through that again with this phone. Should i just follow this tutorial? or is there a better way to flash without tripping Knox? I know how to root & BL Unlock, i've done it on a number of close-to-stock devices, but Samsung devices are a whole 'nother world of trouble that i don't even know how to deal with.
Device: T-Mobile Samsung Galaxy S6 - SM-G920T
Running: Android 7.0
Build Number: NRD90M.G920TUVU5FQG3
Baseband Version: G920TUVU5FQG3
I have the same phone ,first go to developer option and allow iem unlock ,reboot to odin and flash cf auto root (choose the one for your modele and os exactly) then reboot