Develop Bugs

[XT1068] Lollipop with Dual-SIM working!

I did some tricks (like I did before on XT1033->XT1032 variant) and it worked like a charm!!! I'm uploading at this time a flashable zip. I'll post instructions after upload.
There's some screenshots attached.
[]'s
Installation steps:
1) Flash RETUAWS_XT1064_4.4.4_KXB21.85-17_cid9_CFC without flashing fsg.mbn (if you're on another firmware, you'll get errors on install process)
Important: Do not flash fsg.mbn or you will have NO SIGNAL after installation and need to flash XT1068/XT1069 fsg.mbn back after the process to get signal back.
2) Install custom recovery (CWM, TWRP, etc...)
3) Download and install update_nofsg.zip via recovery.
4) Wipe cache/data.
5) If you doesn't get any error message at install process, reboot and wait... (it's around 5 minutes first startup)
update-nofsg-working.zip - https://drive.google.com/open?id=0B3o5NziVM8e5UU9QRjNaYzJQeG8&authuser=0
(I bring back this file because someone said to me that this is working and sent to me screenshots.)
Problems with file permissions. When I get home, I'll fix this.
Magically it's working again. =O
Buglist:
1) no sim selector activity, you need to select a single sim for voice calls (I'm working on this)
Working receive calls from both SIMs

Finally lollipop for xt1058!!

Thanks so much for sharing this.
However, since you can't upload the file right now, would you be able to give a short step by step (I'd gladly take bullett points without long descriptions just as a guideline).
Also: Does it require root? Unlocked phone?
Thanks again!

ffosilva said:
I did some tricks (like I did before on XT1033->XT1032 variant) and it worked like a charm!!! I'm uploading at this time a flashable zip. I'll post instructions after upload.
There's some screenshots attached.
[]'s
PS: See my reputation before saying that this trick is fake. =P
PS2 - AND IMPORTANT! You need to flash RETUAWS_XT1064_4.4.4_KXB21.85-17_cid9_CFC without fsg.mbn image. (keep stock fsg image)
OK:
I can't upload right now the flashable zip (i'm using 3G right now). The trick is adding these lines to end of /system/build.prop file:
persist.radio.multisim.config=dsds
persist.multisim.config=dsds
And flashing back fsg.mbn from stock firmware.
[]'s
Click to expand...
Click to collapse
eagerly waiting

Will there be any drawbacks in installing this ROM? Maybe more battery drain or something?

Use your head, search and read, don't just ask. You're a Senior Member!! Use google to search Project Volta.

Hey, I'm Brazilian too! Parabéns, cara, haha! What have you done? Flashed 4.4.4 image from xt1063 into xt1068, upgraded to lollipop and then just edited the build.prop?

Will Mobile Network eventually work in Europe? Since I'm still waiting for Lollipop to arrive on my XT1068

@samcortez after that, you must flash your original (mean from your original stock KK software) fsg.mbc using mfastboot.

Step by step or a zip file would be awesome, I might try this later

cant wait you upload zip file :good:

Adaho0 said:
Use your head, search and read, don't just ask. You're a Senior Member!! Use google to search Project Volta.
Click to expand...
Click to collapse
Jesus. Jump the gun much? I asked if installing this rom would have some drawbacks. Learn english and then come back to me.

nqddnwhb said:
cant wait you upload zip file :good:
Click to expand...
Click to collapse
Uploading right now.

I have rooted the phone. Please included the steps to flash a rooted XT1068.
Thanks

Great work! É DO BRASIL! hahaha
The flashable file...I have to root my device and flash through recovery, or I can just sideload it via adb?
thx!

ffosilva said:
Uploading right now.
Click to expand...
Click to collapse
So we can falsh it from recovery like a ROM ? Thanks for your great work!

