Database Users

[RECOVERY] ClockworkMod Recovery for Captivate (FINAL! SAFE!)

First things first, if you flashed a previous version of Clockwork Recovery using Odin, FLASH BACK TO A STOCK KERNEL using this Odin package:
http://koush.tandtgaming.com//test/kernel-captivate-stock.tar.md5
This recovery is *very* safe to use. It does NOT flash your kernel; it is a completely uninvasive recovery method.
How it works: The recovery is packaged as an update.zip that you run from STOCK recovery. The update.zip unpacks Clockwork Recovery onto the ramdisk and restarts recovery. When you reboot, it reverts back to the original, unmodified, stock recovery. So, you will need to keep the recovery on the root of your SD card as an update.zip, and apply the zip every time you want to start Clockwork.
HOWEVER, if you use ROM Manager, all of the recovery installation and management instructions are done for you!
Installation instructions:
Download ROM Manager from the Market.
Flash Recovery.
Choose Captivate as your phone.
Accept the Superuser prompt.
Use ROM Manager to create a Backup.
On the very FIRST boot of Clockwork, you may need to manually select "reinstall packages" if Clockwork does not start. You should only ever have to do this once. It will be automatic from then on.
Watch the backup go!
That's it! This is completely painless and safe! There is no need for Odin anymore to replace the recovery or flash updates!
If you appreciate my work, please buy the Premium version of ROM Manager!

Sweet!
Nandroid'd!

Ah yeah....smooth like butter baby!!! Great work once again. Remember to donate people!!!

big99gt said:
Ah yeah....smooth like butter baby!!! Great work once again. Remember to donate people!!!
Click to expand...
Click to collapse
For us Noobs, can we get more information on where and when to use this?
In reading everything I get some of it, but not all. This is my first hackable android phone, so I am still learning the lingo.
With other phones, I would just Flash a custom ROM or Flash Factory ROM back.
So how do ROM Manager and Clockwork recovery come into play?
Are there any tutorials - not that just give step by step (like above) but explain what is happening in each step or why?

alphadog00 said:
For us Noobs, can we get more information on where and when to use this?
In reading everything I get some of it, but not all. This is my first hackable android phone, so I am still learning the lingo.
With other phones, I would just Flash a custom ROM or Flash Factory ROM back.
So how do ROM Manager and Clockwork recovery come into play?
Are there any tutorials - not that just give step by step (like above) but explain what is happening in each step or why?
Click to expand...
Click to collapse
The long and short of it is that you can now flash ROMs and make backups, and restore, without your computer.
The recovery is the tool that lets you do the backups and installations. ROM Manager is a convenient Android front end to the recovery.

