yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] dweebs0r:
This recovery works well for me. Flashed using fastboot.

I also used this recovery to reformat the sd-ext partition and now my nandroid backups complete without freezing (they would freeze on the sd-ext backups last time requiring a battery pull).

Thanks for compiling and sharing this!

-D
[Nexus One Android Development] Deleted member 2044343:
restoring doesn't work with sd-ext (1GB ext4 in my case): it's always aborting during restoring data! no cache and sd-ext restoring and no "restore completed" CWM message but jumping back to the CWM main menu.

it's the same with the other CWM3.2.0.1 for Nexus One.

:-(
[Nexus One Android Development] sir*mez:
This Corrupts EXT partition!

This recovery corrupts EXT partition while the 2.4.0.1 doesn't restore!!! I'm staying away from clockwork recoveries from now on! I'm sick and tried of restoring corrupt ext partitions!
[Nexus One Android Development] zyonee:
So it's safe if not using sd-ext. Sorry I can't help solve the problems...
[Nexus One Android Development] Kelvino9:
Yes, now having the same problem with sd-ext backups too.
[Nexus One Android Development] heywtf:
Aww :(

But still, thanks for bringing it over to the N1.
[Nexus One Android Development] zyonee:
Updated OP to version 4.0.0.0.
[Nexus One Android Development] :
unfortunately cwm 4.0.0.0 isn't able to mount sdcard :-(
[Nexus One Android Development] zyonee:
A quick workaround

1: Reboot into recovery (4.0.0.0)

2: In a console on your computer, type "adb shell mkdir /data/media" (without the quotes).

The problem is that /sdcard is a symbolic link to /data/media where the SD card is actually mounted. But in the source for the recovery, it seems there is nothing that creates this folder in /data, so there's nowhere to mount the partition and that's why it fails.

I'm trying to compile it into the recovery now.

Edit: Fixed. Re-download and mounting /sdcard should work. Please test.

Edit 2: Once you leave the file list, you'll have the error again. Then you have to "adb shell umount /sdcard" each time you leave a file list. Looking into it.
[Nexus One Android Development] zyonee:
Added back the 3.2.0.0 version in the OP so you won't have the /sdcard mounting issue. Hopefully it can be resolved soon, so we can start using the 4.0.0.0 version. Sorry for the inconvenience. :)
[Nexus One Android Development] blahbl4hblah:
Flashable zip of 3.2.0.0

I thought I'd make it simple for everything and make a flashable recovery of 3.2.0.0 for everyone

Enjoy!
[Nexus One Android Development] zyonee:
I edited 4.0.0.2, adding j_r0dd's mods and compiled it. Works well on Nexus One and Nexus S. No more sdcard mounting bug, it's been fixed. Can't test it on any other models myself. Updated first post of this thread.
[Nexus One Android Development] :
First of all: a big thank you to you zyonee in bringing cwm4 to our Nexus One.

It seems that cwm has still its challenges with backing up or restoring sd-ext (in my case ext4): cwm is ignoring my ext4 ... :-(

Is it me??
[Nexus One Android Development] zyonee:
Maybe it hasn't got any support for ext4. I'll investigate this.
[Nexus One Android Development] ronniecarlough:
Did not work for my backup to my nexus 1. Can't backup anything. I tried to flash new recovery. :(
[Nexus One Android Development] zyonee:
Don't know about the ext4 thing for sure, but my N1 (without sd-ext) can backup just fine. Expecting restore to do the job as intended as well.
[Nexus One Android Development] iinga:
Hey, I just popped in here because desire has this exact same problem. Because sd-ext is used, most people do not have apps in the /sdcard/.android_secure folder. In the restore process, this is called before sd-ext restore, and since 3.0.2.1 or something, the restore process bombs out when it tries to restore /sdcard/.android_secure. I am yet to understand why, but compiling the recovery without /sdcard/.android_secure seems to allow it to restore correctly, but obviously would stop it working for people who use /sdcard/.android_secure, so I'm not sure where to go with this.
[Nexus One Android Development] zyonee:
Identifying the problem is always the first step to solving it. I might be able to mod this version into ignoring /sdcard/.android_secure, but it would take a lot of time, since I'm compiling for several devices. Hopefully we can find out why it bombs out and fix that instead of having to choose between two alternatives (one recovery image for all people).

Edit: In nandroid.c, one could easily comment out the backup/restore sections that handle /sdcard/.android_secure. But like I said, I'm not comfortable producing several versions with different functionality. Let's see if we can find out what goes wrong instead. It might reside within nandroid_restore_partition_extended()
[Nexus One Android Development] iinga:
Yes, I looked at nandroid.c and commenting it out works, but seems a pain to have to edit the nandroid.c with each update to it. I'm not sure where the problem lies though, but I have a suspicion its to do with either the backup or restore of .android_secure, but I'm more inclined to think its the restore, seeing as I have a .android_secure.img in my backup directory (which is of an empty directory), but it can't be restored.
[Nexus One Android Development] Kelvino9:
Thanks zyonee and iinga for updating CWM to our devices. Also a big thank you for hanging in there and figuring out the bugs. Totally appreciating your work.
[Nexus One Android Development] :
I have attached my cwm backup directory, it seems there are all necessary files in (backup successful?). But unfortunately the restore doesn't work. It doesn't use e.g. the sd-ext file ...

I hope the information helps ...

Thanks in advance.
[Nexus One Android Development] zyonee:
OP updated. Version 4.0.0.5.

The recovery may show 4.0.0.4, but it's only cosmetical. Android.mk in the source tree shows version 4.0.0.5.
[Nexus One Android Development] MaDInDy:
Can i use CWM 4.0.0.5 with MIUI rom (I using RoDrIgUeZsTyLe MIUIMOD) ?

No issue ?
[Nexus One Android Development] zyonee:
Should be no problem. I haven't tested it fully, but I don't see why it wouldn't work. Might have issues with backing up or restoring ext4 partitions, though. Some people have reported this.
[Nexus One Android Development] clustered:
Thanks very much! flashed!
[Nexus One Android Development] zyonee:
Just updated the 4.0.0.5 version with some ext4 additions from roalex. Hopefully this can solve the ext3/ext4 issues some people have been having.

Make a nandroid backup with a proved working recovery version, then try this if you want to. I'm not responsible for any data loss this may cause, this is a test version of ClockworkMod Recovery. ;)
[Nexus One Android Development] sir*mez:
Im going to test this out on a test sdcard. I'll let you know the outcome.
[Nexus One Android Development] bunnahabhain:
i have installed amon-RA recovery. Is it recommended to update to thid one?

What benefits would i have? And do i just have to flash this over amon-RA recovery via zip (in amon-RA itself??)
[Nexus One Android Development] sir*mez:
No more corrupted ext partition, yyaaaayyyy!!!

FINALLY!!!!! :D :D

No more corrupt Ext partition and it restores Ext partition from backup. I will continue to test it out, but it works. We shouldnt be afraid of corrupted Ext partitions from CWM recovery compiled by zyonee!!
[Nexus One Android Development] zyonee:
It's not my code, it's roalex who fixed it. Glad to hear it's working though. Hopefully it works on other models as well.
[Nexus One Android Development] sir*mez:
Yea but thank you for bringing it to us!!

Edit: okay, now it doesn't want to backup, it starts to backup, then stops and doesn't finish. It worked well on my 4gb sdcard w/ 1gb ext. But it doesn't work with my 16gb w/ 1.5gb ext. Its weird, I'm going to have to pop in my 4gb and see what happens again. But the good thing is it doesn't corrupt my ext which I'm very happy about!
[Nexus One Android Development] bobtentpeg:
I had the same thing happen to me too.
[Nexus One Android Development] zyonee:
Weird.. I really have no idea why it would make a difference between a big and a small sdcard. I'm still hoping that there will be official ext4 support in cwm, in which case I can simply merge that code into this mod. Once again, I'm not a skilled c/c++ programmer, I merely port other people's code.
[Nexus One Android Development] zyonee:
New addition: Added "Show log" in the advanced menu. This can help when reporting errors here. Use it. :)

Redownload 4.0.0.5 from OP.
[Nexus One Android Development] sir*mez:
Heres the log I got:

http://pastebin.com/Z6svg31g
[Nexus One Android Development] zyonee:
Strange. Which files have been created, and what are their sizes?
[Nexus One Android Development] sir*mez:
It creates a boot.img with 3.50Mb, recovery.img with 4.00Mb and system.img with 2.06Kb.
[Nexus One Android Development] zyonee:
So it cannot read /system for some odd reason... :(
[Nexus One Android Development] sir*mez:
Yep, it can't read the /system partition for some reason, I've been trying every combination possible. Its almost there tho, I'm sure that in no time at all the code will be added to fix this problem.
[Nexus One Android Development] zyonee:
I've reverted my ext4 mods and instead picked them directly from roalex's repo. Also included the correct recovery.fstab changes (I think). Will hopefully have time to upload the new version today. Not sure if it can help with the /system problem, though...
[Nexus One Android Development] zyonee:
Updated version to 4.0.0.5.z110621 - Edited recovery.fstab to allow ext4.
[Nexus One Android Development] sir*mez:
Testing this version right now, I'll report soon.
[Nexus One Android Development] zyonee:
It may still have issues formatting ext4 partitions. I think I have the proper fix an will apply it tomorrow. ;)
[Nexus One Android Development] sir*mez:
You are correct. I get the error while restoring sd-ext. Thank you and I hope Im not becoming a bother to you, lol.

http://pastebin.com/s0Zc2vLf
[Nexus One Android Development] zyonee:
Not at all! In fact, I appreciate objective comments.
[Nexus One Android Development] zyonee:
New version (4.0.0.5.z110623) uploaded. This should hopefully get ext4 working. Please test wiping, formatting, backup and restore with ext4 partition.
[Nexus One Android Development] sir*mez:
I finally got some time today. Im backing up and soon to be testing this recovery.
[Nexus One Android Development] zyonee:
Great! Let's hope things are working now. :)
[Nexus One Android Development] sir*mez:
Everything works great with ext4 on my 4gb test sdcard. Now Im going to test it with my 16gb sdcard. Great work in finding what the last update needed, support for ext4 partition.
[Nexus One Android Development] zyonee:
I got help from roalex all the way, actually. Glad it works! :)
[Nexus One Android Development] momomok:
Have been wondering what's new with CWM 4.0. Performance improvement?
[Nexus One Android Development] zyonee:
Can't really remember, but if you look in github, you can see when the 4.0.0.0 commit was made and see what changes were done before it.
[Nexus One Android Development] momomok:
Thanks!

But which repo to read? There are so many repos under author: koush

(I'm sorry, but I am not really familiar with this github thing :p)
[Nexus One Android Development] sir*mez:
I went back to using my 16gb sdcard and it wont make a backup. On my 4gb sdcard it would let me do everything. Here's the log: http://pastebin.com/fTUV39J9

Backup would start and stop. In the backup folder I see boot.img 3.50mb, recovery.img 4.00mb and system.img 2.06kb.
[Nexus One Android Development] zyonee:
So it fails on system for some unknown reason. Strange.
[Nexus One Android Development] sir*mez:
Yes sir....
[Nexus One Android Development] zyonee:
And it shouldn't fail on system, since it's just the same size as before. I'd understand it better if it simply failed on sd-ext, since you changed the SD card. Weird.
[Nexus One Android Development] sir*mez:
I'm going to reformat my 16gb sdcard and see how that goes.
[Nexus One Android Development] zyonee:
I don't think it's going to work any better, but you might as well try it. ;)
[Nexus One Android Development] zyonee:
New update

Updated the original post with version 4.0.0.5.z110706. See the changelog in the OP. I haven't really changed anything concertning ext4 since 4.0.0.5.z110623.
[Nexus One Android Development] Kelvino9:
Any ETA for a 4.0.1.0 update?
[Nexus One Android Development] zyonee:
I've kind of given up on trying to make my own mod. If you guys want, I can compile and upload the latest versions from j_r0dd's sources, but it won't include "Reboot bootloader", "Show log", moving down the "wipe data/factory reset" menu command, etc. In effect, it'll only be j_r0dd's mods and not mine or other's. Most important, it'll also remove the ext4 additions/changes made by roalex, since j_r0dd hasn't included them in his sources. Whether that's a good thing or bad thing is up to you guys, since ext4 wasn't working well for everyone.

The main problem is that I'm not that skilled in programming, and I don't even know everything I need to know about git and how to keep my fork up to date with the changes made by koush, j_r0dd and others. My version is falling behind.

So: Would you want me to simply compile j_r0dd's version for different phone models? That wouldn't be very difficult for me. :)
[Nexus One Android Development] Kelvino9:
I think if your project is done for good and you don't mind compiling for us the latest version of j_r0dd's source I would be very happy.

