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.
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.
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!
Is there any touch recovery for ICS ROM
TWRP
Sent from my Galaxy Nexus using Tapatalk 2
onicrom said:
TWRP
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
That is for AOSP ROMs
melorib said:
That is for AOSP ROMs
Click to expand...
Click to collapse
What gave you that impression?!?!?!
Thread moved. Questions belong in Q&A section.
Also tidied up a little bit. Let's all play nice
kenkiller said:
What gave you that impression?!?!?!
Click to expand...
Click to collapse
"TWRP 2.3 is based on AOSP jelly bean sources"
Did you try on XXLQ2
melorib said:
"TWRP 2.3 is based on AOSP jelly bean sources"
Did you try on XXLQ2
Click to expand...
Click to collapse
Been using it on stock and custom ICS and custom JB since it was available.
install with root
kenkiller said:
Been using it on stock and custom ICS and custom JB since it was available.
Click to expand...
Click to collapse
i have HC now, and to install TWRP, i must root and SU.
in order to root, I have to install CWM 6.0.1 then root then install TWRP.
Can't i just root directly and then install TWRP from goo manager?
kenkiller said:
Been using it on stock and custom ICS and custom JB since it was available.
Click to expand...
Click to collapse
1) Install GooManager from the Play Store
2) Open GooManager and provide root permissions
3) Hit Menu (or the button with the 3 dots on your screen) and then Install OpenRecovery
Did all this, it looked like it installed, but after I reboot in recovery and all I get is CWM 6.0....
melorib said:
1) Install GooManager from the Play Store
2) Open GooManager and provide root permissions
3) Hit Menu (or the button with the 3 dots on your screen) and then Install OpenRecovery
Did all this, it looked like it installed, but after I reboot in recovery and all I get is CWM 6.0....
Click to expand...
Click to collapse
That's the way it worked for me from the beginning. No idea what went wrong for you.
Just updated to 2.3.1.0 2 days ago, everything went fine. I guess you'll have better luck in the TWRP thread.
kenkiller said:
That's the way it worked for me from the beginning. No idea what went wrong for you.
Just updated to 2.3.1.0 2 days ago, everything went fine. I guess you'll have better luck in the TWRP thread.
Click to expand...
Click to collapse
My guess is that it is not compatible with Dedraks kernel
At least I can go into recovery using GooManager app, no need to press for that...
The problem was CWM 6.0.1, installed everything else again, and TWRP works fine :good:
Re: [GUIDE] Root for Jelly Bean 4.1.1 or 4.1.2 OTA ***UPDATED 3/5***
Was running the OTA 4.1.2 stock
I followed the OP in the stated guide, everything went great.
Installed TWRP, rooted and unlocked.
I than flashed the latest CleanRom, that went well also.
Phone was and is running nicely. I had an update for superuser from the play store, which I took, but now I don't have root.
Can I just reinstall the superuser from TWRP or do I have to start over?
I have no trouble getting into TRWP.
Sent from my SCH-I535 using Tapatalk 2
Does this method of rooting wipe the phone data? Before this update I used a nowipe file. Is this the same?
Thanks
rontot said:
I had an update for superuser from the play store, which I took, but now I don't have root.
Click to expand...
Click to collapse
If you're using SuperSU, in the Settings there's Cleanup/Reinstall for reinstallation from Google Play. Maybe try that.
SempaiMatt said:
If you're using SuperSU, in the Settings there's Cleanup/Reinstall for reinstallation from Google Play. Maybe try that.
Click to expand...
Click to collapse
I do not have any settings in the Superuser app to reinstall/cleanup. I have uninstalled the update from the app store.....
Really wondering if I install the Superuser from TWRP do I need to reflash the VRALEC Bootchain first?
I have went ahead and installed the updated binary from in TWRP. That gave me root again.
Case closed......
Thanks
Sent from my SCH-I535 using Tapatalk 2
I was just trying to flash the alpha build 2 of KitKat 4.4 on my nexus s when suddenly in between it failed and said No file_ contexts set_ metadata rexursive_ some changes failed.. Something like that and failed to flash.. I have the latest version of recovery. Wiped data, cache, dalvik cache, system but it is still like this..
Sent from my Nexus S using xda app-developers app
Problem occured flashing 4.4 KitKat
Did you you use the latest CWM recovery which is ver. 6.0.4.3? Atm that's the only one able to flash aosp kitkat 4.4.
Hi guys. My problem is different from the OP's.
After flashing the alpha 2 I can no longer boot into Recovery. Now when I am in the bootloader and select Recovery the phone reboots normally into Android.
Also SU is requesting to update binaries, but the update fails from the app. Was thinking about flashing it again but without getting to Recovery it is not possible..
Cheers
filipeglfw said:
Hi guys. My problem is different from the OP's.
After flashing the alpha 2 I can no longer boot into Recovery. Now when I am in the bootloader and select Recovery the phone reboots normally into Android.
Also SU is requesting to update binaries, but the update fails from the app. Was thinking about flashing it again but without getting to Recovery it is not possible..
Cheers
Click to expand...
Click to collapse
Do you still have superuser function? Outdated is fine if your phone will grant su requests.. If you have su get the CWM app and have it update your recovery..
Sent from my Nexus S using XDA Premium 4 mobile app
Setting.Out said:
...get the CWM app and have it update your recovery..
Click to expand...
Click to collapse
Actually ROM Manager downgraded the CWM to the non-touch version from the touch one that I had downloaded from their site.
It is working well now though... I can live with the non-touch version
Thanks a lot!
filipeglfw said:
Actually ROM Manager downgraded the CWM to the non-touch version from the touch one that I had downloaded from their site.
It is working well now though... I can live with the non-touch version
Thanks a lot!
Click to expand...
Click to collapse
Now that your recovery is back, reflash the touch version..
Sent from my Nexus S using XDA Premium 4 mobile app