Database Info

[RECOVERY][MOD][Desire][02-Nov-2011] Clockwork 5.0.2.7.111102

First of all, this is not my work. I only compiled it.
This is the usual ClockworkMod recovery, compiled from the CM7 sources with additions/modifications by j_r0dd. What I've done is only to compile it for the HTC Desire. For details, check out the link to j_r0dd's original thread for the Nexus S.
The credits go to Koush for the recovery itself and to j_r0dd for the modifications.
j_r0dd said:
This is based on the latest CM7 source which I modified for myself. I take no credit for the recovery whatsoever, but I will take all the blame for my mods . We all know this is Koush's hard work. Just some things were driving me crazy personally. First was the confirmation menu. I really got sick of scrolling through all those "No"s just to flash something, so i changed it for me personally and just thought I would share. I also created a proper wipe menu. I got sick of some wipes in the main menu and the rest in the "advanced" menu. I made this more Amon_RA like. See the attached screenshot for my changes. That change has led to a few others by me. flash with fastboot or flash_image. THESE ARE NOT IN ROM MANAGER. Also if you have an issue with this take it up with me NOT Koush.
Click to expand...
Click to collapse
Original Nexus S thread with changelog here.
Download:
recovery-clockwork-5.0.2.7.111102-j_r0dd_mod-bravo.zip
(old) recovery-clockwork-5.0.2.7.111027-j_r0dd_mod-bravo.zip
Change log:
02-Nov-2011 (v5.0.2.7):
Merged 5.0.2.7 sources from CM7 repo again (some bugfixes)
Added option to wipe cache partition and dalvik cache at the same time
27-Oct-2011 (v5.0.2.7):
Merged 5.0.2.7 sources from CM7 repo (support for internal/external sdcard in backup/restore)
07-Oct-2011 (v5.0.2.6):
Rearranged wipe menu to avoid accidental factory wipes
Added "Reboot Bootloader"
Moved SD Card partitioning into a function of its own for both int/ext SD card
Merged 5.0.2.6 sources from CM7 repo
Added a menu choice of ext2/ext3/ext4 when partitioning SD card
25-Sep-2011 (v5.0.2.3):
Updated to j_r0dd's 5.0.2.3 version. Currently no changes made by myself.
17-Jun-2011 (v4.0.0.5):
Moved the "Wipe data/factory reset" to the bottom of the wipe menu to reduce the risk of accidental factory wipes.
19-Jun-2011 (v4.0.0.5):
Added "Reboot bootloader" option in advanced menu.
Added the ext4 modifications kindly supplied by roalex. Needs testing. Please make a proper nandroid backup with a proven working recovery version before trying this.
20-Jun-2011 (v4.0.0.5):
Added "Show log" in the advanced menu. This can help when reporting errors here. Use it.
21-Jun-2011 (v4.0.0.5.z110621):
Reverted and correctly added roalex's ext4 additions.
Modified recovery.fstab for ext4 support on some devices.
23-Jun-2011 (v4.0.0.5.z110623):
Removed NULL ext3 in recovery.fstab to hopefully get ext4 working properly.
06-Jul-2011 (v4.0.0.5.z110706):
Added "Advanced backup". Now you can backup/restore individual partitions.
Some other commits from other devs in github
Changed file limit from 10000 to 50000 in unyaffs. Should help when restoring large data partitions fails.
17-Jul-2011 (v4.0.1.0.110717):
Rebased completely on j_r0dd's 4.0.1.0 source and removed roalex's ext4 additions, as it wasn't working for everyone. Now trying with the original ext4 support which is included in CWM.
20-Jul-2011 (v4.0.1.4.110720):
Bug fixes
Disclaimer
These recoveries are compiled using the latest commits from koush, j_r0dd and others. That means they haven't been thoroughly tested and might have minor/major issues. I take no responsibility for any damages this thing might cause, but most things should work as intended. If you want something guaranteed to work, I think you should stick with one of the older versions.
Source code available here.

it works... thank you

suiller said:
it works... thank you
Click to expand...
Click to collapse
Superb! I'll change the OP to confirmed then.

bit hesitant to flash this, had a few usb bricks from recent clockworks. reckon some people who have flashed it could nandroid backup then restore and check it all works?

sjknight413 said:
bit hesitant to flash this, had a few usb bricks from recent clockworks. reckon some people who have flashed it could nandroid backup then restore and check it all works?
Click to expand...
Click to collapse
Well, like I said, I can't guarantee that it works, especially since I have no Desire to test it on. I've used j_r0dd's source which is based on Koush's source for the official CM7 3.2.0.0 ClockworkMod recovery. It might work, or it might not work. Testing it is up to each person.

