yashsingh1/xdaforums huggingface dataset:
[Desire Android Development] ahac85:
clarification required?

Hi can somebody please explain this to me To everyone making nandroid backups with Clockworkmod/ROM manager : Don't try to restore them with my recovery. The Clockworkmod recovery isn't using the same nandroid script as my recovery.

i have new sdcard so i transferred the backup image made via clockwork mod from my old sdcard to the new sdcard, then used unrevoked to install amonra 2.0.1, once successfully done then installed leedroid 2.2f using amonra, then gone into rom manager once phone booted up and booted into clockwork mod recovery 2.5.0.1 via rom-manager (fake-flash i think its called) and restored nandroid backup, everything is working fine!

my question is, is that ok to do or was i risking the chance of getting a usb brick??? or does that only apply if you boot into amonra 2.0.1 and to updatezip to clockwork mod thru the recovery??
[Desire Android Development] dkawa:
Sorry, but my answer to :

1. Wipe sd-ext if you are using anything different than apps on your sd-ext (you didn't answer if you are or not).

I had wiped the sd-ext but there were only apps stored on the sd-ext. So I did not have to wipe this prior to the restore?

Do I need to have a full battery when performing a NANDROID backup?

Now I have a ROM with A2SD+ and rooted with no backup. So for a NANDROID I need to Nand+ext backup and for RESTORE I need to Nand restore without PRIOR wiping??
[Desire Android Development] qariboy:
Sorry I am a noob with a question.

I have s-on, so what could happen if I flash recovery amon_ra .20 img ? had amon_ra 1.7 before with s-on. never had any problems.

on alpharev weblink ... how do i flash hboot 1.5? and what to do with bravo-n1table.img?
[Desire Android Development] dkawa:
Originally Posted by Amon_RA

As I mentioned before please provide a recovery log so we can see what went wrong. Without recovery log we can't know what went wrong.

Bootloops are not related to this recovery, use ddms to trace what is going wrong and contact the dev who made the update that made your phone to bootloop.

So :

1. Wipe sd-ext if you are using anything different than apps on your sd-ext (you didn't answer if you are or not).

2. Restore your nandroid backup.

3. Provide us the recovery log.

4. Don't use BOLD, it makes my eyes bleed.

Sorry, but my answer to :

1. Wipe sd-ext if you are using anything different than apps on your sd-ext (you didn't answer if you are or not).

I had wiped the sd-ext but there were only apps stored on the sd-ext. So I did not have to wipe this prior to the restore?

Do I need to have a full battery when performing a NANDROID backup?

Now I have a ROM with A2SD+ and rooted with no backup. So for a NANDROID I need to Nand+ext backup and for RESTORE I need to Nand restore without PRIOR wiping??

Hi Amon_RA, can you please advise?
[Desire Android Development] Amon_RA:
Please upgrade your recovery to v2.0.1, this version will take backup/wipe your entire ext partition so you don't need to wipe anything prior to a restore.

Nandroid checks if your battery is at least 30%, so make sure it's above 30%.

1. Install recovery v2.0.1

2. boot into recovery and select Nand+ext backup

3. if you ever want to restore you just select "nandroid restore" it will see that you have an ext backup and will restore it.
[Desire Android Development] dkawa:
I cannot install the v2.0.1 version with Unrevoked 3.22... So do I have to flash a stock (unrooted) ROM version and then root again with Amon_RA 2.0.1 as custom recovery file?

And afterwards install the rooted ROM with A2SD+ etc..??

Isn't there an easier way to 'update' from v2.0.0 to v2.0.1? I am rooted, uses A2SD+ but S-on...
[Desire Android Development] esskaypee:
Coming from the old Amon_Ra_1.0.7-R5 (I think?!), s-off, no problem installing it, sterling Work, Sir!!!
[Desire Android Development] esskaypee:
Of course it was fine, as you ultimately restored your nandroid backup with the clockwork mod, i.e. the software used to make the backup in the first place.

What the sentence means, is that you can't restore a clockwork mod 'made' backup with Amon-Ra.
[Desire Android Development] dkawa:
How did you install this new version?

Do you have a stock ROM without A2SD+?
[Desire Android Development] esskaypee:
My Set-up

I have LeeDroid 2.3a WITH A2SD+

I'm also S-OFF

I used the fastboot method mentioned in the OP.
[Desire Android Development] dkawa:
Dear Amon_RA

Is it possible to make a ZIP file for updating from v2.0.0 to v2.0.1?

So then it should be able to update with Recovery and then flash...

Please please...
[Desire Android Development] Jagdish84:
Is this v201 the same as the one posted by amonra a couple of pages back? Or should I flash this one instead?

Sent from my HTC Desire
[Desire Android Development] jab1972:
Wipe /sd-ext format back to ext2???

I am currently using v2.0.1. Can anybody answer me this question?

If I currently have an ext4 partition on my SD card and I use the Wipe /sd-ext function, does this format the partition back to ext2 ???

Thanks
[Desire Android Development] Amon_RA:
No, a wipe on ext is just an "rm" command.
[Desire Android Development] Amon_RA:
Place 2.0.1 on your sdcard

Go in recovery

adb shell

mount -a

flash_image recovery /sdcard/nameof2.0.1recovery.img
[Desire Android Development] jab1972:
Thanks Amon_Ra, so it will just wipe the ext partition leaving it in what ever format it was (ext2,3, or 4)?

Is there anyway to convert/format an ext3 or 4 back to ext2 with out formating the whole card (ie losing the fat32 partition)?

Thanks
[Desire Android Development] dannyling:
Thanks for your great work I've had a cool idea to have a new option in the menu to flash new recovery and it could only be one of your recoveries . Making it a bit easier if you update it to a spangaly new version been using amon ra since my g1 days
[Desire Android Development] mobilkungen78:
Can someone please tell me how to delete a nand-ext backup?

Edit:i found the backup in efile and nandroid and deleted the files there
[Desire Android Development] Dante4212:
Wanting to know this as well! I've got a US Cellular Desire CDMA that needs to get rid of ClockworkMod.
[Desire Android Development] APEX.7:
guys, is there a way for me to get this awesome recovery even though i am s-on? currently have clockwork. is there a zip i can flash? thanks :) (sorry im bit noobie)
[Desire Android Development] LfcFan1977:
Thanks for the great recovery.

Thanks for the recovery log commands, thought I had a big problem when I couldn't perform a recovery. Just a low a battery ;)
[Desire Android Development] Han-Droid:
+1 .... acutally i only want it because it can convert ext3 to ext4 and i am just to noob to do it in any other way.

gparted was a f*cking pain in the a**. actually good old acronis did the job...but NOT ext4....:(
[Desire Android Development] juansuandi:
why my trackpad didnt move on recovery? its very smooth on r5. and if i reboot to recovery why its take time so long? screen colours change many time.

desire amoled here. thank you
[Desire Android Development] g-droid:
Is there any app to start flashing roms?

Like the rom manager for clockwork.
[Desire Android Development] skeptic1007:
Please help.

I use AmonRA recovery 2.0.1. I have created a small first-install.zip with a few things to put on SYSTEM and DATA after flashing a ROM. I signed zip files before and cyanogenmod recovery accepted them. Now I have two issues:

- the signature is not accepted, verification failed; i signed with

java -jar signapk.jar file.pem file.pk8 first-install.zip first-install-signed.zip

- with verification off, the installation fails at line 1 of update-script, whose contents I give hereby:

copy_dir PACKAGE:data DATA:

copy_dir PACKAGE:system SYSTEM:

The structure of the file follows:

fresh-install-signed\data

fresh-install-signed\META-INF

fresh-install-signed\system

fresh-install-signed\data\app

fresh-install-signed\data\app\com.keramidas.TitaniumBackup-1.apk

fresh-install-signed\data\app\com.rerware.android.MyBackupPro-1.apk

fresh-install-signed\META-INF\CERT.RSA

fresh-install-signed\META-INF\CERT.SF

fresh-install-signed\META-INF\com

fresh-install-signed\META-INF\MANIFEST.MF

fresh-install-signed\META-INF\com\google

fresh-install-signed\META-INF\com\google\android

fresh-install-signed\META-INF\com\google\android\update-script

fresh-install-signed\system\app

fresh-install-signed\system\lib

fresh-install-signed\system\app\Clicker_hi.apk

fresh-install-signed\system\app\HTC_IME_hi22.apk

fresh-install-signed\system\lib\libt9.so

fresh-install-signed\system\lib\libt99.so

Something must be wrong, but I do not see it.

Thank you for all the help.
[Desire Android Development] b3ndik:
is it possible to make three partitions with amon ra? ext4/ext4/fat32
[Desire Android Development] thanito:
Is it possible for someone to make an update.zip with 2.0.1 so we can use it as fake flash?

I currently use fakeflash method with 1.7.5, i think!
[Desire Android Development] bemymonkey:
2.0.1: Problems after restoring NAND + EXT?

Has anyone else had problems with restoring a NAND+EXT backup made with AmonRA 2.0.1? I just completely ****ed my Desire with it.

1. Made NAND+EXT backup of my working CyanogenMod nightly install w/ EXT partition including Firerat's A2SDEXT script (Everything but Dalvik on EXT)

2. Flashed AdamG's Gingerbread to try it out (Oxygen 2.0 pre-beta)

3. Restored the backup

4. Rebooted into restored CyanogenMod nightly... crap, no data restored. Also, no ADB access (device not found). No access to SD card. No reception...

5. Rebooted into recovery, /sdcard and /sd-ext can no longer be mounted, no ADB access in recovery either.

WTF happened? :confused:

How do I get back ADB access in recovery? Should I re-flash the recovery via Fastboot? This sucks, I really need a working backup/restore system :(

-edit- Why does Windows 7 now detect the phone in recovery mode as a Qualcomm CDMA Technologies MSM?

-edit2- I've now tried 3 different SD cards - all of them show:

E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0)

(No such file or directory)

when trying to mount SD card in recovery.

-edit3- Booted into Android, the SD card is listed as "unavailable".

-edit4- Emergency calls only. Now what?

-edit5- Flashed back Amon_RA 2.0.0 via Fastboot... flashed fine but didn't help. :(
[Desire Android Development] mercianary:
sounds like a usb brick.

fastboot oem enableqxdm 0
fastboot reboot

should fix it apparently, never had to do it myself though.

Let us know how you get on. good luck:)
[Desire Android Development] bemymonkey:
Thanks for the reply, I'll try that out right away.

Any idea what could have caused it?

-edit- Isn't quite working. Looking up Fastboot though... :(
[Desire Android Development] mercianary:
no idea, never had one so i havent really looked into it, people were experiencing loads of usb bricks a few months ago, seemed to go away, but recently i have seen quite a few, kinda like swine flu, maybe theyre connected...

:edit: Look here for more info, follow the rest of the instructions to restore usb function. apparently the command i gave you only fixes sdcard
[Desire Android Development] bemymonkey:
Your commands seem to have restored at least rudimentary SD card function within CyanogenMod. Guess I'll try the instructions from the USB brick thread... thanks for now, and if anyone else has more info or bright ideas, I'd love to hear them ;)
[Desire Android Development] mercianary:
I just edited my last post to tell you that at the same time, lol.
[Desire Android Development] bemymonkey:
Thanks a lot for your help. I'm now typing from my fully functional Desire ;)

@ Amon_RA: Any idea why I'm getting a USB brick (AFAICT that means the MISC partition was somehow modified during the restore...) every time I restore? Any info I can provide to help get it fixed?
[Desire Android Development] Jagdish84:
Head over to modacos and follow the thread about usb bricking, there's a zip file you have to flash as well...

Sent from my HTC Desire
[Desire Android Development] bemymonkey:
Yeah, already found it, thanks :)

