Hello everyone!
Since there was such a demand for a OS X Toolkit, I've made one. It's quite simple and is made in Bash. It should work on all OS X versions.
It has been downloaded over 700 times on MediaFire alone and has been tested by several members, including myself.
Requirements:
* OS X
* A OnePlus One
* Cable to connect to your Mac (needs to be able to transfer data, if one cable doesn't work try another!).
That's it.
What it can do:
* Instructions to enable USB Debugging.
* Unlock or lock the bootloader of your OnePlus One
* Flash a custom recovery or the stock recovery (TWRP, CWM, PhilZ, Stock)
* Can root the OnePlus One (SuperSU)
* Reflash the entire device back to stock
* Install ADB and Fastboot to your Mac for manual use
* Do some basic ADB/Fastboot commands like rebooting, checking bootloader status and sideloading.
* Remove the tamper bit.
It's all one application that you need to run. It's quite simple and I've tried to make it as user friendly as possible. Hopefully it'll work for you. If it doesn't, please post in the thread and I'll probably take a look, same goes for bugs or such things.
Please remember that it must not be renamed, otherwise it won't work.
Thanks to the creators of the recoveries and Chainfire for SuperSU. Those are the real devs.
The source is available inside the application in Contents/Resources/Scripts, it doesn't have any comments or anything, but should be so straight forward that reading it shouldn't be a problem.
Enjoy!
Downloads:
Mega
MediaFire
Changelog:
Ver. 1.2.8
- Updated stock image to XNPH38R.
- Updated the stock recovery to XNPH38R's recovery.
- Added an experimental way to restore the old blue lockscreen.
Ver. 1.2.6
- Updated the TWRP image 2.8.0.1
- Updated SuperSU binary to 2.02.
- Removed unnecessary(?) reboot command at the end of the bootloader unlock menu.
- Updated the "reflash back to stock" image to XNPH33R.
Ver 1.2.4
- Updated the TWRP image to 2.7.1.1.
Ver. 1.2.3
- Made it clear that booting custom recoveries without unlocking the bootloader is impossible in OTA 30O or later.
- Made the DMG automatically open after mounting.
- Changed the wget binary to another one. The previous wget was likely built with my personal OpenSSL setup from Homebrew and was thus not compatible with everyone.
- Small fixes
Ver. 1.2.1
- Big bug fix to rooting without installing a bootloader (rebooted you previously into recovery when it was supposed to reboot you into fastboot). Thanks to Nandmp for finding that one.
- Removed the "You need an unlocked bootloader to root" information in the rooting menu.
- Removed a few sudos that weren't necessary.
- Minor fixes here and there.
Ver. 1.2
- Added a way to lock the bootloader.
- Added a special way to unlock a relocked bootloader without wiping the phone. It can also remove the tamper bit! See the devs' thread for more information.:
- Made it possible to root the phone without installing a custom recovery.
- Made it easier to reflash back to stock. It now downloads and the factory image automatically in a designated folder.
- Added locking in the basic adb/fastboot commands.
- Added reflashing the stock image by using a manually downloaded factory image in the basic commands.
- Loads of fixes here and there.
Ver. 1.15
- Fixed critical bug in reflashing back to stock for 64GB devices (thanks to @X10D3 for finding this one)
- Added experimental "boot to any custom recovery without installing it" to the basic fastboot commands.
Ver. 1.1
- It can now be run from anywhere!
- Added new custom logo and DMG style
- Problem where some people couldn't open the application due to multiple terminals should be fixed now.
- Fixed compression issue. It's now around 45MB again.
Ver. 1.05:
- Added a way to check the current lock status of the bootloader in the basic commands center.
- Small changes to the instructions when unlocking the bootloader.
- Reshuffled Installing ADB/Fastboot and some basic commands.
- Made some small changes to the basic commands menu to make it a little neater and easier to use with some extra instructions for certain commands.
Ver. 1.02:
- Removed warranty disclaimer since OnePlus does actually not invalidate your warranty by unlocking.
- Included further important steps to flash a custom recovery.
- Added the ability to install ADB and Fastboot into the system for manual use in the terminal.
- Added some basic commands you can do without installing ADB/Fastboot to the system like rebooting.
- Added version to About.
- Updated screenshot below.
Ver. 1.00:
-Initial release.
OnePlus thread
Here's a screenshot:
{
"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"
}
Thank you!!
Warranty will NOT be void Anyway thanks, hoping someone will try it
blak24 said:
Warranty will NOT be void Anyway thanks, hoping someone will try it
Click to expand...
Click to collapse
Really? That's very interesting. Got a source on that? If so I'll remove the disclaimer from it in the next version if someone finds bugs or similar problems.
Well OnePlus always stated that rooting the phone will not void phone's warranty
Consistant said:
Really? That's very interesting. Got a source on that? If so I'll remove the disclaimer from it in the next version if someone finds bugs or similar problems.
Click to expand...
Click to collapse
Yeah, I just Googled it and it seems indeed like the warranty isn't voided by unlocking the bootloader. That's a first, props to OnePlus for doing that.
And thanks to you for pointing out! I'll make sure to get that fixed once someone has properly tested it in case it needs additional changes.
When I run the toolkit, this happens?
---------- Post added at 11:35 AM ---------- Previous post was at 11:18 AM ----------
joeg6217 said:
When I run the toolkit, this happens?
Click to expand...
Click to collapse
Seems to have sorted itself out. It's now working
When flashing a recovery:
ERROR: could not get pipe properties
rebooting...
Just posting for FYI.
I've used a few different toolkits for a variety of phones.
This was the best and easiest I've used yet.
Everything worked perfectly.
Brilliant
:good:
in my Mac won't start (mavericks )....
---------- Post added at 09:14 PM ---------- Previous post was at 09:08 PM ----------
only a corrupted downloaded file. noow work on my maverick's imac, sorry
Thank you!
Sent from my One using XDA Premium 4 mobile app
Consistant said:
Hello everyone!
Since there was such a demand for a OS X Toolkit, I've made one. It's quite simple and is made in Bash. It should work on all OS X versions.
It is under testing by several members, but I cannot test it personally due to not having One. I've gone through it many times now, checked that ADB and Fastboot works on two OS X computers and it should work perfectly fine, but at least keep it in mind.
Requirements:
* OS X
* A OnePlus One
* Cable to connect to your Mac (needs to be able to transfer data, if one cable doesn't work try another!).
That's it.
What it can do:
* Instructions to enable USB Debugging.
* Unlock the bootloader of your OnePlus One
* Flash a custom recovery or the stock recovery (TWRP, CWM, PhilZ, Stock)
* Can root the OnePlus One (SuperSU)
* Reflash the entire device back to stock
* Install ADB and Fastboot to your Mac for manual use
* Do some basic ADB/Fastboot commands like rebooting, checking bootloader status and sideloading.
It's all one application that you need to run. It's quite simple and I've tried to make it as user friendly as possible. Hopefully it'll work for you. If it doesn't, please post in the thread and I'll probably take a look, same goes for bugs or such things.
Please remember that it must not be renamed, otherwise it won't work.
Thanks to the creators of the recoveries and Chainfire for SuperSU. Those are the real devs.
The source is available inside the application in Contents/Resources/Scripts, it doesn't have any comments or anything, but should be so straight forward that reading it shouldn't be a problem.
Enjoy!
Downloads:
Mega
MediaFire
Changelog:
Ver 1.1
- It can now be run from anywhere!
- Added new custom logo and DMG style
- Problem where some people couldn't open the application due to multiple terminals should be fixed now.
- Fixed compression issue. It's now around 45MB again.
Ver 1.05:
- Added a way to check the current lock status of the bootloader in the basic commands center.
- Small changes to the instructions when unlocking the bootloader.
- Reshuffled Installing ADB/Fastboot and some basic commands.
- Made some small changes to the basic commands menu to make it a little neater and easier to use with some extra instructions for certain commands.
Ver 1.02:
- Removed warranty disclaimer since OnePlus does actually not invalidate your warranty by unlocking.
- Included further important steps to flash a custom recovery.
- Added the ability to install ADB and Fastboot into the system for manual use in the terminal.
- Added some basic commands you can do without installing ADB/Fastboot to the system like rebooting.
- Added version to About.
- Updated screenshot below.
Ver 1.00:
-Initial release.
OnePlus thread
Here's a screenshot:
Click to expand...
Click to collapse
I'm trying to unlock my boot loader, but thing is popping up.
Make sure your phone is inside Android, is connected to your Mac and has
USB Debugging enabled.
After continuing you need to authorize your computer by looking at your phone and tell it to 'Always allow' your computer.
Press any key to continue...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
sharp2G said:
I'm trying to unlock my boot loader, but thing is popping up.
Make sure your phone is inside Android, is connected to your Mac and has
USB Debugging enabled.
After continuing you need to authorize your computer by looking at your phone and tell it to 'Always allow' your computer.
Press any key to continue...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Click to expand...
Click to collapse
Yes, that's ADB starting up it's server as usual. Keep waiting (it looks for your device) for a minute or two. If nothing happens try using the "See all devices connected" in the "basic adb and fastboot commands" menu. If you need to keep waiting forever or it says "No devices" then you need to try with another USB cable as that one might not have data transfer capabilities.
Remember as the instructions tell you, you need to enable USB Debugging and you need to be inside Android (like on the homescreen or something).
Consistant said:
Yes, that's ADB starting up it's server as usual. Keep waiting (it looks for your device) for a minute or two. If nothing happens try using the "See all devices connected" in the "basic adb and fastboot commands" menu. If you need to keep waiting forever or it says "No devices" then you need to try with another USB cable as that one might not have data transfer capabilities.
Remember as the instructions tell you, you need to enable USB Debugging and you need to be inside Android (like on the homescreen or something).
Click to expand...
Click to collapse
I've managed to get root access thanks to your application for Mac! THANK-YOU!
Huge bug when flashing to stock. It's flashing userdata instead of userdata_64G. userdata_64G has to be used when you're flashing the 64gb variant. A work around is to delete the userdata file and rename userdata_64G to userdata. then run the install script. You may modify your app so that it asks if you have the 16 or 64 then load the install script associated with the size.
Worked great! Thank you!
X10D3 said:
Huge bug when flashing to stock. It's flashing userdata instead of userdata_64G. userdata_64G has to be used when you're flashing the 64gb variant. A work around is to delete the userdata file and rename userdata_64G to userdata. then run the install script. You may modify your app so that it asks if you have the 16 or 64 then load the install script associated with the size.
Click to expand...
Click to collapse
Thank you so much for pointing this out, that's an extremely ugly bug that can cause problems. I'll make sure to get that fixed as fast as I can by adding a simple prompt asking for the version.
Consistant said:
Thank you so much for pointing this out, that's an extremely ugly bug that can cause problems. I'll make sure to get that fixed as fast as I can by adding a simple prompt asking for the version.
Click to expand...
Click to collapse
Awesome. Thanks for the update.
this should be added to the tool/utilities section great work man, saw this on the oneplus forum too :good::good::good::good::good::good::good:
I have a question. We need to download anything else like sdk, drivers or just the tool kit? I have see that adb drivers and fastboot can be installed from the tool kit. Thats all?
Thanks.
Related
Disclaimer: You are responsible for insuring you keep a backup of your stock recovery!
See Post 7 for the Stock Recovery if you failed to keep a copy for yourself: Click here
Steps for Backing up Stock Recovery:
Code:
fastboot boot /path/to/TWRP.img
The above command will only boot the recovery and will not overwrite your stock recovery making it possible to backup your stock from within TWRP. Now backup your recovery partition from within TWRP. It will be saved on your device and named, recovery.emmc.win. You can rename it to recovery.img to flash it back via usage of fastboot or apply restore within TWRP given the original filename, recovery.emmc.win.
Or within a terminal using dd (aka Data Destroyer);
Code:
dd if=/dev/block/mmcblk0p19 of=/sdcard/stockrecovery.img
TWRP for MT2-L03
Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
{
"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"
}
CHANGELOG for 2.8.0.0:
-Add MTP support to recovery thanks mostly to bigbiff with a little help from Dees_Troy
-Add command line capabilities - you can now execute various TWRP features via adb instead of the touchscreen
-Add support for color in the console and give error, warning, and highlight lines different colors
-Track backup and restore progress based on file sizes to provide a much more accurate indication of progress
-Improve handling of /misc thanks to mdmower
-Improve setting of time on Qualcomm devices thanks to [NUT]
-Allow using images on slidervalue GUI objects thanks to Tassadar
-Allow using variables and addition and subtraction in variables for easier theming
-Add support for 1440x2560, 280x280, and 320x320 resolutions and update 240x240
-Allow ui.xml file to include additional xml files to help break up the theme and make TWRP easier to maintain
-Other minor fixes and improvements
Over the course of the last year or so, bigbiff has worked to migrate various Java functions from Android's MTP implementation to bring you a fully C++ based MTP implementation that allows you to transfer files to both emulated storage and Micro SD cards. It's confirmed to work on various Nexus devices but we may have to make some changes on other devices to keep Windows happy. Windows is very picky about USB IDs and its drivers. We have tested it on Windows 7 and 8 as well as Ubuntu 14.04 Trusty. MTP is enabled by default, but we do toggle it off and on automatically during certain operations such as if you choose to wipe a storage partition. You can enable or disable MTP under the mount menu in TWRP. For more about what MTP is here.
Note: Due to a weird bug with our MTP setup, you cannot copy a zip file to the root of storage with Windows. You can change the .zip to something else like .txt and then copy it to the root and rename the file back to .zip once it's copied to the device. You can also copy the zip into any subfolder.
Command line support is also now available. You can perform various OpenRecoveryScript commands via the adb shell. Depending on what you are doing you may wish to do a "twrp set tw_mtp_enabled 0" and then reboot to prevent the MTP auto toggle from killing your adb interface. You can use this option to create and restore backups, wipe, install zips, and more. Via adb shell, type twrp followed by a space then enter the OpenRecoveryScript command and hit enter. Find more OpenRecoveryScript commands here.
Installation (PC):
- You MUST have an unlocked Bootloader! /* See Post 2 */
- Download TWRP Recovery
- Boot to your Bootloader
- Plug your device to your PC
- Open Command Window
- Type, then Enter:
Code:
fastboot flash recovery /path/to/TWRP.img
- Also, a video to demonstrate the process of installing TWRP - Credit goes out to @superbass311:
Installation (Device)(More Experienced Users Only!):
- You MUST have an unlocked Bootloader! /* See Post 2 */
- You MUST be rooted!
- Must have Busybox installed or a properly compiled DD binary
- Download TWRP Recovery
- Install a Terminal Emulator from the Play Store
- Type, then Enter:
Code:
su
Followed By:
Code:
dd if=/path/to/TWRP.img of=/dev/block/mmcblk0p19
Download:
- TWRP 2.8.0.0
CONTRIBUTORS
@Modding.MyMind
@xordos
@Shaky156
SOURCES
- Recovery built in a OmniRom 4.4.4 environment using device trees/kernel/dtb
- Stock Kernel
- Stock DTB
- TWRP source from Omnirom
- MT2-L03 Device Configuration Folder - My Github
VERSION INFORMATION
- Status: Stable
- Created 2014-09-22
- Last Updated 2014-09-22
Unlock Your Bootloader:
As we all know, you are not required to be rooted to install TWRP, however, you must unlock the bootloader on your device.
You must email [email protected] asking:
Hello I purchased the Ascend Mate 2 and I would like my bootloader unlock code.
SN: xxxxxxxxxxxxxxxxxxx
IMEI: xxxxxxxxxxxxxxxxxx
Thank you
Click to expand...
Click to collapse
You should get a response within 24 hours. In a situation where 24 hours has passed by than simply be patient or send another email. This is the 1st step to being able to unlock your bootloader (as of now)!
Here is a video to demonstrate to you viewers how you can go about unlocking your bootloader.
- Video credit goes out to @superbass311
*Reserved Again*
I will flash tomorrow. You just made the HAM2 the hottest phone out.
Sent from my MT2L03 using XDA Free mobile app
Thanks to all involved. Re-installed root using TWRP. Now Titanium Backup is working properly.
Flashed just now!
Backing up at the moment.
THANK YOU ALL!!!
How I did it:
Win 8 pc.
Phone booted and usb debugging allowed.
typed "adb.exe reboot bootloader" in cmd terminal
typed "fastboot flash recovery c:\adb\TWRP.img" in cmd terminal
I downloaded zip to my adb directory, also had to rename it too "TRWP.img" as download was "TWRP_MT2-L03_RECOVERY.img"
back up completed in 480 seconds!
Did have to play with TWRP settings as I hadn't used it in a while .
DID I SAY THANK YOU!!!
For anyone who is lazy to backup your stock recovery, I have uploaded my stock recovery image backup here, it should be same for all our MT2-L03 phone
This is backup of stock recovery, only use this image if you want to revert back from TWRP to Huawei stock crappy recovery.
http://tinyurl.com/qzxkm4x
FileName: recovery_MT2L03_mmcblk0p19.img
md5sum: 35703a1fe81917cb7930ab1e9e93e499
Edit: 2nd thought, they should be same, but let's make sure. Can anyone did (or going to) backup your phone stock recovery post the md5sum of yours? The ES file explorer can calc md5sum for a file.
Thanks iammudd, I think it is confirmed the recovery image is same for all MT2L03 phone.
Absolutely freakin' FANTASTIC!!!
Flashed it via fastboot with no problems.
I couldn't get MTP to work, but that's not a huge surprise to me as I've NEVER seen MTP work properly in TWRP on any device I've had sofar. I'd be interested to see if it works for anyone else.
So awesome that a root method is built right in too!
I think this is the verge of some huge things happening for our MT2-L03s!!!
Thanks for the great work!
TheGeekRedneck said:
Absolutely freakin' FANTASTIC!!!
Flashed it via fastboot with no problems.
I couldn't get MTP to work, but that's not a huge surprise to me as I've NEVER seen MTP work properly in TWRP on any device I've had sofar. I'd be interested to see if it works for anyone else.
So awesome that a root method is built right in too!
I think this is the verge of some huge things happening for our MT2-L03s!!!
Click to expand...
Click to collapse
Thanks for the info, right, mtp not work during my init testing as well. So other device are running twrp 2.8.0 or later?
PS, there are another 2 known issus,
* date is ~1970
* off mode charging
xordos said:
Thanks for the info, right, mtp not work during my init testing as well. So other device are running twrp 2.8.0 or later?
PS, there are another 2 known issus,
* date is ~1970
* off mode charging
Click to expand...
Click to collapse
Check your hangouts
Well done everyone ! Excellent stuff.
I suppose you know what my question will be,lol, but is it feasible to be able to port this to the MT2-L05 or other Chinese models?
If it's likely to be feasible, would it be possible to have your permission to attempt a port, or do you think as the underlying processors are different
it would probably wiser to start from scratch?
Either way, good work again !
xordos said:
* date is ~1970
* off mode charging
Click to expand...
Click to collapse
Interesting that backup filename is 1970-03-23 but the timestamp is 1979-12-31 23:00 on the phone.
After FTP'ing them onto Win7, their last modified times are 2013-12-31 22:00.
The device configuration folder used to build TWRP is available on my github which you can find the link in the OP under "SOURCES". If you have any knowledge on this stuff then feel free to look it over and throw some patches my way. As it stands, mtp isn't working properly however, mtp has only been known to work for a very small select list of devices. A very small list. As for the time stamp, this isn't much of a concern on my part as it is merely cosmetic. However, the problem with it would most definitely be the result of the actual TWRP source and not the configuration folder (device tree). Feel free to look further in to it if it is bothersome.
Right now, my goal is to see if I can resolve the mtp issue if it happens to be at all plausible since the mtp featured in TWRP is still fairly new and has much more work to be done with it over at TeamWin.
Currently looking in to offmode charging as well. This is merely cosmetic. But would be nice to have.
xordos said:
For anyone who is lazy to backup your stock recovery, I have uploaded my stock recovery image backup here, it should be same for all our MT2-L03 phone
This is stock, only use this image if you want to revert back from TWRP to Huawei stock crappy recovery.
http://tinyurl.com/qzxkm4x
FileName: recovery_MT2L03_mmcblk0p19.img
md5sum: 35703a1fe81917cb7930ab1e9e93e499
Edit: 2nd thought, they should be same, but let's make sure. Can anyone did (or going to) backup your phone stock recovery post the md5sum of yours? The ES file explorer can calc md5sum for a file.
Click to expand...
Click to collapse
Yes, md5 are the same and fc on Win7 of your/my versions are the same.
4L0M said:
Well done everyone ! Excellent stuff.
I suppose you know what my question will be,lol, but is it feasible to be able to port this to the MT2-L05 or other Chinese models?
If it's likely to be feasible, would it be possible to have your permission to attempt a port, or do you think as the underlying processors are different
it would probably wiser to start from scratch?
Either way, good work again !
Click to expand...
Click to collapse
Hi, just saw your another post about MT2-L05 RESOURCES. I am not sure if Modding.MyMind have time or not to do this. Maybe we can do some quick test, if worked, then his build (after small update) can support L05 phone as well.
Sending you a PM.
Just flashed TWRP recovery, and it's working great!
Now we just need a CyanogenMod ROM. While I'm thinking about it, when does Android "L" officially get released? It would be nice to just jump from Jelly Bean to L.
xordos said:
Hi, just saw your another post about MT2-L05 RESOURCES. I am not sure if Modding.MyMind have time or not to do this. Maybe we can do some quick test, if worked, then his build (after small update) can support L05 phone as well.
Sending you a PM.
Click to expand...
Click to collapse
I'd be willing to be a guinea pig for the Mt2-l05 if you need more people.
I second that
Sent from my MT2L03 using XDA Free mobile app
Gir357 said:
Just flashed TWRP recovery, and it's working great!
Now we just need a CyanogenMod ROM. While I'm thinking about it, when does Android "L" officially get released? It would be nice to just jump from Jelly Bean to L.
Click to expand...
Click to collapse
L should be released sometime in October I believe, alongside the new Nexus phone and tablet.
Supposedly the HAM2 is getting an EMUI 3.0 update (KK) in November. I don't know if the US version is included though.
Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Phone look:
Tablet look:
CHANGELOG for 2.8.6.0:
-Fix daylight savings time rules for USA and Europe (_that)
-Allow mulitple overlays for popup boxes (Dees_Troy)
-Add pattern style password entry for decrypt (Tassadar)
-Keyboard improvements (_that)
-Update AOSP base to 5.1 (Dees_Troy)
-Reduce theme count to 5 and rely on scaling (Dees_Troy)
-Various scaling improvements (Dees_Troy)
-Improved handling of resources in the GUI (_that)
-Make scroll bar size proportional to list size (_that)
-Allow scoll lists to render without a header (_that)
-Make console scroll per pixel with kinetic scrolling (_that)
-Support styles in XML to reduce XML size and improve consistentcy (Dees_Troy)
-Various other fixes and improvements (mdmower, bigbiff, codelover, etc)
CHANGELOG for 2.8.5.0:
-Scale the GUI - TWRP can read the theme's resolution and scale it up or down to fit the theme to your screen's resolution
-Backups can now be cancelled while the backup is in progress (does not include restore because we don't want to leave your device in a bad state)
-Improve thread handling and move input handling into the main rendering thread to improve stability
-Make MTP work even if unplugged and plugged back in
-Unify scrollable list code and make kinetic scrolling feel more natural
-Fix handling of mapped zip files for OTA updates (CM12 updater)
-USB keyboards should now work on all devices that support USB host mode via a USB OTG cable
-Other small fixes and improvements
CHANGELOG for 2.8.4.0:
-Add flashing of boot and recovery images via the TWRP GUI (Find the Images button on the Install page)
-Fix some MTP related crashes and bugs
-Eliminate TWRP toggling USB IDs during boot if MTP is enabled
-Fix various adb sideload issues
-Improve threading of actions
-Eliminate separate thread for screen timeout
-Update libblkid to 2.25.0
-Use power button as back button on watch themes for easier navigation
-Add mutex locking to data manager
-Improve custom theme handling on encrypted devices
-Allow the stock theme to be offset by build flags so we can center a lower res theme on a higher res screen especially for watches with round screens
CHANGELOG for 2.8.3.0:
-MTP will now tell the host PC that storage is removed instead of disabling MTP completely
-MTP will now report the correct max file size based on the file system in use to the host PC (may fix transfer of large files)
-Update and improve fix permissions and make fixing contexts optional
-Update SuperSU in TWRP to 2.40 and update install process
-Make TWRP work properly on AArch64 (Nexus 9 is now built in true 64-bit binaries and libraries)
-Attempt to set correct permissions and contexts on all files placed in storage so backups will show in Android
-Fix kernel panic during MTP start on some devices
-Support unicode fonts on devices with True Type Font support
-Fix slider value not showing sometimes (vibration settings page)
-Toggle MTP off during adb sideload to set correct USB IDs
-Reduce library requirements for 5.0 L decrypt
-Other minor fixes and improvements
Note: Starting with TWRP 2.8.2.0 and higher, adb sideload uses a new sideload method originally implemented in AOSP recovery. You will need the latest adb binaries to use sideload in these newer versions of TWRP. The version required is 1.0.32. You can find the version by running "adb version" on your computer. The new sideload feature no longer stores the zip on your device. Instead, a fuse file system is created in RAM and the zip is streamed from your computer. This puts less wear and tear on storage and ensures that large zips will not fill up all of your RAM. The sideload may spit an error on your PC side, but the zip should install just fine on your device.
DOWNLOAD:
Most devices can be updated quickly and easily with the TWRP Manager app:
Play Store Link
1) Install TWRP Manager from the Play Store
2) Open TWRP Manager and provide root permissions
3) Hit Advanced->Install Recovery
4) Verify the correct device name on your screen then press Install Recovery if the correct device is showing
OR:
You can find more information and download links on our NEW website! NOTE that the 2.8.6.0 version is ONLY available on our new site and is not available on our other, older mirrors!
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Note, only for H815 with bootloader unlocked!
Device specific page.
Download page with current and past versions.
Thanks to @wolfgart for testing!
Yes yes yes!
Dees_Troy said:
Note, only for H815 with bootloader unlocked!
Device specific page.
Download page with current and past versions.
Thanks to @wolfgart for testing!
Click to expand...
Click to collapse
:good:
TWRP'd and rooted
{
"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"
}
Great work guys.
Getting my device soon hopefully. I understand that we can unlock the boitloader via the unlock.bin file and the fastboot flash the twrp recovery.
But how do we get root @wolfgart?
nickfury said:
Great work guys.
Getting my device soon hopefully. I understand that we can unlock the boitloader via the unlock.bin file and the fastboot flash the twrp recovery.
But how do we get root @wolfgart?
Click to expand...
Click to collapse
once you have TWRP'd just flash supersu.zip
I was thinking exactly that. Thanks for confirming @wolfgart Much appreciated.
Now to see if it will work for h815t variant. I will try try it on my h815 and then my cousins t version
nickfury said:
I was thinking exactly that. Thanks for confirming @wolfgart Much appreciated.
Now to see if it will work for h815t variant. I will try try it on my h815 and then my cousins t version
Click to expand...
Click to collapse
Awaiting the outcome of your testing ... I have an 815T as well. No bootloader unlock for that one yet though
Daptonic said:
Awaiting the outcome of your testing ... I have an 815T as well. No bootloader unlock for that one yet though
Click to expand...
Click to collapse
So have you tried the official unlock method that has been outlined by lg for unlocking the bootloader for the h815 ( but in your case the h815t)? As in have you tried to enter the device Id of the h815t to see if you are actually able to download the unlock.bin file from the lg website or whether the website denies it?
Sorry I don't have the t version on me right now to try it out, but will do in a couple of days
So we just unlock at the LG website (any other way to unlock yet?), then TWRP, then root?
nickfury said:
So have you tried the official unlock method that has been outlined by lg for unlocking the bootloader for the h815 ( but in your case the h815t)? As in have you tried to enter the device Id of the h815t to see if you are actually able to download the unlock.bin file from the lg website or whether the website denies it?
Sorry I don't have the t version on me right now to try it out, but will do in a couple of days
Click to expand...
Click to collapse
I haven't as it specifically states " G4 (H815) for EU open market " ... which is not what I have. I'm in no rush and I'd rather get an exploit that doesn't officially void the warranty.
the_scotsman said:
So we just unlock at the LG website (any other way to unlock yet?), then TWRP, then root?
Click to expand...
Click to collapse
Correct, if you have the h815 model
nickfury said:
Correct, if you have the h815 model
Click to expand...
Click to collapse
Yep, sure do. Tempting...not too fussed about about warranty, but would rather not void it if another way is found soon. What are the chances of this? I'd guess not very likely? I'm only familiar with HTC, no LG dev.
Daptonic said:
I haven't as it specifically states " G4 (H815) for EU open market " ... which is not what I have. I'm in no rush and I'd rather get an exploit that doesn't officially void the warranty.
Click to expand...
Click to collapse
I think you misunderstand the very first bit of the unlocking procedure. Before you do any messing around ie flashing twrp, root etc, you need the unlock.bin file to unlock your bootloader, which is a very straightforward method outlined by lg.
As for your other concern, you can kiss your warranty goodbye as soon as you unlock the bootloader, as stated by lg. So if that is your worry then don't even bother with this process
---------- Post added at 11:45 AM ---------- Previous post was at 11:41 AM ----------
@the_scotsman
As mentioned above, if warranty is your priority, then you shouldn't go down this path.
As for me I am importing the devices, so I don't have warranty to start with lol
nickfury said:
I think you misunderstand the very first bit of the unlocking procedure. Before you do any messing around ie flashing twrp, root etc, you need the unlock.bin file to unlock your bootloader, which is a very straightforward method outlined by lg.
As for your other concern, you can kiss your warranty goodbye as soon as you unlock the bootloader, as stated by lg. So if that is your worry then don't even bother with this process
---------- Post added at 11:45 AM ---------- Previous post was at 11:41 AM ----------
@the_scotsman
As mentioned above, if warranty is your priority, then you shouldn't go down this path.
As for me I am importing the devices, so I don't have warranty to start with lol
Click to expand...
Click to collapse
Nah, warranty isn't a priority. I always unlocked and rooted my HTC flagships on the day I got them. I'm just new to LG, but it's not really any different. Just need to take that step and void it :laugh:
nickfury said:
I think you misunderstand the very first bit of the unlocking procedure. Before you do any messing around ie flashing twrp, root etc, you need the unlock.bin file to unlock your bootloader, which is a very straightforward method outlined by lg.
As for your other concern, you can kiss your warranty goodbye as soon as you unlock the bootloader, as stated by lg. So if that is your worry then don't even bother with this process
---------- Post added at 11:45 AM ---------- Previous post was at 11:41 AM ----------
As mentioned above, if warranty is your priority, then you shouldn't go down this path.
As for me I am importing the devices, so I don't have warranty to start with lol
Click to expand...
Click to collapse
I understand that I need the file ... for the official method. But that doesn't mean some crafty dev here @ XDA won't come up with a way that doesn't need it. Also, since the 815T, which I have, is NOT currently supported by the official unlock tool, your reply is moot.
There is subtle difference between going to their site, putting in my info and clearly voiding my warranty versus using an unofficial method and maybe sneaking in a replacement if things go pear shaped. I'm not worried about voiding my warranty, but why burn a bridge for no reason?
I thank you for your concern, but this isn't my first rodeo.
Can i use unlock the bootloader for h815t from LG?
Arent they (h815t & h815 for eu) the same?
I am confused....
EDIT: Ignore, didn't see the multiple pages.
calchung said:
Can i use unlock the bootloader for h815t from LG?
Arent they (h815t & h815 for eu) the same?
I am confused....
Click to expand...
Click to collapse
No the H815T is for the Hongkong market not EU. I too have the H815T interesting to see if the unlocking tool works for this version. It might since its a 815 base model. :good:
Waiting for 818P
{
"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"
}
This is for Windows ONLY at the moment.
Features:
Unlock bootloader
Relock bootloader
Backup data (all or selectable sections)
Restore data (all or selectable sections)
Optimize all OGG files on device
Zipalign all APK files on device
Batch install APKs from local PC folder
Reboot device
Reboot into recovery
Reboot into bootloader
Flash recovery
Changelog:
v3.21
* Fixed a couple commands
* Fixed broken backup menu
* Cleaned up some menu spacing
* Removed some unneeded comments
Download: v3.21-FREE
Download method 2:
There is now a free version and a donate version. The donate version requires a minimum donation of $5. First, set up a FREE GitLab account. Once you have donated, send me your GitLab username, in a PM or in this thread, and I'll add you to the repo so you have access.
I will be adding features to the donate version as I get time. I have to balance work/college/family, so my time is limited. General fixes will apply to both versions.
Requirements:
GIT (Windows download)
FREE version:
Code:
git clone https://gitlab.com/ChevyCam94/Android-Job-Box-FREE.git
cd Android-Job-Box-FREE
JobBox.bat
DONATE version:
Code:
git clone https://gitlab.com/ChevyCam94/Android-Job-Box-DONATE.git
## enter your GitLab.com username/password here when prompted ##
cd Android-Job-Box-DONATE
JobBox.bat
Previous changes:
v3.20
* Updated SOX to 14.4.1
* Updated all binaries in /Data with up-to-date versions from v26.0.1 tools
* Fixed some zipalign commands not pushing back to correct device folder
* Fixed fastboot reboot command
* Fixed main menu crashing with ENTER
* Overhauled the backup/restore sections
* Separated the CAMERA and PICTURES directories in backup/restore
* Switched to TIMEOUT instead of PING (non-skippable)
v3.10 * Updated all binaries in /Data with up-to-date versions from v26-RC tools
* Fixed menu choices in REBOOT menu
* Fixed backup and restore functions
* Fixed timing issue with bootloader lock/unlock commands
* Fixed a ton of misplaced commands
* Reworked terminal output to be more visually friendly
* Made some adb push/pull functions verbose again
* Removed some unused code blocks
* Made reboot options escapable within the script
v3.00
* Updated all data binaries in /Data with up-to-date versions
* Fixed the OGG optimization process
* Fixed mounting of /system in TWRP
* Fixed a couple menu text inconsistencies
* Removed a couple unnecessary subroutines
* Reduced the size of some subroutines
* Optimized the removal of non-apks and empty folders
Installation:
1: Extract the contents of the zip file somewhere (NO spaces in the whole folder path. Need to sort that out)
2: Double-click on JobBox.bat
Installation for method 2:
1: Navigate to a folder where you want the script (NO spaces in the whole folder path)
2: Run the commands for the version you want
3: Run JobBox.bat
NOTES:
To flash recovery, the recovery image must be in "/Data" as "recovery.img"
Optimizing OGG files is done by pulling all audio from the device, into the local computer
where the are optimized, and then pushed back to the device in their original location. HOWEVER,
be aware that optimizing an audio file too many times will break it, and cause serious loss of
audio quality. I have no way to test if the files were optimized already or not, so please keep
track of that yourself.
Optimizing APK files is done by pulling all APKs from the device, into the local computer
where they are optimized, and then pushed back to the device in their original location. There
is no verbose output (by choice), or progress animation. Believe me, its still working. Just
give it time.
No part of this script may be copied,
modified, redistributed, or included
anywhere without my written consent.
Credit goes to Lexmazter for the original template I'm using to make my script. You can find his tool HERE
Credit to Chris Bagwell for SOX
Credit to Google for the adb/fastboot binaries
Will it be able to root as well in the future?
chevycam94 said:
This tool is a work in progress.
As I add features, I'll release new
versions of the tool. This is for
Windows ONLY at the moment.
Click to expand...
Click to collapse
Just a heads up, you need to update the unlock command to "fastboot flashing unlock" as this is the new command for the M devices - oem unlock no longer works.
Thanks for the heads up. Question. Is that for devices that shipped with M?
Is all data wiped when performing the unlock no matter what?
Heads up - This tool does not work for some reason, just times out every time.
FAILED : (Remote : unknown command)
finished total time : ABC-XYZ
Click to expand...
Click to collapse
Its weird if you enable ADB USB debugging via developers options and allow OEM unlock and boot into bootloader it refuses to OEM UNLOCK even when using ADB terminal commands manually
Adb Devices - Lists the device
Fastboot reboot - Works
Fastboot reboot recovery - works
Weirdness - I'll Try ADB on my chromebook see if i can do it there
hutzdani said:
Heads up - This tool does not work for some reason, just times out every time.
Its weird if you enable ADB USB debugging via developers options and allow OEM unlock and boot into bootloader it refuses to OEM UNLOCK even when using ADB terminal commands manually
Adb Devices - Lists the device
Fastboot reboot - Works
Fastboot reboot recovery - works
Weirdness - I'll Try ADB on my chromebook see if i can do it there
Click to expand...
Click to collapse
use "fastboot flashing unlock" oem unlock has been depreciated on the new nexus devices.
Tung_meister said:
use "fastboot flashing unlock" oem unlock has been depreciated on the new nexus devices.
Click to expand...
Click to collapse
Yeah i can't get that to work on my ADB drivers i think i need to pull them down from google again, ill try after dinner must eat lol
I included (just in case) the 4 adb files from my current SDK, v24.4.1. I don't have my 6P yet, so I can't test it.
Also, when someone unlocks their 6P, report back here if it clobber use of the fingerprint scanner and/or Android Pay. I want to add a warning about them in the script if it does.
chevycam94 said:
Thanks for the heads up. Question. Is that for devices that shipped with M?
Click to expand...
Click to collapse
.
It might just be for the Huawei 6P, not all MM devices not certain. Since it's a Nexus device should be fastboot oem unlock not sure why Huawei changed.
Just in case, I added in an option to choose which method to use to unlock/relock the bootloader.
Added to Nexus 6P index thread:
[INDEX] Huawei Nexus 6P
hutzdani said:
Yeah i can't get that to work on my ADB drivers i think i need to pull them down from google again, ill try after dinner must eat lol
Click to expand...
Click to collapse
make sure you go into developer options and check "oem unlocking"
eneka said:
make sure you go into developer options and check "oem unlocking"
Click to expand...
Click to collapse
All set now had to update my ADB from the SDK, fastboot flashing unlock was not supported or listed as a command until I updated the SDK
Working on a major update to the backup and restore functions. Should really help people out with backing up certain things, not necessarily the whole thing
Ok, updated to v1.20. Now the user can choose to do a backup before unlocking/relocking, without going through two different sections. Fixed the fastboot commands, and added the ability to flash custom recovery.
MAJOR update to the script. Now available in the OP.
Now, in addition to a full backup, you can also backup and restore certain files, such as your downloads, pictures, videos, music, and even Android application data (NOT the apks, just the data user storage (/Android))
So can I use this tool to back up user data from my G4 and restore to my Nexus 6p so I don't have to reconfigure every single app? Like I can do with titanium backup if rooted?
StephenMSmith said:
So can I use this tool to back up user data from my G4 and restore to my Nexus 6p so I don't have to reconfigure every single app? Like I can do with titanium backup if rooted?
Click to expand...
Click to collapse
That's the idea. Just data, not apps....yet
Is this using chainfires systemless root method? And thanks for your contribution to the 6p
Sent from my Nexus 6P using Xparent Blue Tapatalk 2
{
"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"
}
It has LINUX/UNIX and MAC support!
Due to the fact that there is another tool for Android called Android Multi Tools, I decided to rename this one to Lx Multi Tool, future releases will go under this name.
Features: Fastboot
- Unlock/Lock Bootloader
- Flash Recovery Menu (you can choose and add recoveries) - TWRP 2.8.7.1 Included
- Flash any partition (Flashing submenu)
- Flash full Stock images (you can choose and add images)
- Erase partitions (you can choose which of the partitions)
- Reboot (you can choose again...)
Adb
- Sideload .zip files (you can choose and add .zip files) - SuperSU v2.65 (Systemless!) included
- Backup (you can choose the name and place for your backup)
- Restore (you can choose your backup)
- Version (it just shows the version of your adb binaries) - platform-tools 23.1 included
- Logs (DMESG and Logcat)
- Screenshots (you can directly take screenshots to your PC with no Root)
- Reboot (lots of choices)
Others
- Refresh and delete files/folders from menus (Right click or key F5 and Del)
- Open tool folders from the menus (to add your own kernel/stock image/recovery/sideload zip files)
- Tab key support for easier keyboard navigation
- Tool-tips for all buttons
- Check for updates
- Link to xda-thread (here)
Download links: Windows x86|x64 - Linux x64 - MAC x64
All released versions can be found here.
[ROOT] Use SuperSU 2.62 or higher from here systemless for 6.0.1 and above.
Known bugs/limitations: - For partition Flashing, it is recommended(mandatory?) to do a reboot-bootloader if you want to flash multiple partitions one after the other. (according to the Google flashing scripts) (Implemented in 1.2.1)
- For return to stock, the tool will be stuck after your phone successfully boots, you need to reboot to fastboot again in order to flash the Radio and finish the full return to stock. (Fixed in 1.2.0)
Changelog:
Check the changelog for each release here.
Tutorials/FAQ:
Q: How do I get in bootloader/fastboot mode?
Turn off the phone and turn it on by using Volume down + Power key.
Q: How do I check for updates in your tool?
Follow the instructions in the screen below.
Q: Where can I find the device driver to install it for windows?
Click here, download the driver and run the setup.
Q: How do I root my stock phone?
- Unlock bootloader.
- Flash recovery.
- Use SuperSU 2.62 systemless or higher from here.
(Usually the latest version upon tool release is included in the Sideload folder of the tool, you can either sideload it or copy it to recovery and flash it manually)
Q: I get an error "Cannot open file" on MAC, what should I do?
Open the terminal, go to your application path and paste this command:
Code:
chmod +x LxMultiTool.app/contents/macos/*
Q: What do I need to do in order to be in Fastboot or in ADB mode.
Fastboot mode will be detected only while being in bootloader.
ADB mode will be detected from Recovery (custom) and actual ROM with USB debugging active.
Refresh button needs to be used in order to check for what mode you are in.
Q: Are there any other software that I need to install in order to run this tool?
On Windows and MAC everything is bundled, so nothing needs to be installed, just run.
On Linux you need to install from your package manager libQt5Core, libQt5Widgets, libQt5Gui, libQt5Network.
If it's not enough, use ldd LxMultiTool in terminal to find out what you're missing from your environment.
Q: I have an yellow/orange/red text screen during boot, what's that?
When you unlock you usually get the Orange screen and it's normal, but if you really want to know what's this about, give a reading to this.
Q: Hey, my device is not detected, why?
On windows, you need to manually install the USB drivers, they are not included and probably they won't be included in this tool.
Also, make sure you click the connection Refresh button after connecting the device to your PC.
Q: What do i need to do in order to install a custom ROM?
1. Unlock Bootloader.
2. Flash a custom recovery of your choice.
3. Flash an insecure kernel (boot).
4. Flash custom ROM with no problems via recovery.
All those things are found and can be done via this tool.
Q: Hi, i just downloaded this tool, how do i use it?
First, extract the folder somewhere.
After that, run LxMultiTool.exe on windows by double clicking it, LxMultiTool on linux and the same on mac.
Q: Do I need android-sdk installed or something else?
No! This tool uses it's own supplied binaries for adb and fastboot, if you have android-sdk installed it will be ignored anyways.
This tool is fully portable and stand-alone.
Q: I get an error while trying to unlock the bootloader -> FAILED(remote: oem unlock is not allowed), what now?
Starting with Android 5.0, you need to enable Bootloader Unlocking from the developer settings, in order to do that, follow these steps:
- Enable Developer options
- Enable USB Debugging
- Look for the ‘OEM Unlock’ Option and toggle it.
Q: How do I use the return to stock feature?
First download the latest package from here, then extract the contents (there is an archive in the archive) untill you get the a folder like angler-mda89d
that contains the images, that folder needs to be copied in the /Data/StockPackages folder in order to be visible.
Easier steps -> Get your device in bootloader -> Start the tool -> Hit refresh -> go to Stock -> hit open folder -> copy the extracted folder with the name angler-xxxxxx in there, hit F5 or Right-click + Refresh -> you should see the folder in there like in the following screenshot. Thanks @ursa08 for the screenie.
Q: How do I enable Developer options?
- Launch the Settings
- Scroll Down and Tap on About Phone(or About Device)
- Locate the Build Number Section
- Tap on the Build Number Option 7 Times
- Go Back to the Main Settings Page
- Scroll Down and Tap on Developer Options
Q: Hi, i just bought a phone what should i do now?
Well, you firstly need to unlock your bootloader...
Q: What is logcat?
Well, you can pretty much use google for that answer, but to put it short, is that thingy that tells you what is happening behind the scenes of your phone.
It is usually used for debugging and entertaiment(?).
When you report an error/bug to somebody, it will be a blessing to provide a logcat (logfile)!
Q: What is a Custom Recovery and why do i need one?
A custom recovery is that thingy that let's you flash .zip files, use your logic and you wil get it why you need one.
Q:There are others guides/tutorials out there, should i check them instead of this?
If you manage to get things done using this one, no, otherwise yes, note that some could be outdated...
Q:What is sideload and how do I use it?
Sideload is a function from adb that let's you flash a zip file while in recovery directly from your PC.
Please note that you need to be in sideload mode on your recovery before doing this.
To enter sideload mode, in TWRP go to Advanced -> ADB Sideload -> Swipe to sideload
Sources: The official and original repository can be found here.
Bug reports/Feature requests: If you have any bug, or you consider a feature to be a must-have, please use the issue functionality on github for more traceability here.
Licensing: Please note that this tool is open source and released under GPL v3 licence which can be read here.
Make sure you understand at least the short version of the license that's provided in the tool before using it or before contributing/forking and other related stuff.
Tech and stuff: Some additional marketing for stuff used in this tool
Qt - An awesome cross-platform IDE
Vmware - For letting me test this tool on all platforms (Linux and MAC).
Icons8 - A nice platform for good-looking FREE icons. (Big thanks!)
UnixUtils - For the sed utility for Windows.
AndroidFileHost - For the awesome file-management platform for developers.
Donations: Even though this tool is provided free of charge, full open-source, donations are very welcome to support the future development of this tool and to buy me a beer while coding future improvements on it.
This section will also include the hall of fame for donors, as well as on the github repository.
Special thanks for donations:
- @john7760
Disclaimer:I will not be responsible for smashed screens, bricked phones or any other things that you can accuse me of, i've done this tool to help people, use it at your own risk and consider giving a THANKS if you use it and like it.Please consider leaving some feedback, what to improve, what could be done better, what annoys you, it really helps me improve the tool.
Also, to avoid useless threads on general, Q&A or useless posts, please read the FAQ section upside, it's like a Mini-Guide!
Nice! Quick question, will this work for other phones other then nexus 6. Like sam note 3
Sent from my Nexus 6 using Tapatalk
warfenix said:
Nice! Quick question, will this work for other phones other then nexus 6. Like sam note 3
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
This tool has support only for 4 nexus devices, some features might work, some not, it's all down if the commands that are used by the tool are supported by the other device.
For example all fastboot flashing commands use the command:
Code:
fastboot flash <partition> <file_to_flash>
The same goes for the rest of the commads, I will try to investigate more and see if it's worth it to create a Sam Note 3 package for the tool.
The adb features should work though.
That would be awesome as i run only linux. And cant seem to get odin or heindall to work. Tried multiple times. So if there is something you could cook up. Amazing sauce. Its a att note 3. Either way. This will work great for my n6
Sent from my Nexus 6 using Tapatalk
New update with some fixes that should have been implemented a long time ago...
- Fixed Sideload flashing
- Enabled Recovery rebooting
- Fixed open folder for Stock menu
Wow - Great work on this. Love the fact that it supports mac/nix as well.
Nice! Keep up the good work.
Thank you!
This still the go to way to unlock and flash twrp? I'm on latest stock marshmallow.
bL33d said:
This still the go to way to unlock and flash twrp? I'm on latest stock marshmallow.
Click to expand...
Click to collapse
Yes, you can unlock the bootloader and flash TWRP recovery with it.
Support to Nougat?
ipan gulopuan said:
Support to Nougat?
Click to expand...
Click to collapse
Nougat should work with no problems, I personally used it to flash bootloader, radio and vendor images for Nougat update.
ONEPLUS 5T - WILL SUPPORT ALL VERSIONS UP TO THE LATEST ANDROID BUILDS.
SEE SUPPORT LIST FOR PUBLIC/PRO VERSIONS *HERE*
The Unified Android Toolkit brings together all the Google, Nexus, OnePlus and Samsung 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 (G,N,O)
* Download Google Stock Image files directly to the ToolKit (G,N,O)
* Check md5 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)
* Download/sideload stock OTA image (G,N,O)
* 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 Stock Recovery, CWM touch, Philz_touch or TWRP Touch Recovery
* 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 but can be added as an extra]
* 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 file and custom recovery images to latest versions (PRO ONLY)
* Disable forced encryption on Nexus5X,6,6P and 9
* 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 (G,N,O)
* 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 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.
--------------------------------------------------------------
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 CUSTOM 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).
THE ULTIMATE MODE UNLOCKS THE PRO FEATURES FOR ALL DEVICES WITHOUT HAVING TO BUY THEM SEPARATELY. IT ALSO INCLUDES THE CUSTOM SUPPORT BUILDER TO ADD SUPPORT FOR UNLISTED BUILDS AND CAN EVEN ADD UNLISTED SAMSUNG DEVICE SUPPORT.
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 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 Up' 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
--------------------------------------------------------------
*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 ***
First? ?
Have you tested restoring backups? Any "....255" issues?
This is all very interesting and convenient but it's just non-free proprietary software running a few adb and fastboot commands.
** if needed **
cubandanger05 said:
First?
Have you tested restoring backups? Any "....255" issues?
Click to expand...
Click to collapse
I dont own the device if you come across any errors please let me know.
anyone else unable to log into snapchat after rooting?
virtyx said:
anyone else unable to log into snapchat after rooting?
Click to expand...
Click to collapse
Go to majisk, select hide majisk, reboot the device them try to log in.
JD_2322 said:
Go to majisk, select hide majisk, reboot the device them try to log in.
Click to expand...
Click to collapse
im using supersu
virtyx said:
im using supersu
Click to expand...
Click to collapse
Nope snapchat will not work if u have root...hence magisk to hide root and use snapchat...
persieghini said:
Nope snapchat will not work if u have root...hence magisk to hide root and use snapchat...
Click to expand...
Click to collapse
only workaround is to un-root log into snapchat then re-root.
is there a magisk guide somewhere? i dont really know what magisk is.
virtyx said:
only workaround is to un-root log into snapchat then re-root.
is there a magisk guide somewhere? i dont really know what magisk is.
Click to expand...
Click to collapse
Magisk is just a zip file like SuperSU.... You flash it. And it's done.... Let me know if you gonna change to magisk... I'll get the links here
persieghini said:
Magisk is just a zip file like SuperSU.... You flash it. And it's done.... Let me know if you gonna change to magisk... I'll get the links here
Click to expand...
Click to collapse
what are the advantages? or is it the same?
what does magisk support that supersu doesnt?
afaik magisk is more versatile in hiding root, so i can potentially use android pay?
virtyx said:
what are the advantages? or is it the same?
what does magisk support that supersu doesnt?
afaik magisk is more versatile in hiding root, so i can potentially use android pay?
Click to expand...
Click to collapse
It's almost the same with the exception that it can hide root for some apps... And mount systemless for Android pay...
It's way more convinient than SuperSU and I've always used/preferred it over SuperSU...
https://forum.xda-developers.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382
Here u go...v15.3 works like a charm for me right now....I'm running ob stock
Ps: v15.3 also has fingerprint authentication for root access
persieghini said:
It's almost the same with the exception that it can hide root for some apps... And mount systemless for Android pay...
It's way more convinient than SuperSU and I've always used/preferred it over SuperSU...
https://forum.xda-developers.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382
Here u go...v15.3 works like a charm for me right now....I'm running ob stock
Ps: v15.3 also has fingerprint authentication for root access
Click to expand...
Click to collapse
thank you
so if i want to uninstall supersu do i do this within the supersu app then flash stock boot.img and then flash magisk?
virtyx said:
thank you
so if i want to uninstall supersu do i do this within the supersu app then flash stock boot.img and then flash magisk?
Click to expand...
Click to collapse
Yes but I donno if doing it within the app will work or not...flashing unSu zip will definitely work...it had worked for me...rest of the procedure is as u stated..
persieghini said:
Yes but I donno if doing it within the app will work or not...flashing unSu zip will definitely work...it had worked for me...rest of the procedure is as u stated..
Click to expand...
Click to collapse
thank you
where can i find the latest version of unsu.zip?
virtyx said:
thank you
where can i find the latest version of unsu.zip?
Click to expand...
Click to collapse
Take nandroid backup just incase please
All the best..
persieghini said:
Take nandroid backup just incase please
All the best..
Click to expand...
Click to collapse
ty
just one last question
does magisk only affect the boot partition? i just want to know as when i had xposed i noticed a slow down in performance (i guess its because it installs an entire framework)
virtyx said:
ty
just one last question
does magisk only affect the boot partition? i just want to know as when i had xposed i noticed a slow down in performance (i guess its because it installs an entire framework)
Click to expand...
Click to collapse
I've never felt any performance drop after magisk.... So I can vouch for that