Thanks for doing that!
[Nexus One Android Development] zyonee:
Ok, so here goes. I'm making a new attempt. Rebased everything on j_r0dd's current 4.0.1.0, but without roalex's ext4 additions. See original post.

Edit: Whoever did download my 110717 build from few hours ago, please redownload. The "Advanced Backup" was screwing things up. It created individual md5 files for each partition and would mess up the restore process unless a single md5 file for all partitions was manually created. Because of this, I reverted that commit.
[Nexus One Android Development] Kelvino9:
Thanks a lot for the update!
[Nexus One Android Development] zyonee:
Hope it works. It should, since the Desire build does, and it has the same partition layout as the Nexus One except for the sizes.
[Nexus One Android Development] blahbl4hblah:
Could you tell me where you added the ext4 sd-ext support?

Whenever I do show log after partitioning my sdcard it shows sd-ext as ext3 instead of ext4
[Nexus One Android Development] zyonee:
I didn't add anything about ext4 in this version, it's already included from Koush's CWM sources.
[Nexus One Android Development] zyonee:
New version in OP. Minor fixes.
[Nexus One Android Development] wind0zer:
I wish we could get like nightly auto build for the recovery. ::sarcasm emoticon::
[Nexus One Android Development] zyonee:
Hahaha. :)
[Nexus One Android Development] gibosn6594:
Would I be wrong to suspect that ROM Manager would let me know that there is an update to CW?

