FORUMS

XDA Recap: This Week In Android (Apr 18 – 25)

Here in the digital XDA newsroom, we spend our days pouring over an average of … more

Sunday Debate: Custom ROMs vs. Modular Tweaks

Join us in a fun Sunday Debate on Mods and ROMs. Come with your opinions and feel free to … more

AOSP 5.1 Lollipop for Nexus Q

Google Nexus Q is an intriguing device released with Android 4.0 Ice Cream Sandwich. It was abandoned by … more

XDA Picks: Best Apps of the Week (Apr 17 – 24)

Apps are at the front and center of any smartphone experience, and with over a … more
Post Reply Subscribe to Thread Email Thread

[Q] "wingray" ClockworkMod?

13th January 2012, 11:03 PM |#1  
OP Junior Member
Flag New York
Thanks Meter: 4
 
More
I'm trying to flash the OTA with CWM, and the assert
Code:
assert(getprop("ro.product.device") == "wingray" ||
       getprop("ro.build.product") == "wingray");
failed. I suspect that's caused by "stingray" here and there in /default.prop and other places in CWM.

I have flashed the original boot partition and I have checked all the asserts for patches, and I'm sure that they would not fail with "applypatch -c".

So is there any "wingray" version of CWM? So I can flash it and then maybe I can flash the OTA?
 
 
13th January 2012, 11:18 PM |#2  
Member
Flag Utah
Thanks Meter: 13
 
More


Currently sitting in the same boat. I have a US Wifi Only Xoom sitting on HTK75D. I did have a custom kernel Installed which i removed my installing "update_US-Xoom-WiFi-3.2.1-HTK75D_stachre_v02.zip" which just installed the factory boot.img that removed the custom Tiamat kernel. Once there I attempted to install the OTA and receive your same Build.Prop Issue. I first attempted with CWR and then proceeded to Install the Tiamat Recovery that is available on http://www.droid-life.com/2012/01/13...e-zip-for-you/ and still in the same boat.
Hope we can figure this out and get some tasty ICS soon.
Last edited by twofourturbo; 13th January 2012 at 11:31 PM.
13th January 2012, 11:41 PM |#3  
Junior Member
Thanks Meter: 1
 
More
Subscribed b/c I have the same problem, though I had the stock kernel. Also had problems getting it to boot into the CWM recovery vs the stock recovery, but when I'd get it into CWM, this is the error I'd get.
13th January 2012, 11:48 PM |#4  
MeridianSun's Avatar
Member
Thanks Meter: 8
 
More
Same here. And my Xoom was stock. I've never tried any mods until now.

Sent from my DROID RAZR using Tapatalk
14th January 2012, 12:16 AM |#5  
OP Junior Member
Flag New York
Thanks Meter: 4
 
More
Finally I gave up CWM and went to stock recovery.
I grabbed stock rom from

developer.motorola.com/products/software

"Build HWI69 for US Retail"
, extracted recovery.img,
and flashed recovery in fastboot mode to it.

Then I flashed the OTA in stock recovery and then flashed back CWM recovery...
Now it seems to work fine... I've gained root access again by flash su-install.zip...
14th January 2012, 12:28 AM |#6  
Member
Flag Mexico city
Thanks Meter: 1
 
More
Quote:
Originally Posted by henryhu

Finally I gave up CWM and went to stock recovery...

Then I flashed the OTA in stock recovery and then flashed back CWM recovery...
Now it seems to work fine... I've gained root access again by flash su-install.zip...

Did you use OTG or SD card for flashing the ICS OTA? Or maybe something more exotic you can share with us...
14th January 2012, 12:46 AM |#7  
OP Junior Member
Flag New York
Thanks Meter: 4
 
More
Nothing new, just OTG, sorry...
14th January 2012, 01:08 AM |#8  
kerry_xu_cs's Avatar
Member
Thanks Meter: 13
 
More
since you are using CWM recovery you can modify the OTA package without worrying the signature issue.

so,

1) extract the zip package to a folder.
2) open META-INF/com/google/android/
3) use any text editor you have to edit the updater-script file.
4) remove the assert statement
5) repack the folder into a zip package

then flash it with CWM recovery, and it will probably work

====
didn't see you following posts. nvm
Last edited by kerry_xu_cs; 14th January 2012 at 01:10 AM.
The Following 3 Users Say Thank You to kerry_xu_cs For This Useful Post: [ View ]
14th January 2012, 01:51 AM |#9  
megabiteg's Avatar
Senior Member
Flag USA
Thanks Meter: 238
 
More
Quote:
Originally Posted by kerry_xu_cs

since you are using CWM recovery you can modify the OTA package without worrying the signature issue.

so,

1) extract the zip package to a folder.
2) open META-INF/com/google/android/
3) use any text editor you have to edit the updater-script file.
4) remove the assert statement
5) repack the folder into a zip package

then flash it with CWM recovery, and it will probably work

====
didn't see you following posts. nvm

Are you 100% sure that this will work fine?

Sent from my PG86100 using Tapatalk
14th January 2012, 03:25 AM |#10  
Junior Member
Thanks Meter: 5
 
More
Quote:
Originally Posted by henryhu

Finally I gave up CWM and went to stock recovery.
I grabbed stock rom from

developer.motorola.com/products/software

"Build HWI69 for US Retail"
, extracted recovery.img,
and flashed recovery in fastboot mode to it.

Then I flashed the OTA in stock recovery and then flashed back CWM recovery...
Now it seems to work fine... I've gained root access again by flash su-install.zip...

Was debating this, just wondering if it is worth the time and effort?
Post Reply Subscribe to Thread

Tags
project, xoom
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes