I was in stock 5.0 ROM with TWRP recovery, and wanted to try CyanogenMod 12.1.
Did backup in TWRP and then flashed CM12. All went well, but eventually I wanted to go back to my stock ROM.
Entered TWRP, did wipes and went to "Restore", my backup wasn't showing. So it wasn't detected.
Connected my phone to the PC and saw that somehow after flashing CM12 all my /sdcard content went to a "0" folder...
So my backup is in /sdcard/0/TWRP and the recovery is looking up in /sdcard/TWRP, therefore it can't find it.
So my question is what I'm supposed to do? Take all the content of the "0" folder and move it to the root of sdcard? Or just the backup and after restoring all the content will move alone, or will be on /0 but will show as in root?
Also, this will happen with every ROM or it's just CM issue?
Appreciate any help.
Edit: after moving the backup to /sdcard/TWRP and restoring the screen appeared black after boot and another "0" folder have been created inside the previous "0", so my sdcard content is now in /0/0 folder.
Related
Hello, I have a few questions regarding the TWRP recovery particularly the NANDroid backups, please bear with me as I am new to this. I have made a few backups using twrp but I want to put them onto my pc in order to save space however when I plug my phone into my pc I don’t see the TWRP folder unless I boot into recovery and then plug it in. Is this how it is supposed to be?
I wanted to test out restoring a backup that I had saved onto my pc onto my device. To test this out I created a backup through TWRP booted into recovery plugged in my device into my computer copied the backup file located in the TWRP folder and then deleted it from my device. Next I wanted to copy the backup that I just put on my pc back onto my phone and then eventually restore it through TWRP. However I only get as far as copying it from my device onto my pc. When I try to copy it back into the TWRP folder on my device I get an error saying “cannot copy data.ext4.win000 its file size is larger than the device limit” The backup is 4.83gb and I have 10.7gb free. Does anyone know why this is happening?
Last question, seeing as a NanDroid backup is basically an image of your whole device, let’s say I am selling my device and I don’t want the buyer to have any way of accessing any of my data. Would the deletion of my backups, factory reset and an advanced wipe where I select all the partitions to be wiped be enough?
Thank you in advance for your help!
1 - no. You're on lollipop i presume. Read my /sdcard thread in general
2 - sounds like its being mounted as FAT with 4GB file limit. Try web push method
3 - not really. You'd be best overwriting the data partition with files first.
I've taken some backups using online nandroid backup (default settings,which makes a CWM type backup). But now, when I try to restore it using recovery, it is not getting detected.
I did ensure I copied it to correct folder. I'm also able to see it and restore content using nandorid manager. But ,when I'm inside recovery the restore from sdcard1 is not detecting that.
Any ideas, solutions,pointers?
Oneplus with stock rom+unlocked bootloader.
philz_touch_6.59.0-bacon
I had created a nandroid backup on CWM before flashing a rom which failed, causing me to adb sideload back to my old ROM. But before doing so I attempted to restore the backup (which also failed). But after booting in, i noticed that I had multiple 0 folders in my internal storage. Now the available storage on my device does not add up. Also when I open the device on my computer, there is a 8gb zip file that always appears under the "0" folder. Even if I delete it, it returns after rebooting and it cannot be opened or copied. I believe the backup is hidden within this folder but I am not sure how to delete it. Does anyone have any ideas on how I can fix this issue?
Asaad123 said:
I had created a nandroid backup on CWM before flashing a rom which failed, causing me to adb sideload back to my old ROM. But before doing so I attempted to restore the backup (which also failed). But after booting in, i noticed that I had multiple 0 folders in my internal storage. Now the available storage on my device does not add up. Also when I open the device on my computer, there is a 8gb zip file that always appears under the "0" folder. Even if I delete it, it returns after rebooting and it cannot be opened or copied. I believe the backup is hidden within this folder but I am not sure how to delete it. Does anyone have any ideas on how I can fix this issue?
Click to expand...
Click to collapse
First off, flash TWRP instead of this old CWM. Then try to delete your file of 8Gb (which is VERY high for a nandroid...).
I've been having issues flashing the latest Lineage OS. I restored this time and for some reason it moved alot of the system folders into a folder named "0". I didn't think anything of it. So I tried flashing LOS again, still did not work. So I go to restore my phone but when I go to the restore section there is nothing there anymore. I know the files are still there. If I go to the "install" section I can see the main system folder and even the "backup" folder in the "twrp" folder along with my actual backup. How do I get TWRP to see my back up now that all the system files are moved to folder "0"?
Hello
I wanted to install Syberia A12 from stock A11 and I got stuck somewhere in the process.
So I'm stuck with the internal storage on the phone (not backed up) that is inaccessible since it's encrypted and the rest of the partitions backed up on the pc using adb backup (a single .ab file).
In theory I should restore the partitions to the phone and I should be able to access everything and boot as it was before, right? However now I have the syberia ROM installed and I'm not rooted anymore (and won't boot).
Can I restore /system like this?
What I care about is access the internal storage, what can I do?
I tried restoring the entire .ab file, however it gets stuck at "restoring efs2" and I should only try to restore /data and /system but I can't select specific partitions being a adb backup with twrp.
All tools I tried to extract the content fails.