Root Weird goings on... everything wiped, almost

[SUroot]

nah just the ubcd4win programs.

NTFS getdataback is good, but I need FAT. To be honest, I think I may give up and start from the ground up (almost). May go Amon RA now I know I can use it with MTD

Got a link to the best version please? The experimental one?

 

[SUroot]

ooooh hang on, I managed to retrieve one of the backups... and no md5 mismatch this time..... Hmmmmmm

I'm still not holding out hope.

 

[Rastaman-FB]

nah just the ubcd4win programs.

NTFS getdataback is good, but I need FAT. To be honest, I think I may give up and start from the ground up (almost). May go Amon RA now I know I can use it with MTD

Got a link to the best version please? The experimental one?

the experimental one has been rock solid for me
the only thing he changed was sd-ext as the 2.0.0 only backed up apps within sd-ext and nothing custom
2.0.1 works like clockwork by backing up anything in ext

 

[SUroot]

Cool. Do you still have that dropbox link to it please?

 

[SUroot]

OK recovered Nandroid from SD
Copied Nandroid to SD
Restored Nandroid
Patched Boot
Booted, Looked good
Formatted NAND
Changed MTD
Patched Recovery
Rebooted Recovery
Flashed GV 1.3
Flashed my app
Restored DATA and CACHE only
Patched Boot
Lovely Jubly

Handy recovery did the job for me. Version 1.0 is free. I extracted it from ubcd4win, but anyone interested, heres the link to a direct download

Handy Recovery 1.0 - Free software downloads and software reviews - CNET Download.com

 

[Hadron]

Grabbed a copy - always useful to have such things in case.

Anyway, glad that's all worked out. Guess a recovery problem is still the best guess at cause? Don't like the coincidence, but the circumstance seems rather different from those at XDA (when the phone was running Android at the time).

 

[SUroot]

ah but the saga continues. The modified GV I flashed earlier will not now boot properly.

When I log cat it I get:

--------- beginning of /dev/log/main
E/logwrapper(   77): executing /system/xbin/busybox failed: No suc
 directory
I/logwrapper(   71): /system/xbin/busybox terminated by exit(255)

But My nandroid works but now for some reason, it always says system is 90MB, free space none.

Neither the MTD or hboot specifies that though...


Jusr reflashed CWM and repatched. Restoring nandroid for patching right now.

If I get the right partitions now, itll be good but Im still missing mms.apk and browser.apk

May have to push them IF I can get the partitions right

God knows whats going on now

If I do get teh partitions back maybe CWM (patched) is to blame.

 

[Rastaman-FB]

Cool. Do you still have that dropbox link to it please?

its in your guide

roflowned


edit that link for handy recovery forces 4.0 trial
http://www.aplusfreeware.com/categories/LFWV/HandyRecovery.html
is 1.0

 

[SUroot]

FFS!!!!!!!

n00b, this is answered in my FAQ. Please read it!

 

[Rastaman-FB]

Susan you are failing at all levels today

 

[SUroot]

I've failed more than you know. I've been racking my brain as to why my partitions are standard N1 partitions. Just realised there was a typo in mtdpartmap.txt file name.

Serious, I am not touching the phone this weekend. I need time off. These earlies are killing me

 

[porter_james]

I've failed more than you know. I've been racking my brain as to why my partitions are standard N1 partitions. Just realised there was a typo in mtdpartmap.txt file name.

Serious, I am not touching the phone this weekend. I need time off. These earlies are killing me

Wait...the reason for this whole thread was...a typo? No CWM hiccup? Some other intricate and puzzling corruption caused by the ineffability of the Desire? Or maybe a conspiracy centering on Leeds? What a letdown
I'm glad your are back on track though!

 

[SUroot]

Oh, no. This was just what was preventing my very last step of recovery being correct. This typo was only only causing my partition info to be incorrect after my last nandroid restore.

 

[Rastaman-FB]

Oh, no. This was just what was preventing my very last step of recovery being correct. This typo was only only causing my partition info to be incorrect after my last nandroid restore.

any more problems?

 

[SUroot]

Not as yet, thanks. All seems ok right now.

Going to always backup nandroids and zips before flashing from now on though. If it happens again, I shall keep an eye on trends.

 

[Rastaman-FB]

you on 1.3 or 1.2 currently?

 

[SUroot]

1.3 with old RIL. I may be being paranoid, but my display drain seemed higher (well the battery drop graph seemed steeper) on the 1.2 RIL.

 

[SUroot]

Well this happened again today...

I was messing with my installed ROM and decided to flash back over it. Flashed a known good rom.zip, known good kernel.zip

Hung at extracting system files for longer than expected. I was about to pull the battery out when it said finished.

Corrupt /system partition and entire SD card wiped!!!!

 

[Rastaman-FB]

i think something is up with the sdcard tbh.
upon thinking more correctly it does have to mount sdcard to to read the files.
when you flash it is unpacking on the fly while writing to the various partitions that it has read from the updater script

While its not the same, its similar behaviour to when rom manager fks up and wipes card then usb bricks the device to add insult to injury

 

[SUroot]

The card had been acting funny for a couple fo days previously, so I think it is an FS issue, but the underlying cause of that has yet to be determined.