07-12-2014 06:53 AM
177 1234 ...
tools
  1. 2defmouze's Avatar
    One example of a questionable green app is Nova Launcher, which is usually included with AOKP roms (which I almost exclusively run). Assuming it's included in the rom, I know I don't need to restore. However, in the event it's not included, I want it to be restored. Do you suggest just re-installing from the play store if it's not in the rom, or potentially restoring an app that's already installed? Or am I thinking about this too much and I just need to move on?

    Sent from my Galaxy Nexus using Tapatalk 2
    Move on... Lol

    Nah with launchers you have simple options, since the launcher backs up your settings and stuff anyway, if you later want it back on a ROM it didn't come preinstalled in, I would do as you said and just download it from Play then restore your settings and desktop stuff within Nova.. It should work fine I've done it before

    Sent from my Galaxy Nexus using Tapatalk 2
    Empty Hand likes this.
    07-31-2012 01:39 PM
  2. jean15paul's Avatar
    Yeah honestly I go back and forth on that one as well. It's a relatively new feature of TiBu.. so I went a long time just having my Android ID# change every time I flashed something, and now that I have the option I don't really know what to do with it, lol. I usually just have it ignore it since I never have issues with it anyway.
    Huh? I wonder if keeping your previous Android ID# would prevent the issue of everytime yo flash a rom you end up with a new device authorized in Google Music? If you keep you ID number the same, would Google Music recognize that it's the same device and not create a new authorization?
    08-01-2012 10:09 AM
  3. dmmarck's Avatar
    Huh? I wonder if keeping your previous Android ID# would prevent the issue of everytime yo flash a rom you end up with a new device authorized in Google Music? If you keep you ID number the same, would Google Music recognize that it's the same device and not create a new authorization?
    Yes, it will. This exact usage was just discussed in the AOKP thread, seems very interesting.
    2defmouze likes this.
    08-01-2012 10:11 AM
  4. 2defmouze's Avatar
    Huh? I wonder if keeping your previous Android ID# would prevent the issue of everytime yo flash a rom you end up with a new device authorized in Google Music? If you keep you ID number the same, would Google Music recognize that it's the same device and not create a new authorization?
    I've heard that is correct... however its not a big deal. Google did away with that limit of device deauthorizations, for now at least, so you can clear them out anyway. If they hadn't believe me I'd be mad.. between all the flashing and setting up I do on my Gnex and Nex7 I'd be out of luck, lol.

    But if its a concern then sure, have it revert to the previous Android ID when you launch it. I have not heard of any issues caused either way to this point.
    08-01-2012 10:12 AM
  5. Nechasin's Avatar
    I've heard that is correct... however its not a big deal. Google did away with that limit of device deauthorizations, for now at least, so you can clear them out anyway. If they hadn't believe me I'd be mad.. between all the flashing and setting up I do on my Gnex and Nex7 I'd be out of luck, lol.

    But if its a concern then sure, have it revert to the previous Android ID when you launch it. I have not heard of any issues caused either way to this point.
    I've a a few issues with apps not restoring correctly before this was implemented. Presto was one app. It is a purchased app that works with other apps to speed up playback of audio. It wouldn't restore properly and said it didn't have authorization. I had to manually install it from play store. Since the restore Android ID was implemented by TiBu, I haven't hadd this issue. I suspect that will get more important as more anti-piracy checks are implemented by apps.
    2defmouze likes this.
    08-01-2012 11:46 AM
  6. 2defmouze's Avatar
    @Nechasin.. makes sense, I might have had one app thing similar to that or heard about a few offhand. Since it's an option maybe I'll add that in the tips section or just to the main guide. Will research a bit and wait til I learn more about pros/cons of either choice though.. I like to be thorough
    08-01-2012 11:50 AM
  7. Crossfire503's Avatar
    Thanks for this post. I was getting a feel for much of this recently, thanks to flashing a few different ROMs and needing to rely on Tibu to keep the process of restoring apps reasonable. This guide clarifies much of what I was learning and the filter suggestion, combined with creating an update zip, is amazing. Tibu is an excellent tool, but pretty rough without a guide like this.
    08-01-2012 11:39 PM
  8. Canuckfan's Avatar
    I've a a few issues with apps not restoring correctly before this was implemented. Presto was one app. It is a purchased app that works with other apps to speed up playback of audio. It wouldn't restore properly and said it didn't have authorization. I had to manually install it from play store. Since the restore Android ID was implemented by TiBu, I haven't hadd this issue. I suspect that will get more important as more anti-piracy checks are implemented by apps.
    So what are the steps to backing up your Android ID....do we just have to backup Settings Storage? Then once everything is flashed, we just go into option "Manage Android ID" and restore?
    08-02-2012 04:17 AM
  9. pmcd1962's Avatar
    So what are the steps to backing up your Android ID....do we just have to backup Settings Storage? Then once everything is flashed, we just go into option "Manage Android ID" and restore?
    It will ask you when you first open the app after flashing new ROM. I just followed all the step from the op, so nothing special needs to be done.

    Sent from my Galaxy Nexus using Android Central Forums
    Canuckfan, Nechasin and 2defmouze like this.
    08-02-2012 05:20 AM
  10. Empty Hand's Avatar
    2defmouze, Thank you for this guide! I set up TiBu the other day and finally had a chance to do a clean install today using TiBu and following your guide step by step. I had been using mybackup pro, but TiBu is so much faster and using labels to separate data and non data apps is great. This will take a good 30 minutes off my clean install time.

    Sent from my Galaxy Nexus using Tapatalk 2
    2defmouze and Nechasin like this.
    08-02-2012 12:45 PM
  11. 2defmouze's Avatar
    2defmouze, Thank you for this guide! I set up TiBu the other day and finally had a chance to do a clean install today using TiBu and following your guide step by step. I had been using mybackup pro, but TiBu is so much faster and using labels to separate data and non data apps is great. This will take a good 30 minutes off my clean install time.

    Sent from my Galaxy Nexus using Tapatalk 2
    Good to hear.. Yeah that label trick saves me a good 10 minutes off every clean flash as well

    Sent from my Galaxy Nexus using Tapatalk 2
    Empty Hand and Nechasin like this.
    08-02-2012 01:03 PM
  12. Canuckfan's Avatar
    Has anyone tried backing up their personal user dictionary with TiBu? Not sure if it'll work going from ICS > JB.

    Also, is it ok to backup/restore Google Wallet? I will definitely be resetting it before flashing.
    08-02-2012 08:34 PM
  13. 2defmouze's Avatar
    Has anyone tried backing up their personal user dictionary with TiBu? Not sure if it'll work going from ICS > JB.

    Also, is it ok to backup/restore Google Wallet? I will definitely be resetting it before flashing.
    Dictionary I've heard is ok.. I use swiftkey so I back that up and restore it with data no problem.

    Wallet never restore with data. Before you wipe reset it within the app. Afterwards, you should be alright restoring it without data, just like other Google apps.. Tho since it's a special case app that uses the secure element and all that, I'd rather recommend you find a link and install it fresh. But if you do it without data in tibu it should be alright... Again making sure you reset it before wiping and flashing the new ROM.

    Sent from my Galaxy Nexus using Tapatalk 2
    Canuckfan likes this.
    08-02-2012 08:40 PM
  14. SuperChargedJ's Avatar
    Thanks for this awesome guide. Went through the first couple of steps so I would be ready when I had to reflash.
    08-02-2012 10:19 PM
  15. jean15paul's Avatar
    Feedback!

    First of all, thanks again for a great guide to TiBu. I'm brand new to this rooting thing, and your guide took a overwhelming (for me) process of backing up my apps and made it really easy to understand.

    So I flashed a ROM on my (Sprint) Galaxy Nexus yesterday. It was the first time I flashed since reading this guide and using TiBu (2nd time flashing overall). The first time I flashed a ROM, I got some buggy behavior. It was because I wiped everything except internal storage. The folks over at XDA told me that because the Galaxy Nexus doesn't have a seperate partition for it's virtual SD card (instead it's just one big partition for "internal storage" and "sd card") I had to fully wipe my internal storage to get a clean flash. Sure enough, when I wiped my internal storage too (in addition to data, cache, and dalvik) and reflashed, then the bugginess went away.

    I point this out because this adds the extra steps to your guide of saving your "update.zip" file and the entire "/sdcard/TitaniumBackup" folder to your computer, and then pushing them back to your phones internal storage after you wipe. I assume this wouldn't be necessary on other phones that have an external SD card or a seperate partition for a virtual sd card because those don't have to be wiped when you flash. It's important to make sure everyone understands the difference.
    I have been corrected and don't want to put any bad info out there.

    Personally I used Wifi File Explorer Pro to save the files to my computer (no cables needed) and then I used the cmd commands "adb push update.zip /sdcard/" and "adb push TitaniumBackup /sdcard/TitaniumBackup" (no quotes ... not sure if I needed a slash at the end of the latter command) to easily push those files back onto my phone after wiping through recovery.

    Please correct anything that I got wrong. I hope this helps someone.
    08-06-2012 09:18 AM
  16. 2defmouze's Avatar
    Feedback!

    First of all, thanks again for a great guide to TiBu. I'm brand new to this rooting thing, and your guide took a overwhelming (for me) process of backing up my apps and made it really easy to understand.

    So I flashed a ROM on my (Sprint) Galaxy Nexus yesterday. It was the first time I flashed since reading this guide and using TiBu (2nd time flashing overall). The first time I flashed a ROM, I got some buggy behavior. It was because I wiped everything except internal storage. The folks over at XDA told me that because the Galaxy Nexus doesn't have a seperate partition for it's virtual SD card (instead it's just one big partition for "internal storage" and "sd card") I had to fully wipe my internal storage to get a clean flash. Sure enough, when I wiped my internal storage too (in addition to data, cache, and dalvik) and reflashed, then the bugginess went away.

    I point this out because this adds the extra steps to your guide of saving your "update.zip" file and the entire "/sdcard/TitaniumBackup" folder to your computer, and then pushing them back to your phones internal storage after you wipe. I assume this wouldn't be necessary on other phones that have an external SD card or a seperate partition for a virtual sd card because those don't have to be wiped when you flash. It's important to make sure everyone understands the difference.

    Personally I used Wifi File Explorer Pro to save the files to my computer (no cables needed) and then I used the cmd commands "adb push update.zip /sdcard/" and "adb push TitaniumBackup /sdcard/TitaniumBackup" (no quotes ... not sure if I needed a slash at the end of the latter command) to easily push those files back onto my phone after wiping through recovery.

    I hope this helps someone.
    The guys at that other forum have mostly no idea what they are talking about

    Yes, your internal sd card can become corrupted over time and you might occasionally find that doing a complete wipe, internal storage included, might be good for your phone.. but this should be in extremely rare situations. I've done it twice since December, and have flashed around a hundred or more ROMs, lol. All of us regular crackflashers will tell you that when you do a full wipe to flash a new ROM you should pretty much never have to worry about wiping your internal sd, and trust me, we do this A LOT.

    In your case, it is possible the bugginess you experienced required a complete wipe of the phone, but don't assume you should always have to do this. It should only be done in the most extreme cases... 99% of the time a normal Wipe data/factory reset followed by a system wipe before you flash a new ROM will be plenty to ensure a bug free experience. Hope that helps clear things up
    Nechasin and jean15paul like this.
    08-06-2012 09:29 AM
  17. Nechasin's Avatar
    The guys at that other forum have mostly no idea what they are talking about

    Yes, your internal sd card can become corrupted over time and you might occasionally find that doing a complete wipe, internal storage included, might be good for your phone.. but this should be in extremely rare situations. I've done it twice since December, and have flashed around a hundred or more ROMs, lol. All of us regular crackflashers will tell you that when you do a full wipe to flash a new ROM you should pretty much never have to worry about wiping your internal sd, and trust me, we do this A LOT.

    In your case, it is possible the bugginess you experienced required a complete wipe of the phone, but don't assume you should always have to do this. It should only be done in the most extreme cases... 99% of the time a normal Wipe data/factory reset followed by a system wipe before you flash a new ROM will be plenty to ensure a bug free experience. Hope that helps clear things up
    I agree, I have never done a full complete wipe of my internal SD card. But having said that I do recommend that you keep backups off your phone in case soemthing catastrophic happens to your phone and you want to be able to recover your data. I actually have mine setup to back up once a week (if I stay on a ROM that long) and upload the backup to Dropbox.
    08-06-2012 10:56 AM
  18. jean15paul's Avatar
    The guys at that other forum have mostly no idea what they are talking about
    LOL!

    Yes, your internal sd card can become corrupted over time and you might occasionally find that doing a complete wipe, internal storage included, might be good for your phone.. but this should be in extremely rare situations. I've done it twice since December, and have flashed around a hundred or more ROMs, lol. All of us regular crackflashers will tell you that when you do a full wipe to flash a new ROM you should pretty much never have to worry about wiping your internal sd, and trust me, we do this A LOT.

    In your case, it is possible the bugginess you experienced required a complete wipe of the phone, but don't assume you should always have to do this. It should only be done in the most extreme cases... 99% of the time a normal Wipe data/factory reset followed by a system wipe before you flash a new ROM will be plenty to ensure a bug free experience. Hope that helps clear things up
    Thanks for the info. I'm still pretty new at this, so I appreciate the feedback. If you don't mind me bugging you with more questions. This is my first ever custom ROM. I'm using TWRP because the devs recommended TWRP over CWM for this specific ROM. I've heard that you need to wipe "data, cache, and dalvik". On my first attempt I did these 3 wipes from the TWRP wipe menu: "Factory Reset", "Cache", and "Dalvik Cache". Are those the correct things to wipe? After flashing the volume controls and headphones weren't working (a problem that no one else had). Maybe it was just a bad flash or something, I don't know. Someone recommended that I also wipe internal storage, so the 2nd time I did "Factory Reset", "Cache", "Dalvik Cache", and "Internal Storage". After flashing the 2nd time everything worked perfectly. Maybe it was just a coincidence.

    Anyway, after your response I just want a 2nd opinion. What exactly do I need to wipe when trying to get a clean flash?

    Thanks in advance.
    08-06-2012 12:53 PM
  19. 2defmouze's Avatar
    LOL!



    Thanks for the info. I'm still pretty new at this, so I appreciate the feedback. If you don't mind me bugging you with more questions. This is my first ever custom ROM. I'm using TWRP because the devs recommended TWRP over CWM for this specific ROM. I've heard that you need to wipe "data, cache, and dalvik". On my first attempt I did these 3 wipes from the TWRP wipe menu: "Factory Reset", "Cache", and "Dalvik Cache". Are those the correct things to wipe? After flashing the volume controls and headphones weren't working (a problem that no one else had). Maybe it was just a bad flash or something, I don't know. Someone recommended that I also wipe internal storage, so the 2nd time I did "Factory Reset", "Cache", "Dalvik Cache", and "Internal Storage". After flashing the 2nd time everything worked perfectly. Maybe it was just a coincidence.

    Anyway, after your response I just want a 2nd opinion. What exactly do I need to wipe when trying to get a clean flash?

    Thanks in advance.
    Sounds like you did everything right the first time.. Chalk it up to a bad flash or a rare case of corrupted data. Normally those instructions should do you just fine

    Sent from my Galaxy Nexus using Tapatalk 2
    jean15paul likes this.
    08-06-2012 12:57 PM
  20. VAVA Mk2's Avatar
    Excellent post, 2defmouze! Some new tips I can use from that.

    Sent from my Galaxy Nexus using Android Central Forums
    2defmouze likes this.
    08-06-2012 03:33 PM
  21. Keekers11's Avatar
    So when I verfiy my backups, it tells me there was one error found then gives me a choice to delete the backup. I have no idea what the error is.
    08-07-2012 04:18 PM
  22. 2defmouze's Avatar
    So when I verfiy my backups, it tells me there was one error found then gives me a choice to delete the backup. I have no idea what the error is.
    Sounds like the wise idea would be to accept the delete option and just remake the backups.

    Sent from my Galaxy Nexus using Tapatalk 2
    08-07-2012 04:19 PM
  23. Keekers11's Avatar
    Sounds like the wise idea would be to accept the delete option and just remake the backups.

    Sent from my Galaxy Nexus using Tapatalk 2
    Already tried that
    08-07-2012 04:22 PM
  24. 2defmouze's Avatar
    Already tried that
    Try this.. Uninstall TiBu, then using Root explorer or whatever, go into your /sdcard/TitaniumBackup folder and just delete everything in it (you can do it from your computer as well if it's easier to select everything that way).

    Reboot, reinstall TiBu and start from scratch creating backups again.

    Let me know how that turns out.. Sorry I'm shooting guesses here, have never had that error in like 10 months using TiBu, lol..

    Sent from my Galaxy Nexus using Tapatalk 2
    08-07-2012 04:28 PM
  25. Keekers11's Avatar
    Try this.. Uninstall TiBu, then using Root explorer or whatever, go into your /sdcard/TitaniumBackup folder and just delete everything in it (you can do it from your computer as well if it's easier to select everything that way).

    Reboot, reinstall TiBu and start from scratch creating backups again.

    Let me know how that turns out.. Sorry I'm shooting guesses here, have never had that error in like 10 months using TiBu, lol..

    Sent from my Galaxy Nexus using Tapatalk 2
    And people think it's flattering to tell me I'm the first!
    I'm counting on you here
    08-07-2012 07:33 PM
177 1234 ...
LINK TO POST COPIED TO CLIPBOARD