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

[Guest hyakamaru]

Every time I try to run backup on recovery mode, I get this error:

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

E:Can't mount CACHE:recovery/log

E:Can't open CACHE:recovery/log

E:Can't find MISC:

W:Can't unlink CACHE:recovery/command

I've tried MANY different things, like:

1. Erase & re-flash the recovery ROM

2. Rebooting the device using the Power+Menu+End Call buttons, as stated here

3. Using fastboot to restart the device

4. Using a custom ROM to flash the recovery image.

5. [edit] Charging my battery full

6. I don't remember the rest..

I'm using a CHT8000 (U8220) on Android 1.5.

The recovery log is attached for your reference.

Please help. I've been at this for days now. Going insane...

..

recovery.log.txt

Edited June 7, 2011 by Paul

[Guest MRond]

Hey,

I've had the same problem a while a go.

Try to charge your battery full. it sound wierd , but it works for me,

Greeatz

[Guest hyakamaru]

Hey,

I've had the same problem a while a go.

Try to charge your battery full. it sound wierd , but it works for me,

Greeatz

Oh, I've tried this too. Doesn't work for me.

[Guest BigBearMDC]

Hmm this looks indeed a bit weird.

Usually flashing the recovery image once more should fix this, but it doesn't for you.

Have you tried a /dload flash?

This might solve your problem.

Best regards,

BigBear

[Guest twrock]

The only time I saw similar error messages is when I tried to boot into the AmonRa recovery without flashing it first on the newest build of the CHT8000 1.5 ROM (I think it was b279). But after I flashed the recovery image onto the device, it worked fine. You are installing (flashing) the recovery image onto your phone, right?

I'm thinking BigBear has a good suggestion. You could try flashing an updata (you will lose everything though), then reflash the recovery rom, and see if that clears things up. You might even need to go all the way back using the "time machine" first if you can't get one of the other rom's to flash.

Disclaimer: I'm just a newbie; what do I know? :)

[Guest MuhaJR]

The only time I saw similar error messages is when I tried to boot into the AmonRa recovery without flashing it first on the newest build of the CHT8000 1.5 ROM (I think it was b279). But after I flashed the recovery image onto the device, it worked fine. You are installing (flashing) the recovery image onto your phone, right?

I'm thinking BigBear has a good suggestion. You could try flashing an updata (you will lose everything though), then reflash the recovery rom, and see if that clears things up. You might even need to go all the way back using the "time machine" first if you can't get one of the other rom's to flash.

Disclaimer: I'm just a newbie; what do I know? :)

Same thing here - my fix was to do nandroid backup WITHOUT ext... That did it ok for me... Maybe something with ext partition is bad?

[Guest Tom G]

How much space is there available on the sd card? You will get a message similar to that if you don't have enough space for the backup. Run it from the shell and see what it says, the error messages are better in the shell.

[Guest Delta1292]

i have this problem every once in a while.

to fix it plug your phone into your computer, open up the SD card and navigate to nandroid subfolder and cut and paste all of your old nandroid backups to your computer (i presume that you want to keep them, if not delete them) and try again it should work

Edited August 3, 2010 by Delta1292

[Guest BigBearMDC]

How much space is there available on the sd card? You will get a message similar to that if you don't have enough space for the backup. Run it from the shell and see what it says, the error messages are better in the shell.

I think too less memory is not the problem.

The recovery image fails to mount the system and data partition.

Have a look at his recovery log :)

Best regards,

BB

[Guest Kepler]

I have the same problem when I try to run the Recovery-program. Booting it through an MS-dos window (this gives the errors you have) and trying the button combinations (it is just booting up then).

Then I installed the ClockworkMod http://android.modaco.com/content/t-mobile...covery-2-5-0-4/ ). This program force closes and doesn't work as it should. But the button 'Reboot in Recovery' works! This brings me to the AmonRa Recovery menu! Without erros :D

Hope this helps :)

