I was playing with my TF101 earlier today and went to check Titanium Backup when I was given a surprise, I can't use it anymore. My tablet had been rooted since the day I got it nearly a year ago but somehow my busybox got uninstalled. I have not done anything that would cause it to be uninstalled, and when I try to install it again no program is able to. When trying to update the Su binary Superuser fails to gain root access as well, so something weird happened in the past few days (looking at my most recent Titanium Backups manually it seems it happened after 6/3, but I don't know why).
My first attempt to fix was re-flash the most recent Honeycomb-based Revolver update (3.11.1) and run "Fix Permissions" but that didn't help. I'm thinking the only way to be able to fix this is to do a wipe and re-install of everything, or even a new nvflash, but my most recent backup is months old (I'd been travelling and not messing with ROMs so I didn't have a need for a backup).
Does anyone have suggestions as to what else I can do before I try and do a wipe/install?
Thanks
In terminal, does "which su" and "which busybox" return anything?
How about "ls -l /system/*/su" and "ls -l /system/*/busybox"
You probably have 2 versions and one is not does not have the su id set.
sent while running with scissors
gee one said:
In terminal, does "which su" and "which busybox" return anything?
Click to expand...
Click to collapse
I tried running it in "Android Terminal Emulator" but for some reason it doesn't work anymore, it loads and then auto closes... so I did it in "System Tuner"s terminal emulator.
I ran both and got "Failed to run: Error running exec(). Command: [which, su] Working Dierctory:null Environment: null"
How about "ls -l /system/*/su" and "ls -l /system/*/busybox"
Click to expand...
Click to collapse
for both of these i get "No such file or directory"
I honestly have no idea what is going on because this last week I used it as a netbook while travelling Korea and for the 4 months prior I haven't been able to access the internet regularly so I haven't been playing around with CWM, flashing new roms, etc. I think the newest apps I've installed were mixi (like Facebook, but Japanese), Skype, and Temple Run, none of which require root access.
shadowmonk36 said:
I was playing with my TF101 earlier today and went to check Titanium Backup when I was given a surprise, I can't use it anymore. My tablet had been rooted since the day I got it nearly a year ago but somehow my busybox got uninstalled. I have not done anything that would cause it to be uninstalled, and when I try to install it again no program is able to. When trying to update the Su binary Superuser fails to gain root access as well, so something weird happened in the past few days (looking at my most recent Titanium Backups manually it seems it happened after 6/3, but I don't know why).
My first attempt to fix was re-flash the most recent Honeycomb-based Revolver update (3.11.1) and run "Fix Permissions" but that didn't help. I'm thinking the only way to be able to fix this is to do a wipe and re-install of everything, or even a new nvflash, but my most recent backup is months old (I'd been travelling and not messing with ROMs so I didn't have a need for a backup).
Does anyone have suggestions as to what else I can do before I try and do a wipe/install?
Thanks
Click to expand...
Click to collapse
Don't do the wipe yet, just use Recovery to reinstall the same ROM and it may help. It maybe related to kernel or /system/bin or /system/xbin (or even etc).
I tried reflashing the most recent Revolver Honeycomb update (3. 11.1) but it didn't help, still have the problem.
Re-manually install busybox and SU using the superuser.zip that's flashable in cwm, then Install SuperSU and update binary with that. Should fix all issues, I prefer SuperSU to superuser since it doesn't glitch as much. xD
Thing O Doom said:
Re-manually install busybox and SU using the superuser.zip that's flashable in cwm, then Install SuperSU and update binary with that. Should fix all issues, I prefer SuperSU to superuser since it doesn't glitch as much. xD
Click to expand...
Click to collapse
I will give that a try, as soon as I can find the superuser.zip file in question. I googled for it, and looked on XDA but I can't seem to locate it. Could you help point me in the right direction?
I re-thought about what tingtan said and I realized that just an update wouldn't necessarily have everything needed so I found the most recent full ROM and flashed it followed by the update and it looks like things are fixed.
I'd still like a link to that superuser.zip file for the future, but now I can backup and I might try playing with ICS now.
Superuser.zip link: http://androidsu.com/superuser/
I prefer SuperSU though, all preference.
Thing O Doom said:
Superuser.zip link: http://androidsu.com/superuser/
I prefer SuperSU though, all preference.
Click to expand...
Click to collapse
Thanks, that is the one I found but since you were talking about SuperSU I wasn't sure if it was correct. I will also give SuperSU a try, but after I reflash everything (it broke again shortly after I got my titanium backup done).
Related
i am still alittle confused of what i found on the internet and maybe someone can help me understand it. titanium backup backsup apps and data but it only runs when rooted. If i root my phone all the apps get deleted. How am i supose to back it up if all my apps are gone??
You do it after you have all your apps redownloaded. MyBackUp pro could of backed up your apps before you rooted the device.
But the only way you can get them back is to nano back to your original, then you titanium backup and then flash the new rom.
Rooting your phone won't delete anything. Just don't flash another rom untill you install Titanium and backup all your apps.
funcrusher said:
Rooting your phone won't delete anything. Just don't flash another rom untill you install Titanium and backup all your apps.
Click to expand...
Click to collapse
+1
will someone whip this kid up a list of links guiding him through the rooting and flashing process? no flames, but seriously man.
o ok well i rooted my phone and it saysit wont work "please verify that your rom is rooted and includes BusyBox, and try again" What does that mean?? and how do i get busy box??
xxxk15 said:
o ok well i rooted my phone and it saysit wont work "please verify that your rom is rooted and includes BusyBox, and try again" What does that mean?? and how do i get busy box??
Click to expand...
Click to collapse
Use MybackUp free.. It will take a little bit of time restoring your apps, but it will work.
Once you have a custom rom on your phone. Prefer 2.0d or dc 2.07.2, both close to a normal full rom. Then you can use titanium backup
xxxk15 said:
o ok well i rooted my phone and it saysit wont work "please verify that your rom is rooted and includes BusyBox, and try again" What does that mean?? and how do i get busy box??
Click to expand...
Click to collapse
I think you need to click "problems" in the titanium backup app and it will download the latest busy box.
i am sorry if i am asking to many questions this will probley be my last. in titanium backup i went into backup/restore and none of my apps are on there??
You need superuser.apk and busybox. Titanium will get busybox for you if you press problems.
Search "mercado79 superuser"
xxxk15 said:
i am sorry if i am asking to many questions this will probley be my last. in titanium backup i went into backup/restore and none of my apps are on there??
Click to expand...
Click to collapse
You have to have busybox on your phone. Do what i said and us mybackup the free one. Same thing but doesnt require root. Once you get a custom rom, then you can use titanium backup to back your stuff up. The roms will have all the needed apps to run titanium
and how would i get super.apk and would i just put it into the root of my sd card??
xxxk15 said:
o ok well i rooted my phone and it saysit wont work "please verify that your rom is rooted and includes BusyBox, and try again" What does that mean?? and how do i get busy box??
Click to expand...
Click to collapse
http://www.mediafire.com/?wcknmnhtin0
That is busybox 1.15.3
copy it onto your SDcard
get into your cmd prompt and ADB shell
copy/paste or type the following
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
su
mkdir /system/xbin
cd /sdcard
mv busybox /system/xbin/busybox
cd /system/xbin/
./busybox --install -s /system/xbin
I'm sure if you keep running into problems we'll all continue to spoon feed you answers, but please at least make an attempt to search the forums and google beforehand. Most of this stuff has been covered ad nauseum . When you are in the CDMA hero forum index, in the upper right hand portion of the forum you will see a button that says "search this forum"
xxxk15 said:
and how would i get super.apk and would i just put it into the root of my sd card??
Click to expand...
Click to collapse
search for "mercado79 superuser"
http://www.mediafire.com/file/3mddanwztzd/superuser.zip
flash that through the recovery console. please search for information on how to flash update files through recovery before asking us here.
yeah i downloaded mybackup and once i backup everything i just flash the rom and the app will be on my new rom?? is that how that works??
Honestly, you anger me. Seriously. I don't know what PSP hacking forum you came from, but if you acted like this on the one I came from, they would have b& you after ridiculing your inability to take the time to search.
Ok, so this would be my chain of thought.
1. Find out about titanium backup, try it out.
2. Fails because Busybox isn't installed
3. Search the CDMA Hero section for Busybox
4. Find this
5. ???????
6. PROFIT!!!1!1!!ELEVEN!!!
xxxk15 said:
yeah i downloaded mybackup and once i backup everything i just flash the rom and the app will be on my new rom?? is that how that works??
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=593952
i am sorry i anger you i wills end you a picture of my psp if you want but i am sorry if i anger why do you keep coming into and posting
xxxk15 said:
i am sorry i anger you i wills end you a picture of my psp if you want but i am sorry if i anger why do you keep coming into and posting
Click to expand...
Click to collapse
Because I'm the guy that busts your balls constantly, and then shows you what you're doing wrong and how to fix it. That's how I've been trained in every job I've held, and if need be that's how I'll train you.
abcdfv said:
Honestly, you anger me. Seriously. I don't know what PSP hacking forum you came from, but if you acted like this on the one I came from, they would have b& you after ridiculing your inability to take the time to search.
Ok, so this would be my chain of thought.
1. Find out about titanium backup, try it out.
2. Fails because Busybox isn't installed
3. Search the CDMA Hero section for Busybox
4. Find this
5. ???????
6. PROFIT!!!1!1!!ELEVEN!!!
Click to expand...
Click to collapse
I had problems with that flashable zip. SU was not working and busybox was not recognized by TB. anyways he has specific instructions for installing busybox and SU from this thread...I've seen this guy around on androidforums.com too. every freaking post is just another question. Seems like he doesn't even attempt to search.
Okay, first off, I have searched. For the last 3 hours I have searched!!
I foolishly used Razorclaws one-button root method and it worked, However everything after that point has been an utter failure. I tried to flash recovery, and nothing. I tried using CWM, and nothing. I open Super User and it just closes. I don't know what else to do. Yes, I saw post 275 in the razorclaw thread, but when I put in the command list, it tells me it doesn't recognize the command. I previously had a Nook Color and had the easy adb installed. I don't know if this is my problem. I have a B70 transformer, I just want to unroot. I tried the Super User update fixer, nothing. The Transformer is running fine, I get force closes on some apps. I just want to return to stock. Any help will be greatly appreciated.
I unrooted it. But the superuser apk remains in the app drawer. Is there any harm that can be done by having it? I would like to 'successfully' root and flash a rom, but judging from my inability to flash recovery using the one-button method I will wait. I would love to overclock this beast!
You can delete this thread, I apologize for wasting time and resources!
have you tried rebooting and then re-rooting?
how did you unroot ?
Sent from my tf101 using xda premium 1.54Ghz
To get rid of Super user app and binary
http://forum.xda-developers.com/showpost.php?p=19505946&postcount=221
Also if you want to try again and get SU working you can try this
http://forum.xda-developers.com/showthread.php?p=19555429
Thanks for the replies
I did not reboot and reroot, I did have to download the SDK in order to use the adb functions. I used the info provided by doaist to remove su permissions, I suppose. When I checked through the razorclaw app, and terminal. I was not given su access. So, I assumed I didn't have su permission.
And as soon as I try to get into the adb shell and type 'su' it says 'permission denied' , I don't know what else to do to remove it.
Thanks for your input guys, it means a lot.
Okay, so I redownloaded said apps, and I am now performing a backup. Which rom should I use? Which rom will allow me to retain stock functionality , and which OC kernal should I use. Is there a rom that has both?
When flashing recovery, does it go to the emmc or the extrernal sd???
woundedworld said:
When flashing recovery, does it go to the emmc or the extrernal sd???
Click to expand...
Click to collapse
External micro sd card
Hi,
I rotted my phone on 2.3.5 and followed manual upgrade process to get 2.3.6 and indeed it worked fine with keeping root.
Of late, when ever I run TitaniumBackup it give me warning as
"Your ROM is rooted but SU binary has non-optimal access rights, which may cause problems
Titanium Backup Pro can fix this problem automatically in many cases. Do you want to proceed? "
When I say "Yes. do it", it gives me message as
"Access rights on "SU" binary was succesfully corrected from "0:0:[4755]" to "0:0:6755" " and asks to restart for apply changes.
Once it restarted it didn't seems to apply changes and asks me same question when I re-open TB.
I understand it has something with access rights files but not sure how to fix this. [we moved SU to diff path to keep root, is that causing issues?] Can someone help me.
Thank you.
Did you upgrade to root using adding 'chmod 4755' to mount_ext3.sh ?
Shaliuno said:
Did you upgrade to root using adding 'chmod 4755' to mount_ext3.sh ?
Click to expand...
Click to collapse
I think so, used below method.
go to /system/bin/
open in text editor – mount_ext3.sh
add the 3 following lines to the very bottom
chmod 4755 /system/bin/su
chmod 4755 /system/xbin/su
chmod 4755 /system/app/Superuser.apk
I did used ES File explorer to perform this. I also read posts mentioning the problem because of ES, how ever I performed this earlier even before complaints and never had problem as it stayed Rooted, so left as it is.
I also installed SU updated from market as I had problems with updating SU binaries.
Not sure but that is the problem I guess.
On every start this script is executed and besides its normal function, it also changes permissions to maintain root. Titanium changes these permissions but upon restarting all reverts back.
Strange thing is I also got Titanium and it doesn't say anything.
Or maybe ES Explorer really messed something up, so the root stays but something ese like Titanium doesnt like it
Shaliuno said:
Not sure but that is the problem I guess.
On every start this script is executed and besides its normal function, it also changes permissions to maintain root. Titanium changes these permissions but upon restarting all reverts back.
Strange thing is I also got Titanium and it doesn't say anything.
Or maybe ES Explorer really messed something up, so the root stays but something ese like Titanium doesnt like it
Click to expand...
Click to collapse
That is correct, I still see Superuser and TB says as Root Access OK in first screen. So Root seems fine with all restarts but not the access settings.
As far as ES File explorer, I used that for editing but once I knew its rooted in 2.3.6 I removed root access from ES File explorer.
not sure as this needs to be fixed. TB does have option, so we could mute the notification about access permanently but I kind of like to make sure this isn't causing some other issue.
sazhagianambi said:
That is correct, I still see Superuser and TB says as Root Access OK in first screen. So Root seems fine with all restarts but not the access settings.
As far as ES File explorer, I used that for editing but once I knew its rooted in 2.3.6 I removed root access from ES File explorer.
not sure as this needs to be fixed. TB does have option, so we could mute the notification about access permanently but I kind of like to make sure this isn't causing some other issue.
Click to expand...
Click to collapse
Don't worry about what TB says.... 6755 is a security hole that you do not want to leave open.... I would use something else.... I am a UNIX/Linux guy by trade, so I am telling you that 4755 is what it should be... Use root explorer and ROM manager instead of TB, I have had way to many issues with TB in the past.
Could you tell please what kind of issues you had?
Im using TB for backing up apps+data and freezing stock/old ones I dont use. Dont want to get by suprise if it goes mad
Thank you!
jimbridgman said:
Don't worry about what TB says.... 6755 is a security hole that you do not want to leave open.... I would use something else.... I am a UNIX/Linux guy by trade, so I am telling you that 4755 is what it should be... Use root explorer and ROM manager instead of TB, I have had way to many issues with TB in the past.
Click to expand...
Click to collapse
Thank you Jim for clearing up, may be I should setup ignore warning then.
Shaliuno said:
Could you tell please what kind of issues you had?
Im using TB for backing up apps+data and freezing stock/old ones I dont use. Dont want to get by suprise if it goes mad
Click to expand...
Click to collapse
TB can and has messed up backups, frozen apps come unfrozen at the worst times, it has a minimal busybox, it has broken root before, it is just more of a headache than anything else... there are several apps that will give much better results.
For freezing apps, try modaco's eazy freezy
For backups, use ROM manager, way more successfull, and VERY stable and tested, and the backups it uses are the same that most manufactures deliver in the fxz and updates, since they are saved in img files, and they can be restored from a default recovery if you really are stuck, and can not even get into it on boot...
For busybox, there are two really good ones, I personally use busybox installer from JRummy16, also the one from Stephen (stericson) is really good too, and I have used it, but had an issue with a version several versions ago, and switched.
I am not bashing TB in any way, so no flames, if you like it.... This is just my experience and I have been using android since 1.4-1.5 version, and I have seen a lot of things....
I bought this phone yesterday, Rooted this morning before work, Voodoo backed it up, and updated to the newest update,
Now when I try to Restore root everything looks grand except Superuser says the su binary is not found.
The su binary is located in /system/bin I believe or xbin but none the less its there. some apps can access root while other cannot..
Any Ideas anyone can give me besides rooting once again, Not an option at work.
Thanks in advanced,
If not let me know and Ill Root again once I'm home, Just looking to play on the slow day.
It's been my experience that on this particular phone Voodoo OTA Root Keeper isn't effective. Simply save the SuperSU.zip on your external SD card and reflash via custom recovery after updating..
The only thing simple is the belief in simplicity.
Haven't Bootloader unlocked yet, used the moto2failgo, or how ever it was to root this morning, so this is what it will be once again once I get home, Thanks for the response, Makes my wonder, the only App that continues to function with root access (aside from Voodoo its self) is Titanium Backup, I am wondering if this is because it has its own busybox and i had not install busybox prior to the update, and cannot now due to lost root.
Dear community,
honestly I considered myself not a noob anymore when it comes to flashing, rooting and installing devices. But obviously I was wrong: Cyanogenmod, Titanium Backup and SuperSU are fooling me to madness. :silly: So I hope to find help here because all I want to do is to restore all apps' data. But I will start at the beginning:
I updated my rooted Nexus 7 LTE to CM 13.0-20151226-NIGHTLY-deb and it turned out that Google Play Services continue to crash, no PlayStore could be loaded and so on. I've searched for this issue and don't want to discuss this here as there are many threads for this already.
However, I deciced to switch to OpenGapps and downloaded the pico package for Android 6 on ARM.
By the way I also switched from CWM recovery to TWRP 2.8.7.1.
Finally, CM was running as expected and I danced my pants off!
During all this I formatted the device completely, but made a backup of all apps using Titanium Backup.
So, I re-installed Titanium Backup, copied the backup files to the device and started to "restore missing apps and data" from the bulk operations menu.
All selected apps were installed perfectly (danced again) but then I noticed that the apps' data was not restored.
I searched for this issue and found instructions saying that SuperSU is needed for Titanium Backup to restore data. That was new to me as TB worked fine without SuperSU on my device all the time.
However, I flashed the latest stable Version of SuperSU from chainfire.
After rebooting, the SuperSU app was installed and when it starts, an error popup appears saying that no su file is installed and this has to be done manually.
When I now start Titanium Backup, it prompts missing root access and consequently does not start up.
Furthermore CM is really unstable and freezes from time to time.
So, I lost root by flashing SuperSU? What irony!
Anyway, I am willing to format and re-install my device another time and I would gladly set SuperSU aside as I never needed it in the past. But I really need to get Titanium Backup working to restore the apps' data.
Can anyone of you help me on this, please? Is SuperSU really necessary or do you know a way to manage Titanium Backup without SuperSU on CM13?
cocororo said:
Dear community,
honestly I considered myself not a noob anymore when it comes to flashing, rooting and installing devices. But obviously I was wrong: Cyanogenmod, Titanium Backup and SuperSU are fooling me to madness. :silly: So I hope to find help here because all I want to do is to restore all apps' data. But I will start at the beginning:
I updated my rooted Nexus 7 LTE to CM 13.0-20151226-NIGHTLY-deb and it turned out that Google Play Services continue to crash, no PlayStore could be loaded and so on. I've searched for this issue and don't want to discuss this here as there are many threads for this already.
However, I deciced to switch to OpenGapps and downloaded the pico package for Android 6 on ARM.
By the way I also switched from CWM recovery to TWRP 2.8.7.1.
Finally, CM was running as expected and I danced my pants off!
During all this I formatted the device completely, but made a backup of all apps using Titanium Backup.
So, I re-installed Titanium Backup, copied the backup files to the device and started to "restore missing apps and data" from the bulk operations menu.
All selected apps were installed perfectly (danced again) but then I noticed that the apps' data was not restored.
I searched for this issue and found instructions saying that SuperSU is needed for Titanium Backup to restore data. That was new to me as TB worked fine without SuperSU on my device all the time.
However, I flashed the latest stable Version of SuperSU from chainfire.
After rebooting, the SuperSU app was installed and when it starts, an error popup appears saying that no su file is installed and this has to be done manually.
When I now start Titanium Backup, it prompts missing root access and consequently does not start up.
Furthermore CM is really unstable and freezes from time to time.
So, I lost root by flashing SuperSU? What irony!
Anyway, I am willing to format and re-install my device another time and I would gladly set SuperSU aside as I never needed it in the past. But I really need to get Titanium Backup working to restore the apps' data.
Can anyone of you help me on this, please? Is SuperSU really necessary or do you know a way to manage Titanium Backup without SuperSU on CM13?
Click to expand...
Click to collapse
lmao, your title is nice!
i believe your problem is you used the wrong su zip, you need the latest beta, not stable. should be .52 if im not mistaken. .52 is stable even though its not listed as, i have been using it for some time, and its whats needed for M. you may even find some .6 versions, dont use those, they are systemless, well you can if you want lol. i havent tried them yet, so i dont know what pitfalls may lurk.
Thank you for your help and I am happy to entertain
bweN diorD said:
i believe your problem is you used the wrong su zip, you need the latest beta, not stable. should be .52 if im not mistaken.
Click to expand...
Click to collapse
I will try to update SuperSU as soon as possible.
But sadly TWRP now freezes a few moments after I start the device in recovery mode. When the device starts normally, it freezes as well while showing the CM launcher screen. It stays animated but nothing happens. I will try to re-install TWRP via fastboot flash and then install SuperSU .52 and post my experiences here. :fingers-crossed:
Hi again bweN diorD,
bweN diorD said:
i believe your problem is you used the wrong su zip, you need the latest beta, not stable. should be .52 if im not mistaken.
Click to expand...
Click to collapse
Sorry to say so but SuperSU .52 does not solve the problem. In fact, after flashing the BETA-SuperSU-v2.52.zip using TWRP, CM does not start up anymore. The loading screen with the hypnotizing smiley appears and stays animated but even after 15 minutes CM does not start up. Even TWRP was freezing from time to time.
So I re-installed TWRP, CM and Gapps like in my first post again.
So, is the problem that my device is not rooted indeed? Could this be fixed with CF-autoroot or any tool like this?
I found this thread http://forum.xda-developers.com/showthread.php?t=2448352 although it is for the device deb-razor and my device's bootloader says it is a deb-zoo. By the way, the bootloader displays "LOCK STATE - unlocked".
cocororo said:
Hi again bweN diorD,
Sorry to say so but SuperSU .52 does not solve the problem. In fact, after flashing the BETA-SuperSU-v2.52.zip using TWRP, CM does not start up anymore. The loading screen with the hypnotizing smiley appears and stays animated but even after 15 minutes CM does not start up. Even TWRP was freezing from time to time.
So I re-installed TWRP, CM and Gapps like in my first post again.
So, is the problem that my device is not rooted indeed? Could this be fixed with CF-autoroot or any tool like this?
I found this thread http://forum.xda-developers.com/showthread.php?t=2448352 although it is for the device deb-razor and my device's bootloader says it is a deb-zoo. By the way, the bootloader displays "LOCK STATE - unlocked".
Click to expand...
Click to collapse
hmmm,
i havent used 2.52 on a cm rom, but i have used it on plenty aosp 6.0.* roms without issue.
clean things up so its booting again, then look in developer options and make sure root is turned on. i have seen a few times devs default it to off, but i have never seen a custom rom come not rooted at all.
bweN diorD said:
clean things up so its booting again, then look in developer options and make sure root is turned on.
Click to expand...
Click to collapse
Thanks for your support!
I cleaned everything up -- meaning re-installed everything -- so the device boots up. I checked the developer options and root is set to "apps only". That worked up to now.
Speaking of root: As I wrote I used to have CWM and switched to TWRP. Anyhow, CWM always asked to "fix root" when exiting. I think that's why things worked then and now with TWRP this "fix root" option is gone. But why is SuperSU not working for my Nexus 7 deb? I also tried to install older versions like advised in the Nexus 7 thread here but there was not even a SuperSU app.
So, I recap: CWM used to fix root, TWRP does not. That's why installing SuperSU seems to be a good idea. SuperSU's latest version freezes CM at start-up. Without SuperSU Titanium Backup does not restore app data while other apps do not have problems to get root access. I'm confused
cocororo said:
Thanks for your support!
I cleaned everything up -- meaning re-installed everything -- so the device boots up. I checked the developer options and root is set to "apps only". turn it on apps and adb and see if that helps, thats the preferred setting anywaysThat worked up to now.
Speaking of root: As I wrote I used to have CWM and switched to TWRP. Anyhow, CWM always asked to "fix root" when exiting. I think that's why things worked then and now with TWRP this "fix root" option is gone. its not gone in twrp, it sees that you have root and doesnt ask. really its unadvised to use the twrp generated root anyways But why is SuperSU not working for my Nexus 7 deb? I also tried to install older versions like advised in the Nexus 7 thread here but there was not even a SuperSU app.hmm, maybe thats the problem, maybe you need to install supersu to get things working properly. its on the play store, give it a shot
So, I recap: CWM used to fix root, TWRP does not. That's why installing SuperSU seems to be a good idea. SuperSU's latest version freezes CM at start-up. Without SuperSU Titanium Backup does not restore app data while other apps do not have problems to get root access. I'm confused
Click to expand...
Click to collapse
^^^^
so to clarify your last paragraph, when you say that installing supersu breaks things, were talking about the zip right?
i just want you to get the app from the play store, if you havent tried that alone yet. but change the root setting too.
bweN diorD said:
so to clarify your last paragraph, when you say that installing supersu breaks things, were talking about the zip right?
i just want you to get the app from the play store, if you havent tried that alone yet. but change the root setting too.
Click to expand...
Click to collapse
Correct, I was talking about the zip which is meant to be installed through TWRP.
So, I downloaded the SuperSU app after double-checking that root is set to "Apps & ADB" in the developer settings. Btw. debugging and installation from unknown sources (I hope this is the right translation for this feature) is enabled as well.
When I started the SuperSU app, it first says the binary SU needs an update and I could choose the installation method: When choosing "normal", the app tried to install but failed saying "Installation failed! Restart device and try again!" but even after restarting this was what the app gave me. When I chose "TWRP" the app rebooted the device to recovery but I assume this would end up in installing the zip file which crashed my CM.
Finally, I installed CF-autoroot for deb via the .bat file included in the CF-autoroot package. Now, SuperSU and Titanium Backup are not complaining anymore, so I think this root issue is fixed! :highfive: (couldn't find a dancing smiley).
However, Titanium Backup is not bringing back my app data The restore process seems good as Titanium Backup installs missing apps but even if I install an app the official way via PlayStore and then restore the app's data from my backup using Titanium Backup, there is no effect and the app acts like being installed freshly.
TB claims "restore successful" but the app's data is still missing. I will now check if the backup files are really sound and if I can get them to work on another device. The worst thing I could imagine is that TB did not backup data of apps which had been installed on sdcard. In that case, the data is lost, I'm afraid...
Do you have an idea how this could be or what I could try?
cocororo said:
Correct, I was talking about the zip which is meant to be installed through TWRP.
So, I downloaded the SuperSU app after double-checking that root is set to "Apps & ADB" in the developer settings. Btw. debugging and installation from unknown sources (I hope this is the right translation for this feature) is enabled as well.
When I started the SuperSU app, it first says the binary SU needs an update and I could choose the installation method: When choosing "normal", the app tried to install but failed saying "Installation failed! Restart device and try again!" but even after restarting this was what the app gave me. When I chose "TWRP" the app rebooted the device to recovery but I assume this would end up in installing the zip file which crashed my CM.
Finally, I installed CF-autoroot for deb via the .bat file included in the CF-autoroot package. Now, SuperSU and Titanium Backup are not complaining anymore, so I think this root issue is fixed! :highfive: (couldn't find a dancing smiley).
However, Titanium Backup is not bringing back my app data The restore process seems good as Titanium Backup installs missing apps but even if I install an app the official way via PlayStore and then restore the app's data from my backup using Titanium Backup, there is no effect and the app acts like being installed freshly.
TB claims "restore successful" but the app's data is still missing. I will now check if the backup files are really sound and if I can get them to work on another device. The worst thing I could imagine is that TB did not backup data of apps which had been installed on sdcard. In that case, the data is lost, I'm afraid...
Do you have an idea how this could be or what I could try?
Click to expand...
Click to collapse
sorry, i really dont know what happens as far as titanium when you put an app on the sd.
glad you got root working though, although i still dont understand why it wouldnt work the right way.
if you run into any more specific road blocks, ill try and help if i can, but this general problem with the data, i havent a clue the problem or solution, short of the data isnt there completely.
Hi again,
sorry for my late reply! I tried a couple of things but here's the most obvious one:
Apparently the backup files are kind of corrupt. I don't know what went wrong there but TB did not create a full backup. Indeed there is a .tar.gz file for every app but in fact none of these has more than 2 KB. So I strongly assume that this might be the mistake - which also means that all my app's data is lost.
bweN diorD said:
glad you got root working though
Click to expand...
Click to collapse
At least this is a success and I am happy to have TWRP, OpenGapps and Titanium Backup running on a fully rooted device :good:
Thank you for all your time and help! I really appreciate how supportive we "techies" are :highfive:
Have a great day and - a bit late but anyway - a happy new year!