Hello:
I was stuck at JB .30 without root - so I used "adb backup" to copy my apps + data before downgrading to ICS and rooting. Now, thanks to buhohitr, I'm back to JB .30 with root; however, the restore from .ab isn't going so good.
I have a big back up file (about 4GB). The backup went smoothly and officially ended with Backup Finished. Again, before I wiped the tablet with a downgrade. I've tried a couple things and neither seem to get the restore to go through.
1) Titanium Backup. TB did load the .ab file and showed all the apps that were backed up. I can pick through the one's I actually want. But once I start the backup it hangs on the first or second app being restore.
2) Using "adb restore", basically the same thing happens. I run the restore and the tablet asks for permission to continue. I say "Restore" and then it hangs on the first or second app. It's been sitting there for 15 minutes now (i.e., alarm clock app). It really shouldn't be taking this long.
I've tried and tried again several times with both methods. One other thing to mention is that I didn't use a password when backing up. I know other programs want this - but I don't see how it's a problem. Again, I can see all the apps in TB and also "adb restore" actually does get one or two things done before it freezes.
Any help would be appreciated.
Cheers.
-lukin- said:
Hello:
I was stuck at JB .30 without root - so I used "adb backup" to copy my apps + data before downgrading to ICS and rooting. Now, thanks to buhohitr, I'm back to JB .30 with root; however, the restore from .ab isn't going so good.
I have a big back up file (about 4GB). The backup went smoothly and officially ended with Backup Finished. Again, before I wiped the tablet with a downgrade. I've tried a couple things and neither seem to get the restore to go through.
1) Titanium Backup. TB did load the .ab file and showed all the apps that were backed up. I can pick through the one's I actually want. But once I start the backup it hangs on the first or second app being restore.
2) Using "adb restore", basically the same thing happens. I run the restore and the tablet asks for permission to continue. I say "Restore" and then it hangs on the first or second app. It's been sitting there for 15 minutes now (i.e., alarm clock app). It really shouldn't be taking this long.
I've tried and tried again several times with both methods. One other thing to mention is that I didn't use a password when backing up. I know other programs want this - but I don't see how it's a problem. Again, I can see all the apps in TB and also "adb restore" actually does get one or two things done before it freezes.
Any help would be appreciated.
Cheers.
Click to expand...
Click to collapse
I confused, you stated you're on JB .30 before backup and downgrade? (typo with .30, since ICS is .30).
buhohitr said:
I confused, you stated you're on JB .30 before backup and downgrade? (typo with .30, since ICS is .30).
Click to expand...
Click to collapse
Hello:
Sorry for the hiatus. I RMA'd my TF700 for repair and they finally sent back a new replacement unit. Truthfully, I'm starting to get tired of ASUS's sub-par customer service.
Anyways, now I've got a new unit back a the latest JB and need to downgrade to ICS and then use ADB restore to bring everything back again. I think 'll be okay doing the downgrade using the dlpkgfile method.
I tried to do the ADB restore before RMAing and was having difficulty (see OP). What is the right time to do the ADB restore? Or best practices with doing it? Has anyone had success with Titanium Backup and ad file? My backup file is 3.81 GB big.
Thanks for you time.
-lukin- said:
Hello:
Sorry for the hiatus. I RMA'd my TF700 for repair and they finally sent back a new replacement unit. Truthfully, I'm starting to get tired of ASUS's sub-par customer service.
Anyways, now I've got a new unit back a the latest JB and need to downgrade to ICS and then use ADB restore to bring everything back again. I think 'll be okay doing the downgrade using the dlpkgfile method.
I tried to do the ADB restore before RMAing and was having difficulty (see OP). What is the right time to do the ADB restore? Or best practices with doing it? Has anyone had success with Titanium Backup and ad file? My backup file is 3.81 GB big.
Thanks for you time.
Click to expand...
Click to collapse
I strongly suspect that adb backup doesn't work for transformers. At least up to now, nobody has been able to convince me otherwise in this thread: http://forum.xda-developers.com/showthread.php?t=2176169
What you could try is to extract the files from the backup file (https://github.com/nelenkov/android-backup-extractor), then manually copy relevant files to your transformer, which will definitely need root. However, when I carry out "adb backup -all -shared", no app data is stored. Only when I specifically list apps for adb to backup, some of their data is backuped (which then might be restored by Titanium or manually).
sharkcow
Related
I'm having some trouble restoring backups. I recently reflashed my phone. All backups were verified. I have used the help button and redownloaded busybox. I have rooted my phone and given root privileges to TiB. I have usb debugging mode enabled too. When I batch restore, the batch completes as if there wasn't a problem, but none of the apps are installed. I thought that there might be something wrong with the backups even though they passed verification so I moved them off of the sd card. I downloaded some random apps from the market and backed them up. They won't restore either. Same error. I tried restoring my phone to stock and going through the same steps and I have the same problem. I've used TiB for awhile now and haven't had any problems up until now. Does anyone have any ideas?
happened to me once.
reinstall from the matket of TIBU fixxed everything.
The first debloat guide posted for the captivate falsely stated that TiB restored the app
When I was attempting to revert to stock firmware for the recent OTA I discovered that TiB only saves the app's state and not the app itself
I think all of the original APKs are listed on the cognition download page
I got it fixed. I tried reinstalling TiB from the market. It didn't work. I was trying 3rd party apps. Not ones cooked into the rom. I ended up having to do a master clear with odin. It's kind of a brute force method, but at least its working again.
matthewpapa said:
The first debloat guide posted for the captivate falsely stated that TiB restored the app
When I was attempting to revert to stock firmware for the recent OTA I discovered that TiB only saves the app's state and not the app itself
I think all of the original APKs are listed on the cognition download page
Click to expand...
Click to collapse
Back when the pimp my captivate was written, TB was not able to restore what it backed up. It does now. I reverted back to stock after the OTA update and since I was in the "try to break my phone mood" I went ahead and did the Cognition 2.1.6. Right before I started messing with the phone, I backed up everything and anything that TB would allow me to, did a nandroid as well. WHen the time to restore came, everything I had before is right back where it was before I started. Albeit reading all the oops, TB can't restore jack, yadda yadda I wasn't too worried.
I have the same problem. I recently flashed to froyo 2.2 and the TiB won't let me do the restore...I tried to redone the OneClick Rom but It didn't work on 2.2 so I still need help here.
hale88 said:
I have the same problem. I recently flashed to froyo 2.2 and the TiB won't let me do the restore...I tried to redone the OneClick Rom but It didn't work on 2.2 so I still need help here.
Click to expand...
Click to collapse
TiBu has issues trying to restore apps going from 2.1 to 2.2.
CB650 Wolf said:
TiBu has issues trying to restore apps going from 2.1 to 2.2.
Click to expand...
Click to collapse
As far as I know, u can restore apps within the same "version", not between versions. You can restore the apps, but data can't be guaranteed.
Hello!
Some days ago, I've seen here that with ICS we can do a full backup without root, and the backup is saved on a computer. Yes, I know MyBackup and Titanium backup, but I want to try this.
So, I've tried this way, and it seem that all is fine... But 2 hours later from starting the process, my Sensation restarts... I've cheched the generated file size and it's 3'63GB.
The question is, has finished the backup correctly and, by some reason it restarts the phone, or the backup has failed?
Someone had this issue?
I don't want to trying flashing another ROM, and, when I will try to restore the data, ADB says me that the file is corrupt, or, directly, erase my data if I try now...
I've a free-operator Spanish Sensation, S-OFF and stock ICS ROM (3.32.401.1), but rooted.
Thanks for reading, even considering my English
Ok, I understand that anybody has this problem!
First off, I am unfamiliar with any ADB terms used on these forums.
What I did:
I rooted my Tab 2 (GT-P5113) using Odin and everythng worked out fine. Then I wanted to install a custom rom so I used Titanium Backup to back up my information. The directory com.titaniumbackup was on my SD card, but contained no files. I would think it may have cancelled the backup without me knowing.
I then did a NANDroid backup but I have no idea what happened to it. I then downloaded and succesfully installed CleanRom, but now I realized rooting isn't really what I thought, and is much more complicated, so I removed the cleanrom.zip from my SD. The CleanRom however is still on my system.
Is there ANY type of factory reset that will give me how my tablet was before? Unrooted?
atmon said:
I then did a NANDroid backup but I have no idea what happened to it. I then downloaded and succesfully installed CleanRom, but now I realized rooting isn't really what I thought, and is much more complicated, so I removed the cleanrom.zip from my SD. The CleanRom however is still on my system.
Is there ANY type of factory reset that will give me how my tablet was before? Unrooted?
Click to expand...
Click to collapse
If you go back to the backup/restore section where you made the backup and click on restore you should be able to restore your device with the backup it made. Unzipping the clean ROM should not have deleted the backup. The backup file will have the date you created it. From that point you should have the stock ROM. Then from there you can use Odin to unroot device by following the post in the development area of this forum.
Hope that helps - Let me know
Hey guys,
I've broken my Nexus 4, it felt out of my table and the front glass is cracked and the touchscreen unresponsive. However, I can see everything on it and can power the phone normally and such.
The phone is unlocked and rooted, running the stock Android 4.2.1.
I'll send the phone back to the repair center so they can give it a new screen and, obviously, wipe out the phone.
I've already used adb to copy my /sdcard into my computer, but I would like to backup everything that could make the process of using the phone after the repair less painful. I'm unable to run the adb backup utility since I can't unlock the phone as it requests.
I'm right now trying to copy /data into my computer. Is it of any use?
Is there anything else that I can backup before sending the phone out?
Ideally I would like to be able to, after getting the phone back, unlock it, maybe install the Paranoid Android ROM, root it, and then put back applications, settings, pictures, etc etc
Thanks in advance!
igorsantos07 said:
Hey guys,
I've broken my Nexus 4, it felt out of my table and the front glass is cracked and the touchscreen unresponsive. However, I can see everything on it and can power the phone normally and such.
The phone is unlocked and rooted, running the stock Android 4.2.1.
I'll send the phone back to the repair center so they can give it a new screen and, obviously, wipe out the phone.
I've already used adb to copy my /sdcard into my computer, but I would like to backup everything that could make the process of using the phone after the repair less painful. I'm unable to run the adb backup utility since I can't unlock the phone as it requests.
I'm right now trying to copy /data into my computer. Is it of any use?
Is there anything else that I can backup before sending the phone out?
Ideally I would like to be able to, after getting the phone back, unlock it, maybe install the Paranoid Android ROM, root it, and then put back applications, settings, pictures, etc etc
Thanks in advance!
Click to expand...
Click to collapse
since the phone itself still works, and the unresponsive screen is the only issue, you might be able to make a nandroid backup (complete backup of everything on phone-apps, settings, etc.)
I assume you probably have a touch based recovery on your phone like twrp or cwm touch. This is obviously an issue.
To counter this you could try using fastboot to flash clockworkmod non touch recovery. This allows you to use the volume rockers and power button to navigate.
To flash the recovery install all the correct drivers, and download the non touch cwm and place it your fastboot directory. Then boot the phone into the bootloader, and use this command:
Code:
fastboot flash recovery "name of recovery file.img"
Then from there you can boot into recovery, go to backup and restore, and finally make a nandroid backup. From there you could copy the backup using adb onto your computer. (the backups are stored in sdcard/clockworkmod/backups)
Thanks! I'll try that.
I think I tried before but it didn't work because I had little free space, and for some reason I gave up (thinking I was doing something wrong or going to try something else, I tried a lot of things during those days).
And then to restore that backup into the fixed phone I'll flash CWM again and use it's restore function, right?
Would there be any issue to install a custom mod (such as Paranoid Android) and then restoring this backup?
On a sidenote: on my Nexus 4 (without real sdcard) the clockworkmod folder is located at /mnt/shell/emulated/clockworkmod.
igorsantos07 said:
Thanks! I'll try that.
I think I tried before but it didn't work because I had little free space, and for some reason I gave up (thinking I was doing something wrong or going to try something else, I tried a lot of things during those days).
And then to restore that backup into the fixed phone I'll flash CWM again and use it's restore function, right?
Would there be any issue to install a custom mod (such as Paranoid Android) and then restoring this backup?
On a sidenote: on my Nexus 4 (without real sdcard) the clockworkmod folder is located at /mnt/shell/emulated/clockworkmod.
Click to expand...
Click to collapse
Yep once you get the phone fixed/replaced, you may need to reflash cwm and copy the backup back onto the phone (if they wiped it)
Then just use the restore option in cwm.
If you install paranoid android, then restore the backup, it will restore to whatever rom you had when you took the backup.
chromium96 said:
If you install paranoid android, then restore the backup, it will restore to whatever rom you had when you took the backup.
Click to expand...
Click to collapse
Boo =(
Ok, let me try another idea: I could get the phone back, restore it normally as we said with CWM, and then use TitaniumBackup to backup apps and settings, then save that to my computer, install Paranoid and then use TB to restore the useful stuff back into the new ROM?
I should just take care on not backing up system stuff, right?
igorsantos07 said:
Boo =(
Ok, let me try another idea: I could get the phone back, restore it normally as we said with CWM, and then use TitaniumBackup to backup apps and settings, then save that to my computer, install Paranoid and then use TB to restore the useful stuff back into the new ROM?
I should just take care on not backing up system stuff, right?
Click to expand...
Click to collapse
Yep thats probably your best bet. Although I would avoid backing up/restoring system stuff with TB as it causes lots of bugs.
Just use TB to backup apps+app data, and you can restore them after installing PA. There shouldnt be any problems
I had just downloaded the latest firmware to upgrade to lolipop, I did a titanium backup, then a nandroid with TWRP.
Upon reboot I can only get to the default recover screen (The one with the android on the skateboard). I can boot into TWRP and have tried clearing cache and delvik cache, and now doing a factory reset but I'm still having the problem. sometimes when rebooting from TWRP the phone boots to the lock screen (or to setup screen after factory reset), then a few seconds later reboots back to the screen with the android on the skateboard.
I haven't even started installing the new firmware, all I did was backup with TWRP and it seems to have semi bricked the phone.
I also tried restoring the backup and I get an error "E:\ No Partition selected for restore."
Justintoxicated said:
I had just downloaded the latest firmware to upgrade to lolipop, I did a titanium backup, then a nandroid with TWRP.
Upon reboot I can only get to the default recover screen (The one with the android on the skateboard). I can boot into TWRP and have tried clearing cache and delvik cache, and now doing a factory reset but I'm still having the problem. sometimes when rebooting from TWRP the phone boots to the lock screen (or to setup screen after factory reset), then a few seconds later reboots back to the screen with the android on the skateboard.
I haven't even started installing the new firmware, all I did was backup with TWRP and it seems to have semi bricked the phone.
I also tried restoring the backup and I get an error "E:\ No Partition selected for restore."
Click to expand...
Click to collapse
You flashed twrp either by twrp manager or allowed flashify to download the image for you. Try flashing the firmware zip I posted in tigerstowns thread that has twrp in it. If that doesn't work you will need to ruu and then install twrp and restore. Do not use twrp manager.
dottat said:
You flashed twrp either by twrp manager or allowed flashify to download the image for you. Try flashing the firmware zip I posted in tigerstowns thread that has twrp in it. If that doesn't work you will need to ruu and then install twrp and restore. Do not use twrp manager.
Click to expand...
Click to collapse
I beleive I flashed twrp origionally from fastboot, that was months ago though when we got the 4.4.4 update.
Do you mean I need to flash that zip from fastboot?
I'm worried about trying to flash firmware with the phone in a strange state. I'm almost thinking that something went bad inside the phone, but not convinced yet. It has been doing strange things lately, constant searching for location, pausing itself durring playback of music, and some random restarts. I haven't been messing it it so it seems strange to all of a sudden have these issues after many months.
Justintoxicated said:
I beleive I flashed twrp origionally from fastboot, that was months ago though when we got the 4.4.4 update.
Do you mean I need to flash that zip from fastboot?
I'm worried about trying to flash firmware with the phone in a strange state. I'm almost thinking that something went bad inside the phone, but not convinced yet. It has been doing strange things lately, constant searching for location, pausing itself durring playback of music, and some random restarts. I haven't been messing it it so it seems strange to all of a sudden have these issues after many months.
Click to expand...
Click to collapse
Nah man. Just reflash the firmware zip that contains twrp and report back. The older twrp are not safe to use on the newer firmware. I have a pda thread stickied in the general section that explains. Phone is likely fine.
dottat said:
Nah man. Just reflash the firmware zip that contains twrp and report back. The older twrp are not safe to use on the newer firmware. I have a pda thread stickied in the general section that explains. Phone is likely fine.
Click to expand...
Click to collapse
Ok, yea, I flashed the new firmware (with twrp) using fastboot , I'm still stuck on the same screen though. I did not install lolipop because I need to get the phone to USB mode to copy it over, which I cannot do because it will not start up.
Justintoxicated said:
Ok, yea, I flashed the new firmware (with twrp) using fastboot , I'm still stuck on the same screen though.
Click to expand...
Click to collapse
Ok...so follow me...if you flashed what you thought was cache on the new firmware but using an older twrp you wiped system instead.
Do you have your stuff backed up?
dottat said:
Ok...so follow me...if you flashed what you thought was cache on the new firmware but using an older twrp you wiped system instead.
Do you have your stuff backed up?
Click to expand...
Click to collapse
I don't know, I made a nandroid to my external memory card and immediately after that I was no longer able to start up... I tried to restore the nandroid and I cannot. So I would say no I am probably not backed up. I do still have RDKN rom on the memory card for 4.4.3, should I try to re-install that?
TWRP is now version 2.8.5.0, so apparently it updated correctly (I think before it was 2.8.1)
Justintoxicated said:
I don't know, I made a nandroid to my external memory card and immediately after that I was no longer able to start up... I tried to restore the nandroid and I cannot. So I would say no I am probably not backed up. I do still have RDKN rom on the memory card for 4.4.3, should I try to re-install that?
Click to expand...
Click to collapse
No. Your best bet to get your stuff back would be to downgrade firmware back to 4.4.4 and reflash the latest twrp img only and then restore your nand.
dottat said:
No. Your best bet to get your stuff back would be to downgrade firmware back to 4.4.4 and reflash the latest twrp img only and then restore your nand.
Click to expand...
Click to collapse
Ok my internet is not working on my laptop at work (only of the PC I'm on and no way to transfer files without my phone), so I guess I will try to do this when I get home. At this point I don't even care about my data, I wanted to save my text conversations but other than that everything I need should be saved in my titanium backup.
Justintoxicated said:
Ok my internet is not working on my laptop at work, so I guess I will try to do this when I get home. At this point I don't even care about my data, I wanted to save my text conversations but other than that everything I need should be saved in my titanium backup.
Click to expand...
Click to collapse
And that's what I figured. So flash 4.4.4. Flash latest twrp. Restore nand from ext sd. Boot up. Install this app.
https://www.androidfilehost.com/?fid=95916177934537937
Run it and link to your Google account and make it perform a backup.
It will do your apps/email accounts/texts/even home screen layout. And it will do it once a day for you automatically or on demand whenever.
Once you get a good backup on this app you can simply flash the new ruu and use this app to restore.
dottat said:
And that's what I figured. So flash 4.4.4. Flash latest twrp. Restore nand from ext sd. Boot up. Install this app.
https://www.androidfilehost.com/?fid=95916177934537937
Run it and link to your Google account and make it perform a backup.
It will do your apps/email accounts/texts/even home screen layout. And it will do it once a day for you automatically or on demand whenever.
Once you get a good backup on this app you can simply flash the new ruu and use this app to restore.
Click to expand...
Click to collapse
Update, restarted the computer and I was able to restore the old firmware. I re-installed the old rom afterwards (not my nandroid) and I am unable to get into the OS. Well technically I get prompted to select a language, after which the phone reboots back to the S-off androids with skateboards bootloader. Does this mean my phone is toast?
Hey guys, should I S-on the phone load the stock bootloader and try to return it? It is over a year old so I think I will need to use my insurance ($100). What is the best way to go about doing this?
Also when I get my replacement phone will there still be a way to S-off?
Thanks,
- Jusitn
The problem appears to be something wrong with my micro SD card! I removed the micro SD card and I can boot up fine. I guess I need to find another way to copy the rom to the micro SD install the rom then remove the micro SD card.
edit:
Oh this is worse than paying $100 for a new phone. It appears that creating a backup instead of creating a backup, actually corrupted my memory card. Now all the photos are backed up to the cloud but it will take me hours and hours to get all my apps back to the way they were. Some Security camera settings, Rifle target hand load development all gone. Audio book place holders, all notes taken etc. Nothing life or death but those security cameras will take me forever to figure out. I know I know, why not create a backup right? Well that's what I was trying to do!
So I was able to get back some data using some recovery software, unfortunately I was not able to retrieve the nandroid or the titanium backup files. Pictures were backed up to the could and music licenses and other hting I can add back on from the PC. Very time consuming though.
Anyways, what should I do now? Should I just reformat the SD card and continue to use it or should I assume that this happened because the card is bad and replace it with something else?
Justintoxicated said:
So I was able to get back some data using some recovery software, unfortunately I was not able to retrieve the nandroid or the titanium backup files. Pictures were backed up to the could and music licenses and other hting I can add back on from the PC. Very time consuming though.
Anyways, what should I do now? Should I just reformat the SD card and continue to use it or should I assume that this happened because the card is bad and replace it with something else?
Click to expand...
Click to collapse
I don't know what file system you're using but assuming it's one that windows can read, connect it to a PC and run chkdsk on it. If you don't know how to do that from a command prompt, right click on the drive in windows explorer and choose properties. Then tools and then click on the check now button under Error-checking. A small window will open. A line that says automatically fix file system errors will be checked by default. In your case, I'd suggest also checking the line that says "scan for and attempt recovery of bad sectors". It'll take a while for it to complete with that line checked so be patient. If you're lucky, it might just fix your problem. No promises but it's worth a try.
When it's done you can look in your event viewer to see what it found, if anything. If it finds bad sectors, I wouldn't trust the card. It can be used but there's no guarantee that more problems won't pop up. Maybe, maybe not.
To get to your event viewer, in Win 7 (not sure about Windows 8) click start and in the search box type event.vwr. I'm not sure what category you have to look under in there but perhaps under Winlogon. That's where you'll find it if it requires a reboot to check the card but that's not likely so I'm not sure.
robocuff said:
I don't know what file system you're using but assuming it's one that windows can read, connect it to a PC and run chkdsk on it. If you don't know how to do that from a command prompt, right click on the drive in windows explorer and choose properties. Then tools and then click on the check now button under Error-checking. A small window will open. A line that says automatically fix file system errors will be checked by default. In your case, I'd suggest also checking the line that says "scan for and attempt recovery of bad sectors". It'll take a while for it to complete with that line checked so be patient. If you're lucky, it might just fix your problem. No promises but it's worth a try.
When it's done you can look in your event viewer to see what it found, if anything. If it finds bad sectors, I wouldn't trust the card. It can be used but there's no guarantee that more problems won't pop up. Maybe, maybe not.
To get to your event viewer, in Win 7 (not sure about Windows 8) click start and in the search box type event.vwr. I'm not sure what category you have to look under in there but perhaps under Winlogon. That's where you'll find it if it requires a reboot to check the card but that's not likely so I'm not sure.
Click to expand...
Click to collapse
exFat for the card, and yes I am on windows 7. I tried to run a check as it was detected as having problems when I plugged the card into my laptop. Then it said I needed to dismount the drive and I said ok. Then it would just hang up. I reformatted the card and then ran the checkdisk again and it tells me that there are no problems now. I guess the card is ok and the issue was caused by TWRP? Not very cool when creating a back delete all your titanium backups and your nandroid that you were trying to create. Unfortunately I have to start from scratch on everything now. I even tried restoring to an older nandroid from May that was saved on my computer but that failed as well. for different reasons.
Justintoxicated said:
exFat for the card, and yes I am on windows 7. I tried to run a check as it was detected as having problems when I plugged the card into my laptop. Then it said I needed to dismount the drive and I said ok. Then it would just hang up. I reformatted the card and then ran the checkdisk again and it tells me that there are no problems now. I guess the card is ok and the issue was caused by TWRP? Not very cool when creating a back delete all your titanium backups and your nandroid that you were trying to create. Unfortunately I have to start from scratch on everything now. I even tried restoring to an older nandroid from May that was saved on my computer but that failed as well. for different reasons.
Click to expand...
Click to collapse
What reason did the restore fail for? And don't ever s-on unless you have let me have a crack at a phone. Not one thing you have said so far makes me think its phone. Unfortunately I have ended up with corrupt exfat discs before too. Sucks.
dottat said:
What reason did the restore fail for? And don't ever s-on unless you have let me have a crack at a phone. Not one thing you have said so far makes me think its phone. Unfortunately I have ended up with corrupt exfat discs before too. Sucks.
Click to expand...
Click to collapse
I don't remember, probably missing a file or something.