Hello Everyone
I am starting this thread as a COMPLETE GUIDE FOR YOUR DEVICE which would include almost all aspects for your device.
BASIC ANDROID DEVELOPMENT
REFER TO THIS GUIDE FOR BASIC ANDROID KNOWLEDGE AND DEVELOPMENT PROCESS
ALL ROMS,GUIDES, MODS, TUTORIALS LIST CLICK
ALL ROMS,GUIDES, MODS, TUTORIALS LIST
TABLE OF CONTENTS
1. UNLOCK BOATLOADER
2. ROOT YOUR DEVICE
3. FLASHING TOOLS AND GUIDE
4. DRIVER ISSUES
5. MEMORY PROBLEMS
6. TA BACKUP
7. OFFICIALLY UNLOCK YOUR BOOTLOADER (Not available now)
8. FAQ
9. GUIDES LIST
All Credits to the developers for their tools!
HTML:
I take no responsibility for world wars, broken phones, flying machines,
UFO invasions, bricked phones, dead sd card . If you agree to go ahead with this,
it is your choice and no blame should come to any developer/contributor whatsoever
PREREQUISITE
-USB DEBUGGING
For this guide to work, make sure usb debugging is enabled.
Go to Settings> About>Build Number> tap it 7 times and "Developer Options" should appear in settings.
In Developer Options> Enable USB Debugging.
-USB DRIVERS
For these I suggest use Flashtool. Check Drivers guide below for more information
REFER FAQ
New Method to Root M4 Aqua Dual E2363 *26.1.B.1.85 Found on Locked Bootloader. Please click on new method under Root How to root 5.0 Lollipop with RootkitXperia AND CHECK HIS TWITTER FOR UPDATES
STEP BY STEP NOOB GUIDE FOR TWRP AND ROOTING
BOATLOADER
YOU CAN UNOFFICIALLY UNLOCK YOUR BOOTLOADER HERE
You first need to unlock your bootloader before you can root your device.
@lucaszell for the amazing guide. @Sam205 for pointing it out in M4 Aqua forum
1. Go to Sony Website HERE
2. Choose M2 or M and complete the steps to get your KEY
3. Install Flashtool
4. Go to Settings - About phone - Status
Scroll to down to see serial number. (device name)
Amended for clarifications
1.: Go to the folder where Flashtool is installed. Usually C:/Flashtool
2.: Open the folder named "Custom"
3.: Open the folder named "Mydevices" (if it exists, in my case Flashtool version 0.9.18.4) (You may create if it doesnot)
3b.: In the newer Flashtool, you need to put the folder in "C:\Users\<username>\.flashTool\registeredDevices" in step 3.
That is, if you've picked the default for your flashtool home folder or you can choose manually.
4.: Create A New Folder and Rename the folder with your device code. Refer to Obs2 how to find your device code
5.: Open the folder created previously
6.: Create a new text file and rename it as ulcode
7.: Paste your unlock code and save it in the text file
8.: Open Flashtools and try the BLU option again.
Obs 1: the step #3 I think it depends on your Flashtool version, because it wasn't mentioned at the solution
Obs 2: at the step #4 is mentioned your device code. your device code is showed in the log when you click the button BLU, at the "Current device", after your device model.
Search a line like:
09/045/2015 23:45:08 - INFO - Current device : C2104 - AB100C2DE3 - 1272-4136_R5B - 1269-5420_15.3.A.1.17 - WORLD-a_15.3.A.1.17
in this case, the device code is AB100C2DE3 and this should be the new folder name (step 4)
ROOT
NEW METHOD by @cubeundcube for locked bootloaders
OLDER METHOD
@husam666 Successfully found how to root the device. Please refer HERE
WORKING ON DEVICE MODELS
[E2303, E2353, E2333, E2306]
husam666 said:
TWRP Recovery for M4 Aqua (No gui, command line only)
This is for E2303 I didn't test on other models, feel free to do so but I take no responsibility whatsoever if anything happens
This will disable OTA updates, if you want them back you can flash the FOTA kernel with FlashTool
Confrmed to be working on those variants:
E2303, E2306, E2333, E2353, E2363
Ok here it is thanks to @jeffreyvh kernel we can finally flash zips however we have 3 catches:
1. No GUI (Sony's fault until they provide full sources for our phones, we're stuck here)
2. You have to mount /system, /data and /cache manually (Working on it)
3. No external SD card support (working on it)
No problem? Cool..
Ok here's how to do it:
0. You need unlocked bootloader <-- Click here to see how
1. Download the recovery.img
2. Flash the recovery file with fastboot
Code:
fastboot flash recovery recovery.img
3. Pull the cable turning off your phone.
4. Press the power button + volume down, when the phone vibrates, press the volume down button repetedly.
5. The Sony logo will disappear and you'll get a black screen (It's okay, congrats you've now booted twrp)
Now for the magic:
Connect your cable, make sure you have ADB and drivers installed.
In your terminal or dos window type:
Code:
adb shell
you'll get a prompt like ~ #
type these three commands:
Code:
mount -w /dev/block/platform/7824900.sdhci/by-name/system /system
mount -w /dev/block/platform/7824900.sdhci/by-name/userdata /data
mount -w /dev/block/platform/7824900.sdhci/by-name/cache /cache
Now that you have the partition mounted you can flash your zip files:
We don't have external SD card support so for now we're going to stick with sideload
type:
Code:
twrp sideload
adb shell will exit, it's okay now we can install the zip file like this:
Code:
adb sideload <path_to_zip>
path to zip on your computer without the < >
so if you downloaded superSU on C:\Downloads\SuperSU.zip
you type
Code:
adb sideload C:\Downloads\SuperSU.zip
when you're done type:
Code:
adb reboot
and pull the cable
For Rooting:
Download SuperSU flashable zip from here https://download.chainfire.eu/696/SuperSU
and flash it like explained before
good luck
Special Thanks:
@jeffreyvh
@alby_var
@Hnk1
@zw3n
@S7relok
@dexter93
@babydolll @Sam205
The TWRP team and everyone who made this possible
Download Links:
http://d-h.st/wuGD
XDA:DevDB Information
M4 Aqua TWRP, Tool/Utility for the Sony Xperia M4 Aqua
Contributors
husam666
Version Information
Status: Testing
Created 2015-09-11
Last Updated 2015-09-17
Click to expand...
Click to collapse
Last Updated 22-2-2016
SONY OFFICIAL TOOLS
Sony PC Companion
This tool is officially from Sony and can be used to repair your drive.
You can also use this for your phone backup.
http://support.sonymobile.com/global-en/tools/pc-companion/
It is for those who do not prefer unofficial ways!
EMMA
Refer to it here for instructions and download:
http://developer.sonymobile.com/services/flash-tool/how-to-download-and-install-the-flash-tool/
FLASHTOOL
This tool is used to flash stock/custom kernels/recoveries to your device
Download link
http://www.flashtool.net/downloads.php
Instructions
I found this guide very helpful and thus you can refer it here :
http://forum.xda-developers.com/showthread.php?t=928343
SOME CONSIDERATIONS :
1.Make sure you choose the FTF file for your device or you can risk bricking your phone forever.
At the moment, there are no FTF files so you will need to be patient.
2. Make sure all drivers are properly installed
3. To boot into flashmode/fastboot, you will need to turn off device.Hold volume up OR volume down and then connect your device while holding the volume key.
Volume up would take you to flashmode while volume down would take you to fastboot mode. Remember, you will need fastboot/flashtool drivers before you can flash anything.
here is another guide for you just as reference.
http://forum.xda-developers.com/xperia-l/general/xperia-l-how-to-flash-tool-unlocking-t2337955
However if you have still issues , I can rewrite the guide.
ALL DRIVER PROBLEMS SOLUTIONS
I have seen some posts where users are having difficulty connecting Xperia M4 to their PC or ADB. Therefore, I am writing this guide to help you all.
The guide was prepared using Windows 7 Ultimate but should work with Windows XP and Windows 8.
Firstly, Sony uses a different driver for their Xperia devices and therefore, sometimes you are unable to install drivers for your devices especially for ADB commands.
IF YOU ARE LUCKY
There are few ways to get around to install drivers for your device. The most convenient and easy is you plug in your device and wait for automatic detection of your device. Make sure you have USB connected as MTP in MY XPERIA in SETTINGS of your phone. The device drivers would be automatically installed by Windows update.
METHOD
If suppose you can not install your drivers, connect your xperia and then on your PC, go to My computer > Properties>Device Manager.
You should see an undetected hardware with a yellow exclamation mark over it. Open it and click on update my drivers. Then choose GOOGLE DRIVERS by choosing hard-drive. This should install the drivers for you. If this doesnot work. Try the attachment with the post where the drivers are modified to work with Sony Xperia Devices.
Follow the same steps but this time choose the attachment folder to search for drivers. It might say, the drivers are not verified. Just Ignore it and carry on installing them. You will need to unzip these files.
IF suppose you do not see any exclamation mark while you connect your xperia. Just go to control panel and add new hardware. Select, I will choose my device and then install from hard-disk. Select the folder where you have unzipped the files and you are good to go. The name of new hardware is not important as windows will read the drivers files and install drivers for Xperia.
This will install all drivers for your device. If there are two or more drivers while installing them. Redo the steps and install all of them individually.
Suppose your ADB still doesnot work, then
FOR ADB DRIVERS :
Download the ADB Universal Drivers and connect your device. Then hit install. The ADB drivers will be automatically detected and installed.
Further, if these tricks fail, you can delete the unknown driver from your control panel and then try finding it again by using refresh button(scan for new hardware changes) in device manager.
Another trick is to click on unknown drivers and delete them. Connect your phone and restart your phone. Then scan for new hardware in device manager. The drivers should be installed for your device.
If still there are some problems, I will try to help you out.
DOWNLOAD LINKS
DOWNLOAD GOOGLE DRIVERS FOR MTP/ PC ETC
https://dl-ssl.google.com//android/repository/latest_usb_driver_windows.zip
DOWNLOAD UNIVERSAL ADB DRIVERS HERE :
http://adbdriver.com/upload/AdbDriverInstaller.exe
UPLOADED FILE : Sony Xperia Drivers for ADB.
UPDATE (EASIEST METHOD) :
Use flashtool drivers to install adb/fastboot/flashboot drivers. This is the most simplest and easiest method I have come across lately.
Simply download flashtool
http://www.flashtool.net/index.php
Go to folder where you have downloaded it. Usually C:/flashtool/drivers.
Select the drivers for your particular device. I use universal for all three types of drivers. It is helpful to boot into fastboot/Flashtool before installing the drivers but not necessarily.
FOR LINUX DRIVERS :
(No drivers required)
In your Xperia go to :
Settings > Xperia > usb connectivity > usb connection mode
Select Mass storage mode (MSC) > Press OK
Then plug your phone with your SDCARD inside
Try this guide if that does not work,LINUX DRIVERS GUIDE
Good Luck
Still problem ? Quote me back
IMPORTANT
On windows 8 and above you will need to disable DRIVER VERIFICATION in your windows settings to successfully install your drivers
Memory, Storage and Debloating Problems
INSTRUCTIONS
LIST
SD MAID
ADVANCED TASK KILLER
TITANIUMBACKUP
GREENIFY
HOW TO KEEP RAM CLEAN AND KEEP YOUR PHONE BUTTER SMOOTH :
The phone MUST be fully rooted and all the recommended applications isntalled. They can be easily found on the Google Play. Links are provided for reference. In this guide I have used all the PRO (paid) applications. The Free versions will do fine but It is expected that some options are disabled in the free version. You can help developers by your contribution to their work
ADVANCED TASK KILLER
Advanced task manager is used to kill tasks running in the background.
Add advanced task killer widget to your home screen. Every time you need to kill background applications, just tap it once. This way all the applications in the background are periodically killed and thus, more RAM is available to your system and thus increased performance.
GREENIFY[ROOT]:
This application/system basically looks for applications running in the background. These background processes might slow down system. Furthermore, these increase the battery usage and reduce battery time. Greenify detects the background applications and hibernates them. This not only speeds up the phone but also saves battery.
SICK OF BLOATWARE?
TITANIUM BACKUP [ROOT]
Titanium backup is used for backing up your applications and system files. This can also DELETE applications from your ROM permenantly.
I recommend you make a backup with Titanium backup before uninstalling the files. REMEMBER, IF YOU UNINSTALL A SYSTEM FILE, YOU WILL NEED TO REFLASH YOUR ROM and you will end up in BOOTLOOP.
I will paste a screenshot to tell you which applications can be deleted easily.
OTHER SETTINGS :
Go to your settings>developers tools> background limit> use as less as you want. THIS WILL INCREASE USER EXPERIENCE
HOW TO SWAP EXTERNAL MEMORY & INSTALL AS MANY GAMELOFT GAMES AS YOU WANT
Many of you are having problems installing many games in your internal memory and can only utilise 4 gb of your memory. This means only 3 gameloft games. Thus I will briefly help you with memory issues related to Xperia M4
This one is very easy. Install Folder Mount and it will do the rest. Remember with free version, you can only mount 3 folders. The application is frequently updated and it has great support for Xperia M4.
Basically this application creates a link folder in your SD card which is detected by games automatically once fully setup. It also moves your files into your SD card and this saves your EXTERNAL MEMORY FULLY. You can install as many games or applications and link them to your SD card. Its that simple.
Use App analyzer option to mount folders. Manual folder mounts are not recommended!
Go to app analyzer>Select Game> Creat pair(s)>Move files as well> Mounted
Make sure Folder Mount is ticked green before running games.
INTERNAL MEMORY PROBLEMS
Internal memory not adding up? Unknown files hogging your space.
This can be managed by SD MAID and TITANIUM BACKUP.
With SD Maid, you can free a lot of space. It has many cool features. I use the Corpse finder and System cleaner, App Cleaner.
You may also try app cleaner if you like.
Go to CORPSE FINDER>FIND FILES>DELETE ALL FILES. It will take some time looking for files.
SYSTEMCLEANER>FIND FILES>DELETE ALL FILES. It will take some time looking for files.
TITANIUM BACKUP IS USED TO RELOCATE THE MEMORY THAT IS MISSING.
Titanium backup> MENU > clean up the dalvik cache
This will also give you back some INTERNAL MEMORY BACK.
LIST OF APPS SUCCESSFULLY REMOVED WITHOUT ANY PROBLEMS
Active Clip
Calculator (small app version)
Email
Movie Creator
OfficeSuite
PlayStation Video
Sketch
Small App Framework
Small App Launcher
Small App Widget
Small Apps Manager
Smart Connect
Support
Timer (small apps version)
Touch Block
What's New
Music
Music Visualization Wallpapers
Podcast
Video
Visualiser (has same icon as Sony's Music in Titanium Backup)
Refer Screenshots
{
"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"
}
HOW TO MAKE A TA PARTITION BACKUP.
1. Download the latest version of Backup TA from here DOWNLOAD HERE
2. Extract the ZIP file to a folder location of your choosing.
3. Navigate to the folder location of Backup TA.
4. Make sure no other script or application which is using ADB is running.
5. Make sure the device is booted in normal mode (the way you normally use it).
6. Run Backup-TA.bat
7. Read the last paragraph of the license before continuing.
8. Read the information and follow the instructions given by the tool.
Someone pointed out that the script needs root to work.
UNLOCK bootloader from Official Website[ Sony doesnot support unlock bootloader of this device yet
However, Once supported, the following method MUST work!
OFFICIAL SONY WEBSITE TO UNLOCK BOOTLOADER
Please note! It will only be possible to unlock the boot loader for certain releases of this model. You can check if it is possible to unlock the boot loader of your device by checking the service menu.
Open the Contacts app.
Click the menu button in the top right.
Click Settings.
Long press (for about 5 seconds) somewhere in the empty space just above soft key bar, and then release your finger. A button named Enter service code will then appear in the same area (this may take a few tries).
Click Enter service code. A dialler will appear.
Enter *#*#7378423#*#* in the dialler.
Tap Service info > Configuration > Rooting Status. If Bootloader unlock allowed says Yes, then you can continue with the next step. If it says No, or if the status is missing, your device cannot be unlocked(bootloader).
If your bootloader can be unlocked, proceed to the above website and follow the on screen instructions. You do not need to download full adb , just download the platform tools attached with this guide.
FOR MY REFERENCE. IGNORE
Just for my reference. Ignore it
These do not work.
Refer to first post for prerequisites.
ROOT CONFIRMATION
It was false root confirmation. You are more than welcome to try to find which method works for you from the following.
I have few confirmations of root working on Xperia M4 using this tool. Ignore what it says about kitkat or anything. Just make sure you got USB debugging enabled and drivers installed.
http://rootgenius.com/
Other methods that might work.
METHOD 1 (Kitkat/Lollipop. Unlocked/Locked Bootloaders)
This method has been implemented many a times by me and it has yeilded high results on different devices I have worked on.
We will replace the KingUser (chinese app like SuperSu) with SuperSU so you do not need to worry. You can also factory reset in order to be completely certain that no extra scripts are left in your system if you have any doubts about privacy.
1.Install iRoot (also called Vroot) (in chinese). The Chinese version is on 1.83 while the english translated is still on 1.78. Use the Chinese one.
http://www.mgyun.com/
2.Run iRoot app from PC. Wait till it is complete. You will have root with some system cleaner app with King user. Maybe you be successful with full root. Check Root Checker.
METHOD 2
It is also a chinese method and it also has been used by me for few devices. Many people have problems trusting it, but it installs superSU so I think I would not be concerned much. Feel free to try
1.Install KingoRoot
http://www.kingoapp.com/
2. Run the script and see if it helps. Wait about 15 minutes .
METHOD 3
1.After running iRoot for explort, run KingoRoot. Wait about 5-15 minutes as it would go on forever if it is not successful in rooting your device.
2.Close afterwards.
3. Run Iroot and Kingoroot together. Wait till it is restarted and you acquire root with KingUser.
The trick here is the moment, System is being restarted (device), Kingoroot pushes some scripts and together they are a deadly combination.
To GET SUPERSU if you got any other app instead for ROOT
1.Install supersu from market.
2.Update binaries
3.Restart.
Does not work ?
Use Beta SuperSU instead versions 2.48/2.49.
Install apk and try updating binaries.
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
METHOD 4
1.Download towelroot apk.
2.Install and run
Check FAQ
https://towelroot.com/
METHOD 5
SUPERONECLICK ROOT
Check FAQ
http://forum.xda-developers.com/showthread.php?t=803682
METHOD 6
Try the z4root app
Check FAQ
Download here
http://z4root.en.uptodown.com/android/download
METHOD 7
http://www.oneclickroot.com/
Install the programme on the PC and run on screen instructions.
METHOD 8
Download Motochopper and try it
http://forum.xda-developers.com/attachment.php?attachmentid=2004316&d=1369929448
You will need to update SuperSU in these cases as well
METHOD 9
Use DoomLord Tool Kit.
Enable USB debugging and run the script. Start with the latest script v17 and carry on with older version scripts. You may need to update SuperSU/Superuser file to latest 2.49 Beta. Link in FAQ
PLEASE DO NOT MIRROR MY FILES!
NEW:
DooMLoRD_Easy-Rooting-Toolkit_v17_perf-event-exploit.zip
OLD:
DooMLoRD_Easy-Rooting-Toolkit_v16_perf-event-exploit.zip
DooMLoRD_Easy-Rooting-Toolkit_v15_perf-event-exploit.zip
DooMLoRD_Easy-Rooting-Toolkit_v14_perf-event-exploit.zip
DooMLoRD_Easy-Rooting-Toolkit_v13_perf-event-exploit.zip
DooMLoRD_Easy-Rooting-Toolkit_v12_perf-event-exploit.zip
DooMLoRD_Easy-Rooting-Toolkit_v11_perf-event-exploit.zip
FAQ
In some scripts, you might find outdated version of SuperSU and it would not work unless you change the file with the latest SuperSU. Make sure you keep the name of the zip same, for example if the folder contains update, rename superSU 2.48 or 2.49 or2.47 or 2.46 to update as well. If it contains superSU, rename it to SuperSU.zip from supersu beta 2.49Beta etc.
You can find the superSU zip here :
https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
https://download.chainfire.eu/740/SuperSU/BETA-SuperSU-v2.49.zip
Guides List
This would contain all the guides for your device. I have added the basic problems already but I hope more users contribute to this thread
ROOTING
ROOT/TWRP
ROOT ALL MODELS
[TUT] BLU, TWRP , ROOT Xperia M4 Aqua [complete step]
ROMS & DEVELOPMENT
Unofficial CyanogenMod 12.1 by ProjectMarshmallow
[BL LOCKED][ROOT]TWRP Touch Recovery for BL locked M4 Aqua
ANDROID OPEN SOURCE G-OS PROJECT
5.0
[RECOVERY] TWRP Touch Recovery for Sony M4 Aqua
[ROM][Flashable ZIP] STOCK FLASHABLE 26.1.A.2.167
[ROM][E2303]Debloated ROM[v0.0.3]
[5.1.1_r26] [UBL] Temasek's Unofficial Build
Aosp 6.0 - e2303 / e2306
[5.0.2] [WIP] AOSP for E2303 [By: Beta Team]
[5.1.1][E2303] AOSP by Beta Team [WIP]
[ROM] De-Bloated Stock 5.0 (E2303) LITE VERSION
[RECOVERY] Cyanogen Recovery Touch for Sony M4 Aqua
[STOCK][5.0] Xperia M4 Deodex
REPAIR /BRICKED/RETURN TO STOCK
MEMORY GUIDES
DRIVER GUIDES
OTHERS
Fix Camera Stock Retrieving after installing Xposed
[ROOT] Change CPU temp. limits ("Manage" overheating) (Updated 10/11/15)
[xposed] how to install xposed on rooted m4 aqua
MODS
SOUND MOD STEREO SPEAKERS - V3
BOOT ANIMATION CHANGER
[MOD][5.0][M4 Aq][PORT]TeleService: CallRecorder + Disabled Notification Data Traffic
xperia music mod black dark theme by iandroidx
[THEME][TWRP] DARK TWRP beta by alby_var
Ad Blocking without Root
Please quote me if I have missed any important guide and you think it deserves to be here.
SUGGESTIONS ?
Kindly give your suggestions and your feedback
CONTRIBUTIONS AND MY HEARTY THANKS TO
@husam666 for the first person to root the device and make a working recovery via adb commands @lucaszell for the guidance how to obtain ulcode. @Sam205 for pointing it out in M4 Aqua forum
XperiaRootKit developed by cubeundcube and pointed in the thread by @AndroPlus
@TheShadow523 for his support and providing screenshots of apps list.
IF A MISSED SOMEONE, PLEASE PM ME AND I BE HAPPY TO ADD YOUR NAME
Kingo root doesn't work, and there are security concerns about iRoot/vRoot. I wouldn't recommend either. Towelroot doesn't work on any Lollipop device to the best of my knowledge. SuperOneClick and Z4Root are both for Gingerbread devices, so neither of those are even worth trying.
MetalOllie said:
Kingo root doesn't work, and there are security concerns about iRoot/vRoot. I wouldn't recommend either. Towelroot doesn't work on any Lollipop device to the best of my knowledge. SuperOneClick and Z4Root are both for Gingerbread devices, so neither of those are even worth trying.
Click to expand...
Click to collapse
i tried almost everything... but no method is working for me... if one works i let you know^^
I don't see a prerooted ftf working either, until there is a recovery method for the phone. As far as I know, only a true stock ftf can be flashed using flashtools.
M4Aqua said:
i tried almost everything... but no method is working for me... if one works i let you know^^
Click to expand...
Click to collapse
I will update the SuperSU so it might be helpful. Will update you when I am done with the guides
Very nice work sir, Appreciate it very much.
As I said on other thread, I cant wait for my device to be rooted and get all the blootware away
When any method works, I'll post my feedback right here!
MetalOllie said:
Kingo root doesn't work, and there are security concerns about iRoot/vRoot. I wouldn't recommend either. Towelroot doesn't work on any Lollipop device to the best of my knowledge. SuperOneClick and Z4Root are both for Gingerbread devices, so neither of those are even worth trying.
Click to expand...
Click to collapse
M4Aqua said:
i tried almost everything... but no method is working for me... if one works i let you know^^
Click to expand...
Click to collapse
Desakato said:
Very nice work sir, Appreciate it very much.
As I said on other thread, I cant wait for my device to be rooted and get all the blootware away
When any method works, I'll post my feedback right here!
Click to expand...
Click to collapse
The guide has been completed. It is upto you to try and find an exploit. At the moment, this is your best bet and I have used many methods for recent devices on Lollipop to root my devices and these tools have been successful. At times, you only need to update SuperSU in the script usually. Give them a try and post your valuable feedback.
I hope you are all aware of USB debugging needs to turned on and you have all the latest drivers installed!
If any script can not find your device, it means either USB debugging is turned off or you do not have drivers installed
Hnk1 said:
The guide has been completed. It is upto you to try and find an exploit. At the moment, this is your best bet and I have used many methods for recent devices on Lollipop to root my devices and these tools have been successful. At times, you only need to update SuperSU in the script usually. Give them a try and post your valuable feedback.
I hope you are all aware of USB debugging needs to turned on and you have all the latest drivers installed!
If any script can not find your device, it means either USB debugging is turned off or you do not have drivers installed
Click to expand...
Click to collapse
I know USB debugging has to be enabled. Updating or installing SuperSu is only useful once the device has been rooted. Unfortunately none of the methods posted are capable of doing so. If you post a guide to rooting, it shouldn't be up to me to find the solution; respectfully, it rather defeats the object of "a guide". Some of the methods proposed haven't worked since Gingerbread. Which script are you referring to, and how does one update it to include SuperSu?
MetalOllie said:
I know USB debugging has to be enabled. Updating or installing SuperSu is only useful once the device has been rooted. Unfortunately none of the methods posted are capable of doing so. If you post a guide to rooting, it shouldn't be up to me to find the solution; respectfully, it rather defeats the object of "a guide". Some of the methods proposed haven't worked since Gingerbread. Which script are you referring to, and how does one update it to include SuperSu?
Click to expand...
Click to collapse
I understand your point mate. No offense!
The problem is that I do not own this device, if I had this device or you can provide me an FTF file, maybe I can work something out. For now, you can try these methods. I have successfully rooted LG devices/ Xperia and even samsung using the above 8 methods.
For your other questions, look at this. Also, Sometimes when i was trying to root my device , supersu 2.46 was not able to root it with the same script yet when i replaced it with 2.447 beta. It did
http://forum.xda-developers.com/showpost.php?p=61228366&postcount=6
Hnk1 said:
I understand your point mate. No offense!
The problem is that I do not own this device, if I had this device or you can provide me an FTF file, maybe I can work something out. For now, you can try these methods. I have successfully rooted LG devices/ Xperia and even samsung using the above 8 methods.
For your other questions, look at this. Also, Sometimes when i was trying to root my device , supersu 2.46 was not able to root it with the same script yet when i replaced it with 2.447 beta. It did
http://forum.xda-developers.com/showpost.php?p=61228366&postcount=6
Click to expand...
Click to collapse
FTF files: http://www.xperiablog.net/forum/resources/categories/xperia-m4-aqua.78/
banciii said:
FTF files: http://www.xperiablog.net/forum/resources/categories/xperia-m4-aqua.78/
Click to expand...
Click to collapse
Desakato said:
Very nice work sir, Appreciate it very much.
As I said on other thread, I cant wait for my device to be rooted and get all the blootware away
When any method works, I'll post my feedback right here!
Click to expand...
Click to collapse
MetalOllie said:
I don't see a prerooted ftf working either, until there is a recovery method for the phone. As far as I know, only a true stock ftf can be flashed using flashtools.
Click to expand...
Click to collapse
I have few root confirmations. Check root post for details!
Hnk1 said:
I have few root confirmations. Check root post for details!
Click to expand...
Click to collapse
im at the moment trying to root the phone with geniusroot....
when its finished i give u a response
EDIT: Geniusroot is not working.... still without root^^
M4Aqua said:
im at the moment trying to root the phone with geniusroot....
when its finished i give u a response
EDIT: Geniusroot is not working.... still without root^^
Click to expand...
Click to collapse
Can you post screenshots and you have proper drivers and usb debugging on ?
Have you tried any other method from my guide ? I think first 3 ones should work!
Please provide your feedback
Related
recently bought a Huawei ascend y200 and i want to root it!
Any advice gratefully received
in Germany done since may
http://www.android-hilfe.de/root-custom-roms-modding-fuer-huawei-ascend-y200/250421-how-root-werkseinstellung-systemupdate.html
root huawei ascend Y200
thank you very much! anyway is there any english version.
BR
Root Ascend Y200
Then you need to learn German in order to root this device.
your friend.
Come to me Sochhean, i will do it for you for free.
Sent from my Galaxy Nexus
In the German Board is now an english HowTo. I cant link to them, because i’m a new user @xda
Root Huawei Y200 Succesfully (ENGLISH)
sochhean said:
recently bought a Huawei ascend y200 and i want to root it!
Any advice gratefully received
Click to expand...
Click to collapse
Hi, I've successfully rooted my phone. I have a Huawei Y200.it might be easier if you waited for OneClickRoot do be launched maybe they have the device listed for auto flashing that does everything for you.
OneClickRoot: ==> I can't post links sorry ..New User, please search on internet..
But anyway, here's the batch file I think I uploaded it..
So its easy once you root it, but WARNING: DO NOT INSTALL CLOCKWORK MODE AGAIN THROUGH ROM Manager OR ANY SOURCE. (this might bring you into bootloop)
follow steps to use the batch file...
1- You need to do this on your phone: Allow USB Debugging and STAY AWAKE Function, STOP fastboot mode. Now Install ADB Drivers when connecting phone into computer via usb and debugging mode is on (you'll see a drive usually green on your computer, check for "drivers" inside driver folders and install windows drivers.
2- You need to install Android SDK : ==> New User, Can't post links, Search Android SDK..
navigate to default download location: " C:\Program Files\Android\android-sdk\platform-tools ", shift + right click inside the folder with nothing selected, and run command prompt from there. run following command "adb devices" and it should list a device number.
3- Now exctract the zip file in attachement and run these in order: -"adb.exe" then -"fastboot.exe" then -"root_v5.2.bat". It should say a succesfull message and ( as i remember) phone should reboot (if it states "reboot phone now" in cmd prompt). now you shoudl be rooted and see "SuperUser" application installed.
4- Check if you're properly rooted with a "rootchecker" market app. If App requested root access by SuperUser (ofcourse you'll tap Accept right?) and says you have proper root, you can now jump around and scream " I rooted my phone" like i did... You can now Install Link2sd app and enjoy free enternal storage since you've rooted your phone... Any Directions using Link2sd repost or you can search internet... One limitation is you can'r use swap (to increase your RAM ), and have to go through different ROM's. If rooted your phone succesfully please inform and on any questions about ROM switching...
Hi there.
The root process isn't so hard , bit the rom switch what would be important for me (not the method, i know that and i'we installed modified recovery its working...)
Went to hell and back @google to find any custom roms for this little fckr but besides the clean base rom and the ics por (whats not working for me) i could not find any other rom. Sorry my bad i have found one origonal stock rom too, bit besides theese do you know is there any other roms exists for u8655?
anyone try the above method?
is there anyone try the above method for English version?
An earlier version, on hungarian with english and german language included... worked perfect. Since 6 months.
MoH21 said:
Hi, I've successfully rooted my phone.
Click to expand...
Click to collapse
Hey, i know the file, that attached...
I'm happy that you understand my realy bad translation of this howto
tapped via my huawei mobilephone
1- You need to do this on your phone: Allow USB Debugging and STAY AWAKE Function, STOP fastboot mode. Now Install ADB Drivers when connecting phone into computer via usb and debugging mode is on (you'll see a drive usually green on your computer, check for "drivers" inside driver folders and install windows drivers.
2- You need to install Android SDK : ==> New User, Can't post links, Search Android SDK..
navigate to default download location: " C:\Program Files\Android\android-sdk\platform-tools ", shift + right click inside the folder with nothing selected, and run command prompt from there. run following command "adb devices" and it should list a device number.
3- Now exctract the zip file in attachement and run these in order: -"adb.exe" then -"fastboot.exe" then -"root_v5.2.bat". It should say a succesfull message and ( as i remember) phone should reboot (if it states "reboot phone now" in cmd prompt). now you shoudl be rooted and see "SuperUser" application installed.
4- Check if you're properly rooted with a "rootchecker" market app. If App requested root access by SuperUser (ofcourse you'll tap Accept right?) and says you have proper root, you can now jump around and scream " I rooted my phone" like i did... You can now Install Link2sd app and enjoy free enternal storage since you've rooted your phone... Any Directions using Link2sd repost or you can search internet... One limitation is you can'r use swap (to increase your RAM ), and have to go through different ROM's. If rooted your phone succesfully please inform and on any questions about ROM switching...
Click to expand...
Click to collapse
This procedure is for CWM, not for root.The root phone you must copy superuser.signed 3.0.7 on memory card, and boot phone in cwm, and install zip from sd card/choose zip from sd card/superuser.signed3.0.7/yes, and reboot system now, when is proces for install zip over.Then your phone is rooted, you think because write ROOT_V5.0.2 it is for root-NO, this for install CWM.
MoH21 said:
Hi, I've successfully rooted my phone. I have a Huawei Y200.it might be easier if you waited for OneClickRoot do be launched maybe they have the device listed for auto flashing that does everything for you.
OneClickRoot: ==> I can't post links sorry ..New User, please search on internet..
But anyway, here's the batch file I think I uploaded it..
So its easy once you root it, but WARNING: DO NOT INSTALL CLOCKWORK MODE AGAIN THROUGH ROM Manager OR ANY SOURCE. (this might bring you into bootloop)
follow steps to use the batch file...
1- You need to do this on your phone: Allow USB Debugging and STAY AWAKE Function, STOP fastboot mode. Now Install ADB Drivers when connecting phone into computer via usb and debugging mode is on (you'll see a drive usually green on your computer, check for "drivers" inside driver folders and install windows drivers.
2- You need to install Android SDK : ==> New User, Can't post links, Search Android SDK..
navigate to default download location: " C:\Program Files\Android\android-sdk\platform-tools ", shift + right click inside the folder with nothing selected, and run command prompt from there. run following command "adb devices" and it should list a device number.
3- Now exctract the zip file in attachement and run these in order: -"adb.exe" then -"fastboot.exe" then -"root_v5.2.bat". It should say a succesfull message and ( as i remember) phone should reboot (if it states "reboot phone now" in cmd prompt). now you shoudl be rooted and see "SuperUser" application installed.
4- Check if you're properly rooted with a "rootchecker" market app. If App requested root access by SuperUser (ofcourse you'll tap Accept right?) and says you have proper root, you can now jump around and scream " I rooted my phone" like i did... You can now Install Link2sd app and enjoy free enternal storage since you've rooted your phone... Any Directions using Link2sd repost or you can search internet... One limitation is you can'r use swap (to increase your RAM ), and have to go through different ROM's. If rooted your phone succesfully please inform and on any questions about ROM switching...
Click to expand...
Click to collapse
when you say RUN adb.exe fastboot.exe and root.bat what do you mean and where do i run them? ive installed platform tools and have done adb devices//my device is there. i extract the files and run them in cmd and double clicking and it doesnt reboot. i guess im having trouble with the .zip i know the files are good. any help :good:would be appreciated.
sketchscarz said:
when you say RUN adb.exe fastboot.exe and root.bat what do you mean and where do i run them? ive installed platform tools and have done adb devices//my device is there. i extract the files and run them in cmd and double clicking and it doesnt reboot. i guess im having trouble with the .zip i know the files are good. any help :good:would be appreciated.
Click to expand...
Click to collapse
sup
Sent from my H866C using xda app-developers app
Yo brow I'm trying to root the h866c. These directions may work but I think that the huawei mercury root directions will make this a functioning root check it out
Sent from my SPH-D600 using Tapatalk 2
AW: [Q] help for root huawei ascend Y200
German: http://www.droidwiki.de/Huawei_Y200/Root
...using tapatalk on my huawei honor smartphone
Since Firmware B898, the bootloader is locked. no way for using clockworkmod... No downgrade possible.
...using tapatalk on my huawei honor smartphone
det-happy said:
Since Firmware B898, the bootloader is locked. no way for using clockworkmod... No downgrade possible.
...using tapatalk on my huawei honor smartphone
Click to expand...
Click to collapse
Hi there
I did a research about this lock and i found a modified kernel what is capable of unlocking again the bootloader. (Claimed by the author, that it should solwe rhe issue)
Please tell me, since i did not upgraded the firmware due to the issue, could it be true?
Because i did not found any feedback from the users who tried it.
Can we count on another unlockibg method, or is this true that the bl can be unlocked via adb kerbel flash?
Thanks in advance.
I found an information on the german android-board
--> http://www.android-hilfe.de/huawei-ascend-y200-forum/414947-b898.html#post5670959
Fuchsteufel told us, that the recovery is working, but only with adb-commands, without any screen.
The solution is to flash an new version of the kernel and the cwm
fuchsteufel said:
für B898 Modified CMW
B898 kompatible Bootimages
Click to expand...
Click to collapse
Thank you.
NABI LAB v2
{
"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"
}
NOTE: The program is becoming long in the tooth and not as useful with Jellybean on Nabi. For Jellybean TWRP installs check this repackaged version of Nabilab http://forum.xda-developers.com/showpost.php?p=48987089&postcount=2088
This is a tool for performing various automated tasks on the Nabi 2. It's written as a windows command line batch file, and v1 has been tested by a few members of the forum with positive results. Hopefully this means all the bugs are worked out, most issues have been typos on my part. It's an attempt to include all recent developments in Nabi 2 rooting, Gapps install, recovery methods, and modding and provide and all in one experience. Alot of this is my own original work, and other parts are creations of others intact or modded for Nabi use. Using the latest known working methods, it hopefully prevents users from having to install, break things, uninstall, recover, try new method, ask forum questions, try another method, and all the while for those with kids having them ask why you broke their toy.
Currently you cannot install Gapps on 2.1.27 see here http://forum.xda-developers.com/showpost.php?p=45866724&postcount=1647
A test version of NabiLabGUI is here: http://forum.xda-developers.com/showthread.php?t=2391449
Overview
Video Overview of Nabi Lab v1 mostly the same as v2
-Install ADB/Fastboot digitally self-signed drivers.
-Root the Nabi 2
-Install Gapps(Play Store, etc)
-Fix Android is upgrading message
-Make a stock backup of unrooted device
-Install a stock 1.9.37 in the event of loss of backup.
-Install stock, or TWRP recoveries
-Tablet Information
-Lockscreen modding tool
-NabiLab patching system to install updates to this program
-Fix TWRP touchscreen issues
-While not a built in function using the tools to fix broken Wifi
Download
Read the installation section below to determine which version you want.
File names:
NabiLabFull.zip 1.1GB
Download
NabiLabLite.zip 97MB
Download
Download Mirror
NabiLabv2Update.zip 10.1MB(upgrade patch for v1 users)
Download
Download Mirror
Installation
There are 2 versions of Nabi Lab: Full and Lite. The full edition is 1.1GB and includes a stock 1.9.37 backup of the system, data, and boot partition. It's usefulness is really only of interest to those that need to restore to a stock backup. It should be a rather limited group of people as you should have a backup of your system already that you could use in lieu of this. However in the event you have lost your backup, or have mangled the system to the point you aren't sure what to do, the option to restore to stock 1.9.37 is in the full edition. The likely download of choice is the Lite edition at a more manageable download size of 97MB. It has all the tools of NabiLab just without the ability to restore a stock backup(which of course you have one of your own). The upgrade patch zip is for v1 users.
NEW INSTALLS
1) Download Nabi Lab
NabiLabFull.zip 1.1GB
NabiLabLite.zip 97MB
2) Extract the zip files to a location of your choosing. Run the NabiLab.bat file.
PATCH INSTALLS(For version 1 users)
1) Download NabiLabv2Update.zip 10.1MB
2) Extract the zip IN to the directory NabiLab is in not FROM the directory. What ever your unzip program it should be extracting to X:\somefolder\somefolder\yourNabiFolder\ If you do it right there will be a file RunOncePatch.bat in the same folder as NabiLab.bat, and a NabiPatch.zip in a new folder called patch in your NabiLab folder.
3) Run RunOncePatch.bat
note: This is only necessary this time, any future patches will be applied by downloading a NabiPatch.zip, and installing inside the NabiLab program.
Prerequisites
1) ADB enabled in Android. Enter Mommy/Daddy mode. Open settings->developer options->put a check mark in USB debugging.
2) Unsure you are on version 1.9.37. Enter Mommy/Daddy mode. Open settings->About Tablet->Product Version. If it's at something less then 1.9.37 go up to the "Update" selector and check update and install. You may have to do this more then once.
Notes: At this point it is believed that the Madagascar Nabi 2, and UK version have product versions of 1.9.34, and 1.9.35/6 respectively. You can attempt to use NabiLab at those versions but I cannot guarantee results. Most things should work however.
Usage
Obviously using this product on your Nabi 2 voids the warranty and I take no responsibility for the damage you cause.
MENU 1 - Installing drivers
The provided drivers are for Windows XP,Vista, 7 and 8 32bit and 64bit. They are modded version of the drivers by 1wayjonny found in this thread. The mod to those drivers are adding the Nabi, and the HP Touchpad Tenderloin(only because I have one). The are digitally self signed by "NabiLab".
Menu Option 1 - Auto Install
Check in the top left corner under Detected OS to see if it matches your configuration. The most important part is if it says "x86"(32bit) or "AMD64"(64bit) this is what the auto installer is going to install. If you don't know right click "my computer" and look under system type. If everything looks right proceed. An installer will launch and guide you through install.
Menu Option 2 - Manual Install
If you want to manually install, an explorer window will launch allowing you to pick the NabiDriver32.exe or NabiDriver64.exe. In case it needs stating the NabiDriver32 is for 32bit OS, and NabiDriver64 is for 64bit.
Notes: The driver can be uninstalled by going into control panel and add/remove programs, select Nabi Driver and click uninstall. The digital certificate for Nabi lab is installed in Trusted Root Certification Authorities. Probably the easiest way to view is internet explorer. Go to tools->internet options->content->certificates. It can be removed from here should you feel it's a security risk. I don't think it installs properly on XP, so if you want to add it go to your program files folder->NabiLab->driver and find the NabiLab.cer, right click and select install. When you come to option of where to install manually select Trusted Root Certification Authorities.
MENU 2 - Root, Gapps, Recovery
Menu Option 1 - Install Root, Recovery and Gapps
This option is best used if you have a brand new Nabi. At this point you should have met the prerequisites of enabling ADB in Android and upgrading to 1.9.37. Follow directions, most sticking points are pressing the volume + and then pressing the volume - button twice and making sure recovery kernel is the one highlighted. After its complete you should have a rooted Nabi, with Gapps and a backup of your unmodified Nabi in the folder TWRP/BACKUPS/YOURSERIAL/stockunrooted on your device. Not a bad idea to copy this off the Nabi to your computer if you need to free space or have it in a second location.
Menu Option 2 - Install Root and Recovery
Same as above but doesn't install Gapps. Some people have trouble with option 1 taking the Gapps install, I personally have never experienced it but the option is this one, or I guess if you are an elite hacker that just wants root.
Menu Option 3 - Install Gapps
Same Gapps installed in the Option 1. Useful for re-installing Gapps, and/or getting rid of the Android is Upgrading message. It is the immensely popular t499user Gapps with the 2 stray .odex removed. No sense in reinventing the wheel. This makes NO backup of you Nabi. You will have to already have installed TWRP.
Menu Option 4 - Install Root
Installs root. Nothing fancy here, and likely unneeded but here for completeness if you find yourself in a strange situation. One that comes to mind is that you have a stock backup which you restored and don't want to do another backup so you would just run this and the gapps install. It makes NO backup. You will have to already have installed TWRP.
Note: The layout of this is based on the original work by jmztaylor, modified for what we currently know about the Nabi and tweaked accordingly.
MENU 3 - Return Nabi to Stock Condition
The menu options will only be available if you have downloaded Nabi Lab full. If you have a stock unrooted backup you should try that first.
Menu Option 1 - Return Nabi to Stock 1.9.37. Android can boot.
This is useful if you just want to return your Nabi to stock for regular use, sale, or warranty(morals aside). This is the mode to use if you can boot Android. This operation will take some time to run, so let it. Upon completion TWRP is still installed, to entirely restore to stock you will need to install the stock recovery(see Menu 4). You have the option to put on external or internal storage. Although I don't think I compiled TWRP to use "in place" install, which would mean it still copies to internal. I'm not sure on this one, so internal is probably the best bet, but I have performed it on external and it works fine. You will need space on internal storage to do it.
Menu Option 2 - Return Nabi to Stock 1.9.37. Android not booting.
This is useful if you are in a situation that has left Android unbootable and you have no backup. Otherwise it's the same as Option 1. You will boot to TWRP and then perform the restore. Again TWRP will still be installed afterward, no be completely at stock you will have to remove it by Main Menu 4. I have it this way in the event you plan to immediately reroot it.
Notes: If you want to view this menu in the lite version, you need to open the file havefiles.txt, it is located in the stockimage folder. Change the line backup=false, to backup=true. You can then view the menu. You can then copy files you wanted to the stockimage folder and restore. Since the restore portion is manual I'm not sure why you would ever use it this way but if you want to play around that's how to enable it.
MENU 4 - Install Recoveries
Menu Option 1 - Install TWRP 2.3.3.0 for Nabi Version 1.9.37
Installs TWRP 2.3.3.0. This is the version that everyone should be trying to use first before trying other versions. This is the version that has symlinked paritions since it is thought currently their might be different partition structures for various Nabi's. Newer Nabi kernel and fixes touchscreen issues for some people that were using 2.2.2.1.
Menu Option 2 - Install TWRP 2.3.3.0 for Nabi Versions prior to 1.9.37
Use this option if Option 1 didn't work for you. Older Nabi kernel, otherwise same as Option 1.
Menu Option 3 - Install TWRP 2.2.2.1
This is the original TWRP from the first Nabi rooting thread. Use this if the other 2 don't suit you, or you just trust my compile skills, which may be prudent... :silly:
Menu Option 4 - Install Stock Recovery
Installs stock recovery. This is useful for taking an OTA, or completely returning Nabi to stock.
Menu Option 5 - About Recovery Installer
A leftover from my initial recovery installer, I was too lazy to remove it.
Notes: TWRP installs are based off my work in this thread if you want to read more.
MENU 5 - Tablet Information
Nabi Information, serial, version, build date, device mode, internal/external size, detected backups.
Note: This only detects if a backup folder is present, not if there are backups actually inside the folder. The only way this would be the case is if you manually deleted them or just made a empty folder in there, so be aware. Also if you have made a ramdisk modifying init.rc, used creative symlinking to swap internal and external SD, or used a prebuilt app to swap this screen may be incorrect.
MENU 6 - Lockscreen Mod Tool
Don't use this if you have updated to v2.0.5, I haven't tested but the framework-res.apk was updated in the 2.0.5 update and if you are using the old one you could throw yourself in to a bootloop
Menu Option 1 - Install custom lockscreen
Use this to install a custom lockscreen. You will need a picture that is in .png format and is 1440 x 903. A explorer window will open up showing you the location to put the picture. The file MUST be name lockscreen.png, there is one there that is black, you can overwrite it be there MUST ALWAYS be a lockscreen.png file in that folder if you use the tool. Bad things could possibly happen if it doesn't. You have the option to manually install the lockscreen, or automatically install it after the zip is built. In either case it copies whatever you named the zip(you are prompted for a name) to the internal SD, along with a file called lockorig.zip. The lockorig.zip is there if you mess up and Android won't boot you can manually install the lockorig.zip in TWRP to put it back to stock.
Menu Option 2 - Install stock lockscreen
Use this to return to stock. Remember if you used Option 1 there will already be the stock lockorig.zip on your internal storage.
Notes: If you make a custom lockscreen, while it copies the installable zip to your device it also copies it to your picture folder so you can share with others. Make sure you visit in share your creation over in this thread.
MENU 7 - Patch NabiLab
Menu Option 1 - Install Patch
For any updates to Nabi Lab this is where you can automatically load them. Basically you will download NabiPatch.zip and place the entire zip in the patch folder. No unzipping just the single file. Then run this option.
Note: Since this option wasn't in NabiLab v1, we have to do some trickery when coming from version 1 to install, so the procedure is different, all subsequent patches will be the above method however. Coming from version 1 you will need to download NabiLabv2update.zip and extract it into the NabiLab directory such that RunOncePatch.bat is in same directory as NabiLab.bat, and the other file NabiPatch.zip is in the folder "patch", then run the RunOncePatch.bat If you extract into your NabiLab directory it won't be a problem, the hint you didn't do it right will be if the RunOncePatch.bat isn't right there with NabiLab.bat
Credits
jzmtaylor - Original Nabi root. Nabi device code from which to build newer TWRP
t499user - Gapps fix
Dees_Troy - TWRP build tutorial
Eric Karz - Lockscreen Modding, NabiLab scripting
1wayjonny - Universal Driver base code
TeamWin - They are the guys that make TWRP possible
In all honesty everyone that has participated in the main Gapps thread has indirectly made the program what it is from testing, to information, to troubleshooting and everything else Nabi.
Hmmm just for giggles I installed Nabi Lab on my Computer to change the Lock Screen and it does not want to read my Tablet.
Thanks for this! Driver install didn't work for me on any of my computers...well it did install a driver but didn't read my nabi. Uninstalled nabilab driver and used PDA.net and all was good. Nabilab worked great installing recovery root n gapps! Thanks agn.
Sent from my EVO using xda app-developers app
DarkAngel said:
Hmmm just for giggles I installed Nabi Lab on my Computer to change the Lock Screen and it does not want to read my Tablet.
Click to expand...
Click to collapse
So it's saying error Nabi not detected or no driver? Is the device seen in Device Manger? Really can be only 2 thing, adb conflict or device driver.
strive53 said:
Thanks for this! Driver install didn't work for me on any of my computers...well it did install a driver but didn't read my nabi. Uninstalled nabilab driver and used PDA.net and all was good. Nabilab worked great installing recovery root n gapps! Thanks agn.
Click to expand...
Click to collapse
What operating systems and did you have any previous Android devices connected to the computer? Sometimes I noticed it will conflict with any previous driver installs, and while installing the driver is successful it won't use it. I guess it doesnt matter if it's working for you with PDAnet. If you are on vista or later you can try running pnputil -e from command prompt and look through all the oemxx.inf's and see how many google,inc android drivers there are.
aicjofs said:
So it's saying error Nabi not detected or no driver? Is the device seen in Device Manger? Really can be only 2 thing, adb conflict or device driver.
What operating systems and did you have any previous Android devices connected to the computer? Sometimes I noticed it will conflict with any previous driver installs, and not while installing the driver is successful it won't use it. I guess it doesnt matter if it's working for you with PDAnet. If you are on vista or later you can try running pnputil -e from command prompt and look through all the oemxx.inf's and see how many google,inc android drivers there are.
Click to expand...
Click to collapse
Sorry should have been more specific. It detects it via Device Manager but not via Nabi Lab. I am running Windows 7 x64
DarkAngel said:
Sorry should have been more specific. It detects it via Device Manager but not via Nabi Lab. I am running Windows 7 x64
Click to expand...
Click to collapse
Is it detecting 2 Nabi interfaces in Device Manager? I can see it's detecting the MTP interface, but what about the ADB interface. Usually ADB appears under Android Device and MTP under Portable Devices. Is there anything under "Other Devices"? NABI2-NV7A something or other? Only other thing I could think is that there is a hung up ADB process running, kill it in task manager or reboot.
sorry knew i should have stated my operating system. my main computer is a macbook and i have a old xp laptop n xp netbook that i use for flashing. i also tried it on my moms win7 desktop and a friends win8 desktop without luck. never changed in device manager from NABI2-NV7A with yellow exclamation point. ive flashed a bunch of phones from my laptop and probably do have drivers installed from who knows what.. it did install the driver but nabi wasnt detected as adb interface. rebooted computers n nabi after installs. i didnt have any other device attached at the time.
aicjofs said:
Is it detecting 2 Nabi interfaces in Device Manager? I can see it's detecting the MTP interface, but what about the ADB interface. Usually ADB appears under Android Device and MTP under Portable Devices. Is there anything under "Other Devices"? NABI2-NV7A something or other? Only other thing I could think is that there is a hung up ADB process running, kill it in task manager or reboot.
Click to expand...
Click to collapse
Yes it's detecting on both. The only thing that has been baffling me for some time is back when I had a Windows phone and after I switched to android, what appears to show in "Other" looks like my old TouchPro2. I can not delete that.
strive53 said:
sorry knew i should have stated my operating system. my main computer is a macbook and i have a old xp laptop n xp netbook that i use for flashing. i also tried it on my moms win7 desktop and a friends win8 desktop without luck. never changed in device manager from NABI2-NV7A with yellow exclamation point. ive flashed a bunch of phones from my laptop and probably do have drivers installed from who knows what.. it did install the driver but nabi wasnt detected as adb interface. rebooted computers n nabi after installs. i didnt have any other device attached at the time.
Click to expand...
Click to collapse
I had trouble with computers that has previous drivers installed sometimes, other times not. I tested fresh installs on XP 32, 7 32, 7 64, 8 64 and everything went fine, but it was much more hit and miss with computers that already had a slew of drivers. I'm more concerned that NONE of yours would work, although I guess it's offset by the fact that PDAnet driver worked and that NabiLab itself worked fine.
Yes it's detecting on both. The only thing that has been baffling me for some time is back when I had a Windows phone and after I switched to android, what appears to show in "Other" looks like my old TouchPro2. I can not delete that.
Click to expand...
Click to collapse
Well you have me baffled too! haha. If you run "adb devices" from cmd prompt what is the output? You have a modified cmd processor, that opens batch files? Seems like everything is in place. It case it's something with the program did you come from v1 NabiLab and patch or just v2?
f you want to play with the lockmod while we figure it out, the pic zip you made will still be in "pictures" folder, just let that portion of the program run until it errors when it tries to adb transfer. You can manually transfer to SD and flash TWRP.
aicjofs said:
I had trouble with computers that has previous drivers installed sometimes, other times not. I tested fresh installs on XP 32, 7 32, 7 64, 8 64 and everything went fine, but it was much more hit and miss with computers that already had a slew of drivers. I'm more concerned that NONE of yours would work, although I guess it's offset by the fact that PDAnet driver worked and that NabiLab itself worked fine.
Well you have me baffled too! haha. If you run "adb devices" from cmd prompt what is the output? You have a modified cmd processor, that opens batch files? Seems like everything is in place. It case it's something with the program did you come from v1 NabiLab and patch or just v2?
f you want to play with the lockmod while we figure it out, the pic zip you made will still be in "pictures" folder, just let that portion of the program run until it errors when it tries to adb transfer. You can manually transfer to SD and flash TWRP.
Click to expand...
Click to collapse
This is the first time installing it actually since I Rooted and installed GApps through Ubuntu. I just wanted to try it so I can try and change the lockscreen image and update TWRP while I was there also. I downloaded v2 with the backup. I was going to try v1 to see if that made a difference or try the PDAnet driver.
Sent from my NABI2-NV7A using Tapatalk HD
Worked fine as soon I realised I wasnt waiting for the files to transfer :banghead:
Sent from my GT-I9100 using xda premium
kieronw3 said:
Worked fine as soon I realised I wasnt waiting for the files to transfer :banghead:
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
I could add a line that says, go check the mail, run to 7-11, trim the dogs toe nails. Hehe. Glad it worked eventually. 58 or so downloads and not many complaints, I can live with that, better then a brickfest. :laugh:
Nice job on lab update. Good use of the colors
i have a Request
could you add 'upgrade Twrp to the latest version'
maybe under Advanced User tool.
then if for some reason there is changes in the future you could just put the image file down load in that folder and update by click of a button ?
Win 8 64bit... Never had other android drivers installed on this machine. I dont see it listed in device manager at all. But the machine definitely sees it in my computer, and I also see it go into debug mode on the tablet. Confused,,,
Eric Karz said:
Nice job on lab update. Good use of the colors
i have a Request
could you add 'upgrade Twrp to the latest version'
maybe under Advanced User tool.
then if for some reason there is changes in the future you could just put the image file down load in that folder and update by click of a button ?
Click to expand...
Click to collapse
I need something for a version 3, so why not?
delio77 said:
Win 8 64bit... Never had other android drivers installed on this machine. I dont see it listed in device manager at all. But the machine definitely sees it in my computer, and I also see it go into debug mode on the tablet. Confused,,,
Click to expand...
Click to collapse
Are you using NabiLab or just the drivers I linked in another post? Is it detecting it in NabiLab? If it is the drivers have to be there under Android Device.
When I try to install recovery, root, gapps, I get stuck on waiting for device. My device detects just fine. I think it may be an issue with fastboot drivers, not ADB drivers? Because ADB reboots the device into fastboot just fine. But once it's there, it just sits on "waiting for device". Any thoughts?
bradleyw801 said:
When I try to install recovery, root, gapps, I get stuck on waiting for device. My device detects just fine. I think it may be an issue with fastboot drivers, not ADB drivers? Because ADB reboots the device into fastboot just fine. But once it's there, it just sits on "waiting for device". Any thoughts?
Click to expand...
Click to collapse
Have you verified that your fastboot drivers are working? If you navigate to the folder where adb.exe and fastboot.exe are you can just iddues the command fastboot devices to see if the device is connected while in fastboot.
1. How would you update a Nabi that has been originally rooted on .23 with jmz's work. I'd also like to clean up the optimizing android apps issue?
2. Would it be possible for you to add a "Clone Nabi" option to the Lab. Many people have more than one Nabi to tend to and it would be nice if you could duplicate the setup across multiple devices. I did it by hand for a dozen and let's just say it's a bit painful.
Mostly, though I wanted to thank you and all of the other developers for their work. There is a classroom full of 1st graders that use the Nabis everyday. They used to be stuck with nine-year-old Dell computers that would take 15 minutes just to boot...now things are easy and fun. You guys have really made my donation of the Nabis a great project. Thanks!
aicjofs said:
I need something for a version 3, so why not?
Are you using NabiLab or just the drivers I linked in another post? Is it detecting it in NabiLab? If it is the drivers have to be there under Android Device.
Click to expand...
Click to collapse
I am using NabiLab and it said not detected. I eventually got it to work with PDAnet
Ken Esq said:
1. How would you update a Nabi that has been originally rooted on .23 with jmz's work. I'd also like to clean up the optimizing android apps issue?
2. Would it be possible for you to add a "Clone Nabi" option to the Lab. Many people have more than one Nabi to tend to and it would be nice if you could duplicate the setup across multiple devices. I did it by hand for a dozen and let's just say it's a bit painful.
Mostly, though I wanted to thank you and all of the other developers for their work. There is a classroom full of 1st graders that use the Nabis everyday. They used to be stuck with nine-year-old Dell computers that would take 15 minutes just to boot...now things are easy and fun. You guys have really made my donation of the Nabis a great project. Thanks!
Click to expand...
Click to collapse
So is the device still on .23? Probably 3 ways to go about it if that's the case,
1) backup apps with something like Titanium backup, restore the original backup "stockunrooted" of Nabi, reinstall stock recovery, update to 1.9.37, reapply root and gapps, restore app backups, or
2) backup apps, restore a stock 1.9.37 from NabiLab, reapply root, gapps, restore app backup. or
3) you can try updating the safe OTA's people have posted, I came late to the game so I didn't study those, I know there is the wifi issue between kernel and modules if you don't do it right. If you already are on .37 but just rooted back on .23 the only thing to do is gapps to fix android upgrading. The optimizing android is fixed by flashing the fixed gapps.(Gapps only, option 2 then option 3 in NabiLab)
How would you like to see cloning? It just loops through the procedure and you just keep plugging Nabi? Or a restoring image to all of them. Help me visualize what you think would be best.
I'm not sure how you are doing it. How I would do it currenlty for Nabilab if I had 20 brand new Nabi's is like this. Once all Nabi's are at version you want (1.9.37)
Take one Nabi and do a recovery, root, gapps, backup(Option 2, Option 1)
Grab the backup it made and move it to computer.
Take remaining Nabi's
Install TWRP 2.3.3.0(Option 4, Option 1)
Install Root Only(Option 2, Option 4)
Install Gapps Only.(Option 2, Option 3)
What you accomplish here is making the backup only once. So first Nabi takes 15 min, the remaining maybe 3 min.
No thank you for popping in with some feedback.
NEXUS 7 V2 (2013 EDITION) - SUPPORTS ALL VERSIONS UP TO LATEST ANDROID 6.0.1 BUILDS
SEE SUPPORT LIST FOR PUBLIC/PRO VERSIONS *HERE*
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
* 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, 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).
--------------------------------------------------------------
ChangeLog:
ToolKit v1.4.1 (05th Oct 2015)
+Added new upcoming devices to device selection screen
+Main files now signed with Digital Certificate to ensure files are original and safe
+Added file checker after device selection to check needed files are up to date
+Updated UniversalAdbInstaller for Windows 10 compatability
+Added driver installation option at startup for new installs
+Updated ToolKitClean.exe to allow users to update the main ToolKit.exe file to latest available version without having to download/install the whole ToolKit again (like when a new device is added or files/drivers updated)
+Improvements and minor bug fixes
+Installer now give option for Fresh Install (removes any existing device files) or Upgrade (to just update base files)
--------------------------------------------------------------
USEFUL INFORMATION
How to get into your FastBoot Mode
1. Turn your phone off
2. Unplug your usb cable if you have one plugged in
3. Keep holding the 'Volume Down' and 'Power' buttons to boot the phone into FastBoot Mode
How to get into Recovery
1. First boot into FastBoot Mode as described above
2. Scroll down with the 'Volume Down' button until it says 'Recovery mode' at the top and press the 'Power' button to enter Recovery
Show the Menu in the Stock Recovery Screen
1. Hold the Power button and keep holding as you press the Volume Up button quickly. The blue recovery menu screen should pop up.
--------------------------------------------------------------
*DISCLAIMER*
I take no responsibility for any fault or damage caused by any procedures within this guide. No warranties of any kind are given.
UPDATES:
Frequently Asked Questions:
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. What is FASTBOOT?
Fastboot is 2 things. It is a mode on the phone, which looks a little like Bootloader. You can access it by holding 'Volume Up' and 'Volume Down' whilst turning on the phone.
It is also a way of flashing radios, recovery, boot images and system images in a command line method from a PC much like adb.
----------------------------------------------------------------------------
Q. I flashed CWM but each time I reboot the Stock Recovery is back
There is an auto recovery restore system on certain Stock Android Builds that will reflash the Stock Recovery if you flash CWM on a Stock Rom.
Use Root Explorer to Mount the system folder as R/W (or use a free app from Google Play such as ES File Explorer). Rename the files /system/recovery-from-boot.p and /system/etc/install-recovery.sh. Now when you flash CWM Recovery it will NOT be overwritten after a reboot.
OR you can use the ToolKit to rename the files (root access needed).
----------------------------------------------------------------------------
Q. I want to send my phone back so I need to flash a stock rom and relock the bootloader
1. Download, install and run the Google Nexus 4 Toolkit.
2. Install adb/fastboot drivers (if you havent already done so)
3. Option 9 to download a Google Factory Image.
4. After it finishes downloading you will be given the option to flash the image to your tablet. Do this.
4. Let the phone reboot, then shut the device down and reenter fastboot mode (or boot to fastboot mode via the Reboot Screen in the ToolKit).
5. Option3, 2 to relock the bootloader.
Your internal storage will be formatted and data and cache wiped. Your tablet will now be back to an out-of-the-box FULLY STOCK state and ready to send back.
----------------------------------------------------------------------------
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 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) will pick it up as potentially harmful when it is not. They will 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. The ToolKit recognises my tablet in adb mode but not in fastboot mode (or other way round).
Open the Device Manager on your pc and then boot your tablet into fastboot mode or adb mode (dont plug the usb cable in yet). Make sure USB debugging is enabled on your tablet in settings, developer options. Plug the cable in while watching the Device Manager and determine which item is added to the list with the device plugged in. Once you have found it right click on the item and select update driver. Select 'browse my computer' from the list and then browse to the 'drivers' folder in the ToolKit folder (wherever you installed the ToolKit to). Make sure sub folders is ticked and click next. Hopefully the driver will be picked up and installed.
You can check if a driver has been installed by looking at the top of the Main Menu in the ToolKit while in fastboot mode and adb modes. If a serial number is displayed in each mode then it will work fine.
----------------------------------------------------------------------------
Q. Can I back up my apps before unlocking the Bootloader so I don't lose everything?
Performing an APPS BACKUP (option2, 1) will backup all apps that were installed after you first used your device. This will include any associated user data (such as settings or high scores for games) and apps you installed from Google Play Store. Just follow the recommended options and remember to turn your phones screen on before starting it as you need to confirm on your screen.
This option will NOT require your bootloader to be unlocked first.
You can also backup your Internal Storage without unlocking using option 2, 3 from the main menu. This will backup anything you store on your Internal Storage such as game data, music, videos. This is just pulled from your /data/media folder so you can view or edit the files on your pc after they have been pulled.
You can then unlock the bootloader (wiping your device) and retore the apps (option 2, 10) and Internal Storage data (option 2, 11) after doing whatever you want to with your device.
The only thing you cannot do with the ToolKit is to save the system settings but some of those are backed up by google if you chose that option when turning your device on the first time.
----------------------------------------------------------------------------
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 cannot find Developer options to Enable USB Debugging
With Android 4.2 google have thought it would be funny to hide the Developer options screen in the Settings. This means you cannot enable usb debugging to communicate with your device. To show the Developers options screen do the following:
Goto Settings, About tablet and tap your finger on the the 'Build number' text at the bottom 7 times (not too fast).
When you have tapped 3 times you will be given a countdown of taps until you become a 'developer'.
Once you are told you are now a developer you can go back to the Settings screen and can see Developer options.
You can now go into Developer options and enable usb debugging.
----------------------------------------------------------------------------
Q. I tried to enter the code for the professional version but the Toolkit says the code is incorrect
Make sure the code entered is for the correct Toolkit being used.
You need to make sure you start the Toolkit with the toolkit.exe file when activating and not the tkmain.exe file so the settings can be initialised or the code will not be accepted.
Also make sure you enter the code correctly as the characters are case sensitive.
Sounds great! Will test the Toolkit
I dont see the download links..
acdcking12345 said:
I dont see the download links..
Click to expand...
Click to collapse
sigh...
IN TESTING PHASE NOW. DOWNLOAD LINKS WILL BE POSTED LATER TODAY
horst0815 said:
sigh...
IN TESTING PHASE NOW. DOWNLOAD LINKS WILL BE POSTED LATER TODAY
Click to expand...
Click to collapse
Yeah caught that after I posted. Laugh
Download links up in the OP. There is a problem with the add shell su scripts as the Toolkit will not allow an exit but this only affects the NAND backups. I will look at that tonight and update the public version (and push an Auto Update for pro users) as soon as its fixed.
Enjoy and please give feedback as its the first version
Mark.
Worked like a champ on the latest 4.3 OTA update.
Thanks, Mister Skippen! The Boot options, Root / Insecure, and "All-In-One" options all worked perfectly on my new FLO with the latest 4.3 OTA update already applied. So far, I haven't found any glitches in the toolkit.
I bought another pint for you today, too. Maybe a pint and a half, if you go to a cheap pub...
Newest ota for N7 LTE is out^^ JLS36C
Gesendet von meinem Nexus 7 mit Tapatalk 4
good to see this toolkit on nexus 7 (2013), using your toolkit since galaxy nexus and the old nexus 7, great!!
NEXUS 7 [2013 MODEL] TOOLKIT AUTO UPDATE V1.0.2 [04TH SEPT 2013] AVAILABLE!!
Changelog:
+Fixed NAND Backup routine crashing Toolkit
+Added 'Starting out for the first time' help screen in 'Information' section
+Added text to several parts to clarify and add more information
[Auto Updates are only accessible if you have donated to the Toolkit project, received an activation code and unlocked the professional features. Auto Updates are a much faster and easier way of pushing small updates that would otherwise not be worth doing. I can push a single textual change or add support for a new build without having to go through the whole process of building a full version and uploading a large file. IF you are not able to or do not want to donate to unlock the Auto Update feature (and other professional features) then all the smaller updates are collated and a full build made when I have time or if there are enough updates to warrant it. This is the easiest way to make sure all the Toolkits are as up to date as possible. IF you have any views about this please email me at [email protected] about them and do not post in the open thread]
Donation links can be found at http://www.skipsoft.net/?page_id=703 for users who wish to update to the Professional version and enable Auto Updates.
Thread Link: http://goo.gl/B992Qi
Mark.
Hi Mark ,
I'm a user/donor of the Nexus 4 toolkit, can both be installed together?
Is it ok to use samdonation code?
Thanks.
Sent from my Nexus 7 using XDA Premium 4 mobile app
atz6975 said:
Hi Mark ,
I'm a user/donor of the Nexus 4 toolkit, can both be installed together?
Is it ok to use samdonation code?
Thanks.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I have the same question, I use the donor toolkit for my Nexus v1 and still use it to this day. Do we have to pay for nexus v2 toolkit?
Sent from my HTC6500LVW using xda app-developers app
atz6975 said:
Hi Mark ,
I'm a user/donor of the Nexus 4 toolkit, can both be installed together?
Is it ok to use samdonation code?
Thanks.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I have 10 different Toolkits installed and all work fine together so yes you can have more than 1 Toolkit installed on your PC without any problems.
The Toolkits are all seperate projects and an activation code from 1 Toolkit cannot be used to activate another.
Mark.
mskip said:
I have 10 different Toolkits installed and all work fine together so yes you can have more than 1 Toolkit installed on your PC without any problems.
The Toolkits are all seperate projects and an activation code from 1 Toolkit cannot be used to activate another.
Mark.
Click to expand...
Click to collapse
Works with me, you going to be around this Thursday? I'll pay for this toolkit tomorrow.
What happens with the activation key if I have to reinstall my OS?? Can I use it more than once?
NAU420 said:
Works with me, you going to be around this Thursday? I'll pay for this toolkit tomorrow.
Click to expand...
Click to collapse
Im around every day
Mark.
User_99 said:
What happens with the activation key if I have to reinstall my OS?? Can I use it more than once?
Click to expand...
Click to collapse
Yes you can.
Mark.
I can't get this working, when I try to root it reboots into Android and then nothing happens, just says waiting for device.
I've installed and re-installed drivers, USB debugging is enabled.
SAMSUNG GALAXY NOTE 3 - SUPPORTS ALL VERSIONS UP TO THE LATEST ANDROID BUILDS
SEE SUPPORT LIST FOR PUBLIC/PRO VERSIONS *HERE*
INT EXYNOS GSM (SM-N900) SUPPORTED
INT QCOMM LTE (SM-N9005) SUPPORTED
SPRINT LTE (SM-N900P) SUPPORTED
TMOBILE LTE (SM-N900T) SUPPORTED
US CELLULAR LTE (SM-N900R4) SUPPORTED
CANADA LTE (SM-N900W8) SUPPORTED
The Unified Android Toolkit brings together all the Nexus and Samsung Toolkits and supports many Nexus and Samsung devices. There is also an option at startup to run a Basic Android Toolkit which any Android device can use to install drivers, make app backups, install apk files, reboot the device into different modes and run a command prompt for manual input.
FUNCTIONS OF UNIFIED ANDROID TOOLKIT
* Install correct adb/fastboot drivers automatically on Windows xp/vista/7/8 32bit+64bit/Windows 10
* Backup/Restore a single package or all apps, user data and Internal Storage
* Backup your data from selectable folders [internal or external storage] to your PC for a Full Safe backup of data
* Unlock/Re-Lock your Bootloader [Nexus]
* Root Stock builds
* Various Root options using insecure boot image or custom recovery
* ALLINONE to Unlock, Root, Rename the Restore Files and install busybox [Nexus]
* ALLINONE to flash custom Recovery Root, Rename the Restore Files and install busybox [Samsung]
* [NEW] use SkipRoot boot image to Auto Root device, install Busybox Binaries and rename Recovery Restore files [selected devices]
* Install BusyBox on your device
* Perform a FULL NANDROID Backup of your system (Boot, Cache, Data, Recovery and System) via adb and save in Custom Recovery format on your PC which can be Restored via CWM Recovery [if insecure boot image available]
* Fix extSdCard write permissions from installed apps in Android 4.4+ [Samsung]
* Pull /data and /system folders, compress to a .tar file and save to your PC [if insecure boot image available]
* Dump selected Device Partitions, compress to a .zip file with md5 and save to your PC [if insecure boot image available]
* Extras, Tips and Tricks section
* Auto Update ToolKit to latest available version at startup (professional only feature)
* Program up to 10 Quickpick slots and run them very quickly (professional only feature)
* Mods section to automatically perform certain tasks on your device
* Download Google Stock Image directly to correct ToolKit folder for extracting and flashing [Nexus]
* Check md5 of stock image to make sure downloaded file isn’t corrupted before flashing [Nexus]
* Download Samsung Stock Firmware to PC for extracting and flashing via Odin [Samsung]
* Flash Custom Recovery or Google Stock Image to Device
* Flash any part of a stock Nexus image to device [boot, system, recovery] – Great for fixing broken parts of firmware
* Rename the Recovery Restore File present on some Stock Roms
* Boot into CWM Touch, TWRP, Philz Touch Recovery or Stock Recovery without Flashing it [Nexus]
* Flash Custom Recovery to Device
* Boot [Nexus] or Flash .img Files directly from your PC
* Install a single apk or multiple apk’s to your device
* Push Files from your PC to your device
* Pull Files from your device to your PC
* Disable forced encryption on Nexus6 and Nexus9 devices
* Install Root Checker app by Burrows Apps
* Install Backup/Restore app by MDroid Apps [calls log, sms, contacts]
* Install EFS/Partition Backup/Restore app by Wanam
* Dump selected LogCat buffers to your PC
* Dump BugReport to your PC
* Set Files Permissions on your device
* Open new Command Prompt for manual input
* Reboot device to Fastboot Mode or Android from fastboot mode [Nexus]
* Reboot device to Fastboot Mode [Nexus], Recovery, Android or Download Mode [Samsung] from adb mode
* Display Important Information about your device
--------------------------------------------------------------
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
--------------------------------------------------------------
SUPPORTED DEVICES AND LATEST SUPPORTED BUILDS *HERE*
DOWNLOAD THE SKIPSOFT UNIFIED ANDROID TOOLKIT *HERE* (FROM SKIPSOFT.NET)
NOTE: Key files are signed with a Digital Certificate from skipsoft.net but some ‘may’ get picked up as potentially harmful by Antivirus Programs and deleted. They are not harmful, this is a false positive given because of the compiler used. If this happens restore the file and exclude the folder from future scans to use it. This seems to happen mostly on AVG Free and Norton. If you are using the Auto Update feature on pro versions then you will need to disable the AV program or exclude the folder from scans before running the update again.
Credits: ChainsDD for Superuser, Chainfire for SuperSU and kernel patches, koush and the clockworkmod team for cwm and the universal driver pack, 1wayjonny for the adb/fastboot driver pack, Adam Lange for all his support and help with the insecure kernels, Viperboy for the Knox Disabler app, Stephen Erickson for the BusyBox installer app, BurrowsApps for the Root Checker app, NextApp for the SD Fix app, fOmey for TWRP for the Galaxy Gear.
--------------------------------------------------------------
WHAT IS THE DIFFERENCE BETWEEN PUBLIC (FREE) AND PROFESSIONAL (DONATE) VERSIONS?
THE PUBLIC VERSION OF THE TOOLKIT INCLUDES EVERYTHING YOU COULD NEED TO MANIPULATE AND ROOT YOUR DEVICE.
ACTIVATING THE PROFESSIONAL VERSION ADDS THE MOST USEFUL FUNCTION IN THE TOOLKIT, THE ABILITY TO CHECK FOR ‘AUTO UPDATES’ DIRECTLY VIA THE TOOLKIT AND HAVE THEM PUSHED TO YOUR PC RIGHT AWAY AS SOON AS THEY ARE UPLOADED WITHOUT NEEDING TO DOWNLOAD THE WHOLE TOOLKIT EVERY TIME. YOU WILL ALWAYS HAVE THE LATEST VERSION AS SOON AS IT IS MADE AVAILABLE. THIS MEANS SMALLER UPDATES CAN BE SENT OUT MORE FREQUENTLY, SUCH AS ADDING A SINGLE FUNCTION, FIXING A BUG OR ADDING COMPATIBILITY FOR A SINGLE CARRIER. THE SMALLER UPDATES WILL BE COMPILED AND RELEASED TO THE XDA COMMUNITY AS A FULL (PUBLIC) DOWNLOAD VERSION SO PROFESSIONAL VERSIONS ARE ALWAYS UPDATED SOONER.
THE PRO VERSION ALSO ADDS THE ABILITY TO CHECK FOR THE LATEST VERSION OF SUPERUSER AND RECOVERY FILES AND DOWNLOAD THEM DIRECTLY TO THE TOOLKIT.
THE ‘QUICK PICKS’ SECTION[/B] ALLOWS YOU TO PROGRAM UPTO 10 SLOTS WITH TASKS THAT YOU MAY PERFORM ON A REGULAR BASIS OR JUST WANT TO KEEP A SET OF TASKS IN 1 PLACE. THEN JUST SELECT THE SLOT AND IT WILL REMEMBER ALL YOUR SETTINGS FOR THAT TASK AND RUN IT.
PRO USERS CAN ALSO SELECT THE “ANY BUILD” OPTION IN THE BUILD SELECTION SCREEN TO ROOT ANY BUILD AS LONG AS THE VERSION IS SUPPORTED (USEFUL IF YOUR BUILD IS NOT LISTED).
MORE IMPORTANTLY DONATING SHOWS YOUR APPRECIATION AND ALLOWS THE TOOLKIT TO CONTINUE TO EVOLVE AND GROW.
AUTO REPLY LINKS FOR PAYPAL TO GET A CODE INSTANTLY CAN BE FOUND AT http://goo.gl/nyGqv
--------------------------------------------------------------
PLEASE READ THE *HELP* PAGE AT http://www.skipsoft.net/?page_id=1269 OR USE THE INFORMATION SECTION WITHIN THE TOOLKIT IF YOU HAVE ANY QUESTIONS. I HAVE TAKEN A LOT OF TIME TO WRITE IT AND SOMETHING ON THERE SHOULD ANSWER 99% OF PROBLEMS.
--------------------------------------------------------------
1. INSTALLING ADB/FASTBOOT DRIVERS
The first thing you need to do is to install the adb/fastboot drivers. These are needed so that you can unlock your bootloader, root your device and perform other adb/fastboot functions.
THE DRIVERS CAN BE INSTALLED DIRECTLY VIA THE TOOLKIT. OPTION 1 IN THE MAIN MENU.
If drivers are not installed or there is an exclamation mark next to the device:
Plug the device in to a usb cable directly connected to your motherboard.
In the Device Manager a new item, usually called Android 1.0 should pop up in the list.
Right click on the device item then left click on Update Driver Software. Select 'browse my computer' and then 'Let me pick from a list'.
If no adb interface driver appears in the list then untick 'Show compatible hardware' and find the Android or Samsung adb interface driver.
If you cannot find either of these click Have Disk, browse to the Toolkit install folder, drivers folder, click on android_winusb.inf and click Open.
Click OK and select Google ADB Interface.
Make sure you have USB debugging enabled in settings, developer options. In Android 4.2.2 or later you have to enable the developer options screen by going to settings, About on your device and click on Build number at the bottom 7 times until it says You are now a developer. If you have already enabled usb debugging then unplug/replug the usb cable.
On Android 4.2.2 or later when you replug the usb cable after enabling usb debugging for the first time you will get a popup asking you to authenticate your pc. Tick 'Always allow' then click 'ok'.
--------------------------------------------------------------
2. USING SKIPSOFT UNIFIED ANDROID TOOLKIT
When starting the Toolkit you will first be asked which device you want to work with. Working folders will be created and the device files downloaded. You will then be taken to the Model/Build selection screen where you can do a number of things (other than select your model/build): Type '00' to enter your activation code and enable pro features, 'i' will take you to the Information and Help Section, 'a' will give you information on how to add support for a new build.
Supported builds are listed in the Model/Build selection screen and typing the associated number (i.e. 11) will download needed boot and recovery files (stock and custom recovery) then check for and download the latest superuser files available and custom recovery (pro versions only), verify all the files and start the Main Menu. You can now use all the functions and tools the Android Toolkit offers. Pro users can select the "any build" option to root any build (useful if your build is not listed).
--------------------------------------------------------------
USEFUL INFORMATION
How to Hard Reboot the device
1. Unplug the USB cable.
2. Hold down the 'POWER' button for about 5-15 seconds until the device reboots
How to get into Recovery Mode
1. Unplug the USB cable.
2. Hold down the 'HOME' + 'VOLUME UP' + 'POWER' buttons for about 5-15 seconds until you see the Samsung logo on the screen.
3. Release all buttons straight away to enter Recovery Mode.
How to get into Download Mode (For Odin)
1. Unplug the USB cable.
2. Hold down the 'HOME' + 'VOLUME DOWN' + 'POWER' buttons for about 2-15 seconds until a WARNING! Screen appears.
3. Press the 'VOLUME UP' button to enter Download Mode.
--------------------------------------------------------------
*DISCLAIMER*
I take no responsibility for any fault or damage caused by using the Unified Android Toolkit. No warranties of any kind are given.
**FAQ**
Q. Help me I can't find my build in the Model Selection Screen
The Toolkit includes a selection of Insecure Boot Images to cover all the different builds available. As there are very many different builds it is impossible to include an image for every single build but some builds share the same Boot Image. If you have a build that isnt listed on the Model Selection Screen you can therefore use a similar build. The best way to go is up to the next available build as it should offer more compatibility with the build you are using but if that isn't available then try the next build below your one as it should still be almost identical as long as it is the same version (ie. 4.1.1).
The Model Selection Screen is there so that if a task in the ToolKit requires an insecure kernel [to perform adb root commands] and your phone doesnt already include one, a compatible boot image [with an insecure kernel included] can be flashed to provide adb root access.
If you have a Custom Rom flashed to your phone then it will most probably have an insecure kernel included so it doesn't really matter if your build is not listed on the Model Selection Screen and when asked [by certain functions] if you have an insecure kernel on your phone you can answer 'yes'. However if the function fails then your kernel may not be insecure in which case you can flash one from the ToolKit. If you need to do this make sure the right build [or closest available build] is set so you flash the right image for your phone.
----------------------------------------------------------------------------
Q. What is ADB Shell?
Adb shell is a linux command line tool (because android is based on linux) used to send commands to your android device. For S-ON devices, this is crucial for modifying files in the /system partition (where the rom sits) as you cannot modify anything in /system when the rom is running without S-OFF like removing system apps.
----------------------------------------------------------------------------
Q. Why do I need to back up my IMEI/EFS and how do I do it?
There well protected section of your device that is virtually immune to any kind of flashing and manipulation (unless of course you know how to access it). This part of the device contains information such as IMEI (or MEID and ESN in the case of CDMA devices), programming parameters for the device such as your account information (phone number, etc), data provisioning parameters, and a whole bunch of other things that, when not handled properly, can render a device completely useless. All of these are contained in the infamous \EFS folder. If anything messes with your EFS folder, unlike flashing a device (which could potentially lead to bricks as well) it could render your device completely useless as it will no longer be recognized by your carrier. If you are not planning on flashing anything to your device and want to stay on pure Stock then you may never have any problems but it is still advisable to backup this information just in case (better to be safe than sorry).
----------------------------------------------------------------------------
Q. Does flashing a custom image increase my flash counter?
Any image that is flashed via Odin that has been modified will increase the flash counter that can be viewed in the Download Mode on your device (if booted by holding the Volume Down, Home and Power buttons). You can reset the flash counter using an app by Chainfire called Triangles Away and can find instructions on how to use that in the Downloads section in the Toolkit.
----------------------------------------------------------------------------
Q. Will flashing Stock ROM via odin using the toolkit replace everything that was flashed before? recovery? etc?
Yes a Stock Image flashed via Odin will replace all your key partitions (boot, recovery, system) with the stock firmware. If you want to reset the phone back to an 'out of the box' state then you want to enter recovery and do a wipe first which will reformat your userdata partition.
----------------------------------------------------------------------------
Q. I flashed Custom Recovery but each time I reboot the Stock Recovery is back
There is an auto recovery restore system on certain Stock Android Builds that will reflash the Stock Recovery if you flash CWM on a Stock Rom.
Use Root Explorer to Mount the system folder as R/W (or use a free app from Google Play such as ES File Explorer). Rename the files /system/recovery-from-boot.p and /system/etc/install-recovery.sh (requires root). Now when you flash Custom Recovery it will NOT be overwritten after a reboot. You can also do this via the Toolkit.
----------------------------------------------------------------------------
Q. My AntiVirus program says the Toolkit files may be harmful
The exe compiled files are not digitally signed with a Microsoft certificate (as they cost money) so certain AntiVirus programs (mainly Norton and AVG Free) may pick it up as potentially harmful when it is not. They will pick up ANY file that doesn't contain a purchased Microsoft certificate in the same way. Just Restore the deleted file and exclude it from further scans and it will be fine. Or switch to a better AntiVirus program such as BitDefender.
----------------------------------------------------------------------------
Q. I flashed the Toolkit Boot Image, now my wifi + bluetooth won't work
The boot images are made from Stock with only needed changes made to the insecure boot images [modified adbd, default.prop and rc.local edited] and will work on all stock roms. If you flash them to a custom rom and the rom has been altered or uses a custom boot image then it will boot but certain modules may not load such as wifi or bluetooth. In this case you can use the boot image to root or perform adb root functions but will need to flash back the boot image for the custom rom to get other functions working again. This is not a fault of the Toolkit but a difference to stock in the custom rom.
----------------------------------------------------------------------------
Q. I am having trouble getting adb working with the drivers installed
Try switching your connection type from media (MTP) mode to camera mode (P2P). To do this open the notification area, click where it says connected as and change from MTP to PTP.
----------------------------------------------------------------------------
Q. I want to send my device back for warranty purposes
1. Follow the instructions to reset your flash counter with TriangleAway.
2. Download and flash a Stock Firmware image from the download section.
3. Boot into Stock Recovery and perform a wipe/factory reset
.
Your internal storage will be formatted and data and cache wiped. Your device should now be back to an out-of-the-box FULLY STOCK state with the flash counter [shown if you boot to download mode manually] reset and ready to send back.
----------------------------------------------------------------------------
Q. When connecting the phone I get 'USB Device not Recognized' and no serial number shows in the ToolKit
I actually had this problem recently and what fixed it for me was to make sure that the drivers have been installed, then shut my phone down plug the usb cable in and restart it. The phone booted up and the device was recognized and drivers installed correctly. May not work for everyone but worth trying.
----------------------------------------------------------------------------
Q. "Superuser/SuperSU has stopped" message after rooting
After updating Samsung device to newer builds of Android [4.3 and later] which contains the new security from Samsung "Samaung KNOX", you might face a problem if you tried to root your device.
This might happen because of KNOX security, it blocks/disables the Superuser app and you will see this notification after the first boot:
"Unfortunately, SuperSU has stopped" or "Unfortunately, Superuser has stopped" depending on the root method you used.
The easiest way to fix this problem is by installing the superuser apk file. Select option 6 from the Rooting Section and the Toolkit will attempt to extract the superuser.apk file from the root zip file in the Root folder and if successful it will then be installed. You can then run the app [Superuser or SuperSU] from the apps list. A warning message will pop up saying Samsung KNOX has been detected and ask if you want to try and disable it. Click OK, KNOX should be disabled and your device should now be properly rooted.
**UPDATES**
**VIDEOS**
mskip said:
**VIDEOS**
Click to expand...
Click to collapse
Glad to see you here, used your toolkit on S3. Thank you for your work
Many thanks
Used this with great success with the note 2, excellent tool, just updated (donated version)
Many thanks
One of the best tools ever now available for the Note 3 :laugh: what a great surprise :good:
Thank You for this great work and for your tools which made our life easier
Thank you! :laugh:
Cool, just got my Note 3 at the right time it seems
Thanks!
Nice work and many thanks :good:
Oops, wrong thread
Sent from my SM-N900T using Tapatalk
I used your toolkit with succes on the Note 2 but on the note 3 with buildnumber KOT49H.N9005XXUENB4 it won't install TWRP (yes I chose rename files) so no root or custom recovery.
Do you have any idea Mark?
this toolkit grows knox if i try to root note 3?
Finally for Note 3...
Hey guy,
I appreciate your hard work on this awesome program. I really do.
BUT, a donation amount should be at the behest of the donator.
At 4 GBP minimum I simply can't afford to donate to you. The thing that upsets me is the fact I wasn't even after the pro features, I simply wanted to show you my appreciation. It just seems like you're stopping yourself from letting people buy you a beer.
Any alternative donation methods? One's that don't restrict to the minimal amount of money.
Like I said, I don't really care about the pro benefits.
---------- Post added at 01:54 AM ---------- Previous post was at 12:55 AM ----------
Herzog56 said:
I used your toolkit with succes on the Note 2 but on the note 3 with buildnumber KOT49H.N9005XXUENB4 it won't install TWRP (yes I chose rename files) so no root or custom recovery.
Do you have any idea Mark?
Click to expand...
Click to collapse
You are probably being KNOX-blocked. Search XDA for turning off KNOX protections. This may help you actually: http://forums.androidcentral.com/samsung-safe-knox/366118-solution-how-permanently-remove-knox.html If not this then I don't know. Though I do remember seeing "Write protection" on download mode.
Maybe that's why you're having problems.
Image of that here:
hello,
or at the very root and flash a custom recovery without switching to flag knox 0x1? or is 0x0.
stevles said:
Hey guy,
I appreciate your hard work on this awesome program. I really do.
BUT, a donation amount should be at the behest of the donator.
At 4 GBP minimum I simply can't afford to donate to you. The thing that upsets me is the fact I wasn't even after the pro features, I simply wanted to show you my appreciation. It just seems like you're stopping yourself from letting people buy you a beer.
Any alternative donation methods? One's that don't restrict to the minimal amount of money.
Like I said, I don't really care about the pro benefits.
Click to expand...
Click to collapse
I understand your point about the minimum donation amount but had to set this because of people donating 1p just to get an activation code. There is a donation button right under my username on every one of my posts for users who do not want to donate much and there is no minimum amount set on that link.
Mark.
qxv1 said:
hello,
or at the very root and flash a custom recovery without switching to flag knox 0x1? or is 0x0.
Click to expand...
Click to collapse
Any custom image flashed sets the knox flag to 0x1.
Mark.
mskip said:
I understand your point about the minimum donation amount but had to set this because of people donating 1p just to get an activation code. There is a donation button right under my username on every one of my posts for users who do not want to donate much and there is no minimum amount set on that link.
Mark.
Click to expand...
Click to collapse
Bugger it I'll donate the full amount.
You seem like a good guy and 4 GBP isn't really all THAT much. I'll just have a cheap lunch tomorrow :victory:
mskip said:
Any custom image flashed sets the knox flag to 0x1.
Mark.
Click to expand...
Click to collapse
Pretty much, with the exception of using the mobile odin pro method Here. Still a chance to trip it or otherwise rape your device so I wouldn't recommend it unless you know what you're doing
mskip said:
Any custom image flashed sets the knox flag to 0x1.
Mark.
Click to expand...
Click to collapse
Ok, I get the idea but if I don't flash custom image just root, is it possible to keep Knox 0 ?
Thank you for your effort and job.
NEXUS 5X - SUPPORTS ALL VERSIONS UP TO THE LATEST ANDROID 7 BUILDS.
SEE SUPPORT LIST FOR PUBLIC/PRO VERSIONS *HERE*
NOTE: There is no insecure kernel available yet for Android 6 so those options have been disabled in the Toolkit. I will make some and enable the options as soon as possible.
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 your FastBoot Mode
1. Turn your phone off
2. Unplug your usb cable if you have one plugged in
3. Keep holding the 'Volume Down', '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
Show the Menu in the Stock Recovery Screen
1. Hold the Power button and keep holding as you press the Volume Up button quickly. The blue recovery menu screen should pop up.
--------------------------------------------------------------
*DISCLAIMER*
I take no responsibility for any fault or damage caused by using the Unified Android Toolkit. No warranties of any kind are given.
**UPDATES**
**FAQ**
**VIDEOS**
Do you know if this removes the forced encyrption?
There is an initial TWRP build out for bullhead now. No idea if it's ready for primetime, though.
Pikezer1337 said:
Do you know if this removes the forced encyrption?
Click to expand...
Click to collapse
Option 4,9 from the main menu will disable forced encryption. The toolkit will flash a minimally patched boot image then flash the stock recovery (for extra safety) and wipe the userdata partition. This will wipe your device and disable encryption which is needed for custom recovery to work.
I am currently adding some extra information in the root section to state that encryption needs to be disabled for TWRP to boot properly and will upload the new module files shortly.
Mark.
randman2011 said:
There is an initial TWRP build out for bullhead now. No idea if it's ready for primetime, though.
Click to expand...
Click to collapse
Thanks im adding it in now.
Mark.
Purchased an unlock for the 5x module last night and received it, but it does not work ("Incorrect code entered"). Everything is fully up to date, I've followed the troubleshooting advice in the error message and in the FAQ to try to resolve, but no joy. Phone is showing up tomorrow. If it comes to it, I guess I can go commando, but this is a handy tool to have around.
Interesting that when I look at the main menu, it says I last used the Nexus 5 (not 5x) module, even though I've for sure chosen the option for the 5x (option 05). Also the build listing when you choose the 5x option says Hammerhead and not Bullhead. Don't know if that is related to my activation woes or not. Anyway-have enjoyed using your tool on several devices, and I look forward to using it again!
sgravel said:
Purchased an unlock for the 5x module last night and received it, but it does not work ("Incorrect code entered"). Everything is fully up to date, I've followed the troubleshooting advice in the error message and in the FAQ to try to resolve, but no joy. Phone is showing up tomorrow. If it comes to it, I guess I can go commando, but this is a handy tool to have around.
Interesting that when I look at the main menu, it says I last used the Nexus 5 (not 5x) module, even though I've for sure chosen the option for the 5x (option 05). Also the build listing when you choose the 5x option says Hammerhead and not Bullhead. Don't know if that is related to my activation woes or not. Anyway-have enjoyed using your tool on several devices, and I look forward to using it again!
Click to expand...
Click to collapse
I'm having the same problem. Hope it gets straightened out soon. I even donated again thinking that would give me a different code, but it issued the same.
moeava said:
I'm having the same problem. Hope it gets straightened out soon. I even donated again thinking that would give me a different code, but it issued the same.
Click to expand...
Click to collapse
I know whats happened and im extremely sorry I will sort it out right now, upload a new device module so activation will work properly. I will post another message soon with instructions (run toolkitclean.exe, wipe nexus 5x device module and rerun the toolkit to download new module).
Back in a flash.
Mark.
Module files for the Nexus5X have now been updated and uploaded.
Exit the Toolkit if running, run the ToolkitClean.exe program from the Start Menu/Skipsoft Android Toolkit folder or directly, select option 05 to clean the Nexus5X module files and settings and then restart the Toolkit. Select the Nexus5X (option 05) to download new module files. This will fix all problems and contains the latest updates AND includes TWRP recovery for rooting (only build MDB08I is supported at the moment).
Please let me know if everything is ok now.
Mark.
mskip said:
Module files for the Nexus5X have now been updated and uploaded.
Exit the Toolkit if running, run the ToolkitClean.exe program from the Start Menu/Skipsoft Android Toolkit folder or directly, select option 05 to clean the Nexus5X module files and settings and then restart the Toolkit. Select the Nexus5X (option 05) to download new module files. This will fix all problems and contains the latest updates AND includes TWRP recovery for rooting (only build MDB08I is supported at the moment).
Please let me know if everything is ok now.
Mark.
Click to expand...
Click to collapse
Thanks Mark, update works.
sgravel said:
Purchased an unlock for the 5x module last night and received it, but it does not work ("Incorrect code entered"). Everything is fully up to date, I've followed the troubleshooting advice in the error message and in the FAQ to try to resolve, but no joy. Phone is showing up tomorrow. If it comes to it, I guess I can go commando, but this is a handy tool to have around.
Interesting that when I look at the main menu, it says I last used the Nexus 5 (not 5x) module, even though I've for sure chosen the option for the 5x (option 05). Also the build listing when you choose the 5x option says Hammerhead and not Bullhead. Don't know if that is related to my activation woes or not. Anyway-have enjoyed using your tool on several devices, and I look forward to using it again!
Click to expand...
Click to collapse
Everything should work fine now. Just follow the post *HERE* to update the device module.
Mark.
mskip said:
Everything should work fine now. Just follow the post *HERE* to update the device module.
Mark.
Click to expand...
Click to collapse
Working for me as well. Thank you!
Okay what am I doing wrong?
I am getting this error when using option 4 (root) and I tried using the allinone;
FAILED (REMOTE: unlock device to use this command).
Thanks, Bob
vandyman said:
Okay what am I doing wrong?
I am getting this error when using option 4 (root) and I tried using the allinone;
FAILED (REMOTE: unlock device to use this command).
Thanks, Bob
Click to expand...
Click to collapse
Well for starters the ALLINONE option has been disabled as the newest version of twrp doesn't work the the openrecoverscript needed for that function.
You need to unlock your bootloader (option 3 from the main menu) in order to flash images to your device. Thats what the message is about.
When you have unlocked (or just select no when asked if you have unlocked the bootloader) use option 4,1,1 to root. You need to be on MDB08I.
Mark.
Mark,
I solved my problem, I needed to use the OEM unlock option in the developer options.
The last time I unlocked and rooted was with the nexus 5 2013 and there was no such option.
LOL.
Thanks,
Bob
vandyman said:
Mark,
I solved my problem, I needed to use the OEM unlock option in the developer options.
The last time I unlocked and rooted was with the nexus 5 2013 and there was no such option.
LOL.
Thanks,
Bob
Click to expand...
Click to collapse
Yes that is a new option added for the new Android devices. There was a note about it in the bootloader unlocking procedure, maybe I should make it a bit more obvious. I will look in to that as there will be more devices that need that info now.
Mark.
Alright, I'm having a bit of an issue. I'm unlocked, TWRP installed, and running modified MDB08I. I am getting nowhere with root though. I get 'Recovery mode not detected' error. This happens after ABD mode, then it reboots into fastboot, then into TWRP. My phone is in TWRP when the error comes up in the toolkit.
I tried installing SU through TWRP. Install worked fine, but it won't allow me to update the binary through SU or TWRP.
Another issue that I'm finding is that when I am connected to the computer (PTP) I can only access the DCIM and Pictures folders on my internal storage. I'm assuming whatever fixes this particular issue will also likely fix the other problems I'm experiencing. I've got the LG drivers installed, and the device is recognized as a Nexus 5X in the device manager. Any suggestions?
Update: So I've got root (I guess). Root Checker says I've got root, but I cannot update SuperSU Binary. Also, while looking through the TWRP log, I see "E: Unable to mount '/data'