Hi,
as my screen is defect, I want to sell my A310f in parts. Before that I obviously need to wipe it.
The following things I tried in the last days:
- wiping via ADB was not possible -> "unauthorized device" (I had no chance to put in USB-Debug-Mode [the phone should have been in this mode because I always put my phones in debug mode])
- wiping it straight from the phone -> I am on Marshmallow with stock recovery (had a custom recovery with custom kernel on Lollipop)
-> question1: when flashing Marshmallow, does it replace my custom recovery with the stock recovery?
-> question2: is the stock recovery in 6.0 identical to the one on Lollipop?
I assumed the recovery to be stock on my phone und to be identical to the one on Lollipop. So I booted my A310 in recovery and navigated blindly to wipe:
- 4*volume down
- 1* power
- 7*volume down
- 1* power
wait for some seconds
- 1* power
---> phone should have rebooted ... but it did not. It did not respond at all so I had to remove the battery.
After doing this I connected my phone via USB to my PC and tried to look if the internal SD has some more space (should be the case if the wipe was completed).
But now my PC doesn't show the internal SD in the explorer. Phone is charging as usual via USB.
Is this a good sign (wipe done) because the stock settings dont allow the PC to have access to the internal SD? Or did I screw up?
Thanks and regards,
blub
blub0815 said:
Hi,
as my screen is defect, I want to sell my A310f in parts. Before that I obviously need to wipe it.
The following things I tried in the last days:
- wiping via ADB was not possible -> "unauthorized device" (I had no chance to put in USB-Debug-Mode [the phone should have been in this mode because I always put my phones in debug mode])
- wiping it straight from the phone -> I am on Marshmallow with stock recovery (had a custom recovery with custom kernel on Lollipop)
-> question1: when flashing Marshmallow, does it replace my custom recovery with the stock recovery?
-> question2: is the stock recovery in 6.0 identical to the one on Lollipop?
I assumed the recovery to be stock on my phone und to be identical to the one on Lollipop. So I booted my A310 in recovery and navigated blindly to wipe:
- 4*volume down
- 1* power
- 7*volume down
- 1* power
wait for some seconds
- 1* power
---> phone should have rebooted ... but it did not. It did not respond at all so I had to remove the battery.
After doing this I connected my phone via USB to my PC and tried to look if the internal SD has some more space (should be the case if the wipe was completed).
But now my PC doesn't show the internal SD in the explorer. Phone is charging as usual via USB.
Is this a good sign (wipe done) because the stock settings dont allow the PC to have access to the internal SD? Or did I screw up?
Thanks and regards,
blub
Click to expand...
Click to collapse
"unauthorized device" means you'll have to click OK on the pop-up dialog in the phones display before you can use adb.
You have to do when you connect to adb first time, or after a factory reset to authorize cumputer access to it.
Probably not that easy with a broken display.
Q1: Yes, it will overwrite recovery with stock one.
Q2:Yes, they should function the same.
Do you have a lock on your screen?
Computer won't get any access to internal memory before is unlocked.
If you havn't removed your accounts in phone, then it's probably frp lock on as well.
I once was in the same position but for another device, but I managed to find a engineering boot/sboot which allowed adb at all times.
tys0n said:
"unauthorized device" means you'll have to click OK on the pop-up dialog in the phones display before you can use adb.
You have to do when you connect to adb first time, or after a factory reset to authorize cumputer access to it.
Probably not that easy with a broken display.
Q1: Yes, it will overwrite recovery with stock one.
Q2:Yes, they should function the same.
Do you have a lock on your screen?
Computer won't get any access to internal memory before is unlocked.
If you havn't removed your accounts in phone, then it's probably frp lock on as well.
I once was in the same position but for another device, but I managed to find a engineering boot/sboot which allowed adb at all times.
Click to expand...
Click to collapse
Additional info: before the described "wipe" procedure I was able to access the internal storage via PC (without having to click something on the screen, as it wasn't possible because of the broken screen).
Just after this "wipe" it is now not possible to access storage.
How long does it take to wipe the data? I probably just waited for some seconds
Yes I had a lock screen on my A3 (but as described I could access the storage no problem).
Sry, I dont understand what youn mean by that:
If you havn't removed your accounts in phone, then it's probably frp lock on as well.
Click to expand...
Click to collapse
Google is my friend...
The FRP lock would also suggest that the wipe was done correctly, right?
blub0815 said:
Additional info: before the described "wipe" procedure I was able to access the internal storage via PC (without having to click something on the screen, as it wasn't possible because of the broken screen).
Just after this "wipe" it is now not possible to access storage.
How long does it take to wipe the data? I probably just waited for some seconds
Yes I had a lock screen on my A3 (but as described I could access the storage no problem).
Sry, I dont understand what youn mean by that:
Google is my friend...
The FRP lock would also suggest that the wipe was done correctly, right?
Click to expand...
Click to collapse
Well..I don't know. Maybe you successfully wiped it if you can't see anything on your computer.
FRP lock means that if you factory reset your phone with pin/pattern lock set AND have a google account activated on phone,
you will have to log in with your google account after factory reset before you can use it again.
It is locked to your google account.
(if you sell it and someone changes the screen, it still needs to be logged in to your google account before frp can be removed so he can use the phone)
tys0n said:
Well..I don't know. Maybe you successfully wiped it if you can't see anything on your computer.
FRP lock means that if you factory reset your phone with pin/pattern lock set AND have a google account activated on phone,
you will have to log in with your google account after factory reset before you can use it again.
It is locked to your google account.
(if you sell it and someone changes the screen, it still needs to be logged in to your google account before frp can be removed so he can use the phone)
Click to expand...
Click to collapse
So it seems there is no way around and I need to check the mainboard with a display unit ...
Samsung gets on my nerves ....
Thanks for the Help!
Related
SOLVED
See my most recent post in this thread
______________________________________________________________________________________
Firstly, I've spent the last three days scouring XDA and some other forums searching for solutions and trying various options.
The screen on my N4 has cracked and I've lost the use of the bottom half of the touchscreen. This means that I can't unlock my phone.
The phone is insured and will be repaired, but there are photos of my son's first birthday on the internal memory that I don't want to lose. I'm concerned that the phone will be factory reset during a repair or I'll receive a replacement. I'm trying to access the internal memory remotely to backup these files before I send the phone off. The problem is that I hadn't enabled USB debugging before the accident. The phone is completely stock including the bootloader.
So I can access via fastboot but not via adb.
Q1: Can I pull file from the internal memory via fastboot
Q2: Can I enable usb debugging via fastboot
Q3: The phone is set to display as an MTP device in windows but as I can't unlock the screen, none of the files are showing. Is there anyway around this?
Q4: Purely via fastboot, can I unlock the bootloader, install CWM so to use ADB within it and then return to a stock bootloader?
I think they're my options. Any answers to the above or alternatives would be appreciated.
All of the other threads regarding this, the users seem to either already have CWM installed or they're looking to perform a factory reset. I did consider resetting the device via the bootloader in order to bypass the screenlock but I understand that on the N4 this wipes the internal memory as well.
Unlocking the device isn't needed to pull the files from it, just plug it in and get what you need from the internal memory
EddyOS said:
Unlocking the device isn't needed to pull the files from it, just plug it in and get what you need from the internal memory
Click to expand...
Click to collapse
On mine if I plug it in it appears as an MTP device but with no files. I then have to unlock the screen and select USB something-or-other from the notificationss bar, then the files appear in windows.
Strange, mine never needs to be unlocked...I'm using Windows 8 Pro btw but it also works fine in work on Vista Business
Only other thing I can think of is the fact I'm unlocked and running a custom ROM, I've never used my N4 stock. It was on CM within 30 mins of receiving the unit!
So over the last week I've managed to solve my problem. I've seen several other people asking for help with no luck so I'm posting this here in the hope that the search function will bring it up.
Firstly, my phone was completely stock running 4.2.2, unrooted, with the locked stock bootloader. USB Debugging WAS NOT enabled. I had pattern lock enabled when I dropped the phone. The screen cracked and the bottom half of the touchscreen was unresponsive.
The phone was insured, but I wanted to backup photos from the device before sending it off for repair/replacement.
HOW I FIXED IT.
Please note, you need at least some part of the screen to be working, specifically, some part of the screen where the pattern lock is.
You only need two pieces of software. The Android SDK and the Nexus 4 Toolkit http://forum.xda-developers.com/showthread.php?t=1995688
If you are running 4.2.2 you will need to update the toolkit. I also had the standard issues of installing the USB drivers for the N4. You need to get to a point where is shows up as an ADB device in Windows Device Manager.
As I didn't have USB debuggin enabled I couldn't connect tothe phone via ADB, but if you put it into recovery mode you can use Fastboot. Hold down the power key to turn the device off and turn it on while holding down Vol Down to load up recovery mode.
If you then start the N4 Toolkit, you should see the device listed as a fast boot device.
From within the toolkit unlock your bootloader.
Flash a temporary bootlader, (option 10) as the touchscreeen was broken it has to be CWM.
Once in CWM you can start to use ADB. Open up a DOS command prompt in Windows, go to your SDK/platform tools folder/ to access ADB.exe and you can use the pull command to copy folders to your PC. At this point, instead you can use applications like ADBexplorer or DroidExplorer to do the same thing through a nicer GUI.
If you'd like to still be able to use your phone, although without the touchscreen, you can load an unstable image to get into android and then use ADB to start changing system settings.
Firstly, before exiting CWM, clear the cache. Without doing this the phone jsut hung on the Nexus symbol while loading the image.
in the toolkit go to root/unroot options and select load unstable image(option 4 and then 6). This will fire you up into Android and it should be set up as you left it.
I wanted to enable bluetooth so to use a keyboard (I didn't have a mouse but this is a better option) from the DOS window type the following command
am start -a android.bluetooth.adapter.action.REQUEST_ENABLE
You should eventually get a pop-up on your screen saying that a request has been made to enable bluetooth. Hopefully your screen is working enough to select enable.
Then I use the workaround to disable the sceenlock, found here -> (http://www.addictivetips.com/androi...e-pattern-unlock-on-android-via-adb-commands/) I found method 2 worked for me. I imagine this will be stopped in a future update.
Method 1
adb shell
cd /data/data/com.android.providers.settings/databases
sqlite3 settings.db
update system set value=0 where name='lock_pattern_autolock';
update system set value=0 where name='lockscreen.lockedoutpermanently';
.quit
Method 2
adb shell rm /data/system/gesture.key
If either of these methods are successful you will be able to unlock the phone with an pattern, hence why you need to be able to touch some part of it.
From then, my bluetooth keyboard was already mated to my phone to I was able the navigate the menus to turn on USB Debugging, turn-off the screen lock and a few other bits and pieces I needed to do.
I then restarted (I was still working within the unstable image) and on reboot, all my changes had al been applied. No screen lock, bluetooth enabled and USB Debugging enabled.
Hopefully this will be of help to those in a similar position. Thanks has to go to the toolkit though which provides all the necessary access to carry this out.
I should probably add, you can use the toolkit to relock the bootlader if you're concerned about that and if you can't click the screen to enable bluetooth or mate a keyboard or mouse, once you have USB Debugging enabled you can use software like Screencast to control you phone's screen from a PC.
So typically, just as I fill my claim to repair my nexus my wife drops her, smashing the screen even more than I did so she has absolutely no use of her screen. I went through the process again and though I'd post it in a more simple fashion.
1. Reset Nexus into recovery mode (power & volume down)
2. Connect to PC via USB. Install the USB driver from the SDK so that it appears as an ADB device
3. Fire up the updated toolkit. You should see the nexus as a fast boot device
4. Unlock bootloader
5. Using option 10 on the toolkit load up CWM on the phone. This gives you ADB access so can you pull files off the device via ADB although I could access the SD card through programs like Droid explorer.
6. If you want to carry on further and get into Android properly, you'll need to wipe the cache from within CWM
7. Reboot and hold down the volume key to get back into recovery
8. In the toolkit select root options (option 4) and load temporary image (6) If it hangs on the google or nexus logo you've not wiped the cache.
9. With this second phone I couldn't access it through droid explorer as it was popping up as an MTP device but I could pull the files via command prompt or through the toolkit
10. If you have any use of the touchscreen at all you can run the following command which will then mean that any touch will unlock the device
adb shell rm /data/system/gesture.key11. You can activate bluetooth via adb if you have a mouse or keyboard available but you will need to be able to press okay on the screen
12. Any changes you make in the unstable android image such as lockscreen, bluetooth, enabling debugging, etc will remain in place when you restart the device.
13. You can relock the bootloader if you wish via the toolkit. You just need to be in recovery mode first.
Hope this simplifies the process
Does unlocking bootloader via toolkit not wipe everything? How are you unlocking bootloader and still able to pull data off?
EDIT: it appears fastboot oem unlock on the Nexus 4 *does not* wipe data!
Carpetboy said:
So typically, just as I fill my claim to repair my nexus my wife drops her, smashing the screen even more than I did so she has absolutely no use of her screen. I went through the process again and though I'd post it in a more simple fashion.
1. Reset Nexus into recovery mode (power & volume down)
2. Connect to PC via USB. Install the USB driver from the SDK so that it appears as an ADB device
3. Fire up the updated toolkit. You should see the nexus as a fast boot device
4. Unlock bootloader
5. Using option 10 on the toolkit load up CWM on the phone. This gives you ADB access so can you pull files off the device via ADB although I could access the SD card through programs like Droid explorer.
6. If you want to carry on further and get into Android properly, you'll need to wipe the cache from within CWM
7. Reboot and hold down the volume key to get back into recovery
8. In the toolkit select root options (option 4) and load temporary image (6) If it hangs on the google or nexus logo you've not wiped the cache.
9. With this second phone I couldn't access it through droid explorer as it was popping up as an MTP device but I could pull the files via command prompt or through the toolkit
10. If you have any use of the touchscreen at all you can run the following command which will then mean that any touch will unlock the device
adb shell rm /data/system/gesture.key11. You can activate bluetooth via adb if you have a mouse or keyboard available but you will need to be able to press okay on the screen
12. Any changes you make in the unstable android image such as lockscreen, bluetooth, enabling debugging, etc will remain in place when you restart the device.
13. You can relock the bootloader if you wish via the toolkit. You just need to be in recovery mode first.
Hope this simplifies the process
Click to expand...
Click to collapse
Please HELP, i can get to step 5...but then, when I try to use ADB via cmd (ie. adb shell), it says "error: device offline". what can it be? I don't know if this is a driver related issue (i've tried the toolkit drivers and the SDK drivers)...i'm desperated, I can't access the phone!!
Thanks in advance
not working for me
i'm in same boat with cracked screen. i can get CWM installed but i cant enabled usb debugging without touching the screen so i cant get adb working. how did you turn on usb debugging without the screen
Thanks for the guide.
Im curious on why youd want to boot an unstable(temporary) image after pulling the files using ADB in CWM recovery. Why not just wipe cache and reboot normally into Android ?
usb debugging without screen?
compsmart said:
i'm in same boat with cracked screen. i can get CWM installed but i cant enabled usb debugging without touching the screen so i cant get adb working. how did you turn on usb debugging without the screen
Click to expand...
Click to collapse
Can someone please walk me through how to do this? My screen is completely broken, but I can still turn on/off, I have reason to believe debugging is off because when I connect the phone (a Samsung galaxy sII skyrocket) to my Toshiba laptop via a micro USB, it makes a sound to signal that it's connected. Drives E and F then open up (but are empty) and then disappear. I have no idea what's going on but I absolutely cannot lose all of the data on this phone. Pictures and videos from my old blackberry Torch are on here too, making up about 4 years of my daughter's life that I would lose if I cannot retrieve. Also, I am not super -tech savvy, so if someone could help me I would be forever grateful.
Please!!
:crying:
almost the same issue
I have an Asus memo pad 10 (smart) some of the core apps have been corrupted, (keyboard, UI, launcher etc all the essential stuff) I've been trying to reinstall my UI and launcher from my computer when i found out that USB debugging was disabled. the tablet is basically unusable, i have no way of enabling from the tablet itself. is there a piece of script or something i could run from my PC to enable it?
any help would be greatly appreciated :crying:
bob mc bob said:
I have an Asus memo pad 10 (smart) some of the core apps have been corrupted, (keyboard, UI, launcher etc all the essential stuff) I've been trying to reinstall my UI and launcher from my computer when i found out that USB debugging was disabled. the tablet is basically unusable, i have no way of enabling from the tablet itself. is there a piece of script or something i could run from my PC to enable it?
any help would be greatly appreciated :crying:
Click to expand...
Click to collapse
My screen became unresponsive a while back. I ended up getting and OTG cable and plugging in a mouse. This allowed me to do everything as if the touchscreen was working. There's also an app called MyMobiler that let me plug in my device over USB and control my screen from my PC. Those two helped me enable USB Debugging, flash a custom ROM, root the phone, backup everything I needed, then restore the phone to stock. I hope this helps.
*Sorry for bumping such an old post*
Thanks for the really useful guide!
Could you or someone just confirm to me that unlocking the bootloader does not factory reset? The reason I'm doing this process is to access my personal data so it's important that I can keep it all.
I ask because at the unlock bootloader stage it implicitly warns me that there'll be a factory reset.
Thanks again!
HikerMan said:
*Sorry for bumping such an old post*
Thanks for the really useful guide!
Could you or someone just confirm to me that unlocking the bootloader does not factory reset? The reason I'm doing this process is to access my personal data so it's important that I can keep it all.
I ask because at the unlock bootloader stage it implicitly warns me that there'll be a factory reset.
Thanks again!
Click to expand...
Click to collapse
Unlocking to bootloader will wipe your device
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Unlocking to bootloader will wipe your device
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
In that case, I am confused as to how OP managed to unlock his bootloader. He actually states that the purpose of this was to retrieve data, like me.
Also, in a previous comment in this thread by jw95275, they claim that "it appears fastboot oem unlock on the Nexus 4 *does not* wipe data".
I am concerned about the conflicting answers so far, so will hold off for an explanation before I do anything. Thanks for the response!
HikerMan said:
In that case, I am confused as to how OP managed to unlock his bootloader. He actually states that the purpose of this was to retrieve data, like me.
Also, in a previous comment in this thread by jw95275, they claim that "it appears fastboot oem unlock on the Nexus 4 *does not* wipe data".
I am concerned about the conflicting answers so far, so will hold off for an explanation before I do anything. Thanks for the response!
Click to expand...
Click to collapse
You should just be able to "fastboot boot recovery.img" and boot CWM and then use ADB. W/O unlocking the BL
npjohnson said:
You should just be able to "fastboot boot recovery.img" and boot CWM and then use ADB. W/O unlocking the BL
Click to expand...
Click to collapse
This did not work for me. I have a Nexus 4 with a broken digitizer, locked bootloader, and usb debugging disabled. I need to grab some data off.
I've tried `fastboot flash recovery {{recovery .img}}` and `fastboot boot {{recovery .img}}` without unlocking the bootloader first, and via both methods, I get back "FAILED (remote: not supported in locked device)"
So I'm not sure how people are able to get into custom recovery without first unlocking BL/losing all their data. Can someone explain?
jinglejuice said:
This did not work for me. I have a Nexus 4 with a broken digitizer, locked bootloader, and usb debugging disabled. I need to grab some data off.
I've tried `fastboot flash recovery {{recovery .img}}` and `fastboot boot {{recovery .img}}` without unlocking the bootloader first, and via both methods, I get back "FAILED (remote: not supported in locked device)"
So I'm not sure how people are able to get into custom recovery without first unlocking BL/losing all their data. Can someone explain?
Click to expand...
Click to collapse
On some (few) Motorola devices (not nexus 4), you can fastboot boot without unlocking the BL.
Hi guys,
I recently dropped my Nexus 4 on the floor today and the screen cracked. As a result, the screen is completely unresponsive now but I am able to see its display when I press the power button. Could you guys help me/point me in the right direction regarding how to get the data I have on the phone (music, photos etc.) please.
My Nexus is unrooted/stock version. I tried connected it to my laptop via USB, but all it does it charge. I think I might have the USB debugging option enabled (as I remember enabling it before sometime ago). I'm running the latest firmware (5.0.1 I believe). Also the bootloader is locked.
Any help would be much appreciated.
Thanks
EDIT: I should note that I have a Password (PIN) for the lock screen.
I installed android sdk and tried to enter commands, but it didn't work. When I typed in 'adb devices', no serial came up (I checked sdk manager for the google usb driver, and it says it's installed). Also, when I tried typing in anything i.e. 'adb shell' it said error no devices found. I was attempting to follow a guide to set up adb for any other steps required to get my data from the internal storage. Bear in mind, I don't have much knowledge on these tools, all I'm doing is following any guides. Please can you help me how to get my photos or the contents of the sdcard.
The pin is not letting you boot into the os and that's why adb isn't working. Can you get into the bootloader? If so boot into twrp then try adb
fastboot boot twrp.img. Where twrp.img is the full file name.
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
The pin is not letting you boot into the os and that's why adb isn't working. Can you get into the bootloader? If so boot into twrp then try adb
fastboot boot twrp.img. Where twrp.img is the full file name.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for responding. I can enter the bootloader (if that's the Volume Down + power button menu). Quick google search shows that twrp is for customer recovery. Bear in mind that I haven't unlocked the bootloader or installed anything like recoveries before (it is basically a stock N4). Would I need to install it? If so, please could you direct me to a tutorial or guide me step-by-step on what to do as I don't have too many ideas on what to do to get the data from the phone.
Just to clarify: My N4 is completely stock, Bootloader is locked (says 'LOCK STATE - locked' in bootloader menu) and it is unrooted. I remember having the USB debugging option enabled the last time I was in the dev menu on the phone.
oracle93 said:
Thanks for responding. I can enter the bootloader (if that's the Volume Down + power button menu). Quick google search shows that twrp is for customer recovery. Bear in mind that I haven't unlocked the bootloader or installed anything like recoveries before (it is basically a stock N4). Would I need to install it? If so, please could you direct me to a tutorial or guide me step-by-step on what to do as I don't have too many ideas on what to do to get the data from the phone.
Just to clarify: My N4 is completely stock, Bootloader is locked (says 'LOCK STATE - locked' in bootloader menu) and it is unrooted. I remember having the USB debugging option enabled the last time I was in the dev menu on the phone.
Click to expand...
Click to collapse
We'll you've got a problem. You'll have to unlock the bootloader to run fastboot commands and that'll completely wipe your device. And with the pin and an unresponsive screen you can't get into the os. There really isn't anything you're going to be able to do to save your files. Sorry about that.
Edit, just one more thought, are you still on 4.4.4? If so there may be a hope. Shoot, you'll need to boot into the os though. So my idea isn't going to work.
jd1639 said:
We'll you've got a problem. You'll have to unlock the bootloader to run fastboot commands and that'll completely wipe your device. And with the pin and an unresponsive screen you can't get into the os. There really isn't anything you're going to be able to do to save your files. Sorry about that.
Edit, just one more thought, are you still on 4.4.4? If so there may be a hope. Shoot, you'll need to boot into the os though. So my idea isn't going to work.
Click to expand...
Click to collapse
Ah that was what I feared ... I'm running the latest firmware (5.0.1). I wouldn't really care about the phone if it weren't for a few images (should have had it backed up!).
Now I need to decide whether or not to change the screen etc. for £35 or just look in the market for a new phone. If I did buy a new screen/digitiser/frame thing, would these be suitable (where I won't need to use heat guns or glue and stuff)?
ebay (dot) co.uk/itm/LCD-Screen-Display-Touch-Digitizer-for-LG-E960-Google-Nexus-4-Frame-Replacement-/331224787829?pt=UK_Replacement_Parts_Tools&hash=item4d1e892b75
OR
ebay (dot) co.uk/itm/For-LG-E960-Google-Nexus-4-LCD-Display-Digitizer-Touch-Screen-Frame-in-Black-/331227949021?pt=UK_Replacement_Parts_Tools&hash=item4d1eb967dd
Also, if I did change it using the above, would dissembling the phone and reassembling it cause my data to be lost?
Thank you for your help
Edit: I managed to save about 80 photos which were probably in the default images folder in the SD card using AndroidLost. I'm guessing the other images which were in other folders i.e. WhatsApp Images etc. aren't recoverable using the site
Hi, I have a S4 i9505 with a problem, screen broken and no display at all + usb debugging is disabled.
Phone: Not rooted, original software, usb debugging disabled, no display at all
What I want to achieve: restore all my photos / videos on the phone memory, no sd card
What I have attempted:
installed ADB & fastboot based on instructions from http://forum.xda-developers.com/showthread.php?t=2786395
What I need help with:
- When i try to get into recovery mode, i wasn't sure if i am indeed in there since i can't see anything, but in total there's a vibration when i turn on the phone, and another vibration when i release the power up+power+home after pressing them down for about 5 seconds.
- When in command prompt I type adb devices and there was none, and when i type adb shell it says error: device not found
I have ensured all drivers for my phone are installed (even with PdaNetA4180 & UniversalAdbDriverSetup6 from cynanogen) but the error remains. refer to attached image.
I have done extensive search on the forum but still couldn't find any ways to get usb debugging enabled on my crippled phone.
Any step by step guide would really be helpful! Thanks
Ps. Main problem = device not found in adb , usb debugging disabled, screen no display/cracked
What do you want? To recover files? To my knowledge that is not possible.
You would first need to flash a custom recovery for adb to work in recovery.
Then you would need to allow the connection on your device (which you can't do).
Yes I need to recover photos only. Nothing else.
Please kindly guide the steps on how to flash a custom recovery (w/o control of the phone's display or touch)
Thanks.
Your device is shown connected in windows
Why not use the mtp protocol and copy whatever you want
Hi, in the beginning, my phone is locked with a pattern pin.
I read the tutorials and managed to get away with the pattern pin by resetting my phone to factory settings via recovery mode i guess by watching youtube guide.
I didn't knew the photos and all will get deleted off from it, so there's nothing to transfer over when i got MTP working and able to access files inside the phone.
What do you recommend? Would fixing the screen and then using dr fone recovery works? or is there any other way to solve this without getting the phone display fixed? Thanks.
If the photos are deleted by the factory reset then i am sorry to day but you cannot recover them even if you get the screen fixed
bomby481 said:
Hi, in the beginning, my phone is locked with a pattern pin.
I read the tutorials and managed to get away with the pattern pin by resetting my phone to factory settings via recovery mode i guess by watching youtube guide.
I didn't knew the photos and all will get deleted off from it, so there's nothing to transfer over when i got MTP working and able to access files inside the phone.
What do you recommend? Would fixing the screen and then using dr fone recovery works? or is there any other way to solve this without getting the phone display fixed? Thanks.
Click to expand...
Click to collapse
Your photos are gone and there is no way to get them back.
Hi everyone!
I broke my S8 screen completely by dropping it (the phone is still working, not know if the touch still works).
I want to recover WhatsApp backup folder and DCIM folder (i had no backup service enabled, nor samsung account, nor google photo or gdrive), so i thought to go ahed through ADB. Anyway adb list no devices until i unlock my phone through pattern code ( i had no facial/retina/fingerprint mode set).
So i thought to proceed through download mode, flash twrp through odin and access adb through twrp. Anyway it looks like i cannot use odin to flash until i trigger on "OEM Unlock" in developer options which i can't do no more cause of the broken screen.
Is there another way to enable OEM Unlock which doesn't require touch input? Or is there any other way to recover my two folders?
A big thanks for everyone who could help
You can use an otg adapter and a mouse and try to replicate your pattern code and after your in just transfer your files. If you happen to have a second cell phone I would suggest you practise a bit on that screen first so you can replicate the exact movements to unlock your phone. Had an issue with my s6 edge and that worked like a charm.
deveauwelle32 said:
If you don't know how to recover data from S8 phone, just use an Android data recovery software, it can help you recover data from an broken Android device, it is really simple to finsih the recovery process. And you can preview and recover the data from your broken phone, so that you don't lose these data.
Click to expand...
Click to collapse
Yep, that's the best thing you can do.
Cristian.CT46 said:
Hi everyone!
I broke my S8 screen completely by dropping it (the phone is still working, not know if the touch still works).
I want to recover WhatsApp backup folder and DCIM folder (i had no backup service enabled, nor samsung account, nor google photo or gdrive), so i thought to go ahed through ADB. Anyway adb list no devices until i unlock my phone through pattern code ( i had no facial/retina/fingerprint mode set).
So i thought to proceed through download mode, flash twrp through odin and access adb through twrp. Anyway it looks like i cannot use odin to flash until i trigger on "OEM Unlock" in developer options which i can't do no more cause of the broken screen.
Is there another way to enable OEM Unlock which doesn't require touch input? Or is there any other way to recover my two folders?
A big thanks for everyone who could help
Click to expand...
Click to collapse
Log into Samsung Find my mobile. Use your Samsung Account details to log in.
There you will see alot of options that you can perform on your Galaxy S8 remotely.
Use the remotely unlock my device option to unlock your device.
Then connect your phone to the Laptop or PC using data cable and recover the data.
Hope it helps.
Hello!
My nexus 6P is stuck in a bootloop and I need to get my photos from the internal storage. I am unable to enter recovery mode; when I try to enter recovery mode, the device just goes back to the Google logo. Is there a way to recover my files even if USB debugging is not enabled and my device is not rooted?
Thank you!
Is your bootloader unlocked? If it is then you should be able to flash one of the kernels from here: https://forum.xda-developers.com/nexus-6p/general/guide-fix-nexus-6p-bootloop-death-blod-t3640279 and it'll allow your phone to boot up completely so you can transfer data from your phone to your computer.
HesThatGuy said:
Is your bootloader unlocked? If it is then you should be able to flash one of the kernels from here: https://forum.xda-developers.com/nexus-6p/general/guide-fix-nexus-6p-bootloop-death-blod-t3640279 and it'll allow your phone to boot up completely so you can transfer data from your phone to your computer.
Click to expand...
Click to collapse
How could I know if my bootloader is unlocked? But I think it's locked since I don't remember unlocking it.
While your 6P is turned off hold volume down and press the power key to turn it on. This will put the phone into fastboot mode and from there you can look at the text towards the bottom of the screen. If it says: Device is UNLOCKED then the bootloader is unlocked and you can flash one of those kernels. If it says: Device is LOCKED then your bootloader is locked and you will not be able to pull the info off of your phone.
HesThatGuy said:
While your 6P is turned off hold volume down and press the power key to turn it on. This will put the phone into fastboot mode and from there you can look at the text towards the bottom of the screen. If it says: Device is UNLOCKED then the bootloader is unlocked and you can flash one of those kernels. If it says: Device is LOCKED then your bootloader is locked and you will not be able to pull the info off of your phone.
Click to expand...
Click to collapse
It says that device is locked. So this means that there is no way to retrieve the files on my phone? Or is it possible to physically open the device then get the internal storage and access it somehow?
The only other way you might be able to get the data off your phone is to get the SoC re-soldered on so that it'll stop bootlooping, but I'm not entirely sure this will work. Other than that I don't think there's any other way to get your data.
v_17 said:
It says that device is locked. So this means that there is no way to retrieve the files on my phone? Or is it possible to physically open the device then get the internal storage and access it somehow?
Click to expand...
Click to collapse
Because you are bootloader locked, the workaround of flashing a custom kernel is not available to you. In order to flash a kernel you need to be unlocked, but the process of unlocking your bootloader WILL WIPE your phone and all your data will go with it. There are threads talking about using a hairdryer to heat up the phone before powering it on to put it in limp mode. If you can get your phone to boot up, you can enable USB Debugging under Developer Settings and then try to get your files off, but chances are extremely unlikely because you have to keep the phone hot to prevent it from bootlooping again. Opening the phone to access the memory chips is a non-starter. Lastly, are you absolutely positive that your photos are not automatically uploaded to Photos? Have you accessed (logged into) Google photos and verified they are not there?
Help! I'm in the same situation!
v_17 said:
Hello!
My nexus 6P is stuck in a bootloop and I need to get my photos from the internal storage. I am unable to enter recovery mode; when I try to enter recovery mode, the device just goes back to the Google logo. Is there a way to recover my files even if USB debugging is not enabled and my device is not rooted?
Thank you!
Click to expand...
Click to collapse
Hi there. Did you get a solution for this as I am in exactly the same situation :| Thanks!
danielleb21 said:
Hi there. Did you get a solution for this as I am in exactly the same situation :| Thanks!
Click to expand...
Click to collapse
If your bootloader is locked and you don't have usb debugging enabled there is not much you can do. Have you logged into Google photos on your PC to verify your photos are not there? If your data/photos are not the issue and you just need your phone working again, there is another thread on how to do that (with a little luck).
Hi Guys,
I have gone through your messages. In my case bootloader is locked but USB debugging is ON. Also I checked google photos. Some photos are there but camera and whatsapp photos are not there. May I know any work around to get the data ?
vishalgole said:
Hi Guys, I have gone through your messages. In my case bootloader is locked but USB debugging is ON. Also I checked google photos. Some photos are there but camera and whatsapp photos are not there. May I know any work around to get the data ?
Click to expand...
Click to collapse
Drop down to the stock recovery mode and use adb to pull files to your PC. If you have TWRP recovery installed you can just use MTP to drag and drop files. Photos are located in /sdcard/DCIM/Camera. WhatsApp photos are in /sdcard/WhatsApp/Media.
I have exact same problem as OP and my phone is Locked and I don't remember enabling debugging mode. From reading replies I understand I can't get my data in internal storage. Now what should I do to make my phone boot-up. I don't need my data back. Also I'm confused about flashing Factory image vs flashing OTA. What does the two mean and what should I do?
v12xke said:
If your bootloader is locked and you don't have usb debugging enabled there is not much you can do. Have you logged into Google photos on your PC to verify your photos are not there? If your data/photos are not the issue and you just need your phone working again, there is another thread on how to do that (with a little luck).
Click to expand...
Click to collapse
Have you found a way to recover phone the phone from bootlooping. As i'm facing the similar problem, when I try to boot into recovery, it starts bootlooping, and I can't use that hairdryer method as there is no OS installed in my phone, and top of that, my bootloader locked too...
Shabbirkt said:
Have you found a way to recover phone the phone from bootlooping. As i'm facing the similar problem, when I try to boot into recovery, it starts bootlooping, and I can't use that hairdryer method as there is no OS installed in my phone, and top of that, my bootloader locked too...
Click to expand...
Click to collapse
Sorry, but if you have no OS, and bootloader locked, and bootlooping you are dead in the water. My phone was unlocked so I was able to use the 4-core method. If your new phone is a Google product, unlock the bootloader from day one.