Hi all,
i'm trying to access my broken phone (Samsung Galaxy A5 (2017)) by adb. Sadly - the device wasn't never set to debug mode // developer mode enabled. The display is broken - completely - you can't see anything but the device is responding to hardware keys. I'm able to start and shutdown the device. In normal mode - the device is detected on my pc - but only in charging mode. I can't access the storage drives at all.
I tried to start the download mode (as far as google search helped) by
- turning the device off (pressing & hold power % vol down)
- just before it vibrates - release the keys and press & hold power + home + vol down
- waiting a short time
- pressing vol up
this should start the device in download mode - and i'm able to see it at the device manager in windows 10.
BUT - if i start ADB devices - it's not listed / nor i'm able to connect at all.
Do you have any idea whats wrong - what i'm doing wrong to get a grip on the device?
My plan is - to access the device via ADB and enable the debug / developer mode. Then - starting it up again and bridge the screen via scrcpy to my computer. Then - in theory - i would be able to access the device via scrcpy and setup the sync.
If somebody got any other idea how i can access the phone - please let me know. Please keep in mind - the touchscreen is not working at not all.
Thank for your feedback
FatBulldog
Hi, I am in a similar situation and just starting to scan this forum. Phone has ~8G of pics/vids etc. so if you find a solution that forgoes a screen replacement let me know.
Likewise. I bought a cheap USB-C to HDMI connector but it won't work on my SM-520F. I have an OTG and a USB keyboard does work but I can't see a picture so the keyboard is pretty pointless!
Is there any method of doubling the screen when you can't see it on the phone?
I wound up biting the bullet and buying a new screen.
Related
Dear all,
My Universal has been stuck in the bootloader screen after upgrade with DOPOD Rom. I have searched thru the threads but have had no luck so far. Has anyone out there experienced this? Please help me out
Thank you
Ken
STUCK RELEASE!?!?!
Well.very easy for start.
ROM Upgrade Failure
It is possible, in a very small number of ROM upgrades, that the upgrade could fail. The following are workarounds to get the device working and upgraded.
Device stuck in 'Bootloader' mode
When this happens the device screen will be blank except for the words:
Serial v 1.00a
The word [Serial] should change to [USB] when the cradle is plugged into the PC, and the version number below this will vary. When you get this screen, a soft or hard reset will not make any difference.
It is still possible to run the ROM upgrade file again, without using Activesync (Activesync will not restart anyway).
• Firstly unplug the USB cradle and reboot the PC
• Plug the cradle back into the USB port (this must plug directly into the USB port and not into a USB Hub / adaptor).
• Now run the ROM upgrade file again from the PC. This should just run as per normal and correctly reflash the device.
If it is still not working,try this
• Press & hold the power button
• Press & hold the Backlight button
• Push the stylus into the soft reset hole - until you see the word [Serial] on the screen.
• You should now be able to follow the upgrade process above for a device stuck in Bootloader mode.
It work for me,goodluck
henning
find an attachment how to fix this
Many thanks, HENNING RAS
My device is up & running again. Thanks
Ken
Morning, im following this guide - http://forum.xda-developers.com/android/development/guide-root-method-lg-devices-t3049772 and am on the section --
=====
6.) Well that was easy , let's continue (Now that we have the files on our device we want to put our device is download mode)
(Note this method may vary from device to device)
Power off your device
When the device is powered off, hold volume up and insert a USB cable connected to the PC
Wait for the drivers to install
=====
But it just sits there on 0% telling me to not remove the the usb, it never moves. If i remove the cable i have to remove the battery to restart it and then it boots like normal. Tried 3 times now and have the same issue.
Do i just keep trying? Am i missing something?
Thanks in advance for your help.
Hey everyone,
I've got my phone startet now, but I still do need a kind of "backdoor", so I can restart the phone, if the button stops working again or if I loose this small plastic-piece again.
Furthermore it would be really cool if I would not have to dismantle the phone to turn it on
First of all I thought about ADB, but ADB doesn't recognize my device anymore.
I don't know why. My USB-Debugging is (and was) activated, but the PC isn't authorized yet (since it doesn't recognize the ADB it won't ask me for permission).
How can I fix this? I already tried to restart (pc and device), reinstall the drivers and kill/start the sever. Nothing worked.
But I'm also open for new ways.
I thought of some possibilities:
1. Change the "action_on_power_plug_connect": Is there a way to change the action my phone does execute when the power plug is connecting? Right now it's just starting to charge mode.
2. Boot on shedule/remote: Is there any app, which got the power to boot the phone, even if it is completely shut down?
I'm thankful for every single advice you can give me here.
Sincerly,
maj0r_tom
~~~~~~~~~
DEVICE INFO:
~~~~~~~~~
System: ColorOS 2.5.1i (Android Lollipop)
Root: Yes, SuperSU
Recovery: Stock Recovery
Hardware buttons working: None :]
---------------------
OLD POST:
---------------------
Hello everyone,
I've just repaired the broken display of my old Oppo Find 7.
Everything worked fine but one thing: The power button does not respond anymore.
It's a small piece of plastic, held in place by a bridge of metal.
When I press it onto the "sensor", it doesn't seem to recognize it.
Everything else is working perfectly - connecting a power source makes the phone start into loading mode.
Is there any way to start the phone without the physical button?
Maybe something beyond fastboot?
Or do you think that any phone-repair shop could help me there?
Sincerly,
maj0r_tom
Edit: The Volume Buttons do not work, too.
I've tried ADB. I could swear, that USB debugging is enabled (used Titanium Backup, it's asking for it on startup).
But ADB does tell me, that the phone is unauthorized.
Edit 2: Volume buttons repaired.
Edit 3: I got it.
The buttons didn't break - they just lost a small piece - a very ****ing small piece.
I did see it dropping from my Vol+ button and could insert it into the power button.
The phone startet, Debugging was enabled. Do I have to check anything else to activate ADB?
Hello, i don't know if my problem is the same but i have the power button don't work too. For restart my phone, i press VOL- when I charged the phone. He boot in recovery and next i reboot system. If a hardware solution is possible, tell me.
maj0r_tom said:
Hey everyone,
I've got my phone startet now, but I still do need a kind of "backdoor", so I can restart the phone, if the button stops working again or if I loose this small plastic-piece again.
Furthermore it would be really cool if I would not have to dismantle the phone to turn it on
First of all I thought about ADB, but ADB doesn't recognize my device anymore.
I don't know why. My USB-Debugging is (and was) activated, but the PC isn't authorized yet (since it doesn't recognize the ADB it won't ask me for permission).
How can I fix this? I already tried to restart (pc and device), reinstall the drivers and kill/start the sever. Nothing worked.
But I'm also open for new ways.
I thought of some possibilities:
1. Change the "action_on_power_plug_connect": Is there a way to change the action my phone does execute when the power plug is connecting? Right now it's just starting to charge mode.
2. Boot on shedule/remote: Is there any app, which got the power to boot the phone, even if it is completely shut down?
I'm thankful for every single advice you can give me here.
Sincerly,
maj0r_tom
~~~~~~~~~
DEVICE INFO:
~~~~~~~~~
System: ColorOS 2.5.1i (Android Lollipop)
Root: Yes, SuperSU
Recovery: Stock Recovery
Hardware buttons working: None :]
---------------------
OLD POST:
---------------------
Hello everyone,
I've just repaired the broken display of my old Oppo Find 7.
Everything worked fine but one thing: The power button does not respond anymore.
It's a small piece of plastic, held in place by a bridge of metal.
When I press it onto the "sensor", it doesn't seem to recognize it.
Everything else is working perfectly - connecting a power source makes the phone start into loading mode.
Is there any way to start the phone without the physical button?
Maybe something beyond fastboot?
Or do you think that any phone-repair shop could help me there?
Sincerly,
maj0r_tom
Edit: The Volume Buttons do not work, too.
I've tried ADB. I could swear, that USB debugging is enabled (used Titanium Backup, it's asking for it on startup).
But ADB does tell me, that the phone is unauthorized.
Edit 2: Volume buttons repaired.
Edit 3: I got it.
The buttons didn't break - they just lost a small piece - a very ****ing small piece.
I did see it dropping from my Vol+ button and could insert it into the power button.
The phone startet, Debugging was enabled. Do I have to check anything else to activate ADB?
Click to expand...
Click to collapse
Hi, I think that an alarm application in ColorOS was able to start the phone if you had alarm setup.
But I'm sure this only applies to the ColorOS native alarm application, so no third party apps....
tw9 said:
Hi, I think that an alarm application in ColorOS was able to start the phone if you had alarm setup.
But I'm sure this only applies to the ColorOS native alarm application, so no third party apps....
Click to expand...
Click to collapse
I have had same problem. I am not expert at all but can suggest you to check out your phone mother board. Problem might be there. Nothing will work if your phone motherboard is out of function. Thanks
DELETE THIS THREAD PLEASE, PROB is SOLVED
I tried to install lineage os via twrp and i think my tablet its now hardbricked....It go on a blackscreen after the google startup logo and i can'T access bootloader even if it's unlocked, the menu of recovery, bootloader etc don'T pop up when i try button power and vol down....Is there any way to fix that?
myusernameisalreadytaken said:
I tried to install lineage os via twrp and i think my tablet its now hardbricked....It go on a blackscreen after the google startup logo and i can'T access bootloader even if it's unlocked, the menu of recovery, bootloader etc don'T pop up when i try button power and vol down....Is there any way to fix that?
Click to expand...
Click to collapse
Are you sure that in any statup mode you only see the Google logo and then the unit turns off?
Do the following test:
- charge your N7'13 for several hours
- connect it to a PC, and while still connected...
- boot in fastboot mode, "With the device powered off, hold Volume Down + Power until the bootloader appears, then release the buttons."
- observe your PC for new USB device indication (in Device Manager)
What's the new device ID number (if any)?
e.g.
USB\VID_18D1&PID_4EE0
USB\VID_05C6&PID_9008
LOS 15.1 (flex11 build) doesnt have a bootanimaltion. So after rebooting to system You should see a Google logo, then a black screen until setup wizard shows up
Sent from my whyred using XDA Labs
k23m said:
Are you sure that in any statup mode you only see the Google logo and then the unit turns off?
Do the following test:
- charge your N7'13 for several hours
- connect it to a PC, and while still connected...
- boot in fastboot mode, "With the device powered off, hold Volume Down + Power until the bootloader appears, then release the buttons."
- observe your PC for new USB device indication (in Device Manager)
What's the new device ID number (if any)?
e.g.
USB\VID_18D1&PID_4EE0
USB\VID_05C6&PID_9008
Click to expand...
Click to collapse
When i plug it i see LeMobile Android device android composite ADB Interface and when i click on it i see the device id
USB\VID_18D1&PID_4EE7
I can't boot in fastboot mode the screen come black with a backlight after the google logo and nothing happen...
When i flashed the rom i've see the android app update and nothing after
myusernameisalreadytaken said:
When i plug it i see LeMobile Android device android composite ADB Interface and when i click on it i see the device id
USB\VID_18D1&PID_4EE7
I can't boot in fastboot mode the screen come black with a backlight after the google logo and nothing happen...
When i flashed the rom i've see the android app update and nothing after
Click to expand...
Click to collapse
USB\VID_18D1&PID_4EE7 - wow I haven't seen this one before.
Please clarify and/or confirm:
- is it actually Nexus 7 2013 2nd gen?
- what exactly lineage os version/link did you flash?
- "With the device powered off, hold Volume Down + Power until the bootloader appears..." you get blank screen with backlight and USB\VID_18D1&PID_4EE7 on your PC
- "With the device powered off, hold Volume Down + Power..." does it respond OK to "fastboot devices" command on your PC?
NOTE - "With the device powered off, hold Volume Up + Power" gets you into recovery with ADB ID similar to USB\VID_18D1&PID_4EE7 - Have you mixed up " Volume Up" and " Volume Down"?
This case is perplexing and that's why I'm repeating and confirming everything. If it is indeed N7'13 AND there is no hardware issue AND you can't get into fastboot, then proceed to the unbricking guide - https://forum.xda-developers.com/showpost.php?p=75360854&postcount=199
To enter 9008 mode...
- turn it off and disconnect USB
- press both vol buttons and...
- plug in to a PC
k23m said:
USB\VID_18D1&PID_4EE7 - wow I haven't seen this one before.
Please clarify and/or confirm:
- is it actually Nexus 7 2013 2nd gen?
- what exactly lineage os version/link did you flash?
- "With the device powered off, hold Volume Down + Power until the bootloader appears..." you get blank screen with backlight and USB\VID_18D1&PID_4EE7 on your PC
- "With the device powered off, hold Volume Down + Power..." does it respond OK to "fastboot devices" command on your PC?
NOTE - "With the device powered off, hold Volume Up + Power" gets you into recovery with ADB ID similar to USB\VID_18D1&PID_4EE7 - Have you mixed up " Volume Up" and " Volume Down"?
This case is perplexing and that's why I'm repeating and confirming everything. If it is indeed N7'13 AND there is no hardware issue AND you can't get into fastboot, then proceed to the unbricking guide - https://forum.xda-developers.com/showpost.php?p=75360854&postcount=199
To enter 9008 mode...
- turn it off and disconnect USB
- press both vol buttons and...
- plug in to a PC
Click to expand...
Click to collapse
I dindt know for power+vol up.....with that i've fixed my problem! i'Ve reinstalled lineage 14.1 and it work.... The only issus it's i dind't see the normal fastboot or bootlarder menu with vol down...
It's get to annoying not able to get into recovery and download mode. And also wifi is regularly connecting and disconnecting.
I regret to update into one ui 3 it's really sucks.
I cannot say from personal experience how to enter download mode with a Galaxy S10+ but aside from the physical buttons combo, you should be able to use ADB or Fastboot commands to reboot into recovery while connected via USB to a laptop or PC.
I'm not sure how much experience you have with modding Android phones so please don't take offense if you already know the following. It's possible that something is different with Samsung's S10+ if they tweaked security settings. I may be the one who needs to do some research.
A few questions:
1. Have you enabled Developer Mode yet?
--> If not, just go into Settings -> About or Phone Info -> Look for 'Build Number' and tap repeatedly until you see a Toast message popup saying Developer Mode is now Unlocked!.
2. If you have Developer Mode, have you enabled ADB yet?
3. If none of these are available, then I must admit I would be flabbergasted as well. Hopefully Samsung hasn't gone far from the path of moddable firmware. If they have, I would probably just buy a different brand.
Right now my absolute favorite smartphone brand is OnePlus without a doubt! I have a OnePlus 5T and it rocks with 8 GB of RAM and OctaCore processor.
---> When I upgrade, I'm definitely sticking with OnePlus unless some other manufacturer is making ridiculously high-powered devices that make my laptop look weak & pathetic.
Samsung made some changes in the oneui 3 update.
RECOVERY MODE ONEUI 3.0
How to Reboot into Recovery Mode on Samsung’s Android 11 One UI 3.0 Firmware Update Hold the Power button of your device till the power menu pops up and select Power Off. Wait for your device to turn off completely. Plug-in a USB-C data cable connected to your PC or USB-C earphones in your...
r2.community.samsung.com
And what about download mode?
NarendraY11 said:
And what about download mode?
Click to expand...
Click to collapse
For download mode, hold the Bixby and Volume Down buttons together whilst inserting the USB-C cable into the phone.