Related
Hi All,
My Nexus 5 was on 5.1 and is rooted with Chainfire SU. The OTA update arrived a couple days ago but I can't apply it - it goes into recovery, starts the install and then stops showing "Error" and needs a reboot.
Best way to get 5.1.1 on it?
Ric
I have this issue too and would like help. I tried the unrooting function provided by SuperSU but that didn't resolve the issue.
You may find your answer here:
http://forum.xda-developers.com/goo...e-update-rooted-device-to-5-1-lmy47d-t3050789
Thank you! Dirty flash using the nexus root tool did the job nicely
Sent from my Nexus 5 using Tapatalk
I side loaded it in stock recovery.
Today my apps were acting weird so i went to my superSU and it said
"there is no SU binary installed, and superSU cannot install it. This is a problem!"
Seems like I've tried everything to fix this problem. Flashed stock rom using Odin, reflash CF-root after that. Tried installation custom recovery (can't flash using recovery because my phone is encrypted unless there's a way to by pass that). Used different cords, ports, versions of odins. Still nothing. Had this problem since the morning it's now 8pm here so i decided to ask.
Anyone know how to fix this issue?
Hey, is there anyone who solved the problem ? I got the same issue with my brand new Galaxy S7, quite anoying ...
So have i with my S6. No cure so far, tried everything. Waiting for chainfire to jump in...
Verstuurd vanaf mijn SM-G920F met Tapatalk
I have also just experienced this. Everytime I try to remember root and run root checker it says not rooted.
try root with twrp and a kernel like "adam kernel" or a nearly stock one. Then try flash form recovery supersu 2.74
Ive got the same issue. I have G920i stock 6.0.1 rom and stock kernel and rooted using cf-root. However today i noticed my device is not rooted anymore. Also a week ago my phone completly froze and i had to go to download mode and reboot the device. Im not really sure if this incident was related for the device to become unrooted. Any help is appreciated
Same problem! I rooted my galaxy s7 with cf-root and odin and it worked fine for a while until I got no root privileges and had to reroot it. It worked once more and again - unrooted by itself, only this time rooting doesn't work! it says that it roots it but when I check supersu, it says no SU binary. Please someone help!
same issue
deveice is s6 and china version.
I just bought it one week
wait the solution.
Strange, same thing just happened to me today in Samsung S7. Phone restarted on its own and now no root access. I had it rooted like 2 months ago with Cf and Odin and had been working fine. What happened??
same here , S6 G920F... lost all access from rooted apps tried re-root with odin , also installing supersu again and again , deleted also all the required-rood apps ... nothing works
Hey guys this is already solved. Samsung pushed a security policy update that broke the root. So now the way to go is that you need to flash stock rom with odin. I used smart switch which is easier and worked too. Then after you have stock rom you root using the new cf-auto root by chainfire. Enjoy.
LAUNCHERMONKEY said:
Today my apps were acting weird so i went to my superSU and it said
"there is no SU binary installed, and superSU cannot install it. This is a problem!"
Seems like I've tried everything to fix this problem. Flashed stock rom using Odin, reflash CF-root after that. Tried installation custom recovery (can't flash using recovery because my phone is encrypted unless there's a way to by pass that). Used different cords, ports, versions of odins. Still nothing. Had this problem since the morning it's now 8pm here so i decided to ask.
Anyone know how to fix this issue?
Click to expand...
Click to collapse
This happened to me today, I fixed by restoring to stock using smart switch and then using cf-autoroot to re root.
I had same problem
r00tkiller said:
Hey, is there anyone who solved the problem ? I got the same issue with my brand new Galaxy S7, quite anoying ...
Click to expand...
Click to collapse
Basically I just fixed it by reflashing my ROM straight on top of my old ROM (ressurection remix) I did not wipe cache or dalvik just straight reflashed ROM and it fixed it
Nothing else I tried worked not sure if I will get the same error again but it worked for now
Plus I had error previously with su binary update think this is the cause
I have the Exynos S7 Flat (G930FD) and I'm wanting to root it.
I've done this before about a year ago, but then I ended up getting a new device.
Since then, apparently SHealth now requires KNOX, which rooting will trip.
Is there any way I can bypass this? Perhaps a custom ROM or something? I know there used to be an Xposed module that restored private mode and something else, but I don't think it works anymore.
Basically I want to have root access as well as to be able to use S Health.
FallenArchangel7 said:
I have the Exynos S7 Flat (G930FD) and I'm wanting to root it.
I've done this before about a year ago, but then I ended up getting a new device.
Since then, apparently SHealth now requires KNOX, which rooting will trip.
Is there any way I can bypass this? Perhaps a custom ROM or something? I know there used to be an Xposed module that restored private mode and something else, but I don't think it works anymore.
Basically I want to have root access as well as to be able to use S Health.
Click to expand...
Click to collapse
Remove s health and install like a normal app a older version.
Enviado do meu SM-G930F através de Tapatalk
Basically, what vladmir said. S-Health disables services if you're rooted starting from version 5, so any previous versions will not have this problem. Just Google S-health APK 4.9 or something like that, and install.
https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-s-health-devices-knox-t3543306 Works well thanks to CuBz90
FallenArchangel7 said:
I have the Exynos S7 Flat (G930FD) and I'm wanting to root it.
I've done this before about a year ago, but then I ended up getting a new device.
Since then, apparently SHealth now requires KNOX, which rooting will trip.
Is there any way I can bypass this? Perhaps a custom ROM or something? I know there used to be an Xposed module that restored private mode and something else, but I don't think it works anymore.
Basically I want to have root access as well as to be able to use S Health.
Click to expand...
Click to collapse
I'm running Sheath on multiple devices all with Rooted Custom Roms that are AOSP / LineageOS based....
The interesting thing is that Sheath won't run on a Stock Rooted TW Rom
Sent from my SM-G930W8 using Tapatalk
shaggyskunk said:
I'm running Sheath on multiple devices all with Rooted Custom Roms that are AOSP / LineageOS based....
The interesting thing is that Sheath won't run on a Stock Rooted TW Rom
Sent from my SM-G930W8 using Tapatalk
Click to expand...
Click to collapse
It works just fine on Marshmallow, but if you upgrade to Nougat then you need a custom ROM to make it work.
Removing it and installing it as a non-system app doesn't seem to change anything, and installing an older version didn't help me either.
I've downgraded to 6.0.1 so it doesn't really affect me any more though.
It is very simple to make SHealth working.
First root your device with Magisk using this thread:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Magisk is able to hide itself from a lot of apps, which won't run if your phone is rooted (i.e. Pokemon go, Mario run...)
If Magisk won't help you then:
install file explorer, it can be ES file explorer,
enable root explorer option (in ES file explorer)
go to /system directory
edit file build.prop
Look for ro.config.tima=1 and change the value to 0
reboot phone and now SHealth will work perfectly
How do i root/install twrp my sprint s6 edge which is on nougat?
flash this with TWRP https://www.dropbox.com/s/yk71179z29zo87h/N920_Nougat_Root_SuperSU_No_kernel_included.zip?dl=0
i tried to flash twrp twice, my phone is now soft bricked. as soon as i boot it up, there is this flash and when i touch my phones screen, it vibrates. i dont know whats going on anymore. i will now try and flash stock firmare
*UPDATE*
i have successfully flashed the stock firmware and my phone is working. The loss of data is unfortunate, but as long as my beloved s6 edge is working, i dont mind. i think ill just wait until there is a proper way to root 7.0. until that time ill just use 6.01 i guess.
Thanks anyways
FullMetalSusano said:
*UPDATE*
i have successfully flashed the stock firmware and my phone is working. The loss of data is unfortunate, but as long as my beloved s6 edge is working, i dont mind. i think ill just wait until there is a proper way to root 7.0. until that time ill just use 6.01 i guess.
Thanks anyways
Click to expand...
Click to collapse
which stock firmware did u use
6.0.1, G925PVPU3CPB6 from sammobile.
then i got the ota and just updated to 7.0
now im going to re-flash 6.0.1 and then cf auto root. i cant stand my phone without root.
unless someone helps me flash twrp. so that i can flash that super su file with it.
i noticed something while browsing the twrp site, it says something like "This device uses dm-verity. This means that swiping to allow system modifications will prevent you from being able to boot if you are using the stock kernel. In order to bypass dm-verity's boot prevention, you will have to install a kernel that has dm-verity disabled in the fstab". now i this verity thing is my nightmare. before when i had rot, i forgot i had used cf and went to super su and remove root. next thing i know, my s6 is in a boot loop. And when i went to boot loader it showed a message saying dm verity failed. Can anyone guide me? To flashing that kernal that is
guys ive done it. rsktkr1 thanks. i was basically flashing the wrong twrp. I will leave the link to the correct twrp file just in case there is someone who went through the same hardships as me. https:// dl.twrp.me/zeroltespr/twrp-3.1.0-0-zeroltespr.img.tar. html just remove the spaces
Thanks guys. Sorry for all the trouble.
well i got my s6 edge back and running. I had it on mm 6.0 and rooted it once more just now i decided to go back to nougat. I have found that twrp 3.1.0 sent my edge into a bootloop and actually hard bricked my phone. I figured sine my s6 flat took root on nougat that since i used the n20p supersu nand 3.2.0 twrp ran flawless with just one problem which is battery life it dont very long. so if i were to try the note versionj of my edge it might work but for custom recovery stay with 3.2
I have a question. I want to root my phone (upgraded from oreo to pie, stock), but i'm not sure what should i do. Should i use oreo rooting instructions? I can't find any tutorial for rooting on pie. I don't want to change my rom, i just want to have a root and be able do use the magick and modules that's all. It would be nice to have step by step instruction.
I know i have to unlock my bootloader first at htcdev, then install twrp (not sure which twrp and if the installation is same as on oreo?)
In the past i rooted one phone but it was completely different and i almost bricked my device, because some idiot posted wrong link on the forum... There is so many versions of everything and i'm feeling lost in it.
I hope this helps, but Pie is still very new for the HTC U11. Some even are saying that clean flashes of the Pie RUU have flash, camera, and wifi issues. I am currently running the amazing RR-P rom (which is based on pie), but it runs on the latest Oreo RUU. I have no issues with the ROM and I get insane SoT even without battery savings. I am excited for the future of this phone, since I love the hardware navbar (never liked the on-screen one / though my HTC m8 is still a boss, and even the forums there have a very solid Lineage 17.0 (android 10) working on it).
https://dl.twrp.me/ocn/
Above is the official link to the US HTC u11 TWRP recoveries. I don't think (to be safer than sorry) these are 100% compatible over the PIE firmware though.
I checked HTCdev, and it doesn't seem to have any difference in the instructions in unlocking the bootloader. No mention of Nougat or Oreo, so I would assume there's no difference in doing the same with Pie.
I flashed my U11 after Pie update, working fine, no problems with flash, wifi or anything else (CID: HTC__034)
1. Unlock bootloader via htcdev
2. Flash latest TWRP from the official site. Instructions here for example: https://www.xda-developers.com/how-to-install-twrp/
3. Flash Magisk (also from official Magisk site)… that was a little trickier, since TWRP can't mount the encrypted partitions. The workaround is to copy the Magisk ZIP onto an SD Card and flash it from there while in TWRP.
4. Enjoy.
I decided to root this U11 for the first time, since I don't expect any futur software updates coming form HTC.
Thank you for all your help, i'll try this out today. :good:
So i did everything and it's working but i have one problem. After installing magisk i tried to install some modules, and one of them caused bootloop and i was unable to delete it, and also i was unable to install module uninstaller (fail). So i had to do factory reset - any solution to avoid this kind of problems in future?
Also i installed xposed successfully, but none of modules was working..
Togzyk said:
So i did everything and it's working but i have one problem. After installing magisk i tried to install some modules, and one of them caused bootloop and i was unable to delete it, and also i was unable to install module uninstaller (fail). So i had to do factory reset - any solution to avoid this kind of problems in future?
Also i installed xposed successfully, but none of modules was working..
Click to expand...
Click to collapse
I have no answers, but as u can see a rooted pie is problematic, hence the many people reverting back to oreo and or nougat, but some people somehow make it work. Not me I could not downgrade quick enough after rooting, unrooted pie worked great, but my many 'need for root apps' did not , so back to oreo for me . Just my 2 cents!! Good luck.
hammered58 said:
I have no answers, but as u can see a rooted pie is problematic, hence the many people reverting back to oreo and or nougat, but some people somehow make it work. Not me I could not downgrade quick enough after rooting, unrooted pie worked great, but my many 'need for root apps' did not , so back to oreo for me . Just my 2 cents!! Good luck.
Click to expand...
Click to collapse
I found many working apps. The biggest problem is "substratum", especially when it comes to changing navbar buttons. But gravitybox is working, and I'm happy with it. Thanks for your help
My rooted Pie works fine, but I didn't install Substratum or Xposed.