I think have bricked my Infuse! This is what happened:
I have been flexing different custom rom on my infuse 4g and the last one I flashed was AEON v1.4SL rom (so lovely:good. Now, am trying to go back to stock and I flashed this "SGH-I997_I997UCLB3_UC_ATT" through Odin but my infuse will always boot into stock recovery but the problem was fixed by flashing this "GTGs_Ultimate_Unbrick" and another problem arose; the phone will boot, and some messages will come up saying "com.google... is not responding, force close(button), Twh Launcher is not responding, force close(button) and so many pop up like that. At the same time, the phone back light will goes off and come on again and again with the "force close" messages. I flashed different stock roms like "I997UCKI4" "GTGs_Ultimate_Unbrick " SGH-I997_I997UCLB3_UC_ATT" again and again thinking its gonna fix the problem but still the same. I also flashed "ODIN-Entropy_DD-GB-zImage" Red recovery on Gingerbread stock rom, flashed custom rom through the red recovery and the custom rom would never boot finish but vibrate (sign of booting almost done!) with a dim back light and remain there forever.
I just hope someone could help me!
Am so sorry the long story. Thanks in advance.
Related
Hey guys,
So my battery died earlier and I tried to turn on my epic and it started boot looping so I let it charge for a little bit and turned it on while it was plugged in and it acted like i had just flashed a new rom, so I went through the "touch the android screen" and now everything just force closes constantly. All I get is a black screen with FC msgs popping up. I managed to reboot it and it's still doing it. I'm running an Epic with 2.2 rooted with ViperRom Apocalypse on EXT4. I don't know what to do. It will boot into Clockwork but the only backup I have is the "before-ext4-convert-blabla" Should I try to Odin it back to stock or is there another option?
Thanks in advance for the help
Hi guys, reasonable newbie here. My Galaxy S2 has stopped displaying anything after the initial logo. In fact it seems to turn the phone off as you can make repeated attempts to boot it within a few seconds.
I started by flashing an insecure sgs2 kernel from this site with odin, then used s2root.
I then played around with rom managed but found it wouldn't boot into clockworkmod (orange exclamation mark in a white triangle every time) I booted into it manually and started trying to flash cm7 which I had downloaded earlier.
I wiped the data etc and flashed the cm7 zip (plus the google apps zip). Rebooted and got into cm7 with everything seeming fine.
Next I thought I should probably flash back to the stock version of the insecure kernel. I rebooted the phone but got distracted and didn't start it up in download mode, I looked just in time to see the normal logo (with the yellow insecure triangle) and then nothing....just blank.
I tried rebooting afew times and nothing, even after yanking the battery. Then I tried getting back into clockworkmod to reflash cm7. Nope, same thing happens.
I can still get back into download mode but nothing I flash makes the slighest difference. Tried reflashing clockworkmod, insecure and stock kernels of various versions but I'm stuck.
This is almost a new phone and I can't believe I've already killed it I would be so grateful for any tips, I've included as much info as I can think of from the top of my head but I will do my best to answer anything you gurus might need.
Again, very grateful for any help...I don't want to have to explain to Orange how I've managed to brick this after 4 days
Ok after trying over and over again to get into recovery mode, it booted into the original (3e) recovery. I've just flash cwmod to it again and have just flash cm7.
After reading some posts about cyanogenmod sometimes not flashing correctly first time, I did it twice (and it did indeed take longer the second time) and twice for google apps.
Next I'll try to get back to the stock kernel. This is where it went wrong before but i'll cross my fingers.
Edit: Well, multiple reboots didn't cause a problem but flashing the stock kernel back does kill the handset again. I'm sure this stuff is all obvious to those with experience I guess I'll have to sit with an insecure kernel and the yellow triangle for the forseeable future. On a side note, s2root doesn't see the phone connected with cm7 (yes usb debugging was turned on). I'm hoping that it is pre-rooted but I haven't tested that yet.
Hi,
I recently rooted my htc vivid and i tried to flash a rom. However, the rom didnt work and my phone isnt working. The phone's bottom touch-buttons vibrate when touched, but the screen remains off no matter what i do. What's wrong with it?
EDIT: I got it to boot, however, its stuck on booting, the boot logo just keeps on popping up. What should I do?
any luck?
sounds like you need to try and flash the rom again. this may or may not be a know issue with the rom. check the thread where you got the rom. I had to flash twice with the same rom the last time i did it (unrelated device)
May have to hold the buttons in a specific sequence to get back to the debug mode.
also have a look through this thread:
http://forum.xda-developers.com/showthread.php?t=1433149&page=2
Hello folks, first post, hope you can help.
My phone has a very specific problem that happens with every rom BUT with AOKP.
When the phone is on idle it just gets stuck, black screen, button lights are on. Only thing to do is pull the battery out. It also happened with the stock rom, so I tried to unroot it and give it to sprint but they couldn't take it because of a small crack on the screen(been there forever).
I came back home and tried to flash it with a custom rom again, and recovery was broken, so I flashed recovery on the device 3 times before it started working again.
I randomly chose AOKP and it was working pretty well, although it slowed down lately a lot. I tried to install JB on it recently and the problem returned, so I tried CM9 again, CM10 even tried Bugless Beast, same thing. I keep going back to the backup I have of AOKP and it's the only one that doesn't crash my phone.
I've attached the phone information so you guys can see exactly which built I'm running.
Bump.
Please help me fix my phone, I'm really at loss how to solve this problem,
Do you turn deep idle on? If so that could be the problem......when u flash a new rom, as your setting everything up, make sure deep idle is turned off.....the option is under advanced in the cm roms .......hope that helps
10....0011....10101
I installed a custom rom a few weeks back, and now am having problems with it.
When I attempt to turn it on, the boot animation won't even start before my phone decides to turn of and begin a constant vibration pattern.
I would connect to Odin and fix this, but when I load boot menu and the download screen, it does the same thing.
I was running Slimbean on android 4.0, then after having problems running that, I changed to Cyanogenmod. I then attempted to go back to stock because I was having problems with that too, and this is how I got to the problem I'm in.
Is there any way I can flash a rom without having to have the phone on? Anything I can do to fix this?
Thanks,