I have problems with WiFi on Pie. WiFi is connected but sometimes it is inactive. It looks like some kind of deep sleep of WiFi. After couple of seconds it works again. Anyone have problems with WiFi? I know that LG is informed about that strange behaviour on Pie.
Wysłane z mojego LG-H930 przy użyciu Tapatalka
Dizzyrul3z said:
I have problems with WiFi on Pie. WiFi is connected but sometimes it is inactive. It looks like some kind of deep sleep of WiFi. After couple of seconds it works again. Anyone have problems with WiFi? I know that LG is informed about that strange behaviour on Pie.
Wysłane z mojego LG-H930 przy użyciu Tapatalka
Click to expand...
Click to collapse
Have the same problem on h932
Dizzyrul3z said:
I have problems with WiFi on Pie. WiFi is connected but sometimes it is inactive. It looks like some kind of deep sleep of WiFi. After couple of seconds it works again. Anyone have problems with WiFi? I know that LG is informed about that strange behaviour on Pie.
Wysłane z mojego LG-H930 przy użyciu Tapatalka
Click to expand...
Click to collapse
Eliejo said:
Have the same problem on h932
Click to expand...
Click to collapse
on my older h932, i had wifi problems as well with Pie roms so i flashed the modem radio found in this topic via TWRP
https://forum.xda-developers.com/lg-v30/development/stock-t-mobile-lg-v30-stock-collection-t3917560
and found that fixed my problem.
letthebeatrock said:
on my older h932, i had wifi problems as well with Pie roms so i flashed the modem radio found in this topic via TWRP
https://forum.xda-developers.com/lg-v30/development/stock-t-mobile-lg-v30-stock-collection-t3917560
and found that fixed my problem.
Click to expand...
Click to collapse
It brokes the fingerprint, how did you solve it?
Eliejo said:
It brokes the fingerprint, how did you solve it?
Click to expand...
Click to collapse
I didn't? maybe it's the ROM you are using. I did this on a liquid remix pie ROM on an older phone that was stolen from me long ago.
On my new h932 I flashed havoc 2.9 over a flashable stock Oreo and wifi seemed to work but I have the flashable modem on my sd card just in case
letthebeatrock said:
I didn't? maybe it's the ROM you are using. I did this on a liquid remix pie ROM on an older phone that was stolen from me long ago.
On my new h932 I flashed havoc 2.9 over a flashable stock Oreo and wifi seemed to work but I have the flashable modem on my sd card just in case
Click to expand...
Click to collapse
Ah I understand. In fact, the problem is on stock Pie, with custom rom there's no problem
Related
ello to al xda,, ok this is my problem
After i installed TWRP everything was ok. But when i flashed the SuperSU for root, everything worked except the camera.. It shows a sign that says that camera is busy, im not using it, i rebooted a lot of times, i cleaned the cache,, and i installed a custom kernel that was supossed to resolve that problrm.. But everything is on the same.
Can somebody help me?? Please
Im on 5.0.2
Im a new user also
Flash 5.1 stock rom
Wysłane z mojego XT1524 przy użyciu Tapatalka
blacksh4dow said:
Flash 5.1 stock rom
Wysłane z mojego XT1524 przy użyciu Tapatalka
Click to expand...
Click to collapse
My device is the xt1527 its available?
Hello everyone
who tried this firmware?
I'm going to try it tonight when I come home from work I'll be back in the day tomorrow
:good:
gismoboss13 said:
Hello everyone
who tried this firmware?
I'm going to try it tonight when I come home from work I'll be back in the day tomorrow
:good:
Click to expand...
Click to collapse
A few days ago I installed BLA-L29 8.0.0.127(C432) from funkyhuawey. I cannot remember if the particle 'a' was in the name of release. Later it did not appear on FH listing and today i see it as you mention. I don't know if mine was an early release and if it had any bugs...but I am using it with no noticeable problems!
Later I will try to flash BLA-L29 8.0.0.127a(C432) on Hisuiteand see if it is identified as a new version
Ok thanks for your come back ! I try after this FW
I installed it today. Working great.
Phone originally on purchase: BLA-L09 8.0.0.115 (C432)
Now showing: BLA-L09 8.0.0.127 (C432)
So it doesn't effect the BLA number.
Hello,
Where can we download it?
I used Funky Huawei.
Arthur Hucksake said:
I used Funky Huawei.
Click to expand...
Click to collapse
Mirror?
Enviado desde mi ONEPLUS A5000 mediante Tapatalk
https://funkyhuawei.club
sounds like a (for alpha)
virtyx said:
sounds like a (for alpha)
Click to expand...
Click to collapse
a isn't for alpha. They released 127 then fixed a bug and called it 127a internally. On the About Phone screen it might be called 127 without the a.
duraaraa said:
a isn't for alpha. They released 127 then fixed a bug and called it 127a internally. On the About Phone screen it might be called 127 without the a.
Click to expand...
Click to collapse
That's it, i had flashes previous 127 version (but no bug noticed) and now I have flashed new 127a, and on about phone sections there is no mention to 'a'
If the new firmware is approved for instalation (I found it on Huawei Firmware Finder), does it mean then that we will soon receive OTA? Sorry for the question but after 8 years with Samsung flagship phones I don't know how it looks like with Huawei[emoji6]
Wysłane z mojego BLA-L29 przy użyciu Tapatalka
kuleczka1983 said:
If the new firmware is approved for instalation (I found it on Huawei Firmware Finder), does it mean then that we will soon receive OTA?
Click to expand...
Click to collapse
I also see that installation for my IMEI is approved but there is a problem when i try to download by proxy.
edit
Managed to update through FF and proxy by using mobile data to download the update. So far so good.
@up I've watched a few tutorials on YouTube how to do it, but I'm still a little bit afraid. I prefer to install this firmware via official OTA, but I don't know how long it will take until Huawei will release it...
Wysłane z mojego BLA-L29 przy użyciu Tapatalka
i have mate 10 pro BLA-L09 8.0.0.115(C432)
and i don't see any update???
Regionella said:
i have mate 10 pro BLA-L09 8.0.0.115(C432)
and i don't see any update???
Click to expand...
Click to collapse
Use the Firmware Finder app to update! You should choose BLA-L09 8.0.0.127a (C432) FullOTA firmware and use the In-App Proxy to update (you can find the instructions in the app)
Pretoriano80 said:
Use the Firmware Finder app to update! You should choose BLA-L09 8.0.0.127a (C432) FullOTA firmware and use the In-App Proxy to update (you can find the instructions in the app)
Click to expand...
Click to collapse
Hi, I have Pro version and if I will flash FullOTA firmware via Firmware Finder I won't lose (wipe) my data?
Grigorijs said:
Hi, I have Pro version and if I will flash FullOTA firmware via Firmware Finder I won't lose (wipe) my data?
Click to expand...
Click to collapse
you won t lose your data!
Ok. I am after instalation via Firmware Finder. Everything works fine and I don't see any issues with the system. So you can easily upload that firmware straight into your phones.[emoji6]
I also don't have any issues with YouTube and Messenger now.
Wysłane z mojego BLA-L29 przy użyciu Tapatalka
İnstalled the 127 (c432) without any problem. Changed the dns and voila, firmware update appeared.
Sent from my [device_name] using XDA-Developers Legacy app
Hi guys, I just received the official Oreo OTA update.
Does Oreo require a different root method?
If so, where can I find the needed files, like twrp recovery, and so on?
Thank you for the help.
paulopcf said:
Hi guys, I just received the official Oreo OTA update.
Does Oreo require a different root method?
If so, where can I find the needed files, like twrp recovery, and so on?
Thank you for the help.
Click to expand...
Click to collapse
You can find twrp for oreo in roms and kernels section..
hassanjavaid8181 said:
You can find twrp for oreo in roms and kernels section..
Click to expand...
Click to collapse
At this moment there isn't any valid solution to root oreo in this section. Only a beta twrp with one month ago's tests and unknown functionality: https://forum.xda-developers.com/honor-9/development/beta-t3728856
Root for OREO:
https://mega.nz/#!VIlX0DSa!Am38KapbcyOhYNLcNvyLSCK9noe7WvGkWVYvl-UgYYU
Install via TWRP
kac222 said:
Root for OREO:
https://mega.nz/#!VIlX0DSa!Am38KapbcyOhYNLcNvyLSCK9noe7WvGkWVYvl-UgYYU
Install via TWRP
Click to expand...
Click to collapse
Does it work with 360a? I know you are on b321 because of the cap. buttons. But have you tried this su with 360a?
sinraal said:
Does it work with 360a?
Click to expand...
Click to collapse
Yes
Wysłane z mojego STF-L09 przy użyciu Tapatalka
Just for being sure.
1. I wil install Olddroids Oreo
2. Flash TWRP for Oreo
3. Flash this root
4. Should I keep the TWRP (and not use it as it is limited in functionality) or should I flash erecovery back?
Thanks.
kac222 said:
Root for OREO:
https://mega.nz/#!VIlX0DSa!Am38KapbcyOhYNLcNvyLSCK9noe7WvGkWVYvl-UgYYU
Install via TWRP
Click to expand...
Click to collapse
Which version of TWRP? Will the capacitive buttons and camera flash's still working?
kac222 said:
Root for OREO:
https://mega.nz/#!VIlX0DSa!Am38KapbcyOhYNLcNvyLSCK9noe7WvGkWVYvl-UgYYU
Install via TWRP
Click to expand...
Click to collapse
Maybe this is a noob question but is it possible to root without installing twrp recovery?
Because if I install twrp recovery I will probably loose the capacitive buttons and camera flash.
No,is not possible.
Wysłane z mojego STF-L09 przy użyciu Tapatalka
kac222 said:
No,is not possible.
Wysłane z mojego STF-L09 przy użyciu Tapatalka
Click to expand...
Click to collapse
Which version of TWRP? Will the capacitive buttons and camera flash's still working?
What's up Axon 7 community!
Here is the official NFC/Hotspot Universal Fix for Pie Treble!
Fixes both NFC/Hotspot on Phh v105 base roms only.
So far confirmed to be working on New Benzo and New Arrow treble roms. Test it on other treble roms and let me and @raystef66 know how it goes.
Thanks y'all.
Please give thanks to me and @raystef66 on our work.
Credits
Modified config files - @kountry83
Modified updater-script with set permissions - @raystef66
kountry83 said:
What's up Axon 7 community!
Here is the official NFC/Hotspot Universal Fix for Pie Treble!
So far confirmed to be working on New Benzo and New Arrow treble roms. Test it on other treble roms and let me and @raystef66 know how it goes.
Thanks y'all.
Please give thanks to me and @raystef66 on our work.
Credits
Modified config files - @kountry83
Modified updater-script with set permissions - @raystef66
Click to expand...
Click to collapse
Nice work bud !
This Fix could be a one of for more devices too
On OneDotOne Descendant rom this fix don't work for me. It makes NFC visible in menu but it constanly switch off if enabled.
Wysłane z mojego XT1635-02 przy użyciu Tapatalka
sebx_g1 said:
On OneDotOne Descendant rom this fix don't work for me. It makes NFC visible in menu but it constanly switch off if enabled.
Wysłane z mojego XT1635-02 przy użyciu Tapatalka
Click to expand...
Click to collapse
Rom needs to be based off of Phh v105. So it should work if dev updates to this. Hopefully this fix continues to work on future updates from Phh, or better yet he fixes it in the base.
sebx_g1 said:
On OneDotOne Descendant rom this fix don't work for me. It makes NFC visible in menu but it constanly switch off if enabled.
Wysłane z mojego XT1635-02 przy użyciu Tapatalka
Click to expand...
Click to collapse
You could try this. It's from older phh base.
sebx_g1 said:
On OneDotOne Descendant rom this fix don't work for me. It makes NFC visible in menu but it constanly switch off if enabled.
Wysłane z mojego XT1635-02 przy użyciu Tapatalka
Click to expand...
Click to collapse
Small question - Do you have an axon7??
If you flashed this on a Moto Z then please learn xda
HotSpot does work on the Axon 7 with Phh´s v105 by default.
You just have to switch to 2.4 Ghz in the HotSpot settings, since the Axon 7 doesnt support 5 Ghz HotSpot which was set by default.
Voenix said:
HotSpot does work on the Axon 7 with Phh´s v105 by default.
You just have to switch to 2.4 Ghz in the HotSpot settings, since the Axon 7 doesnt support 5 Ghz HotSpot which was set by default.
Click to expand...
Click to collapse
On some ROMs true, but the mod should set it at 2.4 GHz by default for some users that don't know to switch it. Also had devs and users from other device communities saying phh v105 base roms didn't have hotspot working at all until they flashed my fix. Aka somewhat universal.
Thanks
Nvm delete my comment
So is nfc and hotspot somehow connected because all I see in the script is nfc.
Ghost505 said:
So is nfc and hotspot somehow connected because all I see in the script is nfc.
Click to expand...
Click to collapse
The NFC lib config files I modified will tell you it interacts with P2P Protocols through transport drivers. It could interact through hw tunneling to GPS to Bluetooth. One slight little bump with file placement or script modifications could mess with the file structure and synchronization. When I was modifying the transport drivers I even managed to mess up nfc and Bluetooth at the same time lol. Got fixed though before I put it out.
Does that explain it for you a little? It's all about on some system structures interaction and making the file structure as small as possible. May benefit in some areas and may not in others.
Later
I'm on the beta rom and everytime I try to check safetynet it says "ctsprofile:false".
I tried the universal zip method but it disables the magisk root. Can someone help me about this .......
Pourush Sharan Bhargav said:
I'm on the beta rom and everytime I try to check safetynet it says "ctsprofile:false".
I tried the universal zip method but it disables the magisk root. Can someone help me about this .......
Click to expand...
Click to collapse
You choose to modify system partition in twrp when you started it for the first time my friend. That's the result. Keep read only should be your only choice when you start twrp.
Skickat från min POCOPHONE F1 via Tapatalk
How to do that. Twrp now doesn't shows any kind of option as you told???
What? If he did what you just said he wouldn't be able to flash anything. Plz don't try to help if you have no idea what you are saying, cause that's not the first time I saw that. @op try to reinstall magisk or there is module called safety net patch maybe it will help
Zeggi said:
You choose to modify system partition in twrp when you started it for the first time my friend. That's the result. Keep read only should be your only choice when you start twrp.
Skickat från min POCOPHONE F1 via Tapatalk
Click to expand...
Click to collapse
Wysłane z mojego POCOPHONE F1 przy użyciu Tapatalka
I'm not saying he can't install anything.
I'm explaining why safetynet fails.
Reinstall boot.img and it will solve the issue.
But since twrp modified system partition magisk won't solve it.
You could try the following and see if it helps you, check first post for instructions, https://forum.xda-developers.com/on...agisk-17-2-canary-channel-acess-t3840497/amp/
If it doesn't help I would recommend to reinstall rom, when you start twrp don't swipe at first boot just press "keep system read only."
Skickat från min POCOPHONE F1 via Tapatalk
---------- Post added at 10:23 PM ---------- Previous post was at 10:19 PM ----------
uremytoy said:
What? If he did what you just said he wouldn't be able to flash anything. Plz don't try to help if you have no idea what you are saying, cause that's not the first time I saw that. @op try to reinstall magisk or there is module called safety net patch maybe it will help
Wysłane z mojego POCOPHONE F1 przy użyciu Tapatalka
Click to expand...
Click to collapse
You are in the wrong. Please read some and learn how partitions work and what twrp does when you allow it to modify partitions. He clearly gets safetynet failure because system has been changed. Since he is running magisk he clearly wants the phone to run system less which is the whole point of using magisk...
Your claim is pure smack.
Skickat från min POCOPHONE F1 via Tapatalk
Zeggi said:
[/COLOR]You are in the wrong. Please read some and learn how partitions work and what twrp does when you allow it to modify partitions. He clearly gets safetynet failure because system has been changed. Since he is running magisk he clearly wants the phone to run system less which is the whole point of using magisk...
Your claim is pure smack.
Skickat från min POCOPHONE F1 via Tapatalk
Click to expand...
Click to collapse
So if i keep the system read only, can i flash magisk zip in twrp and will CTS passes?
uremytoy said:
What? If he did what you just said he wouldn't be able to flash anything. Plz don't try to help if you have no idea what you are saying, cause that's not the first time I saw that. @op try to reinstall magisk or there is module called safety net patch maybe it will help
Wysłane z mojego POCOPHONE F1 przy użyciu Tapatalka
Click to expand...
Click to collapse
Same issue
Solved this finally by switching from MIUI 10 Beta to Xiaomi.EU rom and I am in love with this ROM....
Safetynet passed by default
I've Miui 10 (beta rom) Bootloader lock and non modified / root device and cts failed. I think we need to report to pocophone
FieryAura said:
I've Miui 10 (beta rom) Bootloader lock and non modified / root device and cts failed. I think we need to report to pocophone
Click to expand...
Click to collapse
If your bootloader is still locked please report this issue to Xiaomi/Poco team on their forum as well as on tweeter.
I discovered this issue a long ago but since my bootloader was unlocked i though it's due to that only.
but if it the same with locked boot loader definitely this is big issue from POCO side and need to be addressed ASAP.
PS: SafetyNet Passes on Xiaomi.EU roms because they use different device's (Polaris-MI Mix 2s) "fingureprint" (i.e device name used while registering on playstore) rather than POCO's (Beryllium)
read more here...https://forum.xda-developers.com/showpost.php?p=77876668&postcount=113
Do point this out when you raise the issue to POCO team so they can track the issue faster
jineshpatel30 said:
If your bootloader is still locked please report this issue to Xiaomi/Poco team on their forum as well as on tweeter.
I discovered this issue a long ago but since my bootloader was unlocked i though it's due to that only.
but if it the same with locked boot loader definitely this is big issue from POCO side and need to be addressed ASAP.
PS: SafetyNet Passes on Xiaomi.EU roms because they use different device's (Polaris-MI Mix 2s) "fingureprint" (i.e device name used while registering on playstore) rather than POCO's (Beryllium)
read more here...https://forum.xda-developers.com/showpost.php?p=77876668&postcount=113
Do point this out when you raise the issue to POCO team so they can track the issue faster
Click to expand...
Click to collapse
Yes, i've reported this on twitter to poco. I hope a quick fix
jineshpatel30 said:
If your bootloader is still locked please report this issue to Xiaomi/Poco team on their forum as well as on tweeter.
I discovered this issue a long ago but since my bootloader was unlocked i though it's due to that only.
but if it the same with locked boot loader definitely this is big issue from POCO side and need to be addressed ASAP.
PS: SafetyNet Passes on Xiaomi.EU roms because they use different device's (Polaris-MI Mix 2s) "fingureprint" (i.e device name used while registering on playstore) rather than POCO's (Beryllium)
read more here...https://forum.xda-developers.com/showpost.php?p=77876668&postcount=113
Do point this out when you raise the issue to POCO team so they can track the issue faster
Click to expand...
Click to collapse
Good thoughts.
I will raise this issue on beta tester page and try to raise a bug report.
FieryAura said:
Yes, i've reported this on twitter to poco. I hope a quick fix
Click to expand...
Click to collapse
sanjay0501 said:
Good thoughts.
I will raise this issue on beta tester page and try to raise a bug report.
Click to expand...
Click to collapse
Great.
I would have done it my self but i'm short on time now a days.