Related
I have been trying to fix permissions in both terminal and Rom manager and have been getting errors. Rom manager says an error occurred and terminal says not found. I tried restoring a backup and still no go. I am currently on axura 1.3.21.11. If anyone can help I would appreciate it.
myboygino said:
I have been trying to fix permissions in both terminal and Rom manager and have been getting errors. Rom manager says an error occurred and terminal says not found. I tried restoring a backup and still no go. I am currently on axura 1.3.21.11. If anyone can help I would appreciate it.
Click to expand...
Click to collapse
Not sure how useful this statement will be,,,,but oh well.....have you tried re-insatlling busybox.....?
reflash Clockwork Recovery 3.0.0.5 in ROM Manager, boot into recovery and do fix permissions in advanced
Thanks for the help fellas. I reinstalled busybox and its working now.
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).
I created an update.zip with my apps+data using Titanium Backup (Pro) on 5.0.1 before I updated to 5.1. I then did a completely clean flash of the 5.1 image (following these instructions, method 2). After that, I did the basic setup of Android and installed Titanium Backup again from the store. I rebooted, flashed and booted into TWRP, then flashed SuperSU 2.46. Rebooted into the system, gave TiBu root access (since other threads said you need to do that before update.zip files can be flashed). Rebooted back into TWRP, finally try to flash update.zip, but I get the error below. Does anyone know why this would be the case?
Additionally, since receiving the error, I have installed busybox and tried fixing my SD card permissions in case they were the problem, no dice.
I do have all of the individual app backups on my computer if update.zip isn't going to work for some reason, and I took a full TWRP backup before upgrading as well (transferred all to my computer since the instructions clear personal data).
Error message:
Installing '/sdcard/update.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
E:Failed to sysMapFile '/sdcard/update.zip'
Error flashing zip '/sdcard/update.zip'
Updating partition details...
...done
Click to expand...
Click to collapse
UPDATE: Just discovered that Android is doing the "Optimizing apps" process at every single normal boot, whether I flash something or not.
vaindil said:
I created an update.zip with my apps+data using Titanium Backup (Pro) on 5.0.1 before I updated to 5.1. I then did a completely clean flash of the 5.1 image (following these instructions, method 2). After that, I did the basic setup of Android and installed Titanium Backup again from the store. I rebooted, flashed and booted into TWRP, then flashed SuperSU 2.46. Rebooted into the system, gave TiBu root access (since other threads said you need to do that before update.zip files can be flashed). Rebooted back into TWRP, finally try to flash update.zip, but I get the error below. Does anyone know why this would be the case?
Additionally, since receiving the error, I have installed busybox and tried fixing my SD card permissions in case they were the problem, no dice.
I do have all of the individual app backups on my computer if update.zip isn't going to work for some reason, and I took a full TWRP backup before upgrading as well (transferred all to my computer since the instructions clear personal data).
Error message:
UPDATE: Just discovered that Android is doing the "Optimizing apps" process at every single normal boot, whether I flash something or not.
Click to expand...
Click to collapse
You have TWRP and you flash successfully supersu2.46. Why you need update.zip? what is this?
just in case run in terminal:
Code:
su
restorecon -FR /data/media/0
maybe it help.
Q&A for [ ROM ][ Apr 14 ] Stock Rooted YNG1TAS0YL
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ ROM ][ Apr 14 ] Stock Rooted YNG1TAS0YL. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
You are my savior!!! :angel: I tried all version and all methods to mount cm12 on multirom as a secondary but nothing works :crying:, nothing except your version!!!! :victory: As primary i have your cm11 XNPH05Q may depend on this?
Can you tell me the default read ahead buffer size, scheduler, tcp congestion Control??? Thanks
Me too, same problem, i install this rom as secondary on multirom, have you resolved in some way?
YNG1TAS0YL Radio - will it give access to FM radio???
Sir Calkulin, ive just flashed the cm12s stock rom manually, will the YNG1TAS0YL Radio help me access to FM radio? or is this somethin else.. In case this update does help me access FM radio then how do i go about it.. my device is unrooted with bootloader still intact..
I'm a noob so please help me out here..
nitsleo85 said:
Sir Calkulin, ive just flashed the cm12s stock rom manually, will the YNG1TAS0YL Radio help me access to FM radio? or is this somethin else.. In case this update does help me access FM radio then how do i go about it.. my device is unrooted with bootloader still intact..
I'm a noob so please help me out here..
Click to expand...
Click to collapse
What FM radio? They're is no hardware in the OPO for it. The radio referred to is the mobile phone radio.
hi, i'm not able to get rid of the developer options crash in the settings menu. It was a clean install, initially it works, as soon as I reboot starts to fc and never works. I didnt flash any super su zip.
A question about changing the temperature unit.
Thanks for this great rom.
Just a quick question on how to change temperature unit from Fahrenheit to Celsius?
Hello!
As reported in the downloadthread there is a problem with the developer options. I have tried two installs, one as update and a second clean one, the result is the same. Setings get a fc when choosing developer options.
Any solution to this?
Best regards!
I have installed this ROM everything is working, except from i can't find the email app (Boxer) nor can i go into the developer options it comes up with a error report.
Here's what i did when i installed CM12S:
In TWRP recovery mode I did the following:
-Wipe data
-Wipe cache
-Wipe Dalvik cache
-Wipe Internal storage
-Wipe System
-Format data
So after that, no OS is installed.
Then:
-Reboot to recovery
-Transferred your ROM Plus the zip files along with the radio files flashed both files to my USB
Then In recovery mode:
-Connected the USB Flash through OTG cable
-Went to Mount and ticked the OTG
-Went Back
-Selected Install zip and selected to install the rooted stock CM12S zip and then afterwards I flashed the Radio files zip of CM12S.
Then:
-Rebooted and after the boot of the device, I turned off the device and rebooted to recovery mode again.
Then:
-Wiped data
-Wiped Cache
-Wiped Dalvik Cache
-Wiped Internal storage
-Format data
Then I rebooted and after the device booted I left the phone 3-5 minutes to settle.
-Settings
-Backup and Reset
-Unticked the 2 boxes
-Reset device
I then let the phone boot up and left it to settle to let it run the background processes run for 3-5mins.
Should I use the Official ROM then re-root the Phone again or have I missed something?
I haven't used any custom kernels i used the stock one installed that shouldn't cause any issues should it?
Nor do I have the F2SP partition I just used the default stock one installed on the phone.
BootLoop
I flashed it, but i got bootloop.
My device is stock 05Q, Rooted, TWRP Recovery.
Why this problem happen?
Someone please help me. I really want this update...
Hi, I notice an problem, when i flash an kernel like a boeffla beta2 or AK 140 and reboot, when go to the developers options, the application settings crash, and the root don't work. For example when i open titanium backup it say i don't have a SU binary installed and the same thing also happens with other app require root. The procedure i use to flash a kernel is, do an wipe cache and dalvik cache, flash a .zip kernel and reboot.
What can i do for install an kernel without this problem?
Sorry for my bad english, i'm italian.
EDIT: the developers options crash also without the istallation of an kernel, when i reboot the phone for the first time after the os12 flash the developers options crash.
so we can flash it as we do for the OTA or we should have a costum recovery ?
So just to be clear, I flash:
1) the ROM
2) the Extras
3) Reboot and we're good to go?
Missing Boxer
I too flashed this OTA ROM and am missing Boxer. The stock email was wiped away but nothing to replace it but Gmail. Tried flashing again and still nothing. Developer working fine for me. Any ideas?
Hi!
I have two very noob questions.
First:
Can i make clean install, whit keep my personal data, my app locations in the home screen and more.... ( I think no )
Second:
What does it mean "FC"? I am not an English pesron but i try to search that and I think this is not mean " finger cross, or football club..... ;-D"
RZeeyy said:
Hi!
I have two very noob questions.
First:
Can i make clean install, whit keep my personal data, my app locations in the home screen and more.... ( I think no )
Second:
What does it mean "FC"? I am not an English pesron but i try to search that and I think this is not mean " finger cross, or football club..... ;-D"
Click to expand...
Click to collapse
First: No - you'll have to install apps from scrartch, or use something like Titanium Backup or Helium if you want the data kept (not system apps though)
Second: FC = Force Close
Calkulin cm12s settings FC when going to dev options (seems to work)
Hi everybody, i had problems with access to developer options (integer causing com.android.settings crash) and thanks to GenghisZ's answer, i was able to repair this error without flashing rom again.
I have looked in /etc/init.d at 99firstboot you mentioned
I have moved file 99firstboot to another folder to disable it at startup
As it was creating persist.sys.root_access (with a '3' valuethat was causing the error?) in /data/property, i have also moved this file somewhere else.
After that, i have rooted it manually and it seems to work well.
I hope it can help other people... If you have this problem maybe we can try this.
I'm not a developper but i know linux a little.
Thanks for amazing site and read you soon
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!