Database Info

Problem restore nandroid backup - "can't mount SDCARD:/nandroid/"

Hello, when I tried to update my Magic to a new radio something went wrong. Start-up screen freezes. Only fastboot and recovery are available.
Now, when I trie to restore my nandroid backup in recovery I get the message:
E: Can't mount /dev/block/mmcblk0
p1 (or /dev/block/mmcblk0)
(No such file or directory)
E: Can't mount SDCARD:/nandroid/
When I trie it with fastboot I get:
C:\AndroidSDK\tools>fastboot flash system system.img
sending 'system' (80002 KB)... OKAY
writing 'system'... INFOsignature checking...
FAILED (remote: signature verify fail)
C:\AndroidSDK\tools>fastboot flash boot boot.img
sending 'boot' (2560 KB)... OKAY
writing 'boot'... INFOsignature checking...
FAILED (remote: signature verify fail)
C:\AndroidSDK\tools>fastboot flash userdata data.img
sending 'userdata' (132301 KB)... OKAY
writing 'userdata'... INFOsignature checking...
FAILED (remote: signature verify fail)
I've searched everywhere for a solution for this problem, and tried everything but nothing helped. So I hope someone can help me here...
These are the specifications of my phone:
SAPPHIRE PVT 32A ENG S-ON H
HBOOT-1.33.2010 (SAP10000)
RADIO-6.35.10.18
The original radio was 3.22.20.17
I had recovery-RA-sapphire-v1.6.2H, but after my failed radio update, it rebootet after 2 seconds...so now I use recovery-RA-hero-v1.6.2 to enter my recovery. This one works, doesn't reboot, but I don't have acces to my SDcard.
Thanks for you're help!

if my memory serves me right that "new" radio is the perfect one?not sure your best to ask on the magic section

Moto G (XT1032) bricked?

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

The unsolvable bootloop [Help Request]

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

[FIXED] Factory Image Bricked My Device?

I'll start this off with the fact that my Pixel 4a is a Google Store variant and the bootloader is unlocked.
So basically I downloaded the October factory image off of Google's website with the intent of wiping my phone completely and starting fresh.
I flashed it using the flash-all script however during the install for some reason an error occurred and my 4a rebooted.
Now it apparently no longer has an OS installed and boots straight into fastboot, so all I have access to is fastboot and recovery mode.
Attempting to reflash the factory image with flash-all while in fastboot gives me the following which I have never seen before:
Code:
Sending 'bootloader' (8341 KB) FAILED (Write to device failed (no link))
fastboot: error: Command failed
Rebooting into bootloader FAILED (Write to device failed (no link))
fastboot: error: Command failed
Sending 'radio' (72372 KB) FAILED (Write to device failed (no link))
fastboot: error: Command failed
Rebooting into bootloader FAILED (Write to device failed (no link))
fastboot: error: Command failed
--------------------------------------------
getvar:version-bootloader FAILED (Write to device failed (no link))
getvar:version-baseband FAILED (Write to device failed (no link))
getvar:serialno FAILED (Write to device failed (no link))
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
getvar:product FAILED (Write to device failed (no link))
Checking 'product' FAILED
Could not getvar for 'product' (Write to device failed (no link))
fastboot: error: requirements not met!
Attempted to run "Wipe data/factory reset" in recovery mode and get the following:
Code:
-- Wiping data...
E:eek:pen failed: /metadata/ota: No such file or directory
Formatting /data...
Formatting /metadata...
Wiping Titan M...
E:can't send spi message: Try again
E:can't send spi message: Try again
E:can't send spi message: Try again
E:can't send spi message: Try again
E:can't send spi message: Try again
E:can't send spi message: Try again
E:can't send spi message: Try again
Data wipe complete.
I've done this plenty of times before with other devices and have never ran into something like this, so I really am lost on what to do.
Edit: Just tried downloading the standalone OTA file from Google and flashing that. It went smoothly until it hit 94% and then there was an error. Even with the error that was enough for it to be able to boot into the OS though and everything seems to be working fine.

Hey there. Did you ever figure out a fix for this? I had a similar thing happen to me last night. Everything is working fine but I'm worried it will eventually have consequences.

Huawei Honor 8 Unable to install any ROMs, flash IMGs, and mount specific partitions

