Hey all,
Tried flashing SuperSU 2.78, and phone went boot-looping.
Tried flashing SuperSU 2.46, and this time it got stuck on the white screen, and booting was not possible (had to wait until the battery drained out).
I'd appreciate it if anyone could explain why this happens, and of course a version which should work.
Thanks!
* Firmware 3.35.401.32
* TWRP twrp-3.0.2-0
I can't explain why it happens. Try 2.66 first and if that doesn't work then try 2.65.
I have a similar problem.
Installed 2.78 and 2.76 and it went to boot-loop. 2.46 rebooted successfully but no root access.
Sunshine says it cannot get temproot access. Please advice.
It's been stated so many times and there seem to be about 1000 threads here in the Q&A section which all deal with this topic. Is there a specific reason why nobody uses the search function?
Firmware versions up to 2.x require you to use SuperSU 2.49. Firmware 3.x on the other hand only works with SuperSU 2.64 or 2.65. (I'm talking about the flashable zips. Updating via play store afterwards is absolutely no problem.)
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
It's been stated so many times and there seem to be about 1000 threads here in the Q&A section which all deal with this topic. Is there a specific reason why nobody uses the search function?
Firmware versions up to 2.x require you to use SuperSU 2.49. Firmware 3.x on the other hand only works with SuperSU 2.64 or 2.65. (I'm talking about the flashable zips. Updating via play store afterwards is absolutely no problem.)
Click to expand...
Click to collapse
Thanks!
I really did try and search for a solution. Honestly! Maybe I need to work on my searching skills.
I used 2.76 and sunshine ,twrp 3.02 hima , I had no problems at all ??
Related
I had a rooted M8, however something was going wrong as it constantly rebooted. So I did a factory reset and that fixed the problem. However now it won't root for some reason. I have TWRP recovery and flashed the root file however when I do root checker it stated that I do not have root access. Anyone know what's wrong?
ILowry282 said:
I had a rooted M8, however something was going wrong as it constantly rebooted. So I did a factory reset and that fixed the problem. However now it won't root for some reason. I have TWRP recovery and flashed the root file however when I do root checker it stated that I do not have root access. Anyone know what's wrong?
Click to expand...
Click to collapse
Have you tried flashing a different version of the root program? I assume it's SuperSU (From Chainfire) ? It still gave me root access on 1.94 I saw that he already updated to version 2.00 by now.
Perhaps try a different version and see what it does.
Thread to Chainfire's SuperSU
BerndM14 said:
Have you tried flashing a different version of the root program? I assume it's SuperSU (From Chainfire) ? It still gave me root access on 1.94 I saw that he already updated to version 2.00 by now.
Perhaps try a different version and see what it does.
Thread to Chainfire's SuperSU
Click to expand...
Click to collapse
I used SuperSU. Should I try Super User?
Just use the normal install method from Google play. Twrp auto Installs the su binary the first time it is booted in to. Then just update super su via play store.
ashyx said:
Just use the normal install method from Google play. Twrp auto Installs the su binary the first time it is booted in to. Then just update super su via play store.
Click to expand...
Click to collapse
What is the install method via google play? I've only ever flashed a zip file.
ILowry282 said:
What is the install method via google play? I've only ever flashed a zip file.
Click to expand...
Click to collapse
Once booted into the os you should see the super su app. Go to play store and update it.
hello, i am new here and had to create an account because all of the threads related to my issue have yet to resolve my problems!
i have an htc on m8 version 5.0.1 and i unlocked my bootloader, flashed twrp, and proceeded to root. However, the first attempt gave me an error once i clicked on supersu that said there is no su binary installed and supersu cannot install it. this is a problem. So i researched and downloaded the updated version of supersu v2.46, still no luck! everything ran smooth up until this point and im extremely confused as to why it wont work! please help!!!
delapimpage said:
hello, i am new here and had to create an account because all of the threads related to my issue have yet to resolve my problems!
i have an htc on m8 version 5.0.1 and i unlocked my bootloader, flashed twrp, and proceeded to root. However, the first attempt gave me an error once i clicked on supersu that said there is no su binary installed and supersu cannot install it. this is a problem. So i researched and downloaded the updated version of supersu v2.46, still no luck! everything ran smooth up until this point and im extremely confused as to why it wont work! please help!!!
Click to expand...
Click to collapse
see http://forum.xda-developers.com/htc-one-m8/help/help-thread-htc-one-m8-questions-t2897783
[UPDATED][INDEX][REPO][AIO] HTC ONE (M8) - ROMs | Kernels | MODs | Recoveries by KidCarter93
This thread will be moved to One (M8) Q&A, Help & Troubleshooting
delapimpage said:
hello, i am new here and had to create an account because all of the threads related to my issue have yet to resolve my problems!
i have an htc on m8 version 5.0.1 and i unlocked my bootloader, flashed twrp, and proceeded to root. However, the first attempt gave me an error once i clicked on supersu that said there is no su binary installed and supersu cannot install it. this is a problem. So i researched and downloaded the updated version of supersu v2.46, still no luck! everything ran smooth up until this point and im extremely confused as to why it wont work! please help!!!
Click to expand...
Click to collapse
Did this ever get resolved? I am having the exact same issue! :crying:
What ROM are you using? it should work fine :/ did you actually flash SuperSu zip? instead of installing just some apk file for the app it self? because the zip comes with the binary.
Hi, I can't seem to be able to root my phone since I upgraded to Marshmallow.
Been using TWRP 2.8.7.0 and SuperSU v2.46. I get stuck on the HTC logo at boot after installing superSU.
Any ideas?
On Marshmallow you could try to use the beta 2.66. This version has a nice to accomplish systemless root, were root is written to boot.img and /data instead of system partition.
As I'm on Maximus HD which comes prerooted with v2.65 I can tell that this version works flawlessly on Marshmallow devices.
Send by the swarm intelligence of my coffee machine (AKA HTC One M9).
Freaksterz said:
Hi, I can't seem to be able to root my phone since I upgraded to Marshmallow.
Been using TWRP 2.8.7.0 and SuperSU v2.46. I get stuck on the HTC logo at boot after installing superSU.
Click to expand...
Click to collapse
Root on Marshmallow has been discussed quite a bit on this forum.
SuperSU 2.46 won't work, no way. Its not updated for MM.
SuperSU 2.51 Beta or higher versions should work. They will give you the option of systemless or traditional root methods (read up on existing threads to learn the difference/benefits of each).
redpoint73 said:
Root on Marshmallow has been discussed quite a bit on this forum.
SuperSU 2.46 won't work, no way. Its not updated for MM.
SuperSU 2.51 Beta or higher versions should work. They will give you the option of systemless or traditional root methods (read up on existing threads to learn the difference/benefits of each).
Click to expand...
Click to collapse
So let's say I'm in marshmallow with trwp 3.0.0
Which version of supersu should I flash and which MOD should I choose ?
ofir_a said:
Which version of supersu should I flash and which MOD should I choose ?
Click to expand...
Click to collapse
SuperSU 2.51 or later will work with MM, as I've already stated. As a number of updated SuperSU versions have been released since that post, so newer may/may not be better. Version 2.65 is the most recent to be labelled STABLE, so if it were me, I'd probably go with that.
The difference between systemless root versus "traditional" root is discussed in a number of places. For instance, you can look in the SuperSU forum section here on XDA. But here is some explanation of the "systemless" approach: http://forum.xda-developers.com/showpost.php?p=63197935
Alternately, I believe (although not sure) that TWRP 3.0.0.0 is updated to properly root MM on our device, using the built-in root option in TWRP. As always, make a TWRP backup before trying any of the above methods, just in case anything goes wrong!
redpoint73 said:
SuperSU 2.51 or later will work with MM, as I've already stated. As a number of updated SuperSU versions have been released since that post, so newer may/may not be better. Version 2.65 is the most recent to be labelled STABLE, so if it were me, I'd probably go with that.
The difference between systemless root versus "traditional" root is discussed in a number of places. For instance, you can look in the SuperSU forum section here on XDA. But here is some explanation of the "systemless" approach: http://forum.xda-developers.com/showpost.php?p=63197935
Alternately, I believe (although not sure) that TWRP 3.0.0.0 is updated to properly root MM on our device, using the built-in root option in TWRP. As always, make a TWRP backup before trying any of the above methods, just in case anything goes wrong!
Click to expand...
Click to collapse
Thanks a lot
redpoint73 said:
Root on Marshmallow has been discussed quite a bit on this forum.
SuperSU 2.46 won't work, no way. Its not updated for MM.
SuperSU 2.51 Beta or higher versions should work. They will give you the option of systemless or traditional root methods (read up on existing threads to learn the difference/benefits of each).
Click to expand...
Click to collapse
Thanks for the insights. I was trying to root my m8 after almost 2 years, I didn't know about the complexity of the SuperSu for marshmellow, finally figured that I flashed 2.37 version of SuperSu. No matter what I do I am stuck in the htc logo bootloop. I'm in desperation but I can't flash the updated version of SuperSu if it's not in the internal memory(or is there any way). And I can't put that file in the internal memory if i don't have an access to it. How do I go about it? I've been trying to find a solution for the last 4 hours, it's 3 in the morning. Help.
post.ratz said:
I was trying to root my m8 after almost 2 years, I didn't know about the complexity of the SuperSu for marshmellow, finally figured that I flashed 2.37 version of SuperSu.
Click to expand...
Click to collapse
Good rule of thumb, on any Android device, is that the root method almost always changes with major build updates (Lollipop, Marshmallow, etc.). So you always need to research for the most current root method for the specific Android build and the specific device.
As mentioned, you should flash SuperSU 2.51 or higher for MM. SuperSU 2.65 is recommended (latest "stable" version).
post.ratz said:
No matter what I do I am stuck in the htc logo bootloop
Click to expand...
Click to collapse
That statement tells us nothing about what you actually tried, nor the specific result for each attempted method.
post.ratz said:
I'm in desperation but I can't flash the updated version of SuperSu if it's not in the internal memory(or is there any way). And I can't put that file in the internal memory if i don't have an access to it.
Click to expand...
Click to collapse
If you made a TWRP backup before rooting (which you should always do before rooting, for this very reason) just restore the backup.
Otherwise, you can adb push the proper SuperSU file with the phone booted into TWRP recovery.
Or use a card reader connected to your computer, to put the file on a removable MicroSD card (then insert card into phone).
You may or may not also be able to mount internal storage (see it on your computer) while booted into TWRP; either in default MTP mode, or you can try to mount USB storage in the TWRP "Mount" options. But mounting storage in TWRP has always been a bit finicky and inconsistent for me.
redpoint73 said:
Good rule of thumb, on any Android device, is that the root method almost always changes with major build updates (Lollipop, Marshmallow, etc.). So you always need to research for the most current root method for the specific Android build and the specific device.
As mentioned, you should flash SuperSU 2.51 or higher for MM. SuperSU 2.65 is recommended (latest "stable" version).
That statement tells us nothing about what you actually tried, nor the specific result for each attempted method.
If you made a TWRP backup before rooting (which you should always do before rooting, for this very reason) just restore the backup.
Otherwise, you can adb push the proper SuperSU file with the phone booted into TWRP recovery.
Or use a card reader connected to your computer, to put the file on a removable MicroSD card (then insert card into phone).
You may or may not also be able to mount internal storage (see it on your computer) while booted into TWRP; either in default MTP mode, or you can try to mount USB storage in the TWRP "Mount" options. But mounting storage in TWRP has always been a bit finicky and inconsistent for me.
Click to expand...
Click to collapse
Hey, thanks for the reply. It probably was too late at night and my mind had stopped functioning, a little common sense was all that was needed. The bootloop had only occurred because of me flashing the lower version of SuperSu. The good rule of thumb, forgive my lack of knowledge, I had no idea that a rooting of a device may change with the upgraded version of the OS. Woke up, took my external memory card out, transferred the SuperSu 2.65 on it and later flashed it though recovery.
Rest assured, I'll never go for a phone that does not have expandable storage option.
Thanks
Was rooted in past on Lollipop. Tried to upgrade to Marshmallow using the 3.38.502.12 file in this thread:
http://forum.xda-developers.com/att...ficial-att-3-38-502-12-rom-7-01-2016-t3409354
Somehow got completely bricked, but I found the full RUU exe file for AT&T using Google which rebuilt everything, with full (ugh) bloat. Anyway I'm now back up & running with Marshmallow 6.0 and latest TWRP 3.0.2-0 is successfully flashed. The weird thing is that it does NOT give me the option to root & install SuperSu. I did make sure the "mount system read only" option was unchecked. I also tried installing SuperSU from the app store, but it reports required binary is missing. Is there any way to force TWRP to do it's root thing? It apparently thinks the phone is already done when it's not.
Hope all this mumbo jumbo makes sense. Thanks!
~Vol
Vol4Ever said:
Was rooted in past on Lollipop. Tried to upgrade to Marshmallow using the 3.38.502.12 file in this thread:
http://forum.xda-developers.com/att...ficial-att-3-38-502-12-rom-7-01-2016-t3409354
Somehow got completely bricked, but I found the full RUU exe file for AT&T using Google which rebuilt everything, with full (ugh) bloat. Anyway I'm now back up & running with Marshmallow 6.0 and latest TWRP 3.0.2-0 is successfully flashed. The weird thing is that it does NOT give me the option to root & install SuperSu. I did make sure the "mount system read only" option was unchecked. I also tried installing SuperSU from the app store, but it reports required binary is missing. Is there any way to force TWRP to do it's root thing? It apparently thinks the phone is already done when it's not.
Hope all this mumbo jumbo makes sense. Thanks!
~Vol
Click to expand...
Click to collapse
You're doing better then me. From what I've read it looks like you need the supersu.zip, but I think you know that. If you haven't try to install the supersu.zip maybe you'll be able to do it without bootloop (I need to make my post). A new version came out 9.15.2016.
Just flash SuperSu 2.64 or 2.65 using TWRP and that's it. Look for the link using google. Ohter versions cause bootloop.
I tried to root my one m9 using twrp-3.0.2-0-hima and the zip file of SuperSU v2.79.
After flashing SuperSU and pressing reboot in the recovery, the phone started to bootloop.
I tried a dalvik clear and a data wipe.
I can still get into the recovery bootloader and download mode.
The phone is the Taiwanese variant and was fully updated if that helps.
Sorry if this seems simple, but I really don't want to mess it up more. Any help is appreciated!
iateapietod said:
I tried to root my one m9 using twrp-3.0.2-0-hima and the zip file of SuperSU v2.79.
After flashing SuperSU and pressing reboot in the recovery, the phone started to bootloop.
I tried a dalvik clear and a data wipe.
I can still get into the recovery bootloader and download mode.
The phone is the Taiwanese variant and was fully updated if that helps.
Sorry if this seems simple, but I really don't want to mess it up more. Any help is appreciated!
Click to expand...
Click to collapse
Try flashing SuperSu 2.79 SR1 - the M9 should accept that without issue.
computerslayer said:
Try flashing SuperSu 2.79 SR1 - the M9 should accept that without issue.
Click to expand...
Click to collapse
The only versions I can find are 2.79 SR2 and the "stable"
Neither are working. Could flashing the latest stock on the htc website or installing a different rom help?
The HTC site says that installing it may damage the device if you modified the device software or Bootloader is that just an obligatory warning or is it serious?
If you are rooting android 6.0 you need twrp 2.9.0.1 and supersu 2.65. You can find them here: https://drive.google.com/folderview?id=0B4vTiHTBB629QmxGTkpyZWlCR28
If you are rooting 6.0.1 you need twrp 3.x and supersu 2.7
Beamed in by telepathy.
According to download mode the OS is 3.36.709.3
I can't tell if that's 6.0 or 6.0.1 even with google.
If it is 6.0, can I just put the twrp file in the adb platform tools folder and flash like before or do I have to do anything different?
shivadow said:
If you are rooting android 6.0 you need twrp 2.9.0.1 and supersu 2.65. You can find them here: https://drive.google.com/folderview?id=0B4vTiHTBB629QmxGTkpyZWlCR28
If you are rooting 6.0.1 you need twrp 3.x and supersu 2.7
Beamed in by telepathy.
Click to expand...
Click to collapse
That is not correct. As already written in a different thread some days ago: captain throwback deleted twrp 2.9 on purpose. So please stop recommending that version.
The currently recommended versions of twrp are 2.8.7.1 for firmware 1.x and 2.x of the M9 and 3.0.3-0 for firmware 3.x and above. Both can be found in the TWRP thread in the original android development section.
And supersu 2.79 sr1 is just working fine with the stock rom of the m9. There you go: http://download.chainfire.eu/1017/SuperSU/SR1-SuperSU-v2.79-SR1-20161221223537.zip
Edit @iateapietod: You need to reflash the stock boot image of your firmware. This can for example be done by restoring it via one of the backups in my thread. Follow the instructions in the twrp section II with the following exceptions: don't wipe anything via TWRP and only restore "boot" and not "system" or "recovery". After that your rom should be booting, again.
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
That is not correct. As already written in a different thread some days ago: captain throwback deleted twrp 2.9 on purpose. So please stop recommending that version.
The currently recommended versions of twrp are 2.8.7.1 for firmware 1.x and 2.x of the M9 and 3.0.3-0 for firmware 3.x and above. Both can be found in the TWRP thread in the original android development section.
And supersu 2.79 sr1 is just working fine with the stock rom of the m9. There you go: http://download.chainfire.eu/1017/SuperSU/SR1-SuperSU-v2.79-SR1-20161221223537.zip
Edit @iateapietod: You need to reflash the stock boot image of your firmware. This can for example be done by restoring it via one of the backups in my thread. Follow the instructions in the twrp section II with the following exceptions: don't wipe anything via TWRP and only restore "boot" and not "system" or "recovery". After that your rom should be booting, again.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
Okay, I completed that and redid TWRP and superSU, now though the SuperSU app is giving the error that its binaries are not installed and it cannot install them.
What do I need to do about that?
Just follow flippy, he knows everything..
Twrp 2.9.0.1 works fine for me since day 1 so i think the issues might not actually be this version of twrp.
Supersu 2.65 works peachy too, no need to use any other.
BUT, everyone seems to think otherwise but I ain't no sheep and my phone works great rooted and s-off. It has done since the day I done it so I have no reason NOT to recommend the files I'm CURRENTLY using and have been for nearly 12 months.
So, smarty pants. Su binaries won't install and I don't know how to solve it. I have no place in this thread now.
Beamed in by telepathy.
iateapietod said:
Okay, I completed that and redid TWRP and superSU, now though the SuperSU app is giving the error that its binaries are not installed and it cannot install them.
What do I need to do about that?
Click to expand...
Click to collapse
Please reflash the boot.img and then flash SuperSU 2.65. It was the latest compatible version before 2.79 sr1 got released. You can update it via the play store, afterwards. It looks like some M9s have issues with 2.79 sr1. You're the second person that reports problems.
shivadow said:
Just follow flippy, he knows everything..
Twrp 2.9.0.1 works fine for me since day 1 so i think the issues might not actually be this version of twrp.
Supersu 2.65 works peachy too, no need to use any other.
BUT, everyone seems to think otherwise but I ain't no sheep and my phone works great rooted and s-off. It has done since the day I done it so I have no reason NOT to recommend the files I'm CURRENTLY using and have been for nearly 12 months.
So, smarty pants. Su binaries won't install and I don't know how to solve it. I have no place in this thread now.
Beamed in by telepathy.
Click to expand...
Click to collapse
I don't know everything. And I apologize for my harsh words but the thing is that I simply don't understand why someone should recommend a version of a custom recovery that got deleted by the dev who created it so that no one is able to download it anymore. It might be working for you but if that version could be used without issues then you would still be able to download it from captain throwback's thread. (I'm not even sure whether you're allowed to re-upload the old TWRP version without captain throwback's permission.) I'm only repeating the recommendations that got posted in captain throwback's thread and I don't think that anyone else than the dev of the custom recovery himself knows better which version is recommended for this phone and which not.
The boot.img is what you said to backup in the one m9 guide correct? Just wanted to be safe.
iateapietod said:
The boot.img is what you said to backup in the one m9 guide correct? Just wanted to be safe.
Click to expand...
Click to collapse
Just restore the backup you restored when your phone wasn't booting after you had flashed SuperSU for the first time. Don't forget the exceptions that I posted at that time.
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
Just restore the backup you restored when your phone wasn't booting after you had flashed SuperSU for the first time. Don't forget the exceptions that I posted at that time.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
Thanks, will-do!
Flippy498 said:
That is not correct. As already written in a different thread some days ago: captain throwback deleted twrp 2.9 on purpose. So please stop recommending that version.
The currently recommended versions of twrp are 2.8.7.1 for firmware 1.x and 2.x of the M9 and 3.0.3-0 for firmware 3.x and above. Both can be found in the TWRP thread in the original android development section.
And supersu 2.79 sr1 is just working fine with the stock rom of the m9. There you go: http://download.chainfire.eu/1017/SuperSU/SR1-SuperSU-v2.79-SR1-20161221223537.zip
Edit @iateapietod: You need to reflash the stock boot image of your firmware. This can for example be done by restoring it via one of the backups in my thread. Follow the instructions in the twrp section II with the following exceptions: don't wipe anything via TWRP and only restore "boot" and not "system" or "recovery". After that your rom should be booting, again.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
I was being sarcastic..
When i rooted my m9 i followed the common guides which all recommended twrp 2.8.7.1 and that failed to boot for me so I went up to 2.9.0.1 and that worked. The next thing I know is it got deleted by the dev for no known reason and another version was immediately put in its place.
Rather than being ocd and updating immediately i decided to wait. Which was a good idea because at the time i was seeing quite a lot of problems relating to rooting with said higher version of twrp. I have stuck with it since.
A flea in your ear about "copyright infringement". Once you release something into the wild, especially under the gnu license, you lose all rights of control but you retain the rights to "design and ownership". I can keep, use and distribute 2.9.0.1 under the gnu license, as it is written in linux/unix, but I may not use it in my own projects or claim it as mine.
Beamed in by telepathy.
To settle this issue definitively it might be worth asking Captain Throwback why 2.9.0.1 was taken down, or searching the thread for discussions about potential issues. But as previously mentioned, the official thread's FAQ (#2) recommends using the 2.8.7.x version for pre-Marshmallow firmware and the latest 3.x.x.x version for post-Marshmallow firmware.
As one who has done so more than a few times, I can testify that it's both embarrassing and potentially damaging to recommend faulty software or advice. I have been grateful for the correction more experienced members have offered, though it's humbling every time. For the sake of helping other users, especially new ones, it's good to be sure that we're offering the best of both.
(For what it's worth: From what I can tell of the conversation in the original thread between 2.8.x.x and 3.x.x.x, the 2.9.x.x series was built primarily to test decryption of the M9. When 3.0.0.1 came out, it supported AOSP decryption, along with the updates that came with 3.0.0.0 (like flashing <4GB zip files). I imagine that the 2.9.x.x series was discontinued due to the success of the 3.x.x.x release. And of course, 3.0.3-0 now supports decryption stock Sense.)