Hello, a year back I had a problem of hardware in my tab, after restoring the hard ware the service center person installed a mobile version of OS.
the tab was ok but when I tried to install a system update, while install I got a error and from then the tab never starts it stuck at the X symbol.
I have tried to reboot the device by doing boot cache clear option, not worked.
I tried by using the adb as well the I am getting the message Verification failed.
As I am not able to use my tab I could not set the USB debug mode.
Can any one please help me in the above issue.
I've heard of a problem with the flash component becoming corrupt after so long. It could be that but did you try fastboot commands on your computer to see if it shows the device?
Sent from my Nexus 6 using Tapatalk
Hello ZionFreak,
Thanks for your response, yes I have tried with adb devices command which don't show any device, I have downloaded the Nexus tool kit, when I tried to unlock the device it says that no device is recognized. Please help me in solving this issue.
Related
Dear XDA Geniuses,
I have a 16gb Nexus 7 WI-Fi. I was using Nexus 7 toolkit 2.0.0 to try and flash my nexus 7 back to the the stock google rom (option 9 in the toolkit.) It seems as if it wiped out cyanogen mod 10, which i had been using, as well as clockwork recovery. My nexus 7 now boot up with the google logo and the unlocked padlock on the bootom. using the volume rocker i can select the bootloader option and get an android figure with his chest open.
this is the only option i can select. my attempts have been:
1)connect it to computer. Windows 7 and Windows 8 will not recognize it, nor let me access it from the command line.
2. Use nexus 7 toolkit, which DOES recognize it in fastboot mode, to flash a new recovery on there. it says that a command failed, and won't let it write to it.
3) install adb and android sdk tools. my tablet won't show up under devices, and I am not sure if it is still in usb debugging mode. command line will not recognize it as an adb device and will not control tablet.
when i looked at this thread it was dealing with a locked bootloader, while mine is unlocked. it also wanted command line operations from the computer, which does not seem to work for me.
i was attempting to do something like this (laptop mag blog how to hard reset a bricked nexus 7) but without my nexus 7 showing up under devices I am not sure what my options are.
TLDR: Nexus 7 16gb WIFI only boots into boot recovery. Using nexus 7 toolkit to recognize as fastboot. otherwise will not show up on computer. no recovery, no boot image.
Thank you for reading.
I went back and reread the thread on flashing and restoring nexus 7 to stock in this forum, but every command I try returns " command write failed invalid argument ". Using android sdk manager i can get it to recognize the device in fastboot mode. my drivers there seem to be working.
edit: I got all the way to flashing the bootloader, but it returned "no such device or address. "
JerryMc88 said:
I went back and reread the thread on flashing and restoring nexus 7 to stock in this forum, but every command I try returns " command write failed invalid argument ". Using android sdk manager i can get it to recognize the device in fastboot mode. my drivers there seem to be working.
edit: I got all the way to flashing the bootloader, but it returned "no such device or address. "
Click to expand...
Click to collapse
latest progress can be found at imgur slash TAikq
now it is say data transfer failure - too many links. 146.84 seconds.
it was my cable. the cable mounted it in fastboot mode, but would not allow writing. switched out the cable, and we are up and running again. thanks!
Um.... Glad we could help?
Sent from my Nexus 7 using xda app-developers app
Sticky?
Man, I would love to see this sticky posted, or at least a list of errors and fixes stickied. I have been looking for an answer to the same issue for two days. Finding out it was just a lousy cable really really really pissed me off... I'm glad someone figured it out and actually posted their solution, most of these wind up with nothing.
OMG, I've tried to flash my N7 with a new lollipop 5.1 today and got the same issue as described here http://forum.xda-developers.com/showthread.php?t=2724273 then, after 5 or 6 hours of thinking what is going on, I finally found this very old thread and guess what? Changing this sh***ty cable I was using solved the problem.
Use USB ports on the back of your computer, not the front.
I have a Nexus 7 2012 (KOT49H, nakasi) which will only boot into fastboot, but not to Android.
I don't know what caused this - when it happened first I rebooted, and it worked again for another couple of days, then I got a "Google Play Services has stopped" message, so I tried to power off and reboot the tablet.... and it won't reboot!
At that time I was unaware that such a thing as USB debugging existed, so it's not been set... Indeed all I know about these problems now is what I've found out here... so sorry if I test your patience!
What I have done:-
I have tried a factory reset, with no effect.
Tried Wug's toolkit, which was unable to do anything (as USB debugging not set?)
(Windows 7 appears to have the drivers for this - it appears in Device Manager as Google Nexus 7 Bootloader interface)
Tried Skipsoft's Toolkit, which succeeded in unlocking the bootloader, and I have flashed images (downloaded from google) for Boot and System to the appropriate partitions... still nothing! Flashing the bootloader image failed ("An error occurred")
Is this Nexus destined for the dustbin? It is, of course, out of warranty :crying:
Apologies if I've done something daft, but I'm getting desperate...
Can anybody help?
Many thanks
hEY,
i got the same. I tried to install cm11 and i format sd card and happens that i formated the system too.
Now i can only to restart in revory "cwm v6.0.5.0" but cant start in download modus with Power+down (see only GOOGLE LOGO with open lock sign).
With wugs fresh i got the same with the f**** usb debugging enable thing, i cant get into nothing only in cwm.
I would be sooo happy to find a tool like (adb-tool) how i can put files again on my nexus 7.
thank you guys in advance!
beaquoy said:
I have a Nexus 7 2012 (KOT49H, nakasi) which will only boot into fastboot, but not to Android.
I don't know what caused this - when it happened first I rebooted, and it worked again for another couple of days, then I got a "Google Play Services has stopped" message, so I tried to power off and reboot the tablet.... and it won't reboot!
At that time I was unaware that such a thing as USB debugging existed, so it's not been set... Indeed all I know about these problems now is what I've found out here... so sorry if I test your patience!
What I have done:-
I have tried a factory reset, with no effect.
Tried Wug's toolkit, which was unable to do anything (as USB debugging not set?)
(Windows 7 appears to have the drivers for this - it appears in Device Manager as Google Nexus 7 Bootloader interface)
Tried Skipsoft's Toolkit, which succeeded in unlocking the bootloader, and I have flashed images (downloaded from google) for Boot and System to the appropriate partitions... still nothing! Flashing the bootloader image failed ("An error occurred")
Is this Nexus destined for the dustbin? It is, of course, out of warranty :crying:
Apologies if I've done something daft, but I'm getting desperate...
Can anybody help?
Many thanks
Click to expand...
Click to collapse
smoschi said:
I would be sooo happy to find a tool like (adb-tool) how i can put files again on my nexus 7.
Click to expand...
Click to collapse
If you have wugs, you already have the adb tool on your computer. Look in the wugs directory. However it sounds like your drivers are messed up. If that is the case nothing is going to work until you get that corrected.
I had non rooted Kitkat 4.4.4 installed on N10. I received update intimation to Lollipop hence downloaded the update. While installing, message regarding error came followed with message "No command" . Now nothing is done further. Even tablet is not getting power off. Periodically screen displaying Google is coming followed with message "No command" I just checked. I can enter in to download and recovery. I now downloaded also Lollipop update for manual updating.
While connecting to PC, it starts searching for driver and after sometime message flashed "Driver not installed successfully" might be due to non detection of MTP. In such case if I try to maually install then ADB also is not recognising the connected device.
Can you suggest how best I can revive N10?
Regards,
Contnuing further, my main problen now is how to make my device visible in computer. I tried to install universal driver/ pda net driver etc. but no success. I feel unless this is done, I can not even use recovery options.
Kindly guide me. I keeps on wasting time on futile excercises.
Regards,
I got the same error last night - went straight for the wugs tool kit - problem is now solved
trriley5 said:
I got the same error last night - went straight for the wugs tool kit - problem is now solved
Click to expand...
Click to collapse
What did you do with the tool kit? Use it to install drivers or what? I've tried it and it does nothing for me except give suggestions on how to install drivers.
I've got ADB &SDK installed on my PC that works with my HTC One M8, so I imagine the drivers should work with my Nexus 10, don't you think?
Sent from my HTC6525LVW using XDA Free mobile app
I Have this problem also. I forgot that I had unlocked the Nexus 10, and let the OTA update install. It failed. I cannot get WUGs to talk to the tablet. If I let it boot I get "No Command"
If I go into Download Mode??? "Power + Sound Up" I get Start and an Robot laying down, says Downloading... but WUGs is never able to talk to it.
Atul Kaji said:
I had non rooted Kitkat 4.4.4 installed on N10. I received update intimation to Lollipop hence downloaded the update. While installing, message regarding error came followed with message "No command" . Now nothing is done further. Even tablet is not getting power off. Periodically screen displaying Google is coming followed with message "No command" I just checked. I can enter in to download and recovery. I now downloaded also Lollipop update for manual updating.
While connecting to PC, it starts searching for driver and after sometime message flashed "Driver not installed successfully" might be due to non detection of MTP. In such case if I try to maually install then ADB also is not recognising the connected device.
Can you suggest how best I can revive N10?
Regards,
Click to expand...
Click to collapse
please refer to my post from another thread regarding the fix for your nexus 10, I also encountered the same problem with you guys.. Below is the link. Thank you. :good:
http://forum.xda-developers.com/showpost.php?p=57001773&postcount=134
Thanks. Problem is solved now. Your guide is perfect.
Regards,
Model: LGMS5500, Lg Stylo 2 Plus (MetroPCS), Android Marshmallow 6.0.1
Here's my issue.
I recently rooted/installed TWRP for this phone, all was working well until one day the system started running extremely slow.
Pulling down the notification bar took about five seconds; it took about the same amount of time to turn the screen on/off.
I searched everywhere for fixes and tried every one to no avail, so I figured I'd do a factory reset.
After trying the factory reset from the settings app; all the phone did was reboot.
So I went into TWRP and reset/cleared data from there.
Now when the phone starts, it brings me to a screen saying "Encryption unsuccessful" and only gives me the option to reset my phone.
When I press this button, it just reboots to the same screen>
I can't get into TWRP because before all of this happened, I disabled USB debugging.
So I can't use my PC to get into recovery.
There's also no way to boot to recovery with just the hardware buttons; the only way to get to TWRP with this phone is either from apps on the phone itself or using ADB.
Am I S.O.L here? Am I going to need to buy a new phone? I'd rather not have to drop another $175 because of something this dumb.
Any help is greatly appreciated.
Run commands fastboot erase userdata
If problems try holding volume down wile phone off and plug in USB to pc..had simular problem and worked for me
supertwin33 said:
Run commands fastboot erase userdata
If problems try holding volume down wile phone off and plug in USB to pc..had simular problem and worked for me
Click to expand...
Click to collapse
That's the thing, even if I do that, on the PC it's stuck on < waiting for any device >
Bump, please halp
Try reinstalling lg drivers .i had to do that. Use the lg tools and don't have phone plugged when you install them. Then try again to clear data prompts. How it helps
Sent from my LGMS550 using XDA Free mobile app
supertwin33 said:
Try reinstalling lg drivers .i had to do that. Use the lg tools and don't have phone plugged when you install them. Then try again to clear data prompts. How it helps
Sent from my LGMS550 using XDA Free mobile app
Click to expand...
Click to collapse
Thank you so much! I reinstalled the drivers and was able to get the phone working again through fastboot, much appreciated
Same ISSUE!
Hi will you please explain all the steps you've gone through to fix the issue? I have my friend's Phone with me it's LG Stylus 2. I have literally the same issue that you've been through. I've tried all possible ways but still I'm unable to Fix it. I've tried LGUP tool that gives Model error. LG Flash tool 2014 which is unable to detect my phone since I've already Installed LG stylus 2 Drivers. Really need Help please reply. :crying:
Hello,
I have a Nexus 6P stuck during boot on the white google logo. Apparently it happened during an update to N.
I have attempted a few solutions I have found either on xda or on other pages but the gist of what I’ve attempted so far is thus:
I have tried to reflash android stock after obtaining it from google : https://developers.google.com/android/images (MTC19T) but the oem option was unchecked so “fastboot flashing unlock” returns with an error.
I have tried to apply an OTA update, again I obtained the file from google (MTC19T) , via the recovery > apply update from adb . But it fails. The error from the phone is:
Code:
E: failed to verify whole file signature
E: signature verification failed
And on the pc side I believe that the failure comes from the fact that my pc has never been connected to the phone via ADB, so it’s unrecognized.
- I have also tried to bypass the adb pc signature issue by connecting a usb flashdrive to my phone via a usb-c adapter but the mount /sdcard command doesn’t work.
I’ve tried a few more esoteric solutions, like booting into Emergency Download (EDL) but my phone just boots into the google logo and stays there.
A few informations on my device (according to the fastboot/recovery screen)
Code:
BL: angler-03.51
Baseband: angler-03.61
Product/Variant: ANGLER-ROW-WN1
6.0.1/MTC19T/2741993
Current Build Number: MTC19T
So, to summarize: Fastboot is locked and won’t work, ADB is unrecognized and using a usb drive pretending to be an sdcard doesn’t work and I’m working with a stock recovery.
I'm looking for a way to bypass the fastbook lock or the adb verification. Or (even better) for anyone here to tell me that I've been going the wrong way all this time and that the solutions involves three easy steps...
Thank you!
Hipstronaute said:
Hello, I have a Nexus 6P stuck during boot on the white google logo. Apparently it happened during an update to N.....I'm looking for a way to bypass the fastbook lock or the adb verification. Or (even better) for anyone here to tell me that I've been going the wrong way all this time and that the solutions involves three easy steps...
Click to expand...
Click to collapse
Try again but you have to use an OTA that is newer than MTC19T. You still may be able to sideload when recovery is in ADB Sideload mode. There is no way to unlock your bootloader. Make sure you are using a recent, known working copy of ADB/Fastboot. The problem many people can't overcome is that they never set up ADB before or used it on a few occasions, so now the phone is dead they can't get it set up correctly. When the phone is connected in recovery>>ADB sideload update, what returns when you run "adb devices"? Do you have another phone you can use to confirm your ADB/fastboot setup is installed correctly?
Download the Nexus toolkit and then boot into recovery and select on the toolkit "softbrick" , good luck. Private message if you need any help
Sent from my Nexus 6P using Tapatalk
Hi,
Thank you for your answers.
@v12xke For the OTA after trying MTC19T I downloaded and tried half a dozen images from Google. Previous versions, next version of marshmallow, a few of the nougat versions. The results were exactly the same.
As for adb I just updated my Android studio, and it's not the first time I've used these tools. The process of sideloading the zip always stops at 47% but I can see that adb and the recovery are communicating.
Fastboot devices also detects my device, but I don't have my computer on me right now.
@DavidSantos I already tried the toolkit but it just launched my phone on the Google logo and got stuck there.
Hipstronaute said:
Hi,
Thank you for your answers.
@v12xke For the OTA after trying MTC19T I downloaded and tried half a dozen images from Google. Previous versions, next version of marshmallow, a few of the nougat versions. The results were exactly the same.
As for adb I just updated my Android studio, and it's not the first time I've used these tools. The process of sideloading the zip always stops at 47% but I can see that adb and the recovery are communicating.
Fastboot devices also detects my device, but I don't have my computer on me right now.
@DavidSantos I already tried the toolkit but it just launched my phone on the Google logo and got stuck there.
Click to expand...
Click to collapse
You have turn off your phone , press volume up and power key , then a menu will pop up , then plug in your phone with your PC
Sent from my Nexus 6P using Tapatalk
DavidSantos said:
Download the Nexus toolkit and then boot into recovery and select on the toolkit "softbrick" , good luck. Private message if you need any help
Click to expand...
Click to collapse
Best way to brick your phone if you don't know what kind of softbrick this tool has been made for... :good:
You have turn off your phone , press volume up and power key
Click to expand...
Click to collapse
Yes, I did that. The soft just makes my nexus reboot to the Google logo.
@v12xke: Looks like there are also more and more of those bootloader + recovery access bootloop. With sideload OTA fails...
@Hipstronaute: I have already seen one or two users with the same kind of problem and if I remember, nothing fixed the problem.
Good luck...
Might be a special edition Nexus 6P , oh well. Mine had the same problem and it worked just fine
Sent from my Nexus 6P using Tapatalk
5.1 said:
@v12xke: Looks like there are also more and more of those bootloader + recovery access bootloop. With sideload OTA fails...
@Hipstronaute: I have already seen one or two users with the same kind of problem and if I remember, nothing fixed the problem.
Good luck...
Click to expand...
Click to collapse
That's too bad. Sounds like the storage memory going bad and the write process is interrupted when it hits that area. Thing is, I've heard the same OTA write failure occurring several times at 47%. Wonder what that means? Anyway sounds like @Hipstronaute is looking at a replacement phone, under warranty or otherwise.
@v12xke
Anyway sounds like @Hipstronaute is looking at a replacement phone, under warranty or otherwise.
Click to expand...
Click to collapse
Gosh do I hope that won't be the last post on this topic.