ZenFone 5 ZE620KL Camera stopped working. - Asus Zenfone 5 (2018, ZE620KL) Questions & Answers

Hello everyone!
I came here to get some help with my device. Everything was perfect until I updated my ZenFone 5 to Android 9. My camera never opened anymore and NFC stopped working. Asus don't give a sh** to support to solve this problem. After a research, I've heard that this happens for those who unlocked the bootloader. But this is not my case. I've checked the bootloader status and shows locked. So, i've tryed to revert the firmware doing a 'downgrade' but the device refuses to install older firmwares. I didn't found any solution for these issues. Anyone could gimme some help?

You can try this: https://forum.xda-developers.com/zenfone-5/general/ze620kl-how-to-to-stock-firmware-t3969849

GVhenrique said:
You can try this: https://forum.xda-developers.com/zenfone-5/general/ze620kl-how-to-to-stock-firmware-t3969849
Click to expand...
Click to collapse
Thanks for your reply. I'll try this tomorrow because my computer is not available right now and i'll come back to post the results. Thanks!!

Related

[Q] Online Update for SEA Region failed

Greetings.
Very recently, there was an official/OTA update for P7-L10. And I subsequently downloaded and tried to update it as soon as it finishes downloading.
But, when it tried to update, it keeps failing. Is the update wrong? or is there something missing that I am not clearly seeing it?
My current version, out of the box - P7-L10V100R001C00B133SP01
and the update (online update) is (as mentioned) : P7-L10_SouthPacific_C00B620.
Please advise me on what might have went wrong?
Thank you.
piring said:
Greetings.
Very recently, there was an official/OTA update for P7-L10. And I subsequently downloaded and tried to update it as soon as it finishes downloading.
But, when it tried to update, it keeps failing. Is the update wrong? or is there something missing that I am not clearly seeing it?
My current version, out of the box - P7-L10V100R001C00B133SP01
and the update (online update) is (as mentioned) : P7-L10_SouthPacific_C00B620.
Please advise me on what might have went wrong?
Thank you.
Click to expand...
Click to collapse
Do you have custom recovery?
ibeqa said:
Do you have custom recovery?
Click to expand...
Click to collapse
Hey there, thank you for the reply.
I'm not sure, how to check. But I have never rooted this phone yet.
piring said:
Hey there, thank you for the reply.
I'm not sure, how to check. But I have never rooted this phone yet.
Click to expand...
Click to collapse
Do you have TWRP or CWM installed? Was your phone brand new or pre-owned? Do you have custom rom or stock rom?
ibeqa said:
Do you have TWRP or CWM installed? Was your phone brand new or pre-owned? Do you have custom rom or stock rom?
Click to expand...
Click to collapse
Nope, I do not have those installed. This is a brand new phone running stock rom.
Ok, I guess your phone is not branded (vodafone, orange, etc.), so get the b609 update and install it.
If you had firmware 133, how come you got SAE update? Where did you buy your phone?
ibeqa said:
Ok, I guess your phone is not branded (vodafone, orange, etc.), so get the b609 update and install it.
If you had firmware 133, how come you got SAE update? Where did you buy your phone?
Click to expand...
Click to collapse
Yep, it's not. Hmm. I am unsure as to how or where I can get the B609 update, because ever since I first laid my hands on this phone, it has been running B133 out of the box. And, since, in between then and now, I have been going to the system update to look for any update prior to this one that I am currently having a problem to update, and there was no new update (until, again, now )
Also, previously I did went online on my PC to find an update B609, and downloaded it and tried to do a local update. and unfortunately for me, it caused my phone to be soft-bricked, and back then, I have not turned on my USB debugging or did any major changes to my phone, thus, requiring me to send my phone to the service centre. So, I'm kinda weary about downloading an update online from my PC, as of now.
Well, I am not sure what SAE is, and to answer that question, again, I do not know how I may have gotten the update. I bought my phone from where I am currently living, Malaysia.
Can you make a print screen of your SAE update problem?
sorry, but um, can you please enlighten me as to what is SAE? I am truly sorry for not knowing this.
piring said:
sorry, but um, can you please enlighten me as to what is SAE? I am truly sorry for not knowing this.
Click to expand...
Click to collapse
SEA is the code Southeastern Asia
Ohhh. haha. Sorry, was wondering what SAE was. Will update as soon as possible.
ibeqa said:
Can you make a print screen of your SAE update problem?
Click to expand...
Click to collapse
Hey there, I couldn't really printscreen it, as it was in the updating process (the one with the Android bot and the black screen behind) anyway, it just it failed. That's all.
Here's however, a printscreen of the update.
piring said:
Hey there, I couldn't really printscreen it, as it was in the updating process (the one with the Android bot and the black screen behind) anyway, it just it failed. That's all.
Here's however, a printscreen of the update.
Click to expand...
Click to collapse
So OTA fails., what's the code of error (why it fails)?
Also, you can try manual update or the "3 button update" (it is described in the forum).
But the most important thing is to know why it fails.
P.S. You can take print screens from the Hisuite during update or when it fails
piring said:
Hey there, I couldn't really printscreen it, as it was in the updating process (the one with the Android bot and the black screen behind) anyway, it just it failed. That's all.
Here's however, a printscreen of the update.
Click to expand...
Click to collapse
Hi piring, I've encounter the same issue with updating from B133SP01 to B620, my set is a"SOUTH PACIFIC" model.
I even brough my set to the huawei service centre to see if the technician over there can solve the issue but unfortunately, they are just as clueless as I am..... They did a factory reset of my set and tried to install the update again but the update still fail to install. There is no error code but only "fail" word appearing. They claim it's because my set was rooted but when I have unroot my phone, it still.can't update.
So if you managed to successfully updated your set, can you share with me how to go about it? Thanks.
[email protected] said:
Hi piring, I've encounter the same issue with updating from B133SP01 to B620, my set is a"SOUTH PACIFIC" model.
I even brough my set to the huawei service centre to see if the technician over there can solve the issue but unfortunately, they are just as clueless as I am..... They did a factory reset of my set and tried to install the update again but the update still fail to install. There is no error code but only "fail" word appearing. They claim it's because my set was rooted but when I have unroot my phone, it still.can't update.
So if you managed to successfully updated your set, can you share with me how to go about it? Thanks.
Click to expand...
Click to collapse
Oh. well, to be honest, I kinda given up hopes on how to update it. And with that, I am still clueless as to how to update it. I have tried using HiSuite, but to my surprise, HiSuite mentioned that my phone is already up to date. So, I am honestly puzzled as to how my phone is pushing for an OTA, but HiSuite insists that my phone model is of current and latest update.
Sorry I am unable to help you.
piring said:
Oh. well, to be honest, I kinda given up hopes on how to update it. And with that, I am still clueless as to how to update it. I have tried using HiSuite, but to my surprise, HiSuite mentioned that my phone is already up to date. So, I am honestly puzzled as to how my phone is pushing for an OTA, but HiSuite insists that my phone model is of current and latest update.
Sorry I am unable to help you.
Click to expand...
Click to collapse
Hi piring, same thing goes for my HiSuite as well. It's kinda of sucks that the update is available but can't update. It's even more worse that Huawei service centre cannot do anything about it and just tell me forget about the update and ignore the notification. Now i have a phone with a permanent notification mark that i cannot get rid of.
P7-L10 is a good phone but the support i'm getting from Huawei service centre is really unprofessional and disappointing.
But anyway, thanks for your reply.

