Related
[TOOLKIT] UNIFIED ANDROID TOOLKIT - SAMSUNG GALAXY NOTE 2 - Drivers, Root, Recovery + MORE
GSM (GT-N7100) and LTE (GT-N7105) SUPPORTED. THREAD: http://forum.xda-developers.com/showthread.php?t=1923956
AUSTRALIAN GSM (GT-N7100T) and LTE (GT-N7105T) SUPPORTED. USE GSM THREAD
SPRINT (SPH-L900) SUPPORTED. THREAD: http://forum.xda-developers.com/showthread.php?t=1957155
TMOBILE (SGH-T889) SUPPORTED. THREAD: http://forum.xda-developers.com/showthread.php?t=1957720
MOBILICITY, VIDEOTRON, WIND [SGH-T889V] SUPPORTED. NO THREAD YET. USE TMOBILE THREAD
AT&T (SGH-L317) SUPPORTED. THREAD: http://forum.xda-developers.com/showthread.php?t=2052779
BELL, ROGERS, SASKTEL, TELUS [SGH-I317M] SUPPORTED. NO THREAD YET. USE AT&T THREAD
VERIZON ([SCH-I605]) SUPPORTED. THREAD: http://forum.xda-developers.com/showthread.php?t=2052788
US CELLULAR (SCH-R950) SUPPORTED. NO THREAD YET. USE ANY
KOREAN SK TELECOM [SHV-E250S] SUPPORTED. NO THREAD YET. USE ANY
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 get into Recovery Mode
1. Unplug the USB cable.
2. Shut down the phone.
3. Hold down the 'HOME' + 'VOLUME UP' buttons and press the 'POWER' button for about 5 seconds to enter Recovery Mode.
How to get into Download Mode (For Odin)
1. Unplug the USB cable.
2. Shut down the phone.
3. Hold down the 'HOME' + 'VOLUME DOWN' buttons and press the 'POWER' button for about 2 seconds until a WARNING! Screen appears. Press the 'VOLUME UP' button to enter Download Mode.
--------------------------------------------------------------
*DISCLAIMER*
I take no responsibility for any fault or damage caused by any procedures within this guide. No warranties of any kind are given.
**FAQ**
Q. 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 (e.g removing system apps).
From Google:
Android Debug Bridge (adb) is a versatile tool lets you manage the state of an emulator instance or Android-powered device. It is a client-server program that includes three components:
A client, which runs on your development machine. You can invoke a client from a shell by issuing an adb command. Other Android tools such as the ADT plugin and DDMS also create adb clients.
A server, which runs as a background process on your development machine. The server manages communication between the client and the adb daemon running on an emulator or device.
A daemon, which runs as a background process on each emulator or device instance.
----------------------------------------------------------------------------
Q. I flashed CWM but each time I reboot the Stock Recovery is back
There is an auto recovery restore system on Android 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 the Market). Delete the file recovery-from-boot.p from /system. Now when you flash CWM Recovery it will NOT be overwritten after a reboot. You can also use the Toolkit to rename the files if you wish.
----------------------------------------------------------------------------
Q. What is the difference between Nandroid and Titanium backup?
A NANDROID will backup the whole system including boot, system, data and recovery partitions so you can restore a complete rom and all data and settings.
Essentially Titanium Backup is used to backup apps and associated user data. These could be restored AFTER a full wipe and a new Rom had been flashed on your phone.
The other option now which google added into the new adb command list is the adb backup which is in the ToolKit and can do the same job as Titanium Backup but will store the data on your PC rather than on the phone (where it takes up space and could be deleted).
----------------------------------------------------------------------------
Q. When would i perform a nandroid vs a titanium backup?
You would perform a nandroid backup to back up your entire system including boot image and data and system partitions so you can restore your entire system back to that particular point in the future.
You would use Titanium Backup mainly to back up your installed apps and settings so they could be reinstalled easily and quickly on any future roms. You can also choose individual apps to backup or restore on Titanium Backup whereas if you restore your boot partition via CWM Recovery you are stuck with the whole lot.
----------------------------------------------------------------------------
Q. When I try to open the ToolKit I get a box pop up for a split second and then it goes away. My AntiVirus program says the file may be harmful.
The exe files I compiled are not digitally signed with a Microsoft certificate (as they cost money) so certain AntiVirus programs (mainly Norton and AVG Free) will pick it up as potentially harmful when it is not. They pick up ANY file that doesnt contain a purchased Microsoft certificate in the same way. Restore the deleted file and exclude it from further scans and it will be fine.
----------------------------------------------------------------------------
Q. I donated but where do I get my activation code from?
Donation Codes are sent out manually to your PayPal email address [unless otherwise stated] after a confirmation email from PayPal has been receive. The Code can then be entered in the ToolKit Settings, Activate Donators Features Screen. This will enable The Auto Updates, Quick Picks and Extras Features in the ToolKit. Please be patient when waiting for the Code to be sent as it depends very much on what I am doing and whether I am at my PC when the donation is made. Please do not post in the ToolKit's thread or pm me asking for the activation code as it clogs up the thread and my messages. If you haven't received your code after 24 hours then feel free to email me via the skipsoft.net contact page.
Don't worry that you have been forgotten about, I check all emails personally and will deal with it as soon as I can.
----------------------------------------------------------------------------
Q. I have Windows 8 and cannot install the drivers
How to Disable Driver Signature Enforcement in Windows 8:
From the Metro Start Screen, open Settings (move your mouse to the bottom-right-corner of the screen and wait for the pop-out bar to appear, then click the Gear icon).
Click ‘More PC Settings’.
Click ‘General’.
Scroll down, and click ‘Restart now’ under ‘Advanced startup’.
Wait a bit.
Click ‘Troubleshoot’.
Click ‘Advanced Options’
Click ‘Windows Startup Settings’
Click Restart.
When your computer restarts, select ‘Disable driver signature enforcement‘ from the list. You can now load your modified driver. Reboot again once the driver is installed and all will be well.
----------------------------------------------------------------------------
Q. I flashed the Stock Firmware Image. Odin flashes the file successfully and the phone reboots but it stays stuck on the samsung logo
If the firmware tar file does not include a userdata image (which most Samsung firmware do not) then your userdata partition will be left from your previous setup. If this is incompatible with the new firmware because of build or something else then your system will freeze on boot up.
This is easily fixable by holding the Volume UP, Home and Power buttons all at the same time for about 10 seconds until the device reboots to the Stock Recovery screen. Use the Volume Down button to scroll down to 'wipe data/factory reset' and press the Home button to select it. Go down to yes to confirm and your userdata partition will be wiped. Your device should now boot fine.
*reserved if needed*
How To Videos on the Samsung Galaxy Note II ToolKit
This post belongs to wwjoshdew I am just mirroring his posts from the other Note2 threads.
Reserved for how to videos on this incredible toolkit!
http://www.youtube.com/playlist?list=PLwCVKEYxr_z7FBQYT32dbYw_kdSJmSDH2
How To Root
How To Manually Boot to Custom (or Stock) Recovery
mskips magic
Another one in the series of TOOLKITS from Mskip ( here since the early xdays ) and im v-happy to see this here.
im already rooted but this will make root a safer process for so many Note-2 owners.
here we go
Appreciate your big work Mskip !!!
This is a wonderful and complete tool
Mskip, the legend! !!!!!
Sent from my GT-N7100 using Tapatalk 2
Great news. Thank you so much for this. I'm sure it will come in very handy :good:
Released!!
Download link in first post.
Please let me know of any errors or bugs so I can get them fixed ASAP.
Mark.
hi mskip
Thanks for this great tool, i was using it on my GS3 to and was very useful.
I have a little issue I'm not able to flash the "boot-insecure-xxalj1-n7100.tar" after i hit start it doesn't goes on, i waited more than 15 min and nothing, see attached picture:
Any advise?
Can this be used for Note 2 LTE?
Sent from my GT-N7000 using Tapatalk 2
M3xital said:
hi mskip
Thanks for this great tool, i was using it on my GS3 to and was very useful.
I have a little issue I'm not able to flash the "boot-insecure-xxalj1-n7100.tar" after i hit start it doesn't goes on, i waited more than 15 min and nothing, see attached picture:
Any advise?
Click to expand...
Click to collapse
Its a driver problem with Odin.
Try rebooting your phone and pc and use a different usb port. I had that problem in the past and it usually fixed it. Also make sure you dont have samsung kies on your pc as Odin doesnt play nicely with it at all.
Mark.
zard said:
Can this be used for Note 2 LTE?
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
As far as I know the gsm and lte lodels are exactly the same hardware so in theory it should work fine. The only difference would be radios. This is what im hoping so I can keep everything under a single Toolkit. Do you have a link to a Note 2 LTE forum so I can check it?
Mark.
I've used these mskip all in one tools for various Android devices and can thoroughly recommend them. Whilst I have already rooted and modded my 7100 I will be downloading this tool and buying him yet another beer!
Sent from my GT-N7100 using Tapatalk 2
mskip said:
Its a driver problem with Odin.
Try rebooting your phone and pc and use a different usb port. I had that problem in the past and it usually fixed it. Also make sure you dont have samsung kies on your pc as Odin doesnt play nicely with it at all.
Mark.
Click to expand...
Click to collapse
Gonna try to reboot phone and PC and try another USB port. Don't have Kies installed. Will let you know.
hey
Is it a chance for mac version ?
Cheers
P
mskip said:
As far as I know the gsm and lte lodels are exactly the same hardware so in theory it should work fine. The only difference would be radios. This is what im hoping so I can keep everything under a single Toolkit. Do you have a link to a Note 2 LTE forum so I can check it?
Mark.
Click to expand...
Click to collapse
Thanks Mark! That did the trick.
Just another question, after making a Nandroid backup I end up (on my PC) with a 16 mb folder like on a incremental backup but without the blobs folder.
Don't know why not able to download from MediaFire.
Try to get it later again. Thanks anyway.
Ive used it, works like a charm!!!! Thanks so much mate, i wil be making a donation tomorrow.
Sent from my GT-N7100 using Tapatalk 2
mskip said:
As far as I know the gsm and lte lodels are exactly the same hardware so in theory it should work fine. The only difference would be radios. This is what im hoping so I can keep everything under a single Toolkit. Do you have a link to a Note 2 LTE forum so I can check it?
Mark.
Click to expand...
Click to collapse
Sorry, no links as yet. I'm waiting for the Note 2 LTE to launch here (that's the only model to be launched here) this month, thus I had started to read Note 2 threads to get myself ready. I'll pm you if I find any link useful. So far, from the threads in Xda Note 2, there's no good information on LTE.
Sent from my GT-N7000 using Tapatalk 2
Hello xda,
Recently We have heard about ubuntu for phones and tablet now this is the time that the first developer preview has rolled out!
Your device must be unlocked! (you can do thiscalso by installing this preview!)
Supported devices are:
- Galaxy Nexus maguro
- Nexus 4 mako
- Nexus 7grouper
- Nexus 10 Manta
What are the Fuetures at the moment?
Shell and core applications
Connection to the GSM network (on Galaxy Nexus and Nexus 4)
Phone calls and SMS (on Galaxy Nexus and Nexus 4)
Networking via Wifi
Functional camera (front and back)
Device accessible through the Android Developer Bridge tool (adb)
How to get the developer preview image?
Deploying Image to Device
To install the Ubuntu Touch Developer Preview on your device, you will need to execute the command below. Please note, this will wipe the contents of the device so ensure you have made a back-up. To install and get updates,
run the following command: phablet-flash -b The -b performs a full bootstrap on the device.
If the device is already unlocked it will carry on.*If you have already bootstrapped once and want to install a daily just do:
phablet-flash, This will deploy the latest build onto your device. Your device should reboot into the Ubuntu Unity shell.
Note: the files are saved in*Downloads/phablet-flash.
Rolling back to android?
The Ubuntu Touch Preview image is not for everyone and may not suit your current needs (yet). If you wish to roll back to an Android factory image, follow these steps:
- Recall the version that was installed before flashing.
- Download the factory image corresponding to your device's model and version (initial table has links).
- Ensure the device is connected and powered on.
- Extract the downloaded file and cd into the extracted directory.
- run*adb*reboot-bootloaderrun*./flash-all.sh*(use*sudo*if lack of permissions on the workstation don't allow you to talk to the device).
Your device should boot into Android after the process is finished.
For more info see:
https://wiki.ubuntu.com/Touch/Install?action=show&redirect=TouchInstallProcess
Left behind in the comments what you think about Ubuntu Touch
Greetings SK.
Porting Ubuntu Touch:
https://wiki.ubuntu.com/Touch/Porting
Dear open developers community I managet to fully root BlueBerry NetCat M-12 Tablet PC (a.k.a rebranded Cube H30GT) using "remount" exploit, here is my contribute:
{
"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"
}
REQUIREMENTS:
* Android SDK with ADB (guess you have this, if not, main files are included in permaroot.zip attached below)
* RockChip RK3066 USB Driver (see attachments below)
* Root/UnRoot script (thanks to Bin4ry from this thread, see attachments below)
* Micro USB Cable to connect Tablet and Windows Desktop PC (Linux is unsupported for now due to manufacturer limited driver distribution)
WARNINGS
1. Using this tutorial will make firmware/software changes on your device(s) but I am not responsible for any damage it could cause.
2. Following steps below will probably VOID YOUR WARRANTY. Read carefully your reseller warranty terms and conditions, and make your decision. It is all up to you.
3. I am not obligated to respond to future questions and/or support, it is my time and good will. If you must, ask here in this thread, there is no need to send me private messages to me because i wont read them at all.
4. You will spot that i dont recommend making any nand backups in this howto - is because I am not aware of any working method for backup M-12. I onlu can imagine dumping whole partition images to your EXTERNAL_SD and flashing back through bootloader but I did not tested that for now.
#GET ROOT
STEP-BY-STEP HOWTO
1. On your tablet PC go Settings -> Developer Options -> Turn on USB Debugging
2. Now You need to manage your Android Debug Bridge recognize your Tablet PC. You can check if it already works by typing this command in command prompt (in ADB folder, or wherever if you extracted adb into windows/system32)
Code:
adb devices
It should give you list of attached devices (something like this: 0123456789ABCDEF device) you should recognize your device if is connected. From my experiences it wont work the way manufacturer described, therefore you need to install patched RK3066 SoC driver you downloaded (this post below). To do so you must right click on My Computer -> Manage -> Device Manager, find your Unknown Device and install driver manually by selecting search folder manually, where you extracted RK3066_ADB_PATCHED.rar content respectively to your OS version (use correct 32-bit or 64-bit driver). Reboot your PC, go to device manager to check if Android Debug Bridge is there:
And You can repeat "adb devices" once again in adb to verify:
3. Now is time to obtain temporary root. To do so, simply navigate command prompt to wherever You extracted adb.exe and type following command:
Code:
adb remount
It uses common JB exploit, which exists in BlueBerry NetCat M-12, alowing you to get temporary root access via ADB shell until next reboot. You can stop at this point and push any system file You want (ie /system/etc/hosts) and set permissions. But if you want permanently rooted device, you need to push SuperSU.apk, su, busybox,... manually via adb before next reboot. Lucky for you, there is a script (permaroot.zip thanks to Bin4ry) which can do it all automatic with just few clicks. Download it from attachment below, extract somewhere on your hard drive run permaroot.bat and have fun.
Comming soon...
++ Flashing through Bootloader (via RockChip Batch Tools) HowTo ++
++ Illustrated Hardware disassembly guide ++
++ There is one custom ROM ported for another device and tested by me, which works in M-12 like a charm. It is purified JB ROM, rooted and without bloatware. I will post it ASAP ++
++ If i be able to obtain original Blueberry firmware dump, i will make CWM Touch based recovery image. Any interested owner of original BlueBerry NetCat should supply me with F/W dump, so if you are one, PM me please ++
++ If I be able to make Cube CWM Touch recovery work I will share (I managed to extract and install it from supersport900 ROM but it wont mount partitions for some reason) ++
BlueBerry NetCat M-12 Disassembly Guide
+++ BlueBerry NetCat M-12 HardWare Assembly +++
Tools needed:
1 x 1mm Torx Screwdriver (pictured below)
2 x sharp plastic departer for simultaneous two-side gently disassembling plastic parts (any Credit Card or guitar pick will do)
Step-by-Step Guide for servicing (H/W repairs, forced bootloader, etc) your BlueBerry NetCat M-12:
* Torx screws are located along port side, noted the difference on Torx and Cross screw types between some devices - Picture 5
* Some BlueBerry NetCats M-12 dont have left speaker - Pictures 20, 25 and 26
* BlueBerry NetCat M-12 has different stamp (OEM Logo) on backside - Picture 14
** Note LED and short circuit testpoint locations for forced bootloader mode which will be described later in more details - Pictures 25-32
Picture 1:
Picture 2:
Picture 3:
Picture 4:
Picture 5:
Picture 6:
Picture 7:
Picture 8:
Picture 9:
Picture 10:
Picture 11:
Picture 12:
Picture 13:
Picture 14:
Picture 15:
Picture 16:
Picture 17:
Picture 18:
Picture 19:
Picture 20:
Picture 21:
Picture 22:
Picture 23:
Picture 24:
Picture 25:
Picture 26:
Picture 27:
Picture 28:
Picture 29:
Picture 30:
Picture 31:
Picture 32:
Picture 33:
There is a PDF with all images in attached archive.
+++ClockWorkMod based recovery image for BlueBerry NetCat M-12+++
CWM Touch 6.0.2.7 (Thanks to Typhoon.X)
CWM Touch is Direct-Touch-Input CWM Recovery image: you can use touch gestures to navigate through menus, but I still prefer old-fashioned way of navigating through menus by using Volume +/- for <UP> and <DOWN>, and Power button as <CONFIRM> which is also available on our devices.
WARNINGS
1. Using this tutorial will make firmware/software changes on your device(s) but I am not responsible for any damage it could cause.
2. Following steps below will probably VOID YOUR WARRANTY. Read carefully your reseller warranty terms and conditions, and make your decision. It is all up to you.
3. I am not obligated to respond to future questions and/or support, it is my time and good will. If you must, ask here in this thread, there is no need to send me private messages to me because i wont read them at all.
4. You are welcome to make backup(s) before make any change to your device; You can export partition(s) dump or make nandroid backup via CWM based recovery image if you have it allrady installed.
Install:
1. Make sure you have installed RK3066 drivers;
2. Download ClockWorkMod.zip, extract, run RKAndroidTool.exe.
3. Reboot your BlueBerry NetCat M-12 in Flash Mode (turn on device by holding Volume- and Power Button or push "Reboot to Flash Mode" button in RKTool)
4. Push "Flash ROM" button like on image below (all settings are stored in config.cfg so You dont need to change anything):
After procedure is finished (cca 15 seconds), device will be automatically rebooted into CWM Recovery, so it's highly recommended making first nandroid backup.
Usage:
If your device is rooted, you can reboot your device into CWM recovery by typing following commands in terminal emulator:
Code:
su
reboot recovery
Or by using any 3rd party rebooting widget/app, which allows rebooting into recovery.
However, if your device is not-rooted, you can reboot into CWM recovery by typing following commands which exploit temporary root access via Android Debug Bridge (adb.exe on your PC, drivers must be installed):
Code:
adb.exe reboot recovery
or
Code:
adb remount
adb shell
su
reboot recovery
Download CWM Touch based recovery image from Google Drive: ClockWorkMod or attachment below.
Be aware that bootsplash will be changed as you need to replace misc.img, so dont panic if you see Cube logo instead of NetCat.
Hey, CyberianIce, thank you for your contribution for this device, since it's really hard to find anything verified out there, and xda is alwas the safest choice.
I wanted to ask you if you could share the info, or link maybe, to that ported ROM you tested on Blueberry, since I don't wont to brick my device by trying an untested ROM.
Thanks in advance!
I can re-upload from my HDD because I forgot original URL, when I got day off my work.
/CyberianIce via TapaTalk HD
That would be amazing, thank you! And if you could write something about the ROM (when you have free time, of course) just so that I know what I'm installing..
Hi, i wonder how to make a hard reset on this devices, i have tried the normal way, volume(-)(+) + power but nothing is working. Can someone help me? Thanks!!
Hi, CyberianIce, I was wondering if you'll have time soon to upload the ROM, if it's not too much trouble. Thank you!
So far I found this Firmware image working best on NetCat M-12: http://www.rockchipfirmware.com/sites/default/files/cube_u30gt-h_V1.11_TNT_R1.zip
For Flashing use this tool: http://www.rockchipfirmware.com/sites/default/files/RKBatchTool1.5en.zip
(Credits: http://www.rockchipfirmware.com/)
It is great because you can flash it vie Rockchip Batch Tool which means its very useful for debricking. It is 4.1.1 from Cube U30GT-H with all this tweaks:
Brief Description:
-Rooted
-Based on stock rom (2012.12.28)
-App partition is Larger
-Build.prop mod based on SGS II SGH-i777 for improved market
-Added Permission Files for improved market
-Removed Chinese Apps
-framework.jar mod for better gameloft compatibility (Asphalt 7 should now work)
-Added SuperSu, gallery with picasa support, ESfile Explorer, english dictionary fix
-Simplified and pretty boot animation
-Changed Annoying Keyboard Key-press sounds... now they are less annoying (based off Cyanogen sounds)
-Default Background should be changed
-Changed "browser" start page to our Google paid search. Use it (free to use for you) to search the web and you will be helping to support us as we release more free firmware. Can easily change this if you want.
Click to expand...
Click to collapse
Afterwards one can flash CWM based recovery image following tutorial from this post
[ROM][RK3066][U30GT-H]BlueBerry NetCat M12
Based on latest original Cube U30GT-H ROM debranded from BlueBerry NetCat M12
Tested on many CUBE U30GT-H devices
Debloated
Removed China
Custom tuned Kernel for optimum performance and stability (up to 15k points in AnTuTu Benchmark)
Increased /data partition size to 2GB instead of 1GB (reduced internal sdcard partition to 12.5GB instead of 13.5GB)
NetCat BootSplash
Custom android bootanimation.zip
Fully working CWM Recovery 6.0.2.7
HOWTO:
1. Shut down your tablet and start it by holding down Volume + button and insert USB Cable with PC. RK Device will apear, if you have no drivers you can find them in archive.
2. Navigate to RKDevelopTool_v1.35 folder and run RKAndroidTool.exe
3. Click Erase IDB and wait for finish
4. Click Run and wait for finish
5. After procedure is complete, if your tablet don't start automatically in CWM, remove USB and shut down tablet by holding POWER button for 8 seconds (you will hear silent *click* sound from tablet as signal it's off). Now download CWM Base from this XDA post put tablet in download mode (VOL+ and USB CABLE) and flash this recovery (run RKAndroidTool.exe, push Flash ROM button). It is very same recovery from this ROM, but after this flashing is finished, tablet will boot into CWM automatically on it's own.
6. Now install ZIP files from after_install folder via CWM recovery. Format NAND is required if you first time using 2GB Data mod, and int2ext is required for some devices which reported switch between internal and external SD card. You must use an external SD Card for flashing ZIPs and search for files in both internal and external sd card in CWM as you still dont know how CMW see your SD card.
7. Reboot System. All done!
DOWNLOAD
Note: If you are used increase /data to 2GB MOD before, you can just install this firmware via RKAndroidTool. If your /data partition was 1GB before, you may need to install patches from folder after_install via CWM recovery.
This thread shall strive to be an all-in-one thread for the phone O+ 8.31z. And to be noob friendly as well. As of now, I have only very limited knowledge so I'll be adding stuff as I go.
Phone Specs:
CPU: MT6572 1GHz Dual-Core
Architecture: ARM Cortex-A7
Clock Speed: 598 MHz - 1.00 GHz-----
GPU Vendor: ARM
GPU Renderer: Mali-400 MP
UBIFS File system
Android: 4.2.2
Kernel Architecture: armv7I
Default Governor: Hotplug
Screen Res: 320x480
Density: 160dpi
RAM: 219MB
Internal Storage: 0.16GB
Sensors: Proximity, Light, 3-axis.
Click to expand...
Click to collapse
For drivers, connect your phone to windows PC, download PDANET (search for it on google) and let it install drivers for your phone.
Preface: TOOLS and THREADS TO BE USED
1. MTK Droid Root and Tools by xda senior member rua1. Press thanks in his thread! Compatible with Windows and Linux(with wine).
2. SP Flash Tool Credits to Khonshu of china.phonearena. I downloaded v3.1344. Here's an xda thread on what you can do with it: Click Me! Troubleshooting SP flash tools: .Click here!
3. Pdanet for Windows drivers
Chapter 1.0.0: HOW TO ENABLE PHONE MODES
Steps:
1.1.0 For MTP mode
1.2.0 For ADB mode
1. Go to Settings>About Phone
2. Click Build number about 6 times, quickly. Developer Options should now appear.
3. Go back to settings then click Developer Options. Here you find so many things you thought didnt exist
4. For now, we only check USB debugging. When a pop-up appears, just click "ok". Done!
1.3.0How to enter recovery mode: (Credits to phcorner.com O+8.52 thread)
Method 1:
1. Remove battery and reinsert.
2. Press Volume Up and power key simultaneously.
3. A blank screen with an android lying down and a red exclamation triangle should appear now.
4. Press Power button once, and the menu will appear.
5. To navigate, Power: Show/Hide options. Vol UP: Confirm. Vol Down: Scroll.
6. When done, reboot system to exit.
Method 2: When you're on a PC,
1. Connect Phone in USB debugging mode.
2. Open cmd (or terminal then change directory to your adb folder) and
Code:
adb reboot recovery
1.4.0 For Phone test mode
1. Press Volume Down and Power simultaneously.
2. Choose among the options.
3. When done, remove battery to exit.
(It seems like reinserting the battery and doing VolDown+Home combo does not do anything else)
1.5.0 For fastboot (aka bootloader) mode
Requirements: Since you want to use fastboot, then you must be on an adb configured computer
1. Open cmd (or terminal then change directory to your adb folder)
2.
Code:
adb reboot bootloader
3. Wait for the phone. Done!
Chapter 2.0.0: ROOTING
Why root?
There are many methods to rooting. I will list what I know might work. I'm 99.9% sure the first one works (given you are not stuck in a bootloop.)
2.1.0 Shuame ROOT GeniusDownloadInfo: This is a one-click PC application. I have used this in Windows 7 32-bit and in lubuntu 13.10 and it works. If your phone is not an MT6572 I'd still recommend that you try this as it can root almost anything! It installs Kinguser as the superuser app.
2.1.1 Requirements for Windows PC: A Windows PC, a USB cable, your phone, and a fully downloaded shuame root genius. No drivers needed as shuame root genius already installs them for you.
2.1.2 Requirements For Linux PC users: A linux PC, a USB cable, your phone, a fully downloaded shuame root genius, WINE, and adb (I might be wrong here, but get this: Since drivers are not really used, we need our phone to be given adb permissions by linux, or else shuame will not be able to recognize your phone. So you will probably need to have adb installed first, just to be sure.)
For info on how to do that, check here: Click Me!
Also, shuame root genius does not display well under wine in my case, but the buttons were clickable anyway so it still works. From here, it's pretty much the same procedures.
2.1.3 Steps:
I made a visual guide here:
And in text, here:
1. Connect your phone to PC using the USB cable and go to MTP mode. See Chapter 1.1.0 for help
4. Enable USB debugging. See Chapter 1.2.0 for help.
5. Open Shuame Root Genius. It will connect to your phone automatically and install drivers for about 3-5 minutes. (No more driver installation on linux PCs)
6. Click "Root it". You should now see your device as rooted. And if you click back, you can unroot. Done!
2.2.0ErootDownload/help threadInfo: Another tool by Chinese developers. I tried it on my lubuntu 13.10 WINE and it worked flawlessly! I'm pretty sure it'll work on a Windows PC as well. It installs superuser by clockworkmod.
2.2.1 Requirements: See 2.1.1 and 2.1.2.
2.2.2 Steps:
Visual guide
Textual guide here:
1. Connect your phone to PC using the USB cable and go to MTP mode. See Chapter 1.1.0 for help
4. Enable USB debugging. See Chapter 1.2.0 for help.
5. Open eroot. It will connect to your phone automatically.
6. Click the root button. It's the only button anyway. When you have rooted successfully, you can click the 解除 button to unroot if you wish. Done!
2.3.0 MTK Droid root and tools
Connect Phone in ADB and MTP mode.Download/Help thread can be found in PrefaceRun MTK Droid Tools. Wait for it to recognize and establish a connection with your phone. This should appear after a minute:
Take note that a blue rectangle on the lower left means you're still not rooted. Press ROOT.
Wait for about three to five minutes. In my case, MTK Droid tools crashed So I didn't see a superuser app.
But I downloaded root checker and sure enough, my phone was rooted. Only the superuser app was missing.
I also opened MTK Droid tools again and saw a green rectangle (which means I am rooted :victory: )
So now, technically, you are rooted. But we still need a superuser app, so I downloaded a superuser app that I liked and updated the binary. I downloaded SuperSU by chainfire from the play store. Done!
or, you could try the superuser button in the root, backup, recovery tab. I didn't try it though
2.4.0 Other stuff you might wanna try or know about if none of these methods worked for you, here: http://forum.xda-developers.com/showthread.php?t=2523814
Chapter 3.0.0: RECOVERY STUFF
3.2.0 How to backup stock recovery
3.3.0 What is clockworkmod recovery?
3.4.0 What is carliv touch recovery?
UPDATE: I think O+ 8.31z was primarily sold for the Philippine Market; as such, I may be in competition with more Philippine based forums such as symbianize and gsmworldfive. Therefore, I think it would be best that I leave the two 8.31z links here and discontinue any plans on improving this thread. Here they are:
http://www.symbianize.com/showthread.php?t=1094034&page=10
^this link contains a SPFT flashable pre-rooted clean stock rom.
http://www.gsmworldfive.com/forum/showthread.php?t=37787
^this link uses the SPFT method too, but the rom here has much more root apps installed already, like swapper, greenify, auto ram cleaner etc. (Oh, stock keyboard was also taken out).
Both confirmed working to bring back a bootlooped 8.31z. I prefer the first one though
Until next time! My dad plans to sell this phone soon so I guess I won't be learning how to make custom roms anytime soon yet... Hope you guys are doing well
Click to expand...
Click to collapse
UPDATE: Since my dad hasn't sold it yet, I'm playing with it again. There is a Filipino facebook group that is dedicated for 8.31z users. I think they have custom roms ported there.
Click to expand...
Click to collapse
Chapter 4.0.0: ADD INIT.D SUPPORT TO STOCK ROM
Check here! http://forum.xda-developers.com/showthread.php?t=1933849
I haven't personally tried any one yet. You are always proceeding at your own risk
Tweak for speed, battery life, and other cool/useful stuff.
Chapter 5.0.0: Speed
There are tons of stuff to speed up your phone, and they're not just limited to one specific phone. So bring in the list.
1. Use Greenify (find it in the play store)
Requirements: Root (optional for auto-hibernation. Highly Recommended.), Android 4.0+
You may greenify stuff like Guardian if you are not using it, or maybe the FB app too. Saves some battery and gives a little free ram for better multitasking.
2. Disable fancy window animations and transitions
Go to settings>developer options and disable the three animation options to animation off.
3. Use a cpu controller like No Frills CPU control (find it in the play store)
Controls how fast or slow you want your CPU to go. Default Governor is hotplug.
For a faster phone, set the governor to performance. It sets the CPU to scale to the max that you set. Use when you are playing heavy games.
For a battery saving phone, set the governor to powersave. It sets the CPU to scale to the min that you set. Use when you only plan to use really light apps.
For a balance between performance and battery save, it's probably best to go back to hotplug since it can turn the second core on or off depending on your usage.
4. Tweaks and Scripts
Info: Tweaks refers to build.prop tweaks. Scripts refer to init.d scripts. So this is a two-part thing. Adding build.prop tweaks, and running init.d scripts. Some do this two-part thing simultaneously in one flasher. Others, separate the tweak part from the script part. The reason they do this is because phones running from stock usually do not support init.d scripts, but only build.prop tweaks.
Our 8.31z cannot support init.d (yet) so for now we will only do the tweak part.
1. Tweak part of [ SCRIPT | TWEAK ] ◢ Project Fluid™ ◣ by Spex. [size="+1"]Recommended.[/size]
Please press thanks in his thread! This is not my work.
Project Fluid has a separable tweak part. I didn't apply all as some are optional. So I just applied it and what happened?
Using Antutu X Benchmark
Before Project Fluid Tweak: 7334
After Project Fluid Tweak: [size="+1"]9264!!![/size]I only selected some of the tweaks (i.e. I didn't use "unlock with volume rocker and other stuff like that) Here's what I added to my build.prop. Feel free to do the same.View attachment 2785183
How to:
1. Open ES explorer (I'm using latest version)
2. Copy the tweaks that you want to add to build prop. Find the tweaks in spex's post or copy my selected tweaks. And thank spex in his thread.
3. Press the menu button on your phone. Click tools. Click on for root explorer and grant root permissions.
4. Click root explorer. Click Mount R/W. Choose R/W for /system and click ok.
5. Navigate to /system and open build.prop with ES note editor. Press the menu button on your phone and click edit.
6. Now paste the tweaks into the build.prop file. Or type them manually
7. Reboot and enjoy!
2. Tweak of Dash-M Script and tweak by myaservip
Please press thanks in his thread! This is not my work.
Dash-M has a tweak part and a script part too. If you want to try Dash-M Tweak, go to his myaservip's thread and download the zip, transfer to the root of your sdcard, go to recovery mode, and flash from there.But personally, Project Fluid's tweaks are more complete. I haven't tried Dash-M script since we haven't added init.d so stay tuned.3. Script and Tweak of ★ [MOD] ◢ PurePerformances™X ◣ | Golden Edition | Scary performances on Android by Jeeko
Please press thanks in his thread! This is not my work.
This is a single inseparable script and tweak in one so we cannot use it yet. Stay tuned.[size="+1"]General reminder: Tweaks and scripts are usually not mix-able. So remove one before trying another.[/size]
Chapter 6.0.0: Cool/Useful Stuff
1. Xposed Framework and Modules.
Our device can definitely benefit from Xposed modules! 4.2 is capable of running these.
2. TouchPal Keyboard
A good replacement to stock keyboard. Contains different keyboard layouts and support for tons of languages! And if you have experienced the keyboard not pressing the right button, this might be a better replacement.
3. Moreto come.
Hi there fellow Filipino! Please continue what you're doing. I can help you in some way in installing CWM-esque recovery tool for our phone. As it is a UBIFS-type system, many have said that it's a tricky job. A lot have failed but some did it successfully like me. I followed this tutorial from here
chinaphonearena.com/forum/Thread-CWM-For-All-MTK-Easy-Magic-CWM-MT6575-MT6515-MT6577-MT6517-MT6589-MT6582-MT6592
Sorry I can't post links yet because this is a new account.
So I was able to boot into recovery, but I stopped there until someone successfully restore our phone from a backup (even if it's just stock ROM)
Cheers! You should try it!
PS. I tried your build.prop and benchmarked afterwards, only to get about 7100+. HOW DID YOU GET TO 9K?! Please indicate if you have a lot of apps and is greenify and that cpu tool the only apps you're using for speed?
After sometime though, my phone got slow, so I deleted the added lines in build.prop and speed went back on. What's happening?
Successfully enabled init.d! I used term-init. It was so easy! Just a matter of minutes. Now, to try some scripts...
Edit: Currently backing up using Carliv Touch Recovery, the MTK compatible CWM recovery tool, before going further. Will try restoring it later. If it is a success, then Chapter 3 is done!
zildjosh97 said:
Successfully enabled init.d! I used term-init. It was so easy! Just a matter of minutes. Now, to try some scripts...
Edit: Currently backing up using Carliv Touch Recovery, the MTK compatible CWM recovery tool, before going further. Will try restoring it later. If it is a success, then Chapter 3 is done!
Click to expand...
Click to collapse
Hi! I've been a little busy lately haha. I'll get back to updating this thread in a week or so
Are you new to this stuff? Or have you had previous experience before? Seems like you're going pretty well! I don't know much about this phone of ours yet, maybe you know more than I do
Update: So my O+ phone wasn't sold, and now I plan to use it. Just tested Carliv 2.4 using Yuweng's Auto Magic Installer, and it installed! Restore doesn't work though. And don't advance restore > restore system. You'll get a bootloop haha.
HELP
What is the best CWM or TWRP on my o+8.31z, newbie here. and How? any Help. Thank you for rooting process. as well.
Sory
Sorry if I'm wrong forum, I just want to ask, is there any one can help me to do the rooting of the device Himax H TWO with the following specifications
CPU: MT6735 OCTACORE @ 1.3GHz
GPU: Mali-T720 MP3
Screen : 5.0 inc 720 x 1280 pixels (~294 ppi pixel density)
Android : Marshmellow with lewa os
Karne : 3.18.19
Ram : 2GB
Internal memory : 16GB
I HOPE there that will help me to do the roots and modify twrp for this device
Thankyou fery much
nothing working for MT6572 device (not that O+) for root.. tried all one click or simple root methods nothing working
MTK Droid root and tools waiting for hours and hours and nothing happens it just wont root my mobile idk what to do
{
"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.2 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!
Thanks!
I think there will be more people. Need to run a better window.
Windows7 64bit, part of the code.
Now, I have a simple editing of it.Make it look good.:laugh::laugh:
Download link:
https://mega.nz/#!nQBiDL7J!aDd9BhKtRw2tuYrpD7fImUXMn_Hl-qmUzwqKY13bYTc
Getting an error
FAILED(remote: oem unlock is not allowed)
Skies/SANKE said:
Thanks!
I think there will be more people. Need to run a better window.
Windows7 64bit, part of the code.
Now, I have a simple editing of it.Make it look good.:laugh::laugh:
Download link:
https://mega.nz/#!nQBiDL7J!aDd9BhKtRw2tuYrpD7fImUXMn_Hl-qmUzwqKY13bYTc
Click to expand...
Click to collapse
Well, I've looked at your edit and I don't understand what looks better than mine... It might be subjective though...
Pikezer1337 said:
Getting an error
FAILED(remote: oem unlock is not allowed)
Click to expand...
Click to collapse
Will investigate this problem and I hope I will get a solution fast
Edit: The information from this link might help with your problem.
I am running Arch Linux.
My shell is ZSH.
I downloaded and extracted, and ran zsh (filename).
I wanted to go with option 1 and got this
Code:
[= LG Nexus 5X - Multi Tool v0.1 - Linux =]
[1] Unlock bootloader. (via fastboot)
[2] Relock your bootloader. (via fastboot)
[3] Flash Recovery menu. (via fastboot)
[4] Backup and restore. (via adb)
[5] Recovery sideload. (via adb)
[r] Reboot menu.
[l] Logging menu.
[q] Quit.
Select your option:
1
menu:23: command not found: bootloader
127 [email protected] ~/Android/5XMultiTool.v0.1 % :(
any ideas?
paOol said:
I am running Arch Linux.
My shell is ZSH.
I downloaded and extracted, and ran zsh (filename).
I wanted to go with option 1 and got this
Code:
[= LG Nexus 5X - Multi Tool v0.1 - Linux =]
[1] Unlock bootloader. (via fastboot)
[2] Relock your bootloader. (via fastboot)
[3] Flash Recovery menu. (via fastboot)
[4] Backup and restore. (via adb)
[5] Recovery sideload. (via adb)
[r] Reboot menu.
[l] Logging menu.
[q] Quit.
Select your option:
1
menu:23: command not found: bootloader
127 [email protected] ~/Android/5XMultiTool.v0.1 % :(
any ideas?
Click to expand...
Click to collapse
The problem should be fixed in the V0.2, the Linux and MAC versions are not tested before posting, so bugs could still be around there...
added to index
Hi all, imusing linux and just tried to unlock my 5X. it worked but my question is, it is normal that it formated automatically?
after reboot, i have to start all over again with my account and setup.
Yes it's normal
Thanks mate, I'm new with nexus devices. One last thing, do I have to locked again or its OK leave it like that since on every reboot its showing me that I'm unlock. Sorry and thanks
Sent from my Nexus 5X using Tapatalk
You can leave it like that as long as you can deal with that message on every boot. If you lock it, you would have to unlock (and wipe) again if you ever want to flash anything again. Personally, unless you want to stick with the stock ROM OTAs, I'd leave it unlocked.
Would you confirm your Tools Re-Lock feature works with Custom Recovery (TWRP) without bricking device?
Born<ICs said:
Would you confirm your Tools Re-Lock feature works with Custom Recovery (TWRP) without bricking device?
Click to expand...
Click to collapse
Usually, locking your device does not brick anything, if everything works fine before locking, everything will work fine after locking, you are only limited after locking.
Lexmazter said:
Usually, locking your device does not brick anything, if everything works fine before locking, everything will work fine after locking, you are only limited after locking.
Click to expand...
Click to collapse
.
Would you mind answering the question?
With custom recovery, TWRP, installed and unlocked what happens when you use your Tool to go back to Lock?
Have you tested?
Thanks
Born<ICs said:
.
Would you mind answering the question?
With custom recovery, TWRP, installed and unlocked what happens when you use your Tool to go back to Lock?
Have you tested?
Thanks
Click to expand...
Click to collapse
To be honest I never locked my bootloader, didn't found a reason to, so I didn't tested.
But technically speaking, the only thing that happens is that you cannot flash other custom recoveries (fastboot stuff basically) without unlocking again and wiping all the stuff on your device.
OK, thank you. ReLocking to flash factory image was what I was thinking. I read doing so can lead to bootloop. Just trying to make note of things to avoid doing.
Cheers
You can lock and unlock your bootloader as much as your heart desires without consequence
skulldreamz said:
You can lock and unlock your bootloader as much as your heart desires without consequence
Click to expand...
Click to collapse
Well, wiping your data partition can be a pretty big consequence...
-edit-
You used to be able to use BootUnlocker for Nexus Devices to lock and unlock the bootloader from within the OS, but it looks like that's a no-go on the 5X...
I'm new to the nexus devices, but if I unlock the bootloader and root, will I loose both if I take an OTA update?
owenrg said:
I'm new to the nexus devices, but if I unlock the bootloader and root, will I loose both if I take an OTA update?
Click to expand...
Click to collapse
You will definitely lose root. I don't know about the bootloader since I've never taken an OTA, but I would guess that, unless there are bootloader changes in the update, your bootloader would stay unlocked. And to my knowledge the bootloaders are pretty much never updated for incremental OTAs.