If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
Jinxy
Just flash .zip with SuperSU through TWRP. However if You do it on official firmware, than You will brick Your Box. With superceleron's roms it works.
As for the fix, it may not be fixable. Not by counting number of variants that are supported (and some still aren't) by superceleron's roms.
ch3mn3y Thanks for the quick reply and the instructions, will try those. Gonna try installing the Android TV version and see whether it works with that one or not first.
With variants, I'm guessing you mean different variants of models on these h96 pro plus? What's annoying with this, is that everything else works just fine.
Thanks again!
If You want ATV coz it cool, You will be disappointed. It looks good, however app support in Google Play is worse than on Normal rom. Which can be made to look like ATV with good launcher.
ch3mn3y Yeah, I noticed, but it seem to work okay for what he's going to use it for. He's mainly going to use it as a media center, VLC, Plex, etc and those apps work fine it seems.
We installed SuperSU but the reboot function still doesn't work on either of these two firmwares I hope SuperCeleron will find and publish a fix in the future, but I understand that he's a busy man.
What I do know however, is that if we reflash it with the stock FW again, it does reboot normally and functions as it's supposed to, so I guess it's some bug that needs to be fixed in the firmware.
If anybody else experienced this issue and managed to solve it, please do tell
ch3mn3y Yeah, I noticed, but it seem to work okay for what he's going to use it for. He's mainly going to use it as a media center, VLC, Plex, etc and those apps work fine it seems.
We installed SuperSU but the reboot function still doesn't work on either of these two firmwares I hope SuperCeleron will find and publish a fix in the future, but I understand that he's a busy man.
What I do know however, is that if we reflash it with the stock FW again, it does reboot normally and functions as it's supposed to, so I guess it's some bug that needs to be fixed in the firmware.
If anybody else experienced this issue and managed to solve it, please do tell
superceleron Long shot here, I know I might be asking too much, but I figured I'd rather ask than not.
Since I don't seem to be able to solve my friends issue by any means, would it be possible to get the source for the OTA so that I may look into what the issue is
that causes the problem with being unable to reboot on this version of his H96 box?
I installed the SCV4 using burn sd card method. But I could not update to SCV7A through OTA. After selecting update, the box suppose to reboot but instead it just shut down. Didn't everything as recommended here but still it would reboot to update the SCV7A firmware. In the end updated to SCV7A using the TWRP recovery method.
One thing I discovered is before updating to SCV7A, the standard remote control that came with the box worked flawlessly. But after updating to SCV7A, the remote control doesn't work anymore.
Did I miss one version by jumping from SCV4 to SCV7A that render the remote control not usable.
I installed the SCV4 using burn sd card method. But I could not update to SCV7A through OTA. After selecting update, the box suppose to reboot but instead it just shut down. Didn't everything as recommended here but still it would reboot to update the SCV7A firmware. In the end updated to SCV7A using the TWRP recovery method.
One thing I discovered is before updating to SCV7A, the standard remote control that came with the box worked flawlessly. But after updating to SCV7A, the remote control doesn't work anymore.
Did I miss one version by jumping from SCV4 to SCV7A that render the remote control not usable.
Had the same prob. Install with USB-Burn-Tool V1a, Then use Burn_Card_Maker to activate version V4a without using Erase_Bootloader. The Clou V1a has TWRP and if it is then chipped with a higher version of the bootloader the TWRP will not work. Then flash the current V7a via TWRP. Good succeed.
Had the same prob. Install with USB-Burn-Tool V1a, Then use Burn_Card_Maker to activate version V4a without using Erase_Bootloader. The Clou V1a has TWRP and if it is then chipped with a higher version of the bootloader the TWRP will not work. Then flash the current V7a via TWRP. Good succeed.
Is there a SCV4A for non ATV. Or just flash the SCV7A over the SCV4A.
If You flash SCV7A over SCV4A it will probably not boot. And if it will, there will be FC after FC, so You probably won't be even able to turn the Box off other way than disconnecting power cord. ATV and Normal Android may both be Android but they are incompatible with each other (it would be like flashing Samsung's firmware onto Sony's device).
As for remote I would suggest to use remote.conf file (it can be found in /system/etc/) from SCV4 on SCV7A.
We process personal data about users of our site, through the use of cookies and other technologies, to deliver our services, personalize advertising, and to analyze site activity. We may share certain information about our users with our advertising and analytics partners. For additional details, refer to our Privacy Policy.
By clicking "I AGREE" below, you agree to our Privacy Policy and our personal data processing and cookie practices as described therein. You also acknowledge that this forum may be hosted outside your country and you consent to the collection, storage, and processing of your data in the country where this forum is hosted.
Comment