After these steps you won't really have to "hack" your phone lol. Root your phone and download Rom Manager from the Android market...then have it flash a recovery (the first selection at the top) choose your device when prompted. Now after that finishes select "reboot into recovery" and as the above post states you may need to select "reinstall packages" (I did). Once that goes through, you'll see your new custom recovery menu. DO A NANDROID BACKUP of your current Rom as soon as you can....then (as long as your current rom isn't messed up, if its stock your fine) from there on out you can play as much as you want with very little risk of bricking your phone. There are others who can explain it better but your stuck with me till they chime in lol. Its a very easy process and nearly foolproof.

Koush said:
That's it! This is completely painless and safe! There is no need for Odin anymore to replace the recovery or flash updates!
If you appreciate my work, please buy the Premium version of ROM Manager!
Click to expand...
Click to collapse
Awesome work! Premium version has been purchased by me. Thank you for the efforts.

Didn't work at first for me.
I installed Rom Manager (premium)
Installed CW recovery
Accepted SU
Tried to backup from within Rom Manager
I got a "Can't find update.zip" message.
When I rebooted and opened Rom Manager again, I got the "Error Occured" message, but it locked up on me and became unresponsive.
I uninstalled Rom Manager, rebooted, then reinstalled. I flashed CW recovery again, rebooted normally, opened rom manager again, and flashed CW recovery again.
After that I was able to use rom manager to reboot into recovery and backup.
Not sure if mine was just a fluke or what, but I figured I would share.

MSigler said:
Didn't work at first for me.
I installed Rom Manager (premium)
Installed CW recovery
Accepted SU
Tried to backup from within Rom Manager
I got a "Can't find update.zip" message.
When I rebooted and opened Rom Manager again, I got the "Error Occured" message, but it locked up on me and became unresponsive.
I uninstalled Rom Manager, rebooted, then reinstalled. I flashed CW recovery again, rebooted normally, opened rom manager again, and flashed CW recovery again.
After that I was able to use rom manager to reboot into recovery and backup.
Not sure if mine was just a fluke or what, but I figured I would share.
Click to expand...
Click to collapse
Titanium Backup did that to me also the first time I ran it....I've had quite a few freezes and slowdowns when opening a program for the first time and waiting for SU to kick in.

It should also be noted that when you chose to partition the sdcard via the recovery menu, it partitions the internal sdcard and not the external.
Maybe that can be made an option? I would like to do my nandroid backup to my external card so I have it for safe keeping.
Everything else working as expected, I enabled advanced options and downloaded the superuser package (from Extras) just to test things. Havent experienced any problems other than the sdcard wipe (which wasnt totally unexpected).
If something should happen to your phone (brick, unrecoverable error, etc), how can we reboot into this custom recovery to reflash the nandroid backup? Can we get into it via adb (adb reboot recovery)?

Yeah, having an external SD Nandroid would be a great option. Not just for safekeeping, but for easy transfer in case of hardware loss or replacement.

dweebs0r said:
It should also be noted that when you chose to partition the sdcard via the recovery menu, it partitions the internal sdcard and not the external.
Maybe that can be made an option? I would like to do my nandroid backup to my external card so I have it for safe keeping.
Everything else working as expected, I enabled advanced options and downloaded the superuser package (from Extras) just to test things. Havent experienced any problems other than the sdcard wipe (which wasnt totally unexpected).
If something should happen to your phone (brick, unrecoverable error, etc), how can we reboot into this custom recovery to reflash the nandroid backup? Can we get into it via adb (adb reboot recovery)?
Click to expand...
Click to collapse
I just did a reboot into recovery mode (the normal way, not with rom manager) and I had to click "reinstall packages" to get into the ClockworkMod recovery menu. So I'm not sure but I'm guessing (hoping) that its still available if we run into problems later.

Yep. It's pretty much how the Droid and N1 people are used to doing it anyway.
Clockwork is hella handy to manage and switch between working ROMs on the fly, as well as triggering recovery mode without keypress acrobatics, but having update.zip on the SD card to fall back on using the normal restore and the stock kernel is great in case of semi-bricking, and as this last week has shown us, the Galaxy phones are a bit prone to this.

THANK YOU!!! Been waiting for this since I got the phone, you are the man, I'll be adding to your Paypal account shortly!

Works like a charm. Thanks Koush!

Thank you. I am new to the scene, but looks like I chose the right hardware for hacking. The swift and easy way in which I have been able to advance my freedom on this gorgeous hardware makes me forget for a while that I am on AT&T, home of the fruit carrying zombie army.

Sweet! Can't wait to try this on my phone later tonight. Will deff be buying ROM Manager Pro

Thanks for this...I just bought the premium version...Since this is my first Android phone I have a question. I previously rooted my phone and uninstalled alll the AT&T bloatware, My question is about the backup I just made using this. If I restore the backup will it restore a rooted backup with out all the AT&T bloatware? Also when I ran the backup I go 2 messages at the end
No /sdcard/.andriod_secure found. Skipping backup of applications on external storage.. Is this normal?
No sd-ext found. Skipping backup of sd-ext. Is this normal?
Also I now have 2 ROM Manager icon in my application screens. 1 will open the program and the other tells me that the aplication is not installed on my phone. I tried to delete that icon but it won't go away, Any ideas? FIXED..I rebooted my phone and the extra icon went away...
Thanks for all help and these great apps...

jhernand1102 said:
Thanks for this...I just bought the premium version...Since this is my first Android phone I have a question. I previously rooted my phone and uninstalled alll the AT&T bloatware, My question is about the backup I just made using this. If I restore the backup will it restore a rooted backup with out all the AT&T bloatware? Also when I ran the backup I go 2 messages at the end
No /sdcard/.andriod_secure found. Skipping backup of applications on external storage.. Is this normal?
No sd-ext found. Skipping backup of sd-ext. Is this normal?
Thanks for all help and these great apps...
Click to expand...
Click to collapse
i got the same message, im assuming that you dont have an external sd card thats why it generated the message...

rabbivj said:
i got the same message, im assuming that you dont have an external sd card thats why it generated the message...
Click to expand...
Click to collapse
I do have one in my phone but there is nothing installed on it yet..maybe that's why..

[A] Bootloop after flashing a ROM via 3.0.0.5 Recovery image.

What you did .. .. ..
Okay so you've rooted your newly bought MyTouch4G, and you've made sure that s=off and you've flashed Clockwork ROM manager's recovery image that you got from the market. That is all the correct order. But when you flashed a ROM you got stuck in a bootloop.
Am i screwed???
Don't worry you are just in a "soft brick mode", or "limp mode" if you will.
What happened? Why is it doing this?
The Image that you downloaded and installed 3.0.0.5 is for 2.3 (Gingerbread) based ROMs only. [n3rd note] these are ext4 style ROMS. They act and store information differently than 2.2 which are Ext3 ROMs[/n3rd note].
This could also be caused by trying to flash a 2.3 using a older 2.x.x.x version of the Recovery Image. Those will only support the Ext3 style ROMs, which are FroYo (2.2) based ROM.
Okay what do i need to do to fix it, there are two methods.
This is Method one it's the older version.
You must use this method if you do not have the engineering screen
If you are using the 3.0.0.5 Recovery image
To fix your problem you need to flash any 2.3 based ROM, for time sake i will recommend Cyanogen(mod). Link to Cyanogen(mod)'s CM7RC4. While you are there you need to also store the G/Apps.
If you are using the 2.x.x.x Recovery Image
To fix your problem you need to flash any 2.2 based ROM, for time sake i will recommend RoyalGlacier Thread can be found here
- Question: How do i find out what Recovery image i am using
- Answer: Boot the phone into the recovery mode. We'll touch on that in a little bit
Now when you download both of those files you also need to store them to SDCard.
NOTE: If you are using 2.x.x.x and going to flash RoyalGlacier you will not need the g/apps. They have included this in their ROM, and MAKE sure to follow their specific directions for installing the ROM.
- Question: Now how in the world i am going to do that since my phone is in bootloop.
Answer:
Two ways one can do that
1) use a SDcard reader and just plug the card into a main USB port.
2) Mount the SDCard in the phone via the Recovery Image. *** i'd recommend this method since you are going to need to be in recovery anyway ***
Pull the battery from the phone an put it back in, then put the back on the phone. turn the phone on holding the power button along with the volume down rocker button. That will boot the phone into the HBoot (Engineering) Screen. From there you will see an option that says "recovery" [this is what i mentioned earlier, about the different versions] use the volume rocker to select it, then tap the power button to select it. The phone will reboot into what is called the recovery image. From there you will select "mount" then USB. That will mount the SDCard to the Computer.
If you are using the 3.0.0.5 Recovery image
Once you have move Cyanogen(mod) and the g/apps to the SD card unmount the SDCard.
Then navigate to "wipe data/factory reset" you will want to wipe the phone. That will format everything to a fashion that can be written over w/o problems.
Then navigate to "install .zip from sdcard" > " choose .zip " > then flash the main Cyanogen(mod) ROM. Then do the same but flash the g/apps that you downloaded.
Once those are done you can re-boot the phone. That will boot you into cyanogen.
If you are using the 2.x.x.x Recovery image
Please use the link i supplied above to get that ROM up and running once it is done, according to their instructions come back here.
Now i understand that may or may not want Cyanogen nor RoyalGlacier on your phone. Well take care of that
What can i do to prevent this from Happening again?
Once you are up and running (make sure to log into your Google Account) go to the market and download Clockwork ROM manager again, and re-flash the recovery image.
Once you are done with that i HIGHLY suggest upgrading to the newest 3.0.0.6 Recovery image. You can do that one of two ways.
one way is to flash True_Blues method for installing 3.0.0.6 recovery image. Use this thread..
This is the way that i would personally recommend.
The second way is download the 3.0.0.6 recovery image, which i've attached and flash it via the ADB commands. If you want to do it this way you do not need to download Clockwork Rom Manager, you can "just flash it". If you need help with that, if you are using Windows or Mac, see my signature for True_Blue's method on EZ ADB. If you are using Unbutu 10.10 use this This Method to get ADB running. This is the method i used to ADB running on my Linux NetBook.
Download the file that i've attached and store just the recovery image from the .zip to the SDCard, from the ADB commands type
adb shell
su
flash_image recovery /sdcard/recovery.img
Click to expand...
Click to collapse
More information on this process can be found here
That will flash the newest recovery image to your phone
Once you have installed the 3.0.0.6 ROM Manager you can wipe and flash ANY MyTouch4G ROM that you want. It will handle both 2.2 (ext3) and 2.3 (ext4) ROM formats.
This is the New Method - Which is a little easier.
AND YOU MUST HAVE THE ENGINEERING HBOOT
Thanks to TeeJay for inspiring this.
I am going to assume that since you have the Engineering Screen you are more familiar with what you are doing so i'll be more to the point with this walk-through.
you will need to have ADB up and running for this method.
1) Download the attached file and store just the .img to your folder from which you preform all of your ADB commands
2) plug the phone into the computer
3) boot the phone into HBoot
4) from the ADB commands change the drive to the folder where you stored the recovery image.
5) type these commands
Code:
fastboot flash recovery recovery.img
the screen should say something to the degree of
Code:
sending 'recovery' (3426 KB)... OKAY [ 1.172s]
writing 'recovery'... OKAY [ 0.797s]
finished. total time: 1.969s
6) then select "bootloader"
7) navigate to "reboot recovery"
8) flash your ROM of choice.
9) enjoy your ROM of choice.
Please feel free to use this in your signature or link people back to. If you feel i made an error in this post please PM and i'll edit it accordingly.
If this thread has helped you solve your problem please hit the "thanks" button.
THE RECOVERY IMAGE HAS BEEN UPDATED TO THE NEWEST ONE.

