Root Need advice from more expert DX'rs (VS, Bo, Col, etc)..tia

[Steven58]

Ever since I flashed .602 (stock rooted) I've not been able to get into cwr for about a week.

I was advised to flash an older version, but Rom Mgr wouldn't let me do that as I've cleared cache.

The dev upgraded cwr several times, last week, one of them worked when I started the phone plugged in. No longer does that work.

I thought the problem may be with my rom, so I d/l'd .602 sbf and rsdlite 5.x, thinking I'd start over to see if that would fix cwr.

However, if that doesn't work, I will not be able to restore my data partition, because I can't get into recover to do it, so I'm holding out on that option.

Here is my question. Is anyone else, who is on .602 rooted, having the same difficulty? I'm trying to determine if the issue is with the rom or the cwr app BEFORE I SBF restore. If it is the app, I won't be able to get my data back.

Flying without cwr is better, to me, than flying without an ability to restore my data partition.

Any wisdom would be appreciated.

TIA

Steven

 

[SimsDelt]

From what I understand it is the app. I'm on CM7 GB kernel edition and couldn't get into cwr at all till the latest update. I've read elsewhere it will work with the D2 bootstrapper if you are on rooted 602 or a blur based ROM (apex, shuji, etc).

 

[Steven58]

From what I understand it is the app. I'm on CM7 GB kernel edition and couldn't get into cwr at all till the latest update. I've read elsewhere it will work with the D2 bootstrapper if you are on rooted 602 or a blur based ROM (apex, shuji, etc).

Nah, I'm on .602 stock blur rooted. No go. This helps however. Ty.

Steven

 

[bouchigo]

Greavous was having similar issues as you Steven, he ended up sbf'ing and got his setup going again.

Koush is aware of the issues CWR is causing on .602 based Roms, so I suggest you use the D2 boot strapper and not Rom Manager until he sorts it out.

Read this:
https://plus.google.com/103583939320326217147/posts/VSdhDWoA59Z

 

[VoidedSaint]

have you tried the d2 bootstrapper?

have you tried using titanium backup to restore a previous version of rom manager?? i wonder if its the newest version of rom manager

 

[bouchigo]

have you tried the d2 bootstrapper?

have you tried using titanium backup to restore a previous version of rom manager?? i wonder if its the newest version of rom manager

Wonder no more, I mentioned it in my previous post.

 

[Steven58]

Restoring a titanium backup does not help, neither does D2 bootstrap. I am unable to access cwr at all, which is why I am reluctant to SBF. If I SBF and still can't get into cwr, then I've lost my desktop setup and would have to set it up from scratch. Or i could just wait until cwr works and restore data then. I don't know. Frustrating.

 

[trophynuts]

Steven. So other than you not being able to get into CWR everything else is working fine? If so i would probably just ride it out until hopefully something is figured out with CWR. I've been on the stock .602 build and i didn't have any problems however i never used Rom Manager. I only used the D2 bootstrap. Now i'm back on CM7 and CWR seems to be working for me. He did push another update today for it though.

on a side note.......what does this matter anyways you'll be buying a Bionic on Thursday anyways lol jk

 

[Steven58]

No bionic. Nexus prime here,

 

[Steven58]

There's a cwr update. My latest G plus to dev:

DX here. Bootstrap - d2 bootstrap, latest cwr and rom mgr premium. With latest cwr, d2 bootstrap works. Rom Mgr. No. I can live with that for now.

 

[trophynuts]

thats cool.

 

[OnaDroidXhigh]

just checked mine out a few minutes ago and it works fine for me.

 

[Steven58]

Well, it's now a known issue, fwiw.

 

[VoidedSaint]

yeah i saw it on koush's post on G+ last night and i was like well im sure steven already knows about this

 

[Steven58]

I contributed to that thread, yeah.

 

[bouchigo]

I contributed to that thread, yeah.

And that's why I don't use Rom Manager.......lol......No, that's not really why, I've just always preferred the DX or D2 bootstrapper

 

[Steven58]

And that's why I don't use Rom Manager.......lol......No, that's not really why, I've just always preferred the DX or D2 bootstrapper

Awhile back it was also unstable for DX and I also stopped using it. Then it became stable. I got used to again, like a drug. I became Rom mgr dependent again. I strayed.

 

[imronburgundy]

FWIW, I used the .602 sbf, then tried to get into d2 bootstrap, but kept getting a weird error message. Then realized I wasn't rooted. So did the one click gb root method and all is well.

 

[Steven58]

I tried to go that way, but I am unable to root .602 sbf. It says it can't recognize my phone. ...yes, I am in charge only mode. I am so frustrated with .602, now, that I can't even speak.

 

[GandalfTehGray]

Ouch sorry steven, go the long way around from .340?

 

[Steven58]

Ouch sorry steven, go the long way around from .340?

Yup.

 

[woodstorm]

I can only reach 5.0.2.0 via RM. D2 Bootstrap brings me to 2.5... Trying out a different ROM right now (not .602 based) and the issues are still there. How can there be 2 different cwr running on the phone. Shouldn't D2boot be going to 5.0.2.0?

 

[Steven58]

I can only reach 5.0.2.0 via RM. D2 Bootstrap brings me to 2.5... Trying out a different ROM right now (not .602 based) and the issues are still there. How can there be 2 different cwr running on the phone. Shouldn't D2boot be going to 5.0.2.0?

Well, it seems as if 602 and cwr don't like each other.

 

[VoidedSaint]

maybe thats how moto configured the .602 update... nothing good ever comes out of these updates moto sends

 

[Steven58]

^^ my thoughts exactly.. thinking of going backwards to .596 again.