KSmithInNY
#winning
- Oct 7, 2009
- 3,536
- 1,441
- 0
ok so im thinking here ........
take update.zip from v8 or v9 (preferably v9) and do the following:
Replace the meta data with the meta data from VC, Replace the build.prop.p with the one from VC, and the radio with VC. Wondering if that would result in the recovery thinking your flashing VC over VC, which it might be more inclined to do then rolling back but in reality ... it's rolling you back but you're keeping the VC radio.
Or make an update.zip for VC BUT the recovery is replaced by V9 recovery image so when you flash everything is VC except recovery which is V9 which is more hacker friendly.
Of course, neither option would work if the VC recovery is unwilling to flash a VC update.zip overtop of it's self. My preference though would be a roll back to V9 while keeping VC radio though cause then then Z4 would work.
take update.zip from v8 or v9 (preferably v9) and do the following:
Replace the meta data with the meta data from VC, Replace the build.prop.p with the one from VC, and the radio with VC. Wondering if that would result in the recovery thinking your flashing VC over VC, which it might be more inclined to do then rolling back but in reality ... it's rolling you back but you're keeping the VC radio.
Or make an update.zip for VC BUT the recovery is replaced by V9 recovery image so when you flash everything is VC except recovery which is V9 which is more hacker friendly.
Of course, neither option would work if the VC recovery is unwilling to flash a VC update.zip overtop of it's self. My preference though would be a roll back to V9 while keeping VC radio though cause then then Z4 would work.