[Verizon] Cwm 6.0.0.1/4/5 warning!!! Don't flash it!!

scary alien said:

I think I've got all the kinks out of it (no recent application error reports that I haven't addressed in the most recently published version). I've got some ideas for additions and enhancements, but nothing imminent to be released.

Click to expand...

As a Gnex user, I can say it was pretty much a RC from the day it was launched. One of the most handy apps in my toolbox quite honestly. :smokingsomb:

Sure hope Koush gets this worked out. A lot of people depend on him...

I used CWM for 2 years and even tried the Touch version. One go-round with TWRP and I was hooked.

And now 2.2 is out in flashable zip form, allowing you to name your backups from within recovery itself.

+1000. TWRP ftw!

Hey guys, by the way, I updated my AFV app last night to support the verification of TWRP Nandroid backups.

(I didn't have time to rebuild the donate version of the app--I hope to get that done tonight (so, no yelling at me, Steven ))

Thanks!

this is the touch version that causing all the may-lay right?

kinfolk248 said:

this is the touch version that causing all the may-lay right?

Click to expand...

The newer 6.x versions yeah. I think it's all straight now, but haven't tested my self.

I'm using CWM 6.0.0.5 and made 2 Nandroids yesterday - both restored just fine. Also flashed a power menu + volume to skip MOD and that worked just fine too.

6.0.1.0 is now available. I personally did not have any issues with previous versions and I made a successful backup using the latest as well. Also had no issues flashing the 7/19 version of Bugless Beast. Fantastic ROM by the way. Zero problems so far.

Just updated to 6.0.1.0, testing now.

Booted just fine, no issues.

Man I wish I had seen this before I upgraded my CWM... stuck and can't boot into recovery now (dead android pops up.) Everything was going well until I flashed a new ROM and after 3 days of using it my phone died. Luckily I still have my old Incredible in good shape so thats what I'm using until I figure this out.

Whats a good link to walk me through this so I don't screw up permanently? I might just go back to stock at this point... my phone is too important to my work not to be reliable. (I know... I'm overexagerating...it is just a bad feeling to lose use of your phone.)

Shachren said:

Just updated to 6.0.1.0, testing now.

Booted just fine, no issues.

Click to expand...

Just saw this is the new version. Anyone else have success?

dreadnatty08 said:

Just saw this is the new version. Anyone else have success?

Click to expand...

I made and flashed 2 Nandroids with no issue. I'm on 6.0.1.0 Touch.

I only see a couple people with this problem.

Most people are on 6.x no problem.

Hi,

I flashed Codename Android Jelly Bean using CWM Recovery 6.0.1.0 and had no issues, thank god!

OK, I'm going to ask a similarly flavored question as I did in the JB warning sticky.

The title of this thread warns against using CWR 6.0.0.x. Now there is CWR 6.0.1.0 which DoctorEyeSight had no problems with and it is also included in ScaryAlien's app (BTW SA, that app F'n ROCKS!!!)

So is this caution still valid, and/or does this still need to be a 'sticky'?

As I said in the other thread, I have only owned this phone for about 72 hours. But I rooted it last night which included installing CWR 5.8.x.x, made a nandroid, but when I installed Rom Manager and had it flash CWR, it was 5.5.x.x and I was skeered to flash the touch recovery within that app because of this thread. And 5.5.x.x would not restore my nandroids from 5.8.x.x, but that is why I said Scary's app rocks.

p.s. my other reason is because I, like most of you prefer to do my wiping, formatting, and flashing while actually booted into recovery but I sure like using Rom Manager to create my backups, so I can give them a custom name.

I'll say one thing, the newest update to rom manager itself caused a .nomedia file to make all my media disappear from the stock gallery. Thought I lost everything for a few days there.

Steven58 said:

Still problematic for the gnex. TWERP world great.

Click to expand...

Fixed it for you Steven.

My experience tonight has been different using CWM (ClockworkMod Recovery) and RM (Rom Manager). Though my situation may be different and a YMMV situation. I took all my MBP files and transferred them from my A855 to my I515. And ScaryAlien's app has been a gr8 help as well.

And just as a note, I'm only using the stock 4.0.4 'rom' rooted. I have yet to flash a custom rom.

I had already flashed the CWM touch 5.8.x.x and made a few backups with that. Then I restored via MBP (MyBackupPro) my RM and license. RM wanted me to flash the latest CWR (albeit non touch). So I did and then used Scary's to flash the CWM touch 6.0.1.0, irregardless of what RM reported to me because it wanted me to pay more $$ to do so. Rebooting into recovery from RM (Rom Manager) was a success into CWM touch 6.0.1.0 and also showed all my backups created with CWM so far.

And then I decided I would try to do a 'dirty' flash of CM 9 and the gapps for the i515. Using RM, I selected "install ROM from sdcard'; and selected the cm9, gapps and such, selected the 'dirty' options, just wipe dalvik and cache, but not do a full wipe.

Well, it sat there and wouldn't quite (after five minutes or so) get past the CM9 bootanimation. So I pulled the battery for about 60, put it back in, booted straight to recovery, restored (via CWM 6.0.1.0 touch) my latest backup, and now my phone is back where it was.

Moral of the story?

Koush was the first one to get 'root' on an Android phone. Google it. He is the developer of CWM and RM. Sometimes there might be a few hiccups, but it is his stuff that will always work.

Everyone else is potentially a twerp.

Just saying . . . . .

From my experience, I have no problems at all with CWM 6.0.1.0 on the I515, maybe Steven . . . . . . . . . . . .

Steven58 said:

I'm running custom roms with JB, fyi.

Click to expand...

Understood. I've got a lot of reading and catching up to do. I haven't even had my Gnex for a week yet. Researching JB roms all over the place, can't wait to flash one. Just thought I'd post my experience so far in relation to this issue.

Thanks for all your info. I'm off to check your JB rom poll right now. . . .

Steven58 said:

Feel free to hit me up if you have any questions. I've pretty much flashed the lot of them and am on sourcery now. Very configurable. Very.

Click to expand...

Many thanks. I might do just that.

[offtopic]I flashed the sourcery rom last night, but for some reason I didn't have everything working, nor all the features. My fault I am sure. I did a clean flash, but after putting the JBS 2 and gapps in the list, I also put an inverted gapps in the list. Made for some wonky stuff, like the phone app not showing up. So I just flashed the rom and gapps again. Then I think I sabotaged myself more by using MBP to restore .apks and data. At the end of the day I was able to configure JBS fairly well, but I think there were some things missing from its' tools, etc., probably because of the way I did my flash and apps restore. I like. I then did a clean flash of BAMF today and it took much better, but it lacked the 'screenshot' option in the power menu and I had to install apex over the top. Plus it lacks alot of the features that my screwed up flash of JBS had. So I'm going to try JBS again.[/offtopic]

However, I did all this using Rom Manager and CWM touch 6.0.1.0. I did have to upgrade RM to the latest version and saw in the "what's new" dept that is is updated for JB and it removed the putting of a .nomedia file in the wrong place.