yashsingh1/xdaforums huggingface dataset:
[HD2 Android NAND Development] tmihai20:
I am using MAGLDR. My ROM is still booting, I took the img file from the 4.0.0.2 archive (the one I was using before flashing 3.2.0.1), I flashed it from terminal and it looks like I can use recovery now. I am getting errors from applications that were running just fine until a few days ago (I am not sure these errors are related to the little gimmick with recovery). I didn't know I could specify filesize instead of filename for recovery (it seems logical and normal to be able to use both options). I was thinking of generating a 5 MB dummy file to use instead of an actual recovery img file so I could use any recovery img file that doesn't go above 5 MB. So I will use the following flash.cfg as soon as possible:

misc ya 1M

recovery rrecov|ro|nospr filesize 5M (should I use recovery rrecov|ro|nospr 5M instead?)

boot yboot|ro 5M

system ya 150M

cache ya 5M

userdata ya|asize|hr allsize

It is a little strange that SD card based recovery doesn't work (the phone loads it, then it just closes no matter what version I am using). I thought I could at least use SD card based recovery.
[HD2 Android NAND Development] clyder:
This is the flash.cfg I used:

misc ya 1M
recovery rrecov|ro|nospr 5M recovery-raw.img
boot yboot|ro 5M
system ya 150M
cache ya 30M
userdata ya|asize|hr allsize

Before that instead of 5M there was filesize tag. I havent had any issue with installing CWR via terminal emulator since then.
[HD2 Android NAND Development] tmihai20:
So you specify you want to use 5 MB for recovery and you flash whatever recovery you have in recovery-raw,img. You don't use the img file size as a marker. This setting should be used by all ROM chefs.
[HD2 Android NAND Development] clyder:
+1 on that
[HD2 Android NAND Development] Daekin:
I just spotted 4.0.0.5 in the Desire thread...hope there will be update of this soon to reflect latest changes :)
[HD2 Android NAND Development] Hammerfest:
no kidding, something about the latest and greatest (besides the actual changes that make it worth the update) just gets me excited! its the NEW "NEW"!
[HD2 Android NAND Development] arif-ali:
If you check my nightlies uin my sig, you'll find them there

The reasons why it hasn't been upated, is that it has issues with backup and restore. Otherwise I would have released it already
[HD2 Android NAND Development] Hammerfest:
thanks for the info, seeing as I dont use backup/restore from CWM this might be a good time for me to test it out (anything else wrong you see?)
[HD2 Android NAND Development] Daekin:
what issues are you talking about exactly?

I have heard that 4.0.0.0 had issues restoring sdext...but since in a2sd build there are only apps, it is OK for me that it does not work because I can flash system apps using CWM and then user apps with 3rd party backup software...
[HD2 Android NAND Development] seadersn:
*oops* thxbutton has to move! :D if sdext isn't woprking, there's no sense to update first post in my opinion; there would be too much unnecessary negative announcements with it. the link for the newest one is in his sig ;) arif's recovcery foilder. next fully stable version will be linked in first post
[HD2 Android NAND Development] arif-ali:
+1 on that

Maybe worth changing the title, so not to confuse the users.

I will try compiling 3.2.0.2, which came just before 4.0.0.0, and worth looking at, I will post that here soon, and see if we can get a more recent stable version, and see if/and what has caused any of the issues
[HD2 Android NAND Development] seadersn:
i've compiled 3.2.0.2 from june 09, 2011. would be nice if someone could test this with sd-ext...? :)