good summary. originally when i flashed cm7 I had to search a bit to come up with what you said above. one addition, CWM lets you mount sd storage to usb so you can copy files to sdcard (say the recovery image). then update CWM 3.0.0.6 with ADB.

leo221 said:
good summary. originally when i flashed cm7 I had to search a bit to come up with what you said above. one addition, CWM lets you mount sd storage to usb so you can copy files to sdcard (say the recovery image). then update CWM 3.0.0.6 with ADB.
Click to expand...
Click to collapse
Added that method as well.

May want to mention that the opposite could be true as well > same boot loop but from flashing 2.3 rom with recovery 2.5.1.2

Thank you for this!! Exactly what I needed...!

austengeist said:
Thank you for this!! Exactly what I needed...!
Click to expand...
Click to collapse
Glad it helped, just make sure to hit the "Thanks" button in the first post.

dang man you're the Q&A champ, every time i'm on this you're answering questions.
well this worked like a charm, idk why people on xda always make things more complicated than it has to be.

option94 said:
May want to mention that the opposite could be true as well > same boot loop but from flashing 2.3 rom with recovery 2.5.1.2
Click to expand...
Click to collapse
Added.
aalsmadi1 said:
dang man you're the Q&A champ, every time i'm on this you're answering questions.
well this worked like a charm, idk why people on xda always make things more complicated than it has to be.
Click to expand...
Click to collapse
Well i work in the Imported Automotive parts. My job requires me to basically sit around and answer the phone when it rings. We have our own "call center" room. I just pick up the phone and answer question and sell parts. Like right now i'm working on a engine rebuild kit for a 1975 2Ton Mercedes Bens..... so i get some free time from time to time, and XDA is one of a few sites they allow me to visit.... BGR/ Android and Me, Android Central are the others....
I can see why some people blow up, spend +$200.00 on a phone then turn around and blow through something w/o taking the time to read something and then you get stuck in a bootloop.... i can see why people go bonkers. But slowing down and reading would solve alot of problems. Heck i've got 3 great threads in my signature that would solve alot question that one could have with a new device.

