Related
So question is, when we ill we be able to successfully root Android M?
Have tired with TWRP. get stuck on HTC One boot screen.
Had to flash stock ROM via stock recovery...
***
TWRP 2.8.7.0
SupersU 2.46 (also tried beta version 2.52 zip
You need to use latest SuperSU 2.65. Download
When TWRP want to install SuperSU check "Do not install" and reboot.
Hmm, I've done the above and it seemed to install correctly, but the SuperSU app which I installed from the zip is saying "no SU binary installed".
Once you flash the superSU zip you then need to install the app from the play store and open the app to finish the process
Sent from my HTC One M9 using Tapatalk
scoot0073 said:
Once you flash the superSU zip you then need to install the app from the play store and open the app to finish the process
Click to expand...
Click to collapse
Thanks, I've also tried the app store app, it says "no SU binary installed".
For me, I can't install SuperSU as system app. (not currently available in system-less root mode). And Twrp says I'm not rooted, asks to install
Try 2.64.zip no problems for me
Running 2.65
2.64 didn't work either, still get the same problem. Think I'll just try to install it the system way.
Try starting from scratch. Flash stock ROM. RE flash twrp and beta supersu
It worked well for me too:
http://forum.xda-developers.com/showpost.php?p=64493553&postcount=296:bien:
Gandalforce said:
Try starting from scratch. Flash stock ROM. RE flash twrp and beta supersu
Click to expand...
Click to collapse
MegaGalan said:
It worked well for me too[/url]
Click to expand...
Click to collapse
I just reinstalled the 3.35.617.12 RUU, then TWRP 2.7.8.1_CPTB-B1, then flashed the 2.64 SuperSU zip without making system writable, rebooted without letting TWRP install su, then installed the play store app and I still get the same problem.
I just can't see what I'm doing wrong. The custom boot.img is built by the installation script - I don't need to get it from anywhere, do I? Or a custom kernel that supports it?
There doesn't seem to be the custom mount point.
If I set the /data/.supersu to SYSTEMLESS=false, it installs in the system, but bootloops (just doesn't boot, there's a repeated init permission problem with the su daemon).
BenPope said:
I just reinstalled the 3.35.617.12 RUU, then TWRP 2.7.8.1_CPTB-B1, then flashed the 2.64 SuperSU zip without making system writable, rebooted without letting TWRP install su, then installed the play store app and I still get the same problem.
I just can't see what I'm doing wrong. The custom boot.img is built by the installation script - I don't need to get it from anywhere, do I? Or a custom kernel that supports it?
There doesn't seem to be the custom mount point.
If I set the /data/.supersu to SYSTEMLESS=false, it installs in the system, but bootloops (just doesn't boot, there's a repeated init permission problem with the su daemon).
Click to expand...
Click to collapse
Using the same vers or twrp as you, with 2.65, zero issues.
Though i have had that problem in the past, ended up being a bad zip file.
Do you want my copy of twrp and supersu?
sssssbarn said:
Using the same vers or twrp as you, with 2.65, zero issues.
Though i have had that problem in the past, ended up being a bad zip file.
Do you want my copy of twrp and supersu?
Click to expand...
Click to collapse
That's a kind offer. The md5sums would be sufficient, I guess.
Sent from my HTC One M9 using Tapatalk
BenPope said:
That's a kind offer. The md5sums would be sufficient, I guess.
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
Try these:
https://drive.google.com/file/d/0B0US5WgszgfdOTRuLUFBZ3pNQlk/view?usp=docslist_api
https://drive.google.com/file/d/0B0US5WgszgfdNDRsODFybzhlRDA/view?usp=docslist_api
Exact files i used
sssssbarn said:
Try these:
https://drive.google.com/file/d/0B0US5WgszgfdOTRuLUFBZ3pNQlk/view?usp=docslist_api
https://drive.google.com/file/d/0B0US5WgszgfdNDRsODFybzhlRDA/view?usp=docslist_api
Exact files i used
Click to expand...
Click to collapse
thanks for the files... fyi you transposed the numbers in the version of twrp. it is 2.8.7.1.
Okay, so now i tired to flash SuperSU 2.66, annddd i get stuck in bootloop.
Only 2.65 works solid.
Any thoughts?
Gandalforce said:
Okay, so now i tired to flash SuperSU 2.66, annddd i get stuck in bootloop.
Only 2.65 works solid.
Any thoughts?
Click to expand...
Click to collapse
I had problems with 2.66 as well. I reported it with a logcat and sticking with 2.65 for now
Same
Gandalforce said:
Same
Click to expand...
Click to collapse
Yeah same here.
Had to install TWRP twrp-2.8.7.1_CPTB-B1-hima and BETA-SuperSU-v2.65-20151226141550. then finally booted in to the OS.
Hello guys
I havea problem after CyanogenMod 12.1 installation on i9082
Everything works fine but
I can't have root access, it seems that the device got unrooted after the ROM
I have tried to enable developer options
And I checked root access in the setting to Apps and ADB
but I still get unrooted messages when I try to open an application that requires root
Also I tried to flash supersu from CM recovery but the installation stops in the middle
I tried several different versions of supersu but still the same problem.
Diaa toulba said:
Hello guys
I havea problem after CyanogenMod 12.1 installation on i9082
Everything works fine but
I can't have root access, it seems that the device got unrooted after the ROM
I have tried to enable developer options
And I checked root access in the setting to Apps and ADB
but I still get unrooted messages when I try to open an application that requires root
Also I tried to flash supersu from CM recovery but the installation stops in the middle
I tried several different versions of supersu but still the same problem.
Click to expand...
Click to collapse
Install Twrp or other custom recovery, dissable update cm recovery first in dev option, then install supersu.
Hello thanks a lot for your reply but twrp custom recovery requires root access
Diaa toulba said:
Hello thanks a lot for your reply but twrp custom recovery requires root access
Click to expand...
Click to collapse
What do you mean? Did you installed twrp manager app? Not that app, you need to flash Twrp/cwm.zip file through cm recovery. Or find the cwm/twrp.tar file and flash by Odin.
NeoLogY said:
What do you mean? Did you installed twrp manager app? Not that app, you need to flash Twrp/cwm.zip file through cm recovery. Or find the cwm/twrp.tar file and flash by Odin.
Click to expand...
Click to collapse
Yes I though you meant the app
I didn't know that can you give me the link to download twrp.rar
Diaa toulba said:
Yes I though you meant the app
I didn't know that can you give me the link to download twrp.rar
Click to expand...
Click to collapse
check it under Grand Android Development thread, there are twrp and cwm in zip file, can be flash through recovery. Same thread with cm12.1 that you flashed.
Flash superuser zip.
Your Rom is Pre-Rooted But you need to flash latest Superuser.zip to gain Root accesses .
Diaa toulba said:
Hello guys
I havea problem after CyanogenMod 12.1 installation on i9082
Everything works fine but
I can't have root access, it seems that the device got unrooted after the ROM
I have tried to enable developer options
And I checked root access in the setting to Apps and ADB
but I still get unrooted messages when I try to open an application that requires root
Also I tried to flash supersu from CM recovery but the installation stops in the middle
I tried several different versions of supersu but still the same problem.
Click to expand...
Click to collapse
OK now I installed CWM v.6 custom recovery
But when itry to flash the supersu zip file it gives installation complete dialogue but when I reboot I can't see the supersu icon and Im still unrooted
Diaa toulba said:
OK now I installed CWM v.6 custom recovery
But when itry to flash the supersu zip file it gives installation complete dialogue but when I reboot I can't see the supersu icon and Im still unrooted
Click to expand...
Click to collapse
Try type this in dialer *#1234#* or *#*#1234#*#*. If any of 5hose doesn't work, visit supersu thread.
OK I tried these lines but nothing happened can you give me link to supersu thread?
cm12 has root disabled by default. Activate it from developer options.
Or you can flash supersu
Diaa toulba said:
OK I tried these lines but nothing happened can you give me link to supersu thread?
Click to expand...
Click to collapse
After you flash supersu, did any app need root worked? Which version supersu did you flashed?
Used the non systemless one( 2.56 and below).
http://forum.xda-developers.com/showthread.php?t=2868133
Also might wanna try twrp recovery.
now it worked! the problem was that i had supersu installed but it was disabled from the app store thats why i didn't see its icon in the apps
thanks alot for your help, man :good:
Diaa toulba said:
now it worked! the problem was that i had supersu installed but it was disabled from the app store thats why i didn't see its icon in the apps
thanks alot for your help, man :good:
Click to expand...
Click to collapse
Good to know. New thing I've learned from your issue. Thanks for that.
I got the same problem as above I just flash su2.76 but it didn't worked out the cm update rec. Is disable ... It give installation completed but doesn't get rooted..
I know it's a known bug that if the data partition is in f2fs.
And if anyone roots any custom rom which doesn't have internal root.
Device unroot itself after sometime after reboot.
Is there any workaround for this?
I'm using tesla 3.4 beta and pico open gapps and supersu 2.79
SuperSU is not compatible with f2fs. Try phh suprsuser, it worls.
If you still want SuperSU try installing it in systemmode after fresh install or switch to ext4.
aadityarulez said:
SuperSU is not compatible with f2fs. Try phh suprsuser, it worls.
If you still want SuperSU try installing it in systemmode after fresh install or switch to ext4.
Click to expand...
Click to collapse
Wut... I've been using SuperSU with f2fs for the last couple months and haven't had any issues
sidhg said:
I know it's a known bug that if the data partition is in f2fs.
And if anyone roots any custom rom which doesn't have internal root.
Device unroot itself after sometime after reboot.
Is there any workaround for this?
I'm using tesla 3.4 beta and pico open gapps and supersu 2.79
Click to expand...
Click to collapse
Use system mode super su, sr4 worked great for me for months on arter97 rom all f2fs
aadityarulez said:
SuperSU is not compatible with f2fs. Try phh suprsuser, it worls.
If you still want SuperSU try installing it in systemmode after fresh install or switch to ext4.
Click to expand...
Click to collapse
Dupleshwar said:
Use system mode super su, sr4 worked great for me for months on arter97 rom all f2fs
Click to expand...
Click to collapse
Well, system mode supersu seems to work fine.
Thank you guys
Edit : Nope root is gone again this bug is really annoying
sidhg said:
Well, system mode supersu seems to work fine.
Thank you guys
Click to expand...
Click to collapse
Happy to help. Cheers.
sidhg said:
Well, system mode supersu seems to work fine.
Thank you guys
Edit : Nope root is gone again this bug is really annoying
Click to expand...
Click to collapse
Could you try with phh superuser ?
aadityarulez said:
Could you try with phh superuser ?
Click to expand...
Click to collapse
I dirty Flashed the Rom.. Then Flashed phh superuser
It solved the issue
Thanks
Phh works nicely, there are still a few issues with mount, but they will get fixed eventually. But I found myself going back to exfat, prefer SuperSU for now.
I recently sideloaded an OTA update which caused me to lose root and TWRP. I reinstalled TWRP but SuperSU will not work. I have the correct one zip. I tried many times and it won't work. When I open the SuperSU app it says there are no SU binaries installed. Any advice? I really don't understand.
Abbieru said:
I recently sideloaded an OTA update which caused me to lose root and TWRP. I reinstalled TWRP but SuperSU will not work. I have the correct one zip. I tried many times and it won't work. When I open the SuperSU app it says there are no SU binaries installed. Any advice? I really don't understand.
Click to expand...
Click to collapse
Your flashing 2.79 sr3 and TWRP rc1
mac796 said:
Your flashing 2.79 sr3 and TWRP rc1
Click to expand...
Click to collapse
I did.
Abbieru said:
I recently sideloaded an OTA update which caused me to lose root and TWRP. I reinstalled TWRP but SuperSU will not work. I have the correct one zip. I tried many times and it won't work. When I open the SuperSU app it says there are no SU binaries installed. Any advice? I really don't understand.
Click to expand...
Click to collapse
Abbieru said:
I did.
Click to expand...
Click to collapse
Do you have pw set up. Is TWRP asking for it when you boot to recovery are u on a custom ROM
mac796 said:
Do you have pw set up. Is TWRP asking for it when you boot to recovery are u on a custom ROM
Click to expand...
Click to collapse
Yes it asks for the password. I don't use a custom ROM
Abbieru said:
Yes it asks for the password. I don't use a custom ROM
Click to expand...
Click to collapse
Have you used that su download before. Maybe you got corrupted download. I'm not on feb yet. Maybe that has something to do with it
Try sr2. Had the same on latest tipsy sr3 didn't work. Sr2 works.
Abbieru said:
I recently sideloaded an OTA update which caused me to lose root and TWRP. I reinstalled TWRP but SuperSU will not work. I have the correct one zip. I tried many times and it won't work. When I open the SuperSU app it says there are no SU binaries installed. Any advice? I really don't understand.
Click to expand...
Click to collapse
Can you send a screen shot of what you are flashing? The actual files
Abbieru said:
Yes it asks for the password. I don't use a custom ROM
Click to expand...
Click to collapse
Last time I got in a jam I flashed boot image to a and b and that should bring your stock recovery back. Then boot TWRP again and install TWRP then boot to system once, then flash su. I think that's what I did.
Hello, just decided to unlock the bootloader and root the device. However, after I rooted the device with SuperSU. I can't open the camera anymore. It crashes every time I take a picture and it doesn't save the picture I took. Is this a problem or am I using the wrong method of rooting?
Edit: Fixed, it was the build.prop permissions all along.
darthbadar said:
Hello, just decided to unlock the bootloader and root the device. However, after I rooted the device with SuperSU. I can't open the camera anymore. It crashes every time I take a picture and it doesn't save the picture I took. Is this a problem or am I using the wrong method of rooting?
Click to expand...
Click to collapse
Try clearing the camera cache and reboot. See if that works.
bonham1988 said:
Try clearing the camera cache and reboot. See if that works.
Click to expand...
Click to collapse
It worked, but just for a while. After that it'll run into the same problems.
darthbadar said:
It worked, but just for a while. After that it'll run into the same problems.
Click to expand...
Click to collapse
Ok that seems weird. Did you root the phone just after unlocking bootloader or you installed your apps after unlocking bootloader and then rooted your phone?
bonham1988 said:
Ok that seems weird. Did you root the phone just after unlocking bootloader or you installed your apps after unlocking bootloader and then rooted your phone?
Click to expand...
Click to collapse
I rooted the phone after unlocking the bootloader, then installed my apps. After noticing the problems I tried a clean flash and then root. Still got the same results.
darthbadar said:
I rooted the phone after unlocking the bootloader, then installed my apps. After noticing the problems I tried a clean flash and then root. Still got the same results.
Click to expand...
Click to collapse
Try rooting again after flashing this new version of twrp i had same issues this fixed my camera
https://forum.xda-developers.com/oneplus-3/oneplus-3--3t-cross-device-development/recovery-official-twrp-oneplus-3-3t-t3543391
ironclad1911 said:
Try rooting again after flashing this new version of twrp i had same issues this fixed my camera
https://forum.xda-developers.com/on.../recovery-official-twrp-oneplus-3-3t-t3543391
Click to expand...
Click to collapse
Twrp version 3.0.4-1 right? I'm using that version to flash the SuperSU and magisk to find out if magisk causes the same problems or not. Or are there another version of twrp?
darthbadar said:
Twrp version 3.0.4-1 right? I'm using that version to flash the SuperSU and magisk to find out if magisk causes the same problems or not. Or are there another version of twrp?
Click to expand...
Click to collapse
This is the latest unreleased version...idk about magisk i dont use it but this twrp latest supersu and ob12 are working together for me
ironclad1911 said:
This is the latest unreleased version...idk about magisk i dont use it but this twrp latest supersu and ob12 are working together for me
Click to expand...
Click to collapse
Hmm still got crashes from when using the camera. I'm going to go back to 4.0.3 and see if it still causes problems for me. I'll be updating.
Edit: I've found out that the cause of the camera crashing is because I've edited the build.prop file to force Google Assistant and it gave the build.prop file wrong permissions causing the device to crash. I've restored the original build.prop permissions and the camera worked again
darthbadar said:
Hmm still got crashes from when using the camera. I'm going to go back to 4.0.3 and see if it still causes problems for me. I'll be updating.
Edit: I've found out that the cause of the camera crashing is because I've edited the build.prop file to force Google Assistant and it gave the build.prop file wrong permissions causing the device to crash. I've restored the original build.prop permissions and the camera worked again
Click to expand...
Click to collapse
Good Job!!