Nandroid backup problem - Galaxy S Advance I9070 Q&A, Help & Troubleshooting

Not sure if this is a SGSA issue or more widespread. I did post this on my other thread, but it was OT for that thread so I thought I'd post here instead.
I have been running stock LQ4 for a month or so, but it was not really living up to my expectations. So earlier this week I rooted using the excellent guide here, and then I also installed CoCore E 6.0 kernel. I was still having the laggy problems, so rather than just do a wipe I thought I'd try a new ROM too.
Backed up the system using the CWM Nandroid backup, which reported no errors. I then did the various wipes of caches and Dalvik cache etc, and installed LightJB1.2 using CWM.
All went well, I had no issues, but I was a little surprised to have lost Swype (I find it works better for me than the Samsung keyboard, even with their swype-style functions). There were a couple of other things that I'd wanted to sort out too, so I decided to restore the Nandroid backup which I'd taken only an hour or so ago.
Bad move!
It all seemed to work fine, but on restoring I get the message that "Unfortunately, the process com.google.process.gapps has stopped". Mildly worrying, but moving on...
Then I came to try to reply to a sms message from my wife. Pressing in the reply box didn't bring up a keyboard. Odd.
I went into other apps and found I couldn't type there either.
Went into settings, and neither the samsung keyboard nor the swype keyboard appear to have been re-stored via the backup / restore.
So for some reason the Nandroid backup that I took appears to be somewhat incomplete and non-functioning. Is it possible that I've missed a step somewhere which would result in the gapps (I presume Google Apps) and keyboards being missed from the Nandroid backup? That was my first experience with a nandroid backup, but of course I'm feeling less trusting towards it now!!
Cheers!
Matt

That is indeed weird. I've never had any problem restoring using cwm before. Did you format system/data/cache before restoring? If you didn't, then that maybe the case.

arffrhn said:
That is indeed weird. I've never had any problem restoring using cwm before. Did you format system/data/cache before restoring? If you didn't, then that maybe the case.
Click to expand...
Click to collapse
No I didn't - I haven't spotted that as a requirement in the guides that I've briefly looked at. Whilst I'm messing around a little, I'll take a backup of the current state (LQ4 / CoCore E 6.0 / LightJB1.2) and then add that step into the clearup / restore to see if that makes a difference.
I noticed that each of the "wipes", CWM confirms that the format is also done. However, those wipes don't include "system", so I'll give that a go. Nothing to lose really!
Thanks!
Matt

Just tried that - made no difference. Is there any point in looking in detail at the files in the clockworkmod/backup folder to see what the issue might be? I'd like to be able to rely on cwm backups!!

larkim said:
Just tried that - made no difference. Is there any point in looking in detail at the files in the clockworkmod/backup folder to see what the issue might be? I'd like to be able to rely on cwm backups!!
Click to expand...
Click to collapse
Just restored from the LightJB backup that I took, and that has worked without any issues. Wonder what is wrong with that first backup set?
Having copied it across to my laptop, the files showing are:-
Code:
23/05/2013 12:02 16,777,216 boot.img
23/05/2013 12:05 0 cache.ext4.tar
23/05/2013 12:05 12,288 cache.ext4.tar.a
23/05/2013 12:03 0 data.ext4.tar
23/05/2013 12:04 1,000,000,000 data.ext4.tar.a
23/05/2013 12:04 458,690,560 data.ext4.tar.b
24/05/2013 16:15 0 dump.txt
23/05/2013 12:07 513 nandroid.md5
23/05/2013 12:02 0 system.ext4.tar
23/05/2013 12:03 476,672,512 system.ext4.tar.a
I'm only pursuing this in case another noob like me gets caught out with the backup failing on them!!
Cheers!
Matt

Did you go and format the /preload folder because the nandroid backup doesn't backup or restore that directory. That may be why the gapps process is stopping.
Sent from my GT-I9070 using xda premium

Restore that backup.
Then go to advanced and select report error.
Then boot back into system and give me the log here.
The file will be saved in sdcard.
I do not respond to tech support via PM

Related

