Develop Bugs

[SAMSUNG GALAXY S3 UNIFIED TOOLKIT V9] Drivers, Backup, Root, Recovery + MORE [TMO]

INTRODUCING THE SAMSUNG GALAXY S3 UNIFIED TOOLKIT
SUPPORTED MODELS
INTERNATIONAL [GT-I9300] SUPPORT THREAD HERE
AUSTRALIAN MODEL GSM [GT-I9300T]
INTERNATIONAL [GT-I9305/GT-I9305N] SUPPORT THREAD HERE
AUSTRALIAN MODEL LTE [GT-I9305T]
C SPIRE MODEL LTE [SCH-L710]
AT&T US [SGH-I747] SUPPORT THREAD HERE
BELL, ROGERS, SASKTEL, TELUS [SGH-I747M] [SGH-I747M] USE AT&T SUPPORT THREAD
US CELLULAR MODEL LTE [SCH-R530] USE AT&T SUPPORT THREAD
METRO PCS MODEL LTE [SCH-R530M] USE AT&T SUPPORT THREAD
SPRINT US [SPH-L710] SUPPORT THREAD HERE
TMOBILE US [SGH-T999] SUPPORT THREAD HERE
MOBILICITY, VIDEOTRON, WIND [SGH-T999V] USE TMOBILE SUPPORT THREAD
VERIZON US [SCH-I535] SUPPORT THREAD HERE
CHINA ANYCALL CDMA MODEL [SCH-I939] USE GT-I9300 SUPPORT THREAD
Click to expand...
Click to collapse
The Unified Android Toolkit supports a multitude of Nexus and Samsung devices with more devices being added all the time. There is also an option at startup to run a Basic Android Toolkit which any Android device can use to install drivers, make app backups, install apk files, reboot the device into different modes and run a command prompt for manual input.
FUNCTIONS OF UNIFIED ANDROID TOOLKIT V1.3.4 [9TH JAN 2015]
* Install correct adb/fastboot drivers automatically on Windows xp/vista/7/8 32bit+64bit
* Backup/Restore a single package or all apps, user data and Internal Storage
* Backup your data from selectable folders [internal or external storage] to your PC for a Full Safe backup of data
* Unlock/Re-Lock your Bootloader [Nexus]
* Root Stock builds
* Various Root options using insecure boot image or custom recovery
* ALLINONE to Unlock, Root, Rename the Restore Files and install busybox [Nexus]
* ALLINONE to flash custom Recovery Root, Rename the Restore Files and install busybox [Samsung]
* Install BusyBox on your device
* Perform a FULL NANDROID Backup of your system (Boot, Cache, Data, Recovery and System) via adb and save in Custom Recovery format on your PC which can be Restored via CWM Recovery [if insecure boot image available]
* Fix extSdCard write permissions from installed apps in Android 4.4+ [Samsung]
* Pull /data and /system folders, compress to a .tar file and save to your PC [if insecure boot image available]
* Dump selected Device Partitions, compress to a .zip file with md5 and save to your PC [if insecure boot image available]
* Extras, Tips and Tricks section
* Auto Update ToolKit to latest available version at startup (professional only feature)
* Program up to 10 Quickpick slots and run them very quickly (professional only feature)
* Mods section to automatically perform certain tasks on your device
* Download Google Stock Image directly to correct ToolKit folder for extracting and flashing [Nexus]
* Check md5 of stock image to make sure downloaded file isn't corrupted before flashing [Nexus]
* Download Samsung Stock Firmware to PC for extracting and flashing via Odin [Samsung]
* Flash Custom Recovery or Google Stock Image to Device
* Rename the Recovery Restore File present on some Stock Roms
* Boot into CWM Touch, TWRP, Philz Touch Recovery or Stock Recovery without Flashing it [Nexus]
* Flash Custom Recovery to Device
* Boot [Nexus] or Flash .img Files directly from your PC
* Install a single apk or multiple apk's to your device
* Push Files from your PC to your device
* Pull Files from your device to your PC
* Disable forced encryption on Nexus6 and Nexus9 devices
* Install Root Checker app by Burrows Apps
* Install Backup/Restore app by MDroid Apps [calls log, sms, contacts]
* Install EFS/Partition Backup/Restore app by Wanam
* Dump selected LogCat buffers to your PC
* Dump BugReport to your PC
* Set Files Permissions on your device
* Open new Command Prompt for manual input
* Reboot device to Fastboot Mode or Android from fastboot mode [Nexus]
* Reboot device to Fastboot Mode [Nexus], Recovery, Android or Download Mode [Samsung] from adb mode
* Display Important Information about your device
--------------------------------------------------------------
SUPPORTED DEVICES AND LATEST SUPPORTED BUILDS *HERE*
DOWNLOAD THE SKIPSOFT UNIFIED ANDROID TOOLKIT *HERE* (FROM SKIPSOFT.NET)
NOTE: As the exe files are not Digitally Signed with a Microsoft Certificate they 'may' get picked up as potentially harmful by Antivirus Programs and deleted on first run. If this happens restore the file and exclude it from future scans to use it. This seems to happen mostly on AVG Free and Norton which is why I switched to BitDefender which is much better.
Credits: Chainfire for SuperSU, koush and the clockworkmod team for cwm and the universal driver pack, 1wayjonny for the adb/fastboot driver pack, Adam Lange for all his support and help with the insecure kernels.
--------------------------------------------------------------
WHAT IS THE DIFFERENCE BETWEEN PUBLIC (FREE) AND PROFESSIONAL (DONATE) VERSIONS?
THE PUBLIC VERSION OF THE TOOLKIT INCLUDES EVERYTHING YOU COULD NEED TO MANIPULATE YOUR DEVICE. NOTHING IS RESTRICTED.
ACTIVATING THE PROFESSIONAL VERSION ADDS THE MOST USEFUL FUNCTION IN THE TOOLKIT, THE ABILITY TO CHECK FOR 'AUTO UPDATES' DIRECTLY VIA THE TOOLKIT AND HAVE THEM PUSHED TO YOUR PC RIGHT AWAY AS SOON AS THEY ARE UPLOADED WITHOUT NEEDING TO DOWNLOAD THE WHOLE TOOLKIT EVERY TIME. YOU WILL ALWAYS HAVE THE LATEST VERSION AS SOON AS IT IS MADE AVAILABLE. THIS MEANS SMALLER UPDATES CAN BE SENT OUT MORE FREQUENTLY, SUCH AS ADDING A SINGLE FUNCTION, FIXING A BUG OR ADDING COMPATIBILITY FOR A SINGLE CARRIER. THE SMALLER UPDATES WILL BE COMPILED AND RELEASED TO THE XDA COMMUNITY AS A FULL (PUBLIC) DOWNLOAD VERSION SO PROFESSIONAL VERSIONS ARE ALWAYS UPDATED SOONER.
THE PRO VERSION ALSO ADDS THE ABILITY TO CHECK FOR THE LATEST VERSION OF SUPERUSER AND RECOVERY FILES AND DOWNLOAD THEM DIRECTLY TO THE TOOLKIT.
THE 'QUICK PICKS' SECTION[/B] ALLOWS YOU TO PROGRAM UPTO 10 SLOTS WITH TASKS THAT YOU MAY PERFORM ON A REGULAR BASIS OR JUST WANT TO KEEP A SET OF TASKS IN 1 PLACE. THEN JUST SELECT THE SLOT AND IT WILL REMEMBER ALL YOUR SETTINGS FOR THAT TASK AND RUN IT.
PRO USERS CAN ALSO SELECT THE "ANY BUILD" OPTION IN THE BUILD SELECTION SCREEN TO ROOT ANY BUILD (USEFUL IF YOUR BUILD IS NOT LISTED).
AUTO REPLY LINKS FOR PAYPAL TO GET A CODE INSTANTLY CAN BE FOUND AT http://goo.gl/nyGqv
--------------------------------------------------------------
PLEASE READ THE *HELP* PAGE AT http://www.skipsoft.net/?page_id=1269 OR USE THE INFORMATION SECTION WITHIN THE TOOLKIT IF YOU HAVE ANY QUESTIONS. I HAVE TAKEN A LOT OF TIME TO WRITE IT AND SOMETHING ON THERE SHOULD ANSWER 99% OF PROBLEMS.
--------------------------------------------------------------
1. INSTALLING ADB/FASTBOOT DRIVERS
The first thing you need to do is to install the adb/fastboot drivers. These are needed so that you can unlock your bootloader, root your device and perform other adb/fastboot functions.
THE DRIVERS CAN BE INSTALLED DIRECTLY VIA THE TOOLKIT. OPTION 1 IN THE MAIN MENU.
If drivers are not installed or there is an exclamation mark next to the device:
Plug the device in to a usb cable directly connected to your motherboard.
In the Device Manager a new item, usually called Android 1.0 should pop up in the list.
Right click on the device item then left click on Update Driver Software. Select 'browse my computer' and then 'Let me pick from a list'.
If no adb interface driver appears in the list then untick 'Show compatible hardware' and find the Android or Samsung adb interface driver.
If you cannot find either of these click Have Disk, browse to the Toolkit install folder, drivers folder, click on android_winusb.inf and click Open.
Click OK and select Google ADB Interface.
Make sure you have USB debugging enabled in settings, developer options. In Android 4.2.2 or later you have to enable the developer options screen by going to settings, About on your device and click on Build number at the bottom 7 times until it says You are now a developer. If you have already enabled usb debugging then unplug/replug the usb cable.
On Android 4.2.2 or later when you replug the usb cable after enabling usb debugging for the first time you will get a popup asking you to authenticate your pc. Tick 'Always allow' then click 'ok'.
--------------------------------------------------------------
2. USING SKIPSOFT UNIFIED ANDROID TOOLKIT
When starting the Toolkit you will first be asked which device you want to work with. Working folders will be created and the device files downloaded. You will then be taken to the Model/Build selection screen where you can do a number of things (other than select your model/build): Type '00' to enter your activation code and enable pro features, 'i' will take you to the Information and Help Section, 'a' will give you information on how to add support for a new build.
Supported builds are listed in the Model/Build selection screen and typing the associated number (i.e. 11) will download needed boot and recovery files (stock and custom recovery) then check for and download the latest superuser files available and custom recovery (pro versions only), verify all the files and start the Main Menu. You can now use all the functions and tools the Android Toolkit offers. Pro users can select the "any build" option to root any build (useful if your build is not listed).
--------------------------------------------------------------
USEFUL INFORMATION
How to get into Recovery Mode
1. Unplug the USB cable.
2. Shut down the phone.
3. Hold down the 'HOME' + 'VOLUME UP' buttons and press the 'POWER' button for about 5 seconds to enter Recovery Mode.
How to get into Download Mode (For Odin)
1. Unplug the USB cable.
2. Shut down the phone.
3. Hold down the 'HOME' + 'VOLUME DOWN' buttons and press the 'POWER' button for about 2 seconds until a WARNING! Screen appears. Press the 'VOLUME UP' button to enter Download Mode.
--------------------------------------------------------------
*DISCLAIMER*
I take no responsibility for any fault or damage caused by any procedures within this guide. No warranties of any kind are given.

