anyone else having this issue? any workarounds?
Documented here:
https://www.asus.com/zentalk/thread-157760-1-1.html
firmware version WW_14.2020.1708.56_20170719
ihacki said:
anyone else having this issue? any workarounds?
Documented here:
https://www.asus.com/zentalk/thread-157760-1-1.html
firmware version WW_14.2020.1708.56_20170719
Click to expand...
Click to collapse
I updated to that firmware version when it came out and haven't had any issues like that.
Maybe some lint in the charge port? Or corrosion? Are you using the ASUS charger that came with the phone?
If it happened the very first time you updated to nougat and plugged in your charger, back it up and then downgrade to an earlier nougat release and see if it corrects the issue. Or just try flashing the same firmware on top, maybe it was a bad flash.
wang1chung said:
I updated to that firmware version when it came out and haven't had any issues like that.
Maybe some lint in the charge port? Or corrosion? Are you using the ASUS charger that came with the phone?
If it happened the very first time you updated to nougat and plugged in your charger, back it up and then downgrade to an earlier nougat release and see if it corrects the issue. Or just try flashing the same firmware on top, maybe it was a bad flash.
Click to expand...
Click to collapse
hello can you please do me a favor and help me out? I rooted my zenfone 3 ZE552KL without backing up the preinstalled rom and installed lineage OS. NOw I want to have my zenui back. Is it possible? Can you help me through?
rsuyogya said:
hello can you please do me a favor and help me out? I rooted my zenfone 3 ZE552KL without backing up the preinstalled rom and installed lineage OS. NOw I want to have my zenui back. Is it possible? Can you help me through?
Click to expand...
Click to collapse
download the latest N firmware here, edit the update script in the firmware, see this
thread, part 1, step 2-4.
Then copy the firmware to your sdcard and flash it through twrp.
wang1chung said:
download the latest N firmware here, edit the update script in the firmware, see this
thread, part 1, step 2-4.
Then copy the firmware to your sdcard and flash it through twrp.
Click to expand...
Click to collapse
Sorry, but I did the thang the way you mentioned in that thread and above but my device's stuck in bootloop. What's the problem that caused this and will you mind to help me out of this?
rsuyogya said:
Sorry, but I did the thang the way you mentioned in that thread and above but my device's stuck in bootloop. What's the problem that caused this and will you mind to help me out of this?
Click to expand...
Click to collapse
factory reset after flashing, along with wiping cache and dalvik. You should always wipe cache/dalvik after flashing, it doesn't delete your data, not factory reset and wiping data does.
wang1chung said:
factory reset after flashing, along with wiping cache and dalvik. You should always wipe cache/dalvik after flashing, it doesn't delete your data, not factory reset and wiping data does.
Click to expand...
Click to collapse
I did exactly everything like you mentioned above and as well as in the thread. I did cleared the cache after flashing as well but it's still stuck in bootloop. Any solutions to it?
rsuyogya said:
I did exactly everything like you mentioned above and as well as in the thread. I did cleared the cache after flashing as well but it's still stuck in bootloop. Any solutions to it?
Click to expand...
Click to collapse
try everything I mentioned above except with the first release of nougat here. After you can successfully boot up, flash the second one.
Also, did everything flash ok with no errors? I had a bad download where it would flash the zip no problem but not boot. I re-downloaded it and problem solved. Might want to test the archive first.
wang1chung said:
I updated to that firmware version when it came out and haven't had any issues like that.
Maybe some lint in the charge port? Or corrosion? Are you using the ASUS charger that came with the phone?
If it happened the very first time you updated to nougat and plugged in your charger, back it up and then downgrade to an earlier nougat release and see if it corrects the issue. Or just try flashing the same firmware on top, maybe it was a bad flash.
Click to expand...
Click to collapse
Well, I just got my phone back from ASUS service center. It was a hardware failure for sure and they had to replace some chip(s). I had them downgrade to Android M for me as well.
I've had this phone since Jan 2017 and it failed in Sep 2017, shortly right after upgrading to Android N. Some people had the same hardware issue with Android M as well. Let's give it a few months and see if this will pop-up again - hopefully, still under warranty.
FYI, this is my first and only USB-C device I have. Having read about nightmares about USB-C cables, I don't dare to use any other charger or cable other than the one came with the phone. My Nillkin case has a cover on the charging port - so we can rule out lint and corrosion as well.
Related
https://www.mediafire.com/?922rx2xn53yt72r
Here it is. Enjoy. And yes it works on mine :fingers-crossed:
It's a new Official Update
Changelog taken from Android Police
-A new radio image.
-Touchscreen fixes (addresses BACON-55, which was originally reported and subsequently brought to our attention by Ausdroid). There's also an extensive thread on OnePlus' forums about it, among many other places (forum account needed).
Update: The fix is not complete, as reports of jumpiness are surfacing once again. It did fix the deadzone / random touches issue which prevented me from unlocking my phone for 10-15s at a time as I simply couldn't trace my pattern due to all the jumping around.
Unfortunately, the grounding issue which results in multitouch going nuts remains unfixed and must be resolved via another driver update. Another excruciating wait begins.
-Decreased power consumption in idle state (fixes BACON-599 which we wrote about here).
-Unspecified audio fixes.
-CVE-2014-4943 and another unspecified security update.
MD5 : 7538A068384C52FF6CA06C4B128B5ED1
P/S : I didn't have that jumpiness of sort, mine is working fine.
Flashing this worked perfectly for me. Thanks.
Glad to see it worked
Good job, works great
ravearamashi said:
https://www.mediafire.com/?922rx2xn53yt72r
Here it is. Enjoy. And yes it works on mine :fingers-crossed:
MD5 : 7538A068384C52FF6CA06C4B128B5ED1
Click to expand...
Click to collapse
Awesome!!!! Thanks so much
what is modified updater-script, is this the ota which is pushed by oneplus?
Is there a change log anywhere?
Fist and foremost,THANKS !
Could you perhaps elaborate on the update a bit ? e.g. this the official NEW update ?
boomam said:
Is there a change log anywhere?
Click to expand...
Click to collapse
You can check it out here. http://www.androidpolice.com/2014/0...ed-fixes-here-is-the-zip-for-manual-flashing/
Seems to work fine, thanks
Thanks m8, works perfectly.
What does it mean by modified updater script?
nice
Thank you
surronix said:
What does it mean by modified updater script?
Click to expand...
Click to collapse
I'm wondering the same thing. Can I flash this if I am on CM nightlies?
GETCASHMONEY said:
I'm wondering the same thing. Can I flash this if I am on CM nightlies?
Click to expand...
Click to collapse
No, it's strictly for CM11S
See, back when XNPH30O came out, lot of people couldn't update using OTA method when they are rooted/running Xposed/custom kernel and so forth because the OTA update would check the files before updating begins which of course the update would fail on devices running the aforementioned stuff. And a guy named Ludester modified the updater-script to bypass that file check and of course the update worked on these modified devices. So fast forward to this update, I just did the same thing.
Sorry Guys, but with TWRP i go into recovery and simply flash this file?
joeee89 said:
Sorry Guys, but with TWRP i go into recovery and simply flash this file?
Click to expand...
Click to collapse
Yes, and wipe cache after flashing then reboot.
joeee89 said:
Sorry Guys, but with TWRP i go into recovery and simply flash this file?
Click to expand...
Click to collapse
Yes you can
wipe
there is no need to wipe
i just installed it an no problems
i didt no wipe
Nope.
Phone is stuck at the OnePlus Logo after flashing via TWRP. Wiping caches and re-flashing didn´t help.
ok heres the issue....im not sure what i did wrong. i flashed a rom and got boot looped, so i said what the heck and went to odin thinking id flash stock firmware back...i did and still bootloop, then i deleted dalvik cache...still boot loop...so i flashed twrps and tried reflashing new rom...still bootloop.....wtf... so i tried odin again...bootloop...i need to fix this asap...any help..obviously this is serious if i cant get the bootloop to stop. recovery and download mode are working so no hard brick.
Primal instinct said:
ok heres the issue....im not sure what i did wrong. i flashed a rom and got boot looped, so i said what the heck and went to odin thinking id flash stock firmware back...i did and still bootloop, then i deleted dalvik cache...still boot loop...so i flashed twrps and tried reflashing new rom...still bootloop.....wtf... so i tried odin again...bootloop...i need to fix this asap...any help..obviously this is serious if i cant get the bootloop to stop. recovery and download mode are working so no hard brick.
Click to expand...
Click to collapse
Hi,
I have reported this thread to be moved to the right Q & A section where you might be able to get help quickly.
Good luck.
You flashed a custom rom?
well did you check the bootloader and modem?
example: your old firmwara was based on a coh4 and the new custom is based on coj3.. then you get bootloops.
In this case please download the fitting bl & modem to your rom!
Primal instinct said:
ok heres the issue....im not sure what i did wrong. i flashed a rom and got boot looped, so i said what the heck and went to odin thinking id flash stock firmware back...i did and still bootloop, then i deleted dalvik cache...still boot loop...so i flashed twrps and tried reflashing new rom...still bootloop.....wtf... so i tried odin again...bootloop...i need to fix this asap...any help..obviously this is serious if i cant get the bootloop to stop. recovery and download mode are working so no hard brick.
Click to expand...
Click to collapse
what version are you from the start before you flashed? please provide complete information
Its easy as anything
Download your phones official firmware from sammobile.com
Flash through odin in pda/ap tab
ankahuja said:
Its easy as anything
Download your phones official firmware from sammobile.com
Flash through odin in pda/ap tab
Click to expand...
Click to collapse
well ive done that like 3 times and it still wont come out of bootloop. its as if the phones bricked...turns on then tries to start up but turns right back off. it sometimes goes as far as saying android is starting and optimizes a few apps and shuts off
kerbiii said:
what version are you from the start before you flashed? please provide complete information
Click to expand...
Click to collapse
I originally was on android 5.1.1 cog5 build for sprint...then went to cm 12.1 remix by sabermod....when i used odin to flash back to original firmware, it kept bootlooping. anything helps
Primal instinct said:
I originally was on android 5.1.1 cog5 build for sprint...then went to cm 12.1 remix by sabermod....when i used odin to flash back to original firmware, it kept bootlooping. anything helps
Click to expand...
Click to collapse
Trying going back to a 5.0.1 firmware
N910PVPU3BOF5 ( I pulled that from N910P) Didn't remember Sprint model number.
So if I'm wrong find the correct model of sammobile and download 5.0.1.
See what that does. Bootloader should not be locked so it should be possible,
Primal instinct said:
I originally was on android 5.1.1 cog5 build for sprint...then went to cm 12.1 remix by sabermod....when i used odin to flash back to original firmware, it kept bootlooping. anything helps
Click to expand...
Click to collapse
what version where you trying to get back?? if its lower 5.1.1 it might be impossible for now since the new bootloader wont let you downgrade,, if not just try wipe cache and factory reset
kerbiii said:
what version where you trying to get back?? if its lower 5.1.1 it might be impossible for now since the new bootloader wont let you downgrade,, if not just try wipe cache and factory reset
Click to expand...
Click to collapse
I was on the correct firmware. but for some reason even if I use odin to flash newer firmware coj6 it still doesn't boot up.
kerbiii said:
what version where you trying to get back?? if its lower 5.1.1 it might be impossible for now since the new bootloader wont let you downgrade,, if not just try wipe cache and factory reset
Click to expand...
Click to collapse
update: i can use cyanogenmod for a few minutes but then it shuts off again. my sprint sim card is not readable which is wierd since its a sprint rom cog5 baseband. any ideas :crying::crying:
deroyabun said:
You flashed a custom rom?
well did you check the bootloader and modem?
example: your old firmwara was based on a coh4 and the new custom is based on coj3.. then you get bootloops.
In this case please download the fitting bl & modem to your rom!
Click to expand...
Click to collapse
i downloaded and installed the correct bootloader and modem but still no bueno. i got cyanogenmod for trltespr to work and boot up but sim card not readable and it shuts down after a few minutes. thats really wierd considering its a sprint based rom. any ideas
I having a similar issue for a few months now. Nobody seems to have a clear answer. I am not a noob and have flashed back to factory a million times on other phones.. I have spent hours trying everything with no luck. Sprint store will not help... pretty frustrating. Let me know if you find a solution.
Have you tried a new battery yet?
Sent from my iPhone using Tapatalk
amongunz said:
I having a similar issue for a few months now. Nobody seems to have a clear answer. I am not a noob and have flashed back to factory a million times on other phones.. I have spent hours trying everything with no luck. Sprint store will not help... pretty frustrating. Let me know if you find a solution.
Click to expand...
Click to collapse
me too, i also have a bootloop for a couple of months now. tried literally every single combination of bootloaders/modems/kernels/ROMs . i can't even get into recovery, but can get into download mode.
do you guys think trying another battery may seriously help? how could a new battery help getting out of a bootloop if download and/or recovery mode work fine?
I don't think another battery will do anything. I think it is all software. I can flash CM11 btw, so you should try that. But my system is extremely unstable... it works... but is beyond frustrating. my smart watch wont work.. have to restart phone throughout day.... so many problems I cant even list them all.
---------- Post added at 08:29 PM ---------- Previous post was at 08:28 PM ----------
Chasef254 said:
Have you tried a new battery yet?
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
A battery? How in the world would that help? That makes no sense... no offense, just sounds like you are asking someone to unnecessarily to spend $$$ when it is clearly software.
I'm having the same problems and want to know if op has tried it so I'll know if it's been ruled out of the problem thats why. Ok so it's software. You have the solution. No offense.
Sent from my iPhone using Tapatalk
d0p3t said:
me too, i also have a bootloop for a couple of months now. tried literally every single combination of bootloaders/modems/kernels/ROMs . i can't even get into recovery, but can get into download mode.
do you guys think trying another battery may seriously help? how could a new battery help getting out of a bootloop if download and/or recovery mode work fine?
Click to expand...
Click to collapse
I think this is a samsung issue. I am going to try and see if i can replace motherboard bc thats the only logical option. I can remarkably download and run (for a few minutes) cm12.1 but my sprint sim card is unrecognized (wierdly). I dont think its the modem or bootloader....ill update yall if i find a fix. Thanks P.I
amongunz said:
I having a similar issue for a few months now. Nobody seems to have a clear answer. I am not a noob and have flashed back to factory a million times on other phones.. I have spent hours trying everything with no luck. Sprint store will not help... pretty frustrating. Let me know if you find a solution.
Click to expand...
Click to collapse
The only solution i can find is to replace the motherboard or replace phone all together.
Primal instinct said:
I think this is a samsung issue. I am going to try and see if i can replace motherboard bc thats the only logical option. I can remarkably download and run (for a few minutes) cm12.1 but my sprint sim card is unrecognized (wierdly). I dont think its the modem or bootloader....ill update yall if i find a fix. Thanks P.I
Click to expand...
Click to collapse
Were you able to get it fixed? I'm probably going to go to a phonerepair shop this weekend or next week and see what they say or can do.
Hi, I am not happy with the latest update (V1.15.40.639) and would like to downgrade to the previous one (V1.13.40.496). I read on zentalk forum that we can downgrade by downloading the latter firmware from asus site(http://www.asus.com/Phone/ZenFone-2-Laser-ZE550KL/HelpDesk_Download/) and place it on SD card root. The reboot to the recovery and select something like "apply update from external". Can someone confirm if this will work? Is there an easy enough and confirmed way to downgrade the firmware. Any help will be much appreciated.
Edit: The method works!
Haven't done that but it should work, if you face any app crashes you will need to reset phone
Pls don't downgrade it will kill ur phone
mannulko said:
Pls don't downgrade it will kill ur phone
Click to expand...
Click to collapse
Have you tried it? If it goes dead, do you think Asus service center will be able to revive it?
No but have heard that software cannot be downgraded in any phone
Gustapo said:
Have you tried it? If it goes dead, do you think Asus service center will be able to revive it?
Click to expand...
Click to collapse
He is wrong xD
Like I said the you'd face app crashes which you can fix by resetting phone.
If you are not comfortable to do this then simply go to service center and tell them you want certain update flashed for whatever reason.
pra300 said:
He is wrong xD
Like I said the you'd face app crashes which you can fix by resetting phone.
If you are not comfortable to do this then simply go to service center and tell them you want certain update flashed for whatever reason.
Click to expand...
Click to collapse
ok. yeah that sounds the safest. Hopefully those guys would've a way to do this.
Hi. I was able to downgrade the mobile successfully following this method.
Gustapo said:
Hi. I was able to downgrade the mobile successfully following this method.
Click to expand...
Click to collapse
Did you actually go into recovery and flash the previous firmware or just let the phone detect the firmware and install it by itself?
heywheelie said:
Did you actually go into recovery and flash the previous firmware or just let the phone detect the firmware and install it by itself?
Click to expand...
Click to collapse
I placed the update on sd card. Booted to recovery. cleared data and cache and applied the update via SD Card method. The cleared cache once more and rebooted.Voila!
This method is going to wipe all user data???
Probably a reboot would do the same result.
I have, like many others, the latest firmware and I didn't encounter no problems. So definitely is not the firmware itself.
kalpit15 said:
This method is going to wipe all user data???
Click to expand...
Click to collapse
LOL. That's one question I never ask. It's always a good idea to do a backup before any update, especially if it's a full firmware flash and not an OTA update.
No. I only wiped cache and it seems to have kept the data intact at the time. I had a backup for safety's sake but I did not need to restore it.
Can We root the phone after downgrading it to lollipop using Kingroot?
pra300 said:
He is wrong xD
Like I said the you'd face app crashes which you can fix by resetting phone.
If you are not comfortable to do this then simply go to service center and tell them you want certain update flashed for whatever reason.
Click to expand...
Click to collapse
It can be downgraded
But if u Go from Marshmallow to Lollipop in ZOOL it won't do u any good moreover u would loose your VOLTE update
Hello, I'll give you all info about the situation.
Its i9505.
There is no sound at all, dialer is VERY VERY laggy and when I manage to dial a number, it just stucks (see photo), it wont play any videos or any music tracks from any web sites or internal memory, the phone itself gets very hot invery fast time, and battery drains enourmously. Problems appeared all in same time, when the phone was still in the stock 4.3 MKF firmware. At first, I thought it was a software problem. Then I just basically tried factory reset, of course it didnt helped, then I flashed few custom roms, and every time still was the same problems. Maybe some you may call me dumb or something, but I've spent about 15hours searching, downloading, reading and flashing lots of ****, and still didnt get these problems solved. In this point I have CM 13 and CWM. I tried flash back the original rom, but ODIN gives me error <ID:0/003> FAIL! (Auth) , and now, with my head aching so much, I ask you for help. Hope to get some answers soon, thanks a bunch in advance.
If you're going to flash custom ROMs, use TWRP.
I flashed all custom roms with twrp, now I have cwm because i saw in One thread that cwm factory reset solves these problems, but it didnt and Then I gave up and started this thread. Its about 1minute to flash twrp back.
XMP LTU said:
I flashed all custom roms with twrp, now I have cwm because i saw in One thread that cwm factory reset solves these problems, but it didnt and Then I gave up and started this thread. Its about 1minute to flash twrp back.
Click to expand...
Click to collapse
I see.
To go back to stock it's recommended to use original cable and back USB ports. If it still doesn't work, try a different Odin and/or Windows version.
But, generally, if you have the same problem across different ROMs, it's usually some kind of hardware problem.
I've read in few threads and forums, that modem issue can cause these problems. Is that true?
XMP LTU said:
I've read in few threads and forums, that modem issue can cause these problems. Is that true?
Click to expand...
Click to collapse
It may be possible. Flashing a newer stock ROM should also update the modem and bootloader.
GDReaper said:
It may be possible. Flashing a newer stock ROM should also update the modem and bootloader.
Click to expand...
Click to collapse
I tried. I get the error which I wrote in my first post.
XMP LTU said:
I tried. I get the error which I wrote in my first post.
Click to expand...
Click to collapse
And I told you in my second reply to this thread the recommended steps. Did you do them?
Just got this phone in yesterday as a replacement for a water damaged LG G3. Thought to myself that I was pretty good at rooting, flashing etc. so I decided that would be the first thing I would do. Long story short, I rooted the phone just fine and even flashed the non-bloatware-filled rom available with little problem. Then I tried to flash xposed with flashfire and, well, things didn't go so smoothly. Ended up getting stuck on the AT&T splash screen after every reboot. To attempt a fix for this I thought I would just use Odin to flash stock, what I thought was stock but was really 930UUEU, once again. I am now realizing that I flashed the wrong firmware and am currently trying to flash G930AAT once more but keep getting "FAIL! Model dismatch fail" in Odin.
Open to any suggestions at this point as I am at a loss. I've tried using a different version of Odin, 3.12.3, but to no avail have not been able to get it right. Let me know if you need any more information as to help me with this problem. Thanks in advance!
You're probably flashing an older firmware than what's on phone? Which verison are you trying to flash?
joe3681 said:
You're probably flashing an older firmware than what's on phone? Which version are you trying to flash?
Click to expand...
Click to collapse
Currently the phone boots straight into recovery. I get the update droid that fails and am sent to the options where it has me as running G930UUEU2APEH. I am pretty certain that this is the firmware I mistook as stock and half-flashed with odin. Still able to get into download mode so let's hope I can work this out!
Download the U firmware that I posted and flash that. Should flash fine. I've done it several times with the mode Odin from the root thread with zero issues
joe3681 said:
Download the U firmware that I posted and flash that. Should flash fine. I've done it several times with the mode Odin from the root thread with zero issues
Click to expand...
Click to collapse
Worked like a charm. Is there anything I should know about being on U firmware while having the 930A?
joe3681 said:
Download the U firmware that I posted and flash that. Should flash fine. I've done it several times with the mode Odin from the root thread with zero issues
Click to expand...
Click to collapse
Alright, looks like I may have run into another problem. I've rooted and flashed xposed properly this time. Kept getting a security warning so I thought it would be okay to uninstall SecurityLogAgent.apk and I am now unable to install apps. This may just be a coincidence and it may be that I have a different problem. May also be important to note that I have to reinput my WiFi password after every reset.
SubjectToReplay said:
Alright, looks like I may have run into another problem. I've rooted and flashed xposed properly this time. Kept getting a security warning so I thought it would be okay to uninstall SecurityLogAgent.apk and I am now unable to install apps. This may just be a coincidence and it may be that I have a different problem. May also be important to note that I have to reinput my WiFi password after every reset.
Click to expand...
Click to collapse
Reflash the U firmware and that will restore the security log agent app. If your rooted you'll get that notification, you'll need to freeze one of the security apps in titanium. As for the WiFi password there is a fix for it in this forum http://forum.xda-developers.com/ver...-root-install-xposed-unroot-t3411039/page230.
Also you should probably flash his V15 fixes it will fix multiple things when you root.
dirtydodge said:
Reflash the U firmware and that will restore the security log agent app. If your rooted you'll get that notification, you'll need to freeze one of the security apps in titanium. As for the WiFi password there is a fix for it in this forum http://forum.xda-developers.com/ver...-root-install-xposed-unroot-t3411039/page230.
Also you should probably flash his V15 fixes it will fix multiple things when you root.
Click to expand...
Click to collapse
Started this about 15 minutes ago. Thanks for the link to fix the WiFi issues.
dirtydodge said:
Reflash the U firmware and that will restore the security log agent app. If your rooted you'll get that notification, you'll need to freeze one of the security apps in titanium. As for the WiFi password there is a fix for it in this forum http://forum.xda-developers.com/ver...-root-install-xposed-unroot-t3411039/page230.
Also you should probably flash his V15 fixes it will fix multiple things when you root.
Click to expand...
Click to collapse
Okay, flashed everything again. Everything was working great and now I am getting that error -505 again when trying to install apps.
SubjectToReplay said:
Okay, flashed everything again. Everything was working great and now I am getting that error -505 again when trying to install apps.
Click to expand...
Click to collapse
Did you run the V 15 fix from the thread that i posted you. The fix corrects a lot of stuff
dirtydodge said:
Did you run the V 15 fix from the thread that i posted you. The fix corrects a lot of stuff
Click to expand...
Click to collapse
I did, it fixed my WiFi issues and being I flashed the debloat version it also got rid of Instagram etc. so I am certain it worked. Could it have something to do with me installing lucky patcher?
SubjectToReplay said:
I did, it fixed my WiFi issues and being I flashed the debloat version it also got rid of Instagram etc. so I am certain it worked. Could it have something to do with me installing lucky patcher?
Click to expand...
Click to collapse
Just an update. After some deduction I decided it must be lucky patcher. Uninstalled it, wiped dalvik cache and everything seems to be fine. I am still cautiously optimistic.
I'm no help on the root issues. Root isn't what it used to be so I don't really mess with it anymore.