Develop Bugs

[Q] Quick Question about restoring apps after applying RUU

Hey guys,
Just wondering if anyone could advise me on the quickest/easiest way to restore my 200 or so backed-up apps from the sd-card after I reapply a stock RUU (which I'm doing so that I can install a recent OTA update)
A couple of things I've considered (with my extremely limited knowledge) in advance:
1.) Reinstalling Titanium Backup and trying to use this. Just not sure whether it can do this, ie: does it work from a log (which presumably would have been wiped after the RUU was applied), or does it simply point to a folder on the sd-card (in which case I imagine a fresh new installation of Titanium would be able to retrieve everything)
2.) Installing each and every one individually via the backed-up APK files on the sd-card. (Not my preference, for obvious reasons)
3. Rerooting the phone and then getting R/W access to /system/apps to just paste everything in there (also not my preference, as I am not confident in my knowledge or abilities of this stuff).
Any advice would be greatly appreciated, thanks!

Titanium backup should work fine, if you've got 200+ apps though I would recommend getting the pro version since it is going to take you very long to restore them one at a time.

Wow, I'm surprised that the free version doesn't do a batch restore, as I was able to perform a batch backup of absolutely everything, and really easily.
Thanks for the heads-up and response, mate.

[Q] N7100 adb backup problems, and potential alternatives without rooting?

