Related
Edit: Lockscreen.apk and odex deleted with TWRP file manager (mount system before). V4a issue still there, even installing apk through TWRP as flashable zip.
Hi, I was trying to install viper4android on my device. The application is installed successfully, but I can't install drivers. After reboot the app asks me again to install drivers. I also tried to get stock android lockscreen deleting HTC lockscreen.apk. Successfully deleted, but present again after reboot. Should I need s-off to do that? With other models I did this without s-off. Indeed with soft reset, I get the Android stock lockscreen, but with a complete reboot I get the sense one again. Any idea or I just have to wait for a way to s-off?
Sent from my HTC One mini 2 using XDA Free mobile app
Edit: solved
gibihr said:
Edit: Lockscreen.apk and odex deleted with TWRP file manager (mount system before). V4a issue still there, even installing apk through TWRP as flashable zip.
Hi, I was trying to install viper4android on my device. The application is installed successfully, but I can't install drivers. After reboot the app asks me again to install drivers. I also tried to get stock android lockscreen deleting HTC lockscreen.apk. Successfully deleted, but present again after reboot. Should I need s-off to do that? With other models I did this without s-off. Indeed with soft reset, I get the Android stock lockscreen, but with a complete reboot I get the sense one again. Any idea or I just have to wait for a way to s-off?
Sent from my HTC One mini 2 using XDA Free mobile app
Edit: solved
Click to expand...
Click to collapse
Any hint on how did you solved that ? I'd like the original lockscreen aswell
JuJuBoSc said:
Any hint on how did you solved that ? I'd like the original lockscreen aswell
Click to expand...
Click to collapse
You need TWRP recovery
Take backup (you'll never know what can happen)
Boot into recovery > mount > pick system
go back to the main menu, advanced > file manager
You'll find HtcLockScreen.apk and HtcLockScreen.odex in system/priv-app
I deleted them and voilà! No more sense 6 Locksreen, stock android.
gibihr said:
Edit: Lockscreen.apk and odex deleted with TWRP file manager (mount system before). V4a issue still there, even installing apk through TWRP as flashable zip.
Hi, I was trying to install viper4android on my device. The application is installed successfully, but I can't install drivers. After reboot the app asks me again to install drivers. I also tried to get stock android lockscreen deleting HTC lockscreen.apk. Successfully deleted, but present again after reboot. Should I need s-off to do that? With other models I did this without s-off. Indeed with soft reset, I get the Android stock lockscreen, but with a complete reboot I get the sense one again. Any idea or I just have to wait for a way to s-off?
Sent from my HTC One mini 2 using XDA Free mobile app
Edit: solved
Click to expand...
Click to collapse
Are there no flashable drivers for Viper4Android like the rSAP app has?
tomatende2001 said:
Are there no flashable drivers for Viper4Android like the rSAP app has?
Click to expand...
Click to collapse
Yes, but nothing happened, same result...
Are you sure? The rSAP App runs fine after flashing the drivers via TWRP.
tomatende2001 said:
Are you sure? The rSAP App runs fine after flashing the drivers via TWRP.
Click to expand...
Click to collapse
Yes I am.. All the other mods work, except for this...
Where you found the flashable version of the app and drivers?
tomatende2001 said:
Where you found the flashable version of the app and drivers?
Click to expand...
Click to collapse
Link removed - not official version, sorry
But this is not a official version! This zip overwrite your audio configuration! Be carefully. I repaired it with the files from the "big" M8. Runs better than ever.
tomatende2001 said:
But this is not a official version! This zip overwrite your audio configuration! Be carefully. I repaired it with the files from the "big" M8. Runs better than ever.
Click to expand...
Click to collapse
There was somewhere in the official thread in the faq a question like "i can't install it anyway? Then try with the flashable zip", it's the same zip that I posted.. Sorry, I'll give you the right link as soon as I find it... but as you solved it anyway,how did you do it?
After I repaired my phone, I never would like to use this app.
And then installed v4a? As normal app?
No, after this repair I was happy that my phone works again. Until there is no official ROM that I can flash or where I can extract the original files, I do not make any change on my phone again!
Confirmed - it's a problem caused by HTC's system write protection. Liberty Kernel solved the issue with viper4android.
But you need a new kernel. With the Android rSAP App you can create a flashable driver ZIP, I think this is the better way to install drivers for an App. They also create a uninstall ZIP.
tomatende2001 said:
But you need a new kernel. With the Android rSAP App you can create a flashable driver ZIP, I think this is the better way to install drivers for an App. They also create a uninstall ZIP.
Click to expand...
Click to collapse
I couldnt find drivers for v4a, i reflashed stock kernel after installing drivers, the problem was indeed system write, no incompatiblity or stuff like that the app is now installed and finally fully working!
I am happy with the write protection, because you never know, what the "driver installation" changed on your system. In a zip I can take a look about the modification and for example with the rSAP app I KNOW, that I can deinstall all modifications. But I dont know anything about Viper4Android. So I have to look for another DSP manager ...
Tried installing the Google Keyboard 5.0 apk on N Preview 2 and it says it's corrupt. I assume this is because it's baked into the system ROM.
I guess I could wait until it updates in the PlayStore, I but has anyone found or made a flashable zip for installing?
KeepingItCuttingEdge said:
Tried installing the Google Keyboard 5.0 apk on N Preview 2 and it says it's corrupt. I assume this is because it's baked into the system ROM.
I guess I could wait until it updates in the PlayStore, I but has anyone found or made a flashable zip for installing?
Click to expand...
Click to collapse
Tried re-downloading and reinstalling that apk?
The available apk file does not work on Android N.
Candy[MAN said:
The available apk file does not work on Android N.
Click to expand...
Click to collapse
Can you elaborate? I am surprised no one else has pointed this out...
Thanks
KeepingItCuttingEdge said:
Can you elaborate? I am surprised no one else has pointed this out...
Thanks
Click to expand...
Click to collapse
android n keyboard has a target of sdk higher than marshmallow. it wont work. but good news. google released the keyboard to market.
edit: if you dont get the update from market you can install this one:
http://www.apkmirror.com/apk/google-inc/google-keyboard/google-keyboard-5-0-18-121010836-release/
make sure you dont install the arm64 one. that will also cause an issue.
SynisterWolf said:
android n keyboard has a target of sdk higher than marshmallow. it wont work. but good news. google released the keyboard to market.
edit: if you dont get the update from market you can install this one:
http://www.apkmirror.com/apk/google-inc/google-keyboard/google-keyboard-5-0-18-121010836-release/
make sure you dont install the arm64 one. that will also cause an issue.
Click to expand...
Click to collapse
That's the one I've tried since beginning that it says is 'corrupt'.
That link worked for me. Thanks!
Sent from my Nexus 6 using XDA-Developers mobile app
KeepingItCuttingEdge said:
That's the one I've tried since beginning that it says is 'corrupt'.
Click to expand...
Click to collapse
Same here
If you guys want to install this on your Nexus 6 running N Developer Preview 2
1. Root your device
2. Install 3rd Party Keyboard
3. Uninstall Google Keyboard via Titanium Backup
4. Install Google Keyboard 5.0
5. Uninstall 3rd party Keyboard (optional)
6. Reboot
benleonheart said:
If you guys want to install this on your Nexus 6 running N Developer Preview 2
1. Root your device
2. Install 3rd Party Keyboard
3. Uninstall Google Keyboard via Titanium Backup
4. Install Google Keyboard 5.0
5. Uninstall 3rd party Keyboard (optional)
6. Reboot
Click to expand...
Click to collapse
This kinda worked. I had to reboot after uninstalling Google Keyboard. Then it allowed me to install without stating the file was corrupt. Thanks for the suggestion though.
fhblake04 said:
This kinda worked. I had to reboot after uninstalling Google Keyboard. Then it allowed me to install without stating the file was corrupt. Thanks for the suggestion though.
Click to expand...
Click to collapse
Just FYI, this will probably break the OTA update to N preview 3 that will be out this month.
benleonheart said:
If you guys want to install this on your Nexus 6 running N Developer Preview 2
1. Root your device
2. Install 3rd Party Keyboard
3. Uninstall Google Keyboard via Titanium Backup
4. Install Google Keyboard 5.0
5. Uninstall 3rd party Keyboard (optional)
6. Reboot
Click to expand...
Click to collapse
ACastanza said:
Just FYI, this will probably break the OTA update to N preview 3 that will be out this month.
Click to expand...
Click to collapse
Not in N OTA.
When I had my Nexus 5 people would make flashable OTA files to be used in TWRP, is no one doing this any longer? All I can find is how to sideload the OTA.
Thanks
idbl_fanatic said:
When I had my Nexus 5 people would make flashable OTA files to be used in TWRP, is no one doing this any longer? All I can find is how to sideload the OTA.
Thanks
Click to expand...
Click to collapse
just flash the boot.img and system.img in twrp. if you had root, youll need to reroot. yes, twrp flashes system.img and boot.img files now as well.
simms22 said:
just flash the boot.img and system.img in twrp. if you had root, youll need to reroot. yes, twrp flashes system.img and boot.img files now as well.
Click to expand...
Click to collapse
WOW thank you, I didn't know that TWRP did this.
simms22 said:
just flash the boot.img and system.img in twrp. if you had root, youll need to reroot. yes, twrp flashes system.img and boot.img files now as well.
Click to expand...
Click to collapse
Ok, I am a little confused, I am trying to apply the MRA58K from LMY48T OTA found here: http://forum.xda-developers.com/nexus-6/general/ref-nexus-6-stock-ota-urls-t2906493 in the ZIP file, I am not finding system.img, or boot.img
Download the factory images and extract the system and boot.imgs,put them on your SD card(phone storage) enter twrp,select install,then select images in bottom right, select the partition you want to flash to, select the correct.img file
Sent from my Nexus 6 using XDA-Developers mobile app
holeindalip said:
Download the factory images and extract the system and boot.imgs,put them on your SD card(phone storage) enter twrp,select install,then select images in bottom right, select the partition you want to flash to, select the correct.img file
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
Just want to double check, this will be ok to do giong from 5.1.1 to 6.0.1?
idbl_fanatic said:
Just want to double check, this will be ok to do giong from 5.1.1 to 6.0.1?
Click to expand...
Click to collapse
yup
simms22 said:
yup
Click to expand...
Click to collapse
Ok, so, I got my phone updates, however, I had systemless xposed working on it, MM 6.0.1 (MOB30M) however when I went in to try and enable the modules, it gave an error (a long one) so I thought that maybe I didn't have the correct version installed, or wasn't rooted right, so I went back into recovery, re-rooted, and installed 85.3, now it says that xposed isn't installed at all. So for now, I went back to my 5.1.1 restore. Any ideas?
idbl_fanatic said:
Ok, so, I got my phone updates, however, I had systemless xposed working on it, MM 6.0.1 (MOB30M) however when I went in to try and enable the modules, it gave an error (a long one) so I thought that maybe I didn't have the correct version installed, or wasn't rooted right, so I went back into recovery, re-rooted, and installed 85.3, now it says that xposed isn't installed at all. So for now, I went back to my 5.1.1 restore. Any ideas?
Click to expand...
Click to collapse
You have to reflash xposed. It is in the system partition so you will have to redo it after making room as google now fills up the system partition almost completely.
zelendel said:
You have to reflash xposed. It is in the system partition so you will have to redo it after making room as google now fills up the system partition almost completely.
Click to expand...
Click to collapse
I thought that was the whole reason behind the System Less Xposed, so it doesn't install to your system partition.
idbl_fanatic said:
I thought that was the whole reason behind the System Less Xposed, so it doesn't install to your system partition.
Click to expand...
Click to collapse
was the systemless updated to work with the new security measures built into the update? You have to remember that with each update google is making things like xposed harder to get working. It is well known that sooner or later xposed all together will no longer be an option.
So I would check all the changes that the update did to see what it changed. I nor most the people I know have not used xposed in a long time so I really cant say for sure
zelendel said:
was the systemless updated to work with the new security measures built into the update? You have to remember that with each update google is making things like xposed harder to get working. It is well known that sooner or later xposed all together will no longer be an option.
So I would check all the changes that the update did to see what it changed. I nor most the people I know have not used xposed in a long time so I really cant say for sure
Click to expand...
Click to collapse
That makes sense, maybe I'll go to MMB29K instead.
Systemless root or systemless exposed?
Sent from my Nexus 6 using XDA-Developers mobile app
I have systemless xposed working on mob30m. currently have v85.2 installed, all modules working. Only hiccup i ran into was the installer apk. you have to use the one linked in the systemless xposed thread, or it won't recognize the framework is installed.
putridfoetus said:
I have systemless xposed working on mob30m. currently have v85.2 installed, all modules working. Only hiccup i ran into was the installer apk. you have to use the one linked in the systemless xposed thread, or it won't recognize the framework is installed.
Click to expand...
Click to collapse
Thank you, I just reinstalled 6.0.1 MOB30M and it works!
I'm on 6.0 right now with TW recovery, root with SuperSU and Xposed v85, I want to go to 6.0.1 latest version, what would be the best was to do it?
Shall I uninstall xposed, unroot and get stock recovery and then just try to install OTA or is there another way?
cL0uD` said:
I'm on 6.0 right now with TW recovery, root with SuperSU and Xposed v85, I want to go to 6.0.1 latest version, what would be the best was to do it?
Shall I uninstall xposed, unroot and get stock recovery and then just try to install OTA or is there another way?
Click to expand...
Click to collapse
Check out Flashfire in the appstore, it let's you update with OTA, and re-root
idbl_fanatic said:
Check out Flashfire in the appstore, it let's you update with OTA, and re-root
Click to expand...
Click to collapse
Yes, used, Great job, Mr Chainfire
Hi, I've a short query, is the Nexus launcher built-in in the Android 7? I've used Nexus launcher leaked version and it is awesome, liked it a lot.just wondering if it comes with final Android build?
It's been rebranded Pixel launcher and will be exclusive to the new Pixel phones (officially) however I'm sure there will be ways to circumvent this.
I have a TWRP flashable version of it, with the new wallpaper app. You can set different lock and home screen wallpapers.
https://www.dropbox.com/s/9bs6rjw237p272k/PixelLauncher7.1.zip?dl=0
Anyone else having issues installing. I have tried to install since we recieved the official Android N update with no luck. I tried the nexus launcher as well as the pixel launcher. I even tried different versions of twrp and does the same thing. It says install was successful, but when phone is rebooted, the launcher is not installed
fiftiey5o said:
Anyone else having issues installing. I have tried to install since we recieved the official Android N update with no luck. I tried the nexus launcher as well as the pixel launcher. I even tried different versions of twrp and does the same thing. It says install was successful, but when phone is rebooted, the launcher is not installed
Click to expand...
Click to collapse
Funny thing, it doesn't seem to be a System/Home option. I flashed mine, and had to choose at reboot, but I don't see if I could change it back (not that I want to).
Edit: Okay, it's not under System/home any more, but in System/Apps, tap the settings gear.
That's what I was thinking as well. But unfortunately it does not even show up there. I am at a lost. Strange part was I had no issues on the developers preview
Also would like to mention, I even flashed the one from the link you provided. It flashes fine in two with no errors, but it does not install.
The update after dp5 is kinda fishy, it seems. Some have problems with the radio. I did a clean flash, then added SuperSu and the Pixel launcher, and it worked for me.
Yes that what i was thinking. I did not really want to root the phone. Which version of the root are you using?
SuperSu 1.78
Just asking out of curiosity. Why that version. I have not used superuser for a while, which is why i am asking. I see SuperrSu is at version 2.78?
Sorry, typo, it's the 2.78.
Just had a chance to flash it.... and it is working. That is pretty strange to say the least.
Is it worth flashing it? Just made a clean install of Stock NPD90 and didn't flash TWRP yet
yeticomes said:
Is it worth flashing it? Just made a clean install of Stock NPD90 and didn't flash TWRP yet
Click to expand...
Click to collapse
Not really. It's just a launcher with no extra features. Unless you count the ability to set different wallpapers for the lock screen and the home screen a feature.
But it looks cool, and you get an extra fixed icon on the bottom.
istperson said:
Not really. It's just a launcher with no extra features. Unless you count the ability to set different wallpapers for the lock screen and the home screen a feature.
But it looks cool, and you get an extra fixed icon on the bottom.
Click to expand...
Click to collapse
So now advantage regarding the usage of Google Assistant from this launcher?
Nothing more than Google Tap already did.
fiftiey5o said:
Just had a chance to flash it.... and it is working. That is pretty strange to say the least.
Click to expand...
Click to collapse
So the launcher only works after flashing SuperSu? Just installed the Pixel Launcher via twrp but it doesn't show up
That was the only way I was able to get both the pixel and Nexus launcher to work on stock.
Obviously a mistype... V2.78r1 is the latest.
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Edit: sorry, I see that I was responding to an old post, but the link may be useful anyway.
I saw in an XDA-TV video that you are supposed to be able to either display the clock or weather on the home screen. Has anyone found a way to switch it? I'm thinking it might only be a feature with the Pixel launcher on the Pixel phones.
As title says, I just upgraded to Oreo with OTA and I can't answer calls.
I can hear the phone ringing but nothing is displayed to accept/refuse the call.
I also tried using Google Dialer as a replacemente but nothing appears there too.
Dialer is present in the apps, and I can use it normally if opened. But even if I start a call from there I can't close it because the screen with the running call (the one with image and bottom keys for speakers, etc) is not appearing at all.
Phone is rooted with Magisk and TWRP.
Keeping your data intact please try to flash the full OOS 5.0 rom. OTA update might have screwed the system.
lontu said:
Keeping your data intact please try to flash the full OOS 5.0 rom. OTA update might have screwed the system.
Click to expand...
Click to collapse
I tried again with Google Dialer and it's working. So it's a problem with stock dialer. Can anyone send me the stock dialer APK from OOS 5?
Are you by any chance using the 'Enable Native Call Recording' module in magisk? If yes, then get rid of that.
fluster84 said:
Are you by any chance using the 'Enable Native Call Recording' module in magisk? If yes, then get rid of that.
Click to expand...
Click to collapse
No, I knew that already. I only have the default ones that come with magisk (auto_mount, system, module.prop, update).
I think I just need to reinstall the stock dialer, but can't find the APK and I don't know how to extract it from the full zip system image.
I'll keep the google dialer in the meantime.
matrixino said:
No, I knew that already. I only have the default ones that come with magisk (auto_mount, system, module.prop, update).
I think I just need to reinstall the stock dialer, but can't find the APK and I don't know how to extract it from the full zip system image.
I'll keep the google dialer in the meantime.
Click to expand...
Click to collapse
Try to clear dialer data. It same as reinstall
Im having the same issue, so let me know if you figure out the solution.
No problems should be there after upgrade.
This shows a problematic Oreo setup.
Better have a factory reset so all apps will be installed correctly.
Sent from my i15-TCL using Tapatalk
Did you guys solve the problem?
I'm having the same problem and have enabled call recording using magisk. I tried upgrading to 5.0.2 and still the same. Please advice.