Help?
jkccl9 said:
Help?
Click to expand...
Click to collapse
Download the zip package and flash with recovery
https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.78-201609011115.zip
Sent from my H60-L04 using XDA Labs
Didn't work, no root app ran and they would just reload
Are you rooted already? Does your SuperSU already work and you just want to update? If yes You could try the apk instead
http://www.androidapksfree.com/apk/supersu-apk-latest-version-download-chainfire/
What firmware are you running on now?!
Having the same error now on latest dev build. I'll let you know if i find a fix
Sent from my H60-L04 using XDA Labs
Try to flash an older version like 2.62 (stable) or the latest 2.78.
Yes. Did that earlier today. Installed version 2.70 direct. Worked fine.
Sent from my H60-L04 using XDA Labs
Related
Is it possible to use goomanager to install TWRP after the device is rooted with cf root?
Sent from my Nexus 5 using xda app-developers app
Yep. That's the easiest way to do it.
Sent from my SGH-M919
nitrogen618 said:
Is it possible to use goomanager to install TWRP after the device is rooted with cf root?
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
Yes, though having a Nexus device, it'd be good for you to learn fastboot/adb. Comes in handy.
Cool. Thanks guys. I guess is this correct?
1. Cf root
2. Goomanager for twrp
Twrp will stick right? I saw some people needing to flash like 6 times before twrp sticks.
Sent from my Nexus 5 using xda app-developers app
nitrogen618 said:
Cool. Thanks guys. I guess is this correct?
1. Cf root
2. Goomanager for twrp
Twrp will stick right? I saw some people needing to flash like 6 times before twrp sticks.
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
As aznk3vi17 says, go the adb fastboot way. You'll be better off in the long run than using a bunch of easy tools. Sooner or later you're going to get yourself into trouble where they'll come in handy.
nitrogen618 said:
Cool. Thanks guys. I guess is this correct?
1. Cf root
2. Goomanager for twrp
Twrp will stick right? I saw some people needing to flash like 6 times before twrp sticks.
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
Yeah but when you download twrp the page go to 403 error.
Thanks guys. I guess I will do it via GooManager.
nitrogen618 said:
Thanks guys. I guess I will do it via GooManager.
Click to expand...
Click to collapse
No you won't. The download page doesn't work.
I'll probably do it later then.
IIRC it's been like that for a week or more. Just do the ADB flash. Or use Flashify. That's just as easy as Goo.
Download the Flashify app, download the TWRP recovery img file to your phone and install with flashify from your phone.
nitrogen618 said:
I'll probably do it later then.
Click to expand...
Click to collapse
Or just fastboot flash the recovery on. It takes 20 seconds tops.
Sent from my Nexus 5
http://techerrata.com/browse/twrp2/hammerhead
I can just download the latest one and flash it with flashify right?
Sent from my Nexus 5 using xda app-developers app
nitrogen618 said:
http://techerrata.com/browse/twrp2/hammerhead
I can just download the latest one and flash it with flashify right?
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
Correct. As long as you have the img file and not zip.
You'll just go in to your downloads and tap it, install with flashify and you're done. Restart the device in fastboot mode and scroll to recovery to make sure it took.
Is it possible to brick devices this way?
Sent from my Nexus 5 using xda app-developers app
nitrogen618 said:
Is it possible to brick devices this way?
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
Just don't use goo manager to flash roms. It's way too easy to find a rom that is not for your device and flash it. I'll use goo to put on the recovery and then remove it from my phone
nitrogen618 said:
Is it possible to brick devices this way?
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
It's possible but not likely. If anything it just won't over write the stock recovery.
when trying to install TWRP with goomanager says 403 error when downloading, why?
---------- Post added at 12:50 PM ---------- Previous post was at 12:46 PM ----------
I'm new in Android and i don't know how install fwrp with other method
Enviado desde mi Nexus 5 mediante Tapatalk
Use flashify. That's what I did.
Sent from my Nexus 5 using xda app-developers app
I don't know do that, how i can do that?I'm very new with Android
For some reason I can't get flashify to work. When I press on the IMG I want to flash it doesn't do anything.
But I also know how to use adb so it's not a huge issue.
Sent from my Nexus 5 using Tapatalk
Hello, Every time i make a backup with cwm i see wrong back update like 1970. How to fix this ?
Update your version of cwm. It's a bug in cwm.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Update your version of cwm. It's a bug in cwm.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I was already using the latest version available .
srujan21 said:
I was already using the latest version available .
Click to expand...
Click to collapse
Are you using 6.0.4.5. I don't use cwm, I use twrp and I know it was fixed in that. It had the same problem for awhile.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Are you using 6.0.4.5. I don't use cwm, I use twrp and I know it was fixed in that. It had the same problem for awhile.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Yes I m using 6.0.4.5 touch version. ohh so you are saying its problem with the recovery and i got nothing to fix that right ?
jd1639 said:
Update your version of cwm. It's a bug in cwm.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Its not a bug. Its a lack of development
No recoveries on any snapdragon 800 device could get the correct time until we understood how the Qualcomm time daemon worked. Once we knew, it was implemented in Philz and TWRP. CWM doesn't bother implementing anything modern. Its a dead recovery.
Sent from my Nexus 5 using Tapatalk
Greetings, I recently lost root on my Nexus 5 because I wanted to switch from supersu to superuser. I uninstall supersu from the app itself. I installed superuser and then tried to download the binaries, but it failed. But my bootloader is still unlocked and I have twrp as my custom recovery.
Sent from my Nexus 5 using XDA Free mobile app
Did you actually uninstall the binaries from SuperSU?
What rom are you on?
Stock ROM Android 5.0
Sent from my Nexus 5 using XDA Free mobile app
Tempest786 said:
Stock ROM Android 5.0
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
As far as I am aware, SuperSU is the only choice.
I tried reinstalling supersu but it doesn't work another thing is that I believe supersu is being detected by some games as a hacking application, once I removed supersu my games started working again. Just wanted to fund out if it really was supersu
Sent from my Nexus 5 using XDA Free mobile app
If you removed the binaries, the only way to get SuperSU is to flash it.
And Is it possible for me to flash superuser? Or am I stuck with supersu? I have no problem with supersu I like it. It's just not compatible with a few games I have.
Sent from my Nexus 5 using XDA Free mobile app
Tempest786 said:
And Is it possible for me to flash superuser? Or am I stuck with supersu? I have no problem with supersu I like it. It's just not compatible with a few games I have.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
AFAIK, SuperSU is the only option.
rootSU said:
As far as I am aware, SuperSU is the only choice.
Click to expand...
Click to collapse
rootSU said:
AFAIK, SuperSU is the only option.
Click to expand...
Click to collapse
I sense your trying to make a point here. lol
OP. You need SSU.
Alrighty, thank you for clearing it up for me.
Sent from my Nexus 5 using XDA Free mobile app
I check everywhere in XDA on how to root 7.1 ROMs so can anybody help me out on how to root 7.1 or do anybody got the link to the superuser.
Sent from my Nexus 5 using Tapatalk
People Really have to learn... pls google superssu, Download 2.78 an Flash through Recovery...
http://download.chainfire.eu/supersu
Flash this zip in recovery
GR0S said:
http://download.chainfire.eu/supersu
Flash this zip in recovery
Click to expand...
Click to collapse
Thanks bro
Sent from my Nexus 5 using Tapatalk
Rezei said:
People Really have to learn... pls google superssu, Download 2.78 an Flash through Recovery...
Click to expand...
Click to collapse
Thanks
Sent from my Nexus 5 using Tapatalk
Does encrypting your phone messes with the supersu?
djevil said:
I check everywhere in XDA on how to root 7.1 ROMs so can anybody help me out on how to root 7.1 or do anybody got the link to the superuser.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Luckily, you have choice on XDA. Besides SuperSU, you can root with Phh's Superuser which is open source.
Nice. Here is the official link:
https://developers.google.com/android/images
Let's find what's new.
Sent from my crosshatch using XDA Labs
Here is the changelog
Sent from my crosshatch using XDA Labs
lollyjay said:
Here is the changelog
Sent from my crosshatch using XDA Labs
Click to expand...
Click to collapse
dope... hopefully this answers a lot of our concerns.
-w to flash.all without losing anything right?
And then twrp and re-root?
masri1987 said:
dope... hopefully this answers a lot of our concerns.
-w to flash.all without losing anything right?
And then twrp and re-root?
Click to expand...
Click to collapse
Yes to all.
Just fyi after I rebooted twrp I had no touch response. I was happy to learn that flashing custom kernel fixed the touch issue with TWRP
Sent from my crosshatch using XDA Labs
If I downloaded the ota and have full twrp installed, the proper way of installing is to sideload through twrp correct?
Drewski_1987 said:
If I downloaded the ota and have full twrp installed, the proper way of installing is to sideload through twrp correct?
Click to expand...
Click to collapse
I have not tested it with the OTA sorry
Sent from my crosshatch using XDA Labs
lollyjay said:
Here is the changelog
Sent from my crosshatch using XDA Labs
Click to expand...
Click to collapse
No fix for the bottom speaker.
swieder711 said:
No fix for the bottom speaker.
Click to expand...
Click to collapse
wasn't aware there was an issue for bottom speaker??
swieder711 said:
No fix for the bottom speaker.
Click to expand...
Click to collapse
I have no issues with the speakers after this update.
Sent from my crosshatch using XDA Labs
Drewski_1987 said:
If I downloaded the ota and have full twrp installed, the proper way of installing is to sideload through twrp correct?
Click to expand...
Click to collapse
No you need the stock recovery for sideloading the ota.
lollyjay said:
I have no issues with the speakers after this update.
Sent from my crosshatch using XDA Labs
Click to expand...
Click to collapse
Did you have an issue with the speaker before this update?
swieder711 said:
Did you have an issue with the speaker before this update?
Click to expand...
Click to collapse
No. I think it is not firmware related. Perhaps a quality problem?
Sent from my crosshatch using XDA Labs
lollyjay said:
Yes to all.
Just fyi after I rebooted twrp I had no touch response. I was happy to learn that flashing custom kernel fixed the touch issue with TWRP
Sent from my crosshatch using XDA Labs
Click to expand...
Click to collapse
wait, i have to remove the -w to prevent the wipe correct?
masri1987 said:
wait, i have to remove the -w to prevent the wipe correct?
Click to expand...
Click to collapse
Ya tru dat ?
Sent from my crosshatch using XDA Labs
lollyjay said:
Yes to all.
Just fyi after I rebooted twrp I had no touch response. I was happy to learn that flashing custom kernel fixed the touch issue with TWRP
Sent from my crosshatch using XDA Labs
Click to expand...
Click to collapse
Same. TWRP was unresponsive. Booted into TWRP using the boot image and fastboot command. Then flashed custom kernel + Magisk and now all is working as it should.
anyone notice any difference from Nov?
considering doing a full wipe after work, as i dont believe in dirty flashing
virtyx said:
anyone notice any difference from Nov?
considering doing a full wipe after work, as i dont believe in dirty flashing
Click to expand...
Click to collapse
Very minor differences.
Free memory is a little greater
Seems smoother
One disappointment is System theme still not working
Sent from my crosshatch using XDA Labs
Can someone please give the steps to update.
Sent from my Pixel 3 XL using Tapatalk
chakra said:
Can someone please give the steps to update.
Click to expand...
Click to collapse
Depends on so many things.
If you are stock, then you can just flash the OTA
If you have twrp and magisk, then you can fastboot flash
So many possibilities
Sent from my crosshatch using XDA Labs