Database Info

Nandroid Problems

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.

[Q] CWM unable to mount /system

This has been mentioned elsewhere, even by me but I think it has fallen through the cracks. It may be an unrelated problem but when trying to use CWM to do a backup it fails saying that /system cannot be mounted.
The issue it may be related to is that CWM on boot installed via either method fails to stick past the initial reboot. It looks to me that it is restoring an image on start up each time undoing any changes. It must not be changing everything because the root sticks. I have made sure init.d support has been installed. The phone is an AT&T branded MB865, has been rooted and is running stock 2.3.6 firmware.
Any pointers will be appreciated and I come from an embedded Linux background so I'm willing to help out, but why re-invent the wheel if this has already been solved.

cdlees said:
This has been mentioned elsewhere, even by me but I think it has fallen through the cracks. It may be an unrelated problem but when trying to use CWM to do a backup it fails saying that /system cannot be mounted.
The issue it may be related to is that CWM on boot installed via either method fails to stick past the initial reboot. It looks to me that it is restoring an image on start up each time undoing any changes. It must not be changing everything because the root sticks. I have made sure init.d support has been installed. The phone is an AT&T branded MB865, has been rooted and is running stock 2.3.6 firmware.
Any pointers will be appreciated and I come from an embedded Linux background so I'm willing to help out, but why re-invent the wheel if this has already been solved.
Click to expand...
Click to collapse
Update your busybox .

I had thought of that, running BusyBox 1.20, 1.20.1 fails to install. As 1.20 is fairly recent I doubt this is the problem. The initial install of CWM via Power Boost works, so busybox is installed correctly. An old version of busy box wouldn't explain the not being able to mount /system as as far as I know it isn't used by CWM for this purpose, but I could be wrong. But it could explain the CWM not sticking problem.

Further investigation shows that the system partition does not change between doing a PowerBoost CWM install and after a reboot meaning that there is nothing screwy going on like the boot sequence over writing files in system so that CWM isn't persistent. Can anyone enlighten me on the boot sequence so I can take a look to see if anything is getting over written?
This of course gets me no closer on why CWM can't mount system but it is just one of two problems.

cdlees said:
Further investigation shows that the system partition does not change between doing a PowerBoost CWM install and after a reboot meaning that there is nothing screwy going on like the boot sequence over writing files in system so that CWM isn't persistent. Can anyone enlighten me on the boot sequence so I can take a look to see if anything is getting over written?
This of course gets me no closer on why CWM can't mount system but it is just one of two problems.
Click to expand...
Click to collapse
Have you tried "fix permissions" in cwm?.then reboot and see if it still gives you that error when you go back into cwm
Sent from my MB865 using xda premium

I'm pretty sure I had already tried all that, but just to be sure I did it all again, here is what happened
PowerBoost CWM install
Reboot into CWM
CWM Fix permissions
CWM recovery restart
CWM backup
Failed due to not being able to mount /system
Power cycled, didn't boot into CWM
Since permissions may have changed once CWM Fix permissions had been run
PowerBoost CWM install
Reboot
Enters CWM
Reboot
Didn't boot into CWM
Surely I'm not the only one seeing this problem?

cdlees said:
I'm pretty sure I had already tried all that, but just to be sure I did it all again, here is what happened
PowerBoost CWM install
Reboot into CWM
CWM Fix permissions
CWM recovery restart
CWM backup
Failed due to not being able to mount /system
Power cycled, didn't boot into CWM
Since permissions may have changed once CWM Fix permissions had been run
PowerBoost CWM install
Reboot
Enters CWM
Reboot
Didn't boot into CWM
Surely I'm not the only one seeing this problem?
Click to expand...
Click to collapse
Well once u reboot your phone it goes into cwm. When u reboot from cwm its suppose to go into rom not cwm again.
Sent from my MB865 using xda premium

Have u tried manually mounting system in cwm and see what happens?
Also what version of busybox do u have installed? . Should be 19.4. Nothing higher.
Sent from my MB865 using xda premium

rdavisct said:
Well once u reboot your phone it goes into cwm. When u reboot from cwm its suppose to go into rom not cwm again.
Click to expand...
Click to collapse
I realise this but I was under the impression that if the phone is power cycled or reboot from Android then it will go into CWM on restart.
Still doesn't explain the inability to mount /system