pls find the files attached; magldr sd-card version not available atm :(.

3.2.0.2 from june 09, 2011
[HD2 Android NAND Development] white-energy:
Oh god! why when i face the problem and find the solution.. the bug gets quickly fixed.. but when i need help.. no one knows anything, this place becomes quiet.. -.-'
[HD2 Android NAND Development] louie317:
No data with 3.2.0.2

I flash 3.2.0.2 from 3.2.0.1

Reboot. Back-up successfully via recovery . Reboot. And no data (normally either 3G or H). Wait for several minutes, and still no data.

Reboot. Still no data for several minutes. Re-flash 3.2.0.1.

Reboot and data is fine with 3.2.0.1

Weird.

MagLdr. 2.15 Radio. USA T-Mobile.
[HD2 Android NAND Development] Bingoig11:
Hi,

I've a question:

I downloaded the recovery_4.0.0.0_leo.img.zip

I downloaded the 250Mb partition layout according to this thread.

Followed the process in OP to flash with MAGLDR NAND

But when going into AD Recovery it still displays 3.0.0.5

What did I missed?

EDIT: Downloaded 3.0.2.5 and re-flashed, it works, issue resolved :D
[HD2 Android NAND Development] clyder:
I have just tested 3.2.0.2. and it doesn't work for me. I am on cLK 1.4.0.1. right now.

What I did was:

-did a backup in 3.2.0.1. just in case

-did a backup in 3.2.0.2.

-reboot to see if I have data issues like louie317. Data worked fine, I tried turning wifi on/off, airplane mode also, and data went back everytime

-did a full wipe in CWR and did a backup from 3.2.0.2. (got stucked in fastboot everytime)

-installed 3.2.0.1. again

-tried to do a restore from backup made in 3.2.0.2. (again stuck in fdastboot)

-tried using advanced restore and I realized that it doesnt restore sd-ext. It just writes checking MD5 sums, restoring sd-ext and shortly after that closes restore.

- restored old backup made in 3.2.0.1.

-booted into android
[HD2 Android NAND Development] clyder:
I have just realized that I cant do a full restore with cLK. I have tried in 3.2.0.1 and 3.2.0.0. Problem is with restoring boot. If I install fresh rom and resotre only boot it just get stuck in fastboot when phone starts. If I restore everything except boot everything works OK. Does anyone else has such experience?
[HD2 Android NAND Development] seadersn:
do you have 1.4.0.1 installed? it's precondition for newer versions of cwm; sounds lime you have 1.4 installed :(
[HD2 Android NAND Development] clyder:
You are right. I initially installed 1.4.0.1. but few days ago I did another clean install of cLK and probably took the wrong files.

I did not another test with 3.2.0.2. but it failed to restore sdext again. In 3.2.0.1. it restores OK.

I'll try full backup/restore test in 3.2.0.2. later.
[HD2 Android NAND Development] seadersn:
ok, so 3.2.0.1 is latest 'fully stable version' for you, which restores everything as it should, incl. sd-ext partition? good to know for looking at code; maybe we find sth which is causing this. :)

thank you for testing ;)
[HD2 Android NAND Development] clyder:
Not quite. When i said that in 3

2.0.1. it restores OK I meant sdext only. I tried now to do a full backup/restore in 3

2.0.1. and after booting there was missing 90 percent off apps I had on sdext. I restored then only sdext and data and now it is OK. I dont have much time to play with it but later i will do another test both with 3.2.0.1. and 3

2.0.2.
[HD2 Android NAND Development] criszz:
3.2.0.1 doesnt restore sdext at all in full restore mode. i will back to 3.1.0.0 version from rom manager
[HD2 Android NAND Development] clyder:
I just did some testing.

Since 3.2.0.1. failed to restore sdext I did next:

-installed 3.2.0.0. and did a full restore from a backup made in 3.2.0.1. - RESTORED OK

-did a backup in 3.2.0.0., full wipe, full restore of the same backup - RESTORED OK

-reinstalled 3.2.0.1., tried full restore of the both backups - BOTH times SDEXT failed

-installed 3.2.0.0. again, another full restore and it is working OK.

So the breaking point seems to be in 3.2.0.1 version.

In 3.2.0.1. full restore dont work, but individual partition restore works

In 3.2.0.2. both full restore and sdext restore dont work.
[HD2 Android NAND Development] casemandan:
So i'm assuming using the 4.0 version has some issues, no wonder I had issues flashing some roms on it...

So I've been using the 3.1.0.0

Is it worth upgrading to 3.2.0.2 since i had some little issues with 3.2?
[HD2 Android NAND Development] clyder:
Two posts above yours. For me 3.2.0.0. works great.

But I am on cLK, I am not sure what is the situation with magldr. I used 3.2.0.1. when I was on magldr, but I never did full restore on it.
[HD2 Android NAND Development] seadersn:
k, i'll change first post when i've got my pc back. is 3.2.0.0 available @ this thread? tapatalk is &%$# in terms of searching (and editing, too) -.- if not, could you pls upload it...?
[HD2 Android NAND Development] Hammerfest:
you know, i didnt see/experience any issues with 4.0.0.0, or 4.0.0.2... what issues does it have that has caused the revert?

as I said I as in ME, dont have any issues, then again, I dont backup from CWM (a few times, but not enough to be considered my MAIN source), im even looking for 4.0.0.5 and above for my HD2... but sadly... now its gone back to 3.2.0.2.... Q_Q
[HD2 Android NAND Development] :
If you try a full restore cwm is not able to restore the sd-ext partition. That issue starts with version 3.2.0.1
[HD2 Android NAND Development] clyder:
I dont know if you found it but I downloaded it from this post.
[HD2 Android NAND Development] seadersn:
thank you :)
[HD2 Android NAND Development] seadersn:
changed first post to last fully stable / working version :)
[HD2 Android NAND Development] tytung:
Below is from the first post.

