Related
Hey guys, new member although I've lurked for a while. I have been searching up and down the last couple of days to find a way to get past KNOX and reroot my device. Me being kinda rustic and not thinking about it, accepted an OTA firmware update a few days ago. Of course I lost root access. What I didn't know about at the time was how big of a problem KNOX had become recently.Well, this firmware update introduced KNOX onto my device. I've heard stories of people being able to use Kingo and Saferoot on 4.2.2 and 4.3 after KNOX. This has not been the case with me, and I'm wondering if anyone has had success with this. Odin doesn't work either. I noticed that write protection is set as yes when in ODIN mode, and I suspect this is KNOX preventing changes to the ROM. As a result I haven't even been able to reflash the stock ROM image I have, whereas I have heard that you can reflash stock ROM's, but can't go backwards as far as version number. Thanks for your help in advance.
HansBlenkers said:
Hey guys, new member although I've lurked for a while. I have been searching up and down the last couple of days to find a way to get past KNOX and reroot my device. Me being kinda rustic and not thinking about it, accepted an OTA firmware update a few days ago. Of course I lost root access. What I didn't know about at the time was how big of a problem KNOX had become recently.Well, this firmware update introduced KNOX onto my device. I've heard stories of people being able to use Kingo and Saferoot on 4.2.2 and 4.3 after KNOX. This has not been the case with me, and I'm wondering if anyone has had success with this. Odin doesn't work either. I noticed that write protection is set as yes when in ODIN mode, and I suspect this is KNOX preventing changes to the ROM. As a result I haven't even been able to reflash the stock ROM image I have, whereas I have heard that you can reflash stock ROM's, but can't go backwards as far as version number. Thanks for your help in advance.
Click to expand...
Click to collapse
Flash anything with ODIN will trip the KNOX. Kingo is basing their root method on Saferoot, just with a GUI to make things simpler. And Saferoot should work with ROM that is before KK (4.4). If your OTA update is 4.4 than Saferoot won't work, since Saferoot is using a vulnerability prior 4.4 version. Does Kingo or Saferoot give any error message?
And just to double check, for both Saferoot or Kingo to work, you need to enable USB ADB and debugging mode.
TNCS said:
Flash anything with ODIN will trip the KNOX. Kingo is basing their root method on Saferoot, just with a GUI to make things simpler. And Saferoot should work with ROM that is before KK (4.4). If your OTA update is 4.4 than Saferoot won't work, since Saferoot is using a vulnerability prior 4.4 version. Does Kingo or Saferoot give any error message?
And just to double check, for both Saferoot or Kingo to work, you need to enable USB ADB and debugging mode.
Click to expand...
Click to collapse
Hey thanks for the reply. I do have USB ADB and debugging turned on. I've also tried reinstalling kies and the USB drivers them selves. I don't really care if an Odin flash trips Knox, as I don't think I have a warranty to worry about. The OTA update brought my firmware upto date , so I'm still on 4.2.2. This means that technically Saferoot or Kingo should work as advertised. This brings me back to the Write Protection set to Yes, and it's the only thing I could see preventing me from rooting my phone.
EDIT: Well I just found out that the Mini USB I use to charge my mouse started shorting other USB devices. Not like short then come back on, it was so bad every port on the computer shut down and I had to restart to get them working again. It was also the cable I was using to plug my phone in. Will update again when I try another cable.
EDIT 2: Just tried with the cable I usually use for charging my phone. No change on Kingo, still get a Root Failed, Need Root error.
HansBlenkers said:
Hey thanks for the reply. I do have USB ADB and debugging turned on. I've also tried reinstalling kies and the USB drivers them selves. I don't really care if an Odin flash trips Knox, as I don't think I have a warranty to worry about. The OTA update brought my firmware upto date , so I'm still on 4.2.2. This means that technically Saferoot or Kingo should work as advertised. This brings me back to the Write Protection set to Yes, and it's the only thing I could see preventing me from rooting my phone.
EDIT: Well I just found out that the Mini USB I use to charge my mouse started shorting other USB devices. Not like short then come back on, it was so bad every port on the computer shut down and I had to restart to get them working again. It was also the cable I was using to plug my phone in. Will update again when I try another cable.
EDIT 2: Just tried with the cable I usually use for charging my phone. No change on Kingo, still get a Root Failed, Need Root error.
Click to expand...
Click to collapse
At this stage I can only suggest to try on a different PC (use don't need Kies, just the Samsung driver will do) with a cable that your are 100% sure it working. If it still not working, my only guess is your network provider enable a looked boot loader in the OTA update you just did (hence the Write Protection flag). If that the case, nothing can be done at this point.
Same Boat
Im in the same boat did realize that KNOX would change so much. I need to reroot so hopefully someone can figure it out without tripping knox.
It fails because of the Security notice....Unauthorized access to a secured area has been blocked. Tap to learn more. If you notice when you check USB debugging, look below at Verify apps via USB. It is checked and grayed out. It isn't checked when USB debugging is off. I don't know how this was circumvented on the S4. But I'm peeved I let the update happen. They conveniently left out any info about security, and I'm tempted to return the phone and get one that hasn't been updated. Figure they weren't forthcoming about what the update contained so I can raise enough stink, get an old phone, download the update, pass it off to someone who can hopefully pull everything but the bootloader and create a tar to flash via odin. If that's possible and someone is willing to do it. If I had another spare line, I'd get another phone to donate for the cause.
I think if we're on Knox we need Odin to Root because anything that gets transferred via USB will be blocked. I even tried rootkeeper, and it was blocked.
The tough part is, unless it's a premium phone, it's not getting the level of dev support we're used to (well I'm used to...haha). Rooting through odin, custom recovery....used to taking it for granted. And with Sprint EOL'ing the phone, it's not really going to gain any momentum, though I did only pay 99 cents for it on a spare line. Kinda ticks me off Samsung has gone this direction when they used to be so dev friendly. Almost enough to make the S4 my last Samsung.
TNCS said:
At this stage I can only suggest to try on a different PC (use don't need Kies, just the Samsung driver will do) with a cable that your are 100% sure it working. If it still not working, my only guess is your network provider enable a looked boot loader in the OTA update you just did (hence the Write Protection flag). If that the case, nothing can be done at this point.
Click to expand...
Click to collapse
the concern is not tripping knox from the bootloader perspective. The problem is the knox security app that can't be removed without root. So for everyone that has OTA updated to NA7, going the odin route to root is the only option as far as I know. I know I don't care about tripping the counter. I just want control back of my phone. And the only way to do that at the moment is to return it for a pre knox version which I'm apt to do at the moment since there is a lack of development, and the ones that are developing don't even have the phone. Kudos to them, but there's not much help once you've updated to NA7. And unfortunately, the update doesn't tell you it's locking down your phone. Then you're stuck in a quandary, because the update also provides updates for Spark, so unless someone does a dump of the download and someone can pick it apart and provide a zip sans Knox, we'll have to deal with a stock phone.
dbpaddler said:
the concern is not tripping knox from the bootloader perspective. The problem is the knox security app that can't be removed without root. So for everyone that has OTA updated to NA7, going the odin route to root is the only option as far as I know. I know I don't care about tripping the counter. I just want control back of my phone. And the only way to do that at the moment is to return it for a pre knox version which I'm apt to do at the moment since there is a lack of development, and the ones that are developing don't even have the phone. Kudos to them, but there's not much help once you've updated to NA7. And unfortunately, the update doesn't tell you it's locking down your phone. Then you're stuck in a quandary, because the update also provides updates for Spark, so unless someone does a dump of the download and someone can pick it apart and provide a zip sans Knox, we'll have to deal with a stock phone.
Click to expand...
Click to collapse
I was (after a good bit of tinkering, and deleting my modem on accident) able to install CWM and flash a CW11 version s0be is currently developing, and it's working pretty well as far as I can tell. Unfortunately, due to the lack of support on this forsaken Sprint device, I haven't been able to find a modem I can flash onto the damned thing to get it working properly again. I don't advise the route I took, firstly because of the effort it took, but I also damned near bricked it about 5 different times, and needed to use a Linux VM. Also, because of the lack of developers on this thing, if you delete your modem and A: don't have a friend (brother in my case, has same phone) you can pull a modem.bin off of and B: don't know how to build that .bin into a working .zip or a flashable tar.md5 you might get stuck with an unusable device at the end of the day. Really, the only thing Knox has done for us is complicate things a hell of a lot more than they need to be. Although, tbh, that might (most likely) have been my stupidity that deleted the modem. In any case, check it (s0be's CM11 development) out, it's coming along nicely. Just be careful with it.
........
thank you very mach
I have a 16gb S3 which has been flashed to 4.3 (several times). My sons S3 is a 32GB but he broke the screen and bought a different phone. I thought I would like to swap out my motherboard and put his in my phone (both for the memory, and because I've set my Warranty Bit and I'm not entirely happy with 4.3's performance and his still has 4.1.2 so I can get a free reset on that). Both phones are T999's on the same account. His was bought off ebay but he was able to activate it so my assumption is that the IMEI is clean. Before I do this my questions are:
Will my IMEI change (is the IMEI locked to the motherboard)? If it changes, that's fine, as long as I can just pop my SIM in and be up and running.
Can I just do that swap, put my SIM in and go, or is there anything else I need to do with the phone after the swap? I work in a micro repair shop so I'm fine with doing all the hardware related work, just want to verify if I need to do anything extra after the swap.
The imei, and pretty much everything will be on the motherboard. Just swap it out and insert your SIM. Should be all you need to do.
Sent from my SGH-T999 using Tapatalk
OK, got the swap done, and a hard factory reset on 4.1.2 without issue.
So now I was planning on leaving it at that, but after reading through the [ROOT] TowelRoot - 4.3 & 4.4.2 thread today I'm thinking I'd like to try that. My goal is:
1. Update to latest 4.3 via OTA
2. Use the Towelroot tool to root and de-knox it
3. NOT set the warranty bit in the process (hopefully)
4. Create a debrick.img for T999 with clean NC2 (if it's still needed)
1,2, and 4 I'm good. Just curios if I OTA update 4.1.2 and follow all the steps for using towelroot, is there anything more I should be cautious or aware of about the warranty bit. My hope is that I don't do something stupid that will set it on this motherboard. I'd love to have 4.3 rooted but not set the bit.
I'm not concerned so much about the "modified" system or other counter(s)... triangle away was still working to clear those on my root66 NC2 load.
I think flashing the firmware via Odin is a better option. Too many people often seem to have trouble with OTA's. Thst and I personally just feel clean flashing the build you want is better than patching them up from a previous version.
In the end its what you are more comfortable with though. Just offering an alternative.
I'm comfortable doing an Odin flash but I thought that would set the warranty bit. I would've used root66, so am I off by thinking that? At any rate, I OTA'ed last night, ran towelroot and that worked, but I had some issues with the Supersu portion. It updated binaries, and then when it ask about disabling knox, I got a message saying Supersu install failed (or something similar). When I root checked it, it said it was rooted, and supersu was working, but all the knox related files were still on my phone. So I rebooted and ran supersu a second time and it just came up as it would if it were fully installed and working.
I never did figure out why, I even completely cleaned up/removed supersu from it's settings menu, re-installed it and tried again. At that point, it updated binaries without a hitch but didn't give me any prompt to do anything with knox. So does supersu somehow just disable knox, but leave all the files intact? I manually went in and deleted all the knox files myself at any rate and it didn't appear to screw anything up so far.
I also wondered if supersu issues had anything to do with the fact that when I installed it, I had not yet set Selinux to permissive.
Anyway, all that probably belongs in the threads for towelroot, so I got a little off topic .
Root66 apparently trips the warranty bit for some, but not all people. It did not trip mine. Since you've already done the OTA it doesn't really matter, but what I would've suggested next would've been to flash stock firmware via Odin, then Towelroot.
As for SuperSU, everyone has to reboot (or kill the process) before it'll properly disable Knox. And yes, that's all it does is disable it. Didn't have anything to do with seLinux.
OK, cool. So I guess it worked exactly as intended. Thanks for all the good info.
Interesting about the warranty bit.
*Updated 3/2017 to include same for LL updated SM-T707A*
For anyone else who has the SM-T707A (tab s 8.4" AT&T LTE version) -
Issues with this tablet:
1. Upgrading to Lollipop - seems that without an actual AT&T sim card installed, you're not going to be able to upgrade from 4.4.2 (cannot download the OTA update, and I haven't been able to find a download of the firmware online ANYWHERE).
2. Locked Bootloader - possible to carrier unlock for any compatible GMS carrier (I'm using mine with a T-mobile sim card), but seems that there is no way to unlock the bootloader/install a custom recovery.
(**NOTE: DO NOT TRY AND INSTALL TWRP OR USE THE UNLOCK/RECOVERY UTILITIES FOR THE SM-T705 ... while it seems like they would effectively be the same devices, both have exynos cpu and identical specs...I have tested out the odin-flashable methods from the development section that are for the SM-T705, and THESE WILL SOFT BRICK YOUR DEVICE. A HUGE ISSUE, SINCE THE STOCK FIRMWARE IS REALLY REALLY REALLY DIFFICULT TO FIND..)
SILVER LININGS:
1. Even if you have to stay on 4.4.2, you should be able to root with Kingo Root.
2. If you are rooted with Kingo on 4.4.2, and want to switch to SuperSU app instead of the KingoRoot one, you can try this (worked for me):
**Update 3/2017 - this will also work on LL updated SM-T707A
1. Install SuperSU app through google play store (regular install...NOT an update via recovery). This means you will now have TWO Superuser apps installed on your phone. Only the Kingo Superuser will have the authority to grant SU permissions at this point. Now open SuperSU and make sure it is installed. It should ask you to update the SU binary (you won't be able to yet, but make sure you get the prompt).
2. Download a terminal emulator app, or enable usb debugging in dev options, connect phone to pc, and open an adb shell.
3. Follow the instructions for switching to SuperSU available on android forums (search for "bakageta" +" supersu to kingo" +"android forums" ).
4. Download @bakageta's zip file and put on your sd card. Then open your terminal emulator or adb shell as root (type "su" + press enter) and run the first command: "# ./step0.sh" Remember to leave your terminal emulator open when you move on to the next step (same goes for your adb window).
5. Uninstall the Kingo Root apps (your tablet will then ~likely~ auto-reboot, closing the terminal emulator...DON'T PANIC, THIS IS OK.)
6. After your tablet boots back up, you should still have root**, but now your Superuser app will be SuperSU.
**UPDATE (3/2017, running the LL updated SM-T707A) If you are doing this on LL, you may need to also run the subsequent bakageta script, "# ./step1.sh" after the initial reboot to get SuperSU root access.
--> If anyone here knows how I can make a backup of the firmware I currently have installed (rooted stock 5.0.1) that can be used as a restore image via odin, please let me know! I'd gladly upload the file for anyone who is having trouble unbricking their devices, since the stock files are so insanely difficult to find for this particular variant of the tab s.
--Thanks to @Kingxteam
--Thanks to @bakageta for the alcatel scripts
see PM
chixvicious, did you ever managed to get those backups? I got a soft-bricked 707A and i also cant find the stock roms anywhere
PAragao said:
chixvicious, did you ever managed to get those backups? I got a soft-bricked 707A and i also cant find the stock roms anywhere
Click to expand...
Click to collapse
still not allowed to post links, but files can be found at dropbox dot com/s/mjobo2sfa53x2dv/T707AUCU1ANH9_T707AATT1ANH9_4.4.4_USA_4Files.rar?dl=0
Okay so I can confirm Galaxy Tab S 707a 8.4" LTE can be rooted in 4.4.2 with Kingo. It's goofy like kingo is , but it worked unfortunately that's not quite enough for myself as six axis never communicates w. Stock annnnd tmobile sucks and are being jerks can't use it without special plan so I'm putting my WiFi board back in. If any one wants rooted 4.4.2 unlocked motherboard......useless wasted tech here, all thanks to software restrictions.
updated for anyone else playing with these / whom it may concern if they ever google up this old ass device , I confirm on 4.4.2 707a I have successfully root with kingo and them using SUPERSUME apk I have swtiched it fully to SuperSU . Also using online nandroid backup with the 805 LTE variant patch I was able to get a full backup. I think I'm in decent shape for experimentation as I'm on the lowest order firmware and hopefully , not sure but hopefully if anything goes badly i can just update to newer firmware. Going to attempt using SAFESTRAP recovery next
SuperlativeB said:
updated for anyone else playing with these / whom it may concern if they ever google up this old ass device , I confirm on 4.4.2 707a I have successfully root with kingo and them using SUPERSUME apk I have swtiched it fully to SuperSU . Also using online nandroid backup with the 805 LTE variant patch I was able to get a full backup. I think I'm in decent shape for experimentation as I'm on the lowest order firmware and hopefully , not sure but hopefully if anything goes badly i can just update to newer firmware. Going to attempt using SAFESTRAP recovery next
Click to expand...
Click to collapse
I still have 2 of these and am constantly disappointed at how much development there is for every other variants but this one.
I got safestrap in , was able to reboot and see it but no luck due to se enforcing , I tried everything to get it to permissive but no luck. I went back to my WiFi model ha , oh well. Have to look for a 705 that has unlocked boot / better firmware
pm me if you still have that!
SuperlativeB said:
Okay so I can confirm Galaxy Tab S 707a 8.4" LTE can be rooted in 4.4.2 with Kingo. It's goofy like kingo is , but it worked unfortunately that's not quite enough for myself as six axis never communicates w. Stock annnnd tmobile sucks and are being jerks can't use it without special plan so I'm putting my WiFi board back in. If any one wants rooted 4.4.2 unlocked motherboard......useless wasted tech here, all thanks to software restrictions.
Click to expand...
Click to collapse
PM me if you still have that! I randomly have an extra (shattered screen) Tab S 8.4" without a motherboard, and would play around with trying to unlock the bootloader on it if I had a mobo to put in it!
Thanks!
SuperlativeB said:
I got safestrap in , was able to reboot and see it but no luck due to se enforcing , I tried everything to get it to permissive but no luck. I went back to my WiFi model ha , oh well. Have to look for a 705 that has unlocked boot / better firmware
Click to expand...
Click to collapse
I could help get this permissive on kitkat, but not LL or MM.
ashyx said:
I could help get this permissive on kitkat, but not LL or MM.
Click to expand...
Click to collapse
What are your thoughts ? It's def still kitkat , but I've tried init'd stuff and all sorts crap. If i got permissive i could possibly get safestrap to boot and then try out roms intended for the regular LTE variant. It is just kind of useless for me as T-mobile it's device Id as tablet so they lock it out then if i just wanted to use it WiFi the TouchWiz stuff kills remote controls like six axis and stuff. Id prob use it daily if i could get past device id pickups / safestrap a way into better rom
anyone have the 6.0.1 firmware?
I had 5.1.1 installed. Couldn't get KingRoot to give temp root (lots of people say you can only do it on 4.4.4, lots of other people say they got it to work on 5.1.1 if you read around).
So I tried downgrading to 4.4.4. Odin failed every time.
So I tried downgrading to 5.0.1. That worked. But kingroot still was unable to get root.
I then found King O Root. Tried that once, no luck. Tried it a 2nd time, and success. I then ran the samsund_fix file. And it changed my CID.
But then you have to restart the phone and run the fix file again.
I have run king o root (and tried kingroot) each at least 30 times now. And I can't get either to give me root access again. I've even tried the desktop version of king o root. Nothing.
I'm SOOO close I feel. But I can't get that last step. Its killing me.
Can anyone help with where to go next?
I figure either 1) I have to find a way to get temporary root one more time. OR 2) find a way to get down to kitkat 4.4.4 to get temporary root.
One other quick question, is the reason I can't get to 4.4.4 because I upgraded all the way to 5.1.1? EVERYTHING I read says 'yeah you can downgrade' but mine won't downgrade. Odin fails with an error So how do I get to 4.4.4? Am I just screwed?
NAND Write Start!
boot.img
FAIL! (Auth)
Are you sure you have to push the file again?
Sometimes it doesn't take and you need to push it again. The last couple of times I unlocked it went on the first try. Go into download mode and see if it says "developer mode."
I was able to unlock on 5.1.1. Kingroot and Kingoroot are extremely unstable besides being Chinese software with all of the risks that entails. There is supposedly a PC version of one of them (shudder) that is allegedly a bit more stable.
Where are you getting the firmware you're trying to use to downgrade?
douger1957 said:
Are you sure you have to push the file again?
Sometimes it doesn't take and you need to push it again. The last couple of times I unlocked it went on the first try. Go into download mode and see if it says "developer mode."
Click to expand...
Click to collapse
So I'm not 100% sure I have to push the file again. I know when I ran the fix file in adb shell the first time, it said I have to run the fix script again. And then when I boot into download mode, I see nothing that says "developer mode".
But, on the other hand. When I check with the eMMC Brickbug checker thing. That says the CID did change according to what the samsung_fix script said it changed it to.
So I *think* the CID changed? But I don't have developer mode. So I think I need to run the fix script again to finish the job.
douger1957 said:
I was able to unlock on 5.1.1. Kingroot and Kingoroot are extremely unstable besides being Chinese software with all of the risks that entails. There is supposedly a PC version of one of them (shudder) that is allegedly a bit more stable.
Click to expand...
Click to collapse
I actually tried a PC version of kingoroot. It also failed numerous times.
douger1957 said:
Where are you getting the firmware you're trying to use to downgrade?
Click to expand...
Click to collapse
I'm getting it from androidfilehost.
https://www.androidfilehost.com/?w=search&s=n910v
That's where I got the 5.0.1 version that worked when I went from 5.1.1 to 5.0.1. But I guess I could try finding a 4.4.4 version from somewhere else. I don't know where though.
It passes md5 check in odin. Though I'm not sure that means much.
nertskull said:
So I'm not 100% sure I have to push the file again. I know when I ran the fix file in adb shell the first time, it said I have to run the fix script again. And then when I boot into download mode, I see nothing that says "developer mode".
But, on the other hand. When I check with the eMMC Brickbug checker thing. That says the CID did change according to what the samsung_fix script said it changed it to.
So I *think* the CID changed? But I don't have developer mode. So I think I need to run the fix script again to finish the job.
I actually tried a PC version of kingoroot. It also failed numerous times.
I'm getting it from androidfilehost.
https://www.androidfilehost.com/?w=search&s=n910v
That's where I got the 5.0.1 version that worked when I went from 5.1.1 to 5.0.1. But I guess I could try finding a 4.4.4 version from somewhere else. I don't know where though.
It passes md5 check in odin. Though I'm not sure that means much.
Click to expand...
Click to collapse
This may be your problem. I don't think you can flash a rooted ROM with a locked bootloader with success. Try this one. (Thanks, @hsbadr!) It's the OEM firmware. This will mean that you'll need to start from scratch. I should note that another poster has had trouble flashing this firmware although other posters including myself have used it successfully.
@hsbadr has a repository of firmwares. What you're looking for is the full firmware. Sammobile is another source of firmware, but they're terribly slow to download from.
douger1957 said:
This may be your problem. I don't think you can flash a rooted ROM with a locked bootloader with success. Try this one. (Thanks, @hsbadr!) It's the OEM firmware. This will mean that you'll need to start from scratch. I should note that another poster has had trouble flashing this firmware although other posters including myself have used it successfully.
@hsbadr has a repository of firmwares. What you're looking for is the full firmware. Sammobile is another source of firmware, but they're terribly slow to download from.
Click to expand...
Click to collapse
I tried that firmware you linked to. That took me back to 5.1.1. I tried kingroot and kingoroot, and still no luck. After 8 or 9 tries each, I still can't get temproot.
I thought it would be better to go back to 4.4.4, and looked through hsbadr's list of roms you linked me to. I tried both of the 4.4.4 full firmwares (NJ5 and NI1) and both fail on odin.
It would seem to me I'm never getting back to 4.4.4/kitkat am I?
Should I just keep running kingroot/kingoroot until I can get temp root? I ran kingoroot at least 30 times last night on 5.0.1 and never got root again. I really don't understand why I could get it once but never again.
Should I try running it a million times on 5.1.1 where I now am again? Or should I go back to 5.0.1? Is there any other way to get temporary root?
nertskull said:
I tried that firmware you linked to. That took me back to 5.1.1. I tried kingroot and kingoroot, and still no luck. After 8 or 9 tries each, I still can't get temproot.
I thought it would be better to go back to 4.4.4, and looked through hsbadr's list of roms you linked me to. I tried both of the 4.4.4 full firmwares (NJ5 and NI1) and both fail on odin.
It would seem to me I'm never getting back to 4.4.4/kitkat am I?
Should I just keep running kingroot/kingoroot until I can get temp root? I ran kingoroot at least 30 times last night on 5.0.1 and never got root again. I really don't understand why I could get it once but never again.
Should I try running it a million times on 5.1.1 where I now am again? Or should I go back to 5.0.1? Is there any other way to get temporary root?
Click to expand...
Click to collapse
I was able to unlock my bootloader twice on 5.1.1. I used Kingroot to unlock Lollipop and Kingoroot to unlock Marshmallow. See if you can find an older version of either root methods. I think I remember reading somewhere that the newer version is flakier than the older stuff. I'm fairly convinced that the rooted ROM you flashed is part of the problem.
As I said, Kingroot and Kingoroot are highly unstable. You may need to spend quite a bit of time in multiple attempts. It comes down to how badly do you want root?
douger1957 said:
I was able to unlock my bootloader twice on 5.1.1. I used Kingroot to unlock Lollipop and Kingoroot to unlock Marshmallow. See if you can find an older version of either root methods. I think I remember reading somewhere that the newer version is flakier than the older stuff. I'm fairly convinced that the rooted ROM you flashed is part of the problem.
As I said, Kingroot and Kingoroot are highly unstable. You may need to spend quite a bit of time in multiple attempts. It comes down to how badly do you want root?
Click to expand...
Click to collapse
Holy success. I have no idea why. But after rebooting the phone for the umpteenth time and running kingoroot another 20 times. It finally gave me another successful temp root, this time while on 5.1.1.
I ran the script again, and now when I got into download mode, I have Mode: Developer showing. Hooray.
BUT....then bootloops. I couldn't get it started.
I then accidentally wiped everything, completely wiped. No operating system according to twrp.
So I looked around, and it appears JasmineRom and CM13 by hsbadr are mentioned as good custom ROMs. So I grabbed CM13, used twrp to install it. And success. I have a working phone. At least, for the past couple minutes.
So a tremendous thank you for giving me some guidance.
I have two more questions for the moment though.
1) How easy/hard would it be to lose developer mode? Do I need to be careful about what roms I flash? Could I lose that? Or now that it is in developer mode, should I be pretty safe in that sticking around?
2) Can I try any Rom on it right now. There don't appear to be a lot of verizon note 4 specific roms around for this phone, because it hasn't had root for long. Will any of the other note 4 roms work? Or should I make sure to stick to only 'proven verizon' roms.
Thanks again for the help.
....
Oh, and how bad do I want root? Badly. Super badly. If I had the money I would have ditched this phone forever ago. I will never buy another phone again on the hope/promise that it will get root soon.
nertskull said:
Holy success. I have no idea why. But after rebooting the phone for the umpteenth time and running kingoroot another 20 times. It finally gave me another successful temp root, this time while on 5.1.1.
I ran the script again, and now when I got into download mode, I have Mode: Developer showing. Hooray.
BUT....then bootloops. I couldn't get it started.
I then accidentally wiped everything, completely wiped. No operating system according to twrp.
So I looked around, and it appears JasmineRom and CM13 by hsbadr are mentioned as good custom ROMs. So I grabbed CM13, used twrp to install it. And success. I have a working phone. At least, for the past couple minutes.
So a tremendous thank you for giving me some guidance.
I have two more questions for the moment though.
1) How easy/hard would it be to lose developer mode? Do I need to be careful about what roms I flash? Could I lose that? Or now that it is in developer mode, should I be pretty safe in that sticking around?
2) Can I try any Rom on it right now. There don't appear to be a lot of verizon note 4 specific roms around for this phone, because it hasn't had root for long. Will any of the other note 4 roms work? Or should I make sure to stick to only 'proven verizon' roms.
Thanks again for the help.
....
Oh, and how bad do I want root? Badly. Super badly. If I had the money I would have ditched this phone forever ago. I will never buy another phone again on the hope/promise that it will get root soon.
Click to expand...
Click to collapse
The only way I know to lock your bootloader is to flash an OEM firmware, take an OTA or mess with flashing bootloader without knowing what you're doing..
What you can flash depends upon which bootloader you have unlocked. Lollipop? You can flash a ROM based on a Lollipop bootloader. Jasmine 4.3 and CM 13 before 6/20 are Marshmallow ROMs based on Lollipop bootloaders. You can also run ROMs made for the N910F/G (also based on Lollipop bootloaders) if you use the proper data fix.
If you want to run a pure Marshmallow ROM, you need to do the unlock dance again. If you're interested in wifi calling, you'll need to stick with a fairly stock OEM ROM like Jasmine 6.0 or 7.0 (both versions are buried pretty deep in the thread) or PaulPizz which I haven't tried but hear good things about.
douger1957 said:
The only way I know to lock your bootloader is to flash an OEM firmware, take an OTA or mess with flashing bootloader without knowing what you're doing..
What you can flash depends upon which bootloader you have unlocked. Lollipop? You can flash a ROM based on a Lollipop bootloader. Jasmine 4.3 and CM 13 before 6/20 are Marshmallow ROMs based on Lollipop bootloaders. You can also run ROMs made for the N910F/G (also based on Lollipop bootloaders) if you use the proper data fix.
If you want to run a pure Marshmallow ROM, you need to do the unlock dance again. If you're interested in wifi calling, you'll need to stick with a fairly stock OEM ROM like Jasmine 6.0 or 7.0 (both versions are buried pretty deep in the thread) or PaulPizz which I haven't tried but hear good things about.
Click to expand...
Click to collapse
Awesome. I downloaded CM13 from before the 20th and it seems to work great. I had to flash the CM13 rom and open GApps at the same time, otherwise the GApps kept crashing. But flashing them at the same time before turning on CM13 for the first time seemed to work.
Thanks for the help. Don't follow things closely enough to have known that I needed a pre 20th build.
Perhaps one more question.
Would you recommend taking the time to unlock the marshmallow bootloader? I don't need wifi calling. And I seem to be getting most of the benefits of 6.0.1 now even though using a lollipop bootloader.
I'm hesitant to try to unlock the marshmallow bootloader, because according to the instructions, it looks like I have to deal with kingroot/kingoroot again to do it. And I had such a hard time getting those to work this first time (easily 80+ tries running kingoroot) before I got temproot, that I'm not sure I want to take the risk of doing it again.
In your opinion, is it worth the risk to unlock the marshmallow bootloader? Or is running marshmallow on the lollipop bootloader reasonable enough?
Thanks
nertskull said:
Awesome. I downloaded CM13 from before the 20th and it seems to work great. I had to flash the CM13 rom and open GApps at the same time, otherwise the GApps kept crashing. But flashing them at the same time before turning on CM13 for the first time seemed to work.
Thanks for the help. Don't follow things closely enough to have known that I needed a pre 20th build.
Perhaps one more question.
Would you recommend taking the time to unlock the marshmallow bootloader? I don't need wifi calling. And I seem to be getting most of the benefits of 6.0.1 now even though using a lollipop bootloader.
I'm hesitant to try to unlock the marshmallow bootloader, because according to the instructions, it looks like I have to deal with kingroot/kingoroot again to do it. And I had such a hard time getting those to work this first time (easily 80+ tries running kingoroot) before I got temproot, that I'm not sure I want to take the risk of doing it again.
In your opinion, is it worth the risk to unlock the marshmallow bootloader? Or is running marshmallow on the lollipop bootloader reasonable enough?
Thanks
Click to expand...
Click to collapse
That's a difficult question to answer and for me would boil down to whether I wanted features available in Marshmallow based ROMs or not.
Wifi calling is a nice to have feature for me but it's not really a dealbreaker. There's a bit more security baked into Marshmallow which is always nice to have.
The development atmosphere is more active over at the generic Note 4 forum. You can now get one of the super ROMs (Note/S7 combo ports) in either flavor. You'll want to stick with ROMs developed for the N910F or G models. They're international phones with fewer integration headaches for our N910V phones. To use those ROMs on our phone, you'll need a data fix most kindly provided by @louforgiveno.
My suggestion in picking a ROM is to zero in on one that seems to have the features you'd like to have and read the entire thread. Look for threads in either the General or Q&A subforums that are dedicated to answering questions about the ROM and read those, too. Some of those threads are upwards to 1,000 posts or more, you say? You'll discover what problems people have had with the ROM and the solutions or workarounds needed to overcome them. You'll also discover just how lazy many posters are either not reading thoroughly or failing to use the search function.
Final suggestions? Do a full nandroid backup before you flash anything. In TWRP, check off all of the boxes. In many of today's ROMs, you'll have a 8 to 10 gig backup file. If you can't keep that on the phone, move it to your PC. There will be far fewer tears if something goes wrong. When you flash a ROM, do a full wipe. I check off Dalvik/ART cache, system, data, and cache. For your first ROM, I would move anything that you have on internal storage off the phone and wipe internal storage too. If you have any Kingroot/Kingoroot cooties, that should clear them off the phone. When you're done flashing a ROM there's an option to wipe the cache. Do it. If you've installed a bunch or apps or deleted them, wipe the Dalvik and cache. It'll help bring the Android stars into alignment as that forces the system to optimize.
Good luck and happy flashing.
You need to go to 5.1.1 use kingOroot and then do it again. Cid will remain that's what I did. Its different for everyone these root methods are pulled from the internet and it will usually take a few time and it will try dufrrent methods of rooting
nertskull said:
I had 5.1.1 installed. Couldn't get KingRoot to give temp root (lots of people say you can only do it on 4.4.4, lots of other people say they got it to work on 5.1.1 if you read around).
So I tried downgrading to 4.4.4. Odin failed every time.
So I tried downgrading to 5.0.1. That worked. But kingroot still was unable to get root.
I then found King O Root. Tried that once, no luck. Tried it a 2nd time, and success. I then ran the samsund_fix file. And it changed my CID.
But then you have to restart the phone and run the fix file again.
I have run king o root (and tried kingroot) each at least 30 times now. And I can't get either to give me root access again. I've even tried the desktop version of king o root. Nothing.
I'm SOOO close I feel. But I can't get that last step. Its killing me.
Can anyone help with where to go next?
I figure either 1) I have to find a way to get temporary root one more time. OR 2) find a way to get down to kitkat 4.4.4 to get temporary root.
One other quick question, is the reason I can't get to 4.4.4 because I upgraded all the way to 5.1.1? EVERYTHING I read says 'yeah you can downgrade' but mine won't downgrade. Odin fails with an error So how do I get to 4.4.4? Am I just screwed?
NAND Write Start!
boot.img
FAIL! (Auth)
Click to expand...
Click to collapse
For me, I had to run Kingoroot from my laptop, and Kingroot never worked.
This is an open discussion about the Straight Talk Galaxy S6. Here I want to discuss about possible root access along with a possibility to downgrade. Looking for any volunteers to help me with this phone.
I own a red magic 3, a G6, and an old S6 with straight talk firmware. I usually use my G6 and S6 to play around with for development purposes.
So awhile back, I managed to root my galaxy S6 straight talk with a third-party rootkit. Not long after that I wanted to upgrade this thing to marshmallow. I managed to succeed in doing it, only to be left with a useless phone.
Upon my research, you can flash an SM-S907VL firmware which appears to be a TracFone firmware for the S6. However, the 907VL appears to not support straight talk users. I attempted to downgrade back to the S906L but the strict SBoot prevents me from going back.
A half year later, I'm still messing with this phone. I want to see about finding a way to gain root access or look for any loop holes (possible exploits) that we could do with this phone. I managed to find a way to root the SM-S907VL. Here's how:
I first did some deep digging on the internet and found combination firmwares for this particular model. Combination ROMs are (what I believe are test ROMs for phones). I managed to flash a combination firmware to it. After that I rooted it with kingroot, uninstalled kingroot SU and switched to SuperSU. Then I installed Flashfire and I tried to flash the SM-S906L but no luck.
However, upon even FURTHER searching, I managed to flash the SM-S906L by ONLY flashing the system.img by extracting it from the md5 and adding it to a tar archive.
Well here is where things get complicated, since I only flashed the system, the kernel is running on a later kernel security patch. Which means rooting it with Kingroot fails. Also, the CVC and modem is still running on the SM-S907VL so even if you put a straight talk sim card into it, it won't work. Bummer
I'm wanting to see how far we can go into this phone and hopefully find a way to somehow get it unlocked somehow.
I'm all ears for y'all!
EDIT: Crap, posted in the wrong category. I should have posted in the general forum.