rdavisct said:
Have u tried manually mounting system in cwm and see what happens?
Also what version of busybox do u have installed? . Should be 19.4. Nothing higher.
Click to expand...
Click to collapse
I'm running BusyBox 1.19.4. I just tried to manually mount /system from CWM, same problem. Just to make sure that mounting works I mounted a few other things that were not already mounted.

cdlees said:
I'm running BusyBox 1.19.4. I just tried to manually mount /system from CWM, same problem. Just to make sure that mounting works I mounted a few other things that were not already mounted.
Click to expand...
Click to collapse
Id say rsd flash 2.3.5 . Root. Install atrix bootstrapper. And see if problem persists.
Sent from my MB865 using xda premium

Ok, reflashed back to 2.3.5, rooted, Bootstraped, tried to mount /system from CWM, no luck, same error. Tried to install CWM on boot using the zip from CWM, didn't seem to work. Tried the fix permissions script from CWM, still doesn't work.
There is something up with this phone, is it possible that Motorola has decided to be extra evil.

I till haven't gotten very far with this but I have some more information on what may be the issue. I can get it to update the system partition by flashing a zip. I decided to give it a go with SCV6 as I was sure I'd be able to recover if it failed. It flashed just fine but on reboot it dropped out to the fastboot screen. This is where I decided to get creative, I mounted the system.img file from from the stock fimware, deleted its contents and replaced it with what is in the SCV6 zip system directory, after all this is what CWM will be doing as far as I could tell. I then flashed this file using moto-fastboot. It failed on boot dropping out at fastboot again.
Running out of time for the day I decide to just restore it back to stock, I have a Linux script to automate the process, on completion, same failure. What had happened is I had mounted the system.img file to look inside and then unmounted it, and this may have changed a signature or checksum in the filesystem so it failed to boot. Re-extracting the system.img file and flashing again worked fine.
Are there different versions of the bootloader that do different things? Mine just being a total pain and not allowing much at all.

Just realised the install script puts in a whole pile of symlinks, not having them would cause a boot failure on creating the image the way I did. It will be possible to create an image with said symlinks.
This though fails to explain while mounting and then unmounting the system.img makes it fail.

I may just be talking to myself here but I have some relevant information relating to the original problem of not being able to mount /system which is why flashing doesn't work as well as the flashing scripts don't actually check to see if the system partition is mounted, they just assume it is.
In CWM if you try to mount /system then look at the log it says
mount: mounting /dev/block/mmcblk1p20 on /system failed: Invalid argument
Now the question is, what is the mount line it is trying to execute and which argument is invalid? Can someone with a working phone go into CWM, unmount /system if its mounted by default and then mount it, look at the log and tell me what it says regarding the mounting of system.
Here is the really interesting part, once the phone has booted and checking what is actually mounted on /system its /dev/block/mmcblk1p21, so CWM is trying to mount the wrong partition

I worked out the problem, I was using the Razr bootstrap which obviously mounts a different partition as system, I had followed some instructions that I read somewhere that the Razr version worked and gave a link to said package. Once I swapped to the atrix 2 version it all works, I'll attempt to install SCV6 tomorrow night when I have some time.

can't mount /system!
[/COLOR]
cdlees said:
I till haven't gotten very far with this but I have some more information on what may be the issue. I can get it to update the system partition by flashing a zip. I decided to give it a go with SCV6 as I was sure I'd be able to recover if it failed. It flashed just fine but on reboot it dropped out to the fastboot screen. This is where I decided to get creative, I mounted the system.img file from from the stock fimware, deleted its contents and replaced it with what is in the SCV6 zip system directory, after all this is what CWM will be doing as far as I could tell. I then flashed this file using moto-fastboot. It failed on boot dropping out at fastboot again.
Running out of time for the day I decide to just restore it back to stock, I have a Linux script to automate the process, on completion, same failure. What had happened is I had mounted the system.img file to look inside and then unmounted it, and this may have changed a signature or checksum in the filesystem so it failed to boot. Re-extracting the system.img file and flashing again worked fine.
Are there different versions of the bootloader that do different things? Mine just being a total pain and not allowing much at all.
Click to expand...
Click to collapse
Can you please post the link/s, i have the same problem as you

CWM restore issues (large data backup file)

