Database Info

MMC fried or how to recreate PIT on the Nexus 5

Hi community,
I desperately need your help now. After trying to update to the most recent PN build, like I did a million times before, I came out with a corrupted /cache partition.
TWRP - and in fact neither stock recovery or CWM - can no longer mount the /cache partition on my Nexus.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So I thought going back to stock would iron the error out, but it didn´t. So I decided to dig a bit deeper and had a look at the partition table.
After wiping the cache parted comes up with
Code:
Error: /dev/block/mmcblk0: unrecognised disk label
I have to manually restart recovery and then it shows me the partition table:
The cache partition should be ext4 formatted, but it is not...
So I decided to recreate the cache partition and format it as ext4:
Code:
parted -s /dev/block/mmcblk0 rm 27
parted -s /dev/block/mmcblk0 mkpart primary ext2 1298MB 2032MB name 27 cache
The filesystem check succeeded this time, before e2fsck told me something about a bad superblock...
But all that to no avail, if I flash all partitions manually in fastboot, my Nexus starts, but it starts forever...
Regarding this little tool, my mmc should be in prime condition, but I don´t know how trustworthy that is!?
Any help would be much appreciated!
Is there a way back or do I have to say goodbye to my hammer :crying:

how to format data to F2FS?

when i installed some rooms i did bricked and broke my data
-when i try to install anything via TWRP shows "failed to mount data (invalid argument)"
-when i try wipe data TWRP shows "failed to mount data (invalid argument)"
-when i try wipe system/data used stock recovery-FAILED
I know that some version TWRP can be formatted on f2fs, but none work on my phone.
does anyone know what to do with it?
Help me
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Mysia said:
when i installed some rooms i did bricked and broke my data
-when i try to install anything via TWRP shows "failed to mount data (invalid argument)"
-when i try wipe data TWRP shows "failed to mount data (invalid argument)"
-when i try wipe system/data used stock recovery-FAILED
I know that some version TWRP can be formatted on f2fs, but none work on my phone.
does anyone know what to do with it?
Help me
Click to expand...
Click to collapse
Try changing twrp version..

I tried a lot of versions TWRP. All does not work.
On my phone works only this three version dedicated to honor 8 https://eu.dl.twrp.me/frd/ , but it's without function format to f2fs

My phone is Honor 8 Lite (model PRA series), not exactly same as yours.
This works on my phone: at TWRP shell,
mkfs.f2fs /dev/block/mmcblk0pxx
where xx is the data partition number.

Did someone successfully mount system as r/w ?

I tried to install Micro-g and still can't figure out if is it possible to mount system as read-write on OxygenOs 10. Standart command to do this
Code:
mount -o rw,remount /system
and many others from internet dont work. Is it possible to do this on OxygenOs 10?

Odalric said:
I tried to install Micro-g and still can't figure out if is it possible to mount system as read-write on OxygenOs 10. Standart command to do this
Code:
mount -o rw,remount /system
and many others from internet dont work. Is it possible to do this on OxygenOs 10?
Click to expand...
Click to collapse
No, OOS is read only. I gave up and installed PixelExperince 10.0 , removed all google stuff, installed microg, patched services.jar and all set .

Here is the solution to your problem my friends. Enjoy!
Works like a charm in Android 10 and later. Now my system, vendor and product partitions are read-write!
Use at your own risk!
https://forum.xda-developers.com/t/script-mount-system-as-read-write-android-10.4240703/
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

While the above might work, you don't need to extract the whole super partitions. You can do it manually on whatever partition you wish.
Make Dynamic Partition Read/Write (github.com)

@Lossyx that's interesting thanks for the feedback. Yes you're right it should be possible to do the whole process directly on the device without having to pull the whole super.img first. But it shouldn't really matter if you do it with the help of your computer or directly on the device itself.
However people decide to do it, what's important is that the Android 10+ users get write access to all their partitions again so we can customize our device to fit our needs and remove all that bloatware and then some.

TWRP error E1001: Failed to update system image.

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
While trying to flash a ROM or Wiping TWRP is giving me the "E001: Failed to update system image , failed to mount '/product' , '/system_root' , '/odm' , ' /vendor' errors.
Device: poco x2
Even tried orange fox, but cant load into the ROM, it again boots into orange fox.

you must format data every time you do anything with twrp or orangefox , because of decryption.

jogeo said:
View attachment 5269507
While trying to flash a ROM or Wiping TWRP is giving me the "E001: Failed to update system image , failed to mount '/product' , '/system_root' , '/odm' , ' /vendor' errors.
Device: poco x2
Even tried orange fox, but cant load into the ROM, it again boots into orange fox.
Click to expand...
Click to collapse
I get the same problem. Can you help me ? How to solve it ? Thank you !

dr.rom said:
you must format data every time you do anything with twrp or orangefox , because of decryption.
Click to expand...
Click to collapse
Will Format data erase all pics, files, and apps installed ? Thank you !

Question Changes applied to /system get lost after rebooting the device

I have a rooted device Xiaomi Poco X3 Pro.
I am copying the the file to /system/bin.
The file stays only until I reboot device. The same with TWRP recovery.
What's the correct way to solve this problem?
What I figured out so far the path /system/bin is using tmpfs system. This would explain why changes do not stay. How can I modify it?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

fastman92 said:
I have a rooted device Xiaomi Poco X3 Pro.
I am copying the the file to /system/bin.
The file stays only until I reboot device. The same with TWRP recovery.
What's the correct way to solve this problem?
What I figured out so far the path /system/bin is using tmpfs system. This would explain why changes do not stay. How can I modify it?
View attachment 5440407
Click to expand...
Click to collapse
[GUIDE] How to make your System RW / Super R/W read/write-able
Welcome to the one and only, the original, universal SystemRW / SuperRW feat. MakeRW / ro2rw by lebigmac This script removes the read-only lock of all partitions embedded in the super partition of your stock firmware. This allows you to mount...
forum.xda-developers.com

Thanks, I may try it later.
I have read about the system-on-root.
Because the file should be copied by other users as well and executed it will make better sense to put this file under /data instead.