yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] thereassaad:
Can u share us zip or tar file please

☞ Reloaded ☜
[Galaxy S III Original Android Development] ad0dh:
http://www64.zippyshare.com/v/17966631/file.html
[Galaxy S III Original Android Development] FD10:
First post in this thread

http://xdaforums.com/showthread.php?t=2052091
[Galaxy S III Original Android Development] omdatura:
Frankly guys it would be really great to have a flashable zip as well as I have already wiped my phone when I realized I had to update my recovery from 6.0.3.1 to 6.0.3.2.

thx for ur great work anyway...
[Galaxy S III Original Android Development] Blackwatch:
A quick question please. If I am running CWM 6.0.1.2 do I still update to 6.0.3.2 via ODIN using the steps listed?

thanks in advance
[Galaxy S III Original Android Development] sunrainsky:
I tried making a backup.

When I restored it, it ended up in a boot loop. Am I missing something here?

I created a backup using the usual method for cwm, big image file.
[Galaxy S III Original Android Development] ad0dh:
I sugest you update to 6.0.4.7!
[Galaxy S III Original Android Development] Back2Revenge:
does my phone need to be rooted to install this CWM touch recovery?

im using stock rom and stock recovery though.
[Galaxy S III Original Android Development] foccacia:
does this work for I9305? I have just used CF Autoroot, installing CWM is next step before i can do a nandroid backup rite?
[Galaxy S III Original Android Development] orgert:
deletedd
[Galaxy S III Original Android Development] 8Marc8D8:
You`re the best.

I removed my brick with that!:good::good::good::good::good::good::good::good::good::good::good::good::good:
[Galaxy S III Original Android Development] Awais Malik:
I just login just to hit Thanks button

Superb work....I was looking for decent method but couldn't find except this one.. Thank you... God Bless You.. keep it up :)
[Galaxy S III Original Android Development] user109:
I also have i9305 and also wonder if this works on my i9305.. Anyone can comment? :crying:
[Galaxy S III Original Android Development] baanne:
after the 'reset' status my phone shutted down instead of reboot.

Now all I have is a black screen, cant use download mode anymore.

what should i do?
[Galaxy S III Original Android Development] nicesoni_ash:
Flash stock rom using odin.

Sent from my "GT-I9300/1+1" powered by Carbon Rom & Boeffla/ak Kernel

Fueled by 7000mAh ZeroLemon Battery
[Galaxy S III Original Android Development] baanne:
i guess there's no turning back cause all i get is a black screen and i can't use my phone on download mode, tried connect it to my pc to see if odin recognizes it, with no success
[Galaxy S III Original Android Development] nicesoni_ash:
Remove Battery and then plug it again and then try going in download mode, it should work then.

Sent from my "GT-I9300/1+1" powered by Carbon Rom & Boeffla/ak Kernel

Fueled by 7000mAh ZeroLemon Battery
[Galaxy S III Original Android Development] baanne:
oh god it worked!!! now i'm afraid to do something really bad lol

you said to install the stock rom, but i was using a custom rom, could i re-install it via odin? or should i go back to samsung 4.3 jelly bean?
[Galaxy S III Original Android Development] nicesoni_ash:
The problem you had was somewhat related to partitions as I had the same issue so it's better to flash the stock rom first with proper pit file if possible. Later you can flash any other rom you wish to have.

Sent from my "GT-I9300/1+1" powered by Carbon Rom & Boeffla/ak Kernel

Fueled by 7000mAh ZeroLemon Battery
[Galaxy S III Original Android Development] baanne:
yeah, it all started with an unsuccessful encryption.

thank you very much, gonna try it.
[Galaxy S III Original Android Development] toterkeks:
does this also work with the SHV-E210S ?
[Galaxy S III Original Android Development] mano2:
What if I can't find the following files?

/system/recovery-from-boot.p

/system/etc/install-recovery.sh
[Galaxy S III Original Android Development] mskip:
You can't see in the system folder unless you are rooted. You can flash the following zip file in custom recovery to delete the needed files.

http://skipsoft.net/download/checkfilesbackup/permanent-recovery.zip

Mark.
[Galaxy S III Original Android Development] reisyreinier:
Help whit my samsung galaxy s3 shv-e210l

Hi, im have a samsung galaxy s3 shv-e210l(korean version) and i flash recovery-cwmtouch-6.0.3.2-GTI9300 from this thread, im reboot in recovery mode and i have this errors

E:Can't mount /cache/recovery/log

E:Can't open /cache/recovery/log

E:Can mount /cache/recovery/last_log

E:Can open /cache/recovery/last_log

E:Can mount /cache/recovery/last_install

E:Can open /cache/recovery/last_install

My goal is install a custom rom but now when try to wipe cache for example im get other related errors.

Thanks in advance, im now stuck at boot logo.
[Galaxy S III Original Android Development] velizarcho123:
cwm is buggy, most of the roms gives error 6 while installing. I prefer TWRP.
[Galaxy S III Original Android Development] Jagadeesh Reddy:
Do i need to unlock boot loader for flashing this

Hi,

My mobile is asia version(Galaxy S3 neo 9300i ) . Do i have to unlock bootloader for this.

I donno whether it contains boot loader or not. Can u please explain the process to flash the recovery.

Thank you.
[Galaxy S III Original Android Development] georgedao123:
There's always bootloader in every Android device. About your device, I'm not sure that this thread is the right one for it. The thread is for I9300 (without anything after the last zero) only.
[Galaxy S III Original Android Development] kurosava:
NAND Write Start fail

<ID:0/003> Added!!

<ID:0/003> Odin engine v(ID:3.1005)..

<ID:0/003> File analysis..

<ID:0/003> SetupConnection..

<ID:0/003> Initialzation..

<ID:0/003> Get PIT for mapping..

<ID:0/003> Firmware update start..

<ID:0/003> SingleDownload.

<ID:0/003> recovery.img

<ID:0/003> NAND Write Start!!

<ID:0/003> FAIL!

<ID:0/003>

<ID:0/003> Complete(Write) operation failed.

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

I get this message whatever I try to do in odin :( any help??? I tried almost everything
[Galaxy S III Original Android Development] Ripae:
I get the same error...please HELP US!! :( :(
[Galaxy S III Original Android Development] DjeanDL600:
do i have to be rooted

need reply asap
[Galaxy S III Original Android Development] veeru153:
I got directed here by a thread related to SHV-E210* devices. Does this work on them as well?
[Galaxy S III Original Android Development] Salacue:
Work fine.

Thanks!
[Galaxy S III Original Android Development] Galeonero:
Hello, first of all thank you for making this post, for someone like me who does not understand anything, I am very clear.

I tell my situation more or less to see if someone would be so kind to give me some tips.

I have my s3 without working the touch after a bad installation, you see that I put the kernel of a note 3 by mistake.

Now I want to change the ROM for another that is not the STOCK.

Install the CWM, I think it was installed without any problems because nothing strange appeared.

The problem I have is that probe 2 ROM to install and all give me failures, try the MIUI 8 and the Linage 16.0.

What ROM is 100% compatible with CWM?
[Galaxy S III Original Android Development] kurtn:
Cwm is old as hell. Try twrp. And flash lineageOS 14.1
[Galaxy S III Original Android Development] Galeonero:
Hello, thank you very much for replying. But TWR is not yes or yes with tacit? According to what I read, they did it to be more comfortable for the installation? If so, it is impossible because I do not know whether or not my tacit is on the plate or because the kernel is wrong
[Galaxy S III Original Android Development] kurtn:
Twrp has it's own kernel. So if touchscreen doesn't work in twrp, it is most probably a hardware issue.
[Galaxy S III Original Android Development] ahac85:
It's working fine for me
[Galaxy S III Original Android Development] brian6685:
Remove please.
[Galaxy S III Original Android Development] fenstre:
Hey, Koush. I think we mean mounting /mnt/sdcard and also mounting /mnt/extSdCard for internal and external storage, in the "mounts" menu--perhaps to rename backups that were just created. For me, it's to use adb shell. (I'm not sure whether you've already added this, because I haven't updated yet. In my older recovery version, there's only an option to mount "sdcard", which seems to mount external storage only.)
[Galaxy S III Original Android Development] Fauert:
Update

Hi Skip . Update please : recovery-clockwork-touch-6.0.0.7-i9300 :D
[Galaxy S III Original Android Development] Northern-Loop:
Is it possible for backups to be in the external sd card?
[Galaxy S III Original Android Development] 9Lukas5:
I haven't a external sdcard, but if you reboot into the recovery you can choose under backup and restore backup to external sdcard, so simply try it, if it doesn't and you need it, simply flash back the one you had before.

L
[Galaxy S III Original Android Development] Burjuy5:
Somebody please post recovery-clockwork-touch-6.0.0.7-i9300 in tar-file...
[Galaxy S III Original Android Development] rendymulandy:
have you tried flash .img file with mobile odin?

i've tried this and its fine :)
[Galaxy S III Original Android Development] Northern-Loop:
Sorry should of said inside ROM Manager
[Galaxy S III Original Android Development] Northern-Loop:
http://db.tt/ScXcb3BF

Greyed out at the moment
[Galaxy S III Original Android Development] Burjuy5:
Tell me how. Mobile Odin don't see .img files. Maybe i do something wrong?
[Galaxy S III Original Android Development] testies99:
Rename the file to recovery.img.
[Galaxy S III Original Android Development] schack:
Same problem here.
[Galaxy S III Original Android Development] Burjuy5:
It's OK now! Thank's! :good:
[Galaxy S III Original Android Development] babijoee:
I'll post a tar file in abit.
[Galaxy S III Original Android Development] kastafela:
6.0.0.7 Is Out

Link

:D:D:D:D​
[Galaxy S III Original Android Development] mskip:
Hey mate,

I have done some preliminary tests so these are my results:

Tested on Galaxy S3 International version with 16GB Internal and 32GB Samsung micro SD Card.

Both recovery images downloaded from clockworkmod this morning at 09:30.

CWM Recovery 6.0.0.8 (non touch)

Install zip, choose zip from external sdcard. No files found (not detecting extsdcard)

Mounts and Storage, mount /sdcard. Not changing to unmount when selected (external_sd will mount and unmount but is being detected by windows explorer when mounted). Im not sure if this is what is supposed to happen when storage is mounted but that was my assumption so that files could be loaded to it from recovery.

Backup and Restore, backup to internal and external sdcard BOTH produce a blobs folder in the Clockworkmod folder and a backups folder with the relative partitions linking to the blobs folder im assuming. Is this right as the tar backups were much better and easier to manipulate?

This is just an observation but the status bar that appears when backing up and such gets hidden by the text so it might be move the status bar to the bottom and have a border of 4mm at the bottom so status text cannot go over the status bar.

CWM Recovery 6.0.0.7 (touch)

Install zip doesnt have an option for extsdcard so I assume this isnt working

Mounts and Storage, same as non-touch version.

NAND backup doesnt have an option for extsdcard so I again assume this isnt working but backing up to Internal Storage gives the same results as the non-touch version.

Ok so I heard something about the new versions having incremental backups? If this is right then it would account for the central blobs folder and small backups size but would standard backups (the old way) still restore on the new clockwork versions? All my ToolKits use scripts to create CWM compatible backups.

Thanks for all your work on Clockworkmod mate :)

Mark.
[Galaxy S III Original Android Development] babijoee:
Hmmm its clears but when it flashes Odin crashes. Must look deeper into it
[Galaxy S III Original Android Development] Walhalla:
I created a flashable tar for Odin/Mobile Odin but it makes no sense to publish as the points mskip mentioned above are not working.
[Galaxy S III Original Android Development] mskip:
I have posted a tar to 6.0.0.7 but also posted my observations above. I still think the best stable version so far is 5.8.4.3 as the format of backups seems to have changed making them less universal :(

Mark.
[Galaxy S III Original Android Development] mskip:
If you use windows then I have created a great new tar convertion process for the S3 ToolKit which just requires putting the img into a folder and selecting yes in the ToolKit to create an Odin tar :)

I will create a standalone app for the img to Odin tar converter for Windows and post it in a bit as I havent ever seen anything like it before.

Mark.
[Galaxy S III Original Android Development] inffy:
Yeah the backup process has changed, and it now uses incremental backups. The blobs folder where the "actual" backup is (if I understanded correctly koushs tweets and posts).
[Galaxy S III Original Android Development] babijoee:
Oh sorry for the confusion, i was talking about my own flashable tars. not yours mskip.

Since theres not much support for extsdcard i guess i wont bother and you've already uploaded it :p
[Galaxy S III Original Android Development] mskip:
I wasnt going to bother either but as other people said they would I thought I would get it first ;)

Mark.
[Galaxy S III Original Android Development] mskip:
Hmm I dont think I like that its soo much harder to seperate backups to save them to pc if all the data goes in the blobs folder..

Would be better to have an option of performing a full (old method) backup or starting an incremental backup.

Mark.
[Galaxy S III Original Android Development] edgarf28:
Can anyone post a tar of 6.0.0.8 (non touch) pls?
[Galaxy S III Original Android Development] brian6685:
6.0.0.8 restores and backs up on ext SD card for me, no problems.
[Galaxy S III Original Android Development] 9Lukas5:
What I haven't understood up to now is, if the backup itself is in the blobs folder and it makes incremental backups, what happens if I change the rom and make a backup of that? If restore it then, do I have things from the old rom included?

I mean, does it see the difference between changes from one to the next backup and a complete new rom/fresh install?

L
[Galaxy S III Original Android Development] bedtime_with_the_bear:
CWM hashes the source file (SHA-256 I think but I could be mistaken) and then checks the blobs directory. If an object for that hash exists, then only a placeholder is created in the backup directory. If the object does not exist, then it is copied into the blobs directory and a placeholder is created in the backup directory.

If you backup a completely different ROM, then the only time you will have files from the old ROM is if they are identical, bit for bit. In that case, there's no problem.

When you flash a new ROM, your blobs directory will grow in size by up to the size of the new ROM, but subsequent backups will only grow it by the size of all changed files at most.

You can trim the blobs directory by deleting a backup directory as normal (NOT the blobs directory) and then running a new backup. The first thing CWM does is garbage collection - basically, deleting all blobs that do not have a corresponding placeholder in any backup directory. Of course, how much space you save will depend on how many blob objects are unique to that particular backup.
[Galaxy S III Original Android Development] IamIrene:
can it backup to micosd storage ???
[Galaxy S III Original Android Development] babijoee:
mskip i would suggest linking 6.0.0.8 build unless i missed it as it works pretty good. restore/backup/install from internal and external sdcard works great.
[Galaxy S III Original Android Development] mskip:
Added to the first post :)

Mark.
[Galaxy S III Original Android Development] Mr. Droid:
The touch still doesnt work with external sd?

Does the new 6.0.0.7 work with Jellybean?

Thanks
[Galaxy S III Original Android Development] inffy:
I think touch doesn't have external support, only the non-touch version 6.0.0.8
[Galaxy S III Original Android Development] :
now this really sucks. i was trying all day to make my own flasable zip with the newest touch recovery and it didnt work! LOL and now i read that it doesnt work right anyway:eek:
[Galaxy S III Original Android Development] fenstre:
I'm getting errors when backing up to internal storage with 6.0.0.8. The first and second times it backed up successfully, but then it started giving errors:

Unable to find mounted volume: /sdcard
Error finding an appropriate backup handler.

To me, it looks like it's trying to mount /sdcard, but /sdcard is internal storage and is a symlink to /data/media and thus should not be mounted. What confuses me is the fact that it worked once or twice but won't work again.
[Galaxy S III Original Android Development] ageva:
6.0.0.9 was out moments ago and I'm not getting this error so you might want to update and check again.
[Galaxy S III Original Android Development] fenstre:
With 6.0.0.9 touch I get:

Error while making a backup image of /system!

Also, "adb shell" isn't working well. It keeps getting disconnected with the only message: "error: closed".
[Galaxy S III Original Android Development] mskip:
Same error message here with 6.0.0.9 touch and just rebooted my phone and its stuck in the bootup screen..

Flashing older recovery and boot image to see if it fixes it.

EDIT: Nope that didnt work I guess it screwed up my system partition somehow, having to restore a backup..

Mark.
[Galaxy S III Original Android Development] fenstre:
My phone is also stuck on the boot screen and cannot even boot recovery. Since two of us are stuck on boot screens, PEOPLE SHOULD NOT TRY THE NEW RECOVERY IMAGES YET. I think there may have been an error about something in /cache getting messed up.

I can still flash using download mode, and I think I'll have to reinstall cf-root in order to get my system back. I'm waiting for a reply on this thread before I try anything, though.
[Galaxy S III Original Android Development] Dextrosan:
I have flashed the new 6.0.0.9 about an hour ago and I thought I would do a backup... Stuck on boot too. Anyone came up with a solution? I dont want to reinstall fresh and my backup is kinda old. Thx for any input.
[Galaxy S III Original Android Development] temasek:
Cwm touch 6.0.0.9 corrupted /system as well as wiped my external sdcard. What i did was to try the backup to external sdcard and im f***. Beware!

I've tweeted koush about these issues.
[Galaxy S III Original Android Development] fenstre:
<delete please>
[Galaxy S III Original Android Development] Boaty:
Overhere not any problem with CWM 6.0.0.9. Just backed up my ROM to the internal SD-card, and restored it from the internal SD-card and no problems occured.
[Galaxy S III Original Android Development] fenstre:
Reflashing cf-root fixes it, partially. This way I can reboot to recovery with Home+VolUp+Power. The problem is that multiple partitions are messed up, and flashing cf-root fixes the cache partition.
[Galaxy S III Original Android Development] temasek:
It's the external sdcard function that has issues. If u don't believe try backup to external sdcard from cwm 6.0.0.9 touch.

Be warned.
[Galaxy S III Original Android Development] Dextrosan:
I forgot to mention that I got the same problem with the non touch version. Unfortunately I also tried to backup to external sd.
[Galaxy S III Original Android Development] mskip:
Well I got my phone back and running by flashing a stock rom via Odin.

CWM TOUCH 6.0.0.9 CORRUPTS ONE OF THE PARTITIONS DO NOT FLASH!!

If you get stuck at the boot logo and dont have a nand backup to restore, download and flash a stock system image via the S3 ToolKit. It may overwrite your system partition but as there is the userdata doesnt get formatted you will not lose your installed apps and uour Internal Storage data will still be there.

Mark.
[Galaxy S III Original Android Development] fenstre:
So after half-fixing the problem, I rebooted into CWM-recovery (from CF-Root, like I said), and had a look at /system--it's totally erased. /data looks pretty bare, too. I think everyone without backups will be screwed...

Also note that CWM-recovery from CF-Root only detects external storage on my phone. But if your backups are on internal storage, I'm sure you could trick the system and mount it in place of /sdcard.

What concerns me even more is that I can't boot the supposedly stable version of ClockworkMod Touch Recovery that's linked in the first post. Only the CF-Root version.
[Galaxy S III Original Android Development] temasek:
The least I expected was the wiped of my external sdcard. Lost about 80+ children photos.

Sad....better don't tell my wife about it....

Lolz
[Galaxy S III Original Android Development] mskip:
Sorry to hear that my External SdCard has been wiped too but luckily I have dropbox set to backup media over wifi so all the important stuff is safe on my pc. Everything else is gone though :(

At least it gives me the opportunity to clean up my micro sdCard there was a load of rubbish building up on it lol.

Have added text in the thread title and OP to hopefully warn people before they flash 6.0.0.9.

Mark.
[Galaxy S III Original Android Development] Northern-Loop:
Is it just touch that is the problem?
[Galaxy S III Original Android Development] mskip:
I only tried the Touch version so I cant comment on the non-touch version but I wouldnt take the risk until someone hears more. I have tweeted clockworkmod to ask for the link to be taken down as it is dangerous but not had any response yet.

Mark.
[Galaxy S III Original Android Development] peosb:
No, non touch wiped my system and internal sd.

External left intakt though.
[Galaxy S III Original Android Development] fenstre:
I'm pretty interested in the new incremental backup system. Did any versions of that reliably work without wiping people's phones?
[Galaxy S III Original Android Development] 9Lukas5:
I hadn't problems up to now with tbe new build.

L
[Galaxy S III Original Android Development] mskip:
Which build are you using and what exactly have you done with it? Have you rebooted your phone after using it?

Mark.
[Galaxy S III Original Android Development] Dextrosan:
I was not that lucky. Non touch also wiped my card. I guess it differs device from device then.
[Galaxy S III Original Android Development] fenstre:
Maybe it wipes whichever location you attempt to back up to. It didn't wipe my sdcard, but I was attempting an internal backup.
[Galaxy S III Original Android Development] 9Lukas5:
I have downloaded the cwm 6.0.0.9 touch .img file from clockworkmod.com/rommanager, renamed it to recovery.img and flashed it through mobileOdin. Then I rebooted into recovery and made a backup of my current setup (CM10 preview2). Hadn't any problems so far.

L
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] kurokirasama:
Hi everyone:

I bought a Galaxy note in March (i still don't get the ICS update T_T) and since e few weeks, when I turn it on, after i enter the pin code to unblock the SIM, the note restarts suddenly, but it is a weird restart because it does not appear the "turning off and turning on videos", only the turning on sound. And then my SIM is not available and it keeps restarting every few seconds...

So I have to turning off manualy, NOT ENTER THE PIN CODE for a few minutes, 3 I think is enough, 5 I am sure it is enough, and then enter the pin code and the everything works find...

This is troublesome because sometimes the note restarts out of nowhere and i have to do all again...

I was thinking in restoring it to the factory configuration if no solution appears...

Thanks for reading and cya
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] Braxos:
First remove Sim and sd card clean them. Reapply them and try the phone if this isn't helping try another Sim, without the sd card. As last solution reset the phone.
[Xperia Play Android Development] IE-coRe:
First =)

Sounds nice, i will try today. Really ICS Beta kernel, not aosp? How is performence? Touchpads are not working right?