Related
after updating my m8 to lollipop, the device says unroot. software status is still unlocked, I went through the rooting process again,flashed twrp recovery. but cant install anything aa it says device is not rooted.
kalim_714 said:
after updating my m8 to lollipop, the device says unroot. software status is still unlocked, I went through the rooting process again,flashed twrp recovery. but cant install anything aa it says device is not rooted.
Click to expand...
Click to collapse
Hi there,
i have the same Problem.
after ota to 5.01 i rooted my m8 with toolkit , everything goes fine (also perm root and install superSu).
But after restart and automatical apps updates, the supersu app says that su files is missing and there ist no root anymore.
How can i solve that rpoblem? thanks alot
John
John-Wu said:
Hi there,
i have the same Problem.
after ota to 5.01 i rooted my m8 with toolkit , everything goes fine (also perm root and install superSu).
But after restart and automatical apps updates, the supersu app says that su files is missing and there ist no root anymore.
How can i solve that rpoblem? thanks alot
John
Click to expand...
Click to collapse
I've never used a toolkit on my HTC devices, so I can't speak to their effectiveness. Perhaps they need an update to work with Lollipop.
I recommend using TWRP recovery (just because it's the one I used and I know it worked for me. Can't speak to CWM or Philz)
Flash the SuperSU update zip found here: http://download.chainfire.eu/695/SuperSU/
craig0r said:
I've never used a toolkit on my HTC devices, so I can't speak to their effectiveness. Perhaps they need an update to work with Lollipop.
I recommend using TWRP recovery (just because it's the one I used and I know it worked for me. Can't speak to CWM or Philz)
Flash the SuperSU update zip found here: http://download.chainfire.eu/695/SuperSU/
Click to expand...
Click to collapse
hi,
thanks alot. that's it!!
with toolkit i've already installed TWRP and with the updated SuperSu (your link) i've root again.
once again, thanks!
It seems there would be a problem in flashing normal downloaded SU and have to go through the long process of flashing systemless SU after which have to upgrade it.
Is it normal for you guys too?
How come 1+3 bricks after installing normal SU?
b.t.w. personal note: thanks to one of the oneplus rep that was in the euro tour in Rome the TWRP recovery fix worked (sorry forgot your name ). Really appreciate the chat and help out!
No, i downloaded normal su (SuperSU) and then flashed it through TWRP. I don't know which su you are using, but there are loads of us who have installed SuperSU without an issue.
nemexs said:
It seems there would be a problem in flashing normal downloaded SU and have to go through the long process of flashing systemless SU after which have to upgrade it.
Is it normal for you guys too?
How come 1+3 bricks after installing normal SU?
b.t.w. personal note: thanks to one of the oneplus rep that was in the euro tour in Rome the TWRP recovery fix worked (sorry forgot your name ). Really appreciate the chat and help out!
Click to expand...
Click to collapse
You may have the wrong flashable, flashing supersu on the OP3 for me is very quick and painless. Make sure you have the latest from chainfire's website v2.76 at the time of me posting this. : http://download.chainfire.eu/supersu-stable
PS: regular supersu is both systemless and "normal" root it makes a decision during installation determining whether your device can support normal root and if not then it does a systemless boot.img patch.
StykerB said:
You may have the wrong flashable, flashing supersu on the OP3 for me is very quick and painless. Make sure you have the latest from chainfire's website v2.76 at the time of me posting this. : http://download.chainfire.eu/supersu-stable
Click to expand...
Click to collapse
You beat me to pointing him to it. If I can add, there's a dedicated SuperSU thread to seek help if SuperSU causes an issue:
http://forum.xda-developers.com/showthread.php?t=1538053
Highly unlikely but just in case. If you are not sure, there are sufficient number of toolkits out there that can simplify the job for you.
@tropicanapure @StykerB
Have tried them the only way I can flash SU is downloading @ahmed_radaideh 's oneplus3 toolkit and then flashing his SU. Tried the normal version and the problem seems to be present (brick), yes chainfire's su. If I don't want to do full wipe I'd have wipe system and just reflash stock and then systemless su
nemexs said:
@tropicanapure @StykerB
Have tried them the only way I can flash SU is downloading @ahmed_radaideh 's oneplus3 toolkit and then flashing his SU. Tried the normal version and the problem seems to be present (brick), yes chainfire's su. If I don't want to do full wipe I'd have wipe system and just reflash stock and then systemless su
Click to expand...
Click to collapse
Then you may want to check the process y you are using for this.
If I can ask what exactly are you trying to fix? Do you already have SuperSU installed? And you are trying to move to systemless?
Or are you unable to install SuperSU itself? If yes, then you may want to post to the SuperSU thread too.
tropicanapure said:
Then you may want to check the process y you are using for this.
If I can ask what exactly are you trying to fix? Do you already have SuperSU installed? And you are trying to move to systemless?
Or are you unable to install SuperSU itself? If yes, then you may want to post to the SuperSU thread too.
Click to expand...
Click to collapse
I had no problem in installing it systemless, however just wanted to see if everyone else had to go through the same process. It seems not, now I'm trying to find out how come I can't install normally.
nemexs said:
I had no problem in installing it systemless, however just wanted to see if everyone else had to go through the same process. It seems not, now I'm trying to find out how come I can't install normally.
Click to expand...
Click to collapse
You still haven't mentioned the process you use[emoji6]
The process most commonly used via TWRP is to download the zip from the link above and flash it. That's all there is to it.
tropicanapure said:
You still haven't mentioned the process you use[emoji6]
The process most commonly used via TWRP is to download the zip from the link above and flash it. That's all there is to it.
Click to expand...
Click to collapse
my bad, yes I use twrp method 3.0.2 the most recent one, flash stock rom and then flash su
nemexs said:
my bad, yes I use twrp method 3.0.2 the most recent one, flash stock rom and then flash su
Click to expand...
Click to collapse
Assuming your bootloader is already unlocked beforehand, the straight answer to your question is yes, that's how most of us do it.
No problem with flashing SU whatsoever,
and i rather not to use any toolkit to flash either recovery or anything,
fastboot for recovery and recovery for anything else,
Simple, straight and safe
otonieru said:
No problem with flashing SU whatsoever,
and i rather not to use any toolkit to flash either recovery or anything,
fastboot for recovery and recovery for anything else,
Simple, straight and safe
Click to expand...
Click to collapse
doesn't work for me.
Hey guys, I'm fairly new to the android scene when it comes to the rom and rooting side of things so I just have a few questions about Sunshine and the whole process in general. Sorry if this may have already been asked but after a quick search many of the answers to these questions seem to be outdated.
1. Do you need to be rooted in order to use Sunshine?
2. If I do, is there any method to root my phone? I can't seem to find any without paying some money.
The only reason why I would want to root my phone is so I can use Titanium root and back up my data.
3. Do I have the order right?
Use Sunshine (gains S-off/unlocks bootloader)Install a custom recovery (TWRP)Super SU (Does this root my phone?)Install Cyanogenmod
4. If I have the order correct, at what point should I backup my data and when would my data get wiped?
5. And if I'm backing up my data should I back it up to my SD card and remove it, or do something else?
Once again, I'm sorry if most of the answers to these questions seem obvious but this is my first time tampering with my phone so I would appreciate any help!
Ok so a little update, I used sunshine, installed twrp, and tried to flash super su but I got stuck on a bootloop. Any help? I tried wiping the cache/dalvik.
.-. said:
Ok so a little update, I used sunshine, installed twrp, and tried to flash super su but I got stuck on a bootloop. Any help? I tried wiping the cache/dalvik.
Click to expand...
Click to collapse
The latest supersu zip will give you a bootloop. The previous version works fine. I don't have it anymore but you will need to download a rom and flash it.
Flyhalf205 said:
The latest supersu zip will give you a bootloop. The previous version works fine. I don't have it anymore but you will need to download a rom and flash it.
Click to expand...
Click to collapse
Would you be able to drop a link please? or give me version number?
.-. said:
Would you be able to drop a link please? or give me version number?
Click to expand...
Click to collapse
Are you looking for Sense rom or CM?
Sense roms you can find them http://forum.xda-developers.com/verizon-one-m9/development There is a complete stock rom and a few modded versions
CM you can find here. http://forum.xda-developers.com/verizon-one-m9/orig-development/rom-cyanogenmod-13-0-t3339509
CM does lack VoLTE
.-. said:
Ok so a little update, I used sunshine, installed twrp, and tried to flash super su but I got stuck on a bootloop. Any help? I tried wiping the cache/dalvik.
Click to expand...
Click to collapse
This is a common issue, it happened to me too, so I wrote a quick post how to avoid it.
https://forum.xda-developers.com/verizon-one-m9/help/s-offed-unlocked-bootloader-via-t3444629
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.)
I keep having this problem. I just tried both KINGROOT and CF-AUTO ROOT.
After doing this whole process through ODIN. I then try to flash the latest TWRP from their website : dl.twrp.me/jfltetmo/twrp-3.2.0-0-jfltetmo.img.tar.html
Then after that finishes, I try to boot into recovery and it gives me the message: recovery is not seandroid enforcing and just sits there.
I have a tmobile s4.
and I also checked if I am indeed rooted by using an app from the play store to check root and it shows Im rooted.
Any help would be great.
Root isn't needed to flash a twrp.
Tried flashing the latest stock rom and twrp without rooting the phone?
audit13 said:
Root isn't needed to flash a twrp.
Tried flashing the latest stock rom and twrp without rooting the phone?
Click to expand...
Click to collapse
Yup didn't work after trying it all the only thing that did work was SkipSoft Unified Android Toolkit and it was the easiest thing I ever used.
Krappa420 said:
Yup didn't work after trying it all the only thing that did work was SkipSoft Unified Android Toolkit and it was the easiest thing I ever used.
Click to expand...
Click to collapse
I have the exact problem, can you kindly explain in details how you went about it? I already downloaded SkipSoft.
Same issues here, buddy.
I tried to work on solving it out for approximately 8 hours and still no sign of success. Tried to reflash stock OS back on the phone via ODIN and it went successful. Tried CF-Auto-root file and it went through successful. But when it only came to the TWRP file, it went successful onto flashing on ODIN's side, but now something is interfering with the boot up process onto TWRP now. Hopefully there's a alternative towards this issue, since i've been wanting to reflash a Nougat OS onto the device.
Edit: I give credit to @Krappa420 for the mention of "SkipSoft Unified Android Toolkit" because i just installed the program on my laptop now and it went successful. But since i already had other materials pre-installed, some others with ODIN and ADB installed can just download this TWRP version here: https://dl.twrp.me/jfltexx/twrp-2.7.0.0-jfltexx.img.html
Edit #2: Seems that the TWRP version is too old to flash some of the newer OS's, such as nougat itself. Will find a way to update TWRP without breaking the boot up process, like the past attempts
Edit #3: After fiddling with TWRP versions 2.7.0.0 and up, i managed to get it capped up to 3.1.1 any future versions will most likely not work, so you're capped at 3.1.1 Here's the link for flashing it with ODIN: https://dl.twrp.me/jfltexx/twrp-3.1.1-0-jfltexx.img.tar.html
So you twrp 3.1.1 and it will work right
I having the same issue
Thank you
so do i need to install cf-auto root first or the twrp 3.11
what are the steps to install
Thank you for helping a disabled veteran
timj3371 said:
so do i need to install cf-auto root first or the twrp 3.11
what are the steps to install
Thank you for helping a disabled veteran
Click to expand...
Click to collapse
It wouldn't really matter what order you're using.
You can use CF-Auto-Root to root it for you while you have stock recovery still, and after you can flash to TWRP and use a custom recovery afterwards
Or you can flash TWRP first and flash a SuperSU zip file afterwards and it'll give you root while maintaining to have TWRP installed.
But to sum it up, it wouldn't matter what order you choose. Help yourself
Trwp
What version of twrp I need to use
Thank you
timj3371 said:
What version of twrp I need to use
Thank you
Click to expand...
Click to collapse
TWRP version 3.1.1
Thank you for the help I have lineage installed. Wow so fast. How ever when trying to root it I get a error says binary occupied. If I uninstall I get no root available. How do I install root ? Thank you so much
A disabled veteran
timj3371 said:
Thank you for the help I have lineage installed. Wow so fast. How ever when trying to root it I get a error says binary occupied. If I uninstall I get no root available. How do I install root ? Thank you so much
A disabled veteran
Click to expand...
Click to collapse
Before anything, try to install the SuperSU app over on the play store, if it says you're not rooted, you may have to restart the whole process within TWRP and reflash the SuperSU Zip file.
Thank you
Says the binary is occupied in su
Where do I find su zip
Should I use the chain fire auto zip
Thanks
timj3371 said:
Says the binary is occupied in su
Where do I find su zip
Should I use the chain fire auto zip
Thanks
Click to expand...
Click to collapse
Try this one: https://download.chainfire.eu/696/supersu/
If it keeps on persisting, I'll have to find another way
I tried that file and it just sits in booting. I left it be then reinstated the ROM. Still no root its OK tight not to have root
Thank you
timj3371 said:
I tried that file and it just sits in booting. I left it be then reinstated the ROM. Still no root its OK tight not to have root
Thank you
Click to expand...
Click to collapse
Yeah try to re-flash the ROM again but this time flash magisk through TWRP since SuperSU is being trippy on your S4
Thank you for the help
Dummy me I found out from reading other forums you have to go in to tools and enable root after going in to recovery and flash the root file in the extra section.
Every thing works
Thank you so much
Disabled veteran