I've read a few threads concerning CWM Recovery possibly causing partition corruption issues on our Skyrocket. I know there are various ways of getting CWM recovery on the SR, with the primary 2 being: (1) root phone, install ROM Manager, then flash CWM via ROM Manager by selecting the "T-Mobile T989" option; (2) flash (via Odin) a pre-rooted ROM which has CWM Recovery already baked in. So my question: Are all these CWM Recoveries identical? Which method is leading to the potential CWM partition corruption issue on the SR? Not sure if Developers are using the same recovery images as the ROM Manager app is using... and which one is best suited for the SR. Thx.
DoctorQMM said:
I've read a few threads concerning CWM Recovery possibly causing partition corruption issues on our Skyrocket. I know there are various ways of getting CWM recovery on the SR, with the primary 2 being: (1) root phone, install ROM Manager, then flash CWM via ROM Manager by selecting the "T-Mobile T989" option; (2) flash (via Odin) a pre-rooted ROM which has CWM Recovery already baked in. So my question: Are all these CWM Recoveries identical? Which method is leading to the potential CWM partition corruption issue on the SR? Not sure if Developers are using the same recovery images as the ROM Manager app is using... and which one is best suited for the SR. Thx.
Click to expand...
Click to collapse
Personally, I had corruption issues after using the ROM manager CWM for T-mobile, but only after flashing Alien #3 ROM. I have now flashed the Odin version and have been running QuikWiz and no problems. I'm not too certain that either version really are able to clear data/cache properly.
Related
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?
Hello everybody. This is my second post and obviously I'm a noob. I own the Samsung Galaxy R I9103 and would love to root it. I have been researching the probable options for the last few days and here's what I have come up with. I really need help in deciding which way to go about rooting my phone.
Option 1. The hard old way - Flashing the Superuser.zip package through ODIN PDA
http://androidadvices.com/root-samsung-galaxy-i9103-tutorial/
The rooting package included in this method probably also includes the CWM(ClockworkMod) recoveryconfused
A simpler explanation of this old school method will be much appreciated.
I'm a bit skeptical about this method as this method probably comes with the famous yellow triangle and I really don't know how to get rid of it.(enlighten me).
Option 2. Flash CWM through ODIN --> Backup through CWM --> Flash Superuser.zip through CWM
http://forum.xda-developers.com/showthread.php?t=1406880
Are the ODIN, CWM and Superuser packages mentioned in this method the latest ones for the Galaxy R or are there new ones available?
Are there any complications that might arise by using this method(known issues?)?
Option 3: Flashing CWM through ODIN --> Flashing a rooted custom kernel through CWM
http://forum.xda-developers.com/showthread.php?t=1418895
Here the dev has been generous in providing 2 options: 1. Zip package Flashabe through CWM recovery
2. ODIN flashable package.
Which one should I go for?
This kernel provides OverClocking options. Is OC only available through custom kernels or can SetCPU help in overclocking if I go for option 2? If I go for option 2 to root my phone will I be able to later flash a custom rooted ROM like the one above without any complications?
Okay, here are a few important questions:
Option 1 seems tedious, so probably ruled out. I'm confused between option 2 and 3. What is the best, easiest and safest(data loss) way to go about?
Will any of the above methods wipe out the phone storage contacts, notes, settings, apps etc? Please provide a few tips about backup as well(Stock ROM or kernel backup through CWM? for later restoration). Any suggestions will be really helpful..TIA
option 1 doesn't exist!!!!!
There's no way to flash zips via Odin, only tar /tar.md5
The best way is to flash CWM via Odin (doesn't increase download counter) and then flash superuser.zip via CWM. So I guess option nr 2. It's the safest!
If you flash custom kernel via Odin, you'll get yellow triangle and your download counter will increase. Via CWM you can flash anything without that risk. Rooting won't cause your data/settings loss. The only way to create a backup of your system, data, cache is nandroid backup on CWM.
Never mind...
E107946 said:
Never mind...
Click to expand...
Click to collapse
Download Counter is Samsung's technique to keep a check on the number of times custom firmware had been flashed on the phone.
But there's a work around & it can be reset before giving to Samsung to service center for warranty claims.
Hope this helps.
Hi!
I'm actually Gio user, my friend has Galaxy Fit. And he is asking me some help for installing CM7.
After do some research at devv section. I found this CWM recovery [DEV] Clockworkmod Recovery for GT-S5670.
It's said the recovery doesn't support RFS file system, and won't work at Stock ROM. My friend running GB 2.3.6 Stock ROM.
In Gio there is moded flashable CWM recovery via stock recovery mode, while this one using Odin.
So I'm afraid to brick his device, since this recovery doesn't support RFS system and I could flash wrong file using Odin.
So, I need some advice and detailed step to flash CWM based recovery in stock ROM for installing CM7 for his Fit.
I appreciate all of your effort and time for helping me
That cwm doesn't support backup and restore if rfs (stock)...so after installing that cwm, you need to flash a custom rom (non cyanogen first, preferably)...then you shall be able to use nandroid backups and restore feature...
Backups feature only for custom ext4 roms (all are), not for stock rfs...
Get it?
(P.s. read the sticky, everything is there )
Typed using a small touchscreen
Recently I hard-bricked my Tab whilst installing a Rom on it (Brick Bug). Now I have a replacement, and it's about time I replaced the HC with something else.
I plan to use the 'Singha ROM ICS P6800DXLP7' ROM and ' Dedraks' GT-P6800' kernel. I'm guessing installation for both is via CWM, but that is how I bricked my tab last time. How can I work around this as to not brick it again? Odin? Which do I install first? Any guidance would really be appreciated!
Thanks
Which cwm you using that cause it to brick?
Share some detail procedure...wipe on stock rom, custom rom, kernel...etc which end with brick?
For now I believe safe atm..
- From stock ICS
- Root with this method: http://forum.xda-developers.com/showthread.php?t=1849235
- Install cwm using Mobile Odin
- Boot to cwm recovery
- Flash custom rom and custom kernel
- Reboot recovery NOT reboot system.
- Full wipe and fix permission
- Reboot system to home screen
That what I always do
Here's what works for me
first, d/l CWM to SD card.
then power down.
reboot into download mode ,PC Odin is my install of choice for the roms...
then power down again after the new rom installs and re-boots
re-boot into recovery and choose install zip from SD and choose CWM (which is a temporary install)
dont wipe anything, just choose to install zip and then choose your new kernel.
After kernel (a safe one) installs, then re-boot system.
Ive never bricked this tab or my GN7000 Note
good luck
correct me if im wrong, but as long as you do not factory reset in stock ics recovery you are okay. Right?
Some Note GT 7000 guys reported that they bricked their phablets by copping large files (being on ICS). If this doesn't affect our P6800s, then you are not wrong.
I had installed LQ2 without wiping anything. But had many Screen Offs and Shut Downs, so I considered to risk the clean install.
Did it with Mobile Odin Pro, but first
Ensured that I already have CWM 6.0.0.1
Flashed Dedraks Kernel.
In Mobile Odin chosen "open file..." and then the particular md5 file,
BUT EXCLUDED:
1. Kernel
2. Recovery
Then I selected "wipe" and "clean", crossed my fingers and everything went OK.
Not quite everything, because I lost root, although I am pretty sure that I did not unselect "everroot'.
It was not a big issue. Installed again "root.zip" via CWM recovery.
Its about a week since then and I have nothing to complain.
...
Thanks for the responses guys.
Does this sound safe?:
Flash LQ2 via PC Odin
Root from universal recovery
Flash CWM 6.0.11 via PC Odin
Flash Dedraks Kernel via CWM
Then root again if needed.
Thanks
rumpypumpy said:
Thanks for the responses guys.
Does this sound safe?:
Flash LQ2 via PC Odin
Root from universal recovery
Flash CWM 6.0.11 via PC Odin
Flash Dedraks Kernel via CWM
Then root again if needed.
Thanks
Click to expand...
Click to collapse
Yeah, with these steps you should be safe.
Happy flashing
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