[Q] "Andoid is upgrading" Screen was looping and now is virtually unresponsive
I attempted to put Cyanogenmod 10 on my SGH-I747 but as soon as it tried to load the Cyanogenmod 10 loading logo kept looping. With the rest of the phone unusable at this point I wiped the cache then the whole phone. I used Odin 3.07 to flash the stock firmware back and it passes each time. My problem is at the "android is upgrading" screen with the loading wheel after it loads all of my 90 apps. After the first time I popped the battery out after 20 minutes and tried flashing a different file, thinking that was the problem.
I was been stuck here for 30 min+ and I was starting to get worried but then I tried to install it a third time and now the phone will only take me to the Clockworkmod screen or the download screen and can still be recognized by my PC by sound when I plug it it, but I can't find it. It will not turn on though and when I try it flashes the Galaxy S and Samsung symbol then goes black. I've searched all over for a solution but can't find one. Please someone help me fix this, I know someone's been through this before. What should I do? Is my phone unrepairable?
Related
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...
i rooted my device and flashed a nightly build of CM 10.1. it was too glitchy for me and i saw a build that i liked more ( google editionv2) but when i tried to flash that from TWRP it would just stay on the bootloader or the GS4 screen forever. getting nervous i decided to try to fix it by flashing a .md5 fix from odin. i watched this video /watch?v=bxNPHKKpvtQ and did all the steps correctly and odin even said it passed but when i try to boot it up it goes to the GS4 screen for about 2 seconds and then turns off. and i cant even get into a twrp anymore! Is my phone dead or is this fixable ?!?!? :crying: PLEASE ANYTHING WILL HELP thank you. and i am not the most experienced with all this stuff but i know a little more than the basics so explanations in detail would be nice
Edit: when I run it in Odin and use the file provided in the video it seems to get out of the boot loader while connected and goes to the android screen with the blue square in the middle, then it goes to the Samsung logo video but then right when it seems it will work Odin says the device has been disconnected and then my s4 goes to a battery charging screen. And then Odin says it passed, but when I try to boot it up it goes to the boot loader for half a second then turns off. Did I brick my phone ?
I'm using the Samsung Galaxy 10.1 Tab (Verizon) SCH-i905
From what I have read, the reboot loop is when the user sees the boot screen, but the tablet keeps on rebooting. My problem is severely worse.
My tablet keeps on reboots, but it doesn't show the boot screen. Instead, it just shows a blank lit up screen.
Not only that, but I cannot always turn on my tablet. I keep trying, but it typically turns on after I keep plugging and unplugging the USB from my outlet to computer, and so forth (for about 10 minutes). When it finally boots, I can go into Odin mode. I flash some sort of firmware to it, and then my device turns off. And I need to keep attempting to turn it on again for 10 minutes before it actually turns on.
Nevertheless, my device still does not work properly. I know this is infact a software problem because my device was working fine yesterday, until I decided to unmount and mount certain things in Recovery mode.
So far, I have flashed recovery.tar.md5 , PDA_SIGNED_P7105.tar, and 75XX_CWM_Recovery_v5.1.2.6.tar. None of these have fixed the problem. How can I return to factory settings?
I just saw the previous thread about this device and am currently installing PDA_HC31_EG0 ... If everything goes right, then there should be no problem. But I highly suspect that the firmware will flash successfully, and then my device will proceed to power off for another 10-15 minutes before turning on again.
If I leave my device plugged into the power source, it will start turning on and off (the blank lit screen) periodically. For example, turns on for 5 seconds, then turns off for 5 seconds (and repeat).
While this is a software problem, it seems to be on the OS level. Are there any other ROM Links besides the ROM in showthread.php?t=1342995 that I should try? Also, is there any other possible alternative?
Ok, so one night I was using my phone normally (Browsing. Watching YouTube, Playing Games) like everyone else does. Then all of a sudden it shuts off, but immediately turns on again without me pressing a button. (So basically it suddenly auto restarts on its own) This occured maybe 2-4 times (all in one night) until one time, it shuts off but doesn't turn on again (basically an automatic shutdown), so I tried turning it on again (Power button), then I got shocked because all of a sudden it enters a boot loop (Screen displaying this sequence : Samsung Galaxy S4 screen, my carrier logo screen, The encrypted screen (where you have to enter your encryption password) then again the Samsung logo but this time with the colors splashing from the background, then it shuts off again.) Sometimes after the boot loop sequence, it vibrates but never turns on again, sometimes it just turns off after the sequence. And as I try and try to get away from the boot loop, the sequence became shorter. So I'm guessing it's a battery problem, BUT my battery isn't bloated or deformed. I tried clearing the cache first, again the sequence got shorter (never going up to the carrier logo screen), then I tried formatting the data, still to no avail. Now, when I turn it on, It shows the Samsung logo screen for 2 seconds and shuts down.
I tried flashing it with ODIN thru Download mode BUT (HERE'S where another problem occured) :
My phone never get pass on the system.img.ext4 dialogue and my screen just goes blank. But ODIN still recognizes my phone. And when I remove the USB cable, ODIN says FAIL.
I'm sure the cable is working. I downloaded the firmware for my carrier (Tre 3).
What could be the real problem here?
Here is the description of my device :
Samsung Galaxy GT-I9505
Bought from Italy, Tre 3 carrier
Can I download a different region/carrier for my I9505 phone?
Advanced thanks for anyone who comments and I'm very sorry for my English. Thanks!
I would install TWRP recovery, boot to it, and use it to format data, which will remove the encryption. Then I would either push a rom to the phone via recovery or try to reinstall the stock firmware with Odin. Make sure that you run Odin as admin as well. The firmware must be the same version or newer. If you still have the stock recovery and can boot to it, then I think the build number of the currently installed firmware will be visible there. You should be able to use that to Google the correct version you need.
Hey it's me. Just posting a quick reply.
Thanks for replying to my post. Yesterday I successfully flash a rom to my GT-I9505 (Version 5.0.1 Italy HUI 3G). However it still didn't boot up. At first try it booted up to the first setup screen then just randomly shuts down. Then as I try to boot it up again, It just shuts down after the first Samsung logo (with the GT-I9505 logo), I can't boot into recovery cause it shuts down. I'm sure it's not a battery issue cause when I boot into download mode, it can stay in that screen for like 10 minutes. What could be the issue? I'm planning to disassemble my S4 sooner to see if something's wrong inside. Thanks again for the reply
Hi all,
To get right to the point, my phone doesn't switch on, and I cannot get into recovery/download mode.
The story:
After my apps kept on crashing for no reason, I restarted the phone. After the restart, when it asked my pin, the google app kept on crashing and the phone completely froze up.
Here is where I suspect I made a HUGE mistake. I Took out the battery and started up the phone again. It immediately told me that the system is corrupt and "cannot be trusted".
I continue the boot process, only to land in a boot loop. I take out the battery once again and restart the phone.
After displaying the LG logo, it just turned off. And that was the last time I could get it on.
I tried booting into recovery, but the phone won't even switch on to begin with.
Absolutely no response. Screen stays pitch black.
I tried doing it with the USB cable in, same result. Nothing.
I also read up on the different combinations to get into download mode to no avail.
Stock ROM and firmware installed, no mods whatsoever.
Android 8.0
Can anyone please suggest anything I can do to save my device?