So I was trying to revert back to Cyanogen from Oxygen OS and I don't know what exactly happened but I think I soft bricked my phone. I think I messed it up when I was in recovery mode before and I decided to try to install Cyanagen in the recovery mode. Now my phone can only go into fast boot mode and it wont go into recovery mode. All it does in recovery is constantly reboots itself until you let go of the buttons and then it gets stuck on the regular rebooting screen. I have no idea what to do now at this stage and pretty much have zero experience is stuff like this. Please can someone help me fix my phone. I'm honestly so scared that I bricked my phone. I've been trying to fix this for hours and I cant seem to figure it out.
Related
My sister said she spilled a little water on the screen of her phone the other day and it started boot looping.
Ive been trying to reflash it, but there are some issues...
If the phone is plugged in, it will cycle the charging battery on and off... unable to get into download or recovery.
If its not, it used to show the galaxy boot screen and turn on and off... now it just stays frozen on that screen. In either instance i was unable to get into recovery or download mode.
I got into recovery a couple of times when it actually booted the ROM, but everytime i would use the power button to try to make a selection the phone would just reboot and go into a cycle again.
I also got it into download mode once through the ROM but it cant get the ROM to boot anymore...
I might be able to get it into recovery but when i do it just reboots when i select anything.
and help would be awesome
thanks.
OH, when i actually got the ROM to boot it would throw an array of system errors and force closes. I also think the water had nothing to do with it and something she did after the water is what started causing the problems
I got recovery and i flashed a new kernal and ROM and erased everything and its still freezing at first Galaxy boot screen.
probably because the phone is water damaged?
See if the guide in the second link of my signature will help.
Thanks ill give it a shot.
But a major problem is that i am unable to get it to boot into download mode.
So i got CWM to boot, and i reflashed the kernal and ROM, with no luck.
CWM read catch error. Unable to mount... format... ect...
From what ive been reading the internal catch is fried....
Anyone have a motherboard they want to ship me? LOL :laugh:
Thanks lumin30, I finally found a way to get the phone into download mode. (take the battery out, Put it back in, hold buttons, plug USB in, press power button) after a few reboots it would finally go.
I followed the link and got it back to stock and it booted. Now letting it sit to settle in and hopefully it will be functional again.
This thread can be deleted! :good:
Hello I am searching for help. The problem is that my galaxy s2 i9100 stopped working properly. It started like this maybe I took out the battery or something I don't remember and then I turned it on the phone wouldn't boot. I thought maybe my android operation system got bricked so I decided to re flash it but as I can remember the phone wouldn't go in to download mode but some how I managed to reflash the firmware but then phone booted it just froze and then I pressed lock button the phone screen would go black and reboot. After installing cyanogen mode 11 the phone would boot and it could be used again until pressed the lock button it would go black and reboot so I have been reading forums and found problems like boot loop corrupted mmc or something else corrupted and I don't know what the real problem is because the symptoms are like boot loop or corrupted mmc or soft brick. I have already tried other kernels other android versions clock work mode
migimantas said:
Hello I am searching for help. The problem is that my galaxy s2 i9100 stopped working properly. It started like this maybe I took out the battery or something I don't remember and then I turned it on the phone wouldn't boot. I thought maybe my android operation system got bricked so I decided to re flash it but as I can remember the phone wouldn't go in to download mode but some how I managed to reflash the firmware but then phone booted it just froze and then I pressed lock button the phone screen would go black and reboot. After installing cyanogen mode 11 the phone would boot and it could be used again until pressed the lock button it would go black and reboot so I have been reading forums and found problems like boot loop corrupted mmc or something else corrupted and I don't know what the real problem is because the symptoms are like boot loop or corrupted mmc or soft brick. I have already tried other kernels other android versions clock work mode
Click to expand...
Click to collapse
I have found that my emmc has the insane chip bug. The phone boots normally with cyanogen mode 11 but then it goes to sleep mode or I press the power button the screen goes black and the phone restarts. I have tried siyah kernel to try dual boot but then I flash siyah I cant get into recovery.
I think you should flash latest STOCK ROM with Odin, and then follow available custom rom instructions on xda...
Test if the stock rom will work for you, boot your phone etc... Try to use it a few days. If everything is OK, proceed with
further procedures...
twinsen.net said:
I think you should flash latest STOCK ROM with Odin, and then follow available custom rom instructions on xda...
Test if the stock rom will work for you, boot your phone etc... Try to use it a few days. If everything is OK, proceed with
further procedures...
Click to expand...
Click to collapse
I have already tried this but with the stock rom phone boots but at the section where I have to chose language I jus freezes stops working
So I think it is a hardware problem. Phone on stock rom shouldn't freeze on language selection. Something is wrong. If you are on warranty, let them fix it for you, if you are not, try to fix it in some phone repair point. I'm sure you can stop your attempts. It will not be better for now.
twinsen.net said:
So I think it is a hardware problem. Phone on stock rom shouldn't freeze on language selection. Something is wrong. If you are on warranty, let them fix it for you, if you are not, try to fix it in some phone repair point. I'm sure you can stop your attempts. It will not be better for now.
Click to expand...
Click to collapse
Take it straight away to the official service centre
Hello I'm a user of a Sky Vega Iron (IM-A870)
And I need desperate help.
It's not an ordinary boot loop I wish it was, here's the story.
I rooted my phone just to let you know.
So I installed the wrong version of cwd recovery on my phone and so when I go into recovery mode the screen will turn like this.
imgurDOTcom/iOFieHG (sorry I can't you links yet cause I'm new)
But it wasn't a big deal I just didn't use it.
Now is the deal I decided to update my phone to stock kitkat that the vega devs supported themselves with vega station(the stock updating app)
And when it started installing it suddenly went into cwm.
I wasn't that worried at the moment just tried pulling the battery out and rebooting but...it started a boot loop.
I can't navigate cwm because of the way it is and I'm stuck. Is there another way to factory reset? or to get out of the loop?
Maybe a way to get rid of cwm and get back to stock recovery mode? Please help I need help until tomorrow! (personal reasons)
I searched online hours for solutions yet I can't find one.
Please help. I'm begging anyone out there.
Thank You
Appears you have already been helped here...http://forum.xda-developers.com/general/help/help-fast-boot-loop-vega-iron-normal-t2836120
Here goes: I was a happy OPO user using the latest crDroid ROM and AK kernel, when suddenly my phone entered the sleep of death. I turned it off and back on, and since then it is in an eternal boot loop, never going beyond the Oneplus logo.
I am able to get into fastboot mode as well as recovery mode (I am using Philz Recovery), however, here is where it gets weird. I was hoping to just flash another ROM from the recovery and fix the problem, but all my files and folders on the SD card are gone, almost as if the chip died.
I also tried flashing a different ROM using ADB, to no avail. ADB shows "OK" but nothing sticks. All I can successfully flash are the boot logo and the recovery. The phone never gets beyond the logo before it reboots.
Does anyone have an idea what else I could try? I feel like sending it back for a replacement, but I am afraid that this will take forever.
Do you have a OTG USB stick ? Maybe you can flash from there.
I was able to get my phone to boot using this:
http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061
All data is gone though. But at least I don't have a brick any more.
I have a t-mobile (snapdragon processor) s7 that this morning when it was charging, it must have reset or something and the logo is all i can see now. I believe it's stuck in a boot loop. When i try to go to recovery mode, it gets stuck in a recovery boot loop as well. The only thing i've really been able to do is put it in download mode, and i've tried several times to flash it, to no avail. I have a crack on the back of the device, so they consider the warranty voided even though it's been like that for a year almost. Is there anything else i should try before i pay off the phone "lease" and upgrade again? Any tricks i don't know about?