yashsingh1/xdaforums huggingface dataset:
[Samsung Captivate Glide] terinfire:
You shouldn't have any problems. Are you sure you downloaded and tried to use the right one? I have tested it, for sure, and it worked great on an I927R (mine, Rogers/International variant) and a I927 (girlfriend's/AT&T variant).

You'll get that error if your partition size is too small for recovery -- our recoveries *are* limited -- to about 5,200,000 bytes -- this is just under that and should work fine. You should not be screwing around with it.

Ensure you are using the recovery.tar.gz I included. Then attempt to do it again -- I have a feeling you may have flashed Aquethys' again.

And just noticed -- the recovery you used is larger than mine -- mine is 5,02x,xxx length in bytes -- so yours is not mine, since it went to 5,213,xxx.

Well, I think I know how to do that -- but it's a little more risky. Involves manually using commands to write to the partition -- which is less stable/ideal than Odin. I was talking to some folks (when my cable was bad) and they said we could do that method as a LAST OPTION. They didn't seem to be too happy of the thought -- but it is something I could potentially research. It may have just been because I was potentially sacrificing my phone, when I didn't know for sure if it was correct/good. :D
[Samsung Captivate Glide] VinayS:
Works well with i927 (AT&T) Version..
[Samsung Captivate Glide] terinfire:
So, after playing around with this some more, this morning, I've discovered that the most important part -- being able to backup/restore -- is not working. Not sure if it is because it may be from an unstable branch of CM10 trying to integrate the newer Jellybean or what -- but I intend on fixing it and finding out what the problem is.

I didn't worry about testing the backup/restore, since I have no data/etc -- but I did test whether or not we could flash from internal or external SD cards, which does 100% work.

So, just a word of warning (I've included it in the topic) to be careful if you flash -- you may not be able to recover/backup as you would like to. I'll try to get this working within a week.
[Samsung Captivate Glide] VinayS:
Will be recovery type be Blob type ?
[Samsung Captivate Glide] terinfire:
If it is CWM6, it will be. I may be able to see if there's a flag or two I can set to change it away from blob -- I know people seem to not like that.
[Samsung Captivate Glide] thegreatergood:
thanks a million this will make development so much easier .. and it can even mount the external :D
[Samsung Captivate Glide] dbrannon79:
my apologies! after going back and looking at my download folder, realizing it's time to clean!! I reflashed your recovery and works!

Thanks,

I would like to see the recovery without the blobs that way single backups can be made and archived! also I do enjoy the "touch" version if there is a possibility putting all that together!

Thanks again and have a blessed thanksgiving!
[Samsung Captivate Glide] Aquethys:
I'll put the touch recovery back up. And...

I'm going to try to build TWRP in the next couple of weeks. Terinfire, you interested in helping me? (:
[Samsung Captivate Glide] elban:
TWRP! Wonderful! Million Thanks! :)

TWRP and physical keyboard is a great combo because you have a comfortable shell in recovery mode ;)
[Samsung Captivate Glide] Aquethys:
Terin did you build in Ubuntu? ;/

I might have to cm sync again.. Takes forever xD like 2 hrs
[Samsung Captivate Glide] terinfire:
Yeah, I setup a VM. Thankfully, my laptop is a monster so I have it virtualizing 8 cores without an issue. Don't ask the specifics, but to give you an idea -- it has two full-sized 5870's in it -- it's a monster.

Yeah, I have it working on Ubuntu. I'll see what I can do to help you out -- I can potentially build it if you help me find all of the details I need. I have a MUCH better understanding about how the entire systems work entirely, now.

So TWRP or whatever it is -- sure, I can see about helping you out with it. I'll probably finally need to get a github account or something, haha. Or get added to an existing TeamGlide one or something, hah.

Has anyone else tried to do a backup/restore with this? It didn't work for me -- but I'm curious if it worked for anyone else and maybe my SDCard's are formatted poorly?
[Samsung Captivate Glide] dbrannon79:
I attempted to test the backup and restore! I found a setting for backup options, set it from "dump" to "tar" backed up to external sd. went well...

attempted to restore and got an error message "md5 mismatch"

opened the folder on my pc and saw where it made 2 .img files one boot and the other recovery. and a "system.ext4.tar" and "system.ext4.tar.a"

tried to open both if the archive files and both gave errors with archive manager in ubuntu, could not open! havn't tried the "dump" style backup yet!

Thanks.
[Samsung Captivate Glide] Aquethys:
terin,

Here's a permanent link for the touch recovery:

http://aquethys.cu.cc/Glide/recovery.tar.md5

