Develop Bugs

HTC Restore Problem

Hi guys
I recently factory restored my HTC Desire and the built-in backup prompted me to restore my settings, which I did, but for some reason my SMS messages were not restored.
I checked the SD card, and there is a backup there, but of course the files are encrypted. Is there any way to read these files, or to restore my messaging SMS?
Thanks in advance!

Am I right in saying that the backups's hashes are salted with the device serial #? If that's the case then decryption should be quite possible.

I have had the exact same problem today. Had to return my Desire as it was faulty for a straight swap (kept the same SIM and SD card). The SD card has restored all contacts and music, but SMS messages have not transferred over. I've looked at every possible option in the settings but can't seem to see how to do this.
I'd be grateful for any advice or info. Thankyou.

slightly old thread, but relevant to my problem....
have been playing around a lot with my desire over the past week, and managed to delete the wrong nandroid backup and lost all my sms. I have a sense auto backup form a day or so earlier, but cannot for the life of me get the phone to read these - there's no option to restore just backup.
So, tried factory reset from recovery, copied the 'old' backup to the sd, and booted. Nothing was restored. Have tried all sorts of combos to try and get the backup to be read, but no joy at all. Even completely wiping everything, flashing the original rom i was using (modaco 3.1) and restarting, but still sense doesnt see the backup.
I definitley remember it doing it once during all the crazy rom swopping of the last few days, and the sms, wifi key etc all restored, but I can't get it to do it again.
Any ideas about 'forcing' the restore? I know that the backup is handset specific (tied to the serial/imei?) but it should restore on any rom using sense yeh?
all help greatly appreciated
ta.
another small thought, there may be an app idea in here for anyone thats interested - reading the sense backup and applying it by force? i know quite a few people tend to backup their sd card regularly, so it could be useful as a last resort option.

I guess there's not much I can help you but to avoid this problem in the future you might want to use SMS backup (by Cristoph Studer, there are 2 others on the Market with the same name) - backs up your sms's to your Gmail account, works great. I love the Cloud!

I have used sms backup in the past, didn't bother this time as i had the nandroid backup. Kicking myself as I'm usually pretty careful about what files i'm getting rid of, and have got all my sms for about the last ten yrs (minus the 2 months i just lost) for blackmail purposes time to crank the delete button paranoia up a notch again
edit: solved tok everything off the sd card, made sure i had the backup set from the date range i wanted, wiped absolutely everything from recovery, reflashed the rom i was running when the backup was taken & rebooted. the backup was picked up fine, all settings, sms etc back with no problems.
the small trick to getting this to occur seems to be just let the phone sit for a minute when it reboots - i assume that if you go into the setup wizard before the sd card is correctly moutned and read that you bypass the restore. i had done the same procedure to try to get it to restore before and it didn't, the pause to allow the sd card to be read was the only thing i did differently.

I'm having the same issue, I want to restore a back-up from my SD card, but cannot see any way to do it. I've tried a factory reset, but still no luck.
Can a restore be forced? The 2.2 upgrade seems to have removed Settings>Privacy

Same problem here, Froyo won't restore my backup.
I tried to downgrade to Eclair, but the installation failed with "Error 140: wrong bootloader version".
I guess my backup is pretty useless now...

Frojo wont restore settings after hardreset
I asked HTC about this, and here's the answer:
Thanks for your question regarding backup of your device. The former feature backup to SD card is missing in this newer version. This is due to Google, which has developed backup feature in the software, changed the system in 2.2, then back out to their servers instead. This applies to the Google devices, such as NexusOne. When your device is the HTC brand, we have some backup features as before. However, you can take backup in the following way (as with older versions of Android): Contacts: You can save contacts via Outlook when they are created as telephone contacts. For this you need HTC Sync and Outlook on your computer. HTC Sync, see your device's SD card. To open the map, select Mount in the device, your device is displayed on the computer as an external disk drive. Then you find the program through your computer's Windows Explorer, and also integrates it on your computer. You can now sync. You can also download HTC Sync from our website under Support tab. If you use Google contacts they can be retrieved back when you set up your email again. If you have configured an Exchange server, you can also download contacts onto the device again. Calendar appointments: These are transferred in the same manner as contacts. Emails: These can be synchronized over again through your Exchange server, or if you have Google mail. Data files: These can be transmitted via computer Explorer when you select Mount as previously described. You can then transfer your files to a folder on your computer. SMS and MMS: Those you can not backup.
Blueyed1

