Related
[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.
[WARNING]
This is a post about my experience, so first i will share in short my experience. For those looking for a step by step guide, go to [GUIDE] section of this post. (this might also prove that most of you people don’t read).
[DISCLAIMER]
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in this guide before flashing it! YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
[My experience]
I would like to share my experience flashing my Oneplus 6T (6010 China Version) (NOT the T-Mobile version) from Hydrogen OS (china version) Oxygen OS. I did this mostly to have all the Google crap installed by default instead of the china stuff (and of course, for the fun).
I found this tutorial first (let’s call it #1):
https://www.xda-developers.com/oneplus-6t-unlock-bootloader-root/
This basically was useful for me to understand 2 things:
#1. Unlock the bootloader
#2. adb sideload (because of force encryption).
The TWRP on the tutorial above was an old version that does not support decryption for the internal storage, so if i tried to flash a rom with that TWRP it was simply not possible, so trying to figure out how to decrypt my internal storage y found that the a newer version (unofficial by the way) supported the decryption, so I gave it try following the flashing TWRP steps of the tutorial #1 (and it worked!):
TWRP (unofficial 3.2.3-12 by mauronofrio):
https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482
For the OS i gave it a try to flashing Oxygen using TWRP:
https://forum.xda-developers.com/oneplus-6t/how-to/official-oxygenos-9-0-4-ota-oneplus-6t-t3860953
After the successful OS flash, then i tried to flash magisk using the tutorial #1, but apparently didn’t worked so the I found this other tutorial (https://android.gadgethacks.com/how-to/magisk-101-install-magisk-root-with-twrp-0179668/) and did only the Magisk part. That did the trick so now i have my Oneplus 6T (6010) with oxygenOS and root
[GUIDE]
Downloads:
[TWRP image twrp-fajita-3.2.3-12.img]: https://www.androidfilehost.com/?fid=11410963190603878816
[TWRP installer twrp-fajita-3.2.3-12-installer.zip]:
https://www.androidfilehost.com/?fid=11410963190603878815
[OFFICIAL OxygenOS 9.0.10 OTA for OnePlus 6T]
http://otafsg1.h2os.com/patch/amazo...Oxygen_34_OTA_017_all_1812111237_f52c4612.zip
[Magisk v18]
https://github.com/topjohnwu/Magisk/releases
[Magisk Manager v6.1.0]
https://www.apkmirror.com/apk/topjohnwu/magisk-manager/
Steps
For those who need an intro for setting up your device for using adb utilities, go to this link, follow the guide. When you’re done come back to this post.
https://www.xda-developers.com/install-adb-windows-macos-linux/
Download all the resources
Reboot your device into your bootloader and run the following command:
Code:
fastboot oem unlock
You can reboot into the bootloader by switching on USB debugging, setting up adb and fastboot and typing “adb reboot bootloader”. Alternatively, you can hold volume down and the power button to boot up your device. USB debugging is also located under the developer options.
Boot the TWRP image
Code:
fastboot boot twrp-fajita-3.2.3-8.img
Flash the TWRP installer. Once on TWRP select Advanced > ADB Sideload swipe to the right and type the following command:
Code:
adb sideload twrp-fajita-3.2.3-8-installer.zip
Reboot System
Copy Oxygen OS into the internal storage.
Boot into Recovery.
Select install, and select the Oxygen OS zip file to start installation.
After boot OS, copy Magisk zip and Magisk Manager apk into the internal storage.
Install Magisk Manager apk into the phone.
Boot into Recovery. (if you lost TWRP recovery on the SO installation, reflash following steps 2 to 4).
Select install and select the Magik zip file.
Reboot into system
DONE!
Credits:
mauronofrio (for the recovery TWRP), Funk Wizard (offical Android Oxygen OS), Adam Conway (How to Unlock the Bootloader and Root the OnePlus 6T).
Sources:
Guides:
https://www.xda-developers.com/oneplus-6t-unlock-bootloader-root/
https://android.gadgethacks.com/how-to/magisk-101-install-magisk-root-with-twrp-0179668/
Magisk (v 18)
https://github.com/topjohnwu/Magisk/releases
TWRP (blu_spark twrp-3.2.3-x_blu_spark_v9.86_op6):
https://forum.xda-developers.com/devdb/project/?id=27466#downloads
TWRP (unofficial 3.2.3-12 by mauronofrio):
https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482
ROM:
https://forum.xda-developers.com/oneplus-6t/how-to/official-oxygenos-9-0-4-ota-oneplus-6t-t3860953
hello, after this "fastboot boot twrp-fajita-3.2.3-8.img" my oneplus 6t does not boot into recovery. I also tried to put it manually into recovery but it does not boot into it.
I am trying to flash an Android 12 GSI onto my Samsung Galaxy Tab Active3. Goal is to install the GSI without root / voiding the warranty. My company produces an app which is primarily used on Android on Galaxy Tab Active devices. It's expected Galaxy Tab Active3 will get Android 12 update in the next few months and we wanted to do some regression testing in advance of that. Hence the need to get Android 12 GSI onto the Tab Active3.
Device is an arm64 so I downloaded the arm64+gms version of Android 12 GSI (from Google's website). I have successfully unlocked the bootloader, and enabled DSU support. The device supports Project Treble and the VNDK isolated namespace, so in theory should support GSIs.
Everything I tried so far has failed. Any ideas to get it working?
Manual DSU
I have tried to install the GSI by manually starting the DSU via activity manager ("am start-activity -n com.android.dynsystem/com.android.dynsystem.VerificationActivity..." etc). Every time it just says "Installation failed" after reaching about 50% progress. I have tried setting different sizes for the USERDATA: 8GB (Google's recommended size), 2GB and 1GB. I get the same error every time. The device has around 40GB free space and the GSI image size is around 2GB (1GB gzipped), so it shouldn't be anything to do with the space requirements.
Logcat reports an error:
11-11 13:10:09.620 1103 3695 I DynamicSystemService: Failed to install system
11-11 13:10:09.621 16445 23403 E InstallationAsyncTask: java.io.IOException: Failed to start installation with requested size: 1257738436
This doesn't help unfortunately; it is thrown from the following file and this is just thrown if there is any error in the underlying dynamic installation:
packages/DynamicSystemInstallationService/src/com/android/dynsystem/InstallationAsyncTask.java - platform/frameworks/base - Git at Google
PS: Unfortunately the device does not support DSU Loader even though it's running Android 11 (searching for "dsu" in the settings returns no relevant results). Apparently none of the Samsung devices are supporting DSU Loader.
Fastboot / FastbootD
The device can be rebooted into fastboot mode ("adb reboot bootloader") but every command just hangs forever (except for "fastboot devices", which does detect the device). I tried "fastboot reboot fastboot", but it just reboots into the standard mode of the device and does not enter a fastboot userspace mode (fastbootd mode) as some have suggested it should.
Heimdall
At least one person has said they can patch GSIs using Heimdall: https://forum.xda-developers.com/t/can-i-flash-gsi-roms-with-odin.4029921/
That person was able to flash their GSI to the SYSTEM partition, but my device doesn't have a SYSTEM partition. The partitions are like SUPER, PRISM, etc.
I'm not able to get Heimdall working properly on Windows 10. I have tried with WinUSB, libusb0 and libusbK, but the same is true for all of them. After rebooting the device into ODIN mode, the device can be detected with "heimdall detect", but I can't do anything more including "heimdall print-pit", as I get a "Failed to access device. libusb error: -12" error.
I managed to set up Heimdall on an Ubuntu instance of WSL and map the USB using USBIPD. Inside WSL, "heimdall print-pit" does work but I can't get further to flashing anything (I tried to flash the GSI to SUPER, not sure if this was a good idea but anyway it failed) as I get a "Protocol initialisation failed!" error.
Odin
I am not sure if Odin itself even supports GSIs and I can't find anyone saying it supports them. I have tried flashing the GSI as an AP in Odin 3.12, 3.13, 3.14 and the patched 3.14 which removes signature checks. But every time it just fails.
Custom recovery
Just to also note, it seems none of the custom recoveries (TWRP, SHRP, Orangefox etc) support the Tab Active3, or I could have tried to flash those using Heimdall/Odin and then use them to flash the GSI. But I feel it's likely I would have had the same issues, at least with Heimdall.
you need custom recovery with dynamic partition support
aIecxs said:
you need custom recovery with dynamic partition support
Click to expand...
Click to collapse
as I mentioned, I couldn't find any custom recovery which supports my device...
Also, if I did have say TWRP or LOS recovery for my device, it seems I could run fastboot through the custom recovery (fastbootd). Then I assume I could just flash GSI using instructions like these: https://forum.xda-developers.com/t/...devices-with-dynamic-super-partition.4256667/
But it's a moot point because no such custom recovery exists for my device. There are custom recoveries for Tab Active 1 and 2, but not 3. So I'm trying to see what I can do with Heimdall
Also, quote from the above-linked thread in response to someone who asked about flashing using TWRP:
kusti420 said:
you can only do it in twrp if you rebuild the whole super partition with the gsi of your choice and flash that
Click to expand...
Click to collapse
if someone could tell me how to "rebuild the whole super partition with the gsi of your choice", that may help. because if I could convert gsi to super partition and if I could get Heimdall working (e.g. using native Linux version off a live USB or whatever), then I could use Heimdall to flash SUPER (in theory)
On that note, I found a couple of possible leads:
(1) https://forum.xda-developers.com/t/...r-img-and-flashing-our-modifications.4196625/ - shows how to unpack and re-pack super image using lpunpack and lpmake. I am wondering if I could use this to replace the system.img in my existing super partition with the one from GSI. But how to get the vendor.img and product.img? I don't think Heimdall has any command to backup existing partitions from a device
(2) https://source.android.com/devices/tech/ota/dynamic_partitions/implement#factory-images - it suggests that you can use "make dist" to build super.img, but I'm not sure if this requires me to completely rebuild AOSP from source or I can do it from existing system.img (i.e. GSI)
super_image_dumper
regarding build TWRP from source there are helpful users here
I ran Heimdall on native Linux rather than on WSL or the Windows version. This worked better and fixed the issues I was having before with Heimdall.
I then tried to flash VBMETA (the one bundled with the GSI) using Heimdall which worked, however my device was then soft-bricked, could only boot into Download Mode, and gave the following error:
ODIN MODE (AVB fail)
vbmeta: Public key used to sign data rejected. (5)
vbmeta: VERIFICATION_DISABLED bit is set.
CUSTOM VBMETA
VBMETA : No sign info
VBMETA ,
I also tried a VBMETA from avbtool, which gave a very similar error on boot:
ODIN MODE (AVB fail)
vbmeta: Error verifying vbmeta image: OK_NOT_SIGNED (3)
vbmeta: VERIFICATION_DISABLED bit is set.
CUSTOM VBMETA
VBMETA : No sign info
VBMETA ,
I managed to restore my stock vbmeta by extracting it from the stock ROM and installing using Heimdall, so my device can boot again, but it's back to vbmeta with verification enabled. How can I resolve this?
I tried to run lpmake, but I don't know my super partition size ("--device super:...") I thought it might be the partition block count from the PIT. but that is 1740800 for SUPER, whereas my system.img has size 2752909312, so surely it doesn't fit inside?
Got it fixed eventually (i.e. I am now able to run the GSI on Samsung Galaxy Tab Active3). I had made a really stupid error when running the DSU command. For KEY_SYSTEM_SIZE I was passing the gzipped system size, not original system image size. This is why the installation always failed after 50%, because it was only installing 50% of the system image. Also another really important thing to note is that after running DSU, you have to restart the system from the DSU notification and not from the normal power menu of the device.
In addition, I did flash "vbmeta_samsung.img" but I'm not sure if this was strictly necessary or not (I happened to notice that vbmeta_samsung.img has the same file size as the vbmeta disable images - 4KB vs 10KB for stock vbmeta). I'm going to be trying to help one of my colleagues to follow the same process, probably in the next few days, so will hopefully be able to report back on whether this flash is strictly necessary.
Also, I found that both Heimdall on native Linux and Heimdall on WSL actually suffer from the same problem. You can only post one command to the device, then subsequent commands fail with "protocol initialisation failed". On WSL I was doing things like "heimdall print-pit --no-reboot" and that's why I was facing issues when flashing. Basically, if you get protocol initialisation failed, just reboot the device and it should work.
ajbcc said:
I tried to run lpmake, but I don't know my super partition size ("--device super:...") I thought it might be the partition block count from the PIT. but that is 1740800 for SUPER, whereas my system.img has size 2752909312, so surely it doesn't fit inside?
Click to expand...
Click to collapse
stumbled across this post
https://forum.xda-developers.com/showpost.php?p=82241115&postcount=70
edit: bytes = block count × block size
aIecxs said:
stumbled across this post
https://forum.xda-developers.com/showpost.php?p=82241115&postcount=70
edit: bytes = block count × block size
Click to expand...
Click to collapse
Thanks for pointing this out, but this doesn't help me unfortunately. The number I'm trying to calculate here is the number 4294967296 in that post, which is the one number the guide doesn't explain how to calculate. Also, the PIT doesn't give my block size, only the "block size/offset". This seems to be just a plain offset, as it increases for every partition, even the small ones. So I have no idea what my block size is.
Just ran through the install steps with one of my colleagues (also with Samsung Galaxy Tab Active3) and there was no need to disable AVB as part of the process. We managed to get through with just the vanilla steps from Google. So all that stuff about "vbmeta_samsung.img" was just a red herring.
For newer ROMs built, there is a term used frequently called RDP. RDP stands fir "retrofit dynamic partitions", which tries to mimic what Android 13 requires (dynamically sized partitins), but also compatible with older OSs. Here is a basic search result.
what is retrofit dynamic partition - Google Search
In a TL;DR perspective, its like the virtual filesystem expansion used by many PC OSs, but for droids. If you have not had the experience before, it just means that system, vendor, data ETC should be able to dynamically resize themselves to how the main operation system sees fit. We must keep in mind how much the base allocated predefined partitions were, as to not push the virtual filesystem beyond the limits of ~4GB.
A long time ago, ROMS were only built for "Olive". Then the "Olives" which also included the 8A variants. With the current main tree dev team, now includes the 439 family of chipset including the Redmi 7A. A simple glance at their subforums show some ROMS are also labelled as Mi, or SDM (Snapdragon Mobile) 439, which should also be compatible with olive.
For RDP ROMs, there are 2 required installations beforehand; an RDP enabled recovery and a converter. This converter currently requires an installed OS before hand, so please do not wipe anything yet. It is recommended to not install an RDP recovery without fully installing an RDP ROM to avoid misshaps. It is also recommended to reinstall a non RDP recovery to install a non RDP ROM.
First step for enabling RDP. ignore all the errors upon boot, and first installation. If there are flashing errors for 439 ROMs, try typing M|mi439 in Advanced - Terminal Emulator to temporarily change the device codename to M|mi439.
The only publicly available RDP enabled recovery is TWRP, there is a better recovery on Telegram, will await mod judgement later. Recoveries are also Android OS version specific and may result in errors such as bluetooth not working. An <A11 and >A12 specific Orangefox is preferred (please wait a bit).
Xiaomi SDM439 Devices
Device List Xiaomi Redmi 7A pine Xiaomi Redmi 8 olive Xiaomi Redmi 8A olivelite Xiaomi Redmi 8A Dual olivewood
twrp.me
TeamWin - TWRP
This is the Team Win website and the official home of TWRP! Here you will find the list of officially supported devices and instructions for installing TWRP on those devices.
twrp.me
BTW, me-cafebabe is one of the core tree dev for our devices.
1 Install an RDP enabled recovery then reboot to it
2 Install the converter
3 Wipe metadata partition
4 Flash ROM
-x additional flash, reboot to recovery again and flash GAPPs, kernel, magisk ETC
5 Factory reset (better to format data)
The following clean installs will be easier
Clean installing another RDP ROM
1 Reboot recovery
2 Wipe metadata
3 Flash ROM + stuff
4 Format data
Clean installing a non RDP ROM (not recommended)
1 Reboot recovery
2 Settings - Unmount System before installing a zip (untick)
3 Advance - Unmap Super Devices (tap)
4 Classic wipe system, vendor, data, dalvik + cache partitions
5 Flash ROM + stuff
6 Format data
reserved
Without confirmation about posting links, please manually input them in your browser. If you have TG installed, it should auto forward you to the needed files.
Hi
I was struggling through the past 4 days since I Bricked my device. And as they say "The charity of knowledge is spreading it"
this will not be a real guide. only links and referral to other guides with some noop-friendly (Such as me) notes (As some people doesn't know that lenovo K12 is the same device as Moto G9 play)
1st: Unlocking bootloader -> The process for unlocking the bootloader is similar to that of a Moto device. You can find detailed instructions on how to unlock the bootloader for Motorola devices at GetDroidTips.The process is similar to the Moto device, you can search getdroidtips for how to unlock bootloader for motorolla devices, it is really a well specified described there
2nd:
In case you are on Stock ROM and want to install Custom ROM
- Unfortunately, there is no single custom ROM available for Guamp devices (Lenovo k12 or Moto G9)
- Although, there Guamp devices supports GSI roms (They are non-specific roms. you can consider them a custom roms without specification to our device)
Here is the guide How to install them: Here - Thanks to michaelmelita1
Notes:
1. You can install any GSI from this link, It only should support the a/b partitions
Here is an example: https://github.com/ponces/treble_build_pe/releases/
If you read the package name (Arm64-ab) any GSI containing them name means it is compatible with our devices
2. From the previous link, always install the biggest package (Do NOT install package contating "Slim" or "Vndklite"
3. Some packages have letter written in the name such as (bvN = Vanilla/No Google apps ||||| bgN=contains Google apps)
Up to the moment, I have tried (And I can confirm it works) the following GSI ROMS (Android 13 only)
Pixel Experience Plus 13.0 v2023.04.21
OctaviOS
Miku UI
3rd: How to root
- You should do these steps just after installing the new ROM, and before booting into the system (after finishing the installation process reboot into recovery directly and install Magisk)
- If you booted to your system, you need to wipe your FULL DATA and everything. enter recovery (TWRP) -> Reset -> Format data -> write yes and then confirm
1. Install TWRP - Discussed in this mechaelmelita1 thread also: here
2. Install Magisk APK file from here
3. Rename the magisk file into (Magisk.ZIP) -> Just change the .APK to .ZIP
4. Move the Magisk.ZIP to your device by a laptop using whatever method, then through TWRP screen -> Install -> Choose the Magisk.ZIP and install it
5. Reboot and starts your system
6. If you faced the issue (Abnormal state - "su" binary not from Magisk has been detected) -> then install this module (Link) through magisk
4th: You want to go back to stock ROM:
- Here is the trick, I spent days to find the proper ROM
- First you should connect your device to a fastboot -> Write this code:
Code:
Fastboot getvar all
this code will reveal a lot of details
- Look for your device version (The retail)
You will find it in Fingerprint line
Mine was: RPXS31.Q2-58-17-7-3
1. Go to this website: Here
2. Copy you device version and Search for your ROM in this website (It has to be specifically the same, I mean a ROM with the name RPXS31.Q2-58-17-7 will not work, because the last 3 isn't there which means it is not specific to your device)
3. Enter bootloader (Bootloader, not fastboot) and follow the steps here - thanks to jitendrapingale35 (Check the next step, there is 2 additional commands you need to add)
4. After executing the command
Code:
fastboot flash super super.img_sparsechunk.16
, add the following two commands and then continue with the instructions in the thread:
Code:
fastboot flash super super.img_sparsechunk.17
fastboot erase carrier
That is all for now
I will post anything new I can add
This is my first guide, so accept any mistakes or misunderstandings
Thank you