[Q] ICS 4.0.3 ROM Manager Problem - Nexus S Q&A, Help & Troubleshooting

I followed the guide on General forum to flash ICS 4.0.3 stock but my ROM Manager Premium isn't working properly.
Flash ClockworkMod, Reboot into Recovery works fine. It seems like everything else works too........
BUT Fix Permission. When I try to run it, it says 'An error occured while attemping to run privileged commands!'
Titanium Back Pro has green check marks on everything including Root access.
SuperUser and other apps that needs root access seems to work fine.
I downloaded Root Checker Basic and it says that my Nexus S is rooted.
Voodoo OTA Rootkeeper has all check marked as well.
Fix permission works fine on CWM recovery and I see CWM recovery when I reboot in recovery, not stock recovery.
Could anyone help me out with this problem... Thank you!

Just tried and same thing....not sure rom manager might need to be updated
Sent from my Nexus S using xda premium

demo23019 said:
Just tried and same thing....not sure rom manager might need to be updated
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
Hopefully that is the cause of the problem. I will try contact the developer.

Related

[Q] root lost after ota gingerbread 2.3.6

Formerly my nexus s 9023 was 2.3.3, when I got the ota I was super excited and careless, I installed the ota and lost my superuser app but my bootloader is still unlocked, how can I really reinstall superuser on my device? Thanks in advance
Sent from my Nexus S using XDA Premium App
Go to this link http://androidsu.com/superuser/
Then download superuser for ics and flash it.
Sent from my Nexus S from Tapatalk
ljordan2 said:
Go to this link http://androidsu.com/superuser/
Then download superuser for ics and flash it.
Sent from my Nexus S from Tapatalk
Click to expand...
Click to collapse
Sir my Current version is gingerbread 2.3.6 will superuser for ICS work on this version?
Mario Christian Oquias said:
Sir my Current version is gingerbread 2.3.6 will superuser for ICS work on this version?
Click to expand...
Click to collapse
Oh my bad, it's suppose to be superuser for eclair/froyo/gingerbread/ics. So it's the same thing.
Sent from my Nexus S from Tapatalk
ljordan2 said:
Oh my bad, it's suppose to be superuser for eclair/froyo/gingerbread/ics. So it's the same thing.
Sent from my Nexus S from Tapatalk
Click to expand...
Click to collapse
Sir installed it and tried to run superuser and just closes without errors, tried rebooting and check if the device is really unlocked ,at bootloader still said its unlocked. hmn, everything works fine, except the apps that require root, my voodoo said it had driver errors .
Mario Christian Oquias said:
Sir installed it and tried to run superuser and just closes without errors, tried rebooting and check if the device is really unlocked ,at bootloader still said its unlocked. hmn, everything works fine, except the apps that require root, my voodoo said it had driver errors .
Click to expand...
Click to collapse
Weird. Did you flash superuser? Or just installed it as an apk file?
Sent from my Nexus S from Tapatalk
Mario Christian Oquias said:
Sir installed it and tried to run superuser and just closes without errors, tried rebooting and check if the device is really unlocked ,at bootloader still said its unlocked. hmn, everything works fine, except the apps that require root, my voodoo said it had driver errors .
Click to expand...
Click to collapse
oops sorry my bad i didnt flashed it thats why it didnt worked... gonna try to flash it now, this will take a while, my recovery is showing a android with a triangle inside it is a exclamation mark, is this normal? i know its gonna take a couple of mins or more...will get back to you after this is done,
ljordan2 said:
Weird. Did you flash superuser? Or just installed it as an apk file?
Sent from my Nexus S from Tapatalk
Click to expand...
Click to collapse
it said :
E:failed to verify whole-file signiture
E:signiture verification failed
installation aborted
Maybe I need to wipe data
Sent from my Nexus S using XDA Premium App
Try the file from http://www.nexusshacks.com there is a super user for gb there.
Sent from my Nexus S using XDA App
[solved] root lost after ota gingerbread 2.3.6
i did it, the fault was in recovery, during OTA i lost the recovery CWM recovery and needed to re install it...thats why i cant flash the superuser app... now everything is ok fine and great! cheers!

