Related
so i rooted my s3 for sprint and beleive everything went fine i do have root...but everytime i am gonna install a rom..(tried 3 diffrent ones) while is installing the android drops flat on his back with the hood open and exclamation on his chest...can some one pls HELP ME AND THE LIL GUY OUT!!!
p.s i tried unrooting and and when checking .md5 file it fails so i cancelled..
HELP ME!!!!!
kay131108 said:
so i rooted my s3 for sprint and beleive everything went fine i do have root...but everytime i am gonna install a rom..(tried 3 diffrent ones) while is installing the android drops flat on his back with the hood open and exclamation on his chest...can some one pls HELP ME AND THE LIL GUY OUT!!!
p.s i tried unrooting and and when checking .md5 file it fails so i cancelled..
HELP ME!!!!!
Click to expand...
Click to collapse
Your going into download/odin mode. You need to go into whatever custom recovery you have to flash roms....
Damn its been a while since i did the 3 finger salute but i think it's power+home+ volume down.
If thats not it then its volume up lol.
Sent from a planet far far away.
Speedin07si said:
Your going into download/odin mode. You need to go into whatever custom recovery you have to flash roms....
Damn its been a while since i did the 3 finger salute but i think it's power+home+ volume down.
If thats not it then its volume up lol.
Sent from a planet far far away.
Click to expand...
Click to collapse
i have tried that and nothing.go into recovery mode and try installing the guy still drops dead.
kay131108 said:
i have tried that and nothing.go into recovery mode and try installing the guy still drops dead.
Click to expand...
Click to collapse
Recovery shouldn't have the android guy. What recovery are you using?
Sent from a planet far far away.
Speedin07si said:
Recovery shouldn't have the android guy. What recovery are you using?
Sent from a planet far far away.
Click to expand...
Click to collapse
ok.sorry you are right that was not recovery..can u pls be a little more specific.. if i press the three buttons with volume down is just an android in download mode..so what do i do next?...clockworkmodrecovery
kay131108 said:
ok.sorry you are right that was not recovery..can u pls be a little more specific.. if i press the three buttons with volume down is just an android in download mode..so what do i do next?...clockworkmodrecovery
Click to expand...
Click to collapse
If it's putting you in download switch the volume button your holding... so if holding volume down gold up instead and vice versa
SPRINT GS3 FAQ
kay131108 said:
ok..can u pls be a little more specific..i if i press the three buttons with volume down is just an android in download mode..so what do i do next?...clockworkmodrecovery
Click to expand...
Click to collapse
Ok, let's start at the very beginning (it's a very good place to start).
Before we get started, I'm going to make the following assumptions:
You successfully rooted your phone through Odin.
You currently have a custom recovery (either TWRP or CWM).
You have a Rom you'd like to flash on either your internal storage or your SDcard (I'd recommend the SDcard, but that's your prerogative).
If either of the first two is not true, I'd recommend going back to qbking77's thread and check out the videos on how to use Odin to gain root and a custom recovery.
If number 3 above is not true, download a ROM (nor someone new to flashing/custom Roms, I'd recommend Freeza's stock rooted Rom, as it's identical to stock TW, but just with Root). Once you download a Rom, check it's md5sum to verify that it's a good download. Copy the file to your SD card and get ready to flash (make sure you have decent battery life left, I try to keep at least 50% or more when flashing Roms, although it shouldn't take too long.
I'll give directions on how to flash a Rom below. The instructions will be for TWRP, but CWM has similar options/settings
Turn your phone completely off (hold down power for 3-5 seconds)
Boot your phone into recovery. Hold Up, Menu, and Power for a few seconds (until SAMSUNG appears on your screen and the phone vibrates)
Make a Nandroid backup. I can't emphasize this enough. In flashing, it's almost a certainty that one time, something will mess up. When that happens, you want to be able to restore a backup. In TWRP, just go into Backup Menu and choose where you want it (internal vs. External storage). It takes my phone a few (5-10) minutes to completely backup my data.
In TWRP, click the wipe button, then system. This will completely wipe the Rom from your phone. Doing this will allow you to get a "clean" install, without any settings or leftover files from your old Rom getting in the way. Instead, you could only wipe data (factory reset), which is good enough for most Roms. I'd still recommend a system wipe, though.
Also while in the Wipe menu, wipe Cache and Dalvik Cache.
Go back to the TWRP main menu.
Click Install, then find your Rom zip file (may have to switch from internal to external storage).
Let TWRP do it's thing.
If you're installing a TW-based Rom, chances are it had gapps already installed. If not, you should now flash the correct gapps package from goo.im. Make sure you're flashing the correct one, as if you don't, your google apps will force close upon use.
Reboot into system and give it time to boot (first boot sometimes takes a couple of minutes).
Set up your phone the way you like.
These should be the directions to follow whenever you flash a new Rom. Some Roms have the Aroma installer, so you'll have more options once you choose to flash the Rom zip, but those are typically easy to follow (and vary from Rom to Rom, so I won't be able to give you a good guide on that).
Hope this helps!
This guy and his mini-guide posts^
CNexus said:
This guy and his mini-guide posts^
Click to expand...
Click to collapse
He's spot on though, lol... great job topherk
SPRINT GS3 FAQ
topherk said:
Ok, let's start at the very beginning (it's a very good place to start).
Before we get started, I'm going to make the following assumptions:
You successfully rooted your phone through Odin.
You currently have a custom recovery (either TWRP or CWM).
You have a Rom you'd like to flash on either your internal storage or your SDcard (I'd recommend the SDcard, but that's your prerogative).
If either of the first two is not true, I'd recommend going back to qbking77's thread and check out the videos on how to use Odin to gain root and a custom recovery.
If number 3 above is not true, download a ROM (nor someone new to flashing/custom Roms, I'd recommend Freeza's stock rooted Rom, as it's identical to stock TW, but just with Root). Once you download a Rom, check it's md5sum to verify that it's a good download. Copy the file to your SD card and get ready to flash (make sure you have decent battery life left, I try to keep at least 50% or more when flashing Roms, although it shouldn't take too long.
I'll give directions on how to flash a Rom below. The instructions will be for TWRP, but CWM has similar options/settings
Turn your phone completely off (hold down power for 3-5 seconds)
Boot your phone into recovery. Hold Up, Menu, and Power for a few seconds (until SAMSUNG appears on your screen and the phone vibrates)
Make a Nandroid backup. I can't emphasize this enough. In flashing, it's almost a certainty that one time, something will mess up. When that happens, you want to be able to restore a backup. In TWRP, just go into Backup Menu and choose where you want it (internal vs. External storage). It takes my phone a few (5-10) minutes to completely backup my data.
In TWRP, click the wipe button, then system. This will completely wipe the Rom from your phone. Doing this will allow you to get a "clean" install, without any settings or leftover files from your old Rom getting in the way. Instead, you could only wipe data (factory reset), which is good enough for most Roms. I'd still recommend a system wipe, though.
Also while in the Wipe menu, wipe Cache and Dalvik Cache.
Go back to the TWRP main menu.
Click Install, then find your Rom zip file (may have to switch from internal to external storage).
Let TWRP do it's thing.
If you're installing a TW-based Rom, chances are it had gapps already installed. If not, you should now flash the correct gapps package from goo.im. Make sure you're flashing the correct one, as if you don't, your google apps will force close upon use.
Reboot into system and give it time to boot (first boot sometimes takes a couple of minutes).
Set up your phone the way you like.
These should be the directions to follow whenever you flash a new Rom. Some Roms have the Aroma installer, so you'll have more options once you choose to flash the Rom zip, but those are typically easy to follow (and vary from Rom to Rom, so I won't be able to give you a good guide on that).
Hope this helps!
Click to expand...
Click to collapse
ok..first thanx guys for taking your time to helping this noob..ok so on to biz.
You successfully rooted your phone through Odin...........YES I DID
You currently have a custom recovery (either TWRP or CWM)................I BELEIVE I HAVE CWM..AND I SEEN TWRP THROGH ROM MANAGER.
You have a Rom you'd like to flash on either your internal storage or your SDcard (I'd recommend the SDcard, but that's your prerogative). YES I HAVE A FEW ROMS ALREADY TO GO>
ok now here......
Turn your phone completely off (hold down power for 3-5 seconds)
Boot your phone into recovery. Hold Up, Menu, and Power for a few seconds (until SAMSUNG appears on your screen and the phone vibrates)................THE PHONE GOES TO A SCREEN THAT SAYS ANDROID SYSTEM RECOVERY <3e>.........
in this screen is a dead android with the hood open and red triangle with exclamation on it....and on the left hand side of the android in Yellow letters it says
# MANUAL MODE #
__APPLING MULTI-csc...
APPLIED the csc-code : SPR
succefully applied multi-csc.
hope this gives you some info on whats going on......
UPDATE:
i downloade goo manager and now have twrp recovery...going to try an install rom now....will update.
kay131108 said:
ok..first thanx guys for taking your time to helping this noob..ok so on to biz.
You successfully rooted your phone through Odin...........YES I DID
You currently have a custom recovery (either TWRP or CWM)................I BELEIVE I HAVE CWM..AND I SEEN TWRP THROGH ROM MANAGER.
You have a Rom you'd like to flash on either your internal storage or your SDcard (I'd recommend the SDcard, but that's your prerogative). YES I HAVE A FEW ROMS ALREADY TO GO>
ok now here......
Turn your phone completely off (hold down power for 3-5 seconds)
Boot your phone into recovery. Hold Up, Menu, and Power for a few seconds (until SAMSUNG appears on your screen and the phone vibrates)................THE PHONE GOES TO A SCREEN THAT SAYS ANDROID SYSTEM RECOVERY .........
in this screen is a dead android with the hood open and red triangle with exclamation on it....and on the left hand side of the android in Yellow letters it says
# MANUAL MODE #
__APPLING MULTI-csc...
APPLIED the csc-code : SPR
succefully applied multi-csc.
hope this gives you some info on whats going on.
Click to expand...
Click to collapse
You're still on stock recovery you need download goomanager from the play store hit the menu button and select install open recovery script to install twrp. Then reboot recovery and flash your rom :thumbup:
☆SoA: Son's of Android™☆
I like to break stuff!
Ok, it sounds like your recovery is bonked (and yes, that is the technical term). Something must've gone wrong when you were flashing the recovery through Odin (not necessarily your fault, sounds like it might've been a corrupted download).
One thing you can do is to download the latest TWRP. The way to do this is to install the GooManager app from the play store.
Once GooManager is installed, click on the "menu" button, then choose "Install OpenRecoveryScript." This will download and install the latest version of TWRP. Let it do it's thing then try to reboot into recovery again (you can do it directly from GooManager, it's one of the main options).
Let me know if that works.
Edit:
Originally Posted by -EViL-KoNCEPTz-
You're still on stock recovery <3e> you need download goomanager from ths play store hit thw menu button and select install open recovery script to install twrp. Then reboot recovery and flash your rom :thumbup:
Click to expand...
Click to collapse
Bah! Beat me to it! I had to get all wordy with my response!
topherk said:
Ok, it sounds like your recovery is bonked (and yes, that is the technical term). Something must've gone wrong when you were flashing the recovery through Odin (not necessarily your fault, sounds like it might've been a corrupted download).
One thing you can do is to download the latest TWRP. The way to do this is to install the GooManager app from the play store.
Once GooManager is installed, click on the "menu" button, then choose "Install OpenRecoveryScript." This will download and install the latest version of TWRP. Let it do it's thing then try to reboot into recovery again (you can do it directly from GooManager, it's one of the main options).
Let me know if that works.
Click to expand...
Click to collapse
Ninja'd they're still on stock recovery, the <3e> is a dead giveaway
☆SoA: Son's of Android™☆
I like to break stuff!
I know one of the steps with the Odin flashing it to reboot into Recovery before rebooting into the Rom (otherwise it re-installs the stock recovery). Do you think this person forgot to do that?
topherk said:
I know one of the steps with the Odin flashing it to reboot into Recovery before rebooting into the Rom (otherwise it re-installs the stock recovery). Do you think this person forgot to do that?
Click to expand...
Click to collapse
Most likely. Alot of people miss that step. You need to reboot recovery to disable the recovery install script that reflashes stock clockwork on boot.
☆SoA: Son's of Android™☆
I like to break stuff!
To the OP why do you say you are rooted? Have to tried to install an app which requires root access and where able to? I think you failed to root the device at all. I think you need to go through the process all over again to root your device. Once you flash the custom recovery via odin you can not let the phone reboot, you must pull the battery then boot into the custom recovery flash the team Epic root zip which will prevent the stock recovery from being installed again. Then at this point will you be able to reboot the phone. Once it boots up verify you have SU installed and have root access. Now the MOST IMPORTANT thing you are going to do is shut down, boot back into custom recovery (cwm) and make a nandroid backup.
Transmitted with a portable device using Xparent Blue Tapatalk 2
flastnoles11 said:
He's spot on though, lol... great job topherk
SPRINT GS3 FAQ
Click to expand...
Click to collapse
I know
To the OP please remember to use a heavy duty or Blackberry cable when using Odin or copying files to your phone from the computer.
YOU GUYS ARE THE GREATES SOB"S ON THIS EARTH,THNX TO ALL FOR YOUR HELP..i will be donating soon!!!.
kay131108 said:
YOU GUYS ARE THE GREATES SOB"S ON THIS EARTH,THNX TO ALL FOR YOUR HELP..i will be donating soon!!!.
Click to expand...
Click to collapse
If you don't mind telling us where was the issue?
Transmitted with a portable device using Xparent Blue Tapatalk 2
Hello all, I was wondering if anyone can point me in the right direction. I have a acer iconia a100 rooted and currently running the carbon rom (4.2.2) and twrp recovery (2.6.3.0). I would like to go back to stock rom (ICS). I have not changed any kernals or anything like that. Can I just restore my nandroid backup of my stock rom or is there something specific I have to do? Also, I just looked and I dont have a stock backup with twrp, only with cwm. When I unlocked bootloader, I installed cwm, then must have done a backup of stock rom, then flashed carbon rom, then switched to twrp and made another backup so I would have to go back to cwm to restore nandroid. How do I go back to cwm from twrp?? Thanks for the feedback.
I looked in my internal storage and it looks like I have 2 zips, fastbootrecovery.zip and xsposeddisabler-cwm.zip, do I flash one of these?? and if I do, can I do it with es explorer?? Thanks
jreink01 said:
Hello all, I was wondering if anyone can point me in the right direction. I have a acer iconia a100 rooted and currently running the carbon rom (4.2.2) and twrp recovery (2.6.3.0). I would like to go back to stock rom (ICS). I have not changed any kernals or anything like that. Can I just restore my nandroid backup of my stock rom or is there something specific I have to do? Also, I just looked and I dont have a stock backup with twrp, only with cwm. When I unlocked bootloader, I installed cwm, then must have done a backup of stock rom, then flashed carbon rom, then switched to twrp and made another backup so I would have to go back to cwm to restore nandroid. How do I go back to cwm from twrp?? Thanks for the feedback.
I looked in my internal storage and it looks like I have 2 zips, fastbootrecovery.zip and xsposeddisabler-cwm.zip, do I flash one of these?? and if I do, can I do it with es explorer?? Thanks
Click to expand...
Click to collapse
Just the stock ROM or completely back to stock, 100%?
If you don't know what those zips are, or how to use them, then don't use them, period.
To get back cwm you can use fastboot to flash it back on or use one of the cwm installers in development, if any are still there, if you want to do it with fastboot you'll need some stuff to get ready, most of it should be there from when you rooted the first time, then a couple lines in a command prompt and you'll have it back. There's also stock rooted ICS ROMs available, so depending on what you want we can go from there.
Tapatalked from my HTC DNA - Akakaze
pio_masaki said:
Just the stock ROM or completely back to stock, 100%?
If you don't know what those zips are, or how to use them, then don't use them, period.
To get back cwm you can use fastboot to flash it back on or use one of the cwm installers in development, if any are still there, if you want to do it with fastboot you'll need some stuff to get ready, most of it should be there from when you rooted the first time, then a couple lines in a command prompt and you'll have it back. There's also stock rooted ICS ROMs available, so depending on what you want we can go from
I am going to sell my tablet so I would like to go to my backup of my stock rom. When I restore my stock backup, I can just do a full wipe, that will get me back to the starting point of just the basic rom, right?? That will wipe all my data from the backup rom, or will a full wipe erase the rom too?? I want to get back to the basic rom (just like if I install a new rom) have to set up accounts, wifi, etc).
Also, is there a tutorial or a step by step guide to reinstall cwm back on my tablet, since my stock rom was backed up with cwm? And where do I have the files to reflash cwm. Thanks for your assistance in helping me return my tablet to the state I want.
Click to expand...
Click to collapse
I found a site that has it step by step, installing cwm. Here it is.
Here it is guys, Stock CWM Recovery for the ACER A100.
Before anything make sure you have the latest ICS leak C/O Vache, Root, and Unlocked Bootloader.
Official ICS Leak c/o Vache:
http://forum.xda-developers.com/show....php?t=1510706
Root Instructions here:
http://forum.xda-developers.com/show....php?t=1531646
Unlock your bootloader for fastboot, follow here:
http://forum.xda-developers.com/show....php?t=1557445
once you have done all of the above, you should be ready to flash this recovery. Make sure you have ADB up and working properly. And place the recovery.img in your working folder (see below)
1- Open a command prompt in your working folder (usually in your platform tools, mine is C:\android-sdk-windows\platform-tools) make sure you are administrator.
2- Connect Tablet to pc and get excited.
3- Type: adb devices (verify your Tab is connected and listed)
4- Type: adb reboot bootloader
5- Once bootloader is in fastboot type: fastboot flash recovery recovery.img
You will see writing recovery, flashing recovery, etc.
6- Once flashed Type: fastboot reboot
7- Profit
But it says make sure you have the latest ics leak?? Are they refferring to the rom?? If so, I currently have carbon rom istalled which is jellybean. This will not work then?? I am a little confused and any feedback would be greatly appreciated.
jreink01 said:
I found a site that has it step by step, installing cwm. Here it is.
Here it is guys, Stock CWM Recovery for the ACER A100.
Before anything make sure you have the latest ICS leak C/O Vache, Root, and Unlocked Bootloader.
Official ICS Leak c/o Vache:
http://forum.xda-developers.com/show....php?t=1510706
Root Instructions here:
http://forum.xda-developers.com/show....php?t=1531646
Unlock your bootloader for fastboot, follow here:
http://forum.xda-developers.com/show....php?t=1557445
once you have done all of the above, you should be ready to flash this recovery. Make sure you have ADB up and working properly. And place the recovery.img in your working folder (see below)
1- Open a command prompt in your working folder (usually in your platform tools, mine is C:\android-sdk-windows\platform-tools) make sure you are administrator.
2- Connect Tablet to pc and get excited.
3- Type: adb devices (verify your Tab is connected and listed)
4- Type: adb reboot bootloader
5- Once bootloader is in fastboot type: fastboot flash recovery recovery.img
You will see writing recovery, flashing recovery, etc.
6- Once flashed Type: fastboot reboot
7- Profit
But it says make sure you have the latest ics leak?? Are they refferring to the rom?? If so, I currently have carbon rom istalled which is jellybean. This will not work then?? I am a little confused and any feedback would be greatly appreciated.
Click to expand...
Click to collapse
Does anyone have any suggestions?? Thanks
Well, before the tab got official ICS, we had a leak. If you had read down the topics some you would've found it. You do not want cwm, you want twrp.
Sent from my SPH-L710 using xda app-developers app
das_webos_transformer said:
Well, before the tab got official ICS, we had a leak. If you had read down the topics some you would've found it. You do not want cwm, you want twrp.
Does anyone have any suggestions on whether it is ok to do this? Thanks
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
I need cwm to restore my stock rom. If I use the steps quoted below to reinstall cwm, will I run into any problems since I'm coing from carbon rom (jellybean) to stock rom which is (ICS)?
jreink01 said:
I need cwm to restore my stock rom. If I use the steps quoted below to reinstall cwm, will I run into any problems since I'm coing from carbon rom (jellybean) to stock rom which is (ICS)?
Click to expand...
Click to collapse
Does anyone know if this how to guide is good to use when coming from carbon rom (jellybean) to stock rom (ics))? Thanks
jreink01 said:
Does anyone know if this how to guide is good to use when coming from carbon rom (jellybean) to stock rom (ics))? Thanks
Click to expand...
Click to collapse
To just go back to stock to sell it you'll run into a couple issues coming from 4.2+, namely the storage path changes, you'll retain the /0 folders, however many were made. Otherwise following the guide that roman made will work to go back to 100% stock, I'll see if I can get a link, I'm in a waiting room with crappy data lol
Edit:
That guide will work for installing cwm, basically get your cwm image then get fastboot going, fastboot flash recovery cwmimageyougot.IMG
http://forum.xda-developers.com/showthread.php?p=33574648
Best way to return to 100% stock. No need to fuss with recoveries just install what he says then the ROM does the rest. While in twrp remember to go delete /0 directories or they'll remain there forever. Or until its deleted at a later date, but if you have stuff in there you should do it prior to going fully stock again.
Tapatalked from my HTC DNA - Akakaze
pio_masaki said:
To just go back to stock to sell it you'll run into a couple issues coming from 4.2+, namely the storage path changes, you'll retain the /0 folders, however many were made. Otherwise following the guide that roman made will work to go back to 100% stock, I'll see if I can get a link, I'm in a waiting room with crappy data lol
Edit:
That guide will work for installing cwm, basically get your cwm image then get fastboot going, fastboot flash recovery cwmimageyougot.IMG
http://forum.xda-developers.com/showthread.php?p=33574648
Best way to return to 100% stock. No need to fuss with recoveries just install what he says then the ROM does the rest. While in twrp remember to go delete /0 directories or they'll remain there forever. Or until its deleted at a later date, but if you have stuff in there you should do it prior to going fully stock again.
Tapatalked from my HTC DNA - Akakaze
Click to expand...
Click to collapse
Thanks for the response, youve fully confused me with the /0 folders?? What exactly is that?? When I go to es file explorer, I see sdcard0 (which looks like the internal storage) and sd01 which looks like my ext sd card. Is it one of those your are talking about??
Also, you said something about go delete in twrp, I went into twrp and did not find anything with that name?? am I deleteing something in twrp. Could you spell it out for me since I am a noob when it comes to reverting a device to stock. Thanks for taking the time to explain this.
jreink01 said:
Thanks for the response, youve fully confused me with the /0 folders?? What exactly is that?? When I go to es file explorer, I see sdcard0 (which looks like the internal storage) and sd01 which looks like my ext sd card. Is it one of those your are talking about??
Also, you said something about go delete in twrp, I went into twrp and did not find anything with that name?? am I deleteing something in twrp. Could you spell it out for me since I am a noob when it comes to reverting a device to stock. Thanks for taking the time to explain this.
Click to expand...
Click to collapse
that is something happening with cwm. i had this problem. it keeps creating a folder names 0 and keep moving old files into that whenever you install a new rom.
Hello guys. I need your feedback. I have a A100 that is rooted and is currently running carbon rom 4.2. I am going to be selling this in the next couple weeks because I just don't use it anymore now that I have a second pc.Do you think it would be more advantagious to sell this just the way it is (rooted and custom rom) or should I take it back to completely stock? Or if it is more advantagious to sell it with a custom rom, which rom would you guys suggest?? Thanks again for any and all suggestions.
Please Help!! I was trying to go to stock ics and these are the steps I used.The simple method to revert back to stock ICS from a custom ROM on an A100.
+++Locked bootloader, no custom recovery, no root. Full stock .014 rom. It will recieve OTA updates to latest Acer version.+++
Get Ready
1) Download this flashable Stock recovery zip, and place in your normal flashing location, - Thx 4 help pio
http://db.tt/VLmnMCzq
Also uploaded below
2) Download the Official .014 Stock ICS rom
The stock ICS zip from zeronull. http://forum.xda-developers.com/show....php?t=1611696
Here is a second link to it. http://ubuntuone.com/7DZtbNqZzOk7qsaQxNk99a - thx zleto
3) Rename the Stock ICS rom to "update.zip", no quotes (make sure you have "hide known file extensions" UNCHECKED, in the folder options). And place it on the root of your microSD card. This will allow you to see the file extension to verify that it is named properly.
Get it Done
1) Flash the Stock recovery zip with your custom recovery. Then wipe cache, davlik cache, and wipe data/factory reset.
2) Reboot to system.
3) Allow it to sit for 5 minutes or so.
4) Then Power off.
5) Update from the microSD card by holding down the power and volume rocker closest to the corner at the same time, until you see "erasing cache .".. ect, ect. The stock rom install should start by itself, dont touch anything, wait for it to reboot.
****** If it won't boot do a factory reset (with the hardware buttons, see below) and/or try to reflash the ics rom one more time. ******
Quote:
To perform a Factory Data Reset use the following steps:
1.Place the rotation lock switch in the up position (tablet held in portrait). Or to the left if held in landscape.
2.Press and hold the Volume down button, which is located farthest from the corner (it is volume up, if held in landscape).
3.With the Volume down button held, press and hold the Power button for 3 seconds then release it. Continue holding the Volume down button.
4.Once the tablet vibrates, switch the rotation lock on and off repeatedly while still holding the Volume down button.
5.Release the Volume down button and stop switching the rotation lock once the "Erasing Userdata..." message appears in the upper left corner of the screen
Now I get the android symbol with the red triangle, that stays for about a minute, then it reboots and stays on thye acer screen. When I did the steps and was going to reboot, I received a waring while in recovery sayiny that I dont have a op installed. I did it anyway, as posted and now I'm stuck, can anyone PLEASE help me.I tried doing a reset with steps 2 though 4 but while pressing the vol up and letting go of the power button, it does not vibrate.
I try to boot into recovery with vol up + power, it boots than says erasing cache, then booting into recovery, the the android synbol comes up with the red triangle.
I can't even get into recovery. It says bootloader (unlock mode) when I pwer it on. If I press power + vol up, it says erasing cache, then booting into recovery kernal, then the android symbol comes up with the red triangle.Thanks for responding and since this is the wrong thread, can we discuss this in the other thread?? While I was typing this, the android symbol with the triangle was on the screen for about 2 minutes, then it just rebooted and now its saying acer acer acer acer acer on the bottom of the screen.
Can anyone help me out with this please?
Phone: T-mobile Samsung Galaxy Note 2 SGH-T889
1. Rooted phone using Zedomax instructions with CWM Recovery 6.
2. Afterwards, unable to boot into recovery.
3. Installed ROM Manager from Playstore, and used it to successfully boot into Recovery.
4. Flashed Nightly CM11 Rom from XDADevelopers site, but forgot to flash GAPPS.
5. Afterwards, booted into CM11 but phone model is listed as N7105 (or something like that). It is not listed as SGH-T889 anymore.
6. Unable to boot into Recovery using Vol Up + Power + Home. The Samsung logo flashed and scrolls vertically twice.
7. Tried installing the GAPPS APK files one at a time, but some files would not install and as a result I was unable to get any GAPPS working.
8. I would like to flash back to stock and have an image, but scared if I do, then I might get stuck if I am unable to boot into Recovery again.
What should I do to get GAPPS applications back on the phone?
What is the correct firmware file named?
Thanks for any help you provide.
cardinal35 said:
Phone: T-mobile Samsung Galaxy Note 2 SGH-T889
1. Rooted phone using Zedomax instructions with CWM Recovery 6.
2. Afterwards, unable to boot into recovery.
3. Installed ROM Manager from Playstore, and used it to successfully boot into Recovery.
4. Flashed Nightly CM11 Rom from XDADevelopers site, but forgot to flash GAPPS.
5. Afterwards, booted into CM11 but phone model is listed as N7105 (or something like that). It is not listed as SGH-T889 anymore.
6. Unable to boot into Recovery using Vol Up + Power + Home. The Samsung logo flashed and scrolls vertically twice.
7. Tried installing the GAPPS APK files one at a time, but some files would not install and as a result I was unable to get any GAPPS working.
8. I would like to flash back to stock and have an image, but scared if I do, then I might get stuck if I am unable to boot into Recovery again.
What should I do to get GAPPS applications back on the phone?
What is the correct firmware file named?
Thanks for any help you provide.
Click to expand...
Click to collapse
Can you post a link to what you used. That method doesn't sound familiar and might possibly be part of the problem.
The N7105 model is not unexpected. It is the model for the intl Note 2.
It can mess with stuff if you use auto installing software such as Goo Manager and *maybe* Rom Manager. It might try to install the wrong recovery based on your inaccurate build prop device ID.
Which version of bootloader are you running? If you had official 4.3 you have fewer options for going back to stock. If when you boot into download (home+vol down+power) you see the word "knox" anywhere you have the 4.3 bootloader.
Look in the Development stickies and check for root66 by MrRobinson. Install Odin on a PC, make certain your phone communicates with the computer, the factory reset it. Install the appropriate version of root66 (UVBMC1 if you are non Knox, UVUCMK7 if you are on the Knox bootloader) following the instructions in the thread.
This should get you back to stock.
Once you can breathe again (getting stuck like that sucks) only flash roms from around here until you become comfortable with the nuances of going elsewhere.
Hastily spouted for your befuddlement
Procedures used to root and clarification
Coug76 said:
Can you post a link to what you used. That method doesn't sound familiar and might possibly be part of the problem.
The N7105 model is not unexpected. It is the model for the intl Note 2.
It can mess with stuff if you use auto installing software such as Goo Manager and *maybe* Rom Manager. It might try to install the wrong recovery based on your inaccurate build prop device ID.
Which version of bootloader are you running? If you had official 4.3 you have fewer options for going back to stock. If when you boot into download (home+vol down+power) you see the word "knox" anywhere you have the 4.3 bootloader.
Look in the Development stickies and check for root66 by MrRobinson. Install Odin on a PC, make certain your phone communicates with the computer, the factory reset it. Install the appropriate version of root66 (UVBMC1 if you are non Knox, UVUCMK7 if you are on the Knox bootloader) following the instructions in the thread.
This should get you back to stock.
Once you can breathe again (getting stuck like that sucks) only flash roms from around here until you become comfortable with the nuances of going elsewhere.
Hastily spouted for your befuddlement
Click to expand...
Click to collapse
The link to the root method I used:
galaxynote2root dot com galaxy-note-2-root how-to-root-galaxy-note-2-easiest-method
I only used ROM manager when I was unable to boot into Recovery after using the above procedure. ROM manager was used only to boot into recovery when I was unable to boot into it using the Vol Up + Power + Home keys method. It has an option to boot into recovery.
If I use the root66 method, is there a chance that I may get a boot loop upon boot after flashing? I read that moving from CM roms to stock might require booting into recovery after flashing the stock firmware file. That being the case, then I was afraid after flashing the right file, I still would not be able to boot into recovery.
Is there a way to simply get the GAPPS installed without recovery? I tried adb and unzipping to use File Manager to install each individual apk...no luck. The CM 11 ROM seems to work just no google apps.
But it would be nice to get back to stock fully too. Am looking into the bootloader version and root66 instructions. Thank you for the direction to follow.
Root66 will get you to a rooted stock beginning place. It will start you out with a bone stock device including bootloader and recovery (if done properly).
At this point if you reset the flash counter via triangle away, unroot the device, and factory reset it looks warranty eligible (unless you have the Knox bootloader tripped).
The reason you would do this: somewhere along the line something got screwed up and starting fresh is in order. Back up your data and start over.
Once you have a stock device, use the resources available here to guide you step by step. Tool kits are all well and good. If you take the steps yourself carefully after learning what they do and why, the mystery of a tool kit is gone. You can be confident into what you put into your device.
I would download the most recent version of TWRP recovery from their website (2.7.0.1) and flash it in Odin while I was at it. Recovery Odin flashes just like the root66 files.
Hastily spouted for your befuddlement
cardinal35 said:
The link to the root method I used:
galaxynote2root dot com galaxy-note-2-root how-to-root-galaxy-note-2-easiest-method
I only used ROM manager when I was unable to boot into Recovery after using the above procedure. ROM manager was used only to boot into recovery when I was unable to boot into it using the Vol Up + Power + Home keys method. It has an option to boot into recovery.
If I use the root66 method, is there a chance that I may get a boot loop upon boot after flashing? I read that moving from CM roms to stock might require booting into recovery after flashing the stock firmware file. That being the case, then I was afraid after flashing the right file, I still would not be able to boot into recovery.
Is there a way to simply get the GAPPS installed without recovery? I tried adb and unzipping to use File Manager to install each individual apk...no luck. The CM 11 ROM seems to work just no google apps.
But it would be nice to get back to stock fully too. Am looking into the bootloader version and root66 instructions. Thank you for the direction to follow.
Click to expand...
Click to collapse
there are more files than just apks in a gapps package.
How do I know which version of boot loader is running? I am currently on CM 11 Nightly.
Then which root66 T-Mobile ROM should I flash using Odin? I did not understand the Mobilicity, Videotron, etc., ROMs.
Sent from my SPH-D710 using xda app-developers app
cardinal35 said:
How do I know which version of boot loader is running? I am currently on CM 11 Nightly.
Then which root66 T-Mobile ROM should I flash using Odin? I did not understand the Mobilicity, Videotron, etc., ROMs.
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
to find out your bootloader version you need to boot into download mode. if you see the word knox on that screen you are on 4.3 bootloader. if you are on tmobile then you have no use for the other carriers roms (mobilicity etc)
Boot Loop after root66 UVBMD1
Coug76 said:
Can you post a link to what you used. That method doesn't sound familiar and might possibly be part of the problem.
The N7105 model is not unexpected. It is the model for the intl Note 2.
It can mess with stuff if you use auto installing software such as Goo Manager and *maybe* Rom Manager. It might try to install the wrong recovery based on your inaccurate build prop device ID.
Which version of bootloader are you running? If you had official 4.3 you have fewer options for going back to stock. If when you boot into download (home+vol down+power) you see the word "knox" anywhere you have the 4.3 bootloader.
Look in the Development stickies and check for root66 by MrRobinson. Install Odin on a PC, make certain your phone communicates with the computer, the factory reset it. Install the appropriate version of root66 (UVBMC1 if you are non Knox, UVUCMK7 if you are on the Knox bootloader) following the instructions in the thread.
This should get you back to stock.
Once you can breathe again (getting stuck like that sucks) only flash roms from around here until you become comfortable with the nuances of going elsewhere.
Hastily spouted for your befuddlement
Click to expand...
Click to collapse
1. Checked bootloader by going into Download Mode (Vol Down, Power, Home) and did not see Know anywhere.
2. I downloaded root66_TMO_T889UVBMD1.7z.
3. Installed using Odin after checking MD5 checksum.
Now the phone goes into a loop. It displays the Samsung logo, then goes to the T-Mobile Splash screen, then returns to Samsung logo...
Any ideas how I should proceed?
Solved!
cardinal35 said:
1. Checked bootloader by going into Download Mode (Vol Down, Power, Home) and did not see Know anywhere.
2. I downloaded root66_TMO_T889UVBMD1.7z.
3. Installed using Odin after checking MD5 checksum.
Now the phone goes into a loop. It displays the Samsung logo, then goes to the T-Mobile Splash screen, then returns to Samsung logo...
Any ideas how I should proceed?
Click to expand...
Click to collapse
Disregard last reply. I solved by:
1. Booting into Stock Recovery (Vol Up + Power + Home) and Factory Data Wipe/Reset.
2. Everything works on boot!
Thanks for all the help guys. What a relief...I will update if any problems are seen later.
So, after years of flashing roms on my phones, this is the first time I got a bootloop issue.
First of all, I tried to install the new Dn3 5.5 rom, which didnt get installed properly and ended up having my Knox warranty bit triggered.
Now on the 'downloading' screen, it shows two more lines,
KNOX WARRANTY VOID: 1
SWREV: A2
I read the forums and am guessing that even after this I should be able to flash custom roms, but I cant.
I tried installing the stock firmwares through Odin, but everything failed giving me an 'Invalid magic string' error, except the new FNI1 firmware, which I am assuming, worked because its the latest one and I cant downgrade due to the Knox bit being set.
Now although my phone has booted up, I rooted it using CF Auto root and de-knoxed it using Dr.Ketan's Multitool, I cant seem to turn off the phone.
Everytime I perform a reboot or 'power off' or even perform a hard restart, it shows the grey battery icon, turns off and loops again.
I have to clear the cache, after which it boots normally.
So, summarizing,
Phone gets a bootloop on the charging screen, and cannot install custom roms.
I am assuming its a bootloader issue, but need some guidelines by someone who has an idea about why this is happening just so that I dont mess up my phone more.
I need to perform a downgrade, and if possible reset the Knox bit too if anyone knows how to by now.
I think Dr.Ketan might be able to help out.
Thanks a lot.
Tan9890 said:
So, after years of flashing roms on my phones, this is the first time I got a bootloop issue.
First of all, I tried to install the new Dn3 5.5 rom, which didnt get installed properly and ended up having my Knox warranty bit triggered.
Now on the 'downloading' screen, it shows two more lines,
KNOX WARRANTY VOID: 1
SWREV: A2
I read the forums and am guessing that even after this I should be able to flash custom roms, but I cant.
I tried installing the stock firmwares through Odin, but everything failed giving me an 'Invalid magic string' error, except the new FNI1 firmware, which I am assuming, worked because its the latest one and I cant downgrade due to the Knox bit being set.
Now although my phone has booted up, I rooted it using CF Auto root and de-knoxed it using Dr.Ketan's Multitool, I cant seem to turn off the phone.
Everytime I perform a reboot or 'power off' or even perform a hard restart, it shows the grey battery icon, turns off and loops again.
I have to clear the cache, after which it boots normally.
So, summarizing,
Phone gets a bootloop on the charging screen, and cannot install custom roms.
I am assuming its a bootloader issue, but need some guidelines by someone who has an idea about why this is happening just so that I dont mess up my phone more.
I need to perform a downgrade, and if possible reset the Knox bit too if anyone knows how to by now.
I think Dr.Ketan might be able to help out.
Thanks a lot.
Click to expand...
Click to collapse
Knox trigger can't be reversed.
Of course, it is a bootloader issue. Follow the procedure and it should work out well for you.
1. Use stock recovery to wipe cache and factory reset.
2. Don't use cf-auto root.
3. Download Philz recovery latest version and supersu zip file. (For Note 2 )
4. Flash Philz. Uncheck auto reboot option in ODIN. Once you get pass message, unplug. Don't start your phone yet. Boot directly into recovery.
5. Install supersu zip file
6. Reboot to check if you are rooted.
7. DN3 5.5 has given me a headache. But it must be something ---- looking at the number of people using it.
8. I prefer Dr. Ketan's V12 Touchwiz ROM.
With Aroma installer, it is almost impossible to go wrong. Support is amazing. Doc himself answers all queries as fast as he can. But choice is yours.
Press thumps up if you found this suggestion helpful.
Link to all the files: http://www.ibtimes.co.uk/root-galax...d-4-4-2-kitkat-install-philz-recovery-1447891
Sent from my GT-N7100 using Tapatalk
Hi...Thanks for the quick reply.
Your solution did help, although partially. I liked the idea of unchecking the auto-reboot option.
I installed the SuperSU as you said, but the problem still remains. I think the bootloader resets all the root access everytime it boots. I had to go with CF autoroot to get it booting again.
But the good news is, with the autoreboot turned off, I was able to install a custom rom.
Here's what happened.
I installed the rom successfully, rebooted the phone n got back to the same battery screen again. Tried hard resetting it but couldnt get too the boot screen. Then I flashed the CF autoroot after which it booted fine into the Aosb rom.
I think a patched bootloader which removes the root disabling would do the trick here. Also, the recovery also gets removed during the next boot.
So is there any way to flash a different bootloader from ODIN? I have this Patched MJ5 bootloader, but there's an error saying 'SWREV: CHECK FAIL, DEVICE:2, BINARY:1'
Tan9890 said:
Hi...Thanks for the quick reply.
Your solution did help, although partially. I liked the idea of unchecking the auto-reboot option.
I installed the SuperSU as you said, but the problem still remains. I think the bootloader resets all the root access everytime it boots. I had to go with CF autoroot to get it booting again.
But the good news is, with the autoreboot turned off, I was able to install a custom rom.
Here's what happened.
I installed the rom successfully, rebooted the phone n got back to the same battery screen again. Tried hard resetting it but couldnt get too the boot screen. Then I flashed the CF autoroot after which it booted fine into the Aosb rom.
I think a patched bootloader which removes the root disabling would do the trick here. Also, the recovery also gets removed during the next boot.
So is there any way to flash a different bootloader from ODIN? I have this Patched MJ5 bootloader, but there's an error saying 'SWREV: CHECK FAIL, DEVICE:2, BINARY:1'
Click to expand...
Click to collapse
Don't flash old bootloaders. Now you are on NI1. (Only a 4.4.2-based bootloader can rewrite the existing bootloader)
Also, losing recovery is common. On 4.4.2, it gets rewritten. Hence, after flashing recovery you should not reboot the phone immediately.
Instead, as I said you press the key combo to enter recovery (preferably Philz recovery) as soon as you flash it.
Clear cache and factory reset.
Then you start the phone
Also, most custom ROMs are prerooted. You don't even have to use cf-auto or supersu zip to root your device if you intend to flash a custom ROM.
I don't know which ROM you like, but, ideally, a ROM should be prerooted, zip aligned and deodexed. For instance, DN3 5.5 and Dr.Ketan's V12 are the leading ones in this category. In fact, you have Omni, Phantom, Ultra, Diamond, etc, etc. One is simply spoilt for choice.
Caution: Bootloaders are sensitive. If they get screwed up, your phone will end up in service centre.
Sent from my GT-N7100 using Tapatalk
ceomaverick said:
Don't flash old bootloaders. Now you are on NI1. (Only a 4.4.2-based bootloader can rewrite the existing bootloader)
Also, losing recovery is common. On 4.4.2, it gets rewritten. Hence, after flashing recovery you should not reboot the phone immediately.
Instead, as I said you press the key combo to enter recovery (preferably Philz recovery) as soon as you flash it.
Clear cache and factory reset.
Then you start the phone
Also, most custom ROMs are prerooted. You don't even have to use cf-auto or supersu zip to root your device if you intend to flash a custom ROM.
I don't know which ROM you like, but, ideally, a ROM should be prerooted, zip aligned and deodexed. For instance, DN3 5.5 and Dr.Ketan's V12 are the leading ones in this category. In fact, you have Omni, Phantom, Ultra, Diamond, etc, etc. One is simply spoilt for choice.
Caution: Bootloaders are sensitive. If they get screwed up, your phone will end up in service centre.
Sent from my GT-N7100 using Tapatalk
Click to expand...
Click to collapse
Yes, but I am losing the recovery everytime when I boot. Its like, Once the rom gets set up and running. I should not switch off or restart my phone at all. Else it again goes back to the battery charging screen and gets stuck.
In case I have to reboot, I must flash the CF autoroot so that it restarts the rom.
Sounds weird right?
Tan9890 said:
Yes, but I am losing the recovery everytime when I boot. Its like, Once the rom gets set up and running. I should not switch off or restart my phone at all. Else it again goes back to the battery charging screen and gets stuck.
In case I have to reboot, I must flash the CF autoroot so that it restarts the rom.
Sounds weird right?
Click to expand...
Click to collapse
Very weird. Never heard of such a thing. Btw, which recovery you are using? TWRP or CWM. Also, chk if the version is latest. The latest versions are fixed for these very issues.
Probably, flashing N7100XXUFNI1 out of the box should solve your problem.
Beyond that I don't have answers.
Sent from my GT-N7100 using Tapatalk
Snippet taken from: http://mark.candleshoreblog.com/2013/06/13/tip-steps-to-prevent-clockwork-or-any-custom-recovery-from-being-overwritten-by-factory-stock-roms-at-android-system-reboot/:
The reason your stock recovery system keeps getting overwritten at Android startup is because of a script that is being run. All you need to do is either rename this script or simply delete it.
Please keep in mind that if you restore your stock ROM, this script will be restored with it so you will have to rename or delete it again. Do the following:
1.
Make sure your device is powered on and running normally,
2.
Make sure you have rooted your device and that you have all of the necessary permissions in order to manipulate system files.
3.
In the root file system go to \system\etc
4.
Find the file named install-recovery.sh and either rename it or, as I did, delete it.
That’s all there is to it.
Hey guys,
Im not new to rooting and custom roms and all, but I never had something like this happen before. I'm on 4.4.2 on my i747 and I got the cwm from Clockworkmod.com and every time I flash the custom recovery with odin 3 my stock recovery overwrites cwm. Can I use the 4.0.4 version of cf autoroot to root my phone or will it brick?
Any help is appreciated, thanks again
Easiest way to root this phone is just flash supersu in custom recovery.
1) Download a recovery flashable supersu.zip to the phone storage.
2) Use Odin to flash custom recovery (consider using TWRP, CWM hasn't been developed in quite some time). Be sure to uncheck auto-reboot in Odin. Upon success do not reboot into system, unplug the USB cable and pull the battery.
3) Replace battery and boot straight into recovery. Hold vol up + home + power together and don't let go until you see "recovery booting" in little blue text in the upper left.
4) Make a backup in recovery, just in case things go wrong.
5) Flash the supersu.zip in custom recovery.
6) Reboot into system.
You might have to update the supersu binary and reboot a few times until it gets Knox properly disabled and everything settles. Once you're rooted the stock rom will stop overwriting your custom recovery every time you boot into it.
This phone is very brickable, but generally not when messing with recovery, rooting, or custom roms. The things that tend to result in hard bricks are messing with the bootloader and modem (keep them matched and don't ever downgrade), accidentally flashing a rom intended for i9300 (the other S3), or attempting to unlock the already not locked bootloader. Use caution in those areas and this is actually a pretty modder friendly phone (especially for a Samsung).
jason2678 said:
Easiest way to root this phone is just flash supersu in custom recovery.
1) Download a recovery flashable supersu.zip to the phone storage.
2) Use Odin to flash custom recovery (consider using TWRP, CWM hasn't been developed in quite some time). Be sure to uncheck auto-reboot in Odin. Upon success do not reboot into system, unplug the USB cable and pull the battery.
3) Replace battery and boot straight into recovery. Hold vol up + home + power together and don't let go until you see "recovery booting" in little blue text in the upper left.
4) Make a backup in recovery, just in case things go wrong.
5) Flash the supersu.zip in custom recovery.
6) Reboot into system.
You might have to update the supersu binary and reboot a few times until it gets Knox properly disabled and everything settles. Once you're rooted the stock rom will stop overwriting your custom recovery every time you boot into it.
This phone is very brickable, but generally not when messing with recovery, rooting, or custom roms. The things that tend to result in hard bricks are messing with the bootloader and modem (keep them matched and don't ever downgrade), accidentally flashing a rom intended for i9300 (the other S3), or attempting to unlock the already not locked bootloader. Use caution in those areas and this is actually a pretty modder friendly phone (especially for a Samsung).
Click to expand...
Click to collapse
Thanks. 2 more questions,
1) Do I use the .img.tar file [twrp-3.0.2-0-d2att.img.tar] or the .img file [twrp-3.0.2-0-d2att.img] here > https://dl.twrp.me/d2att/
2) I have the kot94h....NJ2 build number on my phone as I attempted root before, does this matter?
Ulti2x said:
Thanks. 2 more questions,
1) Do I use the .img.tar file [twrp-3.0.2-0-d2att.img.tar] or the .img file [twrp-3.0.2-0-d2att.img] here > https://dl.twrp.me/d2att/
2) I have the kot94h....NJ2 build number on my phone as I attempted root before, does this matter?
Click to expand...
Click to collapse
The twrp files that end in .tar are packaged to be flashed with Odin.
I never updated my i747 past NJ1, but I've not seen any discussion that NJ2 changed anything with respect to rooting on this phone. Just try the stable TWRP flashable supersu.zip.
My experience has been that even if rooting this way fails the worst thing that happens is your rom won't boot, so you pull the battery, boot back into recovery, restore a backup, and you're back up and running. I've never had rooting this way fail on the good old i747, only on newer phones with stock marshmallow.
jason2678 said:
The twrp files that end in .tar are packaged to be flashed with Odin.
I never updated my i747 past NJ1, but I've not seen any discussion that NJ2 changed anything with respect to rooting on this phone. Just try the stable TWRP flashable supersu.zip.
My experience has been that even if rooting this way fails the worst thing that happens is your rom won't boot, so you pull the battery, boot back into recovery, restore a backup, and you're back up and running. I've never had rooting this way fail on the good old i747, only on newer phones with stock marshmallow.
Click to expand...
Click to collapse
Thanks so much. I will do what you told me and report back. By the way, do all att s3's have unlocked bootloaders?, and how do you update the supersu binary?
Ulti2x said:
Thanks so much. I will do what you told me and report back. By the way, do all att s3's have unlocked bootloaders?, and how do you update the supersu binary?
Click to expand...
Click to collapse
The i747 and i747m were all unlocked by default. I'm pretty sure t999's are too.
Verizon's were locked. There was an unlock exploit for Verizon. Occasionally I read about someone trying it on an AT&T S3 and bricking it here.
I think supersu will pop up something on it's own if it is out of date, and retrieves what it needs from the Play store. It has been ages since I actually rooted stock on this phone. I vaguely remember Knox blocking root, supersu updating, rebooting a time or two then supersu eventually offering to disable Knox.
jason2678 said:
The i747 and i747m were all unlocked by default. I'm pretty sure t999's are too.
Verizon's were locked. There was an unlock exploit for Verizon. Occasionally I read about someone trying it on an AT&T S3 and bricking it here.
I think supersu will pop up something on it's own if it is out of date, and retrieves what it needs from the Play store. It has been ages since I actually rooted stock on this phone. I vaguely remember Knox blocking root, supersu updating, rebooting a time or two then supersu eventually offering to disable Knox.
Click to expand...
Click to collapse
I got backed up and successfully rooted. Thanks so much for the help. By the way, in logs and apps in supersu free it shows the loading circle forever, does that matter? I still have full root access to all apps.
EDIT: Turned out I needed a reboot to disable KNOX, you were right. Thanks for all your help jason!