Database Users

[OTA] Moto G 2014 XT1064 v22.21.25.en.us (5.0.1)

I just got the new OTA for Lolipop 5.0.1. I used ADB to pull the URL for the download and downloaded the attached ZIP using my browser. The URL pulled from ADB was an extremely long randomized string of characters that expired the moment my device was done updating. It seems the link is only active during the update process, so the only way to leave the link active longer is to battery pull or something in the middle of the update. I love you guys... but not that much
Keep in mind that this OTA was offered to me on 22.21.16, so I am assuming that you probably need to be on that update before you can use this OTA.
Let me know if you guys have any questions or run into any issues!

I'm rooted and running TWRP on my XT1064 with 22.21.16. Is there a way to just fastboot flash this update? I don't mind losing root. Thanks!

Okay, I had upgraded to 22.21.16 via TWRP using KennyWuLee's packaged tool. This morning I received a notice that I had an update available for 22.21.25. So like a dummy I went ahead and accepted. Now all it does is boot into TWRP. When I restart to system from TWRP it boots up just fine then after about 15 seconds reboots to TWRP.
I assume it is looking for the stock recovery which will then allow me to install the update? So will I be safe to go ahead and reflash the stock recovery, reboot and go from there? Or should I go all the way back to stock everything?
I have an XT1063.
Edit: I went ahead and flashed stock recovery and rebooted. After boot looping several times it rebooted into the system and gave me the message "Software update unsuccessful. There was a problem ....blah, blah, blah." But I still show an update available when I check.
I suspect it is because I am unlocked and rooted, even though I have stock recovery installed. Any thoughts on this guys? I am going to hold fast until I know for sure.

The update failed because you were rooted. You need a 100% stock /system since updates after 5.0 check the integrity of the filesystem before updating.

I may sound like a noob, but just to be sure..
Name of update says ".en.us".
Is it ok to use it for a french moto G 2d generation?
French will be available?
Thanks!!

DoubleIk said:
I may sound like a noob, but just to be sure..
Name of update says ".en.us".
Is it ok to use it for a french moto G 2d generation?
French will be available?
Thanks!!
Click to expand...
Click to collapse
Not sure if it makes a difference or not. I just put what the build was listed as when I got the update notification.
I put that there in case that was why some people couldn't update from 22.21.6 to 22.21.16

shishir95 said:
The update failed because you were rooted. You need a 100% stock /system since updates after 5.0 check the integrity of the filesystem before updating.
Click to expand...
Click to collapse
Nice theory, but I am now totally restored back to stock with stock recovery and unrooted. Still no luck with the update. Same thing happens.

I'm still stuck on 22.11.6, so I'm assuming I can't install this update until I'm on 22.21.16?

thisisjason said:
I'm still stuck on 22.11.6, so I'm assuming I can't install this update until I'm on 22.21.16?
Click to expand...
Click to collapse
From what I've seen, that is correct.

Any news XT1068 android 5.0.1 #India?

Moto G 2014 5.0.1
Hello good day friends will have some manual to perform the installation ?? and try it for apply update from ADB and I mark error in sideload package , installation aborted

How do I can install this update?

Problem with OTA update to B584

Hi,
I have an ALE-21 on B574, with bootloader unlocked, no root.
I received notification for a new update to B584. So I flashed stock recovery (was on TWRP) and launched the OTA update.
It went all the way to 100% download, but failed to install.
Is there a catch, did I forget something ?

Hmm... Did you have root at any point? What was the failure message that you got? Also, was your B574 rom modified or plain stock?

Hub00 said:
Hi,
I have an ALE-21 on B574, with bootloader unlocked, no root.
I received notification for a new update to B584. So I flashed stock recovery (was on TWRP) and launched the OTA update.
It went all the way to 100% download, but failed to install.
Is there a catch, did I forget something ?
Click to expand...
Click to collapse
Try it once again... I've never received OTA updates from b560 onwards.. You could flash your way through

crashpoum99 said:
Hmm... Did you have root at any point? What was the failure message that you got? Also, was your B574 rom modified or plain stock?
Click to expand...
Click to collapse
I had root to enable the pseudo-gyroscope and then unrooted (with some pain) to play Pokemon go.
The B574 is stock, I got it through OTA last time (september if I remember correctly).
I tried changing the source of the stock recovery, but it did'nt work either. The failure message comes after reboot : it's a EMUI notification "last update failed".

Hub00 said:
I had root to enable the pseudo-gyroscope and then unrooted (with some pain) to play Pokemon go.
The B574 is stock, I got it through OTA last time (september if I remember correctly).
I tried changing the source of the stock recovery, but it did'nt work either. The failure message comes after reboot : it's a EMUI notification "last update failed".
Click to expand...
Click to collapse
You can try local update......And preferably Force update but it will delete all your data so backup your data And Force update........ Btw leave B584 because B588 is avaiable

Hub00 said:
I had root to enable the pseudo-gyroscope and then unrooted (with some pain) to play Pokemon go.
The B574 is stock, I got it through OTA last time (september if I remember correctly).
I tried changing the source of the stock recovery, but it did'nt work either. The failure message comes after reboot : it's a EMUI notification "last update failed".
Click to expand...
Click to collapse
I would try force updating using the Power+Vol.Up+Vol.Down method. Go for B588 if you want, as it's newer with the latest security patch. If the error comes after the reboot, it's most likely that force updating will fix this. Remember, force updating will delete your files!

What actually worked is downloading 'full package' in the update menu (the file was 1.56Go instead of 260 Mo). It updated overnight even with twrp. Of course, I lost gyroscope in the process...
So I'm know with B584. I will try to force update to B588 as soon as it is downloaded.

Ok, i'm know on B588 and I have gyroscope back again. Thanks for your help.
However, despite the changelog, i didn't notice any improvement with the whatsapp notifications.
Any idea why ?

(ALE-L21) Installed firmware B564, still on Lollipop 5.0

Hi,
I have a problem and hope you can help me. I did quite a bit of rooting and installing custom roms on other devices but this was my first try on a Huawei.
I wanted to install a custom rom. The phone was on Lollipop 5.0 (can't remember what firmware it was on). I installed TWRP, did a backup, looked up a rom online and got stuck on boot. So I restored my backup, did some more research and found out that it is possible to upgrade to Marshmallow with an official system update manually.
I then checked what firmware it was running: balongV100R001C50b311. I looked online for the stock recovery for that version, flashed it, then flashed a vendor upgrade to get away from the balong-version (was recommended in another forum in order to be able to upgrade to MM).
So now: I'm on Firmware version ALE-L21C432B564. The thing is, I'm still on Lollipop 5.0. As I understand it, B564 is a MM firmware. I flashed the recovery of B564 for manual updates (via Huawei update extractor), but I still can't do a local update (via dload) to B565 or B574. I tried to manually install the update to B564 again, hoping it would upgrade my Android version to MM, but no luck. It just gives me the error: 'Software install failed!'.
I couldn't find anything online about being on B564 and still running Lollipop. I hope some of you can help.
Thanks in advance

tostre said:
Hi,
I have a problem and hope you can help me. I did quite a bit of rooting and installing custom roms on other devices but this was my first try on a Huawei.
I wanted to install a custom rom. The phone was on Lollipop 5.0 (can't remember what firmware it was on). I installed TWRP, did a backup, looked up a rom online and got stuck on boot. So I restored my backup, did some more research and found out that it is possible to upgrade to Marshmallow with an official system update manually.
I then checked what firmware it was running: balongV100R001C50b311. I looked online for the stock recovery for that version, flashed it, then flashed a vendor upgrade to get away from the balong-version (was recommended in another forum in order to be able to upgrade to MM).
So now: I'm on Firmware version ALE-L21C432B564. The thing is, I'm still on Lollipop 5.0. As I understand it, B564 is a MM firmware. I flashed the recovery of B564 for manual updates (via Huawei update extractor), but I still can't do a local update (via dload) to B565 or B574. I tried to manually install the update to B564 again, hoping it would upgrade my Android version to MM, but no luck. It just gives me the error: 'Software install failed!'.
I couldn't find anything online about being on B564 and still running Lollipop. I hope some of you can help.
Thanks in advance
Click to expand...
Click to collapse
Why you don't just update it from the system updates, you know?
I have EMUI 3.1 too but I received an MM update right when I flashed it

XTutorials said:
Why you don't just update it from the system updates, you know?
I have EMUI 3.1 too but I received an MM update right when I flashed it
Click to expand...
Click to collapse
You mean Settings->Updater->Check for Updates? It tells me there are no updates. It did so even before I started fiddling with it

tostre said:
You mean Settings->Updater->Check for Updates? It tells me there are no updates. It did so even before I started fiddling with it
Click to expand...
Click to collapse
Reset on factory settings, maybe you it will find it? In what region you are?

XTutorials said:
Reset on factory settings, maybe you it will find it? In what region you are?
Click to expand...
Click to collapse
Factory reset doesn't change anything, unfortunately. Still on B564, Lollipop. The region is Europe.
One more thing that could be helpful: The device is unrooted

tostre said:
Factory reset doesn't change anything, unfortunately. Still on B564, Lollipop. The region is Europe.
One more thing that could be helpful: The device is unrooted
Click to expand...
Click to collapse
But you have TWRP. Download B596 update.zip (you will find a thread in "general" section), then restart to TWRP, go to wipe~advanced wipe~ tick Data, system, dalvik/art cache and cache (Be sure to have backup!) and click wipe. Then flash B596 update.zip that you have downloaded

XTutorials said:
But you have TWRP. Download B596 update.zip (you will find a thread in "general" section), then restart to TWRP, go to wipe~advanced wipe~ tick Data, system, dalvik/art cache and cache (Be sure to have backup!) and click wipe. Then flash B596 update.zip that you have downloaded
Click to expand...
Click to collapse
Hm, I read somewhere that flashing an update only works with the stock recovery. But I'll give it a try, thanks

XTutorials said:
But you have TWRP. Download B596 update.zip (you will find a thread in "general" section), then restart to TWRP, go to wipe~advanced wipe~ tick Data, system, dalvik/art cache and cache (Be sure to have backup!) and click wipe. Then flash B596 update.zip that you have downloaded
Click to expand...
Click to collapse
Well, I flashed it via TWRP. Even though it aborted at "Writing radio" or something like this and gave me an unknown error, it seems to have worked.
I'm now on B596, Android 6.0. This device is killing me Thank you very much for your help

tostre said:
Well, I flashed it via TWRP. Even though it aborted at "Writing radio" or something like this and gave me an unknown error, it seems to have worked.
I'm now on B596, Android 6.0. This device is killing me Thank you very much for your help
Click to expand...
Click to collapse
My pleasure

[SOLVED] Huawei nova bricked

I folowed this tutorial https://forum.xda-developers.com/nova-plus/development/rom-aospextended-v4-6-t3717372 and all flashing was fine. Due to some inconveniences of this new flashed rom i decided to restore to default rom. I extracted recovery and update.app version Can-L11 B396 i think from firmware finder and flased with adb this recovery. After that, it asked me to do an factory reset, i did it, but it wont boot any of huawei or Aosp Extended. The main problem i have is i can`t acces any more my phone with adb terminal, maybe after flashing the new original recovery usb debbuging reverted to un-enabled. How can I do now? Thanks in advance.

campeadore said:
I folowed this tutorial https://forum.xda-developers.com/nova-plus/development/rom-aospextended-v4-6-t3717372 and all flashing was fine. Due to some inconveniences of this new flashed rom i decided to restore to default rom. I extracted recovery and update.app version Can-L11 B396 i think from firmware finder and flased with adb this recovery. After that, it asked me to do an factory reset, i did it, but it wont boot any of huawei or Aosp Extended. The main problem i have is i can`t acces any more my phone with adb terminal, maybe after flashing the new original recovery usb debbuging reverted to un-enabled. How can I do now? Thanks in advance.
Click to expand...
Click to collapse
Check this post.

I cant access my phone via adb or twrp recovery. I wonder why. Before flashing a stock recovery all Was fine, adb Was connecting with no problem.

campeadore said:
I cant access my phone via adb or twrp recovery. I wonder why. Before flashing a stock recovery all Was fine, adb Was connecting with no problem.
Click to expand...
Click to collapse
Try to flash the TWRP again with fastboot.
PS: I don't understand how you people end up like this. It never happened to me.

I cant, adb cant be connected to device. Says null operation.

finally i succeed to revert o stock rom. Now i have on About phone CAN-L11C432B397, Emui 5.0 and Android 7.0. One question please, I dont see anymore the Update system tab or something, "Actualizator" on romanian language. Is that normal? How i can check for updates?

campeadore said:
finally i succeed to revert o stock rom. Now i have on About phone CAN-L11C432B397, Emui 5.0 and Android 7.0. One question please, I dont see anymore the Update system tab or something, "Actualizator" on romanian language. Is that normal? How i can check for updates?
Click to expand...
Click to collapse
You need to install the other zip too which has the word "data_full" at zip's name or something like that.
EDIT: @campeadore, i suggest you to edit the thread name and add "[SOLVED]" at begin and write the way you've fixed your phone (the solution), so it'll help other people who might run into the same problem as you.

I`ll do it as soon i fully resolve the problem. I followed your link and everything went fine at step 1 (Go back to EMUI 4.1 (MM). System is booting, but system update is not working. So, i want to flash EMUI 5, but can-l11c432b330 or can-l11c432b396 cant be updated, around 45% gives an error. The only version who work is can-l11c432b320 but i dont have update_full_CAN-L11_hw_eu, only the first update.zip.

campeadore said:
I`ll do it as soon i fully resolve the problem. I followed your link and everything went fine at step 1 (Go back to EMUI 4.1 (MM). System is booting, but system update is not working. So, i want to flash EMUI 5, but can-l11c432b330 or can-l11c432b396 cant be updated, around 45% gives an error. The only version who work is can-l11c432b320 but i dont have update_full_CAN-L11_hw_eu, only the first update.zip.
Click to expand...
Click to collapse
Newer / newest firmware downloaded from Firmware Finder needs to be approved by Huawei and that can take some time. It's failing to install because it wasn't approved. I've read this in past somewhere.
Try B381 or B382 as i've always installed that one when i've went back to EMUI 5.

Yes, i did it now with can-l11c432b330. I think my mistake was trying to flash to EMUI5 with usb cable connected. With cable off all went fine like a charm. Now i do all approved updates with system update. Thank you so much man, really appreciated.

Seeking help: I have a smartphone huawei nova lite plus (TRT LX1) that fails to restart. It goes continuously in a loop. Entering recovery only the first 2 functions come out: wipe wash factory reset and wipe wash partition. Then using eRecovery from PC with the USB cable, proceed up to a certain point and then not continue. I think it's in soft brick. I definitely need the right software for flashing, stock roms and usb drivers. Where can I find them? Many thanks

Problems to update

Hi!!
I'm having problems to update from android 8.0.0. My phone is no rooted, the bootloader is open (I have learned that it's so expensive to close it xD xD, when you close it the phone makes briked) and when the update is downloading and the phone needs to reboot to install it, I can't because apears TWRP and I can't to install from here, and I don't find the normal or stock recovery to install it.
What can I do?
Thanks in advance!

You can flash this in twrp just like any other rom.
https://forum.xda-developers.com/lg-g6/development/rom-eu-lg-h870-20a-rom-t3794503

I had my phone unlocked and rooted with Fulmics 4.2 onboard.
Right when Oreo dropped, I locked my phone and flashed the update straight away.
No brick occured.

Alpha-Retard said:
You can flash this in twrp just like any other rom.
https://forum.xda-developers.com/lg-g6/development/rom-eu-lg-h870-20a-rom-t3794503
Click to expand...
Click to collapse
So I not need another OS, in fact, I have this oreo installed, but when the system sais that there are updates (now I have one update pending of 700mb) and when it's need reboot for install, this can't finish because TWRP appear, and doesn't let it finish to install the update...
I don't know exactly what I need to do, and I don't want to lose mine actual OS.
Could be possible to update the updates, likely manual mode or similar? Without reboot the phone and avoid the reboot and pass by twrp?
Thanks again