I am not sure whether anyone else encountered this, but I am having an epic failure restoring a backup made with Rogue XM Recovery 1.3.0 (CWM-based v5.0.2.7).
The backup proceeded without errors.
The symptom is a beginning of restore followed by this error message:
Code:
Error restoring /data!
Under the hood: tar is complaining that the file is too large (my /data backup weighs in at ~3GB) with the following error from the recovery log:
Code:
tar: seek failure: Value too large for defined data type
I saw remarks here and there that 2GB is the size limit for the version of tar included in busybox (i.e. large file support is missing). Can anyone verify whether this is true?
If so, anyone relying on CWM for backups is screwed if their /data is too big.
I verified that the backup did, in fact succeed (i.e. I have a data.ext4.tar file). At the moment I am trying to restore by re-tarring it piecemeal.
Will see how it goes.
In the meantime: does anyone successfully use a different recovery for large-file backup?

feisty_noodle said:
I am not sure whether anyone else encountered this, but I am having an epic failure restoring a backup made with Rogue XM Recovery 1.3.0 (CWM-based v5.0.2.7).
The backup proceeded without errors.
The symptom is a beginning of restore followed by this error message:
Code:
Error restoring /data!
Under the hood: tar is complaining that the file is too large (my /data backup weighs in at ~3GB) with the following error from the recovery log:
Code:
tar: seek failure: Value too large for defined data type
I saw remarks here and there that 2GB is the size limit for the version of tar included in busybox (i.e. large file support is missing). Can anyone verify whether this is true?
If so, anyone relying on CWM for backups is screwed if their /data is too big.
I verified that the backup did, in fact succeed (i.e. I have a data.ext4.tar file). At the moment I am trying to restore by re-tarring it piecemeal.
Will see how it goes.
In the meantime: does anyone successfully use a different recovery for large-file backup?
Click to expand...
Click to collapse
I have used TWRP to restore 650mb system+3gb data (including movies n songs).... restoring worked fine but at the same time one of my attempts failed n I was stuck at Asus screen.. so very rarely everyone is bound to hit recovery error issues I guess... but mostly it works like a charm...
Sent from my Transformer TF101 using xda app-developers app

[A510/A511] [WIP] Stock ROM dumps - Get back to factory state

As we now have functional recovery options on our tablets, and people will inevitably mess things up with their device, we need to get a way to get your tablets back to factory condition. But I need your help with this!
What do you want?
Here's my idea: We have all seen various ZIPs floating around, most of them leaked from somewhere. The problem with these is that you can't use OTA updates, and I'm not sure what Acer Service Center thinks of custom ROM installs. What I want is to build a list of software that is officially distributed by Acer, is OTA-updateable, etc. For this reason, I want people that have not yet modified their tablets (except root) to provide image dumps of their /system, /boot, /flexrom, and /recovery partition. It's really easy to do, and you'll help yourself and others when they get into trouble.
Can I help?
Answer all of the following questions. If at one point the answer is "Sorry, you can't help", well... You can't help
Is your device unlocked and rooted? Yes - You can help! / No - You can still help, but you need to unlock and root your device.
Do you have the original Acer ROM installed on your device? Yes - You can help! / No - Sorry, you can't help
Have you received the latest OTA updates for your device? Yes - You can help! / No - You can help as well!
Have you removed any apps or files from the /system or /flexrom partition? Yes - Sorry, you can't help / No - You can help!
Have you installed a custom recovery image? Yes - You can still help, as long as everything else is still original / No - You can help!
Okay, so I can help, now what?
If you can and are willing to help (remember, it could save your own ass one day), follow the instructions below. If you get stuck or simply don't know where to start but are willing to help, let us know in this thread and I'm sure we can all help eachother out.
This will not gather any personal data from you. Personal data is stored on the /data partition, which we don't need, so: No worries!
Root your device, if you haven't already.
Connect your tablet to your computer via ADB
Type the following command: adb shell. You are now logged into your tablet. You can exit at any time by typing exit and hitting ENTER.
Type the following command: dd if=/dev/block/mmcblk0p2 of=/sdcard/boot.img. This will copy your /boot partition to a file called boot.img on your internal storage. This one will be fast, it only has about 8MB to copy.
This step can be skipped if you have a custom recovery! Type the following command: dd if=/dev/block/mmcblk0p1 of=/sdcard/recovery.img. This will copy your /recovery partition to a file called recovery.img on your internal storage. This one will be fast as well, it only has about 6MB to copy.
Type the following command: dd if=/dev/block/mmcblk0p3 of=/sdcard/system.img. This will copy your /system partition to a file called system.img on your internal storage. This one will take a bit longer, it has about 360MB to copy.
Type the following command: dd if=/dev/block/mmcblk0p6 of=/sdcard/flexrom.img. This will copy your /flexrom partition to a file called flexrom.img on your internal storage. This one will take a bit longer as well, it has about 360MB to copy.
Type exit to exit the ADB shell. Copy the four .img files from your tablet (internal storage) to your computer. You might have to reboot your tablet if the files don't show up.
ZIP or RAR these files, and upload them somewhere. If you can't find a place to store them: send me a private message or reply in this thread and we'll arrange something else. If you have uploaded the files somewhere: again, send me a private message or reply in this thread.
So now what?
When I receive your files, I will package them into an update.zip that can be flashed from custom recoveries. This will then restore everything (including the custom recovery) to factory state, which can help you in getting your device back to stock.
What versions do you have already?
Acer_AV041_A510_1.044.00_WW_GEN1 (download links will follow shortly)
Acer_AV041_A510_1.098.00_EMEA_CUS1 (download links will follow shortly)
Acer_AV041_A510_1.099.00_EMEA_DE (download links will follow shortly)