Way to go HTC.... hurray
The more I learn about Google and HTC's way of handling my data I get more determined to Root my phone to get full access of my phone, and to control what data and in what way that data is transferred to either google or HTC.
When you compare to the way Apple is controlling it's sheep herd, Google is not any better when it comes to data gathering and data sniping.

Blueyed1 said:
SMS and MMS: Those you can not backup.
Click to expand...
Click to collapse
WTF????????????????????????????

DRMON said:
WTF????????????????????????????
Click to expand...
Click to collapse
Backup not possible with previeus build in backup, that is..

[Q] Recovery not restoring data

hi, i need help restoring my backup in cwm 3.0.2.8.
The system partition restores fine but none of my apps or anything get restored. I've tried different versions of cwm and none of them have worked. I know i can just restore my apps with my backup or titanium but i shouldnt have to and i forgot to before i made the backup.
It doesnt even restore any if my contacts, texts, etc. It seems like its just restoring the rom with what ever mods and tweaks i had applied. This has happened with multiple roms so i reckon its a fault with cwm. Also when restoring just the data in cwm it doesnt say "Restore complete!"
Anybody got any suggestions?

Anybody got any suggestions?

How are you restoring your ROMs?
Your contacts should be backed up with your Google account.

They are backed up but cwm should restore everything. After i restore it asks me to login to my google account, select my time-zone, etc.
Im restoring from recovery.
It seems like cwm is crashing while restoring my data partition because the screen goes black whilst still showing the rom manager icon and it goes back to the inital screen of recovery like i just booted into it.

Have you checked your SDcard for errors?
There are hundreds of people who use ClockworkMod Recovery without issue. (excusing 3.0.2.5)
Could be something as simple as a couple of bad sectors on your card.

I recently formatted it before i made the backup, how would i check for any more errors?

Try HERE. Its in Russian. So you'd need to visit via Google or use Chrome.

I downloaded but i dont have a clue how to use it

Read through the manual.

Or you could follow this guide HERE, I'm pretty certain that the first tool would be more accurate.

I tried the russian one but i got access denied so im doing the windows method. If none of this works, is there a way to manually extract the files from the .img file? I mainly want the data from my apps because i hav around 300

How are you connecting your SDcard to your computer? I just ran a test using ,
Code:
flashnul G: -T
It worked fine, that was connected via USB cable with the card mounted as a drive.
No problems which I'm pretty pleased with, now just to transfer my data back.

I forgot to run CMD as admin, its running now
EDIT: I didnt get any errors

If the SDcard is fine. Then I'd reflash CWM Recovery.

I have. The only reason I flashed .2.8 was because of this problem. I have to send my phone to HTC on monday for repair so when I get I back (20 days later) Il start again from fresh. For now I'm gonna unroot and s-on etc etc... I hate sense.
Thanks a million for your help though!
Question: If HTC swap my phone with another, will my backup still work with the new one?

Off topic, I point blank refused to wait 21 days + for a repair. After some wrangling got an exchange. Sadly the exchange handset had severe case misalignment issues. Refused that also.
Yes your backup will still work. It doesn't matter what handset you use. The backup isn't tied to it.

Haha the speaker for calls doesn't work anymore so i hav to send it back. 20 days is gnna seem like forever lol. I'm gnna hav to look for my Nokia 3310. It's like 10 years old and its never failed me once.
As for my back up, when I do get my phone back i need to go through my apps and delete what I don't want.....or I could buy a bigger mem card and setup A2SD. Is there no way to browse inside the data.img file from the backup?