So we can hope for the official bootloader soon.

Finally some good news!!! https://nokiapoweruser.com/hmd-announces-bootloader-unlock-for-nokia-8/
I doubt it. It's over a year old now and not likely to be the focus of their efforts, and those HMD guys seem like wankers anyway, giving us a Sophie's choice instead of bootloader unlock for all of their phones.
well, someone already tried to do the process in his nokia 5 ??
I tried but at the time of installing the apk I got an error, I think it's because I'm in the 7.1.2 firmware
it would be a matter of trying to update to 8.1 and see if it is feasible to unlock the bootloader
2909luboy said:
well, someone already tried to do the process in his nokia 5 ??
I tried but at the time of installing the apk I got an error, I think it's because I'm in the 7.1.2 firmware
it would be a matter of trying to update to 8.1 and see if it is feasible to unlock the bootloader
Click to expand...
Click to collapse
It's only for Nokia 8 for now. Why would you even try to do that without reading about it?

Need help for Huawei P30 Pro, your device has loaded a different operating system

So my friend got the Huawei P30 Pro three days ago and everything was working fine until one morning it was stuck in a bootloop, it basically powers the phone then the messege " your device has loaded a different operating system " pops up and some other link below the text, then after that it goes to the Huawei eRecovery tab where it has the option to factory reset, update the emui and power off but, we tried updating the emui and a messege appears that " getting package info failed ", also if you try to power off the phone it just goes back to the first messege " your device has loaded a different operating system " . Factory reset doesn't work too. Anyone experienced the same problem or has a solution to it? I'm totally new to installing software to mobile phones so i would like a whole explanation if someone has the time. Thanks in advance.
Kakoda said:
So my friend got the Huawei P30 Pro three days ago and everything was working fine until one morning it was stuck in a bootloop, it basically powers the phone then the messege " your device has loaded a different operating system " pops up and some other link below the text, then after that it goes to the Huawei eRecovery tab where it has the option to factory reset, update the emui and power off but, we tried updating the emui and a messege appears that " getting package info failed ", also if you try to power off the phone it just goes back to the first messege " your device has loaded a different operating system " . Factory reset doesn't work too. Anyone experienced the same problem or has a solution to it? I'm totally new to installing software to mobile phones so i would like a whole explanation if someone has the time. Thanks in advance.
Click to expand...
Click to collapse
You're the same guy from reddit who was told your friend flashed the wrong version of EMUI 10
Read this thread carefully
https://forum.xda-developers.com/huawei-p30-pro/how-to/ready-emui-10-c431-dload-version-t4008639
Your problem got solved?
Kakoda said:
So my friend got the Huawei P30 Pro three days ago and everything was working fine until one morning it was stuck in a bootloop, it basically powers the phone then the messege " your device has loaded a different operating system " pops up and some other link below the text, then after that it goes to the Huawei eRecovery tab where it has the option to factory reset, update the emui and power off but, we tried updating the emui and a messege appears that " getting package info failed ", also if you try to power off the phone it just goes back to the first messege " your device has loaded a different operating system " . Factory reset doesn't work too. Anyone experienced the same problem or has a solution to it? I'm totally new to installing software to mobile phones so i would like a whole explanation if someone has the time. Thanks in advance.
Click to expand...
Click to collapse
Hey did your problem got solved ?
Would be great if you could leave me some information too, due I'm facing a similar problem
It would be great if you could leave some information
Cheers
Binban88 said:
Hey did your problem got solved ?
Would be great if you could leave me some information too, due I'm facing a similar problem
It would be great if you could leave some information
Cheers
Click to expand...
Click to collapse
Hi m8,
What's your actual build number and cust? For how to find out in case you don't know for sure, check my post - https://forum.xda-developers.com/showpost.php?p=81887785&postcount=418
Sent from my VOG-L29 using Tapatalk
SilviuO said:
Hi m8,
What's your actual build number and cust? For how to find out in case you don't know for sure, check my post - https://forum.xda-developers.com/showpost.php?p=81887785&postcount=418
Sent from my VOG-L29 using Tapatalk
Click to expand...
Click to collapse
Hi There,
I have the same problem. I did flash it with a wrong version. I ran that command here is my build number:
PCT-L29 9.0.1.169(C636E1R2P1)
I cannot find anyway to fix this.
Update: Thank you for the reply. That is the first problem that there is no free version. The second one is that these files are full-base version not the sd-base version. How can I convert the full-base version to the sd one?
Matt_honor said:
Hi There,
I have the same problem. I did flash it with a wrong version. I ran that command here is my build number:
PCT-L29 9.0.1.169(C636E1R2P1)
I cannot find anyway to fix this.
Click to expand...
Click to collapse
Hi m8,
Did you flashed a wrong version cust of EMUI 10 on your Honor View 20 device?
Later edit - i've found the dload firmware for your device (EMUI 10) which is needed to be used to revive your device, but it's a paid one and i don't have an account in order to download it
PCT-L29D 10.0.0.179(C636E3R4P3)_Firmware_EMUI10.0.0_05015PVU
Sent from my HUAWEI VOG-L29 using XDA Labs
Thank you for the reply. Unfortunately , I flashed it with C434 and I was not aware of it that it can brick my phone. All the blogs I looked into, they were all mentioning the PCT-L29 not the specific version.
That is the first problem that there is no free version. Is there any other website that I can request to download this version?
The second one is that these files are full-base version not the sd-base version. How can I convert the full-base version into the sd one?
Another question that my version is C636E1R2P1 and the one you provided is C636E3R4P3. They have different regions of E1R2P1 and E3R4P3. Does that create any issue?
Matt_honor1 said:
Thank you for the reply. Unfortunately , I flashed it with C434 and I was not aware of it that it can brick my phone. All the blogs I looked into, they were all mentioning the PCT-L29 not the specific version.
That is the first problem that there is no free version. Is there any other website that I can request to download this version?
The second one is that these files are full-base version not the sd-base version. How can I convert the full-base version into the sd one?
Another question that my version is C636E1R2P1 and the one you provided is C636E3R4P3. They have different regions of E1R2P1 and E3R4P3. Does that create any issue?
Click to expand...
Click to collapse
No, the dload firmware for your device isn't free on other site
You can't convert those files. What you've got is the update zip files that are used by HiSuite when there is an update available for you. But you can't use HiSuite, because you would need your device to be working...
No issues, if you managed to get that firmware, you can use it
Sent from my HUAWEI VOG-L29 using XDA Labs

