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 rom manager

hey guys a have problems with rom manager.
i was trying to do a backup rom. but rom manager gives me 2 different errors 2 different times.
first it tells me the i need to have cmw v4 and up and the other is it cant mount system so it only backup the bootlogo!!!
how can i fix this

gypsy214 said:
hey guys a have problems with rom manager.
i was trying to do a backup rom. but rom manager gives me 2 different errors 2 different times.
first it tells me the i need to have cmw v4 and up and the other is it cant mount system so it only backup the bootlogo!!!
how can i fix this
Click to expand...
Click to collapse
Backup from recovery

mr mystery said:
Backup from recovery
Click to expand...
Click to collapse
i did that and got the same issues.

gypsy214 said:
i did that and got the same issues.
Click to expand...
Click to collapse
Did you boot into recovery from rom manager? Or by holding power + volume down to boot into the nvflashed version? Make sure you're making backups by booting into the nvflashed recovery.

I've noticed that stock GB and ROM Manager do not get along. I'm forced to boot into recovery to do anything.
Sent from my LG-P999 using xda premium

Personally, I find Rom Manager to be completly useless and doesn't allow you to do anything right. Your best bet is to boot into recovery by holding power and vol down if you want something done right.

Tattooed5150 said:
Personally, I find Rom Manager to be completly useless and doesn't allow you to do anything right. Your best bet is to boot into recovery by holding power and vol down if you want something done right.
Click to expand...
Click to collapse
Agreed I find rom manager totally useless too, I haven't even used it since my mytouch 4g days, no need to with the nvflash recovery, once flashed it is just about fool proof. I never. Ever had a problem. Using it, and to rename my backups I use andro zip from the market and its free, also nvflash gets updated in a timely manner.......great great tool and like I said no problems using it

sarni84 said:
Agreed I find rom manager totally useless too, I haven't even used it since my mytouch 4g days, no need to with the nvflash recovery, once flashed it is just about fool proof. I never. Ever had a problem. Using it, and to rename my backups I use andro zip from the market and its free, also nvflash gets updated in a timely manner.......great great tool and like I said no problems using it
Click to expand...
Click to collapse
ROM Manager works fine on phones where the recovery partition is accessible when the phone is booted into the Android OS. On my Nexus One it works great and flashes recovery to the recovery partition where it is supposed to go.
On the G2X, LG made the recovery partition non-accessible when the phone is booted into the Android OS. So ROM Manager cannot flash recovery directly to the recovery partition. It flashes it to regular phone memory and then tricks the phone into running it when you say reboot to recovery in ROM Manager. Because of this people call this a "fake flash" and is not as reliable as recovery flashed to the recovery partition where it should be. Therefore, it is not advisable to use ROM Manager with the G2X and just use NVFlash to flash Clockworkmod Recovery to the recovery partition where it should be.

Kies Failure

After painstaking deliberation, they had reached the decision to eat gingerbread. Cautious and deliberate by nature, they opted to install stock 2.3.6 using Kies, presumably the safest choice. KB5 had been having a hard time connecting to the pc via usb with debugging active - no choice was given how to connect to pc, and Kies was not recognizing the phone. Finally bypassing the usb hub allowed Kies to recognize the device, and after a long download, a usb error message flashed up and process failed. Removed phone battery and reboot, all is well but SCREW KIES
Odin from now on

Probably the most creative thing I've seen here all night. Kudos to you my friend!
Sent from my SGH-T959V using XDA App

Downloaded the stock ODIN version of GB 2.3.6 KJ6 .tar here to flash via ODIN but phone will not connect via usb at all now. I think I reverted it's firmware back to the paleolithic era somehow. Could someone share the link the newest ODIN? I have v1.85 and I think also 4.03?
Unless anyone has any ideas, looks like CWM may be my only chance. How can I upgrade firmware if the method used to update is inoperable? Whenever I go into download mode it will not connect with USB. Instead windows says
"USB Device Not Recognized
One of the USB devices attached tho this compter has malfunctioned and windows does not recognize it. For help with this problem, click here."
Great bricked in a factory reset version of kb5 ugh. And this all happened because I tried to use stupid Kies!

Son of a ginger biscuit I figured out why it would not connect it was the 6 FOOT CORD I had hooked up for convenience it WILL NOT GO INTO ODIN OR KIES without the original 3' cord wow

