yashsingh1/xdaforums huggingface dataset:
[Android General] xiaomiA1:
I have also followed the steps with no success.

I executed the steps manually by adb shell and added the verbose flag to see what happens.

tissot:/ # e2fsck -fvp /dev/block/mmcblk0p49
e2fsck: Bad magic number in super-block while trying to open /dev/block/mmcblk0p49
/dev/block/mmcblk0p49:
The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem. If the device is valid and it really contains an ext2/ext3/ext4
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>
or
e2fsck -b 32768 <device>

After that I executed e2fsck -b for every superblock with no success.

8|tissot:/ # e2fsck -b 229376 /dev/block/mmcblk0p49
e2fsck 1.43.3 (04-Sep-2016)
e2fsck: Bad magic number in super-block while trying to open /dev/block/mmcblk0p49

The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem. If the device is valid and it really contains an ext2/ext3/ext4
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>
or
e2fsck -b 32768 <device>

Next, I execued fsck.f2fs

tissot:/tmp # fsck.f2fs -f /dev/block/mmcblk0p49
Info: Force to fix corruption
Info: No support kernel version!
Info: Segments per section = 1
Info: Sections per zone = 1
Info: sector size = 512
Info: total sectors = 46521295 (22715 MB)
Can't find a valid F2FS superblock at 0x0
Can't find a valid F2FS superblock at 0x1

When I try to format from twrp (it does not matter which file system type), it stucks when writing superblocks

mke2fs -t ext2 -b 4096 /dev/block/mmcblk0p49
mke2fs 1.46.2 (28-Feb-2021)
Creating filesystem with 5815161 4k blocks and 1455328 inodes
Filesystem UUID: 33062afe-6ed7-11ec-847c-7d841f0a278a
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000

Allocating group tables: done
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information:

When execute the format command from fastboot, everything seems to be fine.

fastboot format userdata
mke2fs 1.46.2 (28-Feb-2021)
Creating filesystem with 5815161 4k blocks and 1455328 inodes
Filesystem UUID: 33062afe-6ed7-11ec-847c-7d841f0a278a
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000

Allocating group tables: done
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done

Sending 'userdata' (180 KB) OKAY [ 0.048s]
Writing 'userdata' OKAY [ 0.012s]
Finished. Total time: 0.504s

Nevertheless I cannot mount the data partition after booting into twrp.

There seems to be an issue with the partition table and or the superblock of the data partition.

I can only boot into a pretty old trwp version 3..3.1-0, newer release stuck in trwp splash screen.

Any ideas to get my devices (Xiaomi A1) working?
[Android General] pandmc:
Just flash your phone and all done
[Android General] philipjan26:
Also experienced this. Any idea to fix?
[Android General] macizet_legacy:
Changing Filesystem works, but how to repair it without formatting data? because i want to have possibility to update rom.
[Android General] 1999romelx:
It works but i got stuck on Recovery mode.