I totally agree with it.

We don't need to update CWM if new changes of source code are not related to HD2.

Thanks.
[HD2 Android NAND Development] seadersn:
hey folks :)

as you all may know now, 3.2.0.0 is the last fully stable version for hd2. however, there is a feature that was introduced in version 4.0.0.8, which i wanted to use in version 3.2.0.0: the ability to show parts of log-file in recovery itself, which could also be used to report error via rom manager.

i've applied the necessary changes to version 3.2.0.0, so advanced menu now shows "Show log" menu point. please test this version with sd-ext backup / restore and tell if this special part (restoring sd-ext from within full restore (not advanced restore)) is working; the new log function is tested and working.

find it attached, as cwm flashable zip. have fun :)
[HD2 Android NAND Development] djbarney:
seems to be working okay here seadersn :) no problems so far
[HD2 Android NAND Development] seadersn:
thx for feedback ;)
[HD2 Android NAND Development] Daekin:
I have not tested restore capabilities of 4.0.0.8 and 4.0.0.9 but at least in runtime it is working good (I have tested first 4.0.0.8 daily build by arif-ali) previous 4.0.0.5 was so bad that I could not get my ROM to boot after clean flash...if someone can test restoring in 4.0.0.9 builds and if it will work, we can again get the new one :p
[HD2 Android NAND Development] larryyy:
Hi. So I flash cLK and I got problem with drivers. My Leo restart after flashing and show [2710] --portchange--. Windows can't find driver.

Anyone got the driver?
[HD2 Android NAND Development] seadersn:
http://www.multiupload.com/633J7YLPZK

take this package, google drivers are included :)
[HD2 Android NAND Development] larryyy:
Yeah! This is it! You got big + :)
[HD2 Android NAND Development] Daekin:
Just flashed 4.0.1.0 from arif-ali daily builds - the one from July 14 (last commit to CWM is on July 13).

Then clean flashed my ROM (Sense of Eclipse 2.0.0.0 Data2EXT cLK) [layout 5-400].

Then made a backup using CWM.

Finally restore my backup using basic restore and then advanced restore.

RESULT: All working!

@all: test it too, after more positive reports, it can be put into OP as current stable version.

here is the link: https://www.dropbox.com/s/xoio3dwcxwe25dj/4.0.1.0/recovery_4.0.1.0-20110714_leo.img
[HD2 Android NAND Development] seadersn:
jep, would be nice :)
[HD2 Android NAND Development] clyder:
I have just installed 4.0.1.0. but version from July 16th and I can confirm that backup/restore is working.

I did a backup in 4.0.1.0, wipe data/cache/dalvik, installed another rom, booted it, then did a restore (partition by partition), booted succesfully, another wipe, full restore, and now I am back to android. No problems found so far.

Only thing I noticed that is different. Not sure if its a bug of a feature.

When I was doing backup/restore progress bar was not active (always gray) and there was no listing of filenames that are being backuped/restored...Only info I had was lines with info on what partition started backing/restoring.

Not really a problem for me, just got used to it.
[HD2 Android NAND Development] djbarney:
Noticing the same here, not really important ofcourse, but it'd be nice to get it back, to get a sense of where in the progress you are when it's backing up. So far it seems to be working alright, usb mounting, updating and installing zips for roms seem to work fine here, haven't tried replacing my current rom yet, because it's running very well as is now :) so, i guess except for the progress indicators, everything's working just fine :D

small bug found: when using "reboot system" function in cwm, with usb plugged in to the laptop, it seems to just restart cwm... unplugging usb and using same function does work like expected though (booting to android). Can't remember if that's an older feature that i failed to notice before, or if it's new :)

(forgot to mention that i also used the "recovery_4.0.1.0-20110716_leo.img" build, found in the dropbox link posted earlier)
[HD2 Android NAND Development] seadersn:
good to know, clyder & barney; thank you for testing. both your restorings were with sd-ext partition = full restore is, regarding sd-ext, working again.

i'll test the usb restart bug tomorrow when i'm at home, with my 3.2.0.0 version. depending on the result, i think i'll let build v4.0.1.0 with yes / no patch.