made a big noob mistake, help please!!! :-(

okay heres the problem, i flash roms regularly so i have a few nandroid backups. what i did was rename the backup folders to the name of the roms so i could keep up with them, i just wiped a previous rom and tried to restore a nandroid backup that i renamed and i keep getting restore error. i'm pretty sure its becaused i renamed them, can anyone tell how i can get the orginal folder caption back for the roms i backed up, and to top it off i renamed my stocked 1.5. thanks in advance
winterstormhaku said:
okay heres the problem, i flash roms regularly so i have a few nandroid backups. what i did was rename the backup folders to the name of the roms so i could keep up with them, i just wiped a previous rom and tried to restore a nandroid backup that i renamed and i keep getting restore error. i'm pretty sure its becaused i renamed them, can anyone tell how i can get the orginal folder caption back for the roms i backed up, and to top it off i renamed my stocked 1.5. thanks in advance
Click to expand...
Click to collapse
what is the error? is it run nandroid-mobile.sh from adb?
i tried to restore using the flash rec method. this is what im getting, error : run 'nandroid-mobile.sh restore via adb, problem is i dont know how to through adb i've always used the flash rec method
winterstormhaku said:
i tried to restore using the flash rec method. this is what im getting, error : run 'nandroid-mobile.sh restore via adb, problem is i dont know how to through adb i've always used the flash rec method
Click to expand...
Click to collapse
That usually means you have too many backups on the sd card, move some to your pc and you should be fine..........
Also make sure there are no spaces in the name of the folders, and that your battery isn't too low
-------------------------------------
Sent via the XDA Tapatalk App
It seems the problem was that i added spaces when i renamed the folders. Removed the spaces and problem fixed . Thanx a lot for all the help!

nandroid backup = factory reset??

i made an nandroid backup with amon ra 2.2.1 with sd-ext included and when i reboot, everything was gone, as if the data got wiped....
i see some broken apps so i geuss something happended with the ext partition
my sd-ext map is empty and i have this ext.tar in my nandroid map
wtf happened!?
shiyou,
You are having too many problems from the beginning. I posted some tips on your first thread, but never heard back. Also, a member recommended doing more research before going forward. The N1 is different from other phones as far as flashing roms.
I would recommend you do this assuming you have a working rom or working backup and sdcard backup. Depending what you have or don't have the below order may vary. Maybe someone can help us there:
1. Take your sd card out of phone--believe you said you have a backup--format it with sdformatter: http://panasonic.jp/support/global/cs/sd/download/sd_formatter20.html
You can dl manual also--mainly select full erase on and size adj on as format options.
Put your backup back on sdcard while still outside phone. Put card back in phone and boot into Amon recovery. Go thru the partition steps to get 1gb ext3 and 0swap.
At this point you need to have a working rom to boot into. If not other steps may be needed.
I use Titanium Backup to manage apps, the paid version. After I flash a new rom, I open TB, or get it from Market if not part of rom. Then I restore all apps with data. NOT system data. Then I delete any old rom apps and do a refresh and then backup all apps and data.
At some point you need to get rid of Rom manager and Clockwork and flash a fresh Amon_Ra 2.2.1 from his site: http://forum.xda-developers.com/showthread.php?t=611829 Before flashing make sure the install recovery file from old revovery is deleted thru Root Explorer, see this link: http://forum.xda-developers.com/showthread.php?p=9414097#post9414097. You don't have to use adb, just Root Explorer. Change permission first to R/W.
You can push the 2.2.1 .img after, downloading to root of sdcard, with Terminal Emulator using these commands:
Open TE and type:
SU
at # type flash_image recovery /sdcard/recovery-RA-passion-v2.2.1.img then hit enter. I usually check md5's with a file explorer. The recovery-RA-passion-v2.2.1.img part above should be the exact name of the img file you downloaded.
2. Before flashing an update to a rom wipe dalvik cache and cache in recovery
3. If flashing a new rom wipe Phone's System with Temasek's System Wipe zip 3X by flashing from recovery. It should be in your download folder.
http://forum.xda-developers.com/showthread.php?t=723844&page=1767
Then wipe Dalvik Cache and anything else that wasn't wiped with System Wipe zip 5X
4. You probably already know, but you can't restore a CWMod backup using Amon_RA or vice versa.
5. Read all the OP pages on the links I posted carefully
This is the way I been doing this for a long time--and rarely need any help or have problems. The system wipe is critical as old files can be left on phone even after a phone data wipe and flashing new rom.
Hope this helps and I haven't left anything out. Not a good typer. If I did--someone will correct me and some things are personal preference. But these have worked well for me.
BTW: If you have no good rom, you may want to dl the latest CM7 RC or nightly to pc and put it on sdcard after you format and put your sdcard backup from pc to phone. Then it is there to flash after card is ready and good recovery installed. You can always put the 2.2.1 on I mentioned after you get rest worked out. But, you gotta get off CWMod 3.0.
You should not use the beta Dark Tremor either, Would dl the the latest non beta.
Also, want the correct gapps for CM7 from OP page, and flashing order is rom/gapps/DT
Ken
I guess I was the member who recommended doing more research. So let me repeat:
I suggest leaving your phone alone and reading A LOT before you start doing something with it.
Yea, Sorry Jack
I was too lazy to go back and look--been a busy day and Fits is giving me a hard time on another thread
rugmankc said:
Yea, Sorry Jack
Click to expand...
Click to collapse
Nothing to be sorry for But indeed, I agreed with your point - someone who's looking for help rooting the phone and doing basic stuff for several days in a row, encountering a lot of problems, is most probably not ready for it, or not willing to read the guides.
You were right Jack on last thread. OP has now abandoned two threads he/she started and again asking for help on a CM7 thread.
No return to either with thanks and still looking for one magical answer, wondering why his phone don't work.
I gave enough advice for a dozen new users and over a year of flashing/backup expertise all in one post.
If he had done it right to begin with and followed some advice, he'd be running smooth. Card could be bad too, don't know.
I am done--
Ken
I love how you two are having this random conversation hahaha. Although I don't understand how the op did a nandroid backup and his phone wiped.. he mustve clicked wipe and confirmed it instead of nand backup. It's nearly impossible. I also decided (out of boredom) to look at his other thread.. Jack you said "Flash a new ROM, wipe your data, and try.
Repeat.
If the problems will still persist - they're in HW and you can't do anything about them." and what HE did: "i tried factory reset but didnt work..." lmfao you sir, are too nice jack! I'll give you two a thanks for the entertianment!
Well, rom development is slowing
Gotta do something
can't tell the same. 2 times i saved by nandroid due to bad flashing issue...

Bootstrap backup with CWM No sdcard/ not sd-ext error?

I think I may have successfully created my first nandroid but am unsure due to what I saw. To borrow from another dev thread to which I cannot post:
Installed - started backup, Got message: No/sdcard/.android_secure found. Skipping backup of applications on ext storage. Same thing happened with cache..
Maybe I'll uninstall.
---------- Post added at 04:48 PM ---------- Previous post was at 04:45 PM ----------
[/COLOR]
Originally Posted by bigfooot
the only thing I find is the progress bar does not progress.
but everything seems to work.
Also the time stamp is off.
I have the same issue​
I have the following files in my clockwork backup folder:
cache.img
data.img
nandroid.md5
system.img​
Am I missing anything?
Thanks,
looks right as to what i have seen man
Wonder if it has anything to do with apps i have on sdcard...
I'm greatly relieved if I have actually successfully created my first nandroid.
Now if i could only look at somebodies udev rules file for XT875, i could feel even safer having adb around. I dont think i'll load any roms without the adb safety net.
Sent from my DROID BIONIC using XDA App

No more backups possible in CWM 5.0.2.1 [Solved]

Hi,
Since 4 days I cannot make valid backups. The last good one is from October 12 and has a size of ~ 1000MB.
Now all backups have a size of ~13 MB. You can see the sizes on the attached hardcopy.
There is a \blobs\-subdirectory with many many files.
I tried to de- and reinstall the Rom Manager, checking permissions and so on, rebooted several times...
I restored the "good" backup, did a new backup and got other sizes of the files but always some with the extension .dup.
Even I installed an older version of RomManager without success.
The recovery system is v6.0.1.4 installed within the RomManager.
I have a LG-P970 with Zeus ROM 7.03.
tramp20 said:
Hi,
Since 4 days I cannot make valid backups. The last good one is from October 12 and has a size of ~ 1000MB.
Now all backups have a size of ~13 MB. You can see the sizes on the attached hardcopy.
There is a \blobs\-subdirectory with many many files.
I tried to de- and reinstall the Rom Manager, checking permissions and so on, rebooted several times...
I restored the "good" backup, did a new backup and got other sizes of the files but always some with the extension .dup.
Even I installed an older version of RomManager without success.
The recovery system is v6.0.1.4 installed within the RomManager.
I have a LG-P970 with Zeus ROM 7.03.
Click to expand...
Click to collapse
You might wanna flash this: http://forum.xda-developers.com/showpost.php?p=22121547&postcount=22
Follow the instructions give there. The new CWM v6 doesnt make full backups anymore everytime, but just backs up the parts, that have been changed. The dup files only contain the information about the files that have been changed and a link to them I think. Look in /sdcard/clockworkmod/blobs. There you can find a lot of folders with the made changes Just check the size of that blob folder.
N00BY0815 said:
You might wanna flash this: http://forum.xda-developers.com/showpost.php?p=22121547&postcount=22
Follow the instructions give there. The new CWM v6 doesnt make full backups anymore everytime, but just backs up the parts, that have been changed. The dup files only contain the information about the files that have been changed and a link to them I think. Look in /sdcard/clockworkmod/blobs. There you can find a lot of folders with the made changes Just check the size of that blob folder.
Click to expand...
Click to collapse
Thank you for answering.
So is it correct that I have a blobs subdir with ~ 1GB files and a small backup directory?
What happens to the \blobs\ dir if I make new backups? I assume then only changed files etc. will be added here?
Do I really need to flash your link if I don't need touch? I read the whole thread
I did not understand all.
tramp20 said:
Thank you for answering.
So is it correct that I have a blobs subdir with ~ 1GB files and a small backup directory?
What happens to the \blobs\ dir if I make new backups? I assume then only changed files etc. will be added here?
Do I really need to flash your link if I don't need touch? I read the whole thread
I did not understand all.
Click to expand...
Click to collapse
The link I provided is for CWM touch 5 only. This version will make the "normal/full-sized" backups. I think you're right about the new update, but I gotta confess, I dont really understand it myself yet... I also didnt yet try to restore such a backup and dont really know, how to delete old ones, if you dont need them anymore, but I hope it all should work fine
If your not sure about the old version, just install the one from the link I provided.
Hope it helped you, if not, you may also PM me.
N00BY0815 said:
I also didnt yet try to restore such a backup and dont really know, how to delete old ones, if you dont need them anymore, but I hope it all should work fine
Click to expand...
Click to collapse
To test:
I made a backup, installed a new app, then after another backup I looked in the blobs dir: only a few subdirs are new, all other remain unchanged.
So all files in blobs are cumulative and important for a restore, but bad for a later extern backup on my pc.
The old method of CWM was better.
Perhaps I will try the link from you.
I was trying a backup and found under "choose backup format" the following points:
- dup (default)
- tar
-
-
So I can choose
I did a backup (dup format) and all is working again.

[Q] Questions regarding compressed recovery img and data on note 4

Hey Everyone,
I am new to XDA forums,(have used it for troubleshooting in the past but just registered today)
I am also new to android and linux, personally i don't use my phone for anything other than calls or games(i mostly do pc's), however my wife does a lot, she has written her own code, does mods, etc...., and we are both stumped. I am asking this on her behalf, due to a terminal illness she has lost the ability to do several things. On April 30th the lollipop update was pushed to her Note 4 (T-mobile US branded) and it wiped out all of her app data as well as her entire SD card. My question is in 2 parts one regarding the TWRP backup for this phone, and another regarding recovering the SD data from this phone(please let me know if i need to break this out into multiple sections of the site).
We have a TWRP backup that was compressed and loaded onto her cloud storage on 4/27/15, and we are unable to figure out how to get TWRP to recognize it without giving an error about the binary code or just not working period. Here is what we have tried(On advice not just from other XDA posts but various android forums as well)
Using TWRP(7zip for unpacking and repacking)
1. Downloaded the TWRP back up into windows
2. Renamed all files of the back up to be .tar, with the exception of boot which was converted to .img
3. Added Meta-Inf file from what was suppose to be stock ROM( she was not running a custom on this phone)
4. Re-archived everything back into Zip and sideloaded.
result : Error in binary code
Using Odin
1. Converted recovery (file only from backup) to md5 using Cygwin
2. Flashed using Odin
Result: Gained back a few programs but no app data or text histories
We have also tried varying versions of this, i.e. converting extra files or renaming extra files and receive the same issue. I am wondering if it is just an issue with the cloud stored compressed backup(or more likely i dont know what im doing)?
Second question comes from above, I was able to recovery all of the data from the SD card(everything was stored here, app data, recovery files, imgs, everything). When recovering the data it split everything up so all the sub peices of each recovery file are spread out is there a way to combine the individual file parts that were recovered from the SD card into functional android files again?
As i mentioned before i have never really dealt with this type of thing before but i want to try and fix this for her as between the 2 issues she has lost 5 years of data.
Thank you so much for your responses.
Hi, what you need to do is put the backup back into the exact same form it was before, an uncompressed, unzipped folder, then put it into the exact directory where TWRP puts backups when it makes them, and then in TWRP choose the option to restore. If you put the backup in the correct directory, TWRP will see it and allow you to choose it to restore it. Basically you just wanna put the backup back where it was before and then restore it in TWRP.
I wasn't sure if you had done this or not. If you have the backup folder with all the contents in their original form, it should work. I've even moved a backup from one phone onto another phone, exact same model of course, and then restored that backup onto the new phone!
I've never converted a backup into another form to be flashed another way, like Odin or as a zip in TWRP. Although I guess it could be possible it seems like it could be pretty messy.
Also if the TWRP backup was for a kit at build it will not restore on the lollipop baseband. You will need to Odin back to the kitkat NK4 build them you should be able to take the data.
Sent from my SM-N910T using XDA Free mobile app
ShrekOpher said:
Also if the TWRP backup was for a kit at build it will not restore on the lollipop baseband. You will need to Odin back to the kitkat NK4 build them you should be able to take the data.
Sent from my SM-N910T using XDA Free mobile app
Click to expand...
Click to collapse
YrrchSebor said:
Hi, what you need to do is put the backup back into the exact same form it was before, an uncompressed, unzipped folder, then put it into the exact directory where TWRP puts backups when it makes them, and then in TWRP choose the option to restore. If you put the backup in the correct directory, TWRP will see it and allow you to choose it to restore it. Basically you just wanna put the backup back where it was before and then restore it in TWRP.
I wasn't sure if you had done this or not. If you have the backup folder with all the contents in their original form, it should work. I've even moved a backup from one phone onto another phone, exact same model of course, and then restored that backup onto the new phone!
I've never converted a backup into another form to be flashed another way, like Odin or as a zip in TWRP. Although I guess it could be possible it seems like it could be pretty messy.
Click to expand...
Click to collapse
Thank you both for the suggestions i will give them a try shortly and i will provide an update on how things go.
Yeah, if you put the backup folder in the right directory, which is either internal or external sdxard/TWRP/BACKUPS/serial #/, you could restore just the data at least and it ought to be mostly ok. You ,might need to clear data in an app here or there if they force close.... or if it's too much then yeah, Odin back to KitKat and restore the desired components of the backup.
YrrchSebor said:
Yeah, if you put the backup folder in the right directory, which is either internal or external sdxard/TWRP/BACKUPS/serial #/, you could restore just the data at least and it ought to be mostly ok. You ,might need to clear data in an app here or there if they force close.... or if it's too much then yeah, Odin back to KitKat and restore the desired components of the backup.
Click to expand...
Click to collapse
Thank you for this, i double checked we had it in the right directory, but it still failed. At first it said something about a missing md5, but i tried again and i was able to get the log for the failure though. (attached below)
Hmm, I looked at the logs trying to make sure you chose to Restore in TWRP and not Install. If so it's possible the backup could have gotten altered or corrupted in the transferring back and forth. If you get it intact as it was, it SHOULD work, but I'm but sure what else to do at the moment. I hope you get it working
Sorry for the delay
Hey Everyone,
Sorry for the delay its been a long week, bad thing after bad thing kept happening. I was able to try your suggestions and i put together some additional information in hope this might help us try and figure it out.
*I must figure out how to recover, texts, contacts, call locks. My default texting app was google messenger.
So I figured I would start with the phone
I am using a Samsung SM-910T on 4.4.4 (build *ANK4) It was pretty Vanilla -> rooted, but running the stock ROM
1. The phone was set to do a full internal backup nightly using the online nandroid backup (by H3r3T1L)
2. Backups were set to be in TWRP backup format and to save to an external SD card, then to compress before being uploaded to google drive
3. Backups were set to delete from SD card after the upload was finished.
What happened
1. When stock 5.0.1 firmware OTA came out i was trying to dismiss the notification but apparently hit "accept" by mistake, causing the system to crash.
2. While restoring the phone, i attempted to download the most recent backup from the google drive and flash the zip to restore my data.
3. This Zip would not install, and i noticed all of the backups uploaded had the same anomally-a few of the files were 0 bytes
4. I downgraded the phone to ANK4 based on the above recommendation but it has made no difference.
5. I still get updated binary error and each time i flash the zip, my OS gets wiped.
6. I have tried instructions to just unzip and flash , to put zips in twrp backup folder, to build new file with meta-inf, etc. and nothing seems to work.
When the SD card got deleted I was able to retrieve some data from the deleted SD card, but don't know where the text messages are located or how to combine them back into a usable format. Or at the very least be able to extract the SMS/MMS history.
I hope this extra information helps. In any way im am desperate to try and fix this for my wife.
I believe you can use Titanium Backup to extract files from a TWRP image. If you can't extract anything from the backup it's either corrupted, in the wrong place, or in the wrong form - that is due to the compression decompression not being compatible (all zip programs are not equal). Best of luck.
BTW, you must restore TWRP files not install them.
Sent from my SM-N910T using XDA Free mobile app

Categories

Resources