Database Info

[SOLVED] hosts file restored at boot

Hello,
I rooted my device and installed AdAway,
Everytime I reboot I lose the blocking functionality.
How do I fix that?
Thanks
EDIT: https://forum.xda-developers.com/mate-9/help/ro-rooted-mate9-t3564231

bel3atar said:
Hello,
I rooted my device and installed AdAway,
Everytime I reboot I lose the blocking functionality.
How do I fix that?
Thanks
EDIT: https://forum.xda-developers.com/mate-9/help/ro-rooted-mate9-t3564231
Click to expand...
Click to collapse
If you used PHH to root, open the zip, open config.txt in a text editor, change "verity" to "noverity". Save and flash again.
You might need to flash back your stock boot image before flashing.
Edit: That link you posted there is full of misinformation.
Keeping system RO is best. It's not read-only/read-write that's causing it to roll back hosts.

I did that, but the flash fails with error 1.
I can't even install the original superuser-r310-beta.zip

bel3atar said:
I did that, but the flash fails with error 1.
I can't even install the original superuser-r310-beta.zip
Click to expand...
Click to collapse
Did you restore your stock boot image first?
Post your full build if you don't have it.
MHA/LON-LxxCxxxBxxx

ante0 said:
did you restore your stock boot image first?
Post your full build if you don't have it.
Mha/lon-lxxcxxxbxxx
Click to expand...
Click to collapse
mha-l29c432b182

bel3atar said:
mha-l29c432b182
Click to expand...
Click to collapse
https://mega.nz/#!VhlkmQbJ!sgq55_e6cf78VwxmKvUHD7f23aJnnWUwdOehft2Lpdk
Flash In TWRP to Boot partition, then flash your superuser zip with "noverity" in config.txt

ante0 said:
https://mega.nz/#!VhlkmQbJ!sgq55_e6cf78VwxmKvUHD7f23aJnnWUwdOehft2Lpdk
Flash In TWRP to Boot partition, then flash your superuser zip with "noverity" in config.txt
Click to expand...
Click to collapse
Solved, thank you =)
One more question: Will I still get OTA updates or will I have to apply them manually?

