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,
Related
I have a serious problem with my LG G2 D802 which I could not solve: I used the new LG Flash Tool 2014 , everything was going just fine till I received an error recovery failed, I disconnected the USB cable by mistake from my G2 and afterward I saw that it was in the middle of flashing process (49% was completed). I turned it off and tried to reach download mode again and nothing!, I'm receiving the "LG" logo and nothing- the screen goes black (it is still on).
I tried also to connect my phone to the computer- I received a list of 13 "new" local disks "H" to "T", only "H" disk is available and it's showing "image" folder with list of files.
I cannot reach "download mode", nothing is working!
I hope anyone can help me.
Itried pressing power and volume button down together and aa lot more don't know how to slove.
@sandeep1421 Hi, you can still fix your phone using this guide: http://forum.xda-developers.com/showthread.php?t=2582142
But, Read everything carefully, Download the right files for your phone and do everything good, if not then you could hardbrick your phone if you forgot/didnt flashed an file.
So goodluck :good:
P.S. Ubuntu is recommended for this guide.
195
well thanks i will try this method , i really hope i can fix my phone.
I just want to ask, actually i am using LG G2 D802, which is international version, so hope these files are for my phone. How to stop the pop up "unable to mount..." error messages , in ubuntu.
You have the answer in the OP :
priority3 said:
Excellent tutorial! Thank you! Phone is working again
You can stop the "unable to mount..." error messages from popping up by disabling
the automount feature of Ubuntu.
"To enable or disable automount open a terminal and type dconf-editor followed by the [Enter] key.
Browse to org.gnome.desktop.media-handling."
Click to expand...
Click to collapse
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.
I was trying to flash CM11 ROM in my Samsung Galaxy Ace GT-S5830, for that I have also installed CWM 6.0.5.3. While flashing ROM from recovery it failed with some error message, I tried it once again and again it stopped with the same error message. I decided to try some other ROM and kept mobile on side to search new rom, the mobile was still in recovery mode connected with usb for charging, after a minute as I saw at my mobile it was not in recovery mode, the screen was OFF. I tried to restart it again & again but failed, I even tried to start it in recovery mode but failed. Tried overnight charging, thinking that its battery is down, but failed to restart it. Then I searched about it on google, and came to know it was bricked with solution to flash it with stock rom using Odin, if it is still getting detected in PC. My PC is still detecting my mobile, tried flashing stock rom using Odin, but it is getting stuck at "< 1 >setup connection...". I don't know what to do now. My mobile is not in warranty, so no way in getting it repaired from service center. If anyone know any solution for this, then please tell me. I am eagerly waiting for your reply. Moderators, please don't delete this thread saying to go and search for same kind of threads, I have already done that & at last posted in new thread. Please Help me as soon as possible. Thanks..
http://download1187.mediafire.com/eew353b6p3sg/y2yja47mu5ew4g5/samsung+Galaxy-Ace+gt-s5830.rar
Extract it, open "S5830_Odin+Multi+Downloader+v4.38.exe" then in the OPS section select the .ops file in the extracted folder, then give a check on "One package" check box. Then on the bottom press the "One package" button and select the firmware in the folder and you're done !
P.S. If that doesn't work, try reinstalling Samsung USB Drivers, removing Kies, switching cables, ports or even PC's (if possible)
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.
Hey guys,
im sorry if the topic doesnt fit here. I am new and not a techi. My Son just tried to flash some custom ROM on our Samsung Tab A and somehow bricked it. It is not possible for me to get into Recovery or Download Mode i have already tried all Button-Combinations. It just shows an error saying "An error has occured while updating the device software. Use the Emergency recovery function in the Smart Switch PC software."
I have already tried with draining the Baterry empty (described in forum thread here: https://forum.xda-developers.com/showthread.php?t=1478361) and plug it in to get the Charging symbol. But it doesnt happen. It just shows only the Error..
So i really dont have any more ideas how to get into recovery/download mode.. Is there anything i didnt tried??
It seems like the download-mode is not available. Is there a way to "install" a new one??
edit: it seems like this IS the download-mode.. anyways i think i just need the stock firmware for this model T510NZKDDBT. I cant find it via duckduck/google..
Maybe someone can help me with it?
Thank you
nevermind!! i've figured it out. Flashed new bootloader via Odin. Now its working again
Thread can be closed!
arbmos said:
nevermind!! i've figured it out. Flashed new bootloader via Odin. Now its working again
Thread can be closed!
Click to expand...
Click to collapse
hey bud can you help me out here? I am having the same issue you were. How do I flash a new bootloader into the device?
Pucc0 said:
hey bud can you help me out here?
Click to expand...
Click to collapse
I know I'm a year late, and you've either figured this out or moved on, but maybe I can clear this up for anyone else in the same situation.
I stuffed up and got the same message - "An error has occured while updating the device software. Use the Emergency recovery function in the Smart Switch PC software."
That error message screen is basically the download screen. Windows (and the Smart Switch software) won't connect to the tablet while that screen is displayed, but Odin will.
You can bring up Odin and re-flash the stock software (or whatever you need) while that message is displayed. If you still have trouble, holding power and down-volume will re-initialise the download screen, though it will still display the same "emergency recovery function" error message.
I hope that's enough of a description to get people out of trouble!