Related
Hey there,
today my N7100 surprised me by anouncing that there is a firmware update available. Must be that 4.2(.2). [edit: no, unfortunately it's just a security update] In all my years with my i9000 I never OTA updated because I was always on custom ROMs and like lightyears ahead of the official update cycle, but now I'm uncertain.
Of cause I want to keep root / reroot at least for AFWall and especially the 240dpi is very important to me... will OTA override those settings, going along with those as well the Xposed settings? Any experiences yet?
And if, will rooting and Triangle away work like before on the new version as well? I am as the title says on the stock 4.12 with root and counter reset according to this manual: http://forum.xda-developers.com/showthread.php?t=1896696
On my SGS I'd just give it a shot, but the Note is just like a month old (so me still a bit nooby) and at the moment I don't need&want to mess around with it too much - Especially because all this counter stuff is bugging me ^^
Any advices? I know that's probably not really helpful, but probably someone has the same concerns too and just wants to share his thoughts too
Guess unrooting before OTA updating would be the safest way anyway.. wouldn't it be? ... Kinda have a lack of motivation here ^^
I think that is just a security update. There is still no word on 4.2.2 yet
Sent from my GT-N7100 using xda app-developers app
hendog4385 said:
I think that is just a security update. There is still no word on 4.2.2 yet
Click to expand...
Click to collapse
Good point, found this: http://www.sammobile.com/2013/06/18...ty-update-galaxy-note-ii-still-android-4-1-2/
Questions still persist though..
Adjusted the thread title and initial post to reduce confusion.
Yeah previous 4.1.2 rooting method will work latest too.
OR simply flash prerooted ROM, no need to reset counter/Root.
Read Prerooted ROM in my signature, i have just posted latest XXDMF2
dr.ketan said:
Yeah previous 4.1.2 rooting method will work latest too.
OR simply flash prerooted ROM, no need to reset counter/Root.
Read Prerooted ROM in my signature, i have just posted latest XXDMF2
Click to expand...
Click to collapse
Awesome! Thanks! (will give it a shot as soon as I have a bit mroe time and want to reboot into WIndows. A shame that there's no proper - as easy to use as ODIN - alternative for Ubuntu)
Is this usual, that flashing stock with some extra apks like the su stuff doesn't increase the counter? Or is it that just flashing PDA doesn't affect it? Am curious..
Samsung bootloader only check custom recovery /kernel for flash counter setting. So it can't detect these applications. On prerooted rom everything remains as it is except pushing su +super user +busybox.
Sent from my GT-N7100 using xda premium
XXDMF2 is probably the same as XXDME2 except they could only be bothered to work on/release that geographic variation last?
dr.ketan said:
Samsung bootloader only check custom recovery /kernel for flash counter setting. So it can't detect these applications. On prerooted rom everything remains as it is except pushing su +super user +busybox.
Click to expand...
Click to collapse
That's great thanks. So basically I could as well push some more apps with my installation by following your, how I find very clear and nice to follow, Tutorial in your Pre-Rooted-Thread and varying the step where the superuser.apk is being added from:
Code:
cp Superuser.apk temp/app/Superuser.apk
chmod 0644 temp/app/Superuser.apk
to
Code:
cp Superuser.apk temp/app/Superuser.apk
chmod 0644 temp/app/Superuser.apk
cp myFavoriteApp.apk temp/app/myFavoriteApp.apk
chmod 0644 temp/app/myFavoriteApp.apk
Right? So this way I could have a Stock ROM that comes with my usual App Setups by default when flashing and still leaves my Counter untouched..That's just wonderful, spares a lot of time after wiping..since in this case there is no wipe that's not needed here I know, but having a clean phone without having to install everything manually again would be nice anyway.
Wondering what weird things would happen if I tried to install apk's that are already installed.. will they be skipped..guess so, I mean, superSU is installed as well here already.. ?
Thanks for teaching me A pleasure to learn
When you push applications to rom that install to system rom of your device and that is limited space, so no good idea to push multiple applications.
Sent from my GT-N7100 using xda premium
dr.ketan said:
When you push applications to rom that install to system rom of your device and that is limited space, so no good idea to push multiple applications.
Click to expand...
Click to collapse
Ah I see, sounds reasonable... thanks for clearing that up!
Hey guys, im on the same state like the op.
i have stock rom, but rooted with odin and on TWRP recovery, busybox, superuser and triangleaway.
can i easily run this update without issues or should i completely go back to stock?
thanks, greetz, hope for a fast answer :|
Done! Without problems. but iam lose root, busybox and su
I updated yesterday, rooted stock 4.1.2 with xposed. Flashed new non-rooted (original) ROM from SAM mobile.
upon flashing, I had to
1) root agiain
2) install SU again from apk,
3) run SU and it updated binary
4) run Triangle away and reset counter
5) run Xposed framework and press "install", reboot
6) run busybox and let it auto-install
Then I was able to manualy change sounds for keypress/press and bootanimation.
All well.
D,
Just flashing stock prerooted ROM, you can skip first 4 steps
WARNING: Following any of these instructions WILL void your warranty,
and could possibly cause irreparable harm to your device (i.e. bricked)
If you do Not understand these risks, stop here and do Not proceed.
If you do Not know how to use Odin, stop here and do Not proceed.
This guide is ONLY for SGH-T999 variants that are ALREADY RUNNING android 4.3
If you do Not have a SGH-T999 variant, stop here and do Not proceed.
If you are Not currently running android 4.3, stop here and do Not proceed.
I am not responsible for anything that happens to your device. YOU chose to follow this guide.
I have the SGH-T999V (samsung galaxy S3, canada, Videotron)
I flashed the full 4.3 firmware from samsung-updates.com as soon as it became available ... and then I tried to root it the usual ways
However knox prevented the superSu app from running, and it closed immediately, and obviously root was Not available to any app
This method will obtain ROOT and REMOVE the knox garbage
note ... altho it is optional to remove knox, I have Not tested without removing knox and do Not know if root will work using this method (guide) with knox still installed !
I did NOT create this method ... I simply found it, read thru user comments, and used it
FULL CREDIT goes to
@upndwn4par for the method ... the thread is here
@Kaito95 for the Knox Removal script ... the thread is here
@Dees_Troy for the TWRP recovery
@Chainfire for SuperSu
as you can see, this method was for the AT&T, Rogers, Bell, Telus Samsung Galaxy S3 ... I747 variants, I believe
So here is how I achieved a successful root on 4.3 using the above method, with adjustments for our T999 variant
Using Method #2
1. Download required files
a) download Odin 3.07 to your PC
b) download the latest TWRP recovery for your device, in TAR format, to your PC
click on your device here
scroll down on your device page to the section called Download - Odin Flashable Tar
below that, click on the Select the latest .tar file from here link
scroll to the bottom of the files and click on the latest TAR version
note to d2tmo users ... thanks to @Perseus71 it has been noted that 2.6 versions may have issues on your device, and it is recommended that you choose the 2.5.0.0 TAR version
example: Mine looks like this: openrecovery-twrp-2.6.3.0-d2can.tar
note to T999V users ... both d2can and d2tmo work for our device ... I personally use d2can
c) download SuperSu 1.65 zip to your DEVICE
c) download Knox Removal zip to your DEVICE
2. Reboot into Download mode ... VolumeDOWN + Power + Home
Run Odin
make sure that re-partition is NOT checked!
click the PDA button and point to the TWRP recovery TAR file that you downloaded above
connect your device to the computer ... wait briefly
the COMM port in top left box should turn blue
click Start
when it is done, PASSED, and phone has rebooted, disconnect device
3. Reboot into Recovery mode ... VolumeUP + Power + Home
Flash (install) the Knox Remover zip
Flash (install) the SuperSu zip ... it is version 1.65, current is 1.80, so it will prompt us to update later :good:
Reboot System
4. Update SuperSu from the Play Store
5. Open SuperSu
it should prompt that it needs to update the binary
accept and let it update the binary the Normal way
6. Reboot
7. Enjoy rooted 4.3, knox-free :laugh: :good:
thanks again to @Perseus71 for noting that it is possible that the default Enforcing mode of SElinux may cause issues with the ability and/or performance of some root apps despite being granted root permission
if you are experiencing similar issues, he recommends that you check out the SELINUX Status Changer app.
[I have Not personally tested this app]
reserved
in case
You may also wish to mention the SELINUX Status Changer. Here's the Thread.
With it enabled, root won't be stable.
Ahem. First ?
EDIT - TWRP 2.6.x.x has trouble remounting and formatting /Data. You may wish to reccomend version 2.5.0.0
Perseus71 said:
You may also wish to mention the SELINUX Status Changer. Here's the Thread.
With it enabled, root won't be stable.
Ahem. First ?
EDIT - TWRP 2.6.x.x has trouble remounting and formatting /Data. You may wish to reccomend version 2.5.0.0
Click to expand...
Click to collapse
hi and thanks for your input
I just looked at that SELINUX Status Changer thread and will keep an eye on it ... but for now I won't add it cuz:
the dev says it is pre-alpha version
Mine is Enforcing and root seems stable and hasn't had any problems, yet ... 4 days so far
SElinux is here to stay, and there's a big difference between proper (Google) implementation and samching implementation ... root blocked by samching, but not by standard android enforcing #BAM
congrats on being first, lol
what kind of things are you referring to when you say that root won't be stable?
what is your device d2 id?
I haven't had any problems with twrp 2.6.3 for d2can
THAT is something I WILL add, for your specific device
any particular reason you're recommending all the way back to 2.5 instead of just earlier 2.6 version?
cLogic said:
what kind of things are you referring to when you say that root won't be stable?
what is your device d2 id?
I haven't had any problems with twrp 2.6.3 for d2can
THAT is something I WILL add, for your specific device
any particular reason you're recommending all the way back to 2.5 instead of just earlier 2.6 version?
Click to expand...
Click to collapse
I have D2TMO AKA SGH-T999. Yes this is specific to my variant. I tested all the 2.6.x versions to establish that the /Data Problem exists in all these versions.
As to Root, well, Certain apps such as Nandroid Manager, and other apps have difficulty performing Root operation despite SuperSU granting it. @Aerowinder has a lot of stories. May I suggest you please visit the D2TMO Leaked 4.3 Rom thread in development for more details ?
Perseus71 said:
I have D2TMO AKA SGH-T999. Yes this is specific to my variant. I tested all the 2.6.x versions to establish that the /Data Problem exists in all these versions.
As to Root, well, Certain apps such as Nandroid Manager, and other apps have difficulty performing Root operation despite SuperSU granting it. @Aerowinder has a lot of stories. May I suggest you please visit the D2TMO Leaked 4.3 Rom thread in development for more details ?
Click to expand...
Click to collapse
fair enough ... thanks again for your input ... OP updated
Did this to the letter and soft bricked as soon as I flashed the mod zip in twrp. Stuck on pulsing samsung logo.
Had to reflash. Tried twice just to be sure.
(T999) (root, 4.3 stock)
trepoman said:
Did this to the letter and soft bricked as soon as I flashed the mod zip in twrp. Stuck on pulsing samsung logo.
Had to reflash. Tried twice just to be sure.
(T999) (root, 4.3 stock)
Click to expand...
Click to collapse
what do you mean ... bricked as soon as you flashed mod zip? you mean the knox removal script?
not sure how that's even possible
if you see the pulsing logo, then you rebooted
your T999 is rooted?
meaning it was before, or everything was fine after you did it twice?
cLogic said:
what do you mean ... bricked as soon as you flashed mod zip? you mean the knox removal script?
not sure how that's even possible
if you see the pulsing logo, then you rebooted
your T999 is rooted?
meaning it was before, or everything was fine after you did it twice?
Click to expand...
Click to collapse
The native tether mod. Knox remover worked fine.
Phone is rooted, stock 4.3.
Flashed tether mod in twrp recovery, which succeed but phone would not boot past the pulsing Samsung afterwards (10 minutes of pulsing, never booted past that) nor would it boot to recovery. I could get to boot loader luckily. I pulled the battery and tried again, same thing. Flashed stock 4.3 in Odin to get phone alive, tried flashing tether mod again, exact same result and same solution. HTH.
So close to clicking buy now on a nexus 5...
trepoman said:
The native tether mod. Knox remover worked fine.
Phone is rooted, stock 4.3.
Flashed tether mod in twrp recovery, which succeed but phone would not boot past the pulsing Samsung afterwards (10 minutes of pulsing, never booted past that) nor would it boot to recovery. I could get to boot loader luckily. I pulled the battery and tried again, same thing. Flashed stock 4.3 in Odin to get phone alive, tried flashing tether mod again, exact same result and same solution. HTH.
So close to clicking buy now on a nexus 5...
Click to expand...
Click to collapse
ummm .. not sure what this tether mod is that you are talking about, but it's not part of this guide, lol
this guide simply flashes the knox removal script (to delete knox files) and superSu (to root)
cLogic said:
ummm .. not sure what this tether mod is that you are talking about, but it's not part of this guide, lol
this guide simply flashes the knox removal script (to delete knox files) and superSu (to root)
Click to expand...
Click to collapse
Confounded facts. Always kicking my ass.
This is what happens when I stay up too late and try to do too many things. Linked from another thread and had too many tabs open.
Delete.
Thanks for the post. Sadly, no dice for me. I was directed to this post after creating my own. I've really held off asking for help, but only conclusion I can come to is I got one of those phones that just flat out won't root. Tried everything I can think of. Samsung Galaxy s3, SGH-T999v, 4.3, Wind (Canada). The Odin steps worked, when I boot into recovery, just get the stock android recover menu (original issue I've been having). Nothing seems to work in the slightest.
So I followed this to the letter and it all went well. Except, while the device seems to be rooted, SuperSU seems to be granting permissions to apps, Root Check Pro reports the device is rooted... I still can't use any apps that require root access. GameCIH doesn't work. ROM Manager doesn't work. Nothing wants to work.
Why is this happening? Because every step seemed to go flawlessly. Also, I have no idea how to put it back to stock if I wanted to try and start over lol.
[EDIT]
Oh yeah. Pertinent information. Samsung Galaxy S3 T999V through Mobilicity (Canada) running 4.3.
Used the 2.5 tar rather than the 2.6.
Also set SElinux to permissive.
ksec said:
Thanks for the post. Sadly, no dice for me. I was directed to this post after creating my own. I've really held off asking for help, but only conclusion I can come to is I got one of those phones that just flat out won't root. Tried everything I can think of. Samsung Galaxy s3, SGH-T999v, 4.3, Wind (Canada). The Odin steps worked, when I boot into recovery, just get the stock android recover menu (original issue I've been having). Nothing seems to work in the slightest.
Click to expand...
Click to collapse
are you sure you're running stock 4.3 ? baseband MK5 ?
re-do the Odin steps, except uncheck the auto reboot option .. so that it stops after successfully pushing the recovery tar
unplug the phone from the pc .. it should still be in download mode
pull the battery
then put it back in
boot into recovery immediately
if you see the TWRP recovery, great!, complete the guide and you'll be knox free and rooted
if that worked then there are two files that you seem to still have that are putting stock recovery back on normal boot .. post results here and I'll find them for you
Ergonyx said:
So I followed this to the letter and it all went well. Except, while the device seems to be rooted, SuperSU seems to be granting permissions to apps, Root Check Pro reports the device is rooted... I still can't use any apps that require root access. GameCIH doesn't work. ROM Manager doesn't work. Nothing wants to work.
Why is this happening? Because every step seemed to go flawlessly. Also, I have no idea how to put it back to stock if I wanted to try and start over lol.
[EDIT]
Oh yeah. Pertinent information. Samsung Galaxy S3 T999V through Mobilicity (Canada) running 4.3.
Used the 2.5 tar rather than the 2.6.
Also set SElinux to permissive.
Click to expand...
Click to collapse
did you go into superSu and update it's binary?
what do you mean, exactly, by apps won't work ?
do they run? you said they are being granted permission.
how were they installed?
we're they restored using Titanium?
the 2.5 TWRP was recommended for tmobile users.. we are T999V, can use d2can 2.6.3.0 or d2tmo 2.6.3.1
cLogic said:
did you go into superSu and update it's binary?
what do you mean, exactly, by apps won't work ?
do they run? you said they are being granted permission.
how were they installed?
we're they restored using Titanium?
the 2.5 TWRP was recommended for tmobile users.. we are T999V, can use d2can 2.6.3.0 or d2tmo 2.6.3.1
Click to expand...
Click to collapse
I updated the the SuperSU binary.
The apps will open but when it attempts to do anything requiring root access it is denied or fails.
SuperSU and Knox were installed through the TWRP recovery boot thing as the guide specified. Other things were either installed from the app store or downloaded APK files. I didn't have Titanium at the time I attempted rooting my phone. Wasn't mentioned in the guide so I never got it. I have the basic version now from the play store now. As I'm sure you can tell, I've never rooted my device before. Always had a friend do it for me.
Should I just restore to a stock install (not sure how to do this) and then try again? Especially now that I know the 2.5 warning was specifically for T-Mobile users? Or can I just put the 2.6X version on my phone and try again? lol
it's working
@ cLogic
Thanks a lot man, thanks to you I successfully root my sgh-t999v (stock android 4.3)
I've managed to use GooManager from the Google Play store to install latest TWRP and to flash the 4.3 mod.
Having issues when trying this. I followed all the steps and received no errors. But when the SuperSu ap tries to open on my phone it crashes, the ap only phone is stable.
I have Tomo G3 4.3 Stock rom
Flashed the TW 2.5.0.0 version
Rebooted into the touch recovery
Ran Knox removal
Ran SuperSu
Booted
Knox is not in my list off apps
SuperSu does show
Cant not open supersu, updating binarys does not work since the app crashes.
(Edit)--> Redid the whole process but did not let the phone reboot during the TW flash and the Zip installs. Seemed to of fixed the issue. (Edit)
Thanks added
I flashed Stock 4.3 via Odin before coming across this guide and now my device seems to be stuck at the boot screen. My question is, if I haven't completely booted, can I reflash using the modified version of 4.3 (root, deodexed, knox removed)? Do I have any other options right now?
Hello everyone, so AT&T updated my phone and foxfi used to work just fine for hotspot but since Android 4.3 I can't so I need to root. I've seen a few threads in this site on some roots but don't get much info about them. How can I root my GS3 running 4.3? I've never rooted in my life so I'm making sure I do this right the first time . If anyone can please help me get the proper root for my GS3. I'm not wanting all these custom roms and stuff. I just want to be able to have free wifi hotspot and also a way to remove all that crap Bloatware.
Someone I'm another thread asked but I think it's for the Verizon version only? Link: http://forum.xda-developers.com/showthread.php?t=2565758
I just need some help finding a way to root. Thanks for reading!
Questions and Help issues go in Q&A and Help section
Thread moved
Thanks
FNSM
kennyglass123 said:
Questions and Help issues go in Q&A and Help section
Thread moved
Thanks
FNSM
Click to expand...
Click to collapse
My bad, using my phone to post this and got the wrong section. Thanks for moving it.
Same problem
Gotnitro said:
Hello everyone, so AT&T updated my phone and foxfi used to work just fine for hotspot but since Android 4.3 I can't so I need to root. I've seen a few threads in this site on some roots but don't get much info about them. How can I root my GS3 running 4.3? I've never rooted in my life so I'm making sure I do this right the first time . If anyone can please help me get the proper root for my GS3. I'm not wanting all these custom roms and stuff. I just want to be able to have free wifi hotspot and also a way to remove all that crap Bloatware.
Someone I'm another thread asked but I think it's for the Verizon version only? Link: http://forum.xda-developers.com/showthread.php?t=2565758
I just need some help finding a way to root. Thanks for reading!
Click to expand...
Click to collapse
- Has Anyone had an update to this yet? I am having the exact same issue where several things no longer allow me the permissions I once had. At&t sent out an update that kept popping up on my screen every five minutes for like 2 days so I Finally upgraded and I do not like the new version.
- I am especially ticked that they removed the option to hide Applications now. I use my phone for work and don't need clients and coworkers having easy access to personal apps and data since I collaborate on my phone quite a bit in meetings, plane rides etc.where my phone is passed around. So any new app I try to add also requires root access to do the trick and combined with not being able to use pdanet+ or foxfi to tether I have a big need to root now. I tried to root using GalaxyS3RootATT.zip - which did work on an earlier version of 4.2 but only ended up wiping my phone after the 4.3 update (i think this was the 2nd update for the same OS version 4.3) but it did install super user. However root test fail to show that it is properly rooted. Very Frustating and VERY nervous about Bricking my phone so I want to make sure its done right. Ive only rooted a handful of times every couple of years when I get a new phone and the process seems to change constantly due to so many codes and manufacturers and models and carriers etc.
Anyway please help ASAP. Thanks
http://forum.xda-developers.com/showthread.php?t=1963790
The instructions here worked like a charm after I upgraded to 4.3. Rest assured, CF auto root is compatible with the latest firmware. Just be very careful and follow the instructions meticulously.
First time rooter
Sorry if i don't understand whats going on this is the first time rooting for me.
I am trying to root my phone to be able to run 4.4 on it and have followed the steps to root it using odin3 and CF-Auto-Root but once i get back to my home page and try to use superSU I get an error message stating "Unfortunately, SuperSU has stopped." along with "Security information An application attempted to access system on your device without authorization. This attempt has been blocked".
Sorry if this is an easy fix or i left out important information but i would just like some help getting off the gound
woerner said:
Sorry if i don't understand whats going on this is the first time rooting for me.
I am trying to root my phone to be able to run 4.4 on it and have followed the steps to root it using odin3 and CF-Auto-Root but once i get back to my home page and try to use superSU I get an error message stating "Unfortunately, SuperSU has stopped." along with "Security information An application attempted to access system on your device without authorization. This attempt has been blocked".
Sorry if this is an easy fix or i left out important information but i would just like some help getting off the gound
Click to expand...
Click to collapse
You need to install a custom recovery in order to flash a custom ROM. You don't necessarily need root to load a custom ROM. Are you running a stock 4.3 ROM?
audit13 said:
You need to install a custom recovery in order to flash a custom ROM. You don't necessarily need root to load a custom ROM. Are you running a stock 4.3 ROM?
Click to expand...
Click to collapse
Right now it should be just stock 4.3 straight from At&t about 2 weeks ago
I tried following http://forum.xda-developers.com/showthread.php?t=1963790 and everything seamed to work during the process but now superSU doesn't work
Thank you for any help!
woerner said:
Right now it should be just stock 4.3 straight from At&t about 2 weeks ago
I tried following http://forum.xda-developers.com/showthread.php?t=1963790 and everything seamed to work during the process but now superSU doesn't work
Thank you for any help!
Click to expand...
Click to collapse
If you have knox installed, that could be interfering with root access.
audit13 said:
If you have knox installed, that could be interfering with root access.
Click to expand...
Click to collapse
I have not personally put Knox on the phone but when i go into settings/security/device administrators. It lists Knox as one with an unchecked box so dose that mean its on the phone? and if so how would i go about removing it.
also if i don't necessarily need to root to load a custom ROM where could i be directed to be able to load 4.4?
Thanks!
---------- Post added at 02:54 AM ---------- Previous post was at 02:35 AM ----------
audit13 said:
If you have knox installed, that could be interfering with root access.
Click to expand...
Click to collapse
The end result of what i want to accomplish is to load http://forum.xda-developers.com/showthread.php?t=2556839
again thank you for the help!
woerner said:
I have not personally put Knox on the phone but when i go into settings/security/device administrators. It lists Knox as one with an unchecked box so dose that mean its on the phone? and if so how would i go about removing it.
also if i don't necessarily need to root to load a custom ROM where could i be directed to be able to load 4.4?
Thanks!
---------- Post added at 02:54 AM ---------- Previous post was at 02:35 AM ----------
The end result of what i want to accomplish is to load http://forum.xda-developers.com/showthread.php?t=2556839
again thank you for the help!
Click to expand...
Click to collapse
so i think that my phone is rooted and i am trying to flash the ROM but the Error i am getting is...
set_metadata_recusive: some changes failed
E: Error executing updater binary in zip '.extern
Error flashing zip '/external_sd/Gummy-M. 1-02-27
Any Idea?
woerner said:
I have not personally put Knox on the phone...
Click to expand...
Click to collapse
The 4.3 OTA installs Knox without checking if you want it or not. Fortunately there are ways to remove it after the fact. Most suggestions I have seen recommend using CF-AutoRoot, updating SuperUser, and then going into SuperUser to disable Knox. You don't need root to install custom ROMs but as far as I know you need it to remove Knox. Removing Knox seems to be necessary in order to get the custom recovery required to flash custom ROMs.
|Guide|How-To| Root & Install Custom Recovery for 4.3 Update
[CWM][4.2.2/4.3/4.4] DE-SAMSUNGNIZER Script V5.0.0 - Clean all unneded Samsung Crap contains scripts to remove Samsung bloat and others that seem to just remove Knox.
I was about to offer no comment on the ROM to which you linked because it is in the Verizon forum, but then I noticed the d2lte in the description. My understanding is that d2lte is good for all US SGS3 variants. (Gummy says this in it's forum.) Maybe you can get around using a custom recovery with some ROMs, but the Gummy ROM comes as a recovery flashable zip. So, it looks like: root, remove knox, install custom recovery, flash rom.
---------- Post added at 10:26 PM ---------- Previous post was at 10:14 PM ----------
woerner said:
so i think that my phone is rooted and i am trying to flash the ROM but the Error i am getting is...
set_metadata_recusive: some changes failed
E: Error executing updater binary in zip '.extern
Error flashing zip '/external_sd/Gummy-M. 1-02-27
Any Idea?
Click to expand...
Click to collapse
From reading quite a few ROM threads I have learned that the updater scripts have code that indicates which devices they will work on and will cause the install to fail if you are trying to flash an incompatible ROM to a device. Sometimes these scripts have not been updated to reflect ROM compatibility with devices and editing the updater script will correct this. This is best verified in the ROM thread. Something to check for yourself before posting would be that you are using a compatible ROM version. The d2lte files should work with any of the US variants. If you downloaded one of the older files there is then the need to make sure it works with your device, unless you are confident about editing the script.
Other possible causes of your error:
1) it could be that the zip is on the external_sd and the installer expects it on the internal
2) you have a bad ROM download
From reading quite a few ROM threads I have learned that the updater scripts have code that indicates which devices they will work on and will cause the install to fail if you are trying to flash an incompatible ROM to a device. Sometimes these scripts have not been updated to reflect ROM compatibility with devices and editing the updater script will correct this. This is best verified in the ROM thread. Something to check for yourself before posting would be that you are using a compatible ROM version. The d2lte files should work with any of the US variants. If you downloaded one of the older files there is then the need to make sure it works with your device, unless you are confident about editing the script.
Other possible causes of your error:
1) it could be that the zip is on the external_sd and the installer expects it on the internal
2) you have a bad ROM download
Click to expand...
Click to collapse
Well i think i "Soft Bricked" my phone. currently stuck in a reboot loop but can still boot into recovery and download but nothing seams to be able to get me out of this loop
Look in the development thread for a way to flash back to stock 4.3.
Root problem solved
I have an AT&T S3 SGH-i747. The problems I had with rooting was all related to Knox, unfortunately I had no way to get rid of Knox.
Please follow the web link and follow all the steps in order. The short version of the steps is you install the TWRP recovery using Odin, then boot back into recovery , install SuperSU and then Knox removal script via recovery. After that enjoy whatever custom ROM you want. I'm running the KitKat 4.4 now :good:
As a note getting to the correct download link can be a pain due to the bait and switch of the "download now" button with other shareware apps but the links provided to lead you to the correct zip files.
** honai-android.blogspot.com/2014/02/how-to-root-galaxy-s3-at-sgh-i747-twrp.html **
SGHI-I747 4.3 root wifi tether
I have a SGHI-I747 4.3 I am wondering if I am able to root it with the instructions from http://forum.xda-developers.com/showthread.php?t=1963790&nocache=1 I do not see my phone listed.
I would like to disable knox also and enable wifi tether.
Any help would be much appreciated thanks.
CF-AutoRoot should work fine. But theres also Towelroot now, which is much, much, much easier!
After rooting with Towelroot, install SuperSU from the play store. Then open it and update the binary and disable knox.
DocHoliday77 said:
CF-AutoRoot should work fine. But theres also Towelroot now, which is much, much, much easier!
After rooting with Towelroot, install SuperSU from the play store. Then open it and update the binary and disable knox.
Click to expand...
Click to collapse
Sent from my LG-D851 using XDA Free mobile app
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.