Develop Bugs

nandroid?

Do we have nandroid with full backup/restore of all partitions working yet?
If so, some instructions would be greatly appreciated

we wont have nandroid until we have a custom recovery image and possibly full /system access

So... are we seeing any progress in the nandroid department yet?
I distinctly remember seeing a twitpic (from Paul?) of a Desire running custom recovery image so that shouldn't be a problem.
What's holding it back?

You can make nandroid backups from the recovery....

abats said:
You can make nandroid backups from the recovery....
Click to expand...
Click to collapse
That's precisely what I thought.
Golgo said:
So... are we seeing any progress in the nandroid department yet?
I distinctly remember seeing a twitpic (from Paul?) of a Desire running custom recovery image so that shouldn't be a problem.
What's holding it back?
Click to expand...
Click to collapse
I'm sure he said it wasn't a recovery image, but just an app/script. In any case, if we run the recovery script we have the NAND backup/restore options amongst the others (wipe/partition/etc).
alex101uk said:
we wont have nandroid until we have a custom recovery image and possibly full /system access
Click to expand...
Click to collapse
Can you elaborate on this please? You can write /system (and probably any other partition) from within the recovery.
Run the step2.sh from Paul's given files, and you'll see a quick adb shell and mount /system gives full rw to /system.

Really? And it's fully working?
I've been reluctant to try other roms until I knew nandroid was a go.
So just to be crystal clear - I can take a nandroid backup of EVERYTHING, the full stock-rom incl. every partition and restore it later just as easily?