Xiaomi K30 (Phoenix) | MIUI 13 EU BETA
[Android General] Dazzling_Dazzla:
Nope, you lose your data. I learned the hard way. And every time i go back into TWRP I still have 0mb showing for internal
[Android General] Dazzling_Dazzla:
Yes, in my case the data was lost. Im running pixel experience A12 on Redmi Note 10 pro and I had to put the file system back to F2FS not EXT4 (EXT4 and my phone would bootloop into twrp, after changing it to f2fs the phone would boot back into PE. changing the file system of data partition formats it so you lose all apps ect and the phone is like new when you open it to google, you have to go through google setup screen and install all apps again). And when I boot back into twrp after all this it still shows 0mb. Next time I will not bother with this custom rom malarkey. If I want a puzzle to solve Ill go and buy this (https://tinyurl.com/3z69dz8y), and Ill pay someone to put a custom rom onto my phone. its been one hell of a mission.
[Android General] Dazzling_Dazzla:
Yep serious mission, I spent days getting my phone setup and then wiped it all. I dont want to set it all up again not having fixed twrp
[Android General] Antl_79:
Gracias Funciono en mi Redmi Note 10 (Mojito)
[Android General] JESUSOM5:
Como lo hiciste? yo no he podido
[Android General] haydent:
thank you, worked on nexus 10 manta twrp
[Android General] LON3LY_D3VIL:
man that helped me alot it works just fine for SMJ610F android 10 Q
[Android General] _tanim_0011:
I can't even format data from the wipe option. will this fix my problem?
[Android General] JEETVYAS021:
same problem

please reply
[Android General] alecxs:
guys use your brain, this isn't any fix at all - it's a workaround
[Android General] hadyjsx:
Thank you! This worked for me.
[Android General] d0nger:
Just use FORMAT DATA and use a TWRP that can actually decrypt your phone... Then you don't need to do anything else.
[Android General] Xda889:
Good evening, I have a problem on a Lineage 14 rom mounted on Huawei p9 lite.

I installed Lineage os 14 by replacing the VNS-L31C432B161 version.

I have found that I can no longer restore data from Huawei backup.

I tried to format the data via Twrp but it comes out "Unable to mount data".

I have verified that the date shows 0 mb and it is not possible to format. Can I no longer format in any way? Kindly help me to solve this problem? Thank you have a nice day.

Good evening, I have a problem on a Lineage 14 rom mounted on Huawei p9 lite.

I installed Lineage os 14 by replacing the VNS-L31C432B161 version.

I have found that I can no longer restore data from Huawei backup.

I tried to format the data via Twrp but it comes out "Unable to mount data".

I have verified that the date shows 0 mb and it is not possible to format. How is it possible to format everything from the beginning without encountering an error on the given partition?

Can I no longer format in any way? Kindly help me to solve this problem? Thank you have a nice day.
[Android General] Xda889:
Could anyone help me?
[Android General] SGH-i200:
Try this:

https://xdaforums.com/t/howto-guide-repairing-corrupted-data-partition.2577447/
[Android General] Xda889:
Good evening, I tried to follow the procedure, but on the huawei p9 lite those commands do not start.

Can you tell me the correct procedure for the p9 lite? Thank you.

Will you help me? I'm in serious trouble.
[Android General] markanderson:
Hello,

The simplest approach to fix the unable to mount storage TWRP issue is to change the security password of your phone.

If you are still experiencing TWRP unable to mount storage, and internal storage showing as 0mb, follow the below given steps:

1. The first thing to try is if somehow your internal storage became encrypted when using a legacy screen lock method.

2. After that, go to your Android device’s Settings > Security > Screen Lock, and change your screen lock method to either Pass or Pin. Create a new one.

3. Then, Reboot into TWRP, and it should ask for a password – enter the password or pin you just created.

4. After that, TWRP will attempt to decrypt your device’s internal storage, and if it succeeds, you should not have further issues. However, if this does not solve your issue of “unable to mount data, internal storage 0mb”, continue with the rest of this guide.

5. Then Reboot your device into TWRP again & navigate to Wipe > Advance Wipe > Data, and choose Repair or Change File System.

6. After that, press Repair File System to see if this fixes the issue. If not, continue.

7. Then press Change File System, choose Ext2, and swipe to confirm.

8. Now switch back to Ext4 and swipe to confirm.

9. In the end, Go back to TWRP main menu, then the Mount menu, and check if your partitions can be mounted now.

If you are still unable to mount your partitions, you need to repair Internal partition, which will most likely wipe your internal storage.

Note : Please make a back-up of your data before proceeding to the above steps.

Hope this helps!
[Android General] SGH-i200:
Am I correct?

7. 'Change File System' will DELETE your data!

6. 'Repair File System' will NOT DELETE your data
[Android General] Xda889:
Good evening, unfortunately I am unable to perform these procedures in any way. It keeps giving Failed message if I try formatting and modifying the file system.

I state that I have a huawei p9 lite 2016 that mounts Twrp 3.0.2.0.

Could it be the Twrp version failing to format the file system? Will you give me any other help? Thank you.
[Android General] Xda889:
Now it would no longer make me remove the os 14 lineage rom with another .... it keeps giving errors and I can't go to the given partition. Any help is well helped.
[Android General] Xda889:
It is no longer possible to format the internal memory. Please help me.
[Android General] Fatihh57:
Thank you mate awesome!

Work it realme 3 pro
[Android General] dudos:
Just got my phone out of boot loop fixing "data". Super thanks for the helps.
[Android General] Kien Dinh:
Thanks :) It's worked
[Android General] pmbrs:
Thanks, works for me Xiaomi Mi 6 on lineage-20.0-20230126-nightly-sagit-signed!

BUT, BUT, not permanently! When I reboot the system happened the same.

I'm using Xiaomi Mi 6(sagit) Lineage-20.0-20230202-nightly-sagit-signed (Android 13) with MindTheGapps-13.0.0-arm64 (suggested by Lineage OS).

How can I change permanently?

Thank you
[Android General] pmbrs:
But after starting the smartphone, then coming back to the recovery system the problem again occurs.

How can I solve this problem permanently?

Does anyone have a solution?

Thank you
[Android General] alecxs:
it's not a problem. your TWRP simply cannot handle LineageOS 20.0 encryption (yet).

