Soo... I have a S2 and S3. I use the S2, today I woke up for my phone freezing on Samsung Logo. I tried booting Recovery, froze on Team Win logo, so I guessed that something is the software went wrong. I decided to flash some Recovery from Odin and boot into Recovery. I Googled, downloaded one recovery, flashed it via Odin, didn't work, tried another one, didn't work, I would put out the battery every time between tries. And boom it wont turn on, only gets warm in the camera region. So I tried all the combinations of putting it the power with and without battery, pushing all the button combinations etc. I told myself I'll deal with it later, need a phone right now. So I used a spare phone my brother game me, an S3. It had a stock ROM and I wanted to flash JB on it. I rooted the S3, downloaded TWRP for Odin, flashed it with Odin, it didn't work, it booted me to a stock recovery, so I rebooted the phone, it went to Samsung logo, I removed the battery to go faster to Download Mode and try something else, and it wont turn on. What happened and what can I do to fix that? I really need a phone for tomorrow. Please help.
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.
My friends I9100 has a strange problem: It does boot, but shuts down after first Samsung boot logo. It boots to recovery and download mode, but when I try to flash something (or take backup) in recovery, it shuts down. With Odin, I can flash firmwares normally, but those does same, wont boot. I tried Odin-flashable CM9, latest NEE official, and (first?) JB-leak firmwares.
He says that phone just shutted down right after he opened Facebook, and never booted after that. He was using CM10.2.
What should I try next?
EDIT: Never mind. Problem was battery, tried my own I9100's battery in friends phone, and it worked, also his battery didn't work with my phone.
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?
Hey everyone! Big problem..
I have installed CM12, Android 5.1 it's been all fine up until now, I was planning on selling the phone, so I factory reset it, that went well until it tried to turn itself back on afterwards.
My Samsung Galaxy S3 i9300t is stuck in a bootloop. I can not do absolutely anything.
I've tried taking the battery out, holding the three buttons, putting it back in, doing that with a USB, As soon as I turn it on, holding buttons or not it goes straight into a bootloop. I can't use odin to install the custom firmware again as I can't get into recovery or download mode or anything, once it's in the boot loop it stays there..
Any help is appreciated.
Bump?
Hi guys, I have a samsung galaxy j600fn/ds, tryed to flash twrp, something went wrong and now I'm locked on the ''Samsung'' logo screen
I guess it is brick, though I'm totally stuck at the screen, the phone won't even turn off, so I don't know how to acces download mode to install stock firmware.. anyone can be of help?
EDIT: solved.. of course the solution was just to wait for the battery to be completley depleted, I just got scared there not beeing able to do anything
Wait-
So you just let your phone in bootloop all night (?), then you charge it without turning it on,
waited till 30%, and then you put it in download mode and installed the firmwere?
Does it really work? 'cause I tried to do that before, and the bootloop stopped. I tought I ended up into an hard brick.
I pressed powen and tried to put the phone into download mode, but nothing.
I put the usb on my pc, and odin was actually reading it, so I tried again and again to get into the download mode.
Afret 30 minutes, i pressed power again, (and finally) the boorloop restarted.
Well um.. the phone now is probably at 60%.. I hope it wont stop again, and I hope this method will work.