regarding the progressbar: is a file called '.hidenandroidprogress' present in /sdcard/clockworkmod? this file is created by a setting in rom manager, should be named 'fast backup and restore' in english language. can you check this if it is ativated?
[HD2 Android NAND Development] djbarney:
The file you mentioned is not there on my phone. There is a .settings file, which seems pretty old since it mentions version 3.1.0.0 of cwm, which is also what rom manager reports as being the current and latest for the hd2. The feature in rom manager is called "quick backup and restore" in my version of rom manager (4.3.2.4 free on market), and is not ticked in the settings. I tried toggling it, but it does not create the file or add anything new to the .settings file in /sdcard/clockworkmod.
[HD2 Android NAND Development] seadersn:
merci. it's only recovery related then. and the titles of the files, which are copied to phone, aren't displayed anymore, too...?
[HD2 Android NAND Development] clyder:
Yes. Only lines like 'restoring data' are shown until it jumps to the next partition.

BTW, I also have only the .settings file in /sdcard/ClockworkMod
[HD2 Android NAND Development] djbarney:
Yes, indeed. It only shows the partitions it's currently backing up, and at the end shows that it created an md5 hash and that it's completed. The progress indicator is there, but it does not "fill up", it remains gray.
[HD2 Android NAND Development] Daekin:
I do not care that it is not showing status...remember: writing an output to screen between resotring files slows the process, so no info = faster restore ;) and since it works, I am OK with that...

(and I alwayt unmount SD card manually before resetting, so that small bug when resetting with SD mounted is not critical for me too :p)
[HD2 Android NAND Development] seadersn:
decision: against 4.0.1.0 yes/no :(

reasons: these two bugs mentioned before (no progress bar / reboot system = reboot recovery if usb cable plugged in) and no advantages for hd2 :)

reboot system works on 3.2.0.0. but i'll link the "view log version" in first post, maybe someone's interested in it.
[HD2 Android NAND Development] clyder:
I am fine with 4.0.1.0. Important thing is that it is doing its job well. Dont really care about those two bugs.
[HD2 Android NAND Development] seadersn:
jep, but changes aren't relevant, and maybe the majority of the people may cry "this and that isn't working!" :D

i can do this yes/no version, but won't link it in first post; deal? :)

edit: done :) btw, does arifs 4.0.1.0 already contain yes/no patch...?
[HD2 Android NAND Development] clyder:
Yes it does...
[HD2 Android NAND Development] seadersn:
xD then my compiling was not needed :eek: good to know :) thx for info!
[HD2 Android NAND Development] arif-ali:
I have now started building a weekly build, which will drop into the same dropbox folders for CWR, sd builds

nightly builds as usual
[HD2 Android NAND Development] Daekin:
I see it there..and it is very good timing, because it was yesterday a new 4.0.1.4 version was checked in to GIT :) will test it...
[HD2 Android NAND Development] Kameirus:
hate to be a pain in the butt

can someone please make me

a 8/240/10 clk nbh

will be greatly appreciated

Thanks
[HD2 Android NAND Development] mally2:
Hi All

Sorry if this is the wrong thread to post this

I was wondering of CWR could be modified to have an option do just a DATA backup rather that a full NANDROID backup every time,

for ex it has an option to do an advance restore where DATA can be restored, so why not the same with BACKUPS...

It saves a lot of time, really
[HD2 Android NAND Development] seadersn:
this for sure is true...! i've got some time atm, and will try sth; i believe for now and testing it's sufficient to add only one option "backup data only" (/data and /sd-ext).

but first: can someone confirm latest 4.0.1.4 is fully working? i'm using it atm, but w/o sd-ext stuff, everything's fine, but i don't know about this particular thingy.
[HD2 Android NAND Development] clyder:
I have just installed it. During installation with flash_image in terminal emulator I had lots of out of memory errors followed by lots of flashing progress info but CWR installed properly. Dont know what was the deal with those errors. I have 5MB fixed recovery partition.

But anyway recovery was flashed OK during that flash so it was probably some error caused by me...

Anyway, I did a full backup, wipe everything, full restore, all in 4.0.1.4 and with ext4 partition that is about 200MB full. Booted to android after that and everything is in its place.

There is still missing progress during backup/restore but it works as it should.

I used file recovery_4.0.1.4-20110726_leo.img
[HD2 Android NAND Development] djbarney:
ive got 4.0.1.4 running stable as well, but like you, i haven't tested the sd-ext stuff since i don't use that with my current rom (nexushd 2.8 by tytung). Except from the small progressbar bug and the restarting cwr when usb is still plugged in bug we mentioned earlier, everything else seems to be working fine.
[HD2 Android NAND Development] seadersn:
progress bar and restart function works like it should here for me @ 4.0.1.4 :)

k, i'll try this @ "backup data only" menu entry.
[HD2 Android NAND Development] clyder:
I dont have a restart bug. Just tried reboot option with USB cable plugged in and it restarted normaly.

