I bought a samsung gt-i9500 yesterday with the original software on it and decided to to upgrade with kies to the latest version 4.4.2. I then proceeded to try and obtain root via kingo which takes and keeps failing after a while. Tried towel root -device not supported possibly because of a updated kernel release with the latest upgrade. Anyway i thought after playing around go see if i tripped the knox flag.....indeed i did. Status also changed to custom. Tried downloading super su chainfire for the time that the root actually works before failing......made kingo user crash. Restarted my device and my statust changed back to OFFICIAL and knox flag 0x0........thought i share this with you guys.
I know 100% for fact that the phone is Spark enabled. I did a stock update to Lollipop once and had great Spark signal on my device. I hate Lollipop and my apps that require root access do not function on Lollipop.
I am wondering what I need to do in order to access Spark LTE again. I am using a 4.4.4 stock rom that is rooted via TWRP and Super SU. I don't recall exact versions and such as I have been using the same stock rom for a year now.
I recently retried 5.0/5.1 and my rooted apps still have issues, so I do not want to use Lollipop.
Is there a modem file I need to change to be able to get Sprint Spark? I had it before also on 4.4 when the phone was 100% stock and I did the official update to 4.4 from 4.2 or 4.3(been a year).
The phone was bought out, no longer under warranty as of November, and Knox already tripped so I don't care about any of that. The phone was manufactured Sept/Oct 2014 if that helps.
Any suggestions?
Mplode said:
I know 100% for fact that the phone is Spark enabled. I did a stock update to Lollipop once and had great Spark signal on my device. I hate Lollipop and my apps that require root access do not function on Lollipop.
I am wondering what I need to do in order to access Spark LTE again. I am using a 4.4.4 stock rom that is rooted via TWRP and Super SU. I don't recall exact versions and such as I have been using the same stock rom for a year now.
I recently retried 5.0/5.1 and my rooted apps still have issues, so I do not want to use Lollipop.
Is there a modem file I need to change to be able to get Sprint Spark? I had it before also on 4.4 when the phone was 100% stock and I did the official update to 4.4 from 4.2 or 4.3(been a year).
The phone was bought out, no longer under warranty as of November, and Knox already tripped so I don't care about any of that. The phone was manufactured Sept/Oct 2014 if that helps.
Any suggestions?
Click to expand...
Click to collapse
i dont know specifically how to fix your issue, but im betting if you look in your devices general forum, you will find a thread with all the available modems. you may have to try a couple until you figure out which one is correct for your version, if its not noted.
Since there is still no root method above 5.1.1, perhaps I should make a thread for ideas on rooting the Samsung Galaxy S6 6.0.2 and higher
I was thinking of editing default.prop in the ramdisk so I can gain root access since this is what I am hearing.
ro.secure is like root without the need of ADB
ro.debugging is root but you need ADB.
And then attempt to install su and superuser
I've seen someone on 6.0.2 on root checker saying they have root their S6 but it was hard to get root. So I am guessing he edited default.prop in the ramdisk.
That's all I am thinking, might think wrong or stuck in the past, but what do you guys think on what might get root access? I actually need ideas on what can get root access to the S6
AndroidFan16 said:
Since there is still no root method above 5.1.1, perhaps I should make a thread for ideas on rooting the Samsung Galaxy S6 6.0.2 and higher
I was thinking of editing default.prop in the ramdisk so I can gain root access since this is what I am hearing.
ro.secure is like root without the need of ADB
ro.debugging is root but you need ADB.
And then attempt to install su and superuser
I've seen someone on 6.0.2 on root checker saying they have root their S6 but it was hard to get root. So I am guessing he edited default.prop in the ramdisk.
That's all I am thinking, might think wrong or stuck in the past, but what do you guys think on what might get root access? I actually need ideas on what can get root access to the S6
Click to expand...
Click to collapse
This guy you've heard has root on 6.0.2 is on the G920V right, also seems interesting, do you think you could link this image, or original posting or whatever?
If Root Checker has an option to contact the person that rooted 6.0.2, I would do it, but I can't. That's why I made the "Rooting Ideas"
Also, I have the feeling that since PC2 can be downgraded to OK7, it might have the same bootloader. So technically were not far from root for marshmallow.
You can check in root checker. Cause that's were I found someone that rooted the verizon S6
AndroidFan16 said:
If Root Checker has an option to contact the person that rooted 6.0.2, I would do it, but I can't. That's why I made the "Rooting Ideas"
Also, I have the feeling that since PC2 can be downgraded to OK7, it might have the same bootloader. So technically were not far from root for marshmallow.
You can check in root checker. Cause that's were I found someone that rooted the verizon S6
Click to expand...
Click to collapse
Ok, after I flash again (FLASHFIRE WORKS!, too bad it is pretty much useless now..., may have soft bricked it again XD) Working with Rooted 5.1.1, and it is quite crap... the battery life is maybe 3 hours max, and everything is SLOW!
THINGS I'VE TRIED:
Flashing 5.0.2 via Flashfire - FAIL
Flashing 5.0.2 via Flashfire, then flashing custom sboot - FAIL
SuperSU-MEing Kingroot in 5.1.1 - Kind of....*
Flashing PC2 Firmware (MM), With Everroot Enabled FAIL**
THINGS I NEED TO TRY:
Flashing Custom SU (or Custom VZW S7 SU) via FlashFire
Waiting For ROMS for the Eng-Kernal....
That Is All The Info I Have
*SuperSU works, but bootloops on reboot...
**Stuck at Screen BEFORE BOOT LOGO
(Where is says Powered By Android at the bottom)
---------- Post added at 03:04 AM ---------- Previous post was at 02:46 AM ----------
AndroidFan16 said:
If Root Checker has an option to contact the person that rooted 6.0.2, I would do it, but I can't. That's why I made the "Rooting Ideas"
Also, I have the feeling that since PC2 can be downgraded to OK7, it might have the same bootloader. So technically were not far from root for marshmallow.
You can check in root checker. Cause that's were I found someone that rooted the verizon S6
Click to expand...
Click to collapse
HOLD UP! The S7 SuperSU binary!
What About In FlashFire
WIPE, FLASH PC2 (MM FIRMWARE), FLASH VZW-S7 SU BINARY, REBOOT
Maybe, Just Maybe...
Mnky313 said:
This guy you've heard has root on 6.0.2 is on the G920V right, also seems interesting, do you think you could link this image, or original posting or whatever?
Click to expand...
Click to collapse
Mnky313 said:
Ok, after I flash again (FLASHFIRE WORKS!, too bad it is pretty much useless now..., may have soft bricked it again XD) Working with Rooted 5.1.1, and it is quite crap... the battery life is maybe 3 hours max, and everything is SLOW!
THINGS I'VE TRIED:
Flashing 5.0.2 via Flashfire - FAIL
Flashing 5.0.2 via Flashfire, then flashing custom sboot - FAIL
SuperSU-MEing Kingroot in 5.1.1 - Kind of....*
Flashing PC2 Firmware (MM), With Everroot Enabled FAIL**
THINGS I NEED TO TRY:
Flashing Custom SU (or Custom VZW S7 SU) via FlashFire
Waiting For ROMS for the Eng-Kernal....
That Is All The Info I Have
*SuperSU works, but bootloops on reboot...
**Stuck at Screen BEFORE BOOT LOGO
(Where is says Powered By Android at the bottom)
---------- Post added at 03:04 AM ---------- Previous post was at 02:46 AM ----------
HOLD UP! The S7 SuperSU binary!
What About In FlashFire
WIPE, FLASH PC2 (MM FIRMWARE), FLASH VZW-S7 SU BINARY, REBOOT
Maybe, Just Maybe...
Click to expand...
Click to collapse
It could work though
Since the verizon S7 users are in the same boat as us
I really hate lollipop. Its soooooooooo slooooooooowwwwww. So I want to see if we can try to get the S7 SU binary asap before my phone gets more slower :crying:
Tried to root 6.0.2 with Easy One-Click tool on the forum for tests and giggles. Gave me a bootloop.
I've researched multiple rooting tutorials and have found a lot of guides based on the auto-root file from www(.)autoroot.chainfire(.)eu
However, I still do not know what to do with this. From my research I found out that there is a possibility that the bootloader is locked and that is the reason I am scared, if I brick this phone I will not have a phone for another 2 years. If I flash a new clear android 7.0.0 stock for the S6 without the O2 addon bloatware with the bootloader locked it will brick my phone since this is some sort of security feature.
What I want from my S6:
- VERY good security, I will be banking on it alot, using android pay, etc so I need it to basically be hack-proof etc. Im not going to install apps like lucky patcher which are not from the play store.
- A new clean stock version of Android 7.0.0 without so many O2 apps that I cannot uninstall.
- Root access to remove certain system services and increase my battery life
I am a previous root user, 1 year ago being on my rooted S3 which I rooted using KingoRoot with one click. Now I come back year later to a new phone 3 generations down with things like the locked bootloader and KNOX. Could anyone explain what I can do at this point?
Phone specification essentials:
Name: Samsung Galaxy S6 O2/EU
Model Number: SM-G920F
Build Number: G920FXXU5EQE5
Android Version: 7.0
Knox Version: 2.7.1
The device still has a simlock, and I was told that the sim lock is installed in the ROM. So if I were to flash Im assuming the simlock would be removed however I still have a pending order for the unlock code coming in 7 days.
Try with a TWRP and a Magisk' - SuperSU it's a will be less-stable for now' (Seriously who are be use at This for now?)
Addition advantage it's a doesn't Permissives of a Magisk (Still "Enforced")
There aren't many new topics on this model so here we go,
My z3 stock came with 5.0.1 and as far as i know never (the 6616) had the 4.4 as an option. SO downgrading didn't work, so i'm stuck trying to root this with 5.0.1 and after two days of browsing this site there really doesn't seem to be a way to do so. Eventually i said $%#* it and rooted it using kingroot but after rooting it, root checker passed the root but would not give proper access when installing root apps such as busybox and the ta backup tool.
So i didn't realize that the keys ive been trying to save are useless anyways if i update android and the main reason for me going through this is i really don't like 5.0.1. Only thing i haven't really looked into doing is seeing if kingroot will let me unlock the bootloader then trying to flash an update. SO has anyone successfully updated a 6616 z3 (to 6) who didn't start off with 4.4?