**FAQ**
Q. Help me I can't find my build in the Model Selection Screen
The Toolkit includes a selection of Insecure Boot Images to cover all the different builds available. As there are very many different builds it is impossible to include an image for every single build but some builds share the same Boot Image. If you have a build that isnt listed on the Model Selection Screen you can therefore use a similar build. The best way to go is up to the next available build as it should offer more compatibility with the build you are using but if that isn't available then try the next build below your one as it should still be almost identical as long as it is the same version (ie. 4.1.1).
The Model Selection Screen is there so that if a task in the ToolKit requires an insecure kernel [to perform adb root commands] and your phone doesnt already include one, a compatible boot image [with an insecure kernel included] can be flashed to provide adb root access.
If you have a Custom Rom flashed to your phone then it will most probably have an insecure kernel included so it doesn't really matter if your build is not listed on the Model Selection Screen and when asked [by certain functions] if you have an insecure kernel on your phone you can answer 'yes'. However if the function fails then your kernel may not be insecure in which case you can flash one from the ToolKit. If you need to do this make sure the right build [or closest available build] is set so you flash the right image for your phone.
----------------------------------------------------------------------------
Q. What is ADB Shell?
Adb shell is a linux command line tool (because android is based on linux) used to send commands to your android device. For S-ON devices, this is crucial for modifying files in the /system partition (where the rom sits) as you cannot modify anything in /system when the rom is running without S-OFF like removing system apps.
----------------------------------------------------------------------------
Q. Why do I need to back up my IMEI/EFS and how do I do it?
There well protected section of your device that is virtually immune to any kind of flashing and manipulation (unless of course you know how to access it). This part of the device contains information such as IMEI (or MEID and ESN in the case of CDMA devices), programming parameters for the device such as your account information (phone number, etc), data provisioning parameters, and a whole bunch of other things that, when not handled properly, can render a device completely useless. All of these are contained in the infamous \EFS folder. If anything messes with your EFS folder, unlike flashing a device (which could potentially lead to bricks as well) it could render your device completely useless as it will no longer be recognized by your carrier. If you are not planning on flashing anything to your device and want to stay on pure Stock then you may never have any problems but it is still advisable to backup this information just in case (better to be safe than sorry). If you have a GT-I9300 GSM Model then you can do this from the Toolkit but if you have an LTE device then it isn't soo easy to do. If you have an LTE device you should go to *THIS* thread by lyriquidperfection and follow the information to save your IMEI/NV Data so that you are covered if anything should happen.
----------------------------------------------------------------------------
Q. Is there currently no way to root the Samsung Galaxy S3 without voiding the warranty?
All methods of rooting will void your warranty in some way as you will have superuser files on your phone that arent supposed to be there. There is a method of rooting your phone without increasing the flash counter which involves flashing a complete rom with root files already added but if anything happens and you need to send it back under warranty you will need to flash a 'proper' Stock Rom back before returning it or your warranty will be void. Flashing a custom kernel or recovery to root will increase the flash counter and also void any warranty. There is currently no method of resetting the flash counter on Snapdragon models but im pretty sure there will be some support for it soon. If you dont want to risk it or you aren't sure then you shouldnt really be flashing your phone and should just leave it alone. Its your choice .
----------------------------------------------------------------------------
Q. Will flashing Stock ROM via odin using the toolkit replace everything that was flashed before? recovery? etc?
Yes a Stock Image flashed via Odin will replace all your key partitions (boot, recovery, system) with the stock firmware. If you want to reset the phone back to an 'out of the box' state then you want to enter recovery and do a wipe first which will reformat your userdata partition.
----------------------------------------------------------------------------
Q. I flashed Custom Recovery but each time I reboot the Stock Recovery is back
There is an auto recovery restore system on certain Stock Android Builds that will reflash the Stock Recovery if you flash CWM on a Stock Rom.
Use Root Explorer to Mount the system folder as R/W (or use a free app from Google Play such as ES File Explorer). Rename the files /system/recovery-from-boot.p and /system/etc/install-recovery.sh (requires root). Now when you flash Custom Recovery it will NOT be overwritten after a reboot. You can also do this via the Toolkit.
----------------------------------------------------------------------------
Q. My AntiVirus program says the Toolkit files may be harmful
The exe compiled files are not digitally signed with a Microsoft certificate (as they cost money) so certain AntiVirus programs (mainly Norton and AVG Free) may pick it up as potentially harmful when it is not. They will pick up ANY file that doesn't contain a purchased Microsoft certificate in the same way. Just Restore the deleted file and exclude it from further scans and it will be fine. Or switch to a better AntiVirus program such as BitDefender.
----------------------------------------------------------------------------
Q. I flashed the Toolkit Boot Image, now my wifi + bluetooth won't work
The boot images are made from Stock with only needed changes made to the insecure boot images [modified adbd, default.prop and rc.local edited] and will work on all stock roms. If you flash them to a custom rom and the rom has been altered or uses a custom boot image then it will boot but certain modules may not load such as wifi or bluetooth. In this case you can use the boot image to root or perform adb root functions but will need to flash back the boot image for the custom rom to get other functions working again. This is not a fault of the Toolkit but a difference to stock in the custom rom.
----------------------------------------------------------------------------
Q. I am having trouble getting adb working with the drivers installed
Try switching your connection type from media (MTP) mode to camera mode (P2P). To do this open the notification area, click where it says connected as and change from MTP to PTP.
----------------------------------------------------------------------------
Q. I want to send my device back for warranty purposes
1. Follow the instructions to reset your flash counter with TriangleAway.
2. Download and flash a Stock Firmware image from the download section.
3. Boot into Stock Recovery and perform a wipe/factory reset
.
Your internal storage will be formatted and data and cache wiped. Your device should now be back to an out-of-the-box FULLY STOCK state with the flash counter [shown if you boot to download mode manually] reset and ready to send back.
----------------------------------------------------------------------------
Q. When connecting the phone I get 'USB Device not Recognized' and no serial number shows in the ToolKit
I actually had this problem recently and what fixed it for me was to make sure that the drivers have been installed, then shut my phone down plug the usb cable in and restart it. The phone booted up and the device was recognized and drivers installed correctly. May not work for everyone but worth trying.

