Wondering when xda will have section for s2???? Also hoping a dev can come up with a root method. I can test as I have a sm-t810.
suzook said:
Wondering when xda will have section for s2???? Also hoping a dev can come up with a root method. I can test as I have a sm-t810.
Click to expand...
Click to collapse
Get in line behind the tab a.
OK have you tried the kingroot exploit in this section first?
http://forum.xda-developers.com/showthread.php?t=3158198
ashyx said:
Get in line behind the tab a.
OK have you tried the kingroot exploit in this section first?
http://forum.xda-developers.com/showthread.php?t=3158198
Click to expand...
Click to collapse
King root does not work. Thanks
suzook said:
King root does not work. Thanks
Click to expand...
Click to collapse
Usually takes a few goes, have you tried previous versions?
ashyx said:
Usually takes a few goes, have you tried previous versions?
Click to expand...
Click to collapse
Tried about 50 times, different versions..? No go....I don't care about knox. Was hoping for a cfroot method.
suzook said:
Tried about 50 times, different versions..? No go....I don't care about knox. Was hoping for a cfroot method.
Click to expand...
Click to collapse
Watch this space
ashyx said:
Watch this space
Click to expand...
Click to collapse
I'm watching!
suzook said:
I'm watching!
Click to expand...
Click to collapse
Test 1.
please be as specific as possible if it fails, screenshots or vids are best.
smt810_cf-autoroot_v1
sm-t810_stock_recovery
ashyx said:
Test 1.
please be as specific as possible if it fails, screenshots or vids are best.
smt810_cf-autoroot_v1
sm-t810_stock_recovery
Click to expand...
Click to collapse
I flashed 1st file, all went well, but when i install supersu app, it says it needs to update binaries, but it fails
suzook said:
I flashed 1st file, all went well, but when i install supersu app, it says it needs to update binaries, but it fails
Click to expand...
Click to collapse
looks like the superuser app in system app doesnt have correc permisions???
suzook said:
looks like the superuser app in system app doesnt have correc permisions???
Click to expand...
Click to collapse
Shouldn't need to install the superuser app. It should already be installed.
Root again and watch the process. Particularly watch to see if the system and cache partition successfully mount or fail.
This is why I need screen shots and vids.
ashyx said:
Shouldn't need to install the superuser app. It should already be installed.
Root again and watch the process. Particularly watch to see if the system and cache partition successfully mount or fail.
This is why I need screen shots and vids.
Click to expand...
Click to collapse
OK, i will try again with pics.....they do mount, but the superuser app in /sytem/app doesnt have proper permisions...that make sense?
Here it is
suzook said:
OK, i will try again with pics.....they do mount, but the superuser app in /sytem/app doesnt have proper permisions...that make sense?
Click to expand...
Click to collapse
Can you post a screen shot of root validator so I can see what got installed.
If the partitions mount as you say then there may be a problem with the supersu script.
You should not have to install any superuser app or update the binary as the exploit uses the latest binaries.
I will be turning in for tonight so if you can get the screen shots of the process where it mounts the partitions and where it installs the supersu files and a screen shot from root validator that will give me something to look at tomorrow.
---------- Post added at 12:37 AM ---------- Previous post was at 12:35 AM ----------
suzook said:
Here it is
Click to expand...
Click to collapse
Ok the supersu script didn't run. I will fix that tomorrow.
Good night.
ashyx said:
Can you post a screen shot of root validator so I can see what got installed.
If the partitions mount as you say then there may be a problem with the supersu script.
You should not have to install any superuser app or update the binary as the exploit uses the latest binaries.
I will be turning in for tonight so if you can get the screen shots of the process where it mounts the partitions and where it installs the supersu files and a screen shot from root validator that will give me something to look at tomorrow.
---------- Post added at 12:37 AM ---------- Previous post was at 12:35 AM ----------
Ok the supersu script didn't run. I will fix that tomorrow.
Good night.
Click to expand...
Click to collapse
Great, thanks. Have a great night.
Hi. Any autoroot for SM-T715Y? Thank you.
looking Root for SM-T710 8"
ashyx said:
Watch this space
Click to expand...
Click to collapse
Hello Ashyx,
I am looking for auto Root for SM-T710 as well....
i am checking XDA almost everyday to see if they opened section for Tab S2...
Maybe you are the 1st hero that can make the S2 rooted....
thanks
If and when I get root working for the sm-t810 I will look at root for you guys.
suzook said:
Great, thanks. Have a great night.
Click to expand...
Click to collapse
Test 2.
Watch for the supersu script running in the process. You should see the supersu installer script run after the partitions get mounted.
smt810_cf-autoroot_v2
Check with root validator for root.
ashyx said:
Test 2.
Watch for the supersu script running in the process. You should see the supersu installer script run after the partitions get mounted.
smt810_cf-autoroot_v2
Check with root validator for root.
Click to expand...
Click to collapse
nope, same as build 1. no superuser app, script does not run. Will be away from a computer in a half hour till later on today, won't be able to test for about 11 hrs from now. Thanks, I'm sure we(you) will get it.
Related
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.
My Note 3 SM-N900A was previously rooted with towelroot and after a few days, I decided to unroot via SuperSU. And it was a success, but everytime I reboot, i see a "unlock lock" below the "Samsung Galaxy Note 3" title. How can i get rid of this issue? Does this mean that I'm not yet fully stocked? I'm a noob so please bare with me
I believe you have to factory reset.
440bro said:
I believe you have to factory reset.
Click to expand...
Click to collapse
I already did a factory reset. But same result.
I think this is what I did to fix it.
http://forum.xda-developers.com/showthread.php?t=2502550
Edit: Or you can install Xposed Framework and then Wanam Xposed, there is an option to remove padlock.
RashAPu said:
I think this is what I did to fix it.
http://forum.xda-developers.com/showthread.php?t=2502550
Edit: Or you can install Xposed Framework and then Wanam Xposed, there is an option to remove padlock.
Click to expand...
Click to collapse
The link you provided is to change boot animation and the custom padlock happens before that.
Xposed framework and wanam require root access. The o.p. has unrooted therefore they won't work.
---------- Post added at 11:38 AM ---------- Previous post was at 11:35 AM ----------
@callmetwst are any apps that had root access still installed? When you had root access did you modify any system properties?
callmetwst said:
My Note 3 SM-N900A was previously rooted with towelroot and after a few days, I decided to unroot via SuperSU. And it was a success, but everytime I reboot, i see a "unlock lock" below the "Samsung Galaxy Note 3" title. How can i get rid of this issue? Does this mean that I'm not yet fully stocked? I'm a noob so please bare with me
Click to expand...
Click to collapse
Its not much of a problem, but install xposed installer from the internet, then download wanam xposed within the app/play store. Restart phone after activating the module on from installer. Go to security hacks and click "Fake System Status". Restart phone. Voila! You won't see that problem any time soon after that.
Sent from my SAMSUNG-SM-N900A using XDA Free mobile app
YoungDev said:
Its not much of a problem, but install xposed installer from the internet, then download wanam xposed within the app/play store. Restart phone after activating the module on from installer. Go to security hacks and click "Fake System Status". Restart phone. Voila! You won't see that problem any time soon after that.
Sent from my SAMSUNG-SM-N900A using XDA Free mobile app
Click to expand...
Click to collapse
Please re-read the original post.
callmetwst said:
I already did a factory reset. But same result.
Click to expand...
Click to collapse
Follow these instructions ..... http://forum.xda-developers.com/showthread.php?t=2703006
440bro said:
The link you provided is to change boot animation and the custom padlock happens before that.
Xposed framework and wanam require root access. The o.p. has unrooted therefore they won't work.
---------- Post added at 11:38 AM ---------- Previous post was at 11:35 AM ----------
@callmetwst are any apps that had root access still installed? When you had root access did you modify any system properties?
Click to expand...
Click to collapse
Thank you all for your replies gentlemen. Nope I dont think I still have root apps because I already factory reset it for 2 times already. Im afraid i didnt modify any system properties.
callmetwst said:
Thank you all for your replies gentlemen. Nope I dont think I still have root apps because I already factory reset it for 2 times already. Im afraid i didnt modify any system properties.
Click to expand...
Click to collapse
Step 6: Navigate to System -> xbin and delete Busybox
http://forum.xda-developers.com/showthread.php?t=2296014
Worked on my Note 3.
Use Triangle Away from the Play Store. It'll reset the system status to official.
EDIT: never mind, I didn't see that you had unrooted. You could always re-root, then us a root file explorer to erase everything in system/xbin.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
This is driving me nuts... I was on 5.1.1 and I am trying to get it rooted.
I'm following a guide which goes like this..
1. downgrade to kitkat 4.4 using flashtool
2. root 4.4
3. Install custom recovery
4. Flash 5.1.1 pre-rooted zip
I have had problem after problem and I think something may have screwed up along the way.
I finally managed to get kitkat installed using flashtool and a generic C6903 .108 ftf.
Problem 1... I used 'Easy Root tool' from xda to root kitkat... but it seemed to hang at the cleaning up' stage - is this a problem?
Problem 2... every time I restart my phone - kitkat asks what language etc. Whats that all about?
PROBLEM 3. The guide Im following says to install busybox after rooting kitkat.
I've tried 2 different busybox installers and both of them fail when trying to install bb.
QUESTION: Are these 3 problems linked and will it prevent me from continuing with the guide I am trying to follow??? i.e. do I need busybox to install XZ Dual Recovery and therefore a pre-rooted zip?
Root Checker basic says kitkat is rooted, as does the first busybox installer.
I'm taking a short break from this nightmare, so in the meentime if any of you chaps could advise me on whether or not its ok to continue or if I have fecked up the whole process, that would be great.
Thanks in advance
problem 1 : re run the installer again, don't use administrator mode
problem2 : use any simcard on your phone
others, sorry i have no idea, you could download busybox from playstore ?
I would just start over and try a different root program. busybox is failing to install because the root didn't work.
Gamer4Life said:
problem 1 : re run the installer again, don't use administrator mode
problem2 : use any simcard on your phone
others, sorry i have no idea, you could download busybox from playstore ?
Click to expand...
Click to collapse
Problem1... thank you, I'll try again
Problem2... Thanks. I thought It could be the lack of a SIM card and then I thought no! that can't be it lol... as usual - I was wrong ha
others... yeah mate, tried 2 different installers from play store - no joy with either.
Thanks for your help
xasbo said:
I would just start over and try a different root program. busybox is failing to install because the root didn't work.
Click to expand...
Click to collapse
Cheers bud, I'll try 'easy root tool' once more without admin priv, if its the same story I'll start over and try a different root tool. Any suggestions on that?
Also: how come root checker says I'm all good and rooted but busybox wont install? even one of the busybox installers says "Your device is rooted"!?!?
Thanks for all the help mate
i think you don't have supersu installed, and busy box couldn't get root rights
so download supersu from playstore, open it and update binaries as normal, then reboot
and you would be able to install bb
thesweeney80 said:
Cheers bud, I'll try 'easy root tool' once more without admin priv, if its the same story I'll start over and try a different root tool. Any suggestions on that?
Also: how come root checker says I'm all good and rooted but busybox wont install? even one of the busybox installers says "Your device is rooted"!?!?
Thanks for all the help mate
Click to expand...
Click to collapse
Try the suggestion made by @Gamer4Life, just in case you somehow got root but it failed to install the APK needed to manage it. Might save you some work. That would explain why everything thinks you're rooted.
As for an alternative, if you still need it, I think I used kingroot successfully on 4.4.4.
Gamer4Life said:
i think you don't have supersu installed, and busy box couldn't get root rights
so download supersu from playstore, open it and update binaries as normal, then reboot
and you would be able to install bb
Click to expand...
Click to collapse
thanks for the tip mate but no joy see my reply to xasbo, cheers
xasbo said:
Try the suggestion made by @Gamer4Life, just in case you somehow got root but it failed to install the APK needed to manage it. Might save you some work. That would explain why everything thinks you're rooted.
As for an alternative, if you still need it, I think I used kingroot successfully on 4.4.4.
Click to expand...
Click to collapse
Thanks mate. I was hoping Gamer4life might be right as there was no Supersu installed.
I installed supersu from play store no problem... but when I try to update binaries it says' update failed. Please reboot and try again.'. tried reboot but same story.
I guess I'll try 'easy root tool' again and then will give kingroot a bash if needbe.
One last pre-emptive question...
If I root kitkat using kingroot... should I replace kinguser with supersu before proceeding with XZDR and a pre-rooted zip or will kinguser be sufficient to continue.
Many thanks to you and everyone else who has tried to help me with this clusterf*ck,.. I appreciate it
can you screenshot the error you got ?
i reread your op, you don't need busybox to install dual recovery, it installs like the easy root installer, very easy
just one click and you are ready to go
also xzdualrecovery will root your device and install supersu by default if you have kitkat, so you can skip that.
edit (i don't think this will work because towelroot doesn't work on z1 4.4.4 108)
Gamer4Life said:
can you screenshot the error you got ?
i reread your op, you don't need busybox to install dual recovery, it installs like the easy root installer, very easy
just one click and you are ready to go
also xzdualrecovery will root your device and install supersu by default if you have kitkat, so you can skip that.
edit (i don't think this will work because towelroot doesn't work on z1 4.4.4 108)
Click to expand...
Click to collapse
must have been a glitch in the matrix mate becuase its now working (Possibly thanks to your suggestion of installing Supersu?).
I reconnected to PC in order to give 'easy root tool' another crack at it.
As soon as I start install.bat It says checking if device is rooted AND I get a superuser request on my phone for adb.shell - Happy days!
I granted root access to adb shell and the root tool says Job Done. Root success etc.
So I disconnect and try to update su binaries and it worked first go!!!
*Touch wood* I think I'm now past the tricky part and it should be plain sailing from here on in. lol
THANKS for the help Gamer4Life, and everyone else who has chipped in.... hopefully my next post will be to report a fully rooted 5.1.1 :fingers-crossed:
Gamer4Life said:
also xzdualrecovery will root your device and install supersu by default if you have kitkat, so you can skip that.
edit (i don't think this will work because towelroot doesn't work on z1 4.4.4 108)
Click to expand...
Click to collapse
Correct, TowelRoot doesn't work for this version.
---------- Post added at 01:27 PM ---------- Previous post was at 01:26 PM ----------
thesweeney80 said:
THANKS for the help Gamer4Life, and everyone else who has chipped in.... hopefully my next post will be to report a fully rooted 5.1.1 :fingers-crossed:
Click to expand...
Click to collapse
:good: godspeed
@thesweeney80 you are welcome have fun
xasbo said:
:good: godspeed
Click to expand...
Click to collapse
Gamer4Life said:
@thesweeney80 you are welcome have fun
Click to expand...
Click to collapse
you fellas are the muts nuts.
All done, everything went smoothly once I got kitkat rooted properly.
MANY thanks for all your help.
Honestly I wouldnt even bother owning a smartphone if it wasnt for the peeps on XDA... F*cking awesome. THANKS :good: :highfive:
:good: awesome! don't forget to pay it forward sometime.
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.
Hi!
So, today, I took a look at the zips provided by Lordbannakaffalatta, in his thread. http://forum.xda-developers.com/p8lite/general/mega-thread-root-unbricking-updating-t3400994
I changed the update binaries of the zips, changed the lines "SYSTEMLESS=false" to "SYSTEMLESS=true", and "BINDSYSTEMXBIN=true" to "BINDSYSTEMXBIN=false", and it means that now It'd install itself as systemless root. I'd like to see if anyone could test it, because I don't have my device yet. Thanks for help!:fingers-crossed:
Instructions:
Put 1sysless.zip and 2sysless.zip into your sd card/internal storage.
Boot into TWRP.
Ignore the message from TWRP.
Choose the "install" button.
Locate 1sysless.zip (if on sd card go "up a level" and then "external sdcard" there you should find it).
Install it.
Reboot your phone.
Boot into TWRP again.
Locate 2sysless.zip .
Install it.
Reboot
Downloads : Zip 1:https://mega.nz/#!bVAinYjB
Zip 2 : https://mega.nz/#!rRpnyBAb
Credits goes to Lordbannakaffalatta because he provided the original zips!
Can anyone tell me what is the benefit of systemless root apart from being able to use certain apps which do not run on rooted devices?
---------- Post added at 04:26 PM ---------- Previous post was at 04:25 PM ----------
Szabi01 said:
Hi!
So, today, I took a look at the zips provided by Lordbannakaffalatta, in his thread. http://forum.xda-developers.com/p8lite/general/mega-thread-root-unbricking-updating-t3400994
I changed the update binaries of the zips, changed the lines "SYSTEMLESS=false" to "SYSTEMLESS=true", and "BINDSYSTEMXBIN=true" to "BINDSYSTEMXBIN=false", and it means that now It'd install itself as systemless root. I'd like to see if anyone could test it, because I don't have my device yet. Thanks for help!:fingers-crossed:
Instructions:
Put 1sysless.zip and 2sysless.zip into your sd card/internal storage.
Boot into TWRP.
Ignore the message from TWRP.
Choose the "install" button.
Locate 1sysless.zip (if on sd card go "up a level" and then "external sdcard" there you should find it).
Install it.
Reboot your phone.
Boot into TWRP again.
Locate 2sysless.zip .
Install it.
Reboot
Downloads : Zip 1:https://mega.nz/#!bVAinYjB
Zip 2 : https://mega.nz/#!rRpnyBAb
Credits goes to Lordbannakaffalatta because he provided the original zips!
Click to expand...
Click to collapse
Move this thread to p8lite general.
Suleiman01 said:
Can anyone tell me what is the benefit of systemless root apart from being able to use certain apps which do not run on rooted devices?
---------- Post added at 04:26 PM ---------- Previous post was at 04:25 PM ----------
Move this thread to p8lite general.
Click to expand...
Click to collapse
That's exactly! So, you can use Android Pay, and, in my case, Pokemon Go...
I'd gladly move it, if you could tell me how to do it! Sry, first thread... :/
Szabi01 said:
That's exactly! So, you can use Android Pay, and, in my case, Pokemon Go...
I'd gladly move it, if you could tell me how to do it! Sry, first thread... :/
Click to expand...
Click to collapse
Well only a moderator can do it. I didn't know that in the first place.
---------- Post added at 04:53 PM ---------- Previous post was at 04:47 PM ----------
@Heisenberg Can you move this thread to correct category? Thanks in advance.
Suleiman01 said:
Well only a moderator can do it. I didn't know that in the first place.
---------- Post added at 04:53 PM ---------- Previous post was at 04:47 PM ----------
@Heisenberg Can you move this thread to correct category? Thanks in advance.
Click to expand...
Click to collapse
Then sorry, I just posted it here because i need answers from testers :3
I tested it. It seems to work fine even though it was troubling in the beginning. Pokemon Go works fine just as all other non root apps such as banking or others. I mean I had this working before but I did it just to check this one out. Thanks Bro
PCSE said:
I tested it. It seems to work fine even though it was troubling in the beginning. Pokemon Go works fine just as all other non root apps such as banking or others. I mean I had this working before but I did it just to check this one out. Thanks Bro
Click to expand...
Click to collapse
So, it works with the newest version of PoGo?:000
Thanks for testing!!
Is there something that we should be aware of, after installing these files?
spirto82 said:
Is there something that we should be aware of, after installing these files?
Click to expand...
Click to collapse
I changed those lines only, I left the rest of the zips unmodified.
Szabi01 said:
So, it works with the newest version of PoGo?:000
Thanks for testing!!
Click to expand...
Click to collapse
Well I dont know which version it was. It was an .apk that I had lying around for like 8-10 Days or so.
PCSE said:
Well I dont know which version it was. It was an .apk that I had lying around for like 8-10 Days or so.
Click to expand...
Click to collapse
Please, can you update to the latest version and see if it works?:fingers-crossed:
I've tried it out with updated .apk and it works perfectly.
Certain bank with horse in logo was throwing "your device is rooted" error. I've checked Xposed cloak module but it failed with its job. Your solution works like a charm and now I can use banking app with root.
Has anyone tested it with the latest build (for L21 I think it's B584 and B585)?
Didn't work properly here. It installed fine, and seemed to work but opening the SuperSU app told me to update the binary which it could not do even after a few reboots. This is on stock B575 with TWRP, no other mods.
Worked flawlessly on stock B584. Had to install SuperSU from Play Store after flashing 2sysless.zip and to update the su binary
Latest version of PoGo working too
Neraeh said:
Worked flawlessly on stock B584. Had to install SuperSU from Play Store after flashing 2sysless.zip and to update the su binary
Latest version of PoGo working too
Click to expand...
Click to collapse
Did you install them after factory reset?
Sent using my Huawei P8 Lite Ale L21
spirto82 said:
Did you install them after factory reset?
Sent using my Huawei P8 Lite Ale L21
Click to expand...
Click to collapse
No, I updated from B574 and installed it right after
Neraeh said:
No, I updated from B574 and installed it right after
Click to expand...
Click to collapse
Did you install only the second file or both? Just asking cause you are referring to the second one...
spirto82 said:
Did you install only the second file or both? Just asking cause you are referring to the second one...
Click to expand...
Click to collapse
I installed both
Unfortunately, PoGo isn't working anymore after a reboot
Just a FYI, the instructions to install this are slightly wrong, i'm guessing you copied from the megathread.
The process to install is:
boot to twrp, and flash zip 1
reboot your phone and open the supersu app, then uninstall it by dragging the supersu app to the bin
reboot to twrp and flash zip 2
reboot and voila. if you do not uninstall the supersu after flashing zip 1, when you flash zip 2 supersu wont actually be installed. just a FYI.