I just updated my device from MK6 to NA7. My device was rooted..But obviously it is not rooted anymore after the upgrade. However, the same method i used to root MK6 isn't working for NA7. Any advice on how to regain root access? In the mean time i went back to MK6 and re-rooted my device until i can root the newer version..then i will re-update and root.
If you have Phil's touch recovery then go to Phil's settings and re root and after booting install supersu from play store and update binaries the normal way after opening app.. else go to chain fire thread of supersu and download zip file and flash it through recovery...
Sent from my GT-I9300
Related
(SOLVED)
Hey guys, first time root here. HTC One AT&T 32gb
I was succesfully through the process, used a guide on htconeroot.com to go through all of the steps. Everything went just as expected and I had root access through superSU (was able to install and use root apps, such as Titanium Backup and AdFree). I used Root Manager to flash Clockworkmod because I saw a ROM I'd like to use in the future that only supported that custom recovery. After succesfully flashing that, I then made a backup using Root Manager. Everything was successful and expected, but upon reboot into my stock ROM from the original unrooted phone I had apparently lost SU binaries and root access. Also, ROM Manager (v5.5.3.0) cannot find any backups.
I tried reflashing superSU from the original rooting guide (UPDATE-SuperSU-v1.65.zip), and while it was successfully rooted, I still did not gain root access. I had read through some forums that using the stock ROM that came with the phone might lose root because of the stock recovery, but not sure if that is what happened. I have not installed a custom ROM on this phone yet.
Any help would be appreciated.
UPDATE: Solved, had to select "No" when rebooting from CWM on stock recovery option
I encountered a strange problem while using Mobile Odin Pro v.3.85 with 4.3 MK6
My phone : Samsung Galaxy S3
I usually use Mobile Odin Pro to flash firmware, i enable inject Root and SU so I wont lose Root and dont increase counter, staying all official.
Let me explain what I did.
I started from 4.1.2 all stock with root and MOP v 3.50 (mobile odin pro v 3.50). Downloaded MK6 firmware from thread in general s3 section and flashed using MOP with ever root: everything okay Im on 4.3. I tryied to open SuperSu and it says there isnt any SU binary with a message saying: "if you just updated to 4.3 install root manually". So i used CF Auto Root for S3 and installed it: once rebooted i couldnt find any SU icon in drawer, had to download latest from Play Store and I was rooted but with counters to "Unofficial" since I flashed with odin.
Now I reflashed 4.3 to avoid getting Unofficial Status: updated MOP to 3.85 latest, it auto downloads flash kernel, flashed 4.3 with everroot (I was already on 4.3 but with unofficial status). All I was hoping to achieve was a 4.3 rooted with MOP 3.85 and all counters to official. For past versions like 4.1.2 it worked!
MOP rebooted S3 and started flashing 4.3: at the end it was in a loop, it continued to flash 4.3 over and over.
Why I got that loop? It was an compatibility issue with 4.3 bootloader and MOP flash kernel?
Have I to downgrade bootloader to ICS first (like I had before)?
I had to go in download mode and flash 4.3 using pc odin, I was so scared! Now im on 4.3 without root but id like to have it with counters set to official.
Thank you, steebro.
loop issue
steebro said:
I encountered a strange problem while using Mobile Odin Pro v.3.85 with 4.3 MK6
My phone : Samsung Galaxy S3
I usually use Mobile Odin Pro to flash firmware, i enable inject Root and SU so I wont lose Root and dont increase counter, staying all official.
Let me explain what I did.
I started from 4.1.2 all stock with root and MOP v 3.50 (mobile odin pro v 3.50). Downloaded MK6 firmware from thread in general s3 section and flashed using MOP with ever root: everything okay Im on 4.3. I tryied to open SuperSu and it says there isnt any SU binary with a message saying: "if you just updated to 4.3 install root manually". So i used CF Auto Root for S3 and installed it: once rebooted i couldnt find any SU icon in drawer, had to download latest from Play Store and I was rooted but with counters to "Unofficial" since I flashed with odin.
Now I reflashed 4.3 to avoid getting Unofficial Status: updated MOP to 3.85 latest, it auto downloads flash kernel, flashed 4.3 with everroot (I was already on 4.3 but with unofficial status). All I was hoping to achieve was a 4.3 rooted with MOP 3.85 and all counters to official. For past versions like 4.1.2 it worked!
MOP rebooted S3 and started flashing 4.3: at the end it was in a loop, it continued to flash 4.3 over and over.
Why I got that loop? It was an compatibility issue with 4.3 bootloader and MOP flash kernel?
Have I to downgrade bootloader to ICS first (like I had before)?
I had to go in download mode and flash 4.3 using pc odin, I was so scared! Now im on 4.3 without root but id like to have it with counters set to official.
Thank you, steebro.
Click to expand...
Click to collapse
Hi! Regarding your boot loop problem, may I suggest that after you flash with MOP, do go into recovery (cwm) and first do a wipe data / factory reset, followed by wipe cache partition. This will give you a fresh rom install. I may be wrong, but that is usually where the problem lies (not doing a wipe data / wipe cache after a fresh (official) ROM install. That's what I have read on countless forums. Hope it helps. Good luck!
I have a Samsung Galaxy S3 T99L with 4.3 version.. I recently decided to try to root it (I rooted my old phone, but since this one was new i dint root it before) and its giving me headaches!
I rooted it with CF Auto Root for the same model, I followed instructions (using Odin to root), and when my phone resets, I think its KNOX or the system itself blocks SuperSU. This is another problem, I open SuperSU and the first thing it appears is ''There is no SU binary installed and SuperSU cannot install it'' and then it closes and theres a notification that SuperSU got blocked by the security thing. PLEASE HELP!
Btw: I cant find stock for t99l
Hi, folks,
I have pretty much wasted the past 3-4 hours trying to get cwm superuser to work.
I installed .314 UK generic firmware using FlashTool & unticked wipe data, then used TowelRoot v12 to root then flashed NUT's dual recovery but no matter what cwm superuser flashable zip I use I cant get it to work right, it always prompts me to use recovery install when I open the SuperUser app, tried that but I just get error saying there was a error installing SuperUser. If I disable SuperUser then install SuperSU & SuperSU pro from market I get root access but SuperSU has always had issues with AdAway applying the hosts file so I switched to CWM SuperUser when I was on .402 firmware.
I did have the flashable CWM zip file but can no longer find it
Really need some help with this.
BanziBaby said:
Hi, folks,
I have pretty much wasted the past 3-4 hours trying to get cwm superuser to work.
I installed .314 UK generic firmware using FlashTool & unticked wipe data, then used TowelRoot v12 to root then flashed NUT's dual recovery but no matter what cwm superuser flashable zip I use I cant get it to work right, it always prompts me to use recovery install when I open the SuperUser app, tried that but I just get error saying there was a error installing SuperUser. If I disable SuperUser then install SuperSU & SuperSU pro from market I get root access but SuperSU has always had issues with AdAway applying the hosts file so I switched to CWM SuperUser when I was on .402 firmware.
I did have the flashable CWM zip file but can no longer find it
Really need some help with this.
Click to expand...
Click to collapse
If you're not on CWM, you can't use CWM SuperUser. Install SuperSU and use that. You can also switch to AdFree which is what I use. You'll also need to install XZDualRecovery to be able to write to /system.
Sent from my SGP311 using XDA Free mobile app
Thanks for the reply
I was using CWM superuser with no issues on .402 UK generic & Philz recovery, I have always had issues with SuperSU both on my old Galaxy S3 with custom roms & now on my Z2, most of the time with SuperSU any app that needs root access will freeze due to the delay in SuperSU showing the alert & as I mentioned above with AdAway not being able to apply the hosts file 90% of the time.
I also have Dual Recovery installed but keep losing it, seems that using the NDR tools app it installs causes the phone to forget that the recoveries are installed.
Just want some help with this issue & it would be great if someone could post a working kitkat CWM superuser flashable zip.
Can anyone else help me with this?
Have just done a full wipe & used Flashtool to install UK generic .314, have used EasyRoot 12.1 to root & it says I'm rooted. I then install CWM SuperUser from market & when opening it says the su binary needs to be updated & only gives recovery install or cancel options, I chose recovery & it reboots into Philz recovery & says it has installed but Philz says root is broken. When I boot the phone again I get a notification from SuperUser saying the binary needs to be updated again but when I tap recovery it just says there was a error.
Really would appreciate some help here as I need to get AdAway installed, change the DPI & use the nextapp kitkat SD fix app.
Cheers.
EDIT: forget it, got it fixed myself, now CWM superuser is working fine.
Hey, I'm have the VZW s4 running on straight talk. I am running a rooted, stock 0F1. I rooted using kingroot. Now my problem is that kingroot is currently by default my root manager. I know that I need to update the binary for supersu, have the zip file ready to go and have flashfire installed. However, without supersu installed, flashfire won't recognize kingroot and won't let me flash anything. Is there a way I can flash this through Odin or the stock recovery. Thank you to anyone who can help and if you need more info or sc's just let me know
gms183russ said:
Hey, I'm have the VZW s4 running on straight talk. I am running a rooted, stock 0F1. I rooted using kingroot. Now my problem is that kingroot is currently by default my root manager. I know that I need to update the binary for supersu, have the zip file ready to go and have flashfire installed. However, without supersu installed, flashfire won't recognize kingroot and won't let me flash anything. Is there a way I can flash this through Odin or the stock recovery. Thank you to anyone who can help and if you need more info or sc's just let me know
Click to expand...
Click to collapse
There should be a thread here with instructions on how to switch. Search around and if I find it I'll hit u with the link and hopefully get u on the right path.