-edit- Restoring the same NAND+EXT backup (made with 2.0.1) with 2.0.0 also causes the USB brick. Why is the restore even touching the MISC partition?
[Desire Android Development] APEX.7:
is there a way for us s-on's to get this? flashable zip perhaps?
[Desire Android Development] Amon_RA:
MISC is NOT back-upped or restored with my recovery...

Check your nandroid backup directory : there is no misc.img backup , correct?

Could it be that the rom you flashed did some weird stuff?
[Desire Android Development] hallydamaster:
Apart from the backup of .android_secure, and the wipe all user data, how is this

exactly different from RA.1.7.0.1.R5?
[Desire Android Development] nespresso33:
no ... simply in "Flash item"
[Desire Android Development] da900:
Thanx a lot. Great!...
[Desire Android Development] Invisionx:
Not to sound like a twat, Amon_RA, I'm simply wondering what the difference between this and ClockworkMod is?
[Desire Android Development] Fana7ic:
Sorry for asking noob questions, but Im still fairly new to Android modding and dont know what to do.

My problem is I rooted through unrevoked and used AmonRA 1.7.0.1 Recovery R5 as recovery.

I now wanted to upgrade to the latest version but I cant do the same thing through unrevoked again since it now recognizes my desire as "passion" (Using MIUI Rom)