ffosilva said:
I did some tricks (like I did before on XT1033->XT1032 variant) and it worked like a charm!!! I'm uploading at this time a flashable zip. I'll post instructions after upload.
There's some screenshots attached.
[]'s
PS: See my reputation before saying that this trick is fake. =P
PS2 - AND IMPORTANT! You need to flash RETUAWS_XT1064_4.4.4_KXB21.85-17_cid9_CFC without fsg.mbn image. (keep stock fsg image)
OK:
I can't upload right now the flashable zip (i'm using 3G right now). The trick is adding these lines to end of /system/build.prop file:
persist.radio.multisim.config=dsds
persist.multisim.config=dsds
And flashing back fsg.mbn from stock firmware.
[]'s
Click to expand...
Click to collapse
Thnx for u r effort buddy :thumbup:
Can u tell me how to downgrade from KXB21.85-23 to 21.85-17.
And is downgrade possible because i tried to downgrade to 85-17 earlier for retaildsdsall.en03.retin. It kept giving me errors while downgrading.
Because i m currently on the KXB21.85-23 build.
As u have told that we need to flash The
RETUAWS_XT1064_4.4.4_KXB21.85-17_cid9_CFC. That means its a downgrade to a US firmware.
Plzz provide the steps
I will be grateful to you..

I can't imagine that the AWS version of the USA firmware would be the only one that this could be used with. I'd think that the global GSM variant would be a better fit for non USA owners, in fact:
"Blur_Version.21.11.17.titan_retuglb.retuglb.en.US"
(glb = global)
Thoughts?

I got no signal issue. Solving before send another zip. Wait some minutes.

Where do i need to edit the build.prop ???
On the RETAILAWS or after flashing Lollipop update zip.
I m very much confused...
Plzzz give step by step instructions..

v521 - downgrade from 7.0 to 6.0

Is this possible?
I tried several ways via LGUP and uppercut one and it would just error out. Also tried flashing "pioneer" 6.0 rom, which works fine but my LTE keep dropping in and out. I assumed that is because I am still on a 7.0 Baseband?
If so, can i downgrade to a 6.0 baseband ?
Please help