[Guest Simon O]

Hm, could do with checking the mountpoints.

Any chance you can boot to recovery and connect your phone to your computer and run "adb shell"

I need the output of the following please:

cat /proc/mtd

mount

Edited August 3, 2010 by flibblesan

[Guest hyakamaru]

Check post below~

Edited August 4, 2010 by hyakamaru

[Guest hyakamaru]

Thank you for all the replies! Much appreciated! :)

...

Have you tried a /dload flash?

This might solve your problem.

...

What do you mean by a /dload flash? Erasing all partitions, including recovery, and doing a flash update?

Same thing here - my fix was to do nandroid backup WITHOUT ext... That did it ok for me... Maybe something with ext partition is bad?

Both Nand backup & Nand+ext backup do not work for me. :D

How much space is there available on the sd card? ...

I have around 6.7 GB atm.

to fix it plug your phone into your computer, open up the SD card and navigate to nandroid subfolder and cut and paste all of your old nandroid backups to your computer (i presume that you want to keep them, if not delete them) and try again it should work

I don't have any backups on the SD card, as I have not been able to do any backups at all.

...

Then I installed the ClockworkMod http://android.modaco.com/content/t-mobile...covery-2-5-0-4/ ). This program force closes and doesn't work as it should. But the button 'Reboot in Recovery' works! This brings me to the AmonRa Recovery menu! Without erros :D

...

I'll try this out in a bit! Thanks!

I need the output of the following please:

cat /proc/mtd

mount

On recovery mode:

/ # cat /proc/mtd

dev: size erasesize name

/ # mount

rootfs on / type rootfs (rw)

tmpfs on /dev type tmpfs (rw,mode=755)

devpts on /dev/pts type devpts (rw,mode=600)

proc on /proc type proc (rw)

sysfs on /sys type sysfs (rw)

On non-recovery mode:

$ cat /proc/mtd

dev: size erasesize name

mtd0: 00500000 00020000 "boot"

mtd1: 00500000 00020000 "recovery"

mtd2: 00140000 00020000 "misc"

mtd3: 00060000 00020000 "splash"

mtd4: 0aa00000 00020000 "system"

mtd5: 04600000 00020000 "cache"

mtd6: 0de60000 00020000 "userdata"

$ mount

rootfs / rootfs ro 0 0

tmpfs /dev tmpfs rw,mode=755 0 0

devpts /dev/pts devpts rw,mode=600 0 0

proc /proc proc rw 0 0

sysfs /sys sysfs rw 0 0

tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0

/dev/block/mtdblock4 /system yaffs2 ro 0 0

/dev/block/mtdblock6 /data yaffs2 rw,nosuid,nodev 0 0

/dev/block/mtdblock5 /cache yaffs2 rw,nosuid,nodev 0 0

/dev/block//vold/179:1 /sdcard vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1000,fmask=0000,dmask=0000,

allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8 0 0

...

Edited August 4, 2010 by hyakamaru

[Guest BigBearMDC]

Thank you for all the replies! Much appreciated! :D

[snip]

/dev/block/mtdblock5 /cache yaffs2 rw,nosuid,nodev 0 0

/dev/block//vold/179:1 /sdcard vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1000,fmask=0000,dmask=0000,

allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8 0 0

...

Yap, the partitions aren't mounted in recovery mode.

No wonder, you have a totally different partition layout!

Are you sure you have a U8220?

You can though mount the partitions in recovery mode by typing in the following via adb shell:

mount -o rw /dev/block/mtdblock4 /system

mount -o rw /dev/block/mtdblock6 /data[/code]


The recovery mode should work then.

But you'll have to this everytime you're trying to access the recovery.

Someone would have to adjust the fstab of the amon-ra recovery - I'd do it, but I'm currently working and running windows, sorry :D

That's weird, I haven't seen such a partition layout yet.

Which ROM are you currently running?


Edit: man you're even having a splash partition  :) 

