After rooting the HTC One X (after received OTA JB) I installed custom recovery CWM and SuperSU (not on my phone). Now I need to install busybox, but the ones from Play store does not want to install. Is there any installable zip of last busybox, that I can install through recovery?
Thank you.
Related
Hi,
I'm actually on ARHD 5.0.0 but i still get no root access with SuperSU. Binary gets updated properly but apps like Adaway, Titanium Backup, etc, tell me that i don't have root access.
How is that possible? Bootloader unlocked via HTCDev, latest CWM Recovery, flashing ROM and matching boot.img without any problems but obviously no root.
Flashed the latest SuperSu as flashable CWM zip without any success using root-requirering-apps
Hope someone can help me, never has had any problems like this with my previous HTC devices
Okay, so I installed Clockword Recovery and ROM Manager so that I could get Jellybean early. And it was awesome. But now I'm getting bugged about the OTA update, and I kinda want that. Ofcourse, Clockwork Mod Recovery won't let me install OTA, so how can I go back to stock recovery? Because I dislike the idea of not having OTA updates anymore...
Hopefully before you get hundreds of rude entitled responses you should check out some of the stickies on the various forums. I believe there is one with a title that matches exactly what you are looking for
If not having stock recovery is the only problem (and there are a number of other reasons an OTA update could fail to install), you can definitely use ClockworkMod to install it.
If the update has already been downloaded to the phone, the zip file will be stored in /cache. Just boot into CWM and flash it. If the update hasn't been downloaded, grab zip file yourself (take a look at the OTA update URLs thread) and flash it using CWM.
If you're rooted, don't forget to also flash SuperSU before you reboot, or use some other method to maintain root. OTA updates will remove root regardless of how they are installed unless you take care.
Hi, i got my nexus flo a week ago. This is my first nexus device.I have some queries. I have unlocked the bootloader, installed twrp and rooted the device.
Will that prevent me getting OTA?
Also, does having unlocked bootloader and custom recovery cause failure to update the software?
(Not just the JSS15R but future updates to kitkat as well)
Also what is the odex and deodex in this thread? which one should i flash?
http://forum.xda-developers.com/showthread.php?t=2383059
littleromeo said:
Hi, i got my nexus flo a week ago. This is my first nexus device.I have some queries. I have unlocked the bootloader, installed twrp and rooted the device.
Will that prevent me getting OTA?
Also, does having unlocked bootloader and custom recovery cause failure to update the software?
(Not just the JSS15R but future updates to kitkat as well)
Also what is the odex and deodex in this thread? which one should i flash?
http://forum.xda-developers.com/showthread.php?t=2383059
Click to expand...
Click to collapse
Odex vs deodex: http://forum.xda-developers.com/showthread.php?t=2200349
If I understand well, updates will 'fail' with custom recovery, whereas the update is flashed the firmware version number shows the old version. Explained in the guides somewhere.
Sent from my Nexus 7 (2013)
littleromeo said:
Hi, i got my nexus flo a week ago. This is my first nexus device.I have some queries. I have unlocked the bootloader, installed twrp and rooted the device.
Will that prevent me getting OTA?
Also, does having unlocked bootloader and custom recovery cause failure to update the software?
(Not just the JSS15R but future updates to kitkat as well)
Also what is the odex and deodex in this thread? which one should i flash?
http://forum.xda-developers.com/showthread.php?t=2383059
Click to expand...
Click to collapse
Unlocked bootloader has no direct negative effect on ota installs.
With an unlocked bootloader you might do further actions which can affect the ota like modify or delete /system files. You might install an enhancement like apm. Those, among others, would prevent the ota update from completing.
Now normally root by itself would not prevent an ota update, but there was an issue with SuperSU v 1.51 and earlier which did prevent the ota install from completing. This was fixed in SuperSU v1.55 and above.
Installing twrp will not block the ota.
The ota will disable root and overwrite custom recovery by default.
If you would like to prevent that behavior, the easiest way is to
copy the ota update.zip and supersu update.zip to your virtual sdcard
boot into twrp
install ota update.zip
immediately (prior to reboot) re-install supersu
sfhub said:
Unlocked bootloader has no direct negative effect on ota installs.
With an unlocked bootloader you might do further actions which can affect the ota like modify or delete /system files. You might install an enhancement like apm. Those, among others, would prevent the ota update from completing.
Now normally root by itself would not prevent an ota update, but there was an issue with SuperSU v 1.51 and earlier which did prevent the ota install from completing. This was fixed in SuperSU v1.55 and above.
Installing twrp will not block the ota.
The ota will disable root and overwrite custom recovery by default.
If you would like to prevent that behavior, the easiest way is to
copy the ota update.zip and supersu update.zip to your virtual sdcard
boot into twrp
install ota update.zip
immediately (prior to reboot) re-install supersu
Click to expand...
Click to collapse
Thank you for the guide, updated to JSS15R. There were no touchscreen problems for me before the update and everything is just like before even after update. Hope someone comes up with a changelog soon.
I have an i747M, from Fido (rogers) running the stock 4.3 firmware. yesterday i tried to root it using odin to install CWM, and then CWM to install supersu.
after successfully installing supersu, i restarted the phone, and got knox blocking the app. i updated it from Play, but then i couldn't open it, and it said it can't install the binary. when my phone asked to update the security certificates, i (stupidly) agreed.
i downloaded the .zip for supersu 1.89, and tried installing that, with the same result, but this time i also can't uninstall supersu.
i've bumped my binary counter, but i'm back to basically stock now.
my goal is to install aokp. is there a way to do it without gaining root first?
if i install CWM through odin, can i flash the aokp rom from CWM?
will the phone reset the recovery?
is this risky?
You could try installing a pre-rooted Rogers rom from here: http://forum.xda-developers.com/showthread.php?t=1739426
I was not able to find a pre-rooted 4.3 for Fido and, since you intend to install a custom rom and recovery, the pre-rooted Rogers ROM might be a good place to start.
It's there a reason to install a rooted rom before aokp? As far as I can tell, I can install aokp without rooting at all.
or am I missing something?
Sent from my SGH-I747M using xda app-developers app
Yes, you can just install a custom ROM without rooting first.
I mentioned the prerooted ROM because you post said you wanted to install su.
Ok, please confirm i have this procedure correct:
1. i use Odin to install CWM
2. boot straight into CWM
3. from inside CWM, i flash the AOKP zip file, and then the gapps zip file
my understanding is that this will keep cwm as my recovery and install aokp with gapps.
am i missing anything?
audit13 said:
Yes, you can just install a custom ROM without rooting first.
I mentioned the prerooted ROM because you post said you wanted to install su.
Click to expand...
Click to collapse
Milothicus said:
Ok, please confirm i have this procedure correct:
1. i use Odin to install CWM
2. boot straight into CWM
3. from inside CWM, i flash the AOKP zip file, and then the gapps zip file
my understanding is that this will keep cwm as my recovery and install aokp with gapps.
am i missing anything?
Click to expand...
Click to collapse
Just make sure you flash a tar version of CWM that is meant for your phone.
I can't really speak about 4.3 because I'm on 4.1.2 but the method you described is the same method I used.
Milothicus said:
I have an i747M, from Fido (rogers) running the stock 4.3 firmware. yesterday i tried to root it using odin to install CWM, and then CWM to install supersu.
after successfully installing supersu, i restarted the phone, and got knox blocking the app. i updated it from Play, but then i couldn't open it, and it said it can't install the binary. when my phone asked to update the security certificates, i (stupidly) agreed.
Click to expand...
Click to collapse
If you want to kill Konx to enable root you can flash this knox removal script: http://forum.xda-developers.com/showthread.php?t=2507931
If you are just going to flash AOKP via CWM, this may not be necessary, but this is the answer to your Knox problem.
Hey guys,
I know there are tons of Superuser apps and root methods such as cf autoroot but I'm hoping someone knows is how to root the S4 (SGH-M919) and have Koush's Superuser.apk be your SU client. I don't want to use Chainfire or SuperSU or anything else. It seems 4.3 for me will only accept SuperSU but I was hoping to use the CWM Superuser as I do on all of my other devices. Would hate to have a different SU just on this one device. Any ideas on how to get superuser.apk working on 4.3 on the S4 (Stock, custom recovery, rooted with SuperSU for now).
T-Mobile Galaxy S4 (SGH-M919)
Android 4.3 (MK2 full with KNOX through ODIN)
Don't care about tripping KNOX
Daistaar said:
Hey guys,
I know there are tons of Superuser apps and root methods such as cf autoroot but I'm hoping someone knows is how to root the S4 (SGH-M919) and have Koush's Superuser.apk be your SU client. I don't want to use Chainfire or SuperSU or anything else. It seems 4.3 for me will only accept SuperSU but I was hoping to use the CWM Superuser as I do on all of my other devices. Would hate to have a different SU just on this one device. Any ideas on how to get superuser.apk working on 4.3 on the S4 (Stock, custom recovery, rooted with SuperSU for now).
T-Mobile Galaxy S4 (SGH-M919)
Android 4.3 (MK2 full with KNOX through ODIN)
Don't care about tripping KNOX
Click to expand...
Click to collapse
Method 1
Use Odin to install a custom recovery of your choice.
Boot to recovery.
Flash any Superuser.apk you want.
Using Odin to install the recovery won't root the current ROM. It will just give you a custom recovery. From the custom recovery you can install anything you want, including the Superuser.apk of your choice.
Method 2
Root it using whatever root method works even if it installs SuperSU.
Uninstall SuperSU through the 1 click feature in the app.
Boot to your custom recovery. (Will NOT be automatically installed with CF Auto Root. You will have to flash a recovery after rooting)
Flash Superuser.
Reboot. Enjoy goodness.
Skipjacks said:
Method 1
Use Odin to install a custom recovery of your choice.
Boot to recovery.
Flash any Superuser.apk you want.
Using Odin to install the recovery won't root the current ROM. It will just give you a custom recovery. From the custom recovery you can install anything you want, including the Superuser.apk of your choice.
Method 2
Root it using whatever root method works even if it installs SuperSU.
Uninstall SuperSU through the 1 click feature in the app.
Boot to your custom recovery. (Will NOT be automatically installed with CF Auto Root. You will have to flash a recovery after rooting)
Flash Superuser.
Reboot. Enjoy goodness.
Click to expand...
Click to collapse
Hey SkipJacks! Thanks for the quick reply. Method 2 seems to be the closest for me but it seems to be a no go with Koush's SuperUser. It looks like it relies on some binaries that never download and it won't use the ones that SuperSU installs. I guess I'm gonna have to use SuperSU for now. Thanks again. I just prefer Koush's to Chains and Chainfires. Everything was working fine on 4.2.2 but from 4.3 on it's only been SuperSU.
I'm beginning to think it's broken as many people are saying the same thing.