While flashing anything via TWRP shows error message "failed to mount data argument".... in my m20sf
Any one Help to fix this proplem ?
You need to either format data partition or format all. First try the former.
Rooted.ndroid said:
You need to either format data partition or format all. First try the former.
Click to expand...
Click to collapse
Any other idea to fix without wiping?
DoomStoner said:
Any other idea to fix without wiping?
Click to expand...
Click to collapse
As per my knowledge there's no way around it.
the best you can do is to flash AP from odin along with HOME_CSC and then back everything up in either Samsung Cloud or Google Drive.Even though I haven't tried that option, it must work,if it doesnt dont point at me. But i'm more than open to help.
Same problem
Im on Android 10, I was trying to root using Magisk & TWRP as mentioned in other XDA Post.
Title:: "[RECOVERY] TWRP 3.3.0 for Galaxy M20"
----By DarkLord1731, Senior Member on 3rd March 2019, 08:54 AM
Even after multiple attempts, I also was unable to install
---no-verity-opt-encrypt, as well as---RMM Bypass zip using TWRP.
It kept on failing even when i tried different versions.
-------------
Later on when i tried flashing SuperSU , phone got bootlocked
Related
Hello,
Thanks for taking the time to look at this. I ran into a bootloop issue after updating my nexus 6 to a higher version of android. After I flashed the new version everything worked just fine but I kept getting the error message "Google play services has stopped" so I decided to re-flash something I thought I needed but after I flashed the file called "Modem firmware" it made me get stuck in a bootloop. The error I got during flashing in FlashFire was "IOException: write failed: ENOSPC (No space left on device)" and then after that infinite bootloop. I have TWRP installed but for some reason, I can't access my backup because it's asking for a decrypt code I didn't even setup. So is there a way to fix this? Possibly wipe the phone and install a custom ROM?
Thanks.
Wipe the phone, connect the N6 to your PC, and using ADB flash a stock ROM. Where the components are mismatched, flashing a stock ROM will resolve that issue and probably all your others. You will however need to flash your recovery and then your custom ROM - if you use one - as well as your root solution. Finally, whatever you do from now on, don't use Flashfire for the baseband.
irontaco1 said:
... so I decided to re-flash something I thought I needed but after I flashed the file called "Modem firmware" it made me get stuck in a bootloop. The error I got during flashing in FlashFire was "IOException: write failed: ENOSPC (No space left on device)" and then after that infinite bootloop. I have TWRP installed but for some reason, I can't access my backup because it's asking for a decrypt code I didn't even setup. So is there a way to fix this? Possibly wipe the phone and install a custom ROM?
Click to expand...
Click to collapse
Since I "routinely" flash modem zips through FF, I'm wondering if what you did was try to extract the modem img from the full software update? That is not a direction I would go in [emoji4]
There are modem flashable zips for the N6 that can be flashed through FF.
I also think the issue with accessing your back up is due to the user data partition being encrypted. What version of TWRP are you using? If not the newest (as of this writing 3.1.1-0), then that can also give you trouble.
irontaco1 said:
Hello,
Thanks for taking the time to look at this. I ran into a bootloop issue after updating my nexus 6 to a higher version of android. After I flashed the new version everything worked just fine but I kept getting the error message "Google play services has stopped" so I decided to re-flash something I thought I needed but after I flashed the file called "Modem firmware" it made me get stuck in a bootloop. The error I got during flashing in FlashFire was "IOException: write failed: ENOSPC (No space left on device)" and then after that infinite bootloop. I have TWRP installed but for some reason, I can't access my backup because it's asking for a decrypt code I didn't even setup. So is there a way to fix this? Possibly wipe the phone and install a custom ROM?
Thanks.
Click to expand...
Click to collapse
Read this for information on how to bypass the password that your backup is asking for https://www.google.com/amp/s/www.ho...fter-restoring-from-twrp-android-backups/amp/
Strephon Alkhalikoi said:
Wipe the phone, connect the N6 to your PC, and using ADB flash a stock ROM. Where the components are mismatched, flashing a stock ROM will resolve that issue and probably all your others. You will however need to flash your recovery and then your custom ROM - if you use one - as well as your root solution. Finally, whatever you do from now on, don't use Flashfire for the baseband.
Click to expand...
Click to collapse
Hey thanks for the help phone is running just fine now. I grabbed the factory image from the Google dev page and flashed it the hard way. For some reason ADB wouldn't mount /system after it was finished so I used fastboot to flash system, boot, radio, etc. Guess I won't use Flashfire for baseband anymore :laugh:
ktmom said:
Since I "routinely" flash modem zips through FF, I'm wondering if what you did was try to extract the modem img from the full software update? That is not a direction I would go in [emoji4]
There are modem flashable zips for the N6 that can be flashed through FF.
I also think the issue with accessing your back up is due to the user data partition being encrypted. What version of TWRP are you using? If not the newest (as of this writing 3.1.1-0), then that can also give you trouble.
Click to expand...
Click to collapse
Phone is working fine now. The files were encrypted because the stock kernel I was using was obviously non-permissive so it automatically encrypted my files upon reboot before it bootlooped. Really appreciate the help though.
I recently dusted off my Nexus 6 to test a few projects on and wanted to update everything. But no matter what I try within TWRP, every zip/img fails. Any guidance on how to repair the filesystem would be helpful. The attached images is the error. For now it seems shamu has been beached:crying:
Running TWP 3.1.1.0
ROM: LineageOS, not sure which version
Android version: 7.1.1
Bootloader is unlocked
Update to the latest TWRP and see if that helps. You want version 3.2.1-0.
https://dl.twrp.me/shamu/
Thanks, I just tried that. I was able to flash the recovery img through adb, but any attempt to flash a zip through fails with the same errors
format data on twrp you will lose everything so do backup
belive ihave the same problen but when i formated data with twrp the problem is gone so got to twrp - wipe -format data Type yes
ctrl1122 said:
Thanks, I just tried that. I was able to flash the recovery img through adb, but any attempt to flash a zip through fails with the same errors
Click to expand...
Click to collapse
Your safest bet would be going for a factory image, and then reflash twrp and then try again to see if everything is allright.
Or try formatting data from TWRP, like person above me mentioned. USB Drive+otg adapter might come in handy to keep stuff you want to flash there
VarDes said:
Your safest bet would be going for a factory image, and then reflash twrp and then try again to see if everything is allright.
Or try formatting data from TWRP, like person above me mentioned. USB Drive+otg adapter might come in handy to keep stuff you want to flash there
Click to expand...
Click to collapse
I'll give this a shot, seems likely it will rebuild the corrupted bits.
MiroALG said:
format data on twrp you will lose everything so do backup
belive ihave the same problen but when i formated data with twrp the problem is gone so got to twrp - wipe -format data Type yes
Click to expand...
Click to collapse
After doing this, data fails mount in TWRP. I will tryflashing a factory image. Thanks!
ctrl1122 said:
I'll give this a shot, seems likely it will rebuild the corrupted bits.
After doing this, data fails mount in TWRP. I will tryflashing a factory image. Thanks!
Click to expand...
Click to collapse
no problem back to stock with NRT then root and flash twrp and try it will fix all your problem
---------- Post added at 02:13 AM ---------- Previous post was at 02:12 AM ----------
MiroALG said:
no problem back to stock with NRT then root and flash twrp and try it will fix all your problem
Click to expand...
Click to collapse
but when you format your data you need to reboot to recovery again the copy your rom zip and gapps to your phone with pc or otg and flash
ctrl1122 said:
I'll give this a shot, seems likely it will rebuild the corrupted bits.
After doing this, data fails mount in TWRP. I will tryflashing a factory image. Thanks!
Click to expand...
Click to collapse
Success! Running the latest build now. Thanks everyone, I appreciate your time.
Hello, I installed AOSIP, everything works great but into twrp I can't decrypt data...
I've tried twrp R2.3.2.1 and R2.3.2.5, it says wrong password... I use the pin code of the ROM...
What can I do?
lcarolo said:
Hello, I installed AOSIP, everything works great but into twrp I can't decrypt data...
I've tried twrp R2.3.2.1 and R2.3.2.5, it says wrong password... I use the pin code of the ROM...
What can I do?
Click to expand...
Click to collapse
Hey, the same is happening to me since today, i'm looking why but i can't find the reason its drivin' me crazy i can't setup encryption...
edit : couldn't achieve to unlock TWRP with a custom ROM encryption, stock ROM encryption with MIUI is working fine tho... If someone has any infos
lcarolo said:
Hello, I installed AOSIP, everything works great but into twrp I can't decrypt data...
I've tried twrp R2.3.2.1 and R2.3.2.5, it says wrong password... I use the pin code of the ROM...
What can I do?
Click to expand...
Click to collapse
@Displayer
Your data from the last install appears to be encrypted. If you have a backup the easiest way to resolve the issue is to format your storage. You could also use the All in One tool and use its encryption removal option. Please keep in mind that it will wipe out all of your memes, so hopefully those are backed up.
tsongming said:
@Displayer
Your data from the last install appears to be encrypted. If you have a backup the easiest way to resolve the issue is to format your storage. You could also use the All in One tool and use its encryption removal option. Please keep in mind that it will wipe out all of your memes, so hopefully those are backed up.
Click to expand...
Click to collapse
I mean, i formatted to have a custom ROM booting, encrypting my data. I can use the phone, my pin code works in android but it's impossible to decrypt with TWRP...
Édit : found that message from argraur on telegram, so basically we have to wait for an updated twrp ? "Android release 9.0.0_r36 (r37) with May security patch has updated FBE encryption that breaks decryption in TWRP."
Displayer said:
I mean, i formatted to have a custom ROM booting, encrypting my data. I can use the phone, my pin code works in android but it's impossible to decrypt with TWRP...
Édit : found that message from argraur on telegram, so basically we have to wait for an updated twrp ? "Android release 9.0.0_r36 (r37) with May security patch has updated FBE encryption that breaks decryption in TWRP."
Click to expand...
Click to collapse
That doesn't even make sense. Twrp will not decrypt your phone.
Install Miui again, backup your data, to your desktop, by manually dragging your files over.
Go here and download DM-VERITY, FORCED ENCRYPTION, AND DISC QUOTA DISABLER you will use it to flash between updates or for dirty flashing Miui updates.
Next go back to TWRP the choose format and type yes reboot to TWRP ( you will se a message that says you have no OS are you sure?) Yes, reboot to TWRP
TWRP is not your issue, go read
and read the first comment here
Format storage, or wait for the TWRP and you still need to the format storage, Again a TWRP update will not resolve the issue. We have all had this exact issue.
I'm using another workaround:
With the all in one tool, we can flash .zip from a PC.
So I could install a custom kernel file from my pc directly into phone without loosing data.
Annoying thing is that I need the PC... Can't flash files that are in phone memory... Not such a big issue...
Another question, can I make a backup from the PC? Used to do it via twrp, but it is not safe with that issue...
lcarolo said:
I'm using another workaround:
With the all in one tool, we can flash .zip from a PC.
So I could install a custom kernel file from my pc directly into phone without loosing data.
Annoying thing is that I need the PC... Can't flash files that are in phone memory... Not such a big issue...
Another question, can I make a backup from the PC? Used to do it via twrp, but it is not safe with that issue...
Click to expand...
Click to collapse
Today i found a TWRP with decryption for may patch working for me here : https://forum.xda-developers.com/mi-8/development/recovery-unofficial-twrp-recovery-t3893823
I think u can pull img if i remember well but now its working for me
Displayer said:
Today i found a TWRP with decryption for may patch working for me here : https://forum.xda-developers.com/mi-8/development/recovery-unofficial-twrp-recovery-t3893823
I think u can pull img if i remember well but now its working for me
Click to expand...
Click to collapse
This twrp is working! Thanks a lot!
Hi
*No one answered on respective forum so kinda had to open a thread*
Im trying to install pixel exprience caf... Twrp gives:
28 (ErrorCode DownloadOperationExecutionError)
then
Updater process ended with error 1
previously I had havoc os and I followed the usual procedure as I did for havoc..
I tried adb sideload too. Still same error.. Only thing I didnt do is wipe data(for removing encryption) which seems unnecssary.. Can anyone point me in right direction? Someone who was able to install? It seems Im missing something..
Update 2:
Temporary boot of twrp image 3.2.3 cause OpenDeviceError and twrp 3.3.1 cuause error 28 just like above..
I tried above guide from @firdausimbolon didn't help
https://forum.xda-developers.com/mi-a2/how-to/how-to-avoid-error-28-flash-rom-t3941024
I would really appreciate a proper solution, thanks
wipe all partitions and format data as well on both slots then boot into 3.2.3 if it still doesnt work go to stock oreo rom then follow this guide
https://forum.xda-developers.com/mi-a2/how-to/guide-how-to-flash-custom-roms-stuff-t3876375
Stoopid Dickhead said:
wipe all partitions and format data as well on both slots then boot into 3.2.3 if it still doesnt work go to stock oreo rom then follow this guide
https://forum.xda-developers.com/mi-a2/how-to/guide-how-to-flash-custom-roms-stuff-t3876375
Click to expand...
Click to collapse
I have twrp 3.3 already which was installed by Havoc OS, Should I just temporary boot into twrp 3.2.3?
Cause It possibly will cause OpenDevice Error.
Also I followed the guide already, fastboot -w doesn't work, says failed to get user data so I have to do wipe from twrp itself(system,cache,data) + flashing in both slots cause same error... I will try again more carefully, Maybe I missed some stuff, thanks for reminding me again, I might get it right this time!
update2:Simply downloaded file was corrupted, Now It's Installed
wasd588 said:
I have twrp 3.3 already which was installed by Havoc OS, Should I just temporary boot into twrp 3.2.3?
Cause It possibly will cause OpenDevice Error.
Also I followed the guide already, fastboot -w doesn't work, says failed to get user data so I have to do wipe from twrp itself(system,cache,data) + flashing in both slots cause same error... I will try again more carefully, Maybe I missed some stuff, thanks for reminding me again, I might get it right this time!
update2:Simply downloaded file was corrupted, Now It's Installed
Click to expand...
Click to collapse
temp booting 3.2.3 worked for me although i booted in different slot than 3.3.1, also glad that your device works.
Glad that your device is bootable again.
Hi guys. I rooted my phone before last update with "magisk patch ap file" method. But this method isn't working with the new firmware. And i tried to root with twrp too and it boots but in a black screen its written verification failed. So the both not working anymore. How u guys able to root your m20?
And how about havoc os gsi? Is there a guide for it?
alfadyn said:
Hi guys. I rooted my phone before last update with "magisk patch ap file" method. But this method isn't working with the new firmware. And i tried to root with twrp too and it boots but in a black screen its written verification failed. So the both not working anymore. How u guys able to root your m20?
And how about havoc os gsi? Is there a guide for it?
Click to expand...
Click to collapse
Hey all you need to do is wipe data partition by changing it's file format.
For that do the usual routing stuff.
Boot into Twrp
Formata Data -- Yes---
Flash RMM
Wipe--- Advanced -- data -- change/repair--- choose the one left of f2fs --- wipe --- f2fs now --- wipe --- back
Install magisk
Boom
Let me know if video is needed.
Rooted.ndroid said:
Hey all you need to do is wipe data partition by changing it's file format.
For that do the usual routing stuff.
Boot into Twrp
Formata Data -- Yes---
Flash RMM
Wipe--- Advanced -- data -- change/repair--- choose the one left of f2fs --- wipe --- f2fs now --- wipe --- back
Install magisk
Boom
Let me know if video is needed.
Click to expand...
Click to collapse
https://forum.xda-developers.com/galaxy-m20/development/recovery-twrp-3-2-3-galaxy-m20-t3906705
first i did everything correctly in this post above.
after that i followed your procedure and i did everything correctly.
and it boot up without showing verification error. i was really happy and wanted to thank you. but after i rebooted my device. an then it said only official binaries allowed. then i flashed the firmware again because it cant be booted otherwise now it stucked at the samsung screen. i dont know why samsung makes things like this complicated.
edit: it booted after i format data. but still no root
alfadyn1 said:
https://forum.xda-developers.com/galaxy-m20/development/recovery-twrp-3-2-3-galaxy-m20-t3906705
first i did everything correctly in this post above.
after that i followed your procedure and i did everything correctly.
and it boot up without showing verification error. i was really happy and wanted to thank you. but after i rebooted my device. an then it said only official binaries allowed. then i flashed the firmware again because it cant be booted otherwise now it stucked at the samsung screen. i dont know why samsung makes things like this complicated.
edit: it booted after i format data. but still no root
Click to expand...
Click to collapse
Do you have twrp installed right now?
And did you flash RMM bypass?
Rooted.ndroid said:
Do you have twrp installed right now?
And did you flash RMM bypass?
Click to expand...
Click to collapse
yes i flashed rmm bypass v2 and i realized that there is version 3 i will try with it. and tell how it goes
---------- Post added at 12:02 PM ---------- Previous post was at 11:32 AM ----------
Rooted.ndroid said:
Do you have twrp installed right now?
And did you flash RMM bypass?
Click to expand...
Click to collapse
i didnt get the. only official relases error and it booted up. but i got a sweet bootloop right now . im done with it i ll never try to root again can u tell me how do i get rid of this bootloop
edit: got out of bootloop flashed official firmware. thank you for the help never gonna try to root again