Related
Where would I start to troubleshoot an issue with the MTP Application?
If I select the Media Player or Kies options, the MTP Application continually crashes and restarts every second.
I have connected the device in USB Debugging mode, then reconnected again and it still does it.
I've done the driver installation in the kies application and I've reset both the PC and the phone, behaviour is consistent. Kind of frustrating as I can't upload media (DRM....).
IF anyone has advice on where I could start troubleshooting this issue I would greatly appreciate it
More info:
Win Vista 32Bit
Stock galaxy S as delivered from the shop EDIT: I9000DTJF3
Kies 1.5.1.10071_32
spenceee said:
Where would I start to troubleshoot an issue with the MTP Application?
If I select the Media Player or Kies options, the MTP Application continually crashes and restarts every second.
I have connected the device in USB Debugging mode, then reconnected again and it still does it.
I've done the driver installation in the kies application and I've reset both the PC and the phone, behaviour is consistent. Kind of frustrating as I can't upload media (DRM....).
IF anyone has advice on where I could start troubleshooting this issue I would greatly appreciate it
More info:
Win Vista 32Bit
Stock galaxy S as delivered from the shop EDIT: I9000DTJF3
Kies 1.5.1.10071_32
Click to expand...
Click to collapse
Here is a fix my friend but say goodbye to your saved games and files..
[try transferring or backup your files using wifi or bluetooth in case you have important files on your phone]
[and also, try to backup your phone contacts to your sim because formatting will wipe your entire phone's data]
Once that is done, try to do the following.. go to Settings -> SD card and Phone Storage -> Unmount SD -> Format SD
Once you have formatted the SD card, go to Settings -> Privacy and then choose "Factory Data Reset".
Your phone should now be detected once you connect it to your computer this time around.
Hope this helps.
I've done this once before. I spent a significant amount of time getting the right data under my contacts and linking them properly, I need to know how to find out why kies is borked. Otherwise I'll wipe the phone and possibly be stuck in the same situation again.
Have you had this issue occur and this fixed it though?
I had similar problem. Tried everything you mentioned and nothing helped.
In the end I formated externas SD card. Flashed SG1 firmware and rooted the device (all done in a matter of 30 min).
It fixed the MTP aplication crashes (dont know what of three really did it).
I'd been having the same problem on my Galaxy S.
It had been working fine, and I've done nothing to the phone to change anything with it.
Just opened the MTP App on the phone, then just crash, restart, crash etc and kept looping like that.
(Mines the Optus AU version too - might be a problem with something on there?)
Anyways I used the WebSharing app to download all my files to a zip on my computer, then unmounted and formatted the internal SD card - and then rebooted the phone.
Once it rebooted, moved the zip files (unzipped) back onto the internal SD as they were originally and plugged into the USB and it all worked again.
Hello everyone, I'm new here and own a Galaxy S now for two weeks. Yesterday I to noticed/encountered the rebooting mtp application when plugging in the cable while the USB settings are set to 'connect to Kies'.
To be short I tried all offered solutions found on this topic on the web and in the end only the unmounting and formatting of the INTERNAL sd has helpt.
I made a backup via Websharing since selecting the 'mass storage' option didn't work for me yesterday. Obviously this is a slow way to make a backup. Try to only back-up what you deem to be imported files.
So the unmounting - formatting and rebooting (mounting) of the INTERNAL cards is the quickest solution and will safe you hours of work!
HOWEVER
Today I had the same rebooting MTP issue again. But since re-installing kies version 1.5.1.10083 I'm able to connect to the pc via 'Mass Storage'
You will see drive F: and drive G: if you at least succeed in connecting via the mass storage option.
I than did 2 things:
1.
I recently made some pictures and also copied some pictures from my pc to the G: drive ( INTERNAL SD) I renamed the pictures to short names so they didn't exceed 16 characters (one of the solutions I read online ).
2.
In the map data I found folders with the names of in my case Touiteur and Beautiful Widgets. Both folders contain a CACHE folder. I deleted the complete touiteur folder and thus also its CACHE folder.
Now I connected my Galaxy S to the usb cable again and behold, the rebooting of the MTP has stopped!
Now I'm not technical at all and have struggled with this issue the whole of yesterday ending up formatting my internal SD. And to be honest I don't know for sure what the working solution is in the end but can narrow it down to 2 things you may try if you can connect via the 'mass storage' option:
1. try giving pictures in G:\DCIM\folder name a short name if they are long or try to remove the pictures completely (make backup) just to see if either of this works.
2. Delete the CACHE folders in the APP folder under G:\data and see if this works
Again, I'm unsure what or why I solved it on my Galaxy S but give it a try if you have tried everthing else and do not want to format your INTERNAL SD
I've got a fix
Alright guys, I posted a video on how to repair the MTP application problem, especially for you spencee, check it out. Go to youtube and copy paste: MTP Application Crash Fix. And click the first one. It's by abrar447. Hope this helps!
Ok, I'm having this issue again! I watched the video by Abrar447 and deleted every single file in cash I could find ( actually did a search on the word 'cache' on the internal drive. Although I know this should now work my TMP application keeps rebooting. Am I missing something here ?
qman97 said:
Alright guys, I posted a video on how to repair the MTP application problem, especially for you spencee, check it out. Go to youtube and copy paste: MTP Application Crash Fix. And click the first one. It's by abrar447. Hope this helps!
Click to expand...
Click to collapse
Thanks again for posting this video. It actually worked for me, been trying to find the solution to that MTP crashing problem when trying to connect in Kies mode.
narrowed it down
I have this problem too. I saw the youtube vid and decided i'd delete one cache folder a time to see what was causing the problem. Found out that is was 'Sound Hound'. So i deleted the cache folder, MTP worked, then i used the app so it would create another cache folder, MTP clashed. Did it many times.
Hope this helps.
Aussi Optus
DTJG4
Root + One Click Lag fix
Really weird problem , after clearing the cache it works again.
I reccomend using CacheMate for Root Users (free or pro) which you can find in the market , you dont need to delete all the cache manually then
Hi..
Anyone know the exact name for the MTP Application..is there a way to replace the problematic version with a working version..On my ship with ROM. i9000dxjf4..MTP application showed steadily without keep crashing..
MtpApplication.apk
MtpApplication.odex.
If anyone has the working version (no crashing on Kies connection). can post here..I would like to experiment to overwrite it with a working version..
dehem333 said:
Really weird problem , after clearing the cache it works again.
I reccomend using CacheMate for Root Users (free or pro) which you can find in the market , you dont need to delete all the cache manually then
Click to expand...
Click to collapse
Perfect solution. Did the clearing manually - no success. Only Cachemate did the trick Thanks!
Soundhound
Hello,
I also had a lot of issue's with Kies. I also tried a lot. But the one thing that helped was removing SOUND HOUND (application and directory)
Hope this helpes for some people!
Cheers
I emptied the cache under the Android folder and it started working again. The thing is, as soon as I open the gallery, the cache is written again. I'll try to see if the new update fixed the issue.
The problem is the not cache in itself. The bug is the '16 character extension' problem. Google it if you like. The solution is to delete all the files having its last extension greater then 16 char, in your internal or external SD card.
I asked about the fix on twitter, the reply was this.
I found a small program which tell you which files are the problem.
Credits to the original creator, browse your SD card directory
Hello everybody,
i'm a bit new to Galaxy I9000 but i had the same issue with Kies and MTP apps. Actually i found out that the issue seems to be linked to file extension longer than 16 chars. Usually those files are inside cache directories so, you should just cancel them to fix it. I've got kies running correctly since then (last update of Kies running n Windows 7 64 bit). I know there is also a little app to scan files to search the 16 digits extension called "FileSearcherforKiesFix.rar" you can find it and download just putting it in google.
Hope this can help!
Regards
Mic
APK version?
karanits said:
The problem is the not cache in itself. The bug is the '16 character extension' problem. Google it if you like. The solution is to delete all the files having its last extension greater then 16 char, in your internal or external SD card.
I asked about the fix on twitter, the reply was .
I found a small program which tell you which files are the problem.
Credits to the original creator, browse your SD card directory
Click to expand...
Click to collapse
Is there an apk version of this? I'm unable to connect the phone to my x64 win7 at all right now...
Cheers,
Peter
Have tried everything and nothing seemed to work...
The "FileSearcherforKiesFix" finds some problematic files, but not all off them. Manually deleting long file names and cache folders seems to be insufficient either.. I think that there must be some cache files in other partitions that we cannot access via "Mass Storage" that are causing problems too. So we have to clear those files...
But thanks to a comment in this topic I have found a working solution:
1º Delete any problematic file with the "FileSearcherforKiesFix" method.
2º Use this app: http://www.appbrain.com/app/com.aac.cachemate.demo , with the option "PowerClear" turned on, and clear all cache from the phone.
After this the MTP thing installed instantly and now everything works.
NOTE: The "PowerClear" option may cause some undesired effects in some apps.. Backup first, or, use at your own risk.
For me the problem started when I copied lots of MP3 to my phone.
I solve this like this:
I connected my phone using the media mode.
Searched for all *.mp3 files
renamed them all to *.! (whatever extension)
(I use a program called FAR Manager, which is something similar to the old Norton commander, but for windows)
Connected with Kies and it got recognised
Hope it helps others
Hello !
I am feeling really down today after been trying to get my phone working again.
There is a huge problem currently, I am really annoyed that it doesn't work at all.
First thing, my phone won't start after update it just boot loops and never seem to end it.
First thing I noticed /boot, /cache /system and most things are gone, I can load up recovery but nothing more. I have no idea what happened but the whole image folder was wiped and I had to myself put in the CWM recovery.
I can't do an upgrade "again" as it will be stuck @ the unpacking part without starting it at all.
I been trying with 2.3 V2 and with B133(My stock rom I got).
If anyone has a solution that can solve this problem please help out if you could. Also if you are about to tell me get this and that, please most cases I haven't seen any of the Firmware roms in @modaco wiki links work. Means I can't download them, so if you happen to have spare copy please upload it and link it to me. I have been googling and looking through this section twice, nothing really worked out.
Thanks in advance !
If you didn't erase the .cust_backup partition which contain the image folder with all system' s .img files, then maybe it' s damaged. I had some problems with this partition before and when I checked it with windows check disk it repairs it and I had no problems from then. So, try this, and if you still haven' t any file on image folder, you can find the original folder on X5' s forums. Is definately here, but I don't remember where is the link and I don't gonna search it for you. If you cannot find it, you can allways reflash the original rom. If you fix the partition(if this is the problem), I don't think that you'll have problems with update any more.
dancer_69 said:
If you didn't erase the .cust_backup partition which contain the image folder with all system' s .img files, then maybe it' s damaged. I had some problems with this partition before and when I checked it with windows check disk it repairs it and I had no problems from then. So, try this, and if you still haven' t any file on image folder, you can find the original folder on X5' s forums. Is definately here, but I don't remember where is the link and I don't gonna search it for you. If you cannot find it, you can allways reflash the original rom. If you fix the partition(if this is the problem), I don't think that you'll have problems with update any more.
Click to expand...
Click to collapse
Hello, thanks for the reply.
I have no idea about this .cust_backup partition and how I am supposedly to access it via windows. Also the thing you said about fixing partition within Windows, the check disk thing. I am not sure about that part either as I can load CWM and it can read the partitions but they are empty. Also there is nothing in this forums that contains original things, only way for me to fix this if someone have extra copy and can guide me on how and where to place the all needed files. I am pretty sure it's only things that are missing and I can't get a grip out of this.
So to sum up what my problem is.
I did an upgrade from 2.2 to 2.3 with official firmware, it worked out normally but after a reboot my phone became stuck in an endless loop, I can't do anything and it will not I repeat it will not allow me to "re flash" any firmware I tried so far, the 2.3 V2 and B133.
I am begging someone in this forum section, please if you have the knowledge about this problem care to help?
I can't get a refund out the phone warrenty is off and I do not have that much spare money.
Thanks in advance !
If you can get to recovery, wipe cache and data. It should be possible in stock recovery.
The cust partition has all the images for bootloader, recovery etc. You can get to it with the pink screen. Reformatting and then reinserting the images and files could help, but try that when nothing else works.
I can't give you good help via phone, but try wiping data first. Also, try if you can use some other sd card.
Sent from my U8800 using Tapatalk
Blefish said:
If you can get to recovery, wipe cache and data. It should be possible in stock recovery.
The cust partition has all the images for bootloader, recovery etc. You can get to it with the pink screen. Reformatting and then reinserting the images and files could help, but try that when nothing else works.
I can't give you good help via phone, but try wiping data first. Also, try if you can use some other sd card.
Sent from my U8800 using Tapatalk
Click to expand...
Click to collapse
The most common things I have already done, but do enlighten me what this "custom" parition is. Because in windows I do not see such partition I see a removable partition which I have now added a folder called image with these containing files.
http://forum.xda-developers.com/showthread.php?t=1370960
EDIT ** Also regarding to first person who said about Windows partition manager. The thing is I see a lot of partitions and there is no labeling for them, might be because they are ext2/3 or even something else? In anycase I can't do so much I just find it really odd I have many duplicates and I am guessing that must be errors... Because I am seeing the main recovery partition which has no label too... its at 240 MB where 135MB is used. Lastly there is my internal SD card empty and healthy still I can't reach it within Windows if I do not mount it...And can't now without going into the android OS. I Have loads of free space "partitions I don't understand why they are there".
**
Thanks for helping out, it feels not good to have a half dead phone, it's still not solved :'-(
The .cust_backup is the mount point on android for this removable partition with image folder. In windows haven' t this name. I didn't mean to use the windows partition manager, just to use windows explorer, right click on the partition and choose properties, then tools and then check disk. Of course you can use partition manager too, but because as you found there are all no labeled other partitions there and is a bit confused.
As you mentioned, you found the original image folder and you replaced the files. Did you tried to do the update again after that?
Also you can see and the internal sd partiton, but you need linux system. This partition is not fat32, so windows cannot see it.
dancer_69 said:
The .cust_backup is the mount point on android for this removable partition with image folder. In windows haven' t this name. I didn't mean to use the windows partition manager, just to use windows explorer, right click on the partition and choose properties, then tools and then check disk. Of course you can use partition manager too, but because as you found there are all no labeled other partitions there and is a bit confused.
As you mentioned, you found the original image folder and you replaced the files. Did you tried to do the update again after that?
Also you can see and the internal sd partiton, but you need linux system. This partition is not fat32, so windows cannot see it.
Click to expand...
Click to collapse
I have placed all things that I got from here.
http://forum.xda-developers.com/showthread.php?t=1370960
And I can't run the upgrade firmware, it gets stuck at first stage which is to unpack the the update.app thing.
It just stays like that not blinking and frozen.
Did you tried now that you have the original files, to go to recovery mode and wipe data etc?
Also when you try to do the upgrade do you have the device connected with the cable?
I had this problem once and I think that when I disconnected the cable(or maybe wasn' t connected and I connected it, I don't remember well), the proccess bar starts to moving after a while and the upgrade completed successfully.
dancer_69 said:
Did you tried now that you have the original files, to go to recovery mode and wipe data etc?
Also when you try to do the upgrade do you have the device connected with the cable?
I had this problem once and I think that when I disconnected the cable(or maybe wasn' t connected and I connected it, I don't remember well), the proccess bar starts to moving after a while and the upgrade completed successfully.
Click to expand...
Click to collapse
You are not understanding me :-(, I have wiped already millions of times in millions of different ways just to get it work. And no, I don't have the device connrected when I upgrade, it won't work properly then, I have tried to wait for the progress bar to "start" move it won't happen the battery will die, and nothing happened.
I can't go in with normal Recovery mode, can only go in with CWM, the normal recovery mode is really small, I mean only 3mb, while the froyo version is 5mb. Now I am asking if you have the time to upload the image files from 2.3 V2, the ones in forums are for V1. Which I don't know might conflict.
Thanks again for trying to help me out, this is really frustrating to get it to work.
**EDIT**
I worked it out !
I think I understood what you meant, I did as you told I started first with pluggin in the charger forced it to upgrade and now it's upgrading, thank you so much dancer_69. I was going to go tomorrow to buy a new 2nd hand smartphone. But now I can save my money for other things !
**EDIT of EDIT **
I seem to have downgraded to B133, I will try now with B158 2.3 V2 again and hopefully it will work now.
Yes, wasn't clear because I don' t remember what I've done and solve it. But I think that I did it like you discribed too.
Anyway I'm glad that was helpful(kind of)..
And don' t give up so soon with smartphone' s bricks, I've faced brick kind of problems many times and if the device it' s not completely dead, there is something you can do. Maybe need more search or many tries(sometimes the same things) but at the end(and of course If there isn't a hardware problem) device can unbrick.
I read the threads concerning about this problem but I seem to be only one to have it.
So this is what happened
- I was running stock 4.2.1 rooted with CWM Recovery, awesome
- I see CyanogenMod 10.1 is available, even better lets flash it. It was a nightly version but ok I have never had problems with nightlies
- I make a Nandroid of my stock ROM
- Factory reset, clear cache, dalvik
- Flashed CM10.1
- It booted fine, but first thing I see is "Setup wizard has stopped" , "process com.google.xxxxxxxxxx has stopped" - basically I can't do anything
So I get back in CWM, clean everything again, flash it again since I thought maybe something went wrong when installing it. I got the same problem, again, I can't do anything. So I get back into recovery thiniking I can recover my Nandroid.
Well, no, since I suppose everytime I factory reset, all the files on the Nexus get moved into a new "0" folder, and usual folders like DCIM or ringtones get created too. So I basically have 4 of those. My files which were previously on stock ROM are all in
Computer\Nexus 7\Internal storage\0\0\0\0
Naturally, CWM thinks my backup ROM is in Internal Storage - clockwork mod so I can't recover the ROM.
Logically I decide to move the clockwork mod folder to a place in which recovery wants it. This is where the problems begin. I can't copy anything from N7. Windows explorer creates empty "copying" dialogue and doesn't do anything, or says that it is "calculating time required to copy files" (Windows 7 Ultimate 64 bit)
How do I copy files properly, or at least - how do I restore my ROM?
Thanks.
Use the "adb pull" command?
Maybe adb shell cp /path/to/nandroid /where/you/want/to/move/it
Use cp -r if the android is a folder, sorry its been a while since I checked on mine
Thanks for your replies. In the end, before I saw your answers I raged and just left it to "calculate time" or whatever, and to my surprise when I got back it was copying. I guess it needs time. Thanks though, I hope someone finds your answers useful.
For some reason I cannot move files via Windows 7 file explorer to the Nexus. I can and have done this on every other mobile device that I've had before. What's the difference? Why can't I place pics and videos on it?
A few more details would be super helpful to give you a good answer. Start with if you are running a custom ROM and what if anything you have tried to solve the problem.
When you plug in your usb look under settings - storage and see if there is the option to mount storage.
Note 2 - Nexus 7 - Charge - Player 5.0 - Fascinate
<><><><><><><><><><>
Read twice, flash once
For some reason, now it's letting me even though I didn't change anything. Mods can delete this if they want. And thank you ezas for your reply.
Glad you got it sorted out.
Note 2 - Nexus 7 - Charge - Player 5.0 - Fascinate
<><><><><><><><><><>
Read twice, flash once
Brian Gove said:
For some reason, now it's letting me even though I didn't change anything. Mods can delete this if they want. And thank you ezas for your reply.
Click to expand...
Click to collapse
In my limited experience using MTP (rooted stock N7 4.2.2 + Win 7 x64), what seems to work well is:
- copying files FROM the N7 which were already in the /sdcard mount point when the N7 last booted,
- copying files TO the N7 into a folder which already existed inside the /sdcard mount point when the N7 last booted.
(I should also point out that moving files this way seems to be 5-7 times faster than using "adb push" or "adb pull")
What seems to only work sporadically is trying to copy or write to things which were "recently created" in the /sdcard mount point. For instance, if you generate a large set of files using Android, you won't be able to find them from the PC until a seemingly random ? amount of time later. Similarly, if you create a folder on the N7 (let's say by using a file manager) with the intent of pushing some files there from the PC, you won't see that folder show up in a reasonable amount of time.
This behavior actually does make sense - in principle, it is impossible to allow instantaneous write access to a file system from two independent hosts without running risks of filesystem corruption. In previous versions of Android, external SD cards could be accessed using USB Mass Storage drivers, but only exclusively by either the Android device or the PC - never at the same time. The SD card had to be unmounted from Android in order to be seen by the PC.
But, what is curious is the delays involved. I wanted to do something similar to this the other day (copying a nandroid backup from the PC to a "new" folder on the N7), and thought that by correctly disconnecting from the PC followed by reconnecting to the PC would allow the newly-created folder to "show up" via MTP on the PC. No such luck however; I needed to reboot the N7 for that to happen.
Bottom line is that MTP will work (and quickly, too! - better than 10 MB/sec) - but only with the above limitations in mind. When in doubt, reboot the N7.
I've managed to softbrick my nexus 10 by trying to disable extra services (was getting about 1.5 hours battery life with media services running the processor 100% all the time). It worked wonderfully (no negative side effects, went back to 10+ hours with the screen on, or days on standby) until I reboot it and now it won't load past the moving colors (Android 4.4.3, unlocked and all that).
I have TWRP, I was hoping to backup everything possible via usb, but it seems it's incapable of doing so. ADB backup can't be done using TWRP since there's no unlock function (reaaal useful there, recovery mode that doesn't support backups) and adb pull fails if I try to pull everything since there are files and folders with invalid file names (who puts ":" in folder names? they should be shot), and I don't know specifically what to pull, I was just going to get everything put back what I found was missing that I needed. There's no room to do a backup onto the device, and since the N10 has to sd/microsd, well... Useless options are useless.
Is there anyway to just do a proper backup with TWRP over USB? Or is the "recovery" mode as useless as I think it is when it comes to backups? (I'm aware I can get the tablet back to working order if I disregard the data on it, this is a question about backing things up before doing so)
Edit: Also, I have a pro version of SkipSoft ToolKit, but unless you can actually load into the OS the toolkit can't do anything at all.
Just really frustrated with the lack of doing something as basic as copying files from one place to another. Been messing with this all morning.
Diet6 said:
I've managed to softbrick my nexus 10 by trying to disable extra services (was getting about 1.5 hours battery life with media services running the processor 100% all the time). It worked wonderfully (no negative side effects, went back to 10+ hours with the screen on, or days on standby) until I reboot it and now it won't load past the moving colors (Android 4.4.3, unlocked and all that).
I have TWRP, I was hoping to backup everything possible via usb, but it seems it's incapable of doing so. ADB backup can't be done using TWRP since there's no unlock function (reaaal useful there, recovery mode that doesn't support backups) and adb pull fails if I try to pull everything since there are files and folders with invalid file names (who puts ":" in folder names? they should be shot), and I don't know specifically what to pull, I was just going to get everything put back what I found was missing that I needed. There's no room to do a backup onto the device, and since the N10 has to sd/microsd, well... Useless options are useless.
Is there anyway to just do a proper backup with TWRP over USB? Or is the "recovery" mode as useless as I think it is when it comes to backups? (I'm aware I can get the tablet back to working order if I disregard the data on it, this is a question about backing things up before doing so)
Edit: Also, I have a pro version of SkipSoft ToolKit, but unless you can actually load into the OS the toolkit can't do anything at all.
Just really frustrated with the lack of doing something as basic as copying files from one place to another. Been messing with this all morning.
Click to expand...
Click to collapse
Do you still need help? What about mtp mounting? You can pull * for a whole folder
Why not adb sideload a new rom?
I don't think I can MTP mount a Nexus 10, at least not in recovery mode. What I ended up doing was buying a OTG usb drive and making a backup to that. Problem was it split the tar over 4 files, which corrupted them (or at least made them not work with 7zip or tartool) fortunately I was able to get them to work with cygwin enough to get the files I wanted. I didn't want to sideload a new rom until I had backed up certain application data just in case it removed it.
All in all, had to buy a OTG usb drive (I would have just bought a cable but all the stores around here had was this "Dane 16gb OTG drive". So 20 bucks later I had the files I needed. Still annoyed that you can't do a ADB backup from fastboot or recovery mode, it seems like those would be the best places because no system files are in use, but who knows maybe the developers know something I don't.
In summary:
TWRP recovery cannot confirm a ADB backup over USB. ADB backups can only be done from the operating system.
TWRP recovery mode can only backup to OTG (if your device supports it, Nexus 10 does), but if the backup is larger than 2gb it will split the file and you will need some form of linux to extract it.
ADB cannot copy every file in recovery mode over USB due to certain file names being invalid for NTFS (this is probably not a problem on other file system types), this is problematic since the "pull" command has no skip option, it just fails when it hits one of these files.
Well you can easily flash latest rwrp that does well on my Linux mount internal storage but another solution is just flashing a rom with abd sideload and the'the back up from pc the content
---------- Post added at 04:24 AM ---------- Previous post was at 04:23 AM ----------
Or that will just un brick your tablet
Diet6 said:
Still annoyed that you can't do a ADB backup from fastboot or recovery mode
Click to expand...
Click to collapse
adb doesn't work in fastboot mode, only recovery or Android itself.
Diet6 said:
In summary:
TWRP recovery cannot confirm a ADB backup over USB. ADB backups can only be done from the operating system.
Click to expand...
Click to collapse
Maybe because /data (not talking about /data/media) wasn't mounted?
Diet6 said:
TWRP recovery mode can only backup to OTG
Click to expand...
Click to collapse
Huh?
Diet6 said:
ADB cannot copy every file in recovery mode over USB due to certain file names being invalid for NTFS (this is probably not a problem on other file system types), this is problematic since the "pull" command has no skip option, it just fails when it hits one of these files.
Click to expand...
Click to collapse
That's NTFS' problem, not TWRP's.
beekay201 said:
1. adb doesn't work in fastboot mode, only recovery or Android itself.
2. Maybe because /data (not talking about /data/media) wasn't mounted?
3. Huh?
4. That's NTFS' problem, not TWRP's.
Click to expand...
Click to collapse
1. I was just covering that you can't actually do a ADB backup unless you have access to android OS, in case anyone else came across this. (I didn't know when I started, and it took awhile to find it said concretely anywhere)
2. I made sure everything was mounted, the issue is when you send a backup command over ADB it says the "Now unlock your device and confirm the backup operation" message in terminal which you can't do from recovery mode on the device, thus you cannot do a ADB backup command over TWRP (or other recovery modes I'd imagine).
3. I should have been more specific. TWRP can do a backup to the device itself (built in storage), SD card (if your device has one and you mount it), or a OTG (on the go) device via usb directly to media like a flash drive. It cannot issue a backup over USB to a computer.
4. Completely agree it's a NTFS issue, but it could be mostly avoided by allowing files that error to be skipped or renamed rather than terminating the process. (I understand that's on the android devs since pull is made by them, and I doubt they would care to improve the command for a file system I doubt they use). Again I mostly included that so if anyone else is trying to figure it out they can stop looking for "a way" and just accept it can't be done.
Ultimately Khaon is right in that sideloading a rom would have unbricked it and I could have done the ADB backup then, I just wasn't sure how that might affect the app data storage so I was looking for a way to back it up before doing that.
Diet6 said:
1. I was just covering that you can't actually do a ADB backup unless you have access to android OS, in case anyone else came across this. (I didn't know when I started, and it took awhile to find it said concretely anywhere)
2. I made sure everything was mounted, the issue is when you send a backup command over ADB it says the "Now unlock your device and confirm the backup operation" message in terminal which you can't do from recovery mode on the device, thus you cannot do a ADB backup command over TWRP (or other recovery modes I'd imagine).
3. I should have been more specific. TWRP can do a backup to the device itself (built in storage), SD card (if your device has one and you mount it), or a OTG (on the go) device via usb directly to media like a flash drive. It cannot issue a backup over USB to a computer.
4. Completely agree it's a NTFS issue, but it could be mostly avoided by allowing files that error to be skipped or renamed rather than terminating the process. (I understand that's on the android devs since pull is made by them, and I doubt they would care to improve the command for a file system I doubt they use). Again I mostly included that so if anyone else is trying to figure it out they can stop looking for "a way" and just accept it can't be done.
Ultimately Khaon is right in that sideloading a rom would have unbricked it and I could have done the ADB backup then, I just wasn't sure how that might affect the app data storage so I was looking for a way to back it up before doing that.
Click to expand...
Click to collapse
I'd just 'tar' what I wanted on the device and then pull that with adb.
Yeah, I just had no idea what I wanted. I'm not 100% familiar with how the system stores application data, I figured if I copy everything than anything I "miss" after I formated it I'll be able to just research where it was and dig in the backup and pull it out.
Yeah adb sideload a rom will only affect system partition thus your data would not have been modified in any way. So you are done with your issue?
Sent from my Xiaomi MI2s
Khaon said:
Yeah adb sideload a rom will only affect system partition thus your data would not have been modified in any way. So you are done with your issue?
Sent from my Xiaomi MI2s
Click to expand...
Click to collapse
Yes, sorry for the slow reply. I've completed my update, just wanted to follow up on everything I did incase the information is useful for anyone else new to this like I am.