Database Users

Cannot restore or create Nandroids from phone...

Ok,so I've tried alot of things to try to get this to work.I have adb working and have created a backup through there,but that's not my problem.I need to be able to do it on my phone like usualy because I'm not going to have access to have a PC after tomorrow.I don't know how this has happened but I flashed DCv2 (not saying anything is wrong with it) and wiped everything,including sd card.I assume that when I formatted sdcard it must of jacked something up.Any ideas? Please don't ask the usual questions,as I have done about 20 different things in 20 different orders to try to correct this.So I cannot create a Nandroid+ext backup,I can't restore a Nandroid backup,but for some reason I can make a regular nandroid backup (minus the ext).But that doesn't help as I obviously cannot even restore them.

I'm having same problems after DC..............................

MrTrip said:
I'm having same problems after DC..............................
Click to expand...
Click to collapse
Atleast I know its not just me going insane over here

casperlt1 said:
Atleast I know its not just me going insane over here
Click to expand...
Click to collapse
It happened after 1.1, I cannot backup or restore. It kicks the error about running it via adb. At first it was a power issue, now its constant.

MrTrip said:
It happened after 1.1, I cannot backup or restore. It kicks the error about running it via adb. At first it was a power issue, now its constant.
Click to expand...
Click to collapse
Yea,just RUU'd (1st time doing so) and going to try to go back to DC once he gets that update out.Till then I'll just roll with my stock-ness.

casperlt1 said:
Yea,just RUU'd (1st time doing so) and going to try to go back to DC once he gets that update out.Till then I'll just roll with my stock-ness.
Click to expand...
Click to collapse
There is a PRI fix now for DC 2.0r2

Figures....
Did that fix your problem?

About to find out...

Backup worked after PRI fix and flash to DC 2.0r2

Restoring CWM backup leads to splash loop

I'm using: NexusHD2-ICS-4.0.4-CM9-HWA V2.4
Something went wrong on my phone so I decided to restore a backup. I had one from 2 weeks ago. After the restore completed, I rebooted my phone. It was stuck on the ROM splash screen and never got past that. I left it running for 20 minutes. I tried clearing /cache and dalvik-cache, with no luck. If I format /data then it works, but then of course all my data is gone.
Luckily I had a previous backup which did work.
I'm nervous about nandroid backup/restore. Can I trust it? It only happened for this particular backup, but why would it happen at all? There were no MD5 sum errors at all.
Any advice would be useful.

frostinide said:
I'm using: NexusHD2-ICS-4.0.4-CM9-HWA V2.4
Something went wrong on my phone so I decided to restore a backup. I had one from 2 weeks ago. After the restore completed, I rebooted my phone. It was stuck on the ROM splash screen and never got past that. I left it running for 20 minutes. I tried clearing /cache and dalvik-cache, with no luck. If I format /data then it works, but then of course all my data is gone.
Luckily I had a previous backup which did work.
I'm nervous about nandroid backup/restore. Can I trust it? It only happened for this particular backup, but why would it happen at all? There were no MD5 sum errors at all.
Any advice would be useful.
Click to expand...
Click to collapse
I've had an issue only once with CWM backup where my data from the ROM was lost but the ROM itself flashed fine. I suspect though that I actually had to reboot a few times more before giving up so quickly, because somehow the wallpaper was still kept and I've found on occasion that my data from a ROM restore/update slowly comes back after a few reboots. Anyway, as for your issue, did you change partition sizes between the time you made a backup and when you tried to restore it? I'm using NexusHD2 and I know that the required partition sizes have changed quite a lot between the ROMs.

Nigeldg said:
I've had an issue only once with CWM backup where my data from the ROM was lost but the ROM itself flashed fine. I suspect though that I actually had to reboot a few times more before giving up so quickly, because somehow the wallpaper was still kept and I've found on occasion that my data from a ROM restore/update slowly comes back after a few reboots. Anyway, as for your issue, did you change partition sizes between the time you made a backup and when you tried to restore it? I'm using NexusHD2 and I know that the required partition sizes have changed quite a lot between the ROMs.
Click to expand...
Click to collapse
I did not change the partition size at all. The backup before this one worked fine, so it can't be that. I also just did a new backup of today, and restored it. It worked at the first boot and didn't take extra time. I then tried restoring the broken backup again but ONLY data, and again I got a splash screen loop. I doubt multiple reboots will help, but I did try that.
I have an urge to mount the data backup and slowly take out folders until I find out the cause. If not for anything else, just out of my own curiosity.

