Database Users

Bricked? can't mount sdcard

tried a new rom, wiped, flashed, rebooted then it had sdcard mount problems thought it was the rom so i wiped and then tried to flash with no luck it says
build: RA-sapphire-v1.5.2H
E:Can't mount /dev/block/mmcblk0p1 (or dev/block/mmblk0)
(No such file or directory)
E:Can't mount SDCARD
Boots RA-sapphire-v1.5.2H and fastboot just fine
SAPPHIRE PVT 32A
HBOOT-1.33.2010 (SAPP10000)
CPLD-12
RADIO-3.22.20.17
So can't flash any new roms...
is the phone bricked?
Really need some help here i'm stuck

It´s no bricked dude. Try remove ur sdcard and insert again.
Good luck.

Allready tried that and tried several sdcards, all cards worked before and is working on the pc

Try enable sdcard via usb toggle in RA-recovery. Insert usb cable into phone and pc. Check if your pc recognize your sdcard.

Tried to enable USB-MS no luck in windows

Try clicking the flash button a whole bunch of times, sometimes it just takes a while; I've only seen this on the hero recovery, though.

also tried that

Sorry to hear that.
So can't flash any new roms...
is the phone bricked?
Really need some help here i'm stuck
Click to expand...
Click to collapse
If it's any consolation, you're not bricked! You can install everything using fastboot, you'll have to scour the forums or google, but you should be able to find the instructions to flash an install this way. Generically it will be something like:
Code:
./fastboot erase system -w
./fastboot flash boot ./misc/boot.img
./fastboot flash system ./misc/system.img
./fastboot flash userdata ./misc/userdata.img
Sorry, I can't provide more details, right now.

Btw an actual brick is when you can't even fastboot or get into recovery.
Far as the SD card have you tried to format it with a PC via a card reader?

Searched alot if anyone could provide a link it would be great, sound good that i'm not bricked!!!
tried to format 2 different cards on the pc

did you make a nandroid backup before you flashed the new rom? if so then y not try and load the backup.

Should be same if another rom or nandroid backup through fastboot?

1) Go into fastboot
2) fastboot erase system -w (do it about 5 times in a row.)
3) Completely power down your phone. (battery out, wait)
4) Go into fastboot.
5) Repeat number 2.
6) Complete power down. (remove battery).
7) Boot into recovery.
8) Test sdcard.
Follow these steps exactly and it might work.
I had this same problem from a bad flash.
Hope it works for you.

Still nothing
TigerTael said:
1) Go into fastboot
2) fastboot erase system -w (do it about 5 times in a row.)
3) Completely power down your phone. (battery out, wait)
4) Go into fastboot.
5) Repeat number 2.
6) Complete power down. (remove battery).
7) Boot into recovery.
8) Test sdcard.
Follow these steps exactly and it might work.
I had this same problem from a bad flash.
Hope it works for you.
Click to expand...
Click to collapse

Okay,
My situation, after a bad flash (which I did not actually know was a bad flash), my SDcard reader in my phone would not read an SDcard at all. It would detect that one had been inserted, but acted as if nothing was there.
Also, my hboot showed that my bootloader was now 'S-ON' and not 'S-OFF'.
I was getting denied remote flash commands and everything.
After numerous wipes via recovery and then numerous wipes in fastboot, eventually one of the fastboot wipes fixed the problem.
I'm not 100% sure if it was a combination of erasing and then flashing a new ROM to system (via fastboot, not recovery) or what, but eventually my bootloader changed back to 'S-off' (What it always was for me) and then my SDcard could be read in the phone.
The key here was fastboot/hboot, and not recovery.

how did you flash a rom with fastboot? and which one?
S-ON is there in fastboot/hboot
also tried my nandroid backup with fastboot it says FAILED (remote: signature verify fail)
¤#"%¤#¤

Cronner said:
how did you flash a rom with fastboot? and which one?
S-ON is there in fastboot/hboot
Click to expand...
Click to collapse
In the "Rogers Mandatory Update" thread, post #139, there are clear instructions on flashing the stock Rogers ROM. I'm not suggesting you do this, though, I doubt you want the new radio, just use this as an example and search around for the files that are appropriate for what you want.
But really, I'd only resort to this to get the phone to boot and to try formatting the SD card.
Can you use adb to log into the phone?
Also, correct me if I'm wrong, but doesn't S-ON and S-OFF just indicate if the phone's locked to a carrier?

