This is all new to me and I've read everything I could find.
I successfully rooted my e4 with magisk. Then I wanted to flash the stock rom to get it back to out of the box condition.
I had to flash the .bat file because rsdlite will not recognize my phone no matter what I do. It got stuck on a bad key/erasing bootloop. I was able to flash twrp, format data/unencrpyt, and flash no verity and it booted just fine, unrooted. I rerooted and tried to sign into Google account and Google play services didn't work. I downloaded and installed several versions, deleted data and cache for Google plays services, store, framework, even deleted the hosts.txt file and nothing. So I decided to flash stock and start fresh.
Following the steps I had done previously that worked no longer work. When I format data/unencrpyt I get the failed to mount /data blah blah crypto footer, failed to mount /cache. So I tried to reformat those individually by changing their format to f2fs and back to ext4 and vise versa and reformated and no errors. Flashes no verity thinking everything should go smoothly now and I'm stuck in a twrp recovery loop. I'm just lost. I've spent hours and hours and hours reading and fiddling and I'm at the point where I have to ask for help. So...
Help!
Related
Hello,
my s4 doesn't boot anymore and something weird happens all the time. I already tried delete system and caches, then flash rom (aosp) but this doesn't help.
I think my data partition is corrupted, but I don't want to wipe it as it contains all my stuff.
PS: the screenshot shows files that aren't there, I checked in the filemanager and they are there.
filesystem repair gives:
/sbin/fsck.f2fs /dev/block/mmcblk0p29 process ended with error 139
Even backup fails:
createTarFork() process ended with error 255
What if you use the xposed uninstaller zip?
If the zip doesn't help then I'm pretty sure the only solution is to wipe data.
Happened to me too several times, randomly, during reboots. Sometimes my data would get automatically wiped, and other times my phone wouldn't boot unless I wiped the data partition.
I believe it has something to do with F2FS, because, since I changed back to ext4, I haven't had this problem.
GDReaper said:
What if you use the xposed uninstaller zip?
If the zip doesn't help then I'm pretty sure the only solution is to wipe data.
Happened to me too several times, randomly, during reboots. Sometimes my data would get automatically wiped, and other times my phone wouldn't boot unless I wiped the data partition.
I believe it has something to do with F2FS, because, since I changed back to ext4, I haven't had this problem.
Click to expand...
Click to collapse
I flashed stock and then started over. Somehow my rom zip got corrupted and I got the same problem. So I redownloaded and flashed, everything is good now
Sent from my GT-I9505 using Tapatalk
Phone is working, I suppose doing his job in the process. The problem is that I am waiting already 20 minutes. I am afraid of getting CPU burnt (it is at 51 grades of Celsius).
I have read about the issue and about also the solution [enabling rm -rf in the twrp settings]... But now I am in the process, so not sure if I should shut the phone down or not..
Did you do a factory reset or advanced wipe?
I used advanced wipe, I got really angry with formatting so I removed the battery ... but now I have a problem: failed to mount system... I installed the twrp through odin... And before that I did not do anything, do I have to unlock bootloader or something like that?
binuralka said:
I used advanced wipe, I got really angry with formatting so I removed the battery ... but now I have a problem: failed to mount system... I installed the twrp through odin... And before that I did not do anything, do I have to unlock bootloader or something like that?
Click to expand...
Click to collapse
No. Your bootloader is already unlocked, otherwise it wouldn't have let you flash TWRP.
Have you tried factory reset? Or mounting system manually?
You can also try to mount system by using TWRP's built-in terminal emulator.
Now I flashed 4.4.2 with and Odin, phone was ok. Then I flashed latest twrp and now the system was mounted. I did a backup and wiped all again with advanced wipe. Then I tried to install ROM but it fell again to a error 7 - system not mounted. How can I mount it manually? what command is that?
binuralka said:
Now I flashed 4.4.2 with and Odin, phone was ok. Then I flashed latest twrp and now the system was mounted. I did a backup and wiped all again with advanced wipe. Then I tried to install ROM but it fell again to a error 7 - system not mounted. How can I mount it manually? what command is that?
Click to expand...
Click to collapse
Error 7 means the ROM is not compatible with your model.
Have you tried different version of twrp?
That was a really terrible testing day... I tried every twrp till version 2.8.6 that worked after odin flashing. I managed to mount system and do all wipes. I flashed ROM and gapps, everything went smoothly... But the thing was that the phone started to shut down by itself. Without a message, simply black screen and restart and bootloop after samsung logo. I decided to load 4.4.2 stock with repartitioning (pit file)... 10 hours ok and then again shutting down by itself.
Have you experienced this kind of behaviour?
Yesterday I tried to install Imperium LL ROM (latest). It kept giving me errors about being unable to mount /system while installing (with Aroma). In the rom's thread I saw that someone had similar issues and he fixed it by deleting /dev/block/platform/msm_sdcc.2. I tried renaming it, but it just kept coming back. I the deleted it, rebooted to recovery and tried to install it again. The installer got stuck on formating /system (for about 5 minutes). I rebooted and tried to restore a nandroid backup. It also got stuck on formating /system. In TRWP log I saw 'Failed to mount /system (invalid argument). I went to Wipe->Advanced-> selected system-> Repair or change File System. It shows : Present: Yes; Removable: No; Size: 0MB; Used: 0MB; Free: 0MB; Backup Size: 0MB.
I have full access to recovery and download mode. Is there anything I can do to fix it, or do I have to send it for repair to the shop I bough it in (I have an insurance that covers any damage, even if I caused it)?
I would suggest trying to flash a stock firmware with Odin. Maybe flash it together with a PIT file too.
I flashed Stock, latest Lollipop firmware (without flashing PIT). It seemed to work fine. It did the usual "Optimizing apps" thing, then it rebooted. Right now it seems to be bootlooping. I'm going to try and flash TWRP and see what I can do from there.
EDIT: I flashed recovery and did a factory reset. When rebooting it asked if I want to root and I chose to do so. After about 10 minutes it booted up into the welcome screen (the one where you choose language, wifi etc.). I need to flash the latest modem and bootloader, and then install a ROM.
Thanks @Pwnycorn for help.
If you flash the phone with the latest stock firmware, the phone will be running the latest modem and bootloader.
Hi
I unlocked the bootloader and installed TWRP as described in the tutorials here. I then also flashed SuperSU. Afterwards I booted into stock Android and it worked. I wanted to do a factory reset so that after reinitializing I could install all my apps automatically. I went into TWRP --> Wipe --> Slide to Wipe. After rebooting it asked me for the pincode to decrypt. Since that didn't work I wiped everything except the SD Card and flashed lineage. Since then, my G6 keeps booting into TWRP. I even tried AquariOS (randomls chosen ROM) and I have the same results. I checked into "backup" in TWRP and the system partition is about 1GB. I then wiped it, and it went down to almost 0 I think. I then reflashed lineage and it was again at almost 1GB. So as it seems it is writing something. I then went into "mount" and system was not selected. I checked it and "mount system partition as read only", rebooted into the system, and it booted into TWRP again, system was unchecked under mount, but the read-only option was still checked. tried the same without the read-only option, same result. So now my G6 keeps mounting into TWRP instead of the ROM.
Any ideas what I can do?
Format data in recovery, don't wipe. It will disable encryption. Flash stock 14a again and see if you can get it to boot
I fixed it, somehow TWRP was messed up. I redownloaded it and reflashed it and then it worked
Hey folks. I'm hitting a brick wall trying to figure out this issue and I'm hoping someone will know how to fix this.
I have a Galaxy Tab A 8 (SM-T350) that I rooted and successfully flashed with first crDroid, then Lineage (both Android 9.0) using TWRP. I had made a backup before attempting this just in case I wanted to revert to stock.
Well, that didn't go as smoothly as I was hoping. Ever since trying to restore my backup, I've been stuck on a continuous boot loop that I can't seem to fix.
I keep getting "E:failed to mount /efs (Invalid argument)" and "dm-verity verification failed. . ." no matter what I try. I've googled the error and tried every solution suggested but I still can't get it to boot.
Any help at all would be greatly appreciated. Thanks.
skorpien said:
Hey folks. I'm hitting a brick wall trying to figure out this issue and I'm hoping someone will know how to fix this.
I have a Galaxy Tab A 8 (SM-T350) that I rooted and successfully flashed with first crDroid, then Lineage (both Android 9.0) using TWRP. I had made a backup before attempting this just in case I wanted to revert to stock.
Well, that didn't go as smoothly as I was hoping. Ever since trying to restore my backup, I've been stuck on a continuous boot loop that I can't seem to fix.
I keep getting "E:failed to mount /efs (Invalid argument)" and "dm-verity verification failed. . ." no matter what I try. I've googled the error and tried every solution suggested but I still can't get it to boot.
Any help at all would be greatly appreciated. Thanks.
Click to expand...
Click to collapse
Ignore the EFS error its probably a red herring. Your issue is dm-verity.
3 ways around it. Return to complete stock, including wiping the data partition or flash root (magisk suggested) or disable dmverity using one of the zips out there.
ashyx said:
Ignore the EFS error its probably a red herring. Your issue is dm-verity.
3 ways around it. Return to complete stock, including wiping the data partition or flash root (magisk suggested) or disable dmverity using one of the zips out there.
Click to expand...
Click to collapse
Thanks for the reply ashyx.
I've done two of the three things you suggested. I've tried returning it to stock using an image matching my exact model, and I've tried disabling dmverity. I've also tried rooting it but using a method other than magisk.
The flash seems to go well enough, but then I get stuck at the Samsung logo whenever I try rebooting into the system.
I've tried waiting, thinking I'm just being impatient, but it doesn't ever seem to get past the logo. I've tried googling ways to fix it being stuck on the logo but nothing I do seems to work. Is there any other way around it?
Side note: I've been able to flash Lineage OS again and might just have to stick with that if I can't flash it back to stock. Do you know any resources for replacing the default apps? I've tried GApps but I was wondering if there's a similar Samsung installer?
skorpien said:
Thanks for the reply ashyx.
I've done two of the three things you suggested. I've tried returning it to stock using an image matching my exact model, and I've tried disabling dmverity. I've also tried rooting it but using a method other than magisk.
The flash seems to go well enough, but then I get stuck at the Samsung logo whenever I try rebooting into the system.
I've tried waiting, thinking I'm just being impatient, but it doesn't ever seem to get past the logo. I've tried googling ways to fix it being stuck on the logo but nothing I do seems to work. Is there any other way around it?
Side note: I've been able to flash Lineage OS again and might just have to stick with that if I can't flash it back to stock. Do you know any resources for replacing the default apps? I've tried GApps but I was wondering if there's a similar Samsung installer?
Click to expand...
Click to collapse
You need to wipe the data partition, aka factory reset before or after installing the stock firmware then it will take anything up to 15 mins to boot.
ashyx said:
You need to wipe the data partition, aka factory reset before or after installing the stock firmware then it will take anything up to 15 mins to boot.
Click to expand...
Click to collapse
I've tried leaving it for a few hours in hopes that it would boot, but unfortunately it stays stuck on the logo.
Is there a way to check where or why it's getting hung up?
skorpien said:
I've tried leaving it for a few hours in hopes that it would boot, but unfortunately it stays stuck on the logo.
Is there a way to check where or why it's getting hung up?
Click to expand...
Click to collapse
Did you back up the efs partition with twrp?
If so try restoring it.
ashyx said:
Did you back up the efs partition with twrp?
If so try restoring it.
Click to expand...
Click to collapse
I did and I have been restoring it.
So far, this is what I've attempted:
Flash TWRP (twrp_3.1.0-1_sm-t350_18317.tar using Odin3 v3.10)
Reboot into recovery
Wipe everything from tablet
Format tablet
Reboot into download mode
Flash stock image with Odin
Reboot into recovery
Wipe dalvik cache
Restore backup (including efs partition)
Wipe dalvik cache (again)
Reboot
Get stuck on Samsung logo (left it for hours with no change)
skorpien said:
I did and I have been restoring it.
So far, this is what I've attempted:
Flash TWRP (twrp_3.1.0-1_sm-t350_18317.tar using Odin3 v3.10)
Reboot into recovery
Wipe everything from tablet
Format tablet
Reboot into download mode
Flash stock image with Odin
Reboot into recovery
Wipe dalvik cache
Restore backup (including efs partition)
Wipe dalvik cache (again)
Reboot
Get stuck on Samsung logo (left it for hours with no change)
Click to expand...
Click to collapse
Don't restore everything just EFS No need to keep wiping dalvik it serves no purpose when formatting or wiping the data partition.
Also FORMAT not wipe the data partition (note this wipes internal storage)
If it still doesn't boot install the combo firmware. Let it boot, factory reset from settings then reboot to download mode and install the stock firmware again.