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.
Related
Hi,
I've got a very odd problem:
My Nexus 5 is rooted, I flashed it many times before, the bootloader is unlocked. This morning, it crashed, and couldn't restart. No panic, I launch recovery mode and go for a wipe data / factory reset.
Two hours passed, and nothing happened, it's stuck at formatting /data.
Still no panic! Let's flash that bad boy. I used flashboot to erase all partitions, everything went fine, then flashed each one of them one by one, until system and userdata...
These two give me a "flash write failure". I think it's probably because these two are the largest, and my flash memory would be corrupted or not working at all.
My warranty is dead since one week (yay). What should I do? Maybe it's not a hardware problem and then I'm in luck? :3
EDIT: Locking back the bootloader is ineffective after rebooting the device. According to another post, this means that my eMMC chip is dead. But then why can I still write on boot, cache, bootloader and recovery?
The EMMC doesn't get "fried" per say - it's just that some sectors of it become damage beyond the capabilities of its firmware to bypass. When this happens , the firmware locks/errors out when try to write .
Edit : In your case it seems like the vital parts of it are still working - there might be a way to repartition around the damaged portions , but I'm afraid I have no idea how.
Good day.
I got a Nexus 5 D820 from my mom who dropped it in the river about a year ago at which time the phone was dead. It had indication of power but would not turn on. It was in a drawer powered off until yesterday.
I was able to power the phone on although it would not boot. The Google logo appeared and the android loading animation, but it would always reboot or freeze at different points. From the bootloader the phone seemed stable and I never had an issue pushing/flashing files. At this point I flashed a few different recovery images for the device, but only Philz would work, while TWRP and CWM would only freeze or bootloop.
From Philz I was able to flash a few different ROMS including the latest official one from google and also a few custom roms with/out gapps. None of these would boot and had the same freeze/bootloop at the google logo or android animation with no consistency.
I figured at this point possibly the sdcard had become corrupted/damaged by the water since I was able to flash pretty much anything I wanted. This is where things went downhill.
I followed a guide to use the partition editor from within an ADB shell. The guide assumed I was formatting an external SD card and suggested deleting all partitions. I did make a backup of the configuration of the partitions just in case but followed the instructions and removed everything. I was concerned what would happen once I rebooted the device at this point so I looked around a bit and it was suggested that flashing a google factory image would recreate the missing partitions so I didn't have to do it manually, so I rebooted thinking I could just flash the google package from the bootloader. This was the last time the phone ever showed any indication of working.
Now I have no indication of even power, no LED's, no bootloader.
Please let me know what you think... Thanks.
Before deleting the partitions, did you perform a full factory wipe before or after flashing different ROMs?
Does the phone appear as a device in Windows Device Manager when connected via USB?
If you deleted all of the partitions you deleted the bootloader partition.
Who's THE BEST resource for tablet repair?? GTP5113 w/faulty EMMC "End of Life" issue
Hey all. I'm trying to salvage my mother's Samsung Galaxy Tab 2 10.1 GT-P5113.
U.S. market Tab 2 GT-P5113 with original factory ROM started intermittently bootlooping. At times would successfully boot and operate briefly but then reboot on it's own. Executed wipe process a few times but completed without success. Odin flash completes successfully on most attempts. STILL just BOOTLOOPS! Looking for a reputable service center to resolve.
It's been suggested that the 16 GB Tab 2 have a known faulty EMMC (MAG2GA) issue. It can happen, that your EMMC get “read only”, so you can’t perform any write actions or format anymore.
From the EMMC data sheet:
5.1.7 End of Life Management:
The end of device lifetime is defined when there is no more available reserved block for bad block management in the device. When the device reaches to end of its life time, device shall change its state to permanent write protection state. In this case, write operation is not allowed any more but read operation are still allowed.
But, reliability of the operation can not be guaranteed after end of life.
On a faulty EMMC firmware it happens a lot faster.
What are the symptoms?
Uninstalled apps and deleted files are back after a reboot
Formating the storage doesn’t work (after reboot the old rom and apps are back)
You can flash whatever you like via Odin - it shows “passed” but after reboot nothing changed (e.g. still no StockRom or still the old Recovery you had previously installed)
… there might be some more, but only to mention some …
In most cases, the issue can be fixed by a EMMC firmware update, but you need someone who’s able to do it (possible via ISP, nothing you can do easily at home yourself). In some bad cases you need to find someone who can replace your EMMC.
Hey all. I'm trying to salvage my mother's Samsung Galaxy Tab 2 10.1 GT-P5113.
U.S. market Tab 2 GT-P5113 with original factory ROM started intermittently bootlooping. At times would successfully boot and operate briefly but then reboot on it's own. Executed wipe process a few times but completed without success. Odin flash completes successfully on most attempts. STILL just BOOTLOOPS! Looking for a reputable service center to replace the memory.
It's been suggested that the 16 GB Tab 2 have a known faulty EMMC (MAG2GA) issue. It can happen, that your EMMC get “read only”, so you can’t perform any write actions or format anymore.
From the EMMC data sheet:
5.1.7 End of Life Management:
The end of device lifetime is defined when there is no more available reserved block for bad block management in the device. When the device reaches to end of its life time, device shall change its state to permanent write protection state. In this case, write operation is not allowed any more but read operation are still allowed.
But, reliability of the operation can not be guaranteed after end of life.
On a faulty EMMC firmware it happens a lot faster.
What are the symptoms?
Uninstalled apps and deleted files are back after a reboot
Formating the storage doesn’t work (after reboot the old rom and apps are back)
You can flash whatever you like via Odin - it shows “passed” but after reboot nothing changed (e.g. still no StockRom or still the old Recovery you had previously installed)
… there might be some more, but only to mention some …
In most cases, the issue can be fixed by a EMMC firmware update, but you need someone who’s able to do it (possible via ISP, nothing you can do easily at home yourself). In some bad cases you need to find someone who can replace your EMMC.
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.