Hello,
My LGE Nexus 5 (16GB) recently got stuck during booting. I had to flash the factory image (6.0.1). I want to recover data.
In order to do so I downloaded a data recovery program: "Dr.fone for Android". This told me to root my phone. Which I did using https://autoroot.chainfire.eu/. I have SuperSU Free v2.74.
The data recovery program confirms my phone as rooted: http://imgur.com/a/C7gF7.
However when I attempt data recovery, it doesn't prompt me with a message (when it should): http://imgur.com/a/1rMRg. I can continue to start the data analysing process anyways, during which it will prompt me for SU access, but the data recovery always turn up empty.
I downloaded another data recovery program, EaseUS, to pinpoint the issue. EaseUS simply says my phone isn't rooted: http://imgur.com/a/nfXVh. Which is quite a contradiction.
So.. I looked for another way. I came accross this thread: https://forum.xda-developers.com/showthread.php?t=2450045. However my Nexus 5 DOES NOT HAVE AN SD CARD. I looked further and found: http://www.nburles.co.uk/android/recovering-data-from-an-android-device-using-dd. I installed cygwin+nc and on the phone Busybox v1.26.2-meefik (which contains nc for phone).
So I tried to follow the second guide again, but I kept running into the issue where no actual data was being sent. In my attempt to pinpoint the issue I found that the tcp connection between the phone is not being established properly: http://imgur.com/a/ooe1J.
- If I type anything from my laptop-shell it instatly shows up on the phone-shell. (expected behavior)
- If I type anything from my phone-shell it will instantly echo back. (as if it is connected to itself?)
- If I type anything from my phone-shell it won't show up on the laptop-shell. UNLESS I send 2 messages from the LAPTOP-shell, as if it needs encouragement (1yes I hear you, 2you may talk?).
Using this knowledge I was able to start dd'ing some data to my laptop, however I need to send 2 messages from the laptop shell for each 16Kb chunk of data. http://imgur.com/a/WvrIH. If I want to make a dump of my 12-16GB data I would need to send roughly 2 million messages. As close as I am, this is no solution.
I have searched the internet, but my the guides and tutorials don't venture this deep. Dear XDA, please help me with this issue.
Related
I have come to what seems to be the end of a very unique set of misfortunes. I was keeping my phone stock for as long as possible, to avoid running into these issues (I don't have any "backup" phones), but being sent on travel for work and staying in a hotel with no Internet forced my hand. I needed to be able to tether my phone.
I went about unlocking the bootloader and after booting into TWRP, I immediately made a backup. I then flashed the necessary zip file to acquire root access. After successfully rooting it, I was able to achieve wireless tethering via Wireless Tether for Root. However, I did not want to deal with the power drain and possible latency/bandwidth degradation of a wireless connection, so I began the process of flashing a custom ROM (MeanROM).
After laboriously acquiring the ROM zip via Panera Bread wifi and placing it in my external SD card, I booted into TWRP to attempt to flash it. While trying to flash a ROM, I ran into some problems and was able to successfully restore from the backup I had made. I attempted to flash MeanROM, however, and received a failure message. The zip program was unable to open the file.
After reading up a bit more, I decided to wipe cache, dalvik cache, and perform a factory reset and system wipe. These operations did not enable me to successfully flash my ROM. They did, however, result in corrupting my internal SD card partition, resulting in the loss of my backup. What I mean by this is that there are several messages about "failed to mount /sdcard (Invalid argument)" in the log. The next step was to try to reformat the internal SD card.
I discovered that the busybox install provided did not have the ability to do what I needed, so I went about pushing a newer version onto my phone using adb push. The exact command I ran (copied and pasted from my terminal) was this:
Code:
sudo ./adb-linux push busybox /sbin
This had the unfortunate result of assuming /sbin was the new name of the busybox file on my phone, thus overwriting my /sbin folder with a file. Now, when I try to run adb shell, I get the nasty message
Code:
- exec '/sbin/sh' failed: Permission denied (13) -
So! Does anyone want to undertake the task of trying to help me?
After another Factory Reset and reboot, I was able to get past that last error message and can now adb shell in again. Hopefully I'll just be able to re-download the (or another) ROM and get that flashed.
Aaaaaaaaaaand I just learned about this: Enable WiFi Hotspot and USB / Bluetooth Tethering on the EVO 4G LTE
Note to self, do more reading.
elead1 said:
After another Factory Reset and reboot, I was able to get past that last error message and can now adb shell in again. Hopefully I'll just be able to re-download the (or another) ROM and get that flashed.
Click to expand...
Click to collapse
That would be my suggestion. Make sure to check the md5 on the rom download, especially on questionable wifi networks.
Sent from my EVO LTE
Definitely a bad download. Also, you must be on twrp 2.2.1 to install the latest MeanRom. With the addition of GoogleNow to the rom it has grown to over 600mb and the older versions of twrp seem to fail more often than succeed during install. If you want to use usb tether, you probably should bite the bullet and buy PDAnet. It is by far the best and most reliable method of USB tether. You won't be able to get it in the market though, you will have to get it directly from their website: http://junefabrics.com/android/
I've been using PDAnet for 3 years now and you don't have to be rooted to use it. PDAnet's latest version offers wifi and bluetooth tether now, but unfortunately it doesn't work on HTC phones because it uses FoxFi for its wireless tether which doesn't work on HTC phones.
My device is Amazon Kindle Fire HDX GU045RW 64GB Black 8.9" Wifi 3rd Generation Tablet, and it has had a keeping restart issue since last week, the device is not rooted, and firmware version is 4.5.5.2. I think a factory reset might bring it back to work, but I forgot to back up my pictures and videos in the DCIM folder.
so far the device can start the fire OS for around 10 seconds and restarts again when it is powered by a PC, which recognizes it as a portable device and I can explore the internal storage for a very short time, but when it is powered by a charger, it rarely enter into the main menu, looks like the USB storage enumeration would pend the restart a little bit longer, I am not sure if such info is helpful to narrow the possible causes, just hope anyone who met similar issue would give me some hint about it. Thanks in advance for any comment!
I have managed to install the kindle adb driver on my laptop, and could run "adb devices" and serial number showed , is there any adb command I could use to diagnose my device? Thanks in advance for any suggestion
godhand_sh said:
My device is Amazon Kindle Fire HDX GU045RW 64GB Black 8.9" Wifi 3rd Generation Tablet, and it has had a keeping restart issue since last week, the device is not rooted, and firmware version is 4.5.5.2. I think a factory reset might bring it back to work, but I forgot to back up my pictures and videos in the DCIM folder.
so far the device can start the fire OS for around 10 seconds and restarts again when it is powered by a PC, which recognizes it as a portable device and I can explore the internal storage for a very short time, but when it is powered by a charger, it rarely enter into the main menu, looks like the USB storage enumeration would pend the restart a little bit longer, I am not sure if such info is helpful to narrow the possible causes, just hope anyone who met similar issue would give me some hint about it. Thanks in advance for any comment!
I have managed to install the kindle adb driver on my laptop, and could run "adb devices" and serial number showed , is there any adb command I could use to diagnose my device? Thanks in advance for any suggestion
Click to expand...
Click to collapse
Tough nut to crack. There is no adb magic that will assist in diagnosing/remedying the situation without root access. You can not utilize adb nor see the DCIM folder unless FireOS is running and USB debugging enabled; I believe the latter resets on every reboot. Given the stability window (10-15 sec) there is barely sufficient time to navigate to the option under settings before the device restarts. You could root and unlock but the limited FireOS run time presents an insurmountable obstacle as the procedure takes some time.
I don't think a factory reset will resolve the issue but is likely the only recourse. Sorry to share the bad news ...
Davey126 said:
Tough nut to crack. There is no adb magic that will assist in diagnosing/remedying the situation without root access. You can not utilize adb nor see the DCIM folder unless FireOS is running and USB debugging enabled; I believe the latter resets on every reboot. Given the stability window (10-15 sec) there is barely sufficient time to navigate to the option under settings before the device restarts. You could root and unlock but the limited FireOS run time presents an insurmountable obstacle as the procedure takes some time.
I don't think a factory reset will resolve the issue but is likely the only recourse. Sorry to share the bad news ...
Click to expand...
Click to collapse
Thanks for the information! I have connected my device with adb shell command, and also measured the time from adb server on to device reset, it was around 30 seconds, is it enough to perform the root with adb assistance? I think 30 seconds is enough for moving the jpg files out one by one, but might be insufficient for the mp4 files because some of them are over 1GB.
I can make the device enter FireOS original recovery and it never restarts, so I am thinking maybe it is possible to replace it with some custom recovery like TWRP which supports mount function and adb connection as well, but per my research from the forum, the custom recovery needs a unlocked bootloader, which needs the device to be rooted at first.
BTW, I found the jpg and mp4 files in /sdcard/DCIM/Camera, would it be affected by the factory reset? Or just data and cache would be affected? I know TWRP can perform a factory reset without affecting the internal storage, but not sure what the original recovery would do. Please kindly refer to the attached snapshot for more details.
Thanks in advance for any help
godhand_sh said:
Thanks for the information! I have connected my device with adb shell command, and also measured the time from adb server on to device reset, it was around 30 seconds, is it enough to perform the root with adb assistance? I think 30 seconds is enough for moving the jpg files out one by one, but might be insufficient for the mp4 files because some of them are over 1GB.
I can make the device enter FireOS original recovery and it never restarts, so I am thinking maybe it is possible to replace it with some custom recovery like TWRP which supports mount function and adb connection as well, but per my research from the forum, the custom recovery needs a unlocked bootloader, which needs the device to be rooted at first.
BTW, I found the jpg and mp4 files in /sdcard/DCIM/Camera, would it be affected by the factory reset? Or just data and cache would be affected? I know TWRP can perform a factory reset without affecting the internal storage, but not sure what the original recovery would do. Please kindly refer to the attached snapshot for more details.
Thanks in advance for any help
Click to expand...
Click to collapse
Unfortunately, your research is accurate. Device must be rooted (and usually unlocked) to install a custom recovery. Rooting requires a functioning ROM and typically takes some time (more than 10-30 sec) to complete.
As I recall a stock factory reset is comprehensive including contents of the DCIM folder. So you'll want to move out whatever you can before going that route. I also think the chances are small a reset (basically a user app/data wipe) will resolve the looping problem as it does not touch the system partition.
As a test turn off your AP before powering up the HDX. Outside chance establishing a WiFi connection is somehow contributing to the boot loop. Graphing at straws - not much else you can do in the absence of root.
I would also reach out to Amazon given the value of the device ($400+ USD). While likely out of warranty they may provide some accommodation if you play your cards right and get a compassionate agent. Highly unlikely you'll get anything close to full value but perhaps something.
Davey126 said:
Unfortunately, your research is accurate. Device must be rooted (and usually unlocked) to install a custom recovery. Rooting requires a functioning ROM and typically takes some time (more than 10-30 sec) to complete.
As I recall a stock factory reset is comprehensive including contents of the DCIM folder. So you'll want to move out whatever you can before going that route. I also think the chances are small a reset (basically a user app/data wipe) will resolve the looping problem as it does not touch the system partition.
As a test turn off your AP before powering up the HDX. Outside chance establishing a WiFi connection is somehow contributing to the boot loop. Graphing at straws - not much else you can do in the absence of root.
I would also reach out to Amazon given the value of the device ($400+ USD). While likely out of warranty they may provide some accommodation if you play your cards right and get a compassionate agent. Highly unlikely you'll get anything close to full value but perhaps something.
Click to expand...
Click to collapse
Thanks for the suggestion! I have moved all the pictures and part of mp4 files out of that device by adb pull command, and I found the time from adb connection built to device restarting allows around 300MB data transfer, so the mp4 files more than 300MB are still left in the device. I am thinking if it is possible to copy busybox into my device, and use split command to divide large files into files less than 300MB. Is it ok to use the one from https://busybox.net/downloads/binaries/1.21.1/ directly? Thanks in advance for any comment
godhand_sh said:
Thanks for the suggestion! I have moved all the pictures and part of mp4 files out of that device by adb pull command, and I found the time from adb connection built to device restarting allows around 300MB data transfer, so the mp4 files more than 300MB are still left in the device. I am thinking if it is possible to copy busybox into my device, and use split command to divide large files into files less than 300MB. Is it ok to use the one from https://busybox.net/downloads/binaries/1.21.1/ directly? Thanks in advance for any comment
Click to expand...
Click to collapse
Shouldn't be a problem download from that source. Splitting large files is a good idea.
Regardless of what eventually happens with your device I suspect there will be a take away regarding performing regular backups against personal files. Even something simple like drag/drop of important files/folders on occasion.
Davey126 said:
Shouldn't be a problem download from that source. Splitting large files is a good idea.
Regardless of what eventually happens with your device I suspect there will be a take away regarding performing regular backups against personal files. Even something simple like drag/drop of important files/folders on occasion.
Click to expand...
Click to collapse
Yeah! I did it! Thanks for the powerful busybox, which can continue to split large files even when it is interrupted by device restarting. With this feature I could pull any file out of a keeping restart device given there is enough disk space for storing the split files. The following shares my process & scripts used in the backup. Hope that helps others might meet the similar case.
1. move busybox in the device
adb push busybox /data/local/tmp/
adb shell chmod 755 /data/local/tmp/busybox
2. split the large file
adb shell /data/local/tmp/busybox split -b 300m /sdcard/DCIM/Camera/%%i /sdcard/tmp/split /*used in a DOS bat file*/
3.pull the files out
for /f %%i in (%1) do if not exist .\kindle\tmp\%%i adb pull /sdcard/tmp/%%i .\kindle\tmp\ /*used in a DOS bat file*/
4.combine the split files into what it should be.
cat splita* > a.mp4
Hi everyone, forgive me for my bad english...in this day i'm freaking out because it happend an unexpected thing. 4 days ago in the evening i looked that was an error message about whatsapp in the home screen, then i open the app and appeared that chat list got problem and to solve that i need to restore backup or i get lost chat. The device was connected to wifi house, but i had whatsapp backup on my phone. I searched on internet and on official whatsapp page i red it was possible as an error. To solve that need to restore last backup. I done it but while the loading has started, after a few minutes the devices shut down and reboot. It's arrived to the logo of the ROM and then shut down again and reboot. i undestand it was a bootloop. Two years ago i install android kitkat because the device can't received android 4.4 and i don't want stay with 4.3. Everything fine. After an year the device goes in the bootloop, but i don't know why, so i decided to format data ad restore kitkat again. Before that i can transfered some data because i saw that if device was connected on the pc it not gone in bootloop. This year another problem but more little. The device sometimes reboots so i do a backup with titanium backup and then wipe everything including internal storage because on the boot after flashing the ROM the device can't memorized anything. In that occasion i don't reboot the device because i wiped internal storage so everything. Connected usb-device to the phone, copy gapps, rom, twrp and super su. Reboot and the smartphone was reborn. Whit titanium backup i restored all data. This time the thing is very very different and more difficult. In my opinion probably i could download a virus with whatsapp, usually it is connected to a link into a message sended by a contact in whatsapp, or happened something during the restore of backup of whatsapp. The device goes constantly in bootloop but i can entry in recovery mode. i noted that can't see the gapps, rom e supersu file in the sdcard like the other times. They are only in the data\media\0 folder. Everythime i try to copy something not in the sdcard, it goes on an error about a netstat file i found in the data\system\netstats folder. It's a file short, different by the others. I red that netstat files can be deleted but this file can't be deleted by using twrp>advanced mode>file manager>name of the file>delete. Before try to do another format data or again a total format of internal storage like the other time, i need to know if this procedure can resolve the problem. This time i was not prepared so the last backup is about six months ago. In this months i inserted new contacts and this time i don't sincronized my contact list with my google account like the other times because i couldn't image to be in this situation. I try to delete the file using adb but my phone is not recognized so the serial number doesn't appear. List of deviced attached is empty. In this case i can't activate the developer funcstions by tipping in the device information into the phone because it goes in bootloop. On the pc i have usb-drivers, but now into the phone there's android 4.4 not 4.3 like the first time i do the procedure to unlock the device. So with adb don't see serial number but the pc just see the device like google nexus adb interface. Copying file as contact or dialer or data about apps because are all in the data folder, appears an always an error about netstat and the red failed written. just copy from sdcard folder to usb external device this not happen, what can i do?
I done a nandroid backup because i know that with titanium backup i can restore data i want to restore, but also in this case could appear the same message error about netstat file? All data are been copied on the external usb deviced and then on the pc, but i don't know if the problem will be present again. so if i try to restore data with titanium backup and the problem reappers i don't know what to do.
Here we are some information about my phone. I hope someone in this fantasctic and big community about android developers can help me to solve this very big problem. if i thinking about i've done i feel so stupid because probably i could avoid this problem.
i forget to say also i tried to fix permission, wipe davilk cache and cache, copy log to sd (to see if there's another error but i don't know how to do). After all of this passages, everytime appears the same error.
Fastboot Mode:
Product name: tuna
Variant: maguro 16gb
hw version: 9
Bootloader version: primemd04
basedband version: i9250xxlji
carrier info: none
serial numeber: xxxxxxxxxxxx
signing: production
lock state: unlocked
Rom: omnirom maguro nightly 4.4.2, kernel stock of omnirom. gapps stock 4.4.2
Error: E: unable to stat ' /data/system/netstats/dev.1480018034937_' appears then "updating partition details..."
after error: ....done Full SELinux support is present. Mtp enabled
Update
pc see the device in fastboot mode launching cmd fastboot devices. Get out the serial number. It doesn't work launching cmd adb devices. List of device is empty. On the pc i have two file about usb drivers downloaded by samsung support site. If i change the usb driver folder in sdk with the new samsung usb driver i just download, may i permit to see the phone with adb? or should i try to unistall device recognized as google galaxy nexus adb interface and repeat the installation of google usb drivers with an unknown device?
update
i'm losting hope. I tried also nexus root toolkit (NRT) by wugfresh. Before the programme i can't see the phone with adb, after unistall and reinstall the driver i can se the device. But here the bad news... i can't copy from the pc into the sd folder using windows and i don't know why because pc see the device, i can see the folder inside sdcard internal storage but can't copy from the pc to the phone. Fastboot and adb mode work. I've done a flash stock + unroot using NRT. Everything fine but then phone goes in bootloop and not with the stock logo so Nexus, with the Rom logo intalled instead. The NRT message says that the bootloop could appen so wait. After 20 minutes power off the device. So i try to do format data from TWRP; procedure works with blu written succesfull but there's the same problem E (encrypted or error?) unable to stat data/system/netstat file and the number of the file. So i try to wipe the internal storage. Succesfull but again red written E: same up. Everything i try to do nothing change. Internal storage stuck always the same MB, TWRP 2.8.7 always present, i can't flash 3.0.2. Can't also remove enctrypted data with NRT because is uncheck. Have i throw away the phone? The E unable to stat data/system/netstat with the number of the file goes out everytime because during the process for example about format data check out updating data partition and then E: blablabla also with succesfull written, not failed.
Before I start, I'm aware there are great data recovery guides on this forum and elsewhere. Unfortunately, I was unable to find one pertaining to Nougat and my specific circumstances. Thank you for bearing with me.
How the Data Was Wiped
I ran "fastboot format userdata" to fix a "Decryption Unsuccessful" error message after going from LineageOS 14.1 to 15 on a Xiaomi Mi 5 Pro. Because I was in a hurry to get my phone back online, I foolishly assumed the wipe would leave /data/media intact, just like TWRP, without making sure of it. I know the assumption was wishful thinking at best and I can see the irony in then spending the rest of the day trying to undo the damage.
How the Data Was Dumped
Immediately after finishing the fastboot format, I booted back into TWRP 3.1.1-0 where I discovered the extent of the data loss. Since I hadn't flashed a ROM and didn't want to write anything else to my /data partition, I did a "adb pull /dev/block/sda14 sda14.img" on my computer over USB with my phone still in recovery. With a 128GB phone, the process took a whopping 8102.059s to finish.
How I attempted to Recover Data
I let both R-Studio 8.3 and UFS File Explorer Professional Recovery 5.23.4 scan through my dump to no avail. All they found were meaningless, small files, mostly in a .txt or .so format. I also attempted to mount the image using DiskInternals Linux Reader 2.6, but PhotoRec didn't recognise the volume.
Where do I go From Here?
Christian Weiske wrote about his attempt at recovering photos from a Galaxy S5 mini, running Marshmallow. He noted that data he pulled in Windows was broken using various commands until he tried "adb exec-out". Does the problem lie in my pulled data also being broken/incomplete, or is "fastboot format" actually capable of completely destroying more than 100GB worth of data in mere seconds on TRIM-enabled devices? If I am to do a second /data dump using a different method, I would have to do it directly to my computer as my phone doesn't have a microSD slot. I should add that, to the best of my memory, I never encrypted the storage, as I went directly from CyanogenMod to LineageOS using the experimental migration build.
To anyone who chimes in, if only to tell me that I should suck it up and stick to whatever data I have backed up and move on, I'll be most appreciative! Even more so if anyone can shed some light on modern-day Android data recovery/wiping and limitations.
I'm going thru a recovery process myself. Using a few guides. First I completed a raw dump of the whole phone w/out installing any os over the phone. I'm about to check that and see if testdisk can find something via https://roubert.name/joakim/androidfilerecovery/
In the background, I have another dump going on from https://forum.xda-developers.com/ga...de-internal-memory-data-recovery-yes-t1994705 guide. Hopefully, something comes up.
Hi, few day ago I made a videos with a modded version of Google Camera 8.1,
the first one was not saved properly and was in .pending????????.mp4 state, and I erased it by mistake,
because it was first time, I was using this tool, and I didn't knew that it is a temporary file.
I tried to recover, using many tools, but I was unable to recover it, so I decided to Root my phone using Magisk,
I made some mistake and testing some FastBoot command I relocked my Unlocked phone.
I had to Unlock again by using "miflash_unlock.exe", with advertising that all my data’s will be deleted.
After I managed to patch my phone, he restarted (I don’t installed any previous apps prom store, to avoid my video to wiped by new data,
and I tried with Ult Data, Dr Phone to recover the file, but Root access was not accepted.
Then I tested lot of android tool, nothing worked, after searching a lot I found this page :
https://drfone.wondershare.com/android-recovery/phone-memory-data-recovery.html
And I tried but some command didn’t work, since I didn't have FDISK, FTPPUT on my phone file system,
after some other search I found this ancient page (2014) who seemed to be the source,
https://sudonull.com/post/108208-Recovering-data-from-internal-memory-on-Android-for-dummies
and after installing BusyBox Pro,
I managed to get missing Linux tools.
I tried the command, all worked fine,
but now I’m unable to access this one :
Code:
ftpput -v -u sally -p able -P 40 192.168.1.4 sde55.raw /cache/myfifo
because my FileZilla does not get any information.
And I receive this message :
Code:
can't connect to remote host (192.168.1.4): Connection timed out
The article is old and that guy was using U.S.B. MoDem on CyanogenMod 11.
I use Magisk pro rooting and I do not know what tool I should use to get U.S.B. link with FileZilla Server to get proper connection.
I tried many things, changing protocols, P.T.P., M.T.P., and I do not know what to do,
so I thought may be here, someone with experience could point me to a tool to use in Android 12 / 11 with my Magisk and link to FileZilla Server,
to get image of internal memory back‑up‑ed ?
Thank you in advance.
No one knows how to ?
Someone knows an other methodic to extract partition totally & perfectly ?
forum.xda-developers.com/t/guide_making_dump-files_out_of_android_device_partitions/