the title of this thread is misleading. it's neither a fix nor a permanent solution (btw outdated, recent devices have f2fs file system type).

it's simply a temporary workaround to remove encryption. up on next boot your device becomes encrypted again.

for permanent workaround, disable encryption (if you can live without).

for permanent fix, wait for TWRP is released that is capable of decrypting Android 13.
[Android General] Chris3445:
Hello I rooted and unlocked and rooted my LG g8x i had to Do corssflashing to get it to the rite firmware to rooted the phone came with lmg850um20o firmware and the firmware im at now is a can one its the lmg85020j one im at now but whats happening is this if any one can help or now why this is happening I would really appreciate the help thanks
[Android General] pmbrs:
Thank you so much for your response @aIecxs.

I will stay in this situation until TWRP is released which is capable of decrypting Android 13.

:)
[Android General] HJR_reincarnated:
It works but it erases everything including the os that is installed in my poco x2 and after rebooting the same problem happens again, internal storage (0mb) I'm unable to switch rom because of this, do someone knows any solution??
[Android General] Nimda672:
worked for me as well
[Android General] pusher2308:
Hello,

I hope someone can help me with the following problem:

I wanted to install a custom rom but in twrp got the error message "unable to mount data partition" so I did the following:

1) Reboot the device into TWRP Recovery.

2) Go to Wipe menu.

3) Go to Advance Wipe.

4) Select Data and go to Change File System.

5) Select Ext2 and swipe to confirm.

It seems the formatting wasn't done properly. I had no chance to get back to TWRP. When I boot into TWRP it stucks at the boot screen.

What can I do about it?

Kind Regards

Michael
[Android General] marcelmo:
Hi, I am stuck somehow in with this data partition problem. If I format data, and I reboot to recovery, it is able to mount data and save settings. But, when I boot to OS, I have walk through the first setup. No problem, but... when the setup is complete (with Google account) and I reboot to recovery, the data partition is not mounted. So, changing format to some format and back to ext4, and after that I am able to mount data partition, until I do the first setup when booted to OS, and so it continues...
[Android General] SaikiK:
Thanks a lot, worked for me.
[Android General] Nasrullah 83:
Hi guys,

I have star2qltechn and the system needs to be mounted, if I do so, will it wipe my data (stock ROM)?
[Android General] Baoprohp91:
thanks, works for me S7 (SM-G930S).
[Android General] Anonymous Potato:
All the steps from 1 to 9 will not delete all my data (like internal storage and the custom ROM I've applied), right?
[Android General] DarkDuck007:
Thanks bud, you saved me.
[Android General] Spuqui:
Thank you for explaining properly what is going on.

I would disable encryption to create a full backup and then reenable it, if I knew how to.

Quick question: how far back would I need to go in Lineage version from 20 so that TWRP can decrypt data?
[Android General] alecxs:
two notes: the only method to "disable" encryption is reformatting and start with a fresh unencrypted userdata partition. this requires patched fstab, encryption disablers do that.

encryption keys are downgrade protected, it's not possible to go back to older encryption that TWRP supports (at least not without erasing data) - wait for TWRP supports the newer encryption.

as you quoted my post from about a year ago, the chances are high you will find working TWRP that supports your encryption as of today ;)
[Android General] gigge:
THX !! :D
[Android General] Yusuf T-Deen:
Only sensible answer I have seen here. Everyone is just blindly following the same steps without checking. I realised my data partition is f2fs so I didn't change the type. I've also removed encryption but TWRP still cannot mount the sytem and shows internal memory as 0 MB.

I've asked my question in the Xiaomi 11T Pro forum (https://xdaforums.com/t/how-to-decr...ystem_ext-product-and-vendor-in-twrp.4651310/). I think this is a problem with TWRP and Android 13. Is there any other recovery (like OrangeFox) that currently supports decryption on Android 13 and 14? The versions of TWRP I used are made specially for Vili and to allow decryption but neither are working.

Is there something I missed? Any help would be greatly appreciated :)
[Android General] SaidJan:
Warning:

This will ERASE ALL DATA and ROM.
[Android General] svenagain:
cheers! this saved me
[Android General] migafel:
impecable tu explicacion me ayudo mucho muchisimas gracias

Mod Edit: English Translation Below

Your explanation is impeccable, it helped me a lot, thank you very much.
[Android General] PrateekPanwar64X:
I disabled my phone's Lock (pattern) and now can access storage in TWRP.
[Android General] Snakeforhire:
Try to find another custom recovery : most often tis tpe of isue is due to an unofficial version not being able to handle te encryption of /data. It takes a few weeks to a few months after a device's launch for "proper" versions to be released)