Might want to add it to OP?
[Samsung Captivate Glide] terinfire:
Aquethys -- done.

dbrannon79 -- Thanks for giving it a try and confirming. I have the same issues, regardless of dump-type on mine as well.

I'm wondering if it has something to do with CM's Jellybean source incorporating the latest and greatest from 4.2 Jellybean. It might not be an issue. Maybe it is. Regardless, I'm still trying to figure out the kinks with it. I'll be scheming with the good folks who helped me build it in the first place tomorrow -- and maybe I can at least get CWM5 working with an external card -- I haven't really seen much in terms of difference between 5/6, aside from organization structure... and we're kind of gimped (a little) on the size of our recovery partition, anyway...
[Samsung Captivate Glide] dbrannon79:
sound good! I switched back to ver 5 mainly for the non bump backup! makes things easier to archive backups not to mention the ability to use them tweaking roms!! :D

I'll look forward to helping you test and any other way I can...

Thanks.
[Samsung Captivate Glide] terinfire:
Hopefully going to be able to spit out a new version today for you folks. Will keep you posted!

EDIT:

And that was quick! Tested and working! :)
[Samsung Captivate Glide] terinfire:
Reverted to 6.0.1.2 CWMR and used ICS instead -- everything is working. You guys also have options to not output blobs by changing the backup format to tar.

Everything working from what I can tell!
[Samsung Captivate Glide] dbrannon79:
Downloading and installing now, will report back with the good news!! :D
[Samsung Captivate Glide] amppcguru:
I couldn't get it to Flash to Glide

I downloaded the new version 6.0.1.2

Ran the version of Odin that unzipped with it but got error messages about missing dll files. (tmax.dll & zlib.dll)

Used my own copy of Odin3 v3.07 & loaded up the new recovery.tar.md5

Put Phone in Download mode & Plugged in & got it to connect to Odin.

Clicked Start but it just sat there on SetupConnection for 15 min. Then it failed.

Disconnected after Failed....