Yes, I'm a noob. No, I can't keep things brief. I'm sorry video, I just can't do it. Hello XDA. Here's my pickle:
So, my camera's faulty, and I'm going to have to send my Note II back to Kogan. This is my first Android handset, and my first time properly experiencing and using Android (I moved here from a Blackberry Pearl 9100). I don't consider myself a base-line user, I'm competent with many forms of electronics and computing so I quickly settled into Android nicely. Thus far I've rooted, flashed recovery and flashed CyanogenMod 9 for one Android phone (I was the first in my family to make the switch, my sister got a Galaxy Wonder for Christmas and I flashed CM9 so she could have at least ICS for her phone) and it was a fairly straight-forward process, nothing too difficult (although it seems my father's Motorola Defy+ might be a bit trickier).
I'll get to the point, due to the camera being basically dead on arrival, I've got to send it back. I don't want to send it back with all of my personal information intact however, I'd prefer to take a full backup of it and then factory reset the device before sending it away. This is where the warranty clause comes in.
I can't root the device (this action breaks warranty) and therefore can't flash CWM to do a nandroid backup. After some reading, a nandroid sounded like the ideal solution but obviously I can't do that. See, I wanted to backup all of my data, including (if possible) apps, settings, accounts, the works. I really don't want to have to go through the process of re-downloading all of my apps (my internet connection isn't the quickest around) and setting everything up just the way I want it again.
I stumbled across the adb backup technique, and considering the N7100 shipped with Jellybean 4.1 and adb backup requires ICS 4.0+, I thought "Hey, why not. It seems pretty straight forward." I also figured it'd be a small learning experience, I'm thinking about getting into android app development sometime in the near future and needed the SDK anyway so I downloaded and installed that, fired up adb and ran the backup with the following parameters:
Code:
adb backup -f <FILE PATH> -apk -shared -all -nosystem
And it seemed to get stuck on the apk for GTA Vice City. So, after about an hour of sitting, I pulled the plug and tried again. This time it got to Angry Birds and got stuck once more. I decided to run it again, but with a different set of parameters, I thought "Maybe it's getting stuck with the SD card data."
Code:
adb backup -f <FILE PATH> -apk -all -noshared -nosystem
This time it got stuck on Bad Piggies. I pulled the plug once more and started searching for answers, but there's not a huge amount of discussion about the backup function, let alone specific to the Note II. I read some stuff about the One X getting stuck on certain parts, but they certainly weren't games like this.
And that's the thing that links them all, they're games. I'm not sure if that specifically has any effect on the process, but I'm beginning to think that trying to back up EVERYTHING so that I can restore my device to the same state it is in now is a futile effort. Without the ease of a nandroid 'snapshot', I'm running out of ideas. I could go through and delete every game I've installed and try the backup again, but I'd like to see if anyone else has any alternatives or explanations.
Here are my queries, don't feel like you've got to answer them all, they're just the questions I've got in my head right now.
1. Is there any known reason as to why adb backup gets stuck on these apks?
2. Is there a better way of creating some form of 'snapshot' of my device without rooting it?
3. Would Samsung Kies' backup utility keep my app and system settings after a factory reset (in that it'd load up Nova Launcher with all of it's settings, along with the few widgets I have, intact)?
4. Are there any apps that would do this? I've heard Titanium Backup will, but you need to be rooted to use that.
I'm starting to feel that just doing it the manual way is going to be easier in the long run.
With question three, I'm assuming that Kies won't backup any apks, and therefore when my phone is sent back to me I'll have to set it up again, download my required/desired apps and then restore my settings through Kies (which will hopefully also restore settings for apps like Nova Launcher, and even better, for widget applications like HD widgets). However, if I'm wrong and Kies DOES backup apks, I'll just do that, it's so much less screwing around and it does what I wanted it to do but didn't think it did in the first place.
Thanks XDA,
-svdkillswitch
(Also, first post!)
Other information:
Device: GT-N7100 (international)
Carrier: Unlocked, Telstra
Android version: 4.1.1, 'Jelly Bean'
Baseband version: N7100UBALJ1
Build number: JRO03C.N7100UBALJ1
Rooted: No

Easiest way
Root with exynos abuse exploit (method 3 in link)and install titanium backup and backup all data using it. I recommend to save backup folder in Ext SD card.
After finishing this you can unroot from application itself.

dr.ketan said:
Easiest way
Root with exynos abuse exploit (method 3 in link)and install titanium backup and backup all data using it. I recommend to save backup folder in Ext SD card.
After finishing this you can unroot from application itself.
Click to expand...
Click to collapse
Thanks for your help,
You say in the linked post that while it doesn't trigger the flash counter, it can cause problems with the camera. If I'm just temp-rooting, backing it up with Titanium, and then un-rooting it again, none of these effects will remain I assume. I guess it doesn't matter too much anyway actually, because my camera is the reason I'm sending it back in.
And once I get my device back, it's as simple as installing the apk, rooting the device, installing Titanium and restoring my backup from the ext SD.
Sounds good. I'll give it a whirl and let you know how I go. +1'd.
-svdkillswitch

It cause camera issue only if you disable exploit, here you need not to do anything rather thn just root.
-Install that apk file, get device rooted.(there is option to root device in application), you need not to check disable exploit
-Install titanium Pro from market and backup (first select backup location to Ext sd card)
- Once finish, uninstall titanium and unroot device from exynose app
You can also factory reset and send to service centre.

dr.ketan said:
It cause camera issue only if you disable exploit, here you need not to do anything rather thn just root.
-Install that apk file, get device rooted.(there is option to root device in application), you need not to check disable exploit
-Install titanium Pro from market and backup (first select backup location to Ext sd card)
- Once finish, uninstall titanium and unroot device from exynose app
You can also factory reset and send to service centre.
Click to expand...
Click to collapse
Yeah, that's all I did. Rooted, installed Titanium and backed-up my data to the external SD card. I've un-rooted the device, all I need to do now is factory reset.
Thanks for your help, much appreciated.
-svdkillswitch

but adb doesnt work

[Q] Cannot save attachments

Hello,
I'm currently running the 4.4 rooted deodexed stock Rom downloaded from the developers section. It worked fine for about a month after I installed it (using the recommended recovery, full wipe etc.), and then I ran into the 'process.android.acore stopped' process which rendered the phone unusable. Based on what I read online it seems that the only option was to perform a factory reset which is what I did.
Since that point, any application that needs to download (or upload) files, has been unable to do so. I first noticed it in WhatsApp where the images send to me showed up blurred and when I clicked and tried to download them I would get an error that the download failed. Sending an image would generate an error as well. Looking further I noticed that none of my email apps (outlook.com, Touchdown, Xfinity etc.) is able to download any attachments either.
I tried to wipe and reinstall the Rom, as well as formatting the SD Card and internal memory, but when I reinstall the apps I mentioned or restore them using Titanium I get the same behavior. The errors do not indicate what hte root cause is, but I assume it has something to do with storage on the phone being corrupted somehow.
Any suggestions on how this might be resolved would be appreciated.

Resolved by upgrading to the N1 ROM.

Is it possible to clone Fire TV's with ClockWorkMod?

Is it possible to clone Fire TV's with ClockWorkMod?
I have to set up a bunch of Fire TV's for family and it would be much easier to set one up, create a system image and then clone it onto another Fire TV.
Is this even possible?

yeah, that would be handy. Thread subscribed

Provided the nandroid backup/restore functions are working properly in CWM for this device; that should not be a problem.
The "clones" would need to be rooted have CWM. Probably should back up at least the first device you try this on (just in case the other backup from other device does not work) But either way as long as you don't overwrite recovery you can just reflash whatever rom you were running before trying
All you need to do is pull the images from nandroid backup made on device A and push them to devices B,C,D,etc. Then just do an advanced restore on the clones. Restore system, boot, and data.
Haven't got a spare AFTB to test with, but that's how it's been done on every other device since the first commercial android device to have a custom recovery back in 2008. Don't see any reason it would be any different for this one.
Amazon login might be a slight issue though. You will probably have to sign out before backing up, otherwise you will need to go to your amazon account and deregister all the devices you copied to.

gurnted said:
Provided the nandroid backup/restore functions are working properly in CWM for this device; that should not be a problem.
The "clones" would need to be rooted have CWM. Probably should back up at least the first device you try this on (just in case the other backup from other device does not work) But either way as long as you don't overwrite recovery you can just reflash whatever rom you were running before trying
All you need to do is pull the images from nandroid backup made on device A and push them to devices B,C,D,etc. Then just do an advanced restore on the clones. Restore system, boot, and data.
Haven't got a spare AFTB to test with, but that's how it's been done on every other device since the first commercial android device to have a custom recovery back in 2008. Don't see any reason it would be any different for this one.
Amazon login might be a slight issue though. You will probably have to sign out before backing up, otherwise you will need to go to your amazon account and deregister all the devices you copied to.
Click to expand...
Click to collapse
COrrecting my earlier post... this does actually work I just confirmed it however the amount of time it takes to do may actually be longer than manually sideloading all your apks again. Plus it does not backup data so your xbmc build will have to be reloaded after doing this.

You can nandroid it. You will have to unpair the remote from the one you copied and pair its remote. That was the only issue I ran into.
You can also copy over the data directories.

designgears said:
You can nandroid it. You will have to unpair the remote from the one you copied and pair its remote. That was the only issue I ran into.
You can also copy over the data directories.
Click to expand...
Click to collapse
Can you copy over the rooted firmware etc? or does that need to be done before hand. Also how do you get it to copy the data directory? It didn't carry my xbmc files over when I did this.

danknasty said:
Can you copy over the rooted firmware etc? or does that need to be done before hand.
Click to expand...
Click to collapse
The second one needs to have Clockworkmod recovery installed, you need to root it first.
Setup everything the way you want it on the first one
Make a nandroid backup and copy it to your pc
Root and install clockworkmod recovery on your second, third, forth units (how ever many you have)
copy the nandroid files over to other units
restore the backup
re-pair the remotes

designgears said:
You can nandroid it. You will have to unpair the remote from the one you copied and pair its remote. That was the only issue I ran into.
You can also copy over the data directories.
Click to expand...
Click to collapse
Thanks, but what's Nandroid?

Neo3D said:
Thanks, but what's Nandroid?
Click to expand...
Click to collapse
a clockwordmod recovery backup

danknasty said:
COrrecting my earlier post... this does actually work I just confirmed it however the amount of time it takes to do may actually be longer than manually sideloading all your apks again. Plus it does not backup data so your xbmc build will have to be reloaded after doing this.
Click to expand...
Click to collapse
Wait, so when you did a full image backup, it didn't image the apps + apps data? I thought that's what a full system image meant? Like, when you do a full system image of Windows 8, it restores your whole system.

designgears said:
The second one needs to have Clockworkmod recovery installed, you need to root it first.
Setup everything the way you want it on the first one
Make a nandroid backup and copy it to your pc
Root and install clockworkmod recovery on your second, third, forth units (how ever many you have)
copy the nandroid files over to other units
restore the backup
re-pair the remotes
Click to expand...
Click to collapse
What's the location of the backup files? Are there a lot of files to transfer over?

Neo3D said:
Wait, so when you did a full image backup, it didn't image the apps + apps data? I thought that's what a full system image meant? Like, when you do a full system image of Windows 8, it restores your whole system.
Click to expand...
Click to collapse
If you do a full backup it will get the data partition as well, which will have your apps+data.
Neo3D said:
What's the location of the backup files? Are there a lot of files to transfer over?
Click to expand...
Click to collapse
clockworkmod directory on the sdcard

Neo3D said:
Wait, so when you did a full image backup, it didn't image the apps + apps data? I thought that's what a full system image meant? Like, when you do a full system image of Windows 8, it restores your whole system.
Click to expand...
Click to collapse
When I did it it did not backup the data for xbmc only the app itself. I really don't have much else on my firetv that I use so i can't say if it transferred data for amazon approved apps. All it really did was restore all my apps sideloaded apps etc... somethign I can probably do manually in about 10 minutes or so.

How to copy the system 1:1 to a new device by using TWRP

I got a new device by RMA and now I want to copy my nandroid backup made with TWRP to the new one.
Which partitions do I have to copy?

Most of the partitions are system based, so don't touch them. All you would want to copy is data, but I am not even sure that would work, without a boot loop? I keep all my data backed up with Titanium. And Google drive would restore most of what you had on your phone as long as you were allowing setting>system>backup.

Sui77 said:
I got a new device by RMA and now I want to copy my nandroid backup made with TWRP to the new one.
Which partitions do I have to copy?
Click to expand...
Click to collapse
Data, as it is the one where your settings and app updates are stored. Just be sure the new device is running the same version of Android as the old.
Droid_Nut said:
Most of the partitions are system based, so don't touch them. All you would want to copy is data, but I am not even sure that would work, without a boot loop? I keep all my data backed up with Titanium. And Google drive would restore most of what you had on your phone as long as you were allowing setting>system>backup.
Click to expand...
Click to collapse
Restoring a nandroid backup of the data partition to another, identical, device will work without causing a bootloop given the precautions I describe above. Do note however that Google's backup only restores items acquired through the Play Store. Alternative app stores such as Amazon will not be restored, apps acquired through Amazon will not be restored, and any apps sideloaded will not be restored. Since Google's restore function doesn't restore everything, any backup solution - like a nandroid backup - is going to be a better alternative.

Strephon Alkhalikoi said:
Data, as it is the one where your settings and app updates are stored. Just be sure the new device is running the same version of Android as the old.
Restoring a nandroid backup of the data partition to another, identical, device will work without causing a bootloop given the precautions I describe above. Do note however that Google's backup only restores items acquired through the Play Store. Alternative app stores such as Amazon will not be restored, apps acquired through Amazon will not be restored, and any apps sideloaded will not be restored. Since Google's restore function doesn't restore everything, any backup solution - like a nandroid backup - is going to be a better alternative.
Click to expand...
Click to collapse
Thanks for the clarification that you can restore data as long as you are on the same version, does it have to be at the same security update level as well?
That is why I use Titanium for apps I got off of Fdroid and other sources. I will make sure I try the Nandroid data backup next time.

Security level shouldn't make a difference, but that is not something I have attempted. The pair of identical tablets I have here are running the same security update.

Thanks, data did the trick.
I had to delete 2 files due to a non working finger printer by using TWRP files explorer, but now the phone is fine.
Last thing pending are customer ringtones, but this is a nasty one.
Any idea how to do it?

Sui77 said:
Thanks, data did the trick.
I had to delete 2 files due to a non working finger printer by using TWRP files explorer, but now the phone is fine.
Last thing pending are customer ringtones, but this is a nasty one.
Any idea how to do it?
Click to expand...
Click to collapse
I am having the same problem with the fingerprint reader after restoring data from one phone to another, what files did you delete in TWRP file manager?

Solution for fingerprinter:
1. Boot into TWRP
2. Go to advanced>filemanager to acces the files in your phone.
3. Enter the folder /data/system/user/0
4. Delete following files: ./fpdata/user.db, settings_fingerprint.xml
5. Reboot to system and set up new fingerprints with the fingerprint wizard
6. Everything should work normal
Was not easy to find, but it's easy to do

Sui77 said:
Solution for fingerprinter:
1. Boot into TWRP
2. Go to advanced>filemanager to acces the files in your phone.
3. Enter the folder /data/system/user/0
4. Delete following files: ./fpdata/user.db, settings_fingerprint.xml
5. Reboot to system and set up new fingerprints with the fingerprint wizard
6. Everything should work normal
Was not easy to find, but it's easy to do
Click to expand...
Click to collapse
I didn't think it would be easy to find, but thanks for the tips. :good:

I am just putting this phone online with Q Beta 3 today, I have no notifications for text, and all options are greyed out?

Droid_Nut said:
I am just putting this phone online with Q Beta 3 today, I have no notifications for text, and all options are greyed out?
Click to expand...
Click to collapse
Turns out this is a bug in Android Q. With Pie there were some many notifications that I set my sound to none, so I just set my sound to Gibbon Call, and now I get text notifications. :good: