Hi guys,
I have a terrible problem with my father's DOOGEE S55.
The phone won't start, but recovery mode does.
So I can access recovery, but as USB debug was never activated on the phone (and the phone is not rooted of course) I can do almost nothing with ADB.
I can just activate "apply update from ADB" and ADB sees the phone as "sideload", but of course once i try to install the ZIP file of the firmware, nothing happens as USB debug is not activated.
In all other cases ADB cannot do anything as the device is always "unautorized".
So the question is: what can I do?
Thank you all in advance for your help mates!
Hint: Add DOOGEE S55 to this thread's title thus mainly owners of such phone get addressed.
The 1st thing of all things a serious owner of a mobile device is to enable ADB to have the door to the device's Android open in case it's necessary. My guess is you're out of luck.
jwoegerbauer said:
Hint: Add DOOGEE S55 to this thread's title thus mainly owners of such phone get addressed.
The 1st thing of all things a serious owner of a mobile device is to enable ADB to have the door to the device's Android open in case it's necessary. My guess is you're out of luck.
Click to expand...
Click to collapse
I know but this is my father's phone he does not know how to enable usb debugging of corse..
Believe it or not, that to clone phone's user-data both ADB must got successfully enabled on phone and additonally phone's Android must got successfully rooted: there is no way around it.
Related
Android users need help with my phone! I am trying to manually turn on USB debugging (to access files on phone through update thru ADB mode in recovery options, I can install the driver for the phone but won't work until USB debugging is turned on) while my phone cannot boot into the OS. Is there a secret way to turn on USB debugging through recovery mode? (I do not want to wipe the data, and phone unfortunately is not rooted)
USB debugging has nothing to do with adb via recovery. It is an Android only setting. Recovery cannot use it and does not need it.
Adb doesn't work in stock recovery. I wrote a useful thread for people who are new to adb, as you are. You can get to it via the link in my signature. The thread is called "adb and fastboot. What isn't?".
It teaches you how to set it up and use it correctly.
Sent from my Nexus 5 using Tapatalk
rootSU said:
USB debugging has nothing to do with adb via recovery. It is an Android only setting. Recovery cannot use it and does not need it.
Adb doesn't work in stock recovery. I wrote a useful thread for people who are new to adb, as you are. You can get to it via the link in my signature. The thread is called "adb and fastboot. What isn't?".
It teaches you how to set it up and use it correctly.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
My main issue is that I am trying to retrieve my non backuped data on the phone and the phone itself will not boot into the Android OS.
I have looked into unlocking the fastboot/bootloader but it will wipe the data which would be pointless.
The data on the phone is more critical to me than the phone itself (and yes I was dumb enough to not back it up, didn't expect a flagship phone less than a year to crash on me, but I have learned for next time).
I am looking for any possible way to retrieve the data. I have tried to access the phone from the computer but I cannot access it since USB debugging is turned off and the phone is not rooted or doesn't have any other modifications.
Is there any way at this point I can retrieve the data off the phone with a non bootable OS and locked and stock Android OS?
Y is it non bootable?
Sent from my Android 5.0 Nexus 5
You are stuck. Stock recovery, locked bootloader, and OS will not boot. As RootSU mentioned, USB debugging has nothing to do with this. Stock recovery will not connect to adb.
Unless you can get the phone to boot looks like data is lost. Sorry.
Yoda8232 said:
Is there any way at this point I can retrieve the data off the phone with a non bootable OS and locked and stock Android OS?
Click to expand...
Click to collapse
No.
Yoda8232 said:
didn't expect a flagship phone less than a year to crash on me
Click to expand...
Click to collapse
Expect it from every electronic device. Especially expensive and complicated ones.
So I actually had warranty left from Google (bought directly from Google) and was going to RMA it but I decided not to because the data on there is important to me and worth more than the phone itself (yes I should of backuped everything but oh well what can I do now). And I bought a new phone so this Nexus 5 will be my little side project to try and revive it; somehow.
I will try to keep going at it, I have small programming/coding skills but it would be nice to find a way to open up the USB debugging option on the locked stock phone somehow that doesn't bootup.
Any suggestions on where I should start to start testing different "procedures"?
Well, it happened
I was sitting on a bench and somehow my phone found a way to slide between my fingers and crash. (I must note that it dropped on the bench, which was like 10 cm max fall).
Anyway, I came home, plugged it into my computer and miraculously the phone works even though the screen is all crashed/pixelated/non-responsive.
Is there a way to control my phone with my computer? Like viewing everything on the computer itself?
There are some programs that I need to backup my files there in order to use them on my other phone.
Thanks!
Hi
Thanks for writing to us at XDA Assist. Here is a thread which will be very helpful to you:
[Tool][Windows] Control a device with a broken screen
Good luck!
timmaaa said:
Hi
Thanks for writing to us at XDA Assist. Here is a thread which will be very helpful to you:
[Tool][Windows] Control a device with a broken screen
Good luck!
Click to expand...
Click to collapse
Already tried it.
I can't see if I got into the recovery mode and cmd does not recognize what "adb shell" is.
Even if I somehow reach it (and I'm not sure if I really did) then on windows it gives me an error qhsusb_bulk (driver not found).
Airbender123 said:
Already tried it.
I can't see if I got into the recovery mode and cmd does not recognize what "adb shell" is.
Even if I somehow reach it (and I'm not sure if I really did) then on windows it gives me an error qhsusb_bulk (driver not found).
Click to expand...
Click to collapse
If you're seeing qhsusb_bulk in Windows there's more wrong with the phone than just the screen unfortunately. I think we're going to have to move your thread into the Nexus section so the Nexus experts can lend a hand. Please standby while we have your thread moved.
Good luck!
Transmitted via Bacon
I finally managed to get into recovery mode. It seems like the "qhsusb_bulk" error is gone.
I tried using the adb shell but it doesn't recognize my phone even though device manager sees it perfectly fine.
Any help?
Maybe there is a chance that USB debugging is enabled so I just waste my time, how can I check?
Airbender123 said:
I finally managed to get into recovery mode. It seems like the "qhsusb_bulk" error is gone.
I tried using the adb shell but it doesn't recognize my phone even though device manager sees it perfectly fine.
Any help?
Maybe there is a chance that USB debugging is enabled so I just waste my time, how can I check?
Click to expand...
Click to collapse
Does the "adb devices" command return your serial number?
Transmitted via Bacon
timmaaa said:
Does the "adb devices" command return your serial number?
Transmitted via Bacon
Click to expand...
Click to collapse
Nope, that's the problem I'm facing currently.
It just gives me an error "device not found".
There could be many reasons for that. Unfortunately I'm not terribly experienced with this phone so we'll need to wait for one of the Nexus experts to come and lend a hand.
Airbender123 said:
Nope, that's the problem I'm facing currently.
It just gives me an error "device not found".
Click to expand...
Click to collapse
Please Google "15 second adb installer". Use that to install adb drivers. Then open a command prompt. Make sure you navigate to where adb gets installed (usually in program files) then adb device
Edit: To check Developer Settings go to Settings then About phone. Tap your build number 7 times. This will enable developer options in settings. Turn on developer mode there.
Sandman-007 said:
Edit: To check Developer Settings go to Settings then About phone. Tap your build number 7 times. This will enable developer options in settings. Turn on developer mode there.
Click to expand...
Click to collapse
Ummm that's kind of hard to do with a shattered display.
OP Just follow sandmans advice to get the drivers right and you'll be able to follow the tools instructions you're trying to use to enable USB debugging. If you just want your data off you could also just use:
Code:
adb pull /sdcard
Is your Bootloader unlocked?
If USB debugging is not enabled in Android and you can not enable it in android due to unreadable screen,
Your only option is to ADB shell from custom recovery such as TWRP.
You can only boot into custom recovery if your bootloader is already UNLOCKED.
theesotericone said:
Ummm that's kind of hard to do with a shattered display.
Click to expand...
Click to collapse
Not really. There are some tools out there that let you view and control your screen on a PC.
Sandman-007 said:
Not really. There are some tools out there that let you view and control your screen on a PC.
Click to expand...
Click to collapse
Yes there are. The OP is trying to use one of them. He has a broken screen and is unable to use the screen on the device. He does not have USB Debug enabled. To use the program to mirror screen you need USB Debug enabled. See the catch-22 there? His only hope is to enable it via recovery and ADB. But as @joegestes points out if he's not already unlocked he needs to unlock for that. Unlocking wipes the phone. Another catch-22.
This thread is still alive?
Hi All,
I'd like to know how to use ADB to pull files off a Sony Xperia Z2 convertly when it is plugged into a PC.
I am suspecting my son is misbehaving and he is behaving very coy.
Would is also be possible to install some spy software using ADB so that I can more accurately confirm my suspicions?
Thank you in advance.
saagark said:
Hi All,
I'd like to know how to use ADB to pull files off a Sony Xperia Z2 convertly when it is plugged into a PC.
I am suspecting my son is misbehaving and he is behaving very coy.
Would is also be possible to install some spy software using ADB so that I can more accurately confirm my suspicions?
Thank you in advance.
Click to expand...
Click to collapse
First of all, you should talk to your son about this. Spying and hacking a phone won't solve any parenting issues.
And now to answer your question: Probably not.
If the phone is locked and USB Debugging is disabled you cannot use ADB at all. You have to first enable USB debugging, but to be able to do that you need to know the phone's password.
You could, however, boot into recovery mode to unconditionally activate ADB, but in most cases when you try to do anything the phone will say that you're unauthorized and not allow you to do anything. To authorize ADB you, once again, need the phone's password.
If you do get ADB to work and get it to authorize here are the commands you need:
Pulling files:
Code:
adb pull /path/to/file
Installing an app:
Code:
adb install /path/to/app/appFileName.apk
There are more methods for what you need that use fastboot, hboot, bootloader unlocking, JTAG etc. but they are a lot harder to do than to talk a problem out with your son.
Hello,
I am hoping for some advice on how to revert my phone back to its original "factory settings" after a botched instal of GrapheneOS onto an unlocked Google Pixel 3A.
I got to the point at which I needed to Flash the Graphene Rom to the phone, but rather than installing, I received a message from Smart Screen MS edge asking if I really wanted to run as it's protecting my PC - I clicked run anyway and a blank command line window appeared for a second. Now my pc doesn't seem to be recognising the pixel 3A when I type ADB devices. My phone is currently in Fastboot mode "unlocked" and I'm hoping for some advice on what to do next. I'm total noob, so unsure how to start the process over (return the phone to it's previous state) before, maybe, trying again on a different PC.
I have since turned on my phone and Android 11 is still present and seems to work fine (however it gives me a warning on startup that the bootloader is unlocked.
Any help would be very much appreciated - thank you in advance.
Is all what happened that your phone now:
complains about "'maybe not safe bootloader unlocked".
This is just what android does when the bootloader is unlocked.
This you did before trying the flash.
If you want the warning gone simply lock it again.
However if you into the market for graphene OS then I would recomend: along with following their guide to a t to also read up here on xda about the general rooting unlocking thing a bit more so you get the overall process a bit better perhaps next time.
About windows. There are so many tools out there to help ya with disabling some of it's spying, turning off smartscreen, auto - uploads of all your data to M$oft, etc etc.
It's not hard to find.
Thanks for the response - I think I've worked out what is going on.
Typing ADB devices, my PC recognises the phone until I put it into fastboot mode - typing adb devices when in fastboot comes back with nothing and therefore when I try to flash, I assume the devices aren't talking to each other.
Not sure if there's a work around or whether it's a case of finding a new PC to try it on?
Thanks again.
Ignore
deroller said:
Thanks for the response - I think I've worked out what is going on.
Typing ADB devices, my PC recognises the phone until I put it into fastboot mode - typing adb devices when in fastboot comes back with nothing and therefore when I try to flash, I assume the devices aren't talking to each other.
Not sure if there's a work around or whether it's a case of finding a new PC to try it on?
Thanks again.
Click to expand...
Click to collapse
try another USB port first; use USB 2.0 if available! Reinstall google ADB drivers, make sure to use latest!
If above will not help:
on your computer: open device manager; on your phone: put your phone into fastboot; connect your phone to the computer WHILE keeping an eye on device manager; as soon as you'll connect your phone new device will appear in device manager ("unknown device" most likely but it might be some "android device" or "ADB device" too); right click it —> update driver —> automatic driver update worked in most cases for me, if not, go manual way and select google's "android fastboot device" (or something like that, can't remember actual name of the device); after driver install confirmation you should be good to go
Tamsta_T said:
try another USB port first; use USB 2.0 if available! Reinstall google ADB drivers, make sure to use latest!
If above will not help:
on your computer: open device manager; on your phone: put your phone into fastboot; connect your phone to the computer WHILE keeping an eye on device manager; as soon as you'll connect your phone new device will appear in device manager ("unknown device" most likely but it might be some "android device" or "ADB device" too); right click it —> update driver —> automatic driver update worked in most cases for me, if not, go manual way and select google's "android fastboot device" (or something like that, can't remember actual name of the device); after driver install confirmation you should be good to go
Click to expand...
Click to collapse
Hey there,
This is brilliant - thanks for all the advice. Having this support is helping me gain the confidence to learn more, research more, and then give it a go.
All the best.
deroller said:
Thanks for the response - I think I've worked out what is going on.
Typing ADB devices, my PC recognises the phone until I put it into fastboot mode - typing adb devices when in fastboot comes back with nothing and therefore when I try to flash, I assume the devices aren't talking to each other.
Not sure if there's a work around or whether it's a case of finding a new PC to try it on?
Thanks again.
Click to expand...
Click to collapse
thats if I am not wrongly remembering my experience:
because now your phone is in fastboot mode thus it won't show up with that command anymore.
Try: 'fastboot devices'
I imagine you put it into fastboot through: 'reboot fastboot' when you where in adb?
When in fastboot you can go on and flash the recovery and such.
Are you still in need of help here?
Hey, thanks for the clarification - been away and so haven't implemented all suggestions, yet.
I typed "adb reboot booloader" which I assumed put it into fastboot mode and then unlocked it using "fastboot flashing unlock".
I tried fastboot devices but the PC still doesn't see the phone. I'm going to try the update usb driver suggested by Tamsta_T and see how it goes.
Thanks for your help.
Hi, I was trying to revert back to realme UI stock from Pixel Experience ROM on my Realme 5i device(RMX 2030 EX). So, first I tried to install stock recovery through Orange fox. But after installing the recovery, my phone got bricked and now it's not even being detected by the pc nor I can access fastboot mode. As PC is not detecting my phone, I can't use Realme Flash tool or cmd to change my recovery. What can I do? Please if you know, give me a fix. I would be so grateful to you. Thanks for your time.
Here are some methods that might work for you.
How to Access an Android Phone with a Broken Screen
Dealing with a broken screen on your Android phone is a hassle. Although phone screens are pretty tough, one nasty drop can shatter them completely. Given that most people have a lot of irreplaceable content on their phones, it is
www.alphr.com
@Aranya Kishor Das
My POV: If on Android device side neither adbd ( requires USB Debugging got enabled ) nor fastbootd ( requires OEM unlock got enabled ) is accessible although the device's matching OEM USB driver got installed on Windows computer, then it's recommended to take phone to authorized service center and let them try to fix it.