Don't know if it was related to the Kies failure or not but now I am up and running though I cannot flash any .zip with cwm, says signature not verified, and I cannot find a toggle, I have 2.3.6 running now, rooted with super one click zerg, recovery 3e, is there a difference between "rom manager" and "cwm"?? How do I fix this I'd like to install the custom debloater .zip... upgraded from kb5

Farlander said:
Don't know if it was related to the Kies failure or not but now I am up and running though I cannot flash any .zip with cwm, says signature not verified, and I cannot find a toggle, I have 2.3.6 running now, rooted with super one click zerg, recovery 3e, is there a difference between "rom manager" and "cwm"?? How do I fix this I'd like to install the custom debloater .zip... upgraded from kb5
Click to expand...
Click to collapse
Definitely stay away from ROM Manager, from what I've read. You're getting that signature verification error probably because the phone now has standard recovery vs. CWM. That's an assumption on my part, though. You would have to ODIN one of Drhonk's modded kernels that comes with voodoo/cwm/root to get CWM installed. Within the standard recovery there is not a place to toggle the signature verification.
Considering you're on KJ6 now, go to http://forum.xda-developers.com/showthread.php?t=1194032 and grab drhonk's KJ1 kernel. Put it into the PDA section of ODIN and flash it. Then you'll have CWM.

Farlander said:
is there a difference between "rom manager" and "cwm"??
Click to expand...
Click to collapse
I had the same issue when I first started. ROM Manager is an app used to download & install custom ROMs, make backups, etc., but it does not work correctly on our phones. "CWM" (as used in the context of the SGS4G) is the custom recovery menu we install to do basically the same things. Anyway, follow stephen_w's instructions to install a custom kernel and that will solve your issues.

Awesome response stephen_w. A link! So much info out there I'm compiling a small database but when I need something it's usually back to search!
I was up and running KJ6, trying to install .zip files from root of sd card using cwm. Did not work - error was E:\ signature verification failed
So, decide to ODIN back to KB5, and try to load cwm, upgrade via cwm, and see if there was a glitch there. Did not work. Upon ODINING back to KB5, download screen has different look, and phone bootloops at Galaxy S logo. I'm about to ODIN flash 2.3.6 again and hope that it works....
This all started because Kies failed (presumably due to length of cord) the KJ6 from Raver that I ODIN'd in I THOUGHT was all stock actually came with CWM and super user preloaded. CWM did not recognize su.apk in the root and was therefore less functional. I fixed permissions and the error went away, but many icons were still greyed out. I wanted to bring back my apps/data from rom manager backup, but my recovery would not work. It would not open the .zip files, and there was no toggle to enable/disable signature verify. This may have been because I did not buy the pay version of CWM, or I don't know how to use it properly. Do you have to somehow flash the recovery to enable CWM? Is there a particular recovery designed for KJ6 SGS4G??
Also, what is the "bootloader update" option for in ODIN?

Farlander said:
Awesome response stephen_w. A link! So much info out there I'm compiling a small database but when I need something it's usually back to search!
I was up and running KJ6, trying to install .zip files from root of sd card using cwm. Did not work - error was E:\ signature verification failed
So, decide to ODIN back to KB5, and try to load cwm, upgrade via cwm, and see if there was a glitch there. Did not work. Upon ODINING back to KB5, download screen has different look, and phone bootloops at Galaxy S logo. I'm about to ODIN flash 2.3.6 again and hope that it works....
Click to expand...
Click to collapse
Weird; I've not had the signature verification error with CWM, only with the standard recovery.
When you went back to KB5 you went from a Gingerbread (GB) ROM to a Froyo ROM. Froyo & GB require different boot loaders so if the ROM you flashed did not have both boot loaders, then you get stuck in a boot loop. Going back to KJ6 will probably get you going again.
This all started because Kies failed (presumably due to length of cord) the KJ6 from Raver that I ODIN'd in I THOUGHT was all stock actually came with CWM and super user preloaded. CWM did not recognize su.apk in the root and was therefore less functional. I fixed permissions and the error went away, but many icons were still greyed out.
Click to expand...
Click to collapse
I thought Raver's ODIN version of KJ6 was pure stock. I didn't think it had CWM or Superuser.
I wanted to bring back my apps/data from rom manager backup, but my recovery would not work.
Click to expand...
Click to collapse
You might have problems recovering to GB ROMs. This is due to an error in CWM for GB. The problem prevents the /system partition from unmounting. From what I've been told, you have to flash back to a Froyo ROM, like Bali, to do the recovery then flash back to the GB ROM afterward. Not sure if that's your problem here, though, as I've never used ROM Manager.
It would not open the .zip files, and there was no toggle to enable/disable signature verify. This may have been because I did not buy the pay version of CWM, or I don't know how to use it properly. Do you have to somehow flash the recovery to enable CWM? Is there a particular recovery designed for KJ6 SGS4G??
Click to expand...
Click to collapse
I've never paid for a version of CWM. I've always used one of drhonk's modded kernels to get CWM. Installing the KJ1 kernel I mentioned earlier should do that for you.
Also, what is the "bootloader update" option for in ODIN?
Click to expand...
Click to collapse
My best ODIN advice: Let ODIN decide what needs to be checked and what should not. I've not used the "Phone Bootloader Update" feature. Don't go anywhere near the "Phone EFS Clear", either. I've a feeling that would wipe out your IMEI and other things.
See if you can get Raver's ODIN Stock KJ6 to install, then install drhonk's KJ1 kernel. Once done, reboot into recovery mode and see if it is CWM Red recovery, which is should be. Note the version number at the top and report it back here.
If all of that works well and the right version of CWM is there, then maybe we need to examine what ZIP you're trying to flash. Maybe it's a corrupt file.

