Database Info

4349 with market

installed 4349 today....had some minimal trouble with this hack when installing mybackup pro images but works fine besides. anyways i wanted market and the other gapps on a stock rom with zero other changes. ie ota still works etc...
1. save the update.zip to your root drive on your gtablet
2. turn off then reboot pressing the power and volume-up key
3. choose wipe data/factory reset (must do or the next step will not work properly)
4. after it completes choose apply internal update.zip
5. reboot, allow android to stablize
6. run market (apps will show up but the following steps make sure more do)
7. run android settings-> applications -> system applications -> market
stop market
8. run android settings-> applications -> system applications ->google services frame work
clear data then force stop
9. reboot and your market should be fully functional.
link for to gapps on cyanogens site, remember to rename it as update.zip before saving to your gtab http://android.d3xt3r01.tk/cyanogen/gapps/gapps-mdpi-tegra-20101020-signed.zip

Thanks for taking the plunge. I'll give this a shot tonight when I get home and report back.

After I installed 4349 and booted up I took your linked file, renamed it update.zip, and rebooted the tab into recovery. I just flashed it and didn't do anything else. After the tablet rebooted I skipped some of the setup screens for Google framework and when I ran market it started to update apps automatically. So it worked without doing steps 3,7,8 & 9 for me, although updating Angry Birds from market made the tablet quick reboot... Which was fixed by uninstalling and reinstalling. Everything else works ok.

times i tried to skip step 3 the gapps package would not install properly. it would stop early on the install progress bar and no market or any other apps showed up on reboot. as for steps 7,8,9 those are market fix steps...few apps were missing and those are needed to get them to show up. though the default market is much much fuller then previous hacks. would love to know if anyone else has any other issues similar to mine or not.
also has anyone got myback pro working on 4349. i can install it from market but as soon as i restore any of my programs my reboot-up freezes on the tnt logo. only cure is to nvflash and reinstall.

Tried this a few times with a fresh 4339 installed, followed the steps exactly, but never get the google apps to show up. Oddly, during the install of the update.zip, the tablet resets, and boots normally. I expected to be returned to recovery after installing the update.zip

i have done the fix several times now with the same needs step wise and results...mainly cause i am trying to figure out mybackup pro cause it keeps borking by device and i have to nvflash and start over. turbo you did all the steps and didn't get the gapps package working? make sure your stock 4349 other wise the bluish CWM like thing isn't there to load update.zip's. otherwise i am at a loss? anyone else having trouble?

I an ran through all the steps up to 6.... but now there is no Market app.
I checked the update zip that was on my root (/sdcard is what I assume you mean by root as there is where the other update.zip is, though I initially assumed you meant / as the root) and it is the one that was downloaded from here.
What am I missing? It seems to be it installed the basic 4349

the only way i get those results you speak of is when i omit step 3. are you rebooting between as i am not.

I did step 3 as I had to run through the setup again.
I did not reboot in between step 3 and step 4.

should this work if i installed clockwork after the update?

I just went through it again, step by step, and it did the exact same thing. No Market.
Just to clarify, when I hit apply internal update.zip, the gTab reboots for me. In your instructions you say reboot. When mine boots it takes me into the first time user setup for the gTab, which is UELA, timezone, wireless, username then into the Non-Classic (not sure what it is called, but the one with the weather, news, etc) UI.

haven't used cwm with 4349 as i heard it crashes it though a very similar interface is built into this stock rom.

atomicWAR said:
i have done the fix several times now with the same needs step wise and results...mainly cause i am trying to figure out mybackup pro cause it keeps borking by device and i have to nvflash and start over. turbo you did all the steps and didn't get the gapps package working? make sure your stock 4349 other wise the bluish CWM like thing isn't there to load update.zip's. otherwise i am at a loss? anyone else having trouble?
Click to expand...
Click to collapse
Yes, followed all steps, from a completely stock 4349 (with the 4349 recovery), and no gapps installed.
Justin

if you have done the steps exactly i am not sure what to tell you. and yes it should reboot itself. i have tried the fix a dozen times with no issues so i am not sure what it is your doing differant if anything at all. as of right now i can't reproduce anymore results on 4349 as its not showing up on the OTA anymore as my mybackup pro borked me into yet another install. is 4349 still showing up for other people?

