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.
Related
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
after i install a .zip from ClockworkMod it says installation complete.
but it just sits on the HTC screen after a reboot.
the OS never boots. i never get to a boot animation.
just "htc" screen.
ill list my specs.
HSPL 2.08
RADIO: 2.15.50.14
MAGDLR 1.11
i flashed CWM with these settings in flash.cfg
misc ya 1M
recovery ya|ro 5M
boot ya|boot|ro 8M
system ya 120M
cache ya 30M
userdata ya|asize|hr allsize
i am trying to install the Stock MIUI from jan-willem3
and yes ive checked this thread. because this guy had the same problem. i dunno if anything worked for him.
ive tried other zip roms. still to no avail.
and ive tried other radios. other flash.cfg settings in CWM
continueing to use USB FLASHER in MAGDLR is alright.
but most devs are switching to zips. or not offering a MAGDLR USB NAND flash
bumping this since it got buried and no one can help.
did you flash the partition layout?
basically this:
4. boot into magldr and select USB Flasher option while phone is connected to PC
5. Run DAF.exe included in the zip and follow onscreen instructions.
Click to expand...
Click to collapse
by flashing one of those:
Partition Layouts;
-150MB System- http://www.villainrom.co.uk/releases/hd2/Raidroid_HD_HD2_1.1/Recovery_150M.zip
-250MB System- http://www.villainrom.co.uk/releases/hd2/Raidroid_HD_HD2_1.1/Recovery_250M.zip
-400MB System- http://www.villainrom.co.uk/releases/hd2/Raidroid_HD_HD2_1.1/Recovery_400M.zip
the partition layout is nothing more than a line in flash.cfg
and i started with the 250mb layout.
system ya 250M
Click to expand...
Click to collapse
so yah i did that. didnt make a difference.
i need some help guys. quit ignoring this thread.
after 6 full installs of cwm i finally got a zip rom flashed.
now i just hope i wont wanna switch in awhile.
thanks for all the help.
i wont be posting on this website anymore.
seeing as how helpful the community is.
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 "
Dear Friends,
I usually flash ZIP Android using CWM, through menu no.8 in MAGLDR menu. CMW was flashed via USB Flasher menu no.5 in MGLDR menu.
But after several times of failures, I gave up. I hope somebody can inform me what went wrong.
Here is the issue:
After flashing CWM (partition layout) and try to go into recovery mode, the screen says:
"ANDROID LOAD RAW
ERROR: ERROR: Cannot read kernel image"
I tried so many attempts but always like that. I did task 29, reflashing MAGLDR, radio, I even tried to go back to Winmo and back again to reflash HSPL 2.08 and so on. But no luck
I remember that this happen after I tried flashing CWM using SD Card method (via menu no.2 in MAGLDR). If I used this method, I can go into recovery mode. I dont like this method, because I never succeeded flashing ZIP ANdroid using this method. That is why I want to go back to recovery mode via menu no.8 in MAGLDR.
Is the problem related with what i did (flashing CWM via SD Card method)? Is the NAND is damaged?
Is there a way to solve that?
Many thanks in advance
silverwind said:
After flashing CWM (partition layout)
Click to expand...
Click to collapse
what are the contents of flash.cfg? (you can open that file in notepad)
samsamuel said:
what are the contents of flash.cfg? (you can open that file in notepad)
Click to expand...
Click to collapse
Which one? is it the one with CWM partitioner lay out?
This one was flashed when I tried to flash: Ultimate Droid v.3.1.1.v2:
misc ya 1M
recovery rrecov|ro|nospr filesize recovery-raw.img
boot yboot|ro 5M
system ya 150M
cache ya 30M
userdata ya|asize|hr allsize
And this one is the standard one with 150MB lay out:
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
I used either one as per instruction in the relevant thread
hmm, and there is deffinitely a file called recovery-raw.img in the same folder? do you get any error messages on the phone screen when you flash the cwm layout?
samsamuel said:
hmm, and there is deffinitely a file called recovery-raw.img in the same folder? do you get any error messages on the phone screen when you flash the cwm layout?
Click to expand...
Click to collapse
Yes. Never happened before until I flashed cwm using ad method as explained in the following:
http://forum.xda-developers.com/showthread.php?t=987531
once you install CWM you are installing a rom from zip arent you?
if you just install cwm then it wont boot any existing rom, thats what i have found from past experience
Richy99 said:
once you install CWM you are installing a rom from zip arent you?
if you just install cwm then it wont boot any existing rom, thats what i have found from past experience
Click to expand...
Click to collapse
After flashed Recovery via AD SD boot, I flashed the ROM. But it won't boot. So, I decided to reflashed Recovery via USB FLasher (of course I did task 29, flash MAGLDR again).
After that, I went into MAGLDR menu and selected no.8 (AD Recovery). And, it wont boot to Recovery. It says ERROR cannot read kernel image.
My point is that I want to flash ROM via CWM (this CWM was flashed via USB Flasher), but the CWM itself failed to boot (after successful flashing).
I dont have problem boot into CWM if it is flashed via AD BOOT (menu no.2 in MAGLDR) and I cant flash the ROM (though the ROM fails to boot).
Any idea?
ive not used that edited/tweaked cwm, but two things come to mind.
First off, latest magldr required, check? (im not scrolling back to read, so sorry if you already said that)
and secondly, from teh error you are getting, it can only be that somewhere, (possibly when you are restoring from a backup taken when there was no recovery partition?) you are either wiping the recovery partition, or you arent loading back the contents of the recovery partition.
samsamuel said:
ive not used that edited/tweaked cwm, but two things come to mind.
First off, latest magldr required, check? (im not scrolling back to read, so sorry if you already said that)
and secondly, from teh error you are getting, it can only be that somewhere, (possibly when you are restoring from a backup taken when there was no recovery partition?) you are either wiping the recovery partition, or you arent loading back the contents of the recovery partition.
Click to expand...
Click to collapse
Yes Magldr 1.13. I didn't restore any nandroid backup. How can I restore if recovery failed to boot?
It seem this tweaked cwm did/wrote something In the NAND that cannot be erased by task 29 or by flashing stock rom. I stiil can bot recovery through AD boot (menu no.2 in magldr) the tweaked recovery show version 3.0.1.9. Maybe I
should try mtty?
think id concentrate on getting back to winmo stock with an sd card flash, wipe the lot and start over yet again.
As far as I remember, after you flash magdlr 1.13 you need to flash CWM to get the menu point 8 (ad recovery) working. Magdlr 1.13 itself doesn't have the CWM built in, but it supports CWM.
Sent from my HTC HD2 using XDA App
samsamuel said:
think id concentrate on getting back to winmo stock with an sd card flash, wipe the lot and start over yet again.
Click to expand...
Click to collapse
Like I said, I did start it all over again
But, still it didnt help. That is why I am beginning to think that task 29 does not erase all NAND or else there is a damaged/defect in the physical NAND. Should I try use MTTY?
greg17477 said:
As far as I remember, after you flash magdlr 1.13 you need to flash CWM to get the menu point 8 (ad recovery) working. Magdlr 1.13 itself doesn't have the CWM built in, but it supports CWM.
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
Yes I know. There are 3 methods (as I know from XDA ) to boot Recovery Clockword Mode (CWM). Firstly, flashing via USB Flasher (menu no.5) and after flashing, we should select menu no.8 to go into CWM mode (this one is the issue I am talking about), secondly, flashing via AD Boot (menu no.2), it will directly bring you into the CWM menu, and thirdly, using cLK (which I never try it).
I just wanted to try the second method and it works. However, due to the partition lay out issue (as far as I am concerned, the second method doesnt provide flexibility in providing partition lay out. it uses 150MB lay out). So, for the ROM requires different partition layout, I need to flash CWM in accordance with the relevant ROM requirement. This can only be done if we flash CWM via First method. When I flash CWM (for different partition lay out), it seems flashing successful , but when I selected menu no.8 to go into CWM mode it then says: "Error, cannot read kernel image".
Up to now, I can only boot CWM using second method. I just hope the dev of this method can provide a way to flash different partition lay out or did I miss something?
thanks
does this occur with the standard content of raiderx' recovery download, for example the 400m layout...? you can try to edit the "recovery" line inside flash.cfg: remove "filesize" and instead type "6M", so it shows
...
recovery rrecov|ro|nospr 6M recovery-raw.img
...
maybe there are bad blocks on NAND (which is normal, especially after excessive flashing, which is native to us hd2 users due to the mass of roms available for it ) which are causing this.
alternatively you can try to first delete the original "recovery-raw.img" inside the original raiderx recovery folder and then copy the new one; or to use another windows machine (or harddrive in your computer, if exist). maybe there is sth wrong...?
if all you've tried already and other tipps isn't / aren't working, it would be interesting to know if this occurs if you're using cLK; pure testing purpose
i hope you'll get this running... the sd method is no solution in my opinion.
seadersn said:
does this occur with the standard content of raiderx' recovery download, for example the 400m layout...? you can try to edit the "recovery" line inside flash.cfg: remove "filesize" and instead type "6M", so it shows
...
recovery rrecov|ro|nospr 6M recovery-raw.img
...
maybe there are bad blocks on NAND (which is normal, especially after excessive flashing, which is native to us hd2 users due to the mass of roms available for it ) which are causing this.
alternatively you can try to first delete the original "recovery-raw.img" inside the original raiderx recovery folder and then copy the new one; or to use another windows machine (or harddrive in your computer, if exist). maybe there is sth wrong...?
if all you've tried already and other tipps isn't / aren't working, it would be interesting to know if this occurs if you're using cLK; pure testing purpose
i hope you'll get this running... the sd method is no solution in my opinion.
Click to expand...
Click to collapse
Thank Bro, I will try your suggestion and let u know the result.
I also guess there is something wrong with the NAND, maybe the cluster, block, etc. Maybe need to be defragmented (is there any app for doing that?)
I use standar 150MB partion layout from Raider x and also 135MB layout for flashing Typhoon Cyanogenmod.
I still can flash using DAF, but since there is only few ROM for this method, then I would prefer to go through via CWM
thanks again
sure, no problem! one additional question: this really started out since you've used the sdcard files?
cwm is essential and really needed, especially as the most of chefs doesn't provide DAF ROMs anymore. you want to flash typhoon cm7, right? if nothing is working for you, i'll create a daf version for you, so that you at least can use this ROM. just let me know.
seadersn said:
sure, no problem! one additional question: this really started out since you've used the sdcard files?
cwm is essential and really needed, especially as the most of chefs doesn't provide DAF ROMs anymore. you want to flash typhoon cm7, right? if nothing is working for you, i'll create a daf version for you, so that you at least can use this ROM. just let me know.
Click to expand...
Click to collapse
Yes, since I tried the SD card CWM (no offense Bro )
You are right, CWM is app you cant live without it if you are an Android lover
I highly appreciate if you can provide DAF version. I only knows how to convert from ZIP to DAF but not the other way round
Many thanks
k, i will create it todays evening ~ 20:00 gmt+1; but first, pls try to test the other tipps (6M for adding "some spare blocks" and if nothing helps cLK pls).
i'll pm you if i'm ready ok?
i have to do it tomorrow; today i've painted the livingroom of a friend and didn't go home. that's ok? or is there sth new on your side? did you test cLK?
greetings
seadersn said:
i have to do it tomorrow; today i've painted the livingroom of a friend and didn't go home. that's ok? or is there sth new on your side? did you test cLK?
greetings
Click to expand...
Click to collapse
No need to push yourself mate I am patient enough to learn
For installing cLK, I will do it later because I have to learn it since I am not familiar with it (or else if you have or know tutorial for newbie, i would go for it)
I will start with flashing with Recovery with 150MB layout provided by Raider x. Currently I am using Winmo with HSPL 4.
Here is what I will do:
1. Turn of the phone.
2. Go into bootloader mode
3. Task 29
4. Flashing HSPL 2.08
5. Flashing MAGLDR 1.13
6. Flashing CWM 150MB via USB Flasher in MAGLDR menu no.5
7. Boot into Recovery Mode via MGLDR menu no.8
This is the point where i got the problem. If it works, then I can go into Recovery mode to install ZIP ROM , but if fails then it will say Error: cannot read kernel image and it will bring me back to MAGLDR screen.
EDIT:
After flashing MAGLDR 1.13, the phone reboot and I unplugged the usb cable.
It booted and the screen says:
"Booting Android from SD
Android load at 11800000
from Micro SD
Load zimage
k: / zimage
ssSD kernel open failed"
then it brought me to MAGLDR screen menu.
I thought it is normal, isnt it?
then I flash CWM using USB flasher via menu no.5
After flashing CWM complete, the phone reboot and again it showed the above screen and finally went back into MAGLDR screen.
Here is the same old problem. In MAGLDR screen, I selected menu no.8 in order to boot the Recovery mode.
But it failed and the screen says:
"LOAD ANDROID RAW
ERROR: ERROR: cannot read kernel image"
So, it happens again.
Before I continue with the next trial, I wanna hear your opinion about that.
BTW, the winmo before I started this, is ENERGY ROM.
PC I used is WIN XP SP2.
Battery is full, SIM CArd was in but Micro SD was removed.
Do you think I miss something?
Thanks in advance
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.