Samsung Galaxy A6 touch screen not working after update

Hello, guys! After installing the latest update on my Galaxy A6 (A600FN) the touch screen stopped working. I tried flashing all 3 ROMs for my region that had the version 5 bootloader with Odin and none of them fixed the issue. One of them was Android 10 and 2 were Android 9. ROMs with an older version of the bootloader would fail the flash because apparently you can't downgrade it. It shows this error: Sw rev. Check fail. Device: 5, binary 3. I'm certain it's not a hardware issue because I had this happen on 2 A6 devices right after the update. I thought of trying a custom ROM but I can't find one for A6, only A6+. What can I do here? Can I trick it somehow to downgrade it? Is there some command I can send through adb shell to fix the touchscreen? Any help would be greatly appreciated!
BTW, I can access the device via a USB OTG mouse and it works perfectly fine.
Bump. Please, any help is appreciated!
Do you tried factory reset from recovery?
Zevnor said:
Do you tried factory reset from recovery?
Click to expand...
Click to collapse
That was the first thing I tried. Didn't help.
robert335 said:
That was the first thing I tried. Didn't help.
Click to expand...
Click to collapse
Is your phone carrier-branded? If yes, try to flash unbranded firmware.
I managed to fix it, will update this post soon with how I did it.
robert335 said:
I managed to fix it, will update this post soon with how I did it.
Click to expand...
Click to collapse
HI, if you have a solution to this problem can you share it please? I have the same phone with the same issue .
barthab said:
HI, if you have a solution to this problem can you share it please? I have the same phone with the same issue .
Click to expand...
Click to collapse
First make sure you aren't RMM locked: https://forum.xda-developers.com/sa...w-to/guide-root-install-twrp-samsung-t3747535
Then get yourself TWRP: https://forum.xda-developers.com/galaxy-a6/development/recovery-twrp-3-2-2-0-galaxy-a6-t3819741
Afterwards, I installed this custom ROM which is pretty close to stock Pie: https://forum.xda-developers.com/galaxy-a6/development/rom-pa6-rom-a6-t3943573
Maybe you can try this one too, I haven't tried it: https://forum.xda-developers.com/galaxy-a6/development/phonezippy-microrom-t4083579
After installing the ROM, make sure to install "no-verity-opt-encrypt" and "RMM Bypass v3". This is VERY IMPORTANT, otherwise your device will become RMM locked and brick itself until you flash stock firmware again.
I fixed both of my phones but looks like I messed up on one and after I restarted it had RMM state Prenormal. Does anyone know how to fix this? OEM is unlocked in developer settings but flashing twrp from Odin yields "only official binaries are allowed"...

