New update buggered my xoom - plz help

adamski88

Senior Member
May 5, 2012
95
3
0
Hello,

I tried updating from wingray version 155 to 156. Downloaded it etc, done the usual, installed it, installed the latest version of gapps, it said it all went fine. However once it had loaded and optimised apps, I couldnt get past the lock screen. When i put my unlock combo in it just froze. Tried rebooting a few times with no luck, just kept freezing.

I have then tried to go back to version 155 but its getting stuck at the logo screen (i think its the eos logo, with 4 different colours)

Any help would be greatly appreciated, i really need to use my xoom tomorrow!

Thanks

Adam
 

Mjamocha

Senior Member
Jul 2, 2010
1,255
765
0
Hello,

I tried updating from wingray version 155 to 156. Downloaded it etc, done the usual, installed it, installed the latest version of gapps, it said it all went fine. However once it had loaded and optimised apps, I couldnt get past the lock screen. When i put my unlock combo in it just froze. Tried rebooting a few times with no luck, just kept freezing.

I have then tried to go back to version 155 but its getting stuck at the logo screen (i think its the eos logo, with 4 different colours)

Any help would be greatly appreciated, i really need to use my xoom tomorrow!

Thanks

Adam
You might get more help, if you post your question in the ROM specific to your 155 nightly, thread.
 

adamski88

Senior Member
May 5, 2012
95
3
0
Mj, the thread is now closed.. Therefore I can't.

I cleared dalvik/cache like every other time I've updated. I know I have problems, I'm hoping for some solutions!!
 

OpKnight

Member
Jul 3, 2012
18
4
0
Philadelphia
When you get it working again...

Thanks, wish I had of just left it now :(

Is it worth going to eos 4?
Another piece of advice... Once you get your device working again perform a NAND backup so you can recover easier next time? Nightlies are a great way to see new features and bug fixes but they are still Testing software.. ;)

And yes, EOS 4 is worth going to but it is a little slow right now... give the team a little time to optimize it.