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
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...
Md5s checked out. Wiped dalvik/user data/ factory reset. Flashed with CWM (though i understand this is not preferred). Goes through full AROMA but reboots into recovery every time. After about an hour in recover reboots to a screen with a yellow triangle exclamation point and says, "System software not authorized by Verizon Wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help." In the top left it says in red, "SECURE FAIL: KERNEL". Now can't even boot into recovery at all when press power+volume up --> it boots to custom with blue recovery in top left, then shuts down and goes to the above verizon error. I'm coming from 4.4.4. Any assistance greatly appreciated. Thanks a lot.
Looks like the download link from the 5.0 dev thread points to a i9505 version on romhut. should it not be for sch-1545?
http://forum.xda-developers.com/showthread.php?t=2643031
Hi Guys
This tablet is showing the android guy belly up with a red warning sign and a "No command " message. I try recovery mode/factory reset
1. recovery mode from back up (no sd card w/backup
2. factory reset (data wipe completed) then, at reboot same "No command" screen.
Any options to make this tablet work again?
Hi
I have a trouble if you can help.
I have SM-J701F mobile model. when ever I updated it, the process in recovery installing system update goes to 32 percent and then shows erasing and phone restarts and then Android pic appears with "No command" and every thing stop here. after a period of time it goes to black screen.
Any option I tried to execute in black screen like wipe/cache or other options, it says "e misc partition could not find" even turn off or reboot failed and "e misc partition could not find" appears .
I 'd like to mention that When I used odin tool to install my firmware model to my phone at first try I chose CSC firmware file instead of Home CSC file. Then I tried to repeat the firmware installing process again but with choosing Home CSC file this time. but the problem remains.
How I could solve this problem ? and what is the reason for that ?