OK, well still no luck - I am stuck in Custom Recovery hell - my V1 Cube only boots to recovery, does nothing more. I have no adb access as it isn't booting so I am stuck here. Not having much luck finding info on how to connect to the UART pins either. I have a USB to serial adapter here but not sure if it's a good idea to do much poking around. I have a USB to UART cable on the way that should get me all I need.
Hopefully the cable will give me some low-level access thru UART and perhaps I will be able to revive this Cube eventually. I will post any further info I can gather here. Might be selling this V1 cheap if I can get it fixed!
In the meantime UPS just delivered my new V2 Cube, I'll be running home at noon to connect this baby and get it going. From just the unboxing I only see the one difference: the IR Blaster has 2 outputs (been waiting for that!). Be interesting to know if it will do a firmware update once I get it setup. I'll post more info as need be ....
I think I can answer my original question though, I found the answer within the GTVHacker secure boot file:
Code: Select all
ui_print("- Moving OTA Certs to prevent OTA updates");
run_program("/system/xbin/busybox", "mv", "/system/etc/security/otacerts.zip", "/system/etc/security/otacerts.zip.old");
So it looks to me like root access, and then move otacerts.zip.old back to otacerts.zip should resolve the issue of how to reverse the changes that prevent OTA updates. If I could get my V1 Cube to boot I would give it a shot......
Will post more when I know more.