Related
So I'm rooted with an unlocked boot loader and a custom ROM installed but when I downloaded some apps it said it can't access root so I checked root checker and it said
My phone isn't rooted even tho I have supersu and a custom ROM on it
Sent from my HTC One using xda app-developers app
Remove the super su and install superSU.zip from recovery.
Sent from my One V using xda app-developers app
Are you sure nothing will happen? Can I just get it from Google play?
Sent from my HTC One using xda app-developers app
Zakdroid said:
Are you sure nothing will happen? Can I just get it from Google play?
Click to expand...
Click to collapse
If you just moved up to 4.3, root implementation has changed, so you need to flash SU from recovery the first time.
iElvis said:
If you just moved up to 4.3, root implementation has changed, so you need to flash SU from recovery the first time.
Click to expand...
Click to collapse
I'm having similar issues with my HTC One, I unlocked and rooted and installed Maximus HD 13 rom - that's when I started getting problems with SuperSu - first the update issue, now it says no binaries.
I tried installing it from recovery, I even tried CWM, then reflashed TWRP. Still nothing, same error. No binaries. Driving me bloody crazy.
ieldra said:
I'm having similar issues with my HTC One, I unlocked and rooted and installed Maximus HD 13 rom - that's when I started getting problems with SuperSu - first the update issue, now it says no binaries.
I tried installing it from recovery, I even tried CWM, then reflashed TWRP. Still nothing, same error. No binaries. Driving me bloody crazy.
Click to expand...
Click to collapse
Do a full wipe and start over, flashing rom and then supersu together.
iElvis said:
Do a full wipe and start over, flashing rom and then supersu together.
Click to expand...
Click to collapse
Yeah it looks like that's what I'm gonna have to do, should I wipe boot as well ? Maximus HD installs the stock kernel as well, wondering if it also installs hboot. Afaik /boot is split into boot and kernel. Wouldn't wanna wipe the entire device, install the ROM, reboot and find myself with no hboot !
ieldra said:
Yeah it looks like that's what I'm gonna have to do, should I wipe boot as well ? Maximus HD installs the stock kernel as well, wondering if it also installs hboot. Afaik /boot is split into boot and kernel. Wouldn't wanna wipe the entire device, install the ROM, reboot and find myself with no hboot !
Click to expand...
Click to collapse
hboot and boot.img are two different things. No rom will touch hboot. Only way to change your hboot is via RUU or OTA, or to s-off and flash in RUU mode.
All roms include a kernel, usually the stock kernel. That will overwrite whatever you had there before but you should still wipe /data.
iElvis said:
hboot and boot.img are two different things. No rom will touch hboot. Only way to change your hboot is via RUU or OTA, or to s-off and flash in RUU mode.
All roms include a kernel, usually the stock kernel. That will overwrite whatever you had there before but you should still wipe /data.
Click to expand...
Click to collapse
Thanks for your replies man! Really helpful ! I installed Maximus HD again, formatted everything I possibly could... it comes preloaded with supersu. Still says no binaries... What the hell should I do
ieldra said:
Thanks for your replies man! Really helpful ! I installed Maximus HD again, formatted everything I possibly could... it comes preloaded with supersu. Still says no binaries... What the hell should I do
Click to expand...
Click to collapse
Did you flash the supersu zip separately in recovery? I've had to do that every time I installed a 4.3 rom.
iElvis said:
Did you flash the supersu zip separately in recovery? I've had to do that every time I installed a 4.3 rom.
Click to expand...
Click to collapse
Alright, basically what I did today is I wiped every single partition I had access to, so everything but boot and recovery. installed maximus HD 13, installed faux kernel, installed faux kernel camera fix. Maximus installs supersu by default, I opened it up and I got the stupid no binary error. So I went back to recovery and attempted SuperSu 1.65 from zip, still the same problem. Please note that I did all this BECAUSE of my issues with root, funny how after nuking the whole phone I still have the same problem. I've google extensively, and pretty much the only advice I've found involves either rooting from recovery or changing something in SuperSu settings, which I CAN'T ACCESS because the app closes right after the error prompt pops up.
I'm a few desperate attempts short of attempting an exorcism...
ieldra said:
Alright, basically what I did today is I wiped every single partition I had access to, so everything but boot and recovery. installed maximus HD 13, installed faux kernel, installed faux kernel camera fix. Maximus installs supersu by default, I opened it up and I got the stupid no binary error. So I went back to recovery and attempted SuperSu 1.65 from zip, still the same problem. Please note that I did all this BECAUSE of my issues with root, funny how after nuking the whole phone I still have the same problem. I've google extensively, and pretty much the only advice I've found involves either rooting from recovery or changing something in SuperSu settings, which I CAN'T ACCESS because the app closes right after the error prompt pops up.
I'm a few desperate attempts short of attempting an exorcism...
Click to expand...
Click to collapse
I have not used Maximus, so maybe you should move over to that thread. I had the same issues with ARHD, but flashing SuperSU in recovery after the rom flash took care of it. In all likelihood, you're not the only Maximus user to deal with this, so the answer may be over there.
iElvis said:
I have not used Maximus, so maybe you should move over to that thread. I had the same issues with ARHD, but flashing SuperSU in recovery after the rom flash took care of it. In all likelihood, you're not the only Maximus user to deal with this, so the answer may be over there.
Click to expand...
Click to collapse
I don't know what changed, but i changed TWRP for CWM, installed the rom, then immediately installed supersu and it worked. I love you. I want you to have my babies.
ieldra said:
I don't know what changed, but i changed TWRP for CWM, installed the rom, then immediately installed supersu and it worked. I love you. I want you to have my babies.
Click to expand...
Click to collapse
I'm lacking the uterus for that, but feel free to hit the Thanks button.
iElvis said:
I'm lacking the uterus for that, but feel free to hit the Thanks button.
Click to expand...
Click to collapse
Alright, so SuperSu WORKED. Until I flashed the faux123 kernel, at which point it stopped working again. Same issue, no binaries. So I reformatted the whole phone, installed Rom, then faux123 kernel, then SuperSu. Same issue. No binaries. I can only conclude that installing the kernel causes the issue. Hope this helps someone who has the same problem. Gonna stick to stock kernel for now
ieldra said:
Alright, so SuperSu WORKED. Until I flashed the faux123 kernel, at which point it stopped working again. Same issue, no binaries. So I reformatted the whole phone, installed Rom, then faux123 kernel, then SuperSu. Same issue. No binaries. I can only conclude that installing the kernel causes the issue. Hope this helps someone who has the same problem. Gonna stick to stock kernel for now
Click to expand...
Click to collapse
That's odd. Are you sure you're flashing the right kernel? I had no such problems with the 4.3 version of ElementalX.
iElvis said:
That's odd. Are you sure you're flashing the right kernel? I had no such problems with the 4.3 version of ElementalX.
Click to expand...
Click to collapse
Pretty sure I am, "m7-faux123-Sense43-007m.zip" and "faux123-jb43-sense-camera-fix.zip". Did you have to root again after installing ElemntalX ? Just finished reinstalling ROM for fourth time today, going to check SuperSu works, go back to recovery, make a nandroid backup and perhaps try ElementalX Is there a kernel control app for it ?
ieldra said:
Pretty sure I am, "m7-faux123-Sense43-007m.zip" and "faux123-jb43-sense-camera-fix.zip". Did you have to root again after installing ElemntalX ? Just finished reinstalling ROM for fourth time today, going to check SuperSu works, go back to recovery, make a nandroid backup and perhaps try ElementalX Is there a kernel control app for it ?
Click to expand...
Click to collapse
I only had to flash SuperSU once. I use TricksterMod.
I've experienced this problem on two different ROMs (different variations of the same problem, actually). In both cases, flashing the same SuperSU .zip fixed it. Link here.
iElvis said:
That's odd. Are you sure you're flashing the right kernel? I had no such problems with the 4.3 version of ElementalX.
Click to expand...
Click to collapse
Dude,
Thank you so much for you post, been wondering is this problem bothering me since i saw you post so i tested it out, end up the rom was fine till i flash the faux123 kernal and camera fix, and binary not install issue come out again.
for people who having same problem, this might be the issue
Cheer
I'm root/soff. a new ota just came out that will fix my unusable phone. how do I take it if im root, do I have to fully unroot? or can I take it as is?
Sent from my SM-T217S using XDA Free mobile app
looks like it needs stock recovery to flash, it's not hboot format and twrp won't take it. will report back if I am able to do it
Sent from my SM-T217S using XDA Free mobile app
One of the benefits to being s-off is you don't have to take the OTA...you just flash the firmware and done.
BD619 said:
One of the benefits to being s-off is you don't have to take the OTA...you just flash the firmware and done.
Click to expand...
Click to collapse
i did that and then i was unable to take profile or prl updates :crying: it also didnt apear to have fixed the signal issue... i might not have waited enough... or it could have something to do with the unability to take prl and profile updates... anyhow ill try again from a diferent download see what happens
Did your baseband change? last four should be .0610.
If it did change then it's most likely a network issue.
BD619 said:
Did your baseband change? last four should be .0610.
If it did change then it's most likely a network issue.
Click to expand...
Click to collapse
Yes the baseband did change but the signal problem persists. i need to take the FULL ota to fix my phone (or install something else that will) regardless the radios alone aren't fixing the issue.
i tried flashing the rafios by themselves and it wouldnt update prl or profile; it also had the same signal issue. i tried the radios AND the new stock rom for it and same thing. i tried going back to stock and taking the ota and the ota wouldnt install.
Thoughs?
I'm the same root/s-off. I flash the h/k sound file did you find a way to install the latest ota update?
I cant figure out how to get the OTA either
I have S-Off im also rooted, and i have TWRP recovery, i can't get the zip to flash. I was thinking about doing a stock root recovery using the RUU, but then i thought if i do that, would i still be able to reroot using the same method? so my question is, how can i flash this zip and keep my root? or should do a stock recovery from the RUU and update and wait for another root? if any devs read this, i'd really like your help please and thank you. I currently have the stock rom with just root access and S-Off.no custom roms on here.
man.. i have the same problem bro.. smh.. hey man keep me posted if something comes up
Working via fastboot: http://forum.xda-developers.com/showthread.php?t=2759908&page=8
I am S-Off and had no issues, took 2 minutes, I followed the MikMik link
the 1.54.651.10 update.
If I'm rooted and have S on, how do i take the update?
jchtcusre1 said:
If I'm rooted and have S on, how do i take the update?
Click to expand...
Click to collapse
Settings>System Updates>HTC Software Update
BD619 said:
Settings>System Updates>HTC Software Update
Click to expand...
Click to collapse
I tried that and failed, I returned to a completely stock rooted backup from the day I rooted, downloaded the update, chose install, it rebooted to recovery, saw no stock recovery, so it brought up TWRP and thats it.........
scott_0 said:
I tried that and failed, I returned to a completely stock rooted backup from the day I rooted, downloaded the update, chose install, it rebooted to recovery, saw no stock recovery, so it brought up TWRP and thats it.........
Click to expand...
Click to collapse
I never OTA so not really sure of the process.
scott_0 said:
I tried that and failed, I returned to a completely stock rooted backup from the day I rooted, downloaded the update, chose install, it rebooted to recovery, saw no stock recovery, so it brought up TWRP and thats it.........
Click to expand...
Click to collapse
You have to have stock recovery to take the update, which means you have to flash stock recovery first and then take the update, then repeat the rooting process.
scott_0 said:
I tried that and failed, I returned to a completely stock rooted backup from the day I rooted, downloaded the update, chose install, it rebooted to recovery, saw no stock recovery, so it brought up TWRP and thats it.........
Click to expand...
Click to collapse
you should at least have seen a green arrow circle and/or a red triangle with a "!" in the middle. if you saw the triangle that is recovery trying and failing to update. at this point if you press and releast volumeup+power it should bring up the text of what it did.
rhe12 said:
You have to have stock recovery to take the update, which means you have to flash stock recovery first and then take the update, then repeat the rooting process.
Click to expand...
Click to collapse
I am dev unlocked, rooted, s-on with twrp. If I revert to stock recovery would I be able to take the OTA then reinstall twrp?
Many thanks!
Swyped mobile from HTC One M8.
drich66 said:
I am S-Off and had no issues, took 2 minutes, I followed the MikMik link
Click to expand...
Click to collapse
I'm looking at the MikMik one, and I am just not sure if this will erase all my apps and settings. Do I need to use a backup app or should I be ok flashing this and keeping all my apps and settings?
I'm running a stock rooted rom and I was wondering if it's possible that somebody could please make a flashable zip with the Spark icons from Bad Boyz or at least give me some insight on how to get them and make the zip.
I would greatly appreciate it. Thanks in advance.
levengador said:
I'm running a stock rooted rom and I was wondering if it's possible that somebody could please make a flashable zip with the Spark icons from Bad Boyz or at least give me some insight on how to get them and make the zip.
I would greatly appreciate it. Thanks in advance.
Click to expand...
Click to collapse
Why not just flash Bad Boyz ROM? That's the easiest way to get them .
Captain_Throwback said:
Why not just flash Bad Boyz ROM? That's the easiest way to get them .
Click to expand...
Click to collapse
Well, I tried, the rom flashes and phone boots up and stays on for about 30 seconds before rebooting. I have absolutely no idea what I'm doing wrong. That's why I opted for this lol I've got this rom customized almost perfect. Only thing I'm missing is that Spark icon that should've been the stock one in the first place
levengador said:
Well, I tried, the rom flashes and phone boots up and stays on for about 30 seconds before rebooting. I have absolutely no idea what I'm doing wrong. That's why I opted for this lol I've got this rom customized almost perfect. Only thing I'm missing is that Spark icon that should've been the stock one in the first place
Click to expand...
Click to collapse
Sounds like you're S-ON. S-OFF will fix that problem. Also, flashing the latest SuperSU zip in recovery after flashing the ROM will also fix it.
I'm surprised you didn't come across those solutions when you searched the forum after initially having the issue - that's a pretty common problem with relatively simple options for fixing.
Captain_Throwback said:
Sounds like you're S-ON. S-OFF will fix that problem. Also, flashing the latest SuperSU zip in recovery after flashing the ROM will also fix it.
Click to expand...
Click to collapse
I haven't ben able to get S-Off. Firewater isn't doing it:silly:
levengador said:
I haven't ben able to get S-Off. Firewater isn't doing it:silly:
Click to expand...
Click to collapse
That's what SunShine S-OFF is for .
Captain_Throwback said:
That's what SunShine S-OFF is for .
Click to expand...
Click to collapse
Wrong Kernel/Rom config. My luck hahaha I'll flash a stock rom tomorrow and try again. Thanks for the advice though!
Yeah I had the same problem would just keep rebooting every 30 seconds, you should be able to in command prompt when it says the device is connected type adb reboot bootloader then just go to your twrp menu and reflash super user. That will fix it.
https://www.dropbox.com/s/t9s7hlqk63mjkte/Bad_Boyz_Sprint_ONE_Spark_icons.zip?dl=0 here it is. If it's prohibited please delete post
I've been using ViperOneM8 for the past few months. This weekend I tried to switch to AndroidRevolution, but it got stuck on startup. I decided to cut my losses and go back to Viper. I attempted to restore the backup I had made just before attempting the switch, but that got stuck on startup as well.
I've since tried to restore every backup I have to no avail. I've tried flashing new ROMs. I'm hoping someone smarter than myself has an idea of what to try next...?
When it gets stuck, I see the HTC splash screen, then the ViperOne animation, then nothing changes. All I can do is wait for the battery to die, plug it in, and then I'm able to get to recovery again.
Using TWRP recovery, FYI.
Which version of TWRP are you using? Have you verified md5's on ROM downloads?
EVOuser94 said:
Which version of TWRP are you using? Have you verified md5's on ROM downloads?
Click to expand...
Click to collapse
Thanks for the reply! Yes, I verified MD5s for the new ROMs. I'll have to get back to you re:TWRP version in the next hour or so. It's roughly 3-4 months old I believe.
EVOuser94 said:
Which version of TWRP are you using? Have you verified md5's on ROM downloads?
Click to expand...
Click to collapse
looks like TWRP v2.7.0.2
Update to latest twrp and try again
As far as I know ARHD is not Sprint compatible, by flashing it you messed up the partitions, you will have to RUU and start fresh and only flash roms from the Sprint section.
EVOuser94 said:
Update to latest twrp and try again
Click to expand...
Click to collapse
Flashed 2.8.3.0, but it didn't work. Got stuck loading into recovery (bizarre)
Flashed 2.8.1.0 just fine though. That did the trick! Thanks EVO! I should have thought of that... oh well.
BD619 said:
As far as I know ARHD is not Sprint compatible, by flashing it you messed up the partitions, you will have to RUU and start fresh and only flash roms from the Sprint section.
Click to expand...
Click to collapse
This surprised me so I checked - it was actually an InsertCoin I tried to flash. AR was one I was looking at, probably wasn't able to find it in the Sprint section so I went for a different one. My mistake. Thanks for the response though!
Alright, so I had M Preview 1 and used the rooting procedure from this thread: http://forum.xda-developers.com/nexus-6/general/root-nexus-6-android-m-dev-preview-t3123285 and it worked flawlessly with no booting errors or anything.
Now that I've upgraded to Preview 2 on the day it was released I can't get it to root. I've tried the methods in that post, I've tried some other methods that I've picked up over the years of doing this kind of stuff and no matter what I end up in a boot loop or a boot validation error that just shuts the phone down. So I just end up re-flashing the system and boot partitions to get it back up again while I look for more solutions.
I've looked all over XDA and some other forums thinking that maybe I need a different kernel, or Super SU package but I can't find anything. If someone can explain to me or at least reply with a link to a thread that will help me out I'd really appreciate it.
Thanks in advance!
jonzey231 said:
Alright, so I had M Preview 1 and used the rooting procedure from this thread: http://forum.xda-developers.com/nexus-6/general/root-nexus-6-android-m-dev-preview-t3123285 and it worked flawlessly with no booting errors or anything.
Now that I've upgraded to Preview 2 on the day it was released I can't get it to root. I've tried the methods in that post, I've tried some other methods that I've picked up over the years of doing this kind of stuff and no matter what I end up in a boot loop or a boot validation error that just shuts the phone down. So I just end up re-flashing the system and boot partitions to get it back up again while I look for more solutions.
I've looked all over XDA and some other forums thinking that maybe I need a different kernel, or Super SU package but I can't find anything. If someone can explain to me or at least reply with a link to a thread that will help me out I'd really appreciate it.
Thanks in advance!
Click to expand...
Click to collapse
flash any m based custom kernel, i generally use despair or elementalx, and then flash the latest supersu, when you boot, youll have root. the latest supersu is version 2.49 btw. and if you want to yse the kernel in that thread, elite kernel, grab the latest m version, not the one in that thread, its old.
simms22 said:
flash any m based custom kernel, i generally use despair or elementalx, and then flash the latest supersu, when you boot, youll have root. the latest supersu is version 2.49 btw. and if you want to yse the kernel in that thread, elite kernel, grab the latest m version, not the one in that thread, its old.
Click to expand...
Click to collapse
Yeah I tried using the latest M version of that kernel and yes, I used Super SU 2.49. Thanks though, I'll try the latest elementalx kernel.
jonzey231 said:
Yeah I tried using the latest M version of that kernel and yes, I used Super SU 2.49. Thanks though, I'll try the latest elementalx kernel.
Click to expand...
Click to collapse
well, then its odd, you should have gotten root after flashing both in recovery.
simms22 said:
well, then its odd, you should have gotten root after flashing both in recovery.
Click to expand...
Click to collapse
I know, right? I'll give it another shot. I'm getting ready to do it now. I'll update in a few minutes when I've finished up.
Edit: Grabbed Elemental from here: http://forum.xda-developers.com/showpost.php?p=61931417&postcount=3921&nocache=1
Updated last night so it should be the absolute latest version. So I'll flash twrp in fastboot, then boot into twrp and flash the kernel first, and then supersu and I should be good to go.
The Elemental Installation is freaking awesome! I've never installed it before. That's so cool how it brings up it's own interface for the install to customize your setup.
And the phone just booted up after flashing both the kernel and supersu.
The boot animation (spinning colored dots) is glitching out though. Can't tell if it's a "setting up" type of thing or not. It's optimizing app 1 of 1 right now.
jonzey231 said:
The Elemental Installation is freaking awesome! I've never installed it before. That's so cool how it brings up it's own interface for the install to customize your setup.
And the phone just booted up after flashing both the kernel and supersu.
The boot animation (spinning colored dots) is glitching out though. Can't tell if it's a "setting up" type of thing or not. It's optimizing app 1 of 1 right now.
Click to expand...
Click to collapse
yea, elementalx uses the aroma installer, whete you can pick and chose what you wnt in the kernel. sounds like its booting, hopefully youll have root.
simms22 said:
well, then its odd, you should have gotten root after flashing both in recovery.
Click to expand...
Click to collapse
It's been in a bootloop for like 5 minutes. It would get the the Android is Starting screen and loan for about 30-40 seconds, then reboot.
Then it would hit the validation screen and reboot.
Then it would boot back to Android is Starting, freeze, and reboot lol
It is very erratic, all of this has been going on without any interference from me. Just letting it sit there trying to work through it's issues.
Then all of a sudden as I was typing "adb reboot-bootloader" the thing boots right into my existing lockscreen haha. So I guess I'll just do my best to not have to reboot this thing in case it wants to have a seizure like that again lol.
simms22 said:
yea, elementalx uses the aroma installer, whete you can pick and chose what you wnt in the kernel. sounds like its booting, hopefully youll have root.
Click to expand...
Click to collapse
It's finally up and loaded and yes, I've got root now. Thanks for your help today.
jonzey231 said:
It's finally up and loaded and yes, I've got root now. Thanks for your help today.
Click to expand...
Click to collapse
simms22 said:
Click to expand...
Click to collapse
One final question.
Is there any way to get system write access? If so, what did you use? I tried the fix_rw_boot.img that I used for preview 1 and it just put me in a boot loop lol.
jonzey231 said:
One final question.
Is there any way to get system write access? If so, what did you use? I tried the fix_rw_boot.img that I used for preview 1 and it just put me in a boot loop lol.
Click to expand...
Click to collapse
sure. i just flashed an m compatible kernel(despair), and supersu 2.49. bow ive root with full access, write as well.
simms22 said:
sure. i just flashed an m compatible kernel(despair), and supersu 2.49. bow ive root with full access, write as well.
Click to expand...
Click to collapse
Hmmm...I flashed Elite with SuperSU and ElementalX with SuperSU. Wasn't able to get root with either one. Clean flashes (coming from formatted partitions) each time too.
I've got it up and rooted and restored but don't have access to write to the system partition at all no matter what I try.
jonzey231 said:
Hmmm...I flashed Elite with SuperSU and ElementalX with SuperSU. Wasn't able to get root with either one. Clean flashes (coming from formatted partitions) each time too.
I've got it up and rooted and restored but don't have access to write to the system partition at all no matter what I try.
Click to expand...
Click to collapse
yea, it seems as a few are having this same issue, while most have no issue http://forum.xda-developers.com/nexus-6/general/root-nexus-6-android-m-dev-preview-t3123285/page18
simms22 said:
sure. i just flashed an m compatible kernel(despair), and supersu 2.49. bow ive root with full access, write as well.
Click to expand...
Click to collapse
simms22 said:
yea, it seems as a few are having this same issue, while most have no issue http://forum.xda-developers.com/nexus-6/general/root-nexus-6-android-m-dev-preview-t3123285/page18
Click to expand...
Click to collapse
Yeah I just flashed Despair and SuperSU to replicate what you've done and still nothing.
This is pretty irritating.
jonzey231 said:
Yeah I just flashed Despair and SuperSU to replicate what you've done and still nothing.
This is pretty irritating.
Click to expand...
Click to collapse
ok, i think i have a solution for you. its a little dirty, but its a solution i think. im running it right now, so its safe. its a basic m version 2 rom. it doesnt have many additions to it, its very basic. but i think youll get root. make a backup, i think that you could dirty flash it. or, to be safe, id wipe data. flash supersu 2.49 as well. heres the rom http://forum.xda-developers.com/nexus-6/development/rom-jdx-1-0-t3121053
simms22 said:
ok, i think i have a solution for you. its a little dirty, but its a solution i think. im running it right now, so its safe. its a basic m version 2 rom. it doesnt have many additions to it, its very basic. but i think youll get root. make a backup, i think that you could dirty flash it. or, to be safe, id wipe data. flash supersu 2.49 as well. heres the rom http://forum.xda-developers.com/nexus-6/development/rom-jdx-1-0-t3121053
Click to expand...
Click to collapse
Awesome, I didn't really he'd made a ROM for Preview 2 yet. I'll make a backup and give it a shot, thanks for pointing this out to me.
I'll let you know how it goes as well!
Update: it worked!!! I wiped the system partition and flashed the ROM. It failed the first time so I tried again after mounting the system and now I've got too with system write access!! Spread the word my friend.