So I just tried to go back to a previous nandroid backup I had on my phone, specifically CyanogenTazz because I didn't like the current ROM I was on... So I wiped my dalvik cache and did a factory reset wipe and then went to restore and it gave me this error "error : run 'nandroid-mobile.sh restore' via adb!" What is the exact command in command prompt to do that? And what caused this error? I'm pretty confused
Does your battery have plenty of charge left? If not, plug the phone in and try again. Nandroid will refuse to do a backup or restore unless it knows it has plenty of power.
Sent from my Eris using Tapatalk
plug your phone into a charger and try again
My battery is at 100% And I also had the charger plugged in when I tried to do it.
thisisreallygay said:
My battery is at 100% And I also had the charger plugged in when I tried to do it.
Click to expand...
Click to collapse
I've had this happen to me. Your backup name might be to long or contain characters that aren't kosher. Can you restore an older backup? If you can, restore to an older backup and change the name if that's possible.
I can't restore any backup, I have 3, one is named CyanogenTazz V5 the other is just the like random characters that Nandroid gives it, and then the other one I've used multiple times before and it has worked... I started having this problem right after flashing the Aloysius V12 Purehero port or something like that. The ROM works.. Just nandroid doesn't.
Okay I heard you need to have USB Debugging on when doing it and I had that option on.. but when I would turn off my phone it would disable USB Debugging I think because it just wouldn't work.. So I plugged it into my computer so that it would activate USB debugging and then I turned it off while plugged it and it worked now... So I don't know if that was it or what.. but I didn't do anything different other than that. But its working now so thanks
I had this problem. My recommendation. Make a new backup. Take an old backup and rename this folder the name assigned to the new backup. Then try restoring that backup. I had success with this method.
You can try renaming the backup. I had the same issue and that took care of it. Basic rule of thumb. Keep the new name short and only include alpha numeric characters.
The default naming for new backups works pretty like a time stamp. Bds-yyyyddmm-tttt. If you have multiple backups rename them to what you'll remember easily.
Oh and has anyone tried a BART backup or know what that is?
Sent from my Eris using XDA App
When you get that error message "... run nandroid-mobile.sh...", the cause of the problem is ALWAYS logged in the recovery log; you can discover what the problem is simply by looking at that log file - either using Root Explorer, or by pulling the log file to your PC with ADB, as in:
C:\foobar> adb pull /cache/recovery/log log.txt
C:\foobar> wordpad log.txt
(You can do these steps without ever leaving Amon_RA, as "adbd" is running when Amon_RA is booted)
Turns out to be a lot faster than playing 20 questions with random dudes on the Internet
I'm going to guess NAND backup names can't include special characters as well. I'd also think it'd probably be best not to include spaces in the name either. I'm not positive about such things in Linux but I do know that in some versions of unix-based OS's anything after the space would essentially be ignored. So if the name of the backup is passed as a parameter to a function, "CyanogenTazz v6" would be evaluated as "CyanogenTazz" and thus the backup wouldn't work.
Related
I have found that I can't perform either a Bart or nandroid backup from recovery. Any ideas? Do I perhaps need to update Among RA? My version is 1.6.2.
Sent from my FroyoEris using XDA App
gospodinwizard said:
I have found that I can't perform either a Bart or nandroid backup from recovery. Any ideas? Do I perhaps need to update Among RA? My version is 1.6.2.
Sent from my FroyoEris using XDA App
Click to expand...
Click to collapse
Does it just get like 1 or 2 dots into it and then says it can't?
Sometimes it has to do with it properly mounting your SD card.
Try plugging USB into a computer, turning on USB-MS toggle for a second, then turning off USB-MS Toggle. SOmetimes that works.
Otherwise, turn off the phone, pull out the SD Card, put it back in, then boot back into Recovery.
This happens to me occasionally. You can't Flash from Zip either, when this happens. It's annoying but it'll work eventually.
I haven't tried removing the SD Card, but I will try that. Flashing from zip still works fine. And I can still use nandroid-mobile.sh via adb to make backups with no issues. Restoring from recovery works fine as well. It seems to get about half way through the backup process before it craps out and tells me to use nandroid-mobile.sh. And this all happens even if the battery is at 100% or plugged into the wall charger.
gospodinwizard said:
I haven't tried removing the SD Card, but I will try that. Flashing from zip still works fine. And I can still use nandroid-mobile.sh via adb to make backups with no issues. Restoring from recovery works fine as well. It seems to get about half way through the backup process before it craps out and tells me to use nandroid-mobile.sh. And this all happens even if the battery is at 100% or plugged into the wall charger.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=7661952&postcount=1
Your SD card possibly needs to be re-formatted.
Don't forget to back it up first.
Once I formatted my card with normal FAT and had very strange behavior as such.
And even if you already did as FAT32, sometimes recovery (and android) only likes it if you use home > menu > settings > Sd card and storage > format to format it.
Once, I had to format it fat32, then go into android and format it again.
Odd, I think. But something about how it writes blocks of data, and it can't seem to write it the way it wants in recovery, even though windows can with nandroid-mobile.sh.
I don't know how well this works for our phone, but this might be worth a shot:
http://erlern.wordpress.com/2010/06/03/error-run-nandroid-mobile-sh-via-console/
I had this problem last nite. Possibly your battery may be low or something with the SD card. For me was as easy as letting the phone charge for like 20 minutes then try again
Sent from my Eris using XDA App
dragon1018 said:
I had this problem last nite. Possibly your battery may be low or something with the SD card. For me was as easy as letting the phone charge for like 20 minutes then try again
Sent from my Eris using XDA App
Click to expand...
Click to collapse
I was thinking the same thing, but he said:
And this all happens even if the battery is at 100% or plugged into the wall charger.
Click to expand...
Click to collapse
OK just to top this all off and make it even weirder, nandroid backup from recovery just started working again. I have no concrete idea why, but I did notice something a bit odd. I was poking around in the terminal emulator to see what I could decipher. I entered "whoami" and got the response "app54". So I typed "su" and a message popped on the screen that "Titanium Backup has been granted root access". Another "whoami" returned "root". I uninstalled TB and booted into recovery but the backup still didn't work. Rebooted, reinstalled TB, and went back to recovery at which point nandroid backup decided it was time to work. I can't imagine what, if any, the connection is with my backup problems but nonetheless this is what transpired. I was left wondering if TB had done something with/to busybox that caused the problem.
Ever since i rooted my phone. I have not been able to run any of the backup options in the recovery menu. Is there anything specific i should do? I have tried rerooting and a couple other hocus pocus fixes but nothing ever works and i do not want to run these backups from adb shell.
Seannoxious said:
Ever since i rooted my phone. I have not been able to run any of the backup options in the recovery menu. Is there anything specific i should do? I have tried rerooting and a couple other hocus pocus fixes but nothing ever works and i do not want to run these backups from adb shell.
Click to expand...
Click to collapse
Why exactly can you not use the recovery menu (i.e., is it a trackball issue)?
If so, check out this post: http://forum.xda-developers.com/showpost.php?p=9124095&postcount=83
Cheers!
scary alien said:
Why exactly can you not use the recovery menu (i.e., is it a trackball issue)?
If so, check out this post: http://forum.xda-developers.com/showpost.php?p=9124095&postcount=83
Cheers!
Click to expand...
Click to collapse
Sorry no it's not a trackball issue. It just says Error: run in adb. I have seen a lot of fixes but none of them seem to ever work. It wont ever allow me to bart or nand backup always errors out. I can external backup but that really isn't any sweat off my nuts.
Seannoxious said:
Sorry no it's not a trackball issue. It just says Error: run in adb. I have seen a lot of fixes but none of them seem to ever work. It wont ever allow me to bart or nand backup always errors out. I can external backup but that really isn't any sweat off my nuts.
Click to expand...
Click to collapse
Argh, I really wish I could remember what the solution was for that. I'm afraid someone else is going to have to answer because I haven't had that happen in many months.
One workaround, download the free ROM Manager off the market. It won't replace Amon RA, if that's what you're using, but it'll allow you to load ClockworkMod Recovery from Amon RA, and then perform backups and restores from there. You can also use the ROM Manager app to tell it what to do and then it'll reboot and automatically do whatever you tell it and reboot after.
I don't know for sure that this will alleviate this problem, but it won't do anything permanent to your phone and it's cheap to try. Come to think of it, maybe one of the reasons I haven't had this problem in many months is I've been using ROM Manager for over four months.
Let me know if it helps if you try it.
Can you post your exact error message? I scanned Amon_RA's recovery source as well as the nandroid-mobile.sh script and found similar things, but the exact error message would help tremendously.
1. Make sure you have enough space on your /sdcard. The nandroid-mobile.sh script will check to make sure that you have at least 130MB or more of free space before allowing a backup to be performed.
2. Be sure to have enough battery charge (best bet is to always be topped-off and plugged-in...just to be sure). The nandroid-mobile.sh script will check to make sure that you have at least 30% or more battery charge before he'll allow a backup to take place.
A couple of months back, I examined the nandroid-mobile.sh script for circumstances under which it would return a non-zero return status. This post over on AF details that analysis: http://androidforums.com/eris-all-things-root/142379-help-please-cant-nandroid-restore.html#post1604509
As you can see, there are several scenarios that could lead to the backup refusing to work (including a wonky /sdcard). So, if you have another card you could try, that might help.
Cheers!
Too late to run through this tomorrow but will observe all this new found data and report back. Thanks guys always appreciated.
scary alien said:
2. Be sure to have enough battery charge (best bet is to always be topped-off and plugged-in...just to be sure). The nandroid-mobile.sh script will check to make sure that you have at least 30% or more battery charge before he'll allow a backup to take place.
Click to expand...
Click to collapse
Good point! Now that you reminded me, I think this was the main culprit when I was having a problem, and it just so happens that my phone is nearly always charged pretty full for the past several months since I USB tether for my computer internet.
roirraW "edor" ehT said:
Good point! Now that you reminded me, I think this was the main culprit when I was having a problem, and it just so happens that my phone is nearly always charged pretty full for the past several months since I USB tether for my computer internet.
Click to expand...
Click to collapse
A low battery was the issue the couple of times I ever had it as well.
scary alien said:
Can you post your exact error message? I scanned Amon_RA's recovery source as well as the nandroid-mobile.sh script and found similar things, but the exact error message would help tremendously.
1. Make sure you have enough space on your /sdcard. The nandroid-mobile.sh script will check to make sure that you have at least 130MB or more of free space before allowing a backup to be performed.
2. Be sure to have enough battery charge (best bet is to always be topped-off and plugged-in...just to be sure). The nandroid-mobile.sh script will check to make sure that you have at least 30% or more battery charge before he'll allow a backup to take place.
A couple of months back, I examined the nandroid-mobile.sh script for circumstances under which it would return a non-zero return status. This post over on AF details that analysis: http://androidforums.com/eris-all-things-root/142379-help-please-cant-nandroid-restore.html#post1604509
As you can see, there are several scenarios that could lead to the backup refusing to work (including a wonky /sdcard). So, if you have another card you could try, that might help.
Cheers!
Click to expand...
Click to collapse
I got it to run just the NANdroid backup without error for the first time ever. Whenever i try to do NANdroid + ext or BART backup it says Error:Run X in adb shell. I have enough battery but will try charging to 100% and being plugged in in a second. Will try an alternate SD and report back. I have an 8gig micro sd hc. Transcend. Not sure if that matters.
Seannoxious said:
I got it to run just the NANdroid backup without error for the first time ever. Whenever i try to do NANdroid + ext or BART backup it says Error:Run X in adb shell. I have enough battery but will try charging to 100% and being plugged in in a second. Will try an alternate SD and report back. I have an 8gig micro sd hc. Transcend. Not sure if that matters.
Click to expand...
Click to collapse
Yeah, I've never run anything other than a Nandroid backup and restore--never have done a BART backup or + ext...
Good luck!
Seannoxious said:
I got it to run just the NANdroid backup without error for the first time ever. Whenever i try to do NANdroid + ext or BART backup it says Error:Run X in adb shell. I have enough battery but will try charging to 100% and being plugged in in a second. Will try an alternate SD and report back. I have an 8gig micro sd hc. Transcend. Not sure if that matters.
Click to expand...
Click to collapse
This is weird because I downloaded the rom manager which is quite awesome might i add. It looks at my SD notices it has enough space to backup the NAND but refuses to do the external backup because it says No sd-ext found. Going to try titanium backup + nand + ext backup (from my pc) see if that covers all bases
Seannoxious said:
This is weird because I downloaded the rom manager which is quite awesome might i add. It looks at my SD notices it has enough space to backup the NAND but refuses to do the external backup because it says No sd-ext found. Going to try titanium backup + nand + ext backup (from my pc) see if that covers all bases
Click to expand...
Click to collapse
Did you ever partition your /sdcard (i.e., for apps2sd)? If not, you won't (or shouldn't have) any ext2 or ext3 partitions (I believe...).
Just wanted to make sure you weren't chasing your tail...
scary alien said:
Did you ever partition your /sdcard (i.e., for apps2sd)? If not, you won't (or shouldn't have) any ext2 or ext3 partitions (I believe...).
Just wanted to make sure you weren't chasing your tail...
Click to expand...
Click to collapse
I never did but thought that nandroid+backup did the backup of the sd in general not necessarily the partitions.
Also just installed froshedyp 9 after a full wipe did the nandroid backup and it put xtr back on the phone? I thought nandroid backup was to backup your **** so when you installed a new rom you didn't have to reset everything up (apps and settings and the such)
First, SD-Ext is referring to a Ext2/3/4 partition on the SD card, which you would've had to put there for old style (before Froyo) Apps2SD function, as Scary Alien said. So a failure to backup SD-Ext doesn't mean the backup itself fails, it just skips the SD-Ext backup if it doesn't exist, which it sounds like it doesn't.
Also, no, a Nandroid is to backup your ROM exactly the way you have it configured including the ROM itself. That's why it has to be done outside of the ROM, in recovery. Titanium Backup and other backup apps are for doing what you're talking about, backup up your Apps and your Apps settings.
Note that it's a risky thing to use any backup program to backup the system settings. Not actually risky to back them up, but you should never restore them to a completely different ROM (even if they're both based on CM6.x or whatever, or both based on Stock), so it's really only applicable between minor version upgrades of the same ROM (CelbFroyo 3.9 to CelbFroyo 4.0). Even then this is risky and sometimes breaks things, so don't expect to be able to do it too often if you change ROMs again.
roirraW "edor" ehT said:
First, SD-Ext is referring to a Ext2/3/4 partition on the SD card, which you would've had to put there for old style (before Froyo) Apps2SD function, as Scary Alien said. So a failure to backup SD-Ext doesn't mean the backup itself fails, it just skips the SD-Ext backup if it doesn't exist, which it sounds like it doesn't.
Also, no, a Nandroid is to backup your ROM exactly the way you have it configured including the ROM itself. That's why it has to be done outside of the ROM, in recovery. Titanium Backup and other backup apps are for doing what you're talking about, backup up your Apps and your Apps settings.
Note that it's a risky thing to use any backup program to backup the system settings. Not actually risky to back them up, but you should never restore them to a completely different ROM (even if they're both based on CM6.x or whatever, or both based on Stock), so it's really only applicable between minor version upgrades of the same ROM (CelbFroyo 3.9 to CelbFroyo 4.0). Even then this is risky and sometimes breaks things, so don't expect to be able to do it too often if you change ROMs again.
Click to expand...
Click to collapse
Sweet thanks for clearing everything up man.
Recently I have been having this problem. I go into system recovery and make a nandroid backup. then tell recovery to reboot phone. when the phone loads. I check the backup directory and there is no new backup. I do however get a rather large file in my lost.dir (I am thinking this is my backup?) I am using the system recovery that comes loaded with eclipse v0.6.1 and have it installed and set to recovery. also using the supplied charger from VZW.
So when you go into nandroid restore there is no backups there?
Sent from my DROID X2 using XDA App
right. I load BSR make a Nandroid backup, reboot the phone and it is not there. I do however have a large file in my lost.dir folder. This does not happen every time, but recently started happening, seems to happen more than not. I have been able to get a backup but it took 2 or 3 attemps for it to "stick"
Had a similar problem recently. I did a nandroid backup, but got some weird message about it not being able to backup sd-ext (which was my target). When I checked, there was no backup created, but in addition my entire Titanium Backup directory wound up in LOST.DIR. Dunno what happened, could be related to some other TB problems I'd had recently, but it was annoying as hell.
Deleted the contents of LOST.DIR, recreated Titanium Backup, and tried to do a nandroid backup again. Still got that weird "could not backup sd-ext" message, but it seemed to take this time. Might have been an error on the SD card?
I have ALWAYS gotten the line about not able to backup sd-ext no partition found.
I don't need to backup my external card anyway. It never gets deleted unless I specific format the card.
I have never had a problem when making my nandroid. I ALWAYS backup to external and it shows up in a folder named clockworkmod>backup>then date and time backup was created.
Are u trying to backup to internal or external? I have noticed that even tho sd flip is installed with eclipse that system recovery does not see this flip so if u backup to external and look for it in root explore it will be in the sd card folder(which is really ur external due to sd flip) sorry if that's confusing how I wrote it.
iCurmudgeon said:
Had a similar problem recently. I did a nandroid backup, but got some weird message about it not being able to backup sd-ext (which was my target). When I checked, there was no backup created, but in addition my entire Titanium Backup directory wound up in LOST.DIR. Dunno what happened, could be related to some other TB problems I'd had recently, but it was annoying as hell.
Deleted the contents of LOST.DIR, recreated Titanium Backup, and tried to do a nandroid backup again. Still got that weird "could not backup sd-ext" message, but it seemed to take this time. Might have been an error on the SD card?
Click to expand...
Click to collapse
I believe the message you're getting is normal. I've seen that message with every nandroid backup that I've created. Not sure if it is related to the problem, maybe? Thank you for the reply.
Sent from my DROID X2 using XDA App
This is a very strange problem indeed.
I have created and restored backups consistently over the past few days due to all the activity here with roms but I haven't had the issue of it not "sticking" when making the backup.
I wonder if a reinstall of system recovery could help with this
Um could you possibly reflash your device? This might be a bug buried deep inside the rom, if you use ti backup it restores your data almost 100 percent.
Make sure to clean data, cache, and dalvik cache.
Sent from my DROID X2 using XDA App
First id like to point out some roms delete worthless directories. If it keeps being put into a lost.dir maybe it actually was a needed directory that was deleted. In which case you can just make the dir "clockworkmod>backup>" maybe that's all it needs. Im not 100% sure
I have read a few posts across forums saying to ignore that error of not being able to backup sd-ext ... although I've also never had an issue with using the backups I've created.
However I hit install system recovery and it does. I go into recovery mode and it does. The strange part is every rom I install takes out my recovery. On my DROIDX I never had this problem. And it makes having a backup a little worthless because if the phone boot loops I only have the option of rsdlite then reinstalling recovery and then using the backup. Yes that keeps it worth it but it loses the usefulness. Does anyone know how to make it permanent? Or at least survive a data wipe... my last rom was ATRIX which did a data wipe without asking in past roms I do a cache wipe and leave data on to make sure it is usable. Then I wipe data and reinstall recovery...
Sent from my DROID X2 using XDA App
I think that rom makers might be able to male it permanent by having isbn debugging already on and have the hijack charge only mode script system recovery uses already installed. I don't know if that is possible tho.
ashclepdia said:
I wonder if a reinstall of system recovery could help with this
Click to expand...
Click to collapse
First thing I tried, but still had two out of three backups disappear.
m125 said:
Um could you possibly reflash your device? This might be a bug buried deep inside the rom, if you use ti backup it restores your data almost 100 percent.
Make sure to clean data, cache, and dalvik cache.
Click to expand...
Click to collapse
Happen to me on both the eclipse v0.6 remix5 and the eclipse v0.6.1, all wiped every time, (not saying it has anything to do with the rom, love eclipse, would have hated this phone if not for him)
SubVirus said:
First id like to point out some roms delete worthless directories. If it keeps being put into a lost.dir maybe it actually was a needed directory that was deleted. In which case you can just make the dir "clockworkmod>backup>" maybe that's all it needs. Im not 100% sure...
Click to expand...
Click to collapse
My directory is there. my previous nandroids are there, the new ones just don't always seem to be saved there? somehow getting corrupted?
SubVirus said:
However I hit install system recovery and it does. I go into recovery mode and it does. The strange part is every rom I install takes out my recovery. On my DROIDX I never had this problem. And it makes having a backup a little worthless because if the phone boot loops I only have the option of rsdlite then reinstalling recovery and then using the backup. Yes that keeps it worth it but it loses the usefulness. Does anyone know how to make it permanent? Or at least survive a data wipe... my last rom was ATRIX which did a data wipe without asking in past roms I do a cache wipe and leave data on to make sure it is usable. Then I wipe data and reinstall recovery...
Click to expand...
Click to collapse
After flashing a new rom, I have always had to go back into system recovery and set superuser privileges and "install" again.
I've used this backup before, at least 5 times so I know it's good. But this last time it failed due to the above error, after trying to install Jaime's JB rom (I don't know if that is relevant). I found several ways to fix the error here and elsewhere, but no need as I had a backup from yesterday that still worked. Right now I'm just looking for someone to explain to me what the error means and why it happened to this particular backup given that I didn't rename or change anything? This way I don't repeat the error. Thanks in advance.
Essentially what you need to do is redownload the rom. But this time make sure you have a very strong internet connection. If your downloading on your phone get right next to the router. When your MD5 sums don't match it is because there is an error in the download process and some of the rom files have been corrupted. If you have a strong internet connection it helps ensure all the files are downloaded properly. Hope this helps....
Sent from my SAMSUNG-SGH-I717 using xda premium
I didn't get this error whilst installing a rom though, it was trying to restore a backup. But I guess the principle holds true, somehow my backup got corrupted.
I'll download the rom again (this will be try number 6) and see if getting closer to the router will helpe, thanks.
I get that error when I have too much on the internal sd card. I think the limit is 4gigs. So anything you have in /system/media like movies and music move to external sd card before you make a backup.
So my current state of the internal sd card can affect a known good backup?
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Probably not. Dumb suggestion. But that's one reason that error happens, but that keeps the backup from completing. Sorry.
Are you using Rom Manager or CWM?
I make most of my backups in CWM and copy to my computer. I'm trying to think of what I did between the last time I used that backup successfully... Only thing I can think of is the 6 failed attempts to install the JB rom. Now I'm kindof worried about making attempt #7 because I only have the 1 working backup... If that gets corrupted I'll be soft-bricked with no way to install a rom.
LittleRedDot said:
I make most of my backups in CWM and copy to my computer. I'm trying to think of what I did between the last time I used that backup successfully... Only thing I can think of is the 6 failed attempts to install the JB rom. Now I'm kindof worried about making attempt #7 because I only have the 1 working backup... If that gets corrupted I'll be soft-bricked with no way to install a rom.
Click to expand...
Click to collapse
I have noticed that if I copy a backup to my computer (64-bit, Win 7) and then copy back to my Note, I will get an MD5 mismatch message if I then try to restore from the backup. It may be due to the way that Win 7 file explorer indexes the file - or some other arcane windows thing. In any case I no longer transfer nandroid backps.
Ok I'm gonna stop obsessing over this and chalk it up to bad luck. Actually, since I rooted my first device this is the first time I've had anything go wrong, so I guess it was my turn. Thanks for all the help!
recovery just says something is wrong, look at log?
I tried a few versions (of the backup sets), same error.
What am I doing wrong? How do I fix it? :crying:
Log from recovery run...
Starting recovery on Thu Aug 16 21:58:52 2012
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (720 x 1280)
RA Revamped
Build : RA-VIGOR-v3.15-getitnowmarketing
Command: "/sbin/recovery"
ro.secure=0
ro.allow.mock.location=0
ro.debuggable=1
fuzzynco said:
recovery just says something is wrong, look at log?
Click to expand...
Click to collapse
This happens all the time to people.
You can't simply restore a backup from another device because then your new device will actually appear as your old device on Google and Verizons servers, which will cause all sorts of problems if Verizon were to ever successfully restore your old phone and try and send it off to someone else. To avoid this problem, the recovery won't even let you restore a backup from another phone, even if its the exact same hardware.
Go to play.google.com, go to view your devices in the settings section. You should see two Rezounds. One will have been activated in the past, and one whenever you first turned on your replacement after receiving it and logging in with your account. So the one that was activated in the past is clearly your original Rezound that you've returned. You can give it a name, like "DEAD REZOUND" so that you know by looking at the name which Rezound Google thinks you're using.
There is a workaround that will let you restore the backup anyway if you want to search for it, but I highly recommend you don't. If you do, you can then go to play.google.com again, view your existing devices in the settings section, and you'll see that Google thinks your new phone is the same one you just sent back to Verizon. It should show "DEAD REZOUND" as being registered again today (or whatever day you successfully restored a backup from your old phone)
To sum up: Don't restore a backup from another Rezound. You pretty much have to start over again.
I kind of follow... RA is an image backup
so it would duplicate the serial and device specific data.
I could do a TiBu of the user apps and data (and the
new xml files of the call log and sms's), though.
Use an app to export the calendar data to an
.ics (iCal file) and the phone book to a .vcf
for import on the 'new' phone.
Since Google added some 800+ empty
phone book entries and messed up my phone
book, I don't sync with it. I export the whole
thing to a vcf.
So the missing /dev/tty0 device file
error from the restore is just AR not
letting me shot myself in the foot,
right?
I'll need to install my ROM, then
restore the user apps and data
from TiBu then rebuild my 'desktop'?
Is it worth doing the RUU for ICS
to get there? The new phone was
offered the upgrade OTA, but I think
it was wiped by the unlock prior to
S-Off process. Would I flash
the ICS RUU, then flash the ICS/JB
hboot, to get fastboot commands,
then reflash recovery?
I have seperate micro cards for
the 600mb RUU zip and the
ICS firmware/radio/hboot(JB)
zip.
I'm thinking since I have to rebuild
the desktop anyway, maybe doing
the ICS RUU first is a good idea.
fuzzynco said:
so it would duplicate the serial and device specific data.
I could do a TiBu of the user apps and data (and the
new xml files of the call log and sms's), though.
Use an app to export the calendar data to an
.ics (iCal file) and the phone book to a .vcf
for import on the 'new' phone.
Since Google added some 800+ empty
phone book entries and messed up my phone
book, I don't sync with it. I export the whole
thing to a vcf.
So the missing /dev/tty0 device file
error from the restore is just AR not
letting me shot myself in the foot,
right?
I'll need to install my ROM, then
restore the user apps and data
from TiBu then rebuild my 'desktop'?
Is it worth doing the RUU for ICS
to get there? The new phone was
offered the upgrade OTA, but I think
it was wiped by the unlock prior to
S-Off process. Would I flash
the ICS RUU, then flash the ICS/JB
hboot, to get fastboot commands,
then reflash recovery?
I have seperate micro cards for
the 600mb RUU zip and the
ICS firmware/radio/hboot(JB)
zip.
I'm thinking since I have to rebuild
the desktop anyway, maybe doing
the ICS RUU first is a good idea.
Click to expand...
Click to collapse
In reply to the bolded part: Basically, yes. AR's nandroid places the backups in a folder with your phone's serial as the folder name. Attempting to restore any backup from a folder with any other name will fail to prevent the issues I mentioned above.
I do not and have not ever used Titanium Backup, so in regards to that, I can't be of any help.
If you have a linux machine, you can mount the data.img from any of your backups and then copy all the files from /data/app and data/data to your phone. This will restore most of your apps, and app data/settings. There will still be a few things you'll have to redo from scratch, and this may not work 100% for every app on your phone, but at least this way you don't have to redownload every single app and manually redo all your settings...
I did the RUU zip (it restarted itself, as expected), the firmware/radio/hboot(JB) zip
and then reflashed AR 3.15 from fastboot. Everything seems to be working now.
Do you know if the debloat script (freeze VZW apps) works for ICS OTA ROM?
fuzzynco said:
I did the RUU zip (it restarted itself, as expected), the firmware/radio/hboot(JB) zip
and then reflashed AR 3.15 from fastboot. Everything seems to be working now.
Do you know if the debloat script (freeze VZW apps) works for ICS OTA ROM?
Click to expand...
Click to collapse
not sure...
I couldn't get ViperROM 1.0.3 to not crash (com.android.phone kept crashing).
Trying a couple of others that are prerooted and deboated. So far the ICS &
Sense 3.6 looks fine. Still have the 'social network' stuff to freeze though,
Could I do something like make a zip (from adb shell) of the user apps
/data/app & /data/data directories (to preserve the unix permissions).
and leave that on fat32 sd card? Then merge that into the zip for the
rom to be installed so the installer will reload them?
Would I need to add lines to the installer script to have it load /data (with
the subdirs ../app and ../data)?
hmms maybe better to make a seperate zip to preinstall my saved
/data subdirs? Can I copy the ROMs installer binary and build
a installer script to mount /data, then install the /data directory,
umount /data?
a.mcdear said:
This happens all the time to people.
You can't simply restore a backup from another device because then your new device will actually appear as your old device on Google and Verizons servers, which will cause all sorts of problems if Verizon were to ever successfully restore your old phone and try and send it off to someone else. To avoid this problem, the recovery won't even let you restore a backup from another phone, even if its the exact same hardware.
Go to play.google.com, go to view your devices in the settings section. You should see two Rezounds. One will have been activated in the past, and one whenever you first turned on your replacement after receiving it and logging in with your account. So the one that was activated in the past is clearly your original Rezound that you've returned. You can give it a name, like "DEAD REZOUND" so that you know by looking at the name which Rezound Google thinks you're using.
There is a workaround that will let you restore the backup anyway if you want to search for it, but I highly recommend you don't. If you do, you can then go to play.google.com again, view your existing devices in the settings section, and you'll see that Google thinks your new phone is the same one you just sent back to Verizon. It should show "DEAD REZOUND" as being registered again today (or whatever day you successfully restored a backup from your old phone)
To sum up: Don't restore a backup from another Rezound. You pretty much have to start over again.
Click to expand...
Click to collapse
not really. im on my third rezound and i restored the same viper rom i had before.
this is what i did with AR
1. back up current rom
2. boot into rom
3. use root explorer and find the nandroids
4. noticed 2 folders in the same nanadroid folder ( light bulb)
5. move old back up to the location where the new one was.
6. boot into recovery and did a full wipe
7. restored old back up.
8 boot phone
9. BAM!
This app might work. I use it and it works great but I'm not sure if it restores data.
synisterwolf said:
not really. im on my third rezound and i restored the same viper rom i had before.
this is what i did with AR
1. back up current rom
2. boot into rom
3. use root explorer and find the nandroids
4. noticed 2 folders in the same nanadroid folder ( light bulb)
5. move old back up to the location where the new one was.
6. boot into recovery and did a full wipe
7. restored old back up.
8 boot phone
9. BAM!
Click to expand...
Click to collapse
Yeah this works perfectly fine, but can cause the new phone to register on the network as if it were the old one. It is perfectly possible to restore a backup from another phone, and it works fine... its just a bad idea because if your old phone is ever "recovered" and turned back on, VZW might see two identical devices on the network, which will cause problems in the future.
a.mcdear said:
Yeah this works perfectly fine, but can cause the new phone to register on the network as if it were the old one. It is perfectly possible to restore a backup from another phone, and it works fine... its just a bad idea because if your old phone is ever "recovered" and turned back on, VZW might see two identical devices on the network, which will cause problems in the future.
Click to expand...
Click to collapse
Good to know. Thanks
In my case, the backup is from a device that i bricked totally. couldnt get into download mode so im thinking they will just use it as parts
Sent from my iPhone...