yashsingh1/xdaforums huggingface dataset:
[Galaxy S II General] beaver2233:
pretty sure he wont be able to flash it as its using the stock/standard recovery, not clockworkmod
[Galaxy S II General] da.trute:
so CMR isnt flashing at all then.

To clarify:

- you were defo in download mode, odin picked up you device

- In step 5 you chose "PDA" and the file you flashed was definitely:

GT-I9100_ClockworkMod-Recovery_4.0.1.4.tar

- you didnt unwrap this file to a zlimage did you? (sorry to ask)

-odin also showed green, completed and rebooted your Phone?
[Galaxy S II General] humphrey74:
I really did do all steps right. Believe me, I meanwhile know how to use odin, and that I don´t have to unwrap the file at PDA.

We both (who have this problem) tried everything to get into CWM recovery mode. but we don´t get this advanced menue.

I flashed the 'GT-I9100_ClockworkMod-Recovery_4.0.0.2.tar' file because I didn´t find the 4.0.1.4 Version.

But for now, I removed the battery and want to wait minimum 20 hours as suggested here before.

If not, I will try 4.0.1.4 Version of CWM
[Galaxy S II General] chinhe:
what was the last rom u installed before getting in this situation?
[Galaxy S II General] humphrey74:
It was no ROM, only an Kernel.

I followed the instrucions from here

the kernel used there is 'XWKDD_insecure.tar'. after that I rooted with Superoneclick
[Galaxy S II General] da.trute:
Hi, really sorry this hasn't helped, didn't mean to suggest you didn't know what you were doing, I just try to take a logical approach to these kind of issue which means you have to take a step by step approach and not move on until you are sure each step has been completed correctly.

what is odd here is that you are getting the original recovery options as if your phone has never had another installed, I can only think that when you tried to flash back to stock this overwrote this and the combination of flashing tegrak/cmr and stock has corrupted or locked iy in i some way. Then again does it have an SBL like the galaxy S I wonder as there was a problem with some of the SBL's on the first galaxy.

Hope the battery wait solves your problem, although if you haven't actually got a cooked rom on anymore you could get away with taking back to the shop, just tell them it wont boot. My first phone stopped connecting to my PC, I could'nt get it back to stock so I just took it in saying it wouldn't boot, they turned it on and when it wouldn't boot just replaced it. You could get unlucky in that the assistant might know a bit about these phones but its an option if nothing else works.
[Galaxy S II General] da.trute:
could also try PM codeworkx, probably quite busy but a good place to go with a CMR issue.
[Galaxy S II General] lyriquidperfection:
Try this as no one else has suggested it.

Put the following code into your dialer:

*2767*3855#

This is the engineering code to perform a factory reset. Resetting it via this method is more advanced and does a complete rebuild of the device.

Hope this helps!
[Galaxy S II General] humphrey74:
thanks alot for your ideas. I hope the battery removal will work :)
[Galaxy S II General] humphrey74:
I did this, too. No success either ...
[Galaxy S II General] da.trute:
had another quick look through the thread, didnt notice if you had tried the emergency firmware recovery in Kies, it was suggested but no reply.
[Galaxy S II General] humphrey74:
Hm, I dont know if I have tried this option. But I will do it soon, after my 20 h battery off task ;)

Tomorrow I will let you all know, if this was successful or not. If not, I will try all other methods suggested here.
[Galaxy S II General] Logi_Ca1:
When somebody mentioned "Groundhog Day", that's exactly the way to describe your phone right now.

Unfortunately I don't have any new ideas to offer, except to say good luck to you. That's a really strange issue and I hope you get it fixed soon with a minimum of fuss and financial loss. ;)
[Galaxy S II General] yooyo3d:
Can you try to take picture/video using camera and copy it on another location on phone or on external mcorSD. Is it correct or corrupted copy. If it is hardware error issue you should get corrupted copys. But if everything is OK, then I think that bootloader doesnt do the job. It reports successfull writes but it doesnt happens.

If you try to flash unofficial firmware does the counter change?
[Galaxy S II General] MicioMax:
Just my 2 cents.... can you try to upload via USB or wireless a *big* file to your sd, for example a video file, big enough that it can't buffered in ram, then copy back to your PC and see if it's corrupted ?

If flash is broken or locked, you should have an error copying the file on it, or at least a corrupted file copying back to PC.

After this test, we can at least be sure if flash is broken or not.

I recommend you some really big file, maybe 1 GB.

