I've updated with the OTA from H14 to H15. I restored the stock recovery beforehand and the update went without Problems.
Before starting the update I tried to "unroot" which also was stated neccessary by SuperSU in two dialogs. But this failed and might be the origin of the problem.
Afterwards SuperSU could not find the su binary so I tried to flash it via TWRP 3.0.2.0 which failed after the line "creating ramdisk backup".
Next I tried to dirty flash the H15 Rom, which also went without problems, but the SuperSU install failed at the same point.
I've attached the logfile of the aroma installer, containing the superSU logfile.
The phone works for the moment, without root / superSU but I would like to have it back
Does anyone have an idea / need more informations / can otherwise help ?
Henry
Related
I'm at a loss as to what is wrong. I flashed a prerooted stock version of KitKat and I think root was working. But now for some reason it doesn't work. I flashed the supersu zip (v1.80) via TWRP recovery but after rebooting, the SuperSU app doesn't even show up on my device. When I install manually from thr Play Store it's as if I'm not rooted. I've flashed the zip multiple times and I do not want to factory reset and delete all my data (especially since I really can't backup without root atm). Any ideas?
Edit: sorry about the post title typo. *flashing
My 4.4.3 OTA installed just fine this afternoon and I immediately grabbed the latest SuperSU .zip and installed it with TWRP to get re-rooted, but after I told SuperSU to get itself re-installed from Google Play, it wanted to update the binary, and the "normal" method wouldn't work, even after a couple of reboots and retrys.
I don't have TWRP installed on my Nexus 7, instead just using fastboot to boot it when I need it for something, so the technique that finally got the binary updated was to tell SuperSU to use the TWRP update mode, then when it I got the popup saying it was about to reboot to recovery, I plugged in the USB cable and ran:
adb reboot bootloader
fastboot boot openrecovery-twrp-2.7.1.0-flo.img
That worked. As soon as TWRP booted, it installed the script SuperSU had prepared for it, and the binary was indeed updated.
I never had a problem with the "normal" binary update method before. Something new and "helpful" in 4.4.3 I guess.
You can share the script SuperSU?
RazrBR said:
You can share the script SuperSU?
Click to expand...
Click to collapse
If still having issues, try the 1.99r4 from the link in my signature.
[FIXED] Unable to replace Kinguser with SuperSU, updating binaries & keeping Root
I'm on KitKat 4.4.2 B510 firmware. After days of struggling to replace Kinguser with SuperSU, updating of binaries failed & keeping Root, I finally solved the issue. Now SuperSU is working perfectly. I tried everything possible, thinking there was an issue with my configuration or compatibility conflicts between SuperSU, Kinguser & Huawei P6 firmware. The problem was with SuperSU. There is an incompatibilty issue with SuperSU 2.46 & earlier versions updating binaries on some P6 phones running KitKat & having rooted their phones with Chinese rooting tools which were installing Kinguser instead of SuperUser as the app of choice. If you wanted to replace the app with SuperSU/SuperUser, you would've encountered many issues. Like
updating binaries, root permissions not given to SuperSU & incorrect root setup.
The SOLUTION is simple.
I found the latest version of SuperSU[2.48] in the test section of the SuperSU thread. SuperSU 2.46 is the latest stable official release & therefore found on Google Play, but since 2.48 is still in beta & being tested, it isnt available on Play or as an apk. You can get SuperSU 2.48 beta here:
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
It is a zip file & should be installed via a recovery. It is not available as an apk as it is still in testing & still an unofficial release.
I used TWRP to install it.
Boot into recovery, select install or update, find the file you just downloaded from the link & install the zip. Reboot. When your phone is finished booting up, automatically, Kinguser will be replaced with SuperSU 2.48 beta & the binaries will automatically be updated. Kinguser will be deleted, full root permissions will be restored to SuperSU, & no more issues with updating binaries. Solved.
Here is the link for SuperSU 2.48 beta again:
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Kingo User was driving me nuts!
adnaanhitman said:
I'm on KitKat 4.4.2 B510 firmware. After days of struggling to replace Kinguser with SuperSU, updating of binaries failed & keeping Root, I finally solved the issue. Now SuperSU is working perfectly. I tried everything possible, thinking there was an issue with my configuration or compatibility conflicts between SuperSU, Kinguser & Huawei P6 firmware. The problem was with SuperSU. There is an incompatibilty issue with SuperSU 2.46 & earlier versions updating binaries on some P6 phones running KitKat & having rooted their phones with Chinese rooting tools which were installing Kinguser instead of SuperUser as the app of choice. If you wanted to replace the app with SuperSU/SuperUser, you would've encountered many issues. Like
updating binaries, root permissions not given to SuperSU & incorrect root setup.
The SOLUTION is simple.
I found the latest version of SuperSU[2.48] in the test section of the SuperSU thread. SuperSU 2.46 is the latest stable official release & therefore found on Google Play, but since 2.48 is still in beta & being tested, it isnt available on Play or as an apk. You can get SuperSU 2.48 beta here:
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
It is a zip file & should be installed via a recovery. It is not available as an apk as it is still in testing & still an unofficial release.
I used TWRP to install it.
Boot into recovery, select install or update, find the file you just downloaded from the link & install the zip. Reboot. When your phone is finished booting up, automatically, Kinguser will be replaced with SuperSU 2.48 beta & the binaries will automatically be updated. Kinguser will be deleted, full root permissions will be restored to SuperSU, & no more issues with updating binaries. Solved.
Here is the link for SuperSU 2.48 beta again:
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Click to expand...
Click to collapse
Thanks bro. This Kingo User crap was driving me nuts. I just don't trust the Chinese programmers. Kingo seems to have installed a lot more than su binaries. It was constantly going to the internet and uploading/downloading God alone knows what kind of stuff!
KingUser irritated me for a long long time & I struggled to find a solution. The biggest issue was tht my start ups wouldn't stick after restarting my phone. It definitely installed more than just the appropriate binaries. It made it almost impossible to install any other SuperUser app therefore eliminating the competition. Avast also kept reporting it as a threat. Now tht SuperSU is back on my phone, I've had no problems. My smartphone is running smoother & better than ever.
Glad I could be of help bro.
Any solution to devices without recovery? I own a Xperia C3 and there isn´t a recovery for my phone and I wanna try this method
I think all devices have recoveries. They are used by the phone manufacturer or repair service ppl to service & repair our phones. I take it u mean u don't have a custom recovery, but a stock recovery. I haven't tried installing the file via stock recovery as I have TWRP(custom) installed. Last time I checked, it was possible to install or flash zip files via stock recovery. You may have to rename the file to update. zip, then use the install update option to install your zip file. Also Google what button- combination u have to use in order to enter the stock recovery for ur type of phone.
hi,
i just installed the last beta version of OOS (beta 14) and my phone was previously rooted.
when i instaled the update, i reflashed super SU and when the phone booted up i had TWRP and SuperSU flashed but all my apps said the phone wasn't rooted (superSU showed me the message about SU binary not being installed or whatever).
i then uninstalled SuperSU and rechecked and all my apps said my phone was rooted. what did i do wrong? i am thinking that this is a temporary root without SuperSU so i would love it if someone had a solution and coul help me
Try to flash the superSU.zip once again without clearing cache .....it would work
i tried with and without clearing cache, nothing works. i also tried 4 different supersu zip files.
i even reflashed OOS and tried again (don't know if that does anything)
I was following the guide at:
https://forum.xda-developers.com/pixel-xl/how-to/guide-pixel-xl-android-8-1oreo-unlock-t3715279
I started with a Pixel XL 7.2, unlocked, magisk, etc. I uninstalled magisk, updated all OTA updates, and then began the thread above.
I followed 6 - Extract boot.img from Fcatory Image and fastboot boot.img
The continued with 7 - Root with Magisk
booted to twrp, flashed twrp, no issues.
Rebooted to recovery, flashed elementalX kernel 3.04, and added magisk v16.3
No errors
Rebooted phone, and upon boot, got a message:
"there's an internal problem with your device"
From what I've read, that is not really an issue and has something to do with some things not matching, so, an update to magisk in the future will resolve it. So no big deal.
However, I don't see magisk manager, and have no root.
I reboot back to recovery, uninstall magisk manager, and reboot phone.
Still get the internal problem message, but no big deal.
I reboot back to recovery, and try flashing magisk again.
Still no manager, still no root (from root checker).
I try installing the magisk manager app directly, but, the APK cannot install, and just gives a generic error message of "app not installed".
Reboot to recovery, uninstall magisk again, wipe cache. Reboot, still same internal problem message.
Try to flash magisk 16.0 instead, repeat the above, and still no root, and can't install APK.
So, just kind of stuck at this point. Phone tells me that elementalx installed without an issue though, so, just seems like magisk is the last step. Any help is greatly appreciated. Thank you.
The message you get upon boot is from the kernel, nothing to do with magisk. not that it matters, it doesnt affect anything.
According to EX thread and EX's official websites "How to install" guide, you are supposed to install magisk first. Thats how i do it.
what you need to do is......
Reflash the stock factory boot img and let it boot.
Reboot to bootloader flash or boot twrp, and install magisk.
Reboot let it boot all the way.
Then reboot to bootloader flash/boot twrp and install EX.
Reboot.
---------- Post added at 07:14 PM ---------- Previous post was at 07:12 PM ----------
Double post, sorry, butt.......
https://elementalx.org/how-to-install/
Read part one step three.
"3. Root your device (optional)
If you would like root access to your device, install SuperSU or Magisk. This should be done before installing ElementalX. Other root methods are NOT recommended. Root access will give you full control over your device and allow you to change kernel settings and tweak your device. To install SuperSU or Magisk, download to your device, reboot to recovery and install the zip you downloaded. Make sure you reboot into your system after the installation process completes. Ensure that root is correctly installed and working.
At this step, I usually make a backup of the stock rooted kernel. Now that you are rooted, you can do this very easily in EX Kernel Manager by selecting Tools->Kernel backup. This will save the boot.img."
Thank you for the help, will try it when I get a chance. The guide that I was following said for elementalx, flash kernel first. For exnoshadez, to do magisk first, for other kernels, do kernel first. I had read that some kernels need to go first, while others magisk needed to go first, and since that guide was specifically oreo, I thought kernel was first. But, thanks! Will try going back to factory boot image and progressing through.
So, I flashed back to stock boot.img, booted twrp, flashed twrp, and flashed magisk. But, Magisk still did not show up. I tried installing the magisk manager apk, but still get "App not installed" when trying that. At least the "there's an internal problem with your device" message went away.
Any other ideas on what to check when flashing, or why it's not "taking"?
Thanks again for the help.
Found out the problem:
Had to do:
adb uninstall com.topjohnwu.magisk
The key here was that I was upgrading from 7.2 to 8.1, and in the uninstall of magisk, I guess it left some remnant behind which prevented it from installing the new version.
The way I discovered this was trying to use adb to install the magisk manager apk, and that gave me the error:
adb: failed to install MagiskManager-v5.7.0.apk: Failure [INSTALL_FAILED_UPDATE_INCOMPATIBLE: Package com.topjohnwu.magisk signatures do not match the previously installed version; ignoring!]
Then, I simply uninstalled it, then flashed using twrp again, and it worked fine.