Database Info

[Q] ROM Manager bricking phones...?

Could ROM Manager fake Flash Clockworkmod recovery be responsible for bricking phones on LG update? Let me explain what I mean - Lots of people, like myself, installed ROM Manager and its CWM because we did not know it's not real Flash. Then We switched to "real" CWM. Now the question is when we do normal stock recovery in order to get official GB update, does this CWM of ROM manager still remains in the phone? If so, could it be that it contributed to the troubles updating through LG tool? How can I make sure I removed it from the phone?
Thanks!

Yes. Many people have confirmed that not having the stock recovery on the device is a road to Bricksville. Even though you are fake flashed there is code inserted somewhere to redirect to the fake flash, and the recovery images for flash (normally installed every boot) have been deleted or renamed. You should flash stock recovery with NVFlasher to make sure you are back at a clean stock recovery before using the LG Update tool.

Thanks but what I mean is that AFTER I realized it's fake flash I installed "real" CWM. So when I do stock on this "real", does CWM rom manager still remains in the phone and how can I remove it?

post deleted by poster

so I am a little confused I used CWM to make a backup before I did anything to my phone. And I was already on the 2.3.3 lg update. So if I restore that I should be back to stock and CWM should still be there right? But lets say LG comes out with another update (Doubtful) and I want to use it I should use the NVflash to reture the phone to stock? if I use NVflash will that put me back on froyo 2.2.2 or GB 2.3.3?
Also I used rom manager to make a backup of the rom I was on which was the stock rooted so is that fake or what the hell is fake? is it the first option in rom manager the CWM recovery? is it the same if I use CWM stock recovery? in cwn itself? Oh I am so confused someone help me

ROM Manager cannot flash directly to the phone so it "fake flashes" CWM recovery. It only installs a few files to the system so that when you run recovery the stock recovery runs an "upate" and that launches CWM recovery from your SD card. Just return the phone to GB 2.3.3 stock and be happy with it. If you restore using CWM it will remain there, so you should use NVFlash to restore stock recovery also.

jboxer said:
ROM Manager cannot flash directly to the phone so it "fake flashes" CWM recovery. It only installs a few files to the system so that when you run recovery the stock recovery runs an "upate" and that launches CWM recovery from your SD card. Just return the phone to GB 2.3.3 stock and be happy with it. If you restore using CWM it will remain there, so you should use NVFlash to restore stock recovery also.
Click to expand...
Click to collapse
I have BOTH - CWM AND CWM through the ROM Manager. So if use NV Flash to go to stock, is the CWM from ROM manager still in the phone and how can I remove it?
Thanks!

so what I am getting out of this is rom manager is crap and dont use it. If you just use CWM to do your flashing and backups and recoverys you should be ok.
Charlie

mojorisin7178 said:
so what I am getting out of this is rom manager is crap and dont use it. If you just use CWM to do your flashing and backups and recoverys you should be ok.
Charlie
Click to expand...
Click to collapse
Thanks but my questions are:
1. If I go to stock using NV Flasher, is ROM Manager's CWM still going to be in the phone, since I have BOTH?
2. Can it BRICK my phone if I do the LG update then?
3. How can I make sure I removed BOTH - NV Flash CWM AND ROM Manager CWM?

[Q] Problems with ClockWork Samsung Infuse

I tried putting clockwork recovery onto my Samsung Infuse. I Installed it through a ROM Manager and now everytime i go into the ROM manager and select it to boot into recovery it boots into android system recovery. I cannot get to the Modified Recovery needed to install a cutom ROM.
What do i need to do to get CWM to work?

Flash the community kernel via ODIN
Sent from my SGH-I997 using xda premium

