Link To Main Thread
{
"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"
}
About
The WinDroid Toolkit is a Windows program built in Visual Studio using the C# programming language that simplifies the rooting process for many Android devices. The toolkit makes it easy to unlock your bootloader, flash a custom recovery and gain permanent root. It also includes other functions such as flashing kernels, pushing files and installing apps. If you find it helpful, give me a thanks and a donation if you can. If you find a bug or have a feature request, feel free to leave a reply. Thanks!
Download
WinDroid Toolkit
Changelog
Check out this document for current and past changelogs.
Supported Devices
Check out this spreadsheet for a list of currently supported devices.
Device not supported? Make a request here!
Contribute
Check out the source code on GitHub here.
Disclaimers
Please do not post, mirror, or take credit for this toolkit or any related work without explicit permission.
I am in no way responsible for any harm, damage, nuclear fission or bee infestation that may occur to your device through the use of this toolkit.
Reserved
Reserved.
schweet !
I will d/l and check this puppy out, sounds like a cool program.
: this is above my pay grade and thanks : ) .
has anyone confirmed this working? also is it still usable on 6.0.1 ?
Good stuff mate
I installed the tool but it doesnt recognize my X5.
Keeps saying offline.
Thanks!
WinDroid Toolkit v3.0 Is Now Out!
WinDroid Toolkit v3.0 has been released! It's a huge update with a material redesign, major recode and support for 43 new devices!
You can out more specific changes in the changelog here.
You can download the new update here.
All versions before v3.0 will not have their files updated anymore since I've moved from hosting on BasketBuild to Amazon S3. Please update to v3.0 to ensure you're getting the latest recovery and root files!
On the toolkit gui, when I tried to unlock the bootloader, it just stuck on "reboot device" screen while my phone, nexus 5x, has already in bootloader mode. What should I do now ? I did put my phone on "debug" mode, enable "OEM unlock", disable MTP.
system windows 10 drivers are installed and good for the nexus 5x. Device manager list it as good. Start the unlock process by clicking "unlock" the oem unlock is checked. usb debugging is checked. the tools says everything good and when it gets to bootloader says "fastboot device not found"
I check device manager and now says drivers for device not found and the yellow triangle. as soon as i reboot the phone when fully booted it has it listed in device manager as good but in bootloader it as the yellow triangle. please help to unlock it. thank you
Help. Thank you.
EDIT:
the drivers for nexus do not work for the bootloader fastboot mode. Windows lists it as android with the triangle in device manager when in fastboot and i had to allow windows to search for the drivers for it. When found it is listed as something like Marshall Bootloader in win device manager not nexus after the phone is fully booted up.
Related
Hi XDA, today I'm going to show you how to install CWM recovery onto your INO 2.
I recently got myself one because my workplace does not allow camera enabled mobile phones.
I wanted the root functionality and CWM recovery I had on my previous phone(Xperia Arc S).
Unfortunately, Google didn't throw up the results I wanted until I came across this:
http://forum.xda-developers.com/showpost.php?p=44660171&postcount=417
Following the instructions of the thread, I managed to install CWM recovery on the INO 2
Instructions:
oscarblue48 said:
I believe this procedure is not possible on phones with a ubifs file system.
This Tutorial was originally written by Rua1 on the Russian forum, here.... http://forum.china-iphone.ru/post986046.html#p986046 post #1000
You will need Adb drivers installed on your computer. http://pdanet.co/a/
And MTKDroid tools http://forum.xda-developers.com/showthread.php?t=2160490
Mtkdroid tools contains exploits necessary for the rooting process, and this may be detected as a virus by your antivirus program, just temporarily disable your antivirus while downloading, or if you're really paranoid, don't download!:laugh:
Connect your switched on rooted mtk device to your computer and open MTKDroid tool, the tool will recognise your device and connect to it, if the colour indicator in the bottom left corner is green, you already have root shell,and can go on to the next step, if it is yellow, click on the root button at the bottom, and wait for the progress bar, if the indicator stays yellow, or you get an error message, this probably means you do not have Busybox installed, you can install it from the google play store. When the indicator turns to green you have root shell which is necessary for this operation.
image hosting 20mb
Next click on the tab 'root,backup,recovery' and select 'to use boot from phone' then click on 'recovery and boot' and shortly after a dialogue box will appear asking if you want to 'make cwm recovery automatically' click yes
jpg images
The tool will then create the recovery and another dialogue box will appear asking to 'install created recovery to phone', click yes.
screenshot program
And finally the tool will ask to reboot into recovery mode, click yes and the device will reboot into CWM recovery so you can check the installation was successful.
Thanks to Rua1 for creating this brilliant tool.
Click to expand...
Click to collapse
Proof Of Concept:
{
"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"
}
Alternative download link for MTK Droid Tools (if DepositFiles from original link isn't working for you): http://www.mediafire.com/download/6z9acf5um65cuj2/MtkDroidTools+v2.5.3.zip
Tested and working on latest update (iNO 2-V012 - As of 11/04/2014)
All credits and work belong to the original developers, I do not own anything.
popthosegaskets said:
Hi XDA, today I'm going to show you how to install CWM recovery onto your INO 2.
I recently got myself one because my workplace does not allow camera enabled mobile phones.
I wanted the root functionality and CWM recovery I had on my previous phone(Xperia Arc S).
Unfortunately, Google didn't throw up the results I wanted until I came across this:
http://forum.xda-developers.com/showpost.php?p=44660171&postcount=417
Following the instructions of the thread, I managed to install CWM recovery on the INO 2
Instructions:
Proof Of Concept:
Alternative download link for MTK Droid Tools (if DepositFiles from original link isn't working for you): http://www.mediafire.com/download/6z9acf5um65cuj2/MtkDroidTools+v2.5.3.zip
Tested and working on latest update (iNO 2-V012 - As of 11/04/2014)
All credits and work belong to the original developers, I do not own anything.
Click to expand...
Click to collapse
Good one. Kitkat for it??
defybest said:
Good one. Kitkat for it??
Click to expand...
Click to collapse
Did you bother to check the official website? They already mentioned that they will not update this phone to KitKat.
僕のINO2から送られてきた
is there a site to download the firmware for this phone.
No, you have to go to the service centre to get it flashed
僕のINO2から送られてきた
Hello, my name as you can probably guess is Krutonium.
I do a lot of work over at leshcatlabs (Can't post a link yet, if a mod could edit that would be great!) and I was wondering if this community would be interested in my little project (Story about Why first, or look about 5 inches down).
So I recently got this little Android Tablet as a Gift, and I wanted to root it so I could play around with some less normal features like overclocking and such. So I go and get the ADB Drivers from Google, and quickly discover that I have to re-install the driver every time I reboot my tablet. This quickly got annoying, so I took a look at the actual inf (Over at leshcatlabs, we modify Video Card Drivers, so this was pretty much the norm for me, though it has a much cleaner layout than AMD's inf's) and decided to add my Tablets ID's into the driver. This of course worked, and it stayed installed.
I am willing to make a Massive INF File with your DEV_ID's, if you are interested.
I will sign it with a Driver Certificate, so that it will install on Windows Vista, 7, 8, 8.1, and the upcoming 9, without having to disable Signing Enforcement, and enabling you not not have any issues like having to constantly re-install the driver.
Any Questions? Are you interested? Please reply to let me know!
Hi krutonium i use unifl since years thanks for your work! I'm glad to see you on xda too good luck with your new project! :highfive:
Hi there!
I'm Tito & I've recently joined the Android USB UnifL team - the initiative as told by @Krutonium. Lot of improvements are made already!
Website: http://leshcatlabs.net/2014/09/28/android_adb-usb_unifl_drivers/
Discussion forum: http://leshcatlabs.net/forums/viewforum.php?f=15
Download: http://leshcatlabs.net/downloads_usb_unifl/
In a nutshell:
We provide digitally signed drivers for ADB & Fastboot (if available) interfaces.
Some other interfaces, such as Sony's Flashmode, Samsung's Download mode, Xiaomi's MDB are also supported.
No need to turn off Driver Signature Enforcement in Windows x64 to install these drivers.
Windows XP, Vista, 7, 8, 8.1 (& in future 10) are fully supported.
New devices from OEMs & generic/clone devices can easily be added in the supported list.
Automatic update check in installer.
Rapid development cycle.
List of supported OEMs & devices :
Coolpad
Dell
Google
HTC
Huawei
Intel SoC based devices
LG
MediaTek SoC based devices
Motorola
NVIDIA
OnePlus
Rockchip SoC based devices
Samsung
Sony
Sony Ericsson
Trekstor
Xiaomi
YU
To do:
There are already number of similar efforts exist, like Koush's Universal ADB Driver & @1wayjonny's Universal Naked Driver, but they aren't updated & actively maintained.
We always try our best to swipe out the errors & add more devices in the supported list. But to do so, we need active support from the users.
If your device from mentioned list doesn't work or you have a new device that isn't present in the list, please do the following:
1. Make sure USB Debugging in on in the Android device. Connect it with the PC.
2. Press Win key + R to open the Run dialogue box, type "devmgmt.msc" (without the quotes) & press Enter - Device Manager will be opened.
3. Go to the device that is unrecognized - the name should have something to do with your device, for example:
{
"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"
}
4. Double click on the device, go to Details tab and from the dropdown menu, select "Hardware Ids".
5. Take a screenshot or copy the texts. You need to post like this:
Please add my Tablet/Phone:
(OEM) PROSCAN
(Model) PLT7044K-B
(Dev_ID for ADB)
USB\VID_2207&PID_0010&REV_0222&MI_01
USB\VID_2207&PID_0010&MI_01
Click to expand...
Click to collapse
6. Similarly do for Fastboot interface if your device supports it.
7. Last but not the least, due to increasing number of cloned/generic devices, it is really helpful for us if you also link the official driver pack/sync tool/phone manager application of your OEM.
[Screenshots are created by @Krutonium ]
It would be better to join our forum regarding issues & support but we're also active in XDA too.
:good::highfive:
[WIP] Clean Huawei Forum: Last Update: 24.6.2015
Hello Everyone! VisualTech48 here.
I'm a proud owner of our beloved phone Huawei Y530, and yes, we already have a thread, but its unclean, and hard to find some things, so with the approval of a mod, I'm here to gather everything on the first post so everyone doesn't have to go searching and asking if it works.
In addition here will be also posted any ROMS people make, till we get our official forum.
CyangoenMod Status:
Currently Booting is possible but there is a lot of work needed to be done.
{
"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"
}
We are going to start with CM11 first, as PieroV and CENTSOARER agreed
PieroV said:
I don't think that CM12 will be ported... I'm still on the idea that CM11 has to come first.
I'm gonna borrow another phone from a friend, because I can't be without the phone for many hours...
Click to expand...
Click to collapse
CENTSOARER said:
@PieroV yes, I think CM11 is the way, too.
Click to expand...
Click to collapse
Custom ROMS:
■ Currently non available
Clockwork Recovery v6.0.5.1:
■ Download the ZIP and extract it on desktop
■ Open the CWM-Recovery6.0.5.1.exe
■ Power off your phone, and make sure that fast boot in developer options is disabled
■ --To go into fastboot mode, hold Volume Down(-) and power button. White screen should appear in a few seconds.
■ Press 1 to test it out first, if it works you can flash it with 2 again.
■ Enjoy your CWM
A more detailed guide and credits goes to (himister) for making the flash app, and his post here
Clockwork Recovery.zip
*Requirements: Flashing CWM requires a Unlocked phone and Huawei drivers installed for ADB
Nandroid backups [Restoring if your phone has issues]
■ CENTSOARER: B512 - Orignal Post - Download
■ Alfcup - B512 - Orignal Post - Download
Offical ROMS
Can be found here (Thanks himister): http://susutun1.blogs.com/.../530group.html
Upgrading System guide (DLOAD):
Dload is the way we upgrade frimware in Huawei. To flash a new version of the OS you first need to check what version you have. You can do that by going on your phone and open the SYSTEM Update app.
Image_01
The reason why you have to check this, is due to you cannot flash an lower version. So if you have B179, you cannot flash B177. Keep that in mind as, if you do try to flash it will show you an error.
When you download the new frimware bear in mind to put the dload folder in the root directory of your SD-Card.
Example: /sdcard1/dload
After you have placed your folder, go to the SYSTEM Update app, and press Local Update and comfirm.
Image_02
Rooting Wiki [More detailed guide]
Start by downloading and installing towel root and KingsUser here:
■ http://towelroot.org/Towelroot.apk"]TowelRoot
■ KingsUser
First open towelroot and press "Make it ra1n". If it says sucessful root, you can proceed and go to KingsRoot.
NOTE: Do not update Kings root, you will be offered to fix your root, just press yes. After it finishes, your phone is rooted!
If I forgot something fell free to write it down, this post will be updated as much as it can.
Reserved.
Can you put the latest b515 firmware link for upgrading with dload method
{
"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"
}
Hello every body, I made this guide for thosethose
who are new for Android ( coming from IOS or Windows...)
And for those who wants to know how to understand Guides through XDA.
SO LETS GET STARTED.
Main_Things
About Android
Android is a mobile OS (operating System) currently developed by Google
based on the Linux kernal and designed primarily
for touchscreen mobile devices such as smartphones and tablets.
Now we are going to talk about some main things
that you need in almost every guide:
ADB
A short of : Android Debugging Bridge
What's the ADB??
It's a command line utility which can control your device over USB from
a computer (copy file from and to the device ,install and uninstall apps and more..........).
How to enable it??
Go to Settings>About_Phone>Build _Number and press it 7 times.
Now go back to Settings>Developer_Options and
enable Android Debugging or USB Debugging .
ROOT
What's the ROOT??
Root is the process of allowing users to attain root access over various Android subsystem.
It's like running programs as administor in Windows, or running a command with sudo in Linux.
Notes
1_If you want to root your phone search for it in your device forums.
2_In some modding threads they say:
move it to system>apps and give it rw-r-r. It means to goto app's permissions
and check like in photo.
ROM(s) & MOD(s)
What is the deference between ROM(s) and MOD(s)
Rom(s):
Is a whole Android operating system ( firmware,apps......).
Mod(s):
Is a Modifications added to the software stored on the device.
Here you can learn everything you need before installing Rom(s)
Bootloader
ULB: Short of UnLocked Bootloader
LB: Short of Locked Bootloader
What is the Bootloader
Bootloader is a piece of code that runs before android loads up.
Bootloaders usually contain several ways to boot the OS kernal
and also contain commands for debugging and/or modifying
the kernal environment.
Note:
If you want to unlock your Bootloader you can
look for the way of unlocking n your device forums.
Recovery
What is the Recovery
It's the bootable partition that has the recovery console installed:silly:.
Or Simply it's where you can find tools to repair your phone
and install new ROMs.
The stock ROM recovery is very limited,
but the Custom recoveries offer much more,
they are coded to allow backup and restore function,
selective deletion of data So you don't have to
wipe everything and some of them have file explorer.
And here the most famous custom recoveries:
CWM: Short of ClockWork Mod.
TWRP: Short of TeamWin Recovery Project.
Something
In some ROMs thread's titles you could see these words
Official: it means the phone is supported from
the developer and it's Not port.
Unofficial: it means that it's port and it's not officially
supported from the developer.
Nightly: it means the rom have an every night update
for example: CM.
Shortcut
ADB: Android Debugging Bridge.
AOSP: Android Open Source Project.
CWM: ClockWork Mod.
TWRP: TeamWin Recovery Project.
CM: CyanogenMod.
ULB: UnLocked Bootloader.
LB: Locked Bootloader.
ICE: ICEcream sandwich 4.0
JB: Jelly Bean 4.1 , 4.2 , 4.3
KK: KiKat 4.4
LP: LolliPop 5.0 , 5.1
M: Marshmallow 6.0
Some shortcut that usually used in forums
OP: it means the "original poster" or "original post".
FCorFS: Short of : force close/stop
BL: Shot of BootLoop, it's when the phone stuck
at bootanimation because of something missed in the system.
Hardbrick: It's when your phone is dead
and you can't even boot,
So you must repair the hardware (motherboard....).
Softbrick: it's a software brick which
could be fixed with flashing stock ROM .
If I forgot anything just told me and please feel free to ask
Blackburn: the framework as from its name is the frame that the app work in it's the entire stack of stuff that makes up the OS.
Like siwtchs, buttons, colors, styles and. So on.
This'd the reason that the same app has different look in Samsung (for example) than Xperia .
n78 shadow said:
Shortcut
Softbrick: it's a software brick which
could be fixed with flashing stock ROM .
If I forgot anything just told me and please feel free to ask
Click to expand...
Click to collapse
Awesome work brother it was very useful.
Just one question what is the android framework???
And thank in advance.
What is This?
Yes I know there are tons of drivers Installers around but this is more..
This is a Standalone version of the drivers installer from the SkipSoft Unified Android Toolkit.
--DRIVERS--
There are a selection of driver packages you can install to suit all devices (google, cwm universal, samsung and oneplus). There is also lots of help and information on what to do if the drivers don't work properly. A test routine/checker is available which will attempt to detect the plugged in device (and reboot to fastboot mode and back on google/nexus devices) to verify the drivers are working. Tools are also included to remove unwanted drivers if a fresh start is needed.
--ADB/FASTBOOT--
The Adb/Fastboot installer (Android Debug Bridge version 1.0.36) can install System-Wide (for all Users on the PC) or for the Current User Only. This is a very simple installer and means you do not have to download the complete SDK from google. You can also easily open a command prompt to send commands to your device.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download link: FROM SKIPSOFT
This really is the the most comprehensive driver/adb/fastboot installer available.
Changelog:
1.0.3 - Added adb/fastboot latest version check at startup and download if needed
1.0.2 - Added command prompt option to menu
1.0.1 - Fixes to adb/fastboot installer
1.0.0 - Initial release
Mark.
**RESERVED**
Hey there. Thought I might ask here.
Recently updated to 7.1.1 on my Nexus 5x and now fastboot is not working. Have spent most of the day trying everything I can find on here and installing or uninstalling drivers on both my laptop and desktop with no joy.
Tried all the options within your software but no joy. Adb works ok but fastboot just will not work.
I realise this is not an issue with the software but wondering if you may know of something else to try.
36 hours now on an unrooted phone is the first time in years
Thanks
Just in case this is some use to you with your Toolkit the workaround for the fastboot issue was sorted as shown in the post below.
http://forum.xda-developers.com/showpost.php?p=69273414&postcount=33
divvykev said:
Just in case this is some use to you with your Toolkit the workaround for the fastboot issue was sorted as shown in the post below.
http://forum.xda-developers.com/showpost.php?p=69273414&postcount=33
Click to expand...
Click to collapse
Thanks I will add the google kedacom drivers as an option in the installer.
Mark.