Related
GALAXY NEXUS - SUPPORTS ALL AVAILABLE VERSIONS
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 V1.4.1 [05th Oct 2015]
* Install correct adb/fastboot drivers automatically on Windows xp/vista/7/8 32bit+64bit
* Backup/Restore a single package or all apps, user data and Internal Storage
* Backup your data from selectable folders [internal or external storage] to your PC for a Full Safe backup of data
* Unlock/Re-Lock your Bootloader [Nexus]
* Root Stock builds
* Various Root options using insecure boot image or custom recovery
* ALLINONE to Unlock, Root, Rename the Restore Files and install busybox [Nexus]
* ALLINONE to flash custom Recovery Root, Rename the Restore Files and install busybox [Samsung]
* [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
--------------------------------------------------------------
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.
Manual Rooting Instructions for Galaxy Nexus
UPDATES:
VIDEOS:
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.
thnx man!
Works great. very easy and effective. happy to be rooted and have custom recovery and unlocked boot loader. thnc again for hooking us up so quickly.
Much recomended for all users. Easy and all the options and extras you'll need. Then just flash away..............
dangambino said:
Works great. very easy and effective. happy to be rooted and have custom recovery and unlocked boot loader. thnc again for hooking us up so quickly.
Click to expand...
Click to collapse
You're welcome
Can you just confirm if the cwm included in the ToolKit works with the Sprint phone as I have seen nothing about that working or not.
Mark.
mskip said:
You're welcome
Can you just confirm if the cwm included in the ToolKit works with the Sprint phone as I have seen nothing about that working or not.
Mark.
Click to expand...
Click to collapse
Works for me. Flashed it perm and the first thing i did was do a backup. No issues thus far. About to flash Team Win's to see what its all about. But yeah, its working.
whats option 5 rename recovery restore file and also i see manual wipes everything but does the tool kit? i assume the tool kit does too but would just like to clarify thanks.
Anon9mouz said:
whats option 5 rename recovery restore file and also i see manual wipes everything but does the tool kit? i assume the tool kit does too but would just like to clarify thanks.
Click to expand...
Click to collapse
With the non google stock roms there are 2 files that 'could' be present in the system folder. If these files are present and you flash a custom recovery image such as cwm or twrp then on your next reboot the stock recovery will be reflashed and you will lose your custom recovery. To stop this from happening I simply rename the 2 files if they are present so they cant do any harm. The exact commands I use are:
adb-toolkit shell mv /system/recovery-from-boot.p /system/recovery-from-boot.p-old
adb-toolkit shell mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh-old
Click to expand...
Click to collapse
You can rename them yourself but you need root access and a root explorer.
Unlocking the bootloader will wipe EVERYTHING including the virtual sd card whether done manually or using the ToolKit there is no way round this. Even flashing a rom via odin with the phone still locked will unlock the phone and wipe it during the process.
Mark.
Skip I just sent you a message regarding the radio pull CMD
mskip said:
With the non google stock roms there are 2 files that 'could' be present in the system folder. If these files are present and you flash a custom recovery image such as cwm or twrp then on your next reboot the stock recovery will be reflashed and you will lose your custom recovery. To stop this from happening I simply rename the 2 files if they are present so they cant do any harm. The exact commands I use are:
You can rename them yourself but you need root access and a root explorer.
Unlocking the bootloader will wipe EVERYTHING including the virtual sd card whether done manually or using the ToolKit there is no way round this. Even flashing a rom via odin with the phone still locked will unlock the phone and wipe it during the process.
Mark.
Click to expand...
Click to collapse
O OK thanks for that. I see u mention odin I see it was used for everything with the epic 4g touch (SGS2) but I don't see that yet from this even tho there's a dl mode? Well thanks
_____________________________________________________
Sent from my SPH-L700-GNEX-using Tapatalk 2
Anon9mouz said:
O OK thanks for that. I see u mention odin I see it was used for everything with the epic 4g touch (SGS2) but I don't see that yet from this even tho there's a dl mode? Well thanks
_____________________________________________________
Sent from my SPH-L700-GNEX-using Tapatalk 2
Click to expand...
Click to collapse
I think people just prefer using fastboot I know I certainly do.
Mark.
Awesome, going to check it out ASAP. I hate not being able to install my root required apps (ES Explorer/Titanium/etc).
Just got my GNex yesterday, was only one of two that the store got.
LAYGO said:
Awesome, going to check it out ASAP. I hate not being able to install my root required apps (ES Explorer/Titanium/etc).
Just got my GNex yesterday, was only one of two that the store got.
Click to expand...
Click to collapse
You're lucky then I think there has been more demand for the Nexus than anyone thought and most places are out of stock.
Mark.
mskip said:
You're lucky then I think there has been more demand for the Nexus than anyone thought and most places are out of stock.
Mark.
Click to expand...
Click to collapse
I KNOW! I tried doing the preorder, but I had just dropped $4500 on getting my roof repaired & the funds were all tied up. By time I had em, the preorder had closed.
I half expected a line or something when I got there, but wasn't anyone. Asked for it, she said "hmm, let me check". Came back with one in her hand saying they only received two & mine was the last one.
I'm not taking time to set it all up until I root it . . . only to repeat it. I'm kinda befuddled about the lack of SD Card slot though. I didn't realize it didn't come with one until I had pulled the battery looking for where it mounted!
LAYGO said:
I KNOW! I tried doing the preorder, but I had just dropped $4500 on getting my roof repaired & the funds were all tied up. By time I had em, the preorder had closed.
I half expected a line or something when I got there, but wasn't anyone. Asked for it, she said "hmm, let me check". Came back with one in her hand saying they only received two & mine was the last one.
I'm not taking time to set it all up until I root it . . . only to repeat it. I'm kinda befuddled about the lack of SD Card slot though. I didn't realize it didn't come with one until I had pulled the battery looking for where it mounted!
Click to expand...
Click to collapse
Plus one on no sd
_____________________________________________________
Sent from my SPH-L700-GNEX-using Tapatalk 2
Will be doing this when I get home from work! I was glad I picked my GNex up yesterday...it was the only one my store received! So I was quite happy...can't wait for more support on the sprint side.
I couldn't wait, I rooted after lunch. Getting Swype installed, first thing, EVERY time. I needs my Swype!
Then to get some apps on there. Connection sucks at work though.
Can someone please pull the radio for the sprint galaxy nexus
I did a n00b mistake and restored a google factory image for VZW on my Sprint Galaxy Nexus...
Any help would be greatly appreciated!!!
I may have spoke so soon. I'm getting error 7 assert fail when flashing a twrp recovery zip. Is that an issue with the recovery on the toolkit or the zip. I flashed a teerom and kernel with no issues though.....
Hello, I got the Huawei 651F watch yesterday (bought from amazon.de) and I wonder which is the latest software version?
I'm running on Android Wear 1.3.0.2421912, Google Play Services 9.4.52, Android OS 5.1.1 . I think there is a new version out (which supports speaker and keyboard), but when I click on "System Update" it says my system is up-to-date!
Any ideas?
Mine is running on Android Wear 1.5.0.xxxxx, Google play services 9.4.52 and Android OS 6.0.1
I've had some trouble to get it updated when I bought it, but it was just a matter of time (I guess until the phone wear app downloaded the wear update)
But, for the keyboard it's only available in Android Wear 2 developer preview...
Thanks for your reply. It seems that I run an older version.
So you just waited until the update? How long?
I don't have to do anything and the watch will update itself? No wi-fi on, no other setting etc?
Make sure watch is fully charged and better put watch on charger when checking for updates and have WiFi enabled
That worked for me...
Thanks for your reply.
Tried it and didn't work for me. It still says system is up to date.
No idea if there is meaning in just waiting. It's an old update right?
Be patient, it will come.
Sent from my Nexus 10 using Tapatalk
Other solution if you don't want to wait is to flash the latest stock version with adb/fastboot
I just wanted to know if there's a meaning in waiting.
In addition after I restart my phone the watch loses the recent contacts list (2 swipes right). How can I get it back?
EDIT: Nevermind, I turned on Bluetooth debugging on the phone only (not in the watch) and restarted the phone and contacts are back. I'm not sure I understand what Bluetooth debugging is or if it had anything to do with it.
I've tried restoring to factory defaults in order to get the 1.5 update with no luck. How can I update from 1.3 to 1.5 manually? Any link would be appreciated.
Here you can find the preview image (android wear 2.0 developer preview) and the original image (named : Non-preview image (for after testing)). Make sure you download Huawei watch image and not the LG one : https://developer.android.com/wear/preview/downloads.html
You'll have to flash the "non-preview image" with adb/fastboot
Still no update, despite checking while charging etc. Is there meaning in waiting?
Could you give me the latest "stable" version, with a detailed guide? I remind you that I have version 1.3, so I need a full version to 1.5, not incremental. Right? I think I need to make changes in the phone too, not only download the version and toolkits.
Don't know why you still don't have the update...
For the latest stable version, it's the one I gave you in my last post. The guide to flash it is detailed under the links. Don't worry, it's a full 1.5 version.
You need to have SDK manager (in order to install and use adb/fastboot), but nothing have to be done on your phone (just unpair the watch) : everything else is done from the charger connected to your computer
Thanks.
I meant the watch, not the phone.
So I download the non preview image? The links you provided are for some version 2.0 of wear, not 1.5?
Yes the non-preview is wear 1.5 : Google give this image as a way to revert back to a stable release after testing the wear 2.0 developer preview. In your case, you can just flash it to manually update to official wear 1.5
Sorry for my persistance but I have no experience with android wear plus flashing a watch. Could you check the versions in the screenshots and tell me if it's ok to proceed?
I have to download and flash the following image?
sturgeon-mec23l-factory-48003078.tgz
MD5: 417b5cbddb29a2262bce133e283d2732
SHA-1: 4800307843580f818557dd7c43d8ba2161e289b2
I believe the guide is missing some instructions, in example it says to download and unzip the image, but it doesn't say copy the file in the watch. Don't I have to download the file in my computer, unzip it there, then transfer it to the root directory of the watch? Or like in the phones, you have to transfer the zip file to the device you want to upgrade?
Thanks again.
No problem, but you'll see that in fact, phone or watch, it's very similar !
Yes, this is the good one to download : sturgeon-mec23l-factory-48003078.tgz
About your screenshots, it's ok : it's not an update, it's a full system image which will wipe everything during install (so you could install it on the top of every wear version). I just read again the guide, there is nothing missing : the "flash-all" script is in fact composed of several "adb" commands which will push and install bootloader, rom, recovery, ... as you would had done with a nexus device (exactly the same process).
I think you was thinking about installing it with TWRP, but it's not a zip file as a custom rom.
So I download the file and unzip it in the watch or in my pc?
Furthermore, I don't undestand the following:
"Confirm installation of the fastboot tool
To flash a device using one of the system images, confirm that you have the fastboot tool in the platform-tools/ directory of the Android SDK. Be sure that you have the latest version of the Android SDK Platform-tools from the SDK Manager.
After you confirm that you have the fastboot tool, add the tool to your PATH environment variable so the tool can be found when you flash the watch."
I've download ANDROID STUDIO 2.1.3, but can't find where the platform-tools/directory is? I clicked on Configure -> SDK Manager and installed Android 7, 6, 5.1, 5. I don't know if it was needed...
The part that you don't understand is about adb/fastboot utility which are needed to push the file and install them on your watch. Anyway, you said that you installed Android Studio (it was not really needed) but adb/fastboot is automaticaly installed with it ! So it's a good point.
First, you'll have to search for your sdk folder. Usually it's located in : "C:\Users\<--user name-->\AppData\Local\Android\sdk". There is inside a folder "platform-tool" which contain among all the files adb.exe and fastboot.exe
Then, unzip the tarball (sturgeon-mec23l-factory-48003078.tgz) in this folder. Then Shift + Right-click in the background of the folder and select "open a command window there" (or something like that, my computer is not in english).
Finaly, follow the guide :
2. Attach the watch charger to the watch and plug the USB cord (from the charger) into your computer.
3. Use the following adb command to confirm that the watch is available for flashing: adb devices
4. Use the following adb command to start the device in fastboot mode: adb reboot bootloader
5. Unlock the device's bootloader. This step erases all data on the device: fastboot oem unlock
On the watch, select the Unlock option.
6. Issue the command: flash-all.bat
7. Optionaly, you can lock again your bootloader by the command: fastboot oem lock
Found it thanks.
Frixx_x said:
The part that you don't understand is about adb/fastboot utility which are needed to push the file and install them on your watch. Anyway, you said that you installed Android Studio (it was not really needed) but adb/fastboot is automaticaly installed with it ! So it's a good point.
First, you'll have to search for your sdk folder. Usually it's located in : "C:\Users\<--user name-->\AppData\Local\Android\sdk". There is inside a folder "platform-tool" which contain among all the files adb.exe and fastboot.exe
Then, unzip the tarball (sturgeon-mec23l-factory-48003078.tgz) in this folder. Then Shift + Right-click in the background of the folder and select "open a command window there" (or something like that, my computer is not in english).
Finaly, follow the guide :
2. Attach the watch charger to the watch and plug the USB cord (from the charger) into your computer.
3. Use the following adb command to confirm that the watch is available for flashing: adb devices
4. Use the following adb command to start the device in fastboot mode: adb reboot bootloader
5. Unlock the device's bootloader. This step erases all data on the device: fastboot oem unlock
On the watch, select the Unlock option.
6. Issue the command: flash-all.bat
7. Optionaly, you can lock again your bootloader by the command: fastboot oem lock
Click to expand...
Click to collapse
Frixx_x thanks a lot mate, I've updated the phone as described. Still the version in the link you gave me is Android Wear 1.4 (6.0.1 Android), not 1.5. If I don't see it updating in the next days is there a way for 1.5?
Hello all XDA Developers and site visitors,
I recently picked up a Junsun A931 Rear View Mirror on AliExpress and didn't see any forums on it. So, I decided to write my own about how I managed to gain root and install Magisk. Links to all the files will be included.
This works for Junsun's A930/A931 with Android 5.1. The process will probably work for other Rear view Mirrors with MTK chips, you will need to have access to the boot.img and scatter file for your device.
**Disclaimer: Proceed at your own risk! Although this worked for me without issues, there is always a chance of bricking your devices/making your device unusable. I am not responsible for your device(s).
Instructions:
1. Install MTK Drivers provided.
**I only have the ones for Windows. Mac/Linux, I couldn't find any MTK drivers for you.
**If you have trouble installing drivers, try turning off "signed drivers" in Windows Recovery.
2. Attach device to computer via USB cable.
3. If computer doesn't recognize device when it's fully booted:
-Go to "Set Up"
-Slide over to "Other" tab
-Scroll down to "Version"
-Click on "Version" until it brings up a menu (Same principle as Developer Mode, except it pop's up a menu)
-Click on "USB Host"
-Select "USB Device" (the one that has "adb" in the description)
**If this doesn't work, then try switching USB ports on your computer. It only ever works on my USB 3.0 ports.
4. Install Kingoroot on PC.
5. Launch Kingoroot and let it recognize your device, then click "Root."
** This is only a temporary root. It will reset every time you shutdown/restart. If that's what you want, stop here. Otherwise, continue on.
PERMANENT ROOT:
6. Open your choice of ADB on your PC. (I used Minimal ADB and Fastboot)
-Type "adb devices" to see if your devices is recognized and listed.
-Type "adb install [location of magisk.apk on computer]"
**replace "[location of magisk.apk on computer]" with location of magisk.apk (provided in RootPack.zip). This can be done by just dragging the file into adb or you can type the address from Windows Explorer.
-Type "adb push [location of boot.img for device] /sdcard/download"
**replace "[location of boot.img for device]" with location of boot.img for YOUR DEVICE. USING A BOOT.IMG FOR A DIFFERENT DEVICE WILL MOST LIKELY RESULT IN YOUR DEVICE BEING BRICKED!!! That being said, I have provided the software for Junsun A930/A931 for Android 5.1. If you have a different device, you will need the boot.img for it.
-Type "adb install [location of file explorer apk]" or install an file explorer from the Playstore, etc.
**replace "[location of file explorer apk]" with file explorer of your choice. I used ES Explorer.
7. Now open Magisk on the Rear View Mirror. (Make sure you're either connected to WiFi or Data)
**Be sure to grant it SuperUser Permission from Kingo SuperUser.
- Click "Install" next to "Magisk is not installed"
- Click "Install" on propt that pops up
- Choose "Select and patch a file" option.
- Scroll down and click on Es Explorer (or the file explorer you chose)
- Now go into the "download" folder and click the "boot.img"
- Click the option "File way"
**The "Normal Android Way" option kept failing for me.
- Let this complete.
8. Go back into ADB on the PC
- Type 'adb pull "sdcard/download/magisk_patched.img" C:/Downloads'
**You can replace "C:/Downloads" with whatever location you want to pull the file to on your computer.
9. Launch SP Flash Tool on your PC (provided in RootPack.zip)
-Load Scatter File by clicking the "Scatter-loading" button next to "Scatter-loading File" in the "Download" tab.
**This can be found in the firmware that I've provided, IF you have the Junsun A930/A931. If you have a different device, load the scatter file for it, instead.
-Now unclick all the boxes.
-Now click the box for "location" on the "boot" aisle.
-Select the "magisk_patched.img" that we just made from C:/Downloads or wherever you saved yours. Click "Open."
-It should have now have put the location of your "magisk_patched.img" file in the "location" box and the box next to the "boot" aisle should now be selected again (If not, make sure it is. Also, that it is the only one selected)
-Now click on the "Download" button (with the Green Arrow) at the top.
-Hold the home button the Rear View Mirror and click "Restart" (be sure to keep the mirror connect to the computer via USB)
-Now let the bar at the bottom finish.
-When it's done, there will be a pop-up that says "Download OK"
-Your device will restart
10. In your Mirror, launch Magisk Manager.
-Congratulations! The Magisk Installed option should now be green and you should have permaroot! Enjoy!
**You can now uninstall Kingo SuperUser.
Links:
Root Pack: https://drive.google.com/open?id=11poc-Pr30J_aPmhVJktuqZx1H9fkX371
Firmware: https://drive.google.com/open?id=19zUz_piQ6aiO_uGCQTmKpC9ErAR5-4xZ
A BIG THANK YOU TO THE DEVELOPERS AT MAGISK, KINGOROOT, MINIMAL ADB AND FASTBOOT, MTK DRIVERS, SP FLASH TOOL, XDA, AND EVERYONE ElSE WHO ATTRIBUTED TO THIS THROUGH DEVELOPMENT OF PROGRAMS USED! IF THIS WAS HELPFUL, BE SURE TO THANK ALL OF THEM!
great tutorial, really appreciate it
locale?
Thanks
seeing the A930P mt6735 root here, reboot after root language becomes us and timezone becomes China
I think I'm back to the default, but if you change the language, time zone to Japan and then restart it, it will go back to the default again
Do you need to change settings with build props etc?
otan032 said:
Thanks
seeing the A930P mt6735 root here, reboot after root language becomes us and timezone becomes China
I think I'm back to the default, but if you change the language, time zone to Japan and then restart it, it will go back to the default again
Do you need to change settings with build props etc?
Click to expand...
Click to collapse
Hmm.. could you give me some more information? Did you install Magisk or just use the temporary root with KingoRoot?
You could probably edit the build.prop to get the correct results by changing the "en" to "jp" for Japanese (or the whatever region). However, I'm not sure why yours is resetting to default after reboot? Mine always retains the settings after restarting. So if you could give me a little more information, I'll see if I can figure out what's the problem.
Great write up! Thank you.
I ended up picking a diff model Junsun /w 2gb RAM and am having issues with the USB port:
aliexpress : /item/32844242296.html
It won't recognize any USB devices, so assuming the drivers are missing or it's disabled permanently somehow. This unit is not powered thru USB port, there are separate 12v +/- to hardwire in. I've tried multiple USB cables as well.
I tried USB sticks for storage, but my actual intent is to hook up a USB DAB+ antenna like I'm using on another vehicle's Android
HeadUnit:
aliexpress: item/33003465623.html?spm=a2g0s.9042311.0.0.5ad74c4dUcy6j9
I just need basic USB drivers and 5V output on the USB port, any ideas on how to get this working or add drivers onto the existing ROM etc.?
Thanks!
iamrance.asa said:
Hello all XDA Developers and site visitors,
I recently picked up a Junsun A931 Rear View Mirror on AliExpress and didn't see any forums on it. So, I decided to write my own about how I managed to gain root and install Magisk. Links to all the files will be included.
This works for Junsun's A930/A931 with Android 5.1. The process will probably work for other Rear view Mirrors with MTK chips, you will need to have access to the boot.img and scatter file for your device.
**Disclaimer: Proceed at your own risk! Although this worked for me without issues, there is always a chance of bricking your devices/making your device unusable. I am not responsible for your device(s).
Instructions:
1. Install MTK Drivers provided.
**I only have the ones for Windows. Mac/Linux, I couldn't find any MTK drivers for you.
**If you have trouble installing drivers, try turning off "signed drivers" in Windows Recovery.
2. Attach device to computer via USB cable.
3. If computer doesn't recognize device when it's fully booted:
-Go to "Set Up"
-Slide over to "Other" tab
-Scroll down to "Version"
-Click on "Version" until it brings up a menu (Same principle as Developer Mode, except it pop's up a menu)
-Click on "USB Host"
-Select "USB Device" (the one that has "adb" in the description)
**If this doesn't work, then try switching USB ports on your computer. It only ever works on my USB 3.0 ports.
4. Install Kingoroot on PC.
5. Launch Kingoroot and let it recognize your device, then click "Root."
** This is only a temporary root. It will reset every time you shutdown/restart. If that's what you want, stop here. Otherwise, continue on.
PERMANENT ROOT:
6. Open your choice of ADB on your PC. (I used Minimal ADB and Fastboot)
-Type "adb devices" to see if your devices is recognized and listed.
-Type "adb install [location of magisk.apk on computer]"
**replace "[location of magisk.apk on computer]" with location of magisk.apk (provided in RootPack.zip). This can be done by just dragging the file into adb or you can type the address from Windows Explorer.
-Type "adb push [location of boot.img for device] /sdcard/download"
**replace "[location of boot.img for device]" with location of boot.img for YOUR DEVICE. USING A BOOT.IMG FOR A DIFFERENT DEVICE WILL MOST LIKELY RESULT IN YOUR DEVICE BEING BRICKED!!! That being said, I have provided the software for Junsun A930/A931 for Android 5.1. If you have a different device, you will need the boot.img for it.
-Type "adb install [location of file explorer apk]" or install an file explorer from the Playstore, etc.
**replace "[location of file explorer apk]" with file explorer of your choice. I used ES Explorer.
7. Now open Magisk on the Rear View Mirror. (Make sure you're either connected to WiFi or Data)
**Be sure to grant it SuperUser Permission from Kingo SuperUser.
- Click "Install" next to "Magisk is not installed"
- Click "Install" on propt that pops up
- Choose "Select and patch a file" option.
- Scroll down and click on Es Explorer (or the file explorer you chose)
- Now go into the "download" folder and click the "boot.img"
- Click the option "File way"
**The "Normal Android Way" option kept failing for me.
- Let this complete.
8. Go back into ADB on the PC
- Type 'adb pull "sdcard/download/magisk_patched.img" C:/Downloads'
**You can replace "C:/Downloads" with whatever location you want to pull the file to on your computer.
9. Launch SP Flash Tool on your PC (provided in RootPack.zip)
-Load Scatter File by clicking the "Scatter-loading" button next to "Scatter-loading File" in the "Download" tab.
**This can be found in the firmware that I've provided, IF you have the Junsun A930/A931. If you have a different device, load the scatter file for it, instead.
-Now unclick all the boxes.
-Now click the box for "location" on the "boot" aisle.
-Select the "magisk_patched.img" that we just made from C:/Downloads or wherever you saved yours. Click "Open."
-It should have now have put the location of your "magisk_patched.img" file in the "location" box and the box next to the "boot" aisle should now be selected again (If not, make sure it is. Also, that it is the only one selected)
-Now click on the "Download" button (with the Green Arrow) at the top.
-Hold the home button the Rear View Mirror and click "Restart" (be sure to keep the mirror connect to the computer via USB)
-Now let the bar at the bottom finish.
-When it's done, there will be a pop-up that says "Download OK"
-Your device will restart
10. In your Mirror, launch Magisk Manager.
-Congratulations! The Magisk Installed option should now be green and you should have permaroot! Enjoy!
**You can now uninstall Kingo SuperUser.
Links:
**I am unable to add links due to how new my account is. For the files as of now, search "[Root] Junsun Android 5.1 Rear View Mirror A930/A931 " on YouTube and all the links are in the description. I will update here as soon as time allows.
A BIG THANK YOU TO THE DEVELOPERS AT MAGISK, KINGOROOT, MINIMAL ADB AND FASTBOOT, MTK DRIVERS, SP FLASH TOOL, XDA, AND EVERYONE ElSE WHO ATTRIBUTED TO THIS THROUGH DEVELOPMENT OF PROGRAMS USED! IF THIS WAS HELPFUL, BE SURE TO THANK ALL OF THEM!
Click to expand...
Click to collapse
Also, just adding more info to my post above.
I've tried contacting Junsun directly and thru AliExpress, they weren't helpful and just advised this feature isn't supported.
Apparently the USB port can be used for flashing firmware, but no other information.
rochbaz said:
Great write up! Thank you.
I ended up picking a diff model Junsun /w 2gb RAM and am having issues with the USB port:
aliexpress : /item/32844242296.html
It won't recognize any USB devices, so assuming the drivers are missing or it's disabled permanently somehow. This unit is not powered thru USB port, there are separate 12v +/- to hardwire in. I've tried multiple USB cables as well.
I tried USB sticks for storage, but my actual intent is to hook up a USB DAB+ antenna like I'm using on another vehicle's Android
HeadUnit:
aliexpress: item/33003465623.html?spm=a2g0s.9042311.0.0.5ad74c4dUcy6j9
I just need basic USB drivers and 5V output on the USB port, any ideas on how to get this working or add drivers onto the existing ROM etc.?
Thanks!
Click to expand...
Click to collapse
So MTK usually doesn't recognize in Windows the traditional way. You'll need a MTK program or the ADB/Fastboot. Since I don't have this model, I have no way to test it but I would look around the settings to see if there are some extra settings menus like developer mode. In the A930, they have extra menu by clicking the "version" and tapping it multiple times (not Android's but Junsun's custom one).
The driver's that I provide here: https://drive.google.com/file/d/11poc-Pr30J_aPmhVJktuqZx1H9fkX371/view?usp=drivesdk
Should work for your model since it uses the same processor. It should be able to recognize it on start but if it doesn't recognize it when it boots up then there's probably something in settings that will enable it to. It will probably be hidden since it's most likely only for developers who were working on the rom.
Hello I've just rooted my junsun A930 alps-1.6.91 with Dr. Fone root, it showed device as ASUS A10 but rooted no problem and so far seems permanent..
Monkandi said:
Hello I've just rooted my junsun A930 alps-1.6.91 with Dr. Fone root, it showed device as ASUS A10 but rooted no problem and so far seems permanent..
Click to expand...
Click to collapse
Thanks ! It works! I try many times with Kingoroot, but allways fail. My mirror is recognized as MediaTek FX. It is android 5 . Is there any options to upgrade it to newest Android version?
Hello I'm looking for upgrade or custom rom myself, if I find anything I will let you know, but we're already in the best place XDA for it to happen... Good luck
I ask on Junsun Official Store and their answer: "Our equipment cannot upgrade the system. The system is fixed in the device..." So , no solution from official.
Monkandi said:
Hello I'm looking for upgrade or custom rom myself, if I find anything I will let you know, but we're already in the best place XDA for it to happen... Good luck
Click to expand...
Click to collapse
It depends on if anyone will spend the time to build an update rom or port for that device. If you send your device info, someone might end up working on it for you
nejcov said:
I ask on Junsun Official Store and their answer: "Our equipment cannot upgrade the system. The system is fixed in the device..." So , no solution from official.
Click to expand...
Click to collapse
I doubt it will ever have the support for the most current Android version. Most devices like this don't receive updates from official channels and the product isn't popular enough for most developers to have it.
updating fail due to power failed
I am using 4G Junsun A930 model DVR (1GB RAM) I have lost my framework "alps.l1.mp3.v2.95_t98_v2.1.10" I try to flash "full_E08_KM_4G_9.35_WJ_EN_1.6.91" but failed. any possibility to flash my dvr or get "alps.l1.mp3.v2.95_t98_v2.1.10" framework
ajish110 said:
I am using 4G Junsun A930 model DVR (1GB RAM) I have lost my framework "alps.l1.mp3.v2.95_t98_v2.1.10" I try to flash "full_E08_KM_4G_9.35_WJ_EN_1.6.91" but failed. any possibility to flash my dvr or get "alps.l1.mp3.v2.95_t98_v2.1.10" framework
Click to expand...
Click to collapse
Contact them and ask for the firmware for your device. They will most likely send you it. Flash it instead.
Then follow the steps I outlined but using the firmware they sent you instead. That is if you want root.
I requested but they are not respond
---------- Post added at 10:22 AM ---------- Previous post was at 10:10 AM ----------
Orginal firmware ony we can flash in mtk mt6753 chipset? No other solution? I try miracle tool it shows mt 6753 then try to read boot8 after tool auto shutdown
Do you have a picture of the back of your device?
I don't know of any other tools/methods. There's some other programs for MTK development but they won't be much help in this case. You'll need to get the stock firmware back before anything. There's no programs to find suitable software nor is there a cross-reference. There is also no custom roms for these devices. Thus, why root and Magisk integration is such a positive.
drive.google.com/file/d/1Q9v9S_F3OXGp5h-ekh_yAdtJAk246ukY/view?usp=drivesdk
---------- Post added at 11:34 AM ---------- Previous post was at 11:33 AM ----------
drive.google.com/file/d/1Q0Jsw5QbNm2NRsE9vPAr1nXd8_7s_dja/view?usp=drivesdk
There was no access so I requested it
Ok now added
***Warning: I am not responsible for bricked or broken devices, warranties, computers, etc. This is your phone and your free will to follow the below steps and you bare the full burden of any consequences.***
A note for the Moderators: I am aware that the information I am about to provide exists outside of this thread. The purpose of this is not for redundancy or to clutter the forum. I am making this thread because I had to go to SEVERAL different sources to find these solutions and pull pieces from each. Hopefully, this is comprehensive enough to help someone who may have been in the same boat I was in. This is truly Noob friendly and intended for someone just beginning in the Android community, because of this it is painfully detailed. Hopefully, you will allow it to stay up.
The purpose of this thread is to address several issues I ran into while attempting to unlock my bootloader as well as address questions I personally had that I couldn't find answers to by using myself as the test dummy. Those items are as follow:
1) ADB was not functioning properly with Windows 10.
2) My Windows 10 laptop could recognize my OneTouch 7t in ADB devices but could not recognize it in Fastboot. Windows 10 wouldn't let me install the drivers that come pre-loaded on the OnePlus 7t.
3) After Unlocking the bootloader I hit a "checking info" loop with Google.
4) Does unlocking a bootloader on the OnePlus 7t cause any Safety Net Issues?
5) What does a SafetyNet failure result in?
6) Will every app work with an unlocked bootloader?
Solutions and answers:
1) This is going to be a detailed process but in the end, you'll have universal ADB and fix your windows issues:
If you decide to unlock the bootloader IT WILL WIPE EVERYTHING. This includes photos, apps, music, etc. So start by doing a backup:
-Settings>search "switch">OnePlus Switch>Backup & Restore> New Backup
-Copy that backup folder to your computer by plugging the phone into the computer> settings>search "USB">USB preferences>select file transfer>On your computer open up HD1905>internal shared storage>copy the "opbackup" folder to your computer (this will take a while)
Now to get Developer options:
-On your phone>settings>about phone>Tap build number until it says you are a developer
-Settings>system>developer options>turn on USB debugging
Getting ADB set up on your computer:
-Download and install SDK Platform-Tools for Windows: https://developer.android.com/studio/releases/platform-tools
-on Windows>Open up Command Prompt (run>cmd>enter)>Type sysdm.cpl> hit enter
-Go to the advanced tab in the window that pops up> environment variables>path>new>browse.
-Now find where you installed the SDK platform-tools and select the folder that says "platform-tools"
click ok>ok>ok
Testing ADB:
-Open a new Comand Prompt in Admin mode. To do this Open run type "cmd" and then hit Ctl+Shift+Enter and click ok to the pop-up
-Plug your phone into the computer
-In Command Prompt type "adb devices" and hit enter
-You should now see your phone ID
-Type "adb reboot bootloader" and hit enter
-Your phone will reboot into bootloader
-Type "fastboot devices" and hit enter
-If your ID does not show up go to step 2 without changing anything (ie. stay in Command Prompt with the phone plugged in at the bootloader menu)
2)-This step fixes the driver issue that likely causes problem #1.
Get the newest Android drivers:
-Download and install Android Studio: https://developer.android.com/studio
-Launch Android Studio
-Configure>SDK Manager>SDK Tools>Google USB Driver>Apply>Ok
-At the top, it will say SDK path I highly suggest you copy that or write it down you will need it soon.
-Click Finish and close Android Studio
Installed drivers for fastboot:
-Open any folder and then select "view" at the top of the window and check the box that says hidden files then close the window.
-windows key+x>device manager>right click on the phone with the orange exclamation point>update drivers>browse my computer>browse>go to the folder location>next>finish
If that doesn't work and you get "Windows was unable to install driver" error do the following:
-click search for updated drivers on windows update>a new window will come up> Update and restart your computer
-Once back on and updated>windows key+x>device manager>right click on the phone with the orange exclamation point>update drivers>browse my computer>let me pick from a list>Android Bootloader interface>next>once finished, close the window.
To Test if this fixed the issue:
open an Admin Command Prompt and type "fastboot devices" and hit enter, you should now see your phone's ID.
WARNING: IF YOU DO THE NEXT STEP YOUR PHONE WILL BE FULLY WIPED. ENSURE YOU MADE A BACKUP!!!
Now to unlock the bootloader:
-In Admin Command prompt type "fastboot oem unlock" and hit enter
-On your phone use the volume keys to select "unlock the bootloader" then use the power key to select it.
Congrats your bootloader is now unlocked. Now for the problems you may face once it's back on
3) If you hit the "checking info" Google loop follow these steps:
-Go to Settings> Battery> Battery Saver>Turn off when fully charged>Select OFF,
-Go Settings> Apps¬ifications>See All ## Apps>3 Dot menu>Reset app preferences> reset Apps,
-Go Settings> Apps¬ifications>See All ## Apps>3 Dot menu>Show System
-----Select Google play store >Storage & cache>Clear Storage
-----Press Back
-----Select Download manager> Storage & cache>Clear Storage
-----Press Back
-----Select Google play services> Storage & cache>Clear Storage>Clear All Data
-Go to Settings >Accounts> Google Account name/ Names> 3 Dot Menu> Remove ALL Accounts
-Restart device
-Connect to Wifi
-Go to Settings >Accounts>Add Account>Google
4) Yes, unlocking your bootloader on the OnePlus 7t results in a "CTS Profile Match=false" failure in SafetyNet
5)From what I can tell this SafetyNet failure doesn't really cause too many issues but time will tell and I will update this accordingly.
6) I tested the known problem children ie. Google pay, PokemonGo, and Snapchat. All were good. The only exception I ran into was Netflix. It will not work with an unlocked bootloader. There may be ways to resolve this but I haven't tried them yet as this is all without Root. I will update this post when I find solutions.
Again I know that most of this can be found but it took me a decent amount of digging. More importantly, a lot of the stuff was implied knowledge that many of us already have but a newcomer wouldn't. Hopefully, this is useful to the new and old alike feel free to ask questions below as I will be continuing to test stuff further.
Saved
Update:
How to fix SafetyNet failure:
Get Root
-Follow this link: https://forum.xda-developers.com/oneplus-7t/how-to/magisk-auto-root-tool-oneplus-7t-pro-t4079355#post82221323
This is hands down the easiest root method I have ever seen for any device. HUGE shoutout to @daxiaamu and @mauronofrio for this!
Install Magisk Manager
On Your phone go to https://github.com/topjohnwu/Magisk/releases/
and download the latest version of Magisk Manager.
Allow unknown sources> install
Update Magisk
Once in Magisk Manager it will prompt you to install some updates for our phone. Install them and let it reboot.
Install Magisk Hide
Open Magisk>Three lines in top left corner>Downloads>MagiskHide Prop Config>download>install
Test
Once your phone has rebooted open Magisk>SafetyNet Check Status>Prosper!
Thank you to the Magisk team for making this hands down the easiest experience I have ever seen on Android and to @daxiaamu for making a truly one-click install that works flawlessly!
This should be pinned, but I have ctsProfile: false.
Is that expected?
lucfig said:
This should be pinned, but I have ctsProfile: false.
Is that expected?
Click to expand...
Click to collapse
If you have the bootloader unlocked, yes. Magisk won't be able to hide the lock/root status from SafetyNet once Google fully rolls out their updates to SafetyNet/Play Services.
https://twitter.com/topjohnwu/status/1251712525843918853
Signing ROMs with custom keys and relocking may be a possibility, but I haven't tested anything on the 7T, and I'm staying locked until official support ends since the days of passing SafetyNet with root/unlocked bootloaders appears to be over.
lucfig said:
This should be pinned, but I have ctsProfile: false.
Is that expected?
Click to expand...
Click to collapse
Thank you, it took a while to write was a little discouraged with the lack of response lol. To fix cts error:
Open Magisk>settings>turn off magisk hide
Magisk>Downloads>MagiskHide Props Config> Download and reboot
Magisk>Settings>Turn on MagiskHide
Test again should be good
C4sp3R911 said:
Thank you, it took a while to write was a little discouraged with the lack of response lol. To fix cts error:
Open Magisk>settings>turn off magisk hide
Magisk>Downloads>MagiskHide Props Config> Download and reboot
Magisk>Settings>Turn on MagiskHide
Test again should be good
Click to expand...
Click to collapse
Hope it gets more visibility, is the most detailed and easy to follow instructions.
I figured that out. Without riru or edxposed the Magisk hide works great.
otto888 said:
If you have the bootloader unlocked, yes. Magisk won't be able to hide the lock/root status from SafetyNet once Google fully rolls out their updates to SafetyNet/Play Services.
https://twitter.com/topjohnwu/status/1251712525843918853
Signing ROMs with custom keys and relocking may be a possibility, but I haven't tested anything on the 7T, and I'm staying locked until official support ends since the days of passing SafetyNet with root/unlocked bootloaders appears to be over.
Click to expand...
Click to collapse
We were able to fix it through MagiskHide. Both methods above worked.
Hey guys, I just received my OP7T today (upgrading from the 5T), and I see that there's no official TWRP yet. I've been looking around to see if it's worth it to root the phone already.
Is the rooting already stable enough, or should I wait a couple more months for full modded roms to come out? 'cause I really enjoy having the root features that some apps offer, but I also definitely need MagiskHide to work so my bank app won't have any issues with the unlocked bootloader.
If the guide above is up to date and working like C4sp3R911 posted, I'd be down to try it today.
Could I still use the the following command if OEM Unlocking is grayed out in Settings? Thanks.
"fastboot flashing unlock"
or
"fastboot OEM unlock"
What?... You need to learn a bit more before messing with bootloader unlocking, fastboot flashing unlock is not a command and will do nothing... Check yourself before you wreck yourself as the saying goes,
If it's greyed out doesn't that mean the BL is already unlocked?
C4sp3R911 said:
***Warning: I am not responsible for bricked or broken devices, warranties, computers, etc. This is your phone and your free will to follow the below steps and you bare the full burden of any consequences.***
A note for the Moderators: I am aware that the information I am about to provide exists outside of this thread. The purpose of this is not for redundancy or to clutter the forum. I am making this thread because I had to go to SEVERAL different sources to find these solutions and pull pieces from each. Hopefully, this is comprehensive enough to help someone who may have been in the same boat I was in. This is truly Noob friendly and intended for someone just beginning in the Android community, because of this it is painfully detailed. Hopefully, you will allow it to stay up.
The purpose of this thread is to address several issues I ran into while attempting to unlock my bootloader as well as address questions I personally had that I couldn't find answers to by using myself as the test dummy. Those items are as follow:
1) ADB was not functioning properly with Windows 10.
2) My Windows 10 laptop could recognize my OneTouch 7t in ADB devices but could not recognize it in Fastboot. Windows 10 wouldn't let me install the drivers that come pre-loaded on the OnePlus 7t.
3) After Unlocking the bootloader I hit a "checking info" loop with Google.
4) Does unlocking a bootloader on the OnePlus 7t cause any Safety Net Issues?
5) What does a SafetyNet failure result in?
6) Will every app work with an unlocked bootloader?
Solutions and answers:
1) This is going to be a detailed process but in the end, you'll have universal ADB and fix your windows issues:
If you decide to unlock the bootloader IT WILL WIPE EVERYTHING. This includes photos, apps, music, etc. So start by doing a backup:
-Settings>search "switch">OnePlus Switch>Backup & Restore> New Backup
-Copy that backup folder to your computer by plugging the phone into the computer> settings>search "USB">USB preferences>select file transfer>On your computer open up HD1905>internal shared storage>copy the "opbackup" folder to your computer (this will take a while)
Now to get Developer options:
-On your phone>settings>about phone>Tap build number until it says you are a developer
-Settings>system>developer options>turn on USB debugging
Getting ADB set up on your computer:
-Download and install SDK Platform-Tools for Windows: https://developer.android.com/studio/releases/platform-tools
-on Windows>Open up Command Prompt (run>cmd>enter)>Type sysdm.cpl> hit enter
-Go to the advanced tab in the window that pops up> environment variables>path>new>browse.
-Now find where you installed the SDK platform-tools and select the folder that says "platform-tools"
click ok>ok>ok
Testing ADB:
-Open a new Comand Prompt in Admin mode. To do this Open run type "cmd" and then hit Ctl+Shift+Enter and click ok to the pop-up
-Plug your phone into the computer
-In Command Prompt type "adb devices" and hit enter
-You should now see your phone ID
-Type "adb reboot bootloader" and hit enter
-Your phone will reboot into bootloader
-Type "fastboot devices" and hit enter
-If your ID does not show up go to step 2 without changing anything (ie. stay in Command Prompt with the phone plugged in at the bootloader menu)
2)-This step fixes the driver issue that likely causes problem #1.
Get the newest Android drivers:
-Download and install Android Studio: https://developer.android.com/studio
-Launch Android Studio
-Configure>SDK Manager>SDK Tools>Google USB Driver>Apply>Ok
-At the top, it will say SDK path I highly suggest you copy that or write it down you will need it soon.
-Click Finish and close Android Studio
Installed drivers for fastboot:
-Open any folder and then select "view" at the top of the window and check the box that says hidden files then close the window.
-windows key+x>device manager>right click on the phone with the orange exclamation point>update drivers>browse my computer>browse>go to the folder location>next>finish
If that doesn't work and you get "Windows was unable to install driver" error do the following:
-click search for updated drivers on windows update>a new window will come up> Update and restart your computer
-Once back on and updated>windows key+x>device manager>right click on the phone with the orange exclamation point>update drivers>browse my computer>let me pick from a list>Android Bootloader interface>next>once finished, close the window.
To Test if this fixed the issue:
open an Admin Command Prompt and type "fastboot devices" and hit enter, you should now see your phone's ID.
WARNING: IF YOU DO THE NEXT STEP YOUR PHONE WILL BE FULLY WIPED. ENSURE YOU MADE A BACKUP!!!
Now to unlock the bootloader:
-In Admin Command prompt type "fastboot oem unlock" and hit enter
-On your phone use the volume keys to select "unlock the bootloader" then use the power key to select it.
Congrats your bootloader is now unlocked. Now for the problems you may face once it's back on
3) If you hit the "checking info" Google loop follow these steps:
-Go to Settings> Battery> Battery Saver>Turn off when fully charged>Select OFF,
-Go Settings> Apps¬ifications>See All ## Apps>3 Dot menu>Reset app preferences> reset Apps,
-Go Settings> Apps¬ifications>See All ## Apps>3 Dot menu>Show System
-----Select Google play store >Storage & cache>Clear Storage
-----Press Back
-----Select Download manager> Storage & cache>Clear Storage
-----Press Back
-----Select Google play services> Storage & cache>Clear Storage>Clear All Data
-Go to Settings >Accounts> Google Account name/ Names> 3 Dot Menu> Remove ALL Accounts
-Restart device
-Connect to Wifi
-Go to Settings >Accounts>Add Account>Google
4) Yes, unlocking your bootloader on the OnePlus 7t results in a "CTS Profile Match=false" failure in SafetyNet
5)From what I can tell this SafetyNet failure doesn't really cause too many issues but time will tell and I will update this accordingly.
6) I tested the known problem children ie. Google pay, PokemonGo, and Snapchat. All were good. The only exception I ran into was Netflix. It will not work with an unlocked bootloader. There may be ways to resolve this but I haven't tried them yet as this is all without Root. I will update this post when I find solutions.
Again I know that most of this can be found but it took me a decent amount of digging. More importantly, a lot of the stuff was implied knowledge that many of us already have but a newcomer wouldn't. Hopefully, this is useful to the new and old alike feel free to ask questions below as I will be continuing to test stuff further.
Click to expand...
Click to collapse
Just bought the op7t pro and followed your guide step by step, but still fastboot devices does not show nothing to me
Tried in 2 different windows pc with same results, don't know how to do now
Having trouble getting adb setup on my computer. Specifically here:
-Now find where you installed the SDK platform-tools and select the folder that says "platform-tools"
click ok>ok>ok-
In "Environment Variables" popup, I select "path" in the top field, then click "new". The next popup is "New User Variable". Here, I've clicked "Browse Directory", as well as "Browse File", but each time I click platform-tools and click OK, the OK in the "New User Variable" popup is greyed out. I've tried even clicking on a subfolder to platform-tools, just to see if that 2nd OK would be active, but it isn't. Any help is much appreciated.
doncheadlesdriveway said:
Having trouble getting adb setup on my computer. Specifically here:
-Now find where you installed the SDK platform-tools and select the folder that says "platform-tools"
click ok>ok>ok-
In "Environment Variables" popup, I select "path" in the top field, then click "new". The next popup is "New User Variable". Here, I've clicked "Browse Directory", as well as "Browse File", but each time I click platform-tools and click OK, the OK in the "New User Variable" popup is greyed out. I've tried even clicking on a subfolder to platform-tools, just to see if that 2nd OK would be active, but it isn't. Any help is much appreciated.
Click to expand...
Click to collapse
Great. Thanks for the help.
[GUIDE] IMEI / Connection Repair on Asus Zenfone 2E ZE500CL Z00D
I am writing this guide because I recently recovered a bricked ZE500CL and after flashing around so many different files I lost my IMEI and connection abilities. After a little research and some thought I easily repaired my IMEI and restored my connection abilities. Just follow the steps below. I don't have this phone long and I am still learning so some of these steps might not be needed. Nevertheless it DOES work if you follow it properly.
What you will need:
1) Asus Flash Tool - https://drive.google.com/open?id=1n7tJr7lAlPnL8-nmK8f5kGmDHbRv5gxo
2) Asus Phone Drivers - https://drive.google.com/open?id=11XLRW5pEScYdBYwh0vDM-Wup9orGPWDf
3) Debug Service Firmware - https://drive.google.com/open?id=1ISofitM3yhYpu46JD0KWGLXybvtLQyAy
4) Intel Phone Tool - https://drive.google.com/open?id=1dQjjlHjWs8tDrfNU_ikgesKK2uKaTyXt
5) Intel Drivers - https://drive.google.com/open?id=1hE9j35VMOD5QGHjDy_aM2vVCs2PVOOm1
6) ADB / Fastboot Tools - https://drive.google.com/open?id=1nbAS8k4JMAXG8YH2qIFHpRjX60TTlYIt
7) IMEI Number - You should have this. If not generate one based off another ZenFone 2E Z00D's IMEI.
8) ZenFone Root Tool - https://drive.google.com/open?id=1NHf516Yex9KfsnufVNz0vkchJWCiMHo2
9) Root File Browser (ES File Explorer, Root Browser etc) - Get from the internet, place on your phone via MTP file transfer or push/install it in adb.
NOTE: If you choose the first way you will have to go into your debugging app in the applications. It will be the one with the magnifying glass and says Asus Log something on it. I no longer have the Service Firmware installed so I can't remember. You will find it though. Once you do go in and find the usb settings and just change modes and you will see the drivers install and device ASUS_Z00D or something similar should appear in device manager under devices. If it fails to load make sure you have the correct ASUS Drivers installed and if that doesn't work the last way is to select the ( ! )Driver and then manually install the USB MTP Device driver which will fix the issue.
10) Factory Folder Backup (This MIGHT not all be needed, still checking to make sure.. for now include it) - https://drive.google.com/open?id=1fvH0QdrzLFM34vsm2KNfQBU5fr8eSM14
First Step:
Download everything above and then install 6,2,5,4 (Install the drivers that come with Intel Tool before installing it. You should be prompted during installation) and then install 1.
Second Step:
Open Asus Flash Tool and make sure your phone is connected to the computer and you are in fastboot mode.
You can get there 2 ways. (1) Turn the phone off, hold Vol+, then push the power button, and when you feel it vibrate release the power button while holding Vol+. (2) Open command prompt and enter "adb reboot bootloader" (this is if you're adb is setup system wide, if not navigate to your SDK Tools folder and enter there).
Flash the Debug Service Firmware you downloaded. Check WIPE to wipe before flashing.
Once you see the phone boot up goto the next step.
Third Step:
Open Intel Phone Tool and follow this guide here to fix your IMEI! -
NOTE: You can skip the setprop commands he enters into adb shell in command prompt. This firmware already has the COM Port opened and USB Debugging enabled for you.
Fourth Step:
Now you will need to root your phone using the Root Tool I linked in the beginning (Do not worry about upgrading the SuperSU Binary.) Next you will need to install a root browser on your phone like ES File Browser, Root Browser etc. Something that allows access to root / hidden files. Navigate to /Factory and /Config and backup these two in their entirety to your MicroSD card or computer. Replace your factory with mine if it is empty and doesn't contain the files in the steps below. Now comes time to edit. Makes these changes to the files. (I am not 100% sure which all DO need to be made so I just modified most all of the values.)
These instructions are thanks to @BORETS24
I have changed them a tad as our handset differs from the one he wrote them for. I am still not entirely sure if everything needs to be copied/modified. Don't have a lot of spare time on this handset to figure out everything. I just know from testing this will get your phone functioning again.
Serial number, WI-MAC, BT-MAC repair instructions
(You will be replacing everything after step 5. Below explains what to edit.)
1. If you have an empty factory partition, use the archive, replace factory folder with archive version to root file system via file manager, ES File Explorer or others (root required and root browsing required of the application). Serial Number, WiFi MAC, BTMAC, colorID you may see on box from phone (or make up something for each value). .. you can generate the WiFi MAC based off these Unassigned? Assignments - 00:90:4C, 00:09:4C or just make one up based off a random Assignment from here - https://regauth.standards.ieee.org/standards-ra-web/pub/view.html#registries. For the Bluetooth - 22:22:AF or something you find on the previous site. You can check easier after you generate here - http://www.coffer.com/mac_find/. For color ID I left mine the same as what is in the factory.zip which is Silver.
2. Then open and edit factory/PhoneInfodisk/bt_addr.conf- this BT MAC, replace 00:00:00:00:00:00 numbers to your MAC.
3 Then open and edit factory/PhoneInfodisk/colorID- color code of your phone. For example silver is 6J.
4. Then open and edit factory/PhoneInfodisk/PhoneInfo_inf- 6F0000000 (yours will be 12 numbers) replace to your serial number, 1C002C... change to you BT-MAC, 00B72... change to your WiFi MAC, 6J change to your color code, RU... change to US,EU,CN,TW,RU (do not think this matters much). I changed mine to US I think.
5. Then open and edit factory/PhoneInfodisk/ssn- enter your serial number replacing 0000000. (12 numbers)
6. Then open and edit factory/wifi/mac.txt- enter your WiFi MAC replacing 00000.
Fifth Step:
Open Asus Flash Tools and flash desired build of RAW firmware over the Debug Service Firmware. I suggest the latest WW firmware which is ver .126. From here you can stay on this firmware after replacing the files below or surf around XDA and find out what customized ROMS are available for this phone. Personally I unlocked my Bootloader, flashed TWRP, flashed .126, flashed Resurrection Remix 5.8.4 ? on Nougat 7.1.1 and then flashed a SU. RR I wouldn't recommend as it is buggy and neither would I of MoKee as it is buggy as well. I am fixing the bugs in RR so it runs fine as I particularly like RR over others since it comes pre installed with a horde of features so you can customize your handset to your hearts desire.
1. Install a root File Browser and root your phone again.
2. Replace /config with your backed up /config.
3. Replace /factory with your backed up /factory.
4. Reboot.
Now check everything in settings and make sure it looks right. All should look A-OK except for serial #. I am still working on that and will edit this once I finish. Layout of our phone is different than the one I took files from. You might have to replace the file again if you flash certain custom ROM's. I flashed RR and didn't have to.
EDIT: After a few reboots I seem to lose my MAC's again and the serial (unknown) is replaced by Medfield1534DD97. Both WiFi and BlueTooth still work though. You just have the random default generated MAC's. I can live with that as long as it works. Though if anyone can shed some light on this issue or anything else I would be extremely grateful.
Enjoy Your Phone!
-------------
For the Asus Zenfone 2E ZE500CL Z00D I will be uploading in the near future somewhere an organized package compiled of all recoveries, roms custom + stock firmware, root, bootload unlockers, tools, apps and guides all together so you can easily download and skip the time consuming research I had to endure. It is around 10GB. I am officially done learning this phone now. It has been a long 3 days and now it is time to ship it out to a buyer. =]
XDA: noidodroid