Related
I've made two backups on ClockworkMod, yet EVERY time I try to reinstall data, it restarts midway, and when I start my phone up the bootanimation becomes an flashing android logo, what am I doing wrong? Please help!
kamranh3 said:
I've made two backups on ClockworkMod, yet EVERY time I try to reinstall data, it restarts midway, and when I start my phone up the bootanimation becomes an flashing android logo, what am I doing wrong? Please help!
Click to expand...
Click to collapse
Hmm..that's a strange problem.
Did you try to reinstall the CWM??
Edit: I pushed the Thanks Button unfortunately -.-
Every little helps
And I've tried, no such luck, so I'll try an older version and see what happens
EDIT: There's a thanks back!
Okay I've tried a different recovery, no luck
What have I done wrong? I seem unable to make any recovery.
I think the problem may have originated when I installed CWM 3.0.0.5, everything was fine before that
This is just a long shot, but have you tried checking your SD card for errors from your PC? The backup file could be corrupted, and that might fix it.
It would probably be a good idea to copy the /clockworkmod/backup folder from your SD card to your PC before you run the check. If it doesn't help or makes matters worse, you can copy it back.
Also, which version of CWM did you use to make the backup?
preacher65 said:
This is just a long shot, but have you tried checking your SD card for errors from your PC? The backup file could be corrupted, and that might fix it.
It would probably be a good idea to copy the /clockworkmod/backup folder from your SD card to your PC before you run the check. If it doesn't help or makes matters worse, you can copy it back.
Also, which version of CWM did you use to make the backup?
Click to expand...
Click to collapse
I used 2.5.1.3 in both cases, went down to 2.5.1.2 to see if it was linked to the recovery itself, it wasn't
kamranh3 said:
I used 2.5.1.3 in both cases, went down to 2.5.1.2 to see if it was linked to the recovery itself, it wasn't
Click to expand...
Click to collapse
If you look in the /clockworkmod/backups folder on your card, in the folder for the relevant backups, what size is the data.img file? Have you got any earlier working backups you can compare it to? I'm wondering if the backup failed part way through.
I take it you're trying to restore data only using Advanced Restore?
I can't think what else could cause it apart from a damaged sd card or corrupt file, but I'm not a CWM expert.
preacher65 said:
If you look in the /clockworkmod/backups folder on your card, in the folder for the relevant backups, what size is the data.img file? Have you got any earlier working backups you can compare it to? I'm wondering if the backup failed part way through.
I take it you're trying to restore data only using Advanced Restore?
I can't think what else could cause it apart from a damaged sd card or corrupt file, but I'm not a CWM expert.
Click to expand...
Click to collapse
I have looked at the backup is around 1.11GB which is the expected file size, the data.img being around 730mb, it's done this twice, and I've always checked that I've had plenty of space before attempting nandroid, and nothing's ever happened to the sd, i've never moved it or anything
kamranh3 said:
I have looked at the backup is around 1.11GB which is the expected file size, the data.img being around 730mb, it's done this twice, and I've always checked that I've had plenty of space before attempting nandroid, and nothing's ever happened to the sd, i've never moved it or anything
Click to expand...
Click to collapse
I'm not sure what else to suggest besides checking the sd card for errors. There have been some bugs with the HTC 1.72 stock ROM, which affect all custom ROMs based on it, that occasionally cause sd card errors. This is most likely to happen if you connect to your PC with a USB cable, mount the SD card as a drive in your PC, and disconnect the cable without using "eject" in Windows. It might happen at other times as well, I'm not certain.
This is usually fixed by checking the card for errors through your PC. Some people recommend defrag'ing the card, but I think a check for errors should be all that's needed. I'd copy all contents of the card to a folder on your PC first, just so you have a backup.
Otherwise I've run out of ideas, sorry. Hope you get it working.
What I'll do is transfer my backup to my brother's SD card, and then attempting a nandroid then, if that doesn't work then I don't know what will, but I'm 99% sure it's probably due to a problem on my SD card.
Sent from my Desire HD using XDA App
Hope it works, let us know how you get on.
preacher65 said:
Hope it works, let us know how you get on.
Click to expand...
Click to collapse
Well it doesn't seem like option, brother's too stubborn, so I guess I'll have to stick with what I got for now until I can fix this problem, it's really bugging me
kamranh3 said:
Well it doesn't seem like option, brother's too stubborn, so I guess I'll have to stick with what I got for now until I can fix this problem, it's really bugging me
Click to expand...
Click to collapse
You didn't say whether you tried checking the card for errors from your PC, did you try that yet?
CWM created an MD5 checksum for the backup, so it's not very probable r/w errors are the cause of the problem. If the data was corrupted CWM would notice before attempting to restore the data.
But if in doubt you can verify the checksums manually. In the backup directory there's a file called nandroid.md5 it's a text file that contains the hashes for each backup file. Compare those values to the actual checksums. If you need a tool use Hash My Files.
CWM 3 backups aren't backward compatible with CWM 2? Then you could try restoring with CWM 2 and see if that works. Then you'd at least know if it's you phone or a software problem.
This may sound silly but did you upgrade clockwork to 3.0.0.6?
equlizer said:
This may sound silly but did you upgrade clockwork to 3.0.0.6?
Click to expand...
Click to collapse
I tried upgrading to see if it would solve the issue, it didn't.
And as for md5 checksums, it all checks out fine, everything starts to restore fine, and on two of the latest occasions it will not fully restore data, but will restart CWM between restoring. I really don't know what the cause is :/
Hey quick question,
so I make a backup of my system for flashing. Then I move the backup onto a folder to my computer same with my titanium backup folder. So when I wipe and flash a new rom, I have all of my files for my system backup and my titanium backup on my phone. After I restore all of my apps after flashing the new rom, can I move the backup files and leave them on the computer as well as the system backup to save space? Is there anyway that I can still restore the system if it gets stuck in a bootloop - (besides flashing a new stock one)?
basically I want to store the system backup and the titanium backup on my computer so they are safe and because they take up about 4 gb of space on my phone.
I tried to be clear but let me know if I should further explain
Thanks
I wouldn't backup system apps with titanium, because they can vary from rom to rom. As long as you properly wipe your phone before flashing, you shouldn't get bootloops(can still happen). If you get a bootloop, try pulling the battery 1st. If your phone still bootloops, you have to use download mode and ODIN to flash stock ROM.
sent from somewhere
right which I have done before. I just want to know that if my phone does get stuck somewhere (has happened before, and I had to flash a stock rom and lost everything - lost backup) Would I be able to move my system restore and titanium backup files from my computer to my phone to be able to recover?
Basically store backups on computer, then if something happens, be able to transfer them back to phone
Thanks for the help
Generally it's good to leave backups someplace where they won't get easily corrupted or lost. Since the S3 has a microsd slot, sure, keep them on your computer and move them over if necessary.
My SOP is to keep the current backup on the microsd, and store the backups on my computer. Then if I need to reflash/nandroid back, they're there, and if my microsd is corrupted I have a known good backup.
b11aze said:
right which I have done before. I just want to know that if my phone does get stuck somewhere (has happened before, and I had to flash a stock rom and lost everything - lost backup) Would I be able to move my system restore and titanium backup files from my computer to my phone to be able to recover?
Basically store backups on computer, then if something happens, be able to transfer them back to phone
Thanks for the help
Click to expand...
Click to collapse
As long as you can get into your custom recovery after anything happens, backups will work. Make sure to backup system, data, and boot. If not and you have to flash using ODIN, like starting from scratch, you may have issues such as md5 mismatches.
sent from somewhere
ok I was just looking to see if it was possible or not to transfer backups from computer to phone if the phone cant turn on ie. stuck in download mode or recovery mode.
I've found myself stuck trying to flash a ROM. I'm a newbie, this was my first attempt at something like this, I though I read enough about the process but I guess I screwed up something. I will try to be to the point.
Phone: Samsung Galaxy S3 AT&T i747
Rooted phone with Casual, installed ROM Toolbox and purchased the pro upgrade.
installed TWRP 2.5 and made a nandroid backup, the only place this backup existed was in internal storage.
used ROM toolbox to backup user apps and user data
selected cyanogenmod 10.1 RC5 from within ROM Toolbox and there was a requester for gapps and a checked the box for that also. When the DL was complete I installed the ROM queue with those two items and I checked the boxes Wipe Data & Cache and Wipe dalvic-cache.
Phone went to recovery mode (i guess) and appeared to clear the memory and load the new rom, the phone rebooted and I got the cyanogenmod boot screen but then it went to a requester saying:
Unfortunately , the process com.google.process.gapps has stopped.
When you hit ok you get:
Unfortunately, setup wizard has stopped.
this requester never goes away, just keeps popping up when you hit ok.
So I removed the battery and booted the phone in recovery mode and try to restore but the restore nandroid file in not shown. If I hit the center button in the restore window it says "updating partition details" but never returns.
Whenever you power it up normally now you end up in this gapps loop.
My searching suggested I may have tried to install the wrong version of google apps somehow. What are my options for trying to recover from this? Does my backup still exist somewhere?
If process.gapps is your only warning you can try to reflash the gapps zip from here. http://goo.im/gapps/gapps-jb-20130301-signed.zip If this does not fix your problem, you will have to head deeper into the rabbit hold
You can look for your back with a file explorer. Should be in sdcard/TWRP/BACKUPS/******** (random number). If you dont see them here, check your ext-sd in the same location. If you don't see them, they are gone. Do a Nandroid backup now just to be sure you have one. You should chose to back it up to external in TWRP. As for your FC problem, it would appear that you have not wiped fully. You will likely need to factory reset. the problem is this will remove everything. Titanium back up is a great product for situations like this. If you have used it, you can transfer your backup from the internal storage while connected to your pc. Also copy your DCIM folder as it will contain your photos. This is why you will need to do another Nandroid, because worst case scenario, you can just restore this one.
Thanks for the reply. I will try to reflash the gapps file from the external as soon I can download it, the site is having some trouble right now. I made another Nandroid of the phones current state and stored it to external. I did also have Titanium backup and had backups of the whole system with it. Unfortunately they are also only on the internal storage.
Re-installing the gapps zip file off the extSD from within TWRP did the trick. All the data and backups I created are also still there and are now backed up in several places.
Something that compounded the problem was the 64GB sd card I have for the phone. I was not able to mount it on either of my linux mint machines or an XP machine. Some oddness with the exFAT file system on it, I used a 4GB card I had laying around and it worked fine.
Thank you for the help, the phone is now running CM which is what I wanted and I learned a few things too.
theaxis695 said:
Re-installing the gapps zip file off the extSD from within TWRP did the trick. All the data and backups I created are also still there and are now backed up in several places.
Something that compounded the problem was the 64GB sd card I have for the phone. I was not able to mount it on either of my linux mint machines or an XP machine. Some oddness with the exFAT file system on it, I used a 4GB card I had laying around and it worked fine.
Thank you for the help, the phone is now running CM which is what I wanted and I learned a few things too.
Click to expand...
Click to collapse
I just bought a 64GB card as well. You may be having troubles mounting it due to a partition that comes factory in the SD. If this is the case, you can look at post #57 on the following page http://forum.xda-developers.com/showthread.php?t=1915385&page=6
It helped me tremendously.
Hi,
I flashed last night Temasek's CM11 4.4.2 ROM (http://forum.xda-developers.com/showthread.php?t=2596887), wiping user data, caches, etc (I was on a rooted stock 4.1.2 ROM).
Everything is working great so far, I love this ROM, I just noticed a problem that it's quite annoying: it seems that the internal user data file system (which would be the /sdcard folder in my old ROM) is all messed up and replicated. Here;s what happens:
I created a backup of the current ROM with Online Nandroid backup. If I use a file explorer from my phone (X-plore) and go to the "partition" /storage/emulated/0 I can see the backup created in /storage/emulated/0/clockworkmod/backup/.
However, if I connect the phone to my PC and browse the contents, the partition that I see isn't that same partition, it's an older one with older files (for example it has a clockworkmod folder but the backup isn't there, and some folders are different). What;s worse is that I can't find this "old" partition when browsing my phone with X-plore. These are the palces where I've looked at:
- /storage/emulated/0 (shows the partition where the backup I just created went, I can see the backup there)
- With root privileges:
- /data/media (shows an older second partition with different folders)
- /data/media/0 (shows the "right" partition, where the backup is)
- /sdcard (again, shows the "right" partition)
- /storage/sdcard0 (same here, shows the "right" one)
So to sum up, it looks like I see at least 3 diffent partitions:
1. From my PC, I see an older one that I can't see from X-plore (I tried Cyanogenmod file explorer too)
2. From my phone, I see the one that has the backup I just created
3. From my phone too, I see a second old partition (different from the one I see from my PC)
So what I would like to know is:
1. How can I transfer the backup to my PC if I can't see the partition that holds it from there?
2. Is it safe to just delete all those folders in both old partitions? I'm sure they're taking space unnecessarily
Any help would be much appreciated!
After flashing any CM/AOSP Rom. They actually create a different folder set up. That's because of the ability of different users...
You need to apply the restore SD card after downgrade.
Found HERE:
http://forum.xda-developers.com/showthread.php?p=36873319
After that^^^^^^^^^ just make sure you copy everything you want.. Then you can delete all those other folders you don't need.
SENT FROM MY SAMMY i317 USING TAPATALK
Bajanman said:
After flashing any CM/AOSP Rom. They actually create a different folder set up. That's because of the ability of different users...
You need to apply the restore SD card after downgrade.
Found HERE:
http://forum.xda-developers.com/showthread.php?p=36873319
After that^^^^^^^^^ just make sure you copy everything you want.. Then you can delete all those other folders you don't need.
SENT FROM MY SAMMY i317 USING TAPATALK
Click to expand...
Click to collapse
Thanks for the reply! I'll try this as soon as I get home!
Bajanman said:
After flashing any CM/AOSP Rom. They actually create a different folder set up. That's because of the ability of different users...
You need to apply the restore SD card after downgrade.
Found HERE:
http://forum.xda-developers.com/showthread.php?p=36873319
After that^^^^^^^^^ just make sure you copy everything you want.. Then you can delete all those other folders you don't need.
SENT FROM MY SAMMY i317 USING TAPATALK
Click to expand...
Click to collapse
Hey! So it seems that did it!!! Now I can see ALL the contents in the /sdcard partition (X-plore shows it as /storage/emulated/0)
So my question is (I'm still pretty noob at all this): all the files/folders shown there shouldn't be critical for the OS to work, right? They should all be stuff saved by apps, that if they get deleted the worst thing that will happen is that those apps will lose that info, right? I ask because I can recognize most of them, but not all of them, so I'm not sure, and I would like to remove as much stuff as possible.
One file that makes me doubt specially is /sdcard/clockworkmod/download/download2.clokworkmod.com/recoveries/recovery-clockwork-touch-6.0.4.3-t0lteatt.img. Is that the actual CWM recovery that I have in my phone? Or just the installation image that can be removed?
Thank you very much for your help!
I ended up deleting everything from the sdcard partition and restoring the stuff that mattered to me, and everything seems fine now. The only weird thing is that when I create a backup with Online Nandroid backup (which gets stored in /sdcard/clockworkmod/backups), I can't see it when connecting my phone to my PC. I can see everything else in the sdcard except the backup. I've tried unplugging and plugin again the phone, rebooting it, rebooting my PC... but nothing. However, if I zip the backup folder with X-plore, leaving the zip file in the same folder as the backup folder, my PC can see it...
Weird thing but oh well!
My phone is currently totally F'd up and I'm planning to do an RUU but I want to get the pictures off of it first, is there any method of getting them off via TWRP or something? They are all on Internal storage so i can't just take them out and plug them into a computer. I've tried MTP transfer from it but it only allows me to do my SD card, is there some sort of ADB command or something to extract all of my internal storage or a certain folder to my computer? Anything at all? Even besides that?
Yes the internal storage is accessible, not messed up or encrypted or anything. Just don't know how to get the files off it without having a ROM (can't flash any until i RUU).
Don't use an RUU (yet)?
If you can get any ROM to boot, use that ROM to get your pictures. THEN run the RUU. If you can get to a working recovery, this should be doable.
jshamlet said:
Don't use an RUU (yet)?
If you can get any ROM to boot, use that ROM to get your pictures. THEN run the RUU. If you can get to a working recovery, this should be doable.
Click to expand...
Click to collapse
No ROM will boot, or install, adb will not function properly, TWRP reboots randomly, half of the functions in TWRP are causing it to reboot, MultiROM has a couple partitons I think never got removed, it's quite bad. At the moment I am totally stumped at what to do to even consider 'fixing' this besides an RUU. I'm not stupid when it comes to fixing my phone either, I normally have minimal issues when fixing things but this one is just above my level in actually fixing it rather than just doing the simple way out (RUU). Oh and I can't flash anything via TWRP.
Soo in short I just want to get the pictures...then RUU. I have backups on my SD card to restore and if I can get the pictures then I'll already have a full internal storage backup & sd backup to restore if needed. The pics are the only things not fully backed up, i.e why I need/want them. Probably best I do an RUU anyways, I can't uninstall MultiROM to get rid of the partitions so the RUU seems to be my best bet.
S1L3nTShaDoWz said:
No ROM will boot, or install, adb will not function properly, TWRP reboots randomly, half of the functions in TWRP are causing it to reboot, MultiROM has a couple partitons I think never got removed, it's quite bad. At the moment I am totally stumped at what to do to even consider 'fixing' this besides an RUU. I'm not stupid when it comes to fixing my phone either, I normally have minimal issues when fixing things but this one is just above my level in actually fixing it rather than just doing the simple way out (RUU). Oh and I can't flash anything via TWRP.
Soo in short I just want to get the pictures...then RUU. I have backups on my SD card to restore and if I can get the pictures then I'll already have a full internal storage backup & sd backup to restore if needed. The pics are the only things not fully backed up, i.e why I need/want them. Probably best I do an RUU anyways, I can't uninstall MultiROM to get rid of the partitions so the RUU seems to be my best bet.
Click to expand...
Click to collapse
Ouch. Unfortunately, a screwed up partition map is probably only recoverable by fully wiping the internal storage. I inadvertently did something similar to my daughter's Nexus 7, and the only resolution was reloading a factory image from fast boot. (since Google doesn't seem to do RUUs)
Maybe one of the Multi-ROM devs has a better solution?
jshamlet said:
Ouch. Unfortunately, a screwed up partition map is probably only recoverable by fully wiping the internal storage. I inadvertently did something similar to my daughter's Nexus 7, and the only resolution was reloading a factory image from fast boot. (since Google doesn't seem to do RUUs)
Maybe one of the Multi-ROM devs has a better solution?
Click to expand...
Click to collapse
It's more like I have 4 little partitions for the other ROM's that won't get removed unless I do the RUU anyways or at least get the phone functional enough to where I can remove them with MultiROM but as I said I just want the pictures and to rid of it. Once I get them or if I can/can't then i'll fully wipe it and probably do the RUU too. Just want to at least TRY to get them, if not it's whatever but worth a shot.
Oh and the 4 little partitions thing, thats only from what I know of how MultiROM works, I don't actually know 100% for sure if it really creates partitions. Quite sure it does though
Try
adb pull /data/media/0/
it should pull all files from internal storage
make sure you mount data in TWRP first before you run the command
or
you can try to flash TWRP as linked in my sig, it can mount your internal storage as MTP
or
search for qtADB ... it's a pc-android explorer... then browse to data/media/0/
you can copy whatever that you need with its copy function
(you need to mount data in TWRP first)
ckpv5 said:
Try
adb pull /data/media/0/
it should pull all files from internal storage
make sure you mount data in TWRP first before you run the command
or
you can try to flash TWRP as linked in my sig, it can mount your internal storage as MTP
or
search for qtADB ... it's a pc-android explorer... then browse to data/media/0/
you can copy whatever that you need with its copy function
(you need to mount data in TWRP first)
Click to expand...
Click to collapse
Okay thank the spaghetti monster of doom that last one worked, got the pictures extracted safely. I tried getting my entire internal storage just in hopes I could 100% clone my old setup but it just keeps glitching and won't do it. Either way got what I wanted, attempting an RUU now . Thanks for the help!
Oh and just for informational purposes, I was already using his TWRP and that ADB command just did what every other thing I normally do in TWRP does, rebooted my phone after 2 seconds of it. It did manage to get 2 files but they weren't even what I wanted. Maybe if I did it more specifically it would've worked but oh well.
Updaaaate!: Got everything back as it should be via RUU, Nandroid Backup, & backed up Internal Storage from 8/11/14 along with the Pictures you helped me get!