Tried over twice & redownloaded & got same results. :(

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> recovery.tar.md5 is valid.

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<ID:0/006> Added!!

<ID:0/006> Odin v.3 engine (ID:6)..

<ID:0/006> File analysis..

<ID:0/006> SetupConnection..

<OSM> All threads completed. (succeed 0 / failed 1)

<ID:0/006> Removed!!
[Samsung Captivate Glide] dbrannon79:
Reporting back....

odin installed perfect!

backed up using both dump and tar method, restored both and booted just fine. no problems here! :D

also saw where there are options for the external sd card for both flashing zips and backups!! :D

Great job!!

is there any way to implement this into the touch version?? :p

Thanks
[Samsung Captivate Glide] terinfire:
Just updated -- thanks for pointing out that the DLL's were missing for Odin! Sorry 'bout that.

The recovery should be fine. Did Odin actually recognize your phone? There's a chance that it didn't see it or something. This could also mean that your data cable is bad or something -- are you absolutely sure that Odin sees your phone and that you're in **download mode**?

Yep! And you can *restore* from external too! Haha.

As per a touch version... I'm going to say no for now -- it looks like CWM6 in the latest branch of CM is broken. There is something crapping out and soft-crashing the backup. At the moment, I've tried a few different solutions the smart folks (KemoNine and utkanos) have suggested going back to prior source in CM10 between that and CM9... No luck. But supposedly others are having issues, so it's not just us. I have a feeling that as 4.2 becomes more "stable" in CM, we'll have a chance at getting a more stable, up-to-date CWM6 Touch. There's also TWRP, which may be more viable, but I'd need to research and find out what they require to build a recovery image.
[Samsung Captivate Glide] dbrannon79:
sounds good! I agree we don't need problems! I dont know much about TWRP have only seen screen shots but from what I have seen it kinda looks like a windows 8 environment!! but for us to have it working on our glides would be another Plus!! :laugh:
[Samsung Captivate Glide] amppcguru:
Success!

I have had cable issues before & just bought 2 new ones. I also can no longer charge my phone thru the microusb port as it's no longer stable. Thank Goddess for interchangable batteries! SO I switched the cable to a different USB Port & was able to flash by holding the cable & phone together to maintain the connection. I really despise these microusb ports as they tend to wear out with very little use. :p
[Samsung Captivate Glide] dbrannon79:
just a suggestion... look down into the port on your phone! there may be some dirt or debris collected in the bottom of the port! I had this trouble with my wife's phone, used a tiny pic and compressed air to remove, after that it was fine!

just make sure you power off your phone and remove the battery when doing this and also use a plastic flat dental pic!! :D
[Samsung Captivate Glide] elban:
Installed it, thanks very much for the new recovery, it does have all the options which were missing from the old touch 6 version!

But I have a question.

For every partition, it creates a tar.gz empty file and a tar.gz.a file with the data.

Is this to be expected? I tried decompressing the tar.gz.a file but failed. Isn't it a normal gzipped tar file?
[Samsung Captivate Glide] terinfire:
Not sure -- building CWM doesn't require too much -- just an understanding of the device's partitions and a few other details. There were not adjustments to code. My assumption would be that this is standard CWM behavior.
[Samsung Captivate Glide] elban:
hmmm I've googled it and found only my own post.

can someone else report if they get this strange behavior as well? do you get empty tar.gz files along with tar.gz.a archives?

thanks
[Samsung Captivate Glide] kick buttowski:
Same thing here.
[Samsung Captivate Glide] amppcguru:
Yup same empty file...

Sent from my Rooted Samsung SGH-i927 Captivate Glide

Running Android ICS 4.0.4 LiteRom 0.8.4 LiteKernel 1.1.1 using xda-dev app.
[Samsung Captivate Glide] dbrannon79:
Ya I also have the same two empty files! Not sure what this means!
[Samsung Captivate Glide] terinfire:
I have the same files. I think that since it works and all is fine -- no reason to panic or worry. Just looks a little messier.

It could be an issue with something not compressing things due to the size of our recovery partition. The reason that the latest touch recoveries do not work is because we have to include a flag on the build for small recoveries (which you cannot do using the online builder Aquethys was using) -- our device has about 5MB (notice my actual tar.md5 is < 5MB) in the partition and the ones that have been included for touch that HAVEN'T been working are > 5MB. That's why some people were getting that error.

TLDR - this isn't really a problem, since everything works, I think.
[Samsung Captivate Glide] amppcguru:
Just tried to backup & then restore but got md5 mismatch error each time i tried to restore.

Sent from my Rooted Samsung SGH-i927 Captivate Glide

Running Android ICS 4.0.4 LiteRom 0.8.4 LiteKernel 1.1.1 & ClockworkMod Recovery 6.0.1.2 using xda-dev app.

---------- Post added at 12:47 AM ---------- Previous post was at 12:07 AM ----------

I also noticed after running a backup that the screen goes to just the cwm logo & at the bottom of the screen it says cwm 6.0.1.9? Before returning to the menu.

Sent from my Rooted Samsung SGH-i927 Captivate Glide

Running Android ICS 4.0.4 LiteRom 0.8.4 LiteKernel 1.1.1 & ClockworkMod Recovery 6.0.1.2 using xda-dev app.
[Samsung Captivate Glide] terinfire:
Yeah, you're running the old/bad/borken version. Make sure you're using the one in the OP... 6.0.1.2. If you're on 6.0.1.9, it won't work.
[Samsung Captivate Glide] dbrannon79:
Hey terinfire,

is there a way you can set the backup format to "tar" for the default?

I realized that each time the recovery is rebooted it defaults to "dump"

may be helpful for those who make archived backups!

Thanks
[Samsung Captivate Glide] terinfire:
I was wondering about this as well. I'll poke some of the actual CWM dev's I know and see if it's possible. I imagine if I break the code, it will, but my goal is to have a "pure" form of CWM that I haven't touched, other than the mandatory configuration information and baseline kernel/recovery. There may even be a config setting or something to set it up with in the CWM directory, as you can setup some interesting options that way (i.e. not displaying file names when backing up).
[Samsung Captivate Glide] elban:
I don't have my glide in hand now, but I remember there was a configuration file (a hidden file inside the clockworkmod directory) which contained the default backup format. It was set to tar, probably because that was the format I chose for the last backup I did.

The reason why it doesn't read it may be because that file was in the internal storage and backups were in the external storage instead... Maybe :)
[Samsung Captivate Glide] greeneyez15o:
can someone help me,i can make backups but when i try to restore im stuck on the boot image screen ?
[Samsung Captivate Glide] lorddavid:
Same problem, but with the touch recovery
[Samsung Captivate Glide] sbiricuda:
First of all, thank you!

I have just a small question: can I flash the new CWMR6 just overwriting the previous version?

Would a nand backup help me in case of messing something in this case?

Thank you :)
[Samsung Captivate Glide] terinfire:
Yeah, you can overwrite it -- just make sure you do it through ODIN.

I don't think a backup would really help you too much. It overwrites the recovery and doesn't touch anything else. If you have issues with it, you should be able to flash another recovery.