Thank you very much, succesfully flashed GB 2.3.6 KJ6, succesfully flashed Drhonks KJ1, had a hard time entering recovery boot mode
RECOVERY BOOT MODE 3 BUTTON SGS4G 959V
HOLD: vol up, vol dn, power
RELEASE: power
RELEASE: vol up, vol dn
Disabled voodoo and I'm about to load up busy box, (CWM i.e. rom manager???) per the instructions......
UPDATE 20:02 ownloaded "rom manager", re-enabled VOODOO, rebooting. I think I get what's going on here. The file system is being reformatted / partitioned every time voodoo is enabled/disabled. I'm assuming the enabled mode is ext4 partitioning. However, cwm must be installed during fat32 mode, thus the reasoning for enable/disable voodoo. Can't wait to try this out, is it really faster than stock KJ6?? Love the look and feel of the rom already!

Farlander said:
Thank you very much, succesfully flashed GB 2.3.6 KJ6, succesfully flashed Drhonks KJ1, had a hard time entering recovery boot mode
RECOVERY BOOT MODE 3 BUTTON SGS4G 959V
HOLD: vol up, vol dn, power
RELEASE: power
RELEASE: vol up, vol dn
Disabled voodoo and I'm about to load up busy box, (CWM i.e. rom manager???) per the instructions......
Click to expand...
Click to collapse
Yeah, since being on GB I've been unable to get into recovery unless I use an app like Quick Boot or using ADB from the Android SDK.
Rom Manager and CWM, to my knowledge, are different animals. Good luck getting it going; it sounds like your 95% of the way there.

Heck yea workin good now to restore those apps I lost and debloat and play with boot animations!!!
UPDATE: Just also flashed via CWM .zip the debloater file, SWEET
Bloatware remover flashed with cwm works awesome, just browse to find the .zip doesn't even need to be in root dir
So far no noticeable deficiencies and without even installing app killer I have 165 used and 343 megs of ram free!!
I'm about to try to backup progs using rom manager, but when I click "backup/restore" it tells me I have to flash clockwork mod, which I'm pretty sure is already flashed??

Farlander said:
Heck yea workin good now to restore those apps I lost and debloat and play with boot animations!!!
Click to expand...
Click to collapse
Awesome, glad you got it working

MY PHONE IS NOW ALL THAT IS PERFECT
Thank you EVERYBODY
This took me about 2 weeks of 3-4 hours a day research and thumb work
now operating
2.3.6 KJ6 GB w/
KJ1 drhonk stock + voodoo + cwm
debloater.zip
Titanium Backup to restore all apps (adfree, app killer, etc. etc.)
Icons and background are gone but no bigggy

mine got unplugged in odin download screen can anyone help?

Andrew.80 said:
mine got unplugged in odin download screen can anyone help?
Click to expand...
Click to collapse
That blows. Does ODIN recognize it when you plug it back in? If so, just reflash.
Sent from my SGH-T959V using XDA App

When in doubt take the battery out! (to dinner)
UPDATE: I want to make a total phone backup (of all my current settings) using rom manager. When I go to "backup current ROM" it says cwm needs to be installed and gives me options for several phones, including the i9000. Should I do this even though cwm red is already installed on my phone? Need a workaround here...
thanks in advance