Bad Binary

Hi all,
I Know my Thunderbolt is rooted correctly because I am able to use certian rooted only apps. But when I go into superuser to update binaries it tells me that
1. It cannot gain root access
2. It says the new binaries are bad
3. Overall fail.
There was a similar post on rootzwiki about this, and in that post was a su.zip file that i manually placed in the /system/bin which i overwrote the existing. Still giving me the bad binaries error etc... is there something I am doing wrong? or a new fix avail??
Thanks
PS...also while I'm here i posted this on rootzwiki also but no avail...somewhat on the same lines as what i posted above but with more info about the bootloader.
Thanks
I just picked up a preowned thunderbolt....
currently :
Android Version - 2.3.4
HTC Sense Verison - 2.1
Software Number - 2.11.605.9
.
HBOOT - 6.04.1002
Radio - 1.4.8.00.0.930.w_3
just wondering if this is the most current, and root-able\ s-off friendly software for the thunderbolt. It was already rooted and revolutionary.io hence the bootloader saying so. But for some reason no matter what, I cannot perform a full TB Restore, and cannot successfully update SU binaries ( tried the suFixer on the market..and tried manually putting the file in /system/bin/su . It either says cannot gain root access or insuffiant privileges errors. I can't for the life of me figure wtf is going on. I've never had such difficulty/[problems rooting and customizing any other HTC ( or android phone) before. can anyone help
Run the all in one tool again
Don't update binarys there's issues with the newest update. And reflash your custom recovery. Then flash one of the alrdy rooted stock roms or custom Rom .
Sent from my ADR6425LVW using xda premium
Kidney Poker said:
Don't update binarys there's issues with the newest update. And reflash your custom recovery. Then flash one of the alrdy rooted stock roms or custom Rom .
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
I start by flashing cwm via Rom manager premium. Then always flash the alternative amon recovery becUse I like it.better. is that the way to.go?
When re running the tool should I do the unroot then reroot? Is.there anything that will help me being able to use rooted apps run correctly hence the binary issue? Is this being worked on at all?
Sent from my HTC Thunderbolt. Using Tapatalk 2 premium.
I wouldn't flash anything through rom manager. That's just my opinion. Maybe unroot and then root again using the all in one tool might work.
Sent from my ADR6400L using Tapatalk 2
Go here and scroll down to update 2. There is a link to download a fixed binary that can be flashed in recovery.
http://androidsu.com/
Sent from my ADR6400L using Tapatalk 2
Another option that worked for me when I had my galxy s2 skyrocket. Go here http://forum.xda-developers.com/showthread.php?t=1538053
Download SuperSu and flash in cwm. It replaces su. And fixes the exact issue you are having
I really like supersu more than superuser. If I flash this in recovery will it replace superuser?
Sent from my ADR6400L using Tapatalk 2
Yes it will. Then when you reboot. Open supersu and allow it to update its binaries
Nice I'm going to try it.
Sent from my ADR6400L using Tapatalk 2

No root access

Hello!
So here's the deal: yesterday I decided to try out CM10.1 on my Nexus S. Being my first time rooting this phone all went well and I managed to flash the rom mostly without any problems. But my main concern is that after running root checker I got a message that my device isn't properly rooted... I did it just because I tried using ES file explorer in its root settings in order to delete a gallery2.apk file in system, which resulted in an error.
It's strange because I flashed the superuser zip before the rom and as far as I know CM10.1 comes with SU installed in it initially... Otherwise the ROM works perfect.
Do I need to flash everything from the beginning, doing another factory reset/wiping the cache? So far I've tried just to flash the superuser.zip from recovery (running 6.0.2.5 CWM recovery as far as I remember) and it didn't appear to root the device, although it said it installed successfully in the recovery. It may be something to do with the recovery or SU version? Any help is much appreciated!
Sent from my Nexus S using xda app-developers app
it's a problem about ES,
you should go to the settings and enable the root mode.
Jhyrachy said:
it's a problem about ES,
you should go to the settings and enable the root mode.
Click to expand...
Click to collapse
Yeah I know, tried that and ES said this feature cannot run on your phone... And the app doesn't appear in the superuser app either. Nothing does in fact. xD

[Q] Lost root access after installing supersu

I rooted my phone and installed jellyBAM rom, I later tried to install supersu from the app store and completely lost root access. Now i tried flashing supersu but i still cannot get root again. I removed supersu and tried flashing superuser but im still missing root. Is their any-way that I can regain my root access with your app because I would prefer to not have to do a factory reset. I know that jellyBAM has a built in superuser that's build into the settings.apk, Im assuming that this is the problem.
Demaier said:
I rooted my phone and installed jellyBAM rom, I later tried to install supersu from the app store and completely lost root access. Now i tried flashing supersu but i still cannot get root again. I removed supersu and tried flashing superuser but im still missing root. Is their any-way that I can regain my root access with your app because I would prefer to not have to do a factory reset. I know that jellyBAM has a built in superuser that's build into the settings.apk, Im assuming that this is the problem.
Click to expand...
Click to collapse
On some 4.3 ROMs superuser has to be enabled in the settings.. ??
Sent from my Full Android on Crespo using xda premium
Setting.Out said:
On some 4.3 ROMs superuser has to be enabled in the settings.. ??
Sent from my Full Android on Crespo using xda premium
Click to expand...
Click to collapse
It is in fact a 4.3 rom, do you have any ideas on where the setting may be?
It originally worked with its built in superuser. That superuser has practically no settings.
It just started working randomly.... I did not change anything so i do not understand it so thanks anyways, i guess we will never know what made it misbehave...
In setting -> developer option ->root access ->checked (Apps+Adb) then try again..
I hope this will help..
Sent from my Full Android on Crespo using xda app-developers app

No recovery anymore, Super SU problem

Hello,
I have rooted my phone, flashed TWRP 2.6.0.0 and CM 10.2 with the All-in-One Toolkit. Everything worked fine.
Then I installed the SUPER SU App from Chainfire and updated the Binary on the "normal" way. After that I uninstalled the app.
Today I wanted to install a newer version of TWRP. I used the GooManager. The download worked fine and the device rebooted. I can use the phone and I get into Bootloader but when I want to go to Recovery the device reboots and reboots....
My first thought was, that I don't have Root anymore because I uninstalled the Super SU App from Chainfire and I don't get any notifications when I start a app that needs root and the built in Super SU in the settings doesn't make any logs since some days. But Root Checker says that my device is rooted and for example Titanium Backup works fine although it's not in the list of apps with Super SU.
What can I do? Maybe trying to install the recovery with the GooManager again or new Rooting and Recovery installing with the Toolkit?
Sincerely,
May be you should flash back twrp 2.6.0.0 which was working for your phone and reinstall super su
I tried to root without the toolkit. I followed all steps and everything worked fine. But when the device rebooted after rooting I stopped in the bootscreen. I'm able to get into CM and use the phone without problems, but now the root is completely gone!
Can anyone help? I really don't know what to do now.
Edit: So, after rooting I have a Super SU app installed, but it's not able to update and not working...
Can you try with the twrp from this link:
http://flemmard.net/recoveries/openrecovery-twrp-2.6.3.0-ville-selinux.img
and root again
Sent from my One S using xda app-developers app
Okay, thanks. Wich root shall I try? With flashing the SuperSu with the recovery or with getting rooted over PC?
Thanks again.
Hevy12 said:
Okay, thanks. Wich root shall I try? With flashing the SuperSu with the recovery or with getting rooted over PC?
Thanks again.
Click to expand...
Click to collapse
Try flashing the supersu from recovery
Sent from my One S using xda app-developers app
ka_55 said:
Try flashing the supersu from recovery
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
I flashed the Recovery and the SuperSU. The recovery is installed but there is no root. But I can't uninstall the installed SuperSU apk from the old try of rooting that went wrong. I only can deactivate it. Should I do this and try flashing the SuperSU.zip again?
Thanks!
Sincerely,
Edit: Problem solved with the newer SuperSU version.

Categories

Resources