[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

Cannot access internal storage to make a backup

Hi guys,
After a long break of messing with my phone, I decided to try to root my Sprint Samsung Galaxy S III again. My apologies in advance for this wall of a post.
I'm on Android 4.4.2 on a stock ROM. I do not have an SD card so I am purely using the 16GB internal memory.
Backed up all of my stuff using MyBackup Pro (oh, the regret...), then copied the backed up files - the .zip (Data_2014_12_13.zip) containing all of the personal data like texts, MMS, call log, etc. as well as the folder (AppsMedia_2014_12_14) containing all of my apps, music, videos, and photos - to my PC as I planned on wiping the phone and doing a factory reset.
Followed a video on YouTube to root (the Get High on Android guy that runs galaxys3root.com) and had problems with it, so I followed another one that addressed the issue I was having. Used Odin3 v1.85, "CF-Auto-Root-d2spr-d2spr-sphl710.tar.md5", "openrecovery-twrp-2.7.1.0-d2spr.tar", and "UPDATE-SuperSU-v2.13.zip" to root and it went off without a hitch. Wiped the phone and did a factory reset at this point. Verified root using Root Checker and Titanium Backup and both verified I was rooted. Tried out a bunch of different apps and all showed root access.
Downloaded MyBackup Pro again to try to restore everything. It requests SU permissions and I grant them. Transferred the old backup files over to the phone again and placed them in the correct directory, but MBP isn't recognizing them and doesn't see any backups of data or apps/pics/etc. So I create a backup of the one text I have on the phone and backup one app just to verify everything was in the correct folder and it was. MBP recognized the backup I had just created. Tried to move apps from the old backup folder into the new one next to the one I had just backed up and MBP didn't see it was there. Did the same thing with transferring the picture folder and still nothing.
Decided to do yet another wipe at this point. Problem is, now when I use MBP or Titanium Backup to try to make backups, it shows the directories as inaccessible. In MBP, I get
MBP said:
Error during Backup: unknown error (code 14): Could not open database
Click to expand...
Click to collapse
If I go into the options, the default local storage location is "/storage/emulated/0". If I try to change it to anything else or even leave it as is and hit "Select directory", it gives me an error stating:
MBP said:
Could not write to the path selected.
Note: ONLY Andorid 4.4 (KitKat) removes the ability to access the SD card, Android 5+ has added support again. if you are using Android 4.4 the only way to access the SD card is 1-Root your phone, 2-Install SDFix app from the market.
Android 5+ users, the dialog to select the path does not show the SD card by default, you need to "Unhide SD card" from the dialog's Menu.
Click to expand...
Click to collapse
At this point, I downloaded NextApp SDFix hoping it would somehow affect internal memory even though it's for SD cards, but no dice.
I load up Titanium Backup. "Root access" has a green check mark and tapping it shows I have BusyBox 1.19.4-Titanium from app and YES for SQLite with SQLite 3.7.6.3-Titanium included.
However, "Backup directory" has a red X and says not available. Trying to press the note with check mark at the top right of TiBu yields the error:
TiBu said:
The current backup location ("storage/emulated/legacy/TitaniumBackup") cannot be accessed.
Click to expand...
Click to collapse
When trying to change the backup location, every folder shows a red folder at the top saying "This folder is not writable."
Does anyone have any idea what to do here? I've tried searching and it looks like people have been either having similar problems that worked themselves out by just rebooting (tried it many, many times), reinstalling the backup apps (also tried many times), wiping the phone (did full wipes and factory resets through TWRP), or they were actually talking about external storage (I'm on internal).
All I really care about are getting my texts and pictures back at this point. Unfortunately MBP stores pictures and videos as its own special format and I can't open them on my computer. Same with texts. Can anyone give me any kind of guidance here please?

