Has anyone installed the update from 20170223 to 20170303 successfully without the loss of any data , if no what are the issues/errors and if yes what is the procedure you followed?
And if successfully updated then is there any bug/issue found that was not present in previous built ??
Ok I got time and flashed the new update without loss of any data and till now no new bugs have been found
Related
Guys i recently flashed CM 13 on my ZenFone 2 ZE550ML. I was a beta tester for Asus' Marshmallow version and got tried with their fake update promises. So i downgraded to lollipop using AFT unlocked bootloader, flashed TWRP and then CM 13. But i noticed one thing. My GPS is not working in CM 13. It was not working in Asus' marshmallow beta but it was working on official lollipop firmware. Is anyone else having this issue?
Please check and confirm.
PS. I checked it using apps from playstore but mu GPS didn't even show one satellite while i got 15 satellite locks on my mom's Moto G4 plus.
same problem
after downgrade from MM beta a gps can't lock satellite
it still looking for gps ......... ....... .......
how can i fix this issue? :crying:
Device : ZE551ML
sorry for my bad English
I'm using asus zenfone 2 ze551ml
it's running latest build 21/9/17 of lineage os 14.1
im unable to get root access
i have checked my system folder in root directory through TWRP
Su file is present but although after allowing apps and ADB to get root access in developer setting
the ui which apparently ask for root access is not popping up
and root checker suggests that your device is not properly rooted at all
This problem came up when is switched rom lineage os 14.1 (nougat 7.1.1)
to lineage os 14.1(nougat 7.1.2)
recently updated su addons dated 25/06/2017 are having such a problem for me
plz update the su addon for X86(or firmware) or atleast give me the reason to stay on this rom
Thanks A Lot
andy9970 said:
I'm using asus zenfone 2 ze551ml
it's running latest build 21/9/17 of lineage os 14.1
im unable to get root access
i have checked my system folder in root directory through TWRP
Su file is present but although after allowing apps and ADB to get root access in developer setting
the ui which apparently ask for root access is not popping up
and root checker suggests that your device is not properly rooted at all
This problem came up when is switched rom lineage os 14.1 (nougat 7.1.1)
to lineage os 14.1(nougat 7.1.2)
recently updated su addons dated 25/06/2017 are having such a problem for me
plz update the su addon for X86(or firmware) or atleast give me the reason to stay on this rom
Thanks A Lot
Click to expand...
Click to collapse
Did you upgrade or do a full wipe?
Some stuff that I read indicated that uninstalling old su before installing the new su build was a good idea. It was released for those that had issue with the old one and not really a upgrade.
I recently did a full wipe on my phone (moto z) and used latest su on 7.1.2 without problems.
I suggest checking out what the local forum thread of your device says. If this is a device and build specific issue I'm sure some other people noticed it too.
Sent from my XT1650-03 using Tapatalk
i am facing the very similar issue on my zenfone 2 as well. I updated from rooted stock ROM to latest lineage 14.1 . kindly help
swejuggalo said:
Did you upgrade or do a full wipe?
Some stuff that I read indicated that uninstalling old su before installing the new su build was a good idea. It was released for those that had issue with the old one and not really a upgrade.
I recently did a full wipe on my phone (moto z) and used latest su on 7.1.2 without problems.
I suggest checking out what the local forum thread of your device says. If this is a device and build specific issue I'm sure some other people noticed it too.
Click to expand...
Click to collapse
I know what are you trying to say
That many device uses same su so check you my phones specific
But tbh what is know is there are only 5 devices running x86 cpu zenfone 2,4,5,6
And only one of them is running lineage os 14.1 other dont support officially so they use 13.0 's addon zip
That means only zenfone 2 can flash 14.1's addon su
And FYI I did wiped first
And xiomi's phine are having same problem with this popup
Finally a solution........ That after long desperate efforts worked for me. You can flash the Magisk 13.0 zip. Mind you an upgraded version will lead you to a loop to your custom recovery. Magisk 13.0 is zenfone 2 x86 architecture compatible. Good luck. Just got this solution last night. Tell me if this helped you and also if you found a better way.
Ayushman Tiwari said:
Finally a solution........ That after long desperate efforts worked for me. You can flash the Magisk 13.0 zip. Mind you an upgraded version will lead you to a loop to your custom recovery. Magisk 13.0 is zenfone 2 x86 architecture compatible. Good luck. Just got this solution last night. Tell me if this helped you and also if you found a better way.
Click to expand...
Click to collapse
Did i have to wipe my lineage os?
Ayushman Tiwari said:
Finally a solution........ That after long desperate efforts worked for me. You can flash the Magisk 13.0 zip. Mind you an upgraded version will lead you to a loop to your custom recovery. Magisk 13.0 is zenfone 2 x86 architecture compatible. Good luck. Just got this solution last night. Tell me if this helped you and also if you found a better way.
Click to expand...
Click to collapse
Wherr can i find magisk 13.0 ?
Hello guys!
I just started learning how to root my one plus 5t and in the middle of the proces i bricked it , found an software online that unbricks your phone and i got it back at android 7.1.1 and oxygenOS 4.7.4.
I want to put it back to the highest android and the newest available oxygen os for the 5t. But the update function doesnt work or to be precise it says that the newest version is already installed. I tried to manualy update it but when i tried it says update failed.
If anyone has more experience ( practicaly everyone ) i would be grateful for your help
Good day
BeepBook said:
Hello guys!
I just started learning how to root my one plus 5t and in the middle of the proces i bricked it , found an software online that unbricks your phone and i got it back at android 7.1.1 and oxygenOS 4.7.4.
I want to put it back to the highest android and the newest available oxygen os for the 5t. But the update function doesnt work or to be precise it says that the newest version is already installed. I tried to manualy update it but when i tried it says update failed.
If anyone has more experience ( practicaly everyone ) i would be grateful for your help
Good day
Click to expand...
Click to collapse
Follow this link.
https://forum.xda-developers.com/oneplus-5t/how-to/official-oxygenos-4-7-2-7-1-1-ota-t3709265
The official ROM, and working TWRP Recovery.
If you would do exactly the same as mentioned in the post , probably you will get Android Q along with TWRP installed.
Thanks to me later.
Hi everyone,
Recently I wiped my Moto G5 to factory reset, then installed the official Oreo 8.1 firmware, then installed CarbonROM custom ROM. Since then everything seemed to work fine, but people told me they can't join me via calls, they directly ended on my voicemail ...
I searched as I could a solution at my problem but found anything ... Is there a setting I forgot to set well ?
Thanks for your answers
It's an old outdated no longer supported rom
Please try changing your rom to lineage mintos for the latest custom rom for this device
Hi,
I was trying to update my Redmi Note 8t from 17.1 to 18.1. I ended up in a boot loop. I tried with the update from 22-4-4 and the previous one. I also updated the recovery image. I cleared all partitions and installed again. Nothing works.
Switching back to the latest 17.1. works.
Anyone else having this problem? How can I find out, what the problem is? Can I enable any logging?
adb logcat is not working during startup.
Regards, Sebastian
i can confirm this.
i tried with the 2022-04-18 build on redmi note 8T
I have the same problem.
Do you know where can i get 17 ?
I broke my Redmi Note 8T (Willow) by updating LOS 17 -> 18.1
(Bootloop, without even seeing the LOS animation)
In /proc/last_kmseg I saw that the underlying issue was caused by a fatal error in the modem.
I.e. something kernel<->modem broke the thing.
Through recovery, I flashed a modem update from
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
and everything is working again
Finally, I installed the latest official Miui version (12.5 I think it was), then I installed LinageOS 18.1 recovery and latest nightly from 23.5. again and it worked.
frauschrotti said:
Finally, I installed the latest official Miui version (12.5 I think it was), then I installed LinageOS 18.1 recovery and latest nightly from 23.5. again and it worked.
Click to expand...
Click to collapse
i can confirm that:
the MUI Version i downloaded i got from : https://xiaomifirmwareupdater.com/miui/willow/stable/V12.5.4.0.RCXEUXM/
willow_eea_global_images_V12.5.4.0.RCXEUXM_20220218.0000.00_11.0_eea
i needed to use the fastboot method and reflash all ROMs with the "flash_all.sh"