Details whether some of them matter or not:
Galaxy S3 (Sph-L710)
Virgin Mobile
CM12.1
Over the past couple days, I have been doing research on how to bring my phone back to it's factory firmware.
I tried a couple things, one of them ended up in being stuck on the Download mode, saying that the Firmware Upgrade was incomplete.
I managed to get out of it using a .tar on Odin to bring it back out. It worked. I was at my home screen. Everything was working beautifully. Honestly, I am still a nub when it comes to some of these things. So in that case I had no idea what I was doing.
Now, I have found the original firmware for my phone, and when I was getting ready to use it, I turned off my phone and rebooted it into Recovery mode.
Now when it starts up, it says "Recovery Mode" in the corner in little blue letters as it should.
And then it just goes to a blank black screen.... I have waited for probably 45 minutes, still nothing is happening.
I take out the battery, unplug it, all that jazz, and then reassemble it. And when I try to turn it on normally, just to get back to my home screen, it does the same thing.
I can't get it back to anything. I think something I did either erased or corrupted my recovery, and now it won't do anything.
Halp.
Related
as i mentioned a few days ago, i recently rooted some vibrants for a few of my friends.
one of them decided to switch me phones for a few days just to see if he liked my phone (g2) since he wants to upgrade anyways.
so i unlocked his vibrant using this hex editor method. worked like a charm. popped in my sim and at&t came up, all was well with the world.
i was going to do a nandroid backup of his phone so i used rommanager to boot into recovery.
that didn't happen.
his phone hung at the samsung vibrant screen. i figured no big deal, maybe just a hiccup. pulled the battery and attempted to start the phone again normally, but still stuck on vibrant. tried a few more reboots with no new results. next i booted the phone into download mode which worked just fine. dl mode came up normally and was recognized by odin. still feeling creative, i decided to pull the battery while it was in dl mode then undo the usb cable. put the battery back in, turned it on and voila! phone booted like normal!
i was pretty damn confused. i could get it to boot this way about 1 out of every 3 tries. i thought perhaps changing the nv_data.bin file was what screwed it up so i replaced the modified one with the original and re-locked his phone.
so the phone boots up normally, i go to rommanager, tell it to install clockwork recovery, wait for it to finish and attempt to reboot into recovery mode, this time through adb. the phone still got stuck on the vibrant screen BUT adb still recognized that the phone was attached AND in recovery mode.
still confused. i'm assuming perhaps the adb functionality was due to restoring the original nv_data.bin?
so i rebooted his phone via adb and it turned on like normal, told him not to turn the phone off. i was going to take it with me to work today, but we're generally busy on saturdays and i won't have time to mess with it. gonna take it monday and try some more stuff.
so long story short; unlocked phone, wouldn't reboot into recovery, just hung on vibrant screen. put phone in dl mode, pulled battery, attempted boot and it worked. relocked phone, reflashed cwm in rommanager, rebooted via adb, still hung on vibrant screen but recognized by adb.
anyone ever had anything similar to this happen?
This actually happened to me once. Bit once i odin'ed back to stock it fixed it and it never happened again.
I believe I'm running ICS Passion, I'm not sure what version
Last night I turned my Vibrant off. It wasn't anything special, just a boot because my messenger app wouldn't open. However, when I got home and tried to turn my phone back on the phone will take an unusually long time to get past the loader, and then the boot animation seems to run forever. I left it on overnight and my phone was not booted in the morning. The process seems to take up a lot of battery as well. I'd like to avoid flashing another rom because I haven't had preparation, but I need to update soon anyway so it's not completely out of the question. How can I attempt to fix this?
Odin back to stock
djquick said:
Odin back to stock
Click to expand...
Click to collapse
I figured I'd have to do this.
I used my home made jig to get into download mode (because the three button combo isn't working) however my computer is refusing to recognize the device when I open Odin. I'll try on my desktop when I get home, but for now I'm just going to let the phone boot and see what happens.
I'll post back if I still can't odin to stock.
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...
A couple days ago, within an hour of using my phone and everything seeming to be fine, my phone got stuck at the Galaxy Note II logo. Thinking that it locked up and reset itself or something like that while in my pocket, I pulled the battery because it didn't respond to the power button. after I replaced the battery and turned it on, it stopped at the same screen. After a few attempts, I tried to get into recovery mode and it only got to the download screen. After some research, it sounded like I could maybe flash the stock rom onto the phone and get back up and running. so I downloaded ODIN and found what I thought was the correct ROM and tried to flash it. ODIN gave an error about unable to find a PIT file, so more googleing later, I found a PIT file and tried again. ODIN tried for about 10 minutes and then failed. My phone was still on the download screen so I thought to just try the process completely from the start again. I unplugged my phone from the computer and tried to restart it, I think by holding the power button down but I may have just pulled the battery. once my phone turned off it hasn't turned back on again. It wont even attempt to charge when I plug it into the wall.
So I ask the people who are far more experienced with this kind of thing, did I unrecoverably mess up my phone, or is there something I can still do?
Hi guys,
first of all thank you for taking your time and reading through this. I'm not completely new to android, nor using fastboot and recovery. I flashed a few phones over the past years I even resurrected bricked ones. However I have no idea what is happening to my Honor 8. One thing to mention, it's the latest Nougat update, and a STOCK ROM.
It all started this afternoon. The phone suddenly reboot while using it. After that, the android screen came on, then Honor animation and.. freeze. Completely. I had to reboot using the long press method since it was stuck between the bootloader and the rom itself. It started up ok after that.
An hour passed, and while I was typing a message, it froze again. I could go back to home but the phone was really slow. After opening up Messenger again, it froze completely. Had to restart again with the long-press reboot method. It started up ok, entered the sim pin and upon entering the screenlock code it froze again, completely. Long-press reboot, again.
Since then, the phone won't boot. It gets stuck every time on "Honor powered by Android" for about a minute, then it reboots itself. I even got some weird green screen with a blue and a red rectangle, but that just stopped after a few reboots.
I mentioned that I know how to recover and fix stuff when something acts weirdly, but that's not the case, I can't do ANYTHING. No fastboot, no recovery, no button combinations, I can't even turn off the phone. It just keeps rebooting on and on, and yes, the battery will eventually die, but I have no access to any recovery options. I even tried dload but no luck.
It's still under warranty so I can send it back but I just rather fix it at home (without taking it apart), because I don't want to wait 3 weeks to get fixed. But it seems like that is the only option right now, I have never ever seen anything like this happen.
Any help or comment is appreciated. Even if it's not possible to do it at home (hardware issues?), I am really curious what can be the cause of this issue (damaged rom, filesystem permission issues?).
Thanks.