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,
I've got Lenovo s650, rooted with a custom rom (MIUI). All was perfect for weeks but few days ago it started randomly going off. Then I noticed that sometimes when I listen to music it crashes (making the music freeze and repeat same note for like 10secs) and shuts down. I thought it could be related to some apps but since I was very busy I didn't do anything about it.
Now today I noticed that my phone suddenly lost network coverage (in area where I always use it). I tried airplane mode on/off but didn't help, so I powered off and thought I will do hard reset when I get back home. However since then the phone is completely dead. Can't get into recovery, if I plug into USB nothing happens, if I take out the battery the red light turns and it goes to "META" mode for few secs (as it's intended to) but I can't download anything into it as I get some DRAM error in Upgrade /flash/ tool.
Funny thing that somehow I was trying all the combinations Volume up/down/both + power and at some point I randomly managed to turn it on so I was gonna make a backup of my stuff but it froze and shut down again. Now nothing works......
Any ideas what happened? :/
Some additional info:
I've got TWRP recovery (however I am unable to re-download it again via flashtool because of DRAM error).
I tried getting into adb but I am not sure if it's possible when the phone is off (tried volume button combinations with battery in and out but nothing).
Also when my phone is with battery and I put it into USB, pc recognizes it as "MTK USB Port", but it keeps disconnecting and reconnecting every 5 seconds. Tried to replace it with adb USB driver but didn't work.
Not having a phone I'll probably give a "Format all" option a shot in flash tool... either gonna brick it forever or fix it..
Edit1: Can't even format due to DRAM error....... :/
Edit2: This is so bizarre... I managed to connect my phone a couple of times in Mediatek preloader mode so the flash tool started flashing the rom, but stopped in a few mins unable to format something because it's protected.
I also managed to turn on the phone a couple of times and tried connecting via adb, but once I grant root permissions, adb shell on my pc cannot find device anymore.
It seems like either a hardware or kernel problem but I know nothing about either of them..
Edit3: I don't know how but I fixed it. Phone seems to be fine for now
Edit4: After 1 hour of working the phone died in exactly the same way.... And so this 6-week old phone will be going to rubbish bin. End of my blog.
i tried to upgrade my m9s pro to kodi 17 via apk file...when i tried to install the apk, the installation failed and my box froze...i waited for like 10-15 mins to see if it comes back to normal...but it remain froze...
I unplugged the power and plugged back in to restart it...and then the box was stuck at red light...BUT BUT BUT...after exactly 15 mins or so, the blue light used to turn on with m9s pro logo...and it remained stuck there...
I tried restarting it for few times but always at the start, it was stuck on red light...then after 15 mins blue light turned on n thn stuck on m9s logo...
I searched on the internet and read somewhere to hold the reset button while plugging in the power...i did that and i went into a screen with green android man and at the bottom there were commands like > formatting data, e: can't mount etc etc...
After those commands the box restarted and ever since, the box stays on red light and it does not shows the blue light even after 15 or 30 mins ...or even an hour....
i wished i would have tried flashing when it was on blue light....but now as it is stuck on red light...need to do something...
I am using the correct firmware - that i am sure...because the firmware mentioned on this firmware for this box, and the firmware my supplier sent is the same.
While flashing i get below errors, Do you have any idea regarding the below error,
[0x10105002]Romcode/Initialize DDR/Read initialize status/USB Control setup error
This error comes at 2% and when i only connect the box with laptop using usb...
And the below error comes when i connect both usb n power cord to box and then connect it to laptop,
uboot/disk intialize/send command/error result
This error comes at 7% when formatting is about to start...
I have tried on windows 7 & 10 laptop + pc....Used almost every version of usb burning tool...the usb cable i am using is 1 metre approx...
Any help will be appreciated....
Hey guys hope you're fine ^^
A friend of mine is having an issue with his phone so he asked me for help, and now i'm asking you lol
well the problem is that :
1- having a weird colored screen on startup (1st attached image)
2- after few second the phone just get stuck on boot animation (2nd attached image)
3- sometimes the phone goes into and update screen and then get stuck on 5% and after a while reboots (3rd attached image)
4- the phone just wont shut down it when i hold the power button the screen goes black, then instantly i feel a vibration and the multicolored screen comes back, then the same story "boot loop"
Well now let me tell you how this problem occurred, well my friend bought this phone from someone, so he doesn't know if there was custom recovery ever installed on this phone or if it's on stuck recovery
the phone was working fine, then one day an update notification pops up, he does the update, the first time it showed him an error message, but he tried one more time and it got throw the update process, unfortunately the phone got rebooted but never made it past the boot screen
now because the phone won't shut down, i can't get into fast boot or recovery mode (i don't know how to do that unless the phone is shut down, and doing the volume/power button combination)
i'm really stuck here and don't know what to do, i'd really appreciate your help guy
PS: sorry for the English, that was the best i could do
EDIT : i managed to get into fastboot mode,yeeeey! (see the 4th attachement)
how did you get into fastboot mode
i am not able to do it
When I woke up, my battery was at 0% and the phone was off. I charged it a bit and tried to turn it on and my phone was stuck at mi logo and wasn't doing anything (it wasn't bootloop just a freeze) I tried resetting it few times but it didn't help. I managed to boot to recovery and tried to reboot via every option (system,recovery etc) but the phone freezed just as i clicked reboot. I tried to flash lineage os .zip that I had on my phone but the flashing also freezed and I had to reboot manually. Now I can't turn on my phone at all, I charged it whole night with different cables, it is constantly blinking red light when charging.
Now I'm trying to use miflash 2018.11.15.0 which after installing qualcomm driver recognizes my device (Qualcomm HS-USB QDLoader 9008 (COM4) in device manager).
I downloaded mido_global_images_V11.0.2.0.NCFMIXM_20191107.0000.00_7.0_global_91ed4d2a3f .tgz and I clicked flash
File prog_emmc_firehose_8953_ddr.mbn flashes successfully then the status gets changed to ping target via firehose for 15 seconds and I'm getting write time out,maybe device was disconnected. I have tried different methods, unplugged screen connector, battery, testpoint and held the power for like 30 seconds but I cannot fully flash at all. Any ideas?