I just realized that I probably bricked my phone while trying to install a ROM.
After failing to install the custom ROM, my phone displayed that it is unable to mount:
Failed to mount '/cust' (Invalid Argument)
Failed to mount '/vendor' (Invalid Argument)
Failed to mount '/product' (Invalid Argument)
I have tried to use TWRP to:
Change file system for all of these partitions by switching to EXT2 back to EXT4 but resulted in error messages like this:
Unable to wipe Vendor
Error changing file system
Next I tried to repair these partitions but only resulted in this error message:
Repairing Vendor using e2fsck...
/sbin/e2fsck -fp process ended with ERROR: 16
Unable to repair Vendor
I concluded that perhaps the cust, vendor, and product partitions don't exist.
I then tried to use bootloader to erase the existing partitions of cust, vendor, and product and since my device originally doesn't have a vendor, I decided to just delete and reinstall it (except for cust & product):
platform-tools> .\fastboot.exe erase vendor
Erasing 'vendor' FAILED (remote: 'Command not allowed')Erasing 'vendor'
fastboot: error: Command failed
platform-tools> .\fastboot.exe erase cust
Erasing 'cust' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
platform-tools> .\fastboot.exe flash cust .\System\CUST.img
Sending 'cust' (258509 KB) OKAY [ 6.442s]
Writing 'cust' FAILED (remote: 'partition error')
fastboot: error: Command failed
After these error messages, I tried installing another custom OS that worked previously but it seems like the phone is stuck in the "your device is currently booting" screen although the initial installation of the OS was successful in TWRP besides the error messages of:
Failed to mount '/cust' (Invalid Argument)
Failed to mount '/vendor' (Invalid Argument)
Failed to mount '/product' (Invalid Argument)
I searched online and found that I could use the dload method by having an UPDATE.APP inside a folder called dload on a SD Card which should allow your huawei phone to boot into the stock image. Unfortunately, that did absolutely nothing.
I have then tried to flash the stock BOOT.img from the UPDATE.APP through fastboot:
platform-tools> .\fastboot.exe boot .\System\BOOT.img
creating boot image...
creating boot image - 15863808 bytes
Sending 'boot.img' (15492 KB) OKAY [ 0.332s]
Booting FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
but unfortunately with no success...
I have tried connecting HiSuite with the phone in bootloader but HiSuite returned a message saying that this device isn't supported.
I have lastly tried to relock the bootloader which did nothing with the factory reset failing at ~15%.
Erecovery mode doesn't work for this phone due to a failure to get the packets as well...
Now I am just left with a phone with no OS with TWRP installed...
Are there any solutions to installing an OS on this phone to get this phone running? Thanks in advance!
Some additional information:
My phone displayed that its a FRD-L14C567 before installing a custom OS
After installing the custom OS, it displayed that my phone is a FRD-L04
Since I cannot find any free ROM for FRD-L14, I decided to use the ROM for FRD-L04C567 which are the .img files I flashed to the phone.

