After update to 5.1.1, cannot install xpose, busybox,editing build prop, mout system... Do anyone know how to fix this??
have you root your device?
Rooted
And do not install Xposed, will result in bootloop.
My camera is like 2MP after update, now is very low, pictures are so bad....do anyone have this problem?
+1 Galaxyfreak. OP, did you try using Ric Disabler from AleksJ?
Related
I got this problem on my camera results. The color and texture of the images produce is such a big difference before capturing and after it captured. Its quite annoying and disappointing to see such images not quite good in quality after the update to lollipop. Im using a stock rom with Build number 18.6.A.0.175 and says that its my latest rom, I dont receive any OTA update such as 182.
Is there someone who can solve this problem?
Thanks!
if you don't receive update, i think you have root.
if you have root, flash this: http://forum.xda-developers.com/xpe...ashable-camera-blobs-morpho-settings-t3281766
if you haven't root, flash .182 ftf to your phone via flashtool.
Still the problem
I've alredy flash that camera file zip via recovery but nothing has change, still the results are just like using old one which is the stock camera app of. 175. Help please
sorry for my bad english ?
It does work I've flashed it myself to get the updated files. Try clearing the data from all the camera apps and wiping caches
So, all is well here, the .244 update came and it is smooth as hell, only problem is that xposed is terrorising me.
I installed every .zip xposed files possible for 6.0 and 6.0.1 all giveing me bootloops after i restart the phone...
At first i thought it was a module causing the problem, i had wiped my phone clean several times... Still...
Please help...
It did work fine for me, no issue at all... (with latest xposed v85)
can you share the zip pls
http://dl-xda.xposed.info/framework/sdk23/arm64/xposed-v85-sdk23-arm64.zip
thx, but i have found the problem. Apperantly the problem was in the kernel, i flashed the one that came with the ftf a user shared, after i flashed androPlus's kernel everything was normal
So I updated my newer Shield Tablet to 4.1, and restored everything, flashed SuperSU and Xposed and Viper4Android.. It was working fine until I enabled some Xposed modules and rebooted. It gets stuck on the NVIDIA logo and nothing happens. I got it to boot once after flashing Xposed, but the app said that Xposed was installed but not enabled ("see the logs," which made no sense to me). It said there was an update to the app, so I updated it, then downloaded the zip once again and flashed it, and got the NVIDIA logo stuck again. This is horsh!t. Why is it suddenly not working? I'm using the latest, xposed-v85-sdk23-arm zip.
Bump? Been a day and no response??
GuyInDogSuit said:
Bump? Been a day and no response??
Click to expand...
Click to collapse
Maybe nobody knows HERE?
Xposed is working here with NVIDIA-Update 1.2 (6.0.1) without problems. Did the modules you installed work before the update? A bootloop is a common problem with Xposed.
I doubt that this is ROM problem but an Xposed problem. I would try to find help in the Xposed section. Maybe you should try to find the logs...
edisso10018 said:
Maybe nobody knows HERE?
Xposed is working here with NVIDIA-Update 1.2 (6.0.1) without problems. Did the modules you installed work before the update? A bootloop is a common problem with Xposed.
I doubt that this is ROM problem but an Xposed problem. I would try to find help in the Xposed section. Maybe you should try to find the logs...
Click to expand...
Click to collapse
No, it's a ROM problem. They worked fine before.
I'm also using the 6.0.1 update and the latest xposed with no problems. I'd say it's one of your modules not being compatible, not a ROM problem at all, except that the module doesn't seem to be updated to work on mm.
Sent from my SHIELD Tablet K1 using Tapatalk
Exile1975 said:
I'm also using the 6.0.1 update and the latest xposed with no problems. I'd say it's one of your modules not being compatible, not a ROM problem at all, except that the module doesn't seem to be updated to work on mm.
Click to expand...
Click to collapse
I use the same modules on my phone running 6.0.1, with no issues. It's not a module.
did you flash arm version or arm-64 version? cuz arm-64 and intel wont work and there is a systemless xposed try using that if all else fails. I can use xposed myself on 6.0.1 myself btw.
m666p said:
did you flash arm version or arm-64 version? cuz arm-64 and intel wont work and there is a systemless xposed try using that if all else fails. I can use xposed myself on 6.0.1 myself btw.
Click to expand...
Click to collapse
As I stated in the op, it's the xposed-v85-sdk23-arm zip.
Tried reflashing the ROM, the USA LTE version this time, and I'm STILL getting stuck at the boot screen, after enabling modules. I got it to boot with JUST Xposed, no modules.
GuyInDogSuit said:
Tried reflashing the ROM, the USA LTE version this time, and I'm STILL getting stuck at the boot screen, after enabling modules. I got it to boot with JUST Xposed, no modules.
Click to expand...
Click to collapse
As stated before, a module your using isn't updated to work with our implementation of 6.0.1. now reinstall modules one at a time until you figure out which one is causing problems and then ask in the xposed section for that module. Glad you finally figured it out tho
Sent from my SHIELD Tablet K1 using Tapatalk
Exile1975 said:
As stated before, a module your using isn't updated to work with our implementation of 6.0.1. now reinstall modules one at a time until you figure out which one is causing problems and then ask in the xposed section for that module. Glad you finally figured it out tho
Click to expand...
Click to collapse
Well, it was BootManager, but it's working fine on my phone with 6.0.1.
Nope, wasn't BootManager, either. Just not working, at all.
Hi guys, here is a fix for low sound that Xiaomi "fixed" for us.
Magisk module https://www.dropbox.com/s/jvejynqlw5gz0l6/soundfix_test.zip?dl=0
MD5: 64D9A517EBDD77D7EACD087E1A33FF07
Thanks to KatsonWatson from 4pda
Hi,
Can you tell me if it's working for you (and where is this from)? My phone is not rooted etc., but I can't stand this new poor audio on a pair of high impedance earphones.
Is it installed like a module from zip via recovery?
TheDoom said:
Hi,
Can you tell me if it's working for you (and where is this from)? My phone is not rooted etc., but I can't stand this new poor audio on a pair of high impedance earphones.
Is it installed like a module from zip via recovery?
Click to expand...
Click to collapse
Install and flash Magisk and then install the module vía Magisk interface.
Magisk Is systemless so it's safe to use.
Cant tell if this module works since i still didnt update may patch but dont be afraid to try. I used this to root and install GoogleCam, no issues so far.
Just remember to follow the instructions before installing new OTAs!!
Thanks for the help! So installing this means no more OTA for me? Because I guess that any other update that comes out will bring back the crappy sound.
BTW is Google Cam a huge improvement?
TheDoom said:
Thanks for the help! So installing this means no more OTA for me? Because I guess that any other update that comes out will bring back the crappy sound.
BTW is Google Cam a huge improvement?
Click to expand...
Click to collapse
Google cam is A LOT better than stock camera.
Wysłane z mojego Mi A1 przy użyciu Tapatalka
Yup, you'll need to root and ofc use magisk (because this is magisk module) and you can't do OTAs, but for the sound that our device has, it's worth it.
Deni_NS said:
Yup, you'll need to root and ofc use magisk (because this is magisk module) and you can't do OTAs, but for the sound that our device has, it's worth it.
Click to expand...
Click to collapse
Magisk does not prevent OTA updates, as long as you know what you are doing.
To wit: 0. disable automatic OTA updates, 1. leave the stock recovery alone (TWRP can be booted into without flashing), 2. make sure to check "systemless hosts" in Magisk Manager if you use AdAway or similar, so that you don't ever write to your actual /system partition, 3. leave your phone oem-unlocked (it's OK, /data is encrypted anyway), 4. when an OTA update is available, follow instructions (can't post a proper URL yet, sorry) at github.com/topjohnwu/Magisk/blob/master/docs/tips.md
cmmike1 said:
Magisk does not prevent OTA updates, as long as you know what you are doing.
To wit: 0. disable automatic OTA updates, 1. leave the stock recovery alone (TWRP can be booted into without flashing), 2. make sure to check "systemless hosts" in Magisk Manager if you use AdAway or similar, so that you don't ever write to your actual /system partition, 3. leave your phone oem-unlocked (it's OK, /data is encrypted anyway), 4. when an OTA update is available, follow instructions (can't post a proper URL yet, sorry) at github.com/topjohnwu/Magisk/blob/master/docs/tips.md
Click to expand...
Click to collapse
Yeah, but will another OTA overwrite my Magisk Sound Fix or Google Cam?
TheDoom said:
Yeah, but will another OTA overwrite my Magisk Sound Fix or Google Cam?
Click to expand...
Click to collapse
It won't, that's what "systemless" means.
Working fine, Thanks
Wysłane z mojego Mi A1 przy użyciu Tapatalka
I'm glad to hear that [emoji4]
I can confirm that it works on my phone also. Thank you very much!
May I ask what files the module touches? Also, what did Xiaomi change in the May update to reduce the volume?
Thanks
You can unpack module and see what is changed.
thanks, but when i enable this module the mi a1 hardware keys backlight doesnt work
deewfrank said:
thanks, but when i enable this module the mi a1 hardware keys backlight doesnt work
Click to expand...
Click to collapse
Work for me
Work fine! I love it
When I try to install it via Magisk Manager, it says it's not a magisk module. I don't have custom recovery to preserve OTA, can't it be flashed through magisk somehow?
Can someone confirm if this is working with the last 8.1 update? They improved audio a little bit compared to 8.0 but its nothing compared to the nougat ROM
AceStroke said:
Can someone confirm if this is working with the last 8.1 update? They improved audio a little bit compared to 8.0 but its nothing compared to the nougat ROM
Click to expand...
Click to collapse
Work on June and July update
I'm running, 11.8.0.13 on my 8T (incl. magisk) and trying to update.
The phone claims to detect root and dowwnloads the full image.
When I try to install the OTA file "OnePlus8TOxygen_15.E.26_OTA_0260_all_2106020020_e8382.zip" it simply fails (at 0%, so before even starting to unpack).
I've tried the oneplus installer and twrp.
TWRP 3.5.2._11-0 simply shows Error 7 and install fails as well.
Unrooting didn't fix the problem with the oneplus installler.
Anyone else has this problem? Someone knows the root cause?
Did you remove any bloatware or oneplus apps?
No ... I did only install magisk .. did it work for you ?
Seems to be it detects that file is corrupted and stops installing.