Nandroid+Ext backup fails!

[Guest TylerDurdenK]

What gives, it keeps failing and telling me

Error: run 'nandroid-mobile.sh' via adb!

[Guest kendon]

What gives, it keeps failing and telling me

i think we stopped here:

move recovery.log to sdcard (somewhere in recovery image menu), then mount sdcard on pc and post the log here.

so it is your turn now.

btw in that thread you said that you don't have an ext4 partition, does that mean you have an ext3 or ext2 partition or no extN partition at all?

i can walk you through this, but you need to work with me... (<- recovery.log!)

[Guest TylerDurdenK]

i think we stopped here:

so it is your turn now.

btw in that thread you said that you don't have an ext4 partition, does that mean you have an ext3 or ext2 partition or no extN partition at all?

i can walk you through this, but you need to work with me... (<- recovery.log!)

That was a different thread, but I suppose the same error.

I didn't have an EXT4 partition, but I do now. I'll get the log for you, and post it asap. Thanks for your help.

Edited January 7, 2010 by TylerDurdenK

[Guest TylerDurdenK]

Here you are.

Starting recovery on Thu Jan 7 21:36:39 2010

can't open /dev/tty0: No such file or directory

framebuffer: fd 3 (320 x 480)

Build : RA-hero-v1.5.2

Fixing execute permissions for /cache

I:Set boot command "boot-recovery"

Command: "/sbin/recovery"

ro.secure=0

ro.allow.mock.location=0

ro.debuggable=0

persist.service.adb.enable=1

ro.ril.ecc.HTC-WWE=999

ro.build.id=CUPCAKE

ro.build.display.id=CUPCAKE.eng.u70000.20090827.103405

ro.build.version.incremental=eng.u70000.20090827.103405

ro.build.version.sdk=3

ro.build.version.release=1.5

ro.build.date=Thu Aug 27 10:35:04 CST 2009

ro.build.date.utc=1251340504

ro.build.type=user

ro.build.user=u70000

ro.build.host=Android-X02

ro.build.tags=test-keys

ro.product.model=HTC Hero

ro.product.brand=htc_wwe

ro.product.name=htc_hero

ro.product.device=hero

ro.product.board=hero

ro.product.manufacturer=HTC

ro.product.locale.language=

ro.product.locale.region=

ro.board.platform=msm7k

ro.build.product=hero

ro.build.description=2.73.405.5 146733 CL#61267 release-keys

ro.build.changelist=61267

ro.product.ua=

ro.build.fingerprint=htc_wwe/htc_hero/hero/hero:1.5/2.73.405.5/61267:user/test-keys

keyguard.no_require_sim=1

rild.libpath=/system/lib/libhtc_ril.so

ro.ril.hep=1

wifi.interface=tiwlan0

ro.ril.htcmaskw1.bitmask=4294967295

ro.ril.htcmaskw1=14449

ro.ril.hsupa.category=5

wifi.supplicant_scan_interval=45

ro.sf.lcd_density=160

ro.com.google.locationfeatures=1

persist.service.mount.playsnd=0

settings.display.autobacklight=1

settings.display.brightness=102

ro.ril.def.agps.mode=2

ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html

ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html

ro.com.google.networklocation=1

ro.config.ringtone=Innovation.mp3

ro.config.notification_sound=Color.mp3

ro.config.alarm_sound=Light.mp3

ro.config.cal_notification=Vector.mp3

ro.config.msg_notification=Ascend.mp3

ro.setupwizard.mode=DISABLED

ro.com.google.clientidbase=android-htc

ro.config.sync=yes

net.bt.name=Android

net.change=net.bt.name

dalvik.vm.stack-trace-file=/data/anr/traces.txt

ro.modversion=RA-hero-v1.5.2

ro.factorytest=0

ro.serialno=HT99PL900363

ro.bootmode=recovery_manual

ro.baseband=6.35.09.26

ro.carrier=TMUK

ro.bootloader=1.76.0007

ro.hardware=hero

ro.revision=128

ro.cid=T-MOB005

init.svc.recovery=running

init.svc.adbd=running

I:Set boot command ""

I:Set boot command ""

Move recovery.log to SD

Press HOME to confirm,

any other key to abort.

Moving : .

[Guest kendon]

Here you are.

from what i see i'd guess that you just booted into recovery and copied the log, as the only activity in your log is the copying of the log itself. you need to try a backup first, otherwise there is nothing in the log to examine... good n8!

[Guest TylerDurdenK]