fixed my problem

Thread stuck.

Great guide!

Same issue, except i flashed 3.0.0.6 beforehand to prevent any problems. Iced Glacier flashed okay, I just didn't care for it much. Ive wiped all the necessary parts prior to flashing as I would before flashing any roms. Ive managed to retrieve and restore a previous back (I can haz backups) so Im not stuck. I would like to be in the cool kids cyanogen club. Any ideas?

DHSdrone said:
Same issue, except i flashed 3.0.0.6 beforehand to prevent any problems. Iced Glacier flashed okay, I just didn't care for it much. Ive wiped all the necessary parts prior to flashing as I would before flashing any roms. Ive managed to retrieve and restore a previous back (I can haz backups) so Im not stuck. I would like to be in the cool kids cyanogen club. Any ideas?
Click to expand...
Click to collapse
Meaning you want to run Cyanogen(mod)? Well jump over to their site and download the ROM of your picking; Nightlies are alpha builds, and the RC's are beta builds. I've ran both and both are extremely stable. I have links supplied in the first post. and directions for that matter. just make sure to do a nandroid backup before wiping and flashing.

Thanks ....Saved ME LIFE

Posting so I can see the "thanks" button. Doubley thanks you saved my bacon....err phone!! Hmmmm bacon!

Ok I am having one Problem PLEASE HELP!!!
When I click "wipe data/factory reset" it just shows the clockwork icon (hat and arrow) and nothing happens.
In fact, this happens with all of the options in the clockwork recovery.
I am running clockwork 3.0.0.5. I had CM7 and I did something stupid, tried flashing another ROM via rom manager....I did back up everything though.
Please tell me I am not bricked!!!