Max
[Galaxy S II General] humphrey74:
Mh, I didn´t answer some statements as I see.

But to avoid some missunderstandings:

the SGS2 has one internal sd card which is a partition being mounted by the system itself. AND the SGS2 hast an external sd, which will be mounted as well, if some micro SD-Card is plugged into the slot.
[Galaxy S II General] humphrey74:
OK yooyo, good idea. Because THIS was exactly my first attention for this problem I have.

After my first flash and rooting with superoneklick, I made a video with my SGS2 and wanted to play it in the stock-player on the device. but I only got a message which said something like "File cannot be opened".

I don´t remember the exact phrase, but the new video could not be opened.

In the media gallery the new recorded video didn´t have a preview thumbnail.

Similar with images token by my device. I took a picture, could view it, but it disappeared after a reboot.

This was the reason I decided to flash a custom ROM, hoping this little problem blowing away. ...

Edit: Sorry guys, where can I see this flash-counter?
[Galaxy S II General] Logi_Ca1:
The flash counter is displayed at the top left corner in the download screen that you get when you hold POWER+VOLUME DOWN+HOME when booting.
[Galaxy S II General] humphrey74:
okay thx.

Cannot have a look to it a the moment. but I think the number, if I remember right, didn´t change at all ...

I will report
[Galaxy S II General] Bashkim:
This was one of the first things I've tried...

- I've generated a 6GB File with Java

- Copied it to the internal SD-Card

- Copied it back again

- Compared both files with Java

--> 100% identical
[Galaxy S II General] da.trute:
incidentally, did you both do exactly the same thing to create this problem, .e.i flash a different Kernel on top of the current ROM you are on, just wondering if you have created a kernel / recovery / bootloader conflict in that they are simply not playing well together.

Are you both at the same point with recovery, you both are showing the originalk recovery option when using volume up / power up options>
[Galaxy S II General] Bashkim:
- I've rooted my device with superoneclick after I bought it -> no prblems so far

- Then I updated my device with Odin to K7 and rooted it then with Tegrak Kernel -> still no Problems

- Then I updated again (KF3 & Tegrak kernel) -> also no problems

But after ~4 days I noticed that everything was lost after a restart.

No, I'have a custom recovery mode (by Tegrak).
[Galaxy S II General] MicioMax:
So, your flash is *not* bad, it simply can't. At least, if you don't have some haunted storage media, of course :rolleyes:

There's no way 6 GB file can be stored and successfully retrieved from a broken flash.

So, now, you could do a couple of stuffs to see what's in your flash, supposing, of course, you've got a rooted phone :

1) install a terminal app, or a ssh server, if you know what is it.

2) from terminal, issue following commands :

su

mount > mount.lst

ls -lR / > ls.lst

BTW, the fact that erased data re-appears on boot, besides a broken flash (*very* unlikely....) make me think on some

automatical backup-restore app running on boot.

grab both mount.lst and ls.lst generated files, zip them and attach them here.

That should give us some hints of what you've inside your flash....

Max
[Galaxy S II General] MicioMax:
.... Just another idea that came suddenly in my empty brain....

Did you make some backups with CWM or others ? I mean.... do you have some backup files on your SD ?

Second question.... booting last longer than before ?

If 1 = yes and 2 = yes, it could be some sort of magic script restoring a backup on boot. Look for backups and wipe them, then reflash.

Max
[Galaxy S II General] da.trute:
so your problem is slighty different, you have flash options but they dont work, the other chaps has no flash options just basic recovery mode, no CMR.

Perhaps these are unrelated and should be discussed independently?
[Galaxy S II General] asianguy8569:
*2767*3855# type that in to the phine dialler that should sort it
[Galaxy S II General] da.trute:
! FAIL !

Have you actually read the entire thread?
[Galaxy S II General] blasiusx:
I think that problem is that you had activated a write protection. This could only happened, when you flashed the new root kernel, something goes wrong.

Could you plugin your phone to pc ( usb debbuging on) and use superoneclick once more ? Then try to unroot and deinstall busy box, adb and all other tools ? Is this possible ?
[Galaxy S II General] MicioMax:
Nope, he can write to sd card while phone is on. He just loose all changes on reboot. The only explanation is some backup app/script that re-apply a stored backup.

Max
[Galaxy S II General] Solidswede:
Your phone is corrupted from day 1. Why you flashed a custom ROM even though you knew it didn't behave properly is beyond me. I would seriously suggest you go for warranty repairing it if they will accept it.