bel3atar said:
Solved, thank you =)
One more question: Will I still get OTA updates or will I have to apply them manually?
Click to expand...
Click to collapse
If you don't modify anything in /system, /product or /vendor you should still get OTA.
For example: installing Busybox modifies /system. Viper4Android modifies /vendor and /system.
If you need Busybox you should consider switching to Magiskv12. Its busybox is systemless (Doesn't modify anything).
And with Magisk you can use Android Pay and PokemonGO (and other apps that use SafetyNet).
MagiskHide is a little buggy on Mate 9, and other Huawei devices that use Nougat. If you enable it, fingerprint and pin will break after you reboot. If you just enable, run Android Pay, and disable after you will be fine.

Working ROOT for Oreo SM-J701F

For all Samsung Galaxy J701F users - Test Root with bypass defex​
With the last TW firmwares Samsung released A new security called [Defex].
And this protection prevent any process to run as root if it was not in the whitelist that provided in the kernel source code:
Code:
/system/bin/run-as
/init
/sbin/
/system/bin/
/system/xbin/
/system/vendor/bin/
/vendor/bin/
/tmp/update_binary
So if any app wants to run an elf executable in [e.x "/data/local/tmp"] like [Titanium Backup] of [ES File Explorer] the elf executing process will returns with Killed.
The first release of this protection was in Galaxy A8 2018 (SM-A530F) Android 8.0.0
and then released in Galaxy Note 9 (SM-N960F) 8.1.0
And all of these protections was defeated by some hex patching.
Now it is the time for SM-J701F:
Samsung released the source code of J701F today so i downloaded it and get a new patch to defeat the security

Magisk for deflex
Yes it is working on oreo rom but twrp is not mounting internal storage while using oreo rom on j7 nxt but twrp is working with naugat roms perfectly

Suraj199 said:
Yes it is working on oreo rom but twrp is not mounting internal storage while using oreo rom on j7 nxt but twrp is working with naugat roms perfectly
Click to expand...
Click to collapse
Did you try a factory reset and did you try the Root or what ?

defexer said:
Did you try a factory reset and did you try the Root or what ?
Click to expand...
Click to collapse
now my device is rooted its working
when i format through twrp it mount internal memory but after reboot again it unmount internal memory
thank you

avishekthapamagar said:
now my device is rooted its working
when i format through twrp it mount internal memory but after reboot again it unmount internal memory
thank you
Click to expand...
Click to collapse
Thanks for confirmation

Yes working successfully Root 8.1 Rom Thankyou Very much No Bugs

The magisk manager doesn't show any modules available for download but for root it works fine.
Thanks a bunch for fixing root. I didn't upgrade until this was available!

Hey ! do working successfully ? my phone no sim card error then magisk 17.1 17.2 or 16.4 install from TWRP

File removed
Hi defexer, You shared the twrp recovery file has removed from the link. I need the recovery because I have updated my j7 nxt to android version 8.1 and need to root the mobile. please help.

This work in j5 prime and j7 prime?

gabrielunm said:
This work in j5 prime and j7 prime?
Click to expand...
Click to collapse
Not sure. But take a backup and try Magisk/SuperSU from here: https://forum.xda-developers.com/an.../test-disable-defex-security-samsung-t3851487
Don't forget to confirm in that thread if it works. :good:

The link you provided isn't working. It must have been deleted due to some violations.

DJBhardwaj said:
Not sure. But take a backup and try Magisk/SuperSU from here: https://forum.xda-developers.com/an.../test-disable-defex-security-samsung-t3851487
Don't forget to confirm in that thread if it works. :good:
Click to expand...
Click to collapse
teraworld said:
The link you provided isn't working. It must have been deleted due to some violations.
Click to expand...
Click to collapse
Its back up

I recently updated my J7 Core to Oreo and after that, my oem option is gone and download mode displays RMM State: Prenormal. It hasnt been rooted before and whenever I install a font or themes, nothing shows up. What should I do?

kindly share your twrp?
shahidrok said:
Yes working successfully Root 8.1 Rom Thankyou Very much No Bugs
Click to expand...
Click to collapse
ive updated mine and my previous twrp is not working

Need help sir .. after launch official update from samsung to upgrade from nougat to oreo , my touchscreen not working at all .. only back and menu softkey still working . I followed many tutorial from many threads but still cant fix my j7 core / nxt touchscreen . now my j7 core / nxt is in oreo 8.1.0 , samsung experience version version 9.5 , build number M1AJQ.J701FDDU6BRI1
i can still using it with usb otg mouse to control ...
realy realy need help sir .. can you and anyone here help me please .. need solution

https://drive.google.com/open?id=1hgmUNrS4UdQjQt-sg5wKVEzNze_PWNxU
Magisk has been updated a couple times since the missing file was first uploaded so perhaps this isn't necessary anymore.

PantsDownJedi said:
https://drive.google.com/open?id=1hgmUNrS4UdQjQt-sg5wKVEzNze_PWNxU
Magisk has been updated a couple times since the missing file was first uploaded so perhaps this isn't necessary anymore.
Click to expand...
Click to collapse
i tried rooting my fone and it booted successfully.. but after few moments the antivirus kept on prompting to reboot the fone

jam24ph said:
i tried rooting my fone and it booted successfully.. but after few moments the antivirus kept on prompting to reboot the fone
Click to expand...
Click to collapse
I don't know if you have 3rd party antivirus or not, but if so you'll want to whitelist what its complaining about if you can, otherwise uninstall or freeze the antivirus.
You also want to freeze down Security Log Agent, possibly Device Security, and also Knox related apps are important. There's lots of apps to freeze things down but I've used Titanium Backup for so long that I haven't payed attention to other ones and don't know what they're names are. It can be done at the command line as well. Search for what works and is free, because that feature I think isn't free in non paid version of Titanium backup.
---------- Post added at 03:55 PM ---------- Previous post was at 03:51 PM ----------
Also, if you've gotten errors at TWRP not being able to mount /data you might want to install the Magisk apk separately and then update the Magisk app from the running phone environment assuming it lets you.

PantsDownJedi said:
https://drive.google.com/open?id=1hgmUNrS4UdQjQt-sg5wKVEzNze_PWNxU
Magisk has been updated a couple times since the missing file was first uploaded so perhaps this isn't necessary anymore.
Click to expand...
Click to collapse
PantsDownJedi said:
I don't know if you have 3rd party antivirus or not, but if so you'll want to whitelist what its complaining about if you can, otherwise uninstall or freeze the antivirus.
You also want to freeze down Security Log Agent, possibly Device Security, and also Knox related apps are important. There's lots of apps to freeze things down but I've used Titanium Backup for so long that I haven't payed attention to other ones and don't know what they're names are. It can be done at the command line as well. Search for what works and is free, because that feature I think isn't free in non paid version of Titanium backup.
---------- Post added at 03:55 PM ---------- Previous post was at 03:51 PM ----------
Also, if you've gotten errors at TWRP not being able to mount /data you might want to install the Magisk apk separately and then update the Magisk app from the running phone environment assuming it lets you.
Click to expand...
Click to collapse
what im referring to is the device security, after the succesfull bootup from flashing magisk..

Does AdAway works in OOS 9.5.5?

Hi, first of all, sorry for my bad english.
I just updated my 7Pro and rooted it, and installed the last AdAway release from XDA. The problem is, they didn't block any of the ads from Chrome or any other app like 9gag.
Has anyone tried to use any adblocker for this version of OOS?
Thanks!

yes here is a magisk module of the app i made so if you don't like it just uninstall module
download
u need to make sure you force close chrome and reboot after you updated adaway

Bradl79 said:
yes here is a magisk module of the app i made so if you don't like it just uninstall module
download
u need to make sure you force close chrome and reboot after you updated adaway
Click to expand...
Click to collapse
Thanks for the quick replay, but I finally found a solution. I had to enable the "Systemless host" in Magisk options.
Thanks for you help anyway

Bradl79 said:
yes here is a magisk module of the app i made so if you don't like it just uninstall module
download
u need to make sure you force close chrome and reboot after you updated adaway
Click to expand...
Click to collapse
Dang, you have a Magisk module for everything. You should start a thread with them all listed. I'm sure people would appreciate it.

Garapablo said:
Thanks for the quick replay, but I finally found a solution. I had to enable the "Systemless host" in Magisk options.
Thanks for you help anyway
Click to expand...
Click to collapse
U helped me too, BC I forgot to enable systemless host in Magisk, thank you lol
---------- Post added at 10:45 PM ---------- Previous post was at 10:44 PM ----------
bp328i said:
Dang, you have a Magisk module for everything. You should start a thread with them all listed. I'm sure people would appreciate it.
Click to expand...
Click to collapse
Lol I do, I make one for almost all the apps I use the most
Here is a link if u want to check it out
My modules

I rooted OnePlus 7 Pro and wanted to make OTA update. But as a newbie I didn't turn off fingerprint lock before reboot. OP 7 Pro just froze after reboot on PIN screen and turned off to stock recovery. I could only make a hard reset. After that my OP 7 Pro turned on. I make one more time root process - fastboot boot twrp.img > in TWRP Install Recovery Ramdisk from twrp.img > Flash Magisk.zip. But now Adaway doesn't work and I tried everything - granted root access, permission to write in memory, in adaway systemless option turn on same in Magisk. Can you please help me? Uninstall and install adaway didn't help me. Everything looks good but advertises are still display.

Is root available on EMUI9. 1?

Hi all,
I have a Huawei Mate 9 (MHA-L09C432) with EMUI 9.1 on it and an unlocked booloader with Magisk installed.
Because I want to modify root settings I would like to have full root access...
Is there a method now to get full root access with EMUI 9.1?
Thank you for your answers in advance!

htcdesire-hd said:
Hi all,
I have a Huawei Mate 9 (MHA-L09C432) with EMUI 9.1 on it and an unlocked booloader with Magisk installed.
Because I want to modify root settings I would like to have full root access...
Is there a method now to get full root access with EMUI 9.1?
Thank you for your answers in advance!
Click to expand...
Click to collapse
You have Magisk and that's the root. 'Classic/full root' is no more possible because of EROFS. Only systemless root functionality provided by Magisk

zgfg said:
You have Magisk and that's the root. 'Classic/full root' is no more possible because of EROFS. Only systemless root functionality provided by Magisk
Click to expand...
Click to collapse
Ok thats bad, hoped that there is a solution now...
Is that EMUI related or will no future Android phone have "real" root?
But a SW downgrade would bring back real root?

htcdesire-hd said:
Ok thats bad, hoped that there is a solution now...
Is that EMUI related or will no future Android phone have "real" root?
But a SW downgrade would bring back real root?
Click to expand...
Click to collapse
EROFS means read-only file system, developed by Huawei, used in EMUI 9.1 and 10.
Google is pushing that system must not be changed, and it is similarly enforced in other phones with Android 10.
Read discussions in Magisk and Magisk Canary threads on XDA, even better topjohnwu's (developer of Magisk) blog on Reddit, to understand in which direction (systemless) it goes and why.
By HiSuite you should be able to downgrade from EMUI 9.1 to 9.0 (prior to EROFS)

zgfg said:
EROFS means read-only file system, developed by Huawei, used in EMUI 9.1 and 10.
Google is pushing that system must not be changed, and it is similarly enforced in other phones with Android 10.
Read discussions in Magisk and Magisk Canary threads on XDA, even better topjohnwu's (developer of Magisk) blog on Reddit, to understand in which direction (systemless) it goes and why.
By HiSuite you should be able to downgrade from EMUI 9.1 to 9.0 (prior to EROFS)
Click to expand...
Click to collapse
Ok thanks for the explanation. Doesn't sound good for me... But maybe there will be a solution like reformatting in future I hope to get "real" root!
Thanks for the tip, I will do so.
Good I will do that!

htcdesire-hd said:
Ok thanks for the explanation. Doesn't sound good for me... But maybe there will be a solution like reformatting in future I hope to get "real" root!
Thanks for the tip, I will do so.
Good I will do that!
Click to expand...
Click to collapse
It's unlikely that you'd be able to change the partition types back to ext4 - one of the other things to note about EROFS is that at least some of the contents are compressed, and as a result the system partition is smaller than it was with ext4. It's likely the same is true of all of the other partitions though I haven't checked. But in any case, there likely isn't enough physical space to store a repacked EMUI 9.1 image set in the new partitions.

irony_delerium said:
It's unlikely that you'd be able to change the partition types back to ext4 - one of the other things to note about EROFS is that at least some of the contents are compressed, and as a result the system partition is smaller than it was with ext4. It's likely the same is true of all of the other partitions though I haven't checked. But in any case, there likely isn't enough physical space to store a repacked EMUI 9.1 image set in the new partitions.
Click to expand...
Click to collapse
Ok I understand...
I saw that you can unpack the EROFS partition in a virtual environment, remove or modify system files and repack it...
But that's to complicated for my purpose...

irony_delerium said:
It's unlikely that you'd be able to change the partition types back to ext4 - one of the other things to note about EROFS is that at least some of the contents are compressed, and as a result the system partition is smaller than it was with ext4. It's likely the same is true of all of the other partitions though I haven't checked. But in any case, there likely isn't enough physical space to store a repacked EMUI 9.1 image set in the new partitions.
Click to expand...
Click to collapse
I tried to downgrade but it failed (probably because I have a Magisk patched recovery).
So I tried to install the stock recovery but I can't boot into Fastboot... (I shut down my phone, hold down volume and plugged in USB ... also rebooting to fastbood via ADB did not work -> always booting to system).
What can I do about that? Factory reset? Or is this a known issue with EMUI 9.1?

htcdesire-hd said:
I tried to downgrade but it failed (probably because I have a Magisk patched recovery).
So I tried to install the stock recovery but I can't boot into Fastboot... (I shut down my phone, hold down volume and plugged in USB ... also rebooting to fastbood via ADB did not work -> always booting to system).
What can I do about that? Factory reset? Or is this a known issue with EMUI 9.1?
Click to expand...
Click to collapse
Let it boot to system and use Magisk manager to uninstall it. The 9.1 fastboot doesn't pay attention to the button state if it thinks it should be booting into recovery, and that flag persists as long as stock recovery hasn't booted.

irony_delerium said:
Let it boot to system and use Magisk manager to uninstall it. The 9.1 fastboot doesn't pay attention to the button state if it thinks it should be booting into recovery, and that flag persists as long as stock recovery hasn't booted.
Click to expand...
Click to collapse
Unfortunatelly Magisk says "stock backup does not exist" when I try to uninstall ...

htcdesire-hd said:
Unfortunatelly Magisk says "stock backup does not exist" when I try to uninstall ...
Click to expand...
Click to collapse
Then instead, take your stock recovery image, and from a PC:
adb push recovery_ramdisk.img /sdcard/recovery_ramdisk.img
adb shell
su
dd if=/sdcard/recovery_ramdisk.img of=/dev/block/bootdevice/by-name/recovery_ramdisk

irony_delerium said:
Then instead, take your stock recovery image, and from a PC:
adb push recovery_ramdisk.img /sdcard/recovery_ramdisk.img
adb shell
su
dd if=/sdcard/recovery_ramdisk.img of=/dev/block/bootdevice/by-name/recovery_ramdisk
Click to expand...
Click to collapse
Thank you very much, that worked!
I was not able to do that via ADB but I used the Android App "Termius" which has a local terminal.
Now I was able to remove Magisk, downgrade and root my phone again decently!
One last question: how can I prevent update notifications now?

htcdesire-hd said:
One last question: how can I prevent update notifications now?
Click to expand...
Click to collapse
Code:
adb shell pm disable-user com.huawei.android.hwouc
For that, even root is not required.
And you can always re-enable System Update by:
Code:
adb shell pm enable
com.huawei.android.hwouc

zgfg said:
Code:
adb shell pm disable-user com.huawei.android.hwouc
For that, even root is not required.
And you can always re-enable System Update by:
Code:
adb shell pm enable
com.huawei.android.hwouc
Click to expand...
Click to collapse
Thank you very much, that worked!

htcdesire-hd said:
Thank you very much, that worked!
I was not able to do that via ADB but I used the Android App "Termius" which has a local terminal.
Now I was able to remove Magisk, downgrade and root my phone again decently!
Click to expand...
Click to collapse
Apparently, you had root still working (if I correctly understand your long story).
In that case you could have also flashed stock Recovery by EMUI Flasher apk from post #1 at:
https://forum.xda-developers.com/mate-20-pro/how-to/guide-manual-updating-firmware-t3893171

zgfg said:
Apparently, you had root still working (if I correctly understand your long story).
In that case you could have also flashed stock Recovery by EMUI Flasher apk from post #1 at:
https://forum.xda-developers.com/mate-20-pro/how-to/guide-manual-updating-firmware-t3893171
Click to expand...
Click to collapse
Thank you for the tip!

zgfg said:
Code:
adb shell pm disable-user com.huawei.android.hwouc
For that, even root is not required.
And you can always re-enable System Update by:
Code:
adb shell pm enable
com.huawei.android.hwouc
Click to expand...
Click to collapse
I have one problem after setting up my phone again completely:
I can't connect to WIFI hotspots anymore... It tries to connect but ends in "connection timed out"...
What could cause this problem?
I restored my WIFI connections via Titanium Backup, could that cause a problem?

htcdesire-hd said:
I have one problem after setting up my phone again completely:
I can't connect to WIFI hotspots anymore... It tries to connect but ends in "connection timed out"...
What could cause this problem?
I restored my WIFI connections via Titanium Backup, could that cause a problem?
Click to expand...
Click to collapse
I would not restore by Titanium (specially if changing a firmware) but lby the stock Backup app (or HiSite, it's PC counterpart).
It can also backup/restore WiFi connections and with that I even successfully transfered my WiFi passwords from P9 Oreo to Mate 9 Pie
(You can select which parts you want to restore and if there are incompatible settings, it will not offer that part for restoring to the new Huawei device/firmware)

zgfg said:
I would not restore by Titanium (specially if changing a firmware) but lby the stock Backup app (or HiSite, it's PC counterpart).
It can also backup/restore WiFi connections and with that I even successfully transfered my WiFi passwords from P9 Oreo to Mate 9 Pie
(You can select which parts you want to restore and if there are incompatible settings, it will not offer that part for restoring to the new Huawei device/firmware)
Click to expand...
Click to collapse
I didn't make a backup with HiSuite...
But I solved the problem by resetting the network settings:
Settings -> System -> Reset -> Reset Network Settings

How To Guide I found a way to install GSI roms.

1. Get TWRP (Follow this guide: https://forum.xda-developers.com/t/proper-way-of-installing-twrp.4325927/)
2. Flash the vbmeta provided in the above thread
3. In TWRP, run the no verity patcher.
4. Get any A/B gsi ROM (Treble check lists wrong information)
5. Download the ChonDoe patcher
6. Rename ROM to System.img and put it on the internal storage in the same location as Chondoe patcher.
7. Run the patcher and ignore any fstab errors.
8. Success?
KNOWN BUGS: Touch isn't working after screen lock, reboot needed. Should be OK if you don't turn your screen off.
Enjoy!

There is no need for the chondoe patcher. And finaly i'm not the only one who getts does screen touch issues on gsi roms.

I don't know why you complicated it this much to install a gsi rom, it is:
1. boot in to twrp
2. wipe data, cache, dalvik
3. reboot to twrp
4. install gsi rom and reboot
and make sure dm-verify is allredy disabled.

The touch screen error is not solved if I lock and unlock the cell phone several times?

LAST_krypton said:
I don't know why you complicated it this much to install a gsi rom, it is:
1. boot in to twrp
2. wipe data, cache, dalvik
3. reboot to twrp
4. install gsi rom and reboot
and make sure dm-verify is allredy disabled.
Click to expand...
Click to collapse
How to disable dm-verity? I plan to try to install twrp to see if it works and try miui

BryanCp13 said:
How to disable dm-verity? I plan to try to install twrp to see if it works and try miui
Click to expand...
Click to collapse
You flash this file, then you format data. DO NOT rename the file.

LAST_krypton said:
There is no need for the chondoe patcher. And finaly i'm not the only one who getts does screen touch issues on gsi roms.
Click to expand...
Click to collapse
The error sucks, as anything else works great. I'll let you know if i get it fixed.

Will it be deep sleep related problem as the phone has no problems until you turned off the screen and on again?
If that is the case, using wakelock app with the CPU option enabled (which disables deep sleep) and wakelock settings> autostart on boot enabled, should make the device run fine.
However it increases idle battery drain by some extent, you have been informed about that.
Link is here.
Wakelock Revamp - PowerManager APK 3.4.0 for Android – Download Wakelock Revamp - PowerManager APK Latest Version from APKFab.com
Wakelock Revamp - PowerManager 3.4.0 latest version APK Download by darken for Android free online at APKFab.com. Easy control over Android's PowerManager.
www.google.com

LR7875 said:
Will it be deep sleep related problem as the phone has no problems until you turned off the screen and on again?
If that is the case, using wakelock app with the CPU option enabled (which disables deep sleep) and wakelock settings> autostart on boot enabled, should make the device run fine.
However it increases idle battery drain by some extent, you have been informed about that.
Link is here.
Wakelock Revamp - PowerManager APK 3.4.0 for Android – Download Wakelock Revamp - PowerManager APK Latest Version from APKFab.com
Wakelock Revamp - PowerManager 3.4.0 latest version APK Download by darken for Android free online at APKFab.com. Easy control over Android's PowerManager.
www.google.com
Click to expand...
Click to collapse
I'll try and tell you how it went. Thanks!

LR7875 said:
Will it be deep sleep related problem as the phone has no problems until you turned off the screen and on again?
If that is the case, using wakelock app with the CPU option enabled (which disables deep sleep) and wakelock settings> autostart on boot enabled, should make the device run fine.
However it increases idle battery drain by some extent, you have been informed about that.
Link is here.
Wakelock Revamp - PowerManager APK 3.4.0 for Android – Download Wakelock Revamp - PowerManager APK Latest Version from APKFab.com
Wakelock Revamp - PowerManager 3.4.0 latest version APK Download by darken for Android free online at APKFab.com. Easy control over Android's PowerManager.
www.google.com
Click to expand...
Click to collapse
Still happens, really weird

James 144 said:
Still happens, really weird
Click to expand...
Click to collapse
Well the touch screen works well until you turn the screen off and on?
What GSI do you use? Phh treble? Maybe erfangsi will work, but we don't know.

LR7875 said:
Well the touch screen works well until you turn the screen off and on?
What GSI do you use? Phh treble? Maybe erfangsi will work, but we don't know.
Click to expand...
Click to collapse
Phh Lineage 18.1. Doesn't work on normal phh treble either
I'll try erfangsi.

James 144 said:
Phh Lineage 18.1. Doesn't work on normal phh treble either
I'll try erfangsi.
Click to expand...
Click to collapse
All processes and services are running normal it is that the screen woun't recognize touch. By flashing a custom kernel and disabeling power saveing options could fix the problem.

James 144 said:
You flash this file, then you format data. DO NOT rename the file.
Click to expand...
Click to collapse
Will that remove the mount error when flashing the gsi?

LAST_krypton said:
All processes and services are running normal it is that the screen woun't recognize touch. By flashing a custom kernel and disabeling power saveing options could fix the problem.
Click to expand...
Click to collapse
Do I have to install yes or yes a kernel for that rom? (I am not Rot) since in another rom gsi it gave me mount error and permissions denied

BryanCp13 said:
Will that remove the mount error when flashing the gsi?
Click to expand...
Click to collapse
Yes.

LAST_krypton said:
All processes and services are running normal it is that the screen woun't recognize touch. By flashing a custom kernel and disabeling power saveing options could fix the problem.
Click to expand...
Click to collapse
I've found a telegram group where the rom creator is really active and willing to help. I already tried to solve it but I'm busy. Here's the link: Device name? GSI version? - #phh-treble https://t.me/phhtreble/283195 <---. Tell them that Kuba invited you and they should know that they should help with the touch screen. Rom creator said that it's 100% fixable.

what treble type is a12 has?

Jayke770 said:
what treble type is a12 has?
Click to expand...
Click to collapse
A/B. Some apps say A only but that is wrong