I've got to be doing something wrong (but c'mon, really how can you screw it up?) because this is the second time ClockworkMod (v.3.0.2.4 on my Nexus S) has let me down. First time on my Desire Z, this time on brand new hardware my Nexus S.
When creating the backup, ClockworkMod tells me that the backup was created successfully, but halfway through the restore of said backup (after full data wipe, cache wipe, dalvik wipe) the restore process stops and I'm back at the bootloader with no confirmation of success or failure. Then, when I reboot the system, I'm greeted with the Android setup wizard and a half-restored system.
Two of my last backups that were 'successfully created' fail to restore in the exact same manner.
When I do an advanced restore, the Boot restores OK, the system restores OK, but it's during the data restore it stops. Why is this happening?
I've got 6+GB space free on my storage, space isn't an issue when creating the backup.
This is really disheartening... Any suggestions?
Okay wow, I'm very confused and have been Googling/reading the forums for hours now. I'm a complete noob and here's exactly what I did.
Currently have CWM touch v6 and Cyanogenmod 11
1. I have been running everything for a month with no problems at all.
2. I made a backup of my stock rom before I switched to Cyanogenmod 11, and I've also tested going into it and back to 11 in the past.. I know it works!
3. Today I decided I wanted to go into the the stock rom again and view some old text from my gf.
4. Before going back to my old stock backup, I decided to make a current backup of my Cyanogenmod 11
5. I also decided to make sure that one worked, so I made another backup of my current 11
6. Upon trying to access the backup I ran into a md5 hash error and noticed it wasn't creating a nandroid file for the cyanogenmod backups like it did for the old stock rom backup.
7. I went in and created a new file blank file "nandroid.md5" for both the Cyanogen backups I created.
8. Upon trying to restore again, I now received, "error while restoring /data!"
9. I was able to access the rom, however it only seemed to have loaded a partial amount of my /data ...I even I had to go back through the cyanogenmod prompts as if I freshly installed the rom, but my text messages/apps were all there.
10. I then attempted to wipe everything (using the wipe settings cache/dal/etc in CWM) and install the stock rom (since I know it works). Again I received the, "error while restoring /data!". But, again the same story, it loaded the stock rom, but with partial data and as if I freshly installed it.
11. I found online the problem could be due to the partition size not being able to handle the backup size (and my backups are over 600mb)..I deleted the stock rom (taking up 1gb) and again tried to install my Cyanogenmod 11 backup, to again be greeted with, "error while restoring /data!"
QUESTION 1:. I've read that using the Titanium app or nandroid manager can help alleviate the issue by restoring items, but how can I solve this annoying "error while restoring /data!" error?
QUESTION 2: I have the entire backup folder pulled from adb on my desktop, would it be advisable to use the format /Data and /Data/Media option on CWM and then push the Cyanogenmod 11 backup back into my phone and then try restoring? I've also read someone was able to factory restore their phone from settings, then try restoring the rom.. is this advisable?
Thanks in advance for the help, I have a headache
long story short: just to assure myself for everything to go smoothly while installing Lineage OS 14.2 i stupidly decided to tick the 'system' box on factory reset for TWRP along with the standard data, cache and dalvik. now i tried to system restore the backup i have on my sd card and it says error 225 at the end and its stuck on boot!
what have i done wrong? can you no longer restore if you tickbox the 'system' thing; does the backup option not backup literally everything? did my files corrupt? will the 'format data' option (deleting everything on internal storage), then trying to restore fix it? HELP.
phone is a Samsung Galaxy J3 2016 (J320fn) fwiw
idklol123 said:
long story short: just to assure myself for everything to go smoothly while installing Lineage OS 14.2 i stupidly decided to tick the 'system' box on factory reset for TWRP along with the standard data, cache and dalvik. now i tried to system restore the backup i have on my sd card and it says error 225 at the end and its stuck on boot!
what have i done wrong? can you no longer restore if you tickbox the 'system' thing; does the backup option not backup literally everything? did my files corrupt? will the 'format data' option (deleting everything on internal storage), then trying to restore fix it? HELP.
phone is a Samsung Galaxy J3 2016 (J320fn) fwiw
Click to expand...
Click to collapse
If you wiped everything, you can't just restore the system only, the default restore that restored all partitions that were backed up, is what you need.
Or, you can boot into TWRP, then select the wipe option, then select advanced wipes, then select the system, data, cache and dalvik cache partitions then swipe the slider to wipe. After the wipe is finished, flash your LineageOS ROM and gapps.
After flashing the ROM and rebooting the device, if you want to try to restore the backup that you made, boot into TWRP, when retoring a backup, it isn't necessary to do any kind of wipes because it automatically formats the partitions before restoring the backed up data to each partition.
Sent from my LGL84VL using Tapatalk
Droidriven said:
If you wiped everything, you can't just restore the system only, the default restore that restored all partitions that were backed up, is what you need.
Or, you can boot into TWRP, then select the wipe option, then select advanced wipes, then select the system, data, cache and dalvik cache partitions then swipe the slider to wipe. After the wipe is finished, flash your LineageOS ROM and gapps.
After flashing the ROM and rebooting the device, if you want to try to restore the backup that you made, boot into TWRP, when retoring a backup, it isn't necessary to do any kind of wipes because it automatically formats the partitions before restoring the backed up data to each partition.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
i solved. it turns out i just didnt have enough memory to extract the system restore into internal storage.
what do you mean though? the only problem im having in the stock OS now is that my phone will randomly stop charging and/or display different battery %'s (one time it said i had 89% for 15 minutes straight without charging it. i rebooted it and then it said it was at 94%), as well as im unable to manually update (says my original OS was modified in a non authorized manner)
is there anything i can do in TWRP in regards to either of these things? maybe re flash stock OS? (how would i go about doing that without losing all my data?)
Hello,
I just updated the rom Evolution X 11 on my Xiaomi Mi 9T Pro after using an older version for about half a year.
Now my phone does not boot anymore, its stuck in recovery (TWRP). Also all data seems to be encrypted and TWRP is not asking for a password.
Is there a way to get my phone to boot again or at least backup my data before I do a full wipe?
You should always do a full twrp backup before messing with roms.
The best solution would be to backup the "Data" and "Internal Storage" partitions. Data contains all apps, their appdata and settings, while internal storage contains all of your own files (photos, videos etc.). After you back these up, wipe your phone (system, data, cache, dalvik) and flash the version of evolution x you were using previously. Now restore data and internal storage and your device should be back to normal.
If you get a bootloop while booting after restoring data and internal storage, then wipe the device again and this time flash evolution x, but only restore internal storage. This way, it should boot and you will be able to recover your files, though your apps will be gone.
If you only restore internal storage then it will no doubt boot up and you will have access to your files, but since you'll have already backed up the important stuff (data + internal storage), you might as well try restoring data as well, as there is no harm, and if the phone boots correctly after restoring both partitions, your phone will be as it was before your updated your rom.
This happened a while back to me with my J5, the issue was that I made a full TWRP backup, then began to test other roms. After I was done, I tried to restore my backup, but it would constantly fail. I sat down for a while, confused and sad about how my TWRP backup had failed me. I tried every solution I could think of, eventually this solution I've mentioned in the above paragraph came to my mind. Thank god for putting it into my mind, otherwise I would've lost a lot of stuff (mainly whatsapp chats which werent backed up, and a lot of apps which I took the time to pain-stakingly configure in the best way for my device).
Anyways, enough of my story, hope this helps you out! If it does, message back here and let us know, and also mark my post as the solution if it was able to help you, so that anyone else who stumbles upon this thread can be saved too!
Cheers!
PhotonIce said:
You should always do a full twrp backup before messing with roms.
The best solution would be to backup the "Data" and "Internal Storage" partitions. Data contains all apps, their appdata and settings, while internal storage contains all of your own files (photos, videos etc.). After you back these up, wipe your phone (system, data, cache, dalvik) and flash the version of evolution x you were using previously. Now restore data and internal storage and your device should be back to normal.
If you get a bootloop while booting after restoring data and internal storage, then wipe the device again and this time flash evolution x, but only restore internal storage. This way, it should boot and you will be able to recover your files, though your apps will be gone.
If you only restore internal storage then it will no doubt boot up and you will have access to your files, but since you'll have already backed up the important stuff (data + internal storage), you might as well try restoring data as well, as there is no harm, and if the phone boots correctly after restoring both partitions, your phone will be as it was before your updated your rom.
This happened a while back to me with my J5, the issue was that I made a full TWRP backup, then began to test other roms. After I was done, I tried to restore my backup, but it would constantly fail. I sat down for a while, confused and sad about how my TWRP backup had failed me. I tried every solution I could think of, eventually this solution I've mentioned in the above paragraph came to my mind. Thank god for putting it into my mind, otherwise I would've lost a lot of stuff (mainly whatsapp chats which werent backed up, and a lot of apps which I took the time to pain-stakingly configure in the best way for my device).
Anyways, enough of my story, hope this helps you out! If it does, message back here and let us know, and also mark my post as the solution if it was able to help you, so that anyone else who stumbles upon this thread can be saved too!
Cheers!
Click to expand...
Click to collapse
Thank you for your help but backing up the data and internal storage doesnt seem possible right now because all the data is encrypted in TWRP...
If you can't backup anything, then wipe system, cache and dalvik, and flash the version of evolutionx you were previously using. Then boot, it should be fine. If it wont boot (give it some time, it will take the time of a fresh install), then this time wipe system+data+cache+dalvik, then flash whichever rom you like and you'll be able to access the files.
You can also try using platform tools and fastboot or adb ( i dont remember exactly which one) to copy the filess from your phone onto your pc.
Sorry if this doesn't apply to your situation, I've never used a phone which has been encrypted, as such I have no experience with them.
PhotonIce said:
If you can't backup anything, then wipe system, cache and dalvik, and flash the version of evolutionx you were previously using. Then boot, it should be fine. If it wont boot (give it some time, it will take the time of a fresh install), then this time wipe system+data+cache+dalvik, then flash whichever rom you like and you'll be able to access the files.
You can also try using platform tools and fastboot or adb ( i dont remember exactly which one) to copy the filess from your phone onto your pc.
Sorry if this doesn't apply to your situation, I've never used a phone which has been encrypted, as such I have no experience with them.
Click to expand...
Click to collapse
That sounds like a good idea. I found the old version on my PC.
Now I just need a way to install it... because twrp cant read the file. I tried with adb sideload but that results in an error for some reason. Flashing Magisk for example with adb sideload is possible.
Edit: Got it to work by using a tool called "Large Address Aware". Now waiting for the results...
PhotonIce said:
If you can't backup anything, then wipe system, cache and dalvik, and flash the version of evolutionx you were previously using. Then boot, it should be fine. If it wont boot (give it some time, it will take the time of a fresh install), then this time wipe system+data+cache+dalvik, then flash whichever rom you like and you'll be able to access the files.
You can also try using platform tools and fastboot or adb ( i dont remember exactly which one) to copy the filess from your phone onto your pc.
Sorry if this doesn't apply to your situation, I've never used a phone which has been encrypted, as such I have no experience with them.
Click to expand...
Click to collapse
This did not help unfortunately... Im still in the same recovery-bootloop and my data is still encrypted.
It's probably still bootlooping as the data partition got modified when you flashed the newer version of evolutionx, and now it will not work with the old one. You can try wiping system+data+cach+dalvik and then flashing any rom of your choice. This will give you access to your internal storage (photos, media etc), but it will remove your apps and their settings. Whatsapp images are stored in the internal storage so you won't need to worry about those.
Again, this is risky, as it may not work (I don't know much about encryption), or you might still not be able to access your files after flashing the new rom. Proceed at your own risk.
PhotonIce said:
It's probably still bootlooping as the data partition got modified when you flashed the newer version of evolutionx, and now it will not work with the old one. You can try wiping system+data+cach+dalvik and then flashing any rom of your choice. This will give you access to your internal storage (photos, media etc), but it will remove your apps and their settings. Whatsapp images are stored in the internal storage so you won't need to worry about those.
Again, this is risky, as it may not work (I don't know much about encryption), or you might still not be able to access your files after flashing the new rom. Proceed at your own risk.
Click to expand...
Click to collapse
Thank you for still helping me out but I already did a full reset yesterday. I did not lose much except for the time setting it all up again.
I still dont really get the point of encrypting all your data if you cant decrypt it even if you know the password...
I need help. Problem in TWRP latest version. I will make a backup - I will connect everything that is needed, including data, system, etc. TWRP initially reports that the backup will take place without the data of the internal storage. After the backup is complete, TWRP reports that the backup was successful. After restarting, the MIUI logo will appear after a while, but the system will not boot. I don't understand the reason.
Benoni1 said:
I need help. Problem in TWRP latest version. I will make a backup - I will connect everything that is needed, including data, system, etc. TWRP initially reports that the backup will take place without the data of the internal storage. After the backup is complete, TWRP reports that the backup was successful. After restarting, the MIUI logo will appear after a while, but the system will not boot. I don't understand the reason.
Click to expand...
Click to collapse
System restore cannot work on a different rom.