I used TWRP to wipe all my partitions under advanced wipe.
I Odin'ed the stock kernel, stock rom and TWRP.
I used TWRP to mount the efs partition, and adb pushed my backed up efs.zip into that partition.
I checked using the TWRP file manager that the files and folders are all in the efs partition.
But after a reboot into TWRP, the efs partition would become empty again, as if I never transfered the files.
And off course, my phone is now stuck at the notorious Samsung logo boot loop.
So why did the files delete themselves after every boot? And is there any way to solve my boot-looping issues?
My current partition size:
Boot (10mb)
System (2135mb)
Data (0mb)
Cache (62mb)
Recover (10mb)
EFS (4mb) it is empty, but still has 4mb?
First question is what firmware were you on before all this? Second question is why did you do all this?
If you were not on mf3 firmware get the stock firmware from sammobile.com and flash that in Odin, PDA. Do not check re-root partition. Hopefully that get your phone to work again.
Wooo hooo it works
Ahh I fixed it! Sorry for the troubles.
I'm glad you got it fixed. But don't mess all that stuff you did.
jd1639 said:
I'm glad you got it fixed. But don't mess all that stuff you did.
Click to expand...
Click to collapse
Yea, curiousity definitely killed the cat. This may be my last of my 9 lives.
Would do sufficient research before attempting theses kind of tasks again.
Thank you. I fixed the problem following several other threads in this forum. Vast amount of knowledge here, just a bit too scattered.
So I'm having a weird issue. Whenever I flash any kernel other then stock it stays stuck at the LG logo. I have to pull battery and then restore the stock kernel backup. I have no idea why I'm having this issue. I've also noticed that TWRP sometimes says cannot mount system (probably not the culprit but just adding more info).
Model: T-Mobile (h918)
When I had the "cannot mount" issue, a system partition format was needed from within TWRP. I took a backup of system (not a system.img backup), then formatted system only, then restored the system. It's been fine ever since.
I'm not sure if any special pocedure is needed for the h918 in order not to brick anything. I'm on US996.
I hope that made sense. Please wait for a second opinion before trying anything.
pistacios said:
When I had the "cannot mount" issue, a system partition format was needed from within TWRP. I took a backup of system (not a system.img backup), then formatted system only, then restored the system. It's been fine ever since.
I'm not sure if any special pocedure is needed for the h918 in order not to brick anything. I'm on US996.
I hope that made sense. Please wait for a second opinion before trying anything.
Click to expand...
Click to collapse
Yea. Seems like I have to format system all the time. Also have to format my internal storage all the time. My backups never seem to restore correctly. I can't flash a new ROM because it wont boot with a different kernel. I might just flash KDZ and root all over again.
Hello, for some reason my persist partition corrupted and I think it was my mistake. I flashed the stock rom, and the fingerprint is now working, however, automatic rotation doesn't. Can anybody give a link to persist.img because I haven't able to find it from none of the updates asus released? If not a backup of persist partition. TWRP can easily make a backup of it.
Also, just for you know, deleting persist partition on ZE552KL doesn't lead to broken wifi, bluetooth or imei. Learned it through the hard way. You may ask why I didn't make a backup. It is because I didn't know it previously.
I would appreciate it if anyone could provide persist partition img or backup.
BTW, I also tried a raw image with the full name of "WW_ZE552KL_15.0410.1803.55_M3.10.47.19_Phone-user.raw".
So, today I was going to flash miui 11 andoid 10 and made a backup of all my files to the pc. weird enough some files size was too big (a zip of a rom was like 12 gb) something was wrong there. anyway, after backup, I updated the twrp to the latest chines and after flashing the twrp I wasn't able to enter twrp, it got stuck on the spalsh screen.
So, I flashed the fastboot stable version for eea mi 9t, as usual, to restore to stock. but again it doesn't boot and it still gets stuck on twrp splash screen but after a while, twrp boots and I see that it's unable to mount data and cache.
I try to format the whole data partitions but it only gets stuck there forever.
you can see it in the screenshot attached.
The file system on data appears as f2fs. I tried converting to ext4 and still no luck, it get stuck there forever.
How long should it take to format a corrupted data partition like this?
Any help, please?
Edit: also tried using the command line to format /data myself and it gets stuck here:
Code:
mke2fs -t ext4 /dev/block/sda32
mke2fs 1.43.3 (04-Sep-2016)
Discarding device blocks: done
Creating filesystem with 13518331 4k blocks and 3383296 inodes
Filesystem UUID: 0ea82001-1ff3-47d3-bf7c-19308852ceb3
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424
Allocating group tables: done
Writing inode tables: done
Creating journal (65536 blocks): done
Writing superblocks and filesystem accounting information:
It looks like :
https://twrp.me/site/update/2019/10/23/twrp-and-android-10.html
and
https://forum.xda-developers.com/android/general/how-to-fix-unable-to-mount-data-t3830897
I don´t know what exactly was the problem, I was trying custom ROMs and they worked fine but then I went back to stock and found my persist broken. So flashed a persist.img from the fastboot images, that broke widevine L1 and messed up the sensor, I had to recalibrate the camera etc. But after a while, the stock rom started acting weird, not receiving email, not syncing contacts, lag and stuttering etc, so I decided to flash the fastboot rom again with the wipe everything .bat. It flashed everything fine but didnt boot anymore and wasn't able to enter stock recovery anymore. Was only able to access fastboot and twrp. Tried locking the bootloader and wiping everything again and it got stuck on 99.99% when it's wiping on stock. I left it all night and in the morning I found it on the boot animation but it stayed there for hours and hours and it never booted.
On twrp I was able to mount system and all the partitions except data and cache. I tried repairing them and formating but it was always failing. I even used parted through adb shell, deleted partitions and created new ones but with the same unsuccessful results.
So, in the end, I sent the phone to the repair service under warranty and they fixed it by replacing the mainboard. So I guess the problem bricked the whole memory and who knows what else.
So be careful guys, flashing custom ROMs and other region stock ROMs isn't safe with this phone. We have people with broken persist partition, broken internal storage, sensors, bricked phones...
Personally speaking, I won't flash any custom ROMs or stock ROMs not meant for my device anymore. Xiaomi has introduced to many measures that are causing problems with flashing, similar to Huawei.
bihariel said:
I don´t know what exactly was the problem, I was trying custom ROMs and they worked fine but then I went back to stock and found my persist broken. So flashed a persist.img from the fastboot images, that broke widevine L1 and messed up the sensor, I had to recalibrate the camera etc. But after a while, the stock rom started acting weird, not receiving email, not syncing contacts, lag and stuttering etc, so I decided to flash the fastboot rom again with the wipe everything .bat. It flashed everything fine but didnt boot anymore and wasn't able to enter stock recovery anymore. Was only able to access fastboot and twrp. Tried locking the bootloader and wiping everything again and it got stuck on 99.99% when it's wiping on stock. I left it all night and in the morning I found it on the boot animation but it stayed there for hours and hours and it never booted.
On twrp I was able to mount system and all the partitions except data and cache. I tried repairing them and formating but it was always failing. I even used parted through adb shell, deleted partitions and created new ones but with the same unsuccessful results.
So, in the end, I sent the phone to the repair service under warranty and they fixed it by replacing the mainboard. So I guess the problem bricked the whole memory and who knows what else.
So be careful guys, flashing custom ROMs and other region stock ROMs isn't safe with this phone. We have people with broken persist partition, broken internal storage, sensors, bricked phones...
Personally speaking, I won't flash any custom ROMs or stock ROMs not meant for my device anymore. Xiaomi has introduced to many measures that are causing problems with flashing, similar to Huawei.
Click to expand...
Click to collapse
Yeah, same thing happened to me buy flashing a EU beta ROM in September but I was lucky and got my phone replaced by Amazon, since It was still in return period since then I have stayed away from miui custom ROMs and betas only Aosp. But I always return to miui. And always with a back up of my entire partition.
Hi, I recently upgraded from Lineage 16 to 17.1 and now wifi is off and when I turn it on phone reboots but wifi is still off, location no longer works, camera flash is not working. I have looked online to try to find out what may have caused this and it seems from what I've read that TWRP has corrupted the callibration data in the persist partition. I have updated TWRP to 3.4.0-0 but I am not sure how to proceed to fix the issue. IE: Do I format and reflash 17.1 or does the persist partition need to be repaired first. Any help on how to fix this would be appreciated. Thanks in advance.