I was in the same situation, and this is what I did:
1. using WindowsLGFirmwareExtract-1.2.6.1, extract dz from 10c kdz file.
2. extract modem?????.bin from dz file. (do't remember the exact name)
3. copy this modem???.bin to /sdcard
4. in TWRP, open terminal
5.
Code:
dd if=/sdcard/modem???.bin of=/dev/block/bootdevice/by-name/modem bs=512
6. reboot
And for LGUP error, you need a updated LGUP_c.dll, the 6.0 dll is not compatible with 7.0 downloader.
extract it from 20f(7.0) kdz file and try LGUP again.

yaana said:
I was in the same situation, and this is what I did:
1. using WindowsLGFirmwareExtract-1.2.6.1, extract dz from 10c kdz file.
2. extract modem?????.bin from dz file. (do't remember the exact name)
3. copy this modem???.bin to /sdcard
4. in TWRP, open terminal
5.
Code:
dd if=/sdcard/modem???.bin of=/dev/block/bootdevice/by-name/modem bs=512
6. reboot
And for LGUP error, you need a updated LGUP_c.dll, the 6.0 dll is not compatible with 7.0 downloader.
extract it from 20f(7.0) kdz file and try LGUP again.
Click to expand...
Click to collapse
wow you are a savior.
worked perfectly!
thank you

nnguyen04 said:
wow you are a savior.
worked perfectly!
thank you
Click to expand...
Click to collapse
Is it possible to downgrade without twrp? I haven't been able to root yet because i am on the latest rom. I am trying to downgrade to 6.0 but i am getting same errors. Tried different LGUP_c.dll's but i keep getting errors. I tried flashing modem in fastboot but that also gives error. Im at a loss. TIA!

NoMoreBackdoors said:
Is it possible to downgrade without twrp? I haven't been able to root yet because i am on the latest rom. I am trying to downgrade to 6.0 but i am getting same errors. Tried different LGUP_c.dll's but i keep getting errors. I tried flashing modem in fastboot but that also gives error. Im at a loss. TIA!
Click to expand...
Click to collapse
Used uppercut to downgrade. I had to select refurbish first and let it fail, then select upgrade and it was successful. Weird, but it allowed me to downgrade that way.

can I downgrad LG V521 from v20h to v20f or Marshmallow or not?
Thanks all

hsrose09 said:
can I downgrad LG V521 from v20h to v20f or Marshmallow or not?
Thanks all
Click to expand...
Click to collapse
i need to know too if nougat(20h) can be downgraded to marshmallow.

el_venga said:
i need to know too if nougat(20h) can be downgraded to marshmallow.
Click to expand...
Click to collapse
can

hsrose09 said:
can
Click to expand...
Click to collapse
Hi hsrose09,
How to do it? What tools do I need?
I feel it a little bit slower than previous 6.0.

CAN-L11C432 & CAN-L01C432 Updates

Here are the latest updates for the dual sim and single sim Nova variants:
CAN-L11C432:
Full Update:
CAN-L11C432B340: http://update.hicloud.com:8180/TDS/data/files/p3/s15/G79/g0/v77947/f1/full/update.zip
Changelog: http://update.hicloud.com:8180/TDS/data/files/p3/s15/G79/g0/v77947/f1/full/changelog.xml
Small Update:
CAN-L11C432B340: http://update.hicloud.com:8180/TDS/data/files/p3/s15/G79/g0/v77944/f1/full/update.zip
Changelog: http://update.hicloud.com:8180/TDS/data/files/p3/s15/G79/g0/v77944/f1/full/changelog.xml
CAN-L01C432:
Full Update:
CAN-L01C432B340: http://update.hicloud.com:8180/TDS/data/files/p3/s15/G79/g0/v77904/f1/full/update.zip
Changelog: http://update.hicloud.com:8180/TDS/data/files/p3/s15/G79/g0/v77904/f1/full/changelog.xml
Small Update:
CAN-L01C432B340: http://update.hicloud.com:8180/TDS/data/files/p3/s15/G79/g0/v77930/f1/full/update.zip
Changelog: http://update.hicloud.com:8180/TDS/data/files/p3/s15/G79/g0/v77930/f1/full/changelog.xml
The Full Updates you should be able to install from Marshmallow which will bring you to the current release of Nougat on the Nova and the Small Updates you can install from the Nova Nougat build CAN-L11C432B320 and CAN-L01C432B320.
If your device comes up with NRD90M test-keys then for the CAN-L11C432 variant you can try installing this after to get the correct Build number showing and functionality working: http://update.hicloud.com:8180/TDS/...-L11_hw_eu/update_data_full_CAN-L11_hw_eu.zip and for the CAN-L01C432 variant: http://update.hicloud.com:8180/TDS/...-L01_hw_eu/update_data_full_CAN-L01_hw_eu.zip.
I have managed to get it to work on the CAN-L01C432 variant but a couple of others have not managed to install the hw eu update for their device which has left them with NRD90M test-keys showing under Build number and themes not working.

I tried to update but it fails at 41%. I'm on CAN-L01C02B130 , Vodafone branded.

pasmadferit said:
I tried to update but it fails at 41%. I'm on CAN-L01C02B130 , Vodafone branded.
Click to expand...
Click to collapse
These updates are for CAN-L01C432 and CAN-L11C432 variants of the Nova. You can try this if you want to but I am not sure if it will work on a branded device: http://update.hicloud.com:8180/TDS/data/files/p3/s15/G79/g0/v74460/f1/full/update.zip. This is the latest Nougat update I have found for the CAN-L01C02 variant of the Nova.

lintern said:
These updates are for CAN-L01C432 and CAN-L11C432 variants of the Nova. You can try this if you want to but I am not sure if it will work on a branded device: http://update.hicloud.com:8180/TDS/data/files/p3/s15/G79/g0/v74460/f1/full/update.zip. This is the latest Nougat update I have found for the CAN-L01C02 variant of the Nova.
Click to expand...
Click to collapse
thanks for the link but i have the same problem. On "updater" the phone didn't find it, i tried with putting down the phone with volume and power keys but it gave me the same error at 41%. Shame on Huawei that don't release the original firmware yet >.<

pasmadferit said:
thanks for the link but i have the same problem. On "updater" the phone didn't find it, i tried with putting down the phone with volume and power keys but it gave me the same error at 41%. Shame on Huawei that don't release the original firmware yet >.<
Click to expand...
Click to collapse
I had the same problem at first but after flashing this: https://drive.google.com/open?id=0B4T1GJ6EZ3LvTWNpZ0p5YXVINGs the Nougat update installed fine. The link is the stock EMUI 5 recovery which is for Nougat which I got of this page: https://forum.xda-developers.com/nova-plus/how-to/c432b320-android-7-0-available-try-t3527084/page7.

lintern said:
I had the same problem at first but after flashing this: https://drive.google.com/open?id=0B4T1GJ6EZ3LvTWNpZ0p5YXVINGs the Nougat update installed fine. The link is the stock EMUI 5 recovery which is for Nougats which I got of this page: https://forum.xda-developers.com/nova-plus/how-to/c432b320-android-7-0-available-try-t3527084/page7.
Click to expand...
Click to collapse
I'll try, thanks for the help man

pasmadferit said:
I'll try, thanks for the help man
Click to expand...
Click to collapse
It's up to you if you want to try it. You have to flash the recovery by adb first if you do this and then try updating again I see no reason why it should not work.

lintern said:
It's up to you if you want to try it. You have to flash the recovery by adb first if you do this and then try updating again I see no reason why it should not work.
Click to expand...
Click to collapse
I have to unlock bootloader first i think, right?

pasmadferit said:
I have to unlock bootloader first i think, right?
Click to expand...
Click to collapse
Unfortunately yes which is why I said it's up to you if you want to try it out. Some guys were lucky with the beta Nougat releases on the Nova which installed easily via the updater app or recovery on the device whereas you, me and others have had a bit more trouble which has required us to do more to update. Where it is a official Huawei recovery you may be able to flash it with adb without issues but I'm not sure. It's your call if you want to try it.

Thanks for the help man, i flashed first the recovery and then the update and all was ok. Very grateful.

pasmadferit said:
Thanks for the help man, i flashed first the recovery and then the update and all was ok. Very grateful.
Click to expand...
Click to collapse
No problem, did you install CAN-L01C02B130B407?

lintern said:
No problem, did you install CAN-L01C02B130B407?
Click to expand...
Click to collapse
I don't know what firmware is... In settings It shows me only model Number (Huawei CAN-L01) and serial number. Do you know how i can see it on emui 5.0?

pasmadferit said:
I don't know what firmware is... In settings It shows me only model Number (Huawei CAN-L01) and serial number. Do you know how i can see it on emui 5.0?
Click to expand...
Click to collapse
Extract this: http://update.hicloud.com:8180/TDS/...-L01_ti_it/update_data_full_CAN-L01_ti_it.zip and put the UPDATE.APP in a dload folder on the root of your SD Card and install it like the main Nougat update. This should fix it so the Build number shows up correctly and some other functionality issues. Once this is done next to Build Number it should say: CAN-L01C02B307, if it does then everything is working fine.

Hey I have downloaded CAN-l01 version, installed via fastboot (recovery.img, boot.img and system.img) but the updater is still missing from settings and the version number is NRD90M test-keys i'm not able to install the eu pack (update stops at 5%), how can I solve the missing updater?

mArIuS% said:
Hey I have downloaded CAN-l01 version, installed via fastboot (recovery.img, boot.img and system.img) but the updater is still missing from settings and the version number is NRD90M test-keys i'm not able to install the eu pack (update stops at 5%), how can I solve the missing updater?
Click to expand...
Click to collapse
I never installed mine by fastboot using adb, I extrated the big update then put it in a dload folder and installed using the three button method. I dunno why the hw eu pack is not installing as I had this issue and that installed fine for me.
If you installed this: http://update.hicloud.com:8180/TDS/data/files/p3/s15/G79/g0/v77904/f1/full/update.zip then try installing this using the three button method: http://update.hicloud.com:8180/TDS/...-L01_hw_eu/update_data_full_CAN-L01_hw_eu.zip and if you have tried that and it did not work then try this: http://update.hicloud.com:8180/TDS/...L01_hw_eu/update_data_full_CAN-L01_hw_eu.zip.

lintern said:
I never installed mine by fastboot using adb, I extrated the big update then put it in a dload folder and installed using the three button method. I dunno why the hw eu pack is not installing as I had this issue and that installed fine for me.
If you installed this: http://update.hicloud.com:8180/TDS/data/files/p3/s15/G79/g0/v77904/f1/full/update.zip then try installing this using the three button method: http://update.hicloud.com:8180/TDS/...-L01_hw_eu/update_data_full_CAN-L01_hw_eu.zip and if you have tried that and it did not work then try this: http://update.hicloud.com:8180/TDS/...L01_hw_eu/update_data_full_CAN-L01_hw_eu.zip.
Click to expand...
Click to collapse
It was the only way I was able to install the update method of the three buttons stopped updating to 5% whatever recovery I use.
Update.zip archive goes installed from CWM?

mArIuS% said:
It was the only way I was able to install the update method of the three buttons stopped updating to 5% whatever recovery I use.
Update.zip archive goes installed from CWM?
Click to expand...
Click to collapse
I have no idea then. The update worked fine for me using the three button method and all I had to do after was install the hw eu update that matched and it is all working fine. Yes you can install archived updates through custom recovery but I have not tried it with Huawei updates so I dunno what the outcome will be.
Here is a couple of screenshots which show the update working for me.

Flashed the CAN-L11C432B340 full update with the 3-button-method coming from Emui 4.1 (Android 6).
The update was successful up to 100%, but then I got a flash failed error. Phone booted succesful to Emui 5.0 with the NRD90M test-keys bug so in addition i flashed update_data_full_CAN-L11_hw_eu.zip and all seems to be fine except the hotspot functionality.
Does the hotspot feature work for you on B340? I cant enable it and after a while i get a settings force close....

will this work on Canadian Huawei Nova Plus variant?

jrosero said:
will this work on Canadian Huawei Nova Plus variant?
Click to expand...
Click to collapse
If your device Is CAN-L01C432 or CAN-L11C432 then yes if not then no.

T-Mobile Oreo FLASHALL???

Does anyone have a TMO Moto Z2 Force FLASHALL for the lastest OREO build?
I was on Oreo and i was testing a ROM in Devlopement and someone BASEBAND <not found> so i have no WiFi, no signal, but on a good note the ROM booted...
So any with an TMO OREO FlashAll, please share...
Thanks in advance

I haven't been able to find anyone or any place that has the latest TMO flash all available, but here is the update for the previous 8.0 update for TMO:
here

Shiro12 said:
I haven't been able to find anyone or any place that has the latest TMO flash all available, but here is the update for the previous 8.0 update for TMO:
here
Click to expand...
Click to collapse
Thanks but i need the entire build, not just the up date. I lost my MAC and IMEI and the full firmware is my only way of fixing it, i think

AndroidDevices said:
Thanks but i need the entire build, not just the up date. I lost my MAC and IMEI and the full firmware is my only way of fixing it, i think
Click to expand...
Click to collapse
That should be what you need, I came from a test build for Nash and used the FlashAll zip (RET specifically) from that site to take me all the way back to stock., Hence why each zip is ~3GB uncompressed.

Shiro12 said:
That should be what you need, I came from a test build for Nash and used the FlashAll zip (RET specifically) from that site to take me all the way back to stock., Hence why each zip is ~3GB uncompressed.
Click to expand...
Click to collapse
There is no FLASHALL in the file and i cannot get RSD to recognize device is in fastboot mode

extract This into the firmware's folder and adapt the bat file as needed

Shiro12 said:
extract This into the firmware's folder and adapt the bat file as needed
Click to expand...
Click to collapse
Thanks, flashed and still no baseband... wtf

AndroidDevices said:
Thanks, flashed and still no baseband... wtf
Click to expand...
Click to collapse
There should be a NON_HLOS.bin in that folder, if im not mistaken a fastboot command posted here should fix that, but i should mention that i have not done this myself and can not vouch for it. maybe someone else has a more (for a lack of a better word) trusted way to fix your issue

Shiro12 said:
There should be a NON_HLOS.bin in that folder, if im not mistaken a fastboot command posted here should fix that, but i should mention that i have not done this myself and can not vouch for it. maybe someone else has a more (for a lack of a better word) trusted way to fix your issue
Click to expand...
Click to collapse
I'm having the same issue. I've downloaded every 2+gb zipped XT1789-04 factory reset zip I can get my hands on. It says it's flashing a modem, but I still get no baseband when I go into fastboot. no wifi or cell signal. I've tried the commands linked above after flashing. If someone has a solution I'd be eternally grateful.

Shiro12 said:
There should be a NON_HLOS.bin in that folder, if im not mistaken a fastboot command posted here should fix that, but i should mention that i have not done this myself and can not vouch for it. maybe someone else has a more (for a lack of a better word) trusted way to fix your issue
Click to expand...
Click to collapse
Thanks but NO GO .

I ran into this problem attempting to root the latest Oreo OCX27.1 and got into a bootloop. The only Oreo firmware available to download isis the previous OCX27 and I believe that downgrading to that causes the lost of baseband and imei. I am waiting to see when OCX27.1 will be available to download so I can try to return to stock to 27.1 see if it restores my baseband

The problem i am seeing is that none of the stock firmware are for ocx27.1. they are all for ocx27. i have seen an ota update that is for the ocx27.1 but i have not figured out how to extract it yet

mattlowry said:
The problem i am seeing is that none of the stock firmware are for ocx27.1. they are all for ocx27. i have seen an ota update that is for the ocx27.1 but i have not figured out how to extract it yet
Click to expand...
Click to collapse
https://forum.xda-developers.com/z2-force/help/tmo-oxc27-1-oreo-firmware-t3757469

droidgreg said:
https://forum.xda-developers.com/z2-force/help/tmo-oxc27-1-oreo-firmware-t3757469
Click to expand...
Click to collapse
thats the ota. if you know of a way to extract the contents of the rom for that file i would love to hear it

mattlowry said:
thats the ota. if you know of a way to extract the contents of the rom for that file i would love to hear it
Click to expand...
Click to collapse
Open the file win Winrar or any Zip program and you should be able to extract the contents

droidgreg said:
Open the file win Winrar or any Zip program and you should be able to extract the contents
Click to expand...
Click to collapse
not exactly what im looking for. all of the rom contents are loaded in the payload.bin file. That is the file we need extracted

mattlowry said:
not exactly what im looking for. all of the rom contents are loaded in the payload.bin file. That is the file we need extracted
Click to expand...
Click to collapse
I tried daemon tools lite and PowerISO but both failed to extract the bin file. I'll keep looking...

droidgreg said:
I tried daemon tools lite and PowerISO but both failed to extract the bin file. I'll keep looking...
Click to expand...
Click to collapse
from what i have seen there is not a way to extract it currently

I'm gonna mess with it in linux. I'm no dev but I'll see what I can pull apart, hopefully I find something useful.

https://drive.google.com/file/d/13pKSMS5zGuYsr1EEDma0L6AxHDSUmu2g/view?usp=drivesdk

Looking for NPPS25.137-93-14 fastboot firmware

Could somebody provide full untouched fastboot firmware with build number NPPS25.137-93-14 for DualSIM Moto G5 (XT1676) with reteu software channel and 3GB RAM/16GB ROM, please? Thanks in advance.

https://forum.xda-developers.com/g5/development/official-stock-moto-g5-cedric-firmware-t3733897

I have been looking for it during several weeks too, no success until now. I found 137-92-14, which is built for other software channels. It works well in my XT1685 (Dual sim 3GB/32GB reteu).
Still looking for 137-93-14... Regards.

Doesn't XT1685 equal G5 Plus?

Andrej_SK said:
Doesn't XT1685 equal G5 Plus?
Click to expand...
Click to collapse
Yes.
Enviado desde mi Moto G (5) Plus mediante Tapatalk

Andrej_SK said:
Could somebody provide full untouched fastboot firmware with build number NPPS25.137-93-14 for DualSIM Moto G5 (XT1676) with reteu software channel and 3GB RAM/16GB ROM, please? Thanks in advance.
Click to expand...
Click to collapse
How can I provide you with fastboot firmware as I am having same build version with untouched fastboot firmware.but I am having xt1677 with same specs.

I'm also looking for NPPS25.137-93-14 (or NPPS25.137-93-12)... I only need the stock recovery.img file of either of the two...

Ok I will update recovery for you. Which varient it is if amzin one link will be uploaded at evening. Just let me know. Waiting for reply?

Aaric leo's el drigo said:
Ok I will update recovery for you. Which varient it is if amzin one link will be uploaded at evening. Just let me know. Waiting for reply?
Click to expand...
Click to collapse
Mine is retail. Either *-12 or * -14 recovery.img will be ok.
Thanks.
Sent from my Moto G5 using XDA Labs

Ok I will upload it. As fast as possible
---------- Post added at 04:38 AM ---------- Previous post was at 03:42 AM ----------
Because I can't fine firmware online to download, or I don't have retail varient so I can't help you. But if you have laptop, pc. I can help let you know how you can download firmware. Let me know if you need guide as fast as possible.

leohussey said:
I'm also looking for NPPS25.137-93-14 (or NPPS25.137-93-12)... I only need the stock recovery.img file of either of the two...
Click to expand...
Click to collapse
You can flash older recovery without bricking the phone. However, don't do that if you are running CustomROM. In my case, when I wanted to revert to fully updated stock, I flashed NPPS25.137-93-8 firmware without gpt, bootloader (that's what would brick the phone if flashed) and erase modem commands, updated it to NPPS25.137-93-12, then to NPPS25.137-93-14 using stock recovery and these files https://drive.google.com/drive/folders/1BkpfHvgQ477NViLYvzgv88Fgq3SSt5Py. No issues at all and my phone (XT1676, 3/16, DualSIM, reteu) is still working fine.
In the attachment, I'll put recovery.zip (with recovery.img inside of it) of the NPPS25.137-93-8. Use at your own risk, if you are interested.

Andrej_SK said:
You can flash older recovery without bricking the phone. However, don't do that if you are running CustomROM. In my case, when I wanted to revert to fully updated stock, I flashed NPPS25.137-93-8 firmware without gpt, bootloader (that's what would brick the phone if flashed) and erase modem commands, updated it to NPPS25.137-93-12, then to NPPS25.137-93-14 using stock recovery and these files https://drive.google.com/drive/folders/1BkpfHvgQ477NViLYvzgv88Fgq3SSt5Py. No issues at all and my phone (XT1676, 3/16, DualSIM, reteu) is still working fine.
In the attachment, I'll put recovery.zip (with recovery.img inside of it) of the NPPS25.137-93-8. Use at your own risk, if you are interested.
Click to expand...
Click to collapse
Thanks.
But thing is: I'm currently on NPPS25.137-93-12 with TWRP and Magisk. As a proof of concept I want to go to *-14 via OTA to see if it is possible... And if so: to make the oreo jump when available for my channel (XT1671, 2 sim, retla). I want to avoid losing all my data or any long task that would keep me offline for a long time... Daily driver both work and personal...
Uninstalling Magisk reverts boot.img to stock.... but I still need the stock recovery.img to be in 100% stock state (but unlocked). That's the theory.
Tried yesterday using other recovery.img versions, but failed: /cache/recovery/last_log shows the Blur* OTA file updater-script explicitly checks recovery version to be either source or destination versions... So *-12 or *-14.
After that, updater-script checks boot, system and oem. Those are (will be, supposedly) stock since Magisk only patches boot.img and I'll uninstall it .... should work...
The longer path of flashing other version and do the OTAs is also possible... But I'd have to be on vacation or something...
Thanks again.
Sent from my Moto G5 using XDA Labs