*reserved if needed*

thanx op for all your work and helping us tmo peeps.
EDIt: works as advertised, no issues.

Hey, congrats on finding everything you were looking for and getting the Toolkit up and running for the US variants!
Thanks for the great tool.

Thanks!
Awesome and thanks! I used the GNEX Toolkit you put together and I assume this is very much like that one - I do apprecaite the effort and time you put into this - thanks a lot!

well done mate! everything seems to work perfectly. thanks Mark

Donation sent.
Thanks, Mark! :good:

overground said:
Donation sent.
Thanks, Mark! :good:
Click to expand...
Click to collapse
Thanks mate hope everything works as it should. If you spot anything that needs fixing please let me know. The Snapdragon Edition benefited from a few script upgades over the International version
Mark.

mskip said:
Thanks mate hope everything works as it should. If you spot anything that needs fixing please let me know. The Snapdragon Edition benefited from a few script upgades over the International version
Mark.
Click to expand...
Click to collapse
Well, there's a problem with build.prop push/pulls, at least on this ROM: http://forum.xda-developers.com/showthread.php?t=1728255
Any changes fail to boot...even after restoring backup in recovery.
Seems to be a permissions problem as indicated in this thread (towards the end): http://forum.xda-developers.com/showthread.php?t=1735128

overground said:
Well, there's a problem with build.prop push/pulls, at least on this ROM: http://forum.xda-developers.com/showthread.php?t=1728255
Any changes fail to boot...even after restoring backup in recovery.
Seems to be a permissions problem as indicated in this thread (towards the end): http://forum.xda-developers.com/showthread.php?t=1735128
Click to expand...
Click to collapse
Is that s problem with the ToolKit or with the build.prop changes from the thread you linked to. Its never a good idea to edit too much in the build.prop as it can soft brick your device.
Mark.

mskip said:
Is that s problem with the ToolKit or with the build.prop changes from the thread you linked to. Its never a good idea to edit too much in the build.prop as it can soft brick your device.
Mark.
Click to expand...
Click to collapse
I'm not sure at this point. All I did was use your tool to disable boot ani.
But it's not inherently the tool's fault because it happens if manually done also.

Use the toolkit to restore back to stock for some odd reason my Internet isn't working any ideas
Edit problem solved had to pull some and reboot thanks for this wonderful tool
Sent from my SGH-T999 using xda premium

Just upgraded to an SIII from a G2 and boy, when did rooting get so easy? Thank you for this fantastic tool; your work saves everyone a ton of headaches.

Recovery
Does this recovery support external sd card and if it does do the backup and restore work? I know there was one posted, but restores did not work. The recovery in the root tutorial woks with backup/restore but it's internal storage support only.

Just used This toolkit to root my device. Worked flawlessly. Thanks, bro!

anthonykash said:
Does this recovery support external sd card and if it does do the backup and restore work? I know there was one posted, but restores did not work. The recovery in the root tutorial woks with backup/restore but it's internal storage support only.
Click to expand...
Click to collapse
I would also like to verify this?

I got everything to work except installing superuser. I passed ODIN and then when I try to flash superuser, it flashes but when I restart my phone I don't have superuser.

kharnage said:
I got everything to work except installing superuser. I passed ODIN and then when I try to flash superuser, it flashes but when I restart my phone I don't have superuser.
Click to expand...
Click to collapse
go to the market and download superuser, and busybox.

anthonykash said:
Does this recovery support external sd card and if it does do the backup and restore work? I know there was one posted, but restores did not work. The recovery in the root tutorial woks with backup/restore but it's internal storage support only.
Click to expand...
Click to collapse
The ToolKit uses Team Epic's v4 cwm Recovery which from their changelog supports external sd cards and has no mention of restores not working so I would think its safe.
You can see Team Epic's Changelog *HERE*.
Mark.

Anyone managed to root H815 with v20a (6.0)? (locked bootloader)

