Related
hi i have a i9020a and i returned it back to stock from 2.3.4 but i want to go back to stock recovery and remove clockwork mod can any one help me with that
If you have gone back to stock rom, you should not have clockwork recovery
If by some reason you still have clockwork recovery, go to the Q & A, there is a flashable zip for stock recovery .
You can get the stock recovery from the developer dsixda
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 -- I'm new to the Charge but have a little experience rooting/flashing ROMS with Motorola devices. At this point all I want is a rooted device and everything else stock (2.2.1 firmware / EE4). To achieve this I placed the Superuser app zipfile onto my sd card, flashed CWM with Odin, booted into recovery and applied the zip update. Everything went smoothly, my device is now rooted and works fine. However, when I boot back into recovery I find that CWM is still installed, I was under the impression that this procedure would overwrite CWM with stock recovery when I rebooted. I don't really mind having CWM, just wondering if the fact that it wasn't overwritten is indicative of some other problem that is likely to bite me in the a** down the road.
Also, if all I have done is rooted and kept the kernel untouched, will I be able to receive the gingerbread OTA when it is released (if ever)? Or will I have to flash back to a stock Froyo ROM?
Thank you thank you thank you in advance.
talbot27 said:
Hello -- I'm new to the Charge but have a little experience rooting/flashing ROMS with Motorola devices. At this point all I want is a rooted device and everything else stock (2.2.1 firmware / EE4). To achieve this I placed the Superuser app zipfile onto my sd card, flashed CWM with Odin, booted into recovery and applied the zip update. Everything went smoothly, my device is now rooted and works fine. However, when I boot back into recovery I find that CWM is still installed, I was under the impression that this procedure would overwrite CWM with stock recovery when I rebooted. I don't really mind having CWM, just wondering if the fact that it wasn't overwritten is indicative of some other problem that is likely to bite me in the a** down the road.
Also, if all I have done is rooted and kept the kernel untouched, will I be able to receive the gingerbread OTA when it is released (if ever)? Or will I have to flash back to a stock Froyo ROM?
Thank you thank you thank you in advance.
Click to expand...
Click to collapse
What zip did you apply IN CWM?
Sounds like you applied a kernel too. Having CWM is not normal if you just flashed the superuser zip.
You will likely need to flash back to stock prior to updating with the GB OTA whenever it comes out.
_____________________________
Bloat frozen EE4 / Stock Kernel
V6 SuperCharger / Loopy Smoothness Tweak
Thank you for the reply.
The only zip I applied was the su-2.3.6.3-efgh-signed file downloaded here.
For CWM I flashed 0817_charge_recovery.tar.md5 found here.
Again I am now rooted but can still boot into CWM. After flashing the CWM file and disconnecting my phone, I initially fat-fingered it trying to boot into recovery and it rebooted. I then powered off and booted successfully into CWM to apply the zip file.
Any thoughts?
Ok, the main difference I see between my config and yours is that I may have used a different version of the superuser package.
The one at the link that you provided is superuser/su-3.0-d-signed.zip.
The one that I used is the su-2.3.6.3-efgh-signed.zip from here
You did start out from stock correct?
What is the kernel version in Settings->About phone->Kernel version?
Actually when I downloaded the Superuser zip file from the site I referenced it was su-2.3.6.3-efgh-signed.zip. This was a few weeks ago -- before version 3.0 was added.
My phone was absolutely stock when I got it 2 weeks ago and I have done no other messing with it. The Kernel version as it reads right now is:
2.6.32.9
[email protected] #1
talbot27 said:
Actually when I downloaded the Superuser zip file from the site I referenced it was su-2.3.6.3-efgh-signed.zip. This was a few weeks ago -- before version 3.0 was added.
My phone was absolutely stock when I got it 2 weeks ago and I have done no other messing with it. The Kernel version as it reads right now is:
2.6.32.9
[email protected] #1
Click to expand...
Click to collapse
Looks like you did the same steps that I did other than your extra boot into CWM. Usually, the stock init will check for the proper recovery, file systems, etc and then "fix" that which isn't right.
I have never seen it not do that before (I have had to reflash CWM several times before due to botching the 3 button bit)
_____________________________
Bloat frozen EE4 / PBJT Voodoo 0730
V6 SuperCharger / Loopy Smoothness Tweak
You cannot apply the OTA if you have CWM recovery. It will fail. Usually you need to have a fully bloated stock rom w/ stock recovery. Root is ok but you will lose it w/ the update
hoppermi said:
You cannot apply the OTA if you have CWM recovery. It will fail. Usually you need to have a fully bloated stock rom w/ stock recovery. Root is ok but you will lose it w/ the update
Click to expand...
Click to collapse
That's kind of why I chose this method to root, thinking that CWM would get overwritten when I rebooted -- but it didn't. Oh well.
talbot27 said:
That's kind of why I chose this method to root, thinking that CWM would get overwritten when I rebooted -- but it didn't. Oh well.
Click to expand...
Click to collapse
Enjoy it. I like CWM much better than stock recovery ;-)
_____________________________
Rooted and Bloat frozen Stock EE4
V6 SuperCharger
Last night, after losing 5 hours trying to root my stock Brazilian MZ605 (wifi + 3G, H.6.3-28.6), I had to flash the stock firmware because after rooting neither the wifi or 3G wouldn't work.
I guess it is because I flashed a boot.img that is incompatible with my wifi drivers (bcm4329.ko). Everything else was fine.
So I was thinking: what if I can dump my own boot.img, set ro.secure=0 on it and then flash it back to acquire root?
So, my question is this: how can I dump my own boot.img?
Other than root, I want to keep my Xoom as stock as possible.
You will need the Clockwork Mod Recovery installed it will allow you to create a backup of your existing ROM.
Look here for instructions:
http://forum.xda-developers.com/showthread.php?t=1074979
Sniperet said:
You will need the Clockwork Mod Recovery installed it will allow you to create a backup of your existing ROM.
Look here for instructions:
http://forum.xda-developers.com/showthread.php?t=1074979
Click to expand...
Click to collapse
Thanks, Sniperet.
Supposing I install CWM Recovery, can I go back to my stock Recovery image using the IMG files downloaded from Motorola?
I am trying to update my Radio/modem file with the JB Android 4.3 Radio file. It requires that I install CWM 6.0.3.7. Can I install this alongside my TWRP 2.6.3.0 installation or as I have read, it will overwrite my TWRP recovery mode? If it will overwrite, how do I switch between? Just reflash through ODIN using PDA? That seems like a lot of work and the possibilities of breaking might be high just overwriting Customer Recoveries?
If I would install this JB Radio for Android 4.3, how would I go back to GB? I can't find a single GB Radio/Modem. Could I use Radio files for GB instead of wiping and installing stock GB ROM [No Root, No Custom Recovery, but it includes the GB Radio/modem]. The reason I am worried about this, if I need to load my original stock GB 2.3.6 backup with root from my nandroid, I would need the original GB Radio and the nandroid backup/restore feature doesn't include that. All advice is greatly appreciated.
The Radio Does Not Get Backed Up By Cwm/twrp Backup(nandroid) Method.
Click to expand...
Click to collapse
[RADIO][UCMC1] For I727/I727R [09-APR-2013]
http://forum.xda-developers.com/showthread.php?t=2228292
[Q] I have CWM and TWRP installed, is that OK?
http://forum.xda-developers.com/showthread.php?t=2122152
[ROM][ics][uclf5] •∞ EMBRYO •∞ 4.1 •∞ [08-jul-2012] [It has ICS radio files, but no GB files]
http://forum.xda-developers.com/showthread.php?t=1754473
Just flash it with twrp. It'll work just like if you did it with cwm.
I have read that some of the zip files does work with TWRP as well. However I am interested in using the following Custom Rom [SuperLite AOKP JB 4.3 v1.0]. That installation requires CWM 6.0.3.7, because it will prevent the infamous black screen reboot issue. What about GB radio file & installing on top of or installing side by side TWRP & CWM?
[ROM][AOKP]SUPERLITE AOKP JB 4.3 V1.0| BYO | SLgapps | SEPT 30/13
http://forum.xda-developers.com/showthread.php?p=46066949
Pick a recovery and use it. Backups are not cross compatible. If you make a backup with cwm it won't work with twrp.
You can flash radios with either. Just pick one.
Sent from my HTC One using Tapatalk 4
lowao said:
I have read that some of the zip files does work with TWRP as well. However I am interested in using the following Custom Rom [SuperLite AOKP JB 4.3 v1.0]. That installation requires CWM 6.0.3.7, because it will prevent the infamous black screen reboot issue. What about GB radio file & installing on top of or installing side by side TWRP & CWM?
[ROM][AOKP]SUPERLITE AOKP JB 4.3 V1.0| BYO | SLgapps | SEPT 30/13
http://forum.xda-developers.com/showthread.php?p=46066949
Click to expand...
Click to collapse
If you have not already installed a 4.3 ROM, then you are recommended (nay, required) to use CWM 6.0.3.7 to do the initial wipe and install, after that you can switch to TWRP for any flashing after that.There is something that 6.0.3.7 does to the data partition that TWRP doesn't, on the initial setup. Once that is done, it doesn't matter. Flash the JB radio when you flash the 4.3 ROM. And going back to GB if you need to is fairly simple, just follow Vincom's guide. There are lots of flashable zips of GB radios you can use.
I am still a bit confused regarding TWRP & CWM being installed at the same time or side by side. So, let me get this straight. If I want to install JB 4.3 ROM, I must first boot into ODIN, install CWM through ODIN, reboot, boot into CWM, wipe the system, reboot, boot back into ODIN, install TWRP, reboot, boot into TWRP, install the JB 4.3 ROM, and finally preform the last reboot. Is this correct & it won't break either of the custom recoveries? However rpr69 said "switch back to TWRP." Are you inferring TWRP & CWM can be installed side by side? If so, how do I access one over the other?
Regarding GB's radio files:
Which of the following links is the Radio/modem files? Is it the second one? I know of them is the official stock ROM and the other requires the OTA updates. However the poster didn't include the OTA updates yet...
ATT-UCLI3-odexed-cwm.zip http://d-h.st/rDZ
kernel-ucli3-sgh-i727-RD01-cwm.zip http://d-h.st/QfR
[ROM][ICS][UCLI3][09-NOV-2012] Stock odexed & deodexed UNTOUCHED
http://forum.xda-developers.com/showthread.php?t=1982467
Try this, wipe cache and dalvik.....no promises lol [Link is dead.]
https://dl.dropbox.com/u/60567424/modem-UCLI3.zip
http://forum.xda-developers.com/showpost.php?p=33344009&postcount=22
Sadly no link for UCLI3 [GB's Radio files.]
[ROM][ics][uclf5] •∞ EMBRYO •∞ 4.1 •∞ [08-jul-2012]
http://forum.xda-developers.com/showthread.php?t=1754473
The 1Stop post from Vincom:
http://forum.xda-developers.com/showthread.php?t=1785999
Sadly there are no more links for GB / UCLI3 radio files.
I know you posted but its confusing, let me simplify, I hope:
im assuming you have either cwm or twrp installed, if on stock read this.
you cannot have two recoveries installed at the sametime:
recovery install procedure:
if not on cwm6037 flash cwm6037 with what ever recovery you have now and reboot back into recovery.
then flash any custom jb4.3 rom, preferably latest cm10.2 nightly found here and reboot rom at least twice.
if you like cwm 6037 stay with it, I don't, or else just flash twrp 2.6.3.0 w/cwm 6037 and reboot back into recovery or rom.
now you can just stay w/the cm10.2 nightly you flashed with cwm 6037 or flash any other rom w/twrp 2.6.3.0 which is now your installed recovery.
that's it you should not have the reboot problems on any jb4.3 roms.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
above recovery install procedure is only if a jb4.3 rom on its 2nd reboot just has a black screen and wont boot into rom, but 2nd boot does usually take longer than normal upto a full minute.
if flashing a rom or restoring from nandroid(recovery backup) prior to jb4.3 and then later decide to flash a jb4.3 rom you need todo above recovery installation procedure b4 flashing a jb4.3 rom.
restoring backups only work with whatever recovery they were made with, you cannot restore a cwm backup w/twrp recovery and vice a versa.
newest versions of recoveries should restore backups made with their older versions.
why do u want an old radio, they will not work w/jb roms
old radios are linked in the 1stop sticky under "old stuff".
installing the radio has nothing todo with the recovery you are using.
flash jb radios for jb roms which happen to be all the current roms.
reread the radio section in the 1stop sticky.
I linked this post in the recovery section of the 1stop sticky
Thank you vincom for explaining the process of using both CWM 6.0.3.7 & TWRP 2.6.3.0 together. I am familiar with backups ONLY working with their original customer recovery. I didn't even think about older versions of backups (not) working with newer custom recoveries. Was there an issue working with older backups in the past?
The reason I need the old GB Radio/Modem files, because when I have to return the phone to stock & load up my old Gingerbeard nandroid, I will be able to return it back to AT&T with the original Radio files and the original Gingerbeard OS. Anywho, thank you for the GB radio. I really appreciate it!
lowao said:
Thank you vincom for explaining the process of using both CWM 6.0.3.7 & TWRP 2.6.3.0 together. I am familiar with backups ONLY working with their original customer recovery. I didn't even think about older versions of backups (not) working with newer custom recoveries. Was there an issue working with older backups in the past?
The reason I need the old GB Radio/Modem files, because when I have to return the phone to stock & load up my old Gingerbeard nandroid, I will be able to return it back to AT&T with the original Radio files and the original Gingerbeard OS. Anywho, thank you for the GB radio. I really appreciate it!
Click to expand...
Click to collapse
u can return any phone that has any stock firmware, with our phones that would be stock jb4.1.2 and using odin would be the way to do it , link in my sig. this is assuming your carrier used the latest firmware as with att and rogers.
I am with AT&T and I never got the official ICS or JB through updates. Actually, I thought ICS was discontinue, because it was bricking phones. Thus the stock ICS & JB Roms here were ported over?
lowao said:
I am with AT&T and I never got the official ICS or JB through updates. Actually, I thought ICS was discontinue, because it was bricking phones. Thus the stock ICS & JB Roms here were ported over?
Click to expand...
Click to collapse
these are untouched full official stock firmwares( radio, recovery, kernel and apps/bloatware), just use odin and flash whatever version you want, all info is in the restore to stock sticky
lowao said:
I am with AT&T and I never got the official ICS or JB through updates. Actually, I thought ICS was discontinue, because it was bricking phones. Thus the stock ICS & JB Roms here were ported over?
Click to expand...
Click to collapse
nope, both are fine and are still available officially. You don't need gingerbread to return it.
Sent from my HTC One using Tapatalk 4
I have to go to Samsung's website and download their Kies software to upgrade to Jelly Bean right? It won't be pushed out through Settings > About Phone > System Update then?
Or you can use Odin.
Sent from my HTC One using Tapatalk 4
So if you're flashing 4.3 ROMs just use cwm? Went from twrp to cwm and back to twrp and am getting the same black boot screen on a slim 4.3 weekly.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
beachmiles said:
So if you're flashing 4.3 ROMs just use cwm? Went from twrp to cwm and back to twrp and am getting the same black boot screen on a slim 4.3 weekly.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
To properly set everything up, you need to use the recommended CWM for 4.3, do a full factory wipe, and make sure that data is formatted. Then install the ROM and boot it up. Reboot to verify it works properly. Then you can go to TWRP 2.6.0.1 or later.
I've been using twrp since release and not had any issues why do we need cwm? What's the technical reasoning.
Sent from my XT1080 using Tapatalk
Didn't work
I followed this procedure exactly and it still didn't work.
I gave it ten minutes between boots and ended up having to pull the battery each of the three times I rebooted.
Fortunately I've gotten into the habit of making a backup before flashing, so it was just a loss of 45 minutes of my evening.
I was trying to get the latest CM10.2 Stable build. Has anyone gotten this thing to flash and work as well as 10.1.3 RC2 or 10.1.3 Final? This issue started for me with the second 10.2 Nightly.
...
Just NOW began seeing the replies to the main post. I don't have ANOTHER fresh install in me: I've already had to do that twice with the 2012 Nexus7 and once with the Skyrocket in the last six weeks.