leohussey said:
Thanks.
But thing is: I'm currently on NPPS25.137-93-12 with TWRP and Magisk. As a proof of concept I want to go to *-14 via OTA to see if it is possible... And if so: to make the oreo jump when available for my channel (XT1671, 2 sim, retla). I want to avoid losing all my data or any long task that would keep me offline for a long time... Daily driver both work and personal...
Uninstalling Magisk reverts boot.img to stock.... but I still need the stock recovery.img to be in 100% stock state (but unlocked). That's the theory.
Tried yesterday using other recovery.img versions, but failed: /cache/recovery/last_log shows the Blur* OTA file updater-script explicitly checks recovery version to be either source or destination versions... So *-12 or *-14.
After that, updater-script checks boot, system and oem. Those are (will be, supposedly) stock since Magisk only patches boot.img and I'll uninstall it .... should work...
The longer path of flashing other version and do the OTAs is also possible... But I'd have to be on vacation or something...
Thanks again.
Sent from my Moto G5 using XDA Labs
Click to expand...
Click to collapse
Try one more time with file in the attachment of this reply. Although you will get "Image signed with key bad key" (because it's simply extracted from NPPS25.137-93-14), it should flash just fine. In my case, I've tried to flash it with fully updated phone to NPPS25.137-93-14, no issues at all. However, you should be more careful if you are running .12 firmware - this is stock and newer recovery (recovery of .14 firmware). .
Okay, so there are already 2 files in the attachment, first one contains recovery.img of .12 firmware, second one of the .14 firmware. You can recognize them by name of the file. With each of them, you will still get "Image signed with key bad key" message when flashing, but they flash just fine and everything seems to be working flawlessly on my phone with coresponding firmware version (means .12 recovery for .12 firmware, .14 recovery for .14 firmware). Once again, you are doing it at your own risk if you decide to.

Andrej_SK said:
Try one more time with file in the attachment of this reply. Although you will get "Image signed with key bad key" (because it's simply extracted from NPPS25.137-93-14), it should flash just fine. In my case, I've tried to flash it with fully updated phone to NPPS25.137-93-14, no issues at all. However, you should be more careful if you are running .12 firmware - this is stock and newer recovery (recovery of .14 firmware). Once again, you are doing it at your own risk.
Click to expand...
Click to collapse
Thanks. I'll test tonight.
"Bad key" is no problem... Got it twice already by testing with other versions I was able to get.
As for it being from *-14, it should work if I believe the updater script checking for either *-12 recovery (source) or *-14 recovery (target)... We'll see.
Sent from my Moto G5 using XDA Labs
---------- Post added at 06:31 PM ---------- Previous post was at 06:28 PM ----------
Andrej_SK said:
Try one more time with file in the attachment of this reply. Although you will get "Image signed with key bad key" (because it's simply extracted from NPPS25.137-93-14), it should flash just fine. In my case, I've tried to flash it with fully updated phone to NPPS25.137-93-14, no issues at all. However, you should be more careful if you are running .12 firmware - this is stock and newer recovery (recovery of .14 firmware). .
Okay, so there are already 2 files in the attachment, first one contains recovery.img of .12 firmware, second one of the .14 firmware. You can recognize them by name of the file. With each of them, you will still get "Image signed with key bad key" message when flashing, but they flash just fine and everything seems to be working flawlessly on my phone with coresponding firmware version (means .12 recovery for .12 firmware, .14 recovery for .14 firmware). Once again, you are doing it at your own risk if you decide to.
Click to expand...
Click to collapse
Hm... By the time I quoted to answer, you updated. Cool.
Then I'll test directly on 12. Thanks.
Another question: are you extracting them from your own phone? If so, how? Untill now I only found possible by rooting, but rooting means changing recovery in first place... So... Hen and egg...
Sent from my Moto G5 using XDA Labs

leohussey said:
Another question: are you extracting them from your own phone? If so, how? Untill now I only found possible by rooting, but rooting means changing recovery in first place... So... Hen and egg...
Sent from my Moto G5 using XDA Labs
Click to expand...
Click to collapse
Yes, I rooted my phone by Magisk and used app called Flashify to backup recovery. However, to root, I didn't install TWRP permanently by "fastboot flash recovery twrp.img" command, I just booted into it by "fastboot boot twrp.img", so I was able to root my phone and keep stock recovery installed.

Andrej_SK said:
Yes, I rooted my phone by Magisk and used app called Flashify to backup recovery. However, to root, I didn't install TWRP permanently by "fastboot flash recovery twrp.img" command, I just booted into it by "fastboot boot twrp.img", so I was able to root my phone and keep stock recovery installed.
Click to expand...
Click to collapse
Thanks. I had been reading about it and some posts were misleading saying it was no longer possible and others said it was. Had not gotten down to test it yet. So now I know it works, I'll do it. Thanks again.
Sent from my Moto G5 using XDA Labs

Update: tested.
good: Recovery image -12 worked without issue and updater-script check passed.
bad: it failed while validating boot.img.
Apparently, Magisk uninstall did not restore the boot partition to stock. I also had a TWRP backup from when I had just unlocked. Restored boot. No luck. Maybe I took the backup *after* rooting.
well... I guess I will have to wait until I have some free time to do the long way: full flash
EDIT: @Andrej_SK: would you by any chance have the boot.img of *-12 too?
thanks!!

I am reading this tread form more then 2 days. I already told you I can help but it seems no one want know what I am saying. But it's now seem a serious tread so I will tell in anyway if someone is interested or not.
Guide to repair Moto Lenovo models.
Note: pc, laptop required.
1. Download latest driver for moto device.
2. Download Lenovo Moto smart assistant.
3. Enable usb debugging in developer options.
4. Click on Flash button on top of your tab bar.
5. Click on rescue.
6. Get into bootloader , fastboot.
7. Download your current varient latest firmware.
And all done.
Now you have your firmware with latest security patch.
You can relock bootloader and whatever you like.
Have fun enjoy.

Thanks a lot. This tool won't work if you have lost your IMEI, but it allows you to download the latest firmware (in my case 137-93-14). Using this full stock firmware I have been able to recover the IMEI following the steps explained in other topic in this forum.
Regards.

leohussey said:
EDIT: @Andrej_SK: would you by any chance have the boot.img of *-12 too?
Click to expand...
Click to collapse
I might give it a try, if you give me some time.