Droid Stick A2 Firmware With Google Play Fix
If you have read my previous review of the Droid Stick A2, I was pretty upset about Google Play since I could not install most of the apps. This is now fixed, and Kimdecent has released a firmware upgrade.
Here’s how to upgrade:
- Download g02refDongle-ota-20130201.rar
- Extract it in your PC, and copy the files (g02refDongle-ota-20130201.zip and uImage_recovery) to the root of your microSD card (Formatted as FAT32)
- Insert the microSD into Droid Stick A2
- Boot the mini PC normally, and launch the “Upgrade” app
- Select Local Upgrade, then select g02refDongle-ota-20130201.zip and click on Reboot and Install Package
- Droid Stick A2 will reboot, and it should start upgrading Android.
- Done
Since I’ve been messing up with Android and broken something, “Reboot and Install Package” does nothing for me (some permissions issues with /cache/recovery/command), so I could not verify this works or not. Finally, I could install it on the first version of Droid Stick A2 and Google Play now works fine.
In the other, newer, stick I’ve bricked (or sort of bricked), I’ve tried to enter recovery mode by shorting the two large pads below TP14 (See pic), and it does seem to enter a special mode, but my TV does not detect any video signals.
Works good for the first sample
You can root the stick with the same zip of prometheus
http://www.armtvtech.com/armtvtechforum/viewtopic.php?f=132&t=1276
ADB is lock
@Naismith
Yep, I could also use the Prometheus method, but after I lost Wifi. I don’t know if this is related, or if it is something I did after. Does you Wi-Fi still work?
My wifi work fine.
Try to make a full restore in settings
@Naismith
It looks like I’ve now bricked another device. I used “update_Superuser.zip”, it failed to create the symlink to su, and for some reasons I don’t have access to the mouse or keyboard on this device, and it has reverted to Android UI for phones.
Edit: A reboot fixed that, and my second attempt at apply the root method succeeded. Not sure what caused that.
Any one knows if multichannel audio 5.1 passthrough works on this device?
I am not sure but i think Amlogic AML8726 are the only android devices capable of dts passthrough through HDMI?
Can you confirm?
@Valter84
I think whether DTS passthough support is mainly a license issue. I can’t test it myself since my TV does not support it.
In the other, newer, stick I’ve bricked (or sort of bricked), I’ve tried to enter recovery mode by shorting the two large pads below TP14
Read more: http://www.cnx-software.com/2013/02/02/droid-stick-a2-firmware-with-google-play-fix/#ixzz2LvCcegkS
Yes indeed, it put’s in to a forced SD boot mode. Unfortunately the firmware has no u-boot amlscript logic set!
You can how ever put, factorymode=1 into the build.prop under the u-boot.env settings to force the device to boot into recovery mode – if the NAND is working OK?
Mine had a borked NAND so had to get a usb to serial TTL card and connect to the TX,RX on the underneath. Then short the pins near TP14 to boot from an SDCARD – dd the bootloader.img to the SDCARD, then copy the uImage and uImage_recovery (use an hex editor and remove the first 20bytes IMGdiff2 header), boot from the SDCARD, run a serial console program like ckermit and hit a key, then nand erase to fix all the errors, boot the uImage to recreate the MTD partitions. Boot into recovery and away you go.
Use this as a reference – http://openlinux.amlogic.com/wiki/index.php/Arm/Platform_Info/Information_for_8726M/Burn_system_for_8726M_Howto
sudo dd if=./u-boot-aml.bin of=/dev/sdb bs=640b – to SDCARD bootloader, using fdisk create the partition on the SD card but start the cyclinder from the next number i.e. first cyclinder 1, use 2 instead.