Farlander said:
When in doubt take the battery out! (to dinner)
UPDATE: I want to make a total phone backup (of all my current settings) using rom manager. When I go to "backup current ROM" it says cwm needs to be installed and gives me options for several phones, including the i9000. Should I do this even though cwm red is already installed on my phone? Need a workaround here...
thanks in advance
Click to expand...
Click to collapse
ROM manager doesn't work on the SGS4G. Your best bet right now is titanium backup, or flashing the bali kernel for 2.2 if you want to make a full backup using cwm recovery.

stephen_w said:
Definitely stay away from ROM Manager
Click to expand...
Click to collapse
ultimakillz said:
ROM Manager is an app used to download & install custom ROMs, make backups, etc., but it does not work correctly on our phones.
Click to expand...
Click to collapse
FBis251 said:
ROM manager doesn't work on the SGS4G.
Click to expand...
Click to collapse
Man, this should really be posted somewhere.

stephen_w said:
That blows. Does ODIN recognize it when you plug it back in? If so, just reflash.
That fixed it
Sent from my SGH-T959V using XDA App
Click to expand...
Click to collapse
Sent from my SGH-T959V using xda premium

[Q] CM7 / ICS Flashing issues

I soft bricked my phone playing with ICS, I got a JIG and solved the problem
I can now ODIN back to any version and once rooted I can install any samsung based rom, the problem comes when I try to flash aosp both CM7 and any ICS beta
What happens is I select the zip, it runs a script and the phone reboots, I see the AT&T logo and then it mounts the sd card, it says it can't find the zip file.
I've tried Froyo, Eclair, even gingerbread (I know your not supposed to flash cm7 from gingerbread, I'm just running outta ideas) I have froyo bootloaders, I reinstalled them with heimdal. I've also done a master clear and erased the internal sd card
Does anyone have an idea of why this is happening?

Are you trying to install the zip from ClockworkMod?

Most likely, the rom is incompatible with the flash method you are choosing which bricks your phone. I had this happen to me twice from either flashing a rom the wrong way or just trying to flash the wrong rom all together and killing my system, but I ended up telling AT&T Techs that it happened when I tried upgrading to 2.2 to avoid warranty issues and they replaced my whole device with a refurbished unit =]
However keep in mind that they cannot jig your device and you will have to do that yourself to get your data off your device before you try getting a new one via this method.
Possible Solution:
1. If you can, flash cm7 to your device
2. Flash This ICS rom
http://forum.xda-developers.com/showthread.php?t=1363760
If you have already tried this then I apologize, but I hope this helps.

Another problem
Ok, everything I see says I should flash from a captivatemtd recovery, but when I install Rom manager and select captivatemtd, it says their are no offical recoveries for it, I'm currently running cognition froyo 2.2 with froyo bootloaders
Does anyone know where I can manually get the captivatemtd CWM? and how do I install it?

kataishin said:
Most likely, the rom is incompatible with the flash method you are choosing which bricks your phone. I had this happen to me twice from either flashing a rom the wrong way or just trying to flash the wrong rom all together and killing my system, but I ended up telling AT&T Techs that it happened when I tried upgrading to 2.2 to avoid warranty issues and they replaced my whole device with a refurbished unit =]
However keep in mind that they cannot jig your device and you will have to do that yourself to get your data off your device before you try getting a new one via this method.
Possible Solution:
1. If you can, flash cm7 to your device
2. Flash This ICS rom
http://forum.xda-developers.com/showthread.php?t=1363760
If you have already tried this then I apologize, but I hope this helps.
Click to expand...
Click to collapse
I can't flash cm7 either

