Related
Hero had a hardware fault w/ the SD slot(good thing too! I dropped it last week and had a bit of rub on the top left that was bothering the hell out of me)
Was going to go get it replaced tonight, but for some damn reason the RUU won't work.
I have the latest RUU(1.56?)
Tried with phone w/ and without USB debugging
Went into fastboot mode(which made W7 install drivers for Android 1.0?) yet the RUU still won't recognize the phone.
I'm not computer illiterate, I'm just having problems with this damn RUU.
Halp?
What's the error you're getting?
The RUU basically says like
"Finding your Android Device" for about 30 seconds then says it cannot find it.
error 170...
ahh we meet again
i've helped a few people through this but i don't want to spoil the fun..
read this
all the way through it has the steps needed to get you up and going.
what os are you running?
just read windows 7..
try right clicking and "run as administrator"
thedudejdog said:
error 170...
ahh we meet again
i've helped a few people through this but i don't want to spoil the fun..
read this
all the way through it has the steps needed to get you up and going.
what os are you running?
just read windows 7..
try right clicking and "run as administrator"
Click to expand...
Click to collapse
I've read this before, I got it from geekfor.me
My windows 7 has the real administrator account enabled, running as administrator won't do anything.
intx said:
I've read this before, I got it from geekfor.me
My windows 7 has the real administrator account enabled, running as administrator won't do anything.
Click to expand...
Click to collapse
ok.
basically my next question is do you want my help or not?
i know how to make it work for you, at least three other people have gotten it to run by following my directions.
thedudejdog said:
ok.
basically my next question is do you want my help or not?
i know how to make it work for you, at least three other people have gotten it to run by following my directions.
Click to expand...
Click to collapse
Why wouldn't I want help?
ok try this.
type "adb devices"
if that sees your phone type reboot into fastboot then type "fastboot devices"
if that sees your phone then run the ruu
adb devices sees it.
boot into fastboot, fastboot devices sees it.
run the RUU, error 170 still >_<
intx said:
adb devices sees it.
boot into fastboot, fastboot devices sees it.
run the RUU, error 170 still >_<
Click to expand...
Click to collapse
have you tried this?
realmrealm said:
For some of the people running into problems with Windows 7 you may want to try:
1. Right-click on the executable file "ARUWizard.exe" and then go to "properties"
2. I believe there is a tab called "Compatibility" or something, click on it.
3. there should be a place for you to click next to a "run this program in compatibility mode" put a check there
4. below that there should be a drop down box, try choosing "Windows XP SP3" (or something similar to that)
5. near the bottom should be a place to check "run as administrator" check that.
6. click "ok" and then try running the program again.
I'm in front of a windows xp computer right now, not windows 7, so excuse me if i don't remember the options correctly, but I should be pretty close.
I also don't even know if this will work, but it's definitely worth a shot.
-AndyS-
Click to expand...
Click to collapse
or this?
10 char...
flipzmode said:
Possible resolutions would be:
1) Putting it in to fast boot and trying it again. Check your error log if it fails and seeing if it identified your phone this time.
2) Open a command prompt and "cd" to the folder where your \sdk\tools\ folder and type in "adb devices" and hit enter and see if it sees your phone. If not then that's your problem. If it DOES see your phone then enter the following command
3) adb shell reboot oem-78 -- that will reboot your phone in to RUU-ready fastboot. If you had the RUU still open then close it. Then open it and try running again.
Click to expand...
Click to collapse
or this?
crunchybutternut said:
Just had a thought.. after updating my HTC Sync software the adb included with my RUU might be out of date. I copied adb.exe, AdbWinApi.dll and fastboot.exe from C:\AndroidSDK\Tools and overwrote the files in the RUU folder. Then I ran it without a hitch.. weird, eh?
Click to expand...
Click to collapse
Tried the first two things, neither helped
I figured out part of the problem though. I had to dig up some 64 bit drivers.
I got the RUU to recognize my phone and it sends it to the bootloader and gets stuck on Waiting for bootloader then errors 170 out.
I'll try copying the files over now.
Replacing those 3 files did the trick!
Thanks
intx said:
Replacing those 3 files did the trick!
Thanks
Click to expand...
Click to collapse
no problem, when i did it i tried all of those steps at once, so i wasn't sure which one fixed it for me. so now (in theory) it should work for you on that machine every time.
wont run and get "ARUGlobal.dll can not be found" even tho im looking right at it....
Hi guys.
Sorry for this noobish post, but i cannot remember for the life of me on how to install things by using 'adb' - i know there is an option on the phone, but where bouce is it? I used it when rooting, but i just cant find it.
I'm trying to install a new boot image, but when i go into cmd i type "adb remount" and the reply is "device not found"... AndroidSDK is in my C directory.
Another EDIT; I just rebooted my device into the recoverymode, and i didn't see ndroid back up thing, does that mean my phone hasn't actually been rooted... - But my phone is deffently debranded.
Thanks if anyone can help my noobish style.
Slim.
When in recovery mode you must have the driver installed. If you enter 'adb devices' it should give you the serial number of your device, if the driver is installed correctly.
To enter the recovery menu you must run the recovery-windows.bat from modaco if using windows or a similiar file (recovery-linux.sh, recovery-mac.sh) according to your operating system. The file should be run when in recovery-mode or else it returns a whole bunch of errors.
Awesome, thanks mate. Just what i needed! Could i have advice what driver i need to be able to acsess the adb?
I just use the driver supplied in the newest version of ADB.
You can get it here. usb_driver.rar
Or else just install HTC Sync from htc.com. It also has the driver files needed.
Remember to have USB Debuging enabled from the Programs/Development menu.
in cmd
fastboot devices (shows my serial) but when I try to fastboot flash recovery recovery-clockwork-herring.img it keeps saying error: device not found and I cant for the life of me figure out what's wrong. I have tweeted a few people with no luck...
Try this
shug24 said:
in cmd
fastboot devices (shows my serial) but when I try to fastboot flash recovery recovery-clockwork-herring.img it keeps saying error: device not found and I cant for the life of me figure out what's wrong. I have tweeted a few people with no luck...
Click to expand...
Click to collapse
Try resetting your phone and your computer then try again
like a reboot? that hasn't helped yet...
yeah exactly- hmmm try re-installing the drivers
where can I find the samsung drivers and I am trying to do that again now.. but I am not sure what drivers you are talking about specifically.
shug24 said:
where can I find the samsung drivers and I am trying to do that again now.. but I am not sure what drivers you are talking about specifically.
Click to expand...
Click to collapse
you have to get the drivers through android sdk
(with phone usb connected)
device manager
Android Device
right click
update drivers
click browse my computer then next and then click install
if it doesnt give you that option let me know
okay I am having problems there. First, it doesn't recognize an android device, it says unknown device and it won't take any drivers I have followed the pdanet steps, and I have tried the galaxy s drivers with no luck...
okay there is your problem now we are getting somewhere,
do you have android sdk
if yes do you know how to install packages
I have tried this on two 64bit machines and one x86 the one I am on now.. and can't get it to work. I feel like a total newb but this is not a new thing to me ( rooting/unlocking etc) I have had a g1 since the release, then a nexus one since release and just got the nexus s yesterday and have struggled with this one..
what do you mean by install packages, and I appreciate your help
okay no problem it took me a bit to figure it out too.....there arent samsung drivers for this phone they come straight from google through android sdk. im assuming you have it and im going to assume its in this directory if you did eveything right with your n1
c:/androidsdk
in the directory there is a file called SDK setup.exe open it
once it opens do yourself a favor and click cancel dont ask why just do it
now thats out of the way there is 5 options on the left pane of the android sdk window click settings.
then at the bottom of that window is a box under misc. by force http..make sure its checked
then on the left pane goto then available packages
click them all to save yourself trouble and then on the bottom right install packages
let me know when thats done
doing it now - not sure if this helps or not but I had done this last night on a different pc - unfortunately that is at home and I am on my work laptop right now.
and... done.
okay now go back into the device manager and right click on unknown device
update/re-install/install whichever it says then when it asks search or browse
BROWSE
c:/androidsdk/googleusb driver
and watch the magic happen
okay a few things: first it says e: now for the phone under portable devices second, there is no google usb drivers, so I tried it just under the AndroidSDK folder and all the following and it said:
The best driver software for your device is already installed. WPD Filesystem Volume Driver
thoughts?
go back to the sdk setup.exe expand the boxes under available packages and read me what you see
is this where you are asking me to display from? http://www.twitpic.com/3gwnus
OR here: http://www.twitpic.com/3gwo9i
let me save you the trouble
unzip cut and paste to your androidsdk folder
http://www.multiupload.com/Y3T61793BP
yes and paste the file i sent you into that folder
now it still says the best driver is already installed...
uninstall your phone
ive tried doing the tutorial at http://forum.xda-developers.com/showthread.php?t=1622425 but to no avail have got it to work i keep getting stuck at step 5 where im checking my sbk number but whenever i type the commands into cmd it says nvflaSH is not recognized as an internal or external command, operable program or batch file??? sorry cant figure it out i have all the acer drives installed and all files needed any help would be appreciated
gears177 said:
ive tried doing the tutorial at http://forum.xda-developers.com/showthread.php?t=1622425 but to no avail have got it to work i keep getting stuck at step 5 where im checking my sbk number but whenever i type the commands into cmd it says nvflaSH is not recognized as an internal or external command, operable program or batch file??? sorry cant figure it out i have all the acer drives installed and all files needed any help would be appreciated
Click to expand...
Click to collapse
Sounds like either you're not in the correct directory with your CMD window, or you didn't extract the files properly. Try extracting them again to a folder on your c: then open a cmd window there. Nvflash is really a simple app. Also, make sure you are in apx mode. Should see a icon in windows task bar, or you can check device manager.
A little tip, do search for cmd.exe on your pc, and then copy it to the folder where you would like to use it. Much easier than cd (change directory) or any other way that I know short of adding it to your right click menu. I keep a copy of it on my desktop so I can copy/paste it anywhere that I need it.
Make sure you installed the Acer drivers. At first I didn't b/c I had working ADB. You need those Acer drivers for the APX driver in there. I wasted an hour or two on that one!
strongergravity said:
Make sure you installed the Acer drivers. At first I didn't b/c I had working ADB. You need those Acer drivers for the APX driver in there. I wasted an hour or two on that one!
Click to expand...
Click to collapse
I've tried that even tried a reinstall I'm pretty sure I'm typing in the commands wrong or when it says open cmd on V6-Unlocked-ICS-HC-bootloader-MULTI-CWM folder I'm not sure does that mean just open up cmd and input that directory and then the commands or what?
gears177 said:
I've tried that even tried a reinstall I'm pretty sure I'm typing in the commands wrong or when it says open cmd on V6-Unlocked-ICS-HC-bootloader-MULTI-CWM folder I'm not sure does that mean just open up cmd and input that directory and then the commands or what?
Click to expand...
Click to collapse
Connect tablet to pc, make sure you are in apx mode , open the folder V6-unlocked.......... and click on the .bat that you want to run. It should start , no need to open cmd on the folder .
I got stuck but in different way altogether.
if you don't mind going back to 3.2.1 for a few minutes then I suggest doing that. it also installed CWM to which you can install your chosen ROM.
then after this you could just use blackthunders apx tool to flash your chosen bootloader.
I know your problem is totally different to mine and looks like you are just not in the right directory while trying to use nvflash but the way I suggest was very easy and works.
I cant post links right now but if you look in the thread for unlocking bootloader then I posted a link which should help you do it this way. its on page 47.
hope u get it sorted I spent many hours yesterday always getting stuck at various points but after many hours found an easier way.
cheers
tigermrk said:
I got stuck but in different way altogether.
if you don't mind going back to 3.2.1 for a few minutes then I suggest doing that. it also installed CWM to which you can install your chosen ROM.
then after this you could just use blackthunders apx tool to flash your chosen bootloader.
I know your problem is totally different to mine and looks like you are just not in the right directory while trying to use nvflash but the way I suggest was very easy and works.
I cant post links right now but if you look in the thread for unlocking bootloader then I posted a link which should help you do it this way. its on page 47.
hope u get it sorted I spent many hours yesterday always getting stuck at various points but after many hours found an easier way.
cheers
Click to expand...
Click to collapse
Sweet I'll try civatos way then if that doesn't work I'll give it a shot I'm still on honeycomb boot loader so why not ;-) thnx again for the help......how does black thunders tool work sorry for incompetence I thought I knew about tech :'( any help would be appreciated
its basically GUI program which installs a bootloader of your choice in a few clicks.
of course u dont need the ICS bootloader if you were to choose to install FLEXREAPER rom after going through my method.
just install it by the recovery menu after going back to 3.2.1.
cheers
EDIT: If your already on the honeycomb bootlaoder (just noticed) you should be able to do it pretty easy and civatos way will work fine
Dug up this old threaad because i didnt feel the need to create a new one and still never solved this :/ no matter what i do it seems i get stuck at entering downoad mode it enters apx mode fine but wont enter download mode im on ics locked bootloader and have tried uninstall reinstall of drivers multiple times also tried switching pc's. Is there any preferred os to do this on? and does 64 bit vs 32bit matter?
Edit.....nevermind guys tried on a whole different comp and worked fine
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 ☺