b0rnsusp3ct said:
Ok I am having one Problem PLEASE HELP!!!
When I click "wipe data/factory reset" it just shows the clockwork icon (hat and arrow) and nothing happens.
In fact, this happens with all of the options in the clockwork recovery.
I am running clockwork 3.0.0.5. I had CM7 and I did something stupid, tried flashing another ROM via rom manager....I did back up everything though.
Please tell me I am not bricked!!!
Click to expand...
Click to collapse
Pull the battery. Hold vol down power on them restore cm7. Then flash cwm 3.0.0.6.
Sent from my Inspire 4G using XDA Premium App

b0rnsusp3ct said:
Ok I am having one Problem PLEASE HELP!!!
When I click "wipe data/factory reset" it just shows the clockwork icon (hat and arrow) and nothing happens.
In fact, this happens with all of the options in the clockwork recovery.
I am running clockwork 3.0.0.5. I had CM7 and I did something stupid, tried flashing another ROM via rom manager....I did back up everything though.
Please tell me I am not bricked!!!
Click to expand...
Click to collapse
What button are you pressing to select the option? you should just use the trackpad.

Loll...wow, I am such a noob i def. shouldn't be rooting or anything.
Thanks so much!

b0rnsusp3ct said:
Loll...wow, I am such a noob i def. shouldn't be rooting or anything.
Thanks so much!
Click to expand...
Click to collapse
Why do you say that?

[Q] AD RECOVERY fails after flashing CWM

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

ClockworkMOD now works with 3E recovery?

EDIT: This is not a result of ROM Manager, this is a result of installing Overstock 1.4.3 which also installs CWM recovery.

Not trying to be rude or anything, but I don't remember this ever not working.

I am having issues with 3e. No matter how carefully I follow the instructions (flash->reboot->reinstall packages always fails) when flashing recovery from current Rom Manager and Premium License, it does not work. Additionally, the premium license is persistent in my applications list and no premium ROMs ever show up in my download list. Even when I select Vibrant MTB and either 2.x or 3.x, all I get is a message that states current recovery will be used. I'm still going thru posts for a possible solution.

Try putting this in the root of your internal SD, reboot to recovery and reinstall packages twice.

Yeah, I was misinformed. This is not a result of ROM Manager, this is a result of installing Overstock 1.4.3 which also installs CWM recovery.
If anyone want to do this it is really simple with the SGS kernel flasher app. Download your overstock kernel of choice from here or your choice of kernel that includes CWM from the dev bible, unzip it, move the zimage to the internal phone memory and then choose that file as your kernel with the SGS Flasher.
Note: I have not been successful with going back to stock kernel when I tried to but that may have been because I didn't disable the lag fix.

