I was browsing the Galaxy-Light forums and I didn't see anything concerning CWM at all. I am just wondering what happened to support for CWM on the Galaxy-Light..
Related
So just to make it first stated, im no newb to this forum. i flash all the time. i just had my phone unbricked by Connexion2005 and the crew over at mobiletechvideos.com they did a fantastic job at restoring my vibrant to its previous luster. my problem now is i cannot find a way to flash clockwork recovery. ive downloaded rom manager from the market and tried flashing then rebooting to the recovery environment. but nogo. still on stock recovery. ive tried some of the older versions and none of them work either. what am i doing wrong? i also found others with the same issue in the clockwork thread in the dev section. someone shed some light for a fellow modder.
No, I'm not a (complete) noob to this, but I have a few questions...
1) It seems like more times than not, I can't get something to flash properly with CWM, it'll get to "Installing update" then it just freezes on that forever (the loading bar has the \\\\\\\\\\\ that just stays like that). Am I doing something wrong?
2) I recently flashed the newest version of the Dark Side ROM and all seems to be running smoothly except the stupid new D3 Camera, it won't open. I've seen other people have problems with this, but not for this rom. I've tried flashing the D3 camera separately and even the stock camera but I keep having the issue listed in the first question.
I know there are a thousand other people who have asked this, but I can't get the stupid thing to work. Help would be greatly appreciated!
What/Who's version of CWM are you using first of all?
Tenfar's CWM (1720)
brother, you need to unlock your bootloader and upgrade to romracer's custom CWM 3.2 !
I'd switch to RomRacer's CWM Recovery... newer, better, etc.
First you need to check to see if you have file "install-recovery.sh" @ /system/etc.
If you do, delete it. Then install RomRacer's; thread here: http://forum.xda-developers.com/showthread.php?t=1204500
Alright got the recovery image flashed, where do I go from here, or am I finished? They didn't provide any further instructions, but i'm not seeing an app or anything that would initiate recovery...
Woooowww... nevermind guys, the answer was too obvious. Anyway thanks for the help!
I let Rom Manager update CWM for me. What a mistake.
It updated to V 5.0.2.0 Which is unusable, along with the fact that my old backups are now rendered useless. I need to flash back to V.4 of CWM.
Which leads to my question which Version of CWM 4 is most stable...?
EDIT: Okay i might be able to live with this after all.
However a few questions.
1. Are old backups from V4 compatible?
2. Is the charging bug fixed after all? everyone is spread out over if it is or not fixed...
I use cwm TeamWin. It very good!!
Hey guys, so i got my phone serviced yday and ever since im unable to use any of the Custom ROMS available.
I tried every possibilities, but some how even though im able to install it via recovery, im unable to enter the ROM due to the continuous Boot loop without any animations too.
But im able to FLASH the Normal Stock Roms as many times as i want.
Never experienced this trouble before at all.
Please help/guide me to resolve this issue.
Unable to use my phone without Custom ROMS.
Thanks in advance!
Google searches do work
You might want to google boot loop specificly with your phone's name in the search. Then do the same search here on xda. Your question has most likely been addressed elsewhere and maybe by the tag on the bottom of this thread you started.
Buggy recovery I guess, change or reflash your recovery.
Sent from my LG-P500
Apologies if this has already been covered but I have seen so many old conflicting threads with regards to 6.0.1.2 Touch Recovery.
Therefore I need some clarification.
Is 6.0.1.2 safe to use as I have read people have had several problems and even bricked devices.
Guys in your opinion should I go back to 5.5 or is 6.0.1.2 stable enough to use.
I use it every day I've never had a problem until now