Where to start after all the troubleshooting I've done...:crying:
I have the NVIDIA Shield Tablet K1 and rooted it a while back, it was working fine for a long time, months.... Then I went to use my tablet again after about a week or so of not using it so it was dead of course, charged it. Turned it on and was welcomed by a lovely bootloop. So I restart it and go into my TWRP recovery and go to format the device only to find that none of my partitions are able to mount.
When I Factory reset I get the following...
PHP:
Failed to mount '/cache' (Invalid argument)
E: Primary block device '/dev/block/platform/sdhci-tegra.3./by-name/UDA' for mount point '/data' is not present !
Failed to mount '/data' (Invalid argument)
Unable to recreate /data/media folder.
Updating partition details...
Failed to mount '/system' (Invalid argument)
Failed to mount '/cache' (Invalid argument)
Failed to mount '/data'
...done
Unable to mount storgae
Failed to mount '/data' (Invalid argument)
Full SELinux support is present.
Unable to mount /data/media/TWRP/.twrps
MTP Enabled
Updating partition details...
Failed to mount '/system' (Invalid argument)
Failed to mount '/cache' (Invalid argument)
Failed to mount '/data' (Invalid argument)
...done
Unable to mount storage
But it says successful, and pretty much same error if I try to format the data.
It won't let me mount any partitions even after the following commands which are successful in ADB
I have even tried the nice script NVIDIA made to flash everything as well.
PHP:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash staging blob
Some extra things I have noticed was that my [nvtboot] (version *) appeared as a weird looking symbol , like a circle with a square and a triangle scrambled together and same as my boot.
^^This was the first time I noticed this
Then when I flashed the everything even the bootloader it made this symbol disappear and changed it to [nvtboot] (version 19951_588.2760)
The device still would not boot.
I then loaded TWRP and to my surprise it worked and I got back to square one with the inability to mount any partitions. And for each partition showed 0MB.
I think the device may be bricked but I want to save it because I loved my tablet. It's in pristine condition and is about a year old only after the RMA turn ins for the old model.
When I do the flashall.bat which I am doing right now. I reboot and it still does not boot up.
HTML:
target reported max download size of 570425344 bytes
sending 'recovery' (10286 KB)...
OKAY [ 0.450s]
writing 'recovery'...
OKAY [ 0.413s]
finished. total time: 0.866s
target reported max download size of 570425344 bytes
sending 'boot' (6996 KB)...
OKAY [ 0.297s]
writing 'boot'...
OKAY [ 0.276s]
finished. total time: 0.576s
target reported max download size of 570425344 bytes
erasing 'system'...
OKAY [ 0.232s]
sending sparse 'system' (556862 KB)...
OKAY [ 23.301s]
writing 'system'...
OKAY [ 22.077s]
sending sparse 'system' (547639 KB)...
OKAY [ 22.936s]
writing 'system'...
OKAY [ 20.968s]
sending sparse 'system' (127570 KB)...
OKAY [ 5.434s]
writing 'system'...
OKAY [ 4.940s]
finished. total time: 99.897s
target reported max download size of 570425344 bytes
erasing 'userdata'...
OKAY [ 1.758s]
sending sparse 'userdata' (557052 KB)...
OKAY [ 23.332s]
writing 'userdata'...
OKAY [ 18.589s]
sending sparse 'userdata' (557052 KB)...
OKAY [ 24.195s]
writing 'userdata'...
OKAY [ 18.511s]
sending sparse 'userdata' (517936 KB)...
OKAY [ 22.409s]
writing 'userdata'...
OKAY [ 17.156s]
sending sparse 'userdata' (129718 KB)...
OKAY [ 5.656s]
writing 'userdata'...
OKAY [ 4.516s]
finished. total time: 1028.914s
target reported max download size of 570425344 bytes
sending 'staging' (18041 KB)...
OKAY [ 0.783s]
writing 'staging'...
OKAY [ 0.659s]
finished. total time: 1.445s
Press any key to exit...
I am open to all troubleshooting steps you guys can throw at me. I am very tech savvy and hold a Tier II IT position currently with multiple certifications. I for the life of me can't figure this one out. I have been working on this one for weeks and weeks and decided to post on here to get some assistance.
At least tell me I am screwed haha.
if u boot on TWRP . for me it's maybe soft bricked.
where did u find the nvidia script ?
could u see ur device in adb ?
suicyko said:
if u boot on TWRP . for me it's maybe soft bricked.
where did u find the nvidia script ?
could u see ur device in adb ?
Click to expand...
Click to collapse
So I can freely remove or install TWRP and boot from most versions. But within the TWRP it shows that there are no partitions as stated above which is odd. I got the Nvidia script from developer.nvidia.com / gameworksdownload
And i did see my devices in ADB
Try going into TWRP while connected to PC and see if your PC can detect your tablet as removable storage. If it can try reformatting your tablet.
fpozar said:
Try going into TWRP while connected to PC and see if your PC can detect your tablet as removable storage. If it can try reformatting your tablet.
Click to expand...
Click to collapse
I managed to get it to detect as 'wx_na_wf'. Unable to format or do anything of the sort. I used TWRP 2.8.7.0 to format the partitions as ext4 and still errored out as not being able to mount. Pretty much said unable to repair /'anything' and or unable to mount anything either. I used the file manager and could view some of the files within the devices and even rename or delete them with TWRP but as far as mounting anything or booting the device when I run the install.bat. Nothing works. It's really weird. I can even install different versions of TWRP so how can the recovery work but nothing else. It's really odd
Install the newest twrp from twrp.me or find twrp with f2fs support by BitObsession.
Check &/or repair file system for all partitions. For stock all should be ext4. @Rogark
Everytime I try to repair using TWRP, I receive the below error, I tried every build up from 3.0.0-0 to the latest.
Code:
Failed to mount '/cache' (Invalid argument)
E: Primary block device '/dev/block/platform/sdhci-tegra.3./by-name/UDA' for mount point '/data' is not present !
Failed to mount '/data' (Invalid argument)
Unable to recreate /data/media folder.
Updating partition details...
Failed to mount '/system' (Invalid argument)
Failed to mount '/cache' (Invalid argument)
Failed to mount '/data'
...done
Unable to mount storgae
Failed to mount '/data' (Invalid argument)
Full SELinux support is present.
Unable to mount /data/media/TWRP/.twrps
MTP Enabled
Repairing System using e2fsck...
/sbin/e2fsck -fp process ended with ERROR: 16
Unable to repair System
Same thing with f2fs. (mkfs.f2fs -t 0 processs ended with ERROR: 1
Unable to wipe System.
Error changing file system.
Updating partition details
unable to mount the same as above.
What I don't get is how I can change my recovery just fine and fix my NVTBOOT with a stock shield rom but it's acting like my partitions are not seen or they contain no memory. I don't want to give up on this but
I also don't know what else to do. This is really weird, maybe this is a brick at this point.
Try formatting with stock recovery?
lafester said:
Try formatting with stock recovery?
Click to expand...
Click to collapse
I tried this as well. I boot to recovery, I tried different stock versions from factory to 5.2. When I boot to recovery it takes about 5 minutes for me to get the dead android, sometimes it says no command.
Any other tips or things to try? I am pondering the microwave at this point.
Bump, still want to save my tablet.
Have you tried the Mutlirom TWRP from last Year that is floating around? Give it a shot if not.
I was having the same issue, I did some looking around and found another post stating that after flashing the factory image, to flash the tegra124-tn8-p1761-1270-a04-e-battery.dtb file. I did that and it worked like a charm and now im running lineageOS 15.1, Hopefully that helps you out, although i did try many things prior to that like using fastboot commands to erase/ format my cache and data partitions.
So, I flashed the tegra battery file and tried that and now the screen just begins to load on boot but after about 4 seconds of loading, it will freeze the image of the NVIDIA symbol and get brighter and pixelate until it shuts out and goes black for another reboot. This is a new error. I will flash everything again once more and try this one more time. I miss my tablet lol
Still states that it can't find partition sizes on TWRP after flashing everything to stock even battery.dtb. It continue states unable to mount /data,cache, etc. <--This was with multirom and even tried all of the repairs which all failed out.
I will try whatever else you guys recommend. Just need further guidance please. This one is mind-boggling for sure
Something else to maybe help you guys. I flash to a stock rom even the dtb file and go to recovery mode in which i receive a dead android. Then I hold power and the up volume button to get the sys options and proceed to factory reset or mount /system files in there and receive the partition mounting errors as well. Why does it flash the ROMs successfully but can never mount them or boot properly?
So I can flash TWRP to my recovery and actually use adb to push files to the different /sdcard /data directories and such, I pushed .imgs and even SuperSU.zip and installed it but something is wrong with my partition table.
Did you try flashing the original stock lollipop rom?
fpozar said:
Did you try flashing the original stock lollipop rom?
Click to expand...
Click to collapse
Just tried that and even cleaned all of my partitions once more before hand and flashed everything to the stock build. Still does same thing. This is crazy lol
Related
Hello all
Just bought this phone I9020T. The phone didn't go past Google so I tried to wipe and format/system. Everything completes fine but nothing changed interns of files and folders
I tried installing ICS via 4.0.4 fast boot but failed on system write.
I'm now able to get into the phone it is running cm9 rc0. However can't wipe from with in either. Neither can I wipe the sdcard.
Any thoughts?
I am unable to format /system or /data or /sdcard partition via CWM 5.0.2.3 recovery.
I can't factory reset the phone.
Here is the fastboot output:
-imm76d>fastboot -w update image-soju-imm76d.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: I9020XXKL1
Baseband Version.....: I9020XXKI1
Serial Number........: 393204CBDFEE00EC
--------------------------------------------
checking product... OKAY [ 0.001s]
checking version-bootloader... OKAY [ 0.001s]
checking version-baseband... OKAY [ 0.001s]
sending 'boot' (3444 KB)... OKAY [ 0.629s]
writing 'boot'... OKAY [ 0.423s]
sending 'recovery' (3776 KB)... OKAY [ 0.696s]
writing 'recovery'... OKAY [ 0.466s]
sending 'system' (282046 KB)... OKAY [ 51.201s]
writing 'system'... FAILED (remote: Write Fail)
finished. total time: 53.483s
Also just to add I was able to flash ICS bootloader and recovery via fastboot.
Do you have the newest ClockworkMod Recovery installed?
I have 5.0.2.3 installed.
Not touch. I can't flash system with fast boot why should it matter what recovery I have?
So you want to format your sdcard? Am I right? If so, while in recovery, go to "mount and storage" and choose format sdcard.
Sent from my Nexus S using Tapatalk
I am unable to format /system or /data or /sdcard partition via recovery.
I can't factory reset the phone.
Here is the fastboot output:
-imm76d>fastboot -w update image-soju-imm76d.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: I9020XXKL1
Baseband Version.....: I9020XXKI1
Serial Number........: 393204CBDFEE00EC
--------------------------------------------
checking product... OKAY [ 0.001s]
checking version-bootloader... OKAY [ 0.001s]
checking version-baseband... OKAY [ 0.001s]
sending 'boot' (3444 KB)... OKAY [ 0.629s]
writing 'boot'... OKAY [ 0.423s]
sending 'recovery' (3776 KB)... OKAY [ 0.696s]
writing 'recovery'... OKAY [ 0.466s]
sending 'system' (282046 KB)... OKAY [ 51.201s]
writing 'system'... FAILED (remote: Write Fail)
finished. total time: 53.483s
Made it worse when i did fastboot oem lock.
now I can't unlock.
fastboot oem unlock
... FAILED (remote: Erase Fail)
i have the same problem
accidently wiped the whole system and almost everything besides SD Card and now im stuck on the google logo. Well if you havent already, try fastboot flash recovery twrp-crespo-2.0.0RC0.img. From http://nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread/. That will get you into team win recovery project. From there you can do the same things as CWM Recovery. The problem for me is that i cant flash a rom at all but i can flash google apps. The rom doesnt actually flash for some reason. I have a thread up about this problem aswell :http://forum.xda-developers.com/showthread.php?p=24827487#post24827487
Please check recovery.log after trying to format in CWM (by choosing Report error). If it shows bad blocks, the chances are your NAND chip should be replaced.
The same NAND memory chip stores all partitions (including USB storage area): with high read/write rates on a large storage area (USB/sdcard part) it's more likely for the chip to go wrong.
How do I change the NAND?
By replacing the NAND memory chip mounted on the PCB.
Are we sure it's hardware?
anglergab said:
By replacing the NAND memory chip mounted on the PCB.
Click to expand...
Click to collapse
As in, remove it from the mainboard, somehow find another that is compatible and re-solter the pins back on?
How sure are we that this is a hardware issue? I'd like to be sure before I go plucking NAND chips off of the PCB!
Same exact issue. I've tried countless ways to recover my phone (from recovery and fastboot flashes). It seems like /system not being writable is the kiss of death. Not having /sdcard writable means I can't really do much from recovery. Can't access my backups or transfer anything from my computer. My hands are pretty tied here!
i have the samme problem what can i do?really i can replace nand sd card?
I have the same issue as the OP when flashing the factory ROM for my Nexus S. Things fail at:
writing 'system'...
FAILED (remote: Write Fail)
finished. total time: 37.464s
I put on Clockwork recovery and can not mount / delete /sdcard, /system, or /data. The log message states:
Formatting /system...
E:format_volume: make_extf4fs failed on /dev/block/platform/s3c-sdhci.0/by-name/system
Error formatting /system!
---
Formatting /sdcard
I:Formatting unknown device
W:failed to mount /dev/block/platform/s3c-sdhci.0/by-name/media (No such file or directory)
---
Since Nexus S is a dev device for me I moved onto others, but would like to determine if I should put it out to pasture / throw it away since I assume there will be no equitable repair / return at this stage.
For several months prior the device gets stuck at the Google logo / flashes then requires a battery pull. Oddly enough I was able to get it to boot about 1 in 3 then 1 in 5 times if I went into stock recovery, let it sit there for a minute or so, reboot back into bootloader then hit power off. "Magically" next power on it without going to the bootloader it would boot normally. Well... This stopped working or I gave up after 5 tries!
This does make me think the poster mentioning NAND failure or a hardware failure for the storage is probably what is happening.
Anyway... I'd be glad to hear if there is any resolution to this matter, but kind of guess it's time to blend this device. Sucks cause it was my only ICS device right now... sigh...
I ended up going through warranty services from Samsung, and got it replaced free of charge, within the warranty timeframe. Interestingly enough they repaired it with me being the second-owner.
Thanks for the heads up on the warranty repair.. Though mine is out of warranty it appears they will fix it for no cost or that is what I was told over the phone. That much is good and wasn't my first assumption that it would be a free fix.
Hi all,
one morning my phone (GB retail 1032, 8GB version) running Paranoid Android 4.42 started to throw error messages saying com.google.gapps stopped working. I rebooted the phone which stuck at the Motorola logo, and I cannot get past it since then. When I reboot to recovery there are several error messages:
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't mount /cache/recovery/last_log
In fastboot mode fastboot -w prints the following:
Erase successful, but not automatically formatting.
File system type raw not supported.
Erase successful, but not automatically formatting.
File system type raw not supported.
erasing 'userdata'...
OKAY [ 0.033s]
erasing 'cache'...
OKAY [ 0.033s]
finished. total time: 0.070s
I tried to reflash the ROM in CWM but it fails with "Some symlinks could not be created" error message. Also tried to flash custom recoveries and even full stock ROMs in fastboot mode and although the process is completed without error messages, the changes are not there, for example I flashed TWRP recovery and the phone still boots to CWM like the eMMC card became write protected, so the memory is definitely corrupted. I also tried running the Qualcomm unbrick tool but it does not detect my phone since it is still capable to boot to fastboot or recovery.
Did anyone face something like this?
debaj said:
Hi all,
one morning my phone (GB retail 1032, 8GB version) running Paranoid Android 4.42 started to throw error messages saying com.google.gapps stopped working. I rebooted the phone which stuck at the Motorola logo, and I cannot get past it since then. When I reboot to recovery there are several error messages:
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't mount /cache/recovery/last_log
In fastboot mode fastboot -w prints the following:
Erase successful, but not automatically formatting.
File system type raw not supported.
Erase successful, but not automatically formatting.
File system type raw not supported.
erasing 'userdata'...
OKAY [ 0.033s]
erasing 'cache'...
OKAY [ 0.033s]
finished. total time: 0.070s
I tried to reflash the ROM in CWM but it fails with "Some symlinks could not be created" error message. Also tried to flash custom recoveries and even full stock ROMs in fastboot mode and although the process is completed without error messages, the changes are not there, for example I flashed TWRP recovery and the phone still boots to CWM like the eMMC card became write protected, so the memory is definitely corrupted. I also tried running the Qualcomm unbrick tool but it does not detect my phone since it is still capable to boot to fastboot or recovery.
Did anyone face something like this?
Click to expand...
Click to collapse
did you flash different rom without wipe ? it happened with me on my nexus 7 (2012) , the emmc was corrupted and was gone into a hardware problem.
SahilTech said:
did you flash different rom without wipe ? it happened with me on my nexus 7 (2012) , the emmc was corrupted and was gone into a hardware problem.
Click to expand...
Click to collapse
No, it happened on a morning without any warning. The ROM on the phone was flashed about one week earlier.
Does anyone know where I can get a replacement logic board, or a broken device with good logic board? I tried Ebay without success. I got an offer for BGA rework which would be around 70 USD, but first I'd look for a cheaper solution.
i posted the below in a thread and they said its a emmc failure and it cant be fixed.
Recently my friend bricked his moto g xt1033 while charging. He unplugged the charger when he saw a black screen and when he turned on his phone all his apps started force closing beginning with the message "unfortunately the process-------has been stopped". I tried installing custom recovery to change the rom, the custom recovery didnt get installed. I tried flashing the stock rom again from pc and the problem still persisted. I tried all possible ways to save the phone, finally gave it to the service center and even those guys couldnt fix!
The eMMC is not corrupted or defunct, you just got the fs on those positions destroyed, therefore they are not formatted now, thus being RAW.
If you still have custom recovery installed, try formatting /system, /data and flash CM12.
SAme problem here, has anyone found a solution to recover write permissions to emmc?
ı can twrp boot but ı cant format.data.cache. failed mount cache
C:\Program Files\Minimal ADB and Fastboot>fastboot -w
wiping userdata...
Erase successful, but not automatically formatting.
File system type raw not supported.
wiping cache...
Creating filesystem with parameters:
Size: 694288384
Block size: 4096
Blocks per group: 32768
Inodes per group: 7072
Inode size: 256
Journal blocks: 2648
Label:
Blocks: 169504
Block groups: 6
Reserved block group size: 47
Created filesystem with 11/42432 inodes and 5511/169504 blocks
target reported max download size of 536870912 bytes
erasing 'userdata'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 10.004s
Hi everyone,
So I got a nexus 5 from a friend that he said was broken. He told me that he was doing and update and was taking too long so he rebooted his phone. Now the phone is stuck in a boot loop. Everything is stock on the phone and he said he never rooted it. I followed the steps on this thread(method 2 manually flashing each img) http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701 Here is the output from the CMD window:
C:\Users\brad\Desktop\hammerhead-lrx22c-factory-0f9eda1b\hammerhead-lrx22c>fastb
oot flash bootloader bootloader.img
target reported max download size of 1073741824 bytes
sending 'bootloader' (2579 KB)...
OKAY [ 0.298s]
writing 'bootloader'...
OKAY [ 0.515s]
finished. total time: 0.813s
C:\Users\brad\Desktop\hammerhead-lrx22c-factory-0f9eda1b\hammerhead-lrx22c>fastb
oot reboot bootloader
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format <partition> format a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size. default:
2048
-S <size>[K|M|G] automatically sparse files greater th
an
size. 0 to disable
C:\Users\brad\Desktop\hammerhead-lrx22c-factory-0f9eda1b\hammerhead-lrx22c>fastb
oot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Users\brad\Desktop\hammerhead-lrx22c-factory-0f9eda1b\hammerhead-lrx22c>fastb
oot flash radio radio.img
target reported max download size of 1073741824 bytes
sending 'radio' (45521 KB)...
OKAY [ 1.622s]
writing 'radio'...
OKAY [ 3.120s]
finished. total time: 4.743s
C:\Users\brad\Desktop\hammerhead-lrx22c-factory-0f9eda1b\hammerhead-lrx22c>fastb
oot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.016s
C:\Users\brad\Desktop\hammerhead-lrx22c-factory-0f9eda1b\hammerhead-lrx22c>fastb
oot flash system system.img
target reported max download size of 1073741824 bytes
erasing 'system'...
OKAY [ 1.065s]
sending 'system' (981472 KB)...
OKAY [ 31.005s]
writing 'system'...
OKAY [ 66.272s]
finished. total time: 98.341s
C:\Users\brad\Desktop\hammerhead-lrx22c-factory-0f9eda1b\hammerhead-lrx22c>fastb
oot flash userdata userdata.img
target reported max download size of 1073741824 bytes
erasing 'userdata'...
OKAY [ 13.676s]
sending 'userdata' (137318 KB)...
OKAY [ 4.514s]
writing 'userdata'...
OKAY [ 9.179s]
finished. total time: 27.369s
C:\Users\brad\Desktop\hammerhead-lrx22c-factory-0f9eda1b\hammerhead-lrx22c>fastb
oot flash boot boot.img
target reported max download size of 1073741824 bytes
sending 'boot' (8852 KB)...
OKAY [ 0.485s]
writing 'boot'...
OKAY [ 0.749s]
finished. total time: 1.233s
C:\Users\brad\Desktop\hammerhead-lrx22c-factory-0f9eda1b\hammerhead-lrx22c>fastb
oot flash recovery recovery.img
target reported max download size of 1073741824 bytes
sending 'recovery' (9552 KB)...
OKAY [ 0.517s]
writing 'recovery'...
OKAY [ 0.782s]
finished. total time: 1.299s
C:\Users\brad\Desktop\hammerhead-lrx22c-factory-0f9eda1b\hammerhead-lrx22c>fastb
oot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.452s]
finished. total time: 0.452s
C:\Users\brad\Desktop\hammerhead-lrx22c-factory-0f9eda1b\hammerhead-lrx22c>
Now when I select recovery after I flashed everything the phone turns off and doesn't come back on until I push the power button. Is that normal?(Not sure if this matters as well but sometimes when I push the power button + volume up and down the phone won't turn on. I have to just push the power button and let it boot loop, turn if off with the power button and try getting into fast boot again.) So I pushed the power button and load back into fastboot go into recovery and get the droid with the red exclamation mark. Push power + volume up and get into the options.
At the bottom of the screen it says:
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery / log
E:Can't open /cache/recovery / log
E:failed to mount / cache (Invalid argument)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/last_install
E:Can't open /cache/recovery/last_install
E:failed to mount /cache (Invalid argument)
When I try wipe data/factory reset I get:
--Wiping data...
Formatting /data...
E:failed to mount /cache (Invalid argument)
Formatting /cache...
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery / log
E:Can't open /cache/recovery / log
E:failed to mount / cache (Invalid argument)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/last_install
E:Can't open /cache/recovery/last_install
Data wipe complete.
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery / log
E:Can't open /cache/recovery / log
E:failed to mount / cache (Invalid argument)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/last_install
E:Can't open /cache/recovery/last_install
E:failed to mount /cache (Invalid argument)
So I tried to wipe cache partition command and basically get the same thing as above the only string that is different is:
E:Failed closing /dev/block/platform/msm_sdcc.1/by-name/mis(I/O error)
Anyone know where I can go from here?
From what I can see you erased cache partition but didn't flash it back.
You need to flash cache partition also.
Code:
fastboot flash cache cache.img
varuntis1993 said:
From what I can see you erased cache partition but didn't flash it back.
You need to flash cache partition also.
Code:
fastboot flash cache cache.img
Click to expand...
Click to collapse
Yeah. My mistake. Doing that right now but now it's stuck.....
C:\Users\brad\Desktop\hammerhead-lrx22c-factory-0f9eda1b\hammerhead-lrx22c>fastb
oot flash cache cache.img
target reported max download size of 1073741824 bytes
erasing 'cache'...
Been like this for about 20 minutes.
workonyou said:
Yeah. My mistake. Doing that right now but now it's stuck.....
C:\Users\brad\Desktop\hammerhead-lrx22c-factory-0f9eda1b\hammerhead-lrx22c>fastb
oot flash cache cache.img
target reported max download size of 1073741824 bytes
erasing 'cache'...
Been like this for about 20 minutes.
Click to expand...
Click to collapse
20min, it should only take seconds to flash it.
I hope you are using usb 2.0 ports.
varuntis1993 said:
20min, it should only take seconds to flash it.
I hope you are using usb 2.0 ports.
Click to expand...
Click to collapse
Yes I am.
workonyou said:
Yes I am.
Click to expand...
Click to collapse
Have you tried disconnecting and connecting again?
I am not sure whether you should do that or not, but you have no other choice right now.
varuntis1993 said:
Have you tried disconnecting and connecting again?
I am not sure whether you should do that or not.
Click to expand...
Click to collapse
I tried something else. I flashed the 4.4.4 stock img using flash-all. Phone booted into android but now camera, google play and gallery are constantly crashing. As well when I try to do a software update it won't download. So I tried to download a random file using chrome and when I did it said "NO SD CARD." What can I do now?
workonyou said:
I tried something else. I flashed the 4.4.4 stock img using flash-all. Phone booted into android but now camera, google play and gallery are constantly crashing. As well when I try to do a software update it won't download. So I tried to download a random file using chrome and when I did it said "NO SD CARD." What can I do now?
Click to expand...
Click to collapse
Try factory reset from stock recovery.
Are you able to lock the bootloader? lock it, reboot and check whether it got locked or not.
Code:
fastboot oem lock
varuntis1993 said:
Try factory reset from stock recovery.
Are you able to lock the bootloader? lock it, reboot and check whether it got locked or not.
Code:
fastboot oem lock
Click to expand...
Click to collapse
When you say factory reset from stock recovery do you mean going into fastboot>recovery>factory/data reset?
I'll try locking the bootloader now.
Not sure if this helps. But when I flashed the 4.4.4 cache IMG it worked fine. Why doesn't the 5.01 work? See output for 4.4.4:
OKAY [ 14.446s]
erasing 'cache'...
OKAY [ 0.525s]
formatting 'cache' partition...
Creating filesystem with parameters:
Size: 734003200
Block size: 4096
Blocks per group: 32768
Inodes per group: 7472
Inode size: 256
Journal blocks: 2800
Label:
Blocks: 179200
Block groups: 6
Reserved block group size: 47
Created filesystem with 11/44832 inodes and 5813/179200 blocks
sending 'cache' (13348 KB)...
writing 'cache'...
OKAY [ 1.862s]
****
EDIT
I am able to lock the bootloader
workonyou said:
When you say factory reset from stock recovery do you mean going into fastboot>recovery>factory/data reset?
I'll try locking the bootloader now.
Not sure if this helps. But when I flashed the 4.4.4 cache IMG it worked fine. Why doesn't the 5.01 work? See output for 4.4.4:
OKAY [ 14.446s]
erasing 'cache'...
OKAY [ 0.525s]
formatting 'cache' partition...
Creating filesystem with parameters:
Size: 734003200
Block size: 4096
Blocks per group: 32768
Inodes per group: 7472
Inode size: 256
Journal blocks: 2800
Label:
Blocks: 179200
Block groups: 6
Reserved block group size: 47
Created filesystem with 11/44832 inodes and 5813/179200 blocks
sending 'cache' (13348 KB)...
writing 'cache'...
OKAY [ 1.862s]
****
EDIT
I am able to lock the bootloader
Click to expand...
Click to collapse
Since you are able to lock the bootloader, there should not be any issue with nand.
yep I meant that.
how did you install fastboot? you have latest files? Replace them with these
https://www.androidfilehost.com/?fid=95784891001607611
varuntis1993 said:
Since you are able to lock the bootloader, there should not be any issue with nand.
yep I meant that.
how did you install fastboot? you have latest files? Replace them with these
https://www.androidfilehost.com/?fid=95784891001607611
Click to expand...
Click to collapse
Hmmm. I think I was using an older version of fastboot. I was going to try and re-flash everything so I went ahead and unlocked the bootloader and now it's stuck erasing again.
workonyou said:
Hmmm. I think I was using an older version of fastboot. I was going to try and re-flash everything so I went ahead and unlocked the bootloader and now it's stuck erasing again.
Click to expand...
Click to collapse
It takes quite some time to erase when unlocking the bootloader.
varuntis1993 said:
It takes quite some time to erase when unlocking the bootloader.
Click to expand...
Click to collapse
I was still erasing after 1hr+ so I powered off the phone went back into fastboot(unlocked) and flashed 5.01 images using the fastboot you linked. Output:
C:\Users\brad\Desktop\hammerhead-lrx22c-factory-0f9eda1b\hammerhead-lrx22c>fastb
oot devices
04a9c8e213afcb97 fastboot
C:\Users\brad\Desktop\hammerhead-lrx22c-factory-0f9eda1b\hammerhead-lrx22c>flash
-all
sending 'bootloader' (2579 KB)...
OKAY [ 0.299s]
writing 'bootloader'...
OKAY [ 0.463s]
finished. total time: 0.765s
rebooting into bootloader...
OKAY [ 0.122s]
finished. total time: 0.123s
target reported max download size of 1073741824 bytes
sending 'radio' (45521 KB)...
OKAY [ 1.618s]
writing 'radio'...
OKAY [ 3.124s]
finished. total time: 4.743s
rebooting into bootloader...
OKAY [ 0.120s]
finished. total time: 0.120s
target reported max download size of 1073741824 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.img'
Creating filesystem with parameters:
Size: 29236371456
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 7137786
Block groups: 218
Reserved block group size: 1024
Created filesystem with 11/1785856 inodes and 156120/7137786 blocks
Cannot read image.
Creating filesystem with parameters:
Size: 734003200
Block size: 4096
Blocks per group: 32768
Inodes per group: 7472
Inode size: 256
Journal blocks: 2800
Label:
Blocks: 179200
Block groups: 6
Reserved block group size: 47
Created filesystem with 11/44832 inodes and 5813/179200 blocks
--------------------------------------------
Bootloader Version...: HHZ12d
Baseband Version.....: M8974A-2.0.50.2.22
Serial Number........: 04a9c8e213afcb97
--------------------------------------------
checking product...
OKAY [ 0.100s]
checking version-bootloader...
OKAY [ 0.099s]
checking version-baseband...
OKAY [ 0.100s]
sending 'boot' (8852 KB)...
OKAY [ 0.489s]
writing 'boot'...
OKAY [ 0.753s]
sending 'recovery' (9552 KB)...
OKAY [ 0.545s]
writing 'recovery'...
OKAY [ 0.797s]
erasing 'system'...
OKAY [ 0.950s]
sending 'system' (981472 KB)...
OKAY [ 30.993s]
writing 'system'...
OKAY [ 66.258s]
erasing 'userdata'...
OKAY [ 11.154s]
erasing 'cache'...
OKAY [ 0.449s]
sending 'cache' (13348 KB)...
OKAY [ 0.629s]
writing 'cache'...
OKAY [ 1.029s]
rebooting...
finished. total time: 114.872s
Press any key to exit...
Now when the phone restarted I get the android and gear, it stays on for about 2 minutes and reboots and does the same thing again. Boot loop again.
Just do factory reset from stock recovery.
varuntis1993 said:
Just do factory reset from stock recovery.
Click to expand...
Click to collapse
When I go into recovery I get the same thing now. Sigh
workonyou said:
When I go into recovery I get the same thing now. Sigh
Click to expand...
Click to collapse
You mean those same cache errors?
varuntis1993 said:
You mean those same cache errors?
Click to expand...
Click to collapse
No I get the android with the gear just spinning.
workonyou said:
No I get the android with the gear just spinning.
Click to expand...
Click to collapse
Sorry mate, I am out of ideas now. Hope @abaaaabbbb63 or someone else can help you.
varuntis1993 said:
Sorry mate, I am out of ideas now. Hope @abaaaabbbb63 or someone else can help you.
Click to expand...
Click to collapse
Darn. Thanks for trying. Really appreciate it. I did the oem unlock again and it's still hanging.
C:\Users\brad\Desktop\hammerhead-ktu84p-factory-35ea0277\hammerhead-ktu84p>fastb
oot oem unlock
...
Is what I get and the phone says erasing.... Going to leave it for 2hrs+ this time.
If anyone has more ideas please let me know!
workonyou said:
Darn. Thanks for trying. Really appreciate it. I did the oem unlock again and it's still hanging.
C:\Users\brad\Desktop\hammerhead-ktu84p-factory-35ea0277\hammerhead-ktu84p>fastb
oot oem unlock
...
Is what I get and the phone says erasing.... Going to leave it for 2hrs+ this time.
If anyone has more ideas please let me know!
Click to expand...
Click to collapse
Just came to my mind, how about flashing custom recovery, flash twrp, check how much internal storage it shows. If its 0MB.
Then try this
http://forum.xda-developers.com/google-nexus-5/general/guide-to-fix-persist-partition-t2821576
Also how much time are u waiting for it to boot?
Hi, my phone model is Moto G (XT1032), after some mistakes I stuck in this situation. I can only boot to TWRP. I can boot, but I cannot flash it.
If I try to flash TWRP I get this error message:
fastboot flash recovery twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (9488 KB)...
OKAY [ 5.339s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 10.406s
Click to expand...
Click to collapse
If I try to erase recovery partition I get this message:
fastboot erase recovery
erasing 'recovery'...
(bootloader) Erase allowed in unlocked state
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 10.038s
Click to expand...
Click to collapse
When I boot in TWRP I cannot push ROM file to phone via adb.
When I try to boot CWM I get this error:
fastboot boot cmd.img
downloading 'boot.img'...
OKAY [ 5.321s]
booting...
FAILED (remote failure)
finished. total time: 15.389s
Click to expand...
Click to collapse
Any advice? Pls...
Looks like a MMC hardware fault. Boot TWRP and run "adb shell dmesg > dmesg.txt", search for mmc error messages or post the file to verify.
_that said:
Looks like a MMC hardware fault. Boot TWRP and run "adb shell dmesg > dmesg.txt", search for mmc error messages or post the file to verify.
Click to expand...
Click to collapse
Thank you for the reply. Here is the file.
Some update. I can push .img file to /sdcard/. But when I try to install via TWRP I get this messages:
Update process ended with signal: 9
Error installing zip file '/sdcard/name_of_the_file'
Updating partition details...
Failed to mount '/cache' (Invalid argument)
Failed to mount '/data' (Invalid argument)
Failed to mount '/fsg' (Invalid argument)
Failed to mount '/firmware' (Invalid argument)
Failed to mount '/persist' (Invalid argument)
Failed to mount '/system' (Invalid argument)
Failed to mount '/pds' (Invalid argument)
...done
Unable to mount storage
Click to expand...
Click to collapse
I am in a boot loop like when at blue honor logo like and goes back to your device is unlocked. I try to install img the update.zip and...Full SELinux support is present.
MTP Enabled
Installing zip file 'external_sd/update.zip'
Checking for MD5 files...
Skipping MD5 check: no MD5 file found
Removing uneeded files...
Patching system files...
Removing empty directorys...
Unpacking new files...
add link type file...
write radio image...
32K crc checked failure
E: unknown command [errno]
E: unknown command [errno]
update_huawei_pkg_from_ota_zip: update package from
zip failed
Updater process ended with ERROR: 7
Error installing zip file '/external_sd/update.zip'
Updating partion details...
Failed to mount '/system' (Invalid argument)
Failed to mount '/vendor' (Invalid argument)
Failed to mount '/product' (Invalid argument)
...doneSo what do I do to get it to work again? I have access to erecovery and twrp and fastboot and adb.
This is if I try to flash stock,
C:\Users\User\Desktop\New folder (3)>fastboot flash recovery boot.img
target reported max download size of 471859200 bytes
sending 'recovery' (15462 KB)...
OKAY [ 0.390s]
writing 'recovery'...
OKAY [ 0.221s]
finished. total time: 0.617s
C:\Users\User\Desktop\New folder (3)>fastboot flash recovery cust.img
target reported max download size of 471859200 bytes
sending 'recovery' (259081 KB)...
OKAY [ 6.480s]
writing 'recovery'...
FAILED (remote: partition error)
finished. total time: 6.511s
C:\Users\User\Desktop\New folder (3)>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (36996 KB)...
OKAY [ 0.926s]
writing 'recovery'...
OKAY [ 0.870s]
finished. total time: 1.802s
C:\Users\User\Desktop\New folder (3)>fastboot flash recovery system.img
target reported max download size of 471859200 bytes
sending sparse 'recovery' (425232 KB)...
OKAY [ 18.655s]
writing 'recovery'...
FAILED (remote: partition error)
finished. total time: 18.700s
Johnsonn3 said:
I am in a boot loop like when at blue honor logo like and goes back to your device is unlocked. I try to install img the update.zip and...
Full SELinux support is present.
MTP Enabled
Installing zip file 'external_sd/update.zip'
Checking for MD5 files...
Skipping MD5 check: no MD5 file found
Removing uneeded files...
Patching system files...
Removing empty directorys...
Unpacking new files...
add link type file...
write radio image...
32K crc checked failure
E: unknown command [errno]
E: unknown command [errno]
update_huawei_pkg_from_ota_zip: update package from
zip failed
Updater process ended with ERROR: 7
Error installing zip file '/external_sd/update.zip'
Updating partion details...
Failed to mount '/system' (Invalid argument)
Failed to mount '/vendor' (Invalid argument)
Failed to mount '/product' (Invalid argument)
...doneSo what do I do to get it to work again? I have access to erecovery and twrp and fastboot and adb.
This is if I try to flash stock,
C:\Users\User\Desktop\New folder (3)>fastboot flash recovery boot.img
target reported max download size of 471859200 bytes
sending 'recovery' (15462 KB)...
OKAY [ 0.390s]
writing 'recovery'...
OKAY [ 0.221s]
finished. total time: 0.617s
C:\Users\User\Desktop\New folder (3)>fastboot flash recovery cust.img
target reported max download size of 471859200 bytes
sending 'recovery' (259081 KB)...
OKAY [ 6.480s]
writing 'recovery'...
FAILED (remote: partition error)
finished. total time: 6.511s
C:\Users\User\Desktop\New folder (3)>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (36996 KB)...
OKAY [ 0.926s]
writing 'recovery'...
OKAY [ 0.870s]
finished. total time: 1.802s
C:\Users\User\Desktop\New folder (3)>fastboot flash recovery system.img
target reported max download size of 471859200 bytes
sending sparse 'recovery' (425232 KB)...
OKAY [ 18.655s]
writing 'recovery'...
FAILED (remote: partition error)
finished. total time: 18.700s
Click to expand...
Click to collapse
Am sorry to see u messing up with partitions .
For flashing system.img u should follow this command
Fastboot flash system system.img
For recovery
Fastboot flash boot boot.img
For boot
Fastboot flash boot boot.img
And for cust
fastboot flash cust cust.img
U tried to flash all files in recovery partition..
Recovery is limited to just 256mb u cant flash any other file more than 256mb.
And finally. U cant flash into system cust and data partitions through fastboot .
Only way is to make a zip and flash the files through twrp.
adriansticoid said:
Your phone was somewhat close to salvation until you did rm rf / now it's completely obliterated.
Mine is 5 months now. Happily using RR 5.8.3
Click to expand...
Click to collapse
Hi. I am in a similar situation. What should I do to recover it?
Hey everyone, I just did a clean-up of this thread. Let's please remember to keep things civil and keep our language appropriate for everyone.