The idea sounds great so far. But I have a small problem to make a complete backup for my a511.
Your linked root tutorial for the procedure is only for a100/a510 and doesn't work for a511, as I understand.
The tutorial for rooting the a511 needs first to flash a CWM.
http://forum.xda-developers.com/showthread.php?t=1729432
So it isn't possible for us to backup the recovery partition, right ?
I have the stock Acer_AV041_511_1.028.00_EMEA_DE on my device.
Is it even possible to backup and recover the baseband ?
I'm very interested in your CWM recovery for a511 too, but since many guys f++++d up their device now, I want to make sure that my device will not goes the same way.

i can help, n my tab is rooted.
but i don understand the first step: Connect your tablet to your computer via ADB

What about if we have removed system apps (such as the antivirus that comes with the tablet). It wouldn't be a complete dump if it didn't include those.
I have root and am happy to provide a dump, but I did uninstall several of the crappier pre-installed apps that came with my tablet.

scorpio16v said:
The idea sounds great so far. But I have a small problem to make a complete backup for my a511.
Your linked root tutorial for the procedure is only for a100/a510 and doesn't work for a511, as I understand.
The tutorial for rooting the a511 needs first to flash a CWM.
http://forum.xda-developers.com/showthread.php?t=1729432
So it isn't possible for us to backup the recovery partition, right ?
I have the stock Acer_AV041_511_1.028.00_EMEA_DE on my device.
Is it even possible to backup and recover the baseband ?
I'm very interested in your CWM recovery for a511 too, but since many guys f++++d up their device now, I want to make sure that my device will not goes the same way.
Click to expand...
Click to collapse
Hi, your device will not brick, I can send you a test A511 recovery if you want. Worst that can happen is that recovery won't boot, but in that case you can simply put back recovery. Send me a private message and we can work something out.

scae said:
What about if we have removed system apps (such as the antivirus that comes with the tablet). It wouldn't be a complete dump if it didn't include those.
I have root and am happy to provide a dump, but I did uninstall several of the crappier pre-installed apps that came with my tablet.
Click to expand...
Click to collapse
Then it's of no use, unless you have a backup of your pre-installed apps. Removing apps from the /system or /flexrom partition is not recommended, and you gain nothing by it: You only gain space on read-only filesystems which you won't use in 99% of situations, and you've now broken OTA's for yourself as well, as OTA's will only install when apps are present unless you start modifying OTA files.
The 'correct' way to get rid of pre-installed apps is simply freezing them, either from the settings menu or with an app like Titanium Backup. This will make it seem like they're not there (so they don't use resources at all), but the APKs don't get removed.
So unfortunately, we can't use your dumps to restore devices to factory state. Unless, ofcourse, you've made a backup of the apps somewhere.

skymario said:
i can help, n my tab is rooted.
but i don understand the first step: Connect your tablet to your computer via ADB
Click to expand...
Click to collapse
Do you have ADB or the Android SDK installed?

NoThrills said:
Do you have ADB or the Android SDK installed?
Click to expand...
Click to collapse
I just learned ADB, n successful install ur CWM, later will try to dump my stock Rom to u.
My stock Rom version 1.073 ww gen1

does it matter if the system apps have been frozen or do they need to be unfrozen first?

I have flashed that remove stock recovery mod so the stock rom doesn't keep overwriting cwm on reboot. Does that disqualify me? If not I'll dump my rom for you when I get home.
I'm on this rom version:
ro.build.pandora.id=Acer_AV041_A510_RV28RC04_PA_CUS1
ro.build.flexrom.id=Acer_AV041_A510_1.076.00_PA_CUS1