Hi, has anyone been able to successfully root H815 with v20a kdz?
From 10b to 10d and even 10h, I've rooted all the images my self, by using the root injection method,
Where i extract the system.bin from the kdz (.dz), and run the injection script* on an ubuntu \ fedora.
*Mind you, I've used the same method (With the Updated SuperSU binaries&app [M Compatible]),
[.bin == .img]
After i have a rootedsystem.img I'd copy it onto the internal SD, and then boot in download mode, and used dd..
But ever since the M Upgrade through LGUP, none of the commands works, seems like Send_commands has become useless, likely LG blocked access to shell through downloadmode..
It always return 'FAIL', to any command.
But the os is fine, usb debugged was on, and pc was allowed, also OEM Unlock was ticked
Did anyone try the same method and also failed?
(if not, just test 'id' when using send_commands, the result would always be 'FAIL')

Even if this method would still work, you wouldn't be able to boot into the system. Since Android 6 the bootloader checks if the system partition is modified. Therefore you need to flash a custom Kernel, which is impossible with an locked bootloader.

That's the good part about that method,
It could be used as a 'backdoor' to write ANY part of the main block device,
it's just mostly used to write the system partition part and replace it with rooted system image:
'dd if=/data/media/0/rootedsystem.img bs=8192 seek=55296 count=529920 of=/dev/block/mmcblk0'
But you could calculate where the boot \ kernel partitions are and also use 'dd' to overwrite them as well..
If LG truly blocked this, we're basically screwed for now (Locked bootloader users)
Yes we could always revert back to LP, and then the method should work again.. (I'm really hoping it does...)

Shameless Self bump with edit:
Reverting back now, putting LGUP to the test:
- 1st time Failed OMG OMG Brick?!? - Win10 TH2 driver issues probably
- 2nd time works on Server 2008R2 VM through workstation, fhuu, doged that bullet...
Update:
Send_Command Functionality is working again!!! Whoooohooo
ROOT EXPOSED and all the goodie goodies

X0rzist said:
Even if this method would still work, you wouldn't be able to boot into the system. Since Android 6 the bootloader checks if the system partition is modified. Therefore you need to flash a custom Kernel, which is impossible with an locked bootloader.
Click to expand...
Click to collapse
Correct - root won't happen for MM anytime soon on bootloader locked devices, if ever.

[TOOL] SKIPSOFT ANDROID TOOLKIT -Google Pixel 2 XL- Drivers,Unlock,Firmware,Root

GOOGLE PIXEL 2 XL- SUPPORTS ALL MODELS WITH UNLOCKABLE BOOTLOADER UP TO THE LATEST ANDROID BUILDS.
SEE SUPPORT LIST FOR PUBLIC/PRO VERSIONS *HERE*
NOTE: Verizon models (not sure about ee) have locked the bootloader. In this case you will not be able to toggle the oem unlock setting to unlock the bootloader via the developer screen.
NOTE2: At the moment TWRP is still in alpha testing and lots of things do not work on it such as device decryption, mtp and backup. It's very risky to add this to the toolkit in this state as someone could easily brick their device if they dont know what they are doing so until a more stable version is made custom recovery will not be added.
The Unified Android Toolkit brings together Nexus, Google, Samsung and OnePlus Toolkits and supports many 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
* Backup/Restore a single package or all apps, user data and Internal Storage
* Backup your /data/media (virtual SD Card) to your PC for a Full Safe backup of data
* Root any public build automatically
* SkipRoot boot image to AutoRoot (selected builds)
* Sideload root/unroot files via Custom Recovery
* ALLINONE to Unlock, Flash Recovery, Root, Rename the restore file + install Busybox (G,N,O)
* ALLINONE to Flash Recovery, Root, Rename the recovery restore files + install Busybox (Samsung)
* Unlock/Re-Lock your Bootloader or check status (G,N,O)
* Download Google Stock Image files directly to the ToolKit (G,N,O)
* Check sha256 of google stock image before flashing
* Flash Google Stock Image (G,N,O)
* Flash any part of a stock firmware image to device [boot, system, recovery, etc.] (G,N,O)
* Custom Device Builder can add build support for listed device and add device support for any Samsung device with an unlocked bootloader [included in ULTIMATE, can be added as an extra]
* Download/sideload stock OTA image (G,N,O)
* Install Magisk Root on device [and uninstall if needed]
* Disable dm-verity check
* Install BusyBox binarys on device
* Rename the Recovery Restore File present on Stock Roms (if stock recovery is being restored after flashing custom recovery image)
* Flash Recovery [Stock, CWM, Philz_touch or Twrp Touch]
* Pull /data and /system folders, compress to a .tar file and save to your PC
* Auto Update Toolkit at startup (PRO ONLY)
* Auto Update superuser files to latest versions
* Auto Update Custom Recovery to latest versions [PRO ONLY]
* Disable forced encryption on device if needed
* Install Root Checker app by Burrows Apps
* Install Backup/Restore app by MDroid Apps
* Install EFS/Partition Backup/Restore app by Wanam
* Create tar with 1-Click for flashing via Odin
* Fix extSdCard write permissions in Android 4.4+
* Perform a FULL NANDROID Backup of your system via adb and save in Custom Recovery format on your PC (selected builds)
* Useful Mods, Fixes and Tools Section
* Extras, Tips and Tricks section (includes guides)
* Backup/Restore your /efs partition (gsm only)
* Dump selected Device Partitions, compress to a .zip file with md5 and save to your PC ( on builds with insecure image available)
* Mods section to automatically perform certain tasks on your device
* Boot to any recovery without Flashing it (G,N,O)
* Boot or Flash .img Files directly from your PC
* Quick Picks Professional Feature (10 slots)
* Install a single apk or multiple apk's to your device
* Push Files from your PC to your phone
* Pull Files from your phone to your PC
* Set Files Permissions on your device
* Pull and Trim your Radio Image (gsm models only) to your PC
* Dump selected LogCat buffers to your PC
* Dump BugReport to your PC
* Rip cache.img to zip file in CWM format
* Reboot device to Fastboot Mode or Android in fastboot mode
* Reboot device to Fastboot Mode, Recovery, Android or Download Mode in adb mode
* Turn Initial Start Screen On/Off for next use
* Sideload any zip file via Custom Recovery
* Basic Toolkit for use with ANY Android device
Key: G-Google Pixel, N-Nexus, O-OnePlus, S-Samsung
--------------------------------------------------------------
{
"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, PROFESSIONAL AND ULTIMATE 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 CUSTOM RECOVERY FILES AND DOWNLOAD THEM DIRECTLY TO THE TOOLKIT.
THE QUICK PICKS SECTION ALLOWS YOU TO PROGRAM UP TO 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).
THE ULTIMATE MODE ALLOWS YOU TO ACTIVATE THE PRO MODE ON EVERY DEVICE MODULE THE TOOLKIT SUPPORTS. NO MORE NEED TO BUY A NEW PRO CODE EVERY TIME YOU BUY A NEW DEVICE. THE ULTIMATE MODE ALSO INCLUDES THE NEW CUSTOM BUILDER MODE WHICH LETS YOU ADD SUPPORT FOR NEW BUILDS EVEN BEFORE THE TOOLKIT CAN ADD IT. CUSTOM BUILDER MODE CAN ALSO ADD SUPPORT FOR SAMSUNG DEVICES THAT HAVEN'T YET BEEN ADDED TO THE TOOLKIT.
MORE IMPORTANTLY DONATING SHOWS YOUR APPRECIATION AND ALLOWS THE TOOLKIT TO CONTINUE TO EVOLVE AND GROW. WITHOUT YOUR SUPPORT THE TOOLKIT CANNOT EXIST.
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'.
Newer devices also require you to enable OEM Unlocking in the developer section to allow the bootloader to be unlocked. Tap Developer options and enable OEM unlocking and USB debugging. (If OEM unlocking is disabled, connect to the Internet so the device can check in at least once. If it remains disabled, your device may be SIM locked by your carrier and the bootloader cannot be unlocked.)
--------------------------------------------------------------
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 if you have one, 'dr' will allow you to install drivers, 'i' will take you to the Information and Help Section, 'a' will give you information on how to add support for a new build.
Supported builds are listed in the Model/Build selection screen and typing the associated number (i.e. 11) will download needed boot and recovery files (stock and custom recovery) then check for and download the latest superuser files available and custom recovery (pro versions only), verify all the files and start the Main Menu. You can now use all the functions and tools the Android Toolkit offers. Pro users can select the "any build" option to root any build (useful if your build is not listed).
--------------------------------------------------------------
USEFUL INFORMATION
How to get into your FastBoot Mode
1. Turn your phone off
2. Unplug your usb cable if you have one plugged in
3. Keep holding the 'Volume Down' and 'Power' buttons to boot the phone into FastBoot Mode
How to get into Recovery
1. First boot into FastBoot Mode as described above
2. Scroll down with the 'Volume Down' button until it says 'Recovery mode' at the top and press the 'Power' button to enter Recovery
Show the Menu in the Stock Recovery Screen
1. Hold the Power button and keep holding as you press the Volume Up button quickly. The blue recovery menu screen should pop up.
--------------------------------------------------------------
*DISCLAIMER*
I take no responsibility for any fault or damage caused by using the Unified Android Toolkit. No warranties of any kind are given.

** FAQ **

** reserved if needed **

@mskip
Looks like quite a lot that can help out new users that have never used a Nexus/pixel device. Am I right in assuming that all "Nexus" functions will work for pixel devices aside from what is still a wip on this device? Such as easier downloading of the newest stock image, or just what is stated will work with the xl 2, which from what I can see is just disabling force encryption?
Either way, looks like a ton of work has gone into this. Nice job

Lawlrus said:
@mskip
Looks like quite a lot that can help out new users that have never used a Nexus/pixel device. Am I right in assuming that all "Nexus" functions will work for pixel devices aside from what is still a wip on this device? Such as easier downloading of the newest stock image, or just what is stated will work with the xl 2, which from what I can see is just disabling force encryption?
Either way, looks like a ton of work has gone into this. Nice job
Click to expand...
Click to collapse
Everything that is listed to work on Nexus devices will also works on Pixel devices including unlocking bootloader and downloading/flashing stock images. I have just added support for the new google images added this morning although im a bit confused why google release images for verizon devices when the bootloader cannot be unlocked and the images cannot be flashed.
I have also just added the critical partitions unlock procedure for the Pixel 2 XL. Latest version is 1.0.2 but I will post a message in a few minutes on how to update using AutoUpdate or ToolKitClean.

@mskip
Sounds good, thanks for the explanation

Thanks. Went ultimate. I'll try rooting next. Keep up the good work!

wtherrell said:
Thanks. Went ultimate. I'll try rooting next. Keep up the good work!
Click to expand...
Click to collapse
Please let me know what works and what doesn't so things can be fixed if needed.

UPDATE FOR GOOGLE PIXEL 2 XL DEVICE FOR ALL USERS (PRO AND PUBLIC)
Changelog [Google Pixel 2 XL] v1.0.2:
+Added FULL Support for Android 8.0.0 OPD1.170816.025, Nov 2017, EMR
+Added FULL Support for Android 8.0.0 OPD3.170816.023, Nov 2017, Verizon EMR
+Added above STOCK and OTA images to download/flash directly from Toolkit using option 9,1 [firmware download/flash] or 10,1 [ota download/sideload]
+Added new critical-partitions unlock command to bootloader unlock procedure for full unlock
Pro users can just start the Toolkit as normal. After you have selected your device you will be notified there is an update available and can auto update. SIMPLE.
Non Pro users have a few extra steps.
1. Exit the Toolkit if it is open.
2. Run ToolkitClean.exe from the intallation folder (or the Start Menu)
3. Select the device from the list
4. Type ‘y’ or ‘yes’ (without the quotes) to delete the existing module files and settings for the device
5. Select option 63 to update to the latest md5 firmware check file (if you are downloading new firmware)
6. Restart the Toolkit, select the device and new module files will be downloaded/installed
If you want to donate to the device module project or purchase an Ultimate Code to unlock all devices/features please do it through the Toolkit so you get the right code fast.

I was waiting for this. Probably want to redo all of my partitions, both A and B, at some point.

I am unable to boot to anything but the bootloader. Every attempt to use this to re-flash stock 8.0, it fails. It shows that my device is not set and returns to the main menu. Am I missing something??

chadhoard said:
I am unable to boot to anything but the bootloader. Every attempt to use this to re-flash stock 8.0, it fails. It shows that my device is not set and returns to the main menu. Am I missing something??
Click to expand...
Click to collapse
Had similar issues until I updated Android Tools.
They've just been updated for Pixel 2's. The older versions and 'Minimal' ADB packs do not work on Pixel 2's.

michaelbsheldon said:
Had similar issues until I updated Android Tools.
They've just been updated for Pixel 2's. The older versions and 'Minimal' ADB packs do not work on Pixel 2's.
Click to expand...
Click to collapse
Where and how do I install the most current? Also, I have the Pixel 2 XL, if that matters.

chadhoard said:
Where and how do I install the most current? Also, I have the Pixel 2 XL, if that matters.
Click to expand...
Click to collapse
This'll do it:
https://developer.android.com/studio/index.html

michaelbsheldon said:
This'll do it:
https://developer.android.com/studio...orm-tools.htm
Click to expand...
Click to collapse
Comes up with page not found.

chadhoard said:
Comes up with page not found.
Click to expand...
Click to collapse
Try new link for it: https://developer.android.com/studio/index.html

michaelbsheldon said:
Try new link for it: https://developer.android.com/studio/index.html
Click to expand...
Click to collapse
So just install this and then run SkipSoft ToolKit?

thanks for the great tools. I got the Ultimate version

chadhoard said:
I am unable to boot to anything but the bootloader. Every attempt to use this to re-flash stock 8.0, it fails. It shows that my device is not set and returns to the main menu. Am I missing something??
Click to expand...
Click to collapse
I had the same problem. I am updating the android studio as recommended (thank you @michaelbsheldon) as we speak and I'll try and report back.
So I just download the android studio from the site and don't run it correct? All should be good once it is installed?
Amazing continued work by @mskip by the way! Awesome tool! I have been using it for 4 phones now.

JDROIDS said:
I had the same problem. I am updating the android studio as recommended (thank you @michaelbsheldon) as we speak and I'll try and report back.
So I just download the android studio from the site and don't run it correct? All should be good once it is installed?
Amazing continued work by @mskip by the way! Awesome tool! I have been using it for 4 phones now.
Click to expand...
Click to collapse
I had a couple of issues while installing. However, I was able to get it to install. After rebooting my PC, I still can not get it to flash stock.

[ROM][SHT-AL09][Fenris_SHT-AL09]

{
"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"
}
Fenris Features
Built in current MicroG
Built in Magisk
Built in BusyBox
Built in GNU Utils compiled for android ( bash etc )
Radically debloated
Built for Lucky Patcher ( lvm already patched and modded playstore in place )
Working Desktop Mode ( PC mode ), Yes you read that right
320 DPI and working camera UI etc.
Better sized Launcher icons.
Shipped as a old school zip so fully customisable by anyone with winrar
Bugs
Wallpapers etc missing ( belongs to an apk i deleted and cant be bothered to track it down ) fixed in beta 2
Standard filemanager is replaced by CM native file manager ( dont want the big H knowing whats on your drive ) so some share functions may not be available
but SMB over the network is fine and thats all im interested in.
Both the TWRP 's are flaky, this version https://forum.xda-developers.com/honor-view-10/development/recovery-twrp-3-2-1-0-t3769917 has just refused to boot on me twice despite a decrypted data partition. But thats not down to Fenris in any way. The second twrp ( view 10 ) is no longer possible. It requires formating /data and by doing that wipes all the themes/wallpapers and screws the theming engine so i am having to stick with the first TWRP.
Unfortunately it BARELY works, just good enough to flash Fenris and associated zip kind of correctly.
Because of a crap TWRP Magisk needs to be setup on first use and download the manager, ie internet needed. It also can not update its zip so that has to be flashed by hand
Battery.... Tablet manager had to go, it deliberately interferes with LP in-app spoofing, but it also provides battery statistics and possibly with it missing, battery life could be worse than stock
( memory handling could also be compromised ). Its a damn hard thing to check since i have never run the tab stock. Tablet manager is back, it controls the recents screen which is broken without one of tablet managers services. Writing a startup script to disable some TM services, but at moment i use MyAndroidTools to do same
Maybe more, this is a beta.
Dev Info.
Huawei have done a good job with their Andfroid shell, its very memory aware and frugal ( unlike samsung and HTC ), its a very good base for Fenris
I would have kept a lot more native apk's but then there are some security concerns so anything with a free line out had to go ( except HwShare, use at your own risk )
If there is demand i will release a total stock zip so peeps can mix-match and roll their own.
Information
Based on MediaPad M5 8.4 SHT-AL09 hw eu Schubert-AL09A 8.0.0.196(C432) Firmware 8.0.0 r1 EMUI8.0 05014XYF.
the link for this firmware https://androidhost.ru/tuA
You must be on this firmware to grantee Fenris operating correctly ( currently Fenris does not ship the vendor or kernel due to issues with the TWRP available being flaky )
, fenris may work on other firmware ( Android O ) but this is for you to try.
I will most prob keep Fenris SHT-AL09 updated as i find stuff i like/do not like, but i AM NOT a Dev, i only get my hands dirty when i need to, so as far as support goes, dont expect much and you will not be disappointed.
My tested method of getting fenris on your SHT-AL09
......download Fenris from here https://mega.nz/#!BKpX2YpT!DhotPKAkJvASYQUPeUlNz3MrZanmFNCxmm6tcd4qcE4
......download Huawei MediaPad M5 8.4 SHT-AL09 hw eu Schubert-AL09A 8.0.0.196(C432) Firmware 8.0.0 r1 EMUI8.0 05014XYF from here https://androidhost.ru/6n0
......downgrade using the dload method
......Get a bootloader unlock code using DC unlocker method ( keep the bootloader unlock code, you will friggin need it )
......Unlock bootloader using Fastboot Unlock Method
......download MediaPad M5 8.4 SHT-AL09 hw eu Schubert-AL09A 8.0.0.196(C432) Firmware 8.0.0 r1 EMUI8.0 05014XYF. from here https://androidhost.ru/tuA
......Upgrade using the Dload method
......Unlock bootloader using Fastboot Unlock Method ( dont worry the code is the same )
......Go into you new 196 system and Activate ADB and OEM-Unlock
......Flash this TWRP https://forum.xda-developers.com/mediapad-m5/development/recovery-twrp-3-2-2-1-t3813825 using TWRP fastboot method
......DO NOT LET IT BOOT INTO SYSTEM, BOOT INTO TWRP INSTEAD
......Have a OTG USB adapter ( you can also use the sd card but that is a pain ) and Stick ready , copy all the files your going to need in the further steps onto it
......Hook up the stick and Flash Disable_Dm-Verity_ForceEncrypt_Quota_05.21.2019.zip from here https://zackptg5.com/android.php#disverfe
......Also Kernel-Sepolicy-Patcher.zip from here also https://zackptg5.com/android.php#disverfe
......THen finally flash Fenris
......Boot ito Fenris
TWRP fastboot method
1.... Make sure you have latest HW adb drivers installed ( check by getting an adb shell to work )
2.... Download latest Android platform tools https://developer.android.com/studio/releases/platform-tools
3)... Decompress etc, get to fastboot dir, open a CMD there
4)... Copy your TWRP image to same dir
5).... Boot into Download mode ( vol down while plufgging USB into computer with drivers set up )
5).... fastboot.exe flash recovery_ramdisk xxxxxxxxxx.img
6).... Get frigin ready to pull the usb and hold power + vol UP ( to reboot int TWRP you just flashed ) DO NOT LET IT BOOT INTO SYSTEM
7).... fastboot.exe reboot
8).... Pull USB, Boot into TWRP
9).... TWRP reboot Menue to shutdown
Dload Method
1.... extract the archive
2.... copy dload folder to root of a fat32 formated sd card
3.... boot up, enable dev options
4.... In dev options enable OEM-unlock ( you will need to be on internet from setup onwards ) unlock and adb
5.... In phone dialer dial *#*#2846579#*#*
6..... Get to upgrade from sd card and hit it.
7..... Phone reboots and does the ****
8..... If you have used online Erecovery downgrading may fail but if setting up from new ( unboxing) this will def work
Dc Unlocker Method ( copied from a p20lite thread , but works for m5 identically )
1)First connect your phone to the PC using the original USB cable.
2)When drivers are installed a popup screen would appear to view the "HiSuite" drive. This is a created drive-letter which contains a HiSuite Software downloader. Click to open or use the Windows Explorer to browse to this virtual drive.
3)Install the HiSuite software - this is important to get the correct drivers AND correct COM ports installed on your system. Skipping this step will result in non working DC Unlocker software.
4)When all is done go to the settings in your phone and open: System -> About Phone and tap the Build-number line about 7 to 8 times. Most likely the phone will ask for a PIN to active the developers mode. This is the code you've setup to use your phone. If you're already have a "developers option" you can skip this step.
5)Now click the "back" arrow once and select "Developer options".
6)Tap OEM-Unlock to activate it (confirm if needed), scroll down and tap USB Debugging to turn it on.
7)Your phone should ask permission to connect your PC (with some MAC address). Confirm it so the connection is approved. If that doesn't show up disconnect the USB cable and check if the USB debug mode is still active in the "Developer options". Than reconnect the cable to your PC.
ready to use the DC-Unlocker software to get our unlock code:
8)First you need some credits and you can buy the using this link: https://www.dc-unlocker.com/buy
9)Just fill in the the fields User-name, E-mail and Credits. Leave the "New user account" option selected if you are a new user.
10)For the Credits you only need 4 of them. I, initially, bought 5 so I still have one left
11)You'll receive a confirmation e-mail with a username and password. These are needed a bit later.
12)Extract the DC-Unlocker client to a fold and start it by clicking dc-unlocker2client.exe using the Windows Explorer (or any other file manager). To be sure you can also right-click the file and start the program using Administrator credentials.
13)Select in the right portion of the program the tab "Server" and enter the username and password you've received by mail. Check the "Remeber" box and click "Check login" to verify your account.
14)Click in the left portion of the program the dropdown list below "Select manufacturer" and choose "Huawei phones".
15)Leave the droplist "Select model" selected at "Auto detect (recommended)".
16)Grab your phone and open your dialer to type this code: *#*#2846579#*#* - this will get you into the service menu of the phone.
17)Tap 1. Background Settings -> USB Port Settings and select Manufacture Mode and than tap Close.
18)Put the phone done and let your PC install the newly found drivers.
19)If that's done click the Magnifying glass in the DC-Unlocker client software.
20)If all is connected correctly your phone is detected and a message in the white part of the program will tell you so. Also the "Select Model" field should display Huawei HiSilicon Kirin Android if the detection is succesfull.
**ready to read the unlock code! Yeah!
21)Click in the right portion of the DC-Unlocker client on the tab Unlocking.
22)Several buttons are visible but just click Unlock which could take a few moments before something is displayed in the white area at the bottom of the program window.
23)The unlock code can be copied and pasted - so please do copy the number to a text file and store it savely on your computer or in your cloud.
Fastboot Unlock Method
1).... Make sure you have latest HW adb drivers installed ( check by getting an adb shell to work )
2).... Download latest Android platform tools https://developer.android.com/studio/releases/platform-tools
3)... Decompress etc, get to fastboot dir, open a CMD there
5).... Boot into Download mode ( vol down while plugging USB into computer with drivers set up )
6).... fastboot oem unlock xxxxxxxxxxxxxx

