Hi
I have installed SuperSU to my phone
Will this stop me getting any updates OTA
Thanks
Lee
No,
But you may lose root after ota.
Sent from my GT-N7000 using xda premium
Well, I installed SuperSU by flashing CWM-SuperSU-v.0.87.zip in CWM (which was first temporarily flashed using CWM.zip as an upgrade in the stock recovery)...
Here is the link for both zip files that I used to root:
http://downloadandroidrom.com/file/GalaxyNote/rooting/ICS
That rooted the phone fine while keeping everything stock and everything appears to work great, but now the OTA is failing...
So I'm running, thus rooted, stock 4.0.3 ICS and tried updating to 4.0.4 via OTA. Any ideas how to fix the failing OTA update without flashing a clean stock ROM via ODIN?
voxano said:
Well, I installed SuperSU by flashing CWM-SuperSU-v.0.87.zip in CWM (which was first temporarily flashed using CWM.zip as an upgrade in the stock recovery)...
That rooted the phone fine while keeping everything stock and everything appears to work great, but now the OTA is failing...
So I'm running, thus rooted, stock 4.0.3 ICS and tried updating to 4.0.4 via OTA. Any ideas how to fix the failing OTA update without flashing a clean stock ROM via ODIN?
Click to expand...
Click to collapse
Unroot your phone using Busybox Uninstaller (If you have installed busybox from Dr.Ketan thread only) from Dr.Ketan Thread. And Try Again.
Thanks for the suggestion, but the rooting zip that I mentioned didn't come from the Dr's thread, so his unrooting zip won't help here...
I updated my post above with the link to the zip file that I used for the rooting.
Looks like installing SuperSU this way did something to the /system that causes the OTA to fail... Any ideas on how to work around this?
open super SU - setting - Full unroot
Thanks, but I already tried that: SuperSU uninstalls, but OTA still fails at apparently the same place. I installed it back from the market and tried the full unroot again, with the same result... Any other ideas?
Before rooting, all the previous OTA updates worked flawlessly.
Did you flash a custom kernel, e.g. franco (as also in the webpage)? It may be the issue.
I also tried to unroot using the Voodoo OTA RootKeeper, but that didn't help me either.
If you can download 550MB data, then just flash using PC odin.
kopitalk said:
Did you flash a custom kernel, e.g. franco (as also in the webpage)? It may be the issue.
Click to expand...
Click to collapse
No. Only stock kernels, regularly updated OTA
dr.ketan said:
If you can download 550MB data, then just flash using PC odin.
Click to expand...
Click to collapse
Yeah, looks like I will have to...
I just thought that installing only the SuperSU was such a minimalistic way to root and would be easy to unroot since the app itself provides that feature.
The only other thing that was done to this phone was to make Titanium backups of several apps, but I don't see how that could affect anything either.
Anybody else ran into this exact problem?
Easy Unrooting?
dr.ketan, is there a "SUPERSU-Busybox-UNinstaller.zip" corresponding to the SUPERSU-Busybox-Installer.zip from your original thread:
http://forum.xda-developers.com/showthread.php?t=1424997
?
I see a set of attached files at the bottom of this post:
http://forum.xda-developers.com/showpost.php?p=20963730&postcount=3
, but the insides of the SU-Busybox-Installer.zip are not the same as SUPERSU-Busybox-Installer.zip,
so I assume the SU-Uninstaller-signed.zip will not work. Or will it?
Thanks.
You can try the uninstaller. If you look at the script basically it will remove superuser.apk and su binary. Since superuser (by chainsDD) and superSU are using the same apk name (superuser.apk), the effect will be the same. However I'm not sure how to remove busybox other than by flashing stock kernel.
voxano said:
dr.ketan, is there a "SUPERSU-Busybox-UNinstaller.zip" corresponding to the SUPERSU-Busybox-Installer.zip from your original thread:
http://forum.xda-developers.com/showthread.php?t=1424997
?
I see a set of attached files at the bottom of this post:
http://forum.xda-developers.com/showpost.php?p=20963730&postcount=3
, but the insides of the SU-Busybox-Installer.zip are not the same as SUPERSU-Busybox-Installer.zip,
so I assume the SU-Uninstaller-signed.zip will not work. Or will it?
Thanks.
Click to expand...
Click to collapse
This is for SU Busybox installer, not for SuperSU busybox installer.
If you have rooted with same file, you can see attached with that uninstaller, then only it works
May it be work, but chances of leftover there.
Not so easy UNrooting...
kopitalk said:
You can try the uninstaller. If you look at the script basically it will remove superuser.apk and su binary. Since superuser (by chainsDD) and superSU are using the same apk name (superuser.apk), the effect will be the same. However I'm not sure how to remove busybox other than by flashing stock kernel.
Click to expand...
Click to collapse
Thanks for the input, kopitalk. Sounds like flashing stock kernel would be the only certain way to unroot in this case...
---------- Post added at 09:48 AM ---------- Previous post was at 09:47 AM ----------
dr.ketan said:
This is for SU Busybox installer, not for SuperSU busybox installer.
If you have rooted with same file, you can see attached with that uninstaller, then only it works
May it be work, but chances of leftover there.
Click to expand...
Click to collapse
So there is NO "SUPERSU-Busybox-UNinstaller.zip" corresponding to the SUPERSU-Busybox-Installer.zip from your original thread, right?
Moot
http://forum.xda-developers.com/showthread.php?t=1810954
http://forum.xda-developers.com/showthread.php?t=1329360
Related
Hello there,
Last Sunday I updated my SuperUser apk to the latest version and attempted to update the SuperUser binary to 3.0.6 through the SuperUser app. The update process failed, however, and left me without a working binary. The last 2 days I've been trying to get SuperUser back up using all sorts of things, such as flashing a .zip from the SuperUser website, pushing the contents myself, and using both SuperOneClick and FlashTool, but to no avail. I really need SuperUser because of the limited hard disk in the X8.
I was hoping someone knew of another way of fixing this problem.
Also, is restoring the stock ROM (which I'm using anyways) using PCC or SEUS an option to getting my phone fully unrooted so I can reroot it?
Thanks in advance, Thom
Yes, you can restore the stock ROM via SEUS or PCC, you can re-root later.
It happened to me on sunday when i update superuser, i was using gingercruzt... i lost the root access i was not able to restore all my apps with titanium backup! so, i reinstalled gingercruzt. luck!
For me updated su works fine. Just install and update binary.
Sent from my X8 using xda premium
when i updated the binary, i lost the root access too...
is not necessary restore the original rom.
step1:
make a backup
step 2:
just download “su-3.0-bin-efgh-signed” and flash via CWM
step3:
enjoy again
step4:
remeber never again update the [email protected]%& binary
http://goo-inside.me/superuser/
if it doesn't work, try other SU's like 3.0.1-bin
Hello, my firs post but not last . When I was root x8 15 days before, I installed xRecovery and link2sd, and another app. So, after I update superuser to 3.06, I lost root permissions. Now, there is no chance to access to xRecovery menu, with meny times clicking (I never didn't update android 2.1 to another version 2.2 or 2.3....).
Any help?
Does anybody know how to resolve this?? Please...
crepljanin said:
Does anybody know how to resolve this?? Please...
Click to expand...
Click to collapse
sure you can't access the recovery? when i faced the problem, i was able anyway to enter recovery
@Svartehjerte
Thanks for reply.
Yes, I am sure . What you think, whether to again try to root my x8 whit superoneclick?
Have a very weird and frustrating issue with my UK i9305 on EE.
As soon as it's rooted, no matter what SU app I use, it starts to heat up and leak RAM once booted until it runs out of RAM and restarts. And repeat. Until I unroot it and the problem stops. Initially, I thought it was a problem with SuperSU but I've also tried ChainsDD and Koush's Superuser apps with the same result. It looks like something requesting root access is causing a problem but I don't know what. It has said that it's granting root access to "shell" if that's anything to go by?
I resorted to wiping, flashing a newer 4.1.2 stock ROM (BLL5) but I still have the same problem. Can't for the life of me work out what's going on and really don't want to have to wipe again, especially since it seems not to fix the problem anyway.
Any ideas?
What method of root are you using??
Sent from my GT-I9305 using xda premium
Which version of SuperSU are you using? This was an issue in V1.0 for all Galaxy phones, and Chainfire has already released a workaround for this in the latest versions.
I've rooted using both CF Autoroot and mskip's toolkit. Same issue with both.
I'm aware of the issue with SuperSU and I've used subsequent versions of it (and indeed different SU apps) without success.
Interestingly, whatever version of SuperSU I try, the binaries can't be updated. I'm wondering if a previous unroot has left me with some relic of SuperSU that is causing me problems.
dave_uk said:
I've rooted using both CF Autoroot and mskip's toolkit. Same issue with both.
I'm aware of the issue with SuperSU and I've used subsequent versions of it (and indeed different SU apps) without success.
Interestingly, whatever version of SuperSU I try, the binaries can't be updated. I'm wondering if a previous unroot has left me with some relic of SuperSU that is causing me problems.
Click to expand...
Click to collapse
What about an Odin flash with stock firmware than try and root or flash a pre-rooted stock firmware?
Thanks
I did Odin flash the firmware I currently have but once I rooted, had the same problem.
dave_uk said:
I did Odin flash the firmware I currently have but once I rooted, had the same problem.
Click to expand...
Click to collapse
Use Odin v3.0x and flash Stock pre-rooted ROM from here http://forum.xda-developers.com/showthread.php?p=32929446
Sent from my GT-I9305 using xda app-developers app
Have you tried rooting without restoring the apps?
Snowstormzzz said:
Have you tried rooting without restoring the apps?
Click to expand...
Click to collapse
Thats what I thought reading his problem, never heard of "Shell" asking for SU-Rights
Dear All,
I manage to unlock my bootloader, but enter into recovery,
I also used management to installed Super SU, on internal memory,
While doing the rooting, I using TWRP Recovery method I installed Successfully Super SU, but when I reboot my phone and check for super SU which is not visible on my home screen, and using root cheker when I check with application its showing no root access.
Please help
Thanks
Vivek
vievk said:
Dear All,
I manage to unlock my bootloader, but enter into recovery,
I also used management to installed Super SU, on internal memory,
While doing the rooting, I using TWRP Recovery method I installed Successfully Super SU, but when I reboot my phone and check for super SU which is not visible on my home screen, and using root cheker when I check with application its showing no root access.
Please help
Thanks
Vivek
Click to expand...
Click to collapse
I have the exact same problem. I hope some people here can help.
Aaberg said:
I have the exact same problem. I hope some people here can help.
Click to expand...
Click to collapse
you need an unsecured kernel. if you're still on stock ROM, that kernel has write protection enabled, and system changes won't survive a reboot.
nkk71 said:
you need an unsecured kernel. if you're still on stock ROM, that kernel has write protection enabled, and system changes won't survive a reboot.
Click to expand...
Click to collapse
I'm completely stock besides the unlocked bootloader and recovery. Do you have a kernel that you can recommend?
nkk71 said:
you need an unsecured kernel. if you're still on stock ROM, that kernel has write protection enabled, and system changes won't survive a reboot.
Click to expand...
Click to collapse
Hey Nkk71
That's strange, my device rooted with superSU completely stock and survives a reboot. Titanium backup and other still obtain root and root checker shows rooted.
Just curious
mb_guy said:
Hey Nkk71
That's strange, my device rooted with superSU completely stock and survives a reboot. Titanium backup and other still obtain root and root checker shows rooted.
Just curious
Click to expand...
Click to collapse
I used the method shown in the video. I'm on an unlocked European HTC One, if that helps.
mb_guy said:
Hey Nkk71
That's strange, my device rooted with superSU completely stock and survives a reboot. Titanium backup and other still obtain root and root checker shows rooted.
Just curious
Click to expand...
Click to collapse
I stand corrected then
Can you just explain to the OP how you installed it... I'm on custom ROM so dont have these issues and i'm using superuser not superSU.
and where is the superuser.apk? i'm assuming in your case it would be under /data/app as opposed to /system/app, is that correct?
---------- Post added at 11:41 AM ---------- Previous post was at 11:38 AM ----------
Aaberg said:
I used the method shown in the video. I'm on an unlocked European HTC One, if that helps.
Click to expand...
Click to collapse
Don't know what video you're referring to, but try flashing the zip from this thread: http://forum.xda-developers.com/showthread.php?t=1538053
This flashable zip: http://download.chainfire.eu/supersu in custom recovery.
nkk71 said:
I stand corrected then
Can you just explain to the OP how you installed it... I'm on custom ROM so dont have these issues and i'm using superuser not superSU.
and where is the superuser.apk? i'm assuming in your case it would be under /data/app as opposed to /system/app, is that correct?
---------- Post added at 11:41 AM ---------- Previous post was at 11:38 AM ----------
Don't know what video you're referring to, but try flashing the zip from this thread: http://forum.xda-developers.com/showthread.php?t=1538053
This flashable zip: http://download.chainfire.eu/supersu in custom recovery.
Click to expand...
Click to collapse
I don't now what video either. You are right I flashed 1.93 from TWRP, didn't move the app to system. Perhaps that's why it survives.
Well i flashed some lollipop roms & i have a huge prob...I've lost root access for most apps.SuperSu app show them as greanted & actually no Su access..Any solution please..Well now im on latest official lollipop update...
also i got this " erofs (read-only file system)" when i tried to modify system file.
crazykas said:
Well i flashed some lollipop roms & i have a huge prob...I've lost root access for most apps.SuperSu app show them as greanted & actually no Su access..Any solution please..Well now im on latest official lollipop update...
also i got this " erofs (read-only file system)" when i tried to modify system file.
Click to expand...
Click to collapse
Which rom exactly? There are currently a total of 3 including the RUU. On the Superuser app check if there's a update for the binary.
luigi311 said:
Which rom exactly? There are currently a total of 3 including the RUU. On the Superuser app check if there's a update for the binary.
Click to expand...
Click to collapse
RUU in this thread http://forum.xda-developers.com/sprint-htc-one/general/sprint-htc-one-android-5-0-coming-soon-t3001541.
Thanks i'll check that out
Is there a root method for lollipop yet? S-OFF, unlocked, and TWRP installed, just waiting for a method to root and disable write protection.
Robert542 said:
Is there a root method for lollipop yet? S-OFF, unlocked, and TWRP installed, just waiting for a method to root and disable write protection.
Click to expand...
Click to collapse
Does TWRP ask you to install SuperSU when you try to exit it? I haven't tried on Lollipop yet, but I know when I've been running stock unrooted in the past, TWRP would prompt me to root when I restarted to system.
coal686 said:
Does TWRP ask you to install SuperSU when you try to exit it? I haven't tried on Lollipop yet, but I know when I've been running stock unrooted in the past, TWRP would prompt me to root when I restarted to system.
Click to expand...
Click to collapse
This method seems to work just fine for me. After installing supersu in TWRP then opened supersu selected TWRP and it downloaded the latest binaries and flashed in TWRP and worked fine after reboot.
I RUU'ed today to the newest Sprint M7 version. After downloading TWRP Manager got message that TWRP needs root permissions. Downloaded WinDroid, used it to flash TWRP. then used it to gain root access. WinDroid did not work for me on Windows 10 Tech Preview. Went to other hard drive with Win 7, and worked great. The thing I have noticed is that Root App Delete will not uninstall the Sprint bloat, or the Google crap (movies, TV, books, etc).
coal686 said:
Does TWRP ask you to install SuperSU when you try to exit it? I haven't tried on Lollipop yet, but I know when I've been running stock unrooted in the past, TWRP would prompt me to root when I restarted to system.
Click to expand...
Click to collapse
Unfortunately it does not. I even tried Philz to see if it would root and it's still a no go. Philz said I was rooted and just needed to download superuser from the play store. I downloaded super user and it says I need to root my phone.
---------- Post added at 08:16 AM ---------- Previous post was at 08:13 AM ----------
retiredtrebor said:
I RUU'ed today to the newest Sprint M7 version. After downloading TWRP Manager got message that TWRP needs root permissions. Downloaded WinDroid, used it to flash TWRP. then used it to gain root access. WinDroid did not work for me on Windows 10 Tech Preview. Went to other hard drive with Win 7, and worked great. The thing I have noticed is that Root App Delete will not uninstall the Sprint bloat, or the Google crap (movies, TV, books, etc).
Click to expand...
Click to collapse
Write protection needs to be disabled.
Robert542 said:
Unfortunately it does not. I even tried Philz to see if it would root and it's still a no go. Philz said I was rooted and just needed to download superuser from the play store. I downloaded super user and it says I need to root my phone.
---------- Post added at 08:16 AM ---------- Previous post was at 08:13 AM ----------
Write protection needs to be disabled.
Click to expand...
Click to collapse
And how does one go about disabling write protection?
retiredtrebor said:
And how does one go about disabling write protection?
Click to expand...
Click to collapse
From my understanding, that has to be done by a ROM and/or kernel developer.
Kingroot worked ,it rooted my Xperia ZR ,but the problem occurred when i tried to unroot my phone with the app ,it showed that it was unrooting ,old version so circle was spinning then it automatically closed the app ,but didnt uninstalled itself ,since i had read to reboot after unrooting i tried , but the app was there and suddenly after opening the app it was showing me my phone is rooted ,i tried several times to unroot but of no use but after checking wid root checker it showed my phone is not rooted but now that i want to root i have no option app shows rooted but not working its of latest version. Please i would praise each of u to find me a safe solution to root my phone again pleae guys im in middle of nowhere please .It can also b with the help of PC . Please
Try replacing Kingroot with SuperSU first with this method http://zidroid.com/how-to-get-ride-and-replace-kinguser-with-supersu-app/
Then unroot using SuperSU.
It might work. I have done the first part but not the second.
Ugh.. King root sucks.. Horrible app and don't give full root..
Sent from my Xperia ZR using Tapatalk
hagar006 said:
Ugh.. King root sucks.. Horrible app and don't give full root..
Sent from my Xperia ZR using Tapatalk
Click to expand...
Click to collapse
Could you explain further please, particularly the 'don't give full root' part? I have used it and then immediately switched to SuperSU as explained in the link posted above by me but I have not yet come across any shortcomings.
So what's your problem now?
Sent from my Xperia ZR using Tapatalk
---------- Post added at 02:00 PM ---------- Previous post was at 01:57 PM ----------
sling-shot said:
Could you explain further please, particularly the 'don't give full root' part? I have used it and then immediately switched to SuperSU as explained in the link posted above by me but I have not yet come across any shortcomings.
Click to expand...
Click to collapse
I'm so sorry..Hehe the post was meant for the author of this thread.. My sincere apologies..
Sent from my Xperia ZR using Tapatalk
---------- Post added at 02:04 PM ---------- Previous post was at 02:00 PM ----------
King root by itself is Crap.. Lucky someone made an app to make king root work..
Sent from my Xperia ZR using Tapatalk
sling-shot said:
Could you explain further please, particularly the 'don't give full root' part? I have used it and then immediately switched to SuperSU as explained in the link posted above by me but I have not yet come across any shortcomings.
Click to expand...
Click to collapse
After rooting with king root, if you reboot, then the root is gone. By normal methods, this should not happen, thats why the its often not encouraged.
ariftwister said:
After rooting with king root, if you reboot, then the root is gone. By normal methods, this should not happen, thats why the its often not encouraged.
Click to expand...
Click to collapse
OK. That might have been true. But I did not wait to find out.
Off topic :
Now however I have a problem. Even with the XZDualRecovery installed I am not getting full read write access to system partition. Any ideas? I am on stock ROM.
I will post this in the Ask Anything thread.
sling-shot said:
OK. That might have been true. But I did not wait to find out.
Off topic :
Now however I have a problem. Even with the XZDualRecovery installed I am not getting full read write access to system partition. Any ideas? I am on stock ROM.
I will post this in the Ask Anything thread.
Click to expand...
Click to collapse
So you did it by king root right? I think it may not have given you full root.
ariftwister said:
So you did it by king root right? I think it may not have given you full root.
Click to expand...
Click to collapse
I had created pre-rooted FTF strictly according to the instructions given. But that did not give me root. Why? Was the use of Philz Touch to flash the probable reason?
I am dreading going through the whole process again!
Is there a way to see if I have full root or not? Because Root Checker says I have root. Other super user activities run properly. Link2SD is able to integrate updates of system apps to /system successfully. If there is no read/write access to /system, then how is Link2SD able to do that?
Only in a file manager I am not able to modify /system files.
And funny thing is sometime back, I did have ability to modify /system. Don't know how I got it, don't know how I lost it.
sling-shot said:
I had created pre-rooted FTF strictly according to the instructions given. But that did not give me root. Why? Was the use of Philz Touch to flash the probable reason?
I am dreading going through the whole process again!
Is there a way to see if I have full root or not? Because Root Checker says I have root. Other super user activities run properly. Link2SD is able to integrate updates of system apps to /system successfully. If there is no read/write access to /system, then how is Link2SD able to do that?
Only in a file manager I am not able to modify /system files.
And funny thing is sometime back, I did have ability to modify /system. Don't know how I got it, don't know how I lost it.
Click to expand...
Click to collapse
I'm not king root user, but generally your file manager needs you to grant it root access
btw, just use supersu
cipetonk said:
I'm not king root user, but generally your file manager needs you to grant it root access
btw, just use supersu
Click to expand...
Click to collapse
At present I am using SuperSU. My file manager has super user permission.
sling-shot said:
I had created pre-rooted FTF strictly according to the instructions given. But that did not give me root. Why? Was the use of Philz Touch to flash the probable reason?
I am dreading going through the whole process again!
Is there a way to see if I have full root or not? Because Root Checker says I have root. Other super user activities run properly. Link2SD is able to integrate updates of system apps to /system successfully. If there is no read/write access to /system, then how is Link2SD able to do that?
Only in a file manager I am not able to modify /system files.
And funny thing is sometime back, I did have ability to modify /system. Don't know how I got it, don't know how I lost it.
Click to expand...
Click to collapse
You see KingRoot is the culprit here, I have gone through some threads, which also confirms that king root turns your system, write protected. Also not all apps need write access to system thats why other root apps works properly for you. Regarding Link2SD, they make symlinks to /system so not exactly writing to system.
I suggest you do a clean root by flashing by the correct method.
ariftwister said:
You see KingRoot is the culprit here, I have gone through some threads, which also confirms that king root turns your system, write protected. Also not all apps need write access to system thats why other root apps works properly for you. Regarding Link2SD, they make symlinks to /system so not exactly writing to system.
I suggest you do a clean root by flashing by the correct method.
Click to expand...
Click to collapse
I will try that again. Thanks.
sling-shot said:
I will try that again. Thanks.
Click to expand...
Click to collapse
http://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
Official Thread of KingRoot. It also has links on how to successfully migrate to SuperSU. Hope It helps.
ariftwister said:
http://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
Official Thread of KingRoot. It also has links on how to successfully migrate to SuperSU. Hope It helps.
Click to expand...
Click to collapse
I will go through it. May be the method I followed to get SuperSU was wrong.
ariftwister said:
You see KingRoot is the culprit here, I have gone through some threads, which also confirms that king root turns your system, write protected. Also not all apps need write access to system thats why other root apps works properly for you. Regarding Link2SD, they make symlinks to /system so not exactly writing to system.
I suggest you do a clean root by flashing by the correct method.
Click to expand...
Click to collapse
I do not understand what is going on here. I have flashed and lost root now.
In the previous version of Pre-Rooted Zip (which I had used) I had also included RICDefeat.zip. As all documents suggest that with XZDualRecovery it is not needed, this time I recreated a Pre-Rooted Zip from scratch using PRFCreator v1.1 (the latest available) with only the original FTF created using Flashtool, SuperSU 2.46.zip and XZDualRecovery 2.8.21.zip. PRFCreator worked seemingly without error and I got a nice final ZIP.
Then I booted into TWRP, flashed this ZIP. Everything seemed to go fine except I had an error at the end which said "unable to mount /system" (this was after SuperSU and XZDualRecovery were successfully flashed.)
On rebooting I find that I no longer have root. Does this mean that I cannot flash the firmware again?
.
sling-shot said:
I do not understand what is going on here. I have flashed and lost root now.
In the previous version of Pre-Rooted Zip (which I had used) I had also included RICDefeat.zip. As all documents suggest that with XZDualRecovery it is not needed, this time I recreated a Pre-Rooted Zip from scratch using PRFCreator v1.1 (the latest available) with only the original FTF created using Flashtool, SuperSU 2.46.zip and XZDualRecovery 2.8.21.zip. PRFCreator worked seemingly without error and I got a nice final ZIP.
Then I booted into TWRP, flashed this ZIP. Everything seemed to go fine except I had an error at the end which said "unable to mount /system" (this was after SuperSU and XZDualRecovery were successfully flashed.)
On rebooting I find that I no longer have root. Does this mean that I cannot flash the firmware again?
.
Click to expand...
Click to collapse
I'm sorry, but what are you trying to achieve here? I don't get it.
ariftwister said:
I'm sorry, but what are you trying to achieve here? I don't get it.
Click to expand...
Click to collapse
Full root with read write access to /system in stock firmware.
Flash Stock FTF thru Flashtool, Flash any custom kernel with recovery, flash SuperSu Zip via that recovery, now flash stock kernel then reboot. Done.
ariftwister said:
Flash Stock FTF thru Flashtool, Flash any custom kernel with recovery, flash SuperSu Zip via that recovery, now flash stock kernel then reboot. Done.
Click to expand...
Click to collapse
Apologies if I am testing your patience. Please tell me if so.
How about flashing an older kernel, rooting it using Towelroot, install recovery, flash SuperSU, flash current kernel?
I have not unlocked bootloader yet.