I have a Verizon LGV30 that got wet and now the screen is unresponsive. Is there a way to get info from my phone to a computer? It turns on, I've pressed power and vol down to get it to power off and restart but can't do anything else. Booting into safe mode also doesn't do anything. Any ideas? Thanks.
charulo316 said:
I have a Verizon LGV30 that got wet and now the screen is unresponsive. Is there a way to get info from my phone to a computer? It turns on, I've pressed power and vol down to get it to power off and restart but can't do anything else. Booting into safe mode also doesn't do anything. Any ideas? Thanks.
Click to expand...
Click to collapse
When
your device is completely dried
USB debugging got enabled on device
You check this running
Code:
adb devices
to get your data back then to retrieve back the data can be tried via a so-called Android Data Recovery Software what all are Windows apps - some of them are free-of-charge: GIYF.
jwoegerbauer said:
When
your device is completely dried
USB debugging got enabled on device
You check this running
Code:
adb devices
to get your data back then to retrieve back the data can be tried via a so-called Android Data Recovery Software what all are Windows apps - some of them are free-of-charge: GIYF.
Click to expand...
Click to collapse
I have USB debugging on the device, but if I can't get into the phone, how can I check if its running?
charulo316 said:
I have USB debugging on the device, but if I can't get into the phone, how can I check if its running?
Click to expand...
Click to collapse
You connect your phone with PC via USB-cable, power on the phone and then on PC run the ADB command mentioned
Related
I've seen an increase in people who have gotten themselves stuck in a bootloop or can't seem to get the combo right to get into download or recovery mode.
Assumptions:
You have the proper drivers installed
Samsung Driver
Your phone is recognized by your PC
Instructions:
Power Phone off
Extract this folder to your computer
Run batch file for Download or Recovery Mode (it waits to see your phone)
Plug phone into computer
Power phone on
Phone should be detected and go into the proper mode
Thx Red_81, again. Glad to see u put this here for the i777. Appreciate u sharing this. It should provide some good help for many users. :thumbup:
Sent from my SAMSUNG-SGH-I777 using xda premium
So much easier than trying to explain how to install the sdk and then what commands to run. The only problem is you need to have working drivers.
Sent from my SGH-I777 using xda premium
Red_81 said:
I've seen an increase in people who have gotten themselves stuck in a bootloop or can't seem to get the combo right to get into download or recovery mode.
Assumptions:
You have the proper drivers installed
Samsung Driver
Your phone is recognized by your PC
Instructions:
Power Phone off
Extract this folder to your computer
Run batch file for Download or Recovery Mode (it waits to see your phone)
Plug phone into computer
Power phone on
Phone should be detected and go into the proper mode
Click to expand...
Click to collapse
My phone is stuck in boot logo. Computer is detecting phone as "SAMSUNG Android ADB Interface" but adb is not recognizing my phone.
Any ideas?
---------- Post added at 10:29 AM ---------- Previous post was at 10:23 AM ----------
lambition said:
My phone is stuck in boot logo. Computer is detecting phone as "SAMSUNG Android ADB Interface" but adb is not recognizing my phone.
Any ideas?
Click to expand...
Click to collapse
Never mind. I just got it working.
Had to just enter adb command directly. wait-for-device is not working for my phone for some reason.
If you get stuck there again, unplug and plug in the device again.
Sent from my SGH-I777 using xda premium
Adb kill server, adb start server.
Sent from my GT-I9100 using Tapatalk 2
Phalanx7621 said:
Adb kill server, adb start server.
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
Script already does that
Sent from my SGH-I777 using xda premium
Thanks
Thanks i was tinkering with a noria 7" tablet, which hasn't worked right since i got it but for 65 bucks its to be expected, but i used sdk manager to get it to register on my computer as an android adb device and for some reason i tried to turn the wifi on and it crashed and got stuck in a boot loop idk why. like i said hasn't worked right since i bought it. But i did use adb portable like you said to get into recovery mode and it worked great thanks! For other noria users when i figure out how to flash a rom to it i'll start a section here on xda as soon as i figure it out. Thanks again
Any suggestions if ADB doesn't see it?
- Phone was working fine in the morning and at lunch I noticed it was off.
- Try to turn phone back on and it is stuck at the samsung menu like everyone else.
- Soft and hard reset change nothing.
- Neither recovery nor download mode works using every key combo that I've seen suggested.
- Computer detects a device but "USB Device not recognized" and ADB can't see any devices (and I know it is set up correctly as I have the full SDK installed and known to be working).
- Charging still works fine and the battery is now at 100%
- Phone is NOT rooted and has no special apps or any recent changes to change the situation (not even app updates since a few weeks)
I'm not sure what else to do. I will probably let it sit for a few days without a battery, but otherwise I would open it up and see if there is some mechanical/electrical issue like a short or something somewhere. Pretty sure this is a software issue though. Any ideas?
BrockSamsonFW said:
Any suggestions if ADB doesn't see it?
- Phone was working fine in the morning and at lunch I noticed it was off.
- Try to turn phone back on and it is stuck at the samsung menu like everyone else.
- Soft and hard reset change nothing.
- Neither recovery nor download mode works using every key combo that I've seen suggested.
- Computer detects a device but "USB Device not recognized" and ADB can't see any devices (and I know it is set up correctly as I have the full SDK installed and known to be working).
- Charging still works fine and the battery is now at 100%
- Phone is NOT rooted and has no special apps or any recent changes to change the situation (not even app updates since a few weeks)
I'm not sure what else to do. I will probably let it sit for a few days without a battery, but otherwise I would open it up and see if there is some mechanical/electrical issue like a short or something somewhere. Pretty sure this is a software issue though. Any ideas?
Click to expand...
Click to collapse
To use ADB you must have USB debugging enabled in settings under Developer Options. If you don't keep this enabled all the time, and it wasn't set when the phone stopped working, then ADB is not an option.
Hopefully, you can get into download mode. For reference, here are the ways I know of, in case you haven't tried something here:
If you can get into download mode, you should flash the stock firmware and then perform a wipe data/factory reset from within stock recovery.
There are several ways to put the phone into download mode. You should try all of them that you can before you give up.
Recovery mode:
With the phone off (and not connected to the computer), and battery installed, hold all three buttons, vol- vol+ pwr continuously until the initial boot screen appears the second time.
Download mode:
1. With the phone off and connected to the computer via USB cable, and battery installed, hold all three buttons, vol- vol+ pwr.
2. With the phone off and battery installed, hold vol- and vol+ (but not pwr) while plugging in the USB cable.
3. With the phone off and battery installed, hold vol- (but not vol+ or pwr) while plugging in the USB cable.
4. Attempt each of the above three options with the battery removed from the phone. The computer will supply the power to the phone.
5. Use Android Debug Bridge (adb) which will only work if USB debugging has been already turned on in Developer Options, since you can't boot into the system to turn it on. With the battery installed and the phone connected to the pc via USB cable, use the command "adb reboot download".
6. Use a USB jig. With the battery installed insert the USB jig into the USB connector of the phone. Some have reported that this method works when no other method would work.
creepyncrawly said:
To use ADB you must have USB debugging enabled in settings under Developer Options. If you don't keep this enabled all the time, and it wasn't set when the phone stopped working, then ADB is not an option.
Hopefully, you can get into download mode. For reference, here are the ways I know of, in case you haven't tried something here:
If you can get into download mode, you should flash the stock firmware and then perform a wipe data/factory reset from within stock recovery.
There are several ways to put the phone into download mode. You should try all of them that you can before you give up.
Recovery mode:
With the phone off (and not connected to the computer), and battery installed, hold all three buttons, vol- vol+ pwr continuously until the initial boot screen appears the second time.
Download mode:
1. With the phone off and connected to the computer via USB cable, and battery installed, hold all three buttons, vol- vol+ pwr.
2. With the phone off and battery installed, hold vol- and vol+ (but not pwr) while plugging in the USB cable.
3. With the phone off and battery installed, hold vol- (but not vol+ or pwr) while plugging in the USB cable.
4. Attempt each of the above three options with the battery removed from the phone. The computer will supply the power to the phone.
5. Use Android Debug Bridge (adb) which will only work if USB debugging has been already turned on in Developer Options, since you can't boot into the system to turn it on. With the battery installed and the phone connected to the pc via USB cable, use the command "adb reboot download".
6. Use a USB jig. With the battery installed insert the USB jig into the USB connector of the phone. Some have reported that this method works when no other method would work.
Click to expand...
Click to collapse
Thanks a ton for the reply. Recovery mode does not work but using your methods I AM able to get it to boot to download mode. If it matters, USB debugging was and should still be enabled.
Now the question is... is there any way to backup the phone from this state or get into a state where I could back it up? I don't really care about my pictures or anything else as those were recently backed up but some app settings would be nice to save (Clash of Clans village without Google+, ugh). I'm going to do more research on the next step myself but if you have any suggestions or information to point me in the right direction I would of course appreciate that as well. Thanks for getting me this far though!
BrockSamsonFW said:
Thanks a ton for the reply. Recovery mode does not work but using your methods I AM able to get it to boot to download mode. If it matters, USB debugging was and should still be enabled.
Now the question is... is there any way to backup the phone from this state or get into a state where I could back it up? I don't really care about my pictures or anything else as those were recently backed up but some app settings would be nice to save (Clash of Clans village without Google+, ugh). I'm going to do more research on the next step myself but if you have any suggestions or information to point me in the right direction I would of course appreciate that as well. Thanks for getting me this far though!
Click to expand...
Click to collapse
It's pretty difficult to recover information from the data partition when the phone is in a state such as you describe. Maybe the developers and technogeeks can do it. I can't. However, depending on where the game saves it's game data, you may be fine. If the game data is saved to the USB memory (internal sd card) then it will still be there once you flash new firmware. Your pictures should also be fine, since they are on the sdcard.
I've got a Sprint Galaxy S6 SM-G920P (original stock firmware) which I was doing a routine battery replacement on, but when I reassembled it and tried to power it up, it got stuck with a dark screen and throbbing blue indicator LED. I'm not able to do a volume-down + power reset, and I tried multiple times to boot into safe mode, but with the screen black I can't tell when to push volume down.
When I connect it to a PC via USB, it's detected as a USB device but does not link up as an MTP device, so I can't access the directories, and KIES won't work. I installed android-data-recovery, but the SM-G920P was not on the list of devices for broken phone recovery.
I've written the phone off, but I'd really like to recover the photos. Any ideas or suggestions? I don't mind soldering.
Thanks,
LR
larry5b6 said:
I've got a Sprint Galaxy S6 SM-G920P (original stock firmware) which I was doing a routine battery replacement on, but when I reassembled it and tried to power it up, it got stuck with a dark screen and throbbing blue indicator LED. I'm not able to do a volume-down + power reset, and I tried multiple times to boot into safe mode, but with the screen black I can't tell when to push volume down.
When I connect it to a PC via USB, it's detected as a USB device but does not link up as an MTP device, so I can't access the directories, and KIES won't work. I installed android-data-recovery, but the SM-G920P was not on the list of devices for broken phone recovery.
I've written the phone off, but I'd really like to recover the photos. Any ideas or suggestions? I don't mind soldering.
Thanks,
LR
Click to expand...
Click to collapse
Have you had any luck recovering the data? I have a stock Galaxy S6 from Sprint with a broken screen. No screen lock is enabled, no passcode. I don't have ADB debugging enabled on the phone so all the recovery software out there isn't working. If I somehow figure out how to recover anything off of this phone I'll let you know the steps I've taken
atvcache said:
I don't have ADB debugging enabled on the phone
Click to expand...
Click to collapse
As long as you cant't establish an USB-connection ( read: ADB connection ) you can't revover any data: ADB is the door to any Android device.
jwoegerbauer said:
As long as you cant't establish an USB-connection ( read: ADB connection ) you can't revover any data: ADB is the door to any Android device.
Click to expand...
Click to collapse
I figured as much for as long as I can remember ADB yes has always been the doorway. It'd be nice if ADB was a built in software standard, not only an option you can choose to turn on and off but with security features that would enable people that break their screens to still be able to access their data with a code only verified owners can get from their service providers or manufacturers, it would also stop criminals from being able to access peoples data. ADB is an outdated/old standard in my opinion. In concept it's great but if you don't have it turned on what good is it.... if you need access to your phone through an OTG cable. If you do have it enabled and your phone is stolen, screen locks can be bypassed. We need a new type of ADB, hopefully that becomes a thing in the near future! How many people are tech-savvy or even interested in these type of things, less than the majority. How many people lose memories along with other forms of data and money because of these old standards.....
Hello, today my phone suddenly started to hang and i rebooted it (ROG Phone 1). After the reboot, i got the "Encryption unsuccessful" screen.
Is there any chance to bypass this screen, or save any data that is left on this phone?
The Bootloader is unlocked, but there is no TWRP. My Laptop says it cannot recognize the phone when plugging in the USB cable. Fastboot works fine but it looks like adb does not work. ANY CLUE would be HIGHLY appreciated!
https://img.xda-cdn.com/9uIT10ztA4a...AAAAAD0g/tMxR8lgDVI8/w311-h431-k/IMG_2301.JPG
Einheit-101 said:
Hello, today my phone suddenly started to hang and i rebooted it (ROG Phone 1). After the reboot, i got the "Encryption unsuccessful" screen.
Is there any chance to bypass this screen, or save any data that is left on this phone?
The Bootloader is unlocked, but there is no TWRP. My Laptop says it cannot recognize the phone when plugging in the USB cable. Fastboot works fine but it looks like adb does not work. ANY CLUE would be HIGHLY appreciated!
https://img.xda-cdn.com/9uIT10ztA4a...AAAAAD0g/tMxR8lgDVI8/w311-h431-k/IMG_2301.JPG
Click to expand...
Click to collapse
It seems that you will have to perform a factory reset. Have you backed up your data to Google Drive?
Einheit-101 said:
Fastboot works fine but it looks like adb does not work.
Click to expand...
Click to collapse
Fastboot deals with phone's bootloader, whereas ADB deals with phone's Android OS. Two completely different things
ADB will only work if USB Debugging got enabled in phone's Developer options.
So i guess there is no way to recover the phone in any way....
Except of course full wipe and rip
I seem to have gotten my N200 in a state where it will not power on. No screen display, no vibrations, and unresponsive to volume and power buttons (standalone or combination). It's a DE2118, T-Mobile variant, network locked and not rooted.
Here are the conditions leading up to it:
The phone was plugged in to my PC via USB, (through a USB hub).
My Sim/SD tray was ejected.
I had been using an ADB shell to disable-user some apps and check out some various PM commands.
I did not terminate the ADB shell before powering down from the phone.
Once powered off, I held the volume up+volume down+power buttons to attempt to check out the recovery mode. I've never entered recovery mode before on this device.
The USB cable was still plugged in and I could hear the USB new device sounds on my PC a few times while I did this but didn't think anything of it.
Nothing ever appeared on the screen and pushing any of the buttons seem to provide no response.
Battery usage was at least 80%, if not closer to 90% before this happened.
It almost seems like the device is powered on and running as there feels like there's some very slight warmth on the back panel, near the center just under the camera area but I might just be imagining the warmth.
I'm aware that it needs to be network unlocked before it can be rooted as per other threads and I have not tried any root methods.
I still have my ADB shell dialog up but there really isn't much interesting in it besides a lot of the command help dialog.
What are my options?
Note: I recently installed the Jan 6th android 11 security update maybe a day before.
Edit: For anyone looking at this later, the phone came back after a complete battery drain and partial recharge and I was able to replicate the bricked state performing the same thing, usb debugging on, plugged in to usb hub on pc, shut down phone, then holding all 3 buttons down for a while.
Windows or Linux pc?
Does your device show up in device manager if windows?
If Linux, do you see the device if you run
adb devices or fastboot devices?
mthous01 said:
Windows or Linux pc?
Does your device show up in device manager if windows?
If Linux, do you see the device if you run
adb devices or fastboot devices?
Click to expand...
Click to collapse
I'm using Windows 7 mainly.
It shows up in device manager when I plug in the USB but with error code 28, unknown driver.
In Win7, "adb devices" lists a blank line for devices.
In Linux, "adb devices" lists a blank line for devices.
In Linux, "fastboot devices" has no output at all.
If your phone is showed in device manager you should be able to give him his life back...had the same situation long time ago with my oppo find 7..
Try this, and see if it'll recognize you for MSM download.
mthous01 said:
Try this, and see if it'll recognize you for MSM download.
Click to expand...
Click to collapse
Will give it a try. Going to be a few hours to DL the file as I'm on an extremely slow connection atm.
Well, I think that made it worse. Couldn't get the Qualcomm CAB drivers working on Windows 7, but got it through Windows Update. The MSM tool went through the process fully but afterward I unplugged the device and tried to boot, still no response, nothing on screen, no vibration. Now when I plug my device back in to the USB, I have an endless new usb device noise and windows says "Unknown Device". Device manager refreshes constantly while its plugged in. Looking back I should have probably tried ADB first before running the MSM tool.
After almost 24 hours of being unplugged, I tried plugging it in again and it finally had some signs of life with the low battery warning and then TMobile splash screen+vibration+sound after about 5 minutes. Still waiting on it to charge up for now. Probably just needed to be power cycled in the end instead of attempting to flash anything. I sure do miss the days of removable batteries.
Mtrlns said:
Probably just needed to be power cycled in the end instead of attempting to flash anything.
Click to expand...
Click to collapse
In the future, you can power cycle the device by holding all three buttons on the phone for 30 seconds while it isn't plugged into a PC.
lzgmc said:
In the future, you can power cycle the device by holding all three buttons on the phone for 30 seconds while it isn't plugged into a PC.
Click to expand...
Click to collapse
I had tried that yesterday to no avail. Was very strange. Everything seems to be working as normal now, though factory reset from running the MSM tool. I'm wondering if I'd be able to duplicate the issue again.
Could not replicate with USB debugging off and plugged directly in to my PC's USB port, but turning on USB debugging and plugging in to my USB hub, shutting down the phone, and then power cycling with all three buttons brought the same bricked state.
Don't know for sure if the USB port matters but while bricked plugging in to the USB hub always gives a USB device error sound. Going directly on PC it connects fine as a new device (as QUSB_BULK without drivers or Qualcomm HS USB QDLoader 9008 with drivers). ADB/Fastboot commands from PC's command line don't seem to do anything.
I did notice the fastboot menu show up on screen for a second when power cycling this time and I don't recall it appearing the first time. I think i may have had "advanced reboot" turned on the first time, while it was off this time.
Powercycling actually reset it this time.
Possible solution
It would seem that you can force MSM to write both a and b slots, which might fix your issue. Might be worth a shot
Note: If this swaps you to the Tmobile software, there's no guarantee you'll have anything but a phone that cannot be bootloader unlocked again. Since unlocked have no unlock token, trying to do so with a phone that isn't technically Tmobile may be an issue.
Just had the same problem. Holding all buttons for 30 seconds worked.
if you bricked it and you have tmobile variant you can restore it weather you have a locked or unlocked bootloader.
you have to get your phone in EDL mode, once in EDL mode you will see the "QUSB_BULK_CID" in device manager. you will then need to install qualcomm drivers (if done manually you will have to endable windows test mode, if you use the qualcomm USB driver installer then it will do it for you and you will be in test mode upon next windows reboot.) Reboot windows in TEST MODE. NOTE: i said WINDOWS TEST MODE... Once in windows test mode the driver should function and look normal in device manager. From there just open the MSM tool for your version of Nord N200 and flash and wait about 3-5 minutes. Reboot the phone and you are back in Oxygen OS.
Tips and extra Files needed below:
for the tmobile NORD N200 MSM tool
Index of /list/Unbrick_Tools/OnePlus_Nord_N200
The installer for the QUALCOM USB drivers can be found here at this website (ONLY use the QUALCOMM drivers from here, do not use any other file as it is for a different phone):
droidwin.com/unbrick-oneplus-7-pro/
once done unbricking and restoring your phone you can then exit windows test mode by running
bcdedit -set TESTSIGNING OFF
at the windows command prompt as ADMINISTRATOR.
Hello guys.
I have a unique problem here. I have a Redmi Note 10 with a broken black screen. I want to access the phone to be able to backup all my files and if possible to use it with my PC with Vysor or Cast. Because I am still not able to repair the screen right now. And I would also like to have backed up my files before it is repaired.
So I've tried many youtube tutorials to access the phone but it seems none of them can help me because not only can't I see anything on the screen but also I have a very complicated pattern so it is impossible to guess the pattern with a mouse. The screen itself is dead so it doesn't respond to touch.
But I want to believe that I can be able to access my phone because my phone is rooted with Magisk and I'm running a custom rom - Crdroid version 8.9 Android 12. I also have a PC. I am able to get into Crdroid recovery when I press volume up + power button. I am also able to enter into fastboot mode when I press volume down + power button.
I'm stating all this because I want to know if there is any way I can be able to backup my files or access the phone with my laptop. I saw that one can be able to access their phone if Developer Options are turned on. Mine were turned off before the screen broke. Is there any way I can be able to turn them on in my situation?
Please help.
try to boot twrp in fastboot.
fastboot boot twrp.img
i think mtp is activated automatically. problem is if it will ask for the unlock pattern on twrp
Okay
devcon69 said:
try to boot twrp in fastboot.
fastboot boot twrp.img
i think mtp is activated automatically. problem is if it will ask for the unlock pattern on twrp
Click to expand...
Click to collapse
So if I boot into TWRP, the computer will be able to read my files automatically?
i think there is no hope in your state...
complicated screenlock + fully dead screen + developer options turned off
if you had USB Debugging enabled you could use this software to use the phone on the PC like in the picture because i have a phone in the same status like yours but USB Debugging was enabled.
with twrp you can save your internal storage files but it will ask for pattern and you won't be able to access those files without unlocking it.
so i guess the only way is trying to guess the pattern with a mouse... i know that will be really hard but is the only thing i can suggest.
otherwise just take your phone to a repair shop
Oka
alonsoj636 said:
i think there is no hope in your state...
complicated screenlock + fully dead screen + developer options turned off
if you had USB Debugging enabled you could use this software to use the phone on the PC like in the picture because i have a phone in the same status like yours but USB Debugging was enabled.
with twrp you can save your internal storage files but it will ask for pattern and you won't be able to access those files without unlocking it.
so i guess the only way is trying to guess the pattern with a mouse... i know that will be really hard but is the only thing i can suggest.
otherwise just take your phone to a repair shop
Click to expand...
Click to collapse
Okay. I guess I'll just take it to the repair shop then since it's impossible to guess that pattern. Thank you for your reply.
alonsoj636 said:
i think there is no hope in your state...
complicated screenlock + fully dead screen + developer options turned off
if you had USB Debugging enabled you could use this software to use the phone on the PC like in the picture because i have a phone in the same status like yours but USB Debugging was enabled.
with twrp you can save your internal storage files but it will ask for pattern and you won't be able to access those files without unlocking it.
so i guess the only way is trying to guess the pattern with a mouse... i know that will be really hard but is the only thing i can suggest.
otherwise just take your phone to a repair shop
Click to expand...
Click to collapse
Are there any adb commands that can be used to backup data?
RichezCool said:
Are there any adb commands that can be used to backup data?
Click to expand...
Click to collapse
backup/restore commands needs USB Debugging enabled afaik , so sadly there's no way
alonsoj636 said:
backup/restore commands needs USB Debugging enabled afaik , so sadly there's no way
Click to expand...
Click to collapse
Okay. Thank you.