Glad to read that the development of our Schubert isn't dead

massima said:
Glad to read that the development of our Schubert isn't dead
Click to expand...
Click to collapse
Not sure about that Seems barren in terms of real development. But in this case stock is a very good base, and in terms of memory usage very competitive with LOS, so in this case do not miss real open source code for the device.
The TWRP for our device is not great, and thats something i will get hands dirty fixing.

Any chance you could upload few pictures to show us how pc mode looks on smaller device, and will ever update your rom to 9.0?
Thanks in advance.

xabat said:
Any chance you could upload few pictures to show us how pc mode looks on smaller device, and will ever update your rom to 9.0?
Thanks in advance.
Click to expand...
Click to collapse
Yes sure will get a few screenshots out.
Will update to 9 when the dev community ( LP, Xposed, and all the other projects ) catches up.
At the moment we are prob a year away. ( Xposed barely works on EMUI 8 ).
Fenris is not your normal developers rom, its not about the latest version or untested beta code. Its about providing a stable platform for "alternative" open source code projects focused on Penetration testing, and pushing the boundaries.

any chance you could tell us how to activate desktop mode on stock rom ?

Are you rooted with the TWRP mentioned in the post ?
If not not much point in going further, plus its not an easy job mate, you good at messing around with your internal files ? Permissions and selinux contexts ? Edify script ? If so then you prob could do it. Otherwise best not even start.

