Hi, after i root my Xperia Z1 Compact with the Kernel of the .108 and reinstalling only the Kernel of the .157, when i update the super su app, it shows me this message 'Super su binary needs to be updated', then i choose Normal installation, and always got an error saying me 'Installation Failed! Please Reboot and Try again'
Anybody have the solution to this issue?
Choose the recovery method instead of "normal "
Su needs to be updated
spudata said:
Choose the recovery method instead of "normal "
Click to expand...
Click to collapse
I already try, and the result is the same
Does the phone actually boot into recovery or not?
No, reboot normally, with every option i choose, and always get the same error.
Uninstall then reinstall it.
I had the same problem.
Solution is to flash .108 kernel and than Su binaries will update in 'normal mode'. Last step is to flash .157 kernel again.
I have to do these stepes everytime SU gets an update?
I don't know. It was the first time when I was unable to update Su.
I had the same issue, tried to downgrade back to .108, and although there's no errors during flashing, it stays on .157 - any ideas?
*EDIT* Although I have an update alert for .157 on my phone - it still says .157 in the build number @[email protected]
*EDIT 2* When I connect it to flashtool it says: 'Android version : 4.4.4 / kernel version : 3.4.0-perf-g0109737 / Build number : 14.4.A.0.157' - 'Root Access Allowed'
*EDIT 3* Just check persevering and reboot and it eventually just worked...
I tried to do 'full unroot' in supersu and that's impossible with..157 kernel. So I think that we will have problems with updating binaries everytime.
Related
Hey guys I can't get into the recovery mode, and I really don't know why
what I've done:
rooted my phone with: http://forum.xda-developers.com/showthread.php?t=1886460
unlocked bootloader with: http://forum.xda-developers.com/showthread.php?t=1886460
installed busybox installer with the apk on google play
and installed cwm with: http://forum.xda-developers.com/showthread.php?t=1773227
followed this tut: http://forum.xda-developers.com/showthread.php?t=1756346
the things I've tried to get into the recovery:
Hold down Power and Volume+ till the blue light flashed up for a second > failed
Tapped the screen while the Sony Loadin Screen > failed
in Busybox installer went to scripts and clicked on reboot into recovery > failed
with notification toggle: clicked on reboot into recovery > failed
Android Terminal Emulator: su reboot recovery > failed
Using
- LT26i (Xperia S)
- Android 4.0.4
- Stock ROM 6.1.A.2.45
edit: tried this tut: http://forum.xda-developers.com/showthread.php?t=1756346
didn't work somehow tried it another 3 times and then tapped the sony logo now it worked
edit2: after getting cwm to work and installing a new rom it simply crashes after the booanimation and I get this in CWM:
E: can't mount /cache/recovery/command
E: can't mount /cache/recovery/log/
etc etc
I am also unable to open ums lunfile (no such file or director)E: unable to open
(so I also can't mount the usb storage)
any idea how to save my phone?
ToraDora said:
Hey guys I can't get into the recovery mode, and I really don't know why
what I've done:
rooted my phone with: http://forum.xda-developers.com/showthread.php?t=1886460
unlocked bootloader with: http://forum.xda-developers.com/showthread.php?t=1886460
installed busybox installer with the apk on google play
and installed cwm with: http://forum.xda-developers.com/showthread.php?t=1773227
followed this tut: http://forum.xda-developers.com/showthread.php?t=1756346
the things I've tried to get into the recovery:
Hold down Power and Volume+ till the blue light flashed up for a second > failed
Tapped the screen while the Sony Loadin Screen > failed
in Busybox installer went to scripts and clicked on reboot into recovery > failed
with notification toggle: clicked on reboot into recovery > failed
Android Terminal Emulator: su reboot recovery > failed
Using
- LT26i (Xperia S)
- Android 4.0.4
- Stock ROM 6.1.A.2.45
edit: tried this tut: http://forum.xda-developers.com/showthread.php?t=1756346
didn't work somehow tried it another 3 times and then tapped the sony logo now it worked
edit2: after getting cwm to work and installing a new rom it simply crashes after the booanimation and I get this in CWM:
E: can't mount /cache/recovery/command
E: can't mount /cache/recovery/log/
etc etc
I am also unable to open ums lunfile (no such file or director)E: unable to open
(so I also can't mount the usb storage)
any idea how to save my phone?
Click to expand...
Click to collapse
download flashtool, flash with.50, root with flashtool, install cwn again, you should be good to go.
http://www.xdafileserver.nl/index.php?dir=Sony+(Ericsson)/SE+Xperia+S+(LT26i)/
corum3 said:
download flashtool, flash with.50, root with flashtool, install cwn again, you should be good to go.
Click to expand...
Click to collapse
by .50 you mean stock rom 6.1.a.50?
edit: thank you it's working again :3
ToraDora said:
by .50 you mean stock rom 6.1.a.50?
edit: thank you it's working again :3
Click to expand...
Click to collapse
happy to help, but the real helpers are the guys who create flashtool
Hi folks,
I've follow ParotZ's Recovery Installer process to root and am having SuperSu issues.
I install recovery (option 5), then reboot to recovery (option 0), system > reboot > swipe to install > and then once it loads I'm greeted with
"no su binary installed and supersu cannot install it"
I've put UPDATE-SuperSU-v2.16 on internal storage and tried earlier versions and flashed, with the same result.
The SuperSu app is installed. I attempted a manual update on the Play store, but the 'no su binary' message is still there.
I can't uninstall supersu, either with an uninstaller app or through Play (it does not show 'uninstall', just shows 'open')
It persisted after I factory reset and wiped (not through recovery).
Any help? Keen to get on Cyanogen.
My phone specs.
Model
Oppo x9076
ColorOS
v2.0.0i
Android version
4.4.2
Build number
FIND7WX_12_141017
Kernel
3.4.0-S3753
Baseband
Q_V1_P14
I've seen others with the question, but none with answers for the Find 7 :/
Cheers!!
solved
Hi folks,
I've solved the issue. I could not root using that method because I had updated the OS and there was some form of conflict that stuffed the SuperSu binary.
So I downgraded back to stock (the earlier ColorOS) and reapplied the root process.
For those with the same issue follow these steps http://theunlockr.com/2014/08/22/how-to-unroot-the-oppo-find-7-video/
Then reattempt the root.
Note that step 6. "Using the volume buttons to navigate and the power button to select the option you want, select Wipe Data and Cache." will erase the OS you just copied over, so do this prior to copying the OS or you'll just need to do it again.
When the OS loads and you come to the update SuperSu step, my Play store wouldn't load due to I think a delay in the accept terms of use popup. So I used the TWRP method and it worked fine.
Good luck.
Darren.
Hi all, I have a rooted fire tv with cwm recovery and rbox boot menu, with software ver 51.1.5.3 on it. I have decided I would like to revert the box back to stock. I'm trying to downgrade the box to ver 51.1.4.0 and then follow this guide to unroot. http://www.aftvnews.com/how-to-unroot-a-fire-tv-and-switch-back-to-stock-updates-from-amazon/ , however when I reboot into recovery and attempt to install the zip file, I get an error, unable to open file, I have downloaded software from atvnews and one other site, both give same error. I also tried to use one of the downgrade script tools, however it failed also. Any ideas why I can't get a successful downgrade? thanks.
Update: I'm not sure what went wrong, but now when I try to reboot into recovery via adb reboot , or via selecting launch recovery from the rbox boot menu, it just goes to a screen that says "The system update was unsucessful, your device will reboot in few minutes and should resume normal operation"
Nevermind, solved.
Hello Guys!
I was kinda hyped when I saw on Dec 31st that there's a new Softwareupdate available. Although I have a rooted device with a custom recovery (latest TWRP), previous OTAs always worked well. So I downloaded the OTA, and tapped "install" when it was finished. But this time it rebooted into recovery mode, and TWRP just did nothing. So, assuming it was because of the rooted device, I completely unrooted it and flashed the stock recovery and tried it again. This time there was actually smth. but an error saying "Update failed" appeared. Kinda pissed I downloaded the OTA update to my PC and tried to do it via adb sideload, same error "Installation failed" on the phone and cmd said
Code:
error: protocol fault (no status)
.
After that I copied the .zip to my phone, flashed TWRP again made a nandroid backup, wiped dalvik, chache & CO (no factory reset) and installed the zip. Again: Error. I don't remember the exact code, but it was smth. with "error reading zip" or so, but the file isn't damaged.
So I have the question: What am I doing wrong? Do I have to lock OEM again?
I am looking forward to your answers.
Sincerely, Firnien
PS: I updated adb to the latest version as well and tried, still not working
You should try this : https://forum.xda-developers.com/oneplus-3/how-to/fix-device-mapper-verity-simple-trick-t3530685
Start with flashin twrp -28 then follow step by step.
Nobody07 said:
You should try this : https://forum.xda-developers.com/oneplus-3/how-to/fix-device-mapper-verity-simple-trick-t3530685
Start with flashin twrp -28 then follow step by step.
Click to expand...
Click to collapse
Thanks, I'll try it
tried to replace SuperSU with Magisk via TWRP.
Magisk won't take by itself.
Removed SuperSU. Tried again. Still NG.
"adb reboot recovery" back to TWRP and flashed SuperSU. I have root back, though I don't see SuperSU in the app drawer.
The info to install Magisk leave a bit to be desired.
"install manually" what does that mean?
Remove root (SuperSU) seems to prevent one from installing Magisk, though I did "adb reboot recovery" to get the re-install of SuperSU done.
In the long run, I want to update our other H811 to 20x from 20q. Thats' what started me down this track.
Any input?
Did Magusk Zip Got Trough without any issues in TWRP?
Did you have the magisk App in drawer after flashing Magisk?
Magisk manager is sometimes an older version, so you have to go to magisk manager (app) open ist and click on upgrade or install upgrade.
sometimes my device needed 2installations. one in twrp an another in MAgisk app. but both were v16.0 zip.
no & no. "updater process ended with ERROR: 1
Error installing zip file '/external_sd/Magisk-v16.0.zip'
Tried installing Magisk Manager, which went ok. And then Magisk from that. Error.
"Boot image patched by other programs (SuperSU, perhaps?)
Please restore stock boot image."
So I ran the script that removes SuperSU.
Tried install again from MM.
"Select stock boot image dump in .img or .img.tar format."
No idea where to find that.
Tried this method.
NG. SuperSU doesn't show in app drawer, though it appears to be working as I can reboot recovery from the phone without going into Terminal and adb.
metropical said:
no & no. "updater process ended with ERROR: 1
Error installing zip file '/external_sd/Magisk-v16.0.zip'
Tried installing Magisk Manager, which went ok. And then Magisk from that. Error.
"Boot image patched by other programs (SuperSU, perhaps?)
Please restore stock boot image."
So I ran the script that removes SuperSU.
Tried install again from MM.
"Select stock boot image dump in .img or .img.tar format."
No idea where to find that.
Tried this method.
NG. SuperSU doesn't show in app drawer, though it appears to be working as I can reboot recovery from the phone without going into Terminal and adb.
Click to expand...
Click to collapse
You should Always search the TWRP errors you have, that gives you more info.
Error 1 means on your system partition is not enough space anymore, so delete or Freeze some bloatware/apps and it should go trough.
boot.IMG files are containt in KDZ (firmware files).
Maybe you should visit https://******************/
and read trouh installation (with pictures) for better understanding.
uweork said:
Maybe you should visit https://******************/
and read trouh installation (with pictures) for better understanding.
Click to expand...
Click to collapse
went and posted in digeridoohan original thread.
https://forum.xda-developers.com/showpost.php?p=76980632&postcount=25580
all is well.. thanks very for the help. and I installed the Xposed module that works with TextAid and MM.
also your link won't doesn't seem to work. I've found that a I've had to use shortened links of late or they don't fire on XDA.
Guys I can't run Magisk on my LG G4 H815 with Nougat v29a. After removing Supersu and flashing magisk 17.1 with twrp, the phone doesn't boot normally. It reboots recovery when I click reboot system. It always reboot recovery. I don't know why.
Do you have any Idea?