Related
Hey guys! So I read around about rooting Android 6.0.1 and I only see systemless root. I am rooted right now using systemless root and it works fine, but my question is, is there a way to root 6.0.1 with traditional system root? Or is systemless the only way? Just curious really. Will systemless most likely be the future of rooting and the way it's going to have to be done from now on to keep Android Pay working?
Sent from my Nexus 6
I don't know of anyone who's made the kernel mods required for traditional root. I'd say that systemless root is probably going to be the only way to root from now on at least on nexus devices. Chainfire outlines things that don't work with systemless root on the supersu forums.
StykerB said:
I don't know of anyone who's made the kernel mods required for traditional root. I'd say that systemless root is probably going to be the only way to root from now on at least on nexus devices. Chainfire outlines things that don't work with systemless root on the supersu forums.
Click to expand...
Click to collapse
Thanks for the response! And I wonder if it will be what it is for now! It's the only way to keep Android Pay working while the device is rooted correct? Android Pay refuses to work with a traditionally rooted device?
Sent from my Nexus 6
StykerB said:
I don't know of anyone who's made the kernel mods required for traditional root. I'd say that systemless root is probably going to be the only way to root from now on at least on nexus devices. Chainfire outlines things that don't work with systemless root on the supersu forums.
Click to expand...
Click to collapse
I did. I still use SU2.52. But only until this weekend. I'm switching to systemless too.
Actually building a permissive kernel is really straightforward, needs one line of code added. The build is about five minuters then with abootimg you can just replace the existing with the newly buil kernel in the boot.img, and flash it.
I can give you details if you're interested.
Hi
I have a serious problem with ES File Explorer. This app (and maybe other Apps) says device isn't root, since I cant use ES in root explorer mode.
I heard Titanium Backup has the same issue with this future root!
now I back to 6.0 and waiting for a solution.
kamkar said:
Hi
I have a serious problem with ES File Explorer. This app (and maybe other Apps) says device isn't root, since I cant use ES in root explorer mode.
I heard Titanium Backup has the same issue with this future root!
now I back to 6.0 and waiting for a solution.
Click to expand...
Click to collapse
Mine works perfectly.
kamkar said:
Hi
I have a serious problem with ES File Explorer. This app (and maybe other Apps) says device isn't root, since I cant use ES in root explorer mode.
I heard Titanium Backup has the same issue with this future root!
now I back to 6.0 and waiting for a solution.
Click to expand...
Click to collapse
The first systemless root did that, go back to that thread and get the newest version and flash that, fixed that issue.
Sent from my Nexus 6
Krzysiek_CK said:
Mine works perfectly.
Click to expand...
Click to collapse
How? I pass this steps to install and root 6.0.1:
First of all, I have a clean install of 6.0.1
then flash TWRP
In TWRP, install SuperSU 2.61 that flash a custom boot.img automatically. after dalvik/cash wipe, reboot to OS
After that, reboot to recovery again and flash a custom kernel
but supersu doesn't work and ES file explorer says device doesn't have root permission.
however, I need read/write permission in /system folder to delete some useless apks
H4X0R46 said:
The first systemless root did that, go back to that thread and get the newest version and flash that, fixed that issue.
Sent from my Nexus 6
Click to expand...
Click to collapse
I tested 2.61, is problem fixed in 2.62.3? because I must flash 6.0.1 and setup phone again!
i rooted the old fashioned way, there's no difference except you also have to flash a custom kernel when flashing supersu.
simms22 said:
i rooted the old fashioned way, there's no difference except you also have to flash a custom kernel when flashing supersu.
Click to expand...
Click to collapse
Same way it was with 6.0 right? And Android Pay doesn't work with traditional root? Does it break anything else besides Android Pay?
Sent from my Nexus 6
H4X0R46 said:
Same way it was with 6.0 right? And Android Pay doesn't work with traditional root? Does it break anything else besides Android Pay?
Sent from my Nexus 6
Click to expand...
Click to collapse
ive no use for pay, so never tried. i assume its broken..
Sorry,
I have a Nexus 6 with 6.0.
I am trying to find how to update to 6.0.1 with no-enforced-encryption and then do a systemless rooting but I cannot find the instructions to do this
Seems that just flashing stock, TWRP and the flashing supersu 2.61 from there is enough to have systemless root, right?
but what about no-force-encrypt?
Probably I am changing the discussion but have not found a good thread, apologies.
Thanks in advance.
carmatana said:
Sorry,
I have a Nexus 6 with 6.0.
I am trying to find how to update to 6.0.1 with no-enforced-encryption and then do a systemless rooting but I cannot find the instructions to do this
Seems that just flashing stock, TWRP and the flashing supersu 2.61 from there is enough to have systemless root, right?
but what about no-force-encrypt?
Probably I am changing the discussion but have not found a good thread, apologies.
Thanks in advance.
Click to expand...
Click to collapse
What you probably wanna do is go for a custom kernel that doesn't force encryption. Most if not all don't force it! Elementalx is a good one, maybe elite kernel, and so many others! I use ElementalX on mine, my favorite kernel. www.elementalx.org if you wanna try that one! Others are found here on XDA!
EDIT: Looks like elementalx says to use SuperSU 2.61 or later, which is systemless, I would try another. Maybe elite or another one.
H4X0R46 said:
What you probably wanna do is go for a custom kernel that doesn't force encryption. Most if not all don't force it! Elementalx is a good one, maybe elite kernel, and so many others! I use ElementalX on mine, my favorite kernel. www.elementalx.org if you wanna try that one! Others are found here on XDA!
EDIT: Looks like elementalx says to use SuperSU 2.61 or later, which is systemless, I would try another. Maybe elite or another one.
Click to expand...
Click to collapse
Thanks !!! I will check them, I always have tried to be as close to stock as possible but I think it is time to try something new.
One question: Do Custom Kernels interfere with OTA updates?, this is one of the advertised advantages of systemless rooting and is one of my favorites.
Thanks again
carmatana said:
Thanks !!! I will check them, I always have tried to be as close to stock as possible but I think it is time to try something new.
One question: Do Custom Kernels interfere with OTA updates?, this is one of the advertised advantages of systemless rooting and is one of my favorites.
Thanks again
Click to expand...
Click to collapse
I would say yes, I'm 90% sure but could be wrong. I would flash the a new update with fastboot.
carmatana said:
Thanks !!! I will check them, I always have tried to be as close to stock as possible but I think it is time to try something new.
One question: Do Custom Kernels interfere with OTA updates?, this is one of the advertised advantages of systemless rooting and is one of my favorites.
Thanks again
Click to expand...
Click to collapse
Any mod stops ota's. Root, kernels....You will have to flash full images to get updates. You can skip the userdata part and save your apps and data. But you will have to flash.
Not a big deal, it an extra couple of commands just like the kernel you want to flash.
Thanks!
kamkar said:
How? I pass this steps to install and root 6.0.1:
First of all, I have a clean install of 6.0.1
then flash TWRP
In TWRP, install SuperSU 2.61 that flash a custom boot.img automatically. after dalvik/cash wipe, reboot to OS
After that, reboot to recovery again and flash a custom kernel
but supersu doesn't work and ES file explorer says device doesn't have root permission.
however, I need read/write permission in /system folder to delete some useless apks
Click to expand...
Click to collapse
Clean 6.0.1 followed by systemless root installation as expained in the Root done right thread.
Here's the download link for the factory image at the usual place: https://dl.google.com/dl/android/aosp/hammerhead-mmb29s-factory-6bfcdfa4.tgz
Amazed to see that no one created a thread for this (I guess). I know that this is only a month security bug fixing, but still, sometimes they fix other things beyond that.
If anyone notice more bug fixes (or more bugs!!!) beside the security ones, glad to report.
does anyone manage to root it with superSU 2.66?
onesolo said:
Amazed to see that no one created a thread for this
Click to expand...
Click to collapse
Probably because other threads have the link already...
aslam_ said:
does anyone manage to root it with superSU 2.66?
Click to expand...
Click to collapse
Yes. It works without problems.
Sent from my Nexus 5 using XDA Free mobile app
damijanp said:
Yes. It works without problems.
Click to expand...
Click to collapse
So, one only needs to have TWRP and flash latest systemless SuperSu, right?!
EddyOS said:
Probably because other threads have the link already...
Click to expand...
Click to collapse
It's not about the link!!! It's about a thread to discuss this new factory image!!
onesolo said:
So, one only needs to have TWRP and flash latest systemless SuperSu, right?!
Click to expand...
Click to collapse
Yes.
aslam_ said:
does anyone manage to root it with superSU 2.66?
Click to expand...
Click to collapse
Yes. I now have Android 6.0.1 (MMB29S), SuperSU 2.66 and ElementalX 6.0.7.
What the difference with mmb29k?
faighter said:
What the difference with mmb29k?
Click to expand...
Click to collapse
Monthly security update.
tuncan said:
Yes. I now have Android 6.0.1 (MMB29S), SuperSU 2.66 and ElementalX 6.0.7.
Click to expand...
Click to collapse
I'm now on 6.0.1 MMB29K, SuperSU 2.65, and ElementalX 6.07 and intend to update to MMB29S, SuperSU 2.66, same ElementalX. Were/are you running Xposed? I'm wondering if I should uninstall it first and then reinstall afterwards. Thanks
Yes, it worked for me. After update, I flashed elementsX 6.07, then SuperSU 2.66.
PhilipTD said:
I'm now on 6.0.1 MMB29K, SuperSU 2.65, and ElementalX 6.07 and intend to update to MMB29S, SuperSU 2.66, same ElementalX. Were/are you running Xposed? I'm wondering if I should uninstall it first and then reinstall afterwards. Thanks
Click to expand...
Click to collapse
I tried today with xposed and the new factory, NFC service started crashing (i flashed the new system img without deleting data).
So i rebooted again in twrp, flashed the xposed uninstaller zip, then wiped dalvik/cache, flashed xposed installer, wiped dalvik/cache again. Now it's working fine.
ezio84 said:
I tried today with xposed and the new factory, NFC service started crashing (i flashed the new system img without deleting data).
So i rebooted again in twrp, flashed the xposed uninstaller zip, then wiped dalvik/cache, flashed xposed installer, wiped dalvik/cache again. Now it's working fine.
Click to expand...
Click to collapse
Did you wipe cache and dalvik the first time?
I have problems with the update :crying:
Before updating, I had the phone in "alarms only" mode; I flashed the new factory image, and now I can't disable it anymore! I tried both using the notification pane, and the volume rocker, but the setting doesn't switch off...
Any ideas?
PhilipTD said:
Did you wipe cache and dalvik the first time?
Click to expand...
Click to collapse
Yes i did (i also did a fastboot erase for cache, system and boot partitions).
pgptheoriginal said:
I have problems with the update :crying:
Before updating, I had the phone in "alarms only" mode; I flashed the new factory image, and now I can't disable it anymore! I tried both using the notification pane, and the volume rocker, but the setting doesn't switch off...
Any ideas?
Click to expand...
Click to collapse
Weird issue. I'd try a factory reset.
I figured out how to disable it: I added a rule to enable Do Not Disturb for calendar events, then created an event lasting one minute. At the end of the event, the phone was back to "All notifications"; the toggle works fine now.
Sent from my Nexus 5 using Tapatalk
Does it fix the syncing/notification issues ?
PhilipTD said:
I'm now on 6.0.1 MMB29K, SuperSU 2.65, and ElementalX 6.07 and intend to update to MMB29S, SuperSU 2.66, same ElementalX. Were/are you running Xposed? I'm wondering if I should uninstall it first and then reinstall afterwards. Thanks
Click to expand...
Click to collapse
No, I don't have Xposed at the moment.
Another minor issue is that WiFi seems to be always on, looking at the battery usage graph, even when it's set to be off (WiFi scanning is disabled), and even when the phone is in airplane mode!
I don't know how to check if it's actually always on, but I noticed this both before and after the latest security update.
Sent from my Nexus 5 using Tapatalk
When I had my Nexus 5 people would make flashable OTA files to be used in TWRP, is no one doing this any longer? All I can find is how to sideload the OTA.
Thanks
idbl_fanatic said:
When I had my Nexus 5 people would make flashable OTA files to be used in TWRP, is no one doing this any longer? All I can find is how to sideload the OTA.
Thanks
Click to expand...
Click to collapse
just flash the boot.img and system.img in twrp. if you had root, youll need to reroot. yes, twrp flashes system.img and boot.img files now as well.
simms22 said:
just flash the boot.img and system.img in twrp. if you had root, youll need to reroot. yes, twrp flashes system.img and boot.img files now as well.
Click to expand...
Click to collapse
WOW thank you, I didn't know that TWRP did this.
simms22 said:
just flash the boot.img and system.img in twrp. if you had root, youll need to reroot. yes, twrp flashes system.img and boot.img files now as well.
Click to expand...
Click to collapse
Ok, I am a little confused, I am trying to apply the MRA58K from LMY48T OTA found here: http://forum.xda-developers.com/nexus-6/general/ref-nexus-6-stock-ota-urls-t2906493 in the ZIP file, I am not finding system.img, or boot.img
Download the factory images and extract the system and boot.imgs,put them on your SD card(phone storage) enter twrp,select install,then select images in bottom right, select the partition you want to flash to, select the correct.img file
Sent from my Nexus 6 using XDA-Developers mobile app
holeindalip said:
Download the factory images and extract the system and boot.imgs,put them on your SD card(phone storage) enter twrp,select install,then select images in bottom right, select the partition you want to flash to, select the correct.img file
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
Just want to double check, this will be ok to do giong from 5.1.1 to 6.0.1?
idbl_fanatic said:
Just want to double check, this will be ok to do giong from 5.1.1 to 6.0.1?
Click to expand...
Click to collapse
yup
simms22 said:
yup
Click to expand...
Click to collapse
Ok, so, I got my phone updates, however, I had systemless xposed working on it, MM 6.0.1 (MOB30M) however when I went in to try and enable the modules, it gave an error (a long one) so I thought that maybe I didn't have the correct version installed, or wasn't rooted right, so I went back into recovery, re-rooted, and installed 85.3, now it says that xposed isn't installed at all. So for now, I went back to my 5.1.1 restore. Any ideas?
idbl_fanatic said:
Ok, so, I got my phone updates, however, I had systemless xposed working on it, MM 6.0.1 (MOB30M) however when I went in to try and enable the modules, it gave an error (a long one) so I thought that maybe I didn't have the correct version installed, or wasn't rooted right, so I went back into recovery, re-rooted, and installed 85.3, now it says that xposed isn't installed at all. So for now, I went back to my 5.1.1 restore. Any ideas?
Click to expand...
Click to collapse
You have to reflash xposed. It is in the system partition so you will have to redo it after making room as google now fills up the system partition almost completely.
zelendel said:
You have to reflash xposed. It is in the system partition so you will have to redo it after making room as google now fills up the system partition almost completely.
Click to expand...
Click to collapse
I thought that was the whole reason behind the System Less Xposed, so it doesn't install to your system partition.
idbl_fanatic said:
I thought that was the whole reason behind the System Less Xposed, so it doesn't install to your system partition.
Click to expand...
Click to collapse
was the systemless updated to work with the new security measures built into the update? You have to remember that with each update google is making things like xposed harder to get working. It is well known that sooner or later xposed all together will no longer be an option.
So I would check all the changes that the update did to see what it changed. I nor most the people I know have not used xposed in a long time so I really cant say for sure
zelendel said:
was the systemless updated to work with the new security measures built into the update? You have to remember that with each update google is making things like xposed harder to get working. It is well known that sooner or later xposed all together will no longer be an option.
So I would check all the changes that the update did to see what it changed. I nor most the people I know have not used xposed in a long time so I really cant say for sure
Click to expand...
Click to collapse
That makes sense, maybe I'll go to MMB29K instead.
Systemless root or systemless exposed?
Sent from my Nexus 6 using XDA-Developers mobile app
I have systemless xposed working on mob30m. currently have v85.2 installed, all modules working. Only hiccup i ran into was the installer apk. you have to use the one linked in the systemless xposed thread, or it won't recognize the framework is installed.
putridfoetus said:
I have systemless xposed working on mob30m. currently have v85.2 installed, all modules working. Only hiccup i ran into was the installer apk. you have to use the one linked in the systemless xposed thread, or it won't recognize the framework is installed.
Click to expand...
Click to collapse
Thank you, I just reinstalled 6.0.1 MOB30M and it works!
I'm on 6.0 right now with TW recovery, root with SuperSU and Xposed v85, I want to go to 6.0.1 latest version, what would be the best was to do it?
Shall I uninstall xposed, unroot and get stock recovery and then just try to install OTA or is there another way?
cL0uD` said:
I'm on 6.0 right now with TW recovery, root with SuperSU and Xposed v85, I want to go to 6.0.1 latest version, what would be the best was to do it?
Shall I uninstall xposed, unroot and get stock recovery and then just try to install OTA or is there another way?
Click to expand...
Click to collapse
Check out Flashfire in the appstore, it let's you update with OTA, and re-root
idbl_fanatic said:
Check out Flashfire in the appstore, it let's you update with OTA, and re-root
Click to expand...
Click to collapse
Yes, used, Great job, Mr Chainfire
Hi there,
I'm in the process of deciding whether to root my next phone with Magisk or SuperSU. The point I want to discuss here is the risk of bricking the phone. I found rather little information on how Magisk actually links into the system, but it seem that it modifies the /boot image. Now my concern is that if anything goes wrong with this, the phone may be bricked with no return. If I compare this to installing SuperSU to /system, if something goes wrong with that, I still have a working boot loader to boot into recovery and install a working system image. But if /boot is damaged, there should be no return.
So my question: is my understanding of how Magisk works correct, and does this mean higher risk of bricking the device?
Thanks
Tom
I use Magisk for 1 month and I have no problems. Even that Magisk is much better than SuperSU because you can hide the root for your applications.
The boot.img is not your bootloader, it's basically the kernel (part of it anyways). Reflashing your stock boot.img and wiping data would likely reverse anything magisk does. So risky? Not if you backup your stock boot first in twrp. But we backup everything before we flash anything right? Magisk is doesn't modify system at all, everything it does is in /data (besides patching boot.img)
So the question becomes, do you need to pass safetynet for any reason? And would you like to be able to take ota updates?
madbat99 said:
The boot.img is not your bootloader, it's basically the kernel (part of it anyways). (...)
Click to expand...
Click to collapse
Thanks for the clarification. That basically answers my question!
You can use magisk it safe
The best feature of magisk you can hide root from other app like pokemon go, banking app etc
And also you can modify the the system make some app system app or uninstall system without modification of system
And lots more for more details check the magisk official thread
And ya don't download magisk from magisk.com or other site it not offical
I am using magisk in miui rom, Samsung note 4
Moto G5 plus without any problems
can i use magisk on rokit io pro 3d?
i am using note 9 with twrp and magisk installed i want to use google wallet but its asking me to encrypt device.. i tried to encrypt it but its keeps saying encryption failed and reset device even i tried to reset but its still showing same.. so i want to know is it possible with magisk to simply bypass encryption on apps which required it? i mean how can i run apps which require encryption with enabling encryption?
junaidali15 said:
i am using note 9 with twrp and magisk installed i want to use google wallet but its asking me to encrypt device.. i tried to encrypt it but its keeps saying encryption failed and reset device even i tried to reset but its still showing same.. so i want to know is it possible with magisk to simply bypass encryption on apps which required it? i mean how can i run apps which require encryption with enabling encryption?
Click to expand...
Click to collapse
Yes, posible, try this module -
Fake encryption
Is there any way to fake that system has encryption turned on? I do not want to encrypt my phone but my local bank app need encryption in order to use finger print login. Is there way to fake encryption to that app?
forum.xda-developers.com