[Q] SGH-I317m SuperSu Force Close - AT&T Samsung Galaxy Note II

Hey guys,
Just bought this unlocked Note 2 (SGH-I317M) from someone. I had a previous note 2 that died.
I just rooted the phone to install a custum ROM. Right now I'm at the step where I just rooted it using
CF-Auto-Root-t0ltecan-t0ltevl-sghi317m.tar.md5 on odin 3.09.
I think the root went fine cause the Odin boxed said "pass".
When the phone reboots thought SuperSU is always force closing, so I cannot confirm the root process by going into Titanium Backup since SuperSu is closed.
If I install a custom rom, will that problem disappear?
How can I be sure that the phone has rooted properly?
Since I just bought it, I wish I would not brick it the first night!
Thanks for your time and knowledge!

What recovery do you have installed?
And if you flash a custom Rom that's already rooted then you'll be good to go with root. :thumbup:
Did you try updating the super SU app, to the latest version from the play store??
Sent from my SAMSUNG-SGH-I317 using Tapatalk

Related

How do i install update on rooted note2?

I have a rooted sprint note 2 and i keep getting a system update. Everytime i try to install it the phone goes to TWRP recovery and does nothing. What do i have to do to download and install this update and how do i do it? Im really new to rooting and would appreciate any help. Im not running any roms or anything. I only rooted so i can wifi tether.
boriqua2000 said:
I have a rooted sprint note 2 and i keep getting a system update. Everytime i try to install it the phone goes to TWRP recovery and does nothing. What do i have to do to download and install this update and how do i do it? Im really new to rooting and would appreciate any help. Im not running any roms or anything. I only rooted so i can wifi tether.
Click to expand...
Click to collapse
There is an all in one update zip that you can flash in recovery that will get you from ma7 to mc2 or use root explorer and navigate to etc/security and rename otacerts.zip to otacerts.zip.bak reboot phone and those update notices should stop.
Hope this helps
Sent from my SPH-L900 using Tapatalk 2
Just install this rom. I just did it and it solved all my issues. You will need to flash modem separately. The kernel can be left the same as I dont know if that was updated too. But if you need that I posted link here also.
http://forum.xda-developers.com/showthread.php?t=2241930
Modem and kernel:
http://forum.xda-developers.com/showthread.php?t=2240961
Hopefully this helps.
Sent from my Amazing Galaxy Note 2!
What would happen if i go into my file manager and delete. The twrp file? Will that work or will it just mess up root?

help needed! Trying to root and install OmniROM 4.4 on my i747

