Database Users

[Q] Can't install a .zip rom from clockwork recovery... what am I doing wrong?

I searched for quite a while, and never found any ideas on how to fix this issue.
I followed the youtube video and got the clockwork mod installed correctly. However, anytime I try to install a rom via recovery, it shows that it's installed successfully... but after rebooting, my device freezes on the boot screen (after magdlr displays GO GO GO.)
I've tried 2 different roms, both MDJ builds, and they both do the same thing. I made sure to wait 15 minutes when booting for the first time, thinking it may be slow on first boot... but it never booted. Does anyone know the partition size to use for MDJ's roms? I thought this might be part of the problem, but I'm open to any ideas and suggestions.
In the meantime, I'll just install via Magdlr... but I would really love to have Clockwork mod working. So, any help with this is greatly appreciated.

Make sure you have HSPL 2.08.
Make sure your Radio is at least 2.10.50 and above.

Done and done.

Then you need to Partition the NANDFLASH.
flash.cfg
Code:
misc ya 1M
recovery ya|ro 5M
boot ya|boot|ro 5M
system ya 150M
cache ya 10M
userdata ya|asize|hr allsize
I use the above for MDJ Gingerbread, but now, I am thinking of allocating 350M to system partition instead of 150M which is too small to play with other ROMs.
Finally, after you repartition, boot into Clockwork Recovery on your SD Card, then install ZIP.
After you are done, turn off your device and remove the SD Card. Turn on the device and see if it works.
Clockwork cannot partition your NANDFLASH, which is why you need to use DAF.exe and flash.cfg file to partition the NAND.

gilla409 said:
I searched for quite a while, and never found any ideas on how to fix this issue.
I followed the youtube video and got the clockwork mod installed correctly. However, anytime I try to install a rom via recovery, it shows that it's installed successfully... but after rebooting, my device freezes on the boot screen (after magdlr displays GO GO GO.)
I've tried 2 different roms, both MDJ builds, and they both do the same thing. I made sure to wait 15 minutes when booting for the first time, thinking it may be slow on first boot... but it never booted. Does anyone know the partition size to use for MDJ's roms? I thought this might be part of the problem, but I'm open to any ideas and suggestions.
In the meantime, I'll just install via Magdlr... but I would really love to have Clockwork mod working. So, any help with this is greatly appreciated.
Click to expand...
Click to collapse
I have the same problem

What is the brand, size and class rating for your MicroSDHC card?
Have you tried doing a low level format on the card yet?
It is not that hard to choose a partition size for system.
Look at the size of the system.img, then allocate that size. So say system image file is 237MB, you just allocate 250MB.
350MB seems to cover most of the DesireHD stock CW rom.
250MB covers most other custom CW rom
150MB covers MDJ's Gingerbread 2.3

[Q] Flashing Clockworkmod on MAGLDR 1.13

Hi All,
I've been looking for an answer and have not found one yet.
I have an existing NAND build (MDJ cyanogen 7) of android that I flashed via magldr 1.11. I know I can update magldr to 1.13 safely without messing deleting the the nand rom i have already. But if I want to install Clockworkmod 1.3 onto the nand will I lose my existing rom need to reflash my rom again or does magldr know to flash clockworkmod onto another area of nand that wont overwrite my existing rom?
also with clockworkmod it says:
Download recovery with partition size for the type of rom you plan on using, see guide below if unsure.
it says to use the 150MB partition just wanted to see if anyone else using mdj's cyanogen 7 is using the same thing?
Your help is greatly appreciated

ascrackoo1 said:
Hi All,
I've been looking for an answer and have not found one yet.
I have an existing NAND build (MDJ cyanogen 7) of android that I flashed via magldr 1.11. I know I can update magldr to 1.13 safely without messing deleting the the nand rom i have already. But if I want to install Clockworkmod 1.3 onto the nand will I lose my existing rom need to reflash my rom again or does magldr know to flash clockworkmod onto another area of nand that wont overwrite my existing rom?
also with clockworkmod it says:
Download recovery with partition size for the type of rom you plan on using, see guide below if unsure.
it says to use the 150MB partition just wanted to see if anyone else using mdj's cyanogen 7 is using the same thing?
Your help is greatly appreciated
Click to expand...
Click to collapse
Yes you will lose your current rom, so do a cwm backup first. After flashing the partition for cwm, you will get a kernel error on first boot, so boot into AD Recovery and restore the boot, system and data backups and all is back to normal. As for the partition size, use the same size as you did for the sd version. The guide suggests a 400mb partition for an unsquashed desire hd build, but I used the 250mb partition on my current rom and all is perfect.
PS! Please don't post questions in the ROM Dev section, there's a reason why there is a Q&A section.

