Related
Hi, I tried to do a full wipe from TWRP, but I was unable to wipe Interal Storage, next message appeared:
E:mount -o bind '/data/media/0' '/sdcard' process ended with ERROR=255
Anyways, the message of succesfull wipe appeared (and internal storage was in fact wiped). I don't know if I should worry (everything works fine after installing CM.12.1 nightly 08/06). The previous firmware installed was OxygenOs (I had a remote session thinking they would accept a RMA but they instead installed Oxygen with the latest drivers ). Every time I try to wipe that partition again I get the same message (but it gets wiped).
Thanks for your help and sorry for my english!
trionic said:
Hi, I tried to do a full wipe from TWRP, but I was unable to wipe Interal Storage, next message appeared:
E:mount -o bind '/data/media/0' '/sdcard' process ended with ERROR=255
Anyways, the message of succesfull wipe appeared (and internal storage was in fact wiped). I don't know if I should worry (everything works fine after installing CM.12.1 nightly 08/06). The previous firmware installed was OxygenOs (I had a remote session thinking they would accept a RMA but they instead installed Oxygen with the latest drivers ). Every time I try to wipe that partition again I get the same message (but it gets wiped).
Thanks for your help and sorry for my english!
Click to expand...
Click to collapse
hey and welcome ,
you should always install the newest Twrp. Just download it via playstore
an other method. Download multirom and install twrp from there.
For the next time. Wipe partitions. Try to repair theme and flash it back to ext4.
Now everything should be clean.
If your system runs without any problemes or issues its just a cosmetic issue not more.
regards
Are you using latest 2.8.6.0/2.8.6.1?
davebugyi said:
Are you using latest 2.8.6.0/2.8.6.1?
Click to expand...
Click to collapse
real_pac said:
hey and welcome ,
you should always install the newest Twrp. Just download it via playstore
an other method. Download multirom and install twrp from there.
For the next time. Wipe partitions. Try to repair theme and flash it back to ext4.
Now everything should be clean.
If your system runs without any problemes or issues its just a cosmetic issue not more.
regards
Click to expand...
Click to collapse
I am using 2.8.6.1 (latest version). Unfortunately twrp doesn't allow me to repair / format that partition.
Thanks you both for your response
trionic said:
I am using 2.8.6.1 (last version). Unfortunately twrp doesn't allow me to repair / format that partition.
Thanks you both for your response
Click to expand...
Click to collapse
You're welcome but please don't a new thread write in the specific thread..
please reinstall twrp via playstore flashable zip or just flash the recovery img via adb or any oneplus one toolkit regards
real_pac said:
You're welcome but please don't a new thread write in the specific thread..
please reinstall twrp via playstore flashable zip or just flash the recovery img via adb or any oneplus one toolkit regards
Click to expand...
Click to collapse
I installed again with TWRP Manager and everything works perfectly now (no error message). Thanks again
trionic said:
Hi, I tried to do a full wipe from TWRP, but I was unable to wipe Interal Storage, next message appeared:
E:mount -o bind '/data/media/0' '/sdcard' process ended with ERROR=255
[...]
Click to expand...
Click to collapse
I faced this error once on twrp 2.8.6.1 a week ago. I wanted to restore my nandroid and the error repeatedly happened while restoring data-partition. I then booted the system and deleted some files from internal storage (which was about half full at the time the error occurred). Afterwards I rebooted to twrp and could successfully restore my complete nandroid. It's a bit shocking if you face this error when restoring a nandroid, because the restore process wipes the data partition first and then begins the restore.
real_pac said:
hey and welcome ,
you should always install the newest Twrp. Just download it via playstore
an other method. Download multirom and install twrp from there.
For the next time. Wipe partitions. Try to repair theme and flash it back to ext4.
Now everything should be clean.
If your system runs without any problemes or issues its just a cosmetic issue not more.
regards
Click to expand...
Click to collapse
That tip worked for me (i9192), I just install the last TWRP (I think this is not needed) and wipe /Data with ext4, wipe again to F2FS and restore, thank you.
I woke up to find my 1st Generation Moto G battery was depleted and on charging it a bit., I switched it on only to find it optimizing my apps. All these (battery getting depleted, app optimization) happen all the time and I wasn't the least worried.
I picked up my phone later thinking it must have been done with the app optimization only to discover it was totally dead while still connected to a power bank. When I try to switch it on, it is stuck on the "Unlock Bootloader" page. I have tried flashing a new stock rom and it does not work.
I attached the image I see when I try to use recovery to wipe. Basically, nothing works. Can anybody help as I just fixed the screen and also out of warranty?
Fastboot flash the latest Factory Firmware Image for your model.
Factory Firmware Images: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Fastboot Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
lost101 said:
Fastboot flash the latest Factory Firmware Image for your model.
Factory Firmware Images: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Fastboot Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
Click to expand...
Click to collapse
Thanks lost101, I do know how to flash perfectly well with fastboot. The problem is it flashes successfully but the phone is still stuck on the Bootloader.
I get this particular message on my recovery when I try to wipe either userdata or cache.
blkdiscard on partition /dev/block/platform/msm_sdcc.1/by-name/userdata failed formatting /userdata failed
formatting cache
and
blkdiscard on partition /dev/block/platform/msm_sdcc.1/by-name/userdata failed formatting /cache
wiping clogo
@NaijaAndroid - Can you try booting into TWRP via: fastboot boot twrp.img
lost101 said:
@NaijaAndroid - Can you try booting into TWRP via: fastboot boot twrp.img
Click to expand...
Click to collapse
I do not have a custom recovery presently but when I try to flash TWRP, it flashes successfully with no error message but the phone is still stuck on the stock recovery.
NaijaAndroid said:
I do not have a custom recovery presently but when I try to flash TWRP, it flashes successfully with no error message but the phone is still stuck on the stock recovery.
Click to expand...
Click to collapse
Read again what I told you to do. I did not say for you to flash anything.
@lost101, I just read your instructions again. I can boot in to TWRP. What else should I do after?
Thanks.
NaijaAndroid said:
@lost101, I just read your instructions again. I can boot in to TWRP. What else should I do after?
Click to expand...
Click to collapse
Via PC, do the following wipe: (requires working ADB setup)
http://forum.xda-developers.com/showpost.php?p=65431978&postcount=22
You could then TWRP > Wipe > Format Data > Yes, and try flashing a custom ROM.
Edit: You should backup photos or important data before hand.
I just downloaded CM 12.1. How can I transfer the ROM to the phone?
Edit: I have done it.
NaijaAndroid said:
I just downloaded CM 12.1. How can I transfer the ROM to the phone?
Click to expand...
Click to collapse
Recovery mode ADB will work with Linux - unsure about Windows. You could boot into an Ubuntu LiveCD (without installing) and transfer the ROM to phone that way. Otherwise, an OTG usb pen would be another option.
adb push rom.zip /sdcard
@lost101, I tried to send the Rom via ADB and I got : failed to copy 'Rom.zip' to '/sdcard//Rom.zip' : Read-only file system.
Also, TWRP made my phone to load as MTP on my PC but I could not transfer through that method also. The transfer kept on failing. Seems my internal memory (eMMC) is now Read-only.
NaijaAndroid said:
@lost101, I tried to send the Rom via ADB and I got : failed to copy 'Rom.zip' to '/sdcard//Rom.zip' : Read-only file system.
Also, TWRP made my phone to load as MTP on my PC but I could not transfer through that method also. The transfer kept on failing. Seems my internal memory (eMMC) is now Read-only.
Click to expand...
Click to collapse
Try sideloading the ROM.
TWRP > ADB sideloadadb sideload rom.zip
lost101 said:
Try sideloading the ROM.
TWRP > ADB sideloadadb sideload rom.zip
Click to expand...
Click to collapse
I got:
Installing zip file '/sideload/package.zip'
detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/system
Can't install this package on top of incompatible data. Please try another package or run a factory reset
Updater process ended with ERROR: 7
I was trying to use CM 12.1.
So sorry for taking your time. Thanks.
NaijaAndroid said:
I got:
Installing zip file '/sideload/package.zip'
detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/system
Can't install this package on top of incompatible data. Please try another package or run a factory reset
Updater process ended with ERROR: 7
I was trying to use CM 12.1.
Click to expand...
Click to collapse
Try a CM13 ROM.
lost101 said:
Try a CM13 ROM.
Click to expand...
Click to collapse
Same problem as above. I got the same message.
On PC:
adb shelle2fsck /dev/block/platform/msm_sdcc.1/by-name/userdata
lost101 said:
On PC:
adb shelle2fsck /dev/block/platform/msm_sdcc.1/by-name/userdata
Click to expand...
Click to collapse
I got:
/dev/block/platform/msm_sdcc.1/by-name/userdata is in use.
e2fsck: Cannot continue, aborting.
NaijaAndroid said:
I got:
/dev/block/platform/msm_sdcc.1/by-name/userdata is in use.
e2fsck: Cannot continue, aborting.
Click to expand...
Click to collapse
TWRP > MOUNT > Untick /Data
lost101 said:
TWRP > MOUNT > Untick /Data
Click to expand...
Click to collapse
got this after unticking data and trying again:
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/platform
/msm_sdcc.1/by-name/userdata
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:
NaijaAndroid said:
got this after unticking data and trying again:
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/platform
/msm_sdcc.1/by-name/userdata
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:
Click to expand...
Click to collapse
A certain percentage of phones end up with corrupt emmc (internal storage) over time. This problem is a fairly common thing. I do recall someone managing to boot an use CM13, despite the read-only userdata. I'm guessing they must have flashed it via TWRP, with the ROM.zip on an OTG usb pen. It may have worked because /system was still partially / fully writeable.
Hi, i have the next versions:
CyanogenMod: 13.0-20161004-NIGHTLY-osprey
Kernel: 3.10.49-MPI24.107-56-g09ff0d1
And when trying to install the 1009-NIGHTLY update i get an error without a log in the cianogenmod recovery. When I try to "Apply update" and then "Choose from emulated", it shows the next message:
"E:failed to mount /data (Invalid argument)
Installation aborted"
Then, i go to see the recovery logs, but it blanks and shows the main menu again.
Why do I want to update to the latest version, having 5 days of difference with the installed version?
Because I'm having repeatedly bugs with the Firefox browser, can't update Telegram, can't connect via Bluetooth to the most of the devices, can't update the binaries of SuperSU, and other minor errors.
Which could be the cause of some of this problems?
Sorry for my poor english, Saludos!
Download the latest nightly and before installing wipe the /system /dalvik cache and /cache partition, just be aware that you will need to reflash your gaps package.
Henriquefeira said:
Download the latest nightly and before installing wipe the /system /dalvik cache and /cache partition, just be aware that you will need to reflash your gaps package.
Click to expand...
Click to collapse
Just did what you said, wiped /cache and /system partition, and when the phone reboots it stays in the Motorola logo. Seems that I can't load the installer using USB, because there is no ROM installed.
The good news are that I have access to emulated.
What am I doing wrong?
Gonzon said:
Just did what you said, wiped /cache and /system partition, and when the phone reboots it stays in the Motorola logo. Seems that I can't load the installer using USB, because there is no ROM installed.
The good news are that I have access to emulated.
What am I doing wrong?
Click to expand...
Click to collapse
You wiped your entire internal storage? If not then there is an issue with your internal storage. I once had a similar issue to this, where my phone would keep wiping it's internal storage and crash a lot, the solution was to reflash the stock ROM. Sorry for the inconvenience that I caused to you
Just as a side question, did anyone got AICP nightlies .zip stuck at extracting image to /system? I tried clean install (wipe /system, /data, /cache and dalvik) but its just stuck there. Tried multiple nightlies. Tried deleting Android and .android_secure folders in both external and internal storage. I haven't tried wiping internal storage yet (I will do it ASAP). Any tips will be great. Thanks
Broadcasted from Zeta Reticuli
Henriquefeira said:
You wiped your entire internal storage? If not then there is an issue with your internal storage. I once had a similar issue to this, where my phone would keep wiping it's internal storage and crash a lot, the solution was to reflash the stock ROM. Sorry for the inconvenience that I caused to you
Click to expand...
Click to collapse
I still don't know why cm installs a recovery that it is unstable and with less tools than TWRP. I believe that they should use at least the code of TWRP.
No problem Henriquefeira, everything has it's solution. Besize, your help was too much better than silence in this post. Now, I have to focus on try to enter to the internal storage and flash the update I have.
For that, I'm using fastboot in linux. But I don't know too much about using it. Next, I'll show you the messages that the terminal sent me:
Code:
[email protected]:~$ fastboot -p xxxxxxxxxx flash /data/media /home/imperial/Android2/cmupdater/cm-13.0-20161009-NIGHTLY-osprey.zip
target reported max download size of 268435456 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 91972855 is not a multiple of the block size 4096
fastboot: /build/android-tools-hIu7Bj/android-tools-4.2.2+git20130529/core/libsparse/sparse.c:143: write_all_blocks: Assertion `pad >= 0' failed.
Abortado
Do you know what it means?
Gonzon said:
I still don't know why cm installs a recovery that it is unstable and with less tools than TWRP. I believe that they should use at least the code of TWRP.
No problem Henriquefeira, everything has it's solution. Besize, your help was too much better than silence in this post. Now, I have to focus on try to enter to the internal storage and flash the update I have.
For that, I'm using fastboot in linux. But I don't know too much about using it. Next, I'll show you the messages that the terminal sent me:
Do you know what it means?
Click to expand...
Click to collapse
You can't flash the zip of a ROM via fastboot, follow this tutorial >goo.gl/JfRzZu and on the next time avoid installing the CM bundled recovery
Solved.
I flashed vía fastboot a stable twrp, then after a lot of errors and strange things i was able to flash the ROM.
Thanks a lot for your help.
I was seeing a bricked phone already jajaja.
Background: I have a YU Yuphoria running latest cm13 snapshot (16 Sep, 2016), with latest Xposed framework and TWRP 3.0.2
* I woke up today to find a blank screen, battery reset gives "Encryption Unsuccessful" error message
* Booted to TWRP, unable to mount /data, /cache or /system (All 0 mb in Advanced wipe)
* Couldn't restore Nandroid backup, unable to mount /system
* Booted to fastboot, tried to do factory flash using flash_all.bat, everything succeeds except for system : "remote: flash write failure"
* Reformatted data, cache and system from adb shell, still no dice
What would you suggest i do now?
Is there a way to write those partitions to a microSD card, and make the phone think of it as internal storage?
Looking at this forum (and official YU forums), it seems like this is becoming a rather common problem [1 2 3 4 5 6 7]. How is it possible that so many users come to face this exact problem at the same time (In spite of being on different ROMs)?
reserved
A_K_S_H_ said:
Background: I have a YU Yuphoria running latest cm13 snapshot (16 Sep, 2016), with latest Xposed framework and TWRP 3.0.2
* I woke up today to find a blank screen, battery reset gives "Encryption Unsuccessful" error message
* Booted to TWRP, unable to mount /data, /cache or /system (All 0 mb in Advanced wipe)
* Couldn't restore Nandroid backup, unable to mount /system
* Booted to fastboot, tried to do factory flash using flash_all.bat, everything succeeds except for system : "remote: flash write failure"
* Reformatted data, cache and system from adb shell, still no dice
What would you suggest i do now?
Is there a way to write those partitions to a microSD card, and make the phone think of it as internal storage?
Looking at this forum (and official YU forums), it seems like this is becoming a rather common problem [1 2 3 4 5 6 7]. How is it possible that so many users come to face this exact problem at the same time (In spite of being on different ROMs)?
Click to expand...
Click to collapse
i'm also facing same problem. any solution u found?
Manish Adak said:
i'm also facing same problem. any solution u found?
Click to expand...
Click to collapse
Nope, ended up buying a new phone (Redmi Note 4)
A_K_S_H_ said:
Background: I have a YU Yuphoria running latest cm13 snapshot (16 Sep, 2016), with latest Xposed framework and TWRP 3.0.2
* I woke up today to find a blank screen, battery reset gives "Encryption Unsuccessful" error message
* Booted to TWRP, unable to mount /data, /cache or /system (All 0 mb in Advanced wipe)
* Couldn't restore Nandroid backup, unable to mount /system
* Booted to fastboot, tried to do factory flash using flash_all.bat, everything succeeds except for system : "remote: flash write failure"
* Reformatted data, cache and system from adb shell, still no dice
What would you suggest i do now?
Is there a way to write those partitions to a microSD card, and make the phone think of it as internal storage?
Looking at this forum (and official YU forums), it seems like this is becoming a rather common problem [1 2 3 4 5 6 7]. How is it possible that so many users come to face this exact problem at the same time (In spite of being on different ROMs)?
Click to expand...
Click to collapse
same problem....... i flash stock yu5010a firmware from fastboot.. now:good: but when i flash some files in twrp,strucked on boot animation....so im searching for only fastboot roms..........
A_K_S_H_ said:
Nope, ended up buying a new phone (Redmi Note 4)
Click to expand...
Click to collapse
which varient?
Vimalvt said:
same problem....... i flash stock yu5010a firmware from fastboot.. now:good: but when i flash some files in twrp,strucked on boot animation....so im searching for only fastboot roms..........
Click to expand...
Click to collapse
You mean flashing yu5010a firmware solves the problem for yu5010 [Cyanogen version] ? If so, could you post a link to the firmware version you used?
Manish Adak said:
which varient?
Click to expand...
Click to collapse
13k version (4gb, 64gb)
Vimalvt said:
same problem....... i flash stock yu5010a firmware from fastboot.. now:good: but when i flash some files in twrp,strucked on boot animation....so im searching for only fastboot roms..........
Click to expand...
Click to collapse
Change ur twrp to 3..0.2.0. That should solve the problm
13k version (4gb, 64gb)[/QUOTE]
tell me ur personal user exprience about note 4.....spcly camera...
Manish Adak said:
i'm also facing same problem. any solution u found?
Click to expand...
Click to collapse
Same problem here too! No solution yet.
Internal memory 0 mb
unable to mount system (invalid argument)
unable to mount data (invalid argument)
unable to mount cache (invalid argument)
samujjwalk said:
Same problem here too! No solution yet.
Internal memory 0 mb
unable to mount system (invalid argument)
unable to mount data (invalid argument)
unable to mount cache (invalid argument)
Click to expand...
Click to collapse
The same
Try changing partitions to f2fs or any other partition and change back to default partition...
AmalRam said:
Try changing partitions to f2fs or any other partition and change back to default partition...
Click to expand...
Click to collapse
In TWRP?
If yes, I tried that already.
Tried to convert to all available options and reverted back: FAT, EXT2, EXT3,EXT4, F2FS, VFAT
Nothing works actually.
The internal memory still shows 0 MB
I used a tool also called YUware. There is an option to format all partitions. It formats all but the system partition is failed to get formatted as well.
Twrp version?
try to erase persist.img and flash the persist.img
arun531 said:
try to erase persist.img and flash the persist.img
Click to expand...
Click to collapse
Doesn't work. Gives the same error message : "FAILED (remote: flash write failure)"
how did u flash...? can you lock bootloader ...?
arun531 said:
how did u flash...?
Click to expand...
Click to collapse
Using
fastboot -i 0x2a96 flash persist persist.img
(Source : https://forum.xda-developers.com/yu-yuphoria/general/guide-bricklooping-lettuce-yu-yuphoria-t3181864 )
arun531 said:
can you lock bootloader ...?
Click to expand...
Click to collapse
Yes.
try to flash cm12 fastboot pkg.... or try the qfil flashing...
i also faced this type problem but when i erase and reflash the system and persist... it fixed.
arun531 said:
try to flash cm12 fastboot pkg....
Click to expand...
Click to collapse
That is what i did, as i mentioned in OP :
A_K_S_H_ said:
* Booted to fastboot, tried to do factory flash using flash_all.bat, everything succeeds except for system : "remote: flash write failure"
Click to expand...
Click to collapse
arun531 said:
or try the qfil flashing...
i also faced this type problem but when i erase and reflash the system and persist... it fixed.
Click to expand...
Click to collapse
Isn't qfil flashing meant for Hard Bricked devices? (My device doesn't show up as QHUSB_BULK when connected to PC)
Basically I screw up last night, trying to flash a file that was not supposed to work on minote 3, android 7.
After some tries(flashing pixel experience and appearing the encrypted phone), I was able to flash miuiPro 8.9.20.
The phone works perfectly, but I have some errors, that I need some help:
-when I go to twrp, there is 0 zips in folder, I' can't find them anywhere
-basically when I try to flash magisk, it appears Installation failed
-I can't repair data, error: failed to mount /data
Thanks for all the help I receive.
Try mounting /data manually or format data.
Hi, try to flash fastboot rom with MiFlash and then flash the rom you want.
omercicek43 said:
Try mounting /data manually or format data.
Click to expand...
Click to collapse
thanks for your response.
I already formated my data
what do u mean by: format manually?
Wistake said:
thanks for your response.
I already formated my data
what do u mean by: format manually?
Click to expand...
Click to collapse
I didn't say something like that. I said try mounting data manually.