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.
Related
After carefully reading several guides, I thought I was ready to try flashing a ROM. Wrong.
I have the Samsung Exhibit II. I tried to flash RebelROM 3.0.9 via CWM, but when it booted up, I had no notification window, and if I try to download an app, it kicks me out to the lock screen.
So I thought I would just go back to the backup I made. Nope. Apparently the backup got glitched up somehow. When I try it says "MD5 mismatch".
Then I thought I would try a different ROM, but I don't have an micro SD card, and I can't enable USB storage without the notification bar.
Does anyone have a solution? I've tried everything I can think of, but I'm very new to Android. I have a micro SD card on the way, so I should be able to install a different ROM from that in a couple days, but I'd like to have a functional phone before then.
Thanks in advance!
Make sure you didn't change the name of the folder for the backup with the md5 mismatch. If you didn't, see here:
http://forum.xda-developers.com/showthread.php?t=714114
This is probably the most noobish thing you've heard all day, but where do I type the code from the post you linked me to?
Also, thanks for the reply.
That's on your computer. You connect your phone to you computer via USB cable, and run the commands through adb. If you don't know what adb & fastboot are, you need to download the Android SDK. They're included there.
OK, got it working, and I get as far as getting into my backup folder, but when I try to proceed, it says "No such file or directory". I must have really messed something up. Any other ideas?
EDIT: I'm positive that I left the backup on the default options.
If you changed the name of the backup folder (I used to do this routinely, to help me identify which backups were from which ROMs), you should change them back. Also, make sure you're not just copy/pasting from the other thread! The line that says
Code:
# cd /sdcard/clockworkmod/backup/[B]2010-06-29.20.22.53[/B]
should be adjusted to match the name of the backup you're trying to restore. Pay particular attention to the bolded folder name.
I never changed the name, and the folder name I used was right. I checked the contents of the backup folder, and I have boot.img, recovery.img, system.ex4.dup and data.ext4.dup. That doesn't seem right, so I think I'm going to have to give up on the backup. Luckily, I made a secondary backup with TitaniumBackup, so I think all I should have to do is install a stock ROM and download Titanium to restore my data.
Is there any way I'd be able to move a file from my PC to my phone via adb? Or should I do something else entirely?
Again, thanks so much for your help.
I just OTA'ed to ICS, and the current root isnt working . I know that one of the prerequisites is to wipe data and cache to get it working, but i want to keep my data, and was hoping that there may be a way to either root the phone and then use titanium backup, or find some other way to back it up. I have tried ADB backup, that finishes in less than a second and creates a backup file that's 1kb big, so thats obviously not working, and suggestions would be helpful (With adb backup, i use the command "adb backup -all -nosystem -apk -f F:/backup.ab")
What method did ya use? This? http://forum.xda-developers.com/showthread.php?t=1742879 I was able to root ma ics with that!
I Also rooted using Lifehacker7's linked post.
May be you are connecting phone in 'mass storage mode', when I rooted, it was in 'MTP Mode'.
May be you need to reinstall Motorola drivers.
NHS2008 said:
I Also rooted using Lifehacker7's linked post.
May be you are connecting phone in 'mass storage mode', when I rooted, it was in 'MTP Mode'.
May be you need to reinstall Motorola drivers.
Click to expand...
Click to collapse
Reinstalled, and also tried in every USB mode (Surprisingly camera also worked).
Version: 6.7.2_GC-220-EDS-3-65
this rom can't be root by "http://forum.xda-developers.com/showthread.php?t=1742879" method.
On the gfan forum they found another method by replacing boot.img "http://bbs.gfan.com/android-5201783-1-1.html"
I'm not sure if this method can be used in other ICS roms or not.
Maeur1 said:
I just OTA'ed to ICS, and the current root isnt working . I know that one of the prerequisites is to wipe data and cache to get it working, but i want to keep my data, and was hoping that there may be a way to either root the phone and then use titanium backup, or find some other way to back it up. I have tried ADB backup, that finishes in less than a second and creates a backup file that's 1kb big, so thats obviously not working, and suggestions would be helpful (With adb backup, i use the command "adb backup -all -nosystem -apk -f F:/backup.ab")
Click to expand...
Click to collapse
Try this method as laid out in the following link:
http://forum.xda-developers.com/showthread.php?t=1779968
MAKE SURE THE MD5 MATCHES.
This SHOULD work. :laugh:
Hi, Im new to this device but right after I got it I did the right thing and voided my warranty Rooted and installed a custom recovery. The recovery has been a bit of a pain but that is a story for another thread.
The problem I am having is that when I try to take a backup from recovery it errors (I forget the error, sorry. ) however the backup is still right there in the backup directory. I tried a second attempt at a backup (to see if it would error again) and these two backups filled my remaining memory. lI of course used my file explorer to delete these extraneous backups-- only to see that they are not deletable. I also tried on the PC. The folder lists read and write in the permissions. I am kind of at a loss as to what to do. IIRC correctly from a while back with this issue the answer lies somewhere in CHMOD, but I cant quite seem figure it out. CD to the directory in a terminal emulator and then CHMOD 777? Thanks for your help in advance.
knoober said:
Hi, Im new to this device but right after I got it I did the right thing and voided my warranty Rooted and installed a custom recovery. The recovery has been a bit of a pain but that is a story for another thread.
The problem I am having is that when I try to take a backup from recovery it errors (I forget the error, sorry. ) however the backup is still right there in the backup directory. I tried a second attempt at a backup (to see if it would error again) and these two backups filled my remaining memory. lI of course used my file explorer to delete these extraneous backups-- only to see that they are not deletable. I also tried on the PC. The folder lists read and write in the permissions. I am kind of at a loss as to what to do. IIRC correctly from a while back with this issue the answer lies somewhere in CHMOD, but I cant quite seem figure it out. CD to the directory in a terminal emulator and then CHMOD 777? Thanks for your help in advance.
Click to expand...
Click to collapse
If you are using TWRP, It is not possible to delete twrp backup images using normal ways. Either you can install esfile explorer and navigate to device/data/media/0/twrp/backups/ and delete from there. Or use file manager in TWRP to delete the backups. I think there is also another option in twrp to view or delete backups.
Sent from my Moto G using Tapatalk 2
Ill check out the other things you said, but Im actually getting this problem in ESfile... Ill report back if I can get at it through the recovery.
Edit: ESfile works. I followed the path you laid out ad got there just fine I didnt realize Id have to take such a roundabout path. Thank you.
I've spent the last couple days searching around to fix this problem, not only on XDA and Google, but in TWRP's Issues and code on GitHub; all to no avail. So here it is:
I have a device with a broken display. The only way I can initiate commands on it are with the power, volume, and home buttons, and with adb. I've installed TWRP on it, and I'm able to boot into it. I'm trying to back up everything on the device I can to a 32GB external SD card in the device's SD card slot. But when I keep getting the following result:
Code:
~ # twrp backup SDBOM
Setting backup options:
System
Data
Boot
Compression is on
Digest Generation is off
Updating partition details...
...done
* Total number of partitions to back up: 3
* Total size of all data: 7976MB
* Available space: 496MB
Not enough free space on storage.
Backup Failed
Done processing script file
The External SD Card has more than enough space for the backup (several times over, in fact), so clearly TWRP is attempting to save the backup to the device's internal storage. It seems, from testing I've done on an identical device with a working display, that twrp backup in the command line saves to the Storage last selected in the graphical version, but since my device's display is broken I can't select the External SD Card as the storage for the backup.
Since I have no display, I also can't do adb backup --twrp, since that requires confirmation on the screen.
Is there any way to select the storage for twrp backup fully through the terminal? For example, is there an environment variable I can set, or something I can pass twrp backup?
I figure this is an easy one to answer, and that it's something really, obviously, simple (so much so that I'll have to hang my head and never show my face here again!). But for the life of me, I can't find it.
Same thing here. In my case I have a working display but my kernel does not allow any touchscreen operations when in recovery so I can see TWRP but not input anything. So the command line is my only way to use TWRP but like you I cannot switch to creating backups to my external SD card.
It seems funny there is no solution to this since having touch screen problems with TWRP seems to be a common issue so how do all those folks with no touch recoveries do their backups?
check to which folder mount yours external SD
and set var "tw_storage_path" with "twrp set"
example "twrp set tw_storage_path /external_sd"
you can find this var in android_bootable_recovery/openrecoveryscript.cpp
also
you can change backup folder
example "twrp set tw_backups_folder /external_sd/all"
can find it in android_bootable_recovery/variables.h
OrBitRo said:
check to which folder mount yours external SD
and set var "tw_storage_path" with "twrp set"
example "twrp set tw_storage_path /external_sd"
you can find this var in android_bootable_recovery/openrecoveryscript.cpp
also
you can change backup folder
example "twrp set tw_backups_folder /external_sd/all"
can find it in android_bootable_recovery/variables.h
Click to expand...
Click to collapse
Hello and thank you very much for helping on this issue.
I gave up on this long ago but it is still of great interest to me since I am still using the same phone and TWRP backup would be welcome. But since so much time has passed since I unpacked the recovery, I am a bit rusty at it. I am an old programmer but my android knowledge is limited, still I did succeed to make the sdcard visible to the recovery (cant remember how but I think I changed its block name in recovery.fstab then for some other reason also had to un-repack) so I can handle such things if I am guided a bit.
So your help is very welcome and also reignited my interest to solve this issue. Problem is I cannot find the "android_bootable_recovery/openrecoveryscript.cpp" script in the unpacked recovery or the phone's file system. I am sure I am missing something silly but googling around did not help me either.
Could you possibly guide me into finding those scripts so I can edit the aforementioned variables?
Thank you very much for your attention and help.
Chris.
cfrantzol said:
(cant remember how but I think I changed its block name in recovery.fstab then for some other reason also had to un-repack) so I can handle such things if I am guided a bit.
Click to expand...
Click to collapse
Nice hack too!
cfrantzol said:
Problem is I cannot find the "android_bootable_recovery/openrecoveryscript.cpp" script in the unpacked recovery or the phone's file system. I am sure I am missing something silly but googling around did not help me either.
Could you possibly guide me into finding those scripts so I can edit the aforementioned variables?
Thank you very much for your attention and help.
Chris.
Click to expand...
Click to collapse
I find it (i have same problem like yours after 6 hours mess in adb and googling ) in sources of twrp on github github.com/omnirom/android_bootable_recovery
And also about factory reset (to whom it may concern) github.com/omnirom/android_bootable_recovery/issues/146
OrBitRo said:
Nice hack too!
I find it (i have same problem like yours after 6 hours mess in adb and googling ) in sources of twrp on github github.com/omnirom/android_bootable_recovery
And also about factory reset (to whom it may concern) github.com/omnirom/android_bootable_recovery/issues/146
Click to expand...
Click to collapse
Hi again.
Okay now I understand, I will download from there and check what I can come up with. I already feel that this will involve some compiling and I wonder how that is going to affect my custom TWRP (which I found at twrp builder). I will step into it and see.
Thanks a lot for your prompt help, I really appreciate.
cfrantzol said:
I already feel that this will involve some compiling and
Click to expand...
Click to collapse
Sorry if i misunderstand you but why compiling? You dont need it. You can change this vars from adb terminal. Boot device into TWRP connect USB to PC run adb shell and you can change vars in shell via commands like this: 'twrp set tw_storage_path /external_sd' and so on.
OrBitRo said:
Sorry if i misunderstand you but why compiling? You dont need it. You can change this vars from adb terminal. Boot device into TWRP connect USB to PC run adb shell and you can change vars in shell via commands like this: 'twrp set tw_storage_path /external_sd' and so on.
Click to expand...
Click to collapse
Oops, I thought I had to change the variable in the source files and then compile the recovery from scratch. This is now great news I will check it tonight.
Thank you again!
EDIT: For anyone who has the same problem I confirm that I checked it and the method above works fine! Kudos to you OrBitRo!
So ive searched for an answer to this but couldnt find it with google/xda.
I tried to install a custom rom.
My first rom install attempt ever on android
It failed with a signal 11 error
So after lots of trouble shooting trying any "fix" I could find suggested.
I read wiping before a rom install was required.
So I made a twrp backup, placed it on my pc, this is where I messed up and nobody in the countless threads I read said
I deleted the twrp backup on device
Then wiped with twrp, following the era proper directions for device allegedly.
Which was wipe everything but internal storage, also read to format in the many topics I perused.
Then found everything was wiped, including /sdcard, and system/OS
WELL I STILL GOT SIGNAL 11 on rom flash attempt via sideload, since the zip got erased on sd.
I did manage to flash a rom, but wouldnt you know it, its a rom that cant connect to pc through usb.
If I try to push the twrp backup folder, it just says error in cmd while in sideload
Anybody know the proper way to do that? Or is it just a case of murphys law getting a right good laugh at my devices expense.
I did read I could use a micro usb to external storage to mount, but I lack that.
I need to restore twrp because I think I need to pull the vendor directory off device to try to overcome the signal 11 error.
Anyway any advice is appreciated and hopefully can serve others in the future.
Thanks and cheers
Re-flash Stock ROM.
Well I dont think the device in question has a stock rom. Or I cant find one at first glance.
I had to roll back the version to unlock bootloader and root.
But that .bin wouldnt help I think.. hmm
Back to the drawing board I guess.
Perks of a decade old device.
Apparently androidmtk.com has stock roms available, but is that site safe to use?
Sorry for my noobiness.
Edit: actually that bin is the stock firmware apparently. I hope at least.
Will try and report back.
Thanks jwoegerbauer
Edit2: that worked flashing the bin. Was able to mount on pc and add the backup back up.
Did have a stumble as without making a backup there wasnt a backups folder. I tried to manually create one, but twrp couldnt see the folder I made.
Not sure if it was the naming. I tried "Backups" but twrp created "BACKUPS"
I just backed up efs since it was smallest to get twrp to make it.
Cool. Now I can backup vendor for rom comparison. Was overstressed for half the day about it, but the solution was simple and right there in front of me.
Thanks again Jwoegerbauer
what do you mean "it's a rom that can't connect to pc through usb"?
what do you mean "was able to mount on pc"?
you have backup of old ROM on pc. what do you want to do with?
No worries alecxs
Yeah I was able to sideload a custom rom but that rom had broken/missing usb drivers so mtp on pc failed.
That was before I knew I had the stock rom.
I needed stock rom to be able to restore with twrp in order to pull vendor folder off original device.
(I need vendor folder to try to fix that broken custom rom)
Just me being a noob. Sorry again.
you're welcome. just asking for clarity.
you have answered one question, so let me give you hint on guesswork.
you can connect device with usb-debugging from developer options. adb is the recommended way to transfer files. MTP is a faulty implemented Microsoft protocol I wouldn't use for large amount of data (for small files is okay).
Android devices cannot mounted since Android 5.0.1 Lollipop as UMS has been dropped in favour of MTP. /sdcard is no longer separate FAT partition but emulated storage in /data/media.
Bear in mind TWRP backup does not include /data/media so one have to backup pictures manually. this can be done from adb.
Code:
adb pull -a /sdcard
For the same reason you will lose /sdcard every time you format /data.
If you're interested to restore backup to different ROM, you cannot use TWRP. backup of /data can only restored to the exact same ROM.
For restoring backup to different ROM use Migrate.
[APP][ROOT][5.0+][1st Nov 2020] Migrate - custom ROM migration tool
Jumping from one custom ROM to another can be a challenging task. So I decided to make an app to simplify the process. Introducing Migrate! Migrate-GPE (v4.0) is on Google Play It was temporarily suspended. Read more here...
forum.xda-developers.com