zyonee said:
Well, like I said, I can't guarantee that it works, especially since I have no Desire to test it on. I've used j_r0dd's source which is based on Koush's source for the official CM7 3.2.0.0 ClockworkMod recovery. It might work, or it might not work. Testing it is up to each person.
Click to expand...
Click to collapse
dont get me wrong, i didnt mean any disrespect looks like you have done good work! but i have only had my desire 4 days and already had 2 usb bricks! will probably test in a couple of days

sjknight413 said:
dont get me wrong, i didnt mean any disrespect looks like you have done good work! but i have only had my desire 4 days and already had 2 usb bricks! will probably test in a couple of days
Click to expand...
Click to collapse
Don't worry about it, I wasn't offended in any way. I'm wondering though if the USB bricks are caused by flashed (.img) recoveries. As I remember it, USB bricks were common with the earliest attempts to run recoveries by uploading the recovery binary to the phone's RAM while having to keep it plugged in to the computer.

well i know i got the usb bricks whilst restoring nandroids when my phone wasn't plugged in. that help in any way?

sjknight413 said:
well i know i got the usb bricks whilst restoring nandroids when my phone wasn't plugged in. that help in any way?
Click to expand...
Click to collapse
Maybe your misc partition got overwritten with garbage. In my opinion, nandroid shouldn't touch this partition. The USB brick issue is usually caused by a corrupt misc partition.
Sent from my Nexus S using Tapatalk

yeah i dont really know why it does, its easily fixable by reflashing the mtd0.img file generated from your cid and rom version though, its just a massive nuisance!

sjknight413 said:
yeah i dont really know why it does, its easily fixable by reflashing the mtd0.img file generated from your cid and rom version though, its just a massive nuisance!
Click to expand...
Click to collapse
You should check your nandroid backup folder. If there's a misc.img or something like it, maybe you should move that file elsewhere. That way, nandroid shouldn't overwrite your misc (mtd0) partition. I'm only guessing that it does handle that partition.

Is it wiping sd-ext correctly? "Official" 3.2.0.0 posted here some times ago restarted recovery upon sd-ext wipe.

teorouge said:
Is it wiping sd-ext correctly? "Official" 3.2.0.0 posted here some times ago restarted recovery upon sd-ext wipe.
Click to expand...
Click to collapse
No idea, not using sd-ext in any of my phones.

teorouge said:
Is it wiping sd-ext correctly? "Official" 3.2.0.0 posted here some times ago restarted recovery upon sd-ext wipe.
Click to expand...
Click to collapse
I'd like to know this too. Can anyone who's upgraded to this version of 3.2.0.0 let us know their findings?

Jameswgm said:
I'd like to know this too. Can anyone who's upgraded to this version of 3.2.0.0 let us know their findings?
Click to expand...
Click to collapse
It'll probably behave the same way, seeing as this one only changes the menus, I think.

Updated OP to version 4.0.0.0.

Thanks, please see http://forum.xda-developers.com/showpost.php?p=14598355&postcount=357 .
You should mod 3.1.0.1, no later CWM worked ok.

teorouge said:
Thanks, please see http://forum.xda-developers.com/showpost.php?p=14598355&postcount=357 .
You should mod 3.1.0.1, no later CWM worked ok.
Click to expand...
Click to collapse
Yeah, I got that even on my Nexus S.. I'm just cloning & compiling. Got no idea how to downgrade to an earlier version. Limited programming skills.

I fixed the SD card mounting bug. Please re-download 4.0.0.0.
Still buggy. Each time you leave a file list, you'll need to "adb shell umount /sdcard" from your computer. Looking into it.

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.

having fun in recovery... (and messing with Red5)

So, I'm playing with recovery... In particular, I'm working on replacing the stock recovery with CWM Recovery. A good nandroid backup is always the first step to hacking an android device.
I've managed to repack the recovery partition (finally) as unsecure (meaning I can boot into recovery, adb shell into the device, and have root access.) While in here, I'm just noticing something different on the tablet:
It appears that the firmware update from kies has added some odd bloat: the default factory recovery starts by copying several items from a "preload" partition to your /sdcard partition. How nice of Samsung to add even more addition BLOAT to our devices. (I'll be removing that aspect of recovery, I promise.)
Another oddity I'm finding is that, normally with these devices when they are booted normally (and adb is able to connect), the commandline "adb reboot recovery" will reboot the device into recovery mode. That does NOT happen with this tablet (but I'm not sure why.) I have to power down and power back on with the proper volume switch held down.
Okay... time for me to build a copy of CWM Recovery that'll (hopefully) work on this tablet. Wish me luck!
Gary