Golgo said:
nandroid backup of EVERYTHING, the full stock-rom
Click to expand...
Click to collapse
Nope (unless you invent/modify the method yourself using the RUU and recovery shell - not 100% sure it's possible). You can only nandroid what's on there past Pauls rootedupdate.zip if you use his instructions.

jayshah said:
Nope (unless you invent/modify the method yourself using the RUU and recovery shell - not 100% sure it's possible). You can only nandroid what's on there past Pauls rootedupdate.zip if you use his instructions.
Click to expand...
Click to collapse
Ok, so you cant make a full backup of /system, /data etc?
Too bad. nandroid is damn handy when you'r messing around with custom roms!

Nandroid make full back as usual. I used it many times without any issues when playing with different desire roms.

Golgo said:
Ok, so you cant make a full backup of /system, /data etc?
Too bad. nandroid is damn handy when you'r messing around with custom roms!
Click to expand...
Click to collapse
Of course you can. I said you can nandoid past Pauls update, and not the stock ROM as you said.

jayshah said:
Of course you can. I said you can nandoid past Pauls update, and not the stock ROM as you said.
Click to expand...
Click to collapse
Ah, alright. Shame

Im new to this so let me get this right, I currently have a rooted stock ROM by Paul using the original linux rooting method. Can I use nandroid to back up this up and then flash a cooked ROM and if I do not like it then I can use the back up to reflash back to where I was?

Nekromantik said:
Im new to this so let me get this right, I currently have a rooted stock ROM by Paul using the original linux rooting method. Can I use nandroid to back up this up and then flash a cooked ROM and if I do not like it then I can use the back up to reflash back to where I was?
Click to expand...
Click to collapse
Yes. If you nandroid restore, it will be as if absolutely nothing has changed (excluding any SD card data changes).

jayshah said:
Yes. If you nandroid restore, it will be as if absolutely nothing has changed (excluding any SD card data changes).
Click to expand...
Click to collapse
thanks
I still need to push the recovery files in order to get into the recovery menu in order to flash etc. Will that mean I cant nandroid my current ROM?

That's something I've wondered for a bit - can you push the recovery files (step 2) without doing step 1? And if so, can you trigger a nandroid backup on it?
I don't THINK you can, but I skipped it entirely, so it might be worth trying. Worst thing that happens is it fails, right? Can you get into recovery without rooting?

The Professor said:
That's something I've wondered for a bit - can you push the recovery files (step 2) without doing step 1? And if so, can you trigger a nandroid backup on it?
I don't THINK you can, but I skipped it entirely, so it might be worth trying. Worst thing that happens is it fails, right? Can you get into recovery without rooting?
Click to expand...
Click to collapse
I cant get into the custom recovery menu without pushing the recovery files so I think we need a custom ROM to be able to get into the recovery menu directly from the phone.

The Professor said:
That's something I've wondered for a bit - can you push the recovery files (step 2) without doing step 1? And if so, can you trigger a nandroid backup on it?
Click to expand...
Click to collapse
Yes, this is exactly what I did. I have a recovery.sh file which is just step2.sh without the push of rootedupdate.zip each time.
Code:
# pwd
/sbin
# ./nandroid-mobile.sh -b
cp: './nandroid-mobile.sh' and '/sbin/nandroid-mobile.sh' are the same file
nandroid-mobile v2.2.1
Using G1 keyboard, enter a prefix substring and then <CR>
or just <CR> to accept 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/HT044PL07434/BCDMRS-20100505-1350/boot.img...done
Dumping recovery to /sdcard/nandroid/HT044PL07434/BCDMRS-20100505-1350/recovery.img...done
Dumping misc to /sdcard/nandroid/HT044PL07434/BCDMRS-20100505-1350/misc.img...done
Dumping system to /sdcard/nandroid/HT044PL07434/BCDMRS-20100505-1350/system.img...done
Dumping data to /sdcard/nandroid/HT044PL07434/BCDMRS-20100505-1350/data.img...done
Dumping cache to /sdcard/nandroid/HT044PL07434/BCDMRS-20100505-1350/cache.img...done
generating md5sum file...done
unmounting system, data and sdcard
Backup successful.
#
Edit: Running a nandroid using the GUI method worked too, the 2nd time. 1st time failed, hence I did it manually above.

-edit- hm, got this
Code:
Using - prefix to create a backup folder
mounting system and data read-only, sdcard read-write
checking free space on sdcard
mtd: MEMGETBADBLOCK returned 1 at 0x00240000 (errno=0)
Dumping boot to /sdcard/nandroid/HT03WPL08829/BCDMRS-20100511-1419/boot.img...mt
d: MEMGETBADBLOCK returned 1 at 0x00240000 (errno=0)
done
.
.
.
.
Backup successful.
#
what does this mean?

nandroid img files restore question

So heres the situation. I made a backup of my phone using rom manager because I wanted to try out the new cyanogen. I got done playing with it and I went to revert back to my restore I had just created. During the restore I got an md5 mismatch error.
I used the instructions here to repair the restore
http://www.droidforums.net/forum/droid-hacks/40428-checking-md5-sum.html#post430944
su
cd /sdcard/clockworkmod/backup/*rom name (date and time usually)/
md5sum *img > nandroid.md5
reboot recovery
The procedure worked in the sense that I was able to restore the image. The problem is after the restore I am stuck at the white "HTC Incredible" screen. I tried wiping caches and running the restore again but I am unable to get the phone to reboot.
I was able to restore to a much older restore that I had previously created but it lacks alot of updates and changes that I have made since then. Not to mention my Angry Birds saved game.
Looking at the restore files it looks like the folder for the restore contains a hand full IMG files. What i'm wondering is since it appears that the boot process is damaged I'm wondering if I could make a backup of the phone as it is now then take lets say the data.img file (or whatever file i need to recover installed apps and saved games) and overwrite the img files for the restore i just created. I could then use the same procedure I just performed to recreate the md5 hash and run the restore. My home is that will allow me to get my data back and still allow the phone to boot.
What do you guys think? Is it doable or am I going to be in a world of hurt if I start messing with this?

Something else you might try is to restore the latest backup, then do an advanced restore of just the boot partition from your older backup. It's worth a shot I'd think.

Did you put spaces or special characters when you named your backup? This can cause MD5 mismatch errors.

s197 said:
Did you put spaces or special characters when you named your backup? This can cause MD5 mismatch errors.
Click to expand...
Click to collapse
NO, I didn't. I used the default setting. I think it was 2010-12-29.01.34.10 or something like that.
setexascustoms said:
Something else you might try is to restore the latest backup, then do an advanced restore of just the boot partition from your older backup. It's worth a shot I'd think.
Click to expand...
Click to collapse
Thanks man, This worked perfectly. Restoring the boot.img didn't fix the problem but restoring the system.img did. I have all my data back and my phone is fully functional again. Thanks again.

[Q] Leedroid 2.4.1 freezing pre-boot - any way to fix or access user data?

***IT HAPPENED A SECOND TIME. THIS TIME I WAS ABLE TO FIX IT BY CLEARING CACHE/DALVIK CACHE AND FLASHING A NEWER VERSION OF THE THE SAME ROM***
Hi guys,
I recently bought a Desire and loaded LeeDroid on a week later. Everything's been fine, until today, when I shut-down my phone and went to turn it back on, and it froze at the Telstra (telco who I bought it from) splash screen.
Here's what I did:
- Power + Vol- + trackball, which resulted in it restarting and freezing at the same point (15 minutes wait)
- Pulled battery and booted into recovery
- NAND Backup using AmonRA
- Restored original (pre-LeeDroid) NAND backup, and rebooted, which resulted in phone freezing at the same point
- Shut down, removed SD Card, wiped using AmonRA, restored original (pre-LeeDroid) NAND backup, which enabled it to boot properly
- Restarted and flashed Leedroid Rom from ZIP, which worked fine.
- Restored today's NAND backup, which of course brought everything back to square one.
Can anyone tell me if it's possible to access any of the contacts/SMS/etc? I was planning to back-up tonight as I'd put a whole heap of stuff in today, so of course this arvo was when it had to die. That and there's some stuff I'd really like to have that I'm not sure the relevant apps have stored on the SD.
And how can I ensure a clean restore? Run Telstra's RUU, then install LeeDroid as per instructions?
(EDIT) I notice that the NAND backups consist of a bunch of .img files. I imagine that data.img might have what I'm looking for in it. I've tried searching for a way to explore the contents, but I'm still trying to get unyaffs running...

Reflash or wipe cache and dalvik cache and reflash.
Sent from CM7

So you're suggesting I do the following?
- Restore freezing NAND backup
- Wipe Cache + Dalvik Cache
- Reflash LeeDroid from zip

Are the contacts all google contacts? If so you can recover those that way.
When you signed in for the first time after flashing the rom, while linking your google account, did you check "backup this phone to google servers"? If so, that should restore things if you wipe all and reflash the rom.
I used this option for the first time, and my wallpaper, shortcuts, alarm settings and SMS all restored after 5 minutes or so.

Unfortunately not. I didn't make the same mistake this time though >_>
Even so, I'm still hoping I might be able to pull some of the stuff out of the NAND backup.
Do you know if it's possible to fake/bypass the md5? If I can swap the data.img from the busted backup to a working one (the one before I put all my contacts in etc) then I should be able to access something.
Unfortunately that brings up an error, and I imagine the checksum is what's doing it.

Back up missing MD5 file

I did a backup in ROM manager, I went to restore and it said "This does not seem to be a valid backup. The MD5 file is missing." Is there anyway to fix? I'd hate to lose the data .

do another back up in recovery,

I think the problem with doing another backup is he's already wiped.... Maybe.
sent from Incredible ViperDIX

Assuming you're using CWM or a compatible recovery, you can calculate a new md5 by running this command in a terminal emulator from the directory holding your backup files:
md5sum *img > nandroid.md5
Keep in mind, though, if the files were corrupted since the original backup, this will allow them to be flashed, since it's creating the verification md5 based on what's there now, not what was there originally. But it's pretty rare to have files become corrupted just sitting on your sd card. I've done this many times without issue.

Jizzylax said:
I think the problem with doing another backup is he's already wiped.... Maybe.
sent from Incredible ViperDIX
Click to expand...
Click to collapse
ChrisDDD said:
Assuming you're using CWM or a compatible recovery, you can calculate a new md5 by running this command in a terminal emulator from the directory holding your backup files:
md5sum *img > nandroid.md5
Keep in mind, though, if the files were corrupted since the original backup, this will allow them to be flashed, since it's creating the verification md5 based on what's there now, not what was there originally. But it's pretty rare to have files become corrupted just sitting on your sd card. I've done this many times without issue.
Click to expand...
Click to collapse
Sorry guys, I got busy irl. Forgot i posted this.
The file i looked at it on my comp, it was missing half of the files that a complete back up was. I assume it's corrupt. I already have most things back to the way they were, i'll be sure to make a back up in recovery next time.

If I TWRP backup everything except System will a Restore work later on?

I dont know what I did but I know it was my fault.
Whenever I try to create a full backup of all partitions I get "createTarFork() process ended with ERROR=255"
But when I exclude the System partition it works fine.
So if I restore everything else later on will everything work fine? I'm not exactly sure whats getting left out in the partition.
Btw, my bootloader is unlocked, I'm currently on FreedomOS 2.1, I have Magisk, Xposed, all the good stuff...
ALSO! I did an ADB backup on my computer with "adb backup -apk -shared -all -system -f"
I'd be fine with the ADB backup but "backup.ab is only 1.5 GB and my nandroid backups are usually around 11GB...

lit_lee said:
I dont know what I did but I know it was my fault.
Whenever I try to create a full backup of all partitions I get "createTarFork() process ended with ERROR=255"
But when I exclude the System partition it works fine.
So if I restore everything else later on will everything work fine? I'm not exactly sure whats getting left out in the partition.
Btw, my bootloader is unlocked, I'm currently on FreedomOS 2.1, I have Magisk, Xposed, all the good stuff...
ALSO! I did an ADB backup on my computer with "adb backup -apk -shared -all -system -f"
I'd be fine with the ADB backup but "backup.ab is only 1.5 GB and my nandroid backups are usually around 11GB...
Click to expand...
Click to collapse
Team Win recommends using the system image backup instead of just system for dm-verity devices, but I still get the same problem as you when trying to perform a backup. What you could try is clean flashing the ROM and then just restore data from ur backup. That should work.

Airwolf79 said:
Team Win recommends using the system image backup instead of just system for dm-verity devices, but I still get the same problem as you when trying to perform a backup. What you could try is clean flashing the ROM and then just restore data from ur backup. That should work.
Click to expand...
Click to collapse
Yeah I read in other places a fresh flash would work but I wanted to weight my options.
How does one go about doing the image backup? That sounds a lot better.

lit_lee said:
Yeah I read in other places a fresh flash would work but I wanted to weight my options.
How does one go about doing the image backup? That sounds a lot better.
Click to expand...
Click to collapse
When you select backup in TWRP, it's one of the available boxes to check. Uncheck system, check system image. This hasn't solved my problem of backups not completing though. I always remove my fingerprints and pin before a backup, and I've been able to complete backups before, but usually the problem lies in encrypting the backup itself. However, I've still had backups hang at 95% even without encryption. Maybe someone else can shed some light on to why this is happening.

the createTarFork() process ended with ERROR=255 is not from system its from data and issues with parallel apps on ur OP5T
download Android Terminal and type
Code:
su
pm remove-user 999
then u can backup with twrp, never tried to do a restore yet though