All others posting suggestions should read the entire thread so you know if you truly can help or just posting same suggestions over again.
[Galaxy S II General] MicioMax:
I really can't see where the phone is corrupted :

- it boots and works

- it can read/write to flash without errors

- it can enter load / recovery mode

If you know some flash device of 16 GB that accepts a 6GB file without errors, and can restore erased files by itself when re-powered on, please tell me, I need a couple of those :D

So there are just 2 possibilities :

1) Some script is restoring a backup

2) humphrey74 is just kidding us :rolleyes:

Max
[Galaxy S II General] yooyo3d:
1. Check free space on internal sd card

2. Delete everything you can from your internal SDcard and check free space after. There should be close to 11gb free.

3. Fill internal sd card with some huge file or with tons of mp3. Try to fill up sdcard to the last byte. Make sure you add all those files in one folder.

4. Disconnect phone from PC

5. Connect phone on PC and copy back all your files and compare with original files.

4. Reboot phone.

Is everything restored back? There is no chance to restore all the files. If its restore files then I think filesystem on sdcard partition is corrupted
[Galaxy S II General] CLShortFuse:
Flash this:

http://xdaforums.com/showthread.php?t=1118693

It's a rebuilt kernel. After that, see if you can odin back to stock
[Galaxy S II General] da.trute:
CMR flash has already been attempted, it wont take.
[Galaxy S II General] humphrey74:
Hey dudes :)

I started working now and see you all wrote a lot here. Ok, I will read insensively your postst, but:

I am NOT kidding you guys! ;)

I forgot my device at home, so I have to wait till the evening to test, what happened after my battery-removal.

Battery will be out of device for 32hours then.

Oh,.... there are lot of things to test, I see. I did not test all of your suggestions. but I will do soon!!

It´s great to see you all take your time to get a solution for this f.....g weired problem :) Thank you ALL
[Galaxy S II General] da.trute:
good luck, hope things work out for you.
[Galaxy S II General] pulser_g2:
Can't go into too many details, for various reasons, but there IS an ability to prevent flashing on this phone... It shouldn't trip on these devices though... And it wouldn't (AFAIK) manifest itself in this way...

Anyone with this issue, can you remember what files you SUCCESSFULLY flashed? I have a theory regarding one particular file, but I need to see what you flashed. :)

If you're not 100% sure, try and find out, but it's best if you are certain :)
[Galaxy S II General] DaFileFather:
Can you please give us the link to this trick? :)

@humphrey / bashkim

I was thinking like this:

1)

Try to flash ur

original ROM!

(which u got when bought the phone)

via KIES

!

Look what will happen then.

2)

Use a USB JIG to reset counter and to get in download mode then try another ROM via ODIN. And look what will happen then.
[Galaxy S II General] da.trute:
See above thread, I am convinced Pulser is onto something as this kind of thing just never happens, got to be something deep and dirty only a few people know about.
[Galaxy S II General] MicioMax:
Yep, maybe, but if you erase an app on running phone, it should stay erased, not re-appear mysteriously on reboot :D

It seems that recovery is blocked restoring some backup (as when you select restore from CWM menu, it reboots and restores the backup).

If so, you could flash as many times as you want, you'd get always same rom on reboot.

I don't know how is coded the "restore" feature of cwm, but I suppose it creates a script and, on reboot, when script is present, it gets executed and backup restored.

Just suppose the restore script "forget" to disable itself after restoring, it'll be executed on each boot.

Because of that I asked to locate and ERASE any backup present on sd.

Ciao

Max
[Galaxy S II General] humphrey74:
Hm, as I said some pages before. Me, I successfully flashed the kernel named 'XWKDD_insecure.tar'. After that, I rooted with Superoneclick.

That was the last time a flashing was successfull.

I think the reboot after the rooting and installing some Apps, at the time I discovered that I cannot play my recorded videos anymore, was the last "normal" phone-state which always is getting recovered on new boot.

But if the first flashing itself is the reason for my problem, why are the few apps installed AFTER the rooting being restored as well ? (newer ones NOT)
[Galaxy S II General] MicioMax:
Because you installed something that made a backup and is restoring it on each boot. The *only* possible explanation.