any help?
[Desire Android Development] Mystenes:
CM version totally burn eyes, but i think, there will be a lot o fans o that :)
[Desire Android Development] sfjuocekr:
Differences are nihil, mainly menu structure nothing that makes recovery A, or B perform better than C etc.
[Desire Android Development] sfjuocekr:
Did you S-OFF your phone? If so you can goto bootloader and flash trough fastboot:

fastboot flash recovery <imagename>
[Desire Android Development] Fana7ic:
Nope. The first screen after holding back + power button still shows S-On.

As I said I only did use unrevoked and flashed a custom Rom.

Any way to update without S-OFF?
[Desire Android Development] sbdags:
Think unrevoked can flash s-off at the same time as flashing the custom image. This worked great for me - but make sure you uninstall HTC Sync first and install the adb drivers from the unrevoked home page ;)

Cheers!! :D
[Desire Android Development] Toisan:
hello, great work, flashed with fastboot too, worksgreat, less than 30 sec. time :)

thanks!
[Desire Android Development] iinga:
Might want to erase the recovery first

fastboot erase recovery

fastboot flash recovery <imagename>
[Desire Android Development] ganjbass:
Where can i use this commands?

Where i have to put the recovery img for flash it?

Thanks:P
[Desire Android Development] str355:
you use the commands in dos prompt on your windows PC.

