Hi guys,
little bit of background on the phone, had it since new close to 2 years away (2 year contract and im 7weeks from an upgrade) the phone is on orange (well EE now)
Basically when I turn my phone on it is stuck in a force close loop, with loads of different messages appearing, such as;
(process com.sec.android.provider.logsprovider)
calenders, messaging etc etc
So I have tried going into the boot mode, by pressing volume up, home screen and the power button.
Then when I try to reboot it comes up with the error messages;
e:error in /data/log/recovery_log.txt (read-only file system)
(read-only file system)
e:copy_kernel_file :: Can't Open /data/log/recovery_kernel_log.txt
Rebooting...
It then just continues onto the normal home screen, then when I enter my swipe code it comes up with the force close loop again.
Any solutions to this problem, Or will I have to factory restore, or is completly broken? Im not due an upgrade for about 7weeks either
Would rather not have to factory restore if possible as I have some files on there I dont want to loose, but if its unhelpable so be it
Thanks in advance guys!
Cheeky little bump, Anyone know a fix to this?
Have similar problem...
I believe a factory reset will fix it...sorry to hear you losing files though..
I have a similar problem. I should probably make a new thread for this though...
Background: Samsung Galaxy SII 1900 bought October 2011. Yesterday flashed a stock ROM for the phone and everything was working perfectly. This is probably not related but have been trying to install a working version of Android Keyboard which has gesture typing working for other languages than English, German, Spanish and French and so some hours before this happened I tried to flash a zip with that but it turned up "e: signature verification failed" so I pretty much gave it up and the phone was still working. Then I decided to install another recovery mode on the phone cause that should allow me to install without verification. So I downloaded the one for SGS2 at clockworkmod com rommanager and put it in on the SD card. Then I shut down the phone and this is the weird part: First I accidentally pressed the power button first so I realised the phone was gonna boot normall so I pressed the power button again to force shut it down. I pressed for quite a long time and then it just restarted and I'm at a boot loop where it says Samsung Galaxy S II with white text on black background.... Then suddenly after removing the battery and trying start several times it booted normally. So I just continued where I left off going to make a backup in Titanium Backup before flashing CWM and suddenly the phone just restarted and I got into the boot loop again. I am able to enter Download mode and Recovery mode but the phone no longer starts. Been trying like 30 times to restart it... Now when I entered Recovery mode just now I got the error message
"E:Error in /data/recovery_kernel_log.txt(Read-only file system)" in red letters... and that's where I'm at now.
Here's a sitty picture of it from my HP Chromebook webcam ******* (Google Drive) Edit: Not allowed to post links in first 10 posts
Related
Ok,I tried to install a different OS, on my phone via ODIN, i couldnt get it right the first couple of times so i kept doing more research. SO after i THOUGHT i had a solution i tried again. i was on the last step of the finalization and it said " about two minutes left" or something like that, and i waited about 40 minutes and it still said the same thing. so i thought i'd UNPLUG IT AND TRY AGAIN. well now after i do so,
i try to plug my device in again and it doesn't read it at all, This ALL HAPPENED AFTER THE PHONE ENCOUNTERED THE FIRMWARE PROBLEM WITH THE PHONE... WARNING SIGN... AND COMPUTER.
the only thing i was able to do was go to recovery mode, or download mode. CAN NOT GET INTO THE PHONE. now i'm smart enough to click an option on the recovery menu, but my power button or home button, or ANY Button, would not respond, besides the volume buttons to go up and down. So since the computer will not detect it, i dont know what to do, and i am using the factory cables, and i tried KIES AND ODIN. I have uninstalled drives in and out. still no solution, i read posts ever since last morning until now and decided to create my own posts for my own problems and seek help from people like ones on here who ACTUALLY KNOW WHAT THEY ARE DOING.
it starts up as Samsung GT-i9100 and they goes to Android System Recovery <3e>
and below reads in yellow,
Deleting Cryptoin Meta Data
--Copying media files...
Successfully copied meida files.
# MANUAL MODE #
--Updating application...
Successfully updated application.
--Appling Multi-CSC...
Successfully applied multi-CSC.
and shows and android robot with a white triangle and Orange ! mark in the middle.
The crazy thing about it is that i could use a button as an (Enter key) before i tried to flash my phone , before that i just cleaned the memory,
and once again after i removed phone from ODIN at about 98% im guessing, after i waited 40 minutes when it said about 2 minutes remaining. i was not able to try any other solution or connect to my laptop. and ive tried others, and my other phone connects fine. so i know i did something wrong....
Please Assist me, i'd really appreciate the time and effort,
Hello all,
I am merely posting here if anyone has a better insight or idea, since I haven't followed with all issues regarding the Galaxy S II International version.
I have purchased mine from one of my country's carrier nearly 2 years ago. I have in the course of these 2 years, rooted it, flashed CyanogenMod, and happily updated it every so often. I always used nightlies, updating almost everyday.
In the last 2 months, it had become sometimes very sluggish, frequent slowdowns, and many lockups, freezing, and some random reboots. I was getting a little tired of it, but was getting used to it.
Yesterday, I was using it normally, when a slowdown started. The app (was 3D game) got unresponsive, but I could still pull the notification drawer, so it wasn't frozen. I pulled and pushed the drawer about 2 times, and then it also stopped responding. The screen was on, touchlights were on, and since I had seen it before, I pressed the power button for a reset.
Then the first boot screen, with the yellow triangle (where it says Samsung Galaxy S II GT-I9100) appeared, but it got stuck there and didn't get past, apparently frozen.
I tried a quick more reboots, and then tried (with very difficulty) entering CWM recovery. I got eventually there, and CWM was working as it should. I considered wiping the cache, or just reinstalling the last nightly I had saved, but decided first to just press "reboot system now".
It also got stuck on the yellow triangle initial screen. This time I couldn't get to the CWM recovery (it seems there was a very small time frame to it to enter before it actually restarted again from long pressing the power button). In a dark room, I noticed that even when the yellow triangle screen was black, the display was on, the backlight was on. The black was bright, and if I pressed the powerbutton for a reset, I could see the screen actually turning off and then on again, and going back to the yellow triangle screen.
I tried to go into Odin recovery, and eventually made it there.... So I pressed to restart the phone, and it continued frozen on the yellow triangle.
I went home with the screen frozen (I couldn't power it off, and I didn't remove the battery). I noticed that after some minutes it restarted, the screen went black and again to the frozen yellow triangle.
I managed to get to CWM recovery after several attempts with the 3 button press, but a different error had appeared: E: Can't mount /cache/recovery/command (or something like it)
So I got home, downloaded codeworkx CWM recovery, put the S2 in Odin recovery, and using Heimdall uploaded it. It completed successfully.
I managed after several tries to get to CWM recovery, it opened again, but more "Can't mount messages" appeared, system_log and such, as I have seen on some forums, and that by then I never had. Read somewhere that probably the system partition got corrupted.
Then this time I reinstalled from the internal memory another nightly I had. I was with June 19, and used the June 16 one. It flashed successfully.
Then I pressed reboot system now, but still got stuck at the yellow triangle screen. And again the message "Can't mount /cache/recovery/command".
So I got into Odin recovery mode (volume down) and using Heimdall again uploaded CWM recovery. But Heimdall got stuck at "Loading KERNEL 100%" It reached 100% but never exited. And the bluebar that was supposed to appear on the S2 screen (that appeared the first time I flashed CWM), didn't appear.
Since it got stuck there for a while, I Ctrl-C'ed my way out of Heimdall, and pressed the power putton on the S2 for another reset.
But this time, it never woke up again. No more yellow triangle screen. No more "active bright black screen". Nothing.
And it doesn't charge even when plugged to the charger.
I am reading about SGS2 that won't turn on and won't charge. It seems a general agreement that Samsung assistance tells us it's a motherboard failure, and should be replaced (and at least here in my place it's helluva expensive).
Since many cases the phone just went dead, mine wasn't quite the case, since it was somewhat alive in the yellow triangle and apparently I could have f*cked up when I Ctrl+C'ed Heimdall and turned off the phone when Odin recovery clearly states "Do not turn off target !!", even though when the flash goes ok, you have to reset it.
Two questions:
1. Is there anything else that can I do to revive it?
2. Can I recover at least the pictures and videos I had saved on the internal memory? I had a ton of pictures and videos inside DCIM/Camera, where for a long time CM10.1 camera could only save pictures to the Internal memory, and when a nightly fixed it, I kept it in internal memory.
If anyone got this far since I was exhaustingly detailed, thank you for your attention!
Unpluging was the bad move that killed your phone. Can try a jig
andrewwright said:
Unpluging was the bad move that killed your phone. Can try I jig
Click to expand...
Click to collapse
Well I had just done the same process, and it was quick. There was no waiting period after the 100%, and Heimdall exited cleanly.
The last time it got stuck in 100% for about 30 seconds, and I decided to abort with a Ctrl+C, unplugged and restart...
Hi everyone, I have this weird problem with my S6500, or rather my younger brother has.
He tried to put on his S6500 (not D, this phone is with NFC) Cyanogenmod 10.1, after some ups and downs, he finally got it to work, but... camera wasn't working, it was said on the cyanogenmod page to flash with the newest update, he did that, phone worked good... almost, after he was blocking his screen, he couldn't unlock it, because there was some kind of white screen stuff, weirder was the thing, that he could hear all the *clicking* sounds as he was trying to unlock. He had to restart the phone every time after he blocked the screen, so he wanted the phone to function normally and tried to put his stock ROM back again. Well the flashing went well (as Odin showed) but the phone stucked in bootloop.
The phone showed the Orange logo (he is using his original stock rom from Orange Poland, downloaded from sammymobile) and then it quickly changed to Samsung logo, after that the phone vibrates once, and after that it vibrates 3 times really fast and restarts from the Orange logo.
He tried to get into Recovery mode, but coul;dn't (the phone doesn't react to any of the combinations we found - vol+,vol-, home and power and many others), and as I forgot to mention before, after every flash (while the recovery was working) he cleared data in menu of the recovery.
We also tried the different method to boot the phone into recovery mode (put it in Download mode, which works and then instead of going further by pressing vol+ we pressed the down button and held vol+,vol- and home button, but instead of going into recovery the phone booted in weird screen with small letters RAMDUMP MODE (ARM9 mode).
We tried several times to flash new recovery with Odin, but it doesnt work, the PIT file also doesn't work, or can someone provide me with the stock s6500 PIT file as I couldn't find one, because I read in the Polish forum, that screen mentioned before only shows up if there is a SuperUser app in the phone, so we need the PIT file to flush it.
So the problem is after flashing it with numerous cwm and original stock roms we couldn't get it to boot or to get into recovery menu, or get it working.
Also the hardware is all ok, as the phone is almost brand-new ( he got it from the Orange few months ago).
So help plz?
I have the very SAME problem with my S6500D. Same as described above.
Anyone has managed to fix this problem ? I have all needed tools.
Hello,
I have a big problem with the I9300 from my mother-of-law.
Her Galaxy is neither modified, nor rooted or anything. So it's stilll stock.
Now her I9300 won't boot correctly anymore.
When she starts it, it lasts much longer than normal to boot. When unlocking, an error message pops up immediately "Application Installer stopped" (angehalten), when clicking ok, it comes another time then it reboots completely.
When going into "Android system recovery" and wiping data/factory reset, there still comes an error message when I reboot (error) and the same procedure appears.
> It lasts a long time to boot > after unlocking the error message appears (Application installer stopped and it reboots immediately).
Does anyone have an idea what the issue might be and what I could do?
Flash a new Rom?
(P.S. sometimes it doesn't start at all an just shuts down and the battery is empty - even though it was still 77%).
Edit:
Sorry, I made a data / f factory reset another time and now it finally seems to work, unfortunately with all datas erased..
You should flash newest firmware for your country via Odin and it should work correctly
Greetings,
My device is probably about three years old, I was totally satisfied until I noticed sudden change in my phone's performance about three months ago, way too laggy even after doing factory resets and etc.. , battery was being sucked faster than it supposed (even with a new battery), heating up whenever it decides to, not being able to handle hardcore-use which it could handle in the past... etc.
So, I took all that as a sign that my phone needs to be replaced. Last night while I was on my pc and the phone was sitting in front of me, I caught the phone restarting by it's own. I noticed this happening frequently over the past few months, and usually nothing wrong happens, although I had to remove the SD card once.
But this time its a whole different issue, the phone was stuck on "Samsung galaxy s III .. blah blah" , pressing the power button wouldn't turn off the phone and it would turn itself on the moment I put back the battery. I surfed the web for info and found topics that called this "stuck power button issue" and they suggested to smack the power button with battery or smack the phone itself (without holding any grudge against the phone ). I did that and it fixed the issue of the phone turning itself on.
At this point I found out the next issue, the OS won't boot & i would still be stuck at "Samsung galaxy s III ..." screen. So I tried to boot into CWM (Power+Home+Vol Up) but it would loop me back to the same screen 'till death >_>
Then I checked if I could enter download mode and it was a success, afterwards I downloaded a stock .md5 for my phone (and specified country), Loaded it to odin and tried to flash using that, and it failed on me ... check the pic below if you wanna see the error massages
(add http)
postimg.org/image/dz0c0mu8l/
FAIL !! I tried it twice, I can't think of what to do anymore ... Being able to access BBM (I got a habit of making notes there) & Contacts (I am not sure if superbackup was being a good boy and made backups everyday) would be nice .. But I don't think it's gonna happen ... All I really care about is being able to recover everything from my Internal storage, I don't care if the phone becomes unusable or whatever.. I just need the internal storage.
+ My phone is rooted, I have some nandroid backups and the Rom I was using was Android Revolution HD
Update 12/10
I messed around with the phone, and found out that I can still get in cwm, but I keep getting stuck with "can't mount cache/recovery/..." "can't open cache/recovery/..."error
Since the phone is three years old the battery could be the culprit. Try with your friends battery to see if the phone is booting properly. Still if your phone stucks in boot loop then repalce your power button.
I faced similar issue. My phone went into bootloop even when in recovery. It would reboot while OS installation is in progress. Weird. Rebooting while in recovery could damage the recovery itself and next time it wont even boot into recovery.
mpadhu said:
Since the phone is three years old the battery could be the culprit. Try with your friends battery to see if the phone is booting properly. Still if your phone stucks in boot loop then repalce your power button.
I faced similar issue. My phone went into bootloop even when in recovery. It would reboot while OS installation is in progress. Weird. Rebooting while in recovery could damage the recovery itself and next time it wont even boot into recovery.
Click to expand...
Click to collapse
thank god someone replied, I thought nobody would respond so I gave up on xda .. anyways I just updated my post.
I am positive that the issue is not the battery, since it's new and i did try the older one and nothing changed. I still get stuck at the same screen x_X