I was able to flash the rooted boot.img, but it seems to have caused a problem with the fingerprint sensor. It works a little after a fresh reboot, but then it stops working completely. Anyone have an idea as to why and maybe how I can fix it?
i have the same problem, you fix it?
Probably, incompatible Boot
Try flash stock Boot back and check Fingerprint
5[Strogino] said:
Probably, incompatible Boot
Try flash stock Boot back and check Fingerprint
Click to expand...
Click to collapse
yeah, but we dont have the stock boot, we have tha us version c567 and its not online yet
Same problem
Abumarf said:
I was able to flash the rooted boot.img, but it seems to have caused a problem with the fingerprint sensor. It works a little after a fresh reboot, but then it stops working completely. Anyone have an idea as to why and maybe how I can fix it?
Click to expand...
Click to collapse
Hi Abumarf and depooltrd,
I have the same symptoms. I've flashed boot.img from C432 (rooted now) to my C567. It was the only way to unbrick it.
What region is rooted boot.img you flashed from. Do you think it is a software problem, not a hardware one?
Also, could anyone who has rooted MHA-L29C567B138 confirm that the fingerprint sensor works fine?
night_wind said:
Hi Abumarf and depooltrd,
I have the same symptoms. I've flashed boot.img from C432 (rooted now) to my C567. It was the only way to unbrick it.
What region is rooted boot.img you flashed from. Do you think it is a software problem, not a hardware one?
Also, could anyone who has rooted MHA-L29C567B138 confirm that the fingerprint sensor works fine?
Click to expand...
Click to collapse
I'm not sure as to what region I flashed but I can guarantee you it's a software problem. After checking the System/Bin/ it was clear that the fingerprintID folder and a few others were missing. This is most likely what causes the Fingerprint sensor to no longer work. All we can do is wait for Huawei to release the complete C567 update so we can revert to complete stock.
Abumarf said:
I can guarantee you it's a software problem. After checking the System/Bin/ it was clear that the fingerprintID folder and a few others were missing.
Click to expand...
Click to collapse
That is promising. So did you notice these problems right after you had flashed the boot.img?
BTW, it could work for hours after a fresh restart for me. What about yours?
night_wind said:
That is promising. So did you notice these problems right after you had flashed the boot.img?
BTW, it could work for hours after a fresh restart for me. What about yours?
Click to expand...
Click to collapse
Yes, as soon as I flashed both boot images that I had. One with root and the other with stock. I asked around and a dev buddy of mine told me that the KangVIP root isn't always interchangeable with the non-KangVIP roms. It was the same case for the Mate 8. Mine works for a few minutes at most, but I did flash an unknown stock boot image though it did nothing. It's a pain to live without a fingerprint sensor
Abumarf said:
Yes, as soon as I flashed both boot images that I had. One with root and the other with stock. I asked around and a dev buddy of mine told me that the KangVIP root isn't always interchangeable with the non-KangVIP roms. It was the same case for the Mate 8. Mine works for a few minutes at most, but I did flash an unknown stock boot image though it did nothing. It's a pain to live without a fingerprint sensor
Click to expand...
Click to collapse
I've just ran into this same issue, you think someone could just upload the missing files?
posydon1 said:
I've just ran into this same issue, you think someone could just upload the missing files?
Click to expand...
Click to collapse
I don't think so but I think there may be some hope. Ajsmsg78 released a full root and encryption guide (https://forum.xda-developers.com/mate-9/development/root-root-mate-9-t3556590) which I'm going to try from the complete beginning later to see if it'll restore functionality.
Abumarf said:
I don't think so but I think there may be some hope. Ajsmsg78 released a full root and encryption guide (https://forum.xda-developers.com/mate-9/development/root-root-mate-9-t3556590) which I'm going to try from the complete beginning later to see if it'll restore functionality.
Click to expand...
Click to collapse
That's exactly how I ended up here lol. His method works great but some file are still missing.
posydon1 said:
That's exactly how I ended up here lol. His method works great but some file are still missing.
Click to expand...
Click to collapse
Then we may be stuck until Huawei releases the C567 update. It's pretty disappointing that we seem to be the only version without an update even after almost a month and a half from release. :crying:
Abumarf said:
Then we may be stuck until Huawei releases the C567 update. It's pretty disappointing that we seem to be the only version without an update even after almost a month and a half from release. :crying:
Click to expand...
Click to collapse
Hey Abumarf,
Looks like Huawei released the new MHA-L29C567B167 and also decrypted-boot-MHA-L29C567B138.img has appeared as well. Did you try to flash any of them? Did it fix the fingerprint sensor?
night_wind said:
Hey Abumarf,
Looks like Huawei released the new MHA-L29C567B167 and also decrypted-boot-MHA-L29C567B138.img has appeared as well. Did you try to flash any of them? Did it fix the fingerprint sensor?
Click to expand...
Click to collapse
No I haven't as of yet. I've been trying to download the C567B167 OTA through Firmware Finder but it wasn't working for me. I also haven't had much time to look into it. If you or anyone else do end up trying either of the solutions, please let me know.
Abumarf said:
No I haven't as of yet. I've been trying to download the C567B167 OTA through Firmware Finder but it wasn't working for me. I also haven't had much time to look into it. If you or anyone else do end up trying either of the solutions, please let me know.
Click to expand...
Click to collapse
I tried decrypted-boot-MHA-L29C567B138.img and it fixed the fingerprint sensor, but I didn't manage to restore data partitions and the ROM wasn't full. Finally, I updated through FunkyHuawei and everything works fine now.
night_wind said:
I tried decrypted-boot-MHA-L29C567B138.img and it fixed the fingerprint sensor, but I didn't manage to restore data partitions and the ROM wasn't full. Finally, I updated through FunkyHuawei and everything works fine now.
Click to expand...
Click to collapse
I also did just that but just fixed the problem with the Huawei apps and system update by changing a few file names. Works like a charm now. Will wait till Monday and attempt to flash the B167 update. But as of now, I'm fully root, decrypted, and enjoying life!
Related
I had an OTA update available this morning. It's only 51.3 MB so it can't be anything major. Maybe a stagefright fix? Anyway, I pulled it just in case anyone wants to check it out. I'm already on D80130B. I'm rooted with TWRP. Is there any easy way to install it without losing TWRP?
Here's the link for it: https://www.dropbox.com/s/5ast6zoe514ikjk/update.zip?dl=0
Is it 878 TMO/T-MOBILE(USA) V30c?
D80130c_00.kdz is 1.05 GiB as usual.
trickinit said:
I had an OTA update available this morning. It's only 51.3 MB so it can't be anything major. Maybe a stagefright fix? Anyway, I pulled it just in case anyone wants to check it out. I'm already on D80130B. I'm rooted with TWRP. Is there any easy way to install it without losing TWRP?
Here's the link for it: https://www.dropbox.com/s/5ast6zoe514ikjk/update.zip?dl=0
Click to expand...
Click to collapse
I thought stagefright fix too so I let it go for the heck of it. It installed fine and I didn't seem to lose root or anything. I ran a stagefright test and only 2 are blocked which I think is what it told me a couple months ago. I didn't see any obvious changes.
ApokrifX said:
Is it 878 TMO/T-MOBILE(USA) V30c?
D80130c_00.kdz is 1.05 GiB as usual.
Click to expand...
Click to collapse
I don't think that's it as it's only 51.3 MB. What's new in V30C?
qqq1 said:
I thought stagefright fix too so I let it go for the heck of it. It installed fine and I didn't seem to lose root or anything. I ran a stagefright test and only 2 are blocked which I think is what it told me a couple months ago. I didn't see any obvious changes.
Click to expand...
Click to collapse
Do you have a custom recovery? I tried flashing it in TWRP but it failed.
trickinit said:
Do you have a custom recovery? I tried flashing it in TWRP but it failed.
Click to expand...
Click to collapse
I do. I just ran it right from my running phone. I was in the middle of some work so I wasn't watching it but as far as I know it installed fine. If I check for updates now it says there are none, up to date.
Just tried to install the OTA (51.3 MB).
Phone rebooted, tried to install it and showed error.
Have to hold power button quite sometime to reboot the phone.
ApokrifX said:
Just tried to install the OTA (51.3 MB).
Phone rebooted, tried to install it and showed error.
Have to hold power button quite sometime to reboot the phone.
Click to expand...
Click to collapse
That's the same thing that happened with me. I just got the notification for the update again today.
Sorry, I was wrong about mine getting installed. Like I said was busy with work so I kinda assumed it all went though fine. Still no idea what this is?
qqq1 said:
Sorry, I was wrong about mine getting installed. Like I said was busy with work so I kinda assumed it all went though fine.
Click to expand...
Click to collapse
Looks like nobody got installed?
qqq1 said:
Still no idea what this is?
Click to expand...
Click to collapse
Once it went through for somebody, he can tell us!
I noticed that it fixed all but one stage fright vulnerability.
I also just realized that it patched many of the current root solutions.
lesterf said:
I noticed that it fixed all but one stage fright vulnerability.
I also just realized that it patched many of the current root solutions.
Click to expand...
Click to collapse
Oh really? So you lost root then?
I just switched to TMO and got a refurb LG G2 a couple of weeks ago. I stupidly took the OTA before rooting and then realized that many of the root exploits didn't work afterwards. Thanks to the brilliant devs at XDA, I did find a method that works: http://forum.xda-developers.com/lg-g3/general/guide-root-method-lg-devices-t3129197
I'm a happy camper running CM 12.1 now!
I am half tempted to unroot using SuperSU unroot tool, see if I can apply the patch and see what happens... or has anyone tried this yet?
djmcho said:
I am half tempted to unroot using SuperSU unroot tool, see if I can apply the patch and see what happens... or has anyone tried this yet?
Click to expand...
Click to collapse
I'm not sure that would work. Being rooted doesn't usually prevent the manual installation of updates. The problem is whether or not you have a custom recovery. I believe the OTA needs the stock recovery to install.
so.. anybody found solution how to install?
galets said:
so.. anybody found solution how to install?
Click to expand...
Click to collapse
I never did. I ended up just blocking the notification.
trickinit said:
I never did. I ended up just blocking the notification.
Click to expand...
Click to collapse
but... f-ing stage fright bug!!!
galets said:
but... f-ing stage fright bug!!!
Click to expand...
Click to collapse
I know. I guess I'll just have to be careful.
trickinit said:
I know. I guess I'll just have to be careful.
Click to expand...
Click to collapse
How did you block notification?
I need the stock boot image to flash onto my mate 9. The rooted one from KangVIP messed up a few things that I don't think root is worth. Any help is appreciated.
Abumarf said:
I need the stock boot image to flash onto my mate 9. The rooted one from KangVIP messed up a few things that I don't think root is worth. Any help is appreciated.
Click to expand...
Click to collapse
Out of curiosity, what messed up?
Download the ur current firmware and extract boot.img.
ante0 said:
Out of curiosity, what messed up?
Click to expand...
Click to collapse
The fingerprint sensor no longer works, except for a short period of time after a reboot. The Fingerprint I'd settings crash whenever I try to enter them.
@ante0 @gm007 thanks for the help. I flashed the boot image and it worked. Now completely stock
Abumarf said:
@ante0 @gm007 thanks for the help. I flashed the boot image and it worked. Now completely stock
Click to expand...
Click to collapse
Man i have the same problem with the fingerprint, can you help me?
depooltrd said:
Man i have the same problem with the fingerprint, can you help me?
Click to expand...
Click to collapse
Download Huawei Update Extractor: https://forum.xda-developers.com/showthread.php?t=2433454
Check Settings in your phone to see what firmware you're on and download from the links below.
MHA-L29: http://hwmt.ru/oth/HWFF/info/view.php?find_model=MHA-L29
MHA-L09: http://hwmt.ru/oth/HWFF/info/view.php?find_model=MHA-L09
MHA-AL00: http://hwmt.ru/oth/HWFF/info/view.php?find_model=MHA-AL00
MHA-TL01 :http://hwmt.ru/oth/HWFF/info/view.php?find_model=MHA-TL01
Extract your downloaded firmware then use Huawei Update Extractor and open update.app in it.
Rightclick on BOOT.IMG and select Extract.
Then use TWRP or fastboot to flash it to boot.
ante0 said:
Download Huawei Update Extractor: https://forum.xda-developers.com/showthread.php?t=2433454
Check Settings in your phone to see what firmware you're on and download from the links below.
MHA-L29: http://hwmt.ru/oth/HWFF/info/view.php?find_model=MHA-L29
MHA-L09: http://hwmt.ru/oth/HWFF/info/view.php?find_model=MHA-L09
MHA-AL00: http://hwmt.ru/oth/HWFF/info/view.php?find_model=MHA-AL00
MHA-TL01 :http://hwmt.ru/oth/HWFF/info/view.php?find_model=MHA-TL01
Extract your downloaded firmware then use Huawei Update Extractor and open update.app in it.
Rightclick on BOOT.IMG and select Extract.
Then use TWRP or fastboot to flash it to boot.
Click to expand...
Click to collapse
I'm also back to square one even after flashing the stock image. The only reason I can't follow your guide is that I have the American variant, MHA-L29C567B138, which hasn't been found yet at all. Unless you mean I can use the boot image of any firmware on the list?
Abumarf said:
I'm also back to square one even after flashing the stock image. The only reason I can't follow your guide is that I have the American variant, MHA-L29C567B138, which hasn't been found yet at all. Unless you mean I can use the boot image of any firmware on the list?
Click to expand...
Click to collapse
If something is different in the C567 boot image you'd need someone with a C567 to extract their boot. I'll see if I can find any but I guess you have tried already.
ante0 said:
If something is different in the C567 boot image you'd need someone with a C567 to extract their boot. I'll see if I can find any but I guess you have tried already.
Click to expand...
Click to collapse
I have tried and I've also been checking on the Mate 9 Stock Firmware thread but I haven't seen anything. If you could try to find someone I'd appreciate that.
Abumarf said:
I have tried and I've also been checking on the Mate 9 Stock Firmware thread but I haven't seen anything. If you could try to find someone I'd appreciate that.
Click to expand...
Click to collapse
ante0 said:
If something is different in the C567 boot image you'd need someone with a C567 to extract their boot. I'll see if I can find any but I guess you have tried already.
Click to expand...
Click to collapse
c567 america version is not public yet, my fingerprint stop working
depooltrd said:
c567 america version is not public yet, my fingerprint stop working
Click to expand...
Click to collapse
Yeah, that's why you'd need someone with a stock C567 boot to extract their boot.img.
It can be done with TWRP then just flash the file boot.emmc.win with fastboot.
depooltrd said:
c567 america version is not public yet, my fingerprint stop working
Click to expand...
Click to collapse
Might I ask what you did that made the fingerprint sensor stop working? I'd like to know or at least narrow down the causes to something a bit more specific.
Abumarf said:
Might I ask what you did that made the fingerprint sensor stop working? I'd like to know or at least narrow down the causes to something a bit more specific.
Click to expand...
Click to collapse
i root my phone and after that, the fingerprint work, but late stop, reboot and work for a minutes and stop again. i unroot my phone but still the bug.
depooltrd said:
i root my phone and after that, the fingerprint work, but late stop, reboot and work for a minutes and stop again. i unroot my phone but still the bug.
Click to expand...
Click to collapse
Then it seems we both have the same exact problem.
Abumarf said:
Might I ask what you did that made the fingerprint sensor stop working? I'd like to know or at least narrow down the causes to something a bit more specific.
Click to expand...
Click to collapse
Abumarf said:
Then it seems we both have the same exact problem.
Click to expand...
Click to collapse
yeah, i think we need wait the next update for us version, and take that boot.img
Guys read this maybe it can help you https://forum.xda-developers.com/ma...i-mate-9-pro-unofficial-t3546976/post70843544
Might I ask if anyone has any inclination as to when the update for the C567 would arrive? Any kind of hint would be appreciated
Abumarf said:
Might I ask if anyone has any inclination as to when the update for the C567 would arrive? Any kind of hint would be appreciated
Click to expand...
Click to collapse
man, i rebranded my phone today to international, 636, the fingerprint its wotking fine, give me more time and i can tell you if work or stop.
depooltrd said:
man, i rebranded my phone today to international, 636, the fingerprint its wotking fine, give me more time and i can tell you if work or stop.
Click to expand...
Click to collapse
Please do, I'm getting tired of the password/pin lifestyle.
Accidentally when i updated from B360 to B365, i immediately got prompted with the update to B367, and due my motivation to go on latest security patch i didn't stored the B367 package on my HDD, so i didn't had the chance to extract from it the stock boot and recovery images for future updates. Now B368 is out and obviously I'm in need of those files; someone have a copy of them to share with me (and other members too)?
RedSkull23 said:
Accidentally when i updated from B360 to B365, i immediately got prompted with the update to B367, and due my motivation to go on latest security patch i didn't stored the B367 package on my HDD, so i didn't had the chance to extract from it the stock boot and recovery images for future updates. Now B368 is out and obviously I'm in need of those files; someone have a copy of them to share with me (and other members too)?
Click to expand...
Click to collapse
I think you can use the recovery and boot.img of B360/B365 etc. if you have mate can try else let me know I will download the file and share.
Edit- last file I see available on FF is B366 that too OTA file and full firmware is available only for B365.
shashank1320 said:
I think you can use the recovery and boot.img of B360/B365 etc. if you have mate can try else let me know I will download the file and share.
Edit- last file I see available on FF is B366 that too OTA file and full firmware is available only for B365.
Click to expand...
Click to collapse
Yeah already gave a check on FF bro and as you said it's since B365 that other updates aren't uploaded, so I'll give a try with B365 files... If it should work, I'll report it here... Hope so.
RedSkull23 said:
Yeah already gave a check on FF bro and as you said it's since B365 that other updates aren't uploaded, so I'll give a try with B365 files... If it should work, I'll report it here... Hope so.
Click to expand...
Click to collapse
It will work 99.99%. i have tested this many times..good luck bro
shashank1320 said:
It will work 99.99%. i have tested this many times..good luck bro
Click to expand...
Click to collapse
Nice to hear that, i thought about this some day ago but i was afraid that every recovery.img had its own signature, md5 or SHA calc incompatible if found unmatched by next recovery. Gonna try that, thanks friend
shashank1320 said:
It will work 99.99%. i have tested this many times..good luck bro
Click to expand...
Click to collapse
Today i flashed B365 boot and recovery files: at phone startup I've encountered bizzare things, like an unmatching PIN of screen unlock (never changed it in months), and so I wasn't able to access the phone anymore; luckily i always have with me on my external SD my previous backup, so i reflashed TWRP by fastboot and restored the backup, recovering the access to my device. Anyway i took the files requested by me by myself; for everyone that could ever need 'em, you can find those here
BLN-L21C432B367 boot.img - https://www.dropbox.com/sh/5ltsb3h1ad7yc8y/AAALUixZJTSVIPDcvf__GM-ga
BLN-L21C432B367 recovery.img - https://www.dropbox.com/sh/x28ch38regyzcy9/AAAoXz1w_zqMdqBldBdpF37ta
RedSkull23 said:
Today i flashed B365 boot and recovery files: at phone startup I've encountered bizzare things, like an unmatching PIN of screen unlock (never changed it in months), and so I wasn't able to access the phone anymore; luckily i always have with me on my external SD my previous backup, so i reflashed TWRP by fastboot and restored the backup, recovering the access to my device. Anyway i took the files requested by me by myself; for everyone that could ever need 'em, you can find those here
BLN-L21C432B367 boot.img - https://www.dropbox.com/sh/5ltsb3h1ad7yc8y/AAALUixZJTSVIPDcvf__GM-ga
BLN-L21C432B367 recovery.img - https://www.dropbox.com/sh/x28ch38regyzcy9/AAAoXz1w_zqMdqBldBdpF37ta
Click to expand...
Click to collapse
Sorry to hear about the problem. I am confused now as I had only b357 recovery that i used on many, starting from b350,357,360,365,375,379 and all worked fine for me. But its Huawei so can't say anything new things every day.
shashank1320 said:
Sorry to hear about the problem. I am confused now as I had only b357 recovery that i used on many, starting from b350,357,360,365,375,379 and all worked fine for me. But its Huawei so can't say anything new things every day.
Click to expand...
Click to collapse
Don't worry pal, nothing hard to solve. Huawei devices improved my problem solving :laugh: Recovery sounds ok to use, in fact i think that it was surely boot.img faults.
RedSkull23 said:
Don't worry pal, nothing hard to solve. Huawei devices improved my problem solving :laugh:.
Click to expand...
Click to collapse
Ain't that the truth!! I only used the device for a short time but I learned so much in those few weeks.
Dazed No More said:
Ain't that the truth!! I only used the device for a short time but I learned so much in those few weeks.
Click to expand...
Click to collapse
Ahah! Well everything's a problem on Huawei devices, from updating till various recovery procedures... All experience achieved for future tweaking! Always if there won't be a new Huawei :cyclops:
RedSkull23 said:
All experience achieved for future tweaking! Always if there won't be a new Huawei :cyclops:
Click to expand...
Click to collapse
Exactly. I'll never buy another Huawei phone but it was a great learning experience. My OnePlus 5T came two days ago so my sister got a new phone and I got a great device with tons of development....a win win situation:good:
Dazed No More said:
Exactly. I'll never buy another Huawei phone but it was a great learning experience. My OnePlus 5T came two days ago so my sister got a new phone and I got a great device with tons of development....a win win situation:good:
Click to expand...
Click to collapse
If only 1+ was cheaper, I'd went for it too! Awesome performances but great community support also... I found better support on my previous device, a Galaxy S4 Mini, than here on Honor. You surely did a nice switch
the update of June 2020 is online
https://developers.google.com/android/images
https://dl.google.com/dl/android/aosp/coral-qq3a.200605.001-factory-dbd8ce20.zip
It fixed the face id finally.
Magisk root still working with June update.
gm007 said:
It fixed the face id finally.
Click to expand...
Click to collapse
What was wrong with it?
Personal safety is not available on mine.
pilotgav said:
What was wrong with it?
Click to expand...
Click to collapse
It was broken when downgrading from Android 11.
This include the Covid tracker?
Sent from my Pixel 4 XL using Tapatalk
MicroMod777 said:
This include the Covid tracker?
Click to expand...
Click to collapse
Doesn't give me an option to turn it on but it's there
MicroMod777 said:
This include the Covid tracker?
Click to expand...
Click to collapse
Do you mean an application or the service? The service was there before the update.
gm007 said:
It fixed the face id finally.
Click to expand...
Click to collapse
You might want to state which version of the Face Unlock issue you're talking about, the one from the DP4 and subsequent downgrade is still there.
Tried to update with magisk via OTA method
Phone boots to black screen, only thing I can do is access the power menu...
dragynbane222 said:
You might want to state which version of the Face Unlock issue you're talking about, the one from the DP4 and subsequent downgrade is still there.
Click to expand...
Click to collapse
Yes I'm talking about the downgrade from dp4 to 10.
Let me tell you what I did,it was by mistake that I fix it.
I was on May build with face id broken,I downloaded the June ota yesterday but by mistake I choose Telstra ota the one that end with 002.A1 and face id work.
Then I realized that the build number is wrong for my phone so I tried to flash the full June build the one that end with 001 and again face id stopped working so I decided to stay with Telstra build
Hey guys after flashing magisk image tje touchscreen doest react so i cant log in. After flashing stock image everything works fine again. Anyone else experiencing this??
xdidnothingwrongx said:
Hey guys after flashing magisk image tje touchscreen doest react so i cant log in. After flashing stock image everything works fine again. Anyone else experiencing this??
Click to expand...
Click to collapse
Best advice I could give is to first patch the boot.img when all your magisk modules have either been disabled, or removed. Then dirty fastboot, (-w removed) the factory image to your inactive slot, let it boot up, then fastboot the magisk_patched.img to both slots. Also make sure your platform-tools are up to date. Best of luck to ya :good:
gm007 said:
Do you mean an application or the service? The service was there before the update.
Click to expand...
Click to collapse
Since when?
Sent from my Pixel 4 XL using Tapatalk
MicroMod777 said:
Since when?
Click to expand...
Click to collapse
If you mean the covid exposure notification i got it 2 weeks ago, it's in the google setting in the system settings.
Updates to Telstra and worked. Hope they release an update for the regular software soon. Thank you for the tip.
Worse battery performance on June patch than may
Hi,
I bought my phone three months back. Ever since the last update Version Name - WW18.0840.2106.86 my wifi and Hotspot just won't turn on.
I have been through the asus forum and seems like alot of customers are facing this issue.
One of them confirmed that even after replacing motherboard the issue persists. Others are facing air trigger issues after replacing the motherboard.
Just wanted to know if anyone here is facing similar issues.
DO let me know your thoughts on should I visit service center and Get my motherboard replaced or should I wait for the next update. My current Version Name - WW18.0840.2107.151
PS: My phone is not rooted
Thanks
I have not had these issues personally. I just updated to .151 last night though, so we shall see.
The general consensus is that the mobo needs to be replaced, and will most likely not get fixed with a software update. If it was correctable, a major issue like this would have forced a new FW update after .86 caused your initial problem.
You could always try flashing raw FW if you really want to tinker, but I doubt it will help. I would hit the service center and get the mobo replaced.
Good luck!
BILLYB187 said:
I have not had these issues personally. I just updated to .151 last night though, so we shall see.
The general consensus is that the mobo needs to be replaced, and will most likely not get fixed with a software update. If it was correctable, a major issue like this would have forced a new FW update after .86 caused your initial problem.
You could always try flashing raw FW if you really want to tinker, but I doubt it will help. I would hit the service center and get the mobo replaced.
Good luck!
Click to expand...
Click to collapse
Yup.. .86 update cause this. I just didn't want to change the motherboard,as it will change the imei of phone from what's on the box.
Thanks for your inputs though
I was helped by installing the karnel
do one thing i also got same issue ,what i do means i install twrp and wipe the system and after i install ota file after i reboot in slot b then every thing for fine for me ..
thieftime1980 said:
I was helped by installing the karnel
Click to expand...
Click to collapse
Really? I have same problem after update. It didn't allow me to turn on wifi. But if its sure that installing kernel would solve the problem I might give it a try
Would you elaborate your situation regarding this sir?
jaleel (jelly) said:
do one thing i also got same issue ,what i do means i install twrp and wipe the system and after i install ota file after i reboot in slot b then every thing for fine for me ..
Click to expand...
Click to collapse
HOW DID YOU INSTALL OTA FILE? VIA TWRP OR FLASH ALL?
TOYOBHUMAX said:
HOW DID YOU INSTALL OTA FILE? VIA TWRP OR FLASH ALL?
Click to expand...
Click to collapse
The ota files are installed right in system.
New firmware "keep root" WW-18.0840.2103.26
Okay so I went to the Asus website https://www.asus.com/supportonly/ROG%20Phone%205%20(ZS673KS)/HelpDesk_Download/ Got the latest firmware which is the most recent one for this month with the latest security patch. I remember doing this method...
forum.xda-developers.com
twistedumbrella said:
The ota files are installed right in system.
New firmware "keep root" WW-18.0840.2103.26
Okay so I went to the Asus website https://www.asus.com/supportonly/ROG%20Phone%205%20(ZS673KS)/HelpDesk_Download/ Got the latest firmware which is the most recent one for this month with the latest security patch. I remember doing this method...
forum.xda-developers.com
Click to expand...
Click to collapse
Nothing pops up
thieftime1980 said:
I was helped by installing the karnel
Click to expand...
Click to collapse
What kernel did you install?
https://forum.xda-developers.com/t/kernel-30-09-2021-android-11-kirisakura-1-2-0-for-asus-rog-phone-5-aka-anakin.4333363 / strona-5 # post-85712193
jaleel (jelly) said:
do one thing i also got same issue ,what i do means i install twrp and wipe the system and after i install ota file after i reboot in slot b then every thing for fine for me ..
Click to expand...
Click to collapse
Where did you install OTA file? Does Ota file install mean you in the home screen of the phone? Ota is in the main storage, right?
jaleel (jelly) said:
do one thing i also got same issue ,what i do means i install twrp and wipe the system and after i install ota file after i reboot in slot b then every thing for fine for me ..
Click to expand...
Click to collapse
How did you reboot to slot b? In twrp?
TOYOBHUMAX said:
How did you reboot to slot b? In twrp?
Click to expand...
Click to collapse
There is option in twrp check in reboot section
TOYOBHUMAX said:
Where did you install OTA file? Does Ota file install mean you in the home screen of the phone? Ota is in the main storage, right?
Click to expand...
Click to collapse
Twrp
TOYOBHUMAX said:
HOW DID YOU INSTALL OTA FILE? VIA TWRP OR FLASH ALL?
Click to expand...
Click to collapse
I use twrp for ota files
jaleel (jelly) said:
I use twrp for ota files
Click to expand...
Click to collapse
Hi thanks for the answer... How to install OTA files in twrp? You mean OTA files the one beginning with UL or WW
anybody found a real solution? i was fine and after i flashed a kernel later that day no wifi, I went bk to stock and no luck
chairman011 said:
anybody found a real solution? i was fine and after i flashed a kernel later that day no wifi, I went bk to stock and no luck
Click to expand...
Click to collapse
No one shares how lol. I guess theyre not here. Im struggling same problem too man
TOYOBHUMAX said:
Where did you install OTA file? Does Ota file install mean you in the home screen of the phone? Ota is in the main storage, right?
Click to expand...
Click to collapse
OTA files are the standard updates. There are a lot of how to guides that answer most of these questions, which may be why nobody is jumping up to walk you through it.
I wouldn't trust someone installing OTA files in TWRP because the system handles them already without any software. That is just asking for problems.
ROG Phone 5(s) Help Index
"Quick Filters" let you see all posts of a certain type. This can make finding posts easier, but what if a guide began as a "Question"? This thread aims to bridge that gap. You will find nearly all of the common things new owners are trying to...
forum.xda-developers.com
The link I posted earlier is included in that. Not sure why nothing showed up for it, but maybe you'll have better luck getting to it that way.
There's always a possibility it is a hardware issue. A lot of them have been SIM, Wifi, and Bluetooth issues. If you suspect a kernel issue, make sure you are following the instructions to restore. If you only flashed a boot, you didn't follow the instructions.