Related
Hey guys, flex here. So the deal is that I bought my blade about 2 weeks ago. It's version 2.2 and I've been trying to customizate it for like one week now. At first I heard from someone that my device could have faster that it was when I bought it. So back then I didn't know anything about androids (neither I do now haha), so I just googled "how to make zte blade better" and found someone saying you can do it with Superuser. Downloaded Superuser from somewhere, installed the apk through my sd-card and thought for looong time how does it work and why hasn't my phone become any faster.. :-D
After that I tried still to find solution for this and began to understand what 'rooting' means. And this is where it got tricky. I have tried almost every way how to root, and the rooting programs say that my phone is already rooted, when it really _isn't_. Because all the programs said my phone iz rooted already, I have tried installing some custom ROMs, without any success. It always stays there when I install the clockwork recovery apk, open it and my phone says it's force shutdown, or it doesn't respond. Could it have something to do with the installed Superuser without rooted phone?
What should I do to fix this? Could you help me step-by-step how to root my phone and get some nice custom ROM. I'm not so good at these things as you may see.. :-D
PS. please don't say things like 'go check another threads' because I have checked EVERY of them, guys you are my last hope
Sincerely, flex
Hey flex this thread has got a step by step guide just like you need
wiki.cyanogenmod.com/wiki/ZTE_Blade_(Gen2):_Root_and_Recovery
Sent from my ZTE-BLADE using Tapatalk
Great, thanks! I will try that as soon I wake up tomorrow!
It went well until this part:
Open the Device Manager.
Right-click on My Computer (Windows XP) or Computer (Windows Vista/7).
Click on Manage.
Click on Device Manager on the left.
You will probably see Unknown Device with ADB listed under it with a yellow exclamation mark.
Right-click on ADB.
Click on "Update Driver Software".
Click on "Browse my computer for driver software".
Click on "Let me pick from a list of device drivers on my computer".
Click on "Have Disk".
Click on "Browse".
Navigate to "C:\android-sdk-windows\google-usb_driver" and select "android_winusb.inf".
I clicked "android_winusb.inf" but then it said that my computer doesn't support that filetype or something like that.. What to do now?
Guys what does this mean "Open terminal and run the following commands"?
What is terminal and do I have to download it ?
flexiboi said:
Guys what does this mean "Open terminal and run the following commands"?
What is terminal and do I have to download it ?
Click to expand...
Click to collapse
If youre using win 7/vista, just type in cmd in the start menu and press enter. Else just press win+r and then type cmd and press enter.
flexiboi said:
It went well until this part:
Open the Device Manager.
Right-click on My Computer (Windows XP) or Computer (Windows Vista/7).
Click on Manage.
Click on Device Manager on the left.
You will probably see Unknown Device with ADB listed under it with a yellow exclamation mark.
Right-click on ADB.
Click on "Update Driver Software".
Click on "Browse my computer for driver software".
Click on "Let me pick from a list of device drivers on my computer".
Click on "Have Disk".
Click on "Browse".
Navigate to "C:\android-sdk-windows\google-usb_driver" and select "android_winusb.inf".
I clicked "android_winusb.inf" but then it said that my computer doesn't support that filetype or something like that.. What to do now?
Click to expand...
Click to collapse
It should only say that if you try to open the file not going thru the steps above?
the win+r thingie went well until there came command "exit" it said it didn't find and on the cmd it just closed the cmd
Bro, if you're computer recognizes your Blade, then you probably don't have to do the steps above. That stuff you posted is a "how-to" of installing the Blade drivers on to your computer
---------- Post added at 12:17 PM ---------- Previous post was at 12:16 PM ----------
I mean, can you transfer files to/from your computer, and to/from your phone?
You said you've read all the threads out there, but have you tried this. I had a stock 2.2 blade and when I first flashed a custom rom I had to use temporary root with z4root to install apps I needed (don't ask which cause I don't remember anymore ). Anyhow, If you can't get permanent root for your blade working, You could try temporary rooting it and see how far it gets you
I've spent the last four hours reading forums on how to unbrick my brand new kindle fire, and they would be amazingly helpful if i had twrp to recover or my kindle would even connect to my pc. I rooted my kindle fire and then went to instal twrp and it bricked during installation and is now stuck on the kindle fire logo screen. since my computer wont detect it anymore i can't get any of the fixes to work and hard reset isn't helping at all. i feel like i'm out of options but i'm hoping someone here will have something left to at least get my kindle to connect so i can fix it. anything would be helpful in at least giving me options to fix the problem since right now i just feel lost.
use kf utility and update ur drivers first of all.
second, ur device should be in fastboot. u can use the kf utility to check if fastboot is working and continue installing twrp.
sent from my kindle fire
smirkis said:
use kf utility and update ur drivers first of all.
second, ur device should be in fastboot. u can use the kf utility to check if fastboot is working and continue installing twrp.
sent from my kindle fire
Click to expand...
Click to collapse
it won't connect to my computer so i can use a program on it, when i turn on kf utilities it comes up as offline and when i go to do anything it says the devices isn't connected
punkboyarde said:
it won't connect to my computer so i can use a program on it, when i turn on kf utilities it comes up as offline and when i go to do anything it says the devices isn't connected
Click to expand...
Click to collapse
First of all you will need to follow this guide and you will have the answers to the problems that you are having:
http://forum.xda-developers.com/showthread.php?t=1417234
You will have to update the drivers manually by doing this
- Go to start Menu and right click on computer, Click manage
- In computer Management hit device manager
- I am guessing that you see your kindle connected in there with a yellow ! by it
- Right click on kindle and update driver software
- Click Browse my computer for driver software
- Click let me pick from the list of device drivers on my comp
- Click Next
- Click Have Disk
- Click Browse
- Navigate to your user folder in that window/ or wherever your .android folder is
- Double click on .android folder
- Double click on Driver Folder
- Now Click open
- Now click ok
- Click Next
- ClickInstall driver software anyway
Rmember to hit that thaks button
[-_-] said:
First of all you will need to follow this guide and you will have the answers to the problems that you are having:
http://forum.xda-developers.com/showthread.php?t=1417234
You will have to update the drivers manually by doing this
- Go to start Menu and right click on computer, Click manage
- In computer Management hit device manager
- I am guessing that you see your kindle connected in there with a yellow ! by it
- Right click on kindle and update driver software
- Click Browse my computer for driver software
- Click let me pick from the list of device drivers on my comp
- Click Next
- Click Have Disk
- Click Browse
- Navigate to your user folder in that window/ or wherever your .android folder is
- Double click on .android folder
- Double click on Driver Folder
- Now Click open
- Now click ok
- Click Next
- ClickInstall driver software anyway
Rmember to hit that thaks button
Click to expand...
Click to collapse
it says that windows says the driver is up to date, honestly just knowing that is is connected just not recognized is bringing my hopes up and deserves a thanks
not sure if it's important to note but my computer doesn't show it as a kindle just as an unknown usb device
My only way out of this was to use another computer, download the drivers first, then download the twrp file so it doesn't give you the "trwp isn't downloaded, let me do it for you" message then do all the KFU steps over. Hopefully it will work for you also.
Sent from my MB860 using XDA App
pre4speed said:
My only way out of this was to use another computer, download the drivers first, then download the twrp file so it doesn't give you the "trwp isn't downloaded, let me do it for you" message then do all the KFU steps over. Hopefully it will work for you also.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
i'm not very clear about what you mean by this. i plugged it into my laptop just now and it came up usb device not recognized. I just need to find a way to get a computer to recognize it as a kindle again or for it to get out of getting stuck on booting so i can fix it.
got it fixed, i was still trying a few things and the one i think that did it was i plugged it back in while it was off and while it didn't recognize it at first but about a minute after i turned it back on my computer found it and got the driver installed for me. apparently it has to be off when plugged in the first time for it to work, so i basically spent seven hours to find that out but hopefully this ends up helping someone so the time wasn't that wasted. but it's seven in the morning so i should probably get some sleep.
I installed the twrp and got stuck on the yellow triangle after pressing reboot. My kindle was not recognised by my PC, I had to switch off my kindle then plug it in to my PC then in device manager under android phone i updated my driver from the .android folder. I then reinstalled twrp from the utility even though the utility said device not found it still installed it and my kindle reebooted normally and twrp was installed. ope this helps anybody in need.
✪✪✪ [ROOT] [Restore] [OneClick OR Manual] [PC] [MAC] Kwongger's FLO Noob Root Kit ✪✪✪
EVERYBODY!
WE ARE BACK DUE TO POPULAR DEMAND!!!
Kwongger's All-In-One FLO Noob Root/Restore Kit FOR PC and Mac
YES! We are ADB FREE!!!
Why we are back:
I really feel accomplished when I acutally do the commands myself! Apparently so do others, we are back B****ES!
I felt that I didn't get the help I needed/wanted as a n00b on XDA, this is a new account FYI, so I like to make n00b kits with AWESOME instructions, ENJOY!!!
FYI: I want to provide the best possible support that I can (even though this is free)
DOWNLOAD v3
Hey! The ONE-CLICK/Restore update is currently uploading!
Instructions in post #2, Change-log in post #3.
DISCLAIMER:
By downloading the files, you accept the fact that I am NOT in anyway responsible for what YOU do to YOUR device, unless it starts shooting lasers at iOS devices, then all the credit is mine . Really,in all seriousness, this procedure is a BEGINNER procedure, I am simply providing instructions and TOOLS! I AM NOT RESPONSIBLE FOR ANYTHING THAT HAPPENS TO YOUR DEVICE!!!
Manual ROOT Instructions!
(If you want One-Click, then Just double-click either the Flo ROOT by Kwongger.bat (to root) or the Flo RESTORE.bat for a out-of-box restoration!
I’ll make a video soonish.
Driver Installation!
To Install The Drivers Fresh
Connect your Android-powered device to your computer's USB port.
Right-click on Computer from your desktop or Windows Explorer, and select Manage.
Select Devices in the left pane.
Locate and expand Other device in the right pane.
Right-click the device name (such as Nexus S) and select Update Driver Software. This will launch the Hardware Update Wizard.
Select Browse my computer for driver software and click Next.
Click Browse and locate the USB driver folder. (The Google USB Driver is located in<sdk>\extras\google\usb_driver\.)
Click Next to install the driver.
Follow the Instructions!
Upgrade Existing Drivers
Or, to upgrade an existing Android USB driver on Windows 7 with the new driver:
Connect your Android-powered device to your computer's USB port.
Right-click on Computer from your desktop or Windows Explorer, and select Manage.
Select Device Manager in the left pane of the Computer Management window.
Locate and expand Android Phone in the right pane.
Right-click Android Composite ADB Interface and select Update Driver. This will launch the Hardware Update Wizard.
Select Install from a list or specific location and click Next.
Select Search for the best driver in these locations; un-check Search removable media; and check Include this location in the search.
Click Browse and locate the USB driver folder. (The Google USB Driver is located in<sdk>\extras\google\usb_driver\.)
Click Next to upgrade the driver
Follow the Instructions!
Click to expand...
Click to collapse
Unlocking The Boot Loader!
1. Enable USB Debugging on your Nexus 7 in Development Settings
2. Open yourself a Command Prompt (or Terminal for MAC) in the Kwongger Nexus 7 folder!
a. Hold down shift
b. Right Click in the folder
c. Click Open Command Window/Prompt here
3. Boot into the bootloader using:
Code:
adb reboot bootloader
!!!!!!!!!!!NOTICE!!!!!!!!!!!!!!!
The next step will FACTORY RESET your device!!!
4. Once it is in the bootloader, enter this:
Code:
fastboot oem unlock
5. It will now ask you if you do, in fact, want to unlock your bootloader. Use Volume up/down to select YES and hit power to Confirm.
6. Your Nexus 7 FHD now has an Unlocked Bootloader.
7. IMPORTANT:
Reboot the device!
Click to expand...
Click to collapse
Choose either TWRP or CWM!
Installing TWRP!!!
1. Get into Your bootloader Again. (Above)
2. Type the following to flash the Team Win Recovery Project version 2.6:
Code:
fastboot flash recovery nexus7twrp.img
note: if you change the name use that in the .img part
3. Done!!!
Installing Clockwork Mod Recovery!!!
1. Get into Your bootloader Again. (Above)
2. Type the following to flash the Team Win Recovery Project version 2.6:
Code:
fastboot flash recovery nexus7CWM.img
note: if you change the name use that in the .img part
3. Done!!!
Click to expand...
Click to collapse
Rooting on Android 4.3!!!
.01 Copy The SuperSU.zip to the internal storage of your device.
1. Boot in to your bootloader and use the volume keys to select Recovery and use the Power button to confirm.
1a. RECOMMENDED: Tap BACKUP and Swype to confirm to make a backup of your current, UNROOTED n7.
2. Tap INSTALL.
3. Navigate to where you put the SuperSU.zip
4. Tap the zip.
5. Swype to confirm the flash!
6. If all goes well (no reason that I know that it shouldn’t) YOUR NEXUS 7 IS ROOTED!!!!
Click to expand...
Click to collapse
CONGRATS!!!!!!!!!!!!!
v1
Nothing New! This is 1.0
Click to expand...
Click to collapse
v2
I updated the Fastboot and ADB because some people were having some issues, it seems to have fixed the issues.
Click to expand...
Click to collapse
v3
I added the ever popular Mac Support! AND Clockwork Mod Recover, I don't know it is touch or not XD, could someone check? Just type
Code:
fastboot boot recovery nexus7CWM.img
and let me know! Thanks in advance.
Click to expand...
Click to collapse
I'm on windows 8 and have all the drivers installed but when I try and use the command "adb reboot bootloader" I get "error: device offline"
---------- Post added at 08:30 AM ---------- Previous post was at 08:12 AM ----------
I got it to work using the normal android sdk download. I couldn't get it to work using just the files I downloaded from you.
Gabik123 said:
I'm on windows 8 and have all the drivers installed but when I try and use the command "adb reboot bootloader" I get "error: device offline"
---------- Post added at 08:30 AM ---------- Previous post was at 08:12 AM ----------
I got it to work using the normal android sdk download. I couldn't get it to work using just the files I downloaded from you.
Click to expand...
Click to collapse
That's weird. I will update it.
Sent from my HTCONE using XDA Premium HD app
Actually!
Are you on 32bit? I included 64bit.
I like that you moved it to General!!!
I always thought that the DEVELOPMENT threads should be only used for KERNELS/ROMS
THANK YOU
Hey man, thanks for the instructions but could you clarify that you have to restart/boot up completely after unlocking the bootloader? I was still in fastboot after unlocking it when I flashed TWRP, and now TWRP is asking for a password, failing on all operations and I'm stuck in a bootloop.
EvanVanVan said:
Hey man, thanks for the instructions but could you clarify that you have to restart/boot up completely after unlocking the bootloader? I was still in fastboot after unlocking it when I flashed TWRP, and now TWRP is asking for a password, failing on all operations and I'm stuck in a bootloop.
Click to expand...
Click to collapse
Dang Dude, I am sorry. I just went ahead and put that in. :/
I want to help you with this.
Can you get into the boot loader or anything? Maybe if you can get TWRP working, I can send you a Nandroid of a stock, one (Once I get mine )
Kwongger said:
Dang Dude, I am sorry. I just went ahead and put that in. :/
I want to help you with this.
Can you get into the boot loader or anything? Maybe if you can get TWRP working, I can send you a Nandroid of a stock, one (Once I get mine )
Click to expand...
Click to collapse
Just found the solution in another thread: Open TWRP, Format Data first, then Factory Reset, finally reboot. I knew it wasn't a long term problem but I'm glad I didn't have to wait for Google to release Factory Images lol.
Gabik123 said:
I'm on windows 8 and have all the drivers installed but when I try and use the command "adb reboot bootloader" I get "error: device offline"
---------- Post added at 08:30 AM ---------- Previous post was at 08:12 AM ----------
I got it to work using the normal android sdk download. I couldn't get it to work using just the files I downloaded from you.
Click to expand...
Click to collapse
I am having this issue in windows 8 also, "offline" but I am getting the same thing using android sdk. Can someone provide some assistance please. Not sure why having such an issue.
EvanVanVan said:
Just found the solution in another thread: Open TWRP, Format Data first, then Factory Reset, finally reboot. I knew it wasn't a long term problem but I'm glad I didn't have to wait for Google to release Factory Images lol.
Click to expand...
Click to collapse
AWESOME!!!!!!!!!!
I feel better now XD
jmill75 said:
I am having this issue in windows 8 also, "offline" but I am getting the same thing using android sdk. Can someone provide some assistance please. Not sure why having such an issue.
Click to expand...
Click to collapse
I don't know... I have Windows 7. I also have NO IDEA why this would happen... Try using a port on the back of the PC (desktop) . If that doesn't do it, try USB 3.0 (if you have it). Also, if you are using the Stock cord, try other cords. That is all I can think of... :/
Kwongger said:
I don't know... I have Windows 7. I also have NO IDEA why this would happen... Try using a port on the back of the PC (desktop) . If that doesn't do it, try USB 3.0 (if you have it). Also, if you are using the Stock cord, try other cords. That is all I can think of... :/
Click to expand...
Click to collapse
There is a way to disable driver verification after rebooting in windows 8. I had to do this with my SGSIII and Win 8 x64, just google around for it, bet that's the problem.
RubenRybnik said:
There is a way to disable driver verification after rebooting in windows 8. I had to do this with my SGSIII and Win 8 x64, just google around for it, bet that's the problem.
Click to expand...
Click to collapse
Thanks! I will find it and add it to the instructions with credit.
Sent from my HTCONE using XDA Premium HD app
I see the pack includes the tools for MAC. I am on 10.8.4. Has anyone tried this on a MAC yet? I will be doing so later.
androidfr33k said:
I see the pack includes the tools for MAC. I am on 10.8.4. Has anyone tried this on a MAC yet? I will be doing so later.
Click to expand...
Click to collapse
Wait how would you do this on mac? Does the same .zip file work or would I need a different one? If you get it working please post a tutorial!
Looks like SuperSU came with the TWRP image(no need to copy it over separately). I tried to reboot from TWRP after updating the recovery and it forced me to flash SuperSU to root.
Nxxx said:
Wait how would you do this on mac? Does the same .zip file work or would I need a different one? If you get it working please post a tutorial!
Click to expand...
Click to collapse
I included Mac ADB... But not fastboot, you would need Fastboot as well, i'll get a Mac pack up tonight.
disregard....
working great! thanks OP
Hi?
I'm posting this thread for all those who want to root their tablet but need a step by step guide for the same. I have condensed the information from many threads and put it into one. All the credit goes to the respective thread owners who have posted the guides. Let's begin:
NOTE: Im not responsible if you brick your device. You are solely responsible for what happens. If you follow the steps correctly it is unlikely that it will harm your device. If you face any issues you can post it here and I will try to solve them ( or someone else will). All good.
Scary stuff apart, let's begin to root your device ?
1. On your device, Go to Settings, Developer Options, and click on Enable USB Debugging. If there is no Developer Options in Settings, Click on About Phone and click 7 times on Build Number. This will give u the option.
2. Once you have enabled it, connect your device to your computer via USB cable.
3. Install the device drivers from the autoplay options.
4. Right click on My Computer and click on Manage
5. A new window will open called Computer Management, under which u have to click on Device Manager.
6. A list of devices connected to your computer will be shown on the right hand side.
If your device is listed under heading Android, as Android ADB Composite Device, then there is no need to download and install adb/fastboot drivers, and you can go ahead with the rooting process.
But its most likely your device will be listed under Other Devices. Under that it will be as MTP device or by the name of your device itself. This means you have to download and install adb/fastboot drivers on your computer before rooting it.
7. Open your browser and click on http://adbdriver.com/upload/adbdriver.zip which will download the adb installer on your computer. Run through the setup and install it. Run the program, it will automatically detect your device and install the necessary adb/fastboot drivers for it on your computer.
Alternatively, you can click on http://forum.xda-developers.com/showthread.php?p=48915118 through which you can install the same. I did it with the first method for my device.
Download and install it in [C drive].
8. Once the drivers are installed, go to Device Manager again (Step 4 and 5), and check on the list of devices. Your device should be listed under the heading Android, and showing as Android ADB Composite Device.
9. Open up C drive, there should be a folder named 'adb' under it. Open that folder and right click anywhere and open a command prompt.
U can also press 'Win+R' keyboard keys and type in 'cmd.exe' to open up a command prompt and use the cd command to come into the right folder. Once your into the adb folder in the command prompt (it should show as "C://adb>".
Type in command 'adb devices' and press enter (without the colons).
This should show you that your device is connected by the name of your chipset as Baytrail******. If it doesn't show this it means the adb drivers are not installed or ur device is not connected to the computer. Only once after it detects your device you have to go ahead with your rooting process.
10. After you have successfully completed all the above steps you are now ready to root your device.
11. Click on this link forum.xda-developers.com/showpost.php?p=57543871&postcount=1 from where you will have to download 'Intel Fastboot Tethered Temporary Recovery Session Launcher' onto your computer and extract it to some folder.
12. Download the UPDATE SuperSU zip file to your device and store it in your internal memory so you can find it easily later.
13. Now open the folder where you have extracted the Intel Fastboot Tethred Temporary Recovery Session launcher. Double click the launcher.bat file to start and type " ACCEPT " case sensitive without quotes to continue.
check that the tool is reporting as either :
DEVICE STATUS: ADB-ONLINE
DEVICE STATUS: FASTBOOT-ONLINE*
If " DEVICE STATUS: UNKNOWN " please check your cable connection and driver installation under Windows Device Manager
If " DEVICE STATUS: UNAUTHORIZED "
Please check if your devices is displaying an authorization prompt.
Be sure to check 'Always allow from this computer' and then press ok.
It will ask for the type of recovery u would prefer to run. Options 1-4 will be TWRP recovery and 5 will be CWM. I selected the CWM recovery. So enter number '5' and press enter.
14. It will display the list of triggers to be selected for the rooting process. Select the trigger to launch the Temporary CWM Recovery Session.
The list will be as follows:
T1 oem startftm ( very few devices support this command , but its the original used so )
T2 oem backup_factory ( limited devices support this command )
T3 oem stop_partitioning ( should work on alot of kitkat builds )
T4 oem stop_partitioning ( probably works on all devices that are supported (Jellybean , KitKat , Lollipop)
15. Select trigger 'T4' if you have upgraded your tablet to Lollypop Android 5.0.1. After selecting the trigger your device should reboot into fastboot and begin to copy files to your device.
note :*If your device hangs at the waiting-for-device screen and you see droidboot CMD Waiting on your devices double check that the fastboot driver installed correctly.
note :*If you see unknown oem command the trigger isn't supported by your device.
16. The temporary cwm recovery session will start at this point on your device.
17. Select install zip from the recovery menu using vol up / vol down to navigate and power to select.
18. Select install zip from sdcard / external_sd depending on where you placed the file and select the UPDATE-SuperSU-vX.Xx.zip you downloaded earlier
19. Confirm the installation.
20. After install completes reboot your device*through the reboot device option in the recovery menu itself.
21. It's going to take a while for the device to reboot. 'Android is upgrading' window will pop up once the screen gets on. After the boot is complete open all apps to see Super SU installed in it.
Now you have successfully rooted your Yoga Tablet 2. Enjoy ☺
NOTE: Follow all steps carefully and correctly so it becomes highly unlikely that you may brick your device. Make sure there is no powercut to your computer during the rooting process if you are not using a laptop or a UPS for your system. You can post any queries or questions in the thread.
All credit goes to the original thread owners, social-design-concepts, workdowg for helping all yoga tablet users to be able to root their devices.
A lot of work has gone into making this NOOB friendly step by step guide. Hit thanks if this helps you. Much appreciated. Have fun rooting.☺
Posted from my Rooted Lenovo Yoga Tablet 2 (830LC).
Much appreciated for this noob guide.
Thanks for the tutorial.
I did all the steps as you said. I am at step 15 and selected t4 and then the command prompt showed waiting for device and then my tab rebooted itself and then came to a fastboot mode.
Now n TAB its showing error that "E: No valid installer medium found"
now when i press the volume keys, the boot option changes and then the error message changes to
"could not open /sys/devices/virtual/backlight"
Please help
Thanks........ successfully rooted yt2 1050L
Sent from my YOGA Tablet 2-1050L using Tapatalk
anilkumar247 said:
Thanks for the tutorial.
I did all the steps as you said. I am at step 15 and selected t4 and then the command prompt showed waiting for device and then my tab rebooted itself and then came to a fastboot mode.
Now n TAB its showing error that "E: No valid installer medium found"
now when i press the volume keys, the boot option changes and then the error message changes to
"could not open /sys/devices/virtual/backlight"
Please help
Click to expand...
Click to collapse
Did u check that ADB/fastboot drivers installed correctly? Try to reinstall those drivers and check again. Did u select the UPDATE SuperSU zip file and install it?
AndroMAN said:
Did u check that ADB/fastboot drivers installed correctly? Try to reinstall those drivers and check again. Did u select the UPDATE SuperSU zip file and install it?
Click to expand...
Click to collapse
How can i make sure they are installed correctly ?
I have reinstalled them and tried again, but still getting the same error.
I am not getting the update Super SU option, or any options to get it installed.
@AndroMAN any idea why my 64gb sdcard is not recognized.
Sent from my YOGA Tablet 2-1050L using Tapatalk
anilkumar247 said:
How can i make sure they are installed correctly ?
I have reinstalled them and tried again, but still getting the same error.
I am not getting the update Super SU option, or any options to get it installed.
Click to expand...
Click to collapse
Step 8 and 9. Check under command prompt. It should show the name Baytrail***** when you type in the command "adb devices". Only then u can go ahead.
sajsaj7829 said:
@AndroMAN any idea why my 64gb sdcard is not recognized.
Sent from my YOGA Tablet 2-1050L using Tapatalk
Click to expand...
Click to collapse
Have you rooted your tablet? Was it detecting it earlier?
AndroMAN said:
Have you rooted your tablet? Was it detecting it earlier?
Click to expand...
Click to collapse
Hv rooted...Yes 32gb was working perfect but 64gb it says blank sdcard
Sent from my YOGA Tablet 2-1050L using Tapatalk
Hi
yes, its showing the device ID
prntscr.com/948uzk
prntscr.com/948ybk
I have blackened the device ID
sajsaj7829 said:
Thanks........ successfully rooted yt2 1050L
Sent from my YOGA Tablet 2-1050L using Tapatalk
Click to expand...
Click to collapse
Good? All the best and enjoy your rooted device. Have you installed Xposed Framework on it yet?
sajsaj7829 said:
Hv rooted...Yes 32gb was working perfect but 64gb it says blank sdcard
Sent from my YOGA Tablet 2-1050L using Tapatalk
Click to expand...
Click to collapse
Try formatting the new sd card via the tablet, even I have put a 64GB card and I had to format it before it could detect.
anilkumar247 said:
Hi
yes, its showing the device ID
prntscr.com/948uzk
prntscr.com/948ybk
I have blackened the device ID
Click to expand...
Click to collapse
Sorry to hear your facing issues. There are already people saying they have successfully rooted their device using this guide. So there must be some step u might have missed or done incorrectly.
Send me the details of your device, model of tablet, which Android version.
AndroMAN said:
Good? All the best and enjoy your rooted device. Have you installed Xposed Framework on it yet?
Click to expand...
Click to collapse
Thanks.. cld u please link me to ver of xposed working on yt2.
---------- Post added at 11:25 AM ---------- Previous post was at 11:21 AM ----------
AndroMAN said:
Try formatting the new sd card via the tablet, even I have put a 64GB card and I had to format it before it could detect.
Click to expand...
Click to collapse
@AndroMAN somebody hv made a exfat binary zip to be flashed via teetherd recovery.... any idea how to go into twrp recovery.
anilkumar247 said:
Hi
yes, its showing the device ID
prntscr.com/948uzk
prntscr.com/948ybk
I have blackened the device ID
Click to expand...
Click to collapse
AndroMAN said:
Sorry to hear your facing issues. There are already people saying they have successfully rooted their device using this guide. So there must be some step u might have missed or done incorrectly.
Send me the details of your device, model of tablet, which Android version.
Click to expand...
Click to collapse
Hey i think i have the solution for your problem because everytime i am facing the same issue
That means at first adb drivers are shown as installed correctly within the window of the 'Intel Fastboot Tethered Temporary Recovery Session Launcher' tool. But after my tablet reboots into fastboot via method t4 it always says "No valid installer medium found".
Note: I have these adb drivers installed http://forum.xda-developers.com/showthread.php?t=2588979
So here is my solution that works for me: (this is my first post so i cant provide any screenshots.. )
1. let the tablet stay within the fastboot mode
2. in windows: navigate to the device manager --> there you should see the symbol "android phone" with a yellow triangle
3. right click on this symbol and choose the first option "update drivers" (sry i don't know if i translated it correctly xD)
4. choose the option "search on pc .."
5. there you select the second option "choose from a list.."
6. within the list you select 'android device'
7. within the next list you select 'google nexus adb device'
8. after that the drivers are installing and the recovery starts on your tablet :fingers-crossed:
1subw00fer1 said:
Hey i think i have the solution for your problem because everytime i am facing the same issue
That means at first adb drivers are shown as installed correctly within the window of the 'Intel Fastboot Tethered Temporary Recovery Session Launcher' tool. But after my tablet reboots into fastboot via method t4 it always says "No valid installer medium found".
Note: I have these adb drivers installed http://forum.xda-developers.com/showthread.php?t=2588979
So here is my solution that works for me: (this is my first post so i cant provide any screenshots.. )
1. let the tablet stay within the fastboot mode
2. in windows: navigate to the device manager --> there you should see the symbol "android phone" with a yellow triangle
3. right click on this symbol and choose the first option "update drivers" (sry i don't know if i translated it correctly xD)
4. choose the option "search on pc .."
5. there you select the second option "choose from a list.."
6. within the list you select 'android device'
7. within the next list you select 'google nexus adb device'
8. after that the drivers are installing and the recovery starts on your tablet :fingers-crossed:
Click to expand...
Click to collapse
That might just work :fingers-crossed:
1subw00fer1 said:
Hey i think i have the solution for your problem because everytime i am facing the same issue
That means at first adb drivers are shown as installed correctly within the window of the 'Intel Fastboot Tethered Temporary Recovery Session Launcher' tool. But after my tablet reboots into fastboot via method t4 it always says "No valid installer medium found".
Note: I have these adb drivers installed http://forum.xda-developers.com/showthread.php?t=2588979
So here is my solution that works for me: (this is my first post so i cant provide any screenshots.. )
1. let the tablet stay within the fastboot mode
2. in windows: navigate to the device manager --> there you should see the symbol "android phone" with a yellow triangle
3. right click on this symbol and choose the first option "update drivers" (sry i don't know if i translated it correctly xD)
4. choose the option "search on pc .."
5. there you select the second option "choose from a list.."
6. within the list you select 'android device'
7. within the next list you select 'google nexus adb device'
8. after that the drivers are installing and the recovery starts on your tablet :fingers-crossed:
Click to expand...
Click to collapse
Hello
That worked
But instead of google nexus adb device in the list, i got only motorola ADB device, but still it worked .
Thanks to both of you for the help.
sajju73 said:
Thanks.. cld u please link me to ver of xposed working on yt2.
---------- Post added at 11:25 AM ---------- Previous post was at 11:21 AM ----------
@AndroMAN somebody hv made a exfat binary zip to be flashed via teetherd recovery.... any idea how to go into twrp recovery.
Click to expand...
Click to collapse
There is no working mode of Xposed on YT2 as far as I have seen. Still have to look into it.
Go to recovery the same way u did last time, through 'Intel fastboot launcher:
Congratulations @anilkumar247. I hope your device is rooted and working well. And thanks to @1subw00fer1 for helping out and contributing to this thread. Great work guys. All good ☺
Hi guys and girls...
I just recieved my new phone a few days ago. Plugged it into an old Windows 7 x64 laptop and Windows instantly updated the driver. On a 2016 Dell E7450 Windows 10 x64 laptop... It didn't. Tried the Google USB drver package, but it didn't work either. Windows reports about a problem with an INF file and doesn't finalize the driver install...
I just saw someone reported the same issue in Q/A. I thought it would be a good idea to write a step by step guide.
@ppd0526 proposed an easier solution to fix the issue:
Please if you use this solution, don't forget to say thanks to him in this post: THANKS
ppd0526 said:
I actually just helped a friend out with this. There is an easier fix then having to go through all that and add a known device.
1. Go to C:\Windows\INF
2. Find the file "wpdmtp.inf"
3. Right click the file and click 'Install'
4. Once that is done, simply plug your phone and it should work.
Click to expand...
Click to collapse
Uninstalled the driver and reinstalled using this method works fine! :good:
If someone has difficulty with the above or it doesn't work (which it should) i leave the one below just in case...
Click to show the guide:
Right click on the Windows start menu icon and select Device manager:
From here plug your Pixel using your USB cord to your computer. Pull the notification bar on your Pixel and tap on:
USB charging this device
Tap for more options
From the menu, select:
Transfet files
From here, you should see an "Unknown device" or an "MTP device" with an exclamation mark.
Right click on the device and select "Update driver software":
Click: "Browse my computer for driver software:
Click: Let me pick from a list of device drivers on my computer:
Scroll down till you find "LeMobile Android Device" and select it:
Here, select the second option: "MTP USB device"
Success
Now recognized in device manager:
In "This PC":
Hopefully, it will help some people.
Awesome, thanks! After several months with my phone, this just happened to me yesterday and I couldn't figure it out. The Google USB driver reinstall didn't work for me either, but this did!
As a suggestion, it's quicker to get to Device Manager by right clicking on the gear icon (Start) and selecting Device Manager.
JimSmith94 said:
Awesome, thanks! After several months with my phone, this just happened to me yesterday and I couldn't figure it out. The Google USB driver reinstall didn't work for me either, but this did!
As a suggestion, it's quicker to get to Device Manager by right clicking on the gear icon (Start) and selecting Device Manager.
Click to expand...
Click to collapse
Hooray... Thanks for the suggestion. I'm such a n00b when it comes to shortcuts... Edited to save the extra clicks.
5.1 said:
Hi guys and girls...
I just recieved my new phone a few days ago. Plugged it into an old Windows 7 x64 laptop and Windows instantly updated the driver. On a 2016 Dell E7450 Windows 10 x64 laptop... It didn't. Tried the Google USB drver package, but it didn't work either...
I just saw someone reported the same issue in Q/A. I thought it would be a good idea to write a step by step guide.
Click to show the guide below:
Right click on the Windows start menu icon and select Device manager:
From here plug your Pixel using your USB cord to your computer. Pull the notification bar on your Pixel and tap on:
USB charging this device
Tap for more options
From the menu, select:
Transfet files
From here, you should see an "Unknown device" or an "MTP device" with an exclamation mark.
Right click on the device and select "Update driver software":
Click: "Browse my computer for driver software:
Click: Let me pick from a list of device drivers on my computer:
Scroll down till you find "LeMobile Android Device" and select it:
Here, select the second option: "MTP USB device"
Success
Now recognized in device manager:
In "This PC":
Hopefully, it will help some people.
Click to expand...
Click to collapse
Wow, thanks so much. Couldn't figure this out. How did you?
bobby janow said:
Wow, thanks so much. Couldn't figure this out. How did you?
Click to expand...
Click to collapse
Hey... I once had a similar issue with a printer in the past and found this solution on the internet. So when it reappeared with the Pixel, I thought i would try as well. In the end it worked. That's all. I'm glad you sorted it out.
I actually just helped a friend out with this. There is an easier fix then having to go through all that and add a known device.
1. Go to C:\Windows\INF
2. Find the file "wpdmtp.inf"
3. Right click the file and click 'Install'
4. Once that is done, simply plug your phone and it should work.
ppd0526 said:
I actually just helped a friend out with this. There is an easier fix then having to go through all that and add a known device.
1. Go to C:\Windows\INF
2. Find the file "wpdmtp.inf"
3. Right click the file and click 'Install'
4. Once that is done, simply plug your phone and it should work.
Click to expand...
Click to collapse
Nice... Maybe you can open another thread? Or want me to add it to the OP?
Cheers...
5.1 said:
Nice... Maybe you can open another thread? Or want me to add it to the OP?
Cheers...
Click to expand...
Click to collapse
Adding it to the OP as an alternate method is fine. Better to keep the information consolidated.
ppd0526 said:
Adding it to the OP as an alternate method is fine. Better to keep the information consolidated.
Click to expand...
Click to collapse
Yeah you're right.
By the way, i just tried to uninstall my computer's driver and installed it with your method! Everything's alright.
Thank you...
My PC doesn't have this file wpdmtp.inf
Uninstalled the device and driver. Reconnected and let Windows update driver. Now it works.
Thank you Soo much. It worked exactly like it says in the OP.
This guide doesn't work anymore. MTP Device and MTP USB Device are no longer the menu options. Uninstalling the device doesn't work. You just end up with the exact same MTP with the exclamation point as before.
ppd0526 said:
I actually just helped a friend out with this. There is an easier fix then having to go through all that and add a known device.
1. Go to C:\Windows\INF
2. Find the file "wpdmtp.inf"
3. Right click the file and click 'Install'
4. Once that is done, simply plug your phone and it should work.
Click to expand...
Click to collapse
Yes! This works! WooHoo.... just had to uninstall all previous drivers first at the device manager.
Thanks, this worked!
ppd0526 said:
I actually just helped a friend out with this. There is an easier fix then having to go through all that and add a known device.
1. Go to C:\Windows\INF
2. Find the file "wpdmtp.inf"
3. Right click the file and click 'Install'
4. Once that is done, simply plug your phone and it should work.
Click to expand...
Click to collapse
Thank you sooo much :victory:, I actually didn't have the wpdmtp.inf in C:\Windows\Inf but I had this folder (link) containing a couple of android drivers and there was wpdmtp.inf file in it, I right clicked and installed it and VOILLAA!!... :laugh: everything went perfect after that. If for any reason you still face MTP problems after this I would recommend to do a manual installation of MTP drivers by going to "Device Manager", click MTP entry with exclamation then "Update Driver Software"->"Browse my computer for driver", navigate to the folder location where you extracted the drivers (link).... you should be done after that. If otherwise you face a problem along the lines of "section in this INF is invalid" while doing manual installation dreboot your PC and find the wpdmtp.inf again, right click then install and you would have fixed your problem. :good:
THANKS!
Oh man! Finally, FREAKING FINALLY, I found a solution that works. Thank u so so so much.
Thank you! This tip worked for me!
I have been having this issue for almost a year, if I wanted pictures and files from my phone, I had to get them from the cloud. Today was the first time in a very long time, that I was able to just copy over files from the phone again from Windows Explorer. THANK YOU!
trying these methods is still failing for me... shows "Pixel" in device manager.. if I try to update drive.. it says either can't find.. or failed...
and if i turn on Transfer Files.. Device manager shows ADB and MTP under "Other" but both fail when trying to update drivers..
YES!!!
5.1 said:
Hi guys and girls...
I just recieved my new phone a few days ago. Plugged it into an old Windows 7 x64 laptop and Windows instantly updated the driver. On a 2016 Dell E7450 Windows 10 x64 laptop... It didn't. Tried the Google USB drver package, but it didn't work either. Windows reports about a problem with an INF file and doesn't finalize the driver install...
I just saw someone reported the same issue in Q/A. I thought it would be a good idea to write a step by step guide.
@ppd0526 proposed an easier solution to fix the issue:
Please if you use this solution, don't forget to say thanks to him in this post: THANKS
Uninstalled the driver and reinstalled using this method works fine! :good:
If someone has difficulty with the above or it doesn't work (which it should) i leave the one below just in case...
Click to show the guide:
Right click on the Windows start menu icon and select Device manager:
From here plug your Pixel using your USB cord to your computer. Pull the notification bar on your Pixel and tap on:
USB charging this device
Tap for more options
From the menu, select:
Transfet files
From here, you should see an "Unknown device" or an "MTP device" with an exclamation mark.
Right click on the device and select "Update driver software":
Click: "Browse my computer for driver software:
Click: Let me pick from a list of device drivers on my computer:
Scroll down till you find "LeMobile Android Device" and select it:
Here, select the second option: "MTP USB device"
Success
Now recognized in device manager:
In "This PC":
Hopefully, it will help some people.
Click to expand...
Click to collapse
WOW, Dude you ROCK!! I have been struggling with this for well over 6 months but just pulled my Pixel back off the shelf for Android PIE and have been determined to find this fix.
Again, thank you very much!!!!!!!
Ki11ian said:
WOW, Dude you ROCK!! I have been struggling with this for well over 6 months but just pulled my Pixel back off the shelf for Android PIE and have been determined to find this fix.
Again, thank you very much!!!!!!!
Click to expand...
Click to collapse
Haha, better late than never... :good:
Cheers...