Develop Bugs

Help for a somewhat new person.

I am new with rooting my phone. I have used Rooted phones before, I followed http://forum.xda-developers.com/showthread.php?t=2258633 Motochopper how to. I ran into a problem. I click the superuser app that was installed onto my phone, and it tells me that "The Superuser binary (su) must be updated. Please choose an installation method. Recovery mode installation is recommended for HTC devices." I click install and it tells me there was an error. I would like to root my phone along with potentially installing CWM so that I can easily install Cyanogenmod when they release a stable verison for the S4. Also would love to install titanium backup along with some Adfree apps.
Any help would be very much appreciated.

OK, so it looks like you already have it rooted.
When super SU asks that question, dont install via CWM, tell it to just install normally.
Once you have SuperSU working, Download Rom Manager from the play store and install CWM Recovery right from within the ROM Manager app.
It will give you the option to pick between two types of CWM(ClockWorkMod). The Touch version, like its name gives you the ability to use the touch screen and not only the volume up/down + Power button.

Telling it to install normally causes it to just tell me there was an error, it also tells me it is out of date as well. Titanium Backup tells me that it cant get root access and I was never asked about it.

OK, so your phone is not rooted then.
Your going to have to try rooting it again or flashing an already rooted rom with Odin.

I just tried it again, this time it said failure after the install of the superuser.apk. I just read that one of the later updates by samsung can make it harder to root. I just got my phone and i was fully updated. What Roms, are already rooted for the S4. I am actually enjoying some of the default apps that came with the phone.

