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:
Related
Hi,
After months of near perfect operation (HTC Desire running LeeDroid 3.0.8.2) my phone's SD card (Kingston 16GB Class 10) card all of a sudden became read only.
This had happened a couple of times in the past and after a chkdsk run the corrected file entries are fixed and the card is back to normal.
This time round even though there where a couple of fixes the rooted phone would not boot.
Since I had a ClockworkMod backup form a few days before I tried a restore. The restore process would start running, but then stop with an error that it was unable to format the sd-ext partition.
After a number of trials (and products) I used the gParted live CD to repartition the SD card. Even though gParted reports that is has correctly created the Ext3 partition when it refreshes it does not recognise the partition.
{
"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"
}
(https://picasaweb.google.com/lh/photo/5yRjrW6GS6PIXuQkls6XjtMTjNZETYmyPJy0liipFm0?feat=directlink) and
(https://picasaweb.google.com/lh/photo/5yRjrW6GS6PIXuQkls6XjtMTjNZETYmyPJy0liipFm0?feat=directlink).
Is this normal and how can I determine if the card is dead?
Thank you in anticipation.
Update:
I loaded the card into MiniTool Partition Wizard Home Edition and within this program the card (formated by gParted) is determined correctly. A Surface test of this partition returns that it is OK (screen shot: https://picasaweb.google.com/lh/photo/cZ2ET1Oz_3Df2geaE3rcM9MTjNZETYmyPJy0liipFm0?feat=directlink),
I'm updating the progress of trying to restore the phone (without success).
The check of the Fat32 partition also returned no errors.
I now tried importing a prior backup. The photo at https://picasaweb.google.com/lh/photo/__OUgtNbfs72dM_5L8ynztMTjNZETYmyPJy0liipFm0?feat=directlink (not clear) shows the progress of the restore.
The last two lines read as follows:
Formatting sd-ext...
Error while formatting /sd-ext!
Thankis.
I have a SanDisk Ultra 32 GB microSD HC-I card that I use in my Transformer Infinity tablet as a storage device. I had it setup as (1) 32 Gig FAT32 partition.
Well I messed around with the partition on it the other day and it no longer would work. I decided to just wipe the stick and create a new 32 GB FAT32 Partition.
The thing is, now all (partition) tools I have used says it is only a 30 MB stick and in a "RAW" format !!???
I have tried:
Windows 7 (64bit) Drive Manager and get this this result:
.
Code:
[B]C:\Users\John>chkdsk /X /F S:
The type of the file system is RAW.
CHKDSK is not available for RAW drives.[/B]
==========================================
Mini Tool Partition Wizard with this result:
{
"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"
}
==========================================
Easues Partition Wizard Shows this:
==========================================
I know the sectors must be messed up. I have tried a Low Level Format but it just tells me that 30MB is to small to Low Level Format.
What can I do to make the 32 Gig micro stick show up as 32 Gig (fat32) not 30 MB ??
Please help if you can.... I will try anything. I do not have Linux installed, but supose I could if needed.
Thanks !!!
Thibor69
Hi, i had the same issue.
My phone ran too hot and shut down on its own.
After that my mini sd was displaying only 30mb.
Nothing helped and i replaced it under warranty.
I am trying to mount my System partition with write partitions on my Google Pixel (fully rooted with Magisk).
I have tried the following commands:
$ su
# mount -wo remount /
and I got the error
Code:
'/dev/root' is read-only
I also tried:
$ su
# mount -wo remount /system
And I got the error:
Code:
'/system' not in /proc/mounts
Also after flashing things in TWRP I get failed to mount /system
And failed to mount /vendor
Is there any way I can remount the partition with write permissions?
If not is there a Magisk module that can edit it Systemlessly?
EDIT: I've done some research and I found out that you can't mount the partition as rw so to edit the files you have to make a Magisk module that replaces the files with the modded versions.
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"
}
lebigmac said:
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/
Click to expand...
Click to collapse
while trying to flash your zip , I'm getting an error. I have Redmi k20 pro with Corvus Android v11 flashed. But it worked for many others...
@warhawk971 I just responded to you in the project thread. Please try installing it manually and report back any errors. Thanks!
lebigmac said:
@warhawk971 I just responded to you in the project thread. Please try installing it manually and report back any errors. Thanks!
Click to expand...
Click to collapse
Thanks. I'll report you further...
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.
Hi,
i just bought my gf a samsung evo 128gb sd card for her Nokia 5.3. At first it said its damaged and the formatting in android didnt do anything. So then i tried to use PC and saw that there was no file system at all, but even after formatting it it didnt work. Then i tried using adb to force it to format which kinda worked.
{
"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"
}
I read online both to use the id you get from list-disks aswell as those you get from list-volumes.
What did work was the volume id (179,64). However using "sm partition disk:179,64 mixed 90" was the highest number that worked, since sm partition disk:179,64 private" didnt work at all. The device simply didnt recognize the sd anymore.
And even now the device claims that most of the storage is already being used, despite the card still being empty.
What can i do to fix it and have the entire sd as internal storage??
When a SD-card is accepted as adoptable storage, the Android OS deletes the contents and writes a GUID partition table that defines two partitions:
A small empty android_meta partition reserved for future use. The GUID of the partition type is 19A710A2-B3CA-11E4-B026-10604B889DCF.
A large android_ext partition encrypted with dm-crypt and formatted with either ext4 or f2fs depending on kernel capabilities. The GUID of the partition type is 193D1EA4-B3CA-11E4-B075-10604B889DCF.