I'm having issues getting the Superuser app to grant root to root apps.
The superuser apk is installed but isn't functioning.
Here's what I did. I was coming from pirateghost's CWM root ROM which was built off the stock developer's ICS OTA update (see my signature). I decided to start over since the sync icon would not go away from the notification tab. I know this is a minor issue but it was very annoying staring at it every time I used the phone.
I did the following:
1) Installed Wildchild's recovery using fastboot
2) Wiped all the data from the phone using wildchild's recovery
3) Locked the bootloader
4) Installed the ATT Stock RUU
5) Unlocked the bootloader
6) Reinstalled wildchild's recovery using fastboot
7) Installed the Superuser apk using wildchild's recovery
Everything is working fine and I don't have the sync icon stuck in the notification tab, but now I can't get any root application to be granted root access. The system just times out when the app is requesting root.
I'm guessing that Wildchild's recovery root is not compatible with the stock ICS release, but is this true? I haven't used the vivid all in one kit because it appears to be using the same method to install root. Everytime you install root it blows away all the data on the phone and makes you start from fresh, so I'm reluctant to try anything unless I'm certain it will work.
Any suggestions from the experts?
Did you look at the last post in the superguide? WC made a post to make rooting easier. Also a video in there as well.
Sent from my HTC PH39100 using XDA
megatronisabeast said:
Did you look at the last post in the superguide? WC made a post to make rooting easier. Also a video in there as well.
Sent from my HTC PH39100 using XDA
Click to expand...
Click to collapse
Yes, this is exactly what I did to the "T", just as in his video. SU is installed on my device but it doesn't grant any privileges to any root apps. I've been digging around searching for answers for about 3 hours and have found many people posting about the same issue but no fix.
3.07 is the latest version of su...redo it with unguarded version see if that works...the rom i used was unrooted and all stock
Wild Child said:
3.07 is the latest version of su...redo it with unguarded version see if that works...the rom i used was unrooted and all stock
Click to expand...
Click to collapse
I saw that and was wondering what "engineering Unguarded superuser" was but didn't know. I guess it's worth a try at this point.
FYI, I used the "Install eng (unguarded) su" and all it did was uninstall the Superuser apk.
Now the root apps respond with a different message when they request root. They don't see the SU app and reply with this statement, before they would hang while they requested SU access.
I'll wait until WC figures out what is going on or just download his ROM.
Are there any known bugs with his ROM?
[email protected] rooting....if going through trouble of unlocking bootloader and flashing a recovery....why not just flash a stock custom rom?....This make no [email protected] do this....Im the first to like completely stock builds,as thats what i use personally...but i cannot stand the at&t bloatware....Main problem with trying to root a stock build is the root access to kernel config....ill upload a stock rooted kernel, if having issues with root after using the recovery you need to install busybox from provided link below.
or flash the boot.img provided.
From original [email protected] guide
- ONCE BOOTED, if you have titanium backup installed but it says there isn't root or busybox isn't installed, download a free app from the market called BUSYBOX INSTALLER. Run this program and proceed in installing busybox. After that, try titanium backup again and it should work.
https://play.google.com/store/apps/...DMsImNvbS5qcnVtbXkuYnVzeWJveC5pbnN0YWxsZXIiXQ..
I had pirateghost's rooted ICS ROM installed but had the sync notification issue. That's why I decided to go back to the stock RUU. I've always been a stock kind of person. I don't know why, but I've always gone back to stock with my phones then rooted it and debloated it myself.
I'm downloading your ROM right now! Since I already have your recovery installed I'm sure this will be a breeze. Thanks!
megatronisabeast said:
Did you look at the last post in the superguide? WC made a post to make rooting easier. Also a video in there as well.
Sent from my HTC PH39100 using XDA
Click to expand...
Click to collapse
I tried using the WCX recovery to install su and I now have super user as one of the apps but Titanium backup could not acquire root privileges.
What am I doing wrong?
samsat said:
I tried using the WCX recovery to install su and I now have super user as one of the apps but Titanium backup could not acquire root privileges.
What am I doing wrong?
Click to expand...
Click to collapse
Look at wild Childs post a couple above this.
Sent from my HTC PH39100 using XDA
Thanks for helping Mega.
I tied installing busybox installer but it says no root access.
Is the stock rooted kernel being referred to boot.zip?
What's the safest way to flash this?
The fastboot flash boot boot.img command is the safest.
samsat said:
Thanks for helping Mega.
I tied installing busybox installer but it says no root access.
Is the stock rooted kernel being referred to boot.zip?
What's the safest way to flash this?
Click to expand...
Click to collapse
Wild Child said:
The fastboot flash boot boot.img command is the safest.
Click to expand...
Click to collapse
I successfully flashed the boot.img file above.
Titanium backup and busybox installer both say no root access.
No apps in superuser.
I really want to get your ROM installed, just this root issue which is stopping me!
Something else is going on then, my rom has nothing to do with this....the roms i release are already rooted and debloated stock builds
samsat said:
I successfully flashed the boot.img file above.
Titanium backup and busybox installer both say no root access.
No apps in superuser.
I really want to get your ROM installed, just this root issue which is stopping me!
Click to expand...
Click to collapse
Samsat, so let's see what you have done so far:
flashed boot.img
flashed recovery
what about the rom? What did you do with that? Was it a zip file from WC's site?
megatronisabeast said:
Samsat, so let's see what you have done so far:
flashed boot.img
flashed recovery
what about the rom? What did you do with that? Was it a zip file from WC's site?
Click to expand...
Click to collapse
Yes done the above but still running RUU ICS stock rom.
samsat said:
Yes done the above but still running RUU ICS stock rom.
Click to expand...
Click to collapse
I would say if you want root, the best thing to do is install one of Wild Child's roms. Once you install it, you will have root. He has an att build just like the att ruu but without the bloat.
http://www.wcxxperia-nce.com/index.php
This is his site. You have to register to see the vivid forum. Also, make sure to read the rules before installing his rom.
Exact process i did and it is rooted with titanium back up working...so flashing from wcxrecovery does work.
Testing procedure:
1 Flashed fastboot oem relock...success
2 Flashed PH39IMG.zip
3 Said Update was complete
4 Phone rebooted
5 My custom ROM was still present
6 Flashed PH39IMG.zip again
7 My custom ROM was still present
8 Attempted running RUU,Failed
9 Entered fastboot via Hboot menu
10 Re ran ruu,ROM updated completely.
11 Ran bootloader unlock command
12 Flashed wcx recovery (provided)
13 Flashed rooted kernel (provided)
14 Booted ROM,fully loaded
15 Rebooted into recovery
16 Installed superuser and su
17 Signed into Market
18 installed stericson Busybox
19 Installed titanium Backup
20 Succesfully rooted with stock att rom
21 Reboot phone after doing said process above Perm root achieved
Thanks WC. I must have been doing the same while you were posting this!
All went according to plan. I now have a rooted phone with unbloated ICS kernel, WCX recovery etc. etc.
Thanks WC, This is great
Related
First off I would like to thank everyone on this amazing site for all the advice, guides and tutorials.
I unlocked my nexus bootloader and flashed a couple different roms. I really like the rom manager so I've used that to download roms and then flash them using that app.
When I downloaded the stock version of 91and flashed it, the phone no longer seemed to have root or clockwork recovery but my bootloader was still unlocked. When I downloaded rom manager, it could not get super user permissions, this being useless in flashing a backup or new rom. So I used universal one click root to gain root access and then rom manager was able to flash a backup.
I know this may be a dumb question but hope someone could explain to me why I needed to re-root and why I lost clockwork recovery...?
Thanks for the help in advance.
cwazynit said:
When I downloaded the stock version of 91and flashed it
Click to expand...
Click to collapse
Right theres your problem. stock roms dont have root built in you have to root them again. unless you download a prerooted stock rom. hope this helps.
cwazynit said:
I know this may be a dumb question but hope someone could explain to me why I needed to re-root and why I lost clockwork recovery...?
Click to expand...
Click to collapse
also it isnt a stupid question its that you didnt know and you wanted to know. when i started i didnt know either. lol.
krypticos said:
Right theres your problem. stock roms dont have root built in you have to root them again. unless you download a prerooted stock rom. hope this helps.
Click to expand...
Click to collapse
Yep this seems to be your problem. If you're wanting stock with the basic add-ons then the first link in this thread is your answer: Link.
Thanks very much. That does make sense. I thought unlocked bootloader meant I was rooted regardless of rom! I'm in way over my head lol. Looking forward to learning more...thanks for the new rom link as well
Sent from my Nexus One using XDA App
cwazynit said:
Thanks very much. That does make sense. I thought unlocked bootloader meant I was rooted regardless of rom! I'm in way over my head lol. Looking forward to learning more...thanks for the new rom link as well
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
The advantage of unlocking your bootloader means you can flash a custom recovery from Fastboot mode, without having to "root" the ROM. Next time this happens you can just boot into fastboot and flash clockwork from there like this:
fastboot flash recovery PATHTO\RECOVERYFILENAME.img
so say you download clockwork and save it to c:\sdk\fastboot named recovery.img from a command prompt you enter the following
cd \sdk\fastboot
fastboot flash recovery recovery.img
once it is done flashing you can do this
fastboot reboot recovery
and that should take you into clockwork where you can flash your favorite ROM (or restore a backup).
Thanks for the help. I will be sure to try that method out next time. Very helpful.
Hi,
Upgraded to 2.3.3 and lost root.
Bored of mucking about with oneclick etc, I unlocked the bootloader. Easy(ish), cool!
Trying to flash amon ra with fastboot, everything goes well (appears as though it's flashed). But when I re-boot, it isn't there!
Padlock showing - so bootloader unlocked.
Nexus drivers installed, device showing with "fastboot devices".
Trying to flash amon ra 2.2.1.
Any suggestions?
Ta!
Andy
When you boot a stock rom it wipes custom recoverys and puts the stock one back.
Use the search feature on the forum.
Sent from my Nexus One using XDA App
Read my signature, look there for recovery installation guide w/ unlocked bootloader.
albundy2010 said:
When you boot a stock rom it wipes custom recoverys and puts the stock one back.
Use the search feature on the forum.
Click to expand...
Click to collapse
Thanks for your reply.
I've spent (literally) all day searching the forum (I'm in the uk - so hours and hours). There's so much, and some of it contradictory.
Ok, so I can't put a rom on without a custom recovery, but I can't put a custom recovery on because the stock rom wipes it?
I don't actually want a custom rom, simply a rooted stock phone. Which I have had previously.
Cheers! (driven to booze!)
Andy
Jack_R1 said:
Read my signature, look there for recovery installation guide w/ unlocked bootloader.
Click to expand...
Click to collapse
Thanks.
Yes, that's what I've been doing. There's a mistake in that part of the faq:
Faq states at the end "reboot recovery"
Should be "reboot-bootloader"
That works, but as soon as I then reboot into 2.3.3 - it wipes the custom recovery (which is why I'm in the q + a).
The other problem I'm having is that my phone doesn't appear rooted from within the o/s (apps that require root don't work), but the padlock is there ans the bootloader is unlocked. I can install su and busybox installer from the market, but neither work.
Back to the beer!
Andy
I can't explain all in detail while on my phone.
Do this. Grab a preroooted stock rom from the dev section and put it on SD card.
Boot into fastboot and flash the custom recovery.
Then load up that recovery without booting up the os.
Flash the rom you downloaded.
There are other ways to fix your issue but this is probably the simplest for you.
Sent from my Nexus One using XDA App
albundy2010 said:
There are other ways to fix your issue but this is probably the simplest for you.
Click to expand...
Click to collapse
Thanks, that makes sense - and I agree with your statement above (simplest for me)!
I had (mistakenly) thought that unlocking the bootloader, then installing busybox and su from the market gave me a rooted phone.
I'll give it a go, when my wife regains her patience ;-)
Andy
andynx1 said:
Thanks.
Yes, that's what I've been doing. There's a mistake in that part of the faq:
Faq states at the end "reboot recovery"
Should be "reboot-bootloader"
That works, but as soon as I then reboot into 2.3.3 - it wipes the custom recovery (which is why I'm in the q + a).
Click to expand...
Click to collapse
Damn, you're right. The guide is missing the part of removing 2 files that the other guides have. I'll try adding that.
Jack_R1 said:
Damn, you're right. The guide is missing the part of removing 2 files that the other guides have. I'll try adding that.
Click to expand...
Click to collapse
Guide fixed. I've uploaded and linked the file that removes the stock recovery restoring files from the stock ROM.
You can repeat the guide and include the new part - it should prevent stock recovery from being restored on reboot.
Please try and write your feedback.
cheers! i've done what was suggested tho', and its worked a treat.
thanks again.
Andy
Hi guys
Can any one tell me how to root nexus one 2.3.6 ,i have locked boatloader.
zahid
Try SuperOneClick
http://forum.xda-developers.com/showthread.php?t=803682
or unlock the bootloader, fastboot custom recovery and flash ROM of choice.
Try this
http://forum.xda-developers.com/showthread.php?t=1324227
Sent from my Nexus One using Tapatalk
Use this. I just rooted my stock 2.3.6 nexus using this method. Takes less then a minute once everything is downloaded. Just make sure to extract all the files into the same location as the adb.exe file. Usually its in android/platform-tools.
Good luck and let us know if you have any questions.
BTW it does not unlock you bootloader either!
http://forum.xda-developers.com/showthread.php?t=1324227
krazichinaman said:
Just make sure to extract all the files into the same location as the adb.exe file. Usually its in android/platform-tools.
Is that a compulsion that super one click must be in the same location as adb n sdk tools?
Cos i rooted my stock 2.3.3 using the same method last month
But had it in different directories c: n e:
Sent from my Nexus One using Tapatalk
Click to expand...
Click to collapse
guys thank you so much you all are genius ,today i ll try this method and let everyone know..
hi guys
thanks i finally rooted my nexus one thanks to all
Now question can i install a custom rom from ROM manager or i had to unlock my boatloader first?
zahidismaeel said:
hi guys
thanks i finally rooted my nexus one thanks to all
Now question can i install a custom rom from ROM manager or i had to unlock my boatloader first?
Click to expand...
Click to collapse
You're good to go. Just install a custom recovery
CWM or Amon Ra, you can install them via Rom Manger.
hi
I tried to install custom ROM but when phone reboot it stuck on "triangle android" seems first i have to unlock my boatloader.
Can you post me link..
It means that you didn't flash the file that removes stock recovery reinstaller - and stock recovery is reinstalled on stock ROM boot.
Reboot back to ROM, root again, this time when you reboot to recovery first time, flash the file. It's found in Nexus One Wiki, section "Recovery".
zahidismaeel said:
hi
I tried to install custom ROM but when phone reboot it stuck on "triangle android" seems first i have to unlock my boatloader.
Can you post me link..
Click to expand...
Click to collapse
Its not at all necessary to unlock the bootloader. Did u install custom recovery before flashing a custom rom? I think u skipped that step.
Simple and best way for starters like us is to
1.root via super one click root
2. Install rom manager from market and wid the help of that, flash clockworkmod(cwm) recovery.
3. Install Titanium backup from market and do a backup up of ur apps.
4. Choose the correct rom of ur choice by reading the OP and the thread.
5. Download it and install it via rom manager.
6. Before that back up your current rom and wipe the system,cache,dalvik cache.
Thats it, u r good to go. :thumbup:
This is how i did n doing good
PS: Am just a newbie, so if there's any mistakes in my steps pls correct me.
Sent from my Nexus One using Tapatalk
thanks Man its working,,,,,,
but i am little surprise i did the same like flashing clockworkmod(cwm) recovery first and then ROM..but it didnt work me at that time...strange... Anyways now its working i m now on MIUI ROM looks cool..
question,,, what the advantage of having boatloader unlock?and wat is its use...?
Does SuperOneClick works on Nexus One stock rom 2.3.6?
I went for it and it works. i now have root on my N1 stock 2.3.6!
Hi,
I tryed this ] DooMLoRD's Easy Rooting Toolkit [v4.0] and get this message, can anyone help me?
http://kepfeltoltes.hu/view/120901/r00t_www.kepfeltoltes.hu_.jpg
superoneclick gives almost the result...
whats this? How to do this through?! I'm disappointed and confused, please help!
thanks
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Thanks ✟
Moving to Q&A
Hi, I`m with my first Android and tried to root it using this tutorial (i'm with stock rom):
http://forum.xda-developers.com/showthread.php?t=1327599
Everything seemed to work fine, but it never asked me for root permission and each program that needs it, tells me that I have no root access.
filipelq said:
Hi, I`m with my first Android and tried to root it using this tutorial (i'm with stock rom):
http://forum.xda-developers.com/showthread.php?t=1327599
Everything seemed to work fine, but it never asked me for root permission and each program that needs it, tells me that I have no root access.
Click to expand...
Click to collapse
u have a GB device?which one?V20L/M?
Yeah. Stock V20l. I've got all the right messages, done everything as it saids. But when no program gives me root access.
I forgot to say... I bought this from someone who said that had already rooted it, but I couldn't get root access so I tried this tutorial.
filipelq said:
I forgot to say... I bought this from someone who said that had already rooted it, but I couldn't get root access so I tried this tutorial.
Click to expand...
Click to collapse
Do you have the ROM Manager installed? if yes...switch on wifi and select the clockworkmod choosing the LG Optimus2X and wait for it to be flashed.
Do you get that the apps dont have root access?
---------- Post added at 10:54 PM ---------- Previous post was at 10:47 PM ----------
just have a look at this thread....has some information about rooting....
http://forum.xda-developers.com/showthread.php?t=1458879
hope it helps you
ROM manager says that I cannot select clockworkmod cause I haven't got root permission
I've tried the tutorial to get root access a dozen times. In all of them things seems ok, but when I open apps that need root access, they tell me I don't have it.
filipelq said:
ROM manager says that I cannot select clockworkmod cause I haven't got root permission
I've tried the tutorial to get root access a dozen times. In all of them things seems ok, but when I open apps that need root access, they tell me I don't have it.
Click to expand...
Click to collapse
Personally i think that there is some problem....try rebooting both your computer and the O2X and then restart the rooting process....before that read the thread a bit carefully...might be you are missing something...the rooting process normally works good...
I tried this one and think it worked.
http://forum.xda-developers.com/showthread.php?t=953182
Thanks for the help
More problems...
Root Check Basic says it's rooted;
Busybox installer also says it's rooted. It installs but if I open it again it says Busybox isn't installed.
Titanium Backup says it isn't rooted. FasterFix also.
Is there anyway to go back to zero and do it all again?
Update superuser. Reboot then try again..
Download rom manager flash the recovery.
Sent from my Optimus 2X using Tapatalk
try to get back to stock and re-do things....
http://forum.xda-developers.com/showthread.php?t=1327929
I flashed it again with v20l and then did the tutorial and it worked. Thanks
filipelq said:
I flashed it again with v20l and then did the tutorial and it worked. Thanks
Click to expand...
Click to collapse
Good it worked....
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