put the image anywhere on your PC to flash it

as in "fastboot flash recovery C:\this\way\to\flash\recovery.img"
[Desire Android Development] Jagdish84:
I flashed it via Unrevoked, no need to delete former existing Recovery img...
[Desire Android Development] sfjuocekr:
You want to download the Android SDK first, in the windows version fastboot is included for the linux version google fastboot and it will bring you to the HTC Developer Center.

And yea you might want to

fastboot erase recovery

first indeed, but should not matter as it is a binairy format and the leftover data that might be left behind is not accessible anyway due to the new ToC.
[Desire Android Development] murdoch1:
Menu Navigation

Hi.....loving the new recovery.....any chance you could implement the volume keys to navigate up/down. Its far easier than the optical pad which i dont feel very responsive???? Cheers Andy
[Desire Android Development] ganjbass:
Thanks a lot guys. I just flashed now CM recovery from fastboot

and is very nice.
[Desire Android Development] Bisis:
please add ALT key functions.. I don't find trackball so well functioning
[Desire Android Development] mdmar:
Thx for a great update first of all!

I flashed successfully, but experienced some peculiar issues...

After flashing new recovery, my SU-rights are gone and I cant even open "Super User permissions" anymore - which totally messes up my several apps:(

I get a FC: com.noshefu.android.su for Superuser Permissions was closed ...

Any ideas here?
[Desire Android Development] b3ndik:
Hey, is it possible to make three partitions with this recovery? ext4/ext4/fat32
[Desire Android Development] bemymonkey:
That's what I thought, but it seems to be getting modified every time I restore... no idea why.

Nobody else seems to have had problems restoring to their previous ROM. I'm at a loss myself, because it's just such a weird error - who ever heard of a USB brick from restoring a Nandroid backup?

Also, after fixing my USB brick, I reinstalled the latest CM6 nightly and then tried restoring the backup again - USB bricked again. It's definitely reproducible...

Is there any other information I might be able to provide?
[Desire Android Development] iinga:
What is in your recovery file?
[Desire Android Development] bemymonkey:
"File not found" :p

Apparently it's been deleted already... I'll go through the restore procedure again tomorrow and post a log. Do I need to get the log from in the recovery? Or can I boot into Android and get it then?
[Desire Android Development] iinga:
I just wanted to know what files were actually made into the recovery. Eg what is in the folder on your sd card
[Desire Android Development] bemymonkey:
Ooooh. No MISC, I checked ;)