NextName said:
Hi guys,
After a long break of messing with my phone, I decided to try to root my Sprint Samsung Galaxy S III again. My apologies in advance for this wall of a post.
I'm on Android 4.4.2 on a stock ROM. I do not have an SD card so I am purely using the 16GB internal memory.
Backed up all of my stuff using MyBackup Pro (oh, the regret...), then copied the backed up files - the .zip (Data_2014_12_13.zip) containing all of the personal data like texts, MMS, call log, etc. as well as the folder (AppsMedia_2014_12_14) containing all of my apps, music, videos, and photos - to my PC as I planned on wiping the phone and doing a factory reset.
Followed a video on YouTube to root (the Get High on Android guy that runs galaxys3root.com) and had problems with it, so I followed another one that addressed the issue I was having. Used Odin3 v1.85, "CF-Auto-Root-d2spr-d2spr-sphl710.tar.md5", "openrecovery-twrp-2.7.1.0-d2spr.tar", and "UPDATE-SuperSU-v2.13.zip" to root and it went off without a hitch. Wiped the phone and did a factory reset at this point. Verified root using Root Checker and Titanium Backup and both verified I was rooted. Tried out a bunch of different apps and all showed root access.
Downloaded MyBackup Pro again to try to restore everything. It requests SU permissions and I grant them. Transferred the old backup files over to the phone again and placed them in the correct directory, but MBP isn't recognizing them and doesn't see any backups of data or apps/pics/etc. So I create a backup of the one text I have on the phone and backup one app just to verify everything was in the correct folder and it was. MBP recognized the backup I had just created. Tried to move apps from the old backup folder into the new one next to the one I had just backed up and MBP didn't see it was there. Did the same thing with transferring the picture folder and still nothing.
Decided to do yet another wipe at this point. Problem is, now when I use MBP or Titanium Backup to try to make backups, it shows the directories as inaccessible. In MBP, I get
If I go into the options, the default local storage location is "/storage/emulated/0". If I try to change it to anything else or even leave it as is and hit "Select directory", it gives me an error stating:
At this point, I downloaded NextApp SDFix hoping it would somehow affect internal memory even though it's for SD cards, but no dice.
I load up Titanium Backup. "Root access" has a green check mark and tapping it shows I have BusyBox 1.19.4-Titanium from app and YES for SQLite with SQLite 3.7.6.3-Titanium included.
However, "Backup directory" has a red X and says not available. Trying to press the note with check mark at the top right of TiBu yields the error:
When trying to change the backup location, every folder shows a red folder at the top saying "This folder is not writable."
Does anyone have any idea what to do here? I've tried searching and it looks like people have been either having similar problems that worked themselves out by just rebooting (tried it many, many times), reinstalling the backup apps (also tried many times), wiping the phone (did full wipes and factory resets through TWRP), or they were actually talking about external storage (I'm on internal).
All I really care about are getting my texts and pictures back at this point. Unfortunately MBP stores pictures and videos as its own special format and I can't open them on my computer. Same with texts. Can anyone give me any kind of guidance here please?
Click to expand...
Click to collapse
well...if you back up everything with your Google account you just have to log back in after you Odin the stock firmware again....the only things Google won't backup are app data and phone calls/text messages but all your apps and contacts will restore.....i never use TB or any other backup app just the standard Google backup

6th_Hokage said:
well...if you back up everything with your Google account you just have to log back in after you Odin the stock firmware again....the only things Google won't backup are app data and phone calls/text messages but all your apps and contacts will restore.....i never use TB or any other backup app just the standard Google backup
Click to expand...
Click to collapse
Yeah... as stated, the only thing I'm really worried about are texts, calls, pictures, etc. I don't care about the apps and I already have contacts and everything synced with my Google account.

NextName said:
Yeah... as stated, the only thing I'm really worried about are texts, calls, pictures, etc. I don't care about the apps and I already have contacts and everything synced with my Google account.
Click to expand...
Click to collapse
well picture's will also back up with Google....

6th_Hokage said:
well picture's will also back up with Google....
Click to expand...
Click to collapse
Stupidly forgot about Dropbox. Looks like all pictures are saved. Thank you for reminding me.
Texts are now still a large priority to get back. I have messages from a deceased family member and significant other I'd really like to hold onto and I feel like such an idiot for not backing up earlier. Some 40k texts I backed up when I tried to back up my stuff.
As a small, possibly insignificant update though...
Hooked the phone up to my computer and my computer still reads all of the files fine and I can still transfer files to and from perfectly. I tried setting up the MBP folders again and adding the data backup in to see if it would allow me to restore that backup.
MBP recognized the data backup (the single .zip file containing all texts and data) but wouldn't let me view the contents or restore them. Instead, I get:
MBP said:
I/O error: Unable to write to SD Card. Make sure the SD Card is inserted properly, is not connected to your PC, and is not full.
Click to expand...
Click to collapse
The phone is neither connected to my PC nor even close to full (11GB of free space remaining) and I don't have an SD card at all and I'm not trying to write to it (at least not intentionally).
Edit: For poops and giggles, I'm going to try out the Wicked X 8 ROM. Already verified I'm on the ND8 bootloader and the download just finished so I'll try that.

