Related
Have you seen this app? I find it amazing, it will automatically download differentiated files between your current CM build and the latest build.
It's free from Google Play (but you can donate to the devs from the app) and it is only for CyanogenMod roms.
https://play.google.com/store/apps/details?id=com.cyandelta&hl=en
Description
Tired of download 200 MB everyday to get your latest CM nightly?
CyanDelta lets you update your CyanogenMod ROM by downloading just a small delta file (about 10 MB) instead of a big full zip file each time. With CyanDelta you can finally update your ROM in just some minutes even with a slow and expensive 2G or 3G connection!
CyanDelta is the perfect replacement of “CM Updater”, “ROM Manager” and “BBQLog”. When a ROM update is available it will notify you and show the changelog between the version you have installed and the new one. If you decide to update, it will delta-download the new version and if you want it will automatically install the new zips via recovery.
Main features:
✓ Security: all downloaded data is digitally signed by us to prevent manomissions.
✓ Recovery zip install: it can automatically reboot to recovery, install the ROM zip and other additional zips (kernel, modem...), wipe dalvik cache and reboot (requires root).
✓ Changelog: if you have a NIGHTLY build, when an update is available, CyanDelta will show you the list of changes between the ROM version you have installed and the new one.
✓ Update notification: when a ROM update is available, CyanDelta will notify you.
✓ High efficiency deltas: it uses the RFC3284 VCDIFF algorithm and some magic to produce really small deltas.
✓ Supports TWRP and CWM-based recovery, but NOT the closed-source ClockworkMod (the name is similar to CWM-based, but it’s a different thing!), since it's locked down by its author to only work with ROM Manager. If you have an unsupported recovery you can just manually install the zips generated by CyanDelta.
✓ Supports all official CyanogenMod ROMs and devices listed in http://get.cm
Click to expand...
Click to collapse
FAQs:
How much small are delta updates?
Typically they are about 10 MB, but it depends on how many changes has been made between the old and the new version. Sometimes it may be low as 5 MB, and sometimes a bit bigger, about 30 MB.
Before start downloading the delta update, you can always see the exact size of the data to be downloaded, so you can decide if download it or not.
What kinds of recovery does CyanDelta support?
CyanDelta supports TWRP recovery and CWM-based open-source recoveries (they are the open-source version of ClockworkMod recovery)
CyanDelta failed to install a zip in recovery on my device!
You probably have the official closed-source ClockworkMod recovery. It’s not supported by CyanDelta because his author has locked it to only work with his proprietary app “ROM Manager”, so we are unable to support it.
If you have that recovery you can replace them with the TWRP recovery (download from here: http://teamw.in/project/twrp2 ) or a CWM-based recovery. Otherwise you can just manually install the zip files generated by CyanDelta.
To use CyanDelta with nightly builds, I must update everyday?
No! It’s not necessary to always update to every new build. You can update only when you want, for example when you see something interesting in the changelog. Currently our server makes deltas between the 40 precedent builds, so for example if you use nightlies, you will always get delta updates unless you have a 40 days old version. If your version becomes too to get delta updates, you will need to download the new full zip from get.cm and import it in CyanDelta.
CyanDelta says “Zip not present in our database, ....”, why?
This may be caused by several reasons:
- if some hours or days ago CyanDelta has always worked fine, it’s almost certanly caused by the server that is rebuilding deltas, it’s the sign that a new update is coming. Just wait some minutes (in exceptional cases it may take some hours) and then reopen CyanDelta, it should show you the update.
- if you have just imported in CyanDelta a zip you just downloaded from get.cm, it might not have been imported yet in our database, wait some minutes or hours and then re-open CyanDelta.
- if you have just imported in CyanDelta a zip that you didn’t downloaded from get.cm, it’s almost certanly a unofficial CyanogenMod build that is not supported by CyanDelta.
- if you have a zip that you didn’t update since a lot of time (40 days for nigthly builds, many months for others), it might not be supported anymore by CyanDelta. This means that you must manually download from get.cm the new zip and import them in CyanDelta.
Can you give me step-by-step instructions to use CyanDelta?
- Install CyanDelta from Google Play.
- Download from CyanogenMod website the .zip file of the ROM you are using.
- Launch CyanDelta and select the .zip file you just downloaded from CM website. CyanDelta will import them and will create a new bigger zip in “Cyandelta” directory in the root of sdcard.
- When an update will be available, a notification will appear. Now you can launch CyanDelta and start the download by simply clicking a button!
- The new zip will be placed in “Cyandelta” dir in the root of sdcard. Now you can install it manually from recovery, or you can press “Install zip”. Cyandelta will automatically reboot to recovery, install the zip, wipe cache partition and reboot (this requires root permission).
On what devices and what ROMs does CyanDelta works?
CyanDelta works on all ARM devices running CM7, CM9 or CM10. Note that only official CyanogenMod ROMs available in http://get.cm are supported. For the moment CyanDelta doesn’t work on x86 devices because it uses a native ARM binary of xdelta3.
Does CyanDelta works with my recovery?
CyanDelta can automatically install new zips in CWM-based recoveries and TWRP recoveries. If you have an unsupported recovery, you can simply use CyanDelta to download the new updated zip and then install it manually in recovery, it’s in Cyandelta directory. Otherwise you can install the
The official ClockworkMod recovery it’s not supported because it’s closed-source and it’s locked down by his author to only work with ROM Manager (doesn’t support extendedcommand scripts). The CWM-based recoveries are identical to original ClockworkMod, but they are completely open-source and support extendedcommand scripts, so they work with CyanDelta.
Is CyanDelta secure?
CyanDelta has been designed from the beginning with security and safety in mind. If you are connected through a public untrusted network (a public wifi hotspot) it’s a lot more secure than download zips from CyanogenMod website.
When the CyanDelta app on your phone connect to our server to get updates, it downloads a JSON with update infos signed with our RSA 2048 bit key, that contains SHA1 hashes of the delta files downloaded by our server. In this way we have a HTTPS equivalent security, although we use HTTP for efficiency reasons.
When the app generate a new updated zip, it will always check if his hash match with the one written in the signed JSON, so data will not get corrupted.
What happens if something fails while installing zips in recovery using CyanDelta?
Theorically the recovery will simply not install the new zip, so it will not damage anything. However since is impossible to test that in all existing devices, there may be strange bugs in your device that might theorically corrupt your data and make your device unable to boot. Unfortunately we can’t prevent this, so you always use this feature at your own risk.
Before installing a zip with CyanDelta for the first time, we suggest you to do a nandroid backup manually.
What happens if the new ROM I have just installed doesn’t boot or it’s unusable?
We know that you want to always use the latest cutting-edge most experimental and unstable ROM! And we know that sometimes these updates can suddently leave you with an unusable device.
To prevent this, CyanDelta always keep one zip file of a previous version of the ROM you are installing. So if the new ROM doesn’t work, simply go to the recovery, reinstall the old zip et voilà!
Thanks to this, we think it’s reasonably safe to update your ROM even without making a nandroid backup every time before flashing.
Why the generated zips by CyanDelta have different size and MD5 than the official CyanogenMod zips?
Because zip files generated by CyanDelta are decompressed. Since data is stored uncompressed inside these zip files, they are bigger and obviously they have different MD5 too.
We have to do that because delta files generated between two uncompressed zips, are a lot smaller than between two compressed ones.
I don’t trust you! If the MD5 is different than the official CyanogenMod zips, who assures me that you haven’t tampered zips?
The content of our zip files and official ones are exactly the same. You can verify that by comparing the hash of every file inside the zip.
Zips produced by CyanDelta are identical (have the same MD5) for all our users, so everybody can verify if the files have been tampered, and in this case alert the whole community.
Does CyanDelta supports other ROMs apart from CyanogenMod?
Not for that moment, but we are planning to add support for other ROMs too, provided that they are completely free to redistribute by us. We will not accept anything that is based on non-free ROMs released by device manufacturers.
If you are a ROM developer that comply with these conditions and you are interested to make your ROM supported by CyanDelta, please contact us.
Click to expand...
Click to collapse
Looks like must have app for cm and should be integrated in cm.. My opinion
Sent from my XT910 using Tapatalk 2
ROM Manager by Koush uses another delta update solution, so there's little chance that CyanDelta will prevail.
I'd like security aspect to be more pronounced, so that you could be less paranoid about updates being tampered with.
It looks convenient to get system updated. But it's safe?
Sent from my XT910 using xda app-developers app
zhichao22 said:
It looks convenient to get system updated. But it's safe?
Sent from my XT910 using xda app-developers app
Click to expand...
Click to collapse
Why not?
Sent from my XT910 using xda premium
Jack'O said:
Why not?
Sent from my XT910 using xda premium
Click to expand...
Click to collapse
testing :good:
Be interesting to hear some detailed feedback on this app. I like the idea of incremental updates instead of totally reinstalling each new rom update.
Sent from my GSM XT910 running AOKP V7 using Xda Premium
I have CM10.1 and installed CyanDelta, I found it easy to use, but for some reason its folder is created on the external sdcard and when it tries to automatically install the update, the recovery doesn't find the update because it searches in the internal sdcard. Now I just use it to download the update and then install it manually.
lukaop said:
I have CM10.1 and installed CyanDelta, I found it easy to use, but for some reason its folder is created on the external sdcard and when it tries to automatically install the update, the recovery doesn't find the update because it searches in the internal sdcard. Now I just use it to download the update and then install it manually.
Click to expand...
Click to collapse
same here, but i can access to the external sdcard so i dont have any problem, works perfectly :good:
What do you mean with that? Is there a way to fix this issue and make CyanDelta really automatic?
Just wait for the next nightly, the internal and external SD cars have been swapped just to tackle this particular issue.
Vatazhka said:
Just wait for the next nightly, the internal and external SD cars have been swapped just to tackle this particular issue.
Click to expand...
Click to collapse
Yup flashed 04-06 here and now the folder shows correct, when a new nightly is released I will try it.
Anyone use cyandelta? I have been trying to use it for the last 2 months but it always comes back with this error during the execution of xdelta. Anything I can do?
Tnks!
Testing.
Right now the app says there is not update available, I will wait a few days to see how it works.
Thank you for the app.
iZak17 said:
Testing.
Right now the app says there is not update available, I will wait a few days to see how it works.
Thank you for the app.
Click to expand...
Click to collapse
I was just trying it out, doesn't work for me since I can't tell it to look on my SDCard.
RedBullet said:
I was just trying it out, doesn't work for me since I can't tell it to look on my SDCard.
Click to expand...
Click to collapse
I'm not using this app any more because for some reason, after download and install the small file made by CyanDelta, I just got bootloops, no matter what, always bootloops.
I'm don't know, maybe is because I use BMM not SS.
Now I'm on CM 11 4.4.2, Not sure if this app can be used with this ROM.
I am using it with CM11 nightlys myself. XT912, SS 3.65. Works great.
Sent from my XT912 using XDA Premium 4 mobile app
:good: Luv the ability to add JBX kernel zip and WIFIAP zip, and have all flash smooth!! xt912 SS 3.65, CM11 12/29 JBX 12/09, Cyandelta as updater, successfully flashed 12/27, 12/29 updates with extra zips, worked perfect both times!! :highfive:
Installed last nightly through CyanDelta, and all the process went perfect. CM team has done a very good work.
Thanks!!
Enviado desde mi XT910 mediante Tapatalk
:laugh: Very sweet, 12/30 flash 7mb download, flawless update!! While download size not an issue, it does kinda "auto"mate the flash process, especially if you flash more then one zip regularly, like JBX or WIFIAP!! :highfive::good:
I was prompted with a Software Update version 2.18.707.5 (Android 4.2.2 with Sense 5),
I downloaded the update,
The Update Package was downloaded to the Download folder in Internal SD Card,
In order to take the backup of the Update Package I accidentally moved instead of copying to another location,
After that I copied the package back to its original location which was the Download folder,
I ran the Update Check again to see if it detects the restored Update Package in the Download folder,
But it didn't and instead prompted me to download the Software Update again.
I don't want to download it again as I downloaded it using mobile data, also I don't have any other internet facility available other than that.
Is there anything that I can do besides downloading the entire Update again?
Moreover what precautionary steps should I take before running the Update like reset to factory defaults, etc?
Device details
HTC One X+ (India)
Android 4.1.1 (Stock/Official)
Never Rooted
Hi Vivek,
Make sure you backup all important data. I've had a couple of friends who updated their phone and then it did not restart. It gets stuck at the HTC logo after installing the update. So most importantly backup your data.
Also on a side note, if possible, could you please upload and share the OTA zip file which was downloaded?
Thanks.
Hello all,
I am VERY new to this and was reading a fair bit on forums etc before having a go. I really want to make my Desire X use more of its memory as its internal memory is just way to small....
I have the HTC Windroid universal tool.
I have successfully unlocked the phone (its shows unlocked on bootup)
I have then installed TWRP successfully.
I have also installed a new Kernel (NeXus) in an attempt to help.
The issue I have am having is when I used the "Gain Root" - Flash Superuser option, it ran OK and said installing (although on the phone it wouldn't access some cahces), but said it was done successfully. The SU App was then ont he phone, BUT when i ran the Root Checker app, it said the phone was NOT properly rooted. When I ran the SuperUser app it said the binary was out of date, but the install options both failed.
I have also tried to manually load the UPDATE-SuperSU-v2.02.zip but that also didn't work?
My main (and only real object) is to get the phone so I can use more memory and run more apps etc, and possibly dump some bloat stuff I will never use, but i dont know how to continue without a successful root in place?
Any ideas? I have read around a lot but cant find a solution?
HTCdesireXrookie said:
Hello all,
I am VERY new to this and was reading a fair bit on forums etc before having a go. I really want to make my Desire X use more of its memory as its internal memory is just way to small....
I have the HTC Windroid universal tool.
I have successfully unlocked the phone (its shows unlocked on bootup)
I have then installed TWRP successfully.
I have also installed a new Kernel (NeXus) in an attempt to help.
The issue I have am having is when I used the "Gain Root" - Flash Superuser option, it ran OK and said installing (although on the phone it wouldn't access some cahces), but said it was done successfully. The SU App was then ont he phone, BUT when i ran the Root Checker app, it said the phone was NOT properly rooted. When I ran the SuperUser app it said the binary was out of date, but the install options both failed.
I have also tried to manually load the UPDATE-SuperSU-v2.02.zip but that also didn't work?
My main (and only real object) is to get the phone so I can use more memory and run more apps etc, and possibly dump some bloat stuff I will never use, but i dont know how to continue without a successful root in place?
Any ideas? I have read around a lot but cant find a solution?
Click to expand...
Click to collapse
Try flashing the zip in this link http://download.chainfire.eu/396/SuperSU/ from recovery, I would advise you use the newer TWRP recovery (2.7.1) found here http://forum.xda-developers.com/htc-desire-x/orig-development/recovery-twrp-2-7-1-desire-x-t2830924 and infinityshooter's kernel http://forum.xda-developers.com/showthread.php?t=2483489
Hope it helps... (Providing you're Desire X single sim)
Thanks yes I am single sim...
How do I "Update" my TWRP?
HTCdesireXrookie said:
Thanks yes I am single sim...
How do I "Update" my TWRP?
Click to expand...
Click to collapse
Install recovery.img via Fastboot, theres quite alot of guides around xda if you do a search
Will_Xda said:
Install recovery.img via Fastboot, theres quite a lot of guides around xda if you do a search
Click to expand...
Click to collapse
OK progress report, I have uploaded the recovery img of TWRP with windroid tool fastboot. 2.7.1 now installed.
TWRP 2.7.1 looks much nicer..no grafix glitches.
installed the zip 1.94 SU you pointed me too.......
SuperSu then said it needed to update the binary when I ran the app on the phone, which I chose to do via TWRP.
Reboot completed via TWRP (all automatically)
SuperSu app then opened and seemed to work.
Rootchecker says: ROOTED!
WOOT! thanks a lot....
Now the question comes .. how do I get my Desire X to start using all its available memory eg SD car, and also how do I use priority access to get rid of default apps I never use?
PS I do appreciate the time you are taking to answer these questions!
HTCdesireXrookie said:
O
TWRP 2.7.1 looks much nicer..no grafix glitches.
installed the zip 1.94 SU you pointed me too.......
SuperSu then said it needed to update the binary when I ran the app on the phone, which I chose to do via TWRP.
Click to expand...
Click to collapse
Don't forget to update supersu to latest version by flashing flashable zip :
http://forum.xda-developers.com/showthread.php?t=1538053
Delta-flasher said:
Don't forget to update supersu to latest version by flashing flashable zip :
http://forum.xda-developers.com/showthread.php?t=1538053
Click to expand...
Click to collapse
That version didn't work before? Will it be OK now I have got it working with the 1.94 version?
HTCdesireXrookie said:
That version didn't work before? Will it be OK now I have got it working with the 1.94 version?
Click to expand...
Click to collapse
It should work now.
HTCdesireXrookie said:
OK progress report, I have uploaded the recovery img of TWRP with windroid tool fastboot. 2.7.1 now installed.
TWRP 2.7.1 looks much nicer..no grafix glitches.
installed the zip 1.94 SU you pointed me too.......
SuperSu then said it needed to update the binary when I ran the app on the phone, which I chose to do via TWRP.
Reboot completed via TWRP (all automatically)
SuperSu app then opened and seemed to work.
Rootchecker says: ROOTED!
WOOT! thanks a lot....
Now the question comes .. how do I get my Desire X to start using all its available memory eg SD car, and also how do I use priority access to get rid of default apps I never use?
PS I do appreciate the time you are taking to answer these questions!
Click to expand...
Click to collapse
Niceee, if you want to remove system apps (e.g. apps you don't use like teetr) then use titanium backup or root explorer, as far as extending memory (e.g. ram or internal memory) i don't think it's possible *Anyone who knows otherwise feel free to correct me*
I'm happy to help, as there were users ready to help me when i started.
plus: are you the guy that posted on the FB group about rooting and extending memory ?
Will_Xda said:
Niceee, if you want to remove system apps (e.g. apps you don't use like teetr) then use titanium backup or root explorer, as far as extending memory (e.g. ram or internal memory) i don't think it's possible *Anyone who knows otherwise feel free to correct me*
I'm happy to help, as there were users ready to help me when i started.
plus: are you the guy that posted on the FB group about rooting and extending memory ?
Click to expand...
Click to collapse
Yeah I have Titanium backup installed now and will work through the rubbish non used apps....
As for Facebook, no that wasnt me...
By the way, I have Android 4.1.1. on the phone as stock.
Do you think its worthwhile upgrading it (somehow?) to Android 4.3? Will that be more efficient and save battery better, and be more optimised? Or will it be more bloated and cane my phone more?
Opinions please....
In fact will flashing a different ROM actually include an upgrade to a different base droid OS?
This is my first attempt of creating any Android Rom myself, so don't expect too much.
Changes to the original OTA update which was the base for all:
Removed Superuser in favour for a fully integrated SuperSU by Chainfire.
Changed some root related settings in the kernel to allow a full root instead of factory default.
Keyboard bug fixed for all included keyboards and added a definition for those cheap wireless keyboards with touchpad you often get with the box.
This means pressing ENTER or OK really does just that instead of only producing unwanted characters.
Several versions for download (once I managed to test and upload all), all include a power menu for Kodi to shut down the box without the need for the IR remote.
General instructions:
Download the RAR archive of your choice and unpack the contents to a micro SD formatted in FAT32.
Insert SD into box and press the little button inside the AV port while you power the box up.
Once the logo appears release the button.
TWRP recovery will start and you should do a full backup of your box first!
I do recommend a full wipe after the backup to avoid conflicts after the firmware installation.
Install the ZIP and reboot once done.
Take your time as the initial boot will take quite some time, especially for the versions with more added programs.
Just the recovery image - for those who need it.
X96 stripped down...
In this version I removed all content from the OTA update that might be considered to be a concern in legal terms.
So no Kodi addons, no streaming apps, just a naked system with the standard Google apps and a modified Kodi.
The crappy file browser was replaced by the FX filebrowser.
For those with the need for more than the Media Box Launcher I added the ADW Launcher as well as the XMBC Launcher to have Kodi as the homescreen.
After the boot is finnished I strongly recommend to update the SuperSU binary.
I left this part manual as a confirmation that the first boot and setup really completed.
Only then can SuperSU update the binary in normal mode with success.
After that reboot to clear the memory and all leftovers.
Once you are done with all modifications and app installations you might need do a full backup trough TWRP again to safe you the time if something goes wrong.
Download RAR
After a lot of swearing, flashing, more swearing and flashing I finally managed to create a fully unbranded system that can be installed through TWRP.
If you still know how the original X96 looks with the original firmware you will be surprised
What has changed from the branded firmware:
Bootlogo original S905X.
Google bootanimation - that was the hardest part, allowing for a custom animation...
Media Box Launcher unbranded and with unbranded theme.
Unbranded Kodi completely removed so the rom will comply with all piracy laws and restrictions - more in the added apps section.
OTA updater removed.
All programs from the branded version removed, so no social media, Chrome, Netflix and so on.
Apart from the naked system with Google apps I included:
AdAway
ADW Launcher
XMBC Laucher for Kodi
File browser replaced by FX filemanager
Power Menu added - still requires to root the box! More under added apps.
Added apps and modifications:
Kodi was removed, but the install script for the addon packs is still valid.
The script no longer refers to the system folder but to /sdcard/apps
This means if you decide to install Kodi you can place the tar.gz archive for the addons in the apps folder of the internal SD.
Kodi itself is not included.
The additional apps I thought to be of use will be in the apps folder of the internal SD.
In FX file explorer it is called "Main Storage".
Here you will find:
Chrome
Facebook
Film On (from the branded firmware)
Lucky Patcher
Mobdro (from the branded firmware)
Netflix (from the branded firmware)
Showbox (from the branded firmware)
Skype
SuperSU by Chainfire
Twitter
VLC for Android
Three different Youtube apps to choose from, including a TV version.
How to install SuperSU:
All modifications to the boot image, scripts, libraries and so on are done and included.
This means the system is rooted except for the actual Superuser app.
Install from the apps folder and let the binary update, once done reboot and enjoy.
Ads...
Not all ads in programs or while surfing can be disabled by AdBlock.
For example everything coming from "trusted sources" like Google will still be allowed.
This is the only reason I included Lucky Patcher as it can be of use for some apps to enjoy without ads.
Install and use at your own risk!
Installation of the ROM:
As before wipe all through TWRP then install the ZIP file from extracted RAR archive - so unpack the RAR first to your SD card.
Installation through TWRP does take a few minutes due to the hash verification.
Since all included apps are integrated into the system the first boot is a bit faster compared to the above ROM.
And the additional apps land on the internal SD for everyone to choose or delete if not wanted.
Please allow about 5 minutes after after the launcher selection appeared before you actually start using the apps - some things are still installing in the background!
Once you finnished the network and personal setup of accounts and such bott into TWRP and make a full backup in case you need it.
A factory reset will set you back to the point of the installation of the rom - so no SuperSU and the added apps folder might be gone too.
Known bugs:
Just noticed the WiFi is not available at first activation.
As the chipset is identified during activation you might have to select the network twice until you see WiFi available.
Watch the boot on Youtube
Download from Filefactory
Beta2 with shutdown using F12 on the Wifi Keyboard and some other fixes. - This is just with the most basic apps.
I finally found a neat way to use the WiFi remote to shut down the box the same way the power button on the IR does.
Just press F12 and you will be asked if you want to power down
Will upload the Beta2 with this fix soon.
What's left to do?
Well, now that there is an unbranded and working S905x system out there it means someone could use it to make a ROM that works on all S905X systems out there...
Just needs including WiFi and where existant BT drivers, libraries and calls....
And of course a recovery capable of working on all boxes but that should not be too hard actually
Update: 12/05/2017:
Beta 3 and a Fully Naked Rom is available now.
The Fully Naked Rom has the FX File Explorer and SuperSU included, apart from that it is a naked Android without any Google apps left - great if you want to play around with different GAPPS packages.
The Beta 3 has some minor fixes and most apps moved into the system area instead of the user space.
If you need more apps or launchers then please check the Playstore.
Both have a system partition inflated to 1536mb, which is the same size as the factory OTA update.
On the Fully Naked Rom you can only install apps through the filemanager as no store of any kind is included.
Update 17/07/2017:
A new firmware was released and finally we have a navbar and notification shade "out of the box".
Other changes include the launcher and Kodi, now you find KD Launcher and KD Player...
The OTA can be found here, just unpack to the SD and use as usual, either with the supplied original recovery or your favourite TWRP.
Only downside is we have a locked bootanimation again
A cleaned rom with the usual fixes for keyboard and root can be found here as my Beta 4.
All removed and some additional apps can be found in this archive, just unpack to your SD and install with FX.
Those with just 1GB system memory or wanting to customise all themself can try the Beta 5, which is made small enough to fit on 1GB systems.
Use the above archive to add the programs you need.
Libreelec for SD or USB install.
Unpack the archive to your PC and use Rufus to get the tar.gz image to your SD/USB stick - all existing data will be wiped.
Copy the dtb.img to the SD, overwriting the existing file.
Plug in the box and boot using a toothpick.
Once Libreelec is set up it will work with the SD/USB inserted without you boot the normal Android from the internal memory.
Videoboot
With this version you can use a MP4 video file instead of a bootanimation.
Works with sound of course and should support every MP4 video the normal video player can play.
For your own video simply replace the bootvideo.mp4 in the systems media folder.
Update 04/06/2017: Finally with Open GAPPS!
The X96 showed some real resistance to overcome the chinese limitations and to allow a working installation of updated Google Apps.
As I already spent a lot of days trying to get it to work I only focussed on Open GAPPS but no manual install or the XIAOMI Gapps installer.
With the troubles in the beginning I created a way of installing it all that worked with no errors for me - I suggest to follow it before you try other ways.
This Beta is right now considered to be in an experimental stage until users provided enough feedback to confirm it indeed works fine.
All is based on a naked and slightly modified Beta 5.
The system itself is pretty much naked except for the usual fixes, everything that could make troubles was removed, this includes:
Camera, video and music, wallpapers and so on - install what you want and need through the playstore once all is working.
Main reason for this was to avoid problems with the GAPPS package and to allow the use on 1GB systems as well.
How to install:
Unpack the RAR archive to your favourite SD card or USB stick.
Plug into the box and start with a toothpick - TWRP will show up.
Go to Wipe, Advanced Wipe and wipe Dalvik/Art cache, Data, Internal Storage and Cache.
Go back and install the X96-no-gapps archive and add the opend gapps archive into the line.
Upgrading the neural network takes a few minutes, once the AI is fully operational the GAPPS package will install.
Simply ignore the fact that some of the listed apps will not be available, like Faceunlock - this is due to the removed camera and other things but also because of our harware platform.
After that reboot.
If all goes well and the intial boot goes well you can simply follow the on screen instructions from the wizard.
In case after 10 minutes the Google animation is still going you have to try again but with a different approach (50/50 chance for the first to work).
Start over with a another wipe as above, then install only the X96-no-gapps firmware.
Reboot and do your usual setup of network and screen settings - don't start any apps or mess with SuperSu yet!
Once all is good reboot into the TWRP recovery and install the Open GAPPS package.
Reboot.
Now all should go according to plan.
Troubleshooting and additional infos:
If neither the first nor the second way of installing works for I suspect that your previous ROM was not based on mine or the OTA firmware.
In this case try one of my other beta firmwares if the included firmware itself already failed to boot.
The initial connection to Google can take 4-5 minutes instead of the advertised 2 minutes, so please allow 5 minutes before you panic.
The additional Google apps are not available at this stage and the loading will stay on the screen until you click next - simply add whatever Google app you need from the playstore.
This included Google Music and Google Play TV.
Again: no additional apps of any kind are included, I suggest to use VLC for audio and video or simply whatever you prefer.
Oh, before you ask: Navbar and notification shade are active and working.
Allow some time and check the notification shade for the updates once the system is running, I did not include all updated versions at this stage.
Download the new Beta 6 - Open Gapps version.
Update 15/11/2017:
They finally released another update, got available two days ago but file date is a bit older.
You can check on the Baidu servers yourself if you like Baidu X96 Downloads
Password there is: hp7u
Download as a RAR from Filefactory.
Once I find some time I will check if and what fixes are needed that I can do.
My new x96 arrived yesterday also I found this thread and instructables yesterday. I'm really glad that you take care of this little machine.:good:
Sent from my I9195I using XDA Labs
Guess I was just in the same boat as everyone else with these noname things.
Figured almost everything out I need, ecxept how to change the bootloader/kernel to allow for a custom bootanimation.
Main thing though was to have a working recovery to avoid weird UBS cables and manual flashing.
I wish I was 2 weeks further so I could test your build but I have to look through these things atm. Its interesting that the youtube tv app hasn't changed for a while.
Too many boxes available but I do think x96 is a solid little machine.
There's also opportunity to work with libreelec.
On my s4mini I have a dolby atmos app running modded by ahrion here on xda. Maybe it would be interesting.,wheather it runs on our little devices or not.
I am working on a fully unbranded firmware for the X96 atm.
The problem of converting USB burn images into flashable ZIP was one problem to get the "unbranded" original firmware to at least install another.
They really don't like you messing with their toys in china LOL
If I can't solve the bootanimation problem I will at least upload the otherwise unbranded version with a choice of launchers and updated apps.
Chinese toys. LOL.
Who has made the custom rom from February 16th. Rar @entertainmentbox?
No clue as I did not do it and did not check either.
But the fully unbranded firmware is on the way to upload
Finally custom bootanimations are possible
The pictures I've seen on instructables are awesome. Nice launcher.
Hope you're having fun tuning these Chinese toys.
Sent from my I9195I using XDA Labs
Congrats to your unbranded system. Hope there will be soon more users for testing and enjoying your work
Fixed the shutdown through WiFi remote problem
Is it possible to have look like the normal android tablet/phone?
Hey Downunder35m http://www.tvboxforum.com/archive/index.php?thread-671.html
Just curious is the remote working? I btw changed the keyboard layout so the annoying enter key is fix as well as added the F1 = Power function
Nevermind I fixed my issues with the remote too. Now it is 100% working.
Wasn't aware that the keyboard needs fixing as it works fine here, including powering down the box
I didn't upgrade to the Beta2
Hello!
I have the X96 box mentioned here. Exactly this 2GB model: https://www.aliexpress.com/item/Hot...32779857015.html?spm=2114.13010608.0.0.dF9x4G
The problem is... No matter what i do, i get the error 7 in TWRP. I tried beta1 and beta2, but same error.
I have tried retrying, rebooting, but no effect.
Any suggestions?
What i did was;
-backup files (to internal memory)
-wipe all (byebye backup )
-try to install image from sd-card or usb-stick (both fat32)
-installed TWRP recovery (which caused SD card not to be recognized anymore)
The recovery is specifically for the X96, I had no time to make a generic recovery for all S905X boxes, but seems it should be the next step here.
The error 7 through TWRP is caused by two things (at least during all my tests):
a) The system is totally wiped and the updater script is unable to find the correct hardware info as the build.prop is no longer present.
For this problem and during my tests it just works if you flash again without a wipe.
So right after the error 7 go back and install the firmware again without any reboot or anything else and it should flash successfully.
b) Your system uses different space allocations for the boot, bootloader and recovery partitions.
For this problem the only real cure is to first use the OTA installer for the genuine firmware to get the system working again.
Then only wipe Dalvik, cache and data - the system partition will be overwritten once the update starts but then the installer can find the build prop and if compatible will continue.
If you have a download for the original firmware I will try to incule your system stuff into the next recovery I make.
Otherwise you can always try the hard way if the system is currently toast anyway:
Open the updater script in the META-INFO folder (down in the last subdirectory) and remove the device check for the X96.
That would be the first two lines of the script- everything before th OTA check.
Downside of this approach is that your entire system will be replaced by mine and if your hardware is differernt or the partition sizes won't match then it still won't boot.
Let me know how you go and I will see that by tomorrow evening I have a universal TWRP for all S905X ready.
so, the weirdest thing happened to me. I spent the whole day in an attempt to root my Samsung A8 star with Magisk and after many times failed, i have finally rooted my phone. The next thing i did was install the newest Magisk Manager (Safetynet all green) , the EdXposed framework module, BusyBox binaries module , and Titanium backup
I have uninstalled several bloatwares (both Google's and Samsung's Bixby stuffs) via Titanium, everything went smooth, i can either download apps from CH play or upgrade them.
AND when i checked out the Samsung's default file app, my phone's memory capacity just went BELOW ZERO (-44.72 GB/4GB), the storage analysis showed -1111% used , there was nothing there left, it just showed the ram capacity as the internal storage. I also did some restart and power off but nothing changed, i downloaded the google's File app on CH play (the phone can only receive data from CH play, it doesn't work with chrome or via usb cable, or even screenshot), and the memory capacity in the Google's File app is still there, still normal (11/64GB used) but in the default file app isn't.
But it still shows nothing when i connect the phone to my laptop
You guys can take a look at those pics that i took. (sorry guys, newbie here, right now i can't attach any images )
i really hope you guys can help me with this, but now i will flash the OG firmware back to the phone via odin, i will update for you guys if anything back to normal ](btw all the rooting i did was on odin)
vinhpool said:
so, the weirdest thing happened to me. I spent the whole in an attempt to root my Samsung A8 star with Magisk and after many times failed, i have finally rooted my phone. The next thing i did was install the newest Magisk Manager (Safetynet all green) , the EdXposed framework module, BusyBox binaries module , and Titanium backup
I have uninstalled several bloatwares (both Google's and Samsung's Bixby stuffs) via Titanium, everything went smooth, i can either download apps from CH play or upgrade them.
AND when i checked out the Samsung's default file app, my phone's memory capacity just went BELOW ZERO (-44.72 GB/4GB), the storage analysis showed -1111% used , there was nothing there left, it just showed the ram capacity as the internal storage. I also did some restart and power off but nothing changed, i downloaded the google's File app on CH play (the phone can only receive data from CH play, it doesn't work with chrome or via usb cable, or even screenshot), and the memory capacity in the Google's File app is still there, still normal (11/64GB used) but in the default file app isn't.
But it still shows nothing when i connect the phone to my laptop
You guys can take a look at those pics that i took. (sorry guys, newbie here, right now i can't attach images )
i really hope you guys can help me with this, but now i will flash the OG firmware back to the phone via odin, i will update for you guys if anything back to normal ](btw all the rooting i did was on odin)
Click to expand...
Click to collapse
It just seems to be a bug with the device itself after you've rooted. Does your device give you a notification about it? If not then the filemanager could be bugged out
TheExploitedOne said:
It just seems to be a bug with the device itself after you've rooted. Does your device give you a notification about it? If not then the filemanager could be bugged out
Click to expand...
Click to collapse
no, it doesn't show anything, i just got back to the OG rom and everthing is back to normal now, although i really enjoy a rooted phone
vinhpool said:
no, it doesn't show anything, i just got back to the OG rom and everthing is back to normal now, although i really enjoy a rooted phone
Click to expand...
Click to collapse
It could also be a bug with Magisk as well, but does seem to just be a bug eith the filemanager itself. Try the ROM again and use termux to check the real space that you have (df -h or use df). I think Magisk breaks some Samsung features after rooting though as far as i know so that may have been the problem