[SM-G532F]TWRP can't mount data after flashing stock boot.img - Samsung Galaxy J2 Questions & Answers

Hi guys,
I have recently installed twrp and formated data and flashed magisk and dm-verity and every thing is ok. But i have turned off developer options in mistake and rebooted my phone and it is blocked by frp lock so i have flashed stock boot.img only and booted without losing any data and enabled oem unlock and reflashed magisk and rooted again but unfortunatly twrp can't mount data as like as it is from beginning and i don't want to reformat data because of my data in it .Any soloutions?
Will backup data and reformat data and do every thing and restore data backup be ok?
Sorry for bad english.

Related

Unable to mount /data after encryption

I've just had a bit of a panic then worked myself out of it. To help others in a similar situation, I thought I'd put what to do here, as searching doesn't help.
I'd encrypted my phone (and the external SDcard FWIW) via the Security settings. But it slowed it down a lot. I'd thoughtfully backed up a NANDROID to my PC before doing anything. So instead of unencrypting, I thought I'd go the quick way: go in through CWM Recovery (previously flashed on the phone) and sort things out from there.
Big mistake. CWM Recovery doesn't deal with encrypted phones or SDcards. So I took the SDcard out, reformatted it in a reader on my PC, stuck the NANDROID back on it. Then back into Recovery. Still whenever I tried to do anything, such as wipe / factory reset or restore the NANDROID, I got "unable to mount /data".
Oh dear. Next step: I downloaded a stock N7100 firmware and flashed it via ODIN. But I discovered this doesn't sort the problem either; it still leaves the /data partition encrypted. On booting up, it asks me for the encryption password; but won't boot further - presumably due to incompatibilities between teh custom ROM's Data partition and the stock rom.
Rebooted into Stock Recovery; multiple errors "unable to mount /data". BUT happily Wipe / Factory Reset from the Stock recovery did work.
I was then able to reroot, re-install recovery, and restore the NANDROID, thank God. Major panic for a while there.
tl;dr if you get in a state with an unbootable encrypted phone, and non-stock recovery gives "Unable to mount /data", you need STOCK recovery on it (flashed via ODIN, perhaps from full stock firmware or separately if you can find it) then factory reset with that. You'll then obviously need to reroot etc.
hope that's of use to somebody.
kingqueen said:
I've just had a bit of a panic then worked myself out of it. To help others in a similar situation, I thought I'd put what to do here, as searching doesn't help.
I'd encrypted my phone (and the external SDcard FWIW) via the Security settings. But it slowed it down a lot. I'd thoughtfully backed up a NANDROID to my PC before doing anything. So instead of unencrypting, I thought I'd go the quick way: go in through CWM Recovery (previously flashed on the phone) and sort things out from there.
Big mistake. CWM Recovery doesn't deal with encrypted phones or SDcards. So I took the SDcard out, reformatted it in a reader on my PC, stuck the NANDROID back on it. Then back into Recovery. Still whenever I tried to do anything, such as wipe / factory reset or restore the NANDROID, I got "unable to mount /data".
Oh dear. Next step: I downloaded a stock N7100 firmware and flashed it via ODIN. But I discovered this doesn't sort the problem either; it still leaves the /data partition encrypted. On booting up, it asks me for the encryption password; but won't boot further - presumably due to incompatibilities between teh custom ROM's Data partition and the stock rom.
Rebooted into Stock Recovery; multiple errors "unable to mount /data". BUT happily Wipe / Factory Reset from the Stock recovery did work.
I was then able to reroot, re-install recovery, and restore the NANDROID, thank God. Major panic for a while there.
tl;dr if you get in a state with an unbootable encrypted phone, and non-stock recovery gives "Unable to mount /data", you need STOCK recovery on it (flashed via ODIN, perhaps from full stock firmware or separately if you can find it) then factory reset with that. You'll then obviously need to reroot etc.
hope that's of use to somebody.
Click to expand...
Click to collapse
I was just wondering if i encrypt my phone but after reading this i think i will only encrypt external sd card so i wont fsck up because of rooting etc.

[SOLVED] Help! "encryption unsuccessful" message!