ClydeB1 said:
PS! Please don't post questions in the ROM Dev section, there's a reason why there is a Q&A section.
Click to expand...
Click to collapse
+1
Its so frustrating, why on earth would anybody post a question topic in here when we have dedicated Q&A forum??
It should be obvious to anybody that this is a "dev" forum for posting developments not for asking questions.

Since the rom was originally flashed via DAF, will CWM still allow me to do a backup?
Was hoping for a guide, it's so confusing.

No, from what I understand you don't have CWM installed yet, so you can't use it now. Use titanium backup (market), and then flash cwm so you can use it in the future.

ascrackoo1 said:
Since the rom was originally flashed via DAF, will CWM still allow me to do a backup?
Was hoping for a guide, it's so confusing.
Click to expand...
Click to collapse
It seems confusing at first but it is not really that difficult.
StephanV said:
No, from what I understand you don't have CWM installed yet, so you can't use it now. Use titanium backup (market), and then flash cwm so you can use it in the future.
Click to expand...
Click to collapse
Correct, on first flash of cwm it will erase all data/roms etc on NAND. You will not be able to backup the rom if it was initially flashed via daf. As StephanV says, use Titanium Backup or MyBackup Root to back up your data/apps etc and you can restore them after.
Once you have cwm installed and have flashed a new rom and set it all up, then you can do a cwm backup.

So if i use cwm then I can only flash zip based roms from that point on? I cant use the daf ones anymore then.

You can still use daf, but each time you run a daf file it will remove the cwm recovery partition and you will need to reflash it to use cwm again.

I'm finding that if i flash cwm ontop of a daf rom the rom becomes unbootable. and the only way to get it to work again is use a cwm version of the rom.

ascrackoo1 said:
So if i use cwm then I can only flash zip based roms from that point on? I cant use the daf ones anymore then.
Click to expand...
Click to collapse
i'm not sure about the rom you are using but i was able to back up a few different roms with cwm which i installed using daf. this is what i did:
1. create a folder on sdcard name "cwm" (you can name it whatever you want). i actually have a folder for each clockwork recovery version.
2. put the zImage and initrd.gz for cwm (version 1.0,1.1,or 1.2) in the folder you just created. (do not flash anything at this point)
3. boot into magldr and go to services, boot settings, ad sd dir and select the directory you just created
4. now in magldr menu boot ad sd, and you should hopefully boot into clockwork
5. go to backup and restore and backup your rom. if you try cwm 1.2 and it doesn't work try 1.0 to back it up, you can then update to 1.2 again and it will still restore just fine.
6. before restoring your rom, install cwm1.3 and choose a partition size bigger than the size of the system.img of the rom that you backed up. clockwork backs up your rom in your sdcard->clockworkmod->backup. it creates a folder with the timestamp.
7. now you can follow the steps from the clockworkmod thread to load cwm1.3 and restore from there.

ClydeB1 said:
You can still use daf, but each time you run a daf file it will remove the cwm recovery partition and you will need to reflash it to use cwm again.
Click to expand...
Click to collapse
ascrackoo1 said:
I'm finding that if i flash cwm ontop of a daf rom the rom becomes unbootable. and the only way to get it to work again is use a cwm version of the rom.
Click to expand...
Click to collapse
dont bother 'installing' clockwork, just put the two files on your sd card, then go into your MDJcyanogen rom folder on the PC, open (in notepad) flash.cfg and it will look something like
boot ya|boot|ro filesize+1M boot.img
misc ya 1M
recovery ya|ro 3M
cache ya 3M
system ya filesize system.img
userdata ya|asize|hr allsize
the partitions 'recovery' and 'misc' will allow cwm to work, they arent needed for this rom, they are only there for compatibility however if you plan on flashing to a different rom using sd card/cwm, (rather than simply using cwm to do backups of MDJcyanogen) you will want to edit the
system ya filesize system.img
and maybe set it to one of teh recommended cwm sizes, example
system ya 150M
this is because the original line
system ya filesize system.img
will set a system partition of the same size as the MDJcyanogen system.img, (about 130meg) but if your next rom has a bigger system.img, when you try load it from cwm it wont fit, so wont work. by setting it to 150 (or whatever you want) you are allowing for different size system.img in various roms.
Whenever you flash a nand rom, so long as you edit the flash.cfg and make sure those two partitions, misc and recovery (and maybe cache too, i do) are there, then cwm will work.

