Related
ATTENTION: PUBLIC SERVICE ANNOUNCEMENT
It has come to my attention that under certain circumstances when the Kindle HD's get stuck in a bootloader bootloop the information on the "boot0" block of the internal storage can be ERASED and RESET.
This partition is special and contains ALL of your device's hardware specific information:
- Wifi MAC address + Encoded Secret for registering w/ Amazon services
- BT MAC address
- Serial #
etc
FOR BACKING UP THIS PARTITION:
Code:
adb shell su -c "dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot0block.img"
adb pull /sdcard/boot0block.img
Place the "boot0block.img" file with the other files that you backed up in the original instructions for safe keeping.
FOR RESTORING THIS PARTITION:
(do not do this unless you are absolutely SURE that your boot0 block got wiped out -- hopefully you never need to)
This is done via adb from your PC while the device is in TWRP recovery or in the Android OS (not fastboot):
Code:
cd <your safekeeping files>
adb push boot0block /sdcard/boot0block.img
adb shell "echo 0 > /sys/block/mmcblk0boot0/force_ro; dd if=/sdcard/boot0block.img of=/dev/block/mmcblk0boot0;"
THIS FILE IS UNIQUE TO YOUR DEVICE AND CANNOT BE REPLACED OR REBUILT FROM ANOTHER DEVICE. DO NOT SHARE IT WITH ANYONE AS IT CONTAINS INFORMATION ABOUT YOUR DEVICE USED BY AMAZON DURING REGISTRATION.
very interesting Hashcode,thanks for the information :good:
Odd, I can't seem to find the file after I pulled it with ADB.
EDIT: I didn't even assign the command an output location to begin with. LOL.
Thanks for the info.
How can I access KFHD via ADB if CM10.1 installed.
I can't see my device in device manager only as a media storage or sth like that.
Should I remove KFHD adb driver and install the google driver?
Or just using the hidden trick in cm10.1?
"Enable Developer options in your phone (Settings > About phone and tap Build Number until you are a developer (about 7 times)
Set root access for APPS and ADB in: Settings > Developer Options > Root Access
Enable Android debugging at the same page (Developer Options). Enable ADB over network if you need.
Check if your Settings > Security > Unknown Sources is checked. you will need it to install over ADB."
Yeah...it helped
esox_hu said:
Thanks for the info.
How can I access KFHD via ADB if CM10.1 installed.
I can't see my device in device manager only as a media storage or sth like that.
Should I remove KFHD adb driver and install the google driver?
Or just using the hidden trick in cm10.1?
"Enable Developer options in your phone (Settings > About phone and tap Build Number until you are a developer (about 7 times)
Set root access for APPS and ADB in: Settings > Developer Options > Root Access
Enable Android debugging at the same page (Developer Options). Enable ADB over network if you need.
Check if your Settings > Security > Unknown Sources is checked. you will need it to install over ADB."
Yeah...it helped
Click to expand...
Click to collapse
Just turn on ADB debugging on the tablet, and plug it into the computer. On the computer, open command prompt, use the command "adb devices" to see if your ADB is working.
Other than that, I don't know what happened in your post.
Ok i really can't figure this one out, I used adb many times while testing KFFAide tool so I am 100% sure my adb drivers are installed correctly, But since i switched to cm10.1 (Thanks hashcode) ADB cannot recognize my device anymore, I have enabled ADB on my KFHD and when i connect it to my pc a small notification appears "Android debugging enabled" but when i use "adb devices" command nothing shows up!
Can anyone help me with this i'm completely lost here!
AmrBanawan said:
Ok i really can't figure this one out, I used adb many times while testing KFFAide tool so I am 100% sure my adb drivers are installed correctly, But since i switched to cm10.1 (Thanks hashcode) ADB cannot recognize my device anymore, I have enabled ADB on my KFHD and when i connect it to my pc a small notification appears "Android debugging enabled" but when i use "adb devices" command nothing shows up!
Can anyone help me with this i'm completely lost here!
Click to expand...
Click to collapse
Leave the device plugged in, go to Developer Setting and uncheck ADB debugging, then check it again. You should see a prompt, select OK for both.
seokhun said:
Leave the device plugged in, go to Developer Setting and uncheck ADB debugging, then check it again. You should see a prompt, select OK for both.
Click to expand...
Click to collapse
Ok thanks i tried but to no avail
AmrBanawan said:
Ok thanks i tried but to no avail
Click to expand...
Click to collapse
Yeah I actually have the same problem too now
Thanks for the heads up hash, got it on a usb stick now
---------- Post added at 11:41 PM ---------- Previous post was at 11:39 PM ----------
Protomartyr said:
Yeah I actually have the same problem too now
Click to expand...
Click to collapse
I had to manually check android debugging and usb debugging notify and it worked just fine.... make sure adb over network is not checked
Protomartyr said:
Yeah I actually have the same problem too now
Click to expand...
Click to collapse
AmrBanawan said:
Ok thanks i tried but to no avail
Click to expand...
Click to collapse
Why don't you guys try this, go into CMD while connected with the device (ADB debugging on), and type "adb devices" to start the daemon, then try the commands. Other than that, I don't know what else to do.
seokhun said:
Why don't you guys try this, go into CMD while connected with the device (ADB debugging on), and type "adb devices" to start the daemon, then try the commands. Other than that, I don't know what else to do.
Click to expand...
Click to collapse
Nope. Just get "List of Devices Attached" but no serial number. Checked device manager and it's showing up as a portable device. Probably will reinstall them and see if that solves it.
On a side note:
if we ran these commands in terminal emulator on the device, would that be sufficient?
Protomartyr said:
Nope. Just get "List of Devices Attached" but no serial number. Checked device manager and it's showing up as a portable device. Probably will reinstall them and see if that solves it.
On a side note:
if we ran these commands in terminal emulator on the device, would that be sufficient?
Click to expand...
Click to collapse
Yes
run the first command then pull it manually
But we need to know what's going on, i will need adb sometime soon when prokennexusa releases the next version of KFFAide
AmrBanawan said:
Yes
run the first command then pull it manually
But we need to know what's going on, i will need adb sometime soon when prokennexusa releases the next version of KFFAide
Click to expand...
Click to collapse
you can always open up your device manager and manually apply the adb drivers to your kindle
How do we know the boot0 partition is erased?
Sent from a Kindle Fire HD running CM10.1 using Tapatalk 2
had same probs on cm10 getting the files no matter what i tried.in windows 7 and xp it wouldnt install normal driver so i could see kindle as a drive so flashed an amazon zip and pc recognizes it without any problems and now have the files needed
dugoy13 said:
How do we know the boot0 partition is erased?
Sent from a Kindle Fire HD running CM10.1 using Tapatalk 2
Click to expand...
Click to collapse
Normally you would notice WiFi doesn't work under any circumstances same for BT. And when on Amazon's software it won't let you register.
Sent from my Amazon Kindle Fire HD using Tapatalk 2
I can't get ADB to find it either, think i'll revert back to stock to get the file then go back to CM - I notice though on CM turning USB Debugging on doesn't change anything in device manager, it still stays connected as a media device or camera, depending on which you have ticked in storage setting *shrugs*
Thank you Hashcode
PaulJCW said:
I can't get ADB to find it either, think i'll revert back to stock to get the file then go back to CM - I notice though on CM turning USB Debugging on doesn't change anything in device manager, it still stays connected as a media device or camera, depending on which you have ticked in storage setting *shrugs*
Thank you Hashcode
Click to expand...
Click to collapse
No don't, just type the command hashcode provided in terminal emulator and you'll find the backup in your sdcard, just copy it to your pc like normal!
You can do it from the terminal without typing ADB. that may be why people are confused. Start with hashcodes command but start with "su -c" in the terminal.
Sent from my Nexus S 4G using xda app-developers app
I've been trying for the past couple of days to root my Oneplus One. I started with this tutorial: (http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471) which is featured in the FAQ (which I've read through) and I've gotten stuck at one location.
You can test fastboot by connecting your device to your PC while booted into fastboot mode (power + volume up) and issuing this command:
Code:
fastboot devices
It should return your device serial number, if so, fastboot is working.
Click to expand...
Click to collapse
The ADB command appears to be working, but when I boot into fastboot mode (and when I'm not in it as well), the PC does not detect the phone. I've tried connecting it to multiple USB ports, and I'm using the official Oneplus One cable, so I'm at a bit of a loss of what to do.
However, I feel like I've identified where the source of the error is. If you see here: (http://i.imgur.com/IE1Bxjs.png), you can see that the phone is being detected under Portable Devices. In all of the tutorials I've looked through so far, it's been detected under something like "Android Phone" or "ADB Interface". I've tried various things to fix this, the most common of which is installing drivers onto/for the phone. I've tried the one here: (http://forum.xda-developers.com/showthread.php?t=1413293), which I know is for Archos phones, but should work similarly, as I tried both the Universal ADB driver and the Google one, from the SDK Manager. I kept getting an error telling me that: "the folder you specified doesn't contain a compatible software driver for your device."
I've also tried the one here: (http://www.makeuseof.com/tag/android-wont-connect-windows-adb-fix-it-three-steps/) (let me know if external links aren't allowed and I'll remove it.) This doesn't seem to work either, as I get this error (http://i.imgur.com/CLATXsl.png) when it tells me to:
If you cannot get any driver to work, you will need to force installation. Instead of choosing “Let me pick from a list of device drivers on my computer” in the previous step, you will choose “Browse for driver software on your computer” and manually find the directory where you installed Koush’s drivers.
The location on your hard drive looks something like this:
C:\Program Files (x86)\ClockworkMod\Universal Adb Drivers\
Windows will then install the drivers. From now on, whenever you connect the Android device with debugging enabled, Koush’s drivers will load in place of the ones that failed to work.
Click to expand...
Click to collapse
And now I'm posting here, praying that someone will have some sort of idea what to do. Any help at all would be greatly appreciated,
Fappled
EDIT: Managed to get it working, messing around with the drivers in device manager while in Fastboot mode seemed to work.
Fappled said:
The ADB command appears to be working
Click to expand...
Click to collapse
Feel your pain, I've been thru some pain myself with some weird issue, posted here yesterday. Though, my issue is different from yours, I have some ideas for you.
You say that adb works, so I assume your usb cable & PC are OK here.
I aslo assume that your Device Manager screenshots taken when connected to your phone in device mode (rom running). Don't worry about what you see in Device Manager just yet. Your goal is to make fastboot work, right. Note: Adb works in recovery mode and device mode, but not in fastboot mode. Fastboot works only in fastboot mode.
You could try this, put your phone in fastboot mode, then connect to your PC. Now, see what in your Device Manager. In my case, the phone is under Android Device>Android Bootloader Interface and I use Google driver. Then, try "fastboot devices" to see if your phone is detected.
If not, play with the driver in Device Manager (uninstall, rescan, install another). No need to unplug the phone. After the driver changed, see your Device Manager changed, and then try "fastboot devices".
I played with the driver changing a few time and got fastboot to work. I hope you get it to work too.
Hello Everyone,
I would like to learn how to remove bloatware Apps from my Android phone.
I have tried using "ADB commands" but for some reason my computer doesn't recognize/find my Android phone when I connect it to it.
Please help.
Thanks in advance
Download drivers for samsung and enabled adb developer option then type following "adb devices" press enter and should see serial number indicating phone connected via adb
petiolarissean said:
Download drivers for samsung and enabled adb developer option then type following "adb devices" press enter and should see serial number indicating phone connected via adb
Click to expand...
Click to collapse
Hello, and Thanks
I have done that exactly, but it still doesn't work.
And I can't figure out why is not working.
I have installed the Samsung driver, allowed the ADB function on my phone from "Developer Options" etc.
In addition to the advices by petiolarissean , check whether the driver works well, please.
In the 'Devices Manager' of your Windows, check the driver for your Android phone.
If this doesn't work yet, change an usb cable and then try again.
Only to have mentioned it:
So-called bloatware typically is housed in Android's locations /system and/or /system/priv--apps what only can get accessed by Android's root-user after successfully mounted as RW.
James_Watson said:
In addition to the advices by petiolarissean , check whether the driver works well, please.
In the 'Devices Manager' of your Windows, check the driver for your Android phone.
If this doesn't work yet, change an usb cable and then try again.
Click to expand...
Click to collapse
Thanks for your help
I think I will buy a new USB cable and give it a try, hopefully it will work.
Have a nice day
Sorry late reply.I have like 5 different phone.Hard core modder.
This question help alot
Even though you csnt get adb working
Can you still move files from your phone to pc or computer.Or nothing ay all.Your answr will tell me your problem
The screen on my Pixel 4a died - google is sending a box to send it back for warranty repair. However, before I send it I want to wipe all the data - it is rooted with Magisk. How do I wipe the data given I can't operate the screen - can't even turn it off.
has it previously been paired with your computer via ADB ?
3mel said:
has it previously been paired with your computer via ADB ?
Click to expand...
Click to collapse
yes - it shows up as a device with adb
nogods said:
yes - it shows up as a device with adb
Click to expand...
Click to collapse
hope this works for ya
Factory reset Android using ADB
I am trying to factory data reset my Oppo Neo 7 (Android 5.1) using ADB shell. Any way I can try and link to ADB shell?
android.stackexchange.com
nogods said:
The screen on my Pixel 4a died - google is sending a box to send it back for warranty repair. However, before I send it I want to wipe all the data - it is rooted with Magisk. How do I wipe the data given I can't operate the screen - can't even turn it off.
Click to expand...
Click to collapse
try flashing the stock rom from adb/fastboot
nogods said:
The screen on my Pixel 4a died - google is sending a box to send it back for warranty repair. However, before I send it I want to wipe all the data - it is rooted with Magisk. How do I wipe the data given I can't operate the screen - can't even turn it off.
Click to expand...
Click to collapse
A hammer does a full wipe in seconds...
This is one reason why you use a SD card as your data drive. Simply pull it, set a new Google password, done.
blackhawk said:
A hammer does a full wipe in seconds...
This is one reason why you use a SD card as your data drive. Simply pull it, set a new Google password, done.
Click to expand...
Click to collapse
the pixel 4a doesn't have an sd card
the ADB devices shows the phone's id with "unauthorized" next to it. All ADB commands return this:
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
maoriboi said:
try flashing the stock rom from adb/fastboot
Click to expand...
Click to collapse
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
\
Just to be clear: can you enter bootloader? If you're in ADB, type: adb reboot bootloader. If not, can you turn the phone off and then hold volume down while plugging the USB cable in?
Then commands will be fastboot erase userdata or fastboot -w
nogods said:
the pixel 4a doesn't have an sd card
Click to expand...
Click to collapse
Yes I know. Keep that in mind next time around as it makes life much easier.
All joking aside, sorry to hear about your issues.
AlexKarimov said:
Just to be clear: can you enter bootloader? If you're in ADB, type: adb reboot bootloader. If not, can you turn the phone off and then hold volume down while plugging the USB cable in?
Then commands will be fastboot erase userdata or fastboot -w
Click to expand...
Click to collapse
Nope - adb devices shows id number and "unauthorized". Any other adb commands return the
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
nogods said:
Nope - adb devices shows id number and "unauthorized". Any other adb commands return the
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Click to expand...
Click to collapse
has it previously been paired with your computer via ADB ?
Click to expand...
Click to collapse
yes - it shows up as a device with adb
So it looks like you never authorized it between the phone and the computer. When you enable USB debugging and then plug in a USB cable, a window will pop up with a check box and ask if you want to authorize/trust this device and you mark the box and click yes. I'm guessing you didn't do that? But what about turning it off and starting in fastboot mode. Forget ADB for the time being and start in fastboot mode. If that doesn't work, make sure you have the right drivers and try again. Otherwise, that's all I've got. I'm sorry...
AlexKarimov said:
yes - it shows up as a device with adb
So it looks like you never authorized it between the phone and the computer. When you enable USB debugging and then plug in a USB cable, a window will pop up with a check box and ask if you want to authorize/trust this device and you mark the box and click yes. I'm guessing you didn't do that? But what about turning it off and starting in fastboot mode. Forget ADB for the time being and start in fastboot mode. If that doesn't work, make sure you have the right drivers and try again. Otherwise, that's all I've got. I'm sorry...
Click to expand...
Click to collapse
this phone was rooted on this computer using adb and fastboot. How do I start it in fastboot? The screen is off completely - I can hear the phone because I set a shortcut key for Talkback so I know it is turning on, telling me there is no sim, and then reading my lock screen with my name, phone numbers, and email.
nogods said:
this phone was rooted on this computer using adb and fastboot. How do I start it in fastboot? The screen is off completely - I can hear the phone because I set a shortcut key for Talkback so I know it is turning on, telling me there is no sim, and then reading my lock screen with my name, phone numbers, and email.
Click to expand...
Click to collapse
Thank you for that info. So here is what happens.
1. I shut it down by pressing both power and down volume buttons while attaching it to a charger.
2. I start it in fastboot mode by holding down the down volume button while attaching it to the computer.
3. The computer notification says "preparing pixel 4a" and I heard the classic connected sound.
4. If I try "adb devices" I get back an empty list of devices (unlike when I just connected it without holding down the down volume button, so I think that means it is NOT in adb mode, right?)
5. But if I try "fastboot device" or any other fastboot command it merely says "waiting for any device"
nogods said:
Thank you for that info. So here is what happens.
1. I shut it down by pressing both power and down volume buttons while attaching it to a charger.
2. I start it in fastboot mode by holding down the down volume button while attaching it to the computer.
3. The computer notification says "preparing pixel 4a" and I heard the classic connected sound.
4. If I try "adb devices" I get back an empty list of devices (unlike when I just connected it without holding down the down volume button, so I think that means it is NOT in adb mode, right?)
5. But if I try "fastboot device" or any other fastboot command it merely says "waiting for any device"
Click to expand...
Click to collapse
That sounds like a driver issue. It's a different driver for each state the phone is in. If I remember right, the Google USB driver handles the ADB.
Here's the other one for fastboot
[TOOL][WINDOWS] 15 Seconds ADB Installer Reborn V2.0 - ADB/Fastboot, and Drivers.
15 Seconds ADB Installer Reborn V2.0 Introduction: We can all agree with the fact that the Android Debug Bridge (ADB) is one of the most important tools when it comes to developing for android, uninstalling bloatware, flashing recoveries...
forum.xda-developers.com
Once connected in fastboot mode, you'll have to assign the driver manually. Don't let the computer do it, it will almost always say you have the best one already. In device manager, right-click the phone(unknown android device, i think) and update driver. Then select 'browse my computer for drivers' and then 'let me pick from available drivers on my computer'.
AlexKarimov said:
That sounds like a driver issue. It's a different driver for each state the phone is in. If I remember right, the Google USB driver handles the ADB.
Here's the other one for fastboot
[TOOL][WINDOWS] 15 Seconds ADB Installer Reborn V2.0 - ADB/Fastboot, and Drivers.
15 Seconds ADB Installer Reborn V2.0 Introduction: We can all agree with the fact that the Android Debug Bridge (ADB) is one of the most important tools when it comes to developing for android, uninstalling bloatware, flashing recoveries...
forum.xda-developers.com
Once connected in fastboot mode, you'll have to assign the driver manually. Don't let the computer do it, it will almost always say you have the best one already. In device manager, right-click the phone(unknown android device, i think) and update driver. Then select 'browse my computer for drivers' and then 'let me pick from available drivers on my computer'.
Click to expand...
Click to collapse
Thank you, thank you, thank you. You were correct about the driver issue. I downloaded the official google driver, and now it shows as a device in fastboot. Thanks again.
nogods said:
Thank you, thank you, thank you. You were correct about the driver issue. I downloaded the official google driver, and now it shows as a device in fastboot. Thanks again.
Click to expand...
Click to collapse
nogods said:
Thank you, thank you, thank you. You were correct about the driver issue. I downloaded the official google driver, and now it shows as a device in fastboot. Thanks again.
Click to expand...
Click to collapse
O
AlexKarimov said:
That sounds like a driver issue. It's a different driver for each state the phone is in. If I remember right, the Google USB driver handles the ADB.
Here's the other one for fastboot
[TOOL][WINDOWS] 15 Seconds ADB Installer Reborn V2.0 - ADB/Fastboot, and Drivers.
15 Seconds ADB Installer Reborn V2.0 Introduction: We can all agree with the fact that the Android Debug Bridge (ADB) is one of the most important tools when it comes to developing for android, uninstalling bloatware, flashing recoveries...
forum.xda-developers.com
Once connected in fastboot mode, you'll have to assign the driver manually. Don't let the computer do it, it will almost always say you have the best one already. In device manager, right-click the phone(unknown android device, i think) and update driver. Then select 'browse my computer for drivers' and then 'let me pick from available drivers on my computer'.
Click to expand...
Click to collapse
yup - looks like it worked:
Erasing 'userdata' OKAY [ 15.171s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Erasing 'metadata' OKAY [ 0.158s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Finished. Total time: 15.797s
What nows "not automatically formating" mean?
nogods said:
O
yup - looks like it worked:
Click to expand...
Click to collapse
Awesome, thanks for the updates. I'm glad you got it going
nogods said:
What nows "not automatically formating" mean?
Click to expand...
Click to collapse
I'm not sure about this, I've never encountered that as far as I know. Did it say "can't determine partition type" after that?
hi guys I need help to recover some personal photos I had saved on my device. The phone has a broken screen and touch so I cannot use a mouse or try to blindly unlock it, but it has been rooted and usb debugging is enabled; unfortunately my pc is not authorized by the phone and I have no way to authorize it through the pop up without a screen. I have searched around many forums to find a solution but it seems every time there was something wrong, so I need some help.
The solution that got me the nearest to a conclusion that I tried are:
using adb in custom recovery (which I do have) and trying commands like "adb pull /sdcard" which resulted in "pull: building file list... 0 files pulled. 0 files skipped.", I don't understand why it's unable to pull any file.
trying to authorize usb debugging for my pc through adb by "adb push adb_keys /data/misc/adb", adb_keys is the adbkey.pub file in the .android folder renamed. I can confirm i pushed them since "adb pull /data" pulled "data/adb/misc/adb_keys" as the only file, but I still don't have authorization
I'm not too literate in this kind of commands so please be patient but I really need help
RECAP OF MY PHONE STATUS
Xiaomi Mi 10 5G is the device
both screen and digitizer broken, I'm not able to see the screen or use touch (but I'm 100% sure the phone still works)
Android 12 rom (xiaomi.eu stable)
custom recovery available
rooted device
usb debugging enabled
no device authorized by the phone for usb debug
I found somewhere on xda that the problem could be solved by mounting/unmountind sdcard, but I have no ideea hoe to do that
damndaniel0 said:
hi guys I need help to recover some personal photos I had saved on my device. The phone has a broken screen and touch so I cannot use a mouse or try to blindly unlock it, but it has been rooted and usb debugging is enabled; unfortunately my pc is not authorized by the phone and I have no way to authorize it through the pop up without a screen. I have searched around many forums to find a solution but it seems every time there was something wrong, so I need some help.
The solution that got me the nearest to a conclusion that I tried are:
using adb in custom recovery (which I do have) and trying commands like "adb pull /sdcard" which resulted in "pull: building file list... 0 files pulled. 0 files skipped.", I don't understand why it's unable to pull any file.
trying to authorize usb debugging for my pc through adb by "adb push adb_keys /data/misc/adb", adb_keys is the adbkey.pub file in the .android folder renamed. I can confirm i pushed them since "adb pull /data" pulled "data/adb/misc/adb_keys" as the only file, but I still don't have authorization
I'm not too literate in this kind of commands so please be patient but I really need help
RECAP OF MY PHONE STATUS
Xiaomi Mi 10 5G is the device
both screen and digitizer broken, I'm not able to see the screen or use touch (but I'm 100% sure the phone still works)
Android 12 rom (xiaomi.eu stable)
custom recovery available
rooted device
usb debugging enabled
no device authorized by the phone for usb debug
Click to expand...
Click to collapse
There is a way to do it, but it costs money
@damndaniel0
If USB-MTP mode is enabled on phone - what should be default - then you can access all user-data stored in /storage/emulated/0 directory where among others photos are stored.
See also here:
MTP USB Device Driver Windows 10 64bit Driver | Device Drivers
MTP or (Media Transfer Protocol) is a set of custom extensions to the Picture Transfer Protocol (PTP) devised by Microsoft, to allow the protocol to be used for devices other than digital cameras, for example digital audio players such as MP3 players, and other portable media devices, for...
oemdrivers.com
xXx yYy said:
@damndaniel0
If USB-MTP mode is enabled on phone - what should be default - then you can access all user-data stored in /storage/emulated/0 directory where among others photos are stored.
See also here:
MTP USB Device Driver Windows 10 64bit Driver | Device Drivers
MTP or (Media Transfer Protocol) is a set of custom extensions to the Picture Transfer Protocol (PTP) devised by Microsoft, to allow the protocol to be used for devices other than digital cameras, for example digital audio players such as MP3 players, and other portable media devices, for...
oemdrivers.com
Click to expand...
Click to collapse
If you mean simply to connect the phone through usb to pc, I cannot do that because MIUI asks everytime if I want to transfer photos, files or just charge with a pop up on screnn (which I obviously cannot do)
iBowToAndroid said:
There is a way to do it, but it costs money
Click to expand...
Click to collapse
what would it be
damndaniel0 said:
If you mean simply to connect the phone through usb to pc, I cannot do that because MIUI asks everytime if I want to transfer photos, files or just charge with a pop up on screnn (which I obviously cannot do)
Click to expand...
Click to collapse
Not in system but in custom recovery (which you do have).
Timmmmaaahh! said:
Not in system but in custom recovery (which you do have).
Click to expand...
Click to collapse
Honestly I did not try, but I don't remember the phone directory showing up in windows file explorer after connecting the phone in recovery mode, I'll try againg when I'm home and I'll let you know
anyway I checked and no, I cannot access phone files
In Recovery mode you should can run
Code:
adb devices
adb pull <LOCATION_OF_DATA_OF_INTEREST> <STORAGE_LOCATION_ON_PC>
xXx yYy said:
In Recovery mode you should can run
Code:
adb devices
adb pull <LOCATION_OF_DATA_OF_INTEREST> <STORAGE_LOCATION_ON_PC>
Click to expand...
Click to collapse
unfortunately the result of this operation is always "pull: building file list... 0 files pulled. 0 files skipped". I tried already to pull form /sdcard, /storage, /data. Am I getting the location wrong?