Related
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 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!
Alright so I was rooted, but now there's been at least one new version of Android, so I need to do it again and update. I am confused as to how this whole thing works. I used to have an iPod touch which I jailbroke, and you could update the firmware simply by jailbreaking with a jailbroken version of the newer OS. Does Android work in a similar fashion with rooting, in which when you flash the ROM (am I saying this right?), it is a different Android version? So can I just find a ROM that's 4.3 to update, or should I update to 4.3 over the air and then root again? I actually already did the OTA update because it was really bothering me and currently I don't even use root features frequently. Anyway, the no-flash trip link in the how to root section says 4.1.1, which I assume means Android 4.1.1, and I don't want this. What can I do?
If I get a current version of a custom ROM, LiquidSmooth or something, will that update my Android version?
I'm sorry if I'm making zero sense right now, or if this is in entirely the wrong section. I'm trying my best here.
You're on stock ? If so what version,4.3?
FYI this isn't the right place to post this. But check out THIS thread about Preparing to flash an ND8 (kitkat) rom. It is short, very informative and has important links to other things you may need. Good luck!
~CTP
Nexus11 said:
You're on stock ? If so what version,4.3?
Click to expand...
Click to collapse
Indeed.
Azhai said:
Indeed.
Click to expand...
Click to collapse
I will help U but you take full responsibility for anything that may happen to your device in the process.
It seems like U are still rooted, but but just on MK3 still. This will upgrade U to ND8
Here goes:
#1 Install Odin on your PC, run the program. (Link to Odin 3.07. LINK for ODINClick link and it will automatically download to system) Extract from ZIP
#2 Load the ND8 tar in the PDA Slot, put your phone in Download Mode (power off, hold Vol Down, Home, and Power), and connect your phone to the PC. (leave check in the Auto-Reboot and F-Reset)
#3 Then after that is successful run CF Auto Root LINK CF-AUTO ROOT This down load must be extracted and U will see Odin application in there too along with CF-Auto tar
#3b (I didn't do this because I don't really care, but if U want) get ROM Toolbox or something of that nature and remove any app with Knox in the title or that has the Knox symbol.
#4 Load your phone into Download Mode one last time and then put whatever recovery you have (I use Philz, make sure you grab the .tar format instead of the zip) and put that in the Bootloader slot in Odin. U will then be rooted and custom recovery.. U can stay there and set up phone or flash a custom ROM. I would do a nandroid back-up in philz first before U flash a new ROM though.
Link to PhilZ 6.416 Tar DIRECT LINK I use this one because it WORKS with no issues
or U can go here and get other versions of Philz. LINK
This guide was originally posted by Bilgerryan (below) and I augmented a few things and added links so U wouldn't have to search and search.
Quote:
Originally Posted by bilgerryan
Install Odin on your PC, run the program. Load the ND8 tar in the PDA Slot, put your phone in Download Mode (power off, hold Vol Down, Home, and Power), and connect your phone to the PC. Then after that is successful run CF Auto Root or whatever root injector you have in the PDA slot again. Once that finishes (wait until Odin tells you it was a Success before doing anything), get ROM Toolbox or something of that nature and remove any app with Knox in the title or that has the Knox symbol. Load your phone into Download Mode one last time and then put whatever recovery you have (I use Philz, make sure you grab the .tar format instead of the zip) and put that in the Bootloader slot in Odin. Then you're good to go, rooted and custom recovery, sky's the limit.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2738533&page=51
Needs to be moved
Glad that answers are coming in, but this thread needs to be moved; @KennyG123, can you assist?
What in the blue hell????!! A question in Development?!!!
Please read forum rules before posting. Rule 15 will help you decide where your post needs to go.
Thank you for your cooperation
Thread moved
Thanks for the move. Reading is hard.
So can someone just clear up the whole version thing for me? I attempted to do the 4.4 OTA update that showed up, and it seems to have worked in the sense that the notification went away, but my version is the same (4.3) and I seem to still be rooted. I guess I really don't understand any of the rooting process. I know I've used Odin and stuff but I really don't know what any of it does. Is there already a thread somewhere that explains what all of this stuff actually does? I mean, updating and staying rooted can't be that hard to do.
Azhai said:
Thanks for the move. Reading is hard.
So can someone just clear up the whole version thing for me? I attempted to do the 4.4 OTA update that showed up, and it seems to have worked in the sense that the notification went away, but my version is the same (4.3) and I seem to still be rooted. I guess I really don't understand any of the rooting process. I know I've used Odin and stuff but I really don't know what any of it does. Is there already a thread somewhere that explains what all of this stuff actually does? I mean, updating and staying rooted can't be that hard to do.
Click to expand...
Click to collapse
Attempts to take an OTA on a rooted phone should fail. There is already a thread, chad the pathfinder gave u the link...
Sent from my SPH-L710, using Tapatalk 2 Cyan. ND8. Rooted and rom'd with WICKED-X (HELLS YA!)
I got a Galaxy S3 SPH-L710 and it was all ready updated to the L710VPUDOH1 baseband version. After searching around a little bit I noticed that most of the Roms are for baseband L710VPUDND8 and that some of the ND8 roms would not flash correctly.
I guess maybe i found a workaround for this. When i first tried to flash the CM 12.1 Rom I got error and it did not load. Did not hurt anything either. Was a little tricky getting initial root but got it all working.
Figured id share how i accomplished this in case someone else with the L710VPUDOH1 baseband wants to run the other Roms.
First i tried to root with Odin and the supersu.zip but it didnt take correctly.
Odin showed successful and the supersu flashed to the /system but every time i tried to run supersu I get Unfortunately SuperSU stopped working.
So i ended up using ODIN to get Temp CWM recovery and installed the CF-Autoroot in the CWM recovery. This woorked to get Root.
I downloaded the TWRP manager from playstore andused it to install TWRP 2.8.1.0
The TWRP Manager gave me an error but when i booted into recovery I had TWRP.
After that i tried to flash CM 12.1 in TWRP but got error and it didnt work.
I read that wicked 2.2 would load,
its big all most a gig so i figured it was pretty complete. maybe based off of stock.
I loaded it successfully.
afterwards i booted back into twrp and did an advanced wipe of.
Dalvic Cache
/ system
/data
/internal storage
/cache
Then i loaded Cm 12.1 with no issues.
Tested Pac-Rom No issues.
Im thinking any of the newer roms will flash fine now.
BigCountry907 said:
After that i tried to flash CM 12.1 in TWRP but got error and it didnt work.
Click to expand...
Click to collapse
I'm hoping you left out some steps, because if you tried flashing CM 12.1 without doing a wipe on System/Data/Cache/Dalvik then you will not have a working phone.
BigCountry907 said:
I got a Galaxy S3 SPH-L710 and it was all ready updated to the L710VPUDOH1 baseband version. After searching around a little bit I noticed that most of the Roms are for baseband L710VPUDND8 and that some of the ND8 roms would not flash correctly.
I guess maybe i found a workaround for this. When i first tried to flash the CM 12.1 Rom I got error and it did not load. Did not hurt anything either. Was a little tricky getting initial root but got it all working.
Figured id share how i accomplished this in case someone else with the L710VPUDOH1 baseband wants to run the other Roms.
First i tried to root with Odin and the supersu.zip but it didnt take correctly.
Odin showed successful and the supersu flashed to the /system but every time i tried to run supersu I get Unfortunately SuperSU stopped working.
So i ended up using ODIN to get Temp CWM recovery and installed the CF-Autoroot in the CWM recovery. This woorked to get Root.
I downloaded the TWRP manager from playstore andused it to install TWRP 2.8.1.0
The TWRP Manager gave me an error but when i booted into recovery I had TWRP.
After that i tried to flash CM 12.1 in TWRP but got error and it didnt work.
I read that wicked 2.2 would load,
its big all most a gig so i figured it was pretty complete. maybe based off of stock.
I loaded it successfully.
afterwards i booted back into twrp and did an advanced wipe of.
Dalvic Cache
/ system
/data
/internal storage
/cache
Then i loaded Cm 12.1 with no issues.
Tested Pac-Rom No issues.
Im thinking any of the newer roms will flash fine now.
Click to expand...
Click to collapse
I don't think the roms care if your on ND8 or NJ2 or whatever the latest is . You should also update twrp to 2.8.7.0 . Version 2.8.4.0 and on allow you to flash a new twrp version image right from recovery . 2.8.1.0 is pretty old . Best of luck with your new hobby .
Ya i didnt have any troubles.
Im currently working on 5 devices and writing sort of a kitchen.
But it dose way more than most kitchens. Even creates a CWM style backup over adb like onandroid.
I found a way to patch a factory recovery.img to flash files signed with my own keys and that kinda started it all.
Anyway Merry Christmas
what's the root method for DOH1? ;; I can't seem to find a thread specifically walking through the root method for the latest baseband and i have an old S3 and was thinking of playing around with it for a while for fun turn it into a light weight media player to save battery on my LG G4 since we all know how inconsistent and crap the battery can be with the G4 lol
The root is pretty easy.
I used this.
http://forum.xda-developers.com/showthread.php?t=1963812
Then just get Clockworkmod or TWRP recovery for the d2spr sphl710 and flash it.
After that load any rom you want
silvernirvash said:
what's the root method for DOH1? ;; I can't seem to find a thread specifically walking through the root method for the latest baseband and i have an old S3 and was thinking of playing around with it for a while for fun turn it into a light weight media player to save battery on my LG G4 since we all know how inconsistent and crap the battery can be with the G4 lol
Click to expand...
Click to collapse
Same as always, use odin to flash a .tar of twrp. Then use twrp to flash a .zip of SuperSU. Done
Doh1
Is there any rom working at Doh1 version?
bael616 said:
Is there any rom working at Doh1 version?
Click to expand...
Click to collapse
All of them
madbat99 said:
All of them
Click to expand...
Click to collapse
Really? I have been told there was nothing for the l710vpudoh1 version. Would you mind to help me out with this topic of flashing a rom, please? P.D: Sorry about my english.
bael616 said:
Really? I have been told there was nothing for the l710vpudoh1 version. Would you mind to help me out with this topic of flashing a rom, please? P.D: Sorry about my english.
Click to expand...
Click to collapse
Oh1 is not a version of the phone. It's just a build number.
Do you have the triband model? What carrier?
madbat99 said:
Oh1 is not a version of the phone. It's just a build number.
Do you have the triband model? What carrier?
Click to expand...
Click to collapse
Got no idea. It is the sprint CDMA version.
bael616 said:
Got no idea. It is the sprint CDMA version.
Click to expand...
Click to collapse
Well that's what you need to know. Oh1 doesn't matter. There is oh1 for regular s3 and triband s3. Regular is sph-L710 and triband is sph-L710t. Does it have a t at the end of the model number?
madbat99 said:
Well that's what you need to know. Oh1 doesn't matter. There is oh1 for regular s3 and triband s3. Regular is sph-L710 and triband is sph-L710t. Does it have a t at the end of the model number?
Click to expand...
Click to collapse
It doesn't have any t. So I guess it Ies the regular one. I want to know how to root it and flash a rom.
bael616 said:
It doesn't have any t. So I guess it Ies the regular one. I want to know how to root it and flash a rom.
Click to expand...
Click to collapse
To root, you need odin on your PC. You can get it here.
Use odin to flash twrp recovery. You can get twrp from their site. twrp
Get the .tar of the newest build for d2spr (sprint s3). Put it on you PC somewhere you can find it (download folder is fine)
There are tutorials everywhere for using odin. It's the way to root almost all Samsung phones.
You also need the Samsung drivers on your PC. I don't have a link for that at this moment.
Then launch odin on your PC.
Put phone in download mode (from powered off, hold power+home+volume down)
Plug phone in to PC and odin should say "added"
Click AP button in odin then navigate to where you have the Twrp .tar downloaded and select it
Click start in odin.
When it finishes it should say pass.
Don't let the phone boot to system, unplug it and take out battery
Put batter back in and boot directly to twrp recovery by holding power+home+VOLUME UP
In twrp select reboot, then system. It should say you don't have root and ask if you want root. Swipe the arrow for yes. Once it boots, open SuperSU and update binaries if it asks. Choose normal method.
Done. Rooted.
You should really have looked up how to root before coming to a thread about flashing roms. There are tutorials everywhere for rooting this phone. Google is your friend dude.
Edit: you can get the Samsung USB drivers here
That thread has rooting instructions too. It's for the virgin Mobile s3, but its the same phone. Those instructions work fine. Only difference is I linked you to twrp recovery instead of philztouch (philz development is dead) and I linked you to a newer odin.
If you are that new that you aren't sure about rooting, maybe start over there in Android forums. I'm a guide there.
bael616 said:
Really? I have been told there was nothing for the l710vpudoh1 version. Would you mind to help me out with this topic of flashing a rom, please? P.D: Sorry about my english.
Click to expand...
Click to collapse
I was given a SPH-L710... Originally purchased from sprint.... Currently activated on boost. I got the phone Dec. 24 2015. It had stock unrooted DOH1 with untripped warranty bit. I have successfully booted and ran these roms for a minimum of 24 hrs each. As far as I could tell they were fully functional including: 4G LTE, MMS send and recieve, hotspot, wifi, bluetooth, camera (still and video). All main fuctions worked correctly for the limited time that I used each rom. :
-Wicked-X-Bare-Bones.zip
-Wicked-X-v8.2.zip
-cm-11-20150831_SNAPSHOT-XNG3CAO3FN-d2lte.zip
-cm-12.1-20151117-SNAPSHOT-YOG7DAO1K7-d2spr.zip
-cm-12.1-20160202-NIGHTLY-d2spr.zip
-cm-13.0-20160130-UNOFFICIAL-d2spr.zip
Im currently running CM13 unofficial as a daily driver. Cm12.1 SNAPSHOT was also very responsive and gave me no problems. I flashed them with twrp.2.8.7.2-d2spr.img. i flashed the recovery with odin after i made it into a .tar.md5 using linux mint 17.3 cinnamon. For the lte and mms i used "apn backup and restore" from google play with the root explorer method. Open gapps aroma for each android version i got from cyanogenmod website. i would recommend searching and using the dd command with adb shell in a linux terminal or cygwin to backup every partition on your doh1 first. (You will need root and busybox) There should be 24 partitions in mmcblk0. Make a backup of every one and you can recover one way or another ALMOST regardless of what may or may not go wrong. I used supersu 2.65 zip. Ive had alot of issues due to DOH1 but all the resources are in that easily used omnibox. Hope any of this info helps you.
madbat99 said:
To root, you need odin on your PC. You can get it here.
Use odin to flash twrp recovery. You can get twrp from their site. twrp
Get the .tar of the newest build for d2spr (sprint s3). Put it on you PC somewhere you can find it (download folder is fine)
There are tutorials everywhere for using odin. It's the way to root almost all Samsung phones.
You also need the Samsung drivers on your PC. I don't have a link for that at this moment.
Then launch odin on your PC.
Put phone in download mode (from powered off, hold power+home+volume down)
Plug phone in to PC and odin should say "added"
Click AP button in odin then navigate to where you have the Twrp .tar downloaded and select it
Click start in odin.
When it finishes it should say pass.
Don't let the phone boot to system, unplug it and take out battery
Put batter back in and boot directly to twrp recovery by holding power+home+VOLUME UP
In twrp select reboot, then system. It should say you don't have root and ask if you want root. Swipe the arrow for yes. Once it boots, open SuperSU and update binaries if it asks. Choose normal method.
Done. Rooted.
You should really have looked up how to root before coming to a thread about flashing roms. There are tutorials everywhere for rooting this phone. Google is your friend dude.
Edit: you can get the Samsung USB drivers here
That thread has rooting instructions too. It's for the virgin Mobile s3, but its the same phone. Those instructions work fine. Only difference is I linked you to twrp recovery instead of philztouch (philz development is dead) and I linked you to a newer odin.
If you are that new that you aren't sure about rooting, maybe start over there in Android forums. I'm a guide there.
Click to expand...
Click to collapse
Thanks a lot. I have already rooted the phone but now I want to know what Roms are made to this device.
---------- Post added at 05:28 AM ---------- Previous post was at 05:24 AM ----------
HouseHG said:
I was given a SPH-L710... Originally purchased from sprint.... Currently activated on boost. I got the phone Dec. 24 2015. It had stock unrooted DOH1 with untripped warranty bit. I have successfully booted and ran these roms for a minimum of 24 hrs each. As far as I could tell they were fully functional including: 4G LTE, MMS send and recieve, hotspot, wifi, bluetooth, camera (still and video). All main fuctions worked correctly for the limited time that I used each rom. :
-Wicked-X-Bare-Bones.zip
-Wicked-X-v8.2.zip
-cm-11-20150831_SNAPSHOT-XNG3CAO3FN-d2lte.zip
-cm-12.1-20151117-SNAPSHOT-YOG7DAO1K7-d2spr.zip
-cm-12.1-20160202-NIGHTLY-d2spr.zip
-cm-13.0-20160130-UNOFFICIAL-d2spr.zip
Im currently running CM13 unofficial as a daily driver. Cm12.1 SNAPSHOT was also very responsive and gave me no problems. I flashed them with twrp.2.8.7.2-d2spr.img. i flashed the recovery with odin after i made it into a .tar.md5 using linux mint 17.3 cinnamon. For the lte and mms i used "apn backup and restore" from google play with the root explorer method. Open gapps aroma for each android version i got from cyanogenmod website. i would recommend searching and using the dd command with adb shell in a linux terminal or cygwin to backup every partition on your doh1 first. (You will need root and busybox) There should be 24 partitions in mmcblk0. Make a backup of every one and you can recover one way or another ALMOST regardless of what may or may not go wrong. I used supersu 2.65 zip. Ive had alot of issues due to DOH1 but all the resources are in that easily used omnibox. Hope any of this info helps you.
Click to expand...
Click to collapse
Thanks man is there any link you can share with me? I really want to flash a rom but there is no one with this device in Facebook groups. So if you can share any Rom and the way it should be flashed I will be really thankful.
P. D: as I mentioned before I have no perfect English skills so I hope you understand what I mean.
bael616 said:
Thanks a lot. I have already rooted the phone but now I want to know what Roms are made to this device.
---------- Post added at 05:28 AM ---------- Previous post was at 05:24 AM ----------
Thanks man is there any link you can share with me? I really want to flash a rom but there is no one with this device in Facebook groups. So if you can share any Rom and the way it should be flashed I will be really thankful.
P. D: as I mentioned before I have no perfect English skills so I hope you understand what I mean.
Click to expand...
Click to collapse
I cant post links due to my total number of posts. PM me and I'll send them to you.
bael616 said:
Thanks a lot. I have already rooted the phone but now I want to know what Roms are made to this device.
---------- Post added at 05:28 AM ---------- Previous post was at 05:24 AM ----------
Thanks man is there any link you can share with me? I really want to flash a rom but there is no one with this device in Facebook groups. So if you can share any Rom and the way it should be flashed I will be really thankful.
P. D: as I mentioned before I have no perfect English skills so I hope you understand what I mean.
Click to expand...
Click to collapse
You have the sprint s3, but are you on sprint? If you are not on Sprint there are additional instructions. Any rom that says its for D2spr is fine. That's the sprint s3.
this is the one I'm using.
HouseHG said:
I cant post links due to my total number of posts. PM me and I'll send them to you.
Click to expand...
Click to collapse
Ok man thanks
---------- Post added at 01:39 AM ---------- Previous post was at 01:35 AM ----------
madbat99 said:
You have the sprint s3, but are you on sprint? If you are not on Sprint there are additional instructions. Any rom that says its for D2spr is fine. That's the sprint s3.
this is the one I'm using.
Click to expand...
Click to collapse
Actually, I don't use any company cause I don't live in the US so I use the phone only with WiFi.
**IGNORE POST #1 ONLY FOLLOW POST #2-#4!!!**
Info and DL on SuperSU v2.6x and Systemless Root
1. MUST flash a 100% stock (Odin) firmware.
2. DL SuperSU v2.6x
3. Install custom recovery
4. Install new SuperSU zip
5. Let it run through the process then reboot.
Hey Joe, your link about the info is broken. Also your 'click source' on #2. is not a link.
balistic2 said:
Hey Joe, your link about the info is broken. Also your 'click source' on #2. is not a link.
Click to expand...
Click to collapse
I think that this is the link: http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
If I read Chainfire's notes correctly, this is only for systems running Marshmallow, which would let us out for a while. But....
Once Samsung updates our OS to Marshmallow or they get CM 13 working on our phones (currently a work in progress) this could allow us to use Android Pay on a rooted phone.
balistic2 said:
Hey Joe, your link about the info is broken. Also your 'click source' on #2. is not a link.
Click to expand...
Click to collapse
Fixed!
koop1955 said:
I think that this is the link: http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
If I read Chainfire's notes correctly, this is only for systems running Marshmallow, which would let us out for a while. But....
Once Samsung updates our OS to Marshmallow or they get CM 13 working on our phones (currently a work in progress) this could allow us to use Android Pay on a rooted phone.
Click to expand...
Click to collapse
I do not believe it is MM only bc it's posted in the international S6 general forum too (and they obviously aren't on MM yet either).
JoeFCaputo113 said:
I do not believe it is MM only bc it's posted in the international S6 general forum too (and they obviously aren't on MM yet either).
Click to expand...
Click to collapse
I wasn't sure if CM13 is already working on International phones.
I only know what I read....
From Chainfire's post:
Rooting procedure:
- flash/upgrade to Marshmellow
- flash modified boot.img
- flash/boot TWRP and sideload latest...
Joe, be careful if you try this. Looks like you need to Odin back to stock.
Does this still void knox?
1619415 said:
Does this still void knox?
Click to expand...
Click to collapse
That is the key question. Also, would Google detect the phone as being rooted.
For the Knox part, someone with a "virgin" phone would need to test. Both Joe and I have already rooted using the current method, so Knox is already tripped.
koop1955 said:
That is the key question. Also, would Google detect the phone as being rooted.
For the Knox part, someone with a "virgin" phone would need to test. Both Joe and I have already rooted using the current method, so Knox is already tripped.
Click to expand...
Click to collapse
Seems to work on Note 5, just flashed TWRP with ODIN and then flashed SuperSu and there is no text while booting
---------- Post added at 09:19 PM ---------- Previous post was at 08:29 PM ----------
Thank you for posting this, now we have a method of rooting that A: Does not require custom kernels #Marshmallow and B: May not trip Knox
1619415 said:
Seems to work on Note 5, just flashed TWRP with ODIN and then flashed SuperSu and there is no text while booting
---------- Post added at 09:19 PM ---------- Previous post was at 08:29 PM ----------
Thank you for posting this, now we have a method of rooting that A: Does not require custom kernels #Marshmallow and B: May not trip Knox
Click to expand...
Click to collapse
Well Merry Christmas!
JoeFCaputo113 said:
Well Merry Christmas!
Click to expand...
Click to collapse
You to
---------- Post added at 01:52 PM ---------- Previous post was at 01:01 PM ----------
Has anyone tried rooting with this method and trying samsumg pay?
Decided to give this a try. Odin flashed OL1. Booted OL1 with no problem. Odin flashed TWRP, without reboot. Rebooted directly into TWRP and flashed SU beta 2.65. It booted without problem with root access. When I go into SU, it says there is an update available, but I just cancel out.
I was hoping android pay would work as I could never get it to work except stock unrooted. I started android pay and got the message "android pay cannot be used." I realized I needed to unroot in SU. I did that and still get the same message.
EDIT: Tried it again. Odined OL1, rebooted and android pay worked fine. Odined TWRP, booted into TWRP, fine. Rebooted into rom, bootlooped at Samsung logo, over and over. Rebooted into recovery and flashed SU 2.65. Rebooted into rom with no problem. Android Pay no longer works.
todivefor said:
Decided to give this a try. Odin flashed OL1. Booted OL1 with no problem. Odin flashed TWRP, without reboot. Rebooted directly into TWRP and flashed SU beta 2.65. It booted without problem with root access. When I go into SU, it says there is an update available, but I just cancel out.
I was hoping android pay would work as I could never get it to work except stock unrooted. I started android pay and got the message "android pay cannot be used." I realized I needed to unroot in SU. I did that and still get the same message.
EDIT: Tried it again. Odined OL1, rebooted and android pay worked fine. Odined TWRP, booted into TWRP, fine. Rebooted into rom, bootlooped at Samsung logo, over and over. Rebooted into recovery and flashed SU 2.65. Rebooted into rom with no problem. Android Pay no longer works.
Click to expand...
Click to collapse
Try Number 15
1619415 said:
Try Number 15
Click to expand...
Click to collapse
Thanks. Been there done that.
Sent from my SM-T710 using Tapatalk
For those asking about whether this root method trips knox or not. Yes this will trip knox. Anytime you use odin to flash non official Samsung firmware/software then it forever trips knox. Therefore flashing any custom recovery will absolutely trip knox... forever.
Samsung and Android pay apps will not work on rooted devices. Period. The pay apps are intended for official factory software for obvious reasons. Security is the main focus with these types of apps that deal with your personal banking/credit card information. Hence a rooted device is not considered "secure".
using this method and my S6 is rooted without custom kernel which i prefer.
however, it seems like i cant use titanium backup to restore any backed up apps. Titanium app just runs endlessly.
yaibakt said:
using this method and my S6 is rooted without custom kernel which i prefer.
however, it seems like i cant use titanium backup to restore any backed up apps. Titanium app just runs endlessly.
Click to expand...
Click to collapse
Try installing/updating busybox and try removing titanium backups root access them regrant it
JoeFCaputo113 said:
**IGNORE POST #1 ONLY FOLLOW POST #2-#4!!!**
Info and DL on SuperSU v2.6x and Systemless Root
1. MUST flash a 100% stock (Odin) firmware.
2. DL SuperSU v2.6x
3. Install custom recovery
4. Install new SuperSU zip
5. Let it run through the process then reboot.
Click to expand...
Click to collapse
Nice work will give this a go soon.
1619415 said:
Try installing/updating busybox and try removing titanium backups root access them regrant it
Click to expand...
Click to collapse
thank you. ill give it a try. :good:
This may be a weird question, but we don't have a stock kernel to flash. Would there be a way to make a zip of a stock kernel and then use this to get root? I'd like to have a custom ROM but with the stability of a stock Kernel. This is the first phone I can think of that I've owned that didn't have a stock kernel with root.