Turbo4V said:
Yes, followed all steps, from a completely stock 4349 (with the 4349 recovery), and no gapps installed.
Justin
Click to expand...
Click to collapse
I suspect we are both having the same problem

atomicWAR said:
if you have done the steps exactly i am not sure what to tell you. and yes it should reboot itself. i have tried the fix a dozen times with no issues so i am not sure what it is your doing differant if anything at all. as of right now i can't reproduce anymore results on 4349 as its not showing up on the OTA anymore as my mybackup pro borked me into yet another install. is 4349 still showing up for other people?
Click to expand...
Click to collapse
Can you verify that when you say root you mean /sdcard/?
Outside of the Market is there any way to tell if it did it right, like some file someplace? I checked the /system/app folder and it has none of the apps that were in your update.zip in the app folder, does this mean anything?
I renamed my old update.zip to update_old.zip, could this cause a problem?

yes the root drive i spoke of is /sdcard. i do not think your renamed file should cause a conflict though you might try deleting it and see. again the only time i had this trouble was when i didn't do a factory wipe first...every other time it has worked but i don't know if their is some trouble with 4349 as it seems to have been pulled from the OTA in the last half hour. can anyone else confirm the OTA now set back to 3588?

I deleted update_old.zip, and no dice.
If you come up with some troubleshooting steps I am happy to try them.

210danielz said:
should this work if i installed clockwork after the update?
Click to expand...
Click to collapse
Don't apply Clockwork .08, you will soft brick your tab.

Well I applied the gapps using clockworkmod from roebeet for 1.2 bootloaders and everything flashed fine. Running the latest version so I dunno.
Sent from my HTC Inspire 4G using Tapatalk

Titanium Restore on 3.1

3g Xoom with freshly installed BRD 3.1 packages.
3.1 update went well, reinstalled Titanium to restore everything.
Restore seems to go fine, yet virtually every app that gets restored, once run will FC. Every single time.
Any ideas???
Thanks in advance!

Im not sure, but I think it has something to do with the fact that the update gave us a new android version. I dealt with the same problem last night as well. What was weird was that the only app that restored the app+data without FC probkems was Angry Birds.
Restoring the apps only (no data) worked every time though...

Reboot into recovery, Fix permissions, reboot. I had no problems at all after doing this.

When i use titanium backup i'm only showing some xoom functions, not my apps. How do i fix that? Did look for threads before posting btw.

