So I dropped my phone and shattered the screen a few days ago. Just today a section of the screen failed that prevented me from unlocking the device with my pattern. Like an idiot, I kept trying to obtain the pattern unlock, but ultimately failed and now the phone is forcing me to unlock it by signing into the Google account associated with the phone. Unfortunately that only works if you have a Wifi or data connection, which I DON'T have because I had it in Airplane mode when the digitizer died.
So what are my options here? The phone DOES have an unlocked bootloader, as I loaded the Mexican ROM a while back to replace the stock U.S. one. When I boot up to Fastboot mode, it says unlocked status 3, and I can successfully see the device by using the "fastmode devices" mode. However, I cannot access the device via ADB because I didn't have USB debugging turned on.
I'm not all that familiar with Android recovery options and would just like to see if I can get into my device without having to wipe it. Ideally all I want to do is either:
A.) Somehow turn on Wifi so I can unlock the device by signing into google (I can connect a keyboard up to the phone to type in my credentials)
B.) Somehow turn on USB debugging so I can use ADB to then clear the password or turn on wifi, etc
Help!
Farfolomew said:
So I dropped my phone and shattered the screen a few days ago. Just today a section of the screen failed that prevented me from unlocking the device with my pattern. Like an idiot, I kept trying to obtain the pattern unlock, but ultimately failed and now the phone is forcing me to unlock it by signing into the Google account associated with the phone. Unfortunately that only works if you have a Wifi or data connection, which I DON'T have because I had it in Airplane mode when the digitizer died.
So what are my options here? The phone DOES have an unlocked bootloader, as I loaded the Mexican ROM a while back to replace the stock U.S. one. When I boot up to Fastboot mode, it says unlocked status 3, and I can successfully see the device by using the "fastmode devices" mode. However, I cannot access the device via ADB because I didn't have USB debugging turned on.
I'm not all that familiar with Android recovery options and would just like to see if I can get into my device without having to wipe it. Ideally all I want to do is either:
A.) Somehow turn on Wifi so I can unlock the device by signing into google (I can connect a keyboard up to the phone to type in my credentials)
B.) Somehow turn on USB debugging so I can use ADB to then clear the password or turn on wifi, etc
Help!
Click to expand...
Click to collapse
When you hold down the power button at the lockscreen, isn't there an option to turn on/off airplane mode?
TheCrazyDirectioner said:
When you hold down the power button at the lockscreen, isn't there an option to turn on/off airplane mode?
Click to expand...
Click to collapse
Huh I can't believe I didn't see that option. Unfortunately, I also had my data connection turned off as well, so simply turning off airplane mode is not sufficient.
I tried to load CWM recovery using the fastmode flash recovery cmd, thinking it would give me some sort of ADB access, but it errored out with a "remote failure" error. I'm not even sure that recovery would have let me disable the pattern lock anyways.
Thanks for the help!
Farfolomew said:
So I dropped my phone and shattered the screen a few days ago. Just today a section of the screen failed that prevented me from unlocking the device with my pattern. Like an idiot, I kept trying to obtain the pattern unlock, but ultimately failed and now the phone is forcing me to unlock it by signing into the Google account associated with the phone. Unfortunately that only works if you have a Wifi or data connection, which I DON'T have because I had it in Airplane mode when the digitizer died.
So what are my options here? The phone DOES have an unlocked bootloader, as I loaded the Mexican ROM a while back to replace the stock U.S. one. When I boot up to Fastboot mode, it says unlocked status 3, and I can successfully see the device by using the "fastmode devices" mode. However, I cannot access the device via ADB because I didn't have USB debugging turned on.
I'm not all that familiar with Android recovery options and would just like to see if I can get into my device without having to wipe it. Ideally all I want to do is either:
A.) Somehow turn on Wifi so I can unlock the device by signing into google (I can connect a keyboard up to the phone to type in my credentials)
B.) Somehow turn on USB debugging so I can use ADB to then clear the password or turn on wifi, etc
Help!
Click to expand...
Click to collapse
http://forum.xda-developers.com/sho...mctr=(not provided)&__utmv=-&__utmk=201566226
That link doesn't help me at all, since I can't unlock the phone to turn on USB debugging, nor would I even be able to unlock it even if I could control it remotely.
But anyways, great news to report! I was able to eventually load the Clockwork mod (CWM) as the recovery partition in fastboot mode. The problem earlier trying to flash CWM was that the phone's battery was too low and it threw a vague "remote failure" error. After charging it up to 100% the flash worked fine. After that, I rebooted into CWM and then flashed the Aroma file manager zip (using method VII on this page: http :// en. miui. com /thread-5684-1-1 . html) , and managed to delete the password and gesture key files, and voila! after restarting my phone I was in! Wooo!
So obviously I was only able to do this because my phone was previously rooted with bootloader unlocked. If that weren't the case (ie, default from the factory), then the only option would have been to wipe the device.
Farfolomew said:
That link doesn't help me at all, since I can't unlock the phone to turn on USB debugging, nor would I even be able to unlock it even if I could control it remotely.
But anyways, great news to report! I was able to eventually load the Clockwork mod (CWM) as the recovery partition in fastboot mode. The problem earlier trying to flash CWM was that the phone's battery was too low and it threw a vague "remote failure" error. After charging it up to 100% the flash worked fine. After that, I rebooted into CWM and then flashed the Aroma file manager zip (using method VII on this page: http :// en. miui. com /thread-5684-1-1 . html) , and managed to delete the password and gesture key files, and voila! after restarting my phone I was in! Wooo!
So obviously I was only able to do this because my phone was previously rooted with bootloader unlocked. If that weren't the case (ie, default from the factory), then the only option would have been to wipe the device.
Click to expand...
Click to collapse
why dont you take an HDMI cable then connect it to a TV or screen then you can see everything
Mine screen was broken some moths ago and I did this to use phone before new screen replacement came. Maybe it can help you.
devilsking said:
why dont you take an HDMI cable then connect it to a TV or screen then you can see everything
Mine screen was broken some moths ago and I did this to use phone before new screen replacement came. Maybe it can help you.
Click to expand...
Click to collapse
Yes, I should have immediately stopped trying to pattern-unlock it with the broke screen and waited until I could have hooked up my mouse. I didn't know it would lock me out of the pattern-unlock method after so many tries and force me to unlock using google signin. Also, with the google sign in, I assumed it used cached credentials, but it does not. It requires an active data or wifi connection to verify. Neither of those were turned on, nor could I turn them on. The only option I had was to get in there using a Recovery ROM and remove the password key files. I guess the moral of this story is don't be an idiot and absolutely try to get into your phone right away, when there are plenty of other ways to get in even if hte screen is completely broke (like you said with HDMI cable, keyboard, mouse, etc)
Also, I had a "fun" little issue after that where I tried to edit the build.props file to enable home screen rotation, but that ended up crashing the OS and I had to use fastboot to flash just the system.img that was from the stock Mexican 4.1.2 ROM. So now, I just downloaded an app that allows me to rotate my device, and thus allow me to avoid the dead part of the digitizer when I need to.
My stock Nexus 6 wanted to update to April security update. (I believe my phone storage was almost full)
It failed the update, is stuck on No Command dead android guy and then pops this address up.
g.co/abh
Factory reset the only option?
You might want to try flashing the update manually, using ADB and Fastboot. Doing so will wipe your device, so if you have anything in the internal storage, back it up if you can.
I try flashing manually via adb/nexus toolkit and it just says error code 7 on the phone. The device is bootlocked.
this may help
http://forum.xda-developers.com/nexus-6/general/to-save-bricked-nexus-device-t3334660
Are you trying to update with an OTA? If I remember correctly, error 7 means an OTA update check found that your phone isn't stock. This happens if you have messed with the system (rooting and other stuff), have a custom recovery (TWRP) or a custom kernel.
If the above applies to you, use factory images and fastboot to update instead (leave out userdata.img so as not to wipe your data). Ooops. Just saw you're bootloader is locked. Your data will get wiped when you unlock... Make sure to have a backup.
I have no backup, the phone is under warranty and as this has happened before. Stock update killed phone, i'm taking it to vodafone today.
I can't be bothered to mess about when my contract comes with warranty
Good thinking...
Didgeridoohan said:
Are you trying to update with an OTA? If I remember correctly, error 7 means an OTA update check found that your phone isn't stock. This happens if you have messed with the system (rooting and other stuff), have a custom recovery (TWRP) or a custom kernel.
If the above applies to you, use factory images and fastboot to update instead (leave out userdata.img so as not to wipe your data). Ooops. Just saw you're bootloader is locked. Your data will get wiped when you unlock... Make sure to have a backup.
Click to expand...
Click to collapse
Exactly same problem, struggling for a day now.
unable to unlock bootloader for flashing the device
"fastboot flashing unlock" returns OKAY but the screen still shows "Device is LOCKED. Status Code: 2"
any suggestions??
Try "fastboot oem unlock".
Strephon Alkhalikoi said:
Try "fastboot oem unlock".
Click to expand...
Click to collapse
"fastboot oem unlock" gives:
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.001s
But of course I can't do that as I cannot get it to start. I tried "adb sideload image-shamu-mmb29x.zip" too, but it fails for signature verification probably because it shows I have "MMB29V" on the phone. Downloading "MMB29V" image now, will try that too.
With your bootloader locked, you cannot flash factory images using fastboot, and ADB is not for flashing factory images. You have to flash the Android N preview as an OTA in recovery to restore your device to an operable state. Once Android N finishes optimizing apps and is booted, you need to go into the hidden Development Options menu in Settings and tick "Enable OEM Unlock". Then you can unlock the bootloader in fastboot with the command " fastboot oem unlock" so you can flash factory images.
Aston Martin said:
My stock Nexus 6 wanted to update to April security update. (I believe my phone storage was almost full)
It failed the update, is stuck on No Command dead android guy and then pops this address up.
g.co/abh
Factory reset the only option?
Click to expand...
Click to collapse
Got into the same situation yesterday. Seems like it was not just a security update (it didn't say so though), but it was update for the Android-N preview.
Wasted a whole day trying to figure out what did I do to brick my phone. In the end it was just the stupid update by google.
The solution to the problem now is to update your phone to Android-N preview OTA update - you can get it from here: http://developer.android.com/preview/download-ota.html
aHR0cDovL2RldmVsb3Blci5hbmRyb2lkLmNvbS9wcmV2aWV3L2Rvd25sb2FkLW90YS5odG1s --> base64decode this to get the link [new users not allowed to put direct links ]
Steps for solving your problem:
Connect your phone to the computer
On your phone go to the No Command screen and press the three buttobns (Vol-UP + Vol-DOWN + POWER) simultaneously [it will take a couple of tries before you succeed]
You will now reach the Android Recovery screen
Select the option "Apply update through ADB"
From the computer execute "adb sideload <OTA_UPDATE_FILE_NAME>.zip"
Wait for a few minutes and you will see the update progress on adb
Here OTA_UPDATE_FILE_NAME.zip is the name of the ota-update file you download from the developer.android.com link [given above as base64]. For Nexus 6 it is - shamu-ota-npc91k-201dd8d1.zip
Hope it will save someone a lot of their important time.
Well, I am having the same issue as OP. Stock Android on Nexus 6 (t-mobile), received OTA security patch last night. Checked that I have a little over 1GB storage left (24.90GB out of 25.98GB available) and proceeded with installation. Now it says "device is corrupt" and after the four rotating colorful circle animation it gives me the "Unfortunately, Settings has stopped" message box over and over again which I cannot get past. I tried safe mode and it hits the same error.
I am trying the manual OTA update now as ravikumr posted, but I suspect it may run out of storage space since the zip file is 855MBs. Any way I can go in and clean up some space before the installation?
If the reason the original OTA update failed was due to insufficient storage, that would be a really stupid way to annoy the user. I have been reasonably happy with my phone so far but this experience today sucks. I depend on the phone for a lot of things so I never tried to root it or modify in any way, but I guess that's still not enough to make the phone reliable.
I will post my results with the manual update.
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Target: google/shamu/shamu:N/NPC91K/2751853:user/release-keys
Patching system image unconditionally...
Verifying the updated system image...
E:unknown command [retry_update]
system partition has unexpected contents after OTA update
E:Error in /sideload/package.zip
(Status 7)
Installation aborted.
Anyone has suggestion I can try?
I couldn't wait since I needed the phone to work so I did factory reset. I had to do it twice since the first time it looked hung formatting /data (I waited over an hour) but second time it went through fairly quickly. Afterwards it was stuck on the google logo at boot, probably due to the bad system. I reinstalled the Android N preview OTA patch and it successfully completed this time, and I was off setting up the phone again.
I am still not convinced that what I have experienced was not a simple mistake that whoever put this package together forgot to put in code to check for available storage space before allowing the installation to proceed, or it could be a bug that when space ran out the installation code didn't handle it gracefully and started to do bad things. Either way it was a bad experience for me. Luckily I saved all my pictures and videos a week ago so only lost a few pictures plus other data.
I was experiencing this problem with a Nexus 6 - Update failed due to insufficient space, and it was impossible to get back into Settings to unlock the bootloader, to be able to use the Nexus toolkit or to otherwise flash a factory image.
Forgive any repetition herein, I am simply explaining how I was able to fix everything.
I am explaining how to fix this on a Windows PC. Sorry Mac/Linux users.
Firstly - if your bootloader is locked - the simplest way to get the phone back up and running is to download the Android N OTA.zip - download that here: http://developer.android.com/preview/download-ota.html
You will need to have the android sdk toolkit installed - or the basic adb/fastboot version. Click here if you need a guide on how to do that - http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
Once you have got the OTA update, and adb is installed do the following:
1. Move the OTA update into the android sdk folder.
2. Rename it Update - for simplicity's sake.
4. Reboot your phone into Recovery mode (switch phone off, hold Volume Down and Power until you get to the Bootloader Menu, Use volume down to navigate to "Recovery" and then press Power. You'll see a dead looking android dude - hold Power and press and release volume up. You'll now be in stock Recovery)
5. Scroll down to Apply update through ADB and select.
6. On your PC - in the Android SDK folder, hold down Shift and then Right Click. Select "Open Command Window Here".
7. Type the following command - "adb sideload <OTA_UPDATE_FILE_NAME>.zip" and press Enter. As explained above, to make this easier I renamed the .zip as "update". It is still a .zip file, so make sure you type adb sideload update.zip.
8. You'll see the progress and once it has done, reboot the phone.
9. If you want to stick with Android N - enjoy your phone.
10. If you don't - do this. You cannot select unlock OEM from Developer options as it is grayed out. Instead (and you need to have signed into your device with a gmail address, and selected yes to be part of the Android Beta Programme) go to the following web address - https://www.google.com/android/beta?u=0
Sign in with the same google account you signed into your device with. Select enrol device. Now select de enrol device - you should then receive a notification for a system update that will downgrade your device to the latest publicly available, stable, Marshmallow build.
And thats it.
I hope this has been helpful, apologies for any repetition.
Thanks
Kam_El said:
I was experiencing this problem with a Nexus 6 - Update failed due to insufficient space, and it was impossible to get back into Settings to unlock the bootloader, to be able to use the Nexus toolkit or to otherwise flash a factory image.
Forgive any repetition herein, I am simply explaining how I was able to fix everything.
I am explaining how to fix this on a Windows PC. Sorry Mac/Linux users.
Firstly - if your bootloader is locked - the simplest way to get the phone back up and running is to download the Android N OTA.zip - download that here: http://developer.android.com/preview/download-ota.html
You will need to have the android sdk toolkit installed - or the basic adb/fastboot version. Click here if you need a guide on how to do that - http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
Once you have got the OTA update, and adb is installed do the following:
1. Move the OTA update into the android sdk folder.
2. Rename it Update - for simplicity's sake.
4. Reboot your phone into Recovery mode (switch phone off, hold Volume Down and Power until you get to the Bootloader Menu, Use volume down to navigate to "Recovery" and then press Power. You'll see a dead looking android dude - hold Power and press and release volume up. You'll now be in stock Recovery)
5. Scroll down to Apply update through ADB and select.
6. On your PC - in the Android SDK folder, hold down Shift and then Right Click. Select "Open Command Window Here".
7. Type the following command - "adb sideload <OTA_UPDATE_FILE_NAME>.zip" and press Enter. As explained above, to make this easier I renamed the .zip as "update". It is still a .zip file, so make sure you type adb sideload update.zip.
8. You'll see the progress and once it has done, reboot the phone.
9. If you want to stick with Android N - enjoy your phone.
10. If you don't - do this. You cannot select unlock OEM from Developer options as it is grayed out. Instead (and you need to have signed into your device with a gmail address, and selected yes to be part of the Android Beta Programme) go to the following web address - https://www.google.com/android/beta?u=0
Sign in with the same google account you signed into your device with. Select enrol device. Now select de enrol device - you should then receive a notification for a system update that will downgrade your device to the latest publicly available, stable, Marshmallow build.
And thats it.
I hope this has been helpful, apologies for any repetition.
Thanks
Click to expand...
Click to collapse
This works if you are completely stock with no custom recovery and your OS is gone ? When your phone gets downgraded, does the OEM unlock appear in developer options so you can toggle it ? If so there are a lot of phones in all the threads that have been RMA due to this.
mikeprius said:
This works if you are completely stock with no custom recovery and your OS is gone ? When your phone gets downgraded, does the OEM unlock appear in developer options so you can toggle it ? If so there are a lot of phones in all the threads that have been RMA due to this.
Click to expand...
Click to collapse
This worked for me, specifically with the update issue on a fully stock and OEM locked Nexus 6 that became buggy after the update was attempted but there was not enough memory. After the update failed and it booted back up (there was an error your device is corrupt message on bootup) there were a ton of error messages and the settings app was broken. Package installer was also broken and Google play and media services were broken, therefore couldn't use the Wugfresh Nexus toolkit, couldn't use fastboot as OEM was locked and couldn't access settings to change it. Factory reset from stock recovery did not fix the errors and following bootup the startup wizard couldn't start either.
The only option was to sideload the OTA - however, for the Nexus 6, after the OTA installed the OEM unlock option was transparent and set at off (because my bootloader was always locked). I then enrolled the device on the Beta programme, and then unenrolled it. Almost immediately a downgrade able OTA notification arrived which dropped it back down to Marshmallow. After bootup all seemed fine, then play services stopped working. I was worried until I recieved a notification for a Marshmallow update - after that was installed everything worked fine as normal. The OEM unlock option was again available (although I decided to keep it locked).
For other devices it won't work, as I believe the Android N OTA is for a select few Nexus devices and possibly GPE devices (full list available on the website above).
Whether this work if you've completely deleted the OS - again I'm not sure. But I cannot see the harm in trying in that scenario. More experienced users could assist here. It should work as long as you can get into stock recovery.
Hope this helps.
Thanks Kam_El for posting the instructions. I followed the exact same steps except that "adb sideload update.zip" command wasn't successful (see my posts above). It only worked after I did a factory reset. My phone was stock Android with latest patches.
I followed your last step to downgrade the Android N back to Marshmallow. The main issue I have with N is that wechat crashes the system as soon as it's launched and only a reboot can fix it.
lyuanrich said:
Thanks Kam_El for posting the instructions. I followed the exact same steps except that "adb sideload update.zip" command wasn't successful (see my posts above). It only worked after I did a factory reset. My phone was stock Android with latest patches.
I followed your last step to downgrade the Android N back to Marshmallow. The main issue I have with N is that wechat crashes the system as soon as it's launched and only a reboot can fix it.
Click to expand...
Click to collapse
Glad to have helped. I had already attempted a factory reset before momentarily losing hope lol. Incidentally I'm now running N on my Nexus 9 - loving the new notifications.
Anyway ✌?
I have ADB and Fastboot installed on my computer. Nothing lists/shows up when the watch is connected and I run "adb devices" in terminal (as I thought would happened) .
In the recovery, there's a choice for "apply update from sd card". How does that work or does it even work, on this watch?
I haven't used the watch in some time (silver 1st gen); I guess I gave up on it a while ago. It used to be stuck on the 4 spinning circles but not anymore. When I put it on the charger, it's just stuck on the LG boot screen. I think it showed the empty battery icon and thunderbolt but can't remember seeing it today. Search for some threads on being stuck on the LG screen, not charging and stock image recovery.
So trying to troubeshoot it, I tried to charge it (w/stock charger) and all I got was stuck on the LG screen and it got warm to the touch after about 20 mins. I worried about screen burns so, I shut it down. I'm able to get into the fastboot and recovery menus. In the recovery menu, I tried a reset but nothing changed after a reboot.
In thinking it may need a restoring with the stock image, I've read that ADB Debugging on the device must be enabled (or am I incorrect about that?) Question: How can I do that if I can't get into the settings of the watch?
I'm on Linux Mint. I have SDKManager on it but not quite sure how to use it. Not a power user by any means. A little help is greatly appreciated. The only other device I've used XDA before was on a Galaxy Note (1). That was a long time ago (what we're on Note 9 now!)
Well after thinking about it, I figured I'd try the option "apply update from ADB" in the recovery mode on the watch. The watch prompted for the package I wanted to apply to the device. I opened a terminal window on my computer and ran "adb devices" and lo and behold, it came up with the watch's serial number and the text "sideload" next to it. So does this mean I could sideload a stock (or custom) ROM back on to it?
here's some specifics of the watch:
Fastboot menu
Product name - bass
Variant - bass 4GB
HW version - rev_10
Bootloader version - BASSZ12b
Singing - Production
Secured Boot - enabled
Lock State - locked
Android Recovery menu
lge/bass/bass
7.1.1/NWS2.170620.003/4125898
Any help would be appreciated for this noob.
Hello,
I need some help with my Huawei P20 Pro.
Last week it rebooted by its own and this error appeared:
"Your device has failed verification and may not work properly"
--------------------------------------------
(1) Press power key to continue
(2) Press Volume Up key up to 3 seconds to enter erecovery to restore your phone
(3) Your device will stop start , if there is no operation
After this it goes automatically to eRecovery but none of the options are working, thus "download latest version" and "Emergency backup". Only reboot and shutdown are working, but when the phone boots, this error appears again. When I click on "Emergency backup" the phone wants to reboot. After reboot the error appears and the phone goes to eRecovery again without making a backup.
When I click on "download latest version" it starts downloading and installing an update when I plug in an USB stick (because the storage is full) but it stops at 95% and "downloading package failed" is written there.
Also, the battery is damaged/bloated. I do not know if the battery contributes to the hardware verification.
I have done research on how to enable USB debugging without access to the phone but could not find anything useful. When I boot in fastboot mode there is written: phone locked, FRP lock, so I think it will not be possible to flash TWRP, right?
Is there any way to access the phone without enabling USB-debugging directly on the phone in developer options (e.g to use ABD commands) and to save the data on the phone?
I do not want to lose all my data, so I appreciate every help from you.
Thanks in advance!