hi, i had bionix 1.3.1 and i just flashed cm7.1.0.1
after i flashed the phone was in a bootloop installing it on cwm,
the the phone bootloops with the "galaxy s cyanogen" logo
every method i try to enter download mode it shows a grey battery ith a loading circle in it instead.
adb does not work i am getting a "device not found" error,
how can i fix this?
Yoy are not in a soft brick, you are in a CWR mismatch. All you have to do is boot back into recovery and reflash CM7 over itself again and then it should boot up just fine.
This is a known problem with going to CM from 2.2, so don't think that you have to Odin back to 2.1 and then re-install CM as you will only get back to where you are now.
Related
my phone keeps resetting every time i reboot. i was originally running community rom v1.3. over the yesterday, i thought i install a new theme (touchwiz4 for community rom 1.3) on it. when booted into recovery (red) and installed it, i rebooted the phone. the phone got stuck in a boot loop. i pulled the batter and manually boot to recovery and flash the commrom 1.3 again. that also for stuck on boot loop. so i thought i odin back to stock and reroot and do it again, the same problem occured. so i odin back to stock again and flash evil fascination v3.5.1 and thankfully, it worked. i signed in and redownloaded all my apps again. then i went into tsm parts in the setting so i can get the clock back onto the status bar. after i did that, i restarted my phone to get the clock back. when the phone booted back up again, everything started forceclosing. even the launcher (zeam). i also noticed that everything had been reset to when i first installed the rom. i have no idea what is going on. please, any one help?
nevermind, i solved my own problem
odin back to dl09
ota to ed01
then rooted and flashed com rom 1.3 again
Hi all,
Today I wiped all data and cache from my device and installed VillainROM from CWM Recovery Manager. Install looked fine it said that it finished, so I went to reboot.
The device was stuck on the Samsung Galaxy S II logo with the yellow triangle (!) for around 10 minutes. I then turned it off cause I realized it wasn't going to boot.
Anyone have any idea why this happened? I restored a backup of my previous ROM and my phone booted up real fast and it was fine.
Could just be a bad download?
Sent from my GT-I9100 using XDA App
Try flash it again before it boots. IE: Flash from zip, then go back and falsh from zip again.
I've had to do that with CM...
OK will try that, cause the same thing happened to me when I installed Cyanogenmod straight from Rom Manager. Thx
Update: No go, I also made sure Deluxe Settings was uninstalled before I went into recovery. It's stuck at the boot screen.
However, upgrading my previous ROM (WanamLite v4.0) to WanamLite 5.2 worked fine and the device booted. It was exactly the same procedure in recovery mode but a different ZIP file.
Will try another ROM like LiteningRom and see if anything changes. I don't think it's a CRC error because I open up the files before I copy to the device to see if WinRAR pops any CRC errors.
I'd start on the thread a few up from yours.... the one that mentions if you have a boot loop
Sorry, I didn't realize it was a boot loop because it wasn't actually looping, just stuck on the image. Is that considered a boot loop?
I was trying to upgrade a friend's phone to CM7, which I did but it wasn't working very well. I booted back into recovery and restored the backup I made before CM7 and it got stuck at the Vibrant screen. I flashed PDA_T959UVKB5.tar via Odin and now it only boots into recovery. Download mode still works, not getting any "Can't mount X" errors. Anyone know of a fix?
Solved, used AIO Vibrant toolbox to flash back to stock
I just got my P500 back from warranty after I hard bricked it a few weeks before (KDZ crashed during flashing). They replaced the whole PCB.
Now I wanted to install the Clockwork Mod again and so I downgraded to Android 2.2 (they sent it back with 2.3.3), rooted it, installed ROM Manager and CWM. But if I want to boot into recovery mode I get the recovery mode unpacking-logo (not the warning sign, it's the logo with the arrow indicating something's installing) and after a few seconds the screen turns black and the device boots the normal ROM with factory settings.
I also tried that on 2.3.3 with the same result and I just don't know what I should do to get into recovery mode :/
I downgraded the OS because of the baseband (I want to use CM7) and I rooted it with SuperOneClick using the GingerBreak exploit.
Reflash recovery because your recovery not flashed properly.don't use rom manager to flash recovery use another method like lgmdp or terminal or adb.
lgmdp worked like a charm, thank you!
Hi guys just did something real stupid today... I tried flashing the maximus1.2 custom rom and ended up stuck in a bootloop. After that i tried to flash the maximus 1.0 rom and it work again... Stupidly enough i tried to flash the maximus 1.2 rom again and this time it went back to the bootloop but however this time i can't access to clockmodrecovery to flash back to the stock rom. everytime i enter the recovery mode, it just crashes itself and reboot and enters recovery and crashes again, the cycle repeats. When i enter bootloader, somehow i can't flash back the clockmod rom cause it keep saying waiting for device. Is it possible that the device itself is bricked?