Or are these something different?

Thanks.
[Nexus One Android Development] zyonee:
Well, my 4.0.1.4 is quite up to date, but with some mods. ROM manager won't recognize mine and will say there's an update. ;)
[Nexus One Android Development] gibosn6594:
Interesting, what version does RM try to update you to?
[Nexus One Android Development] zyonee:
No idea, actually.
[Nexus One Android Development] blahbl4hblah:
I believe it's 3.0.0.5
[Nexus One Android Development] zyonee:
Updated original post. j_r0dd's 5.0.2.3 version is up. Please test.
[Nexus One Android Development] DeTool:
+1 amon ra all the way. Been burnt too many times by cwr.
[Nexus One Android Development] zyonee:
I wish I could help you guys. Anyway, the latest version changes nothing from the original 5.0.2.3 in terms of handling sd-ext. It's purely cosmetical changes like menu layouts.
[Nexus One Android Development] zyonee:
Version 5.0.2.6

New version and changelog in the OP. Please test. :)
[Nexus One Android Development] Spakainz:
Hm I'm useing RA recovery. I have problems with clockworkmod, when backuped my system, allways freezed on sd-ext backup. With RA I have not problems.
[Nexus One Android Development] zyonee:
Hmm, which versions of ClockworkMod did you use? And what size and file system does your sd-ext use? When I was still using the Nexus One with a 512 MB sd-ext (ext4), CWM was backing up and restoring without problems.
[Nexus One Android Development] Spakainz:
I'm tryied CWM 5.0.2.0 and 5.0.2.3, my sd-ext is EXT3 512MB...
[Nexus One Android Development] zyonee:
Strange. Could there be a permissions problem on the sd-ext partition? You say it freezes, does this mean you have to pull the battery, or can you go to the advanced menu and select "Show log" in CWM? Did you wait for a long time after it froze?
[Nexus One Android Development] Spakainz:
I'm wait about 10 min, nothing happens, then must pull battery. And everytime at the same time it freezes, my sd-ext is empty, because I don't use APPS2SD or other tool.
[Nexus One Android Development] zyonee:
Then maybe you should back up your FAT32 partition and repartition the card without sd-ext?
[Nexus One Android Development] DaXmax:
Hey bro, i created a flashable zip for recovery instead of going to the fastboot flash_image... -.-