how do u get 1.13

sbgleeko said:
how do u get 1.13
Click to expand...
Click to collapse
Go to nand development and its in the thread called (quite cunningly) "magldr 1.13 released "

[TUT] Flash a DAF rom and apply CWM at the same time.

Combining a DAF rom with CWM
This assumes you have magldr 1.13. if you have an older version, backup your rom data, and flash magldr 1.13 first.
A few times there have been posts asking about applying clockworkmod whilst keeping using a DAF rom.
Here's how.
Image 1 - Top left DAF rom folder contents, top right CWM folder contents, bottom middle, combined contents to a new folder.
Copy only system.img and boot.img from the DAF rom folder, and ALL files from the CWM folder, combine into a new folder as per image 1.
In the new combined folder, find flash.cfg, open it in notepad.
(open notepad and drag the file into the empty window)
Edit the boot and system lines to include the filename, and adjust the size of the system line so that it is bigger than system.img
Image 2 - Top left DAF flash.cfg, top right CWM flash.cfg, bottom middle, combined flash.cfg which started out as the CWM flash.cfg and now references the two extra .img files, system.img and boot.img, plus the size of the system partition has been adjusted to allow system.img to fit.
Save flash.cfg
Boot phone into magldr, USB flashing, run DAF.exe just like normal.
Hey presto, CWM is applied and the DAF rom is installed all in one go.
If you did a backup first using titanium, for example, you should now be able to restore your apps and data without issue, and you should also now be able to boot into CWM from magldr by choosing 8 - AD recovery, and you can now use teh CWM backup and restore feature, plus flash CWM roms.
Note that the 300meg system partition used in this example is just that, and example, simply because i used the original DFT release to test this TUT. You could just as easily use 260meg. So long as it is bigger than the system.img by a meg or two it should be fine.
If you want to change to a smaller rom (or bigger) you would need to flash normal cwm again (not this combined one) using a smaller(bigger) partition layout.
Note that flashing a small rom into a big system partition (example a 130meg cm7 rom into this 300meg system partition) will NOT cause any problems, you would just waste 170meg.

Nice work Sam, the screen shots made it really easy to understand also. I will be the first to hit the thanks button, even though I prefer to use CWM to flash my Adroid ROMs and not DAF.
Now if yo could figure out how to flash cLK and CWM at the sametime that would be awesome.

Thanks,
T-Macgnolia said:
I prefer to use CWM to flash my Adroid ROMs and not DAF.
Click to expand...
Click to collapse
yea, me too, and it does have limited uses, but having seen three or four posts asking how they could (for example) use the cwm backup/restore with a DAF rom, i figured id write it up.
As for cLK, i still havent managed to flash cLK on its own! let alone with anything else, hehe. (my fault, im sure, im not blaming anything else, , user error, for sure)

samsamuel said:
Thanks,
yea, me too, and it does have limited uses, but having seen three or four posts asking how they could (for example) use the cwm backup/restore with a DAF rom, i figured id write it up.
As for cLK, i still havent managed to flash cLK on its own! let alone with anything else, hehe. (my fault, im sure, im not blaming anything else, , user error, for sure)
Click to expand...
Click to collapse
Oh yeah it is a reason why ROM chefs right for "experienced user" above the cLK instructions I am whale to get cLK flashed and get CWM flashed but still have not got a ROM flashed using it as I did not have a cLK compatible ROM at that point. So I Task 29ed and flash MAGLDR and then CWM then Hyperdroid back to my HD2. I downloaded the cLK compatible ROM night before last but before I could reflash CLK and CWM I accidently busted the LCD screen on my laptop
As soon as AI actually get a ROM flashed using CLK and CWM I will add it to my guide.

You beat me to the punch with this one
Nice TUT man, haven't tried it but I've been curious for a while if this could work. Will try!