from what i see i'd guess that you just booted into recovery and copied the log, as the only activity in your log is the copying of the log itself. you need to try a backup first, otherwise there is nothing in the log to examine... good n8!

Have you read the title to this thread?

If you had you would realise that I have tried the backup and it fails.

Edited January 8, 2010 by TylerDurdenK

[Guest GodsDevil]

You are supposed to perform a backup again...let it fail...THEN create a log without rebooting and post THAT log here. :)

[Guest kendon]

Have you read the title to this thread?

If you had you would realise that I have tried the backup and it fails.

you gotta work on your attitude dude. there is nothing of a failed backup in your log, so either your phone is so special that it doesn't log its errors or you're doing it wrong. actually you ARE doing it wrong, otherwise it would work. it is not me who doesn't get how it works, it is you, so maybe you should dial your tone back a little bit :)

[Guest ptruman]

you gotta work on your attitude dude. there is nothing of a failed backup in your log, so either your phone is so special that it doesn't log its errors or you're doing it wrong. actually you ARE doing it wrong, otherwise it would work. it is not me who doesn't get how it works, it is you, so maybe you should dial your tone back a little bit :)

For the OP (not kendon) : read http://forum.xda-developers.com/showthread.php?t=561124 (Amon Ra's actual thread)

It says :

For those with ext4 issues, try running this in shell :

tune2fs -E test_fs /dev/block/mmcblk0p2

THEN run the nandroid+ext backup. Works for me - granted I have to wait maybe 10 secs for the mount to sort itself, but it works.

(and so it's painfully clear, run that from the recovery/adb shell, when Amon Ra has booted)

Edited January 8, 2010 by ptruman

[Guest CitizenLee]

I've had a backup fail on me before so I just deleted the nandroid files from my SD and tried again... worked fine.

[Guest TylerDurdenK]

you gotta work on your attitude dude. there is nothing of a failed backup in your log, so either your phone is so special that it doesn't log its errors or you're doing it wrong. actually you ARE doing it wrong, otherwise it would work. it is not me who doesn't get how it works, it is you, so maybe you should dial your tone back a little bit B)

Sorry if it came across like that, and thanks for the help.

You are supposed to perform a backup again...let it fail...THEN create a log without rebooting and post THAT log here. :)

Pretty sure I had just tried a backup, but I'll do it again and repost the log just to make sure.

[Guest TylerDurdenK]

Okay, hopefully this has the details you need.

Starting recovery on Fri Jan 8 10:57:47 2010

can't open /dev/tty0: No such file or directory

framebuffer: fd 3 (320 x 480)

Build : RA-hero-v1.5.2

Fixing execute permissions for /cache

I:Set boot command "boot-recovery"

Command: "/sbin/recovery"

ro.secure=0

ro.allow.mock.location=0

ro.debuggable=0

persist.service.adb.enable=1

ro.ril.ecc.HTC-WWE=999

ro.build.id=CUPCAKE

ro.build.display.id=CUPCAKE.eng.u70000.20090827.103405

ro.build.version.incremental=eng.u70000.20090827.103405

ro.build.version.sdk=3

ro.build.version.release=1.5

ro.build.date=Thu Aug 27 10:35:04 CST 2009

ro.build.date.utc=1251340504

ro.build.type=user

ro.build.user=u70000

ro.build.host=Android-X02

ro.build.tags=test-keys

ro.product.model=HTC Hero

ro.product.brand=htc_wwe

ro.product.name=htc_hero

ro.product.device=hero

ro.product.board=hero

ro.product.manufacturer=HTC

ro.product.locale.language=

ro.product.locale.region=

ro.board.platform=msm7k

ro.build.product=hero

ro.build.description=2.73.405.5 146733 CL#61267 release-keys

ro.build.changelist=61267

ro.product.ua=

ro.build.fingerprint=htc_wwe/htc_hero/hero/hero:1.5/2.73.405.5/61267:user/test-keys

keyguard.no_require_sim=1

rild.libpath=/system/lib/libhtc_ril.so

ro.ril.hep=1

wifi.interface=tiwlan0

ro.ril.htcmaskw1.bitmask=4294967295

ro.ril.htcmaskw1=14449

ro.ril.hsupa.category=5

wifi.supplicant_scan_interval=45

ro.sf.lcd_density=160

ro.com.google.locationfeatures=1

persist.service.mount.playsnd=0

settings.display.autobacklight=1

settings.display.brightness=102

ro.ril.def.agps.mode=2

ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html

ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html