vecna said:
Are you rooted with the TWRP mentioned in the post ?
If not not much point in going further, plus its not an easy job mate, you good at messing around with your internal files ? Permissions and selinux contexts ? Edify script ? If so then you prob could do it. Otherwise best not even start.
Click to expand...
Click to collapse
Yes, I unlocked bootloader months ago and I have root.

xabat said:
Yes, I unlocked bootloader months ago and I have root.
Click to expand...
Click to collapse
And twrp ? Cos your going to have to write an edify script to flash everything.

vecna said:
And twrp ? Cos your going to have to write an edify script to flash everything.
Click to expand...
Click to collapse
No I don't have twrp at the moment. I can't find working recovery for emui 9.
I wanted to see if desktop mode will work on android 9

xabat said:
No I don't have twrp at the moment. I can't find working recovery for emui 9.
I wanted to see if desktop mode will work on android 9
Click to expand...
Click to collapse
Well on EMUI 9 not happening, and not happening without TWRP anyway.
So why exactly are you on EMUI 9

I guess there is no external monitor support as I dident read that anywhere.
Is it a hardware limitation?

Well, this ROM is clean and awsome, i have the 10 inch tablet but i envy those who have the Schubert model as they can try this ROM??

Fenris is now at Beta 4, front post updated.

any development for this rom?

