I have same problem as parrotheadmjb, Google Play won't install and I am unable to sideload any system app due to apk signatures.
History: 2.1 -> 3.1 UserDebug -> 3.1 Final (very first build posted!)
I've tried all I can think of with various results, but I don't think I can go any further without some good advice.
1) I've done all shenangians with apk files I could think off, I've even tried resigning youtube app for kicks. Thats the only thing I am need, since they removed most of features from web leanback version. Didn't get anywhere.
2) Restore recovery is out of the window, simply because this function is not supported on production builds (final). Also at this point its strange that /var/tmp is not writeable by all. Still you can push it elsewhere, but it will not flash this build bootloader.
3) Yesterday got bored so I tried also
http://forum.gtvhacker.com/troubleshoot ... ic404.html - in short connect physically to /cache and put command file for recovery.
My reasoning was that a) recovery is till present, adb reboot recovery works just fine. b) I've never soldered anything more complicated than what couldn't have been solved by duck type. Was I surprised with size of those resistors... in picture they look 10x bigger. Anyway I managed cleanly to connect wires, much to my surprise.. I did pull of one of pads, but it left a little copper wire from trace luckily.
After everything further failed in that thread, it wont detect command file on boot and holding connect button just starts recovery wipe-data command after Fn+Left Arrow, any other combination wouldn't work.
Examining wipe log (which it leaves on "cache"), I found out that it expects 3 partitions on "cache" device (internal-usb1), so I created three partitions, which revue immediately used for directories /home and /tmp. Still it would not take update.zip from /tmp. With adb reboot recovery it started recovery process, but ended up with gray triangle in seconds. Logs on cache indicated that box didn't find what to do. Some logs from "cache device" partition 1:
If I hold connect and then press left arrow:
Code: Select all
I:Boot command: boot-recovery
I:Got arguments from boot message
Command: "recovery" "--wipe_data"
adb reboot recovery or adb reboot recovery --update-cache..... or ... adb reboot "recovery --update-cache..."
Code: Select all
I:Boot command: boot-recovery
Command: "/bin/recovery"
ro.recovery.version=3
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
persist.service.adb.enable=0
ro.macaddr=121212121212
ro.factorytest=0
ro.serialno=0000GB000000
ro.bootmode=recovery
ro.baseband=unknown
ro.carrier=unknown
ro.bootloader=5.303-g49cc594d
ro.hardware=logitech_ka5
ro.revision=0
persist.init.boot.token=1
ro.boot.token=1
init.svc.recovery=running
init.svc.console=stopped
Still nothing to do, trying auto recovery...
I:Mounting DATA:
I:Mounting CHROME:
I:executing /sbin/auto-recovery
auto-recovery v1.02
At one point it appears I got somewhere, since there was also file last_install with:
but it looks like update.zip was already gone from previous reboots
and I don't have idea at which point this happened.
That's about time I stopped trying and reason for this long wall of text, but I am sleep deprived at work now - so I got to look busy.
Any ideas or help, or advises would be welcome. I don't care about Revue that much actually - I am super surprised that I didn't mess up soldering, I am just inclined to finish this one way or another.
Thanks,
Yanex