M8s+ Amlogic S812 Devices
---------------------------------------------------------------------------------------------------------------------------------------------------------
M8s+ With s812 amlogic with the XT-S812-V10 Board / Samsung chipset.
ABOUT DEVICE:
Brand: WIIKEE
CPU:Amlogic S812 Quad Core up to 2.0GHz(Cortex-A9)
GPU: Octa Core ARM Mali-450 GPU up to 600MHz
Operation System: Andriod kitkat 4.4 Upgrade to 5.1
RAM: DDR3 2GB
EMMC: 16GB
Shell Material: Plastic
Card Extended: Support SD/TF card up to 32GB
Antenna: Built-in antenna for dual WIFI
Ethernet: 1000M LAN
WIFI:Support Dual wifi 2.4G/5G, IEEE 802.11a/b/g/n
Bluetooth:Bluetooth 4.0
Graphics Type: Integrated Graphics Mali400, Supports 1080P video (1920*1080)
Flash Player:Support Adobe Flash 1.1
Gaming: Built-in 3D Accelerator. Support 3D gaming
Video Decoding: Mpeg1/2/4.H.264,VC-1,Divx,Xvid,RM8/9/10,VP6
Power management: Adapter 5V 2A
And like no other development section. Please make backups before taking this journey with me and im not liable for your messed up bricked device's so CONTINUE AT YOUR OWN RISK!!!
A ton of this info is coming from freaktab.com and some other russian/german sites that ive found. Including the chinagadgets.com updates page for the m8 boxes.
---------------------------------------------------------------------------------------------------------------------------------------------------------
:::::::::::The links::::::::::::
Root:
Rooting these boxes seems to be incredibly simple. They are either prerooted or can be done easily.
Kingoroot app , and kingo superuser app got me enough access to Install img twrp via Rashr app all avalible via the playstore. As well as you can use the updater app to install roms in zip format using the stock recovery without twrp but backups are important! Theres a few recoveries out there for our boxes. Some work for the clones, some dont.
You need to verify if you have the s812 chipset or not.
**************************************************************************************************************************************************
:HOW TO ENTER RECOVERY MODE:
To enter the recovery stock or not, there are multiple methods.
Using a toothpick and pushing the reset button inside the AV port ( Harder/nonrooted )
1.) At the bottom of the AV jack hole is the reset button.
Using a tooth pick hold this button in. You know you have pressed it if you feel the click.
2.) Now plug in the power cord.
3.) While holding the reset button down, wait until you see the logo and you can then release the reset button.
done: The recovery menu should now be shown and the device should update.
ALT For rooted devices:
1.) Install romtoolbox lite and Give romtoolbox superuser permissions
2.) Use the rebooter function inside the app to enter recovery mode. (easier)
To install the custom recovery I used [Root] Rashr - Flashingtool app to install the custom TWRP recovery, this also can be used to install the image files. The images are only the recovery, or boot images for the device. Im assuming here that these images should match the firmware version you are on. IE: 4.4 needs the 4.4 boot/recovery not the 5.1 . The Zips contain the correct boot images for the roms and will flash everything in one shot. The images are a seperate source for modding as well as using the usb flash tool or the apps i suggested. The files came prezipped together to be used with the pre installed updater program on most boxes, Its alot lighter to only update what you need.
---------------------------------------------------------------------------------------------------------------------------------------------------------
Recovery:
Twrp:
Source:
http://freaktab.com/forum/tv-player...-unofficial-twrp-3-0-2-videostrong-acemax-kii
DirectDL:
https://www.androidfilehost.com/?fid=24588212152304611
---------------------------------------------------------------------------------------------------------------------------------------------------------
*****Stock Based Roms***
Roms Zips:
4.0 Roms:
Coming soon.
5.0 Roms:
1.) https://www.androidfilehost.com/?fid=24588212152304603
2.) https://www.androidfilehost.com/?fid=24588212152304604
Tested :
*Wifi
*Playstore
*Root - SU/SuperUser/KingoRoot/KingoSuperUser
*TWRP By Abdul
*Kodi
*Showbox
*BusyBox
Broken Items on 5.1:
* Ethernet Wont connect without manual entry of Ip
* Remote needs re-installed via remote.zip matching remote you have
* Front LED lights get reversed / red is on / blue is off (wont wake up from standby needs unplugged)
----------------------------------------------Custom Roms By Team DevDigitel Universal!!!------------------------------------------------------------------
No Boot.image included, must be on 5.1.1 for this to work, if no boot, restore boot.img only from twrp backup.
Rom:
TeamDevDigitel 5.1.1 -
1.) https://www.androidfilehost.com/?fid=24588212152304711
*StatusBar Fixed must be turned on under display. Resolution may also need adjusted.
*Speed Increases to wifi
*May need your own Build.prop to function perfectly, backup using zipme and flash after flashing this.
*Boot.img not included. Will use your boot.img, bust be on 5.1.1 for this to work!!
Tested :
*Wifi
*Playstore
*Root - SU/SuperUser/KingoRoot/KingoSuperUser
*TWRP By Abdul
*Kodi
*Showbox
*BusyBox
Broken Items on :
* Ethernet Wont connect without manual entry of Ip
* Remote needs re-installed via remote.zip matching remote you have
* Front LED lights get reversed / red is on / blue is off (wont wake up from standby needs unplugged)
----------------------------------------------------------------------------------------------------------------------------------------------------------
Custom Boot.img :
Flash Via Twrp:
For s812 (tested on board xt-s812-v10)
https://www.androidfilehost.com/?fid=24588212152304713
----------------------------------------------------------------------------------------------------------------------------------------------------------
Custom Build Props:
Team DevDigitel Custom Build.prop
Flash Via Twrp:
https://www.androidfilehost.com/?fid=24588212152304712
Others:
http://freaktab.com/forum/development-area/build-prop-tweaking
------------------------------------------------------------------Custom Roms From Others------------------------------------------------------------------
VS/Acemx KII : http://freaktab.com/forum/tv-player...tools-al/571716-rom-vs-acemax-kii-xsatius-rom (based on 4.4)
KII Valkostur : http://freaktab.com/forum/tv-player...rmware-roms-tools-al/553983-rom-kii-valkostur (based on 4.4)
-----------------------------------------------------------OPEN ELEC PROJECT--------------------------------------------------------------
Links:
HOW TO INSTALL VIDEO: https://www.youtube.com/watch?v=QEuBQEGTpP4 (justmeroms)
OpenELEC 6.0 ROMS Below:
OpenELEC-Amlogic-MXiiiG - http://*******/12297117/mxiiig-update
OpenELEC-Amlogic Minix x8HP6.0 - http://*******/1Vfxnq
OpenELEC-Amlogic-M8-6.0 - http://*******/1VLUcI
OpenELEC-Amlogic-M8S-6.0 - http://*******/1VLV3J
OpenELEC-Amlogic-M8S+-6.0 - http://*******/1VLUvn
OpenELEC-Amlogic-S82-6.0 - http://*******/1VLV89
OpenELEC-Amlogic-MXQ -6.0 - http://*******/1VLqJz
Updated files for some that may get black blank screen posted below.
Another Solution for people that get a blank black screen is to use these files and extract all 3 files onto the root directory
of the SD Card.
You sould see ( factory_update_param.aml, recovery.img and OpenELEC.zip) files then do the toothpick method by pressing the micro switch inside and releasing after 5 seconds.
OpenELEC-Amlogic-MXiiiG - http://*******/12297117/mxiiig
OpenELEC-AMlogic Minix x8HP6.0 - http://*******/1VfxUv
OpenELEC_6.m M8/M8N - http://*******/1VdS7g
OpenELEC_6.0 M8s - http://*******/1VdSXO
OpenELEC_6.0 M8s+ - http://*******/1VdSfS
OpenELEC_6.0 s82 - http://*******/1VdSmi
OpenELEC_6.0 MXQ - http://*******/1VdSuR
Added 27.03.2016
OpenELEC 6.0.1 MX2 - http://*******/12297117/openelec601-mx...
-----------------------------------------------------------------EtertainmentBox-----------------------------------------------------------------
Etertainment Box Brand M8s Stock Dl - https://www.entertainmentbox.com/latest-m8s-firmware-download/
DL Mirorr: N/A
-------------------------------------------------------------------------------------------------------------------------------------------------------
Apps:
KingoRoot : https://root-apk.kingoapp.com/kingoroot-download.htm
KingoSuperuser : https://superuser.kingoapp.com/
{Root} Rashr - Flashtool :http://forum.xda-developers.com/showthread.php?t=2334554
Romtoolbox: https://play.google.com/store/apps/details?id=com.jrummy.liberty.toolbox&hl=en
Busybox: https://play.google.com/store/apps/details?id=com.jrummy.busybox.installer&hl=en
SuperSu: https://play.google.com/store/apps/details?id=eu.chainfire.supersu&hl=en
Kodi: https://play.google.com/store/apps/details?id=org.xbmc.kodi
Zipme: https://play.google.com/store/apps/details?id=zip.me&hl=en
Tons of others : https://www.entertainmentbox.com/official-android-tv-box-apps/
---------------------------------------------------------------------------------------------------------------------------------------------------------
Utilities:
Usb img burning tool: https://mega.nz/#!cJ1RnI4T!S2dq8VnObB4TLSHjCvJBx7zD5A__LPrLKvm999qsxwY
How To Usb Burn tool:
[Video]
http://chinagadgetsreviews.blogspot.ro/2014/08/how-to-easily-flash-firmware-on-probox2.html
Unbrick M series boxes:
[Video] https://youtu.be/1o7KQaLAEeU
Identify your box:
http://freaktab.com/forum/tv-player...ilogic-device-is-bricked-read-this-post-first
----------------------------------------------------------------------------------------------------------------------------------------------------
Remote Configure zips:
These are flashed to get the stock remotes found for these boxes working aftee changing roms.
The remote config files are located at
/System/ETC/remote.conf
These will determine what keys on the remotes do.
Link to Download Zips:
http://freaktab.com/forum/tv-player...tools-af/18312-s802-multi-remote-patcher-zips
---------------------------------------------------------------------------------------------------------------------------------------------------------
*
*
*
*::::::::::::::::::::Resources::::::::::::::::::::
Freaktab Amlogic Based Devices. S8xx Series
http://freaktab.com/forum/tv-player-support/amlogic-based-tv-players
JustmeRoms
https://justmeroms.com/
Chinagadgets.com Firmwares Page
http://chinagadgetsreviews.com/firmwares
S8xx Chipse Devices UNIVERSAL ROM:
Roms Zip:
4.0:
Coming Soon
----------------------------------------------Custom Roms By Team DevDigitel Universal!!!------------------------------------------------------------------
No Boot.image included, must be on 5.1.1 for this to work, if no boot, restore boot.img only from twrp backup.
Rom:
TeamDevDigitel 5.1.1 -
1.) https://www.androidfilehost.com/?fid=24588212152304711
*StatusBar Fixed must be turned on under display. Resolution may also need adjusted.
*Speed Increases to wifi
*May need your own Build.prop to function perfectly, backup using zipme and flash after flashing this.
*Boot.img not included. Will use your boot.img, bust be on 5.1.1 for this to work!!
Tested :
*Wifi
*Playstore
*Root - SU/SuperUser/KingoRoot/KingoSuperUser
*TWRP By Abdul
*Kodi
*Showbox
*BusyBox
Broken Items on :
* Ethernet Wont connect without manual entry of Ip
* Remote needs re-installed via remote.zip matching remote you have
* Front LED lights get reversed / red is on / blue is off (wont wake up from standby needs unplugged)
** If playstore wont Login through app. Go to settings/more settings/accounts and sign in through there.
If playstore wont download apps or fully load up like its not getting network. Go to settings/more settings/Apps/ and force.stop.playstore and clear its data.
Enjoy
----------------------------------------------------------------------------------------------------------------------------------------------------------
Custom Boot.img :
Flash Via Twrp:
For s812 (tested on board xt-s812-v10)
https://www.androidfilehost.com/?fid=24588212152304713
----------------------------------------------------------------------------------------------------------------------------------------------------------
Custom Build Props:
Team DevDigitel Custom Build.prop
Flash Via Twrp:
https://www.androidfilehost.com/?fid=24588212152304712
Reaerved 2
Reserved 3
Reserved 4
Reserved 5
Bare with me
Please hit Thanks Button On Main Op;
This helps me know if this is helping people and being used!
also, this work is free of charge and its motivational!
Now that the base info is up. Is anyone on this side of xda interested in getting xdas android tv boxes more orginized and displayed? If not ill just limit my work to what i developed for and move on..
Using brackets on your posts helps users navigate the forum so much easier.
[Wip] work in progress
[Rom] Flashable rom
[Q&A) questions section to keep forums clean
[Dev] developers needed / open project
[Guide] walk throughs
Identifying the model is good, but identification of your chipset is the important part. These boxes are heavily clones and sold as whatever the distributor said it was. And a lot of times it wasnt what you thought it was.
Rkxxxxx S8xxxxx Txxxxxx Etc is how you will be locating the correct firmwares for your devices. Im hoping that in the future we can go cross platform/chipset by including the correct boot.img and xml/build.prop files for the right chips and the software will be universal (ish)
See post #2 for Universal rom Flash.
Highly suggest only using TWRP and backing up to your external SD.
the build.prop and the boot.img are both twrp flashable files.
these also can be used to put your stock boot.img or build.prop after flashing a universal softwear rom to gain all
your device specifics back. the custom one is based on m8s/+ models and was off a 16gb device so both 8/16 can flash.
you can alos use the app zipme to make your own flashable zips. great for backing up certain files.
remote.config is another one thats important to backup from your original build the device shipped with!
how to adjust twrp screeen size
screen size is to big on my tv i cant navigate some keys on my usb keyboard,, imean i cant navigate twrp properly using my navigation keys on my wireless key board...pls help thanks
Hey man first of all big thanks for the THREAD, is very hard to find some information about all of this you have no idea how this thread can help us with these android TV devices (F**** smart TV's)
So i have a S82 Plus, with the android 5.1.1, kernel 3.10.33, fimrware 101L1 and running silk and smooth the only problem for me is the remote controler that i bought... doesn't work well some keys and functions just dont work!! and i don't know why..
And i was thinking maybe i just the ROM because if i put to work with my computer works fine, if i put it with my S4 works well too...
So i was thinking is there any 6.0 rom for this device?? Would you recommend another one to try??
My Remote is the measy rc12-b5
Big thanks again for the help!!
nice i finally found this thread all i really want is to make it like a basic tablet with out the crap. Where can i learn how to dump a new box and change it to work like a tablet. btw the game myvegas doesnt work
Hi Team DevDigitel thanks for your work
I think this will be a great place for M8s owners .
My Box is a M8S now running this 5.1 rom (M8S(n200c)_to_M8S+ 5.1 20151022-aml_upgrade_package) it works fine only no WIFI and no remote seams that only 2 of the 4 cpu cores are working non rooted
download (M8S(n200c)_to_M8S+ 5.1 20151022-aml_upgrade_package) here https://mega.nz/#!ZUxQSJQK!nt8g1nGV6jdTe3mZFa3_aXPY4UcXTaLQuUIGK-c-jbg
Threre is also a android 4.4 rom what is working okay pre rooted (M8S_aml_upgrade_package_16.0_20160229)
download https://drive.google.com/file/d/0B4NYLg8trzWdYl82UlpteHppOU0/view
I cant get my box into recovery whit the sd card toothpick method
I only can flash img whit usb burningtool
Goal to get a fully working 5.1 rom whit working wifi and remote in img because my M8S cant get into recovery whit SD card toothpick method
it also be nice to have root so i can boot in recovery
I hope that this becomes a place to collect and develop M8, M8S M8S+ roms
I recently bought m8s+ and wondering if we can get latest 6.0 firmware on this tv box btw it came with 5.1 Lollipop.
I second that also make sure the MyVegas app works from google play. It didnt with the last firmware
Hi i want know how i can unpack and repack stock rom? I want change the stock apk with other ones! Otherwise there is another method?
All the tools create an incompatible system.transfer.list (not for android lollipop 5.1.1!) because the version that will be created is 1 but the original version of 5.1.1 is 2!
And so when i flash a new rom i get this error: unexpected transfer list version [1 ]
I tried to change version with notepad++ and the error no longer appears but the firmware cannot be flashed because the installation starts but doesn't complete!
Please help me
Stock system.transfer.list:
Code:
2
146445
0
0
erase 2,0,262144
new 32,0,32767,32768,32770,32833,32835,33347,65535,65536,65538,98304,98306,98369,98371,98883,131071,131072,131074,163840,163842,163905,163907,164419,196607,196608,196610,229376,229378,229441,229443,229955,247047
Repack system.transfer.list
Code:
1
150644
erase 2,0,262144
new 84,0,64,65,179,579,580,4675,20050,20053,22476,22479,22487,22490,22491,22500,22506,22517,22671,22672,23814,23826,24082,24094,25259,25260,32767,32768,32770,32833,32834,33347,41193,41196,45537,45538,49457,49464,49622,49623,54103,54105,54112,54118,54139,54140,54141,54160,55263,55264,65535,65536,65537,98304,98306,98369,98370,98883,122919,122920,123534,123539,131071,131072,131073,163840,163842,163905,163906,164419,166592,166593,196607,196608,196609,229376,229378,229441,229442,229955,254995,254996,255021,255074,255906
Big thanks for the ROMS!
I just want to say thank you for your big effort on making these ROMS! :good:
Like my username indicates, I finally got my troublesome M8S box working flawlessly with Android Lollipop, in which your Universal ROM was the key. I documented my steps in another related thread.
m8s+ firmware IMG format for USB method
Hi,
Where I download rom (android 5.1.1 lollipop on 2016.1219) for IMG format for USB upgrade method?
I have problem at upgrade SD card method.
gorus1 said:
Hi,
Where I download rom (android 5.1.1 lollipop on 2016.1219) for IMG format for USB upgrade method?
I have problem at upgrade SD card method.
Click to expand...
Click to collapse
Here you are https://androidtvbox.eu/new-firmware-m8s-tv-box-amlogic-s812-20161219-release/
Thanks for link, but I need have ROM in IMG format becose i have problem with SD card port.
I downloaded ROM from link and unzipped this, but there is no IMG format.
Sorry, maybe something I do not know, but I need have IMG compilation.
Please for help!
Related
INTRODUCING THE SAMSUNG GALAXY S3 UNIFIED TOOLKIT
SUPPORTED MODELS
INTERNATIONAL [GT-I9300] SUPPORT THREAD HERE
AUSTRALIAN MODEL GSM [GT-I9300T]
INTERNATIONAL [GT-I9305/GT-I9305N] SUPPORT THREAD HERE
AUSTRALIAN MODEL LTE [GT-I9305T]
C SPIRE MODEL LTE [SCH-L710]
AT&T US [SGH-I747] SUPPORT THREAD HERE
BELL, ROGERS, SASKTEL, TELUS [SGH-I747M] [SGH-I747M] USE AT&T SUPPORT THREAD
US CELLULAR MODEL LTE [SCH-R530] USE AT&T SUPPORT THREAD
METRO PCS MODEL LTE [SCH-R530M] USE AT&T SUPPORT THREAD
SPRINT US [SPH-L710] SUPPORT THREAD HERE
TMOBILE US [SGH-T999] SUPPORT THREAD HERE
MOBILICITY, VIDEOTRON, WIND [SGH-T999V] USE TMOBILE SUPPORT THREAD
VERIZON US [SCH-I535] SUPPORT THREAD HERE
CHINA ANYCALL CDMA MODEL [SCH-I939] USE GT-I9300 SUPPORT THREAD
Click to expand...
Click to collapse
The Unified Android Toolkit supports a multitude of Nexus and Samsung devices with more devices being added all the time. There is also an option at startup to run a Basic Android Toolkit which any Android device can use to install drivers, make app backups, install apk files, reboot the device into different modes and run a command prompt for manual input.
FUNCTIONS OF UNIFIED ANDROID TOOLKIT V1.3.4 [9TH JAN 2015]
* Install correct adb/fastboot drivers automatically on Windows xp/vista/7/8 32bit+64bit
* Backup/Restore a single package or all apps, user data and Internal Storage
* Backup your data from selectable folders [internal or external storage] to your PC for a Full Safe backup of data
* Unlock/Re-Lock your Bootloader [Nexus]
* Root Stock builds
* Various Root options using insecure boot image or custom recovery
* ALLINONE to Unlock, Root, Rename the Restore Files and install busybox [Nexus]
* ALLINONE to flash custom Recovery Root, Rename the Restore Files and install busybox [Samsung]
* Install BusyBox on your device
* Perform a FULL NANDROID Backup of your system (Boot, Cache, Data, Recovery and System) via adb and save in Custom Recovery format on your PC which can be Restored via CWM Recovery [if insecure boot image available]
* Fix extSdCard write permissions from installed apps in Android 4.4+ [Samsung]
* Pull /data and /system folders, compress to a .tar file and save to your PC [if insecure boot image available]
* Dump selected Device Partitions, compress to a .zip file with md5 and save to your PC [if insecure boot image available]
* Extras, Tips and Tricks section
* Auto Update ToolKit to latest available version at startup (professional only feature)
* Program up to 10 Quickpick slots and run them very quickly (professional only feature)
* Mods section to automatically perform certain tasks on your device
* Download Google Stock Image directly to correct ToolKit folder for extracting and flashing [Nexus]
* Check md5 of stock image to make sure downloaded file isn't corrupted before flashing [Nexus]
* Download Samsung Stock Firmware to PC for extracting and flashing via Odin [Samsung]
* Flash Custom Recovery or Google Stock Image to Device
* Rename the Recovery Restore File present on some Stock Roms
* Boot into CWM Touch, TWRP, Philz Touch Recovery or Stock Recovery without Flashing it [Nexus]
* Flash Custom Recovery to Device
* Boot [Nexus] or Flash .img Files directly from your PC
* Install a single apk or multiple apk's to your device
* Push Files from your PC to your device
* Pull Files from your device to your PC
* Disable forced encryption on Nexus6 and Nexus9 devices
* Install Root Checker app by Burrows Apps
* Install Backup/Restore app by MDroid Apps [calls log, sms, contacts]
* Install EFS/Partition Backup/Restore app by Wanam
* Dump selected LogCat buffers to your PC
* Dump BugReport to your PC
* Set Files Permissions on your device
* Open new Command Prompt for manual input
* Reboot device to Fastboot Mode or Android from fastboot mode [Nexus]
* Reboot device to Fastboot Mode [Nexus], Recovery, Android or Download Mode [Samsung] from adb mode
* Display Important Information about your device
--------------------------------------------------------------
SUPPORTED DEVICES AND LATEST SUPPORTED BUILDS *HERE*
DOWNLOAD THE SKIPSOFT UNIFIED ANDROID TOOLKIT *HERE* (FROM SKIPSOFT.NET)
NOTE: As the exe files are not Digitally Signed with a Microsoft Certificate they 'may' get picked up as potentially harmful by Antivirus Programs and deleted on first run. If this happens restore the file and exclude it from future scans to use it. This seems to happen mostly on AVG Free and Norton which is why I switched to BitDefender which is much better.
Credits: Chainfire for SuperSU, koush and the clockworkmod team for cwm and the universal driver pack, 1wayjonny for the adb/fastboot driver pack, Adam Lange for all his support and help with the insecure kernels.
--------------------------------------------------------------
WHAT IS THE DIFFERENCE BETWEEN PUBLIC (FREE) AND PROFESSIONAL (DONATE) VERSIONS?
THE PUBLIC VERSION OF THE TOOLKIT INCLUDES EVERYTHING YOU COULD NEED TO MANIPULATE YOUR DEVICE. NOTHING IS RESTRICTED.
ACTIVATING THE PROFESSIONAL VERSION ADDS THE MOST USEFUL FUNCTION IN THE TOOLKIT, THE ABILITY TO CHECK FOR 'AUTO UPDATES' DIRECTLY VIA THE TOOLKIT AND HAVE THEM PUSHED TO YOUR PC RIGHT AWAY AS SOON AS THEY ARE UPLOADED WITHOUT NEEDING TO DOWNLOAD THE WHOLE TOOLKIT EVERY TIME. YOU WILL ALWAYS HAVE THE LATEST VERSION AS SOON AS IT IS MADE AVAILABLE. THIS MEANS SMALLER UPDATES CAN BE SENT OUT MORE FREQUENTLY, SUCH AS ADDING A SINGLE FUNCTION, FIXING A BUG OR ADDING COMPATIBILITY FOR A SINGLE CARRIER. THE SMALLER UPDATES WILL BE COMPILED AND RELEASED TO THE XDA COMMUNITY AS A FULL (PUBLIC) DOWNLOAD VERSION SO PROFESSIONAL VERSIONS ARE ALWAYS UPDATED SOONER.
THE PRO VERSION ALSO ADDS THE ABILITY TO CHECK FOR THE LATEST VERSION OF SUPERUSER AND RECOVERY FILES AND DOWNLOAD THEM DIRECTLY TO THE TOOLKIT.
THE 'QUICK PICKS' SECTION[/B] ALLOWS YOU TO PROGRAM UPTO 10 SLOTS WITH TASKS THAT YOU MAY PERFORM ON A REGULAR BASIS OR JUST WANT TO KEEP A SET OF TASKS IN 1 PLACE. THEN JUST SELECT THE SLOT AND IT WILL REMEMBER ALL YOUR SETTINGS FOR THAT TASK AND RUN IT.
PRO USERS CAN ALSO SELECT THE "ANY BUILD" OPTION IN THE BUILD SELECTION SCREEN TO ROOT ANY BUILD (USEFUL IF YOUR BUILD IS NOT LISTED).
AUTO REPLY LINKS FOR PAYPAL TO GET A CODE INSTANTLY CAN BE FOUND AT http://goo.gl/nyGqv
--------------------------------------------------------------
PLEASE READ THE *HELP* PAGE AT http://www.skipsoft.net/?page_id=1269 OR USE THE INFORMATION SECTION WITHIN THE TOOLKIT IF YOU HAVE ANY QUESTIONS. I HAVE TAKEN A LOT OF TIME TO WRITE IT AND SOMETHING ON THERE SHOULD ANSWER 99% OF PROBLEMS.
--------------------------------------------------------------
1. INSTALLING ADB/FASTBOOT DRIVERS
The first thing you need to do is to install the adb/fastboot drivers. These are needed so that you can unlock your bootloader, root your device and perform other adb/fastboot functions.
THE DRIVERS CAN BE INSTALLED DIRECTLY VIA THE TOOLKIT. OPTION 1 IN THE MAIN MENU.
If drivers are not installed or there is an exclamation mark next to the device:
Plug the device in to a usb cable directly connected to your motherboard.
In the Device Manager a new item, usually called Android 1.0 should pop up in the list.
Right click on the device item then left click on Update Driver Software. Select 'browse my computer' and then 'Let me pick from a list'.
If no adb interface driver appears in the list then untick 'Show compatible hardware' and find the Android or Samsung adb interface driver.
If you cannot find either of these click Have Disk, browse to the Toolkit install folder, drivers folder, click on android_winusb.inf and click Open.
Click OK and select Google ADB Interface.
Make sure you have USB debugging enabled in settings, developer options. In Android 4.2.2 or later you have to enable the developer options screen by going to settings, About on your device and click on Build number at the bottom 7 times until it says You are now a developer. If you have already enabled usb debugging then unplug/replug the usb cable.
On Android 4.2.2 or later when you replug the usb cable after enabling usb debugging for the first time you will get a popup asking you to authenticate your pc. Tick 'Always allow' then click 'ok'.
--------------------------------------------------------------
2. USING SKIPSOFT UNIFIED ANDROID TOOLKIT
When starting the Toolkit you will first be asked which device you want to work with. Working folders will be created and the device files downloaded. You will then be taken to the Model/Build selection screen where you can do a number of things (other than select your model/build): Type '00' to enter your activation code and enable pro features, 'i' will take you to the Information and Help Section, 'a' will give you information on how to add support for a new build.
Supported builds are listed in the Model/Build selection screen and typing the associated number (i.e. 11) will download needed boot and recovery files (stock and custom recovery) then check for and download the latest superuser files available and custom recovery (pro versions only), verify all the files and start the Main Menu. You can now use all the functions and tools the Android Toolkit offers. Pro users can select the "any build" option to root any build (useful if your build is not listed).
--------------------------------------------------------------
USEFUL INFORMATION
How to get into Recovery Mode
1. Unplug the USB cable.
2. Shut down the phone.
3. Hold down the 'HOME' + 'VOLUME UP' buttons and press the 'POWER' button for about 5 seconds to enter Recovery Mode.
How to get into Download Mode (For Odin)
1. Unplug the USB cable.
2. Shut down the phone.
3. Hold down the 'HOME' + 'VOLUME DOWN' buttons and press the 'POWER' button for about 2 seconds until a WARNING! Screen appears. Press the 'VOLUME UP' button to enter Download Mode.
--------------------------------------------------------------
*DISCLAIMER*
I take no responsibility for any fault or damage caused by any procedures within this guide. No warranties of any kind are given.
**UPDATES AND UPDATE CHANGELOG**
This Updater file will update your Toolkit to the latest version and add the latest support the Toolkit offers. Download the below file, move the file to the Toolkit installation folder and run the file to update to the latest version.
THIS IS AN XDA EXCLUSIVE AND MUST NOT BE REDISTRIBUTED IN ANY FORM!!
IF YOU ARE PLEASED WITH HOW THE TOOLKIT WORKS DON'T BE TIGHT AND CONSIDER DONATING TO THE PRO VERSION TO SAY THANK YOU AND GET UPDATES PUSHED STRAIGHT TO YOUR TOOLKIT WITHOUT HAVING TO UPDATE MANUALLY. A LOT OF WORK GOES IN TO THE TOOLKITS AND IM ALWAYS TRYING TO MAKE THEM BETTER. THANK YOU.
**FAQ**
Q. Help me I can't find my build in the Model Selection Screen
The Toolkit includes a selection of Insecure Boot Images to cover all the different builds available. As there are very many different builds it is impossible to include an image for every single build but some builds share the same Boot Image. If you have a build that isnt listed on the Model Selection Screen you can therefore use a similar build. The best way to go is up to the next available build as it should offer more compatibility with the build you are using but if that isn't available then try the next build below your one as it should still be almost identical as long as it is the same version (ie. 4.1.1).
The Model Selection Screen is there so that if a task in the ToolKit requires an insecure kernel [to perform adb root commands] and your phone doesnt already include one, a compatible boot image [with an insecure kernel included] can be flashed to provide adb root access.
If you have a Custom Rom flashed to your phone then it will most probably have an insecure kernel included so it doesn't really matter if your build is not listed on the Model Selection Screen and when asked [by certain functions] if you have an insecure kernel on your phone you can answer 'yes'. However if the function fails then your kernel may not be insecure in which case you can flash one from the ToolKit. If you need to do this make sure the right build [or closest available build] is set so you flash the right image for your phone.
----------------------------------------------------------------------------
Q. What is ADB Shell?
Adb shell is a linux command line tool (because android is based on linux) used to send commands to your android device. For S-ON devices, this is crucial for modifying files in the /system partition (where the rom sits) as you cannot modify anything in /system when the rom is running without S-OFF like removing system apps.
----------------------------------------------------------------------------
Q. Why do I need to back up my IMEI/EFS and how do I do it?
There well protected section of your device that is virtually immune to any kind of flashing and manipulation (unless of course you know how to access it). This part of the device contains information such as IMEI (or MEID and ESN in the case of CDMA devices), programming parameters for the device such as your account information (phone number, etc), data provisioning parameters, and a whole bunch of other things that, when not handled properly, can render a device completely useless. All of these are contained in the infamous \EFS folder. If anything messes with your EFS folder, unlike flashing a device (which could potentially lead to bricks as well) it could render your device completely useless as it will no longer be recognized by your carrier. If you are not planning on flashing anything to your device and want to stay on pure Stock then you may never have any problems but it is still advisable to backup this information just in case (better to be safe than sorry). If you have a GT-I9300 GSM Model then you can do this from the Toolkit but if you have an LTE device then it isn't soo easy to do. If you have an LTE device you should go to *THIS* thread by lyriquidperfection and follow the information to save your IMEI/NV Data so that you are covered if anything should happen.
----------------------------------------------------------------------------
Q. Is there currently no way to root the Samsung Galaxy S3 without voiding the warranty?
All methods of rooting will void your warranty in some way as you will have superuser files on your phone that arent supposed to be there. There is a method of rooting your phone without increasing the flash counter which involves flashing a complete rom with root files already added but if anything happens and you need to send it back under warranty you will need to flash a 'proper' Stock Rom back before returning it or your warranty will be void. Flashing a custom kernel or recovery to root will increase the flash counter and also void any warranty. There is currently no method of resetting the flash counter on Snapdragon models but im pretty sure there will be some support for it soon. If you dont want to risk it or you aren't sure then you shouldnt really be flashing your phone and should just leave it alone. Its your choice .
----------------------------------------------------------------------------
Q. Will flashing Stock ROM via odin using the toolkit replace everything that was flashed before? recovery? etc?
Yes a Stock Image flashed via Odin will replace all your key partitions (boot, recovery, system) with the stock firmware. If you want to reset the phone back to an 'out of the box' state then you want to enter recovery and do a wipe first which will reformat your userdata partition.
----------------------------------------------------------------------------
Q. I flashed Custom Recovery but each time I reboot the Stock Recovery is back
There is an auto recovery restore system on certain Stock Android Builds that will reflash the Stock Recovery if you flash CWM on a Stock Rom.
Use Root Explorer to Mount the system folder as R/W (or use a free app from Google Play such as ES File Explorer). Rename the files /system/recovery-from-boot.p and /system/etc/install-recovery.sh (requires root). Now when you flash Custom Recovery it will NOT be overwritten after a reboot. You can also do this via the Toolkit.
----------------------------------------------------------------------------
Q. My AntiVirus program says the Toolkit files may be harmful
The exe compiled files are not digitally signed with a Microsoft certificate (as they cost money) so certain AntiVirus programs (mainly Norton and AVG Free) may pick it up as potentially harmful when it is not. They will pick up ANY file that doesn't contain a purchased Microsoft certificate in the same way. Just Restore the deleted file and exclude it from further scans and it will be fine. Or switch to a better AntiVirus program such as BitDefender.
----------------------------------------------------------------------------
Q. I flashed the Toolkit Boot Image, now my wifi + bluetooth won't work
The boot images are made from Stock with only needed changes made to the insecure boot images [modified adbd, default.prop and rc.local edited] and will work on all stock roms. If you flash them to a custom rom and the rom has been altered or uses a custom boot image then it will boot but certain modules may not load such as wifi or bluetooth. In this case you can use the boot image to root or perform adb root functions but will need to flash back the boot image for the custom rom to get other functions working again. This is not a fault of the Toolkit but a difference to stock in the custom rom.
----------------------------------------------------------------------------
Q. I am having trouble getting adb working with the drivers installed
Try switching your connection type from media (MTP) mode to camera mode (P2P). To do this open the notification area, click where it says connected as and change from MTP to PTP.
----------------------------------------------------------------------------
Q. I want to send my device back for warranty purposes
1. Follow the instructions to reset your flash counter with TriangleAway.
2. Download and flash a Stock Firmware image from the download section.
3. Boot into Stock Recovery and perform a wipe/factory reset
.
Your internal storage will be formatted and data and cache wiped. Your device should now be back to an out-of-the-box FULLY STOCK state with the flash counter [shown if you boot to download mode manually] reset and ready to send back.
----------------------------------------------------------------------------
Q. When connecting the phone I get 'USB Device not Recognized' and no serial number shows in the ToolKit
I actually had this problem recently and what fixed it for me was to make sure that the drivers have been installed, then shut my phone down plug the usb cable in and restart it. The phone booted up and the device was recognized and drivers installed correctly. May not work for everyone but worth trying.
Changelogs from previous builds to the Unified version
ToolKit v6.0 (08th November 2012)
+Added Full Support for International LTE Model GT-I9305
+Updated root support for latest 4.1.1 builds
+Added new Builds to Model Selection Screen
+Added Hotfile links to Stock Firmware for both Models in Downloads Section
+Added choice of Superuser or SuperSU on all root procedures
+Added choice of Custom Recovery when rooting (I9300 only)
+Updated Samsung USB Drivers to v1.5.15.0 (latest version)
+Added Device Information Screen from Main Menu
+Fixed Odin Tar Creator crashing
+Disabled ICS mods being enabled on JB builds which could soft brick the device
+Added NEW ‘Quick Picks’ Donators Feature
+Re-wrote lots of procedures to incorporate the Quick Picks Feature
+Re-ordered some functions on the Main Menu
+Added solution if CWM Root boots into Stock Recovery after flash
+Fixed lots of parts to improve the Toolkit
ToolKit v5.0 (23rd August 2012)
+Added Root Support for new Jelly Bean Builds
+Added Model Selection Screen at startup for selecting different builds
+Added cwm unroot zip file for quick unroot without wiping and flashing stock firmware
+Added cwm root for Superuser or SuperSU
+Added new Stock and Insecure kernels
+Added new Stock Recovery images
+Added new Stock Firmware download method and new links to various Stock Images
+Wrote new Date/Time method to give support for non UK Regions in various functions
+Added teaser for upcoming Quick Pick function
+Added new options to Settings Screen
+Added ‘Help’ option on Model Selection Screen
+Added ‘Auto Update’ check in Settings Screen
+Checked entire code and made edits to parts
ModsSection v2.1 (23rd August 2012)
+Updated Date/Time stamp method
+Updated NAND Backup script
+Added Jelly Bean detection for mods that do not work on that build
ToolKit v4.0 (24th July 2012)
+Added Auto Update Feature (at startup)
+Added 1-Click tar file creator to flash via Odin (from upto 10 images placed in the INPUT folder)
+Added Donator Features Activation from within ToolKit
+Changed Extras Section for new Activation method
+Added CWM Touch 6.0.1.0 to ToolKit
+Added Reboot to Download + Start Odin in ‘Reboot Phone Options’ screen
+Edited backup scripts for easier operation
+Removed Sim Unlock Tool for further testing
+Various tweaks
ModsSection v2.0 (24th July 2012)
+Added NAND backup option when starting to safe guard against bad mods
+Fixed some code
ToolKit v3.0 (4th July 2012)
+Added CF-CWM Recovery (thanks to Chainfire) as option
+Added cache.img dump to backup options
+Fixed /efs backup/restore tool from previous version not working
+Added Galaxy S3 SIM Unlocker by Adam Lange
+Added Samsung Cache Ripper by Adam Lange
+Updated Odin Flash Tool to v3.07
+Added option to NAND backup to Internal or External Storage + keep/delete files on phone after completion
+Added Rename Recovery Restore files for future proofing
+Fixed CWM Rooting as it wasnt working (incorrect script)
+Lots of re-written code for better functionality
+A few minor bug fixes
+A few other things I forgot to write down
ToolKit v2.0 (22nd June 2012)
+Updated CWM Recovery to Touch v5.8.4.3
+Updated Samsung drivers to v1.5.5.0
+Added text on NAND Restore option to check free space (2GB) before starting
+Streamlined Odin flash process. Phone will now automatically reboot into Download Mode
+Added Download Mode to reboot options
+Added Download, extract, flash Stock Rom option. Everything you will ever need to know is in there
+Added Stock Boot Image option
+Added full information on Resetting flash counter
+Alot more minor stuff
ModsSection v1.0 (22nd June 2012)
+Added first version of Mods Section. 3 mods
available for now with more to be added
ToolKit v1.0 (10th June 2012)
+First version of SGS3 ToolKit released
thanks for the great app! coming form galaxy nexus (thanks god i sold it) and knowing it will work flawlessly waiting for dl link
great application
Download link posted in Post#1
Mark.
AWESOME !!
Amazing work ! Can't wait to see what the future holds for this app !!
@mskip good to see u here and congrats on becoming a MOD :0)
Coming from the Galaxy Nexus,and i used your toolkit software many many times and it worked like magic..and im sure this one will be the same
Sent from my GT-I9300 using Tapatalk 2
Hi Mark,
amazing work and very useful app,
thank you very much!
Absolutely Perfeeeeect tool
Amazing, wonderful. Damn job dude. no words at all. U all DEVS ROOOOCKS. AMAZING GUYS HERE.
sooo goood baby baby
Used your toolkit on my Gnex (so easy to use )
And now we can enjoy it on the S3 !! Thank you mskip, for your great job, and for sharring this wonderful tool !
thank you very much good business
Thank You from a fellow East Anglian S3'er
72931761ND9517718
PS: ROM Manager isnt great with Sammy devices - may want to update first post to recommend use of CWM Manager instead.
Cool look epic good work :thumbup::thumbup::thumbup::thumbup:
Sent from my GT-I9300 using xda premium
Very good work!!
I test now the backup options. I already made an efs-backup and try now to make a full backup of the internal sd-card. Till now everything work very well.
Thanks very much for the toolkit!!
subvertbeats said:
Thank You from a fellow East Anglian S3'er
72931761ND9517718
PS: ROM Manager isnt great with Sammy devices - may want to update first post to recommend use of CWM Manager instead.
Click to expand...
Click to collapse
Thank you very much
First post updated, I just took out the link to Rom Manager as I have never used CWM Manager and dont know if you can get to CWM directly from the app.
What part of East Anglia?
Mark.
hurray said:
Very good work!!
I test now the backup options. I already made an efs-backup and try now to make a full backup of the internal sd-card. Till now everything work very well.
Thanks very much for the toolkit!!
Click to expand...
Click to collapse
You're welcome
If you find any bugs or have any opinion on improvements please let me know as im working on the mods and extras section now for the next version.
Mark.
oned said:
Used your toolkit on my Gnex (so easy to use )
And now we can enjoy it on the S3 !! Thank you mskip, for your great job, and for sharring this wonderful tool !
Click to expand...
Click to collapse
Although the S3 is a bit harder to automate without fastboot flashing I hope the ToolKit can be every bit as good as for the GNex (maybe even a bit better)
There will certainly be alot more mods in the mods section
Mark.
[TOOLKIT] UNIFIED ANDROID TOOLKIT - SAMSUNG GALAXY NOTE 10.1 [2014] - Drivers, Root, Recovery + MORE
SUPPORTED MODELS/VARIANTS
WIFI ONLY MODEL [SM-P600] [Supported up to 4.4.2]
3G/WIFI MODEL [SM-P601] [Supported up to 4.4.2]
LTE/WIFI MODEL [SM-P605] [Supported up to 4.4.2]
The Unified Android Toolkit supports 22 Android devices: Galaxy Nexus, Nexus 4, Nexus 5, Nexus 6, Nexus 7 [2012], Nexus 7 [2013], Nexus 9, Nexus 10, Samsung Galaxy S3, Samsung Galaxy S3 Mini, Samsung Galaxy S4, Samsung Galaxy S4 Mini, Samsung Galaxy S5, Samsung Galaxy Note 2, Samsung Galaxy Note 3, Samsung Galaxy Note 4, Samsung Galaxy Note 8.0 [2012], Samsung Galaxy Note 10.1 [2012], Samsung Galaxy Note 10.1 [2014], Samsung Galaxy TabS 8.4 and 10.5 models [2014], Samsung Galaxy Camera (smartcamera) and Samsung Galaxy Gear [smartwatch] on Android Only. The Galaxy Gear Toolkit module will not work if the watch is using the Tizen operating system. There is also a Basic Android Toolkit included which any Android device can use.
FUNCTIONS OF UNIFIED ANDROID TOOLKIT V1.3.4 [9TH JAN 2015]
* Install correct adb/fastboot drivers automatically on Windows xp/vista/7/8 32bit+64bit
* Backup/Restore a single package or all apps, user data and Internal Storage
* Backup your data from selectable folders [internal or external storage] to your PC for a Full Safe backup of data
* Unlock/Re-Lock your Bootloader [Nexus]
* Root Stock builds
* Various Root options using insecure boot image or custom recovery
* ALLINONE to Unlock, Root, Rename the Restore Files and install busybox [Nexus]
* ALLINONE to flash custom Recovery Root, Rename the Restore Files and install busybox [Samsung]
* Install BusyBox on your device
* Perform a FULL NANDROID Backup of your system (Boot, Cache, Data, Recovery and System) via adb and save in Custom Recovery format on your PC which can be Restored via CWM Recovery [if insecure boot image available]
* Fix extSdCard write permissions from installed apps in Android 4.4+ [Samsung]
* Pull /data and /system folders, compress to a .tar file and save to your PC [if insecure boot image available]
* Dump selected Device Partitions, compress to a .zip file with md5 and save to your PC [if insecure boot image available]
* Extras, Tips and Tricks section
* Auto Update ToolKit to latest available version at startup (professional only feature)
* Program up to 10 Quickpick slots and run them very quickly (professional only feature)
* Mods section to automatically perform certain tasks on your device
* Download Google Stock Image directly to correct ToolKit folder for extracting and flashing [Nexus]
* Check md5 of stock image to make sure downloaded file isn't corrupted before flashing [Nexus]
* Download Samsung Stock Firmware to PC for extracting and flashing via Odin [Samsung]
* Flash Custom Recovery or Google Stock Image to Device
* Rename the Recovery Restore File present on some Stock Roms
* Boot into CWM Touch, TWRP, Philz Touch Recovery or Stock Recovery without Flashing it [Nexus]
* Flash Custom Recovery to Device
* Boot [Nexus] or Flash .img Files directly from your PC
* Install a single apk or multiple apk's to your device
* Push Files from your PC to your device
* Pull Files from your device to your PC
* Disable forced encryption on Nexus6 and Nexus9 devices
* Install Root Checker app by Burrows Apps
* Install Backup/Restore app by MDroid Apps [calls log, sms, contacts]
* Install EFS/Partition Backup/Restore app by Wanam
* Dump selected LogCat buffers to your PC
* Dump BugReport to your PC
* Set Files Permissions on your device
* Open new Command Prompt for manual input
* Reboot device to Fastboot Mode or Android from fastboot mode [Nexus]
* Reboot device to Fastboot Mode [Nexus], Recovery, Android or Download Mode [Samsung] from adb mode
* Display Important Information about your device
--------------------------------------------------------------
DOWNLOAD THE SKIPSOFT UNIFIED ANDROID TOOLKIT *HERE* (FROM SKIPSOFT.NET)
NOTE: As the exe files are not Digitally Signed with a Microsoft Certificate they 'may' get picked up as potentially harmful by Antivirus Programs and deleted on first run. If this happens restore the file and exclude it from future scans to use it. This seems to happen mostly on AVG Free and Norton which is why I switched to BitDefender which is much better.
Credits: ChainsDD for Superuser, Chainfire for SuperSU, koush and the clockworkmod team for cwm and the universal driver pack, 1wayjonny for the adb/fastboot driver pack, Adam Lange for all his support and help with the insecure kernels.
--------------------------------------------------------------
WHAT IS THE DIFFERENCE BETWEEN PUBLIC (FREE) AND PROFESSIONAL (DONATE) VERSIONS?
THE PUBLIC VERSION OF THE TOOLKIT INCLUDES EVERYTHING YOU COULD NEED TO MANIPULATE YOUR DEVICE. NOTHING IS RESTRICTED.
ACTIVATING THE PROFESSIONAL VERSION ADDS THE MOST USEFUL FUNCTION IN THE TOOLKIT, THE ABILITY TO CHECK FOR 'AUTO UPDATES' DIRECTLY VIA THE TOOLKIT AND HAVE THEM PUSHED TO YOUR PC RIGHT AWAY AS SOON AS THEY ARE UPLOADED WITHOUT NEEDING TO DOWNLOAD THE WHOLE TOOLKIT EVERY TIME. YOU WILL ALWAYS HAVE THE LATEST VERSION AS SOON AS IT IS MADE AVAILABLE. THIS MEANS SMALLER UPDATES CAN BE SENT OUT MORE FREQUENTLY, SUCH AS ADDING A SINGLE FUNCTION, FIXING A BUG OR ADDING COMPATIBILITY FOR A SINGLE CARRIER. THE SMALLER UPDATES WILL BE COMPILED AND RELEASED TO THE XDA COMMUNITY AS A FULL (PUBLIC) DOWNLOAD VERSION SO PROFESSIONAL VERSIONS ARE ALWAYS UPDATED SOONER.
THE PRO VERSION ALSO ADDS THE ABILITY TO CHECK FOR THE LATEST VERSION OF SUPERUSER AND RECOVERY FILES AND DOWNLOAD THEM DIRECTLY TO THE TOOLKIT.
THE 'QUICK PICKS' SECTION[/B] ALLOWS YOU TO PROGRAM UPTO 10 SLOTS WITH TASKS THAT YOU MAY PERFORM ON A REGULAR BASIS OR JUST WANT TO KEEP A SET OF TASKS IN 1 PLACE. THEN JUST SELECT THE SLOT AND IT WILL REMEMBER ALL YOUR SETTINGS FOR THAT TASK AND RUN IT.
PRO USERS CAN ALSO SELECT THE "ANY BUILD" OPTION IN THE BUILD SELECTION SCREEN TO ROOT ANY BUILD (USEFUL IF YOUR BUILD IS NOT LISTED).
AUTO REPLY LINKS FOR PAYPAL TO GET A CODE INSTANTLY CAN BE FOUND AT http://goo.gl/nyGqv
--------------------------------------------------------------
PLEASE READ THE *HELP* PAGE AT http://www.skipsoft.net/?page_id=1269 OR USE THE INFORMATION SECTION WITHIN THE TOOLKIT IF YOU HAVE ANY QUESTIONS. I HAVE TAKEN A LOT OF TIME TO WRITE IT AND SOMETHING ON THERE SHOULD ANSWER 99% OF PROBLEMS.
--------------------------------------------------------------
1. INSTALLING ADB/FASTBOOT DRIVERS
The first thing you need to do is to install the adb/fastboot drivers. These are needed so that you can unlock your bootloader, root your device and perform other adb/fastboot functions.
THE DRIVERS CAN BE INSTALLED DIRECTLY VIA THE TOOLKIT. OPTION 1 IN THE MAIN MENU.
If drivers are not installed or there is an exclamation mark next to the device:
Plug the device in to a usb cable directly connected to your motherboard.
In the Device Manager a new item, usually called Android 1.0 should pop up in the list.
Right click on the device item then left click on Update Driver Software. Select 'browse my computer' and then 'Let me pick from a list'.
If no adb interface driver appears in the list then untick 'Show compatible hardware' and find the Android or Samsung adb interface driver.
If you cannot find either of these click Have Disk, browse to the Toolkit install folder, drivers folder, click on android_winusb.inf and click Open.
Click OK and select Google ADB Interface.
Make sure you have USB debugging enabled in settings, developer options. In Android 4.2.2 or later you have to enable the developer options screen by going to settings, About on your device and click on Build number at the bottom 7 times until it says You are now a developer. If you have already enabled usb debugging then unplug/replug the usb cable.
On Android 4.2.2 or later when you replug the usb cable after enabling usb debugging for the first time you will get a popup asking you to authenticate your pc. Tick 'Always allow' then click 'ok'.
--------------------------------------------------------------
2. USING SKIPSOFT UNIFIED ANDROID TOOLKIT
When starting the Toolkit you will first be asked which device you want to work with. Working folders will be created and the device files downloaded. You will then be taken to the Model/Build selection screen where you can do a number of things (other than select your model/build): Type '00' to enter your activation code and enable pro features, 'i' will take you to the Information and Help Section, 'a' will give you information on how to add support for a new build.
Supported builds are listed in the Model/Build selection screen and typing the associated number (i.e. 11) will download needed boot and recovery files (stock and custom recovery) then check for and download the latest superuser files available and custom recovery (pro versions only), verify all the files and start the Main Menu. You can now use all the functions and tools the Android Toolkit offers. Pro users can select the "any build" option to root any build (useful if your build is not listed).
--------------------------------------------------------------
USEFUL INFORMATION
How to Hard Reboot the device
1. Unplug the USB cable.
2. Hold down the 'VOLUME DOWN' + 'POWER' buttons for about 5-15 seconds until the device reboots
How to get into Recovery Mode
1. Unplug the USB cable.
2. Hold down the 'VOLUME UP' + 'POWER' buttons for about 5-15 seconds until you see the Samsung logo on the screen.
3. Release all buttons straight away to enter Recovery Mode.
How to get into Download Mode (For Odin)
1. Unplug the USB cable.
2. Hold down the 'HOME' + 'VOLUME DOWN' + 'POWER' buttons for about 2-15 seconds until a WARNING! Screen appears.
3. Press the 'VOLUME UP' button to enter Download Mode.
--------------------------------------------------------------
*DISCLAIMER*
I take no responsibility for any fault or damage caused by using the Unified Android Toolkit. No warranties of any kind are given.
**UPDATES**
**VIDEOS**
**FAQ**
Q. Help me I can't find my build in the Model Selection Screen
The Toolkit includes a selection of Insecure Boot Images to cover all the different builds available. As there are very many different builds it is impossible to include an image for every single build but some builds share the same Boot Image. If you have a build that isnt listed on the Model Selection Screen you can therefore use a similar build. The best way to go is up to the next available build as it should offer more compatibility with the build you are using but if that isn't available then try the next build below your one as it should still be almost identical as long as it is the same version (ie. 4.1.1).
The Model Selection Screen is there so that if a task in the ToolKit requires an insecure kernel [to perform adb root commands] and your phone doesnt already include one, a compatible boot image [with an insecure kernel included] can be flashed to provide adb root access.
If you have a Custom Rom flashed to your phone then it will most probably have an insecure kernel included so it doesn't really matter if your build is not listed on the Model Selection Screen and when asked [by certain functions] if you have an insecure kernel on your phone you can answer 'yes'. However if the function fails then your kernel may not be insecure in which case you can flash one from the ToolKit. If you need to do this make sure the right build [or closest available build] is set so you flash the right image for your phone.
----------------------------------------------------------------------------
Q. What is ADB Shell?
Adb shell is a linux command line tool (because android is based on linux) used to send commands to your android device. For S-ON devices, this is crucial for modifying files in the /system partition (where the rom sits) as you cannot modify anything in /system when the rom is running without S-OFF like removing system apps.
----------------------------------------------------------------------------
Q. Why do I need to back up my IMEI/EFS and how do I do it?
There well protected section of your device that is virtually immune to any kind of flashing and manipulation (unless of course you know how to access it). This part of the device contains information such as IMEI (or MEID and ESN in the case of CDMA devices), programming parameters for the device such as your account information (phone number, etc), data provisioning parameters, and a whole bunch of other things that, when not handled properly, can render a device completely useless. All of these are contained in the infamous \EFS folder. If anything messes with your EFS folder, unlike flashing a device (which could potentially lead to bricks as well) it could render your device completely useless as it will no longer be recognized by your carrier. If you are not planning on flashing anything to your device and want to stay on pure Stock then you may never have any problems but it is still advisable to backup this information just in case (better to be safe than sorry).
----------------------------------------------------------------------------
Q. Does flashing a custom image increase my flash counter?
Any image that is flashed via Odin that has been modified will increase the flash counter that can be viewed in the Download Mode on your device (if booted by holding the Volume Down, Home and Power buttons). You can reset the flash counter using an app by Chainfire called Triangles Away and can find instructions on how to use that in the Downloads section in the Toolkit.
----------------------------------------------------------------------------
Q. Will flashing Stock ROM via odin using the toolkit replace everything that was flashed before? recovery? etc?
Yes a Stock Image flashed via Odin will replace all your key partitions (boot, recovery, system) with the stock firmware. If you want to reset the phone back to an 'out of the box' state then you want to enter recovery and do a wipe first which will reformat your userdata partition.
----------------------------------------------------------------------------
Q. I flashed Custom Recovery but each time I reboot the Stock Recovery is back
There is an auto recovery restore system on certain Stock Android Builds that will reflash the Stock Recovery if you flash CWM on a Stock Rom.
Use Root Explorer to Mount the system folder as R/W (or use a free app from Google Play such as ES File Explorer). Rename the files /system/recovery-from-boot.p and /system/etc/install-recovery.sh (requires root). Now when you flash Custom Recovery it will NOT be overwritten after a reboot. You can also do this via the Toolkit.
----------------------------------------------------------------------------
Q. My AntiVirus program says the Toolkit files may be harmful
The exe compiled files are not digitally signed with a Microsoft certificate (as they cost money) so certain AntiVirus programs (mainly Norton and AVG Free) may pick it up as potentially harmful when it is not. They will pick up ANY file that doesn't contain a purchased Microsoft certificate in the same way. Just Restore the deleted file and exclude it from further scans and it will be fine. Or switch to a better AntiVirus program such as BitDefender.
----------------------------------------------------------------------------
Q. I flashed the Toolkit Boot Image, now my wifi + bluetooth won't work
The boot images are made from Stock with only needed changes made to the insecure boot images [modified adbd, default.prop and rc.local edited] and will work on all stock roms. If you flash them to a custom rom and the rom has been altered or uses a custom boot image then it will boot but certain modules may not load such as wifi or bluetooth. In this case you can use the boot image to root or perform adb root functions but will need to flash back the boot image for the custom rom to get other functions working again. This is not a fault of the Toolkit but a difference to stock in the custom rom.
----------------------------------------------------------------------------
Q. I am having trouble getting adb working with the drivers installed
Try switching your connection type from media (MTP) mode to camera mode (P2P). To do this open the notification area, click where it says connected as and change from MTP to PTP.
----------------------------------------------------------------------------
Q. I want to send my device back for warranty purposes
1. Follow the instructions to reset your flash counter with TriangleAway.
2. Download and flash a Stock Firmware image from the download section.
3. Boot into Stock Recovery and perform a wipe/factory reset
.
Your internal storage will be formatted and data and cache wiped. Your device should now be back to an out-of-the-box FULLY STOCK state with the flash counter [shown if you boot to download mode manually] reset and ready to send back.
----------------------------------------------------------------------------
Q. When connecting the phone I get 'USB Device not Recognized' and no serial number shows in the ToolKit
I actually had this problem recently and what fixed it for me was to make sure that the drivers have been installed, then shut my phone down plug the usb cable in and restart it. The phone booted up and the device was recognized and drivers installed correctly. May not work for everyone but worth trying.
----------------------------------------------------------------------------
Q. "Superuser/SuperSU has stopped" message after rooting
After updating Samsung device to newer builds of Android [4.3 and later] which contains the new security from Samsung "Samaung KNOX", you might face a problem if you tried to root your device.
This might happen because of KNOX security, it blocks/disables the Superuser app and you will see this notification after the first boot:
"Unfortunately, SuperSU has stopped" or "Unfortunately, Superuser has stopped" depending on the root method you used.
The easiest way to fix this problem is by installing the superuser apk file. Select option 6 from the Rooting Section and the Toolkit will attempt to extract the superuser.apk file from the root zip file in the Root folder and if successful it will then be installed. You can then run the app [Superuser or SuperSU] from the apps list. A warning message will pop up saying Samsung KNOX has been detected and ask if you want to try and disable it. Click OK, KNOX should be disabled and your device should now be properly rooted.
Thanks for an excellent tool!
I'm having issues with my P600, and I'm pretty sure I've tried everything I can think of, but I'm also sure there is a strong possibility that I'm making a noob mistake. I haven't rooted anything since my Galaxy S3, so I'm incredibly rusty.
Here's what I've done:
32. Samsung Galaxy Note 10.1 (2014)
01. Wifi Only Model
12. 4.4.2
1. Install Device Drivers
This was done successfully with no issues reported by the toolkit.
After this, I know I selected option 3 and I know I installed TWRP 2.8.3.0 and SuperSU 2.45. When I first installed it, I got all successful messages, and I made sure to follow the directions precisely (always read first and then execute). Now my end game here is to install Lollipop on this puppy, which I really cannot wait for. I have three huge issues preventing me from doing that. First, when I launch SuperSU is says something about it cannot find the binary and it cannot install itself (I will update this with the exact message when I get home). The next problem is I attempted to fix that by reinstalling using the toolkit, and whenever my tablet restarts it hits that "android man laying on his back". Then, the third issue is my tablet keeps coming to a message screen saying something along the lines of "installing a custom rom is dangerous and can affect the installed applications" (again, I will update this with the exact message when I get home tonight).
Can anyone suggest a course of action to fix these issues? Even if it involves starting from scratch, I don't mind at all. I just want to be able to install Lollipop already, and I really do not know what I did wrong.
Thanks in advanced, XDA.
- Brandon
BBKoenigsegg said:
I'm having issues with my P600, and I'm pretty sure I've tried everything I can think of, but I'm also sure there is a strong possibility that I'm making a noob mistake. I haven't rooted anything since my Galaxy S3, so I'm incredibly rusty.
Here's what I've done:
32. Samsung Galaxy Note 10.1 (2014)
01. Wifi Only Model
12. 4.4.2
1. Install Device Drivers
This was done successfully with no issues reported by the toolkit.
After this, I know I selected option 3 and I know I installed TWRP 2.8.3.0 and SuperSU 2.45. When I first installed it, I got all successful messages, and I made sure to follow the directions precisely (always read first and then execute). Now my end game here is to install Lollipop on this puppy, which I really cannot wait for. I have three huge issues preventing me from doing that. First, when I launch SuperSU is says something about it cannot find the binary and it cannot install itself (I will update this with the exact message when I get home). The next problem is I attempted to fix that by reinstalling using the toolkit, and whenever my tablet restarts it hits that "android man laying on his back". Then, the third issue is my tablet keeps coming to a message screen saying something along the lines of "installing a custom rom is dangerous and can affect the installed applications" (again, I will update this with the exact message when I get home tonight).
Can anyone suggest a course of action to fix these issues? Even if it involves starting from scratch, I don't mind at all. I just want to be able to install Lollipop already, and I really do not know what I did wrong.
Thanks in advanced, XDA.
- Brandon
Click to expand...
Click to collapse
Which root option did you use to root the device? Using the push method is the simplest.
If the device is booting in the the Stock Recovery screen (Android man on his back) then it looks like the stock recovery restore files are present on your device. In this case choose options 7,3 from the main menu and follow the instructions to stop the stock recovery being restored after a reboot.
Mark.
Update
I have updated the module files (that are downloaded after the Note 10.1 2014 is selected at startup) to fix several config settings, update some Toolkit functions and update TWRP for all variants to 2.8.5.0. The unroot zip file has also been fixed/updated.
Supported models/builds list: http://www.skipsoft.net/?page_id=1203
Download from: http://www.skipsoft.net/?page_id=1069 if you don't already have the Toolkit
If you have already downloaded the new Toolkit and have the v1 module for the Note 10.1 2014 then delete the ConfigGalaxyNote101_2014.exe and the _currentrecoveryversionGalaxyNote101_2014.ini from the tools folder and the Unroot-UninstallBusybox-CwmManager.zip from the root folder. Download the new unroot zip file from http://skipsoft.net/download/fileupd...CwmManager.zip and move it to the root folder, start the Toolkit and select the Galaxy Note 10.1 2014 from the list. The Toolkit will then download new module files.
I will also push an AutoUpdate with the same updates/fixes for Pro users to automate the whole above procedure.
Note: Can someone let me know if the openrecoverscript method via twrp works with twrp 2.8.5.0. I know 2.8 has problems with adb and the openrecovery script method is heavily reliant on this. If it does not work I can revert the recovery back to 2.7.1.1 which has no problems with adb.
Mark.
mskip said:
Update
Supported models/builds list: http://www.skipsoft.net/?page_id=1203
Click to expand...
Click to collapse
This lists the P605, but doesn't state specific carriers. I believe the Verizon is P605V. I am aware the Bootloader is locked, but will it at least Root the P605V?
Any question: do you see any chance to insert a tool into the kit,for enabling otg usb ajd charge at the same time? On Note 3 snapdragon it works with a y adapter,but not on the P605.....
Gesendet von meinem SM-N9005 mit Tapatalk
I've finally decided to root my Note 10. Almost at the end I get this message, "Rebooting device to recovery mode, error: no device/emulators found". What am I doing wrong?
AutoUpdate Available for Samsung Galaxy Note 10.1 (2014) module (Ultimate/Pro Users)
CHANGELOG: [1.5.5]
+Updated FULL support for Android 5.1.1 for ALL models
+Added futureproof support with the new custom support loader option
+no-verity-opt-encrypt zip file [downloads to tools folder after device selection]
+Added latest Magisk zip file [downloads to root folder after device selection]
+Added NEW ULTIMATE FEATURE to add build support for any supported Toolkit device from download link, firmware or boot/recovery images. More Info at skipsoft.net
+Added completely new much improved detection routine for adb/recovery modes and integrated it in Toolkit procedures so automatic detection/rebooting works better|
+Updated Toolkit base for NEW Ultimate feature. Toolkit will update any device module to latest main module version even if an AutoUpdate is not ready yet
+Updated some root functions and removed SuperUser by CWM from root relection
+Added VerifiedBootSigner zip file to use in the Toolkit on newer builds if needed
+Integrated flashing verifiedbootsigner in to root procedures if ever needed
+Toolkit will disable all server pings if they cause any trouble with downloads
+Made some routines work better with more checks to make sure files exist
+Updated Drivers section with new options and adb check tool
+Updated Firmware section with better firmware support. Added Updato.com links
+Improved some Main Menu functions
+Updated app/file versions to latest
+Bug fixes and more I probably forgot to write down
If you find any of this useful PLEASE donate to a device project. You can do it through the Toolkit (after selecting the device at startup) or from the link at https://www.skipsoft.net/?page_id=703 so you get the right code fast and can update to the latest version. You can also go ULTIMATE mode and unlock ALL device modules for the lifetime of the Toolkit. Follow us on twitter at https://twitter.com/mskipxda for posts/updates.
Enjoy.
old thread but still, thanks!
mskip said:
AutoUpdate Available for Samsung Galaxy Note 10.1 (2014) module (Ultimate/Pro Users)
CHANGELOG: [1.5.5]
+Updated FULL support for Android 5.1.1 for ALL models
+Added futureproof support with the new custom support loader option
+no-verity-opt-encrypt zip file [downloads to tools folder after device selection]
+Added latest Magisk zip file [downloads to root folder after device selection]
+Added NEW ULTIMATE FEATURE to add build support for any supported Toolkit device from download link, firmware or boot/recovery images. More Info at skipsoft.net
+Added completely new much improved detection routine for adb/recovery modes and integrated it in Toolkit procedures so automatic detection/rebooting works better|
+Updated Toolkit base for NEW Ultimate feature. Toolkit will update any device module to latest main module version even if an AutoUpdate is not ready yet
+Updated some root functions and removed SuperUser by CWM from root relection
+Added VerifiedBootSigner zip file to use in the Toolkit on newer builds if needed
+Integrated flashing verifiedbootsigner in to root procedures if ever needed
+Toolkit will disable all server pings if they cause any trouble with downloads
+Made some routines work better with more checks to make sure files exist
+Updated Drivers section with new options and adb check tool
+Updated Firmware section with better firmware support. Added Updato.com links
+Improved some Main Menu functions
+Updated app/file versions to latest
+Bug fixes and more I probably forgot to write down
If you find any of this useful PLEASE donate to a device project. You can do it through the Toolkit (after selecting the device at startup) or from the link at https://www.skipsoft.net/?page_id=703 so you get the right code fast and can update to the latest version. You can also go ULTIMATE mode and unlock ALL device modules for the lifetime of the Toolkit. Follow us on twitter at https://twitter.com/mskipxda for posts/updates.
Enjoy.
Click to expand...
Click to collapse
no android 5 support for note 10.1 2014
will this allow you to dump a custom rom on the device? The last samsung I had was like a galaxy 2 or 3 and it was impossible then. I came accross a verizon 10.1 2014 from work and its a nice beater tablet but the UI just sucks compared to my nexus and pixel vanilla android devices.
Team Win Recovery Project, or twrp for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Version Information
Status: Unstable
Created: 2016-09-04
Last Updated: 2016-09-04
DOWNLOAD: https://mega.nz/#F!ZsxV0CrB!vsR6rdmZkpI9HShdPxybog
HOW TO USE (INSTALL FREE):
1. Rename the img file you uploaded to "recovery.img"
2. Put the file on USB stick
3. Put USB stick on the S905X device
4. Open recovery like you normally do
TESTED DEVICES:
Mini M8S II - Worked perfectly
IMPORTANT:
You have to use USB mouse to have input.
You can remove USB stick after opening TWRP.
VirusTotal:
twrp.s905x-3.0.2-0.img - https://www.virustotal.com/en/file/54f14e348747039ec63888f03f15bd8aa529cc92e413ac82f9fd3ee008ecd241/analysis/1472972666/
Is valid for Nexbox A95X 2Gb / 16Gb?
oskarbcn said:
Is valid for Nexbox A95X 2Gb / 16Gb?
Click to expand...
Click to collapse
Would like to know this also.
Invalid for M96X.
Caused me massive problem as there was no way for custom recovery to read onboard storage.
Had to dump original recovery from the depths of hell to restore it back to stock.
In case anyone's looking for it: stock recovery image for M96X S905X 2gb RAM, 8GB ROM
flash with RASHR app (through android)
seven2099 said:
Invalid for M96X.
Caused me massive problem as there was no way for custom recovery to read onboard storage.
Had to dump original recovery from the depths of hell to restore it back to stock.
In case anyone's looking for it: stock recovery image for M96X S905X 2gb RAM, 8GB ROM
flash with RASHR app (through android)
Click to expand...
Click to collapse
I have an m96x and t95x pro. I am basically just trying to figure out a way to make a nandroid backup and a restore method. Does these two devices simply have no compatible custom recovery to make a nandroid backup and restore?
ftateen said:
I have an m96x and t95x pro. I am basically just trying to figure out a way to make a nandroid backup and a restore method. Does these two devices simply have no compatible custom recovery to make a nandroid backup and restore?
Click to expand...
Click to collapse
No one has made a compatible custom recovery for the M96X.
However restoring is easy as pie if you have the right firmware. I have it backed up and am about to restore a bricked box.
seven2099 said:
No one has made a compatible custom recovery for the M96X.
However restoring is easy as pie if you have the right firmware. I have it backed up and am about to restore a bricked box.
Click to expand...
Click to collapse
may i have a copy? cant find the firmware anywhere....
redgrass83 said:
may i have a copy? cant find the firmware anywhere....
Click to expand...
Click to collapse
edit
please ? I have two of these wedge bricks
Could I request a version compiled with TW_THEME := landscape_hdpi? I have trouble reading the terminal text when it's so pixelated.
seven2099 said:
No one has made a compatible custom recovery for the M96X.
However restoring is easy as pie if you have the right firmware. I have it backed up and am about to restore a bricked box.
Click to expand...
Click to collapse
Steve please help me. i came across your post on google. i bricked my m96x by editing build.prop and now its stuck on startup screen where it says box something . i downloaded all your 3 files you provided but did not understand how to flash it.
can you please explain why there is 3 img zips instead of just 1 . also can you tell me how to flash and fix my m96x box.
thank you
Installed in Zenopllige Z11 PRO, it works. I flashed it with the video application https://www.youtube.com/watch?v=UZMS8qYs2tQ
Unable to Restore TWRP Backup on Mini M8S II
Hi,
Bought this Box few days ago and now found several issues, one that bothered me the most was the dark screen (have read several forums where people complained about this issue). There are no options to increase or decrease the brightness. Anways I wanted to flash another firmware/update to see if the issue will resolve so I made a TWRP Backup using the UNOFFICIAL TWRP 3.0.2-0 Recovery Image for S905X which went smoothly but now I am trying to restore the device and all I get is errors every time I try.
TWRP Restore Error:
Error during restore process.
extractTarFork () process ended with ERROR: 255
Pls can someone help me to restore the TWRP backup on this crappy Box.
Thanks
Can I use it for a M9C Pro Smart Amlogic S905X TV Box? Thanks
Someone tried this on M96X-II? It seems to be M96X with 16 GB NAND memory chip.
robinkooli said:
Team Win Recovery Project, or twrp for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Version Information
Status: Unstable
Created: 2016-09-04
Last Updated: 2016-09-04
DOWNLOAD: https://mega.nz/#F!ZsxV0CrB!vsR6rdmZkpI9HShdPxybog
HOW TO USE (INSTALL FREE):
1. Rename the img file you uploaded to "recovery.img"
2. Put the file on USB stick
3. Put USB stick on the S905X device
4. Open recovery like you normally do
TESTED DEVICES:
Mini M8S II - Worked perfectly
IMPORTANT:
You have to use USB mouse to have input.
You can remove USB stick after opening TWRP.
Click to expand...
Click to collapse
Why you ppl posting link then deleting file!!!! I have mine threads they are 15 years old and links are still live...You guys just waste forum space
Hi everyone, I recently bought a Xiaomi Mi box3c and was very disappointed with custom rom and the interface that it came with on it. So surfing the web there are a few tutorials on how to change it and I tried a few but they are not that great either, till finally someone patched the stock android TV Lean back Launcher for it, it took some tinkering but I got it working, this may not be the best way but this is how I did it form the start. This is not my work, I just followed instructions and I have gathered them here. As I am lazy Im not gonna provide pictures for every step but it’s pretty straight forward.
For using some the apps during the process you will need usb mouse cause not every apps supports Mibox remote configuration
As I am a new poster I am not allowed to post any links so change every dot word to an actual . for the links.
1. Turning on the Box and Changing to English
1.1 Download this apk provided by Xiaomi veterans on forum, it’s a shortcut to the stock android setting
drive dot google dot com/open?id=0B16bkj0QSkYnc0k2UUFTU05vSHM 1.2 copy the apk to a normal usb flash drive and connect to mibox and install the apk
1.3 Run it and now you can change the language as in any android device.
2. Downgrading Firmware
All of the root options available for this device are for the older firmware so you need to downgrade the device. (it’s much easier than it sounds.)
2.1 Download the original firmware for MDZ-16-AA from this link: (both are the same thing)
yadi dot sk/d/Yvr1jYflm6GZR androidfilehost dot com/?fid=745425885120695554 2.2 Extract the contents of the downloaded zip file to a formatted usb tick (Fat32). (There should be two files: xiaomi_update and update.zip)
2.3 Put the USB flash drive in your Mi Box and boot in recovery
(How to boot into recovery: Unplug power > press and "hold back + ok" button while plugging the power back in. The remote should be nearby and facing the box. Do not let go of the buttons until it booted in recovery. for some devices its "home + menu" button instead of the previous one.
2.4 the flashing should start and finish automatically. don’t connect the device to WIFI after this step until you have disabled the intelligent update.
(Credits to passerby on xiaomi.eu forums for the guide)
3. Rooting the device
I tried almost all of the rooting apps, none of them worked for me but I have seen people insisting that permroot works for them so I put the link for that, using it is pretty straight forward, download, install on device and try to root with it.
but in case that doesn’t work Kingoroot Windows app will definitely work. this is how to root with kingoroot. For this method you need a USB type A --> USB type A cable.
3.1 First download the kingoroot desktop app from their website
3.2 Install the app on your windows desktop
3.3 Go to your mibox device setting (mibox setting not android stock from part 1) and in Security setting and Enable USB/ADB debugging, device will restart for this setting to change.
3.4 connect your mibox to your desktop and wait for the device to be installed and recognized by windows. (If you are using windows 10 it will detect the device by itself)
3.5 Run the kingoroot app on the windows and let it detect the device, as soon as it detects the device root option will appear, click on root option it and wait
3.6 Kingoroot will try to install an app on your mibox, allow it and then this will continue and finish the rooting process.
3.7 Disable USB/ADB debugging, so you can connect USB Flash drives to the device again.
3.8 Check for the root stastus with rootchecker.
(Credits to passerby on xiaomi.eu forums for the guide)
4. How to flash TWRP to device
4.1 download the TWRP App from this link:
dl dot twrp dot me/twrpapp/me.twrp.twrpapp-18.apk 4.2 Download the android ROM and TWRP image together from this link:
goo dot gl/q5DGED password : Mibox2015 4.3 open the zip file and copy this image file to your USB Flash drive
MDZ-16-AA-AndroidTV-V1\TWRP-RECOVERY\twrp-mdz-16-aa.img
4.4 Connect the USB flash drive to the box and copy the image to device storage
4.3 Install the TWRP app on the device using the USB flash drive
4.4 Run it and select first two boxes.
4.5 Go to flash TWRP option and wait for app to ask permission from SU, grant permission.
4.6 Select TWRP flash and select flash from image. Select the image that you copied to device storage.
4.7 Boot into recovery (by this time you have root access and it’s better to boot to recovery with one of the reboot apps ex. Quick Reboot)
(Now you have TWRP, but the problem is every time you reboot the box, the stock rom overwrites the TWRP files and it goes back to Default recovery, to solve this we need to replace the Rom itself too)
5. Replacing the Rom
5.1 While still in TWRP page, make a small boot backup just so TWRP makes a folder in storage of your device.
5.2 Reboot the device from TWRP (reboot system)
5.3 Now using a File manager (I used X-plore) copy the Rom folder to the same backup folder that was created by TWRP in your storage.
Copy This folder:
MDZ-16-AA-AndroidTV-V1\TWRP\BACKUPS\11608V180037788\2014-12-31--18-01-42_6.9.7.949
To this folder: (Which is already should be there created by TWRP)
Internal Storage\TWRP\Backups\ (your device’s Serial number)\
5.4 Repeat steps 4.6 & 4.7 again to Flash TWRP again, after booting to TWRP go to restore and select file (2014-12-31--18-01-) to restore, swipe to restore and wait for 10-15 minutes
5.5 After restore is done don’t reboot, go back to TWRP main page, go to Wipe then advanced wipe, select Dalvik, Cache and Data to be wiped. After wipe is done reboot system
5.6 When android system boot is complete, go to setting down below and change the language to English and its done.
I hope it helps
Someone posted a tutorial on YouTube, the title of video is "MIBOX 3 MDZ-16-aa ROOT + Install Android TV English".
@[email protected], did you get Netflix to work on it?
dummyaccount said:
Someone posted a tutorial on YouTube, the title of video is "MIBOX 3 MDZ-16-aa ROOT + Install Android TV English".
@[email protected], did you get Netflix to work on it?
Click to expand...
Click to collapse
I tried all the steps.
No google play videos, no voice search and most of all no netflix.
=(
I hate the ****ing Chinese that sold me MDZ-16-aa saying it was the international version.
dont work password androidtv rom....... is Mibox2015?
mdz 16-AA
I faced the same issue.Wrong password.
Thanx for your post [email protected] I am going to use this method for my Mi box3.
As I am going to root any device for the first time, what precautions should I take
that I don't brick it?
Does the Microphone and and Ok button on Remote work normally after rooting by your method ?
Thx in advance....
[email protected] said:
Hi everyone, I recently bought a Xiaomi Mi box3c and was very disappointed with custom rom and the interface that it came with on it. So surfing the web there are a few tutorials on how to change it and I tried a few but they are not that great either, till finally someone patched the stock android TV Lean back Launcher for it, it took some tinkering but I got it working, this may not be the best way but this is how I did it form the start. This is not my work, I just followed instructions and I have gathered them here. As I am lazy Im not gonna provide pictures for every step but it’s pretty straight forward.
For using some the apps during the process you will need usb mouse cause not every apps supports Mibox remote configuration
As I am a new poster I am not allowed to post any links so change every dot word to an actual . for the links.
1. Turning on the Box and Changing to English
1.1 Download this apk provided by Xiaomi veterans on forum, it’s a shortcut to the stock android setting
drive dot google dot com/open?id=0B16bkj0QSkYnc0k2UUFTU05vSHM 1.2 copy the apk to a normal usb flash drive and connect to mibox and install the apk
1.3 Run it and now you can change the language as in any android device.
2. Downgrading Firmware
All of the root options available for this device are for the older firmware so you need to downgrade the device. (it’s much easier than it sounds.)
2.1 Download the original firmware for MDZ-16-AA from this link: (both are the same thing)
yadi dot sk/d/Yvr1jYflm6GZR androidfilehost dot com/?fid=745425885120695554 2.2 Extract the contents of the downloaded zip file to a formatted usb tick (Fat32). (There should be two files: xiaomi_update and update.zip)
2.3 Put the USB flash drive in your Mi Box and boot in recovery
(How to boot into recovery: Unplug power > press and "hold back + ok" button while plugging the power back in. The remote should be nearby and facing the box. Do not let go of the buttons until it booted in recovery. for some devices its "home + menu" button instead of the previous one.
2.4 the flashing should start and finish automatically. don’t connect the device to WIFI after this step until you have disabled the intelligent update.
(Credits to passerby on xiaomi.eu forums for the guide)
3. Rooting the device
I tried almost all of the rooting apps, none of them worked for me but I have seen people insisting that permroot works for them so I put the link for that, using it is pretty straight forward, download, install on device and try to root with it.
but in case that doesn’t work Kingoroot Windows app will definitely work. this is how to root with kingoroot. For this method you need a USB type A --> USB type A cable.
3.1 First download the kingoroot desktop app from their website
3.2 Install the app on your windows desktop
3.3 Go to your mibox device setting (mibox setting not android stock from part 1) and in Security setting and Enable USB/ADB debugging, device will restart for this setting to change.
3.4 connect your mibox to your desktop and wait for the device to be installed and recognized by windows. (If you are using windows 10 it will detect the device by itself)
3.5 Run the kingoroot app on the windows and let it detect the device, as soon as it detects the device root option will appear, click on root option it and wait
3.6 Kingoroot will try to install an app on your mibox, allow it and then this will continue and finish the rooting process.
3.7 Disable USB/ADB debugging, so you can connect USB Flash drives to the device again.
3.8 Check for the root stastus with rootchecker.
(Credits to passerby on xiaomi.eu forums for the guide)
4. How to flash TWRP to device
4.1 download the TWRP App from this link:
dl dot twrp dot me/twrpapp/me.twrp.twrpapp-18.apk 4.2 Download the android ROM and TWRP image together from this link:
goo dot gl/q5DGED password : Mibox2015 4.3 open the zip file and copy this image file to your USB Flash drive
MDZ-16-AA-AndroidTV-V1\TWRP-RECOVERY\twrp-mdz-16-aa.img
4.4 Connect the USB flash drive to the box and copy the image to device storage
4.3 Install the TWRP app on the device using the USB flash drive
4.4 Run it and select first two boxes.
4.5 Go to flash TWRP option and wait for app to ask permission from SU, grant permission.
4.6 Select TWRP flash and select flash from image. Select the image that you copied to device storage.
4.7 Boot into recovery (by this time you have root access and it’s better to boot to recovery with one of the reboot apps ex. Quick Reboot)
(Now you have TWRP, but the problem is every time you reboot the box, the stock rom overwrites the TWRP files and it goes back to Default recovery, to solve this we need to replace the Rom itself too)
5. Replacing the Rom
5.1 While still in TWRP page, make a small boot backup just so TWRP makes a folder in storage of your device.
5.2 Reboot the device from TWRP (reboot system)
5.3 Now using a File manager (I used X-plore) copy the Rom folder to the same backup folder that was created by TWRP in your storage.
Copy This folder:
MDZ-16-AA-AndroidTV-V1\TWRP\BACKUPS\11608V180037788\2014-12-31--18-01-42_6.9.7.949
To this folder: (Which is already should be there created by TWRP)
Internal Storage\TWRP\Backups\ (your device’s Serial number)\
5.4 Repeat steps 4.6 & 4.7 again to Flash TWRP again, after booting to TWRP go to restore and select file (2014-12-31--18-01-) to restore, swipe to restore and wait for 10-15 minutes
5.5 After restore is done don’t reboot, go back to TWRP main page, go to Wipe then advanced wipe, select Dalvik, Cache and Data to be wiped. After wipe is done reboot system
5.6 When android system boot is complete, go to setting down below and change the language to English and its done.
I hope it helps
Click to expand...
Click to collapse
I tried to downgrade my MDZ-16-AA device with the MiBOX3_jurassicpark_gitv_1.3.106.386 file ... but it brings it down only to 1. 3. 114 and not to 1. 3. 106.
Secondly I do not get "ADB Debugging" option. Hence I cannot connect my Mi Box to my laptop.
Can anyone help ?
the correct password is : '@'mibox2015
the quotes are only to avoid mention to xda user "mibo" in xda forum...u don't have to write it in...
mibox v1.5.1
I've troubles to root my mibox, I've the 1.5.1 version.
Can you help me, please ?
Mi box 3C v 1.5.1
Can it possible to do the same for version 1.5.1?
I have Mi box 3C v 1.5.1 and I can't even boot into recovery yet.
Add widevine drm in MDZ-16-AA
To complete your notice, I found a way to launch MyCanal and molotov.tv (not tested for netflix yet).
As you know these apps requires widevine drm.
First download
extractor 4.0 and Xiomi 3S official rom
Then extract update.zip and add in root folder of extractor: system.new.dat + system.transfert.list.file_context
Use Extractor.bat to uncompact system.new
On folder go on system\vendor and copy paste lib folder on USB key.
Does anybody know how to go to recovery mode?
HOLD Back + OK and Home + Option doesn't work for my MDZ-16-AA
the system has been automatically updated yesterday.. :crying:
Thank you so much, I got it installed.
Step 1 can be hard because of the chinese language therefor I used this link:
https://www dot cnx-software dot com/2016/04/12/how-to-change-language-to-english-and-install-apps-remotely-on-xiaomi-mi-box-3-enhanced/
at step 2 I made the mistake that I extracted the update.zip aswell. while I needed to keep it zipped.
I used the app RUFUS to make the usbdrive a FAT32 drive.
at step 3 Kingoroot worked for me, although I needed to restart several times to make the ADB debugging connection work.
at step 4 sending the TWRP files, was a bit of a hurdle. It wwas not possible for me to copt them from the USB stick with ES file manager to the device. I needed to use the USB cable to my computer (ADB off) password: "@mibox2015"
At point 5 I was not able to use my remote or keyboard, I needed to turn off ADB!
At the end allot works, but there is still some bugs:
- MIUI still present. eg. when connecting an usb stick you get a chinese menu. and you are able to get into the old system menu
- unable to get NETFLIX to work
- allot of bloatware, apps I can not disable or delete.
- im unable to disable search by microphone in the UI, which is not supported by the remote of the 16-AA
- im unable to edit the tiles in the homescreen to eg. hide the supersu, market etc. and to put PLEX of KODI more in front
Thanks!!!!
I have rooted my mibox 3c and installed TWRP app
I copied img to device and flash drive, but I can't choose any img in TWRP app...
any method to replace custom recovery?? THX
weiabroad said:
I have rooted my mibox 3c and installed TWRP app
I copied img to device and flash drive, but I can't choose any img in TWRP app...
any method to replace custom recovery?? THX
Click to expand...
Click to collapse
Go through each step carefully, if stuck be clear about what you have done
Sent from my A0001 using Tapatalk
Arquivo converter ROM chinesa para global 3C-16AA
Olá, gostaria dos arquivos para converter a ROM 3C-16AA, você tem whats para contato?
Hey,
Im' trying to get mycanal to work on my mibox MDZ-16-AA.
I copied the lib folder on my usb stick.
it's still not working, isn't any steps missing ?
Thanks.
Secure Check failed error while downgrading
I Got "secure check failed." error while downgrading. What did i do wrong ?
[email protected] said:
Hi everyone, I recently bought a Xiaomi Mi box3c and was very disappointed with custom rom and the interface that it came with on it. So surfing the web there are a few tutorials on how to change it and I tried a few but they are not that great either, till finally someone patched the stock android TV Lean back Launcher for it, it took some tinkering but I got it working, this may not be the best way but this is how I did it form the start. This is not my work, I just followed instructions and I have gathered them here. As I am lazy Im not gonna provide pictures for every step but it’s pretty straight forward.
For using some the apps during the process you will need usb mouse cause not every apps supports Mibox remote configuration
As I am a new poster I am not allowed to post any links so change every dot word to an actual . for the links.
1. Turning on the Box and Changing to English
1.1 Download this apk provided by Xiaomi veterans on forum, it’s a shortcut to the stock android setting
drive dot google dot com/open?id=0B16bkj0QSkYnc0k2UUFTU05vSHM 1.2 copy the apk to a normal usb flash drive and connect to mibox and install the apk
1.3 Run it and now you can change the language as in any android device.
2. Downgrading Firmware
All of the root options available for this device are for the older firmware so you need to downgrade the device. (it’s much easier than it sounds.)
2.1 Download the original firmware for MDZ-16-AA from this link: (both are the same thing)
yadi dot sk/d/Yvr1jYflm6GZR androidfilehost dot com/?fid=745425885120695554 2.2 Extract the contents of the downloaded zip file to a formatted usb tick (Fat32). (There should be two files: xiaomi_update and update.zip)
2.3 Put the USB flash drive in your Mi Box and boot in recovery
(How to boot into recovery: Unplug power > press and "hold back + ok" button while plugging the power back in. The remote should be nearby and facing the box. Do not let go of the buttons until it booted in recovery. for some devices its "home + menu" button instead of the previous one.
2.4 the flashing should start and finish automatically. don’t connect the device to WIFI after this step until you have disabled the intelligent update.
(Credits to passerby on xiaomi.eu forums for the guide)
3. Rooting the device
I tried almost all of the rooting apps, none of them worked for me but I have seen people insisting that permroot works for them so I put the link for that, using it is pretty straight forward, download, install on device and try to root with it.
but in case that doesn’t work Kingoroot Windows app will definitely work. this is how to root with kingoroot. For this method you need a USB type A --> USB type A cable.
3.1 First download the kingoroot desktop app from their website
3.2 Install the app on your windows desktop
3.3 Go to your mibox device setting (mibox setting not android stock from part 1) and in Security setting and Enable USB/ADB debugging, device will restart for this setting to change.
3.4 connect your mibox to your desktop and wait for the device to be installed and recognized by windows. (If you are using windows 10 it will detect the device by itself)
3.5 Run the kingoroot app on the windows and let it detect the device, as soon as it detects the device root option will appear, click on root option it and wait
3.6 Kingoroot will try to install an app on your mibox, allow it and then this will continue and finish the rooting process.
3.7 Disable USB/ADB debugging, so you can connect USB Flash drives to the device again.
3.8 Check for the root stastus with rootchecker.
(Credits to passerby on xiaomi.eu forums for the guide)
4. How to flash TWRP to device
4.1 download the TWRP App from this link:
dl dot twrp dot me/twrpapp/me.twrp.twrpapp-18.apk 4.2 Download the android ROM and TWRP image together from this link:
goo dot gl/q5DGED password : Mibox2015 4.3 open the zip file and copy this image file to your USB Flash drive
MDZ-16-AA-AndroidTV-V1\TWRP-RECOVERY\twrp-mdz-16-aa.img
4.4 Connect the USB flash drive to the box and copy the image to device storage
4.3 Install the TWRP app on the device using the USB flash drive
4.4 Run it and select first two boxes.
4.5 Go to flash TWRP option and wait for app to ask permission from SU, grant permission.
4.6 Select TWRP flash and select flash from image. Select the image that you copied to device storage.
4.7 Boot into recovery (by this time you have root access and it’s better to boot to recovery with one of the reboot apps ex. Quick Reboot)
(Now you have TWRP, but the problem is every time you reboot the box, the stock rom overwrites the TWRP files and it goes back to Default recovery, to solve this we need to replace the Rom itself too)
5. Replacing the Rom
5.1 While still in TWRP page, make a small boot backup just so TWRP makes a folder in storage of your device.
5.2 Reboot the device from TWRP (reboot system)
5.3 Now using a File manager (I used X-plore) copy the Rom folder to the same backup folder that was created by TWRP in your storage.
Copy This folder:
MDZ-16-AA-AndroidTV-V1\TWRP\BACKUPS\11608V180037788\2014-12-31--18-01-42_6.9.7.949
To this folder: (Which is already should be there created by TWRP)
Internal Storage\TWRP\Backups\ (your device’s Serial number)\
5.4 Repeat steps 4.6 & 4.7 again to Flash TWRP again, after booting to TWRP go to restore and select file (2014-12-31--18-01-) to restore, swipe to restore and wait for 10-15 minutes
5.5 After restore is done don’t reboot, go back to TWRP main page, go to Wipe then advanced wipe, select Dalvik, Cache and Data to be wiped. After wipe is done reboot system
5.6 When android system boot is complete, go to setting down below and change the language to English and its done.
I hope it helps
Click to expand...
Click to collapse
I successfully rooted my mibox 3c (MDZ-16-AA) and installed TWRP app and Android TV.
Now I want to go back to the Xiaomi Original Firmware (1.5.25). I tried to use TWRP and the Update.zip, but it did not work. How can I do it? Many thanks!
---------- Post added at 09:59 AM ---------- Previous post was at 09:53 AM ----------
I read from a Chinese forum that the 1.4.32 can also be rooted. As far as I know the Android TV is based on the 1.3.106. Does it make any sense to root the MDZ-16-AA with the firmware 1.4.32 and install the Android TV then?
MXQ PRO 4K 5G OFFICIAL STOCK FIRMWARE (ROOTED)If you have an MXQ PRO 4K 5G that it's bricked or a firmware that doesn't support your current WiFi module then this is for you.Only works for Allwinner H3 models with 5G support!
SPECS WITH THE BOX THAT I TESTED:
CPU: Allwinner Tech H3 @1.1Ghz
RAM MODULES: SEC 246 (4 Chips) and ELPIDA J2104ECSE (4Chips)
RAM Space: 4GB (1GB Actual)
ROM: 64GB (8GB Actual)
WiFi: SV6256P (Most stable)
Board ID: QL2039 - Q44_V4.0_20200602
Things to prepare:
A full sized USB to USB cable (You can make your own using your old charging cables)
A computer that is running Windows 7 or later
A toothpick or anything that would fit on the AV port
USB Mouse to interact with TWRP Recovery
5G only:
-Flash box with the firmware H3-R69-MXQ-S-MXQ4K-8PD3-1.1.4 using phoenix suite
The Box will boot, but WiFi not working
-Go and activate developer options and enable USB debugging and USB0 device mode
-Copy twrp.zip (from archive in link bellow) to flash drive
-Connect Phoenix suite to box using the USB to USB cable and press recovery and the box will boot into recovery mode
-Press install update from external and choose twrp.zip (executable only) DO NOT TRY to install just run it!
-Make full backup of "no-WiFi" rom (check all boxes) and save it to external flash drive
-When is done, disconnect flash drive from box and connect to pc. Replace only files ( from backup in link bellow ) to folder in flash drive. DO NOT rename folder!
-Boot box to "no-WiFi" rom and connect to phoenix suite and press recovery again.
- From stock recovery load twrp.zip again, point where backup is, mark again all boxes, and choose restore.
- Wait to finish and press reboot when is done.
Box will now boot to stock firmware with working Wi-Fi
This firmware is tested with the "SV6256P" WiFi chipset.
XR819 Devices are not supported!
This ROM will still boot without the following WiFi modules but Wi-Fi function will not work, Hope you will find the right one soon though GL on your next Google search
Tips:
1. If you've noticed the display output resolution is not 4K
Go to Settings>Display>HDMI output mode>4K_30Hz (Refresh rate is limited to 30Hz/FPS due to hardware limitations)
2. If you accidentally deleted Netflix app or you want to update YouTube just go to GetApps app (No need to go to some dodgy websites just go to the built in rooted store to get the latest updates)
3. It's really hard to find a custom ROM that is fully working for this Box but you can actually customize it on your own like the attached image below
4. A driver is required for Phoenix Suit to detect the box when plugged in please download a working driver before doing so, if the box is detected you can continue the steps without downloading the driver.
5. To flash the box use the USB port 4 (Located at the back side of the box or the rear panel where the rear ports are located) your PC will not detect the box if you use USB port 1-3!
Downloads:
Phoenix Suit V1.10 Flash Tool Download
Download all files Here
ROM INFO:
ROM OS Version: Android 7.0-7.1 Actual
ROM Kernel: Linux 4.4.55
Android Security patch level: (Located in Settings>TV Status)
Klein61967 said:
MXQ PRO 4K 5G OFFICIAL STOCK FIRMWARE (ROOTED)If you have an MXQ PRO 4K 5G that it's bricked or a firmware that doesn't support your current WiFi module then this is for you
SPECS WITH THE BOX THAT I TESTED:
CPU: Allwinner Tech H3 @1.1Ghz
RAM MODULES: SEC 246 (4 Chips) and ELPIDA J2104ECSE (4Chips)
RAM Space: 4GB (1GB Actual)
ROM: 64GB (8GB Actual)
WiFi: SC6256P, SV6256P and SV5256P
Board ID: QL2039 - Q44_V4.0_20200602
Things to prepare:
A full sized USB to USB cable (You can make your own using your old charging cables)
A computer that is running Windows 7 or later
A toothpick or anything that would fit on the AV port
USB Mouse to interact with TWRP Recovery
5G only:
-Flash box with the firmware H3-R69-MXQ-S-MXQ4K-8PD3-1.1.4 using phoenix suite
The Box will boot, but wifi not working
-Go and activate developer options and enable usb debugging and USB0 device mode
-Copy twrp.zip (from archive in link bellow) to flash drive
-Connect Phoenix suite to box using the USB to USB cable and press recovery and the box will boot into recovery mode
-Press install update from external and choose twrp.zip (executable only) DO NOT TRY to install just run it!
-Make full backup of "no-wifi" rom (check all boxes) and save it to external flash drive
-When is done, disconnect flash drive from box and connect to pc. Replace only files ( from backup in link bellow ) to folder in flash drive. DO NOT rename folder!
-Boot box to "no-wifi" rom and connect to phoenix suite and press recovery again.
- From stock recovery load twrp.zip again, point where backup is, mark again all boxes, and choose restore.
- Wait to finish and press reboot when is done.
Box will now boot to stock firmware with working Wi-Fi
This firmware is tested with the following WiFi modules below:
SC6256P
SV6256P
SV5256P
(It is possible that this firmware will work without the following WiFi modules just make sure you have the 5G model or else success rate is very low)
Tips:
1. If you've noticed the display output resolution is not 4K
Go to Settings>Display>HDMI output mode>4K_30Hz (Refresh rate is limited to 30Hz/FPS due to hardware limitations)
2. If you accidentally deleted Netflix app or you want to update YouTube just go to GetApps app
3. It's really hard to find a custom ROM that is fully working for this Box but you can actually customize it on your own like the attached image below
Download files Here
ROM INFO:
ROM OS Version: Android 7.1 Actual
ROM Kernel: Linux 4.4.55
Android Security patch level: (Located in Settings>TV Status)
Click to expand...
Click to collapse
From where can I download this Rom
Klein61967 said:
MXQ PRO 4K 5G OFFICIAL STOCK FIRMWARE (ROOTED)If you have an MXQ PRO 4K 5G that it's bricked or a firmware that doesn't support your current WiFi module then this is for you
SPECS WITH THE BOX THAT I TESTED:
CPU: Allwinner Tech H3 @1.1Ghz
RAM MODULES: SEC 246 (4 Chips) and ELPIDA J2104ECSE (4Chips)
RAM Space: 4GB (1GB Actual)
ROM: 64GB (8GB Actual)
WiFi: SC6256P, SV6256P and SV5256P
Board ID: QL2039 - Q44_V4.0_20200602
Things to prepare:
A full sized USB to USB cable (You can make your own using your old charging cables)
A computer that is running Windows 7 or later
A toothpick or anything that would fit on the AV port
USB Mouse to interact with TWRP Recovery
5G only:
-Flash box with the firmware H3-R69-MXQ-S-MXQ4K-8PD3-1.1.4 using phoenix suite
The Box will boot, but wifi not working
-Go and activate developer options and enable usb debugging and USB0 device mode
-Copy twrp.zip (from archive in link bellow) to flash drive
-Connect Phoenix suite to box using the USB to USB cable and press recovery and the box will boot into recovery mode
-Press install update from external and choose twrp.zip (executable only) DO NOT TRY to install just run it!
-Make full backup of "no-wifi" rom (check all boxes) and save it to external flash drive
-When is done, disconnect flash drive from box and connect to pc. Replace only files ( from backup in link bellow ) to folder in flash drive. DO NOT rename folder!
-Boot box to "no-wifi" rom and connect to phoenix suite and press recovery again.
- From stock recovery load twrp.zip again, point where backup is, mark again all boxes, and choose restore.
- Wait to finish and press reboot when is done.
Box will now boot to stock firmware with working Wi-Fi
This firmware is tested with the following WiFi modules below:
SC6256P
SV6256P
SV5256P
(It is possible that this firmware will work without the following WiFi modules just make sure you have the 5G model or else success rate is very low)
Tips:
1. If you've noticed the display output resolution is not 4K
Go to Settings>Display>HDMI output mode>4K_30Hz (Refresh rate is limited to 30Hz/FPS due to hardware limitations)
2. If you accidentally deleted Netflix app or you want to update YouTube just go to GetApps app
3. It's really hard to find a custom ROM that is fully working for this Box but you can actually customize it on your own like the attached image below
Download files Here
ROM INFO:
ROM OS Version: Android 7.1 Actual
ROM Kernel: Linux 4.4.55
Android Security patch level: (Located in Settings>TV Status)
Click to expand...
Click to collapse
josejosemanoel said:
From where can I download this Rom
Click to expand...
Click to collapse
Download files Here
Anyone knows for a custom rom for this Cortex version? The stock rom really s*x
will this work on rockchip 3299 version?
_harley said:
will this work on rockchip 3299 version?
Click to expand...
Click to collapse
This ROM is tested for Allwinner only but you could try, if you have TWRP recovery...
Just tested this firmware on my box with exact same board ID
Board ID: QL2039 - Q44_V4.0_20200602
The box is bricked, only the red light light on and no blue light when I press power on.
Press the reset once and blue popped up for 2 sec and then again red.
Really no hard feelings here, this box is a trash and I got "cheated" by Banggood selling this as a 4+64 Android 10 device.
It is a modified 7.1 version that looked like 10, so I wanted to get rid of it because lagged or crashed randomly.
@Klein61967 if you have any suggestion happy to hear it. Box still accepts flashing.
Kamui_ said:
Just tested this firmware on my box with exact same board ID
Board ID: QL2039 - Q44_V4.0_20200602
The box is bricked, only and the red light stays on. Tried to press the reset and blue popped up for 2 sec and then again red.
Really no hard feeling here, this box is a trash and I got "cheated" by Banggood selling this as a 4+64 Android 10 device. It was a modified 7.1 version that looked like 10, so I wanted to get rid of it because lagged or crashed randomly.
@Klein61967 if you have any suggestion happy to here them. Box still accepts flashing.
Click to expand...
Click to collapse
Honestly, I really don't know what I can suggest for you to flash. I made this thread to help troubleshoot this box cause I've seen a lot of people complaining about the box like Netflix not working keeps crashing, unwanted UI and Corrupted Roms etc. and yes those specs advertised is obviously fake but this ROM I posted only works with Allwinner H3 Processors it doesn't work on Rockchip, S905W etc. make sure you have Allwinner H3 processor by (carefully) removing the heatsink on top.
Klein61967 said:
Honestly, I really don't know what I can suggest for you to flash. I made this thread to help troubleshoot this box cause I've seen a lot of people complaining about the box like Netflix not working keeps crashing, unwanted UI and Corrupted Roms etc. and yes those specs advertised is obviously fake but this ROM I posted only works with Allwinner H3 Processors it doesn't work on Rockchip, S905W etc. make sure you have Allwinner H3 processor by (carefully) removing the heatsink on top.
Click to expand...
Click to collapse
Yeah I did that months ago when I got the box and understood that its a fake one. Its an Allwinner H3
Maybe the flash messed up the bootloader or maybe your model use a different one because of the different ROM. Do you include bootloader in your img file? I will try once more (already flashed 3 times)
P.S. It's a good reason for me to buy a new "good" one this time
Some extra news. I found and flashed this one https://mega.nz/folder/y4ZSkbDL#5KLc5vKUWOyBAMmJXfGQZw from this video
.
The TV box is alive again
thanks for this. it worked, but i want to tell you that the rom android version is 7.0(sdk24) and not android 7.1 as mentioned.
SreyasXd said:
thanks for this. it worked, but i want to tell you that the rom android version is 7.0(sdk24) and not android 7.1 as mentioned.
Click to expand...
Click to collapse
I'm pretty sure this rom is Android 7.1.2 with API Level of 24 (CPU-Z), also what software did you use?
Klein61967 said:
I'm pretty sure this rom is Android 7.1.2 with API Level of 24 (CPU-Z), also what software did you use?
Click to expand...
Click to collapse
yeah, API level 24 means Android 7.0, and API level 25 is android 7.1, i am going to post my modded tv rom thread for this soc by tomorrow
SreyasXd said:
yeah, API level 24 means Android 7.0, and API level 25 is android 7.1, i am going to post my modded tv rom thread for this soc by tomorrow
Click to expand...
Click to collapse
Oh ok, my apologies...
Hi, this rom work with QL-2036 board?
CPU: ALLWINNER H3 L3064BA
BOARD ID: QL-2036 - Q44_V4.0_20200602
29F64G08CBABA FLASH MEMORY
SV6256P WIFI CHIP TAC 2032 19U68B
sixtoja said:
Hi, this rom work with QL-2036 board?
CPU: ALLWINNER H3 L3064BA
BOARD ID: QL-2036 - Q44_V4.0_20200602
29F64G08CBABA FLASH MEMORY
SV6256P WIFI CHIP TAC 2032 19U68B
Click to expand...
Click to collapse
As long as you have the Allwinner H3 chip and this following onboard WiFi chips:
WiFi: SC6256P, SV6256P and SV5256P
then yes it will work.
My board is this. The PC doesn't recognize it and not the card, it doesn't recover from the SD card either.
Kamui_ said:
Some extra news. I found and flashed this one https://mega.nz/folder/y4ZSkbDL#5KLc5vKUWOyBAMmJXfGQZw from this video
.
The TV box is alive again
Click to expand...
Click to collapse
Hi, I did the installation of that rom and it remains in the ALLWINER logo. Does not start. any ideas to fix it?
I attach images of the board
Klein61967 said:
As long as you have the Allwinner H3 chip and this following onboard WiFi chips:
WiFi: SC6256P, SV6256P and SV5256P
then yes it will work.
Click to expand...
Click to collapse
Hi, @Klein61967 , the system boots fine after (+-) 15 tries (I remove and insert the power cable several times because in those times it is frozen). what is happening with my board, why is that happening?
When the system is running it has no problems, it connects to the wifi well, and it executes the applications perfectly.
any ideas please.
sixtoja said:
Hi, @Klein61967 , the system boots fine after (+-) 15 tries (I remove and insert the power cable several times because in those times it is frozen). what is happening with my board, why is that happening?
When the system is running it has no problems, it connects to the wifi well, and it executes the applications perfectly.
any ideas please.
Click to expand...
Click to collapse
Sorry I don't, I haven't encounter this type of problem before maybe your CPU is overheating make sure you reapplied your heatsink properly after checking it's model or if the motherboard is outside the case don't touch it you're probably shorting the contacts on your motherboard tried it before and sure enough it did freeze.