So I have one of the original 'lucky' i9000m phones with working recovery and download.
I was on Darky's resurrection 9.2 ROM and it was working fine for the past month or so and then the Facebook app buggered up some stuff.
Blah blah, long story short after the last time I did a Wipe Data/System from CWM, it is now stuck at the White on black Galaxy S boot logo (not the loading animation).
tried reflashing the ROM but no luck. I can still of course go into recovery and download, so I'm not worried about it being a brick, just want to be able to use my phone.
Any ideas?
EDIT: I also tried flashing CM7 on here again. Same deal, it flashes on fine, it even swaps out to the CM7 boot screen (again not the loading animation) but won't go any further.
I don't think it's a brick, but I'm running out of ideas.
Nevermind.
Flashed CM7 again and used the latest nightly initial package. Worked like a charm
Related
I have a sprint galaxy tab, was rooted and had Bauxite OC kernal but otherwise stock. Was working fine this morning, picked it up tonight wont power on past samsung logo, not the glowing one. I can't get into recovery at all, download yes. Tried putting stock firmware with odin back on says pass but still stuck at logo. Did this a few times same results other that once it would just keep turning off and on by itself in a loop. I tried Baush [Kernel][CDMA][VZW/SPRINT]KhasMek Voodoo Plus v5 Now with Full Voodoo CwM! and went through that it installed but the voice says not enough space. I did get into recovery with it but it would not let me do anything at all.
Hi all,
I just flashed cyanogenmod 7.2 rc2 onto my samsung captivate yesterday via clockwork recovery. Now my phone is stuck in an infinite loop.
It loads At&T logo then displays the cyanogenmod screen, then goes in recovery mode for a second running some installation? then quickly back to AT&T logo again... this cycle repeats indefinitely unless I pull the battery out.
I am panicking right now =_=''. Can someone helP????
Do you not read??? It is supposed to do that. you have to do a battery pull and go into recovery (will be blue now and a different version) and re install
intellium said:
Hi all,
I just flashed cyanogenmod 7.2 rc2 onto my samsung captivate yesterday via clockwork recovery. Now my phone is stuck in an infinite loop.
It loads At&T logo then displays the cyanogenmod screen, then goes in recovery mode for a second running some installation? then quickly back to AT&T logo again... this cycle repeats indefinitely unless I pull the battery out.
I am panicking right now =_=''. Can someone helP????
Click to expand...
Click to collapse
ya you need to go to recovery manually and reflash the rom again go and read about it and you will also get the reason for that
Hi - need some advice on my Galaxy Ace S5830T.
For some history, I rooted it a year ago and installed clockwork mod recovery. Apart from loading a few apps that need root privelage I haven't done much to it, ie has standard rom etc.
The other day a couple of applications came up with the 'Force Close' Screen (internet, facebook). Normally I just click on OK and everything is fine, but whenever I ran either app I got a force close error straight away. Used my app killer to shut down everything running, still had same problem.
Switched phone off and went to reboot, now it displays initial "samsung" screen with web address, flashes the Telstra logo in a few colours, displays "samsung" in the glowing letters, then hangs for a while. Goes back to Telstra logo and repeats.
I can boot into recovery mode. I tried restoring the boot partition from a backup I made before rooting, but it made no difference.
I've tried wip;e data/factory reset, wiping cache, and restoring the image, but it's still stuck in the boot loop.
The fact that I can boot into recovery means, I assume, that the hardware is still all functional, so can anyone advise what to try from here?
Thanks.
Hi guys, I'll try to explain my problem:
My Milestone has been running the rom "cm-7.2.4e-umts_sholes" since two years without issues... until a few days ago: aleatory restarts and freezes. Yesterday, I turned it on and was stuck on "M" logo. Several restarts later, it shows the "2ndBoot - Kernel Restart in progress" logo and nothing else.
I tried to reflash the rom and encountered some issues:
Bootloader 90.73, I flashed the vulnerable recovery "vulnerable_recovery_only_RAMDLD90_78.sbf" and enter in recovery stock. When I tried to run the "OpenRecovery_2ndbootOR_v1_2" the OR doesn't start at all. Black screen, restarts and recovery stock again. Only the "OpenRecovery_v1_46_SHOLS_inkl_ext_mmcfix_parted_update" does the trick and starts the OR with red letters. After all the obligatory wipes, applied update from "cm-7.2.4e-umts_sholes" and then reboot system. And the same "M" stuck or "2ndboot" stuck screen. I tried wipes again, but no results.
So, I tried to go back to an earlier version and installed "SHLA_U2_02.02.0_USASHLSPERARLA017.0R_USASHLSPERARLAT_P037_A015_HWp2a_1FF" with RDSLite. It boots up Android BUT the touchscreen not works at all, even with several reboots. Tried to reflash Cyanogenmod from here, but the same issues above listed appears.
I really going crazy with this... Did I make some mistake at any point? Must I reflash the bootloader 90.73 if I found it? (besides all the webs containing all the .sbf's and bootloaders appears to be offline by now).
Any solution/advice you can give me please?
Thanks in advance and sorry my english, isn't my first language.
Several times, I tried (and failed) at installing CM on my Nook HD. It went through all of the motions of installing the ROM (no errors, nothing), but when I rebooted, it went straight back to stock with "Hi, welcome to your NOOK."
I thought maybe my version of CWM was too old. I finally found a newer version (6.0.4.9, I think). I flashed TWRP first and then tried to flash CM. This time it crashed in the middle of the installation! Now, it won't boot at all. It just shows the Nook logo, then goes to the Cyanoboot screen, then goes black, then back to Cyanoboot, and so on. It won't boot from the SD card, either. I tried holding N and power to get into TWRP, which was allegedly installed, but that doesn't work, either.
Every web page that I could find discussing the issue of bootloops says, "First, boot into recovery..."
So, what do I do if I can't boot into recovery? Or is there a way I haven't tried yet?
Okay, I was able to restore. I inserted a bootable SD card and held down the N key and the power button. It takes a few times to get it right. So, now I'm back to stock.