Nigeldg said:
I've had an issue only once with CWM backup where my data from the ROM was lost but the ROM itself flashed fine. I suspect though that I actually had to reboot a few times more before giving up so quickly, because somehow the wallpaper was still kept and I've found on occasion that my data from a ROM restore/update slowly comes back after a few reboots. Anyway, as for your issue, did you change partition sizes between the time you made a backup and when you tried to restore it? I'm using NexusHD2 and I know that the required partition sizes have changed quite a lot between the ROMs.
Click to expand...
Click to collapse
I am facing exactly the same problems...
In same cases i got bootloops when restoring a Backup, in other cases i can boot after restoring but then my data is gone and i am asked to configurate my phone again with the wizard...
I never tried to boot several times if the data comes after some tries...
Btw I also didn't change the partitions...is it possible that it has something 2 do with link2sd?

In that case (@OP) I'm guessing its just a broken backup. This is why I always use Titanium as well. It takes up less space and you can restore it on almost any ROM.
Sent from my NexusHD2

Are you using an A2SD script? or do you have an ext partition?
You may have resized it, you can also try formatting it.

Nigeldg said:
I've had an issue only once with CWM backup where my data from the ROM was lost but the ROM itself flashed fine. I suspect though that I actually had to reboot a few times more before giving up so quickly, because somehow the wallpaper was still kept and I've found on occasion that my data from a ROM restore/update slowly comes back after a few reboots. Anyway, as for your issue, did you change partition sizes between the time you made a backup and when you tried to restore it? I'm using NexusHD2 and I know that the required partition sizes have changed quite a lot between the ROMs.
Click to expand...
Click to collapse
Marvlesz said:
Are you using an A2SD script? or do you have an ext partition?
You may have resized it, you can also try formatting it.
Click to expand...
Click to collapse
I use Link2SD, i have ext4....i didn't change anything in the SD Card Layout since first install of the Rom and updated several times without any problem...

[Help] TWRP reboots during restore

TWRP 2.5.0.0 reboots my device while performing a restore. It usually happens during the DATA phase. I've tried two different restores and the same thing happens. Thanks
If you need more detail, i'll do my best to provide.

sorryihaveaids said:
TWRP 2.5.0.0 reboots my device while performing a restore. It usually happens during the DATA phase. I've tried two different restores and the same thing happens. Thanks
If you need more detail, i'll do my best to provide.
Click to expand...
Click to collapse
I've actually been getting random freezes and reboots in TWRP myself, in the last 2 weeks or so, since I've gone flash-crazy. Have you been flashing a lot?

dibblebill said:
I've actually been getting random freezes and reboots in TWRP myself, in the last 2 weeks or so, since I've gone flash-crazy. Have you been flashing a lot?
Click to expand...
Click to collapse
I wouldn't say flash-crazy, but i've tried two different roms in the past two days. It's not really freezing either. It will just start to restore, make it half way through, and reboot. My rom will be restored but none of my data.

sorryihaveaids said:
TWRP 2.5.0.0 reboots my device while performing a restore. It usually happens during the DATA phase. I've tried two different restores and the same thing happens. Thanks
If you need more detail, i'll do my best to provide.
Click to expand...
Click to collapse
Yep, seems to be happening a lot. One suggestion was to revert to 2.4 or even 2.3.3.0. I tried that, and thought the problem was solved, but then it happened again, so I figured what the hell, I'll go back to 2.5.
You're right, it always happens during the data restore, but so far the second attempt at restoring always succeeds, so it's more annoying than anything. I can't recall it ever happening on my phone, though, so I wonder if it's a device issue. Also my phone is running JB 4.1.2 and my N10 is on 4.2.2.
Sent from my Nexus 10 using Tapatalk HD

Ive noticed this problem as well. Hopefully it will be fixed in later releases.

