[Q] MZ604 won't boot after installing Wingray ROM

[lotus49]

I have been running CWM recovery and installing Wingray nightlies on my MZ604 without any problem for more than a year. A couple of days ago I flashed what I think was a partially downloaded ROM. This soft bricked my Xoom (somewhat unsurprisingly). I ended up in a boot loop so I used this method http://www.xoomforums.com/forum/motorola-xoom-development/18743-how-flash-sbf-rsd-method.html to get out of it.

That worked fine leaving me with a stock Xoom running 3.1.

I then unlocked the bootloader and flashed CWM Touch using adb. I then booted into recovery and flashed the universal Xoom root from here http://forum.xda-developers.com/showthread.php?t=1242241.

Again, this worked fine so now I had what appeared to be a fully functional Xoom running CWM Touch and 3.1. So far, so good.

The final step was to install a recent ROM so I booted into recovery again, flashed the latest Wingray nighly and the GApps package as I have done on numerous occasions (after doing a factory reset and wiping the cache and the Dalvik cache). This appeared to work just as it has always done but now my Xoom just sits at the M logo and nothing else happens. I can still boot into CWM Touch but my Xoom won't get past the M logo in normal boot.

Since everything seemed to work exactly as I would expect right up to the final boot, I'm somewhat mystified as to what is wrong. Can anyone give me any suggestions as to what to do next?

 

[maxvsmith]

Now I can actually help you. I saw this a day ago but did not respond yet because I did not test my method.

It's been stated by a few in the eos 4 wingray thread that nightlies 204-205 are TEST builds. Only one person said that but from what everyone else is experiencing this appears to be true. You are not alone mine was bootlooping and never getting past the splash animation either.

You don't need to fix or flash a new recovery. All you have to do is use a lower build such as 203 and you'll be fine. I'm testing some roms right now and they work fine now. I did upgrade to twrp recovery as well.

I'm sorry you went through the whole boot loader process again.

At least it's a simple fix. I'd recommend monitoring the eos4 thread and see when people post about newer builds working. I'm sure 206 will fix everything.

Best of luck.

 

[lotus49]

Thanks for the suggestion but unfortunately it didn't work. I did get past the M logo and the multicoloured splash screen appeared but it just got stuck there.

I tried going back to 203 and that didn't work. I also tried going way back to 155 (with the appropriate Google apps package) and that didn't work either.

I am starting to wonder if there is something about the way I am flashing these that isn't working. I have done it so many times that I am rather baffled as to what is going on this time but I think I shall try flashing using Odin and see if that gets me any further. It's all rather frustrating as I haven't been able to use my Xoom for days now.

 

[lotus49]

I have now fixed this although I am not absolutely sure whether my diagnosis is correct.

By flashing Wingray 203 and a very old GApps package, I got past the splash screen. The Google setup program then crashed but at least it had booted. I then tried 203 and the second most recent GApps package (dating from January I think) and it worked.

My guess is that there is some weird interaction between the most recent versions of Wingray and the most recent GApps package (and possibly other factors) but at least my Xoom now works.