movielover76 said:
Ok, everything I see says I should flash from a captivatemtd recovery, but when I install Rom manager and select captivatemtd, it says their are no offical recoveries for it, I'm currently running cognition froyo 2.2 with froyo bootloaders
Does anyone know where I can manually get the captivatemtd CWM? and how do I install it?
Click to expand...
Click to collapse
I'll go over my method of installing(I've had ZERO issues flashing from/to any ROM)
1. I FTS/MC using Odin 1 Click. My phone build is 1008
2. Root with 1 click root(I have to do steps 2 and 3 because I do not have 3 button recovery)
3. Sideload and install ROM Manager(Rom manager, and CWM update.zip are in the Sideload zip that's attached)
4. Copy CWM Update.zip and ROM to device. Reboot and install CWM
5. Reboot into recovery and install ROM
Odin 1 Click(If you can use it)
http://dl.dropbox.com/u/12100225/Odin I897UCJF6-final-OCD-REV0.zip
Root 1 Click
http://dl.dropbox.com/u/12100225/Root.zip
Sideload Wonder Machine and ROM Manager
http://dl.dropbox.com/u/12100225/Sideloading.zip
Edit** What is the build number of your phone?

Here's what you need
Just download this rom
http://download.cyanogenmod.com/get/cm_captivatemtd_full-181.zip
And then watch this video!
http://www.youtube.com/watch?v=iBPu-GqM9RE
Flash CM7 using odin
then flash ICS using clockwork mod using the instructions I gave you before.
That's the easiest way I found to do it and that's how I went from stock rom to CM7 rom and then finally to ICS

kataishin said:
Most likely, the rom is incompatible with the flash method you are choosing which bricks your phone. I had this happen to me twice from either flashing a rom the wrong way or just trying to flash the wrong rom all together and killing my system, but I ended up telling AT&T Techs that it happened when I tried upgrading to 2.2 to avoid warranty issues and they replaced my whole device with a refurbished unit =]
However keep in mind that they cannot jig your device and you will have to do that yourself to get your data off your device before you try getting a new one via this method.
Possible Solution:
1. If you can, flash cm7 to your device
2. Flash This ICS rom
http://forum.xda-developers.com/showthread.php?t=1363760
If you have already tried this then I apologize, but I hope this helps.
Click to expand...
Click to collapse
Tried this to the letter still doesn't work, could it be because of rom manager not finding a recovery for captivatemtd, some pages say I need that recovery but it isn't available in rom manager.

Finnally
Finnally got CM7 installed the problem was I had to do the three button boot into recovery twice, the first time updates clockworkmod to version 5.x
Now to try ICS again, wish me luck

Thanks
Thanks for all the suggestions, the tip in the video about flashing the speedmod kernel did help I think, I've successfully flashed
teamhacksung's ICS Port for Captivate (BUILD 9) again.

A couple notes here:
1 when your flashing cm7 from cwm( NOT 3e RECOVERY THOUGH) you need to flash the. Zip file, then reboot system, IT WILL PROBABLY BOOT LOOP, three button back to recovery and flash again, then while in recovery still flash gapps. Reboot and it will install fine. You should ONLY need to do the two time flash the first time going to cm7.
2. When you go to rom manager and choose manual flash overide from hitting the menu button you will get the unsupported recovery, DON'T WORRY about it and hit ok. Then another popup will come up and choose 3.x and it will work.
Sent From My KickAss ATT SGS2 SPORTING CM7

ROM Manager?

I hear some people use it some say it doesent work. Does it work? Is it worth installing? Just want to know if its worth my time or not lol
Sent from my LG-P999
MIUI 2.3.2

The problem with ROM manager and the G2x is that the proper method of installing the recovery is is not used. If you install recovery from ROM manager it does install a fake recovery that is basically a use-once recovery. The proper method to install the recovery on the G2x is to use NVFLASH to low level flash it. Once you install the recovery in this method the device is almost unbrickable.
Many functions in ROM manager do not work with the NVFLASH installed recovery so this kinda renders ROM manager useless. I think the only function in ROM Manager that has some merit is the fix permissions, but you can run the same thing faster from CWM recovery that is installed through NVFLASH.
A side benefit to using NVFLASH is that you do not have to root your device to install it since it is a much lower level than the OS. You can install recovery, backup the stock OS, then flash a custom ROM. If you want to go back to stock just restore the backup and use the NVFLASH program to install the stock recovery and you are back to stock for repairs or whatever.
Link to NVFlash: http://forum.xda-developers.com/showthread.php?t=1056847

I've installed recovery with nvflash but and works great but just wondering cause roms will come with ROM manager installed and I'm just wondering if I'm missing anything I guess by not letting it install its "fake" recovery or if it will mess up my nvflash version?
Sent from my LG-P999
MIUI 2.3.2
"Thanks Richie390"

I have never tried allowing ROM Manager to install the fake recovery but I do not think that it will be harmful to the NVFLASH recovery.
I believe this because many people use ROM Manager without knowing and post here that they bricked their devices and the stock recovery is always reachable. Also I bought my G2x from craigslist from someone that used ROM Manager and "bricked" the phone. I was able to fix it using the NVFLASH to flash CWM and install CM7.

Some roms (like Bionix) come with Rom Manager because the user can track OTA updates of the Rom they're using, so if the dev releases a new version, the user will get a notification that an update is available for download, if the dev set it up right.
Sent from my G2X XDA app cuz I'm stalking your mom....