my friend gave me his galaxy captivate. he was messing with the software an screwed something up an he gave up trying to fix it an gave me the phone. it is a galaxy captivate with froyo 2.2 what happened as he told me is he flashed a new kernel with rom manager, but rebooted the phone before he was suppose to. now when it boots it shows the i896 on startup but goes to this glitched out screen with random colors in lines, the phone vibrates a few times then restarts itself an repeats. is there anything i can do to fix this?
If you can go into recovery, reflash a stock ROM and see if that will help. There are plenty of resources on this site that will teach you how to recover from a bootloop (which is what it sounds like it is from your description).
Seems like a bootloop. If you can get into recovery: factory reset, wipe everything. Go mounts/usb storage (or something like that) and mount it to your pc. Download a stock rom if you can. Hope it helps. Sorry if it doesn't.
Related
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.
I just switched from the old Epic Experience to Cyanogen 7, the latest nightly version. When my phone boots up, everything works except for my phone, text messaging, and 3g. The phone keeps looping from Airplane mode off to on. I can't even make calls but wi-fi works.
I tried to replace the Cyanogen Rom with 4 other roms with no luck. It just keeps booting back into the Cyanogen one. Now I'm stuck. I've booted to CWM several times now, wiped the cache and dalvik and nothing. (I get the /sd-ext error but I heard that doesn't matter).
Can someone please help or direct me to where I can find help on the issue?
I ended up just following the video here:
www youtube watch?v=pleE_tzmiMo
It was very helpful for using Odin to put my phone back to stock. I don't know why but I can't get my phone to install any new ROMS. I just tried installing the one that says "ERA" and I get the Samsung screen on boot up but it freezes. :-l Why are ROMs better than having root access to the main stock?
Hi guys,
Really sorry to ask about this but tearing my hair out!
I have a P6200 UK model. I installed CWM v6.0.1.0 and it worked fine. The intention was to install Galaxy ROM HD (build #06), so I downloaded it, put it on my SD card, and installed from CWM recovery. The install got stuck on "Flashing boot" - so after around 15 mins I reset it.
It went into a boot loop on the initial Samsung logo. Luckily I'd previously re-flashed stock HC with Odin (to cure a dead Wifi problem caused by, I think, an errant install of Busybox) so I did this again, rebooted, and the system came up, text started scrolling up the screen, followed by a red error message (see picture) and a reboot. I was then once again stuck on the initial Samsung Tab 7.0 Plus log. I repeated the process and it didn't even get past the Samsung logo.
So I thought I'd try the newly released ICS Rom (GT-P6200_ATO_P6200XXLQ1_P6200OXALQ1) - this seemed to install OK, then half booted, did some text type installation stuff with the blue Android, then rebooted again, finally getting stuck on the Samsung logo with blue pulsating behind it. It never gets any further than that.
I tried flashing HC back - same result as earlier. I can also reflash CWM and sometimes it works, sometimes it doesn't. It seems I've run out of options.
So - question is - where (if anywhere!) can I go from here?
Help greatly appreciated, many thanks!
have you tried a system wipe in cwm? if not do a system wipe and reflash HC using odin.. same thing happen to me 2 days ago.. I think something is up with HD rom
Hello fellow XDA members! I am a Noob.
So I believe I have a Bricked Galaxy Note 10.1. Model GT-N8013
I Rooted Stock ROM, and flashed Collective Edition 5 Dark Side.
So heres what happened, everything seemed fine, until I made a mistake, I was Pimping my ROM with the PimpMyRom app. Every change seemed fine and my note worked, but when i saw the double boot screen slide in the app, i did what it said, i have the imf support or something like that. Then after i had the ''support'' needed, i clicked install button on the double boot slide, it seemed to do something and requested nothing, so i went ahead chose a second clip, and clicked set as second boot screen. It said it wont take effect until the 3rd boot, so i rebooted 3x, but at the third time, it was stuck at the boot screen with the galaxy note 10.1 logo ! It did not start or did anything, over time it would turn off and automatically reboot, but it would get stuck again !.
To attempt to fix it, I Booted into recovery (CWM) and did everything i could. I wiped nearly all cache, factory reseted, then out of fear, i flashed the stock firmware ROM from Sammobile website, with ODIN, and to my knowledge, it got worse!! It booted, seemed to do something then in the logo screen it got stuck once again!! Stock recovery says unable to mount /efs, i don't believe EFS is completely corrupted, I left it stuck for awhile and it shut down in like an hour. Help, what can i do to fix this!?!?!?!
Device cannot boot up.
I could boot into recovery and download mode only.
I thought that I too had bricked my 8013 the past weekend. Trying to do something that I shouldn't. It took me a bit of work and a lot of worry (my wife gave me my 8013 for Xmas and if I had to tell her that it was now a doorstop, she would have killed me). I used this method to get back to stock and then was able to work my way back to the ROM I use. I disremember in which order I Odin'd things, but in the end was able to un-brick. All I can say is give it a shot.
jusliloleme said:
I thought that I too had bricked my 8013 the past weekend. Trying to do something that I shouldn't. It took me a bit of work and a lot of worry (my wife gave me my 8013 for Xmas and if I had to tell her that it was now a doorstop, she would have killed me). I used this method to get back to stock and then was able to work my way back to the ROM I use. I disremember in which order I Odin'd things, but in the end was able to un-brick. All I can say is give it a shot.
Click to expand...
Click to collapse
i did what u said...but all i got is i able to get through the logo but without seeing anything only able to hear the sound. any other tip? i got the same problem as above.
Hello
G920f came to me that cannot startup. I powered on but after 10 seconds it freezed. if you leave longer powered of it can works maybe to one minute and freezed again. I tried 4 different flashes but same. I tried to hard reset but in freezed on android figure. I flash unikernel so I could enter on recovery meny made hard reset and wipe cache but still same situation. The phone is brand new and costumer said that he had this problem from begining after thid day of work and he didnt bought with warranty. Most likely its looks like hardware(CPU) problem but I want to know if any has these problem and if anyone has managed to resolve this problem
Might be a lemon S6. Return your S6 back to Samsung for warranty replacement.
I'm also in limbo, can't get into stock recovery at all to wipe anything it gets stuck in the android Logo, custom recovery like twrp and phil just freezes up also flash kernel with root(S6_UniKernel_v8-0002-ODIN) still no go I did just about everything I had up my sleeve and some I didn't mention still nothing still freezes.. Also flash firmwares just end up with the same result