brGabriel said:
Ive noticed this problem as well. Hopefully it will be fixed in later releases.
Click to expand...
Click to collapse
So yesterday I went to flash a new ROM and TWRP froze immediately after doing a Factory Reset Wipe. Nexus kept bootlooping and then getting stuck on the TEAMWIN screen. Was able to get into the bootloader and flash the stock image and unroot through the Nexus Toolkit. I lost all my data though. So my question is, if you can get to bootloader mode and the toolkit recognizes it in bootloader mode, can you recover data without having to do what I did and wipe the device? For future reference sake. God I need to get better about backing up my data on my PC.

Anyone found the solution to this? I am not able to restore my data ( During the resotre in TWRP it goes blackscreen and then just reboots. I've triel like 10 times already..

ky3bmu4 said:
Anyone found the solution to this? I am not able to restore my data ( During the resotre in TWRP it goes blackscreen and then just reboots. I've triel like 10 times already..
Click to expand...
Click to collapse
I had the same issue. Its most likely a corrupt backup and can't be solved. But if you've successfully restored that backup before try reflashing the recovery. Just a tip that somebody else gave me. Use philz cwm touch recovery. It has no issues and more reliable then other recoveries.
Sent from my Nexus 10 using xda app-developers app

abdel12345 said:
I had the same issue. Its most likely a corrupt backup and can't be solved. But if you've successfully restored that backup before try reflashing the recovery. Just a tip that somebody else gave me. Use philz cwm touch recovery. It has no issues and more reliable then other recoveries.
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
Yes, i'm thinking the same. Maybe it also because the backup was huge (maybe like 4 gb).
But I am not really sure if it is corrupted because the system restores fine and data do not, but it fails in different places, i.e. it may reboot in 30 seconds and may reboot in 2 minutes...

twrp recovery

Im trying to go a backup of my rom and when I go into recovery to do the backup it says not enough space . I am backing it up to a 64 gb sd card with obee 39 of gb left. After a couple of times I looked at the data and it was at somthing 750000mb on datawhich is almost 70gb of data which is impossible

scotty25 said:
Im trying to go a backup of my rom and when I go into recovery to do the backup it says not enough space . I am backing it up to a 64 gb sd card with obee 39 of gb left. After a couple of times I looked at the data and it was at somthing 750000mb on datawhich is almost 70gb of data which is impossible
Click to expand...
Click to collapse
this happened to me. Unfortunately i gave up and ended up reflashing the rom i was using.
I originally tried to just flash twrp via odin and the same problem would happen. I ended up just wiping and installing everything from scratch. Weird thing was that it happened again. I did a final wipe and after i would flash one thing i would make a backup. Now i don't have the issue. Originally it said i had 7tb of /data.

scotty25 said:
Im trying to go a backup of my rom and when I go into recovery to do the backup it says not enough space . I am backing it up to a 64 gb sd card with obee 39 of gb left. After a couple of times I looked at the data and it was at somthing 750000mb on datawhich is almost 70gb of data which is impossible
Click to expand...
Click to collapse
And you selected the sdcard as the backup location? It defaults to internal. I know it is reading the data size wrong from what you posted but thought I would check to make sure.

That is correct. But how do I fix the data so I can backup my roms

Please read forum rules before posting
Questions and Help issues go in Q&A and Help section
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator

all i know is that TWRP has some major issues...and ill probalby be going back to CWM
even the timestamps are way off

Anyone else have problems with TWRP 2.6.0.0 locking at the splash screen? Its really annoying. I went back to TWRP 2.5.0.2 for the time being until this can get worked out.

raxxid said:
Anyone else have problems with TWRP 2.6.0.0 locking at the splash screen? Its really annoying. I went back to TWRP 2.5.0.2 for the time being until this can get worked out.
Click to expand...
Click to collapse
how did you upgrade to 2.60 ??
try directly from goo manager
or if you are upgrading from twrp zip file then make sure you wipe/dalvik first
i am on 2.6 upgraded from 2.5 works great no problem what so ever

saj070 said:
how did you upgrade to 2.60 ??
try directly from goo manager
or if you are upgrading from twrp zip file then make sure you wipe/dalvik first
i am on 2.6 upgraded from 2.5 works great no problem what so ever
Click to expand...
Click to collapse
I have been trying both methods. Though I never tried wiping dalvik. I figured recovery would be separate from all that stuff but it does seem to happen more when I do a reboot into recovery from cm10.1. I'll give it a shot. While I like the additions in 2.6.0.0 it does lack the polish of 2.5.0.2 so I may end of staying with that release long term until a maintenance release is made for 2.6.0.0.

cwm recover not recognizing restore files

I recently rooted my phone and tried a few different roms. I'm currently on cyanogen mod 10.2. I used cwm to backup my original ROM. I copied the backup file to my computer and uploaded it to my dropbox. I formatted my SD card since it had a lot of junk on it. I copies them back and now they aren't being recognized. This is my original stock ROM and since this is my first time rooting I really want to keep a stock ROM on hand for easy access incase I mess something up and need my phone to work properly. Thanks for any help. Its also a Samsung s4 i337m from fido.

can you see the backup and it's just not letting you restore it or can you not see the backup at all?
i'll tell you to keep researching and troubleshooting but if all else fails, odin back to stock, reroot, install cwm and make a new stock backup again.

Its not appearing in cwm at all unless i have a restore that was on it post format and not copied off the computer. Like if I make a backup of my current ROM the stock one will appear and just hang in checking md5. If there are no backups other than the original stock one it isn't being recognized. Also it worked before I formatteebthe SD card.

when you formatted the card and then replaced the cwm backup, where did you place the backup?
for example: 0/clockworkmod/backup, /clockworkmod/backup, etc.
if you make a backup now, where does it save the new one?
i'm just running through the bases here.

Sorry I don't know the exact locatiotion but I just dragged and dropped the "Clockworkmod" That cwm created when I made my first restore to my PC. Formatted the SD card and just dragged and dropped it back to the SD card. The new restore saves in the same folder also.

i'm assuming they're both in something like sdcard1, extSdCard or external_sd /clockworkmod/backup.
if so, and you didnt change cwm versions (i.e. from 6.0.3.6 to 6.0.4.4), then something may have been corrupted when moving the backup folder back and forth.

Yes that seems about right. I didn't change anything on cwm, unless my ROMs did. If it is corrupted will it just hang indefinitely or is there a chance it can work? And is there any other way to do a restore?

i'm no recovery expert but if your backup is corrupt than i dont imagine there's a fix for it.
i accidentally deleted my stock backup a couple phones ago. in order to have a fully stock backup on the sd card again (in the event i needed/wanted to restore to the original factory setup), i had to odin back to the stock firmware and start over.

Do you know any good guides on how to do that?

michael74195 said:
Do you know any good guides on how to do that?
Click to expand...
Click to collapse
Try to re-downloading from drop box. Could have gotten corrupted during the download process.

Download it straight from dropbox to the SD card through the phone?

michael74195 said:
Download it straight from dropbox to the SD card through the phone?
Click to expand...
Click to collapse
yup

Alright I will try it when I get home so I don't kill my data.

michael74195 said:
Alright I will try it when I get home so I don't kill my data.
Click to expand...
Click to collapse
true story.
report back. cheers

Nope, no luck. It just hangs at checking MD5 Sums. I tried the backup i made for foxhound 2.0 and it did the same thing.
edit: It worked it was just hanging for a good 15 minutes though.

michael74195 said:
Nope, no luck. It just hangs at checking MD5 Sums. I tried the backup i made for foxhound 2.0 and it did the same thing.
Click to expand...
Click to collapse
Can you have cwm not check for the md5? It's been awhile since I've used cwm. I use twrp.
Edit, doesn't look like you can. I just flashed cwm to see. Was the foxhound nandroid one you just made and it still doesn't restore?

jd1639 said:
Was the foxhound nandroid one you just made and it still doesn't restore?
Click to expand...
Click to collapse
yeah, thats what i was gonna ask: if you've made one just now and tried restoring it.

Ok thanks for the help but the problem resolved itself after letting ti hang until it did something. It worked after about 15 minutes.
edit: I just rooted the phone a few days ago and I'm all new to this, so i figured after it not doing anything for 5 mins with the dead android on the screen was bad. Thanks for the help.

michael74195 said:
Ok thanks for the help but the problem resolved itself after letting ti hang until it did something. It worked after about 15 minutes.
edit: I just rooted the phone a few days ago and I'm all new to this, so i figured after it not doing anything for 5 mins with the dead android on the screen was bad. Thanks for the help.
Click to expand...
Click to collapse
Good, yea a restore and reboot can take longer than you think. And waiting seems like forever when you're expecting it to boot. You'll get used to it.