I have a Samsung S3 Intl. (i9300) which does not boot anymore. When I entered the recovery mode I got a lot of error messages (unable to mount ...). But as the phone has still the stock recovery I cannot connect with ADB. So I started it in download mode to boot/flash a custom recovery mode. While fastboot never detected the phone Odin and Heimdall did. But when I tried to flash the recovery mode with Odin or Heimdall I got error messages that the PIT is broken.
What do I want?
Primary Objective: Recover the Data
Secundary Objective: Repair the Phone
So is there any way to dump the internal memory of the phone while having it connected to a PC in download mode?
If I would have a large file with a broken partition table and broken filesystems I would know my way around.
DiskDumper said:
I have a Samsung S3 Intl. (i9300) which does not boot anymore. When I entered the recovery mode I got a lot of error messages (unable to mount ...). But as the phone has still the stock recovery I cannot connect with ADB. So I started it in download mode to boot/flash a custom recovery mode. While fastboot never detected the phone Odin and Heimdall did. But when I tried to flash the recovery mode with Odin or Heimdall I got error messages that the PIT is broken.
What do I want?
Primary Objective: Recover the Data
Secundary Objective: Repair the Phone
So is there any way to dump the internal memory of the phone while having it connected to a PC in download mode?
If I would have a large file with a broken partition table and broken filesystems I would know my way around.
Click to expand...
Click to collapse
Recovering the data is a lost cause at this point.
It sounds like the partition setup is screwed. You would have to find a way to repatriation everything back the way it was.
If the device is encrypted that will also cause it not to be able to read the partitions (or so I have read as I don't use encryption)
zelendel said:
It sounds like the partition setup is screwed. You would have to find a way to repatriation everything back the way it was.
If the device is encrypted that will also cause it not to be able to read the partitions (or so I have read as I don't use encryption)
Click to expand...
Click to collapse
Well yeah, but as it had a stock rom and was probably not encrypted (Android 4.3) it might be possible the recover some files (I have done things like that in the past). Maybe the /data filesystem is okay and the partition table is just broken.
But without having the data at all I can't even try to recover the files.
Hello there. I have an Elephone P9000 Lite, which required a re-flash. Fair enough. After I formatted everything then flashed the stock ROM... I tried booting it up, but the boot animation won't show up, instead, it's all just a black screen. It went on like that for 10 minutes, before I decided to stop trying. It got bricked. Now, I decided to try and flash CM13 (I found a ROM on this forum), but I can't flash it using SP Flash Tool (what I used to flash stock) because it's an .img file, so it doesn't have a scatter. I came to the conclusion that I can use:
a) Recovery, which I can't access due to the device being bricked
or
b) ADB, which requires USB debugging to be enabled, but I can't enable it due to my device being bricked.
Can anyone help me?
(I have quite some experience with flashing and stuff, but I have no idea how to flash .img using a PC without having to access the phone's OS)
Hi, offering $10 PayPal to anyone that helps me fix my phone. (Don't know if this is against the rules, if so, I take it back).
Here's the situation:
Was on stock MIUI Global 9.5.8.0 with RedWolf Recovery.
Did a backup and flashed LineageOS
Wasnt happy with it and flashed back the backup, including the Firmware and EFS partitions, basically every partition
Bootloop, WiFi and BT driver prolly messed up, cant connect and restarts upon trying to connect to WIFI/BT.
Tried flashing other firmware, various combinations of wipes, flashes, MiFlashTool fastboot rom, nothing helped.
Tried flashing with EDL, the newest ROM gives me "Too many lines in XML file", old ROM flashed fine, but then couldn't even get to fastboot.
Now: Can't get to fastboot nor recovery, phone goes to EDL mode w/ red LED blinking when connected to PC.
QFIL gives me "Cannot read packet header, read 0 bytes", same with MiFlash.
What are my options guys? Is this a dead case? Any help is greatly appreciated.
Hi.
I need some advice regarding bootloops on my Sharp Aquos S2. Device is unlocked and TWRP installed.
note: I have backup all of partition including modem1st etc.
Everytime i reflash ROM, it always bootloop. Bootloop will dissapear if i "fastboot erase persist" on download mode. Of course, side effect by deleting /persist, there will be no sensors working. Camera, wifi, fingerprint are not working.
What i did to fix:
1. dd if=sdcard/persist.img of=/dev/block/bootdevice/by-name/persist - still bootloop.
2. make_ext4fs and e2fcsk - still bootloop.
3. 9008 mode and emmcdl with firehose persist.img - still bootloop.
4. fastboot flash persist persist.img - still bootloop
5. using OST tools with nb0 image file - still bootloop
6. manual copy paste of extracted persist.img file via adb and root -
still bootloop
7. flash persist.img via twrp - still bootloop
8. Change sparse image to RAW command failed as persist.img already RAW.
9. Evertime i erased /persist with fastboot, device is booting but still with no sensors working.
Is there any way to fix /persist that probably i missed? As i discussed with @heineken78 it's probably hardware problem, but who knows it's just a partition or something that is not hardware related. Just wanna try my luck.
Any help would be greatly appreciated.
Thanks.
Hello
I tried to flash a custom rom on my Nord N10 --> [ROM][UNOFFICIAL] LineageOS 18.1 [OnePlus Nord N10/billie] <--
At 47%, the flash stopped. I tried it a several times but always with the same result.
I did a factory reset in twrp, since then all was gone from internal storage.
And now I'm unable to flash ANY rom on the device.
I tried a lot of ways: flashing stock rom with stock recovery, flashing different custom roms in twrp and other recoveries, Msmtool, extracting payload.bin and flash all the images in fastboot (I followed the commands at the bottom of this page), ... but I haven't got the result I wanted.
I even got into "Qualcom crash dump mode". That's when I tried to use the MsmDownloadTool but it wouldn't recognize any COM port.
I can transfer .zip files to the internal storage when using twrp, but flashing always fails (see attached file).
Sideloading in PE or Lineage recovery works, but flashing fails (2nd attached file).
Overview:
Positives:
bootloader is unlocked
fastboot is accessible
fastboot commands are working so I'm able to flash by fastboot command
recovery is accessible and different versions can be flashed
internal storage is accessible and copying files is possible (though, folders like Android, DCIM, downloads, etc... are all gone)
Negatives
Msmtool doesn't recognize the COM ports
some images (like vendor.img) can't be flashed in fastboot when extracted from the rom by using Payload Dumper
error shown in twrp (file attached)
neither can a rom be flashed in PE recovery or Lineage recovery
Anyone able and wanting to help or provide a link to a tutorial? I don't care which rom is installed, I just want to get the phone working again and at this point I fail to see what I'm doing wrong.
Kind regards
Its been a while since I used the N10, but I can at least help with the MSM tool: note that the MSM tool uses what is called EDL mode, which is basically a hardware (ROM) backed loader. If the phone isn't physically damaged, EDL should work no matter what you did to the partitions. It is lower level than the bootloader lock, so that shouldn't matter.
(Disclaimer: each EDL mode phone uses a signed loader, which can restrict what memory is read or written to... so technically, you could brick the phone and not be able to get it back if the loader won't let you write to a particular block. That said, I've never seen OnePlus phones unrecoverable, and if you can get the bootloader and fastboot back, you can then write to anything from FB that the partition table lets you, although that is subject to unlocking the bootloader at that point. It's why I'm probably OnePlus for life unless they do something stupid.)
Anyway, you have to get the phone in EDL mode. Off the top of my head, power it off, hold both volume keys down, then insert the USB cable. You will have a ** SHORT ** time period- like 5 sec - where the USB port will be identified as a Qualcomm 9008 (or whatever) and the MSM tool will see it. Have the tool running, and put your mouse over the "start" button, so you hit it in the window.
To be clear, EDL mode is NOT the same as crashdump mode, and any other mode than EDL will NOT be recognized by the MSM tool as valid.
Hope that helps!
I'll look into it and give it a try. Thanks!
SomeRandomGuy said:
Its been a while since I used the N10, but I can at least help with the MSM tool: note that the MSM tool uses what is called EDL mode, which is basically a hardware (ROM) backed loader. If the phone isn't physically damaged, EDL should work no matter what you did to the partitions. It is lower level than the bootloader lock, so that shouldn't matter.
(Disclaimer: each EDL mode phone uses a signed loader, which can restrict what memory is read or written to... so technically, you could brick the phone and not be able to get it back if the loader won't let you write to a particular block. That said, I've never seen OnePlus phones unrecoverable, and if you can get the bootloader and fastboot back, you can then write to anything from FB that the partition table lets you, although that is subject to unlocking the bootloader at that point. It's why I'm probably OnePlus for life unless they do something stupid.)
Anyway, you have to get the phone in EDL mode. Off the top of my head, power it off, hold both volume keys down, then insert the USB cable. You will have a ** SHORT ** time period- like 5 sec - where the USB port will be identified as a Qualcomm 9008 (or whatever) and the MSM tool will see it. Have the tool running, and put your mouse over the "start" button, so you hit it in the window.
To be clear, EDL mode is NOT the same as crashdump mode, and any other mode than EDL will NOT be recognized by the MSM tool as valid.
Hope that helps!
Click to expand...
Click to collapse
Couldn't get into EDL mode (I tried EVERYTHING). I updated/repaired the Qualcomm drivers, re-flashed another version of twrp and was able to flash this rom in twrp after I copied the rom to the sd card. It worked, the N10 is back alive again.