I unlocked bootloader,rooted,installed cwm then backed up my stock rom.Could i restore my stock rom then be able to send you those fills
and return to total stock.

NoThrills said:
Hi, your device will not brick, I can send you a test A511 recovery if you want. Worst that can happen is that recovery won't boot, but in that case you can simply put back recovery. Send me a private message and we can work something out.
Click to expand...
Click to collapse
i think he mean that the a511 recovery doesn't work properly....you can flash a zip, but nearly all other options brick the device
i have a a511 too with Acer_AV041_A511_1.028.00.EMEA_DE and can help with testing or something else

I have Acer AV041_A510_1.079.00_PA_CA. (Canada)
I have not done a thing to it because it is a replacement for the Galaxy Note I bricked trying to upgrade from GB to ICS, too early.
I might try again if I was sure I could get back to where I am, using your process.
I assume that your Root link is comprehensive but I also need reassurance on how to ADB.
[email protected]
Sent from my A510

blgblade said:
i think he mean that the a511 recovery doesn't work properly....you can flash a zip, but nearly all other options brick the device
Click to expand...
Click to collapse
No, as I understand, the only working methode to root the a511 is to bootloader unlock, flash the custom recovery and then the root.zip.
Maybe I'm wrong and there is another working way to root the device ?
The problem is simply, that we lost the stock recovery before we have a backup from it.
If we have another root way for a511, the backup of stock firmware is done in a few minutes and from this point we can test the a511 custom recovery from NoThrills.

To the A511 owners: Technically, if you have a install-recovery.sh file on your device, the device will always flash recovery back from the boot.img.
In theory: To test, one could simply overwrite the stock recovery with my Recovery (not the other ones, they will brick your device) and then when you reboot, your device will overwrite the recovery with the stock one again. So you really don't need a backup of the recovery partition.
As long as you don't let your device fully boot (so, stay in recovery) there's plenty of time to test if the recovery works or not. If it doesn't, simply reset your device and it will flash back the original recovery (again: provided there is a install-recovery.sh in your /system partition).
So again, if anyone is willing to test, let me know

NoThrills said:
To the A511 owners: Technically, if you have a install-recovery.sh file on your device, the device will always flash recovery back from the boot.img.
Click to expand...
Click to collapse
I can't find a install-recovery.sh in /system partition on my a511. Search on root-explorer can't find one on the device.
Even NOT on /system/etc like on other devices.

NoThrills said:
So unfortunately, we can't use your dumps to restore devices to factory state. Unless, ofcourse, you've made a backup of the apps somewhere.
Click to expand...
Click to collapse
Ah damn, I did back them up via titanium but it doesn't seem to want to restore them - it just sits there say restoring app.

scorpio16v said:
I can't find a install-recovery.sh in /system partition on my a511. Search on root-explorer can't find one on the device.
Even NOT on /system/etc like on other devices.
Click to expand...
Click to collapse
Yeah, I meant /system/etc... That's weird, I'd figure Acer would use the same system on the A511... Let me check one of the leaked ROMs...

Hello,
I have an stock Acer_AV041_A510_1.098.00_EMEA_CUS1, there we go for the files
Host file is not the stock version, it was edited by AdAway.
Can you make a version without recovery overwritting ?
I thinks a lot of people want to try some roms... just for testing...
Acer_AV041_A510_1.098.00_EMEA_CUS1 boot && system && flexroom:
http :// dl.free.fr/jDEmTNSD4
Have Fun

Hello,
I have the same rom without root or unlocked bootloader or moded recovery so if the above on does not make it I'll upload mine.
Sent from my A510 using xda app-developers app

Why does restoring my backup.ab get stuck at restoring efs2?

I made a backup.ab straight to my PC from twrp since I didn't have enough storage on my phone, not thinking much of it. Now when I try to restore it, everything goes fine except for the last part where twrp tries to restore efs2 and gets stuck on it. I can't install other ROMs after this either and my phone is practically a brick right now. What can I do? Any kind of help is appreciated.

.AB - files are TAR-archives. Hence you can try to extract them by means of Android's TAR applet. TAR is also available in Windows OS as command line tool.

Have you found a way to fix this?

-sandro- said:
Have you found a way to fix this?
Click to expand...
Click to collapse
I realized I backed up both System and System Image partitions. I think my tissot device only supported System Image backups so that's why it was messing up.