Related
Hi guys I have some questions about the new Firmware and KitKat in general and you may have answers I'll try to update first post with your answers!
-Will I loose root when I flash through Odin? --> Yes
-Is the new firmware rootable, or is there a way to keep root when I upgrade from rooted 4.3?
-->For upgrade yes: If you are rooted on 4.3 you can restore root by flashing a custom recovery and flash superSU manually.
-->chainfire autoroot works but you need to update the superSU app through play store after flashing.
-Will KitKat restrict access to my SD card? -->Yes but fixable through an app or editing a file (needs root), there is already a thread about that.
-Can I still use flash with KitKat? How?
-->Yes, there is a hacked version see 2nd post for link.
-How is the touchscreen driver? Is the stuttering fixed? Do touch and hold actions still drop after ~23sec?
-->Pretty much fixed. To about the same state as the improved Kernel we had a while ago.
-Are there any apps that are not working (root apps too)?
-Gesture Controls? --> works
-Xposed framework app settings? -->works
-Is Hancom Office included or does it still work? --> not included but does still work.
Thats about what I can think of a the moment.
Hi,
If you are already rooted then all you have to do is re install TWRP and then flash SU zip then you have root.
For flash player, download hacked version here, it works I tested it on new software :
http://forum.xda-developers.com/go...e-how-to-play-flash-video-android-4-t2548001
Also, xposed works. Tested it on new software
Sent from my Note 2014 using Tapatalk
Chainfire's Auto Root does work, once you flash it thru odin and reboot, go to the Play store and update the app.
- Please update OP
Here's a question: I'm already rooted. Is flashing the stock KitKat image via Odin and rerooting the only way to upgrade?
starfall42 said:
Here's a question: I'm already rooted. Is flashing the stock KitKat image via Odin and rerooting the only way to upgrade?
Click to expand...
Click to collapse
If you are already rooted, I assume you have TWRP too. Just download this KitKat rom, full wipe and install.
http://forum.xda-developers.com/show....php?t=2720631
Itchiee said:
Chainfire's Auto Root does work, once you flash it thru odin and reboot, go to the Play store and update the app.
- Please update OP
Click to expand...
Click to collapse
Not for me I flashed a stock 4.4 kit kat on my tablet coming from root 4.3. I then flashed chainfire autoroot thru odin on the 4.4 and the superuser there only problem is it displays this ' There is no SU binary installed, and SuperSU cannot install this is a problem! I formatted my 4.3 before flashing it maybe thats why?
itachi30s said:
Not for me I flashed a stock 4.4 kit kat on my tablet coming from root 4.3. I then flashed chainfire autoroot thru odin on the 4.4 and the superuser there only problem is it displays this ' There is no SU binary installed, and SuperSU cannot install this is a problem! I formatted my 4.3 before flashing it maybe thats why?
Click to expand...
Click to collapse
Not sure... I installed KK on the tablet via Odin, then rebooted and setup, then rebooted into download mode and flashed auto root thru Odin.
Upon reboot I got an error selecting SuperSU, but once I updated it thru the Play Store its been fine.
Using ES Explorer I removed the items I don't need and removed all of the Knox stuff.
There are a few of us this worked for so I don't know what went wrong for you.
If you don't succeed then try again, and again, and again....Good luck.
Do I have to update to kitkat bootloader?
gcrutchr said:
Do I have to update to kitkat bootloader?
Click to expand...
Click to collapse
Not needed. The bootloader is same for 4.3 and 4.4
Itchiee said:
Not sure... I installed KK on the tablet via Odin, then rebooted and setup, then rebooted into download mode and flashed auto root thru Odin.
Upon reboot I got an error selecting SuperSU, but once I updated it thru the Play Store its been fine.
Using ES Explorer I removed the items I don't need and removed all of the Knox stuff.
There are a few of us this worked for so I don't know what went wrong for you.
If you don't succeed then try again, and again, and again....Good luck.
Click to expand...
Click to collapse
Thx for the response from what i can see you never fully wipe your data before installing 4.4 KK but i did so i believe i lost my root like that. So when i updated the supersu never carried over from 4.3
Srikar_NBK said:
Not needed. The bootloader is same for 4.3 and 4.4
Click to expand...
Click to collapse
Thanks.
Itchiee said:
Not sure... I installed KK on the tablet via Odin, then rebooted and setup, then rebooted into download mode and flashed auto root thru Odin.
Upon reboot I got an error selecting SuperSU, but once I updated it thru the Play Store its been fine.
Using ES Explorer I removed the items I don't need and removed all of the Knox stuff.
There are a few of us this worked for so I don't know what went wrong for you.
If you don't succeed then try again, and again, and again....Good luck.
Click to expand...
Click to collapse
man you're awesome thx a bunch I saw my mistake, I was using chain fire root except the one I had downloaded from a third party site wasn't exactly for my device. Went to chainfire official site got the autoroot bam im rooted at.
Rep + 1
How do you get hancom office?
-Will KitKat restrict access to my SD card? -->Yes but fixable through an app or editing a file (needs root), there is already a thread about that.
Click to expand...
Click to collapse
Sorry, but I cant find thread related to the issue .
What do you mean by `fixable through an app`? I`m not rooted and full stock.
Kit Kat SD Card Issue
clouds5 said:
Hi guys I have some questions about the new Firmware and KitKat in general and you may have answers I'll try to update first post with your answers!
-Will KitKat restrict access to my SD card? -->Yes but fixable through an app or editing a file (needs root), there is already a thread about that.
Click to expand...
Click to collapse
Is this the app you are referring to? http://forum.xda-developers.com/showthread.php?t=2684188
Still not out in Germany
I intend on rooting this tablet. Am I better off rooting 4.3 and then flashing KK update? Or is it possible to update to KK and then root?
supremekizzle said:
I intend on rooting this tablet. Am I better off rooting 4.3 and then flashing KK update? Or is it possible to update to KK and then root?
Click to expand...
Click to collapse
Both ways work equally well I was already rooted with 4.3 but either way has been confirmed working so it doesn't matter.
clouds5 said:
Both ways work equally well I was already rooted with 4.3 but either way has been confirmed working so it doesn't matter.
Click to expand...
Click to collapse
Thank you. So any guide I find on rooting 4.3 should be the same procedure as 4.4?
supremekizzle said:
Thank you. So any guide I find on rooting 4.3 should be the same procedure as 4.4?
Click to expand...
Click to collapse
Yes. Refer to this one
http://forum.xda-developers.com/showthread.php?t=2490805
I'm sorry i had the wrong links and because of this i had miss information. So i formally apologize by updating with the proper links.
this first method doesn't work with the Sph-L710T or the Sph-L710 on NJ2/NJ3
First method: You can root the stock 4.4.2 ND8/NDC:laugh:
1st. Make sure your on 4.4.2 ND8 or NDC
2nd. Download Towel Root
3rd. Place Towel Root in sdcard or internal storage
4th. With any file manager find and install Towel Root
5th. Open Towel Root and well root
6th. Go to play store and download https://play.google.com/store/apps/details?id=eu.chainfire.supersu&hl=en and also https://play.google.com/store/apps/details?id=stericson.busybox&hl=en let super user update the binary
7th. Flash any recovery you want {personally i went with PhilZ Touch (this was before PhilZ had a root Option)}
8th. Enjoy your rooted stock 4.4.2 ND8/NDC
Down below is one more way too root Stock ND8/NDC/NJ2/NJ3 or NF4/OA3 (L710T) and basically any other update
(link to the almighty ODIN)
Second Method: mostly recommended
1st. Odin flash TWRP
2nd. In Odin choose PDA, PA or AP then select the TWRP Tar you just downloaded
3rd. Make sure Auto reboot is unchecked (also at this time your s3 should be in download mode)
4th. Hit start and let Odin let it finish!!
5th. Hold power button to turn off your S3, after it turns off about 10 seconds later it will turn back on to the battery charging screen so before that quickly hold Volume+ and Home, to boot into recovery
6th. now your in TWRP
7th. so to root your stock rom with TWRP flash the following file SuperSU.zip by Chain fire (pro tip. Install any other custom recovery the same way I did for TWRP above if it is in .tar format)
and here is Philz recovery for the D2Lte 6.48.4 ( which you must flash in TWRP)
and here is TWRP that was made specifically for the D2Rephersher/triband/L710T TWRP (which you must flash in a recovery)
Third method Most recent.
Hidyman said:
This is in reference to Samsung Galaxy S3 for Boost Mobile SPH-L710.
Just want to let anyone out there that updated their Boost S3 to L710VPUC0J1 know that you can still root and/or ROM your phone.
Use the instructions to (use Odin to) update the recovery to TWRP first (in the second set of instructions). I had trouble trying to go right to PhilZ Recovery (which I believe is based off of ClockWorkMod). I Had to do the TWRP (twrp-2.8.7.0-d2spr.img.tar) first.
It was the only way to get it to actually accept the recovery, not sure why, maybe because the latest Samsung firmware fixed an exploit or two.
This is an older phone, but it is still a viable one.
I hope this helps someone out there.
It took me a while to figure this quandary out.
As always this WILL flag KNOX, but I'm sure this won't be an issue at this date and time (8/2016).
Click to expand...
Click to collapse
work on ND8 rom? sprint phone?
Tekone said:
work on ND8 rom? sprint phone?
Click to expand...
Click to collapse
i want to say yes but towel root does come with a warning that it might brick your device.....but i want to say yes since most things that can be done to the ND8 can be done to the NDC and also in reverse order.....so try it and report back it will be good to know if it works on both bootloaders
Sprint S3 Android 4.4.2 ND8-It works!
I just used this method to root my Sprint S3 running Android 4.4.2 and ND8, since my USB port is on the fritz, and it worked successfully. I have root, and was able to do a full apps backup with Titanium Backup, and gained root access in ES File Explorer. Next, download and install a custom backup. Thanks, great job, and could not have been made easier to do!
oops
Rooted the phone in one click. Unfortunately, I lost all data (no 3G or 4G connection). Did I goof? I'm looking in the stickies and can't seem to find an answer. I'd appreciate any help I can get.
henhun said:
Rooted the phone in one click. Unfortunately, I lost all data (no 3G or 4G connection). Did I goof? I'm looking in the stickies and can't seem to find an answer. I'd appreciate any help I can get.
Click to expand...
Click to collapse
ND8 or NDC? have you tried updating your profile/PRL?
6th_Hokage said:
ND8 or NDC? have you tried updating your profile/PRL?
Click to expand...
Click to collapse
Ya know. People keep talking about ND8 and ND___. I have no idea what that means. I know I should be embarrassed.
UPDATE: FIGURED IT OUT, BASEBAND VERSION. GOTCHA. IT IS NDC.
I was JUST coming back to update my post. I DID update the PRL and restarted my phone. That seems to have done the trick. Thank GOD I got my data connection back!! It worked. Even though I found the info somewhere else, thank you so much for the quick reply. PRL update fixes the problem. You're awesome.
I used it before i had a custom recovery. And on reboot i wouldnt have root. After i ran it root checker told me i was rooted then reboot killed. I installed philz and all was ok
Sent from my SPH-L710 using XDA Free mobile app
jbnorton0524 said:
I used it before i had a custom recovery. And on reboot i wouldnt have root. After i ran it root checker told me i was rooted then reboot killed. I installed philz and all was ok
Sent from my SPH-L710 using XDA Free mobile app
Click to expand...
Click to collapse
many users of basically the same phone report different things with every root method out there. If it worked for you that's great tell other users what you did for it to work and if it didn't work, then ask for help and you will get help; some people don't have success with any method while others do with all of the methods.....my phone falls under every method.....
Successful Towelroot on VM Galaxy S3 4.4.2.NDC
6th_Hokage said:
you can root the stock 4.4.2
first step make sure your on 4.4.2
second step download Towel Root
third step place Towel Root in sdcard or internal storage
fourth step with any file manager find and install Towel Root
fifth step root
sixth step go to play store and download Superuser (Chainfire) and also Busy Box (Stericson) let super user update the binary
seventh step flash any recovery you want personally i went with Philliz Touch
eighth step if you want flash a custom rom now if not enjoy your rooted stock 4.4.2
Click to expand...
Click to collapse
Straight forward, fast and easy. I did notice the following:
1) Updating binary reported it did not successfully install. I've seen this before on other devices, but everything worked well. Ext SD and Camera all OK. Everything works fine so far - Titanium, Nandroid, Root Browser, etc.
2) At one point, I was directed to install Busy Box. Having done this on other devices, I said "Yes" and installed it.
3) I see that my device now shows Device Status as Custom ( was Normal before, if I remember correctly). Is this due to Busy Box?
4) Is Device Status the only way to know the KNOX Status? I see no yellow triangle as I did on my Galaxy Reverb.
5) I got a Google warning to uninstall Towelroot since it is usafe and a security exploit. I understand that.
I would like to verify the KNOX status and if tripped in the Towelroot process, to let potential users know of that possibility.
Thank You! And thanks to everyone who has continued to work on keeping root free!
Dave
dave260 said:
Straight forward, fast and easy. I did notice the following:
1) Updating binary reported it did not successfully install. I've seen this before on other devices, but everything worked well. Ext SD and Camera all OK. Everything works fine so far - Titanium, Nandroid, Root Browser, etc.
2) At one point, I was directed to install Busy Box. Having done this on other devices, I said "Yes" and installed it.
3) I see that my device now shows Device Status as Custom ( was Normal before, if I remember correctly). Is this due to Busy Box?
4) Is Device Status the only way to know the KNOX Status? I see no yellow triangle as I did on my Galaxy Reverb.
5) I got a Google warning to uninstall Towelroot since it is unsafe and a security exploit. I understand that.
I would like to verify the KNOX status and if tripped in the Towelroot process, to let potential users know of that possibility.
Thank You! And thanks to everyone who has continued to work on keeping root free!
Dave
Click to expand...
Click to collapse
Knox only notifies Samsung that your device isn't stock anymore not necessarily rooted like with a custom recovery and then flashed mods and what not but if you Odin the stock rom it resets the counters so Samsung will never know....and that i have noticed TowelRoot doesn't trip that counter.....only the recoveries and when you update the binary (<---completely forgot to fix that) you must hit the option normal not TWRP/CWM
churninern said:
I just used this method to root my Sprint S3 running Android 4.4.2 and ND8, since my USB port is on the fritz, and it worked successfully. I have root, and was able to do a full apps backup with Titanium Backup, and gained root access in ES File Explorer. Next, download and install a custom backup. Thanks, great job, and could not have been made easier to do!
Click to expand...
Click to collapse
That's great news because same boat here. It worked on 4.3 as well.
I had the phone hacked before and something must not be fully stock so the Ota fails.
I downloaded a package and mobile odin should flash it properly and then I can root it with this again and install a nice modified TouchWiz rom.
Darkangels6sic6 said:
That's great news because same boat here. It worked on 4.3 as well.
I had the phone hacked before and something must not be fully stock so the Ota fails.
I downloaded a package and mobile odin should flash it properly and then I can root it with this again and install a nice modified TouchWiz rom.
Click to expand...
Click to collapse
just a quick add on Mobile Odin and stock ND8/NDC don't mix at all
Knox Counter and "Device Status"
6th_Hokage said:
Knox only notifies Samsung that your device isn't stock anymore not necessarily rooted like with a custom recovery and then flashed mods and what not but if you Odin the stock rom it resets the counters so Samsung will never know....and that i have noticed TowelRoot doesn't trip that counter.....only the recoveries and when you update the recovery you must hit the option normal not TWRP/CWM
Click to expand...
Click to collapse
Thanks for your response. I may be over thinking these indicators. All I did was Towelroot, successfully. On the phone, the "About Device, Status" now says CUSTOM (was "Official"). The Knox counter according to app "Phone Info" shows Knox Counter at 0x0. As you said, since the counter is not tripped, should be no problem on warranty. So then Device Status CUSTOM is not a problem? I'm not really worried about warranty at this point, but I think I'll hold off further mods for another 6 moths.
Thanks again for your help!
6th_Hokage said:
just a quick add on Mobile Odin and stock ND8/NDC don't mix at all
Click to expand...
Click to collapse
Thanks. I tried the md8 and mk3 "mk3 is what it's on". Both just restart and get stuck on splash screen :/.
I have to go to download mode and and restart it that way to boot system back up.
Do you have any other suggestion. I'm not sure what part of the system is altered. It seems like a stock recovery and it's stock firmware "now rooted". Maybe the kernel.
I can't use USB at all.
I'm guessing maybe I should install twrp. Then install a stock zip or try out a 4.3 rom that way. I would like to get to md8 one way or another. Most md8 Roms want you to odin or flash an md8 base.
Darkangels6sic6 said:
Thanks. I tried the ND8 and MK3 "MK3 is what it's on". Both just restart and get stuck on splash screen :/.
I have to go to download mode and and restart it that way to boot system back up.
Do you have any other suggestion. I'm not sure what part of the system is altered. It seems like a stock recovery and it's stock firmware "now rooted". Maybe the kernel.
I can't use USB at all
I'm guessing maybe I should install TWRP. Then install a stock zip or try out a 4.3 rom that way. I would like to get to md8 one way or another. Most ND8 Roms want you to Odin or flash an md8 base.
Click to expand...
Click to collapse
cause they need the ND8 base to work as intended...my suggestion would be to get the usb port on your phone fixed but i don't know how expensive that will be
6th_Hokage said:
just a quick add on Mobile Odin and stock ND8/NDC don't mix at all
Click to expand...
Click to collapse
6th_Hokage said:
cause they need the ND8 base to work as intended...my suggestion would be to get the usb port on your phone fixed but i don't know how expensive that will be
Click to expand...
Click to collapse
I was afraid you would say that.
Holy crap. May I say, I am quite impressed. I never planned on rooting my S3 (I like it that much!) but this just looked so damn easy to do and it was!
For the curious! I have a Virgin Mobile S3, and I'm on Kitkat 4.4.2, baseband NDC. Verified root with Root Checker Basic. No problems with mobile data.
Many thank yous, 6th_Hokage!
strangelady said:
Holy crap. May I say, I am quite impressed. I never planned on rooting my S3 (I like it that much!) but this just looked so damn easy to do and it was!
For the curious! I have a Virgin Mobile S3, and I'm on Kitkat 4.4.2, baseband NDC. Verified root with Root Checker Basic. No problems with mobile data.
Many thank yous, 6th_Hokage!
Click to expand...
Click to collapse
your welcome strangelady and if you want check out the links in my signature area for other cool stuff
added two more t=root methods
So I recently updated to the I747MVLUFNF2 update in Kies from the I747MVLUFNE6 Update and I can't seem to root it using towelroot (I keep getting a phone unsupported message). Is there another method to root the phone without tripping KNOX?
Not without tripping the Warranty Bit, no. But most of the older methods of rooting will still work.
DocHoliday77 said:
Not without tripping the Warranty Bit, no. But most of the older methods of rooting will still work.
Click to expand...
Click to collapse
I understand once I root it with CF Auto Root then the warranty bit is tripped, but does this prevent me from using my phone with kies to update or backup? Or what exactly happens?
It just means you cannot use Knox for secured storage. The vast majority of us hate knox anyway so you might actually call this a win!
Of course it also means they can refuse warranty services, but most never need this, and many have reported their warranty being honored regardless.
Otherwise, it has no other effect on how you use your device, flash roms, root, etc.
I have the same issue.
I don't care about knox... but rooting it with the other ways that I know installs the super user app properly but then the SU app keeps crashing... I was assuming it was because of knox but now I'm not sure anymore, tried to reset it and to reflash the rom twice and every time it did the same thing...
Do you have any ideas why that might be happening?
I really would need a solution as I hate unrooted 4.4.2... :S
Thank you!
After rooting, you should be able to open SuperSU and it'll update its binary if needed and will disable knox.
Did you do that part?
I did try to update SU... The result was the same... the SU app would crash when I tried to launch it, before it even gives you the screen to disable knox... Trying to download the slightly older I747MVLUFNE6 which hopefully will root better...
You cant downgrade firmware. You could flash a rom, but i dont think that's what you were getting at.
How did you try to root? Have you tried using the oldest method we've got? Seems to never fail when others do!
Flash custom recovery with Odin.
From recovery flash the SuperSU update zip. You can find it by going to chainfires thread. (Its also in my sig bit I haven't added the very latest version yet)
Yeah, I realized my stupidity after posting the last message... I was thinking of flashing the older rom in... but that would have crapped out...
Finally got it to work...
Thought I had tried it before... but now I kind of doubt myself >.>
Reflashed the same version of the rom ... Found a really old version of auto-root, flashed it in... then I could update SuperSU and it disabled Knox...
Should have tried a bit harder before posting... sorry about that...
Thank you very much for your help.
Bob Terwilliger said:
Yeah, I realized my stupidity after posting the last message... I was thinking of flashing the older rom in... but that would have crapped out...
Finally got it to work...
Thought I had tried it before... but now I kind of doubt myself >.>
Reflashed the same version of the rom ... Found a really old version of auto-root, flashed it in... then I could update SuperSU and it disabled Knox...
Should have tried a bit harder before posting... sorry about that...
Thank you very much for your help.
Click to expand...
Click to collapse
Hi Bob
please witch version of auto-root have you use ?
The one I used was hard to find. Most people only post a link to Chainfire's website when making a rooting tutorial. This was a problem because Chainfire updated his official auto-root release with the latest SuperSU apk, making it impossible to update...
http : // androidxda . com / root - samsung - galaxy - s 3 - sgh-i747m
(can't post links yet, apparently...remove all spaces from previous line after copying it to address bar)
The guy from the above website decided to go the longer way of uploading an auto-root that he re-zipped himself. Not sure why he did that but it was perfect for what I needed.
Just download and unzip the auto-root that he provided and you'll be able to root your 4.4.2 SGH-I747M.
Bob Terwilliger said:
The one I used was hard to find. Most people only post a link to Chainfire's website when making a rooting tutorial. This was a problem because Chainfire updated his official auto-root release with the latest SuperSU apk, making it impossible to update...
http : // androidxda . com / root - samsung - galaxy - s 3 - sgh-i747m
(can't post links yet, apparently...remove all spaces from previous line after copying it to address bar)
The guy from the above website decided to go the longer way of uploading an auto-root that he re-zipped himself. Not sure why he did that but it was perfect for what I needed.
Just download and unzip the auto-root that he provided and you'll be able to root your 4.4.2 SGH-I747M.
Click to expand...
Click to collapse
Using the zip you provided, which version of SU did you use?
The auto-root tar in the zip the guy provided on his site is dated 2014-2-27 11:13.
Bob Terwilliger said:
The auto-root tar in the zip the guy provided on his site is dated 2014-2-27 11:13.
Click to expand...
Click to collapse
i have tried this one but it doesn't solve my problem, SuperSU crashed when it start, i don't understand what is the cause :crying:
It'll work... SuperSU crashing is normal... you need to go to the play store and update SuperSU... after that you'll be able to run the app and disable Knox.
Bob Terwilliger said:
It'll work... SuperSU crashing is normal... you need to go to the play store and update SuperSU... after that you'll be able to run the app and disable Knox.
Click to expand...
Click to collapse
thanks bob, i discover that the problem was about the I747MVLUFNF2 rom, so I changed it by I747MVLUFNE6 and all ok now
thank you again :good:
I did the opposite. I flashed the latest version of CF-Auto-Root from http://autoroot.chainfire.eu/. SuperSU was crashing, so I re-flashed the latest version of SuperSU (v2.01) from http://download.chainfire.eu/supersu and it worked fine after that. This was on the I747MVLUFNF2 ROM.
DocHoliday77 said:
Not without tripping the Warranty Bit, no. But most of the older methods of rooting will still work.
Click to expand...
Click to collapse
I've also updated to the latest firmware for gs3-1747m and tried to root using these new rooting tools that are on the device itself. Can you elaborate on an older version that would work on the device? My data pins on the mico-usb port were damaged, so I cannot transfer any data with a PC. Can't use Odin or other devices that require USB debugging
Thanks!
If Towelroot doesn't work, there is no other way to root without using Odin and a PC.
Sent from my SAMSUNG-SGH-T999 using Tapatalk
hey
aryan.yazdani said:
I've also updated to the latest firmware for gs3-1747m and tried to root using these new rooting tools that are on the device itself. Can you elaborate on an older version that would work on the device? My data pins on the mico-usb port were damaged, so I cannot transfer any data with a PC. Can't use Odin or other devices that require USB debugging
Thanks!
Click to expand...
Click to collapse
Actually... PM me, I'll tell you how I did it.
Hi friendly xda android enthusiasts. I have, after many issues, finally rooted my gt-n5110 using odin and cf-auto. Workered without a hitch. Odin passed, tab rebooted, and BAM, "superSU has stopped working". I immediately navigated myself over to the playstore to reinstall SuperSU and for the first time i have ever seen it wouldnt allow me to. It only gave me a choice to open. No update no uninstall. Going into my apps list it was not present on downloads but was available on device list. Clucked it and no option to uninstall, only to force stop or turn off. So it is incorporated as a system with no access to it. This has me stumped. I have only seen old threads with answers to this and they are temp fixes. Need to know what i can do to fix this on a permanent basis and if someone could help me understand how and why this issue occured it would give me a better understanding and possibly prevent further issues. Thanks in advance guys.
Try the flashable version in this post after you install a custom recovery with odin.
ramjet73
ramjet73 said:
Try the flashable version in this post after you install a custom recovery with odin.
ramjet73
Click to expand...
Click to collapse
This may be a very stupid question but i have to be sure. As i stated the odin DID pass the auto root and tab rebooted. But along with the superSU error i ran root checker and was unable to obtain root. Im assuming its because supersu is not embedded. So with that said is it still ok to attempt to flash a recovery to the tab?
mattdiehl83 said:
This may be a very stupid question but i have to be sure. As i stated the odin DID pass the auto root and tab rebooted. But along with the superSU error i ran root checker and was unable to obtain root. Im assuming its because supersu is not embedded. So with that said is it still ok to attempt to flash a recovery to the tab?
Click to expand...
Click to collapse
Yes. Recovery is independent of whether or not you are rooted. You can install it from Android using tools like Flashify once you are properly rooted, but Odin works fine as long as you have a version of recovery in that format.
Flashing SuperSU from a custom recovery once it is installed should fix the superuser problems you are having.
ramjet73
ramjet73 said:
Yes. Recovery is independent of whether or not you are rooted. You can install it from Android using tools like Flashify once you are properly rooted, but Odin works fine as long as you have a version of recovery in that format.
Flashing SuperSU from a custom recovery once it is installed should fix the superuser problems you are having.
ramjet73
Click to expand...
Click to collapse
Doing now. Thankyou. Fingers crossed.
I had the same issue on my 5110. The flashable root only worked for me until I rebooted, then it would lose root. What ultimately worked for me was to unroot with Kingo. Then with USB debugging enabled, re-rooted with Kingo (which took around 10 min).
Sent from my AT&T Galaxy Note 3 using Tapatalk®
andygev35 said:
I had the same issue on my 5110. The flashable root only worked for me until I rebooted, then it would lose root. What ultimately worked for me was to unroot with Kingo. Then with USB debugging enabled, re-rooted with Kingo (which took around 10 min).
Click to expand...
Click to collapse
If flashing SuperSU from recovery doesn't result in a successful rooted system someone should let @Chainfire know. I've never had a problem rooting a stock ROM that way but let's see what @mattdiehl83 reports.
ramjet73
OS X
ramjet73 said:
If flashing SuperSU from recovery doesn't result in a successful rooted system someone should let @Chainfire know. I've never had a problem rooting a stock ROM that way but let's see what @mattdiehl83 reports.
ramjet73
Click to expand...
Click to collapse
Not near pc. Only have OS X available now. Can anybody walk me through using OS X to flash?
mattdiehl83 said:
Not near pc. Only have OS X available now. Can anybody walk me through using OS X to flash?
Click to expand...
Click to collapse
The recovery? I don't know if there is an OS X version of Odin.
ramjet73
ramjet73 said:
The recovery? I don't know if there is an OS X version of Odin.
ramjet73
Click to expand...
Click to collapse
I am wondering what flashing tool to use with OS X. Odin is for windows. I know of heimdall but that requires ALOT to flash anything. Wondering if there is another odin like tool for OS X
You could try this: http://forum.xda-developers.com/showthread.php?t=2598203
Sent from my AT&T Galaxy Note 3 using Tapatalk®
done.
Hi guys sorry for the delay in update. I ended up using VM ware and it allowed to operate as windows on OS X. I installed TWRP, went into the file manager in TWRP and removed the superSU, i then flashed superSU and rebooted. Once back to the tablet i went and restored services to superSU and went into the play store. And finally the playstore gave me the option the update the superSU. And then the rest was all normal installation of superSU. Hope this thread helps anybody dealing with these issues.
Glad you got it working. :good:
This post in the CF-Autoroot thread might be helpful as well.
ramjet73
there is a easy way to fix it!
download supersu 2.02 and install ta da and it works
2.01 does not work with n5110 well if you flash cf auto root
hmmmm.....
Bordo_Bereli51 said:
there is a easy way to fix it!
download supersu 2.02 and install ta da and it works
2.01 does not work with n5110 well if you flash cf auto root
Click to expand...
Click to collapse
Tada..your a genius. Oh wait i believe i stated it didnt have that option it was disabled. Yes i decided scarcasm would be fitting due to the fact it says ALL OVER xda to please read before you post.
mattdiehl83 said:
Tada..your a genius. Oh wait i believe i stated it didnt have that option it was disabled. Yes i decided scarcasm would be fitting due to the fact it says ALL OVER xda to please read before you post.
Click to expand...
Click to collapse
I read all the post and didnt found something
YOU DONT NEED TO DELETE SUPERSU 2.0.1
Install 2.02 apk and go to supersu, then to settings and push to /system
This is the easiest way. the one you found: go to recovery delete that and this. download supersu 2.0.2 apk and install it not the recovery zip i mean the APK! i didnt say the flashable supersu zip.
oh wait, yes you are a intelligent boy, you know everything.
mattdiehl83 said:
I am wondering what flashing tool to use with OS X. Odin is for windows. I know of heimdall but that requires ALOT to flash anything. Wondering if there is another odin like tool for OS X
Click to expand...
Click to collapse
That's a bit of a dilemma.
Unfortunately Samsung does not support using fastboot and bootloader mode (they call it download mode) so that standard SDK tool Google provides for Windows, Linux and MAC OS X isn't applicable. Your best bet would be to find a Windows PC that you can use to flash the recovery with Odin since that is the most common and best documented method.
Edit: NVM, somehow I responded to an old post of yours.
ramjet73
tried to root my phone and ran CF auto root...everything went smooth with odin but not phone is stuck on boot screen and i cant boot into recovery....only download mode.
That happend to me as well and I just went back into download mode and flashed the regular S6 root for tmobile
http://forum.xda-developers.com/tmobile-galaxy-s6/help/cf-auto-root-tmo-s6-t3069386
Tweezydak1d said:
That happend to me as well and I just went back into download mode and flashed the regular S6 root for tmobile
Click to expand...
Click to collapse
I have the same problem. tried your suggestion, I get a boot loop after flashing S6 Auto root. I guess I have to wait for Chainfire to come up with an update for S6 Edge.
STUCK - Same Issue
So I'm stuck at the Samsung screen even after using the recommended ODIN version v3.10.6. Does anyone have the factory image for SM-G925T to restore using Kies? Is there something else I can try? I can't get into recovery mode using the posted button combinations.
Hey sorry it didn't work for you. Like I said I was in the same situation as you and sombody suggested it to me in the cf auto root thread and it worked for me. Once again my oppologies
Was the suggestion to use a different root image or a different version of Odin? I have not tried a different root image.
Tweezydak1d said:
Hey sorry it didn't work for you. Like I said I was in the same situation as you and sombody suggested it to me in the cf auto root thread and it worked for me. Once again my oppologies
Click to expand...
Click to collapse
elite04 said:
Was the suggestion to use a different root image or a different version of Odin? I have not tried a different root image.
Click to expand...
Click to collapse
The suggestion was to use different root image. I had already downloaded the Odin that was recommend in the forum I believe the Odin I used was 3.10.6 and I used the galaxy S6 root image. Also I took the first ota before I did this
SUCCESS!!
BINGO!!! I used the SM-G920T root image and it worked!!!!
elite04 said:
Was the suggestion to use a different root image or a different version of Odin? I have not tried a different root image.
Click to expand...
Click to collapse
I haven't had any luck :crying: did anyone encrypt or enabled Knox before trying to root? because I had enabled all those before rooting, maybe that's why I can't root.
I tried rooting my phone yesterday using CF's root for SM-G925T and Odin 3.10.6, but it just got stuck on the boot screen. I tried to fix my phone several times using different versions of Odin, using different computers and nothing, then I just tried one last thing before sending my phone back to T-mobile - I rooted my phone using the file for the regular S6 (SM-G920T) and voila!! My phone came back to life and it's been working great with no issues.
For now make sure to root your S6 Edge using the root method for the regular S6.
elite04 said:
BINGO!!! I used the SM-G920T root image and it worked!!!!
Click to expand...
Click to collapse
Right on glad it worked for you
Does anyone know what are the differences between G920T and G925T? (And I don't mean 5 ) besides of one being for S6 and S6 edge. Any difference in functionality? (I assume they had a reason for the two variants).
I got the root to work but I can't boot into recovery...the screen flashes and freezes...any suggestions
you folks who successfully rooted; did you root before the OTA, or did you take the OTA, and then root?
thanks, waiting for my phone today!
wase4711 said:
you folks who successfully rooted; did you root before the OTA, or did you take the OTA, and then root?
thanks, waiting for my phone today!
Click to expand...
Click to collapse
Afterwards
any idea what was in that update?
It wasn't the memory leak fix or cell standby fix I know that lol
Sent from my SM-G925T using XDA Free mobile app
I tried the S6 root file and it just bootloops. The S6 Edge file just gets stuck on the bootscreen. Any suggestions?
After rooting, does the Knox flag get tripped to like 0x1? And with the Knox flag tripped, does the fingerprint security still work?
And I wonder if a tripped Knox flag will affect future Samsung Pay functionality?