Well, it's fixed now, I guess.
For poops and giggles I decided to try out Wicked X 8 and, after quite a bit of extra time spent because I'm an idiot and wiped the entire internal storage prior to flashing the ROM and requiring a sideload, I finally got the new ROM up and running.
I was very delighted to see when I started it up that Titanium could access the directory, as could MBP, and I'm currently going through a full restore right now. Has to restore around 40,000 texts so that'll take a while, but it appears to be going smoothly.

NextName said:
Well, it's fixed now, I guess.
For poops and giggles I decided to try out Wicked X 8 and, after quite a bit of extra time spent because I'm an idiot and wiped the entire internal storage prior to flashing the ROM and requiring a sideload, I finally got the new ROM up and running.
I was very delighted to see when I started it up that Titanium could access the directory, as could MBP, and I'm currently going through a full restore right now. Has to restore around 40,000 texts so that'll take a while, but it appears to be going smoothly.
Click to expand...
Click to collapse
nice wicked x is a great rom too

40,000 texts to restore? What? Wow.

Best way to backup data before rooting

Hi guys! What is the best way to backup as much data as possible before rooting? I'm coming from an iPhone but prior to it I was on Android so I'm a little rusty. I'm aware of TiBu backups but if I recall correctly you need root to get a full backup. What I'm doing now is backing up everything through Google Drive backups and Google Photos. Is there an app that can maybe batch backup/restore apks along with their data without root? I'd like to keep as much data as possible like app data and MMS before I wipe and root.
One more thing, I'm currently on the 8.1 official firmware but came from the DP2 OTA. If I were to unenroll from the beta program, will it force a wipe? I know it forces a wipe when unenrolling and going down to the 8.0 firmware but since it's on the same version of Android, will it still require a wipe?
Thanks in advance for any help.

I hope someone has a better one. But one that is clunky but works without root is Helium by clockworkmod. Need a PC since you run a program on the PC as part of the process. Not all apps will backup with it, but it does lots of apps. I can pretty much do all the apps I need to do that aren't already backed up by Google backup. Most of the apps that won't allow backup will be financial ones and others that you just log back into your account, and you're back in business that way.
You download the Helium app from the playstore. When you run the app, it'll tell you to connect to a PC. And it'll show you a link to download a program for the PC. The program on the PC is what allows the app on the phone to do backups. I don't know if ADB or Android tools have to also be installed, but I think it stands alone. You have to run the PC program every time to do backups. After the first time, you just start the program, plug the phone to the PC and start the app, or any change in order of those steps you want.
The clunky part for me is the password. You have to set a password for the phone since the app can't access the data without the password. So it can't be a pattern lock or pin.
That's no big deals since you only need to do this when backing up so can just temporarily change it, and is not the clunky part.
Here's the clunky part. When you go to backup, It makes no difference whether you've saved the password or not. When you get to the password field It'll autofill the password (with any characters saved or not) in addition to anything you started filling and the start backing up. Then may finally say backup failed. If you wait enough time it will not auto enter stuff, then you can manually enter the password. And it'll backup just fine. But it will show a prompt that the device is protected so enter the password. So you enter it all over again. Except this time it has some data to autofill in. So if you want to select another app to backup, it'll seem to backup better. Except it often will give an error.
For me, the best approach seems to be don't save the password in the app. Wait for a few seconds to make sure it isn't going to try to auto-enter. Manually enter the password. When it prompts the second time, just cancel instead of entering anything.
And after I just typed all that, I kept getting backup failed trying to do a backup. I finally managed to do it, but it is like that every time I try. some days it just works first time. Some days it takes trying different things. Once it a while it is better to save the password.
Anyway, the backups are good. Oh, after you've selected the apps/data to backup. Go to the bottom and kinda pull up below the green line and it'll show a check box to just save the data and not the app apk if you want a smaller size backup. I think it is faster just saving the app with it if you are moving or backing up to restore. Otherwise you have to wait for the download and install from the playstore.
The backups end up in their own folder in a folder named Carbon.

