Related
INTRODUCING THE SAMSUNG GALAXY S3 UNIFIED TOOLKIT
SUPPORTED MODELS
INTERNATIONAL [GT-I9300] SUPPORT THREAD HERE
AUSTRALIAN MODEL GSM [GT-I9300T]
INTERNATIONAL [GT-I9305/GT-I9305N] SUPPORT THREAD HERE
AUSTRALIAN MODEL LTE [GT-I9305T]
C SPIRE MODEL LTE [SCH-L710]
AT&T US [SGH-I747] SUPPORT THREAD HERE
BELL, ROGERS, SASKTEL, TELUS [SGH-I747M] [SGH-I747M] USE AT&T SUPPORT THREAD
US CELLULAR MODEL LTE [SCH-R530] USE AT&T SUPPORT THREAD
METRO PCS MODEL LTE [SCH-R530M] USE AT&T SUPPORT THREAD
SPRINT US [SPH-L710] SUPPORT THREAD HERE
TMOBILE US [SGH-T999] SUPPORT THREAD HERE
MOBILICITY, VIDEOTRON, WIND [SGH-T999V] USE TMOBILE SUPPORT THREAD
VERIZON US [SCH-I535] SUPPORT THREAD HERE
CHINA ANYCALL CDMA MODEL [SCH-I939] USE GT-I9300 SUPPORT THREAD
Click to expand...
Click to collapse
The Unified Android Toolkit supports a multitude of Nexus and Samsung devices with more devices being added all the time. 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.3.4 [9TH JAN 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]
* 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
* 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: As the exe files are not Digitally Signed with a Microsoft Certificate they 'may' get picked up as potentially harmful by Antivirus Programs and deleted on first run. If this happens restore the file and exclude it from future scans to use it. This seems to happen mostly on AVG Free and Norton which is why I switched to BitDefender which is much better.
Credits: 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.
--------------------------------------------------------------
WHAT IS THE DIFFERENCE BETWEEN PUBLIC (FREE) AND PROFESSIONAL (DONATE) VERSIONS?
THE PUBLIC VERSION OF THE TOOLKIT INCLUDES EVERYTHING YOU COULD NEED TO MANIPULATE YOUR DEVICE. NOTHING IS RESTRICTED.
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 (USEFUL IF YOUR BUILD IS NOT LISTED).
AUTO REPLY LINKS FOR PAYPAL TO GET A CODE INSTANTLY CAN BE FOUND AT http://goo.gl/nyGqv
--------------------------------------------------------------
PLEASE READ THE *HELP* PAGE AT http://www.skipsoft.net/?page_id=1269 OR USE THE INFORMATION SECTION WITHIN THE TOOLKIT IF YOU HAVE ANY QUESTIONS. I HAVE TAKEN A LOT OF TIME TO WRITE IT AND SOMETHING ON THERE SHOULD ANSWER 99% OF PROBLEMS.
--------------------------------------------------------------
1. INSTALLING ADB/FASTBOOT DRIVERS
The first thing you need to do is to install the adb/fastboot drivers. These are needed so that you can unlock your bootloader, root your device and perform other adb/fastboot functions.
THE DRIVERS CAN BE INSTALLED DIRECTLY VIA THE TOOLKIT. OPTION 1 IN THE MAIN MENU.
If drivers are not installed or there is an exclamation mark next to the device:
Plug the device in to a usb cable directly connected to your motherboard.
In the Device Manager a new item, usually called Android 1.0 should pop up in the list.
Right click on the device item then left click on Update Driver Software. Select 'browse my computer' and then 'Let me pick from a list'.
If no adb interface driver appears in the list then untick 'Show compatible hardware' and find the Android or Samsung adb interface driver.
If you cannot find either of these click Have Disk, browse to the Toolkit install folder, drivers folder, click on android_winusb.inf and click Open.
Click OK and select Google ADB Interface.
Make sure you have USB debugging enabled in settings, developer options. In Android 4.2.2 or later you have to enable the developer options screen by going to settings, About on your device and click on Build number at the bottom 7 times until it says You are now a developer. If you have already enabled usb debugging then unplug/replug the usb cable.
On Android 4.2.2 or later when you replug the usb cable after enabling usb debugging for the first time you will get a popup asking you to authenticate your pc. Tick 'Always allow' then click 'ok'.
--------------------------------------------------------------
2. USING SKIPSOFT UNIFIED ANDROID TOOLKIT
When starting the Toolkit you will first be asked which device you want to work with. Working folders will be created and the device files downloaded. You will then be taken to the Model/Build selection screen where you can do a number of things (other than select your model/build): Type '00' to enter your activation code and enable pro features, 'i' will take you to the Information and Help Section, 'a' will give you information on how to add support for a new build.
Supported builds are listed in the Model/Build selection screen and typing the associated number (i.e. 11) will download needed boot and recovery files (stock and custom recovery) then check for and download the latest superuser files available and custom recovery (pro versions only), verify all the files and start the Main Menu. You can now use all the functions and tools the Android Toolkit offers. Pro users can select the "any build" option to root any build (useful if your build is not listed).
--------------------------------------------------------------
USEFUL INFORMATION
How to get into Recovery Mode
1. Unplug the USB cable.
2. Shut down the phone.
3. Hold down the 'HOME' + 'VOLUME UP' buttons and press the 'POWER' button for about 5 seconds to enter Recovery Mode.
How to get into Download Mode (For Odin)
1. Unplug the USB cable.
2. Shut down the phone.
3. Hold down the 'HOME' + 'VOLUME DOWN' buttons and press the 'POWER' button for about 2 seconds until a WARNING! Screen appears. Press the 'VOLUME UP' button to enter Download Mode.
--------------------------------------------------------------
*DISCLAIMER*
I take no responsibility for any fault or damage caused by any procedures within this guide. No warranties of any kind are given.
**FAQ**
Q. 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). If you have a GT-I9300 GSM Model then you can do this from the Toolkit but if you have an LTE device then it isn't soo easy to do. If you have an LTE device you should go to *THIS* thread by lyriquidperfection and follow the information to save your IMEI/NV Data so that you are covered if anything should happen.
----------------------------------------------------------------------------
Q. Is there currently no way to root the Samsung Galaxy S3 without voiding the warranty?
All methods of rooting will void your warranty in some way as you will have superuser files on your phone that arent supposed to be there. There is a method of rooting your phone without increasing the flash counter which involves flashing a complete rom with root files already added but if anything happens and you need to send it back under warranty you will need to flash a 'proper' Stock Rom back before returning it or your warranty will be void. Flashing a custom kernel or recovery to root will increase the flash counter and also void any warranty. There is currently no method of resetting the flash counter on Snapdragon models but im pretty sure there will be some support for it soon. If you dont want to risk it or you aren't sure then you shouldnt really be flashing your phone and should just leave it alone. Its your choice .
----------------------------------------------------------------------------
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.
*reserved if needed*
Wow! Even the tech challenged girlfriend should be able to use this. No time to test but will be back.
Faaaaantastic! I'll be getting my phone this afternoon so should be able to report back tonight.
Worked Great on My Rogers Samsung Galaxy S3 , thank you so much
Worked great on my Rogers. Finally decided to root
trublu said:
Wow! Even the tech challenged girlfriend should be able to use this. No time to test but will be back.
Click to expand...
Click to collapse
Jirv311 said:
Faaaaantastic! I'll be getting my phone this afternoon so should be able to report back tonight.
Click to expand...
Click to collapse
Please do report back as I want to know if anything doesnt work as expected.
Mark.
I selected all in one for Rogers but it looks like it never installed CWM app touch.
Awesome, I'll be trying this out when I get home from work tonight!
Wow nice job!! gonna check this out after work!!
Nice, but didn't work on my AT&T. Odin got to RESET and rebooted phone, but did not get to PASS. Closing Odin by X, returned to toolkit, but could not get ACK, install su or set root.
Dx9 said:
I selected all in one for Rogers but it looks like it never installed CWM app touch.
Click to expand...
Click to collapse
Yeah that happened with me too, stock CWM is fine for me ahha
---------- Post added at 12:23 PM ---------- Previous post was at 12:22 PM ----------
alkiter said:
Nice, but didn't work on my AT&T. Odin got to RESET and rebooted phone, but did not get to PASS. Closing Odin by X, returned to toolkit, but could not get ACK, install su or set root.
Click to expand...
Click to collapse
Mine took about 3-5 minutes for it to stay PASS and rebooted before pass.
I ran the #3 root option and everything worked fine. i have att version. I'm making a nandroid right now not issues.
When Im tried this method:
http://forum.xda-developers.com/showthread.php?t=1725395
from noobnl, I had force close everywhere. I unrooted it with the steps provided in the same thread and reseted my phone. When it rebooted, screen rotation was the oposite of normal, the screen was always upside down. I could change it from Rogers, Do you think this method would do the same?
Thanks
xhead said:
Yeah that happened with me too, stock CWM is fine for me ahha
---------- Post added at 12:23 PM ---------- Previous post was at 12:22 PM ----------
Mine took about 3-5 minutes for it to stay PASS and rebooted before pass.
Click to expand...
Click to collapse
So how do I get the actual app? Should I redo it again and select a different option or is there a way to actually install from CWM? Thanks
Looks amazing!
Quick question does the root function trigger the modify counter?
Sent from my SAMSUNG-SGH-I747 using xda premium
skalatsky said:
Looks amazing!
Quick question does the root function trigger the modify counter?
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Yes
What root option do I have to go for? (in the root folder) I am with Rogers, i747m -
Does this trigger flash counter?
UPDATE:
The solution/walkthrough can be found here. It's also the fourth post on this thread.
Click to expand...
Click to collapse
Sorry if this seems like it is an obvious answer but I have once again gotten totally lost in trying to upgrade, mostly out of fear of bricking my phone. I went to Viper's site for the HTC One M8 and was just going to grab the latest version of the ViperOneM8 mod. I then quickly ran into something that stopped me in my tracks!
The 4.3.0 rom is based on HTC’s latest M8 Sense 6 Android 5.0.1 base and requires you to update your firmware to at least the 5.0.x (Lollipop) version! Else you will run into hiccups, like Wi-FI not working or No Boot and so on…
You need to do that on your own, because we can’t install the firmware for you with the rom installation.
Click to expand...
Click to collapse
Well I really appreciate them letting me know that but points off for not giving me a little insite on how I would do that. I have managed to get confused with all the terms and versions being thrown around, for example...
The 4.3.0 rom is based on HTC’s latest M8 Sense 6 Android 5.0.1 base
Click to expand...
Click to collapse
Ok, let's talk about BASES. When looking at my phones current info screen the ONLY thing I see that says anything with the word "base" in it is "Baseband Version". Now I know that's not what they are talking about because logic would suggest they are talking about something else just based on version numbers. So I'm guessing when they say "base" they are talking about 1 of 2 things.
The "Android Version" (which is currently KitKat v4.4.2)
The Software Version Of The Mod (which is currently ViperOneM8 1.8.0)
The current Android version out there is Marshmallow 6.0.1 and the current ViperOneM8 mod out there is 5.0.2. Because these are so close together (the Android version and the Mod version) It's making me a little uneasy about just going with my gut feeling.
So with Viper's warning, what steps do I take when trying to upgrade my HTC OneX M8? I have already backed up EVERYTHING on my phone and I would like to wipe it clean (both the internal storage and the added SD card) and start fresh with the latest Viper mod. Thanks for any help one might provide! The following are my current specs.
Software Info
Android Version: 4.4.2
HTC Sense Version: 6.0
Software Number: ViperOneM8 1.8.0
HTC SDK API Level: 6.17
Software Status: Official
PRI Version: 1.46_002
PRL Version: 15450
ERI Version: 5
Kernal Version: 3.4.0-g2e0a4a7 - [email protected] #1 - SMP PREEMPT
Baseband Version: 0.89.20.0321
Build Number: 1.54.401.5 CL325784 release-keys
Hardware Info
Model Number: HTC6525LVW
Hardware Version: 0004
Check the support ticket that you submitted at venomroms.com. I've given you directions there.
Run the latest Verizon RUU, flash TWRP 2.8.7.0, then flash ViperOneM8 4.3.0. Links given in the ticket.
Once I get through this all and it's done, I will post my findings. I will say right now that xunholyx helped me dodge a MASSIVE bullet by telling me to leave that the firmware I downloaded from "http://www.latintimes.com/android-501-lollipop-htc-one-m8-one-m7-downloads-available-now-manual-update-video-281741" was for GSM devices and I needed to have a version for CDMA! That made perfect sense and I wasn't even thinking about it at the time! So once again to xunholyx, hats off for saving me a brick!
Solution Steps
OK, so this turned out to be a long bumpy road. Everytime I go to upgrade my phone I have the same thought... First it's ahh no, phone is going to be DOA for about 2-3 days, and second I think "Why is there not a single page (that stays up to date) with an easy to follow tutorial on how to do this whole process??". Don't get me wrong, we would be nowhere without XDA but usually (due to lack of staying up to date) on the site I always feel like it's way to cluttered and complicated to find the "right" path.
Luckily I found a few people along the way to help me out. The Viper team over at http://venomroms.com/tickets were really great in keeping me pointed back on the right track. With their help and a LOT of reading on the web once again I managed to come out of the dark with an upgraded phone. Here are the steps that I came up with.
Note: Theses instructions are all based on using Windows, if someone wants to add to this thread with Mac instructions be my guest to copy paste all this and change content to suit Mac purposes.
Note: My phone is both *UNLOCKED* and S-OFF. If your phone does not show this in the bootloader screen at the top then the following might not work.
Note: When I say type 'this text'. Don't type the quotes unless they are bolded. It's VERY rare that they are needed! This is what it 'looks like' when the quotes are bolded as well.
Setup your phone for use with ADB/FastBoot
- Go into Settings, About, Software Information, More.
- Tap Build Number SEVEN times to enable developer mode.
- Go back to Settings, Developer options.
- Make sure Developer options is turned on at the top.
- Scroll down to Debugging area and make sure USB debugging is enabled (checked).
- Go back to Settings, Power and IF (depending on what OS you are in) you have a setting for fastboot, just uncheck it so you can get into the bootloader a little easier.
- At this point you should have your phone with USB debugging turned on so you should be set!
Download the latest Android Platform Tools:
- You can find the SDK here if you want to go through the long process (takes forever!) of getting the new tools OR for speedy results you can download a package that is a 100% replica of just the "platform-tools" directory that you need out of the SDK located here.
- Extract these tools into any directory (for example c:\tools\) and from this point on they will be referred to as "the tools directory".
Get the command window ready to do work:
- While in the tools directory, hold shift and right click in some EMPTY area within that folder. You should now see a sub menu option that says "Open command window here". Click it and get that command window open.
- Now if you have not already, connect your phone.
- In the command window type 'adb kill-server'. This is to ensure your device list will be clean and you only see your phone connected.
- Type 'adb devices'. To get a connection to your phone. You should see something like this...
C:\tools>adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
FA45WSF03873 device
- If you see that last line showing you your device and says "device" next to it, everything is great and you can continue. If not, if it says 'disconnected' or something similar then you need to work on getting that fixed before you can go any further.
Download and flash the L hboot (version: 3.19.0.0000):
- Go here and download the vzwm8Lhboot.zip file.
- Rename the zip to '0P6BIMG.zip'.
- Put zip on root of sd card (aka external memory).
- Reboot phone to bootloader (power off, then hold VOL DOWN and POWER)
- In bootloader, "Do you want to start the update?" Press VOL UP (for yes)
- Press POWER button for reboot.
- Wait for phone to boot back up to OS and use PC to browse SD card.
- Remove (delete) the 0P6BIMG.zip file from the sd card.
Update TWRP to latest stable (version: 2.8.7.0):
- Go here and grab TWRP and save it to the tools directory. Side note, I noticed the URL says GSM and with Verizon you should be using CDMA. But the links I followed on their page said "All Variants" so I guess there URL is just named weird because it works perfectly fine for me.
- Under Download Links, click on the Primary (Recommended) link and grab a copy of TWRP (twrp-2.8.7.0-m8.img).
- Save that file to the tools directory and rename it to 'twrp.img'.
- Now we need to get the phone to boot up to the bootloader screen. There are a few different ways to do this but the easiest way that people usually don't get confused is the following... Power off your phone. Once off hold down the VOL DOWN key, and then ALSO hold down the POWER button UNTIL you see a white screen with a bunch of green text at the top and three little androids skateboarding at the bottom.
- Navigation is easy while in the bootloader screen. VOL UP moves you up in the list and VOL DOWN moves you down. Pressing (not holding) POWER will select the option you are on.
- Make sure the selection is on 'FASTBOOT' and press POWER to select it.
- Over on the PC in the command window (where you should still be in the tools directory) type 'fastboot flash recovery twrp.img'.
- You should get a success message.
Update the phones firmware:
- Go here and grab the 'VZWm8LfirmwareTWRP.zip' file. This will upgrade some very important things.
- Save this file to the tools directory.
- In the command window type 'fastboot oem rebootRUU'. The phone should change to the silver HTC logo screen.
- In the command window type 'fastboot flash zip VZWm8LfirmwareTWRP.zip'. This will start a long process that DOES NOT NEED TO BE INTERRUPTED!!! Go get a pizza or something just leave the phone alone!
- After about a minute or two when it finishes in the command window type 'fastboot reboot-bootloader'. This will get you back to the bootloader screen so you can confirm the new versions.
Android 5.0.1
CID-VZW__001
HBOOT-3.19.0.0000
RADIO-1.12.20.1211
OpenDSP-v47.2.2-00564-M8974_FO.1024
OS-4.17.605.5
eMMC-boot 2048MB
Feb 3 2015,21:50:28.0
- Get back to the menu on the phone and select the 'REBOOT' option then press POWER. The phone will boot back the the Android OS.
Install the new Viper ROM (version: 4.3.0):
- Now grab a copy of the Viper ROM from here. Click on "Previous roms" and choose "ViperOneM8 4.3.0".
- Save this to your SD card as the default name 'ViperOneM8_4.3.0.zip'.
- Boot into recovery by powering down the phone, holding VOL DOWN and POWER until you get to the bootloader screen and then choosing 'RECOVERY'. This should get you into TWRP.
- While in TWRP choose install and choose the Viper ROM you just added to your SD card. The location is at '/external_sd/'.
- This should take you through the Viper setup. Just follow the steps on screen at this point!
References:
- Venom ROMs - A great team of guys with great ROMs.
- Venom Helpdesk Ticket System - A place to submit tickets to get help when trying to install Venom ROMs.
- XDA Thread By dottat - A place I found my L hboot update and learned a few things.
- XDA Thread By Tigerstown - A place I found my new firmware to upgrade to Android 5.0.1, hboot, radio, etc.
- VenomOneM8 ROM - This is where I was able to download my VenomOneM8 4.6.0 ROM that I use for my HTC One (M8).
arvo.bowen said:
"Why is there not a single page (that stays up to date) with an easy to follow tutorial on how to do this whole process??". Don't get me wrong, we would be nowhere without XDA but usually (due to lack of staying up to date) on the site I always feel like it's way to cluttered and complicated to find the "right" path.
Click to expand...
Click to collapse
Simply put, its harder than you would think to keep such guides updated and organized. And what is the "right path" is not the same for all versions. The specific files needed are different for each version; and are also changing over time due to version updates. Combine this with the fact that this device is going on 2 years old, and a lot of contributors have moved onto other devices.
Your frustration is understandable. The information is all there, but it is daunting to sift through it and understand it properly. While forum traffic for this device is not what it used to be; there arestill some great "helpers" (xunholyx is one of those) here to assist in guiding your way.
---------- Post added at 10:36 AM ---------- Previous post was at 10:31 AM ----------
arvo.bowen said:
[*]Update TWRP to latest stable (version: 2.8.7.0):
- Go here and grab TWRP and save it to the tools directory. Side note, I noticed the URL says GSM and with Verizon you should be using CDMA. But the links I followed on their page said "All Variants" so I guess there URL is just named weird because it works perfectly fine for me.
Click to expand...
Click to collapse
Much earlier on, there used to be different TWRP versions depending on GSM vs. CDMA. And in fact, flashing the wrong TWRP led to some bricks (due to partition differences between GSM and CDMA versions). But some time ago, the TWRP folks figured out how to "unify" the TWRP versions so the one now marked "all variants" works on both GSM and CDMA variants.
This is a low-level backup comes from an ARM64 test machine made by Microsoft, codenamed Hapanero.
For the Lumia 950XL, since it also uses the Qualcomm Snapdragon MSM8994 SoC, the bottom layer can still operate but the display driver are not the same. Running on the Luumia950XL will damage the Amoled driver IC.
For the RX-130, please check the HW Build number of the model, the sticker is on the back of your device. Only EB2.X can be use this file, EB1.0 can't flash those file for the moment, and will causes an infinite boot loop. Before flashing, be sure to back up the original low-level 0-3 partition (DPP, MODEM_FSG, MODEM_FS1, MODEM_FS2) with Winhex. You need to restore the baseband after flash back to the ARM32.
After the flashing is completed, please restart your device. Please notice that the bottom layer does not have start-up vibration.
If you need to enter the Mass Storage mode, download the provided file into the SD card and extract the files in it to the root directory of the SD card. After the SD card is inserted into the device and the device is started, the system will automatically enter the menu.
After testing, due to the particularity of RX-130, it has no bricks at all, expect flash the android bootloader (how to unbrick the device in 9008 mode will public later).
Download link: (with Windows10 Mobile with build 14822 in ARM64)
HTML:
Bootloader backup image: https://pan.baidu.com/s/1d6UktLuIYuPk2qeq2eL3QA
PASSWORD: ylcg
Full system backup image(with certificate provided by imbushuo): https://pan.baidu.com/s/1EQ7OC9h3xSvVT8WzvUzdyA
PASSWORD: 96gk
SD card boot file(ARM64): https://pan.baidu.com/s/17DqccVMqJmLgAtMnlcXjrw
PASSWORD：kgo8
Thanks to imbushuo, JerryYin and other people make contribute to this project.
The ARM64 UEFI was originally uploaded by windowsbuildcollect.
备份最初由百度windowsbuildcollect吧发布
RX-130 Product Code: 059W1B4 , 059W1B6
Baidu
Very Nice :good:
But cannot use Baidu, please upload files on English site, Mega ect.
jbdxbl said:
(how to unbrick the device in 9008 mode will public later).
Click to expand...
Click to collapse
I.m waiting patiently, to see if i can unbrick lumia640 xl DS.
MazeAlpha6gb said:
Very Nice :good:
But cannot use Baidu, please upload files on English site, Mega ect.
Click to expand...
Click to collapse
https://drive.google.com/drive/folders/1bMG3d5mdfa_kLCT5KTbr5YxLmrxvEkKB
Teclast M40 Pro DiscoveriesVarious helpful points of knowledge to unlock your bootloader, to root, and use your tablet.
Problem: Where can I obtain the official firmware?
Solution: Teclast Website
Usage: type M1A3 in search
Problem How can I unpack "pac" files?
Solution: Build C utility divinebird / pacextractor
Solution: Download pre built Linux executable pacextractor.zip
Usage: >./pacextractor Firmware.pac
Bash:
git clone https://github.com/divinebird/pacextractor
cd pacextractor
make
Problem: I need tools to flash my device
Solution: Download the latest SPD Upgrade Flash Tool SPD_Upgrade_Tool
Problem: msvcr100.dll missing error in Windows whilst running SPD (Factory/Research/Upgrade) Tools
Solution: Download and install 2010 Visual C++ Distribution
Problem: I want to unlock my bootloader. (Window and Linux kit)
Solution: Download TeclastM40Pro_Unisoc_UnlockTools.zip
Usage: Read readme file.
Problem: How can I remove the dm_verify warning on boot up after unlocking the bootloader?
Untested Solution: digitally sign the vbmeta partition and write it back. See [Tutorial] How to create a custom signed vbmeta.img
Problem: I want to root my device.
Solution: Modify boot.img with Magisk, then sign.
Usage: Upload to your device's download directory, the current boot.img read from your device, or from the same version firmware. Then install Magisk app from here. Use Magisk to patch the boot.img. Sign the partition. Then flash back the signed magisk version of boot.img to "boot_a" partition. Guide to flashing single partition at Hovatek Website
Problem: I need to emergency flash my device?
Solution: Currently only from Windows, use SPD Upgrade Tools to reflash firmware.
Usage: From the tablet powered off, or if boot looping. Hold down the power-button and volume-down for five seconds, release the power-button, and keep the volume-down button still held for another five seconds, then release or release if the detected earlier. Windows and SPD tools should then detect your device to flash.
Problem: I want to improve my Telcast M40 Pro
Solution: List of suggested apps below;
FDroid App Store F-Droid Website
Aurora > via FDroid. App store allowing the direct download from Google Playstore, without your own account.
Lawnchair > via FDroid. Fast open source sophisticated launcher.
AdAway > via FDroid. Removes adverts whilst using apps.
TrackerControl > via FDroid. Manages apps access to internet, and blocks spyware and trackers.
.
Problem: I want root mode without the effort of hacking a rom partition.
Solution: For those with World version Teclast M40 Pro device, here is a signed rooted boot partition I created. Read the readme file inside the zip. You will require an unlocked device, windows setup with USB drivers for Teclast, the complete firmware from Teclast website, and SPD Update Tools installed. If you're successful, then on rooting you will need to install Magisk app to get root active. Magisk will reboot once to finalise.
Download : TeclastM40Pro_ROW__v1p0_signedboot_magiskrooted.zip
Download : TeclastM40Pro_ROW__v1p2_signedboot_magiskrooted.zip
SPD Upgrade Tools is closing while trying to flash stock firmware, both with M40 Pro locked and unlocked bootloader. What should i do?
laurorual said:
SPD Upgrade Tools is closing while trying to flash stock firmware, both with M40 Pro locked and unlocked bootloader. What should i do?
Click to expand...
Click to collapse
Sorry for replying late. I got no indication of the response. To the problem, I can only suggest getting a different version of SPD or m aking sure your computer system is properly updated. I hope you've already solved the issue!
Maybe you're experiencing, "Problem: msvcr100.dll missing error in Windows whilst running SPD (Factory/Research/Upgrade) Tools" See above for solution.
I've noticed a new ROM for world edition, "M40 Pro(M1A3)_Android 11.0_ROW V1.02_20220525", but not getting any system update options for OTA. People flashing their systems may want the latest firmware!
Thanks to your Magisk file I was able to root my tablet, but when updating to the latest version it goes into bootloop, I have tried updating the original firmware image again, but it also goes into bootloop.
Is there any way to install Magisk modules?
Thanks for your post, it helped me a lot to unlock my tablet.
Edit: My version is the M1A1 firmware V1.03_20210804
Edit 2: Finally, when updating my tablet with the root file that is in the post, it did not allow me to install any Magisk module, the solution is to download version 24.3, and update automatically, without changing to a higher version of Magisk
Glad you worked it out Miny !!! Sorry the warning emails for new posts have been going to a gmail account I no longer use.
Also your hardware maybe different and require it's own unique firmware and boot images. It seems the cracking in similar though.
Some questions:
Do I need to unlock my bootloader in order to be able to get root with magisk?
The tools for unlocking the bootloader uses
Code:
fastboot flashing unlock_bootloader
. My version of fastboot (33.0.3p1-android-tools) doesn't have that command. The included one (0.0.0-09219) does, but I wan't to be careful about running softwar from untrusted sources. Where is that version of fastboot from?
Does any of the steps necessary to get root access delete my data?
Hi there.
I have a m40pro (M1A1) running android 11, do you know if I can install firmware Z3A1 to get android 12? Or will be bricked?
Thanks in advance
rubsbcn said:
I have a m40pro (M1A1) running android 11, do you know if I can install firmware Z3A1 to get android 12? Or will be bricked? Thanks in advance
Click to expand...
Click to collapse
To tell you the truth, not sure. Most SoC are impossible or near impossible to brick. They usually allow for an injection or have a read only boot section. Other words you could test. Also research difference in hardware between models, and that may indlicate if something may not work. The kernel/drivers are the improtant aspect.
jorkusjorkus said:
Some questions:
Do I need to unlock my bootloader in order to be able to get root with magisk?
The tools for unlocking the bootloader uses
Code:
fastboot flashing unlock_bootloader
. My version of fastboot (33.0.3p1-android-tools) doesn't have that command. The included one (0.0.0-09219) does, but I wan't to be careful about running softwar from untrusted sources. Where is that version of fastboot from?
Does any of the steps necessary to get root access delete my data?
Click to expand...
Click to collapse
What OS are you using? Google is constantly changing Android Studio and the added modules. Then others may build with options removed. Personally I use Archlinux and load up standalone android-tools from the community repository. Currently v33.0.3-3
Try fastboot --help
Your version may have
Code:
fastboot flashing unlock_critical
minyfriki said:
Thanks to your Magisk file I was able to root my tablet, but when updating to the latest version it goes into bootloop, I have tried updating the original firmware image again, but it also goes into bootloop.
Click to expand...
Click to collapse
What I found works, is when using SPD Research Tool, load up the firmware.pac and then go into settings and click "Select All Files" and again to unselect, which leaves the default required items.
Then manually change BOOT to the Magisk img. Then click on all VBMETA types, and UBOOT_LOADER (may not be required though). Then flash.
You should get bootable tablet (no looping). Warning: UserData partition is written over.
I'll share my Magisk image for v1.2
e8hffff said:
What OS are you using? Google is constantly changing Android Studio and the added modules. Then others may build with options removed. Personally I use Archlinux and load up standalone android-tools from the community repository. Currently v33.0.3-3
Try fastboot --help
Your version may have
Code:
fastboot flashing unlock_critical
Click to expand...
Click to collapse
I'm using the same version as you on the same OS. After some research it seems like unlock_bootloader was removed in this commit from 2018. From what I can tell, unlock_critical does something else (unlock_bootloader runs
Code:
fb_queue_download("unlock_message", data, sz); fb_queue_command("flashing unlock_bootloader", "unlocking bootloader");
while unlock_critical runs
Code:
do_oem_command("flashing", "unlock_critical" and doesn't take the signature argument);
)
I'll see if I can compile the older version with the needed command.
What about my other questions?
Issue: Android not starting. I had the infinite restart when plugged in the usb. I tried to reload the installation package (succeeded), but didn't fixed the issue. Battery was not charging yet. When I started the Teclast M40 pro, the logo showed up, but the tablet turned off again.
Solution: I have disassembled the cover, unplugged the 5 pin plug from the battery for half hour and plugged again. When I tried to turn it on, everything was fine.
dougcwb said:
Solution: I have disassembled the cover, unplugged the 5 pin plug from the battery for half hour and plugged again. When I tried to turn it on, everything was fine.
Click to expand...
Click to collapse
Wow that's weird Doug. Remember this, if you don't already know, that you can do a cold start by holding down the power button for over 10 seconds, on most devices.
I guess you're running now on rooted tablet !!!
e8hffff said:
Wow that's weird Doug. Remember this, if you don't already know, that you can do a cold start by holding down the power button for over 10 seconds, on most devices.
I guess you're running now on rooted tablet !!!
Click to expand...
Click to collapse
I did the installation package process that the Teclast sent me. The last thing they told me to do was keep trying to install the package (wft?). Well, I just open the tablet, unplugged the battery for a while and after that it worked.
Maybe this resolved 2 things:
1-the battery was not properly connected in the first place, so when I plugged the 5 pin to the board it connected as it should.
2- Maybe there is a "memory" in the board attached to the battery that was bricked (or something like that) when I pulled off the plug, this memory was reseted.
BTW, when the tablet came to life again, the battery was at 87%.
WP17 is a rugged phone with Infrared Night Vision Camera, Helio G95 8GB+128GB 6.78“FHD+ 90Hz 64MP Triple Camera+16MP Selfie 8300mAh Android 11 Global Version.
{
"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"
}
Bought me a Oukitel WP17, but couldn't find much information about this phone.
So I'm going to post info here for everyone to see and participate in how to flash, root and update the phone.
Update:
Using the MTK-bypass Small utility to disable bootrom protection(sla and daa).
According to this Exploit, this MT6785 Oukitel WP17 is fully unlocked, and should be flashable:
Windows10:
[2022-10-13 02:45:23.376773] Found device = 0e8d:0003
[2022-10-13 02:45:23.766358] Device hw code: 0x813
[2022-10-13 02:45:23.776413] Device hw sub code: 0x8a00
[2022-10-13 02:45:23.786386] Device hw version: 0xca00
[2022-10-13 02:45:23.796588] Device sw version: 0x0
[2022-10-13 02:45:23.806536] Device secure boot: False
[2022-10-13 02:45:23.816739] Device serial link authorization: False
[2022-10-13 02:45:23.816739] Device download agent authorization: False
[2022-10-13 02:45:23.836660] Disabling watchdog timer
[2022-10-13 02:45:23.846734] Insecure device, sending payload using send_da
[2022-10-13 02:45:23.896695] Found send_dword, dumping bootrom to bootrom_813.bin
Linux:
[2022-10-13 09:15:03.350097] Found port = /dev/ttyACM0
[2022-10-13 09:15:03.423994] Device hw code: 0x813
[2022-10-13 09:15:03.425119] Device hw sub code: 0x8a00
[2022-10-13 09:15:03.425523] Device hw version: 0xca00
[2022-10-13 09:15:03.425902] Device sw version: 0x0
[2022-10-13 09:15:03.426248] Device secure boot: False
[2022-10-13 09:15:03.426595] Device serial link authorization: False
[2022-10-13 09:15:03.426923] Device download agent authorization: False
However, flashing this phone in any Sp flash tool, is ending up in:
ERROR : STATUS_SEC_PUBK_AUTH_MISMATCH_N (0xC002001B)
The PUBK_AUTH part of this error message, is the Authorization for flashing Signed/verified image files. In the Oukitel WP17 firmware folder, downloaded from Oukitel Downlod Center, are their only certain files marked as verified.img, and now after testing in Sp flash tool, loading ALL non-verified files, you can flash these files to the phone without problems.
.
Stock Oukitel Android 11 recovery
Let's fix this phoneDownload these files:Oukitel WP17 firmware: ASW2100YJ_2201_T2046
Python 6.3.1
Mediatek VCOM, CDC, USB Serial & Smartwatch Drivers
UsbDk_Brom-mode
MTKClient
Flash_Tool_v5.2028
Computer with internet
But before we can start, we need to format the phone, to delete all old configurations and settings.
1. Start by extracting the firmware file to your desktop. Now open up the MTKClient zip file and drag all files to your firmware folder.
2. Now you Install all needed drivers: Mediatek VCOM, CDC, USB / UsbDk_Brom-mode.
3. Extract the Flash_Tool to your desktop and open the flash_tool.exe.
ONLY check the UNverified files. We will flash the verified files later. Click on the Download button when you're done. Take your dead phone and connect it to the computer with the USB cable. Hold down Volume+ Volume- and power-button together, hold the buttons until the flashing start.
Once you have flashed the UN-verified files to your phone, we start the process of flashing the verified files.
4. Now we need access to the verified files. open a prompt in the firmware.
To do that, go to the start menu and type CMD.
4. Right-click and copy the address and paste it in the prompt window.
5. Now we have to configure MTKClient to be able to communicate with the phone.
Past in these commands one at a time in to the promt window.
Code:
python setup.py install
pip3 install -r requirements.txt
6. And now finally after you have set up the environment in python.
The flashing of the verified files to you phone can begin. copy and paste in the hole commands.
Code:
python mtk w md1img,spmfw,scp1,scp2,sspm_1,sspm_2,cam_vpu1,cam_vpu2,cam_vpu3,gz1,gz2,lk,lk2,logo,dtbo,tee1,tee2 md1img-verified.img,spmfw-verified.img,scp-verified.img,scp-verified.img,sspm-verified.img,sspm-verified.img,cam_vpu1-verified.img,cam_vpu2-verified.img,cam_vpu3-verified.img,gz-verified.img,gz-verified.img,lk-verified.img,lk-verified.img,logo-verified.bin,dtbo-verified.img,tee-verified.img,tee-verified.img
Press Enter,
On the phone: Hold down Volume+ Volume- and power-button together, hold the buttons until the flashing start. Sit back and wait
.
Your phone will end up like this after boot.
Done ....
Now Update your phone by Android update service by going in to 'Settings / System and update phone.
.
-- IMEI Restore --
After formatting the phone. I use ModemMETA tool to restore my IMEI.
Select the “Smart Phone” option from “Platform Type” section. Same as , select “USB” option from “PORT” section.
Press the Connect button in Modem METAtool. Hold down the Volume+ Volume- and power buttons at the same time while plugging in the USB cable. Meta tool will detect the device and it will start to load Boot file, karnel port etc. You can see all the process in “Connection Stages” section.
After completing the configuration process, you will be able to see “Connect” message at the bottom of the tool.
Now click on “Load DB”. “Load Database file from target”.
Now click on search box and select IMEI download option from drop down menu.
A new IMEI window will pop up in front of you.
Type in yor IMEI : and hit on “Write” button from same window.
ILLEGAL to Creating your own: 12345.12345.1234
if everything went well, it looks like this.
Update:
Easy rooting with Magisk ......
This will Unlock your bootloader!.
Unlocking your bootloader will send your phone in to a emergency state, and delete all personal data on the device. Back up everything that is important to you, before proceeding with rooting your phone -
Download and extract AA - Install Android to your desktop. Turn off your phone and enter 'fastboot mode'. Connect your phone to the computer and open AA - Install ROOT.dat.
Install Magisk25.
.
-- WARNING --Thinking of upgrading to Android 12 / Android 13 ?
The camera drivers found in the Android 11 version your phone was shipped with -Are NOT in the Android 11 version from the Oukitel Download Center !.You will brake your 64MP Camera if you flash GSI ore the version from Download Center .
Although I copied all the files required to restore the camera, which you can find below in a zip file -
Are the drivers in all other roms and GSI's to control the camera missing.
--FM drivers are located in kernel. Most other oem drivers are in vendor. And the definitions are in system
However, there is an easy fix for this, and that is to make a backup of your working phone firmware before you start installing other versions of Android, so that you can always restore your phone from this backup, with the correct drivers and get a fully functional phone again.
Dump/extract/backup your Oukitel WP17 firmware.It is ALWAYS a good practice to backup your firmware. Any phones sooner or later will have issues and since you don't have a copy to restore yor phone, you will spend money sending it in for repair which sometimes costs more than the phone is worth. There are many ways to make a copy of your phone's firmware. search on the internet or use this simple guide:
All the files you need can be found under this video
And to everyone who already broken their phone and is now looking for a way to restore their phone. Have I already ordered a new WP17 that I will create a firmware backup of, and make available for you and a manual for how to restore. I will keep you updated on that, but it takes a long time to get things shipped from China these days.
.
Android 12 / 13 on Oukitel WP17 -I created a small script that quickly installs Android 12 and 13 on your phone.
Get rid of the pesky red text on the screen.
Android 12 ...
Android 13 ...
To begin with, you need to decide which version of Android you want on your phone.
To help you on your way, I suggest you check out the link below. It's important that you choose the ARM64 AB version.
Generic System Image (GSI) list
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
In this example, let's say you want to install Spark OS Android 13.
Go to the download page and select the latest version.
1. Extract Android 13 from the downloaded file to your desktop.
2. Rename the file to GSI.img
3. Download and extract AA - Install Android to your desktop
4. Move the GSI.img file to the install folder.
Double-click on AA - Install Android.
Turn off your phone.
Press and hold Volume+ Power and Ptt button until you get to the bootloader menu.
Select Fastboot mode.
Connect your USB cable to your phone, Look at your phone, and press Volume+ button 2 times when prompted to start. That's all. Sit back and relax for a couple of minutes.
The installation script will install your chosen Android version and reboot the phone when everything is done. After boot install Magisk25.
.
Udate:
I have created a new lk.img file to remove the 'Orange State' Warning during boot of Android.
The file is added to the installation scripts.
Hi,
I've just intalled SparkOS (the same file you show in the tutorial) on my WP17.
The default camera has been replaced and now I can't use the triple camera or infrared.
I was wondering if you knew how to install/flash the NightVision Camera_Oukitel WP17.zip back onto the phone. Or maybe where to put the files?
Best regards, picipi.
PS: keep on the great work!
.
No. Sorry, not yet. The problem is the drivers for the camera. The Android version your phone is shipped with has these drivers pre-installed. As I wrote before, if you flash GSI or other versions of android, these drivers are not included, and you will have problems with your camera.
This forum is aimed primarily at those who have had problems with their phone and need help getting their phone to a working condition for calling and normal daily operation. However the NightVision Camera can be partly fixt by installing the default camera app.
It's important for EVERYONE with Android 11 stock firmware, to extract a copy of the firmware as a backup, before flashing other GSI roms. And share a link here on the forum, so others can restore their phones to.
There are many ways to do this. Find a method that suits you best:
pull Stock Android Firmware - Google Search
Perhaps this one for Windows users:
How to use SP Flash tool to backup Mediatek firmware
Update: I suggest you use Wwr tool + SP flash tool for the dump instead of SP Flash tool alone as you can proceed without first having the scatter file and using MTK Droid Tools (which is now outdated
www.hovatek.com
PS..
When you extract you firmware. DO NOT copy the USERDATA partition!, this partition can hold up to 20-40 gigabits of your old useless user data, of you using your phone on a daily bases.
.
--- BlissOS Android 13 and lightning fast ---
This rom has the bare minimum of needed apps, no bloatware and lightning fast.
highly recommended and fit's the Oukitel WP17 spec perfectly.
Download the rom here:
BlissOSv16.0-arm64-bgN-slim-Unofficial
1. Extract Android 13 from the downloaded file to your desktop.
2. Rename the file to GSI.img
3. Download and extract AA - Install Android to your desktop
4. Move the GSI.img file to the install folder.
Enjoy ...
If you choose to go back to stock rom, and you have formatted the phone to flash GSI, is the precise partition deleted, and you end up with missing google key / Red txt on the top of your phone.
Here is the file you flash to get rid of that Red txt…
Code:
fastboot flash persist persist.img
_____________________________________________________________________________________
Update:
Some users reported it doesn't work for them.
For me it did the trick, but it doesn't work for everyone.
.
.
.....
Hey, thank you so much, got my WP17 working again but now I don't have IMEI and I'm getting a watermark saying "No google key and tee key" any ideas how to fix this ?
JustNabus said:
Hey, thank you so much, got my WP17 working again but now I don't have IMEI and I'm getting a watermark saying "No google key and tee key" any ideas how to fix this ?
Click to expand...
Click to collapse
.
The IMEI fix: https://forum.xda-developers.com/t/...rm64-a-b-treble-enabled.4504207/post-87571063
Working on a solution for the "No google key and tee key".
Don't forget to update the Android system for camera fix.
.
SwedishForenger said:
.
The IMEI fix: https://forum.xda-developers.com/t/...rm64-a-b-treble-enabled.4504207/post-87571063
Working on a solution for the "No google key and tee key".
Don't forget to update the Android system for camera fix.
.
Click to expand...
Click to collapse
I forgot to say that I don't have any backup on my IMEI and I've no idea where the box is. Is there any other way to get it ? I've sent an email to Oukitel but no answer so far
.
Yes. just copy and paste these numbers. Ore just scramble the numbers around.
IMEI 1: 35524555061532
IMEI 2: 35524555061573
If you don't want to use these IMEI numbers, you can just take the IMEI number under the battery from one of your old phones you already have lying around. it doesn't matter how old they are, even an old Nokia from 1990 works perfectly fine.
_______________________________________________________________________________________DisclaimerEditing or changing the serial number or IMEI of your device is illegal in some countries.
I take no responsibility for your actions. This is for educational purposes only.
.
To remove the Red txt "No google key and tee key".Some people have sent me a pm and say that flashing persist.img didn't work for them.
Try this instead:
Code:
adb devices
pm uninstall -k --user 0 com.mediatek.engineermode
Reboot the phone.
.
noob here, can you create a youtube video on how to install a custom rom to this phone?
dalelad said:
noob here, can you create a youtube video on how to install a custom rom to this phone?
Click to expand...
Click to collapse
.
It's not relay necessary.
There are only 4 small simple steps to perform, the Installer does everything else for you.
Oukitel WP17 [Root][GSI ARM64 A/B Treble-Enabled]
WP17 is a rugged phone with Infrared Night Vision Camera, Helio G95 8GB+128GB 6.78“FHD+ 90Hz 64MP Triple Camera+16MP Selfie 8300mAh Android 11 Global Version. Bought me a Oukitel WP17, but couldn't find much information about this phone. So...
forum.xda-developers.com
It's important for EVERYONE with Android 11 stock firmware, to extract a copy of the firmware as a backup, before flashing other GSI roms. And share a link here on the forum, so others can restore their phones to.
There are many ways to do this. Find a method that suits you best:
pull Stock Android Firmware - Google Search
.