Database Develop

Can access fastboot and Recovery, but cannot flash anything

Hello and greetings from germany,
I have a problem with my Moto G 2014 XT1068. I'm coming from rooted stock KitKat (Xposed) with open bootloader and TWRP 2.8.6.0. Everything seemed fine until yesterday, when the phone just went off (0% battery) and stayed at boot animation.
I've tried a lot of things, but the phone seems to be hardbricked:
- I can access recovery, but restoring does "FAIL" (restoring boot partition works, though). Restoring "system" aborts at about 18%, "data" immediately.
- I can access the phone through fastboot, but cannot flash anything. Whatever I do, the phone isn't changed. Tried reverting to stock (getting error when flashing gpt.bin, everything else seemed to work without errors, but no changes), tested flashing other recoveries (partition size mismatch, but that seems to be normal, whatever I flash, it keeps being TWRP 2.8.6.0), or even upgrade the bootloader (no errors reported at all, but no changes made to the phone).
- I can access the phone by MTP from TWRP, but cannot write to or delete anything from the internal SD.
Do you have any further ideas or is it an hardbrick?
Thanks in advance
René

Seems like the internal SD card is damaged, or there's a faulty partition table. Have you tried repairing and formatting /system and /data partitions with TWRP? Does it read external sd cards? If yes you could try flashing CM11 (because lollipop roms need an updated bootloader) from an external sdcard and see what happens. Also your backup could be corrupted, that's why it doesn't let you restore it at all.
As for the recovery, try updating your twrp to the latest version available (3.0). You can update twrp from twrp itself, just to see if it's fastboot's fault.

Wiped /system and /data. Didn't help. Wiping /data/media led to an error.
Is there anything beyond "wipe" to repair and format those partitions?
Thanks for the hints, will try updating TWRP and installing 11 this weekend, as external SDs can be accessed.
Greetings from Germany
René

*SOLVED*Mounting error after wiping /data,/cache and /system via twrp on my z3c d5803