Unlock carrier locked bootloader Pixel [BETA]

UPDATE AS OF 16 OF MAY 2023
This project isn't working right now, but I am still working on it.
However due the complicated nature of the projects and the fact that I have little free time means this project will probably still take time to get to functional state.
If anyone has any idea please contact me, any hell is welcome!
______________________________________________________
Hi!
So I decided I wanted to flash custom software into my phone, but it's bootloader was locked so I figure a way to unlock it!
I am going to leave 2 methods:
1. It's the most risky but has more chance of working. The idea is to flash the whole firmware again to the phone, but from an unlocked model.
This is posible using the EDL mode and Sahara protocol.
The EDL mode is an emergency mode which allows user to flash firmware in case fastboot and ADB fails. It's also available in all Qualcomm devices.
It is also completly independent from the rest of the phone, and it's the first bootloader we have. If everything is ok it triggers the second bootloader(fastboot) which then boots the system(See the diagram if you want).
As we want to reflash the firmware keep in mind this could brick your phone and I won't take any resposability if it happen
Materials:
-QPST
-Qualcomm Driver
-Working USB Cable
-Fastboot and ADB set up and working
-knoledge on using ADB
Procedure:
1. Download and install Qualcomm drivers
2. Download and install QPST
4.Downlaod the MBN file
3. Reboot
4. Connect the phone to the PC, then open cmd and run "adb reboot edl".
If you are on fastboot mode, then try "fastboot oem edl", "fastboot reboot-edl", "fastboot reboot edl". One of this should work
5. Go to C:\Program Files\Qualcomm\QPST\bin\
6.Open QPST Config(it's a blue phone, see picture)
7. Click on "Start clients" and then "Software download". A new window should open
8. Now we need to select the phone image using the browser button
9. Click on start to flash ⚡️
Please be aware the method wasn't tested, so this could brick your phone.
If you decide to try it, and have questions or ru into problems during the process, please let me know.
Also remember to take a backup of your data, as it is goig to be lost. ℹ
____________________________________________________________________________
As for the second method, I tried it and it didn't work for me, but is completly safe so you may want to give it a try.
1. Enrrol on the android 12 beta program, AND MAKE A BACKUP OF YOUR DATA
2. Install the update
3. Now exit from the beta program
4. Now you should have an update, it's a rollback to the stable version of android 12. After you installed the update the phone will restart and factory reset.
5. Do the setup as normal
In the end you may have unlocked the bootloader, to check just go to developer options and check if it is enabled or not.

			
				
Can we get a video of how to do this?
trzpro said:
View attachment 5491701
Click to expand...
Click to collapse
So you attempted one of these methods and did it work or not work.What device did you use?
trzpro said:
View attachment 5491701
Click to expand...
Click to collapse
That seems to be a probelm with the drivers. Did you install everything properly?
You may want to uninstall them and reinstall again to see if we solve the problem. Also try to run the app with admin privileges
Let me know how if you have more issues or if this doesn;t solve the problem at all.
AtrixHDMan said:
Can we get a video of how to do this?
Click to expand...
Click to collapse
I can make a video, but I can only publish it on January. Untill then I think the guide is easy to understand so if you want to try the method you shouldn't have problems.
#mcl said:
I can make a video, but I can only publish it on January. Untill then I think the guide is easy to understand so if you want to try the method you shouldn't have problems.
Click to expand...
Click to collapse
I understand thanks
#mcl said:
这似乎是驱动程序的问题。您是否正确安装了所有内容?
您可能需要卸载它们并重新安装,看看我们是否能解决问题。还尝试以管理员权限运行该应用程序
如果您有更多问题,或者这根本无法解决问题,请告诉我
MOD EDIT: You may need to uninstall them and reinstall to see if we can fix the problem. Also tried running the app with admin rights
Let me know if you have more questions, or if this doesn't solve the problem at all.
Click to expand...
Click to collapse
同样的问题,无法解决。
MOD Edit: Same problem, can't solve it.
Looks like this is a common issue, I will look the documentation of QPST and see if I see the cause of the problem. Thank you guys for helping up this project
So I found that that version of QPST is outdated(it's the 2.7 build 140 and the latest version is 2.7 build 460). I am leaving a zip with it here.
Try and see if this time around we manage to unlock the bootloader
MOD EDIT:
This is the latest version
这是最新版本
#mcl, I have the same problem as you have, I live in Portugal and bought a used Pixel 4 but apparently it's origin is the US, Verizon. From your original post I take it that you didn't try this method yourself and hope others will try? Or were you successful?
for anyone in the same situation, read this thread: https://android.stackexchange.com/q...ed-against-physical-tampering-in-google-pixel
My guess is: if your pixel's " OEM unlocking " is greyed out it will not be possible to unlock. Although I didn't try the EDL route I'm quit sure that at some point you will get a message "bootloader is locked"
gentle_giant said:
for anyone in the same situation, read this thread: https://android.stackexchange.com/q...ed-against-physical-tampering-in-google-pixel
My guess is: if your pixel's " OEM unlocking " is greyed out it will not be possible to unlock. Although I didn't try the EDL route I'm quit sure that at some point you will get a message "bootloader is locked"
Click to expand...
Click to collapse
Hey I am quite busy recently so I haven't really had time to look more on the thread, though I believe there will always be a way, it may be hard to find but no OS is perfect, and Android is no exception. As it turns out, even if this method worked, when it connect to the internet there will be a high chance that using the IMEI of the phone it will "remember" it's a locked model and won't allow you to flash new firmware.
However I am working on a new method, which is also safer, though I have still work to do, so when It is ready I am going to publish another guide.
Good luck all untill them
Hi mcl, my problem is: I do like to change OS and I did so on my previous HTC M7 and M10. And these 2 phones still function with PixelExperience 10 or 11.
But at best I'm a simple layman with a lot of enthusiasm.
Anyway, I will keep an eye on this thread and hopefully you will find time to make this new method work!
By the way, I see that we are "neighbors", I live in Portugal.
gentle_giant said:
Hi mcl, my problem is: I do like to change OS and I did so on my previous HTC M7 and M10. And these 2 phones still function with PixelExperience 10 or 11.
But at best I'm a simple layman with a lot of enthusiasm.
Anyway, I will keep an eye on this thread and hopefully you will find time to make this new method work!
By the way, I see that we are "neighbors", I live in Portugal.
Click to expand...
Click to collapse
Hahah yeah we are definitely neighbors.
Well I do want to become a software engineer though right now I am just a busy enthusiastic.
I also really enjoy custom OS, when I had my Galaxy S9 I used to have custom ROMs.
Hope I manage to find a new solution as soon as posible for all if you guys!!!

			
				
How is bootloader state protected against physical tampering in Google Pixel
A week ago my professor's Pixel 4 XL was stolen from his desk when he left it there for charging. The phone has been shut down. It had few minutes of battery left when it was plugged in charging. T...
android.stackexchange.com
any luck with that? can I backup my firmware before doing it?
darknmy said:
How is bootloader state protected against physical tampering in Google Pixel
A week ago my professor's Pixel 4 XL was stolen from his desk when he left it there for charging. The phone has been shut down. It had few minutes of battery left when it was plugged in charging. T...
android.stackexchange.com
Click to expand...
Click to collapse
We are not doing physical atack, so that is not a problem for us.
Also, I don't believe the pixel 4 XL is perfect, for sure there are errors and security vulnerabilities. We just need to find them.

Categories

Resources