condi, I just love your work, I just bought you a cold drink

since I don't drink
also as a cheer to help us find a root for the OTA ICS
Thank you very much

My wife also does not drink, for next 3(/9) months for sure she cant
BTW guys - some news regarding 'ICS rescue-backdoor' and region changer after ICS flash:
1) 'rescue-backdoor' for ICS is built-in in custom zip made with AiO, everything is correct, it looks that in new firmware there is one new condition in order to get ota notifications. Update app checks for vendor.prop values, AND ALSO for region.zip. OTA notifications can be achieved, only when vendor.prop values are corresponding with region.zip. In other words vendor.prop values needs to be for the same region as in /configs/region.zip - device region.
2) regarding region changer after ICS flash - strange, but for me it works just great. I've changed several times region in my device with ICS on it
I've made US custom prerooted ICS with built-in polish region, flashed it with polish region already.
If you want to check if OTA notifications are working correctly, then just if you have changed region to US -> change vendor.prop values to nbx03_001 and ota will be shown.
Lets summarize ICS update - for now ~1400 downloads, and few bricks, 10? more? 3 of them has been fixed already. Lets say that maybe 20 - its 0,0143%.
About bricks - the only situation I can help - when there is any proper /configs/region.zip on the device. There were few cases, when I saw from recovery.log error about opening region.zip - not exists.. This looks like that:
Code:
Verifying update package...
I:comment is 1465 bytes; signature 1447 bytes from end
I:whole-file signature verified against key 0
I:verify_file returned 0
Checking version is passed, 1 -> 111201009
minzip: file is empty
minzip: Map of '/configs/region.zip' failed
Fail to open /configs/region.zip
If you've got this in /tmp/recovery.log after flash try, then I'm sorry but for now we can't bypass that.
The only solution for now is warranty.
I have no idea how could this be possible, it looks that MAYBE there is some variant/revision of the device which can be bricked? OR MORE POSSIBILITY - just a pure user mistake?
I cant predict more, without all the revelant data, details.
Also its very hard to say what caused that, because AiO has got checks, which are looking for backed up region.zip file if its empty or not (correct one).
Another thing about bricks - I'm making a list of most common firmwares, which can fix your device (thanks to built-in ICS rescue-backdoor by me

) - but of course there got to be not-damaged region.zip on the device!
Another scenario which came through my mind - when region is going to be changed - new region is being copied to /data/local/tmp, maybe that few cases where caused by not enough free space?
-- I've almost done implementing check for the free space, for the size of region.zip on the device in few locations in the code, before device reboot - this could save user from getting a brick.
Next thing is that every user who is not familiar with all the flashing custom rom thing, then just check first post, there are few youtube videos there made by me, which shows step by step how it should look! It would be good to spend a few minutes more and learn how it should looks.
br
condi