This problem has been solved by @Didgesteve
Thank you very much, Didgesteve!
For everyone who is a genius(like me), read his post.
Hi Community,
short story: my device seems kind'a bricked, because i am not able to install a rom via twrp; error: unable to mount /data /cache and /system.
What I did:
I unlocked my bootloader via the official sony method > everything worked flawlessly
I bootet my device into fastboot mode and flashed twrp onto it > everything still workes fine
I wiped /data /cache and /system according to the normal cm13.0 installation process > still finr
I installed the cm13.zip from an external sd-card > no errors
I installed the gapps.zip from the sd-card > Nothing unusual
I booted into cm13, configured it and installed some apps > works as usual
I noticed that a new version of the rom was published, so I booted into twrp > worked
I wiped /data /cache and /system > worked
I reallized, that i could flash my external sd-card, too because i wanted to install the new cm13-version via adb-sideload > now the errors came in
So i thougt retrying wiping /data /cache and /system and the same errors occured > holy sh*t
Last I tried simply installing the cm13.zip from the external sd-card > same errors
What the errors are for wiping(those for install are basically the same:
Code:
could not mount /data and unable to find crypto footer
failed to mount /data (no such device)
Unable to recreate /data/media folder
Failed to mount /system (Invalid argument)
Failed to mount /cache (Invalid argument)
Unable to mount storage
Same goes for using the official cyanogen recovery and other cyanogenmod versions.
I am also not able to find/mount it via adb shell.
The images, etc:
CM13: http://forum.xda-developers.com/z3-compact/development/rom-cm13-t3277402/page7 version by @nelvinchi on 25th February 2016, 12:39 PM
TWRP: https://twrp.me/devices/sonyxperiaz3compact.html
Gapps: https://www.androidfilehost.com/?fid=24269982087021755
Additional information:
OS: Mac OSX El Capitan and Linux Mint 17.3
Sd-Card: SanDisk Ultra 64GB micro sdxc
Phone: Sony Xperia Z3 Compact D5803 (colorrange)
My ideas for fixing this:
-manually adding the partitions via adb shell
+required: correct partiton table and adb commands
+don't now, if this would work
Hope i didn't miss anything and there is someone out there, how can help me,
yours sincerely,
Niggl

Well I followed your method up to step 8 and the point of wiping system in recovery mode. Even if you were flashing a completely different rom, you shouldn't have to touch system unless you're coming from LL to CM for the first time. Updating roms to a later version should only require a wipe of dalvik/cache. By the sound of it there are no system files for it to boot into, either that or the partition tables are corrupt.
Have you got flashtool working? Have you tried pushing a stock tft? to see if you can repair it?
There is Sony Bridge, which if it does the same as the PC version will repair the phone to stock, as long as you can still get into Flashmode.
The chances of being able to repair it back into CM are slim, I suspect you're going to have to start from scratch, get stock working then go back to CM after.

**SOLVED**
Thank you for your help!
Didgesteve said:
Well I followed your method up to step 8 and the point of wiping system in recovery mode. Even if you were flashing a completely different rom, you shouldn't have to touch system unless you're coming from LL to CM for the first time. Updating roms to a later version should only require a wipe of dalvik/cache. By the sound of it there are no system files for it to boot into, either that or the partition tables are corrupt.
Click to expand...
Click to collapse
The partition tables were(because of bull**** or something like that) corrupted(I checked it: not because of the wiping, but i will not wipe /system at an update in the future)
Didgesteve said:
There is Sony Bridge, which if it does the same as the PC version will repair the phone to stock, as long as you can still get into Flashmode.
Click to expand...
Click to collapse
I can boot into recovery and fastboot/flash mode.
Xperia companion and sony bridge are both not working because of "modified software".
Flashtool worked for the stock tft.
So THANK YOU VERY MUCH,
you are my savior!
I hope nobody else, will be a genius like me
Thx again,
Niggl1999

[HELP PLEASE] NEED HELP WITH make_ext4fs

Hello. So i have a S3 LTE with possibly(?) an insane eMMC. Long story short: phone bought back in dec 2012. Changed battery twice. Last battery started acting up, lost all power, next thing i know phone is in permanent bootloop. Odin won't repartition the phone (idk why) nor can it flash a full firmware, getting stuck on SYSYEM flash, but can flsh recoveries. After fiddling around with recoveries, i finally flashed TWRP. What i found out : /cache, /system, /data, /sdcard and /tombstones couldn't be mounted (invalid argument). After wiping everything with make_ext4fs, everything works fine, except for /tombstones, which can't be mounted. What i have seen from the logs is that twrp doesn't wipe /tombstones as well, so there was no way of getting it to work.
Full story here http://forum.xda-developers.com/galaxy-s3/help-i9305/i9305-bootloop-mount-data-sdcard-t3379377
WHAT MY PROBLEM IS:
I need somebody to tell me the parameters for make_ext4fs in order to wipe /tombstones as well, as it seemed to work flawlessly with the other folders.
UPDATE: I managed to wipe /dev/block/mmcblk0p11, which mounts in /tombstones. used rm -fr, then mkdir for the tombstones folder. Everything mounts just fine now. Will reflash and post an update.
UPDATE 2: Phone still won't work with odin. i flashed amcha with twrp. Boots just fine, but 10 seconds after boot finishes, phone freezes and won't respond to button presses. Any ideas?

Huawei p9 format Data from ext4 to f2fs fail

hi
i have a problem with formatting Data in twrp recovery on huawei P9 eva-L09C432B182
https://dl.dropboxusercontent.com/u/67361401/IMG_20170309_174811.jpg
ive tried this ROM:
https://forum.xda-developers.com/p9/development/rom-huawei-p9-newworld-7-tecalote-t3543296
and it installs, but i get message after boot:
https://dl.dropboxusercontent.com/u/67361401/IMG_20170309_180017.jpg
i can actually see navi bar for a sec and volume buttons still work(can set alarm and sound loudness)
and here is install image of Rom:
https://dl.dropboxusercontent.com/u/67361401/IMG_20170309_175844.jpg
only error is mount: failed to mount /dev/block/dm-0 at /dat: No such file or directory
so i can only use twrp recovery and fastboot to fix this.
mkfs.f2fs -t 0 /dev/block/mmcblk0p42 process ended with error: 255
unable to wipe Data.
error changing file system.
every other is good for format(System and Cache) to f2fs and ext4 just Data folder has problem with format but wipe works :crying:

Are you using the last version of TWRP? Twrp 3.0.3.0

henryco11 said:
Are you using the last version of TWRP? Twrp 3.0.3.0
Click to expand...
Click to collapse
no i use 3.0.2.0
i think 3.0.3.0 is only for updated huwei with nougat and EMUI5?

Why you decrypted it?
It should work normal after you reset it.

dkionline said:
Why you decrypted it?
It should work normal after you reset it.
Click to expand...
Click to collapse
reset what excatly? factory reset works but Data is in ext4 format. i can wipe it but cant format it.
what if i erase this mmblck0p42 file and then flash twrp in fastboot will the file be reinstalled or will it be after i flash ROM in recovery again?
i made a mistake by formatting it in first place from f2fs to ext4 but before even factory reset didnt work, now it works and only think is left is this encryption error.

jure482 said:
hi
i have a problem with formatting Data in twrp recovery on huawei P9 eva-L09C432B182
https://dl.dropboxusercontent.com/u/67361401/IMG_20170309_174811.jpg
ive tried this ROM:
https://forum.xda-developers.com/p9/development/rom-huawei-p9-newworld-7-tecalote-t3543296
and it installs, but i get message after boot:
https://dl.dropboxusercontent.com/u/67361401/IMG_20170309_180017.jpg
i can actually see navi bar for a sec and volume buttons still work(can set alarm and sound loudness)
and here is install image of Rom:
https://dl.dropboxusercontent.com/u/67361401/IMG_20170309_175844.jpg
only error is mount: failed to mount /dev/block/dm-0 at /dat: No such file or directory
so i can only use twrp recovery and fastboot to fix this.
mkfs.f2fs -t 0 /dev/block/mmcblk0p42 process ended with error: 255
unable to wipe Data.
error changing file system.
every other is good for format(System and Cache) to f2fs and ext4 just Data folder has problem with format but wipe works :crying:
Click to expand...
Click to collapse
Why is your data partition ext4?
Normally it is on each p9 device f2fs.
This can only occur if you were on Nougat between and had installed the TWRP-n which has no Decryption Support and if you had by yourself formated data with this TWRP to ext4.
To install NewWorld Rom you must be on Marshmallow Firmware (because of Android 6 Bootloader) and your data partition must be f2fs.
In the meantime there's a new TWRP for Android 7, which has already Decryption Support.
But you cannot use this TWRP for installing NewWorld. You must have the one, which I have linked in my OP.
On which Firmware or Rom have you been, before you tried to install NewWorld?
If you were on Nougat, NewWorld could not flashed, cause you must be on Marshmallow.
Please answer my questions that I can realize in which situation you are.

i have Marshmallow Firmware and yes i formatted data to ext4 myself
the problem occured when i wanted to get nougat but OTA update failed but it booted back into 6.0 normally just root didnt work so i went in TWRP and flashed supersu 2.79 which i had before, then i was stuck in bootloop, manged to get to fastboot but Hisuite says no update packeg for this phone. i flashed back stock recovery and tryed to factory reset but didnt work, flashed twrp back and factory reset then it said data format error so i went and changed it to ext4 after factory reset worked but i cant put it back to f2fs.
aldo i wiped all cache, dalvik/ARTcache, Data, internal storage and system

jure482 said:
i have Marshmallow Firmware and yes i formatted data to ext4 myself
the problem occured when i wanted to get nougat but OTA update failed but it booted back into 6.0 normally just root didnt work so i went in TWRP and flashed supersu 2.79 which i had before, then i was stuck in bootloop, manged to get to fastboot but Hisuite says no update packeg for this phone. i flashed back stock recovery and tryed to factory reset but didnt work, flashed twrp back and factory reset then it said data format error so i went and changed it to ext4 after factory reset worked but i cant put it back to f2fs.
aldo i wiped all cache, dalvik/ARTcache, Data, internal storage and system
Click to expand...
Click to collapse
Okay, you are now on Stock Marshmallow (which version?) and you maked factory reset after formatting data to ext4
Which phone EVA model to you have?
It is recommended to flash Stock Recovery with adb and flash latest official Marshmallow Full Firmware once again (downloaded and unzipped) with 3 Button (Force Update) from the folder dload on your phone (update.app and if present meta-inf must be in this folder only) Force Upgrade to Marshmallow Firmware should solve your problem (Bootloader get closed, data should be formatted to f2fs automatically)

Tecalote said:
Okay, you are now on Stock Marshmallow (which version?) and you maked factory reset after formatting data to ext4
Which phone EVA model to you have?
It is recommended to flash Stock Recovery with adb and flash latest official Marshmallow Full Firmware once again (downloaded and unzipped) with 3 Button (Force Update) from the folder dload on your phone (update.app and if present meta-inf must be in this folder only) Force Upgrade to Marshmallow Firmware should solve your problem (Bootloader get closed, data should be formatted to f2fs automatically)
Click to expand...
Click to collapse
thanks soo much i did what you said on pm. went to bootloader and flashed your twrp then wiped again arpcache, cache, system, data, reboot to twrp then installed your ROM which still said that mount dev-0 error but i still rebotted and bam it booted longer with this very nice animation you have and showed emui and now im at select language page!
Flashing your twrp in bootloader fix the problem and formatted Data to f2fs thank you again.
also i used command recovery --wipe_data --set_filesystem_encryption=off before all above to make sure ecryption is off not broken.
im now on home screen it looks nice just 3 navigation buttons on bottom look smaller then i had before, thanks again.

Formatted to exfat. Now stuck at formatting

Hey,
I was trying to unroot my phone (8.0 + Magisk beta) to go back to stock 8.0. I flashed the stock recovery but it would not boot. So I decided to follow this method. https://forum.xda-developers.com/on...ota-update-t3519074/post74716080#post74716080
However, as I flashed back TWRP (bluspark) and formatted, the /data was unable to mount. Last time that happened, I change format to ext4 and then back to f2fs. It worked fine last time although that time i was on official TWRP and on nougat...
This time the format change from ext4 to f2f2s was failing so I tried exfat.
I am now stuck at the formatting screen (for more than 40 min). The console says
Updating partition details...
...done
Formatting Data using mkexfatfs...
Done.​
The progress bar is still flashing/moving. There is no option to go back or reboot etc etc...
Should I wait it out until it completes? or can I turn off the phone. I do not want to risk bricking my device so did not turn it off yet. Was hoping it does it soon...
Any suggestions?

Force turn off the phone and then boot to TWRP again, should work fine. But format back to ext4

Why EXFAT out of all the widely more supported partitioning methods?
Reboot to TWRP and follow the same procedure, but format to EXT4.
If you want to unroot your device, just flash the Magisk uninstaller, or reinstall the ZIP. Don't flash Stock Recovery when you have Magisk or other add-ons installed.
If all fails, try the MSM tool and restore your device.