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
Related
Hi everyone,
pardon me for my noobiness
I have tried cf autoroot step by step with caution. but my device still stays unrooted.
i have i747 at&t with 4.1.2
in odin i does see everything as good, but no SuperSU app.
root checker goes in infinte loop returns nothing, Tibu says device not rooted.
do i have options?
i want to stick to 4.1.2 TW stock with root access, twrp and triangle away to reset my counter.
as I already used CW 10.2 JB 4.3 and was missing my ugly touchwiz, camera, multiwindow
mr.squiggly said:
Hi everyone,
pardon me for my noobiness
I have tried cf autoroot step by step with caution. but my device still stays unrooted.
i have i747 at&t with 4.1.2
in odin i does see everything as good, but no SuperSU app.
root checker goes in infinte loop returns nothing, Tibu says device not rooted.
do i have options?
i want to stick to 4.1.2 TW stock with root access, twrp and triangle away to reset my counter.
as I already used CW 10.2 JB 4.3 and was missing my ugly touchwiz, camera, multiwindow
Click to expand...
Click to collapse
If the auto root worked (rebooted into recovery and did it's thing) than just download SuperSU from the play store. Update the binary by opening the app and than recheck for root.
Sent from my SGH-I747 using xda app-developers app
after trying for 5 times, it worked.
i am rooted now.
but have another issue, gave my google account for phone setup. also used mrrobinson debloater.
noticed that none of my apps from playstore are getting installed on my phone.
is it because mrrobinsoon debloater deleted something or its just me , a noob..
pls help.
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
Here is what happened, i downloaded the OTA from AT&T, unrooted my phone and installed the update. It went all the way through, rebooted and that's where it stops. As soon as the AT&T welcome screen comes up the phone just freezes. When i plug it to my PC the phone is not recognized. Kies says it can't connect to the device. I'm able to get into download mode and odin seems to find the phone. But in download mode there is no option to reboot or anything. It only says "custom" on all options.
Can anybody help?
Factory reset usually solves most boot hangups. It will wipe your internal sd if you have stock recovery though.
i can't find any option to do a factory reset. I flashed Philz touch with odin, it said it passed. Tried a factory reset but it still freezes at the AT&T homescreen.
Any other way to do a factory reset?
Why'd you re-root BEFORE installing the update? Is there a particular reason? From what I've read on here, towelroot will easily root it afterwards.
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app
keithfrombm said:
Why'd you re-root BEFORE installing the update? Is there a particular reason? From what I've read on here, towelroot will easily root it afterwards.
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app
Click to expand...
Click to collapse
I took root off the phone since most of the time root stops OTA updates. Then i downloaded and installed the update. I had plans to root it again after the update.
Hello there. I also attempted the 4.4.2 OTA from stock 4.3, and now I'm having this exact same issue. The device had TWRP recovery installed, so I re-installed the stock recovery. It was also rooted and a few system files were edited (lock sounds, hosts file), I reverted all the changes, did a full unroot via SuperSU and proceeded with the OTA. It seemed successful until it tried to boot.. it now freezes on the AT&T logo, as the OP mentioned. I installed TWRP recovery again via Odin so I could back up all the data from the phone and do a factory reset. Unfortunately, this did not fix the freezing. I've attempted reverting back to the latest official Odin .tar (4.1.1), which I've now learned is not possible since the 4.3 update and its locked bootloader. It would seem that the only thing that would do the trick now would be an Odin-flashable 4.4.2 tar. For now, I've installed CyanogenMod as a temporary solution.
I dunno if it has been tested yet but this is a TWRP/CWM flashable zip which also preserves root.
http://forum.xda-developers.com/showpost.php?p=53539462&postcount=5
It didnt work. I am currently uploading two more attempts now and will post the links in that thread as soon as they are ready.
this worked for me
Hi All, Just wanted to share a solution that worked for me. I was in the same boat. OTA update locked phone on ATT screen. Used steps 2 and 6 from link below and now have 4.4.2 running on my phone. Happy flashing.
http://forum.xda-developers.com/showthread.php?p=53574211
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
I used supersu to root my original phone on 4.1.1. this was maybe 2 years ago. i want to update to 4.4 but the root doesnt let me, so i uninstalled SuperSU hoping it would unroot and tried to update usin g"software update". still nothing--hitting the butting doesnt even register a click.
tried using odin to update but it stalls on one of the early processes (then i realized i needed root for this step!)
so i went to DL SuperSU again but installing it doesnt work: "There is no SU binary installed and SuperSU cannot install it. This is a problem!"
What to do??
The simplest way to get to 4.4.2 via OTA updates would be to use Odin and flash back to completely stock 4.1.1.
Using Odin will wipe all data files on the phone.