Related
Finless juste made a new rom (version 1.7) for these android stick:
Measy u2c / B12 / imito v2 (camera)
libstagefright inside
support and download here:
http://www.freaktab.com/showthread.php?4282-NEW-Measy-U2C-B12-Finless-ROM-1-7
my question.. Is he the only one who cook rom for android stick? cant find alternative here on xda...
anyway, a great Rom done by Bob!
Code:
Features in my Measy / B12 / Imito V2 ROM:
This is an entirely new system. This is not much from the original Measy/B12 ROM in this as fas as system goes.
Many features from my 1.6 ROM are of course in this along with new features.
BE SURE to check out the mouse wheel ZOOM function to enable google earth etc to zoom!!!!
Set it by going into settings>accessability> and turn on mouse zoom!
1) New "auto hide" status bar! To enable this go into settings>Display and turn it on.
Now anytime you run an APP it will automatically hide the status bar. Please note, some badly written APPs
can leave you in a stuck condition that you cannot exit the APP. You will need you keyoard exit key.
2) While you in settings>display there is another feature to force the settings menu icon in the status bar.
It is 3 dots vertically. NOw anytime you in a APP that has a settings capability, if you click that you get settings!
3) Lock screen is back friends! Now is settings>security you can
A) Disable the lock screen completely (default is slide)
b) Setup a pattern for lock screen
c) Setup a PIN for lock screen
d) Setup a password for lock screen
4) Sleep is back like a tablet!!!! Go into settings>display and you can turn on sleep!
Now understand how this works
a) If there is no wifi or ethernet connection, when it goes to sleep will power off.
b) If there is a connection, it will simple go into low power mode and turn the display off. Moving the mouse turns it back on again
5) I enabled location services. This is now in the settings menu. Tested and working with all APPs that use it.
remember to turn off GPS as we have no GPS.
6) New "grid" style launcher available as a choice of launcehrs.
Some people still want the Alternate launcher that comes with many TV sticks for EZ TV use.
I took this from the Neo X5 ROM as I liked it better than previous versions. This of course comes with the RK settings as well.
If you want to remove this just use ES File explorer and delete these files from /system/app
LauncherNEW.apk
AllApp.apk
RKSettings.apk
RKBasicsettings.apk
Now just reboot and all this will be gone.
7) Gameloft fix. This fixes Gameloft games from crashing to the desktop.
Many of them do not run and crash to the desktop. This is due to a license check based on the device.
Special thanks to Christian Troy for inventing this fix. I modded it for this ROM.
8) Build.prop edit to open up the Google Play store to APPs that normally say "not compatible".
I am spoofing a Samsung device that will show almost any APP as compatible.
YOur device will show up in google play as NOT a B12 device! Understand this please.
I also left the original buiild.prop in the ROM called build.orig.
If you want to go back, just use ES FIle Explorer or a root file explorer and rename build.prop to build.old
Then rename build.orig to build.prop.
Go into settings, apps, all and go into the Google Play app. Clear the cache and data.
Reboot! You should be back to showing up as a Minis Nexo X5.
9) Rockchip just released a updated libstagefright.so to try and fix HW decoding issues in XBMC.
Ihadd added this ot the ROM but have not fully tested it yet.
See info here regarding this new library.
http://forum.xbmc.org/showthread.php...756#pid1345756
10) As always, full init.d support! If you do not know what that is... ignore it. For geeks that want to use it. It is there!
11) RK Mirrioring is enabled. I have yet to figure it out or how to use it but if we ever do, its there.
I think we need a client on our tablets to use it. Hopefully more info will come from WiMo about this.
12) Remote Control using RK Remote APP is now fully supported!
In the ROM kit is a RKRemoteControl.apk.
You install this on your phone or tablet and now it can remotly control your TV player!
Just put the APK on sdcard or something and install it on your Android phone, tablet, etc.
ENJOY this one! I had a HARD TIME getting it to work!
13) I added a reboot APP that will allow optional reboot options like reboot to bootloader (flash mode).
14) As always I added the Xbox XPAD.KO module is now injected on boot. This was by request! Enjoy!
15) I added Xbox360 keylayout to fix some games and camera spin with xbox 360 controller. Per this post here:
http://forum.xda-developers.com/show....php?t=1792531
16) TUN.ko module is also added by request. (CIFS and MD4 are already in the latest kernel).
Be aware if you use another kernel other than whats in this ROM, you may have to manually insmod CIFS and MD4.
The files are in /system/lib/modules
This ROM has several options for you to choose from for flashing so please read carefully how to change these flash options.
I have provided 4 parameter files. These will increase APP space and decrease internal sdcard space.
1GB APP space (this is default setting for the flash tool).
2GB APP space.
4GB APP space.
6GB APP space! This is the max! This leave only 400MB of space for the internal SDcard.
___________________________
NOTE:
USB OTG port boot up:
Anytime the Measy/B12 is booted AND the OTG port is plugged into a PC, it will boot with USB storage turned on! What this means is on boot up you will not be able to see the internal SDcard or the External SDcard from within Android. On your PC you see the removable drives because on boot they are mounted to the PC not Android. Now you can this OFF once booted. Go into settings and USB. You will see PC connection is grayed out.
1) Click it and it will then put the check box in "conneted". Odd it is OFF by defualt even though it is really connected to the PC.
2) Now turn it off and it will unmount the SDcards from your PC and you can now see them in Android.
HOWEVER... Realize next reboot, it will be on again.
In my opinion this should not work this way but at least you can turn it off once booted.
The other work around is to always hook up the USB cable to the back micro USB port not the OTG port.
The back port ONLY powers the unit. There is no data connection on this port for PC.
This solves that issue. But remember the back port will NEVER connect to a PC or allow ROM flashes.
Only the OTG port allows that.
Can I install this ROM on MK809II?
ledzgio said:
Can I install this ROM on MK809II?
Click to expand...
Click to collapse
YES. And I think it's the best ROM for MK809 II. Try it and you'll see...
g.b.a. said:
YES. And I think it's the best ROM for MK809 II. Try it and you'll see...
Click to expand...
Click to collapse
Thank you! Is everything working with this ROM? even Wifi and bluetooth? I read that there are problems with them...
ledzgio said:
Thank you! Is everything working with this ROM? even Wifi and bluetooth? I read that there are problems with them...
Click to expand...
Click to collapse
Yes. They are working fine with this ROM...
Enjoy!
Hi I am looking for cmw flashable zip for mk808 will this work ?
g.b.a. said:
Yes. They are working fine with this ROM...
Enjoy!
Click to expand...
Click to collapse
I have heard that, with the MK809II because it doesn't have the reboot button, I have to open the device and do something inside...is it correct? do I have to do this operation even with this ROM?
thanks
ledzgio said:
I have heard that, with the MK809II because it doesn't have the reboot button, I have to open the device and do something inside...is it correct? do I have to do this operation even with this ROM?
thanks
Click to expand...
Click to collapse
Reboot?
If it is a normal reboot, you don't have to open the device.
There is a Reboot app included in the New Measy Finless 1.7 Rom.
Correct me if I am wrong but based on my understanding, you only have to open your device and do the "Shortcut" method when you are having
some problem in getting into recovery mode. or your small switch button is not working anymore...
Can I install this rom on my MK809III rk3188
are there some instructions/guide how to make rom for this little sticks on your own?
adiprince1 said:
Hi I am looking for cmw flashable zip for mk808 will this work ?
Click to expand...
Click to collapse
I would like to know this also.
Thanks
Sent from my SGH-T889 using xda premium
Hello everyone,
I am kind of new to Kodi and FireTV Stick but already fell deeply in love with all of it’s features. Last week I installed a MegaPack for Kodi which comes with all the repos and addons already installed. Really love it but I guess that this image I installed can be stripped down to reduce size and overall hardware needs.
The instructions to install the MegaPack required a 1 GB download and adbfire. In adbfire with the help of the restore button the whole extracted “MegaPack.zip” was copied to the FireTV Stick and everything worked fine.
Now yesterday I tried the following: I installed Kodi on my Laptop, installed the same MegPack (which in case of Windows just requires to copy all the folder to C:/Users/xxx/AppData/Roaming/Kodi) and made some changes. These changes I then copied again with the help of adbfire to the stick and voila it worked…
To keep it short my question is the following: Is my described procedure “good”? I really love the ease of setting up Kodi on the PC and push the files to the stick. With help of mouse and keyboard the setup process is much more convenient. I am just not sure if this might lead to technical problems. Anybody can tell me if I was lucky with my try yesterday or that this is a perfectly fine way to do it? The addons on Kodi for Windows and FireTV Stick are the same?
Thank you very much in advance and happy Kodiing
Thanks Anhaussner for the information!
Could please post the download link for the MegaPack for Kodi that you have installed?
I also would like to know how to install this MegaPack and on which folder you will have to copy all these files?
anhaussner said:
Hello everyone,
I am kind of new to Kodi and FireTV Stick but already fell deeply in love with all of it’s features. Last week I installed a MegaPack for Kodi which comes with all the repos and addons already installed. Really love it but I guess that this image I installed can be stripped down to reduce size and overall hardware needs.
The instructions to install the MegaPack required a 1 GB download and adbfire. In adbfire with the help of the restore button the whole extracted “MegaPack.zip” was copied to the FireTV Stick and everything worked fine.
Now yesterday I tried the following: I installed Kodi on my Laptop, installed the same MegPack (which in case of Windows just requires to copy all the folder to C:/Users/xxx/AppData/Roaming/Kodi) and made some changes. These changes I then copied again with the help of adbfire to the stick and voila it worked…
To keep it short my question is the following: Is my described procedure “good”? I really love the ease of setting up Kodi on the PC and push the files to the stick. With help of mouse and keyboard the setup process is much more convenient. I am just not sure if this might lead to technical problems. Anybody can tell me if I was lucky with my try yesterday or that this is a perfectly fine way to do it? The addons on Kodi for Windows and FireTV Stick are the same?
Thank you very much in advance and happy Kodiing
Click to expand...
Click to collapse
Only thing is that the two file systems are different, you need to change the file system on the fire stick, one of the maintenance programs can change it for you, download "The Community Portal" & goto mantenance/advance settings & then select "convert physical paths to special" this will fix the file system to Android from the Pc version. If you need to install this install it from File manager/add sources & type in- http://noobsandnerds.com/portal
then name it what ever you like & select ok, then install from zip, not go to programs & open it.
Hope this helps If so hit that like button
Ideally, I would install the build on the Fire Stick, tailor it to your requirements (stripping out the add-ons you don't want etc) and then performing a backup via ADBfire. You'll then have a build perfectly set up to restore to any new Fire Stick using only the "Restore" feature also in ADBFire. It would be the cleanest method to do it.
For example, I do the same for my builds. However, I applied the same restore to the Fire TV, and while most things worked some did not (and there shouldn't be that much variation between the Fire Stick and TV.)
WARNING: I am not responsible if you use any of the following and for any troubles you may experience with your device.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I recently got a Z4L and wanted to do a few things with it. After many days and nights, I am ready to share. I also wanted to consolidate an area for us to easily get items. I will add things from others if pertinent or greatly desired. Much of this will also apply to the Z4 and to other Rockchip Android TV Boxes (to a lesser extent).
This first section will entail some information, firmwares, apps, and performance tweaks and tricks.
The second section will have information on flashing firmware, ROMs, and recoveries.
The third section will have all the available tools for Rockchip boxes.
Z4 vs. Z4L
The Z4 and Z4L are essentially the same Android TV Box with a few minor differences. The Z4 has dual band WiFi, while the Z4L only supports wireless b/g/n. This is because the Z4 uses an Ampak AP6335 chip, while the Z4L uses a Realtek RTL8723. Does it matter? Yes. I have found that many firmwares and ROMs will work on the Z4L, however, all WiFi and Bluetooth connectivity is lost. And even other Rockchip Android TV Box firmwares sharing the same chip have had problems (e.g. USB ports no longer work, partial loss of remote functionality).
Another difference on the Z4L is OTG capability. While the port works for flashing, it will not work for any external devices when in the Android OS...
A final, possible, difference is that I think the Z4L only comes with 8GB of storage, but I could be wrong.
Firmware
This is the stock firmware for the Z4L. It was quite difficult to find, and was the only one I have come across:
Z4L Stock Firmware
Custom Firmwares
This is the Z4L stock firmware with enhancements. I have made some performance tweaks to help make the Z4L run smoother. Apps have also been added (with the exception of FolderMount), which I will have available in a separate section below.
In the slim version, I have taken out several apps I found unnecessary (e.g. Gmail, Calculator, etc.). Things you would normally leave to a smartphone or PC. While the firmware will be the exact same size as the stock firmware, rest assured it is slightly lighter:
Z4L Slim
In the lug version, I have not taken out any of the preinstalled apps. Instead, I have just added the same ones placed in the slim version. This will be a larger file size due in part to the additional apps, and the extra space I left for possible future modification needs:
Z4L Lug
Apps
Kodi
Kodi 15.2 RC PL
This is the beta that comes with a lot of the Android TV Boxes. It is preloaded with official and non-official add-ons. While it is suggests it is a 15.2 Isengard Release Candidate, the app settings in Android (and at least one Kodi updater app) will state that it is version 15.1.
Kodi 15.2 PL
What I have found on the Z4L is that I cannot update it. The Play Store gives no update option. Update apps for Kodi will attempt to update and fail to install, as will a manual download from the Kodi site. The only way I could update to 16.0 was by uninstalling 15.2 RC and then installing 16.0. I would lose all add-ons, and even a backup from Kodi will disallow restoring unofficial add-ons. Even if manually adding unofficial channels, I had problems getting them to work...
Kodi 16.0 PL
This is the latest (Jarvis) Kodi, and I have gone ahead and preloaded it with all the same add-ons from the 15.2 RC version:
Kodi 16.0 PL
ZDMC 16.0 PL
This is a software built on Jarvis. I have inserted all the preloaded add-ons from the 15.2 RC version in it. I am unsure what the difference is with Kodi. They look virtually the same, except for the logos and branding (since Kodi does not allow others to use their IP).
ZDMC 16.0 PL
Stock Apps
The only other stock app I thought would be of interest is the launcher. I actually prefer it to any of the others available. It may or may not work fully with other Android TV Boxes:
MyLauncher
Apps in Custom Firmwares
These are all the apps that come in the custom firmwares I created:
Added
Other Apps
FolderMount is an app that can help when you have little storage space. The only reason I have it here is because it does not come with any of the custom firmwares and will be needed for one of the performance tweaks and tricks:
FolderMount
Performance Tweaks & Tricks
Some of these tweaks or tricks may be dependent upon root. The Z4L comes prerooted, but others may need to obtain root first.
Speed Up
One of the best fixes I can recommend to help with any sluggish performance is to speed up your CPU cores. Download an app like Kernel Adiutor to give you as much access as possible. If you download something like No-frills CPU Control, you will only have access to the "Little" cores of the RK3368.
Open your app of choice and find the area that allows you to set the minimum and maximum states of the CPU.
Ensure that the "Big" cores are set to 1.5GHz for the maximum state.
Change the minimum state to 1.5GHz.
Do the same for the "Little" cores, where the maximum state should be 1.2GHz.
You can leave the governor as Interactive or change it to Performance.
Leave the I/O scheduler as "cfq" for daily use, use "noop" for benchmarks.
I have not experienced any type of overheating from these settings.
Maximum GPU Performance
If you want to get a bit more out of the PowerVR Rogue G6110 GPU, you can downsize your resolution. I use a 1080p TV, so I changed the Android OS resolution to 720p. Download something like NOMone Resolution Changer, or equivalent. A few items will have some larger writing even after the DPI change, but nothing that should deter you from keeping the setting.
Open your app of choice.
Set the resolution to something like 1280x720.
Change the DPI to (or around) 151.
Apply.
Some apps will ask if you want to keep the settings, and prompt you if you need another message in case something happens. With NOMone, this does happen. It also gives you the ability to reset to default settings if need be.
With the two above tweaks, I was able to get the multi-thread score to outperform an iPhone 5S in GeekBench. And in GFXBench, I was able to outperform a LG G4.
Internal/External Storage Swap
The greatest drawback of the Z4L is the 8GB of storage space. It can fill up quickly if you want to play games, or have hefty apps. You will need to download SD Fix and FolderMount. I have tried other apps like Links2SD and Int2Ext, but they do not work.
Open SD Fix and follow the instructions.
Reboot.
Open FolderMount.
Analyze the apps and see which have Data or OBB files, and are not grayed out.
Select them and make a pair.
You can select a USB flash drive if you do not want to use a micro SD card, but either way, ensure the source and destination sources are properly chosen.
SD Booster
It is probable that your internal storage and micro SD card are not optimized. Download SD Booster to change this and speed up your I/O abilities. Red means that you are definitely not optimized, yellow means you are operating at substandard levels, green means your are at the perfect level, and purple means you are operating beyond the perfect level.
Open SD Booster.
Select the internal or external storage.
Change the original value to a different one (i.e. 512, 1024, 2048, 8096).
Use the green checkbox to confirm the changes.
Use the green checkbox on the main window to implement the changes.
The Z4L's internal storage is in the red when first opening this program, so this will help somewhat. You may not get a huge jump in read or write speeds, but every little bit helps.
Developer Options
The Z4L does not have the ability to enable Developer Options natively. The "Build" section is not present. Download and app for Developer Options, I recommend the one from Andev.
Open your app of choice.
Click whatever button(s) needed to access Developer Options.
The one I have mentioned is part of the custom firmwares I created. The only caveat is that it will require you to sign into your Google account before proceeding.
Xbox 360 Wireless Controller
If you want to use a Xbox 360 wireless controller instead of a wired one or Bluetooth gamepad, you can! You will need a Xbox 360 wireless gaming receiver. Download USB/BT Joystick Center.
Open USB/BT Joystick Center.
Plug in the wireless receiver.
Click the button on the wireless receiver for sync.
Click the middle button of your Xbox 360 wireless controller.
Click the sync button located on the top of the Xbox 360 wireless controller.
Select the option to search for controllers on USB/BT Joystick Center.
Once the controller is recognized, immediately begin testing the buttons and whatnot or you may lose connectivity.
This is a bit finnicky, but it does work. The first couple times I could not get the controller to stay synced. Once it did stick, I tried it with Dead Trigger 2 and found that almost everything worked but the D-pad. Of course, I still had to setup the buttons.
Misc. Issues
Apps Not Working
Some apps can be downloaded but will FC when trying to open them. For this, I do recommend downloading the APKs from somewhere reputable and installing them with the file explorer.
Stock File Explorer
The stock file explorer is actually good, but it will not let you go to root ("/"). For this you will require something like ES File Explorer File Manager or Root Explorer. I found that whenever I would go to the Data folder on ES File Explorer File Manager (after selecting show Hidden Files), it would show it as empty. Whereas, Root Explorer would show everything. However, I have not been able to access my USB flash drive through Root Explorer, but can do so with ES File Explorer File Manager.
Stock Media Player
The stock media player plays most everything, and has built-in 3D capabilities. However, when trying to play some x265 files, there were problems. I would recommend installing MX Player to help with H.265 or VP9 codecs.
10-Bit Video Files
8-bit video files for H.265 or VP9 have no problems playing on these boxes. But when trying to play something that is 10-bit, it has nothing but major frame stutter, audio skip or silence. Until these codecs are made to not utilize so much CPU power, I do not think anything other than actual PC's will be able to play them properly.
External Webcam
It may be possible to use an external webcam on these boxes, and some of the files I have looked at suggest this. I do not currently have an external webcam that I can try this out with, but if someone else does, please inform me and I will update the information here.
External 3G/4G
It may also be possible to use an external USB SIM Card Modem to get data to work on these boxes (if ever needed). I do not currently have any such device that I can try this out with, but if someone else does, please inform me and I will update the information here.
Thanks: XDA, Freaktab, 4PDA
This section only contains the TWRP files. Other necessary files are in the next section.
How To Get Into LOADER Mode
Loader mode is needed in order to flash ROMs. If you simply connect your Android TV Box with the a USB cable to your PC and power it on, you will only get ADB mode, which will not work.
Plug in the USB cable to a PC and the Android TV Box.
Press and hold the reset button. (On the Z4L/Z4 it will be located on the bottom of the box. On some others it will be in the A/V port, so use a toothpick or paperclip).
Plug in the power adapter while still holding the reset button.
4 seconds should pass before it is in Loader mode.
Let go of the reset button.
DO NOT TRY TO PUT A THIN OBJECT INTO THE Z4L/Z4! There is no back (at least on the Z4L), which means you can go straight into the area of the PCB and possibly destroy something or disconnect the antenna cable.
How To Flash Firmwares/ROMs
You can use either the Android Tool or the Batch Tool to flash IMG files. I prefer Android Tool since it provides more options, but I will explain how to use both.
Open the program of choice.
Switch to the "Upgrade Firmware" tab if using Android Tool.
Click the "Firmware" button (or the 3 dots button for "FW Path:" if using Batch Tool).
Navigate to your "update.img", or the IMG file for your firmware/ROM.
Select the IMG file.
Click "Open".
Click "Upgrade".
The Batch Tool can only do firmware/ROM IMG files, but Android Tool will allow you to flash BIN or entire extracted ROM files.
How To Flash Extracted Firmwares/ROMs
The Android Tool can be used to flash extracted firmwares and ROMs. You will notice that the software comes with a "rockdev" folder filled with IMG and other files. I have come across at least one ROM that was extracted and needed Android Tool in order to be flashed. For the purposes of this tutorial, ROM is interchangeable with firmware.
Open the "rockdev" file of Android Tool.
Go to the "Image" folder.
Replace all the files in the "Image" folder with the extracted IMG files from the ROMs "Image" folder.
Go back up one folder (into "rockdev").
Replace all the IMG files with the extracted IMG files from the ROMs root folder.
If you have any extra files from the ROM that are present in the "rockdev" folder, replace those as well.
For at least the Z4L, be sure that you have the Loader BIN file that is version 2.40!
Open Android Tool.
Put your Android TV Box into Loader mode.
The first tab will show you all the IMG, TXT, and BIN files that you should have from your ROM in the "rockdev" folder. The only file you may not have, but should already be in the folder, is "baseparamer.img". The one that comes with Android Tool will suffice.
Ensure all the check boxes for each IMG, TXT, and BIN file is checked.
Click "Run".
Note: NEVER FLASH AN EXTRACTED ROM ALONG WITH A TWRP RECOVERY! The box will boot immediately into TWRP, making it impossible to ever get to the ROM itself!
Once the process has completed, which should take no more than a few minutes, your Android TV Box will no longer state that is in Loader mode, and will either state no device is connected or "Found One ADB Device". If you see this, or at least that you were successful on the message prompt of Android Tool, then you can go ahead and disconnect everything and boot your box!
How To Flash TWRP Recovery
You will need the Android Tool for this. Download either Abdul's TWRP, Generic TWRP, or Specific TWRP. I have tested and used Abdul's TWRP on the Z4L, and it works without issue.
Change the name of the TWRP IMG to "recovery.img".
Go to "rockdev>Image" of the Android Tool folder.
Replace "recovery.img" with the renamed TWRP IMG.
Open Android Tool.
Uncheck every box except "Recovery".
Put your Android TV Box into Loader mode.
Click "Run".
TWRP is now installed. I am unsure for the other TWRP IMG files, but the Abdul variant will require a mouse in order to be used because the remote is not supported.
How To Root
If your Android TV Box is not prerooted, then you will need to use SuperSU. Download SuperSU from here. If you want to try the latest version, you can find it here. Ensure that you already have TWRP installed.
Place the SuperSU ZIP on your internal or external storage.
Boot into TWRP.
Click on Install.
Add a zip.
Find your SuperSU ZIP file.
Select it.
Flash the ZIP file.
You should now be rooted and can check with an app from the Play Store to verify. I have not tested this as I do not need it, so if any steps are different, please let me know and I will change accordingly.
How To Flash Firmwares/ROMs with a SD Card
You will need the Upgrade Disk Tool and a micro/SD card that is 4GB or more. For the purposes of this tutorial, ROM is interchangeable with firmware, and SD card is interchangeable with micro SD card.
Open the Upgrade Disk Tool (SD Firmware Tool).
Select your SD card from the dropdown menu.
Click the "Firmware" button.
Find your ROM's IMG file.
Select it.
Click "Open".
Click "Create".
Once done, ensure your Android TV Box is turned off.
Insert the SD card into your Android TV Box.
Power on the Android TV Box.
The process will take some time, but a notification of a successful completion will appear when done.
Turn off the Android TV Box.
Remove the SD card.
Power on the Android TV Box.
The Android TV Box should now be "upgraded" to the firmware or ROM you used.
I want to remind people that every time you flash a firmware or ROM, it will take around 10 minutes for the Android TV Box's initial boot into the Android OS.
I may also put some more information here about how to open the compiled IMG files and play around with the system IMG file inside, if people want to know (and I have time).
The Rockchip drivers needed for these tools can be found in Batch Tool v1.8 as "DriverAssitant" [sic].
Android Tool
This is the probably the best tool for flashing and dumping firmware or ROM files:
Android Tool v2.35
Batch Tool
This is a great tool for flashing firmware or ROM files. It is the easiest to use:
Batch Tool v1.8
Batch Tool v1.7
Again, v1.8 has the drivers needed to make all the Rockchip tools function.
Factory Tool
This is a tool that should allow you to change things like the boot animation, add or delete APKs, and even make system clones. However, this does not work with the Z4L. The latest version gets close to completing its initialization process, but fails at the end, keeping all the options grayed out...
Factory Tool v3.4
Factory Tool v4.0
Factory Tool v4.4
Factory Tool v5.0
I have changed a couple of the versions to default to English (or as much English as afforded by the program without too much modification). The others were already in English.
Dump Tool
This is a tool that is essentially Android Tool. I believe that the version of Android Tool I have linked will perform the same functions, but this was one specifically made for dumping stock IMG files. I have used it unsuccessfully, as I can dump all the IMG files, but I am unable to make them work together. However, the "system.img" file may or may not work for modification purposes, but I have yet to check...
Dump Tool v2.3
IMG Mod Tool
This is a great and useful tool for those who want to modify firmwares or ROMs. It allows you to open firmware or ROM IMG files and recompile them. And despite its name, it does work for RK3368 Android TV Boxes.
RK3066 IMG Mod Tool
Upgrade Disk Tool
This allows for "upgrading" your Android TV Box with a different firmware or ROM.
SD Firmware Tool
If I have missed any tools that do something different, have extra functions, or simplify procedures; let me know and I will add them here.
Reserved..
Reserved...
Great consolidated info for Z4 / Z4L RK3368.
Different ROMs being developed for this beast, mostly Z4. IMO best, fastest and stablest is @yablrar mod v1.2 A multi window one is also there. I believe MM 6 is releasing soon.
On a side note:
An easier way to get into recovery/bootloader mode is to use an App like Titanium or other to reboot. No need to tinker around with reset/power buttons.
I have this android tv...should your firmware work in it?¿?
http://www.leotec.com/index.asp?acc...LEOTEC&familiaweb=TV&CodigoArticulo=LETVBOX02
Z4 Rockchip Bluetooth Issues
I have the Z4 Rockchip , I have tried 3 different firmwares and I can't bluetooth past 4 feet ? It has 4.0 , is there a way to upgrade it ?
Thanks
WAIKIKI728 said:
I have this android tv...should your firmware work in it?¿?
http://www.leotec.com/index.asp?acc...LEOTEC&familiaweb=TV&CodigoArticulo=LETVBOX02
Click to expand...
Click to collapse
It might work, yours looks like it does not have wireless AC, so there is a chance. Get a backup of your stock firmware, then try mine out. Be sure to check if your ports, WiFi, and Bluetooth work after flashing my firmware...
pimpurlid said:
I have the Z4 Rockchip , I have tried 3 different firmwares and I can't bluetooth past 4 feet ? It has 4.0 , is there a way to upgrade it ?
Thanks
Click to expand...
Click to collapse
The hardware will be near impossible to upgrade, and not worth your time. If you really want to have it work past 4 feet, you would need to buy a Bluetooth signal booster. However, if you are just using a mouse or keyboard, I would try getting a USB 2.4GHz device instead. Those seem to work much better.
Heatshiver said:
It might work, yours looks like it does not have wireless AC, so there is a chance. Get a backup of your stock firmware, then try mine out. Be sure to check if your ports, WiFi, and Bluetooth work after flashing my firmware...
The hardware will be near impossible to upgrade, and not worth your time. If you really want to have it work past 4 feet, you would need to buy a Bluetooth signal booster. However, if you are just using a mouse or keyboard, I would try getting a USB 2.4GHz device instead. Those seem to work much better.
Click to expand...
Click to collapse
Thank - You .
Have you tried getting a version of Linux installed on one of these Z4's?
Other other people have got the 64 bit arm version running on devices that use the same chip (RK3386 chip).
how get loader mode
Please help ... I can't make that my pc find the Z4 rk3368 in loader mode, just the ADB mode.. to install you costum ROM Z4L slim..
tank you..
Hi, been trying to install custom roms, with rockchip batch tool and android tool, i am in loader mode and with org cable but all i get is test device fail. I can update stock firmware with usb just can't get custom roms to work. Thanks for any help.
Z4L
Has anyone installed this rom, any feedback?
I have the Andoer Z4L and wanted to try this as I am experiencing some issues with audio via optical where it drops intermittently. Would any of the Z4 roms for RK3368 work on this device also?
Z4 ROM that should also work with the Z4L
d33pblu80 said:
Has anyone installed this rom, any feedback?
I have the Andoer Z4L and wanted to try this as I am experiencing some issues with audio via optical where it drops intermittently. Would any of the Z4 roms for RK3368 work on this device also?
Click to expand...
Click to collapse
My Z4 android TV (ATV) ROM should also work with the Z4L.
Just install my custom Z4 custom ROM available at freaktab. I'm a new user here at XDA so it's not allowed to me to post any external link. So just google for the name of my ROM. "[ROM] Z4 RK3368 - android TV (ATV) for Andoer Z4 - ENY EKB368 - Acemax AK838 - Tronfy X6"
Then just flash on top of that ROM the needed Z4L KRS files (resource & kernel) to activate the Z4L RTL8723bs WiFi chip (also described at my freaktab thread).
Good luck and much fun
-cOOLio-
In the end I gave up.
No one can tell me what is the most complete and working firmware.
All firmware always has something that does not work.
Now I still have the firmware 22.12.2015
It's not really a speed champion, but at least it works at all!
does anyone tell me how to get into recovery mode?
I would like to flash the supersu file, but I can not get into recovery
Hi all. Only reason I am thinking of rooting my Shield TV is so I can write to my removable drives. From my understanding is that SDFix does not work with marshmallow. Is this correct? I Would love to access my non adoptable drive from my network. Or if rooted, can i also use FTP to read and write? Thank you.
robjbw said:
Hi all. Only reason I am thinking of rooting my Shield TV is so I can write to my removable drives. From my understanding is that SDFix does not work with marshmallow. Is this correct? I Would love to access my non adoptable drive from my network. Or if rooted, can i also use FTP to read and write? Thank you.
Click to expand...
Click to collapse
Hope this helps... looks like newest update on 1/18/17 (v5.0.1)
"Other Enhancements
*Added ability to write to attached USB or SD card storage."
forums.geforce.com/default/topic/988354/shield-tv/shield-experience-upgrade-5-01-feedback-thread-for-shield-2017-/
I assume you mean network access to the attached storage
SHIELD TV Gen. 2015
write access was, for me, only possible through root and a SMB/samba server.
Root via http://download.chainfire.eu/supersu from chainfire
SMB server via https://play.google.com/store/apps/details?id=com.icecoldapps.serversultimate + https://play.google.com/store/apps/details?id=com.icecoldapps.serversultimate.packb for a native SMB server, normally i use a FTP-server like https://play.google.com/store/apps/details?id=lutey.FTPServer but was not able to get it running on the shield
SHIELD TV Gen. 2017
As of 5.0 i was not able to write to the storage
Actual there is no way to root the 2017 and therefore no SMB server.
The bootloader was updated and ca be unlocked but does not allow to flash the recovery, even if it tells you so (fastboot).
Android 7 recognize a manipulation and reflashes the stock recovery
But i am not sure if 5.0.1 added the network write access storage feature.
robjbw said:
Hi all. Only reason I am thinking of rooting my Shield TV is so I can write to my removable drives. From my understanding is that SDFix does not work with marshmallow. Is this correct? I Would love to access my non adoptable drive from my network. Or if rooted, can i also use FTP to read and write? Thank you.
Click to expand...
Click to collapse
Assuming we're talking a 2017 Shield, I actually managed to access my non-adapted storage over FTP. Without root.
I have a 5TB external HDD hooked up to my Shield, and sideloaded an FTP app. I set my external HDD as root-folder for said app, and could both read/write to it (most recent software update, 5.0.1). I wanted easy management/streaming from my PC though, so I installed WebDrive so I could mount the FTP server as a local drive.
Works like a charm, can post a how-to if required.
Radnu said:
Works like a charm, can post a how-to if required.
Click to expand...
Click to collapse
Yes please!
twe69 said:
Yes please!
Click to expand...
Click to collapse
Updated: We still need FTP to write to an external, non-adopted storage. Viewing can be done over SMB though!
Alrighty then, here goes nothing, please do keep in mind the "fix" you'll find down below is a quick and dirty one. It will allow you to both read and write to your external storage over FTP, without actually needing to have root.
Requirements
1. Sideload Launcher by Chainfire
2. A file manager, preferably with cloud access. I prefer X-plore myself.
3. FTP Server by The Olive Tree (others may work, your mileage may vary).
4. Any FTP client to access your shiny new server.
Step 1
- Install the Sideload Launcher if you haven't done so yet, it will allow us to open APKs that weren't designed for AndroidTV. You can just grab it from the PlayStore.
Step 2
- We're going to need an APK from FTP Server. The easiest way so far seems to be to install it on another device (in my case, my trusty Note3), and "backup" the APK to your Google drive using X-plore as you can see *here*.
- After we've gotten the APK there, hop back to the Shield and open X-plore. Go to your Google drive and install the FTP Server we just put there.
Step 3
- Use the Sideload Launcher to open our FTP server and set it up. Tapping your D-pad "up" once gets us to the settings of the app. Open it, and scroll down till you're looking at something like *this*.
- Most of these settings are up to your own discretion, but I strongly advice to untick "anonymous login" and set a username/pw. The most important bit is to set the home-directory to your non-adapted HDD.
- Close the settings, and tap your D-pad "down" once. Click [ A ], and we should get a nice green icon saying we're up and running! Should be something like *this*.
- The app will "survive" Sleep-mode, but after a restart you'll have to toggle it on again.
Step 4
- Profit!
- You should be able to access your FTP server on your specified local port, and using WebDrive you can even access it easily on a PC. It'll look something like *this*.
- You can use your regular SMB share to view your files over your local network, the catch is that you'll need to use FTP to write to it.
Final note!
It looks like setting X-plore as "default handler" for the non-adapted storage makes it disconnect from your shield. Don't tick it!
I read that writing to the external usb HDD is now fixed in the latest update v5.0.2?
In which case enable the following Settings > Device > Storage & reset > SHIELD storage access > Over local network > On and map the drive to the laptop.
Is this correct? I need to test it out still.
twe69 said:
I read that writing to the external usb HDD is now fixed in the latest update v5.0.2?
In which case enable the following Settings > Device > Storage & reset > SHIELD storage access > Over local network > On and map the drive to the laptop.
Is this correct? I need to test it out still.
Click to expand...
Click to collapse
Don't think so yet. I *can* view and play it, but can't write to it. Screeny over here: imgur,com/ieuhlB0
Any one have luck with this yet? Really hoping to be able to write easy to the external storage.
candymann said:
Any one have luck with this yet? Really hoping to be able to write easy to the external storage.
Click to expand...
Click to collapse
As I explained above, you actually can write to it using FTP (non-adopted storage, no root required whatsoever). Currently I would just advice using the regular SMB share to view it on other devices (since you don't want to download anything before viewing).
I've edited the instructions to clarify.
Here is something I discovered. When you hook up a USB flash drive or HD, it creates some folders on that drive. Android nvidia shield(something like that)
The nvidia folder it creates is writable. I am using a flash drive as non adoptable to play ROMs on with emulators. On the root of the drive I had issues. But once I moved my ROMs folder inside the nvidia folder all was well. No my emulators can load the ROMs from the nvidia folder created on the drive and write the save files to the same folder the ROMs are located in.
Hope this helps. Only issue is that when u restart, you get the annoying pop up asking to adopt the drive. I just hit browse each time.. Because I don't want to adopt it.. I just want it to store files..
Android went plum retarded post kitkat with drives and SD cards and write permissions.. Its very annoying and makes me long for the good OK days where u could just insert something and do with it slas you please... In my opinion they have over complicated what should be a rather simple procedure.. But it looks like this is the direction they have choose..
adam_ky said:
Here is something I discovered. When you hook up a USB flash drive or HD, it creates some folders on that drive. Android nvidia shield(something like that)
The nvidia folder it creates is writable. I am using a flash drive as non adoptable to play ROMs on with emulators. On the root of the drive I had issues. But once I moved my ROMs folder inside the nvidia folder all was well. Now my emulators can load the ROMs from the nvidia folder created on the drive and write the save files to the same folder the ROMs are located in.
...
Click to expand...
Click to collapse
Checked this and the [\\SHIELD\ExternalStorage\NVIDIA_SHIELD] folder is writable over SMB indeed.
Now it's just a matter of whether or not you're willing to put up with the popup.
Hope that helps ya. The android folder is most likely writable as well.
I remember this work around when lollipop came out and apps were not built with the proper permissions. You could use the apps folder in android on the SD card to circumvent this.
But yea I'm good for now just using the shield folder on my flash drive... I do wish there was a way to remove the popup on boot asking to adopt storage though....
I'm beginning to loathe nougat....
The later android versions are hardly usable for me without the use of xposed.
Anyways, hope that trick helps you and anyone else
If you have root couldn't you just mount the drive as writeable using a file explorer? I'm interested in writing to a removable drive in general (don't care about network access specifically).
Any news here?
I am on Nvidia Shield 2017 with 8.0.1 rooted.
I can only READ my attached NAS (network storage).
But I want to get WRITE access too
The workaround with the NVIDIA_SHIELD folder did not work... And Apps like SDfix ends up in error ??!
I own two Shields and need them to write to my NAS.
Does anyone can help me how to get this working?
Both Shields are rooted
Anyone know, if THIS is still actual? (4 years old)
Thank u very much
Kamikaze01 said:
Any news here?
I am on Nvidia Shield 2017 with 8.0.1 rooted.
I can only READ my attached NAS (network storage).
But I want to get WRITE access too
The workaround with the NVIDIA_SHIELD folder did not work... And Apps like SDfix ends up in error ??!
I own two Shields and need them to write to my NAS.
Does anyone can help me how to get this working?
Both Shields are rooted
Anyone know, if THIS is still actual? (4 years old)
Thank u very much
Click to expand...
Click to collapse
Same setup as you. I have been searching everywhere on a way to do this and no luck.
I wanted to use a carplay device with my car . for this purpose I installed a firmware upgrade in order to unable to installation of applications.
After the upgrade, access to files on USB was lost .
Upgrade was taken from here :
That means that before an upgrade, I was able to listen to the music from USB stick via builtin media player. After the upgrade, media player does not see the USB.
For the same reason, carplay app doesnot see the device attached to USB port.
The strange thing is that I can see the files via file explorer ( from the head unit) , they are available at /storage/udisk.
so from one side the unit can see the USB and files, but from other side applications cant see it .
What can be the problem and possible solution ?
The details about versions :
car type : Mitsubishi Outlander 2016
MGCOL_MITSU1
Android version
4.4.2
Baseband version
MPSS.TR.1,0-01780-M8626AAAAANAZM
Kernel version
3.4.0
[email protected]#1
Thu Jan 17 17:33:30 CST 2019
Build number
msm8226-userdebug 4.4.2 KVT49L eng.fengxunyi.20190117.171930test-keys
Permissions... file managers generally have global permissions.
Check through settings under storage and individual apps. That's my guess.
blackhawk said:
Permissions... file managers generally have global permissions.
Check through settings under storage and individual apps. That's my guess.
Click to expand...
Click to collapse
yes , I was thinking about it too.
The problem that when I want to change permissions via this file explorer , I got the error message that I am not root . but I do .
How can I be sure that I do root , or alternatively how to change permissions ?
ostap26 said:
yes , I was thinking about it too.
The problem that when I want to change permissions via this file explorer , I got the error message that I am not root . but I do .
How can I be sure that I do root , or alternatively how to change permissions ?
Click to expand...
Click to collapse
Many times if a app is well coded and needs special permissions it will ask for them during installation. Sometimes they can be set after the fact. Try looking in accessibility.
I haven't played with Kitkat in years but generally it's pretty straight forward. I don't root so know very little on that side. ABD editing might be another option but my knowledge of that is very limited.
Try doing a bunch of Google searches for similar problems with Kitkat storage. The device doesn't have to be the same. You can find solutions many time by cross referencing other devices even platforms.
Many issues are long standing
After the initial search for each parameter, add XDA at the end to find posts here about it easily.
Doing searches for solutions is how I first learned of XDA many years ago
blackhawk said:
Many times if a app is well coded and needs special permissions it will ask for them during installation. Sometimes they can be set after the fact. Try looking in accessibility.
I haven't played with Kitkat in years but generally it's pretty straight forward. I don't root so know very little on that side. ABD editing might be another option but my knowledge of that is very limited.
Try doing a bunch of Google searches for similar problems with Kitkat storage. The device doesn't have to be the same. You can find solutions many time by cross referencing other devices even platforms.
Many issues are long standing
After the initial search for each parameter, add XDA at the end to find posts here about it easily.
Doing searches for solutions is how I first learned of XDA many years ago
Click to expand...
Click to collapse
I rooted the device , gave permissions , but nothing happend.
I put the app in the system/app folder , installed it from there . also does not helped ...
somehow a tool called 'root explorer' can see the usb content, but my app or media player cant see it .
ostap26 said:
I rooted the device , gave permissions , but nothing happend.
I put the app in the system/app folder , installed it from there . also does not helped ...
somehow a tool called 'root explorer' can see the usb content, but my app or media player cant see it .
Click to expand...
Click to collapse
Ummm, I take OTG support for granted... but does your OS/device support it?
Maybe this is the issue?
Incompatible format on the card?
Try formatting card in the device then load data preferably with that device.
Swapping cards between devices can cause issues if each device is writing to it. Haven't seen it happen on Androids but Canon cams, hell yeah.
blackhawk said:
Ummm, I take OTG support for granted... but does your OS/device support it?
Maybe this is the issue?
Incompatible format on the card?
Try formatting card in the device then load data preferably with that device.
Swapping cards between devices can cause issues if each device is writing to it. Haven't seen it happen on Androids but Canon cams, hell yeah.
Click to expand...
Click to collapse
I tried several cards , small and big , formatted in a different ways.
And my device worked in the past , it is something that happened after the upgrade
ostap26 said:
I tried several cards , small and big , formatted in a different ways.
And my device worked in the past , it is something that happened after the upgrade
Click to expand...
Click to collapse
It's rooted?
If it was a OTA upgrade I normally say factory reset time. In your case, not sure that's the right thing to do.
It's not the cards, it's settings or firmware I think it's safe to say.
Try clearing the system cache and a hard reboot.
Try in safe mode to rule out a rogue 3rd party app. Try clearing the data in the associated system apks.
Sometimes poorly coded 3rd party apps can toggle hidden user settings that remain even after uninstall. It's rare but quit the horror when it happens. Scruntinize the apps you installed.
One other irritating thing I've seen happen is clearing the data of a system appd in settings doesn't always remove presumably null marks. When I cleared the data with my package disabler, it fixed the problem.
Saved me a factory reset.
Fun isn't it? Been running down some glitches on my N10+'s, eventually you'll sort it out.
Keep at it over the course of a few days, weeks...
Only persistent is omnipotent