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!
Related
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.
So I just got some type of OTA update from Verizon, I have an unlocked bootloader as well as rooted. Can I install this update or will it brick? The file is under /cache/fota/update.zip 30.92mb. I thought if you was rooted you couldn't even get OTA's. Any ideas? I renamed the file so it wouldn't update even though it asked me when to install and I entered 10pm tonight to retry.
Sent from my SCH-I535 using xda app-developers app
It's a pretty major security patch so hopefully someone here puts it in a package for flashing. Someone else said they just unlocked again immediately after but I'm not sure how to best approach it for you.
Sent from my SCH-I535 using Tapatalk 2
---------- Post added at 05:31 AM ---------- Previous post was at 05:29 AM ----------
Rooting doesn't do anything about receiving updates, it's a particular file that is phoning home.
Sent from my SCH-I535 using Tapatalk 2
bskarpa said:
So I just got some type of OTA update from Verizon, I have an unlocked bootloader as well as rooted. Can I install this update or will it brick? The file is under /cache/fota/update.zip 30.92mb. I thought if you was rooted you couldn't even get OTA's. Any ideas? I renamed the file so it wouldn't update even though it asked me when to install and I entered 10pm tonight to retry.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Do you have a rom? If not people are saying they installed update and rooted device again.
I just got it this morning as well.... I'm stock rooted and I don't want the update. Do I have to accept it? Do I need to un-root? What will happen to my Google Wallet & Google Now?
I'd like to know also, I am stock rooted, unlocked and don't know if I should accept the update or not??
I got the same update but it flashed itself into recovery and then failed to install the update. Says "install aborted"
pmdied said:
I got the same update but it flashed itself into recovery and then failed to install the update. Says "install aborted"
Click to expand...
Click to collapse
You are right, I clicked "OK", it rebooted and went into CWM. I clicked "reboot now", when the phone finished booting I got an error message. Hopefully it won't continue doing this.
No I'm on a stock rooted ROM, it tried to install just now and failed as well.
Sent from my SCH-I535 using xda app-developers app
This is because you all most likely have a custom recovery like TWRP or CWM and it can only install on stock recovery. If you freeze sdm1.0 it wont keep asking you to update
Tap'n
bskarpa said:
So I just got some type of OTA update from Verizon, I have an unlocked bootloader as well as rooted. Can I install this update or will it brick? The file is under /cache/fota/update.zip 30.92mb. I thought if you was rooted you couldn't even get OTA's. Any ideas? I renamed the file so it wouldn't update even though it asked me when to install and I entered 10pm tonight to retry.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I've heard that to be safe, you need to re-lock the boot loader, un-root, and go back to stock in order to accept the updates.
There is a guide to do that here: http://forum.xda-developers.com/showthread.php?t=1867253
mooremh said:
I've heard that to be safe, you need to re-lock the boot loader, un-root, and go back to stock in order to accept the updates.
There is a guide to do that here: http://forum.xda-developers.com/showthread.php?t=1867253
Click to expand...
Click to collapse
Thanks yall!
I updated to newest ota g7 and rooted now. But can I push the aboot in terminal like I originally did? I only ask cause of all the issues I see with ez unlock. I like the manual way anyhow
Sent from my SCH-I535 using Tapatalk 2
I just flashed Scott's Rom latest vlrag7 and now my device says up to date:thumbup:
Sent from my SCH-I535 using xda app-developers app
mooremh said:
I've heard that to be safe, you need to re-lock the boot loader, un-root, and go back to stock in order to accept the updates.
There is a guide to do that here: http://forum.xda-developers.com/showthread.php?t=1867253
Click to expand...
Click to collapse
You are okay to be rooted and do a update. I do it all the time, it just unroots you and you have to rerun ur rooting. As for the bootloader i lock it before a update
Sent from my SCH-I535 using Tapatalk 2
hopesrequiem said:
I updated to newest ota g7 and rooted now. But can I push the aboot in terminal like I originally did? I only ask cause of all the issues I see with ez unlock. I like the manual way anyhow
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
If you use version 1.2 there isn't any issues. The 1.4 in the market of the one with issues. There's a thread somewhere in here that you can download the older versions that work correctly still
Tap'n
Just find ez-unlock in the play store and click on the link in the description. It will take you to the app's website,which has links for all versions.
Sent from my SCH-I535 using xda app-developers app
Ok so i FXZ back to stock, and i uninstalled A2Bootstrap, installed Busybox and updated to latest version it installed to system/xbin. Now i installed BMM and try to install and i get a error 'Wrong BMM busybox" what did i do wrong?
Darell3 said:
Ok so i FXZ back to stock, and i uninstalled A2Bootstrap, installed Busybox and updated to latest version it installed to system/xbin. Now i installed BMM and try to install and i get a error 'Wrong BMM busybox" what did i do wrong?
Click to expand...
Click to collapse
Did you have a2 bootstrap installed previously... And did you do the edits required for the boot menu manager to work??
Sent from my MB865 using XDA Premium HD app
nikhJ said:
Did you have a2 bootstrap installed previously... And did you do the edits required for the boot menu manager to work??
Sent from my MB865 using XDA Premium HD app
Click to expand...
Click to collapse
Yeah, just fix it i guess, all i wanted was stock 4.0.4 so i flashed AT&T version for my stock my original is TNZ.
Darell3 said:
Yeah, just fix it i guess, all i wanted was stock 4.0.4 so i flashed AT&T version for my stock my original is TNZ.
Click to expand...
Click to collapse
How did you fix the issue? I keep getting the busy box error when i try to install to system 1.
ins5736 said:
How did you fix the issue? I keep getting the busy box error when i try to install to system 1.
Click to expand...
Click to collapse
I just flashed AT&T ICS and install BMM from there.
wrong bmm busy box
samsung nexus s 4 g .I seen on the play store description it say it was only for 2 motorola devices so that may be my issue.If not does anyone know how I could fix this to work .I installed latest busybox .I am running slimrom if that matters.
I face the same issue as well. I have a Huawei G700-U00 running ColorOS 4.2.2... please help
androKP said:
I face the same issue as well. I have a Huawei G700-U00 running ColorOS 4.2.2... please help
Click to expand...
Click to collapse
Boot Menu Manager is only for Motorola's OMAP4 device, so on any other device except tegra it wont work.
Sent from my Atrix 2 using Tapatalk.
Yeah Ive been getting this as well. Just dont install busybox from the Play Store. Killed BMM on the install I had and needed to reflash.
I just ignore it and it seems to work alright for the most part. Only noticed this on a custom Roms. Stock rooted doesnt seem to have the problem even when using the busybox installer from play store.
hi
this morning i have received the OTA, i ran it and it successfully updated to 4.4.2 however i no longer have root access.
so do i have to redo everything again (backup everything and reboot again) or is there any quick way to fix this?
Sent from my Nexus 5 using xda app-developers app
its like no one searches anymore...
just reflash a custom recovery and then flash supersu.zip again.
redjersey said:
hi
this morning i have received the OTA, i ran it and it successfully updated to 4.4.2 however i no longer have root access.
so do i have to redo everything again (backup everything and reboot again) or is there any quick way to fix this?
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
Of course you lost root. That's normal. Just re-root. How did you root before?
jd1639 said:
Of course you lost root. That's normal. Just re-root. How did you root before?
Click to expand...
Click to collapse
bet he used a toolkit.
Zepius said:
bet he used a toolkit.
Click to expand...
Click to collapse
I'm guessing too.
Shoulda just flashed su zip after flashing the update then reboot
Sent from my Nexus 5 using Tapatalk
I was using this method:
http://www.youtube.com/watch?v=w3beFx-3Ic4
to root my nexus 5.
redjersey said:
I was using this method:
http://www.youtube.com/watch?v=w3beFx-3Ic4
to root my nexus 5.
Click to expand...
Click to collapse
Use this method http://forum.xda-developers.com/showthread.php?p=47025283
installed supersu from google play, now it's fine
redjersey said:
installed supersu from google play, now it's fine
Click to expand...
Click to collapse
I'm a bit surprised that installing the app from the market fixed it..... maybe I am missing something... LOL
Zepius said:
bet he used a toolkit.
Click to expand...
Click to collapse
hell guys, why be snobs?
ive been around here for many years, had many, many devices, probably a hundred roms, and I use the toolkit because I find it easier...and have had no major problems.
so
After rooting with the toolkit, SuperSU was not showing up as an app. Installing it via play store worked for me too... - it asked if I wanted to update binaries, I chose normal instead of via twrp, and after doing that and a reboot, all is good...
cheers
Mark.
redjersey said:
installed supersu from google play, now it's fine
Click to expand...
Click to collapse
If you accepted an OTA you will have to re-root manually or with the tool kit you originally used.
You can't simply install SuperSU from the Play Store and regain root. Sure the app will install (anyone can do this) but the binaries will be absent (i.e. no root).
You can test this by opening SuperSU. When you open it, it will tell you if it's working correctly.
Sent from my Nexus 5 using Tapatalk
Whenever superSu asks for permission to run a root app my screen becomes unresponsive. Timer runs out and i am not able to apply grant permission. Help. This didnt use to happen when i was earlier rooted with towelroot. Right now also i ised towelroot
Have you tried re-flashing the supersu zip?
jameson21 said:
Have you tried re-flashing the supersu zip?
Click to expand...
Click to collapse
Yes. Didnt work.
Btw by reflash the zip file you mean reinstall it from pkay store, right?
Pardon the ignorance. Just found out that flashing a zip file and installing apps from play store are 2 different things.
Well my bootloader is locked and neither do i have a custom recovery installed. So flashing doesnt seem to be an option right now.. If i am not missing anything.
Are you running 5.0? If so how the heck did you root with towelroot? AFAIK you can not root 5.0 that way. Maybe that is a problem.
Sent from my Nexus 5 using Tapatalk
frenziedfemale said:
Are you running 5.0? If so how the heck did you root with towelroot? AFAIK you can not root 5.0 that way. Maybe that is a problem.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
No no. I am on kitkat only
Tried reinstalling it. This is what came up. I am on android 4.4.4 btw
You need to flash the supersu zip using fastboot:
teamandroid. com/2014/06/19/root-nexus-5-android-444-ktu84p-kitkat/2/ (you're going to have to fix that link because I have under 10 posts so the forum won't let me post..)
Additionally you need to have an unlocked bootloader
jameson21 said:
You need to flash the supersu zip using fastboot:
teamandroid. com/2014/06/19/root-nexus-5-android-444-ktu84p-kitkat/2/ (you're going to have to fix that link because I have under 10 posts so the forum won't let me post..)
Additionally you need to have an unlocked bootloader
Click to expand...
Click to collapse
Why is it happening now? Didnt use to happen earlier..
You say you were rooted ...why did you re-root? It looks like you are no longer rooted. Did you do an update or anything?
Sent from my Nexus 5 using Tapatalk
frenziedfemale said:
You say you were rooted ...why did you re-root? It looks like you are no longer rooted. Did you do an update or anything?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I was rooted. I unrooted because i thought it was required to update to lollipop. But i dont have any intention to update to L for now.
rahul9five said:
I was rooted. I unrooted because i thought it was required to update to lollipop. But i dont have any intention to update to L for now.
Click to expand...
Click to collapse
To get root again either flash the latest CF Auto Root in fastboot or flash the latest superSU.zip in recovery or flash a pre-rooted custom rom in a custom recovery.