So here, for an easy changing recovery... Here!

Link: http://db.tt/p8fLCOgE
[Nexus One Android Development] zyonee:
New version

Version 5.0.2.7 in the OP.
[Nexus One Android Development] zyonee:
New version

OP updated!
[Nexus One Android Development] Basil 123:
Great - any chance of a flashable zip plz?

Cheers

Baz
[Nexus One Android Development] zyonee:
Here you go. The zip not signed, since I never bothered to learn how to do that on my hackintosh, but it should work just as well.

I don't usually recommend flashing these things from within recovery. Fastboot is really not that difficult.
[Nexus One Android Development] ortigosano:
Signature verify fail

Hello everybody!

Some knows why I get this message: "signature verify fail"

./fastboot-linux flash recover recovery-clockwork-5.0.2.7.111102-j_r0dd_mod-passion.img

sending 'recover' (3402 KB)... OKAY

writing 'recover'... INFOsignature checking...

FAILED (remote: signature verify fail)

Happy Xmas!!

Thanks in advance!!!
[Nexus One Android Development] zyonee:
No idea. Are you sure your bootloader is unlocked?
[Nexus One Android Development] ortigosano:
yes!

the problem was that I typed recover and should be recovery!

thanks for you help!

Enjoy the rest of the year!
[Nexus One Android Development] zyonee:
Oops. :)
[Nexus One Android Development] Kelvino9:
Could you please compile an updated version for the Nexus One?
[Captivate Q&A, Help & Troubleshooting] axel4401:
My captivate will no longer vibrate. Haptic intensity is up, vibrate is turned on. I even went to the test using sgs tools. Nothing. I am running Serendipity 6.4. It's been a while since it has vibrated, but I'm just now getting around to asking the fine folks here. Thanks for any info.