ro.com.google.networklocation=1

ro.config.ringtone=Innovation.mp3

ro.config.notification_sound=Color.mp3

ro.config.alarm_sound=Light.mp3

ro.config.cal_notification=Vector.mp3

ro.config.msg_notification=Ascend.mp3

ro.setupwizard.mode=DISABLED

ro.com.google.clientidbase=android-htc

ro.config.sync=yes

net.bt.name=Android

net.change=net.bt.name

dalvik.vm.stack-trace-file=/data/anr/traces.txt

ro.modversion=RA-hero-v1.5.2

ro.factorytest=0

ro.serialno=HT99PL900363

ro.bootmode=recovery_manual

ro.baseband=6.35.09.26

ro.carrier=TMUK

ro.bootloader=1.76.0007

ro.hardware=hero

ro.revision=128

ro.cid=T-MOB005

init.svc.recovery=running

init.svc.adbd=running

adb.connected=

I:Set boot command ""

I:Set boot command ""

Create Nandroid + ext backup?

Press HOME to confirm,

any other key to abort.

Performing backup : .

nandroid-mobile v2.2.1

Using G1 keyboard, enter a prefix substring and then <CR>

or just <CR> to accept default: Accepting default.

Using - prefix to create a backup folder

mounting system and data read-only, sdcard read-write

checking free space on sdcard

..Dumping boot to /sdcard/nandroid/HT99PL900363/BCDEMRS-20100108-1057/boot.img.....done

...Dumping recovery to /sdcard/nandroid/HT99PL900363/BCDEMRS-20100108-1057/recovery.img.....done

.Dumping misc to /sdcard/nandroid/HT99PL900363/BCDEMRS-20100108-1057/misc.img....done

Dumping system to /sdcard/nandroid/HT99PL900363/BCDEMRS-20100108-1057/system.img....................................................done

Dumping data to /sdcard/nandroid/HT99PL900363/BCDEMRS-20100108-1057/data.img.......................................done

Dumping cache to /sdcard/nandroid/HT99PL900363/BCDEMRS-20100108-1057/cache.img...done

Storing the ext2(Apps, Dalvik-cache) contents in the backup folder.

Warning: --ext2 specified but unable to mount the ext2 partition.

Error : Run 'nandroid-mobile.sh' via adb!

I:Set boot command ""

I:Set boot command ""

I:Set boot command ""

Move recovery.log to SD

Press HOME to confirm,

any other key to abort.

Moving : .unmounting /system

unmounting /sdcard

unmounting /data

[Guest TylerDurdenK]

I guess this is the important bit.

Storing the ext2(Apps, Dalvik-cache) contents in the backup folder.

Warning: --ext2 specified but unable to mount the ext2 partition.

Error : Run 'nandroid-mobile.sh' via adb!

I notice it is looking for ext2 contents, but I upgraded to ext3 and then to ext4. Am I a moron for doing that?

[Guest kendon]

Sorry if it came across like that, and thanks for the help.

okay, no problem. the log doesn't show what i expected, there is no error mounting the ext partition. nevertheless you should try this:

For those with ext4 issues, try running this in shell :

tune2fs -E test_fs /dev/block/mmcblk0p2

from here: http://forum.xda-developers.com/showthread.php?t=561124

[Guest TylerDurdenK]

okay, no problem. the log doesn't show what i expected, there is no error mounting the ext partition. nevertheless you should try this:

tune2fs -E test_fs /dev/block/mmcblk0p2

from here: http://forum.xda-developers.com/showthread.php?t=561124

That's sorted it. Thanks

Edited January 8, 2010 by TylerDurdenK

[Guest kendon]

That's sorted it. Thanks

glad i could help. not so hard, wasn't it? :)

[Guest Fleming]

Sadly, I have the same problem, and 'tune2fs -E test_fs /dev/block/mmcblk0p2' did not fix it. I have also tried doing what it says, but do not fully understand what it wants me to do :S

I get up to

"Using G1 Keyboard, enter a unique name substring to change it and <CR> or just <CR> to accept:"

I tried enter, which seemed to work, until;

"error: /sdcard/nandroid/HT...64/BC...27/nandroid.md5 not found, cannot verify backup data"

Any Ideas?

[Guest kendon]

Any Ideas?

posting your recovery.log comes to mind...

Edited January 9, 2010 by kendon

[Guest Fleming]

Don't worry, I read you post on XDA about how to do the restore manually via adb, that works. Thanks