send partition data failed
I did exactly what was said! I flash CMW recovery, did a SD ext partition, and did what you mentioned.. However as i reach: "Flashing 2 Partition....2 {23E-266} M1" i get the following error:
Error Description: send partition data failed
Info: .\RSPL\RSPL.cpp (815)
Error Description:
Info: .\RSPL\RSPL.cpp (558)
My flash.cfg is :
misc ya 1M
recovery rrecov|ro|nospr filesize recovery-raw.img
boot yboot|ro 5M boot.img
system ya 400M system.img
cache ya 4M
userdata ya|asize|hr allsize
what should i do? Please help asap!
I tried again! I was able to flash the ROM! the phone booted but it gave me directly that my internal memory is almost full notification and many process unexpectedly closed errors! i turned off the phone rebooted but its now stuck on HTC splash screen repeating over and over again without booting into android! Please help!

This is an outdated tutorial. You should pick the rom you want, put it on the SD card, then into magldr, USB flasher, run the "android toolkit" and use it to set whatever partition size you require, reboot,into magldr, option 8 ad recovery, that starts cwm, then choose instal zip from SD - choose zip. Done.

[Q] Can i repair cwm recovery?

Hello,
Ive magldr cwm recovery installed, and a magldr NAND rom.
Yesterday i tried to play with rom manager.
I didnt know it only work with clk, and i made the mistake to update recovery throug rom manager.
So it broke my MAGLDR cwm recovery :-(
My question is : can i repair my MAGLDR cwm recovery without wiping my rom?(because i didnt recently do a nandroid backup)
Thx for your help.

Unfortunately, no you can't.
The only way to fix your cwm is to re install cwm. And that will wipe off your rom, data and everything else.
Edit:
wow, i never knew about that !

denseye said:
Hello,
Ive magldr cwm recovery installed, and a magldr NAND rom.
Yesterday i tried to play with rom manager.
I didnt know it only work with clk, and i made the mistake to update recovery throug rom manager.
So it broke my MAGLDR cwm recovery :-(
My question is : can i repair my MAGLDR cwm recovery without wiping my rom?(because i didnt recently do a nandroid backup)
Thx for your help.
Click to expand...
Click to collapse
I think you can do it.
If your phone still don't boot, reflash your Rom without wipe maybe can help
Sent from my GT-I9100 using xda premium

get a version of cwm that loads from sd card,
put it on your sd
from magldr choose 'ad sd'
flash a new cwm.zip using 'instal zip from sd' option.

samsamuel said:
get a version of cwm that loads from sd card,
Click to expand...
Click to collapse
where can I find one ???
samsamuel said:
put it on your sd
from magldr choose 'ad sd'
flash a new cwm.zip using 'instal zip from sd' option.
Click to expand...
Click to collapse
won't it wipe my rom data ???

We are just writing an image to the already created recovery partition,, not using daf to write a partition layout. It's just like flashing a rom, but only the recovery partition is affected.
In the android nand section, titled something like "clockworkrecovery, nand,SD, ver 5.0.2 yes/no stable" or something, (currently top post
Get both
recovery_5.0.2.6_leo_sd.zip (3.93 MB, 1153 views)
and
recovery_5.0.2.6_leo_CWR.zip (4.25 MB, 3415 views)
Extract and copy the SD card ver onto SD card (copy the two files to SD, done)
And then copy the whole cwr.zip to SD card too.
Then, into magldr, "ad SD" will boot into the cwm files you placed on SD, and choose instal zip from SD,,, choose zip,, and select the cwm.zip you also placed on SD.
This will write the cwm image into the recovery partition without reflashing the cwm partition layout, so nothing lost.

it worked
thank you for your help and your very precise explanations

welcome. Its worth leaving those two files on the SD in case recovery fails for whatever reason, since you can backup and restore just like in nand cwm recovery.

samsamuel said:
welcome. Its worth leaving those two files on the SD in case recovery fails for whatever reason, since you can backup and restore just like in nand cwm recovery.
Click to expand...
Click to collapse
yes indeed
I will keep those to files on my sdcard

Many thanks to samsamuel !
i could not get into the CWM menu, but with your help i was able to flash to a new custom rom.

In attempting this, I get the following error:
Writing recovery partition...
assert failed: write_raw_image("/tmp/recovery.img", "recovery")
E:Error in /sdcard/recovery_5.0.2.6_leo_CWR.zip
(Status 7)
Installation aborted.
Any help?

Perhaps the recovery partition is too small? Perhaps you don't have a recovery partition? Check the flash.cfg you last used for partition sizes you used.
Alternatively, use the SD cwm to make a backup and do a fresh flash.

samsamuel said:
Perhaps the recovery partition is too small? Perhaps you don't have a recovery partition? Check the flash.cfg you last used for partition sizes you used.
Alternatively, use the SD cwm to make a backup and do a fresh flash.
Click to expand...
Click to collapse
I have the same error as the person above you. Do you recommend using the SD cwm to flash Recovery_150M_system_44M_cache[v3.0.2.4].zip? I cannot recall what flash.cfg I used.
I think I may have no recovery partition if I recall correctly. I digged through my old files I think this was the flash.cfg I usd:
misc ya 1M
recovery rrecov|ro|nospr filesize recovery-raw.img
boot yboot|ro 5M
system ya 150M
cache ya 44M
userdata ya|asize|hr allsize
Click to expand...
Click to collapse

I had the same error. I made a copy of the recovery_5.0.2.6_leo_CWR.zip and copied my original CWMRecovery's recovery-raw.img on top of the new zip's recovery_leo.img file. That got me past the error and AD recovery works now.

Thanks for that just fixing mine as well now

does not work for me, boot AD SD = ssSD Kernel open failed, no idea.
But manage to reinstall the recovery without wipe with Windows version software - HD2 Toolkit, connect USB cable to PC, while phone staying in Andriod, run Toolkit > MAGLDR update recovery > click "update" and done.

gl7 said:
does not work for me, boot AD SD = ssSD Kernel open failed, no idea.
But manage to reinstall the recovery without wipe with Windows version software - HD2 Toolkit, connect USB cable to PC, while phone staying in Andriod, run Toolkit > MAGLDR update recovery > click "update" and done.
Click to expand...
Click to collapse
Same problem here??? Why?

I have the same problem. Add sd dir does not work. I only get back in the menu.
Using the toolkit and update the recovery shows this fault.
Look attachment.
I want to flash the new ics nexus rom without loosing data. Normal i would flash in ad recovery and make a update. Poorly i tried this Tom manager and now my recovery is broken.
Anyone can help? Sry for my german-english.

Wow, I didn't know that

Your radio links are blank
samsamuel said:
get a version of cwm that loads from sd card,
put it on your sd
from magldr choose 'ad sd'
flash a new cwm.zip using 'instal zip from sd' option.
Click to expand...
Click to collapse
Kindly check on the status of your radio links as the seem to lead to a dead end.

Doesn't reboot into recovery

I installed ROM manager, then tried to back up my HD. It requested I install clockworkmod, but the installation hung. The second attempt was successful, but I cannot reboot into recovery mode. It just reboots normally. If I power on holding the power button it goes into the MAGLDR menu. If I select AD Recover it says:
ANDROID LOAD RAW
ERROR: ERROR: Cannot read ramdisk image
How can I get clockworkmod working without wiping my device?
Thanks

You corrupted the recovery partition by using rom manager,, it doesn't work with magldr.
Find the clockwork thread with "yes/no " in the title, from there get both the SD version and the cwm version ,,put the cwm.zip onto the SD, and also unzip the SD version to the root of SD, then into magldr, "boot ad SD" to start the SD version of cwm then use that to "flash zip from SD"(just like a normal flash) and select the cwm.zip. this will reflash the ad recovery nand partition without affecting the rom

samsamuel said:
You corrupted the recovery partition by using rom manager,, it doesn't work with magldr.
Find the clockwork thread with "yes/no " in the title, from there get both the SD version and the cwm version ,,put the cwm.zip onto the SD, and also unzip the SD version to the root of SD, then into magldr, "boot ad SD" to start the SD version of cwm then use that to "flash zip from SD"(just like a normal flash) and select the cwm.zip. this will reflash the ad recovery nand partition without affecting the rom
Click to expand...
Click to collapse
Thanks, I understand. Is it not worth installing ROM manager at al then if I'm running magldr?
I originally installed/paritioned using the DAF.exe version of CLK 150MB 44MB cache. The ROM only requires 150MB 2MB cache. Am I loosing out on space with this size cache. Partitioning using HD2 Toolkit doesn't work on my device. magldr or clk doesn't boot properly afterwards.
Thanks

The cache is only used by cwm, so yea, 44 is way plenty. I normally give it 5.

samsamuel said:
The cache is only used by cwm, so yea, 44 is way plenty. I normally give it 5.
Click to expand...
Click to collapse
Just found out I can change flash.cfg for DAF.exe. That helps a lot! All working and backed up now. So I'll go for a repartition. The helps greatly appreciated!