Hi guys, I realize this is an OLD device, and that this section probably isn't as frequently visited as others. I've got an SM-G550T1 that I've been trying to extract data from, but there's a dm-verity verification failure and it will not fully boot. Safe mode doesn't appear to work either.
So far, I've tried the Exynos Recovery method in Cellebrite UFED to no avail. All other methods within Cellebrite prompt for "tapping Allow" but obviously this can't be done due to the fact that it cannot boot into the OS. Or should I just ignore these messages and let Cellebrite do its thing? I've never had a device with this issue before.
Recovery and attempting to recover the data after the fact seems worthless as it'll be encrypted anyway. Looking for any assistance in this matter!
Hey there! I totally understand that dealing with an old device can have its challenges. It sounds like you've already tried some methods like Exynos Recovery in Cellebrite UFED, but unfortunately, haven't had success due to the dm-verity verification failure and the inability to fully boot into the OS. It's frustrating when recovery and data extraction efforts seem to hit roadblocks.
I'm not exactly sure about the prompt messages you're seeing within Cellebrite, but it's possible that they won't affect the data extraction process. However, it's always better to be cautious and not ignore any potential warnings that could compromise the data. Have you considered reaching out to the manufacturer or a professional data recovery service for assistance https://www.nannostomus.com/ ? They might have more specialized knowledge or tools that could help you recover the data from the device. In any case, I hope you find a solution that works for you!
Related
I have a Verizon Samsung Galaxy S5, SM-G900V, running Android 4.4.4. I accidentally ran a factory restore, wiping out my files. I want to try to get the data off of it, since the files may not yet be overwritten, but I have no idea of how to go about this, especially using a method that does as few writes to the internal memory as possible (to increase the chance of success). I would very much rather not root, or at the very least not trip Knox or otherwise void my warranty. However, I might be willing to risk it if necessary. I have never rooted before, and it seems as though rooting utilities have a difficult time with this phone (at least in part thanks to Verizon).
I have not found any guide on how to do data recovery in this situation. I've tried at least one recovery program that was completely useless, though that might be due to lack of root. I am familiar with computers, and Linux, but Android is very foreign to me, and it seems like most data recovery attempts require me to mount the device on a computer as a disk drive. Although I've gotten it to connect for file browsing and transfers, I have not managed to get a connection where it acts like a mountable, normal disk. Naturally this rules out getting a memory image with this method, leaving me rather stranded.
Can anyone provide me with some assistance? I'm not expecting to fully restore the phone, but I've got some files (especially the memo and contacts) I'd rather not say goodbye to since my last backup.
Any assistance would be greatly appreciated. Thank you.
NoBricksPlease said:
I have a Verizon Samsung Galaxy S5, SM-G900V, running Android 4.4.4. I accidentally ran a factory restore, wiping out my files. I want to try to get the data off of it, since the files may not yet be overwritten, but I have no idea of how to go about this, especially using a method that does as few writes to the internal memory as possible (to increase the chance of success). I would very much rather not root, or at the very least not trip Knox or otherwise void my warranty. However, I might be willing to risk it if necessary. I have never rooted before, and it seems as though rooting utilities have a difficult time with this phone (at least in part thanks to Verizon).
I have not found any guide on how to do data recovery in this situation. I've tried at least one recovery program that was completely useless, though that might be due to lack of root. I am familiar with computers, and Linux, but Android is very foreign to me, and it seems like most data recovery attempts require me to mount the device on a computer as a disk drive. Although I've gotten it to connect for file browsing and transfers, I have not managed to get a connection where it acts like a mountable, normal disk. Naturally this rules out getting a memory image with this method, leaving me rather stranded.
Can anyone provide me with some assistance? I'm not expecting to fully restore the phone, but I've got some files (especially the memo and contacts) I'd rather not say goodbye to since my last backup.
Any assistance would be greatly appreciated. Thank you.
Click to expand...
Click to collapse
My experience has been that once a factory reset has been done, that's it. Your phone is back to the state it was when shipped from the manufacturer. Any personal info is gone. One caveat though. Unless you've backed up to a "cloud" (VZW provides this with Contacts natively) or saved to a micro disc, you are out of luck.
Wish I had better info for you.
Hi guys I have a problem, I am using miui7 developer ROM and my phone has been compromised twice, I have had my bank account hacked(long story but calls where diverted and bank log in details changed) and 4 days ago someone tried to log on to my banking app remotely 5 times and so it was locked down, bank has confirmed it was my phone and my WiFi provider that was used and I know it wasn't me, so I have tried to flash 2 ROMs using all the correct methods and it always results in the same, a boot loop, I am wondering if partitions have been messed with, or if there is something hidden on the file system causing this, what I would like to do is wipe everything, I don't mean just system data cache etc I have tried all that unsuccessfully, I mean fully wipe and reset all the partitions memory emc chip and totally start fresh, can anyone help please, I really need to sort it out I know my phone is compromised because of things that have happened. Any solutions please. Anyone experienced malware in miui7 ROMs? Your help is really appreciated.
Rich
Phone? BL locked/unlocked? Root?
krcovsky said:
Phone? BL locked/unlocked? Root?
Click to expand...
Click to collapse
Redmi note 4g single sim doir, bootloader not sure never unlocked so presume locked, rooted and unrooted tried both methods, flashed plenty of ROMs in the past without trouble.
Sorry but i cant really help since i do not own the device. It would probably be best to try to find a solution on miui forum, directly ask a member of a Dior device team. And don't know if you flashed through recovery or fastboot mode - try both mehtods, also developer/stable rom. I think flashing through fastboot also acts as a full factory reset. There must be a tutorial for unbricking or resolving bootloops. Also try some custom cm/aosp based roms to see if the phone will boot. And since miui is chinese, you can presume that there is some data leaking, but i don't think that it contains malware - it would be too much even for xiaomi (unless you "picked up" some shady script/trojan/whatever along the way).
As the title implies, I've failed in my attempt to root my S7 Edge. I can access the custom download tool as well as the TWRP tool that I installed via Odin. However, I have no SD card and my attempts to use ADB have been unsuccessful. Right now I am looking for an option to reset my device to factory settings. I don't care about my previous data, as this is a relatively new phone. However, I believe my warranty is voided, and that is why I am posting here.
What are my options at this point? If it helps, a micro SD is arriving via Amazon tomorrow afternoon. Ultimately, I'd like to be able to install a custom ROM or root my existing Nougat that I started with (my original intention).
As for how the process may have failed, the tutorial I watched didn't seem to make it clear that I had to enable USB debugging. I enabled OEM Unlock, but not USB Debugging. Any help would be greatly appreciated. :good:
EDIT: Smart Switch does not support the device for emergency recovery. I really think I messed up my phone
EDIT 2: After suddenly disconnecting during the download process of a fresh firmware via sammobile, I restarted the device to reach an error screen telling me to use Smart Switch Emergency recovery. However, my device was not supported. Following a guide online, I clicked on the More tab at the top right corner of the Smart Switch program and chose "Emergency software recovery and initialization". I entered the relevant information for my device and the recovery process began (fingers crossed). After it has completed, I am now once again booting my factory firmware. I'll leave this post here because I couldn't find a similar post on the first couple pages of the forum or with the search function.
Now, can anyone direct me to a proper beginners' guide to rooting the S7 Edge? I'm fresh off of iOS, which I've used and been jailbreaking for the past nine years. I thought it would only slightly more complex, but I see due to the many different versions of the same device, rooting can be quite tricky.
Edit 3: New question which I can't find the answer to anywhere... Do you need an SD card to root? I'm resetting my phone for the second time now. Got a boot loop after using ADB sideloader to install supersu.
Where did you get the stock firmware? I have the unlocked sm-g935u... made an unbelievable stupid mistake and my three day old s7 edge is partly functional (only bare essentials), but whatever I did before wasn't wiped when I did a factory wipe so my phone thinks it's rooted even though it most certainly is not. (And many features and apps won't work bc of it. )
I can't find anything useful about theNougat firmware. I'm really desperate. My company bought me this and i broke it within a week. :'(
Hello,
I am trying to work around/bypass the password lockscreen for a friend that accidentally set it (I think her kid did) and doesn't know what the actual password is. I've already tried ADM and Samsung's "Find My Mobile" service but neither were helpful.
So I'm pretty sure my only two options now are to backup the existing data to my PC (though I'm not sure how given that I don't have access to important functions like ADB, custom recovery, etc.) and then factory reset the phone, OR just deal with the KNOX/warranty flag being tripped and delete the necessary files from /data/system using a custom recovery. If there's another alternative I'm missing, I would love to hear it.
Excuse me for already jumping ahead, but assuming I go the latter route, what would be the easiest way to flash a custom recovery? I've already looked at various other posts on this phone's board regarding rooting and everything looked quite involved.
The phone says it's a G935PVPS4BQE1, if that helps.
Thanks in advance.
P. S. I currently come from a OnePlus One, though I previously had a Galaxy S3 and remember quite vividly how much of a huge pain it was to properly root the device and deal with KNOX. I imagine the rooting process is even more of a pain with more recent Samsung phones.
So I've been rooting me phone for a while and have managed to never f*** up, till now, and I sincerely hope you guys can help me.
After rooting my S7 a while back, I just recently noticed SuperUser telling me that I didn't have root anymore, so I decided to follow these instructions to re-root my phone:
https://forum.xda-developers.com/ve...-to-notes-root-install-xposed-unroot-t3411039
I successfully followed all the steps to get root, but when I opened Flashfire it told me I could install a new update while maintaining root, so since my android is at 6.0.1, I did that and it bricked my phone.
On boot it says "Startup Failed - Use the Verizon Software Repair Assistant . . . " and on top it also says "Custom binary blocked by SECURE BOOT." I have tried going into recovery mode and deleting the system cache, but that doesn't do it. So is there any way to get the phone to properly boot while not deleting my data? I was rooting my phone precisely so I could use Titanium Backup again, so I don't have any backups stored anywhere. I have heard that flashing a recovery image with Odin can work, but would that delete my files? Someone please lend me your expertise.
My phone is a Verizon S7.
Fixed
I am surprised that no one responded to me, but what's important is that, miraculously, I managed to un-brick the phone myself without losing any data! What I did was, as my last hope (since Odin wasn't able to flash the stock image, a la the traditional soft-brick fix), decide to follow the on-screen instructions my phone was giving me and to download and run something called the "Verizon Software Repair Assistant," which can be found in the top google results after searching for the quoted name (xda doesn't let me post the link).
After putting my phone into download mode, I plugged it in, ran the software and let it work overnight. Checking on it in the morning, I found my phone, not only completely functional and working, but updated to Android 7.0 (it was 6.0.1 previously before the failed Flashfire OTA update) and still holding all of my data intact.
So, the interesting thing that I learned is that flashing to stock via Odin to fix a soft-bricked phone should not be the default resolution for potentially most people, as the carrier's default (in my case, Verizon's) repair utility managed to completely fix my phone without any side effects or data loss.
Is there anyone who could chime in on why the Repair Utility did not wipe my phone's memory, even though it warned it would?
**Note**
Verizon links to the Windows version of the repair assistant on their site, but to get the Mac version (which I used), the only way you can get it is by changing the end of the url they mention within the thread from "Win" to "Mac."
Pleased you managed to fix it, and thanks for posting the method for others
As for replies, if you stick around XDA you'll see replies can take days sometimes, patience is the key here
*Detection* said:
Pleased you managed to fix it, and thanks for posting the method for others
As for replies, if you stick around XDA you'll see replies can take days sometimes, patience is the key here
Click to expand...
Click to collapse
I guess I am not acquainted with this forum enough then, thanks!
Most likely the cause of the fault would be updating via FlashFire and keeping root. When the update was flashed, it most likely flashed the stock kernel and patched it for root, which is not a compatible root for our devices. Flashing the root kernel with Odin probably would have made the phone boot normally.