Trying to salvage the user data from a friend's Oneplus 8 Pro, that had a nice and salty sea bath. Took the phone apart, and managed to clean it up enough to be able to boot EDL and Fastboot modes. There's no hope for the screen, the connections/PCB are too badly corroded to fix up.
The obvious method is to get another OP8 Pro and swap the mobos, but the cost is of course quite prohibitive. Since you'd have to break the water/dust seals, reselling the donor phone at the same price afterwards isn't an option, there's still some traces of honesty left in me. Finding and buying a bricked phone to use as a donor seems to be easier said than done.
The phone is completely stock with locked bootloader. USB debugging isn't enabled.
Managed to dump the encrypted storage in EDL mode. As expected, the dumps seems to be more or less impossible to decrypt off the phone. Guess protection from that is the main reason why the storage is encrypted
TWRP is available for OP8 Pro.
A possible approach here would be to unlock the bootloader, boot TWRP on the phone, and try to transfer the userdata off the phone with ADB. The problem is of course that the bootloader unlock will factory reset the phone, and erase the user data.
Would it perhaps work to unlock the bootloader, restore the EDL userdata partition dump after the factory reset, boot TWRP, and access the userdata? Or will the factory reset also affect the encryption chain somehow?
I do of course have the current screen lock PIN.
Related
Like others, the OTA Nought update hard bricked my phone while continuing to freeze recovery menu. I have used Odin to flash the original rom but it remains in a bricked state (recovery menu freezes after 1/2 second rendering the buttons inoperable and freezes in the Verizon logo during boot). I have my Bitcoin block chain and important documents on this device that had just transferred an hour before the forced OTA rebooted the phone and am hopeful I can recover them. I don't care if I destroy the phone in the process but I would really like to recover my blockchain.
Can anyone confirm or deny whether the internal UserData, which now appears to use the new faulty UFS 2.0 over the older but reliable emmc is encrypted or if it can be manipulated through jtag or an emmc reader? I have the Allsocket reader for emmc chips but UFS is foreign to me.
If there is another possibility using an on-Chip method, I would also like to hear about it. Note that the Verizon version has a locked bootloader so I cannot install a custom recovery.
Hi all,
I have a Galaxy S7 Edge SM-G935V and the other day I put my case on and put the phone in my pocket not realizing I had put the case on upside down. With the case on the wrong way, the power and volume buttons were pressed and the phone rebooted several times. I thought I was just getting notifications when my phone was vibrating in my pocket, but in reality it was vibrating because it was rebooting. It must have booted to recovery and/or download mode and then because the buttons were still pressed, rebooted again and again. When I checked my phone after a few minutes of it unknowingly rebooting, it was in recovery mode so I attempted to boot normally. It didn't fully boot, but I got a message "Phone storage corrupt. The data partition has been corrupted. You need to reset your phone to factory default settings. This will erase all your data."
Now, I'm an IT professional so I know how storage disks work. I know that the partition table is probably corrupt but the data itself is probably intact. I would like to recover the data on the partition such as photos, videos, texts etc, but since the phone doesn't fully boot, I can't get to the storage from a PC, and when I connect via ADB I get the message "error:closed" when I try to do anything.
My questions/thoughts:
In the same way you would slave a damaged hard drive to recover the data, is there a way to access the partition without booting to it?
Is there a way to do a full ADB backup of the partition and try to extract the data from the backup?
Is it possible to install a custom recovery and do an image backup of the partition and try to extract the data from that?
What is the likelihood of recovering the data after a reset to factory settings? I have access to professional data recovery software and I'm willing to spend some money on specific software for Android recovery.
Is there any other way that anyone can think of to retrieve data from an Android device that can't boot? Or to repair the corrupt partition?
My stock Nexus 5 hardlocked today while attempting to connect to a wifi network. Upon restart, the boot-up animation took longer than usual, then displayed the 'Optimizing Apps' screen (which is not typical). It completed optimization on 5 apps, claimed to be starting Android, and then reset back to the boot-up animation, continuing the same cycle.
Unsuccessfully tried to boot into safe mode, although I can access Recovery Mode. Wiping system cache did not help. Installed ADB/Fastboot and sideloaded the original OTA without any improvement.
At this point, I'm hoping for either another path to get the device to boot or a way to extract some critical data (SMS, docs, etc.) off the device before doing a factory reset.
If the bootloader is unlocked, you could try flashing TWRP, booting into TWRP, and pulling off the data.
audit13 said:
If the bootloader is unlocked, you could try flashing TWRP, booting into TWRP, and pulling off the data.
Click to expand...
Click to collapse
Sadly no, fully stock phone.
Gave up and pulled the trigger on factory reset. We'll see if it helps.
On the plus side, this incident has motivated me to unlock and root my phone, hopefully expanding my options for the next time this happens.
Yup, an unlocked bootloader is definitely a plus in these situations.
I always unlock the bootloader unless it voids the warranty on the phone. Once the warranty is over, I unlock it if possible.
Factory reset seemed to work. Now unlocked and rooted!
I found the phone in my bag with a discharged battery and does not want to boot all the way. It shows the animated MIUI logo for about 1 minute and then restarts, sometimes showing the menu to switch to 'wipe data' and 'assistant'.
It's all stock, locked, up-to-date, I think still on Android 10 or which one it is. I did not install any new apps and don't even use the phone for anything other than gaming.
I've tried connecting with PC Suite but it doesn't see the phone. Fastboot anything does not work since the bootloader is locked. I know I can wipe data and be done with it, just wondering if there is anything else I can do.
EDIT: I've wiped the data and reinstalled the phone but would like to know if there is a way to avoid this in the future.
Unlock bootloader. This is very important. Then you have full control over the device.
For example the other day I had hard brick because fastboot flash was interrupted. And I still managed to unbrick the device thanks to unlocked bootloader and custom recovery.
It's really hard to hard brick this device. I love Xiaomi <3
Yesterday I accidentally drained my phone. I put it on charge, the next day I turned it on, but it went into boot loop. It tried to start maybe 5 times, and went into recovery. After selecting the language a strange message popped up: "kindly reminder
system error, after selecting language, please select Online update(keep data) to reover system, thanks!" (There is no such option in the recovery, only wipe, reboot and shutdown)
My 8T was with locked bootloader, last stable OTA update(13.0), no modifications.
I've had the phone discharge a couple of times before, and in all cases it was OK, just started up as normal.
But this is the first time I've had it drained on new update.
Is there any way to fix it without wiping data? I am currently in a country where there is no oneplus service center, and sending the phone to another country would be problematic for me.
I was able to dump the partitions in EDL mode, but I can't flash them. Can I use the MSM tool to simply update the phone without erasing the data?
Any help would be appreciated.
penguineer said:
Yesterday I accidentally drained my phone. I put it on charge, the next day I turned it on, but it went into boot loop. It tried to start maybe 5 times, and went into recovery. After selecting the language a strange message popped up: "kindly reminder
system error, after selecting language, please select Online update(keep data) to reover system, thanks!" (There is no such option in the recovery, only wipe, reboot and shutdown)
My 8T was with locked bootloader, last stable OTA update(13.0), no modifications.
I've had the phone discharge a couple of times before, and in all cases it was OK, just started up as normal.
But this is the first time I've had it drained on new update.
Is there any way to fix it without wiping data? I am currently in a country where there is no oneplus service center, and sending the phone to another country would be problematic for me.
I was able to dump the partitions in EDL mode, but I can't flash them. Can I use the MSM tool to simply update the phone without erasing the data?
Any help would be appreciated.
Click to expand...
Click to collapse
Try changing boot slot with
fastboot --set-active=other
TheNewHEROBRINE said:
Try changing boot slot with
fastboot --set-active=other
Click to expand...
Click to collapse
Hi! Unfortunately I have already tried this, switching slots is impossible with the bootloader locked...
After long-long research i think there is no way to fix that properly.
Now, i dumping whole phone (painful process, freed 260GB of space on my PC...) and after unlocking will try flashing userdata back.
penguineer said:
After long-long research i think there is no way to fix that properly.
Now, i dumping whole phone (painful process, freed 260GB of space on my PC...) and after unlocking will try flashing userdata back.
Click to expand...
Click to collapse
I don't think it will work. Userdata is encrypted and the key changes everytime you factory reset (although I don't exactly know what counts as a factory reset).
TheNewHEROBRINE said:
I don't think it will work. Userdata is encrypted and the key changes everytime you factory reset (although I don't exactly know what counts as a factory reset).
Click to expand...
Click to collapse
Yea, i heard about that, but i have no choice.