5,605,120 Members 37,475 Now Online
XDA Developers Android and Mobile Development Forum

[Q] "wingray" ClockworkMod?

Tip us?
 
henryhu
Old
#1  
Junior Member - OP
Thanks Meter 2
Posts: 8
Join Date: Jul 2010
Location: New York
Default [Q] "wingray" ClockworkMod?

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?
 
twofourturbo
Old
(Last edited by twofourturbo; 13th January 2012 at 11:31 PM.)
#2  
Junior Member
Thanks Meter 10
Posts: 25
Join Date: Feb 2011
Location: Utah


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.
 
rmm989
Old
#3  
Junior Member
Thanks Meter 1
Posts: 14
Join Date: Jan 2012
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.
 
MeridianSun
Old
#4  
MeridianSun's Avatar
Member
Thanks Meter 6
Posts: 56
Join Date: Apr 2011
Same here. And my Xoom was stock. I've never tried any mods until now.

Sent from my DROID RAZR using Tapatalk
 
henryhu
Old
#5  
Junior Member - OP
Thanks Meter 2
Posts: 8
Join Date: Jul 2010
Location: New York
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...
 
drnoir
Old
#6  
Member
Thanks Meter 1
Posts: 79
Join Date: Oct 2007
Location: Mexico city
Quote:
Originally Posted by henryhu View Post
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...
 
henryhu
Old
#7  
Junior Member - OP
Thanks Meter 2
Posts: 8
Join Date: Jul 2010
Location: New York
Nothing new, just OTG, sorry...
 
kerry_xu_cs
Old
(Last edited by kerry_xu_cs; 14th January 2012 at 01:10 AM.)
#8  
kerry_xu_cs's Avatar
Member
Thanks Meter 13
Posts: 67
Join Date: Feb 2010
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
The Following 3 Users Say Thank You to kerry_xu_cs For This Useful Post: [ Click to Expand ]
 
megabiteg
Old
#9  
megabiteg's Avatar
Senior Member
Thanks Meter 238
Posts: 1,136
Join Date: Apr 2010
Location: USA
Quote:
Originally Posted by kerry_xu_cs View Post
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
MSG Megabite

"Perfection is my life goal, excellence will be tolerated... WHOA!!"


Stock, Un-rooted T-Mobile HTC One
 
whatsamod
Old
#10  
Junior Member
Thanks Meter 5
Posts: 19
Join Date: Apr 2010
Quote:
Originally Posted by henryhu View Post
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?

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

Advanced Search
Display Modes