Long story short - I thought I had lost my phone so I used Google's ADM to lock my Mi4c, it asked for a password and I entered 8 characters incl. numbers and letters, as I normally would. Anyways found my phone and now it's asking for a 4 digit pin, which I've never set up, I have no idea what the it could be. I've tried all the usuals.
So in the past I've used the tutorials on here to flash my device (thank you very much ), but it seems which ever way I updated it last time, it has relocked the bootloader. I was just re-granted permission (I was surprised to find that the permission expires) to use the miflash unlock tool, which completed successfully (as far as I'm aware). I thought this would allow me to access the recovery but it seems to be gone, no Mi recovery or TWRP! Nothing happens when I hold down the vol up and power button. No trouble accessing the fastboot though.
My questions is, before I go messing trying to fix this device:
Can I flash TWRP without USB debugging enabled? I can't access the settings due to the pin.
What is the best approach to solving this? I was hoping to use TWRP to delete the *.key files and hope that would unlock the device, but honestly I'm not precious about my content anymore I just want my phone back.
cherbe.3 said:
Long story short - I thought I had lost my phone so I used Google's ADM to lock my Mi4c, it asked for a password and I entered 8 characters incl. numbers and letters, as I normally would. Anyways found my phone and now it's asking for a 4 digit pin, which I've never set up, I have no idea what the it could be. I've tried all the usuals.
So in the past I've used the tutorials on here to flash my device (thank you very much ), but it seems which ever way I updated it last time, it has relocked the bootloader. I was just re-granted permission (I was surprised to find that the permission expires) to use the miflash unlock tool, which completed successfully (as far as I'm aware). I thought this would allow me to access the recovery but it seems to be gone, no Mi recovery or TWRP! Nothing happens when I hold down the vol up and power button. No trouble accessing the fastboot though.
My questions is, before I go messing trying to fix this device:
Can I flash TWRP without USB debugging enabled? I can't access the settings due to the pin.
What is the best approach to solving this? I was hoping to use TWRP to delete the *.key files and hope that would unlock the device, but honestly I'm not precious about my content anymore I just want my phone back.
Click to expand...
Click to collapse
Can't you just use android device manager again?
If your phone still boots up to lockscreen and is connected to the internet (mobile or better Wi-Fi) you should be able to access it from your computer or another device...
Sent from my OnePlus 3T using XDA Labs
Sam Nakamura said:
Can't you just use android device manager again?
If your phone still boots up to lockscreen and is connected to the internet (mobile or better Wi-Fi) you should be able to access it from your computer or another device...
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
Unfortunately not, I've tried changing the pin with ADM but it just tells me that a pin is already is place.
The phone is connected to the internet (both data and wifi), I just can't figure out how to get around it.
cherbe.3 said:
Unfortunately not, I've tried changing the pin with ADM but it just tells me that a pin is already is place.
The phone is connected to the internet (both data and wifi), I just can't figure out how to get around it.
Click to expand...
Click to collapse
If you contact Google support? Maybe they can assist a little or Google some more about the 4 vs 8 digits pin - there's something wrong, sure that the 8 digits aren't your PUK?
Maybe use ADM again, there're more options,
If you reset it via AMD?
Edit:
https://www.ifixit.com/Guide/Android+Device+Manager+-+Bypass+Screen+Lock+on+any+Android+Device/34600
Sorry, just have no time atm but I'll come back later
Sent from my OnePlus 3T using XDA Labs
Sam Nakamura said:
If you contact Google support? Maybe they can assist a little or Google some more about the 4 vs 8 digits pin - there's something wrong, sure that the 8 digits aren't your PUK?
Maybe use ADM again, there're more options,
If you reset it via AMD?
Edit:
https://www.ifixit.com/Guide/Android+Device+Manager+-+Bypass+Screen+Lock+on+any+Android+Device/34600
Sorry, just have no time atm but I'll come back later
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
Unfortunately every time I tried to replace the lock pin, Google told me that there was already a pin assign and it wouldn't be replaced.
Anyways, I'm back into my phone! Ended up having to flash the Chinese official rom using fastboot and the MiFlash tool. From there I could enable USB debugging, and flash TWRP and then install a custom global rom. Lost all my content, but a lesson learnt. No complaints, I'm back to being connected to the world!
Thanks for taking the time to help, I really appreciate it
Related
Hi, I've broken the touchscreen of my Idol3, and the phone is switched off (it's not just that the display is locked).
Powering it up requires my pin ("to start android, enter your PIN"), which I can't type.
Most solutions I've seen on the Internet require using adb, but they all assume
adb devices
lists my phone. My adb doesn't (at least, not at that point).
I assume it's because the boot sequence hasn't got far enough to make my phone visible to adb.
The adb setup seems to be fine because, when I enter the (stock) recovery mode (which I can access via power + volume up), picking the option "apply update from adb" suddenly makes my phone visible to adb (and otherwise, it's unvisible just as in normal booting).
Unfortunately, it is listed in sideload mode, which makes any adb command other than sideload miserably fail.
Question 1: is it expected that in the normal boot sequence, adb does not see my Idol3 when the phone prompts for my PIN to start Android?
Question 2: can I use the sideload function to install a more permissive recovery mode like twrp (I've found the twrp img file for the Idol3 on this website; can I turn it into a flashable zip and install it via sideload?)
Question 3: if that succeeds, is there a chance the phone responds to adb commands when the boot sequence asks for my PIN, and will I be able to simulate the typing of my PIN (which I know) via adb commands?
Ah, one precision: maybe the phone asks for a PIN to start the OS specifically because the phone (I assume the main partition) is encrypted, and the PIN allows it to be decrypted and mounted. Would that make things more complicated to recover my data?
Thanks in advance...
Hello,
i dont have experience with encrypted devices, so as far as i can tell when the device is encrypted and locked with pin untill you give the pin you cannot access any data from it.
1-No, because you have to enable usb debugging from developer menu, which you cannot access now (is in settings ). So without this you cant access your phone using adb commands
2-No, because to sideload a TWRP recovery you have to unlock the bootloader and to do that you have to enable usb debugging
So i think you have to order a new touchscreen and change it on your own. Sorry
DallasCZ said:
i think you have to order a new touchscreen and change it on your own. Sorry
Click to expand...
Click to collapse
Thanks, I wonder where can I order a screen replacement and how much would it cost me?
Sent from my 6045K using XDA-Developers mobile app
DaHiA said:
Thanks, I wonder where can I order a screen replacement and how much would it cost me?
Sent from my 6045K using XDA-Developers mobile app
Click to expand...
Click to collapse
for example here on aliexpress.com
or here on ebay
next time try to use google search. It will make your life a little easier
Ah, that's what I was afraid of.
But actually, as I finally accepted defeat and went to a shop to spend some money, I bought a USB On-the-go cable and an old-style USB-cabled mouse.
To my surprise, it did work even before the partition was decrypted and Android booted, allowing me to type in my PIN. The USB On-the-go driver must be loaded really early like the touch screen's.
Thanks for your answers! My problem taught me a lot about phones, recoveries, etc thanks to XDA!
sgl_silicon said:
Ah, that's what I was afraid of.
But actually, as I finally accepted defeat and went to a shop to spend some money, I bought a USB On-the-go cable and an old-style USB-cabled mouse.
To my surprise, it did work even before the partition was decrypted and Android booted, allowing me to type in my PIN. The USB On-the-go driver must be loaded really early like the touch screen's.
Thanks for your answers! My problem taught me a lot about phones, recoveries, etc thanks to XDA!
Click to expand...
Click to collapse
good that all is backed up now. But you didn't say, that only touchscreen is broken. I thought that also the screen is brokem and you dont see anything.
DallasCZ said:
good that all is backed up now. But you didn't say, that only touchscreen is broken. I thought that also the screen is brokem and you dont see anything.
Click to expand...
Click to collapse
Ah yes indeed; should have been more specific!
sgl_silicon said:
Ah yes indeed; should have been more specific!
Click to expand...
Click to collapse
Did the encryption make your phone slow?
I have the same model and i want to encrypt it. But i don't know if this affect significantly the performance of the cellphone.
What is your experience using this phone encrypted?
ShintaFreeman said:
Did the encryption make your phone slow?
I have the same model and i want to encrypt it. But i don't know if this affect significantly the performance of the cellphone.
What is your experience using this phone encrypted?
Click to expand...
Click to collapse
Hi,
I haven't done any real tests, but from the feel of it, encryption didn't make it slower as far as I could tell.
Great experience, in general.
sgl_silicon said:
Hi,
I haven't done any real tests, but from the feel of it, encryption didn't make it slower as far as I could tell.
Great experience, in general.
Click to expand...
Click to collapse
Thanks for the quick reply. I want to encrypt my phone but I was afraid of the performance
been trying all morning to flash pn rom, had hx of multiple android phones most recent s8 but dont like the thinness of the phone,
prefer pixel much more comfortable
okay managed to get twrp to stick and not delete itself afterwards,
now twrp basically is all random alphanumerical folders!
Any tips guys
sutty86 said:
been trying all morning to flash pn rom, had hx of multiple android phones most recent s8 but dont like the thinness of the phone,
prefer pixel much more comfortable
okay managed to get twrp to stick and not delete itself afterwards,
now twrp basically is all random alphanumerical folders!
Any tips guys
Click to expand...
Click to collapse
Just keep rebooting to recovery until TWRP prompts you for your pin or pattern lock. The one you use for locking your phone. It may take several reboots but eventually you'll get the prompt.
What you're seeing with the random folder names is caused by the encryption used on these phones. TWRP can't decrypt it if you don't enter your pin/pattern. The fact that you don't always get prompted for it by TWRP is caused by a bug in TWRP. There's nothing wrong with your phone.
robocuff said:
Just keep rebooting to recovery until TWRP prompts you for your pin or pattern lock. The one you use for locking your phone. It may take several reboots but eventually you'll get the prompt.
What you're seeing with the random folder names is caused by the encryption used on these phones. TWRP can't decrypt it if you don't enter your pin/pattern. The fact that you don't always get prompted for it by TWRP is caused by a bug in TWRP. There's nothing wrong with your phone.
Click to expand...
Click to collapse
This is not true, I don't use pin, pattern, password on nexus 4, 2 nexus 5, nor my pixel, I don't lock any of them either
I have no problems using twrp, once in a blue moon I get the garbled text, usually after a clean install, just keep rebooting back to twrp usually 2-3 times to you can use it
Sent from my Pixel using XDA-Developers Legacy app
It's really not that hard to flash ROMs on, it just needs to strictly follow order of operations and needs some additional operations compared to other Android phones. A good understanding of the A/B partitions system and how they work and switch helps a lot.
Did you set up a PIN or a Pattern Lock? It is needed for TWRP to be able to decrypt phone.
If you haven't, just boot your phone, go to Settings > Security > Screen lock and set up a Pattern, PIN or Password. Then reboot to Recovery and see if it asks for what you just set up before entering Recovery.
@piperx I experienced exactly that problem and setting up a lock solved it, good for you that you did not need that but others may do. Is your phone encrypted?
TWRP gave me problem of encrypted folders a lot of times, even after set a pin/password/pattern.
I just discovered that if you boot to TWRP when you have connected an OTG or the PC that error occurs, but if you unplug the device and input the pin and after that plug what you want, it works.
appreciated gents will try again now and see how i go, makes sense as 1. i didnt have a lock screen (new setup) and 2. it was plugged into laptop majority of tries!
will update in an hour i hope
update finally got pn on the pixel
i had to reboot twrp a few times to get it to ask me for my pattern!
cheers guys
kudos given
piperx said:
This is not true, I don't use pin, pattern, password on nexus 4, 2 nexus 5, nor my pixel, I don't lock any of them either
I have no problems using twrp, once in a blue moon I get the garbled text, usually after a clean install, just keep rebooting back to twrp usually 2-3 times to you can use it
Sent from my Pixel using XDA-Developers Legacy app
Click to expand...
Click to collapse
It is true if you use a lock of some kind. If, when you boot to TWRP, you don't get the option to enter your pattern or whatever, you're going to get the garbled text thing. Each and every time.
its more like Android Nougat thing than Pixel. I had similar issues even on One Plus 3. New android always brings more complicated issues. (i.e we still don't stable xposed for nougat yet )
Hi All,
First, thanks for clicking into my question! This is my first post, but I've been lurking here since I used to flash new roms on my original Nexus on a frequent basis, and a Gen1 Kindle Fire before that.
My fiancee is in a bind with her Pixel 2, so I'm hoping you all can help me out.
Her Pixel 2 threw a bunch of app errors over the course of two days, so she opted to reboot -- unfortunately it now locks up at the loading screen, with the Google 'G' and a loader bar (she's running the latest 8.1, pre-Pie) and hangs there, overheating until the battery runs out and we shut it down. We can get into the Recovery menu, but none of the reboot options there seem to help, and there is only the Factory Reset option remaining that we haven't tried.
This happened in the middle of a huge camping excursion as her Bachelorette, so there was limited WiFi and data access to back anything up -- so locked behind that endless boot sequence is a lot of irreplaceable images and video.
What are my options to pull the user data out of there before a factory reset? Is it possible on a (stock, non-root, Google sourced) phone to flash the Pie update? Would that restore functionality?
Can I get to the data somehow through ADB without the phone booting up and unlocked?
Maybe something crazy, like a take a full image of the phone that I then shove on the replacement Pixel 2 that Google is sending us?
Any guidance would be much appreciated!
You could try booting to TWRP with "fastboot boot <filename here>". Then copy the files from there. I'm not sure if this will work if she had the screen locked beforehand though. You could also try flashing the latest factory image but make sure your remove the "-w" from the flash-all.bat file before running the script so it will not wipe user data. Both of these options might not be possible though if you do not have the boot-loader unlocked.
cynnican said:
Hi All,
First, thanks for clicking into my question! This is my first post, but I've been lurking here since I used to flash new roms on my original Nexus on a frequent basis, and a Gen1 Kindle Fire before that.
My fiancee is in a bind with her Pixel 2, so I'm hoping you all can help me out.
Her Pixel 2 threw a bunch of app errors over the course of two days, so she opted to reboot -- unfortunately it now locks up at the loading screen, with the Google 'G' and a loader bar (she's running the latest 8.1, pre-Pie) and hangs there, overheating until the battery runs out and we shut it down. We can get into the Recovery menu, but none of the reboot options there seem to help, and there is only the Factory Reset option remaining that we haven't tried.
This happened in the middle of a huge camping excursion as her Bachelorette, so there was limited WiFi and data access to back anything up -- so locked behind that endless boot sequence is a lot of irreplaceable images and video.
What are my options to pull the user data out of there before a factory reset? Is it possible on a (stock, non-root, Google sourced) phone to flash the Pie update? Would that restore functionality?
Can I get to the data somehow through ADB without the phone booting up and unlocked?
Maybe something crazy, like a take a full image of the phone that I then shove on the replacement Pixel 2 that Google is sending us?
Any guidance would be much appreciated!
Click to expand...
Click to collapse
ADB sideload the latest OTA zip in stock recovery, that should get you up and running again without needing a wipe
crixley said:
ADB sideload the latest OTA zip in stock recovery, that should get you up and running again without needing a wipe
Click to expand...
Click to collapse
Thank you! I'll be giving this a try as soon as she's home on Monday.
Does recovery mode automatically enable the USB Debugging that ADB uses?
cynnican said:
Thank you! I'll be giving this a try as soon as she's home on Monday.
Does recovery mode automatically enable the USB Debugging that ADB uses?
Click to expand...
Click to collapse
Yep you can sideload without needing it toggled in developer mode
crixley said:
Yep you can sideload without needing it toggled in developer mode
Click to expand...
Click to collapse
This worked perfectly, thank you!
cynnican said:
This worked perfectly, thank you!
Click to expand...
Click to collapse
I'm glad to hear! Nothing worse than having to wipe and losing important things you can't get back. I've had that happen a few times. Happy to help.
I'm not very technical - please keep this in mind with my query below.
I have a Pixel 2 which overnight stopped working - my guess is that it rebooted due to an automated software update.
I now only get the page with the robot on it's back.
Options in green on this page are Barcodes, Power Off, and Start.
After reading a lot online I've tried all the usual key press combinations to no avail.
I've also downloaded ADB and FASTBOOT to my Mac.
ADB doesn't see the phone when plugged in via USB (ie. ADB DEVICES doesn't return anything)
FASTBOOT DEVICES does, however, show the serial number as listed on the page with the robot on it's back (and the -l option adds "usb:" plus an 8 digit number and the letter "X"
FASTBOOT REBOOT restarts the phone and brings me back to the robot on it's back page.
Other information on the Robot on it's back page include -
Product Revision: walleye MP1
Boot-slot: b
Console: DISABLED
Secure Boot: yes (PRODUCTION)
Device State: locked
Advice online suggests I need to unlock the phone, so I've tried FASTBOOT FLASHING UNLOCK, and FASTBOOT OEM UNLOCK but neither work.
When I try these I get "FAILED (remote: Flashing Unlock is not allowed)"
An article on Android Police suggests this may have been a bug on the Pixel 2 originally and that it's now resolved.
Unfortunately, my cat 22 situation seems to be that I need to do a factory reset, but the steps I've found as to how to do a factory reset all lead back to the Robot on it's back page, so I can't see how to move forward to with recovering my phone?
Can anyone help please?
Really frustrated that my new phone can put itself into this state without me having done anything and that it's seemingly impossible to recover from this state now that it's in it.
At very least I'd like to wipe all data from the phone so I can send it off for repair.
Thanks in advance.
So for the last three months I've been using my rooted phone with the Pixel Experience ROM, and today I decided to switch back to the stock rom. I first tried to uninstall Magisk, but when I checked the app it was already uninstalled, which I think was a bit strange. Then I downloaded the global 14.0.1 MIUI and tried to flash it via recovery mode using adb, and it failed at the end of the flashing process. So I went to try to install it using fastboot, but after using the command fastboot devices, my phone was not listed. Then I went to the recovery mode again (I was using orange fox when doing so) and tried to reboot into fastboot mode. Doing so didn't change anything when using the command to list the devices, but MiFlash had it listed, so I tried using it. I selected the rom, and selected the "clean and lock" IIRC, it started to flash and said it finished without any errors, however my phone showed some errors that I can't remember now. I tried to reboot the phone, and it went back to recovery mode, so I tried to flash it again. In this time, I tried to stop the flashing process by removing the usb because I thought I should look for the errors first, and then I remembered that I shouldn't do it (I have a very bad short term memory), so I tried to put the usb back and flashing it again. This time the Miflash showed an error, and I realized I was using the flash command while in recovery mode, not fastboot (I accidentaly pressed "adb" in the recovery), so I tried to reboot my phone to change it and it turned off. There's no more battery charging screen, fastboot or recovery. After a lot of research, I found out that my phone is in ETL mode, it shows in the device manager on my pc and also shows in the miflash as "COM3" or "COM4".
Can someone please help me? I tried so many things so far, and I still don't want to send it to repair
If you selected clean and lock and it finished, that means you locked your bootloader, and with locked bootloader, you can't flash anything. And you also yanked usb out of your phone in the middle of flashing process? My bet, you screwed up partition or two, and now your phone is in EDL, my man... Just take it to a service centre, before it's completely destoryed
When I was writing the thread I was wondering how could I be that stupid. I think I'll really need to send It to a service center.
seiguisage said:
When I was writing the thread I was wondering how could I be that stupid. I think I'll really need to send It to a service center.
Click to expand...
Click to collapse
I would be surprised if they would be of any help, except maybe to ask you to change the motherboard completely.
TheMystic said:
I would be surprised if they would be of any help, except maybe to ask you to change the motherboard completely.
Click to expand...
Click to collapse
So probably It really is just a paperweight now
seiguisage said:
So probably It really is just a paperweight now
Click to expand...
Click to collapse
If it shows signs of life, you may be able to resuscitate it. But I doubt an official service centre would be of any help here, except as stated above.
Just do some more research. You may find a way. All the best.
TheMystic said:
If it shows signs of life, you may be able to resuscitate it. But I doubt an official service centre would be of any help here, except as stated above.
Just do some more research. You may find a way. All the best.
Click to expand...
Click to collapse
Since my gf gave me her old Mi 9 I think I'll make this a new hobby lol
TheMystic said:
I would be surprised if they would be of any help, except maybe to ask you to change the motherboard completely.
Click to expand...
Click to collapse
What are you talking about. if he has access to EDL mode he can fix everything. Even if your UFS was completely wiped and had no partitions. EDL is a completely separate thing. However you can't reflash the software using EDL because only service centers have the authorisation to do that (some people have that access too, and you can reflash your phone if you pay them). Another way to do it is open the phone up, and short some pins to get access to unauthorised EDL.
TheMystic said:
If it shows signs of life, you may be able to resuscitate it.
Click to expand...
Click to collapse
Yeah, mouth-to-usb always helps.
Hi all,
Im in a desperate and urgent need of help.
My Mrs pixel 7 pro is stuck in a boot loop that restarts 5 seconds after the google writing appears when starting. I wasn't home when it happened but she doesnt really make sure her phone has some battery before turning it on, as soon as she sees 2% she starts it, so im guessing maybe she bricked it while the phone was trying to apply an update when turning it on as she said that the external battery didnt have any juice left inside.
Anyway,
I know i can wipe the phone from recovery mode and make it into a factory reset phone. The issue here is we have over 6000 photos and videos of our son in that phone that she hasnt copied to the external hard drive i gave her for months due to her not liking that her little laptop is slow.
I tried recovery mode Reboot, i tried going into safe mode (no luck as it will go straight into fastboot mode). She doesnt care about a lot of things and obviously she never unlocked the developer setting or bootloader so device state is also locked.
I am begging you, anything any info or advice on how i can get those pictures out of the phone. Is there any way i can flash the stock firmware just to make the phone start and copy them after?
Any possibility or chance or retrieval?
I am willing to pay anyone that can guide me in the right direction as there are over 6 months worth of photos and memories.
Thanks in advance and may the luck be on my side.
andyysk said:
Hi all,
Im in a desperate and urgent need of help.
My Mrs pixel 7 pro is stuck in a boot loop that restarts 5 seconds after the google writing appears when starting. I wasn't home when it happened but she doesnt really make sure her phone has some battery before turning it on, as soon as she sees 2% she starts it, so im guessing maybe she bricked it while the phone was trying to apply an update when turning it on as she said that the external battery didnt have any juice left inside.
Anyway,
I know i can wipe the phone from recovery mode and make it into a factory reset phone. The issue here is we have over 6000 photos and videos of our son in that phone that she hasnt copied to the external hard drive i gave her for months due to her not liking that her little laptop is slow.
I tried recovery mode Reboot, i tried going into safe mode (no luck as it will go straight into fastboot mode). She doesnt care about a lot of things and obviously she never unlocked the developer setting or bootloader so device state is also locked.
I am begging you, anything any info or advice on how i can get those pictures out of the phone. Is there any way i can flash the stock firmware just to make the phone start and copy them after?
Any possibility or chance or retrieval?
I am willing to pay anyone that can guide me in the right direction as there are over 6 months worth of photos and memories.
Thanks in advance and may the luck be on my side.
Click to expand...
Click to collapse
If you can enter recovery mode try to sideload the same exact ota package of the rom she's running, maybe that can help. Good luck!
andyysk said:
Hi all,
Im in a desperate and urgent need of help.
My Mrs pixel 7 pro is stuck in a boot loop that restarts 5 seconds after the google writing appears when starting. I wasn't home when it happened but she doesnt really make sure her phone has some battery before turning it on, as soon as she sees 2% she starts it, so im guessing maybe she bricked it while the phone was trying to apply an update when turning it on as she said that the external battery didnt have any juice left inside.
Anyway,
I know i can wipe the phone from recovery mode and make it into a factory reset phone. The issue here is we have over 6000 photos and videos of our son in that phone that she hasnt copied to the external hard drive i gave her for months due to her not liking that her little laptop is slow.
I tried recovery mode Reboot, i tried going into safe mode (no luck as it will go straight into fastboot mode). She doesnt care about a lot of things and obviously she never unlocked the developer setting or bootloader so device state is also locked.
I am begging you, anything any info or advice on how i can get those pictures out of the phone. Is there any way i can flash the stock firmware just to make the phone start and copy them after?
Any possibility or chance or retrieval?
I am willing to pay anyone that can guide me in the right direction as there are over 6 months worth of photos and memories.
Thanks in advance and may the luck be on my side.
Click to expand...
Click to collapse
As @acuicultor said;
Here's Googles official OTA updates and instructions etc.
From what i've read briefly and as far as i can gather (still running a stock pixel 7 pro - for the first phone in god knows how long, so i'm not well read on this device but...) if you can sideload the latest OTA update via sideload then you should in theory be able to save the data and boot again. But if you flash full firmware then your device will be wiped in the process (if that's even possible with a locked bootloader).
Very best of luck
EDIT: hmm thinking about it, you won't have enabled USB debugging in dev options, hang on, i'll reboot direct to recovery to see if i can get the device recognised without USB debugging enabled. Sorry to be vague (hopefully someone more experienced with this device will chime in with more advice), like i say, i'm not rooted, flashed with custom rom - nothing, just plain old stock so i've not read up much on proceedures for this device. Bare with me!!
Had another thought, do you or have you been using Google photos to view your images on the device. If so, did you enable backup photos online when you first set the app up? If so, they could be backed up automatically...
Edit: my bad..
Try this link
If that fails just Google 'Google photos sign in'
Just tried from recovery to run some adb cmd's, no joy without enabling debugging 1st
There may be hope... If your photos aren't backed online already from above link...
EDIT:
1. From power off state (make sure the device is charged before apply any ota update) Press vol down and power together. As soon as it boots to google logo, let go of vol down, then power. That will put you in fastboot mode where you use the vol up/down to navigate to Recovery mode and power button to select.
2. Then when you have the screen that says 'no command', press power button and CLICK vol up (releasing vol up straight away but keeping power pressed). That'll take you a blue menu at top of screen.
3. Use vol buttons to navigate to 'apply update from adb'. I have checked using 'adb devices' and 'adb reboot sideload' cmd's on PC and the device is now recognised...
Will write further instructions shortly. (no guarantees this will work tho without losing data...or even if it'll work at all - i suspect the OTA update with just fail to transfer)
OR there is another option, using the same instructions above (1) in fastboot mode use the volume buttons to navigate the menu, power button to select Rescue mode. Then contact your service center for support who will advise/offer support - hopefully, which may end up having to send the device in and still offers no guarantee of preserved data
reg66 said:
@acuicultor said;
Here's Googles official OTA updates and instructions etc.
Click to expand...
Click to collapse
Following the link it's all explained there:
- no USB-Debugging needed
- booting recovery by key combo
- no loss of any data when using the OTA files
Also turning on USB-Debugging in developer options is not necessary for the recovery. It's enabled by default and moreover the recovery doesn't consider any system settings like disabled/enabled USB-Debugging.
WoKoschekk said:
Following the link it's all explained there:
- no USB-Debugging needed
- booting recovery by key combo
- no loss of any data when using the OTA files
Also turning on USB-Debugging in developer options is not necessary for the recovery. It's enabled by default and moreover the recovery doesn't consider any system settings like disabled/enabled USB-Debugging.
Click to expand...
Click to collapse
Ahh cool. I obviously didn't read much of it! Dunno what's happened to the chap, maybe his wife has killed him lol
reg66 said:
Ahh cool. I obviously didn't read much of it! Dunno what's happened to the chap, maybe his wife has killed him lol
Click to expand...
Click to collapse
yes, maybe...
FYI: Stock recovery only uses a minimal adbd with a very limited set of commands. That's why some known ADB commands won't work.
minadbd