I followed the instructions on how to do a restore using nandroid and fastboot. All steps in Fastboot gave okay's but when I do the reboot it just hangs on the first screen "T-Mobile G1" and will not move past.
I was able to get the phone back up and working by putting JF R33 back on the phone after doing a wipe. I then put all the apps back on and did another nandroid back up and then tried to do a restore following the steps in from the second post and the same results. It gets to the first T-Mobile G1 screen and stays there. I would really like to get this to work so that I can test out other builds but still get back to a working phone.
One thing I noticed in trying to get the phone back up and working. When trying to reinstall JF R33 I get the following error if I do not do a wipe and just try and install it after a fastboot restore:
"E:Can't mount DATA:
E:Failure at line 2:
copy_dir PACKAGE:data DATA:
Installation aborted."
Paul
That's weird, I just restored about 20mins ago and I did not have any problems. Try re downloading the SDK then copying the ADB files to your system32 folder.
Just downloaded android-sdk-windows-1.1_r1.zip and the same thing it boots to the T-Mobile G1 screen and stays there. I let it sit there for 10 minutes now and nothing. I am using JFv1.42 R33. If anybody can help I would really appreciate it as I would like to be able to try out other builds but I would need to get back to this one.
Issue seems to resolved not sure which was the solution. I downloaded a new copy of JFv1.42 R33 and then used a different SD card. I can now do a back up and restore. Now I get to go and play.
Make sure the sdcard partitions are set up how there were when the backup was created and retry the restore. Chances are you had an ext2 partition for apps/data when you backed up and you don't now.
makethetick said:
Make sure the sdcard partitions are set up how there were when the backup was created and retry the restore. Chances are you had an ext2 partition for apps/data when you backed up and you don't now.
Click to expand...
Click to collapse
I was having trouble with nandroid backup too i tried this and it worked. thanks a lot man.
Related
I get to the part where it would restore the .android_secure part and it gives me this error this is with 3.0.2.4 and I can properly wipe and such...
"error while making a yaffs2 image of /sdcard/.android_secure"
and this prevents it from making a md5 sum so I basically hve no backups at all, is anyone else having issues with this? I'm going to try and toubleshoot back to 3.0.2.2 and see if i can get that to back up but if anyone can help it would be appreciated
I can make nandroid backups no problem. Do you use Clockwork recovery?
ERIFNOMI said:
I can make nandroid backups no problem. Do you use Clockwork recovery?
Click to expand...
Click to collapse
uh... your intelligence exceeds you
as for OP, I would try, if you haven't, in rom manager, hitting menu, delete cache, then menu again, settings, delete recovery, then reflash 2.4 and see if you can backup then.
nosympathy said:
uh... your intelligence exceeds you
as for OP, I would try, if you haven't, in rom manager, hitting menu, delete cache, then menu again, settings, delete recovery, then reflash 2.4 and see if you can backup then.
Click to expand...
Click to collapse
I have uninstalled 2.4 installed 2.2... same thing.. all while delete recovery every flash... still nothing... not being able to nandroid means having to start from scratch if I get a loop... I dont know when this started to happen but my past weeks nandorids are all screwed up... and I deleted the 1 nandroid I had that worked cause I thought the newer one was good
ok to anyone having this issue it seems to be a problem with my sd card... I plugged my sd card into my computer via a card reader and the "there may be errors on this storage device" came up... I did a nandroid with my 2g sd card just fine so it not an error with CWM atleast...
scanning for errors on my computer brought up a bunch of errors within .android_secure and corrected them and now I can backup... it said the errors are from removing the sdcard while its being written... how can we do that when its under the battery? and I only did a battery pull when I got a ten minute hang on bamf 1.2...
hope this will help someone if they get the same error
Thanks for posting this! This helped, thank you!
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
Hello,
I installed the latest cyanogenmod nightly. There were issues with the google play store so I had to switch back to a cyanogenmod 11 nightly from december. Unfortunately there was a problem with CWM and based on the information on the forums I flashed the old nightly manually in CWM. Unfortunately, my phone became stuck in a bootloop. I was not thinking clearly so I did not make a backup at the right time. I am trying to recover some data. I have first done a backup within CWM, it has apparently created a backup file in the /sdcard/. I then used "adb pull /sdcard/" to copy the contents of the /sdcard/ to a safe location on my PC. It seems to have worked but I am not sure. I do not know in which folders the data is actually stored.
(I don't know if reflashing the most recent nightly will work)
I was wondering if this solution will work, and if I will be able to keep the app data this way as well as retrieve a few pictures. Ideally I hope this will allow me to put the phone back to its original state at some point. I hear a factory reset deletes the contents of the internal sdcard on the moto g so that is why I am trying to copy it back to PC. But I wonder if I will be able to restore it afterwards. Any adivce would be greatly appreciated.
edit: uh oh seems adb pull sdcard has not completed successfully so I am at a loss at what to do
Is there an option in CWM or TWRP to mount partitions for access by a PC?
audit13 said:
Is there an option in CWM or TWRP to mount partitions for access by a PC?
Click to expand...
Click to collapse
Thanks for your help. I'm sorry I couldn't get back to you earlier. Thankfully I have been able to solve the problem by reflashing the cm12 nightly, retrieving the data from that, and then wiping the phone and reflashing an old snapshot. Now I will be careful with backing up my data in the future.
I don't understand why the cm12 don't work though. I get weird scan lines on everything, including the boot screen. I think it may be due to the google apps because they keep quitting. I will try something else.
edit: I will post this issue in a separate thread
I'm getting "extractTarFork( ) process ended with ERROR: 255" whenever I try to restore the back up. I'm able to successfully restore system and boot without any issues, so it seems to be something to do with the data section.
I recently upgraded my TWRP to the latest so I tried to downgrade back to the previous version but it still doesn't let me restore it.
From googling, I've seen posts suggesting that people have been deleting a line by finding it in their log, but I'm unable to find the log nor do I understand how to edit it to try and solve the issue.
Any help would be appreciated
I had this problem and it took me two days to resolve it. I had a good backup and I know it was good because I had used it several times and it worked. But then after doing some system installs I got the error 255 when I tried to restore it. I tried several things to fix it and nothing worked and I really did not want to lose my backup. What did work for me was to use TWRP wipe function to FORMAT the phone. Wiping or factory reset did not work. I lost the contents of my internal SD card but I was able to transfer most to my external SD card. You could also connect the phone with a cable to a computer and use the pull command in ADB to backup the contents f the internal SD card. Given the choice between losing the SD card and the data files I come to lose some of the SD card. Anyway, a FORMAT worked when nothing else did. I read that this error is caused by a lack of space. When I checked the log it seemed that the restore was failing with a particular file which misled me to thinking I had to remove the corrupt file, but since after the format I was able to restore without any problem, it would seem that there was no corrupt data. Hope this helps someone.
sir..please help me.. I have a twrp backup of system image vendor image data boot recovery persist but im unable to recover because it shows an error extract tar fork process ended up with error 255
i also have a backup of my internal storage in twrp but im not able to restore because of this error
I keep trying to do backups but it gets about half way through and the error 255. I don't understand what I'm doing wrong. Is it not possible to backup through twrp on xt1955-5. If not any suggestions on other means. Something that would include my accounts as well would be great. I have an google acct that google refuses to give back. Be cause they say can't verify. I know password but 2sv got messed up. Which is a bunch of bs. They track everything. I would prefer to never have to go through this again. Any help would be great.
First question. What all are you trying to backup? Second, to where? Third, do you have adequate space for said backup?
Also, if you have a pin or code enabled for access to the device I would disable it for the backup process.
I'm trying to back up system and data only to my ext sd with 50g avail but only needing 12g
Pbsipher1 said:
I'm trying to back up system and data only to my ext sd with 50g avail but only needing 12g
Click to expand...
Click to collapse
I was able to use TWRP to create a backup on an SD card. I'm running Android 10 and rom RR.
You might try other avenues like titanium or migrate. A quick internet search might lead you to a better procedure and app.
I've been having the same trouble. I just restored my XT1955-5 to stock RETAIL. Then installed TWRP and Magisk. I set my phone up as I like it, and want to back it up - everything I can possibly backup - boot, data, system, system image, efs, persist1, persist2, fsg, vendor, vendor image, dsp, and boot logo.
Before I tried to backup anything, I made sure that I mounted all of the partitions in TWRP.
The first few times I tried to back them all up at once, I got the error 255. So I started backing up the partitions one by one. The only partition that would NOT backup was the data partition. I still get the error 255 on the data partition backup. But all the others worked fine. I even went back and selected all the partitions except the data partition, and it backed up in one large backup just fine. So I don't know what the deal is with the data partition, but I can grab it with adb pull, so I guess I'm good to go.
I even booted back into the system and turned off the screen lock PIN - changed it to none. But I still couldn't backup the data partition via TWRP.
This should work for you from adb to backup your data partition:
Code:
adb push mmcblk0p64-data.img /dev/block/mmcblk0p64
Thanks tom2112 I'll give it a try what can it hurt. I also heard u have to be decrypted in order to backup data but can't seem to get decryption to stick
i was no able to backup using that command got
adb: error: stat failed when trying to push to /dev/block/mmcblk0p64: permission deni
Tom2112 said:
I've been having the same trouble. I just restored my XT1955-5 to stock RETAIL. Then installed TWRP and Magisk. I set my phone up as I like it, and want to back it up - everything I can possibly backup - boot, data, system, system image, efs, persist1, persist2, fsg, vendor, vendor image, dsp, and boot logo.
Before I tried to backup anything, I made sure that I mounted all of the partitions in TWRP.
The first few times I tried to back them all up at once, I got the error 255. So I started backing up the partitions one by one. The only partition that would NOT backup was the data partition. I still get the error 255 on the data partition backup. But all the others worked fine. I even went back and selected all the partitions except the data partition, and it backed up in one large backup just fine. So I don't know what the deal is with the data partition, but I can grab it with adb pull, so I guess I'm good to go.
I even booted back into the system and turned off the screen lock PIN - changed it to none. But I still couldn't backup the data partition via TWRP.
This should work for you from adb to backup your data partition:
Code:
adb push mmcblk0p64-data.img /dev/block/mmcblk0p64
Click to expand...
Click to collapse
ed
Hmm... if it is "permission denied" that sounds like you need root permissions to back it up. I'm sorry, but I'm not good enough with ADB to tell you how to get higher privs. Maybe ADB SHELL then SU, but I don't honestly know.