VetteZ06 said:
I tried putting clockwork recovery onto my Samsung Infuse. I Installed it through a ROM Manager and now everytime i go into the ROM manager and select it to boot into recovery it boots into android system recovery. I cannot get to the Modified Recovery needed to install a cutom ROM.
What do i need to do to get CWM to work?
Click to expand...
Click to collapse
Option 1:
1.-Download Sgs Kernel installer
2.- Download a Kernel with modified cwm included ( here one choice: http://www.multiupload.com/1E3AWIQYAA <--If you are on Froyo;
http://www.multiupload.com/6ZVYU3F106<-- If you are on Gingerbread) The links ARE NOT mine are gtgx.
3.-Put the kernel in your sd card.
4.-Open sgs kernel flasher and select the kernel.
It will reboot and convert your data to ext4 and also give you modified red cmw ready to install custom roms. It will take about 5 minutes be patient.
Option 2:
1.- Download the Defuse 1.5 one click kernel from:
http://forum.xda-developers.com/showthread.php?t=1331381 (link NOT mine)
2.- Put your phone into download mode
3.- Run the file you downloaded it will do the work for you.

Find Odin preset with 3e and root. Follow directions and run odin properly with phone in download mode (explained in odin post). After that you will be rooted with modded 3e recovery. Then you can download rom manager when the phone reboots and flash for galaxy i9000, reboot into recovery and reinstall packages. You should be able to reinstall packages now since odin set up your recovery. It sounds like you aren't able to put the modded recovery in the system/bin folder; same thing happened to me. I had root, but could not modify the recovery file in system/bin. Odin is a charm, if I had the money I would donate to the guy who made it, unfortunately I don't at the moment. Odin says phone should show as com## yet mine showed as com0 and still worked. Probably depends on which USB port you use. Odin takes about 10 minutes to flash your phone but it will be worth it when you are done. I was skeptical because of the steps but it is very easy, once you get your phone into download mode its a breeze. PLEASE HAVE A FULL CHARGE WHEN YOU DO ANY FLASHING. If your phone dies you can have serious problems during the flash.

thank you all, I am going to try these once I get my internet restored.... this is kinda agony since my t1 line died....
Sent from my SAMSUNG-SGH-I997 using xda premium

Just an update, Forced it to work with SGS kernel, it put up a huge fight tho... after CWM was installed i got GingerReal 2.3.5 on there. I iz happeh

Rooting I727 compared to I9100

I'm rooting and upgrading a I727R for a friend and want to just double check something before I proceed.
I've got the I9100 and rooting and flashing is an absolute breeze. According to these instructions it isn't quite as easy with the 727, unless I'm just not understanding things.
I believe with the I9100 recovery is integrated with the Kernel so every time you flash a Kernel you automatically flash the accompanying custom recovery. Therefore to root you simply put the phone in download mode, connect to Odin and flash CF-Root kernel => DONE. Superuser is automatically installed, as well as CWM. Then you just drop and flash whatever ROMs you want.
From the above link, am I to understand that an EXTERNAL SD Card is truly essential? And since CWM can be installed without rooting couldn't I do the following?
1. Drop ROM onto root of internal SD
2. Flash CWM via Odin
3. Boot to recovery, flash ROM.
4. Done.
Will that process not automatically root the phone during install of the Rom?

anonomike said:
1. Drop ROM onto root of internal SD
2. Flash CWM via Odin
3. Boot to recovery, flash ROM.
4. Done.
Will that process not automatically root the phone during install of the Rom?
Click to expand...
Click to collapse
Right, put custom rom on sd,flash cwm with odin
that will give you the cwm to flash a custom rom which will already be rooted for him.

Soft Brick CM9 bootloop- CWM 5.8.4.3 semifail

Currently I am in a soft brick state- I cant remember which CM- 9 either cm-9-20120614-EXPERIMENTAL-skyrocket-alpha5.zip, or cm-9-20120709-NIGHTLY... (I can see that those are the only two I have on my sd card. I am on an ATT GS2 skyrocket
If I boot normally - it stays stuck on the CM9boot screen.
I can use the 3 finger method to boot into CWM 5.8.4.3
While searching for answers I read that this CWM is broken.
Initially I was trying to go back to an earlier recovery. CWM would see the recoveries on the SDcard, but when I tried to recover- it would not mount from the SD card.
I got to CM( by using odin to put an earlier CWM, and superuser on the phone, then installed Rom manager, then used rom manager to flash CWM (via tmobile sgs2) then updated to CWM touch...
When I tried using the CWM to factory restore and cache wipe it starts then hangs I cant install zips from the external SD card, or any recoveries...
I'm figuring worst case - I can go back to ODIN, and do stock recovery http://forum.xda-developers.com/showthread.php?t=1342348 , then flash the non touch CWM, superuser http://forum.xda-developers.com/showthread.php?t=1340526, then flash a recovery from my sd card??
Is there something else I might have missed in trying to get back to a functional state without going to odin?
Many thanks in advance for any assistance
Ihab

ihabelnaccash said:
Currently I am in a soft brick state- I cant remember which CM- 9 either cm-9-20120614-EXPERIMENTAL-skyrocket-alpha5.zip, or cm-9-20120709-NIGHTLY... (I can see that those are the only two I have on my sd card. I am on an ATT GS2 skyrocket
If I boot normally - it stays stuck on the CM9boot screen.
I can use the 3 finger method to boot into CWM 5.8.4.3
While searching for answers I read that this CWM is broken.
Initially I was trying to go back to an earlier recovery. CWM would see the recoveries on the SDcard, but when I tried to recover- it would not mount from the SD card.
I got to CM( by using odin to put an earlier CWM, and superuser on the phone, then installed Rom manager, then used rom manager to flash CWM (via tmobile sgs2) then updated to CWM touch...
When I tried using the CWM to factory restore and cache wipe it starts then hangs I cant install zips from the external SD card, or any recoveries...
I'm figuring worst case - I can go back to ODIN, and do stock recovery http://forum.xda-developers.com/showthread.php?t=1342348 , then flash the non touch CWM, superuser http://forum.xda-developers.com/showthread.php?t=1340526, then flash a recovery from my sd card??
Is there something else I might have missed in trying to get back to a functional state without going to odin?
Many thanks in advance for any assistance
Ihab
Click to expand...
Click to collapse
Hi there,
I recently experienced the same thing, and it was a hassle to fix--but I have got my phone working each time. The downside being that I /had/ to switch over to Odin. Mind you, I am not necessarily experienced with Android, so I can't really say that this is the only way.
At any rate, here's what I did to get it back to normal:
Load up Odin
Put it in download mode -- I assume you know to hold the volume keys and then plug in the USB.
Flash either the ICS leak or the stock 2.3.5 Gingerbread.
You should be back to good. I hope you backed everything up in either Kies or some other resource...else you're in for a hell of a time setting stuff up.
Oh: bad news about the 2.3.5 stock is that, as far as I can tell, you're unable to upgrade to 2.3.6. In turn, you're then unable to update to the official ICS through Kies or OTA. I assume you don't mind, considering you're trying to flash a new rom anyway.
Anyway, I do hope there is some bit of clarity on getting CM9 on the Skyrocket. As of now I have still been unable to do it. Just as you, no matter the settings I try, I end up being stuck at that screen. The only difference between your method and mine is that I completely did mine through CWM...nothing through ROM Manager. (Actually, I believe I tried a few differing methods involving the CWM touch and non-touch...followed many different guides but still no good.)
Hope you get it back to a functioning state. If you get CM9 working on the Skyrocket, I'd appreciate you sending a bit of details on how to do so.
EDIT: I am now on CM9. Through magic, ponies and friendship I have failed to accomplish this feat. But by pure science and the blood of a pony, I have successfully installed CM9.
After you've restored to 2.3.5 or the ICS leak (the one I was on), do the following:
- Grab the recovery-clockwork-touch U27 described below. Flash it.
- Download both the newest CM9 build from their website, as well as Google Apps, and then copy those to your external SD.
- Follow this guide: http://www.teamchopsticks.org/p/install-guide.html. Here's what's relevant to you:
Wipe data/factory reset.
Format /system (mounts and storage->format /system).
Install the CM9 zip from SD card.
Install the gapps zip from SD card.
ONLY IF YOU ARE ON TOUCH CWM RECOVERY: Format /cache (mounts and storage->format /cache)
Reboot. Let it sit for a few minutes after the first boot. Be patient.\
Click to expand...
Click to collapse
After ~10 minutes you should be fine. Mine took less, but I'd bet it could take longer. Please follow those directions above EXACTLY. I'll be happy to help you in any way I can if you reply to this thread/ send me a PM.

When I softbricked with the latest CWM I wasn't able to return back since it wouldnt detect my SDcard so I just loaded up odin and used recovery-clockwork-touch-5.8.1.3-hercules.tar and was able to read my SDcard again which had all my backups and CM9 files. I have flashed every version of CM9 every since and still using this CWM version and havent had any problems. :good:

All better now- I used ODIN to restore to stock, then used it again to put CWM (non-touch) back on, then added superuser, then just did a restore from SDcard! Muchas Gracias all!
Should I be able to then use a restore of when I had a working CM9 (and backed up with CWM)? Or would I have to do all the cache wiping/ factory reset like I did to install it the first time before using such a recovery? (and I will try that recovery- clockwork touch hercules... latrer tonight from home)

ODIN tar to restore back to factory. I got the boot loop too. Only until after I flashed CM9 then flashed dark side wipe cache only would CM9 work for me. Only on regular CWM though. Try and give that a go.
Sent from my SAMSUNG-SGH-I727

[Q] Install ClockworkMod persistently

Hi,
I downloaded and flashed my S2 with this firmware:
http://forum.xda-developers.com/showthread.php?t=1996714
Works very well. But I would like to have a better ClockworkMod Recovery. So I downloaded CWM Touch 5.8.1.5 (and also the "regular" CWM 4.0.1.5 as an alternative). I started the phone into recovery mode and used "apply zip". It says "replacing stock recovery", and the CWM Touch shows up with all functions working like a charm.
But next time I reboot the phone into recovery, the old recovery mode is present again. Same happens with the other CWM (4.0.1.5). It's like the installation is not done persistently on the partition but just temporarily into RAM ...
If I use the ROM Manager app to install one of the two CWMs, the app accepts the zip file, reboots the phone - but like before, the old recovery is still there. And it doesn't make a difference whether I select "wipe cache/data" and/or "wipe dalvik" prior to installation or not.
Is there a way of persistently installing this (or maybe a different) CWM?! Does it depend on the specific kernel that is in place with the firmware? Does said firmware and its kernel prevent installing a different CWM?
Regards,
Mac

Found a CWM6 here
http://forum.xda-developers.com/showthread.php?t=1877270
Works alright and can be installed permanently.
Mac

The cwm of kernel doesn't allow another cwm to be installed!
Unless you're on stock kernel,I think this won't be possible!
But there should be a way out!!
Sent from my MT11i using Tapatalk 2

Ghostfreak NB said:
The cwm of kernel doesn't allow another cwm to be installed!
Click to expand...
Click to collapse
Well, obviously it does. Said CWM 6 can be installed via Odin. I did not try CWM installation. This indeed may not work.
Mac