lacaprjc said:
Hi guys! What is the best way to backup as much data as possible before rooting? I'm coming from an iPhone but prior to it I was on Android so I'm a little rusty. I'm aware of TiBu backups but if I recall correctly you need root to get a full backup. What I'm doing now is backing up everything through Google Drive backups and Google Photos. Is there an app that can maybe batch backup/restore apks along with their data without root? I'd like to keep as much data as possible like app data and MMS before I wipe and root.
One more thing, I'm currently on the 8.1 official firmware but came from the DP2 OTA. If I were to unenroll from the beta program, will it force a wipe? I know it forces a wipe when unenrolling and going down to the 8.0 firmware but since it's on the same version of Android, will it still require a wipe?
Thanks in advance for any help.
Click to expand...
Click to collapse
learn: adb backup
when unenrolling from the beta, and you are already on current stable, it will not wipe, nor update.

Voicebox said:
I hope someone has a better one. But one that is clunky but works without root is Helium by clockworkmod. Need a PC since you run a program on the PC as part of the process. Not all apps will backup with it, but it does lots of apps. I can pretty much do all the apps I need to do that aren't already backed up by Google backup. Most of the apps that won't allow backup will be financial ones and others that you just log back into your account, and you're back in business that way.
You download the Helium app from the playstore. When you run the app, it'll tell you to connect to a PC. And it'll show you a link to download a program for the PC. The program on the PC is what allows the app on the phone to do backups. I don't know if ADB or Android tools have to also be installed, but I think it stands alone. You have to run the PC program every time to do backups. After the first time, you just start the program, plug the phone to the PC and start the app, or any change in order of those steps you want.
The clunky part for me is the password. You have to set a password for the phone since the app can't access the data without the password. So it can't be a pattern lock or pin.
That's no big deals since you only need to do this when backing up so can just temporarily change it, and is not the clunky part.
Here's the clunky part. When you go to backup, It makes no difference whether you've saved the password or not. When you get to the password field It'll autofill the password (with any characters saved or not) in addition to anything you started filling and the start backing up. Then may finally say backup failed. If you wait enough time it will not auto enter stuff, then you can manually enter the password. And it'll backup just fine. But it will show a prompt that the device is protected so enter the password. So you enter it all over again. Except this time it has some data to autofill in. So if you want to select another app to backup, it'll seem to backup better. Except it often will give an error.
For me, the best approach seems to be don't save the password in the app. Wait for a few seconds to make sure it isn't going to try to auto-enter. Manually enter the password. When it prompts the second time, just cancel instead of entering anything.
And after I just typed all that, I kept getting backup failed trying to do a backup. I finally managed to do it, but it is like that every time I try. some days it just works first time. Some days it takes trying different things. Once it a while it is better to save the password.
Anyway, the backups are good. Oh, after you've selected the apps/data to backup. Go to the bottom and kinda pull up below the green line and it'll show a check box to just save the data and not the app apk if you want a smaller size backup. I think it is faster just saving the app with it if you are moving or backing up to restore. Otherwise you have to wait for the download and install from the playstore.
The backups end up in their own folder in a folder named Carbon.
Click to expand...
Click to collapse
Thanks for the help! I'm gonna try this method now and let you know if all is well.

lacaprjc said:
Hi guys! What is the best way to backup as much data as possible before rooting?
Click to expand...
Click to collapse
Sounds like you've done all you can... except for unlocking the phone as soon as you got it. Just make sure you use both separate unlock commands and get unlock and unlock_critical done properly. I think you'll find the phone will be pretty much back where you left it. Just get on with it ffs! Not a big deal.