I was running oos based nougat custom rom with blu spark recovery. Then flashed official ob1, didnt like it, wiped cache/data/system and reinstalled my old oos nougat rom (audax 4.7.6). Now i get the above mentioned message..
Things i tried:
- addionally wipe internal storage and media (installed rom via adb sideload then)
- reformat system/cache/date with ext4
I googled the error and for most people (threads werent particularly concerning the op5t however) it seems that just wiping data and reinstalling the rom did the trick. Not for me though..
What can i do now?
Solution: reformating the data partition with ext4 is not enough. I had to format to FAT and right after that again to ext4, reboot to system and boom, it worked!
PS: i wonder what data is on the internal storage partition that i deleted? I didnt have any data on the phone, i just wonder.. It isnt somehow crucial to the phone?!
I think the decryption key is somehow embedded into the internal storage as wiping /data does not delete the PIN/pattern. Might be a hidden partition or something similar that is not wiped when wiping /data as long as it is ext4.
Your data is gone. It failed to completely encrypt and now there's nothing that can be done. Format /data as ext4 and let it try encrypting again
I have the same problem exactly. Can you explain in steps you have installed then format or how?
I have the same problem exactly. Can you explain in steps you have installed then format or how?
Click to expand...
Click to collapse
I had the exact same problem. But it is an easy fix but does require wiping your internal storage.
So the save way of doing this would be:
1. Backup all your data by going to TWRP or your ROM if that still works. Plug in an USB cable and use MTP or the adb pull command to backup your data
2. Reflash OB1 with no root (like Magisk of SuperSU) if you have TWRP. This will cause you to have the stock recovery again. I also recommend to do a clean flash (Wiping system and data before flashing the rom).
3. Download the rollback build from Oneplus [HERE] and copy this to the internal storage.
4. Boot into the stock recovery flash the rollback build. THIS STEP WILL WIPE YOUR INTERNAL STORAGE.
5. Now you have OxygenOS 4.7.5. Download OxygenOS 4.7.6 Incremental Update [HERE]
6. Go back to the Stock recovery and flash the incremental 4.7.6 zip.
7. You have the latest version now. So boot to fastboot reflash TWRP and flash SuperSU or Magisk in TWRP to regain root
Guys I did a fail, i had OB3 installed, and I wanted to try RR so I wiped system and when I tried to install I have seen error 7 saying its for dumpling not for oenplus5t.
So I restored.... But instead restoring OB3 I have restored stock Nougat rom -.- I have even stock recovery now, what is the best way to fix it?
Can i change to FAT and stay and dont go back to ex4 again?
Hi i don't know if u r reading this but if you are please help me cause I'm so lost and confused over this since yesterday...
so 2 days ago my phone started lagging and hanging and freezing until i realized i have got this issue with data encryption
i have a rooted sony z2 with TWRP Custom recovery
first i didn't know it was with data encryption failure so i literally factory reset and installed all my apps and data again and again!!! after every time my phone started to lag !!
after one whole day of trying everything i finally realized its actually with the data encryption and i should change my ex4 to something else... so here again i wiped the phone and changed to ex3 and installed and all my data and apps all over again
but after a couple hours...same problem again.....
im literally so tired of not knowing what to do ! my head hurts so much due this ugh....
i havent changed to FAT from ex3 so im wondering if it will finally solve my problem permanently if i change to FAT ??
And if it did can i just keep it on FAT forever ?
Please guide me thanks ...!
Lasersdude said:
I was running oos based nougat custom rom with blu spark recovery. Then flashed official ob1, didnt like it, wiped cache/data/system and reinstalled my old oos nougat rom (audax 4.7.6). Now i get the above mentioned message..
Things i tried:
- addionally wipe internal storage and media (installed rom via adb sideload then)
- reformat system/cache/date with ext4
I googled the error and for most people (threads werent particularly concerning the op5t however) it seems that just wiping data and reinstalling the rom did the trick. Not for me though..
What can i do now?
Solution: reformating the data partition with ext4 is not enough. I had to format to FAT and right after that again to ext4, reboot to system and boom, it worked!
PS: i wonder what data is on the internal storage partition that i deleted? I didnt have any data on the phone, i just wonder.. It isnt somehow crucial to the phone?!
Click to expand...
Click to collapse
Finally. Thank you so much!

Problem after flashing wth global rom

