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
Related
Hello guys, I open a Question and Answer Thread for all SuperMan Rom users, so even users under 10 posts can ask their questions here.
Below I added some basic Q&A stuff which can also be found at the main thread, if you have any question, read through them before posting, thanks!
In case you search for the changelog have a look: Changelog post
If you want to see my post with all useful links such as TWRP, magisk, xposed and more visit: useful post
Basic Questions:
Q: How to get into Download Mode?
A: Power off your phone, than hold: home + volume down + power on button until you see the download mode.
Q: How to get into Recovery Mode?
A: Power off your phone, than hold: home + volume up + power on button until you see the recovery mode.
Q: My Phone is stuck at boot and doesn't start, what to do??
A: Update your bootloader and modem. Also make sure you have made a fresh install of the rom. Bootloader and Modem can be found in the OP. Another problem can be that you are didn't decrypt your phone. To fix this read below how to disable encryption.
Q: Do I need to update bootloader and modem after every update?
A: It's recommend to update your bootloader and modem everytime there is a new base yes. The developer will tell you if necessary on every rom changelog.
Q: I get verification failed at start up!?!? My phone is broken now?
A: Yes, you have to buy a new phone now. Just kidding You did not disable force encryption in TWRP (how to do so you will find below in how to decrypt your phone).
Q: I get verification FRP LOCK? WHYYYYYY???
A: Very simple answer, you did not enable OEM Unlock in developer options. Now you need to flash full rom with odin again and start from scratch. But don't forget to enable OEM Unlock this time!
Q: Which devices are supported at the moment?
A: Current supported devices are: SM-G930F/FD/K/L/S/W8. Snapdragons are NOT supported
Q: Is this rom working on Snapdragon 820 variants?
A: No, sadly not.
Q: I want to change something in my rom setup, how can I do that?
A: Simply reflash the same rom version without any wipe and than choose the correct things you want.
Q: Some features are not present in this rom, but they are on stock rom, so where are they?
A: In aroma installer you have the option to select bloat you want to install or not, you probably didn't select all package, this is why it's missing now.
Q: After a clean install my phone is overblated with many custom settings. What to do?
A: Open my romcontrol, grant it root permissions and then my default settings will be applied.
Q: Will you add X or Y feature?
A: You can kindly ask in the thread for that, if I like your suggestion I will think about adding it to the rom.
Q: You said you fixed SD card RW but Titanium Backup can't write to external SD card, why???
A: This is because of googles changes concerning SD card, to fix this open Titanium Backup, Menu, Preferences, Backup Folder Location, Storage provider and than hit DocumentProvider Storage and select your SD card. Problem solved
Q: I can't find X and Y mod. Please help
A: I've added many links and useful stuff to this post here. Hope that's what you have been looking for!
Q: I want to have my external storage like an internal as well. Google introduced it with android Marshmallow, but I can't see this option?
A: Just follow this Guide here and you can setup your SD card as normal storage
Q: I got a new strange icon appearing after nougat update. What's that?
A: This is a new advanced calling feature introduced in android nougat. Should make your call quality better or something like this. To hide it please visit following forum: Get rid of RCS icon
Questions concerning rom updates:
Q: Do I have to do a full wipe for the new version?
A: It is always the best option to make a clean install, otherwise please don't come and report bugs!
Q: But I don't want to make a full wipe when only small stuff changed!
A: For updates using the same bases you can install the rom with a dirty flash. BUT with a new base a clean install is highly recommend!
Q: What steps should I do to update to a new version with a full wipe but keep all data?
A: There are some different ways. One way is to make a backup with Titanium Backup, you can backup all Apps and Preferences there. Make sure to store this backup on external SD card (if you have one). Second way would be to save your data onto a google account or samsung cloud and restore it after a clean install.
Q: I miss an apk after rom update, how can I get it back?
A: Simply reflash rom and select "dirty flash" in aroma + select the app this time in aroma.
Q: My battery life is so bad and performance is very poor after an update!?!?
A: This comes actually not form the rom itself, dirty flash can cause problems even if only some small things have been changed. So simply install it clean again and it will solve your problem.
Q: Performance and battery is very poor even after clean install. What should I do now?
A: I assume you installed Xposed than, some modules can cause batterydrain and performance problems. So try to make a clean install of the rom WITHOUT xposed installed.
Questions about log and logcats:
Q: I got FC's and other Problems with the rom, what to do?
A: Take a logcat for me, developers use to say: without a log, it never happened . A logcat can be grabed with a PC and ADB installed, simply type: adb logcat > log.txt while your phone is connected and the error is happening. Same can be done if you have a terminal installed on your phone. Simply type adb logcat > log.txt and you will have the same output as on the PC.
Q: What kind of logs can I provide to help you?
A: Logcat: This one is for general infos about FC's
DMESG: this is for kernel related things
Last_Kmsg: this can be used after a random reboot
Q: How to get logs?
A: 1. Connect your phone to your pc
2. Make sure you got usb debugging enabled
3. Install Minimal ADB tool
4. After install open it and type: adb logcat > logcat.txt, adb shell dmesg > dmesg.log, adb shell cat proc/last_kmsg kmsg.log
5. Send me the file you got
You can also send me a log created by your phones terminal with the exact same commands!
Questions about RomControl:
Q: None of my romcontrol changes do anything, why are you such a bad dev!?!?
A: The problem is not on my end, you installed stock systemUI (which is STOCK and does not support one single mod). Use another one in aroma instead. The same thing can happen with good lock!
Q: Romcontrol gives FC's to me. HELP!
A: Very simple answer here: wipe data and cache from superman control application. Also make sure storage permissions are given to the romcontrol.
Q: Romcontrol still FC after cleaning data and cache!
A: Make sure you allow storage permission in main settings.
Q: I try to backup my current RomControl setup, but it won't work?
A: It works. Just make sure to enable storage permission in main samsung applicatoin settings. You will find it in internal sdcard under RomControl folder.
Q: I can't restore SuperMan control settings after a clean base update, why?
A: Backup for SuperMan control only works as long as you use the same version of the app, I mostly change very much things in new releases that's why it won't work there.
Q: SystemUI reboot doesn't work in SuperMan settings app, why?
A: Since Nougat update, you need to install busybox in order to get this button working. Without busybox the button will just do nothing.
Q: I enabled weather on lockscreen but I can't see anything...
A: You probably didn't setup or even installed samsungs weather widget. Without it weather on lockscreen won't work too. So reflash the rom with the widget installed this time and set it up.
How to go back to stock:
Q: I like to go back to stock rom, how is this possible?
A: I can provide you here all steps which are needed to go back to a full stock rom.
0. Make a backup and than wipe all partitions in TWRP
1. Go to Sammobile and choose your country
2. Download the file and the attached Odin on sammobile
3. After downloading, put your phone into download mode
4. Make sure drivers are installed and your pc can detect your phone in odin
5. If the box in odin turns blue, add the AP file to AP tab, BL file to BL tab, CP file to CP tab and CSC_HOME to CSC tab
6. Hit start and wait until it is finished.
7. Reboot and you have a stock rom again
Questions about Encryption:
Q: On TWRP there is an error about /data mount, what to do?
A: Your device is encrypted, follow the steps below to get rid of your encryption.
Q: Help, I never had a code and now after installing the rom my phone asks for a password??
A: Your device is still encrypted, on step 0 of my rom instructions it tells you to be sure you're not. So, what do you need to to in case you are still encrypted.
A: HOW TO DISABLE ENCRYPTION:
1. Boot into TWRP
2. Select Wipe
3. Select format data
4. Then you manually need to type "yes" with the keyboard
5. Confirm the wipe (this will remove the encryption)
6. Reboot your recovery
Q: Is there a way to get rid of encryption which is simpler?
A: Not really, you could also wipe data with stock recovery but this is quite a big hassle so above method works better.
Q: And if I want to use this rom with encryption?
A: Normally we can use the stock kernel to encrypt our device, but since the Android 7.0 Nougat update samsung makes a check kernel sides to block deodexed roms from booting. This means that even the stock kernel is build by me to disable knox and tima. So encryption won't work there and you have to encrypt your device after you set up your phone. After that go to settings, security, encrypt device. It may need some additional steps to work...
Questions about CSC/Signal:
Q: Where has the CSC selection gone?
A: To include all csc files, the rom get way to big, so it got it's own thread now, take a look here: CSC installer
Q: I have a weak cellular signal, what can I do against it?
A: Two things: first, install your providers CSC using CSC installer and flash in TWRP or flashing stock CSC with Odin. Second Thing: You can install the modem from your provider, also find your modem on Sammobile and install it with Odin in CP tab.
Q: I don't have all sHealth features, how come?
A: Not all CSCs include this feature. I recommend to use AUT or DBT as it has the best compatibility!
Q: Can I flash MM CSC on N and vis a verse?
A: No, this is clearly not recommend! You can and will face call fc's!
Questions about Xposed:
Q: Does Xposed work yet on Android N 7.0?
A: No it does not! You will end up in a bootloop when you flash it on android N
Q: I selected xposed but now I don't see an app for it?
A: Maybe there went something wrong with installing the app to /data/app from my installer script. But xposed is actually installed only the app is missing, so head over to the download page of xposed app: Material Xposed Thread
Q: I selected xposed but the app shows not active or something else with xposed is not working.
A: This can have 2 reasons:
1. You have installed latest xposed version without installing magisk, magisk is required for most recent xposed version!
2. You used 86.2 xposed (which does not need magisk) but you did not install supersu. Since 86.2 does not use magisk to be systemless it uses supersu instead!
Questions about Magisk:
Q: How can I pass safetynet?
A: 1. Make sure to fully uninstall SuperSU by chainfire
2. Flash most recent 2.4.3 SuperStock Kernel
3. Flash Magisk V12
4. install latest Magisk Manager from playstore
5. Open Magiks Manager, go to settings
6. Enable MagiskHide, systemless hosts and systemless busybox
7. Reboot the phone and check safetynet!
Q: I got out of date binary issue?
A: Since Magisk V11.1 there is no need for phh root anymore. Everything is handled inside the MagiskManager apk!
Q: Where can I configure the root settings in Magisk?
A: Since Magisk V11.1 Magisk uses MagiskSU, you can find it in latest Magisk Manager V4.1
Questions about Snapchat:
Q: Even when I did not use xposed during my setup in rom I can't login to snapchat anymore!
A: Snapchat got updated and now detects even root access on your phone!
Q: What to do to login to snapchat then?
A: Clean install the rom without root and xposed and login to your snapchat, save the app with titanium backup, flash back xposed and root. For the next update of the rom just restore snapchat backup in TB.
Q: Any other possibility?
A: You could enable MagiskHide and check Snapchat inside it so root will be hidden from Snapchat. You will be able to perfectly login without any issues.
Q: I want to discuss this problem a bit deeper. Should I do so?
A: Do that, but this has nothing to do with this rom, so please go ahead and post your experience here on this Snapchat Thread.
Questions about Kernels:
Q: I want to switch kernel, how?
A: Since we have systemless xposed and systemless supersu, we have patches in ramdisk of boot.img. This means you have to reflash Magisk and supersu (or any other zip that changes some stuff in ramdisk partition) after every change of kernel!
Q: Synapse shows no UCI support!
A: Most comon issue is that no busybox is installed. Download the one from here: Latest busybox and flash it in recovery.
Q: I got random reboots, heeelp!
A: This is most likely from a custom kernel, if you face random reboots please check if you have the latest kernel installed or switch back to the stock kernel included in the rom.
Q: My screen is kind of yellow/orange and the touchscreen doesn't work at all!
A: You have chosen the wrong kernel in aroma selection. Reflash the rom without any wipe selecting the right kernel version.
Questions about Root:
Q: I lost root after installing this rom. What to do?
A: All mods (like supersu, phh's root, xposed and magisk) are stored in ramdisk of kernel boot.img. So if you flash this rom, and after this another kernel, simply reflash your preferred root method and it will work again!
Q: I selected phh root but my phone tells me I am not rooted!!
A: There are two possibilities:
1. You have mixed supersu/phh with magisk.
2. You did not install phhs root app from playstore.
Q: I get a warning about binary out of date. Help!
A: That happens on latest Magisk V11.1. Reason: Root has fully moved into Magisk Manager, no additional app required. Uninstall phh or supersu apps and only use magisk!
Q: I want to use su hide on my phone, how to do so?
A: Both below variants are outdated, I recommend to use Magisk with its build in MagiskHide. Check the thread: Magisk Thread
Link to phh's hidesu: Phh's thread
Link to chainfires suhide: Chainfires thread
Hi,
I have a bit of a silly question. I have enabled the torch to be turned on by the volume button but now want to turn that function off and can't remember where i enabled it from. I have looked everywhere but can't find it. Are you able to point me in the right direction.
Many thanks.
reeves72 said:
Hi,
I have a bit of a silly question. I have enabled the torch to be turned on by the volume button but now want to turn that function off and can't remember where i enabled it from. I have looked everywhere but can't find it. Are you able to point me in the right direction.
Many thanks.
Click to expand...
Click to collapse
Hello
Settings, display, torchlight
Sent from my SuperMan powered SM-G930F
Tkkg1994 said:
Hello
Settings, display, torchlight
Sent from my SuperMan powered SM-G930F
Click to expand...
Click to collapse
Thanks that was driving me crazy.
downloadable files verification
Can some one verify that all of the downloadable files on the OP are the correct ones?
Can't seem to get it working, the steps I follow, are as following.
-> flash to stock rom from sammobile
-> OEM unlock
-> flash latest TWRP
-> in TWRP, format data
->install latest BL and CP from OP
-> flash rom -> Clean install
result is a non booting superman rom.. What can I do? I have been trying for DAYS now...
grave-diggers said:
Can some one verify that all of the downloadable files on the OP are the correct ones?
Can't seem to get it working, the steps I follow, are as following.
-> flash to stock rom from sammobile
-> OEM unlock
-> flash latest TWRP
-> in TWRP, format data
->install latest BL and CP from OP
-> flash rom -> Clean install
result is a non booting superman rom.. What can I do? I have been trying for DAYS now...
Click to expand...
Click to collapse
There are several reasons:
1. Encryption is still enabled
2. BL/CP was not successfull
3. You mixed your settings about G930F or G935F model
I noticed a few things in aroma log when it was installing
failure to boot.img extracting ramdisk failure, aborting, is this something that's causing the problem?
I am still not getting it right..
grave-diggers said:
I noticed a few things in aroma log when it was installing
failure to boot.img extracting ramdisk failure, aborting, is this something that's causing the problem?
I am still not getting it right..
Click to expand...
Click to collapse
Thats not really good lol. Redownload the rom. Maybe you got a corrupt zip file
Sent from my SuperMan powered SM-G930F
Holy crap I got it to work.. 4 days of trying to get this to work made me get alot of knowledge about this stuff, the file was corrupt, redownloading the file worked.
grave-diggers said:
Holy crap I got it to work.. 4 days of trying to get this to work made me get alot of knowledge about this stuff, the file was corrupt, redownloading the file worked.
Click to expand...
Click to collapse
Finally!
Sent from my SuperMan powered SM-G930F
Right at this point I am wondering why snapchat doesn't want to log me in. There's no xposed or snapprefs on my phone, exposed uninstaller was flashed. Does this come familliar? There has to be a workaround without having to use bluestacks right?
grave-diggers said:
Right at this point I am wondering why snapchat doesn't want to log me in. There's no xposed or snapprefs on my phone, exposed uninstaller was flashed. Does this come familliar? There has to be a workaround without having to use bluestacks right?
Click to expand...
Click to collapse
Someone said that it even checks for root now
Okay, here's the solution. If you find yourself having trouble logging in in to snapchat on a rooted device without xposed framework installed. Make sure to search for xposed using root explorer, delete all system files manually.. For some reason xposed uninstaller did not completely remove every xposed file in my phone.
SM-G930L
Does this ROM works on Korean variant? SM-G930L is the model. Thanks in advance
genorazer said:
Does this ROM works on Korean variant? SM-G930L is the model. Thanks in advance
Click to expand...
Click to collapse
Make a full backup and try
Sent from my SuperMan powered SM-G930F
Im on fully stocked g930fd
Can u confirmed is this the correct sequence
Root
Install twrp
Make a back up
Make a clean flash
Install superman rom
tatuboy said:
Im on fully stocked g930fd
Can u confirmed is this the correct sequence
Root
Install twrp
Make a back up
Make a clean flash
Install superman rom
Click to expand...
Click to collapse
No need to flash root. Flash twrp, flash bl and cp? backup, wipe (remove encryption) flash rom.
Sent from my SuperMan powered SM-G930F
Tkkg1994 said:
No need to flash root. Flash twrp, flash bl and cp? backup, wipe (remove encryption) flash rom.
Sent from my SuperMan powered SM-G930F
Click to expand...
Click to collapse
Can u link to me the needed files?
If it have video tutorial much better..
Im from oneplus3 users before.
So i dont have much knowlege in s7.
I need to know
First how to flash TWRP?
2ND What is bl? U mean boot loader?
Cp? What does it mean for?
Then after i back up. And wipe.
How to remove encryption?
tatuboy said:
Can u link to me the needed files?
If it have video tutorial much better..
Im from oneplus3 users before.
So i dont have much knowlege in s7.
I need to know
First how to flash TWRP?
2ND What is bl? U mean boot loader?
Cp? What does it mean for?
Then after i back up. And wipe.
How to remove encryption?
Click to expand...
Click to collapse
Okay you want to install this rom. So go to my main page and follow all android beginner steps. Very detailed guide there
Sent from my SuperMan powered SM-G930F
Tkkg1994 said:
Make a full backup and try
Sent from my SuperMan powered SM-G930F
Click to expand...
Click to collapse
is there a chance it could brick the phone?
OK, I’ve ordered and am awaiting arrival of my unlocked Pixel 2 from Google. I am on Verizon GFUDP and I plan on unlocking, rooting with Magisk and installing the tethering module. Then I plan on enjoying the phone and pretty much don’t plan on fussing around much with it.
I plan on unlocking before I do anything, including installing my Verizon sim. But do I have to allow the phone to do any upgrading prior to the rooting process? Also, can I (should I)hold off installing my sim until everything is rooted and up and running?
I was also thinking of using the Skipsoft toolset, but not sure if it is necessary. What are your thoughts on that?
Also, regarding lockscreen security on the phone, is fingerprint or password required? Can you use one or the other? I never use a passcode in general so wondering how it works.
Any "must have" apps to take advantage of Pixel 2?
Any help or advice is much appreciated!
Thanks in advance!
I purchased two Pixel 2 phones, and did the same thing you're planning on doing. I also have Verizon.
1) Unlocking the bootloader will wipe the device; Do this first. If you set up the phone prior to OEM unlocking, you will lose everything you set up.
2) Installing the SIM at anytime won't affect anything. When you install the Verizon SIM, some verizon apps will download. You can delete them if you want.
3) I did not use skipsoft. If you have a basic knowledge of ADB/Fastboot you will be fine without it.
4) The finger print reader is crazy fast. Also, setting up the phone it asks for a pin. Try it with the security of both to start. If you dislike it you can disable it in the future.
5) Apps I like/use: Tasker, Magisk, Titanium Backup, Custom Navigation Bar, Hide "using battery" notification, AdAway, Nova Launcher, Swipepad (where I put the "reboot" shortcuts), Reboot (Material Design) [ I made shortcuts to enter recovery, bootloader, etc], 1weather, Digilux (screen brightness control from the fingerprint reader), and Naptime (Have seen some battery length increase, though slows down notifications)
6) Not really apps, though @Tulsadiver made mods via Aroma from here: Various Mods for 8.1 December Update (Added Screen shots to show black notifications, battery icon removal, and clock w/day & ampm)
7) I like the Snoke kernel found here: [KERNEL]Snoke Kernel by @DespairFactor
There is a guide here: [GUIDE] Unlock/Flash/Root for the Pixel 2 (walleye) by @nathanchance
I laid out steps in this post here: [GUIDE] Unlock/Flash/Root for the Pixel 2 (walleye) - Post 127
Here are links because sometimes they can be tiresome to find:
SDK Platform Tools
(Follow the steps in the linked Post 127 to make cmd and SDK tools easier)
Factory Images for Nexus and Pixel Devices
Full OTA Images for Nexus and Pixel Devices
amajamar said:
Do I have to allow the phone to do any upgrading prior to the rooting process?
Click to expand...
Click to collapse
You should.
amajamar said:
Also, can I (should I)hold off installing my sim until everything is rooted and up and running?
Click to expand...
Click to collapse
Doesn't make a difference.
amajamar said:
I was also thinking of using the Skipsoft toolset, but not sure if it is necessary. What are your thoughts on that?
Click to expand...
Click to collapse
I'd do it manually via the command line with fastboot and adb - knowing how to use these tools is very important in case something ever goes wrong.
amajamar said:
Also, regarding lockscreen security on the phone, is fingerprint or password required? Can you use one or the other? I never use a passcode in general so wondering how it works.
Click to expand...
Click to collapse
You can use both.
Diesel_Jeremiah said:
I purchased two Pixel 2 phones, and did the same thing you're planning on doing. I also have Verizon.
1) Unlocking the bootloader will wipe the device; Do this first. If you set up the phone prior to OEM unlocking, you will lose everything you set up.
2) Installing the SIM at anytime won't affect anything. When you install the Verizon SIM, some verizon apps will download. You can delete them if you want.
3) I did not use skipsoft. If you have a basic knowledge of ADB/Fastboot you will be fine without it.
4) The finger print reader is crazy fast. Also, setting up the phone it asks for a pin. Try it with the security of both to start. If you dislike it you can disable it in the future.
5) Apps I like/use: Tasker, Magisk, Titanium Backup, Custom Navigation Bar, Hide "using battery" notification, AdAway, Nova Launcher, Swipepad (where I put the "reboot" shortcuts), Reboot (Material Design) [ I made shortcuts to enter recovery, bootloader, etc], 1weather, Digilux (screen brightness control from the fingerprint reader), and Naptime (Have seen some battery length increase, though slows down notifications)
6) Not really apps, though @Tulsadiver made mods via Aroma from here: Various Mods for 8.1 December Update (Added Screen shots to show black notifications, battery icon removal, and clock w/day & ampm)
7) I like the Snoke kernel found here: [KERNEL]Snoke Kernel by @DespairFactor
There is a guide here: [GUIDE] Unlock/Flash/Root for the Pixel 2 (walleye) by @nathanchance
I laid out steps in this post here: [GUIDE] Unlock/Flash/Root for the Pixel 2 (walleye) - Post 127
Here are links because sometimes they can be tiresome to find:
SDK Platform Tools
(Follow the steps in the linked Post 127 to make cmd and SDK tools easier)
Factory Images for Nexus and Pixel Devices
Full OTA Images for Nexus and Pixel Devices
Click to expand...
Click to collapse
Nice! Thanks! No need for TWRP? I was going to install it.
Was there a "thing" regarding which version of Magisk to install? I thought I read something somewhere about issues with the newest version.
amajamar said:
Nice! Thanks! No need for TWRP? I was going to install it.
Was there a "thing" regarding which version of Magisk to install? I thought I read something somewhere about issues with the newest version.
Click to expand...
Click to collapse
I have TWRP installed as well. I didn't comment on it since you didn't ask about it.
NOTE: You have to boot TWRP img, then install TWRP ZIP. Search threads, you'll find the info.
NOTE 2: You cannot install TWRP, Magisk and Kernel at the same time. Best way is to install everything is: TWRP ZIP, reboot. Flash Kernel, reboot. Flash Magisk, reboot.
As for Magisk, I'm on v5.5.3 and V15.2 without issues.
I've been upgrading through Magisk direct install without issues.
NOTE: You will get a pop up that your system has an issue and contact the manufacturer after Magisk. Do not panic, it'd because Magisk is modifying the DTBO img. It does not harm anything.
I also installed Viper4Android from Magisk.
Version 2.5.0.4 = works normal and processes correctly.
Diesel_Jeremiah said:
I have TWRP installed as well. I didn't comment on it since you didn't ask about it.
NOTE: You have to boot TWRP img, then install TWRP ZIP. Search threads, you'll find the info.
NOTE 2: You cannot install TWRP, Magisk and Kernel at the same time. Best way is to install everything is: TWRP ZIP, reboot. Flash Kernel, reboot. Flash Magisk, reboot.
As for Magisk, I'm on v5.5.3 and V15.2 without issues.
I've been upgrading through Magisk direct install without issues.
NOTE: You will get a pop up that your system has an issue and contact the manufacturer after Magisk. Do not panic, it'd because Magisk is modifying the DTBO img. It does not harm anything.
I also installed Viper4Android from Magisk.
Version 2.5.0.4 = works normal and processes correctly.
Click to expand...
Click to collapse
Awesome! What features does the Snoke kernel give? Any issues with it? Do you need to flash the factory kernel to take an OTA?
I never used Viper4Android before. What does it do?
Thanks.
amajamar said:
Awesome! What features does the Snoke kernel give? Any issues with it? Do you need to flash the factory kernel to take an OTA?
I never used Viper4Android before. What does it do?
Thanks.
Click to expand...
Click to collapse
Custom Kernel: Android Basics 101: Understanding Kernels – XDA Developer TV
I feel a bit snappier response and better battery life. There is Snoke, Flash, and ElementalX to name a few.
If you've loaded TWRP at all or mounted system rw; OTAs will not work. You'll have to use the factory images.
I've had no issues with the Snoke kernel. Just ensure you use the proper one for 8.0 or 8.1.
Viper4Android: Get the Sound you Deserve with ViPER4Android -- Android App Review
Viper4Android and Pizel 2 front facing speakers work very well together.
Diesel_Jeremiah said:
Custom Kernel: Android Basics 101: Understanding Kernels – XDA Developer TV
I feel a bit snappier response and better battery life. There is Snoke, Flash, and ElementalX to name a few.
If you've loaded TWRP at all or mounted system rw; OTAs will not work. You'll have to use the factory images.
I've had no issues with the Snoke kernel. Just ensure you use the proper one for 8.0 or 8.1.
Viper4Android: Get the Sound you Deserve with ViPER4Android -- Android App Review
Viper4Android and Pizel 2 front facing speakers work very well together.
Click to expand...
Click to collapse
Excellent information! Thanks!
Hello all, long time member but never really had a reason to post.
I just received my oneplus6, I wanted IOS style emojis (ridiculous I know... lol) So I unlocked bootloader, flashed the temporary TWRP release and flashed MAGISK.
When I booted my phone the error "There's an internal problem with your device contact your device manufacturer" comes up. Unfortunately I took my nandroid backup AFTER installing MAGISK.
I have no wifi at all, I can't use wifi hotspot either, but cellular works. I wanted to flash back to stock recovery but it seems oneplus hasn't released it. I have tried removing magisk and rebooting (via the magisk app) but then the device wont boot.
I canno't flash a stock copy of OxygenOS as it seems it can only be flashed with stock oxygen oneplus6 recovery (which I cannot get access to.) TWRP simply fails to flash it.
Recently in an attempt to solve my issue I formatted the memory, magisk has gone from my app drawer, but the effects it had are still there (I still have IOS emojis) Now apps wont login (snapchat for example says there is a temporary error) Facebook managed to login after a few reboots, I cannot stream video at all. And as I have formatted memory the original nandroid backup (after magisk flash where apps would login but still gives the internal error message and no wifi) is gone.
I really just want to get the device back to a stable operation, if anyone knows what I should do next or somehow has access to stock oneplus6 recovery, please let me know! Thankyou in advance for all help.
Find post with stock fastboot ROMs, download it and extract, then run flash-all.bat while phone is in fastboot
But data will be gone
DalekExt said:
Find post with stock fastboot ROMs, download it and extract, then run flash-all.bat while phone is in fastboot
But data will be gone
Click to expand...
Click to collapse
you mean this?: https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
I just did this and it has bricked the phone lol, it fails when I try to complete it
Bricked
19kylegreer96 said:
you mean this?: https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
I just did this and it has bricked the phone lol, it fails when I try to complete it
Click to expand...
Click to collapse
Hi,there is un-brick tool available
I would just like to guide anyone who might be having the same issue as me, to this post:
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
And take note of what I said here about Large address aware ( to make this fix work on 64bit PC):
https://forum.xda-developers.com/showpost.php?p=76658555&postcount=34
Using the BAT file in that post that I have linked and the large address aware fix, my problem is fixed and I have now booted the phone and have working wifi!
If you run into that issue next time, just remember to install the provided boot image within TWRP, along with the other zip files to get TWRP to not lag. I had the exact same issues as you and I realized I missed the step of flashing the boot.img within TWRP.
Once I did that, I had working TWRP and WiFi!
I received the same message after rooting. However, everything is working well (wifi, 4G/LTE/camera, etc) except this message [There's an internal problem with your device. Please contact your adminstrator] during start-up.
Whenever I have seen this I just flash the same version of the original rom over my install and it fixes it.
I also notice that for me, Magisk 6.6 causes this, whereas 6.4 does not.
Was an issue if you use Magisk and stock kernel. Use any other kernel around: They fixed it. @Sultanxda pointed the issue at his GitHub site and kernel devs have included it. Thanks @Sultanxda for this .
MickyFoley said:
Was an issue if you use Magisk and stock kernel. Use any other kernel around: They fixed it. @Sultanxda pointed the issue at his GitHub site and kernel devs have included it. Thanks @Sultanxda for this .
Click to expand...
Click to collapse
Going from memory so I might not have it straight but I want to say this was from installing either twrp on just 1 partition or Magisk on the inactive partition. Making 16.4 and 16.6 works perfectly with stock kernel since already 5.1.6 for me as I've had this phone since launch.
It was all working without a problem - just the message popped up. Altering something in the kernel triggered this to happen. @eng.stk got this issue explained by another user, pointing to the Git from sultanxda. Since then, it was solved. Dunno. Had this in the very beginnings and since then never again. Well... Yeah
Thanks
MickyFoley said:
Was an issue if you use Magisk and stock kernel. Use any other kernel around: They fixed it. @Sultanxda pointed the issue at his GitHub site and kernel devs have included it. Thanks @Sultanxda for this .
Click to expand...
Click to collapse
Thank you. That worked fine. I flashed [KERNEL] [blu_spark r31 OP6] [OOS 5.1.*] and the Error-Message is gone.
Installing a custom kernel fixed the issue for me as well.
Magisk fully working now as well as safetynet.
Might want to to edit the title to *fixed* so people know you resolves your issue.
Q: After flashing Magisk, my device will show a scary popup saying "There's an internal problem with your device. Contact your manufacturer for details"
A: This is caused by dtbo image patched to remove AVB 2.0 of the vendor partition. This is required for allowing you to mount vendor to rw and make modifications
If you never plan to modify the vendor partition, in Magisk Manager, "Uninstall > Restore Images" to restore the images, check "Preserve AVB 2.0/dm-verity" box in Advanced Settings, then reinstall Magisk via the app.
JerryGoyal said:
Q: After flashing Magisk, my device will show a scary popup saying "There's an internal problem with your device. Contact your manufacturer for details"
A: This is caused by dtbo image patched to remove AVB 2.0 of the vendor partition. This is required for allowing you to mount vendor to rw and make modifications
If you never plan to modify the vendor partition, in Magisk Manager, "Uninstall > Restore Images" to restore the images, check "Preserve AVB 2.0/dm-verity" box in Advanced Settings, then reinstall Magisk via the app.
Click to expand...
Click to collapse
Great, it worked!!!! It solved the scary message pop-up and kept the root. Thanks!!!
Hey guys,
since i got my Oneplus 6, i couldnt get viper to work quite right. Most of the time its just shows "Processing: No" till i restart it and after like a hour or device switch it turns off.
I tried:
Copying the Audioeffects.conf from system/etc to vendor/etc
Using Magisk Audio Compability Module
Using Alternate Magisk V4A Module
Using a Magisk Rom with Build-In V4a (currently xXx 2.8)
Disabling Dirac and Services
but nothing worked
thanks for your help
i had the same but then i tried to use the other viper release from magisk and it worked. there is this one called hifi and fx
Try exiting the viper app with the 3 dots top right hand corner. That is what worked for me
dgunn said:
Try exiting the viper app with the 3 dots top right hand corner. That is what worked for me
Click to expand...
Click to collapse
that works for like 10 mins and then it gets killed
byReqz said:
that works for like 10 mins and then it gets killed
Click to expand...
Click to collapse
Sounds to me like you need to disable the battery optimizations for Viper. It's almost as if your phone is detecting High battery drain and shuts down the app
dgunn said:
Sounds to me like you need to disable the battery optimizations for Viper. It's almost as if your phone is detecting High battery drain and shuts down the app
Click to expand...
Click to collapse
yeah thats what i thought too, i zried whitelisting it and installing it as system app (+ magisk module) but it didnt seem to work.
I removed the one from my rom and tried the magisk repo version again and somehow its working till now
byReqz said:
yeah thats what i thought too, i zried whitelisting it and installing it as system app (+ magisk module) but it didnt seem to work.
I removed the one from my rom and tried the magisk repo version again and somehow its working till now
Click to expand...
Click to collapse
I was unaware that you were using the magisk module. I could not get that one to work either
dgunn said:
I was unaware that you were using the magisk module. I could not get that one to work either
Click to expand...
Click to collapse
the normal one doesnt work with viper doewsnt it?
Try just exiting the viper app then reopening it. I had this problem before and it just randomly went away.
TheNetwork said:
Try just exiting the viper app then reopening it. I had this problem before and it just randomly went away.
Click to expand...
Click to collapse
it only works for a few mins that way
I'm using the Android p beta and i don't have the problems with viper as i did with oxygen os 5. it's always processing for my headphones, either plugged in or Bluetooth. the only exception is sometimes after receiving a call while listening to music, after the call is over and my music resumes, viper is no longer processing. not every time though. i used the latest magisk and the viper module in the screenshot.
i also didn't make any changes to conf files, just installed through magisk download. rebooted, opened viper fx, gave it storage permissions and turned it on.
Had the same problem, but was able to resolve it by choosing the legacy (non-material) interface when installing the Magisk module. I still flashed the full module and selected the latest version, just not the material interface. It may have been something else, but I've updated my ROM (HavocOS) several times and even done a couple full fastboot stock resets and the issue is yet to resurface.
TuxRuffian said:
Had the same problem, but was able to resolve it by choosing the legacy (non-material) interface when installing the Magisk module. I still flashed the full module and selected the latest version, just not the material interface. It may have been something else, but I've updated my ROM (HavocOS) several times and even done a couple full fastboot stock resets and the issue is yet to resurface.
Click to expand...
Click to collapse
as i said, idk why but its working now.and im on material now
byReqz said:
Hey guys,
since i got my Oneplus 6, i couldnt get viper to work quite right. Most of the time its just shows "Processing: No" till i restart it and after like a hour or device switch it turns off.
I tried:
Copying the Audioeffects.conf from system/etc to vendor/etc
Using Magisk Audio Compability Module
Using Alternate Magisk V4A Module
Using a Magisk Rom with Build-In V4a (currently xXx 2.8)
Disabling Dirac and Services
but nothing worked
thanks for your help
Click to expand...
Click to collapse
I've had this problem on an Samsung S7 Edge, S8 Plus, and now, a Oneplus 6.
Everything appears to look good on Driver Status, except "Processing:No" and it's audibly not on.
What's worked for me in this specific situation is replacing the configuration file "audio_effects.conf" in /system/vendor/etc with another configuration file that I found in another XDA thread. So here's the concrete steps:
1. Install the viper4android FX module from Magisk manager that has four devs (v1.7 as i write this) and reboot. I don't know if this method will work with other v4a modules. Note that Processing will work temporarily, but likely won't survive a reboot.
2. Download this file (files_for_v4a.zip) from here:
https://forum.xda-developers.com/ga...laxy-s8-s8-t3596933/post72049061#post72049061
3. Unzip files_for_v4a.zip and make note where it extracted. (You'll need one of its contents, audio_effects.conf, later)
4. Using a file explorer with root capability, go to the following directory:
/system/vendor/etc
5. Copy the existing "audio_effects.conf" to another directory, for example /download, to use as a backup in case this goes badly
6. Copy the file "audio_effects.conf" that you unzipped earlier to /system/vendor/etc, overwriting the existing file.
7. Reboot and test v4a.
Good luck!
Note: The Pulse feature of a custom NavBar in custom ROMS based on LOS 15.1 will not work if you do the above.
Although I'm just a hack, I modded an "audio_effects.conf" file using commits from the above to work with Pulse. I've tested it on my device (despite my lack of know-how, it seems to work for me and others!), so be aware of this if you download the following file and use it (by renaming it audio_effects.conf and placing it in /system/vendor/etc):
reaper000 said:
I've had this problem on an Samsung S7 Edge, S8 Plus, and now, a Oneplus 6.
Everything appears to look good on Driver Status, except "Processing:No" and it's audibly not on.
What's worked for me in this specific situation is replacing the configuration file "audio_effects.conf" in /system/vendor/etc with another configuration file that I found in another XDA thread. So here's the concrete steps:
1. Install the viper4android FX module from Magisk manager that has four devs (v1.7 as i write this) and reboot. I don't know if this method will work with other v4a modules. Note that Processing will work temporarily, but likely won't survive a reboot.
2. Download this file (files_for_v4a.zip) from here:
https://forum.xda-developers.com/ga...laxy-s8-s8-t3596933/post72049061#post72049061
3. Unzip files_for_v4a.zip and make note where it extracted. (You'll need one of its contents, audio_effects.conf, later)
4. Using a file explorer with root capability, go to the following directory:
/system/vendor/etc
5. Copy the existing "audio_effects.conf" to another directory, for example /download, to use as a backup in case this goes badly
6. Copy the file "audio_effects.conf" that you unzipped earlier to /system/vendor/etc, overwriting the existing file.
7. Reboot and test v4a.
Good luck!
Note: The Pulse feature of a custom NavBar in custom ROMS based on LOS 15.1 will not work if you do the above.
Although I'm just a hack, I modded an "audio_effects.conf" file using commits from the above to work with Pulse. I've tested it on my device (despite my lack of know-how, it seems to work for me and others!), so be aware of this if you download the following file and use it (by renaming it audio_effects.conf and placing it in /system/vendor/etc):
Click to expand...
Click to collapse
Thanks for your long answer, will be trying the files if this module fails again.
Also im not on a LOS Based Rom, im on OOS and GravityBox
byReqz said:
Thanks for your long answer, will be trying the files if this module fails again.
Also im not on a LOS Based Rom, im on OOS and GravityBox
Click to expand...
Click to collapse
Just seeing if I can help! And I did the same sequence of steps on OOS as well ... But I haven't run gravity box in awhile. Hope it works out for you.
reaper000 said:
Just seeing if I can help! And I did the same sequence of steps on OOS as well ... But I haven't run gravity box in awhile. Hope it works out for you.
Click to expand...
Click to collapse
I tried everything but it still needs a restart to be working sometimes, do you know if i have to disable dirac or something?
byReqz said:
I tried everything but it still needs a restart to be working sometimes, do you know if i have to disable dirac or something?
Click to expand...
Click to collapse
I haven't messed with dirac at all, and v4a still works for me.
Some clarification, please:
Did you uninstall the v4a magisk module that came with xXx and reboot?
Then go to magisk manager and install v4a fx materialized1.7 and follow the rest of the steps outlined in my post?
reaper000 said:
I haven't messed with dirac at all, and v4a still works for me.
Some clarification, please:
Did you uninstall the v4a magisk module that came with xXx and reboot?
Then go to magisk manager and install v4a fx materialized1.7 and follow the rest of the steps outlined in my post?
Click to expand...
Click to collapse
yeah, its 1.7 from magisk repo, disabling dirac seems to help a bit but not everytime
byReqz said:
yeah, its 1.7 from magisk repo, disabling dirac seems to help a bit but not everytime
Click to expand...
Click to collapse
And you replaced the audio_effects.conf file in /system/vendor/etc with the one from the downloaded zip?
(Sorry to belabor the point, but it's not clear to me you tried all that)
Nokia Extensions!Telegram Group
This thread is discontinued. Future posts will be made here.
Module description
Why should the Chinese have all the fun? This module aims at porting features from the Chinese variants of Nokia phones to Global variants (Android One).
Features
1. AI Floating Ball
The phone will recommend relevant application shortcut settings according to your usage. You can also:
Use the custom shortcuts to customize the shortcut menu.
Use gestures to enrich your interaction with the phone.
2. Data speed indicator
Tested and working on Nokia 6, Nokia 8 and Nokia 7 plus on Oreo. After installation, go to Settings - Network & Internet - Data Usage and toggle Show data speed. Now you should be able to see your internet speed on your status bar.
3. Screenshot Plus
Take long screenshots, edit them on the go.
4. Screen Recorder
Supports FHD, HD and SD at 30 and 60 FPS, records audio too.
5. Junk Cleaner
Clears cache and junk files.
6. Task Manager
View and end a running task.
7. Smart Boost
Enjoy gaming without frame drops and hiccups!
8.. Virus scanner
Scan for virus and keep your phone secure.
9. NokiaPure fonts
Change your system font to NokiaPure
How to's
To install the module, flash the zip using Magisk manager or TWRP and reboot.
To uninstall the module, flash the same zip again and reboot.
To get the internet speed on the status bar, go to Settings - Network & Internet - Data Usage and toggle Show data speed.
To use Screenshot plus and Screen Recorder, add them to Quick Settings.
To open AI Floating Touch, Smart boost, Task manager, Junk Cleaner and Virus scan use NEX Launcher.
Compatibility
Nokia Phones
Magisk 17+
Android 8.1.0 and above
Download from Magisk Manager.
Source code: Github[/SIZE]
Credits
@topjohnwu for Magisk
@ahrion & @Zackptg5 for Unity template and Volume Key Selector
FIH/Evenwell/HMD Global (whoever it is) for making these apps
Changelog
v1
Initial release
v1.1
Added more features - Screenshot plus, Screen Recorder, System dashboard
Added NokiaPure fonts
v1.2
Added smart boost
fixed some FCs
v1.3
Merged Pie and Oreo files into a single package
Users can now select only the files they want to install using volume keys
How to use these apps? I am unable to use the apks after downloading.
yagyanshskumar said:
How to use these apps? I am unable to use the apks after downloading.
Click to expand...
Click to collapse
The Title shows that it's a Magisk Module. Means that you need to be rooted using Magisk
Akilesh T said:
Nokia Extensions!
Module description
Why should the Chinese have all the fun?
Click to expand...
Click to collapse
Haha, great!
maybe is not working on nokia 6 with magisk root which have locked bootloader
frnsl3 said:
maybe is not working on nokia 6 with magisk root which have locked bootloader
Click to expand...
Click to collapse
I guess you are using Magisk 16.1
This module requires Magisk 17+
ZeroPointMax said:
Haha, great!
Click to expand...
Click to collapse
These features could have been added by Nokia mobile itself if they wanted to. But they decided to keep it only for China, going with "Pure stock" Android for the rest of the markets. You can say that it might reduce the speed of the updates, but China variants have been getting updates at almost the same speed as the global variants. It would have been great if they had gone with something like OOS.
Akilesh T said:
I guess you are using Magisk 16.1
This module requires Magisk 17+
Click to expand...
Click to collapse
yep so sad, able rooting but not maximum potential and soft brick too often if we modify the system
frnsl3 said:
yep so sad, able rooting but not maximum potential and soft brick too often if we modify the system
Click to expand...
Click to collapse
Magisk is systemless
Akilesh T said:
Magisk is systemless
Click to expand...
Click to collapse
not talking about magisk there, i tell you about rooting
Unable to install
I have nokia 8. When i try to install this module, it says that my decvice is pixel Xl and refuses to install. I think this is because i have installed daydream enabler module. Is there a way to bypass the device check and proceed with installing this module?
audiophile55 said:
I have nokia 8. When i try to install this module, it says that my decvice is pixel Xl and refuses to install. I think this is because i have installed daydream enabler module. Is there a way to bypass the device check and proceed with installing this module?
Click to expand...
Click to collapse
Looks like that module edited your build.prop
You can bypass it. Extract the zip. Remove the device check part in install_module function inside the config.sh file. Rezip it and flash again
Akilesh T said:
Looks like that module edited your build.prop
You can bypass it. Extract the zip. Remove the device check part in install_module function inside the config.sh file. Rezip it and flash again
Click to expand...
Click to collapse
Can you tell me exactly which lines to remove? I try removing few lines but getting the same error. I am a noob at this. BTW, i also tried deleting the entire config.sh file and still I get the same error.
EDIT: My bad. I kept flashing the original zip and not extracted zip. All good now.
audiophile55 said:
Can you tell me exactly which lines to remove? I try removing few lines but getting the same error. I am a noob at this. BTW, i also tried deleting the entire config.sh file and still I get the same error.
EDIT: My bad. I kept flashing the original zip and not extracted zip. All good now.
Click to expand...
Click to collapse
You mustn't delete config.sh file
:good:
does this module work with other android one phones? im using xiaomi a2 lite @ oreo 8.1
How can i use ai floating? . I cant find where to activate it
cbkottege said:
How can i use ai floating? . I cant find where to activate it
Click to expand...
Click to collapse
Search for "touch" in settings. There'll be a result like "Hide in do not disturb apps". That'll take you to the AI floating button' settings
Hi. I am using nokia 8. After installation module and restart, i get smart tuner and data speed indicator force close, how to fix it sir?
(Sorry for my bad english)
zeronatdo said:
Hi. I am using nokia 8. After installation module and restart, i get smart tuner and data speed indicator force close, how to fix it sir?
(Sorry for my bad english)
Click to expand...
Click to collapse
Are you using the latest version (v1.3)?