Alternatively, in the past I've been able to fix this issue either by dirty-flashing the exact same ROM over the messed-up one by using an external SD mounted via OTG, or by erasing the /misc partition, or restoring /misc and/or /metadata (from an earlier backup).

In extreme cases it takes a wipe of the /metadata partition to right things up, but you're almost guaranteed to lose the data on the internal storage if you do this.

The lesson here is : before you go playing with 3rd-party OS'es, ALWAYS make a backup of your internal storage on some external media (I'm partial to Micro-SD over OTG adapter myself, which works everywhere (if you don't forget it at home !), even if it is kinda slow to transfer to/from it's still better than MTP connection, and about on par with Wifi'ing the backups to/from my fileserver). "Two is one, one is none." 😁
[Android General] fede01_8:
You're replying to a 5 years old post. I don't even remember what device I owned back then. wtf?!
[Android General] Snakeforhire:
It might be useful to someone else stumbling upon the same issue, for one. Second : you're welcome, ye ingrate (censored) !!! 🤬
[Android General] Z3l1x:
It (the original 5-year old solution) worked for me, but when I try to boot Android, the startup screen says "Decryption unsuccessful" and I can only fix it by pressing "Reset Phone", which undoes the work in these steps, meaning I once again can't mount storage through TWRP. Any ideas on how to fix this without screwing it up for Android? I have a Moto 5G S+, btw.

Thanks in advance
[Android General] Nigo10:
thanks mate, u saved my life hahaha
[LG G6 Questions and Answers] webking:
Hi,

I've got the latest update of Android 8 to my LG G6 .

Now I get some strange behaviour:

I'm watching a video in the gallery. After the video, I want to go back to the gallery, to view other stuff. But, the back button sends me back to the main screen!

If I open the gallery again, I go back to the same video I watched.

Only by cleaning all running apps, I can get to the main gallery page again.

I don't see this issue when watching photos.

Any idea?!

It's super annoying :(
[Xiaomi Redmi Note 5 / 5 Plus Questions & Answers] KaranBhatia:
What is the difference between China/India/global MIUI ROMs and can I interflash stable/beta builds between each other?
[Samsung Galaxy Note 9 Guides, News, & Discussion] lawtq:
Ok we all know what to do. Post screen on times and general experiences here, please.
[Samsung Galaxy Note 9 Guides, News, & Discussion] bat0nas:
Here's my first real life experience (everything's ON and configured.. haven't disabled any bloat yet; always on mobile data).

5hrs of SOT - more than enough for me.View attachment 4575764
[Samsung Galaxy Note 9 Guides, News, & Discussion] pigglett:
Image is giving a 404 error
[Samsung Galaxy Note 9 Guides, News, & Discussion] bat0nas:
Imgur url:

https://imgur.com/a/UX2UzxF
[Samsung Galaxy Note 9 Guides, News, & Discussion] lawtq:
With always on display on for all those hours... That's not bad at all! Interesting
[Samsung Galaxy Note 9 Guides, News, & Discussion] Venom0642:
Decent battery life AT&T Note 9 512GB

View attachment 4579339

Running On My Galaxy Note9 SM-N960U Wicked Venom
[Samsung Galaxy Note 9 Guides, News, & Discussion] lawtq:
On course for 10hr battery life sot. What I expected for that battery size. That's good
[Samsung Galaxy Note 9 Guides, News, & Discussion] Jammol:
Not too bad, used it for 9 straight hours today and had a 8 hour SOT. I even talked on the phone for an hour today. Stand YouTube for about the first 3 hours, streamed Google play music the rest of the day, also finished installing my apps and such.
[Samsung Galaxy Note 9 Guides, News, & Discussion] Venom0642:
Very Decent battery life on my AT&T Note9 512GB Snapdragon can't complain.

View attachment 4579521

Running On My Galaxy Note9 SM-N960U Wicked Venom
[Samsung Galaxy Note 9 Guides, News, & Discussion] smentoma:
Please mention chipset. Exynos or snap when you post battery
[Samsung Galaxy Note 9 Guides, News, & Discussion] lawtq:
Yes needed

But you can tell who has what above by the location with their profile
[Samsung Galaxy Note 9 Guides, News, & Discussion] sandeeppathak007:
Which font is that, looks really nice
[Samsung Galaxy Note 9 Guides, News, & Discussion] Zanr Zij:
Black theme and Video are Amoled friends :)
[Samsung Galaxy Note 9 Guides, News, & Discussion] Venom0642:
Sonysketch Font

