Hi,
My Phone restart itself several times and the sdsard0 partition is damage,
I didn'y backup my photos, are there any way to get back the photos?
My phone is stock, locked, non root, 4.4.4 KTU84P.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
IMEI is also losted But the photos is the most important in this stage
Google auto back up wasn't turned on?
Sent from my Nexus 5 using XDA Free mobile app
Only synced Contacts , Chrome and app data
Really nothing can do?
Looks like ya may have to format the card in windows and hope it restores. Im gonna add that your photos and more than likely gone. I have all my photos auto back up to google and Dropbox daily. If ya manage to fix it, I'd definitely look into a service to back your stuff up.
Sent from my Nexus 5 using XDA Free mobile app
OP, not sure if you'll be able to access your data after this, but can't hurt to try: check general section for a how-to fix a corrupted /data partition.
still not working
Method1:
~ # [6ne2fsck /dev/block/platform/msm_sdcc.1/by-name/userdata
e2fsck /dev/block/platform/msm_sdcc.1/by-name/userdata
e2fsck 1.42.9 (28-Dec-2013)
/dev/block/platform/msm_sdcc.1/by-name/userdata is in use.
e2fsck: Cannot continue, aborting.
--------------------------------------------------------------------------------------------------------------------------
Method2:
[GUIDE] to fix persist partition
Result :
This looks bad, worst case you need to flash a factory image in order to at least restore the IMEI.
If you´re brave enough, try to boot from eg. Gparted Live ( look it up on the web ) and try to restore the file system with this partition tool. Maybe your device can be identified again as a Nexus 5. But be warned, I would try this method as the last resort only since there is a risk involved of losing your partition table.
Only try this if fastboot and all other methods fail.
nat510 said:
still not working
Method1:
~ # [6ne2fsck /dev/block/platform/msm_sdcc.1/by-name/userdata
e2fsck /dev/block/platform/msm_sdcc.1/by-name/userdata
e2fsck 1.42.9 (28-Dec-2013)
/dev/block/platform/msm_sdcc.1/by-name/userdata is in use.
e2fsck: Cannot continue, aborting.
--------------------------------------------------------------------------------------------------------------------------
Method2:
[GUIDE] to fix persist partition
Result :
Click to expand...
Click to collapse
when trying to fix /data, was it mounted? if it was, you might need to unmount it first.
also, that last error when flashing factory images... not a good omen
flash a cwm recovey
connect phone to your pc
open cmd
type adb shell
type parted /dev/block/mmcblk0
type print
post the screenshot of the output
beekay201 said:
when trying to fix /data, was it mounted? if it was, you might need to unmount it first.
also, that last error when flashing factory images... not a good omen
Click to expand...
Click to collapse
Oops, I forgot...
But still not working
bitdomo said:
flash a cwm recovey
connect phone to your pc
open cmd
type adb shell
type parted /dev/block/mmcblk0
type print
post the screenshot of the output
Click to expand...
Click to collapse
and
nat510 said:
and
Click to expand...
Click to collapse
On the first picture you are not the root.
The prompt on the second picture looks like you have twrp and not cwm. twrp does not have parted included.
Also in your previous posts I saw you were using the wrong commands to flash lollipop 5.1.1.
You used fastboot flash update -w hammerhead.......zip which is wrong. That command wipes /data and /cache then tries to flash hammerhead.......zip to the "update" partition and it fails there. There is no update partition.
The correct command is fastboot -w update hammerhead....zip, but it would be better if your run the flash-all.bat as it will flash the bootloader and the modem too.
bitdomo said:
On the first picture you are not the root.
The prompt on the second picture looks like you have twrp and not cwm. twrp does not have parted included.
Also in your previous posts I saw you were using the wrong commands to flash lollipop 5.1.1.
You used fastboot flash update -w hammerhead.......zip which is wrong. That command wipes /data and /cache then tries to flash hammerhead.......zip to the "update" partition and it fails there. There is no update partition.
The correct command is fastboot -w update hammerhead....zip, but it would be better if your run the flash-all.bat as it will flash the bootloader and the modem too.
Click to expand...
Click to collapse
O......low level mistake.
The partition problem seems to be fixed:good:
Related
Hello, I'm sorry if my english was bad since its not my native language .
Recently I accidentally clear data of naver line applications and now I'm trying to recover the apps database since all my naver line contacts were gone, I already try using the method provided on this link: http://forum.xda-developers.com/gal...de-internal-memory-data-recovery-yes-t1994705 it gives me 0 bytes of raw data, all step by step including using cygwin 32bit still 0 bytes, so is there any other way to image the userdata partition? Or is there a way to recover applications database properly? My Moto G were XT1033 version with android 5.1 lollipop.
Every help were appreciated, Thank you .
This thread may help you: (read up to post #42)
[Being resolved!] MotoG Bootup Problem - Recovery Mode failed
lost101 said:
This thread may help you: (read up to post #42)
[Being resolved!] MotoG Bootup Problem - Recovery Mode failed
Click to expand...
Click to collapse
Hi! Thank you so much it works! But now how do i access the RAW file to recover? Im using Autopsy and FTK Imager.
prayogasp said:
Hi! Thank you so much it works! But now how do i access the RAW file to recover? Im using Autopsy and FTK Imager.
Click to expand...
Click to collapse
adb reboot recovery
adb pull /dev/block/platform/msm_sdcc.1/by-name/userdata userdata.img
This is done in TWRP. It's important to pull the .img directly to PC rather than dumping on internal storage.
lost101 said:
adb reboot recovery
adb pull /dev/block/platform/msm_sdcc.1/by-name/userdata userdata.img
This is done in TWRP. It's important to pull the .img directly to PC rather than dumping on internal storage.
Click to expand...
Click to collapse
Okay, but this command will dumping directly to PC right? Didnt need any additional command to direct it to pc?
prayogasp said:
Okay, but this command will dumping directly to PC right? Didnt need any additional command to direct it to pc?
Click to expand...
Click to collapse
Commands are performed in Command Prompt / Terminal. Report back what happens.
lost101 said:
Commands are performed in Command Prompt / Terminal. Report back what happens.
Click to expand...
Click to collapse
I tried using this command when on twrp recovery but it give me this reply:
Code:
E:\Android\android-sdk\platform-tools>adb devices
List of devices attached
TA9330F2RS recovery
E:\Android\android-sdk\platform-tools>adb pull /dev/block/platform/msm_sdcc.1/userdata userdata.img
adb: error: remote object '/dev/block/platform/msm_sdcc.1/userdata' does not existt
EDIT: Sorry my fault missing by-name, i will report what happen, thank you!
lost101 said:
Commands are performed in Command Prompt / Terminal. Report back what happens.
Click to expand...
Click to collapse
I already have the img of userdata but when i add it as data source on ftk imager or autopsy it shows as unrecognized file system and i cant access it even using other apss like linuxreader cant access it, what happens? Is there any other way around this?
prayogasp said:
I already have the img of userdata but when i add it as data source on ftk imager or autopsy it shows as unrecognized file system and i cant access it even using other apss like linuxreader cant access it, what happens? Is there any other way around this?
Click to expand...
Click to collapse
GetDataBack: https://www.runtime.org/data-recovery-software.htm
lost101 said:
GetDataBack: https://www.runtime.org/data-recovery-software.htm
Click to expand...
Click to collapse
Hello,
I already tried using GetDataBack heres what happen:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
what should i do now? Btw my phone i was trying to recover was after unlocking bootloader.
prayogasp said:
I already tried using GetDataBack heres what happen:
what should i do now? Btw my phone i was trying to recover was after unlocking bootloader.
Click to expand...
Click to collapse
I think I recall the demo version of GetDataBack did not work as well as the full version. Even after bootloader unlock (data wipe) - you should still be able to recover files.
lost101 said:
I think I recall the demo version of GetDataBack did not work as well as the full version. Even after bootloader unlock (data wipe) - you should still be able to recover files.
Click to expand...
Click to collapse
Well, right now im using the full version still post the same result , is there any other way? Or maybe the problem was on the .img i created?
prayogasp said:
Well, right now im using the full version still post the same result , is there any other way? Or maybe the problem was on the .img i created?
Click to expand...
Click to collapse
Try this utility. In Command Prompt type:
ImgExtractor.exe userdata.img userdata
lost101 said:
Try this utility. In Command Prompt type:
ImgExtractor.exe userdata.img userdata
Click to expand...
Click to collapse
Hello, I tried using this utility and suddenly it stop working and giving this reply to command prompt:
I extract the imgextractor.exe to my backup folder and run cmd from there, is it the problem was my img file?
lost101 said:
Try this utility. In Command Prompt type:
ImgExtractor.exe userdata.img userdata
Click to expand...
Click to collapse
What should i do now sir?
prayogasp said:
What should i do now sir?
Click to expand...
Click to collapse
I do not have the time to test solutions for you. I suggest you try a google search and re-read the thread I initially linked to above.
lost101 said:
I do not have the time to test solutions for you. I suggest you try a google search and re-read the thread I initially linked to above.
Click to expand...
Click to collapse
Hi! It seems i found the problem, the problem is because userdata partition detected as a Unallocated Space thats why all apps like Autopsy, FTK imager, GetDataBack, cant determine the file system for userdata partition, do you know the way around this?
My rooted Nexus 5 has got bootloop issue because of faulty power button. It keeps restarting on its own. After replacing the power button with new One from LG Service center, now it stuck
at marshmellow boot screen, that boot keep running entire day untill battery died. LG Service center guys told me to replace the mother board. Since i was not convinced, i decided to make sure
if it is really required. My Nexus 5 has CWM recovery ver 6.0.4 with usb debugging on. Fastboot, adb everything is working. But if i tried to flash / wipe or mount i simply get error
can't mount /persist
cant mount /data
I tried following links to fix it-
https://forum.xda-developers.com/go...-unbrick-nexus-5-stucked-qualcomm-hs-t3043301
https://forum.xda-developers.com/go...orial-how-to-flash-factory-images-lg-t2713833
and some other first hand advice like run "Flash-all.bat" from stock rom, use WUG Toolkit to fix soft brick and flash stock rom or try flashing another custom recovery. But no matter what i try
CWM never get replaced and again same error. i was able to flash TWRP ( only untill reboot)and able to see folders under File Manager. But can't select Data, persist if try to wipe or mount from there.
One thing though, While using LG Flash tool my device never got detected in the tool even though i could see LG USB Serial Port under device manager in PC.
Please suggest if there is anything can be done to get it into working mode ,or motherborad replacement is the only way to go ahead.
You could try repartitioning device. try doing this:
https://forum.xda-developers.com/go...guide-repartition-nexus5-to-increase-t3509880
Actually resizing system partition also deletes userdata partition and it should work after recreating it. You have nothing to loose if it is already broken.
Try flashing the oldest stock ROM from the Google site. Make sure to flash userdata.img and perform a factoru wipe before booting the phone for the first time.
aciupapa said:
You could try repartitioning device. try doing this:
https://forum.xda-developers.com/go...guide-repartition-nexus5-to-increase-t3509880
Actually resizing system partition also deletes userdata partition and it should work after recreating it. You have nothing to loose if it is already broken.
Click to expand...
Click to collapse
Okay. Let me just try what you said. Will post the result
Edit1 -
I was not able to unmount /cache, /data .
On umount /cache it restart on its own and for other unmount /data and unmount /system invalid argument.
This is what happend (See image)--
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
audit13 said:
Try flashing the oldest stock ROM from the Google site. Make sure to flash userdata.img and perform a factoru wipe before booting the phone for the first time.
Click to expand...
Click to collapse
I am really sceptical if this will work. Since I have already tried flashing oldest rom of marshmallow (6.0.0).
Anyways, it won't take much time so will try to flash KitKat and let you know.
Edit -
Result was as expected
remote : failed to erase partition
remote : flash write failure
Any other Help ?? How to make sure if its really hard brick and not soft brick?
Sounds like the internal memory chip is damaged. I had one phone where I could not flash anything so I changed the motherboard and everything worked perfectly after the change.
I think I have a similar issue. Someone please help!
Flashed MIUI8 about a month ago and now I got some 'systemui has stopped working' errors, the device rebooted and got stuck on the MI logo. So I used a fastboot guide on the MIUI forums and fastbooted a Global MIUI V8.0.1.0 rom using MI Flash (selected the 'flash all' option).
The tool says that it has successfully flashed the rom but instead, it just wiped the whole device and not actually flash the rom.
Now the device is stuck on fastboot mode. If I try to reboot the device through TWRP it says 'No OS installed! Are you sure you wish to reboot?'
Tried to flash miui using OTG, it detects the pendrive, but it gives errors while flashing-
Code:
Installing '/usb_otg/miui_MI4iGlobal_V8.1.5.0.LXIMIDI_bd019203d_5.0.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
[COLOR="Red"]E:Error executing updater binary in zip '/usb_otg/miui_MI4iGlobal_V8.1.5.0.LXIMIDI_bd019203d_5.0.zip'[/COLOR]
Error flashing zip 'usb_otg/miui_MI4iGlobal_V8.1.5.0.LXIMIDI_bd019203d_5.0.zip'
Updating partition details...
[COLOR="Red"]E:Unable to mount '/system'
E:Unable to mount '/cache'
E:Unable to mount '/data'[/COLOR]
...done
I've tried to flash different roms (CM, diff versions of miui) but all give pretty much same error.
Also tried ADB sideload method, gives the same errors as above.
I'm out of ideas, anyone has a fix for this?
Fastboot flash, run the bat files instead of using Mi flash. Should work
I ran the .bat file directly but it still says No OS installed in TWRP and boots directly to fastboot mode.
Which file did you ran? From where did you get the firmware?
I got the firmware from the MIUI forums. There are two bat files - flash_all.bat and flash_all_except_data_storage.bat. I tried both but didn't work.
Try to flash it 1 by 1
By typing
Fastboot flash system system.IMG , fastboot flash boot boot.IMG and so on...
There are many .img files in my 'images' folder. Do I flash all img files one by one or what? Please elaborate.
Face6000 said:
There are many .img files in my 'images' folder. Do I flash all img files one by one or what? Please elaborate.
Click to expand...
Click to collapse
Yes , all of them..
The example command is in the vla bla .bat
But , just take a few line or figure it out
Ex: "fastboot flash system system.IMG"
Also , don't forget to place adb and fastboot inside image folder...
*this is a manual fastboot
Copy paste the commands from the bat file
Typed all the commands which were in the .bat file manually in cmd one by one, no errors while flashing but it STILL reboots to fastboot mode and 'No OS installed'.
Hackerpunk1 said:
Copy paste the commands from the bat file
Click to expand...
Click to collapse
Not all of them , the bat file is a script for Miflash , not the manual fastboot ...
Face6000 said:
Typed all the commands which were in the .bat file manually in cmd one by one, no errors while flashing but it STILL reboots to fastboot mode and 'No OS installed'.
Click to expand...
Click to collapse
Are you sure? Do you flash the mbn files?
Could you please send a screenshot ( to make sure )
faizauthar12 said:
Not all of them , the bat file is a script for Miflash , not the manual fastboot ...
Are you sure? Do you flash the mbn files?
Could you please send a screenshot ( to make sure )
Click to expand...
Click to collapse
Yes, I did flash the mbn files. Here are the screenshots -
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm facing a similar situation. Were you able to figure out the solution?
Hello.
I made a typo on the phone and ended up doing rm -rf / * ...
I have unlocked the boot loader and have introduced custom recovery, but when I flush the ROM it doesn't boot at all.
I did a clean install of the stock ROM using Mi Flash or Xiaomi ADB / Fastboot Tool, but it doesn't boot. Boot loop.
Can I fix the phone?
(I'm using Google Translate.)
try to reflash recovery version of full MIUI ROM (cca 2.4 GB) - download from here, try to boot it, if boot loop format data (not wipe), reboot recovery, reboot system
jeryll said:
try to reflash recovery version of full MIUI ROM (cca 2.4 GB) - download from here, try to boot it, if boot loop format data (not wipe), reboot recovery, reboot system
Click to expand...
Click to collapse
I tried using TWRP, but it flashes normally, but Android cannot start
Freezes with the first POCO logo and boot loops…
Try with latest version of Orange fox recovery
jeryll said:
Try with latest version of Orange fox recovery
Click to expand...
Click to collapse
I used Orangefox to flash MIUI, but it flashes successfully but I can't start it ...
I noticed that some folders in / system_root / are empty.
(Even if you mount system, vendor, product)
Is this causing the boot to be blocked?
I decided to try a clean install again using the Xiaomi ADB / Fastboot Tool
But I have already tried this and I don't think it will be solved ...
I did a clean install but it failed ...
I want a Super partition of POCO X3 NFC, or a backup of everything.
It's a straightforward idea, but I think you can boot if you restore a system that is working properly ...
Please help me ... I don't want to make this phone a brick ...
I ran df -h.
Is this information correct? To me, rootfs usage seems strange.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Amatsu1805 said:
I ran df -h.
Is this information correct? To me, rootfs usage seems strange.View attachment 5194031
Click to expand...
Click to collapse
Contact someone online who has an EDL license. At this point, its best to minimize the damage and let an expert handle it.
Amatsu1805 said:
I ran df -h.
Is this information correct? To me, rootfs usage seems strange.View attachment 5194031
Click to expand...
Click to collapse
can't see firmware partition there, wasn't it mounted when you did df -h, or you actually missing it? if it's not present, there could be your problem
jeryll said:
can't see firmware partition there, wasn't it mounted when you did df -h, or you actually missing it? if it's not present, there could be your problem
View attachment 5194327
Click to expand...
Click to collapse
Mounted all partitions.
It will be displayed like this.
My phone is back!‼
It seems that it was fixed by flashing the image file taken out from the fastboot ROM with Orangefox.
Thank you for your support!
Hi all,
I'm going to make a long story short and say that my brother's phone has a cracked screen, so I tried to use TWRP to backup everything through ADB. But googling SM-J530F TWRP brings 'j5lte' as one of the first results, I went and flashed it under the wrong assumption that j5lte was SM-J530F's code name (it was not) and that caused severe bootloops.
I flashed correct TWRP, but USERDATA would not mount. I panicked and the crystal bleeding was progressing fast, so I pulled the entire mmcblk0 to dump a raw image of the phone's NAND.
This was the right move, as the phone is completely dead now. Crystal bleeding has made the screen completely dead, but the phone still works.
All I'm left with is the raw NAND backup.
The first thing I did was inspect the image with fdisk. It can recognize the GPT partition table and structure. The USERDATA partition is at the very end.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
GDISK is also recognizing it no problem. It seems like the partition table is in good condition:
GPARTED is also recognizing partitions, but it does not look good:
Looking at more information:
For the record, e2fsprogs is installed. It's always installed by default. GPARTED here is complaining about the superblock, but I can see that its looking to open the partition through /dev/loop0p24 which is no good. The kpartx tool is giving me access to all the partitions of the image through /dev/mapper/loop0p24, so that explains the errors.
Superblocks seem to be present in USERDATA:
I tried mounting the partition with a backup superblock, but...
I was at a loss at this point, so I tried mounting the SYSTEM partition just to see what happens and... it worked?
This proves what I said: This partition is fine, GPARTED was complaining simply because its trying to target them through the wrong device path.
But this raised the question: What the heck is wrong with the USERDATA partition? Why is it ext2 (Isn't that SUPER old?) and could it be that its not corrupted at all, and I'm just trying to mount it the wrong way or something? TWRP couldn't mount it though (Why?).
Being at a loss, I tried repairing the ext2 USERDATA partition using `fsck.ext2 /dev/mapper/loop0p24` and it found so many errors (including a corrupted journal) the file I redirected stdout to (console output) ended up being 78MB. Here it is if you want it (obviously can't post here).
So anybody knows what I can do? Is there any hope? I'm positive that the recovery image couldn't have corrupted the USERDATA partition (How could it? I still can't find a possible explanation). And even if it did, it couldn't overwrite the files. The file data should STILL be in that partition completely in-tact (There's NO WAY the recovery image overwrote them) though the journal is gone, so I can't use a tool like extundelete to recover them.
I tried to flash the phone with a stock rom through download mode to reconstruct everything with a healthy structure. This was so I could flash TWRP again and pull another NAND raw dump to have as a healthy reference I could use, but this doesn't work. Odin fails and I don't know why because the screen on the phone is dead.
Is there some place where I could get this maybe?
Is there something you can suggest I do?
Thanks!