I have one problem. When I try to install new ROM, the recovery (TWRP) says that my device isn't rooted (I tried it on few ROMs, always the same...). Also, in the things that are shown when the ROM is installing (like mounting data, system, installing system files etc.) ins't installing superuser (I think that should be there)
Is there somebody to help me? Thank you...
XTheMike said:
I have one problem. When I try to install new ROM, the recovery (TWRP) says that my device isn't rooted (I tried it on few ROMs, always the same...). Also, in the things that are shown when the ROM is installing (like mounting data, system, installing system files etc.) ins't installing superuser (I think that should be there)
Is there somebody to help me? Thank you...
Click to expand...
Click to collapse
TWRP search whether the superuser app is install in your phone or not,and roms like cyanogenmod have a inbuilt superuser ,so you should ignore that. :highfive:
But it seems to be.happening only on sense based roms... And it won't boot either I install it or not...
XTheMike said:
But it seems to be.happening only on sense based roms... And it won't boot either I install it or not...
Click to expand...
Click to collapse
Search for super su apk in xda you will find it..
flash the rom.. after completing flash the super su reboot..
XTheMike said:
But it seems to be.happening only on sense based roms... And it won't boot either I install it or not...
Click to expand...
Click to collapse
and here comes a superuser zip out of nowhere
Thanks for your help It works now...
Related
Hey guys,
I am pretty new to rooting, and I am sorry if I am noob to the max.
I just rooted my Nexus S 4G, and installed ROM Manager v5.0.0.7. I want to put cm9 (the release candidate) on my phone. Every time I open ROM Manager, and hit Flash ClockworkMod Recovery, it says "An error occurred while attempting to run privileged commands!"
Thinking this was an issue with the root access ROM Manager has, I looked at the app list in Super User, and nothing is there.
How can I fix this and get cm9 on my phone??
Thanks for your help.
EDIT: I uninstalled both SuperUser and ROM Manager, got the latest version of SuperUser (v3.1.3) and ROM Manager. When I hit Flash CWM, the blue bar at the top goes almost all of the way, then the program quits responding.
Why are you flashing a recovery when you already installed one??
you have not given Rom manager root access, hence nothing in the superuser app. try clear su's data and cache, and go to its settings>security>Automatic response>Prompt and clear rom manager's data and cache as well, and try again. this time, you will encounter a message titling superuser request and click allow and remember options and you're on your way to the ICS party, although im leaving in 2 weeks in favour of jellybean
Alternative: install TWRP, and flash it via adb, and use reboot recovery command in terminal
That didn't work.
MikeMBau said:
That didn't work.
Click to expand...
Click to collapse
what didn't go right? no prompt? more info please... and make sure you're actually rooted, not just install superuser app
Do you or do you not already have a recovery on your phone? Installing superuser =/= rooted. If you don't you should manually install a recovery so that: A. You have a better understanding of what you did (it's always better to know what you're doing when you're messing around with your phone) and B. If something goes wrong you know exactly what caused it.
If you already have recovery why are you bothering with Rom manager? Just wipe cache and data (make a backup first) then flash the Rom.
@063_XOBX it looks to me as if he didn't root, thus the rom manager error message, privileged commands=root required commands, and rom manager's not getting it. or it's the superuser app didn't allow it to access root
Billchen0014 said:
@063_XOBX it looks to me as if he didn't root, thus the rom manager error message, privileged commands=root required commands, and rom manager's not getting it. or it's the superuser app didn't allow it to access root
Click to expand...
Click to collapse
That was my first conclusion too, I just wanted to make sure before I flat out said that he wasn't rooted.
Just wanted to update the situation:
I definitely was rooted at the time of posting this, as I could tell by the open lock on the bottom of the boot screen under Google and it said S-OFF when I would boot into recovery.
I ended up just unrooting the phone and rerooting, and this seemed to fix whatever bug I had.
A while back, I always rooted and unrooted my Nexus S with no problems at all. Now whenever I try to root it, it just goes wrong. I've tried TWRP & CWM, CWM used to always work but now it just messes up. Both TWRP and CWM both give me an error that say Installation Aborted when I try to install a custom rom. I've redownloaded the rom from different browsers and even different PCs but nothing working, still that same error. Does anyone have a guide that is 100% to work without any errors during the process?
What guide are you using?
paul96 said:
What guide are you using?
Click to expand...
Click to collapse
I used this one: http://nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread/
1. Make sure you're running one the more recent versions of the custom recovery. You probably are but there are issues with older versions so just make sure.
2. Boot into what ever recovery you pick and do a full wipe. That is everything gets wiped but your SD card. Factory reset. Format /system etc.
3. Flash your ROM and gapps if they are seperate.
You should not get any errors. If your recovery is current and your flashing a new rom onto a fully wiped system and you still get a error either you're screwing something up or you may have a hardware problem.
To rule out a hw problem flash the factory images with fastboot. If those flash normally and everything works it is almost certainly user error.
albundy2010 said:
1. Make sure you're running one the more recent versions of the custom recovery. You probably are but there are issues with older versions so just make sure.
2. Boot into what ever recovery you pick and do a full wipe. That is everything gets wiped but your SD card. Factory reset. Format /system etc.
3. Flash your ROM and gapps if they are seperate.
You should not get any errors. If your recovery is current and your flashing a new rom onto a fully wiped system and you still get a error either you're screwing something up or you may have a hardware problem.
To rule out a hw problem flash the factory images with fastboot. If those flash normally and everything works it is almost certainly user error.
Click to expand...
Click to collapse
Alright, thanks Do you recommend that I root my Nexus S or should I wait for the Jelly Bean update? I've rooted before and I enjoyed it but now I don't see that many reasons to root, do you have any good reasons?
I have many. My reasons for root don't matter. If you don't have a reason for root then don't root. Its that simple really.
Make sure you're on a stock 4.0.4 rom. When the ota is out install it.
If you want just root on either os at any time just flash su.zip from custom recovery. Its that simple. Having root on a stock rom does not affect the ota process.
albundy2010 said:
I have many. My reasons for root don't matter. If you don't have a reason for root then don't root. Its that simple really.
Make sure you're on a stock 4.0.4 rom. When the ota is out install it.
If you want just root on either os at any time just flash su.zip from custom recovery. Its that simple. Having root on a stock rom does not affect the ota process.
Click to expand...
Click to collapse
What are your reasons for root? Please share?
Getting rid of stuff I don't want in a ROM.
Apps that do things that require root.Titanium backup/autoruns adaway ( ad blocker app alone could be its one point) etc
Changing kernel settings. Bid/bin clocks volts etc.
Being able to have a replacement launcher use the ICS style widget drawer.
Lastly , I simply just can't see having a computer that I don't have root/admin rights to. Its my damn device and I do what I want.
albundy2010 said:
Getting rid of stuff I don't want in a ROM.
Apps that do things that require root.Titanium backup/autoruns adaway ( ad blocker app alone could be its one point) etc
Changing kernel settings. Bid/bin clocks volts etc.
Being able to have a replacement launcher use the ICS style widget drawer.
Lastly , I simply just can't see having a computer that I don't have root/admin rights to. Its my damn device and I do what I want.
Click to expand...
Click to collapse
Oh cool. There is this project that some members from XDA are working on called Sense4All and they are porting Sense to many devices. Im probably going to wait until a fully functionable release is available for the Nexus S. I do like AOKP a lot, so that might be a reason for why I'll root.
You seem to be a little confused with some terms. Root is simply being able to grant superuser permission.
You don't need to root to flash a custom rom on a nexus. Just a unblocked bootloader. You could run aokp or any other rom without root if you wanted to.
albundy2010 said:
You seem to be a little confused with some terms. Root is simply being able to grant superuser permission.
You don't need to root to flash a custom rom on a nexus. Just a unblocked bootloader. You could run aokp or any other rom without root if you wanted to.
Click to expand...
Click to collapse
Oh, I never knew that, haha. Is it possible to flash a custom kernel with an unlocked bootloader or does that require root access?
m1l4droid said:
No you just need a custom recovery. But using that kernel's mods, like BLN, OC, UV, touchwake, etc, requires apps that need root, like NSTools, SetCPU, etc.
Click to expand...
Click to collapse
Oh alright. Now I really wanna root + install a custom rom. Do any of you have a full 100% fully working guide for rooting Nexus S and which rom should I flash first? I already know what kernel I want.
http://forums.acsyndicate.net/showthread.php?2024-ACS-Nexus-S-One-Click-Root-V4-0
leap_ahead said:
http://forums.acsyndicate.net/showthread.php?2024-ACS-Nexus-S-One-Click-Root-V4-0
Click to expand...
Click to collapse
Thank you so much! I rooted my phone with CWM recovery installed and Paranoid Android + gapps installed
Hi all!
I rooted my S4 with the all-in-one toolkit but I have the feeling that something didn't worked out. First thing, I don't get the boot screen with the red writing..I still have the normal one. It installed TWRP recovery alright and it works well. It installed SU, but i had troubles installing busybox..it gave errors about permission, even if I gave the installer root permission at launch..I had to install busybox through recovery. Other thing it didn't work is uninstalling system apps..I tried with Titanium, Anttek app manager and even with manually delete the apks, but after a reboot the apps and the apks reappeared..
All this things made me think that something went "not-fully-ok" in the unlocking process...
Is there something I can do to verify this?
Edit: forgot to say i'm on stock rom, last update.
Jeeza said:
Hi all!
I rooted my S4 with the all-in-one toolkit but I have the feeling that something didn't worked out. First thing, I don't get the boot screen with the red writing..I still have the normal one. It installed TWRP recovery alright and it works well. It installed SU, but i had troubles installing busybox..it gave errors about permission, even if I gave the installer root permission at launch..I had to install busybox through recovery. Other thing it didn't work is uninstalling system apps..I tried with Titanium, Anttek app manager and even with manually delete the apks, but after a reboot the apps and the apks reappeared..
All this things made me think that something went "not-fully-ok" in the unlocking process...
Is there something I can do to verify this?
Click to expand...
Click to collapse
Hi, are you using a custom ROM or the stock ROM? The apps reappearing issue is on the stock ROM and happens on the 4.1 Jelly Bean ROM because HTC in their infinite wisdom (lmao who did I copy) introduced a write-protect feature in the Jelly Bean kernel. So installing stuff will work, but only in recovery when the kernel isn't active. I assume this is how you installed Superuser - through recovery. To overcome this issue you can flash a custom ROM like ViperOneS or if you don't want a custom ROM you can flash a zip in recovery which I will provide the link to shortly
Edit: page 212 of the official jelly bean thread in the general forum
Sent from my One S using Tapatalk 2
... Or you can flash custon kernel (I.e.elementalS 2.5) if you want to stay on stock and have no write protection......
Sent from my HTC One S using xda app-developers app
tominozh said:
... Or you can flash custon kernel (I.e.elementalS 2.5) if you want to stay on stock and have no write protection......
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Until CM 10.1 reaches stable, I think i'll stay with stock rom..does a new kernel provides other benefits?
Jeeza said:
Hi all!
I rooted my S4 with the all-in-one toolkit but I have the feeling that something didn't worked out. First thing, I don't get the boot screen with the red writing..I still have the normal one. It installed TWRP recovery alright and it works well. It installed SU, but i had troubles installing busybox..it gave errors about permission, even if I gave the installer root permission at launch..I had to install busybox through recovery. Other thing it didn't work is uninstalling system apps..I tried with Titanium, Anttek app manager and even with manually delete the apks, but after a reboot the apps and the apks reappeared..
All this things made me think that something went "not-fully-ok" in the unlocking process...
Is there something I can do to verify this?
Edit: forgot to say i'm on stock rom, last update.
Click to expand...
Click to collapse
is this a device you have unlocked and bought brandnew yourself? or used?
mayby you dont have full root (after flashing root)
if your on JB maybe you have to flash the edited init d file for full r/w in system
http://forum.xda-developers.com/showpost.php?p=36099646&postcount=2111
---------- Post added at 07:32 PM ---------- Previous post was at 07:30 PM ----------
Jeeza said:
Until CM 10.1 reaches stable, I think i'll stay with stock rom..does a new kernel provides other benefits?
Click to expand...
Click to collapse
nightlys are stable enough to be daily drivers.
real187 said:
is this a device you have unlocked and bought brandnew yourself? or used?
mayby you dont have full root (after flashing root)
if your on JB maybe you have to flash the edited init d file for full r/w in system
http://forum.xda-developers.com/showpost.php?p=36099646&postcount=2111
Click to expand...
Click to collapse
Thank you all for your replies! I'll try and flash this zip with twrp..the phone was used, but the previous owner did nothing like flashing stuff, or rooting..
Does flashing this package allows me to permanently delete system apps?
And are there real benefits with flashing a non-stock kernel?
Meanwhile, bought flash image gui, flashed the kernel with it, and again with recovery. Now I can uninstall system apps permanently!
Jeeza said:
Hi all!
I rooted my S4 with the all-in-one toolkit but I have the feeling that something didn't worked out. First thing, I don't get the boot screen with the red writing..I still have the normal one. It installed TWRP recovery alright and it works well. It installed SU, but i had troubles installing busybox..it gave errors about permission, even if I gave the installer root permission at launch..I had to install busybox through recovery. Other thing it didn't work is uninstalling system apps..I tried with Titanium, Anttek app manager and even with manually delete the apks, but after a reboot the apps and the apks reappeared..
All this things made me think that something went "not-fully-ok" in the unlocking process...
Is there something I can do to verify this?
Edit: forgot to say i'm on stock rom, last update.
Click to expand...
Click to collapse
What version is your toolkit? 3.4?
It looks more like you S-Offed, because HBOOT didn't give a da*m about the red message when S-Offed.
You're running stock. Kernal reboot would force it to reinstall.
mr_verystock said:
What version is your toolkit? 3.4?
It looks more like you S-Offed, because HBOOT didn't give a da*m about the red message when S-Offed.
You're running stock. Kernal reboot would force it to reinstall.
Click to expand...
Click to collapse
On the Hboot screen it says clearly S-on...and i'm sorry but i didn't understand your "Kernal reboot would force it to reinstall"
Heyy devs I may use some help!
I am unable to install xposed framework on my fit since when I installed cm10.2. It was working perfectly when I was using cm10.1.
Some info you might use:-
1. Rom installed - cm10.2 rc2
2. No partition
3. No scripts
4. No performance patches
Help me as soon as possible
P.S. It says sumthng like it can not mount/write system!
And even root chekcer says I haven't got proper access!
Ifs there any way u can solve this???
I really need xposed installed on my system!
No idea man.
Ate you able to run other root apps?
panya_ck said:
Heyy devs I may use some help!
I am unable to install xposed framework on my fit since when I installed cm10.2. It was working perfectly when I was using cm10.1.
Some info you might use:-
1. Rom installed - cm10.2 rc2
2. No partition
3. No scripts
4. No performance patches
Help me as soon as possible
P.S. It says sumthng like it can not mount/write system!
And even root chekcer says I haven't got proper access!
Ifs there any way u can solve this???
I really need xposed installed on my system!
Click to expand...
Click to collapse
Are you using SuperSu? What version?
Have you tried re-flashing the SuperSu?
@nitin
I hv tried flashing superSU but got stuck in the bootloop !
donno wat version !?
Should flashing it with SuperSU shud do it ??
BTW thnx for ur rply !
@nitin
i tried to flash latest supersu....no luck though....rootchecker says the device doesnt hv proper root access ....
any idea ???
Me too have issues with supersu!! Need to re-install the ROM when I loose root access(sometimes...some apps still access superuser but not all of 'em)
& even some apps that usually work on gb/ics/jb(10.1) didn't run(force close) on cm10.2.
[Solved]
Done !
Flashed latest SuperSU using CWM 6.x.x.x !
older recoveries may not give proper access !:angel::cyclops::cyclops::cyclops:
Hello, i was looking for some diferent rom ( was using cm12.1) and wanted to try blisspop 6.0 , idk why it didnt work with cwm recovery so i tryed to instal twrp recovery, i saw i have to wipe all the data so i entered "advanced mode" and wiped everything except microsd and now i cant install any rom, every of them just write "E:Error executing updater binary in zip 'romname.zip' "
i was looking a bit, found some fixes, power off and let twrp install supersu, it offers it again anyway. Or it was some files to install, but im afraid cuz it was in topics for phones and idk if this files arent specificly for this phones... did anyone had same problem or know how to fix it?
siroga825 said:
Hello, i was looking for some diferent rom ( was using cm12.1) and wanted to try blisspop 6.0 , idk why it didnt work with cwm recovery so i tryed to instal twrp recovery, i saw i have to wipe all the data so i entered "advanced mode" and wiped everything except microsd and now i cant install any rom, every of them just write "E:Error executing updater binary in zip 'romname.zip' "
i was looking a bit, found some fixes, power off and let twrp install supersu, it offers it again anyway. Or it was some files to install, but im afraid cuz it was in topics for phones and idk if this files arent specificly for this phones... did anyone had same problem or know how to fix it?
Click to expand...
Click to collapse
ok fixed, just have to install lastest version of twrp, bliss pop 6.0 wont start anyway but atlast im abkle to install it or any other rom
siroga825 said:
ok fixed, just have to install lastest version of twrp, bliss pop 6.0 wont start anyway but atlast im abkle to install it or any other rom
Click to expand...
Click to collapse
Can you post a link or send it to me in a private message? and what twrp version you were running and the new one?
Mohdhamm said:
Can you post a link or send it to me in a private message? and what twrp version you were running and the new one?
Click to expand...
Click to collapse
im already back on stock rom on it but i belive lastest twrp from https://twrp.me/devices/nvidiahshieldtablet.html was the working one ....