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
Good evening everyone.
To start with, yes I've read all the similar topics and none of them helped me
To my problem now. My phone has been flashed with a custom ROM for 1-2 months now (I don't remember exactly) and this morning I woke up to find my phone turned off. While trying to turn it on, no matter how much time has passed, it's stuck on the splash screen refusing to load the home screen
Is there any suggestion that does not involve me losing all my data because I have no backup of them?
Waiting for any suggestions.
See if you can connect with usb, and adb can communicate with device.
If yes, you can save the /data/data folder(in which are all configurations) + /data/app folder(in which are all apps except these on sdcard if any).
You can also run adb logcat from command prompt and see if you can find what app causes the error and the bootloop, and if maybe you can uninstall/reinstall this app, or delete the folder of that app on /data/data folder, to hopefully solve the error.
Try to install a program like QtADB, droid explorer or Android manager to avoid use command line and simplify some of above operations as copy/delete folders or install/uninstall apps.
If you need more help, PM me to speak in greek(it' s better)
I've just installed QtADB and connected the phone while being inside ClockwordMod v4.0.0.5.
The truth is that from here I don't get almost any useful information (don't know why). One positive aspect is that I can copy data from/to the phone.
While stuck in the splash screen I can't connect through adb though.
You mean not at all? Usually when appears IDEOS screen you can connect via adb, after some time and when the error start maybe the device freezes and then adb probably disconects, but until then you can take some useful logcat info for the error.
You can also have some more functions with QtADB on recovery mode if you mount the partitions first.
Maybe and the app manager work then(I haven't tested though).
Managed to get logcat information while turning on the phone. I'm attaching the log file with the error lines.
Trying to read them right now to find a solution. Any help appreciated.
gkaran said:
Managed to get logcat information while turning on the phone. I'm attaching the log file with the error lines.
Trying to read them right now to find a solution. Any help appreciated.
Click to expand...
Click to collapse
By reading your log i think the problem is permissions. Try to fix permissions with recovery tool.
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.
[Q] ***URGENT Help*** ZTE Libra stuck on BootLoop because of insufficient Internal Memory
Hello there,
I have a very big problem and i need urgent help to Recover All data from an ZTE Libra android phone INTERNAL MEMORY who is stuck in Bootloop after ran out of Internal Memory.
I don't have made any backup of my Data.
I don't want to do Factory Reset yet.
I have tried wipe cache partition that don't work for me.
About phone: ZTE Libra bought on amazon, i think is android 2.2 STOCK ROM installed, NOT rooted, USB debugging NOT activated,I can enter Recovery Mode by pressing Power button + Volume Down + Home Button,I can enter FTM mode (Field Test Mode) - i think its called by pressing Power Button + Volume Up, I can connect it to PC - Windows 7 with USB cable in FTM mode and Wondershare Dr Fone Recovery program recognize it but i am stuck on 2nd Step where it ask me to activate USB Debugging and i am not able to do so, I can connect it to PC - Windows 7 with USB cable while is Turned ON and in Bootloop and My PC list it in My Computer but if i click on it is empty - If i click Properties it shows empty also, but it shows there,
PS. I also contacted ZTE Support directly by email and discussed with them about this, and ask them for a solution. i still wait for answer at the moment as they told me so.
After reading all possible forums since Monday i have found some information who make me think there is possible to find a solution, in the forms of some Exploits/Debugging software made by Developers,etc
I try to achieve the followings:
1. I want to fix the Bootloop or restore back the phone to its normal state so i can use it again.
2. I want to recover Phonebook Contacts from the Phone memory, Notepad Notes from the phone, Whatsapp Data from the Phone memory, Bookmarks if possible from Browser, etc
3. I want to know if i can install ClockworkMod recovery from the sd card and install an factory image or update without losing DATA.
4. I have found a script in this thread http://forum.xda-developers.com/showthread.php?t=2138661&nocache=1
Is possible to fix the boot loop by trying to free some space on the internal memory with this script ????
5. Is possible to install stock rom without wiping data or how to update stock rom without wiping my data ????
Here is some info i have found on some other thread
http://forum.xda-developers.com/galaxy-s5/help/soft-brick-bootloop-stock-recovery-t2806516
" Also search XDA for reactivation lock threads.. some people were claiming that they have found bugs /exploits that may aid you in recovering. You might also be able to dump the data partition from a JTAG interface - but that would be a highly technical, expert level procedure where a misstep could brick your phone.
And as a practical last resort, if nothing else works, try installing a firmware update instead of a full OEM image. That may replace enough system files to fix the boot process and might not delete your user files in the data partition. "
In the last resort i think i reset to factory and then use Wondershare Dr Fone to recover my Data but i have very important Notes and Phone numbers that i want to recover and i want to make sure i can save them.
What happened is:
Monday i was using Whatsapp and after several times getting an error that Whatsapp stop working,and Browser stop working - Internal memory ran Out of Space lt was less than 1 MB just few kb left , i was trying to delete some Voice messages from Whatsapp to create some space because the phone has only 100 MB of Internal Memory and in the last time always tell me it Runs out of Space.
I deleted the voice messages and then i turned OFF the phone in the idea that it will update the memory space and show how much i have left.
When i want to turn ON the phone it got stuck in the Bootloop.
First i did not know what is happening but then i searched on google and found out about this.
Please Help me. I need urgent help from Professionals and Developers, i am willing to pay also to recover my data. Any solutions, there has to exist a solution.
I am waiting for your answer, Thank you so much in advance.
2. i think contacts are saved on your gmail account.
5. when you update stock rom you don't lose anything
Help Anyone ?!
smushyyy said:
2. i think contacts are saved on your gmail account.
5. when you update stock rom you don't lose anything
Click to expand...
Click to collapse
How do you expect me to update stock rom if i don't have more space.
Contacts from Phone are not saved on gmail account
And how i can find an update for this stock rom?!
Anyone can help ? I am really need to find a solution ASAP
I am thinking to use that Fix bootloop script, put it on the sd card and delete Whatsapp APP to create free space and hopefully i can gain access again to the phone and then reinstall Whatsapp
Any advice? PLEASE!!!
Help anyone ????????????
PLEASE HELP
I am trying to recover my data and i need some advice whether to use this methods or no
1 method
I have found a BOOT LOOP zip fix script here http://forum.xda-developers.com/showthread.php?t=2138661 that can delete apps from the phone in order to fix the boot loop. i am thinking to use this to create some space on the phone since my phone is stuck in boot loop because of insufficient internal memory. I am thinking to delete whatsapp and hope to be able to gain access to the phone so i can save my phonebook,notes,etc and then reinstall whatsapp and recover my messages from whatsapp backup. I need to know if this script work with a phone that is not rooted. i already sent message to the person who posted the thread but still no answer. I need advice if this CAN work or no ??????????????????
2 method
I have found on internet information of how to install Clockworkmod recovery, so i downloaded this file " recovery-clockwork-6.0.1.2-blade " that i think work with ZTE Libra too. If i can install this maybe i can find a solution.
I need to know can i install this if my phone is not rooted ??????????????????
Can any of this work ?????????????
I NEED URGENT HELP !!!!!!!!!!!!!!!!!!!!!!!!!!!!
I think no one has expirience with this problem, you shuold post question somewhere elese, like android general etc.
Hi,i have root my phone.please,what next.
Sent from my Infinix-X551 using XDA Free mobile app
When I plugin my Samsung Galaxy J7 Prime and then select recovery module and it show as connected and then I select android data recovery option and then select recover documents only and then click next. Then it show and detected device model, downloading package and it went like that till 99% uncertain if it hit 100% or not and then it caused my device to reboot and after it reboot now it is asking for a password to start up device but I tried device screen password, google account password and samsung account password but all didnt work. Thus it shows have 7 attempts left before factory reset itself.
The boot up looks a bit different from normal too, unsure if it is coming through a different type of boot and if there is a way to reverse to how it was earlier?
In recovery mode it shows in recovery log pid 2064 ran. where first line filesystem table code was;
0/ efs ext4/ dev/block/platform/1354000.dwmmc0/by-name/EFS(/dev/block/mmcblk0p3) 0
and in following
#ls /cache/recovery
ksmg
-rw------root root 8190724 2022-04-02 11:19 last_ode_dumpstate_err_check_password.log
From what I could see further in log it seems like maybe dr fone tried to root phone since I see files seem to have been overwritten probably as same file name shown where earlier recorded in time stamp as either 2017 or 2008 and underneath that dst is run with today tim stamp.
What would be method to solve to get back to normal working state without any data loss?
It seems when check via dr fone transfer showing as mem capacity 2797mb and 1362mb used whereas it should show as 32Gb, also when start up it says Enter your password to start up your device but I am certain I enter correct passwords but it is not verifying. Also in recovery mode it shows No support single sku supported api:3.
And when try backup option no files come up on scan does that mean the Dr fone recovery package that it installed wiped out the data? Or is it like in another different boot system for recovery? How to solve this problem?
Also any backup software you think could backup stuff before applying any drastic fixes
I think your phone internal storage is corrupted because of Dr. Fone and this is caused by the data encryption inside the phone and I think that it requires the encryption password, and to solve this problem, you must flash a modified recovery like TWRP or CWM and then pull all the data by making a MOUNT of the internal storage it will only works on old Android version 6.x or 7.x but you can try
My android is 6.0.1 so I think it should work, do you have any video tutorials or a thread with stepwise instructions to get twrp or cwm to backup current data and later restore?
Also any idea if use the dr fone repair device feature it might fix?
Dr.Fone only one thing do transfer WhatsApp chat between android and iOS all else features not work perfect so try another way, ask google how mount internal storage on android phones by twrp it’s easy and not need a tutorial just flash a custom recovery and don’t let device to boot enter recovery mode immediately and go to mount and press mtp or mount storage
Looks like the device name has got renamed as well best try to see if have a file explorer or manager for android so can see if files still intact? Any pc softwares that can be used to clarify without need to unlock screen since it is asking for a pass saying Enter your password to start up your device but I am certain I enter correct passwords but it is not verifying.
If the files are intact then I can try twrp or odin cf root flashing to see if can flash home version file so files possibly stay intact. Or if they are anyways not then will try factory reset via recovery mode and then will need recommendation of good software to recover data for free
Any ideas?
That app is trashware. Do Not use!
If a factory reset doesn't clear it you'll need to reflash the stock rom.
The data is lost... that's my opinion.
Always backup all critical data redundantly to at least two hdds that are physically and electronically isolated from each other and the PC... or you will lose data, eventually!
NEVER encrypt a data backup drive.
Do copy/paste file transfer, verify file size and folder count match. Test for readability.
NEVER clone music data bases, copy/paste only.
Do not use compression or apps like SmartSwitch to backup critical data, they can fail you miserably.
You can never have too many backup data drive. Avoid using flash memory; quality hdds have better memory retainment. Store in more than one location. Near lightning strikes can wipe them; a metal earth grounded box or safe is best.
blackhawk said:
That app is trashware. Do Not use!
If a factory reset doesn't clear it you'll need to reflash the stock rom.
The data is lost... that's my opinion.
Always backup all critical data redundantly to at least two hdds that are physically and electronically isolated from each other and the PC... or you will lose data, eventually!
NEVER encrypt a data backup drive.
Do copy/paste file transfer, verify file size and folder count match. Test for readability.
NEVER clone music data bases, copy/paste only.
Do not use compression or apps like SmartSwitch to backup critical data, they can fail you miserably.
You can never have too many backup data drive. Avoid using flash memory; quality hdds have better memory retainment. Store in more than one location. Near lightning strikes can wipe them; a metal earth grounded box or safe is best.
Click to expand...
Click to collapse
Can you recommend a free pc software that could possibly backup device in current state? Or a free pc software that could do data recovery without need to root phone so if I do go ahead with flash and it wipes data or i do factory reset then I could try to get backup data.
NW_Work said:
Can you recommend a free pc software that could possibly backup device in current state? Or a free pc software that could do data recovery without need to root phone so if I do go ahead with flash and it wipes data or i do factory reset then I could try to get backup data.
Click to expand...
Click to collapse
Not on an unrooted phone. You can try this.
If you used Drfone it has likely already encrypted the data with their own encryption key.
Hopefully some of your data is backed up somewhere else because this is a dead horse... I believe.
I be more concerned about salvaging the phone at this point. It's a tough lesson from the U of hard knocks... don't repeat it. Sorry.