I'm checking out my sister's phone that she dropped and broke the screen. Device boots up, since I can feel the vibration and hear alarms but the screen is dead. Debugging was not enabled, bone stock. I can see it in fastboot, but I'm not sure if there is a specific mode to be in to allow ADB for this device. I've read Downloader mode, which should be 3 spots below where Fastboot drops you, but I get no change. Anyone have a suggestion on how to pull the old data off?
Atemi1337 said:
I'm checking out my sister's phone that she dropped and broke the screen. Device boots up, since I can feel the vibration and hear alarms but the screen is dead. Debugging was not enabled, bone stock. I can see it in fastboot, but I'm not sure if there is a specific mode to be in to allow ADB for this device. I've read Downloader mode, which should be 3 spots below where Fastboot drops you, but I get no change. Anyone have a suggestion on how to pull the old data off?
Click to expand...
Click to collapse
You can only have adb connectivity when booted in the OS and usb debugging must be ON. You must also allow your computer RSA key from your phone at the first attempt to use adb.
adb can also be used form a custom recovery (even with debbug off) but if the phone was still stock it's bootloader is probably locked... Unlocking the bootloader will wipe data (and a working screen is also needed to unlock it).
At this point I think replacing the display would be the only option...
Sorry
alray said:
You can only have adb connectivity when booted in the OS and usb debugging must be ON. You must also allow your computer RSA key from your phone at the first attempt to use adb.
adb can also be used form a custom recovery (even with debbug off) but if the phone was still stock it's bootloader is probably locked... Unlocking the bootloader will wipe data (and a working screen is also needed to unlock it).
Sorry
Click to expand...
Click to collapse
Pretty much confirmed my thought. Thanks for the glance.
Related
I woke up this morning and my Pixel is dead. Completely unresponsive, can not get into bootloader from the phone.
Any ideas?
I got a replacement ordered through Google, and am using my Nexus 6 for now. It's a little frustrating that they authorize the replacement cost of the phone to process the order when I've got multiple credit cards on file with my Google account (which goes back to when Gmail was invite only) but I'll deal with it.
Just went through this yesterday. Put a hold on my card to replace even though I paid in full for the first one. So now I'm out the cost of 2 and have no phone.
Are you guys still stock?
magnumtripod said:
Are you guys still stock?
Click to expand...
Click to collapse
Yes. Stock. Bootloader unlocking enabled in developer settings but not unlocked. Running the latest OTA.
This is precisely why I always unlock the bootloader immediately after I pull my Nexus (now Pixel) devices from the packaging.
Sorry to hear about the issues. Hope you get your replacements soon.
sn0warmy said:
This is precisely why I always unlock the bootloader immediately after I pull my Nexus (now Pixel) devices from the packaging.
Sorry to hear about the issues. Hope you get your replacements soon.
Click to expand...
Click to collapse
Having the bootloader unlocked would not help in this case, since the phone is completely dead. It will not connect to the computer at all. If I could connect it I could unlock the bootloader through adb and try reinstalling the software. With a complete unresponsive brick, I'm pretty much out of ideas.
atlp99 said:
Having the bootloader unlocked would not help in this case, since the phone is completely dead. It will not connect to the computer at all. If I could connect it I could unlock the bootloader through adb and try reinstalling the software. With a complete unresponsive brick, I'm pretty much out of ideas.
Click to expand...
Click to collapse
Having the bootloader unlocked very well could have helped in this situation, even if the screen won't turn on. There have been a few times that I had phones go completely unresponsive on me and appear to not turn on at all. But following the procedure of booting the phone into the bootloader (power/volume down), allowed me to connect the phone to the computer and communicate with it using fastboot commands. Even with nothing appearing on the phones screen.
This allowed me to fastboot wipe everything and flash a new factory image. The phone booted up just fine afterwards.
Obviously, I can't say with 100% certainty that this would have worked in your case but I've been in your exact situation, more than once, with a phone that was nothing more than a paperweight. Having the bootloader unlocked did solve the problem each time.
sn0warmy said:
Having the bootloader unlocked very well could have helped in this situation, even if the screen won't turn on. There have been a few times that I had phones go completely unresponsive on me and appear to not turn on at all. But following the procedure of booting the phone into the bootloader (power/volume down), allowed me to connect the phone to the computer and communicate with it using fastboot commands. Even with nothing appearing on the phones screen.
This allowed me to fastboot wipe everything and flash a new factory image. The phone booted up just fine afterwards.
Obviously, I can't say with 100% certainty that this would have worked in your case but I've been in your exact situation, more than once, with a phone that was nothing more than a paperweight. Having the bootloader unlocked did solve the problem each time.
Click to expand...
Click to collapse
I didn't say it but I tried that.
The phone doesn't show up at all on the computer. No USB connection at all. If it connected, I could unlock the bootloader through adb and reflash.
atlp99 said:
I didn't say it but I tried that.
The phone doesn't show up at all on the computer. No USB connection at all. If it connected, I could unlock the bootloader through adb and reflash.
Click to expand...
Click to collapse
What? The phone is unresponsive and the screen won't turn on. So there is no way you could unlock the bootloader through ADB because you need the phone's screen functioning in order to check "Yes" for the final prompt of unlocking the bootloader.
With that said, even though the computer doesn't recognize the phone as a USB connection, that doesn't mean it wouldn't communicate with the phone using fastboot commands. Like I said, myself (and many others on this forum) have been in your EXACT situation with a completely unresponsive phone which the computer wouldn't recognize as a connected USB device. However, that didn't stop the computer from recognizing/communicating with the phone via fastboot commands.
It's a moot point now that your replacement is on the way. But I'm still convinced that if your bootloader was unlocked you could have saved the phone.
sn0warmy said:
What? The phone is unresponsive and the screen won't turn on. So there is no way you could unlock the bootloader through ADB because you need the phone's screen functioning in order to check "Yes" for the final prompt of unlocking the boot loader.
With that said, even though the computer doesn't recognize the phone as a USB connection, that that doesn't mean it wouldn't connect to the phone using baseline fastboot commands. Like I said, I've been in your EXACT situation with a completely unresponsive phone and the computer would not prompt me that a new USB device was connected even when the phone was plugged into it. However, that didn't stop the computer from recognizing/communicating with the phone via fastboot commands.
It's a moot point now that your replacement is on the way. But I'm still convinced that if your bootloader was unlocked you could have saved the phone.
Click to expand...
Click to collapse
If it would connect through adb (even if the phone was unresponsive) fastboot OEM unlock would work. I forget off the top of my head what the new command is, but at this point it doesn't respond to that at all.
atlp99 said:
If it would connect through adb (even if the phone was unresponsive) fastboot OEM unlock would work. I forget off the top of my head what the new command is, but at this point it doesn't respond to that at all.
Click to expand...
Click to collapse
"fastboot oem unlock" is just the first part. You still need a responsive phone to unlock the bootloader by hitting 'volume up' and then 'power' as the final step to unlock the bootloader. The computer won't recognize the phone via ADB because the phone is unresponsive and won't power up fully. But just because the computer won't recognize/communicate with the phone via ADB commands, doesn't mean it wouldn't recognize/communicate with it via fastboot commands.
It's pretty common that people have run into an issue where their phone won't recognize ADB commands but still recognizes fast boot commands, especially with bricked phones.
https://www.google.com/search?clien...not+working+but+fastboot+is&ie=UTF-8&oe=UTF-8
I'm telling you, if your bootloader was unlocked, I'd bet money that you would still be able to communicate with your bricked phone using fastboot commands. The inability to communicate with your phone using ADB commands does not negate that.
Possible workaround...
Try holding the power and volume down for 20 seconds no matter what the phone does, or whether you even see anything on the screen, and if you get nothing, then try to do the same with volume up. I have had phones get stuck "in between" modes, for example trying to leave bootloader, recovery, or whatever else, and got stuck on a black screen, when the phone was in fact on. Everyone else's responses here were legit, though. I agree totally on the communicating with the phone via fastboot etc. If you can get it to bootloader even with the screen off, you can flash the entire phone. Of course this means you may lose items saved on the device.
I had this same issue happen...black screen but could hear the phone connect to the computer but fastboot wouldn't work...tried every possible combination oh buttons to get into anything and could...had to replace
http://forum.xda-developers.com/pix...ader-total-t3503963/post69713209#post69713209
Me too.
Well I got the replacement from Google on Wednesday and everything is running fine.
They did send a new phone, in retail packaging with all new chargers and cables. At least it wasn't a refurbished one.
Hello,
So my mom owns a Xperia Z3, and each time she would turn it on, the System UI would keep crashing. I didn't know why, but I thought I would boot into recovery and clear the cache/dalvik and see if that fixes anything. I'm not sure if it would, but I'm putting that investigation on hold for now because I noticed a bigger problem - I can't even boot into recovery or the bootloader!
So here is what I did: I enabled USB debugging, connected the phone to my PC, accepted the RSA fingerprint and opened up to command prompt. Ensuring the device was there, I typed `adb devices` and it was successful. Then, I typed `adb reboot bootloader`. The phone just gave me a black screen. After about a minute I decided to turn the phone off, and so I did, and it rebooted into the ROM. Then, when the device restarted and it connected to the PC, I went through the steps to ensure the device was connected and I typed `adb reboot recovery`. The device simply rebooted into the ROM. I looked at a few articles on how to start either recovery or the bootloader using key combinations, but it was of no use.
I have never really messed with a Sony phone before; I use a Nexus 5X and the most I did was install LineageOS. Pardon my ignorance if I am missing something that only Sony phones have, but to my understanding, the partitions should be identical to that of my phone (the names, of course, not the images)
I appreciate anyone who takes the time to help me (and therefore my mom) with this issue.
Have you solve your problem?
Have the same problem ... any solutions?
I know this is old but for the Z3 (or at least my D6633) the bootloader (aka fastboot) mode is indicated by a blue notification light, if you have that, you should be able to use
Code:
fastboot devices
and see your phone. I still couldn't boot into any recovery mode, stock or custom, and would appreciate any help with the matter.
Anyone, please help, I charge the phone overnight at normal, wake up in the morning the phone is in bootloop Forever!
(It's Samsung A51 Global version, A515F with the 5/18 firmware stock ROM, NO rooting, No custom ROM)
I even try Reiboot's repair function multiple times and it didn't work. It did re-apply the latest Firmware to the phone for me but still cannot boot to android.
The phone is able to boot to recovery mode only, I cleaned up the dust of the internal also as it has no warranty at all.
I am not attempting to fix the phone, I just wanna pull all the files of the internal memory back before I can factory reset it in Recovery mode.
I have the USB debugging activated. Any questions or details please ask, I can replace it with a new phone, but at least I can pull the data out, or better yet, able to boot it to the android system, I tried the safe mode method NOT working.
Any helps appreciated, from my history of android phones start with the Nexus One, only experiences with broken screens, touch screen not working...... never experience like this cannot access anything before
To pull out data out from phone requires you can access phone in ADB mode. My guess is this isn't possible at all due of phone's boot-looping, what means a stable ADB connection can't get established.
jwoegerbauer said:
To pull out data out from phone requires you can access phone in ADB mode. My guess is this isn't possible at all due of phone's boot-looping, what means a stable ADB connection can't get established.
Click to expand...
Click to collapse
I can access Download mode is that enable the ADB, or when it's in download mode if I plug it to a PC, it'll detect the system like a thumb drive?
Hi people.
I have a Pixel 2 which dropped and contains a file I really want to get a hold of. After it dropped, the screen was completely black, but the phone was responsive. I can't seem to get it to work in Recovery, so assuming it's dead and not just BSOD.
Now, I could still "use" it via my smartwatch, but obviously after rebooting, I now need to type in my pin before I can simply unlock it with my fingerprint. I seem to be able to do this, as, when I restart the phone, it doesn't mount as USB, but when I then plug in a keyboard and type "space space pin enter" after, and then plug it into the PC, it is mounted, but I still can't see any files.
Anybody know if I now still need to enable mass storage instead of MTP or something like that, and what keyboard shortcuts I would need to do this?
Or any other method to get hold of the files?
I have tried adb, but it doesn't see any devices, so I'm guessing developer mode is turned off.
kowalski5233 said:
Hi people.
I have a Pixel 2 which dropped and contains a file I really want to get a hold of. After it dropped, the screen was completely black, but the phone was responsive. I can't seem to get it to work in Recovery, so assuming it's dead and not just BSOD.
Now, I could still "use" it via my smartwatch, but obviously after rebooting, I now need to type in my pin before I can simply unlock it with my fingerprint. I seem to be able to do this, as, when I restart the phone, it doesn't mount as USB, but when I then plug in a keyboard and type "space space pin enter" after, and then plug it into the PC, it is mounted, but I still can't see any files.
Anybody know if I now still need to enable mass storage instead of MTP or something like that, and what keyboard shortcuts I would need to do this?
Or any other method to get hold of the files?
I have tried adb, but it doesn't see any devices, so I'm guessing developer mode is turned off.
Click to expand...
Click to collapse
If I remember correctly you can still use fastboot boot with a locked bootloader. In that case download TWRP, reboot phone into bootloader and do fastboot boot /path/to/twrp.img. That should get you a storage device once twrp is booted, then pull the file out
muhammad42620 said:
If I remember correctly you can still use fastboot boot with a locked bootloader. In that case download TWRP, reboot phone into bootloader and do fastboot boot /path/to/twrp.img. That should get you a storage device once twrp is booted, then pull the file out
Click to expand...
Click to collapse
Thanks so much Muhammad. The problem is, the screen is completely black, so I can't see anything, even in the bootloader. I guess I can install TWRP from the browser on my PC, but not sure if it will install until I've unlocked the phone, for instance, which brings me back to square one. But I'll see if that's possible using my other phone, though it still runs Android 5, not sure if they will behave the same.
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