Solimian said:
In the "Rogers Mandatory Update" thread, post #139, there are clear instructions on flashing the stock Rogers ROM. I'm not suggesting you do this, though, I doubt you want the new radio, just use this as an example and search around for the files that are appropriate for what you want.
But really, I'd only resort to this to get the phone to boot and to try formatting the SD card.
Can you use adb to log into the phone?
Also, correct me if I'm wrong, but doesn't S-ON and S-OFF just indicate if the phone's locked to a carrier?
Click to expand...
Click to collapse
S-ON stands for security on, S-OFF, off. It's not locking to a carrier, but merely a security setting for the phone itself. There's a thread about it somewhere.
I don't think this has anything to do with formatting. As long as the SDcard can be read in another device such as a computer fine, I am still siding with the idea that it was a bad flash. I spent a day stressing that my SDcard reader on my phone was borked and now I would be screwed. Amon_Ra was there to offer support, but at the end of the day, after several wipes, the fastboot erase eventually got it to come right.
Amon_Ra and I summarised that somewhere a byte or a few bytes got written where it shouldn't have and corrupted some base code somewhere.

Solimian > is something wrong with the new radio?
yes adb and fastboot works now...
adb shell also works but can't mount sdcard there either!
C:\android>fastboot flash hboot hboot-1.76.2007.img
sending 'hboot' (512 KB)... OKAY
writing 'hboot'... INFOsignature checking...
FAILED (remote: signature verify fail)
also tried: adb shell mount /sdcard
mount: mounting /dev/block/mmcblk0p1 on /sdcard failed: No such file or directory
and:
adb shell
/ # mount -a
mount -a
mount: mounting /dev/block/mmcblk0p1 on /sdcard failed: No such file or directory
mount: mounting /dev/block/mmcblk0p2 on /system/sd failed: No such file or directory

TigerTael
TigerTael Please remind what you do, i have same problem

Can't mount cache... can't change droidboot and recovery