Teclast M40 Pro Discoveries

Teclast M40 Pro Discoveries​Various helpful points of knowledge to unlock your bootloader, to root, and use your tablet.
Problem: Where can I obtain the official firmware?
Solution: Teclast Website
Usage: type M1A3 in search
Problem How can I unpack "pac" files?
Solution: Build C utility divinebird / pacextractor
Solution: Download pre built Linux executable pacextractor.zip
Usage: >./pacextractor Firmware.pac
Bash:
git clone https://github.com/divinebird/pacextractor
cd pacextractor
make
Problem: I need tools to flash my device
Solution: Download the latest SPD Upgrade Flash Tool SPD_Upgrade_Tool
Problem: msvcr100.dll missing error in Windows whilst running SPD (Factory/Research/Upgrade) Tools
Solution: Download and install 2010 Visual C++ Distribution
Problem: I want to unlock my bootloader. (Window and Linux kit)
Solution: Download TeclastM40Pro_Unisoc_UnlockTools.zip
Usage: Read readme file.
Problem: How can I remove the dm_verify warning on boot up after unlocking the bootloader?
Untested Solution: digitally sign the vbmeta partition and write it back. See [Tutorial] How to create a custom signed vbmeta.img
Problem: I want to root my device.
Solution: Modify boot.img with Magisk, then sign.
Usage: Upload to your device's download directory, the current boot.img read from your device, or from the same version firmware. Then install Magisk app from here. Use Magisk to patch the boot.img. Sign the partition. Then flash back the signed magisk version of boot.img to "boot_a" partition. Guide to flashing single partition at Hovatek Website
Problem: I need to emergency flash my device?
Solution: Currently only from Windows, use SPD Upgrade Tools to reflash firmware.
Usage: From the tablet powered off, or if boot looping. Hold down the power-button and volume-down for five seconds, release the power-button, and keep the volume-down button still held for another five seconds, then release or release if the detected earlier. Windows and SPD tools should then detect your device to flash.
Problem: I want to improve my Telcast M40 Pro
Solution: List of suggested apps below;
FDroid App Store F-Droid Website
Aurora > via FDroid. App store allowing the direct download from Google Playstore, without your own account.
Lawnchair > via FDroid. Fast open source sophisticated launcher.
AdAway > via FDroid. Removes adverts whilst using apps.
TrackerControl > via FDroid. Manages apps access to internet, and blocks spyware and trackers.
.