At present, though, this works fine. I have the phone, and I built the recovery from scratch myself *and* I use it pretty frequently. If it doesn't work, you can try using Aquethys' other recovery, but it doesn't support external SD. His does have "touch" on it, though.
[Samsung Captivate Glide] sbiricuda:
Crystal clear.

Thanks :)
[Samsung Captivate Glide] greeneyez15o:
O can make a backup but cant restore...its beeen workin fine til tonight
[Samsung Captivate Glide] VinayS:
not finding option to "Wipe Battery Stats"
[Samsung Captivate Glide] terinfire:
What are you backing up to and restoring from? Are you sure you're backing to/from the same source? I just did it now to test and make sure it wasn't some weird date issue -- and had no problems.
[Samsung Captivate Glide] terinfire:
It's there. Advanced > Wipe Battery Stats.

Are you using my Recovery?
[Samsung Captivate Glide] VinayS:
there was a version change,,(the previous recovery i had was showing as v6.0.1.9)..

had got it from xda only..

reflased the one in OP, it has the option..
[Samsung Captivate Glide] terinfire:
v. 6.0.1.9 was out for only a few hours and had some massive issues. If anyone else has this version in future posts, make sure you get the latest (which is an earlier version of CWMR). As it stands, currently CWMR 6.0.1.2 is the only fully-functioning CWM, due to an issue with current repo's of CM10 and beyond. In the event that these are fixed, I will update the main topic again.
[Samsung Captivate Glide] roothorick:
I'm getting "Can't mount backup path" when I try to backup to external SD. I have to help it along and mount /dev/block/mmcblk1 to /external_sd via ADB. Maybe you're assuming the external SD has a partition table? Mine doesn't.
[Samsung Captivate Glide] terinfire:
That's an interesting problem.

Just a few questions, first, though:

Are you sure you're using MY *latest* CWMR (v.6.0.1.2)? I know, it sounds like a stupid question -- but I released one version way too early before I had the chance to test it (6.0.1.9, I believe). And I regularly get silly questions (I have someone who's asking me if our CWMR will work on their Nokia or LG... and this isn't too uncommon) Please double check!

In the CWMR source (the partition table), I have it specifying/mounting mmcblk1 as external_sd. So this should already be getting taken care of inside the source. If not, maybe for some reason, there was a bad flash. If that's the case, can you try to reflash the recovery?

Let me know!
[Samsung Captivate Glide] bobbinthreadbare:
Finally got around to updating from the Touch version. Glad I can backup to TAR again instead of the billion files the blobs folder generates. Much, much better IMO. Thanks.
[Samsung Captivate Glide] hazard1nc:
I agree! It's awesome, thanks foe the share bro!
[Samsung Captivate Glide] dudejb:
Can I use backups from 5 on this version? Just asking as I have many cwm vs 5 backups that I would like to not lose.
[Samsung Captivate Glide] terinfire:
I'm not sure. You could try making a backup and then try to restore from a v. 5 backup. If you let me know, I can post it in the OP.
[Samsung Captivate Glide] yankeeornovember:
This may be a silly question, but here goes.

If I flash this (assuming it actually does flash, and I don't end up with a brick: I had TERRIBLE luck with my old Samsung Vibrant...), and already have a ROM zip on the SD card, can I flash the ROM successfully from Recovery without being rooted? Or is root required to flash a custom ROM on this phone?

I'm used to working only with Motorola, HTC, and my Nexus devices, but I'm trying to get my boyfriend's Rogers Captivate Glide to be a little more usable and stable (currently the phone's on stock, unrooted GB, and it lags, freezes, and shuts off regularly). Like I said, I HAVE played around with Android before, so I know of course to wipe data, cache, and dalvik cache before flashing, and know to backup my current ROM before doing anything else.

Any help would be much appreciated, and thanks in advance for all the work you've put into this!
[Samsung Captivate Glide] dman3285:
The phone doesn't need to be rooted. Just flash the recovery, wipe data, cache, and dalvik cache, format system( make sure you have a fully flashable rom zip on your sdcard before you format) then flash zip. As long as the ROM your flashing is rooted your good to go..
[Samsung Captivate Glide] dman3285:
Deleted double post..
[Samsung Captivate Glide] yankeeornovember:
edited to make a reply

---------- Post added at 04:30 PM ---------- Previous post was at 03:57 PM ----------

Thanks for the tip! And I forgot that formatting /system was a thing, I'll make sure I do that too. I'll follow up once I actually get the phone in my hands to flash this!
[Samsung Captivate Glide] taiber2000:
how to erase system with this version of CWMR?
[Samsung Captivate Glide] amppcguru:
Just switched back from twrp & forgot to set default to tar on first backup & tried to delete the blobs later but couldn't due to a bunch of weird files that couldn't be deleted.