hey guys. lurker turned new poster here at XDA. a friend of mine turned me on to this a while back when he introduced me to the world of rooting. I've recently bought a Galaxy S III (SGH-i747), and I've been trying to root it using mskip's unified toolkit (http://forum.xda-developers.com/showthread.php?t=1979290). I got it rooted once, but eventually bricked it when trying to get 4.4 on it, and had to reinstall the stock 4.1.1 rom on it and lost the root in the process.
I'm completely new to all this, and I'm still trying to figure it out. I've been searching as much as I can and reading a lot, but I'm not sure if there's something I'm missing here. when I try to root it lately using the toolkit, it gets stuck in the process after I exit Odin, and will never progress.
before when the root was actually in place, I tried to install a custom OS after doing a full wipe of the system, and it never would install. I tried it with TWRP and CWM, and there was no success with either of them. the one peculiar thing, however, is that I could never get it to install with the "ALLINONE" option. when I got it to work that once, I had to install it each individually.
is there some sort of guide out there that would make this easier for me to get 4.4 on the phone? or will someone be able to help me through the process?
thank you for your time!
I just rebooted my comp, reinstalled the drivers for the phone through the toolkit, and gave it one more shot at rooting it (option 1 in the program), and this is what the process looked like.
*see attached image*
I *always* get stuck at the "pushing superuser.apk and su binary.." part.
any thoughts?
hachikid said:
I just rebooted my comp, reinstalled the drivers for the phone through the toolkit, and gave it one more shot at rooting it (option 1 in the program), and this is what the process looked like.
*see attached image*
I *always* get stuck at the "pushing superuser.apk and su binary.." part.
any thoughts?
Click to expand...
Click to collapse
I used this when I first rooted my I747. http://galaxys3root.com/galaxy-s3-root/how-to-root-att-galaxy-s3-sgh-i747/
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
My Bell s3 was on 4.1.2. I rooted by installing a rooted rom from here: http://forum.xda-developers.com/showthread.php?t=1739426
Do not flash a 4.1.1 or 4.1.2 rom if you have a bootloader from 4.3.
when I got the phone, it had 4.1.2 on it. when I bricked it, I flashed a stock 4.1.1 ROM on it, and that's what I've been using as my base ROM.
Boomer1605: I'll try that when I get home.
anyone else know what is up with the place I get stuck at during the toolkit way?
My Bell s3 was on 4.1.2 when I got it. SInce I needed to unlock it and didn't want to pay, I installed the stock Bell 4.1.1 firmware from here: http://www.sammobile.com/.
After using the menu option to unlock the phone and confirm that it was unlocked, I flashed the pre-rooted Bell s3 4.1.2 rom.
Everything worked perfectly, no errors or issues at all.
Cool! Can I find a pre-rooted 4.1.1 AT&T rom on that site? I can't really look at that link cause I'm currently at work.
Pre-rooted roms are here: http://forum.xda-developers.com/showthread.php?t=1739426
I was able to install Root Explorer on my pre-rooted ROM and delete a tonne of Samsung apps.
I was able to install a pre-rooted version of 4.1.1, and I did a system/data/cache/dalvik wipe from the TWRP screen, but when I tried to install both Liquid Smooth and Omni Rom, it failed. I even restarted and didn't wipe, and it still failed. not sure where to go from here... :/
tativle coast
totally got it to work! I skipped using the toolkit to install TWRP, and used GooManager to use the latest TWRP. worked like a charm! currently running on Liquid Smooth 4.4.2!
thanks for the rooted copy of 4.1.1!
hachikid said:
totally got it to work! I skipped using the toolkit to install TWRP, and used GooManager to use the latest TWRP. worked like a charm! currently running on Liquid Smooth 4.4.2!
thanks for the rooted copy of 4.1.1!
Click to expand...
Click to collapse
Awesome! Congratulations. For future reference, TWRP also had tar images for use with Odin.

[Q] unstable root on stock 4.3

