Related
I'm having a problem completing the upgrade to 2.2. I have a XT720 from Cincinnati Bell and was following the procedure from their website. I successfully did this upgrade on my XT720 and was upgrading my wife's phone. Everything was going the same as my phone until I got to "Install System Recovery". When it was pressed there was no prompt for super user access. It came back and said successful install and I pressed the OK. Then I pressed the "Recovery Reboot" and nothing happened.
After that happened I did a factory reset, using the settings>privacy>factory data reset menu , and tried again with the same result.
I'm sure this has something to do with not prompting for the superuser access. What might be happening?
Same happened to me first go around. There tutorial Os horrible. Revs is better. All I Did was restart And then I got the SU prompt. Use universal androot And root again If su isant in your app list. Universal androots is more convenent than super one click
Disconnect the phone from the PC before using the install option from the System Recovery app.
3rdstring said:
Disconnect the phone from the PC before using the install option from the System Recovery app.
Click to expand...
Click to collapse
I cant remember, but I think I did do that one time. I think I went through the whole procedure 4 times.
Why do you think there was no prompt for the su access?
easye420 said:
Same happened to me first go around. There tutorial Os horrible. Revs is better. All I Did was restart And then I got the SU prompt. Use universal androot And root again If su isant in your app list. Universal androots is more convenent than super one click
Click to expand...
Click to collapse
I searched for user rev or revs to see that tutorial but didn't find anyone. Is that short for something? Can you post the link to that tutorial? Thanks
punchback said:
I searched for user rev or revs to see that tutorial but didn't find anyone. Is that short for something? Can you post the link to that tutorial? Thanks
Click to expand...
Click to collapse
http://www.youtube.com/user/reverendkjr
Mioze7Ae said:
http://www.youtube.com/user/reverendkjr
Click to expand...
Click to collapse
Thanks, didnt have time to post it.
3rdstring said:
Disconnect the phone from the PC before using the install option from the System Recovery app.
Click to expand...
Click to collapse
Well tonight I gave it another try and I disconnected from the laptop before starting the recovery app. No joy! Here's what happened after following the CBW instructions and skipping the optional Titainium backup step.
1. Started System Recovery from the phone per pg 15 of the CBW instructions.
2. Pressed "Install Recovery System". I did not get a request for super user access but it did say install success and I pressed OK. Almost immediately after pressing OK I got the following error
"Activity System Recovery (in application System Recovery) is not responding. Force Close or Wait.
I pressed wait and nothing else happened.
3. I pressed "Recovery Boot" and after a short time got the above error again and I again pressed wait. Nothing ever happened.
This all worked fine on my phone!
Any Ideas?
punchback said:
Well tonight I gave it another try and I disconnected from the laptop before starting the recovery app. No joy! Here's what happened after following the CBW instructions and skipping the optional Titainium backup step.
1. Started System Recovery from the phone per pg 15 of the CBW instructions.
2. Pressed "Install Recovery System". I did not get a request for super user access but it did say install success and I pressed OK. Almost immediately after pressing OK I got the following error
"Activity System Recovery (in application System Recovery) is not responding. Force Close or Wait.
I pressed wait and nothing else happened.
3. I pressed "Recovery Boot" and after a short time got the above error again and I again pressed wait. Nothing ever happened.
This all worked fine on my phone!
Any Ideas?
Click to expand...
Click to collapse
I think you're not rooted. The System Recovery app always says install success even when it crashes and burns. Did you remember to turn on ADB (Settings > Applications > Development > USB Debugging) before rooting?
You can also try to root using UniversalAndroot 1.6.2-beta5 http://forum.xda-developers.com/showthread.php?t=747598
Another option is that you accidentally denied Superuser access. Open the Superuser app and see what's in the logs/deny lists.
Try running another app that requires root access (e.g. Titanium Backup). Do you get a popup asking about root access?
I just checked and it's still turn on. Does it matter if it's on or off while you're running the Recovery program?
Is there any advantage/disadvantage to using Androot?
Can you check to see if you're rooted?
3rdstring said:
Try running another app that requires root access (e.g. Titanium Backup). Do you get a popup asking about root access?
Click to expand...
Click to collapse
I'll hook er' back up and install Titanium and see if it prompts me for su access. I'll let you know waht happens in a little bit.
When I use Superoneclick it never detects the software version and asks if I'm on 2.0 or higher. Is this some what normal? After i say yes it goes on it's way and seems to complete. It also did this on my phone and it upgraded without a hitch.
Well I installed Titanium Backup and it prompted for su access I clicked OK and it started up. On the main screen of Titanium it says:
Root access: OK (BusyBox 1.17.2 from system)
So I think I'm rooted??
Yes. You can try to uninstall the System Recovery app, reboot, & re-install it. Mod My Mobile has the Open Recovery files & manual installation instructions. Or maybe try copying the OpenRecovery.apk to the sd card & installing it with a file explorer (e.g. ES File Explorer or Astro from the market)
FINALLY!! YEAH!! I'm updated!!
I've watched some videos by reverandkjr and he wipes the Dalvik Cache and the Cache Partition. Should this be done??
punchback said:
Well I installed Titanium Backup and it prompted for su access I clicked OK and it started up. On the main screen of Titanium it says:
Root access: OK (BusyBox 1.17.2 from system)
So I think I'm rooted??
Click to expand...
Click to collapse
Open your Superuser app and see if you've denied access or what the logs say.
Mioze7Ae said:
Open your Superuser app and see if you've denied access or what the logs say.
Click to expand...
Click to collapse
Didn't CB's Froyo have a hidden SU? I can't remember I only ran it for a day or two before Wanhu's was brought to our attention.
Edit: Doh!! not if he hasn't flashed it yet.
I've got into Open Recovery and have already flashed to the 2.2 CBW image. Is there any benefit to wiping the Dalvik Cache and the Cache Partition like I've seen on reverandkjr videos.
I will wipe the Dalvik, cache & data/factory reset whenever I flash a new ROM
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
Hello,
I need to unroot by ICS ROM temporarily so I can install and run certain application, how do I do that with minimum amount of work?
Thanks,
G
Questions belong in Q&A. Moved
artisticcheese said:
Hello,
I need to unroot by ICS ROM temporarily so I can install and run certain application, how do I do that with minimum amount of work?
Thanks,
G
Click to expand...
Click to collapse
i cant c y u would have to unroot, it shouldnt matter as apps dont care if it is rooted or unrooted, correction some apps u have to b rooted to work properly.
do u actually get an error message when trying to install an app
the only way is to restore back to stock, or if u just rooted ur stock firmware, meaning u didnt flash a rom, u can try flashing the system.img file, that might work but i never heard of any1 doing that
Yes, application refuses to work telling me that "rooted" phones are not supported. So basically it installs, checks if phone is rooted and refuses to proceed. I hoped I can flash something in CMW to temporarely unroot, then run application, let it do it one time thing (I need to run this application only once successfully) and then I root back in CWM again.
artisticcheese said:
Yes, application refuses to work telling me that "rooted" phones are not supported. So basically it installs, checks if phone is rooted and refuses to proceed. I hoped I can flash something in CMW to temporarely unroot, then run application, let it do it one time thing (I need to run this application only once successfully) and then I root back in CWM again.
Click to expand...
Click to collapse
dont think there is a temporary unroot method, going back to stock was the true method to unrooting, which app were u trying to install.
u can trying going back to stock, installing app, let it do its thing, backup with tibu or some other backup, reroot and then restore backup of app.....maybe wont work as restoring a backup is actually reinstalling the app
edit: try this i havent so try at ur own risk http://www.thespicygadgematics.com/2012/06/how-to-easily-unroot-any-android-phone.html it seems easy enough, i didnt think it was possible but it seems to b
artisticcheese said:
Hello,
I need to unroot by ICS ROM temporarily so I can install and run certain application, how do I do that with minimum amount of work?
Thanks,
G
Click to expand...
Click to collapse
Using root explorer or ES File Explorer, mount system as r/w, delete /system/app/Superuser.apk, /system/bin/su or /system/xbin/su (it will be in one of those two places), and then reboot. done.
cschmitt said:
Using root explorer or ES File Explorer, mount system as r/w, delete /system/app/Superuser.apk, /system/bin/su or /system/xbin/su (it will be in one of those two places), and then reboot. done.
Click to expand...
Click to collapse
thats deleting the app the rooted the phone, but does it actually undo the rooting process, the system files the app changed to make it rooted r still there, the way to check is if u do delete su app, c if root explorer can can mount ur system folder to r/w, or op can c if it the app does install after deleting su.
actually u need su to grant su, so that might not b a good test
cschmitt said:
Using root explorer or ES File Explorer, mount system as r/w, delete /system/app/Superuser.apk, /system/bin/su or /system/xbin/su (it will be in one of those two places), and then reboot. done.
Click to expand...
Click to collapse
Thanks,
How do I root back after that though?
vincom said:
thats deleting the app the rooted the phone, but does it actually undo the rooting process, the system files the app changed to make it rooted r still there, the way to check is if u do delete su app, c if root explorer can can mount ur system folder to r/w, or op can c if it the app does install after deleting su.
actually u need su to grant su, so that might not b a good test
Click to expand...
Click to collapse
The superuser cwm zip installs su and superuser.apk, that's it. There are no other modified apps.
You can remove busy box also if you like, but it's not much use without su.
artisticcheese said:
Thanks,
How do I root back after that though?
Click to expand...
Click to collapse
Flash superuser zip in cwm.
cschmitt said:
The superuser cwm zip installs su and superuser.apk, that's it. There are no other modified apps.
You can remove busy box also if you like, but it's not much use without su.
Click to expand...
Click to collapse
kool. i learn something everyday
There is cool app in Playstore (free) which allows rooting/unrooting with no reboots and other complicated steps
FYI
https://play.google.com/store/apps/...51bGwsMSwxLDMsImV1LmNoYWluZmlyZS5zdXBlcnN1Il0
Voodoo OTA can do a temp unroot as well. The Flixter app will not allow you to stream movis on a rooted phone. I used Voodoo to temp unroot then went back into Flixter and it started to play the movie.
I use an app called Temp root remover
It allows you to temporarly unroot and reroot in a matter of seconds
I somehow have managed to lose root access. I have superuser installed but the prompt to give root access to apps does not appear anymore.
I tried to do a factory reset, which was a huge mistake as I had changed the dpi and the launcher failed to start after reset. I tried rerooting using sparkym3s auto rooting tool, but no luck.
I now have the device somewhat operational again after installing apex launcher, but several apps show up as incompatible in the market that used to work before.
How can I regain root?
Factory reset clears the /data partition (you should've just renistalled the Superuser app, possibly a different version, or use and run SuperSU), where your installed apps and data are stored, so it will only delete the Superuser app for managing su access, but the su binary itself should remain on the /system partition. Check for it it /system/xbin/su
What's the problem with sparkym3's method anyway?
Thank you for replying.
After installing supersu it appears i have somewhat regained root access.
I can now change dpi with LCD Density Modder.
However, titanium backup, and several other apps dont get root access, and I dont get a prompt asking for access either.
Rootchecker shows that I dont have root access.
When I run the supersu app, it wants to update, i click ok, but i get error message "installation failed. There is nothing in the supersu log or apps tabs.
The su binary is in /system/xbin/su.
Should I un-root and then re-root perhaps?
I have messed around with this thing so much now, that I would prefer to wipe the entire storage and start completely fresh. Is this possible?
According to this topic I had rooted my infinity but now I did a wipe from boot (volume down + power on) so I lost all my apps including superuser app. My answer is: have I got root yet? Or have I lost only superuser app?
Inviato dal mio ASUS Transformer Pad TF700T con Tapatalk 2
maanebedotten said:
I have messed around with this thing so much now, that I would prefer to wipe the entire storage and start completely fresh. Is this possible?
Click to expand...
Click to collapse
Try a few variants of what you've mentioned, if this doesn't help, you can try re-flashing firmware from the bootloader level.
mouse100 said:
According to this topic I had rooted my infinity but now I did a wipe from boot (volume down + power on) so I lost all my apps including superuser app. My answer is: have I got root yet? Or have I lost only superuser app?
Click to expand...
Click to collapse
Just install Superuser from the Playstore and see for yourself before asking You should have your root access back.
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!