About progress bar for me it only shows some kind of idle animation with stripes moving but no actual progress and no info about files being copied. I have tried restoring only sd-ext and it also dont have progress but it restores OK.
[HD2 Android NAND Development] mally2:
That will be marvel :), thanks for investing the time... would save us a lot of time :)
[HD2 Android NAND Development] MarkAtHome:
Hi seadersn - How do we get ROM Manager to work with the versions beyond 3.1.0.0?
[HD2 Android NAND Development] seadersn:
4.0.1.4 is working well :) 3.1.0.0 isn't working with rom manager anymore...??
[HD2 Android NAND Development] seadersn:
why is a version below 3.1.0.0 needed...?

btw: testings with 'backup data only' aren't stopped, but it's trickier than i thought. will give feedback on this next 3to4 days.

btw: for displaying progressbar tick 'quick backup' in rom manager options; this is having the opposite effect from what it means :ugly: then the progressbar / name of file currently copied/backed up in cwm will be shown ;) i'll update first post today.
[HD2 Android NAND Development] Rick_1995:
Hey seaderson,

You guys build this from koush's source or CM's source ?

The CM bootable recovery for bravo/desire today got the offmode charging patch including the png images for checking the charging status and proper power button reset. Hope you guys will look into it and maybe provide it as an option if not as default ;)
[HD2 Android NAND Development] seadersn:
it is built from cm source. i've seen this charge thingy and compiled one; find it attached :) i'm messing around with charans kernel and have no time to do this :D ;)
[HD2 Android NAND Development] Rick_1995:
hmmm, doesn't seem to work. Hope you'll look at it after the kernel :D

btw, why don't you post the dmesg on the thread so giorgio and charan can also have a look at it ?
[HD2 Android NAND Development] seadersn:
let's hop over there ;)
[HD2 Android NAND Development] MarkAtHome:
Oh. It works fine, but ROM Manager says that the current CWR is 3.1.0.0, indicates that that is the version you running, even if you flashed a more recent version (e.g. 4.0.1.0). If you choose to have ROM Manager flash CWR to the latest version it will flash 3.1.0.0 and your 4.0.1.0 bites the dust. It does not seem that the are working together.
[HD2 Android NAND Development] seadersn:
workaround for this: edit /sdcard/clockworkmod/.settings file and change the version number to anything you want; above 3.1.0.0 makes sense, of course. save it, go into application settings, choose all and then rom manager; delete data / cache for rom manager. @ next start of RM this problem's gone :)
[HD2 Android NAND Development] MarkAtHome:
Will give it a try. Thanks.

Out of curiosity, why should we need a work-around? ;-)
[HD2 Android NAND Development] seadersn:
only because of we can do it :D
[HD2 Android NAND Development] MarkAtHome:
"Of course!" said the blind man. :-)

Continuing... since ROM Manager is a shell for CWR, why the disconnect?
[HD2 Android NAND Development] seadersn:
sry, what discon do you mean...? :)
[HD2 Android NAND Development] arif-ali:
The disconnect is there, only because we only submit the CWR to CM team/koush. When we ask koush to build us a new CWR, only does it then come under RM, it's not under our control.

At least it is a starting point for some people.

If people are happy with the current v4.0.1.4, I will get the RM CWR updated to that level by speaking to koush
[HD2 Android NAND Development] tomoffel:
sorry for the question.. but where is the 4.0.1.4? I just can find the .1.0..
[HD2 Android NAND Development] arif-ali:
Check the link in my signature for the nightly builds, or the link below

https://www.dropbox.com/s/xoio3dwcxwe25dj#view:list
[HD2 Android NAND Development] tomoffel:
wow, that was fast :)

I am a little drunk right now, but.. to update the 4.0.1.4 on my CWR I only have to download the recovery_4.0.1.4_leo_CWR.zip and "flash" it in CWR right? :D

EDIT:

Just tried it and it worked, so again thank you :)
[HD2 Android NAND Development] seadersn:
don't drink and flash ;)

i've updated first post with recent version 4.0.1.4, which is working well for now. only thing is that you need to check "quick backup and restore" in rom manager for showing progress bar and filenames in cwm. so this option turned other way round :ugly: if unchecked, no progress bar and filenames.
[HD2 Android NAND Development] MarkAtHome:
I have not experienced any problems with 4.0.1.4 other than the previously-mentioned progress bar, which is not a deal-breaker.

Would be nice if RM would check which version of CWR was already installed, the latest available stable and beta versions, and subseqently provide the user a choice of versions prior to implementing a CWR flash from the RM shell... or not... :-)
[HD2 Android NAND Development] MarkAtHome:
Thank you.