Hello.
After a successful backup of Android 4.2 and a failed flash of Android 4.4, I am unable to see the contents of my micro SD card from within TWRP 2.7.0.0. So, I am unable to restore my backup.
Thoughts?
Thanks!
stanelie said:
Hello.
After a successful backup of Android 4.2 and a failed flash of Android 4.4, I am unable to see the contents of my micro SD card from within TWRP 2.7.0.0. So, I am unable to restore my backup.
Thoughts?
Thanks!
Click to expand...
Click to collapse
Flash your stock BOOT.IMG with Sp Flash Tool , then restart TWRP and restore your backup
Thanks, I did something like that in the end and it fixed my problem.
Related
This is my first thread after a years here without any problems to flash on my i9300.
My condition:
1. Previously use CM 10.1
2. Update to CM 10.2 --> It's OK without problems.
4. Restore all my apps from Titanium Backup --> Still OK
5. Uninstall Xposed framework for Reverse Tethering 3.7 --> Reboot --> Install same Xposed framework --> Reboot --> TADAAA!! problem occured :crying:
6. Stuck at bootloader
7. Have done many things but failed untill reinstall stock recovery and stock rom through ODIN --> Myphone start to breath
8. Done MegaWipe before reinstall TWRP recovery, CM 10.2, Gapps and restore some apps through TB --> No problems.
9. Try to nandroid backup via TWRP and get error log as below :
Backing up Data...
Breaking backup file into multiple archives...
E: Error tarring split files!
abusuffian said:
This is my first thread after a years here without any problems to flash on my i9300.
My condition:
1. Previously use CM 10.1
2. Update to CM 10.2 --> It's OK without problems.
4. Restore all my apps from Titanium Backup --> Still OK
5. Uninstall Xposed framework for Reverse Tethering 3.7 --> Reboot --> Install same Xposed framework --> Reboot --> TADAAA!! problem occured :crying:
6. Stuck at bootloader
7. Have done many things but failed untill reinstall stock recovery and stock rom through ODIN --> Myphone start to breath
8. Done MegaWipe before reinstall TWRP recovery, CM 10.2, Gapps and restore some apps through TB --> No problems.
9. Try to nandroid backup via TWRP and get error log as below :
Backing up Data...
Breaking backup file into multiple archives...
E: Error tarring split files!
Click to expand...
Click to collapse
Maybe sectors in eMMC going bad. My advice would be to have at least 4GB free on internal SD at all times. Backup weekly but only to external SD. Avoid writing to internal SD as much as possible. (also be 100% certain that you have multiple EFS backups). If you are using a dual-boot kernel - try to do most of your extensive work in a ROM that you install as second (and keep 1st as emergency backup).
xclub_101 said:
Maybe sectors in eMMC going bad. My advice would be to have at least 4GB free on internal SD at all times. Backup weekly but only to external SD. Avoid writing to internal SD as much as possible. (also be 100% certain that you have multiple EFS backups). If you are using a dual-boot kernel - try to do most of your extensive work in a ROM that you install as second (and keep 1st as emergency backup).
Click to expand...
Click to collapse
Thank you for your advice..
Is the problems under samsung warranty? how to prove to them?
Is there any way to do nandroid backup?
abusuffian said:
Thank you for your advice..
Is the problems under samsung warranty? how to prove to them?
Is there any way to do nandroid backup?
Click to expand...
Click to collapse
I don't think it is covered - or at least not as long as the phone is non-stock and it still starts
The backups can be done from a custom recovery - for instance with Philz there is a menu called "Backup to external SD". By using external SD you are minimizing the chance that something goes bad on the internal SD.
xclub_101 said:
I don't think it is covered - or at least not as long as the phone is non-stock and it still starts
The backups can be done from a custom recovery - for instance with Philz there is a menu called "Backup to external SD". By using external SD you are minimizing the chance that something goes bad on the internal SD.
Click to expand...
Click to collapse
TWRP also can backup to external drive. Have been tried and failed...
As your suggestion I installed Philz recovery and "Backup to external SD" and it completed nicely without any problem :laugh:
what is the different? i think it should be same backup target. it is external SD card but failed with TWRP.
Thank you
abusuffian said:
TWRP also can backup to external drive. Have been tried and failed...
As your suggestion I installed Philz recovery and "Backup to external SD" and it completed nicely without any problem :laugh:
what is the different? i think it should be same backup target. it is external SD card but failed with TWRP.
Thank you
Click to expand...
Click to collapse
I think it might be a small difference on where the intermediary files are stored but I can't say anything more without studying the source code (and asking Phil what the differences are in the dedicated Philz thread might be simpler).
I have rooted my moto E. Installed twrp recovery. Now i want to take backup of stock rom (android 4.4.4). While taking backup from twrp recovery I'm getting error
E: Unable to create folder: /external_sd/TWRP/
errno=13
failed to make backup folder
Please help.
I also got same error while trying to backup in internal sdcard, you sure you are making backup in external?
man droid said:
I have rooted my moto E. Installed twrp recovery. Now i want to take backup of stock rom (android 4.4.4). While taking backup from twrp recovery I'm getting error
E: Unable to create folder: /external_sd/TWRP/
errno=13
failed to make backup folder
Please help.
Click to expand...
Click to collapse
Backup to external SD card.... Internal gives this problem
Sent from Moto e
Issue resolved
Gogeta said:
I also got same error while trying to backup in internal sdcard, you sure you are making backup in external?
Click to expand...
Click to collapse
Thanks Gogeta. I changed storage memory to external and it worked successfully.
Issue resolved
luvk1412 said:
Backup to external SD card.... Internal gives this problem
Sent from Moto e
Click to expand...
Click to collapse
Thanks luv1412. I changed storage memory to external and it worked successfully
so I wanted to try cm12. I did a nandroid of my current rom with twrp. I used flashify to install philz recovery. Here's where I went wrong, I should have done a backup using philz recovery first, instead I wiped system and data and realized philz recovery would not read my sdcard. (I do not have security encryption enabled) my nandroid backups were to my external sd card not my internal. I tried getting adb to connect from within philz recovery but that's a no go. might have a usb driver issue Philz file manager is not working also. any ideas for now. I do not want to flash back to stock as i havefiles on the internal sdcard I don't want to delete. i wasn't expecting this.
Can't you just flash cm12 and backup your internal files. You don't need adb with removable memory. Also, twrp will flash cm12
Edit: I mean format new SD card with recovery, place cm12 on it, flash. Than backup all your stuff and start over
luke1987 said:
Can't you just flash cm12 and backup your internal files. You don't need adb with removable memory. Also, twrp will flash cm12
Edit: I mean format new SD card with recovery, place cm12 on it, flash. Than backup all your stuff and start over
Click to expand...
Click to collapse
@rp201
+1
This guy has the right idea. Just save what you can from your SD to your computer, then format your SD using Philz so it can read it. Then pop your SD back in the computer and copy your files over and just flash CM12 that way or restore your old ROM using Philz "TWRP" restore method (it actually does backups to and restores from the TWRP folder on either internal or external SD).
I just tried to upgrade from Alliance build 26 to build 30. I also loaded TWRP and used that to load update to build 30 since trying to load build 30 with CWM kept resulting in an abort with error 7. Now I am stuck at either simply booting into TWRP or to Droid logo to use Odin. I have have no useable file to recover to since all my backup files are CWM and I find out now they are useless in TWRP. Can I bypass TWRP and get back into CWM or am I screwed and need to start all over with Adam's thread to use Odin and stock files?Will I lose my saved CWM files entirely now on the phone itself? I need help please!
NB2A said:
I just tried to upgrade from Alliance build 26 to build 30. I also loaded TWRP and used that to load update to build 30 since trying to load build 30 with CWM kept resulting in an abort with error 7. Now I am stuck at either simply booting into TWRP or to Droid logo to use Odin. I have have no useable file to recover to since all my backup files are CWM and I find out now they are useless in TWRP. Can I bypass TWRP and get back into CWM or am I screwed and need to start all over with Adam's thread to use Odin and stock files?Will I lose my saved CWM files entirely now on the phone itself? I need help please!
Click to expand...
Click to collapse
Here's a few options off the top of my head to get you up and running again.....
1. You can use Odin to flash CWM recovery back to your phone, then (if you saved the CWM backup to your external sd card prior to flashing TWRP)... you could just restore that backup from the external sd card. If you saved your CWM backups to internal memory, they are probably deleted because I'm assuming you wiped when trying to install Alliance 30.
2. You can mount TWRP in USB mode, then transfer a recovery flashable CWM zip over to your external sd from the computer, and then flash CWM back to your phone and restore your CWM backup.
3. If you have an external sd card adapter for the computer... then you can remove the external sd card from the phone and mount it in the computer to transfer over a CWM recovery flashable zip and your backup files (assuming that you saved a backup in the computer). Put the sd card back into the phone.... then use TWRP to reinstall CWM.... then use CWM you restore one of your backups.
4. If you keep encountering booting problems and none of those ideas work... it would probably be best to just use ODIN to restore back to stock 4.1.2... then start from scratch by re-rooting the with Casual.
Good luck.
mattnmag said:
Here's a few options off the top of my head to get you up and running again.....
1. You can use Odin to flash CWM recovery back to your phone, then (if you saved the CWM backup to your external sd card prior to flashing TWRP)... you could just restore that backup from the external sd card. If you saved your CWM backups to internal memory, they are probably deleted because I'm assuming you wiped when trying to install Alliance 30.
2. You can mount TWRP in USB mode, then transfer a recovery flashable CWM zip over to your external sd from the computer, and then flash CWM back to your phone and restore your CWM backup.
3. If you have an external sd card adapter for the computer... then you can remove the external sd card from the phone and mount it in the computer to transfer over a CWM recovery flashable zip and your backup files (assuming that you saved a backup in the computer). Put the sd card back into the phone.... then use TWRP to reinstall CWM.... then use CWM you restore one of your backups.
4. If you keep encountering booting problems and none of those ideas work... it would probably be best to just use ODIN to restore back to stock 4.1.2... then start from scratch by re-rooting the with Casual.
Good luck.
Click to expand...
Click to collapse
Thank you for responding with such detail. It finally started to boot into Alliance logo but never completed. Now it says with yellow triangle phone needs to be returned to Verizon. It does not even work in Odin. I do have an external reader for the card but I guess I am screwed now anyway.I wonder if Verizon will even help me at all back to stock.
I've got 2015052 device from jd.com and flashed stock rom from here: http://en.miui.com/download-274.html using stock recovery. Then I've flashed twrp from here http://en.miui.com/thread-152550-1-1.html using stock recovery again.
Now I have twrp that can do backups but can't restore them. my twrp alsco can't install anything that modifies system partition.
I store backups on 64gb sdcard.
When I restore backup twrp starts restoring system as usual but then dies in few seconds with following message:
Code:
E:extractTarFork() process ended with ERROR=255
Does anybody have recovery for this phone that can do backup/restore? Please report what recovery works for you and where you get one.
nETPOBu4 said:
I've got 2015052 device from jd.com and flashed stock rom from here: http://en.miui.com/download-274.html using stock recovery. Then I've flashed twrp from here http://en.miui.com/thread-152550-1-1.html using stock recovery again.
Now I have twrp that can do backups but can't restore them. my twrp alsco can't install anything that modifies system partition.
I store backups on 64gb sdcard.
When I restore backup twrp starts restoring system as usual but then dies in few seconds with following message:
Code:
E:extractTarFork() process ended with ERROR=255
Does anybody have recovery for this phone that can do backup/restore? Please report what recovery works for you and where you get one.
Click to expand...
Click to collapse
Copy the backup into internal-storage and restore again, it should work now.
jwchen119 said:
Copy the backup into internal-storage and restore again, it should work now.
Click to expand...
Click to collapse
Same error with internal memory. I have a feeling that wiping data from twrp makes it unable to restore and install zips.
nETPOBu4 said:
Same error with internal memory. I have a feeling that wiping data from twrp makes it unable to restore and install zips.
Click to expand...
Click to collapse
DId you ever figure this out? Have the same issue on my Nexus7 2013 Wifi, installed CM, want to move back to backup of stock. But crash in to that proverbial Wall. And given that it's a Nexus, it's on Internal Storage, as it's all one big internal Storage.
thanks...
vevmesteren said:
DId you ever figure this out? Have the same issue on my Nexus7 2013 Wifi, installed CM, want to move back to backup of stock. But crash in to that proverbial Wall. And given that it's a Nexus, it's on Internal Storage, as it's all one big internal Storage.
thanks...
Click to expand...
Click to collapse
Nope. I've tried 4 to 5 twrps for my device but none of them can restore backup reliably.
Отправлено с моего Redmi Note 2 через Tapatalk