i have h910 when trying to install gpu drivers by twrp i get a vendor error and i can't enable emount
Just use the Magisk module...
iTzFeRReTTi said:
Just use the Magisk module...
Click to expand...
Click to collapse
by magisk causes bugs and is not 100℅, google play starts from error and the system bugs in lineage 18
I'm using v0490.0 with Vulkan 1.1.128 without any issues with the module...
iTzFeRReTTi said:
I'm using v0490.0 with Vulkan 1.1.128 without any issues with the module...
Click to expand...
Click to collapse
Do you use this module on Crdroid or Lineage 18.1 ?
sajadzarepour said:
Do you use this module on Crdroid or Lineage 18.1 ?
Click to expand...
Click to collapse
Works on both.
iTzFeRReTTi said:
Works on both.
Click to expand...
Click to collapse
after you installed the module did you do any cleaning? have a clean gpu file if you used this for twrp?
Where is driver link for los18 ?
sajadzarepour said:
Where is driver link for los18 ?
Click to expand...
Click to collapse
v5.5 ([email protected]) - Google Drive
drive.google.com
rafrgt said:
i have h910 when trying to install gpu drivers by twrp i get a vendor error and i can't enable emount
Click to expand...
Click to collapse
if you cant mount you have to flash the boot partition again.
get the boot.img file from your rom, put it in phone, open magisk and go for patch boot file, select boot.img, it will creat a new file, like patched_boot.img, flash it in recovery. now /vendor error is fixed.
now, what is this driver? what does it do?
hamid_valad said:
if you cant mount you have to flash the boot partition again.
get the boot.img file from your rom, put it in phone, open magisk and go for patch boot file, select boot.img, it will creat a new file, like patched_boot.img, flash it in recovery. now /vendor error is fixed.
now, what is this driver? what does it do?
Click to expand...
Click to collapse
have you tested this? is gpu drivers, by magisk causes bugs in apps could you make a video to see if it works?
rafrgt said:
have you tested this? is gpu drivers, by magisk causes bugs in apps could you make a video to see if it works?
Click to expand...
Click to collapse
nope. i don't even know what this driver is!!!!
I just read that you have /vendor issue, and since i had the same issue (different reason) i thought i may tell you the work around.
hamid_valad said:
nope. i don't even know what this driver is!!!!
I just read that you have /vendor issue, and since i had the same issue (different reason) i thought i may tell you the work around.
Click to expand...
Click to collapse
I did here by magisk and error in my recovery I had to reinstall
Related
FIRST UNLOCK BOOTLOADER AND FLASH TWRP
2ND install " disable force encryption.zip after that . for video guide go here
and for file go here
3RD DO FACTORY RESET DONT DELETE SYSTEM AND VENDOR
4TH MOUNT SYSTEM AND FLASH ANY GSI IMAGE YOUR CHOICE TO SYSTEM IMAGE PARTIONDONT FLASH ZIP, EXTRACT .IMG FILE AND FLASH
FOR SEMI GSI YOU HAVE TO MOUNT VENDOR THEN FLASH 1,2,3 ZIP
FOR PROOF WATCH THIS VIDEO
Wow man! Someone "ACTUALLY" did it!
I'll try when my f1 arrives
the top corners curves and the margin being small is just killing me :/
But nice work dude
How did you manage to unlock so fast?
1emrys1 said:
How did you manage to unlock so fast?
Click to expand...
Click to collapse
Yeah, how
sankhauaa said:
FIRST UNLOCK BOOTLOADER AND FLASH TWRP
2ND install " disable force encryption.zip after that . for video guide go here
and for file go here
3RD DO FACTORY RESET DONT DELETE SYSTEM AND VENDOR
4TH MOUNT SYSTEM AND FLASH ANY GSI IMAGE YOUR CHOICE TO SYSTEM IMAGE PARTIONDONT FLASH ZIP, EXTRACT .IMG FILE AND FLASH
FOR SEMI GSI YOU HAVE TO MOUNT VENDOR THEN FLASH 1,2,3 ZIP
FOR PROOF WATCH THIS VIDEO
Click to expand...
Click to collapse
How's the experience using a GSI on this phone? What works and what doesn't? Camera usable?
ffh2303 said:
How's the experience using a GSI on this phone? What works and what doesn't? Camera usable?
Click to expand...
Click to collapse
Open camera is working fine.
Almost all working but all GSI have little bug and u have to fixed it manually
Jio volte not working in some gsi
1emrys1 said:
How did you manage to unlock so fast?
Click to expand...
Click to collapse
Ok lets unlock your device within a second
Dont update your phone before this process
First backup your some data like sms call history to mi cloud with sync on ,(see pic in attachment)
Now enable developer option
In this setting u have to check 4 option.dont forget 4 option
Check devoloper option
Check miui unlock(wait mi server read your device)
Check two types of usb debugging
Now download some photo from miui cloud that u just uploaded see sync on and find my device on
Now use mi unlock tool v2.2.406 or other versions u can try
Hope this time u can unlock .dont forget dont update your phone before unlock
Notch support and Jio Volte support for phh treble based ROMs
Can someone make a flashable zip to add notch support to phh treble based ROMs like how it is for mi 8 and can someone make flashable zip to add Jio Volte support for phh treble ROMs any help would be appreciated!
Have a nice day!
I've got mine unlocked fast because I am an old user of xiaomi and i've unlocked my old phone(also xiaomi phone).
Otherwise u've to wait for 720hrs.
Might clear out abit confusion.
sankhauaa said:
FIRST UNLOCK BOOTLOADER AND FLASH TWRP
2ND install " disable force encryption.zip after that . for video guide go here
and for file go here
3RD DO FACTORY RESET DONT DELETE SYSTEM AND VENDOR
4TH MOUNT SYSTEM AND FLASH ANY GSI IMAGE YOUR CHOICE TO SYSTEM IMAGE PARTIONDONT FLASH ZIP, EXTRACT .IMG FILE AND FLASH
FOR SEMI GSI YOU HAVE TO MOUNT VENDOR THEN FLASH 1,2,3 ZIP
FOR PROOF WATCH THIS VIDEO
Click to expand...
Click to collapse
do you flash A or B GSI?
thank you
abihakim said:
do you flash A or B GSI?
thank you
Click to expand...
Click to collapse
A gsi
It shows 57hours waiting time before unlock. I'm on miui version 9.6.18.0.
How can I unlock for sure?
sankhauaa said:
FIRST UNLOCK BOOTLOADER AND FLASH TWRP
2ND install " disable force encryption.zip after that . for video guide go here
and for file go here
3RD DO FACTORY RESET DONT DELETE SYSTEM AND VENDOR
4TH MOUNT SYSTEM AND FLASH ANY GSI IMAGE YOUR CHOICE TO SYSTEM IMAGE PARTIONDONT FLASH ZIP, EXTRACT .IMG FILE AND FLASH
FOR SEMI GSI YOU HAVE TO MOUNT VENDOR THEN FLASH 1,2,3 ZIP
FOR PROOF WATCH THIS VIDEO
Click to expand...
Click to collapse
Hi, I'm quite new here and while I have a general understanding of what you say here, I'm not sure I could follow those instructions without bricking my device by overlooking something or just basic newbie stupidity... Could you make a more detailed guide, please?
PocoSteve said:
Hi, I'm quite new here and while I have a general understanding of what you say here, I'm not sure I could follow those instructions without bricking my device by overlooking something or just basic newbie stupidity... Could you make a more detailed guide, please?
Click to expand...
Click to collapse
after unlock ur device flash twrp then post here i will help you
Pranay nagavolu said:
It shows 57hours waiting time before unlock. I'm on miui version 9.6.18.0.
How can I unlock for sure?
Click to expand...
Click to collapse
you r lucky then not 72 only 57
sankhauaa said:
you r lucky then not 72 only 57
Click to expand...
Click to collapse
Lol
Should we disable force encryption if we want to flash Magisk ?
Hi,
Any place where GSI ROMs are listed ?
That would also be a nice addition to XDA I think
Regards.
I'm experimenting with getting the cm 12.1 to work on my hd8 2017.
One of my college friend suggested to try replace part of the folders in the system partition with the one in the cm and today i've tryed and to my astonishment it reachd the cm 12.1 splash screen and from there i'm getting a very nice bootloop
I know this is probably the worst way of porting a rom ( seems to me so, im not an expert) but if some rom-porting expert can tell me what is wrong with the boot process even just for the sake of knowledge.
in the attachments a splash-screen image and a partial logcat (the logcat was capture when the tablet was "dirty" and still had FireOS data and cache)
I know @Rortiz2 was looking at doing the same thing.
Maybe you two can coordinate.
t0x1csh said:
i'm experimenting with getting the cm 12.1 to work on my hd8 2017.
One of my college friend suggested to try replace part of the folders in the system partition with the one in the cm and today i've tryed and to my astonishment it reachd the cm 12.1 splash screen and from there i'm getting a very nice bootloop
i know this is probably the worst way of porting a rom ( seems to me so, im not an expert) but if some rom-porting expert can tell me what is wrong with the boot process even just for the sake of knowledge.
In the attachments a splash-screen image and a partial logcat (the logcat was capture when the tablet was "dirty" and still had fireos data and cache)
Click to expand...
Click to collapse
oh my god!! What rom used as base!!??? What folders did you replaced? More info please! Also you need to wipe data and system before flash a ROM.
Send it to me please, I will take a look.
Rortiz2 said:
oh my god!! What rom used as base!!???
Send it to me please, I will take a look.
Click to expand...
Click to collapse
cm-12.1-20190616-UNOFFICIAL-i9105p from androidfilehost on top of 50.6.2.6 i dont have the image right now but i can make you one
my friend send me this https://forum.xda-developers.com/showthread.php?t=2545618 and i followed it step by step
t0x1cSH said:
cm-12.1-20190616-UNOFFICIAL-i9105p from androidfilehost on top of 50.6.2.6 i dont have the image right now but i can make you one
my friend send me this https://forum.xda-developers.com/showthread.php?t=2545618 and i followed it step by step
Click to expand...
Click to collapse
Dude you need to use a ROM from an mtk 64 bit device!
I suggest this: https://forum.xda-developers.com/elephone-p7000/development/rom-t3355842
Let me port it using that guide and I will send you a .zip for flash it using flashfire.
Rortiz2 said:
Dude you need to use a ROM from an mtk 64 bit device!
I suggest this: https://forum.xda-developers.com/elephone-p7000/development/rom-t3355842
Let me port it using that guide and I will send you a .zip for flash it using flashfire.
Click to expand...
Click to collapse
well what i changed is mostly java so i dont think the arch is that important plus mostly of the libraries on the fire hd8 are 32 bit
t0x1cSH said:
well what i changed is mostly java so i dont think the arch is that important plus mostly of the libraries on the fire hd8 are 32 bit
Click to expand...
Click to collapse
Libraries on hd8 2017 are 64 bit too (lib64 folder). And yes, it's very important. You can't port a ROM from an Snapdragon device to an MTK one lol.
I'm surprised that the bootanimation started.
Did you used flashfire for flash it?
Rortiz2 said:
Libraries on hd8 2017 are 64 bit too (lib64 folder). And yes, it's very important. You can't port a ROM from an Snapdragon device to an MTK one lol.
I'm surprised that the bootanimation started.
Did you used flashfire for flash it?
Click to expand...
Click to collapse
nope i've patched the system image from the ota
but excluding the libraries (that i didn't touch) i know that you can't port a rom if the apps are odex at least until you deodex all of them becouse the odex contains the compiled code specific to the processor, correct me if i'm wrong
t0x1cSH said:
nope i've patched the system image from the ota
Click to expand...
Click to collapse
And flashed it with "hacked fastboot" no?
Rortiz2 said:
And flashed it with "hacked fastboot" no?
Click to expand...
Click to collapse
yep
t0x1cSH said:
yep
Click to expand...
Click to collapse
So you mounted stock system.img, replaced that folders, unmounted it and flashed it tought fastboot? Very interesting. IDK why bootanimation started if you're using stock boot.img that doesn't starts the bootanimation service from init.rc.
Rortiz2 said:
So you mounted stock system.img, replaced that folders, unmounted it and flashed it tought fastboot? Very interesting. IDK why bootanimation started if you're using stock boot.img that doesn't starts the bootanimation service from init.rc.
Click to expand...
Click to collapse
should i try with the link you send me or is a waste of time? the process is quite laborious
t0x1cSH said:
should i try with the link you send me or is a waste of time? the process is quite laborious
Click to expand...
Click to collapse
You can try if you want. I'm porting it too for see if it works, the problem is that I will make a zip so you will need to use flashfire to flash it..
PS: your hacked fastboot allows to flash boot.img's that are not from amazon?
Rortiz2 said:
You can try if you want. I'm porting it too for see if it works, the problem is that I will make a zip so you will need to use flashfire to flash it..
PS: your hacked fastboot allows to flash boot.img's that are not from amazon?
Click to expand...
Click to collapse
no
t0x1cSH said:
no
Click to expand...
Click to collapse
Ok.
is this a little step forward? @Rortiz2
t0x1cSH said:
is this a little step forward? @Rortiz2
Click to expand...
Click to collapse
Yep all it's ok except one rror:
Code:
load_driver(/system/lib/egl/libGLES_mali.so): dlopen failed: cannot locate symbol "_ZN12DpBlitStream14setPQParameterERK9DpPqParam" referenced by "libgpu_aux.so"...
You need to create a shim for that and since is ported, you can't
What ROM used this time?
Rortiz2 said:
Yep all it's ok except one rror:
Code:
load_driver(/system/lib/egl/libGLES_mali.so): dlopen failed: cannot locate symbol "_ZN12DpBlitStream14setPQParameterERK9DpPqParam" referenced by "libgpu_aux.so"...
You need to create a shim for that and since is ported, you can't
What ROM used this time?
Click to expand...
Click to collapse
well last night i switched to the cynogenmod 12.1 port for the hd7 (i know 32bit) this time i copied also part of the 32bit libraries (when an import error on a library occurred i replaced the library with the hd7 one ) slowly advancing in the android boot before a bootloop
t0x1cSH said:
well last night i switched to the cynogenmod 12.1 port for the hd7 (i know 32bit) this time i copied also part of the 32bit libraries (when an import error on a library occurred i replaced the library with the hd7 one ) slowly advancing in the android boot before a bootloop
Click to expand...
Click to collapse
Glad to see that is working
Try replacing libgpu_aux.so
Regards!
Rortiz2 said:
Glad to see that is working
Try replacing libgpu_aux.so
Regards!
Click to expand...
Click to collapse
actually i did not replace libGLES_mali.so(still from hd8 rom) but i replaced libgpu_aux and i get the same error
[Global] Mi A2 Lite V11.0.10.0.QDLMIXM rolling out!
Wow. That's gotta be some kind of record for Xiaomi
Mine is only 13M though. Must be a tiny update.
Wow! First time ever that this Android One device is actually up to date security wise.
Yes, from July update only 13MB.
Maybe it was there before, but after updating I noticed a native screen recorder icon.
Updated: It is not native. I have a screen recorder app installed.
Direct share not yet available.
penahj said:
Maybe it was there before, but after updating I notice a native screen recorder icon
Click to expand...
Click to collapse
strange i dont have this one and never had screen recording option
Antho02 said:
strange i dont have this one and never had screen recording option
Click to expand...
Click to collapse
You are right. It's not a native app. I have a screen recordering app installed. Sorry for the wrong news.
Does someone know how to install an OTA Update without using the System Update App? It always says Installation Problem. Installation failed.
I'm rooted with magisk, that's the reason i guess.
I found the 13mb Update as a zip file, but it's not flashable via twrp... Any Suggestions?
Best regards
Alex
Alibabara said:
Does someone know how to install an OTA Update without using the System Update App? It always says Installation Problem. Installation failed.
I'm rooted with magisk, that's the reason i guess.
I found the 13mb Update as a zip file, but it's not flashable via twrp... Any Suggestions?
Best regards
Alex
Click to expand...
Click to collapse
+1 I am also looking for this
Alibabara said:
Does someone know how to install an OTA Update without using the System Update App? It always says Installation Problem. Installation failed.
I'm rooted with magisk, that's the reason i guess.
I found the 13mb Update as a zip file, but it's not flashable via twrp... Any Suggestions?
Best regards
Alex
Click to expand...
Click to collapse
with twrp/magisk i always do
1-xiaomiflash rom (keep user files)
2-boot and install twrp
3-boot and install magisk
no problem this way
Antho02 said:
with twrp/magisk i always do
1-xiaomiflash rom (keep user files)
2-boot and install twrp
3-boot and install magisk
no problem this way
Click to expand...
Click to collapse
So you Flash the whole Rom (~1.2gb) and not just the Update?
I would like to find a way to Flash just the Update since your method is taking too long for me...
Best regards
Alex
If you only have Magisk, the standard process should work for you.
https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-proper-support-ota-t3836952
If it's not working and you have somehow modified some other partition, it will be written to the logcat.
adb logcat | grep update_engine
My Problem is, even with magisk 'uninstalled' the Update App from xiaomi still says 'Installation failed: Installation Problem'
That even happens with totally Stock rom, no root and no twrp.
I dont know why. But is there any other way to Update manually without flashing the whole Big Rom file? Just the Update file...
There must be a reason why there is an update file in zip Format which is 13mb Big.
Best regards
Alex
Alibabara said:
My Problem is, even with magisk 'uninstalled' the Update App from xiaomi still says 'Installation failed: Installation Problem'
That even happens with totally Stock rom, no root and no twrp.
I dont know why. But is there any other way to Update manually without flashing the whole Big Rom file? Just the Update file...
There must be a reason why there is an update file in zip Format which is 13mb Big.
Best regards
Alex
Click to expand...
Click to collapse
Alex, You don't have to flash the whole big rom file, but you do have to download it though. You can get it from here: https://mirom.ezbox.idv.tw/en/phone/daisy/roms-global-stable/
You then have to extract the files that you need with payload_dumper which you get from here:
https://androidfilehost.com/?fid=818070582850510260
NB that is the Windows 64bit version so make sure that is the OS your pc is using.
You then have to find which partition it is that is causing the problem for which you have to use a1291762's advice:
Code:
adb logcat | grep update_engine
and read very carefully through the results because the offending entry will be difficult to spot amongst the dozens of others.
You then flash the partition mentioned in the logcat. For example if 'system' is mentioned in the logcat as having an incorrect hash (that is always the reason for the failures) you would have to extract 'system.img' with payload_dumper and run
Code:
fastboot flash system system.img
Then try the update again. If it works you will also probably have to reinstall Magisk from scratch again as flashing system will probably remove it.
Yes it is complicated - far too complicated, but the simple measure you call for - just flash an update file - has, to the best of my knowledge never been possible, so there must be some reason why that is so, but I don't know what it is.
Incidentally, the reason I am able to respond to this question is that I had a torrid time yesterday trying to update my A2 lite on which I had not one, but 3 errors. aboot hash incorrect, system hash incorrect, and before any of that the normal Magisk uninstall told me it had no images to restore and so had to be uninstalled completely. It took me hours and it wasn't that much fun.
Alibabara said:
There must be a reason why there is an update file in zip Format which is 13mb Big.
Click to expand...
Click to collapse
The update is only 13M because it contains only changes. But for that to work, your partitions must be unmodified.
The larger update zip has complete partitions so it can work even if you have changes. You may be able to do the recovery update method with that file...
The even larger fastboot image has every partition.
thanks everyone for the help!
I did it as you said viking777 and it worked.
It's sad, that for an 13mb update this procedure is necessary, but thats how it is..
So thanks again everyone for the help
Antho02 said:
with twrp/magisk i always do
1-xiaomiflash rom (keep user files)
2-boot and install twrp
3-boot and install magisk
no problem this way
Click to expand...
Click to collapse
Can I do this with out installing TWRP as I haven't installed it already.
Aadil Gillani said:
Can I do this with out installing TWRP as I haven't installed it already.
Click to expand...
Click to collapse
sure, even more quick if u dont need twrp
flash last rom with xiaomi flash (save user data selected)
then boot patched.img and install magisk, less than 10 mins and no need to worries about uninstall magisk or any mod before
Antho02 said:
sure, even more quick if u dont need twrp
flash last rom with xiaomi flash (save user data selected)
then boot patched.img and install magisk, less than 10 mins and no need to worries about uninstall magisk or any mod before
Click to expand...
Click to collapse
I have some questions it would be a be a pleasure if you could answer.
Q1 will the modules remain or not ?
Q2 how to make make patched boot img I mean should I make my self using Magisk Manager app
Q3 Also which TWRP do you use and if it has any problems
Q4 should I use zip file or tgz for mi flash
Hello everyone.
If you want to have a recovery with the ability to backup/restore, this instruction is for you.
Here are recovery, while they do not know how to encryption of data section (I hope we will have such ones sometime).Yes, recovery already patched by magisk 25.2
Download the patch, copy it to the SD card (if you have it) or to a USB flash drive, for firmware by otg.
We set the recovery in fastboot mode with the command:
fastboot flash boot (recovery name).img
We load into the recovery, flash the patch, and make FORMAT DATA.
Attention!!!This will delete all your settings and installed programs, including deleting everything from the internal memory.
After that, we boot into the system, configure and "rejoice", now the recovery will see data and, accordingly, internal memory.
And yes, if you have a security thing, this procedure disables the encryption of your data
COMPLETELY, THAT IS, COMPLETELY.
Oh, I forgot, although I think it's clear by the name of the recovery, they (recovery) are designed for firmware on Android 12.
Download files:
RECOVERY
Guys, one jamb got out here, my system has been transferred to RW, and I checked the script on such a system. As it turned out, the script does not work on the stock system. So, in order for it to work normally, you need to first transfer the system to RW
Any chance to explain step by step?
reosm said:
Any chance to explain step by step?
Click to expand...
Click to collapse
What exactly?
In the post everything is written as to put.
There are 2 img in the recovery file, which one will be loaded before or after
reosm said:
There are 2 img in the recovery file, which one will be loaded before or after
Click to expand...
Click to collapse
one is TWRP recovery and the other is Orange Fox recovery, choose which one you want to use, just flash one of them.
Hey does twrp/orangefox actually work on this phone. I've heard that those are currently under development. And does flashing these .img require wipe data or can they work with sd card or OTG?
Soma Das said:
Hey does twrp/orangefox actually work on this phone. I've heard that those are currently under development. And does flashing these .img require wipe data or can they work with sd card or OTG?
Click to expand...
Click to collapse
Recovery can work with both sd and otg. While they cannot decrypt the data, but if you transfer the system to RW, and flash the patch to disable encryption in the system, then everyone will see the recovery.
Who has a system in RO, you can use these, checked, it also works
[A/B][A-ONLY][SCRIPT][READ-ONLY][EROFS][ANDROID 10+] Universal Disable Force Encryption for RO and RW "NEO STABLE"
Disable Force Encryption NEO Do you all know what DFE is? no? Anyway. Basically, your device has an encrypted data section "/data" by default. Let's look at the advantages of google's solution that we will lose after disabling encryption: -...
forum.xda-developers.com
arraki said:
Recovery can work with both sd and otg. While they cannot decrypt the data, but if you transfer the system to RW, and flash the patch to disable encryption in the system, then everyone will see the recovery.
Click to expand...
Click to collapse
Can it backup anything such as boot.img, vendor etc?
Soma Das said:
Can it backup anything such as boot.img, vendor etc?
Click to expand...
Click to collapse
Probably you can, but why. A backup of the datа section is enough for normal recovery. Of course, you can also make a backup of the super section if you changed something in it.
arraki said:
Probably you can, but why. A backup of the datа section is enough for normal recovery. Of course, you can also make a backup of the super section if you changed something in it.
Click to expand...
Click to collapse
Do I need to flash disable dm Verity?
Soma Das said:
Do I need to flash disable dm Verity?
Click to expand...
Click to collapse
In the first post, everything is written.
does it work for Mediatek cpu install on the Note 11 pro plus 5g?
Christ_soyo said:
does it work for Mediatek cpu install on the Note 11 pro plus 5g?
Click to expand...
Click to collapse
MediaTek chip on is Redmi note 11 pro. It wilont work and you will get soft brick.
Christ_soyo said:
does it work for Mediatek cpu install on the Note 11 pro plus 5g?
Click to expand...
Click to collapse
What exactly works?
Do we need to unlock the bootloader firtst before we flash the recovery, right?
derjango said:
Do we need to unlock the bootloader firtst before we flash the recovery, right?
Click to expand...
Click to collapse
Of course
After using this patch my device doesn't know how to be case sensitive, which makes some apps have weird errors with read and write functions
nimade2333 said:
After using this patch my device doesn't know how to be case sensitive, which makes some apps have weird errors with read and write functions
Click to expand...
Click to collapse
This is clearly not because of the patch, I have put it on for a long time, and there are no problems. Yes, and he only disables encryption in the system, how can he influence this.
Hello, so I build twrp for my device, SM-A032F, now TWRP is running nice and good but, you cant format /system, /vendor, etc...
Only /data.
Now the problem is that... how am I gonna install a gsi when you cant wipe nor install anything to /system ??
So, I want help from you guys to fix this for me, if you do so, I will credit your XDA username on the TWRP splash screen
The AIK files are here
update: i'm good now
Have you tried flashing gsi through your twrp build ?
tinurad said:
Have you tried flashing gsi through your twrp build ?
Click to expand...
Click to collapse
No not yet, /system is still r/o even tho i mount it
I've been planning of making a CustomAP and just stop with twrp
Idk
XanderXDA said:
update: i'm good now
Click to expand...
Click to collapse
update: nope, I need help
XanderXDA said:
No not yet, /system is still r/o even tho i mount it
I've been planning of making a CustomAP and just stop with twrp
Idk
Click to expand...
Click to collapse
It's better. I think twrp will be useful to disable dm verity. If you can please, try with dot os (https://www.droidontime.com/devices/a64). Can I contact you through telegram ?
tinurad said:
It's better. I think twrp will be useful to disable dm verity. If you can please, try with dot os (https://www.droidontime.com/devices/a64). Can I contact you through telegram ?
Click to expand...
Click to collapse
I created a matrix space if you wanna join
Matrix - Decentralised and secure communication
You're invited to talk on Matrix. If you don't already have a client this link will help you pick one, and join the conversation. If you already have one, this link will help you join the conversation
matrix.to
Never heard of DotOS before, okay, ill try