:confused:
[Captivate Q&A, Help & Troubleshooting] bryman27:
Probably a hardware problem, flash to stock and see if it vibrates then.
[Captivate Q&A, Help & Troubleshooting] axel4401:
ok so, noob question. Do I just find a stock ROM and flash it? or is there a different procedure? If it's just a matter of finding a stock OS ROM, where might i find one?
[Captivate Q&A, Help & Troubleshooting] studacris:
http://xdaforums.com/showthread.php?t=731989

you really should've know that BEFORE you flashed away from stock.
[Captivate Q&A, Help & Troubleshooting] axel4401:
thanks, backing up apps and flashing right meow. will i have to reinstall clockwork and reroot? Any suggestions if I dont get my vibration back? Also, any ROM suggestions? Ive been running serendipity 6.4 for a while now and have enjoyed it, but i want a change.
[Captivate Q&A, Help & Troubleshooting] studacris:
that will take you back to stock 2.1 like you just turned it on for the first time.

if the vibration doesnt work from there call and ***** to at&t or samsung and get a warranty replacement as that would be a hardware issue.

if you still have the update.zip with clockwork on it rooting isnt needed just have that on the root directory of the /sdcard and 'reinstall packages' twice to install a rom.

as for rom suggestions noone can really tell you as its all based on personal preference.
[Captivate Q&A, Help & Troubleshooting] axel4401:
:( no vibration. oh well. I'd rather not sit on hold with at&t or samsung
[Captivate Q&A, Help & Troubleshooting] axel4401:
Thanks to the people that helped me. I think it's probably a hardware issue and now I will take it up with AT&T :( . I really do hate being on hold.
[Captivate Q&A, Help & Troubleshooting] wonder186:
I have the same issue. Did you replace the speaker/vibrator assembly? Thinking about buying one from Mobiletechvideo guy.
[Eee Pad Transformer Themes and Apps] Highland3r:
*Disclaimer*

The widget is very much a "beta"/"test". It come's as is. If it doesn't work/does weird stuff I'll try and investigate but won't make any promises.

Happy to listen to feature/improvement requests but they may not ever be implemented.

I'm new to Android Development (although not to java/development as a whole) so this is a learning exercise for personal knowledge gain.

*Disclaimer*

Now the excuses are out of the way, widget is attached.

Should be a case of installing and the widget will then be available. Some people have reported a reboot is required before the widget is visible

Tested against a ROOTED version of Prime! V1.4, also works fine on stock 3.1

Not working with clemsyn-blades cusom kernel (Widget reports dock as unplugged. Looks like a kernel issue rather than a widget/app problem)

Tested up to version 3.2 with no issues. Also working on ics (galaxy nexus)

Source code can be made available if anyone wants a laugh.

Added Configurable text size and color in V2.1

Enter a valid color (List - red, blue, green, black, white, gray, cyan, magenta, yellow, lightgray,darkgray) in the first box

Enter a valid textsize in the second. 20 is about right (was the default for v1.3 of widget)

There's some basic validation added, if you get a force close on config it's likely you've entered something wrong.

Planning on beefing up validation & available config shortly.

Downloads

Version 1.3

White - http://db.tt/DhjaUEA

Black - http://db.tt/RcPWpjq

Version 2.1.1

http://db.tt/8vAFlAh

--------------------------------

ChangeLog:
V1.3 - Initial Release
V2.0.1 - Added Basic Size & Color config.
Added Shadow to Text
Small change to Widget Sizes
V2.1 - Internal Modifications.
V2.1.1 - Fixed issues with preferences being lost

The widget is based off code from the following two sources -

Modifications were required to get the dock readout to work properly.

http://android-er.blogspot.com/2010/10/home-screen-battery-widget.html

http://www.tutorialforandroid.com/2009/01/getting-battery-information-on-android.html
[Eee Pad Transformer Themes and Apps] rilot:
Seems to work on stock UK 3.1 just fine.
[Eee Pad Transformer Themes and Apps] Mr.Clark:
Awesome!

MoDaCo 3.1 ROM, I had to reboot after installing to get it to show up in the list of widgets, but it's there, it's resizable, it's really bloody useful!

Thanks!
[Eee Pad Transformer Themes and Apps] mb2k:
Great app! Resizeable at that! Makes you wonder why Asus took the feature out of the beta firmware that was released prior to the one that fixed the dock issues.

Thanks much Highland3r
[Eee Pad Transformer Themes and Apps] gniouki:
Using primordial 3.1 and clemsyn-blades kernel it shows "detached" for the dock
[Eee Pad Transformer Themes and Apps] Highland3r:
Open terminal on your tablet and paste the following command:

logcat BatteryService:D *:S

Paste the output (or a few lines of it) back here.
[Eee Pad Transformer Themes and Apps] gniouki:
the command doesn't work

edit : ok I tried again and i get that :
[Eee Pad Transformer Themes and Apps] Highland3r:
Do you get any errors? What's the output when you attempt to run the command?