Sharing mi pad 4 plus twrp link - Xiaomi Mi Pad 4 Plus Guides, News, & Discussion

Remember I am not dev of this twrp. I found this twrp in chinese forum and sharing for other mi pad 4 plus users
Note: I am not responsiple if your device was brick.
Make full back up your files. To flash twrp your device need to be unlock. Unlocking your device will void warranty of your device. Carefully use it.Thank.
Original chinese miui forum Link: http://www.miui.com/thread-16375014-1-1.html
RECOVERY information:*
Name version: Xiaomi Tablet mi pad 4(plus) special edition TWRP-3.2.3 Chinese and English modified optimization*
file package name: TWRP-3.2.3-XIAOMI_PAD4 (PLUS ) -CN-wzsx150-fastboot.7z*
build time: 2018.09.30*
applicable models: mi pad 4 and 4plus*
Twrp creator : wzsx150*
micro-blog account: wzsx150*
team name: LR.Team*
email address & Alipay donation account:*wzsx150 @ 163. Com
brushing method: fastboot flash with toolkit contain in zip by extracting 7z file or unzip and flash img by fastboot mode.
Acknowledgement: omni, TeamWin, etc.*
Introduction:*
* * Authors synchronize TWRP latest source code, in the omni environment, use the official kernel file, write your own device code.*Fixed some bugs by modifying the source code, added some functions, and finally compiled.*Thank you for your enthusiastic oil test*.*
* * This RECOVERY is stable and practical, and has many functions. The author has repeatedly measured it and recommended it when using it.*No big bugs have been found yet.*My own test is not very comprehensive, I hope that if the machine friends find any bugs, please give me feedback in time, thank you ~~~~ Brush machine is risky, the operation should be cautious.*The brush machine is an individual voluntary act, and the author does not assume any problems caused by brushing into the rec.*
Welcome to pay attention to Weibo wzsx150, submit bug feedback!*Experience the best REC!
Modify the optimization project:
* Delete redundant languages, keep English, add Chinese language, default Chinese.*
* Modify the default configuration, for example, the default time zone is East Eight Zone, default screen brightness, default vibration, default 24 hours, default return button on the right, default Chinese and so on.*
* Modify the default configuration file path to reduce the possibility of conflicts with other people's compiled versions.*
* Adjust and optimize the Chinese text and description, and re-edit all the items one by one, which is more accurate, understandable and humanized.*Also added display mtp enable off display, file operation result display, operation page title display, permission description when modifying permissions, etc. UI text display.*
* Modify the unlocking interface and adjust the height of the sliding unlocking bar, which can effectively prevent misoperation (the original unlocking bar and the operating unlocking bar are of the same height. When the unlocking is completed, the sliding may be repeated, and the corresponding action is directly operated).*
* Open more partition backup and restore, such as modern baseband partition, bootloader, persist, cust and other partitions, easy to backup the underlying files before brushing, can restore the underlying files after brushing.*
* Add .bin and .mbn format image files, so you don't need a zip brush package, you can write the underlying file.*The original version only supports the brushing of .img format image files.*(Be sure to pay attention to the selected partition!!!!)*
* Solve the problem of interface jam when using the simulation operation (the simulation operation is mainly for testing the theme, and no actual operation).*
* Add the manual installation root function in Advanced Options > root system.*Add a display root system option on this basis for manual operation.*
* Added the ability to unenforce encryption, in advanced options > Unforce Encryption.*You can remove the official system to force encryption and cancel the check.*
* Change the built-in root mode and add magisk as the default root mode.*
* Fixed button and button operations for some interfaces.
* The adb/usb debug mode is enabled by default, which is convenient for operating the phone through the computer command line in rec mode.*
* MTP is enabled by default. In the rec state, you can also connect your phone to your computer to facilitate file copying.*
* Modify the logo interface, modify the header of the main interface page, and add the display phone model and team name, author name.*
* Fix some logical relationships and modify some interface displays.*
* Added clear root function*
* Added clear power-on password function*
* Added clear battery information function*
* Added signature boot function*
* Added restore official rec function
2018.9.30 update:
1. Update source code to 3.2.3
2. Update built-in magisk version to v17. 1
3. Increase the removal of dm checksum and cancel the forced encryption function
4. Support both Xiaomi Tablet mi pad 4 and Xiaomi Tablet mi pad 4plus​
2018.7.13 update:
1. Fix the problem of not recognizing the external memory card
2. After brushing in twrp, the first time Entering twrp may restart once. This is normal. If you restart repeatedly, or you cannot decrypt the data, please give me feedback in time.*
2018.7.11 update:
1. Update the attempt to repair the decrypted data, and expect whether the follow-up can reach the expected.*
2. After brushing in twrp, the first time you enter twrp, it may restart once. This is normal. If you restart repeatedly, or you cannot decrypt the data, please give me feedback in time.*
Important note:
1.*This rec supports data partition automatic decryptionThe encrypted data can be used normally under rec without formatting.*The official system defaults to encrypting data partitions.*Note: If there is a problem with the system inside the phone, there may be cases where the temporary decryption cannot be performed normally.*Android's recent new system for data encryption and twrp automatic decryption may not be compatible, resulting in the system can not get in, please be careful to brush!*!*
2. This rec support to brush into the official original full card brush package.*
3. The bootloader must be unlocked to be able to brush into a third-party rec.*
4. Built-in root system / remove root function, through the root system, you can also remove dm check, prevent card screen, and can make the system root privileges.*
The root system is strongly recommended, otherwise twrp may be overwritten by the official rec.*
Please use my own brush into a key tool into the brush, otherwise, there is a mess of problems arise, do not ask me ha*
known bug:*
no*
pre-brush into the third-party rec, must unlock the phone!*!*Remind again, the brush machine is risky, please be cautious!*
Twrp download address:
link:*https://pan.baidu.com/s/1VX1W5t-K6R5CwSdyRcMYFQpassword: 5fby
(original baidu cloud link)
https://drive.google.com/file/d/1UP9_bapdzmjq4LaMBFYRHKyMZA8xii5d/view
(google drive upload link)
one-click flash into the twrp line brush package (generally download this): TWRP-XXX-CN-wzsx150-fastboot*
After downloading the*.7z*,*unzip the*phone, connect the computer to the computer, double-click to run*the recovery tool.bat*file, follow the prompts, and finally brush the rec into the phone through the fastboot mode.*
twrp image file in the*cost post*: recovery-TWRP-XXX-CN-wzsx150.img*
from the above compressed packages You can extract the image file, you can use the twrp brush image to brush in, app to brush in, QPST to brush in or brush in other ways.*
Twrp image in original chinese forum post.:fingers-crossed:

Do you have any idea to remove mi account on miui10?
do you have any process to remove mi account on miui10? Thank you.

I believe I only have a mi pad 4 which I don't think is the + model. It's hard to say there being no guides or manuals and the people at Xiaomi just say it's a just released and we don't know nothing about it. Come on where is this PR. And I didn't get much from your twrp intro I just read and although it is considered a medium difficulty root I'm getting nowhere.

Related

[TOOLKIT] GALAXY NOTE 8.0, Drivers, Backup, Root, Recovery, Flash + MORE

[TOOLKIT] UNIFIED ANDROID TOOLKIT - SAMSUNG GALAXY NOTE 8.0 [2012 MODEL] - Drivers, Root, Recovery + MORE
The Unified Android Toolkit brings together all the Nexus and Samsung Toolkits and supports a multitude of Nexus and Samsung devices. 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.
SUPPORTED MODELS
GT-N5100 3G/WIFI MODEL
GT-N5110 WIFI ONLY MODEL
GT-N5120 LTE MODEL
Click to expand...
Click to collapse
FUNCTIONS OF UNIFIED ANDROID TOOLKIT V1.3.3 [8TH DEC 2014]
* 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 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
Enable Developer options for usb debugging
Go to Settings, System section, About device and tap on 'Build number' 7 times until it says you are now a developer. You can now go to Settings, System section, Developer options and enable USB debug.
How to get into Recovery Mode
1. Unplug the USB cable.
2. Shut down the device.
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 device.
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.
**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.2).
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).
This feature will be added to the Toolkit after testing has been completed.
----------------------------------------------------------------------------
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.
*reserved if needed*
Mskip
thanks for this
is your version of cwm working properly?
thanks
jocko6872 said:
Mskip
thanks for this
is your version of cwm working properly?
thanks
Click to expand...
Click to collapse
I think that's for us us to test and tell him
sefrcoko said:
I think that's for us us to test and tell him
Click to expand...
Click to collapse
It's the same version as provided in the development thread.
i flashed the cwm
but cant do anything
cant even reboot
jocko6872 said:
Mskip
thanks for this
is your version of cwm working properly?
thanks
Click to expand...
Click to collapse
CWM is the experimental port from emwno in *THIS* thread.
I need people to test if the insecure boot image flashes and whether the root process works.
Mark.
madsatan said:
i flashed the cwm
but cant do anything
cant even reboot
Click to expand...
Click to collapse
Flashing custom recovery shouldnt affect the boot process have you tried just holding the power button for about 15 seconds to force a hard reboot?
Are there any lights or anything on the screen?
Mark.
Sorry that i didnt make myself clear
What i was saying is that i boot into cwm
Cant press any fuctions (cant back up or reboot etc)
I had to use power buttom to restar the tablet
Sent from my GT-N5110 using XDA Premium HD app
madsatan said:
Sorry that i didnt make myself clear
What i was saying is that i boot into cwm
Cant press any fuctions (cant back up or reboot etc)
I had to use power buttom to restar the tablet
Sent from my GT-N5110 using XDA Premium HD app
Click to expand...
Click to collapse
As stated the cwm port is still experimental but it is being worked on by emwno and im sure he will get there.
Has anyone tried the root procedure yet with the insecure boot image? I really need some feedback here.
Mark.
Hey mskip,i just downloaded the toolkit and went through the insecure kernel process with no problems,tho i had already rooted using the Framaroot app. I also installed cwm and booted into it,although it's a little buggy it's useable ,just need something to flash in it now
ktmman said:
Hey mskip,i just downloaded the toolkit and went through the insecure kernel process with no problems,tho i had already rooted using the Framaroot app. I also installed cwm and booted into it,although it's a little buggy it's useable ,just need something to flash in it now
Click to expand...
Click to collapse
Glad its all working ok. Did you go through the ALL-IN-ONE process? Just wondering if you had installed busybox as I need someone to make a NAND backup from the backups section. If you can do that and then post a screenshot of the files (filenames and file sizes) then I can update it to a public version
Mark.
mskip said:
Glad its all working ok. Did you go through the ALL-IN-ONE process? Just wondering if you had installed busybox as I need someone to make a NAND backup from the backups section. If you can do that and then post a screenshot of the files (filenames and file sizes) then I can update it to a public version
Mark.
Click to expand...
Click to collapse
ok,i downloaded Busybox from the market,it looks like its going well,here's the data.
ktmman said:
ok,i downloaded Busybox from the market,it looks like its going well,here's the data.
Click to expand...
Click to collapse
Looks good
Now I just need someone with a full stock firmware flashed that can test the ALL IN ONE process and perform a NAND backup to make sure it works from scratch. Any takers?
Mark.
I will try once I'm home
Sent from my GT-N5110 using Tapatalk HD
n5120
got n5120, lte. can I use tools or I have to wait for n5120 version?
thanx in advance for answer.
goo.im seems to be down. Got a mirror?
thanks mskip
i use your nexus 4 tool kit a lot and was excited to see this one
i had already rooted via the framaroot app. was able to successfully load up CWM recovery (although it needs some help but i see in the other thread its being worked on).
also ran a backup successfully.
Sardo Numspa said:
thanks mskip
i use your nexus 4 tool kit a lot and was excited to see this one
i had already rooted via the framaroot app. was able to successfully load up CWM recovery (although it needs some help but i see in the other thread its being worked on).
also ran a backup successfully.
Click to expand...
Click to collapse
Flash Experimental #4 for your specific device (from my thread). Its working properly now.