Hello,
I get Xiaomi mix 2s global with:
-Unblocked bootloader
-Installed OrangeFox Recovery
-Installed some Android 10 pixel experience rom
I wanted back to original global rom with stock recovery and reblock bootloader, so i download Global Stable ROM V11.0.5.0.QDGMIXM, put to internal storage and install from OrangeFox.
And now, when I turn on the smartphone, it’s starts, restart and go again to OrangeFox recovery.
In log I have: “Android Rescue Party trigger! Wipe data and caches and/or clean-flash you ROM!"
OrangeFox disables forced encryption by default, and now I need to enabled encryption? How to do it?
So, How to fix it?
I want to back to original global rom with stock recovery and reblock bootloader, bu first I have t turn on system.
Thanks
EDIT:
After installatin PixelExperience_polaris-10.0-20200528-1111-OFFICIAL from OrangeFox, smartphone starts normally, now I want to back to stock rom, recovery and reblock bootloader.
If your bootloader unlocked try formatting your data in orange fox recovery and reboot and see if that fixes it. Just remember formatting data partition wipes everything on your device so anything you want to save be sure and transfer over to your PC first.
doesntwork
flash713 said:
If your bootloader unlocked try formatting your data in orange fox recovery and reboot and see if that fixes it. Just remember formatting data partition wipes everything on your device so anything you want to save be sure and transfer over to your PC first.
Click to expand...
Click to collapse
I got the same error - Android Rescue Party trigger..." and bootlop.
EDIT:
But I wiped:
Dalvik / ART Cache
Cache
System
Data
Didn't wipe: Internal storage and Vendor.
After that, i installed Global stable V11.0.5.0.QDGMIXM and get the same error, but some settings have been saved - for example my pattern for unlocking.
EDIT:
I did: wipe all, reboot to twrp, flash ROM, and when I try format data, I get error:
Formatting Data using mke2fs...
mke2fs -t ext4 b...
Proces ebded with ERROR: 1
Unable to wipe Data.
Unable to format to remove encryption.
EDiT3:
Success!
I tried once more, and it's ok.
Solution:
1. Wipe all via recovery
2. reboot to recovery
3. flash rom
4. Format data partition (format, no wipe, if mke2fs doesn't work, try with rm-f)
5. Reboot system.
After that everything is ok, at the end uploading stock recovery via adb went without a any problem.
Thanks!
Just to help many others. The trick here, is to format data, not just wipe data from TWRP. You need to hit format data from the wipe menu and type "yes" to confirm. Some things need to be said in plain English.
MetallicGR said:
Just to help many others. The trick here, is to format data, not just wipe data from TWRP. You need to hit format data from the wipe menu and type "yes" to confirm. Some things need to be said in plain English.
Click to expand...
Click to collapse
Thank you so much. I had formated the internal memory and working, no bootloop into recovery.
master_lam said:
Thank you so much. I had formated the internal memory and working, no bootloop into recovery.
Click to expand...
Click to collapse
i did all the steps you did and i still had problems, any other solution?
Forget it, your steps worked for me too!

how to decrypt after installing twrp

i have twrp installed using the bootloader unlock bypass.
how do i go about decrpyting the phone so i can install stuff from twrp in the future?
cheers
This question was lost with time.
If i seen it before i would have answered it before.
Wgen you first install vbmeta skip partition it wipes your security options. Messing with the encryption of your data partition.
The only way to gain access to the data partition again is to format the data partition and start the phone fresh.
I assume since this post is 2 months old you made the choice already to format data to gain access to you drive once more.
As long as you keep your new vbmeta through all your new zip installs you should be able to access your data on each update.

[Q] How to decrypt data partition without losing data?

Hi there,
My phone doesn't boot to android and returns to recovery every time, after doing a dirty installation from ArrowOS 11 encrypted to 12 also encrypted.
I made a backup, but I selected the internal storage by fault.
And now TWRP doesn't ask me for a password, so I can't decrypt the data partition.
What I tried to fix the issue:
I tried to install more than one TWRP version included [Orange fox, PBRP, and a one called twrp_ginkgo-willow-3.4A9_23-12-2020_BL.img (this was one I used before with ArrowOS 11]
installed the last working firmware and the latest ArrowOS 11 as I can't find older versions.
decrypting the data with this command: "ADB shell twrp decrypt mypincode"
The last time this happened to me, I followed those steps:
I had to wipe all partitions and clean install the same previous ROM
Then I created the same pin code as my previous one
I created a backup of boot, Dtbo, and recovery
restored my data backup through TWRP
restored the boot, Dtbo, and recovery
wiped the Dalvik / Art Cache and Cache
The problem now is that I created the backup on the internal storage by fault. If someone made the same pin code as mine and created a backup of the boot, Dtbo, and recovery for me is it going to work?
Is there anything else I can do to recover my data?
QuietLife said:
The problem now is that I created the backup on the internal storage by fault. If someone made the same pin code as mine and created a backup of the boot, Dtbo, and recovery for me is it going to work?
Click to expand...
Click to collapse
No, decryption key is unique
QuietLife said:
Is there anything else I can do to recover my data?
Click to expand...
Click to collapse
If you already (sometime in the past) flashed DFE wih format data , then just flash DFE and clear chache/dalvik + reboot
if you never did it then i'm afraid there is no solution ,you have to format
Ask in DFE topic to make sure
loopypalm said:
No, decryption key is unique
If you already (sometime in the past) flashed DFE wih format data , then just flash DFE and clear chache/dalvik + reboot
if you never did it then i'm afraid there is no solution ,you have to format
Ask in DFE topic to make sure
Click to expand...
Click to collapse
I didn't use it, but last time I didn't use it also and I restored my data, so I think I might have a chance.
Is there a way to backup the current encrypted data partition to a PC or a memory card?
QuietLife said:
I didn't use it, but last time I didn't use it also and I restored my data
Click to expand...
Click to collapse
Some roms does not encrypt data by default, that was the case i think
QuietLife said:
Is there a way to backup the current encrypted data partition to a PC or a memory card?
Click to expand...
Click to collapse
I never tried it (i never encrypt) so i'm not sure
you can change the bkp path in Ofox to USB (OTG) or SDCard and see if it work

Categories

Resources