Sent from my Rooted Samsung SGH-i927 Captivate Glide running @ndroid ICS 4.0.4 LiteRom 0.9.0 LiteKernel & CWMR 6.0.1.2 using xda-dev app.
[Samsung Captivate Glide] amppcguru:
Go to mount & format system

Sent from my Rooted Samsung SGH-i927 Captivate Glide running @ndroid ICS 4.0.4 LiteRom 0.9.0 LiteKernel 1.2.5 & TeamWin Recovery Project 2.4 using xda-dev app.
[Samsung Captivate Glide] terinfire:
Hm, weird. The way I like to delete the blobs is by connecting the phone to a PC and then deleting it via USB. Deleting it via the internal file explorers can sometimes not work. I nuked a LOT of Galaxy Nexus blob's yesterday via PC.
[Samsung Captivate Glide] amppcguru:
I have trouble with my microusb connection so ended up putting my sdcard into my laptop & deleted that way...

Sent from my Rooted Samsung SGH-i927 Captivate Glide running @ndroid JB 4.2.2 Rootbox & CWM 6.0.1.2 using xda-dev app.
[Samsung Captivate Glide] elmer71:
I followed the steps, I installed the CWMR sucesfully by odin

I started the phone in Download Mode but the odin application is showed. How I can start the CWMR ??

Sorry for my english
[Samsung Captivate Glide] jevan24:
So you have already installed cwm? Then you should boot into recovery..not back into download mode. Turn the phone all the way off and hold power and volume down until it boots into recovery.
[Samsung Captivate Glide] terinfire:
Exactly this.

There are three modes on the phone to boot:

1) Normal OS (Android)

2) Recovery (Can be a Custom Recovery)

3) Download (Used when EVERYTHING on the phone is bad)

You should only do #3 to install a recovery, but once that is done, you should NEVER need to do it again. 1 & 2 should be enough.
[Samsung Captivate Glide] hazard1nc:
Only in rarest occasion, as when I was modding the original captivate (still am), we had to reflash with kernels and modems, fully unlocked at&t version, as i guess there was a couple? Anyway...

Things have surely changed and become easier now for newer models and devs making it easier ;) just pointing out that, sometimes we can only do what we can do as we are given the tools to work with, but yes for the most part, download mode is only needed for flashing bad install fixes or flashing recoveries onto your phone. There are twrp and cwmr. As such, your phone ships with mobile odin on it, but very limited and I dunno if the mobile Odin apk works on this or not, I have not tried.
[Samsung Captivate Glide] jzamoras:
Hi, I'm little confused. I bought an unlocked AT&T which does have latest stock rom. It does have a recovery mode and looks like CWM. I would like to install a new kernel, new recovery and a new debloated and rooted rom before start using, I dont mind if it's JB or ICS at this time.

is there a debloated stock rom? if not, which one suits best for daily use?

do I need to update kernel? how can I do that?

do I need to update CWM? how can I do that?

coming from xperia looks like it's much easier than captivate :( thanks!!!
[Samsung Captivate Glide] phatryan69:
Learn to read the forums man... not trying to be an ass but its everywhere
[Samsung Captivate Glide] mrroks:
dude Touch Recovery CM6 link is not working ?? can u provide me the link ?
[Samsung Captivate Glide] bubor:
he said he doesnt support old recovery, you can download from xda the new one.
[Samsung Captivate Glide] mrroks:
sorry but i wanted the touch recovery !! .. so that my hardware buttons dont get affected ... :/
[Samsung Captivate Glide] AndyYan:
Get TWRP 2.6.0.0. It's this simple. Way better than an average CWM.

If it doesn't flash the old stock ROMs, learn to edit the ROM's updater-script and remove the assert getprop section.

Sent from Samsung Captivate Glide @ CM10.1.2
[Samsung Captivate Glide] mrroks:
Leave man :( i want the CWM Touch ...
[Samsung Captivate Glide] AndyYan:
But why? Seriously :confused:
[Samsung Captivate Glide] Adam77Root:
The Glide is among the selectable build targets now, you can make yourself one easily with the online builder. (http://builder.clockworkmod.com)

Sent from my LG-P880
[Samsung Captivate Glide] mrroks:
Leave .. dont want it anymore cause i use menu button as going up and home button as going down and serch key for select .. ;) thnks man Nice Recovery ! ;)
[Samsung Captivate Glide] AndyYan:
The Builder never successfully built anything for me...

Sent from Samsung Captivate Glide @ CM10.1.2