[Krymsyn]

Please refer to THIS LINK for a much easier fix. Have fun!


Follow at your own risk.
This was done with all .602 in mind.
Pretty sure that 2nd-init based ROMS are going to need a different workaround.

**Successfully recreated my success by following the steps in post 2.
Ignore all of this in post 1.**


So, in pursuit of isolating anything that could be of help in the process of fixing the CWR flashing for the Droid X...

SBF'd using the .602 Official SBF from TBH app.
Ran 1 click root app 1.03 from psouza4.
Installed Rom Manager + Premium 4.4.0.6.

Flashed 5.0.2.0 (Droid X Option), attempted to reboot recovery from RM.
Phone rebooted as if normal.

Fixed Permissions.
Reflashed 5.0.2.0 (Droid X Option), attempted to reboot into recovery from RM.
Phone rebooted as if normal.

Downloaded D2 Recovery Bootstrapper.
Attempted to reboot into recovery from D2 Bootstrapper (Did NOT click Bootstrap Recovery).
Phone rebooted as if normal.

Flashed 5.0.2.0 (Droid X 2nd-Init Option), attempted to reboot recovery from RM.
Phone rebooted as if normal.

Reflashed 5.0.2.0 (Droid X 2nd-Init Option), attempted to reboot recovery from RM.
Phone rebooted as if normal.

Attempted to reboot recovery from D2 Bootstrapper (Did NOT click Bootstrap Recovery).
Phone rebooted as if normal.

Flashed 5.0.2.0 (Droid X Option), attempted to reboot recovery from RM.
Phone rebooted as if normal.

Ran D2 Recovery Bootstrapper, clicked Bootstrap Recovery and then Reboot Recovery.
Phone booted into CWR 2.5.0.8

Cleared Download Cache
Reflashed 5.0.2.0 (Droid X Option), attempted to reboot recovery from RM.
Phone rebooted into CWR 5.0.2.0!
*NOTE : Seemed to me the RM took a second longer to reboot the phone at this point, and I got a notification just before reboot about RM being granted SU permissions. I don't remember this from the earlier tests.

Rebooted.
Attempted to reboot recovery from RM.
Phone rebooted into CWR 5.0.2.0.
*NOTE : Again, phone seemed to reboot just a tad slower, and I got the SU permissions notification for RM again.

Rebooted.
Attempted to reboot recovery from D2 Bootstrapper (Did NOT click Bootstrap Recovery).
Phone booted into CWR 5.0.2.0.

Rebooted.
Attempted to reboot recovery from RM.
Phone rebooted into CWR 5.0.2.0.
Wiped Data / Factory Reset
Wiped Cache
Wiped Dalvik Cache
Flashed .602 based Rom (Shuji 2.1)

Rebooted.
Ran through setup process.
Downloaded and installed ROM Manager + Premium 4.4.0.6
Attempted to reboot recovery from RM.
Phone rebooted as if normal.

Cleared Download Cache.
Reflashed 5.0.2.0 (Droid X Option), attempted to reboot recovery from RM.
Phone rebooted as if normal.

Reflashed 5.0.2.0 (Droid X Option), attempted to reboot recovery from RM.
Phone rebooted as if normal.

Attempted to reboot recovery from D2 Bootstrapper (Did NOT click Boostrap Recovery).
Phone rebooted as if normal.

Attemped to reboot erecovery from D2 Bootstrapper, clicked Bootstrap Recovery and Reboot Recovery.
Phone rebooted into CWR 2.5.0.8

Rebooted.
Cleared Download Cache.
Reflashed 5.0.2.0 (Droid X Option), attempted to reboot recovery from RM.
Phone rebooted into CWR 5.0.2.0

Rebooted.
Attempted to reboot recovery from RM.
Phone booted into CWR 5.0.2.0.

Rebooted.
Attempted to reboot recovery from RM
Phone booted into CWR 5.0.2.0.

Rebooted.
Attempted to reboot recovery from D2 Bootstrapper (Did NOT click Bootstrap Recovery).
Phone rebooted into CWR 5.0.2.0.
Wiped Cache.
Flashed ROM Theme zip. (Skynet for Shuji 2.1)

Rebooted.
Theme applied Successfully.
Attempted to reboot recovery from RM.
Phone rebooted into CWR 5.0.2.0.

Rebooted.
Will spend some time setting things back up. I'll pop back into recovery occasionally to make sure things are sticking.
Success.

 

[Krymsyn]

Tested successful. Green is reported to be optional.

SBF to 602, root, install RM and D2 Bootstrapper...
D2 Bootstrapper, Click Bootstrap Recovery,
Reboot Recovery.
Assuming you get 2.5.0.8, reboot
and flash Droid X option 5.0.2.0

Reboot recovery from RM.
If you don't get 5.0.2.0, try wiping download cache, flashing again and reboot recovery from RM.
If you do get 5.0.2.0, flash whatever 602 ROM you're using, following the instructions for the ROM.
Boot into it, run setup, and install D2 Bootstrapper and RM.
Repeat D2 Bootstrapper instructions to get into 2.5.0.8.
Reflash Droid X Option 5.0.2.0.
You should have 5.0.2.0 when you reboot recovery from RM now.