[TOOLKIT] UNIFIED ANDROID TOOLKIT - GALAXY TAB S - Drivers, Root, Recovery + MORE

[TOOLKIT] UNIFIED ANDROID TOOLKIT - SAMSUNG GALAXY TAB S - Drivers, Root, Recovery + MORE
SUPPORTED MODELS/VARIANTS
GALAXY TAB S 8.4 [KLIMT]
WIFI ONLY MODEL [SM-T700]
LTE/WIFI MODEL [SM-T705]
LTE/WIFI CANADA MODEL [SM-T705W]
LTE/WIFI S AMERICA MODEL [SM-T705M]
GALAXY TAB S 10.5 [CHAGALL]
WIFI ONLY MODEL [SM-P800]
LTE/WIFI MODEL [SM-T805]
LTE/WIFI CANADA MODEL [SM-T805W]
LTE/WIFI S AMERICA MODEL [SM-T805M]
The Unified Android Toolkit brings together all the Nexus and Samsung Toolkits and supports many Nexus and Samsung devices. 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
* Install correct adb/fastboot drivers automatically on Windows xp/vista/7/8 32bit+64bit/Windows 10
* 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]
* [NEW] use SkipRoot boot image to Auto Root device, install Busybox Binaries and rename Recovery Restore files [selected devices]
* 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
* Flash any part of a stock Nexus image to device [boot, system, recovery] – Great for fixing broken parts of firmware
* 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
--------------------------------------------------------------
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
--------------------------------------------------------------
SUPPORTED DEVICES AND LATEST SUPPORTED BUILDS *HERE*
DOWNLOAD THE SKIPSOFT UNIFIED ANDROID TOOLKIT *HERE* (FROM SKIPSOFT.NET)
NOTE: Key files are signed with a Digital Certificate from skipsoft.net but some ‘may’ get picked up as potentially harmful by Antivirus Programs and deleted. They are not harmful, this is a false positive given because of the compiler used. If this happens restore the file and exclude the folder from future scans to use it. This seems to happen mostly on AVG Free and Norton. If you are using the Auto Update feature on pro versions then you will need to disable the AV program or exclude the folder from scans before running the update again.
Credits: ChainsDD for Superuser, Chainfire for SuperSU and kernel patches, 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, Viperboy for the Knox Disabler app, Stephen Erickson for the BusyBox installer app, BurrowsApps for the Root Checker app, NextApp for the SD Fix app, fOmey for TWRP for the Galaxy Gear.
--------------------------------------------------------------
WHAT IS THE DIFFERENCE BETWEEN PUBLIC (FREE) AND PROFESSIONAL (DONATE) VERSIONS?
THE PUBLIC VERSION OF THE TOOLKIT INCLUDES EVERYTHING YOU COULD NEED TO MANIPULATE AND ROOT YOUR DEVICE.
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 AS LONG AS THE VERSION IS SUPPORTED (USEFUL IF YOUR BUILD IS NOT LISTED).
MORE IMPORTANTLY DONATING SHOWS YOUR APPRECIATION AND ALLOWS THE TOOLKIT TO CONTINUE TO EVOLVE AND GROW.
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 '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 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.
Cool thing remember you from the Hd2 Era
Thanks for porting your tookit over to support our devices. Will be very useful for many
Cheers,
UITA
JUNEBUG-1 said:
Cool thing remember you from the Hd2 Era
Click to expand...
Click to collapse
yes I recall too..great work mskip!
---------- Post added at 08:36 PM ---------- Previous post was at 08:33 PM ----------
mskip..you may want to add that the NA models of the 705 and maybe 805 too cannot make cellular calls even though have LTE data...there have been several threads on this..most recent one in the original development section posed as a question..
this was discussed here already clarified by oldblue (am sure elsewhere too)
http://forum.xda-developers.com/galaxy-tab-s/general/pre-galaxy-tab-s-att-t2881310
http://forum.xda-developers.com/showpost.php?p=56084215&postcount=44
Thanks for your work!
Thanks for the Kit,
I'm looking for a perfectly stable ROM for Tab S 8.4 SM700. The only ROM I saw that seems stable is Iron-man. Are there any other ROM stable for SM 700?
Amazing job!
Thank you very much.
Thanks for this toolkit and for replying to my email, all working ok now.:good:
Does this tool support the SM-T800NTSSXAR ? ( 16GB Wifi US Model - also know as just the SM-T800 )?
ClockerXP said:
Does this tool support the SM-T800NTSSXAR ? ( 16GB Wifi US Model - also know as just the SM-T800 )?
Click to expand...
Click to collapse
Yes. I think there is a typo in the toolkit. It should say SMT800 instead of SMP800
Donated & THANK YOU!
Hi. Thanks for the tool, I'm looking for the root access and I'm wondering if your tool can support the newer version of Tab S 10.5 based on 5433 SoC (i.e., SM-T805K)
http://pdadb.net/index.php?m=specs&...b_s_10.5-inch_broadband_lte-a_samsung_chagall
I have this 5433 model from Korea, which the shell cmd tells me this: chagall. I could not find any root tools for this.
many thanks
Howdy-
I donated so that I could use this toolkit with my Tab S. Works great.
I also made another donation so I could use the Pro version with my Galaxy S4. Unfortunately, when the Pro version loaded up I saw it doesn't support the SCHi545 Verizon version of the phone. I immediately emailed the tool author to see if he would send back my extra donation since I could not actually use the tool for the S4 and because I had already donated for the Tab S. Been over a day and no response. I got the activation code within minutes but no reply the other way around.
I have a question, this root changes Knox to "1"???
Hi guys,
what's the meaning of [KLIMT] in "GALAXY TAB S 8.4 [KLIMT]" pl?
I hate to root my GALAXY TAB S 8.4 WIFI,16G0, is it ok with your tools?
Ths for you answer, good job!
B
Bishopandme said:
Hi guys,
what's the meaning of [KLIMT] in "GALAXY TAB S 8.4 [KLIMT]" pl?
I hate to root my GALAXY TAB S 8.4 WIFI,16G0, is it ok with your tools?
Ths for you answer, good job!
B
Click to expand...
Click to collapse
klimt is the models of the tab s 8.4. Your exact model is SMT700 so Im pretty sure it should work. Hope this helps!
Just got done trying to root and install twrp recovery on the tab s 10.5 wifi and I can get into recovery that worked bu the device is not rooted. twrp installed supersu and then I started it and it preceded to to an update. So I go to start supersu and it give me this message
There is no SU binary installed and supersu cannot install it
Any ideas. I have rooted lots of devices and have never seen this.
Thanks.
kendive said:
Just got done trying to root and install twrp recovery on the tab s 10.5 wifi and I can get into recovery that worked bu the device is not rooted. twrp installed supersu and then I started it and it preceded to to an update. So I go to start supersu and it give me this message
There is no SU binary installed and supersu cannot install it
Any ideas. I have rooted lots of devices and have never seen this.
Thanks.
Click to expand...
Click to collapse
Download a zip(google it) called supersu.zip then flash it with twrp and you will have root.

Axon7Toolkit - Unlock BL, Root, and more! (1.2.1 - 09/04/17)

