Hey xda.
Recently I flashed my GS with this rom (http://forum.xda-developers.com/showthread.php?t=1449156&page=), but just in a older version(pre-alpha) and after probably a month of use I began to experienced at lot og bugs and suddenly crashes in apps and programs. I decided to do a reboot,battery pull or wipe cache to see if that clould do it, but nothing help. On the contrary, my phone would not start. The Galaxy S logo showed u, but when the miui xiaomi.com logo showed it bootlooped. Several reboots did not work, so i decided to mount usb from recovery and download the newest version of the rom and then try to flash. I did not wipe, but i worked just fine and i thought i had my phone back, but after little over a day of use the screen began to flicker and blink, and no programs nor apps worked, just crashed. I flashed again again but nothing worked, and now i'm stuck with the same problem as before. bootloop..
So have anyone experienced the same or does anyone have a solution for this problem?
Related
Hi guys,
So i went to Romkitchen.org, and cooked a rom. now this is my first rom so i have never flashed one before. Now whats happening is that when i boot up my phone, everything seems fine. although there is a pixelated screen before the splash pops up. Now thats not the problem, the problem is that i cant do anything on my phone. whenever my phone is turned on, i can use it for like 5-6 seconds, and then the splash screen pops up again. And this keeps looping over and over again. i tried using that small window of time to factory reset, since it didnt reset when i flashed the rom for some reason. except when i try to reset it, the phone reboots. except it keeps on the AT&T screen. Same thing happens when i try to flash to rom with ROMmanager. Please help! im 13 so i cant afford a new phone, since i got this one with a contract. Oh by the way, My phone is the Samsung Captivate.
Hi guys, I've recently installed MIUI 1.11.11, and this friday there was an 1.11.18 update listed in the updater app which was already included.. I opened it, did a backup with the app and after that I downloaded the latest release and pushed UPDATE after that, and it went into reboot, then phone rebooted, I got into GALAXY S GT-I9000 screen, shortly after I got GALAXY S Cyanogen(mod) screen and shortly after that it went loading something for a quick second, then just rebooted, and then the phone started normally, I thought that was it, but when it loaded to the lockscreen I checked the version and it was still 1.11.11, so clearly something went wrong.. I did that several times after, but I get the same result everytime..
Looks to me like bootloops.. Bootloops gave me some problems while installing 1.11.11 in the first place, was stuck in bootloops in the middle of the installation of the rom until I pressed the three buttons to go into recovery mode and selected install .zip once again.. then it went through without a problem. Also I had no other problems with this rom so far..
So if anyone knows what could be wrong here, or what I could be doing wrong, so I can update I would really appreciate your help..
I recorded my screen. Recording has everything I did, nothing more nothing less, only after I stopped recording I pushed UPDATE in the updater as it clearly can't record screen while phone is rebooting.. Check it, I hope it helps with the problem.
The video is on youtube under -> watch?v=J01LpijBJ7c
Lumix357 said:
Hi guys, I've recently installed MIUI 1.11.11, and this friday there was an 1.11.18 update listed in the updater app which was already included.. I opened it, did a backup with the app and after that I downloaded the latest release and pushed UPDATE after that, and it went into reboot, then phone rebooted, I got into GALAXY S GT-I9000 screen, shortly after I got GALAXY S Cyanogen(mod) screen and shortly after that it went loading something for a quick second, then just rebooted, and then the phone started normally, I thought that was it, but when it loaded to the lockscreen I checked the version and it was still 1.11.11, so clearly something went wrong.. I did that several times after, but I get the same result everytime..
Looks to me like bootloops.. Bootloops gave me some problems while installing 1.11.11 in the first place, was stuck in bootloops in the middle of the installation of the rom until I pressed the three buttons to go into recovery mode and selected install .zip once again.. then it went through without a problem. Also I had no other problems with this rom so far..
So if anyone knows what could be wrong here, or what I could be doing wrong, so I can update I would really appreciate your help..
I recorded my screen. Recording has everything I did, nothing more nothing less, only after I stopped recording I pushed UPDATE in the updater as it clearly can't record screen while phone is rebooting.. Check it, I hope it helps with the problem.
The video is on youtube under -> watch?v=J01LpijBJ7c
Click to expand...
Click to collapse
I'm finding the same issue. Help please!
Hi everyone.
I have a problem with my phone, I've used it over 6 month without any problem, firmware was custom. Several days ago I found, that icon for FFC disappered, then sometimes the phone was freezing. But it happened not so often. Today the phone was freezed, i've removed the battery and restarted it, but it's showing only first logo and then it's restaring again. I've tried to enter to Clockwork Mod Recovery, I've entered to it without problem, but then the problem freezed and it doesn't react at any key.
Also I've tried to flash boot.img from my present firmware, but it didn't give me success.
Please advice, what else can I do and what's the problem. Tx
Hi Guys, I've have been very confident about rooting and flashing ROMS on different Android Phones because of this Forums but I'm stuck with this Korean S2 that I've flashed a MOD ROM to. It's an SHW M250S and unfortunately I've bricked the internal storage of the phone during hack. I thought that this was the issue why whenever I flash a ROM it will eventually crash. It'll turn-on and boot-up okay (though sometimes it initially gets stuck on the CM logo and I have to reboot the phone to reach the Set-up wizard) but when I start installing apps it'll eventually stop responding and then crash, it will still start up but then it will crash again immediately. And when I say crash I mean i get stuck on a particular screen, it'll eventually goes black (notification bar still visible) and the only way to get it running again is to restart it. I tried Multiple Mods JB and KK and Stock 19100 Roms but i had the same result. The last thing I tried doing was swapping the Internal Storage with the SD card and I though I had it fixed but still same issue remains. Please Help Guys.
Hi guys, so recently I bought a Galaxy S6 Verizon off of eBay. I got it for fairly cheap because it was stuck in a boot loop. I usually have no problem fixing stuff like this, but this time is different. So the first thing I tried when I got the phone was to do a reset and cache wipe from recovery. I rebooted the phone and it showed a screen that said "Android is starting, optimizing app 9 out of 31." when it got to 21 the phone rebooted and went back to 9. It did this several times before I attempted to wipe/reset again. I then downloaded the tar file G920VVRU4CPH1 and flashed it in Odin. I did a manual reset before the phone booted, and it is doing the same thing again. reboots to a green screen where it tries to optimize apps, stays there for about 20 seconds, and reboots over and over again in the same cycle. I have tried all other stock marshmallow roms that i can find, Odin won't flash older ones, (assuming its not letting me downgrade). Also another weird thing, every time I flash, the blue update screen goes to 32%, stops, erases, and reboots. Phone is on 6.0.1 version MMB29K.G920VVRU4CPH1 as seen in recovery. Any help would be gladly appreciated. Thank you!
I am having a similar problem with loading new rom. The farthest it gets is 32%. Sometimes it doesn't get even that far.
I ended up just buying a trashed s6 and swapping the motherboards. Only way I could fix it