paulLi_01 said:
I just realized that I probably bricked my phone while trying to install a ROM.
After failing to install the custom ROM, my phone displayed that it is unable to mount:
Failed to mount '/cust' (Invalid Argument)
Failed to mount '/vendor' (Invalid Argument)
Failed to mount '/product' (Invalid Argument)
I have tried to use TWRP to:
Change file system for all of these partitions by switching to EXT2 back to EXT4 but resulted in error messages like this:
Unable to wipe Vendor
Error changing file system
Next I tried to repair these partitions but only resulted in this error message:
Repairing Vendor using e2fsck...
/sbin/e2fsck -fp process ended with ERROR: 16
Unable to repair Vendor
I concluded that perhaps the cust, vendor, and product partitions don't exist.
I then tried to use bootloader to erase the existing partitions of cust, vendor, and product and since my device originally doesn't have a vendor, I decided to just delete and reinstall it (except for cust & product):
platform-tools> .\fastboot.exe erase vendor
Erasing 'vendor' FAILED (remote: 'Command not allowed')Erasing 'vendor'
fastboot: error: Command failed
platform-tools> .\fastboot.exe erase cust
Erasing 'cust' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
platform-tools> .\fastboot.exe flash cust .\System\CUST.img
Sending 'cust' (258509 KB) OKAY [ 6.442s]
Writing 'cust' FAILED (remote: 'partition error')
fastboot: error: Command failed
After these error messages, I tried installing another custom OS that worked previously but it seems like the phone is stuck in the "your device is currently booting" screen although the initial installation of the OS was successful in TWRP besides the error messages of:
Failed to mount '/cust' (Invalid Argument)
Failed to mount '/vendor' (Invalid Argument)
Failed to mount '/product' (Invalid Argument)
I searched online and found that I could use the dload method by having an UPDATE.APP inside a folder called dload on a SD Card which should allow your huawei phone to boot into the stock image. Unfortunately, that did absolutely nothing.
I have then tried to flash the stock BOOT.img from the UPDATE.APP through fastboot:
platform-tools> .\fastboot.exe boot .\System\BOOT.img
creating boot image...
creating boot image - 15863808 bytes
Sending 'boot.img' (15492 KB) OKAY [ 0.332s]
Booting FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
but unfortunately with no success...
I have tried connecting HiSuite with the phone in bootloader but HiSuite returned a message saying that this device isn't supported.
I have lastly tried to relock the bootloader which did nothing with the factory reset failing at ~15%.
Erecovery mode doesn't work for this phone due to a failure to get the packets as well...
Now I am just left with a phone with no OS with TWRP installed...
Are there any solutions to installing an OS on this phone to get this phone running? Thanks in advance!
Some additional information:
My phone displayed that its a FRD-L14C567 before installing a custom OS
After installing the custom OS, it displayed that my phone is a FRD-L04
Since I cannot find any free ROM for FRD-L14, I decided to use the ROM for FRD-L04C567 which are the .img files I flashed to the phone.
Click to expand...
Click to collapse
Unlock bootloader with PotatoNV or DC Unlocker or DC Phoenix
then u will allowed commands.

sircamot said:
Unlock bootloader with PotatoNV or DC Unlocker or DC Phoenix
then u will allowed commands.
Click to expand...
Click to collapse
Yes, I have already done that! Unfortunately, I believe that these commands requires root access which I have tried installing super SU with which did not help with my problem...
I have already bought a new phone since there are no official huawei repair centers in the US with the Canada one not supporting repairs on this huawei honor 8 international model. However, fixing it would be nice though...
In addition, I have tried installing Havoc OS for hopes to have the partitions rewritten for android 9 but it didn't help at all

Really used DC Phoenix? this tool will rewrite all phone firm to DC Original firmware like OFW
after all, unlock bootloader in phone's setting, now again DC Phoenix, choose Update by TP,
check Load and temporally unclock boot loader, select ur cpu at bootloader files, and press Do job
(Maybe Kirin650 will success after all)
now, u can use PotatoNV and make ur bootloader unlock num
then open windows powershell, enter like this
fastboot oem unlock numbers (PotatoNV generated)
u know? u already can use fastboot command at this time but wait patiently
next, push vol+ buttom to toggle bootloader unclock and push power to comfirm.
ur phone will reboot and initialize user data
again enter bootloader mode and open DC Phoenix
check Load and temporally unclock boot loader, select ur cpu at bootloader files, and press Do job
now u can use fastboot commands
Note: this method means reflesh ur phone at all so of course ur root should lost
u need to flash TWRP and super su after all again

sircamot said:
Really used DC Phoenix? this tool will rewrite all phone firm to DC Original firmware like OFW
after all, unlock bootloader in phone's setting, now again DC Phoenix, choose Update by TP,
check Load and temporally unclock boot loader, select ur cpu at bootloader files, and press Do job
(Maybe Kirin650 will success after all)
now, u can use PotatoNV and make ur bootloader unlock num
then open windows powershell, enter like this
fastboot oem unlock numbers (PotatoNV generated)
u know? u already can use fastboot command at this time but wait patiently
next, push vol+ buttom to toggle bootloader unclock and push power to comfirm.
ur phone will reboot and initialize user data
again enter bootloader mode and open DC Phoenix
check Load and temporally unclock boot loader, select ur cpu at bootloader files, and press Do job
now u can use fastboot commands
Note: this method means reflesh ur phone at all so of course ur root should lost
u need to flash TWRP and super su after all again
Click to expand...
Click to collapse
I haven't used DC Pheonix. I can try it right now! Thanks!

paulLi_01 said:
I haven't used DC Pheonix. I can try it right now! Thanks!
Click to expand...
Click to collapse
Welcome, cheers!