Are you sure you don't own a U8230?


Best regards,

BB

[Guest hyakamaru]

Yap, the partitions aren't mounted in recovery mode.

No wonder, you have a totally different partition layout!

Are you sure you have a U8220?

You can though mount the partitions in recovery mode by typing in the following via adb shell:

mount -o rw /dev/block/mtdblock4 /system

mount -o rw /dev/block/mtdblock6 /data

The recovery mode should work then.

But you'll have to this everytime you're trying to access the recovery.

Someone would have to adjust the fstab of the amon-ra recovery - I'd do it, but I'm currently working and running windows, sorry :D

That's weird, I haven't seen such a partition layout yet.

Which ROM are you currently running?

Edit: man you're even having a splash partition :)

Are you sure you don't own a U8230?

Best regards,

BB

Attached below is my hell-raiser. He is definitely an U8220.

No worries, you've given me enough help as it is. Much appreciated, thanks! :D

I'm not sure which ROM you were talking about, but using the 1.5.2 AmonRA over Huawei's U8220 V100R001C05B279SP01(Taiwan CHT).

[Guest BigBearMDC]

Attached below is my hell-raiser. He is definitely an U8220.

No worries, you've given me enough help as it is. Much appreciated, thanks! :)

I'm not sure which ROM you were talking about, but using the 1.5.2 AmonRA over Huawei's U8220 V100R001C05B279SP01(Taiwan CHT).

Hmm okay.

Seems like you ROM has another partition layout though.

Have you tried mounting the partitions manually?

Best regards,

BB

[Guest Tom G]

I think that will be a CHT8000+ or whatever it is that has more RAM + more ROM. That partition layout looks roughly double the size of the original U8220 nand.

Combine the kernel from the boot image (or the original huawei recovery image) with the ramdisk from AmonRA and it might work.

[Guest BigBearMDC]

I think that will be a CHT8000+ or whatever it is that has more RAM + more ROM. That partition layout looks roughly double the size of the original U8220 nand.

Combine the kernel from the boot image (or the original huawei recovery image) with the ramdisk from AmonRA and it might work.

I don't think this would work because the mountpoints are defined in the amon-ra ramdisk somewhere.

I once asked amon-ra when I had trouble with my phone (back when the 2.1 update was leaked) and he told me I might edit the fstab (or something like this).

I'll have a look at my twitter profile, one moment ...

Okay, here's the reply I got from Amon RA back in May:

unpack the recovery image, update fstab to the new partition layout, repack the image.

I'll have a look if I can access a Linux PC and see if I can get the recovery image adapted to your phone.

But I can't promise anything though :D

Maybe Tom G could do this for you?

All that would have to be changed would be the mountpoints from

/dev/block/mtblock1 to /dev/block/mtdblock4

and

/dev/block/mtblock2 to /dev/block/mtdblock6[/code]


Should work like a charm then :)


Best regards,

BB

[Guest Simon O]

I've patched the Amon_RA recovery image with the correct mount points. Please download and flash through fastboot as normal please.

1.5.2-cht8000-amonrarecovery.zip

[Guest TaiwanCHT8k]

clockwork recovery works well on both cht8000 and cht8000+

give it a try

[Guest hyakamaru]

I have the same problem when I try to run the Recovery-program. Booting it through an MS-dos window (this gives the errors you have) and trying the button combinations (it is just booting up then).

Then I installed the ClockworkMod http://android.modaco.com/content/t-mobile...covery-2-5-0-4/ ). This program force closes and doesn't work as it should. But the button 'Reboot in Recovery' works! This brings me to the AmonRa Recovery menu! Without erros :D

Hope this helps :)

The ClockworkMod worked for me. No errors, and the backup ran very smoothly.

I've patched the Amon_RA recovery image with the correct mount points. Please download and flash through fastboot as normal please.

1.5.2-cht8000-amonrarecovery.zip

I'll try this out in a bit. Thanks flibblesan! :D