Related
I HAd Niks Trinity Xl Installed in my incs i was facing some force closes and hangs..so i went into EXT4 touch Recovery and fixed permision..to my suprise Recovery Hanged there...after successfully fixing permission
so i pooped out the battery and reboot the devbice hunged at htc logo
wiated for long lime 15 mins
tried this 2-3 times
again poped out the battery and booted into recovey
wiped cache
wiped dalvik cache
data
and battery stats
installed the same rom again
flashed kernel from adn as im s-on
but still the device wont boot
stuck at htc logo
what is the issue can anyone please help me..
now when im entering in recovery ext4 is saying system not accessible please partition system..if u have chnged hboot the partition all except system...
The recovery is telling you to format, did you? What version 4ext are you using?
ext4 v1.0.0.4 rc3
i havent formated the system yet
im really not that into such thing have alreadyy caused many issues so dont want futher..so what would happen when i exavtly format the /system partition...and i guess the recovery is also lagging...dont know why..
its saying recovery is in safe mode..
rhlmhrtr said:
im really not that into such thing have alreadyy caused many issues so dont want futher..so what would happen when i exavtly format the /system partition...and i guess the recovery is also lagging...dont know why..
Click to expand...
Click to collapse
Formatting system is similar to wiping in the way that you will have to restore it from a nandroid or more wisely, reinstall the entire rom. But reformatting may fix your phone if it is a corrupt partition that is the issue.
Edit: you may need to reinstall/install different recovery. I would seriously consider flashing a different rom also.
http://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.2.0-vivo.img
i formatted the system and rebooted the recovery still recovery is saying
recovery in safe mode.system not accessible please enter wipe menu and format system.if you have changed hboot then choose to format all partition(except sdcard)
afterwards reboot recovery
recovery is saying format failed on /dev/block/mmcblk0p25
so i should change the recover to clockwork mode..??after doing that should i again try to format system..????
how can i flash another rom i cant access my sdcard without the usb cable..dont have a card reader tooo....
I'm sure you are not saying that you have no USB cable. You flash recovery in fastboot mode, similar to how you flash boot.img
Code:
fastboot flash recovery recovery.img
Change "recovery.img" to name of the .img you are using.
Edit: misread your question. You should be able to mount your sdcard in recovery and then copy the rom over that way. I suggest you reflash recovery first.
i have usb cable
but i dont have any other rom zip on my sdcard..and i dont have a card reader to...
the commmand prompt is stuck at writing recovery now what...??????
rhlmhrtr said:
the commmand prompt is stuck at writing recovery now what...??????
Click to expand...
Click to collapse
What does the command prompt say?
nothing just
c:\Android>fastboot flash recovery recovery.img
sending 'recovery' (3726 KB)...
OKAY [ 1.164s]
writing 'recovery'...
thats it then nothing its stuck there only
rhlmhrtr said:
nothing just
c:\Android>fastboot flash recovery recovery.img
sending 'recovery' (3726 KB)...
OKAY [ 1.164s]
writing 'recovery'...
thats it then nothing its stuck there only
Click to expand...
Click to collapse
Unplug the phone, reboot into fastboot and wipe recovery partition.
Code:
fastboot erase recovery
And try again
it is saying something like this
c:\Android>fastboot erase recovery
erasing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 0.001s
rhlmhrtr said:
it is saying something like this
c:\Android>fastboot erase recovery
erasing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 0.001s
Click to expand...
Click to collapse
Do you have another phone you could copy files to your sdcard?
yes i have...tell me what can be done..????
rhlmhrtr said:
yes i have...tell me what can be done..????
Click to expand...
Click to collapse
First try fastboot boot recovery.img
Tell me if that works please.
c:\Android>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 1.164s]
booting...
OKAY [ 0.001s]
finished. total time: 1.165s
now i have cwm on my incs and plus down it has also listed something like this
ClockWorkMoD.......
E:Cant open /cache/Recovery/log
E:Cant open /cache/Recovery/log
E:Cant open /cache/Recovery/last_log
E:Cant open /cache/Recovery/last_log
rhlmhrtr said:
c:\Android>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 1.164s]
booting...
OKAY [ 0.001s]
finished. total time: 1.165s
now i have cwm on my incs and plus down it has also listed something like this
ClockWorkMoD.......
E:Cant open /cache/Recovery/log
E:Cant open /cache/Recovery/log
E:Cant open /cache/Recovery/last_log
E:Cant open /cache/Recovery/last_log
Click to expand...
Click to collapse
This command does not flash the recovery, its only booted and will disappear next boot. Will it let you format any partitions with those errors?
tl;dr Android OS is missing from my Nexus 6 for an unknown reason, fastboot isn't working (nor is flashing via recovery), /system and /firmware partitions read 0 MB in each. Help!
Context
My Nexus 6 is a replacement I got in the beginning of February after some speaker issues with my original N6. The device was unlocked, encrypted, used TWRP as custom recovery, and rooted (with Chainfire's SuperSU). I was running stock 5.1 (shamu-lmy47d). My root apps were few: AdAway, TitaniumBackup, SuperSU, Solid Explorer, and Cerberus (no account activity with Cerberus in the past two weeks). I'm familiar with fastboot, custom recoveries, flashing, etc. I've been doing this on my Droid X, Nexus 4, Nexus 7, and Nexus 6 for years and never had anything like this happen (nor have I really run into issues I couldn't figure out).
Situation
While using Sync for Reddit, some apps started crashing. Then Sync stopped loading anything. Then seemingly every app on my device reported a crash. Thinking a reboot would fix whatever was going on, I rebooted my phone. The boot animation didn't end after ten minutes, so I shut my phone back off and got into recovery.
I tried rebooting to system from TWRP. The first thing I noticed was that TWRP did not prompt me for a PIN. When I tried rebooting to system, I was greeted with the following message: "No OS installed! Are you sure you wish to reboot?". Confused, I went to the backup page to check partition sizes. TWRP showed "System (0MB)", "Data (56975MB)" (that's 57GB--I probably had 20GB maximum).
TWRP logs read as follows:
Code:
Data successfully decrypted, new block device '/dev/block/dm-0'
Updating partition details...
[COLOR="Red"]E:Unable to mount '/system'
E:Unable to mount '/firmware'[/COLOR]
...done
[COLOR="red"]E:Unable to mount storage[/COLOR]
Successfully decrypted with default password.
Updating partition details...
[COLOR="Red"]E:Unable to mount '/system'
E:Unable to mount '/firmware'[/COLOR]
...done
[COLOR="red"]E:Unable to mount storage.
E:Unable to mount /data/media during GUI startup.[/COLOR]
Full SELinux support is present.
[COLOR="red"]E:TWFunc::Copy_Log -- Can't open destination log file: '/cache/recovery/log'
E:Unable to mount /data/media/TWRP/.twrps when trying to read settings file.
E:Unable to open '/cache/recovery/.version'.
E:Unable to mount '/data'[/COLOR]
MTP Enabled
A factory reset from TWRP returns the following:
Code:
Factory Reset Complete
[COLOR="red"]Failed[/COLOR]
and in the log:
Code:
[COLOR="red"]E:Unable to mount '/data'
E: Unknown MTP message type: 1[/COLOR]
Formatting Cache using make_ext4fs function.
[COLOR="red"]E:Unable to mount '/cache'[/COLOR]
Updating partition details...
[COLOR="red"]E:unable to mount '/system'
E:Unable to mount '/cache'
E:Unable to mount '/firmware'[/COLOR]
...done
[COLOR="red"]E:Unable to mount storage.[/COLOR]
I will now post the results of several fastboot commands. Some analysis will follow at the end of this post, but I don't really have a clue as to what is going on.
Code:
$ fastboot flash system system.img
target reported max download size of 536870912 bytes
sending sparse 'system' (522112 KB)...
OKAY [ 17.483s]
writing 'system'...
OKAY [ 8.162s]
sending sparse 'system' (510197 KB)...
OKAY [ 17.036s]
writing 'system'...
OKAY [ 7.362s]
sending sparse 'system' (515601 KB)...
OKAY [ 17.891s]
writing 'system'...
OKAY [ 8.047s]
sending sparse 'system' (188485 KB)...
OKAY [ 6.661s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 94.184s
Code:
$ ./flash-all.sh
target reported max download size of 536870912 bytes
sending 'bootloader' (3807 KB)...
OKAY [ 0.120s]
writing 'bootloader'...
(bootloader) flashing partition ...
(bootloader) This may take a few seconds if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Failed to write primary GPT.
(bootloader) Failed to flash partition
FAILED (remote failure)
finished. total time: 6.105s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
target reported max download size of 536870912 bytes
sending 'radio' (85422 KB)...
OKAY [ 2.676s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) Failed to erase partition
(bootloader) Failed to flash modem
FAILED (remote failure)
finished. total time: 13.678s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: moto-apq8084-71.08
Baseband Version.....: D4.0-9625-02.95
Serial Number........: ZX1G322CNQ
--------------------------------------------
checking product...
OKAY [ 0.002s]
checking version-bootloader...
OKAY [ 0.002s]
checking version-baseband...
OKAY [ 0.003s]
sending 'boot' (7681 KB)...
OKAY [ 0.243s]
writing 'boot'...
(bootloader) Failed to flash partition boot
(bootloader) Failed to flash partition boot
FAILED (remote failure)
Code:
$ fastboot oem lock
...
(bootloader) Failed to erase partition
(bootloader) General Lock failure!
(bootloader) sst lock failure!
FAILED (remote failure)
finished. total time: 11.836s
Code:
$ fastboot -w
erasing 'userdata'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 5.758s
Code:
$ fastboot format system
formatting 'system' partition...
Formatting is not supported for filesystem with type 'raw'.
FAILED ()
finished. total time: 0.002s
I'll try any suggested commands as nothing appears to be working anyways. At this point, I don't care about my data. It's encrypted anyways, so it's probably unrecoverable regardless of if I get my phone working again.
I think the partition table somehow got destroyed or the flash memory failed. What's curious is that /data, /boot, /recovery, /EFS are still intact while /firmware and /system are not. I blame hardware because the issues started while the OS was booted (what on the OS level has permissions to write to /system and /firmware?) and nothing writes to the partitions anymore (they can't even be mounted!).
I'm looking for help in any way, especially the in the following:
(1): Finding the cause of this issue and squashing it if it's a bug in Android, TWRP, or some other software.
(2): Getting my phone back to a working state. Again, I don't care about the data on the device.
(3): (if 2 fails) getting my phone locked and removing TWRP so that I can RMA it--Google has already offered a replacement, but I don't want to send it in unlocked and with TWRP (may cause them to charge me for the replacement)
If this is indeed a software-caused error (again, I don't think my actions of using Sync for Reddit caused this issue), I'm terrified that this may affect others who are less capable of seeking help, or those who have critical data on their devices.
Thanks for reading. Please offer any guidance you may have.
-Ethan
kudos to you for providing so much detail for your problem. It's a rare sight here. It really helps people who are trying to help you.
I have a feeling your device is completely fried as even fastboot isn't working. I remember I had a similar problem with the OS disappearing but I solved it with a fastboot flash. If that doesn't work for you, I'm not sure what can. But then again, I'm not a seasoned tinkerer when it comes to android partitions. Let's wait for someone with more knowledge to share their opinion.
@rootSU do you have any ideas here? Can he mount in TWRP and possibly push the files needed or is TWRP too broken at this point?
Thank you for providing such details with the errors. I wish everyone was so thorough.
Thanks for the replies so far @exb0 and @Evolution_Freak!
For the record, "fastboot devices" and "adb devices" do work. It just appears that any thing operating on the file system does not work. Strangely, I was able to "adb push" a ZIP over and tried to flash it from recovery (flashing failed, of course). I was also able to move the ZIP around using TWRP.
I wonder if it would be feasible to move files into place manually and get a working system again by doing that. I don't want to do that unless it appears to be my only option and there's a good chance of it actually working.
I don't frequent XDA, so help getting knowledgeable community members would be greatly appreciated.
Even if you got it working, if it went *this* bad, you don't want the risk of futures failure. Flash as much stock as you can after formatting each partition using fastboot and return it.
rootSU said:
Even if you got it working, if it went *this* bad, you don't want the risk of futures failure. Flash as much stock as you can after formatting each partition using fastboot and return it.
Click to expand...
Click to collapse
Good point. I think my plan is to get it back to a locked state without TWRP. But how to get there, I have no idea. As you can see in the logs, I can't flash anything with fastboot :\ How can I format the partitions? I might be able to do that.
ethanmad said:
Good point. I think my plan is to get it back to a locked state without TWRP. But how to get there, I have no idea. As you can see in the logs, I can't flash anything with fastboot :\ How can I format the partitions? I might be able to do that.
Click to expand...
Click to collapse
fastboot flash recovery recovery.img
You can try and also:
fastboot format system
fastboot format userdata
fastboot format cache
See if you can then flash system.img, userdata.img and cache.img separately.
Also, which version of adb/fastboot are you using? if you are using the one from the Android SDK i would recommend running the sdk update manager and making sure the SDK platform tools are the latest version
@rootSU I believe the OP already tried "fastboot format system" and got the error "Formatting is not supported for filesystem with type 'raw'."
Didgeridoohan said:
@rootSU I believe the OP already tried "fastboot format system" and got the error "Formatting is not supported for filesystem with type 'raw'."
Click to expand...
Click to collapse
Yes, it says in his post
I will add this, do NOT attempt to OEM lock again. I'm glad it had failed when you tried. Otherwise, we would already be done here.
Code:
$ fastboot oem lock
...
(bootloader) Failed to erase partition
(bootloader) General Lock failure!
(bootloader) sst lock failure!
FAILED (remote failure)
finished. total time: 11.836s
---------- Post added at 07:25 AM ---------- Previous post was at 06:50 AM ----------
Did some searching and found this:
https://help.ubuntu.com/community/DataRecovery
However, being that you've already tried writing to the damaged partitions, it might not be of any help.
---------- Post added at 07:45 AM ---------- Previous post was at 07:25 AM ----------
Not even sure that those tools would apply here but this seems to be a very rare or random error you've encountered.
I am no expert, but the concept about reflashing the default partition table contained in this thread may be helpful. I am not fluent enough in this to advise, but given the detail with which you posed your OP, I figgered you would have no trouble making sense of this:
http://forum.xda-developers.com/nexus-6/general/fix-fix-qhusbbulk-cm12-t3059518
Edit: Look for an explanation of GPT.bin.
SFVDan said:
I am no expert, but the concept about reflashing the default partition table contained in this thread may be helpful. I am not fluent enough in this to advise, but given the detail with which you posed your OP, I figgered you would have no trouble making sense of this:
http://forum.xda-developers.com/nexus-6/general/fix-fix-qhusbbulk-cm12-t3059518
Edit: Look for an explanation of GPT.bin.
Click to expand...
Click to collapse
I had initially thought of this but his phone is still recognized by a PC as it normally should be and not as qhusb bulk. But if this could be a possible solution to his partition problem, then thank you for pointing him in that direction. :good:
IINexusII said:
Also, which version of adb/fastboot are you using? if you are using the one from the Android SDK i would recommend running the sdk update manager and making sure the SDK platform tools are the latest version
Click to expand...
Click to collapse
ADB is version 1.0.31. Fastboot is 4.2.2+git20130218-3ubuntu23, which is the latest version on Ubuntu 14.04. I think my SDK platform tools are up-to-date, but I'll make sure to update when I get home.
Evolution_Freak said:
I will add this, do NOT attempt to OEM lock again. I'm glad it had failed when you tried. Otherwise, we would already be done here.
Code:
$ fastboot oem lock
...
(bootloader) Failed to erase partition
(bootloader) General Lock failure!
(bootloader) sst lock failure!
FAILED (remote failure)
finished. total time: 11.836s
---------- Post added at 07:25 AM ---------- Previous post was at 06:50 AM ----------
Did some searching and found this:
https://help.ubuntu.com/community/DataRecovery
However, being that you've already tried writing to the damaged partitions, it might not be of any help.
---------- Post added at 07:45 AM ---------- Previous post was at 07:25 AM ----------
Not even sure that those tools would apply here but this seems to be a very rare or random error you've encountered.
Click to expand...
Click to collapse
What's wrong with running oem lock? What damage would it do?
I'll try using that link when I get home.
And the error is very strange, yes.
SFVDan said:
I am no expert, but the concept about reflashing the default partition table contained in this thread may be helpful. I am not fluent enough in this to advise, but given the detail with which you posed your OP, I figgered you would have no trouble making sense of this:
http://forum.xda-developers.com/nexus-6/general/fix-fix-qhusbbulk-cm12-t3059518
Edit: Look for an explanation of GPT.bin.
Click to expand...
Click to collapse
Thanks, that looks like it might help. I'll try when I get home. To be honest, the detail in the post is not indicative of my knowledge level. I just copied and pasted (or typed out) logs and command results.
@opssemnik is this is a similar issue to what your post is about? I'm not quite sure what qhusb_bulk means, but my phone is recognized as "Nexus 6" in the file explorer and fastboot/adb devices show the device.
ethanmad said:
ADB is version 1.0.31. Fastboot is 4.2.2+git20130218-3ubuntu23, which is the latest version on Ubuntu 14.04. I think my SDK platform tools are up-to-date, but I'll make sure to update when I get home.
What's wrong with running oem lock? What damage would it do?
I'll try using that link when I get home.
And the error is very strange, yes.
Thanks, that looks like it might help. I'll try when I get home. To be honest, the detail in the post is not indicative of my knowledge level. I just copied and pasted (or typed out) logs and command results.
@opssemnik is this is a similar issue to what your post is about? I'm not quite sure what qhusb_bulk means, but my phone is recognized as "Nexus 6" in the file explorer and fastboot/adb devices show the device.
Click to expand...
Click to collapse
Had your OEM lock succeeded, with no OS installed, you could have inadvertently bricked yourself. It's in your best interest to leave it unlocked until you're sure you can boot into Android and ensure that the "allow OEM unlock" stays ticked after a reboot. If you'd like more information on that, click the top link in my signature.
First things first though, let's get you up and running.
ethanmad said:
To be honest, the detail in the post is not indicative of my knowledge level. I just copied and pasted (or typed out) logs and command results.
Click to expand...
Click to collapse
That you knew enough to do so IS indicative -- at least from my perspective. Well done! Keep us all posted.
ethanmad said:
ADB is version 1.0.31. Fastboot is 4.2.2+git20130218-3ubuntu23, which is the latest version on Ubuntu 14.04. I think my SDK platform tools are up-to-date, but I'll make sure to update when I get home.
Click to expand...
Click to collapse
Just as an FYI, the most current version of ADB is 1.0.32. The Ubuntu repositories do not contain the up to date version.
Louie998 said:
Just as an FYI, the most current version of ADB is 1.0.32. The Ubuntu repositories do not contain the up to date version.
Click to expand...
Click to collapse
Correct. I had to download and install the full SDK to get the latest version. Couldn't flash the OTA with the version that was available from Ubuntu repositories.
If this just happened out of the blue, your internal storage probably has (hardware) issues, flash back stock boot and recovery and return it. Unless you have some data you really want to recover, what's the point of trying to fix it? You can never trust this device again.
Chainfire said:
If this just happened out of the blue, your internal storage probably has (hardware) issues, flash back stock boot and recovery and return it. Unless you have some data you really want to recover, what's the point of trying to fix it? You can never trust this device again.
Click to expand...
Click to collapse
That's part of the problem, he can't get anything to flash. Everything attempted errors out.
[SOLVED: http://forum.xda-developers.com/showpost.php?p=61960808&postcount=2
Also, I realize this should be in the Q&A section. Apologies.]
Until a few days ago, I was on stock 4.4.4 (rooted, unlocked bootloader). I decided to try out the modified stock 5.1 posted on this thread . I had no problems making a backup on TWRP before flashing, but after I flashed 5.1 and went to make a backup, I got stuck in a boot loop.
I had to factory reset from TWRP and tried again, same problems (boot loop whenever I made a backup, and no access to TWRP folder from the OS), so I downloaded the full firmware (TMO_5.1_LPA23.12-15_15_release-keys_Retail_US) from this thread and tried to flash manually using ADB and fastboot, following the instructions in the ReadMe file in the firmware.
Everything was fine until I tried to flash system.img, when this happened:
D:\Phone\MotoX\root>fastboot flash system system.img
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 603230508 is not a multiple of t
he block size 4096
sending sparse 'system' (785522 KB)...
error: write_sparse_skip_chunk: don't care size 603230508 is not a multiple of t
he block size 4096
error: write_sparse_skip_chunk: don't care size 603230508 is not a multiple of t
he block size 4096
OKAY [ 51.425s]
writing 'system'...
(bootloader) Sparse image is malformatted
FAILED (remote failure)
finished. total time: 88.818s
I tried a couple of times, but the same result. So I tried the instructions for manual flashing in this post, and got a different error:
D:\Phone\MotoX\root>mfastboot flash system system.img
load_file: could not allocate 1438613804 bytes
error: cannot load 'system.img'
I'm stuck now and have no idea what to do. It's the exact same file, so I'm not sure why it's being read as two different sizes.
I also tried to factory reset and got this:
D:\Phone\MotoX\root>fastboot -w
erasing 'userdata'...
OKAY [ 1.524s]
formatting 'userdata' partition...
(bootloader) Variable not supported!
Erase successful, but not automatically formatting.
Can't determine partition type.
OKAY [ 0.274s]
erasing 'cache'...
OKAY [ 0.748s]
formatting 'cache' partition...
(bootloader) Variable not supported!
Erase successful, but not automatically formatting.
Can't determine partition type.
OKAY [ 0.278s]
finished. total time: 2.835s
I'd like to be able to use my phone again! Can anyone help, please?
Try mfastboot.
ong14 said:
Try mfastboot.
Click to expand...
Click to collapse
Thanks. I did try, but I got this error:
D:\Phone\MotoX\root>mfastboot flash system system.img
load_file: could not allocate 1438613804 bytes
error: cannot load 'system.img'so I think I'm out of space. Can I use mfastboot to erase and then format the system partition, and then try flashing again? If not, what else can I do?
ruach13 said:
Thanks. I did try, but I got this error:
D:\Phone\MotoX\root>mfastboot flash system system.img
load_file: could not allocate 1438613804 bytes
error: cannot load 'system.img'so I think I'm out of space. Can I use mfastboot to erase and then format the system partition, and then try flashing again? If not, what else can I do?
Click to expand...
Click to collapse
I used this script (modified from xt1053dev) with fastboot from xt1053dev;
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase system
fastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem config carrier YOUR CARRIER
fastboot oem fb_mode_clear
You can try this script with mfastboot instead.
ong14 said:
You can try this script with mfastboot instead.
Click to expand...
Click to collapse
Managed to do it using mfastboot flash system system.img -P
Thanks so much for responding!
Every time I open TWRP(V2.8.6.0) this message shows on the log.
E: Could not mount /data and unable to find crypto folder.
E: Unable to mount '/data'
E: Unable to recreate /data/media folder
Updating partition details...
E: Unable to mount '/data'
..done
E: Unable to mount storage.
E: Unable to mount /data/media during GUI startup.
Full SELinux support is present.
E: Unable to mount /data/media/TWRP/.twrps when trying to read settings file.
E: Unable to mount '/data'
MTP Enabled
E: Unable to mount '/data'
Click to expand...
Click to collapse
I am trying to restore from Stock Partition but it seems the update doesn't fix the partition because of this error.
I think my userdata.img is broken but I don't know how to fix it. I even tried to flash using MiFlash but I wasn't able to flash because of my current partition. I can access fastboot, recovery, adb, and OTG. Can someone please help me with this problem. I've been trying to search for a fix for this problem for a looooong time.
Sephema said:
Every time I open TWRP(V2.8.6.0) this message shows on the log.
I am trying to restore from Stock Partition but it seems the update doesn't fix the partition because of this error.
I think my userdata.img is broken but I don't know how to fix it. I even tried to flash using MiFlash but I wasn't able to flash because of my current partition. I can access fastboot, recovery, adb, and OTG. Can someone please help me with this problem. I've been trying to search for a fix for this problem for a looooong time.
Click to expand...
Click to collapse
try this
reboot in fastboot mode and type these cmds in adb/fastboot
fastboot erase system
fastboot erase userdata
fastboot erase cache
and then flash fastboot miui rom using miflash
ashish289 said:
try this
reboot in fastboot mode and type these cmds in adb/fastboot
fastboot erase system
fastboot erase userdata
fastboot erase cache
and then flash fastboot miui rom using miflash
Click to expand...
Click to collapse
I've tried it but it fails.
Here are the results.
E:\platform-tools>fastboot erase system
******** Did you mean to fastboot format this partition?
erasing 'system'...
FAILED (remote: failed to erase partition
)
finished. total time: 0.011s
E:\platform-tools>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.006s]
finished. total time: 0.007s
E:\platform-tools>fastboot erase userdata
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
FAILED (remote: failed to erase partition
)
finished. total time: 0.011s
E:\platform-tools>
Click to expand...
Click to collapse
Sephema said:
I've tried it but it fails.
Here are the results.
Click to expand...
Click to collapse
bootloader locked or unlocked ? if locked then unlock the bootloader
Hi all,
I have a Nexus 6 phone with disk encryption enabled. I am trying to recover my userdata, could someone help me with this?
Following is what I did.
Backed up encrypted user data:
HTML:
$sudo adb shell dd if=/dev/block/platform/msm_sdcc.1/by-name/userdata myencrypted_userdata
while flashing the new firmware images I accidentally flashed the userdata image that came with factory images too.
I remember the the password I used to encrypt the disk. So I thought I can flash the myencrypted_userdata back, in order to recover the my old data.
I used following command to do that:
HTML:
$ sudo fastboot flash userdata+userdata1 myencrypted_userdata
Unfortunately, that didn't work so how do I flash my backed up "myencrypted_userdata" to my device? and recover it using the the password I know?
Thank you so much for your time
Post note:
Following is the error I am getting:
HTML:
$ sudo fastboot flash userdata+userdata1 myencrypted_userdata
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
fastboot: ../libsparse/sparse.c:143: write_all_blocks: Assertion `pad >= 0' failed.
and size of backed up "myencrypted_userdata" is huge :
HTML:
$ ls -alh myencrypted_userdata
-rw-rw-r-- 1 kar kar 56G mrt 3 13:03
karthik9;71266527
while flashing the new firmware images I accidentally flashed the userdata image that came with factory images.......[/QUOTE said:
It looks like dirty flashing.
New firmware and data from previous version.
That doesn't work in many cases.
Click to expand...
Click to collapse
NLBeev said:
It looks like dirty flashing.
New firmware and data from previous version.
That doesn't work in many cases.
Click to expand...
Click to collapse
Okay, I tried to use the same firmware image version I had, just to recover the data. That is also not working.
I followed the same steps I mentioned earlier:
HTML:
$sudo fastboot flash userdata+userdata1 myencrypted_userdata
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
fastboot: ../libsparse/sparse.c:143: write_all_blocks: Assertion `pad >= 0' failed.
Is there there any other way to recover the data? (I remember the password though)
karthik9 said:
...
Is there there any other way to recover the data? (I remember the password though)
Click to expand...
Click to collapse
Are you sure the data partition is wiped/formatted before restoring your data?
(Assumed, but did not see that in the steps you wrote.)
NLBeev said:
Are you sure the data partition is wiped/formatted before restoring your data?
(Assumed, but did not see that in the steps you wrote.)
Click to expand...
Click to collapse
Thank you for you response.
So I did wipe out the old userdata with new firmware image (userdata.img) using following command .
HTML:
$sudo fastboot flash userdata userdata.img
Then now I am trying to restore my old userdata partition using following command:
HTML:
$sudo fastboot flash userdata+userdata1 myencrypted_userdata
No I didn't do anything else in between. Am I missing something in between? if so, how do I format the data partition? Also, the encrypted image size is huge "56G". Is that a problem?
karthik9 said:
No I didn't do anything else in between. Am I missing something in between? if so, how do I format the data partition? Also, the encrypted image size is huge "56G". Is that a problem?
Click to expand...
Click to collapse
Don't know about the size, try it. But you have to fastboot erase the data partition first.
Try fastboot erase userdata and fastboot erase cache before restoring.
EDIT the format command is
Fastboot format <partition>
NLBeev said:
Don't know about the size, try it. But you have to fastboot erase the data partition first.
Try fastboot erase userdata and fastboot erase cache before restoring.
EDIT the format command is
Fastboot format <partition>
Click to expand...
Click to collapse
Still getting same error:
HTML:
[email protected]:~ $ sudo fastboot erase userdata [134]
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 1.649s]
finished. total time: 1.649s
[email protected]:~ $ sudo fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.024s]
finished. total time: 0.024s
[email protected]:~ $ sudo fastboot flash userdata+userdata1 myencrypted_userdata
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
fastboot: ../libsparse/sparse.c:143: write_all_blocks: Assertion `pad >= 0' failed.
Last idea:
Fastboot erase userdata
Fastboot format userdata
<Restore>