Running On My Galaxy Note9 SM-N960U Wicked Venom
[Samsung Galaxy Note 9 Guides, News, & Discussion] learn2route:
3rd days using the battery. So far battery life is very good View attachment 4580439
[Samsung Galaxy Note 9 Guides, News, & Discussion] sandeeppathak007:
Is it from the Samsung app or some other method because I have not rooted my note yet
[Samsung Galaxy Note 9 Guides, News, & Discussion] suzook:
10 hours SOT??? At what brightness? Thats awesome.
[Samsung Galaxy Note 9 Guides, News, & Discussion] Venom0642:
If you mean me at 95% brightness, auto turned off.

Running On My Galaxy Note9 SM-N960U Wicked Venom
[Samsung Galaxy Note 9 Guides, News, & Discussion] eastsidebiz:
2nd day with my note 9.

drained it when i received the phone then charged to full.

did my thing, heavy music/media/browsing and gaming.

total use in hand was about 6 hours. The phone got warm. so much for water cooling.

Im now at 15 hours, 15% left.

Happy, but could be happier
[Samsung Galaxy Note 9 Guides, News, & Discussion] Zanr Zij:
Oh black theme help not much
[Samsung Galaxy Note 9 Guides, News, & Discussion] michelino159:
What theme are you use?Thanks!
[Samsung Galaxy Note 9 Guides, News, & Discussion] Zanr Zij:
After tried some more times, I know that anyone use wifi most of time will get much better than 4G ( the diferrences is much bigger than other phones ). The same situation with indoor and outdoor.
[Samsung Galaxy Note 9 Guides, News, & Discussion] alex989898:
I would say that's true but be carefull.

From what I see on my phone, a strong and stable 4G network (or, certainly Edge, maybe not 3G/H+) hasn't too much impact on battery life (similar to WiFi I would say maybe a bit better but not sure).

But when, 4G signal become weak (as it is in my apartment), I see a real difference with WiFi. That's why I use phone over WiFi when at home.

For indoor/outdoor, I would say it's normal because AMOLED screens (at least in the past, but I haven't read on this subject in a while) have a power consumption for luminance curve that's not completely linear.
[Samsung Galaxy Note 9 Guides, News, & Discussion] nathlynn22:
Swift installer
[Samsung Galaxy Note 9 Guides, News, & Discussion] @rbiter:
You are assuming way too much and getting defensive. Every single SOT I have posted is not padded. I have not used power save mode yet. BT is on from 6a until at least 5 and usually used about 3-7h a day. LTE only. GPS and high accuracy one. The only padding I've done is black theming but that is what I prefer and it is just bonus AMOLED benefits from this. Many of SOT have been heavy YouTube usage over LTE and all my sync'ing is on aside from Google play store because I hate it when my apps get broken. I've gotten 24h before on Note4 by accident. My note4 was blacked out and I was pulling down SOTs like I am now but the devs we're not updating anything so I had to move on.
[Samsung Galaxy Note 9 Guides, News, & Discussion] lawtq:
There's your drainer, Google maps. Looks ok
[Samsung Galaxy Note 9 Guides, News, & Discussion] nathlynn22:
Enjoying it though too much to set up in 1 go haha.

You enjoying the SnapDragon version.

It was on maps and playing music so was being used well at the time. Didn't charge it in my car like I usually do wanted to see how it would get on. I'll have to get an in car wireless charger.

Sent from my ONEPLUS 5
[Samsung Galaxy Note 9 Guides, News, & Discussion] lawtq:
I admit I'm impressed with the snapdragon

The only power saving I have on is the minus 10% screen brightness. Every year screens are brighter, they trying to blind us?

Includes about 15 minutes of tekken 6 psp which is nowhere to be seen in stats. I really don't like Samsung battery stats. Not detailed. Huawei do a much better job there
[Samsung Galaxy Note 9 Guides, News, & Discussion] Zanr Zij:
People can get sot about 10h or more on stock Rom should out of here. It is not real moderate usage result without battery saving mode
[Samsung Galaxy Note 9 Guides, News, & Discussion] enigma79:
For Oreo max battery life is 8-9 hors screen,AOD is off.Britges is automatic mode.
[Samsung Galaxy Note 9 Guides, News, & Discussion] desolli:
:good:
[Samsung Galaxy Note 9 Guides, News, & Discussion] karan2012:
I am now somewhat satisfied with battery life will just reset it once again as I think that will help me get more of phone.

Exynos
[Samsung Galaxy Note 9 Guides, News, & Discussion] themaximillian:
Here's mine, Exynos

Skickat från min SM-N960F via Tapatalk
[Samsung Galaxy Note 9 Guides, News, & Discussion] @rbiter:
60h charge.