I was rooted prior to the OTA. Relocked my phone and did a stock recovery. Acquired the update, now I'm trying to re-root and not having any luck. I've successfully unlocked again, flashed amon ra, and installed su in recovery. However when I check for root access or try and use titanium backup it's unable to acquire root access. I've updated to the newest SU and still no dice. Any ideas as to what I'm missing? Thanks for any input.
zerodarkelement said:
I was rooted prior to the OTA. Relocked my phone and did a stock recovery. Acquired the update, now I'm trying to re-root and not having any luck. I've successfully unlocked again, flashed amon ra, and installed su in recovery. However when I check for root access or try and use titanium backup it's unable to acquire root access. I've updated to the newest SU and still no dice. Any ideas as to what I'm missing? Thanks for any input.
Click to expand...
Click to collapse
The su that Amon Ra installs is outdated and doesn't work. You could do one of two things:
1. Flash a rom(all roms have su) or
2. Go to the superuser website and find the latest binary.
Po1soNNN said:
The su that Amon Ra installs is outdated and doesn't work. You could do one of two things:
1. Flash a rom(all roms have su) or
2. Go to the superuser website and find the latest binary.
Click to expand...
Click to collapse
Thanks very much that did the trick!
i installed the latest ruu 4.0.3 and try to unlock and root the phone.
flashed amon ra 3.15. installed supersu from play store. but couldn't update su binary.
thanks for help.
leotnnz said:
i installed the latest ruu 4.0.3 and try to unlock and root the phone.
flashed amon ra 3.15. installed supersu from play store. but couldn't update su binary.
thanks for help.
Click to expand...
Click to collapse
You have to flash the SuperSU file from recovery to actually be rooted.
http://forum.xda-developers.com/showthread.php?t=1538053
Download the "CWM flashable zip" and flash through Amon-Ra.
Indeed, you need two things for root.
The su binary, which is in one of your system folders.
And an app like SuperSu to manage root access for apps.
] PLEASE HELP!!Su binary not installed and SuperSu cannot install it.
I have Xperia U awhich i had rooted with Root_with_Restore_by_Bin4ry_v18 withouth unlocking the bootloader.
Recently my phone failed to start at the screen got stucked on the Xperia logo so i had to repair the installation by updating the phone with ICS from update service.
After that my phone seems to be half rooted, it installs the root apps like SuperSu , busybox but it has lost the su binary files.
The SuperSu gives the error 'Su binary not installed and SuperSu cannot install it'. I know this is a common problem i searched a lot on it and the best solution i fiund was to flash the SuperSu zip file from Clockwork Mod recovery.
But i dont have CWM as i didnt unlock my bootloader while rooting and i tried to install it but it didnt get installed as there was no su binary.
I cant un-root my phone i cant re-root it. I have tried everything but nothing works.
Is there no way i can have root access again?
you will stuck at the boot image cause u need to unlock boot loader, for the root, you need to aware that the ICS 4.0.1.a.0.283 easier to root but 4.0.1.b.0.112 and above most root software cant do the root, u better install those rom to root, and after you root, just install x-part and u will install the CWM easily through the apps, hope is help for you
timmy5822 said:
you will stuck at the boot image cause u need to unlock boot loader, for the root, you need to aware that the ICS 4.0.1.a.0.283 easier to root but 4.0.1.b.0.112 and above most root software cant do the root, u better install those rom to root, and after you root, just install x-part and u will install the CWM easily through the apps, hope is help for you
Click to expand...
Click to collapse
Sorry i cant understand what you are trying to say. My problem is i am already rooted and i can install SuperSu but it gives error that su binary is not installed. I tried to unroot and re-root from 'Root_with_Restore_by_Bin4ry_v18' but the process gets stuck midway and nothing changes.
The only possible solution i found to install su binary was from CWM but i dont have cwm and there is no way to install cwm without supersu permission.
Is there any other way to install su binary?
Or is there any other way to install cwm without it needing su binary?
tejasn11 said:
Sorry i cant understand what you are trying to say. My problem is i am already rooted and i can install SuperSu but it gives error that su binary is not installed. I tried to unroot and re-root from 'Root_with_Restore_by_Bin4ry_v18' but the process gets stuck midway and nothing changes.
The only possible solution i found to install su binary was from CWM but i dont have cwm and there is no way to install cwm without supersu permission.
Is there any other way to install su binary?
Or is there any other way to install cwm without it needing su binary?
Click to expand...
Click to collapse
Define 'process gets stuck halfway'
Sent from my Xperia P using Tapatalk
AndroidNoob69 said:
Define 'process gets stuck halfway'
Sent from my Xperia P using Tapatalk
Click to expand...
Click to collapse
It gets stuck at the reboot stage. It doesn't reboot the phone when i restore the Root Me file.
When i rebooted it manually after waiting for a long time, it corrupted my phone with icons turning black and phone slowing down. So i had to repair the insatllation again with update service.
If i re-root it with some other method or maybe with 'Bin4ry v31', do you think it will work?
.
Please help! Anyone?
Sorry about the newbie questions but this is my first HTC. In order to flash the Xposed installer does the bootloader need to be unlocked or is rooting the phone enough?
Also, once the phone is rooted can I flash the Xposed installer using the stock recovery or do I need to use a custom recovery? Thanks.
Device needs root and the Xposed can be install from custom recovery or apk installation. Stock recovery can't flash custom rom or basically anything other then stock ota.
jerrycycle said:
Device needs root and the Xposed can be install from custom recovery or apk installation. Stock recovery can't flash custom rom or basically anything other then stock ota.
Click to expand...
Click to collapse
Thanks. So can I root using TowelRoot or one of the other methods without unlocking the bootloader or is unlocking the bootloader necessary before I root?
Depends on hboot version. If you have newer hboot, weaksauce will temp root & firewater will soft. Older version needs romrunner. Guide out there
I got the update for the January Security Update today. I grabbed the .zip's location and the link on Google's servers is:
https://android.googleapis.com/pack...51c56752.signed-angler-MMB29P-from-MMB29M.zip
Hope it helps others!
PSA: this is not flashable over custom ROMs, and cannot be used to install the factory OS from nothing. That's what the factory images are for . This .zip is solely to incrementally update from the December security update to the January one.
Is there an easy way to flash this update.zip without the need of a computer?
tinker_tf said:
Is there an easy way to flash this update.zip without the need of a computer?
Click to expand...
Click to collapse
Unless you have a custom recovery, no. Sorry about that
Updated. Thanks for the link!
I have a rooted, stock ROM and TWRP and with several Xposed Modules, can I flash this?
Also, I don't have the December update, where do I find that?
And lastly, I'm on MDB08L Build, will that work?
For those wanting to use this update and have completely stock system based on MMB29M. Boot into recovery and do an ADB sideload update.zip (rename zip first). Mine updated with no issues.
CipherSec said:
I have a rooted, stock ROM and TWRP and with several Xposed Modules, can I flash this?
Click to expand...
Click to collapse
If you've got all that set up, why not just update using the full factory image (without the wipe)
LeoRex said:
If you've got all that set up, why not just update using the full factory image (without the wipe)
Click to expand...
Click to collapse
I assumed I'll lose all my system modifications (i.e. Xposed Modules and their settings) as well as losing root and TWRP and having to reroot again.
pmedwards25 said:
Unless you have a custom recovery, no. Sorry about that
Click to expand...
Click to collapse
This is exactly the file you need if you don't have custom recovery, don't have root, and have not unlocked bootloader. It is the same file that would eventually come to you OTA. You do however need access to adb and a computer. I don't think this is flashable with a custom recovery.
Thanks..
Thanks for this file bro. dont need to wait.
Alright, feeling like a complete noob, here. I'm on systemless root 2.61 with TWRP. I fastboot flashed the stock boot.img and stock recovery, then tried to sideload the OTA zip. I got a "system contains unexpected contents" error, then installation aborted. Now, with systemless root, I had the understanding that flashing the stock system.img would not be necessary. I was not using systemless root before when I flashed the previous OTA zip. Can anyone spot where I might have gone wrong?
Casyis said:
Alright, feeling like a complete noob, here. I'm on systemless root 2.61 with TWRP. I fastboot flashed the stock boot.img and stock recovery, then tried to sideload the OTA zip. I got a "system contains unexpected contents" error, then installation aborted. Now, with systemless root, I had the understanding that flashing the stock system.img would not be necessary. I was not using systemless root before when I flashed the previous OTA zip. Can anyone spot where I might have gone wrong?
Click to expand...
Click to collapse
Try flash stock system image
Does this update fix the LTE issue?
HRodMusic said:
Does this update fix the LTE issue?
Click to expand...
Click to collapse
No it does not
I got it:
For systemless root, fastboot flash: 1) boot.img; 2) recovery.img; 3) vendor.img; 4) system.img
Boot to recovery and enter sideloade mode. adb sideload [update].zip
Reboot to bootloader. Re-flash TWRP, then in TWRP re-flash kernel (if custom) & superSU.
I used a toolkit to root my 6P. I'm using rooted stock rom. I got an OTA update but it seems I can't update it that way as per all others. So how do I go about installing this on my mobile? Do I need to unroot, flash stock recovery & then flash the new image? Then again I have to root?
fyi: i'm rooted with systemless root and twrp
I tried to take this update per usual as i would if i were unrooted, of course that didn't work totally. i assumed i would just find the update.zip file (i did: /data/data/com.google.android.gms/app.download/update.zip, icywtk) but when i tried to flash that it said the zip was corrupted. i deleted the zip and now it still says my december build is up to date. can't we just flash the update.zip with twrp? i did allow for the system to be modified this time when i booted twrp.
asj0422 said:
fyi: i'm rooted with systemless root and twrp
I tried to take this update per usual as i would if i were unrooted, of course that didn't work totally. i assumed i would just find the update.zip file (i did: /data/data/com.google.android.gms/app.download/update.zip, icywtk) but when i tried to flash that it said the zip was corrupted. i deleted the zip and now it still says my december build is up to date. can't we just flash the update.zip with twrp? i did allow for the system to be modified this time when i booted twrp.
Click to expand...
Click to collapse
I am rooted with twrp. Same deal, twrp reports and error 7 when trying to flash the Jan security update.
kmp14 said:
I am rooted with twrp. Same deal, twrp reports and error 7 when trying to flash the Jan security update.
Click to expand...
Click to collapse
i just tried this again with the same results. it says that the installer is expecting a different build (the one that my settings app shows i'm on) but that i have a build called huawei/mmasomething/ dee_stroyer somethingsomething. (i would post exactly what it says but i've already rebooted into system). I do remember something with "dee_stroyer" when i was rooting but it's not the system...
anyone else have any ideas? i'd like to just update normally and keep my data... and the stock android with root.
EDIT: also, the update won't update my recovery will it? i don't want to have to reflash that. i should be able to update even when i'm away from a computer haha.
Rooted with TWRP. I just tried an ADB sideload and get the same error.