Hi. So my device is POCO X3 NFC with device model SURYA and I am on android 11. So my problem is i can't flash a custom rom. I think i accidentally wiped my internal storage. Can someone help me? Can I still use my device? Should i still flash a disable dm verity?
also showing errors that follows
1. unable to decrypt FBE device
2. unable to update logical partition: /system_root
3. unable to update logical partition: /product
4. unable to update logical partition: /vendor
also tried flashing a few custom roms, still not working
hi. seems that i need to update my recovery (which i already did) but now its showing error installing zip file. what should i do? i think its about the partitions. how do you mount system partition to install zip file if this is the case, if not, help me IM GOING TO DIE HAHAHAHA
davepayra said:
also showing errors that follows
1. unable to decrypt FBE device
2. unable to update logical partition: /system_root
3. unable to update logical partition: /product
4. unable to update logical partition: /vendor
Click to expand...
Click to collapse
Did you ever resolve this? I"m having similar issues.....
Related
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.
Can't flash anything through recovery. (failed to mount "/cpefs" (Invalid Response)
I recently got this phone and I've been trying to install a custom rom, however, I can't seem to do anything while using TWRP. For some reason the file explorer shows no files and no /storage folder. It also says that the /system partition weights 0MB. I've already tried formatting the /data partition from EXT4 to extFAT, but it won't let me because it cannot mount the "/cpefs" partition, which I've been unable to find any information about.
I can flash the stock firmware trough ODIN, and I can flash the recovery. The internal storage works fine, but nothing shows up when I open TWRP.
I've tried formatting the data partition, repairing it, changing the partition format, wiping, installing a custom rom, installing superSU. But it won't allow me to do any of those things. Either "/data" can't be mounted, or "/cpefs" can't be mounted while formatting /data.
Cepillado said:
I recently got this phone and I've been trying to install a custom rom, however, I can't seem to do anything while using TWRP. For some reason the file explorer shows no files and no /storage folder. It also says that the /system partition weights 0MB. I've already tried formatting the /data partition from EXT4 to extFAT, but it won't let me because it cannot mount the "/cpefs" partition, which I've been unable to find any information about.
I can flash the stock firmware trough ODIN, and I can flash the recovery. The internal storage works fine, but nothing shows up when I open TWRP.
I've tried formatting the data partition, repairing it, changing the partition format, wiping, installing a custom rom, installing superSU. But it won't allow me to do any of those things. Either "/data" can't be mounted, or "/cpefs" can't be mounted while formatting /data.
Click to expand...
Click to collapse
Which phone you're using?
J7 Pro?
Secondly make sure to enable OEM unlock options from the stock ROM's Developer option!
Thirdly check the recovery patches etc of the desired recovery's webiste (you're using) and flash it through the recovery if you're facing the problem!
It'll work, mostly some users said they fixed this by the above mentioned step!
If no luck, maybe someone will sort it out for ya, soon! :laugh:
Good Luck! :good:
sosukeaizen said:
Which phone you're using?
J7 Pro?
Secondly make sure to enable OEM unlock options from the stock ROM's Developer option!
Thirdly check the recovery patches etc of the desired recovery's webiste (you're using) and flash it through the recovery if you're facing the problem!
It'll work, mostly some users said they fixed this by the above mentioned step!
If no luck, maybe someone will sort it out for ya, soon! :laugh:
Good Luck! :good:
Click to expand...
Click to collapse
Thanks for your reply. The model of the phone is SM-J710MN. The OEM unlock option is enabled, otherwise I wouldn't be able to flash the recovery. I am trying to use TWRP. Where would I find a recovery patch for this model?. Everything works fine in the recovery, but it won't let me wipe/format/repair or change ANY partition. It can't mount anything, and the error that I see the most often is that it cannot mount the /cpefs partition.
Cepillado said:
Thanks for your reply. The model of the phone is SM-J710MN. The OEM unlock option is enabled, otherwise I wouldn't be able to flash the recovery. I am trying to use TWRP. Where would I find a recovery patch for this model?. Everything works fine in the recovery, but it won't let me wipe/format/repair or change ANY partition. It can't mount anything, and the error that I see the most often is that it cannot mount the /cpefs partition.
Click to expand...
Click to collapse
try flashing a lower version of the same frimware you've already installed e.g if the latest is nougat 7.1.1 with the recent security update, try flashing with another nougat version that is lower to the recent one's security patch #
Hi All,
I am trying to root Samsung S7 Oreo 8.0 with TWRP & Magisk. But, when ever I log into TWRP it's saying "Inernal Memory 0MB)
I've followed below steps :
Installed TWRP and no-verity-opt-encrypt zip, it worked until I reboot to system
After reboot again the internal memory showing as 0MB (may be re-encrypted)
Is there any way that I can remove the encryption permanently?
Error :
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
PS : I've gone through the forum to find different solutions, but nothing working to remove the encryption permanently.
yes, it is possible. is use it all the time with my stock android. give me some time to write it...or maybe someone other can tell u. u already used the search in this forum?
an other question, u really need an unencrytped internal memory?
snowfirewall said:
Hi All,
I am trying to root Samsung S7 Oreo 8.0 with TWRP & Magisk. But, when ever I log into TWRP it's saying "Inernal Memory 0MB)
I've followed below steps :
Installed TWRP and no-verity-opt-encrypt zip, it worked until I reboot to system
After reboot again the internal memory showing as 0MB (may be re-encrypted)
Is there any way that I can remove the encryption permanently?
Error :
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
PS : I've gone through the forum to find different solutions, but nothing working to remove the encryption permanently.
Click to expand...
Click to collapse
Thank you.. Am not exactly looking for unencrypted partition. Am just confused whether it's expected to format data and no variety everytime or is it just one time for root?
Also I gone through the threads to find fix for this issue. But most of the people are suggesting to format data.
Any other better ways? Can we take backup of existing ROM from TWRP without root?
Roberto W. said:
yes, it is possible. is use it all the time with my stock android. give me some time to write it...or maybe someone other can tell u. u already used the search in this forum?
an other question, u really need an unencrytped internal memory?
Click to expand...
Click to collapse
i am using a stock firmware by telekom, it installs some features after first flash and first reboot (maybe ur firmware does not need step 3, so my second reboot is ur first reboot into download mode)
1. flash stock firmware
2. first reboot
3. install for provider reasons and then
4. second reboot (important: into download mode)
5. flash twrp
6. third reboot (important: into twrp)
7. flash zip-file (attached to this post)
8. reboot and wait....
now u should have an unencrypted system. the only thing is, u need to repeat these steps on firmware updates.
snowfirewall said:
Thank you.. Am not exactly looking for unencrypted partition. Am just confused whether it's expected to format data and no variety everytime or is it just one time for root?
Also I gone through the threads to find fix for this issue. But most of the people are suggesting to format data.
Any other better ways? Can we take backup of existing ROM from TWRP without root?
Click to expand...
Click to collapse
I recently started flashing my Poco X3 with a new rom and some mods, but I quickly realized that when I was flashing my G-Apps package that my /system partition didn't have the free space required to install this package.
I did a bit of research and found out that with TWRP or OrangeFox recovery you could increase the partition size by going into: Wipe > Selecting the partition you want > Fix Partition.
So the next logic step was to try and replicate the same thing on my own phone, but when I went on my custom recovery, I saw that my /system partition wasn't appearing, so I tried to manually mount it by going into the mount option but that did not work, also tried in the terminal by typing "mount /system" but that did nothing saying that "partition /system is not in fstab".
So now I'm completely stuck because to change my ROM I need to wipe the /system partiton which apparently doesn't exist and both recoveries do not work.
PS: I tried this method on all of the recoveries present on the Forum.
I'm asking you guys if you have any idea how to fix this issue or if I have to wait until someone releases a new recovery that is actually fixed ? Thank you.
AFAIK you can't and you shouldn't mess with system partition in any "old standard" way in Poco X3 NFC ... for now it will can make more damage than benefits... you should flash gapps with minimal size that can be safely flashed and install the rest from Play... you want to know more? learn about dynamic partitions used in our phone, I just know that recoveries are patched so people can't brick their phones anymore...
Hello, i have a Redmi note 9S which shipped with Android 10 out of box.. i'm using Dynamic System Updates (DSU) with unlocked bootloader to try custom roms and decided to modify some custom GSI to manually root it and customize some apps (modifications directly to system partition) but noticed that system partition can't be mounted as rw and gives error "wrong fs type, bad option,.." i can only mount it as ro.
I knew that this happens because ext4 partition formatted with EXT4_FEATURE_RO_COMPACT_SHARED_BLOCKS (so called ext4 dedup) and this prevent it from being mounted as rw, trying to extend system.img with fallocate and resize ext4 file system with resize2fs and then use "e2fsck -E unshare_blocks" seems to work but the phone can't boot and trying to create a new rw system.img also fail as device doesn't boot, also i noticed that GSI versions with "vndklite" can be mounted as rw but same thing, it fail to boot when flashed with DSU and the device reboot again to the main OS..
So i have two questions here:
1) is that happens because the device refuse to boot system partition without EXT4_FEATURE_RO_COMPACT_SHARED_BLOCKS as it's already shipped with Android 10 and support this out of box or this happens because of DSU and will boot if flashed with fastboot?
2) and most importantly how can i modify system.img and then apply EXT4_FEATURE_RO_COMPACT_SHARED_BLOCKS (apply shared blocks feature on the file system) like what custom roms developers do so i can boot a modded system partition?
Any help would be appreciated.. Thanks!
same question, did you find answer?