jneal9 said:
Try putting this in the root of your internal SD, reboot to recovery and reinstall packages twice.
Click to expand...
Click to collapse
I'm 100% stock on 2.2Froyo except for root/unlock and am puzzled by this. I know it's not ROM Manager because it worked on my first SGS4G which died and totally bricked after a week (TMO exchanged it happily cause it wouldn't even go into download mode or charge).
What's in this update you linked? Cause I'm smart, but not as smart as most of the posters here and I recognize only a couple things in the file.

It installs CWM.
Are you using a Vibrant or SGS4G?

SGS 4G for TMobile.
BTW... I totally appreciate the help here. I don't know the ins-n-outs of the android phones like I do IOs, not that I'm all that up to date on that either.
Update... Still does not work. I get the failed signatures error and the update is aborted. I tried doing a factory reset and re-rooting the phone in case something didn't work correctly and get the same error. At this point, it's all gravy since the only thing I really needed was the unlock but now I'm in a "I just want to know how this works" mode.
Thanks for the help.

Ok yeah that my be the problem since that zip is for the Vibrant. So just to be straight, you are unable to get CWM on your SGS4G?

That's correct. I can't apply any update.zip nor does flashing CWM recovery work. It says it's flashing but then when I do the 3 button reboot to get to recovery, it's the 3e version still and when I go to reinstall packages, it starts but then fails as it tries to verify signatures.

[Q] Custom Recovery & Flashing issues

I'm new to the Moto Droid world coming from Samsung, and trying to learn about it. I've googled and read a lot about all of the topics below, and I'm looking to learn more. Here are some observations/issues that I'd appreciate any insight on - It would also be helpful to know if these are known, open/unresolved issues:
My device is rooted and unlocked, running sys. ver. 183.46.10.xt907.Verizon.en.US, build KDA20.62.10.1. (I think that's stock Verizon). I have CWM ver. 6.0.4.8 installed. When I try a nandroid backup to my external sd card (/storage/sdcard1), boot-image, recovery image, and system complete normally. When it tries to backup data, I get the error "Can't mount /data!". When I look at my external SD card, I see 4 non-empty files (boot.img, recovery.img, system.ext4.tar.a, system.ext4.tar.b) and 1 empty file (system.ext4.tar). Is there anything I can do to get CWM to backup data also? Do I need to resort to backing up with ADB to get everything?
When I reboot from CWM, I get "rom may flash stock recovery on boot - can't be undone" with "no" or "yes - disable recovery flash" as my choices. I think either choice keeps my CWM recovery. I then get "root access possibly lost - fix? with "no" or "yes fix root (/system/xbin/su)". If I select "yes fix root (/system/xbin/su)", it keeps root, and if I select "no", it loses root. Shall I consider these as minor annoyances that I shall forever live with?
I've tried to flash TWRP, and the only version that I've been able to boot up is the latest one, version 2.8.1.0. The problem is that the font is too big, or our screen size is too small for that version. Is there a version of TWRP that works on our device? I tried ver 2.5, and it doesn't boot.
To flash, I boot the phone into AP Fastboot and use mfastboot on my Windows PC.. Flashing seems to work, but I always get the "<bootloader> variable not supported" message at the start. Is this anything to worry about or indicating some other problem?
Thanks in advance for any and all responses.

beeewell said:
I'm new to the Moto Droid world
coming from Samsung, and trying to learn about it. I've googled and read a lot about all of the topics below, and I'm looking to learn more. Here are some observations/issues that I'd appreciate any insight on - It would also be helpful to know if these are known, open/unresolved issues:
My device is rooted and unlocked, running sys. ver. 183.46.10.xt907.Verizon.en.US, build KDA20.62.10.1. (I think that's stock Verizon). I have CWM ver. 6.0.4.8 installed. When I try a nandroid backup to my external sd card (/storage/sdcard1), boot-image, recovery image, and system complete normally. When it tries to backup data, I get the error "Can't mount /data!". When I look at my external SD card, I see 4 non-empty files (boot.img, recovery.img, system.ext4.tar.a, system.ext4.tar.b) and 1 empty file (system.ext4.tar). Is there anything I can do to get CWM to backup data also? Do I need to resort to backing up with ADB to get everything?
When I reboot from CWM, I get "rom may flash stock recovery on boot - can't be undone" with "no" or "yes - disable recovery flash" as my choices. I think either choice keeps my CWM recovery. I then get "root access possibly lost - fix? with "no" or "yes fix root (/system/xbin/su)". If I select "yes fix root (/system/xbin/su)", it keeps root, and if I select "no", it loses root. Shall I consider these as minor annoyances that I shall forever live with?
I've tried to flash TWRP, and the only version that I've been able to boot up is the latest one, version 2.8.1.0. The problem is that the font is too big, or our screen size is too small for that version. Is there a version of TWRP that works on our device? I tried ver 2.5, and it doesn't boot.
To flash, I boot the phone into AP Fastboot and use mfastboot on my Windows PC.. Flashing seems to work, but I always get the "<bootloader> variable not supported" message at the start. Is this anything to worry about or indicating some other problem?
Thanks in advance for any and all responses.
Click to expand...
Click to collapse
You're using the wrong TWRP. Use TWRP281KK.img > http://d-h.st/511
All the info you need is here > http://forum.xda-developers.com/dro...oot-unlock-t2869432/post55282645#post55282645

Thank You !!
ATTACK said:
You're using the wrong TWRP. Use TWRP281KK.img > http://d-h.st/511
All the info you need is here > http://forum.xda-developers.com/dro...oot-unlock-t2869432/post55282645#post55282645
Click to expand...
Click to collapse
Thank you so much for your reply, and for pointing me to the correct TWRP for my device. It worked like a charm !! :good: