Develop Bugs

System update not showing

Hi !
I bought an asus zenfone 2 ZWE551ML - Z00ADA from china , and it cames with android 5.0 LRX21V.WW-ASUS_Z00A-2.19.40.18 firmware.
The problem is that , the device cames already rooted , and the system update it´s not showing in settings-> about . I also search for system update app , and i don´t have it in app drawer . I think my phone cannot be updated with OTA , right ?
I´m stuck here . I tried to search in this forum, but i didn´t found an answer .
Can anyone help me to solve this problem ?
thanks in advance

Yes, you cant update until you unroot, then you have to download update .97 and update via ota to .139

ElmirBuljubasic said:
Yes, you cant update until you unroot, then you have to download update .97 and update via ota to .139
Click to expand...
Click to collapse
I already unroot . I´ve also factory reset the device .
I´m trying now to find the firmwares in the asus forum , but i cannot find it . It´s also in xda the version .97 ?
I´ve checked the bootloader , and it says that is " unknown " . This problem is related ?
thanks
PS: I found the firmwares

I´ve downloaded the version .97 ww , and now i have to flash this ?
Type fastboot flash fastboot droidboot.img (be very careful in writting this line). Hit Enter. Wait till it's done.
Type fastboot flash recovery recovery.img and hit Enter. Wait till it's done.
Type fastboot flash boot boot.img and hitEnter. Wait till it's done.
thanks

Please can anyone help me ?
Thanks
Enviado do meu ASUS_Z00AD através de Tapatalk

Tuga2010 said:
Please can anyone help me ?
Thanks
Enviado do meu ASUS_Z00AD através de Tapatalk
Click to expand...
Click to collapse
Put in adb folder and do sideload

ElmirBuljubasic said:
Put in adb folder and do sideload
Click to expand...
Click to collapse
I´ve also done that of my own risk, and the recovery did not detected the device . I tried to push the firmware but gives me " timeout ... " i don´t remember the rest . I have adb version 1.0.32, i think is the latest.
I have to do a reboot , to get back to the fastboot mode.
Although In the fastboot , my device is detected
The problem is related to the recovery ? Can i flash something in fastboot mode ? it´s a problem in abd ?
thanks in advance

Tuga2010 said:
I´ve also done that of my own risk, and the recovery did not detected the device . I tried to push the firmware but gives me " timeout ... " i don´t remember the rest . I have adb version 1.0.32, i think is the latest.
I have to do a reboot , to get back to the fastboot mode.
Although In the fastboot , my device is detected
The problem is related to the recovery ? Can i flash something in fastboot mode ? it´s a problem in abd ?
thanks in advance
Click to expand...
Click to collapse
probably problem with adb, use windroid to sideload and you must wait at least 1 hr to finish, its gonna take time or simply put the firmware in rood of interna memory and phone will detect it at next reboot

ElmirBuljubasic said:
probably problem with adb, use windroid to sideload and you must wait at least 1 hr to finish, its gonna take time or simply put the firmware in rood of interna memory and phone will detect it at next reboot
Click to expand...
Click to collapse
i´ve tried to copy the firmware to the root folder but i have " permission denied " . I only can copy to the sdcard folder .
I think it´s related to have now an unrooted device right ?
I will try with windroid later
thanks

I´m trying to use windroid , and when i click in " sideload zip " it says that i have to had twrp instaled . My recovery is the stock recovery , not twrp
Can i keep going forward ?

Tuga2010 said:
i´ve tried to copy the firmware to the root folder but i have " permission denied " . I only can copy to the sdcard folder .
I think it´s related to have now an unrooted device right ?
I will try with windroid later
thanks
Click to expand...
Click to collapse
no, just follow this asus istructions http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE500KL/Software_Update_SOP_V3.pdf

ElmirBuljubasic said:
no, just follow this asus istructions http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE500KL/Software_Update_SOP_V3.pdf
Click to expand...
Click to collapse
I followed these indications and no notification in my device . Tried also to reboot the phone , the same result.

go to stock recovery, it should detect it from there, if not go sideload it

ElmirBuljubasic said:
go to stock recovery, it should detect it from there, if not go sideload it
Click to expand...
Click to collapse
I´m now sideloading the .97 firmware . I´ve instaled adb files all over again , and now my device as indeed been detected in recovery .
I´m upgrading now , i hope it works

Problem solved . Next I flashed the latest firmware ( .139 ) , and all went well .
thank for your help
regards

Tuga2010 said:
Problem solved . Next I flashed the latest firmware ( .139 ) , and all went well .
thank for your help
regards
Click to expand...
Click to collapse
i have exactly the same problem.
i tried side loading .97, but after the device reboots into service mode it comes up with Error!
What would be the next step?

tommy4q said:
i have exactly the same problem.
i tried side loading .97, but after the device reboots into service mode it comes up with Error!
What would be the next step?
Click to expand...
Click to collapse
you have to press vol up and power few times to see the menu

ElmirBuljubasic said:
you have to press vol up and power few times to see the menu
Click to expand...
Click to collapse
I think I am having similar problem,.
I got a new phone and checked for updates. It updated to 2.20.40.97 version (~220Mb). Then I rooted it using "Method 3".
After this I again checked for update and it showed 2.20.40.160 was available (~221Mb). Downloaded it but it gave error when installing.
The phone is booting fine but now it shows no updates. I tried factory reset and also clear cache but no update is shown in System->Check Updates
Now I have tried to adb sideload the OTA updates after 2.20.40.97 and all are getting stuck up after some time. The updates are 160 and 105Mb long. I tried to sideload 2.20.40.97 itself which was just 35mb and that worked.
What should I do to resolve the problem?

You have root... You can't be rooted when doing an update over OTA...

jesrani said:
I think I am having similar problem,.
I got a new phone and checked for updates. It updated to 2.20.40.97 version (~220Mb). Then I rooted it using "Method 3".
After this I again checked for update and it showed 2.20.40.160 was available (~221Mb). Downloaded it but it gave error when installing.
The phone is booting fine but now it shows no updates. I tried factory reset and also clear cache but no update is shown in System->Check Updates
Now I have tried to adb sideload the OTA updates after 2.20.40.97 and all are getting stuck up after some time. The updates are 160 and 105Mb long. I tried to sideload 2.20.40.97 itself which was just 35mb and that worked.
What should I do to resolve the problem?
Click to expand...
Click to collapse
Finally had to flash the recovery images as well as the complete ROM (2.20.40.160) through ADB and this worked. Phone now updated.

Mobile not turning on after flashing. pls help

Hi I was on Pixel Experience ROM then I flashed MIUI 9.5.17 via Recovery TWRP 3.2.2.0 with clean flash (i.e. dalvik cache, data, system and internal storage wiped)
but Now mobile is dead its not even turning on. What should I do please help

Flash lazyflasher.
I think this thread provide a compatible version.
https://forum.xda-developers.com/an...zip-lazyflasher-tool-flashing-custom-t3549210
Or from here: -
https://forum.xda-developers.com/showpost.php?p=76904750&postcount=146

Device Manager is showing this
1
corkiejp said:
Flash lazyflasher.
I think this thread provide a compatible version.
https://forum.xda-developers.com/an...zip-lazyflasher-tool-flashing-custom-t3549210
Or from here: -
https://forum.xda-developers.com/showpost.php?p=76904750&postcount=146
Click to expand...
Click to collapse
Qualcomm HS-USB QDLoader 9008 (COM3)

follow this guide:
https://forum.xda-developers.com/redmi-note-5-pro/how-to/guide-redmi-note-5-pro-unbrick-t3816178

huttui said:
Hi I was on Pixel Experience ROM then I flashed MIUI 9.5.17 via Recovery TWRP 3.2.2.0 with clean flash (i.e. dalvik cache, data, system and internal storage wiped)
but Now mobile is dead its not even turning on. What should I do please help
Click to expand...
Click to collapse
huttui said:
1
Qualcomm HS-USB QDLoader 9008 (COM3)
Click to expand...
Click to collapse
mmhuseyni said:
follow this guide:
https://forum.xda-developers.com/redmi-note-5-pro/how-to/guide-redmi-note-5-pro-unbrick-t3816178
Click to expand...
Click to collapse
He flashed a safe MIUI version, so should have not triggered ARP!

Solution needed
corkiejp said:
He flashed a safe MIUI version, so should have not triggered ARP!
Click to expand...
Click to collapse
Please provide solution asap

huttui said:
1
Qualcomm HS-USB QDLoader 9008 (COM3)
Click to expand...
Click to collapse
I think you are in edl mode right now. You can try to flash the 9.5.17 ROM (use the fastboot ROM, not recovery ROM) with MiFlash tool.
edit: If you are not in edl mode, try to enter fastboot and put this code "fastboot oem edl" to enter edl mode.

Tried it
finsx said:
I think you are in edl mode right now. You can try to flash the 9.5.17 ROM (use the fastboot ROM, not recovery ROM) with MiFlash tool.
edit: If you are not in edl mode, try to enter fastboot and put this code "fastboot oem edl" to enter edl mode.
Click to expand...
Click to collapse
Everytime I flash With MIFLASH Tool i end up with this
I have tried this methods on fastboot rom version 9.5.17, 9.5.14 and global beta 8.7.12
but nothing works results are same

huttui said:
Everytime I flash With MIFLASH Tool i end up with this
I have tried this methods on fastboot rom version 9.5.17, 9.5.14 and global beta 8.7.12
but nothing works results are same
Click to expand...
Click to collapse
Never faced something like that so i looked at google and found some solutions.
1. Try to use test point, flash the ROM.
2. Unplug the battery and charge it with wall charger to get some juices, then plug it again, enter edl, then flash the ROM.
3. Just unplug the battery, enter edl mode, flash the ROM.
4. The worst solution and also the last, take it to the service center, hope they could help you fix your device.
I still have to wait 10 days to unlock bootloader, so i have not tried to enter edl mode with this Whyred yet. Don't know if the edl mode even works in Whyred.
edit:
5. Try to use beta version of MiFlash, because i have tried to unlock bootloader before, the newest version cannot detect my phone, so i used the old one.
6. Use the 64 bit version of windows.

huttui said:
Hi I was on Pixel Experience ROM then I flashed MIUI 9.5.17 via Recovery TWRP 3.2.2.0 with clean flash (i.e. dalvik cache, data, system and internal storage wiped)
but Now mobile is dead its not even turning on. What should I do please help
Click to expand...
Click to collapse
Hii...bro am in exact same situation right now. Did u solve it? Did u find any method to do?

What version of miui you had installed before pixel?

have you flashed any beta versions after 8.7.5 like 8.7.12, 8.7.26, 8.8.2 etc? If yes, then your device has triggered anti rollback and can only be resurrected using authorized mi account or change of motherboard.

EDL mode is disabled in whyred through fastboot command. You'll have to proceed with test point method to enable edl (I've seen in many threads which points to only test point method for edl) and then flash the rom which was there before you flashed PE.
Or, you should take help from service center.
If you can remember ARB3 before PE, then 9.5.17 will work but if you are not sure (like miui used to download the 9.5.19 rom automatically in wifi and a single reboot will upgrade you to ARB4 without your consent and then you wouldn't know it before it's too late and to avoid that, revoking updater authorization in the settings would be the only way to disable downloading ota in wifi ) , then you should flash 9.5.19 otherwise downgrade arb will brick your phone. Also, it s not clear whether you have bricked it while flashing 9.5.17 after PE which was a common reason when people downgraded from 9.5.19 to 9.5.17.

animeshsahood6 said:
Hii...bro am in exact same situation right now. Did u solve it? Did u find any method to do?
Click to expand...
Click to collapse
You have bricked your device by downgrading from arb4 to arb3. go to mi service center to get your mother board replaced as soon as possible..

epicwarlock said:
You have bricked your device by downgrading from arb4 to arb3. go to mi service center to get your mother board replaced as soon as possible..
Click to expand...
Click to collapse
Its covered under warranty r8?

animeshsahood6 said:
Its covered under warranty r8?
Click to expand...
Click to collapse
If you go to xiaomi authorised service centre then it is covered under warranty..

Lucky
animeshsahood6 said:
Hii...bro am in exact same situation right now. Did u solve it? Did u find any method to do?
Click to expand...
Click to collapse
Luckily for me mi service centre replaced the board for free as it was in warranty. try your luck. i told them it stuck during miui10 update.

How can i flash twrp again?

I had unlocked the bootloader and then, flashed global stable, but unfortunately, the mtp (and by the way, fastboot and adb access from a pc) was somehow disabled, and to complete the disgrace package, i have just the original mi recovery. I'm currently at the lastest global stable rom, 10.2, without any hope. What can i do?

jvictor852 said:
I had unlocked the bootloader and then, flashed global stable, but unfortunately, the mtp (and by the way, fastboot and adb access from a pc) was somehow disabled, and to complete the disgrace package, i have just the original mi recovery. I'm currently at the lastest global stable rom, 10.2, without any hope. What can i do?
Click to expand...
Click to collapse
can you enter fastboot. if so then
flash a fstboot rom same ARB as your last .. using miflash tools.

raptorddd said:
can you enter fastboot. if so then
flash a fstboot rom same ARB as your last .. using miflash tools.
Click to expand...
Click to collapse
No, i can surely enter on fastboot but it wont connect to pc. By the way it just dont works.

is your problem solved? Because I'm also facing this same issue and i have tried almost everything which i could.
I'm on MIUI latest version and I'm trying to downgrade miui verision to 10.2 through OTA updates in order to fix it but it's showing downgrading is not allowed and I'm completely stucked.
Plz if anyone know to solv this out kindly let me know.
As issue says MTP not working i also can't flash TWRP recovery from fastboot and since i'm on stock rom, my phone can't be rooted and i can't edit build.prop file to enable mtp.
Thanks.

TheDeaDKiLLer said:
is your problem solved? Because I'm also facing this same issue and i have tried almost everything which i could.
I'm on MIUI latest version and I'm trying to downgrade miui verision to 10.2 through OTA updates in order to fix it but it's showing downgrading is not allowed and I'm completely stucked.
Plz if anyone know to solv this out kindly let me know.
As issue says MTP not working i also can't flash TWRP recovery from fastboot and since i'm on stock rom, my phone can't be rooted and i can't edit build.prop file to enable mtp.
Thanks.
Click to expand...
Click to collapse
Lol win10 is a bad joke... use usb2.0 hub or search for reg fix on xda forum. Or use win7 or linux.
And there is few versions of fastboot.

[SOLVED] chinese variant to Global NEED HELP!!!

Hi!
i installed the global rom via TWRP recovery
now when i try to set up new device all i get is chinese region
Then i hit next and started looping for some reason and message showing "Find Device Automatically Closed"
After multiple loops it restarts and the TWRP is gone
i tried multiple Roms all the same
if anyone has a clue please help
The solution : use MiFlash not TWRP and careful just flash not flash and lock you might get into a bootloop if you made that mistake just like i did don't panic use Mi Unlock
After it reboots setup your device say goodbye to Chinese bloatware.
Thx @nhtnokia

Flash cust.img or use MiFlash to flash stock ROM.

nhtnokia said:
Flash cust.img or use MiFlash to flash stock ROM.
Click to expand...
Click to collapse
I cant find firmware .img i only found Tgz file type
i have done a backup before flashing i get file types .win001.sha2

faroukxda said:
I cant find firmware .img i only found Tgz file type
i have done a backup before flashing i get file types .win001.sha2
Click to expand...
Click to collapse
I think you should use MiFlash to change from CHINA to the GLOBAL version.

nhtnokia said:
Flash cust.img or use MiFlash to flash stock ROM.
Click to expand...
Click to collapse
nhtnokia said:
I think you should use MiFlash to change from CHINA to the GLOBAL version.
Click to expand...
Click to collapse
i think i screwed up very bad. i flashed and locked with miflash now it goes directly to recovery
saying miui vesion isn't supported
is there any way that i can reflash a locked device to stock firmware " Hard Reset" ?

faroukxda said:
i think i screwed up very bad. i flashed and locked with miflash now it goes directly to recovery
saying miui vesion isn't supported
is there any way that i can reflash a locked device to stock firmware " Hard Reset" ?
Click to expand...
Click to collapse
If your bootloader is still unlocked. I can help you. Let's inbox me.

nhtnokia said:
If your bootloader is still unlocked. I can help you. Let's inbox me.
Click to expand...
Click to collapse
check DM

Question Soft bricked my phone

Hello everyone i have a trouble with my poco f3.
I tryed to unlock the Bootloader with the xiaomi utilities, i waited 7 days and clicked on unlock everything was fine till the phone reboot and then did a bootloop.
i tryed to flash a rom stock with fastboot and xiaomi flash, but everytime after the flash my phone get stuck on the poco logo....
I tryed to install twrp but when i launch adb in cmd it say "device null not found"
i really need some help please...
Thank you

If you already unlock bootloader read this thread maybe helpfully
Bricked device?
I tried to flash Evolution X 5.9. I came from the latest Xiaomi.eu stable (12.5.4). Followed the installing instructions (flash via twrp/ format data), but after reboot, i got a "no command" error message. I then tried to flash the original F3...
forum.xda-developers.com
Try to install another fastboot ROM

To flash a fastboot rom wich driver i need ? Bootloader ? Adb ? Qualcomm ?

Georgebabush said:
To flash a fastboot rom wich driver i need ? Bootloader ? Adb ? Qualcomm ?
Click to expand...
Click to collapse
U need adb ... To flash something bro respect from Georgia for trying to Unlock bootloader on f3

(Gugucha) said:
U need adb ... To flash something bro respect from Georgia for trying to Unlock bootloader on f3
Click to expand...
Click to collapse
Well i tryed to flash syberia fastboot, i tryed like one hundred time and this time, it worked i dont know why.....
I'll maybe try to reflash the EEA rom if i dont like Syberia, it's the only rom that worked
Thanks for your help all !

Georgebabush said:
Well i tryed to flash syberia fastboot, i tryed like one hundred time and this time, it worked i dont know why.....
I'll maybe try to reflash the EEA rom if i dont like Syberia, it's the only rom that worked
Thanks for your help all !
Click to expand...
Click to collapse
Good job nice to hear that where are u from ? anyways ?

Georgebabush said:
Well i tryed to flash syberia fastboot, i tryed like one hundred time and this time, it worked i dont know why.....
I'll maybe try to reflash the EEA rom if i dont like Syberia, it's the only rom that worked
Thanks for your help all !
Click to expand...
Click to collapse
Great to hear you solved the problem