Related
One day, about 2-3 weeks ago, on my way to home, I decided to install an other ROM (5.1.1 ivanchi -> CM9). Went straight into recovery (TWRP 2.8.5 or 6) and formatted everything except microsd, everything seemed to go as planned. Then proceeded to install the ROM; it gets stuck, can't get pass the booting screen even after 20-30 minutes. Force-Reboot into recovery and receive "unable to mount /data | /system | /cache error". Tried changing fs-type of /data /cache /system to any other type, no success.
Got back home, tried installing RUU. Got stuck at 39%. every. single. time. !! Tried an older RUU, same response.
Then tried even oem lock + flash recovery_signed.img + boot boot.img with fastboot and then RUU install. Then again with unlocked bootloader. Still no! But, I didn't tried lock + recovery signed + boot + S-On, because I am afraid not to be able to regain S-Off at this state.
Even tried a parted format, implying that one guy managed to make it work in the end. See topic here : link.
Tried doing guy's steps but after parted /dev/block/mmcblk0 I receive Error: Can't have overlapping partitions. Tried then parted /dev/block/mmcblk0p23 (userdata), it works, and if I try mkfs/rm on partition 1, it says it's in use (p23p1 ...).
Output:
~ # parted /dev/block/mmcblk0p23
parted /dev/block/mmcblk0p23
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0p23
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
print
Model: Unknown (unknown)
Disk /dev/block/mmcblk0p23: 1253MB
Sector size (logical/physical): 512B/512B
Partition Table: loop
Number Start End Size File system Flags
1 0.00B 1253MB 1253MB ext4
(parted) rm
rm
rm
Partition number? 1
1
1
Error: Partition /dev/block/mmcblk0p23p1 is being used. You must unmount it
before you modify it with Parted.
(parted) mkfs
mkfs
mkfs
Warning: The existing file system will be destroyed and all data on the
partition will be lost. Do you want to continue?
Yes/No? yes
yes
yes
Partition number? 1
1
1
Error: Partition /dev/block/mmcblk0p23p1 is being used. You must unmount it
before you modify it with Parted.
I can format my /data /system /cache one at the time, after doing reboot recovery and that's only in CWM 6.0.1.2. But this CWM isn't able to install ROMs somehow, wether it gets stuck of just plain fails. So, if I want to install a ROM, after the format, I have to install 4Ext (latest) recovery and do it there. Install everything from recovery, boot, sign in for GApps etc etc and while trying to install apps from Google Play, after about 4 to 6 apps, it gives a black screen, leaving no option but remove battery and reboot. Do that and get stuck on bootsplash / bootscreen. Everytime!
If then I try formatting paritions using 4Ext most of the time it fails, making them unmountable again after all.
Tried everything mentioned running PG58IMG with firmware 3.33, Hboot 1.27.1100, worldwide english (.104.). Tried fashing rom.zip as the PG58IMG.zip from fastboot in rebootRUU (gets stuck at [RUU]WP,dzdata,0) and now even from sdCard (gets stuck at [6] USERDATA).
I dug furthermore into bricked Sensation, seeing a QHSUSB brickbug (thread). It is refeered to be a bootloader brickbug; problem which I am not facing right now. Eventho, followed OP's instruction my freshly installed Ubuntu 14.04 can't detect my HTC. Also did some of the YouTube instructions, connecting sdcard's plate with lower pin from the back (trolled?!) (video), yet nothing.
Out of disperation, asked hinxnz and rzr86, and both of you adviced me to try thread 1 or 2 (relying on sdCard as primary/sec partitions). Good advices but I don't consider this be the best solution for this problem; STILL HAVE HOPE MAKING INTERNAL SD TO WORK! :d
ASK ME ANYTHING REGARDING MY PROBLEM! Will post every bit of information you consider relevant.
PLEASE HELP!
u tried ruu, didnt work, tried firmware, didnt work. @rzr86 and @hinxnz gave u those guides coz its the only known way to fix/bypass that problem on xda. maybe there is another way but no one has found it yet. u could take ur phone to a repair shop, pay bout a hundred bucks, connect it to jtag and hope for the best, but that might not even flash partitions back.
personally i dont see how twrp is still allowed to be downloaded on xda in the sensation thread coz it keeps killing peoples phones. that jus my opinion tho.
Atm my phone is literally bricked, QHSUSB brick because of my stupidity... Maybe I will make it to work again; anyways...
For the partition problem, don't the HTC has some kind of .pit files like Samsung does? They should! Also, what if someone with a 'healthy' Pyramid does a dd of the /dev/block/mmcblk* for those with fk'd partitions to use ?
Hi, one more here with wrecked partitions by TWRP factory reset....
Trying to Ruu the Sensation, but RUU has been getting stuck in the process ... I'll edit if I success.
Thanks for all the info out htere!
Edit: no success, even tried at last to fix partitions (parted and fdisk) via ADB, device is now dead. So sad HTC or any ever gave the details for the partition table, a simple script might have solved this.
I'm just catching up on this one.
If I read this right,the information on the partitions was trashed by TWRP recovery?
There was a member that stated the HTC Desire used to be able to have it's partitions reconfigured,IIRC.
Perhaps this is the first step to achieving that with the Sensation?
Sent from my SM-N915W8 using XDA-Developers mobile app
I'm too woried nowadays....i got the error can't mount system,data,cache inmy xolo a600...i can't flash custom rom or can't do factory data reset...but when i try to factory reset using my stock firmware recovery it's done...but in twrp & cwm recoverys say can't mount system,data,cache...i also can't connect my device to pc using usb mode,mtp...my pc said unknown device detected...what to do?...i just really tired & tensed please please please guys give me the solution...please...!!
Hi, i have a problem with my sensation.. When i tried to do factory reset from phone settings including SD card (i didnt needed anything from sd) before installing new rom, something went wrong. After that format my phone doesnt boot any more, it get stuck on rom logo. I still can enter bootloader and recovery (TWRP 2.8.6) but when i try to use factory reset (wipe) again in recovery it shows me this (i cant upload images so i took everything in text):
Updating partition details...
E:Unable to mount '/cache'
E:Unable to mount '/data'
...done
Full SELinux support is present.
E:Unable to mount '/cache'
E:Unable to mount '/cache'
MTP Enabled
Formtatting Cache using make_ext4fs function.
E:Unable to mount '/cache'
Formtatting Data using make_ext4fs function.
E:Unable to mount '/data'
Wiping android secure
Updating partition details...
E:Unable to mount '/cache'
E:Unable to mount '/data'
E:Unable to mount '/system'
...done
and on top i get message Factory reset complete - successful.
Then when i try to install rom i get this:
Format and Mount System, Mount Data...
Symlinks and permissions...
set_metadata_recursive: some changes failed
E:Error executing updater binary in zip '/sdcard/' rom.zip
Error flashing zip '/sdcard/rom.zip'
Updating partition details...
E:Unable to mount '/cache'
E:Unable to mount '/data'
E:Unable to mount '/system'
...done
And there i get zip install complete - failed... Is my device briked? I dont even know what should i do.. I tried to search something similar but didnt realy found any solution. Maybe anyone knows this problem?
Bootloader info:
-Firmware-3.33-
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.1100
RADIO-11.24A.3504.31_M
OPENADSP-v05.6.0.2226.00.0418
eMMC-boot
Jan 13 2012.17:33:34
P.s. Sorry for my english
Sounds like good old "there goes your motherboard". I've had it happen last week or so.
you used wipe option from twrp
big mistake
see here if you have any luck
http://forum.xda-developers.com/htc-sensation/help/recovering-data-mount-issues-t2859588
pay attention to the last posts
As @Harakhti and @rzr86 said, you are in deep trouble, just like many of us. Unfortunately, no one knows a solution to this problem. It is an old phone and most Android tech "wizards" have upgraded to newer devices, so I am not so sure we will ever get one. People here try their best to come up with solutions (and are being helpful), but the diagnosis is always the same: eMMC blocks are corrupted, no data is allowed to be written on them. Possible fixes? Complete repartition, but we need to have detailed information about whole partition/block layout, and the right knowhow.
Check the thread @rzr86 has linked. There is a post by @Harakhti that provides some (very) technical information about a similar problem. It could be related to our Sensations, but this doesnt solve our issues unfortunately.
But you know whats the real problem? I am convinced that the TWRP pyramid .zip on their official website caused this problem to appear in the first place. 4EXT and ivanovichs recovieries seem to be safe. Amount of people who encountered this problem and soft-hardbricked their phones keeps on growing every day. And yet, this .zip is still on that website, so more and more people who are looking to mod their old smartphones are installing this buggy version. We, as a community on xda, should make sure that no more phones will be damaged by this glitchy piece of software.
Still, I am sorry for that. I am in the exact situation. My phone is being "repaired" by my fathers friend, but I am pretty much convinced that this phone is a lost cause. Unless a miracle happens. Sometimes they do. Most of the time not.
XTacDK said:
above post
Click to expand...
Click to collapse
This is pretty summarizing and accurate, except I got bricked with Ivanich's TWRP R14 for CM13.
The issue, if it's what I assume to be, would be that the eMMC just burns itself out when given a secure erase command. This possibility is tough, since it's about almost impossible to find a replacement motherboard for this device (FYI, the price for the mainboard is around 50€ at the time of writing, which is a hella lot for a device that costs around €95 total in a retail store around here).
To be honest, I'm not keen on getting a new phone, so if I turn out to be wrong, then I'll be happy that I can keep it for a few more years. This device has proven that it's absolutely capable of running any and all Android versions as long as you have a decent SD card.
I srcewed up my data partition with @ivanich twrp on one of my two sennys.
Weired since I formatted partitions many times on one phone in twrp, but the first time I switched from 4ext to twrp on the other phone,
the partition was corrupted after 1st wipe.
I still use this phone as a daily driver with @hinxnz mod "All Data on SD-EXT" (here) using a fast class 10 card.
There's definately no remarkable performance difference between the 2 phones + now I have a larger data partition.
Harakhti said:
This is pretty summarizing and accurate, except I got bricked with Ivanich's TWRP R14 for CM13.
The issue, if it's what I assume to be, would be that the eMMC just burns itself out when given a secure erase command. .
Click to expand...
Click to collapse
Funny thing is that secure erase has been disabled in kernel few years ago the same goes for discard and other dangerous things, also it has been disabled in userspace utils like mkfs.*
At the most cases it's ends up like this:
Jonas_HtcSensation said:
Hello ivanich,
I accidently formatted /data with the TWRP that is linked in your cm13 thread.
As i know now this will mess up the partitions for our Sensation as some other people have experienced as well.
I dont blame any one else than myself for not looking into TWRP enough, but maybe it is an good idea to warn people about using TWRP in your initial post.
When there is a recovery that is 'promoted' by a qualified person as you, people often think that everything fully works on this recovery. As happend to me.
So maybe just add a warning? If i manage to get my phone working somehow, i will make an instruction that can also be added.
Thank you for your work on our phone, i used your cm 12 for a long time and it was awesome.
Jonas
Click to expand...
Click to collapse
Quote:
Originally Posted by ivanich
Hi, perhaps you a first person who bricked /data partition with TWRP from https://drive.google.com/folderview?...p=sharing#list . I'm using twrp almost every day and formating partitions, including /data, 7-10 times per day without any issues, also AFAIK the were no reports about such problems with my twrp builds. Sometimes peoples bricked their phones with official twrp builds
Okay. You seem to be right, sorry.
I looked into my Download history:
I downloaded ~6 different versions from your google drive and 1 single version from twrp direct.
With my luck i bricked my phone the one time i had the wrong twrp installed... That makes it even annoying for me
Sorry to bother you,
Click to expand...
Click to collapse
ivanich said:
Funny thing is that secure erase has been disabled in kernel few years ago the same goes for discard and other dangerous things, also it has been disabled in userspace utils like mkfs.*
At the most cases it's ends up like this:
Click to expand...
Click to collapse
Odd. Thanks for the heads-up. All I did was change between the CM12 and CM13 versions, so I'm not sure how I screwed it up (particularly, formatting got stuck in 2.8.7.0 R14 for CM13).
But I guess the suspicion's correct and I blew my MMC, right?
Harakhti said:
Odd. Thanks for the heads-up. All I did was change between the CM12 and CM13 versions, so I'm not sure how I screwed it up (particularly, formatting got stuck in 2.8.7.0 R14 for CM13).
But I guess the suspicion's correct and I blew my MMC, right?
Click to expand...
Click to collapse
I'm not sure about that. Discarding device blocks: 4096/305852 - according to your log mkfs was completed succesfully but discard failed. Try to boot into recovery and play with mkfs and data partition, something like this:
make_ext4fs /dev/block/mmcblk0p23
or
mkfs.f2fs /dev/block/mmcblk0p23
Hey, @ivanich
Its good to see you here
Maybe those commands will help other people. They did nothing for me. unfortunately. I tried commands with mmcblk0p23, 22 and 24 (/data, /system, /cache), but it all said something in lines of "make ext4fs not found"
Either my ADB was not setup properly (weird because every other command i needed worked fine) or my partition table was broken beyond means of repair.
ivanich said:
I'm not sure about that. Discarding device blocks: 4096/305852 - according to your log mkfs was completed succesfully but discard failed. Try to boot into recovery and play with mkfs and data partition, something like this:
make_ext4fs /dev/block/mmcblk0p23
or
mkfs.f2fs /dev/block/mmcblk0p23
Click to expand...
Click to collapse
Code:
~ # mkfs.f2fs /dev/block/mmcblk0p23
F2FS-tools: mkfs.f2fs Ver: 1.5.0 (2015-11-05) [modified by Motorola to reserve space]
Info: Debug level = 0
Info: Label =
Info: Segments per section = 1
Info: Sections per zone = 1
Info: Trim is enabled
Info: sector size = 512
Info: total sectors = 2446818 (1194 MB)
Info: zone aligned segment0 blkaddr: 512
Info: format version with
"Linux version 3.4.110-ga791ac3-05576-g23ced4d ([email protected]) (gcc version 4.8 (GCC) ) #1 SMP PREEMPT Wed Dec 30 20:19:53 EET 2015"
Info: Discarding device: 0 sectors
Code:
~ # make_ext4fs /dev/block/mmcblk0p23
Creating filesystem with parameters:
Size: 1252769792
Block size: 4096
Blocks per group: 32768
Inodes per group: 7648
Inode size: 256
Journal blocks: 4778
Label:
Blocks: 305852
Block groups: 10
Reserved block group size: 79
Created filesystem with 11/76480 inodes and 10067/305852 blocks
Then it freezes. Logs:
http://pastebin.com/4NSf9zBG
Last 5 lines repeat forever.
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.
Hi all,
Rooted Nexus running stock 6.0.1 M4B30Z. Phone suddenly switched off and went into bootloop and haven't been able to re-flash stock... bootloader unlocked, fastboot working but no flashing possible (constant flash write error).
I managed to temporarily install TWRP using the excellent NRT v.2.1.9, but still unable to install anything. Seems the problem is storage cannot be mounted with the message 'unable to mount storage'. Again, managed to push the stock ZIP onto the sdcard but can't install.
Anyone got an idea of what it could be? is the device a certified brick now?
Thanks,
Bumping this thread to share steps to solve an identical problem I faced. My Xiaomi Mi 3 W suddenly switched off one evening. It was rooted with TWRP. I had LiveBoot installed. On the initial boot, I could see log data with the phone unable to find/load resources and a "fatal error 6".
I booted into TWRP and found that it could not read any of the partitions. I sense the eMMC memory or the partition table somehow got corrupted. Everything was "0 Mb" in TWRP and wiping or formatting via TWRP was useless -- showing the "unable to mount storage" error.
The OS/data was not in any bootable state at this point.
After an hour of scouring many solutions on Google, the one that worked was: using the "fastboot erase userdata" , "fastboot erase system" & "fastboot erase cache" commands via the ADB shell on Windows.
After this, TWRP could detect my data partition. Cache and System were still 0 MB. But you can fix this by separately reformatting these partitions to "EXT4" via Wipe > Advanced Wipe > Repair/format > Format as EXT4. This was not possible earlier. The error message "unable to mount storage" would have vanished at this point. But you will see "failed to mount system" (invalid argument) for some reason. This isn't a problem.
You'll be able to flash/restore your ROM/backups etc again, now that TWRP detects all three partitions. Sadly, the old data is long gone in this situation. Would love to know what caused this whole issue in the first place.
Thank you !!!!!!!!!!!
IT works!!!:good:
I found your reply by chance after three days of googling around. I was losing hope on my Nexus 5. So far "fastboot erase userdata" , "fastboot erase system" & "fastboot erase cache" worked. Now I'm trying to boot on twrp. If this works you saved me lots of hours.
---------- Post added at 08:14 AM ---------- Previous post was at 08:07 AM ----------
Still the same "unable to mount storage". Any other ideas?
ferarbe said:
I found your reply by chance after three days of googling around. I was losing hope on my Nexus 5. So far "fastboot erase userdata" , "fastboot erase system" & "fastboot erase cache" worked. Now I'm trying to boot on twrp. If this works you saved me lots of hours.
---------- Post added at 08:14 AM ---------- Previous post was at 08:07 AM ----------
Still the same "unable to mount storage". Any other ideas?
Click to expand...
Click to collapse
LOL i was doing the same this days on a Nexus5
The phone was in a reboot loop.
The error i was seeing was "unable to mount \data"
This is how i fixed id:
1. Open the Android Boot select (if this is how is called, the screen where you can select from start, recovery, reboot...)
2. Open the terminal and run "fastboot erase data"
3. After some time reboot the phone
2PointOBoy said:
Bumping this thread to share steps to solve an identical problem I faced. My Xiaomi Mi 3 W suddenly switched off one evening. It was rooted with TWRP. I had LiveBoot installed. On the initial boot, I could see log data with the phone unable to find/load resources and a "fatal error 6".
I booted into TWRP and found that it could not read any of the partitions. I sense the eMMC memory or the partition table somehow got corrupted. Everything was "0 Mb" in TWRP and wiping or formatting via TWRP was useless -- showing the "unable to mount storage" error.
The OS/data was not in any bootable state at this point.
After an hour of scouring many solutions on Google, the one that worked was: using the "fastboot erase userdata" , "fastboot erase system" & "fastboot erase cache" commands via the ADB shell on Windows.
After this, TWRP could detect my data partition. Cache and System were still 0 MB. But you can fix this by separately reformatting these partitions to "EXT4" via Wipe > Advanced Wipe > Repair/format > Format as EXT4. This was not possible earlier. The error message "unable to mount storage" would have vanished at this point. But you will see "failed to mount system" (invalid argument) for some reason. This isn't a problem.
You'll be able to flash/restore your ROM/backups etc again, now that TWRP detects all three partitions. Sadly, the old data is long gone in this situation. Would love to know what caused this whole issue in the first place.
Click to expand...
Click to collapse
Thanks very much. This solution works for me.
My case is Nexus 5 showing android robot after turning on. Luckily, the bootloader still works so I replaced the recovery with TWRP. Following the format steps and flash system, cache and userdata images again. It's so good to see the Welcom UI again.
Hello guys,
I run into a problem recently were my device won't boot. I tried a plethora of different solutions but nothing worked, I will have to factory reset to fix the issue.
My problem right now is that I can't access my files to make a backup. On my computer the device is connected and recognized but I can't access it's files. I also have TWRP and in TWRP Recovery it's unable to mount the Internal Storage and it shows up as 0MB. After a lot of research what seems to be the problem is that my files are encrypted, I don't know why this is (I guess for protection) but I didn't have any problems before. To my understanding if the phone is booted up you can access the files but if it can't boot then they stay encrypted. The encryption key should still be in my phone since I haven't formated it.
So how can I decrypt my data so that I can backup my files ? there must be a way for cases like this when something happens and the device can't boot, since the key is in the device it's self and I have the phone I should be able to, I also have access to every single account (google, xiaomi etc.) that is associated with this smartphone. If for security reasons that is not possible, would an authorized repair center be able to do it with proof of purchase and ownership ?
I am not 100% sure of my os version but it was 12.5.x.x, I have the unofficial twrp 3.5.0_10-beta. USB Debugging is enabled. Any other information you might need I can provide!
Thanks a lot everyone !
Your phone basically uses FBE ( File-Based Encryption ) to encrypt /data partition. When you boot phone into Recovery mode then the recovery.fstab file gets read by system
If you take a look into this file then you can notice that /data partition isn't encrypted ( it's only flagged encryptable and NOT fileencryption ).
TWRP will ask for lock screen credentials used for decrypting userdata partition. on FBE encryption the partition is mounted and even with no credentials provided one should at least see encrypted files.
In your case it's bit more complicated as that device uses FBE + metadata encryption. while in TWRP provide recovery.log to see what is going on. (share link to pastebin.com with expiration date 1 month)
Code:
adb pull /tmp/recovery.log
Note: there exist no relation between (FDE) encryptable= and (FBE) fileencryption= flags, these flags aren't interchangeable.
https://github.com/mhmdeve/twrp_dev...-twrp/recovery/root/system/etc/twrp.fstab#L18
aIecxs said:
TWRP will ask for lock screen credentials used for decrypting userdata partition. on FBE encryption the partition is mounted and even with no credentials provided one should at least see encrypted files.
In your case it's bit more complicated as that device uses FBE + metadata encryption. while in TWRP provide recovery.log to see what is going on. (share link to pastebin.com with expiration date 1 month)
Code:
adb pull /tmp/recovery.log
Note: there exist no correlation between (FDE) encryptable= and (FBE) fileencryption= flags, these flags aren't interchangeable.
https://github.com/mhmdeve/twrp_dev...-twrp/recovery/root/system/etc/twrp.fstab#L18
Click to expand...
Click to collapse
Here is the pastebin: Recovery.log
I read somewhere that changing the flags would solve the problem, after looking into it I pretty much found out what you said.
I also have an updated thread, if you can take a look it has some extra information provided !
Updated Thread
Hello guys,So my devices is stuck in a bootloop, I want to reflash the ROM but I need a backup first.Things I've tried to fix bootloop that didn't work:
Re-flashed the boot.img
Re-flashed the vbmeta.img
Wiping cache through TWRP Recovery
Things I've tried to back up my data:
Going into TWRP to make a backup it reads: "Internal Storage (0MB)", when I try to mount system or data I get "Unable to mount."
When I use the Mount->Decrypt Data option it asks me for a password, I tried every password I ever had on the phone and any "default" ones I found online and nothing worked.
I tried the adb pull command from my computer I get: "0 files pulled, 0 skipped." and nothing gets copied over.
So I don't know where to go from here, I have some things I have yet to try like:
Re-flashing ROM (dirty flash)
Re-flashing ROM update
Flash TWRP Update (if any)
But I don't know if they're going to to anything or just waste my time. Also I am not sure any of the 3 options will 100% keep my data.I am not too worried about apps and settings but more about Photos, Videos, PDFs, TXTs and Downloads.
Any ideas on what I should do ? Thanks a lot !
My device: Xiaomi Mi 10T Pro
If Stock Recovery would be the default recovery - and not TWRP - then if ADB got successfully established there would be a chance to pull the data interested in.
Code:
I:Unable to decrypt metadata encryption
E:Unexpected value for crypto key location
E:Error getting crypt footer and key
Code:
I:operation_start: 'Repair Partition'
Repairing Data using fsck.f2fs...
I:Repair command: /system/bin/fsck.f2fs /dev/block/sda34
Info: No support kernel version!
Info: Segments per section = 1
Info: Sections per zone = 1
Info: sector size = 4096
Info: total sectors = 28051451 (109575 MB)
Invalid SB CRC offset: 1205917355
Can't find a valid F2FS superblock at 0x0
Invalid SB CRC offset: 876348585
Can't find a valid F2FS superblock at 0x1
/system/bin/fsck.f2fs /dev/block/sda34 process ended with ERROR: 255
Unable to repair Data.
you have formatted userdata partition. your data is gone now...
Code:
I:operation_start: 'Change File System'
Formatting Data using mke2fs...
I:mke2fs command: mke2fs -t ext4 -b 4096 /dev/block/sda34 28051451
mke2fs 1.44.4 (18-Aug-2018)
Discarding device blocks: 4096/28051451 done
Creating filesystem with 28051451 4k blocks and 7020544 inodes
Filesystem UUID: c9db44bf-b076-41c6-b191-1013f3c1184e
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872
Allocating group tables: 0/857 done
Writing inode tables: 0/857 done
Creating journal (131072 blocks): done
Writing superblocks and filesystem accounting information: 0/857 done
I:mke2fs -t ext4 -b 4096 /dev/block/sda34 28051451 process ended with RC=0
I:Cannot lookup security context for '/data'
Done.
to fix boot-loop, factory reset device and format userdata back to f2fs from fastboot.
Code:
fastboot format:f2fs userdata
fastboot format:ext4 metadata
jwoegerbauer said:
If Stock Recovery would be the default recovery - and not TWRP - then if ADB got successfully established there would be a chance to pull the data interested in.
Click to expand...
Click to collapse
of course not. stock recovery neither provides adb nor is able to decrypt data.
aIecxs said:
Code:
I:Unable to decrypt metadata encryption
E:Unexpected value for crypto key location
E:Error getting crypt footer and key
Code:
I:operation_start: 'Repair Partition'
Repairing Data using fsck.f2fs...
I:Repair command: /system/bin/fsck.f2fs /dev/block/sda34
Info: No support kernel version!
Info: Segments per section = 1
Info: Sections per zone = 1
Info: sector size = 4096
Info: total sectors = 28051451 (109575 MB)
Invalid SB CRC offset: 1205917355
Can't find a valid F2FS superblock at 0x0
Invalid SB CRC offset: 876348585
Can't find a valid F2FS superblock at 0x1
/system/bin/fsck.f2fs /dev/block/sda34 process ended with ERROR: 255
Unable to repair Data.
you have formatted userdata partition. your data is gone now... factory reset device and format back to f2fs from fastboot.
Code:
I:operation_start: 'Change File System'
Formatting Data using mke2fs...
I:mke2fs command: mke2fs -t ext4 -b 4096 /dev/block/sda34 28051451
mke2fs 1.44.4 (18-Aug-2018)
Discarding device blocks: 4096/28051451 done
Creating filesystem with 28051451 4k blocks and 7020544 inodes
Filesystem UUID: c9db44bf-b076-41c6-b191-1013f3c1184e
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872
Allocating group tables: 0/857 done
Writing inode tables: 0/857 done
Creating journal (131072 blocks): done
Writing superblocks and filesystem accounting information: 0/857 done
I:mke2fs -t ext4 -b 4096 /dev/block/sda34 28051451 process ended with RC=0
I:Cannot lookup security context for '/data'
Done.
Click to expand...
Click to collapse
But how ? I never formatted my data ?
you have formatted -> to ext2 -> to ext4 -> with the 'Change File System' option in TWRP
aIecxs said:
of course not. stock recovery neither provides adb nor is able to decrypt data.
Click to expand...
Click to collapse
It's NONSENSE what you tell here. It's not the 1st time you do so. Wondering why?
aIecxs said:
you have formatted -> to ext2 -> to ext4 -> with the 'Change File System' option in TWRP
Click to expand...
Click to collapse
That deletes your data ? I read it on a guide and it was not mentioned. I has 110+ GBs worth of files and the process was done in seconds, are you sure the data is gone ? Or that this was the cause ?
jwoegerbauer said:
It's NONSENSE what you tell here. It's not the 1st time you do so. Wondering why?
Click to expand...
Click to collapse
actually it's you repeating nonsense without reading explanations because usually you already "no longer participate in this thread"
https://forum.xda-developers.com/t/...e-is-stuck-on-boot-loop.4536965/post-87941947
btw should I remind you to forum rules
MikeChannon said:
14. Create only ONE User Account
You are allowed ONE User Account at XDA-Developers. If you create additional accounts, Moderators will disable them and your original account may also be disabled or infracted.
Click to expand...
Click to collapse
https://forum.xda-developers.com/t/xda-developers-forum-rules.4200559
Leonniar said:
That deletes your data ? I read it on a guide and it was not mentioned. I has 110+ GBs worth of files and the process was done in seconds, are you sure the data is gone ? Or that this was the cause ?
Click to expand...
Click to collapse
No, that wasn't the cause of boot-loop. but next time you must not follow random guides without understanding what you're actually doing. yes, formatting userdata partition deletes all data. it's too late now...
aIecxs said:
No, that wasn't the cause of boot-loop. but next time you must not follow random guides without understanding what you're actually doing. yes, formatting userdata partition deletes all data. it's too late now...
Click to expand...
Click to collapse
I was under the impression that changing the system file could be done without deleting the data, that's what the guide said and there was no warning or message regarding loss of data inside TWRP (for example there are a lot of messages in the WIPE section) so I figured it could work... I was out of options... damn...
So I am screwed pretty much ?
wording matters.
changing the system file could be done without deleting the data.
changing the file system of the partition not. this is common sense, no warning required.
my explanation: you don't know what a file system actually is (but then you're not in the position of dealing with file systems anyway)
https://forum.xda-developers.com/t/...ed-to-unlock-bootloader.4531349/post-87917999
that said, if it's any consolation to you, encryption of userdata partition was already corrupted beforehand. on (plain) FBE encryption some users could repair ext4 file system with e2fsck. your device is formatted f2fs which isn't as easy to repair as ext4.
'Repair Partition' fsck.f2fs could have worked in case the f2fs file system have had (minor) issues.
But in your case most likely (if I got the recovery.log right) the early metadata encryption was broken (maybe metadata partition faulty) so there were no chance to decrypt block device anyway, which is prerequisite for mounting/decrypting or even just repairing (FBE encrypted) userdata partition.
So the chances to recover any files were very low to zero from the beginning.
aIecxs said:
wording matters.
changing the system file could be done without deleting the data.
changing the file system of the partition not. this is common sense, no warning required.
Click to expand...
Click to collapse
Yeah I know, for real I don't know why I didn't realize. I've been changing file systems of USB Drives to use for softmoded consoles and I format them every time. Yet I didn't even realize I did the same here...
But yeah, since I didn't have much luck from the beginning I guess it just made it easier for me to delete my files...
Thanks for all the help and the explanations !
aIecxs said:
wording matters.
changing the system file could be done without deleting the data.
changing the file system of the partition not. this is common sense, no warning required.
my explanation: you don't know what a file system actually is (but then you're not in the position of dealing with file systems anyway)
https://forum.xda-developers.com/t/...ed-to-unlock-bootloader.4531349/post-87917999
that said, if it's any consolation to you, encryption of userdata partition was already corrupted beforehand. on (plain) FBE encryption some users could repair ext4 file system with e2fsck. your device is formatted f2fs which isn't as easy to repair as ext4.
'Repair Partition' fsck.f2fs could have worked in case the f2fs file system have had (minor) issues.
But in your case most likely (if I got the recovery.log right) the early metadata encryption was broken (maybe metadata partition faulty) so there were no chance to decrypt block device anyway, which is prerequisite for mounting/decrypting or even just repairing (FBE encrypted) userdata partition.
So the chances to recover any files were very low to zero from the beginning.
Click to expand...
Click to collapse
Hello and sorry for bothering you again.
I am currently trying to fix the bootloop, I formatted userdata back to f2fs but I noticed Cache is also on ext4 format, should I change that as well ?
Also on your original comment on how to fix bootloop you told me
aIecxs said:
factory reset device and format userdata back to f2fs from fastboot
Click to expand...
Click to collapse
But factory reset fails so I am changing the file system first before trying again.
I will also root my device again as soon as I have it up and running, will a factory reset be sufficient ? NO leftovers or anything ? Or should I go with "Format Data" or just wipe everything ?
And absolute last question, I am trying all this through TWRP Recovery. Will any of the above mentioned options (Factory Reset, Wipe Data, Format Data) delete TWRP as well ? As I said since I will root the phone again I would like to remove TWRP as well and do a clean install.
Thanks again !
Format Data is what I meant with factory reset. you can do it from TWRP. you haven't changed file system of cache therefore no need to change file system to f2fs.
aIecxs said:
factory reset device and format userdata back to f2fs from fastboot.
Code:
fastboot format:f2fs userdata
fastboot format:ext4 metadata
Click to expand...
Click to collapse
You won't lose root or TWRP, unless you restore backup of stock boot.img
aIecxs said:
Format Data is what I meant with factory reset. you can do it from TWRP. you haven't changed file system of cache therefore no need to change file system to f2fs.
You won't lose root or TWRP, unless you restore backup of stock boot.img
Click to expand...
Click to collapse
Oh so Formatting Data keeps magisk ?
So there is no need for clean install of TWRP or Root ? I just update anything if needed and I am good to go ?
Edit:
After rebooting the device and trying to re-activate it with my Mi Account I can't connect to the internet. SIM Card is inserted, I was not asked for a pin and it shows no signal (there is definitely signal). Turning on wifi shows 0 available networks even tho there are plenty. Any idea why ?
you lose Magisk superuser but you won't lose root. just install apk from github again.
the other issue sounds like you lost baseband, probably due booting into wrong slot.