Related
Sorry for creating a new thread, but I have searched and worked at this problem for hours and can't find a solution. I have a myTouch 3G running the latest Cyanogen ROM, the latest Amon_RA recover image, and the Engineering 2010 SPL. This phone is a replacement and I had done a Nandroid backup on the old one before sending it back. Oddly enough, it would not let me do a BART backup, saying there was an unknown error and I should do it from a computer. Since there is not Apps to SD, I figured Nandroid would be good.
Now my problem is restoring it, if I try to restore it from the recovery image, it says "Error : run 'nandroid-mobile.sh restore' via adb!" Does anyone know why the recover will not run a BART backup or Nandroid restore without me doing it via the computer? Both of these functions work fine on my G1. At first, I thought it might be the SPL as I read of problems with the stock SPL not writing in fastboot mode. I actually tried to do the Nandroid restore via fastboot, but kept getting an error there. When researching that error, I saw that it was a result of the "Perfect SPL" so I changed it to the engineering SPL. I had a thought that this might be why the recovery would not complete these functions, but the problem persists.
I decided to follow the directions and loaded up my adb shell to try it that way. When following the directions on Cyanogen's website, I was unable to even mount my SD card, getting this error: "Mounting on sdcard failed: Device or resource busy". I then tried the 'nandroid-mobile.sh restore' function, but got this message: "nandroid-mobile.sh not found". It seems nothing works as it should, and I can't figure out why, especially since they all work fine on my G1. Any help is greatly appreciated. Thanks.
Edit: I just tried doing it via fastboot again following these directions: http://code.google.com/p/android-roms/wiki/NANDROID_Fastboot
It worked well, until I got to the UserData section when it said "FAILED <remote: data length is too large>"
you may get that error when using bart if you do not have an ext partition. check make sure you have properly formatted your sd card, fat32 and ext2/3/4.
r u on adb shell mode? while on the recovery mode?
ensure that everything has been wipe~
i also face the same problem while restore it.. but.. it work when using adb..
its very simple..
I do not have an EXT partition as I do not need apps to SD. If you're saying I can't do a BART backup without one, that's fine. Any ideas as to why the Nandroid restore won't work?
@moosunk What do you mean by ADB shell mode? I am using the Windows Command Prompt and have typed "ADB Shell." I am able to navigate through all the normal ADB shell commands I'm used to (ie ls, cd, etc), but it doesn't find the restore option. I did try wiping right before doing the restore in the recovery mode. To get to ADB shell, I had to let the phone boot as I don't see any option in my recover image to access the phone via ADB, but if there is a way, please let me know. Thanks.
jimbo831 said:
I do not have an EXT partition as I do not need apps to SD. If you're saying I can't do a BART backup without one, that's fine. Any ideas as to why the Nandroid restore won't work?
@moosunk What do you mean by ADB shell mode? I am using the Windows Command Prompt and have typed "ADB Shell." I am able to navigate through all the normal ADB shell commands I'm used to (ie ls, cd, etc), but it doesn't find the restore option. I did try wiping right before doing the restore in the recovery mode. To get to ADB shell, I had to let the phone boot as I don't see any option in my recover image to access the phone via ADB, but if there is a way, please let me know. Thanks.
Click to expand...
Click to collapse
ahaa.. u face the same problem with me..
nandroid from adb doesnt recognize any of the default backup that have been created...
u need to key in manually, when u do a nandroid recovery on your phone, there have specific file name base on date,
what i do is, just use the file name as a string to search the backup..
use this location also on adb..
/sdcard/nandroid/HT95YKF08716/BCDMRS-20091210-0806
this is mine, i dont know what is yours.. but u can check it by yourself i think..
I get that error message when using Amon_ra's recovery but when I reboot all of my information is there.
decepticon said:
I get that error message when using Amon_ra's recovery but when I reboot all of my information is there.
Click to expand...
Click to collapse
Hmm, it doesn't seem to do anything on mine. I only get one little status dot before I get the message and it takes less than a second, so I don't think it's copying anything.
Regarding typing out the string in ADB, I have tried that, but the problem seems to be that the nandroid script isn't recognized by my phone since it says "android-mobile.sh not found." If I understand that message correctly, it's saying it is not finding the script it needs to run the nandroid restore. Do I have to CD to a certain directory first or something, and shouldn't this script be built into my Cyanogen ROM?
and what if you try to restore it with an older recovery image? this problem has surfaced with the latest releases, I think (it gave me that error on the last restore too but the backup was restored)
ID?
I am getting the same error. It started to happen right after (test)flashing a Motoblur Rom. My wild guess is that flashing this ROM has changed some ID (maybe of the SD CARD) leading to a missmatch error and failure to reflash the backup. However, at this point only a wild guess. As it is possible to access the SD card from PC via new Recovery, it does not worry me too much (read backup from Recovery to Desktop, switch to Fastboot, flash the .img's). But I agree it is a pain in the ....
For all the "why" questions : Check /tmp/recovery.log right after you have an issue to see what is going wrong!!! I even added an extra menu option to move the log to your sd card so you can view it more easily....
feicher said:
I am getting the same error. It started to happen right after (test)flashing a Motoblur Rom. My wild guess is that flashing this ROM has changed some ID (maybe of the SD CARD) leading to a missmatch error and failure to reflash the backup. However, at this point only a wild guess. As it is possible to access the SD card from PC via new Recovery, it does not worry me too much (read backup from Recovery to Desktop, switch to Fastboot, flash the .img's). But I agree it is a pain in the ....
Click to expand...
Click to collapse
I finally gave in and tried that, but it didn't work either. When I was doing this, I got this error message when flashing the data.img: "FAILED <remote: data length is too large>"
This is just getting more and more frustrating. I finally figured out how to use ADB with the phone in recover mode and access the nandroid-mobile.sh commands and that is not working either. It finds the backup and the nandroid.md5 file, but then says "Error: no backups found" when I try to use it or any of the three I have. It says the nandroid.md5 is not found, even though it shows that file in the path. I can't do this using adb shell, fastboot, or the recovery menu like every guide I have found on the internet says, and I can't figure out why it doesn't work. I highly doubt the backups are corrupted as I have 3 seperate backups and none of them are working. However, I have been able to read these backups off the SD card using windows and even flash all the files via Fastboot (except the most important data.img since it says it's too large for no apparent reason). Please somebody help, I am about to jump over a cliff.
Try the following :
Run the following in adb and note down the serial number :
Code:
cat /proc/cmdline | sed "s/.*serialno=//" | cut -d" " -f1
Rename the nandroid backup directory on your sdcard to the serialnumber you just noted down
/sdcard/nandroid/NEW-SERIAL/BCDMRS-20091210-0806
Run nandroid restore from the recovery menu and choose the new serialnumber ID and then the backup to restore.
Amon_RA said:
Run the following in adb and note down the serial number :
Code:
cat /proc/cmdline | sed "s/.*serialno=//" | cut -d" " -f1
Rename the nandroid backup directory on your sdcard to the serialnumber you just noted down
/sdcard/nandroid/NEW-SERIAL/BCDMRS-20091210-0806
Run nandroid restore from the recovery menu and choose the new serialnumber ID and then the backup to restore.
Click to expand...
Click to collapse
Thank you, I will try that when my wife gets home today. I sure hope it works, but I wonder why it wouldn't work without changing it. When I swapped my G1, the recovery found the old backup regardless of the serial number change, but that is definitely something I hadn't thought to try. <Fingers Crossed>
Edit: Thanks so much, it worked perfectly!!! You sir deserve a Redbull!
I was having this same problem, I figured it out I couldn't do a nandroid backup because I didn't have enough room on my sd card, easily solved. but bart still wouldn't work, in my search of solutions to my problem it was NguyenHuu post about the ext partition, so did a repair ext through the recovery and everything is working.
Hope this helps someone.
Hi everyone.
I just made a backup/full wipe/restore with CWM latest version available on rom manager.
The backup are good (their MD5 sums are correct) but clockworkmod recovery is not able to restore the data.img
(while restoring it hangs and exits)
The problem is in the yaffs .img file (incorrectly created by the recovery).
If you try to unyaffs it the software begins the extraction and then
Code:
C:\Users\Lino\Desktop\secure>unyaffs data.img
read image file
: Bad file descriptor
read image file
: Bad file descriptor
DO NOT TRUST ON BACKUPS made by cwm 3.0.2.6 if you don't want to lose your data.
You are warned.
UPDATE in post #20
FIX in post #24
I'm sure I can speak on behalf of many people here. I have been using cwm for years on 3 different devices without any issues. Just because you are having an issue does not mean you should post a thread claiming no one should trust cwm.
I did it too but in latest (published) version of CWM there must be a bug in yaffs creation.
You can ignore this if you think I'm wrong.
I'm not stating that in EVERY version there was a problem...
I'm warning everybody that THIS version does.
The created IMG is corrupted even if its MD5 is correct and the recovery "crashes" when trying to restore the backup. try it yourself.
Steps:
Full backup.
Wipe data/factory reset.
Restore.
....the restore process aborts while restoring.
Maybe you are trying to backup/restore an EXT4 rom with an EXT3 CWM version (3.0.2.6)
No, I'm not.
The restore process starts and restores correctly about 600mb of data (on a total of 800) after that the recovery reboots (without restoring android secure, I suppose it gets restored after data).
The phone can boot up but with crippled data.
I successfully restored android secure unyaffsing the img and copying manually the data back to the card but I have no way to extract the remaining 200 mb from data.img because the image is bad.
The only time I've had this issue was when I made a backup without paying attention to how much space I had left on my SDcard, it was practically full, but Recovery happily completed and generated an md5. Needless to say my backup didn't work, but really it was my own fault for not making sure I had enough space on my card.
Nope. 5 gb still free.
Even the backups made with 3.0.2.5 are damaged.
..and I'm reading there was a similar problem (in the backup part) in the past:
1.8.4.3 Fix bug in yaffs2 where the max path was set to 500, rather than PATH_MAX. This was causing issues when creating yaffs2 images of files with very long names that were generated by a process gone bad, or the like. This causes a segfault during backup of the cache and the recovery reboots. The "symptom" is a missing md5 file.
Click to expand...
Click to collapse
This time the backup completes but the restore reboots the recovery leaving the restore process incomplete.
@LinoX
I can confirm your findings since I already hit the problem sometime ago.
I already mentioned this problem and since now has to use my own method of backup using dd
(I no longer use nandroid of cwm to backup). I already PM to CWM's author without any reply received since.
http://forum.xda-developers.com/showpost.php?p=14714800&postcount=319
http://forum.xda-developers.com/showthread.php?t=1124939
dnlilas said:
http://forum.xda-developers.com/showpost.php?p=14714800&postcount=319
Click to expand...
Click to collapse
YESSS!! IT IS EXACTLY THE SAME PROBLEM!!!
It's definitely the CWM broken.
I don't want to "restore" with dd because dd will write the partition directly to nand (transferring to nand the yaffs problem)... did you find a solution?
Did you try the 'Quick Backup and Restore' option from RM? I've struggled with a backup in the past with similar symptoms you described and enabling it helped along with 2 other steps:
1. Manually Advance Restore boot, system etc.
2. Fix permissions after then repeat step 1.
LinoX said:
YESSS!! IT IS EXACTLY THE SAME PROBLEM!!!
It's definitely the CWM broken.
I don't want to "restore" with dd because dd will write the partition directly to nand (transferring to nand the yaffs problem)... did you find a solution?
Click to expand...
Click to collapse
There is no problem using dd for backup/restore. Just make sure all partitions are unmounted before using dd.
Jacob1369 said:
Did you try the 'Quick Backup and Restore' option from RM? I've struggled with a backup in the past with similar symptoms you described and enabling it helped along with 2 other steps:
1. Manually Advance Restore boot, system etc.
2. Fix permissions after then repeat step 1.
Click to expand...
Click to collapse
I can't try... I have a partially recovered phone.. the backup I have is already "broken"..so that's a warning for everybody: don't trust nandroid backups.
Use DD method for backing up partitions (check 10 times command line before restoring, 'cause if you restore to the wrong partition you brick the phone)
I don't care about losing a couple of files.. I need a way to read a "broken" yaffs filesystem (in order to copy all "good files" skipping the damaged one)
maybe a mount -t yaffs?
dnlilas said:
There is no problem using dd for backup/restore.
Click to expand...
Click to collapse
Yes but it's a risky operation.. And I was referring to my damaged yaffs filesystem. The data partition should be ext3 so I need a way to "gracefully skip" the yaffs errors in order to read every file after the "error".. do you know if is there a way to do it?
http://androidforums.com/android-ap...workmod-recovery-failing-restore-backups.html
here's the same problem, f**k!
Well i never faced any problem so far...
LinoX said:
I need a way to read a "broken" yaffs filesystem (in order to copy all "good files" skipping the damaged one)
maybe a mount -t yaffs?
Click to expand...
Click to collapse
No way..
Code:
# mount -t yaffs2 -o ro,loop /sdcard/clockworkmod/backup/2011-07-05.09.38.18/data.img /sdcard/bkdata
mount -t yaffs2 -o ro,loop /sdcard/clockworkmod/backup/2011-07-05.09.38.18/data.img /sdcard/bkdata
ioctl LOOP_SET_FD failed: Device or resource busy
I never faced any problem...
Anyways will be careful next time.....
it would be interesting to see if we could replicate this and try to find out what is actually corrupting the image.
Ricey
Sad to say if the yaffs image is broken it is broken.
Yaffs is a filesystem stored in an image. It has indices and all. if unyaffs cannot read the file system it would be like guessing wich filename matches which part of the data. In a way that would be riskier than not putting data at all.
Do you have an older backup that is intact? It might save your Phone.
OK. I found the problem!!!
The yaffs image is NOT corrupted!!!
It's the UNYAFFS code that actually is broken.
I downloaded the unyaffs.c because I wanted to debug it (skipping the part of the damaged file) and extracting every possible file.
The recovery seems to use the SAME unyaffs code (because the exception is the same).
The problem is in the MAX number of files!!!!!
the code has a limit hardcoded in:
Code:
[COLOR=Blue]#define[/COLOR] MAX_OBJECTS 10000
when I debugged it it halted with an access violation simply because the number of files was bigger.
Modifying the unyaffs.c (increasing the constant to 50000) allowed me to extract every file (50.000 is the maximum defined in the "backup code")
So... at the moment your backup are good (unless we find some other error) but you can't restore them with every cwm so far (it will halt at the 10.000th file/dir).
Hi,
I checked through many threads to see if anyone had a similar problem but couldn't find anything unfortunately.
Background :
I was running a Lite'ning ROM on my Samsung Galaxy S2. You're probably familiar with this ROM, but for those who aren't it gets flashed with ODIN and comes rooted and pre-installed with CWM.
I forget which version of Lite'ning ROM it was, but I am fairly certain it was pre-1.5 as the bundled CWM was definitely version 3.x.x.x (later versions I found had 4.x.x.x and 5.x.x.x).
I wanted to try a version of GalnetMIUI for something a bit different and hadn't changed ROMs in quite some time, so I booted into CWM 3.x.x.x (maybe 3.0.0.2?) and did a backup to the internal SD. This came in at around 1.4 GB and comprised of 4 files :
cache.img
data.img
nandroid.md5
system.img
I copied these to my PC too, just in case they somehow got erased from my phone.
Once I'd done this, I then copied the new ROM .zip file (latest version of GalnetMIUI) to the root of the internal SD, booted the phone into CWM, wiped user data and Dalvik cache, then proceeded to install it.
The problem :
I can't get my apps or data back. I was under the false impression that my Google account was automatically backing this up for me, and would restore everything once logged in as it had in the past (factory resets etc.). So once this didn't happen, I tried using CWM to revert back to how things were before installing the new ROM but although the restore appears to work I end up with issues.
I've tried a number of different ROMs and they either get stuck in 'boot loops' or a black screen after running through the restore procedure. I've tried restoring just data via the 'Advanced' option but this doesn't help.
I was under the impression that I'd be able to fully restore the ROM backup if I needed to, and have the phone running exactly how it was prior to messing around. It would seem this is not the case.
In desperation I tried flashing every Lite'ning ROM from version 1.0 to 4.2, restoring my backup each time but as mentioned I always get boot issues.
Have I lost my data? I hope not, as I had 'To Do' lists and all sorts of things that would cause problems if they were not retrievable. I realise this is a lack of knowledge and foresight on my part. I'm thinking now that I should have run Titanium Backup prior to this, and not assumed that CWM was going to provide a complete solution.
Hope all this makes sense and if any of you have the time to read through and offer advice it would be greatly appreciated. I am currently running a very pretty and slick GalnetMIUI without any of my data!
Thanks in advance.
download cwm 2.5.x.x its better
[email protected] said:
download cwm 2.5.x.x its better
Click to expand...
Click to collapse
Thanks for that, I'll give it a go tonight after work. Am I right in thinking that if it doesn't work I can extract the individual files and insert them manually to get my app data back?
OK, so after hours of searching I'm still no wiser as to how to install CWM 2.5.1.2
I found a zip file that was apparently version 2.5.1.2 but when I tried to install it from inside CWM 5.0.2.6 (included with GalnetMIUI) it sometimes gives an error, sometimes it reboots CWM and sometimes it simply says it has successfully installed (it lies). No matter what it says or does, it doesn't seem to actually replace version 5.0.2.6 with the older one and every time I do the three-finger boot it loads up the latest version like nothing changed.
I'm just so lost. All I want to do is restore my old backup, get my data back and move on. Please someone help me before I go insane from all this research!
[EDIT] In case any more information is needed, my exact procedure for installing version 2.5.1.2 of CWM went like this :
Download 2.5.1.2 zip file
Copy zip file to root folder on internal SD
Boot into CWM 5.0.2.6
Select "install zip from sdcard"
Select "choose zip from sdcard"
Navigate to 2.5.1.2 zip file, select and confirm
Can anyone help me at all?
In particular I'd like to know how I can downgrade to CWM 2.5.1.2 or similar in order to give [email protected]'s suggestion a go.
Failing that, if anyone has any suggestions whatsoever about how I can get my backup data restored it would be greatly appreciated. After spending some time with MIUI - in particular the Galnet ICS build - I have nothing but praise, but I really have to get my data back!
You should be able to downgrade through ROM manager. Go to "All Clockwork Mod Recoveries" and just flash one that is not 5.x.x. Any backup not made with version 5 will not work with the new version So if you can flash one that is version 2, 3 or 4 you should be good to go. If that doesn't work you can fastboot flash it. There are guides on how to do that.
Wait.....did you mount /system before installing the CWM zip ?
Sent from my GT-S5830 using XDA App
Sorry for the delayed reply, for some reason I didn't get an email notification that my thread had been updated.
lowandbehold said:
You should be able to downgrade through ROM manager. Go to "All Clockwork Mod Recoveries" and just flash one that is not 5.x.x. Any backup not made with version 5 will not work with the new version So if you can flash one that is version 2, 3 or 4 you should be good to go. If that doesn't work you can fastboot flash it. There are guides on how to do that.
Click to expand...
Click to collapse
For some reason, when I select "All ClockworkMod Recoveries" the only two options are 4.0.1.4 and v4.0.1.4. I'll have to look into "fastboot" flashing as I've never heard of that.
By the way, if I boot into CWM via ROM Manager the version that loads is 4.0.1.5, but if I perform the three-button combo when switching my device on I get version 5.0.2.6.
EmoBoiix3 said:
Wait.....did you mount /system before installing the CWM zip ?
Sent from my GT-S5830 using XDA App
Click to expand...
Click to collapse
I didn't, is that something I should try?
Edit - Just tried this and at first it rebooted CWM and the version number hadn't changed. Doing this again yielded me the following error with no change in version number :
Code:
E:Error in /sdcard/CM V 2.5.1.2_update.zip
(Status 0)
Installation aborted.
I found out that I can extract the contents of my backed up .img files using unyaffs.exe.
Unless I'm doing something wrong, it would appear that my backup is corrupt somehow. When trying to extract data.img, it processes for a while and does bring back a lot of files but I also get the following :
Code:
read image file
: Bad file descriptor
read image file
: Bad file descriptor
data.img is around 1.2GB but the files I extract only amount to around 190MB.
It would appear that I don't have my contacts database in there which is annoying as for some reason there were quite a few that didn't get synced to Google's servers.
Hello everyone,
First let me give you some background information.
I have a P6210XXLB2 and I was on android 3.2
I have been waiting 2 years and + for an update for my tablet
Never dared to do it myself
Recently, I have tried doing so, I tried to grasp as much information as I could
However, they were no clear easy tutorial step by step on the subject
I decided to start, and rooted my phone with KangoRoot
Then, I installed CWM 6.0.2.7 through ODIN 1.85
Proceeded to a nandroid backup on my external SD.
I tried Installing PA3 following that tutorial
http://forum.xda-developers.com/showthread.php?t=2221328
Realized none of the p6210 versions were working
Followed this guy recommendation
http://www.jawalak7yatak.com/en/how...ranoid-android-3-60-on-galaxy-tab-7-plus.html
Installed the 3.60 version + 4.2.2
The phone booted up until the splash screen and then black screen
Tried different versions of p6200 and p6210 while removing the prop thing command from the p6210 one
Nothing but black screens
Decided it was enough and tried to go back to my original version
Which is on my ex SD, I had mismatches with MD5
Decided to remove the MD5 check
Now were here, I have an error while restoring /system
If I check the log, only thing that shows up is
I:Can't partition non-vfat: datamedia
I: Can't format unknown volume: /emmc
Thought it was maybe a problem with permissions, tried using fix permissions
However, its still the same error MSGs
The only solution I can come up with is from here
http://forum.xda-developers.com/showthread.php?t=2349776
I will probably do that tomorrow when I wake up If dont get any answers
http://www.ibtimes.co.uk/galaxytab-plus70-gtp6210-official-android412-xxdm3-jellybean-467821
Solved it.
I have p6210xxlb2 with android 3.2 (from Canada)
Installed the 4.1.2 MF1 from russia
Installed cwm 6.0.2.7
Bootloop, cleared cached, data, dalvik
It works now.
Hope it helps someone !
my tab plus Upgraded to 4.4.4。i think you can try it.
open nandroid.md5 .delete all text in file-save and no md5 mismatch.or u just delete file md5 and creat a new file text(blank file) with the name nandroid.md5
As I understand, my situation is fairly specific, and so I need to address a few points:
This is my first time rooting a phone- I've made several mistakes but managed, at this point, to avoid bricking my phone
I'm using a Nexus 5, and flashing the pwnphone system (Android Open Pwn Project)
I've followed all the standard steps (except one... see below) for unlocking, rooting, and using TWRP as my recovery
I've also successfully flashed AOPP once, although I made an error I couldn't fix during setup and needed to reinstall
To my stupidity, I forgot to make a Nandroid backup on both attempts
I've just used TWRP to wipe my phone's Dalvik/ART Cache, system, data, and cache, assuming I could reflash the same zip I used before
MD5 check is disabled
Zip validation is disabled
Okay, so let's get down to the heart of the issue now. My phone is sitting here, plugged into my computer, I have a command prompt running, and adb is working properly. I try to flash THE SAME ZIP file I used, just before, to start from a clean slate AOPP install, and now I'm recieving an Error: 7.
I looked up the fixes for this, and ran into a problem: I'm already using the most recent version of TWRP- and I just made an alternate AOPP.zip where I removed the asserts from /META-INF/com/google/android/update-script. I was hoping this would solve my problem, but it didn't.
Now, instead of getting an Error: 7, I'm getting an "invalid zip format" notice with very little other information.
Installing zip file '/sdcard/aoppfix.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Invalid zip file format!
Error installing zip file '/sdcard/aoppfix.zip'
Updating partition details...
...done
Click to expand...
Click to collapse
I have no idea what to do at this point. In my earlier error, I failed to make a Nandroid backup file- and much to my dismay- I can't even find one someone has uploaded elsewhere which I could use to at least have a functioning phone to to boot into.
Can someone please help figure out what my next course of action is?
Hi and welcome to XDA Assist !
I`ve searching and I couldn`t find that rom on the Nexus 5 development forums so it`s hard to figure out what`s the problem
Your attempts to modify that script are courageous but I`m afraid that is more than a script issue
Try to flash a different rom with xda support and you`ll get more info and help , good luck !