Max
[Galaxy S II General] richyy74:
How long does it take the phone to boot up? That is because any kind of restore takes time. But I guess it is not a restore issue, something is preventing the flash memory to be written. Just if you could test out: can you place anykind of file to internal sdcard partition which stays over a reboot? Is it there between reboots: if you unmount and remount internal sd?
[Galaxy S II General] MicioMax:
He told that if he erases an app, on next reboot it's still there, and newly installed apps vanishes. It *must* be a restored backup happening there.

Max
[Galaxy S II General] daraj:
Choose repartition with PIT file when flashing. Try it. Just 2 cents.....
[Galaxy S II General] richyy74:
I know that but:

1,I know no app that would backup or restore /mnt/sdcard. Furthermore there is no space to backup to as that is the largest partition.

2, I think no backup-restore can survive a format internal sd then flash new firmware sequence.

If a file, any file survives an internal sd unmount-remount then physically the movienand can be written. If not there is a big problem. I say internal sd because it is movienand and not related to system or root or anything.

Another test is if external sd can be written in the phone and maintains its files. I guess that will be a yes and internal sd would be a no.

I think new data physicaly do not get written to flash. My best guess that some kind of writelock got triggered in the flash memory. If it is some feature samsung never used, a hardware fault, or caused by software failure I do not know.

Anyway I think it is due to a repair center.
[Galaxy S II General] richyy74:
Furthermore no app will survive a repartition to restore anykind of backup afterwards.

So I suggest:

Check if anykind of file let say a picture survives a reboot on ext sd then on internal sd then on cache then on system. I bet only ext sd will work. Then it can be movienand failure for example.

If internal sd works best bet it is somekind of a writelock mechanism.
[Galaxy S II General] MicioMax:
Resuming :

1) The card *can* be written, and is no matter of cached files in ram, because he tested with 6 GB file, writing to it then restoring to PC and comparing. So the card is writeable and ok.... or am I missing something ?

2) Phone boots. So, the card is readable on boot too

3) Erased files reappears and added file disappear after booting.

4) flashing seems to go well (besides some cases)

I don't know how far he went on formatting/repartitioning the flash, but I guess not too deep. But, of course, it could be a recovery code that hides inside boot part, quite unlikely but not impossible.

That's one of the reasons I asked for some listing of internal data, if a backup is restored, it *must* be somewhere, in boot area there's no space for it.

Max
[Galaxy S II General] richyy74:
If i remember well it was an insecure kernel rootes with superoneclick so basicly a stock kernel so I thomk anykind of boot time restore is very unlikely.
[Galaxy S II General] MicioMax:
You forget that with a rooted phone, *any* app could do the trick, and he installed many apps after rooting.
[Galaxy S II General] Solidswede:
Max he wrote earlier in his thread that the reason he started custom flashing was because he had troubles with corrupted movies when recording them.

A corrupted card or memory for that matter can behave like this because you never delete when you format. While I did ask him to try and copy a big file to his newly erased internal memory I guess he forgot to test this.

There is a controllerchip that handles the phones memory and other things that might report stuff even though they are untrue. Also as you are saying there could..... wait a minute..... the phone has a retail mode.

Hey you might have triggered the phone's retail mode, you didn't download and use that app did you?

Anyway as you are saying Max, sure the phone could be fine but if he did have problems from day 1 and it was in the way he described it, it is and will always be corrupt.
[Galaxy S II General] htc9420:
Are you talking about AMEND support - I didn't know any reason why would someone still use scripts from 1.5 devices...hmmm?...but, anyhow, it should never flash.

However, it ''could'' be a possibility....because I've seen someone exploiting that in order to have his business thrive ... but it really makes no sense in 2011.

Hmm, I don't have the tools/time to research that AND the way to help them get rid of the 100...:D
[Galaxy S II General] humphrey74:
okay, quick-report of what I have done:

- battery was out about 30 hours. put it in, pushed device directly into dl-mode and flashed a full stockrom. -> no change

- watched out that DL-Counter in Modus is still on 1?!!

- copied 4GB file to internal sd via pc, and back. compared, file not corrupt

- deleted all internal sd data via pc. after reboot all data still there

- took a picture, tipped on the lower left side thumbnail to view it, imgviewer shows the last picture from my f...ing rebooted state. actual image I made blowed away...

I am very tired now. I just want to let U all know my few first results.

Tomorrow morning I will read all the missed replies, to test all the other suggested methods.

Cheers Guys :)
[Galaxy S II General] humphrey74:
sounds like pretty good way... I will post this data tomorrow. i promise ;)
[Galaxy S II General] Paul2436:
guys...did you really test this? i can't belive it...