android_secure.tar

boot.img

cache.img

data.img

ext.tar

nandroid.md5

system.img
[Desire Android Development] iinga:
Ok, what had you done prior to backing up. Is it just this backup file?
[Desire Android Development] bemymonkey:
I'm beginning to feel a little lost. Could you rephrase the question? Or explain the reasoning behind it?

Prior to backing up, I'd done nothing. I've been using the same nightly installation since around ~nightly 180. FireRat Apps2SDEXT partition and so on... was running the latest nightly without problems.
[Desire Android Development] iinga:
Is it just that one backup that causes a usb brick?
[Desire Android Development] Amon_RA:
Weird...

Could you provide a bit more info :

- hboot/radio version ?

- S-OFF / S-ON ?

- Did you flash a custom HBOOT or anything else that alters the partition sizes ?

- Could you please provide a recovery.log ? Make it right after you did a restore (so don't reboot).
[Desire Android Development] PaY87:
Great job - like always!
[Desire Android Development] dislok:
Great job, but doesn't work with rom manager.
[Desire Android Development] dkawa:
So basically, there is a problem with the backup function in this v2.0.1 version?
[Desire Android Development] bemymonkey:
I'll leave that verdict to AmonRA after he's seen my recovery log file (when I get home tonight), but it isn't working properly on my Desire.

Has anyone else successfully created and restored a NAND+EXT backup on 2.0.1?
[Desire Android Development] mercianary:
@bemymonkey

Did you manage to get your rom restored? If not you could try fastboot to restore data, cache and system .img's, then manually restore ..android_secure and sd-ext. Then at least you'll have your data back.
[Desire Android Development] VK7HSE:
Yes I have! As I've been playing with AdamG OxygeN rom and at the same time I decided to give AmonRA a try...
[Desire Android Development] hallydamaster:
Restored many backups using 2.0.1, and nevery ecperienced any USB what so ever. Must be your setup ;-)
[Desire Android Development] bemymonkey:
After I executed your Fastboot commands and flashed the Modaco MISC-fix, everything works fine again. Thanks again for your help :)

Good to know, at least it's not really broken then. Maybe just a bad backup?

What setups do you two have?

I'm running:

CyanogenMod Nightly 218

FireRat A2SDEXT 1.36c, DDB activated

8GB SD card, 1GB EXT2, rest FAT

HBOOT 0.93 (Alpharev) w/ N1Table