Problem: I want root mode without the effort of hacking a rom partition.
Solution: For those with World version Teclast M40 Pro device, here is a signed rooted boot partition I created. Read the readme file inside the zip. You will require an unlocked device, windows setup with USB drivers for Teclast, the complete firmware from Teclast website, and SPD Update Tools installed. If you're successful, then on rooting you will need to install Magisk app to get root active. Magisk will reboot once to finalise.
Download : TeclastM40Pro_ROW__v1p0_signedboot_magiskrooted.zip
Download : TeclastM40Pro_ROW__v1p2_signedboot_magiskrooted.zip

SPD Upgrade Tools is closing while trying to flash stock firmware, both with M40 Pro locked and unlocked bootloader. What should i do?

laurorual said:
SPD Upgrade Tools is closing while trying to flash stock firmware, both with M40 Pro locked and unlocked bootloader. What should i do?
Click to expand...
Click to collapse
Sorry for replying late. I got no indication of the response. To the problem, I can only suggest getting a different version of SPD or m aking sure your computer system is properly updated. I hope you've already solved the issue!
Maybe you're experiencing, "Problem: msvcr100.dll missing error in Windows whilst running SPD (Factory/Research/Upgrade) Tools" See above for solution.

I've noticed a new ROM for world edition, "M40 Pro(M1A3)_Android 11.0_ROW V1.02_20220525", but not getting any system update options for OTA. People flashing their systems may want the latest firmware!

Thanks to your Magisk file I was able to root my tablet, but when updating to the latest version it goes into bootloop, I have tried updating the original firmware image again, but it also goes into bootloop.
Is there any way to install Magisk modules?
Thanks for your post, it helped me a lot to unlock my tablet.
Edit: My version is the M1A1 firmware V1.03_20210804
Edit 2: Finally, when updating my tablet with the root file that is in the post, it did not allow me to install any Magisk module, the solution is to download version 24.3, and update automatically, without changing to a higher version of Magisk

Glad you worked it out Miny !!! Sorry the warning emails for new posts have been going to a gmail account I no longer use.
Also your hardware maybe different and require it's own unique firmware and boot images. It seems the cracking in similar though.

Some questions:
Do I need to unlock my bootloader in order to be able to get root with magisk?
The tools for unlocking the bootloader uses
Code:
fastboot flashing unlock_bootloader
. My version of fastboot (33.0.3p1-android-tools) doesn't have that command. The included one (0.0.0-09219) does, but I wan't to be careful about running softwar from untrusted sources. Where is that version of fastboot from?
Does any of the steps necessary to get root access delete my data?

Hi there.
I have a m40pro (M1A1) running android 11, do you know if I can install firmware Z3A1 to get android 12? Or will be bricked?
Thanks in advance

rubsbcn said:
I have a m40pro (M1A1) running android 11, do you know if I can install firmware Z3A1 to get android 12? Or will be bricked? Thanks in advance
Click to expand...
Click to collapse
To tell you the truth, not sure. Most SoC are impossible or near impossible to brick. They usually allow for an injection or have a read only boot section. Other words you could test. Also research difference in hardware between models, and that may indlicate if something may not work. The kernel/drivers are the improtant aspect.

jorkusjorkus said:
Some questions:
Do I need to unlock my bootloader in order to be able to get root with magisk?
The tools for unlocking the bootloader uses
Code:
fastboot flashing unlock_bootloader
. My version of fastboot (33.0.3p1-android-tools) doesn't have that command. The included one (0.0.0-09219) does, but I wan't to be careful about running softwar from untrusted sources. Where is that version of fastboot from?
Does any of the steps necessary to get root access delete my data?
Click to expand...
Click to collapse
What OS are you using? Google is constantly changing Android Studio and the added modules. Then others may build with options removed. Personally I use Archlinux and load up standalone android-tools from the community repository. Currently v33.0.3-3
Try fastboot --help
Your version may have
Code:
fastboot flashing unlock_critical

minyfriki said:
Thanks to your Magisk file I was able to root my tablet, but when updating to the latest version it goes into bootloop, I have tried updating the original firmware image again, but it also goes into bootloop.
Click to expand...
Click to collapse
What I found works, is when using SPD Research Tool, load up the firmware.pac and then go into settings and click "Select All Files" and again to unselect, which leaves the default required items.
Then manually change BOOT to the Magisk img. Then click on all VBMETA types, and UBOOT_LOADER (may not be required though). Then flash.
You should get bootable tablet (no looping). Warning: UserData partition is written over.
I'll share my Magisk image for v1.2

e8hffff said:
What OS are you using? Google is constantly changing Android Studio and the added modules. Then others may build with options removed. Personally I use Archlinux and load up standalone android-tools from the community repository. Currently v33.0.3-3
Try fastboot --help
Your version may have
Code:
fastboot flashing unlock_critical
Click to expand...
Click to collapse
I'm using the same version as you on the same OS. After some research it seems like unlock_bootloader was removed in this commit from 2018. From what I can tell, unlock_critical does something else (unlock_bootloader runs
Code:
fb_queue_download("unlock_message", data, sz); fb_queue_command("flashing unlock_bootloader", "unlocking bootloader");
while unlock_critical runs
Code:
do_oem_command("flashing", "unlock_critical" and doesn't take the signature argument);
)
I'll see if I can compile the older version with the needed command.
What about my other questions?

Issue: Android not starting. I had the infinite restart when plugged in the usb. I tried to reload the installation package (succeeded), but didn't fixed the issue. Battery was not charging yet. When I started the Teclast M40 pro, the logo showed up, but the tablet turned off again.
Solution: I have disassembled the cover, unplugged the 5 pin plug from the battery for half hour and plugged again. When I tried to turn it on, everything was fine.

dougcwb said:
Solution: I have disassembled the cover, unplugged the 5 pin plug from the battery for half hour and plugged again. When I tried to turn it on, everything was fine.
Click to expand...
Click to collapse
Wow that's weird Doug. Remember this, if you don't already know, that you can do a cold start by holding down the power button for over 10 seconds, on most devices.
I guess you're running now on rooted tablet !!!

e8hffff said:
Wow that's weird Doug. Remember this, if you don't already know, that you can do a cold start by holding down the power button for over 10 seconds, on most devices.
I guess you're running now on rooted tablet !!!
Click to expand...
Click to collapse
I did the installation package process that the Teclast sent me. The last thing they told me to do was keep trying to install the package (wft?). Well, I just open the tablet, unplugged the battery for a while and after that it worked.
Maybe this resolved 2 things:
1-the battery was not properly connected in the first place, so when I plugged the 5 pin to the board it connected as it should.
2- Maybe there is a "memory" in the board attached to the battery that was bricked (or something like that) when I pulled off the plug, this memory was reseted.
BTW, when the tablet came to life again, the battery was at 87%.