Wicked (and most ROMs that don't include the [STOCK] tag) are pre-rooted...but you'll need to ODIN a custom recovery first then flash the ROM.
If you want to stay on rooted stock, follow the steps in the "root May 7 MDL" thread to ODIN a rooted kernel, and you'll be good to go.
(You don't need root access to get a custom recovery flashed)
Basically, any of your options are pretty straightforward, but they're going to involve Odin-ing stuff.

So there isn't really a way to just root my phone without installing a custom rom?

There was before the second update, with the second update rooting got just a little bit more steps
Sent from my SGH-M919 using xda premium

movieaddict said:
There was before the second update, with the second update rooting got just a little bit more steps
Sent from my SGH-M919 using xda premium
Click to expand...
Click to collapse
So is there a way to keep it stock but root it? What are the other steps I would have to take. Why does Samsung not like people rooting their phones, I thought carriers were the ones that hated people rooting their phones

Spud37 said:
So is there a way to keep it stock but root it? What are the other steps I would have to take. Why does Samsung not like people rooting their phones, I thought carriers were the ones that hated people rooting their phones
Click to expand...
Click to collapse
Are you still on the MDB firmware or have you done any over the air updates? Specifically the May 7 update which is MDL. Motochopper is specifically for then older firmware (MDB) and it won't work if you are already on the updated. MDL firmware. In which case you would have to follow these instructions to acquire root.
http://forum.xda-developers.com/showthread.php?p=41162041
I usually use a market app called root checker to quickly check if I do have root.
And yes you can be rooted on stock.
Sent from my SGH-M919

lazaro17 said:
Are you still on the MDB firmware or have you done any over the air updates? Specifically the May 7 update which is MDL. Motochopper is specifically for then older firmware (MDB) and it won't work if you are already on the updated. MDL firmware. In which case you would have to follow these instructions to acquire root.
http://forum.xda-developers.com/showthread.php?p=41162041
I usually use a market app called root checker to quickly check if I do have root.
And yes you can be rooted on stock.
Sent from my SGH-M919
Click to expand...
Click to collapse
Root checker says no root. I believe it does have that over the air update installed. T Mobile updated it when they gave me the phone, because they thought I didn't really know anything about phones. I assume this means I have to follow another method to root my phone?

If you have the MDL update you have to root using the steps listed here:
http://forum.xda-developers.com/showthread.php?t=2268880
Easily done, just a few more steps.

ronin4740 said:
If you have the MDL update you have to root using the steps listed here:
http://forum.xda-developers.com/showthread.php?t=2268880
Easily done, just a few more steps.
Click to expand...
Click to collapse
This is going to sound like a dumb question but from reading all of that I need to use ODIN to install the ROOT_M919?UVUAMDL onto the phone? that should root the phone and allow me to install ROM Manager and install CWM from there right?
Also would doing this delete everything I have on my phone right now?

Spud37 said:
This is going to sound like a dumb question but from reading all of that I need to use ODIN to install the ROOT_M919?UVUAMDL onto the phone? that should root the phone and allow me to install ROM Manager and install CWM from there right?
Also would doing this delete everything I have on my phone right now?
Click to expand...
Click to collapse
No, you use Odin to install one of the recoveries. You use the recovery to install the zip ROOT_M919?UVUAMD. Personally I didn't use that file. I installed the kernel in recovery and SuperSU in recovery. And no, it won't delete things on your phone.

Atmazzz said:
No, you use Odin to install one of the recoveries. You use the recovery to install the zip ROOT_M919?UVUAMD. Personally I didn't use that file. I installed the kernel in recovery and SuperSU in recovery. And no, it won't delete things on your phone.
Click to expand...
Click to collapse
Thank you so much, I am about to go and do this. I will use the kernel you suggested since that looks like a better option, after flashing the kernal should i reboot and just use it normally for a bit and then go to recovery and flash SuperSU?
EDIT: The steps on the thread for ODIN are for installing a rooted ROM, I am assuming its still the same steps for installing a recovery instead of a rooted ROM

Spud37 said:
after flashing the kernal should i reboot and just use it normally for a bit and then go to recovery and flash SuperSU?
Click to expand...
Click to collapse
If I remember right I just flashed them both at the same time. Just make sure you do the kernel first.
---------- Post added at 02:01 PM ---------- Previous post was at 01:59 PM ----------
Spud37 said:
EDIT: The steps on the thread for ODIN are for installing a rooted ROM, I am assuming its still the same steps for installing a recovery instead of a rooted ROM
Click to expand...
Click to collapse
The steps for Odin are for the stock rom, but yes, you use it the same way for a recovery.

Atmazzz said:
If I remember right I just flashed them both at the same time. Just make sure you do the kernel first.
---------- Post added at 02:01 PM ---------- Previous post was at 01:59 PM ----------
The steps for Odin are for the stock rom, but yes, you use it the same way for a recovery.
Click to expand...
Click to collapse
Okay I didn't get any error using ODIN, however when I try and boot into CWM using Volume Up + Power it just goes to android recovery. Which doesn't have any of the options I need. Am I just booting up the wrong way, or did I do something wrong. I tried both the touch version and the non-touch version

Spud37 said:
Okay I didn't get any error using ODIN, however when I try and boot into CWM using Volume Up + Power it just goes to android recovery. Which doesn't have any of the options I need. Am I just booting up the wrong way, or did I do something wrong. I tried both the touch version and the non-touch version
Click to expand...
Click to collapse
2 options. uncheck auto reboot in Odin. When Odin is done, unplug your phone, pull your battery, then boot into recovery. Or .. when Odin is done and it reboots your phone, keep holding volume up to get to recovery.

Atmazzz said:
2 options. uncheck auto reboot in Odin. When Odin is done, unplug your phone, pull your battery, then boot into recovery. Or .. when Odin is done and it reboots your phone, keep holding volume up to get to recovery.
Click to expand...
Click to collapse
Thank You so much. However it now seems like I have both Super User and SuperSU installed.

How did you root? Did you install the ROOT_M919?UVUAMDL zip and install SuperSU?

How to root a Samsung Galaxy S3 4.3 (SGH-I747)?

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

Need help recovering from failed root

I opened the box on my new Galaxy Tab 12.2 SM-T900 today. I immediately rooted it with CF-Auto-Root-v2wifi-v2wifixx-smt900.zip. That worked fine. But before I rooted it there was a notification of an OTA update, so I unrooted and did the OTA update. That went fine as well. But then I attempted to root using the same file, odin got stuck at writing the cache. I tried it several times, but no go.
Having run out of time, I pulled the battery and set it aside to deal with tomorrow. It would be great if some one could point me to the correct image to flash to bring the device back to life.
As background, my last Samsung device was a Vibrant that I flashed repeatedly. Back then I didn't need to select a ROM, as there was a dev section full of them. Now I need a pointer to the correct firmware, and maybe some words of wisdom. I think the original firmware was NB5, and the OTA was ND2. I'm afraid that I was too excited to b quite organized enough to write this stuff down.
I'm uncertain whether I would prefer to flash back to the original and root, or flash to the newer firmware and wait and hope for the root issue to be resolved by Chainfire. Suggestions?

Try flashing the recovery from sm-p900 from this post, the one with the filename ending with "b3", then try to root agajn. Should work after that.
http://forum.xda-developers.com/showthread.php?p=50492301
If not, install Kies 3 and do an emergency restore. It will ask for your serial# and download the correct rom and flash it back to stock
Sent from my SM-P900 using Tapatalk

dodo99x said:
Try flashing the recovery from sm-p900 from this post, the one with the filename ending with "b3", then try to root agajn. Should work after that.
http://forum.xda-developers.com/showthread.php?p=50492301
Click to expand...
Click to collapse
Thanks! I'll give that a shot. But a question before I do something really dumb. Where does this recovery tar file go in odin? PDA?

Yep always PDA
Sent from my SM-P900 using Tapatalk

Worked! I now have rooted KOT49H.T900UEUAND4.

Good stuff
Sent from my SM-P900 using Tapatalk

OK. Here comes the "but". It turns out that I cannot connect over SSL. Wifi works, I have an IP, I can brows non-secure websites. But I cannlt connect to anything https, nor will apps like Google Play connect.
Do we think this is related, or should i start a new thread?
UPDATE: I wiped data and now all is fine. The really interesting thing that I've noticed is that the Device Status is showing as "Official".

JJMT - you are rooted and it says official? Can you go through the exact steps you used please? Is KNOX enabled?

gbr357 said:
JJMT - you are rooted and it says official? Can you go through the exact steps you used please? Is KNOX enabled?
Click to expand...
Click to collapse
Yes. I am rooted and it says official. What's more, it checks for updates, although who knows what will happen when one shows up.
What I have is the ND4 firmware with the NB5 recovery. To get to this state:
1. OTA to ND4.
2. Boot into download mode. Flash the NB3 recovery. (P900XXUANB3-RecoveryImg.tar) It will reboot automatically.
3. Boot into download mode. Flash the root file. (CF-Auto-Root-v2wifi-v2wifixx-smt900.tar.md5). It will reboot automatically.
4. Boot into recovery mode. Wipe data/factory reset.
I believe at this point we are done. If you do this and it doesn't come up "official", then there must be something peculiar in the back-story. I am happy to answer questions.
UDATE: Forgot to mention - KNOX was disabled by SuperSU.

Thanks for the instructions. OTA done. I am going to give the rest a shot later tonight. I wonder though if using the B5 recovery for the T900 wouldn't be safer. It was posted later in the same thread referenced above by TweakerL (post #344 pg35). Going to give that a shot vice using the P900 recovery. What do you think?

gbr357 said:
Thanks for the instructions. OTA done. I am going to give the rest a shot later tonight. I wonder though if using the B5 recovery for the T900 wouldn't be safer. It was posted later in the same thread referenced above by TweakerL (post #344 pg35). Going to give that a shot vice using the P900 recovery. What do you think?
Click to expand...
Click to collapse
I think I would have done that if I had known there was a B5 recovery image available. The guidance that I was given was to flash the B3 image from the P900. And that *did* work fine. Before there was a root flash for the T900, people were using the P900 root with success. Don't know that there is much difference. In the end, either way, you will end up with a B5 recovery image, as that is what Chainfire included in the T900 root file.

Well I got everything ready and instead of flashing the B5 image, I just flashed the root image from Chainfire. I didn't even think about what I was doing because that's such a normal process. Anyway, everything went off without a hitch. Rooted and rebooted in 10 seconds. Device now says custom however and I can't check for updates. That's fine though because all I wanted was root and I have ND4.

gbr357 said:
Well I got everything ready and instead of flashing the B5 image, I just flashed the root image from Chainfire. I didn't even think about what I was doing because that's such a normal process. Anyway, everything went off without a hitch. Rooted and rebooted in 10 seconds. Device now says custom however and I can't check for updates. That's fine though because all I wanted was root and I have ND4.
Click to expand...
Click to collapse
Which file from Chainfire did you flash? Was it CF-Auto-Root-v2wifi-v2wifixx-smt900.zip? For me, flashing that after OTAing to ND4 left me unable to boot. Maybe that got fixed in the past couple of day?

Yes it was that file off chainfire's site. Either something got fixed or the fact that I wasn't rooted before the OTA??

gbr357 said:
Yes it was that file off chainfire's site. Either something got fixed or the fact that I wasn't rooted before the OTA??
Click to expand...
Click to collapse
Well. technically I wasn't rooted either. I completely removed root with SuperSU.Is your recovery NB5?

JJMT said:
I opened the box on my new Galaxy Tab 12.2 SM-T900 today. I immediately rooted it with CF-Auto-Root-v2wifi-v2wifixx-smt900.zip. That worked fine. But before I rooted it there was a notification of an OTA update, so I unrooted and did the OTA update. That went fine as well. But then I attempted to root using the same file, odin got stuck at writing the cache. I tried it several times, but no go.
Having run out of time, I pulled the battery and set it aside to deal with tomorrow. It would be great if some one could point me to the correct image to flash to bring the device back to life.
As background, my last Samsung device was a Vibrant that I flashed repeatedly. Back then I didn't need to select a ROM, as there was a dev section full of them. Now I need a pointer to the correct firmware, and maybe some words of wisdom. I think the original firmware was NB5, and the OTA was ND2. I'm afraid that I was too excited to b quite organized enough to write this stuff down.
I'm uncertain whether I would prefer to flash back to the original and root, or flash to the newer firmware and wait and hope for the root issue to be resolved by Chainfire. Suggestions?
Click to expand...
Click to collapse
That's the problem I've been writing about for a week. The new OTA update (t900ueuand4) doesn't work with auto-root and crashes exactly where yours did.
---------- Post added at 11:28 PM ---------- Previous post was at 11:25 PM ----------
gbr357 said:
Yes it was that file off chainfire's site. Either something got fixed or the fact that I wasn't rooted before the OTA??
Click to expand...
Click to collapse
Can you give me the link for the new chainfire file that must have been re-written in the last 2 days
---------- Post added at 11:32 PM ---------- Previous post was at 11:28 PM ----------
gbr357 said:
Yes it was that file off chainfire's site. Either something got fixed or the fact that I wasn't rooted before the OTA??
Click to expand...
Click to collapse
Just re-downloaded the chainfire file and it's identical to the file I got 10 days ago dated May 10th. If you had success flashing it with the firmware t900ueuand4 installed at the time of rooting, then I'll give it a shot too.

JJMT said:
Yes. I am rooted and it says official. What's more, it checks for updates, although who knows what will happen when one shows up.
What I have is the ND4 firmware with the NB5 recovery. To get to this state:
1. OTA to ND4.
2. Boot into download mode. Flash the NB3 recovery. (P900XXUANB3-RecoveryImg.tar) It will reboot automatically.
3. Boot into download mode. Flash the root file. (CF-Auto-Root-v2wifi-v2wifixx-smt900.tar.md5). It will reboot automatically.
4. Boot into recovery mode. Wipe data/factory reset.
I believe at this point we are done. If you do this and it doesn't come up "official", then there must be something peculiar in the back-story. I am happy to answer questions.
UDATE: Forgot to mention - KNOX was disabled by SuperSU.
Click to expand...
Click to collapse
All I had to do, was stop after 3. Didn't require a factory reset. Everything is great

The same here. Used the Note 12 recovery mod to unbrick the tablet.
Flashed the CF-Auto-Root-v2wifi-v2wifixx-smt900.tar.md5 and it works. :good:
Now oor Samsung tablet pro 12.2 is rooted.

dodo99x said:
Try flashing the recovery from sm-p900 from this post, the one with the filename ending with "b3", then try to root agajn. Should work after that.
http://forum.xda-developers.com/showthread.php?p=50492301
If not, install Kies 3 and do an emergency restore. It will ask for your serial# and download the correct rom and flash it back to stock
Sent from my SM-P900 using Tapatalk
Click to expand...
Click to collapse
I ran into a similar issue except my device came up to an error regarding firmware upgrade failed, use kies to recover. I could not get this to work with kies 3. Searching the threads, I found your post. Worked beautifully. The failed attempt did trip Knox. Not sure I care.
Thanks!

Root to sg3 4.4.2 i747m

THERE is a way to root the kit kat 4.4.2 official of the D2CAN ?

brayhanrd said:
THERE is a way to root the kit kat 4.4.2 official of the D2CAN ?
Click to expand...
Click to collapse
Try Towelroot.

vbetts said:
Try Towelroot.
Click to expand...
Click to collapse
that work for you!!! confirmation plz!!

chewingum16 said:
that work for you!!! confirmation plz!!
Click to expand...
Click to collapse
Works like a charm. install towel root let it do it's method then phone will reboot once it reboots install super su from play store and hola!
---------- Post added at 11:40 PM ---------- Previous post was at 11:39 PM ----------
Xami said:
Works like a charm. install towel root let it do it's method then phone will reboot once it reboots install super su from play store and hola!
Click to expand...
Click to collapse
https://mega.co.nz/#!Ah9BmApB!N0W7vyZ23_yhDooMxo-zhF3WYqEioStM8J-opaVjXWk
Flash in odin for recovery

vbetts said:
Try Towelroot.
Click to expand...
Click to collapse
thanks it work like a charm..

Xami said:
Works like a charm. install towel root let it do it's method then phone will reboot once it reboots install super su from play store and hola!
---------- Post added at 11:40 PM ---------- Previous post was at 11:39 PM ----------
https://mega.co.nz/#!Ah9BmApB!N0W7vyZ23_yhDooMxo-zhF3WYqEioStM8J-opaVjXWk
Flash in odin for recovery
Click to expand...
Click to collapse
thanks for help !!! it's the amazing apk in the history of rooooooooot

This rooting method was made by GeoHot. The same guy who unlocked the first iphone back in 2007. He jail broke the ps3 in 2011 then Sony tried to sue him. Then anonymous shut their a$$es down for a good two weeks.

Does towelroot trip the knox counter?

I saw someone say it does not. It preserves the stock recovery so it makes sense that it wouldn't. But if you plan on using a custom recovery or kernel it won't matter as that would trip it anyway.

audit13 said:
Does towelroot trip the knox counter?
Click to expand...
Click to collapse
I used it to root my phone and no my Knox flag is still at 0 so your good to root and have warranty
Sent from my ATT Samsung Galaxy SIII using TapaTalk

Towelroot AT&T Galaxy S3 i747 with 4.4.2 Working.
Towelroot installed with No problems on my AT&T SGH-i747 Galaxy S3 with the new 4.4.2 update. See screenshots below.
Does not affect Knox Warranty Bit! I am staying with factory recovery mode.

so i've tripped my knox, and towelroot says it's incompatible. any suggestions?

Towelroot will only work for NE6 firmware on the I747M. The exploit it uses was patched in NF1/NF2.
you can try cf autoroot, or just flash recovery then flash SuperSU.

I have tried to root my phone, I747M, Canadian, 4.4.2 version, with SRSRoot, it says that process is complete and that everything is OK but root checker says that phone isn't rooted and Superuser icon can't be found anywhere. I tried Towelroot few minutes ago, it says that my phone isn't currently supported. Dunno what to do any more...

No idea what srsroot is... Just flash a supersu update package from my sig. Flash in recovery.
Sent from my SAMSUNG-SGH-T999 using Tapatalk

Recovery won't stay flashed after reboot. Twrp 2.6.3.0 and 2.8 if I don't let phone finish booting into ROM after flashing I can access twrp but there's no storage. Won't mount any partitions, data/system/cache or external/internal SD. If I do let it finish reboot into ROM, then shut down and boot into recovery it reverts back to stock recovery. Towel root and cf auto root both are unsuccessful as well as Kingo. Any help please?
Also tried cwm recovery. Same deal as twrp

Flash recovery again. Use its built in file manager to delete or rename these files and recovery will stay after rebooting.
/system/recovery-from-boot.p
/system/etc/indtall-recovery.sh
Try to mount partitions again. If it fails, go to advanced and copy log to sd. Then attach it here. Do the same if flashing the rom fails.
You may want to try cwm or philz recoveries too.
Sent from my SAMSUNG-SGH-I747 using Tapatalk

Ok, thanks. I'm heading home from work n I'll try what u suggested, altho I don't think I'll be able to modify and files, since nothing mounts but I will try. Also definitely won't be copy the log to SD if it won't mount, but could still probably pull it thru adb. Have tried twrp and cwm neither will mount. Will update this post after I try. Thanks

Good point! Sorry bout that! Have you tried philz recovery?
Sent from my SAMSUNG-SGH-I747 using Tapatalk

I747 NF1 and NF2 root?
Wrong title. I meant I747M not I747. Anyways, is it possible to just downgrade the NF1 or NF2 kernel to the NE6 kernel then root via towel root then put back the NF1 or NF2 kernel after its rooted?

after flashing oxygenos 4.1.1 twrp recovery is not coming

after flashing oxygenos 4.1.1 through twrp recovery when i rebooted my phone into recovery stock recovery came i dont have pc right now can anyone help it's very urgent

after flashing new OOS update , should always boot into TWRP first than boot into OS. flash TWRP recovery again ver 3.0.4-1.

anup807 said:
after flashing new OOS update , should always boot into TWRP first than boot into OS. flash TWRP recovery again ver 3.0.4-1.
Click to expand...
Click to collapse
Actually I don't have PC is there any other way

how did you install it earlier?
---------- Post added at 02:02 PM ---------- Previous post was at 01:56 PM ----------
https://www.youtube.com/watch?v=BYUycIr7xQo - try this.

If you've lost your custom recovery after flashing a ROM, I'm assuming that you didn't root immediately afterwards?
In that case, you won't be able to use Flashify and your only option is to wait until you have access to a PC.

You should flash twrp after flashing any rom. Then reboot to recovery to check if it works. Official roms flash official recovery...

Anova's Origin said:
If you've lost your custom recovery after flashing a ROM, I'm assuming that you didn't root immediately afterwards?
In that case, you won't be able to use Flashify and your only option is to wait until you have access to a PC.
Click to expand...
Click to collapse
Can i root my phone through app like kingoroot or any other app then can i flash trwp through falshify

sauravid said:
Can i root my phone through app like kingoroot or any other app then can i flash trwp through falshify
Click to expand...
Click to collapse
If kingoroot works, then yes, you can probably flash TWRP that way.

Anova's Origin said:
If kingoroot works, then yes, you can probably flash TWRP that way.
Click to expand...
Click to collapse
No rooting app is working did you know any app which can work

anup807 said:
how did you install it earlier?
---------- Post added at 02:02 PM ---------- Previous post was at 01:56 PM ----------
- try this.
Click to expand...
Click to collapse
Actually it requre root access. Do you know how to get root access without pc

You could give Kingroot (not Kingoroot) a try. I used to use it on old devices and it does work from time to time. Beware that it does contain a lot of bloat and is suspected to datamine its users. If it successfully roots your phone, I would advise you to clean flash your ROM again after flashing a custom recovery just to make sure it doesn't linger. It it fails to root, then just delete the app (it shouldn't be able to install anything malicious without root access).

Anova's Origin said:
You could give Kingroot (not Kingoroot) a try. I used to use it on old devices and it does work from time to time. Beware that it does contain a lot of bloat and is suspected to datamine its users. If it successfully roots your phone, I would advise you to clean flash your ROM again after flashing a custom recovery just to make sure it doesn't linger. It it fails to root, then just delete the app (it shouldn't be able to install anything malicious without root access).
Click to expand...
Click to collapse
Not working..bro

I would suggest not to take too much risk with rooting without the access to PC. If by chance, something goes wrong, like bootloop or something, you'll be screwed big time.

anup807 said:
I would suggest not to take too much risk with rooting without the access to PC. If by chance, something goes wrong, like bootloop or something, you'll be screwed big time.
Click to expand...
Click to collapse
Ohk bro