-edit- Just tried a straight backup + restore (no flash or wipe between 'em), worked without problems. Looks like the backup was broken for some reason... I'll try restoring that one again and get a log.
[Desire Android Development] mad-murdock:
i did a couple of backups & restore's with 2.0.1 - everything went fine and i also checked if whole sd-ext is backed up/restored
[Desire Android Development] bemymonkey:
It's really starting to look like the backup was just bad. Copying the borked one to SD card now, will restore when it's done and then post a log...
[Desire Android Development] mad-murdock:
amon ra + gingerbread => usbbrick

i installed oxygen 2.0 test4 (gingerbread AOSP), later made a nandroid backup, restored my cyanogen, worked fine as usual, then i restored the gingerbread backup.

i ended up with a usb brick (misc partition destroyed) and a system not booting.

i started recovery again, flashed oxygen rom, rebooted, everything worked. data and sd-ext partition were restored like they should. so it probably was the system.img or boot.img

i have no recovery log, since i had no time, but i am sure, you can reproduce it (: if you cannot, tell me, i brick my desire again for the log.
[Desire Android Development] bemymonkey:
Aha! Looks like we're getting closer to finding the culprit... but how come the problem doesn't appear until after a restore then?

-edit- We have another one: http://xdaforums.com/showpost.php?p=9952345&postcount=496

Looks like Amon_RA was maybe right... it's Oxygen-Gingerbread?

-edit2- Looks like I just don't have any luck with Nandroid. Trying to restore the "faulty" backup in order to get a recovery log file, and it just won't finish restoring. Half of the entire display is filled with dots... is it safe to pull the battery? o.O

-edit3- After a battery pull and a restore of the "faulty" backup, I now have a bootloop (WTF). And a USB-Bricked Recovery... :|

-edit4- Here's the recovery.log: http://www.multiupload.com/Z9MYY2A6LH
[Desire Android Development] Amon_RA:
I don't see anything strange in your recovery log, looks like it's restoring everything fine.

The only weird thing might be the "mtd: read error at 0x00000000 (Out of memory)" but that's after the restore.

As you can see the MISC partition is not even touched...

Both you and mad-murdock are using the alpharev HBOOT with N1table, I wonder if the same is happening when you use the alpharev HBOOT with stock table...

It also seems to only happen with the Oxygen ROMs => Can anyone point me where I can find the official builds of these? Is it the Oxygen ROM posted by AdamG here in the Desire XDA forum?
[Desire Android Development] bemymonkey:
This is becoming ridiculous - I just restored the backup that I made at ~11:000 (less than 3 hours ago), the one that restored just fine then, and that has now USB bricked me too. :rolleyes:

If I have time later this week I'll try with regular partition layout... :(

Yep, AdamG's Oxygen Gingerbread here in the Desire forum.

The weird thing is, the backups I just restored had nothing to do with Oxygen - one was made before Oxygen had ever been flashed, and one was made three hours ago. Both restored with USB brick just now.
[Desire Android Development] Jagdish84:
I used the Alpharev stock HBOOT and got USB bricked on several occassions after running nandroid, i got bk to version 1.7.5(or something like that) which is a port of your Recovery, everything was ok, since you posted 2.0.1 i removed the recovery.img(via fastboot) and flashed your 2.0.1, all seems ok now, dunno what happened but it kindda worked itself out(i changed to Alpharevs N1table since then as well).
[Desire Android Development] bluelavender:
Jagdish, now you know the answer to your question to me some times ago "why i back to s-on after s-off" ;) that's only part of quirky thing of s-off i found... i let you find out the rest ;))
[Desire Android Development] bemymonkey:
Are you saying this problem is related to S-OFF? I highly doubt it... why would that be the case?:confused:
[Desire Android Development] Uqbar:
Hi.

I did a Nand + Ext backup. Tested a ROM and then did a Nand restore.

The result was an unusable phone so I had to reinstall everything!

This has happened twice now.

Any hint?