Thanks in advance! Always glad to hear the interesting finds in a new device.
Sent from my GT-P6210 using Tapatalk

ah, yes... the "new" shared partitions in honeycomb (and ICS.) No longer is there supposed to be dedicated space for /data and /sdcard partitions. They are supposed to use the same space.
Actually, that makes sense. You never have to use something like app2sd, because it's all really the same space. How it gets there, however, is annoying (when trying to reverse engineer a gingerbreak CWM recovery to a honeycomb device.) There is no /sdcard parition on this thing. /sdcard is actually a remap of the /data/media directory. Nice.
My problem is getting CWM Recovery to understand that. pfft.
I wish I could find some source for a CWM recovery partition for another honeycomb tablet. that'd make my life easier, I think.

WARNING: Playing "world of goo" is a major distraction to getting other things accomplished.

have recovery making a nandroid. This would probably be easier if I knew what I was doing. Oh, btw, who wants to test this stuff for me?

garyd9 said:
have recovery making a nandroid. This would probably be easier if I knew what I was doing. Oh, btw, who wants to test this stuff for me?
Click to expand...
Click to collapse
Hey,
I'm also working on it, I'm an dev who ported CWM to the Galaxy Note.
Wait a few hours and you will have CWM

netchip said:
Hey,
I'm also working on it, I'm an dev who ported CWM to the Galaxy Note.
Wait a few hours and you will have CWM
Click to expand...
Click to collapse
I might have just beat you to it. I'll give you a hint, though: honeycomb does some things with partitioning thats very different from previous android versions. CWM tries to take some of that into account, but because of how /data is set up in recovery.fstab, it's not detected that /sdcard should really be /data/media. (I'm rambling.. heh..)
Anyway, pershoot worked this out, so if you pull a specific changeset from his github (https://github.com/pershoot/android...mmit/6dacf061b8476c3e3e2857ca078df95706d62770), and apply it to the CWM in the current cyanogen 7.2, everything should work.
Well, so far everything appears to be working. I've validated the backup works, but haven't verified the restore. I've also modified the code to discourage people from partitioning their sdcards (and it's a bug in CWM that they can choose that option when /sdcard is just a symlink to /data/media)
Anyway, I'll dump the image someplace if anyone wants to mess with it. I honestly have NO idea how to build any kind of package to automate installing it. I've been using "dd" all night long.

On second thought, maybe I'll go to bed... (been awake for over 24 hours)
I'm in the middle of testing the nandroid restores, and there's no way I'll post anything until I'm sure it works. Considering how tired I am, I'll feel better testing this when I'm rested.
One issue I'm REALLY getting annoyed by: For some reason, when I do a "adb reboot recovery", the tablet doesn't reboot into recovery. Even if I'm in a root shell, "reboot recovery" isn't taking me into recovery.
Good night!
Gary

garyd9 said:
On second thought, maybe I'll go to bed... (been awake for over 24 hours)
I'm in the middle of testing the nandroid restores, and there's no way I'll post anything until I'm sure it works. Considering how tired I am, I'll feel better testing this when I'm rested.
One issue I'm REALLY getting annoyed by: For some reason, when I do a "adb reboot recovery", the tablet doesn't reboot into recovery. Even if I'm in a root shell, "reboot recovery" isn't taking me into recovery.
Good night!
Gary
Click to expand...
Click to collapse
I think the kernel is not connected with HC
ICS == almost HC.
There we also don't need the patch

thank you guys so much! great job!

chrisrotolo said:
thank you guys so much! great job!
Click to expand...
Click to collapse
Is on this device the Download mode?
I compile my kernels from source, now I need a tester who don't care about warranty.
I use a module of the SGS2, I've contacted a few people experieced in param.lfs, and they say if the kernel can't mount it it says "logo.jpg not found" and it still boots further.
PM me if you are interested!

posted CWM Recovery.

this is habit forming.
the upcoming version will, in addition to being in a nice update.zip, will also install 'su' so you can root your tab and install recovery all at once.
I am _not_, however, installing the SuperUser application (which is needed as well.) That can easily be done from the market after installing this update file.
All will be documented soon.

I could swore I had an sdcard partition, under it's own or external
Sent from my GT-P6210 using xda premium

For the internal, it's not a real partition. The "/mnt/sdcard" mount is a FUSE link to /data/media. (It's a real parition on the external sdcard if you have one installed.)