Hi,
I have a note 2 N7100 and a few days ago installed a German stock rom downloaded from samfirmware. Then I rooted it (I tried posting a link to the rooting instructions but new users can't post links).
When the phone rebooted after root, I got a message from superSU app to manually re-root. Then I just restarted the phone, and suddenly I had root privileges!
Since then, after each restart I sometimes have root and sometimes not. Mostly not. Sometimes I have to restart 10 times in a row before the root works. If I go to CWM recovery, it warns me that the rom will try to reinstall the stock recovery and asks if it should try to prevent this, I say yes but it doesn't change anything.
I also used to get a lot of knox warnings so I froze everything that had the word "knox" in it using titanium backup.
Is there an explanation for this weird behavior? Can I do something to fix it?
I have the same problem with you when rooting by kingo app. But when I reflash firmware and root by lastest cfautoroot and update supersu in play store everything is stable.
Sent from my GT-N7100 using Tapatalk

[Q] Newbie (kinda) help rooting my note

I've been rooting phones for a few years now (my evo and my Note 2.) I had my note 2 rooted for about a year and while having performance issues with Sprint (hate sprint) I flashed back to stock and updated everything, including the firmware. Ugh, I updated the firmware to the new knox firmware. Not knowing I was up a creek, I reflashed my phone with the tools I already had and had already used and triggered knox and cant get a recovery to stick. As far as I can tell the phone is still stock with knox tripped and I cant get any farther. I've spent a few hours reading now and I cant seem to find a way to either reverse knox or root the phone with knox tripped. I tried the cf auto root in the origional development section and couldn't figure it out.
Anybody got any advice, or a link to a thread started post knox so it talks about how to deal with it?
koker93 said:
I've been rooting phones for a few years now (my evo and my Note 2.) I had my note 2 rooted for about a year and while having performance issues with Sprint (hate sprint) I flashed back to stock and updated everything, including the firmware. Ugh, I updated the firmware to the new knox firmware. Not knowing I was up a creek, I reflashed my phone with the tools I already had and had already used and triggered knox and cant get a recovery to stick. As far as I can tell the phone is still stock with knox tripped and I cant get any farther. I've spent a few hours reading now and I cant seem to find a way to either reverse knox or root the phone with knox tripped. I tried the cf auto root in the origional development section and couldn't figure it out.
Anybody got any advice, or a link to a thread started post knox so it talks about how to deal with it?
Click to expand...
Click to collapse
You shouldn't be up a creek. What recovery did you flash? Try the latest Philz for note2. Unchecked auto-reboot in Odin before flashing it, and when it's done pull the battery then put the battery back in and do the power button/home button/volume up to get into recovery...
Sent from my SPH-L710 using Xparent Cyan Tapatalk 2
g_money said:
You shouldn't be up a creek. What recovery did you flash? Try the latest Philz for note2. Unchecked auto-reboot in Odin before flashing it, and when it's done pull the battery then put the battery back in and do the power button/home button/volume up to get into recovery...
Sent from my SPH-L710 using Xparent Cyan Tapatalk 2
Click to expand...
Click to collapse
I've been using the unified android toolkit. It seemed to work flawlessly before knox. Now it just stalls. Odin installs the custom recovery, the phone reboots, and goes into the stock android recovery. So I unchecked the auto reboot option, flashed CWM, and while looking nervously at the do not power down device screen, pulled the battery. It booted into CWM fine, flashed Paranoid Android and gapps fine, and rebooted into the new ROM just fine.
Not really sure why I was having problems, or why the pull the battery step is necessary, but it seems to have worked. I did not flash any SU files. Is that necessary?
I would download 1 of the root checker apps, or just install an app that requires root.
Usually (though I can verify not always. Lol) you have to reboot directly into download mode to finish the install of the custom recovery. If you let your phone reboot, stock recovery will over-write the custom recovery that you're trying to install...
Sent from my SPH-L710 using Xparent Cyan Tapatalk 2
I ran a root checker and it says I do not have root access. But the phone is running paranoid...so what am I missing here? I thought I needed root access to install the recovery and install a ROM. Seems I do not. Should I care about the lack of root access? Because all I really wanted was to replace the ROM, and that seems to have worked.
koker93 said:
I ran a root checker and it says I do not have root access. But the phone is running paranoid...so what am I missing here? I thought I needed root access to install the recovery and install a ROM. Seems I do not. Should I care about the lack of root access? Because all I really wanted was to replace the ROM, and that seems to have worked.
Click to expand...
Click to collapse
PA Roms work funny with root access on my device also. Just download and flash the latest SuperSU zip. If you already have it installed wipe the data first.
Sent from my SPH-L900 using XDA Free mobile app

Stuck, can't install recovery

When I got this note 2, it didn't have the ota to lock the bootloader. I after a year or so on the Alliance 26 rom I had some issues and wanted to upgrade to the newest one. I tried to install it and it didn't take and was stuck in bootloop.
So I used the same files in odin to flash the phone back to stock and start it again.
I was finally able to get it rooted but no recover will install. I am having a hell of a time and I don't understand what I have done wrong. Even casual wont work.
Well when I try to install recovery like twrp the install fails and on boot it says software not supported my Verizon , take to your local vzw store for repair.
Knox has even been tripped as well and it seems like the bootloader is locked. How is that possible? Don't know how, i flash with odin a stock rom as I did when I got the phone rooted and installed a recovery and than a rom. No issues what's so ever.
Now it seems everything I try it either says software not supported by vzw or bad firmware update or boot loops. I have downloaded so many files from all of these recovery threads I'm lost .
Never had the ota update, once I got the phone I flashed it to mj9 per beanstown on the original alliance rom and ran that room ever since.
I think I have tried every how to in this forum. Can someone chime in and tell me what I am doing wrong?
Sent from my SCH-I605 using Tapatalk 2
Phone info..
Sent from my SCH-I605 using Tapatalk 2

Categories

Resources