Code:
/*
* Your warranty is not void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* make sure you are aware of any risks associated with using the options in
* the toolkit BEFORE using it! YOU are choosing to use this toolkit, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Do you want to unlock your bootloader and root? Or switch to another ROM? Are you asking yourself which one of the 100s of guides here on xda should I use? Well no need for any guides! Use this toolkit and be bootloader unlocked and rooted or on a different ROM within MINUTES! Super simple to use, just a couple of clicks and the toolkit does everything else!
COMPATIBILITY​
Supports A2017, A2017G, and A2017U (all software builds)
Windows 7 and up
FEATURES​
- Automatic file downloads with hash verification
- OTA updates
- ADB and Qualcomm EDL driver Installation
- ADB and Fastboot Test
- Backup apps+data
- Restore apps+data
- Backup system/data/boot partitions
- Restore system/data/boot partitions
- Unlock bootloader on ALL software builds (Marshmallow and Nougat) without voiding your warranty!
- Lock bootloader
- Flash TWRP and disable dm-verity and forced encryption
- Root with SuperSU
- Restore to stock/ Recover from hard bricking with EDL restore packages
- Flash an unlimited amount of ROM, kernel, and other zips at once!
-Magisk root (Coming soon)
-Unroot (Coming soon)
-Remove ZTE bloatware (Coming soon)
DOWNLOAD​
You may need to disable your antivirus as the EXE file may get quarantined or removed due to "malware". This is because of the BAT to EXE compiler used and is a false positive. More information available here: [url]https://superuser.com/questions/1117747/why-do-av-software-thinks-that-all-compiled-batch-files-are-viruses[/URL] (read the answer)
CREDITS​
ZTE of course for the Axon 7
Google for Android
 @Unjustified Dev for being the reason why there is any development in the first place
 @Koush for Universal ADB Drivers
 @Dees_Troy and @jcadduono for TWRP
Xiaomi for MiFlash
 @jcadduono for MiFlash method and A2017U packages
 @djkuz for A2017 and A2017G MiFlash packages
 @Chainfire for SuperSU
 @WugFresh for his awesome Nexus Root Toolkit and inspiring me to make one for the Axon 7
Anyone on Stack Overflow who helped me with batch commands
AFH for hosting setup files
Github for hosting masterlist files
Any one else who I forgot to mention (sorry)
And of course...me!
Please make sure you are aware of any bugs/issues BEFORE trying any of the toolkit options!(4th post)
XDA:DevDB Information
Axon7Toolkit, Tool/Utility for the ZTE Axon 7
Contributors
bkores
Version Information
Status: Stable
Current Stable Version: 1.2.1
Stable Release Date: 2017-09-04
Created 2017-03-14
Last Updated 2017-10-16
FAQs and Troubleshooting
I want to switch to [insert ROM name]How?
1) Use the Install Drivers option
2) Use the ADB+Fastboot test option to test the ADB and fastboot drivers
3) Use the backup apps+data option
4) Use the bootloader unlock option
4) Download the ROM of your choice, along with gapps (such as Opengapps arm64 7.1) and anything else you want to flash. Make sure you download the universal bootloader and modem for your variant as well from the lineage thread otherwise THE ROM WILL NOT FLASH!
5) (optional) Use the Flash TWRP option.
6) Use the flash zips option to flash the ROM along with everything else
7) (optional) Use the root option.
Profit!
The adb restore apps+data option did not work on my device.
Unfortunately, this is a ROM issue as some ROMs have broken backup managers. There is no other way to restore the backup through the adb way, however there is a way to restore a backup on the device. This method requires an unlocked bootloader and root. It also requires a paid app.
1) Download Titanium Backup from the Play Store: [url]https://play.google.com/store/apps/details?id=com.keramidas.TitaniumBackup[/URL]
2) Download the Pro key. It costs $5.99 US but the app itself is extremely worth it (from my experience) : https://play.google.com/store/apps/details?id=com.keramidas.TitaniumBackupPro&hl=en
3) Open up the app on your device. You should get a Superuser request popup. Tap `Grant`.
4) Connect your device to your computer with the factory USB-C cable. Open a command window anywhere by holding down shift and then right clicking. Click on 'Open command window here' from the menu options.
5) Execute the following command to push the backup file to your internal storage:
Code:
C:\Axon7Development\Axon7Toolkit\adb push filepath /sdcard/
where filepath is the location and name of your backup such as C:\Axon7Development\Axon7Toolkit\backups\my-backup.ab
6) If there is no menu option in the app execute the following command to emulate a "menu" key press:
Code:
C:\Axon7Development\Axon7Toolkit\adb shell input keyevent 82
This should bring up Titanium Backup's menu options.
7) Scroll down to 'Extract from ADB backup' and select it. This will bring up a list of "Open with" options. Choose any installed file manager on your device, such as the one pre-installed with the stock ROM or a third-party file manager such as ES File Explorer.
8) Navigated to the /storage/emulated/0 directory and find your backup file and select it.
9) Restore the backup on your device.
The partition restore option did not work on my device.
Follow the instructions above but use the 'Extract from Nandroid backup' option instead.
My device is stuck on an 'Enter your password to start Android' screen.
Unfortunately this requires a factory reset.
1) Boot your device into recovery mode by pressing and holding the power and volume up buttons for 10-15 seconds.
2) Stock Recovery: Use the volume down key to go down to 'Wipe data/factory reset' and press power to select. Press the volume down key again to go down to 'Yes' and press power to select.
TWRP Recovery: Tap "Wipe" < Tap "Advanced Wipe" < Check the box next to "data" < Tap "Repair or change file system" < Tap "EXT4" < Swipe to confirm.
3) Reboot your device.
The download of a file keeps failing even though I am definitely connected to the Internet.
-There may be problems with the link or server, usually in the event of high traffic. In this case use the import option. Please let me know if this happening for longer than 24 hours so I can investigate it.
-If you are on versions 1.0.0-1.1.1 the download agent is outdated. Download and run the fix here: [url]https://drive.google.com/open?id=0B2VBJePGznYjdXNUUkY5UzFJTm8[/URL]
Can I access the source code?
No.
Changelog
v1.2.1
-New design
-Added back Driver Installation option
-Added back variant auto-detection
-Added android version auto-detection
-Fixed adb backup save location/name bug
-Remove system apps backup option for better chance of successful adb restore
-Fixed system partition restore bug
-Fixed flash zips option
-Fixed "boot failed" error
-Fixed bootloader lock brick for some users
-Fixed Android Marshmallow compatibility issues
-Other minor enhancements and bug fixes
v1.2.0
-Dropped support for Windows XP and Vista
-All drivers now installed during setup
-New popup design and system
-Revised some popups with more helpful information
-Revised and removed some notifications
-Faster launch (~15 seconds)
-Minimized use of temp files
-Completely new downloader with new UI, integrated hash verification, fixed hash mismatch bug, revised import option, and option to override hash verification
-Downgraded adb version to 1.0.36 to fix toolkit hang bug for some users
-Updated download agent (wget) to latest version
-Completely new updater with automatic installation and logging
-New simplified toolkit: removed Advanced Utilities and Driver Installation/Test
-Added emulator check on startup to prevent conflicts
-Build no longer required, just variant
-Added ADB+Fastboot Test option
-Added Flash TWRP option
-User can now set backup name and location for the backup options, default path is the toolkit's backup folder
-Fixed restore apps+data(ADB) option
-Revised miflash unlock package (it's the A2017G unlock package from the Russian forum)
-New toolkit UI
-Fixed numerous minor bugs
-Minor enhancements
-Updated MiFlash to latest version
-EDL connectivity checking and driver replacing now done by the toolkit
-Implemented more error checking
-Toolkit will launch FileDependencyChecker instead of exiting if file dependency is missing
-Fastboot and aboot images will be reflashed before bootloader lock to guarantee success
-Added A2017G B10 for restore stock option
-Added A2017U B19 for restore stock option
-Fixed bugs with restore stock option
-Fixed wipe system and data loop bug for flash zip option
-Fixed toolkit crashing when choosing file with spaces or special characters in path or name for import
-Zips no longer need to be imported for flash zip option, the toolkit can now use the original path
-Cache and dalvik now wiped automatically for all zip flashing
-Added limit download rate for downloader to settings
-Added view most recent update log to settings
-New uninstaller
v1.1.1
-FULL SUPPORT FOR A2017G! This means if you are on the G variant you can now UNLOCK YOUR BOOTLOADER and (in the future) RESTORE TO STOCK!
-Miscellaneous bug fixes
-Fixed "hashcheck mismatch" bug when importing a file dependency
-Added FAQs & Troubleshooting option
-Option to auto-detect device variant/build on startup
-Minor improvements to UI and options
-NEW ADVANCED OPTION! Bugreport generator
-Added options to filter log output by verbose, debug, info, warning, error, fatal or silent for Logcat generator
-Fixed unable to uninstall toolkit from Settings
-System write protection is now automatically disabled for root option
-Fixed incorrect canceling of download dependencies when inputting cancel option after failed download or hashcheck mismatch
v1.1.0
-Added support for B19_N
-Full support for A2017! This means those of you with the Chinese variant can now unlock your bootloader and restore to stock B13! (Set your build to "Any A2017")
-Option to choose "Any" build for A2017G variants or unsupported builds
-Fixed inability to change theme and build in settings
-THE MIFLASH ISSUE IS COMPLETELY FIXED! THIS MEANS THAT THOSE OF YOU HAVING TROUBLE USING MIFLASH FOR THE BOOTLOADER UNLOCK AND RESTORE TO STOCK OPTIONS THEY WILL NOW WORK!!!
-Option to skip ADB check for bootloader unlock & restore to stock options if your device is already in EDL mode
-Cache and dalvik will now be wiped automatically when flashing zips
-Removed all powershell commands for better compatibility
-Added option to wipe system and data before flashing a Custom ROM zip
-NEW OPTION! Support for twrp adb backups and restore in TWRP 3.1.0
-Changed the "Flash TWRP and/or root" option to just "root". If you want to flash TWRP permanently, use the fastboot flash recovery option in Advanced Utilities
-minor enhancements to UI and options
-B29 added as restore stock option along with B15_N with @jcaudanno's MiFlash package and @DrakenFX's TWRP package for A2017U
-Screenshots and screen recordings are now pulled from device to PC
-Added rotate 90 degrees and verbose logging options for screen record
-Option to backup system and shared storage applications for adb backup
-Downgraded ADB version to 1.0.31 and revised syntax to fix adb backup issues
-completely new ADB check method to prevent false "device connected" for instances when device is not actually connected
-Downloader will now launch the AFH download page of all dependencies instead of the direct download link for failed file dependency
downloads in case the direct download link is no longer working
-Updater will now launch the AFH download page for all toolkit versions if downloading of the update package fails
-List connected devices option now shows device state in addition to serial number for ADB
-NEW ADVANCED OPTION! ADB logcat
v1.0.2
-fixed syntax errors for flash zip option
v1.0.1
-fixed application closing during fastboot check for bootloader unlock option
v1.0.0
-Initial release
Bugs/Issues:
-TWRP gets stuck in loop when wiping system for flash zips option if system is mounted read-only
Thanks man. It's good to see more developers for Axon 7.
Cool, will probably check it out later. You should post up some sceenshots so we can see how it works.
Just one thought, does bootloader lock warn user to have untouched system? Lots of people lock on custom rom/modified stock for some reason.
lafester said:
Cool, will probably check it out later. You should post up some sceenshots so we can see how it works.
Just one thought, does bootloader lock warn user to have untouched system? Lots of people lock on custom rom/modified stock for some reason.
Click to expand...
Click to collapse
Yep. You'll get a popup that says you have to be complete stock to use it otherwise you'll be hard bricked.
I kinda wish we'd scrap all of the unlock and recover methods and just have all of the devs making threads to just resort to a Wugfresh tool like this. Any way to make unlock/locking/restoring/recovering hands off and safe would really help a lot of us out.
We could implement a bunch of backing up, signature verifications, and delays before steps occur so it's more foolproof and not have to rely on timing of key combinations and picking which file to use for whatever.
Here are some screenshots i just took. Thanks for your work on this, bkores.
http://imgur.com/a/qS4Ib
sm.bxsq said:
Here are some screenshots i just took. Thanks for your work on this, bkores.
http://imgur.com/a/qS4Ib
Click to expand...
Click to collapse
Thanks. You beat me to it lol.
Also, since you're using it please let me know of any bugs or improvements. Thanks!
Wow, nifty. Thanks, man.
Thanks for providing this to the community! Good work!
I'm planning to release a new version soon with support for adb backups in TWRP, restore to stock using TWRP, and an option to restore to B29 in edl for those who don't want B15.
Stay tuned
This does not seem to be working for me. When attempting to unlock the bootloader the application puts my phone into fastboot mode, and closes. ZTE Axon 7 factory nougat upgrade (B15). Have downloaded the MiFlash application as requested, but option 4 just places my phone into fastboot mode and then the application just exits.
Phone will now only boot to Team Win asking for a password (I didnt have a password set). Looks like my phone may be dead.
wyrethewolf said:
This does not seem to be working for me. When attempting to unlock the bootloader the application puts my phone into fastboot mode, and closes. ZTE Axon 7 factory nougat upgrade (B15). Have downloaded the MiFlash application as requested, but option 4 just places my phone into fastboot mode and then the application just exits.
Phone will now only boot to Team Win asking for a password (I didnt have a password set). Looks like my phone may be dead.
Click to expand...
Click to collapse
Hold on let me look into this.
@wyrethewolf The issue has been fixed. I'll upload the new version as soon as possible. For the time being if you are in TWRP you should be able to boot to system by pressing cancel on the decryption screen and then going to Reboot<System.
It was a tiny typo in the fastboot check which screwed up the entire script lol.
bkores said:
@wyrethewolf The issue has been fixed. I'll upload the new version as soon as possible. For the time being if you are in TWRP you should be able to boot to system by pressing cancel on the decryption screen and then going to Reboot<System.
It was a tiny typo in the fastboot check which screwed up the entire script lol.
Click to expand...
Click to collapse
Thank you, I will give this a try. Thank you for checking in on this!
New version is up! This should *hopefully* fix the application closing issue with the bootloader unlock option.
If you already have the toolkit, no need to download this one. It'll automatically be downloaded when you launch the toolkit.
Also if you get any errors of failing to close adb.exe during installation just press ignore. I've already fixed this for future releases.
@wyrethewolf tell me if the update fixed the issue. Thanks!
@bkores thanks for all you hard work

[INDEX] REDMI S2/Y2 Ultimate Collection & Guides

Welcome to REDMI S2/Y2 Ultimate Collection!
(ysl)
Template for the index by Retrial
​OFFICIAL STOCK MIUI ROM
You can check my Guides for installation.
Recovery ROM V12.0.2.0.PEFMIXM
Fastboot ROM V12.0.2.0.PEFMIXM
FIRMWARES
Redmi S2/Y2 Firmwares
Redmi S2/Y2 Vendors
CUSTOM ROMS
You can check my Guides for installation.
Based on Stock MIUI ROM
Xiaomi.eu V11.0.1.0.PEFCNXM
Most of this Custom ROMS listed are UNOFFICIAL and with a great probability that will never get updated.
Android 12/12L​
Lineage OS 19.1 (unofficial)
PixelPlusUI
LineageOS 19.1 (unofficial)
Project Elixir
AOSP 12
ArrowOS (Unofficial)
CorvusOS vS3.0 (Unofficial)
Android 11
Pixel Experience
LineageOS
crDroid Android
EvolutionX
Palladium OS
Descendant XI
Pixel Extended
Pixel Blaster
StagOS
DerpFest
RevengeOS
Superior OS
Pixel Plus UI
Styx OS
CipherOS
DotOS
KangOS
Octavi-OS
Project LegionOS
Android 10
Pixel Experience
LineageOS
HavocOS
FreakyOS
PixysOS
AncientOS
RevengeOS
ShapeShiftOS
MSM-Xtended
CUSTOM KERNELS
Linux Kernel 4.9 Source
StormBreaker EAS Kernel
Fox Kernel Project
Qwerty Kernel (Discontinued)
Revvz Kernel
CUSTOM RECOVERY
You can check my Guides for installation.
TWRP Recovery
PitchBlack Recovery
OrangeFox Recovery
Sky Hawk Recovery Project
GAPPS
Note: be sure you have selected Platform: ARM64 and the proper Android version of the ROM you are going to flash. If the ROM you want to flash include GApps, no need to download and flash any GApps at all.
Most of the GApps have also a config. file which can be used to to configure your installation the way you like. You can skip any Package that you don't want to be part of your installation. For more infos about that, read the instructions of the GApps you chose or search in Google.
NikGApps[Create your own NikGApps build -> Video Guide]
Open GApps
MindTheGapps
FlameGApps
BiTGApps
MAGISK ROOT SOLUTION
You can check my Guides for installation.
Magisk (APK)
Magisk.zip (Flashable Zip)
Uninstall.zip (Flashable Zip)
Magisk Canary (APK)
Disable Force Encryption (DFE) & Encryption
You can check my Guides to find for what is used for.
Disable Force Encryption (No Magisk Included)
Disable Force Encryption (With Magisk Included)
Encrypt Data
GOOGLE CAMERA PORTS & UNIVERSAL STOCK CAMERA UNINSTALLER & ANXCAMERA
Only works if you're installed a 64-bit Android
san1ty
Parrot043
BSG (Private Version) [XML Configs] [Video Review]
BSG (Public Version) [[/B]Video Stabilization Settings]
ANXCamera(Magisk Module - No Addon needed)
Universal Stock Camera Uninstaller(Flash it in Recovery)
Note: If you updated GcamGo from the Play Store, you will need to flash this file and manually uninstall GcamGo from the app info.
GOOGLE PLAY SYSTEM UPDATE 🛡
You can manually update Google Play System by downloading and installing Main components.
USEFUL APPS
Check the Privacy & Security section in my Guides
If for some reason you can't find/install an app on Google Play Store due country restrictions or anything, you can sideload the app from APKMirror.
Adaway: Open Source ad blocker for Android using the hosts file.[/B]
Aegis Authenticator: Aegis Authenticator is a free, secure and open source app for Android to manage your 2-step verification tokens for your online services.[/B]
BetterBatteryStats: With BetterBatteryStats you can analyse the behavior of your phone and find applications causing the phone to drain battery while it is supposed to be asleep.
Brave Browser: Open Source Privacy Browser with built-in adblock.[/B]
Bromite: Bromite is a open source Chromium fork with ad blocking and enhanced privacy.[/B]
Cryptomator: Cryptomator encrypts your data quickly and easily. Afterwards you upload them protected to your favorite cloud service.
Device Info HW: A hardware and software information app for Android devices.
FairEmail: Fully featured, open source, privacy oriented email app.[/B]
Franco Kernel Manager: Complete toolbox for all devices with a rich feature set aimed for ease of use to supercharge your kernel.[/B]
KeepassDX: KeePassDX is a free open source password manager for Android, which helps you to manage your passwords in a secure way.[/B]
MiXplorer: Fully-featured File Manager.[/B]
NetGuard: NetGuard provides simple and advanced ways to block access to the internet - no root required. Applications and addresses can individually be allowed or denied access to your Wi-Fi and/or mobile connection.
NewPipe: Open Source Youtube alternative platform without ads.[/B]
Nova Launcher 7: Nova Launcher replaces your home screen, providing you with powerful features that you will soon realize you can't live without.
Shade Launcher: Make your phone feel like home. Free, open source, no ads.[/B]
Signal: Signal is a free and open source software application, allowing users to send end-to-end encrypted group, text, picture, and audio & video messages, and have encrypted phone conversations between Signal users.
Simple Mobile Tools: A group of simple, open source Android apps without ads and unnecessary permissions, with customizable widgets.[/B]
SysLog: Open Source tool for quickly taking and sharing system logs.[/B]
Today Weather: Today Weather is a beautiful & simple-to-use weather app that provides the world's most accurate local weather forecasts.[/B]
Youtube Vanced: Vanced is a well known modded version of YouTube with many features such as adblocking, background playback and many many more.[/B]
XIAOMI TOOLS
Mi Unlock
Xiaomi Mi Flash Tool
Xiaomi ADB/Fastboot Tools
MINIMAL ADB AND FASTBOOT
Minimal ADB and Fastboot
AMD RYZEN FASTBOOT FIX
Check the AMD Ryzen Fastboot Fix Guide for the proper steps.
AMD Ryzen Fastboot Fix (Batch File .bat)
(Scroll Down to check the Guides)
​
REDMI Y2/S2 Ultimate Guides!
(ysl)
!DISCLAIMER!
Most people I know (including myself) who used my Guides and steps, did that with success many times. If you don't follow exactly the steps or you do a mistake during the process, I do not take any responsibility for any unexpected results or damage that may happen. However I am here to help if something goes wrong, just ask in the thread.​
AMD RYZEN FASTBOOT FIX
Some AMD Ryzen Systems may have problems to recognize your device in fastboot. Try the following ways:
1. Install AMD Ryzen Chipset Drivers.
2. Enable USB Debugging at device (Settings > Additional settings > Developer options > USB Debugging) and give authorization after connecting it to PC.
3. Use USB Hub.
4. Use USB Type-A 2.0.
5. Download this .bat file (unzip it) or manually create a .bat file with these lines below, and run it as an administrator, then reboot:
reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\usbflags\18D1D00D0100" /v "osvc" /t REG_BINARY /d "0000" /f​reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\usbflags\18D1D00D0100" /v "SkipContainerIdQuery" /t REG_BINARY /d "01000000" /f​reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\usbflags\18D1D00D0100" /v "SkipBOSDescriptorQuery" /t REG_BINARY /d "01000000" /f​Check the steps an another user did to make it work here.
If this doesn't help, unfortunately you have to use Intel System.
UNLOCK BOOTLOADER
Note: Some AMD Ryzen Systems may have problems to recognize your device in fastboot. [Read the AMD Fastboot Fix Guide above]
Please keep in mind by Unlocking Bootloader the device will reset and all your data will be lost. Make a backup of your data first to PC or to USB.
1. Create a Mi account on Xiaomi’s website.
2. Add a phone number to your Mi account.
3. Insert a SIM into your phone (If you haven't added already).
4. Enable developer options in Settings > About Phone by repeatedly tapping (7 times) on MIUI Version.
5. Link the device to your Mi account in Settings > Additional settings > Developer options > Mi Unlock status. Also enable USB Debugging.
6. Download the Mi Unlock app (Windows is required to run the app).
7. Run the Mi Unlock app and follow the instructions provided by the app.
8. Reboot your device into Fastboot mode. For that simply turn off your device, press the Power Button + Volume Down (–) button at the same time. Then connect the device to the Windows PC/laptop via a micro USB cable.
9. After device and Mi account are successfully verified, the Bootloader should be Unlocked and your device will restart by itself.
INSTALL CUSTOM RECOVERY
Fastboot Method (No Custom Recovery currently installed)
Note: Some AMD Ryzen Systems may have problems to recognize your device in fastboot. [Read the AMD Fastboot Fix Guide above]
1. Make sure your Bootloader is Unlocked.
2. Enable developer options in Settings > About Phone by repeatedly tapping (7 times) on MIUI Version.
3. Enable USB Debugging in Settings > Additional settings > Developer options > USB Debugging.
4. Download a custom recovery of your choice. [You can find a recovery of your choice in my Collection]
5. Download the portable Minimal ADB and Fastboot and run adb.exe
6. Reboot to Fastboot mode by pressing Power Button + Volume Down (–) and keep holding both buttons until the word “FASTBOOT” appears on the screen, then release.
7. Once the device is in Fastboot mode, connect your device to PC and verify you can find it by typying in adb: fastboot devices.
8. Flash Recovery by typing in adb: fastboot flash recovery <recovery_filename>.img (The file may not be named identically to what stands in this command, so adjust accordingly).
9. Reboot to Recovery by typing in adb: reboot recovery or manually hold Power Button + Volume Up (+) until you boot to Recovery.
10. Done! You now have a new Custom Recovery installed.
Recovery Method (Custom Recovery already installed)
1. Download a custom recovery of your choice. [You can find a recovery of your choice in my Collection]
2. Reboot to Recovery by holding Power Button + Volume Up (+).
3. Press Install Image.
4. Locate the recovery.img you recently downloaded.
5. Select it and choose the option Recovery and Flash.
6. Go back and Reboot to Recovery.
7. Done! Your new recovery should be installed.
MAGISK ROOT SOLUTION
The easiest way to root your device is via Magisk, it should work in all ROMs, Stock and Customs.
Install Magisk:
1. Install latest TWRP Recovery. [Read the Install Custom Recovery Guide above]​2. Download the Magisk [You can find it in my Collection]​3. Reboot to TWRP Recovery by pressing Power Button + Volume Up (+) and flash it.​4. Reboot and check whether the Magisk app is installed. If it isn’t installed automatically, manually install the APK. [You can find it in my Collection]​Note: From Official TWRP Recovery 3.5.1 and onwards (and other recoveries based on that), Magisk.apk can be flashed as apk without the need of rename it to .zip. So you can simply flash the Magisk.apk in TWRP.​Manually Creation of Flashable Zip:​Download the latest Magisk APK and rename the Magisk.apk → Magisk.zip.​
Uninstall Magisk:
Flash the Uninstall.zip in TWRP Recovery and reboot. [You can find it my Collection]
If Magisk App isn’t uninstalled automatically, manually uninstall the app.
Manually creation of Flashable Uninstall Zip:
Download the latest Magisk APK and rename the Magisk.apk → uninstall.zip
Uninstall Magisk directly through the Magisk app. Simply press the Uninstall button.
DISABLE FORCE ENCRYPTION (DFE) & Encryption
[You can find it in my Collection]
Disable Force Encryption
Disable Force Encryption (a.k.a DFE) is flashed during installation of a custom ROM to avoid the system encrypting /data partition when the devices boot for the first time.​Some ROMs are not encrypted by default and so is not necessary to flash DFE. However if your ROM comes with encryption by default you can always flash DFE after clean installation of ROM and always after every update or flash or you can use any custom recovery like OrangeFox, Pitchblack, Skyhawk Recovery Project which can automatic flash DFE after every flash.​I don't recommended to use DFE if you don't switch ROMs frequently and you are casual user. Beside the fact that if you lose your device your data are not protected, many people get in confusion while doing OTA or manually updates, which if the ROM is encrypted by default and flashed DFE and in next update you forget to flash DFE you will lock out from your data and you wil get into bootloop (use custom recoveries mentioned above to avoid that).​​
Encryption
Warning - This works only on clean flash:
1. Flash ROM.zip in recovery
2. Mount vendor partition in recovery (for some reason does not mounting with newer TWRP).
3. Flash encrypt.zip.
4. Reboot to system.
Note:
The encrypt zip needs to be flashed after every update.
So flash ROM.zip and follow with encrypt zip.
Encrypted ROMs are recommended if you are stable and casual user of a ROM. Encryption have the benefit to protect your data, in case you lose your device for example. ​Always use the latest TWRP Recovery so you can be able to decrypt the data by filling the same lock screen password you have set in ROM.​Some ROMs are not encrypted by default but devs provide an Encryption.zip (script) which can encrypt the ROM. Same as DFE you need to flash it after clean installation of ROM and always after every update to stay encrypted and not get into bootloop. Unfortunatly there is not any custom recovery automatic doing that like with DFE, so you must be careful, avoid doing OTA updates and flash it every time you manually update a ROM.​
BATTERY TIPS
Advanced Guide
Simple Battery & Charging Tips
Improve your SOT
Battery Calibration
Steps:
1. Discharge your phone fully until it turns itself off.
2. Turn it on again and let it turn itself off.
3. Plug your phone into a charger and, without turning it on, let it charge until the on-screen or LED indicator says 100 percent.
4. Turn your phone on. It's likely that the battery indicator won't say 100 percent, so plug the charger back in (leave your phone on) and continue charging until it says 100 percent on-screen as well.
5. Unplug your phone and restart it. If it doesn't say 100 percent, plug the charger back in until it says 100 percent on screen.
6. Repeat this cycle until it says 100 percent (or as close as you think it's going to get) when you start it up without it being plugged in.
Overheating
Following reasons will lead to device heating issue:
During the initial setup after purchase or when restoring data.
Downloading large files.
Using apps that require more power or using apps for extended periods such as:
Playing high-quality games for long time.
Recording videos for extended periods.
Streaming videos while using the maximum brightness setting.
Using the Screen Mirroring / Smart View feature (connecting mobile to a TV).
While multitasking or when running many apps in the background i.e:
Using Multi window.
Updating or installing apps while recording videos.
Downloading large files during a video call.
Recording videos while using a navigation app.
Large amount of data for syncing with the cloud, email, or other accounts.
Exposing device under sunlight when temperature is high around you.
Extensive usage of mobile hotspot and tethering feature.
Using device in areas with weak signals or no reception or in roaming network.
Charging the battery with a damaged / unapproved USB cable.
Device's multipurpose jack is damaged or exposed to foreign materials, such as liquid, dust, metal powder, and pencil lead.
Solution:
Turn off Wi-fi, GPS , bluetooth and other connectivity options when not in use by dragging the notification panel.
Decrease screen brightness.
Close background running applications.
Too many applications installed in device may result in device heating since their corresponding process will keep on running in background. It is advised to uninstall un-necessary apps if not using them.
Avoid using apps like GPS, data dependent apps or graphic intensive games for longer duration since they require more energy to function, causing device to heat.
It is advised not to use device while charging as it may cause the device to over heat.
General:
DO:
Use manual brightness or dim the screen.
Turn off notifications for apps you don't use. Better still, delete/disable the apps entirely if you don't need them.
Enable battery or power saving mode when you want to extend your battery life.
Use the power adapter that came with your phone. Other chargers can charge slowly/faster but they can also damage your phone or battery.
Turn off bluetooth, location tracking, and Wi-Fi (unless you are actively using it)
Turn off print services from bluetooth connection preferences.
Avoid extremes of heat and cold. If your phone gets very hot or cold it can strain the battery and shorten it's lifespan.
DON'T:
Have Bluetooth or Wi-Fi turned on constantly.
Leave apps running in the background. Instead restrict background usage off apps that you don't need running.
Push email means your device is always listening for new email which drains alot of battery.
Drain your phone battery all the way to 0% or charging it all the way to 100%. Keep it between 20% - 90% for longer battery lifespan.
The more advanced the graphics and animations are (games, videos, photos, animations), the harder the processor and graphics chip in your smartphone have to work. More activity means more battery use.
PRIVACY & SECURITY
Some useful links:
All about Privacy & Security at PrivacyTools.
Electronic Frontier Foundation
Check if your email address is in a data breach at Firefox Monitor & at Have I been Pwned
Test your browser to see how well you are protected from tracking and fingerprinting at Cover Your Tracks by EFF.
Ad Block Tester is a free service on the Internet to evaluate content blocking solutions. It is not designed to be a benchmark, but it reveals the level of blocking against a set of hosts that are very popular.
Check on AM I FLoCed? by EFF if your your Chrome browser has been turned into a guinea pig for Federated Learning of Cohorts or FLoC, Google’s latest targeted advertising experiment.
How to block ads on Android.
General:
Always prefer Open Source or well popular Programs, Apps, ROMs, Kernels & Stuff.
Open Source doesn't mean it's 100% safe but it's unlikely to have something suspicious, since you and other users can check the code in GitHub or in any other code hosting platform the "stuff" is hosted.
Prefer ROMs & Kernels with SELinux Enforcing. You can find informations here.
Always download and install Apps, Programs, ROMs & Stuff from official sources and do not use redirection links from different sites. Google is your friend to find the official source of the stuff you want.
Always check the permissions an app requires, before download and install it to your device. If an app ask for permissions which has nothing to do with the app functionality then it's should be reconsider or ask the developer why these permissions needed.
If you want to avoid Google and Play Store (De-Google), you can choose a ROM without GApps preinstalled like LineageOS and use F-Droid client which is an installable catalogue of FOSS (Free and Open Source Software) applications for the Android platform. The client makes it easy to browse, install, and keep track of updates on your device. Note that not all apps from Play Store will be available in F-Droid. Only Open Source projects. You can find alternatives though.
Alternative you can use LineageOS for microG or any ROM which support signature spoofing and can support microG.
For Windows use the default Windows Defender & Malwarebytes to scan your files whenever you want (Prefered before open or install them). Also use the addon/extension uBlock Origin in your Browser. These should be enough for normal users.
For Android Do not use any antivirus - antimalware since it's useless, just check what apps and from where you installing.
Always verify the source of addons/extensions in your browser. Avoid installing random and unpopular addons/extensions. Keep it minimal and clean, so browser can be fast and safe, no need bunch of extensions.
If you are using VPN, always check the terms and rules of the provider. Avoid random VPN Services.
Recommended VPN Services.
Using a VPN will not keep your browsing habits anonymous, nor will it add additional security to non-secure (HTTP) traffic.
Recommended is to encrypt your data/files always before uploading them to cloud with tools like Cryptomator.
Always use unique and strong passwords for each of your accounts.
Use awarded open source Password Managers like KeePass or KeePassXC for Desktop and KeePassDX for Android to manage your passwords and have them with you safe, encrypted and secure. Must be noted you can use the same database file between these programs.
Always enable 2 Step Authentication wherever is available for your accounts.
You can use apps like Aegis Authenticator.
Do not open or click on links attached in unknown emails you may get. Always check the adress of the email and verify it's legit from the official source.
Create and use "burned" email for accounts/sites you have concerns but you definitely want to try them. Do not use your personal or business email.
CLEAN INSTALL CUSTOM ROM
You can also do the same steps below to install Stock MIUI Recovery ROM.
1. Backup all your data to PC or to external SDCard. [All your data into Internal Storage will be lost on step 7 while Formating Data or Wiping Internal Storage]
2. Unlock Bootloader. [Read the Unlock Bootloader Guide above]
3. Download: [You can find everything in my Collection]
Custom Recovery of your choice.
Custom ROM of your choice
GApps (be sure you have selected Platform: ARMx64 and the proper Android version of the ROM you are going to flash) if the ROM you are going to flash does not include. [Optional]
Magisk Root Solution [Optional]
Disable Force Encryption [Optional]
4. Move all these files in one folder to your Internal Storage or to External SDCard if you have.
5. Install Custom Recovery. [Read the Install Custom Recovery Guide above]
6. Reboot to Recovery Power Button + Volume Up (+)
7. Installation:
Steps without external SDCard:
Select Wipe > Advanced Wipe
Select Dalvik / ART Cache, System, Data, Vendor, Cache and then Swipe to Wipe.
Flash ROM > GApps [Optional] > Magisk [Optional] > DFE [Optional - Not Recommended]
Go back and select Wipe > Format Data > type yes [All your data into Internal Storage will be lost]
Reboot Enjoy!
Steps with external SDCard:
go to Advanced > File Manager > External_SD and delete all folders in ur ext sd card (For example you should delete: Android, .android_secure, LOST.DIR, DCIM, etc) except your personal files/folders and the folder with your custom ROM/Gapps/Magisk/DFE you want to flash.
Each app on your phone with the WRITE_EXTERNAL_STORAGE permission may create files or folders in ur sdcard. Most of these folders have once been created by one of these apps and many of them may be deleted with a few exceptions (e.g. Android, .data, .android_secure, these contain important system or app data like a game's downloaded content):
.android_secure: apps installed and then moved to sdcard
Android: app data/cache
data: app data
.estrongs: ES file manager
LOST.DIR: sort of trash folder (collects recovered files after phone crashes)
DCIM: phone gallery's photos and previews
OTA-update: Over The Air update service
ppy_cross: an unknown third-party app's data.
So I recommend to delete them so you can put your phone/sdcard in a clean state and is guaranteed to be able to re-create these folders.
Select Advanced Wipe
Select Dalvik / ART Cache, System, Data, Internal Storage, Vendor, Cache and then Swipe to Wipe. [All your data into Internal Storage will be lost]
Flash ROM > GApps [Optional] > Magisk [Optional] > DFE [Optional - Not Recommended]
Go back and select Wipe > Format Data > type yes [All your data into Internal Storage will be lost]
Reboot Enjoy!
DIRTY INSTALL YOUR CUSTOM ROM
Note: Before you start flashing, keep in mind the ROM you dirty flashing MUST be the same with the one you have already installed.
1. Make a full nandroid backup, just in case something goes wrong. You can use TWRP to do that. (TWRP > Backup > Select everything) [Optional]
2. Remove all Magisk modules. [Optional]
3. Reboot to TWRP and Wipe Dalvik / ART Cache, System, Vendor, Cache.
4. Flash the ROM > GApps [Optional] > Magisk [Optional] > DFE [Optional - Not Recommended]
5. Reboot and Enjoy!
I've skipped some explanations, because if you are going to dirty flash, you already know for example how to boot to TWRP.
CLEAN INSTALL OFFICIAL STOCK MIUI ROM & RELOCK BOOTLOADER
Note: Some AMD Ryzen Systems may have problems to recognize your device in fastboot. [Read the AMD Fastboot Fix Guide above]
1. Download the official Fastboot ROM and unzip it to your PC. [You can find it in my Collection]
2. Download Xiaomi Mi Flash Tool and run XiaomiMiFlash.exe
3. Turn off you device and then boot in Fastboot mode by pressing Power Button + Volume Down (–) and keep holding both buttons until the word “FASTBOOT” appears on the screen, then release.
4. Connect your device to PC via USB Cable.
5. On the Xiaomi Mi Flash Tool, Click on Select and browse to the folder where you have Unzip the downloaded ROM file then press OK.
6. Click on Refresh button and you will see that your device connected to port com.
7. Select what method you prefer:
Clean All: The process will flash full Fastboot ROM and will wipe everything (include user data) but Bootloader will remain unlocked.
Save User Data: The process will flash Fastboot ROM without wiping user data.
Clean All and Lock: The process will flash full Fastboot ROM and will wipe everything (include user data) but Bootloader will be relocked
8. Now click on the Flash button to begin the flashing progress.
9. Once your ROM is successfully flashed, you’ll see green bar inside XiaomiMiFlashtool.
FIX FOR STUCK ON OREO FIRMWARE (SOFTBRICKED)
FIX (Read Carefully)
New Update: 12/11/2021
Changelog:
Adding the Android 12 roms
Updating links
Minor text fixes
New Update: 23/07/2021
Changelog:
Initial Release
Links to Custom ROM is broken ???

Development ***CLOSED*** [ROM] Project Unbound V1.1 [G99xB]-[DVL3]-[OneUI5.0]

PROJECT UNBOUND
Hello XDA Community, I present the newest project for the Galaxy S21 series...Project Unbound.​
POLITE NOTICE: I AM NOT RESPONSIBLE FOR ANYTHING THAT HAPPENS TO YOUR DEVICE; IT IS YOUR CHOICE AND RESPONSIBILITY FOR WHAT YOU DO. IF YOU COME TO ME AND COMPLAIN, I WILL LAUGH AT YOU.
Spoiler: View Unbound Information
Spoiler: Supported Devices
SM-G991B
SM-G996B
SM-G998B
Spoiler: Base
G998BXXS5DVL3
Spoiler: View Unbound Features
Spoiler: View Kernel Information
This ROM currently uses the Unbound Kernel
The original clean source of the Kernel used in this Project can be found here.
The Unbound modified kernel source code is private.
Spoiler: View CSC Information
Spoiler: View selectable CSC Features
Call Recording
Shutter Sound Menu
Real-time Network speed
App Lock support
Anti-Phishing support in Samsung Messages
Anti Malware feature disabled in Device Care
Colour of Days in the Calendar app.
Camera enabled during calls.
Recent App protection
The default homepage in Samsung Internet is set to this
Knox Guard support is disabled.
Enhanced Image Quality.
eSIM support.
Spoiler: View CSC Base
G998BOXM5DVL3
Spoiler: View ROM Features
Spoiler: Settings/Services & other Features
Knox disabled
Disabled file encryption
Disabled process authentication
Disabled VaultKeeper
Disabled SCS
Disabled esecos daemon
Disabled AVB
Loads of additional camera features
Loads of additional Single Take features
Full OneUI 5.0 experience
Fully enabled screenshots in secure apps (Including DRM-protected apps). Thanks @edzamber
Disabled Watchdog, thanks @ananjaser1211
Official Status in Settings
Unbound Information & Banner in Software information
Spoiler: Aroma Features
A new menu containing many additional selectable features exclusive to UnboundROM.
Integrated ROM control into the installation.
Wipe Options (Dirty Flash or Clean Flash)
CSC Features (Add a range of CSC features during the installation)
Boot Animation options (Choose to either stay stock or apply our V2 animation)
Embedded Magisk Installation (Optional to choose Magisk Canary, Magisk Alpha, or stay Unrooted)
Hosts options (AdAway installation, with the ability to backup & restore your previous hosts file)
Spoiler: Generic fixes
Galaxy Watch Pairing
64MP Super Resolution (On G991B & G996B)
SafetyNet (must use kdrag0n's module)
Private Share
Secure WiFi
Spoiler: Misc Tweaks & Mods
Custom Boot logos for each device, thanks @dutchman89
Unbound boot animation by @dutchman89
A large number of prop tweaks for battery, data, performance, and Dalvik
Netflix fix (HD is now fixed)
Frame buffer increased to help with gaming
Spoiler: The Bug list
RED = The Bug needs logs.
ORANGE = The Bug has been reported, and the error has been found; a fix is expected in a future release.
GREEN = A fix file has been provided for this bug and will be implemented in the next available rom release.
Spoiler: View Installation Information
Spoiler: Stock ROM to UnboundROM
NOTICE: The steps below will trip Knox & possibly void your Warranty; following these steps will perform a mandatory data wipe due to Bootloader status changes, so please make sure you back up any/all of your important files somewhere else other than your phone's storage.
STEP 1: UNLOCKING THE BOOTLOADER:​
1. Enable Developer Options; you can do this by going to Settings -> About Phone -> Software Information -> Tap "Build Number" 7 times and enter your phone's pin if prompted.
2. Open Developer Options and enable the "Allow OEM Unlocking" option.
3. Shut down your phone.
4. Connect your phone to your PC or connect your headphones to boot into Download Mode with the combination (HOLD VOLUME UP + VOLUME DOWN)
5. Press and hold the volume up button (Bootloader unlock screen)
6. Once on the bootloader unlock screen, press the volume up button to confirm the unlock (WARNING: This action will perform a factory reset, and the phone may restart once or twice (this is normal), you will soon boot back into the Setup wizard, skip this initial setup there is no need to login to anything.)
7. Enable Developer options again (Follow Step 1) and check that the OEM toggle is enabled & greyed out.
8. Congratulations, you have unlocked the Bootloader and are ready to continue to the next step.
STEP 2: FLASHING TWRP + PATCHED VBMETA:​1. Download TWRP for your device.
2. Boot your phone into Download Mode.
3. Single press Volume Up to start ODIN Mode
4. Load ODIN on your PC.
5. Go to options and untick "Auto Reboot"
6. Select the (USERDATA) slot and select the downloaded file from Step 1.
7. Click start on ODIN and wait for it to finish.
8. Upon a pass, keep the phone connected to your PC or headphones, then hold the Power button + Volume down button; as soon as the screen goes black, hold the Power button and Volume UP button.
9. You should now be in TWRP.
STEP 3: INITIAL TWRP STEPS:​1. Do a complete data wipe (Wipe -> Format Data -> Type "yes")
2. Reboot back into RECOVERY (Reboot -> Recovery)
3. Download the latest Unbound release and copy it to your phone (PC to Phone) or a USB OTG device, or if you have SD Card, you could store it on that.
STEP 4: INSTALLING UNBOUNDROM:​1. In TWRP, click "Install" if using a USB OTG device, press "Select storage", and press "USB OTG" or "SD Card" if using an SD Card.
2. Browse to the location you stored the ROM zip.
3. Swipe to confirm the flash.
4. Follow the on-screen instructions, select your desired features, and wait for the ROM to install.
5. When the ROM has finished installing, press "Save Logs" to send to the Developer if you bump into any issues.
6. Reboot into the System.
7. Do the setup wizard as usual.
8. Congratulations, you have successfully installed UnboundROM and are good to go! Enjoy!
Spoiler: Other ROM to UnboundROM
CLEAN FLASH (RECOMMENDED)​
1. Boot into TWRP
2. Load UnboundROM zip
3. In Wipe Options, select "Clean Install"
4. Follow the on-screen instructions, and wait for UnboundROM to be installed.
5. Boot into the system.
DIRTY FLASH (NOT RECOMMENDED)
A dirty flash may or may not work, as we cannot guarantee that flashing UnboundROM over the top of another ROM will cause any issues. So, therefore, we do not recommend it, but of course, it is your device and your responsibility, so please feel free to make your own choice here but do not come to our chats and complain about issues caused by a dirty flash over another custom ROM.​
Spoiler: Unbound version update (V1.1 to V1.2 etc)
When updating versions of Unbound, it is very dependent on what version you are currently running and the version you want to update to, an example being if you are on V1.0 and want to update to V1.1, a dirty flash would be fine unless stated in the OP otherwise.
However, if you say you are upgrading the OS version, i.e. OneUI 3 to OneUI 4, you would need to update your device to the latest firmware first via SamFirm/Frija/hadesFirm etc.​
Please take note of the changelogs of each version as they will state the requirements to update and if a clean flash will be required or not.
When a dirty flash is impossible, and you need to update your device to the latest/specified firmware, please follow the recommended steps below. These steps will assume you are already running UnboundROM:
1. Download the latest/required firmware using either samFirm, Frija or hadesFirm
2. Unzip the firmware zip and remove the .md5 from the end of each file name.
3. Boot your phone into download mode, load Odin, turn off Auto reboot options, and load the files into the relevant slots. ( BL = BL, AP = AP, CP = CP, CSC = HOME_CSC) (IT IS IMPORTANT TO USE "HOME_CSC" TO KEEP YOUR DATA INTACT)
4. Press start, and wait for it to complete.
5. When complete, keeping the phone connected to the PC, boot your phone into TWRP, and load the latest/downloaded rom.zip
6. Follow the on-screen instructions and wait for the ROM to be installed.
7. When the installation is complete, press the "Save Log" button in case of any issues.
8. Congratulations, you have successfully updated your version of UnboundROM. Boot to the system and enjoy!
Spoiler: View Changelogs
Spoiler: V1.1
Removed the Christmas Theme
Added the Unbound Kernel
Spoiler: V1.0 - Christmas Edition
The Unbound Christmas Theme has been applied.
The Christmas theme includes a new boot animation, new logos and new boot logos.
Spoiler: V1.0
Initial release for G99X
Spoiler: Useful Links
Telegram links removed by moderator
Discord links removed by moderator
GitHub link removed by moderator
PayPal link removed by moderator
Download links removed by moderator
Spoiler: Unbound Credits
Dutchman89 - Boot Animation, custom boot logos, and other branding logos. Thanks a ton.
Anan1211 - Endless help throughout the years
corsicanu - Endless help throughout the years & official TWRP
Topjohnwu - Magisk Developer
Nathan - Aroma colouring
Samsung - Base Firmware
Andrei - Help & Support
All of the Unbound testers team
If I missed your name and you feel you should be credited, please DM me on Telegram with why you should be credited.
**Reserved**
Reserved
Reserved
Reserved
Yaay!!
Downloading right away!
Edit: I'm back to BeyondRom. Thanks for your effort though.
I have to be on android 13 to install this rom right?
fedex_742 said:
I have to be on android 13 to install this rom right?
Click to expand...
Click to collapse
Yes.
Hello there,
I installed your rom (clean install obviously) but i can't use it. For me there are a lot of issue, no gestures, when i pull down notification bar i can't change or add or remove toggles, there isn't a magnifying glass to look for in settings, i can't return in twrp from system. I'm sorry but or i wrong something or there are these issues, and it's difficult that i wrong something.
See you to next build
It happens that doing a clean installation, I can practically not use the phone and the power off button does not respond. The rom promises.
So this isn't a flushable rom? No success stories?
Issues have been addressed, there were some errors in the aroma, causing setup apps to be debloated no matter what was ticked.
Will wait for the custom kernel
Very good and intuitive STEP by STEP instructions for installation. Well done!
Heavily looking forward to the KERNEL release!
LeeXDA18 said:
View attachment 5768703
PROJECT UNBOUND
Hello XDA Community, I present the newest project for the Galaxy S21 series...Project Unbound.​
POLITE NOTICE: I AM NOT RESPONSIBLE FOR ANYTHING THAT HAPPENS TO YOUR DEVICE; IT IS YOUR CHOICE AND RESPONSIBILITY FOR WHAT YOU DO. IF YOU COME TO ME AND COMPLAIN, I WILL LAUGH AT YOU.
Spoiler: View Unbound Information
Spoiler: Supported Devices
SM-G991B
SM-G996B
SM-G998B
Spoiler: Base
G998BXXSDVK1
Spoiler: View Unbound Features
Spoiler: View Kernel Information
This ROM currently uses the stock Samsung kernel, but a custom Unbound Kernel is planned for a future release.
The source of the Kernel used in this Project can be found here.
Spoiler: View CSC Information
Spoiler: View selectable CSC Features
Call Recording
Shutter Sound Menu
Real-time Network speed
App Lock support
Anti-Phishing support in Samsung Messages
Anti Malware feature disabled in Device Care
Colour of Days in the Calendar app.
Camera enabled during calls.
Recent App protection
The default homepage in Samsung Internet is set to this
Knox Guard support is disabled.
Enhanced Image Quality.
eSIM support.
Spoiler: View CSC Base
G998BOXM5DVJC
Spoiler: View ROM Features
Spoiler: Settings/Services & other Features
Knox disabled
Disabled file encryption
Disabled process authentication
Disabled VaultKeeper
Disabled SCS
Disabled esecos daemon
Disabled AVB
Loads of additional camera features
Loads of additional Single Take features
Full OneUI 5.0 experience
Fully enabled screenshots in secure apps (Including DRM-protected apps). Thanks @edzamber
Disabled Watchdog, thanks @ananjaser1211
Official Status in Settings
Unbound Information & Banner in Software information
Spoiler: Aroma Features
A new menu containing many additional selectable features exclusive to UnboundROM.
Integrated ROM control into the installation.
Wipe Options (Dirty Flash or Clean Flash)
CSC Features (Add a range of CSC features during the installation)
Boot Animation options (Choose to either stay stock or apply our V2 animation)
Embedded Magisk Installation (Optional to choose Magisk Canary, Magisk Alpha, or stay Unrooted)
Hosts options (AdAway installation, with the ability to backup & restore your previous hosts file)
Spoiler: Generic fixes
Galaxy Watch Pairing
64MP Super Resolution (On G991B & G996B)
SafetyNet (must use kdrag0n's module)
Private Share
Secure WiFi
Spoiler: Misc Tweaks & Mods
Custom Boot logos for each device, thanks @dutchman89
Unbound boot animation by @dutchman89
A large number of prop tweaks for battery, data, performance, and Dalvik
Netflix fix (HD is now fixed)
Frame buffer increased to help with gaming
Spoiler: The Bug list
RED = The Bug needs logs.
ORANGE = The Bug has been reported, and the error has been found; a fix is expected in a future release.
GREEN = A fix file has been provided for this bug and will be implemented in the next available rom release.
Spoiler: View Installation Information
Spoiler: Stock ROM to UnboundROM
NOTICE: The steps below will trip Knox & possibly void your Warranty; following these steps will perform a mandatory data wipe due to Bootloader status changes, so please make sure you back up any/all of your important files somewhere else other than your phone's storage.
STEP 1: UNLOCKING THE BOOTLOADER:​
1. Enable Developer Options; you can do this by going to Settings -> About Phone -> Software Information -> Tap "Build Number" 7 times and enter your phone's pin if prompted.
2. Open Developer Options and enable the "Allow OEM Unlocking" option.
3. Shut down your phone.
4. Connect your phone to your PC or connect your headphones to boot into Download Mode with the combination (HOLD VOLUME UP + VOLUME DOWN)
5. Press and hold the volume up button (Bootloader unlock screen)
6. Once on the bootloader unlock screen, press the volume up button to confirm the unlock (WARNING: This action will perform a factory reset, and the phone may restart once or twice (this is normal), you will soon boot back into the Setup wizard, skip this initial setup there is no need to login to anything.)
7. Enable Developer options again (Follow Step 1) and check that the OEM toggle is enabled & greyed out.
8. Congratulations, you have unlocked the Bootloader and are ready to continue to the next step.
STEP 2: FLASHING TWRP + PATCHED VBMETA:​1. Download TWRP for your device.
2. Boot your phone into Download Mode.
3. Single press Volume Up to start ODIN Mode
4. Load ODIN on your PC.
5. Go to options and untick "Auto Reboot"
6. Select the (USERDATA) slot and select the downloaded file from Step 1.
7. Click start on ODIN and wait for it to finish.
8. Upon a pass, keep the phone connected to your PC or headphones, then hold the Power button + Volume down button; as soon as the screen goes black, hold the Power button and Volume UP button.
9. You should now be in TWRP.
STEP 3: INITIAL TWRP STEPS:​1. Do a complete data wipe (Wipe -> Format Data -> Type "yes")
2. Reboot back into RECOVERY (Reboot -> Recovery)
3. Download the latest Unbound release and copy it to your phone (PC to Phone) or a USB OTG device, or if you have SD Card, you could store it on that.
STEP 4: INSTALLING UNBOUNDROM:​1. In TWRP, click "Install" if using a USB OTG device, press "Select storage", and press "USB OTG" or "SD Card" if using an SD Card.
2. Browse to the location you stored the ROM zip.
3. Swipe to confirm the flash.
4. Follow the on-screen instructions, select your desired features, and wait for the ROM to install.
5. When the ROM has finished installing, press "Save Logs" to send to the Developer if you bump into any issues.
6. Reboot into the System.
7. Do the setup wizard as usual.
8. Congratulations, you have successfully installed UnboundROM and are good to go! Enjoy!
Spoiler: Other ROM to UnboundROM
CLEAN FLASH (RECOMMENDED)​
1. Boot into TWRP
2. Load UnboundROM zip
3. In Wipe Options, select "Clean Install"
4. Follow the on-screen instructions, and wait for UnboundROM to be installed.
5. Boot into the system.
DIRTY FLASH (NOT RECOMMENDED)
A dirty flash may or may not work, as we cannot guarantee that flashing UnboundROM over the top of another ROM will cause any issues. So, therefore, we do not recommend it, but of course, it is your device and your responsibility, so please feel free to make your own choice here but do not come to our chats and complain about issues caused by a dirty flash over another custom ROM.​
Spoiler: Unbound version update (V1.1 to V1.2 etc)
When updating versions of Unbound, it is very dependent on what version you are currently running and the version you want to update to, an example being if you are on V1.0 and want to update to V1.1, a dirty flash would be fine unless stated in the OP otherwise.
However, if you say you are upgrading the OS version, i.e. OneUI 3 to OneUI 4, you would need to update your device to the latest firmware first via SamFirm/Frija/hadesFirm etc.​
Please take note of the changelogs of each version as they will state the requirements to update and if a clean flash will be required or not.
When a dirty flash is impossible, and you need to update your device to the latest/specified firmware, please follow the recommended steps below. These steps will assume you are already running UnboundROM:
1. Download the latest/required firmware using either samFirm, Frija or hadesFirm
2. Unzip the firmware zip and remove the .md5 from the end of each file name.
3. Boot your phone into download mode, load Odin, turn off Auto reboot options, and load the files into the relevant slots. ( BL = BL, AP = AP, CP = CP, CSC = HOME_CSC) (IT IS IMPORTANT TO USE "HOME_CSC" TO KEEP YOUR DATA INTACT)
4. Press start, and wait for it to complete.
5. When complete, keeping the phone connected to the PC, boot your phone into TWRP, and load the latest/downloaded rom.zip
6. Follow the on-screen instructions and wait for the ROM to be installed.
7. When the installation is complete, press the "Save Log" button in case of any issues.
8. Congratulations, you have successfully updated your version of UnboundROM. Boot to the system and enjoy!
Spoiler: View Changelogs
Spoiler: V1.0 - Christmas Edition
The Unbound Christmas Theme has been applied.
The Christmas theme includes a new boot animation, new logos and new boot logos.
Spoiler: V1.0
Initial release for G99X
Spoiler: Useful Links
Spoiler: Telegram
The leading chat link is here.
The unbound news channel is here.
Spoiler: Discord
The main Discord server link is here.
Spoiler: GitHub
The Unbound Hub link is here.
Spoiler: PayPal
If you appreciate & like my work, you can support me here.
Spoiler: Downloads Section
Spoiler: ROM
Unbound V1.0 Christmas Edition - Google Drive
MD5 = 5e5f614e4ee3bdbc24d8e7b90a827dd7
SHA1 = 63e45281e28d2a379f5d0d05f5f1ee10d75b0cb1
SHA256 = db7a63fdf397294700ae6973e166257fb01c0aea7600153eecbe62c4e14fcb82
CRC32 = 51b6f37e
Spoiler: Fixes
None is required for this release.
Spoiler: Unbound Credits
Dutchman89 - Boot Animation, custom boot logos, and other branding logos. Thanks a ton.
Anan1211 - Endless help throughout the years
corsicanu - Endless help throughout the years & official TWRP
Topjohnwu - Magisk Developer
Nathan - Aroma colouring
Samsung - Base Firmware
Andrei - Help & Support
All of the Unbound testers team
If I missed your name and you feel you should be credited, please DM me on Telegram with why you should be credited.
Click to expand...
Click to collapse
Brilliant, not tried the rom but love the fact you've taken the time and energy to have all the necessary details to successfully flash your rom coming from stock unrooted phone!
Newbie could follow this, will provide feedback once I've used your rom!
Brillant approach
Hello! Thank you for your work! i have a problem with aroma detecting my phone which is the G998B, says its not supported. Any workround for this? Im trying dirty flash approach.
Thanks!
EDIT: Had to reflash stock with different region to get it to work. PS: Users need to reflash twrp right after stock.
LOG:
Code:
AROMA Installer version 2.71
(c) 2013 by amarullz xda-developers
ROM Name : Project Unbound
ROM Version : v1.0 DVK1 - Christmas Edition
ROM Author : Lee
Device : G99X
Start at : Fri Nov 25 13:07:26 2022
SELinux: Skipping /product_file_contexts: empty file
SELinux: Skipping /odm_file_contexts: empty file
SELinux: Loaded file_contexts
=====================================
=====================================
Project Unbound v1.0 - Christmas Edition for G99X
@Project Unbound v1.0 - Christmas Edition for G99X
=====================================
=====================================
Galaxy S21 Exynos Series
Galaxy S21 Exynos Series
=====================================
=====================================
by Lee
by Lee
=====================================
=====================================
Checking Your Compatibility
@Checking Your Compatibility
about to run program [/system/bin/sleep] with 2 args
about to run program [/system/bin/sleep] with 2 args
script aborted: - Sorry, your device is not supported. This ROM only supports G99X devices on the latest DVK1 firmware.
- Sorry, your device is not supported. This ROM only supports G99X devices on the latest DVK1 firmware.
log error: 25
Installer Error (Status 7)
End at : Fri Nov 25 13:07:28 2022
I really want to flash this rom, however, support seems nonexistent and it sou ds like there are still issues with the aroma file.
Somehow it's funny to post questions about a rom? Gotta love the keyboard warriors, keep it up, I'm sure you are doing great things in the android community
I am away on trips at the moment, I will look into issues as soon as I can, I am nowhere near my PC.
I went a b ead and flasbed this rom and what a surprise. Tons of aroma options. 0 issues flashing. Smooth and I have seen 0 issues in 24 hours. Thanks for your work. I look forward to your kernel also.
Any update for this nice rom ??

Categories

Resources