Related
[TOOLKIT] UNIFIED ANDROID TOOLKIT - SAMSUNG GALAXY S4 MINI - Drivers, Root, Recovery + MORE
INTERNATIONAL GSM MODEL [GT-I9190] [Supported up to 4.2.2]
INTERNATIONAL LTE MODEL WITH NFC [GT-I9195] [Supported up to 4.2.2]
DUAL SIM GSM MODEL [GT-I9192] [Supported up to 4.2.2]
LATIN LTE MODEL [GT-I9195L] [Supported up to 4.2.2]
LTE MODEL [GT-I9195T] [Supported up to 4.2.2]
Click to expand...
Click to collapse
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. Hold down the 'HOME' + '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 any procedures within this guide. No warranties of any kind are given.
**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.
There is more Information/Help at http://www.skipsoft.net/?page_id=1269
**VIDEOS**
**UPDATES**
Amazing! Thanks!!
Tapatalk-kal küldve az én GT-I9195-el
Glad to see this. I've got the toolkit for my 2012 Nexus 7, it is very useful.
hi !
i have a question about full backup/restore of roms ,but nobody can answer to me .
=> http://forum.xda-developers.com/showthread.php?t=2697516
what do you think about ?
thank in advance !
Loulou-13 said:
hi !
i have a question about full backup/restore of roms ,but nobody can answer to me .
=> http://forum.xda-developers.com/showthread.php?t=2697516
what do you think about ?
thank in advance !
Click to expand...
Click to collapse
If you have a backup made in custom recovery then you can boot to custom recovery and restore it. This will take you back to the exact state when you made the backup. The /data/media/ (internal storage) is not backed up by custom recovery but this will not affect the backup in any way.
If you wipe data from recovery after the flash then all installed apps (apart from the stock ones) will be deleted so if you want to wipe the /data/media folder then do so before restoring the backup. Also make sure the backup is on your external storage (micro sdcard) or it will be deleted when you perform a wipe.
Mark.
hi !
thank you very much for your answer !
when i have made a backup of a stock rom (rooted) , i have tested CM10.1.2 ...and after that, i go to recovery for to restore my previous backup ( with wipe data-factory +cache + dalvik before restoring my stock rooted rom ) ====> i had lots of bigs FCs !!!! hard to switch off the phone (too much FCs)
why ??? where is the problem ?
( to solve it in emergency ,i had to do the 3 wipes agains ,switch-off the phone and flash stock firmware via odin ... )
mskip said:
**UPDATES**
Click to expand...
Click to collapse
Could you by any chance provide a full firmware for I9195 and the others I9190, I9192?
(meaning PIT, CSC, BOOTLOADER files for Odin)
I want to provide a free mirror for my unbrick thread
Deleted....
Sorry this should have been posted on here a while ago.
The device module has just been updated and i'm trying to update all the threads.
Toolkit Update
+Updated Toolkit base to v1.3.4
+Added support for the latest available builds on all device modules
+Updated SuperSU [Chainfire] root app to latest version v2.45
+Added SuperSU Beta [Chainfire] root app to flash if required latest version v2.42
+Updated Busybox installer by Stephen Erickson to v25
+Updated Root Checker by Burrows Applications to v3.68
+Added Install EFS/Partition Backup/Restore app by Wanam v1.33
+Added an any build option to the build menu [pro users only] to root any build
+Updated root procedures for better operation
+Toolkit will now notify you a new public version is available and download the installer for you
+Fixed unroot zip file to properly unroot your device
+Updated a lot of the code
Supported models/builds list: http://www.skipsoft.net/?page_id=1203
Download from: http://www.skipsoft.net/?page_id=1069
If you have already downloaded the new Toolkit and have the v3 module for the S3 Mini then delete the ConfigGalaxyS3Mini.exe 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/fileupdates/Unroot-UninstallBusybox-CwmManager.zip and move it to the root folder, start the Toolkit and select the Galaxy S3 Mini from the list. The Toolkit will then download new module files.
Mark.
AutoUpdate Available for Samsung Galaxy S4 Mini module (Ultimate/Pro Users)
CHANGELOG:
BIG UPDATE [sorry its not been updated in a while]
+Updated models to support latest builds [including any build option]
+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 selection
+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.
Code:
*** Disclaimer
I/XDA am/is not responsible for any kind of damage to your device,
or in case it explodes, your surroundings.
Please use it at your own risk!
Team Win Recovery Project 2.x, or twrp2 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.
Phone look:
Tablet look:
Bugs :
1. Reboot->Recovery doesn't work as required. Reboots to system instead.
Please do report any, if found.
Click to expand...
Click to collapse
Download :
Recovery-TWRP_2.8.3.0u1-NK.zip
Installation :
A. With custom recovery already installed :
1. Download zip
2. Reboot to recovery
2. Install zip in recovery
3. Reboot to recovery
B. With stock recovery (Root required) :
1. Download zip & extract recovery.img
2. Move recovery.img to root of external storage
3. Open Terminal
4. (If using terminal on PC) Execute :
Code:
adb shell
5. Execute the following commands :
Code:
su
dd if=/sdcard/recovery.img of=/dev/recovery
exit
C. Through SP flash tools :
1. Install drivers for your phone using Micromax drivers.
2. Extract the Stock ROM folder and replace recovery.img with recovery.img from zip.
3. Extract and open the SP Flash Tools.
4. In SP Flash Tools, click on Scatter-Loading and the program will ask you the location of the scatter loading file for your device select mt6589 scatter file.txt of your phone.
5.Check only Recovery, Preloader and uncheck all others.
6. Switch off your phone (Remove the battery to make sure it is switched off).
7. In Flash Tool, go to Options and Click USB Mode so that it is enabled. Click options again and then go to DA Download All > Speed and finally select High Speed.
8. Click the Download option (present on the right of Firmware > Upgrade option) and the flash tool will start looking for your phone.
9. Connect your phone now. The Flash Tool will start the flashing process, the progress of which can be viewed from a yellow progress bar at the bottom of the flash tool.
Warning 1 - Don't interrupt this process as it can potentially brick your device.
Warning 2 - Make sure no power interruption takes place. (Use a laptop to ensure this).
10. After the process completes, a green ring will appear on your device signalling that the process was successful.
11. Disconnect your phone.
Sources :
Recovery : https://github.com/omnirom/android_bootable_recovery
Kernel : https://github.com/neomanu/NeoKernel-MT6589-A116
Device : https://github.com/neomanu/android_device_micromax_a116-twrp
Credits :
@suhas.holla (for original device tree)
NO PORT REQUESTS
NO QUOTING THE WHOLE OP
You will be reported!
XDA:DevDB Information
TWRP 2.8.3.0, Tool/Utility for the Micromax A116
Contributors
neomanu
Version Information
Status: Stable
Current Stable Version: 2.8.3.0u1
Stable Release Date: 2014-12-26
Created 2014-12-22
Last Updated 2014-12-29
Reserved
Changelog :
2.8.3.0u1 :
- Added F2FS tools. Can be used to format filesystems to F2FS.
- Removed SuperSU (to fit into partition)
2.8.3.0 :
- MTP will now tell the host PC that storage is removed instead of disabling MTP completely
- MTP will now report the correct max file size based on the file system in use to the host PC (may fix transfer of large files)
- Update and improve fix permissions and make fixing contexts optional
- Update SuperSU in TWRP to 2.40 and update install process
- Make TWRP work properly on AArch64 (Nexus 9 is now built in true 64-bit binaries and libraries)
- Attempt to set correct permissions and contexts on all files placed in storage so backups will show in Android
- Fix kernel panic during MTP start on some devices
- Support unicode fonts on devices with True Type Font support
- Fix slider value not showing sometimes (vibration settings page)
- Toggle MTP off during adb sideload to set correct USB IDs
- Reduce library requirements for 5.0 L decrypt
2.8.2.0 :
-Pull in all changes from Android 5.0 lollipop into TWRP
-Add decrypt support for Android 5.0 lollipop encrypted partitions including automatic decrypt when the default_password is in use
-Revert some changes to exFAT that were breaking exFAT support on some devices
-Other minor fixes and updates
Note: At this time we do not have a GUI representation for pattern unlock. You can still decrypt patterns though by translating the pattern dots to numbers. The pattern dots correspond to numbers in the following pattern:
1 2 3
4 5 6
7 8 9
So an upper-case L would translate to a password of 14789 entered on the keyboard. Eventually we plan to add a proper pattern unlock to TWRP but it is a relatively low priority at this point.
Also note that you will need the latest adb binaries on your computer to sideload with this new version of TWRP.
2.8.1.0 :
- MTP fixes and improvements - you can now copy zips to the root of storage - thanks to _that
- TrueType Font support - optional as it takes up a decent amount of space so may not be available on all devices - thanks to Tassadar
- Temperature support - thanks to bigbiff
- Various other bugfixes and tweaks
2.8.0.1 :
- Fix a bug that caused weird graphics and touch issues
2.8.0.0 :
- Add MTP support to recovery thanks mostly to bigbiff with a little help from Dees_Troy
- Add command line capabilities - you can now execute various TWRP features via adb instead of the touchscreen
- Add support for color in the console and give error, warning, and highlight lines different colors
- Track backup and restore progress based on file sizes to provide a much more accurate indication of progress
- Improve handling of /misc thanks to mdmower
- Improve setting of time on Qualcomm devices thanks to [NUT]
- Allow using images on slidervalue GUI objects thanks to Tassadar
- Allow using variables and addition and subtraction in variables for easier theming
- Add support for 1440x2560, 280x280, and 320x320 resolutions and update 240x240
- Allow ui.xml file to include additional xml files to help break up the theme and make TWRP easier to maintain
- Other minor fixes and improvements
Over the course of the last year or so, bigbiff has worked to migrate various Java functions from Android's MTP implementation to bring you a fully C++ based MTP implementation that allows you to transfer files to both emulated storage and Micro SD cards. It's confirmed to work on various Nexus devices but we may have to make some changes on other devices to keep Windows happy. Windows is very picky about USB IDs and its drivers. We have tested it on Windows 7 and 8 as well as Ubuntu 14.04 Trusty. MTP is enabled by default, but we do toggle it off and on automatically during certain operations such as if you choose to wipe a storage partition. You can enable or disable MTP under the mount menu in TWRP. For more about what MTP is here.
Note: Due to a weird bug with our MTP setup, you cannot copy a zip file to the root of storage with Windows. You can change the .zip to something else like .txt and then copy it to the root and rename the file back to .zip once it's copied to the device. You can also copy the zip into any subfolder.
Command line support is also now available. You can perform various OpenRecoveryScript commands via the adb shell. Depending on what you are doing you may wish to do a "twrp set tw_mtp_enabled 0" and then reboot to prevent the MTP auto toggle from killing your adb interface. You can use this option to create and restore backups, wipe, install zips, and more. Via adb shell, type twrp followed by a space then enter the OpenRecoveryScript command and hit enter. Find more OpenRecoveryScript commands here.
2.7.1.0 :
- Add GUI option to change or repair file systems on individual partitions. The change is destructive so backup your data including internal sdcard first. This option should make it a little easier to migrate a device from ext4 -> f2fs, for instance. You will find this option under Wipe -> Advanced Wipe, then select only one partition and then press the Repair or Change File System button. If a developer has added f2fs support for your device and we don't have it in TWRP, please contact me via PM to arrange for it to be added.
- Various bugfixes to backup and restore
- Improvements to USB storage handling
- Added a class to search for files to make finding the correct brightness file automatic in most cases
- Various other bugfixes and tweaks
Reserved
Awsome work bro.. :thumbup::thumbup:
Thank you so much.. Downloading
good work bro!!:good::good:
thanks for compiling this !!
Can we use this to flash Android 5.0.1 by kashifmin ?? !!
and anyway to solve reboot --> recovery problem ! ?
Awsome work once again MAN!!!!! Really, very greatful to you.... Just one more request to you...... Can you just compile a new kernel for our device from this Source (a tweaked kernel) so that we can have it on cm11.... because the kernel used in cm for now is not tweaked and a bit poor performance... i would have done that work but busy with my exams... so if you can please .. or i would be back within few weeks....
Once AGAIN , NICE WORK!! Keep it UP!!
Regards
Andy
can I flash this recovery... ?? currently I'm using AOSB ROM...
Sent from my Canvas HD
vaas kr said:
can I flash this recovery... ?? currently I'm using AOSB ROM...
Sent from my Canvas HD
Click to expand...
Click to collapse
Sure... you can with mobileuncle tools... (AND RECOVERY(S) ARE MEANT FOR FLASHING )
Regards
Andy
neomanu said:
Code:
*** Disclaimer
I/XDA am/is not responsible for any kind of damage to your device,
or in case it explodes, your surroundings.
Please use it at your own risk!
Team Win Recovery Project 2.x, or twrp2 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.
Phone look:
Tablet look:
Bugs :
Download :
Recovery-TWRP_2.8.3.0u1-NK.zip
Installation :
A. With custom recovery already installed :
1. Download zip
2. Reboot to recovery
2. Install zip in recovery
3. Reboot to recovery
B. With stock recovery (Root required) :
1. Download zip & extract recovery.img
2. Move recovery.img to root of external storage
3. Open Terminal
4. (If using terminal on PC) Execute :
Code:
adb shell
5. Execute the following commands :
Code:
su
dd if=/sdcard/recovery.img of=/dev/recovery
exit
C. Through SP flash tools :
1. Install drivers for your phone using Micromax drivers.
2. Extract the Stock ROM folder and replace recovery.img with recovery.img from zip.
3. Extract and open the SP Flash Tools.
4. In SP Flash Tools, click on Scatter-Loading and the program will ask you the location of the scatter loading file for your device select mt6589 scatter file.txt of your phone.
5.Check only Recovery, Preloader and uncheck all others.
6. Switch off your phone (Remove the battery to make sure it is switched off).
7. In Flash Tool, go to Options and Click USB Mode so that it is enabled. Click options again and then go to DA Download All > Speed and finally select High Speed.
8. Click the Download option (present on the right of Firmware > Upgrade option) and the flash tool will start looking for your phone.
9. Connect your phone now. The Flash Tool will start the flashing process, the progress of which can be viewed from a yellow progress bar at the bottom of the flash tool.
Warning 1 - Don't interrupt this process as it can potentially brick your device.
Warning 2 - Make sure no power interruption takes place. (Use a laptop to ensure this).
10. After the process completes, a green ring will appear on your device signalling that the process was successful.
11. Disconnect your phone.
Sources :
Recovery : https://github.com/omnirom/android_bootable_recovery
Kernel : https://github.com/neomanu/NeoKernel-MT6589-A116
Device : --to be updated--
Credits :
@suhas.holla (for original device tree)
XDA:DevDB Information
TWRP 2.8.3.0, Tool/Utility for the Micromax A116
Contributors
neomanu
Version Information
Status: Stable
Current Stable Version: 2.8.3.0u1
Stable Release Date: 2014-12-26
Created 2014-12-22
Last Updated 2014-12-26
Click to expand...
Click to collapse
I have flashed twrp recovery 2.7.00 already.. Do i need to flash it ..?
Sent from my Micromax A116
jam884 said:
I have flashed twrp recovery 2.7.00 already.. Do i need to flash it ..?
Sent from my Micromax A116
Click to expand...
Click to collapse
No, you don't.
And everyone, please refrain from quoting the whole OP, and specially no port requests.
Both will be reported immediately.
jam884 said:
I have flashed twrp recovery 2.7.00 already.. Do i need to flash it ..?....
Click to expand...
Click to collapse
neomanu said:
No, you don't. .....
Click to expand...
Click to collapse
you mean there's no tangible benefit of using v2.8.3.0u1 if one's already running v2.7.0.0?
m0han said:
you mean there's no tangible benefit of using v2.8.3.0u1 if one's already running v2.7.0.0?
Click to expand...
Click to collapse
I'm saying that if someone is going to ask such questions after such a lengthy changelog has been posted, they might as well not.
neomanu said:
I'm saying that if someone is going to ask such questions after such a lengthy changelog has been posted, they might as well not.
Click to expand...
Click to collapse
your twrp v2.8.3.0u1 seems to work ok :good:.backup got saved in /emmc/TWRP/BACKUPS/Canvas_HD. how about shortening that to A116?
on another note, i'd like to have the font you've used in your recovery, on twrp v2.8.2.0 for xolo q3000. can you help in any way? thanks.
m0han said:
on another note, i'd like to have the font you've used in your recovery, on twrp v2.8.2.0 for xolo q3000. can you help in any way? thanks.
Click to expand...
Click to collapse
The font used is the new default in TWRP, from v2.8.1.0.
Refer to this commit.
All you need to do is to unpack the ramdisk, add RobotoCondensed-Regular.ttf to /res/fonts/ and change the following in /res/ui.xml according to the required resolution.
Repack and you have the font.
neomanu said:
No, you don't.
And everyone, please refrain from quoting the whole OP, and specially no port requests.
Both will be reported immediately.
Click to expand...
Click to collapse
In my twrp 2.7.0.0 it shows wipe option with dalvik,cache,factory reset..in single swipe.. What should i do to separate them..
Sent from my Micromax A116
jam884 said:
....What should i do to separate them....
Click to expand...
Click to collapse
try clicking advanced wipe and choosing what you need....
m0han said:
try clicking advanced wipe and choosing what you need....
Click to expand...
Click to collapse
Thanx a lot friend...
Sent from my Micromax A116
@neomanu
Thanks for TWRP_2.8.3.0
I have one issue some time stuck when flash zip on TWRP_2.8.3.0u1-NK
When flash same zip in preview recovery (TWRP 2.8.0.0 hyperion70) it work fine
any news on an update to fix the boot to recovery option ??
Hi,
My mobile name is "Walton Primo-GF4" it's Android version Lollipop 5.1 and Chipset "MTK6580" I want to ROOT my phone!! I also tried many kind of ROOT Apps.. Like: Framroot, Kingroot, iRoot, Baidu Root, A-Key Rootmaster etc but all apps didn't worked!!
NOTE: MY PHONE ALSO UNLOCKED BOOTLOADER
My Acer tablet runs Android version Lollipop 5.1 with CPU MTK8151. I also tried many kind of root Apps including Framroot, Kingroot, and Kingo Android Root but none of the apps worked. I would welcome any suggestions.
How to install and recowery TWRP ROOT - as I do.
On the drain insertion rekaveri I did not run after the entry androyd lying belly to the top with an exclamation mark.
1) Put Flash Tool 5
1.1) Put the USB driver on the PC (It is advisable to disable the driver signature verification in windows- google to help)
2) Download Recovery - TWRP
3) Fail scatter
------ = 2.3 points lozhish files in a separate folder ---
4) I can not remember without root works or not, but just in case I will write. If you need a backup of your phone (need Flash card gigs 4-8) is placed on the phone titanium backup - you come - Click on the second tab (backups) from the top of the icon sheet daw - choose "Make RK entire user software." move to backup to a different folder, and once again do but to "make all RK custom software and system data" - this just in case.
5) Turn off the phone
6) includes a program Flash Tool
7) specifies the path to the file scatter
8) Should Fail recovery stand daw
9) Put Download only
10) Press Download
11) Connect the power cord to the body.
After excluding telephone (ALWAYS !!!!) Press VOL +, and ON. together, should see boot menu, select the button and press the + recovery - to go to TWRP
In the TWRP - press "backup" in the next window, you put all the jackdaws and snap your top do not remember exactly where, but there you can select the external sd card to record backup. and backup for 10 more minutes.
All of us do not care at all, you can do what you want =))
Then do in TWRP reboot in normal mode (need WI-FI), should appear with an offer to make a root or not to do - disagree. body boot turn on the 'Net WI-FI and start downloading the patch for the root, then as a patch will be downloaded will choose the menu that appears after installation TWRP, body restarts itself do everything.
ALL! Ruth received.
use CF-auto-Root
Hey, guys New kingroot app version is worked mt6580.. now my Walton-GF4 is ROOTED, Thanks Everyone!!
can you give me link new version kingroot . i have kingroot 4.9.0 its not work my mt6580 Android 5.1
magik235 said:
My Acer tablet runs Android version Lollipop 5.1 with CPU MTK8151. I also tried many kind of root Apps including Framroot, Kingroot, and Kingo Android Root but none of the apps worked. I would welcome any suggestions.
Click to expand...
Click to collapse
Try downloading latest MTK droid tool and see if it detects your phone. If it detects, then you could just root by clicking root button. If you do not know how to use MTK droid tool, just search for the instruction on XDA. Pretty easy.
twrp-custom-recovery-for-wiko-sunny
tlysovych said:
How to install and recowery TWRP ROOT - as I do.
On the drain insertion rekaveri I did not run after the entry androyd lying belly to the top with an exclamation mark.
1) Put Flash Tool 5
1.1) Put the USB driver on the PC (It is advisable to disable the driver signature verification in windows- google to help)
2) Download Recovery - TWRP
3) Fail scatter
------ = 2.3 points lozhish files in a separate folder ---
4) I can not remember without root works or not, but just in case I will write. If you need a backup of your phone (need Flash card gigs 4-8) is placed on the phone titanium backup - you come - Click on the second tab (backups) from the top of the icon sheet daw - choose "Make RK entire user software." move to backup to a different folder, and once again do but to "make all RK custom software and system data" - this just in case.
5) Turn off the phone
6) includes a program Flash Tool
7) specifies the path to the file scatter
8) Should Fail recovery stand daw
9) Put Download only
10) Press Download
11) Connect the power cord to the body.
After excluding telephone (ALWAYS !!!!) Press VOL +, and ON. together, should see boot menu, select the button and press the + recovery - to go to TWRP
In the TWRP - press "backup" in the next window, you put all the jackdaws and snap your top do not remember exactly where, but there you can select the external sd card to record backup. and backup for 10 more minutes.
All of us do not care at all, you can do what you want =))
Then do in TWRP reboot in normal mode (need WI-FI), should appear with an offer to make a root or not to do - disagree. body boot turn on the 'Net WI-FI and start downloading the patch for the root, then as a patch will be downloaded will choose the menu that appears after installation TWRP, body restarts itself do everything.
ALL! Ruth received.
Click to expand...
Click to collapse
I wish it could work for me to?
but ´till now noppes nada nothing,, I'll try to send up some files like the scatter file and custom recovery rom, maybe you´re able to check them out, what is wrong with it.?
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?
Galaxy Tab A 10.5 SM-T590/SM-T595/SM-T597
TWRP and Lineage 16/17.1 for (SM-T590/SM-T595/SM-T597)!!!!!!!!!!!!!!!!!!!!!
BROUGHT TO YOU BY: MrHomebrew
BIG CREDIT TO: Rupansh (For his time, work: dedication and discovery on how to achieve TWRP on these devices).
THANK YOU TO: Cale (For his time, findings and testing).
READ ENTIRE POST!!!!!!!!
READ ENTIRE POST!!!!!!!!
READ ENTIRE POST!!!!!!!!
THIS IS AT YOUR OWN DESCRETION AND I AM NOT RESPONSIBLE FOR ANYTHING THAT COULD GO WRONG (for example a BRICKED DEVICE)!!!!!!!!
EXPECIALLY IF YOU CAN NOT FALLOW INSTRUCTIONS PROPERLY!!!!!!!!
THIS IS SIMPLY A GUIDE AND IF YOU ARE WILLING TO ATTEMPT ON YOUR OWN DEVICE THAT IS FULLY YOUR CHOICE, RESPONSIBILY and DESCRETION!!!!!!!!
IF YOU ARE STUCK IN A BOOTLOOP REBOOT TO DOWNLOAD MODE AND FLASH STOCK SAMSUNG ROM IN ODIN AND IF YOU WOULD LIKE, TRY AGAIN!!!!
1.
Download stock/unmodded Odin:
https://forum.xda-developers.com/attachment.php?attachmentid=4946889&d=1581302091
Install stock SM-T590/T595/T597 PIE rom with stock/unmodded Odin in download mode
(POWER OFF TABLET AND BOOT WITH VOLUME UP, DOWN AND POWER BUTTON WELL PLUGGED IN TO YOUR PC THROUGH USB).
2.
Finish setup SKIP ALL and enable OEM UNLOCK in developer options/settings.
(If developer options/settings is not viewable tap build number in settings/about a bunch of times)
(Then go back and you should see developer options in settings and ENABLE OEM UNLOCK).
3.
Download patched/modded Odin:
https://forum.xda-developers.com/attachment.php?attachmentid=4952061&d=1581888388
Reboot to recovery (POWER OFF TABLET AND BOOT WITH VOLUME UP AND POWER BUTTON).
Select wipe data/factory reset in recovery (THIS WILL WIPE THE TABLET).
THEN SELECT REBOOT TO BOOTLOADER (DO NOT REBOOT THE DEVICE TO THE SYSTEM, STRAIGHT TO THE BOOTLOADER/DOWNLOAD MODE)
(BLACK LOOKING SCREEN THIS TIME).
4.
Download TWRP:
(SM-T590)
Mega - https://mega.nz/#!nVIknQrB!-Zb_xBWy2_Ruj0TBMHPQGvND1uA_LtOvwdRkmV9sFnQ
Zippyshare - https://www15.zippyshare.com/v/dLVoxicq/file.html
(SM-T595/SM-T597)
Mega - https://mega.nz/#!GQQWnASY!T0oJEkwu9m2rviVYFHy_E5tfithsqLYUTjcIW04iGzw
Zippyshare - https://www45.zippyshare.com/v/2VGMIYyb/file.html
Well in download mode open patched/modded Odin.
Select options in patched/modded odin and UNCHECK Auto Reboot and F. Reset Time.
Select recovery.tar.md5 (SPECIFIC FOR YOUR DEVICE MODEL SM-T590 or SM-T595/SM-T597) in the AP tab of patched/modded odin.
Flash recovery.tar.md5 to your tablet.
WHEN FINISHED MAKE SURE TO REBOOT TO RECOVERY MODE/TWRP(STEPS BELOW).
HOLD (VOLUME DOWN AND POWER BUTTON) AND AS SOON AS THE TABLET TURNS OFF HOLD (VOLUME UP AND THE POWER BUTTON) TO FORCE RECOVERY MODE/TWRP
(DO NOT REBOOT THE DEVICE TO THE SYSTEM, STRAIGHT TO RECOVERY MODE/TWRP).
5.
Download Lineage 16 Download Lineage 16 and unpack the .xz so you are left with a .img file (PLACE IT ON A SECONDARY/SPARE MICRO SD CARD):
(SM-T590/SM-T595/SM-T597)
Sourceforge - https://sourceforge.net/projects/an...017-UNOFFICIAL-treble_a64_avN.img.xz/download
Download Disable_Dm-Verity_ForceEncrypt_08.18.2019.zip (PLACE IT ON A SECONDARY/SPARE MICRO SD CARD):
Mega - https://mega.nz/#!eUpj3AAR!B-3_dgBX9nEj4PJufCnCl7FsiS5bJXy-XvNsBg2KQXg
Zippyshare - https://www120.zippyshare.com/v/fDpBrVte/file.html
Download open_gapps-arm-9.0-nano (SELECT AND DOWNLOAD ARM, 9.0 nano VARIANT) (PLACE IT ON A SECONDARY/SPARE MICRO SD CARD):
https://opengapps.org/
Unmount your micro sd in TWRP, remove CURRENT/MAIN micro sd card from your tablet and replace with the SECONDARY micro sd.
In recovery/twrp select wipe tab, then format data and type yes fallowed by enter (THIS WILL FORMAT/ERASE ALL DATA ON THE TABLET).
Go back to main TWRP menu, select reboot and then REBOOT TO RECOVERY.
Once Rebooted to RECOVERY/TWRP select install and at the bottom select install img.
Find the lineage-16.0-20191017-UNOFFICIAL-treble_a64_avN.img select and install it to SYSTEM IMAGE (MAKE SURE YOU SELECT SYSTEM IMAGE FOR INSTALL LOCATION!!!!).
Go back and select wipe then advanced wipe. Toggle System partition, select repair or change partition and then Resize File System.
(Swipe to resize).
Go back select install and at the bottom select install zip.
Then install open_gapps-arm-9.0-nano zip file in TWRP (AND THEN WIPE CACHE/DALVIK).
Go back select install and install Disable_Dm-Verity_ForceEncrypt_08.18.2019.zip in TWRP.
Unmount your micro sd in TWRP, remove SECONDARY micro sd from your tablet and replace it with the MAIN micro sd card.
6.
REBOOT TO SYSTEM AND SEE THE MAGIC HAPPEN (NOT DONE YET IF YOU WANT ANDROID 10 ALONG WITH ADOPTABLE STORAGE!!!!).
Setup device
FORMAT your MAIN micro sd card in android (SHOULD SEE A NOTIFICATION TO FORMAT MICRO SD CARD).
Select the formatting notification, dismiss the first popup and select adoptable/internal storage. (Be Patient and let it finish formatting).
(IF LINEAGE 16 DOES NOT ASK TO FORMAT MICRO SD CARD EJECT THEN PLACE IT IN A WINDOWS COMPUTER AND FORMAT TO SOMETHING ANDROID DOES NOT LIKE AND TRY AGAIN)
(FALLOWING INSTRUCTIONS BELOW)!!!!
Then insert your MAIN micro sd card (THAT IS FORMATTED IN A WAY THAT FORCES YOU TO HAVE TO REFORMAT) the MAIN micro sd card in Lineage 16
(SHOULD SEE A NOTIFICATION TO FORMAT MICRO SD CARD).
Select the formatting notification, dismiss the first popup and select adoptable/internal storage. (Be Patient and let it finish formatting).
7.
Download Lineage 17.1 and unpack the .xz so you are left with a .img file (PLACE IT ON A SECONDARY/SPARE MICRO SD CARD):
(SM-T590/SM-T595/SM-T597)
Sourceforge - https://sourceforge.net/projects/an...111-UNOFFICIAL-treble_a64_avN.img.xz/download
Download open_gapps-arm-10.0-nano (SELECT AND DOWNLOAD ARM, 10.0 nano VARIANT) (PLACE IT ON A SECONDARY/SPARE MICRO SD CARD):
https://opengapps.org/
Download PHH-Magisk (PLACE IT ON A SECONDARY/SPARE MICRO SD CARD)
https://sourceforge.net/projects/de...magisk/Magisk-v20.2-b29f0ca4-phh.zip/download
Power off or reboot to twrp (VOLUME UP AND THE POWER BUTTON).
Unmount your micro sd in TWRP, remove MAIN micro sd card (NOW USED AS ADOPTABLE STORAGE) from your tablet and replace with the SECONDARY micro sd.
Now select install and at the bottom select install img.
Find the lineage-17.1-20200111-UNOFFICIAL-treble_a64_avN.img select and install it to SYSTEM IMAGE (MAKE SURE YOU SELECT SYSTEM IMAGE FOR INSTALL LOCATION!!!!).
Go back and select wipe then advanced wipe. Toggle System partition, select repair or change partition and then Resize File System.
(Swipe to resize).
Go back select install and at the bottom select install zip.
Then install open_gapps-arm-10.0-nano zip file in TWRP (AND THEN WIPE CACHE/DALVIK).
Go back select install and YOU MUST INSTALL Magisk-v20.2-b29f0ca4-phh.zip (OR ELSE LINEAGE 17.1 WILL NOT BOOT).
Go back select install and install Disable_Dm-Verity_ForceEncrypt_08.18.2019.zip in TWRP.
Unmount your micro sd in TWRP, remove SECONDARY micro sd from your tablet and replace it with the MAIN micro sd card (STILL USED AS ADOPTABLE STORAGE).
8.
(VERY IMPORTANT YOU CAN UPDATE (MAGISK MANAGER) BUT NOT (MAGISK) ITSELF!!!! DO NOT UPDATE MAGISK!!!!) YOU WILL END UP IN A BOOT LOOP).
(VERY IMPORTANT) REBOOT TO SYSTEM AND GO IN TO MAGISK MANAGER.
Go to modules in Magisk Manager and install Busybox for Android NDK (DO NOT REBOOT) and also install MagiskHide Props Config (NOW REBOOT).
After reboot go to developer options/settings (System/Advanced/Developer options) and enable Local terminal.
(If developer options is not viewable tap build number in settings/about a bunch of times till it enables)
(Then go back and you should see developer options in settings).
9.
Return to home screen and launch terminal app.
In terminal app type "su" (WITHOUT QUOTES) and hit enter (ALWAYS HIT ENTER TO EXECUTE THE COMMAND).
Accept Magisk/Superuser popup for terminal.
(If you accidentally deny/miss permission go to Magisk a enable Superuser for terminal).
In terminal app type "props" (WITHOUT QUOTES).
Select option "1" (WITHOUT QUOTES), then select option "f" (WITHOUT QUOTES) and then select option "23" (WITHOUT QUOTES).
Now select (ONE OF THESE 3) options "45" (WITHOUT QUOTES) for SM-T590 / option "46" (WITHOUT QUOTES) for SM-T595 / or option "47" (WITHOUT QUOTES) for SM-T597.
Finally select "y" (WITHOUT QUOTES) to accept and then select "y" (WITHOUT QUOTES) to restart.
FINISHED!!!!
YOU ARE DONE!!!!
Hope you enjoy, a lot of work has gone in to making this possible on the Galaxy Tab A 10.5 SM-T590/SM-T595/SM-T597.
BUGS/ISSUES:
Encryption
Lockscreen password NOT WORKING (DO NOT SET A PASSWORD)
MTP not working in TWRP
Two out of four speakers WORKING
Can only enable adoptable storage in Lineage 16 and carry it over to Lineage 17.1
DEMONSTRATION/REVIEW VIDEO COMING SOON!!!!
BROUGHT TO YOU BY THE ONE AND ONLY: MrHomebrew
Contributors: MrHomebrew, Rupansh and Cale.
Source Code Used To Help Build TWRP For SM-T590/SM-T595/SM-T597
https://github.com/rupansh/android_kernel_samsung_gta2xl
Magisk_PHH and Lineage 16/17.1 GSI: AndyYan
XDA:DevDB Information
[RECOVERY][ROM][ROOT][UNOFFICAL] TWRP 3.3.1-0 + Lineage [SM-T590/SM-T595/SM-T597], Kernel for the Samsung Galaxy Tab A series
Contributors
Leonidas87, rupanshji, AndyYan, Cale
Source Code: https://github.com/rupansh/android_kernel_samsung_gta2xl
Kernel Special Features:
Version Information
Status: Stable
Created 2020-02-20
Last Updated 2020-02-20
confirmed working on sm - t590.
many thanks !
supelele said:
confirmed working on sm - t590.
many thanks !
Click to expand...
Click to collapse
You are welcome, thanks for confirming you had success on your end :good:
One issue. Wifi does not stay enabled.
Connection gets disconnected here.
supelele said:
One issue. Wifi does not stay enabled.
Connection gets disconnected here.
Click to expand...
Click to collapse
Try forgetting the network in wifi settings. Reboot and then connect to the network again with the password. Might help, I noticed that one time during testing
MrHomebrew said:
Try forgetting the network in wifi settings. Reboot and then connect to the network again with the password. Might help, I noticed that one time during testing
Click to expand...
Click to collapse
Did try that. It keeps remembered and after a resstart it is connected. But after 2 Minutes it goes to disconnected and stays there.
Tried 2 wifis. Tried aswell reflashing line 17.
No success :/
MrHomebrew said:
Try forgetting the network in wifi settings. Reboot and then connect to the network again with the password. Might help, I noticed that one time during testing
Click to expand...
Click to collapse
Disableing location did the trick
Want to try but...
Firstly, thank you for this. I can only imagine the time and effort to figure this out.
How the hell you guys do this I'll never know. Kudos.
Now, what if I want to install LineageOS 16 without the adoptable storage and get root? Is there a reason one needs adoptable storage for this process?
Nervous about having an eventually-to-fail sd card in there and no spare sd card slot to add storage.
All I really want (sorry, would like) right now is root so I can fiddle with my device. It seems all other attempts at pure root result in bootloop and having to reflash stock. I know, I tried https://forum.xda-developers.com/showthread.php?p=81286251#post81286251 and posted my results.
Is there a method to just install LlineageOS/Gapps, Magisk, Busybox/su?
Not wanting to knock your efforts, but a slimmed down LinOS16 with root installation instr. will be fantastic!
Is there a benefit to having to do the system install with adoptable storage?
Thanks again.
T
TrinityTrip54 said:
Is there a method to just install LlineageOS/Gapps, Magisk, Busybox/su?
Not wanting to knock your efforts, but a slimmed down LinOS16 with root installation instr. will be fantastic!
Is there a benefit to having to do the system install with adoptable storage?
Thanks again.
T
Click to expand...
Click to collapse
You don't have to use adoptable storage it's just an option really. If you want to use lineage 16 you can just fine with even magisk canary builds, might want try out some other GSI a64a ( ARM 32-bit with 64-bit binder, A-only) builds with an AOSP base and see what works. The only benefit would be having extra install space for loads of apps and full access to storage. As far as lineage 17 goes you must flash the magisk-phh for it to even boot but adoptable storage you don't need. Still follow the instructions minus adoptable storage and you'll achieve root in no time. As of right now there's been weekly builds of lineage GSI. Hopefully we'll get a real build of lineage 17 eventually.
Highly recommend orange fox recovery.
whenever i try to flash the recovery i get an error only official released binaries are allowed to be flashed how do i resolve this problem?
Mikxx said:
whenever i try to flash the recovery i get an error only official released binaries are allowed to be flashed how do i resolve this problem?
Click to expand...
Click to collapse
https://www.the***********.com/prenormal-rmm-state-on-samsung-galaxy-guide/
dm.homelinux.com said:
https://www.the***********.com/prenormal-rmm-state-on-samsung-galaxy-guide/
Click to expand...
Click to collapse
link broken but it still helped me out thanks
Boot loop after installing Busybox for Android NDK and MagiskHide Props Config
8.
(VERY IMPORTANT YOU CAN UPDATE (MAGISK MANAGER) BUT NOT (MAGISK) ITSELF!!!! DO NOT UPDATE MAGISK!!!!) YOU WILL END UP IN A BOOT LOOP).
(VERY IMPORTANT) REBOOT TO SYSTEM AND GO IN TO MAGISK MANAGER.
Go to modules in Magisk Manager and install Busybox for Android NDK (DO NOT REBOOT) and also install MagiskHide Props Config (NOW REBOOT).
After reboot go to developer options/settings (System/Advanced/Developer options) and enable Local terminal.
(If developer options is not viewable tap build number in settings/about a bunch of times till it enables)
(Then go back and you should see developer options in settings).
Click to expand...
Click to collapse
Hello community,
I am now at this point. I have installed just Linage 17, without Linage 16 without gapps, because i dont need them.
So, lineage 17 is starting, now I have to prepare Magisk.
I have updated _JUST_ Magisk Manager (see screenshot) and installed two recommended modules (Busybox for Android NDK and MagiskHide Props Config)
After reboot ends up in a boot loop. Interim solution is start to recovery and make factory reset. In this case is Magisk not available. After Magisk installation there is again a loop. I tried this 3 times. What I am doing wrong?
dm.homelinux.com said:
Hello community,
I am now at this point. I have installed just Linage 17, without Linage 16 without gapps, because i dont need them.
So, lineage 17 is starting, now I have to prepare Magisk.
I have updated _JUST_ Magisk Manager (see screenshot) and installed two recommended modules (Busybox for Android NDK and MagiskHide Props Config)
After reboot ends up in a boot loop. Interim solution is start to recovery and make factory reset. In this case is Magisk not available. After Magisk installation there is again a loop. I tried this 3 times. What I am doing wrong?
Click to expand...
Click to collapse
Are you using magisk-phh? Also try using magisk manager Canary
Yes. Step 7
https://sourceforge.net/projects/de...magisk/Magisk-v20.2-b29f0ca4-phh.zip/download
What ist Magisk Manager canary?
Edit: many thx
https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337
It semms to be stable, after I installed this apk. Magisk is now available as app, i can see the installed modules and the system starts correctly.
Do I ned the next steps with su?
The rom works great, but one question, is it possible to get the assistant ambient mode on this device when i place it in my pogodock?
Mikxx said:
The rom works great, but one question, is it possible to get the assistant ambient mode on this device when i place it in my pogodock?
Click to expand...
Click to collapse
As far as I know probably not. These are GSI builds and are not exactly fully supported for our devices but still function pretty good.
---------- Post added at 08:53 AM ---------- Previous post was at 08:53 AM ----------
dm.homelinux.com said:
Yes. Step 7
https://sourceforge.net/projects/de...magisk/Magisk-v20.2-b29f0ca4-phh.zip/download
What ist Magisk Manager canary?
Edit: many thx
https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337
It semms to be stable, after I installed this apk. Magisk is now available as app, i can see the installed modules and the system starts correctly.
Do I ned the next steps with su?
Click to expand...
Click to collapse
Next steps for su? Which steps are you referring too? As soon as you have magisk-phh flashed with Canary manager on 17 you have SU. As far as 17 goes do not update magisk just manager. 16 you can use any magisk up to Canary
koobie777 said:
Next steps for su? Which steps are you referring too? As soon as you have magisk-phh flashed with Canary manager on 17 you have SU. As far as 17 goes do not update magisk just manager. 16 you can use any magisk up to Canary
Click to expand...
Click to collapse
I refer to step 9 in this manual on page 1.
But su is indeed over Magisk configuration. ROM works very well
Magisk also working with LineageOS 16 ?
jb44 said:
Magisk also working with LineageOS 16 ?
Click to expand...
Click to collapse
Yes up to Canary. Use magisk-phh for 17
---------- Post added at 09:35 AM ---------- Previous post was at 09:34 AM ----------
dm.homelinux.com said:
I refer to step 9 in this manual on page 1.
But su is indeed over Magisk configuration. ROM works very well
Click to expand...
Click to collapse
Step 9 is recommended for safteynet