I'm working with someone to get copies of the recovery and normal boot kernel partitions from the P6200 (international 3g.) Once I have that, and assuming my blind kernel compiles actually work, we'll have CWM recovery for that tablet as well.
Take care
Gary

I have an international 6200. If you tell me what you need and maybe some help in how to get it, I will dump whatever you want.
Z.

garyd9 said:
I'm working with someone to get copies of the recovery and normal boot kernel partitions from the P6200 (international 3g.) Once I have that, and assuming my blind kernel compiles actually work, we'll have CWM recovery for that tablet as well.
Take care
Gary
Click to expand...
Click to collapse
BTW, have you confirmed that recoveries are incompatible between variants? The 10.1 was "one recovery fits all".

Entropy512 said:
BTW, have you confirmed that recoveries are incompatible between variants? The 10.1 was "one recovery fits all".
Click to expand...
Click to collapse
Currently, they all share the same "recovery" binary (entire /sbin directory, actually), but they need different recovery.fstab files in the initramfs due to different /system (and /data, I think) locations. I'm not at home, so I can't check if it was only 'system' or both.
That one file being different causes them to have a different initramfs, and therefore a different zImage (recovery.img.) I once considered using init.rc to dynamically put a different recovery.fsab into place based on the tablet model at runtime, but how would I be able to determine the tablet model dynamically? default.prop would be useless (as it's also part of the recovery initramfs) and it wouldn't be a good idea for the RECOVERY to rely on the existance of valid data on any other partition. There are ways to take educated guesses based on partition counts and other strange things, but I don't think it's worth the risks.
I do have to admit that I've been having fun messing with this stuff.
Take care
Gary

Ah, that's odd/rare - kind of disappointing.

[Q] CWM unable to mount /system

This has been mentioned elsewhere, even by me but I think it has fallen through the cracks. It may be an unrelated problem but when trying to use CWM to do a backup it fails saying that /system cannot be mounted.
The issue it may be related to is that CWM on boot installed via either method fails to stick past the initial reboot. It looks to me that it is restoring an image on start up each time undoing any changes. It must not be changing everything because the root sticks. I have made sure init.d support has been installed. The phone is an AT&T branded MB865, has been rooted and is running stock 2.3.6 firmware.
Any pointers will be appreciated and I come from an embedded Linux background so I'm willing to help out, but why re-invent the wheel if this has already been solved.

cdlees said:
This has been mentioned elsewhere, even by me but I think it has fallen through the cracks. It may be an unrelated problem but when trying to use CWM to do a backup it fails saying that /system cannot be mounted.
The issue it may be related to is that CWM on boot installed via either method fails to stick past the initial reboot. It looks to me that it is restoring an image on start up each time undoing any changes. It must not be changing everything because the root sticks. I have made sure init.d support has been installed. The phone is an AT&T branded MB865, has been rooted and is running stock 2.3.6 firmware.
Any pointers will be appreciated and I come from an embedded Linux background so I'm willing to help out, but why re-invent the wheel if this has already been solved.
Click to expand...
Click to collapse
Update your busybox .

I had thought of that, running BusyBox 1.20, 1.20.1 fails to install. As 1.20 is fairly recent I doubt this is the problem. The initial install of CWM via Power Boost works, so busybox is installed correctly. An old version of busy box wouldn't explain the not being able to mount /system as as far as I know it isn't used by CWM for this purpose, but I could be wrong. But it could explain the CWM not sticking problem.

Further investigation shows that the system partition does not change between doing a PowerBoost CWM install and after a reboot meaning that there is nothing screwy going on like the boot sequence over writing files in system so that CWM isn't persistent. Can anyone enlighten me on the boot sequence so I can take a look to see if anything is getting over written?
This of course gets me no closer on why CWM can't mount system but it is just one of two problems.

cdlees said:
Further investigation shows that the system partition does not change between doing a PowerBoost CWM install and after a reboot meaning that there is nothing screwy going on like the boot sequence over writing files in system so that CWM isn't persistent. Can anyone enlighten me on the boot sequence so I can take a look to see if anything is getting over written?
This of course gets me no closer on why CWM can't mount system but it is just one of two problems.
Click to expand...
Click to collapse
Have you tried "fix permissions" in cwm?.then reboot and see if it still gives you that error when you go back into cwm
Sent from my MB865 using xda premium

I'm pretty sure I had already tried all that, but just to be sure I did it all again, here is what happened
PowerBoost CWM install
Reboot into CWM
CWM Fix permissions
CWM recovery restart
CWM backup
Failed due to not being able to mount /system
Power cycled, didn't boot into CWM
Since permissions may have changed once CWM Fix permissions had been run
PowerBoost CWM install
Reboot
Enters CWM
Reboot
Didn't boot into CWM
Surely I'm not the only one seeing this problem?

cdlees said:
I'm pretty sure I had already tried all that, but just to be sure I did it all again, here is what happened
PowerBoost CWM install
Reboot into CWM
CWM Fix permissions
CWM recovery restart
CWM backup
Failed due to not being able to mount /system
Power cycled, didn't boot into CWM
Since permissions may have changed once CWM Fix permissions had been run
PowerBoost CWM install
Reboot
Enters CWM
Reboot
Didn't boot into CWM
Surely I'm not the only one seeing this problem?
Click to expand...
Click to collapse
Well once u reboot your phone it goes into cwm. When u reboot from cwm its suppose to go into rom not cwm again.
Sent from my MB865 using xda premium

Have u tried manually mounting system in cwm and see what happens?
Also what version of busybox do u have installed? . Should be 19.4. Nothing higher.
Sent from my MB865 using xda premium

rdavisct said:
Well once u reboot your phone it goes into cwm. When u reboot from cwm its suppose to go into rom not cwm again.
Click to expand...
Click to collapse
I realise this but I was under the impression that if the phone is power cycled or reboot from Android then it will go into CWM on restart.
Still doesn't explain the inability to mount /system

rdavisct said:
Have u tried manually mounting system in cwm and see what happens?
Also what version of busybox do u have installed? . Should be 19.4. Nothing higher.
Click to expand...
Click to collapse
I'm running BusyBox 1.19.4. I just tried to manually mount /system from CWM, same problem. Just to make sure that mounting works I mounted a few other things that were not already mounted.

cdlees said:
I'm running BusyBox 1.19.4. I just tried to manually mount /system from CWM, same problem. Just to make sure that mounting works I mounted a few other things that were not already mounted.
Click to expand...
Click to collapse
Id say rsd flash 2.3.5 . Root. Install atrix bootstrapper. And see if problem persists.
Sent from my MB865 using xda premium

Ok, reflashed back to 2.3.5, rooted, Bootstraped, tried to mount /system from CWM, no luck, same error. Tried to install CWM on boot using the zip from CWM, didn't seem to work. Tried the fix permissions script from CWM, still doesn't work.
There is something up with this phone, is it possible that Motorola has decided to be extra evil.

I till haven't gotten very far with this but I have some more information on what may be the issue. I can get it to update the system partition by flashing a zip. I decided to give it a go with SCV6 as I was sure I'd be able to recover if it failed. It flashed just fine but on reboot it dropped out to the fastboot screen. This is where I decided to get creative, I mounted the system.img file from from the stock fimware, deleted its contents and replaced it with what is in the SCV6 zip system directory, after all this is what CWM will be doing as far as I could tell. I then flashed this file using moto-fastboot. It failed on boot dropping out at fastboot again.
Running out of time for the day I decide to just restore it back to stock, I have a Linux script to automate the process, on completion, same failure. What had happened is I had mounted the system.img file to look inside and then unmounted it, and this may have changed a signature or checksum in the filesystem so it failed to boot. Re-extracting the system.img file and flashing again worked fine.
Are there different versions of the bootloader that do different things? Mine just being a total pain and not allowing much at all.

Just realised the install script puts in a whole pile of symlinks, not having them would cause a boot failure on creating the image the way I did. It will be possible to create an image with said symlinks.
This though fails to explain while mounting and then unmounting the system.img makes it fail.

I may just be talking to myself here but I have some relevant information relating to the original problem of not being able to mount /system which is why flashing doesn't work as well as the flashing scripts don't actually check to see if the system partition is mounted, they just assume it is.
In CWM if you try to mount /system then look at the log it says
mount: mounting /dev/block/mmcblk1p20 on /system failed: Invalid argument
Now the question is, what is the mount line it is trying to execute and which argument is invalid? Can someone with a working phone go into CWM, unmount /system if its mounted by default and then mount it, look at the log and tell me what it says regarding the mounting of system.
Here is the really interesting part, once the phone has booted and checking what is actually mounted on /system its /dev/block/mmcblk1p21, so CWM is trying to mount the wrong partition

I worked out the problem, I was using the Razr bootstrap which obviously mounts a different partition as system, I had followed some instructions that I read somewhere that the Razr version worked and gave a link to said package. Once I swapped to the atrix 2 version it all works, I'll attempt to install SCV6 tomorrow night when I have some time.

can't mount /system!
[/COLOR]
cdlees said:
I till haven't gotten very far with this but I have some more information on what may be the issue. I can get it to update the system partition by flashing a zip. I decided to give it a go with SCV6 as I was sure I'd be able to recover if it failed. It flashed just fine but on reboot it dropped out to the fastboot screen. This is where I decided to get creative, I mounted the system.img file from from the stock fimware, deleted its contents and replaced it with what is in the SCV6 zip system directory, after all this is what CWM will be doing as far as I could tell. I then flashed this file using moto-fastboot. It failed on boot dropping out at fastboot again.
Running out of time for the day I decide to just restore it back to stock, I have a Linux script to automate the process, on completion, same failure. What had happened is I had mounted the system.img file to look inside and then unmounted it, and this may have changed a signature or checksum in the filesystem so it failed to boot. Re-extracting the system.img file and flashing again worked fine.
Are there different versions of the bootloader that do different things? Mine just being a total pain and not allowing much at all.
Click to expand...
Click to collapse
Can you please post the link/s, i have the same problem as you

[Q] Please explain "Installation" per cmenard's ROM

Hi Guys,
I have a Samsung Tab 2 GT-P5113, rooted, and love it. I had to install drives and use Odin to get this ROM installed but it worked and it worked really well. Um, this is the one I used:
http://www.androidauthority.com/galaxy-tab-2-10-1-root-clockworkmod-recovery-cwm-95536/
It is great, I love it, but it is not Jellybean. I have 4.0.4. Now I have ClockworkMod, love it, it really works well. So I downloaded the Milestone zip from here:
http://forum.xda-developers.com/showthread.php?t=1892046
I got the gapps to go with it, and used CWM to install it. CWM works really well, I rebooted to the CWM boot screen and chose the zip file, wiped all caches, and I did pick the make a backup first option and performed the install. The device booted to the little green guy and all the text details appeared. Wiping cache, etc., but when the zip installed, it failed with a Status 7 error, failed to mount /system/ errors such as fonts, device or resource busy, /system/app/ApplicationProvider.apk "Read only file system".
I saved the report log, it is very informative down at the end, last paragraph gives all the juicy details. I should publish this log if I want real help. Let me do it now. Yeah, here ya go:
http://home.comcast.net/~theohmster/text/cwm_fail.txt
Oh, I can attach it! The original CWM recovery.log is attached as a txt file. Duh! :silly:
Look at the last page of the attached log. I understand Linux so I actually know what all these errors mean. Read only files means that the installer does not have root permission. Resource busy means an open file. Can't find /sd-ext in /etc/fstab, now that is a good one, there is no fstab in the /etc/ directory, not even on the phone. But why they are occurring is out of my grasp as I am not a ROM developer and android OS is not Linux, exactly. ...ugh!
Why? I mean, I do not know what to do about this. I tried this several times, first time was a total failure, the MD5 was off by a mile, downloaded it again, got a good copy, could view in Winzip, MD5 matched, but this failure. I did this several times, thank God I had chose the backup first option in CWM and was able to restore the system in short order. The entire process took about ½ hour or less. Am I doing this wrong? I tried to understand cmenard's instructions and I don't quite understand what he is saying to do. The instructions are simple. Here is the URL to the download and instruction page:
http://forum.xda-developers.com/showthread.php?t=1892046
But, it fails by my method, what do these instructions mean in plain English? Flash Rom, what do you mean "flash the Rom"? I got two zip files, gapps and milestone. What is this "Rom" to flash? Wipe I can do in CWM. Flash the zip. You mean install with CWM? Wipe the cache. Again? How? Run CWM again?
Flash Rom in CWM or TWRP
Wipe data/factory reset if you are coming from another ROM
Flash the zip
Wipe cache/dalvik cache
Then flash GApps.
Reboot
So like what am I doing wrong? I really want this Jellybean, especially for my Razr Maxx, but if it will not work on the tablet, I will not mess with my rooted 4.0.4 Razr where I really want JB. The phone was pretty fast 6 months ago, but it seems that all these updates and apps have slowed the thing to a crawl. I use Micro CPU Monitor and love it, two single pixel wide green lines at top screen, one for each core. They are often both pinned all the time so the phone is slow. Use it on the tablet too, same issue but nowhere near as bad on the tablet as it is on the phone. Like who wants to wait 60 seconds every time you touch the screen to make a call or use the maps? Jellybean is said to make things a LOT smoother and really grease the wheels to make ICS really slick and that would help, yes?
I showed the log to a developer on droidxforums, he is really good and made the CD iso files that boot the PC to Linux and rooted the phone. But he really was not sure of the issue and does not have this device.
Somebody help me please. I really want to fix this and am really bummed. Thanks. Happy New Year. :crying:

Okay folks, don't break a leg or anything in your mad dash to render assistance here. It is not worth it, take your time...

OK let me start up my computer and I'm gonna take a look...
Ok...
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /emmc during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
Click to expand...
Click to collapse
AFAIK these are fine.
EDIT: The datadata one is questionable though.. that might be a typo somewhere (maybe... not totally sure. I know there's a /data/data directory, maybe a missing slash? Just thinking out loud here. Whatever it is, I doubt that this is your real problem. That would be the inability to mount /system
Couple questions/things to try.
Firstly, can you remount /system as RW in terminal emulator?
Second, can you install any custom ROMs other than CM10? Try any really, just want to see if the problem is CM10 or your device/CWM setup (Let's hope not the second one)
You do seem to be doing the CM10 install correctly from what I can see.
Oh, and thank you for having the sense to make a backup. Too many people don't and complain about bricking their device and having to ODIN to stock.
Sent from my GT-P3110 using Tapatalk HD

FYI, datadata is a partition symlinked to /data/data, it is only present on some devices like my Fascinate where /data/data is stored on a different memory chip.
Posted from my Fascinate using XDA Premium

[DEV][RECOVERY]CWM Touch 6.0.2.7 for OT-995 [2013-01-09]

Should be working fine but it's thoroughly untested so expect errors at some point.
It's for cyanogenmod installations where /custpack is mounted to /system/app, if there is a request i'll make a version that mounts /custpack to /custpack but for now this is it.
I take no responsibility for what this will do to your phone, it's entirely possible that it will kill your phone and even cause a rift in the space time continuum which will kill us all.
Anyway, here it is, flashable via fastboot as usual, if it goes to stable i'll make an installer for it to install via CWM.
For those not comfortable with flashing via fastboot or who don't have access to a computer at this time, use flash_image via terminal, it should work fine.
Latest version:
cwm_touch_cocktail_6.0.2.7-testing-V2.img
MD5: feb35010a527de42c6c68d6987b939e1
Old versions (kept but not recommended):
cwm_touch_cocktail_6.0.2.7-testing.img
MD5: da314f6eb6429bc3530539d8a0e9e20a

Changelog:
2013-01-09
* Fixed buttons, you can now scroll, select and go back using the buttons.
* Fixed backup, /custpack is now linked to /system/app, this should also make it compatible with older roms. (Remember, this is still testing)
* Added mountpoint for /sd-ext to fix nandroid backups for A2SD/S2E/Links2SD installed apps.
* Fixed some glitches and updated kernel code.
2013-01-08
* initial release

Just flashed it to my mobile and thus far it looks promising. Currently I am not planning to change my rom yet so I haven't confirmed if it is able to flash a rom I only saw it boot.
A little thing I noticed though.
When CWM boots and you are in the main menu the menu fills around 80% of the screen. But when you go to another menu lets say flash something from SDCard it only fills up 50% of the screen and you have to scroll a lot to reach the bottom.
Also the buttons are not working at all?
When you press some of the buttons it starts doing weird stuff..
It seems like the volume buttons and the power button work currectly but the buttons at the bottom of the screen are weird.

Hylix said:
Just flashed it to my mobile and thus far it looks promising. Currently I am not planning to change my rom yet so I haven't confirmed if it is able to flash a rom I only saw it boot.
A little thing I noticed though.
When CWM boots and you are in the main menu the menu fills around 80% of the screen. But when you go to another menu lets say flash something from SDCard it only fills up 50% of the screen and you have to scroll a lot to reach the bottom.
Also the buttons are not working at all?
When you press some of the buttons it starts doing weird stuff..
It seems like the volume buttons and the power button work currectly but the buttons at the bottom of the screen are weird.
Click to expand...
Click to collapse
I had completely forgotten about the bottom buttons TBH, i'll fix that in a future version.
Regarding the screen space, it's not much i can do about that ATM but i'll keep it in mind when and if it gets to stable.

Awesome looking good so far

Really cool. Just point and I'll help test.

Downloading and testing.
With this we can backup and restore CM/PA/PAC roms right?

Mrwargod said:
Downloading and testing.
With this we can backup and restore CM/PA/PAC roms right?
Click to expand...
Click to collapse
If you mount /system/app in mounts and storage it should work just fine.
I'm probably going to write a script and put it in the place of the nandroid/nanddump/nandwrite files so /system/app is mounted before the backup/restore is written.
Just added some stuff to it, partitioning sdcard and support for sd-ext (and swap).
Should work well with an init.d script and s2e for those interested in larger storage for apps.
(simple script to mount /dev/mmcblk1p2 to /sd-ext would work)

tumaini418 said:
Really cool. Just point and I'll help test.
Click to expand...
Click to collapse
Would be great it you have the opportunity.

When i use key test section, its dont back main screen and i need unplug battery.
You did great job thanks a lot...

master' said:
When i use key test section, its dont back main screen and i need unplug battery.
You did great job thanks a lot...
Click to expand...
Click to collapse
You are welcome.

Jinxxed said:
If you mount /system/app in mounts and storage it should work just fine.
I'm probably going to write a script and put it in the place of the nandroid/nanddump/nandwrite files so /system/app is mounted before the backup/restore is written.
Just added some stuff to it, partitioning sdcard and support for sd-ext (and swap).
Should work well with an init.d script and s2e for those interested in larger storage for apps.
(simple script to mount /dev/mmcblk1p2 to /sd-ext would work)
Click to expand...
Click to collapse
Yes, having that automated would be great. If i could backup/restore/install zip's all in one CWM that would be awssome and render it definitivelly daily usable. And way easyer for me to test more roms without the concern in loosing my previous rom.

Mrwargod said:
Yes, having that automated would be great. If i could backup/restore/install zip's all in one CWM that would be awssome and render it definitivelly daily usable. And way easyer for me to test more roms without the concern in loosing my previous rom.
Click to expand...
Click to collapse
Should work fine now, to check if it is, analyze the content of your /sdcard/clockworkmod folder.

Already on it to try the latest version of PAC.
I'll feed you on how it went.
---------- Post added at 11:39 AM ---------- Previous post was at 11:18 AM ----------
The link is dead Jinxxed, or is it still uploading?

Mrwargod said:
Already on it to try the latest version of PAC.
I'll feed you on how it went.
---------- Post added at 11:39 AM ---------- Previous post was at 11:18 AM ----------
The link is dead Jinxxed, or is it still uploading?
Click to expand...
Click to collapse
I mistyped the link. :silly: It's fixed now.
Sorry about that.

Yeah, i had already figured out the correct link anyway.
Thanks, testing!

Wipe battery stats is missing in advanced menu.
Backup / Restore - Not working properly - Some of my apps got lost in restore, namedelly all the gapps, some launchers (holoHD), some file explorers (root file explorer), google account, . . .
Flash zip - ROM flashed ok but gapps didn't flashed, neither did an aditional mod.
But it's really looking really good. And the hardware buttons are fixed.
Keep up the good work.

Mrwargod said:
Wipe battery stats is missing in advanced menu.
Backup / Restore - Not working properly - Some of my apps got lost in restore, namedelly all the gapps, some launchers (holoHD), some file explorers (root file explorer), google account, . . .
Flash zip - ROM flashed ok but gapps didn't flashed, neither did an aditional mod.
But it's really looking really good. And the hardware buttons are fixed.
Keep up the good work.
Click to expand...
Click to collapse
Thank you.
It's a weird result since that means that the backup has problems with both /data and /system/app (i assume since google account and launchers not installed via CWM are stored on /data). It really should be all or nothing, one would think...
There is a problem with mounting /system/app for some reason, that's why gapps isn't installed properly, i'll look into it.
It should be easy enough to fix though, expect a new version within the next couple of days.

Will post the same post here as in Benetnath his PAC rom cause maybe it has something to do with CWM?
-------------------------------------------------------------------------------------------------------------------------------------------------------------
Just ran against a problem with doing the PAC update.
All my gapps seem to be broken and some apps crash on start up.
I had the first PAC rom running and flashed the newest over it while clearing my cache (tried flashing the gapps after this but still didn't fix it)
After this I did a complete reset and flashed it and now it seems to work.
Don't know if its the ROM or if its the new touch CWM which is still in testing..
NOTE: It seems like other people succeeded in flashing the updated rom over the previous rom.
I am not the only one with this problem and it seems like there are other people who have the same problem with the other CWM so ignore this all

trying to flash image in terminal in phone. i keep getting "error scanning partitionsfailed with error: -1
??????????
anyone?
nevermind i went ahead and did it the way i know how.
2nd Edit: just did a backup and restore. Seems to have worked fine.
I couldn't mount usb though.
Great work man. Between you and Benetnath we should be cooking with gas soon.
Thanks jinxxed.