I was able to Fully Restore a Nandroid Backup from before all of my SBFing and testing tonight, when I was having the hanging at boot logo issue...
The problem has stayed dead and I have successfully booted into CWR 5.0.2.0 using RM's "Reboot Recovery" option.

 

[Droidx0351]

Where did u get that 1 click root app to work on the x by psouz4 for the new gingerbread 602. The only one that I know of is by using linux way that was just released by p3 drod.

Sent from my DROIDX using Tapatalk

 

[Krymsyn]

The link for that is actually HERE. Steps are the same no matter what Motorola phone you're on.

 

[BrentBlend]

If you can add some sort of tl:dr I maybe able to stick this...this is interesting

 

[Omega Blaze]

I would try the second post but i'm on a milestone x by alltel..

Should i be able to update to .602 if i SBF to my stock alltel rom (2.2.1)??

 

[CBlaze]

Might be off topic, but I had to do the same thing on the OTA GB for the D2, flashed recovery 5.0 in Rom Man, rebooted to recovery and would reboot as normal. Installed D2 Bootstrapper. Flashed bootstrapper, rebooted to recovery booted to CWR 2.5. Rebooted, Flashed 5.0 with Rom Man. All working, Everything I tried it would stick coming from Rom Man. at first.

 

[Krymsyn]

If you can add some sort of tl:dr I maybe able to stick this...this is interesting

Thats sorta what the second post is... I just am not going to SBF AGAIN tonight to try it. But someone else that may be on the road to doing it... Have at it. =D

I lied, I did do it all over again.

 

[Omega Blaze]

Might be off topic, but I had to do the same thing on the OTA GB for the D2, flashed recovery 5.0 in Rom Man, rebooted to recovery and would reboot as normal. Installed D2 Bootstrapper. Flashed bootstrapper, rebooted to recovery booted to CWR 2.5. Rebooted, Flashed 5.0 with Rom Man. All working, Everything I tried it would stick coming from Rom Man. at first.

I just flashed the bootstrap2 recovery. Still gets froze at the M logo.

 

[BrentBlend]

The only reason I say that is a lot of X users are having recovery issues.
Koush is trying diligently to remedy this...
If anyone can find a sure-fire way to fix/avoid this I can guarantee a stuck thread until Koush releases more info.

 

[Omega Blaze]

Thats sorta what the second post is... I just am not going to SBF AGAIN tonight to try it. But someone else that may be on the road to doing it... Have at it. =D

Would i be able to?

 

[Krymsyn]

I would try the second post but i'm on a milestone x by alltel..

Should i be able to update to .602 if i SBF to my stock alltel rom (2.2.1)??

Not sure how to help you mano, I was under the impression that the SBF files were Verizon specific. What version Android are you running currently? Screenshot of About Phone maybe?

 

[Krymsyn]

Would i be able to?

Assuming you have all the files I listed, working on a Verizon X... the TBH .602 SBF, D2 Recovery Bootstrapper and Rom manager.
Just follow the steps in post #2 and see where you get.

 

[Omega Blaze]

I'm running 2.3.5 i think it is..

Liquid 2.6

I'm currently STUCK at the M logo completely because i just used droid2bootstrap so i can't take a screen shot lol..

I may have to SBF now..

 

[Fox_Dye]

I've been using the new recovery since it came out. I am running shuji right now and apex before. Didn't do anything special just flashed with rom manager and went to bootstrap and hit boot to recovery. Simple as that never had any problems. I use the droid x bootstrap not the d2 don't know if that makes a difference or not. Wish I could help more.

Sent from my DROIDX using Tapatalk

 

[Krymsyn]

I'm running 2.3.5 i think it is..

Liquid 2.6

I'm currently STUCK at the M logo completely because i just used droid2bootstrap so i can't take a screen shot lol..

I may have to SBF now..

If you're on a 2nd-init based ROM, yeah, D2 Bootstrap is going to kick your behind.

Go ahead and follow my instructions in the second post... I'm going to SBF again and try it all over, same steps, from post 2. With any luck it'll work just fine.

 

[BrentBlend]

clockworkmod Koushik Dutta
My favorite user of all time is @asotelo23: http://t.co/2ylLpbc

 

[Krymsyn]

Wait, if you're on the Alltel network, I dont know if my instructions will still apply. Should, just sub in your SBF and any updates for the verizon ones.

 

[Omega Blaze]

Ok let me get this correct..

I need to go back to SBF back to stock alltel froyo..(2.2.1)

and then update to .602?

Or find the stock Verizon SBF and SBF back to froyo

and then update to .602?

 

[Omega Blaze]

Wait, if you're on the Alltel network, I dont know if my instructions will still apply. Should, just sub in your SBF and any updates for the verizon ones.

That's where i'm confused at.

Alltel didn't receive gingerbread OTA yet.

So i'm thinking i should sbf back to my stock alltel rom..

and then update to Verizon's .602 maybe..

I heard that switching base bands may mess something up..