Related
Purchased a gtablet, all went smooth after I installed the TNT Rom, but found some sound issues, and found out that seemed to plague a lot of other people, so decided to try another ROM - can't even recall which one now. But now where I'm stuck at is if I hold down vol up and power, I get "Recovery key detected Booting recovery kernel image" and it sits there forever. Even if I take out the microsd card, I get the same screen. A normal power attempt sits forever at the Viewsonic "birds" screen. I've tried just about every rom, none take . I'm pretty sure I had the clockwork recoverymod installed, but now I can't even get into that.
I tried volume down + power, (ATP mode?) but none of the drivers I've found are for Windows 7 64 bit, so I can't access the tablet in that mode because the lack of drivers.
Any suggestions on what to do from here?
Thanks!
http://forum.xda-developers.com/showthread.php?t=989320&highlight=nvflash+windows
Good Luck
http://forum.xda-developers.com/showpost.php?p=9302497&postcount=5
Bottom of instructions section -- a few users have written posts on nvflash for windows.
LGCubana said:
http://forum.xda-developers.com/showthread.php?t=989320&highlight=nvflash+windows
Good Luck
Click to expand...
Click to collapse
Hi,
Thanks for the link.. I think I've seen that - I don't see a APX driver missing in Device Manager - there is a ADB Interface, however when I let that install drivers, it says the Device cannot start - Code 10.
I may have another computer I can boot up and try
phirephoto,
I wrote the USB post and used the files there to NVFlash in APX mode. I know the info there is accurate.
I also have found, however, that if you install the whole SDK kit instead of the files in my post, it installs ADB. I don't know much about ADB but I know it basically works about the same.
If you have the APX driver it says it is the nVidia USB driver in Device Manager. So I am assuming you have installed SDK.
I can only suggest you make sure what files are installed on your PC and what method you are using and then research this site. I know several people have used the ADB methods and posted about them.
Good luck.
Rev
If you have another computer -- try the method reobeet posted along with the Advent Vega USB files. I know that has worked.
butchconner said:
phirephoto,
I wrote the USB post and used the files there to NVFlash in APX mode. I know the info there is accurate.
I also have found, however, that if you install the whole SDK kit instead of the files in my post, it installs ADB. I don't know much about ADB but I know it basically works about the same.
If you have the APX driver it says it is the nVidia USB driver in Device Manager. So I am assuming you have installed SDK.
I can only suggest you make sure what files are installed on your PC and what method you are using and then research this site. I know several people have used the ADB methods and posted about them.
Good luck.
Rev
If you have another computer -- try the method reobeet posted along with the Advent Vega USB files. I know that has worked.
Click to expand...
Click to collapse
It did work on my old POS XP Laptop I knew that thing was useful for something!
Thanks again.. Never thought I'd be so happy to see "TapnTap" again. And now I'm up and running on the Vegan rom
Hi everyone, first, this is my first post, new to the forums, at least as a registered user. I have a problem with my phone. I know most of you are wondering why I have not just read the other posts on the forums, but I have. I have attempted every solution to the problem posted previously.
Background: Phone: Samsung charge.
I was being impatient and did not want to wait for the gingerbread update form Verizon. I flashed the leaked gingerbread 2.3.4 onto my phone using odin. Everything went great. I was able to use my phone with no problems except shortened battery life, but nothing major. About a month ago the battery life was impossible to maintain and there were some software bugs, like clicks during calls, startup taking forever, around 2 minutes on average!, and random restarts that never happened before. I decided to look up some fixes and found that verizon and samsung had released GB 2.3.6 for the charge. I got excited and decided I wanted to get that, but I could not via OTA. I read some forum posts and they mentioned attempting a factory reset on the phone then trying OTA update. I went ahead with factory reset and everything went fine. My startup time is around 25 seconds now and no random clicks or gliches, but still not on 2.3.6, which was the whole point. I then decided to just flash the stock 2.3.6 rom to the phone.
Problem: When I plug my phone in to multiple computers it will charge but not connect to the computer. This means on my Mac it does not show as an external drive, which it has in the past. On my windows 7 machine it says that drivers were installed but could not be used (I can get the exact quote if needed.) I attempted to go into device manager and solve problem that way but it shows my phone as "unknown device". I have tried to enter download mode when hooked up to windows computers and no connection is found.
Possible solutions attempted and their outcomes:
1. As stated, I attempted the method shown in a thread on droid forums for installing the samsung drivers. I have attempted multiple times to install the drivers on my windows machine and the device remains "unknown".
2. I have attempted multiple cables on multiple computers, both mac and windows 7. No change.
3. I have installed adb and attempted to locate devices using adb devices command on mac. No devices found.
4. I have attempted all methods with both usb debugging checked and unchecked.
5. I have tried every possible usb port I have.
Ideas/questions I have had that I have no idea are possible or how to fix!
Would a factory reset take away the ability to connect to a computer from my phone. So, is there a piece of software in the build I have that controls the connection between the computer and the phone, an identifier of sorts, which is now missing, now that I have reset the leaked ROM.
Is there a way to flash a new ROM without connecting to a computer, via the sd card, and what is that? I have read some things in other posts but am too much of a n00b to understand most of them when using sdcards.
ANY help will be greatly appreciated. PLEASE PLEASE PLEASE!!! I have been at this for at least 6 hours, sifting through forums, searching google, attempting fixes that others have stated worked for them, only to fail every time. Thank you all.
i've had a few issues with this on my Droid Pro. with windows connection a connection assistant came up with some options that I was able to get it to work as a drive.
Getting it to work with adb is another issue alone. The phone needs to be in "debug" mode. I would search for a tutorial on this because you need to edit files on the computer.
for example on my windows I needed to edit one set of files, while on my linux I had to edit another set of things.
I leave my phone in debug mode because i use it for my android app dev on both computers. try that and see if it shows up on your mac.
So I'm trying to fix a Xoom for a client. Her nephew was using it over Thanksgiving weekend and has managed to mess it up.
1) On a normal boot it never gets past the boot animation. The animation just loops and loops.
2) I was able to get into recovery and do a factory reset, but that didn't improve anything.
3) I can get to "Starting Fastboot protocol support" or "Starting RSD protocol support 0"
4) I have used two different moto drivers on Win 7 and Win 8, but neither computer ever recognizes the xoom is connected regardless of mode
5) Adb never sees the xoom either.
6) This device should have been completely stock, but no one knows what this kid did with this tablet.
7) USB debugging was probably off since the owner would not have known about it or had a reason to turn it on.
What are my options here? I'm thinking that I need to flash a good factory image, but I need to get some communication going first.
Update: I've been trying different cables. I found one where the computers will see that a devices is connected, but am getting "USB device not recognized" with either set of drivers that I have on both computers. Making progress, but could still use some help.
DiGi760 said:
So I'm trying to fix a Xoom for a client. Her nephew was using it over Thanksgiving weekend and has managed to mess it up.
1) On a normal boot it never gets past the boot animation. The animation just loops and loops.
2) I was able to get into recovery and do a factory reset, but that didn't improve anything.
3) I can get to "Starting Fastboot protocol support" or "Starting RSD protocol support 0"
4) I have used two different moto drivers on Win 7 and Win 8, but neither computer ever recognizes the xoom is connected regardless of mode
5) Adb never sees the xoom either.
6) This device should have been completely stock, but no one knows what this kid did with this tablet.
7) USB debugging was probably off since the owner would not have known about it or had a reason to turn it on.
What are my options here? I'm thinking that I need to flash a good factory image, but I need to get some communication going first.
Click to expand...
Click to collapse
I had a problem similar to that about a year ago, somewhere in these forums was the suggestion to remove the SD card and then do a factory reset, it worked for me. My xoom just stopped working, I thought at first it was a flat battery but after charging the symptoms were the same as yours, might be worth searching through the forums if you haven't already
There's no sd card in it, just the little plastic place holder. I've been looking all over the forums, but I normally deal with Samsungs. I've been figuring out Motorola's little quirks as I go along. Is there a recommended moto driver for these things?
DiGi760 said:
There's no sd card in it, just the little plastic place holder. I've been looking all over the forums, but I normally deal with Samsungs. I've been figuring out Motorola's little quirks as I go along. Is there a recommended moto driver for these things?
Click to expand...
Click to collapse
Sorry can't help , mine is just over 2 years old and except for that one problem have never had any issues so have never needed to even connect it to a PC
DiGi760 said:
There's no sd card in it, just the little plastic place holder. I've been looking all over the forums, but I normally deal with Samsungs. I've been figuring out Motorola's little quirks as I go along. Is there a recommended moto driver for these things?
Click to expand...
Click to collapse
I recently discovered these handy files when I needed to return to stock:
4G Xoom (MZ600) Restore
3G Xoom (MZ601/3) Restore
WiFi Xoom (MZ604) Restore
If you need to find out which Xoom model it is, power on whilst holding the volume down button, this will take you in to fastboot. Then (you sound like you'd know how do this, PM me if you don't) use "fastboot getvar all". This will return the model.
Unzip the file above, there's a batch file in there which will install the drivers, then fastboot the firmware over.
If you boot to fastboot, then run the batch file, it installs the drivers, then "adb device", then it asks if your device is connected - it won't show up cos it's in fastboot. Just ignore that and say yes, and it'll start flashing the files.
Sorry if I'm too late - don't visit these boards much these days. Good luck, let me know if this works.
Thanks for giving me something to try. I uninstalled the moto drivers I had and installed the ones included in the zip file and restarted my computers. The Windows 8 computer never recognizes that the xoom is connected in any mode. The 7 machine does see it in fastboot mode but as a "fastboot" device for which it fails to find drivers. When I run fastboot getvar all, all I get is <waiting for device>.
I do know that this is a wifi only (mz604) xoom. Thanks for the image files. If I can get this stupid thing to communicate with a computer, I think I'll be in business.
In fastboot mode (vol -) it won't acknowledge that it's connected. Just fastboot your image over and it will work.
If I try to do anything with fastboot, it just says "< waiting for device >". Fastboot doesn't see a device to flash to.
OK, it's either your cable or your driver. Many cables are for charging only, and have no data lines. I throw those away.
As to drivers, I'm Debian for 15 years so can't advise on Winduhs.
Oh, one more thing: I've noticed that on my old HP laptop I had to use a certain USB port, or else it wouldn't comm with my phone for fundamental actions like loading new firmware.
These were the drivers I used: https://motorola-global-portal.cust...sion/L3RpbWUvMTM4NjM1MjA0NC9zaWQvWEo3SWU5SGw=
They don't seem to be windows 8 certified though.
Sent from my Nexus 5 using Tapatalk
We finally got it. We used DriverEasy to look for drivers because we have a bunch of extra licenses and the drivers we had obviously weren't working. DriverEasy was able to install an "Android Bootloader" driver that must not be part of the SDK. Once that was installed, I was able to use fastboot to flash the images from above. The device is in good working order again and fully updated.
Thanks for all your help.
Always nice to hit the Thanks button for those who've helped.
Hi all,
I am have bricked my device, its in fastboot mode but wont do anything anymore.
Ive tried literally everything possible, ive read numerous manuals, seen tons of video tutorials but nothing works.
The main issue I am facing now is that MSMDownloader tool does not recognize my phone because of an Driver issue.
However, whatever I am doing I cant get the correct driver to function on my Windows 10 machine.
Whatever I do, it either does not recognize the device, or shows it as Kedacom USB Device / Android Bootloader Interface.
I have manually removed the drivers from the device manager as well as removing them manually with pnputils, it does remove the driver and then shows it as Android Device.
If i then scan the folders (whole windows is in testing mode like many manuals tell me to) it just wont install the driver and if i do that manually using pnputils it changes nothing.
The only moment it changes is when I connect to the internet and search for a driver and the old samer driver will be installed.
I have tried the OnePlus driver installer, I have tried the All In One tool, I tried the Qualcomm QDLoader HS USB Driver, I tried it totally disconnected, i rechecked if i was running cmd and the msmdownload tool as administrator, i have rebooted and updated my pc, rebooted and tried again.
I am pretty sure its an driver issue, but apparently whatever I do i cant seem to be able to fix it, and another way of fixing this phone is probably not gonna work as whatever I do with the volume, power buttons, how many times i reboot i just keep getting the same Fastboot/Download screen.
Does anyone have any other idea, am i missing something? I really have no idea. I have followed several manuals step by step, googled and found people with similar issues tried those solutions, i am now busy for like over 12 hours and am really getting the idea that i cant fix it
This can be closed, I have used the info from this thread:
https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
It helped me revive my phone without having to deal with the USB issues and MSMDownloader.
schorrie said:
This can be closed, I have used the info from this thread:
https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
It helped me revive my phone without having to deal with the USB issues and MSMDownloader.
Click to expand...
Click to collapse
THREAD CLOSED on request of OP!
So Ive just bought a brand new U12+, and obviously the very first thing I did was attempt to root it.
Main hiccup Im running into here is that my PC wont recognize the phone while its in recovery or fastboot/download mode.
If I had to guess, I think it's a driver issue, problem is I've been searching for hours now and cannot find the proper drivers for it to be recognized. (I've also tried every USB port on my PC, both 2.0 and 3.0.)
Ive tried using HTC sync, uninstalling it and leaving that driver, Ive tried letting windows auto install the driver, and I tried a generic android USB driver, none of which have seemed to work.
PC will recognize the phone while it's fully booted to OS, and I can even command it to reboot into recovery from there, but once its in recovery I lose connection.
Not sure how much of a difference this makes, but I bought a factory unlocked phone, still sealed, with all the plastic and accessories inside the box. But when I boot into download I get the message "Security checking failed DENY", this is only supposed to show up after the bootloader has been unlocked isn't it?
Anyways, if someone could point me in the right direction for these drivers it'd be greatly appreciated.
chaosrde said:
So Ive just bought a brand new U12+, and obviously the very first thing I did was attempt to root it.
Main hiccup Im running into here is that my PC wont recognize the phone while its in recovery or fastboot/download mode.
If I had to guess, I think it's a driver issue, problem is I've been searching for hours now and cannot find the proper drivers for it to be recognized. (I've also tried every USB port on my PC, both 2.0 and 3.0.)
Ive tried using HTC sync, uninstalling it and leaving that driver, Ive tried letting windows auto install the driver, and I tried a generic android USB driver, none of which have seemed to work.
PC will recognize the phone while it's fully booted to OS, and I can even command it to reboot into recovery from there, but once its in recovery I lose connection.
Not sure how much of a difference this makes, but I bought a factory unlocked phone, still sealed, with all the plastic and accessories inside the box. But when I boot into download I get the message "Security checking failed DENY", this is only supposed to show up after the bootloader has been unlocked isn't it?
Anyways, if someone could point me in the right direction for these drivers it'd be greatly appreciated.
Click to expand...
Click to collapse
Strange suggestion but try a different pc. My phone isnt recognised when I try to install magisk on my phone on my home pc but it works on my work pc.
I got about 9 different USB ports on my home PC and none work
Also download platform-tools_r29.0.2-windows for fastboot etc.
While you're in troubleshooting mode, try another USB cable. I had issues running fastboot commands and the like when using a generic USB cable, but it worked fine using an OEM one. Can't hurt to rule that out too.
Icculus760 said:
While you're in troubleshooting mode, try another USB cable. I had issues running fastboot commands and the like when using a generic USB cable, but it worked fine using an OEM one. Can't hurt to rule that out too.
Click to expand...
Click to collapse
I am using the OEM cable, straight out the box. I'm gonna try meddling with it again when I get home and see if I can get it working.
bigAL99 said:
Also download platform-tools_r29.0.2-windows for fastboot etc.
Click to expand...
Click to collapse
Ive done a fair bit of searching but I can't find anywhere to download older version of platform tools, I have the current build 29.0.5.