Related
I have unlocked bl, cwm 6023 and stock 422.
Now I want to root.
Tried already toolkit and n- cry tool without success.
Although the tool says root, there is no root.
How can I get root?
Thx
thebrainkafka said:
I have unlocked bl, cwm 6023 and stock 422.
Now I want to root.
Tried already toolkit and n- cry tool without success.
Although the tool says root, there is no root.
How can I get root?
Thx
Click to expand...
Click to collapse
if you flashed a custom recovery and have the bootloader unlocked, all you have to do is either flash the su binaries or a custom rom via your recovery. latest su binaries http://download.chainfire.eu/311/SuperSU/UPDATE-SuperSU-v1.05.zip
AW: [Q] root 4.2.2
simms22 said:
if you flashed a custom recovery and have the bootloader unlocked, all you have to do is either flash the su binaries or a custom rom via your recovery. latest su binaries http://download.chainfire.eu/311/SuperSU/UPDATE-SuperSU-v1.05.zip
Click to expand...
Click to collapse
Thx. I have cwm installed.
Means flash this su.zip and boom.
Will try. Thx
thebrainkafka said:
Thx. I have cwm installed.
Means flash this su.zip and boom.
Will try. Thx
Click to expand...
Click to collapse
How did it go? I'm inetersted in doing the exact same
Chainfire has developed a new SuperSu Update zip, Version 2.60 and newer 2.61.
with using this update zip, you will not need a custom kernel for getting root in future, works fine on F, FY Model on Android 5.1.1 (tested).
many, many THX to one of best worldwide developer!
This method will work on many othere phones, please read threads for more infos!
First read here: http://forum.xda-developers.com/app...ersu-v2-05-t2868133/post64161544#post64161544
then download latest SuperSu Update zip here: http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
Changelog here: http://forum.xda-developers.com/showpost.php?p=23427824&postcount=3
very easy to use:
Install Stock Samsung based FW with stock bootloader etc...
Install latest TWRP
Use TWRP to install latest SuperSU Zip
Attention: If TWRP tells you SuperSU is not installed, and asks you to install it, do not do it, you will break things!
many thanks to developers!!!!!! Great new thing!!!!
Petteri said:
Chainfire has developed a new SuperSu Update zip, Version 2.60 and newer 2.61.
with using this update zip, you will not need a custom kernel for getting root in future, works fine on F, FY Model on Android 5.1.1 (tested).
many, many THX to one of best worldwide developer!
This method will work on many othere phones, please read threads for more infos!
First read here: http://forum.xda-developers.com/app...ersu-v2-05-t2868133/post64161544#post64161544
then download latest SuperSu Update zip here: http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
Changelog here: http://forum.xda-developers.com/showpost.php?p=23427824&postcount=3
very easy to use:
Install Stock Samsung based FW with stock bootloader etc...
Install latest TWRP
Use TWRP to install latest SuperSU Zip
Attention: If TWRP tells you SuperSU is not installed, and asks you to install it, do not do it, you will break things!
many thanks to developers!!!!!! Great new thing!!!!
Click to expand...
Click to collapse
so can i install xposed without flashing kernel?
Does this work with N915A?
Aggiefury101 said:
Does this work with N915A?
Click to expand...
Click to collapse
Please let me know if you are able to root it. I am wondering if other universal rooting methods work with this phone.
Everything worked fine, you don`t need wondering...it`s Chainfire who developes here! Schould work on all phones (inkluding A VErsion) from Android Lolliopop and higher!
mtayabkk said:
so can i install xposed without flashing kernel?
Click to expand...
Click to collapse
You could of already done that. I flashed xposed and it worked without root. Just flash in custom recovery
Darth-Kadd said:
You could of already done that. I flashed xposed and it worked without root. Just flash in custom recovery
Click to expand...
Click to collapse
without ROOT ? how
No issues with latest stock firmware on 915G. Thanks. ?
mtayabkk said:
without ROOT ? how
Click to expand...
Click to collapse
Trust me, I've done it without root. I had xposed installed before with root then I flashed the latest stock rom from n915w8 and flashed xposed right after without wiping data and it worked. I guess it was because the xposed modules were already configured but ultimately, I did not root in order to use xposed. The functionality of xposed is increased if you root. This is from my experience
The latest xposed for Samsung probably has some loop hole I'm unaware of that allows you to install it without root.
Petteri said:
Everything worked fine, you don`t need wondering...it`s Chainfire who developes here! Schould work on all phones (inkluding A VErsion) from Android Lolliopop and higher!
Click to expand...
Click to collapse
the boot-loader is not unlocked for n915a currently, how can we install twrp? or you mean install supersu by odin without twrp?
step 2... Install latest twrp... How can you do that if your phone has never been rooted before?
for my note edge sprint (915p) i used CWM cos twrp didnt work. after flashing supersu said i dont have root access and if i would like to have it. I SELECTED NO. after rebooting once phone booted fine. took a while for supersu to take over things and now its all good
Petteri said:
Chainfire has developed a new SuperSu Update zip, Version 2.60 and newer 2.61.
with using this update zip, you will not need a custom kernel for getting root in future, works fine on F, FY Model on Android 5.1.1 (tested).
many, many THX to one of best worldwide developer!
This method will work on many othere phones, please read threads for more infos!
First read here: http://forum.xda-developers.com/app...ersu-v2-05-t2868133/post64161544#post64161544
then download latest SuperSu Update zip here: http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
Changelog here: http://forum.xda-developers.com/showpost.php?p=23427824&postcount=3
very easy to use:
Install Stock Samsung based FW with stock bootloader etc...
Install latest TWRP
Use TWRP to install latest SuperSU Zip
Attention: If TWRP tells you SuperSU is not installed, and asks you to install it, do not do it, you will break things!
many thanks to developers!!!!!! Great new thing!!!!
Click to expand...
Click to collapse
Do you by any chance have the latest twrp (2.8.0.7) in .tar file? I've been lurking around for a while now and I'm not able to find it. I can only find .img and I need Linux to convert it to .tar to be able to Odin. I've lost root and now I can't get it back.
Osaab said:
for my note edge sprint (915p) i used CWM cos twrp didnt work. after flashing supersu said i dont have root access and if i would like to have it. I SELECTED NO. after rebooting once phone booted fine. took a while for supersu to take over things and now its all good
Click to expand...
Click to collapse
ok now that ive spent more time with it i believe the root i got is incomplete. on many apps supersu dialogue doesnt pop and they dont recognize the phone as rooted. i used titanium backup to try and remove system apps and despite everything going fine the apps didnt go anywhere
UPDATE: problem fixed. I edited the build.prop in /system/ using a build.prop editor and now all my apps are asking for root
In build.prop look for ro.securestorage.support=True and set it to False
Also solves if your phone keeps forgetting the wifi passwords
It works. SM-915F. Just don't forget to off 'reactivation lock' in security tab in androud in order to install TWRP successfuly. Thanks a lot!
No you're right. Twrp is in img format but you can easily convert it to tar using a linux emulator. Took me minutes to convert it to tar. Google "how to convert img to tar. Running twrp fine
Does it work in 915V ??
So,it's strange how the method works on my 915f. For example; Titanium Backup can't remove systems apps. It looks like I have a root, but not fully operated. Any advices?
Does this still trip the knox counter?
I want to root, but I must keep my warranty as this N915F is on my company's name.
benna said:
Does this still trip the knox counter?
Click to expand...
Click to collapse
Yes. Knox tiked(((
After installing the lollipop update I lost the rooting to the phone.
I rooted my phone again but to be sure for the next time,is there a way to root Lenovo a6000 plus permanently?
When u flash new rom, you have to root again, no way for permanent exept root option include in the rom
You wanted to root again hah? Flash SuperSU.zip (based on my knowledge stock LL cannot/hard to root withe root.apk like kingroot. So, i think the latest tricks is flash the supersu.zip) but still... if you are Advanced User if not dont trying it
GuestStar said:
You wanted to root again hah? Flash SuperSU.zip (based on my knowledge stock LL cannot/hard to root withe root.apk like kingroot. So, i think the latest tricks is flash the supersu.zip) but still... if you are Advanced User if not dont trying it
Click to expand...
Click to collapse
Dude sometimes root doesn't install properly i don't know why... I am on stock with 1.4Ghz oc kernel... Thing happens to me is that whenever i reboot my phone. Root stops working and says su binary needs to be updated.. I just have reinstall again and again to keep it working after boot.. So do u have any to solve it?
MukulGamer said:
Dude sometimes root doesn't install properly i don't know why... I am on stock with 1.4Ghz oc kernel... Thing happens to me is that whenever i reboot my phone. Root stops working and says su binary needs to be updated.. I just have reinstall again and again to keep it working after boot.. So do u have any to solve it?
Click to expand...
Click to collapse
For me root still work even on reboot. To root my phone, i flashed SuperSU.zip with custom recovery twrp. How about you? Did you using same thing like me or by apps like KingRoot.apk?
GuestStar said:
You wanted to root again hah? Flash SuperSU.zip (based on my knowledge stock LL cannot/hard to root withe root.apk like kingroot. So, i think the latest tricks is flash the supersu.zip) but still... if you are Advanced User if not dont trying it
Click to expand...
Click to collapse
Yup obviously.. By SU... I never use kingroot... Well i know it shouldn't have happened... Btw fresh rom install will solve it.. But i don't wanna do that.. Setting up phone again and again suks.. I just asked it because i thought if you might have had this problem! Thanks btw
To clear things up. Think of root as a system module (binary) ("su" module located in "xbin"). Each time you install a new OS, core partitions need to be formated (/cache, /data, and ofc /system). If the SuperUser module is not pre-installed in the new firmware you are flashing, it can be additionally obtained through Chainfire's installation zip. Nearly all custom ROMs have it and will work just fine, with some needing user input to activate it (Settings > Dev Settings > Root Access). While stock ROMs will NEVER have root capabilities pre-loaded.
So, all in all:
No, there is no such thing and will never be, as permanent root. Everything is being overwritten all the time.
Rooting and re-rooting the A6000 is safe and easy.
Hi guys, I have successfully rooted using temporary TWRP + modded magisk method, but now I gain root and checked via Root checker. But the problem is most of the root functions don't work as /system is read-only. Any idea?
Ya i have an idea.. Happened to me as well. I tried almoat everything but system won't be accessible anywhere.. I followed the same tutorial and installed magisk 13.4.
The only solution i could find was flash the latest factory image, and root again using supersu. I used the AIO tool by ghpranav and have got my phone rooted with xposed working without any issues.
zazzy24 said:
Ya i have an idea.. Happened to me as well. I tried almoat everything but system won't be accessible anywhere.. I followed the same tutorial and installed magisk 13.4.
The only solution i could find was flash the latest factory image, and root again using supersu. I used the AIO tool by ghpranav and have got my phone rooted with xposed working without any issues.
Click to expand...
Click to collapse
I also fixed the issue. I flash the modified boot image and I am now gaining proper root access + Xposed. Get it working using Super SU, idk why Magisk keep failing thou. Was wanted to give Magisk a try, but it doesn't work properly on our device.
Cool:good:
Xposed isn't working with magisk? I was planning to install it
amithiel said:
Xposed isn't working with magisk? I was planning to install it
Click to expand...
Click to collapse
Only with SuperSU as I know.
Sent from my Mi A1 using Tapatalk
Guys, this is Magisk from Pixel. You can't expect that it is working. I wrote to MagiskDevs already, they are working on a own Version for Mi A1. Use for that time normal SuperSU (Xposed works normally )
how to??
soralz said:
I also fixed the issue. I flash the modified boot image and I am now gaining proper root access + Xposed. Get it working using Super SU, idk why Magisk keep failing thou. Was wanted to give Magisk a try, but it doesn't work properly on our device.
Click to expand...
Click to collapse
Hay how do you Fix the Read only Issue? can you please share the Modified Boot image and process for same, thanks
maxsan20 said:
Hay how do you Fix the Read only Issue? can you please share the Modified Boot image and process for same, thanks
Click to expand...
Click to collapse
https://desktop.firmware.mobi/device:1748
Just root with replacing the boot image then you are good to go.
soralz said:
https://desktop.firmware.mobi/device:1748
Just root with replacing the boot image then you are good to go.
Click to expand...
Click to collapse
Hi,
I have TWRP installed and unrooted, what I need to do please?
We7dy said:
Hi,
I have TWRP installed and unrooted, what I need to do please?
Click to expand...
Click to collapse
You need flash back stock boot image first, due to some limitations you can't have TWRP and SuperSU root at the same time. If you don't have the stock boot image. I suggest download the ROM from MIUI and then flash it. You can choose "flash_all_except_storage" option, this will keep your data.
http://en.miui.com/download-333.html
After flashing. Reboot back to fastboot and then:
Code:
fastboot oem unlock
After that just run root.bat from the cf-auto root folder you downloaded and wait for it to automatically reboot your phone. You should have root now, if you wish you can download SuperSU from the store.
soralz said:
You need flash back stock boot image first, due to some limitations you can't have TWRP and SuperSU root at the same time. If you don't have the stock boot image. I suggest download the ROM from MIUI and then flash it. You can choose "flash_all_except_storage" option, this will keep your data.
http://en.miui.com/download-333.html
After flashing. Reboot back to fastboot and then:
After that just run root.bat from the cf-auto root folder you downloaded and wait for it to automatically reboot your phone. You should have root now, if you wish you can download SuperSU from the store.
Click to expand...
Click to collapse
Ok, thanks. It's not possible to do that via TWRP? I don't have PC. Currently my bootloader is unlocked, I have TWRP and I'm unrooted.
We7dy said:
Ok, thanks. It's not possible to do that via TWRP? I don't have PC. Currently my bootloader is unlocked, I have TWRP and I'm unrooted.
Click to expand...
Click to collapse
I actually tried before, and I tell you the results:
Option 1 TWRP installed + Rooted with Magisk
= Pretty much useless as /system is read-only. Every root app doesn't function, unless it is system-less. But system-less modules nearly all doesn't work as the Magisk version too old. And this method won't trip safetynet
Option 2 no TWRP + Rooted with SuperSU (cf-root method) -- Currently using this state
= Got proper root access, Xposed works but will trip safetynet
Option 3 TWRP installed + Rooted with SuperSU (cf-root method)
= Don't try this, will cause your phone stuck in boot loop
soralz said:
I actually tried before, and I tell you the results:
Option 1 TWRP installed + Rooted with Magisk
= Pretty much useless as /system is read-only. Every root app doesn't function, unless it is system-less. But system-less modules nearly all doesn't work as the Magisk version too old. And this method won't trip safetynet
Option 2 no TWRP + Rooted with SuperSU (cf-root method) -- Currently using this state
= Got proper root access, Xposed works but will trip safetynet
Option 3 TWRP installed + Rooted with SuperSU (cf-root method)
= Don't try this, will cause your phone stuck in boot loop
Click to expand...
Click to collapse
So not possible via TWRP? Get root access and remove TWRP? I just need that... The root.
We7dy said:
So not possible via TWRP? Get root access and remove TWRP? I just need that... The root.
Click to expand...
Click to collapse
The best bet and possible trouble free is to first download the stock ROM from MIUI, reflash it and then root.
soralz said:
The best bet and possible trouble free is to first download the stock ROM from MIUI, reflash it and then root.
Click to expand...
Click to collapse
:/ Can't root with TWRP without system read only...
We7dy said:
:/ Can't root with TWRP without system read only...
Click to expand...
Click to collapse
It's possible to root without CF-Auto-Root? Why can't flash SuperSu directly with TWRP?
We7dy said:
It's possible to root without CF-Auto-Root? Why can't flash SuperSu directly with TWRP?
Click to expand...
Click to collapse
No, it will cause your phone stuck it boot loop if you try to flash the SuperSU zip directly from the official ChainFire site. I think probably is the AB partitioning problem or some sort (unsure). As I said you need to run CF-Auto root to get proper root access, otherwise flashing Magisk through TWRP will makes most of the root apps does not work properly unless it also uses system-less root function.
soralz said:
No, it will cause your phone stuck it boot loop if you try to flash the SuperSU zip directly from the official ChainFire site. I think probably is the AB partitioning problem or some sort (unsure). As I said you need to run CF-Auto root to get proper root access, otherwise flashing Magisk through TWRP will makes most of the root apps does not work properly unless it also uses system-less root function.
Click to expand...
Click to collapse
Ok I have TWRP installed can I use directly CF auto root?
We7dy said:
Ok I have TWRP installed can I use directly CF auto root?
Click to expand...
Click to collapse
No if you want proper root with CF-auto root you must not have TWRP installed. You either choose TWRP + Magisk (non-working root) or no TWRP but with SuperSU (working root, Xposed works too).
Follow the instruction here to get you on track:
https://forum.xda-developers.com/showpost.php?p=74326169&postcount=2
Although TWRP is *supposed* to be lokied, it turns out that all the 3.x versions are not properly lokied. This has been reported in the last couple of pages of this thread, and it's been reported in their bug tracker (although they seem to be ignoring it for now).
One of the users in that xda thread was kind enough to loki a few TWRP releases, but the latest one he did was v3.1.1.0, and he hasn't done any more since.
Can someone else be kind enough to Loki the latest version of TWRP for jflteatt, located here? (Preferably both IMG and TAR, so people can use it with whichever installation method they prefer/need)
My guide tells you how to Loki CWM recovery, it should work the same for TWRP (should is the keyword here).
https://forum.xda-developers.com/galaxy-s4-att/general/how-to-one-guide-to-mdl-bootloader-t3584122
StoneyJSG said:
My guide tells you how to Loki CWM recovery, it should work the same for TWRP (should is the keyword here).
https://forum.xda-developers.com/galaxy-s4-att/general/how-to-one-guide-to-mdl-bootloader-t3584122
Click to expand...
Click to collapse
Thank you. However, the method described requires root.
I had root on CyanogenMod 11, but ever since I flashed LineageOS 14.1, I haven't been able to root my phone without bricking it - so this method won't work for me.
How are you on lineage OS without having root? You need root to install a custom recovery which then in turn allows a custom ROM. I know lineage OS hides or does sometimes with superSU, so it might be hiding root as well (unless I am thinking of Oct OS).
Your phone is probably rooted, use the root checker app from the play store to check. If by chance somehow it's not, then use towel root, king root, one click root, safe root, CF auto root, or kingo root to root it. If all else fails you might have to ODIN back to stock, then root, then install the latest TWRP then Loki it using my guide then install lineage OS.
StoneyJSG said:
How are you on lineage OS without having root? You need root to install a custom recovery which then in turn allows a custom ROM. I know lineage OS hides or does sometimes with superSU, so it might be hiding root as well (unless I am thinking of Oct OS).
Your phone is probably rooted, use the root checker app from the play store to check. If by chance somehow it's not, then use towel root, king root, one click root, or kingo root to root it.
Click to expand...
Click to collapse
No, my phone is definitely not rooted. It *previously* had root under CyanogenMod 11. That's how I had a custom recovery installed. So I was able to use TWRP to flash LineageOS 14.1 just fine. However, here are the results of my trying to root this phone under LOS 14.1:
1. Magisk: Bricked on Samsung Logo.
2. SuperSU (normal systemless): Not installed properly. Seems to fail on patching the boot image.
3. SuperSU (system mode): Bricked on Lineage boot screen.
4. LineageOS addonsu: Installs fine, but doesn't seem to do anything. I still don't have root.
I've tried posting about this in a few places on xda, but so far, I haven't had any luck.
So *maybe* if I revert back to an older version of Android, I might be able to get a working root. But in order to be recent, it's looking like I have little choice but to finally retire this phone and get something newer. Which is unfortunate, because there's nothing wrong with the phone hardware-wise.
Perhaps I'll try one of the other root options you mentioned and hope it doesn't brick my phone as well.
That's really odd that you have a custom recovery and ROM without root. You might have to ODIN back to stock Android 4.2.2 jelly bean using the MDL firmware .tar file. Can you revert back to a TWRP that is Loki?
StoneyJSG said:
That's really odd that you have a custom recovery and ROM without root. You might have to ODIN back to stock Android 4.2.2 jelly bean using the MDL firmware .tar file. Can you revert back to a TWRP that is Loki?
Click to expand...
Click to collapse
I have a Lokied version of TWRP (3.1.1.0), which is working fine. But with all of the problems I've been having trying to get root, I was wondering if perhaps a newer version of TWRP might make the difference. That's why I was trying to get a Lokied version of the latest TWRP.
Ah so you're trying to gain root by flashing TWRP. No idea why lineage OS removed root, unless the people who made it built it that way. The only thing I can think of is either try all the root apps I mentioned before and if that doesn't work then ODIN back to MDL stock and use towel root to root. If lineage OS is anything like Oct OS, you will have to root using a root .zip file.
I wish I could be more help, but I haven't ever used lineage OS before due to liking touchwiz. I run golden eye ROM on my at&t Loki phone.
StoneyJSG said:
My guide tells you how to Loki CWM recovery, it should work the same for TWRP (should is the keyword here).
https://forum.xda-developers.com/galaxy-s4-att/general/how-to-one-guide-to-mdl-bootloader-t3584122
Click to expand...
Click to collapse
Unfortunately it does not work:
Code:
1|[email protected]:/data/local/tmp # ./loki_flash recovery twrp.img
[+] loki_flash v1.1
[-] Input file is not a Loki image.
1|[email protected]:/data/local/tmp #
jabulon said:
Unfortunately it does not work:
Code:
1|[email protected]:/data/local/tmp # ./loki_flash recovery twrp.img
[+] loki_flash v1.1
[-] Input file is not a Loki image.
1|[email protected]:/data/local/tmp #
Click to expand...
Click to collapse
Thanks for trying it! It's now confirmed my guide is only for CWM recovery.
Not sure if you've already searched it out, but HERE is my thread with the latest Loki patched twrp. I lokied jfltexx 3.2.3-0 which works on the i337 (ATT) s4.
There's also this:
https://forum.xda-developers.com/galaxy-s4-att/general/lokid-jfltexx-twrp-att-vzw-s4-t3869503
StoneyJSG said:
There's also this:
https://forum.xda-developers.com/galaxy-s4-att/general/lokid-jfltexx-twrp-att-vzw-s4-t3869503
Click to expand...
Click to collapse
Your link IS my link from the post directly above yours
Oh crap haha so it is. Oops brain fart there, my fault.
StoneyJSG said:
Oh crap haha so it is. Oops brain fart there, my fault.
Click to expand...
Click to collapse
You're good ? I had it in a separate post, and I just created that thread the other day to give it a permanent home more easily found.