hello xda community
I made sure to try everything (or almost) before post here
my ZenFone 5 show a message that it cannot mount the cache partition and I am stuck on the Asus logo (I can access droidboot and recovery but I cannot replace them)
factory reset and cache wipe does not make any change (they return the same "can't mount cache" error.
I am trying to change the current droidboot and recovery to fastboot and TWRP but not matter how much I flash them, it does not take change (yes, I am unlocking the bootloader)
I am also executing a script to get the original partitions table back but when sec_offline_update_image.cmd executes the command "fastboot oem partition /tmp/partition.tbl" I get the error "FAILED(remote: GPT command failed)"
as this came out of thin air, I didnt have the chance to activate developer mode on my phone
I starting to get concerned .... any help?
thnk you very much in advance

@dgadelha any help ?

What are the specs of your Zen 5?

dgadelha said:
What are the specs of your Zen 5?
Click to expand...
Click to collapse
ZenFone 5 - A501CG T00J
Serial # with 0123456789ABCDEF issue
Box info: A501CG2 / A501CG-1F589 / CPU Intel Clover Trail Plus + Dual Core 1.6 Ghz, Purple, 8GB RAM
I already checked basically all links on Google related to the above issues (4 days Googling it already).
I really don't know what to do anymore.

A little more context @dgadelha.
2 months ago, I unlocked my bootloader for the 1st time and installed BlueLight 3.24.40.87... after the installation I locked my bootloader again using the boot, recovery and droidboot images contained in UL-ASUS_T00F-TW-3.24.40.87-user (Asus' official).
BlueLight worked fine with minor bugs for 2 months until past week when it suddenly started to crash a LOT, get slow and overheat (I didn't had time to fix it).
Then suddenly, all Android services and apps on the phone crashed and the phone turned off entering in a bootloop (Asus logo) everytime I reboot.
Since then I am getting the "E:Failed to mount /cache (Invalid argument)" issue when loading the recovery mode.
Since then I am also not being able to flash anything on my phone... no different recovery, no other fastboot and no other image... I get success messages on the flash process but nothing changes after restart (I can still access droidboot and recovery but nothing works there as the "Failed to mount /cache" error pops up for any action I try... recovery mode shows version 3.24.40.87_201).
When I try a system image via adb sideload I get error "Total xfer: 0.00x".
When I try "sec_offline_update_image.cmd" I get an error on the command "fastboot oem partition /tmp/partition.tbl"... the error is "FAILED(remote: GPT command failed)".
I have tried 2 different "partition.tbl" files... one that contains the "spare" partition and another one that contains "misc" instead... both failed.
I am now currently trying xFSTK (I don't even know what this does on my phone) and ASUS Flash Tool... ASUS Flash Tool returns "Flash image failure (FAILED (remote: GPT command failed))".
PS: I forgot to activate developer mode and other related options before the crash.
I hope that my phone is somehow alive... btw, thank you very much in advance!!!

jaabax said:
A little more context @dgadelha.
2 months ago, I unlocked my bootloader for the 1st time and installed BlueLight 3.24.40.87... after the installation I locked my bootloader again using the boot, recovery and droidboot images contained in UL-ASUS_T00F-TW-3.24.40.87-user (Asus' official).
BlueLight worked fine with minor bugs for 2 months until past week when it suddenly started to crash a LOT, get slow and overheat (I didn't had time to fix it).
Then suddenly, all Android services and apps on the phone crashed and the phone turned off entering in a bootloop (Asus logo) everytime I reboot.
Since then I am getting the "E:Failed to mount /cache (Invalid argument)" issue when loading the recovery mode.
Since then I am also not being able to flash anything on my phone... no different recovery, no other fastboot and no other image... I get success messages on the flash process but nothing changes after restart (I can still access droidboot and recovery but nothing works there as the "Failed to mount /cache" error pops up for any action I try... recovery mode shows version 3.24.40.87_201).
When I try a system image via adb sideload I get error "Total xfer: 0.00x".
When I try "sec_offline_update_image.cmd" I get an error on the command "fastboot oem partition /tmp/partition.tbl"... the error is "FAILED(remote: GPT command failed)".
I have tried 2 different "partition.tbl" files... one that contains the "spare" partition and another one that contains "misc" instead... both failed.
I am now currently trying xFSTK (I don't even know what this does on my phone) and ASUS Flash Tool... ASUS Flash Tool returns "Flash image failure (FAILED (remote: GPT command failed))".
PS: I forgot to activate developer mode and other related options before the crash.
I hope that my phone is somehow alive... btw, thank you very much in advance!!!
Click to expand...
Click to collapse
Hi,
Did you have any kernel mods when using BlueLight?
Sorry but I don't know if it had a custom kernel, but a custom one could have lead a storage drive crash.
Also, xFSTK will just attempt to restore your droidboot and dnx/ifwi, not the partition table or w.e.
Maybe you could try extracting the Jelly Bean RAW file with 7-Zip, flash the droidboot signed image (should be like, fastboot flash fastboot file.img, or fastboot flash droidboot file.img), the droidboot signed image name might be something like droidboot.signed_POS.bin (it's an img file too, but with a bin extension).
After flashing that droidboot image, reboot your bootloader and try running the sec_offline_image_update.cmd again.
I wish I had Zenfone Assist active yet, but had to take down it.
Thanks

Hey jaabax, were you able to fix your device ?

Hi @vikrammarkiv.
Sorry for the big delay in response... I am not using this e-mail anymore and I quit fixing my phone.
Unfortunately I could not fix it and I ended up buying another phone.
Could you fix it?
Sorry again and hope you fixed it.
Best regards.

same issue, anyone got any update on fix?

jaabax said:
A little more context @dgadelha.
2 months ago, I unlocked my bootloader for the 1st time and installed BlueLight 3.24.40.87... after the installation I locked my bootloader again using the boot, recovery and droidboot images contained in UL-ASUS_T00F-TW-3.24.40.87-user (Asus' official).
BlueLight worked fine with minor bugs for 2 months until past week when it suddenly started to crash a LOT, get slow and overheat (I didn't had time to fix it).
Then suddenly, all Android services and apps on the phone crashed and the phone turned off entering in a bootloop (Asus logo) everytime I reboot.
Since then I am getting the "E:Failed to mount /cache (Invalid argument)" issue when loading the recovery mode.
Since then I am also not being able to flash anything on my phone... no different recovery, no other fastboot and no other image... I get success messages on the flash process but nothing changes after restart (I can still access droidboot and recovery but nothing works there as the "Failed to mount /cache" error pops up for any action I try... recovery mode shows version 3.24.40.87_201).
When I try a system image via adb sideload I get error "Total xfer: 0.00x".
When I try "sec_offline_update_image.cmd" I get an error on the command "fastboot oem partition /tmp/partition.tbl"... the error is "FAILED(remote: GPT command failed)".
I have tried 2 different "partition.tbl" files... one that contains the "spare" partition and another one that contains "misc" instead... both failed.
I am now currently trying xFSTK (I don't even know what this does on my phone) and ASUS Flash Tool... ASUS Flash Tool returns "Flash image failure (FAILED (remote: GPT command failed))".
PS: I forgot to activate developer mode and other related options before the crash.
I hope that my phone is somehow alive... btw, thank you very much in advance!!!
Click to expand...
Click to collapse
Same problem, only fastboot and GPT failed (Asus zenfone 2 ze551ml). No solution

Exactly the same problem. It appears there are no fixes. How did the xf... thingy go?

Оh man.. I have the same issue, and can't fix it...

Phone is not encrypted but Android and TWRP say it is. [Solved]

SOLVED:
In TWRP I went WIPE > FORMAT DATA
The format failed with error 255 (with many more errors relating to encryption and mounting of /data) and /data would no longer mount
Noticed that the failed format had changed the file system of /data from ext4 to f2fs
Used WIPE > ADVANCED WIPE > REPAIR OR CHANGE FILE SYSTEM to change /data back to ext4
Bob's your uncle
Original issue:
Currently my device is fully functional except that in Android settings under "Security" it indicates that my phone is encrypted. When booting TWRP the console says:
Code:
Data successfully decrypted, new block device: '/dev/block/dm-0'
Updating partition details...
...done
Successfully decrypted with default password.
Updating partition details...
...done
Full SELinux support is present.
MTP Enabled
Here's how I got here:
-Device arrived yesterday with B29 installed
-Took official OTA to B15
-Unlocked bootloader using the Axon7Toolkit (flashes the unlock EDL file via MiFlash and issues a "fastboot oem unlock" command)
-Flashed TWRP 3.1.1-0 via "fastboot flash" command
-Flashed B19 bootstack and system from post #4 of this thread: https://forum.xda-developers.com/axon-7/development/bad-boyz-zte-axon-7-rom-m-magisk-root-t3543201 (in preparation for Bad Boyz ROM)
-TWRP reported that no OS was installed when attempting to reboot system. Tried to boot system anyways. No boot. Reflashed the above mentioned B19 system. Same as before, no boot.
-Flashed stock recovery
-Used the update.zip file provided by ZTE to flash B19 in stock recovery
-Tried to reboot to fastboot so I could flash TWRP. It just rebooted after selecting the fastboot option.
-Used the test adb and fastboot option in Axon7Toolkit. Toolkit told me that access to fastboot may be locked out due to an incorrect partition flag. It suggested that I use the bootloader unlock option. I followed the prompts again and used MiFlash to flash that EDL file that enables certain fastboot commands. Instead of continuing the bootloader unlock process in the Toolkit (which would have issued a 'fastboot oem unlock' command) I exited the toolkit after flashing the EDL file.
-Flashing that EDL file did enable me to boot to fastboot. However when I booted the system I was asked for a PIN to decrypt data. When I rebooted to TWRP I was asked for a PIN as well.
-Used the "Restore to stock" option in Axon7Toolkit (flashed the full B19 EDL via MiFlash)
-Device now boots both recovery and the system without asking for a PIN. However, as mentioned above, both Android and TWRP say the device is encrypted. (this is the current state of the device)
I'm not sure that this adversely effects me beyond not being able to actually encrypt my phone but I would still like to fix it. I'm might be returning this phone and I'd like to send it back the way I got it. Even if I keep it, leaving it pseudo-encrypted would bug me. How do I fix this please? I made sure that before I started installing things via recovery that I removed my fingerprint and PIN.

Doc Ames said:
Currently my device is fully functional except that in Android settings under "Security" it indicates that my phone is encrypted.
Click to expand...
Click to collapse
You could do a full backup in TWRP and wipe the data partition. After that you can restore the backup. If you have no PIN or gesture unlock enabled, then it should boot fine. Otherwise you should delete the locksettings.db* files in /system/data in TWRP.
Sent from my ZTE A2017U using Tapatalk

DaCashFlow said:
You could do a full backup in TWRP and wipe the data partition. After that you can restore the backup. If you have no PIN or gesture unlock enabled, then it should boot fine. Otherwise you should delete the locksettings.db* files in /system/data in TWRP.
Sent from my ZTE A2017U using Tapatalk
Click to expand...
Click to collapse
Thank you for the reply. I ended up having to format /data in TWRP. See above.

Phone stuck on erasing boot loop

Hello guys, I ran into some trouble by trying to reset my phone to stock firmware. I followed this guide https://forum.xda-developers.com/showthread.php?t=2759495 but with the moto e4 firmware, now it bootloops to erasing and bad key. Please help, it doesnt let me boot into recovery

frederickrl said:
Hello guys, I ran into some trouble by trying to reset my phone to stock firmware. I followed this guide https://forum.xda-developers.com/showthread.php?t=2759495 but with the moto e4 firmware, now it bootloops to erasing and bad key. Please help, it doesnt let me boot into recovery
Click to expand...
Click to collapse
Update, I was able to boot into twrp, currently attemtping to flash a rom

similar problem: recovery loop
frederickrl said:
Update, I was able to boot into twrp, currently attemtping to flash a rom
Click to expand...
Click to collapse
Hello,
this is my situation:
- switchin-on my new moto e4 (XT1762)
- boot into recovery (TWRP)
- in TWRP, I am able to 'work', i.e. install LineageOS 15.1 (this is my main goal)
--- I WIPE
--- I INSTALL the lineage ZIP file (lineage 15.1 20180310 unofficial woods
--- I REBOOT
BUT, sadly, the reboot is done again into TWRP.
The installation of lineageos did not report any error.
How can I check, that what I've installed so far (TWRP and magisk) is correct and working?
Did I forget something? E.g. do I have to install GAPPS as well? Or Magisk? Or SUperSU?
Shall I try another custom ROM? Or another version of lineageOS? (Oh, yes, I tried Lineageos 15.0, but I got 'ZIP error'.
Thanks for your help!

Fussloseskriechtier said:
Hello,
this is my situation:
- switchin-on my new moto e4 (XT1762)
- boot into recovery (TWRP)
- in TWRP, I am able to 'work', i.e. install LineageOS 15.1 (this is my main goal)
--- I WIPE
--- I INSTALL the lineage ZIP file (lineage 15.1 20180310 unofficial woods
--- I REBOOT
BUT, sadly, the reboot is done again into TWRP.
The installation of lineageos did not report any error.
How can I check, that what I've installed so far (TWRP and magisk) is correct and working?
Did I forget something? E.g. do I have to install GAPPS as well? Or Magisk? Or SUperSU?
Shall I try another custom ROM? Or another version of lineageOS? (Oh, yes, I tried Lineageos 15.0, but I got 'ZIP error'.
Thanks for your help!
Click to expand...
Click to collapse
I imagine you are having the same problem that I was having. This is what I think happened, there is a particular partition which TWRP fails to erase, if this is the case I believe you are able to boot into the device by hitting start in the bootloader, hold volume down and power then select start. Tell me how it goes

TWRP loop
frederickrl said:
I imagine you are having the same problem that I was having. This is what I think happened, there is a particular partition which TWRP fails to erase, if this is the case I believe you are able to boot into the device by hitting start in the bootloader, hold volume down and power then select start. Tell me how it goes
Click to expand...
Click to collapse
Thanks for this hint, frederick.
Unfortunately, it did not work.
I rebooted to bootloader mode, then I pushed 'DOWN' and 'POWER' for several seconds - but I could not select anything - display was switched off and the device rebooted to TWRP again.
That's strange, because yesterday I've got this 'MENUE', when pushing 'DOWN'&'POWER' for selecting FACTORY, RECOVERY, ... but this does not appear now.
More facts (it might help):
- After switching on the the device, I get this 'Orange state' message.
Perhaps any other hints?

Fussloseskriechtier said:
Thanks for this hint, frederick.
Unfortunately, it did not work.
I rebooted to bootloader mode, then I pushed 'DOWN' and 'POWER' for several seconds - but I could not select anything - display was switched off and the device rebooted to TWRP again.
That's strange, because yesterday I've got this 'MENUE', when pushing 'DOWN'&'POWER' for selecting FACTORY, RECOVERY, ... but this does not appear now.
More facts (it might help):
- After switching on the the device, I get this 'Orange state' message.
Perhaps any other hints?
Click to expand...
Click to collapse
I have no other recommendations as to what to do. Just flash stock firmware with rsdlite and everything will be back to normal, if you have any data that you need to back up you can use TWRP to transfer the files to a PC

Fussloseskriechtier said:
Thanks for this hint, frederick.
Unfortunately, it did not work.
I rebooted to bootloader mode, then I pushed 'DOWN' and 'POWER' for several seconds - but I could not select anything - display was switched off and the device rebooted to TWRP again.
That's strange, because yesterday I've got this 'MENUE', when pushing 'DOWN'&'POWER' for selecting FACTORY, RECOVERY, ... but this does not appear now.
More facts (it might help):
- After switching on the the device, I get this 'Orange state' message.
Perhaps any other hints?
Click to expand...
Click to collapse
In twrp select reboot bootloader. In bootloader, tap volume until you see "start". Tap power. Do not try holding buttons together in bootloader. It doesn't do anything. Single taps.

madbat99 said:
In twrp select reboot bootloader. In bootloader, tap volume until you see "start". Tap power. Do not try holding buttons together in bootloader. It doesn't do anything. Single taps.
Click to expand...
Click to collapse
After "REBBOT BOOTLOADER" in TWRP, I get a black screen, where (on the very bottom) there are two lines: => FASTBOOT mode
=> device unlocked
Tapping or holding the volume&power buttons does not work in this state.
As mentioned before, by any reason I do not have this nice menue anymore, the one with RECOVERY, START, ...
So this could be the problem, right? Is my bootloader not working properly? Which part is telling the device to startup either in TWRP (=recovery) or into the Bootloader/System?
Mmmmh....

Fussloseskriechtier said:
After "REBBOT BOOTLOADER" in TWRP, I get a black screen, where (on the very bottom) there are two lines: => FASTBOOT mode
=> device unlocked
Tapping or holding the volume&power buttons does not work in this state.
As mentioned before, by any reason I do not have this nice menue anymore, the one with RECOVERY, START, ...
So this could be the problem, right? Is my bootloader not working properly? Which part is telling the device to startup either in TWRP (=recovery) or into the Bootloader/System?
Mmmmh....
Click to expand...
Click to collapse
Fastboot mode is bootloader. Why the options aren't there I couldn't tell you. I see you flashed a rom for woods. Do you have the mediatek version? Hopefully you didn't flash wood stuff on a Perry device. Bootloader may be different. I have Qualcomm. Was that option ever there in fastboot mode?
This is how to fix the recovery loop. And possibly boot you in to whatever is left of your os.

madbat99 said:
Fastboot mode is bootloader. Why the options aren't there I couldn't tell you. I see you flashed a rom for woods. Do you have the mediatek version? Hopefully you didn't flash wood stuff on a Perry device. Bootloader may be different. I have Qualcomm. Was that option ever there in fastboot mode?
This is how to fix the recovery loop. And possibly boot you in to whatever is left of your os.
Click to expand...
Click to collapse
Thanks again for your hints!
First of all, my device variant is XT1762, i.e. woods. I did not use PERRY software.
The bootloader options (RECOVERY MODE, FACTORY MODE, etc.) were there, but it seems I've somehow broken this peace of code... I believe this is the reason of my problems. Unfortunately I do not understand the Android boot sequence...
However, I tried >> fastboot erase misc << via terminal:
result:
erasing 'misc'...
FAILED (remote: partition table doesn't exist)
finished. total time 0.009s
I double checked it vie file manager in TWRP: there is no MISC folder.
It seems, my only option is to go back to stock ROM... :crying:

Fussloseskriechtier said:
Thanks again for your hints!
First of all, my device variant is XT1762, i.e. woods. I did not use PERRY software.
The bootloader options (RECOVERY MODE, FACTORY MODE, etc.) were there, but it seems I've somehow broken this peace of code... I believe this is the reason of my problems. Unfortunately I do not understand the Android boot sequence...
However, I tried >> fastboot erase misc << via terminal:
result:
erasing 'misc'...
FAILED (remote: partition table doesn't exist)
finished. total time 0.009s
I double checked it vie file manager in TWRP: there is no MISC folder.
It seems, my only option is to go back to stock ROM... :crying:
Click to expand...
Click to collapse
I think the partitions are different in mtk version. But I would try flashing stock.

I have exactly the same problem after trying to flash lineage 14.1 to my XT1762.
Unfortunately I have only a TWRP Backup of my stock system before the flash and recovering that didn't fix the problem.

Fussloseskriechtier said:
Perhaps any other hints?
Click to expand...
Click to collapse
MiGri said:
I have exactly the same problem after trying to flash lineage 14.1 to my XT1762.
Unfortunately I have only a TWRP Backup of my stock system before the flash and recovering that didn't fix the problem.
Click to expand...
Click to collapse
I know what a pain in the ass my Perry variant was just to get the root going, so I can just imagine your frustration.
Did you guys take the update they're pushing out on the phones? Check. Some of the updates might be forced or you may accidentally said Okay and didn't realize it- that could be the reason why you're having trouble. The significant other got an update on the E4, and now can't do root.

I was able to get my phone back to work using https://forum.xda-developers.com/moto-e4/development/rom-original-stock-firmware-woods-twrp-t3766902

Stock ROM used to repair bootloader
Articul8Madness said:
I know what a pain in the ass my Perry variant was just to get the root going, so I can just imagine your frustration.
Did you guys take the update they're pushing out on the phones? Check. Some of the updates might be forced or you may accidentally said Okay and didn't realize it- that could be the reason why you're having trouble. The significant other got an update on the E4, and now can't do root.
Click to expand...
Click to collapse
Hello!
In the meantime I actually deleted everything and flashed the Stock ROM on my XT1762.
After that, my Bootloader menue (RECOVERY MODE, FACTORY MODE, START, ...) appeared again...
I felt lucky and started the whole procedure again: use TWRP, backup, delete Cache, Flash custom ROM, delete Cache, restart... and finally, I got lineageOS 15.1 and CrDroid running on my phone.
Now I use CrDroid, because LineageOS 15.1 did not Support my SIM Card... ? However, I am happy with CrDroid: fast, slim, nice looking, ...
So in the end, it seems that I deleted a specific part in my Flash which caused the "boot Loop". But I could repair it by flashing the Stock ROM again.
Thanks guys, you're doing a good Job!
Buy!

Fussloseskriechtier said:
Hello!
In the meantime I actually deleted everything and flashed the Stock ROM on my XT1762.
After that, my Bootloader menue (RECOVERY MODE, FACTORY MODE, START, ...) appeared again...
I felt lucky and started the whole procedure again: use TWRP, backup, delete Cache, Flash custom ROM, delete Cache, restart... and finally, I got lineageOS 15.1 and CrDroid running on my phone.
Now I use CrDroid, because LineageOS 15.1 did not Support my SIM Card... ? However, I am happy with CrDroid: fast, slim, nice looking, ...
So in the end, it seems that I deleted a specific part in my Flash which caused the "boot Loop". But I could repair it by flashing the Stock ROM again.
Thanks guys, you're doing a good Job!
Buy!
Click to expand...
Click to collapse
I'm also stuck in boot loop... What directories/files did you delete? Have backup of stock rom, but restore fails:
This /data backup was made with f2fs file system! The backup may not boot unless you change back to f2fs
Failed to mount /data (Invalid argument)
TWRP says that file system of /data is ext4. Not possible to change or repair the file system in TWRP with Wipe / Advanced wipe / Repair or change file system. Result:
Error changing file system
or
/sbin/e2fsck -fp /dev/block/mmcblk0p27 process ended with error: 8
Phone is always starting in TWRP ending with:
Could not mount /data and unable to find crypto footer.
Failed to mount '/data' (Invalid argument)
Unable to recreate /data/media folder.
Updating partition details...
Failed to mount '/data' (Invalid argument)
...done
Unable to mount storage
Failed to mount '/data' (Invalid argument)
Full SELinux support is present.
Unable to mount /data/media/TWRP/.twrps
MTP Enabled
In terminal no problem to create (mkdir) and delete directories.
Flashing of lineage 14.1 or 15.1 for woods ends also with:
Failed to mount '/data' (Invalid argument)
This command in TWRP terminal didn't work:
fastboot erase misc
erasing 'misc'...
FAILED (remote: Partition table doesn't exist)
There is no misc folder.
Any ideas?
Thank you in advance!

pancobe said:
I'm also stuck in boot loop... What directories/files did you delete? Have backup of stock rom, but restore fails:
This /data backup was made with f2fs file system! The backup may not boot unless you change back to f2fs
Failed to mount /data (Invalid argument)
TWRP says that file system of /data is ext4. Not possible to change or repair the file system in TWRP with Wipe / Advanced wipe / Repair or change file system. Result:
Error changing file system
or
/sbin/e2fsck -fp /dev/block/mmcblk0p27 process ended with error: 8
Phone is always starting in TWRP ending with:
Could not mount /data and unable to find crypto footer.
Failed to mount '/data' (Invalid argument)
Unable to recreate /data/media folder.
Updating partition details...
Failed to mount '/data' (Invalid argument)
...done
Unable to mount storage
Failed to mount '/data' (Invalid argument)
Full SELinux support is present.
Unable to mount /data/media/TWRP/.twrps
MTP Enabled
In terminal no problem to create (mkdir) and delete directories.
Flashing of lineage 14.1 or 15.1 for woods ends also with:
Failed to mount '/data' (Invalid argument)
This command in TWRP terminal didn't work:
fastboot erase misc
erasing 'misc'...
FAILED (remote: Partition table doesn't exist)
There is no misc folder.
Any ideas?
Thank you in advance!
Click to expand...
Click to collapse
Just flash stock firmware with rsdlite, it's the simplest way to go. Then if you'd like flash your rom

frederickrl said:
Just flash stock firmware with rsdlite, it's the simplest way to go. Then if you'd like flash your rom
Click to expand...
Click to collapse
Thank you for the hint on rsdlite, didn't know the program! Unfortunately I have two problems, have only access to an old XP box (I'm normally on a mac), and rsdlite doesn't recognise the phone, driver problem presumably... And the program doesn't recognise the format of the backup I made with TWRP...
Is it possible to repair the file system on the phone via terminal? Or to delete parts of the system safely and reinstall the stock system? The other guy apparently did something like that. Or to unpack a custom rom and place the parts via terminal so it can install on next boot?
Thank you!

Did following check:
mount /data
mount: '/dev/block/mmcblk0p27'->'/data': Invalid argument
e2fsck -n /dev/block/mmcblk0p27
e2fsck 1.42.9 (28-Dec-2013)
ext2fs_open2: Bad magic number in super-block
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/block/mmcblk0p27
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
Would it be safe to rmdir /data and mkdir /data ?
Thanks...

pancobe said:
Thank you for the hint on rsdlite, didn't know the program! Unfortunately I have two problems, have only access to an old XP box (I'm normally on a mac), and rsdlite doesn't recognise the phone, driver problem presumably... And the program doesn't recognise the format of the backup I made with TWRP...
Is it possible to repair the file system on the phone via terminal? Or to delete parts of the system safely and reinstall the stock system? The other guy apparently did something like that. Or to unpack a custom rom and place the parts via terminal so it can install on next boot?
Thank you!
Click to expand...
Click to collapse
Rsdlite is not meant to install your twrp backup. It's for installing the official firmware package. And you need to install moto drivers of course.

/data, /storage, /cache could not mount

Hi All
Please help me with this
My phone is Lenovo A6000+ and last month, after lot of hard work I was able to get my phone up and running and installed Dot OS custom rom for A6000+ based on oreo 8.1
It was running fine up until yesterday. I was changing settings and unluckly I turned on Data saver, It unleashed havoc on my phone and I dont know how my phone went into encryption mode. On restarting the phone I was getting some about encryption, I dont how it happened. I never turned on anything like that in settings. May be it was google settings. I don't know.
I thought I can reinstall OS again as i have done in the past.
I started doing it and i got this message /storage /data could not be mount, I dug up the internet for solutions and implemented most of the solution provided here or youtube or different websites or blogs , nothing worked.
I have tried format option as told , repair, but it didnt help me out.
I reinstalled stock recovery, tried twrp 3.2.1.0 for A6000+ but it didnt work out.
Twrp shows 0 MB for internal storage.
Please help me out.

anandhunt said:
Hi All
Please help me with this
My phone is Lenovo A6000+ and last month, after lot of hard work I was able to get my phone up and running and installed Dot OS custom rom for A6000+ based on oreo 8.1
It was running fine up until yesterday. I was changing settings and unluckly I turned on Data saver, It unleashed havoc on my phone and I dont know how my phone went into encryption mode. On restarting the phone I was getting some about encryption, I dont how it happened. I never turned on anything like that in settings. May be it was google settings. I don't know.
I thought I can reinstall OS again as i have done in the past.
I started doing it and i got this message /storage /data could not be mount, I dug up the internet for solutions and implemented most of the solution provided here or youtube or different websites or blogs , nothing worked.
I have tried format option as told , repair, but it didnt help me out.
I reinstalled stock recovery, tried twrp 3.2.1.0 for A6000+ but it didnt work out.
Twrp shows 0 MB for internal storage.
Please help me out.
Click to expand...
Click to collapse
First of all Chill!!
boot to fastboot mode and try formating data
-> fastboot -w
-> fastboot format:ext4 userdata
-> fastboot format:ext4 cache
-> try 'fastboot erase system' first if that doesn't work then fastboot format:ext4 system
-> reboot to recovery
-> Flash your rom
-> Reboot
Try these steps and tell whether they work for you or they don't

dev_harsh1998 said:
First of all Chill!!
boot to fastboot mode and try formating data
-> fastboot -w
-> fastboot format:ext4 userdata
-> fastboot format:ext4 cache
-> try 'fastboot erase system' first if that doesn't work then fastboot format:ext4 system
-> reboot to recovery
-> Flash your rom
-> Reboot
Try these steps and tell whether they work for you or they don't
Click to expand...
Click to collapse
ok i wil try today n will tell you about this

dev_harsh1998 said:
First of all Chill!!
boot to fastboot mode and try formating data
-> fastboot -w
-> fastboot format:ext4 userdata
-> fastboot format:ext4 cache
-> try 'fastboot erase system' first if that doesn't work then fastboot format:ext4 system
-> reboot to recovery
-> Flash your rom
-> Reboot
Try these steps and tell whether they work for you or they don't
Click to expand...
Click to collapse
Did this and fastbooted to recovery but didn't work, couldn't mount /system or /data which means couldn't flash any rom .

didnt worked
dev_harsh1998 said:
First of all Chill!!
boot to fastboot mode and try formating data
-> fastboot -w
-> fastboot format:ext4 userdata
-> fastboot format:ext4 cache
-> try 'fastboot erase system' first if that doesn't work then fastboot format:ext4 system
-> reboot to recovery
-> Flash your rom
-> Reboot
Try these steps and tell whether they work for you or they don't
Click to expand...
Click to collapse
it didnt worked for me and the exact same thing happend to me,i got some encrypting msg and my phone start to rebooting,and when i open twpr getting same error
plz help out