I have been trying to flash Magisk onto my device (H930) however when I do this using TWRP I get the following message:
Failed to mount /vendor (invalid argument)
I have looked around and haven't been able to find much on this issue and how to resolve it. In order to get this to work is this becasuse I haven't got a Vendor Partition available on my phone? If so is the correct way of resolving this by following this guide: https://forum.xda-developers.com/lg-v30/how-to/guide-how-to-repartition-vendor-how-to-t3789787
I am very new to all of this and am still finding my ground in regards to how to all this using ADB and TWRP.
Any assistance would really help!
Sixtte said:
I have been trying to flash Magisk onto my device (H930) however when I do this using TWRP I get the following message:
Failed to mount /vendor (invalid argument)
I have looked around and haven't been able to find much on this issue and how to resolve it. In order to get this to work is this becasuse I haven't got a Vendor Partition available on my phone? If so is the correct way of resolving this by following this guide: https://forum.xda-developers.com/lg-v30/how-to/guide-how-to-repartition-vendor-how-to-t3789787
I am very new to all of this and am still finding my ground in regards to how to all this using ADB and TWRP.
Any assistance would really help!
Click to expand...
Click to collapse
You NEVER need a vendor petition on your phone unless you intend to flash a Treble-ized ROM.
What version of Magisk are you trying to use? In TWRP, try rebooting to recovery from the TWRP menu and see if it mounts.
You are following the instructions in the WTF thread, right?
ChazzMatt said:
You NEVER need a vendor petition on your phone unless you intend to flash a Treble-ized ROM.
What version of Magisk are you trying to use? In TWRP, try rebooting to recovery from the TWRP menu and see if it mounts.
You are following the instructions in the WTF thread, right?
Click to expand...
Click to collapse
I followed that thread exactly and got the same issue. Then when I tried to flash back to stock kdz it kept timing out then completely bricked the phone so RIP.
Sixtte said:
I have been trying to flash Magisk onto my device (H930) however when I do this using TWRP I get the following message:
Failed to mount /vendor (invalid argument)
I have looked around and haven't been able to find much on this issue and how to resolve it. In order to get this to work is this becasuse I haven't got a Vendor Partition available on my phone? If so is the correct way of resolving this by following this guide: https://forum.xda-developers.com/lg-v30/how-to/guide-how-to-repartition-vendor-how-to-t3789787
I am very new to all of this and am still finding my ground in regards to how to all this using ADB and TWRP.
Any assistance would really help!
Click to expand...
Click to collapse
Why do you need vendor partition? That's not part of WTF bootloader unlock and root instructions.
Do you intend to flash Treble-ized ROMs? You don't need vendor partition for normal ROMs...
---------- Post added at 10:01 PM ---------- Previous post was at 10:00 PM ----------
See below.
ChazzMatt said:
You NEVER need a vendor petition on your phone unless you intend to flash a Treble-ized ROM.
What version of Magisk are you trying to use? In TWRP, try rebooting to recovery from the TWRP menu and see if it mounts.
You are following the instructions in the WTF thread, right?
Click to expand...
Click to collapse
I don't know why I need or don't need one. All I was trying to do was flash a slightly modified stock firmware through TWRP and that's the error it gave.
Cordtus said:
I don't know why I need or don't need one. All I was trying to do was flash a slightly modified stock firmware through TWRP and that's the error it gave.
Click to expand...
Click to collapse
For you, you were trying to get back to H933 from US998. The person who wrote those instructions will have to answer why that's neccesary.
I'm asking the guy who started this thread, and he has H930. He has always been on H930.
ChazzMatt said:
For you, you were trying to get back to H933. The person who wrote those instructions will have to answer why that's neccesary.
I'm asking the guy who started this thread, and he has H930.
Click to expand...
Click to collapse
Does the 933 need a vendor partition then? Is that how i royally ****ed myself?
Sixtte said:
I have been trying to flash Magisk onto my device (H930) however when I do this using TWRP I get the following message:
Failed to mount /vendor (invalid argument)
I have looked around and haven't been able to find much on this issue and how to resolve it.
In order to get this to work is this because I haven't got a Vendor Partition available on my phone? If so is the correct way of resolving this by following this guide: https://forum.xda-developers.com/lg-v30/how-to/guide-how-to-repartition-vendor-how-to-t3789787
Click to expand...
Click to collapse
@Sixtte, I have asked a lot of question the past couple of days to you to get more information and you are not responding. Did you solve your problem?
The thread you are citing is HOW TO GET A VENDOR PARTITION, BUT YET you claim you do NOT have one. If you could answer the other questions I asked earlier we can try to find out why TWRP thinks you have a vendor partition or possibly how you created one without realizing it.
@seadersn, questions for you as the TWRP expert...
Could TWRP be saying he has a vendor partition when he doesn't?
Could he have created a vendor partition using the "basic" TWRP in WTF thread or does that need the more advanced TWRP in the dedicated TWRP threads?
IF someone can create a vendor partition using the the the "basic" TWRP in WTF thread, can they mount vendor partition using that basic TWRP or does that need the more advanced TWRP in the dedicated TWRP threads?
Note that last question is slightly different -- create on one TWRP, but need another version to actually mount that vendor partition.
ChazzMatt said:
@Sixtte, I have asked a lot of question the past couple of days to you to get more information and you are not responding. Did you solve your problem?
The thread you are citing is HOW TO GET A VENDOR PARTITION, BUT YET you claim you do NOT have one. If you could answer the other questions I asked earlier we can try to find out why TWRP thinks you have a vendor partition or possibly how you created one without realizing it.
@seadersn, questions for you as the TWRP expert...
Could TWRP be saying he has a vendor partition when he doesn't?
Could he have created a vendor partition using the "basic" TWRP in WTF thread or does that need the more advanced TWRP in the dedicated TWRP threads?
IF someone can create a vendor partition using the the the "basic" TWRP in WTF thread, can they mount vendor partition using that basic TWRP or does that need the more advanced TWRP in the dedicated TWRP threads?
Note that last question is slightly different -- create on one TWRP, but need another version to actually mount that vendor partition.
Click to expand...
Click to collapse
@ChazzMatt Apologies for not getting back to you, I have been having issues with my internet. No I haven't managed to resolve my problem and are still looking to sort it.
I have been trying to flash Magisk Version: 17.1 But when I try I get the above issue. I do not know whether I need the Vendor or not to mount Magisk, this is just what is coming up when I am flashing it. The thread I have cited is just what I have found which may be a possible solution. Booting into recovery from twrp didn't enable the mount to work.
Whatever I have tried it seems to think I don't have a vendor partition or that I need to have one to flash Magisk.
ChazzMatt said:
@Sixtte, I have asked a lot of question the past couple of days to you to get more information and you are not responding. Did you solve your problem?
The thread you are citing is HOW TO GET A VENDOR PARTITION, BUT YET you claim you do NOT have one. If you could answer the other questions I asked earlier we can try to find out why TWRP thinks you have a vendor partition or possibly how you created one without realizing it.
@seadersn, questions for you as the TWRP expert...
Could TWRP be saying he has a vendor partition when he doesn't?
Could he have created a vendor partition using the "basic" TWRP in WTF thread or does that need the more advanced TWRP in the dedicated TWRP threads?
IF someone can create a vendor partition using the the the "basic" TWRP in WTF thread, can they mount vendor partition using that basic TWRP or does that need the more advanced TWRP in the dedicated TWRP threads?
Note that last question is slightly different -- create on one TWRP, but need another version to actually mount that vendor partition.
Click to expand...
Click to collapse
i don't know this 100% atm, but imo every twrp can ***** about a non-existent partition. no matter if it has capabilities for that particular partition or not. would need to test this to be really sure but that doesn't help him.
vendor partition creating is independent of twrp version, the script uses a default command available in twrp = sgdisk. so every recovery version available can create a vendor partition.
mounting no way with default only with DataIMG and IntSD versions, and SGCMarkus' vendorized recovery, since these have vendor mounting capability. for being able to mount vendor an fstab entry is needed, which isn't present in default recovery.
Sixtte said:
@ChazzMatt Apologies for not getting back to you, I have been having issues with my internet. No I haven't managed to resolve my problem and are still looking to sort it.
I have been trying to flash Magisk Version: 17.1 But when I try I get the above issue. I do not know whether I need the Vendor or not to mount Magisk, this is just what is coming up when I am flashing it. The thread I have cited is just what I have found which may be a possible solution. Booting into recovery from twrp didn't enable the mount to work.
Whatever I have tried it seems to think I don't have a vendor partition or that I need to have one to flash Magisk.
Click to expand...
Click to collapse
You shouldn't have a vendor partition unless you intentionally created one. @seadersn can possibly investigate why TWRP thinks you have a vendor partition. I don't understand why that should prevent you from flashing Magisk. I've never had a vendor partition, and my TWRP has never mistakenly thought I did.
In the WTF instructions I suggest Magisk 17.3, by the way. 17.1 should still work, however.
Related
Hi guys
Can't install any OS (tried via ADB commands and flashing custom roms via TWRP).
Whatever I try, it just boots to TWRP.
ADB commands do work because I managed to install TWRP 3.0 and 3.1 for the Moto Z Griffin
Bootloader is unlocked
This device was working fine on Stock Noughat (installed via ADB) and AOKP (installed via TWRP).
Problems began when the camera "failed to start" and in my frustration, I wiped everything via TWRP including system, so now I have no OS.
Not sure why I can't get anything to install.
Follow this guide: https://forum.xda-developers.com/showthread.php?t=3506342
Sent from my XT1650 using XDA-Developers Legacy app
grneyez said:
Follow this guide: https://forum.xda-developers.com/showthread.php?t=3506342
Sent from my XT1650 using XDA-Developers Legacy app
Click to expand...
Click to collapse
followed that guide
Had this working for months and needed to wipe so I did a factory reset and all my phone does is boot to twrp
I tried this process again and all goes good or so it seems but just boots to twrp
I tried a restore from my backup from twrp and get all the way done and it fails on "unable to wipe Fsg."
Above there is a bunch of red failed:
Could not mount /data and unable to find crypto foooter
Failed to mount '/data' (Invalid argument)
Unable to recreate /data/media folder
Failed to mount'/cache' (invalid argument)
failed to mount'/system'(invalid argument)
Failed to mount storage
failed to mount'/data'(invalid argument)
failed to mount'/cache'(invalid argument)
failed to mount'/data/media/twrp'(invalid argument)
unable to wipe fsg.
any ideas? right now just a brick here. i have tried flashing roms from twrp and still just boot to twrp
I'm assuming you tried to flash the stock ROM via fastboot?
If so, I'm a little at a loss here. Although since you have TWRP, try flashing the stock ROM along with its recovery following the guide linked below;
https://forum.xda-developers.com/moto-z/development/android-nougat-moto-z-versions-t3506342
And grab the firmware for your device here;
https://firmware.center/firmware/Motorola/Moto Z/Stock/XT1650-03/
Make sure it's the correct firmware for your device. If you updated to Nougat via an OTA, you have to flash a Nougat ROM. You may also use the one linked in the XDA article, although I can't guarantee its stability.
D13H4RD2L1V3 said:
I'm assuming you tried to flash the stock ROM via fastboot?
If so, I'm a little at a loss here. Although since you have TWRP, try flashing the stock ROM along with its recovery following the guide linked below;
https://forum.xda-developers.com/moto-z/development/android-nougat-moto-z-versions-t3506342
And grab the firmware for your device here;
https://firmware.center/firmware/Motorola/Moto Z/Stock/XT1650-03/
Make sure it's the correct firmware for your device. If you updated to Nougat via an OTA, you have to flash a Nougat ROM. You may also use the one linked in the XDA article, although I can't guarantee its stability.
Click to expand...
Click to collapse
Maybe it's because I haven't had my coffee yet, but is there a US 7.0 file on that site? I can only find the 6.0 version. I'm on Rodgers nougat rom I flashed a couple weeks ago and I'd like to get on the US version since I've been having apn issues
royalflush5 said:
Maybe it's because I haven't had my coffee yet, but is there a US 7.0 file on that site? I can only find the 6.0 version. I'm on Rodgers nougat rom I flashed a couple weeks ago and I'd like to get on the US version since I've been having apn issues
Click to expand...
Click to collapse
Sadly, no.
As of right now, there's only a Marshmallow-based RETUS firmware. It'll take a while for someone to post firmware that's Nougat-based for RETUS.
D13H4RD2L1V3 said:
Sadly, no.
As of right now, there's only a Marshmallow-based RETUS firmware. It'll take a while for someone to post firmware that's Nougat-based for RETUS.
Click to expand...
Click to collapse
Ah, thanks for confirming. Do you happen to know of a twrp flashable zip for retus 7.0 then?
royalflush5 said:
Ah, thanks for confirming. Do you happen to know of a twrp flashable zip for retus 7.0 then?
Click to expand...
Click to collapse
Again, there's sadly no TWRP-flashable firmware for 7.0 RETUS.
There's only one for TELUS. While it works on other XT1650-03s with unlocked BLs, can't guarantee that it's all stable.
https://forum.xda-developers.com/moto-z/development/android-nougat-moto-z-unlocked-versions-t3552210
I know this thread is old but maybe this will help someone out. I had the exact same problem after a Factory Reset my phone went on a TWRP bootloop. To resolve it, just reboot into Bootloader and then select Factory Mode. My phone just started as new.
lovetatfitties said:
I know this thread is old but maybe this will help someone out. I had the exact same problem after a Factory Reset my phone went on a TWRP bootloop. To resolve it, just reboot into Bootloader and then select Factory Mode. My phone just started as new.
Click to expand...
Click to collapse
Thank you for this!!!!!!! It solved my boot loop problem too after installing stock via fastboot. Only thing that worked.
raymccoy said:
Thank you for this!!!!!!! It solved my boot loop problem too after installing stock via fastboot. Only thing that worked.
Click to expand...
Click to collapse
thanks for the Rescue same trick work for me though as i was been stuck on TWRP after flashing stock firmware via fastboot , so i manage to flash irfan v4 stock rom and booted to factory image to get it resolved , But now i want to move to complete stock without twrp as i think Oreo update is near by but i get the same issue again, Just wanna ask can u help me out with the process to go back to stock Rom
lovetatfitties said:
I know this thread is old but maybe this will help someone out. I had the exact same problem after a Factory Reset my phone went on a TWRP bootloop. To resolve it, just reboot into Bootloader and then select Factory Mode. My phone just started as new.
Click to expand...
Click to collapse
that worked for me also, but it's not a fix, its a workaround. is there an actual fix for this? I've tried the Verity_FE_patcher but that didn't work also.
I have clean installed Magisk because of an irregularity. To be specific: when I TWRP>Install systemless_xposed-uninstaller-signed.zip, I get an error: Updater process ended with ERROR: 1. TWRP last_log shows ¨e2fsck: No such file or directory¨while trying to open /data/adb/magisk.img¨. So Magisk seems not to be installed.
While this happens, at the same time, when sytem is booted, I have no issues (seemingly) using Magisk manager and installing and using modules.
Because of this irregularity I clean installed Magisk:
- un-installed Magisk through Magisk manager>Uninstall>Complete uninstall
- flashed stock boot image using ¨fastboot flash ramdisk RAMDISK.img¨
- and re-installed Magisk TWRP>Install Magisk-v16.0.zip
After which the Magisk installation on my device is still broken in some way and regarded as ¨weird¨ by fellow xda members; I was advised to ask about it in the device forum.
I attach last_log-magisk-install.txt & last_log-systemless_xposed-uninstaller-signed.txt
Does anybody have a clue and/or experience in this matter maybe?
It's because /data/adb/ is encrypted after installing Magisk.
Not sure why it does that, that folder used to stay unencrypted after installing.
You can use TWRP file manager and check /data/adb/ for encrypted files, and check while booted too. If it's empty it is indeed not installing correctly.
Why are you running Xposed uninstaller by the way?
ante0 said:
It's because /data/adb/ is encrypted after installing Magisk.
Not sure why it does that, that folder used to stay unencrypted after installing.
You can use TWRP file manager and check /data/adb/ for encrypted files, and check while booted too. If it's empty it is indeed not installing correctly.
Why are you running Xposed uninstaller by the way?
Click to expand...
Click to collapse
/data/adb in twrp filemanager looks encrypted yes. Booted to system however, it shows correctly (screenshot). I do not understand why you expected it to be empty as you say.
What do you advise? Decrypt data partition maybe?
You ask why i run Xposed uninstaller; I just ran this script now to get the log. Before all this investgation started I was advised to run it to get rid of possible Xposed framework leftovers after I had installed Xposed, bootlooped and deletef the module.
lvbaal said:
/data/adb in twrp filemanager looks encrypted yes. Booted to system however, it shows correctly (screenshot). I do not understand why you expected it to be empty as you say.
What do you advise? Decrypt data partition maybe?
You ask why i run Xposed uninstaller; I just ran this script now to get the log. Before all this investgation started I was advised to run it to get rid of possible Xposed framework leftovers after I had installed Xposed, bootlooped and deletef the module.
Click to expand...
Click to collapse
No, I meant if it was empty it would be a reason why it can't find magisk.img. But in this case its encryption thats causing it.
You could decrypt, it would fix it. Though as you probably know you'd have to do this after each update.
You might be able to go back to fastboot directly after update finishes and flash twrp, then to twrp and replace fstab in /vendor/etc/ so it doesn't encrypt again. I haven't tested but should work. As long as you don't boot to system before replacing fstab it should stay decrypted.
I have a feeling it's caused by the FBE bypass that was introduced in v16 (actually 1541 from the custom honor v10 link, but added in 16 to stable). Magisk refused to even install because of encryption before this was fixed.
ante0 said:
No, I meant if it was empty it would be a reason why it can't find magisk.img. But in this case its encryption thats causing it.
You could decrypt, it would fix it. Though as you probably know you'd have to do this after each update.
You might be able to go back to fastboot directly after update finishes and flash twrp, then to twrp and replace fstab in /vendor/etc/ so it doesn'tencrypt again. I haven't tested but should work. As long as you don't boot to system before replacing fstab it should stay decrypted.
I have a feeling it's caused by the FBE bypass that was introduced in v16 (actually 1541 from the custom honor v10 link, but added in 16 to stable). Magisk refused to even install because of encryption before this was fixed.
Click to expand...
Click to collapse
Thanks for your input. I'll keep decrypting in mind. For now, it looks like I can install a module from Magisk manager - greenify4magisk. I could not do this however when I had v16. Now on v16.1 it installs. I will check it's functioning later.
ante0 said:
No, I meant if it was empty it would be a reason why it can't find magisk.img. But in this case its encryption thats causing it.
You could decrypt, it would fix it. Though as you probably know you'd have to do this after each update.
You might be able to go back to fastboot directly after update finishes and flash twrp, then to twrp and replace fstab in /vendor/etc/ so it doesn't encrypt again. I haven't tested but should work. As long as you don't boot to system before replacing fstab it should stay decrypted.
I have a feeling it's caused by the FBE bypass that was introduced in v16 (actually 1541 from the custom honor v10 link, but added in 16 to stable). Magisk refused to even install because of encryption before this was fixed.
Click to expand...
Click to collapse
I'm not sure what alteration in /vendor/etc/fstab is needed to prevent encryption. Can you elaborate maybe? Also, in this regard, can you confirm the following:
when I decide to format internal storage in TWRP with ¨Format Data¨and thus getting rid of encryption(link), will it still be (re-)encrypted if I use the unmodified stock kernel (I'm using stock Emui8)? If so, do you know of a modified kernel without encryption for BLA-L29(C432)?
lvbaal said:
I'm not sure what alteration in /vendor/etc/fstab is needed to prevent encryption. Can you elaborate maybe? Also, in this regard, can you confirm the following:
when I decide to format internal storage in TWRP with ¨Format Data¨and thus getting rid of encryption(link), will it still be (re-)encrypted if I use the unmodified stock kernel (I'm using stock Emui8)? If so, do you know of a modified kernel without encryption for BLA-L29(C432)?
Click to expand...
Click to collapse
This flag: ",fileencryption=aes-256-xts:aes-256-cts" on the /data line needs to be removed. After that you format data in twrp and decryption will stick. As of Oreo fstab is located in /vendor/etc so it doesn't matter what ramdisk you use, only matter is when you update firmware as /vendor is over-written. In theory you should be able to update, go straight to fastboot after and flash twrp, go to twrp and replace fstab. I haven't tested that yet, but as long as you don't boot to system it should stay decrypted.
(TWRP with FBE decryption support is on the horizon so you might want to wait. A fix was pushed a few days ago and it works on Honor 9, we just need a newly built twrp. I can't get the 8.1 tree to build a working one so I will check if it can be done with the 7.1 tree.)
ante0 said:
This flag: ",fileencryption=aes-256-xts:aes-256-cts" on the /data line needs to be removed. After that you format data in twrp and decryption will stick. As of Oreo fstab is located in /vendor/etc so it doesn't matter what ramdisk you use, only matter is when you update firmware as /vendor is over-written. In theory you should be able to update, go straight to fastboot after and flash twrp, go to twrp and replace fstab. I haven't tested that yet, but as long as you don't boot to system it should stay decrypted.
(TWRP with FBE decryption support is on the horizon so you might want to wait. A fix was pushed a few days ago and it works on Honor 9, we just need a newly built twrp. I can't get the 8.1 tree to build a working one so I will check if it can be done with the 7.1 tree.)
Click to expand...
Click to collapse
Hi and thanks for the clarification. As I'm in the process of re-flashing complete stock firmware (131->138 from pro-teammt.ru) I think I will be going for the solution provided by @Didgeridoohan. As I understand it at this moment, both solutions will permanently decrypt my /data, but the your solution does not mention Magisk installation. Does a Magisk installation not have any bearing to the issue then?
lvbaal said:
Hi and thanks for the clarification. As I'm in the process of re-flashing complete stock firmware (131->138 from pro-teammt.ru) I think I will be going for the solution provided by @Didgeridoohan. As I understand it at this moment, both solutions will permanently decrypt my /data, but the your solution does not mention Magisk installation. Does a Magisk installation not have any bearing to the issue then?
Click to expand...
Click to collapse
I'm not sure Magisk can. It could when I pushed a commit that added fileencryptioninline (this was for nougat), and when fstab was located in boot partition.
But that was removed as it broke support for Pixel devices.
This is what it looks for: https://github.com/topjohnwu/Magisk...285d860b4d95db13f7/native/jni/utils/pattern.c
"const char *encrypt_list[] = { "forceencrypt", "forcefdeorfbe", NULL };"
As you see it doesn't contain "fileencryption".
I'm not sure it even looks for fstab in /vendor. That would break the systemlessness of Magisk (doesn't modify /system or /vendor)
Though, it doesn't matter anyway, it does the exact same thing as manually editing /vendor/etc/fstab.kirin970
You can test though, to confirm
When you do Format Data you need to manually flash back the public and hw data zips in TWRP, they give errors but it's the folder "hw_init" that's placed in /data/ that's needed. Themes and stuff are in there.
ante0 said:
This flag: ",fileencryption=aes-256-xts:aes-256-cts" on the /data line needs to be removed. After that you format data in twrp and decryption will stick. As of Oreo fstab is located in /vendor/etc so it doesn't matter what ramdisk you use, only matter is when you update firmware as /vendor is over-written. In theory you should be able to update, go straight to fastboot after and flash twrp, go to twrp and replace fstab. I haven't tested that yet, but as long as you don't boot to system it should stay decrypted.
(TWRP with FBE decryption support is on the horizon so you might want to wait. A fix was pushed a few days ago and it works on Honor 9, we just need a newly built twrp. I can't get the 8.1 tree to build a working one so I will check if it can be done with the 7.1 tree.)
Click to expand...
Click to collapse
Thanks again But I cannot quite picture this; when you say ¨In theory you should be able to update, go straight to fastboot after and flash twrp¨, because when I have flashed the complete stock firmware, I suppose Developper option USB debugging is off and I cannot send command <fastboot flash recovery_ramdisk twrp.img> from PC, or can I?
lvbaal said:
Thanks again But I cannot quite picture this; when you say ¨In theory you should be able to update, go straight to fastboot after and flash twrp¨, because when I have flashed the complete stock firmware, I suppose Developper option USB debugging is off and I cannot send command <fastboot flash recovery_ramdisk twrp.img> from PC, or can I?
Click to expand...
Click to collapse
When you flash on Oreo it will not wipe anything, /data stays.
Basically it does an OTA but with a full fw.
Unless you factory reset after, then it would wipe.
As I said it's in theory as I haven't tested it yet, so you're free to try if you're going to update anyway
Mine has been on everytime I've updated anyway. Only difference was in Nougat where bootloader was locked and you had to unlock it, which meant a mandatory wipe...
ante0 said:
This flag: ",fileencryption=aes-256-xts:aes-256-cts" on the /data line needs to be removed. After that you format data in twrp and decryption will stick. As of Oreo fstab is located in /vendor/etc so it doesn't matter what ramdisk you use, only matter is when you update firmware as /vendor is over-written. In theory you should be able to update, go straight to fastboot after and flash twrp, go to twrp and replace fstab. I haven't tested that yet, but as long as you don't boot to system it should stay decrypted.
(TWRP with FBE decryption support is on the horizon so you might want to wait. A fix was pushed a few days ago and it works on Honor 9, we just need a newly built twrp. I can't get the 8.1 tree to build a working one so I will check if it can be done with the 7.1 tree.)
Click to expand...
Click to collapse
Hello again. I've studied the shell scripts used in the HWOTA8 package and found out that the kernel and stock recovery will be flashed to the device after which it switches to recovery mode and the update zips will be pushed to /data/update along with update commands in /cache/recovery/command. Then it is supposed to reboot to recovery; to apply the updates I presume?. So when I interrupt this flow and do not boot to recovery but to fastboot to flash twrp and replace fstab, how will the updates be applied then?
I attach the script in question.
Any news already on TWRP on the horizon?
lvbaal said:
Hello again. I've studied the shell scripts used in the HWOTA8 package and found out that the kernel and stock recovery will be flashed to the device after which it switches to recovery mode and the update zips will be pushed to /data/update along with update commands in /cache/recovery/command. Then it is supposed to reboot to recovery; to apply the updates I presume?. So when I interrupt this flow and do not boot to recovery but to fastboot to flash twrp and replace fstab, how will the updates be applied then?
I attach the script in question.
Any news already on TWRP on the horizon?
Click to expand...
Click to collapse
First, copy fstab to computer and remove the fileencryption flag.
If course you need to flash update first.
You install update using HWOTA8. After it's done with the update in recovery mode you boot directly to fastboot instead of booting to system. You'd have to watch phone while it's updating as it reboota automatically. You should have USB plugged in already, so just start holding vol down when it says update is complete and it will reboot and you should land in fastboot. Now flash twrp to recovery_ramdisk and type 'fastboot reboot'. Remove USB and hold vol up. Now you should boot to twrp. Adb push the modified fstab to /vendor/etc/fstab.kirin970.
Also check Internal storage in twrp to make sure it's still decrypted. (you would have to decrypt before installing update to make sure this theory actually works ).
I could actually test it tonight on my Mate 9.
As for TWRP, the fix has been pushed to gerrit but it's not merged yet. I've been trying to get the android-8.0/8.1 branch to build a functional twrp but no luck yet. For some reason a bunch of folders are missing, and I'm not sure why. They are there in the source branch for both 8.0/8.1... I will test using git clone instead if repo sync.
ante0 said:
As for TWRP, the fix has been pushed to gerrit but it's not merged yet. I've been trying to get the android-8.0/8.1 branch to build a functional twrp but no luck yet. For some reason a bunch of folders are missing, and I'm not sure why. They are there in the source branch for both 8.0/8.1... I will test using git clone instead if repo sync.
Click to expand...
Click to collapse
I managed to build an Ubuntu based development environment, but using minimal manifest (8.1 branch) to build TWRP throws errors (i don't know if you have the same errors).
Here's the error log - > https://pastebin.com/C6jVg2eY
ante0 said:
First, copy fstab to computer and remove the fileencryption flag.
If course you need to flash update first.
You install update using HWOTA8. After it's done with the update in recovery mode you boot directly to fastboot instead of booting to system. You'd have to watch phone while it's updating as it reboota automatically. You should have USB plugged in already, so just start holding vol down when it says update is complete and it will reboot and you should land in fastboot. Now flash twrp to recovery_ramdisk and type 'fastboot reboot'. Remove USB and hold vol up. Now you should boot to twrp. Adb push the modified fstab to /vendor/etc/fstab.kirin970.
Also check Internal storage in twrp to make sure it's still decrypted. (you would have to decrypt before installing update to make sure this theory actually works ).
I could actually test it tonight on my Mate 9.
As for TWRP, the fix has been pushed to gerrit but it's not merged yet. I've been trying to get the android-8.0/8.1 branch to build a functional twrp but no luck yet. For some reason a bunch of folders are missing, and I'm not sure why. They are there in the source branch for both 8.0/8.1... I will test using git clone instead if repo sync.
Click to expand...
Click to collapse
Actually the ota.sh script boots to recovery after pushing the update. Presumably to apply the update through stock recovery. There fore I issued command adb reboot bootloader in an other powershell window. Then I flashed TWRP rebooted to TWRP to replace replaced fstab but then TWRP decides to apply the update because of input in /cache/recovery/command, so at that point I cannot replace fstab. Therefor I altered the script ota.sh and de-activated writes to /cache/recovery/command, and started over...
[/B]
lvbaal said:
Actually the ota.sh script boots to recovery after pushing the update. Presumably to apply the update through stock recovery. There fore I issued command adb reboot bootloader in an other powershell window. Then I flashed TWRP rebooted to TWRP to replace replaced fstab but then TWRP decides to apply the update because of input in /cache/recovery/command, so at that point I cannot replace fstab. Therefor I altered the script ota.sh and de-activated writes to /cache/recovery/command, and started over...
[/B]
Click to expand...
Click to collapse
Well, it has to apply the update in stock recovery. It can't do it in TWRP.
Basically you:
Format Data in TWRP and replace fstab with one that has fileencryption flag removed.
Boot to system once and then back to TWRP, check that you are decrypted (file manager in TWRP to Internal SD or browse child folders in /data).
Run HWOTA8 and let it update through stock recovery.
When it's done updating and about to reboot back to system, hold vol down so it goes to fastboot mode.
Now flash TWRP and issue 'fastboot reboot', quickly remove usb cable and hold volume up. Or remove usb and hold power+vol up.
Check that you are still decrypted.
Replace Fstab again with the 'fileencryption' flag removed one.
Now you can boot to system.
Edit: I managed to get TWRP source working, will test the decrypt fix soon.
---------- Post added at 08:44 PM ---------- Previous post was at 08:01 PM ----------
Pretoriano80 said:
I managed to build an Ubuntu based development environment, but using minimal manifest (8.1 branch) to build TWRP throws errors (i don't know if you have the same errors).
Here's the error log - > https://pastebin.com/C6jVg2eY
Click to expand...
Click to collapse
You need the full Omni source. Takes a while to sync
It's missing stuff from minimal that's needed.
After it's done syncing, you need to git clone https://github.com/omnirom/android_bootable_recovery to TWRPfolder/bootable/ and replace the recovery folder.
Same with https://github.com/omnirom/android_external_busybox/ to TWRPfolder/external/busybox (folder doesn't exist).
I'm not sure why it does this, the source looks fine when viewed in browser, but it doesn't sync everything...
ante0 said:
Well, it has to apply the update in stock recovery. It can't do it in TWRP.
Basically you:
Format Data in TWRP and replace fstab with one that has fileencryption flag removed.
Boot to system once and then back to TWRP, check that you are decrypted (file manager in TWRP to Internal SD or browse child folders in /data).
Run HWOTA8 and let it update through stock recovery.
When it's done updating and about to reboot back to system, hold vol down so it goes to fastboot mode.
Now flash TWRP and issue 'fastboot reboot', quickly remove usb cable and hold volume up. Or remove usb and hold power+vol up.
Check that you are still decrypted.
Replace Fstab again with the 'fileencryption' flag removed one.
Now you can boot to system.
Edit: I managed to get TWRP source working, will test the decrypt fix soon.
Click to expand...
Click to collapse
When I format data in twrp, replace fstab and boot to system once and then back to twrp to check encryption state in twrp filemanager, will /data not be empty then, so there's noting to check? Or am I missing something here?
lvbaal said:
When I format data in twrp, replace fstab and boot to system once and then back to twrp to check encryption state in twrp filemanager, will /data not be empty then, so there's noting to check? Or am I missing something here?
Click to expand...
Click to collapse
/data will not be empty. Unless you completely wipe it. But I think phone refuses to boot if you Wipe instead of Format Data
ante0 said:
/data will not be empty. Unless you completely wipe it. But I think phone refuses to boot if you Wipe instead of Format Data
Click to expand...
Click to collapse
I took my chances and did as proposed: only booting to system will not happen: it tries 2 times and the third time Huawei eRecovery comes up ¨Data partition was damaged seriously and you are recommended to format it to recover your phone¨ . It recommends Low level format data partition or shutdown. I chose Shutdown and booted to twrp once more to check /data. There's only lost+found and media/0 both empty. So /data turns out to be empty nevertheless. I did not completely wipe it; I did TWRP>Wipe>Format Data and typed ¨yes¨ to continue. Is this not what you meant by Format data in TWRP then?
lvbaal said:
I took my chances and did as proposed: only booting to system will not happen: it tries 2 times and the third time Huawei eRecovery comes up ¨Data partition was damaged seriously and you are recommended to format it to recover your phone¨ . It recommends Low level format data partition or shutdown. I chose Shutdown and booted to twrp once more to check /data. There's only lost+found and media/0 both empty. So /data turns out to be empty nevertheless. I did not completely wipe it; I did TWRP>Wipe>Format Data and typed ¨yes¨ to continue. Is this not what you meant by Format data in TWRP then?
Click to expand...
Click to collapse
Yes. That's where you Format Data.
Hmm.
Unless this twrp actually wipes rather than format.
Did you do update too now or just remove the flag in fstab and Format Data?
To get to Low level format, flash stock recovery OR the nocheck recovery from HWOTA8.
Hay,
today I've tried to root my OnePlus 7t Pro and installing TWRP my drive is killed.
At the first try of flashing the "twrp-3.3.1-4-guacamole" the system get completely wiped and the phone was fully wiped (and the installation doesn't work to)
Later I've managed to flash "twrp-3.3.1-74-guacamole-unified-Q" and that worked, but now I cant do anything because I only get "Failed to mount '/vendor' (invalid argument)" and "Failed to mount '/system' (invalid argument)".
And yes, I have tried to change the file system to ext2 and back to ext4 but this fails to.
Do have some one any idea I can "remount" the two partitions?
Sorry if this sounds completely stupid but I have searched for 4 hours on google and found something like 100 times the same solution but that doesn't work. :crying:
EDIT: I have try'ed "Repair File System" to, there i get a "/sbin/e2fsck -fp process endet with ERROR: 16" "Unable to repair System.".
Maybe because TWRP doesn't actually work on devices on launched with Android 10.
It literally says in the TWRP thead that mounting these partitions does not work.
You'll just have to wait.
Sent from my OnePlus7TPro using XDA Labs
Lossyx said:
Maybe because TWRP doesn't actually work on devices on launched with Android 10.
It literally says in the TWRP thead that mounting these partitions does not work.
You'll just have to wait.
Sent from my OnePlus7TPro using XDA Labs
Click to expand...
Click to collapse
Even if it doesn't mount drives?
Because, a.t.m. there is no android because it was wiped completely.
TazztheMonster said:
Even if it doesn't mount drives?
Because, a.t.m. there is no android because it was wiped completely.
Click to expand...
Click to collapse
You'll likely have to use MSM tool or fastboot ROM to flash your device to stock.
Sent from my OnePlus7TPro using XDA Labs
same problem here. cannot mount drives after non branded rom flashing through fastboot after trying to rollback from beta to stable channel.
TazztheMonster said:
Hay,
today I've tried to root my OnePlus 7t Pro and installing TWRP my drive is killed.
At the first try of flashing the "twrp-3.3.1-4-guacamole" the system get completely wiped and the phone was fully wiped (and the installation doesn't work to)
Later I've managed to flash "twrp-3.3.1-74-guacamole-unified-Q" and that worked, but now I cant do anything because I only get "Failed to mount '/vendor' (invalid argument)" and "Failed to mount '/system' (invalid argument)".
And yes, I have tried to change the file system to ext2 and back to ext4 but this fails to.
Do have some one any idea I can "remount" the two partitions?
Sorry if this sounds completely stupid but I have searched for 4 hours on google and found something like 100 times the same solution but that doesn't work. :crying:
EDIT: I have try'ed "Repair File System" to, there i get a "/sbin/e2fsck -fp process endet with ERROR: 16" "Unable to repair System.".
Click to expand...
Click to collapse
You know guacamole is oneplus 7pro not our 7tpro right?
Is for another device...
Secondly our twrp is not functioning bc of the super partition that is on our phones
Our phones shipped with Android 10 so they have to have a new twrp made for our devices to support this.
The 7pro shipped with Android 9.0 that is why twrp works on their device and not ours
Currently I would not flash twrp on our device until they have made one that works for us
Until then patch your boot img in magisk (Google search this if you don't know how) to obtain root.
Btw 7tpro is called hotdog
toolhas4degrees said:
You know guacamole is oneplus 7pro not our 7tpro right?
Is for another device...
Secondly our twrp is not functioning bc of the super partition that is on our phones
Our phones shipped with Android 10 so they have to have a new twrp made for our devices to support this.
The 7pro shipped with Android 9.0 that is why twrp works on their device and not ours
Currently I would not flash twrp on our device until they have made one that works for us
Until then patch your boot img in magisk (Google search this if you don't know how) to obtain root.
Btw 7tpro is called hotdog
Click to expand...
Click to collapse
Perfect
Now you’re talking!‘.
Sent from my OnePlus7TPro Global using XDA Labs
Have you solved? I have the same problem
TazztheMonster said:
Even if it doesn't mount drives?
Because, a.t.m. there is no android because it was wiped completely.
Click to expand...
Click to collapse
(OnePlus 7T Pro)
I unlocked bootloader, i installed ADB, I installed TWRP. But as I wanted to install Magisk i got an error. I ALREADY WIPED VERYTHING DUE TO A WRONG VIDEO
So now I can´t boot, because no OS. I also can´t install an OS, because System and Vendor can´t be mounted. I tried everything which were in those forums ( exFAT, exFAT 4, back to exFAT 2)
Pls help if this got solved anywhere. I don´t care about bootloader or root now. I just want to USE my device again with an OS
I beg you please help me
nikiwithstyle said:
(OnePlus 7T Pro)
I unlocked bootloader, i installed ADB, I installed TWRP. But as I wanted to install Magisk i got an error. I ALREADY WIPED VERYTHING DUE TO A WRONG VIDEO
So now I can´t boot, because no OS. I also can´t install an OS, because System and Vendor can´t be mounted. I tried everything which were in those forums ( exFAT, exFAT 4, back to exFAT 2)
Pls help if this got solved anywhere. I don´t care about bootloader or root now. I just want to USE my device again with an OS
I beg you please help me
Click to expand...
Click to collapse
Use MSMtool and stay on stock.
So I fixed the problem one day after. IF YOU GET THE MESSAGE NO OS INSTALLED ASWELL IGNORE IT! Trust me there. The Errormessage itself is a error. Because there is no real TWRP for the oneplus 7T pro. Just boot it it will work
So Ive never thought about or had anyone around me ever talk about android developers or enthusiasts or whatever it is... the past few years I ran into quite a few issues that ive needed root.. so I tried researching and trying to learn and well.. i should of maybe hopped on here before i did the actual attempt... SO heres my **** up!
I unlocked my bootloader... then followed a guide and I had tried flashing a img without flashing twrp and magisk and so now I figured out how to boot into recovery, twrp... and flashed magisk and then I tried installing no verity opt encrypt 6.1 and it states failed then i started moving around through twrp and tried mounting data and it will not even highlight the data checkbox and wont let me repair the data under the wipe command and wont let me change it to any of the extensions? no os found it says it wont let me format userdata says this.
fastboot: error; cannot generate image for userdata
please if you can help me out... any help would be greatly appreciated and would be lifesaving... thx
I am new to trying out this kind of stuff i believe i flashed possibly the wrong boot img! before I had flashed twrp and well i was stuck in fastboot.. but managed to get twrp and then flashed magisk and tried flashing no verity opt encryption but it will not flash I'm unable to mount the checkbox data in mount It wont even highlight the checkbox... i go to try to wipe some partitions and the only one it lets me wipe is metadata... I've tried format and It said failed to generate userdata partition and then i = tried fastboot erase userdata it worked tried erase/format cache it didn't work so any help at this would be greatly appreciated... thanks for your time
Re-flash phone's Stock ROM to get rid off of all modifications you applied so far.
so just download original stock rom to my computer into the file that holds adb and fastboot and then flash it and then reboot and it should work?
You shouldn't post duplicate threads.. I noticed you already had one the same day a few hours earlier for the same thing.. You might want to read the rules before posting to avoid any issues.
@Learnitright Hello, as mentioned above, please do not make duplicate threads with same topic. All replies from other users can be on this thread.
I have merged another thread by you into this one. Thanks.
I am sorry i wasnt sure if the first one went through or not I am stuck with a slow computer isnt very good im just trying to fix my phone.. If anyone could help?
You need stock-ROM and msm-tool, sadly metro version stock-ROM might not available for public right now. You should have used
Code:
fastboot boot twrp-n200.img
instead of flash recovery.
kdm6389 said:
You need stock-ROM and msm-tool, sadly metro version stock-ROM might not available for public right now. You should have used
Code:
fastboot boot twrp-n200.img
instead of flash recovery.
Click to expand...
Click to collapse
even if its just named recovery.img in the folder where i open up the command prompt ? sorry im so new to this
try msm-tool with TMO-Stock-ROM, maybe yout phone become TMO from Metro.
** UNOFFICIAL A-TEAM RELEASE**
*******Testing ONLY*******
**testing has only been done on GN2200 July patch device but should atleast boot into twrp on other sec patch on GN2200 devices***
***Let us know if not***
*****HEED THE WARNING OF IMPENDING APOCALYPSE, DOOM, BOOTLOOPS , BRIMSTONE AND FIRE, AND ALSO TWRP ******
***NOBODY IS RESPONSIBLE FOR WHAT YOU DO WITH THIS EXCEPT YOU***
***DO NOT BUILD AND FLASH THIS UNLESS YOU KNOW EXACTLY WHAT YOUR DOING***
****DONT DO ANYTHING I SAY, I CANT BE HELD RESPONSIBLE FOR WHAT I SAY OR DO*****
**THIS IS AN ** UNOFICIAL RELEASE ** SO DONT GO CRYING TO ANYONE THAT YOU MADE YOURSELF AN EXPENSIVE PAPERWEIGHT IF YOU USE ANYTHING IN THIS POST***
********* THE RESPNSIBILITY LIES SOLELY UPON YOU***
***FLASHING IN CURRENT STATE DOES NOT BOOT INTO SYSTEM****
****READ EVERYTHING BEFORE YOU DO ANYTHING******
******ONLY POSTING THIS FOR DEV PURPOSES*******
******Huge THANKS to PizzaG for this!!!******
***Thanks to Eduardo as well for his contributions, he may still be working on his own release***
Am posting this with a copy/paste i posted in telegram group..
We need people with the knowledge/skills and experience to help get this TWRP finished AND/OR work out the bugs.
GitHub - PizzaG/recovery_device_oneplus_OP515AL1
Contribute to PizzaG/recovery_device_oneplus_OP515AL1 development by creating an account on GitHub.
github.com
*this is not ready for release but the source is here for anyone who can build upon it*
touch is not working
you cant fastboot boot on this device so DO NOT flash this to your device without a backup of your stock/current boot image
issues we are having is no touch, can't mount /data, and so far cant boot into system with the recovery installed so if you want to use it youll need to flash this to boot, use it for whatever and then flash stock boot back, if your magisk patched youll need to flash the backup of that patched boot image you made before flashing this in order to get back into your system....... i have sort of found a slight work around for having to keep flashing the boot partitions until someone can get this to boot by placing my current boot image on an sdcard along with the twrp, flash the twrp to the active boot partition, boot into twrp, install image and install your backed up boot image to the current slot, then go back to advanced and install twrp to ramdisk and select and install the twrp image to the ramdisk, if your magisk patched you need to flash magisk zip right now, you can adb shell into twrp to pull a copy of this boot image if you want and i have flashed my "twrp-ramdisk installed boot image" on the Slot that my system is on and stock/backup boot image to inactive slot because its the only way to boot back to system for now without reflashing the stock(backed up) boot image back to the slot. and reboot into bootloader, change active and reboot and your back into your system.... when you need twrp you can set active to the other slot, it will bootloop once into bootloader and choose recovery to get back to twrp... when done reboot to bootloader and set active back to the other slot and reboot into system.............otg mouse works, adb works, mtp works, some work has been done on the touch but thats still not working yet, everything seems to be mounting except data............. big shout out to PizzaG for this
***this is a very round-about way to get a currently buggy twrp on the device but if you have a usb-c adapter and mouse you can navigate twrp....***
PizzaG doesnt have the device and has spent more time than anyone could possibly ask someone to spend on this for free... I dont have the skills required yet to really work on this. I have tested as much as possible and here it is for those who can build and work on it. i dont recommend releasing in its current form because im sure alot of people will be complaining and bricking their devices. if you can build it im sure you can work on it and should have the skills to atleast recover and have the sense to make backups first.......
Thanks again to everyone who has already donated the valuable time working on this for us and to everyone who will follow and build upon this!
You can find the telegram group for our device here:
You can find the A-Team in telegram
Also FYI in case you missed the post about our kernel source, it can be found here:
GitHub - OnePlusOSS/android_kernel_msm-5.4_oneplus_sm6375 at oneplus/sm6375_r_12.0.1_oneplus_nord_n20_5g
Contribute to OnePlusOSS/android_kernel_msm-5.4_oneplus_sm6375 development by creating an account on GitHub.
github.com
If anyone with experience building twrp and especially for OnePlus devices needs a tester or any files from the device hit me up on telegram @PsYk0n4uT2 and I will do my best to provide whatever you need and test builds along with providing logs.
heres a compiled boot image from the above tree as of 10/02/2022.
**remeber it DOES NOT boot to system, this is twrp only, not installed into recovery ramdisk yet. so BACKUP YOUR STOCK(current) boot image FIRST**** you will have to flash your stock(current) boot image back to boot back into your system. you can sort of get around this by above mentioned method BUT here it is for the GN2200 anyways. working on my July patched device and my May patched device so it should work for other GN2200 sec patches too...
***BACKUP BACKUP BACKUP*****
also cant change active slot from twrp, must reboot to bootloader to change active slot
Heres TWRP installed to ramdisk on a july patched boot image. does not boot to system but since it doesnt you should still be able to use this on any patch for testing purposes.....
You can backup your boot image and flash your current boot image to inactive slot and flash this to active slot by selecting recovery from bootloader after it loops once.... use twrp then go back to bootloader and change active and reboot to get back into your system.
**BACKUP YOUR CURRENT BOOT IMAGE****
***DOES NOT BOOT TO SYSTEM**
***YOU WILL NEED YOUR CURRENT BOOT IMAGE TO BOOT YOUR SYSTEM< YOU SHOULD ALREADY HAVE A BACKUP OF YOUR STOCK IMAGE IN THE CASE THAT YOU ARE MAGISK PATCHED ALREADY< KEEP A COPY OF BOTH IN CASE YOU DECIDE TO WIPE DATA< YOU WILL NOT BOOT BACK INTO YOUR SYSTEM WITH A MAGISK PATCHED BOOT IMAGE IF YOU WIPE DATA*******
if someone can get their system to boot after installing the TWRP from post 4 or their own build after personal edits please post here how you were able to achieve the install and maintain booting into system..
currently twrp indicates that path to /mnt could not be found and cant mount /data .. i think if someone could fix this maybe some progress could be made
ScarletWizard said:
I wonder if TWRP will work for devices with a serial number defeicy
Click to expand...
Click to collapse
halfway working on mine, just isnt finished yet, we need someone who knows alot more about this than i do. another dev is working on twrp but needs a device. the serial wont affect anything else other than the oneplus care app and getting the unlock token..... other than that u have full functionality.... the one posted above needs ALOT of work to finish. no touch yet but it could work for SOME things....
I know C/C++ at a decent level, however; I don't have much experience with low level stuff (especially dealing with bootloaders and other specific proprietary android kernel stuff). If there is anything that needs testing, I am down for it since this is just a secondary phone for me and I won't be too upset if it explodes.
I'm going to attempt this
[ SOLUTION ] [ MTK ] to Fix Touch not Working on TWRP / Philz Due to Kernel Disabled Touch.
In this tutorial, i'm going to show how i managed to patch kernel to enable touch in recovery TWRP / Philz. WARNING : This worked fo...
factopea.blogspot.com
It's written for mtk device but might have similar enough instructions to port for qcom kernel,
But I believe this is what is needed to get the TWRP touch going
Is the trwp.fstab using the right version? Both have different
Code:
/dev/block/bootdevice/by-name/userdata /data f2fs noatime,nosuid,nodev,discard,inlinecrypt,reserve_root=32768,resgid=1065,fsync_mode=nobarrier latemount,wait,resize,check,formattable,fileencryption=aes-256-xts:aes-256-cts:v2+inlinecrypt_optimized+wrappedkey_v0,keydirectory=/metadata/vold/metadata_encryption,metadata_encryption=aes-256-xts:wrappedkey_v0,quota,reservedsize=128M,checkpoint=fs
Try this instead in twrp.fstab
Code:
/data f2fs /dev/block/bootdevice/by-name/userdata flags=fileencryption=ice:aes-256-cts;wrappedkey;keydirectory=/metadata/vold/metadata_encryption
Techted89 said:
Is the trwp.fstab using the right version? Both have different
Code:
/dev/block/bootdevice/by-name/userdata /data f2fs noatime,nosuid,nodev,discard,inlinecrypt,reserve_root=32768,resgid=1065,fsync_mode=nobarrier latemount,wait,resize,check,formattable,fileencryption=aes-256-xts:aes-256-cts:v2+inlinecrypt_optimized+wrappedkey_v0,keydirectory=/metadata/vold/metadata_encryption,metadata_encryption=aes-256-xts:wrappedkey_v0,quota,reservedsize=128M,checkpoint=fs
Try this instead in twrp.fstab
Code:
/data f2fs /dev/block/bootdevice/by-name/userdata flags=fileencryption=ice:aes-256-cts;wrappedkey;keydirectory=/metadata/vold/metadata_encryption
Click to expand...
Click to collapse
i just unpacked the twrp image with AIK and made the suggested edits and repacked, reflashed, same...... another person is working on twrp and has gotten much of the fstab corrected in their build but their keeping their source closed til they get it ready for release and is still very far from being finished with it and doesnt have much time to work on it right now so we are just kinda stuck waiting on someone that knows what their doing to help get this going. the other person has touch working on theirs so i know its possible i just dont know how long it will be before we see a beta even
Techted89 said:
Is the trwp.fstab using the right version? Both have different
Code:
/dev/block/bootdevice/by-name/userdata /data f2fs noatime,nosuid,nodev,discard,inlinecrypt,reserve_root=32768,resgid=1065,fsync_mode=nobarrier latemount,wait,resize,check,formattable,fileencryption=aes-256-xts:aes-256-cts:v2+inlinecrypt_optimized+wrappedkey_v0,keydirectory=/metadata/vold/metadata_encryption,metadata_encryption=aes-256-xts:wrappedkey_v0,quota,reservedsize=128M,checkpoint=fs
Try this instead in twrp.fstab
Code:
/data f2fs /dev/block/bootdevice/by-name/userdata flags=fileencryption=ice:aes-256-cts;wrappedkey;keydirectory=/metadata/vold/metadata_encryption
Click to expand...
Click to collapse
also i see a recovery.fstab instead of twrp.fstab in /system/etc. is this what your referring to?
You need both from what iv read ,. TWRP.flags is a module that rewrites the stab at a certain point which may be the reason it's not compiling but I will post. Recovery.fstab is supposed to be a copy paste from the boot.img and gives the general mount partitions locations,. TWRP.fstab is mounted using the same partitions but different format/flag structure to be available to TWRP .
Techted89 said:
You need both from what iv read ,. TWRP.flags is a module that rewrites the stab at a certain point which may be the reason it's not compiling but I will post. Recovery.fstab is supposed to be a copy paste from the boot.img and gives the general mount partitions locations,. TWRP.fstab is mounted using the same partitions but different format/flag structure to be available to TWRP .
Click to expand...
Click to collapse
Interesting article above. Were you able to get that to work? I know it says MTK but seems like mechanism should be the same, or atleast I would assume anyways that the function would be very similar in the case of a flag. Was told you needed to use original kernel but then I couldn't get that to boot period. I'm out of my area of knowledge at this point but always willing to learn.
Also I tried messing around a little with the f stab and TWRP flags I was told that TWRP flags is pretty much the same as the twrp.fstab... also this build needs to have something added to the drivers I do believe that this is somehow related to USB touch it is a goodix gt9886 touch panel using the Samsung 9886 drivers. Maybe the init's need some help here as well.
I have the programming knowwledge that TWRP would require, but have not as of yet created one as my devices were typically readily complete before-hand. Once my device is back up, and running I am going to boot into Ubuntu and give it a go.
I need some excuse to have learned assembly x86, c, c++, Java, Python, and rust and have been eyeing learning scripting so it could be a fun side project assuming it is still incomplete as of the moment?
Is it normal for manufacturers to use components from other's in their builds? The kernel posted seemed to indicate at least a couple Samsung files included.
Well C is a guarantee possibly some C++ as well and definitely some sh scripting if you know rust and know how to attach it to C well enough that could add more possibilities I would imagine. The recovery is from my understanding in the boot image Android Image Kitchen would help you see it unmodified if that is the case.
I found a unofficial TWRP that flashes to the boot partition, and works pretty damn well, id have to say! I am not an experienced developer, I just like to flash around on my phone in my spare time.. Anyways here y'all go:
I am down while I got partitions backed up to the cloud.