Hi,
Due to an unfortunate accident, my nexus 6P's screen is not longer functional. The screen is blank and the touchscreen does not work anymore. I am able to get into fastboot mode and installed TWRP (previously had CWM) but I am unable to access recovery mode in order to backup my files into my computer. Is there any way around this? Thank you for the help. Holding power and volume up keys does not work and only bootloader mode works but since I can't see anything, I am unable to select the recovery mode option
faatehhamad said:
Hi,
Due to an unfortunate accident, my nexus 6P's screen is not longer functional. The screen is blank and the touchscreen does not work anymore. I am able to get into fastboot mode and installed TWRP (previously had CWM) but I am unable to access recovery mode in order to backup my files into my computer. Is there any way around this? Thank you for the help. Holding power and volume up keys does not work and only bootloader mode works but since I can't see anything, I am unable to select the recovery mode option
Click to expand...
Click to collapse
have you tried
Code:
fasboot reboot recovery
Reboot to bootloader, volume down button twice then power button. It will boot into TWRP. Good luck trying to your password if you're encrypted. You should be able to adb from there.
Sent from my Nexus 6P using Tapatalk
I had a similar issue with an S4, and the phone functioned, but without an active screen. I was able to boot it normally, and access the files on my phone when connected to my laptop. Have you tried that?
83097markcynt said:
have you tried
Code:
fasboot reboot recovery
Click to expand...
Click to collapse
I used the fastboot flash recovery recovery.img command and used the latest TWRP version for it. However, I don't remember if encryption or pattern lock was set on the recovery (does it matter though, if I reflash the recovery?). After the command, fastboot tells me that it has successfully booted into the recovery mode, and is evident from the fact that my device no longer lists in the fastboot devices command, and Nexus ADB interface appears on my computer's device manager window. Assuming that ADB is enabled in recovery mode, I try to connect my computer via ADB but no device is recognized. I can boot into my phone normally, but since I cannot see the screen, unlocking my phone is impossible and without that, I can't access my files, also ADB does not work on the lockscreen and it probably has to be enabled via developer options initially.
Is there any work around for this? Perhaps enabling ADB on the recovery using fastboot? Or disabling the pattern lock using a flashable .zip file that I can flash via Fastboot? I just want access to my phone as it has important data that needs to be recovered. Thank you for all the help!
dratsablive said:
I had a similar issue with an S4, and the phone functioned, but without an active screen. I was able to boot it normally, and access the files on my phone when connected to my laptop. Have you tried that?
Click to expand...
Click to collapse
Yes, I can boot into my phone. However, I cannot access files and my laptop does not detect it whilst on the lockscreen
faatehhamad said:
Yes, I can boot into my phone. However, I cannot access files and my laptop does not detect it whilst on the lockscreen
Click to expand...
Click to collapse
That's the rub, I probably didn't have a lock screen enabled.
Related
I am trying to root my Nexus 10. This is what I did, but it ended up bricked!
I installed the Android SDK on my Windows 7 computer, and downloaded the Android USB drivers and tools.
I turned on USB debugging, and checked I could see the device with adb list devices.
I downloaded recovery-clockwork-touch-6.0.4.3-manta.img, booted the tablet into bootloader, and flashed it
Code:
fastboot oem unlock
fastboot flash recovery recovery-clockwork-touch-6.0.4.3-manta.img
That seemed to work, so I went into recovery, but recovery had all sorts of errors - it couldn't find the sdcard, or mount most of the partitions.
Rebooting stops in the animated logo, apparently for ever.
I have since tried to reload the factory image, but the computer no longer recognises the device - fastboot devices returns nothing.
Help!!!
[Later] The tablet was running the latest O/S (if I could boot it, I could tell you the number!)
Things have got worse. Now, when I go into bootloader mode, the volume keys don't do anything any more, so I can't even turn it off now
Make sure fastboot is set up properly, may need to reinstall drivers or try another computer or try another USB
http://forum.xda-developers.com/showthread.php?t=2277112
I have a feeling the recovery you flashed was corrupt in some way, did you by chance check the md5sum of the image first?
If your able to get fastboot to recognize tab
fastboot erase recovery
fastboot erase system -w
fastboot erase boot
Download latest twrp recovery
Check md5sum
fastboot flash recovery nameofrecovery.img
Then you will either need to flash stock system.img from fastboot or boot to new recovery and adb sideload a ROM
Hopefully your emmc is not to severely corrupt to all this, best of luck!
Sent from my Nexus 4 using XDA Premium 4 mobile app
Thanks, that was pretty much what I did. The trick was to get it working in boot loader mode. I kept trying to reboot it, and in the end holding down power plus both volume up and down all at the same time for 2 beeps made it work.
Sent from my Nexus 10 using Tapatalk
nikkilocke said:
I am trying to root my Nexus 10. This is what I did, but it ended up bricked!
I installed the Android SDK on my Windows 7 computer, and downloaded the Android USB drivers and tools.
I turned on USB debugging, and checked I could see the device with adb list devices.
I downloaded recovery-clockwork-touch-6.0.4.3-manta.img, booted the tablet into bootloader, and flashed it
Code:
fastboot oem unlock
fastboot flash recovery recovery-clockwork-touch-6.0.4.3-manta.img
That seemed to work, so I went into recovery, but recovery had all sorts of errors - it couldn't find the sdcard, or mount most of the partitions.
Rebooting stops in the animated logo, apparently for ever.
I have since tried to reload the factory image, but the computer no longer recognises the device - fastboot devices returns nothing.
Help!!!
[Later] The tablet was running the latest O/S (if I could boot it, I could tell you the number!)
Things have got worse. Now, when I go into bootloader mode, the volume keys don't do anything any more, so I can't even turn it off now
Click to expand...
Click to collapse
I have the same problem, however I can't access my Nexus 10, fastboot devices and adb devices gives back an empty line, so I can't access the N10 with fastboot or adb, to lash a ROM. Factory reset from CWM doesn't work, ˛internal card can't be accessed from CWM ("E: Can't mount /sdcard).
How can I get out of this trouble? (Solutions in forums usually involve reflashing with fastboot or formatting the external SD card. These solutions don't work here...
Any idea would be highly appreciated...
Csaba
Keep trying to reboot into bootloader mode, until it works. Hold down power and both volume buttons at the same time until it beeps twice. If the volume buttons then work to change the option on the left, but fastboot devices on the pc shows nothing, try reinstalling the Google drivers on the pc (via Device Manager, update drivers, have disk). (may have missed out a step in device manager instructions, but there are plenty of Google hits on installing add drivers if you don't already know how).
Sent from my Nexus 10 using Tapatalk
nikkilocke said:
Keep trying to reboot into bootloader mode, until it works. Hold down power and both volume buttons at the same time until it beeps twice. If the volume buttons then work to change the option on the left, but fastboot devices on the pc shows nothing, try reinstalling the Google drivers on the pc (via Device Manager, update drivers, have disk). (may have missed out a step in device manager instructions, but there are plenty of Google hits on installing add drivers if you don't already know how).
Sent from my Nexus 10 using Tapatalk
Click to expand...
Click to collapse
Sorry, I don't understand what you mean.
I can get into into bootloader mode after keeping the 3 buttons (power+volume up+volume down) pushed together (after two beeps). From there I can't boot the device. (Boot gets into the Google animation forever), so as factory reset.
Also device manager doesn't see the N10, so I can't update the drivers on my PC.
Csaba
---------- Post added at 05:17 PM ---------- Previous post was at 05:00 PM ----------
ixxion said:
Sorry, I don't understand what you mean.
I can get into into bootloader mode after keeping the 3 buttons (power+volume up+volume down) pushed together (after two beeps). From there I can't boot the device. (Boot gets into the Google animation forever), so as factory reset.
Also device manager doesn't see the N10, so I can't update the drivers on my PC.
Csaba
Click to expand...
Click to collapse
After some repeated turning off and on, now I can see the N10 from the PC (also updated the USB drivers to be on the safe side).
If I enter the bootloader, fastboot sees the N10 in a normal form, if from there I go into recovery mode, adb sees the N10 in recovery mode. Should I proceed from here by using fastboot, or rather adb?
Csaba
You should just use volume up + power (or the whatever the volume rocker button closer to power key) never had it beep to get there
To both of you, follow the steps from above, so long as it isn't a hardware issue this will get you working
Sent from my Nexus 7 using XDA Premium 4 mobile app
ixxion said:
After some repeated turning off and on, now I can see the N10 from the PC (also updated the USB drivers to be on the safe side).
If I enter the bootloader, fastboot sees the N10 in a normal form, if from there I go into recovery mode, adb sees the N10 in recovery mode. Should I proceed from here by using fastboot, or rather adb?
Csaba
Click to expand...
Click to collapse
Glad you have managed to make the device visible again (it's really scary when you can't, I know from yesterday!).
Go into bootloader mode (not recovery), and follow the fastboot instructions demkantor gave earlier in the thread.
Get your factory image from https://developers.google.com/android/nexus/images#mantaray.
Get TWRP recovery from http://teamw.in/project/twrp2/128.
At least, that's how I did it.
demkantor said:
Make sure fastboot is set up properly, may need to reinstall drivers or try another computer or try another USB
http://forum.xda-developers.com/showthread.php?t=2277112
I have a feeling the recovery you flashed was corrupt in some way, did you by chance check the md5sum of the image first?
If your able to get fastboot to recognize tab
fastboot erase recovery
fastboot erase system -w
fastboot erase boot
Download latest twrp recovery
Check md5sum
fastboot flash recovery nameofrecovery.img
Then you will either need to flash stock system.img from fastboot or boot to new recovery and adb sideload a ROM
Hopefully your emmc is not to severely corrupt to all this, best of luck!
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
How do I check md5sum?
Use this for windows
http://www.microsoft.com/en-us/download/details.aspx?id=11533
Or terminal for Linux
md5sum nameoffile.extention
Sent from my Nexus 7 using XDA Premium 4 mobile app
demkantor said:
You should just use volume up + power (or the whatever the volume rocker button closer to power key) never had it beep to get there
To both of you, follow the steps from above, so long as it isn't a hardware issue this will get you working
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thank you very much. Tablet is up and running again. :good:
Now, my next question, after being unsuccessful with CWM, I tried using TWRP for rooting the tablet, however it wouldnt start.
When I go from the bootloader into recovery mode only a laying android figure is displayed with a red triangle with an exclamation mark inside.
I have USB debugging enabled. What can be the problem?
ixxion said:
Thank you very much. Tablet is up and running again. :good:
Now, my next question, after being unsuccessful with CWM, I tried using TWRP for rooting the tablet, however it wouldnt start.
When I go from the bootloader into recovery mode only a laying android figure is displayed with a red triangle with an exclamation mark inside.
I have USB debugging enabled. What can be the problem?
Click to expand...
Click to collapse
That means you don't have twrp installed. That's the stock recovery. You can download twrp and use fastboot yo flash it or try the app twrp intaller which dies or fir you
Sent from my VS980 4G using xda app-developers app
I had to replace a battery on my Nexus 4, and the new battery is just as broken (red light of death). I'd like to pull the files off the device.
Now, I've tried multiple different methods that claim to fix the red light of death and none have worked, so I'm trying some other things now.
When holding volume down + power and giving the phone a usb power source, I manage to get into the bootloader screen. I've checked fastboot and it's recognising the device, however adb is not. I have a feeling since last flashing a rom I have not re-enabled USB Debugging, that or adb requires the phone to be on which I am not sure about.
I was wondering is there a way I can copy files across with fastboot or if there is a way to get adb working with only fastboot?
Other Information: In the bootloader screen I cannot select any of the options with the power button, I can only scroll through them with volume keys. I cannot boot into recovery/into my phone through fastboot or the red light comes back. I simply only have fastboot through the bootloader.
If your phone's bootloader is unlocked, you can install a custom recovery (like TWRP) and pull the files from the internal storage with "adb pull".
If it is locked, you can't do much, because unlocking it will wipe your device.
Erovia said:
If your phone's bootloader is unlocked, you can install a custom recovery (like TWRP) and pull the files from the internal storage with "adb pull".
If it is locked, you can't do much, because unlocking it will wipe your device.
Click to expand...
Click to collapse
I had a go at booting into a recovery image, however that set off the red light again :/
Is the bootloader locked or unlocked?
Erovia said:
Is the bootloader locked or unlocked?
Click to expand...
Click to collapse
Unlocked, Thanks
Have you tried flashing TWRP or CWM recovery?
Erovia said:
Have you tried flashing TWRP or CWM recovery?
Click to expand...
Click to collapse
Yup, Just did it again:
Code:
fastboot flash recovery cwm.img
It succeeds. I then click to boot into recovery and I get the red light again. It doesn't seem to be possible :/
As far as I know, there is no way of retrieving data with fastboot. :S
Erovia said:
As far as I know, there is no way of retrieving data with fastboot. :S
Click to expand...
Click to collapse
It would seem that way. So fustrating, I almost always have USB Debugging enabled because I fiddle about with my phone regularly, but of course when it is so dearly needed I forget to turn it on!
It might ease your pain: USB Debugging has nothing to do with your problem, because it is a service of Android. So if you can't boot into Android, you can't use it.
Erovia said:
It might ease your pain: USB Debugging has nothing to do with your problem, because it is a service of Android. So if you can't boot into Android, you can't use it.
Click to expand...
Click to collapse
Ahh ok, I guess I'll just need to splash out on a new battery/fix this one if possible. Thanks for your help!
I have unlocked my phone, hoping to find a fix to USB external camera not being recognized. As a consequence, I am not able to update my system through OTA. Moreover, I am no longer able to enter fastboot mode. Whatever key combination I tried, my phone will do a normal boot. When I power up or I press volume - I only end up doing a normal boot or powering off. If I press all 3 keys together I get into the e-recovery boot, which fails. I have only been able to boot into TWRP after downloading a system update and choosing to install it. With this procedure, the update will not be installed, but I will boot into TWRP. From here, if I choose recovery, I do boot into fastboot, but my fastboot is not recognized by my computer, as it was before. Running either ADB or Fastboot will not reveal any device connected.
pieemme said:
I have unlocked my phone, hoping to find a fix to USB external camera not being recognized. As a consequence, I am not able to update my system through OTA. Moreover, I am no longer able to enter fastboot mode. Whatever key combination I tried, my phone will do a normal boot. When I power up or I press volume - I only end up doing a normal boot or powering off. If I press all 3 keys together I get into the e-recovery boot, which fails. I have only been able to boot into TWRP after downloading a system update and choosing to install it. With this procedure, the update will not be installed, but I will boot into TWRP. From here, if I choose recovery, I do boot into fastboot, but my fastboot is not recognized by my computer, as it was before. Running either ADB or Fastboot will not reveal any device connected.
Click to expand...
Click to collapse
When you use key combinations, you must shutdown your phone first, not reboot or you can boot into system, make sure that usb debugging is turned on, open adb and type "adb reboot bootloader".
DeathBell said:
When you use key combinations, you must shutdown your phone first, not reboot or you can boot into system, make sure that usb debugging is turned on, open adb and type "adb reboot bootloader".
Click to expand...
Click to collapse
Thanks, I followed your instructions but with no success. As soon as I plug into USB it will power on and go on with a normal system boot, no matter how quick I am in typing the command "adb reboot bootloader", which invariably returns "no devices/emulators found", or whether I press the volume - button or not. This also happens when I am in the charging screen (not sure whether this also equals power off).
pieemme said:
Thanks, I followed your instructions but with no success. As soon as I plug into USB it will power on and go on with a normal system boot, no matter how quick I am in typing the command "adb reboot bootloader", which invariably returns "no devices/emulators found", or whether I press the volume - button or not. This also happens when I am in the charging screen (not sure whether this also equals power off).
Click to expand...
Click to collapse
No, you need to boot to Android to use adb.
Is your device bricked or stuck in a bootloop or something?
DeathBell said:
No, you need to boot to Android to use adb.
Is your device bricked or stuck in a bootloop or something?
Click to expand...
Click to collapse
I wouldn’t call it properly bricked, inasmuch as it is actually doing its job. However, It does some strange things: it gets the OTA updates, but when I click on Download and Install, it restarts in the TWRP menu (which I cannot otherwise access. I have 2 TWRP apps installed, which don’t seem to be of any use: official TWRP App and TWRP Manager). When I am in the TWRP menu, I can choose to restart in the bootloader. However, once there, with the green window telling me that my phone is flashed, the phone is still not detected by ADB or Fastboot commands. I don’t know when the bootloader started to be unaccessible because I left the tinkering a couple of months ago, when I realized that nobody so far has had any success in getting a P10 Lite to work with a USB Endoscope.
pieemme said:
I wouldn’t call it properly bricked, inasmuch as it is actually doing its job. However, It does some strange things: it gets the OTA updates, but when I click on Download and Install, it restarts in the TWRP menu (which I cannot otherwise access. I have 2 TWRP apps installed, which don’t seem to be of any use: official TWRP App and TWRP Manager). When I am in the TWRP menu, I can choose to restart in the bootloader. However, once there, with the green window telling me that my phone is flashed, the phone is still not detected by ADB or Fastboot commands. I don’t know when the bootloader started to be unaccessible because I left the tinkering a couple of months ago, when I realized that nobody so far has had any success in getting a P10 Lite to work with a USB Endoscope.
Click to expand...
Click to collapse
Thats normal behaviour, when you have a custom recovery installed and do anything in the stock recovery then it boots you into the custom recovery, it should also boot to TWRP when you do factory reset in the stock recovery. And when your phone isn't detected by fastboot then its probably a adb and fastboot installation issue on your PC, type "fastboot devices" to see if it detects your device. And what do you even want to do in fastboot?
Also are you in Nougat or Oreo?
DeathBell said:
Thats normal behaviour, when you have a custom recovery installed and do anything in the stock recovery then it boots you into the custom recovery, it should also boot to TWRP when you do factory reset in the stock recovery. And when your phone isn't detected by fastboot then its probably a adb and fastboot installation issue on your PC, type "fastboot devices" to see if it detects your device. And what do you even want to do in fastboot?
Also are you in Nougat or Oreo?
Click to expand...
Click to collapse
I am not too sure to have any working recovery at all, right now. If I press all 3 buttons, I get into the Huawei recovery mode, which fails. I am on EMUI 5.1.1 (Nougat) and would like to install a stock recovery to Oreo. If I am able to get to a working bootloader mode, I would like to install this file which seems to be a stock recovery with Oreo (WARSAW L21C432B182_EU_SERVICE_ANDROIDHOST.RU.RAR). Otherwise, I will buy a MicroSD card reader and try copying this installation to the card, which, according to this video (https://www.youtube.com/watch?v=0vDgDXePAR4&feature=youtu.be) should be the last resort, if everything else fails. I would be perfectly happy to return to a working and updated standard EMUI. I'm told that if I installed the OTA version this would not be working correctly on my my phone. According to an app called Rootchecker, my phone is not properly rooted either, but there are a lot of crappy apps out there, so I don't know what to believe.
BTW: I don't believe there is any problem with my adb fastboot installation (on MacOS). It was working earlier on. When I type "fastboot devices", it returns: "waiting for any device"
pieemme said:
I am not too sure to have any working recovery at all, right now. If I press all 3 buttons, I get into the Huawei recovery mode, which fails. I am on EMUI 5.1.1 (Nougat) and would like to install a stock recovery to Oreo. If I am able to get to a working bootloader mode, I would like to install this file which seems to be a stock recovery with Oreo (WARSAW L21C432B182_EU_SERVICE_ANDROIDHOST.RU.RAR). Otherwise, I will buy a MicroSD card reader and try copying this installation to the card, which, according to this video (https://www.youtube.com/watch?v=0vDgDXePAR4&feature=youtu.be) should be the last resort, if everything else fails. I would be perfectly happy to return to a working and updated standard EMUI. I'm told that if I installed the OTA version this would not be working correctly on my my phone. According to an app called Rootchecker, my phone is not properly rooted either, but there are a lot of crappy apps out there, so I don't know what to believe.
BTW: I don't believe there is any problem with my adb fastboot installation (on MacOS). It was working earlier on. When I type "fastboot devices", it returns: "waiting for any device"
Click to expand...
Click to collapse
I still can't uderstand you. Can you boot into Android or not? And Does TWRP work? When you device is softbricked, what did you do to brick it?
At one point you say that you can access fastboot by choosing reboot to bootloader in TWRP and then you say that you have no working recovery at all.
Anyway I can't help you with the fastboot thing then and that file isn't Oreo it's an old version of Nougat, B360 and up is Oreo and also B321 witch is Oreo Beta. You can only flash image files in fastboot anyway as that file needs to be unpacked and put on the dload folder on your sd card.
When you want to get to Oreo you can either use service roms from this thread https://forum.xda-developers.com/p10-lite/development/service-rom-b362-c432-upgrade-o-o-n-o-t3813946, you need to copy the two zip files into the dload folder in your SD card. You can also use HWOTA but that wouldn't work since fastboot isn't working for whatever reason. Or when your custom recovery is working you can use HuRUpdater. But you need to be on the newest version of Nougat B210 or B209 to update as otherwise you may brick your phone.
Hey, I have an XT1563 with an SD card integrated into internal storage (which I'm regretting deeply now). Never unlocked bootloader.
Long story short, the screen fried and now won't turn on. Now I'm on a long journey trying to recover the data from it.
I'm also a noob at all of this, here's what I've done so far:
I have the Motorola drivers installed, and just the SDK platform-tools installed.
I can't remember if I kept USB debugging enabled or not, but I figured if I could get it into recovery mode I could enable it through that.
But I can't enter recovery mode. The only thing I'm successfully able to do is enter fastboot mode. I tried doing a flash recovery but of course since bootloader is locked it failed.
So from fastboot, since I can't see the screen, I can only guess at which buttons lead to recovery mode. From images, recovery mode is second on the list, right?
I've tried Vol Down + Vol Up. Didn't work. Also tried Vol Down + Pwr. Also didn't work. Fastboot still says it's in fastboot mode and adb doesn't recognise anything.
The only way my laptop is recognizing the phone is through fastboot. When I plug it in normally it doesn't connect (guessing it jumps into charging mode, but adb still doesn't recognise it)
Can somebody help me here? IIRC Moto X Play does have a built-in recovery mode, right? Is there a way to enter recovery mode through CMD/fastboot functions, or can anyone help me with the hardware buttons to reach it?
Bump
svxyl said:
Bump
Click to expand...
Click to collapse
I'm not sure what is possible. My idea would be:
1. Enter fastboot
2. Fastboot boot twrp
3. Use integrated adb of twrp to access data and shell as well as adb backup. Transfer data using data exchange for Android should also be possible.
Hello everybody, I have a OnePlus 6T that's rooted and has an unlocked bootloader, but USB debugging is off.
I installed LineageOS on it, and it also has an LineageOS Recovery (I didn't use TWRP).
I dropped it recently and now the screen is dead, but the phone is still alive...
So, I'm wondering if I could recover my contacts and hopefully other data as well.
I'm able to enter fastboot, however even when I do `fastboot reboot recovery` it seems that it goes straight to booting the OS.
Maybe it doesn't, I don't know since there isn't a way to see, all in all `adb devices` doesn't show anything.
The reason why I think that it boots the OS, is because my computer's file explorer detects the device and I'm able to change the sound mode (vibrate, no sound, etc.).
Also when trying to use buttons(Power+VolumeDown) to enter recovery it also seems to go to the OS.
I'm trying to enter recovery since, if I understand correctly, ADB works from there.
Every answer is appreciated. Thanks!
Not an expert but
Could you go to fastboot mode and do
fastboot boot TWRP.img
Boot to TWRP?
But if the phone is encrypted, I believe you'll have to decrypt using the screen, which is broken. I don't see a way out..
If you can get to recovery adb should work from there and you can pull the contacts file from wherever it is