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..
If I upgrade to 7.0 on my nexus 5x, will i be able to install twrp as i normally would through fastboot?
You need to decrypt the phone for it to work.
Hmm anyone got the 7.0 recovery? I installed it thinking it would work but I want to keep the system encrypted. Does the stock 7.0 recovery mount system? I want to mod my build.prop dpi.
trollyphysicist said:
If I upgrade to 7.0 on my nexus 5x, will i be able to install twrp as i normally would through fastboot?
Click to expand...
Click to collapse
Try TWRP 3.0.2-1, should work properly.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Try TWRP 3.0.2-1, should work properly.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I just tried 3.0.2-1, and it worked. Before that, 3.0.2-0 also got stuck at the splash screen. However, I wasn't able to root. I tried installing SU via TWRP, but it didn't successfully root.
pkadavid said:
I just tried 3.0.2-1, and it worked. Before that, 3.0.2-0 also got stuck at the splash screen. However, I wasn't able to root. I tried installing SU via TWRP, but it didn't successfully root.
Click to expand...
Click to collapse
I had no issues obtaining root with the new twrp on an encrypted phone.
Am I the only one who encounters the flasing of recovery not sticking? After system reboot, then going back to recovery, it reverts to stock.
legendarren said:
Am I the only one who encounters the flasing of recovery not sticking? After system reboot, then going back to recovery, it reverts to stock.
Click to expand...
Click to collapse
Flash twrp, while still in bootloader volume down to reboot bootloader, hit the power button, volume down to reboot recovery, hit the power button. Twrp should stick now.
Sent from my Nexus 5X using Tapatalk
PiousInquisitor said:
Flash twrp, while still in bootloader volume down to reboot bootloader, hit the power button, volume down to reboot recovery, hit the power button. Twrp should stick now.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Thanks, man. But still TWRP still doesn't stick after system reboot.
legendarren said:
Thanks, man. But still TWRP still doesn't stick after system reboot.
Click to expand...
Click to collapse
If you decrypt it first by flashing the modified boot.img, and then flash recovery and reboot it should stick and work right? Can you kindly describe your steps?
Vanschtezla said:
If you decrypt it first by flashing the modified boot.img, and then flash recovery and reboot it should stick and work right? Can you kindly describe your steps?
Click to expand...
Click to collapse
Yes, I forgot about decrypting. It works fine now, thanks!!
legendarren said:
Yes, I forgot about decrypting. It works fine now, thanks!!
Click to expand...
Click to collapse
No problem mate ??
Vanschtezla said:
No problem mate ??
Click to expand...
Click to collapse
Which boot IMG did you use to decrypt the final release of n?
kevtrysmoddin said:
Which boot IMG did you use to decrypt the final release of n?
Click to expand...
Click to collapse
In my case I updated mine from DP5. I had my DP5 decrypted and rooted and update it using the flashfire app to flash the ota. I don't think any of the existing modified boot.img will work on the final release yet idk mate.
Vanschtezla said:
In my case I updated mine from DP5. I had my DP5 decrypted and rooted and update it using the flashfire app to flash the ota. I don't think any of the existing modified boot.img will work on the final release yet idk mate.
Click to expand...
Click to collapse
No probs
trollyphysicist said:
If I upgrade to 7.0 on my nexus 5x, will i be able to install twrp as i normally would through fastboot?
Click to expand...
Click to collapse
Just installed twrp and seeing if flashign super su stuck or not... Have to wait for modified boot images to decrypt, though
---------- Post added at 10:25 AM ---------- Previous post was at 10:14 AM ----------
trollyphysicist said:
If I upgrade to 7.0 on my nexus 5x, will i be able to install twrp as i normally would through fastboot?
Click to expand...
Click to collapse
Update-phone is decrypted after installing twrp, wiping userdate, rebooting twrp, flashing latest super su, rebooting
eggman618 said:
Hmm anyone got the 7.0 recovery? I installed it thinking it would work but I want to keep the system encrypted. Does the stock 7.0 recovery mount system? I want to mod my build.prop dpi.
Click to expand...
Click to collapse
3.0.2-1 TWRP that got released soon after I posted fixed any hanging issues.
eggman618 said:
3.0.2-1 TWRP that got released soon after I posted fixed any hanging issues.
Click to expand...
Click to collapse
-1 installs, but two issues if you're encrypted:
1) TWRP doesn't stick. After a restart, you won't be able to get back into TWRP and need to reflash it.
2) Installing SU via TWRP doesn't work. It runs into an error if you read the responses during the flash in TWRP.
We'll just have to be patient until the devs do their magic on the encrypted version.
pkadavid said:
-1 installs, but two issues if you're encrypted:
1) TWRP doesn't stick. After a restart, you won't be able to get back into TWRP and need to reflash it.
2) Installing SU via TWRP doesn't work. It runs into an error if you read the responses during the flash in TWRP.
We'll just have to be patient until the devs do their magic on the encrypted version.
Click to expand...
Click to collapse
If you root using phh's superuser and magisk, TWRP will stick. His solution also allows you to use Android Pay with root, albeit with a little hoop-jumping
http://forum.xda-developers.com/android/software/mod-magisk-v1-universal-systemless-t3432382
I had the twrp not sticking issue in the past. What has worked is to boot twrp, not flash it, then flash SU. Then boot back into the bootloader and flash twrp.
Sent from my Nexus 9 using XDA-Developers mobile app
There is no way to flash supersu on my phone on any rom, on freedomos rom when i select install supersu doesnt work with neither elementalx or stock patched kernel, i tried flashing stock unpatched kernel and then supersu neither that work, it always comes to boot image patcher and then says failure aborting, i had the same problem with other roms, can someone tell me whats the problem ?
Flash modded twrp http://forum.xda-developers.com/devdb/project/dl/?id=21065
Credits to @ eng.stk for this. I had the same issue.
ungeeked said:
Flash modded twrp http://forum.xda-developers.com/devdb/project/dl/?id=21065
Credits to @ eng.stk for this. I had the same issue.
Click to expand...
Click to collapse
Can I use this recovery for every rom in future or I have to go back to official one?
ach3fck said:
Can I use this recovery for every rom in future or I have to go back to official one?
Click to expand...
Click to collapse
No need to go back to official
ungeeked said:
No need to go back to official
Click to expand...
Click to collapse
Ok thanks, sorry to bother you, but should I flash the ROM again via Aroma or I should just flash SuperSu?
Just flash SuperSU. That should do it
Flashed SuperSU and got stuck in a bootloop, did a clean flash again and it worked, thanks a lot!
And now this, f*ck, maybe it could be because I restored backed up data partition, will try to do a clean flash and let you know.
I had this issue yesterday and fixed it today.
try deleting the su binary in twrp.
goto: /data/system/xbin
delete su
flash your SuperSU.zip again.
worked for me, because i had an systemless supersu installed, but an old su file in xbin.
Hi dudes! Im trying to find a way to install Monthly Updates without loose the root and the custom recovery, some body can tell me how? Because im really want update to Oreo but i want be root user and dont have to make a clean install system every month... exist the way? Please help.... And Thanks!
What I do is flash all the updated partition images individually using "fastboot flash", then let it boot and settle for a few minutes (at the very least until the "performing updates" notification completes).
I then reboot into bootloader and from there boot into TWRP (without installing it) using "fastboot boot twrp.img" and then reinstall Magisk zip. None of Magisk's settings or modules are lost by doing it this way.
If you uninstall Magisk before updating the system, you risk losing its settings.
You can use Flashfire.
nowster said:
What I do is flash all the updated partition images individually using "fastboot flash", then let it boot and settle for a few minutes (at the very least until the "performing updates" notification completes).
I then reboot into bootloader and from there boot into TWRP (without installing it) using "fastboot boot twrp.img" and then reinstall Magisk zip. None of Magisk's settings or modules are lost by doing it this way.
If you uninstall Magisk before updating the system, you risk losing its settings.
Click to expand...
Click to collapse
Okey, but using adb?
fnldstntn said:
You can use Flashfire.
Click to expand...
Click to collapse
How dude? Can you tech me please?
Aijen said:
How dude? Can you tech me please?
Click to expand...
Click to collapse
https://youtu.be/WxWRYnzI1O4
Now it is competible with magisk and if you want magisk instead of supersu on installation process you can disabel the installation of supersu and ad magisk to flash afterwards. you can also use the factory images or full ota zips from googles website.
Yes, you can use TWRP's "Advanced" adb sideload feature to install Magisk zip.
"adb" only works when Android is running (or some recovery images are running). When the phone is in bootloader mode the tool you need is "fastboot".
fnldstntn said:
Now it is competible with magisk and if you want magisk instead of supersu on installation process you can disabel the installation of supersu and ad magisk to flash afterwards. you can also use the factory images or full ota zips from googles website.
Click to expand...
Click to collapse
Thanks a lot! I will tried to do it!
fnldstntn said:
Now it is competible with magisk and if you want magisk instead of supersu on installation process you can disabel the installation of supersu and ad magisk to flash afterwards. you can also use the factory images or full ota zips from googles website.
Click to expand...
Click to collapse
Are you do that method without problems?
Aijen said:
Are you do that method without problems?
Click to expand...
Click to collapse
Yes it worked for me. But if you have twrp make a nandroid backup.
fnldstntn said:
Yes it worked for me. But if you have twrp make a nandroid backup.
Click to expand...
Click to collapse
Another thing....the last. Did you maintain the Custom Recovery or Flash it again?
fnldstntn said:
https://youtu.be/WxWRYnzI1O4
Now it is competible with magisk and if you want magisk instead of supersu on installation process you can disabel the installation of supersu and ad magisk to flash afterwards. you can also use the factory images or full ota zips from googles website.
Click to expand...
Click to collapse
dude! one last need reflash Magisk every time the OTA comes or Magisk survival the OTA flash with Magisk? THANKS A LOT WORKS!!!!
Aijen said:
Another thing....the last. Did you maintain the Custom Recovery or Flash it again?
Click to expand...
Click to collapse
i dont remember
Aijen said:
dude! one last need reflash Magisk every time the OTA comes or Magisk survival the OTA flash with Magisk? THANKS A LOT WORKS!!!!
Click to expand...
Click to collapse
i dont know.
Aijen said:
dude! one last need reflash Magisk every time the OTA comes or Magisk survival the OTA flash with Magisk?
Click to expand...
Click to collapse
Magisk embeds itself in the boot partition. This prevents OTA from working.
Replacing the stock recovery partition also stops OTA from working.
The only reliable way to upgrade is by flashing the partitions again from the new factory image zip file, then reinstalling TWRP and Magisk afterwards.
fnldstntn said:
You can use Flashfire.
Click to expand...
Click to collapse
Any ideas what will happen to ElementalX after flashing OTA using Flashfire?
zo1021 said:
Any ideas what will happen to ElementalX after flashing OTA using Flashfire?
Click to expand...
Click to collapse
Using the logic need to reflash it again
nowster said:
Magisk embeds itself in the boot partition. This prevents OTA from working.
Replacing the stock recovery partition also stops OTA from working.
The only reliable way to upgrade is by flashing the partitions again from the new factory image zip file, then reinstalling TWRP and Magisk afterwards.
Click to expand...
Click to collapse
Sounds logic to me....
FlashFire is saying that the update will likely fail because the OTA update is a block level update. Suggestions on how to get around this?