Hello together,
I'm using Titanium Backup for years. This week I bought my first Huawei. I unlocked the bootloader, installed TWRP and rooted it.
The Problem now is when I want to restore my apps in titanium backup it keeps stuck at 0%.
I enabled installation of apps from unknown sources.
I googled my problem and some people said "USB Debugging" must be enabled. When I enable it it turns it off automatically when I change to another app.
Can you help me please?
thanks!
Are you using Magisk SU? It doesn't work well with Titanium Backup.
hi,
no I use SuperSU Free v2.82
SuperSU wants to update but I just get an error every time (SuperSU updated unsucessfully)
Avil said:
hi,
no I use SuperSU Free v2.82
SuperSU wants to update but I just get an error every time (SuperSU updated unsucessfully)
Click to expand...
Click to collapse
Your device is not rooted properly. Try to flash supersu again then update its binary library then try titanium backup. Same happened with me that's how I fixed it
Related
need help
i deinstall supersu by mistake..
so i run auto-root again but supersu said su-file is not installed.
What can i do???
Thanks for help!
If you had root and all you did was uninstalled SuperSU, you should just be able to reinstall SuperSU from Google Play Store. You don't lose root by uninstalling the app. You would loose root if you say unrooted through the app w/o backing up your root.
Xdad_0001 said:
If you had root and all you did was uninstalled SuperSU, you should just be able to reinstall SuperSU from Google Play Store. You don't lose root by uninstalling the app. You would loose root if you say unrooted through the app w/o backing up your root.
Click to expand...
Click to collapse
Thanks for answer.
First how can i backup?
And when i uninstall in supersu - how can i get root back?
After about 16 hours supersu work again. I just rebootet 15 times - but everytime supersu said: su-file not installed and now it worked.
I thougt i will hopeless - im just begann to flash...
Hi all,
Just flashing my note 3 to stock rom 4.3 latest update. Then using dr.ketan multitool to root, at this stage all is good. Until I install apps like titanium backup (titanium said no binary found) or triangle away (it says supersu needed, even the phone is rooted and supersu can be updated). Tried to install busybox from apps store but still can't fix the problem. checked with root checker, it says device rooted but no busybox found.
Does anyone know how to fix this issue? Have tried to flash and reflash so many time with different options but still no fix. I just need to get the busybox get recognised so my titanium backup and triangle away can work properly.
I recently got a Galaxy S5 (SM-G900T with LMY47X.G900TUVS1FOJ4).
I grabbed chainfire autoroot and flashed it with the Odin 3.10.6 that came with the CF file. It successfully rooted the phone. I installed Titanium Backup and restored all the stuff I wanted from my old device.
I've been using the device for 1-2 days now and lost root. I opened TB and it says I'm no longer rooted. I confirmed this by downloading a root checker and it also says I'm not rooted.
According to TB, I had BusyBox for root. There was no application icon nor was it in my list of installed applications. When I used chainfire's autoroot on my S4, it installed a super user program that I could open from my app list.
I would really like to continue using Titanium Backup. Does anyone know how I can gain root access again? I already messed it up once by reflashing the autoroot. This caused an infinite bootloop and I eventually got out of it by doing a factory reset. I've returned my S4 to T-Mobile and don't want to soft brick my phone again.
Thanks.
Anyone have any suggestions of how I can reroot my phone?
If you successfully used cf autoroot then that's not the issue.....My money is on a deleted or disabled or un-updated super user app.... this is what will give you (or prevent you from having) root access to your device.
http://i.imgur.com/rVnFwJM.jpg
Using supersu v2.65 works well for me
whynoteel said:
Anyone have any suggestions of how I can reroot my phone?
Click to expand...
Click to collapse
Some days ago I get same problem ( lost root ) because i use supersu v2.67 on cm13 for sg s5 : g900f
therefore, after installed cfroot you can use twrp 3.0.0.0 as custom recovery
Then , Download. & update supersu to v2.65 by using twrp recovery ZIP version
Thanks i'm waiting for a reply
SuperSU updated yesterday like normal, required updating binaries and I used TRWP. I updated the app with my Titanium Backup. Another app updated today but when I tried to back it up Titanium had lost root. Opened SuperSU and got SU Binaries occupied. Later today, I powered up again, SuperSU and Titanium both had new updates. I thought the problem was reported and fixed but it still does the same thing! :crying: Anybody??
EDIT: A known issue, https://forum.xda-developers.com/ap...6-09-01supersu-v2-78-release-t3452703/page165
I had the same problem as well after SuperSU binary update
SuperSU 2.82 no loger have ability to replace Kingoroot and now it says "SU Binaries occupied". Really Chainfire?
SuperSU 2.79 was the best version.
evildog1 said:
I had the same problem as well after SuperSU binary update
SuperSU 2.82 no loger have ability to replace Kingoroot and now it says "SU Binaries occupied". Really Chainfire?
SuperSU 2.79 was the best version.
Click to expand...
Click to collapse
Got this error too after installing 2.82. What I did was to Reinstall ("Cleanup to reinstall from Google Play" option in Settings) and then installed the 2.79 apk I have as backup. Got a prompt that SU binaries needed to be updated and so I did. Update was successful and seemed to do the trick since I'm not receiving the error and still have root.
evildog1 said:
I had the same problem as well after SuperSU binary update
SuperSU 2.82 no loger have ability to replace Kingoroot and now it says "SU Binaries occupied". Really Chainfire?
SuperSU 2.79 was the best version.
Click to expand...
Click to collapse
I am also having the same problem...
Now what to do...?
ashesall said:
Got this error too after installing 2.82. What I did was to Reinstall ("Cleanup to reinstall from Google Play" option in Settings) and then installed the 2.79 apk I have as backup. Got a prompt that SU binaries needed to be updated and so I did. Update was successful and seemed to do the trick since I'm not receiving the error and still have root.
Click to expand...
Click to collapse
I have staright talk stylo 2 lgl82vl 5.1.1 lollipop think thats issue? I cant really find info on my stylo 2 version.. Rooted phone with kingroot 4.6 and reboots itself and losses root within minutes of completing root. Any help for this rookie tech. Guy...thanks
ashesall said:
Got this error too after installing 2.82. What I did was to Reinstall ("Cleanup to reinstall from Google Play" option in Settings) and then installed the 2.79 apk I have as backup. Got a prompt that SU binaries needed to be updated and so I did. Update was successful and seemed to do the trick since I'm not receiving the error and still have root.
Click to expand...
Click to collapse
No... It doesnt work... Failed to update binaries... And asks to update the app...
yashasvi.malik said:
No... It doesnt work... Failed to update binaries... And asks to update the app...
Click to expand...
Click to collapse
The last SuperSU version I had before updating to 2.82 was 2.79. I was lucky I turned off automatic updates because the next SuperSU versions after 2.79 were buggy based on reviews. I updated to 2.82 because I thought bugs were already ironed out. It was a bad decision because I started having "SU Binaries occupied" error popping up. I solved this by reinstalling the 2.79 apk I had as backup.
Maybe you updated from a different SuperSU version that's why it didn't work. Make sure that you reinstalled the SuperSU apk version you were using before you upgraded to 2.82.
I've been reading the reviews and the most common reply by support is to flash the SuperSU binaries that corresponds to version 2.82. You can try that. Visit the XDA thread of SuperSU for the flashable zip.
If all things fail with SuperSU, you can try phh's Superuser as an alternative.
---------- Post added at 05:55 PM ---------- Previous post was at 05:32 PM ----------
JGene1983 said:
I have staright talk stylo 2 lgl82vl 5.1.1 lollipop think thats issue? I cant really find info on my stylo 2 version.. Rooted phone with kingroot 4.6 and reboots itself and losses root within minutes of completing root. Any help for this rookie tech. Guy...thanks
Click to expand...
Click to collapse
Sorry, I'm not an expert with these kinds of things. However, you can try visiting the XDA thread of SuperSU and ask for help there.
And also, I'll stay away from Kingroot if I were you. Search for "Kingroot malware/adware" on XDA for more information.
You can try 'phh's Superuser' as an alternative. You can also ask help there.
Install SuperSU 2.65 and update binary, then reboot, and update from Play Store, then update binary again (using "normal" option).
evildog1 said:
I had the same problem as well after SuperSU binary update
SuperSU 2.82 no loger have ability to replace Kingoroot and now it says "SU Binaries occupied". Really Chainfire?
SuperSU 2.79 was the best version.
Click to expand...
Click to collapse
This works for me:
1° Root using Kingoroot
2° Install Supersu
2° Install link2sd
3° open link2sd and found in the list Supersu, press continuolsy (not simple click) and Click "convert to system app"
4° Remove Kingoroot supersu and Kingoroot
5° Reset device
6° Open Supersu and apply binaires!
lucasgabmoreno said:
This works for me:
1° Root using Kingoroot
2° Install Supersu
2° Install link2sd
3° open link2sd and found in the list Supersu, press continuolsy (not simple click) and Click "convert to system app"
4° Remove Kingoroot supersu and Kingoroot
5° Reset device
6° Open Supersu and apply binaires!
Click to expand...
Click to collapse
this solved for me, thanks a lot!
For me root works, but SuperSU SU Binaries are still "occupied" Device: Huawei y540
for me it helped to:
* install version 2.79
* run it and follow instructions
* update to 2.82
* reboot
* 2.82 works!
delete this please
super su binaries occupied
wptski said:
SuperSU updated yesterday like normal, required updating binaries and I used TRWP. I updated the app with my Titanium Backup. Another app updated today but when I tried to back it up Titanium had lost root. Opened SuperSU and got SU Binaries occupied. Later today, I powered up again, SuperSU and Titanium both had new updates. I thought the problem was reported and fixed but it still does the same thing! :crying: Anybody??
EDIT: A known issue, https://forum.xda-developers.com/ap...6-09-01supersu-v2-78-release-t3452703/page165
Click to expand...
Click to collapse
this worked for me. https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip?retrieve_file=1. I installed the update zip from the sd card
lucasgabmoreno said:
This works for me:
1° Root using Kingoroot
2° Install Supersu
2° Install link2sd
3° open link2sd and found in the list Supersu, press continuolsy (not simple click) and Click "convert to system app"
4° Remove Kingoroot supersu and Kingoroot
5° Reset device
6° Open Supersu and apply binaires!
Click to expand...
Click to collapse
do we need to unroot the device for this first?????
akshayrrrb said:
do we need to unroot the device for this first?????
Click to expand...
Click to collapse
No.
You need to root your mobile first. Kingroot works for me.
I have read many threads and lots of videos and cannot seem to get the Magisk installed.
I have flashed back to stock many times with (N900VVRUEOF1_N900VVZWEOF1_N900VVRUEOF1_HOME.tar.md5) in order to try multiple methods.
Rooted with Arabictoolapp - used rootchecker to verify/application also says true for root
followed: https://forum.xda-developers.com/ve...guide-ob6-of1-root-bootloader-unlock-t3439010
installed SU from playstore to unlock bootloader using the adp method - shows developer mode to verify - using eMMc to verify CID starts with 15
followed: https://forum.xda-developers.com/ve...l/official-note-3-verizon-bootloader-t3359370
installed twrp using official twrp app & also tried ODIN in another trial (picked verizon americas and got twrp-3.2.3-0-hlte.img.tar and twrp-3.2.3-0-hlte.img )
turned phone off and boot into recovery to verify; at this time i created a recovery
using MagiskManager i downloaded the zip (Magisk-v18.1.ip) and flashed using twrp - no errors but when i restart the phone it says Magisk not installed
next attempt was to extract the boot.img from the stock OF1 and then flash the Magisk - no errors but when i restarted the phone it says the same thing - Magisk not installed
another attempt was to patch the boot.img and got a patch_boot.img then using TWRP i flashed the patch_boot.img - restarted and magisk not installed
after further digging, i tried another method which was to unroot using SU, reboot, go into recovery to then install Magisk - magisk not installed
*note each attempt to install Magisk unrooted my phone
*was able to use Magisk-uninstaller-20190204.zip to uninstall Magisk manager from recovery - icon went away
anyways i am completely stuck now. any suggestions or comments on my approach?
jordanfan23 said:
installed SU from playstore to unlock bootloader using the adp method - shows developer mode to verify - using eMMc to verify CID starts with 15
followed:
Click to expand...
Click to collapse
Did you uninstall SU before trying to install magisk. The two together may cause conflict.
cssr said:
Did you uninstall SU before trying to install magisk. The two together may cause conflict.
Click to expand...
Click to collapse
Yes my last attempt i tried.
please help! there has got to be something i am doing wrong or missing. i can flash the uninstall zip and it does uninstall the magisk manager
@cssr any other input or suggestions?
jordanfan23 said:
@cssr any other input or suggestions?
Click to expand...
Click to collapse
Try twrp 2.8.7 hltevzw. You are using the stock ROM which is android 5. Twrp 3.1 and higher is for android 7 and up. I missed that the first time I read your post.
cssr said:
Try twrp 2.8.7 hltevzw. You are using the stock ROM which is android 5. Twrp 3.1 and higher is for android 7 and up. I missed that the first time I read your post.
Click to expand...
Click to collapse
no go =(
@cssr should i try another version of magisk?
jordanfan23 said:
@cssr should i try another version of magisk?
Click to expand...
Click to collapse
Yes. Are you installing Magisk .zip in twrp and installing Magisk Manager APK after normal reboot?
cssr said:
Yes. Are you installing Magisk .zip in twrp and installing Magisk Manager APK after normal reboot?
Click to expand...
Click to collapse
what do you mean after normal reboot? so flash magisk in twrp. reboot. reboot again then install magisk manager? do you know what version of magisk i should run and where i can find the dl link?
What he means is you install the Magisk ZIP via TWRP in Recovery mode, reboot the phone, then you install Magisk Manager via the APK.
Go to magiskmanager dot com website which has the ZIP installer plus the APK for the Manager.
I only just recently tried to tackle this challenge. I also installed 0F1 with Odin, then rooted with Arabic. I was messing with Pokemon go and it wasn't happy I was rooted. I downloaded magisk manager, installed it that way. At reboot, angry message from Verizon that I have custom software and phone won't boot. I assume this is because I didn't install custom recovery.
If you figure a way to get this done, I will be grateful. One thing I don't quite follow. Magisk is a root method...so should we really be rooting the phone prior? Seems redundant and going against the whole point of magisk. Right?
I wanted to play around with spoofing GPS with PGO which requires making a GPS spoofer a system app (need root for that). Is that still possible using magisk?
I'll post any updates I have as well.