Hi guys.
Im a newbie here inb the forums and new to the world of modifying android (i was an apple user for a long time).
My problem here is that i am trying to install a custom ROM and to do that i have to unlock the boot loader.
>>Downloaded the SDK and drivers that came with it via instruction provided thru SE lin for unlocking boot loader
>>Connected device and the blue led turned on
upon plugging in the phone, device manager popped out of this error >> Unknown USB Device (Device Failed Enumeration)
>>tried updating the driver automatically and manually by directing it to the usb_driver folder inside SDK but to no success
>>done uninstalling and reinstall, done disabling and re-enabling still same error
>>tried all the USB ports in my desktop and still the same
>>checked properties of the driver and here are the details
Device USB\VID_0000&PID_0000\5&21f49dea&0&4 had a problem starting.
Driver Name: usb.inf
Class Guid: {36FC9E60-C465-11CF-8056-444553540000}
Service:
Lower Filters:
Upper Filters:
Problem: 0x2B
Status: 0x0
>>I've already tried searching thru XDA forums but most of the solutions ive seen are outdated.
>>By the way, I am using Windows 8.1 64bit / Phone is SE Xperia Arc S
I would really appreciate it if you could help me here.TIA
Have you tried following instructions from both of the following threads:
http://forum.xda-developers.com/showthread.php?t=1034087
http://forum.xda-developers.com/showthread.php?t=1794800 - I believe this is what you are using?
jay_r95 said:
Have you tried following instructions from both of the following threads:
http://forum.xda-developers.com/showthread.php?t=1034087
http://forum.xda-developers.com/showthread.php?t=1794800 - I believe this is what you are using?
Click to expand...
Click to collapse
Hi!
Thank you for this reply. I will try this post later and will get back to you with the results.
Have a good Day!
trekker04 said:
Hi!
Thank you for this reply. I will try this post later and will get back to you with the results.
Have a good Day!
Click to expand...
Click to collapse
This is the exact issue I have with my Nexus 4. Were you able to figure this out? TIA.
just4ivaylo said:
This is the exact issue I have with my Nexus 4. Were you able to figure this out? TIA.
Click to expand...
Click to collapse
Sorry, it took time for me to reply. I was never able to figure it out. The threads provided were not helpful at all though thanks to all whomtried to help. i gave up with it and sold it. Currently using S2.
Related
I have a problem. I just got my Android a couple of days ago and I really badly want to root it. I've tried multiple different programs and with each one the problem I get is "Waiting for device" in the cmd/terminal (Tried on multiple platforms: Vista, Win7, Ubuntu). I've tried installing drivers too and still didn't work (maybe the wrong drivers?).
Yes I realize that I am a "noob", but I really need some help here.
Got USB Debugging enabled ??
Got the correct upto date drivers ?
You navigated to the right location in ADB ??
azzledazzle said:
Got USB Debugging enabled ??
Got the correct upto date drivers ?
You navigated to the right location in ADB ??
Click to expand...
Click to collapse
>Yes
>I think so, not positive.
> What do you mean?
bumpp someone help?
Well Redownload the drivers and see if that helps, You could try Hasoon2000's All In One Kit to help with this. http://forum.xda-developers.com/showthread.php?t=1604677
As for ADB, (Android Debug Bridge) you should have this already, You need it to get unlock the bootloader and flash superboot (root) http://forum.xda-developers.com/showthread.php?t=1583427
Be sure to check out those links and also look at my FAQ section http://forum.xda-developers.com/showpost.php?p=24884624&postcount=3
I have all the files that it says are necessary to unlock the bootloader. It's just when I type "fastboot oem get_identifier_token" it just sits there saying "waiting for device".
I've tried hansoon's all in one program as well and it didn't work either.
Well that means it cannot find your phone, So the issue lies with the drivers and/or the location from which the command prompt is opened..
Put all of the files into 1 folder called android or adb and move that 1 folder to the root of your C Drive..
This should make navigating easier. Also, In that folder should be adb.exe and fastboot.exe do you have these ?
I fixed this by just playing around with it a bit more. Thanks for the help, though.
infam0us me said:
I fixed this by just playing around with it a bit more. Thanks for the help, though.
Click to expand...
Click to collapse
what exactly did you do? I am stuck with this problem for a long time now. nothing seems to help. what does "playing around" mean?
windows 8.1
htc one s (c2)
morphication said:
what exactly did you do? I am stuck with this problem for a long time now. nothing seems to help. what does "playing around" mean?
windows 8.1
htc one s (c2)
Click to expand...
Click to collapse
Well man, I really wish I could help you out because I remember how frustrating this was for me. This post was 2 and a half years ago though. Just really make sure that your drivers are up to date. If I could remember my exact solution I would help you out for sure.
infam0us me said:
Well man, I really wish I could help you out because I remember how frustrating this was for me. This post was 2 and a half years ago though. Just really make sure that your drivers are up to date. If I could remember my exact solution I would help you out for sure.
Click to expand...
Click to collapse
ok. it was windows 8 not allowing unsigned drivers to install properly. note: not "not installing at all", but "not installing properly". meaning: htc drivers installed somehow, so I was able to see the device and copy files around, but it was not enough for flashing roms.
so I started this guide to disable driver signature:
https://www.youtube.com/watch?v=gmw86KplqmU
... but my laptop is a business laptop and this guide demands BitLocker key if hard drive is encrypted (mine is). I also have a windows 7 desktop machine. So I decided to go the easy and quick way of simply doing flashing on my desktop computer. Windows 7 worked like a charm. But I'm sure the guide above would've helped as well. If somebody tries that, please post results.
This has been a fiasco... Ive been attempting to Root, Unlock Bootloader, Install CWM, and Flash to HD Custom rom that is now out for this device. Ive found two tutorials on how exactly to do this and one video. The one originally posted on this forum by Superdragonpt has been modified by this forum and there no longer is any useful information or files available (after sifting over 120 pages in that thread) then there is another one posted on Android Forums here (http://androidforums.com/memo-pad-h...ad-hd7-us-backup-restore-unlock-recovery.html) using SP Flash Tool. However he clearly states that he was only capable of doing this walk-through on Windows XP and had limited success on Windows 7. As I am running windows 7 this creates an issue... There is also attempted to follow the YouTube instructions posted here (https://www.youtube.com/watch?v=yuNFx10cS2U) however the OP of that doesnt respond to his numerous requests stating that "App Not Installed" error upon attempting to install.
I delved even deeper to find the root of my Windows 7 errors. When using the SP Flash Tool Ive read that the battery needs to be fully charged and vcom drivers need to be installed. Well ok, I've installed over 20 different drivers from aproximatly 7-8 different threads on the SP Flash Tool, the battery is fully charged and there doesnt seem to be any conclusive resolution to any of this. The device seems to cycle between modes when you plug it into the PC full battery or not and the SPFT begins the process and stops the second the device cycles modes...
After all this research and work itd be great if someone could jump in here...
Berrabus said:
This has been a fiasco... Ive been attempting to Root, Unlock Bootloader, Install CWM, and Flash to HD Custom rom that is now out for this device. Ive found two tutorials on how exactly to do this and one video. The one originally posted on this forum by Superdragonpt has been modified by this forum and there no longer is any useful information or files available (after sifting over 120 pages in that thread) then there is another one posted on Android Forums here (http://androidforums.com/memo-pad-h...ad-hd7-us-backup-restore-unlock-recovery.html) using SP Flash Tool. However he clearly states that he was only capable of doing this walk-through on Windows XP and had limited success on Windows 7. As I am running windows 7 this creates an issue... There is also attempted to follow the YouTube instructions posted here (https://www.youtube.com/watch?v=yuNFx10cS2U) however the OP of that doesnt respond to his numerous requests stating that "App Not Installed" error upon attempting to install.
I delved even deeper to find the root of my Windows 7 errors. When using the SP Flash Tool Ive read that the battery needs to be fully charged and vcom drivers need to be installed. Well ok, I've installed over 20 different drivers from aproximatly 7-8 different threads on the SP Flash Tool, the battery is fully charged and there doesnt seem to be any conclusive resolution to any of this. The device seems to cycle between modes when you plug it into the PC full battery or not and the SPFT begins the process and stops the second the device cycles modes...
After all this research and work itd be great if someone could jump in here...
Click to expand...
Click to collapse
The forum your link leads to is down atm so I couldn't check it out. However, in the meantime, why don't you try booting Windows XP in a virtual machine, and give it a go there?
pokrajac said:
The forum your link leads to is down atm so I couldn't check it out. However, in the meantime, why don't you try booting Windows XP in a virtual machine, and give it a go there?
Click to expand...
Click to collapse
And virtually load drivers? Because thats where the issue is that Windows 7 only recognizes the driver for a brief 3-5 second window...
Berrabus said:
And virtually load drivers? Because thats where the issue is that Windows 7 only recognizes the driver for a brief 3-5 second window...
Click to expand...
Click to collapse
Yeah, you install drivers on the virtual OS and it should get detected.
pokrajac said:
Yeah, you install drivers on the virtual OS and it should get detected.
Click to expand...
Click to collapse
Ill give that a **** once I get my me173x out of its eternal boot loop. Im under the impression I need to download the stock ROM image and throw that on a SD card and attempt to do a restore... Hope it works
Berrabus said:
Ill give that a **** once I get my me173x out of its eternal boot loop. Im under the impression I need to download the stock ROM image and throw that on a SD card and attempt to do a restore... Hope it works
Click to expand...
Click to collapse
Well that would be the proper course of action if you can get to CWM yes. Just don't forget to do a clean install, wipe data and cache.
pokrajac said:
Well that would be the proper course of action if you can get to CWM yes. Just don't forget to do a clean install, wipe data and cache.
Click to expand...
Click to collapse
Unfortunately CWM is not even installed at this point... I didnt get that far as I was attempting to unlock the bootloader when this happened
Berrabus said:
Unfortunately CWM is not even installed at this point... I didnt get that far as I was attempting to unlock the bootloader when this happened
Click to expand...
Click to collapse
Well, if the drivers on a virtual xp aren't working and you don't want to set up a dual boot with xp, then your only option is to send it to a service center.
pokrajac said:
Well, if the drivers on a virtual xp aren't working and you don't want to set up a dual boot with xp, then your only option is to send it to a service center.
Click to expand...
Click to collapse
Nabbed the tablet for 15 dollars with cracked digitizer at that point if I cant repair it myself then Id say cut my losses and have a pretty paperweight lol... I actually located a Windows XP machine and will be heading to get it seems that their a bit of a rarity these days
Hello, I bought my shield a while back, rooted in KitKat just to get my backup data from apps from my previous device transferred and then happily ungraded to Lollipop with the intention to stay unrooted since it means unlocking the bootloader which may void my warranty. Recently I came upon an app named Helium which I knew nothing about and which seems to be able to backup app data even without root, but to use the no-root version you need to have ADB drivers installed. I found a bunch of sets of ADB drivers, like for example this http://developer.download.nvidia.com/mobile/shield/SHIELDTablet_WHQL_USB_driver.zip but nowhere real instructions explaining how to install them in a Windows 7 PC. I've searched all over the place with no luck so help would be greatly appreciated. I installed drivers for my older device about 3 years ago so I've done it before but I can't remember a thing about it, even if it was a similar method that I had followed.
Thanks in advance, hope someone replies. Help a fellow keep his data backed up please!
Hey there, man.
First of all, neither rooting or unlocking bootloader will void your wartranty, unless the installation you made after that, break the whole tablet in pieces. For example, if you happened to install Windows 8 and it burns.
As for ADB, just read this thread: http://forum.xda-developers.com/showthread.php?t=2317790
Good luck.
YuriPan said:
Hello, I bought my shield a while back, rooted in KitKat just to get my backup data from apps from my previous device transferred and then happily ungraded to Lollipop with the intention to stay unrooted since it means unlocking the bootloader which may void my warranty. Recently I came upon an app named Helium which I knew nothing about and which seems to be able to backup app data even without root, but to use the no-root version you need to have ADB drivers installed. I found a bunch of sets of ADB drivers, like for example this http://developer.download.nvidia.com/mobile/shield/SHIELDTablet_WHQL_USB_driver.zip but nowhere real instructions explaining how to install them in a Windows 7 PC. I've searched all over the place with no luck so help would be greatly appreciated. I installed drivers for my older device about 3 years ago so I've done it before but I can't remember a thing about it, even if it was a similar method that I had followed.
Thanks in advance, hope someone replies. Help a fellow keep his data backed up please!
Click to expand...
Click to collapse
When I'm faced with a .zip file, the first thing I do is to unzip it and look at the contents. If there's an installer in there, I just double-click on it ... Sorry if this sounds very basic, but it might not occur to everyone =)
If there's not an installer, you'll probably have to install those drivers through Device Manager. Good luck =)
CM17X said:
Hey there, man.
First of all, neither rooting or unlocking bootloader will void your wartranty, unless the installation you made after that, break the whole tablet in pieces. For example, if you happened to install Windows 8 and it burns.
As for ADB, just read this thread: http://forum.xda-developers.com/showthread.php?t=2317790
Good luck.
Click to expand...
Click to collapse
Oh I see. Then I might actually root it but since I have to unlock the bootloader and it will wipe my device I definitely need to make this no-root backup work first >.<
I opened the link. The instructions are just to install the exe? I did but my pc still thinks I have no drivers installed... *sigh* Any ideas?
Ok, I figured it out, I installed via Device Manager after all, I was using a bad set of drivers, apparently some file was missing from them so the DM didn't recognize it as drivers... ugh, such confusion for such a silly little thing! Thank you for your help!
amartolos said:
When I'm faced with a .zip file, the first thing I do is to unzip it and look at the contents. If there's an installer in there, I just double-click on it ... Sorry if this sounds very basic, but it might not occur to everyone =)
If there's not an installer, you'll probably have to install those drivers through Device Manager. Good luck =)
Click to expand...
Click to collapse
I tried unziping it. Dunno what I'm supposed to do next. There's no exe's in there, there are 2 files that are considered "Security Catalog", 2 are "Setup Information" and there's 2 folders and each contains 3 files that are "Application exension"
I'd like to try installing them through Device Manager but... how do I do that?
Ok, ignore whatever I wrote before, I figured it out. Looks like I was using a bad package of adb drivers. The funny thing is, the link I posted above is the one that worked but the one I was trying to install was a different one! I suppose I got confused after finding more than one set of instructions! >.<
Hey everyone -
The title says it all! Reading, searching, and experimenting for hours... no dice. Time to ask for help.
I'm trying to unlock the bootloader of my Shield Tablet, but no matter what I do, I can't install the Universal Naked Driver (which I understand to be step #1). I've tried to troubleshoot this to no avail (including turning off driver signature verification, etc.)... Windows 10 refuses to do it, complaining that "Windows was unable to install your Shield Tablet. Windows could no find driver software for your device".
I'm posting this question *here*, because it makes me wonder if something has changed in the last firmware update from Nvidia (I'm running the very latest - LMY48C.35398_567.2193)... so here's my question: has anyone out there tried to root (which requires bootloader unlock) a Shield Tablet with this firmware? If you've been successful, could you point me toward a tutorial I haven't yet read? Thank you!
I think your first issue would be installing the wrong drivers. Install the actual nVidia Shield Family drivers from the gameworks download centre. Next, make sure to try a few different adb versions. Not all of them are identical, and you might have better results with one but not another.
Good luck!
amartolos said:
I think your first issue would be installing the wrong drivers. Install the actual nVidia Shield Family drivers from the gameworks download centre. Next, make sure to try a few different adb versions. Not all of them are identical, and you might have better results with one but not another.
Good luck!
Click to expand...
Click to collapse
You just fixed me up with this piece of advice!
Really appreciate it... thanks for taking the time.
Great! Glad it worked
Hello!
Well, i just got my hands on a Moto X 2014, already updated to Android MM 6.0.
Was trying to install TWRP through fastboot, but i keep getting this message:
"FAILED <data transfer failure <Unknown error>>"
I'm sure i have sdk tools properly installed, drivers downloaded, fastboot mode on the device working properly as well, and an unlocked device... So, i'm kinda new at this, and i'd appreciate your help very much!
Thanks!
AJValle said:
Hello!
Well, i just got my hands on a Moto X 2014, already updated to Android MM 6.0.
Was trying to install TWRP through fastboot, but i keep getting this message:
"FAILED <data transfer failure <Unknown error>>"
I'm sure i have sdk tools properly installed, drivers downloaded, fastboot mode on the device working properly as well, and an unlocked device... So, i'm kinda new at this, and i'd appreciate your help very much!
Thanks!
Click to expand...
Click to collapse
Hello,
What OS are you using? USB 3.0?
A similar issue for a different device is addressed here.
-Vatsal
Vatsal said:
Hello,
What OS are you using? USB 3.0?
A similar issue for a different device is addressed here.
-Vatsal
Click to expand...
Click to collapse
I'm using a 2.0 USB port on a Windows 7 ultimate 32 bits. Thank you so much for your reply, I checked the thread, and I'll try using another of the 2.0 USB. The SDK tools are updated tho
Well, after a couple days i managed to install TWRP 3.0. I don't specifically know what was the problem, but i freed up some space on the device, changed USB cable and USB port on the computer, and.. that did the trick.
Thank you so much for your replies!