I had this problem also. I tried restoring all my apps + data and got force closes. I uninstalled the apps and downloaded them from the market- they'd work.. Try to restore data to the newly downloaded app and again it would FC. Market doesn't recognize the apps that are replaced via Titanium Backup so I had to download them anyway just so I would be able to stay updated.
Another problem I had- Titanium no longer recognizes that I bought the pro version. I downloaded both parts (titanium free and the pro version- that's just a key...) but Titanium doesn't open all features after downloading Pro from Market. I see donate version only beside hypershell, etc...
It also takes a VERY long time to ask for root rights when starting up... Anyone else?
I will try to restore one app from Titanium and fix permissions as mentioned earlier in the thread. Here goes nothin'....
To the guy having issues finding his apps- try installing the busybox installer from jrummy16 in the market (the other one didn't work for me), install busybox 1.9 from it because the busybox that TB installs didn't work for me (and other people) and then make sure in your preferences that you have the correct folder selected for backing up. The autodetect worked for me.
EDIT: Wow! Fixing permissions solved the FC issue- now I can restore all my apps. The problem with TB not recognizing that I've downloaded Pro version remains however.

MileHighClubAV8R said:
I had this problem also. I tried restoring all my apps + data and got force closes. I uninstalled the apps and downloaded them from the market- they'd work.. Try to restore data to the newly downloaded app and again it would FC. Market doesn't recognize the apps that are replaced via Titanium Backup so I had to download them anyway just so I would be able to stay updated.
Another problem I had- Titanium no longer recognizes that I bought the pro version. I downloaded both parts (titanium free and the pro version- that's just a key...) but Titanium doesn't open all features after downloading Pro from Market. I see donate version only beside hypershell, etc...
It also takes a VERY long time to ask for root rights when starting up... Anyone else?
I will try to restore one app from Titanium and fix permissions as mentioned earlier in the thread. Here goes nothin'....
To the guy having issues finding his apps- try installing the busybox installer from jrummy16 in the market (the other one didn't work for me), install busybox 1.9 from it because the busybox that TB installs didn't work for me (and other people) and then make sure in your preferences that you have the correct folder selected for backing up. The autodetect worked for me.
EDIT: Wow! Fixing permissions solved the FC issue- now I can restore all my apps. The problem with TB not recognizing that I've downloaded Pro version remains however.
Click to expand...
Click to collapse
I'm having the same issues you are having with TB. It takes a very long time to get root permissions and it will not recognize my pro key either. It says "Reboot / See checkout.google.com". I found a thread ( http://forum.xda-developers.com/showthread.php?p=13728994&highlight=titanium#post13728994 ) that has mention of what at least one person was able to do to get it working, but it's not working for me. My busybox is v1.18.4, but it's just not working.

Fixing permissions didn't do it for me, but I appreciate the response.
It's weird- the apps and data install fine. I run the apps and they seem to load alright but within 2 or 3 seconds they always FC.
It's very odd....
Thanks for the replies folks!

Titanium has been updated. Everything works great now.

[SOVLED] No Lock (and others) after latest KF update

Yeah, they all FC now. I've tried several things, wipes, clears, the usual suspects, but it seems they might have built something in to deliberately block the current methods for disabling their stupid lock screen.
If anyone has any suggestions, I'm open to them.
Check below. Moving the app from /data/app to /system/app seems to be the solution to this problem.

I thought the same thing cuz mine would block the default screen but it would just be blank even when I chose a picture so I looked at my version # and it had done an OTA update to 6.3
Sent from my Kindle Fire using xda premium

No No Lock without root?
my KF is rooted from the NFX update from 6.2.2 (which puts me at 6.3 of course); I've installed No Lock as a system app (selected in Titanium Backup, which was really just moving to the \system\app\ directory anywho), no force closing issues, seems to work quite fine
can't speak for all situations, but, theoretically, anyone rooted should not be bothered with a problem; shouldn't even have to Stay rooted

4iiiidnerd said:
my KF is rooted from the NFX update from 6.2.2 (which puts me at 6.3 of course); I've installed No Lock as a system app (selected in Titanium Backup, which was really just moving to the \system\data\ directory anywho), no force closing issues, seems to work quite fine
can't speak for all situations, but, theoretically, anyone rooted should not be bothered with a problem; shouldn't even have to Stay rooted
Click to expand...
Click to collapse
You are awesome, thank you! I had removed it, so I installed it again, and before even trying to open it I used Root Explorer to move it from /data/app to /system/app, renamed it to a friendly name (NoLock.apk), and rebooted. Works just fine now, widget included!

[Q] Removing ads, an app that sticks?

Morning all.
So i'm on a rooted 4.3 sense 5.5 Rom but can't seem to get rid of ads.
I've tried AdAway 2.8 and AdFree 0.8.66 but both work for a few hours then revert back. If I reboot as suggested my changes are reverted as if I never ran the program in the first place.
Any suggestions?

elmuziko said:
Morning all.
So i'm on a rooted 4.3 sense 5.5 Rom but can't seem to get rid of ads.
I've tried AdAway 2.8 and AdFree 0.8.66 but both work for a few hours then revert back. If I reboot as suggested my changes are reverted as if I never ran the program in the first place.
Any suggestions?
Click to expand...
Click to collapse
Which ROM are you running? Real stock, but rooted? Your problem is HTC system protection, it's reverts all system changes on boot or specific system events....
I'd recommend this ROM - choose the deodex ROM - the ROM includes a modded kernel which removes the protection.....
Or you could S-OFF, but read this first!
Have fun!
Any issues, let me know!

Morning,
Yeah the deox ROM is the one I'm on thanks to your recommendation.
Originally I could never get Xposed or SuperSU to work but ever since that ROM, and the SuperSU mentioned in the post and Xposed 2.4.1 these have been fine which is why I wondered if maybe there were updates available for the ad away apps.
Is there a way of re-flashing the kernal without taking the ROM back to the initial setup?

elmuziko said:
Morning,
Yeah the deox ROM is the one I'm on thanks to your recommendation.
Originally I could never get Xposed or SuperSU to work but ever since that ROM, and the SuperSU mentioned in the post and Xposed 2.4.1 these have been fine which is why I wondered if maybe there were updates available for the ad away apps.
Is there a way of re-flashing the kernal without taking the ROM back to the initial setup?
Click to expand...
Click to collapse
Before we go to flash city, try this version of adaway https://db.tt/nVzVc7m5
You may have to try and apply a few times, if it gets stuck on applying, reboot and try again

yeah that's the one i have.
Is it as easy to apply the host files from recovery or bootloader if flashing the kernal is tricky?
Thanks again for your help, you're becoming super helper guy for me!

elmuziko said:
yeah that's the one i have.
Is it as easy to apply the host files from recovery or bootloader if flashing the kernal is tricky?
Thanks again for your help, you're becoming super helper guy for me!
Click to expand...
Click to collapse
You could have the generated hosts file written to an alternative location by setting it in preferences - then move it manually.... BUT you shouldn't need to....
The kernel is integrated into the ROM, there isn't a custom ROM available to flash....
Can you screenshot the errors you get, and also go to supersu and select full logging for adaway, once done, try updating and applying.... Send the supersu logs please!
Sent by my favorite carrier pigeon.... hope he comes back.....

Eugh, now it appears ad-away has taken a turn for the worse.
Removed, rebooted, reinstalled.
See attached. Computer sez no.
Worth a complete re-install of ROM?

Do you have Titanium Backup Pro? If so.....
Remove the app from supersu.
Force Stop the app via apps in settings.
Convert the app to a system app using Titanium Backup (or an alternative app that converts apps system apps, search the store).
Start the app again, supersu will ask for permissions.
Restart your phone.
Try again!

Boy I am not having any luck with this whatsoever.
Ok so I reflashed my ROM with the one mentioned earlier.
Tried AdAway without any jiggery pokery and it applys successfully but then two hours later it's reverted back.
I tried full logging but then AdAway kept crashing.
I tried Titanium backup Pro and spent an hour watching it "Processing... Please wait".
I rebooted, Opened ESFileExplorer, mounted the System folder, copied AdAway into System\Apps, opened the app and it crashed.
Rebooted and AdAway is no longer installed. Slapped it in System\Apps again, managed to open with full logging and got the attached.
I think I'm just destined to have Ad's on a few apps. It just keeps reverting when I reboot.

elmuziko said:
Boy I am not having any luck with this whatsoever.
Ok so I reflashed my ROM with the one mentioned earlier.
Tried AdAway without any jiggery pokery and it applys successfully but then two hours later it's reverted back.
I tried full logging but then AdAway kept crashing.
I tried Titanium backup Pro and spent an hour watching it "Processing... Please wait".
I rebooted, Opened ESFileExplorer, mounted the System folder, copied AdAway into System\Apps, opened the app and it crashed.
Rebooted and AdAway is no longer installed. Slapped it in System\Apps again, managed to open with full logging and got the attached.
I think I'm just destined to have Ad's on a few apps. It just keeps reverting when I reboot.
Click to expand...
Click to collapse
Bizarre.....
Right, I now recommend this rom (sweet updates on the way to!!) http://forum.xda-developers.com/showthread.php?t=2616780
Install this from Play https://play.google.com/store/apps/details?id=stericson.busybox&hl=en
Install adaway....

I found the easiest solution was to install a custom /etc/hosts file, search google for "/etc/hosts adblock"

Try this: http://forum.xda-developers.com/showthread.php?t=2597332 , it works for me with xposed.I am on stock 4.3 rooted. I have tried adfree, adaway, manualy edited hosts but no succes.

CM Titanium Backup and SuperSU - a strange journey to apocalypse?

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!