1. copy a big file (>= 1gb) to your internal sd

2. disconnect your phone

3. connect it again

4. copy the file back

5. open it with a hex-editor (e.g. with hxd)

i'm prettey sure you will only see zeros.

=> your memory controller is ****ed up.
[Galaxy S II General] humphrey74:
Hi

few more tests I´ve done:

- removing battery while running OS, then putting it back an switch it on -> does not take some effect

- flashing ONLY a PIT file does not take some effect

- after copying a 3.2GB sized file to internal sd, unplugging device, plug it again -> copied file dissapeared

- leaving the phone w/o battery for 30 hours -> no change

- ClockWorkMod Recovery install doesn´t affect, because after reboot I only have the standard recovery options

- flashin stock firmware after 30 hours battery removal -> no change

- cannot test an emergency recovery via kies, because I dont have any recovery

- made 'ls.lst' and 'mount.lst' and zipped´em into attached 'mnt.zip' here

View attachment mnt.zip

Edit: "Erased files reappears and added file disappear after booting." => AND after sharing/unsharing internal_sd with USB storage
[Galaxy S II General] flamingspaz:
Maybe try downloading a terminal emulator and typing:

>su

>chmod -R 777 /

EDIT: You can also try flashing CWM using Odin then holding Power + Home + Vol UP right after it finishes.

All other options have been tried, im just thinking out loud here.
[Galaxy S II General] humphrey74:
# su

# chmod -R 777 /

Bad mode

Hä??
[Galaxy S II General] humphrey74:
won´t have an effect. we both have already tried this
[Galaxy S II General] flamingspaz:
The last thing I can think of is to download aLogCat from Market, Delete any app, load aLogCat and save the file, then post it here.

I'm not sure if you've already done this, but if you have you're gonna need to send it in for repairs.
[Galaxy S II General] humphrey74:
ähm,.... guys, is THAT normal?

# busybox chmod -R 777 /

Gives me a 'chmod: /: Read-only file system'

This is an issue I was wondering while try to use SuperOneKlick again and test, if I could get out of stuck system.

I tried some changing by clicking on 'unroot'. Log-output after all processing sais 'successfully mounted as read-only' .. or somethin like this...

is that correct??
[Galaxy S II General] flamingspaz:
It seems ok to me. I think you're kinda stuffed now, as I assume you have SuperOneClick stuck in this state too? So you can't send it back to Samsung.
[Galaxy S II General] MicioMax:
You must remount the filesystem in r/w mode before doing that.

If you dig into forums you'll find how... I don't remember the exact command now.

It's something like sudo mount -o remount,rw rootfs /

Anyways, did you get the file listings and mount points in your phone as I asked some posts ago ?
[Galaxy S II General] humphrey74:
what do you mean with 'you have SuperOneClick stuck in this state too'??

everytime I tried some stuff with superoneclick I saw in the log-output, that the programm mounts read/write and after doing some stuff it mounts filesystem back to Read-only
[Galaxy S II General] humphrey74:
Look @ my post from Today, 11:16 AM ;) there it is
[Galaxy S II General] flamingspaz:
Disregard that bit, I always get mixed up. :o
[Galaxy S II General] MicioMax:
Ok, seen it.... if you're brave enough (and have a backup of your data, just to be sure....) issue following commands, from inside terminal :

sudo mount -o remount,rw rootfs /

sudo rm -rf /cache

sudo rm -rf /data

sudo rm -rf /system

At some point you'll be not able anymore to do anything, I guess.... but doesn't matter. Then reboot, enter download mode, flash a stock firmware.

Max
[Galaxy S II General] humphrey74:
mh, I am on my phone via putty to sshdroid server now.

with "sudo mount ... " I get sudo not found

Do I have to use the terminal emulator and execute these commands directly on the phone?

Edit: aah, I see, you wrote "from inside terminal" ..sry :)
[Galaxy S II General] MicioMax:
Hmmmm.... sorry, used with ubuntu :-)

Just issue "su" command to enter superuser, then all what I wrote before without the "sudo".

Shell prompt should be "#" for superuser mode, not "$".

Btw, it should work from ssh too, of course.....

Max
[Galaxy S II General] humphrey74:
haaaa.... I have little problem to copy these folders as a backup

I use e.g. "cp -R /data/* /mnt/sdcard/*"

but on some files I get "operation not permitted"

su is active on ssh terminal