I recently did a nandroid backup and it worked. I then flashed a theme that I thought I liked but didn't so I ended up using the restore nandroid process in recovery mode and it worked. I then changed the name of the first folder inside of the Nandroid folder so I know which ROM it is. I then ended up flashing another theme that I did not like. I tried to do a nandroid restore but this time I get an error says to do "nandroid-mobile.sh restore" or something like that from ADB.
How do I do the restore from ADB? I would use the CMD correct? I tried looking for possible command using CMD but could find nothing. Anyone know why this happened. Why I get this error? I use to get this error all the time on my G1 so I instead would use SwitchRom, but does anyone know if a SwitchRom exists for NexusOne?
I got this same error tonight!
unfortunately my computer no longer recognises my nexus one in either windows or linux, so i can't use ADB anymore.
MFK DGAF said:
I recently did a nandroid backup and it worked. I then flashed a theme that I thought I liked but didn't so I ended up using the restore nandroid process in recovery mode and it worked. I then changed the name of the first folder inside of the Nandroid folder so I know which ROM it is. I then ended up flashing another theme that I did not like. I tried to do a nandroid restore but this time I get an error says to do "nandroid-mobile.sh restore" or something like that from ADB.
How do I do the restore from ADB? I would use the CMD correct? I tried looking for possible command using CMD but could find nothing. Anyone know why this happened. Why I get this error? I use to get this error all the time on my G1 so I instead would use SwitchRom, but does anyone know if a SwitchRom exists for NexusOne?
Click to expand...
Click to collapse
if you are using RA recovery, just open CMD and type
Code:
adb shell
# switchrom
when you are in recovery... from there you can do what you need to do... but if you are only restoring a nandroid, use BART (also built into RA recovery)
Code:
adb shell
# bart
a list of options will come up, for nandroid backup i think it is just
Code:
bart -n
but im not entirely sure.
you can also restore the backup from the actual recovery... scroll down to nandroid/backup and then choose bart nand restore or whatever the option is.
Sometimes that happens to me when my phone is low on battery try fully charging your phone.
Does changing the name somehow cause this problem?
I have noticed that when you change the name of the folder that contains the nandroid backup it will fail to restore it.
McFroger3 said:
I have noticed that when you change the name of the folder that contains the nandroid backup it will fail to restore it.
Click to expand...
Click to collapse
The name of the folder has to be "Nandroid" or its will not properly restore. I never had to noticce this, it was actually obviously since the G1 days.. don't know how I already knew.
You'll get that error if you battery is <30%
Full charge when you flash people, full charge.
(Edit: and search)
Related
Hi
I have problem when i does nandroid i get the massege
Run nandroid-mobile.sh via adb.
And i try to do it wheb i connect to the pc and when i'm not
I have nexus one cm6
Thenks
Unmount your sdcard.
from recovery mount then unmount
How i'm doing mount from recovery?and unmount???
The option mount sdcard from recovery.
yet didn't find it
Its very easy to solve this. Just charge your phone for an hour or so. Then boot to recovery, run nandroid . Everything will be fine.
This prob arises cos ur low on battery.
gud luk
Sent from my Nexus One using XDA App
Yeah. You're battery is too low. It won't let you run for safety reasons.
I've had this error (or a similar one) when I didn't have enough space on the SD card...
i have enough place and enogh battery but still it didn't do it
This fixed this problem for me:
- Enter Recovery
- Mount USB
- Open up a cmd window in your tools/adb folder
- Type: adb remount
- Then: adb shell mkdir /system/sd
It supposedly occurs because there is a missing SD folder in the System folder.
how to do mount usb at the recovery?
i connected my nexus and do the cmd and type the commend and it give me these
remount failed:invalid argyment
ok here is the thing that i did..and yet you can see the "not fouand "at the end..
also i tried after these to do regular from the phone and yet i get the same massege at the start
http://yfrog.com/1g42509115j
you can look here
if you're using amon-RA recovery press USB MS toggle to mount your sd card while it's connected to your computer.
and what after?i did ot and than tried to do again nandroid and it the same
did you rename the nandroid file/folder? make sure there are no spaces.
I7210I said:
Hi
I have problem when i does nandroid i get the massege
Run nandroid-mobile.sh via adb.
And i try to do it wheb i connect to the pc and when i'm not
I have nexus one cm6
Thenks
Click to expand...
Click to collapse
britoso said:
did you rename the nandroid file/folder? make sure there are no spaces.
Click to expand...
Click to collapse
Britoso got the answer
I had this problem for the first time EVER a few days ago.
I thought it was because I upgraded from amon_ra 1.7, to 1.8.
THE PROBLEM IS DUE TO THE FILENAME, make sure to remove spaces, or replace them with dashes or underscores.
Access the nandroid folder on your sdcard in any way possible: via usb cable, or stick it in a card reader and do it that way. there are many ways to rename the nandroid folder.
ok i removed the folder NANDROID from my sdcard and yet it doesn't help it's create a new folder but the massege s come back and the folder is full so what is going on there?
The suggestion was to RENAME not REMOVE - though I don't really think it was the right suggestion anyway (your file naming convention looks good, from the image you posted).
I recommend you pay close attention to your typing though, because there are a lot of input errors in the image you posted, and that's a sure way to screw things up...
Adb is telling you that you don't have an md5 file for that nandroid, so I'd try listing the folder contents to confirm (you may have deleted it). I would also try the other backups, and hope one works...
Which recovery do you have? I think Amon Ra's will let you run nandroid from the phone, which might be a better/safer option?
Sent from my Nexus One using XDA App
first of all i have recovery-RA-nexus-v1.7.0.1 (amon)
and i tried to do the nandroid from the recovery...and at the start i get the message Run nandroid-mobile.sh via adb.
the funny is that i did upgrade to my frend phone and i get the same message to (from 5.0.7 to cm6)
ok ...good news..
i changed the recovery to clockware and now i did backup..
so the setioation is that i have a file called NANDROID and one more fie called clockware backup so i can be sure that the backup s good now?and i can erase the file nandroid?
Hi guys, I recently used the 'fix permissions' option in ROM Manager, which caused my SMS contact pictures to disappear. I then was trying to fix this by doing:
Code:
su
chmod 666 /data/data/com.android.providers.contacts/files/*
in Terminal Emulator on the device and dropped it right at :
Code:
su
chmod 666 /data/data/
anyways, long story short......./data/data/ is now 666, the device just constantly force closed eveything and is now in a constant boot loop. So any advice in the best way to fix this? I have tried booting into recovery and doing 'fix permissions' but this does not fix it.
Would fastboot allow me to connect to PC and chmod /data/data/ to the correct permissions? (and what would those be??) Or is it screwed and do I need to factory reset?
Many thanks for any hrlp guys
Have you tried re-flashing your ROM form recovery, this should reset the permissions
To be honest I'm new to Android and don't know which img that would be or how to go about doing it. Would doing this wipe any of my data? I was hoping there would be a simple way of getting a terminal through my pc and chmod from there (if I knew the correct permissions).
fubofo said:
To be honest I'm new to Android and don't know which img that would be or how to go about doing it. Would doing this wipe any of my data? I was hoping there would be a simple way of getting a terminal through my pc and chmod from there (if I knew the correct permissions).
Click to expand...
Click to collapse
fix permissions will do it for the files within the folder so if it where that simple I think it you would have fixed it 666 gives read/write permissions to everyone so I don't see that would have caused your problems, what ROM are you currently running? If it's a custom one simply reflash it, which should preserve all your Data if not you may need to run an RUU for your vendor/market which will wipe everything
ghostofcain said:
fix permissions will do it for the files within the folder so if it where that simple I think it you would have fixed it 666 gives read/write permissions to everyone so I don't see that would have caused your problems, what ROM are you currently running? If it's a custom one simply reflash it, which should preserve all your Data if not you may need to run an RUU for your vendor/market which will wipe everything
Click to expand...
Click to collapse
Thanks for the reply, I'm running stock ROM with eng hboot, recovery obviously and custom kernel. The reason I ask about fastboot chmod is because I'm not 100% 'fix permissions' is working via recovery.
Also, just for knowledge sake, what .img would be for what from my backup?
- .android_secure.img
- boot.img
- cache.img
- data.img
- nandroid.md5
- recovery.img
- system.img
Re-reading your original post, something weird is going on here as running 'fix permissions' shouldn't have caused any grief in the first place, possibly your OC is too aggressive for your CPU? (although it shouldn't be).
Plenty of people have come across the same issue when running 'fix permissions' from ROM Manager. It causes contact pictures to not display in the SMS apps in some cases.
Also, I remember running an option from recovery and it did nothing (even though reported completed) hence why I want to overrule the fix permissions from CM Recovery 2.5.1.3 and try to run commands into the device someway (via fastboot if possible or another method).
I just need to know what permissions should be for /data/data/ and how I would go about running commands to the device. And failiing that, what .img would be needed flashed to get a working device again with as little data lost as possible nd how to go about flashing it... fastboot or recovery update.zip?)
fubofo said:
Plenty of people have come across the same issue when running 'fix permissions' from ROM Manager. It causes contact pictures to not display in the SMS apps in some cases.
Also, I remember running an option from recovery and it did nothing (even though reported completed) hence why I want to overrule the fix permissions from CM Recovery 2.5.1.3 and try to run commands into the device someway (via fastboot if possible or another method).
I just need to know what permissions should be for /data/data/ and how I would go about running commands to the device. And failiing that, what .img would be needed flashed to get a working device again with as little data lost as possible nd how to go about flashing it... fastboot or recovery update.zip?)
Click to expand...
Click to collapse
assuming you are running cM 2.5.1.3 recovery?, have you a nandroid backup to fall back ON, restoring that, from recovery, would be my first step. If not Modaco has a stock ROM that you could try flashing from recovery which should retain your data
ghostofcain said:
assuming you are running cM 2.5.1.3 recovery?, have you a nandroid backup to fall back ON, restoring that, from recovery, would be my first step. If not Modaco has a stock ROM that you could try flashing from recovery which should retain your data
Click to expand...
Click to collapse
Yeah I have backups but from a while ago (first boot to be honest lol). But what should I restore and how? (system.img or data.img? as its /data/data/ that seems screwed)
fubofo said:
Yeah I have backups but from a while ago (first boot to be honest lol). But what should I restore and how? (system.img or data.img? as its /data/data/ that seems screwed)
Click to expand...
Click to collapse
Not sure how a partial restore would go, I normally do a full restore via recovery
OK so I have managed to get it working again. Ran backup form recovery which seemed to allow me to gain adb shell once the backup was completed. From there I chmod 777 /data/data/ and this allowed me to boot the device.
Everything seems to be gone, like contacts and such, but my apps are all there inc. Titanium backup. I have restored all system data from the Titanum backups and am currently running Rom Manager 'fix permissions' to see if that will add the correct permissions to /data/data/ again.
Hopefully I just now need to add my Google / exchange / etc. accounts again to be back to normal.
[UPDATE] - everything now seems to be working fine (except the original SMS contact pictures issue) and my entire device is back to the way it was last week (from Titanium backup I presume).
[UPDATE 2] - have now successfully ran chmod 666 /data/data/com.android.providers.contacts/files/* (after Rom Manager 'fix permissions' and reboot) and SMS contact pictures are all working again. Everything is syncing now so should be back to normal soon!!
on a side note, this obviously shows there is an issue with fix permissions, looks like it needs updated.
I too had the "contact picture" issue after performing the mentioned "fix permissions" command in ROM Manager. By the way, I simply fixed it by manually re-assigning the picture for each contact -- fortunately I have just a couple dozen contacts with picture so it didn't take too long.
capt_harlock77 said:
I too had the "contact picture" issue after performing the mentioned "fix permissions" command in ROM Manager. By the way, I simply fixed it by manually re-assigning the picture for each contact -- fortunately I have just a couple dozen contacts with picture so it didn't take too long.
Click to expand...
Click to collapse
Yeah I tried that too first but it didnt seem to work for me, removed image then reassigned for a number of contacts but nothing worked. It's fixed now so I'll just let this die here for future similair issues.
Trying to restore a NAND in CWM but it says "couldn't find directory, no files found" when I click "restore"
So i did a backup, and it shows up when I then hit "restore" in sdcard/clockworkmod/backup (listed at top of recovery screen) but when I boot and look on my sdcard, it shows the old backups I made in the folder listed, not the one I just made. I can't find the one I just made, even though if I reboot into recovery, it still shows it (the latest) and only it.
Any idea where the newest one is, and why I cant restore the older ones?
Are you running CWM 6.0.1.9?
Also, take a look at http://forum.xda-developers.com/showthread.php?t=1991657.
I am running v6.0.1.9 and the link you posted seems to say that this should be an issue resolved with this version. Though it did tell where to find the new backup.
It lists some adb commands to move the old backups to the new directory, can I just do that in rootexplorer with copy/paste?
TheAtheistReverend said:
I am running v6.0.1.9 and the link you posted seems to say that this should be an issue resolved with this version. Though it did tell where to find the new backup.
It lists some adb commands to move the old backups to the new directory, can I just do that in rootexplorer with copy/paste?
Click to expand...
Click to collapse
I don't see why you couldn't move the files with rootexplorer. Give it a try!
They moved fine
They are seen by recovery, and now I just switched to TeamWin recovery. We'll see if that sees them too.
Are we confident that wiping doesn't clear this location? I'm a little worried that a factory reset or something might wipe the data folder
TheAtheistReverend said:
They moved fine
They are seen by recovery, and now I just switched to TeamWin recovery. We'll see if that sees them too.
Are we confident that wiping doesn't clear this location? I'm a little worried that a factory reset or something might wipe the data folder
Click to expand...
Click to collapse
Please read the following
http://forum.xda-developers.com/showthread.php?p=34794673
If you are worried about losing the backups, copy them to your pc or onto OTG storage. I use cwm and my backups are now in /data/media/clockwork. If you activate multi-user, I think they go to /data/media/0/clockwork, but I can't test. Not sure about the TW recovery.
scott_doyland said:
Please read the following
http://forum.xda-developers.com/showthread.php?p=34794673
Click to expand...
Click to collapse
Confusing But the info is there. I don't like how complicated it ahs gotten to wipe, restore, recover, and flash. It used to be so simple...:silly:
Hi
I did a backup with nexus 4 toolkit before rooting but now when I try to restore my backup it starts backing up but just 1 app and then reeboots without adding any of the other apps. Anyone know an alternate method or whats wrong?
c2h5oh2 said:
Hi
I did a backup with nexus 4 toolkit before rooting but now when I try to restore my backup it starts backing up but just 1 app and then reeboots without adding any of the other apps. Anyone know an alternate method or whats wrong?
Click to expand...
Click to collapse
thats reason # 84261 why you should never use a toolkit.
Well, whats done is done. It seems like it tries to recover some system file that causes a reebot. I will try to restore from recovery mode if the bootloader can restore .ab-files.
Failed to restore .ab file in bootloader. Does anyone have any idea how I can restore the .ab file?
Why would you want to go back to stock? You want to get back the apps you had?
I guess you will have to re-download them... This is what I did : I made a Titanium backup save for my apps, before rooting, and restored it, after rooting.
To restore .ab files install adb and open a command window (or a terminal on linux). Then navigate to the folder where the .ab file is or open the command window there. Connect your phone now powered on to your PC and be sure unknown sources and usb debugging are enabled
Now type
Code:
adb restore nameofyourbackup.ab
Unlock your device, confirm the restore and wait until it has finished
Sent from my Nexus 4 running Android 4.2.2
I shouldn't have used a toolkit :S
I'm having the same issue, I used the toolkit, created a backup from all apps (including system and data) in a .BAK, unlocked, rooted, and now I try to restore with the toolkit, the process triggers my phone's backup but then it restarts and nothing has been restored! I tried HOLO Backup as well, and I'm trying with the SDK method right now.
Is .BAK compatible with full backup? Is there any other way (other than ADB) to restore my info?
Thanks
Edit: Trying with SDK as command prompt didn't recognize adb as a valid command.
Edit: SDK did not work, I guess I just did the same in 3 different ways... any ideas?
Got it!
Titanium tools pro version has an ADB backup extraction. Move the .BAK file to your SD card folder, and then restore the extracted info
So I was able to do a full adb backup when I was on 4.1.2 before I updated to 4.2.2.. I wanted to do another full adb backup again on 4.2.2 before putting a recovery or custom rom on my device so it would be easy to restore back to my completely stock experience (with root) if I choose. But for some reason after letting it run all the way through (I let it run overnight since it takes so long) the backup is nowhere to be found which leads me to believe it failed somewhere along the way, but no errors are reported. Has anybody had this issue or have any advice on what may be going on? I've tried doing:
Adb backup -all
Adb backup -all C:\Users\Wyth\Desktop
Adb backup -all G:\ (external HDD)
Adb backup -all G:\xtzbackup (in case adb backup had some sort of bug saving to the root of the drive)
If anybody has any help or alternative solutions to creating a full system backup I'd appreciate it! Thanks in advance!
If you are going to supply a path and file name, don't forget the -f switch
dph3055 said:
If you are going to supply a path and file name, don't forget the -f switch
Click to expand...
Click to collapse
Thanks, that was absolutely the issue. I guess I did that the first time around but forgot the second. I ended up making the backup and then unlocking the bootloader. Unfortunately I forgot that it would completely wipe the internal storage rather than just a factory reset, so I lost my titanium backups. Tried to do the adb restore, and every time after the first app it would just reboot the device. After trying it many times I ended up using the adb extractor tool to create a tar from the backup. Apparently however the backup was no good because when extracting the tar after getting to a certain part every time it came up with unexpected end of archive. But I at least got most of the titanium backup folder out. Tried copying that to internal storage and it was permission denied. Copied it to external sd, and then on the tablet transferred it to internal storage. Then every time I restored any of the data, when I rebooted the tablet it would go into bootloops. After many ftf flashes and time wasted copying things back and forth all over the place I finally am basically just resigning to starting over. Boot into CWM and made a backup, and find that it makes the clockwork mod backup folder in data/media rather than the proper place in data/media/0 or even data/media/legacy. The option to backup to external sdcard also doesn't work, as it refuses to mount sdcard or external-sdcard. Needless to say the last 24 hours or so has been massive headaches. Is there a newer version of CWM for the tablet than 6.0.3.2? It seems pretty buggy and hard to believe that it is what everyone has been using as the button combination to reboot to recovery doesn't even work.
Btw, I'm trying to do this on the stock sony 4.2.2 firmware for sgp312.
Using kernel and recovery from here:
http://forum.xda-developers.com/showthread.php?t=2433466
with ftf from here:
http://forum.xda-developers.com/showthread.php?t=2424550